Database Info

[Possible DEFECT] UPDATE! (Sep. 16, 2011) Touchscreen Responsiveness Issues

Ok I've been meaning to make this thread for a while now but held off on it assuming it was just my phone, or maybe even just a small batch of phones. But now that I have noticed a lot of people having the same problem as mine the I feel that it should definitely be addressed and hopefully more people will be more aware of it.
Basically the problem is with the touchscreen while I am typing. Certain keys will just "lock" up and become unresponsive. The most noticeable key would be the "Delete" key. It won't work and would be completely unresponsive, only way it will come back in working form is if I just simply wait, or close/re-open the keyboard. Other keys get affected as well, such as other vowels and the letter "O" is prominent as well. But pretty much almost every key gets affected here and there, the "delete" key is just the most prominent and happens more than the others.
Now the obvious first act would be to pin-point the problem. Various possibilities would be:
- Keyboards fault
- Kernel/ROM's fault
- Or if it's just a manufacture defect
First I thought it was just the stock Android KB's problem, so I'e literally tried almost every mainstream KB out there in the market such as:
- SmartKeyboard Pro
- SwiftKey X
- Flex T9
- Swype
- HTC's Touch Input
- Go Keyboard
And with all of those I still experience the problem. So I counted out the possibility of the KB being the cause of the problem. So then i figured it was the ROM itself, but I've tried numerous ROM's such as Virtual Fusion, Virtual Unity, speedDEMON MIUI, CM7 and it's numerous RC's/Nightly's. And the problem still persisted with all of those ROM's.
The only ROM's I know it doesn't happen on is Royal Ginger 2.1 and the stock T-Mobile mySense build. Also I've had other MT4G's in the past that did not have this problem on any ROM.
That confused me as now I can't tell if the problem is software or hardware related.
Thus, I called TMO for a warranty exchange. The phone I had where the problem happened was good screen with BAD eMMC chip. The new one I just received is good screen with GOOD eMMC. With my new phone the problem still persists.
So basically I would just like to get to the bottom of this problem and see if anyone else is having this problem, and if so please post your issue here as well. I would really like to know if this is just maybe a kernel issue with the latest MT4G kernels that are out, or if it's just another one of the plethora of hardware problems that haunts the MT4G.
====UPDATE====
Okay, so there seems so have been a fix floating around for this and it was DEFINITELY not what I had expected. Credit goes to the dude that found it and for jberg22 for bringing it to the attention in this thread. Here is the thread that you can read up on. I'm not sure if it's a 100% fix but it has been a fix for some. Try it and let us know what your results are! It would be nice to know if this has worked for people with this problem. Here's a picture of what it looks like on our MT4G thanks to Mathato!

Glad you decided to post about this. Since more and more people are having touchscreen issues, it's definitely becoming a problem. The mystery is why the problem occurs on all ROMs except for RG. Hopefully more people will post here with their issues and we can get this thing nailed down!

TeeJay3800 said:
Glad you decided to post about this. Since more and more people are having touchscreen issues, it's definitely becoming a problem. The mystery is why the problem occurs on all ROMs except for RG. Hopefully more people will post here with their issues and we can get this thing nailed down!
Click to expand...
Click to collapse
I had that problem with my first mytouch 4g and then ended up bricking it trying to unroot it...but i've never had a problem with this one.

never had any problems like this before... did it happen over time? or immediately after you flashed the ROM?

saranhai said:
never had any problems like this before... did it happen over time? or immediately after you flashed the ROM?
Click to expand...
Click to collapse
Pretty much after a day I started to notice it with VU. But it's usually instant.

I've been complaining about this for a while. Since it doesn't happen on stock rom I don't know wtf to think.
Sent from my HTC Glacier using XDA Premium App

I've definitely seen this,
Some keys lock,
The answer button when receiving a call,
The pull down bar not sticking, for example able to grab it but once sliding it down an inch it goes right back up.
All this on ONLY VU.
No other ROM does this to me, but I stick with it because I love unity!
Sent from my HTC Glacier using XDA App

