Hey everyone! My Nexus 5 is experiencing random reboots and does so regardless of which rom I have installed. I started by pulling logcats and didn't find anything interesting (not an expert though), so I moved on to pulling the last_kmsg and saving it to a txt file. It says the reason for the last reboot was "kernel panic," but I assume there is more to it. There has to be a message in there explaining what caused it, but to be honest, I'm not really knowledgeable enough to pull it out of what looks like 50% gibberish to me.
http://pastebin.com/315jSBZt
I would be more than happy to provide needed logs or run tests, just let me know what you need. If someone can give me a good answer that is corroborated by someone else in the community, I'll make a $5 donation to the EFF in your honor.
Possible power button issue?
audit13 said:
Possible power button issue?
Click to expand...
Click to collapse
Unlikely. Power button feels good and this phone hasn't really even been used very much. If it's a hardware issue, I think we'll find a clue in the logs. Kernels shouldn't just panic of their own accord, right?
I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?
audit13 said:
I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?
Click to expand...
Click to collapse
Yes, I've experienced this problem on the stock ROM, Cataclysm, and Chroma (what I'm using now).
Some observations that might help:
- Sometimes it reboots more frequently than others. I've had it reboot several times within 10 min. I've also say in front of my computer with logcat running, purposefully trying to make it crash, and for 30min. it didn't do anything. (I got it to eventually, but didn't find anything useful)
- I recently reflashed everything to stock including the bootloader and recovery to see if it would help. I also updated the radio to see if that would do anything.
- It boots up fairly quickly. There are no real performance issues while using the phone
- Before it crashes, it freezes for a few seconds with whatever is on the screen. You can't use any of the buttons or do anything.
- It does not require screen-on or user interaction to prompt a reboot. I've had it reboot while sleeping before and I can hear it vibrate when it hits the "google" screen.
Is there any way to identify the cause of a kernel panic? I assume that the kernel logs what it does or what it's trying to do somewhere. I'd love to be able to pull some intel out of the logs to figure out exactly what's causing it. Any other logs I should be pulling?
Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.
audit13 said:
Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.
Click to expand...
Click to collapse
Good call. That was one of my possible guesses too. I keep looking for evidence of that in the logs, it's gotta leave a trace somewhere! The phone is "certified refurbished" one that I bought off Amazon fairly cheap ($160-180ish). I think I'm just going to flash it back to stock and return it. Not sure what I want to get as a replacement. I might be able to beat my old Moto G (original) back into submission and use it for a while. It had some problems too, and it was worse when it comes to specs, but it was a really well thought out put together device. Never noticed the little things mattered so much until I bought my Nexus 5. I love it, don't get me wrong, but the positioning of the speaker, the slow-focusing camera, and a few other things keep it from hitting 100% for me. It's odd that two phones from the same manufacturer could be so different feeling when it comes to polish. Maybe I should buy a Moto X just so I can experience them all!
I used to have a Moto g as well. It as a great phone until I damaged the sim reader.
Although Google used to own Motorola, the nexus was made by LG which probably explains the different approaches to building a phone.
I'm okay with my lg which is a frankenphone that I clobbered together using spare parts I salvaged from cheap used nexus 5 phones I bought over a period of a few weeks.
Related
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
The issue is real and Google have confirmed it. They've been working on a fix and the official word was an OTA update was going to be released this week:
Just a heads up that our initial tests look good and that we are expecting to send out an OTA within one to two weeks that will resolve the issue. Thanks for your continued patience!
Click to expand...
Click to collapse
code.google.com/p/android/issues/detail?id=13674
silfer said:
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
Click to expand...
Click to collapse
Argh. I did not have this problem until yesterday (had the phone since January). Now my phone will reboot right after a call.
apreichner said:
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
Click to expand...
Click to collapse
I've had three Nexus S so far. The first one I picked up on dec 16th and didn't get a single reboot on - but the oleophobic coating on the screen was coming off in spots so I swapped it for another unit.
The second unit had issues rebooting. I saw it immediately - it rebooted while sitting on my desk. I could constantly recreate this by streaming audio over BT in my car - every 10-15 minutes it would reboot.
I picked up a mt4g for a few weeks to see if they could sort whether this was a hardware of sw issue (that thing is a brick to hold) and eventually picked up a third Nexus S once they identified it as a SW issue. This device has not rebooted a single time in the 27 days I've had it. I can stream audio and make long calls without an issue.
All three devices have operated with identical configurations. Based on this I'd say that some units are worse than others.
Maybe it's issue with the hardware tolerances and some hardware that falls within the accepted tolerance is not operating as expected and causing kernel panics as a result. This would explain why some have this issue constantly and others rarely or never see it. Perhaps it's something seemingly unrelated that everyone experiencing the reboots has in common. It would be nice if Google weren't so tight lipped about this. Supposedly the OTA will address these issues and moving forward it should be irrelevant.
I get this issue at least 60% of my calls (not that i call much). i have made 4 calls today, and 3 of them my phone rebooted during the proccess.
I am returning this to CW tommorrow for a replacment unit, i love the phone dearly but do not want to be robbed for £429 but not being able to take it back if they do not resolve.
It could be a batch issue, or something i guess, but that's not my job to find that out, that's for the people i paid for the hardware/software
I hope i get another unit, and if not problem free at least i can rely on a warranty, hopefully making sure if google slack on fixing this i can get my money back.
If it fixes soon or the new handsets ok, i can keep this lil beauty of a phone
I've had my SNS since launch. My phones has rebooted on me twice. It was right after playing a 3D game. Right after i exited the game the phone rebooted. Funny though, it hasn't happened again.
I've gone back to using my Desire until Google sort this out. For me, any call above 5 minutes has a 50% chance of rebooting the handset.
The handset (running stock 2.3.2 and un-rooted) will on occasion spontaneously reboot as well. Not good.
It is a bug that seems to be very limited in scope but is very serious for those affected. Personally, I've never had it happen to me or my wife.
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
apreichner said:
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
Click to expand...
Click to collapse
Getting the insurance is definitely the right choice. I hope you enjoy your phone and your stay here!
I get periodic reboots on both my phones.
It is not that noticeable, since it often happens when I am not using the phone and unless I glance at it and see the start animation, I may be unaware of it.
But it has happened during a call as well (couple of times on each phone) and then it is definitely noticeable.
I have this bug... not during phone calls but random reboots. 2-3 a day. I hate it but its tolerable.
Weird, I don't have this bug
If flashing a custom rom, the problem will be solved? Since i am considering if i should get Nexus s later on.
Thanks
This is my third device and for 8 days it has been pretty rock solid, Yesterday I had 2 screen freezes and noticed it had been rebooting randomly.(for how long I do not know but I thought at first the app was turning itself off, than learned the device was actually rebooting itself) Today while at a restaurant I lost data and the signal would go in and out. In this same place my Vibrant gets 3-4 bars of 3G consistently. Upon arriving at home I had the same situation but additionally the GPS refused to lock or even see any sats. After rebooting twice it finally straightened out. I only have a couple of days left to decide whether to get a refund or take the chance of getting one that has even more issues or just keep this one and hope for the best. Anyone else have these or issues like them?
Are you running stock? There is a patch that fixes the slow Downs which can cause a reboot.
LG left the device in engineering mode which is why it boots up so fast.
Root and flash the patch, or wait for official gingerbread, or foot and flash CM7 which is doing me good.
LG G2x CM7 2.3.4
http://www.MiiWiiChat.com
http://www.SnapSiteAdmins.com
Yes, my data randomly gets stuck, switching to airplane mode and back fixes it sometimes, otherwise a reboot fixes it.
My GPS randomly dies and gets stuck, usually while navigating, only way I've found to fix that is yet another reboot. Cycling the GPS on and off does nothing.
Also, about once a week, the phone will crater, come back up to "system checking", decide it doesn't like something and do a factory reset! I'm actually scared every time I reboot that it'll come up reset.
Also notice if I make heavy use of the internal SD card, say, 1080p video recording, it'll randomly reboot. Defective memory?
Par for the course until LG figures stuff out. I wish this was like a computer and everything worked when it was expected to work!
Running the dexopt patch, rooted, and nothing else major.
player911 said:
Are you running stock? There is a patch that fixes the slow Downs which can cause a reboot.
LG left the device in engineering mode which is why it boots up so fast.
Root and flash the patch, or wait for official gingerbread, or foot and flash CM7 which is doing me good.
LG G2x CM7 2.3.4
http://www.MiiWiiChat.com
http://www.SnapSiteAdmins.com
Click to expand...
Click to collapse
Yes running stock and applied the patch as soon as it came out. I have not tried cm7 yet. The patch does not seem to do any good for this device.
Lightning Blue said:
Yes, my data randomly gets stuck, switching to airplane mode and back fixes it sometimes, otherwise a reboot fixes it.
My GPS randomly dies and gets stuck, usually while navigating, only way I've found to fix that is yet another reboot. Cycling the GPS on and off does nothing.
Also, about once a week, the phone will crater, come back up to "system checking", decide it doesn't like something and do a factory reset! I'm actually scared every time I reboot that it'll come up reset.
Also notice if I make heavy use of the internal SD card, say, 1080p video recording, it'll randomly reboot. Defective memory?
Par for the course until LG figures stuff out. I wish this was like a computer and everything worked when it was expected to work!
Running the dexopt patch, rooted, and nothing else major.
Click to expand...
Click to collapse
Gosh, sounds like we got the exact same phone!!LOL Almost my situation word for word!!!!!!!!!!!!!!!!!!! Do you really think that software patches will fix all the issues? I would like to believe but am doubtful. I went through the GPS debacle with the Vibrant and it still has not been fixed after almost a year for a lot of people.
As powerful this phone sounds I am hesitant of getting it because of the list of complaints. I think the g2 might be a better choice even though it has an inferior chip
The patch made a big difference with mine. After the patch is successfully applied, it will take longer to boot and won't slow down and laggy after a few hours.
I'm wondering if it was applied correctly? It would have to be applied after every wipe you've done. Thing is you have to remove the X-Factor from the equation. Flash CM7 and see if the problem is persistent or not. If it is, replace the phone. If not, then you owe me $5 cause I called it. There is a weird bug with the stock kernel. We are expecting an updated Kernel with the new Gingerbread rom that is about to be released.
@Jjday7: I wouldn't sweat it. I've been around the block and as far as hardware goes; the G2x is solid. The initial kernel is a little wonky but thank god we have CM7 right? I used my GPS today and had no problem getting a lock and keeping it. Of course I'm on CM7. I also don't have anymore random lockups.
player911 said:
The patch made a big difference with mine. After the patch is successfully applied, it will take longer to boot and won't slow down and laggy after a few hours.
I'm wondering if it was applied correctly? It would have to be applied after every wipe you've done. Thing is you have to remove the X-Factor from the equation. Flash CM7 and see if the problem is persistent or not. If it is, replace the phone. If not, then you owe me $5 cause I called it. There is a weird bug with the stock kernel. We are expecting an updated Kernel with the new Gingerbread rom that is about to be released.
@Jjday7: I wouldn't sweat it. I've been around the block and as far as hardware goes; the G2x is solid. The initial kernel is a little wonky but thank god we have CM7 right? I used my GPS today and had no problem getting a lock and keeping it. Of course I'm on CM7. I also don't have anymore random lockups.
Click to expand...
Click to collapse
I have applied it before and after GB update. I have hesitated flashing cm7 (have a couple of questions) If I do flash it and want to go back to stock or some other rom, would I have to flash a different kernel even with my nanroid? If so what would be the process for that? AS far as GApps I notice that you cannot use the one for tegra. All I have found at the cm7 site is universal which I suppose would be the one to choose. Do you know for sure?I have used cm7 on my nexus one but not on my Vibrant . Any and all help is greatly appreciated.
I also have all the same issues as the OP. Hopefully the update fixes all these issues. Did any of you notice the phone really hot when the reboots and freezes occurred?
Sent from my LG-P999 using XDA App
So where is this patch? My GPS has been non-functional this morning. Usually it just takes a LONG time to lock on. Also, last two days I've been getting the freezing while on a call. Black screen, won't come back, have to remove the battery. Early this morning after taking the phone off the charger was the first time it froze to black screen while not on a call.
Jjday7 said:
As powerful this phone sounds I am hesitant of getting it because of the list of complaints. I think the g2 might be a better choice even though it has an inferior chip
Click to expand...
Click to collapse
To my G2x friends above. Keep swapping phones. Don't give up. I was at my wits end until I swapped out a couple of times. My new phone has no bleed issues and the random crazy stuff has completely stopped.
lilaliend... take it back. get another. It should not do that. It will be nothing but a head ache/heart ache until you do. I get a solid lock within 5 seconds.
Jjday... if you get one, run the heck out of it the first few days to see if all is good. Any issues pop up...swap it.
This is a solid phone that seems to have had some issues with the first run of production. There are many detailed posts on how to fix any minor annoyances. TMobile sold out of them for a reason.
Swap bad behaving phones then read, read, and then read some more. The potential of this phone is awesome. I am a die hard WM guy who has been converted.
So .. I ended up exchanging my g2x in via t-mo customer support since I was out of the window of taking it back to the store (having 4g/wifi toggle issues etc, random reboots). The new phone is by far better, but I am having issues with the GPS still. It will see 10 satellites, all locked on (green via GPS test) but it takes forEVER to lock. When I first took the phone out of the box it locked within seconds inside my house ... should I send this back for another one again?
I posted this almost verbatim to my G+ stream. It says it all, basically, and I don't have time (at work right now) to give a lot of detail but I wanted to get this out there...
----
I received three text messages this morning at 7:25 EDT.
They appeared to be random characters, like when an OS is trying to display characters from a language that requires a codepage it doesn't have installed. They are as follows:
<sisa:68571244:1:1:199:41970681>ezG7k3jzC7mFo6SSm7KUIg
<sisa:65471246:1:1:199:43800551>HE85MqRY33Xf0qmVbaCjyQ
<sisa:65471245:1:1:199:43799818>SpxSbHILo1mHG/EjkMAF2g
All three received at 7:25. I was able to use my phone up to this point because I was able to view the messages normally. Now, suddenly I have no digitizer response. None whatsoever. To use my phone, I have to pull the battery and boot to safe mode then use my trackpad and menu buttons to access certain features.
Now, it seems to me, the first part is like an address packet, maybe including a sequence number. The second part is like what I see when e.g. viewing the output of 'cat somefile.binary' in Linux. At first I thought it was spam from a foreign country, but now I'm wondering if this was some binary code received and interpreted by my phone. I wonder if this is possibly an android virus/remote hack? Is that possible?
I may wind up wiping the phone when I get home and have ability to back stuff up, but this is annoying, to say the very least.
-----------
Now, I did a little googling and it appears that it may just be that T-Mobile was trying to send an update to the phone (maybe the fact I'm on a custom ROM is why it borked). But has anyone had this or anything like it happen to them?
Thanks much in advance,
CJ
Update
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
cj chitwood said:
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
Click to expand...
Click to collapse
My evo **** needs a good smack every now and then when the kb gets opened because it has a bad flex cable. since I'm not with sprint and only test roms on that phone I don't need the kb anymore but sometimes the little one opens it
Sent from my myTouch_4G_Slide using Tapatalk 2
Yep, I'm not so lucky. I need the touchscreen more than the keyboard
Still, was on the phone for 45 minutes today talking with two different reps, and my replacement phone (another MT4GS in Khaki) is scheduled to arrive in three days.
Time to see if I can return it to stock. It's a hardware problem, so what ROM is on it shouldn't matter, but I don't want to give them any reason to balk.
Ok, I've been having some network issues, some of you may know. My service cuts off randomly and im quite sick of it. I've tried everything, nothing will fix it. I dont have an extra $400 laying around to RMA it. So, I am at the last resort. Its been fun, its a good phone, but at this point it really doesnt matter to me if i break it. I can get a moto g for $120 thqt will work like it was ment to. I really thunk its something wrong with the phone, I've never had this problem on tmobile before.
Anyway, im ready to crack this thing open and see if i cant fix it on my own. Maybe a connection is lose or something. I've watched a few videos, looks easy, ive popped my N72013 open so i im not worried.
Now, would anyone have any ideas what it could be? It acts like its a grounding issue, i can do just about anything, but when i download a rom, app, stream a video, anything that maxes out my internet, the service just completely drops, and says "no service" but usually comes back on after a few seconds. Sometimes the whole phone reboots. But, if is use 3g i never have any problems
So, any ideas on what to look for inside the phone? I was gonna unplug the wire for 4G and 3G, inspect maybe dust it off, and plug it back in.
If anyone has any ideas please fill me in. Thanks for your time.
Andromendous said:
Ok, I've been having some network issues, some of you may know. My service cuts off randomly and im quite sick of it. I've tried everything, nothing will fix it. I dont have an extra $400 laying around to RMA it. So, I am at the last resort. Its been fun, its a good phone, but at this point it really doesnt matter to me if i break it. I can get a moto g for $120 thqt will work like it was ment to. I really thunk its something wrong with the phone, I've never had this problem on tmobile before.
Anyway, im ready to crack this thing open and see if i cant fix it on my own. Maybe a connection is lose or something. I've watched a few videos, looks easy, ive popped my N72013 open so i im not worried.
Now, would anyone have any ideas what it could be? It acts like its a grounding issue, i can do just about anything, but when i download a rom, app, stream a video, anything that maxes out my internet, the service just completely drops, and says "no service" but usually comes back on after a few seconds. Sometimes the whole phone reboots. But, if is use 3g i never have any problems
So, any ideas on what to look for inside the phone? I was gonna unplug the wire for 4G and 3G, inspect maybe dust it off, and plug it back in.
If anyone has any ideas please fill me in. Thanks for your time.
Click to expand...
Click to collapse
They don't cash the 400 bucks, they just put a hold on it, I did it recently via a credit card, and the charge was quickly reversed.
I'd recommend replacing it, if you still don't want to do it (because of money), go directly through LG they'll have you send in the device and they'll fix it for you.
What you're suggesting is a last resort when you're out of warranty
Andromendous said:
Ok, I've been having some network issues, some of you may know. My service cuts off randomly and im quite sick of it. I've tried everything, nothing will fix it. I dont have an extra $400 laying around to RMA it. So, I am at the last resort. Its been fun, its a good phone, but at this point it really doesnt matter to me if i break it. I can get a moto g for $120 thqt will work like it was ment to. I really thunk its something wrong with the phone, I've never had this problem on tmobile before.
Anyway, im ready to crack this thing open and see if i cant fix it on my own. Maybe a connection is lose or something. I've watched a few videos, looks easy, ive popped my N72013 open so i im not worried.
Now, would anyone have any ideas what it could be? It acts like its a grounding issue, i can do just about anything, but when i download a rom, app, stream a video, anything that maxes out my internet, the service just completely drops, and says "no service" but usually comes back on after a few seconds. Sometimes the whole phone reboots. But, if is use 3g i never have any problems
So, any ideas on what to look for inside the phone? I was gonna unplug the wire for 4G and 3G, inspect maybe dust it off, and plug it back in.
If anyone has any ideas please fill me in. Thanks for your time.
Click to expand...
Click to collapse
Looks like u are not running stock kernel ? Dose that kernel run westwood or googles default cubic for TCP congestion ? And have u tried restore factory IMG and test ?
drawde40599 said:
Looks like u are not running stock kernel ? Dose that kernel run westwood or googles default cubic for TCP congestion ? And have u tried restore factory IMG and test ?
Click to expand...
Click to collapse
Yes, I've fastboot flashed stock 4.4.4, 4.4.3, 4.4.2, 4.4, tried different kernels, roms, called tmobile numerous times, changed sim cards, gone to different areas in town, you name it, I've probably tried it.
I had a similar problem with my nexus 5 it would be on LTE most of the time but after a few minutes of watching YouTube it would switch to h/h+/3g I did RMA through T-Mobile and this new one hasn't done it if you don't have a warranty your only choice is to replace the antenna or the radio hardware
So you are willing to buy a Moto G but not deal with Google RMA? RMA is free, a hold on your credit card is just that, nothing is charged unless you plan on skipping town with the 2nd Nexus.
Google support is one of the best in the business.They do everything they can possibly do to make your RMA as quick and painless as possible by cross shipping you the replacement device. If you have an issue with Google's RMA then you must have never been forced to RMA something before.
Its not that i have an issue with rma, its just, by the time i save up $400 and they ship me the new one, this phone will be obsolete anyway. The battery life isnt that good, its starting to get lcd bleed, ive read many people go through 5+ device and have the same issues. Im not saying its a bad phone, its the best phone ive ever had and ive had many good android phones im just saying, at this point it doesnt seem worth the time and effort, its like a 50/50 shot that ill get a good one.
Andromendous said:
Its not that i have an issue with rma, its just, by the time i save up $400 and they ship me the new one, this phone will be obsolete anyway. The battery life isnt that good, its starting to get lcd bleed, ive read many people go through 5+ device and have the same issues. Im not saying its a bad phone, its the best phone ive ever had and ive had many good android phones im just saying, at this point it doesnt seem worth the time and effort, its like a 50/50 shot that ill get a good one.
Click to expand...
Click to collapse
It's like you're not listening...
It's a hold, not a charge.
ALSO.
LG (directly) will FIX / REPLACE FOR FREE. NO HOLDS YOU JUST SEND IT IN FIRST.
ericerk said:
It's like you're not listening...
It's a hold, not a charge.
ALSO.
LG (directly) will FIX / REPLACE FOR FREE. NO HOLDS YOU JUST SEND IT IN FIRST.
Click to expand...
Click to collapse
..::FACE PALM::..
Nope... not even going to try anymore
Please dont. You obviously dont get the point of my post.
Not sure if I know the point of your post either, but another option is sending your N5 for RMA first (that way there's no hold on your account at all) and wait for them to send you a new one. You can even buy a moto g use it for the week or two you won't have a phone and return it or something.
I understand that you're trying to see if anyone knows what's wrong but to me it's like a needle in a haystack. You're going to be opening up the device to look for a loose connection, but it could be something completely different. Maybe it's a hardware part that is malfunctioning in which case you would need to track down a replacement. This is why everyone is suggesting you just RMA because, speaking from experience, it really isn't a bad experience at all. If you really want to try and fix it yourself of course you're free to do as you wish since it is your device, but I highly doubt anyone on the forum will be able to say for sure what the problem is.
Sounds like you're in a fringe 4g area like me. A few blocks away I get full 4g. On my block, I get almost nothing. I constantly drops 4g, then picks it back up again.
I get a full lte signal nearly everywhere i go, it doesnt just drop 4g, it drops all service completely
My pixel 7 pro freaked out on me the other day and went black on me when I played a game and didn't come back for over 15 minutes then finally was responding again. Any reason why this happened . Hopefully software and not hardware. Hasn't happened since but still concerning .
Anyone ?
Redbeardkevv said:
Anyone ?
Click to expand...
Click to collapse
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
jaseman said:
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
Click to expand...
Click to collapse
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
EtherealRemnant said:
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
Click to expand...
Click to collapse
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Hmmm
jaseman said:
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Click to expand...
Click to collapse
That's called a hardware defect if the hardware can't cope. Going blank for 15 minutes is not normal.
Hardware hmm and not software?
Redbeardkevv said:
Hardware hmm and not software?
Click to expand...
Click to collapse
What were you playing? If it was a graphically intensive game, I would definitely lean more towards blaming the hardware. It's very rare that a game can actually make a phone that unstable. In fact I can't remember the last time I've had a game make my phone unresponsive.
Roblox with my nephew
Redbeardkevv said:
Roblox with my nephew
Click to expand...
Click to collapse
I've never played that game but their site seems to suggest some rather low requirements so I would be shocked if an ARMv8 processor like Tensor 2 is going to struggle with it.
Android warning screens
Due to the very large number of Android devices in existence, we cannot be certain that all devices will run optimally even if they are running the correct version of the operating system and do not have a Tegra 2 chipset.
We have 2 levels of unsupported Android devices - skippable and unskippable:
Skippable Devices: These types of devices will get a warning telling you that your device may not be powerful enough to play experiences smoothly. This is just a warning to let you know that while your device isn't specifically supported, experiences might still run though they will likely lag a little (or a lot). Tapping outside the warning box will make it go away and the experience should keep loading.
Unskippable Devices: will get a message that informs you that your device doesn't meet the minimum system requirements. This means the device is not able to play experiences on Roblox. This message usually shows up on devices that use the Tegra 2 graphics chipset or a processor older than ARMv7. These kinds of tablets/phones do not support features that the Roblox needs to be able to function. However, users with these unskippable messages will still be able to access all other parts of the app outside of experiences.
Click to expand...
Click to collapse
https://en.help.roblox.com/hc/en-us/articles/203625474-ROBLOX-Mobile-System-Requirements
Yea I was thinking it had low requirements. Maybe bad coding ??? But then again no other app or game has caused that to happen. Sooo. Yea
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
I've had a few wonky screen issues that hard locked my phone. Had one go black, but fortunately came back after holding power down. It once went all yellow with weird shapes/sections. And then just had some freezes with artifacts on the screen.
I'm going away for the holidays so I'll send it back when I get home if I'm still having issues. If you're going away, I'd suggest taking a backup phone just in case. Had mine die the first time when I was visiting my folks out of state. It sucked with no backup.
One thing I noticed is the screen does a fuzzy flash whenever I plug in a USB charger. It's only a split second but it is noticeable. Has anyone else experienced that?
Superguy said:
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
Click to expand...
Click to collapse
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
V0latyle said:
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
Click to expand...
Click to collapse
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Superguy said:
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
Click to expand...
Click to collapse
Yeah, that's definitely a display issue. I'm talking about when the device doesn't work or respond at all, maybe vibrates on power up but doesn't respond to anything, and usually will come up as "Qualcomm Bulk USB" or something when connected to PC
Superguy said:
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Click to expand...
Click to collapse
For sure, active development may or may not have stability issues, it's all a learning process!