Issues With Lollipop - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

When Lollipop first came out I had a bunch of issues with it on my Note 4.
I couldnt have multiple sound effects. I couldnt join a Wireless network. My battery life was cut in half. It was bad so I had to Odin back to JellyBean and block OTA updates. Have these issues been fixed with updates yet?

whitedragon551 said:
When Lollipop first came out I had a bunch of issues with it on my Note 4.
I couldnt have multiple sound effects. I couldnt join a Wireless network. My battery life was cut in half. It was bad so I had to Odin back to JellyBean and block OTA updates. Have these issues been fixed with updates yet?
Click to expand...
Click to collapse
That's strange. I didn't have any of these issues, but I did a factory reset after the upgrade.

Related

OTA 4.0.4 (new) IMM76I - improves on signal loss issue, not solve it

Previously on the older 4.0.4 I lost the GSM signal AND could not recover signal every day after my phone went to deep sleep.
Since I updated, this morning is the ONLY day so far that I lost signal and did not recover signal.
Looks like this fix is not perfect but it helps.
You needed to create a new topic for this?
Sent from my Galaxy Nexus using XDA
I saw the same thing on my Nexus
So went back to setcpu setting the min speed of 700. Works like a charm
Drift spunk said:
You needed to create a new topic for this?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
arguably yes, isn't it the most important thing this update is supposed to address? There's no bug thread on 4.0.4 IMM76I. pray tell what you would have done.
There is another one: http://forum.xda-developers.com/showthread.php?t=1614575
I think you should extend this thread title with "for me". Because who had the "real" signal drop during sleep issue, the new OTA fixed it for them. Probably you have another issue, what is look-a-like the signal issue, but it is not that.
Sent from my Galaxy Nexus using xda premium
I never experienced the issue, but I love how everybody is assuming that this new build fixes this notorious issue. I have yet to see a change log or any kind of information from Google that explains what was done in this release other than "a few kernel tweaks." People's posts on XDA quickly turn into accepted facts of information without any kind of verification.
Fixed it for me. What do you think it was?
sent with 3g courage. better recognize. 4g courage coming soon. stock up on diapers.
I have no idea, but shouldn't these things be logged somewhere? It would be nice if Google issued some release notes with their releases so people can stop speculating whether a certain bug was fixed or not.
Some people don't feel there is a need to do a factory default after every update, I on the other hand disagree.
When I changed over to Yakju, I did a factory default and wiped everything. I never had a signal drop issue at all.
However when I got the new small update via OTA, I decided to let it run for a bit without the factory default.... As such, I experienced one drop as noted on Signal Alert.
Immediately I did a factory default and wiped everything again. Haven't had one signal drop since...
So not saying there never was a problem to begin with, but it does seem that factory defaulting after every update causes things to run a lot more smooth, permanently. At least for me.
Agreed. I always do a reset then restore particular apps with titbu. No software issues so far.
greeced said:
Some people don't feel there is a need to do a factory default after every update, I on the other hand disagree.
When I changed over to Yakju, I did a factory default and wiped everything. I never had a signal drop issue at all.
However when I got the new small update via OTA, I decided to let it run for a bit without the factory default.... As such, I experienced one drop as noted on Signal Alert.
Immediately I did a factory default and wiped everything again. Haven't had one signal drop since...
So not saying there never was a problem to begin with, but it does seem that factory defaulting after every update causes things to run a lot more smooth, permanently. At least for me.
Click to expand...
Click to collapse
Will try this when I get home today. It's really irritating me how my signal just drops and I have to do a "Airplane Mode On/Off" to reacquire signal.
It actually got worse since I updated to IMM76I.
greeced said:
Some people don't feel there is a need to do a factory default after every update, I on the other hand disagree.
When I changed over to Yakju, I did a factory default and wiped everything. I never had a signal drop issue at all.
However when I got the new small update via OTA, I decided to let it run for a bit without the factory default.... As such, I experienced one drop as noted on Signal Alert.
Immediately I did a factory default and wiped everything again. Haven't had one signal drop since...
So not saying there never was a problem to begin with, but it does seem that factory defaulting after every update causes things to run a lot more smooth, permanently. At least for me.
Click to expand...
Click to collapse
A slightly sloppy whenever you install an update you have to do wipe the phone .. It should not be so
@rbiter said:
Fixed it for me. What do you think it was?
sent with 3g courage. better recognize. 4g courage coming soon. stock up on diapers.
Click to expand...
Click to collapse
IMM76I was just a kernel. The kernel reverts the radio and voltage changes.
If folks really believe that IMM76I was not a fix, they could easily run an old 4.0.3 kernel. If it fixes it, then the problem is IMM76I, if it does not, then they are pointing their finger in the wrong direction.
Here is a 4.0.3 image I found. Fastboot it.
Code:
adb reboot bootloader
fastboot boot boot.img