I wonder if this is happening on 2.3.4 builds only?

my2sense said:
I wonder if this is happening on 2.3.4 builds only?
Click to expand...
Click to collapse
I'm assuming the ota 2.3.4 doesn't have this issue?
Sent from my HTC Glacier using XDA Premium App

Phateless said:
I'm assuming the ota 2.3.4 doesn't have this issue?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Good question. I have yet to try the official TMO OTA ROM. But I would assume the problem would disappear in that build. I'll probably flash it to check one day.
Sent from my HTC Glacier using XDA Premium App

If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.

Jack_R1 said:
If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.
Click to expand...
Click to collapse
I agree. I went back to stock, almost hoping to see the issue appear again, but it didn't.

Jack_R1 said:
If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.
Click to expand...
Click to collapse
I would tend to think so too, but I've run VU since the day it was released with no issues, yet Mackster can't run that ROM because he's unable to type. I think it's possible that within the MT4G production run, there are slight H/W differences somewhere within the phone's internals. I mean, the problem occurs on almost every ROM for him (everything except RG). The problem seems a little more complex than a simple ROM bug.

This happens on my phone as well. Thought it was just me... it didn't happen on stock mySense, or RoyalGinger 2.1. I'm currently running RoyalGinger 3.0 & it hasn't happened yet. It DOES/DID occur on CM7 (nightly & stables), MIUI, Virtuous unity & virtuous fusion ...
I currently have a mt4g with the good screen & bad eMMC chip...
Sent from my HTC Glacier using XDA App

cbutt said:
This happens on my phone as well. Thought it was just me... it didn't happen on stock mySense, or RoyalGinger 2.1. I'm currently running RoyalGinger 3.0 & it hasn't happened yet. It DOES/DID occur on CM7 (nightly & stables), MIUI, Virtuous unity & virtuous fusion ...
I currently have a mt4g with the good screen & bad eMMC chip...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
God damn dude, same exact situation as me. What are the odds?? Lol. Weird ain't it?
I have a new phone now with good eMMC and it doesn't happen nearly as much, but still happens a little.

mackster248 said:
God damn dude, same exact situation as me. What are the odds?? Lol. Weird ain't it?
Click to expand...
Click to collapse
I don't think it's chance. I think we're onto something here. On phones that have the touchscreen typing problem, it occurs on every ROM except for stock and RoyalGinger. So the question is, what's different about RG? What does it have in common with the stock OTA ROM?

I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.

Jack_R1 said:
I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.
Click to expand...
Click to collapse
How is it based on stock btw? Because isn't RG pretty much like 99% CM7? And I think he said his kernel is based off of Zinx's?

Jack_R1 said:
I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.
Click to expand...
Click to collapse
I think you're thinking of RoyalGlacier, which is based on mySense. RoyalGinger is an AOSP-type CM7-based ROM. I think you're right that this issue may be driver related. It'd be nice to figure out what's different about the stock and RG drivers, compared to all other ROM's hardware drivers.

TeeJay3800 said:
I think you're thinking of RoyalGlacier, which is based on mySense. RoyalGinger is an AOSP-type CM7-based ROM. I think you're right that this issue may be driver related. It'd be nice to figure out what's different about the stock and RG drivers, compared to all other ROM's hardware drivers.
Click to expand...
Click to collapse
I think for the purpose of testing we should roll back to a 2.3.3 build of cm7, because I never noticed this until a couple months ago.
Sent from my HTC Glacier using XDA Premium App

Annoying headset switching to mono

I have an annoying problem with my Inspire. I am running the latest CM7. No matter, because it did this on any/all iterations of CM7.
When listening to music with a stereo headset, every now and then, the phone has a glitch where it will for no reason turn the output signal from a stereo signal into what sounds like a mono. I have to pause the music, unplug my headphones (until the headphones icon disappears), then plug it back in again, which fixes it. It does this often enough to be an annoyance.
I've already tried different headphones, and it does it to all of them, so the issue is with the phone.
Does anyone else have this problem, and, if so, can you tell me how to fix it?
Thanks!

