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.
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?
I flashed this ROM about a week ago or so and only when I'm at home does my signal completely drop. Sometimes it even says emergency calls only. This signal loss dilemma is driving me insane. Has anyone else had this issue or know of a fix? I read online on another website that another person had this problem, but they're using a completely different phone than me. The article stated to try flashing a new radio, would doing this make a huge mess? I'm totally new to flashing kernels and never flashed a radio before. Initially I had no sound when I first flashed the ROM and read that Tiamat 1.1.5 kernel would fix that, which it did. I really like this ROM and I've never had this before but if I can't get a steady signal I'll have to switch. I read that MIUI v4 builds don't support themes completely, but they do support lock screens, icons, and wallpaper changes. Any ideas on what I should/can do?
Before flashing a radio, I would say to re-flash the rom.
Full wipe and re-download the file.
Sent from a dream.
Try restoring your APN settings.
Sent from my GT-N7000 using xda premium
ok. I started my phone from scratch earlier. Everything was fine. Flashed Final-fixed. Everything was fine. Got a few apps back, everything was fine. After a while, I flashed the Booster... rebooted, and now my status bar/notification bar is GONE! On boot, I get an error about systemui problem had to force close. How can I fix this?
Exact error, which came up when in SetCPU, which is also giving me problems:
The application Status Bar (process com.android.systemui) has stopped unexpectedly. Please try again.
Final fixed already comes with booster. You're constantly having problems no one else is. You're not reading. You're flashing randomly. You're not doing things right. If you don't want problems go back to stock, or you can read carefully and not just flash willy nilly
FBis251 said:
Final fixed already comes with booster. You're constantly having problems no one else is. You're not reading. You're flashing randomly. You're not doing things right. If you don't want problems go back to stock, or you can read carefully and not just flash willy nilly
Click to expand...
Click to collapse
No man, I DO READ. I read it all. Sometimes I get a little confused about what some things are, but I'm not a dev, and this is my first smart phone. I'm NOT flashing randomly, either. Jesus, man not everyone can just jump right into this stuff and know it all. If you didn't want to offer a little help or a solution, don't be an ass. I'm trying to learn ffs. I was under the impression that val final and val black were different.
Seriously man? 6 posts in a row:
http://forum.xda-developers.com/showthread.php?p=27290880#post27290880
If someone had help to offer you're gonna have to wait for it. You're spamming the hell out of the board, so how about YOU quit being an ass.
I don't think you're reading at all. You're doing more typing and flashing than reading. If you don't understand how something works, why are you flashing it? You should be trying to understand how it's going to affect your device.
My advice: reflash valhalla final, don't install any tweaks. Valhalla final is one of the most stable roms out there and it's been used as the base for at least 3 roms that have been posted.
Here's a lot of reading for you:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
FBis251 said:
Seriously man? 6 posts in a row:
http://forum.xda-developers.com/showthread.php?p=27290880#post27290880
If someone had help to offer you're gonna have to wait for it. You're spamming the hell out of the board, so how about YOU quit being an ass.
I don't think you're reading at all. You're doing more typing and flashing than reading. If you don't understand how something works, why are you flashing it? You should be trying to understand how it's going to affect your device.
My advice: reflash valhalla final, don't install any tweaks. Valhalla final is one of the most stable roms out there and it's been used as the base for at least 3 roms that have been posted.
Here's a lot of reading for you:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Click to expand...
Click to collapse
Thanks, that's better man. FYI, i'm not posting the same stuff everywhere. I'm reading and learning stuff, then trying to see what I can do. It's not all the same posts, just like the last 5 of mine have been about the notification bar, but all different querys. I'll clean it up tho, after I get sorted out. Also, I've already read the whole wiki, and the ENTIRE threads for all the things I've considered flashing.
Oh, how do I get into my phone if I cant pull down the notification bar to connect USB?
Never mind. I know already. Mount USB in CWM sry.,
Just an update after lots of troubleshooting, in case anyone might run across the same problem and did as I did:
I added the paid version of SetCPU to system/apps in the zip of the ROM I was flashing. I guess that's what was causing the issues, because now everything is stable. I kept Paid ADW Launcher, replacing the stripped down version, also a modified SystemUI.apk, framework-res.apk, and twframework-res.apk. All three from the zip I got from UOT Kitchen. So, now this great rom is even greater, and HIGHLY customized. Dont know why the modified crucial apks will work, but it wouldn't take the addition of setcpu...
If you pushed those apk's without rebooting to recovery and fixing permissions that will throw all the force closes.
eollie said:
If you pushed those apk's without rebooting to recovery and fixing permissions that will throw all the force closes.
Click to expand...
Click to collapse
After I figured out what you meant by 'pushing', I got it sorted out just like you said. Thanks man!
Regarding Twistedumbrella 4.04 Rom found here:
I've never donated to a developer (shame on me) but I just did for this one. I really want to keep my Thunderbolt going cause I'm off contract and have an unlimited data plan. Like some are reporting, the most recent builds of this ROM gave me a boot loop and I can't run them, but anyone considering trying this rom I encourage you to try the 12/06 edition at the link below. This 12/06 installed for me and ran just fine, and I am SO pleased at the increased speed AND battery life that I perceive I am getting. This ROM is not loaded with the HTC sense overhead, and things seem much snappier all around. I was about to ditch my Thunderbolt because things had slowed to molasses using the original BAMF 4.04 rom, but this one is working great!
Here's the link (copied from the thread linked above)
THANK YOU TWISTEDUMBRELLA
I too would like to join in and say thanks to twisted. His rom is the only thing that is keeping me on the Tbolt. I am one of the few with a model that gets bootloops from the newer versions but 12/06 works great for me.
I'm grateful too...
Ionace7 said:
I too would like to join in and say thanks to twisted. His rom is the only thing that is keeping me on the Tbolt. I am one of the few with a model that gets bootloops from the newer versions but 12/06 works great for me.
Click to expand...
Click to collapse
I too am grateful for the twisted ROM. I also have the boot loops on versions younger than 12/06. I also have the serial number ending in "A". However, my Bolt is working quite well with the 12/06 ROM!
Thanks Twisted!
bbshopper said:
I too am grateful for the twisted ROM. I also have the boot loops on versions younger than 12/06. I also have the serial number ending in "A". However, my Bolt is working quite well with the 12/06 ROM!
Thanks Twisted!
Click to expand...
Click to collapse
What 4ext recovery version are you using? I'm using rc8 and all his builds boot fine. Hall is using rc5 and doesn't get them either. I'm just curious if the rc9 version of the recovery has a bug that is causing the boot loops.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
What 4ext recovery version are you using? I'm using rc8 and all his builds boot fine. Hall is using rc5 and doesn't get them either. I'm just curious if the rc9 version of the recovery has a bug that is causing the boot loops.
Click to expand...
Click to collapse
As mentioned in the Dev section thread, the bootloops coincide with a certain version of hardware of the Tbolt. Specifically, those with a TBolt with a model number ending with an "A" are affected by the bootloops. It doesn't have anything to do with the recovery software.
Bingo. I pulled my battery to check the serial number and yes indeed, mine ends "A." But like is also mentioned above, my 12/06 rom is running VERY well, so I'm completely happy where I am.
But thanks for pointing this out -- that saves me a lot of time from being tempted to play with the recovery software or partitions or anything else.
Ionace7 said:
As mentioned in the Dev section thread, the bootloops coincide with a certain version of hardware of the Tbolt. Specifically, those with a TBolt with a model number ending with an "A" are affected by the bootloops. It doesn't have anything to do with the recovery software.
Click to expand...
Click to collapse
Ionace7 said:
As mentioned in the Dev section thread, the bootloops coincide with a certain version of hardware of the Tbolt. Specifically, those with a TBolt with a model number ending with an "A" are affected by the bootloops. It doesn't have anything to do with the recovery software.
Click to expand...
Click to collapse
That still doesn't take away from the fact that the recovery could be causing the problem. It's possible that whatever is different with the hardware could have an affect on the recovery as well.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
That still doesn't take away from the fact that the recovery could be causing the problem. It's possible that whatever is different with the hardware could have an affect on the recovery as well.
Click to expand...
Click to collapse
Good point, nonetheless it seems there may be a work around of restoring just the boot data from a earlier (12/06) version of the rom will make the newer ones work while sacrificing the camera (it stops working).
Update: (don't want to keep adding off-topic posts) The work around worked for me without any problems (camera worked) when going from 12/06 to 12/19. Also the new 12/28 update doesn't bootloop for me.
But for a majority of tbolt usrs if u got a p/n ending with an "A", "B" and you experience any issues i.e. bootloops I caution you to stay away from ics for now until something stable comes out if it ever will. Lol!
For those with p/n "C", "XC" etc happy flashing. Seems these experience random reboots at some point but do not have major issues as the ones above.
Just thot I'd put this out there for those going thro bootloops and its driving them nuts!
Sent from my ADR6400L using Tapatalk 2
I cannot believe anyone actually used the BAMF ICS rom for more than 5 mins. that rom is full of so much wack. Never had any bootloops with any of Twisted builds and ive tried pretty much all of them since day one. TWRP...
a bit of info on this particular bootloop for those not following the thread:
-flashing a previous working boot partition from recovery seems to get you past the loop (e.g. flash new rom, restore boot from 12/06 backup)
-alternatively, the 12/28 version on page 28 of the thread works with no loop on my particular hardware. i think twisted is still working on a final build though, which could potentially return to bootlooping if he hasn't isolated the problem.
viceversa said:
I cannot believe anyone actually used the BAMF ICS rom for more than 5 mins. that rom is full of so much wack. Never had any bootloops with any of Twisted builds and ive tried pretty much all of them since day one. TWRP...
Click to expand...
Click to collapse
HA! I deserved that, vice versa. I know enough to be dangerous to myself most of the time but that's about it. The BAMF rom looked so much prettier I stayed with it but it ended up a nightmare, as you suggest. I'm now almost on my 24th hour of the 12/06 rom and no spontaneous resets at all, MUCH better batter life, MUCH snappier in general, and I am MUCH happier with my thunderbolt! Presumably there's things that need to be improved past 12/06, but I'm not so much of a power user (obviously) even to have found them.
freecicero said:
HA! I deserved that, vice versa. I know enough to be dangerous to myself most of the time but that's about it. The BAMF rom looked so much prettier I stayed with it but it ended up a nightmare, as you suggest. I'm now almost on my 24th hour of the 12/06 rom and no spontaneous resets at all, MUCH better batter life, MUCH snappier in general, and I am MUCH happier with my thunderbolt! Presumably there's things that need to be improved past 12/06, but I'm not so much of a power user (obviously) even to have found them.
Click to expand...
Click to collapse
If you liked the bamf leak then try NuSense out. It is a fantastic rom that uses parts from it and a desire hd rom. For a snappier version that is more stable than the aosp rom try unsense.
Sent from my ADR6400L using Tapatalk 2
I've never had boot loops with any of twisted's releases. I did however had the occasional random reboot. I'd go to answer a phone call and this sucker would just reboot on me for no reason.
Sent from my ADR6400L using Tapatalk 2
rafaelvelasquez2 said:
I've never had boot loops with any of twisted's releases. I did however had the occasional random reboot. I'd go to answer a phone call and this sucker would just reboot on me for no reason.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
The only time I heard of that was when people used the leaked radios or the combination radio made from the leak and .19 radio.
Sent from my ADR6400L using Tapatalk 2
Hey guys I have run into a problem I would appreciate any comments on -- I've been all over the internet reading about the failure of Google Maps/Navigation to read street names in Andriod 404 without finding anything that helps me. I already had Ivona voice installed, and I even installed SVOX to see if that what help, but the app refuses to use anything but the standard voice, and it never gives street names, just "turn right, turn left" etc.
I've done all the clear data and cache suggestions and that isn't helping.
Does anyone know if a fix was developed that I can apply using this 12/6 ROM? other than that this rom is working great for me, and I suspect the problem isn't in the rom itself. I'd even gladly download an older version of the MAP apk if I could find it - I don't use the advanced MAP features at all.
Thanks for any suggestions.
freecicero said:
Hey guys I have run into a problem I would appreciate any comments on -- I've been all over the internet reading about the failure of Google Maps/Navigation to read street names in Andriod 404 without finding anything that helps me. I already had Ivona voice installed, and I even installed SVOX to see if that what help, but the app refuses to use anything but the standard voice, and it never gives street names, just "turn right, turn left" etc.
I've done all the clear data and cache suggestions and that isn't helping.
Does anyone know if a fix was developed that I can apply using this 12/6 ROM? other than that this rom is working great for me, and I suspect the problem isn't in the rom itself. I'd even gladly download an older version of the MAP apk if I could find it - I don't use the advanced MAP features at all.
Thanks for any suggestions.
Click to expand...
Click to collapse
Wrong forum my friend
Sent from my ADR6400L
Wifi Working at all?
Has anyone gotten any of the WiFi apps to work on this? Barnacle works on Ad-hoc, but I can't seem to get even the Wifi Tether app to work. Thanks guys.
pdub517 said:
Has anyone gotten any of the WiFi apps to work on this? Barnacle works on Ad-hoc, but I can't seem to get even the Wifi Tether app to work. Thanks guys.
Click to expand...
Click to collapse
Wireless tether has to be setup using the Google nexus one profile. Routing fix checked and wake lock checked.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The only time I heard of that was when people used the leaked radios or the combination radio made from the leak and .19 radio.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Really, I been only getting the random reboots, however I am on the leaked ICS radio.
Maybe I should switch back to the stock .19 radio.... Unless the new HTC ICS radio comes out soon with this update.
Does anyone know where the radio forum went too?