Database Users

YET another Possible GPS issue fix for CM6..Tested!

Hey guys, so I am just like some of you who are the victims of the GPS issue when flashing CM6 nightly. At some point for me GPS failed to lock me in quickly, and it's somewhat broken, because it usually took about 2-3 minutes to lock under clear sky, and about 4-5 minutes inside of my apartment. Before the issue, it locks like instantly. Anyway, did some research and ran into a post that really helped me cleared up the issue and here's how you do it.
Things you need:
1. A rooted stock Froyo 2.2 ROM, yes there's no way around it because you will need to dial some "##" code, and CM6 dialer doesn't support some of it as I know of.
2. Your MSL code. The quickest way is to get this app from market (thanks JFree for sharing).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/QUOTE]
OK ready?
Code:
1. Nandroid backup your current CM6 (will need to restore later)
2. Boot to recovery
3. Wipe data, cache, Dalvik
4. Flash the rooted stock rom
5. do a wipe data, cache, dalvik one more time to be sure after flash.
6. Let it boot up and the next step is VERY important
7. Launch phone dialer and dial ##GPSCLRX#
8. It will ask you for your MSL, feed it.
9. Upon hitting OK, your phone will just say reboot in 10 secs, let it reboot.
10. Once rebooted, launch maps and your GPS should lock almost instantly.
11. If it worked, then boot into recovery.
12. Wipe data,cache,dalvik
13. Restore your previous CM6
14. Now try to launch maps again and you should expect same result as in step 10.
15. If NOT, then reboot and do a wipe.
NOTE: the way I understand GPSCLRX is that it somehow clear some settings internally within the radio and/or via your account provisioning with Sprint. I think the long lock time is caused by something got stuck in the process.
NOTE: For me after step #13, it worked right away, even inside of my apartment, without me having to do a wipe.
Try it out and please post your results.
Source/reference: http://community.sprint.com/baw/thread/37566 --> although it was meant for Hero but it worked for Evo apparently.
EDIT: I did several reboot after the fix and same result of instant lock. I will continue to test for several days to see if this is a permanent fix or not.

I fixed mine on accident doing everything EXCEPT the dialing GPS thing.
I just flashed to sense, my GPS locked on, flashed back to CM6 and I was good (wiping data and cache TWICE between every rom flash). If you don't have your MSL you can try what I did first and maybe save some trouble.

This worked for me. Amazing. Thank you, sir.

ViViDboarder said:
I fixed mine on accident doing everything EXCEPT the dialing GPS thing.
I just flashed to sense, my GPS locked on, flashed back to CM6 and I was good (wiping data and cache TWICE between every rom flash). If you don't have your MSL you can try what I did first and maybe save some trouble.
Click to expand...
Click to collapse
Yep I tried this approach mentioned in the other thread but no go. That prompted me to go and look for another solution.

vboyz103 said:
Hey guys, so I am just like some of you who are the victims of the GPS issue when flashing CM6 nightly. At some point for me GPS failed to lock me in quickly, and it's somewhat broken, because it usually took about 2-3 minutes to lock under clear sky, and about 4-5 minutes inside of my apartment. Before the issue, it locks like instantly. Anyway, did some research and ran into a post that really helped me cleared up the issue and here's how you do it.
Things you need:
1. A rooted stock Froyo 2.2 ROM, yes there's no way around it because you will need to dial some "##" code, and CM6 dialer doesn't support some of it as I know of.
2. Your MSL code. The quickest way is to call/chat with Sprint and it only took me 3 minutes of chat to get it.
OK ready?
Code:
1. Nandroid backup your current CM6 (will need to restore later)
2. Boot to recovery
3. Wipe data, cache, Dalvik
4. Flash the rooted stock rom
5. do a wipe data, cache, dalvik one more time to be sure after flash.
6. Let it boot up and the next step is VERY important
7. Launch phone dialer and dial ##GPSCLRX#
8. It will ask you for your MSL, feed it.
9. Upon hitting OK, your phone will just say reboot in 10 secs, let it reboot.
10. Once rebooted, launch maps and your GPS should lock almost instantly.
11. If it worked, then boot into recovery.
12. Wipe data,cache,dalvik
13. Restore your previous CM6
14. Now try to launch maps again and you should expect same result as in step 10.
15. If NOT, then reboot and do a wipe.
NOTE: the way I understand GPSCLRX is that it somehow clear some settings internally within the radio and/or via your account provisioning with Sprint. I think the long lock time is caused by something got stuck in the process.
NOTE: For me after step #13, it worked right away, even inside of my apartment, without me having to do a wipe.
Try it out and please post your results.
Source/reference: http://community.sprint.com/baw/thread/37566 --> although it was meant for Hero but it worked for Evo apparently.
EDIT: I did several reboot after the fix and same result of instant lock. I will continue to test for several days to see if this is a permanent fix or not.
Click to expand...
Click to collapse
Use this to get your MSL code its on the market:

