Related
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.
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
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.
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
well, regarding the screen issue, use the battery all the way, til it shuts down. then rwmove the battery n press the powere button as if u were turning on ur phone. then let the phone be still over a night. then re-insert the battery n plug the phone into charge but BEWARE THAT U WILL NOT TOUCH THE SCREEN AT ALL, TIL IT'S FULLY CHARGED. i tried this solution, n it worked. maybe so did it for u :-??
n about the lags, i recommend u to install Seeder 2.00 which is recently released n can decrease the lags as much as possible. and also u could try out making 256/128MB swap with 100% swappiness using Kernel Tuner v4. alsi set these settings IN THE ORDER I'VE TYPED in venom tweaks --> misc --> minfree settings
4
8
16
32
48
64
got no more idea
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
Install TWRP (TeamWin Recovery Project) and use that to flash ViperS once more (after doing a full wipe of course). Since the only recovery that allows the installation of kernels on an S-ON device is 4ext, you will need to extract the boot.img file from the ViperS installer .zip and flash that using fastboot. Detailed instructions on how to flash a boot.img file through fastboot can be found here: http://forum.xda-developers.com/showthread.php?t=1752270
I don't really trust 4ext because 4ext gave me a lot of weird and nasty bugs. Using TWRP is worth a shot.
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Meshelton said:
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Click to expand...
Click to collapse
If you were happy with everything working WHY in the world did you upgrade to a Nightly? Nightly by definition is only for people who know what they're doing and are not afraid of the Night.
Anyway, there are like 6.0221413e+23 changes from cm 10.0.0 to 10.1 RC2. What can I say you did a dirty flash (upgrade!), and probably didn't back up.
So the first thing you should do is back up. NOW (go to CMW recovery and back up)
Download a better behaving nightly like the one JD1639 uploaded. get it from http://forum.xda-developers.com/showthread.php?t=2272261
Download the UCMC1 radio (assuming you're on at&t)
Download the gapps 20130301
Put them all on in one folder for easy access
goto the CWM recovery and get to work:
1-backup
2-cleanup: go to mounts and format data, cache, system (don't format the sdcard!!!) and don't reboot until everything is finished
3-clean dalvik cache from advanced
4-install in this order: RADIO file.zip (UCMC1)
5-CM ROM
6-gapps
7-go to Advanced Restore option, find you back up and restore the "DATA" portion ONLY
This should save you ... good luck,
Commodore 64
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Meshelton said:
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Click to expand...
Click to collapse
You know I don't think it is a hardware issue since it started after one of your updates. If you were on a ROM for while, and one morning you wokeup and the sound didn't work ... maybe. But i'm not convinced since also I remember around Feb-March there were some complains on sound not working after flashing to 4.2.2 version of the cm. Try flashing back to the stock UCMC1 ROM (absolute stock flashed with Odin not CMW) and then do a factory reset.