Guys please help me, i have the latest rom cm9 gingerbread made by Epsilon, and i have a great problem (i had this problem on all custom roms, miui, cm7 etc.) after a call, if the other person that i was engaed in a conversation does not hang up, i canno't get the screen back ON. the only workaround is to remove the battery and boot up again. any ideeas? it might have someting to do about the proximity sensor... i think.
Sorry if this problem was discussed on another topic, i could not find any relevant answer. thnx in advance.
Do you have a screen protector?
Edit: But why on dev section?
nope, don't use one.
didn't pay attention
I think the Epsylon's CM7 builds have an option to force the screen on after a call. This should do the trick.
Thnx very much. Haven't thought about that till now. I'll come back with a result. Hope it works.
@robertocav
Got it fixed yet ?
Since a couple of weeks i have the same problem and its pretty annoying.
I'm running CM7.1.0 jordan
Related
Hi all.
Im having a bit of a problem with my HD2. Whenever im in a call if i adjust the volume the earpiece goes dead, starts making a quiet buzzing noise and cuts the other person off. If you want to call the person back the phone wont let you back into the phone menu, and starts to act all strange and slow and you have to pull the battery off. I have been searching the forums for a solution but i havent found one yet. I have even flashed 3 different Roms to see if that fixes the problems but no.
Please HELP!!!
Adam.
i had exactly same problem, so tried another rom. and everything ok. but i did do a task 29 first.....try doing that then re-flashing your rom.
Don't forget to change radio to a compatible one with the rom.
Cheers you guys. At least im not the only one who has had this problem Phew. I will try what you both have said and see if it solves the problems! Thanks again.
YAY Fixed. Cheers you guys for all your help!!
Adam
adamlayzell69 said:
YAY Fixed. Cheers you guys for all your help!!
Adam
Click to expand...
Click to collapse
please specify what solved the problem for you so that other people going through the forum and its threads can get some idea and so that this thread gets meaningful "closure".
lets try to avoid using the forum as personal tech support, and instead add information where necessary so that it can truly be the knowledge base it aims to be.
Don't get any info
Fido. I don't get any info from this thread. This user has opened up a thread and after some time he is saying that Ok my problem solved. What this thread can give others in terms of knowledge and info - Nothing but time waste.
IF somebody know the inverse option on photoshop when black comes as white and same for all colors it happens to my hd2 after a while when I unlock is cuz I press harder on it or is a soft problem?
I've seen a few people reporting this, luckily haven't experienced it myself. Nobody seems to have figured the cause as yet, but a reboot solves the issue (until the next time of course).
I had inverted colours recently. Was weird... I was on the phone when it dialed another number (possibly i did it with my cheek cos i'd been switching back and forth from keypad and loudspeaker settings). When i hung up my phone went strange with the 'inverted' look.
I'd love to know why because it's the only stability issue I have now.
Regards
sp33dy_gtx said:
IF somebody know the inverse option on photoshop when black comes as white and same for all colors it happens to my hd2 after a while when I unlock is cuz I press harder on it or is a soft problem?
Click to expand...
Click to collapse
This happened to me as well. I had to give it a restart. It happened after I waked the phone from screen off. It would be nice to find a fix for this.
Edit: we are not alone: http://forum.xda-developers.com/showthread.php?p=10851646
+1
Hope it is just a soft prob and not a sign of hardware fail.
TheATHEiST said:
+1
Hope it is just a soft prob and not a sign of hardware fail.
Click to expand...
Click to collapse
Haven't tried it myself, but they say taking a screenshot creates a normal looking one.
So I'm afraid it is a sign of hardware fail. The bad thing is my phone is barely 2-3 months old.
edi: could you all please post the kernel you have. From what I've read, it seems an MDJ kernel problem. I used MDJ 0.2oc
I had this a few times before Xmas on one of Darkstones SD builds, only did it 4 or 5 times though. Taking a screenshot didn't work, just got a normal screen.
Since using NAND builds I've not come across this problem once, so I'm guessing the problem is Software/Kernel related rather than Hardware, which should come as a relief.
Sent from my HTC HD2 using XDA App
Did anyone find a fix for this?
I am using prj Clean Desire v0.3.2 (NAND) [Kernel: prj v0.4] and am getting the same issue, unlock the phone and everything is inverted but taking a screenshot with drocap2 comes out perfectly normal. It is happening every few days now.
I am going to try a different ROM and see if it still occurs.
Never had inverted colors in WinMo, with first Android SD releases I've had that problem quite often. But since flashed NAND Android 45 days ago haven't seen any inverted colors yet.
Sent from my HTC HD2 using Tapatalk
Had this problem today for the first time while in a call. A reboot put it back to normal...
Any known reason?
hyperdroid 2.1.0
I get this error occasionly on hyperdroid 2.1.0 but it happened to me again today.... its also happened on miui. No one found a solution or cause?
I have had this on various occasions and there i various topics on it but with no resolution of any answer as to possible cause.
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705
Thanks, I will try that out tonight and report!
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.
Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!
Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...
need help also
Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?
xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time
Hello Everyone!
I just want to say some words about my experience with Insanity.
I got my sgs ~3 months ago and i tried a almost all the cooked roms.
I started with darky, that was the first I've installed then I found this forum and tried almost everything(only GB roms).
but I sticked to insanity cause thats all i want very simple only a few apps are installed and its kinda fast.Then I realized that this blueish screen is awful. I started to look after kernels with voodoo color. first i tried glitch that caused my first BSOD i was very scared but I then i was able to fix it. Then I used Fugumod for a while that was allright original CM led notifications worked perfectly it was fast but I had some problems like when I charged my phone the screen became funny i have to pull off the cable to be able to write a sms message. Then the new neo18 kernel came out that's almost perfect led notifications work voodoo color gives amazing screen and until now my only problem is when I'm outside so the temperature is low like minus 1-5 the android.com process gives FC and I cant see my contacts.
So i really like insanity as a rom but i want to hear others experience about it.
So far my problems are:
Viber stopped working i dont know why i cant remember what change made it cause lot of things happened changed to new insanity cm51 as i remember new viber came out. I can't get it work with stock fugu or neo kernel
The other big problems is sometimes when i answer a call they cant hear me or i cant hear them for the first time then i call them back and everything works fine.
Can somebody give me any advice to solve these problems?
please dont be rude I'm not a complete noob but Im not a developer either.
Thank for anyone who helps
PS.: if you give me any advice whats the best kernel for insanity in your opinion i will be happy
So I switched to GB from WM65 and found it's pretty slow but usable. I don't have time to switch back to WM65 so I'll stick with GB.
Now, one big issue I have is the phone app (not wifi app, just plain phone). When I dial a number, the screen goes black to prevent pressing the wrong button with your ear etc. Problem is, I can't get back to the screen, meaning I don't have access to the dialpad. Annoying when you're on queue and you need to press a key to get to a menu... like repeat a message on your messagebank for instance.
Second issue, is after the call, the phone is frozen for about a minute or two. Nothing responds. Then it comes back alive.
I haven't found any threads on this, though users seem to complain about wifi calling, which is not my case.
Anyone has seen this ?
Txs.
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
I had this problem with almost every gingerbread build on my HD2.
Im not sure what's causing it, but i fixed this issue by installing screebl lite from play store. While this app enabled, phone would wake up normally after a call in 99.9% of the cases. You should try the same.
Strangely, i don't have any issues on ICS or JB roms.
Marvlesz said:
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
Click to expand...
Click to collapse
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Boags said:
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Click to expand...
Click to collapse
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Marvlesz said:
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Click to expand...
Click to collapse
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Boags said:
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Click to expand...
Click to collapse
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Marvlesz said:
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Click to expand...
Click to collapse
Right, I'll go with the hypothesis that a dirty screen hinders proximity sensors. That should affect a black screen DURING a call (issue I'm also facing) but that should not affect the phone once the call is terminated, should it ? What I mean is, in my case, when I hang up a call, I can't use my phone for a couple of minutes, until it comes back to life. I will get a new "screen protector" and see what happens in the meantime though.
As for a hotfix, seems odd there is none out there. Thanks for trying.