Hi all,
Since two days my gnex is shutting itself down randomly. It happened first after my phone was charging and I deleted modern combat 3. Since then it happens app 2 times a day. I'm running stock JB deodexed with faux 123 kernel (the ultimate version). Could this happen because I unfroze google wallet? I must say that I was experiencing random freezes or reboots, but they happened more less often
Sent from my deodexed Jelly Beaned Galaxy Nexus
Bump
Sent from my deodexed Jelly Beaned Galaxy Nexus
Are you running a battery saving app a'la JuiceDefender or Easy Battery Saver? I had some similar issues when I used them under stock. I can't say that's the problem, just throwing something out there.
Nope, not using those at all. Maybe I could post a logcat here if I knew how to retrieve them ?
Sent from my deodexed Jelly Beaned Galaxy Nexus
tobitronics said:
Nope, not using those at all. Maybe I could post a logcat here if I knew how to retrieve them ?
Sent from my deodexed Jelly Beaned Galaxy Nexus
Click to expand...
Click to collapse
Hey u guys can uv right??
Sounds like an overclock, kernel or framework issues to me.
Issues like this are usually ROM/Kernel related.
Don't over clock on some kernels, some kernels don't mix well with certain Roms.
I've had reboots, freezes when over or underclocked.
Sent from my Galaxy Nexus using Tapatalk 2
tobitronics said:
Nope, not using those at all. Maybe I could post a logcat here if I knew how to retrieve them ?
Sent from my deodexed Jelly Beaned Galaxy Nexus
Click to expand...
Click to collapse
check out efrants android 101 on how to work with adb. i find it easier to work with than with an app.
Sent from my i9250
I would try to flash another kernel and see if it keeps happening. A few experimental versions of trinity was causing me random reboots like that but now with the new version it's running just fine. The best thing to do is go back to stock and make sure it isn't something wrong with the phones hardware.
Sent from my Galaxy Nexus using Tapatalk 2
Lightflow installed?
Yes, however the problem seems solved, i put the OC back to stock and the problems are gone
Sent from my deodexed Jelly Beaned Galaxy Nexus
I'm seeing a connection between Lightflow and my random shutdowns, as discussed here: http://forum.xda-developers.com/showthread.php?t=1643550. I have already re-installed Lightflow to see if the behavior returns, and will report back in a few days.
tobitronics said:
Yes, however the problem seems solved, i put the OC back to stock and the problems are gone
Sent from my deodexed Jelly Beaned Galaxy Nexus
Click to expand...
Click to collapse
Glad the problem is resolved. If you ever want to try overclocking with Trinity kernel again, you could try adjusting the voltage for the overclocked setting. That can sometimes stabilize things very well. And of course you probably already know that you should turn off smart reflex mpu when overclocking.
tobitronics said:
Hi all,
Since two days my gnex is shutting itself down randomly. It happened first after my phone was charging and I deleted modern combat 3. Since then it happens app 2 times a day. I'm running stock JB deodexed with faux 123 kernel (the ultimate version). Could this happen because I unfroze google wallet? I must say that I was experiencing random freezes or reboots, but they happened more less often
Sent from my deodexed Jelly Beaned Galaxy Nexus
Click to expand...
Click to collapse
Clear cache and dalvik cache
Sent from my Galaxy Nexus using xda app-developers app
Related
I had a moto atrix was great no lag nothing with cm7. I get the galaxy nexus for sprint and it seems every ROM I get has some kind of lag. I'm trying to get my device lag less like my atrix. I'm running jelly bean on lean kernel with tweaks the closet I've gotten
Sent from my Galaxy Nexus using xda app-developers app
JuanDaDon86 said:
I had a moto atrix was great no lag nothing with cm7. I get the galaxy nexus for sprint and it seems every ROM I get has some kind of lag. I'm trying to get my device lag less like my atrix. I'm running jelly bean on lean kernel with tweaks the closet I've gotten
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What do you mean by lag?
I'm running ACS 4.1 and its great!
Are you on toro toroplus or maguro?
Idk it lags up the launcher moving threw apps maybe its my ROM I'm running r u jellin but its the best I've found so far any mods u guys do?
Sent from my Galaxy Nexus using xda app-developers app
JuanDaDon86 said:
Idk it lags up the launcher moving threw apps maybe its my ROM I'm running r u jellin but its the best I've found so far any mods u guys do?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Maybe you got a bad ROM flash.
Do a nandroid backup and rewipe everything and reflash.
If it doesn't fix it then just restore to the backup.
Or try a different kernel. I'm using ACS are you jellin rc 2. With the IAP kernel.
Tue only mod I use is to get rid of the Google search bar.
Hi guys
I ask the question because everyone is quick to say how nice the AOSP or OTA ROMs are to start with in the threads posted, but if you fast forward to the latter pages of the thread you start to see what the issues are that have been caused by flashing these early ROMs.
I've gotten Soft Reboots on Stock/OTA odexed and deodexed 4.2 and 4.2.1 ROMs.
Just wondering if I'm alone and if anyone is actually waiting for this to calm down before flashing further?
I'm running JellyBro CM10.1 with the ZenSERIES v9 kernel. I've had no softboots. I've only been on this ROM 24 hours, but I previously typically had at least 1 softboot (graphics engine reset, usually) per 24 hours on CM10 (Android 4.1.2) with ZenSERIES v8.
Frankly, 4.2.1 has been much smoother and more problem-free than 4.1.2, though that might be due to it being my first clean flash in quite a while.
I am currently on stock 4.2.1 and before that on 4.2 stock. Have not experienced any soft reboots.
Wiggz said:
Hi guys
I ask the question because everyone is quick to say how nice the AOSP or OTA ROMs are to start with in the threads posted, but if you fast forward to the latter pages of the thread you start to see what the issues are that have been caused by flashing these early ROMs.
I've gotten Soft Reboots on Stock/OTA odexed and deodexed 4.2 and 4.2.1 ROMs.
Just wondering if I'm alone and if anyone is actually waiting for this to calm down before flashing further?
Click to expand...
Click to collapse
Wrong section - goes in Q&A! Reported!
apologies keyboard warrior....
no reboots here
Sent from my Galaxy Nexus using xda app-developers app
Since I upgraded to 4.2 I've had a few times when my phone is locked but the screen wont't turn on but the phone is still on because I can hear sms or mail notifications and even the alarm clock.
I have to take the battery out in order to use it again.
Sent from my Galaxy Nexus using xda app-developers app
The reason for my musing is I'm seriously considering going back to 4.1.x ROm that was flawless. Just didnt have the Camera or the quick settings :/
AOSPA2.99x (with Franco kernel) since it came out. Never had a single problem (no reboots, no SODs, no battery drains, bluetooth working, ...)
I just hope that I didn't jinx it now.
Paranoid Android 2.99 + Jame Bond 4.2 test kernel = Rock Solid.
Stock 4.2 no soft reboots at all
Sent from my Galaxy Nexus using xda app-developers app
elmerendeiro said:
Stock 4.2 no soft reboots at all
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Same, no problem with stock 4.2
Sent From Mobile...
OK to those saying they are running Stock or OTA with no issues - may I ask who's ROM? (if not completely stock)
No problems here. Galaxy Nexus and Nexus 7 stock roms
Sent from my Nexus 7 using xda premium
I'm running mWalt's mROM (basically a stock 4.2 AOSP ROM) for over a week, with no reboots or any other problems to speak of.
Sent from my Galaxy Nexus using Tapatalk 2
No problem at all on both 4.2 and 4.2.1
I flashed stock takju factory image with root and busybox and had an uptime of over 5 days with no issues.
I have just changed over to an alpha cm10.1 and cannot comment on uptime here yet.
Sent from my Galaxy Nexus using Tapatalk 2
None at all either here. 4.2.1 MMuzzy's build on my GNex, stock kernel.
4.2.1 stock ROM on stock kernel on my Nexus 7 hasn't given me a single reboot issue either.
My VZW GNex has been on every version of MMuzzy's 4.2 and 4.2.1 ROMs from the start (stock kernel) -- not one hiccup.
Plain stock, no reboots
Sent from my Galaxy Nexus using Tapatalk 2
I had miserable lag and battery life on 4.2.1. I tried every solution presented here. I flashed in every way imaginable. I did factory resets, wipes, etc, and nothing worked.
Then I downgraded to 4.1.1 and I had no more lag and got my battery life back.
I haven't even noticed a difference between the functionality of 4.2.1 and 4.1.1. Seriously! Try it!
OK.
For me battery life improved with 4.2.1 (as good with stock kernel as with Franco on 4.1.2) and I have had no issues.
Looks like I'm one of the few that didn't had any problem with 4.2.1, battery seems good as usual, no Bluetooth problem either, no lag.
I'm using everything stock and when I need to re-flash the room I use the 4.0.3 ROM.
Are you jelly? Sent from my jelly belly GNex
This is why I didn't upgrade until I looked at what people were saying about the update. Good thing I use a custom rom so I don't have to be nagged about it.
the problem on 4.2.1 isn´t solved^^
but same here xD i´m using 4.1.2.
got this combination:
-jellybro 4.1.2
-new camera+gallery ->4.2.1
-new clock ->4.2.1
-franco kernel 300
so i got the benefits of 4.2.1 and the performance of 4.1.2
new lockscreen of 4.2.1 is senseless in any way. performance is better on 4.1.2.
the only thing i like on 4.2.1 is the cam and the clock and i got them on 4.1.2
got great batterylife, usually 3,5h displaytime. uninstalled unnecessary things. made a few synchro-optimazations and i am very happy. disabled the transitionseffects as well, no need if apps are opened up nearly instantly
Useless thread; you didnt solve anything.
Sent from my i9250
montrealguy said:
I had miserable lag and battery life on 4.2.1. I tried every solution presented here. I flashed in every way imaginable. I did factory resets, wipes, etc, and nothing worked.
Then I downgraded to 4.1.1 and I had no more lag and got my battery life back.
I haven't even noticed a difference between the functionality of 4.2.1 and 4.1.1. Seriously! Try it!
Click to expand...
Click to collapse
LOL, please don't suggest this to anyone. There is no methodical approach to what you've done - or atleast you didn't specify what it was.
And, since there isn't one, this is a completely blind approach at fixing an issue.
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
L-ViZ said:
the problem on 4.2.1 isn´t solved^^
but same here xD i´m using 4.1.2.
got this combination:
-jellybro 4.1.2
-new camera+gallery ->4.2.1
-new clock ->4.2.1
-franco kernel 300
so i got the benefits of 4.2.1 and the performance of 4.1.2
new lockscreen of 4.2.1 is senseless in any way. performance is better on 4.1.2.
the only thing i like on 4.2.1 is the cam and the clock and i got them on 4.1.2
got great batterylife, usually 3,5h displaytime. uninstalled unnecessary things. made a few synchro-optimazations and i am very happy. disabled the transitionseffects as well, no need if apps are opened up nearly instantly
Click to expand...
Click to collapse
Downvoted.
4.2.1 will eventually fly no doubt, but like many others my nexus suffers from the SOD no matter what kernel I try.
I'm back on rascarlo 4.1.2 /w franco #300 and my battery must be at least 30% better off, but more importantly not one SOD/lag in sight.
Sent from my Galaxy Nexus using Tapatalk 2
chrisgtl said:
4.2.1 will eventually fly no doubt, but like many others my nexus suffers from the SOD no matter what kernel I try.
I'm back on rascarlo 4.1.2 /w franco #300 and my battery must be at least 30% better off, but more importantly not one SOD/lag in sight.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
All lies...
Flash 4.2.1 on your device, leave all stock apps on there and see what happens. Whatever is happening is probably caused by some 3rd-party application that isn't fully supported on 4.2.1.
akira02rex said:
All lies...
Flash 4.2.1 on your device, leave all stock apps on there and see what happens. Whatever is happening is probably caused by some 3rd-party application that isn't fully supported on 4.2.1.
Click to expand...
Click to collapse
Ooh look, we have a bigger numbers are always better brigade.
Obviously not all lies, the 4.2.1 SOD has nothing to do with app's - perhaps go read the development section?
Well done for looking like a complete fool though lol
Sent from my Galaxy Nexus using Tapatalk 2
chrisgtl said:
Ooh look, we have a bigger numbers are always better brigade.
Obviously not all lies, the 4.2.1 SOD has nothing to do with app's - perhaps go read the development section?
Well done for looking like a complete fool though lol
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not trying to be crappy or anything but how do you explain people not having SOD on 4.2.1 like myself?
I guess it's the same principle as a cpu, some overclock well, some overclock slightly, some don't overclock stable at all.
All our Nexus are different.
Sent from my Galaxy Nexus using Tapatalk 2
chrisgtl said:
I guess it's the same principle as a cpu, some overclock well, some overclock slightly, some don't overclock stable at all.
All our Nexus are different.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
All our nexus are different down to a molecular level. If Samsung quality control was letting loose devices that didn't all run the software as intended then I think we'd have much bigger issues. NO, this is NOT the same principle "as cpu"...
I do not have SOD issues at all. You can't justify you're statement one bit because you have done ZERO testing to prove otherwise. Just because you read about it in the development section doesn't mean it's true. :victory:
akira02rex said:
All our nexus are different down to a molecular level. If Samsung quality control was letting loose devices that didn't all run the software as intended then I think we'd have much bigger issues. NO, this is NOT the same principle "as cpu"...
I do not have SOD issues at all. You can't justify you're statement one bit because you have done ZERO testing to prove otherwise. Just because you read about it in the development section doesn't mean it's true. :victory:
Click to expand...
Click to collapse
Yeah ok. Me and the other multiple users are obviously doing something wrong, maybe you can write us and the dev's a guide to having a SOD free experience?
Until the guide turns up I will wait for the next bug fix release as Google have admitted there is a SOD problem across the board when using 4.2.1 :victory:
Sent from my Galaxy Nexus using Tapatalk 2
chrisgtl said:
Yeah ok. Me and the other multiple users are obviously doing something wrong, maybe you can write us and the dev's a guide to having a SOD free experience?
Until the guide turns up I will wait for the next bug fix release as Google have admitted there is a SOD problem across the board when using 4.2.1 :victory:
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where is the report that google admitted it?
I just suggested to you on the 1st page that you can try... Flash 4.2.1, don't install any 3rd-party applications for several days. If you're SoD-free, then try installing your apps one by one to narrow it down.
You also failed to provide any logcats.
My uptime is nearly 1 week now.. SoD-free! I must have a magical device or the molecular bonding at the factory was "just right" that day when they produced the PCB lol.
erm...i dont have SOD btw...100% stock..
Sent from my Galaxy Nexus using xda app-developers app
The only SoD i had was when used google maps for navigation. Had to pull the battery. And actually that is the only one i have heard off.
Except of that i have been SoD free with atleast 5 different kernels on stock 4.2.1 with about 100 apps.
The only reason for the kernels change was to find the best for battery.
Still no luck
Sent from my Galaxy Nexus using xda premium
Hello people,
I have my GNexus about a year now and I never experienced such bad multi tasking and overall lag. I run AOKP with Franco kernel. I did a clean install a few days ago, normally I just dirty flash. It seemed to be solved when I did a clean install but it's back now. I have to turn my nexus on and off every day for a couple times because it completely hangs. Could you please help me? Is this rom and or kernel related or am I doing something wrong? Any help is welcome. Thanks in advance.
Verstuurd van mijn Galaxy Nexus
LarsAussems said:
Hello people,
I have my GNexus about a year now and I never experienced such bad multi tasking and overall lag. I run AOKP with Franco kernel. I did a clean install a few days ago, normally I just dirty flash. It seemed to be solved when I did a clean install but it's back now. I have to turn my nexus on and off every day for a couple times because it completely hangs. Could you please help me? Is this rom and or kernel related or am I doing something wrong? Any help is welcome. Thanks in advance.
Verstuurd van mijn Galaxy Nexus
Click to expand...
Click to collapse
I would say kernel related..try AK kernel. the best kernel so far for our gnex
Why franco? Doesn't the newest aokp use lean kernel?
Alternate Rom and kernel combo may help.
LarsAussems said:
Hello people,
I have my GNexus about a year now and I never experienced such bad multi tasking and overall lag. I run AOKP with Franco kernel. I did a clean install a few days ago, normally I just dirty flash. It seemed to be solved when I did a clean install but it's back now. I have to turn my nexus on and off every day for a couple times because it completely hangs. Could you please help me? Is this rom and or kernel related or am I doing something wrong? Any help is welcome. Thanks in advance.
Verstuurd van mijn Galaxy Nexus
Click to expand...
Click to collapse
I would try the new 4.2.2 Carbon Rom. I am running the newest AK kernel (you may have to flash GPU binaries for any of the true 4.2.2 kernels). But I tried the bundled kernel and Morfic Kernels (4.2.1) before I flashed the binaries and in all instances THIS ROM WAS EXCELLENT!
No noticeable lag, recents screen worked great, and battery was a bit better than any of the 4.2.1 Roms I tried (Purity, Evolution, LS and Carbon included).
Give it a shot you wont regret it. I clean flashed Carbon 1.0 two weeks ago and then dirty flashed 1.1 Friday. If you're having lag issues I would do at least one full wipe...
I'm having the same problem on carbon and pa3. I can't tell if it is an app issue or rom/kernel related. After 12-24 hours, the lag gets terrible!
Sent from my Galaxy Nexus using Tapatalk 2
devarshi said:
I'm having the same problem on carbon and pa3. I can't tell if it is an app issue or rom/kernel related. After 12-24 hours, the lag gets terrible!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Which kernel are you using? I usually reboot every day, so not sure if this would help...
clearyt1 said:
Which kernel are you using? I usually reboot every day, so not sure if this would help...
Click to expand...
Click to collapse
I've used the stock one, Franco, lean, and ak dummy. They all have the same problem. I feel like I shouldn't have to restart every day, should I?
Sent from my Transformer TF101 using Tapatalk HD
devarshi said:
I've used the stock one, Franco, lean, and ak dummy. They all have the same problem. I feel like I shouldn't have to restart every day, should I?
Click to expand...
Click to collapse
try greenify to prevent unwanted apps running in the background. it really helps when it comes to multitasking and battery life: https://play.google.com/store/apps/...biflipde&utm_medium=website&utm_campaign=blog
what kernels do is mostly placebo i think. They are only good for added functionality like OTG or screen calibration, not for performance.
i had issues like that when i first flashed a 4.2 rom, tried a few and all were terrible and had reboots. finnally had the idea to wipe sd storage along with everything else and all 4.2 roms i have used since have been like butter. i always flash ak kernel.
madphone said:
try greenify to prevent unwanted apps running in the background. it really helps when it comes to multitasking and battery life: https://play.google.com/store/apps/...biflipde&utm_medium=website&utm_campaign=blog
what kernels do is mostly placebo i think. They are only good for added functionality like OTG or screen calibration, not for performance.
Click to expand...
Click to collapse
I just found greenify the other day. It seems to be helping, but I had a SOD this morning.
Sent from my Transformer TF101 using Tapatalk HD
---------- Post added at 01:50 PM ---------- Previous post was at 01:49 PM ----------
Deejayadhd said:
i had issues like that when i first flashed a 4.2 rom, tried a few and all were terrible and had reboots. finnally had the idea to wipe sd storage along with everything else and all 4.2 roms i have used since have been like butter. i always flash ak kernel.
Click to expand...
Click to collapse
Why would sd storage make a difference? I'd hate to wipe it, but I'll try if I have to.
Sent from my Transformer TF101 using Tapatalk HD
What is the CPU temperature when you notice the most lag? The nexus has thermal throttling to save our phones from melting in our hands. It could be the culprit... Or at least a part of it.
Sent from my Galaxy Nexus using Tapatalk 2
so finally some other people get this problem... having this issie for quite some time now as soon as i use something else than pure stock.
after a reboot it runs really smooth but the cpu usage for everything is always extremly high on custom roms/kernels and locks up the device if some io operations happen.
on pure stock it never locked up.
since i have no knowledge about finding the culprint i can only hope that some dev will get that issue and travk it down.
it sucks to run stock....
Sent from my Galaxy Nexus using xda premium
mmcqd appears pretty high on cpu list when it gets to the lockup... anyone has more infos on that one?
Sent from my Galaxy Nexus using xda premium
Thanks for your answers, it could maybe be related to aokp itself. Aokp build 3 and a few nightly builds have a memory leak issue and bad ram behavior.
Verstuurd van mijn Galaxy Nexus
Ever since I changed from 4.1.1 yakyjxw to 4.2.2 Takju ive been having random lag which requires me to reboot to fix. So annoying..I Just want to have stock 4.2.2 and everything to run smooth like 4.1.1!!
LarsAussems said:
Thanks for your answers, it could maybe be related to aokp itself. Aokp build 3 and a few nightly builds have a memory leak issue and bad ram behavior.
Verstuurd van mijn Galaxy Nexus
Click to expand...
Click to collapse
im on sourcery and also have the problem, was on cna and also had the problem and on aokp as well. actually it was the reason i left aokp but every rom is the same.
the only rom i never had it was pure stock. and as soon as i used a custom kernel the problem returned.
Sent from my Galaxy Nexus using xda premium
and back to stock.... couldnt stand the bad performance i get from all the custom roms i tried:banghead:
i would like to get to the root of this lag problem because i hate stock lock but this lag is even worse than not having all the freedom:what:
Sent from my Galaxy Nexus using xda premium
I have no idea why but when 4.2.2-based ROMs came out, my phone started to run like garbage. Slowdowns, lag, memory leaks, you name it, it happened. And it seemed to have started with 4.2.2. I don't ever remember this being a problem with 4.1.2-based ROMs.
So I ask... has anyone else experienced these issues? Does your phone run like garbage on 4.2.2-based ROMs?
I've been thinking of going back to a 4.1.2-based ROM just to try and get back some of the speed that my phone used to have. There are times I want to throw this thing against the wall because lately trying to get it to do anything without seriously bad lag is like trying to pull teeth.
You people overreact to everything. If its so bad, and you knew it was going to be bad, then why in the world did y'all upgrade to 4.2.2?
Try UDKs ROM, works fine for me
I'm thinking that 4.2.2 may be too heavy for the hardware of the Galaxy Nexus. 4.1.2 never was this slow and laggy on this phone.
Sent from my Galaxy Nexus using Tapatalk 2
trparky said:
I'm thinking that 4.2.2 may be too heavy for the hardware of the Galaxy Nexus. 4.1.2 never was this slow and laggy on this phone.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
considering my phone runs just fine 4.2.2 on stock rom, its prolly the rom you're running.
I think 4.2.2 runs great. Compare it to the original 4.0 ics firmware it blows it out of the water.
Sent from my Galaxy Nexus using Tapatalk 2
akira02rex said:
I think 4.2.2 runs great. Compare it to the original 4.0 ics firmware it blows it out of the water.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Does it not even lag after running it for a few days without reboot? That is the issue many people are seeing and 4.2.2 is smoother than ICS for the most part except the recents may sometimes lag worse on 4.2.2. The worse part of ICS was the unlock lag with auto brightness on.
Sent from my Galaxy Nexus using Tapatalk 2
4.2.2 is running super smooth for me. I dont know what all these people having issues is all about. It all depends on what ROM you use, and also could be the recovery you use. If your using an old recovery, it may not be wiping stuff right before flashing. A lot of factors go into a phone running crappy. Dont blame it all on 4.2.2.
Zepius said:
considering my phone runs just fine 4.2.2 on stock rom, its prolly the rom you're running.
Click to expand...
Click to collapse
This issue only happens on custom roms because its an issue with stock though maybe less noticeable there.
But as far as the OPs comments, if you're annoyed by 4.2.2 so much then switch back to 4.1.2 if you like it better.
Sent from my Galaxy Nexus using Tapatalk 2
I got the OTA yesterday for my VZW GNex and it's running great. So far, it's a better experience than 4.1 for me. Battery life seems the same (in a good way) and the UI is acting smoother than before.
jsgraphicart said:
4.2.2 is running super smooth for me. I dont know what all these people having issues is all about. It all depends on what ROM you use, and also could be the recovery you use.
Click to expand...
Click to collapse
Not really. Try not to reboot your 4.2.2-based rom for 2-3 days and you'll see the real smoothness (Sometimes it take couple of hours sometimes couple of days to reproduce the issue). I've tested 6 roms so far including non-rooted, slimmed stock - Low fps scrolling issue appears on every single one, clean install and always updated twrp recovery.
I think android 4.2.2 is an interesting project and it works not that bad. However there are some annoying bugs there. I don't use WIFi tethering or BT and I know how to deal with scrolling lag so it doesn't bother me that much. I can patiently wait for fix but problems exist and full wipe will not solve them.
my only issue is the battery drain lol thats all
I've got a epic 4g touch and I'm running cm10.1 wild for the night 4.2.2 and it works perfectly! Way faster than before.
Sent from my SPH-D710 using xda premium
I use WiFi tethering and Bluetooth on Rasbean/Trinity 4.2.2 and don't have any issues even after 2-3 days. Only issue I had initially was major lag in recents after a couple days. Rebooted and haven't had that problem since, even after several days uptime.
Sent from my Galaxy Nexus using xda premium
There is already a thread about the lag problem on roms based on 4.2.2 update - http://forum.xda-developers.com/showthread.php?t=2178962 and I confirm the lag.after 2-3 days ui starts to lag.everything gets better if you flash ak kernel diamond ed plus download clean master app by ksmobile from play store and you open it/go to history and clean cache once a day.The second thing that i found is that if you change the wallpaper when the lag start it goes away.hope this helps.good luck! Also the problem was reported to google
Sent from my Shining Nexus using AK DIAMOND ED.
4.0 < 4.2 < 4.2.1 < 4.1 < 4.2.2 < 4.1.2.
4.1.2 has been the smoothest version of stock in all the time I've been using Android. If 4.2.2 seems that bad, try running Lagfix once.
I've been on cm 10.1 nightlies (4.2.2) for awhile now and no lags/slowdowns whatsoever. Aside from the SOD when I first tried it (fixed now), it has been just as smooth if not smoother than 4.1.2
Sv: Anyone else's phone run like garbage on 4.2.2?
biscuitownz said:
I've been on cm 10.1 nightlies (4.2.2) for awhile now and no lags/slowdowns whatsoever. Aside from the SOD when I first tried it (fixed now), it has been just as smooth if not smoother than 4.1.2
Click to expand...
Click to collapse
Cm10.1 is not bad indeed (I am running it now and I'm pretty much enjoying it) but 4.1.2 based roms like cna 3.8.0 or cm10 are by far smoother. If you want to see the difference in smoothness go to application drawer (widget tab) and swipe left or right. On every 4.2.2 based rom swiping there is more or less but still kinda choppy.... On two 4.1.2 roms I mentioned above it's almost perfect. Small thing.
Sent from my Galaxy Nexus using xda premium
in my case it was franco kernel that caused the super bad performance.
the problem was coming from write performance which caused cpu overloading and locking down the device. this got worse after some time without reboot ~2days.
i did a clean install of sourcery rom with cmw (twrp seems to leave some stuff behind which will cause the lag again?) and so far my device is up for some time without any slowdowns.
maybe you once installed a kernel and use twrp which never got you a clean rom again? hope that helps some of you troubled ones.
Sent from my Galaxy Nexus using xda premium
I'm running lean kernel and the latest AOKP.
Sent from my Galaxy Nexus using Tapatalk 2