Related
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 .
I pasted this in Google's official forum but no reply. Can anyone one here please reply to this?
******************************
Here it goes:
The phone is perfect. Works very well. With a small annoying issue.
Sometimes after calling some someone when I hang up and keep it aside, the screen times out (which is normal).
But later when i try to wake the phone by pressing power button it does not do anything. No matter which button i press the phone lies dead.
Take out the battery and the phone starts working great as if nothing happened.
I have experienced this issue atleast 5 times. I tried factory reset just to make sure any random application is not doing this. But, after couple of weeks the issue came again.
I am not sure if HTC is the only one that can help because I am basically scared that they might screw other areas of phone which are working just fine.
Can this be solved by Froyo? Should I wait for it come OTA?
Also, there can be an application which wakes up phone via trackball but would that help?if no button is responding.
Please help guys!!
Always include:
Carrier:Singtel
Country / Language:Singapore
OS / Browser / build number (if applicable):2.1-update 1 (Unrooted, waiting for Froyo OTA)
Try calling your phone from another line first. That would happen to me on my HD2 (a really awesome phone if it didn't suck ass so bad) and, sometimes calling it from another line would cause it to wake up.
OK
Will try to call from another phone once the issue re-occurs.
Should get Froyo by this week as per google so lets see if that can eliminate the issue.
Just now this issue reappeared. I tried calling my phone with other phone but it just kept ringing, no response on N1.
I tried connecting charger and usb but again phone lies dead.
Pull-push battery and now I am typing this message with same phone.
Still wating for froyo ota.
Guys, pls suggest if someone is facing same issue.
I know Leo Laporte had this problem with his N1. Because the power botton is used for unlocking the phone it is more prone to having issues. Everything on his phone was fine, then the power/wake button stopped working. He pulled the battery and could never get it to boot up again, since the power button didn't work. He called up HTC customer service and they sent him out a new phone minus the battery and back cover. That may be the easiest solution to your problem.
I had that problem at one point, although not so severely. Froyo put an end to it but I have a strong feeling the problem will return since I am starting to notice a ~1/2 second lag between pressing the button and the phone waking up.
I think the problem lies in the hardware/software interaction for the button. Can you try something:
-Plug in your phone to your computer
-Start logCat* on your computer
-Keep messing around with your phone while its still connected (logCat will keep scrolling by itself, displaying the system log - if it doesn't, scroll to the bottom of the log and it should begin auto-scroll)
-Wait for the problem to come back
-Press the power button ONCE and see if ANYTHING shows up in logCat that coincides with you pressing the button.
The reason I say this is that I tried this with my phone (i'm a dev so I had it plugged in at the time already) and when I clicked the power button, although the screen would not turn on, logCat would indicate that the Android system registered the click.
Post the results for everyone, if you would be so kind.
*logCat is part of Android-SDK and can be downloaded from the Android Developer's Resources.
it's most likely a hardware issue with the button itself. 3 weeks ago I had a very similar problem where the button was working 1 out maybe 5 times. I called up HTC and they sent me a new one (well technically they're refurbished but I honestly couldn't tell the difference). I was rooted and everything, but they still didn't charge me for it. New phone is still working just fine.
So give them a try.
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
MSigler said:
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
Click to expand...
Click to collapse
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
maniacx21 said:
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
Click to expand...
Click to collapse
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
musashiken said:
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
Click to expand...
Click to collapse
Ahh. I believe you misunderstand my intention;
The logcat output won't explicitly say that the sleep/wake button was pressed, rather you would see some indication of background [system] activities reacting to the press (you would see 'x many' log entries appear RIGHT when you clicked the power button). There would be no way to tell for sure if you see it after the fact. You would essentially be clicking the button with your finger while staring at the logcat output on your computer. You could not do that with alogcat (from the market) as the [device's] display would be off at the time.
*I bolded alogcat to differentiate it from logcat.
For those unfamiliar, the Android system (and activities spawned by applications) send 'messages' to a sub-system in the Android-OS called logcat. The logcat is used by developers to find out at what part of the program an error occurred while debugging as they can output detailed error logs to it from their app. Logcat also outputs things such as results from OTA checkins so Google can debug the OTA system to make sure it is pulling the correct download paths, ect. This was put in place by Google devs (and led to the public finding out the google server addresses of the Froyo 'test' builds).
On average, there are 2-3 logcat entries added per second when the device is being used, and about 0.1 logcat entries per second when the device is in standby mode. What we are looking for in this case is whether there is a sudden surge of entries when the button is pressed, indicating that SOME part of the Android system recognized the press. The entries wouldn't have anything to do with the button itself, but if the same [few] entries come up EVERY time you press the power button and nothing happens visually, you know something was triggered.
Logcat is a software that runs on your computer (what we want in this case) that lets you view log entries in real time. Alogcat on the other hand, is a software that RUNS ON YOUR PHONE that allows you view log entries in real time.
Let me know if you have any questions!
Do you use a taskiller? Ever since I got burned by a taskiller, I've been wary about them. Not wary enough to uninstall them though.
Not a fix:
But a workaround would be using Trackball Wake to circumvent having to use the power button to wake your device. Especially since you are not running on Froyo.
Greetings,
I'm not experienced with android devices, so i thought i'd ask here first before trying to do anything.
Since a few months ago some weird things started happening to my X8 - random display glitches and blackouts at completely random intervals (sometimes one or even two a day, sometimes it can last two or more weeks w/o an incident, i haven't figured out any relation yet).
Glitches manifest in distorted view on screen - shifted up/down/sideways - or colored graphics artefacts - up to completely bizarre patterns of random-colored pixels covering the whole screen. Weirdly enough, pushing power button as if to lock the screen usually alleviates the issue, sometimes i need to do it few times to remove completely, but it works. Touchscreen works fine, but i need to tap the "right" spot on the screen, not where it's displayed on the screen ("right" as in where the element is when the screen is not glitching).
The other issue (may be related) i'm having with the phone is random screen "blackouts" - the screen goes completely black and the power button cycling doesn't help - but the phone still reacts to screen input (i.e. i can unlock the screen by dragging the slider, launch app, start/stop music playback and so on). I can see the backlight on, so it's definitely screen/gfx hardware issue, not backlight. If i try to reboot the phone, it hangs on either shutdown or boot up. Removing the battery, placing it back and booting the phone up doesn't help - it vibrates as usual, i see the backlight go up, but screen stays black and i can't interact with the phone even if i leave it there for a few minutes (which is more than enough for it to boot up - it usually takes ~30 seconds till full boot). Also the backlight won't go off. It usually helps to boot normally if i hit the phone with a palm on the back side and/or leave it alone for a while. This issue is much more rare (only had it three times), but it puts the phone out of service for a while, so it's an issue for me.
Now, the device info:
Sony Ericsson Xperia X8 E15i
015 baseband
10W44
Unlocked bootloader
Alfs8 kernel (2.6.29.6-Alfs v08a 24/03/2012)
GingerDX v026 ROM
No cpu tweaks done, cpu governor "ONDEMAND", cpu speeds 122-600.
The glitches started when i was still using the older version, GindgerDX v013 with locked bootloader, i have done factory reset and flashed a new version with new kernel (and unlocked the loader along the way), but apparently it did not help fix the issues.
I can't provide and screenshots/photos of the issue because the only camera i have access to at most times when it happens is my phone one and, obviously, i can't use that in this case
The question is: can i still try to fix it by myself (i can do it if it doesn't involve disassembling the phone completely - i don't have the screwdrivers required) by software tweaks or other techniques or should i reflash stock kernel/rom, apply for warranty and hope they find the defect and fix it? I really do like the phone. Or, maybe, you have encountered anything resembling these issues and may shed some light on what's happening.
Appreciate any input in trying to figure out and fix this.
Thank you if you have read all this even if you can't help me, cheers!
1st problem could be 'Screen Cut' issue which is solved using kernel without FPS Cap...
2nd problem usually happens on my phone with miniCM9 3.0.2 but shows splash and boot animation...
Can you see the splash screen and the bootanimation? Because my friends' Xperia Ray has the issue on official firmware... so it could be hardware damage...
Try unlocking the screen then press the power button then press it again...
and also try flashing the stock firmware... If it doesn't work... I think you should live with it...
Sounds like a hardware problem to me. Reflash stock kernel and ROM and full wipe and then flash a different ROM and see it it still happens. If it does I think it is advisable to send it to Sony for repair.
Sent from my E15i using Tapatalk 2
Thanks for your replies, i'll try reflashing the stock rom and see if it still happens.
@Lily48: no, no splashcreen or boot animation, just black screen and visible backlight.
I have the same problem and I checked it many times and my conclusion is....ITS A HARDWARE PROBLEM NOT SOFTWARE..
KASHYAP9 said:
I have the same problem and I checked it many times and my conclusion is....ITS A HARDWARE PROBLEM NOT SOFTWARE..
Click to expand...
Click to collapse
Well, notify me if you find a solution, thanks
Sorry for double post, but this is important update:
My phone died this morning with the permanent black screen syndrome. Until i rebooted i could use it to receive phone calls or even listen to music (i knew where to touch to activate the features). However it would not boot sompletely after restart, even if i leave it for ~hour. Connecting to flashtool showed that it does boot to a certain stage, but no GUI (for user interaction with haptic feedback) available - the flashtool does show that device connected with usb debugging enabled.
I reflashed the stock ROM, now it's apparently stuck in some sort of bootloop - it keeps on connecting and disconnecting. But the screen is still black, with backlight. If i remove the battery, replace it and just connect to pc w/o trying to boot on, it acts normally as if trying to charge - backlight activates for a few seconds if i touch a key and green led is lit, but still the screen is black.
I will RMA it tomorrow, thanks for help, hopefully i'll get a new one, or they'll repair this one so it does not glitch on me again. Anyway it was/is a good phone, i absolutely love it.
Wish me luck =]
Aessaya said:
Sorry for double post, but this is important update:
My phone died this morning with the permanent black screen syndrome. Until i rebooted i could use it to receive phone calls or even listen to music (i knew where to touch to activate the features). However it would not boot sompletely after restart, even if i leave it for ~hour. Connecting to flashtool showed that it does boot to a certain stage, but no GUI (for user interaction with haptic feedback) available - the flashtool does show that device connected with usb debugging enabled.
I reflashed the stock ROM, now it's apparently stuck in some sort of bootloop - it keeps on connecting and disconnecting. But the screen is still black, with backlight. If i remove the battery, replace it and just connect to pc w/o trying to boot on, it acts normally as if trying to charge - backlight activates for a few seconds if i touch a key and green led is lit, but still the screen is black.
I will RMA it tomorrow, thanks for help, hopefully i'll get a new one, or they'll repair this one so it does not glitch on me again. Anyway it was/is a good phone, i absolutely love it.
Wish me luck =]
Click to expand...
Click to collapse
It is a hardware problem and Sony Service Center is the last option you have.. if your X8 is in warranty period.
I did the same and they replaced its display with new one.
Hello, reporting back in:
Just got my X8 back, it really was a hardware problem. They changed the screen now it works as good as new =]
Thanks everyone for support
Hi.
I've own P970 Swift/Optimus Black since 4 and a half year, now with Android 4.0.4.
Lately strange things happen with it.
1. Softkeys refuse to work. They don't react to touch at all. They are lit up correctly by pressing other physical buttons but no function at all.
2. Power button refuses to work. I don't think it is physically broken because it works when smartphone is connected to the charger. It hardly works when phone is unplugged.
3. Screen brightness and other screen settings aren't saved after phone restart. Brightness goes up to maximum on phone startup even when setting up automatical brightness couple of times.
4. Phone refuses to be recognized as mass storage. Last few times I've tried to save some apks on SD card I couldn't do it directly via USB cord.
Phone was hard reset. I've flashed 2.3.4 V20S ROM via Smartflash - no change to the issues. Then I've made full wipe from CWM - no change at all.
Then I've flashed 4.0.4 V30B via Smartflash - no change as well.
I've Kingorooted Swift Black and installed Floating Soft Keys as a workaround for not working softkeys, but it is just workaround, no full function.
Any tips, clues?
EDIT: I've just installed eMMC Brickbug and run memory test with "Congratulations. Test Passed." If you believe that app the memory isn't corrupted, so why I'm still having 4 hard issues?
rafnov said:
Hi.
I've own P970 Swift/Optimus Black since 4 and a half year, now with Android 4.0.4.
Lately strange things happen with it.
1. Softkeys refuse to work. They don't react to touch at all. They are lit up correctly by pressing other physical buttons but no function at all.
2. Power button refuses to work. I don't think it is physically broken because it works when smartphone is connected to the charger. It hardly works when phone is unplugged.
3. Screen brightness and other screen settings aren't saved after phone restart. Brightness goes up to maximum on phone startup even when setting up automatical brightness couple of times.
4. Phone refuses to be recognized as mass storage. Last few times I've tried to save some apks on SD card I couldn't do it directly via USB cord.
Phone was hard reset. I've flashed 2.3.4 V20S ROM via Smartflash - no change to the issues. Then I've made full wipe from CWM - no change at all.
Then I've flashed 4.0.4 V30B via Smartflash - no change as well.
I've Kingorooted Swift Black and installed Floating Soft Keys as a workaround for not working softkeys, but it is just workaround, no full function.
Any tips, clues?
EDIT: I've just installed eMMC Brickbug and run memory test with "Congratulations. Test Passed." If you believe that app the memory isn't corrupted, so why I'm still having 4 hard issues?
Click to expand...
Click to collapse
At 4.5 years, my thoughts are that you've gotten incredible life out of your P970! With hard and soft buttons failing, it's probably time to call it "done" and move to a newer phone. From what other users have reported, once hardware issues start cropping up, more are soon to follow. Anything prior to Android 4.4 (KitKat) is a security nightmare, and any hardware repair will cost more than a replacement phone.
I wish I had a better answer, but I don't.
Hi.
Thanks for the reply. I've just moved to new LG phone last christmas - G3, seems I've done it just in time
I'd like P970 to work just for general purposes of smartphone newbie: calls, sms and simple web browsing. Those are pretty hard with softkeys not working and screen wake up failing.
As I said about power button - it doesn't seem to be physically broken - it usually works - mainly when phone is charged - so that tells me that it's software problem.
Workaround for physically damaged button on rooted P970 wouldn't be hard. I've found instructions about remapping some functions to G button which was rarely used on my Swift Black.
The main problem is softkeys panel not reacting for any touch and I would be thankful of any good clue if it is possible and how to fix it myself without additional cost.
The softkey not responding is a bug introduced in 4.0.4 (I readed this in this forum). It seems there is no fix.
As a workaround I use Ultimate Dynamic Navbar, I prefer it over Floating SoftKey.
If you switch back to an older version of Android (2.3.4) , it should work normally.
As a workaround for the power button, you can change the G button to wake on your mobile from standby.
And try to never have to shutdown your phone (I think you can Power on the mobile by charging it, and disconnect the charger on the first logo (sometimes it work sometimes not, there must be a precise timing)
Also if you use your phone without LockScreen, you can wake it up with any button on the phone (G Key, Vol+, Vol- )
Hello friends,
My situation:
Out of the blue my phone stopped responding to the wake-up action. Every time I lock it, I have to restart for the screen to turn on again. The power button is working just fine, since I can go to recovery mode and use it to select options there. I even installed a somewhat wrong version of the TWRP recovery that would not boot to the main OS, but the power/lock button would work just fine in recovery, putting the phone to sleep and waking it up. I reverted the instalation after so I could boot to the main OS ( Android 10). I tried reinstalling(from an official image of the rom) the full rom, incluing everything from OS to Bootloader, and could not make the wakeup action work again. Once my phone is on, if I lock it, I have to force a restart to turn the screen on again. I even tried sending a direct command to the OS using adb shell input keyevent KEYCODE_POWER and KEYCODE_WAKEUP to no success. Even tough I made sure other common events like opening the camera (KEYCODE_CAMERA) were working when the screen was on, and I bet it was working when the screen was off too, but it would not wakeup the screen and I would not be able to see the camera view finder.
My phone is a Samsung galaxy A30, model SM-A305G, currently in Android 10.
I think I described the problem good enough, but If anyone have a problem understanding it, just let me know and I try to explain it better.
Can anyone help me out here? I tried a lot of things to not success.
Thanks!
I have the exact problem you described, did you find any solution ?
Shalesh said:
I have the exact problem you described, did you find any solution ?
Click to expand...
Click to collapse
flash official ROM with Odin or with twrp
I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?
Shalesh said:
I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?
Click to expand...
Click to collapse
very strange
I made furher research about the issue and here is what i've found.
Some videos mentioned same problem in similar samsung models and they stated that changing the daughterboard that connected to motherboard via screen flex resolved the issue. Other videos reflowed the connector in the motherboard side of the flex.
Also phone not responding the adb power commands while in sleep but responding fine when awake got me thinking there is a problem with a some kind of awake pin of screen. Probably there is a short or a missconnection in that pin. That's why solutions in the videos work I think.
It is definitelty not a software issue because it happens in every official or custom rom except in twrp (which does not put screen into sleep mode according "mScreenState" info)
It is not a hardware issue related to power button. Power button works perfectly fine in recovery, download mode and when awake.
Its a hardware issue that probably about the connection that sends wake up signal which maybe from motherboard side of the connection or maybe daughterboard side.
Not a real solution but I found a app called touch protector which has an option that you can disable the touch and set screen brightness to 0%, basically means normal off state for the amoled screens.
I set double click of volume down to sleep mode for touch protector. Maybe with some keymap editing someone can set powerbuttons function to not real sleep but touch protector's sleep. This will be best software solution.
In the hardware side if the problem is daughterboard it can be swapped easily but reflowing smd connecters in motherboard could be risky for me and I don't want to open the never opened device for not solving the problem.