After flashing CM7 N100 & N101, I had to re-flash my gapps & GPS fix zips. I hadn't had to do that since first flashing those & generally flashing a Nightly every night.
On N101, I've had 3g dropping off on me & a notification telling me I've lost connection to my home... then it drops off but I has a header of International Roam.
I'm about to go back to N99 but I was wondering if anybody else has noticed these things.
Have you?
nope. and 102 works fine too
There its a nightly thread specifically for discussing nightlys already
http://forum.xda-developers.com/showthread.php?t=729802
Related
Had great success with CyanogenMod 7 RC1 and the #12 nightly (from 3/2/2011) on my G2.
Just wrapped up a quick flash to RC-2, but quickly started seeing weirdness, namely a continuous reboot to the CyanogenMod 7 bootup animation (blue skating android). Has anyone else ran into this on RC2 on the G2?
For now, restoring my nandroid backup from the #12 nightly which seemed pretty solid.
Also, fwiw, any US T-mobile users running into GPS issues (not locking) on the newest radio (26.06.02.27), I can confirm downgrading the radio back to 26.03.02.26 fixed this problem in my scenario.
Yes, same behavior. No idea about the radio and GPS. Just got my G2 today
I had the same issue when I went from RC1 to RC2, it kept rebooting so I just turned it off and it rebooted normal and has been working good ever since, maybe I just got lucky, idk.
_________________________________
Sent from my CM7 T-Mobile G2 using XDA app
If you're having bootloops try to do a reflash of the zip and reboot.
Many GPS issues have been fixed in the latest couple nightlies. For many people flashing the new radio doesn't work.
I've had GPS issues for a while on the stock T-mo radio, and it works fine now with the latest nightlies.
For detailed posts and info on the GPS, go read the nightly forum, there's 100000 posts on it.
moneybagsxp said:
Also, fwiw, any US T-mobile users running into GPS issues (not locking) on the newest radio (26.06.02.27), I can confirm downgrading the radio back to 26.03.02.26 fixed this problem in my scenario.
Click to expand...
Click to collapse
Also can go other way. Fixed my GPS No Lock problem in CM7-RC1 going from 26.03.02.26 to 26.06.02.27
Perhaps it doesn't matter what radio you use, it just needs the radio to be flashed??? (YMMV, I'm still newb-ish)
So I updated my DInc to CM7 and updated the kernel to the latest Incredikernal version.
Two days ago, I noticed that I had no 3G connection at all, but could still make phone calls/send SMS. I updated to the latest build (33 I think) and the issue still persists. What next?
Try goin to rc4 see ifit fixes wait to flash kernel cw just may hav not wiped properly
sent from dinc
I heard there were problems with RC4 and Build 33 so im still on build 32.
Just a quick update - I did a *228 after posting this question - thought it might have something to do with Verizon as they are updating my area to the 4G LTE and my wife's phone (DInc - unrooted) was having similar issues. Upon doing the *228 and waiting about 15 minutes, everything was back to working normally. Just a heads up if others are having similar issues.
Okay so I have CyanogenMod and I am still running nightly 56. About a month or two ago, my screen became unresponsive in certain areas. I was told that it was a hardware issue and required replacement, but I am really unsure about how to unroot, so I haven't returned it to stock. Today, as I took my phone off Airplane Mode, the dbm signal meter read -1 and I had no service. No matter what I do (battery pull, wipe cache, on/off airplane mode) I don't get signal. Has anybody else experienced this before? Or do I finally need to face my fear of unrooting my phone and sending it in?
Are you still rooted and running cm7? did you play around with the network options in settings? This sometimes causes no signal issues if not done correctly. I would try flashing 56 again after you wipe cache and dalvik, or flash the newest 100 nightly or cm7 stable build, both which have been reported to work now.
I have always had issues with cm7 on my inc2. From the earlier days to current versions. It is like my phone doesn't like aosp tons. I always have inconsistent signal and my highest battery drainer is cell.
Sent from my Incredible Sensation using xda premium
MJL99 said:
Are you still rooted and running cm7? did you play around with the network options in settings? This sometimes causes no signal issues if not done correctly. I would try flashing 56 again after you wipe cache and dalvik, or flash the newest 100 nightly or cm7 stable build, both which have been reported to work now.
Click to expand...
Click to collapse
So you think this is a software issue, not a hardware issue with the radio? And is it okay to jump from nightly 56 to nightly 100 without a full wipe? Thank you so much for your help.
yes it is ok to jump without a full wipe. just wipe cache and dalvik. and the only way to tell if its a software issue is to try different roms. try a newer nightly and if that gives you problems try a sense based rom and if it still doesnt work then it might be a hardware issue.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Okay. I overcame my fear of unrooting and I'm stock now. The signal does work, so you were right, it was a software problem. My screen is still unresponsive though. I switched to stock, but my phone is now 2.2.1. Will that be a problem for returning it for a replacement?
I've searched, so please forgive me if there's something similar. I've found nothing that solves my issue. I have freshly installed cm9 a couple days ago, and then shortly after upgraded to 10. That is where my woes began. Friends and fam started telling me that my phone would ring onced and straight to vm. I get texts in huge batches, a lot of repeats, and very unreliably. I've installed a few other different roms and kernels to no avail. And yes I've wiped everything, every time. My 3g/4g/wifi are fine.. just texts and calls messed up. What's happeninggg =[[[[. Is my radio corrupted or something? How can I fix this?
First: This is a support question and should have been posted in the Q/A forum.
Second: You should probably not install the RC of CM9, since CM9 is now stable and has an official release. http://get.cm/?device=epicmtd&type=stable
Third: Before flashing CM, use Odin to go back to stock and test out SMS, MMS and calls. If all works well, then you can Odin flash CWM, pull the battery, 3-finger boot to CWM and then flash CM9 stable.
If testing SMS, MMS and calls do not work properly on stock, then you need to go to a Sprint store and get them to fix it. Just leave it on the stock rom to bring it in.
Moved
Sent from my SPH-L710 using xda premium
I tried to post this in the development section, under the rom I flashed directly, but since I don't have 10 posts I couldn't. Anyway, I am having issues sinced I flashed this rom last night. I flashed the hellfire rom, and also the liquid smooth rom. In both roms, when I am using my phone it states that is has a 3g connection in the notification bar, but immediately once I start using the data (speed test, chrome, etc.) it jumps to H+. As soon as I close the application I am using, it reverts back to the 3g connection. Is that something that was done on these newer roms, possibly to conserve battery? I have never flashed any other roms with this phone and until recently was sitting on stock rooted UVLH2.
Also, another question I had is when I flashed both of these roms through CWM 6.0, everything installed correctly but the baseband stayed on UVLH2 and didn't update to the LI7 or LI8 that it was supposed to, and I had to directly install LI7. Is that normal? I came from the Vibrant and G2X and whenever I flashed a rom, it normally also changed the baseband itself. I have tried searching before starting this thread but haven't found an answer to either of these questions. Thanks for any help guys.