Develop Bugs

[Q] Broken Wifi - Hardware Fault? Help!

Hey there everyone, so since i flashed the CM10 nightly from the 24th, wifi has been nearly completely broken for me. You may have seen my posts where i described how my phone barely ever manages to load anything over wifi and when it does, it does so intermittently and at an extremely slow pace. This renders wifi pretty much useless on my phone. Mobile data IS working though.
Now, i first thought it might just be an issue with the nightly i was using, but this issue persisted on the nightlies from the 25th and 26th of this month (which i did full wipes between). So then, since i wanted to stay with Jelly Bean, i decided to try out Tgascoignes AOSP Jelly Bean (another full wipe here), but then this same issue was there as well. Then, i figured i'd try the first Jelly Bean CM10 nightly, since everything was working great on that one, but then this issue with wifi was still there.
So then i thought it must be an issue with Jelly Bean, so i went back to the most trustworthy and stable ROM i have used so far - One Maximus V2.1 with ICS. Then, this issue still persisted.
So, the tl;dr version of this is, wifi isn't working on any ROM for me and i can't seem to do anything to fix it and i really need some help with this. Do you guys think it might be a hardware issue? My router has been working perfectly for other wireless devices in my house. What plan of action would you recommend? Any help will be very very highly appreciated.
Also, the reason that i'm posting this as a new thread is because this isn't the same wifi antenna problem that has been documented a lot in the other thread. My wifi reception doesn't improve or vary depending on where i press on my phone and that's not the issue at all. If this post still doesn't deserve it's own thread then mods, please remove it and i will ask for help elsewhere.

The most complete restore would be to fastboot oem lock and.run the RUU for your device.
If that doesn't fix it, I don't know what will and neither will HTC I suspect, they'll likely replace the motherboard.

BenPope said:
The most complete restore would be to fastboot oem lock and.run the RUU for your device.
If that doesn't fix it, I don't know what will and neither will HTC I suspect, they'll likely replace the motherboard.
Click to expand...
Click to collapse
Well, i fully restored my phone back to stock and the issue is still persisting . Mobile data is also being really weird now even though i have set the correct APNs.
I also can't update my phone from the 1.29 firmware to the 2.17 base firmware because my carrier (Virgin) hasn't bothered to put any effort towards pushing out an update.
I think i will have to claim the warranty for my phone through Virgin and hope that they don't notice that it has been re-locked as other people have had such luck too.
Does anyone else have any other ideas about this?

I had a similar problem with my sensation after flashing some custom ( & official roms not meant for my region). Try WIFIX, somewhere in the forums. This could be a WiFi radio region code problem

magic_android said:
Well, i fully restored my phone back to stock and the issue is still persisting . Mobile data is also being really weird now even though i have set the correct APNs.
I also can't update my phone from the 1.29 firmware to the 2.17 base firmware because my carrier (Virgin) hasn't bothered to put any effort towards pushing out an update.
I think i will have to claim the warranty for my phone through Virgin and hope that they don't notice that it has been re-locked as other people have had such luck too.
Does anyone else have any other ideas about this?
Click to expand...
Click to collapse
just do it through virgin - in uk its the retailers responsibility to repair, replace or refund it if they can't prove that the fault was caused by you unlocking it etc.. (if before 6 months after purchase)

I don't know how this has happened now but I had a feeling that there was something wrong with the WiFi antenna of my phone, so I squeezed it really tight at the top left corner where the WiFi antenna is located (as seen in the WiFi faults thread) and now all of the issues mentioned above have been fixed . I have no idea if it was just pure luck and coincidence but now my phone is working normally again. If it wasn't a coincidence, then I really hope that this issue doesn't come up again.
I feel very lucky either way right now! No more need to worry about warranty issues and such . Thanks anyway to you guys for replying though, it's good that this forum chips in to help out those that are in need of help!

Dammit i have no idea what is wrong with my phone. Wifi and mobile data were working fine for a day and a half on the stock ROM, so then i decided to re-root and flash some custom ROMs again and this annoying wifi issue is back now :S. Why would this even happen? I am honestly at such a loss with this. Does anyone have any ideas about what's going on?

[Q] Caller ID Hieroglyphs

Wondering if anyone has seen this issue before. (see attachment)
If the caller is in my contact list, name is displayed without issues. However, if they are not, I get a string of strange characters appear as the name. Same goes for Private Callers, or unknown numbers.
The phone is a Samsung Galaxy S3 running AOKP d2att (4.2.1 JOP40D) Build 1.4.2012
Kernel Version: 3.0.57
Android Version: 4.2.1
Baseband: I747MVLDLK4
Model: SGH-I747(M)
Originaly purchased from Rogers (Canada) but used on the Fido network. I have had no other issues, LTE works great via FIDO or Rogers apn's and caller ID worked fine in stock.
I also have the same issue with CM10. Any help would be great!

