UPDATE: don't need anyone testing this anymore as it is not fixing most reboots
Can someone who is running custom recovery and has bad/frequent reboots install the attached file and see if it alleviates your reboots?
Please let me know what version of the OS you are running and if you are on JSS15J or JSS15Q, whether you updated via factory image or OTA.
I am 99.99% sure nothing bad will happen to your system. This will not disable your ability to get OTAs, nor change any system files, nor affect touchscreen, nor affect GPS, ...
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Sent from my Nexus 7
joeshmoo said:
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Click to expand...
Click to collapse
If it works, it should work ok with CM as long as you run it in TWRP.
It doesn't actually touch the ROM. It uses the kernel to reset the DDR3 memory timings and allows the system to retrain.
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
getting desperate and flashing this to try..
Didn't work. Just had my first reboot.
Sent from my Nexus 7 using Tapatalk 2
fkfs9 said:
Didn't work. Just had my first reboot.
Click to expand...
Click to collapse
Could you tell me what OS you are running and whether you've run an OTA before?
sfhub said:
Could you tell me what OS you are running and whether you've run an OTA before?
Click to expand...
Click to collapse
I'm on 15Q odex stock ROM. I never had an ota before.
I rooted and unlocked the boot loader and flash this ROM yesterday.
Just had a reboot on mine as well.
Running build 8 of this:
http://forum.xda-developers.com/showthread.php?t=2391779
[ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 8][2013/08/25]
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
sfhub said:
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
Click to expand...
Click to collapse
Thanks for trying
Sent from my Nexus 7 using Tapatalk 4
joeshmoo said:
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
Click to expand...
Click to collapse
Don't you mean you like to know who you are flashing?
Sent from my Nexus 7 using xda app-developers app
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
KiaraTheDragon said:
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
Click to expand...
Click to collapse
can i flash clean rom without losing data or apps? im on modded stock rom + elementalX
I haven't had a reboot since the newest update.
Sent from my Nexus 7 using xda app-developers app
Related
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
phermey said:
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
Click to expand...
Click to collapse
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
yes if rooted. lots of people are stock and running franco.
phermey said:
yes if rooted. lots of people are stock and running franco.
Click to expand...
Click to collapse
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
phermey said:
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
Click to expand...
Click to collapse
wouldn't hurt to wipe anyway. ill stop wiping and see if i notice a difference though, so far i dont notice any. so id probably just skip out on wiping as it does seem useless because my phone still feels the same
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue?
I've flashed the December version of the kernel afterwards and the problem prevails (ktoonsez doesn't include every kernel download link, a bad practice in my opinion)
I am on CM now and everything is working fine, I wonder if anyone has been victim to this weird issue
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue? ...
Click to expand...
Click to collapse
I am guessing but is this a permissions issue? I've flashed KTManta a number of times including just yesterday with TWRP and never had the issue you describe. Occasionally, right after flashing a ROM or Kernel, I have seen from TWRP a "Fix Permissions" message which I always execute. Some custom ROM/Kernels flash instructions even include a "Fix Permissions" instruction.
Also sometimes after flashing then rebooting I've had to "reinstall" Superuser so it can grant root permissions to various programs. As a habit, right after a new flash, I start Superuser once just to see if it says it needs to be reinstalled. This is not a reinstall from an apk but is a dialogue message displayed when the app is started.
As I wrote this is purely a guess on my part.
I had a laugh at the thread title. (sorry) You either have a corrupt download or something else really weird going on. A kernel wont remove root from your unlocked firmware and ROM files unless the flashing script is actually programmed to remove the files needed. Which its not.
Well this is strange, because I have fixed the permission issue and wiped cache and dalvik, not once but multiple times (I set up the kernel thrice, after it was malfunctioning).
But seeing you two replying, I set up KtManta over CM today and it is not giving me a bit of trouble, strange indeed.
btw, is it true that KTManta fixed the color issue a bit?
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
EniGmA1987 said:
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
Click to expand...
Click to collapse
Stock
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
Stock
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
brees75 said:
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
Click to expand...
Click to collapse
What's the difference between AOSP and stock roms?
And yes it's now working flawlessly with CM.
Sent from my Nexus 10 using Tapatalk HD
My Nexus 7 just got the new 4.4.2 OTA update. Can't see any differences yet.
Anyone seen an OTA link?
wilde68 said:
My Nexus 7 just got the new 4.4.2 OTA update. Can't see any differences yet.
Click to expand...
Click to collapse
There's now cast screen option in the display settings!
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
chnages:
1. transparent lockscreen, nice! but launcher is not transparent
2. in app drawer apps and widgets text is now in white colour.
this is for now, i need to take a look more
I think Chrome feels a lot smoother, still got the boot animation glitch and the jumping back to another app when hitting the back key out of an app.
Sent from my Nexus 7 using Tapatalk
There's any link to download the stock kernel from the 4.4? I don't have any PC now and I can't extract it from the Google image.. Sorry for my English
Este mensaje se autodestruirá desde tapatalk
Anyone having issues with their screen on time?
Sent from my Nexus 7 using XDA Premium 4 mobile app
khaytsus said:
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
Click to expand...
Click to collapse
I received the update and i have mkernel.
Sent from my Nexus 7 using Tapatalk
khaytsus said:
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
Click to expand...
Click to collapse
Whats the kernel version is it finally 3.4??
chand9336 said:
Whats the kernel version is it finally 3.4??
Click to expand...
Click to collapse
Yup....Its version 3.4 :good:
jithumon said:
Yup....Its version 3.4 :good:
Click to expand...
Click to collapse
Are you talking about grouper/nexus 7 2012?
nikola1970 said:
chnages:
1. transparent lockscreen, nice! but launcher is not transparent
2. in app drawer apps and widgets text is now in white colour.
this is for now, i need to take a look more
Click to expand...
Click to collapse
transparent lockscreen was also there in 4.4.1 :silly:
khaytsus said:
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
Click to expand...
Click to collapse
I'm back on the google kernel but still the ota or sideload doesn't work.
Sent from my Nexus 7 using XDA Premium 4 mobile app
chand9336 said:
Whats the kernel version is it finally 3.4??
Click to expand...
Click to collapse
Kernel on my device is 3.1.10-g4776c68 after up date to 4.4.2 dated 20 Nov 2013 on grouper
quincyquinn said:
Kernel on my device is 3.1.10-g4776c68 after up date to 4.4.2 dated 20 Nov 2013 on grouper
Click to expand...
Click to collapse
Same here
On my N4 it is 3.4 though
Rob
redmonke255 said:
I received the update and i have mkernel.
Click to expand...
Click to collapse
It installed? I'd be quite surprised It'd fail for both boot.img and power grouper library. I just removed both from my OTA zip and left m-kernel in place
ev!denz said:
I'm back on the google kernel but still the ota or sideload doesn't work.
Click to expand...
Click to collapse
Can't just restore kernel if you're using a kernel which replaces any files, such as m-kernel replaces the power grouper. You could restore the full system image, the power grouper lib, or remove it from the OTA. I opted for the latter.
I took the ota and it caused me to bootloop. Anyone know how to fix this?
fyi not rooted and hardly anything even installed on it. My mother used it to play solitaire basically.
I cant for the life of me get this OTA installed. Running stocked rooted 4.4.1, installed and set up yesterday. No custom kernel. Have tried flashing in latest TWRP, as well as sideloading via adb and same result.
It states:
Not enough free space on /system to apply patches
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Just applied the 4.2.2 OTA to my WiFi N7 2012 and noticed that the System ROM size is 670MB. Was this the default System ROM size for previous ROM versions? I never paid attention to the System ROM size before, but I was about to integrate a couple apps using Titanium Backup and got a message saying that I did not have enough room to integrate the app. I had integrated some of these apps before without running into a storage room problem. Also, how can I determine the version of the bootloader that's currently being used?
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
When I flashed stock 4.4.3 update (kernel, radio and firmware) I thought maybe I've installed a bad ROM.
Every time I backed out of certain applications, the last application in the recent apps list (the one before the one I just backed out from) opened for a second and closed it self.
For example, I played Boom beach, sent it to background using HOME.
Then, I used App Stats, played around in some screens and then backed out of it -> Boom beach opened for a second and closed itself.
Then I installed the 4.4.4 update, and this still occurs...
This doesn't happen with every application... I can back out of most apps without any issue.
This never happened on 4.4.2 and lower.
It may be an app issue and not the system so I'd love a feedback from you guys before I contact the apps developers.
Am I the only one who experience this issue?
liorry said:
When I flashed stock 4.4.3 update (kernel, radio and firmware) I thought maybe I've installed a bad ROM.
Every time I backed out of certain applications, the last application in the recent apps list (the one before the one I just backed out from) opened for a second and closed it self.
For example, I played Boom beach, sent it to background using HOME.
Then, I used App Stats, played around in some screens and then backed out of it -> Boom beach opened for a second and closed itself.
Then I installed the 4.4.4 update, and this still occurs...
This doesn't happen with every application... I can back out of most apps without any issue.
This never happened on 4.4.2 and lower.
It may be an app issue and not the system so I'd love a feedback from you guys before I contact the apps developers.
Am I the only one who experience this issue?
Click to expand...
Click to collapse
Backup your data and try factory reset.
liorry said:
Am I the only one who experience this issue?
Click to expand...
Click to collapse
No you're not alone, I've also gotten this behaviour after a clean install of 4.4.3
Any apps in particular or every app you back out of?
Salty Wagyu said:
No you're not alone, I've also gotten this behaviour after a clean install of 4.4.3
Click to expand...
Click to collapse
liorry said:
Any apps in particular or every app you back out of?
Click to expand...
Click to collapse
Happens with any app that was last used
Wiped my data couple of times and reflashed different Roms. Most of them had this issue.
You suggest a factory reset through settings will do the trick?
sidnoit22 said:
Backup your data and try factory reset.
Click to expand...
Click to collapse
Very weird... I wonder how this is not well known by now. Did you update your firmware with the OTA or a flashable zip? Maybe it's ROM related?
Salty Wagyu said:
Happens with any app that was last used
Click to expand...
Click to collapse
liorry said:
Very weird... I wonder how this is not well known by now. Did you update your firmware with the OTA or a flashable zip? Maybe it's ROM related?
Click to expand...
Click to collapse
I factory resetted in TWRP then Fastboot erased leaving no trace behind, and then fastboot flashed 4.4.3. It's stock.
It's probably not well known because people may be using their device differently, pressing Home to exit an app instead of using Back maybe... or they don't think much of it to report it, I know I didn't, but it does get annoying after a while.
Salty Wagyu said:
I factory resetted in TWRP then Fastboot erased leaving no trace behind, and then fastboot flashed 4.4.3. It's stock.
It's probably not well known because people may be using their device differently, pressing Home to exit an app instead of using Back maybe... or they don't think much of it to report it, I know I didn't, but it does get annoying after a while.
Click to expand...
Click to collapse
Well, now that I know I'm not alone, I'll report it later today.
Maybe Google is trying to kill the back button
Thanks for the info!
Same problem here. 4.4.3 and 4.4.4.......
MelquiXDA said:
Same problem here. 4.4.3 and 4.4.4.......
Click to expand...
Click to collapse
OTA or custom ROM?
Strange, I just tried to reproduce this bug on my phone with 4.4.3 and I don't have that bug. But, I have franco's kernel, maybe that makes some difference.
liorry said:
OTA or custom ROM?
Click to expand...
Click to collapse
CM11, Stock ROM or Stock ROM with root, xposed and franco.kernel. All have this issue. My Moto X with stock rom too.
Sent from my Nexus 4 using XDA Free mobile app
mara- said:
Strange, I just tried to reproduce this bug on my phone with 4.4.3 and I don't have that bug. But, I have franco's kernel, maybe that makes some difference.
Click to expand...
Click to collapse
MelquiXDA said:
CM11, Stock ROM or Stock ROM with root, xposed and franco.kernel. All have this issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I was about to flash franco kernel but it seems it's not the solution
Well, I don't have this bug. I just opened CSR Racing, pressed Home to minimize it, then I opened eBay application, then I pressed Back, and it went normally to home screen, CSR Racing did not appear.
EDIT: I managed to reproduce it. CSR Racing appeared for a second when I exited from Settings. I never noticed this until I read this topic. So, bug exists.
mara- said:
Well, I don't have this bug. I just opened CSR Racing, pressed Home to minimize it, then I opened eBay application, then I pressed Back, and it went normally to home screen, CSR Racing did not appear.
EDIT: I managed to reproduce it. CSR Racing appeared for a second when I exited from Settings. I never noticed this until I read this topic. So, bug exists.
Click to expand...
Click to collapse
It's a intermittent bug....
Sent from my Nexus 4 using XDA Free mobile app
That's a known bug... No kernel or rom can change it. Funny how people think changing kernel can solve it lol.
Possibly it's related to Android system/systemui. I think only Google can fix this issue...
sarus_b said:
That's a known bug... No kernel or rom can change it. Funny how people think changing kernel can solve it lol.
Possibly it's related to Android system/systemui. I think only Google can fix this issue...
Click to expand...
Click to collapse
I'm sorry to ruin your LOLness but it may be a kernel/ROM related issue. I already found a 4.4.3 ROM (LiquidSmooth 3.0, didn't check 3.1) where this bug doesn't occur.
Moreover, the kernel is responsible for cleaning up the memory by killing and restarting applications.
I created a small application that behaves like a taskiller (restartPackage/killBackgroundProcesses) and kills every app I exit, just for testing purposes and it didn't work as expected on 4.4.3/4.4.4 so I think it's probably a kernel issue (4.4.3 received an updated kernel which is used on 4.4.4 as well).
It can still be a systemUI issue but even if it is, that can be fixed on AOSP ROMs, without waiting for Google.
If you have a link to the reported bug ("known bug"?) that would be great.
Edit. Bug persists with CM11
https://code.google.com/p/android/issues/detail?id=63570
http://forum.xda-developers.com/nexus-4/help/strange-nexus-4-kitkat-4-4-2-button-t2565035