Database Users

When waking up device, gets black screen, hangs for few secs, then reboots

When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?

its because of the kernal, mine does this aswell..

kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!

I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.

beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.

verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.

I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying

There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading

beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!

Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.

It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.

Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.

grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.

i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..

[Q] freezes on 4.4.2 custom roms / kernels

on the latest d802 4.4.2 custom roms and kernels i get a lot of freezes.
it will freeze in the middle of an animation and will take some seconds up to some minutes and then working normal again.
sometimes i have to hard-reboot to get out of freeze / lag.
on older 4.4.2 slimroms i never had this behavior, only since some weeks with new roms / kernels.
i`ve tried every rom / kernel combo but sooner or later i will get a freeze again.
could a revert to stock and re-rooting / flashing custom rom maybe a solution? i`m afraid to do this because of the long time to backup my 32gb data.
what are your experiences with the latest 4.4.2 roms and kernels? did you find a solution for this with any combo or fixes?
help would be appreciated.

push! no one else with same problems? maybe i got a hardware defect?

paratox said:
push! no one else with same problems? maybe i got a hardware defect?
Click to expand...
Click to collapse
The only thing I can say is I own the VS980 version of the device and i've tried every single 4.4 rom offered on this sight and have the same issue with all. Most of the time i'm using the device and it freezes, sometimes reboots, and sometimes comes out of it after a few minutes. Also not being able to wake the device only seeing a black screen and forced to hard reboot device. 4.3 seems to be a much better with these issues but not completely solved for me. I'm hoping the release of 4.4 source from lg will fix these issues but i'm unsure. So at least your not alone in these problems lol. I've tried multiple kernels and governors etc. Bumping up the min freq on the cpu seems to help and changing to interactive governor but doesn't eliminate the issue just help. I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.

flyinj54 said:
I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
Click to expand...
Click to collapse
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^

paratox said:
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
Click to expand...
Click to collapse
Yea unfortunately it seems very common among these devices so i'm pretty confident it's a software issue although i'm not 100% sure of that. I ran a flex rom for a few days on 4.2.2 and didn't have any of the same issues.

added a poll as a matter of interest.

omni-ROM, Mokee rom, vanir rom etc.freezing problem still continues.

Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.

lubirdy said:
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
Click to expand...
Click to collapse
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk

flyinj54 said:
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, stock cm kernel.
I'm thinking back now and it did freeze once when first signing into the Google account immediately after flashing the ROM, but nothing after that. So.. nearly spotless

Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk

flyinj54 said:
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Best of luck! To be specific, I'm using the snapshot release of cm11... still don't trust the nightly releases

i did a lg flash tool stock restore, factory reset and OTA updates. now the freezes did not come back until now *knock on wood*.
when i did a backup of the sd there was one corrupt media file which was not able to transfer.
maybe the media scanner did go crazy and was the reason for the freezes.

using cm11 m3 on my d802... very little freezes compared to previous nightlies, fingers crossed

Replaced digitizer & screen - Fixed then broken again?

Hello,
I have a UK unlocked, GT-I9505 that had a broken screen, I bought a new black edition screen (dark black not black mist) and replaced it. Previously there was an AOSP 4.4.2 ROM on it that worked fine and everything was happy and good. I then upgraded to a AOSP 4.4.4 ROM which stopped the touch screen functioning (it displays, but no touch), and also tried a 4.4.3, same story.
The touch screen works in TeamWin but anytime it gets on the OS it just stops taking input.
Any help/advice would be massively appreciated

It almost sounds like you placed a different type of touchscreen in your phone and you got lucky it worked in the 4.4.2. It sounds to me like some drivers were changed after the 4.4.2. versions.
If your touch screen works in the recovery, then it's definitely software related.
Do a full wipe in the recovery and flash the rom again. If it still doesn't work, try a different rom (preferably TW based, because you are already on an aosp rom).

Lennyz1988 said:
It almost sounds like you placed a different type of touchscreen in your phone and you got lucky it worked in the 4.4.2. It sounds to me like some drivers were changed after the 4.4.2. versions.
If your touch screen works in the recovery, then it's definitely software related.
Do a full wipe in the recovery and flash the rom again. If it still doesn't work, try a different rom (preferably TW based, because you are already on an aosp rom).
Click to expand...
Click to collapse
Thanks, I've tried full wiping, I'll flash a TW (TouchWiz?) rom and see if that works

jamie_ap said:
Thanks, I've tried full wiping, I'll flash a TW (TouchWiz?) rom and see if that works
Click to expand...
Click to collapse
Hi,
Yes TW stands for TouchWiz, and I agree with the person above there. As it works on recovery, it should work on system. Just try flashing another ROM, and the best would be go back to the ROM you were IMHO. At least it worked right .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10