Jfree3000 said:
Use this to get your MSL code its on the market:
Click to expand...
Click to collapse
lol wow that was super easy...thanks for sharing.

We need the option to dial ##---# its so usuful and yet its left out.

vboyz103 said:
lol wow that was super easy...thanks for sharing.
Click to expand...
Click to collapse
Not a problem, just spreading the knowledge. This app was made by a forum member btw.

worked for me

Worked for me, dear lord thank you. I wonder if one of the nightly builds corrupted this?

Thanks OP. It worked just like you posted.

Yep took my phone on a road trip to Vegas this labor weekend and GPS is locking instantly even when I was in MGM grand hotel room. I used the google nav the entire time while driving and having it plugged to charger, there was no hickups whatsoever. This Evo is rocking solid.

The ##GPSCLRX# command worked perfectly for me as well. I didn't bother with all the extra wipes (other than one before the new ROM flash). I'm convinced that all these WIPE EVERYTHING TWICE THEN WIPE IT AGAIN steps in a lot of guides are basically rain dancing.

worked like a charm..thanks!

I was hopeful after getting linked to this thread, but my GPS still locks extremely slow after following all the steps, I didn't get a quick lock on #10, rebooting and wiping again didn't help either.
Just posting to balance out the raucous "It works!" statements.

Temragon said:
I was hopeful after getting linked to this thread, but my GPS still locks extremely slow after following all the steps, I didn't get a quick lock on #10, rebooting and wiping again didn't help either.
Just posting to balance out the raucous "It works!" statements.
Click to expand...
Click to collapse
Did you try other methods other than this? If yes and still doesn't work then your phone might have an issue.

vboyz103 said:
Did you try other methods other than this? If yes and still doesn't work then your phone might have an issue.
Click to expand...
Click to collapse
No, I haven't, actually. Other than flashing stock -> Sprint Nav. (Which doesn't lock any faster)
Since topics sink so fast, would you mind pointing me in a direction to look? Thanks much.

can some1 link me to stock 2.2, i would really appreciate it.

i2ichal2d said:
can some1 link me to stock 2.2, i would really appreciate it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=743352 is the one I found, though my experience doesn't exactly lend it credit

this tutorial worked as advertised. thank you!

[Q] Just a weird screen flicker, normal?

I've had my phone since end of November so its one of the original rev.
Just a few minutes ago I rebooted my phone to recovery and this is what happened.
- Rebooted to Recovery (TWRP)
- Screen turned White
- Didn't do anything and went to take a picture of it.
- Took a Picture (view below)
- Then it loaded TWRP but screen is still flickering
- Didn't touch anything and it went to the bootloader menu and screen was still flickering.
What I mean about flickering, the screen was still viewable just the brightness was going higher and lower.
- Rebooted back to System (still flickering), tried to record it but couldnt really since the quality of the cam couldn't see what was going on.
- Rebooted back to TWRP, loaded it fine but still flickering.
- Rebooted back to System and it went away.
- Rebooted back to TWRP and it looks fine.
Modem: .83
OS: 4.3
ROM: Paranoid Android 4.3 August 16
Kernel: hells-Core b33-ANY
Now someone might say oh its the kernel, probably kernel or ROM. But this happened in both the bootloader menu and TWRP and during that time ROM and kernel wouldn't be running.
Anyone has had this happen, please share your experience
Wanted to know if this is a known thing or my phone is starting to die?
Only dropped once like 6 months back and thats w/ a hard case on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Happened to me twice till now. I think it's just a bug with gpu and a reboot should fix that. Although, I have no clue why it happens or what triggers it. Also I have noticed that both the times it happened to me, I was rebooting into recovery (TWRP).

