I bought a MotoX Verizon Dev Version last week.
I unloced the boot loader following these instructions:
motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth
I am planning on travelling International (india) next week. Do I still need to do something for it to be able to use on international GSM?
Also, another general question:
When I on call and turn ON speaker, the screen goes blank after few secs. How do I turn the screen back on? If I click power button it disconnects the call (I set that option on), volume button does not turn it on, tapping the screen does nothing. Any idea?
Related
Hello everyone. I have an AT&T Tilt, and it's great so far, except for two issues:
1) After I end a phone call, the backlight seems to go off and the screen is very dim. Pressing keys does not bring the backlight back. If I power the screen off and on, the backlight comes back on and the screen is at its normal brightness.
2) I lock my AT&T Tilt using the "Device unlocked" area on my home screen, and when I unlock the phone, sometimes it asks for my PIN, and sometimes it just shows the unlock button on the screen. My settings are for a 12 hour timeout.
If anyone can shed any light on possible fixes to these issues, that would be great. Thanks!
mrbofus said:
Hello everyone. I have an AT&T Tilt, and it's great so far, except for two issues:
1) After I end a phone call, the backlight seems to go off and the screen is very dim. Pressing keys does not bring the backlight back. If I power the screen off and on, the backlight comes back on and the screen is at its normal brightness.
2) I lock my AT&T Tilt using the "Device unlocked" area on my home screen, and when I unlock the phone, sometimes it asks for my PIN, and sometimes it just shows the unlock button on the screen. My settings are for a 12 hour timeout.
If anyone can shed any light on possible fixes to these issues, that would be great. Thanks!
Click to expand...
Click to collapse
I have the same issue after a phone call....
Same issue here too... it doesn't happen when on USB-power... and I don't remember it doing this before the security-Exchange policy was forced onto my phone.
http://forum.xda-developers.com/showpost.php?p=1566518&postcount=2
I think this happens coz the phone goes into standby / lock mode during your phone call. Just press the on/off button to turn screen off, and press again to turn on. Now your phone will be responsive again.
Minor bug.
Or you can just scroll the volume wheel to turn it back on.
michi123 said:
http://forum.xda-developers.com/showpost.php?p=1566518&postcount=2
Click to expand...
Click to collapse
thanks michi
thanks everyone for your replies. I will try the StayUnlock application.
I still don't understand my second issue though. If the bug is causing this issue, shouldn't it at least be consistent in either requiring me to type in my PIN or just hit the unlock button? I have set my phone to lock after 12 hours, so it should never ask for my PIN, just the unlock button...
I now see that people have been having the first issue since the Cingular 8125 but I have been unable to find any references to my second issue.
ATT Til and Backlight
When making a phone call, once connected, about 12 seconds later the screen goes dark regardless of the setting on the backlight. I am not using a password, and the only way to get back is to use the power button. using the phone button puts the call on hold
I just recieved unlcoked version of XT1058. But I was amaizing that power button don't turn off the screen. Not only...if the time for display time out finish, the screen try to go black for a second and after this wake up again.
This make the telefone to wakeup on every 15 secconds as my time out is 15 s.
I cannot turn the screen off in any case.
The telephone is stock AT&T branded.
Any suggestions?
kokonai said:
I just recieved unlcoked version of XT1058. But I was amaizing that power button don't turn off the screen. Not only...if the time for display time out finish, the screen try to go black for a second and after this wake up again.
This make the telefone to wakeup on every 15 secconds as my time out is 15 s.
I cannot turn the screen off in any case.
The telephone is stock AT&T branded.
Any suggestions?
Click to expand...
Click to collapse
Well, this is -either- a hardware problem, or a software problem. You can find the "Return to Stock" thread, and flash the entire SBF for your Model/Carrier from here: http://sbf.droid-developers.org/phone.php?device=0
This will replace your entire filesystem, and repair any corruption that may be present. You will be back to 100% STOCK filesystem.
If a FULL SBF to stock does not fix the problem, it is most likely a hardware issue. Hope your phone is still under warranty.
Good Luck.
Thanks, The phone now is on the way back to the seller.
Moto X was bought via Amazon.com from WIRELESS WORKS.
NEVER MORE. The box was not original but some fake, the phone is non workable, the accesories is China made and again no original.
The phone was sold as NEW ORIGINAL XT1053 but comes XT1058 AT&T
After few angry mails to Amazon the seller accpet return and I hope my money will be return.
So watch out even in amazon for tricky sellers.
Best Regards, Nick
I can't tell if this issue is with the specific ROM I'm using, or if it's just a Lollipop issue in general. During phone calls, the screen goes black (as it should) when I bring the phone to my ear, but now with Lollipop ROMs, most of the time when I pull the phone away, the screen stays black instead of coming back on. Normally, the screen would illuminate when I pull the phone away, but now it doesn't always work correctly. This is particularly annoying at the end of a call when I would normally touch 'end call', but now I have to wait for the caller on the other end to hang up before the screen comes on. Anybody else notice this?
I'm running gruesomewolf's GPE version 1 and I noticed it. I can usually just press the power button and the screen comes back on though.
A workaround
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.
Abdou.rk said:
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.
Click to expand...
Click to collapse
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:
One more solution
coal686 said:
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:
Click to expand...
Click to collapse
You can also enable DoubleTap2Wake by using a custom kernel.
Same problem on TMo m7
Last week I upgraded to Android 5.0.2 on my TMo HTC One m7.
Since then when I remove the device from next to my head during a phone call the screen stays black.
This means I cannot use a keypad to navigate a phone menu or to enter a PIN.
I can tap the power button to re-awaken the screen but it takes several seconds to come back - and sometimes stays dark.
This is a mild nuisance if simply trying to end a call but is a major issue if I'm trying to use an IVR (this device is, after all, a PHONE!)
I have run the HTC Function test on the phone and the P-Sensor test runs fine.
Hi everyone,
So my issue is one that I don't see anywhere else, hence this thread. I'm not entirely sure if it's a hardware or software issue, and I'd like your help/suggestions (pls)
If I boot the phone via "normal startup" or whatever it is from fastboot mode, it boots. However, after I get into the OS, if I press the power key to take the screen off, and I press it again to turn it back on, it doesn't turn back on. The phone still operates - it receives calls, I hear all sounds, I can even tap by memory to get to different settings, but the screen won't turn on at all until I boot into fastboot and reselect the normal startup option.
I tried enabling tap to wake via custom kernel, reassigning the volume keys to turn it on, but it simply doesn't work. I get the same issue if I double tap to sleep (the top bar) and then double tap to wake. I don't know what else to try - any suggestions?
I'm wholly ready to just call it a loss (I already have a new Moto G) but it would be cool if I could somehow revive this one. The reason I decided not to use the warranty is because I was pretty sure it had already been voided since my mother dropped it in water. As I said, this may be a hardware issue, but I'm not entirely sure and I'd like your opinions/suggestions?
For reference, it had this issue while on stock as well. It ran the latest update Motorola had sent out. It's the XT1063.
Thanks in advance!
I just recently purchased a Nexus 6 project FI phone that was on sale and have been encountering a weird issue: whenever I lower the brightness down all the way and try to hit the power button to unlock, the lock screen flashes for a second and goes back to black and I'm not able to unlock it. What's weird is it still registers my touches because it vibrates as if I was swiping for my unlock pattern. The only solution to this is to keep hitting the power button quickly until the screen finally decides to turn on.
The build is LYV48h running 5.1.1 and rooted/unlocked
Has anyone run into this issue, and if so what can I do to fix it? My next plan is to factory reset it and see if that helps at all
Thanks for your help!