[Q] Android Crashs On/After Phone calls - HD2 Android Q&A, Help & Troubleshooting and Genera

Hi everbody,
i'm a newbie within the Android on HD issue. I have read many threads but i didn't find a solution about my problem.
First i have tried the 'AmeriCanAndroid AOSP HD2 GB2.3.5 CM7' SD-Version and i have the following problem.
If i get or take a phone call the display goes black and there are no reaction on key presses or so on. I think the android is crashed.
Only accu on/off will help
Did anyone have some i idea about the reason.
Best Regards
Superelmo

SuperElmo said:
Hi everbody,
i'm a newbie within the Android on HD issue. I have read many threads but i didn't find a solution about my problem.
First i have tried the 'AmeriCanAndroid AOSP HD2 GB2.3.5 CM7' SD-Version and i have the following problem.
If i get or take a phone call the display goes black and there are no reaction on key presses or so on. I think the android is crashed.
Only accu on/off will help
Did anyone have some i idea about the reason.
Best Regards
Superelmo
Click to expand...
Click to collapse
This issue is known by user, you can digg up on ACA build topic.
You need to put minimal freq of cpu to higher then 128 to possibly fixed it.
Imo, i had similiar issue in latest build, manage to fixed somehow by using Setcpu app or you can do that in system part of Aca build.
You can try this:
Put Governor on Interactive
Put Min Freq on 245 and Max on highest possible(or keep default value).
On setcpu if you use put mark on "set on Boot".
Cope is working hard on ACA build, he will fix issue for sure in next builds.
But if you cant fix issue, for now ill recommend you NexusHD2-Gingerbread V3.0 SD which for me works perfectly(this build is based on kernel Tytung version 11).
Link NexusHD2-Gingerbread V3.0: https://sites.google.com/site/nexushd2android/nexushd2-gingerbread/v3-0/download
Topic link(its in NAND section but he also provide us with sd builds there): http://forum.xda-developers.com/showthread.php?t=905060
I hope this help you.

and please, next time post in the proper forum, there's a Q&A forum for android just for that purpose. and you can always ask in the build's page, because users who have experienced similar problems will be able to answer you faster, since most of them would subscribe to the build's thread.

SuperElmo said:
Hi everbody,
i'm a newbie within the Android on HD issue. I have read many threads but i didn't find a solution about my problem.
First i have tried the 'AmeriCanAndroid AOSP HD2 GB2.3.5 CM7' SD-Version and i have the following problem.
If i get or take a phone call the display goes black and there are no reaction on key presses or so on. I think the android is crashed.
Only accu on/off will help
Did anyone have some i idea about the reason.
Best Regards
Superelmo
Click to expand...
Click to collapse
what radio version do you use?
maybe it will work with a newer radio.
cheers

Related

Walking dead.... I can't be the only one

