Hello, everyone.
Well...3 days ago it was raining in my city and I was talking with the Defy on the streets, the phone fell to a puddle in the sidewalk, I just picked it up and kept talking, but then I saw there was some fog and little drops of water inside the screen, though the phone was still working perfectly. The next day the fog was still there and the phone was working, but later that day the screen just didn't turn on and the LED was always turned on in red (but I could see the screen items under high light and I managed to see something in the notificacion bar like "new electronic device recognized"). In order to remove the fog I took the battery off and put the phone under my laptop, so the low heat would vaporize the remaining water and maybe the screen would work again.
Now I have the phone with no fog but the screen is still not working, though I can turn on the phone and it vibrates when I press the capacitive keys and it sounds when someone calls and that stuff, it's just the screen isn't working, all black, like missing the retroilumination. The red LED is always on. So I thought of sending it for repairment, but I can't flash any sbf, as I didn't had USB debug mode enabled the RSD Lite says "unable to retrieve initialization values from INI file (0x7029);phone connected". Can I enable the usb debug mode via adb shell?
The phone is rooted, using JBoogie3 Blurless Honey, it's a Vodafone Spain.
TL;DR version: phone got into a puddle, screen stopped working, red LED always on, can't flash any SBF to send it to repair because usb debug mode is not enabled and can't enable it since I can't see the things that are on the screen.
I'll love for ever the one who can lead me to a solution. Thanks in advance, please help, I'm desperate.
PS: The phone was closed and the rubbers on the sides (headphones and usb) were closed too. Sorry for the long post.
i can try and guide you to the usb debug on of settings if you want
That'd be helpful, any screencaps would be awesome. I think there was no scrolling to do in Settings tab nor in applications,therefore, easier.
danirolo7 said:
That'd be helpful, any screencaps would be awesome. I think there was no scrolling to do in Settings tab nor in applications,therefore, easier.
Click to expand...
Click to collapse
first thing first can u get into the settings? if not wat launcher do u have?
GoLauncher EX..I think settings is in the right low corner when you hit menu key in the homescreen..
ok once ur in the settings press near the botton of the screen so the last selection, then turn ur screen sideways and select the last box again to go into development however this time press about 0.5 - 1cm above the botton of the screen. once you in development select get a ruler and from the top of the screen not the fone press at 1.5cm. that should then enable usb debug. if you need any more help just ask or if something does not make sense
Will try several times..but I can't lose time rebooting everytime I try, anyway I can check if debugging is enabled trough adb or something? >.<
danirolo7 said:
Will try several times..but I can't lose time rebooting everytime I try, anyway I can check if debugging is enabled trough adb or something? >.<
Click to expand...
Click to collapse
Sorry none that I no of
I've managed to flash the SBF, downloaded this RSD http://cyberwarez.googlecode.com/files/RSDLite-4.7+patch.zip and put the INI file in the root folder of RSD installation. Thanks for your help
np. glad i could help out
Related
Hi All,
Does anyone know how to get this working on our beloved HD's? I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
So this seems like the ideal solution - but i can't get it to work!!
I've copied over the file to the windows folder, then soft reset. Changed the registry entry for phoneLockEnable to 1 in HKLM/Software/HTC/Phone but still no joy!
All help would be greatly appreciated.
Regards
DF
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Sorry, i don't have the cab file, i just saw the screenshot and thought 'that's what i need'!!!
Hopefully some bright spark here can help us both (and others probably).
Regards
DF
Beside this transparent canvas, where can I get the orginal canvas?
I am using a offical ROM but I don't see this function!
I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
Click to expand...
Click to collapse
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
take55 said:
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
Click to expand...
Click to collapse
Hi take55,
Yes, i'm aware of the advanced config tweak (also in HD Tweak), and as you correctly state, the screen should/will go blank on call connection (i'm running kwbr's A Touch Of HD 3.3.4 and mine doesn't, even with tweak applied!!).
Unfortunately, when the call ends and you move the phone away from your ear, the screen still stays blank????? I've read somewhere on these forums that it never will work like the iphone (not sure why, as the light sensor should recognise that we've moved the phone away from our ears).
So that is why i'm trying to get this other method to work. What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
It also might be the fact that this was designed for the Diamond (found the cab on the Diamond forums).
Just hoping some genius here might now how to sort this.
I've attached the cab file i've found, give it a try and see if you have the same issue as me.
Regards
DF
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Datafanatic said:
What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
Click to expand...
Click to collapse
It has nothing to do with the BMPs but with the registry setting that the CAB also makes. It sets HKLM\Software\HTC\Phone\PhoneLockEnable to 1, in wich case you'll have to press the power button to unock (no need to soft reset). For the BMP to work the phone/dialer software will have to support it, otherwise it just locks the phone in the usual way: black screen, power button to unlock.
Datafanatic said:
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Click to expand...
Click to collapse
tks but your cab only for the canvas skin only, do not contain the original software (slidable canvas), anyway, tks for your help
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
rubbermonkey123 said:
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
Click to expand...
Click to collapse
Useful info - I found this particularly annoying yesterday during a ouple of calls.
Also discovered Gyrator tries to turn the phone screen and was laggy - which was even more annoying!
Everyone!!!
CHECK THIS OUT - http://forum.xda-developers.com/showthread.php?t=489034
Answer to all our prayers - a screen lock which uses the g-sensor and not the light sensor.
Now, when a call is connected, holding the phone to the ear blacks the screen, but when you bring the phone down (to use the keypad or something), THE SCREEN COMES BACK ON!!!!!!!
Tried and tested on kwbr's A Touch Of HD v3.3.4 (probably the best manila2 ROM out there!)
Regards
DF
I wanna make another post here cause in the last post this issue wasnt resolved and i wanna fresh thread here, please only post if you have the solution, thanks hope theres someOne who can get this issue resolved.
Do you use AutoKeylock ?
I had this problem when I started using 6.1 ROMs first.
In my case I had about 6 applications I always installed right off the bat after a new ROM flash. One of those was Maniac's AutoKeylock.
I timed the duration between answering a call and having the call go white one day, and it seemed to me to match precisely with the screen timeout settings I had in AutoKeylock.
I removed the application, and have never seen the problem happen again.
However, I do miss having AutoKeylock.
I realize that this could be totally coincidental, and thus I asked before whether others who had the problem also used AutoKeylock but never got a reply.
Perhaps you can reply as to whether you use it or not. And, if you do, whether removing the application resolves the issue for you.
If there is a correlation then we can alert Maniac to the issue, and he may be able to find a solution.
LiverpoolFCfan said:
I had this problem when I started using 6.1 ROMs first.
In my case I had about 6 applications I always installed right off the bat after a new ROM flash. One of those was Maniac's AutoKeylock.
I timed the duration between answering a call and having the call go white one day, and it seemed to me to match precisely with the screen timeout settings I had in AutoKeylock.
I removed the application, and have never seen the problem happen again.
However, I do miss having AutoKeylock.
I realize that this could be totally coincidental, and thus I asked before whether others who had the problem also used AutoKeylock but never got a reply.
Perhaps you can reply as to whether you use it or not. And, if you do, whether removing the application resolves the issue for you.
If there is a correlation then we can alert Maniac to the issue, and he may be able to find a solution.
Click to expand...
Click to collapse
You know if the reason you miss autokeylock is for the ability to set a time for the screen to turn off and the keypad to lock, smarttoolkit does that, with no problems.
HTCP4000PPC said:
I wanna make another post here cause in the last post this issue wasnt resolved and i wanna fresh thread here, please only post if you have the solution, thanks hope theres someOne who can get this issue resolved.
Click to expand...
Click to collapse
How often it happen?
With my phone running Kavanas I will get a white screen once after a reboot and then I press and button and it goes back to normal and wont do it again. I have gotten used to it.
For some reason I think it has to do with Tornado PowerControl, do you have that installed? I just cant figure it out exactly. Maybe we can find a solution.
We'll i believe this White screen has something to do with the backlight settings in power managment, i find if you leave screen on full and turn off the phone from turning off the screen, the white screen wont happen, this isnt so bad, cause if u want the screen to go off just hold down the disconnect phone button, not too bad cause when your not wanting to use the phone anymore the screen still goes off, also you can turn the backlight off in accessories which is the same as setting the screen to go off automatically in 5 seconds, white screen fixed moreless.
Same issue with Ricky's v24 and now with Rose 1.7
I also am experiencing this issue, but do not have installed neither Maniac's AutoKeylock nor Tornado PowerControl.
It happens sometimes during a call, sometimes not.
It happens when leaving the phone unlocked and timesout idle time. If hit the Home or back buttons, it shows the home screen again and next timeout does work fine.
I have beeing looking up and down for fixes but was unable to find one. Some say turning off "Run Lowlight" JOGGR setting, some say flash after a hard reset...
It seems that running lowlight (joggrinfo.exe -m -t) helps a bit. If the phone is fully bright and rests on the table, the screen goes white after timeout.
However, if run lowlight and let it alone, it turns off the screen normally.
Also when it goes white and hit back or home button, the screen goes mid-bright, and then turns off normally.
However, when unlocking, it goes full bright, and then the issue comes back.
In summary ...
Full Bright -> Times out to whitescreen.
Mid Bright -> Times out to lights off.
Unlock -> Goes full bright -> Times out to whitescreen.
White screen -> Hit Back/Home button goes mid-bright -> Times out to lights off.
It would be great if lowlight could be run when unlocking the device.
Does it work same way for you guys??
Regards.
This will stop White Screen from happening.
ok this is a way to avoid the white screen issue, (Click on Light Config) then open CeleTask and in CeleTask - Tools use Close Screen this will turn off your screen and allow the backlight from turning on when screen turns back on, also remember u need to set your power settings to (Backlight time out on battery 5 Seconds and Backlight on AC can be 1 minute which u never use) and Display time out Never..)
You can also use CeleTask to disable the screen when you make a call, just open CeleTesk when you hit call.
Topic should be changed as not a fix but work around "sortof":
Process of illimination:
My recomendation would be try a hard-reset, don't install any programs see if that fixes it now when installing programs don't bung them all on install 1 @ a time soft-reset give it while see if problem resumes, do this for all software then you may find the culprit?
This is not an issue faced by all so something has to be the culprit.
Bad Flash?
Software Install?
JOGGR?
Power Settings?
They are just examples.
I had this happen once but on WM6 and a hard-reset was what was needed and didn't pop up again........
HTCP4000PPC said:
ok this is a way to avoid the white screen issue, (Click on Light Config) then open CeleTask and in CeleTask - Tools use Close Screen this will turn off your screen and allow the backlight from turning on when screen turns back on, also remember u need to set your power settings to (Backlight time out on battery 5 Seconds and Backlight on AC can be 1 minute which u never use) and Display time out Never..)
You can also use CeleTask to disable the screen when you make a call, just open CeleTesk when you hit call.
Click to expand...
Click to collapse
These instructions have fixed my device... I got an Elf and I made it my primary phone, and now I´m experiencing new ROM´s in my S621. This problem happens in my device (the S621, of course), and I´m now using NRG remade by Ricky and Stylez, and this problem with the screen seems to be solved with this tip.
This problem does not happen when I use "Kavana remade by Ricky and Stylez" only with NRG and it´s Remake.
Regards
If this isnt helping try just disabling Timeout and set everything else ur way u want.
It is my understanding that some gen8 devices aren't waking up from sleep when they go to sleep in a dimmer screen state. Thanks to a diligent XDA user with a 101, I was able to fix this problem.
To fix this, download SuperDim 1.51dev2 from http://code.google.com/p/superdim/downloads/list
Then go to Menu | Options, and check "Fix no-wake-from-sleep". That's all: it should now work.
My testing indicates that low brightness levels aren't enough to switch the backlight from off to on. So what the SuperDim fix option does is that when the device awakes with a low brightness setting, it first sets 22% brightness, which is enough to activate the backlight, and only then sets the desired lower brightness level.
I reported both the bug and the fix to Archos.
It might be possible to make the fix work without root if there is enough demand.
I would very much like to have a fix without having to root my 101!
I installed and to exactly what u introduced but I still have that issue now. Im realy disappointed. Is there any other methods
yes i also tested it - but somehow i didnt see the feature while waking up - but when going to sleep - this somehow is weird and useless - might be the reason for not working for others
Sleep: press power - screen gets brighter -> get darker -> off
Wake up: press power -> wake up by luck
perhaps recontact the develoeper something might be messed up
(i didnt take the version u mentioned - but the latest maket version wich is newer)
So, let me get clearer on what's happening. You have SuperDim installed, and its "fix wake from sleep" option is activated. And you're still not having the device wake from sleep when the screen is dimmed. Right?
If you can install adb on your PC, or install an ssh daemon on your device and connect to the device via ssh from your PC, you can help me diagnose the problem.
Well I hoped my explanation was clear enough - it is what u said + the point that the function u explained in post 1 doesn't happen while waking up but instead when going to sleep...
Device is on (screen is dimmed, archos option is on) -> press power -> screen gets brighter -> screen gets darker -> off
Device is in sleep -> press power -> wake up by luck
Anyway I got ssh woring thought putty(win) and UD ssh daemon.
ADB is also installed on my pc but i nerver used it
EDIT:
hey - btw i asked u for the cycle funktion some time ago and noticed u implemented it now - and a lot of other things
Thanks for that - somehow i lost track of your app since i had exams
Anyway i just noticed i have the turn-on bug also when I don't use your app sometimes... (even when the screen is not dimmed at all) so there must be another problem also i suppose
Regarding the cycle funktion i noticed a "strange" behaviour:
"night 1" -> 3x cycle -> ends in "day 2" (thast right)
but
"night 1" -> 2x cycle -> "night 1" -> cycle -> ends in "day 2" also and not in "night 2" (so it seems u forgot to ask for the current state while cycling though the modes)
anyway I would be glad if u would make a cycle+ and a cycle-
jw3 said:
I would very much like to have a fix without having to root my 101!
Click to expand...
Click to collapse
PM me your email address. I may have a fix for you.
hello.
I have a similar problem with my GEN 8 A43
I am runing Cyanogenmod bull latest VR since yesterday with GO lancher/
and when i wake up my phone it is only making a sound -"bip" like its turned on, but I dont see anything of the screen...
so the only thing I can do is tern off the device by long press on the power key, and turn it on again...
rarely it is working fine and the regular unlock screen show up...
plese help my to fix this.
thank you !
Moko_Loko said:
hello.
I have a similar problem with my GEN 8 A43
I am runing Cyanogenmod bull latest VR since yesterday with GO lancher/
and when i wake up my phone it is only making a sound -"bip" like its turned on, but I dont see anything of the screen...
so the only thing I can do is tern off the device by long press on the power key, and turn it on again...
Click to expand...
Click to collapse
Have you tried SuperDim, now known as RootDim, and its sleep of death fix option?
Hi peoples, I'm new here.
My htc one is broken but everything still work fine, boot up like normal, the problem is i can't c anything at all. I try to control my phone through a usb stick, but it required me to turn the USB debugging on, the problem is i can't c a thing on the phone.
Is there a way to turn it on from my PC?
P.S my phone is rooted, using mike revolution hd 13.3
Thanks in advance.
frostchill said:
Hi peoples, I'm new here.
My htc one is broken but everything still work fine, boot up like normal, the problem is i can't c anything at all. I try to control my phone through a usb stick, but it required me to turn the USB debugging on, the problem is i can't c a thing on the phone.
Is there a way to turn it on from my PC?
P.S my phone is rooted, using mike revolution hd 13.3
Thanks in advance.
Click to expand...
Click to collapse
when you say that everything still works fine, does that mean the you can unlock the phone or answer calls?
.kronos. said:
when you say that everything still works fine, does that mean the you can unlock the phone or answer calls?
Click to expand...
Click to collapse
Yea, i can unlock, but i can't c anything, I can answer the phone n talk normal. screen just flashing pixel n black area, like black and white tv without signal.
frostchill said:
Yea, i can unlock, but i can't c anything, I can answer the phone n talk normal. screen just flashing pixel n black area, like black and white tv without signal.
Click to expand...
Click to collapse
that's good. you should at least be able to turn usb debugging on. have you tried to get to the bootloader or recovery? does the screen look the same there? if so...
unlock the phone, use two fingers to pull the notification bar down, 1 inch down on the top right side is settings, tap settings, scroll to the very bottom and tap dev options, usb debugging is at about the middle of the phone.
i hope the below images will work for you. i just pulled them off of google searches. i havent used mikey's rom so i dont know if the settings are in the same places but it cant hurt to try
settings - http://img13.imageshack.us/img13/1893/eqly.png
developer options - http://img.wonderhowto.com/img/80/8...tc-one-s-off-using-moonshine-windows.w654.jpg
usb debugging - http://img.wonderhowto.com/img/82/9...tc-one-s-off-using-moonshine-windows.w654.jpg
PS - this forum is for the Verizon HTC One.
.kronos. said:
that's good. you should at least be able to turn usb debugging on. have you tried to get to the bootloader or recovery? does the screen look the same there? if so...
unlock the phone, use two fingers to pull the notification bar down, 1 inch down on the top right side is settings, tap settings, scroll to the very bottom and tap dev options, usb debugging is at about the middle of the phone.
i hope the below images will work for you. i just pulled them off of google searches. i havent used mikey's rom so i dont know if the settings are in the same places but it cant hurt to try
settings - http://img13.imageshack.us/img13/1893/eqly.png
developer options - http://img.wonderhowto.com/img/80/8...tc-one-s-off-using-moonshine-windows.w654.jpg
usb debugging - http://img.wonderhowto.com/img/82/9...tc-one-s-off-using-moonshine-windows.w654.jpg
PS - this forum is for the Verizon HTC One.
Click to expand...
Click to collapse
nope, unless you already enabled dev options you have to go into about phone, software, and tap a million times on one of the lines of info to unlock dev settings.
Then you can turn on usb debugging. Quite annoying.
http://androidtechy.com/index.php/s...eloper-mode-on-htc-one-running-4-2-2-rom.html
nrfitchett4 said:
nope, unless you already enabled dev options you have to go into about phone, software, and tap a million times on one of the lines of info to unlock dev settings.
Then you can turn on usb debugging. Quite annoying.
http://androidtechy.com/index.php/s...eloper-mode-on-htc-one-running-4-2-2-rom.html
Click to expand...
Click to collapse
and have you tried to do that?
.kronos. said:
and have you tried to do that?
Click to expand...
Click to collapse
yeah, but not with a busted screen.
The problem is the screen is kinda in pieces, i can barely pick up calls, i don't think i enable debugging mode bofere hand.
frostchill said:
The problem is the screen is kinda in pieces, i can barely pick up calls, i don't think i enable debugging mode bofere hand.
Click to expand...
Click to collapse
man sorry to hear about this, what do you plan on doing with the phone?
get the screen fixed?
I buy broken phones is why I ask.
Hi,
I am using Note II, stock ROM and unrooted....Only install a few apps like facebook, line, whatapps, viber, candy crush.....everything works fine....
I found a problem and hope friends here can give me some advices...
My screen turn off during answering call but sometimes the screen won't turn back on automatically when I move the phone away from ear....I have tried the following when the screen remains off:
a) open and close the flip cover
b) move the finger to cover the censor and then move away
c) shake the phone up and down
d) turn the phone back and front
All the above actions failed to turn the screen on..I have to press the home button in order to turn it on..
I already check the censor in #*0*# mode and the censor works well...
I am wondering why sometimes can work, sometimes cannot work..
anybody facing the same problem? is it software bugs or hardware failure?
Thanks for help!!
P/S:
I have done censor test in development mode, factory reset and clear call cache.....
Don't know why sometimes still failed to turn screen on....every time my wife complain the screen won't turn on, i told her to dial again, like to those customer service line which need to key-in menu selection 1-2-3-4-5, the screen turn on well to let her key in number....wired....
maybe like 70% success 30% fails...
i also get this most of the time. i talked to 2 reps at local stores and 1 had just recently heard the same complaint about the same phone. it is likely the proximity sensor.my screen even goes dark before i put it to my face so if i wanted to use speaker and / or input anything, i couldnt even if i wanted to. i have had to wait a whole minute a few times before the screen comes back on or reboot the phone. i talke to samsung tech support to ask if i send it in will the sensor be replaced with a known good part and i kinda got the runaround stock answer . ( theyll test and fix or replace with refurb) which means i am likely to get the same issue.
dunno, otherwise great device.