Database Develop

Powering X1i through USB -- any hacks to do the following...

Hi all,
I frequently charge my X1i through USB. There are 2 problems with this method, however.
1) The device goes into USB drive mode, disabling my SD card apps (I keep them on SD card AT ALL TIMES due to frequent backups/restores)
2) Screen does not turn off! while connected to computer! The screen only dims, but does not turn off.
WITHOUT resorting to a) plugging into wall outlet b) connecting to Activesync, is there any to fix these behaviors?
Thanks!

just let it go into activesync mode, that way you can still access your files on your phone and micro sd card from both your pc and phone. And if you dont like the screen not turning off, they just change the settings or just press the power button, to shut off the display.

I know about the power setting, but when your computer is connected to the computer via USB, it refuses to turn off the screen (only dims it)

what? one simple button press and the screen is off. the device is still visible to the pc. I do it all the time - r3a generic uk rom.

in power options u can set after what time it disables screen... default is never

what? one simple button press and the screen is off. the device is still visible to the pc. I do it all the time - r3a generic uk rom.
Click to expand...
Click to collapse
Weird. When I'm connected to Pc, it dims the screen, it does not shut it off. Also, it does NOT auto-shut of screen after the 2 minutes specific in the Power options

You can also use "safely remove devices" to disconnect the data connection from the phone, it'll still charge.

There's nothing we can do AUTO. But like said before, a simple pression on the power button will do it, or you can use My Mobiler and press F11 on your PC.

stisev said:
Weird. When I'm connected to Pc, it dims the screen, it does not shut it off. Also, it does NOT auto-shut of screen after the 2 minutes specific in the Power options
Click to expand...
Click to collapse
Yep, I've had 5 different WinMo devices since '05 and they all worked as expected except the X1. I like to use it as an MP3 player at night, Pocket Player has a sleep timer built in so I just like to leave it running as I drift off most nights. But if I do anything, change the volume, rewind, anything at all the screen comes back on and stays on until I hit some other button to turn it back off. All my other devices obeyed the settings you set in the Power tab, but not the X1...
I'd very much like the screen to auto-off if I tell it to while on USB power. It's not only wasting power, but it wakes me up and gets me fumbling for the tiny power button at 2 in the morning. Any fix would be greatly appreciated.
Thanks,
Peter
I bumped up thread: http://forum.xda-developers.com/showthread.php?t=561832 Since it has a better title and shows the exact same unresolved issue...