I experience this as well. It started happening after i changed from running stock Touchwiz to Task's AOKP. It would be nice to have it fixed but as long as I can see the number of the caller that's good enough.

I was afraid someone was going to say that. However, I don't believe this is an issues we should have to live with, there has to be a reason as to why this is occurring. Anyone have any ideas?

Lahey360 said:
I was afraid someone was going to say that. However, I don't believe this is an issues we should have to live with, there has to be a reason as to why this is occurring. Anyone have any ideas?
Click to expand...
Click to collapse
Full Wipe, Reflash Everything. Should be your first thought every time there is some funky problem that no one else really has.

BAM1789 said:
Full Wipe, Reflash Everything. Should be your first thought every time there is some funky problem that no one else really has.
Click to expand...
Click to collapse
Agreed, and believe me, I have already been down that road numerous times. After a full wipe and reflash back to stock, everything works fine. As well as simply restoring to stock after AOKP/CM flash via CWM backup. Yet, as soon as a custom ROM is applied, good bye call display. Something has to be missing...

My friend is having this issue with his Fido Galaxy S3 running CM10 stable. A fix is definitely needed!

Same thing here on latest AOKP on SGS3 on Fido.

Rogers here, same issue. CM10 stable. If the person is in my contact list it shows normally, but the caller id is wonky as described above.
I think since people on the contact list show normally this issue takes a little while for some people to notice. At first I thought it was just some foreign guy calling me Then a few more calls... and I found this thread, although I would describe the display as "garbled" really. But obviously more than a few people have this issue.
This might be one of you guys, http://code.google.com/p/cyanogenmod/issues/detail?id=7074 -- talking about CM10.1, but this bug is in CM10 too obviously.

Possible fix
Hi guys,
I was thinking about this and noticed that people with this problem seemed to be on the I747MVLDLK4 baseband. It occurred to me to try switching it out and seeing if that had any effect.
Yes it does.
I used my co-workers phone (removing his phone number from my contacts first of course) and called my phone. Normally I get gibberish (I tested immediately before flashing to verify) and viola, my caller ID works now, with the tiny exception that there is a trailing "@" symbol. But otherwise it showed up correctly.
I flashed the I747MVLLH1 baseband and that *seems* to have fixed the issue. Apparently the speeds, connectivity and such can vary between basebands and your location so you may want to try a few basebands listed here and see if any of these work for you. Just remember not to flash an AT&T baseband on a Canadian phone or the other way around.
Post your results if this works for you. Cheers!

That is great news!!! I will test a few and post results.
Link is broken tho....
Edit:
http://forum.xda-developers.com/showthread.php?t=1831898
Edit2:
WORKED LIKE A F**KING CHARM!!!!!
Went down the list flashing each one and doing some various tests. Placing/receiving calls, LTE connectivity, speed tests, etc... Safe to say, I747MVLLH1 seems to be working best.
My phone is originally from Rogers, but service is with Fido (Fido sim) yet still using the Rogers APN settings.

Right on man Glad it worked for more than just me. That default base band actually seems pretty lousy in general, thinking back I'm not sure it was really working in the stock, factory firm ware either. I recall seeing unknown caller from phone numbers that I knew had id's.
Cheers!
Edit: can we mark this solved?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

After banging my head against the wall, I finally came across this thread..... THANK YOU!
I747MVLLH1 fixed my scrambled callerID

chasem said:
After banging my head against the wall, I finally came across this thread..... THANK YOU!
I747MVLLH1 fixed my scrambled callerID
Click to expand...
Click to collapse
This worked for me as well, thank you.

Same problem on my LG P930 from Bell, unlocked and connected to rogers. Using CM 10.1 2/21 nightly currently, but it was happening on older nightly's too.
I guess I have to hunt down baseband options for my handset unless other solutions have come up since the last posts to this thread.

spindley said:
This worked for me as well, thank you.
Click to expand...
Click to collapse
Worked for me too.
Samsung Galaxy S3 i747 Rogers Toronto "I747MVLLH1"

Open jira report
There is an open JIRA report against CM10.1 RC3 in regards to this issue.
Yes flashing an older ICS modem will work temporarily but there is obviously a problem with the newer JB modems released for our devices that we can hopefully get resolved.
If you want to see this fixed, sign in to JIRA and vote for the issue to help get it some support.
https://jira.cyanogenmod.org/browse/CYAN-1202
I also understand that not all of you are necessarily using CM10.1 but you may be using a ROM that pulls it's base code from CM so there is a good chance if they fix it, it will be fixed for whatever other ROM you are using.
Thanks.