Ok I'm using newest energy cht rom radio 2.12.50 and shubcraft froyo android build with 384 zimage....
Heres the problem that I have had all week my phone works fine when I am stationary minimal screen freezes great speed but when I get up and walk with my phone and try to use it the screen freezes almost every time then the entire phone freezes. I have also noticed this on elevator and when I step out of my car.. this is weird and I know it can't be just me as its been going on for a week now.
So to sum it up stationary best phone ever...walking phone dead and I wanna slam it on the ground.
Sent from my HTC HD2 using XDA App
try the desire v5's zimage, no freeze at all
Im having same issues,with all the version i have tried, including V5 aparently this screen freezing is a known issue and makes the use of Android in our HD2 very very frustrating.
ive upgraded my SD to a class 6 and still suffering from it
Im wondering if there is a program that causes it or its just the OS...
in any case We have to be patient ,im sure pretty soon the amazing developers will come with a solution.
might be a screen rotation issue
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
miko3d said:
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
Click to expand...
Click to collapse
I've just learned to deal. Its better than SoD's or being in Winmo and having to pull the battery out.
I actually noticed it today as I went from a dark room to a very well lit room so Im with u guys it seems its either rotation issue or light sensor issue andvi have no doubt in my mind the devs will have it fixed in no time just didn't see it mentioned anywhere else so figured it was worth a mention. Thanks all I'm so glad I'm not alone on this one.
Sent from my HTC HD2 using XDA App
when in windows mobile make sure to disable all battery and back light settings and in android change blacklight settings and sleep setting to stay on
I am having the same issue - using ChuckyDroidROM + shubCRAFT CM6RC2, basically when I start moving or even moving the phone the touch screen becomes very unresponsive and sometimes even the hardware buttons don't function properly. At first I thought it was just my device until I saw this post...
Think its a bug with manusfreedoms 384mb ram enabled Zimage dident get this problem using past images.
sure it will be sorted next image release.
I thought i was alone in this case too !
We are not a lot with that screen touch lag, so maybe we did something wrong. Here is what i found so far :
-Changing build don't rix the problem
-tried another radio, another rom...nothing.
I tested 27/07 03/08 cotulla zimage, now manufeeedom 382mo zimage-nopc, the problem is still here.
changed from a class 2 to a class 4 and seems to be worse. (!)
You are right, it seems to be worse when i am moving from one room to another so maybe it is gsensor related.
Right now it is hard for me to type that text,
Don't know what to do... buy a class 10 sdcard ?
I just got my HD2 today and got android set up. I'm noticing the same thing as everyone else with the unresponsive touchscreen. It happens every time I tilt the phone to try to change the screen rotation. Usually hitting the hardware button allows it to respond once again, but it happens quite often.
hey hey hey first and formost i see u guys all hav the same issuse what i dont see is ur device info along with the rom, radio, android verison, and the location ur android is stored ... i have the lates verison of droid v5 also energy with cookie full and my radio is 2.8 i believe android is on the sd card and running smooth ... now that the intro is out of the way hav u guys read what was needed , reason askin i found the thread where the question and answer is... and yes u guys are the only ones... now please do a search go up to the first thread of android on hd2, and good day to u all
Wingtytn, can you be more precise in your answer ? I am a quite long user in Xda, always try to help when i know and i never ask a question wich have been answered somewhere. I don't think i have the noob profile you seems to write. If you think about formatting sdcard, of course i did. I have a 2.08 radio, latest shubcraft build with manufreedom 382mo zimage. My rom was changed to a light android dedicated one, the latest chuckydroid rom. Just don't know what else to do and waste a lot of time trying to fix that from myself.
Sent from my HTC HD2 using XDA App
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
shu8i said:
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks a lot shu8i, i will try an older zimage than the 27/07's cotulla.
Edit : Mmh exact same problem with the 23/07 zimage Cotulla_zImage_CABDET_NOSPEEDDY. That is weird.
I will order a clas 10 sdcard and see what happen...
Try the game ”Runners”. It uses both the camera and the g-sensor and freezes mad anytime, anywhere. Huge affirmation to the idea it's a bug of the g-sensor's or otherwize the screen's drivers.
DuperMan
Me too with screen freezes, i had tried all builds and same result. I think this is a problem with SD access because i noticed more freezes as more apps opened in backgroud.
Try to calibrate the g sensor
Found something ...
try disabling auto-rotation feature (settings -> display)
It works perfectly for me now.
Can you confirm that works for you too?
Did you dind a way to calibrate g-sensor on froyo?
Why the auto-rotation feature hangs so much for us?
Sent from my HTC HD2 using XDA App

(Possible solution) Freezing Issues

