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.
Related
I've had this problem for awhile now, and i was just thinking it was some 'quirk' with the T-mobile ROM, but recently i've installed the new ROM, and i'm getting the exact same problem, so i really am confused now :/
(I haven't installed any apps, or hacked the device in anyway btw)
Basically, i'll be composing a standard TXT, and the brightness on the screen will go to maximum (as if it's been plugged into charge) then when i come to pressing 'send' it does nothing. Then i close the messaging app, then whatever i try to load, it comes up with a 'this program is unsigned' error, all the txt on the screen does white, and basically everything looks screwed.
If i go into task manager and close the messaging app, then the screen goes back to its normal brightness, but the application errors still continue.
The only way to get around this, is by rebooting the device, but then once it's reloaded, it seems to randomly loose my latest TXTs/e-mails!
Really starting to annoy me now!
Does anyone have ANY Idea what might be causing this, or experienced this before?
Any help appreciated!
Thanks
*bump*
No one else had a similar problem?
OK and another thing ive noticed, when i go to the lock options, even if i type in an incorrect PIN, or even if i click 'ok' it just bypasses the lock screen! How s**t is that!
I've got no idea what's up with this phone, but i'm really pissed off with it now, i'm sending it to t-mobile for their engineers to look at, but im 99% sure that they'll run a few simple tests on it, and declare that it's totally fine, then send it back to me... GRRRRRRRR :evil:
hey same thing happening to me too.
mine too sometimes goes to full brightness while composing SMS. If u then switch off the phone(by power button), it comes up with a message box asking for driver. In the end, i hv to reboot the device.
And the poor part is that it doesnt happens all the times. This has started happening to since I have upgraded to latest imate ROM(I have O2 Exec). I had similar problem with the latest Qtekk ROM.
The only thing i d not installed was 'ms_.nbf' from both of the ROMs,which is actually represent the 'extended rom' of HTC devices.
kdskamal said:
hey same thing happening to me too.
mine too sometimes goes to full brightness while composing SMS. If u then switch off the phone(by power button), it comes up with a message box asking for driver. In the end, i hv to reboot the device.
And the poor part is that it doesnt happens all the times. This has started happening to since I have upgraded to latest imate ROM(I have O2 Exec). I had similar problem with the latest Qtekk ROM.
The only thing i d not installed was 'ms_.nbf' from both of the ROMs,which is actually represent the 'extended rom' of HTC devices.
Click to expand...
Click to collapse
Ahh, well i'm glad im not the only one!
I'm going to assume it's a hardware issue..... possibly..... because ive had the exact same problem on the past 2 t-mobile ROMs. So annoying :S
why dont u give a try to other ROMs like imate, qtekk. May be, you do away with this 'annoying' problem somehow
kdskamal said:
why dont u give a try to other ROMs like imate, qtekk. May be, you do away with this 'annoying' problem somehow
Click to expand...
Click to collapse
Well i've had problems with the past 2 T-mobile ROMs, so i'm thinking that it's not really an issue with the software.. but i really dont know. Have you fixed the problem, or are you still getting it?
Pooper said:
kdskamal said:
why dont u give a try to other ROMs like imate, qtekk. May be, you do away with this 'annoying' problem somehow
Click to expand...
Click to collapse
Well i've had problems with the past 2 T-mobile ROMs, so i'm thinking that it's not really an issue with the software.. but i really dont know. Have you fixed the problem, or are you still getting it?
Click to expand...
Click to collapse
today, i installed the latest qtekk rom with ms_.nbf(extended rom) stuff allowed to install.
Now, from past 2 days,this has not happened. yay
so far, so good
Hmmmm interesting
How frequently did you have the problem before? + can you keep me updated if you get the same problem again on this new ROM? Thanks
Pooper said:
Hmmmm interesting
How frequently did you have the problem before? + can you keep me updated if you get the same problem again on this new ROM? Thanks
Click to expand...
Click to collapse
I used to suffer from this problem at least 2-3times a day. And it was very frustrating too.
Till now, not a single problem with latest qtekk ROM, FABULOUS is the word for it !!
No problem at all till now. Popper, you should give it a try now
kdskamal said:
Pooper said:
Hmmmm interesting
How frequently did you have the problem before? + can you keep me updated if you get the same problem again on this new ROM? Thanks
Click to expand...
Click to collapse
I used to suffer from this problem at least 2-3times a day. And it was very frustrating too.
Till now, not a single problem with latest qtekk ROM, FABULOUS is the word for it !!
No problem at all till now. Popper, you should give it a try now
Click to expand...
Click to collapse
Hmmm I might give that a go. Which ROM contains all the network setting information? Was that the "ms_.nbf" file you mentioned?
Thanks
yes, its the ms_.nbf which contains the network settings. In other words, it the one, which represents the extended rom of your device
kdskamal said:
yes, its the ms_.nbf which contains the network settings. In other words, it the one, which represents the extended rom of your device
Click to expand...
Click to collapse
Gotya
Well that crappy problem has happened again today, so in a minute im gonna install the latest QTEK ROM, fingers crossed
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?
hi all
i have been using nand android builds since day one , and in most of the builds i am having this same issue
sometimes when i receive a phone call the system just hangsout and then gives me a force close msg for the phone application !!
either way , if i force close or not , no further phone calls can be answered and the phone will freeze for about 30 seconds with every call
also when this happens the volume buttons wont modify the volume for the media anymore and the phone wont give any sounds
so is there something i can do to get rid of this ?
i tried android builds based on 2.3.3 and 2.3.4 , miui , sense , no sense , and i have this issue with all of them
again , it happens like 10% of the times
hope i get an answer to this
I want to ask what exactly rom are you using (does it use newest tytung r10 kernel?) and tell you that I have not been experiencing these issues with NexusHD2 2.8 rom (2.3.4).
fpu
i tried typhoon , rafdroid , ndt miui , and plenty more and i think typhoon and ndt miui has the latest kernel
have you ever tried receiving a phone call while the camera application is running
this seems to trigger the issue many times , not always tho
if you have the call recorder running turn it off. it was causing me lot's of problems.
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
domenukk said:
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
Click to expand...
Click to collapse
+1 Same ****...
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
I just recieved a phonecall without problems.
Flashed the .12 radio from http://forum.xda-developers.com/showthread.php?t=611787&highlight=radio
however... My rom feels a bit slower now.
I am playing with it now.
Maybe clearing Dalvik cache will help. Or the issue comes back... Will see.
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Synthezys said:
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Click to expand...
Click to collapse
Switching Radio to something.12 did the trick for me.
No problems for two days now.
domenukk said:
Switching Radio to something.12 did the trick for me.
No problems for two days now.
Click to expand...
Click to collapse
Leo_RADIO_2.12.50.02_2 - is this good?
Synthezys said:
Leo_RADIO_2.12.50.02_2 - is this good?
Click to expand...
Click to collapse
Yes that's it. Works fine for me
Mea culpa just today I had the same issue, for first time.
It's nothing major and reboot made it work fine again, but breaks my belief in HD2 as perfect, native-like Android device.
[email protected] said:
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
Click to expand...
Click to collapse
Beside changing of radio, THIS seems to be interesting.
I'm on MAG but considering switching to cLK (for many reasons - fastboot support being one, second that I don't need 99% of MAGLDR features).
Let's see how it all pans out ;-)
fpu
It just happened again! On the new rom... :/
There is a thread, however, stating that it's due to skype.
This can very well be true.
http://forum.xda-developers.com/showthread.php?t=1164058
but I need skype to stay on contact with my girlfriend... why can't android support skype natively instead of sipthings? -.-
Well still... anyone tried clk (instead of magldr) and skype?
Disable "Audible touch tones". It's under Sound in Settings, it did the trick for me.
I thought this was against robot voice?
well what ever. let's give it a try. Thx
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
An0n1mUs said:
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
Click to expand...
Click to collapse
For me recieving a call does nothing but a very bad noise. hd2 nearly freezes after that. I cannot hang up most of the times. If I somehow manage to, phone app forcecloses and connection cannot be reestablished until I pull out the battery...
Good old Robotvoice. I wish that was my problem.
i have switched to cLK about 3 days ago and till now i have got no problems at all
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
I can't hang up my phone, for some reason. If I call someone, and they don't answer, it goes to voicemail, and I can't hang up the phone. I tried pressing the red button, but the screen doesn't come on, and the only thing I can do after that is to pull the battery.
I'm using the ROM from this page:
http://forum.xda-developers.com/showthread.php?t=953078
Firmware Revision Number: 2250.09.07491.HD2O
Radio Software Version: 5.71.09.02a_22.51.50.21U
I don't know if this information is helpful, but I hope someone can help me out.
Thanks!
Hi!
Should be easy to fix Go to settings, brightness, turn off automatic adjustment, restart phone - done!
Please let me know how it goes!
/Anders
Hi
Thanks for the advice, but it didn't seem to work.
The call works and all, but the screen is still blank, and pressing the buttons does nothing. I also tried holding on to the buttons, but it still didn't work.
It should be noted, however, that the call actually does go through, and I can talk normally. If the other party hangs up, I get my functionality back.
Really weird.
*edit* I've also tried other ROMs, and this occurs on pdaimatejam's ROM as well. I changed to this one because I thought there was something wrong with the WP7 Tango. It worked for a while, and randomly stopped working on pdaimatejam's ROM.
Now that is really strange! Have you had problems like this using Android or WM?
/Anders
No, I haven't. It's not a hardware issue, if that's what you're thinking.
I'm pretty sure it's got something to do with WP7. I just don't know what. Hmm.. Maybe I'll go try flash Mango and see if the problem's still there.
I had that issue but with HD2Owner ROM's, but with Pdaimatejam ROM's (7.3 or 7.5) it seems solved. Try it.
myself11 said:
I had that issue but with HD2Owner ROM's, but with Pdaimatejam ROM's (7.3 or 7.5) it seems solved. Try it.
Click to expand...
Click to collapse
I've tried Pdaimatejam's 7.5 and 7.8. Still didn't work. Hmm. Something's really weird about this.
markiemice said:
I've tried Pdaimatejam's 7.5 and 7.8. Still didn't work. Hmm. Something's really weird about this.
Click to expand...
Click to collapse
I have the same problem, have you solved the problem or not?
rafa89 said:
I have the same problem, have you solved the problem or not?
Click to expand...
Click to collapse
No, I haven't. I just live with it for now. I don't call people until I'm sure they're going to answer. If they don't, well, lucky the phone boots up fast.