Android 4.3 WiFi Issue

Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!

I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app

Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.

geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?

http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2

What I really wanto to know if this issue is posted in the official google bugs tracker

Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4

stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.

I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.

FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app

Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.

FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app

FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4

I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.

I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..

memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.

stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?

stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4

memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?

stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844

[Q] AOSP Known Issues?

I'm just trying to keep these straight, since I've seen bits and pieces of various problems on the various dev threads. Would someone be so kind as to check my logic here? Thanks in advance!
Problem: Can't get a GPS lock after flashing any AOSP-based 4.3 rom
Solution: Flash back to stock (RUU?), open up Maps or otherwise get a good GPS lock, flash back to your rom of choice
Burning Question: Why does this happen and why does stock flashing work?
(Idiot Newbie Question: RUU is basically a stock image? I need an encrypted version? Do I need to worry about breaking my rumrunner s-off/root?)
Problem: When on a phone call, and the other party hangs up, you get "call lost" instead of the standard graceful disconnect.
Solution: Isn't one yet. Gotta wait for a fix to be made.
Problem: Signal strength meter shows impossibly low values, despite data, voice, LTE all working as expected.
Solution: No idea. Of the 3 roms I've tried, (CM10, Liquid, Carbon), all do this. Minor problem, but anyways.
Problem: Purplish tint on the camera in dark scenes.
Solution: Phone's defective, send it in. / Or: Wait for a software patch.
Which is it?

@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.

Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?

adrenalinemotion said:
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
Click to expand...
Click to collapse
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free

Flyhalf205 said:
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?

adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.

Does one need to have the stock recovery to reset from Hboot?
Sent from my HTC6500LVW using Tapatalk now Free

Flyhalf205 said:
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Click to expand...
Click to collapse
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.

Karunamon said:
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Click to expand...
Click to collapse
check DBM isntead of looking at your bars to see if you even have an issue.

The signal issue sounds the same as AOSP on the Rezound. The signal strength would be same, but the signal icon would be different. Basically, HTC has set the icons to show more than AOSP.
I didn't factory reset after using rumrunner and the only thing I have noticed was I would not connect to 4g as much or as fast as before. It seems to be getting better though. I am running bonestock.
Sent from my phone using an app

Like it was explained to me the bars are kinda like the idiot lights on a cars dash. They really don't do much. Aosp shows your true signal and sense and so on shows a false truth just so people doesn't complain about poor signal. As long as my data works I don't care if I have zero bars.
Sent from my M7 using Tapatalk

Are there any bluetooth issue's ?

nujackk said:
Are there any bluetooth issue's ?
Click to expand...
Click to collapse
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.

sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
IR work yet?

exzacklyright said:
IR work yet?
Click to expand...
Click to collapse
IR is working on VanirAOSP.
I'm using Smart IR Remote to control my devices; great interface and works well with the majority of the stuff that I have.
Not sure what the progress is re: IR with the other AOSP ROMs.

With smart ir remote it should work on any Rom.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
The streaming is my main concern, Use is inmy truck and main reason I will try to keep my unlimited data FOREVER

adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
Did this happen using twrp or cwm? Some folks are thinking its cwm causing this.
Sent from my HTC6500LVW using Tapatalk
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Flyhalf205 said:
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Click to expand...
Click to collapse
This happened to people who hardware s-off'd and flashed the gpe rom too. Don't think it has anything to do with it.
Sent from my HTC6500LVW using Tapatalk

Kitkat Update = Wifi Calling/Radio Issues

I posted about this briefly on the T-Mo forums, looks like I'm not the only one who is having some issues with Kitkat. Mainly, sometimes when you leave Wifi you will lose all radio signal until a reboot. Also, on Wifi Calling, usually after 20 minutes or so you can send text messages just fine but you won't receive them until you reboot.
Just want to warn anyone who is looking to update their bootloader like I did and now can't go back to the fully functional 4.3. I'm completely reliant on Wifi calling where I am so this is a bad situation.
I've also heard there are some battery drain issues in 4.4.2 with the Note 3.

no problem here if not i get better lte signal b4 i only get one 1 bar at my work now i get 3

mrej201 said:
no problem here if not i get better lte signal b4 i only get one 1 bar at my work now i get 3
Click to expand...
Click to collapse
Yeah, the signal is a little better in some areas, but I'm not sure if that's just the way the signal is displayed or if there was actually something done to improve the signal, I tend to think it's the first option.
These are mostly issues related to Wifi calling, just wanted to warn people who are reliant on it like me.