Just out of curiosity have you tried a fresh install? Almost every issue I've run into I've been able to cure by wiping everything and starting fresh.
Sent through the power of Cthulhu!

hungmung said:
Just out of curiosity have you tried a fresh install? Almost every issue I've run into I've been able to cure by wiping everything and starting fresh.
Sent through the power of Cthulhu!
Click to expand...
Click to collapse
I haven't tried that so far with this phone, although I'm 100% certain it didn't help (as I'm on my second Inspire, the first one's vibrator was defective, and it used to do the same thing).

Ugh, annoying! It just did it 2 times already since then!

Have you tried a non CM based rom?

zelendel said:
Have you tried a non CM based rom?
Click to expand...
Click to collapse
Now that is the one thing I have not tried. However, I only have 2 choices, right? It's either a CM7 based ROM or a Sense based ROM; all of them are based off those two.

ajm786 said:
Now that is the one thing I have not tried. However, I only have 2 choices, right? It's either a CM7 based ROM or a Sense based ROM; all of them are based off those two.
Click to expand...
Click to collapse
Pretty much. But you can flash a sense rom and then run the no sense script if you want to try a sense rom but don't like sense

Jb rom questions and talk thread for bruce 2728 cm10 alpha kang thread

Starting this to clear up space hopefully in the developer thread as I am no developer just a user that really loves this rom and want to help by having questions that are not developmental here also if you want to say that this rom is the best just to say it please do it.
By not developmental I mean what kernels are working for you, possible workaround apps, your roms settings, advanced app that just works better than maybe a pre-installed etc.pretty much anything you would want to say in the rom thread that you know someone is probably gonna say that should be somewhere else.
If Bruce wants me to take this down I will but figured it may help some.
Here is a list of working and not working functions
Thanks to Bruce 2728 and cm team for great work also anyone else that is helping with development have a good day
Not working
??????
Working
F***king camera
Wifi
Audio
Radio
Hardware acceleration (videos need s/w decoder at moment)
button lights
vibration
USB
Charging
Notification led
Sensors
Root
TORCH
HEADPHONES
In call audio (Google now, voice dictation etc)
Bluetooth
for full screen video playback go into settings then developer options and check disable hw overlay box as a workaround
Here is a screencast of Rom
https://www.youtube.com/watch?v=iNKJqimJP70&feature=youtube_gdata_player
Sent from my HTC Sensation using xda app-developers app

Haha it's very to the point, hopefully people take notice and use this. One suggestion: in your OP, you might want to make a list of what works and what doesn't, just to keep it up to date so that it mirrors the dev pages progress. Otherwise, thanks!
Sent from my HTC Sensation Z710e using xda app-developers app

monkor said:
Haha it's very to the point, hopefully people take notice and use this. One suggestion: in your OP, you might want to make a list of what works and what doesn't, just to keep it up to date so that it mirrors the dev pages progress. Otherwise, thanks!
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
+1 totally agree with you bro, just some info on what's working and what's not in the OP would do it, hopefully ppl would use this and keep that dev thread clean:thumbup:
Sent from my GT-N7000 using xda app-developers app

Says in the original thread "Bluetooth partially working" and "Wifi Working" I have found this to be the other way round for me with Bluetooth working fine and Wifi partially working? Wifi just scans saying "Scanning for network" and never finds anything. Not sure if this is the same for everyone or not? Looks like a fix for wifi as well as Google Now maybe imminent though if you look here: https://github.com/febycv

chronic8000 said:
Says in the original thread "Bluetooth partially working" and "Wifi Working" I have found this to be the other way round for me with Bluetooth working fine and Wifi partially working? Wifi just scans saying "Scanning for network" and never finds anything. Not sure if this is the same for everyone or not? Looks like a fix for wifi as well as Google Now maybe imminent though if you look here: https://github.com/febycv
Click to expand...
Click to collapse
Wifi working beautifully for me here. Actually getting reception in the back rooms of my house that I usually don't. As for BT... I can't say as I don't ever use it.

