Can't hear calls - LG Nitro HD

I first noticed this problem when I was on a CM9 nightly a few weeks ago, but the problem resolved itself after I installed RC1. When I installed RC2 the problem resurfaced & I can't seem to find a work-around. I've tried enabling & disabling the bluetooth radio, turning airplane mode on & off, wiping both cache partitions & even wiping all data yet the problem still persists. If it makes any difference I applied the leaked ICS & unbricked later, so I should be on either the latest AT&T baseband or the original SK one. I'm afraid of adb flashing the AT&T ones from the stock images because I'm afraid it'll enable secure boot again. Oh, & also for those who haven't been following outside the US, AT&T found a way to enable secure boot.

okay so it appears they re-released RC2 w/ some bugfixes, one of which covers this problem...

Related

Data connections issue

Hi all,
I own a Desire GSM version and been running a pre-rooted stock ROM for quite a while and have been very happy with it. I have been running this with an ext3 partition and ran app2sd+ script to make use of it. All good.
My sense of curiosity got stronger and always wanted to try a custom ROM so I tried Cyanogenmod 7 RC1 on Monday.
I have been running the latest Radio (32.49.00.32U_5.11.05.27) so didn’t have to update that for CM7.
I formatted the DATA as well as the CACHE before flashing the CM7 ROM, then applied GAPPS to the ROM then restarted the phone.
All went OK and I loved this new ROM, except that I have been experiencing very strange connection issues whether I am on WiFi or 3G (Vodafone AU). The phone will establish connection; however sometimes will not be able to get data out of a request as simple as getting emails, opening a webpage through the stock browser etc …
The workaround to that was to tun off wifi and turn it back on, same for 3G …
I re-flashed numerous times the ROM (formatting the CACHE/DATA each times) but was still experiencing these issues, when sometimes I couldn’t even set my Google account at the first start of the phone…
After a couple of days of scratching my head I did find a potential solution that was suggesting updating the /system/lib/libhtc_ril.so file with the one provided in the nightly build. This had no effect what so ever to the situation.
I then decided to go back to FroYo () so re-flashed the pre-rooted ROM, but then I experienced the exact same issue!! I then re-flashed the Radio ROM thinking this may have been affected by all these changes but no changes at all …
I am a bit at a loss here and don’t know how to fix that really …
Is there any setting that resides on the phone relating to Radio ROM even if I format both Data and Cache each time I flash the ROM??
Thanks for your help guys.
Any ideas on this issue at all ??

Help! Phone crashes after booting OS!

Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.

[Q] WiFi seems broken (phone crashes)

I have massive problems using WiFi.
If I activate it, the phone spontanously "crashes", means it reacts extremely slow and is totally unusable till restarted.
It's always when WiFi is on, just the time till it starts differs. I've tried some different ROMs (MIUI with LordMods kernel or stock kernel with vanilla ROM-settings and no apps, CM7.1 stable with stock kernel) and also different WiFis and settings and can say it's independent from an established connection, so it also occurs when there is nothing in sight to connect to.
I can't remember since when I got this problem as I only recently activated WiFi again for usage. Before I never had such problems. I accidentally flashed a zip file as a radio some time ago o) and then flashed the right radio again after I got the battery out for some time. Possible the phone got damaged somehow or is there a possibility that it's a software related issue like a module that doesn't work well with more recent radios in combination with my phone?
I tried radios 12.59.60.26_26.11.04.21_M and 12.62.60.27_26.13.04.19_M, same problem.
Thanks
See if the official software works, try to install a 1.32 RUU.

[Q] Suddenly lost 3G on my Arc S (solved)

Yesterday I flashed CM 7.2.0 FXP109 on my Xperia Arc S.
3G worked perfectly.
Later I installed AdFree, and set my phone on the table. I do not remember if I rebooted it first. About an hour later when I picked up the phone again, I had no 3G signal. Still nothing today. Tried re-flashing CM7.2 FXP109, whilst first wiping data/cache/dalvik. Still nothing.
Tried to put it into airplane mode, waiting 10 seconds and turning it back off, checked all the settings (and the APN settings are set the way they should).
Also, after having wiped the phone data and cache and re-flashing, somehow USB Debugging and Unknown Sources are still turned on. Shouldn't that reset?
Either way, something is wrong and I'm at a loss. I have no idea what to do, and I just bought the phone yesterday. Before that I had an X8 with GingerDX, so it's not my first time installing a bootloader, and I haven't had these problems on my old phone.
Any help would be greatly appreciated!
EDIT:
I found a (possible) solution, at least it seemed to have worked for me.
I flashed a different kernel (and thus got a different version of CWM), formatted, wiped cache/dalvik cache and flashed back to the kernel needed for FXP109. Then I installed FXP109 CM7.2 and GAPPS again. Problem solved.
My guess is that for some reason, I had to flash to a different kernel and back to solve it.
Cheers!
-Zareph

[Q] 2G/3G & Alarm clock turns off intermittently on several ROMs

Hello all,
Since a few months I have the problem that my 2G/3G seems to loose connection every now and again.
I used to use MildWild Oxygen 4.0 which was one of the most stable ROMS I ever tried
After that I tried
- several AOKP 4.0.4 ROMS
- the latest couple of versions of Sandvolk's ICS ROM
On all of these I had several problems with 2g/3g turning off every now and again, recently also the alarm clock stopped (or changing time, which i found very bizarre).
Now I re-flashed my NAND backup of MildWild 4.0, and I have the same problem.
Any idea what that might be?
I am using the latest radio version and the data++ HBoot, if that helps.
Ok - that seem to be 2 different problems.
The problems on Mild Wild and the alarm clock seems to be linked to enabling app2SD without wiping the ext partition up front. wiping and/or disabling app2sd solved the problem.
However, the 2G/3G loss on the ICS ROMS seems to persist.
I installed the latest sandvolks recently from scratch (0.13.1) and I had exactly the same problem.
2G/3G seems functional, but no internet connection possible.
Switching flight mode on/off several times helps every now and again, but also not consistently.
I am on the latest radio version, so I don't think it's that either.
Maybe a known bug to the ROM?
Any sort of help is highly apreciated

Categories

Resources