[Q] Losing Network Constantly - Latest CM Nightly Build - Galaxy Tab 2 Q&A, Help & Troubleshooting

Hello!
I was using the SungSonic ROM for almost a year now and I decided to change it today. So I flashed a CyanogenMod Nightly build for the P3100 This morning.
It booted up fine, and there were no issues in the beginning.
But then it started disconnecting calls randomly. Like, Someone calls, The phone rings for a second and boom! It shows a missed call.
I figured rebooting it would fix it but it made my problem only worse.
It now barely shows any Network service at all. If it is there, only for about 20s before it goes back off.
Is there any way to fix it without flashing another ROM? I like CyanogenMod and plus, its for my mother and I prefer keeping it simple.
Also, keep in mind that my Tab does not get recognised on any PC with any Cable I could find.
So, I am stuck with PhilZ Recovery for the P3100.
If the problem can be fixed via Flashing a new Mode/Baseband then please, give me a .zip for only the modem and not the whole ROM.
Thank You for Reading and I will hope you guys help me out.
Regards,
Shinichi Reshima

Always do a nandroid B/U before you flash so if you run into a problem like this you can go back. CM nightlys are not always stable, and sometimes you can't use them unless you have the base stable version of that ROM already installed. Must try and install the base version of the build, it may fix your problem. I run CM11 by Android Andi with no issues and no nightlys.
Pp.

Related

S3 rom wifi issue help please

hey im new to the forum and i rooted my s3 and have the r420 senergy rom installed but the wifi dooesnt work! uhhhhh i cant post in the development section till i have 10 posts. so any one who can help that would be great. ive been doing a lot of reading and what is the differnce between nightly and and regular roms? and i read that the wifi wont work on the nightly rom with out a kernel flash?>?>? Is this right? im going to try the v1.6 senergy any way .....my model is the i535 but yall probably already know that because you hacked my ip address and seen my phone plugged in J/K ha thanks in advance
First off, Synergy r433 is the latest version. And a new release is scheduled to drop any minute now.
A nightly is an experimental build that gets updated nightly. Whereas a stable build is less frequent but as the name suggests is stable. Nightly you must really know what you're doing and are be okay with occasional bugs, otherwise use the stable releases. (fyi SynergyROM stopped releasing nightlies)
As for your Wifi problem, reflash but the make sure you do a full factory reset, and then a super wipe within the AROMA installer. *This will wipe internal storage, make sure to have the ROM zip on external storage* Wifi is not bugged, I'm suggesting the was a flashing error.
Sent via SGS3 using Tapatalk
Thank you so much for replying. i was thinking the same about the nightly "name" but thanks for clarifying. i have tried several times. in clockworkmod recovery(or whatever the name is) i factory reset and in the installer i wipe everything. (on the internal sd) and then install cleanly. but my kernel doesnt flashed it says its not unlocked.?!?! how do i unock it? i unlocked the bootloader and once more so i knew for sure. and my phone says custom with a padlock unlocked symbol below. but same thing everytime...wifi is buggy. i like this rom and just want it to work...thanks!!!!!!!!!!!!! is there a special "better" kernel unlock method? my paitients are getting low...lol well my girl wants her phone stock ...F**CK THATT!!!!!!!!!! thanks man
Bump please someone plesase help.. I need this phone working asap
Check out this link
seems to work for some.
http://forum.xda-developers.com/showthread.php?p=40531554
Mine has always been good.
I also use an app called Opensignal
https://play.google.com/store/apps/details?id=com.staircase3.opensignal
When on the OpenSignal app select > wifi then select the > refresh then the > refresh network.
I do this every week or so. I have no issues with wifi, ever.
Some say tightening the screws
help check out rhe link below
http://gs3.wonderhowto.com/how-to/s...-gps-problems-your-samsung-galaxy-s3-0145332/
I hear it's just some phones. Anyways
good luck
Sent from my Smoking smooth
Synergy r484
Mods by gunthermic,
Theme by jbeitel
I am experiencing the same issue.
I rooted, flashed CWO, and then installed synergy. Nothing worked... then I read that you need to unlock the bootrom so I did that, rebooted and got the same... no wifi. After unlocking the bootloader I reinstalled synergy (R484) and still WiFi will not turn on.
I followed they synergy thread for flashing and This thread for bootloader unlocks.
Provider: Verizon
Phone: GS3
ROM: SynergyROM (r484)
Recovery: ClockworkOrange
Got it fixed!
So... I only used odin... no romloader apps or any of that crap...
1: Reinstalled stock ROM
2: Reinstalled CWO
3: Reinstalled Root+Bootloader
4: Reinstalled SynergyROM
5: Enjoy! Wifi works, all applications work!
Chris

