Hello,
I got my Note9 (N960W) at the beginning of December and was really happy with it, great quick phone, getting 8-9 hours SOT with AccuBattery, which is quite exagerated probably, and around 4h30 while monitoring with GSam.
I got the Android 10 update on Monday, March 9. I used to lose around 8-9% total overnight, but now with Android 10, it's more than 20%-30%. SOT is really worse than before too, but screen off time is the worst, more than 5% per hour. It was 2% per hour with Android 9.
I didn't change anything, didn't install any new apps or didn't change my habits. I just upgraded the OS. What the hell happened? Anyone with the same problem? What can I do? I already wiped off the cache but it didn't change a thing...
Thanks for any help...
Edit: I forgot to mention I also got a couple random freeze and reboot while using TuneIn Radio, something which never happened while on Android 9...
Do a fresh install and see if problems persists, if not, you fixed it.
For me fresh install solved all bugs and problems I had with dirty update
Do a factory reset or new clean install.
My phone is 1.5 years old and battery life is very well with android 10. About 7hrs sot.
metaleloi666 said:
Hello,
I got my Note9 (N960W) at the beginning of December and was really happy with it, great quick phone, getting 8-9 hours SOT with AccuBattery, which is quite exagerated probably, and around 4h30 while monitoring with GSam.
I got the Android 10 update on Monday, March 9. I used to lose around 8-9% total overnight, but now with Android 10, it's more than 20%-30%. SOT is really worse than before too, but screen off time is the worst, more than 5% per hour. It was 2% per hour with Android 9.
I didn't change anything, didn't install any new apps or didn't change my habits. I just upgraded the OS. What the hell happened? Anyone with the same problem? What can I do? I already wiped off the cache but it didn't change a thing...
Thanks for any help...
Edit: I forgot to mention I also got a couple random freeze and reboot while using TuneIn Radio, something which never happened while on Android 9...
Click to expand...
Click to collapse
-CRO-Maher said:
Do a fresh install and see if problems persists, if not, you fixed it.
For me fresh install solved all bugs and problems I had with dirty update
Click to expand...
Click to collapse
Mr.Vag said:
Do a factory reset or new clean install.
My phone is 1.5 years old and battery life is very well with android 10. About 7hrs sot.
Click to expand...
Click to collapse
This. Android updates are terrible with the incremental update system where only the changed portion of code are pushed to the device.
always do a factory reset when ther are major changes, such as when we went from 8->9 and 9->10.
Thanks for the replies.
But what's the difference between a factory reset and a clean install? If there is one, which one is the best?
metaleloi666 said:
Thanks for the replies.
But what's the difference between a factory reset and a clean install? If there is one, which one is the best?
Click to expand...
Click to collapse
Theoretically, if you update your phone from OTA and something goes wrong, then it's possible that the problem won't be fixed by a factory reset because the files it's "restoring" from are already corrupt in some way.
When you clean install through odin, you are flashing the entire OS and replacing every file in the filesystem. This can solve a lot of random problems when Android phones get updated from one flavor to another, i.e, Android 8 -> 9, or 9-> 10.
A lotmof people here disagree that factory reset and a clean install are different. But I disagree with them. If you only update through OTA, then it's entirely possible something can be "corrupt" in the filesystem.
This is because OTA updates are "block based", so instead of replacing all of the files for an update, only the modified "blocks" of data are downloaded and installed. So over time, it's possible to get a bad OTA update that doesn't clean up prior conflicting files, or something like that.
Just my 0.02$
My phone is not rooted. Can I update from Odin still?
metaleloi666 said:
My phone is not rooted. Can I update from Odin still?
Click to expand...
Click to collapse
Ofc you can. No root needed.
Mr.Vag said:
Ofc you can. No root needed.
Click to expand...
Click to collapse
I didn't do factory reset or clean install so far.
This is weird. Today, I was off work and I nearly had 8 hours SoT. Screen off time seems to be improving too. Still, got some wifi bugs today, it shut off a few times for no reason while being home.
But just before posting this, I got a random reboot.... Hmmmm...... Never had a random reboot while on Android 9.
Looks like I'll have to do this reset or clean install....
metaleloi666 said:
I didn't do factory reset or clean install so far.
This is weird. Today, I was off work and I nearly had 8 hours SoT. Screen off time seems to be improving too. Still, got some wifi bugs today, it shut off a few times for no reason while being home.
But just before posting this, I got a random reboot.... Hmmmm...... Never had a random reboot while on Android 9.
Looks like I'll have to do this reset or clean install....
Click to expand...
Click to collapse
Yep..always must leave phone 1-2 days to see exactly how battery is.
For my opionion just reset your phone and you'll be fine.
Do a reset from recovery if you want..
Vol up + Bixby + power buttons.. and pick factory reset ...
Mr.Vag said:
Yep..always must leave phone 1-2 days to see exactly how battery is.
For my opionion just reset your phone and you'll be fine.
Do a reset from recovery if you want..
Vol up + Bixby + power buttons.. and pick factory reset ...
Click to expand...
Click to collapse
I prefer odin, because unlike a factory reset, you can use the HOME_CSC file and keep you apps and settings intact, while re writing the filesystem for system. If that fixes things then no need to re set up your device, saving you between 30 mins-2 hours depending on how many settings you prefer to be a certain way.
If that doesn't fix your problem, then you can nuke the whole thing with the CSC file.
Factory reset through the phone relies on having the correct files to restore from, and with the way Android updates, it's becoming more common for the filesystem to get mildly corrupt in one way or another where factory reset through the device doesn't fix the issue thanks to block based updates. I don't think the block based system is cleaning up after itself properly and is leaving behind old code that conflicts with new code personally, but that's just a guess.
Frick_trump said:
I prefer odin, because unlike a factory reset, you can use the HOME_CSC file and keep you apps and settings intact, while re writing the filesystem for system. If that fixes things then no need to re set up your device, saving you between 30 mins-2 hours depending on how many settings you prefer to be a certain way.
If that doesn't fix your problem, then you can nuke the whole thing with the CSC file.
Factory reset through the phone relies on having the correct files to restore from, and with the way Android updates, it's becoming more common for the filesystem to get mildly corrupt in one way or another where factory reset through the device doesn't fix the issue thanks to block based updates. I don't think the block based system is cleaning up after itself properly and is leaving behind old code that conflicts with new code personally, but that's just a guess.
Click to expand...
Click to collapse
Thanks. Where can I find the exact file I need for my phone to flash with Odin? I'm from Canada, on the Videotron carrier and the phone is the N960W.
metaleloi666 said:
Thanks. Where can I find the exact file I need for my phone to flash with Odin? I'm from Canada, on the Videotron carrier and the phone is the N960W.
Click to expand...
Click to collapse
Search xda for samfirm download tool, install it and the needed windows components on your computer.
Then go to sammobile.com and look up your phone, sm-n960w and find your specific carrier code, it'll be 3 letters. Then use that code for the "region" box in the samfirm tool, and sm-n960w for model. It will download the latest firmware from samobile at the fastest speed your internet will allow.
Alternatively you can download it straight from samobile, but the download speed is DSL like unless you pay for an account.
The flash through odin, make sure you load the HOME_csc file and not the stands CSC file in order to reta9your settings and data.
flash CSC (along with all other fields) if your problem isn't fixed.
i got 960ou1 and i get 7 hours or more with the 10 update
Frick_trump said:
Search xda for samfirm download tool, install it and the needed windows components on your computer.
Then go to sammobile.com and look up your phone, sm-n960w and find your specific carrier code, it'll be 3 letters. Then use that code for the "region" box in the samfirm tool, and sm-n960w for model. It will download the latest firmware from samobile at the fastest speed your internet will allow.
Alternatively you can download it straight from samobile, but the download speed is DSL like unless you pay for an account.
The flash through odin, make sure you load the HOME_csc file and not the stands CSC file in order to reta9your settings and data.
flash CSC (along with all other fields) if your problem isn't fixed.
Click to expand...
Click to collapse
Thanks. I'll hold for a while, as the battery gets better as it seems... But I keep this in my bookmarks.
Well, I just flashed with the HOME_CSC file. Hope it'll fix the problems with the battery...
Related
[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac
Q&A for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
lamhcmute said:
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
Click to expand...
Click to collapse
In post# 1 under the downloads section, below version 03 you will find revert longpress to recents & menu. You can download and flash this zip through recovery and menu key will be as before.
no root after flashign WizCyan
After flashing WizCyan 4 with update 1 I don't have root access. I've tried reinstalling several times and I've also tried to install superSU on it's own using CWM, both the latest version and older versions, with no success. I've also tried to install just v4 but the problem persists. Does anybody have any clue on what could be wrong? I've had root on the phone using other ROMs. I use the latest CWM.
And yes, I chose no when promted to fix superuser in CWM. Although I have also tried to pres yes during one installation.
What version of cwm are you having? Also when you click on the supersu app what message do you get?
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Gudiol said:
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Click to expand...
Click to collapse
I would suggest that you do a clean install of the ROM, now that your recovery has been updated
Excessive consumption of battery
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Will suggest to do a clean install and check and if not then report back. Anyone else facing this issue.. kindly report
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Ok, did some testing and found that some of the init.d scripts were eating battery therefore have posted an update in the OP removing these and battery consumption should be better after flashing this update.
can i install
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
s4active user said:
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
Click to expand...
Click to collapse
Sure, you can install on any firmware, but if you have wifi issues then you may need to flash modem or some other workaround. Just wipe data/factory reset and install version 04 followed by update 02. I am not sure on what you mean by memory but presume that you are referring to internal sd card. This will depend on what apps/features you install from the addon package and playstore. The ROM will not affect your internal sdcard space as it will be installed on the reserved system space.
Problem with Rom Super Wizcyan - S5 Style
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Kaitenx said:
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Click to expand...
Click to collapse
In case you want to use screen mirroring then you would need to install allshare from the addon package
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Still can't get my Wifi to enable. The flash was successful, as I can see the correct baseband on the "about" screen, but it refuses to enable. I'm in Australia, but I believe this phone came from UAE -- would that make a difference to the way the modem interacts with the Wifi hardware? I pulled this info from logcat:
Code:
I/WifiManager( 1084): setWifiEnabled : true
I/WifiService( 882): setWifiEnabled: true pid=1084, uid=10008
E/WifiHW ( 882): ##################### set firmware type 0 #####################
E/WifiHW ( 882): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 882): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 882): return of insmod : ret = -1, Exec format error
E/WifiStateMachine( 882): Failed to load driver
E/WifiStateMachine( 882): sendErrorBroadcast code:10
E/WifiController( 882): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
In the mean time, I'm going to try to source either a local radio, or one from the original region, to see if that helps.
andycore said:
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Click to expand...
Click to collapse
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
JASONRR said:
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
Click to expand...
Click to collapse
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
andycore said:
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
Click to expand...
Click to collapse
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
JASONRR said:
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
Click to expand...
Click to collapse
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
andycore said:
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
Click to expand...
Click to collapse
Glad to know that you managed to get the wifi working.
Personally, I did not face the wifi issue after flashing PHN firmware, but know that quite a few have faced this issue as reported in this thread
Normally my understanding and experience is that when you flash different modems / firmware some corruption occurs and factory reset from within the phone resets the partition & firmware. 1st time I experienced this was when I was using a MTK 6575 based device and had amended the EBR, MBR and scatter files to modify the partition sizes, even though these were flashed through mobiuncle tools (similar to odin), the revised partitions did not get changed until I did a factory reset from within the phone. I know that this is irrelevant here but thought that I would share this.
Hi guys,
Which method is better? OTA update or Odin update? If I do OTA I'd do a factory reset but I still think there'd be 'remnants' of previous OTA especially in this case moving from Nougat to Oreo.
Because I did the OTA update, factory reset but now I'm facing battery draining faster than normal.
Battery draining.........
For one, I prefer a full wipe, none of the update stuff, so Odin would be my method.
Second, Battery draining after recently flashing is normal, You need to allow time for the device to settle. The kernel needs to do alot processes after a flash and normally you dont see decent battery until 24 hours.
dave7802 said:
Battery draining.........
For one, I prefer a full wipe, none of the update stuff, so Odin would be my method.
Second, Battery draining after recently flashing is normal, You need to allow time for the device to settle. The kernel needs to do alot processes after a flash and normally you dont see decent battery until 24 hours.
Click to expand...
Click to collapse
Yeah, I'm flashing the firmware via Odin now. Hopefully that resolves it.
That could be it too, as it was factory reset so it was still 'setting up'.
Thanks
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
logs from odin? Or any error code or anything?
Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.
pzzamakr1999 said:
Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.
Click to expand...
Click to collapse
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry
pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
Which ODIN are you using? Make sure you're using the modded 3.13.1. Try this: Uncheck the auto-reboot option on ODIN. Flash the Oreo firmware and let it finish. Once it's done, manually reboot into recovery and perform a factory reset. Then boot into the OS.
ScaleneVirus288 said:
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry
Click to expand...
Click to collapse
That only happens when they update the bootloader version. It has nothing to do with the OS version. The Pie leaks are still on the v5 bootloader.
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
Also check the USB port, use the older USB port this has happened to me or PC and see the phone is probably not compatible with newest USB port....
Sent from my SM-N960U using Tapatalk
pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
What issues are you having with Spay? It seems to work for everyone else, me included.
No, you can't flash a different radio.
Not sure yet what will be required when when the official drops. Won't know until it drops.
So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.
pzzamakr1999 said:
So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.
Click to expand...
Click to collapse
Weird. I'll have to try it. I thought it was working, but now I'm not sure. I use my Gear S3 so often to pay, now I'm not sure LOL.
Update on the effort to revert back to CRK1.
Used the modified Odin, and un-checked auto-reboot. Phone remained in Download mode.
I could not figure out a way to go from Download mode to recovery mode directly. If someone knows how to do this, it would be appreciated if you could let me know.
However, rather than the "Error!" message, I received a "Erasing" message. Than the phone rebooted, and just kept rebooting, going from T-Mobile splash screen to Samsung and back over and over, with some optimizing apps screens thrown in for good measure.
So I tried again with auto-reboot on, and this time received the "Error!" message, and was able to go into recovery once that happened.
The odd thing is, nothing on my phone was changed, other than having to redo the Samsung biometrics for security. All of my apps and accounts and emails were already there, undeleted.
One more update on the S-Pay. After reinstalling the Update.zip from my SD card in Recovery, iIt does seem like there may have been a change. It is now doing the vibrate thing, which I don't think it was doing before. I will put it to the test later this week.
Downgrade Successful
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.
pzzamakr1999 said:
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.
Click to expand...
Click to collapse
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!
Mr. Orange 645 said:
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!
Click to expand...
Click to collapse
No worries, and I did very much appreciate the help. I should have realized that that should come first. I was a bit frustrated and wasn't thinking logically. It was actually the "fixing apps" message you get when you upgrade that clued me in I wasn't properly resetting the phone prior to install.
Regardless, its all good, and now that I know how to do it, I'll be more inclined to try these out in the future.
Any specific reason for the downgrade? Anything not working?
Camera issues on pie beta
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue
Fitted2 said:
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue
Click to expand...
Click to collapse
Yes
Mr. Orange 645 said:
Yes
Click to expand...
Click to collapse
You downgraded because no AR emoji? And what force closes are you having?
dami00976 said:
You downgraded because no AR emoji? And what force closes are you having?
Click to expand...
Click to collapse
I never said I downgraded.
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
ucladave said:
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
Click to expand...
Click to collapse
you may have a couple of options.
I have heard that if you reboot in to the bootloader mode and clear cache then it will get rid of the downloaded firmware update.
I'm not sure.
you can download package disabler pro and disable the update services. I went back to oreo after pie update was horrible.
in package disabler pro follow the directions to enable it
search in the app for "update"
I disabled
"Software update" (com.sec.android.soagent)
"Software update" (com.wssyncmldm)
"System updates" (com.samsung.sdm)
No more updates or notifications
Good luck
jd14771 said:
You can flash the unlocked 8.1 oreo ROM and it will remove the ability to receive updates all together. it will also remove all the bloatware from tmobile. You will have to flash this with odin. After downloading the .zip ROM, Unzip it and flash all 4 files.
You want the XAA download.
https://forum.xda-developers.com/ga...ck-960u-firmware-att-vzw-tmo-spr-usc-t3837086
Click to expand...
Click to collapse
You still need package disabler pro or some kind if service blocker.
I down graded to Oreo on two devices using XAA and I still got firmware update messages for pie. Once I set up the phone.
Blocking the services keeps the phone from checking and downloading the update.
ucladave said:
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
Click to expand...
Click to collapse
Easiest thing to do is to flash a different version modem for your device. Just flash the previous version modem file with Odin and you'll be set. If you want ota again, just flash the modem for your device matching the software update your device has installed.
I was on Oreo running the Pie modem and never got the Pie ota alert.
Jammol said:
Easiest thing to do is to flash a different version modem for your device. Just flash the previous version modem file with Odin and you'll be set. If you want ota again, just flash the modem for your device matching the software update your device has installed.
I was on Oreo running the Pie modem and never got the Pie ota alert.
Click to expand...
Click to collapse
My phone has already downloaded the update and is prompting me to install it. If I flash or run a package disabler at this point will it be effective? How can I erase the update data so it isnt eating space? Do I need to factory reset the phone first to wipe all that out before I flash or run disabler?
ucladave said:
My phone has already downloaded the update and is prompting me to install it. If I flash or run a package disabler at this point will it be effective? How can I erase the update data so it isnt eating space? Do I need to factory reset the phone first to wipe all that out before I flash or run disabler?
Click to expand...
Click to collapse
You could try clearing cache like an earlier poster suggested.
I have misplaced the solution for this problem. I am on A13 crDroid 9.3 so no ability to dump Dalvik or cache in the limited recovery. Here is a screenshot. (Plus, Mobile Network is almost always the top app despite not using mobile data)
It's exactly the same for me. I am also with crdroid 9.3.
The excessive battery consumption problem happens because for some strange reason there is a wakelock related to the mobile data network, which causes the phone not to go into deepsleep when it is idle. In fact to me it literally marks 0% deepsleep. And perfectly in one night I can go 30% of the battery without doing absolutely nothing.
PinguiNUX said:
It's exactly the same for me. I am also with crdroid 9.3.
The excessive battery consumption problem happens because for some strange reason there is a wakelock related to the mobile data network, which causes the phone not to go into deepsleep when it is idle. In fact to me it literally marks 0% deepsleep. And perfectly in one night I can go 30% of the battery without doing absolutely nothing.
Click to expand...
Click to collapse
Oddly, I always (and I mean always) see Mobile Network on A13 (or Cell Standby on A12) as the top battery app, and no suggestions worked for me. Saw in multiple custom ROMs, but not everyone sees it. I do not even use mobile data, only wifi. This "thousands" bug is sometimes part of it. Even putting the phone in airplane mode for a day does not change the battery stats at all for me.
I already found out what is the wakelock that causes this thanks to betterbatterystats. And the culprit seems to be IPA_WS or any other of the IPA family. These wakelocks indeed seem to be related to the mobile data network.
I just flashed crdroid build 9.5 on my phone. Despite being a nightly (beta) version, it fixes many bugs present in crdroid 9.3.
According to the developer the next stable version will be released soon. But in the meantime, I'm going to try a few days the 9.5 to see how it goes. And so check if they have corrected the failure of battery consumption.
In fact I have already checked that they have fixed some small bugs that were present in version 9.3. So so far so good.
UPDATE: the latest MIUI firmware update seems to have helped me. I was on the .08, and this stable is .12. My battery percents are back in the tens. Good, since there is no known optional kernel yet.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Is there a way to flash just the kernel from the latest firmware? I don't want to reinstall everything again..
mierdaseca said:
Is there a way to flash just the kernel from the latest firmware? I don't want to reinstall everything again..
Click to expand...
Click to collapse
SPES Global: https://xiaomifirmwareupdater.com/firmware/spes/stable/V14.0.2.0.TGCMIXM/
SPESN Global: https://xiaomifirmwareupdater.com/firmware/spesn/stable/V14.0.2.0.TGKMIXM/
flash via TWRP/Orangefox > done.
gentano said:
SPES Global: https://xiaomifirmwareupdater.com/firmware/spes/stable/V14.0.2.0.TGCMIXM/
SPESN Global: https://xiaomifirmwareupdater.com/firmware/spesn/stable/V14.0.2.0.TGKMIXM/
flash via TWRP/Orangefox > done.
Click to expand...
Click to collapse
That is firmware, not kernel. There are no kernel install options for spes yet. It even says "firmware" in the links.
I see the official crDroid site (https://crdroid.net/spes/9) now links to the A13 V14, which has updated in the last few days from the A12 V13 version. I'll install it myself.
My deep sleep has returned to the 90's again.
Oh lol, I misread your question.... but why you need to install everything again if You install the firmware only? the firmware is just the firmware and has nothing to do with data.. or do I miss something here?
gentano said:
Oh lol, I misread your question.... but why you need to install everything again if You install the firmware only? the firmware is just the firmware and has nothing to do with data.. or do I miss something here?
Click to expand...
Click to collapse
I just flashed the firmware. You thought I rebuilt everything else from scratch too?
I am installing the A13 firmware that just came out on the 6th of June now.
Hm, I still dont get you.
Why You need/ask for seperate kernel to flash when there is the firmware, which doesnt change any of your userdata?
Sheist! said:
I am installing the A13 firmware that just came out on the 6th of June now.
Click to expand...
Click to collapse
Ye, thats what I linked and installing that firmware wont mess with Your userdata. So there is no need to reinstall any apps or whatever. Its the just the firmware (contains drivers and boot stuff) and not the whole rom image.
gentano said:
Hm, I still dont get you.
Why You need/ask for seperate kernel to flash when there is the firmware, which doesnt change any of your userdata?
Ye, thats what I linked and installing that firmware wont mess with Your userdata. So there is no need to reinstall any apps or whatever. Its the just the firmware (contains drivers and boot stuff) and not the whole rom image.
Click to expand...
Click to collapse
RN10P has kernel downloads available to fix battery issues, etc like this, in ADDITION to firmware provided by MIUI. There are no kernels for the RN11 as of today. The RN11 firmware from MIUI just updated to A13 as of June 6, but had only the A12 version from April of this year before that on their "firmware" download link. Both files are just 1 zip files that get installed via recovery. I hope that clears it up.
Ignore any suggestions about removing/reinstalling anything else; I never asked about any of that.
(added P to RN10 to correct error and not confuse with any RN10 users)
gentano said:
SPES Global: https://xiaomifirmwareupdater.com/firmware/spes/stable/V14.0.2.0.TGCMIXM/
SPESN Global: https://xiaomifirmwareupdater.com/firmware/spesn/stable/V14.0.2.0.TGKMIXM/
flash via TWRP/Orangefox > done.
Click to expand...
Click to collapse
So I can flash this, and I won't lose any data? For the naming of the firmware, I thought it was just a word for "official rom"
mierdaseca said:
So I can flash this, and I won't lose any data? For the naming of the firmware, I thought it was just a word for "official rom"
Click to expand...
Click to collapse
Just firmware. Firmware size is extremely small, while ROM size is extremely large. ROM and firmware are 2 different things. You could say the ROM is the house and the firmware is the land, but post-updatable land. No loss of data, except when something borks and the firmware has issues within it, causing you phone headaches.
Sheist! said:
Just firmware. Firmware size is extremely small, while ROM size is extremely large. ROM and firmware are 2 different things. You could say the ROM is the house and the firmware is the land, but post-updateable land. No loss of data, except when something borks and the firmware has issues within it, causing you phone headaches.
Click to expand...
Click to collapse
Thanks I just flashed it. But I still see the battery in thousands. How can I check the firmware version on phone?
BTW where can I download the nightly?
On https://crdroid.net/spes/9 I don't see anything besides the April b uild
mierdaseca said:
Thanks I just flashed it. But I still see the battery in thousands. How can I check the firmware version on phone?
BTW where can I download the nightly?
On https://crdroid.net/spes/9 I don't see anything besides the April b uild
Click to expand...
Click to collapse
Really? Hunh. Mine popped back to normal, but I did fully charge it and reboot it too. The deep sleep number (look under About Phone) jumped back into the upper 90's as well (good), and it had been stuck at 0.
I use Device Info HW which SHOULD (but does not even with root enabled on it!) show it on the 3rd tab, System, for the value of Description, but mine keeps showing just a dash! You'll have to locate an app that reveals the installed firmware.
Are you in India?
Sheist! said:
Really? Hunh. Mine popped back to normal, but I did fully charge it and reboot it too. The deep sleep number (look under About Phone) jumped back into the upper 90's as well (good), and it had been stuck at 0.
I use Device Info HW which SHOULD (but does not even with root enabled on it!) show it on the 3rd tab, System, for the value of Description, but mine keeps showing just a dash! You'll have to locate an app that reveals the installed firmware.
Are you in India?
Click to expand...
Click to collapse
I just checked on about phone, and deep sleep still at 0%.
I also fully charged it, and rebooted and wiped battery usage data, but still shows thousands.
I also get a dash in that app.
No, I'm not from India.
mierdaseca said:
I just checked on about phone, and deep sleep still at 0%.
I also fully charged it, and rebooted and wiped battery usage data, but still shows thousands.
I also get a dash in that app.
No, I'm not from India.
Click to expand...
Click to collapse
Look at the firmware link on crDroid again and try the A13 MIUI V14 firmware released on June 6. I installed it via adb sideload since my phone temporarily won't read my external SD card. I do not recall anything else to try. Good luck.
Sheist! said:
Look at the firmware link on crDroid again and try the A13 MIUI V14 firmware released on June 6. I installed it via adb sideload since my phone temporarily won't read my external SD card. I do not recall anything else to try. Good luck.
Click to expand...
Click to collapse
I flashed again via adb sideload, but still nothing. I even updated to the latest crdroid 9.5 build and still nothing
mierdaseca said:
I flashed again via adb sideload, but still nothing. I even updated to the latest crdroid 9.5 build and still nothing
Click to expand...
Click to collapse
Then you are not speaking about the RN11 spes. There is no 9.5 update for this phone. This forum is for RN11 spes. Look at Device Info HW again and find out what phone you are actually using.