Related
I have had no major problems with my Inspire 4G while on Inspire 4G ROMs (well... Stock, rooted stock, and Inspired Ace which is customized for the inspire.) On every DHD ROM I have installed, there seems to be a problem with touch input. When typing emails, searches, SMS, and other things random keys will just stop working! Sometimes I can tap them repeatedly and fix it while others you have to exit whatever app you are in and open it back up. It gets really annoying.
I am currently on CoreDroid, but have had this problem with TB Fusion, RCMixHD, and RCMix3D as well. Since Inspired Ace worked fine I tried flashing its HTC_IME.apk to see if this fixed the problem. It didn't. I seem to be the only one with these problems on the Inspire. Has anyone else noticed? Does anyone have any suggestions for what could cause these issues?
(Yes, I am aware of the problems flashing ime packages from other ROMs can cause, I was just trying to see if it fixed the problem. I had to backup zip ready to flash in case it caused FC problems...)
Thanks in advance guys!
I'm using leedroid and I have the same problems of random keys not working at random times.
Sent from my Inspire 4G using XDA Premium App
It's a driver issue with inspires iirc. No fix
Sent from my Inspire 4G using XDA App
1.18.12 said:
It's a driver issue with inspires iirc. No fix
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Wait so there is no possibility of ripping the drivers from stock and flashing or getting a kernel with them? And how come it worked on Inspired Ace? Did gtg465x get the driver issue fixed? Not trying to sound angry there just a bit perplexed since IA was dhd based....
Sent from my Desire HD using XDA App
Might be hardware than, I do remember it being brought up and it's unfixable.. I've had it happen on factory stock plenty of times. I just change my screen to horizontal and fixes it.
Sent from my Inspire 4G using XDA App
1.18.12 said:
Might be hardware than, I do remember it being brought up and it's unfixable.. I've had it happen on factory stock plenty of times. I just change my screen to horizontal and fixes it.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Hmm... Well mine never did that. Only failed to rotate a few times due to a few malfunctioning third party apps... If i find a fix I will post it.
I've had this as well and thought that maybe it was Better Keyboard having an issue with either the Inspire in general, or CoreDroid. So this is happening to others using the stock keyboard. Glad it's not just me.
Demented71 said:
I've had this as well and thought that maybe it was Better Keyboard having an issue with either the Inspire in general, or CoreDroid. So this is happening to others using the stock keyboard. Glad it's not just me.
Click to expand...
Click to collapse
No you aren't alone... I consulted gtg465x and he only edited a few things in /system/customize so I flashed the IA /system/customize/default.xml and it seems to have greatly improved. Noticed one of those such lags but it is not the one out of every hundred that it was. I typed this a few other things multiple sms one of which was long and only had to tap one key multiple times to get it to work. And only three taps at that!
If I further test it I will ask gtg for his permission and post the default.xml in a flashable zip.
Now all that is left to do is edit build.prop to make my phone say inspire not dhd then flash from mdj v21 to 23, calibrate battery for this ROM (grr... Coredroid updates wiped my battery stats while it was only at 63 percent charge during install) and then I can finally be happy and leave my phone exactly how it is! Yeah that will last all of what? A week maybe? Haha nah I am happy on coredroid!
Sent from my Desire HD (INSPIRE 4G!) using XDA App
I've had this happen to me on multiple ROM's and it always seems to be the "e" key that stops working for me. I just restart my phone or change input methods and it usually fixes it for a while.
Wish there was a permanant fix cause it does get annoying.
willwalk93 said:
No you aren't alone... I consulted gtg465x and he only edited a few things in /system/customize so I flashed the IA /system/customize/default.xml and it seems to have greatly improved. Noticed one of those such lags but it is not the one out of every hundred that it was. I typed this a few other things multiple sms one of which was long and only had to tap one key multiple times to get it to work. And only three taps at that!
If I further test it I will ask gtg for his permission and post the default.xml in a flashable zip.
Now all that is left to do is edit build.prop to make my phone say inspire not dhd then flash from mdj v21 to 23, calibrate battery for this ROM (grr... Coredroid updates wiped my battery stats while it was only at 63 percent charge during install) and then I can finally be happy and leave my phone exactly how it is! Yeah that will last all of what? A week maybe? Haha nah I am happy on coredroid!
Sent from my Desire HD (INSPIRE 4G!) using XDA App
Click to expand...
Click to collapse
According to my research, editing the build.prop file on Sense ROMS doesn't directly reflect what is listed in About Phone. It seems that you have to edit default.xml in /system/custom/CID.... before installing the ROM
Yeah I read the same thing.right after i posted that... Oh well! Maybe when I get bored enough to do it. And after further testing i concluded that changing the default.xml to disable some of the keyboard layouts and things as gtg465x did didn't really help all that much... On the bright side, i may just go back to inspired ace and use uot kitchen to customize it
Sent from my Inspire 4G using XDA App
So nobody has any other potential fixes for these freezes? Has it happened on every ROM you guys have used or what? I tried replacing my customize folder with the one from ia with cut down keyboard languages and layouts but no luck. Maybe we can find a fix!
EDIT: There may appear to be some confusion here. The problem in reference is not that the keyboard fails to rotate, gets stuck in landscape, or shows that a message is being typed and nothing appears on screen. The problem I am having here is that certain keys in random order at completely random times do not work but the keys around them do. This results in messages such as "Hey that bnd sunded relly gd" instead of "Hey that band sounded really good!!!" because the A and O ceased to function and likewise the exclamation point which is with the A. Also, at times the key will show it is being pressed but stops registering before the symbol it relates to is pressed. These problems exist on stock android keyboard and on sense keyboard. Hopefully someone will find a fix in drivers or something otherwise we will have to wait for a cracked official OTA GB update if that ever happens as they say it will...
Sent from my Desire HD using XDA App
BTT
I´m having the same issue, and it´s driving me crazy!!!
It´s weird, because I´ve had this phone for months, and had no problems, until a week ago.
I´m on Stock ROM BTW.
no solution? this is an on going problem and hard to ignore...
I have to agree with everyone here.. It is a pretty glaring flaw in the Inspire. And many people think that it barely happens.. But it is a problem that occurs for me at least 5 times a day and that is not an exaggeration. Everything that I have been reading does say that this is an impossible thing to fix.. Just a bit frustrating. Does anyone have a way that lessens this from occurring?
ive had this problem also for awhile. ive had it on every custom rom that i can think of. i used coredroid and cm7 for awhile. right now im using miui. ive tried 3-4 different keyboard at least, and had this problem with all of them. the keyboards accuracy also seems to decline. when switching to a new keyboard the problem initially goes away, but it eventually starts doing it again with the different keyboard.
finally! thanks you, guys. Finally I get support for a bug that supposedly didn't exist. I have been out of the rooting and ROM flashing game for a few months, as I got a new Inspire and never got the chance to root it. I finally caught a break from school work and got fed up with having to do battery pulls on the ATT stock ROM (terribly made, I must say. Sense froze daily.) I rooted and flashed the trusty old Inspired Ace and what do you know? flawless. as always. I flash the new coredroid 8.1 to see if the keyboard bug still persisted. For the first day, I had no problems. Then the freezes came back. I think it is very possibly a side effect of the undervolt kernel. As for those that say all phones are not created equally, and my processor just can't take the ROM, is that really likely on two phones in a row while the inspired ace ROM works flawlessly?
Edit: Also, for those that say stick to IA if it works, it hasn't been updated in a long long time and never will be since GTG465x moved to the Captivate
It's not that people don't beleive you, its just that this is not a common enough bug for it to be a software issue. It has to be a specific hardware malfunction. I have never had this problem on any Rom configuration that I have used. I have never seen it as a reported bug either.
Sent from my Inspire 4G Using XDA Premium
Good point... It just still doesn't make since since one DHD ROM didn't do it all yet others do. Coredroid I is not doing it nearly as severely cd6 did. So maybe there is hope that it is a fluke combination of hardware and software bugs rarely manifested.
Sent from my Inspire4G using XDA App
Bump
Well, in preparation for android 4 I decided to get used to AOSP ROMs since they will probably be more widely available than ICS Sense ROMs. After using cm7.1 for just two days, the bug is still there. Note that this is a different inspire than the thread was started on. Does anyone have any solutions? It just makes no sense that this bug does not occur for me on Inspired Ace or Stock but does on every other GB Rom I have tested. For everyone reading this with the urge to pop a comment at me like "Stupid, stick with IA if it works," that ROM has been abandoned since May 5, so it is outdated. Any hopes for ICS roms solving the problem?
Keyboard app is not the problem. Does it on touch input (sense ROMs), swiftkey X, swype, and android default keyboard.
I have been running ICBINB for about a week. Stumbled upon this:
http://forum.xda-developers.com/showthread.php?t=1172028
and flashed it because i thought i read in the ICBINB thread, it was not part of final release.
After about 15 - 20 mins, i loose signal and it's gone until i reboot or log into a wifi connection then log out. This is the only thing that i added to the phone, which is why i think it is the problem. After wards my signal seems to work great, it's a mysterious issue and i was just bringing it to the light.
Since i'm a hardcore lurker and don't post until i have an issue, because "I SEARCH" i can't directly post in the build.prop. I will be reverting back to ICBINB final to see if this solves my issue.
Has anyone else had this problem? Does the final release already have the most recent build.prop enhancement? Could flashing the build.prop again fix this gremlin?
Galaxy s 4g, White Hawk KC1 base, then followed op ICBINB instructions and it's worked smoothly until i flashed 7/17/2011 Build.prop.
Love the phone and Love the ROM, was on black ice stable before and stock before that. I did at one point use the whitehawk KD1 that is mentioned to have issues, But that is why i KC1'ed.
Any help/Advice would be greatly appreciated.Should i re-flash entire rom, or just build.prop? Could it be something else? Is it just a ghost in the machine? Did Aliens do it or is it just residual debris from the recent rash of troll wars?
Dev's keep me away from mindless I-phone, Thanks for keeping my mind active.
Mr Nosrok said:
I have been running ICBINB for about a week. Stumbled upon this:
http://forum.xda-developers.com/showthread.php?t=1172028
and flashed it because i thought i read in the ICBINB thread, it was not part of final release.
After about 15 - 20 mins, i loose signal and it's gone until i reboot or log into a wifi connection then log out. This is the only thing that i added to the phone, which is why i think it is the problem. After wards my signal seems to work great, it's a mysterious issue and i was just bringing it to the light.
Since i'm a hardcore lurker and don't post until i have an issue, because "I SEARCH" i can't directly post in the build.prop. I will be reverting back to ICBINB final to see if this solves my issue.
Has anyone else had this problem? Does the final release already have the most recent build.prop enhancement? Could flashing the build.prop again fix this gremlin?
Galaxy s 4g, White Hawk KC1 base, then followed op ICBINB instructions and it's worked smoothly until i flashed 7/17/2011 Build.prop.
Love the phone and Love the ROM, was on black ice stable before and stock before that. I did at one point use the whitehawk KD1 that is mentioned to have issues, But that is why i KC1'ed.
Any help/Advice would be greatly appreciated.Should i re-flash entire rom, or just build.prop? Could it be something else? Is it just a ghost in the machine? Did Aliens do it or is it just residual debris from the recent rash of troll wars?
Dev's keep me away from mindless I-phone, Thanks for keeping my mind active.
Click to expand...
Click to collapse
Lmao "Troll wars" I love it, good stuff.
As for your issue I would pm dsexton702 as he should be able to shed some light on this little dilemma.
Sent from my SGH-T959V using XDA Premium App
After you flash the performance.zip, maybe clear cache and fix permissions. that usually solves my problems.
Sent from my SGH-T959V using XDA Premium App
I always obey the law of the three W's. Wipe, wipe, wipe. Then back-up. i'll try again. maybe it missed something on one of the previous wipes. And i also fix permissions whenever i am in recovery.
I will pm dsexton.
Have you tried flashing a new modem?
Sent from my SGH-T959V using XDA Premium App
Okay. Moving from orlando to miami and havent had much time to mess with my phone. Wiped and fixed permissions again and it seems to be working fine now. probably a ghost in the code.
Spreading the sgs4g love. May the dev's "live long and prosper."
Hello, I've been running xboarder56's rooted GB OTA (not the tweaked one) for about 2 months now with almost no problems. However, my phone slows down and starts getting laggy to the point of being unusable after a day or two, and the frequency seems to be increasing. I don't run many background services. Only rebooting fixes the problem temporarily. I'll try to load a webpage on either opera mobile or the stock browser while listening to music and the music starts skipping and popping while the page loads slower than usual, but after rebooting it's fast again with no skipping.
I've been searching the forums and Google and seen a few others with this problem but can't find a fix for it. I've tried clearing the Dalvik cache (with NVflashed CWM) but it didn't seem to help any. Is this a common problem with LG-based Gingerbread ROMs, and does anyone else here still have this problem? I started having this problem after running my last ROM, CM7 RC1 after a month, and when I switched to my current ROM I did do a full wipe/factory reset. I'm thinking about trying the new-ish CM7.1.0.1 stable ROM or Weapon G2x and am wondering if those have this problem as well. Any suggestions? Thanks for your time!
I have honestly had that problem with every most roms I've tried at some point. Maybe not instantly, but it will eventually start to slow down like you described in which i have to reboot.
Dang. Do you think a fix actually exists for this, or does everyone have this problem? It's strange since I can't find much discussion about this.
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
jboxer said:
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
Click to expand...
Click to collapse
That's the issue I have with any 2.3.3 builds. But with 2.3.4 straight for 2 days now, hasn't experienced this issue yet. Unlike 2.3.3 that even within a day, it needs a reboot. I think there is a problem with LG's memory management.
-----------
sent from my calculator with android
jose makalolot said:
That's the issue I have with any 2.3.3 builds. But with 2.3.4 straight for 2 days now, hasn't experienced this issue yet. Unlike 2.3.3 that even within a day, it needs a reboot. I think there is a problem with LG's memory management.
-----------
sent from my calculator with android
Click to expand...
Click to collapse
If I flash CM7.1.0.1 stable, will ClockWorkMod 3.0.2.7 that I flashed for the CM7 RC suffice? Or do I need to update that too before flashing? Sorry to drag the thread along.
LuponX said:
If I flash CM7.1.0.1 stable, will ClockWorkMod 3.0.2.7 that I flashed for the CM7 RC suffice? Or do I need to update that too before flashing? Sorry to drag the thread along.
Click to expand...
Click to collapse
It should work fine flashing any zip, but the 5.0.2.0 version of CWM is far better. Flashing it with the One Click tool is a no brainer. Go ahead and update it. It will only take you a few minutes of your time.
jboxer said:
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
Click to expand...
Click to collapse
Do you have any evidence to support that? From what i've read android is made to run better when more memory is used.
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
I never had to reboot my Nexus One, or even my T-mobile G1.
I've tried just about every rom for the g2x since i got it about a month ago and they are slow down. I'm not on the 2.3.4 rom and it started out great; now its almost unusable.
Anyone know whats wrong?? i'm about to call t-mobile and try to get another phone. I don't understand how they can release phones that just don't work. How can my single core 1ghz Nexus one be faster then this dual core 1ghz phone?
i'm just on stock and i have to reboot my phone every single day or else it's not useable. i have like zero apps on my phone almost so i know that can't be the problem, it's ridiculous
Sent from my LG-P999 using XDA App
tokimaromi said:
i'm just on stock and i have to reboot my phone every single day or else it's not useable. i have like zero apps on my phone almost so i know that can't be the problem, it's ridiculous
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good to know it isn't only me. I'm trying some more tests on my phone to see whats going on. I think i'm gonna call tmo soon and see what they say.
i'm sure they won't have a good reply for you but definitely share with us if they do! i understand having to reboot the phone like once every three days or so but every single day is totally unacceptable
Sent from my LG-P999 using XDA App
Did anything ever come from this? I'm completely stock, just got this phone the other day. This phone lags harder then my HD2 I just had, which I would have kept if the digitizer didn't go out.
Are you guys on stock? If so then i highly recommend going custom. LG can't code for crap, so lots of stuff that was wrong with this phone has been fixed in the recent custom roms/kernels.
I've had the same issue until i recently switched to Phoenix Blood rom. I recommend it if you want to forget when was the last time you rebooted and still use the phone buttery smooth. I am using Faux kernel and the ROM is rock solid for me. Recently ran and the V6 script(instructions are on the rom's page in development section) with it and now it's even better! Give it a try you would love it;-)
Sent from my LG-P999 using XDA App
Okay I'll check it out later, ya I'm out the box right now but not for long.
Sent from my LG-P999 using xda premium
Yeah get on a ROM without any LG coding or framework. If you guys prefer a more stock 2.3.3 feeling I would suggest Bionix Reloaded.
I make it a habit to reboot my phone every night before I sleep.
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?
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.