[Possible DEFECT] UPDATE! (Sep. 16, 2011) Touchscreen Responsiveness Issues - myTouch 4G General

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

Related

Keyboard randomly freezes on DHD ROMs!

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.

MT4G

Hey guys, I have a chance to switch out my MT4G for a G2x through insurance.
I know the spec difference, my only concern is how CM7 and MIUI run on the G2x?
CM7 and MIUI both run perfectly on the MT4G, so was worried that it won't be as good on the G2x.
Main concerns are if it has any GPS and or.wifi problems?
Anyways, any response would be greatly appreciated!
Sent from my HTC Glacier using xda premium
Both work great on it in my experiences miui runs smmoth as butter but mom's pictures come in and send out low quality pictures. And wifi calling doesn't work. CM7 is awesome especially with the new 7.101 update.
Sent from my LG-P999 using XDA Premium App
Mini still have wifi And GPS problem. Well lots of people does including me.
Sent from my LG-P999 using Tapatalk
Thanks guys. So there's some issues with the G2x running CM?
Sent from my HTC Glacier using xda premium
Both of those ROM's work and run awesome on the G2x. Although if you were to flash a ROM, i would definitely go with CM7. MiUi still has its problems....CM7 on the other hand, is very close to perfection!
Although, all phones are different...some could have running problems and some never do. I guess this what i like most about my G2x, i learn something new about the phone everyday. Lol.
But this phone is virtually, BULLETPROOF. (just like a 4G63 or 4B11 )
babymatteo said:
Both of those ROM's work and run awesome on the G2x. Although if you were to flash a ROM, i would definitely go with CM7. MiUi still has its problems....CM7 on the other hand, is very close to perfection!
Although, all phones are different...some could have running problems and some never do. I guess this what i like most about my G2x, i learn something new about the phone everyday. Lol.
But this phone is virtually, BULLETPROOF. (just like a 4G63 or 4B11 )
Click to expand...
Click to collapse
Thanks for the reply man! Screen bleed is the only hardware problem for this phone right?
mackster248 said:
Thanks for the reply man! Screen bleed is the only hardware problem for this phone right?
Click to expand...
Click to collapse
Kinda...some phones might be worst than others. Other know Hardware problems are the Random reboots and freezes. But a custom ROM should be able to fix any hardware imperfection.
i went from a mt4g to a g2x through insurance too and its the best decision i ever made it only has 1 issue, screen bleeding but it doesnt make a difference at all unless you put full brightness in a dark room thats when youll notice it or when you look from an angle and i only use miui for the g2x its perfect
babymatteo said:
Kinda...some phones might be worst than others. Other know Hardware problems are the Random reboots and freezes. But a custom ROM should be able to fix any hardware imperfection.
Click to expand...
Click to collapse
I believe random reboots and freezes are software issues
i went from a mt4g to a g2x through insurance too and its the best decision i ever made it only has 1 issue, screen bleeding but it doesnt make a difference at all unless you put full brightness in a dark room thats when youll notice it or when you look from an angle and i only use miui for the g2x its perfect
Click to expand...
Click to collapse
+1 I did the exact same thing and if I had to do it all over again, I would. I've been running eaglesblood for a while but started running CM7.1 the other day with no flaws. I don't even notice any screen bleed on my phone but my brightness is set low. Every G2x is different from the next.
Sent from my LG-P999 using XDA App
I use MIUI also. Works awesome except wifi on the latest build is iffy. Seems to not have problems at home but my work router seems to keep dropping and it's on my damn desk.
Wifi calling also doesnt work on MIUI.
CM7 I think is all good.
Little Bugs are still being nailed down but nothing to worry over.
Sent from my LG-P999 using xda premium
A few phones from the earlier batches (including mine, which has now been replaced with insurance... damn tile floors) had issues with the HDMI out causing the battery to short out when you plugged in an HDMI cable. The most logical explanation was bad soldering, but the issue was never common enough to make it to T-Mo's known issues.
Several people's phones got fried (there's a really old thread about it in this forum I believe), while in mine I just had to get a new battery. Doubt it would be an issue, but you can never know too little.

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?

How to upgrade the LG G2x P999 to Android 4.1.1 JB via CyanogenMod 10 (Unofficial)