sandy-achar said:
Happened to me twice till now. I think it's just a bug with gpu and a reboot should fix that. Although, I have no clue why it happens or what triggers it. Also I have noticed that both the times it happened to me, I was rebooting into recovery (TWRP).
Click to expand...
Click to collapse
Ah alright thanks, good to know I'm not the only one or at least its known.
I practically flash my phone weekly/daily and never had that happen to me before so when I did it today I was like wth lol. Now with my experiences with computers when it something flickers like that or graphic errors we think drivers and if its not loaded up we think its memory dying so I was already trying to diagnose it lol..
But if its a known issue guess I cant do anything about it, at least its back in working condition :good:

The same thing has happened to me, but when I am running Google Maps. The first time it happened the screen became unresponsive and I went to reboot and had the same flashing screen you are describing. I started freaking out and went to reboot again and it was persistent in the boot screen each time. After about 5 minutes it stopped but I still have issues with my phone freezing with Maps and now when I look at flash videos on the stock Browser (I don't use Chrome).
I had a similar issue with my Macbook Pro when I accidentally block the exhaust but my phone is set to very lore frequency's with SetCPU.
I am using AOKP Milestone 2 and Ziddy's kernel for OTG support.

[Q] Display Glitch on CyanogenMod M10 and Onwards.

Sept 20
I've been getting a display bug while using the Cyanogen M10 snapshot and I can't figure out the issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have done a fresh install, no kernels, no messing with stock performance settings, and lately no Xposed. Disabling Xposed seemed to have no resolve with the issue so I've tried a dirty flash this time to see if it could be something that messed up system files.
Anyone know what might be causing this or be suffering from the same issue?
In addition I tried doing a reflash of the ROM after having determined Xposed is not at fault (issue persists), this is me testing to see if some system files are somehow corrupt and have done something to cause this.
Sept 21
I noticed that the issue commonly occurs while I am in the middle of typing with the keyboard, cleared cache & data of Google Keyboard.
I have installed the latest Nightly in an attempt to fix this, if it is an issue with the M10 Snapshot.
Time since boot: About 4 hours. (Trying to find a correlation).
Issue persisting.. kinda?
The screen flashes the glitch this time, rather than freezing with the screen. So think of using some sort of app or interacting and for a split second the above image, or something similar, appears then reverts to proper rendering. My phone froze not too long after this, I didn't sit and wait to figure out if it was lag or full-freeze.
The display stopped responding though the keys still would re-light after touching the home key. I waited only 10 seconds before pulling the battery, since it wasn't worth the time finding out.
P.S. I have also posted this in the CyanogenMod Builder Thread, so if it looks familiar.. there you go.

i
Serotheo said:
Sept 20
I've been getting a display bug while using the Cyanogen M10 snapshot and I can't figure out the issue.
I have done a fresh install, no kernels, no messing with stock performance settings, and lately no Xposed. Disabling Xposed seemed to have no resolve with the issue so I've tried a dirty flash this time to see if it could be something that messed up system files.
Anyone know what might be causing this or be suffering from the same issue?
In addition I tried doing a reflash of the ROM after having determined Xposed is not at fault (issue persists), this is me testing to see if some system files are somehow corrupt and have done something to cause this.
Sept 21
I noticed that the issue commonly occurs while I am in the middle of typing with the keyboard, cleared cache & data of Google Keyboard.
I have installed the latest Nightly in an attempt to fix this, if it is an issue with the M10 Snapshot.
Time since boot: About 4 hours. (Trying to find a correlation).
Issue persisting.. kinda?
The screen flashes the glitch this time, rather than freezing with the screen. So think of using some sort of app or interacting and for a split second the above image, or something similar, appears then reverts to proper rendering. My phone froze not too long after this, I didn't sit and wait to figure out if it was lag or full-freeze.
The display stopped responding though the keys still would re-light after touching the home key. I waited only 10 seconds before pulling the battery, since it wasn't worth the time finding out.
P.S. I have also posted this in the CyanogenMod Builder Thread, so if it looks familiar.. there you go.
Click to expand...
Click to collapse
did you Wipe completely and then install fresh rom?
1. wipe completely through recovery (cache/dalvik/data)
2. install Fresh (latest nightlies) firmware
> if problem remains after few hours (without any extra customization) it might be the hardware problem... so take it to a services.
:good:

I have done those entirely.

[Q] USB Debugging Issue on Redmi 4G LTE

Hello developers
This is to bring to your notice that i have Redmi 4G with me. I am not able to connect it to my laptop via USB
My Laptop Configutration:
OS - WIn 8.1 [x64]
HDD - 1TB
I have CM-11 on my Redmi 4G, fully rooted and even the "Developer options are enabled on the phone.
Despite that I am not able to connect the phone through my laptop.
I have tried the following two threads by far, but none worked for me :
http://en.miui.com/thread-34384-1-1.html
and this as well :
http://en.miui.com/thread-78249-1-1.html
I did endless search on XDA-Forum, MiUi forum, Google but none as in nothing worked.
Here are few screenshots I am attaching just for your reference purpose:
Laptop Screenshots​
My Laptop's Device Manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try installing or updating HM NOTE 4G (LTE) drivers , I get this error :
When I enable the Tethering options , I get this screen ( P.S -> Its different from screenshot-1)
CellPhone Screenshots​
My Developer Options screen:
Notification Drawer Screenshot:
USB Computer Connection Screenshot:
Now, can somebody please tell me where am I doing it wrong. This problem repeats itself every now and troubles me.
Can the developers tell me as to what is wrong. ? ??
PLEASE HELP me Developers.
Response eagerly awaited.
Thanks & regards.

Dude, do you really think that Windows install/update driver ever worked since win 2000? Also 100%working solution is drivermax/drp.su

sm_94 said:
Dude, do you really think that Windows install/update driver ever worked since win 2000? Also 100%working solution is drivermax/drp.su
Click to expand...
Click to collapse
Bro it always did worked for me almost 99.99% cases, and secondly i have tried doing all this well in advance. I tried almost 3-4 such softwares(simialar to drivermax/drp.su)
to check as to any update for my device driver, but nothing works. . !
Any other solution is more than welcome.
Thanks & regards.

Do u have legal copy of Windows?

sm_94 said:
Do u have legal copy of Windows?
Click to expand...
Click to collapse
Yes brother its a genuine copy of Windows 8.1 [x64] OS.

That's probably the reason why it was working most of the time tho, switch to Ubuntu and gg problem slowed.

sm_94 said:
That's probably the reason why it was working most of the time tho, switch to Ubuntu and gg problem slowed.
Click to expand...
Click to collapse
Bro just due to one driver issue, you are telling me to shift my OS completely. That is something that would consume a lot of time . Tell me something for this OS only please.
Thanks & regards.

Hmm how about livecd boot?

sm_94 said:
Hmm how about livecd boot?
Click to expand...
Click to collapse
That might come handy. let me give it a try.
Will inform you shortly in an hour at max.

Blah, I've forgotten about it, download philz touch cwm and there is Pico adb with drivers for redmi integrated into it ;p

sm_94 said:
Blah, I've forgotten about it, download philz touch cwm and there is Pico adb with drivers for redmi integrated into it ;p
Click to expand...
Click to collapse
Brother , I already have PhilZ touch recovery installed on my Redmi 4G. . .
Please explain this part though -> and there is Pico adb with drivers for redmi integrated into it
Didn't get this part of your reply.
Thanks & regards.

I own a Note 4g and had the exact same problem (although with miui installed, not cm). Whas this problem present since you first installed cm?
From the middle of nowhere to the center of everywhere...

chandoliasnikos said:
I own a Note 4g and had the exact same problem (although with miui installed, not cm). Whas this problem present since you first installed cm?
From the middle of nowhere to the center of everywhere...
Click to expand...
Click to collapse
Brother, I faced this issue on both the CM-11 ( currently installed on my phone) and when I was initially on MiUi v6.4.2.0[KHIMICB] , the issue was on that ROM too.
Doesn't understand why such happens frequently with me.
Highly pissed off.
Regards.

I have miui and not cm. This problem occured about a month after using the phone, so I got suspicions that the phone itself was responsible for this. Particularly I used to "dirty" flash each miui developer rom in the top of the previous, and just do a wipe cache and wipe dalvik cache before. So I decided to move to a miui stable version with clean install. Did a full wipe, cleaned everything and installed rom. After that everything worked just fine with every windows pc and laptop I've tried.
From the middle of nowhere to the center of everywhere...

chandoliasnikos said:
I have miui and not cm. This problem occured about a month after using the phone, so I got suspicions that the phone itself was responsible for this. Particularly I used to "dirty" flash each miui developer rom in the top of the previous, and just do a wipe cache and wipe dalvik cache before. So I decided to move to a miui stable version with clean install. Did a full wipe, cleaned everything and installed rom. After that everything worked just fine with every windows pc and laptop I've tried.
From the middle of nowhere to the center of everywhere...
Click to expand...
Click to collapse
I understand this brother. Though i never developed any ROM or such thing myself, but i have been tinkering with almost every device i ever got my hands laid on.
Its in my habit to do a full clean swipe of everything be it system wipe, cache, dalvik cache basically everything which a developer says to do before installing a new ROM on the device.
I have been doing it from the start, but still got this issue.
I did a clean install [twice] of MiUi ROM[Stable] but still this issue came in like every 10-20 days. So , recently i have switched to a custom ROM , CM-11 as i mentioned.
For now i am using an alternate to transfer content between the two devices, and waiting for someone from the developers end to help me out.
Lets see when do i get a stable solution for this never-ending issue.
Regards.

chandoliasnikos said:
I have miui and not cm. This problem occured about a month after using the phone, so I got suspicions that the phone itself was responsible for this. Particularly I used to "dirty" flash each miui developer rom in the top of the previous, and just do a wipe cache and wipe dalvik cache before. So I decided to move to a miui stable version with clean install. Did a full wipe, cleaned everything and installed rom. After that everything worked just fine with every windows pc and laptop I've tried.
From the middle of nowhere to the center of everywhere...
Click to expand...
Click to collapse
I understand this brother. Though i never developed any ROM or such thing myself, but i have been tinkering with almost every device i ever got my hands laid on.
Its in my habit to do a full clean swipe of everything be it system wipe, cache, dalvik cache basically everything which a developer says to do before installing a new ROM on the device.
I have been doing it from the start, but still got this issue.
I did a clean install [twice] of MiUi ROM[Stable] but still this issue came in like every 10-20 days. So , recently i have switched to a custom ROM , CM-11 as i mentioned.
For now i am using an alternate to transfer content between the two devices, and waiting for someone from the developers end to help me out.
Lets see when do i get a stable solution for this never-ending issue.
Regards.

for Developer Option Enable
MIUI 5
1. Go To "Settings > About Phone > Android version."
2. Tap "Android version" until developer mode appears.
MIUI 6
1. Go To "Settings > About Phone > MIUI version."
2. Tap "MIUI version" until developer mode appears.
after that, you can check your device is attached to your window via adb command

To enable USB try *#*#717717#*#* and it'll not connect as regular USB but visible under debugging mode.
type the same command on your phone it will [I]disable[/I] USB and once disabled - now it will appear in your my computer and visible as USB drive.

Marshmallow Updates Issues .....

Here are the Marshmallow Update 6.0.1 issues I have so far on my T-Mobile Note 4 (just updated today):
1) Random Reboot
2) Amazon app issues
3) Can't open txt. files
4) Can't reset the Default app to open up PDF files
5) Lag
6) Apps suddenly quitting
7) Increased battery drain