[Q] Frequent updte from Samsung?

Hello all. I have my Note rooted with a custom recovery, but I have not flashed a rom. Well, I have flashed a few, but I've since gone back to stock and re-rooted because the bluetooth issues are a dealbreaker for me.
Here is the actual question. I've been getting a lot of updates from samsung. I came from an HTC Evo - and HTC rarely did updates. Has Samsung really released 3-4 updates in the last 2 weeks? Or is my phone just not properly installing them? The android version is 4.1.1, also not sure if this is all the way current. I just checked on the update your phone page in the system settings and it says I am current...
I'm running the same thing as you (stock, rooted with custom recovery) and I have not had an update recently. Mine is currently 4.1.1 as well, with the L900VPALJC build. I agree that it's the BT streaming that's keeping me from custom roms right now
bl4ckllama said:
I'm running the same thing as you (stock, rooted with custom recovery) and I have not had an update recently. Mine is currently 4.1.1 as well, with the L900VPALJC build. I agree that it's the BT streaming that's keeping me from custom roms right now
Click to expand...
Click to collapse
I've had issues not only with A2DP, but also with call quality on BT as well. It sounds choppy and has TERRIBLE range on at least 3 different roms...Paranoid Android is awesome on our 5.5" screen, but I cant talk on the phone or use Slacker radio Hopefullt someone does a better job with the BT drivers sometime soon.
I imagine once the CM blue tooth problems are fixed the roms using it will get stepped up. I downloaded Macksrom today to run a trial to see how the improvements are. Though now that I know ADW isn't messing up my phone anymore I may just stick with stock for now. I have a current backup and I'm feeling bored, so I'll most likely **** around with it this weekend

Jan 2013 OTA push T989UVLH1 update fixed hanging!

So I realize this isn't on the cutting edge of development, but I come here for info from the experts, and I didn't see any info posted about this OTA push.
So I'm still running stock ROM, rooted for tethering with CWM recovery installed, and I was trying to find some feedback on this update that was pushed OTA. I see vassosman started a topic the other day, but it was quickly closed.
Let me say that I was HATING my phone because scrolling would hang the phone for minutes at random times in the day with random apps and it was maddening! Several times I had to stop myself from throwing it up against a wall.
This OTA update completely fixed it! No need to re-root it either. I love my GS2 again!
So if you were skeptical of the update (I was because one of the listed fixes was "security enhancements" which sometimes means unrooting) I can say that my experience was very positive. I'm sure I probably should have connected to Kies and installed this update long ago. Life happens. I'm behind. I'm posting for others that are behind as well.
Does the LI4 update provide even more worthy fixes? Will I have problems with CWM installed?
neubian said:
So I realize this isn't on the cutting edge of development, but I come here for info from the experts, and I didn't see any info posted about this OTA push.
So I'm still running stock ROM, rooted for tethering with CWM recovery installed, and I was trying to find some feedback on this update that was pushed OTA. I see vassosman started a topic the other day, but it was quickly closed.
Let me say that I was HATING my phone because scrolling would hang the phone for minutes at random times in the day with random apps and it was maddening! Several times I had to stop myself from throwing it up against a wall.
This OTA update completely fixed it! No need to re-root it either. I love my GS2 again!
So if you were skeptical of the update (I was because one of the listed fixes was "security enhancements" which sometimes means unrooting) I can say that my experience was very positive. I'm sure I probably should have connected to Kies and installed this update long ago. Life happens. I'm behind. I'm posting for others that are behind as well.
Does the LI4 update provide even more worthy fixes? Will I have problems with CWM installed?
Click to expand...
Click to collapse
Nope, as you stated it mostly had security improvements, but I doubt it affected rooting methods. People have reported that the normal methods to root the old firmwares still work on this one. So overall it wouldn't harm CWM or TWRP while using it, though you have to obviously reflash it
Sent from my Galaxy S2 X T989D running Jedi Jelly 4
Im on stock li4, rooted using supersu and twrp 2.4. The same old rooting methods apply, no rules changed. Happy flashing!
Sent from my SGH-T989 using Tapatalk 2
I figured I would just add my experience in this thread.
My wife's completely stock GS2 had OTA updated to LI4 2 days ago and last night the phone shut off while in the middle of a call and will not power back on. No odin, no recovery. Nothing. Had to warranty exchange.
It doesn't seem widespread as I have not seen this reported elsewhere, but my wife is a mild user and was only using the most basic of apps. I think she was using Google Talk and Messaging and the Phone app at the time.

