Related
First off I'm on CM7 RC4...So i got my motorola xoom bluetooth keyboard today and was so excited to try it out. I opened it, got it connected no problem at all (except getting BT enabled, which is something I still have issues with), went to start typing, first sentence perfect, no lag, it was great. Went on to write more, got about 3 or 4 full sentences in (i'm a fast typer) and the keyboard stopped working. It looks like it went to sleep midtyping. Another person who bought this keyboard says he gets a similar (if not exactly the same issue, most likely) problem. Is this common with keyboards? is it something that can be fixed or something with the keyboard not working right with the nook?
One of the major reasons I bought the nook was for BT keyboard support and this is the second one iv'e gone through (the first one was DOA, different brand/product though). I bought this one because it's made for androids, so I thought it'd be my best bet. I've tried fixing permissions and a hard restart, but nothing seems to help.
I've had bluetooth problems since build 19 and am tempted to do a full wipe and reinstall CM7 RC4 fresh and see if it helps. I know many people are still having problem with bluetooth in general (getting it to work even...takes me a lot to be able to get it turned on) and it's still a work in progress, so if this is something that will eventually be fixed, I'll keep the keyboard.
Edit: It seems to happen more in some apps than others...facebook app happened almost immediately, quickoffice I wrote for 5 mintes with no problems, dolphin browser about a minute. Then I let it sit there connected and whenever it comes out of whatever it's doing, it's like it hits the back button and it'll then work again. any advice or information would be appreciated
Does anyone else have this issue? I have a stock Moto X on 4.4.4. I use it at work with a bluetooth LG headset and up until a few weeks ago never, ever had a problem with it. I cant pinpoint when it became to happen, if I had to guess Id say a month or 2 ago, it got to the point where I literally have to keep the phone in my pocket to get a clear bluetooth connection. Now, its to the point I cant even do that. I have to have the phone right in front of me, unobstructed, to get a clear stream. If I walk away from it 2-3 feet it gets terribly scratchy and the audio cuts in and out.
I began to think maybe the headset was going bad. I got out my old Bionic and found I have no issues with the headset. I can walk 30+ feet away with it connected with clear stream. I just bought a car with bluetooth connectivity and also have problems with the bluetooth crashing on the phone, yet my kids phones connect with no problem.
Ive googled the issue and only found a few people that seem to have the same problems. They said it seemed to have happened with the latest update to 4.4.4. My phone shows the last update was August 1. Thats coming up on 3 months ago, that seems a little long ago when the issue first started, but I know Ive been dealing with this for at least 6 weeks. Its possible it has been 3 months.
I have cleared the cache in recovery mode, no help. Short of doing a factory reset I dont know what else to try. One person that had this issue did a factory reset and said it didnt help. So I dont necessarily want to wipe my phone to find out it didnt fix it.
Was hoping the update to 5.0 might fix this, but who knows when thats coming, especially on Verizon.
Any suggestions to this issue?
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Oblox said:
Just curious if anyone else has had similar?
Click to expand...
Click to collapse
I haven't, and I use BT in the car everyday.
Thanks. I'll see if it happens again this week and take mine back if so.
No, I haven't had a single reboot in the 6 days that I own the device.
Oblox said:
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Click to expand...
Click to collapse
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Rebooted again today just in the camera.
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
If i can get a new unit id prefer that so i can see if its just my current one with an issue, even with the pain of having to buy a new screen protector.
Lazaros_K said:
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Click to expand...
Click to collapse
If the factory reset doesn't work, install the Sony Companion software and run a software repair on it. That may fix the issue. Mine hasn't restarted at all in the 24 hours I've had it, even after using Wifi, Bluetooth, installing lots of apps, using 3G and 4G... However, I installed Newpipe via F-Doid and it crashed at least 4 times on me when I left the video I was watching and came back to it.
No reboots. Two days of heavy use.
I factory reset it soon as I received it and firware update poped up.
Oblox said:
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
Click to expand...
Click to collapse
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
mhaha said:
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
Click to expand...
Click to collapse
I took it into a store the other day and they had no stock so i'm taking it to a different one today. The store i went to said it would be no problem though as id not had it long. Its been rebooting still a few times just when sitting in my pocket doing nothing, ive had the must enter pin after reboot message.
Well on the way to store speaking to my wife (also with XZ1 compact) her phone froze mid call and rebooted. When she rang back she said she was showing a software update. Checked mine when parked and i had it too.
Sony rep happened to be in store today so told him the issue, he had one himself and hasn't experienced or heard of this but said to do a repair with xperia companion to clean flash the new firmware on both our phones. If still having issues then theres nothing more we could do ourselves and bring back to store to swap.
I have another week in which i can change phone or another 3 weeks to swap for a new XZ1 compact.
Will do repairs tonight and hope the problem goes away.
Repaired friday evening, phone rebooted randomly again after freezing sunday. Taking in today to swap for a new unit.
If any similar problems this week with the new one ill ask to swap to a different phone entirely.
Probably need a software update. Mine is running fine on 47.1.A.2.324
Sent from my G8441 using Tapatalk
No i updated that on friday before repairing and the repair had that version too and it still rebooted sunday and today.
Me and my wife got a new unit now so will see how these ones go.
got my first reboot today after plugging the headphone... weird...
profyler said:
got my first reboot today after plugging the headphone... weird...
Click to expand...
Click to collapse
Not good if others are getting this too, lets hope it was a one off for you.
So far just setup and listened to music on my new phone and all is good but there's no pattern to what causes the reboot so will see how the next few days go.
My XZ1 Compact also has the reboot-issue...
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
flyhigh79 said:
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
Click to expand...
Click to collapse
Difficult to tell. A hard reset might help but it could also be a problem with Android 8 on xz1 that wasnt very well optimized..
Id get the handset replaced, 'repairing' didn't do anything for my issue. Only time will tell if my new handset has the same issues and same for you.
Well this morning I got in the car to go to work and went to turn on bluetooth. Tried OK google no response at all, went to manually unlock and it sat on the lock screen my finger prints not working and wouldnt swipe up for PIN entry. Mic and camera toggle reacted to swipes but didnt do anything. Then it rebooted.
Bye bye Xperia XZ1 Compact, the potential was there but rebooting and dodgy camera is too much to hope for a fix for.
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.