I had random reboots, lags, and app freezing. Had to factory reset and all is good. It's been about a week.
Sent from my SM-N910T3 using Tapatalk

I might give Factory Reset a try, but not yet. I need to make sure that I have everything backed up correctly.

vja4Him said:
Here are the Marshmallow Update 6.0.1 issues I have so far on my T-Mobile Note 4 (just updated today):
1) Random Reboot
2) Amazon app issues
3) Can't open txt. files
4) Can't reset the Default app to open up PDF files
5) Lag
6) Apps suddenly quitting
7) Increased battery drain
Click to expand...
Click to collapse
It is 100% caused by not doing a clean update / install.

Would a Factory Reset fix the excessive battery drain issue ?

I just updated and the only issue I'm having is reaaaallly slow LTE. It's painfully slow. I've tested it several times and its not even going over 1Mbps sometimes it jumpa a bit more but it always goes down.
Any ideas what that could be?

My T-Mobile Internet connection has always been very slow. Charter WiFi at home is great. Here is an image showing my Internet connection on my Note 4:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why is my image not displayed ... ?

A lot of my problems came from restoring apps from old versions. After some digging, it turns out I was carrying old Titanium backups from 3 different phones. Cleared the old/ non-compatible apps and no problems since.

vja4Him said:
Would a Factory Reset fix the excessive battery drain issue ?
Click to expand...
Click to collapse
Ideally its best to at least factory restore wipe.
However, I personally always do the following on new ROMs and new Android versions.
-Backup things you want from your internal storage
-Make sure you have a Tar of the version you want. (and Odin of course)
-Flash TWRP if you don't already have it flashed
-Boot into TWRP
-Wipe System, Data, Internal Storage, Dalvik, and Cache
(once you do this your phone wont boot as there is no OS installed on the phone)
-Boot into Download
-Use Odin to flash the Stock FW tar file you want.
Doing this method will ensure you have a 100% clean install of the new Android version and/or ROMS
It can be a pain to do all this because you have to set everything back up.
However, I have seen this resolve so many problems at this point I personally feel this is a must.
Too many people are out there saying A Rom, a new Kernel, or a new version of Stock has this problem or that problem with out actually going clean stock. Have some problems with MM, a ROM, or a Kernel?
Do this!