I'm using the Tamcore kernel for overclocking purposes and as a result, the Bluetooth behavior I'm seeing won't be the same as others are experiencing necessarily, but I'll add it for the sake of the few who are also using this kernel.
Pairing is working - I can see my laptop from the Sensation and vice versa. However, when I attempt to transfer files from the laptop to the phone, the transfer fails with an error that states the type of file cannot be transferred. Seeing as it's a simple .rtf file, that is a highly unlikely scenario and something else is going on there.
That's all I have re this issue, but hopefully it will strike a chord with the devs and point toward a fix.
Meantime, there is also some interference between music playback via Apollo and GPS activity - pauses happen seemingly in sync with the GPS doing stuff in the background. The rest of the time, playback is flawless.
Played some video on YouTube and had no issues. Didn't try full screen though but will update when I've had the chance to do so.
Camera, as noted elsewhere, cannot be found by the app.
Apps other than Phone are unable to use the mic so voice search, G Now, Gstrings guitar tuner and so on won't work as yet.
WiFi is working and I get 10Mb's down no probs. GPS is outstanding... getting GPS lock indoors in 8 seconds.
Occasional graphics glitches, but rare and not debilitating.
Not seeing the UI smoothness experienced by others, but should add that my ICS install was already smooth. Or maybe my expectations were unrealistic.
That's about it. No doubt the next fixes from bruce2728 will render these comments moot.
Cheers,
R2

R2D2_NZ said:
I'm using the Tamcore kernel for overclocking purposes and as a result, the Bluetooth behavior I'm seeing won't be the same as others are experiencing necessarily, but I'll add it for the sake of the few who are also using this kernel.
Pairing is working - I can see my laptop from the Sensation and vice versa. However, when I attempt to transfer files from the laptop to the phone, the transfer fails with an error that states the type of file cannot be transferred. Seeing as it's a simple .rtf file, that is a highly unlikely scenario and something else is going on there.
That's all I have re this issue, but hopefully it will strike a chord with the devs and point toward a fix.
Meantime, there is also some interference between music playback via Apollo and GPS activity - pauses happen seemingly in sync with the GPS doing stuff in the background. The rest of the time, playback is flawless.
Played some video on YouTube and had no issues. Didn't try full screen though but will update when I've had the chance to do so.
Camera, as noted elsewhere, cannot be found by the app.
Apps other than Phone are unable to use the mic so voice search, G Now, Gstrings guitar tuner and so on won't work as yet.
WiFi is working and I get 10Mb's down no probs. GPS is outstanding... getting GPS lock indoors in 8 seconds.
Occasional graphics glitches, but rare and not debilitating.
Not seeing the UI smoothness experienced by others, but should add that my ICS install was already smooth. Or maybe my expectations were unrealistic.
That's about it. No doubt the next fixes from bruce2728 will render these comments moot.
Cheers,
R2
Click to expand...
Click to collapse
What radio / hboot versions are you using? I have forever had wifi problems with my sensation really trying to sort it out been bugging me for days, tried nearly everything i can think of and I been flashing android phones for years now. I know it is not a hardware issue as it works on stock roms but not on CM9 / CM10.

chronic8000 said:
Says in the original thread "Bluetooth partially working" and "Wifi Working" I have found this to be the other way round for me with Bluetooth working fine and Wifi partially working? Wifi just scans saying "Scanning for network" and never finds anything. Not sure if this is the same for everyone or not? Looks like a fix for wifi as well as Google Now maybe imminent though if you look here: https://github.com/febycv
Click to expand...
Click to collapse
are you using the kernel that was included because I have found that tamcore's cm9 kernel had fully working Wi-Fi and Bluetooth works perfectly for me and is incredibly smooth also
I am currently using it on the Pegasus q governor just to see how it runs so far really smooth @1728 & 432 almost as good as intellidemand going to see how battery is on this governor though
Sent from my HTC Sensation using xda app-developers app