"loosing" 3G on 4.3 Toro

So i was wondering if anyone else is having this issue.
for reference, I am on VZW, with the 4.1.1 radios (as the updated 4.2 radios had me locked into 3G no matter what, at work)
and i ALWAYS do a complete wipe (data/cache/dalvik/system) between ROM flashes.
4.3 bootloader as well.
anyway, this has been an issue since 4.3 hit my device...anything from pure AOSP to CM builds.
when I am on 3G, the bars will go gray and i cannot pull down data at all. (and yes i know the difference between blue and gray bars, I'm saying ANYTHING will say "network not available" not just google apps)
toggling data on/off fixes the problem. I ususally run into this problem 2-3 times a day and it is ALWAYS on 3G.
its not a huge deal, just more annoying than anything else. just wondering if I am alone here. going to be giving the 4.2.2 radios another chance and see if that fixes things.
Having this exact issue...it's driving me nuts as well. At this point I believe I've tried every radio with no luck. Going to try jumping back to 4.2 soon to see if it solves the issue.
Me too
+1
I love how much fast my GNex is on 4.3, but I don't think I can deal with this data bull**** much longer. Frankly, I'm really getting tired of getting a new version of Android, being happy at first, then finding the HUGE bug that makes my phone a horror to use. WHY HAVE YOU FORSAKEN THINE VZW GNEX, GOOGLE!?!?
Just an update, as I updated my radios right around the time I updated to 4.3. I just switched back to CM 10.1 and all my data connection issues went away. That means it definitely has to do with 4.3 builds and not the radio firmware.
ericbarch said:
Just an update, as I updated my radios right around the time I updated to 4.3. I just switched back to CM 10.1 and all my data connection issues went away. That means it definitely has to do with 4.3 builds and not the radio firmware.
Click to expand...
Click to collapse
That's right, 4.3 sucks.
Sent from my Galaxy Nexus using Tapatalk 4
Edit build.prop and include this line:
ro.telephony.default_cdma_sub=0
Data issues are being reported on nearly every rom for the gnex. My data reconnect /switch went from about 60 - 90 secs to a reasonable 5-10. (don't forget to reboot to apply changes)
Sent from my Galaxy Nexus using xda app-developers app
So happy I found this thread!
I'm having the SAME issue: GSM i9250 on Straight talk ATT sim (apn setting are updated and correct). Stock not rooted; been happening since 4.3 Update. From what I've read even folks on the N4 are having similar issues.
I've factory reset 3-4 times for testing purposes (back to "normal" for about an hour then those pesky gray bars and NO data on 3G/4G).
I have to do the airplane mode toggle every 1/2 hour if I'm really using the internet. Big pain in the ass!
I always rooted my devices in the past and haven't done the GNEX because I always felt stock was smooth enough for my purposes (quasi-work-phone and I need stability). If I have to deal with this bull-sh&% I'm probably gonna have to root and install a 4.2 ROM.
Any-whoo...thanks for letting me rant :^)
Hopefully "kit-kat" will help?
same issue its very annoying... did anyone find the fix ??
ffejy462 said:
Edit build.prop and include this line:
ro.telephony.default_cdma_sub=0
Data issues are being reported on nearly every rom for the gnex. My data reconnect /switch went from about 60 - 90 secs to a reasonable 5-10. (don't forget to reboot to apply changes)
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Is this a fix?
My issue seems to be on 4g as well. If the phone switches from wifi to 4g or if it goes from 4g to 3g and back to 4g it shows a connection with bars but never connects to data again.

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.

Categories

Resources