Well, I finally gave in and did the Factory Reset. I need to charage my Note 4 up to 100% and see how many hours I get from my ZeroLemon 10000mAh battery now .....
Still have the issue with Default apps settings ......

DeeXii said:
Ideally its best to at least factory restore wipe.
However, I personally always do the following on new ROMs and new Android versions.
-Backup things you want from your internal storage
-Make sure you have a Tar of the version you want. (and Odin of course)
-Flash TWRP if you don't already have it flashed
-Boot into TWRP
-Wipe System, Data, Internal Storage, Dalvik, and Cache
(once you do this your phone wont boot as there is no OS installed on the phone)
-Boot into Download
-Use Odin to flash the Stock FW tar file you want.
Doing this method will ensure you have a 100% clean install of the new Android version and/or ROMS
It can be a pain to do all this because you have to set everything back up.
However, I have seen this resolve so many problems at this point I personally feel this is a must.
Too many people are out there saying A Rom, a new Kernel, or a new version of Stock has this problem or that problem with out actually going clean stock. Have some problems with MM, a ROM, or a Kernel?
Do this!
Click to expand...
Click to collapse
I followed this step-by-step down to the letter and have not been able to solve the problem of apps losing their updates after reboot. I've actually tried this twice already and I'm now in the process of downgrading to 5.1.1.

