[Q] AOSP Keyboard keep crashing on CM10 - HTC Sensation

Hello there,
i've tried to find an answer to my question in the forum and on the internet but, to the present day, I'm still wandering in the dark.
On my sensation i used to have a CM10 rom which worked quite well and, in october, i decided to switch to viperS 1.4.1.
Now i wanted to try again CM10 (doesn't matter which one, i've tried both bruce's and jellybam, the problem is the same) but right after flashing the AOSP keyboard keeps force closing making the phone useless. I'm not new to flashing roms so i've tried formatting all partitions (except sdcard) and flashing again but no progress was made. I've even flashed the latest 3.33 firmware just to be sure and tried clearing the keyboard data from "settings->applications": still no result.
If i restore the viperS backup, the phone works flawlessly (even tho i'm using switftkey there, so i don't know if the aosp kb works right under viper).
Any thoughts? Is there something else i could try?
Thank you very much in advance, regards.
A.

Related

[Q] 4 separate ROMS. Gets stuck at Turning wi-fi on, nothing else

I have tried all of the ICS roms, and always gets stuck at the same spot. Wi-fi is turning on.
It worked on the Revolver 4, but I wanted to try another one. Did a super wipe, and bam. Nothing after that..
Any thing I might be able to try?
Nandroid restore, if that won't work nvflash?
you mean use NVflash to do the rom install vs the recovery?
I made a topic about this, check my post (not able to give you a link right now sorry)
I also need help with this. I am trying to come from CM9 cornerstone build back to revolver. I have done a couple restores and I still get no WIFI. Anybody have anymore info on this?
Have a look at this : http://forum.xda-developers.com/showthread.php?t=1530612
You can try this:
- Turn off wifi
- rename the file /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
- reboot
- try wifi again to see if it works
**note
This might cause the tablet to forget any previously saved networks.
I have tried Outpoxs' method in varies combinations with no success also I have tired your method a.mcdear and also with no success. Mine is still stuck on Turing WI-Fi on... The one thing with outpox method there might have been something I was doing wrong.
This is how I fixed my tablet after 15 hours of trying everything. I downloaded the ota rooted full version of ics and performed a full wipe then made sure it booted into that rom with wifi working then proceeded to flash my revolver backup with no problems. Hope that helps.
Similar WiFi issue - still stuck
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
I've have a rooted TF101 B50 and most ROM's that I have tried seem to fail at this point as well. However, I did notice that when I flashed my first ROM (AOKP) it has the same stock kernel. So I tried another one. This time was Revolution 4. It seemed to work out just fine because I belive it has the stock kernel. Next I moved onto a CM10 Eruoskank ROM. It too had the problem of the AOKP ROM in that after I flashed it, the stock kernel was still present, presumably left over from the Revolution 4 ROM. I am now on Android Revolution HD 3.5.0 and it seems to work fine so I am sticking with it for the time being.
I beleive something in the flashing script of the ROM or the recovery program itself is not flashing the /boot partition properly. I am not a developer nor do I have an in depth knowledge of the inner workings of Android...but this is just a guess. I hope there is a way to flash just a kernel in the /boot partition from these individual ROMs. That would be nice.
If can access recovery then do a full wipe(system, cache and dalvik) and install the ROM again... that should do the trick... you might wanna try some other kernel also... there few kernels for ICS in the forum look for them and flash them via recovery...
Sent from my Transformer TF101 using xda app-developers app
It seems as thought someone else is on the same track as I am.
http://forum.xda-developers.com/showpost.php?p=29447134&postcount=8
rstry this:
take unit out of dock if you use one. restore via cwm if u can, to 3.01 firmware, honeycomb. wipe all cache, data, etc prior to flash.
DO NOT SIGN INTO GOOGLE ACCOUNT.
Turn tablet completely off following boot. Cold boot back on. Grab latest official firmware off Asus website, xx.27
Install via CWM, and again wipe ALL.
Boot into system again, and cold boot back on. Asus should prompt you with 300mB update now, which differs from the official .27,but had same filename...
I found this bug/glitch a few hours ago... Somehow downgrading to HC and back to stock triggers this unknown update...
See if you can reproduce please. I also saved the firmwares to sdcard external.
The various ROMs require a supporting kernel. I would try obtaining the correct kernel for the ROM you want and then flash them both at the same time from recovery.
Resolved - for me
From replies here and other research, it became clear to me that I should reflash my transformer back to stock (NVFLASH down to the metal). Every other ROM would show the stuck WiFi issue or (worse) would get into a boot loop.
This was something of a problem, because my volume up button was broken and I couldn't enter APX mode. I finally managed a workaround for that (see http://forum.xda-developers.com/showthread.php?t=1890236) and then used EasyFlasher to restore the Asus firmware. Now the WiFi works fine and all is well again.
So, as a last resort - scrub and start over.
Cheers!
--Roger
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
I also have the same issue. Bought the eee pad transformer with a cracked screen; touch screen did not work. I replaced it and everything works great! except for Wi-Fi =\ Any help would be greatly appreciated!
You should really start your own thread. That being said, first thing to try is to back up all your data and wipe it to factory using EasyFlasher. If the problem persists after a stock firmware flash, then it's likely a hardware issue. If it's resolved, then it was a rom/software issue.
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
Im 99% sure your problem is that you haven't got the right kernel for the rom your using, this is the usual outcome - wifi not working/ turning on. i don't think nandroid backs up the kernel so your basically restoring stock ICS rom with cm9s kernel. Try find the related kernel to rom your currently on. As for your rom failed flashing, you might be using a very old recovery try updating to the newest twrp recovery. Better yet join the dark side and move up to Jelly Bean, makes the tf101 a whole new device.

Bluetooth never reconnecting to my car's audio [SOLVED]

Hi all,
I have used ARHD's ROM for some time (ever since ICS i think) and I thought it might be time for a change since some Jelly Bean ROMs started appearing in the forums. I first tried Bruce2728 CM10 ROM. Installed with 4Ext wiping everything before hand from recovery and NOT with a superwipe script (ARHD). Everything worked fine but the bluetooth. I could easily pair and connect to my car's audio system (for calls only) but everytime I would turn the car off and turn it back on again, it would not reconnect. If I tried to re-pair the phone, it would work until I'd stop the car again. So I tried other ICS (OpenSensation and CM9) and JB (AOKP) ROMs but every single one had the exact same issue.
So I went back to a Sense based ROM (Virtuous) and everything went back to normal... up until this week. I tried again AOKP's ROM since I had a reply from a user saying he didn't have that issue but, no luck so, I restore my Virtuous back up from and with 4Ext and now, i'm having the same problem with Virtuous...
What am i doing wrong? I've wiped everything but the sdcard (Data, Cache, Dalvik, ...), I haven't changed kernel for each rom, meaning I've used the one recommended for each (could another kernel help?). Should I used a superwipe script? Any info available in the logcat?
Please help!
Wiped everything twice and flashed AOKP's ROM. Works.

[Q] Wifi Issues

I would have posted this in the Sensation Android development area, but I don't have sufficient privileges to do so.
I no longer have WiFi.
I am using the 4.1.2 CM Kang, and I originally had WiFi working with that ROM, but it stopped working about a weeks ago, and I can't get it to come back.
If I watch the Wifi on/off toggle, I can see it blink white for a split second then return to grayed out about once every 5-10 seconds.
I've checked the WiFi settings, and the only thing that looks peculiar is that the region code under Advanced says "Europe," but when I try to change that, it just reverts.
I have tried a factory data reset,re-flash of the ROM, and installing newer versions of the ROM with no luck.
Does anyone have any suggestions?
tried this ?
WiFi will not turn on
ganeshp said:
tried this ?
Click to expand...
Click to collapse
I tried to install WiFix Manager, and I followed the directions closely, but WiFi still will not turn on.
The country code always reverts back to Europe in the Advanced WiFi Settings.
I'm on T-Mobile US, running AOKP aokp_pyramid_unofficial_Oct-19-12.zip; a JB ROM; 4.1.2
I previously tried the CM10 Kang for the HTC Sensation, but switched ROMs to make sure that it wasn't issue with the ROM.
To be clear, my problem is not that the WiFi radio never locks to a particular signal, it's that the WiFi radio won't even turn on.
When I go to WiFi settings it just says, "Turning on WiFi...," and never actually turns on.
My best guess was that it had something to do with the WiFi country code, but that's really just a stab in the dark; open to suggestions.
Thanks
bump
Surely, there's someone out there that can help?
kosstheory said:
Surely, there's someone out there that can help?
Click to expand...
Click to collapse
In order of easiest and quickest to longest time it will take to do each one...
Install the latest version of the ROM (10/23) overtop of your existing rom (5 minutes)
If that doesn't work...
Do a full wipe and install a fresh copy of the latest version. (15 minutes, with Nandroid backup)
If that doesn't work...
Format your SD card (save all the contents to your computer first) (40 minutes between copying every to the computer and back to the SD card)
NON ROM RELATED OPTION IF YOU ARE S-OFF
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops. (5 minutes, but a little more involved)
My guess is that the full wipe and fresh install is the most likely to work the first time.
Skipjacks said:
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops.
Click to expand...
Click to collapse
is there a sensation specific guide for this procedure?
Still perplexed
How do I know which kernel and radio combination should work best with my ROM. I switched out to AOKP to see if that was the problem, and I believe I'm using the 3.33 Kernel, but I don't know how to check to make sure it installed correctly.
Had the same problem as you but a full wipe and reflash would bring it back. Seems to be a CM10 problem since it happens with Bruce's and Paranoid roms. Try a Sense rom and see if wifi works.
Is OpenSense considered a "Sense ROM?"
http://forum.xda-developers.com/showthread.php?t=1926858
Try that rom, more stable and better performance than all the popular roms.
I had the same problem only option was another room Android_Revolution_HD-Sensation_6.8.0 (this is the rom)
so long, and thanks for all of the fish...
I figured it out.
I bought a Samsung Galaxy S III. WiFi is working again.
Thanks for all of the help!
wifi cm10
I have tried several CM10 roms. It is as you said about the region code. It reverts back to the original and doesnt save it on the settings
Even though editing db file doesn't work. Actually it changes the country code. I guess the ROM changes it during booting. Because while it boots you can see that the wifi is connecting first then goes off. I have tried several roms. DOnno what the problem is. probably JB both on cm10 and aokp

XT925 - Wifi not working after Custom Rom install (but bluetooth works?)

So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
di3zelherbert said:
So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
Click to expand...
Click to collapse
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
koftheworld said:
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
The first time, no. I thought I may have installed 4.4 incorrectly so after installing 10.2 i tried flashing 4.4 again, but I did wipe the caches, system, data and dalvik caches the second time going back after reading in this forum how to flash over a custom rom. But then seeing that the bugs were still there, i wiped again and went back to 10.2 and I've been there for a day now.
Missed Wifi
I'm facing the same trouble , same conditions.
Solved
zirig said:
I'm facing the same trouble , same conditions.
Click to expand...
Click to collapse
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
zirig said:
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
Click to expand...
Click to collapse
That worked! Thank you!

[Q] Touch Screen Not Working with Non-Sense ROMs

Hello,
I've used Cyanogenmod 9 with my sensation for while sometime ago with no problems. Then I flashed other ROMs to try them out. I've been using ViperS C2 3.1.3 for sometime and saw albinoman's cyanogenmod 10.2 version. So i wanted to give it a go.
Now, my problem is that the touch screen is not working(power button and volume buttons are working though) with non-sense ROMs(cyanogenmod, virtuous inquisition) but it's working with stock, arHD, viperS etc.
I've tried "RUU_Pyramid_HTC_TUR_1.45.468.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_219996_signed" and flashing 3.32 and 3.33 (separetely) then flashing cyanogenmod 9, (stable and some nightly builds), inquisition, also tried albinoman's cm 10.2 but nothing worked for me. (Also tried the things above with "RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed".
I've rebooted after flashing cm via adb to see if that works( read somewhere that this solved someone's problem.)
Always did factory reset and wiped the cache + dalvik prior to flashing any ROMs.
I'm using CWM as recovery but tried with 4EXT (pretty sure that does not make any difference though)
I really want to go back to cm ( Although viperS is a good ROM IMO i'm looking for something lighter).
Any suggestions?
kemal409 said:
Hello,
I've used Cyanogenmod 9 with my sensation for while sometime ago with no problems. Then I flashed other ROMs to try them out. I've been using ViperS C2 3.1.3 for sometime and saw albinoman's cyanogenmod 10.2 version. So i wanted to give it a go.
Now, my problem is that the touch screen is not working(power button and volume buttons are working though) with non-sense ROMs(cyanogenmod, virtuous inquisition) but it's working with stock, arHD, viperS etc.
I've tried "RUU_Pyramid_HTC_TUR_1.45.468.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_219996_signed" and flashing 3.32 and 3.33 (separetely) then flashing cyanogenmod 9, (stable and some nightly builds), inquisition, also tried albinoman's cm 10.2 but nothing worked for me. (Also tried the things above with "RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed".
I've rebooted after flashing cm via adb to see if that works( read somewhere that this solved someone's problem.)
Always did factory reset and wiped the cache + dalvik prior to flashing any ROMs.
I'm using CWM as recovery but tried with 4EXT (pretty sure that does not make any difference though)
I really want to go back to cm ( Although viperS is a good ROM IMO i'm looking for something lighter).
Any suggestions?
Click to expand...
Click to collapse
Hello
http://forum.xda-developers.com/showthread.php?t=2437293
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
ashkan-khatar said:
Hello
http://forum.xda-developers.com/showthread.php?t=2437293
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
Click to expand...
Click to collapse
Thanks for the link but it's not working. It's either saying launch app fail(diag part) or android readfile info error(flash part) eventhough i'm super cid and have the right firmware for it (<1.18). But i'll ask there as well, so thanks.
Any other suggestions ?
i have also flashed this rom a few days ago on my htc sensation and my sensation got hang on home screen, i tried flashing 3 times and same problem, after all i flashed another rom.

Categories

Resources