Reg Fix
Adding this potential fix here as well so anyone subscribed to this thread sees it.
Ok, I think I have a fix for this. I googled around some more and found that this might be an HTC problem more than an SE one. There were various registry keys people suggested to try to fix the 'backlight problem' - which may or may not be related. None of those suggestions seemed to work, but I kept changing keys myself and eventually found this seemed to do the trick.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\ACUserIdle: 120
I confirmed that changing this value affects the amount of time before my X1's screen turns off - but my MP3s still play with the screen off and my phone wakes on receipt of a new call. This value is the # of seconds before the screen turns itself off (in this case 2 minutes). You do need to soft reset for the change to take effect.
This doesn't seem to be posted anywhere else that I've found doing this to fix this issue issue - I changed a few other registry keys as well that might be enabling this fix. So anyone with this problem, please do give this a try and if it doesn't work I'll post the other keys I changed as well - and if it does then post to say so and we're good
Peter
Update: I tested it also while hooked up to the computer and it does work with the phone accessible through active sync with the screen off and the battery charging (faster now that it isn't competing with the screen for power, except for the 2 minutes before it times out). If I want to use it I just click a button and the screen stays on till I leave it alone for 2 mins and it remains off. Get a call or a message and the screen goes on for 2 minutes and then off - Exact same behaviour on AC and USB - exactly the behaviour I wanted .

Can receive calls, texts, but will not wake from sleep and no home screen.

Hello everyone. I have had my Droid Bionic since day one and I have never had an issue with it. It has been wonderful.
Until today. I am on the stock OS. I had a Live Wallpaper that showed a little Android figure that melts based on the percentage of my battery. I went into my Gallery and clicked on "Set As Wallpaper" on an image I took with my camera on the phone.
At the bottom of the phone, a small popup showed up that said "COMPLETED". When I went to the home screen, there was no wallpaper in the background. It was just black, though the icons were still there and it was responsive. I thought maybe the image was corrupt, so I went and tried another image.
This caused the phone to reboot. When it rebooted, there was a notification bar, the time, the lock screen, and a thing that said No Signal. I tried to unlock it, but the phone was unresponsive.
Then I got a text message, even though I had no signal. The notification light was blinking. I could not unlock the phone. I hit the sleep button, and it went to sleep. I tried hitting it again, and it would not wake up.
I tried pulling the battery and putting it back in, and now it won't properly boot. Right when it boots, it goes to sleep (the little shutdown animation). I texted myself from my sister's phone and the notification light blinks, the phone vibrates, and the screen turns on and shows I have a text on the notification bar. The screen and the buttons are completely unresponsive, however.
I tried calling myself from my home line and I could pick up the call just fine and end the call. I could not, however, go back to the home screen while on the call. The capacitive buttons on the bottom were completely unresponsive. When I hung up the call (by touch), it went to a completely black screen with the notification bar showing that I had some text messages and the time and my service, etc.
I have rebooted the phone five times now by removing the battery and it keeps going to this. I have never rooted the phone (I wouldn't even know how to) and I am concerned because of all of the information that I have saved on the phone.
Yes I have tried removing the SD card. Didn't help.
Any suggestions? :/
UPDATE: Now the phone doesn't even boot, it gets stuck at the Red Eye spinning logo. It vibrates twice and the notification light begins blinking, meaning it is letting me know that I have received text messages... but it isn't actually booting to the Android home screen. Really strange...

You should fxz back to stock
It will wipe your application data but not you're sdcard info or internal storage
Sent from my DROID BIONIC using xda premium

Hard reset using all three external buttons
Try doing a hard reset - it's one of those things they only tell you about at the Verizon store when you're stuck:
Once you have the phone on and at least responsive, press and hold BOTH volume keys, then hold the power button down for 10 seconds (it's really about 6, but 10 will do it for sure). This procedure can also be done to force a reboot when you load a gnarly application that sux and locks your phone up - without having to disassemble everything and pull the battery.
Hopefully with any luck, you're phone will do a back-flip and come up!

Nexus 4 Screen Wouldn't Turn On

Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.

efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?

apollohay said:
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
Click to expand...
Click to collapse
it was at ten percent brightness and the screen was completely unresponsive as far as i could tell. doing the power + volume up press made it reboot and return to normal.

efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.

kingwaffle said:
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
Click to expand...
Click to collapse
exactly the same here. felt like i had dropped a baby on it's head haha. i wish i knew a way to figure out what caused it.

My wife and I have been having the same issue, and I'm surprised that there's not more reports of this behavior The worst part is that I use my phone as an alarm, and the alarm won't go off if this happens in the night.
It has happened to me 3 times now, and 2 times in one day for my wife. Holding down the power button for ~20 seconds will cause the reboot, which is the good news. This morning after holding down the power button I noticed the notification light flashing red.
The phone appears to be still on, because if it happens overnight I will still see the white notification light flashing even though the screen won't turn on.

I had this problem on faux123 kernel on the second day after I got my Nexus 4.
Doesn't encounter it on franco.Kernel...

Sleep of death brozillas! Happens to all android phones. Happened to all my phones listed in my signature. You can reboot the device and you should be good. For the dude that's missing his alarm you should do a factory reset if you are stock or if you have root do not set your min cpu values to less than 3xx MHz.
Sent from my Nexus 4 using xda app-developers app

Same thing happened to me on my N4. Did a hard reboot and it came back on. Has happened at least twice since then, usually after being plugged in.
Sent from my Nexus 10 using XDA Premium HD app

Change chargers, cables. Make sure the charger is 5v 1.2a. Factory reset to stock.
If all that fails, RMA if you can.
Sent from my Nexus 4 using xda

I observed the same issue (going to standby, then cannot switch on within an hour) with my [just bought] Nexus 4 (latest 4.2.2 firmware OTA updated, nothing special in setup, second day of use).
Certainly must be difficult to say if it's hardware of software (that is, JB/drivers, since I cannot see how such issue can be caused by any virtual machine application) and when/if the latter will be fixed. I have another such great device already -- ASUS TF700 transformer, with similar "everything works, just reboots occasionally", which I think is enough for me
As with the ASUS Transformer case, I have trouble understanding: if it's the issue with all devices/firmware, although not too frequent -- then why everybody does not complain/return the units massively: the phone is pretty unusable if it cannot be relied upon. If it's just some isolated cases with particular units -- then what happened to QA/testing at LG...
So I guess I am going to return it while I can.
Too bad, good model otherwise, will have to see other phones or wait/observe.

My point is, I understand: fairly new device, can have quite a few faults to be fixed later -- now everybody seem to work that way, for better or worse.
It can have more or less beautiful (or ugly) designs, more or less features, larger or smaller batteries/working time; it can have problems with data connectivity, it can have better or worse browser (or the lack thereof completely). I'm fine with the lack of text reflow in Chrome although that was surprising.
One thing a phone/communicator/PDA absolutely cannot do, provided its battery is not empty, is going into "sleep of death"-like states -- it just cannot serve its purpose then, I cannot see how people sell it at all...

I have had a similar issue before, but i have experienced it when my phone has been through one of 2 sets of scenarios.
1 - It gets really warm and the screen becomes unresponsive, dead if you will. The hard reboot fixes this.
2 - When the signal to my phone is sporadic. An example of this would be my recent trip to London. I was on the underground quite a lot, and I'd lose signal quite often whilst travelling. On a couple of occasions i had to reboot my phone the hard way to get it going again.
Hope this helps?

In my case the device was lying near me on the sofa, the time between its going to standby and my attempt to switch it on was something within 1 hour. Nothing especially intensive had been done before.
BTW, while the phone was in that state, trying to call it resulted in long tones, i.e., apparently the radio/cell was online.
Hope this will help somebody, I returned mine.

Good evening. First post but long time lurker. My N4 is unrooted and on 4.2.2. I'm troubled with this as well especially so when the alarm doesn't ring in the morning after it's crashed overnight and I'm late for work!
Not sure if this is relevant though. I don't listen to music frequently on my N4 but the 3 times it had crashed overnight I had been listening to music before going to bed. Twice using Google music being streamed via my home wifi and once using poweramp with music on internal memory. I remember on 2 occasions the phone feeling rather hot as I was plugging the charger in as I was about to turn in.
I suspect there's a process that's causing the the phone to overload/ overheat and then switch off as a result. Because it's plugged in, it'll just continue to charge overnight and present you with a 100% battery in the morning once you've got it to reset again.
I have also found that doing a soft reset before going to bed prevents this from happening.
Just my observations.

Hi all, I got my Nexus 4 a week ago to replace a broken HTC One X (The cost of repairs was almost equal to the cost of a new Nexus 4). Since I got it, SoD happened twice, both times when I left it to charge overnight. The weird thing is that I have this LED application that blinks the notification light when charging with screen off. When I unplugged the phone, the LED was still blinking as if charging, so the phone is definitely not dead. I will try to set it to day-dream while charging and see if it helps. If it does, it might be considered a way of Google encouraging developers (like myself) to create more daydream apps .

Good morning from beyond the pond,
had the same thing happening as described in the first post solution (pressing POWER+VOL UP) helped to reboot my device.
Only thing that was showing was the led, flashing a blueish white light.
Now runs again on rasbeanjelly. Thanks to OP.
EDIT: since this happened the first time, I thought about what I had altered in my setup.
Only thing that was new was "Greenify". Maybe it sent the APEX launcher into standby?!

Having same problem on my 1 week older n4, my friend having the same problem . only thing in commune we have is the WHATSAPP app that once the phone restart it give a notification that the phone date is wrong,once I look at the date settings yes it is wrong, it says 1970 ,so I have to reset it. It does it every time the problem happens ,can this be a clue???
Sent from my Nexus 7 using xda app-developers app

guinnes.s said:
it says 1970
Click to expand...
Click to collapse
UNIX equivalent of Pol Pot's year zero

I'm having similar problems.
The first time I believe it was just an issue of slight overheating. I turned off the screen but left Google Maps running & put it in my bag. It didn't actually turn off, but the screen didn't want to come on when I took it out later. I did notice it was hot, and after it cooled for a couple mins, it worked fine again. I haven't done this again, and so far, so good.
However, now, on occasion the phone won't respond to the power button. I've never had to actually do a reset - it will eventually decide to work after a couple of presses.. but when it does, it will be slow to come on. The screen will be backlit (but black) for a few seconds, then it will load and respond as normal.
Since the light comes on prior to the screen, it seems like a software rather than hardware issue to me. If the screen was damaged, I don't think it would act that way. I don't know phones, but that's my intuition. I'm going to try and remember to turn it off on occasion and see if that helps. I don't think it's been reset since the last push update.
(I'm rooted, but stock)

Help! Moto X (XT1049) Constantly Freezing and Restarting Itself (RW)

I purchased a used Republic Wireless Moto X (1st Gen) and in the beginning I was happy with the phone, but then I got to school with it...
The first thing I noticed was the issue the phone was having with the college's network. The network requires a one time login every 10 hours to authenticate that you are a student. I would login and the phone would work normally on the school's network until it turned the screen off or I hit the power button once to sleep the phone. Once you did this and then tried to use the phone again it was like there was no network even though it was connected and already authenticated. I am forced to disconnect from the school's network and reconnect every time I want to use WiFi if the screen was turned off...
Well that problem was annoying as hell, but it got even worse as time went on (2 weeks). Now I can barely even use the phone at all on campus or sometimes even at my own house. I will be trying to do something very simple like open txt messaging and it will show my messages and then load the names to match the cell numbers (slowly). However when I click on a message it will stay stuck at a white text body with the person's name at the top and a txt enter box at the bottom that I can't do anything with (keyboard won't pop up).
If I hit back normally it will freeze the phone and it will restart, this is my primary problem. When trying to do basic things like txt messaging the phone freezes and restarts itself. Once it restarts on its own, nothing has fixed. I try to open txt messaging again and I get the EXACT same problem and the phone will restart again. The only semi-solution I have found is once the phone restarts itself, I shut it down through the normal hold power button briefly and click power off. Then when it comes back up, SOMETIMES it will act normal-ish.
The odd thing is a lot of the time once I get home on my network these restarts and freezes are much less frequent vs. on the school's network. This could be a coincidence, but I thought I should bring it up.
-------------------------------------
This is my first smartphone I have ever owned, but I have owned two tablets so I am familiar with Android and also with modding Android (rooting, boot loaders, custom ROMs, etc). If modding is the answer here then by all means tell me what I need to do so I can get a phone that functions properly.
I saw that Motorola is testing 5.1 for this phone now, perhaps that may fix these problems? Right now I am tempted to throw this phone out the window and go back to my flip phone that I can at least txt message on.

Not even a single idea?
Edit, found this:
http://www.androidauthority.com/moto-x-problems-528956/
Some users have faced problems with the device freezing, or randomly rebooting occasionally.
Potential Solution –
If the screen is frozen, tapping on the power button to turn the screen off, and turning the screen on again might unfreeze it. If that doesn’t work, a long press on the power button will reboot the device.
The likely culprit for this issue is a specific application. You can follow the instructions in Problem #4 above to find out if this is the case.
Click to expand...
Click to collapse
and
https://community.republicwireless.com/docs/DOC-1965

Black Screen, won't do anything.

Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?

Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..

Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.

Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?

Buy a new one. Send yours in as defect. Done.

erase111

I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!