Related
Hi all,
A week ago I bought a brand new Desire S and installed latest CM 7.1 stable following the guide on cyanogemod Desire S Wiki using revolutionary 0.4pre4. Everything was smooth and nice, I flashed ROM and GAPPS and my phone is working absolutely perfectly... but there is one little problem...
I am using Desire to fetch my mails from 2 mailservers using IMAP every 30 mins. But when the phone is switching between network modes i.e. HSDPA -> EDGE or EDGE -> GSM or any other way, I am disconnected from operator network for about 10 seconds until the network mode changes and everything is fine after that, until there is another network mode switch.
This happens for me about 10 times a day, so my phone sometimes appears that It is turned off for people who want to call me. Immediately after connecting to network I get a missed call SMS from my operator.
Interesting thing is, that when I disable email fetching, disable background data transfer and disable network data, the phone works fine without "blackouts".
Can someone help me with this problem? Maybe a radio issue?
Some more info:
ROM: Cyanogenmod 7.1.0 Desire S
Recovery: Revolutionary CWM v4.0.1.4
HBOOT: 6.98.1002
Kernel: 2.6.35.14-cyanogenmod+ [email protected] #1
Radio: 20.28I.30.085AU_3805.06.02.03_M
There is a newer radio-file online.
Maybe it's solving your problem.
I'm using MIUI and never had such problems, but i'm interested in flashing CM, so please report if the problem is gone by flashing newer radio!
Which radio version are you using?
Today I am testing 2G only switch so I am on EDGE data only.
Flashing radios is safe......, but a bad radio flash will instantly brick your phone.
You are using 1.47.401.4 radio, try updating to the 2.10.401.5 one.
Thanks for reply.
Shoud I flash something else with the radio?
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Another I have is ftom OTA update zip file OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210fmxlt12djw1sr7y5.zip where is one radio.img in formware.zip file too - version unknown
So Which one to flash?
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?
MyroLM said:
Shoud I flash something else with the radio?
Click to expand...
Click to collapse
no need
MyroLM said:
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Click to expand...
Click to collapse
this file is what ur looking for! check md5-checksum before flashing!
MyroLM said:
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?
Click to expand...
Click to collapse
Both will work, i'm using method by using bootloader normaly
Strangely I had the same issues as you on Endymion.
Then I updated radio to the latest.
It worked well.
Then I went to CM7. It was fine for a while, but now I'm losing signal with no 3G bars and its not switching automatically to 2G like it should when It has no 3G signal!
EDIT:
After really reading your post, I realise my issue is no way like yours! Yours seems really bad. Update your radio.
-------------------------------
Sent from my HTC Desire S
So, here we go with the results
I flashed 20.4801.30.0822U_3822.10.08.04, md5sum checked OK, update sucess, but phone with no signal...
I flashed 20.48.30.0822U_3822.09.08.20, md5sum checked OK, update sucess, but phone with no signal again...
I flashed 20.28I.30.085AU_3805.06.02.03 back, md5sum checked OK, update sucess, but phone with no signal again...
... what now ... ?
After each flash wiped cache and Dalvik...
in your telephone-info there is shown the new radio after every flash?
do you have removed the batterycover, because there is integrated the antenna of your device!
mouzzza said:
in your telephone-info there is shown the new radio after every flash?
Click to expand...
Click to collapse
Yes, correct number every time.
mouzzza said:
do you have removed the batterycover, because there is integrated the antenna of your device!
Click to expand...
Click to collapse
No, the cover is at its place where it should be. Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now.
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??
MyroLM said:
Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now
Click to expand...
Click to collapse
in your area 3g is actually available?
may it helps to go outside, to find your net for the first time!
did you set an accesspoint for 3g?
may you have to set automatic settings, rather than 3g/2g-only?!
MyroLM said:
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??
Click to expand...
Click to collapse
using same hboot as you, never had problems on flashing radio-files!
yes, in my area there is 3g, when I turn off 2g only switch there is a problem described in my first post, so i am on 2g for now just to keep phone connected to network.
main problem is when i am driving and the phone is switching network modes.
so I give 20.4801.30.0822U_3822.10.08.04 today another chance, try to flash if again.
but i am woried about stucking on HTC logo after flash :-( and brick it.
MyroLM said:
but i am woried about stucking on HTC logo after flash :-( and brick it.
Click to expand...
Click to collapse
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days
I have the same or a very similar problem. I have the stock rom.
I already had 3 different desire s motherboard's and 2 different display's.
The first Desire S i had, with android 2.3.3, had a excellent signal. Due some problems i had, the phone bricked and had to go to HTC to repair.
HTC replaced the motherboard and update the version of the android to 2.3.5 and ever since the signal caption, the signal switch was working very bad.
The phone went to a second repair because of this, new phone, and again with android 2.3.5. The problems persisted.
I also tested with different SIM cards, from different mobile operators.
So, my conclusion is either android 2.3.5 or this new versions of Desire S have problems with signal caption and signal switch.
So as you, i need some help with this issue!
mouzzza said:
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days
Click to expand...
Click to collapse
But when I reboot to recovery it will flash the radio again I think.
i hate stock roms, and dont like MIUI design That is why I am using Cyanogen
Anyway if I use 2G only switch, the phone is stable as rock both calls and data transfer.
EDIT: OK, flashed 20.4801.30.0822U_3822.10.08.04 sucessfully, signal OK, I will see what happens whet metwork mode switches
@Green Hawk:
give us more information about your device please, which radio you're using? Did they flash actual radion also?
@MyroLM:
report if the problem is still there or it's gone with flashing the rom
I am still testing new radio, but looks good Give me some days let you know...
Hi All,
I have a similar problem with the latest CM7.1 nightly builds (Reaper, jorgen2009). I never saw this with older CM7.1 versions, e.g. Nexx version, ICS, MIUI oder Endymion.
I have WLAN on and leave my house. Phone switches to 2G/3G..., so far so good. When I return home, The WLan sign in the status bar appears again, everything seems to be fine, but I have no connection. I get no data via WLan until I swicth WLan off and on again.
Radio is the latest from 2.10.401.5.
Best Regards
Wrapp
Had similar problems, upgrading to the latest radio helped. I got stuck on the HTC screen and I went through flashing RUU's and unlocking bootloaders back and forth... when the only thing that needs to be done is to wipe the cache.
Learned a lot about bootloaders though. But my warranty got void because i did the htcdev unlock... (Sorry for OT)
Hello everybody,
I rooted and upgraded my T-mobile(US) SGs4G from Froyo to ICS, currently:
model sgh-t959v
firmware 2.3.6
baseband ver t959vuvkj6
kernel ver 2.6.35.7-t959vuvkj6-cl694130
build # gingerbread.vuvkj6
since this upgrade i have 2 bugs:
1. usb(mass storage mode) is not working in my car (read error), worked before OK. it's still working when i connect phone to computer. We got another SGs4g in the family (not rooted, just upgraded to GB), it's stop working in USB mass storage in the car too. Any ideas? could i replace usb driver in ICS or do i need to go back to Froyo?
2. I worked in the building with poor reception of GSM signal, so if phone could not connect to the cell, then even if i go outside later it's still "searching" and could not find signal, so i need to turn phone off/on in order to get signal.
Could it be fixed? again it was OK with Froyo: 5-10 sec and reception re-established.
Thanks in advance.
You don't have ICS. You have Gingerbread. Try a factory reset for your problems.
I did
Thanks, my bad, sure it's not ICS, its GB. And i did HW reset in the begining, do you think it's the number of resets that counts? BTW i did not back up my Froyo, do you know where i can get one?
When did you do the factory reset in relation to your problems? How did you upgrade?
Depending on your answers my recommendation is follow the guide in the second link of my signature. GB is worth having.
I can find you a link for Froyo but it is not as simple to downgrade to Froyo as you might think. You will need to make sure to flash Froyo bootloaders also.
first i did root still with froyo
then updated to GB with keos
did reset, and re-installed all applications.
I did figure out how to "trick" lost connection due to no signal:
turn on flight mode and turn in off. so definitely it's a bug.
still no luck with USB
I know that downgrade to froyo is not easy, and i like GB, this is why i'm asking if there is a way to patch usb driver only
regards
I just ordered a recertified Verizon 3G Xoom, and I didn't think about the implications of it being a Verizon device. This is NOT upgraded to 4G LTE -- will the "Stingray" builds of the various ROMS still work? Is there any way to apply WIFI-only ROMS (including stock) if I don't care about the 3G working? Given the age of the device I really want to get Jelly Bean on it.
I will need to cancel this order ASAP if the answers to these questions turn out to be "no"...
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
trunzoc said:
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
Click to expand...
Click to collapse
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
magnafides said:
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
Click to expand...
Click to collapse
Thanks. I'm placing my order as soon as Wife says OK. If you don't mind, and if you remember, please send me a PM of how it goes with the flashing once to get yours.
Would love to coordinate what we do since there doesn;t seem like a whole lot of certainty exists about what we are trying to do.
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
magnafides said:
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
Click to expand...
Click to collapse
Any luck? I also have a Xoom 3G MZ600 on the way and could careless about 3G...
hasnt eos got jellybean roms for all versions of the xoom? 3g should work imo
Sent from my Xoom using XDA Premium App
I'm in the same boat and curious to see if anybody has any words of wisdom. I love my refurbed Xoom 3G but am eager to get JB on it. Any help is greatly appreciated.
FWIW everything I have heard/read seems to indicate that it is possible to flash WiFi only ROMs on the 3G Xoom, and apparently everything will work fine except for the 3G (naturally). I haven't taken the plunge yet myself, still running stock ICS.
Is there any word on whether the Verizon 3G Xoom will get Jelly Bean?
It can be done....
I purchased a used 3g Xoom around Apr 2012. After initially unlocking / rooting and installing a ROM (EOS) on my 3g Xoom, the 3G radio wasn't working so I started fresh. I locked the device and SBF'd the original Xoom firmware, then used the official over the air (OTA) upgrades to get back to stock ICS. I thought this might fix the 3g issue; it did nothing.
EOS Roms overclock the GPU by default, which caused problems with my (and my wife's Wifi version) Xoom. My only requirements for a ROM are stability, no clutter from dumb carrier installed applications, compatibility, and of course root access. I found a pre-rooted stock Jellybean rom, but it was for the Wifi Xoom. It worked great on my wife's though; and heard rumors that it could work with mine.
*SO*...I took a leap of faith and installed it. It works great. No 3g radio of course, but I gave up on trying to get that to work anyway...so if you don't care about losing your 3g , this will probably work for you. I don't think my 3g will ever work, but I suspect this won't ruin yours if it is currently working. Don't hold me to that; this is a risk.
Random notes and refresher info:
-you will need an SD card. I'm pretty sure the following instructions will only work if you use one.
-If at any point you get the android guy with an orange exclamation point during boot...it is probably ok, just let it sit there for a couple minutes. it should continue to boot into whatever ROM you are currently on. Make sure you enable usb debugging in settings after boot.
-to access RSD, Recovery, or Fastboot mode, press and hold your power button to start the Xoom booting. When you see the Motorola logo, wait a second then press the volume down button. Then you can use volume down again to cycle through your options, and use volume up to choose one.
-the exact differences between RSD / Fastboot and Recovery modes are beyond the scope of this post (and me) so just know that your Xoom can be modified using software on your PC via USB with RSD and Fastboot modes, and stock recovery can be replaced with modified versions to add more functionality. Recovery is used to do all sorts of things...flash Roms, mount drives, format, cleanup caches, etc.
***
General instructions. Just guidelines; you will probably need some previous experience with computers / rooting etc.
(If you are already unlocked, rooted, and have a replacement recovery, skip to the last step.)
1.) Follow this guide to prep your Xoom: (unlocking, rooting, and install CWM recovery)
http://www.xoomforums.com/forum/motorola-xoom-development/15179-how-rookie-rooting-flashing-unrooting-under-one-roof.html
Note: you may have heard of Lord AOI tool; it is supposedly designed to simply the above process. I found it didn't work well and was more difficult to use than good ol' adb commands. I recommend skipping it.
2.) OPTIONAL: Next, I recommend using the latest Rogue recovery. Just use standard CWM recovery to flash it. It is nice because it allows you to use the touchscreen to manipulate instead of having to use the hardware buttons (volume buttons are kind of a pain). See here: http://forum.xda-developers.com/showthread.php?t=1235170
3.) Finally, flash the pre-rooted stock Jellybean ROM. See here: http://forum.xda-developers.com/showthread.php?t=1796335
(here's the direct ROM link for those not needing instructions or extra info: http://www.mediafire.com/?7w5w65l66hgggo8 )
Good luck and let us know your results...
I don't get a battery drain with 2.3 (Honeycomb 3.2) EOS,Stingray, but if I flash 3.0 Stingray on my Xoom I will get horrible battery drain. Only by flashing the wifi only version of JB will I not get a wakelock, caused by Android OS. I have tried disabling mobile data, since I don't use it and just use wifi to begin with, but it does nothing to improve it.
i'm getting the same exact issues
Have you updated your Radios? Wade thru the Team-EOS JB Nightly thread to see how that's done; it's in there ... somewhere.
kcrudup said:
Have you updated your Radios? Wade thru the Team-EOS JB Nightly thread to see how that's done; it's in there ... somewhere.
Click to expand...
Click to collapse
I tried every combination of Stingray ROM and radios I could find, all resulted in this drain. I was updating over in this thread my battery results:
http://forum.xda-developers.com/showthread.php?t=1485853
Long story short, Wingray ROM is necessary if you want JB level and normal battery life.
And you used the latest Rogue Recovery(link in my sig) to flash the radio (which there should only be 1 flashable radio for the LTE so far)? If you are trying to use any other recovery it will NOT work.
For me it was a combo of things. I used rogue recovery to flash the updated radios on the new cyanmod 10 rom and then checked to see what app might be causing the battery drain or not letting the tablet enter deep sleep. Turns out it was setcpu that did not allow the tablet to go into deep sleep. I uninstalled it and now my tablet sleeps like normal,,,will update when I know more about the battery savings i receive. Hope this help!
fudsak said:
I tried every combination of Stingray ROM and radios I could find, all resulted in this drain. I was updating over in this thread my battery results:
http://forum.xda-developers.com/showthread.php?t=1485853
Long story short, Wingray ROM is necessary if you want JB level and normal battery life.
Click to expand...
Click to collapse
Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes
I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app
You need to flash to stock and back.
Sent from my SGH-I777 using xda premium
How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium
KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?
rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.
Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.