I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
http://forum.xda-developers.com/showthread.php?t=2001868
Everything will work fine. All that I have ever found not working is my employer's software developed only for the employees. No mass produced app will give you any trouble.
Enjoy CM10!
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
DroidBois said:
I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
You lose everything, including your home and first-born child.
In all seriousness, just about everything will work fine if you only root. Some custom ROMs do introduce incompatibility problems, but it's usually on a pretty small scale (an app here or there might not work if your ROM/kernel choice tweaks how the device handles graphics, for example). By and large, you should be fine, but be careful of certain content apps that will refuse to play on rooted devices.
SacGuru said:
Everything will work fine. All that I have ever found not working is my employer's software developed only for the employees. No mass produced app will give you any trouble.
Enjoy CM10!
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
Come now, you know that's not entirely true. Many stuck-up content providers won't support rooted devices, and you'll also get the standard "unsupported device" claim if you're rooted or have an unlocked bootloader from apps like Google Wallet. By and large though, OP, you should be fine.
Rirere said:
You lose everything, including your home and first-born child.
In all seriousness, just about everything will work fine if you only root. Some custom ROMs do introduce incompatibility problems, but it's usually on a pretty small scale (an app here or there might not work if your ROM/kernel choice tweaks how the device handles graphics, for example). By and large, you should be fine, but be careful of certain content apps that will refuse to play on rooted devices.
Come now, you know that's not entirely true. Many stuck-up content providers won't support rooted devices, and you'll also get the standard "unsupported device" claim if you're rooted or have an unlocked bootloader from apps like Google Wallet. By and large though, OP, you should be fine.
Click to expand...
Click to collapse
You are right, but I was responding to what the OP had asked. Movies from play will work just fine afaik. And yes, there would be some app developers who won't support modified devices (I've heard of some trouble with the Sky tv app), but then again on some devices there are ways to temporarily unroot to allow such apps to run.
Again, how the device handles graphics can be modified as well. I had trouble with the Naked Browser before I modified the dpi using an xposed framework module.
In simple terms, so as to not confuse things, I would say that the huge majority of apps would give him no problems, and he would be missing out a lot if he refuses to root his device in the fear of one or two apps not working.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
You are right, but I was responding to what the OP had asked. Movies from play will work just fine afaik. And yes, there would be some app developers who won't support modified devices (I've heard of some trouble with the Sky tv app), but then again on some devices there are ways to temporarily unroot to allow such apps to run.
Again, how the device handles graphics can be modified as well. I had trouble with the Naked Browser before I modified the dpi using an xposed framework module.
In simple terms, so as to not confuse things, I would say that the huge majority of apps would give him no problems, and he would be missing out a lot if he refuses to root his device in the fear of one or two apps not working.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
There's a fine line between "not confus[ing] things" though and glossing over very real issues. It's significantly better for a new user to go into rooting aware of potential problems than rush in and get screwed on something because they expected rooting to be a land of sunshine, rainbows, and daisies, and found it was actually one that also had blood and tears.
That's especially true when you start getting into things like XPosed modules, which, while simple are much more than a new user should really have to contend with. Full stock+rooted is probably the safest introduction because it's so comparatively trivial to revert if you blow yourself up.
Rirere said:
There's a fine line between "not confus[ing] things" though and glossing over very real issues. It's significantly better for a new user to go into rooting aware of potential problems than rush in and get screwed on something because they expected rooting to be a land of sunshine, rainbows, and daisies, and found it was actually one that also had blood and tears.
That's especially true when you start getting into things like XPosed modules, which, while simple are much more than a new user should really have to contend with. Full stock+rooted is probably the safest introduction because it's so comparatively trivial to revert if you blow yourself up.
Click to expand...
Click to collapse
I know people who went on to custom roms the day they rooted their phones. I myself used one within a fortnight of using my first android device. Rooting isn't exactly rocket science.
I would really like to know what percentage of apps you believe do not work on custom roms/rooted phones out of all apps in the world. Impossible though it might be to have an exact number, I have a slight suspicion you have a larger-than-what-could-be-true figure in your head. While at it, do mention some of the blood and tears you have had while using your device.
In all the time I have been using android devices, I have only once encountered an app which I couldn't run on my device, and I believe that was purely due to lack of effort on my part.
Again, many people turn on to modifying their devices only because they want to use a custom rom, as the OP already wants to. I have never seen a comment by an user who regrets rooting his device as an app isn't working. I have seen numerous from users who are disappointed with the capabilities of their unrooted devices.
Had you understood my second comment, you would have realized that not only had I agreed with what you had said, I had also, unlike you, actually mentioned a couple of apps which might have problems on a rooted device. Glossing over issues might be wrong, but complicating simple questions is worse, in my opinion.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
I know people who went on to custom roms the day they rooted their phones. I myself used one within a fortnight of using my first android device. Rooting isn't exactly rocket science.
I would really like to know what percentage of apps you believe do not work on custom roms/rooted phones out of all apps in the world. Impossible though it might be to have an exact number, I have a slight suspicion you have a larger-than-what-could-be-true figure in your head. While at it, do mention some of the blood and tears you have had while using your device.
In all the time I have been using android devices, I have only once encountered an app which I couldn't run on my device, and I believe that was purely due to lack of effort on my part.
Again, many people turn on to modifying their devices only because they want to use a custom rom, as the OP already wants to. I have never seen a comment by an user who regrets rooting his device as an app isn't working. I have seen numerous from users who are disappointed with the capabilities of their unrooted devices.
Had you understood my second comment, you would have realized that not only had I agreed with what you had said, I had also, unlike you, actually mentioned a couple of apps which might have problems on a rooted device. Glossing over issues might be wrong, but complicating simple questions is worse, in my opinion.
Click to expand...
Click to collapse
You're starting to get a little touchy there.
I've been rooted and flashing ROMs for several years now, so I'm hardly new to the field. Nor do I think that there's even a large portion of apps out there that have trouble on rooted devices-- because that is not the point. From an end-user perspective, it only takes the loss of one app or a misbehaving one to ruin the experience. A great day-to-day example is Foldersync-- while the app "runs" correctly, if it detects you have root privileges it will spam superuser requests to perform a better sync. If you deny the request, your sync may fail, and if you accept it, the app potentially causes a wakelock. Random behavior can be just as bad as an outright crash.
OP's interest with ROMs is also a point of greater concern than just root. You really don't have to look too far to see people having problems, especially if you every venture outside of Nexus-land. The last hulabaloo I saw over this was back in the HTC One forums because a popular AOSP ROM had a misconfigured graphics driver that caused a few games to fall over and die.
As far as blood, sweat, and tears, try a bootlooping Galaxy Player 4.0 with a wiped /efs that was essentially softbricked for about two months before I had a free six or seven hours to manually dd everything back into place. I've also had my share of bootloops on Nexus devices while experimenting, although with a little fastboot or adb knowledge it's not hard to get out of them.
I have seen plenty of people regret their root or flash. I don't think you quite remember how bad the first bootloop or problem can be if you have never messed with this stuff before. Fastboot and adb are pretty easy to learn to use, but when you're first starting and every black screen seems like the death knell, it's a different matter altogether. Yes, I saw your post, and I understood, but it's a lot better to play it safe, especially at first, then charge ahead unaware of the consequences. Don't tell me you haven't seen people whining in countless ROM threads because they've done something stupid, usually because they didn't know not to.
Bottom line: better to play it safe and know than not. The only point I made up top was that you have to be 100% aware that you're playing with fire before you get burned. That doesn't mean fire isn't useful or that it's scary, but it does mean you have to be careful.
Edit
SacGuru said:
The whole point of my second post was that there are alternatives - to roms, to mods, to apps, to hardware limitations. The availability of these alternatives is amongst the prime reasons we love android, you and I.
The Op is not asking us about Softbricks/bootlooping devices, or black screens. He is asking only about apps. As I said before, I haven't yet seen a comment from someone who wants to unroot his device just because a particular app does not work. It might be possible that with your experience you might have seen one or two, but as you mention yourselves, people sometimes tend to be stupid.
It's unfortunate that I sounded touchy to you. My only answer to the Op still remains that it would be highly unlikely for him to have trouble with apps, even though there could be apps which do not work on modded phones (as I did mention in my very first comment).
Click to expand...
Click to collapse
I think we're reading the comment a little differently. This is why I brought up what I did.
I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
Click to expand...
Click to collapse
Based on the questions being asked, I think it's reasonable to assume OP doesn't know anything about rooting or ROMs, so I'm being a little more liberal in looking at this comment than I would be otherwise. As such, I'd rather err on giving them information a little outside the original scope than too little.
Rirere said:
You're starting to get a little touchy there.
I've been rooted and flashing ROMs for several years now, so I'm hardly new to the field. Nor do I think that there's even a large portion of apps out there that have trouble on rooted devices-- because that is not the point. From an end-user perspective, it only takes the loss of one app or a misbehaving one to ruin the experience. A great day-to-day example is Foldersync-- while the app "runs" correctly, if it detects you have root privileges it will spam superuser requests to perform a better sync. If you deny the request, your sync may fail, and if you accept it, the app potentially causes a wakelock. Random behavior can be just as bad as an outright crash.
OP's interest with ROMs is also a point of greater concern than just root. You really don't have to look too far to see people having problems, especially if you every venture outside of Nexus-land. The last hulabaloo I saw over this was back in the HTC One forums because a popular AOSP ROM had a misconfigured graphics driver that caused a few games to fall over and die.
As far as blood, sweat, and tears, try a bootlooping Galaxy Player 4.0 with a wiped /efs that was essentially softbricked for about two months before I had a free six or seven hours to manually dd everything back into place. I've also had my share of bootloops on Nexus devices while experimenting, although with a little fastboot or adb knowledge it's not hard to get out of them.
I have seen plenty of people regret their root or flash. I don't think you quite remember how bad the first bootloop or problem can be if you have never messed with this stuff before. Fastboot and adb are pretty easy to learn to use, but when you're first starting and every black screen seems like the death knell, it's a different matter altogether. Yes, I saw your post, and I understood, but it's a lot better to play it safe, especially at first, then charge ahead unaware of the consequences. Don't tell me you haven't seen people whining in countless ROM threads because they've done something stupid, usually because they didn't know not to.
Bottom line: better to play it safe and know than not. The only point I made up top was that you have to be 100% aware that you're playing with fire before you get burned. That doesn't mean fire isn't useful or that it's scary, but it does mean you have to be careful.
Click to expand...
Click to collapse
The whole point of my second post was that there are alternatives - to roms, to mods, to apps, to hardware limitations. The availability of these alternatives is amongst the prime reasons we love android, you and I.
The Op is not asking us about Softbricks/bootlooping devices, or black screens. He is asking only about apps. As I said before, I haven't yet seen a comment from someone who wants to unroot his device just because a particular app does not work. It might be possible that with your experience you might have seen one or two, but as you mention yourselves, people sometimes tend to be stupid.
It's unfortunate that I sounded touchy to you. My only answer to the Op still remains that it would be highly unlikely for him to have trouble with apps, even though there could be apps which do not work on modded phones (as I did mention in my very first comment). Somehow your answer seemed pretty similar to mine ('just about everything would be fine'), so I just wondered why you had to mention to me problems with apps like the google wallet which are easily fixed.
By now, I am sure both of us understand what the other is talking about. Also, the op has enough info to take a decision on his own. My only qualm is that the inclusion of some seemingly complex terminology might turn him off rooting his device
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Wow... I just love you guys so much... So much detailed analysis here..
I've rooted all my devices in the past and generally not had any issues if I use a mature solid tool and ROM, I've only had issues with more 'pioneering' ROM's and tools, but for good reason. So I try to stick to the stable well tested mature varieties like Cyanogen and well supported tools, generally where the developer gets some payment (as reward encourages good development).
I'm more concerned with anything like content apps so Google Books / Magazines / Movies / Zinio etc or any other apps that may kick a stink about running on a rooted device?
Spotify seems fine on a rooted device so far though (Nexus 4).
It may not be an issue for some, but I am one of the (possibly rare?) people who PAY for content - specifically reading material. And I have an extensive library so I don't want to lose that.
I'm not so concerned on the technical front as the Nexus should be fairly well community supported and understood mainstream devices and likely to have stable development and mature community support.
I have the mskip tool ready to go so I'm fine with that.
It's not a debate about rooting vs not. I always root because simple things like having a quick tile for WLAN AP can make a HUGE difference through the day as opposed to this retarded idea that people ENJOY diving deep through menu layers for simple on / off functions - it drives me completely and utterly insane over the course of a day. So I like to set up and streamline my device how I need it, and even have accurate time with root tools like ClockSync, or better security support to lock out spyware crap like FaceSpy and so on (if root helps) and also, being able to properly back up my phone.
Or employer mandated junk like Afaria that some companies mandate for BYOD-to-work devices, not that I have any idea what it's for as opposed to a trusted workable solution like Google Apps (I guess everyone has to make their own thing to put their own buggy bloated stamp on everything). Will that mandated junk still work?
The biggest problem I have still is this MTP *CRAP* which which I believe you can't work around? That's another story and Google should be shot for this.
But root vs not has little to do with that. I guess we're stuck with this MTP crap no matter what we do (thanks Google, you tools).
Thanks for the advice here though.
DroidBois said:
Wow... I just love you guys so much... So much detailed analysis here..
I've rooted all my devices in the past and generally not had any issues if I use a mature solid tool and ROM, I've only had issues with more 'pioneering' ROM's and tools, but for good reason. So I try to stick to the stable well tested mature varieties like Cyanogen and well supported tools, generally where the developer gets some payment (as reward encourages good development).
I'm more concerned with anything like content apps so Google Books / Magazines / Movies / Zinio etc or any other apps that may kick a stink about running on a rooted device?
Spotify seems fine on a rooted device so far though (Nexus 4).
It may not be an issue for some, but I am one of the (possibly rare?) people who PAY for content - specifically reading material. And I have an extensive library so I don't want to lose that.
I'm not so concerned on the technical front as the Nexus should be fairly well community supported and understood mainstream devices and likely to have stable development and mature community support.
I have the mskip tool ready to go so I'm fine with that.
It's not a debate about rooting vs not. I always root because simple things like having a quick tile for WLAN AP can make a HUGE difference through the day as opposed to this retarded idea that people ENJOY diving deep through menu layers for simple on / off functions - it drives me completely and utterly insane over the course of a day. So I like to set up and streamline my device how I need it, and even have accurate time with root tools like ClockSync, or better security support to lock out spyware crap like FaceSpy and so on (if root helps) and also, being able to properly back up my phone.
Or employer mandated junk like Afaria that some companies mandate for BYOD-to-work devices, not that I have any idea what it's for as opposed to a trusted workable solution like Google Apps (I guess everyone has to make their own thing to put their own buggy bloated stamp on everything). Will that mandated junk still work?
The biggest problem I have still is this MTP *CRAP* which which I believe you can't work around? That's another story and Google should be shot for this.
But root vs not has little to do with that. I guess we're stuck with this MTP crap no matter what we do (thanks Google, you tools).
Thanks for the advice here though.
Click to expand...
Click to collapse
I've not had any problems with Google Play services and root, although most of my books are sideloaded after ripping DRM off of Amazon purchases (I don't really believe in the idea of a "perpetual lease"). As someone who has spent time working on that "employer junk" for corporate use, it may annoy the living **** out of you as a rooted user, but from a corporate standpoint it's actually pretty damn important.
Now, as far as MTP goes, don't quote me on this, but I remember seeing a setting in DriveDroid a while back (it's an app that lets you mount an ISO on your computer by connecting your device) that would let you change your USB connection mode to something other than MTP/PTP. I dont' remember the acronym, unfortunately, but it was a lot more in line with the way a "standard" USB device would connect (with the attendant issues of not using FUSE).
Related
Just wondering if anyone knows details on how market listings work. I know there are some apps that show or not to certain phones, but is that just a version issue, a special exception google makes?
At any rate, it's moot, because if google has a solution, they aren't making it very clear to lots of people.
Anyway, the problem:
As android ages, the phones age, and the apps mature. There are lots of apps that won't adequately run on older phones, but as far as I can tell, the only recourse devs have is to put a note in the description, which stops no one from actually downloading it, then clogging the reviews with 1 star "does not work on the ___" reviews.
While this was always a problem, now that we've reached the point in time where this is starting to happen to Droid 1 users, it's less an annoyance, and more a serious issue. Ratings almost mean nothing on those apps, and it's hard to use the reviews to see if there are actually any real issues.
(There are 10 billion droid users, and because it was true for quite a while they seem particularly locked in to the "I have one of the better phones out there" mentality )
Ok, rant over. Not sure anyone else even notices this.
Also, I'm not sure the solution is to restrict access, but an official way to list the phones that work or don't work needs to be in place, and then maybe another dev option to still allow access*
Then, if your phone isn't compatible, but the dev okays downloading anyway, you are given an extra screen to dismiss, explaining the app probably wont work for you, and you aren't allowed to leave reviews.
*Not all phones are equal, a stock phone, and a tricked out custom kerneled OC'd version, are very different, so a user might opt to give it a whirl anyway.
I have several apps on the market. In the manifest for the app you declare the minimum version of Android required for the app, and it's my understanding that phones that do not have at least that version of Android will not see the app.
Now, just because an app doesn't work on one person's phone, and they write a nasty review saying "doesn't work on the Epic!" doesn't actually mean that it doesn't work on the Epic, it just means that one person couldn't get it to work. Also, the developer may have made some hardcoding choices (like directories, etc.) that are not universal, and that may lead to incompatibilities that were un-anticipated. But, other than version of Android, I'm not sure what else is available to a developer to restrict access.
Yeah, I figured you could set the version. It's too bad there's no way to control it a bit finer.
I also realize that it's entirely possible someone is just being an idiot, but the fact remains we're past the days where you could necessarily infer anything about the phones from the version, or NEED the latest API version to do something useful/cool.
There are apps that legitimately don't run on some phones, and I feel like google needs to offer an official solution, rather than rely on dev comments that no one reads.
Obviously there are lots of ways to fake what your phone is, and whatnot, so nothing is going to be perfect, but there needs to be some way to officially denote "This app only requires 2.2, but your phone can't be one that shipped with Cupcake"
Edit: perhaps an easier approach is to have a market setting that only factors ratings/reviews of people that have the same phone.
I also don't mean to sound like I install every 5 star app, and wont even think about installing a 3 star app, no matter what I've heard. I've just noticed this in apps I was installing for one reason or another, and felt bad for the devs. It also gives a little less incentive to provide new/cool things for those of us with better phones.
I also suppose there's no "official" guidelines on what these stars are supposed to mean, but to me 1 starring an ap that says "this won't work for you" when it doesn't work for you is like telling people your dentist sucks because he wouldn't change your oil or make you a burger.
Hey guys, remember when the carriers blocked wireless tethering apps from the market for 'their phones'? I don't believe they ever REMOVED the apps from the market, just tagged them in such a way that they are not visible to any of the phones they provide service for. Just a thought, maybe devs could do the same kind of 'blacklisting' based on model number...
Sent from my pocket rocket
This is what I type at 3 in the morning. Please read for a minute, I'll keep it short and get to the point. I feel NS owners should see this since they seem the most enthusiastic.
This is generally for Android as a whole, targeting Google. Wow, so it's been how many years since Android first came out? And what is the only other competitor in the market - oh right, iOS. iOS has been destroying the market with only one phone which rarely has any lag/bug/glitch issues, namely the 4S or the new 5 (minus the Maps).
The only reason Android has a large market share is due to the large number of phones at reasonable prices. That is all. There are only two competitors in this oligarchy, and one still can't do it right. Google engineers are apparently among the highest paid, yet they decide to constantly release updates which constantly has bugs. It is a pity, to look at many of you Android enthusiasts that are giving a lot of attention to Android development and are contributing to this world, when Google themselves is not treating you right, thus I feel that you are the reason that the brand is remaining strong. You guys have the capacity to overlook its bugs/lags and see what Android is there truly for. On the other hand, I doubt iOS users actually care about that topic since it is rarely seen.
Next, the phones. So we have like a thousand phones running Android from like 20 different manufacturers. What the..? Alright, phones that are aimed for a low budget do not count, but the Nexus devices that Google works on - they should be at least revolutionary. Google has to partner up with different manufacturers each time when creating the next Nexus? Talk about inconsistency, and inviting a lack of hardware acceleration with its software. Google can even build their own phones if they have to, but just get it right! I mean their latest phone, the Galaxy Nexus, is still not a stable phone (although I thought it would be). Samsung is actually holding it down and implementing their own stuff to create a good user experience (thus the success of the Galaxy line). Other than that, ALL other manufacturers are literally wasting money (but producing profits) by adopting Android and Google themselves are getting much more love than they should be getting.
Creating new updates and naming them after the alphabet and weird food names is quite cheesy. That's not the issue though, it creates hype by many users - the anxiety of waiting for the next update that will 'fix all problems' - but what happens? Promises are broken, and the software is bad once again. Like the JB update - turns out it's bad and many/most users tend to agree. So much for project butter haha. It's simply not worth it, not worth stressing or wasting time on it. I realize I am doing that by typing this post, but it needed to be done. People who are making money off of it - you're fine actually.
The message I am trying to get across is that Google's android software is not worth it, we all know it's bad, and Google seriously needs to get it right before everyone hops on the iBoat. There are actually multiple little things that I tried to get across in the post. That is all.
Cool story. Feel free to jump on the iOS wagon. I, for one, really like android.
I'm with android for the customization and freedom. I came from Windows Mobile where you could change anything you wanted and fell in love with flashing custom ROMS and even had a duel boot of WM6 and android 1.0 when I first came out (hated it back then, by the way.)
I bought an iPhone 3g when they came out and sold it by the next day. As you said, it was "flawless" as far as the operation of the OS, but when the OS imposes so much control over user input what do you expect? The iPhone tells you what you're allowed to do, it's not the user that defines what the phone can do.
After dropping my Tilt 2 flat on its face and tearing the ribbon for the screen, I hit the market for a new phone. Windows Mobile was still in the hundreds, but android was a cheaper alternative. I got a Samsung Moment and never looked back.
Maybe coming from Windows Mobile to android is why I don't have as many bug complaints. WM was mostly ALL bugs and glitches. That's not why I had the phone though - I had it for the features. Namely the ability to tether, which took android AND apple several releases to incorporate into their builds, but which was plug-n-play on every WM device I owned YEARS before. I also really enjoyed Windows Voice Command, better recognized as the Sync system in Ford vehicles. I could wear my bluetooth headset and make calls, open programs, listen to music and change songs all without having to touch the phone. Once again, it took apple and Google several editions to add useful voice commands to their systems.
I still miss remote desktop. I stopped having to store music and movies on my device because I could open a program and directly access every file on my home computer and stream anything to my phone screen.
So ultimately I'm with android for the freedom. The openness. The fact that they ALLOW outside developers to exist at all! It's the creativity found in the android community that has kept me, not the hope for a "fix all" update. Personally, the only problem I've ever had with my Android phones is the actual phone app itself. Delayed ringing and sometimes the inability to answer to even slide and answer the call due to screen freezing.
That's MY rant at 5 am lol
Sent from my Nexus S 4G using xda app-developers app
I'll have a Lamborghini Gallardo, Olivia Wilde and a cherry Coke, while we're at it (dreaming).
When you buy a new phone it should be completely yours not locked down by the manufacturer. If I want to brick I want to be able to do it.
If you really don't like it there a lot of rotten apple phones out there for you to buy.
anyway, I was on stock JB for a while, I haven't encountered all this **** your talking about. It could be faster, nicer, with more options but it is working quite well
Envoyé depuis mon Nexus S avec Tapatalk
Go get lost. Steve Job is waiting there to pay you for this iPhone advertisements in an android thread. You are required there not here. Lol....
Sent from my Nexus S
madd0g said:
I'll have a Lamborghini Gallardo, Olivia Wilde and a cherry Coke, while we're at it (dreaming).
Click to expand...
Click to collapse
Scratch that lambo make it an Aston Martin Vantage V12. Regarding the other two: Plenty of cherry coke around, but we're gonna have a problem with Olivia: I won't share, no crossing swords!
I love when people try to tell me how I should feel about the products I enjoy.
Logomotph said:
Cool story. Feel free to jump on the iOS wagon. I, for one, really like android.
Click to expand...
Click to collapse
I know right?
madd0g said:
I'll have a Lamborghini Gallardo, Olivia Wilde and a cherry Coke, while we're at it (dreaming).
Click to expand...
Click to collapse
Can I get that with no cholesterol burger and fries?
p.pavljasevic said:
When you buy a new phone it should be completely yours not locked down by the manufacturer. If I want to brick I want to be able to do it.
If you really don't like it there a lot of rotten apple phones out there for you to buy.
Click to expand...
Click to collapse
I've said this before. I hate when companies wanna slap their branding all over my 4 to 600 dollar smartphone and load it up with their crap I am never gonna use.
styckx said:
I love when people try to tell me how I should feel about the products I enjoy.
Click to expand...
Click to collapse
My best friend is a iPhone fanboy. I have to show him once a month why my Nexus S 4G is better then his iPhone 4s.
to each his own, i don't mind jb's quirkyness, it's also a matter of finding just the right rom/kernel combo... can't speak for stock JB.
aokp JB 4 + marmite 4.8.7 is doing quite nice, steady & haven't had weird reboots yet
I will admit that the Nexus S has a hard time with stock Jelly Bean. It pushes the NS basically to its limits in terms of hardware capability. That said, as a daily driver, it's still very, very usable. If you want to see Jelly Bean run like a f**king champ, run it on a Galaxy Nexus or Nexus 7. It's pretty amazing.
Okay I'm not favouring iOS or anything and no I'm not jumping on their wagon, and I am also not hating on Android's customization/community. I've had my Nexus S for almost 1.5 years now and I still believe it's not outdated (great camera, front-facing camera, good screen, good touch sensor)
I appreciate that Android lets its customers customize the phones more than Apple. But what about the 'majority' who don't root or install 3rd party keyboards, etc. and like to run stock? I for one am running stock and native since I believe it should give the best performance as it is made by the manufacturer. But I'm not getting that! There are the red flags going off.
Additionally, when I was referring to iOS, I mean to say mainly iPhone 4 and up. The iPhone 3 was quite bad (although still better than android at that point in time). But with iOS 5/6, sure it takes away user customization, but the majority does not anyway - they just use their phone for their intended purposes and yet experience difficulties? That's a no no. However, ONE thing I do enjoy is widgets over having iOS.
Plenty of people dont run stock as per your definition. Plenty of people use or at least tried different keyboards / launchers / messaging apps etc
Root is not required and installing those apps is no different then installing any other app like Pandora. They are also often editors choice and top selling / top free apps in the play store. People know about them and use them. You don't need a to be a hardcore user to know about and use them.
People actually do change up there apps all the time and on all platforms. Its like saying people with a iPhone shouldn't use instagram because the phone comes with a camera application out the box.
Bottom line is if the user has a option to try different apps they will. Especially if its easy for the average user to install like a normal app. Imagine for a second if winterboard was freely available in the app store and functioned the same way it does on a jail broken device. I'd bet within 24 hrs it would become the most popular app in the app store. Your argument just seems silly to me. People will and do change things are freely and easily changed
albundy2010 said:
Plenty of people dont run stock as per your definition. Plenty of people use or at least tried different keyboards / launchers / messaging apps etc
Root is not required and installing those apps is no different then installing any other app like Pandora. They are also often editors choice and top selling / top free apps in the play store. People know about them and use them. You don't need a to be a hardcore user to know about and use them.
People actually do change up there apps all the time and on all platforms. Its like saying people with a iPhone shouldn't use instagram because the phone comes with a camera application out the box.
Bottom line is if the user has a option to try different apps they will. Especially if its easy for the average user to install like a normal app. Imagine for a second if winterboard was freely available in the app store and functioned the same way it does on a jail broken device. I'd bet within 24 hrs it would become the most popular app in the app store. Your argument just seems silly to me. People will and do change things are freely and easily changed
Click to expand...
Click to collapse
Wonderfully said.
Another tiny bit to add on to my previous point.
The focal point of apples marketing strategy used to be " there is a app for that". Of course this is after they decided to even include a store. Who can forget the air traffic controller getting the weather from his iPhone?
But this doesn't seem to apply to things apple thinks its users shouldn't change.
What are you going to use your nexus to do as you write it has a hard time using jelly bean? - I my self have not got complications - I think I have used jelly bean nearly from when it was free - and I for my part - find it fast and free from lack - it play film - I read a lot news on it - it is very nice to read ebooks - see tv - you name it - ok - I do not use it for play - as all play for me are more or less the same - but ells I injoy jelly bean on my nexus s
Sent from my Nexus S using xda app-developers app
albundy2010 said:
Plenty of people dont run stock as per your definition. Plenty of people use or at least tried different keyboards / launchers / messaging apps etc
Root is not required and installing those apps is no different then installing any other app like Pandora. They are also often editors choice and top selling / top free apps in the play store. People know about them and use them. You don't need a to be a hardcore user to know about and use them.
People actually do change up there apps all the time and on all platforms. Its like saying people with a iPhone shouldn't use instagram because the phone comes with a camera application out the box.
Bottom line is if the user has a option to try different apps they will. Especially if its easy for the average user to install like a normal app. Imagine for a second if winterboard was freely available in the app store and functioned the same way it does on a jail broken device. I'd bet within 24 hrs it would become the most popular app in the app store. Your argument just seems silly to me. People will and do change things are freely and easily changed
Click to expand...
Click to collapse
I don't understand, you're going off on apps when I am not talking about customization. I am just talking about the performance of the phone and the bugs it has. Let me be specific - as I unlock my phone, i swipe through home screens = lag. I open my camera, it takes a while at times = lag. I scroll through a list, and it lags on me. Even though it is minuscule Google needs to clean it up, since I never see it on an iOS device which is a fair comparison as it is the leading competitor.
I am not talking about apps or anything, I think we and everyone has already established that it has more customization. I know most users have 'tried' some customizable app that is not available to iOS but that is no excuse for the actual performance bugs it has. I don't play games (like rarely maybe) on the phone and don't have a huge load of apps installed either. Things just aren't nifty..and it is taking them years to get it right but they'd rather focus on other feature additions which also work poorly.
You are the one who brought up that entire what about the majority of the people out there that don't run third party keyboards etc.
You brought it up. I said it was rubbish.
Android has always been laggy compared to iOS. Apple did a good job with that from the beginning.
The majority of your op is simply not worthy of responding to. Actually I re read it just now and I consider it all entirely flame bait/ trolling. You joined the forum 3 days prior to that as well. Not bothering with that type of silly debate/flaming.
Your 2nd post in the thread actually had something I felt was worth giving a legit response to.
It can be due to Google not paying enough attention to this device, however, I urge you to try new phones like the Nexus and this upcoming LG Nexus. For me, Jelly Bean have been smooth all the way through. Lag is inevitable on this device due to its old single core cpu.
We are atleast fortunate to retain nearly all the features from the latest Android version, Apple withheld features from old phones on purpose so you have to buy their newest and most expensive device.
So I download this X-Ray vulnerability scanner app (it's legit) and scan my device. To my surprise, even my Nightly is vulnerable to the mempodroid exploit. Should this concern me enough to file a CM bug report? By the way I use Franco kernel so if this is a legit exploit should I consider contacting him? See original G+ thread. https://plus.google.com/117694138703493912164/posts/AfNQ7cT9JYV
Sent from my Nexus 4 using Tapatalk 4 Beta
Mempodroid is a root exploit and considering that CM comes pre-rooted you shouldn't have anything to worry about
Sent from my NEXUS 4 using xda premium
Oh good. What a relief. So that means we have no known vulnerabilities. That's good. Take that Apple.
Sent from my Nexus 7 using Tapatalk 4 Beta
MikeRL100 said:
Oh good. What a relief. So that means we have no known vulnerabilities. That's good. Take that Apple.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
http://www.theepochtimes.com/n3/152836-android-master-key-security-flaw-affects-900m-devices/
If people are worried about security they should not be rooting their devices to begin with.
Sorry if I'm offending
zelendel said:
If people are worried about security they should not be rooting their devices to begin with.
Click to expand...
Click to collapse
Sorry for disagreeing with you, but I worry about common sense security. If this is a root exploit that is needed to ship with CM to allow one to use root, no biggie. I know root makes you vulnerable, but guess what? So does administrative access on Windows. If I worked for the governemnt or a large business I would have a different, possibly non-smart phone to do that task. I'm not stupid enough to go downloading cracked apps from pirated sites, but let me tell you all something. On my PC I had Opera 14 installed and used it during when one of Opera's employee's PCs got hacked and injected the Opera certificates with malware. I freaked. Prooves that a targeted attac could be successful, even with good protection. Luckily, my layer of security (MVPS hosts, Avast, and Malwarebytes Pro) kept it from even approaching the front door. And my Linux box even has the MVPS hosts file as well. Also, if this was an actual vulnerability to be concerned about, Steve Kondik would've patched it before the iCrap loving media could get new anti-Google propaganda. By the way, I am arguing with none of you, but I do need to make a point. I know since Android is based of Linux and not Windows NT, it is hella more secure. I would not root this if this phone had to be used under secure conditions. I'd either disable root while at work, or get a second phone. Yes I love root that much. But I don't get malware very often, havent' had an actual infection that wasn't blocked in many many years. Never even had Android malware. You know why? Hosts file+common sense. I never go to pirated sites, and never will. I love the XDA devs, community, and even some of the non-XDA Google Play devs enough not too. And when I say love, I mean I don't want to see their income sapped. Piracy is a no-no on XDA, but I'm sure it's OK to condemn it. And my talk on that ends now. :good: So onto the main topic, I have common sense, some privacy protections, and I don't just allow any app superuser access. I check reviews first and even have a malware scanner in Advanced Mobile Care. No on demand protection since its not necessary for me, and I never have gotten malware. I bet jailbroken iOS devices get more malware since most of the apps on them are cracked since Apple boots you out of iTunes for jailbreaking. Also, even though I'm rooted I like to know what each exploit means. No device or computer (even a hardened Linux server) is safe from the most skilled black hat. But since I'm not a target of interest, I have some malware prevention via the HOSTS file, Android is more secure than Windows, and I most importantly have common sense, I'll be fine. Maybe I'm too lax on security, but I guarantee you, I will adapt if some freak drive by download trojan comes to Android and by some crazy way gets malware through the Play Store with reputable apps. If a nasty was detected, or an app just looked different enough, it ain't gonna get no system access from me. So go ahead you iOS loving "Android is the next Windows XP" malware magnet pundits in the media, go ahead (that i if any Apple trolls stumble across this thread). I guarantee none of the streams of infected botnets will not add another to the collection. Like I said, not arguing with you but I disagree with you (at least initially) on how powerful my common sense is. I'm not saying you're doubting me, you're a cool guy and more than likely give a lot of assistance around here, but I may look like a noob troll cause I am a Junior member, but I was a long time lurker, and on AndroidForums I have been around a bit. I'm not some sort of super brain (at least not yet) and I do know rooting hampers security, but although I care about security, I just don't want my precious Nexus 4 and 7 to ever become virus magnets. I should have mentioned it, but I thought that vulnerability in CM was because it needed an exploit to have root by defaul (even though CM has disabled it recently). Also I will take some blame myself if I offended any of you. I am paranoid about a lot of things. But it's good to be paranoid to a certain extent. That would explain the lack of malware on all of my computers. But I should pay less attention to the social networks. Even G+. If this was on Facebook, mind you all, I wouldn't have game a damn about it. Facebook is full of trolls, fanboys, and noobs. That's why I rarely use that site and when I do, I pretty much block off all access to my profile from strangers. G+ encourages sharing with new people, while Facebook is like being with your old clique of buddies. That's why I use G+ so much now. That and I can help idiiot test things for developers. :laugh:
scream4cheese said:
http://www.theepochtimes.com/n3/152836-android-master-key-security-flaw-affects-900m-devices/
Click to expand...
Click to collapse
Yes you're definitely right we have a security issue. Not that Android itself is insecure (both my Nexus 4 and 7 were rushed to the latest Nightly to prevent them from joining a botnet) Good thing is custom ROMs create headaches for the bad guys cause they fragment Android (not in the iSheep style way of not getting updates) but in the way that they remove bloatware and some system apps, increase security in some areas, and in general all the code changes make it harder to create a universal botnet. I guarantee 95% of that botnet will be from OEM stock phones. We forget around here that most people are ignorant of common sense and security, if not downright stupid and don't care about security as long as they get their free cracked apps. We're the nerds here and most people are going to make it easy for these holes to be abused. They go to the most untrustworthy sites, install unstrustworthy apps, and are basically asking for it. Also the OEMs are pathetic for not all having a way to quickly patch Android. This type of stuff should sound an alarm to create a security update. I can see not giving an old phone a new version of Sense/touchwiz/Motoblur,etc. but denying security updates is ridiculous. The government should sue the offending OEMs if they want to be respected by the geeks a little more after the whole NSA mess. Because despite the fact that we aren't the ones here creating the botnet, what are we gonna do if thousands of clueless users install cracked apps that contain malware with the exploit, and form a botnet, that say DDOS attacks Google. Then Google Services would be disrupter. Also Google (who I am a big fan of) needs to stop being greedy in the one area of Android updates and force OEMs to include security patches and also backport and open source the security patch ASAP. I know CM is safe from that exploit already, I saw Steve Kondik's commit. But the OEMs are the problem. Google needs to push them past their comfort zone. You can have a car that is 10-20 years old and just because it's out of warranty doesn't mean that even if it takes a fool to make the engine explode in a deadly blast, that the manufacturer would just it there. I've seen Chevy recalls for example. One of them was a recall because something would catch fire if you were an idiot and poured gasoline or engine fluid or somehting on the engine. Of course the people doing this were stupid, but the same is true with technology. Why let the clueless and in the worst case those that just don't care create a botnet for us all to suffer from? Create an idiot patch and stop the situation from exploding. Please OEMs. Do something right for once.
MikeRL100 said:
Sorry for disagreeing with you, but I worry about common sense security. If this is a root exploit that is needed to ship with CM to allow one to use root, no biggie. I know root makes you vulnerable, but guess what? So does administrative access on Windows. If I worked for the governemnt or a large business I would have a different, possibly non-smart phone to do that task. I'm not stupid enough to go downloading cracked apps from pirated sites, but let me tell you all something. On my PC I had Opera 14 installed and used it during when one of Opera's employee's PCs got hacked and injected the Opera certificates with malware. I freaked. Prooves that a targeted attac could be successful, even with good protection. Luckily, my layer of security (MVPS hosts, Avast, and Malwarebytes Pro) kept it from even approaching the front door. And my Linux box even has the MVPS hosts file as well. Also, if this was an actual vulnerability to be concerned about, Steve Kondik would've patched it before the iCrap loving media could get new anti-Google propaganda. By the way, I am arguing with none of you, but I do need to make a point. I know since Android is based of Linux and not Windows NT, it is hella more secure. I would not root this if this phone had to be used under secure conditions. I'd either disable root while at work, or get a second phone. Yes I love root that much. But I don't get malware very often, havent' had an actual infection that wasn't blocked in many many years. Never even had Android malware. You know why? Hosts file+common sense. I never go to pirated sites, and never will. I love the XDA devs, community, and even some of the non-XDA Google Play devs enough not too. And when I say love, I mean I don't want to see their income sapped. Piracy is a no-no on XDA, but I'm sure it's OK to condemn it. And my talk on that ends now. :good: So onto the main topic, I have common sense, some privacy protections, and I don't just allow any app superuser access. I check reviews first and even have a malware scanner in Advanced Mobile Care. No on demand protection since its not necessary for me, and I never have gotten malware. I bet jailbroken iOS devices get more malware since most of the apps on them are cracked since Apple boots you out of iTunes for jailbreaking. Also, even though I'm rooted I like to know what each exploit means. No device or computer (even a hardened Linux server) is safe from the most skilled black hat. But since I'm not a target of interest, I have some malware prevention via the HOSTS file, Android is more secure than Windows, and I most importantly have common sense, I'll be fine. Maybe I'm too lax on security, but I guarantee you, I will adapt if some freak drive by download trojan comes to Android and by some crazy way gets malware through the Play Store with reputable apps. If a nasty was detected, or an app just looked different enough, it ain't gonna get no system access from me. So go ahead you iOS loving "Android is the next Windows XP" malware magnet pundits in the media, go ahead (that i if any Apple trolls stumble across this thread). I guarantee none of the streams of infected botnets will not add another to the collection. Like I said, not arguing with you but I disagree with you (at least initially) on how powerful my common sense is. I'm not saying you're doubting me, you're a cool guy and more than likely give a lot of assistance around here, but I may look like a noob troll cause I am a Junior member, but I was a long time lurker, and on AndroidForums I have been around a bit. I'm not some sort of super brain (at least not yet) and I do know rooting hampers security, but although I care about security, I just don't want my precious Nexus 4 and 7 to ever become virus magnets. I should have mentioned it, but I thought that vulnerability in CM was because it needed an exploit to have root by defaul (even though CM has disabled it recently). Also I will take some blame myself if I offended any of you. I am paranoid about a lot of things. But it's good to be paranoid to a certain extent. That would explain the lack of malware on all of my computers. But I should pay less attention to the social networks. Even G+. If this was on Facebook, mind you all, I wouldn't have game a damn about it. Facebook is full of trolls, fanboys, and noobs. That's why I rarely use that site and when I do, I pretty much block off all access to my profile from strangers. G+ encourages sharing with new people, while Facebook is like being with your old clique of buddies. That's why I use G+ so much now. That and I can help idiiot test things for developers. :laugh:
Yes you're definitely right we have a security issue. Not that Android itself is insecure (both my Nexus 4 and 7 were rushed to the latest Nightly to prevent them from joining a botnet) Good thing is custom ROMs create headaches for the bad guys cause they fragment Android (not in the iSheep style way of not getting updates) but in the way that they remove bloatware and some system apps, increase security in some areas, and in general all the code changes make it harder to create a universal botnet. I guarantee 95% of that botnet will be from OEM stock phones. We forget around here that most people are ignorant of common sense and security, if not downright stupid and don't care about security as long as they get their free cracked apps. We're the nerds here and most people are going to make it easy for these holes to be abused. They go to the most untrustworthy sites, install unstrustworthy apps, and are basically asking for it. Also the OEMs are pathetic for not all having a way to quickly patch Android. This type of stuff should sound an alarm to create a security update. I can see not giving an old phone a new version of Sense/touchwiz/Motoblur,etc. but denying security updates is ridiculous. The government should sue the offending OEMs if they want to be respected by the geeks a little more after the whole NSA mess. Because despite the fact that we aren't the ones here creating the botnet, what are we gonna do if thousands of clueless users install cracked apps that contain malware with the exploit, and form a botnet, that say DDOS attacks Google. Then Google Services would be disrupter. Also Google (who I am a big fan of) needs to stop being greedy in the one area of Android updates and force OEMs to include security patches and also backport and open source the security patch ASAP. I know CM is safe from that exploit already, I saw Steve Kondik's commit. But the OEMs are the problem. Google needs to push them past their comfort zone. You can have a car that is 10-20 years old and just because it's out of warranty doesn't mean that even if it takes a fool to make the engine explode in a deadly blast, that the manufacturer would just it there. I've seen Chevy recalls for example. One of them was a recall because something would catch fire if you were an idiot and poured gasoline or engine fluid or somehting on the engine. Of course the people doing this were stupid, but the same is true with technology. Why let the clueless and in the worst case those that just don't care create a botnet for us all to suffer from? Create an idiot patch and stop the situation from exploding. Please OEMs. Do something right for once.
Click to expand...
Click to collapse
Oh you have many valid points. My statement was more for the average user that really has no use for root. They root and flash cause they think it is cool.
The carriers and OEMs are trying to do something to stop it. The are locking bootloaders and making unrootable kernels (Samsung) To be honest I think this is a good idea for most users. They have no really need for those things and only end up with issues cause they have no idea what they are doing.
Cm Released a set of patches today to block some of the security issues.
See that is the issue with With OEM. Google cant force them to do anything. All the carrier has to do is take the AOSP code and add their stuff to it. No one can say what they have to add or not. This is why I only get nexus devices. I watched Euro devices get updated by the OEM while the US based devices never saw any updates at all. Including security updates that the OEM had issued. As long as the Carriers control what happens to the devices there is nothing that we can really do.
#Nexus4Lyfe I wish this was G+. I felt like a stupid hash tag would be appropriate.
Has anyone else seen this yet? It's a supposed secure OS for nexus devices. https://copperhead.co/android/downloads If anyone checks it out, let us know how it goes.
Wow I never seen this.:laugh:
Looks interesting, Im gonna check it further. Probably a AOSP based with some patches, fdroid, and some anti-gapps apps?
Most definitely curious as to how this runs....they want you to relock the bootloader though...????????????
Runs really nice. But there is no open source support for my android wear watch which I need.
No thank you. I would rather trust google and NSA, instead of some no name offshore company.
Sent from my Nexus 6P using XDA Labs
suhridkhan said:
No thank you. I would rather trust google and NSA, instead of some no name offshore company.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Toronto is off-shore?
Lol
Sent from my Nexus 6P using XDA-Developers mobile app
Locking the bootloader is good for your security.
Sent from a 128th Legion Stormtrooper 6P
toronto is offshore? do you think they live in igloos still aswell?
also this is just aosp with google signatures,
i tested for fun, boot animation is crap,
some lag going n settings,
no playstore access, no gapps at all from what i saw,
secure unsure, i dont know enough to rip apart the source and see if any holes from the company,
I was intrigued by Copperhead since reading about the Unaphone, another Google free operating system. Unlike Unaphone, whom's developers were providing it only for their proprietary hardware, when I saw CopperheadOS I knew I was going to try it for sure!
Previously running Resurrection, my phone already had an unlocked bootloader. Even if it hadn't, flashing Copperhead using the developer's instructions is very easy.
First impressions were good. The phone was noticeably more responsive, lacking google services normally running, and stable since the OS itself is based on stock which was considerably more stable than other roms I've tried. All the features you would expect from 6.0.1 are present and working. What is not preset however is the Google Play store or services! I didn't appreciate the implications of not having google services before actually trying to use a phone without them. Although it is possible to sideload gapps, one would rather negate the point of this ROM.
Poking around the settings the first thing I noticed were granular security settings with detailed descriptions. There is also a nice security versus performance slider for the layman. The idea of preventing exploits using the techniques in this rom is my main reason for using it.
After an evening of use, the vast majority of closed-source-paid apps I was able to replace with open-source alternatives. There are a few exceptions I am still trying to figure out, but overall, I think if you are willing to cut the google-cloud-services cord its worth a try. If you really must, most apk's for closed apps can be found and installed but these decisions should probably be weighed carefully.
I never realized my reliance on google and closed apps until I tried to use an OS that doesn't rely on them. Trying this rom is a good exercise in living off the google grid; or at the least driving the use of google services back into the browser.
At the end of the day this rom has its place for the privacy and security minded enthusiast, but for the average user, sticking to something with google services is probably more realistic.
longview41 said:
Toronto is off-shore?
Click to expand...
Click to collapse
pacman photog said:
toronto is offshore? do you think they live in igloos still aswell?
Click to expand...
Click to collapse
The 'offshore' part was simply a figure of speech.
What I mean is that if you don't trust google with your data, you have more reason not to trust an unknown company.
At least google is transparent about my data, and gives me control of how much I want to share with them. https://myactivity.google.com/myactivity
Installed it yesterday on a Nexus 5x and so far it runs great. It indeed seems really security orientated with no default root or GApps. Didn't try to activate xposed (which I hope will work) or related stuff yet but so far I intend to keep it.
Copperhead is trusted. They will be working with Guardian Project and Fdroid to build a complete system. Read this post for more info: https://copperhead.co/blog/2016/03/29/crowdfunding-partnership-announced
mg.degroot said:
Installed it yesterday on a Nexus 5x and so far it runs great. It indeed seems really security orientated with no default root or GApps. Didn't try to activate xposed (which I hope will work) or related stuff yet but so far I intend to keep it.
Click to expand...
Click to collapse
Please let us know if you're able to root, install xposed and still relock the bootloader.
mg.degroot said:
Installed it yesterday on a Nexus 5x and so far it runs great. It indeed seems really security orientated with no default root or GApps. Didn't try to activate xposed (which I hope will work) or related stuff yet but so far I intend to keep it.
Click to expand...
Click to collapse
Could you please share some screenshots... Would like to try the OS... But would like to see how it is ...
Also do you see the sRGB mode in developer options... Without it the colors on the Nexus 6P are inaccurate at best...
Stop asking about features or customisation options, this rom has none. Its about security, not features
kbBT4A5e said:
I was intrigued by Copperhead since reading about ...
After an evening of use, the vast majority of closed-source-paid apps I was able to replace with open-source alternatives. There are a few exceptions I am still trying to figure out, but overall, I think if you are willing to cut the google-cloud-services cord its worth a try. If you really must, most apk's for closed apps can be found and installed but these decisions should probably be weighed carefully.
I never realized my reliance on google and closed apps until I tried to use an OS that doesn't rely on them. Trying this rom is a good exercise in living off the google grid; or at the least driving the use of google services back into the browser.
At the end of the day this rom has its place for the privacy and security minded enthusiast, but for the average user, sticking to something with google services is probably more realistic.
Click to expand...
Click to collapse
Thanks for sharing your experience. So we have decide if security is really more important than our investment and dependency in the Google ecosystem. I depend on G too much. My email is like my passport or online identification. I dont sideload unknown or unverified apps, dont visit links i dont know about, etc. Yes, i can still be remotely exploited, but i am not a gov official or some sort of millionaire with top secret info on my phone, as most of us. You saved me couple of hours of my day
A little update since I've been running this for about 2 weeks. I sideloaded gapps and the phone has been running fine, but found out today while trying to install the latest OTA update from copperhead it fails to install due to inconsistencies detected in the system partition since I installed gapps; from a security standpoint this feature is great. Unfortunately I can't function without gapps. In order to get the latest security updates, which is probably more important than the security features cooked into copperhead, I must: reflash the device with the latest full image, install twrp, sideload gapps, restore the copperhead recovery, then reinstall all my apps.
This being the case to get OTA updates, unless you can really commit to opensource with no gapps its not really worth the hassle.
Using it for an extended period I did notice the device was a bit slow even on medium security settings. Originally I had it maxed right out, but it wasn't usable. On medium it was a small price to pay for security but its hard to quantify the value.
I think its time to return to an AOSP rom for me.
I'm running it currently runs great but I can't figure out how to fix the dreaded APN issues :\ Tried almost every fix on XDA haven't gotten Any dev help either :\ other than the lack of data its a great ROM. Apparently I'm not alone judging by the other post on XDA about this. Apparently this is a known issue with no real fix. Sucks since its the only reason I got this phone
Hi guys add me also 09945673600
Hi -
As the title says, I'm a total Android noob. I tried a droid phone many years ago, but found it irritating and fiddly, and went with an iPhone. I'm no fan of Apple, but it works pretty good, and as long as I was able to jailbreak the phone, I was OK with it. I think the future of JB for iphone may well be at the end of the road. If I ever have to replace or reload my iphone, then I lose my JB & I'm locked into Apple's walled garden. Unacceptable, as then I lose my ad-block and other items that make the device tolerable.
Realizing that my current iPhone is very likely my last, I snagged a Samsung Galaxy Tab A SM-T580 to see if I could learn to live with Android. One of my biggest issues with Android is Google. I despise Google and avoid using Google & their services to the greatest extent possible. (Yes, I know, flames and criticism headed my way for saying that ).
I don't want anyone's cloud, mail or other services.; I have my own servers for caldav, mail and file services. I want a stripped down, unbloated, and ad blocking android experience that is as free as possible from google or 3rd party services.
I understand there are other images (Cyanagen, AOKP, etc) but I don't know enough about any of this yet to know what I'd be getting into there.
But as a start, following a guide found here on XDA, I have rooted the tablet, and using Titanium, removed a good bit of the bloatware. I notice that since rooting the tablet, there is a 6 - 8 second delay after entering the pin code and hitting OK before the tablet unlocks. Not sure what that's all about.
There's a lot to learn and a lot of mis-information out there. It's hard to find a straight answer. Any tips or info appreciated as I try and figure out how to get as close as possible to my goal.
kalart said:
Hi -
As the title says, I'm a total Android noob. I tried a droid phone many years ago, but found it irritating and fiddly, and went with an iPhone. I'm no fan of Apple, but it works pretty good, and as long as I was able to jailbreak the phone, I was OK with it. I think the future of JB for iphone may well be at the end of the road. If I ever have to replace or reload my iphone, then I lose my JB & I'm locked into Apple's walled garden. Unacceptable, as then I lose my ad-block and other items that make the device tolerable.
Realizing that my current iPhone is very likely my last, I snagged a Samsung Galaxy Tab A SM-T580 to see if I could learn to live with Android. One of my biggest issues with Android is Google. I despise Google and avoid using Google & their services to the greatest extent possible. (Yes, I know, flames and criticism headed my way for saying that ).
I don't want anyone's cloud, mail or other services.; I have my own servers for caldav, mail and file services. I want a stripped down, unbloated, and ad blocking android experience that is as free as possible from google or 3rd party services.
I understand there are other images (Cyanagen, AOKP, etc) but I don't know enough about any of this yet to know what I'd be getting into there.
But as a start, following a guide found here on XDA, I have rooted the tablet, and using Titanium, removed a good bit of the bloatware. I notice that since rooting the tablet, there is a 6 - 8 second delay after entering the pin code and hitting OK before the tablet unlocks. Not sure what that's all about.
There's a lot to learn and a lot of mis-information out there. It's hard to find a straight answer. Any tips or info appreciated as I try and figure out how to get as close as possible to my goal.
Click to expand...
Click to collapse
My advice.
Ignore built.prop mods. I haven't seen any empirical evidence to prove it does what people say it does. Infact I've read more to say its bolony. However, I did find 3c toolbox improved my battery life on my Galaxy s5 with lineage os installed.
I managed to remove google from my android box. Use aptiode for an app store.
Download F droid,
Install newpipe YouTube client. Then ads are banished forever.
Install ad-away. Helps block ads on browser.
I use mi-explorer.
Don't use greenify or clean master they don't help.
With 3c toolbox and root you can remove a load of rubbish. My basic M8S runs really great with google removed.
I would recommend lineage OS, I have it running on 3 devices so far. I'm the nougat Aosp from this forum on my tab 10.1.