hardik119 has found out that going to account & sync and disabling background data has stopped his device from freezing and it has also stopped mine afer 1 hours use. Before it was freezing about every 5 minutes. With doing this I have also disabled setCPU, auto screen rotate and removed gsensor.dll in windows mobile. Please try this out and respond if this has worked for you because maybe we can get a perminant solution. Thanks and also thanks to hardik119 for his extensive testing and possible solutions he is finding all the time Android is usuable on my device hopefully will be for everyone else aswel. Also sorry for opening another thread but there doesn't seem to be any action on hardik119's original thread.
maybe suggested solution works...but...wot is android without data background?
If you disable background data, doesn't that like stop gmail and weather and such updating automatically??
leginag said:
If you disable background data, doesn't that like stop gmail and weather and such updating automatically??
Click to expand...
Click to collapse
Yep...sure does..
the_scotsman said:
Yep...sure does..
Click to expand...
Click to collapse
As has been suggested above...that is kind of /fail.
I'd prefer to live with the occasional few second freeze than not have constant updates.
I applied the RC 7 and my screen freezes are gone. Using this image with mattc nexus 1.0 rom,
http://forum.xda-developers.com/showthread.php?t=756513.
Pretty sure he's just looking for testers to confirm the association. That way developers can narrow down the cause of the issue and possibly fix it. Stop whining about the "solution" he suggested.
Touchscreen freezes still exist
No freezing issues as long as you get the right WM build and android port. Mine is 100% freeze free thanks to the awesome devs here at Xda.
I have auto screen rotate on and still no freezing or SOD. I am using Darkstone's 2.1 build full time now.
Fyi.
Sent from my Hd2 using XDA App
Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)
Thanks for the tips currently using maths 1.5b Rom with 23rd kernel
Hspl3 & radio .12 aswel also tried with calibration on the g sensor in winmo and also deleting sensor.dll also using energy light but have also tried with Miri light the only build I haven't tried so far is the one you mentioned so will give it a go. Thanks
Sent from my HTC Desire using XDA App
Hi I can confirm the disable background sync fix works for me.
Running
- Android O.K. v2.6 [Kumars Leo Touch Premium]
- Mattc 1.6
- Radio 2.12.50.02
LondonTownGuy said:
Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)
Click to expand...
Click to collapse
where to fing the original zimages not the overclocked
touch screen freez reason
I nenarly identified the reason of touch screen freezing ,,it is possibly in the touchscreen kernel ,download figure race from market and the touch screen fresez due to random pess of touch screen with both hands ,I think this is the main problenthl
hoss_n2 said:
where to fing the original zimages not the overclocked
Click to expand...
Click to collapse
http://oe.netripper.com/files/htcleo_autobuild/
23rd august is very stable, you also get usb sinc working and HTC sync.
You need to download the corresponding modules to extract the BCM and TUN files for wi fi to work.

[Q] Auto Reboot/Restart Issue/problem on android boot