drdoombot said:
I followed this step-by-step down to the letter and have not been able to solve the problem of apps losing their updates after reboot. I've actually tried this twice already and I'm now in the process of downgrading to 5.1.1.
Click to expand...
Click to collapse
Something isn't right here.
It is in your best interest to find out what went wrong.
It seems that 5.1.1 and below is known be conceptually a horrible version of Android (at least for our phone).
The several things including memory management have vastly improved on MM.
Please feel free to PM me and perhaps we can chat via some chat medium to get this resolved.

Make sure you are using the proper APN for your carrier.

Lollipop was much better on my Note 4. Although my Note 4 still had problems with excess battery drain, but I could still put my Note 4 through constant heavy use for over 14 hours and come home with battery power still remaining.
My Note 3 does much better with battery management. I have the same ZeroLemon 10000mAh battery in both Note 3 and Note 4. I have been using the ZeroLemon 10000mAh battery in my Note 3 for more than two years, and still get much better battery life than my Note 4 with a brand new ZeroLemon 10000mAh battery.
I tried using the stock battery in my Note 4, and only got 4 1/2 hours, but would have gotten much less if I had been out gaming at night. Probably would have gotten only 2 or 2 1/2 hours.
I might take my Note 4 to Best Buy and have them do a Software Reflash ..... If the Note 7 had a removable battery, I would definitely get the Note 7.

I guess I am one of the lucky ones who did a dirty update with no bugs

Interesting ..... With each update some people have serious issues, some people only have minor issues, and some people even claim they have no issues.
For me, Lollipop was good, but the most stable was KitKat. My Note 3 is still at Lollipop 5.0, with only minor issues. Great battery life with my Note 3. Battery life is seriously damaged on my Note 4. If I do not get an update that fixes this issue, I will be forced to buy a different smartphone that has a removable battery, and compatible with ZeroLemon 10000mAh extended battery .....

my biggest issue with marshmallow is that everytime i send texts, my phone lags really bad. everything else works perfectly, but the stock messaging app lags when i'm sending texts even if it's just 1 regular text. it also lags when i'm receiving a lot. no issue with this from lollipop. clean install and even factory reset after installing, same thing

So far, I am not having any issues with Text Messaging.

Well, I just ran into another Marshmallow bug .... I can no longer save my Docs To Go files on my SD card. Error tells me that I do not have permission. I followed the instructions to give permission, but it doesn't work. So, I'm stuck with saving files to the phone first, then I have to copy the files to the SD card. I did not have this issue with Lollipop.

Is there any way to add a mobile data toggle to stock rooted mm? I liked how maximum overdrive has it, but have been having some issues so trying to fully debloat stock now.