melo563 said:
are you using the kernel that was included because I have found that tamcore's cm9 kernel had fully working Wi-Fi and Bluetooth works perfectly for me and is incredibly smooth also
I am currently using it on the Pegasus q governor just to see how it runs so far really smooth @1728 & 432 almost as good as intellidemand going to see how battery is on this governor though
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Yes using kernel that was included and I also tried bricked 1.31 aosp kernel both with no joy. I am going to try tamcores cm9 kernel now you said working wifi though! Don't suppose you gotta link to the exact kernel your using do you?

chronic8000 said:
What radio / hboot versions are you using? I have forever had wifi problems with my sensation really trying to sort it out been bugging me for days, tried nearly everything i can think of and I been flashing android phones for years now. I know it is not a hardware issue as it works on stock roms but not on CM9 / CM10.
Click to expand...
Click to collapse
I'm using firmware 3.33 with Radio 11.76A.3504.00P_11.24A.3504.31_M and stock kernel with amazing wifi.

chukis13 said:
I'm using firmware 3.33 with Radio 11.76A.3504.00P_11.24A.3504.31_M and stock kernel with amazing wifi.
Click to expand...
Click to collapse
exactly same setup as me 3.33 firmware and 11.76A radio but with stock kernel no wifi? Is there different versions of the sensation or something? Very weird

melo563 said:
Not working
Camera
Video playback is buggy (temp fix http://forum.xda-developers.com/showthread.php?p=29243391 )
Headphones.
Click to expand...
Click to collapse
There's a headphones workaround that uses a Play Store widget to re-route the speaker though the headset. Not a fix, obviously, but enough to get by for those for whom no headphones is a deal-breaker for flashing onto their phone.
HTH.
R2

R2D2_NZ said:
There's a headphones workaround that uses a Play Store widget to re-route the speaker though the headset. Not a fix, obviously, but enough to get by for those for whom no headphones is a deal-breaker for flashing onto their phone.
HTH.
R2
Click to expand...
Click to collapse
I concur with this. It works beautifully.

chronic8000 said:
What radio / hboot versions are you using? I have forever had wifi problems with my sensation really trying to sort it out been bugging me for days, tried nearly everything i can think of and I been flashing android phones for years now. I know it is not a hardware issue as it works on stock roms but not on CM9 / CM10.
Click to expand...
Click to collapse
HBOOT version is1.29.0000
Radio is 11,24A.3504.31_M
HTH
R2

for me youtube full screen causes reboots
but if you download super video pop-up video player from the market you can drag the video pretty big almost full screen with no issues so far from me
all you have to do is go to youtube find the video you want them press share and select super video to play youtube videos
Sent from my HTC Sensation using xda app-developers app

do you guys think I should put some of the workaround apps we find in op as we go
Sent from my HTC Sensation using xda app-developers app

melo563 said:
do you guys think I should put some of the workaround apps we find in op as we go
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Yes, in hopes that retards might actually read it.

Girlfriend is out of town so I've got nothing to do for awhile so I'm going to flash this and test a bunch of stuff out. If anyone has any requests on apps to test, I'd be glad to download em and give it a whirl. That is, provided I don't bork my phone flashing this directly over Virtuous Inquisition.

melo563 said:
are you using the kernel that was included because I have found that tamcore's cm9 kernel had fully working Wi-Fi and Bluetooth works perfectly for me and is incredibly smooth also
I am currently using it on the Pegasus q governor just to see how it runs so far really smooth @1728 & 432 almost as good as intellidemand going to see how battery is on this governor though
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Well I tried with Tamcore's 3.0.38 00673 kernel and it doesn't break or fix anything. JB does run a little smoother than stock kernel but still broken wifi

did you reflash rom or just flash kernel maybe try full wipe and reflash with tamcore from start if you didn't already
Sent from my HTC Sensation using xda app-developers app

Hellfire Phoenix V2.3 p999 [cm7.2 /super tweeked] - audio/music stops randomly...

Hi,
Firstly, want to thank the dev for this great rom. I recently switched back from ICS because I couldn't take the lag/wanted a fully functioning operating system.
The main problem I' having with this rom is that when I'm listening to music/audio files they'll stop for no apparent reason. The only thing I can think of is that maybe they're stopping when I go in and out of service. When I either unlock and press play or switch apps and press play they start again with not problems. I've found this to happen in multiple audio player (Poweramp and BeyondPod being the two main ones I use).
Any help would be greatly appreciated as this is incredibly frustrating.
Thanks very much for your hard work.
btw: the reason I didn't post this in the related dev forum is that I don't as yet have enough posts to do so...so no flaming please).

Nobody is gonna flame you for posting a question on the questions forum.. (unless you didn't search first)
I've had this happen to me as well with different ROM's. I don't believe its ROM specific. My problems were related to some of my notification settings. I also switched from the standard player to UberMusic. It's old but does the job well.

New2my8125 said:
Nobody is gonna flame you for posting a question on the questions forum.. (unless you didn't search first)
I've had this happen to me as well with different ROM's. I don't believe its ROM specific. My problems were related to some of my notification settings. I also switched from the standard player to UberMusic. It's old but does the job well.
Click to expand...
Click to collapse
Can't be too careful when it comes to flames.
I thought it might be my notification settings but I've tried pretty much every permutation of those. Can't really bring myself to switch from PowerAmp (paid) and BeyondPod(free) is the best podcast player I've found to date...I might try reinstalling the rom, maybe I didn't wait long enough before using it?

sellless said:
Can't be too careful when it comes to flames.
I thought it might be my notification settings but I've tried pretty much every permutation of those. Can't really bring myself to switch from PowerAmp (paid) and BeyondPod(free) is the best podcast player I've found to date...I might try reinstalling the rom, maybe I didn't wait long enough before using it?
Click to expand...
Click to collapse
Does the problem exist if you were to use Google Music? If it does, then it's most definitely a problem with the ROM. Try a re-install and if that doesn't clear it up, you might want try out a different ROM to see if it's the ROM or not.

New2my8125 said:
Does the problem exist if you were to use Google Music? If it does, then it's most definitely a problem with the ROM. Try a re-install and if that doesn't clear it up, you might want try out a different ROM to see if it's the ROM or not.
Click to expand...
Click to collapse
Sadly, or happily as I love PowerAmp, it does occur with Google Music too. Never had this problem on eaglseblood gb (which I mainly used before trying a few ICS roms) but switched as their GB rom is no longer maintained. Will try re-flashing. Hopefully that helps.
Thanks for your suggestions.

sellless said:
Sadly, or happily as I love PowerAmp, it does occur with Google Music too. Never had this problem on eaglseblood gb (which I mainly used before trying a few ICS roms) but switched as their GB rom is no longer maintained. Will try re-flashing. Hopefully that helps.
Thanks for your suggestions.
Click to expand...
Click to collapse
Yeah, i just recently discovered this issue too, and it kind of bugs me.

Still haven't found a way around this. Tried reflashing the rom which didn't help. Just tried flashing faux's 49b1 to see if that helps. The dalvik cache is being very slowly rebuilt. The newer kernel (the one included in hellfire 2.3) has a MUCH faster loading time (at least upon first load). Will post if this helps with the sound issue.

sellless said:
Still haven't found a way around this. Tried reflashing the rom which didn't help. Just tried flashing faux's 49b1 to see if that helps. The dalvik cache is being very slowly rebuilt. The newer kernel (the one included in hellfire 2.3) has a MUCH faster loading time (at least upon first load). Will post if this helps with the sound issue.
Click to expand...
Click to collapse
Well. I'm still having this problem. I've tried multiple kernels, multiple roms and even completely formatted my phone (all partition including boot sector). No luck. Truly aggravating because aside from this issue, I love this rom. Very smooth/fast and stable. Not sure I can live with this audio problem though as it's incredibly frustrating.
If anyone else has encountered this problem and found a solution, please post. Thanks,

I just dl the old music player apk here see if it helps. https://play.google.com/store/apps/details?id=com.jrtstudio.music
Also does it occur both when using headphones and not? I had issue with a set of headphones with a break in the wire, which would make the phone appear as though the headset was unplugged and plugged back in, which stopped playback constantly.
Let me know if this helps any.
Sent from my LG-P999 using xda app-developers app

Thanks for replying.
I'd wondered if that might be the reason too. I know it gains with different headphones as I've tried four different pairs. I'll have you try it without any and see. I did try disabling the setting for stop playback upon removal of headphones with no success. I'll try without headphones in and see. I'll have to flash the Rom again as I've been trying a few others out.
Sent from my LG-P999 using xda app-developers app

sellless said:
Thanks for replying.
I'd wondered if that might be the reason too. I know it gains with different headphones as I've tried four different pairs. I'll have you try it without any and see. I did try disabling the setting for stop playback upon removal of headphones with no success. I'll try without headphones in and see. I'll have to flash the Rom again as I've been trying a few others out.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Did you get it figured out?

justjackyl said:
Did you get it figured out?
Click to expand...
Click to collapse
Sadly, no. I've tried playing music without headphones attached and the same problem occurs. Random stops. I go into whichever application (it happens in everyone single one I've tried) was playing an audio file and it starts up right where it left off when I press play.
It's worse now actually in that it occurs with whatever all roms. So now I'm left wondering if there's a micro fracture in the headphone sensor that only started acting up at the exact time I put Hellfire Phoenix 2.3 on my phone or if, somehow, it corrupted some base setting on the phone that even reformatting it can't get rid of.
Terribly aggravating. Debating taking it in for service but I need to find a Wind factory rom before I can do so. Think I saw one in the forums a few months ago. hopefully the link's still active.
Loathe/love technology.

justjackyl said:
Did you get it figured out?
Click to expand...
Click to collapse
I've reinstalled my phone's stock rom (WIND Mobile).
This seems to have sorted out the issue. I'm going to try reinstalling Hellsfire Phoenix in a few hours if it doesn't happen again (I'm playing music nwo and will continue for a couple hours to make sure).
I'm now wondering if maybe this was some sort of error caused by downgrading from an ICS build (hadn't occured to me previously but that's when I started having this issue and it didn't matter which GB rom I tried after that)? Hopefully this will be the end of these problems and I can enjoy Hellsfire Phoenix as it was great aside from that issue.
I'll post in a couple days if all goes well....or if it doesn't.

sellless said:
I've reinstalled my phone's stock rom (WIND Mobile).
This seems to have sorted out the issue. I'm going to try reinstalling Hellsfire Phoenix in a few hours if it doesn't happen again (I'm playing music nwo and will continue for a couple hours to make sure).
I'm now wondering if maybe this was some sort of error caused by downgrading from an ICS build (hadn't occured to me previously but that's when I started having this issue and it didn't matter which GB rom I tried after that)? Hopefully this will be the end of these problems and I can enjoy Hellsfire Phoenix as it was great aside from that issue.
I'll post in a couple days if all goes well....or if it doesn't.
Click to expand...
Click to collapse
That's so odd. I'm curious to see what happens if you go from stock to HFP v2.3.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.

justjackyl said:
That's so odd. I'm curious to see what happens if you go from stock to HFP v2.3.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
Click to expand...
Click to collapse
Well, sad to say that I still had that problem after trying HFP 2.3 again. So I went back to stock. This time it happened on stock too so I have to assume it's a hardware problem. I guess I just lucked out (well, poor luck in this case) that it went for four hours Friday without halting playback.
Better take it in for warranty service while it's still covered.
At least it seems unlikely that any rom/kernel combo was to blame now.

[Q] GPS always drops signal after ~5 mins of navigation

A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!

rpod83 said:
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
Click to expand...
Click to collapse
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.

MagicalHobo said:
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
Click to expand...
Click to collapse
Thanks, MagicalHobo. Did you ever try a different ROM with success?

rpod83 said:
Thanks, MagicalHobo. Did you ever try a different ROM with success?
Click to expand...
Click to collapse
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.

Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2

biglittlegato said:
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Click to expand...
Click to collapse
From my experience, GPS works perfectly on aospx.