[Q] In call volume muted and random network disconects

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.

bluetooth issues

I installed the slimbean 4.3 ROM a free days ago and I've been experiencing some Bluetooth issues. It will randomly close, and the only way I can get the Bluetooth to restart is to reboot the phone.
now, correct me of I'm wrong please, but Bluetooth is controlled by the modern, so I'll want to maybe flash another compatible modern?
I'm using the latest version of TWRP as my recovery.
It's a known issue with 4.3 roms. You'll just have to wait until if and when the devs figure it out.
Almighty then... thanks for the reply
eachitandi said:
I installed the slimbean 4.3 ROM a free days ago and I've been experiencing some Bluetooth issues. It will randomly close, and the only way I can get the Bluetooth to restart is to reboot the phone.
now, correct me of I'm wrong please, but Bluetooth is controlled by the modern, so I'll want to maybe flash another compatible modern?
I'm using the latest version of TWRP as my recovery.
Click to expand...
Click to collapse
I have similar problem with CM 10.2 and an earlier Rom as well ... kinda learned to live with it.

HTC One S doesn't connect to WiFi in Cyanogenmod 10.2 20131115-NIGHTLY

Hi everybody,
I decided to go back to Cyanogenmod, because i had some issues with the ROM I used before. First I flashed the CM 10.1.3 stable, everything worked fine, but I couldn't connect to any WiFi. So i tried flashing the nightly 10.2 10.2 2013111 over the Updates in the preferences. Still, i couldn't connect to any WiFi. I tried it two more times with full wipes and flashing the nightly over my Recovery, but couldn't make it work.
All these times i flashed the boot.img after flashing the nightly. I don't really know what to do anymore and thought anyone might have an idea for me?!
I didn't have any major issues until today, so i don't know what Information you might need to help me, so please tell me if I should say something more about the system or how I flashed it etc.
Thanks in Advance!
Edit: Same Problem with CM11...
Edit 2: Tried to flash the Bubba Kernel, because i read something about it...now i can't even turn the wifi on. -.-

[Q] Factory reset/wipe, new installation, still Rebooting

So...I have had a captivate and SGS3 and have never had so much trouble with a phone. This infuse is frustrating and complicated to work with. I have blue CWM which was acquired by using Entropy's guide and the other numerous helpful tips out there. I had rootbox running which would eventually start FC'ing and acting dumb. I wiped everything the other day and flashed unofficial CM 10.2, it worked perfect then random reboots to stuck at samsung then cyanogen mod then back again. Sometimes it would randomly reboot in CWM, which has never happened to me on other phone. I feel like going back to stock and back again is the only answer, but it seems like a lot of work and I already did that and it was fine.
So, all you guys that understand whats going on behind that scenes, what do you think the issue is?
UPDATE: I found a video that may link this behavior to a hardware issue caused by poor design by Samsung having too many contacts that can get gunked up and causing issues.
Might be a problem with the version of the Gapps you're using. Consider changing and even going back to older versions. I found v 12/12 signed very stable on cm10.1.
If still stuck, consider Odin back to stock in download mode and flash cm9 and cm10.2 again!

Categories

Resources