Hi All!
Recently, while surfing through the ocean of ROMs for my LG G2X P999, I came across this ROM. Couldn't find any link related to this on XDA. So thought of pointing the G2X owners to this link:
http://www.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536/
Flashed it just yesterday. Apart from the Video-recording did not notice any bugs so far. In fact I haven't used it enough to comment on bugs. But I can confirm that Calls and Wifi are both working fine.
If any one knows any prior publication of this work on XDA; please let me know so we can avoid duplicates.
Hackfest in development section.
Sent from my LG-P999 using xda premium
Wifi calling probably does not work
Sent from my LG-P999 using xda premium
Pain-N-Panic said:
Wifi calling probably does not work
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
It doesn't,
I can't get it to work on anything that is not CM7 based.
Kinda blows that our phone is limited to cm7. I love cm7 as it is treating me well, but selection is always a nice privilege
Sent from my LG-P999 using xda premium
nagenderjeet said:
Hi All!
Recently, while surfing through the ocean of ROMs for my LG G2X P999, I came across this ROM. Couldn't find any link related to this on XDA. So thought of pointing the G2X owners to this link:
http://www.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536/
Flashed it just yesterday. Apart from the Video-recording did not notice any bugs so far. In fact I haven't used it enough to comment on bugs. But I can confirm that Calls and Wifi are both working fine.
If any one knows any prior publication of this work on XDA; please let me know so we can avoid duplicates.
Click to expand...
Click to collapse
so data is working? i thought the data or radio was still broken. does this mean we may get a somewhat stable build of JB?
Still a hackfest.
Sent from my LG-P999
Pain-N-Panic said:
Kinda blows that our phone is limited to cm7. I love cm7 as it is treating me well, but selection is always a nice privilege
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I tried a couple different versions of CM7 over the past few days, and its nothing but a nightmare. It will run flawlessly for hours and then something quirky will happen and I either cant get data, or cant make calls, or my screen locks up, and im rebooting the phone or looking for a fix on google. Wound up just going back to the stock rom with faux123 kernel.
Spawne32 said:
I tried a couple different versions of CM7 over the past few days, and its nothing but a nightmare. It will run flawlessly for hours and then something quirky will happen and I either cant get data, or cant make calls, or my screen locks up, and im rebooting the phone or looking for a fix on google. Wound up just going back to the stock rom with faux123 kernel.
Click to expand...
Click to collapse
Well the problem is that other developers take the vanilla cm7 code and tweak/mod the hell out of it which is always awesome but they put out an unstable build/ROM. If you haven't tried vanilla CM7.2 from get.cm (latest build) then you're missing out. I have had the ROM installed running with mazout's latest kernel for over a week now and its been running extremely well. All and any problems that I experienced with this setup were directly due to ignorance and human error as I'm still a flaming n00b. At the same time they were great learning experiences and easily fixed.
Spawne32 said:
I tried a couple different versions of CM7 over the past few days, and its nothing but a nightmare. It will run flawlessly for hours and then something quirky will happen and I either cant get data, or cant make calls, or my screen locks up, and im rebooting the phone or looking for a fix on google. Wound up just going back to the stock rom with faux123 kernel.
Click to expand...
Click to collapse
The problem is going to lie in your setup somewhere.
Maybe kernel level as it is known that some G2xs will run great on Trinity but crash on Faux and vice versa. That's just a quick example.
I've run vanilla CM7 for like 13 months now and do not encounter the issues you are describing.
Soooo...what's your setup.
ROM w/build date
Kernel and version
Baseband date
Sent from my LG-P999 using xda premium
Data does work
joker550 said:
so data is working? i thought the data or radio was still broken. does this mean we may get a somewhat stable build of JB?
Click to expand...
Click to collapse
Data does work but there is issue related to rapid battery drain. Back to my stock ROM. This hasn't been updated since a long time. I wonder if any developer at all is working on this phone or not!
nagenderjeet said:
Data does work but there is issue related to rapid battery drain. Back to my stock ROM. This hasn't been updated since a long time. I wonder if any developer at all is working on this phone or not!
Click to expand...
Click to collapse
You are late to the party... This device is a dying device. There's 1 dev working on a CM7 Kernel and that's about it. More than likely we will never see fully working 4.1.1 or higher on our device. They tried real hard and are some talented people (our devs), but LG handed them a broken pile of excrement and said, "here you go... Jellybeans!!"...
New2my8125 said:
You are late to the party... This device is a dying device. There's 1 dev working on a CM7 Kernel and that's about it. More than likely we will never see fully working 4.1.1 or higher on our device. They tried real hard and are some talented people (our devs), but LG handed them a broken pile of excrement and said, "here you go... Jellybeans!!"...
Click to expand...
Click to collapse
That's almost all true! I have another old phone, Mytouch4g/HTC Glacier. On that one I am running 4.2.2 and there is a lot of development still on. Huge number of ROMs which can be used as daily drivers. But here we don't even have a perfectly working 4.0.4. But again, no complain to Developers. they have tried really hard with a lot of time invested in this device. All the blame on LG.
This phone is lightning fast on 2.3.X variants. still very much usable. I may be late to the party, but the party is yet not over
I just want to chime in that I used this and the phone is working. The camera seems slower (and therefore more blurry). Other than that everything that I use (I do not use bluetooth, tethering, or wi-fi calling) is working. It's about the same speed as CM7 I had on here before. Don't know about battery since I only just did it.
If anyone knows any tricks for the camera please share. I babysit a toddler and his face is often blurry in photos. I'm pretty sure with this new ROM it will be even more blurred. I have already removed the plastic cover over the camera lens, it's not that issue. This is clearly software as it has gotten slower with this ROM.
We thought we might have a jellybean breakthrough when cm started deving cm10.1 on the p990 and had the courtesy of posting a half port of their work in progress. I believe it's called AdamPK's cm10.1 and is usually found with Mazout360 kernel. Hardware Acceleration Work so no camera, camcorder, sluggish or other problems that plagued the hackfests but they ran into and issue with the radio because O2x and G2x use different radio chips. So you have wifi but no data and battery can't be read correctly but other than that it would be as close to a perfect 4.x as we could get.
http://forum.xda-developers.com/showthread.php?t=1977573

