Related
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
The_Wolf91 said:
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
Click to expand...
Click to collapse
Flashed Android 5.0.1 and no random reboots (as I also said when i wrote my first post).
I don't know if the "question" is clear, but can you help me reading the "last_kmsg" which I attached in first post? Thanks
Same exact thing happening to me also.
Sent from my Nexus 5 using XDA Free mobile app
The same is happening to me. And it looks like a hardware problem cuz when the phone reboots it keeping reboot until I keep pressing the power button while boots.
I have a bad experience about it. In my Nexus S when updates to Jelly Bean the same occurs until phone suddenly die. (I live in Brazil so, guess what? I have now a wonderful paper weight)
No luck with 5.1.1
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Try another (custom) kernel.
beekay201 said:
Try another (custom) kernel.
Click to expand...
Click to collapse
I just flashed ElementalX kernel but no luck, random reboot happened on 5.1.1 too. By the way it was quite obvious because it happened already on 5.1 Google's factory image (stock kernel so)..
I have exactly the same issue with nexus 5 since upgrading to 5.1.0.
I went back to 5.0.1, which solved it for a few days, but now this happens with 5.0.1 as well.
also, before random reboots happen, the power button becomes extra sensitive, so one keypress causes the screen to turn on and off again, or to display the shutdown menu.
this does not happen when the phone is stable.
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Sent from my Nexus 5 using XDA Free mobile app
noob424 said:
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Click to expand...
Click to collapse
Same here.
LG Nexus 5 - Lollipop 5.1.1 LMY48B
Unlocked bootloader;
Rooted;
ClockWorkmod 6.0.4.5 (not flashed - just boot on image when used);
Wipe factory reset (in cwm). Flashed 5.1.1 image files (boot, radio, bootloader, system and cache).
Random reboots, and sometimes with apps optimizing.
I have the same problem with N5 since upgrading to 5.1.1 - never had any problems before. Doing it several times an hour now. Trying a cache clean next, after I wait for the optimising apps to finish yet again!
Hi all,
I had the same problem. Everything stock, up to datę, no root. Phone was rebooting itself several times in a row.
Right now it seems that problem dissapeared. Reboots in my case was caused probably by application Autoguard Dash Cam Blackbox. After removal no reboots for 2 months and no memory leak.
cleared cache and it happened again within a minute...
Does seem to be linked to the power button
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
simbapenn said:
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
Click to expand...
Click to collapse
I have N5 kit kat 4.4.2 in Chrome watching videos randoms reboot its happens
This is happening to my fiance's N5. It happens when she's using it and also when it's not being used. When it reboots, it optimizes the apps and says the battery is at 0 when it was a full charge. Only way to turn it back on is to connect it to a charger. Frustrating.
FYI the update to 6.0 did not solve the restart problem. It's either hardware related, app related or a bug that's still in the OS.
I'm selling my Nexus because of this, has been happening for a few months now.
It's not software related, it has to do with the actual power button. Some people had success changing it out, soldering it etc., but I don't have that time or knowledge.
Google wouldn't help, as I'm out of warranty. So I guess it's goodbye Nexus. Really unfortunate given that the phone works fine, it's just a quality issue.. will have to re-evaluate buying another Nexus in the future.
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
---------- Post added at 04:41 PM ---------- Previous post was at 04:20 PM ----------
I have been using this awesome app on my nexus 5, just so I don't have to use the power button here is the play store link.
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree
maccboy2010 said:
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
Click to expand...
Click to collapse
Confirmed the update will NOT fix this issue.
MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
The lower part of my screen (last inch or so) is often unresponsive so if I type, I'll miss a bunch of spaces.....
theMoiz94 said:
MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
Click to expand...
Click to collapse
Test your touchscreen using this app https://play.google.com/store/apps/details?id=com.rn.yamtt
If there are issues with multi touch, only thing I can suggest is to switch to other ROM if you are rooted and bootloader unlocked
I had read that CM has fixed touchscreen issue in their latest CM12.1 nightlies
If you are not rooted, a factory reset may work (hopefully) else call the customer service for RMA if they do it for you so easily
I was facing such issue on CMOS12 and also on all lollipop ROMs so I downgraded to XNPH05Q
Q&A for [ROM] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*
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.
Before posting, please use the forum search and read through the discussion thread for [ROM] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can I install it without bootloader unlock?
Summersett said:
My bootloader unlocked Maxx is on 4.4 (19.5.3.obake-maxx_verizon.Verizon.en.US). Since my bootloader is unlocked, do I really have anything to fear when flashing ROMs or am I pretty much guaranteed to be able to always have WP off and root? I'd like to give this one a shot but don't want to cross any bridges I may not be able to come back across if need be.
Click to expand...
Click to collapse
My bootloader is locked, I'm on 4.4.4 with root, but I don't now how I can unlock my moto, I must to have TWRP? How can I install this recovery? Help me please, I want lollipop, and verizon is so slow.
This isn't the place to ask that, and right now you are stuck on stock. Please dig around the forums and do some research before spamming threads where content does not belong.
No GPS
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
I haven't had this issue and have reflashed this ROM a few times. Tbh I have never even heard of that as an issue (though it's not like I researched Lollipop problems since I wasn't having any).
I used TWRP 2.8.4.0, factory reset, flashed the ROM, and then flashed these GApps. Idk if that makes a difference. Give it a shot if nothing else is working for you? Good luck.
Dang... That is exactly how I did it. I used that same exact gapps file and also am on TWRP 2.8.4.0. Seems like none else is reporting this problem on our phones. Maybe the radio got screwed up? Just thinking out loud here
Installed OctOS on two separate MAXXes. My gfs seems stable. Mines been touchy though-
A) Like someone else mentioned, using the flashlight for an extended period often ends up in the phone doing a hard reboot. Haven't tested this with her phone but she hasn't reported anything to me either.
B) WiFi has been unstable. Initially it was fine, but every now and then it starts refusing to connect to any network. It doesn't kick back any error. It will say connecting, etc, then at some point fail and go back to just noting it's a saved connection. Have to go through some combination of forgetting the connection, wiping cache/Darvin, think I even tried running fix permissions. Eventually it will work normally again, but not for long before having the same issue. There haven't been any wifi issues with the other phone. The first time this ever occurred was right after using it as a hotspot, but its happened more often without any hotspot usage than with it.
C) Did great at first, but without installing very many apps, it feels like it's gotten slightly sluggish and is often low on memory, and is burning through the battery much quicker. Used the be able to clear 24 hours before needing to charge, now I'm lucky to get 16. I haven't had the chance to see if this is also an issue on the other phone or not.
GPS works nicely for me with this rom. My phone got a fix in seconds with 16 satellites.
Question: which is the best way to theme this (or others, for that matter) rom? Download CM12 themes from mayket?
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
Did you ever get GPS back? Some say going back to stock, getting a lock, and then go back to the custom rom works. There is also a link in the exodus thread about doing two fastboot commands, which worked for me for a bit, bit now I'm back on stock with no GPS at all. Curious if you got yours working.
Hello there,
Is there anyone who can help me getting back to KitKat 4.4?
I have bought a Note Pro and the previous owner cleaned it and updated it to Lollipop.
The troubles I experience are:
flickering screen,
unwanted reboots and
the message: cpu overheated.
[solved this a bit by limiting background services and it is al lot less but I do not like it].
So I would like to go back to KitKat as I understood on this forum this OS is rockstable.
I flashed original firmware P900XXUANK2 [PHN version] with Odin to my Pro, well it starts up but freezes with
"Samsung" in the screen, and that is it. [Did this several times]
When I flash it back to Lollipop it works, but still having prementioned problems.
Is there anyone who would like to help me, I am a newby and searched on XDA but am stuck.
Would appreciate any help.
Greetings
Aedriaen
The Netherlands
I have a note pro p905
I flashed between lollipop and KitKat and never had similar problem
maybe it is your bootloader that is locked to lollipop and it prevents you from flashing KitKat
maybe you need to flash the KitKat factory firmware which is 4 files with pit file
if someone can confirm this I will put the link to a factory firmware
This sounds like the battery connector issue to me, it may not be software.
http://forum.xda-developers.com/showthread.php?t=2835337
Sent from my SM-P900 using Tapatalk
Aedriaen said:
Hello there,
I have bought a Note Pro and the previous owner cleaned it and updated it to Lollipop.
The troubles I experience are:
flickering screen,
unwanted reboots and
the message: cpu overheated.
[solved this a bit by limiting background services and it is al lot less but I do not like it].
So I would like to go back to KitKat as I understood on this forum this OS is rockstable.
I flashed original firmware P900XXUANK2 [PHN version] with Odin to my Pro, well it starts up but freezes with
"Samsung" in the screen, and that is it. [Did this several times]
Click to expand...
Click to collapse
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
muzzy996 said:
This sounds like the battery connector issue to me, it may not be software.
http://forum.xda-developers.com/showthread.php?t=2835337
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Hello Muzzy996,
thanks for the reply, battery connector seems to be OK since I am able to transfer data between de pro and my pc.
Also Odin gives me a green light when I connect the pro to the pc. Loading the battery is not a problem either. So it seems to me the connector don't seems to be the problem.
Anyway, thanks for your help.
Appreciate it!
Beut said:
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
Click to expand...
Click to collapse
Hello Beut, thanks for the reply.
Connectors seems to be ok, loading the battery works fine, transfering data to my pc and vice versa works fine.
Odin gives a "green" light when flashing so I don't think this is the problem.
Tried it again with the latest Odin and flashing works fine, but the problem remains.
Flickering occurs only when the connector is not conneted to the device.
Appreciate your help.
Teflanzy said:
I have a note pro p905
I flashed between lollipop and KitKat and never had similar problem
maybe it is your bootloader that is locked to lollipop and it prevents you from flashing KitKat
maybe you need to flash the KitKat factory firmware which is 4 files with pit file
if someone can confirm this I will put the link to a factory firmware
Click to expand...
Click to collapse
Hello Teflanzy,
Thanks for the reply. I searched the internet for hours but am only able to find 1 file containing the Samsung
Galaxy Pro 12.2 Kitkat 4.4 firmware.
If someone has another or a site where to fetch it, I would appreciate it.
Appreciate your help.
Aedriaen said:
Hello Beut, thanks for the reply.
Connectors seems to be ok, loading the battery works fine, transfering data to my pc and vice versa works fine.
Odin gives a "green" light when flashing so I don't think this is the problem.
Tried it again with the latest Odin and flashing works fine, but the problem remains.
Flickering occurs only when the connector is not conneted to the device.
Appreciate your help.
Click to expand...
Click to collapse
I think you confuse between battery connector and USB connector. When using Odin, you are only working with USB connector.
Flickering when not connected to a charger, the problem is from your cracked battery connector which can only see under microscope.
Trust me, the only fix is resoldering your battery connector. Kitkat or Lollipop has nothing to do with flickering screen.
Beut said:
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
Click to expand...
Click to collapse
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
I think this is the problem, any idea where I can get the Kitkat bootloader for the Pro. Searched but didnot find it.
When I have this file [excuse me for being a newby] can I flash this with Odin using the BT option?
Greetings
Aedriaen
Aedriaen said:
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
I think this is the problem, any idea where I can get the Kitkat bootloader for the Pro. Searched but didnot find it.
When I have this file [excuse me for being a newby] can I flash this with Odin using the BT option?
Greetings
Aedriaen
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
I don't know which model you have SM-P900 or SM-P905/907. Search for firmware from that site, Cellular South is for US region.
Depending which one you want, Kitkat and Lollipop have different bootloader.
what is your model ? What firmware are you going to flash ?
This is Bootloader for Kitkat Note Pro
http://www.mediafire.com/download/6862sfh6d8bjas7/BL_Kitkat_Note_Pro.rar
In Odin, you should load BL ( bootloader ) and AP ( rom file ), after it's done, you should boot normally to the start screen.
Beut said:
I think you confuse between battery connector and USB connector. When using Odin, you are only working with USB connector.
Flickering when not connected to a charger, the problem is from your cracked battery connector which can only see under microscope.
Trust me, the only fix is resoldering your battery connector. Kitkat or Lollipop has nothing to do with flickering screen.
Click to expand...
Click to collapse
Hello Beut,
I found out that when the battery is above 40% the problem does not occur. Only beneath 40% the flickering
starts???
Greetz
Aedriaen
Aedriaen said:
Hello Beut,
I found out that when the battery is above 40% the problem does not occur. Only beneath 40% the flickering
starts???
Greetz
Aedriaen
Click to expand...
Click to collapse
Must either be the internal battery connection or the battery itself. Again going to point you back to the flickering thread, specifically post 131 in it. Look at the photos in that post.
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Sent from my SM-P900 using Tapatalk
suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?
I don't know the answer to that
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom
lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working
dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???
Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u
Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem