So my Moto G just showed up. [emoji1]
I am thinking before I insert SIM or restore any data, should probably fire it up, skip all the setup, and let it OTA to the current firmware... Then factory default and start clean. Any reason not to do that or other thoughts?
Sent from my Nexus 4 using Tapatalk
Odd... it shows that the software version is up to date, but the firmware is .44, I assume I probably need to charge fully first, the battery is at 47% out of the box?
Or do I need to add my Google/Moto account before it will get an OTA update?
EDIT: Nevermind, it must be current... After installing tempered glass screen protector and moving SIM, reinstalling apps right now. Really liking the display over my old Nexus 4.
Related
Unrooted, Stock.
Everytime I try to unlock, it sits there and looks at me like I am stupid. The only way I can unlock is to restart the device and then only on first time will it unlock. I have tried wiping cache, and a factory reset in the stock recovery, any ideas?
EmerikL said:
Unrooted, Stock.
Everytime I try to unlock, it sits there and looks at me like I am stupid. The only way I can unlock is to restart the device and then only on first time will it unlock. I have tried wiping cache, and a factory reset in the stock recovery, any ideas?
Click to expand...
Click to collapse
sounds like your touchscreen is failing. Mine would do this too. It would work after restart until the screen timed out or it was locked. After that the touchscreen would no longer function. I returned mine for a new one.
That is what I was afraid of. Just had Amazon send me a new one.
This is a new feature they put in so that they don't infringe on Apple's innovative patent
Sent from my GT-N8013 using Tapatalk 2
EmerikL said:
Unrooted, Stock.
Everytime I try to unlock, it sits there and looks at me like I am stupid. The only way I can unlock is to restart the device and then only on first time will it unlock. I have tried wiping cache, and a factory reset in the stock recovery, any ideas?
Click to expand...
Click to collapse
Sorry to hear. Mind if I ask how long ago you got it from Amazon?
I ordered it on launch day. Got it the Friday after that.
Unlock
You did not say if it's not unlocking with the stylus , or finger .
I had some trouble with stylus but it went away for no reason , but this is what I discovered :
At some point my screen was not responding regardless if I just rebooted it or if I used rubberized stylus , finger or original pen .
Then when it came back on , I changed settings in " PEN " for pen sensor to be disabled . Well the sensor is NOT disabled , but when I pull the pen out my screen does not work . I put the pen back and it works . If the sensor is enabled , when I pull the pen out screen does not respond even when I put the pen back . I have to reboot it . So I was gonna take it back to worstbuy ( bestbuy ) and exchange , but I see that other peeps have same problem so I decided to keep it and start updating and installing apps on it . Next day I forgot that pen does not work and I pulled it out , screen comes on , I swipe pen and start doing this and that and I realized that pen works . Somebody on samsung or xda will figure it out and fix it .
No it is not responding to pen or finger input.
Sent from my ADR6425LVW using xda premium
I had the same exact issue with my tablet! IT just stopped responding unless you would restart it but as soon as it went to sleep it would be unresponsive once again. I had mine replaced by Best Buy. I hope this doesn't turn out to be a common issue and 2-3 months from now I'm dealing with this and RMA issues.
I had the issue right after the update. I think that is the cause. I exchanged mine at Best Buy. I made sure to not update again. Not long after Samsung pulled the update.
Now my S Pen is done. Thank God my replacement will be here today.
ImMendota said:
I had the issue right after the update. I think that is the cause. I exchanged mine at Best Buy. I made sure to not update again. Not long after Samsung pulled the update.
Click to expand...
Click to collapse
I hope you're right but my unit didn't start messing up until 3 days after I did the update. I did notice that when I got my replacement unit that there has not been an update so you are correct in that the update has been pulled by Samsung. I know I will feel much better in knowing that the problem with my first unit was software related rather than hardware related!
I'm on a business trip and have brought my Note with me which is in a cover and carried in the notebook slot of a backpack. Once I arrived I noticed the tablet, though on, appeared to be locked up, no response to touch or pen input. Forced a restart and touch stated working until I pulled out the pen and then everything froze again, including touch. Tried this several times with the same result. Did a factory reset thinking something got messed up with the software which is invoked when the pen is pulled but no help. Something has happened but to what I don't know. Was thinking about returning anyway for a 32gb version so now I guess the decision has been made. Still curious as to what happened so I might avoid it in the future....
One more thing. In the notebook compartment I also had my series 7 slate which also was in it's own cover as well. I can't see where that could have been a problem as there was plenty of room in the compartment. I guess having another semi hard object there may have stressed the screen of the note but that doesn't seem likely.
Sent from my SCH-I535 using XDA Premium HD app
Yep, some of us have had this problem, the exact same problem. I am returning mine to Amazon and receiving a replacement. I don't know if the update has anything to do with it or not, but I am going to keep the update off of it for a while to see if the problem happens to my new one.
I've had the update loaded since the day it came out, what a week ago or so. Wasn't a problem
Sent from my SCH-I535 using XDA Premium HD app
Same exact thing happened to my 1 week old note. Did the reset and still the touchscreen would not work correctly. Crazy thing with mine I could force a restart just as it came back on the touch screen would work fine until I let the screen turn off then it would not let me unlock. Had to return it.
Sent from my GT-N8013 using Tapatalk 2
Me too. I got my second unit last Friday and no problems yet but no update available either. It seems that Samsung pulled the update for some reason.
Hello,
Yesterday at lunch I dropped my droid Razr HD on the floor, and broke the screen and digitizer outright.
The screen is unusable, however the phone appears to be working. I can get text messages and see the LED blink.
I am going to verizon today to purchase a new one, be it under warranty or not, because I need my phone for work.
Right now I am keeping the phone on the charger so verizon can transfer whatever they can.
My question is, is there any way I can copy over or "clone" the phone over to the new one?
As if nothing ever happened?
I am rooted, however the screen is unusable. I intend to buy the exact same phone.
I don't want to use anything overly complex if I don't need to. I just want my new phone to look like my old one.
Any help/tips/advice is really appreciated. I need my phone back ASAP.
I will have a stock Droid Razr HD along with my broken one today around 8:00 est.
Thanks in advance!
Samg381 said:
Hello,
Yesterday at lunch I dropped my droid Razr HD on the floor, and broke the screen and digitizer outright.
The screen is unusable, however the phone appears to be working. I can get text messages and see the LED blink.
I am going to verizon today to purchase a new one, be it under warranty or not, because I need my phone for work.
Right now I am keeping the phone on the charger so verizon can transfer whatever they can.
My question is, is there any way I can copy over or "clone" the phone over to the new one?
As if nothing ever happened?
I am rooted, however the screen is unusable. I intend to buy the exact same phone.
I don't want to use anything overly complex if I don't need to. I just want my new phone to look like my old one.
Any help/tips/advice is really appreciated. I need my phone back ASAP.
I will have a stock Droid Razr HD along with my broken one today around 8:00 est.
Thanks in advance!
Click to expand...
Click to collapse
Use philz, you can use the keys & the screen shots from the main thread to judge you presses. That is if your boot is open.
If you are locked-boot. You are done.
You could also try and replace the screen on the phone yourself?
Sumanji said:
You could also try and replace the screen on the phone yourself?
Click to expand...
Click to collapse
Digitizer is broken as well.
Screen (LCD + Digitizer) is available on eBay/Amazon for about $100/120 and is very easy to replace it
Enviado desde mi HTC Explorer A310e mediante Tapatalk
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
MarkMRL said:
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
Click to expand...
Click to collapse
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Aronuser said:
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Click to expand...
Click to collapse
My phone is completely stock and I still have these weird reboots. Before I do another factory reset I'm trying to understand if other people have them (and then not bother with a factory reset because that would mean it's a firmware issue) or if I'm the only unlucky one who keeps getting them. Anyway, I was considering getting my phone serviced, I noticed the glass is a bit misaligned and I have a dead pixel, I called the service center and they said both issues are covered by the warranty. Might as well add random reboots to the list, maybe they'll get me a refurbished phone, mine has a few marks on it.
I factory reseted my phone and then sent it in for repairs, most likely got a refurb too since this one looks brand new, and I still have those "system incidents" happening early in the morning when the phone is just resting on my table.
I don't like begging for replies but please if you stumble upon this thread just drop a line saying if you have them or not. At this point I can't be the only one.
Also I'd like to know if there is any way to consult a log or something that would tell me why it happened.
I used to have them on kk, but they stopped. Mine would only happen at work, which led me to believe it was network related somehow... As if a spotty signal was heating up the phone or something. They stopped as randomly as they started.
Sent from my SM-T700 using XDA Premium HD app
I factory reseted my phone again after messing with the concept rom, and guess what, not even one day passes and the piece of crap reboots out of nowhere like always. I'm so mad right now, I only have 3 thirdparty apps installed, poweramp, the app from my mobile data provider and waze. I will start to try and get rid of this phone now, this is absolutely ridiculous.
I have exactly the same problem. Started after installing LP. Had someone found a solution?
Sam
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
robogo1982 said:
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
Click to expand...
Click to collapse
Dude, read the post again. It's happening on stock lollipop with literally no mods installed. I kept the concept rom for 5 days and it was absolutely stable for those 5 days. Stock lollipop reboots at least once every 10 days, but usually twice.
Here's a recap: I had the phone for quite a while now, I don't remember if I had reboots on KitKat, but I definitely have had them for the past 2 months or so. Meanwhile I got my phone refurbished because I had a dead pixel, it was already rebooting when I sent it in, got it back factory reseted and hardware refurbished and the reboots continued once I started installing all my stuff. Now I installed the concept rom to check it out, went back to stock lollipop with a full factory reset via PCC and after a day with pretty much nothing installed I had another reboot. The only thing that was kept during all this time is my 16Gb Class 3 SanDisk SD Card and my WIND (IT) nano sim card. I've decided to buy another SD Card anticipating the Android M memory unification feature, so I bought a Class 10 uhs3 32Gb SD Card from Kingston (which by the way isn't reaching anywhere near the declared speeds of 80/90mb/s, it only reads and writes at around 35 on the phone, I made a thread about it, maybe the phone itself can't read that fast), and I've been using it for a day now. I had no reboots yet but I had some weird app incidents under diagnostics, one from photo analyzer service and one from backup and restore (I hope they happened when I was still messing with the memory card in and out, because I didn't use any of those apps).
Here's a thread I made on the official forum:
https://talk.sonymobile.com/t5/Xper...oubleshoot/m-p/1057964/highlight/false#M26160
By the way, I still don't know if these reboots are rare or if everyone has them. Too few people have commented on whether they have them or not, while this thread has 447 views. If even 10 people commented saying if they had reboots or not I'd be able to rule out glitchy firmware. A friend of mine has the Z3C and he said he has no system incidents and his phone never rebooted.
Still getting soft/stealthy reboots
After doing a complete repair via pcc, I did not put a SD card back in my phone and only installed my google account and apps... No 3rd party apps. It goes for a couple days and then starts doing a reboot usually once every charge and mostly in the morning. The battery usage graph shows a pretty significant gap as if the phone was off but not completely off. Then I find system incidents in the diagnostic app but it only gives me the date and time of when it happens. No other information. Kind of useless if you ask me. This has all started after updating the official LP build . 200 firmware. Sony needs to investigate this became it's happening more and more for people on 5.1.1
I have a locked bootloader, stock kernel, rooted, xposed, dual recovery, tricked out rxz experience ROM with 85 apps (it includes 17-19 xposed add-ons) in addition to 102 system apps, no random reboots at all. I keep an eye on phone diagnostics, system status (temperatures, etc.) like a hawk.
So guys if this happens at you at stock rom , my suggestion is ask the service for replacement maybe.
Sent from my D6603 using Tapatalk
I am currently doing a test after repairing via pcc, installing a new Google acc, only important updates to apps I use that come pre-installed. So far it's been 5 days and no soft boots or incidents in diagnostics. Although it means nothing because usually after about a week or so is when the issues come back after doing a full repair or factory reset. I guess time will tell. Otherwise everything seems to be working great, especially battery life.
My phone's screen was broken. So, i went to a shop and the repairer installed a new one. The phone was working fine. I updated it to Marshmallow but it has some brightness issues. So, i decided to downgrade it. I flashed my phone and after flashing, when i restarted it, my device is showing white thick vertical lines and then my device turns off. I tried re-flashing but still i have same issue. I cannot buy a new one as i am a uni student. I need help. it has almost been more than a week and i am without any smartphone lol. Kindly help me. Thanks! I have OPPO A39.
umer.khan said:
My phone's screen was broken. So, i went to a shop and the repairer installed a new one. The phone was working fine. I updated it to Marshmallow but it has some brightness issues. So, i decided to downgrade it. I flashed my phone and after flashing, when i restarted it, my device is showing white thick vertical lines and then my device turns off. I tried re-flashing but still i have same issue. I cannot buy a new one as i am a uni student. I need help. it has almost been more than a week and i am without any smartphone lol. Kindly help me. Thanks! I have OPPO A39.
Click to expand...
Click to collapse
Probably because the replacement screen wasn't the exact same model as your original screen, meaning that the repair shop probably had to flash a different kernel or a modified kernel to make the different screen work with your stock software and when you updated to Marshmallow it probably flashed your stock kernel(the kernel that would have worked with the original screen but not exactly right for the new screen). If that is what they did, you might need to flash a different or modified kernel to fix this.
Sent from my LGL84VL using Tapatalk