I've noticed many people complaining about a screen of death (SOD), hang ups and all kinds of problems with their Sony Xperia Z Ultra. I understand their frustration, since I also had this problem the day I got and updated my Ultra. But, I found a method (which I've read about here, but seems like a major number of people don't know about) and my phone has been flawless ever since. Not one single hang up, reboot or SOD. No need to mess with the Optimized Backlight setting or anything.
Now, bare with me, since I could be wrong and am just theorizing here, but the cause of most of these problems is flashing a FTF using Flashtool. But, don't worry. If you want the latest firmware and don't want to wait for your country to release it, you can still use the Flashtool method. Although, if you don't want the SOD and other issues, you'll want to do a little more than Flashtool.
What should I do, then?
Simple:
Flash your FTF file as usual. (If you're already on the desired firmware and experiencing these issues, skip to the next step.)
Download Sony PC Companion
Install and execute Sony PC Companion.
Connect your Sony Xperia Z Ultra to the PC using a USB cable.
Optional: Backup your data from the Backup and Restore option, if you don't want to lose it.
Go to Support Zone on Sony PC Companion.
Click on "repair my phone/tablet" (in blue letters, as seen in the picture below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow the on-screen instructions and wait for it to finish. (Might take a while)
Unplug your phone and turn it on.
Optional: Restore the previously backed up data using the Backup and Restore tool.
Enjoy a bug-less experience.
Don't forget to hit the thanks button if this helps you in any way. :good:
To make short, seems you need to wipe data and make a clean install to fix SOD issue. To do so you can update with Sony Ericson Update Service (SEUS) or flash .ftf via Flashtool. What I did and never had SOD.
Sent from my C6802 using Tapatalk 4
Try below step before you can assure it is fixing the issue, as it didn't fix any issues actually.
Go to Settings - Display - Brightness.
Tick back Adapt to lighting conditions. (If you off previously)
Un-tick Optimized backlight.
Shutdown the phone.
On back the phone, did the fake hang appear?
One success login to phone, immediate locking the screen by pressing the power button, did the Screen of Dead (SOD) happen?
Check below to rectified whether it is free of bugs or not, in-fact it is not.
Issue 1 to 3 appear after .510 firmware, issue 4 to 6 appear since 1st initial firmware.
1. Fake hang in next startup once shutdown the phone with condition un-tick optimize backlight and tick adapt to lighting conditions.
2. SOD appear after the fake hang by simply click the power button to lock the screen.
3. English swiping input in Chinese Keyboard at mini keyboard layout is not working. All output is wrong wording. It look obvious it registered the swiping at full screen keyboard layout.
4. Chinese input by typing in most website not working in proper, only swiping is working.
5. Flickering / frame chopping when viewing Youtube video directly via Chrome where it not link to YouTube own app. No issue if watching YouTube at own YouTube app.
6. Download YouTube movie using third party app like JetVD facing same flickering / frame chopping video result.
Andrewtst said:
Try below step before you can assure it is fixing the issue, as it didn't fix any issues actually.
Go to Settings - Display - Brightness.
Tick back Adapt to lighting conditions. (If you off previously)
Un-tick Optimized backlight.
Shutdown the phone.
On back the phone, did the fake hang appear?
One success login to phone, immediate locking the screen by pressing the power button, did the Screen of Dead (SOD) happen?
Check below to rectified whether it is free of bugs or not, in-fact it is not.
Issue 1 to 3 appear after .510 firmware, issue 4 to 6 appear since 1st initial firmware.
1. Fake hang in next startup once shutdown the phone with condition un-tick optimize backlight and tick adapt to lighting conditions.
2. SOD appear after the fake hang by simply click the power button to lock the screen.
3. English swiping input in Chinese Keyboard at mini keyboard layout is not working. All output is wrong wording. It look obvious it registered the swiping at full screen keyboard layout.
4. Chinese input by typing in most website not working in proper, only swiping is working.
5. Flickering / frame chopping when viewing Youtube video directly via Chrome where it not link to YouTube own app. No issue if watching YouTube at own YouTube app.
6. Download YouTube movie using third party app like JetVD facing same flickering / frame chopping video result.
Click to expand...
Click to collapse
Yeah... I had a hard time trying to figure out what you were trying to say.
Once I did figure it out, I tried following the directions you gave step by step, and my phone definitely doesn't have any of the bugs you mentioned.
Like I said, I used to experience bugs like that, until I used the method I explained in the OP.
Did you try it?
P-Men said:
Yeah... I had a hard time trying to figure out what you were trying to say.
Once I did figure it out, I tried following the directions you gave step by step, and my phone definitely doesn't have any of the bugs you mentioned.
Like I said, I used to experience bugs like that, until I used the method I explained in the OP.
Did you try it?
Click to expand...
Click to collapse
Maybe you not really understand what I mean. Your above step I did try at .510 and it is same. I had repair my phone before, factory reset before, all same. I not going to try again on .526 since already got people try and use my method, and it happen.
Maybe screenshot let you understand more.
Set as screenshot below:
Immediate Power Off the Phone.
Turn on the Phone, you will notice after SONY logo, they is a fake hang, it take sometimes before continue.
The phone will became 100% brightness after success load to main launcher. You can only change the screen brightness after un-tick adapt to lighting conditions and move the slider.
Immediate click the power button to lock the screen. SOD (Screen Of Dead) appear.
I tried a clean reset / update with Sony Ericson Update Service (SEUS) and still the problem with the Optimized Backlight is there.
Related
change's log
V1.6 2009-09-11
Phone doesnt lock if there is a call in progress
V1.5 2009-08-26
1) Added an option to lock the device when a player (HTC player, WM Player, HTC FM Radio, etc) turns the screen off...
V1.4 2009-08-14
1) Added command argument. "lock". this will lock the device.
2) Added a link called "Lock Now" to lock now....
3) All the links are located in a folder called "Lock Device". (because there are 4 links and I dont want to fill the directory \windows\start menu (in your language) with many links
V1.3 2009-08-04
1) Commands support. The program LockDeviceGUI.exe supports 4 commands.
enabled -> Enable LockDevice
disabled -> Disable LockDevice
wakeup -> Run Mode: Lock on wakeup
screenoff -> Run Mode: Lock on screen off
Your can set one or two parameters. For example:
61#"\Archivos de programa\LockDevice\LockDeviceGUI.exe" disabled -> Disable LockDevice
61#"\Archivos de programa\LockDevice\LockDeviceGUI.exe" enabled screenoff -> Enable LockDevie and run mode set to "lock on screen off"
The installer creates out of the box two links in the system programs folder: EnableLock.lnk and DisableLock.lnk (The first with "enabled" parameter and the second one with "disabled" parameter).
V1.2 2009-08-03
1) The installer includes a little GUI program.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With this program you can configure how LockDevice must behave.
View attachment 211920
1) Enabled / Disabled
2) Work Mode:
2.1) Lock on wakeup. This is how works previous version. Pros: The program doesnt stay resident. Cons: The device must be "off" some seconds before windows really suspend the device. This time is longer with wifi active. So if you press power off and then power on quickly probably the device wont lock (because windows never suspended the device)
2.2) Lock on Screen off. Pros: The device is locked when the screen goes off so always works correctly. Cons: The program stays resident. Anyway the program is "paused" all the time so no CPU is used. the program stays sleeping until windows notifies it the screen is off. Then LockDevice lock the device and goes to sleep again
Please report any bug, suggestion, etc...
Dani
V1.1 2009-07-31
1) The device is locked directly using keybd_event. No sendkey.exe call . So smaller, quicker and no dependence of sendkey.exe configuration.
Initial post
Hi
Today I ve been searching for a very little program, not resident in memory to lock my device on wakeup. There are other ones but I didnt find one that isnt resident in memory.
So I ve done quickly a very small program that is notified by windows when the device is woken up, so no resident, and executes \windows\endkey.exe. So if you ve configured your end key long press to lock the device then your device will be locked.
I ve tested it in my Touch Pro 2 and works.
I really needed it and maybe other people are in the same situation.
Dani
It doesn't seem to do anything on my Touch HD. I tried turning off and on, nothing. Tried soft resetting, tried again. Nothing. I even tried running it from File Explorer on the LockDevice folder (Maybe it needs to instantiated or something), then tried turning off and on again. Nothing.
EDIT: Oh ok... It doesn't work if you just turn it off then on immediately (which is a good thing). It had to be off for at least 3 seconds. Although there is a second delay before it locks after turning it on, which is ok I guess. Nonetheless, this is good stuff! Since it's the first one I've seen that is not memory resident (which makes me wonder.. how does it work??).
DaVince said:
It doesn't seem to do anything on my Touch HD. I tried turning off and on, nothing. Tried soft resetting, tried again. Nothing. I even tried running it from File Explorer on the LockDevice folder (Maybe it needs to instantiated or something), then tried turning off and on again. Nothing.
Click to expand...
Click to collapse
I ve reuploaded it to avoid to hang a call
Do you ve \windows\endkey.exe ?
Is it configured to lock the device?
If you suspend the device and quickly press the power button then the device really isnt suspended so It doesnt work. The device must be screen off several seconds (5-10) to consider itself suspended.....
DaVince said:
It doesn't seem to do anything on my Touch HD. I tried turning off and on, nothing. Tried soft resetting, tried again. Nothing. I even tried running it from File Explorer on the LockDevice folder (Maybe it needs to instantiated or something), then tried turning off and on again. Nothing.
EDIT: Oh ok... It doesn't work if you just turn it off then on immediately (which is a good thing). It had to be off for at least 3 seconds. Although there is a second delay before it locks after turning it on, which is ok I guess. Nonetheless, this is good stuff! Since it's the first one I've seen that is not memory resident (which makes me wonder.. how does it work??).
Click to expand...
Click to collapse
Remember to install the new one or the program will hang a incomming call if the device is suspended
When the program starts the first time it register itself to windows to be notified when the device wakes up.
So when the device wakes up Windows execute the LockDevice.exe with an argument "AppRunAfterWakeup". Then the program check if there isnt a call in progress and then execute \windows\endkey.exe. Simple
could some people with other device than mine (tp2) to try if it works ok?
By now all works perfectly without a process spending ram/cpu
Tried the new cab on my Touch HD (Running WM6.1). Everything works ok so far.
Thanks a lot for this! I prefer this solution since this the simplest most efficient one that makes use of the built in Lock.
Nice. I thought about write an small resident process that monitors changes of power state to be more efficient but I prefer a process that only runs for a few ms when the device wakes up and then dies...
awesome app dude. well done. i was wondering though, since its possible to run an app on device wake up...is there a way to call upon an app when the device is set into suspend? cause even though the device's screen isnt on, stuff is still running, so what if a reg entry like the "on device wake up" is used as a "device suspend". that would get rid of the 1 sec wait on wake up and also still not be resident. i actually dont know if there is a way to do that, i dont fully comprehend it but it was an idea. cause it would be sick to be able to get rid of the 1 sec wait.
chronodrago said:
awesome app dude. well done. i was wondering though, since its possible to run an app on device wake up...is there a way to call upon an app when the device is set into suspend? cause even though the device's screen isnt on, stuff is still running, so what if a reg entry like the "on device wake up" is used as a "device suspend". that would get rid of the 1 sec wait on wake up and also still not be resident. i actually dont know if there is a way to do that, i dont fully comprehend it but it was an idea. cause it would be sick to be able to get rid of the 1 sec wait.
Click to expand...
Click to collapse
Hi¡
You can, but using a resident process. The feature I used in the "wake up" process isnt avaible in that way for "before going to sleep". A process can register itself to get notifications about changes in power state (From On state to suspended state)(RequestPowerNotifications api). So you could do some stuff when the device goes to idle state (screen off) but It requires the process to stay running in memory. Really It would be "paused" waiting for a queue event but spending one of the 32 available process in WinMo. Later I will upload a little process doing that. Just for try and play
Dani
Hi
I ve uploaded in first post a more optimized version. Now the program can lock the device by itself instead of rely on call sendkey.exe. So smaller and more efficient. To avoid the 2-3 seconds needed to be suspended to make it work correctly I ve done other version that monitors the power state. It locks the device when the screen goes off (instead of when the device wakes up) but it spend one process (WinMo only can run 32 process at same time). Question of tastes...
The reason about 3-4 seconds needed to wait between power off / power on is this:
When you press power off, the screen goes off (power idle state) but the system needs some seconds to really be suspended. Its in this way because windows notifies drivers about the power event and they must adjust their power levels....So if you press power off and quickly power on then the device really didt was suspended so It isnt really being woken up and the program isnt called by windows
Dani
I'm testing it on a Vogue tomorrow. Looks cool. I'll let ya know how it goes.
Thank you very much
Works well on the Vogue, though sometimes there seems to be a huge delay before the lock screen launches. It seems random though.
Just dropping in to say it works on original Touch Pro and Diamond.
Thanks!
Can't seem to get it to work on the HTC Snap. Anything I am missing here?
Once the screen is off you must wait 3 or 4 seconds before press power on to make it works. Only after that amount of time windows really suspend the device and triggers the wake up event when power on. This time is bigger if wifi is enabled. Tomorrow I will upload a version that locks the device when the screen goes off. It will be even smaller. But it has an inconvenient:will be resident....
Dani
does this lock also have a password lock to it?
Works great on my HTC ATT FUZE running the latest chrome rom 6.5 Thank you very much.
hi.
Tomorrow I will post a new version with 3 options.
1)work mode: lock on wake up (no resident but you ve to wait some seconds between power off / on to lock or lock when screen goes off.(works always but resident)
2)Lock or unlock when suspended and the phone rings. If the device is locked you can pick up/hang the call but you cant activate speakers, for example
3)Enabled / Disabled
Dani
tried it on my toshiba tg01 and it doesn't work,
just wanted to let you know.
cheers
My A101it, just shut it self... after that I cannot open the device... please help...
Try holding the power button down for like 10-15 seconds, then press it again and see if it starts. When I first got the device that happened to me a few times. Hasn't happened since the 2.0.71 update, but that was the fix. The 10-15 second power button hold basically does a "cold boot" like on a PC that is locked up.
ExploreMN said:
Try holding the power button down for like 10-15 seconds, then press it again and see if it starts. When I first got the device that happened to me a few times. Hasn't happened since the 2.0.71 update, but that was the fix. The 10-15 second power button hold basically does a "cold boot" like on a PC that is locked up.
Click to expand...
Click to collapse
I tried everything Turn off Turn On... Shutdown hilding - or + then open... nothing comes out. Maybe their is a recovery something, using a PC..
Update on my A101IT, even thought its totally blackout, I can still press something on the screen, before I install RAMSHOOTER and place widget on the desk. I can still remember where I can press. So if press that part I can still here something. Maybe I can update orignal firmware...
In order for me not to guess,Is there anyone there can post a screenshot of a Recovery Menu that has a Developers Options or when you update the firmware by using a PC and transfering the update, so that I can touch the correct button... I can still connect my archos to my PC, it can be recognize. I'm still guessing were to press...Please help!
Help...please
raymondht said:
Help...please
Click to expand...
Click to collapse
If the cold boot did not work you are rather stuck. Have you considered contacting Archos for support?
ExploreMN said:
Try holding the power button down for like 10-15 seconds, then press it again and see if it starts. When I first got the device that happened to me a few times. Hasn't happened since the 2.0.71 update, but that was the fix. The 10-15 second power button hold basically does a "cold boot" like on a PC that is locked up.
Click to expand...
Click to collapse
Thank you very much but I have found this problem still in firmware 2.1.08
I had fixed this problem by adjust Brightness to 15-20%
jakkrith said:
Thank you very much but I have found this problem still in firmware 2.1.08
I had fixed this problem by adjust Brightness to 15-20%
Click to expand...
Click to collapse
Maybe I should have wrote a bit more by saying "It hasn't happened to me since 2.0.71" LOL
Im from the philippines, bought this from Hongkong.... I'll try calling them...
Latest update...
If I put some light like a flash light on the screen I can see a some of the deskstop... so its like the device has no light inside..
Even in the Archos startuplogo no light, but I can see it using a flash light.
Okay, so basically you are in a "no warranty" situation (unless this Hong Kong site will allow you to return it for replacement). The problem you are describing does not sound like a software issue. This seems to be a hardware problem.
You might want to find some kind of "tear apart" diagram for the 101 like http://www.theandroidphone.com/tag/how-to-disassemble-the-archos-101/
Perhaps you will get lucky and it will just be a loose connection or something simple like that. Otherwise you will need to get a new display...which is nearly as expensive as the unit itself. If that is the case, seriously...just wait a few more months and get one of the new Honeycomb tablets.
i had a similar problems some weeks ago with my 101 (was running an older firmware when it happened though)
for me those steps helped, i found them somewhere on the archosfans forums:
- remove sd card if you are using one
- hold down power button for 10 to 15 seconds
- release power button
- tap the power button 5 times
- archos will boot now if everything worked out
hope this helps
If I use a flashlight I can see the icons and buttons... so possible its a Backlight issue..
raymondht said:
If I use a flashlight I can see the icons and buttons... so possible its a Backlight issue..
Click to expand...
Click to collapse
didnt get that before, sorry
raymondht said:
Update on my A101IT, even thought its totally blackout, I can still press something on the screen, before I install RAMSHOOTER and place widget on the desk. I can still remember where I can press. So if press that part I can still here something. Maybe I can update orignal firmware...
In order for me not to guess,Is there anyone there can post a screenshot of a Recovery Menu that has a Developers Options or when you update the firmware by using a PC and transfering the update, so that I can touch the correct button... I can still connect my archos to my PC, it can be recognize. I'm still guessing were to press...Please help!
Click to expand...
Click to collapse
first screen after boot in recovery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
second screen - after click on "Recovery System":
after clicking "Format System":
plug in usb, copy aos-file and press the power button once
let us know if it worked out...
JeG81 said:
didnt get that before, sorry
first screen after boot in recovery:
second screen - after click on "Recovery System":
after clicking "Format System":
plug in usb, copy aos-file and press the power button once
let us know if it worked out...
Click to expand...
Click to collapse
Done this using a flashlight, reformat everthng, I also removed the Developer menu... But thanks for your suggestions..
Sounds like you turned the back light off. Some widgets have the ability to turn it off and not just down. Have you checked the settings for the back light to make sure it is on?
blazingwolf said:
Sounds like you turned the back light off. Some widgets have the ability to turn it off and not just down. Have you checked the settings for the back light to make sure it is on?
Click to expand...
Click to collapse
I have blackout on Archos Startup LOGO & Reovery Menu, incase where can I find it? I can still glans some buttons, using a flashlight...
raymondht said:
I have blackout on Archos Startup LOGO & Reovery Menu, incase where can I find it? I can still glans some buttons, using a flashlight...
Click to expand...
Click to collapse
have you tried to reformat your system in recovery?
(instead of the old version linked in the thread, get the newest firmware here)
what happens when you boot freshly installed android?
if its still dark then:
what is shown in > settings > display > brightness?
Yesterday i noticed that the camera on WP7 has started working absolutely fine all by itself.
Earlier i was getting a tint when i tried taking pictures, and when i looked in the threads, it was said that the problem is with the camera driver.
But i checked the camera yesterday and the pictures are turning out to be perfect without any tint now. Not sure how this happened. The only change i remember making to the phone is that i installed Android on SD along with WP7.
Could this have fixed the camera on WP7, there is no relation between the two, but that was the only change i made to the phone.
I hope someone can shed some light on this.
thanks...!
With or without flash?
Generally, when I take pictures with my HD2, they look quite good. However, when the flash is used, the pictures have a greenish tinge.
So, did your camera flash while you took the pictures?
Nice!
I hope someone can shed some light on this, as the camera is the only problem i still have with the device.
I am using the .xap camera software, which is working nice, but i feel the camera has more potential......
yes, the camera did flash and still took the pics perfectly, that is what i was amazed with...no idea how that worked, but i am scared to even restart the phone as i might loose it back.
The tinting only happens when using the flash.
I think, (sounds a little weird) that the thing with the green light has something to do with RGB. I saw It by coinsedince..I was drinking beer in the bar, and I watched at a picture on my phone wich was taken wich when I had win6.5
I raised the BROWN beer bottle and then I saw the same and famous green light. As If I tooked It just a minute ago.
Maby It's nothing, then forgive me for saying it. Just want to help.
Greetz
well cant say its worked for me, but i think the green tint may have something to do with the timing of the flash
Dunno what you guys are smoking but dont change !
It's a good one
Seriously, if i got it right, the "only" problem with WP7 installed on a HD2 is the fact that we dont have the real button to take photos.
On the HD7 you press the button half way, it setup the focus, and then you finish to press the button to take a photo, exactly like a normal camera.
On the HD2 when we press the button it just take the photo but doesnt set the focus.
Maybe I'm wrong, but i think it is the only difference, at least it is the real problem.
If you use SHCameraApp, you can set the focus by touching the screen or if you turn on autofocus in the settings and then it makes perfect photos ... and THAT's IT !
If you got accidently a good photo, that s probbaly because you was at the right distance, matching with the default focus of the HD2 or something ....
But maybe I dont get it, and in that case I would love to smoke that thing ;-)
I hope some developers use my idea for camera app. Since HD2 doesn't have camera button, and since the volume buttons don't function when in camera mode, why not utilize the volume up button as half press and call button for taking pictures? So you would hold down the volume up button to focus, and press the call button to take a snap shot! It is actually intuitive when i tried to emulate it~
its not somethink that can be easily changed, its a hardware function built in to the device, WP7 isnt like WM, you cant go about changing things like that with any degree of success, until DFT release the tools to go about messing with ROMS its not even a remote possability.
[IDEA]Mapping key on HD2
JC_Agga said:
I hope some developers use my idea for camera app. Since HD2 doesn't have camera button, and since the volume buttons don't function when in camera mode, why not utilize the volume up button as half press and call button for taking pictures? So you would hold down the volume up button to focus, and press the call button to take a snap shot! It is actually intuitive when i tried to emulate it~
Click to expand...
Click to collapse
After how I see things the best way of mapping buttons on HD2 with WP7 is:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Green button
- hit to open Phone
- hit in Phone page make a call
- hit in call to switch to speaker
Red button
- hit to turn off screen
- hit to turn off the device
- in Phone page hit to end the call
Start menu/windows key - hit to go to app list
Home button
-hit to go to home page
Back button
- hit to go back just like now
Volume up and down - hit them to chane volume
- but in camera hit vol down to focus and vol up to make a photo
What about searching?
Schlurcher said:
What about searching?
Click to expand...
Click to collapse
Long press on "home" button, because "back" button will be use for multitasking in Mango
nichitandrei said:
Red button
- hit to turn off screen
- hit to turn off the device
- in Phone page hit to end the call
Click to expand...
Click to collapse
Problem with end call: In an active call, the display is switched off and you must activate the display with the end call button!? So it would ends the call...
How to remap buttons?
Nice, this idea with a booloader as cLK instant boot no go go go etc my HTC HD2 would be perfect!!
1 click into photo app is one of the major selling points of WP7.
Don't kill it off because you can't read around icons.
Co2_13 said:
Dunno what you guys are smoking but dont change !
It's a good one
Seriously, if i got it right, the "only" problem with WP7 installed on a HD2 is the fact that we dont have the real button to take photos.
On the HD7 you press the button half way, it setup the focus, and then you finish to press the button to take a photo, exactly like a normal camera.
On the HD2 when we press the button it just take the photo but doesnt set the focus.
Maybe I'm wrong, but i think it is the only difference, at least it is the real problem.
If you use SHCameraApp, you can set the focus by touching the screen or if you turn on autofocus in the settings and then it makes perfect photos ... and THAT's IT !
If you got accidently a good photo, that s probbaly because you was at the right distance, matching with the default focus of the HD2 or something ....
But maybe I dont get it, and in that case I would love to smoke that thing ;-)
Click to expand...
Click to collapse
I know I'm a little late here, but the autofocus on the stock WP7 camera does actually work on the HD2. Just hold the green key down while holding the phone still and the camera will focus. What is probably throwing people off is that the focusing is occurring after the shutter sound goes off. Anyway, thought this might be helpful for those who wish to use the stock camera app.
Hi, just had a thought about the camera fault with WP7 and HD2.
Wasn't the original DFT rom created from the HTC Mozart?
If that is so the mozart has a zenon flash where as the HD7/HD2 have an LED flash. the timing would be different for the zenon flash and possibley Hue/White balance etc settings.
Would this explain why there is a driver issue?
emdelect said:
Hi, just had a thought about the camera fault with WP7 and HD2.
Wasn't the original DFT rom created from the HTC Mozart?
If that is so the mozart has a zenon flash where as the HD7/HD2 have an LED flash. the timing would be different for the zenon flash and possibley Hue/White balance etc settings.
Would this explain why there is a driver issue?
Click to expand...
Click to collapse
Yes sounds Good.
If the Mozard has Xenon.
In Physik, we tested the lightwave-lenghts und there are bit differenzen throug xenon between a "white" led!
If anyone have interessting i will searching for the test-examples. ( I hope i have this at home ).
sry for bad english...
Anyone else having any problems with the touchscreen? I noticed the phone was very very accurate when texting among other things (coming from the EVO 4G) and I thought something was up the past few days because my autocorrect was stepping in a lot more than usual even thought I thought I was hitting the right keys.
Now, when I'm at the pattern lock screen, I can draw my pattern as many times as I want and it never draws the pattern I draw. I will drag an entire line and it will either show I'm touching the first or the last dot. And on the home screen, I'll swipe and it won't move (kinda rebounds back to the page I was on) or it thinks I'm pinching the screen.
Just wondering if anyone else had this problem and had to return it yet?
I'm having problems where I can't use my screen from time to time. It seems to stick. The only way to get back to my screen working is by turning my phone screen off. This is starting to become an issue. Especially when I am in the middle of a message or email.
Sent from my great Evo3D.
Is it certain keys don't work? Actually noticed that in landscape mode, my palm was touching the corner of the screen rendering some key strokes unrecognizable. Seems to have a more sensitive screen.
jrdoctor said:
I'm having problems where I can't use my screen from time to time. It seems to stick. The only way to get back to my screen working is by turning my phone screen off. This is starting to become an issue. Especially when I am in the middle of a message or email.
Sent from my great Evo3D.
Click to expand...
Click to collapse
Sent from my PG86100 using XDA App
The phone thinks It's being touched around the Y and G keys. I went to enter my gmail account info since I got locked out and it kept pressing those keys. Really annoying.
I'm having same problem and its annoying me allot .. I'm not sure if its the screen or a bug .. but there is times my screen is not responsive.. I've thought of bringing it in.
Sent from my PG86100 using XDA App
I'm having this problem right now. My phone seems to be hitting keys by itself(like continuously going back to the previous screen) and my lockscreen pattern only registers one hit even though i'm moving to more than one dot at a time. I just rebooted and it's still doing this. It's randomly doing this over the past 2 days though.
There is times that ill do the pattern 3 or 4 times and it will reset itself.. or ill have to wait 30 seconds after i have repeatedly done the pattern.. It has been doing it since I had the phone.. its irritating as hell.. not sure if its a phone issue or screen issue ... But I'm sure Sprint will make something up and just so a reset..
Sent from my PG86100 using XDA App
sdezrilov said:
Is it certain keys don't work? Actually noticed that in landscape mode, my palm was touching the corner of the screen rendering some key strokes unrecognizable. Seems to have a more sensitive screen.
it's not certain keys, no difference whether in landscape or not. It's become a major issue. I haven't used the lock screen because I have problems so often with the regular screen. Just really frustrating.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Sent from my great Evo3D.
Have any of you guys temp rooted? I have. I don't know if that is the issue since temp root attacks the graphics driver to get root.
-viperboy- said:
Have any of you guys temp rooted? I have. I don't know if that is the issue since temp root attacks the graphics driver to get root.
Click to expand...
Click to collapse
Bone stock here. The problem comes and goes randomly. Had the problem half hour ago, just left it alone for awhile, and now it seems to be normal again.
I've never thought I had very good luck, but when I come to these forums and read the problems so many of you guys have with your phones, I think I do. I've never had an issue with any of my Android phones. I wonder if its because I hardly download any apps. I mainly use it for browsing the net, text and phone calls. Just weird.
Any of you guys with this problem notice that it happens more when attached to USB? I just realized that the past 2 or 3 times I have the touchscreen issue that I also had the 3D charging on via USB on my computer.
dcfella said:
Any of you guys with this problem notice that it happens more when attached to USB? I just realized that the past 2 or 3 times I have the touchscreen issue that I also had the 3D charging on via USB on my computer.
Click to expand...
Click to collapse
Yeah, seems like most phones act weird when plugged in. Still having lockscreen issues, really REALLY annoying!
Mine has been having a ton of issues starting this last weekend. Sometimes it seems to have a mind of it's own and keys just start getting pressed. Other times it won't process touches. Most of the time the App drawer and personalization launchers at the bottom of the sense skin won't work. Thought I had it fixed last night by clearing a bunch of program data, but came back today. Seems to be a hardware issue. Probably take it back in. Really upset as this is my third one so far. Have done multiple hard resets to try to clear it.
I was able to catch this happening in the "MultiTouch Visualizer" app, and took some screenshots of it. These screenshots show what appears to be 2 separate issues, but they seem to be closely related.
In this one, I'm actually touching in the center of the two touch points (i.e., where the blue circle appears), but there it seems to have some kind of "gap" in the sensor, where it thinks that my one touch is actually two. It always occurs at that horizontal location -- basically along the blue horizontal line.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I move my finger up, it goes back to one pointer:
and likewise if I drag down, below that problem region:
But when crossing that region of the touchscreen, it gets interrupted and thinks there are 2 touch events. That's what makes it difficult or impossible to unlock when the problem is occurring.
The 2nd issue is that after a while of testing, it actually ended up "sticking" where it was registering two touch events at the bottom center, even though I am not touching the screen:
and this is what happened when I did touch the screen (pointer "1" is where I was actually touching, but pointers 2 and 3 were still registering, so it thought I was touching the screen in 3 places):
The problems seem to come up about 2 or 3 times a day. Usually at the worst possible moment -- there was one time I was trying to snooze the alarm, and somehow it ended up tapping that center location on its own several times... First tap opened the Phone app (the center button on the Sense home screen) to the call log. Second tap registered on the green "Call" button, so it ended up redialing the last number I called. I panicked and tried to end the call by tapping several times on the End Call button, but it wouldn't register at all... I tried home, back, opening the notification bar, etc, and nothing was responding. Eventually the call ended after going to their voicemail, but then it tapped the green "Call" button again, and called them again!
I'm probably going to have the same issue trying to replace it, because it doesn't happen all the time.
Devilived666 said:
I'm having same problem and its annoying me allot .. I'm not sure if its the screen or a bug .. but there is times my screen is not responsive.. I've thought of bringing it in.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I've had this issue I can recreate it, I returned my first 3d and noticed the second one did the same thing. I think its a kernel issue because the cooked kernels don't have this problem. And this seems to happen after rooting the phone using the temp root method.
It has something to do with the multi touch.
Ill take the draw app, draw a line and at the same time touch a different part of the screen, the line im drawing will now look like this __ __ __ __ all broken like that. This has happened on two 3d's now. So when your keyboard is suddenly becomes non responsive, this is probably what's going on. The problem will fix itself in about five seconds or so and operate normally again. I thought about making a video of it.
I made a cool YouTube video of the problem:
http://www.youtube.com/watch?v=8rz3uWFuDkI
phatmanxxl said:
I made a cool YouTube video of the problem:
http://www.youtube.com/watch?v=8rz3uWFuDkI
Click to expand...
Click to collapse
i was watching that video and i was gonna paste the link lol
maejrep said:
The problems seem to come up about 2 or 3 times a day. Usually at the worst possible moment -- there was one time I was trying to snooze the alarm, and somehow it ended up tapping that center location on its own several times... First tap opened the Phone app (the center button on the Sense home screen) to the call log. Second tap registered on the green "Call" button, so it ended up redialing the last number I called. I panicked and tried to end the call by tapping several times on the End Call button, but it wouldn't register at all... I tried home, back, opening the notification bar, etc, and nothing was responding. Eventually the call ended after going to their voicemail, but then it tapped the green "Call" button again, and called them again!
I'm probably going to have the same issue trying to replace it, because it doesn't happen all the time.
Click to expand...
Click to collapse
I had this exact thing happen to me yesterday. It called someone I really didn't want to talk to, and I kept trying to hang the freakin phone up. It went to their voice mail and I am yelling at the phone to shut off at this point, and I finally just ripped the battery out... Probably was a funny voicemail for the person.. ugh..
I get touchscreen issues but it only seems to be when I just washed my hands and they are still ever so slightly wet. Thats when the screen gets super stuck and I have all sorts of issues. And I would never use my phone with "wet" hands, this is like after I used a paper towel and I didn't even think they were wet, wet lol..
It happens often enough to be annoying, but not so often that each time it does it I am still confused as to wtf is going on.
Mine has had random times where most of the touch screen wont work since day one, happens every couple of days, usually have to reboot for it to work again
About 2-3 times a hour, the screen will turn itself on and display the lockscreen, then go back to sleep if i don't touch it.. I always think i'm receiving a text message or something and it's getting annoying.
I'm on VR 2.3, but I also had this problem on Lite'ning, so i don't think it's rom dependent. Could any of these apps be the issue? I've frozen a bunch of them tho and it didn't help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had similar problem.. maybe something related to USB connector.
My phone randomly wakeup showing a steering wheel in notification area (using stock rom).. also, when that happen during a call, it switch to handsfree mode. That's was very annoying!
I've sent it back for assistence.
Bye
KK
You must have something running on the background, could be GMaps/Latitude, Push/Pull exchange etc etc..to know what it is, download and install Better Battery Stats and look under the 'Wakelocks' option. You will see what is causing the Awakes and take further steps.
And ATK is not advised for Android. (I was against it but now I too agree it )
Regards.
ithehappy said:
You must have something running on the background, could be GMaps/Latitude, Push/Pull exchange etc etc..to know what it is, download and install Better Battery Stats and look under the 'Wakelocks' option. You will see what is causing the Awakes and take further steps.
And ATK is not advised for Android. (I was against it but now I too agree it )
Regards.
Click to expand...
Click to collapse
Are you sure it's called Better Battery Stats? I can't see it on the market
edit* never mind, found it on xda.
Under wakelocks there's a huge list of stuff. Can any of these be the culprit?
Just check the first three or four, no need to check those which has some seconds duration, only check which has some minutes, like 10,15 mins duration.
Regards.
Please Help
my phone gets new problem each day and any further i go it get worse.
first i couldn’t connect to Vpn sometimes. i thought it may be personal problem.
then it got reset randomly with no reason. i didn't notice.
then it didn't recognized by computer and randomly didn't get charged.
today when it goes to standby mode it light up after few seconds and if i try to put it back in sleep mode by pushing power bottom it gets freeze and hang up.
Even when I turn the phone off sometimes it turns on by itself and after booting goes to car mode
Does have anybody similar problem?
I searched and found this (copy following line to address bar.. xda didn't let me to put a URL)
phonesreview.co.uk/2011/05/31/samsung-galaxy-s2-problems-by-users-discussions/
so it’s not just me.
Could anybody help me?
kasperok said:
I had similar problem.. maybe something related to USB connector.
My phone randomly wakeup showing a steering wheel in notification area (using stock rom).. also, when that happen during a call, it switch to handsfree mode. That's was very annoying!
I've sent it back for assistence.
Bye
KK
Click to expand...
Click to collapse
I'm having exactly the same issue... but I'm experiencing also USB issues: sometimes the phone "believes" is USB connected without any physical cable connected... very weird... I'm still searching in the forum if can be fixed by software, before to send it to a service
khosronejad said:
my phone gets new problem each day and any further i go it get worse.
first i couldn’t connect to Vpn sometimes. i thought it may be personal problem.
then it got reset randomly with no reason. i didn't notice.
then it didn't recognized by computer and randomly didn't get charged.
today when it goes to standby mode it light up after few seconds and if i try to put it back in sleep mode by pushing power bottom it gets freeze and hang up.
Even when I turn the phone off sometimes it turns on by itself and after booting goes to car mode
Does have anybody similar problem?
I searched and found this (copy following line to address bar.. xda didn't let me to put a URL)
phonesreview.co.uk/2011/05/31/samsung-galaxy-s2-problems-by-users-discussions/
so it’s not just me.
Could anybody help me?
Click to expand...
Click to collapse
Similar to me (see previous post) but I didn't experience any randomly restart, however the phone randomly is believing that USB cable is connected
The only culprit I cant really think off is your Advanced task killer, its doing more harm than good. Uninstall it and observe.
There a read up about task killers and what they actually do
Sent from my GT-I9100 using XDA Premium App
I see, I have uninstalled it and monitored my wakelocks with better battery stats.
Can't really find anything. Facebook, Spotify, Dialer, Tapatalk, Widgetlocker etc. Tried freezing them all except dialer problem still occurs (but not so often?)