My thoughts on my Optimus 3D P920

Well, I've been using this phone for 6 months now, I got it as a brand new phone. Maybe some of you interested in this, so let me point out the pros and cons here. Also, the point of this thread is to find a solutions to the mentioned _problems_ :angel:
Cons.
ICS is a battery and RAM hog. Sometimes I have the feeling that it's like running Windows 7 on a Pentium 3 with 512MB RAM. It's working but not as _fluid_ as Windows 98 on the same machine. Battery performed much much better on Froyo.
I heard there was a ghost call issue with GB ROMs. Never used GB on my P920.
Again, ICS. Since I am on the new OS I think I have to push the screen a bit more agressively. On Froyo I barely had to touch the screen and the phone responded very well. Not on ICS.
On Froyo with the same device the GPS lock were about 2-10 minutes. Such a joke.
Pros.
On ICS, I can get a GPS lock in 10-15 seconds. That is awesome. But still, battery drains much faster.
Finally I can use apps that require Android 4.0+ but I've been okay with Froyo.
Well, what do you think? I'm not saying that ICS is a bad os, but I beleive now that this handset is just way too underpowered to run ICS smoothly.
I also run into another issue, please refer to this thread.
Another question would be, how can I downgrade to a stable GB ROM (a rom without ghost calls) from the current ICS? Look, fellas. I'm not that techy guy but I can deal with it following a tutorial or something. But there are so many around here and can't decide which one to follow and the last thing I want to do is brick my phone. I'm kinda looking for a ROM where all the bloatware vanished from it
Appreciate your input, and sorry for the crappy layout and explanations, I'm not native when it comes to english
Take care!
pebito said:
Well, I've been using this phone for 6 months now, I got it as a brand new phone. Maybe some of you interested in this, so let me point out the pros and cons here. Also, the point of this thread is to find a solutions to the mentioned _problems_ :angel:
Cons.
ICS is a battery and RAM hog. Sometimes I have the feeling that it's like running Windows 7 on a Pentium 3 with 512MB RAM. It's working but not as _fluid_ as Windows 98 on the same machine. Battery performed much much better on Froyo.
I heard there was a ghost call issue with GB ROMs. Never used GB on my P920.
Again, ICS. Since I am on the new OS I think I have to push the screen a bit more agressively. On Froyo I barely had to touch the screen and the phone responded very well. Not on ICS.
On Froyo with the same device the GPS lock were about 2-10 minutes. Such a joke.
Pros.
On ICS, I can get a GPS lock in 10-15 seconds. That is awesome. But still, battery drains much faster.
Finally I can use apps that require Android 4.0+ but I've been okay with Froyo.
Well, what do you think? I'm not saying that ICS is a bad os, but I beleive now that this handset is just way too underpowered to run ICS smoothly.
I also run into another issue, please refer to this thread.
Another question would be, how can I downgrade to a stable GB ROM (a rom without ghost calls) from the current ICS? Look, fellas. I'm not that techy guy but I can deal with it following a tutorial or something. But there are so many around here and can't decide which one to follow and the last thing I want to do is brick my phone. I'm kinda looking for a ROM where all the bloatware vanished from it
Appreciate your input, and sorry for the crappy layout and explanations, I'm not native when it comes to english
Take care!
Click to expand...
Click to collapse
Almost all GB Basebands have ghost call problems.
It's baseband related not ROM.
In v21e it occurred less frequently so people got the idea that it's not present. It is.
You have to flash an ICS baseband to get rid of the ghost call problem. I don't know if it's compatible with a ginger ROM.
I suggest giving cyanogenmod a crack , in either dual-boot or otherwise.
It's the fastest ROM there is but 3d and wireless hotspot doesn't work. I don't use those really.
It has nothing to do with the handset , the stock ROM is poorly made is all.
Sent from my LG-P920 using xda premium
Be warned that ICS does had the ghost problem issue too.
I have thoroughly tested it and found it to happen on several occasions.
omgomg said:
Be warned that ICS does had the ghost problem issue too.
I have thoroughly tested it and found it to happen on several occasions.
Click to expand...
Click to collapse
Ouch. Thanks for the heads up! Any chance to get back to a custom Froyo maybe? The phone was really fast with that OS, and I don't see much benefits running ICS on the P920.
omgomg said:
Be warned that ICS does had the ghost problem issue too.
I have thoroughly tested it and found it to happen on several occasions.
Click to expand...
Click to collapse
I have not had this happen in Texas on v30A or v30C basebands.
I've tested it using both 30A and 30C basebands. Either on stock and non-stock ROMs.
I'm absolutely sure about this as I did the tests myself in front of my own eyes.
This also applies to ghost SMS, both sent and received.
SMS reported as sent were never delivered and I missed some received SMS too, checked from few different friends.
Hmm, dunno then. I've had some callers with the wrong number, but I have definitely had no SMS issues, except when I wad on 'ported ICS' from SU760, and that was only a character limit and no picture messages. Once official LG ICS for P920 came out, those bugs were killed.
If you used LG update tool, well that's another matter.
Sent from my Oldschool Hardcore LG P925 with XBSA vR3D ROM and Backside Boneless FTW
omgomg said:
I've tested it using both 30A and 30C basebands. Either on stock and non-stock ROMs.
I'm absolutely sure about this as I did the tests myself in front of my own eyes.
This also applies to ghost SMS, both sent and received.
SMS reported as sent were never delivered and I missed some received SMS too, checked from few different friends.
Click to expand...
Click to collapse
I'm noticed ghost issue too, but only when i had installed xposed framework.
Sent from my LG-P920 using xda premium
krija said:
xposed framework
Click to expand...
Click to collapse
What is that?
drastic00 said:
What is that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24267797
Sent from my LG-P920 using xda premium
omgomg said:
Be warned that ICS does had the ghost problem issue too.
I have thoroughly tested it and found it to happen on several occasions.
Click to expand...
Click to collapse
No v30c baseband doesn't have ghost calls. I thoroughly tested it.
Maybe the one you tested is v28b beta?
Sent from my LG-P920 using xda premium
Well, happened me today. A friend of mine called me three times - and not a single notification on my phne. This is definitely no good. Guys, any chance to downgrade to Froyo? It was working just fine for me, but I can't find a guide or software anywhere.
pebito said:
Well, happened me today. A friend of mine called me three times - and not a single notification on my phne. This is definitely no good. Guys, any chance to downgrade to Froyo? It was working just fine for me, but I can't find a guide or software anywhere.
Click to expand...
Click to collapse
As far as I know, this is the best solution for all your programs.
This special build got absolutely no serious bugs so you will enjoy it.
Follow this http://forum.xda-developers.com/showthread.php?t=2195753
Karim Kahale said:
As far as I know, this is the best solution for all your programs.
This special build got absolutely no serious bugs so you will enjoy it.
Follow this http://forum.xda-developers.com/showthread.php?t=2195753
Click to expand...
Click to collapse
Thanks for the heads up. Downloading the files now, will post an update to there if I'm stuck. Anyways, what caused that the GPS lock took forever on Froyo? It's still super fast on ICS, even in offline mode. It's a crucial question for me, I like to geocache sometimes and it comes really handy
pebito said:
Thanks for the heads up. Downloading the files now, will post an update to there if I'm stuck. Anyways, what caused that the GPS lock took forever on Froyo? It's still super fast on ICS, even in offline mode. It's a crucial question for me, I like to geocache sometimes and it comes really handy
Click to expand...
Click to collapse
Try to set your ntp pool server in accordance to your location.
That'll speed it up.
If it doesn't fix it , i think it's simply a problem with froyo roms.
There's just no way i'm gonna use froyo now that i had a taste of vanilla android with cyanogenmod.
I'm selling this already , will go for nexus 4 or galaxy s4 i think.

Categories

Resources