Stock my Gnex was a rocket, but after I started ROMing it is a laggy MESS. I do a clean wipe on each ROM install, but even before I load up any apps it stutters like crazy. The nav buttons can take seconds to respond, swiping through home screens jerks really bad.
Currently I am running the latest CM10 nightly JB rom, but it acts this way on any ROM I have tried. It seems to be a file system issue...the lag feels like the lag you get when you update a lot of market apps all at the same time...except all the time. Opening Google now can take up to 30 seconds on a clean install.
Any ideas on what may be going on?
Grims said:
Stock my Gnex was a rocket, but after I started ROMing it is a laggy MESS. I do a clean wipe on each ROM install, but even before I load up any apps it stutters like crazy. The nav buttons can take seconds to respond, swiping through home screens jerks really bad.
Currently I am running the latest CM10 nightly JB rom, but it acts this way on any ROM I have tried. It seems to be a file system issue...the lag feels like the lag you get when you update a lot of market apps all at the same time...except all the time. Opening Google now can take up to 30 seconds on a clean install.
Any ideas on what may be going on?
Click to expand...
Click to collapse
Suggestion-1: Flash stock once again and check whether the same happens. If the same happens again you may contact for phone replacement.
Suggestion-2: Try Wiping cache and Dalvik cache in CWM and reboot. Many times this has helped my phone to work fast.
Suggestion-3: There are many other ROMs around. Try them out.
I am not an expert to suggest you. But hope above works. Hope any more suggestions come up for you.
I have tried every popular ROM out, and wipe data and all cache on every install. They all act exactly the same. I really think there is some kind of bandwidth issue on the system partition. Maybe the flash storage has degraded? I will try flashing it back to stock to see if that would makes aay kind of difference.
I had been planning to RMA it anyway because of some major screen burn in issues...but was trying not to because I bought it through Letstalk, so I need to deal directly with Samsung for a replacement...which means being without a phone for a week or two.
I believe prior to flashing you should do data wipe cache and wipe System also :/ don't know if you've tried that it's under mounts and storage in CWM =)
I just setup a Samsung RMA for the screen issue. Hopefully they simply give me a refurb instead of repairing it.
logcat, df, dmesg and in this case, maybe a 0xbench math/vm test or it didnt happen.
not sure how a custom rom would be slower than stock.
i dont think its hw issue, or stock would suffer from the issue.
sent from my i9250
bk201doesntexist said:
logcat, df, dmesg and in this case, maybe a 0xbench math/vm test or it didnt happen.
not sure how a custom rom would be slower than stock.
i dont think its hw issue, or stock would suffer from the issue.
sent from my i9250
Click to expand...
Click to collapse
My apologies, I wasn't clear. I meant that the device worked great while it was stock, but now it runs like crap. Custom ROMs may or may not have anything to do with that which is why I mentioned it. I will say that the stock-ish JB leaks ran flawlessly, while the ICS custom ROMs I was running before ran like crap. After I moved off the JB leaks to custom JB ROMs it started to run like crap again.
Grims said:
My apologies, I wasn't clear. I meant that the device worked great while it was stock, but now it runs like crap. Custom ROMs may or may not have anything to do with that which is why I mentioned it. I will say that the stock-ish JB leaks ran flawlessly, while the ICS custom ROMs I was running before ran like crap. After I moved off the JB leaks to custom JB ROMs it started to run like crap again.
Click to expand...
Click to collapse
I thought I'd update this in case anyone else has ever had a similar issue. As I was preparing the device to be sent back to Samsung for a screen defect, I flashed the stock 4.1.1 factory image, and locked the bootloader. It feels like a completely new device..flying faster than I have ever seen it go.
I do not know why this resolved my issues and a wipe data/clear cache never did. Maybe encrypting the bootloader did something to the file system a normal wipe data doesn't? But then again the JB leak seemed to run well too if memory serves..so I just don't know.
Now that it is running properly for the first time in months...I really cannot stand sending it back and being without it while waiting for the repair.
Cm10 issue same happens to me
Enviado desde mi Galaxy Nexus usando Tapatalk 2
coldrazor said:
Cm10 issue same happens to me
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Click to expand...
Click to collapse
It did it on ICS ROMS too, but now that i think about it every ROM I have tried was based off CM9 or 10. Either way it's on the way back to Samsung now (for screen problems) so hopefully the next one doesn't have this odd issue.
Related
I have a Gnex rooted and unlocked - DroidModderX - I'm currently running Android Revolution HD very simple mod, barely has anything changed. This mod is 4.0.2. I have tried installing gummy, AOSP, a bunch of other ones. it always says error installing it. Anybody have any advice. Any way to get my Rogers Gnex to 4.0.3?
Thank you
does the error say something like a word i think its like outset or something (100% sure this is not the word) then alot of numbers after? that happens with mine too, but the rom installs fine.
Do you have the latest Clockwork Recovery Mod installed?
Also are you doing a full wipe before you attempt to flash the ROM?
doublea500 said:
does the error say something like a word i think its like outset or something
Click to expand...
Click to collapse
I have seen it say "offset" when I was using the Codename Android ROM.
I did not wipe my cache and data, I was scared that if I did that and it didn't work... I would have to start over again. Download all my programs. configure
Sometimes it doesn't download any of my programs. I restarted it and installed my old OS three times to get it to download my contacts.
I will see the exact thing it says to me soon. thanks guys
You *must* do a full wipe before going to a 4.0.3 ROM. Since your /system is still there, that is what is causing the issue.
However, use the Backup feature in CWM and you can restore it if anything goes bad.
The wipe will knock out your /system, /cache, and /dalvik but will not touch anything on your SD card which holds you photos, etc.
Wish me luck...
I already did a backup - FULL - in Galaxy Nexus Toolkit.
I'm thinking of going with AOKP M3. Let me know if you have any other suggestions.
I hope that is enough to get my phone back to the way it was...
I would like to change the Kernel too. Do you recommend any? I was thinking about franco kernel.
Thanks guys
Good luck!
I have tried three ROMs now and I greatly prefer AOKP the most. Currently I am on AOKP M3 using Faux's kernel but I was running AOKP M3 with Leankernel 1.9.0 with great results.
My battery drain seems a *little* bit more on Faux's but I have only been running it for one day.
Every kernel I try, the battery life improves over a couple days or more so I am going to let it settle.
I tried doing the change. I wiped everything that you could choose and it still gave me the same error. Didn't do it. I have no idea what the problem is. I have no idea how to get my phone to 4.0.3. F***
How about actually mentioning the error you're seeing as opposed to just winging?
It will work so it has to be something you're doing that's wrong
I'm just going to throw this out there for anyone who may know the answer, after searching for the last 3 days, I'm not finding anyone else having the same problem, so I'm thinking it may be something I did. Here's the issue.
I'm a confirmed flash-a-holic, and flash new roms or backups probably 2-3 times per week. I haven't tried any of the JB roms until recently, but dove in just before Nit's Viper Rom became available for ICS. I had installed the JB "global" rom, and had it working(ish), and then changed to the viper mod, then installed Aeroevan's "unofficial JB" when the 10/25 update on Goo.im came available. The install went smoothly and it worked great for about a day, then tanked big time when I tried to change the launcher from Trebuchet to Nova (I can't even guess why THAT had anything to do with it). It started lagging big time and then boot looping. Now, upon trying to wipe everything (factory reset/cache/dalvik/all partitions but sd), I get nothing but boot loops and NONE of the JB roms will install. From my reading, I know others get boot loops, but after a sequence, finally get into setup. Mine will too after 5-6 boot loops minimum, but the screen freezes on the initial setup screen and it's completely unusable (touch screen unresponsive). I don't get why that is when I HAD it installed the other day and it was very responsive (using Aeroevan's JB mod). I WAS using the 4EXT recovery when I started doing all of this, then switched recoveries to the most recent TWRP, and it allowed me to install Aeroevan's JB mod, and even start the setup, but very soon started lagging and then the boot loops again. At this point, I'm sortof at a loss, and the only thing I can think of is that maybe I should NOT have been wiping the sd partitions and SHOULD have only been wiping cache/dalvik/factory reset. At the moment, anyway all ICS mods are flashing/running just fine (currently on Nit's Vipermod and really liking it btw), but if anyone knows where I went astray, I'd appreciate any pointers. Thanks all, this is by far the best forum I have been a part of!
http://forum.xda-developers.com/showthread.php?t=1805773&page=117
Oh boy..... Be sure and post back if you find a solution, glad I'm not the only one! I thought I did this to myself... which I guess I sortof did if you get technical.
Sent from my Dinc2 using Tapatalk
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
auberry05 said:
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
Click to expand...
Click to collapse
Which radio did you flash?
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
bwpoersch said:
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
Click to expand...
Click to collapse
On follow-up, I read mixed opinions about the wisdom of using TiBu on restores, assuming I'm able to ever recover this my thinking is that one could use TiBu to restore apps ONLY and NO data and that would/should not cause a problem (assuming you're restoring a backup from within your installed ROM's file structure .i.e., JB/ICS/GB)? Also, I use My Backup Pro to restore call/MMS/texts only, that oughta be safe too shouldn't it?
I had a similar issue last night. never had problems flashing from viper to cm10 till yesterday. I've flashed back and forth about 3 times until I flashed the leaked 4.2 camera with sphere camera on aero cm10 Halloween build. I was playing around with the sphere camera and attempted to get it to actually finish loading the pics together by overclocking to 1.4mhz and I ended up pulling the battery. it boot looped very slow and laggy after. I did a full wipe, fresh install of aeros cm10 from twrp and got the same thing. So I recovered viper Rom from twrp , booted, then did a full wipe and install of cm10 and still boot loops laggy. I did not have the overclock settings "set at boot" ticked when I put it to 1.4mhz. odd indeed
sent by the viper
So... I was having no issues until today's huge headache. I was on cm10 10-25 and it worked great. Dirty flashed to 31 and it all went to hell. Slowed to a crawl so restarted to recovery to fix permission. Restarted and it kept restarting. I got some failure message when it would boot. Don't recall what it was.
I then tried 3 different recoveries and also full wipes and fresh flashes of 3 different roms. Same loop result basically. Finally an old recovery worked and I'm on a month old mrom version now. Soo... any thoughts on what the heck happened? I did nothing out of the ordinary. I was worried I somehow bricked but obviously not since I'm sending this on my phone. Kinda freaked to do anything right now... any thoughts or help/ideas?
PS... I just use the basic cwm and only cwm for my recoveries.
Sent from my Incredible 2 using xda app-developers app
Ukb wont boot here.
Sent from my HTC_Amaze_4G
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
fen0m said:
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
Click to expand...
Click to collapse
Someone just threw down on the info. Sounds like I will be flashing the latest mrom. Not gonna repeat the horror of my recent cm10 fiasco. Thanks for this.
Sent from my Incredible 2 using xda app-developers app
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
jtsrtr13 said:
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Sent from my Incredible 2 using xda app-developers app
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Sent from my MB865 using xda premium
A2Trip said:
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Click to expand...
Click to collapse
I did the revert a while back for some other issues and didn't have any trouble getting aeroevan's CM10 up and running. I haven't had any issues with it other than the persistent bugs which are no problem for me. I don't think these issues have anything to do with the radio, but with the way the stuff is getting flashed. You might try a different recovery. I have had success with TWRP and CWM (as installed from ROM Manager, not touch) restored from a backup for me, but I didn't install using CWM.
ericsdeadinside said:
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Click to expand...
Click to collapse
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Don't know what to tell you. I switched to 4ext ran CDMA miui for a week and I was able to flash cm10 with no issues.
Sent from my Incredible 2 using xda app-developers app
jtsrtr13 said:
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
+1... seems like only Sence ROMs have been working on my girls Inc. 2. Viper seems fine for now... But her phone must literately hate CM9 and 10...7 works fine too. Not quite sure why these issues have been going on to few of us but I'm almost certain it will not be solved... On the move...
Sent from my MB865 using xda premium
hey guys I fixed my Inc 2 with jb ics lag/ boot looping issues.
check it out
http://forum.xda-developers.com/showthread.php?t=1987051
Sent from an incredibly running JB inc2
Hi everyone,
I've searched everywhere for a solution so please help!
Basically i've had my note 2 for around 3 months and it keeps freezing (so frustrating).
Surprisingly this happend on stock before i even rooted or anything like that.
I remember installing some game from the app store that started the freezing but i re flashed it on stock and this was ages ago. I went to samsung and they flashed it but they said that they dont know what it is. Without sending my baby away i'd love to get this fixed.
I've tried rooting, unrooting, different roms, clearing all the cashes.. apps to reduce lagg (incase it was something inducing it).
Im really clueless where to go with it..
(Freezes up to 5 times a day)
(On 4.1.2 because of custom rom)
(On Stock rom now trying to fix but still on 4.1.2)
Thanks for all your help in advance!
legendberry said:
Hi everyone,
I've searched everywhere for a solution so please help!
Basically i've had my note 2 for around 3 months and it keeps freezing (so frustrating).
Surprisingly this happend on stock before i even rooted or anything like that.
I remember installing some game from the app store that started the freezing but i re flashed it on stock and this was ages ago. I went to samsung and they flashed it but they said that they dont know what it is. Without sending my baby away i'd love to get this fixed.
I've tried rooting, unrooting, different roms, clearing all the cashes.. apps to reduce lagg (incase it was something inducing it).
Im really clueless where to go with it..
(Freezes up to 5 times a day)
(On 4.1.2 because of custom rom)
(On Stock rom now trying to fix but still on 4.1.2)
Thanks for all your help in advance!
Click to expand...
Click to collapse
try flashing latest stock rom and dont install any apps and play around with it, if it still freezes they you may have a fauilty unit
do you notice the phone heating up at all if so try removing any cases/pouch you may have
brockyneo said:
try flashing latest stock rom and dont install any apps and play around with it, if it still freezes they you may have a fauilty unit
do you notice the phone heating up at all if so try removing any cases/pouch you may have
Click to expand...
Click to collapse
Hi Broky
Its on stock at the moment and i've taken my case of because i thought it might be that before....
When i was in the samsung store it was flashed to the stock and i opened skype after the flash and it froze....
Dont know if this is much help?
Thanks!
Try super wipe script by zoot.
Then flash stock rom.
Don't tell it samsung or google account.
Play around with it like browse or do anything. If it still freezes then I am sorry then brockyneo is correct.
Sent from my GT-N7100 using xda app-developers app
Could be a faulty ram chip. Or flash chip. I don't think check disk works on flash drives. But if it was a hard drive that's be the fix.
Sent from my GN2 using XDA app.
ya it shouldnt freeze if its been flashed back to stock rom,especially through odin as it near bullet proof
maybe try what UtkarshGupta with the superwipe and try again with a stock rom
if not then you maybe looking at a faulty unit :crying:
brockyneo said:
ya it shouldnt freeze if its been flashed back to stock rom,especially through odin as it near bullet proof
maybe try what UtkarshGupta with the superwipe and try again with a stock rom
if not then you maybe looking at a faulty unit :crying:
Click to expand...
Click to collapse
Thanks a lot...
Is this quite a rare case? Im un able to re flash it at the moment but if it wasn't a faulty unit... what else could be the issue?
Thanks again for the help!
legendberry said:
Thanks a lot...
Is this quite a rare case? Im un able to re flash it at the moment but if it wasn't a faulty unit... what else could be the issue?
Thanks again for the help!
Click to expand...
Click to collapse
What firmware do you have? 4.1.1 or 4.1.2? If you are on a safe kernel (latest 4.1.2 for example) you could try "Dummy File Generator" from Playstore. (there are many reports with succesfull fixes on freezes.) Or, better, take a look at this thread, everything you want to know is here: http://forum.xda-developers.com/showthread.php?t=2133401
zetlorf said:
What firmware do you have? 4.1.1 or 4.1.2? If you are on a safe kernel (latest 4.1.2 for example) you could try "Dummy File Generator" from Playstore. (there are many reports with succesfull fixes on freezes.) Or, better, take a look at this thread, everything you want to know is here: http://forum.xda-developers.com/showthread.php?t=2133401
Click to expand...
Click to collapse
Hi,
thanks for responding! Im on 4.1.2 at the moment and il try the dummy file generator.... How does that exactly work?
Thanks again,
legendberry said:
Hi,
thanks for responding! Im on 4.1.2 at the moment and il try the dummy file generator.... How does that exactly work?
Thanks again,
Click to expand...
Click to collapse
Hey legendberry! Did you fix your problem? I'm having the same issue on a stock rom. Resetting and wiping didn't help so I sent mine for repair but it got sent back to me unrepaired and the issue is still there
I have stock note 2, running 2.1 worked flawless since day 1 (was first release in France). Last 2 days been freezing. Have freed up space in internal and external sd. Still happens. Removed some apps, still happens. Reboot, sometimes it works for while then locks up. Very frustrsting as this is business phone.
......
I am in the same situation, because my Note 2 in the last few days has been freezing with maxed out cpu (as reported by the Cool Tool app).
I am now in the process of wiping everything and restoring in the feeble hope to overcome the problem.
Edit: i have wiped everything by formatting with Odin and reloading firmware, then restoring nandroid backup. So far so good, almost 24h without freezing.
Edit2: 2nd day, started freezing again 0
Same problem here, since 2 days my Note 2 freezes all the time, sometimes with 100% cpu load. Sometimes I can use it for a couple of hours, sometimes after reboot it freezes instantly. :S
I did a factory reset (stock 4.1.2), wiped everything but still the same issue...
Very, very frustrating!
To users above: When did you get your Note 2? I've had mine since Oct 10, 2012.
R: Note 2 constant freezing issue
Me too, phone bought in October 2012.
Today I flashed latest Italian firmware, MB2, and started over. No freezes. Even filling sdcard with dummy file generator, which in previous firmware (French MB2) gave several freezes.
Ok.
Then restored nandroid, data partition only, and wiped cache and dalvik. Lots of freezes again, device almost unusable.
So I thought what's the difference? When freshly flashed phone had Touchwiz, while after restore had Go Launcher.
Uninstalled Go Launcher. Bingo.
No freezes anymore so far.
Weird, uh?
I'll report how it behaves in next hours.
Edit: it was go launcher indeed. It's been updated for a reported crashes reboots problem. Now my device is rock steady.
Sent from my GT-N7100 using xda premium
Currently having the same issue. What i had done is cleanwipe and restore to factory setting (4.1.2).
Just the moment i finished setting up, the problem occured.
I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.
Hi guys, i swear i searched! for like days! i still haven't found out how to solve this issue. problem started when i tried hellybean a few weeks back, and then i heard someone on the thread said to try and use the latest beta uber kernel at the time, and i did. What end up happening was that my hardware keys are dead, the lights still works but very dim, i think this is because of the swipe to wake thing where it leaves your hardware keys on 24/7 as long as the phone is on, which is not that bad because i'm now used to using the nav bar. but the real problem is that now every time I install a rom that is not JB 4.1 (haven't tried 4.2 though) i.e. 4.3, 4.3.1, it gets stuck at the app optimization screen, it would go about half way through optimizing the apps, and then just reboots itself, and it'll do that over and over, like boot loop but it can actually go into the rom. So i think this is not as bad as a situation as soft bricking or hard brick, but i just really don't know what the heck is going on to even try and fix it. I've tried odin, thinking that there may be something wrong in the boot file, nada, factory reset, nada, the only thing that worked was installing the 4.1 roms, i think it is because the 4.1 roms don't require app optimization.
If anything maybe anyone out there can help me find a way to disable app optimization? maybe that'll let me get into the rom.
btw, i dont really mind using 4.1, but i really want to try the jedi rom, but having my hardware buttons dead and jedi rom being TW and it doesn't seem to have a nav bar make it impossible for me to use the rom, so i've only been able to use cyanogen 4.1, which are great but they are pretty outdated, so if there are anyway to fix that, lmk too.
Anyways, any help would be appreciated thanks a ton guys! sry for essay!
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
krazierokz said:
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
Click to expand...
Click to collapse
Lol actually the problem started when I was on 4.3, and then upgraded to 4.3.1 helly bean, in which i tried to use the beta uber kernel, that was when the problem started. So the only roms that allows me to get pass the optimization screen were the 4.1.2 roms, which were TW, pananroid, like i tried a bunch, like super old ones, they all worked, just that when i try to get any rom higher than 4.1.2, it keep going back to that. And yeah when i tried to upgrade from jedi to aosp, to tried using infamous cache and it didnt work :/ because i've heard that's what would fix it... and lastly, Im using twrp 6.1 i think, not the latest one.
Thanks alot for the reply!
PS. I see you running slimbean 4.2.2, how is it? any probs? maybe i can try a 4.2.2 if this doesn't work out, i havn't been able to get any 4.2.2 roms cause the links are all dead, so idk if i'll have problems with 4.2.2. if there's anyway you can link it for me that'll be great! thanks!
PSS: also i've tried odin, but idk if that actually wipes everything, i'm having a feeling that it might be a script problem or something because it goes into the rom once, but it just refused to work and after like 10 seconds it reboots.
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
krazierokz said:
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
Click to expand...
Click to collapse
Ey thanks for the reply, ok so first, I did not try to restore any apps or system apps, I even odin so everything were wiped cleaned. So really dont know whats going on. After I updated to a newer hellybean, not newest by now, and a beta uber kernel, this happens. I see two other people having the same problem too. Also I tried to use 4.2.2 roms, did not work
Anyways any insight would be apreciated!
Thanks!
One more thing, I tried twrp 2.6.1.0 to flash as reccomended by all devs and still no results. :/
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
krazierokz said:
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
Click to expand...
Click to collapse
oh well, thanks for the reply then, im trying 4.4, hopefully it'll help... somehow... lmao idk haha