XxLordxX said:
Hi,
Yes TW stands for TouchWiz, and I agree with the person above there. As it works on recovery, it should work on system. Just try flashing another ROM, and the best would be go back to the ROM you were IMHO. At least it worked right .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Click to expand...
Click to collapse
Don't seem to be getting anything working , I'ved tried what I believe to be the 4.2.2 ROM I had working but as soon as I swip install on TeamWin it insta-power offs and then reboot into TeamWin :/

[Q&A] [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]

Q&A for [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.

NEO2598 said:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
Click to expand...
Click to collapse
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk

MeestaAytch said:
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
It has been stated in the ROM thread multiple times that you must use a 4.2 STOCK JB MODEM for best compatibility. Any other modems you guys use is solely at YOUR OWN DISCRETION. @MeestaAytch they should know what to use at this point but thanks for clarifying again for those who don't want to search before posting :highfive:

@jakew02 no problem. I know it's tiring repeating the same information but from what I've seen in my time using XDA.... It'll never change.
I'm glad you devs still continue doing what you're doing for us though knowing this nonsense goes on.
Sent from my LG-LS980 using Tapatalk

A few bugs
Hi,
The thread is too big for me to go thru it post by post so I'll just make a few questions and hopefully I'll get some answers. I flashed this ROM and it was working flawlessly. I only found very few bugs like not being able to set up multiple recurrent alarms because the app would freeze and there was another bug but I can't remember. The problem I find frustrating is with the text messages or SMSs. At first I was not receiving SMSs. Then I was receiving them but I couldn't send any. I returned back to stock VS98024a and I'm still having the same problem but at least I'm getting a pop-up when "General problems: cause code 96". I have googled this several times in several ways and can't seem to find a solution, not even on the Verizon site or help app on the phone. I need help with this please.

How to keep the back home task manager buttor on the screen?

battery life? i want to install on lg d800 and its beta only..

dori kernel
Hi,
From where you get Dorimanx kernel for AOSP ROMs ?

My phone says it can't connect to the camera, and the torch. Does anyone know how to solve this?
Sent from my LG-LS980 using XDA Free mobile app

LG G2 D802 SIM not recognized
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex

a13xch1 said:
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
Click to expand...
Click to collapse
Please state exact filename and order of wipe/flash.

Just tried the test build for D802. Booted at LG logo for a while then screen turned black with 2 red lines and one green vertical line. I was so sure I was gonna get the permanent black lines but then again I read that the damaged screens are caused by already faulty hardware under high heat.
Anyways, I panicked and then I restarted the phone by pressing power + down. Then I got the weird boot sequence like everyone above describes and it boots into the OS. Thank God I got no black lines! However it wasn't stable for me as the phone rebooted itself twice within the span of 20 minutes. I'm going back to 13/10 build for now.

Any d802 users flashing latest twitter released rom can you please report here if jdi or lgd and whether or not weird logo appeared?
I'm on jdi and had weird logo appeared after clean flash. I did not let the rom boot and reflashed previous version without further problems

FYI, houston's latest works great so far on the VS980. Clean flash, using RenderKernel R24.

So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up

jclemens23 said:
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
Click to expand...
Click to collapse
Migrating from one ROM to another is for me like this:
1. Nandroid backup
2. Wipe all except sdcard (yes, wipe system)
3. Flash new ROM
Be sure to always have a Nandroid backup!
And always check what baseband (aka radios or modem) your new ROM is requiring.
-___-
If you are UPDATING your current ROM, I.e. flashing a new build of let's say paranoid android, you can flash the updated file right on top of your old system. That is called DIRTY FLASHING and it's actually risky, so please, always do Nandroid backups!
-____-
Peace

Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed

jclemens23 said:
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
Click to expand...
Click to collapse
Ok
I would;
Update my custom recovery to the latest
Download recommended baseband, to be on the safe side
Redownload the ROM
Check the md5-checksum
Retry to install it
Flash the recommended baseband, better safe than sorry
Never give up
Peace

Hi guys i just flashed the newest build and out of all the roms i have flashed i have never seen this problem. After i flashed i have no sim service at all. Done a clean install still no good.

Random reboot with lollipop 5.1

I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.

Greetings.
Have you tried using any other kernel, eg. franco kernel?

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)

Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app

killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.

This does not happen at all to me(using stock 5.1 with Franco Kernel).

This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.

_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).

Your battery is dying, I've been getting the same problem until I replaced the battery today.

richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?

I've been getting the same issues on my N7 since updating.

regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....

ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.

gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.

_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks

I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.

Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng

gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.

I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk