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

A simple question about wifi.

Hi everyone, i'm glad to see we are on official gingerbread now.
I wanted to know if anyone will be working on a cwm package (or something) to make previous GB roms have the wifi strength of froyo?
-I want to emphasize that i'm not asking for an eta. More so if this is possible and something that I just need to wait to be released.
-I'm running icbinb ki3 tweaked exactly how i like it with battery how i like it. I'd rather not flash stock 2.3.6 unless that's the only way to improve my wifi. If I only have to wait for a package that will improve it on ki3, then id rather do that.
So thanks for reading, dont flame if you can help it.

Mizun0h said:
Hi everyone, i'm glad to see we are on official gingerbread now.
I wanted to know if anyone will be working on a cwm package (or something) to make previous GB roms have the wifi strength of froyo?
-I want to emphasize that i'm not asking for an eta. More so if this is possible and something that I just need to wait to be released.
-I'm running icbinb ki3 tweaked exactly how i like it with battery how i like it. I'd rather not flash stock 2.3.6 unless that's the only way to improve my wifi. If I only have to wait for a package that will improve it on ki3, then id rather do that.
So thanks for reading, dont flame if you can help it.
Click to expand...
Click to collapse
The short answer from me is that I don't know. I wish I had more insight into what changed between Froyo & GB to cause the wifi to weaken. Could be as simple as drivers, could be that's how they're saving power, etc. I know flashing the KJ6 modem file caused people to have a big of an improvement with wifi though not the same level of performance with Froyo. I also read a lot of people had issues sending big SMS messages with KJ6, so that might be something to be wary about.
Anyway, you could flash the KJ6 modem file to see if it helps. As for something to get it back on par with Froyo, I'll have to leave that to the experts around here.

stephen_w said:
The short answer from me is that I don't know. I wish I had more insight into what changed between Froyo & GB to cause the wifi to weaken. Could be as simple as drivers, could be that's how they're saving power, etc. I know flashing the KJ6 modem file caused people to have a big of an improvement with wifi though not the same level of performance with Froyo. I also read a lot of people had issues sending big SMS messages with KJ6, so that might be something to be wary about.
Anyway, you could flash the KJ6 modem file to see if it helps. As for something to get it back on par with Froyo, I'll have to leave that to the experts around here.
Click to expand...
Click to collapse
Yea i understand and get that to some degree. thanks for the reply.
Was wifi confirmed to be as strong as froyo on the stock gb?

Mizun0h said:
Yea i understand and get that to some degree. thanks for the reply.
Was wifi confirmed to be as strong as froyo on the stock gb?
Click to expand...
Click to collapse
It's not. It's stronger on Froyo.

stephen_w said:
The short answer from me is that I don't know. I wish I had more insight into what changed between Froyo & GB to cause the wifi to weaken. Could be as simple as drivers, could be that's how they're saving power, etc. I know flashing the KJ6 modem file caused people to have a big of an improvement with wifi though not the same level of performance with Froyo. I also read a lot of people had issues sending big SMS messages with KJ6, so that might be something to be wary about.
Anyway, you could flash the KJ6 modem file to see if it helps. As for something to get it back on par with Froyo, I'll have to leave that to the experts around here.
Click to expand...
Click to collapse
To be honest, noone really knows exactly what the problem is.
But if you want to add the wifi properties of KJ6 to any ROM, which are way stronger than any previous GB build, you can refer to my thread in the development section. The mod I posted gives you the wifi of KJ6 without the modem. (Im currently using this mod with KI3 and my wifi is pretty darn good ATM ;p)

Look in dev section... possible fix posted earlier
Sent from my SGH-T959V using XDA App

[Q] What is radio?

I realize many of you see this as a dumb question. But I see a lot of posts about radios. I've tried looking around the web what it is but couldn't really find good explaining information. I see a lot of posts for flashing the radio and a lot of different versions.
I'm running MIUI on my Sensation 4G and if radio is something I need to flash then I want to know what it is before I try flashing and brick my phone. So I've managed to find the version I have so if someone can point me the right direction I'd be very grateful.
So the main question is - WHAT IS RADIO?
So this is what I got
Radio - 10.14.9035.01_M

the radio pretty much just has to do with the wireless connectivity of ur phone, so ur wifi, bluetooth, 3g all controlled by your phones radio.
you shouldnt have to flash a new radio for every rom, if your facing problems, and think a new radio could fix them then you could try a new radio if you wanted.
hope this helped

Lol oh yea definitely! very simply put too! I just was wondering why there's so many versions and chance of bricking dam thing.
Sent from my Sensation 4G using XDA App

maxe30is said:
Lol oh yea definitely! very simply put too! I just was wondering why there's so many versions and chance of bricking dam thing.
Sent from my Sensation 4G using XDA App
Click to expand...
Click to collapse
Flashing the radio is just about the only sure fire way of bricking it.. It's one of those things people are most skeptical about flashing. No nandroid will save you with an improperly flashed radio
EDIT: I've been flashing roms for a long time now and not once have I ever had to flash a new radio.
Sent from Tapatalk Modified

OK. I installed the HD Revolution 3.6.9 ROM days ago and have 2 major issues. As I am a new member, I am unable to post in the developmental section. Grateful for the OP to ask the question as I am also seeking to know "what radio is".
Although, I also want to ask - what is a kernel?
I believe thousands of members installed that HD Revolution 3.6.9 ROM and I couldn't find any reference for bluetooth and mms issues.
My phone can only detect my Nokia phone, my Plantronics bluetooth M100 is undetectable.
I am also unable to send MMS and yes, I tried the original settings, called the network and played with different settings but problem persists.
I checked the Hardware Information of the phone and it says "Bluetooth address - unavailable"

Kernel is a bridge between applications and the actual data processing done at the hardware level. So basically kernel tells all the hardware what to do (overclocked processors, undervolted batteries and etc) So far best one I've tried for Sensation 4G is the 2.6.35.14 Trinity S4G. Processor is overclocked to 1.7Ghz from stock 1.2 Ghz and the battery life is great!

masonic1032 said:
OK. I installed the HD Revolution 3.6.9 ROM days ago and have 2 major issues. As I am a new member, I am unable to post in the developmental section. Grateful for the OP to ask the question as I am also seeking to know "what radio is".
Although, I also want to ask - what is a kernel?
I believe thousands of members installed that HD Revolution 3.6.9 ROM and I couldn't find any reference for bluetooth and mms issues.
My phone can only detect my Nokia phone, my Plantronics bluetooth M100 is undetectable.
I am also unable to send MMS and yes, I tried the original settings, called the network and played with different settings but problem persists.
I checked the Hardware Information of the phone and it says "Bluetooth address - unavailable"
Click to expand...
Click to collapse
btw try wiping you sd card and then flashing the Rom. helped me few time (im no developer )

IAmTheOneTheyCallNeo said:
Flashing the radio is just about the only sure fire way of bricking it.. It's one of those things people are most skeptical about flashing. No nandroid will save you with an improperly flashed radio
EDIT: I've been flashing roms for a long time now and not once have I ever had to flash a new radio.
Sent from Tapatalk Modified
Click to expand...
Click to collapse
Obviously some radios are better than others?
Like the goal for man:
We want the best and we want it now.

Hardcore69er said:
Obviously some radios are better than others?
Like the goal for man:
We want the best and we want it now.
Click to expand...
Click to collapse
Well that I'm not sure how accurate this statement is. That's why I started this thread just to know what it is. But from all the info I gathered online, you don't really need to flash a radio. Every thread with radios I saw that ppl will put a warning that you might brick your phone. So, my phone works great, never had any problems so I'll stay on the safe side (for now) and just do more research

maxe30is said:
Well that I'm not sure how accurate this statement is. That's why I started this thread just to know what it is. But from all the info I gathered online, you don't really need to flash a radio. Every thread with radios I saw that ppl will put a warning that you might brick your phone. So, my phone works great, never had any problems so I'll stay on the safe side (for now) and just do more research
Click to expand...
Click to collapse
Good decision..

G2X Discussion Thread (CM Nightly issues, ICS updates, etc.)

Well everyone, since my KANG thread in the development section has become a discussion thread since official CM nightlies started again, I've decided to redirect the discussion to here. I'm going to ask the thread in the development section to be closed, so it can stop taking up space there...instead we'll take up space here! Lol. But anyways I want this to basically be a continuation of the old thread...you can talk about your G2X questions, comments, problems, etc. here. This will be especially geared toward CM-related problems, but all G2X-related topics are welcome here I hope that everyone will continue to help each other out, and of course I'll monitor the thread to help as much as I can and research things if necessary. Enjoy!

This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.

Kalm_Traveler said:
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Click to expand...
Click to collapse
Ya I couldn't stand that answer my phone wait for it to ring after I select answer was surely a big annoying thing that and wifi calling issues but other then that VERY usable can't wait for newer builds and development on 4.0.3..
I'm on his GB CM7 build and love it great great battery life only at 90% with descent use today.
Sent from my LG-P999 using xda premium

Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??

j.d.r said:
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
Click to expand...
Click to collapse
As it is always said, it is best to do a full wipe. You never know what issues may stick behind or get caused by not doing a full wipe, but give it a shot and report back and hopefully you don't have issues.
Sent from my LG-P999 using xda premium

Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk

I believe Hellfire sandwich is the most updated and closest to everything working build. But there's lots coming down the pipeline thanks to our AMAZING DEVS!!!
Sent from my LG-P999 using xda premium

What's the best source for finding out the status of official Cyanogen 9 work on the G2X? I am not interested in kangs or spin-offs.

joeyxl said:
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I haven't tried any of the other ICS roms, but been using HFS since the initial release. Obviously it's not perfect, but I've been running it everyday and don't have any major complaints

CM Nightly 226/Unnamed & Kernels
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
I've used Faux123's UV/OC kernels, but seem to have lost my copy of his v0.4.3 (long term CM7.1.0.1 support). So, the newest v0.4.8 and T15 or ELF Trinity's won't work with mine. I know chip's vary, but mine seems to not like even the ELF Trinity kernel (which has worked for a few peeps running CM7.1.0.1).
Anyway, the breakdown of my ramblings are:
1. Anyone try CM Nightly 226/Unnamed?
2. Anyone happen to have a copy of Faux123's v0.4.3 kernel (CM Battery Version, not the DS driver) lying around? Or a compatible Trinity (preferred, actually)?
Eh, I know #2 is more wishful thinking. I'm mostly interested in anyone's experience with Nightly 226/Unnamed.
Ah, good to be back on XDA and CM, at that. I rolled on MIUI for way too long. Nice GUI & the customization was awesome, but man is that sucker a memory hog! Not to mention the random reboots and screen freezes... I should have never left my good ol' CM. Hindsight and all...

The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.

long story short, i have a wiped g2x. power button is a ***** to turn on to the point that my finger tips are sore from trying to get it to boot into recovery since last night. i can only seem to get 2 different screens trying to do this:
a) the lg boot animation which promtly freezes as the phone has been wiped & i probably haven't held the volume down button
b) the s/w screen used for flashing a recovery, etc
the phone is not mine but trying to help someone out. is there a timing to releasing the buttons? seems that when it goes to the s/w screen, lg appears for only about a second and then straight to that one. any help would be appreciated.
edit: posted it here only because i'd been following the old thread which led me to this one. i was trying to update to the latest while this happened. i started a similar thread in q&a so if it doesn't belong i''ll remove it, thanks

I've been in a loop like this before. Make sure you have done a battery pull. I think the key is not to hold the volume down button so long, and then be patient for recovery to load, it takes longer than expected in this situation.
Good luck.

Nightly #225
my_former_self said:
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
Click to expand...
Click to collapse
Ah, you want to talk to me! I just went from CM7.1.0.1 Stable to #225. More stable, much faster than CM7 Stable, #225 really should be CM7.2 Stable.
#226 seems to have a bug with the lockscreen PIN. Go get #225 and don't look back.

azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.

dmwOtis said:
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
Click to expand...
Click to collapse
Lots have stated the same thing doesn't work for most some say it did. Worth a try if you haven't yet, no go for me
Sent from my LG-P999 using xda premium

Where is this getril app?
Sent from my LG-P999 using XDA

azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I agree, this is by far the most annoying bug and the only "show stopper" I can think of on CM7. I do not think it's a 'phone-by-phone' thing, because if I flash to stock or Weapon G2X, my mic volume is fine. It's only on CM/CM-based ROMs, such as MIUI. I can't count the number of times where people have told me to "speak up" until I'm practically yelling into my phone. I think there's a bug with noise cancellation that causes it to be quieter than it should be.

Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA

imoumni said:
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
GetRIL went the other way for my phone (Wind Canada P999), recommending v11h. Any notes re: the different builds?

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.