Related
When I got my Galaxy Nexus, I was more than content never to install a custom ROM on it for two reasons:
1. It had no carrier or OEM bloatware on it. It was as close to the Google Experience™ as one could get.
2. My previous phone was a Samsung Captivate, and no ROM, custom or otherwise, worked very well on it.
Well, that lasted about a month. There was nothing at all wrong with running stock on the GNex. The battery life was incredible. It was super fast. The reception is not so great, but there's nothing a custom ROM could really do about that anyway. It was certainly running well enough.
But I can't leave well enough alone.
I wanted themes. I wanted to make the phone my own in ways that were not possible in the buttoned-down, odexed world of stock ROMs. So, after prudently making a Nandroid backup, I held my breath, and dove headlong into the world of customization. I picked a really obscure ROM at first. I won't say which one it is because I don't want to discourage their work. But, I got more force closes in the first hour of running that ROM than I did in the first month of stock. Since my GNex is my daily driver, that wasn't working for me, but I'm not bitter. A lot of these ROMs are a learning process for the developer as well as the user. I left a bit of well-intentioned feedback in the thread, and moved on to another lesser-known ROM. This one worked a lot better for me. It was very stable, and much to my surprise, the upgrade was entirely free of problems.
I should digress to describe briefly my experience with flashing ROMs on my previous phone, the Samsung Captivate. I originally upgraded because Froyo was delayed, and I didn't like the bloware that AT&T felt the need to add to my device. I don't know if the leaks were bad, or the hardware just wasn't all that great, but each reinstall took several hours to get my device up to where it needed to be, and each firmware had HUGE problems, including regular freezes, and sometimes entire system apps would disappear for no reason. It led me to consider custom ROMs to be a necessary evil, but one that could be avoided on the GNex due to it being a Google phone.
It's clear from my experience that either the hardware or the ROM development has extremely matured over two years. The installation was quick and bug-free. Even the "bad" ROM I started on managed to pick up most of my existing apps, and only took about 30 minutes to install. The "good" ROM was unlike anything I've ever seen before. Not only was the upgrade practically instantaneous, but it even downloaded all my apps from the previous install and started up TiBu to install the system data. I was back up to speed in < 30 minutes, a far cry from the seemingly interminable hours that it took on the Captivate. I've only been running the current ROM for about a day, but if it continues with this stability, I will be a happy camper.
Why did I bother to write this?
1. Some people may be on the fence about whether they should stick to stock or go custom. Having a firsthand account of how truly painless the experience was may help them make a more informed decision.
2. Kraken Rum.
Just run CM9. Simple.
Sent from my Galaxy Nexus using XDA
Any ROM that takes more than ~five minutes to install I abort. I'm not sure how or why you waited half an hour to install one. Also every rom since gingerbread has auto installed apps unless it was specifically disabled.
But, good thoughts.
Sent from my Galaxy Nexus using xda premium
ROMs I tried on Captivate (with varying degrees of success):
ICSSGS
Mosaic
Pinnacle
Fasty
Sensation
Fusion
Cognition
Stock
Many of these I tried multiple versions.
Of those, none of them auto-installed apps. Most of them would be broken when I tried to restore with Tibu and I would have to do a complete SD card wipe to get an extra week of stability.
Point is, whatever awful experiences happened on other ROMs don't seem to apply to the GNex.
The reason roms just work on nexus phones is down to just 4 letters: AOSP.
Archpope said:
ROMs I tried on Captivate (with varying degrees of success):
ICSSGS
Mosaic
Pinnacle
Fasty
Sensation
Fusion
Cognition
Stock
Many of these I tried multiple versions.
Of those, none of them auto-installed apps. Most of them would be broken when I tried to restore with Tibu and I would have to do a complete SD card wipe to get an extra week of stability.
Point is, whatever awful experiences happened on other ROMs don't seem to apply to the GNex.
Click to expand...
Click to collapse
I tried some and loved them especially serendipity I loved that rom
Sent from my Galaxy Nexus using Tapatalk 2
Archpope said:
2. Kraken Rum.
Click to expand...
Click to collapse
THIS. YES.
Well this should be persuasive enough for others
Sent from my Galaxy Nexus using Tapatalk 2
Archpope said:
ROMs I tried on Captivate (with varying degrees of success):
ICSSGS
Mosaic
Pinnacle
Fasty
Sensation
Fusion
Cognition
Stock
Many of these I tried multiple versions.
Of those, none of them auto-installed apps. Most of them would be broken when I tried to restore with Tibu and I would have to do a complete SD card wipe to get an extra week of stability.
Point is, whatever awful experiences happened on other ROMs don't seem to apply to the GNex.
Click to expand...
Click to collapse
Like I said, it could be auto-disabled. My Thunderbolt autoinstalled apps when I first got it, and my Nexus tries to do the same.
Also, if you are restoring SYSTEM DATA through Titanium Backup, you're doing it all wrong.
ShredEight02 said:
THIS. YES.
Click to expand...
Click to collapse
I love the kraken. This thread is for people with great taste in phones and booze lol.
joshnichols189 said:
Any ROM that takes more than ~five minutes to install I abort. I'm not sure how or why you waited half an hour to install one. Also every rom since gingerbread has auto installed apps unless it was specifically disabled.
But, good thoughts.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have never installed a rom that took 5mminute to install, or flash atleast. However, it did took me 3 hours on my first HTC device to unlock bootloader, downgrade HBoot, S-off, root, cwm and all that. For the nexus it took me the time to type: fastboot oem unlock.
eksasol said:
I have never installed a rom that took 5mminute to install, or flash atleast. However, it did took me 3 hours on my first HTC device to unlock bootloader, downgrade HBoot, S-off, root, cwm and all that. For the nexus it took me the time to type: fastboot oem unlock.
Click to expand...
Click to collapse
Five minutes is a lot, but I didn't think it was too much. Usually if it isn't done in after a minute or two I pull the battery.
nodstuff said:
The reason roms just work on nexus phones is down to just 4 letters: AOSP.
Click to expand...
Click to collapse
+1 on AOSP
...but you know what, I have tried pretty much every ROM out there and to be honest I find myself always coming back to stock, stock but Rooted and with a custom kernel. At the moment I am running Trinity (literally my first day) and I'm very impressed. This is a stock Galaxy Nexus enhanced; better battery life, faster and with the Trinity's colour settings it even looks better.
There are just so many different ways to customise Android that it'll leave us all playing and experimenting forever.
Sent from my Galaxy Nexus using Tapatalk 2
I should clarify. The part of "installing a ROM" that took place within CWM never took more than 2 minutes. It was all the setup after that which took all the time. I learned very early on not to use TiBu to restore system apps. Even with that, it just never worked properly. Some apps would FC like crazy and have to be reinstalled and setup manually anyway. Some apps would just be gone with no explanation. So, I quit using it. That meant reinstalling each and every app and setting them up the way they were. Reinstalling whichever launcher I was using and putting all the icons and widgets back in place. This rarely took less than two hours, and never less than one. The reason I did this so much is that after two weeks, three at the most, the Captivate would start freezing randomly, for do discernible reason, no matter how little I had installed on it. Until I got to ICSSGS. That was the only stable ROM out of more than a dozen in two years. But by then, I was tired of the treadmill and sold it.
I'll see if the GNex starts freezing. Even if it does, I can restore my Nandroid back to stock and be happy.
I'm currently on 4.1 and it is great. However I was considering moving to 4.2 for the new features but judging by many threads with problems on 4.2 I'm starting to reconsider. Is it really as bad as it looks (the battery dying quickly, problems with updating from 4.1, other stuff), or is it worth to update my Gnex?
I'm getting my GNex today. Hope this thread gets answers
There are numerous threads on this subject. Instead of being lazy and having someone answer your question, why don't you actually read the threads? Hell, you've already answered some of your own questions.
Read, read, read and then just when you think you have the answer, read some more. Ultimately, it comes down to your own judgements and opinions.
Yes but what I can see are some individual cases of those things. Or are they? I just want to know if all those things are common in 4.2.
Basically, my question: does anyone who moved from 4.1 to 4.2 regret it in any way?
That question is also answered in all the "i'm going back to 4.1" threads..
As for whether this is a general thing, it is definitely more common with problems than other updates, but as several of us have had no problems at all, it cannot be a problem with 4.2 as such, so it would have to be either
1. a problem with the update process(i made a clean install)
2. a problem with certain hw/sw combinations(there have been reports of a certain error in the latest hw, which has coincided with the update itself)
I dont have any problems with 4.2. Question for u is are u rooted? Stock?
Sent from my Galaxy Nexus using xda premium
Compared my nexus with a friend's and experience is different.
Same exactly clean installation and my phone after 1 day starts lagging but my friend's is smooth as ever..
Maybe slight variation in hardware causes this difference...
Don't know what else to assume..
Sent from my Galaxy Nexus using xda app-developers app
I've tried CM10.1 which is 4.2 and after awhile the phone will stop responding and the screen will turn off. Only way to get it back on is to battery pull, reverted back to 4.1 for now.
I ran stock 4.2 from release to about a week ago, had a few problems at first but after a factory reset I was happy. Only issue was occasionally, maybe after a day, maybe a week, screen would go black right after waking and have to battery pull. But as is not an everyday occurrence I'll stay with 4.2.1 (rasbean) and wait for Google to fix.
Sent from my Galaxy Nexus using xda premium
I suggest get a decent Kernel as many issues are Kernel related. I'm running LeanKernel for the Verizon Galaxy Nexus and everything runs perfect. I have used LeanKernel since the Thunderbolt days and have tried Trinity and Franco. I always end up coming back to Lean Kernel. No SODs, weird lags, rebooting or other issues. The only think I tweaked was bump the GPU to 384, and over clock to 1350 MHz. Plus force the GPU for 2D in the developer settings which have always used since 4.1.
Hey guys. I borrowed my brother's old Galaxy Nexus while my HTC One is being repaired and I couldn't help noticing it lags. Immensely. I flashed SlimKat build 3 on it and before that I ran LiquidSmooth. I was under the impression that KitKat was supposed to be less resource hungry.
Is it because it's not "official" (from Google)? Would 4.3 run better, say in the form of CM10.2.1 stable?
Theshawty said:
Hey guys. I borrowed my brother's old Galaxy Nexus while my HTC One is being repaired and I couldn't help noticing it lags. Immensely. I flashed SlimKat build 3 on it and before that I ran LiquidSmooth. I was under the impression that KitKat was supposed to be less resource hungry.
Is it because it's not "official" (from Google)? Would 4.3 run better, say in the form of CM10.2.1 stable?
Click to expand...
Click to collapse
Try Deleting The (Google +) and if its Build in App try deleting it with Root Permission.
this Should Fix that Lag. It did For mine ^.^
The unfortunate reality is that most Galaxy Nexus units have sluggish internal storage, and any background processes that are trying to write to it while you interact with the phone can create lag in processing and the UI. It was such a relief to switch to the Nexus 5.
Mine is not lagging but not fast too.. But with the right rom and kernel and some tweaking its pretty fast for its age
Sent from my Galaxy Nexus using xda app-developers app
I flashed back to 4.3. CM10.2 stable and now it runs better but still lagging. Not as much, though.
lets try cm11 remix .....
Let me know how it is.running slimkat right now and I'm getting pretty much decent performance. We all have to remember this phone is older. I've been trying to justify getting the nexus 5. Will wait until the price comes down a little bit
Sent from the homie
Theshawty said:
Hey guys. I borrowed my brother's old Galaxy Nexus while my HTC One is being repaired and I couldn't help noticing it lags. Immensely. I flashed SlimKat build 3 on it and before that I ran LiquidSmooth. I was under the impression that KitKat was supposed to be less resource hungry.
Is it because it's not "official" (from Google)? Would 4.3 run better, say in the form of CM10.2.1 stable?
Click to expand...
Click to collapse
It's just the phone. My work phone is a gnex bone stock. And it lags horribly.
Mine is very fast, no lag at all, even after more than 1700 hours without rebooting :good:
Vanir 4.3.1 (final version)
.
This thread is active again. I thought I could get my One yesterday but Telecare messed up and sent me one that had even more tint than before, so I'm stuck with this until after May 9th because my carrier store closes for renovation between April 22nd and May 9th..
C'est la vie.
Since someone already opened a topic on this, I would like to chime in. This started happening too to me two days ago and it's driving me nuts. I must have done something somewhere but I just couldn't find any solutions.
As of two days ago, my Gnex started to lag since I flashed Fancy kernel r50. Serious f-ing lag. Nothing I do seems to help. I've dirty flashed my current rom (OmniMetal), I tried reflashing a previous version of the kernel like I've always done, I tried clean flashing everything again, I tried installing another rom (Paranoid Saberdroid) and whatever option available. The lag won't go away. This ain't your average lag. Even TWRP is lagging. Any suggestions?
SOLVED: It was a rewrite problem, what i did was i ran lagfix(fstrim) app and voila! Fast and speedy again.
Really happy with cm 11 remix, almost no lag.
Sent from my Galaxy Nexus using xda app-developers app
As mentioned before some of the nexus's suffer from the degrading EMMC performance. Refer to this thread to make sure which side you are on...
hope that helps :good:
I think cm remix is the most stabile/fast ROM now
Keep in mind you came from a HTC One to a Galaxy Nexus.. That's a big loss of processing power. Another thing is if he's had it OC'd a lot the processor may be in it's final days.
My Thunderbolt gave me the same issues while I waited to get my Gnex.
(I know there isnt any solution except to root and flash to a custom, just ranting. Thanks ahead to those who dont flame me)
Hey guys,
its been some time since my last post and boy is this one a headache. as many of you know the 5.0.1 update got rolled out to a major portion of note 4 devices recently. Me being one of them as of yesterday. Since I made the bad decision to click update I have had nothing but issues. Battery life, overall performance and graphics have taken heavy hits. My gear 2 only unlocked my phone and randomly dialed ppl maybe 2 times a day before now its 15. I mean i called my ex at 3am.....long story but hell! its gotten to be a huge headache. The chromecast refuses to connect or be setup by my note 4. It insists that theres some new wifi network issue that wasnt there the night before when I casted some youtube to the tv. My gear 2 has also had constant connection issues, not nearly the range it had before.
The most annoying issue which is also related to the excessive pocket dials is that everytime I pick up(and even when its just laying there not being touched) my phone and unlock it, it immediately takes me to the phone/contacts. No pressing anything, no swiping, just looking at the screen as i pick up the phone some how indicates that I was finished with whatever I was doing before and want to suddenly call someone up. So it doesnt matter what I do this thing is just being difficult. The new phone pop up is a nightmare I somehow hung up on 3 ppl today while just holding it against me ear, wasnt even resting on my shoulder.
now excuse me while i eat some cheese....
Factory reset and you'll find it smoother, quicker and less buggy.
The user file system is mixed lollipop and KitKat until you do that. Try that if wipe, root and custom is not your thing.
samep said:
Factory reset and you'll find it smoother, quicker and less buggy.
The user file system is mixed lollipop and KitKat until you do that. Try that if wipe, root and custom is not your thing.
Click to expand...
Click to collapse
Ya i figured as much. thanks for the reply
actually all you have to do is clear the cache and it stablizes.. But i do feel the Note 4 is has more hicups with the 5.0.1 update.
i just have not found a ROM yet that i want to flash. Still waiting for the Cyanogen official.
All lollipop roms have issuses with performance. My nexus 6 was really buggy to the point i sold it and picked up a lg g flex 2 running 5.0.1 and it was slower than my g3. So far after selling that device and getting the note 4 the note 4 with lolipop seem the most fluid out of the bunch. It's gonna take several updated for this lolipop os to run like kit kat. Maybe take years.
Maybe when 5.1 comes they fixed alot
All these little issues are starting to get to me. With the slow io performance, dodgy camera, random spouts of lag etc.
I have tried decrypting the storage to see if that helps, changing the io scheduler and using the optimised kernel clock optimisations in another thread, but to no avail.
Shall I give up on Google fixing these performance issues and replace with something else, like the LG G4. Anyone else considering giving up on the nexus 5x?
Yep. You should get a different phone.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Yep. You should get a different phone.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Gotta agree with above. If the 5X is not meeting your needs, you should switch to another device. No point dealing with a phone you are dissatisfied with.
Sent from my Nexus 5X using Tapatalk
Don't even contemplate it anymore. Get something that you're going to be happy with and enjoy using everyday.
I've got to say, my device has ran well and I've ran pretty much all the Roms available for it, if you're unhappy then yeah you should switch...but what device are you thinking of moving to? I like my device I'm just really surprised by the lack of community when it comes to Roms and stuff also, cases and Accessories etc. Don't get me wrong but the devs that are putting stuff out are doing excellent work and Ive enjoyed the major players in the ROM community but I feel like the 6p and other devices are getting waaayy much more love right now. Its kinda freaked me out on the lack of Roms and stuff but it is kinda still early I guess. I've though of switching but I just don't know what I would get yet.
I agree. The thing is, all the power phones with better performance that I have looked at have the larger screen. I am finding it difficult to find out if the lag is due to bad io performance due to a hardware limitation. If so, what other phones have the similar problem...
If my device had performance issues I would have returned it a while back.
Luckily my 5x is smooth for all tasks and a noticeable improvement over my N5 in almost every way.
If you want to try and fix the issue it's probably related to the apps you have running in the background as 24/7 services, as seen in Developer Options > Running Services. Some of them might not be playing nice with Android 6 or you may just have too many using your memory (64bit uses more RAM than 32bit). You can also try a factory reset without restoring from a previous device and test, or reboot the device into safe mode and compare.