Related
hi guys i was hoping you could help me out, the thing is that my wifi isnt working with all ics roms that i flash, when i turn on the wifi it says "turning on wifi" and stays like that, then when i press the back button and re-enter the wifi menu there nothing, no scannig, no nothing ...... although wifi works in cm7 but i prefer ICS roms better than cm7 roms. itried changin kernels and all but still nothing.
please help me out
here are some screenshots :
BlacKfenX said:
hi guys i was hoping you could help me out, the thing is that my wifi isnt working with all ics roms that i flash, when i turn on the wifi it says "turning on wifi" and stays like that, then when i press the back button and re-enter the wifi menu there nothing, no scannig, no nothing ...... although wifi works in cm7 but i prefer ICS roms better than cm7 roms. itried changin kernels and all but still nothing.
please help me out
here are some screenshots :
Click to expand...
Click to collapse
which cm9 build are you using? nightly or hephappy's?
rohitsk said:
which cm9 build are you using? nightly or hephappy's?
Click to expand...
Click to collapse
Im using hephappy's tinystream, but u know ive tested many ics roms, including AOKP; but the wifi still isn't working....
BlacKfenX said:
hi guys i was hoping you could help me out, the thing is that my wifi isnt working with all ics roms that i flash, when i turn on the wifi it says "turning on wifi" and stays like that, then when i press the back button and re-enter the wifi menu there nothing, no scannig, no nothing ...... although wifi works in cm7 but i prefer ICS roms better than cm7 roms. itried changin kernels and all but still nothing.
please help me out
here are some screenshots :
Click to expand...
Click to collapse
I have EXACTLY THE SAME PROBLEM. Help PLEASE...
BlacKfenX said:
hi guys i was hoping you could help me out, the thing is that my wifi isnt working with all ics roms that i flash, when i turn on the wifi it says "turning on wifi" and stays like that, then when i press the back button and re-enter the wifi menu there nothing, no scannig, no nothing ...... although wifi works in cm7 but i prefer ICS roms better than cm7 roms. itried changin kernels and all but still nothing.
please help me out
here are some screenshots :
Click to expand...
Click to collapse
I have the same problem. Tried various ROMs from various people (CM [arjen, hehappy], MIUI, AOKP), also various kernels... no results.
dariemp said:
I have the same problem. Tried various ROMs from various people (CM [arjen, hehappy], MIUI, AOKP), also various kernels... no results.
Click to expand...
Click to collapse
Although the problem still exists, but now, at least I know that there are some other persons on the planet who suffer just like me! It also indicates that it is a systematic problem and there may be a solution. We have to keep trying.
I dont have any problems on wifi. I dont use wifi much since I rely on data connection. But phone/ROM scans and displays network without any problems.
Currently Im using AOKP milestone build #6 and its stable apart from some minor bugs.
See if you can use wifi tethering....
dariemp said:
I have the same problem. Tried various ROMs from various people (CM [arjen, hehappy], MIUI, AOKP), also various kernels... no results.
Click to expand...
Click to collapse
I also have exact same problem - NO WIFI on Android 4.x.x. Problem is related to SIM card and Baseband issue. If you flash ROM with no SIM card, wifi works! If you install SIM card wifi no longer works.
First discovered this when I upgraded from Froyo to LG 2.3.3 and the wireless would not work then, and I had to change network selection from Automatic, and select my service provider manually to get WiFi to work. I think the problem with 4.x.x is similar, but it gives an error trying to manually select the service provider, so wifi does not work.
I have 20G baseband (latest I think).
Does anyone else have error when selecting service provider manually?
CyanogenMod-7 nightly builds wifi works perfectly. Just fails with any 4.x.x versions.
Problem Solved!!
Eventually I found a solution for this problem at: http://forum.xda-developers.com/showpost.php?p=35592444&postcount=5856
or directly at: http://forum.xda-developers.com/showthread.php?t=1445766
I'm very happy now, hope you to be happy as well!!
CyanogenMod 9 is a free, community built distribution of Android 4.0 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This phone isn't my daily driver, so I only tested a few things, and only slightly:
Known Bugs:
BLN is wonky. This is a CM9 thing and applies pretty much to all the msm8660 devices that use the cypress-touchkey BLN driver. Unlikely to be fixed
Other things maybe? Discuss in the thread...
How to get it:
Download: http://get.cm/?device=t769 (ChangeLog)
Or download it directly through ROM Manager or CM Updater.
Google Apps:
Make sure to download and install the ICS GApps
http://goo.im/gapps/gapps-ics-20120429-signed.zip
IF YOU ARE COMING FROM ANOTHER ROM, PLEASE MAKE SURE TO DO A FACTORY/DATA RESET BEFORE USING THIS. This isn't up for debate. A reset of the dalvik cache helps too. If you do a dirty flash, please make sure to do a dalvik cache wipe. If you have searched this forum for a problem and haven't found it, please do a nandroid backup, then a full factory/data reset and check to see if you still have the problem. If it still persists AFTER the factory/data reset, then report it here.
Thank You!
CyanogenMod Team (all of you, seriously, you guys are awesome)
SGH-T989 Devs (all of you, cuz I basically stole all your configs)
ShabbyPenguin & PlayfulGod for encouraging me when times looked grim.
UberPinguin and others on #jb-dev-e4gt for helping me get all of this work into CM proper
Oreo, my dog, for licking me whenever I needed it.
Older/Unofficial Versions (don't use if you can help it).
For older/legacy/test/unofficial versions of my work, you can find them (for a while at least) here: My Funhouse. Please take care and all necessary steps to verify MD5 sums before installing any zips.
Since CM9 is not a moving target like CM10, it may be some time before we get a point release. Therefore the occassional CM9 Nightly will have to do.
I'm not creating a Q&A thread for this one. Please behave yourselves and be nice to your neighbors.
That is all
Nice work getting it official man
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
erikmm said:
Nice work getting it official man
Click to expand...
Click to collapse
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work
does cm9 have wifi calling?
Bradlees said:
does cm9 have wifi calling?
Click to expand...
Click to collapse
no it doesnt.
dr4stic said:
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work
Click to expand...
Click to collapse
Lol yea that's true I got aokp-jb and ics almost complete so again thanks for the work
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
I've been using this due to the stability over cm10. Good stuff!
Hardkeys illumination
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?
lnxzilla said:
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?
Click to expand...
Click to collapse
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.
dr4stic said:
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.
Click to expand...
Click to collapse
I see, tnx for the clarification as it was my understanding the issue only occurs when the lights are actually used for notifications hence the BLN name. Oddly enough I didn't notice this happening when I was running the unofficial build, must have been a coincidence then I suppose.
CM9 after 11/2 will contain WiFi Random MAC fix
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run
dr4stic said:
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run
Click to expand...
Click to collapse
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......
boulos said:
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......
Click to expand...
Click to collapse
This is why swiching mounts is not great. The kernel flash replaces the boot.img.
Your best bet might be to wait till the next CM9 nightly comes out and modify that one.
Nightly build
CM9 downloads seem to go to internal storage but CWM was directed to perform update from external sd (ie microsd card). Unless I'm missing something, it doesn't look like the location can be changed manually.
Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?
creeve4 said:
Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?
Click to expand...
Click to collapse
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.
Which cm9 version are you using?
Sent from my SAMSUNG-SGH-T769 using xda premium
lnxzilla said:
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.
Click to expand...
Click to collapse
I've found that CLEAN flashes eliminate this for me on all ROMS. I think multiple dirty flashes like flashing updates over previous versions will eventually mess things up expecially when changes r made to the kernel
-I'm not a Dev, I just flash alot-
-If I've helped you the Thanks button is only 2 clicks away!
@woodzx67: Currently latest official cm9 20121125
@johnb380: Started fresh with a full wipe a few times already, makes no difference in this case as the data connection issue has always been there for me with cm9 in particular. I've only used cm10 briefly, don't recall that happening but then again the SOD issue prevented it from running for too long.
I've been using the Jellybro kang of CyanogenMod (10-20121120-SKANK-d2vzw). I had NFC working as recently as the 11/3 build, but when I flashed the 11/5 build NFC broke.
I tried flashing a stock JB (deodexed and rooted) rom, enabling NFC and restoring back to my nandroid, but the NFC still wasn't fixed. I've tried the NFCfix.zip and that didn't work either.
Do I need to flash stock.vzw_root66.tar in Odin and turn on NFC? Or is there a specific stock rom I should be using?
What am I doing wrong, or what else should I try? I've done my best to search the forums and figure out a solution, so figure me if there has been clearly hashed out elsewhere.
Thanks!
[edit] Solution: flash this NFC fix http://www.mediafire.com/?y6vx27cpaasqhxs
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
ddurandSGS3 said:
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
Click to expand...
Click to collapse
Let me give it a shot. Are you suggesting any TW ICS rom or specifically a stock ICS? Can you link me to the rom you use, please?
Thanks!
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
i use a stock rooted from scottt that i have saved on my laptop to fix my NFC.
ive seen people ahve success wth the zips floating around, try that first its quickest easiest
Polymira said:
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
Click to expand...
Click to collapse
Perfect! That fixed it. Thank you very much.
try this
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
majixx11 said:
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
Click to expand...
Click to collapse
I'm having the exact same problem and seems like no one can help with this
On my S4 I9505 I can turn on S4 but then nothing happens whenever I try to scan any tag... Any ideas? I flashed different stock roms and tested 3 different batteries with visible loop antennas on them. Nothing works.
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
chrisszz said:
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
Click to expand...
Click to collapse
Hi, the reason for this is unknown.. but upgrading to Android 4.2.2 + seems to fix the issue. It was fixed in the kernel for those ROMs.. So only possible workaround is to upgrade to 4.3.1.. which is bugfree..
Edit .. : Now I recall that it was an issue with the wifi drivers in the kernel. If you can .. search for the wifi fix by Immortalyash .. He had done it in cm9.. as well as in minicm9. check it out.
Red Devil said:
Hi, the reason for this is unknown.. but upgrading to Android 4.2.2 + seems to fix the issue. It was fixed in the kernel for those ROMs.. So only possible workaround is to upgrade to 4.3.1.. which is bugfree..
Edit .. : Now I recall that it was an issue with the wifi drivers in the kernel. If you can .. search for the wifi fix by Immortalyash .. He had done it in cm9.. as well as in minicm9. check it out.
Click to expand...
Click to collapse
Thank's for the suggestion...will try one or the other this evening.
chrisszz said:
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
Click to expand...
Click to collapse
this is a common bug in cm9 & minicm9 roms..4.3 roms don't have this issue. I'm using minicm9 with aries kernel oc & no wifi toggle issue yet..you should try aries kernel too maybe it'll solve your problem.
Affangta said:
this is a common bug in cm9 & minicm9 roms..4.3 roms don't have this issue. I'm using minicm9 with aries kernel oc & no wifi toggle issue yet..you should try aries kernel too maybe it'll solve your problem.
Click to expand...
Click to collapse
And what is the difference between cm9 and minicm9?
New problems...
So i've tried a bunch of different kernels starting with pandora r3...that didn't do anything, then i installed garuda v5 that fixed the wifi problem but made another one...that being it can't recognize the sd card anymore, i can see the second partition but sd card appears removed and when i take the card out i can still see the message sd card unexpectedly removed, so most of the apps are crashing, and also when i go to Settings->Storage i get "Settings has stopped". This also happens for Settings->Apps.
Now i've reflashed pandora but i think something from garuda remains because i still get the errors from it even with pandora installed. And i know this because every time i reboot, after the cm9 logo i get "Android is upgrading. Optimizing xx from xx apps". I've only seen this with garuda.
I wanted to try aries kernel now but cannot download it because i cannot see the card and i'm also at work so i'm not able to connect the phone to the pc and copy the kernel from recovery mode because of the restrictions on the computer....It's really messing my day...Should I do a clean install when I go home? What is the best cm version for this phone? I've also had 10.1 but this had problems with the alarm...like it only rang after i woke up and unlocked the phone...never at the hour selected...and also it drained the battery faster...Waiting for a good suggestion for this letter ...Thanks in advance!
chrisszz said:
So i've tried a bunch of different kernels starting with pandora r3...that didn't do anything, then i installed garuda v5 that fixed the wifi problem but made another one...that being it can't recognize the sd card anymore, i can see the second partition but sd card appears removed and when i take the card out i can still see the message sd card unexpectedly removed, so most of the apps are crashing, and also when i go to Settings->Storage i get "Settings has stopped". This also happens for Settings->Apps.
Now i've reflashed pandora but i think something from garuda remains because i still get the errors from it even with pandora installed. And i know this because every time i reboot, after the cm9 logo i get "Android is upgrading. Optimizing xx from xx apps". I've only seen this with garuda.
I wanted to try aries kernel now but cannot download it because i cannot see the card and i'm also at work so i'm not able to connect the phone to the pc and copy the kernel from recovery mode because of the restrictions on the computer....It's really messing my day...Should I do a clean install when I go home? What is the best cm version for this phone? I've also had 10.1 but this had problems with the alarm...like it only rang after i woke up and unlocked the phone...never at the hour selected...and also it drained the battery faster...Waiting for a good suggestion for this letter ...Thanks in advance!
Click to expand...
Click to collapse
For the sd card issue you can try multimount from the playstore
Also check the 4.3 roms as they are very stable and don't have any issues.
And before flashing any rom just do a factory reset, thats all...
Hit THANKS if I helped
SSKSSK said:
For the sd card issue you can try multimount from the playstore
Also check the 4.3 roms as they are very stable and don't have any issues.
And before flashing any rom just do a factory reset, thats all...
Hit THANKS if I helped
Click to expand...
Click to collapse
Tried the multimount app...didn't work...will check 4.3 roms later today.
Thanks for the response
android.process.media has stopped
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
chrisszz said:
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
Click to expand...
Click to collapse
Weekly 7 has some sort of issues.. read the thread before you flash anything. You can try weekly 6.. it doesnt have any known issues.
chrisszz said:
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
Click to expand...
Click to collapse
You can try Carbon 4.3 rom or the TriumphHD 4.1 rom as they r stable
Try Carbon 4.3
chrisszz said:
And what is the difference between cm9 and minicm9?
Click to expand...
Click to collapse
not much..cm9 is build for hdpi devices & minicm9 is for mdpi devices so it flies better on our pico.
I've installed cm10.2 weekly 6 and it works fine...a bit laggy sometimes but it's stable...now i'm having trouble increasing internal memory. I tried mounts2sd but it messed things up...
chrisszz said:
I've installed cm10.2 weekly 6 and it works fine...a bit laggy sometimes but it's stable...now i'm having trouble increasing internal memory. I tried mounts2sd but it messed things up...
Click to expand...
Click to collapse
You can try int2ext+.. it works fine.. just backup your apps using titanium backup or helium or similar and reflash the ROM with int2ext
Ok so finally I've managed to make everything work. First I tried to increase the memory using int2ext+ but it got stuck in cm logo loop, or I didn't wait enough I don't now, but then i reflashed using int4ext+ and it worked like a charm . So thanks everyone for the feedback and have a nice day...Cheers!
my experiences for htc explorer roms
more than 40 different rom and kernel for a long time I did try.
1-original stock rom-telephone conversations is extremely slow and sometimes do not sound or sound from the other side
2- CM7 - do not even need to comment ... very very impractical .
3- cm9 do not have any problems except for the opening of wifi for everyday use . There are original rum they use a much more streamlined and spacious
Everything was excellent but the 4- cm -10 is based on telephone interviews with purpose robot voice problem. solved the problem with different kernel installations
5- cm - 1.10 robotic voice problem ..
6 - cm 10.2 ( 4.3.1) and freezes a lot of memory problems programmer jobs Even though there is a friend that is useful for cm9 combinations up there and he's coming rom with different kernels .
Result : the value to be used as a result I have seen many times rom Trials following : Vanir AOSP (thanks 7alvi ) + sakindia aries 767 mhz oc kernel 3.5 stable and smooth with use .. If I find a single fault for making a phone call notification panel wide-screen mode by turning itself down opening.its got a lead on the issue .:good:
fromturkey said:
more than 40 different rom and kernel for a long time I did try.
1-original stock rom-telephone conversations is extremely slow and sometimes do not sound or sound from the other side
2- CM7 - do not even need to comment ... very very impractical .
3- cm9 do not have any problems except for the opening of wifi for everyday use . There are original rum they use a much more streamlined and spacious
Everything was excellent but the 4- cm -10 is based on telephone interviews with purpose robot voice problem. solved the problem with different kernel installations
5- cm - 1.10 robotic voice problem ..
6 - cm 10.2 ( 4.3.1) and freezes a lot of memory problems programmer jobs Even though there is a friend that is useful for cm9 combinations up there and he's coming rom with different kernels .
Result : the value to be used as a result I have seen many times rom Trials following : Vanir AOSP (thanks 7alvi ) + sakindia aries 767 mhz oc kernel 3.5 stable and smooth with use .. If I find a single fault for making a phone call notification panel wide-screen mode by turning itself down opening.its got a lead on the issue .:good:
Click to expand...
Click to collapse
I don't know why you faced so much issues because for me there are no such problems..only cm9 wifi toggle issue was there before using aries kernel & ofcourse cm10.1 bluetooth toggle issue. I never faced robotic call or freezing problem on any rom.
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
I'm 717
Sent from my SCH-I535 using Tapatalk
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.
Anyone try aosp to see if fixed yet?
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.