Related
OK, we all know the problem with radio 1.65.17.10... DO NOT FLASH IT, IF YOU WANT TO CHANGE RADIOS!!!
I actually found a major benefit (for me) to use it.
I had been experiencing problems with ATT here in California, where my data connection would just stop working, despite showing it being connected. The fix would be easy, just disconnect the data session and reconnect and it would be fine again for awhile (anywhere from an hour to a day). The problem for me is that I use direct-push email for work, when the data connection would fail, there was no warning of a problem. Emails would go missing until I checked Activesync, noticed the failure, and reinitiated the data connection. Very annoying, and easy to miss important messages...
So after troubleshooting with ATT, to no avail, and numberous trys with various radios and ROMs here on XDA, I decided to try it.
My issue has been gone for 4 days now. It is possible that Dutty's new Hybrid v2 helped, but all of his previous ROMs had the problem. So, it was either the new radio, or the new ROM.
DO NOT INSTALL THIS RADIO, YOU CAN'T REMOVE IT CURRENTLY!!!! (but it worked well for me)
For all the bad things about this ROM, read here:
http://forum.xda-developers.com/showthread.php?t=387395
motocrossmann said:
OK, we all know the problem with radio 1.65.17.10... DO NOT FLASH IT, IF YOU WANT TO CHANGE RADIOS!!!
I actually found a major benefit (for me) to use it.
I had been experiencing problems with ATT here in California, where my data connection would just stop working, despite showing it being connected. The fix would be easy, just disconnect the data session and reconnect and it would be fine again for awhile (anywhere from an hour to a day). The problem for me is that I use direct-push email for work, when the data connection would fail, there was no warning of a problem. Emails would go missing until I checked Activesync, noticed the failure, and reinitiated the data connection. Very annoying, and easy to miss important messages...
So after troubleshooting with ATT, to no avail, and numberous trys with various radios and ROMs here on XDA, I decided to try it.
My issue has been gone for 4 days now. It is possible that Dutty's new Hybrid v2 helped, but all of his previous ROMs had the problem. So, it was either the new radio, or the new ROM.
DO NOT INSTALL THIS RADIO, YOU CAN'T REMOVE IT CURRENTLY!!!! (but it worked well for me)
For all the bad things about this ROM, read here:
http://forum.xda-developers.com/showthread.php?t=387395
Click to expand...
Click to collapse
Great....but why start a new thread on an existing topic about the radio.
cuz he wanted to! so na-na-na-na
motocrossmann said:
OK, we all know the problem with radio 1.65.17.10... DO NOT FLASH IT, IF YOU WANT TO CHANGE RADIOS!!!
Click to expand...
Click to collapse
Just be sure that you're kaiser is "security unlockt" before installing 1.65.17.10, then there is no problem to change to another radio.
monkey0 said:
Just be sure that you're kaiser is "security unlockt" before installing 1.65.17.10, then there is no problem to change to another radio.
Click to expand...
Click to collapse
How can check this ?
Faster4 said:
How can check this ?
Click to expand...
Click to collapse
Hold in the camera button then hit reset. On the top of the bootloader screen should say "security unlocked"
Com'on guys. This is a PUBLIC forum. As long as he follow the rules, and I think he is fine. lately I have see so many "police" wants ppl to follow he or her rules.
I understand how difficult to read the same post again and again.
His topic might not interest you, but here I am. I like to know what are the benefits from previous user.
Please do not judge people by your standard.
BTW, what I do not like to see is: "good job", "you the best", "Dutty, you did it again"...etc all the good words. That is what I call a waste of my time. But you see hundreds of posts like that. This is just an example. What I like to see is the "pro" and "con", so I can narrow down the actual benfit of flash to a new ROM. I have never see anyone here saying anthing about this. Everytime when a new ROM update, I probably have to read more than 50% on good words. Tell me about that!!
rac2371 said:
Hold in the camera button then hit reset. On the top of the bootloader screen should say "security unlocked"
Click to expand...
Click to collapse
I'm doing everything you say but it shows me the three color screen without say "security unlocked" . What else can I do to unlock it?
Thank you
Being a chef, putting out a special rom for the public takes a great deal of time. They need the certain feedback from users on the rom. The first few posts are cluttered with the good jobs and great rom, but this is the thing to thank the chefs for their time and efforts.
As for this thread, I know its dug up in there, but people have stated the benefits in the 1.65.17.10 radio thread. The Kaiser ROM development forum is really cluttered with a lot of threads so having these redundent threads just makes the development forum more cluttered.
Penske MB said:
Com'on guys. This is a PUBLIC forum. As long as he follow the rules, and I think he is fine. lately I have see so many "police" wants ppl to follow he or her rules.
I understand how difficult to read the same post again and again.
His topic might not interest you, but here I am. I like to know what are the benefits from previous user.
Please do not judge people by your standard.
BTW, what I do not like to see is: "good job", "you the best", "Dutty, you did it again"...etc all the good words. That is what I call a waste of my time. But you see hundreds of posts like that. This is just an example. What I like to see is the "pro" and "con", so I can narrow down the actual benfit of flash to a new ROM. I have never see anyone here saying anthing about this. Everytime when a new ROM update, I probably have to read more than 50% on good words. Tell me about that!!
Click to expand...
Click to collapse
Faster4 said:
I'm doing everything you say but it shows me the three color screen without say "security unlocked" . What else can I do to unlock it?
Thank you
Click to expand...
Click to collapse
You could follow the info/link in the WiKi
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
That would take you here:
http://forum.xda-developers.com/showthread.php?t=361236
motocrossmann said:
OK, we all know the problem with radio 1.65.17.10... DO NOT FLASH IT, IF YOU WANT TO CHANGE RADIOS!!!
I actually found a major benefit (for me) to use it.
I had been experiencing problems with ATT here in California, where my data connection would just stop working, despite showing it being connected. The fix would be easy, just disconnect the data session and reconnect and it would be fine again for awhile (anywhere from an hour to a day). The problem for me is that I use direct-push email for work, when the data connection would fail, there was no warning of a problem. Emails would go missing until I checked Activesync, noticed the failure, and reinitiated the data connection. Very annoying, and easy to miss important messages...
So after troubleshooting with ATT, to no avail, and numberous trys with various radios and ROMs here on XDA, I decided to try it.
My issue has been gone for 4 days now. It is possible that Dutty's new Hybrid v2 helped, but all of his previous ROMs had the problem. So, it was either the new radio, or the new ROM.
DO NOT INSTALL THIS RADIO, YOU CAN'T REMOVE IT CURRENTLY!!!! (but it worked well for me)
For all the bad things about this ROM, read here:
http://forum.xda-developers.com/showthread.php?t=387395
Click to expand...
Click to collapse
Motorcross,
Tq for yourfeedback. I face the same problem with what u had but mine is more serious!!! My EDGE connection (I am in Malaysia using DiGi) lasts only minutes. 50% of the time a reconnections do not get my connection back and the wait for the disconnection of "E" takes 2-3minutes too. So far as you had mention, all the ROMs and RADIOs i have tried did not solve this issue and no one here had any clue to this. I am really TEMPTED to test this radio from HELL but am worried I may get more hell should it not solve my problem.. Appreciate your input here
thomassster said:
Being a chef, putting out a special rom for the public takes a great deal of time. They need the certain feedback from users on the rom. The first few posts are cluttered with the good jobs and great rom, but this is the thing to thank the chefs for their time and efforts.
Click to expand...
Click to collapse
Feedback is far better thanks than just "thanks." If people are saying thanks, then they are probably using the ROM, and if they're using the ROM they should have something to say about it. Even if it's just a few things they like.
motocrossmann said:
OK, we all know the problem with radio 1.65.17.10... DO NOT FLASH IT, IF YOU WANT TO CHANGE RADIOS!!!
I actually found a major benefit (for me) to use it.
I had been experiencing problems with ATT here in California, where my data connection would just stop working, despite showing it being connected. The fix would be easy, just disconnect the data session and reconnect and it would be fine again for awhile (anywhere from an hour to a day). The problem for me is that I use direct-push email for work, when the data connection would fail, there was no warning of a problem. Emails would go missing until I checked Activesync, noticed the failure, and reinitiated the data connection. Very annoying, and easy to miss important messages...
So after troubleshooting with ATT, to no avail, and numberous trys with various radios and ROMs here on XDA, I decided to try it.
My issue has been gone for 4 days now. It is possible that Dutty's new Hybrid v2 helped, but all of his previous ROMs had the problem. So, it was either the new radio, or the new ROM.
DO NOT INSTALL THIS RADIO, YOU CAN'T REMOVE IT CURRENTLY!!!! (but it worked well for me)
For all the bad things about this ROM, read here:
http://forum.xda-developers.com/showthread.php?t=387395
Click to expand...
Click to collapse
I have asked this in the Dutty's ROM section but no answer - so let me try here. I was wondering if this radio would solve a big problem I have had ever since I switched to Dutty's ROM. In HSDPA mode I have lost the feature of simultaneous data and voice. Before I flashed over from the AT&T stock ROM I was able to stream from my Slingbox or Sirius Radio applications and, when I got a phone call, the phone would ring and I could make the call. Post call, the data session would still be active.
With all the Dutty ROMs I have tried once the call comes in - or is placed - the data session ends. BTW - If I switch my SIM over to my Blackjack the simultaneous data/voice feature returns - the BJ has a cooked WM 6.1 ROM also.
Have you found that this radio resolves those issues??
rdecker692000 said:
I have asked this in the Dutty's ROM section but no answer - so let me try here. I was wondering if this radio would solve a big problem I have had ever since I switched to Dutty's ROM. In HSDPA mode I have lost the feature of simultaneous data and voice. Before I flashed over from the AT&T stock ROM I was able to stream from my Slingbox or Sirius Radio applications and, when I got a phone call, the phone would ring and I could make the call. Post call, the data session would still be active.
With all the Dutty ROMs I have tried once the call comes in - or is placed - the data session ends. BTW - If I switch my SIM over to my Blackjack the simultaneous data/voice feature returns - the BJ has a cooked WM 6.1 ROM also.
Have you found that this radio resolves those issues??
Click to expand...
Click to collapse
Hmm, I never had that problem and still don't. I have tested simultaneous data with my phone and it works fine pre/post installing this radio.
cmloo said:
Motorcross,
Tq for yourfeedback. I face the same problem with what u had but mine is more serious!!! My EDGE connection (I am in Malaysia using DiGi) lasts only minutes. 50% of the time a reconnections do not get my connection back and the wait for the disconnection of "E" takes 2-3minutes too. So far as you had mention, all the ROMs and RADIOs i have tried did not solve this issue and no one here had any clue to this. I am really TEMPTED to test this radio from HELL but am worried I may get more hell should it not solve my problem.. Appreciate your input here
Click to expand...
Click to collapse
Well, I wish I could provide you some good advice on that one, but your problem is quite different than mine. Have you tried changing the GPRS authendication menthod? PAP vs CHAP?
Odd - I have tried a bunch of the Kaiser, Sena and Niki radios with the same issues. Once I go back to the stock AT&T ROM all is well. Definitely not worth running the AT&T ROM for the feature; I may try one of the Non-Dutty ROMs just for a test.
5/19/2013 Update: The bug might be dead! Like for real this time. See this post, post number 14 in this thread with an explanation of what to do.
10/25/2012 Update: TRY THE LATEST BUILDS OF BRUCE'S CM10 STARTING WITH THE 10/25 VERSION!
Bruce has made a change that helps differentiate between the regular data stream and the MMS data stream in an attempt to see if that was what was causing the instability issue. This is only on Bruce's CM10 Kang as of 10/25. If you are only another CM ROM, flash Bruce's (even if just for a minute or two) and see if the data bug goes away. Please report back if it did!
If this does cure it, I'm sure Bruce will share the sollution to all other devs and your favorite other AOSP ROm will have the cure shortly.
Updated 10/24/2012
This is a detailed description of the 6 million or so things that various people have attempted to do in order to rectify the blinking data connection problem plaguing T Mobile USA users on AOSP ROMs for the Sensation. This issue is non existant in Sense based ROMs.
The problem has something to do with how the Sensation authenticates itself with the T Mobile Data Network. It's not based on the cell towers as voice calling is unaffected. The theory is that the AOSP framework lacks the proper authentication certificates for part of the data network and when the phone is routed to that part of the network, it gets kicked off teh network, then continually retries to connect.
This was and issue on the Sense Gingerbread Stock ROM in 2011 but T Mobile and HTC patched it. All Sense ROMs are free from this bug. But no one knows what exactly the patch was so AOSP ROM's have not been able to be cured yet.
Short version....
Problem started for me on Bruce's CM10 rom. But it's reported on all CM10 variants and most CM9 ROM's as well.
One day I noticed that data wasn't connecting well. It would blink on and off. Sometimes it would stay on, but if I turn it off then right back on, it might go back to blinking.
The problem exists on all AOSP roms (AOKP, CM9, all versions of CM10) even after full wipes and restores of known working nandroids.
Cell signal for voice calls works perfectly. No problems whatsoever. So the phone is connecting to T Mobile. It just won't get data.
Long version....
To fix this I've tried the following...and how each does or doesn't work.
Switch to 2G networks only and switch back. Problem remains, and still blinks E on the EDGE networks rather than being solid on them.
Updated the radio. Problem remains.
Updated the entire firmware package. Problem remains.
Superwipe and flashed Sense, verify data works well. Then regular wipe and flash a fresh install of CM10. Problem remains.
Flashed clean version of CM10 and fixed permissions. Problem remains.
Made calls from the phone. Some people have reported that this helps temporarily.
Sent myself a text message. Some people have reported that this helps temporaliy.
Turn on airplane mode for a minute then go back to normal. Some people have reported that this helps temporarily.
It's not related to Wifi at all because I've created the error on fresh installs of CM10 before ever turning Wifi on.
Formatted SD card. Problem remains (and just to be sure I got the error while the blank formatted SD was removed from the device)
Checked the APN's 100 times. They are correct.
Spent an hour on the phone with T Mobile. Their tech said everything looked good on their end. He cleared the SIM and reactivated it. Problem remained.
Other people have gotten new SIM cards and found that while they helped right away, the problem eventually came back.
The only things that have shown any help to multiple users are in bold above. There are various reports of 100 other 'fixes' that people swear fixed the problem for them. But all of them involved the phone disconnecting from the network and reconnecting. That appears to be the key to get data working again temporarily. Making calls and sending yourself text messages also forces authentication on the T Mobile network without breaking the original connection.
If you want more details or want to review the logs to see if you can figure it out, logcats of the problem are located in this post! Click here for logcatty goodness!
Here is the real kicker....
Everyone once in a while...it connects. And once it's connected it'll stay connected until I turn the connection off or reboot the phone. Then it'll go back to blinking in and out when I try to turn it back on.
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Whyzor said:
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Click to expand...
Click to collapse
Okay here's an update on this for anyone who finds this thread through a search or Google or something....I'll try to describe this using the simplest terms possible so those of us who aren't cell tower engineers can understand it. (And I assume that's most of us, including me!)
The latest running theory is that the issue occurs due to the way the phone is handed off from 1 tower to another.
As you move your phone is handed off from one tower to the next. You get unregistered with tower 1 and reregistered with tower 2. That's normal.
However if you are within range of 2 towers you can't be on both. You have to be registered with 1, and that's supposed to be the stronger one. But AOSP ROMs lack a T Mobile certificate that authenticates which tower is supposed to have priority. So when the data is blinking you are getting bounced between 2 towers because the phone is trying to register with both.
The latest version of Bruce's CM10 ROM (Dated 10/10/12 and with TMOUS DATA in the rom name on the download page) supposedly includes patches that fix how this authentication works. And I only say 'supposedly' because the patches have only been up for about 12 hours so the jury is still out on how well it works. Personally I've been on it all day today and haven't had the data issue yet. But it can be days in between seeing it. So it'll take a while to know for sure that it's fixed.
If this turns out not to be the exact cause of the problem, it's something similar and a final sollution should be found soon.
Update: This have never been substantiated, and several users with the bug have reported knowing for a fact that they experience the problem when in range of only 1 tower.
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
malybru said:
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
Click to expand...
Click to collapse
That's one of the 1000 things that's been tried, to no effect. If he APN is set to the correct one the extra APN's are ignored.
Nothing that you do within the phone can cure the problem. At most, forcing the phone to re-register with the tower is the only thing that can help, and that will be temporary if it works at all.
The best bet now is to hope that Bruce fixed it with his latest additions to CM10 now that we understand what the actual problem is (or at least that we think we do)
Update....
T Mobile data is still broken. It has not been fixed yet. The latest theory may just be one more in a long line of theories that turned out to be wrong.
There are days when I really hate this phone.
Thanks for the update. I've been monitoring that thread occasionally, but it has way too much traffic for me to keep up. I was close to switching to it, but I need good battery life and reliable cell service over any smoothness benefits of JB, which is why I'm sticking with HyperNonSense ICS for now.
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
cpittman said:
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
Click to expand...
Click to collapse
I have tried the SIM swap fix. And that has apparently worked. I've been using in good for about the last 6ish hours without any problems. :good:
So i'd give that a shot if your willing.
I've been using CM10 KANG since it was available for HTC sensation. Never had the data blink issue. Recently, my phone started to have this issue. Data would simply not connect with CM10 or CM10.1 with any radio/firmware combination. I also noticed that when I travel to work, i get data say after 10 miles away from my home and it continues to work after coming back home. However, after restarting the phone, i hit the blink problem again. Wondering if its because of some cell tower maintenance/upgrade near my area.
So I was on bruce's ROM until a week ago and this never happened while on his ROM. Just upgraded to albinoman's ROM and this started happening. I have to send myself a MMS picture to get it back again. Hope this helps
Fix
Ive had this problem on and the only thing that seems to help is flashing a new ROM but then a few weeks later it returns... I realized that this only happens when I try to send an MMS message or attempt to receive them. I don't know how to stop receiving an MMS but just delete the picture message you're trying to send and your data should stop blinking on and off. Can't guarantee it'll work for you but it worked for me! GL!!
It appears as though this stupid annoying silly obnoxious bug has finally been squished, sprayed with 3 cans of Raid, and its' mangled corpse then burned to a crisp...I hope.
3 weeks ago W1ldFl0wer brought this fix to Albinoman's attention...
In the build.prop under phone>system was the following line....
ro.telephony.ril.v3=datacallapn,signalstrength
This line appeared like this on all AOSP roms for the sensation.
The fix was to add skipbrokendatacall to the line so it looked like this....
ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Save the file, reboot, and data should spine right up and work fine. So far the peopl ewho have run into the data bug have implimented this change and BOOM, data fixed.
So if you use any AOSP ROM 4.0, 4.1, or 4.2 other than Albino's CM10.1 Kang just add skipbrokendatacall to that line and see if it fixes it. Only do this if you on in the US on T Mobile's network. If you are in parts of Europre making this change will screw up your data.
If you are using Albinoman's CM10.1 Kang ROM, he has already included this line in the build.prop for you. You just have to activate it. About 30 lines into the build.prop is the new line that reads...
#ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Just delete the # in front of that line. (The # makes the ROM skip the line when loading everything, but lets it stay in the file so you can read it. Deleting the # means that the phone will read that line when it reboots.) Then go up to the line that says the same thing without skipbrokendatacall and delete that line entirely. Save the file and reboot. If you don't delete the original line without skipbrokendatacall, your phone will go haywire, data might not work at all, and you might inadvertantly trigger Z Day. So if you're not ready to fight in the zombie apocolypse, only leave one of those lines in the build.prop.
Hope this cures it for everyone! Again, don't make this change if you live outside the USA or are not on T Mobile's network! Doing so on other networks in other parts of the world could make things worse for your phone!
Here is the link to the post where W1ldFl0wer informed Albinoman of this fix.
http://forum.xda-developers.com/showpost.php?p=40755845&postcount=9003
I don't think W1ldFl0wer invented the fix, but he certainly is the one who made it public to Sensation users so go to that post and thank him/her bcause I might finally be able to stop obsessing over this stupid bug because of this user!!! :good:
First of all I would like to say I appreciate all the work that the XDA forums has been doing, and I am pleased to see that the community is as strong, if not, stronger since the last time that I have been here a couple years ago. The questions, answers, feedback and help, let alone for the Samsung Galaxy S 4G released by T-Mobile in February of 2011, is amazing. These forums have really helped people make the most out of their device, and had it not exist, this Galaxy S in my hand would have been long forgotten by Samsung, and the Gingerbread stock ROM that I was given with would be my home. It reminded me of how much I had missed messing with these android devices; nothing like jailbreaking and installing cydia on my iPhone. The experience is not the same. Anyways...
Pulling out my T959V from its box I decided it was time to finally install ICS on it after Samsung have let these great device fade away.
I installed ICS last night and stayed up searching for kernels and testing out different ROMS some slow and many faster than others and decided that Cyanogen 9 was the best looking and performance-wise ROM on the phone in my opinion. Considering that all other ROMS base it on the nightly builds extra stuff was just junk, considering this phone only has one processor. So I upgraded from Gingerbread 2.3.6 and I've tried many different kernels and everything works except WiFi. It can not even search for one network no matter how many times I press "Scan". I'd appreciate all the help I can get.
Thanks
Try rebooting into recovery and running fix permissions. Usually fixes wifi right up.
getochkn said:
Try rebooting into recovery and running fix permissions. Usually fixes wifi right up.
Click to expand...
Click to collapse
gave that a go no good :/ I wonder what the problem is?
mkho30 said:
gave that a go no good :/ I wonder what the problem is?
Click to expand...
Click to collapse
Was wifi working after you went to GB? Just trying to eliminate a hardware issue. I've flashed CM9 a bunch and have never had wifi issues on it.
hechoen said:
Was wifi working after you went to GB? Just trying to eliminate a hardware issue. I've flashed CM9 a bunch and have never had wifi issues on it.
Click to expand...
Click to collapse
yeah I actually used wifi on that same day before I upgraded to ICS. I was using stock GB 2.3.6 then rooted and all that stuff...
mkho30 said:
yeah I actually used wifi on that same day before I upgraded to ICS. I was using stock GB 2.3.6 then rooted and all that stuff...
Click to expand...
Click to collapse
I'd check the MD5 of the CM9 DL and make sure it's a match. I haven't heard of anyone else having that issue. Also make sure you DL the latest CM9. If the MD5 matches format system, wipe cache/dalvik and flash again. Reboot an let it sit for five minutes then try wifi.
hechoen said:
I'd check the MD5 of the CM9 DL and make sure it's a match. I haven't heard of anyone else having that issue. Also make sure you DL the latest CM9. If the MD5 matches format system, wipe cache/dalvik and flash again. Reboot an let it sit for five minutes then try wifi.
Click to expand...
Click to collapse
Yeah I've checked the MD5 sums of the zip packages after download. This is so bizarre, and the CM9 is not the only ROM I've tried. I've tried about 4 or 5 of them and different kernels as well and all of them do not connect to WiFi. I have formatted system, and always wiped any trace of the prior ROM before installing. Plus, I have tried the method where I would boot to recovery and "fix permissions". No good.
I would use a heimdall one click go back to stock kj6 then flash up to cm9. Sounds like you have some bugs that will only get squashed by going back to stock. IMO I would flash bootloaders too. Just so it overwrites EVERYTHING.
eollie said:
I would use a heimdall one click go back to stock kj6 then flash up to cm9. Sounds like you have some bugs that will only get squashed by going back to stock. IMO I would flash bootloaders too. Just so it overwrites EVERYTHING.
Click to expand...
Click to collapse
I just used the Stock KJ6 + Root with the Blastoff v2 kernel integrated, flashed, flashed again and installed boot-loaders as well. Phone restarted, went to WiFi, checked it, and it says "Error". Now I'm going to flash it to true stock using Odin rather than the .jar executable no luck so far and I don't know whats going on.
mkho30 said:
I just used the Stock KJ6 + Root with the Blastoff v2 kernel integrated, flashed, flashed again and installed boot-loaders as well. Phone restarted, went to WiFi, checked it, and it says "Error". Now I'm going to flash it to true stock using Odin rather than the .jar executable no luck so far and I don't know whats going on.
Click to expand...
Click to collapse
Sounding more and more like a hardware issue. Wifi and bluetooth are on the same chip so if your still on stock try and turn on BT. If it turns on it might not be the chip. If it gives the same error I'd bet money on a bad chip.
This would be a good time for logcat and dmesg...
Posted from my SGS4G, thanks to Team Acid development
hechoen said:
Sounding more and more like a hardware issue. Wifi and bluetooth are on the same chip so if your still on stock try and turn on BT. If it turns on it might not be the chip. If it gives the same error I'd bet money on a bad chip.
Click to expand...
Click to collapse
Bluetooth works fine, WiFi just wont turn on. Its not a hardware issue, and WiFi was working the same day before I flashed to ICS
Done use stock + blastoff that is a stepping stone one click for people to go back to stock then either flash another gb rom or ics rom. Wifi is broken because of the new wifi module used. I never meant for it to be used as a daily driver. Use the heimdall one click bhundven has posted in his one click thread.
@mkho30
I had the same exact Wi-Fi issue a few months ago. I tried everything you tried and what members are suggesting in this thread.
I also asked about this issue on irc (Team Acid) and was told by Bryan that ICS (if I remember correctly) doesn't support WPS button connection. I assumed it was "on my end" and not ROM related.
Bryan suggested that I reboot my router. I had done that several times before asking. I didn't even know you could log in to your router to reconfigure it so he suggested that I Google to learn.
Long story short. I googled and read allot. I reconfigured my router many different ways. I disabled my WPS button connection and reset my router many times. I changed the security every way possible. I even set up a guest network.. the ONLY way I was able to connect to my Wi-Fi network was if I disabled the security COMPLETELY.
That wasn't an option for me. I live in an apartment building and I have seen people in the halls with laptops using their neighbors Wi-Fi.
I tried everything for a couple of months and finally went back to Gingerbread last weekend.
Sorry I can't be of any help with this reply. I just wanted to share my experience and let you know that you aren't the only one that has this issue...man I miss ICS. I didn't have an issue with the battery after "I settled in" Hopefully we can find out what is going on with us.
Btw. I'm back on Gingerbread and I connect to Wi-Fi with no problems.
WPA2 encryption should work fine. It works fine with my router configuration
FBis251 said:
WPA2 encryption should work fine. It works fine with my router configuration
Click to expand...
Click to collapse
I tried that several times FB. During my searching I came across a thread (one of those answers sites) that gave your answer as a fix.
I REALLY did my do diligence in trying to get connected. I hadn't seen anyone else with this problem until today so I spent hours trying WPA2 and other configurations. I thought WPA2 would fix it for sure because that was what I had read so I kept trying it. It never worked for me. The only thing that did was having no encryption at all..I started to think that it was a "Black Ice Voodoo thing" lol. Remember how some users, no matter what they did, could never flash Black Ice Voodoo?
Btw the error I always got was an Authentication error.
Thanks for replying
If you're up for it and your router is supported, try OpenWRT. It really sounds like a router issue.
Posted from my SGS4G, thanks to Team Acid development
Sorry. I don't use a pc at work. I have to sneak on xda using my phone and they don't like seeing is on our phones for to long.
I forgot to mention in my reply to the OP that I DIDN'T have a problem scanning for Wi-Fi access. I could do that. I just couldn't connect without getting an Authentication Error. My phone would scan, connect, then discontent and give me the error.
I've had the exact same authentication error, scans,asks for password, tries to connect, then errors out, usually always after flashing CM9 and either a reinstall (recopying to my SDcard too) or a fix permissions have fixed it.
ALSO, this is very important. FORGET the connections in your wifi list after doing the fix permissions. IT WILL NOT connect to a saved connection. Reboot to recovery, fix permissions (don't use a tool within android), goto wifi, click on the connection and choose forget, then choose the connection again and try that.
jeffsf said:
If you're up for it and your router is supported, try OpenWRT. It really sounds like a router issue.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
Thanks Jeff. I'll try it when I get home. I have a Motorola Surfboard that is less than a year old (It's a modem/router combo) so the unit is "up to date"
---------- Post added at 05:35 PM ---------- Previous post was at 05:16 PM ----------
getochkn said:
I've had the exact same authentication error, scans,asks for password, tries to connect, then errors out, usually always after flashing CM9 and either a reinstall (recopying to my SDcard too) or a fix permissions have fixed it.
ALSO, this is very important. FORGET the connections in your wifi list after doing the fix permissions. IT WILL NOT connect to a saved connection. Reboot to recovery, fix permissions (don't use a tool within android), goto wifi, click on the connection and choose forget, then choose the connection again and try that.
Click to expand...
Click to collapse
I will try this. I have done much of what you have stated here maybe even all of it before. But not in the order you describe.. I'd really like to go back to ICS. I had 4G on it (home) where I used to get 3G on Gingerbread. Also at home I needed Wi-Fi calling on Gingerbread but on ICS I had great reception.
@jeff. I just googled OpenWRT and I should have before I said I'll try it when I get home lol. OpenWRT might be to much for me right now.
Thank you for all your help people. I'll update you as soon as I can. I must go sailing now. It's Red Flag!
ISSUE RESOLVED
Thanks, SlimSnoopOS!
Alright let me say that while I am very inexperienced with ROM-ing and the like, I have done it once successfully in the past (several years ago with my Droid X) without any issues. I rooted my phone today and installed the latest D2VZW release (not nightly) of the Carbon ROM.
My biggest problem is that I have no mobile network connection. I have looked at other discussion boards with people having similar problems, but were not of help to me as I have no idea what they are saying. I can say, however, that my IMEI number is correct (had it written down), but my phone number according to the Status is 000-000-2212.
EDIT: There is a mobile network connection. I have the bars, and "4G" switches back and forth to "R". I can't, however, call or receive calls, or text message at all.
EDIT2: Upon updating to latest version, my phone number is reporting correctly, but I still can't use my mobile network connection. It does not ask me to do the initial setup upon starting for the first time after flash.
Second, there is no lock screen, the home button doesn't work, most apps don't come up at all, etc. I'm totally lost.
I appreciate all help trying to get me pointed in the right direction here, or at least figuring out what's happening. I will do my best to provide as much information as I can, and I apologize ahead of time for my lack of understanding.
EDIT: If it's not something I can fix, I'll try to reset it back to stock using the pinned thread, but I don't have time to do so right now.
EDIT2: I updated from v1.0 to v1.8, and it resolved most of the problems, which I deleted from this thread. The vital ones are still present, however.
When you flashed CarbonRom, what did you wipe in recovery? Also, have you done any of these steps? Lastly, since you performed some edits, could you clarify what is currently wrong with your phone?
Thanks for your reply! I was actually going to delete this post and start a new one because I've greatly narrowed down my problem. Just typing it all out above seemed to help me think about the problem and fix it.
After getting all updated ZIPs and flashing them, I got the ROM working properly.
The problem with the mobile network persisted, but after trying Fix #2 in your link, it worked. As far as I can tell, my phone is fully functioning now. Thanks a ton!
Always here to help!
Sent from my SCH-I535 using Tapatalk 4
Hey all,
Ugh, didn't mean to post yet!
I just updated from CM9 to 10.2 in the hopes it might fix this bug, but it didn't. I suspect then that it's not ANYTHING to do with a ROM per se but I'm perplexed as to what it is.
The behaviour is:
- I get a voice mail
- After listening to the voice mail, deleting it, and hanging up, the notification doesn't disappear
- Some time later, I get a repeat notification of the voice mail
- During this time, I can't receive any texts
- About a DAY later, the phone will realize that voice mail actually has been deleted
I've tried searching xda, and I've tried general googling, but I haven't pinned anything down. I've seen some references to what might be a similar bug, but not with these ROMs, and... honestly a couple of YEARS ago.
ccamfield said:
Hey all,
Ugh, didn't mean to post yet!
I just updated from CM9 to 10.2 in the hopes it might fix this bug, but it didn't. I suspect then that it's not ANYTHING to do with a ROM per se but I'm perplexed as to what it is.
The behaviour is:
- I get a voice mail
- After listening to the voice mail, deleting it, and hanging up, the notification doesn't disappear
- Some time later, I get a repeat notification of the voice mail
- During this time, I can't receive any texts
- About a DAY later, the phone will realize that voice mail actually has been deleted
I've tried searching xda, and I've tried general googling, but I haven't pinned anything down. I've seen some references to what might be a similar bug, but not with these ROMs, and... honestly a couple of YEARS ago.
Click to expand...
Click to collapse
I have not seen this on any of my T-Mobile phones....did you do a full wipe before flashing CM10.2..
Which 10.2 Rom did you flash..
You Might have to one-click back to
stock.
That should fix it..then work back up.
Sent from my SM-G900T using XDA Premium 4 mobile app
Well, I did do a factory reset.
Is resetting to the stock ROM actually guaranteed to, well, basically format /system?
(Oh, and I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2451317 )
P.S. see here for someone's... probably unorthodox solution to the problem. Basically seems to be forcing # of voice mail notifications to 0. Which isnt really what I want, anyway.
http://forum.xda-developers.com/goo...w-to-sprint-fix-persistent-voicemail-t2562262
ccamfield said:
Well, I did do a factory reset.
Is resetting to the stock ROM actually guaranteed to, well, basically format /system?
(Oh, and I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2451317 )
P.S. see here for someone's... probably unorthodox solution to the problem. Basically seems to be forcing # of voice mail notifications to 0. Which isnt really what I want, anyway.
http://forum.xda-developers.com/goo...w-to-sprint-fix-persistent-voicemail-t2562262
Click to expand...
Click to collapse
That looks like a work-around not a solution. .
Yeah if you odin back to stock...
Its a guarantee it will format your system partition..
Try gremlin remover its always worked for me and odin is pretty simple..follow the OP its a one-click pre-made odin setup so dont change anything and your good.
http://forum.xda-developers.com/showthread.php?t=1500427
Once your back to stock...
And the problem is fixed.
I always went to Team Acids CM9.
Let the partitions convert..
Then on to CM10.2 or whatever..
Never had a problem this way..
Sent from my SM-G900T using XDA Premium 4 mobile app
hutson23 said:
That looks like a work-around not a solution. .
Yeah if you odin back to stock...
Its a guarantee it will format your system partition..
Try gremlin remover its always worked for me and odin is pretty simple..follow the OP its a one-click pre-made odin setup so dont change anything and your good.
http://forum.xda-developers.com/showthread.php?t=1500427
Once your back to stock...
And the problem is fixed.
I always went to Team Acids CM9.
Let the partitions convert..
Then on to CM10.2 or whatever..
Never had a problem this way..
Click to expand...
Click to collapse
Unfortunately, I have the 959W rather than the 959V so I can't use it.
And I remember upgrading from gingerbread to CM9 was a lot tougher than I expected (I think getting the drivers to work right) and I had to get a LOT of help from a member here on the forum. IIRC there were a lot more reboots required of the phone / my PC to get things to work.
All in all I probably shouldn't mess around with ROMs. Hardware problems make me angry and frustrated.
ccamfield said:
Unfortunately, I have the 959W rather than the 959V so I can't use it.
And I remember upgrading from gingerbread to CM9 was a lot tougher than I expected (I think getting the drivers to work right) and I had to get a LOT of help from a member here on the forum. IIRC there were a lot more reboots required of the phone / my PC to get things to work.
All in all I probably shouldn't mess around with ROMs. Hardware problems make me angry and frustrated.
Click to expand...
Click to collapse
O..didn't know you had the T959w..
Well I have seen something similar
On the Samsung GS4G Blaze..
They had a call fowarding bug that was carrying over on Roms..
It was something in CM11 that they
Figured was being written on the
Sim Card..and it was even carrying over to any Rom you flashed..
Once you got it... it didn't matter
what Rom you installed
full wipe or not it stuck..
They have Offical CM11 and the
CM team fixed it..but I remember it took a couple weeks..
Have you tried getting another
Sim Card..couldn't hurt..
Have you tried Force closing the
Phone Apk.and clearing data..
Also found this..
Here's what just worked for me on my Tmobile Galaxy S III
1) Pull the battery
2) Wait a few minutes with the battery out (I waited 5 minutes)
3) Pull the SIM card
4) Replace battery and power up phone. Wait until phone is fully booted
5) Power down phone
6) Replace SIM card and power up
Annoying VoiceMail icon is now gone.
BTW.. I hate the voice mail notification...
I wish people would
Never leave me a voice mail..LOL..
Sent from my SM-G900T using XDA Premium 4 mobile app
Oh huh, I missed your reply till now.
I think force closing the phone app and clearing caches works but ONLY temporarily and then the problem reoccurs (when the phone decides to check for more voice messages?)
Man if this was something being written on the sim card and not a ROM thing that'd be really annoying. But couldn't I "just" wipe the whole sim card? That's gotta be possible, right?
I'm trying the pull-battery-and-sim-card just to see what happens.
On the plus side I found some old posts of mine on the forum and realized that I only ever used this new computer for flashing stuff. So I just have to figure out which USB port worked last time... the usb drivers should still be installed and everything.
^ Just curious what modem are you using? Is it patched to work on MTD partitions layout? Is it the stock one from Wind the Canadian carrier?
Try using modem LB6 for 959w/v patched to work for mtd roms, hope this will fix the issue.
Rebel_X said:
^ Just curious what modem are you using? Is it patched to work on MTD partitions layout? Is it the stock one from Wind the Canadian carrier?
Try using modem LB6 for 959w/v patched to work for mtd roms, hope this will fix the issue.
Click to expand...
Click to collapse
I believe I am using the LB6 - certainly, I'm not using the stock. (The only confusion is that I've got zip files on my PC for the LB6 and a KG4 modem.)
Whatever modem I have on my phone was working fine prior to some upgrade of CM9 (IIRC).
God!!!
So I got Heimdall working again, flashed to stock, reformatted my SD card, re-updated to CM10... and I'm getting the same problem again!
So either it's the CM 10 ROM or something with my phone company! GRRRR...
Maybe the next step is to go back to stock and then just try CM 9. Or even CM 7 or something... put a modem on the stock ROM and see if THAT still ****s up.
Aaaaand stock + LB6 modem gets the voice mail notifications.
!%()*!%()*!#% phone company!