Hi there! after googling a lot, and looking here and there around the forum's threads, i found no solution to this one....
I'm quite new at all this so i might not make myself clear enough.
I am using stock winmo HD2 Rom (the october 2010 ROM Update for EU) with 2.15 radio version.
So far have tried only Mdeejay's roms yet still i will try the rest to confirm the problem exists.
So on the first load of any of the version's i've tried (even after swapping kernels and trying different sizes of data.img file) android boots perfectly, runs amazingly smooth, fast, battery long lasting and so on (thanks to MDJ for all this), yet! i've seen many people have the same problem: After some random time (maximum of a few minutes) the phone reboots automatically thus taking you back to winmo.
It's not that i don't like winmo, it's just that i thought someone had found a solution to that.
So.... any clues?
mine is more of, turns off automatically. I thought the battery is dead (or the batt meter/notification is inaccurate) only to find out that it just turned off automatically.
have you tried checking the Q and A section rather than the Development thread???
2 solutions = Format sd card. if problem still persists than you need a custom winmo rom. I suggest elegancia. My setup in my signature runs without a hitch
iv never expierience this, i do get the coma bug, but iv heard a newer radio fixes that so im about to update mine
jose makalolot said:
have you tried checking the Q and A section rather than the Development thread???
Click to expand...
Click to collapse
Sorry, was in a rather hurry and mistakenly posed it here, please admins could you move this?
I have the same problem.
At first the reboot was performed afeter a while, from 30 to 15min, and then it quickly began to reboot after a short time, around 5min. Now, the reboot is performing during the loading process of Android.
My winmo ROM is an Energy 23699 from 24th Nov, but the problem was present while I was in Energy ROM 21xxx from October one month ago.
My Radio is 2.07.50_27.2 flashed 5months ago, no issue with it.
My Android ROM is the llast Froyo with Sense from Darkstone (17th october).
I didn't formatted my SD Card because I wanted to know if there was some boot log somewhere in order to check the problem.
I can't use Android on my HD2 I am sad..
xnnc said:
I have the same problem.
...
I can't use Android on my HD2 I am sad..
Click to expand...
Click to collapse
I am satisfyingly using android on my HD2 using a stock ROM.
I guess that the problem exists on using some of Android Kernels on some HD2s
I found my solution by using "evo carbon remix" currently using v.0.3.1 with Hastarin r8.2
I have not updated nor nothing, having a great battery life and all looking more or less the same as Mdeejay's rom.
I hope this works for you too!
@jsacp : Thank you for the advice, I will try later when I will 100% switch to android.
Well I think I have found the problem. My data.img was 256Mo and I have installed a lot of applications lately, maybe I ran over memory. I replaced the 256Mo data.img with the 1Go data.img which was present in the archive of my Android ROM, and Android didn't have reboot since then. But, of course, I lost all my setup, preferences and applications, I knew it before doing the jump, but glad to see Android back on my HD2
Hope it can help.
Did you notice if your phone feels hot at all? Last time I had a reboot I was downloading stuff with the phone plugged in and it got really hot and restarted. Was an older kernel tho and I think it happened when ppp connection got stuck.
Sent from my HTC Desire using XDA App
When I undervolt my phone too much, it starts randomly rebooting as well.
My guess is that mdeejay's undervolt is too much for your phone.
Try a ROM with hastarin's kernel, it will probably end the random reboots.
How to fix Android phone automatic rebooting problem
Recently my phone got into trouble, it kept restarting. I had to get out of the boot loop error. My phone was HTC Desire 1818 runs on Android Bravo. I was really frustrated because I had many valuable phone contacts in my phone. I searched everywhere on the, I couldn't find any solution at that time, so the only solution in front of me was to format my phone!. Oh.!.. Error fixed by formatting, but my all data on the phone including my valuable phone numbers lost. After 7 or 8 months my phone again got in to the same auto restarting trouble when I installed WhatsApp in my phone. It was really irritating me to encounter these sorts of wretched errors on Android. But at this time I found a good solution. This solution is available and applicable for all Android phones, and Tablets regardless of models and companies.
The solution is simple, Simply Switch on your Android device in 'Safe Mode'
See the Explained Tutorial on How to fix Android auto-rebooting problem going below link
mobihackman.in/2014/02/fixing-android-automatic-repeated-booting.html

NAND Builds: 2sec Wakeup LAG