Bacardi222 said:
Yeah, the signal is a little better in some areas, but I'm not sure if that's just the way the signal is displayed or if there was actually something done to improve the signal, I tend to think it's the first option.
These are mostly issues related to Wifi calling, just wanted to warn people who are reliant on it like me.
Click to expand...
Click to collapse
Have you tried a fresh install
TWEAKED 2.0 ELEMENT V3.0 NOTE 3

Bacardi222 said:
Yeah, the signal is a little better in some areas, but I'm not sure if that's just the way the signal is displayed or if there was actually something done to improve the signal, I tend to think it's the first option.
These are mostly issues related to Wifi calling, just wanted to warn people who are reliant on it like me.
Click to expand...
Click to collapse
How did you take the update? If you're not concerned with knox flags I really suggest backup apps etc and use philz or twrp....wipe that thing till it bleeds haha...i like to follow wipes with a reboot back into revovery....(also tapping No to any requests to add root) then flash the stock deodexed or odexed if you must lol....I've not had a single hangup. ....then after loading rom set everything up and proceed to remove bloat from [system/app] AND [data/app] ....reboot....profit.
Let me add I've had my note for about 2 weeks with stock 4.3 no root nada...straight from t-mo and had about 12-15 random reboots....After update (1st took ota then said f*÷! it and rooted and slapped custom recov on him then wiped everything except external sd and flashed stock zip) Not 1 reboot ! since what...Wednesday .....wifi calling 100 %....best of luck

BACARDILIMON said:
Have you tried a fresh install
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Click to expand...
Click to collapse
louforgiveno said:
How did you take the update? If you're not concerned with knox flags I really suggest backup apps etc and use philz or twrp....wipe that thing till it bleeds haha...i like to follow wipes with a reboot back into revovery....(also tapping No to any requests to add root) then flash the stock deodexed or odexed if you must lol....I've not had a single hangup. ....then after loading rom set everything up and proceed to remove bloat from [system/app] AND [data/app] ....reboot....profit.
Let me add I've had my note for about 2 weeks with stock 4.3 no root nada...straight from t-mo and had about 12-15 random reboots....After update (1st took ota then said f*÷! it and rooted and slapped custom recov on him then wiped everything except external sd and flashed stock zip) Not 1 reboot ! since what...Wednesday .....wifi calling 100 %....best of luck
Click to expand...
Click to collapse
Yes, tried multiple fresh installs/re-downloads.
I Odin'd the 4.4.2 update, rooted, flashed philz recovery, then wiped and installed the de-odexed from that thread over in development. It isn't an issue with the roms, it's definitely the update itself, people over on the T-Mo forums are having the same issues. Hopefully it gets worked out.

Bacardi222 said:
I posted about this briefly on the T-Mo forums, looks like I'm not the only one who is having some issues with Kitkat. Mainly, sometimes when you leave Wifi you will lose all radio signal until a reboot. Also, on Wifi Calling, usually after 20 minutes or so you can send text messages just fine but you won't receive them until you reboot.
Just want to warn anyone who is looking to update their bootloader like I did and now can't go back to the fully functional 4.3. I'm completely reliant on Wifi calling where I am so this is a bad situation.
I've also heard there are some battery drain issues in 4.4.2 with the Note 3.
Click to expand...
Click to collapse
My wife and I have Note 3s, both still on 4.3, rooted only otherwise stock rom and we are having this problem. We've had our phones since launch and this problem only started happening a couple of weeks ago. I definitely do not think it's an OS update problem.

Russbad said:
My wife and I have Note 3s, both still on 4.3, rooted only otherwise stock rom and we are having this problem. We've had our phones since launch and this problem only started happening a couple of weeks ago. I definitely do not think it's an OS update problem.
Click to expand...
Click to collapse
Strange, I didn't notice any issue at all before the update. This is my second phone and both have been fine, so maybe something larger at hand here.

Russbad said:
My wife and I have Note 3s, both still on 4.3, rooted only otherwise stock rom and we are having this problem. We've had our phones since launch and this problem only started happening a couple of weeks ago. I definitely do not think it's an OS update problem.
Click to expand...
Click to collapse
It not an is update issue. This happened to a few. Don't know exactly what fix was.
TWEAKED 2.0 ELEMENT V3.0 NOTE 3

Try this
I had similar problem on 4.3.
Try what I did here and see if it fixes it?
I know it is a little different problem, but nothing wrong in trying different fixes
Good luck.