Hello and sorry to open a new thread but i find that problem on every build!
Have you notice Wakeup Lag in all Nand builds?
It whant 2 seconds to light up the screen after i press the power (or any other) button.
Also the same lag ii take from sensor when i make a call.
Is that Kernel problem or is from MAGLDR?
I try SD and NAND build's.
Also i find that thread but....?
http://forum.xda-developers.com/showthread.php?t=813000
I have an euro HD2.
Many Thank's for reading and i wish for a fix..
Happy new year to ALL!
Video of my problem:
ausdim said:
Hello and sorry to open a new thread but i find that problem on every build!
Have you notice Wakeup Lag in all Nand builds?
It whant 2 seconds to light up the screen after i press the power (or any other) button.
Also the same lag ii take from sensor when i make a call.
Is that Kernel problem or is from MAGLDR?
I try SD and NAND build's.
Also i find that thread but....?
http://forum.xda-developers.com/showthread.php?t=813000
I have an euro HD2.
Many Thank's for reading and i wish for a fix..
Happy new year to ALL!
Click to expand...
Click to collapse
Flashing MDJ's Revolution HD Super Light v1.0 NAND ROM fixed this issue for me, it's completely unnoticeable on my HD2 now. I had a little bit of lag on the non light one, and always had it on any other ROMs I've tried. So glad it's fixed now
Even with wifi on it doesn't lag, I'm on an euro HD2 also
I have the same problom but someone doesn´t have this problem.
Many of the kernals had this issue in the past for me on the hd2. Good news is iv never had this on gingerbread releases.
Sent from my HTC HD2 using Tapatalk
This doesn't belong here, it belongs in discussion or questions forum.
Just to add though, I haven't experienced any wake up lag.
I still have this issue with my HD2...Sd builts takes about 1 second lag on wakeup...
Nand builds have less than 1 second lag with a green line on the screen... I might try the GingerBread build to see if the problem is fixed!
Just recorded a video (ignore music, heh) showing how this lag is eliminated with my current build. Wake up lag and during call "black screen" is no longer an issue. Just noticed that proximity sensor doesn't work while having the speaker "on" during the call as you can see in the video, but I guess this is normal.
premikkoci said:
I have the same problom but someone doesn´t have this problem.
Click to expand...
Click to collapse
So all the device's is not the same?
Btw i use:
Radio 2.15.50.14
HSPL 2.08
And i install MAGLDR after my Custom cooked winmo rom.
I have the same lag in EVERY build!!
Thank's
ausdim said:
So all the device's is not the same?
Btw i use:
Radio 2.15.50.14
HSPL 2.08
And i install MAGLDR after my Custom cooked winmo rom.
I have the same lag in EVERY build!!
Thank's
Click to expand...
Click to collapse
Even I have this wakeup lag while turning on the screen and during calls on EVERY build. Tried almost every rom on SD. Haven't tried Gingerbread yet. This is the only reason for me not switching entirely to Android. Previously the SD card was blamed for this. But if its still there with the NAND, this should be a kernel issue. The minimum lag was with the RAM built, but nowhere close to WM.
I guess the DEV's never had this issue, so they never fixed it. But as far as I know, there are many many people having trouble with this and still waiting for a fix.
I have this issue with my EU LEO. Is it specific to the EU hardware?
Yeap! It's very weird but yes...HD2 devices are not the same!
As is said on other threads ...My friend gave me an EU HD2 and Android didn't lag on wake up at all!!!!!!!!!!
I upload a video to show my proble in first post.
Sorry for the bad video quality.
we all have the same problem mate! Ok...sorry...the most of us!
ausdim said:
I upload a video to show my proble in first post.
Sorry for the bad video quality.
Click to expand...
Click to collapse
Yeah, I see that extra 1 sec delay. Try this ROM, see if it changes anything.
http://forum.xda-developers.com/showthread.php?t=893675
And this lag gets worse, if something is getting downloaded or installed and I try to turn on my screen. This really sucks when you have to use your keyboard in between the calls if you are not on speaker.
This will be present in every single build.
It needs to get fixed on kernel level...
To tell you the truth guys! I don't mind that 1 second lag on the wake up... My built is the Nand Froyo something(cmn 6.1 nand) I got the BEST BATTERY DRAINAGE.... Before 2 days i had 75% and today i left with 25% with a few calls,sms,wifi!!!! This ROCKS!!!!
secano said:
Yeah, I see that extra 1 sec delay. Try this ROM, see if it changes anything.
http://forum.xda-developers.com/showthread.php?t=893675
Click to expand...
Click to collapse
Many Thanks but i get the same results. I just reflash that build to see but nothing changed.
kundanjuit said:
This really sucks when you have to use your keyboard in between the calls if you are not on speaker.
Click to expand...
Click to collapse
+1 for that. The most annoying think.
projection said:
This will be present in every single build.
It needs to get fixed on kernel level...
Click to expand...
Click to collapse
Yes that is the true but how is gona fix that? Cause the Android cookers may dont have that problem, so didnt care a lot.
I see the US hd2 doesnt have that problem.
I also try your at: http://forum.xda-developers.com/showthread.php?t=897191 with the same results...
Thanks.
No tmous users don't have this issue at all! Maybe we need to change Countries LOL!
arkatis said:
No tmous users don't have this issue at all! Maybe we need to change Countries LOL!
Click to expand...
Click to collapse
Assumption is the mother of all ****ups.
Wait for it to be fixed in kernel, or get the source and fix it yourselves.
Maybe we need to change Country! Kapish?

[Q] Phone is frozen after a call

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.

Categories

Resources