[DISCUSSION][4.3] Knox Bootloader - Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve

As most users know, people who flashed Sammy's 4.3 stock with ODIN have the infamous and (yet) unremovable Knox bootloader. This bootloader is known for causing numerous FC's, freezes and random reboots to people who flash custom roms/kernels.
For me (and for most users, I believe), the custom roms/kernels are the main reason why I love Android (and xda too), thus the Knox bootloader has became one hell of a headache for me and other people who unfortunately have been naive enough to flash stock 4.3 in the early days.
It doesn't matter if we have flashed the Knox bootloader by oversight, or just because we didn't know it was included in the stock 4.3 (as the i9300 stock 4.3 was Knox free). What does matter, is that many people are now having problems in enjoying their favorite custom roms and kernels thanks to this evil invention by Samsung.
Therefore, and as I didn't see any thread like this one, I created this thread so we can discuss what we can do to, at least, minimize the problems cause by this bootloader. I am not even dreaming with restoring our warranty. At this moment, I just want to peacefully enjoy the custom roms and kernels that the great developers of xda release for our beloved I9305.
Although I haven't seen many developers talking about this problem in our device's threads, I noticed that some have already tried to trick the bootloader and avoid the FC's (like @Hbohd, for example). However, I think that this is a huge task and should be done with the help of everyone. I know by first hand that we have many talented developers working for our device (and for others too) and I'm sure that we, united, could, at least, try to do something about this and teach Samsung not to mess with our devices. I have always stood for the policy that says "I've paid for my device, thus I should be able to do anything I want with it".
Note: If any of you developers have some idea but don't know how to test it because you don't have the Knox bootloader, I don't mind to test it on my I9305 (and I'm sure that other users don't mind too). I'm using Alliance ROM v2+ with Boeffla Kernel v5.1+ and Knox bootloader.
Let's start the brainstorming: (I warn you guys that I don't know much about Android developing, so please bear with me if I say any stupidity)
- As we know, our brother i9300 doesn't have Knox included in stock 4.3. As one the main differences between I9300 and I9305 is the RAM, maybe this Knox thing is something that uses some RAM?
- I can reproduce a FC that only happened to me since I have Knox (I am supposing that Knox-free 4.3 users don't have this FC): everytime I benchmark my I9305 with AnTuTu, it FC's in the 3D test. Always. Maybe Knox is related to Mali drivers?
- Can we trick the Knox bootloader by changing SELinux status or Samsung root restriction status? @Hbohd already tried something like that but it didn't seem to be conclusive. But I guess that at this point no possibilities should be eliminated.
- And what about restoring the old bootloader from 4.1.2? We already know that restoring previous nandroid backups or flashing stock 4.1.2 from ODIN are useless...
So, what you guys think?
Please, be free to say anything you want, as long as it is on topic. In my opinion, we are currently far away from the solution so any help is welcome

I have Knox and running cm 11 no problems here..
Flash counter is at 6 maybe its The boeffla ?
Tested antutu no problems here
Sent from my GT-I9305 using xda app-developers app

toeterbaas said:
I have Knox and running cm 11 no problems here..
Flash counter is at 6 maybe its The boeffla ?
Tested antutu no problems here
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, that's a surprise to me, thanks for informing.
Regarding what you said, it seems that Knox only brings problems when you use a custom stock based ROM or Kernel (or both).
However, you (and other people who have Knox + non-stock ROMs) would still benefit from a possible solution that would revert our bootloader and restore our warranty. If that is ever possible

My counter is on 4 but for knox there is a special/ extra counter.
Maybe some modders can try let the boot loader think that the
moded kernel is an original stock kernel?
name installation scripts with original kernel letters
and is it possible to make the modded kernel with same filesize
like stock kernel?
regards
sonic76

I think is custom kernel wich causes all your troubles . I experienced same problems , even network signal loss with custom kernel .
Lately I am using kenar2's deodexed , rooted rom with kernel replaced to the original . I have no problem and battery life is great . I uninstalled all bloat including Knox software .
Let's give custom kernels some time to mature and I think we can continue to use them and custom roms like we used to do.
Of course we have to live with voided warranty .

I do use a custom ROM.
Its cm 11 but The kernel is standard and i have zero problems here.
I used other roms to no problems.
I had problems with stock ROM rooted and boeffla kernel.
So it must be The kernel.
I am not affraid of The waranty because never ever one of nu phones broke from Samsung and i had a lot of Samsung phones
Sent from my GT-I9305 using xda app-developers app

Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?

oswade said:
Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?
Click to expand...
Click to collapse
Did you tried different version of boeffla and the yank kernel to.

Why do you think you have knox bootloader? Even if you have it, question is does it work in a way it works on newer devices, where according to Samsung, bootloader uses eFuse to flash/check knox flag.
When you reboot into download mode, do you see knox flag mentioned. Counter someone above mentioned has nothing to do with knox, and can be set zero with triangle away, chain fire's app.
Sent from my GT-I9505 using Tapatalk

You cant set Knox to 0×0
Only ROM counts :thumbup:
Sent from my GT-I9305 using xda app-developers app

toeterbaas said:
I do use a custom ROM.
Its cm 11 but The kernel is standard and i have zero problems here.
I used other roms to no problems.
I had problems with stock ROM rooted and boeffla kernel.
So it must be The kernel.
I am not affraid of The waranty because never ever one of nu phones broke from Samsung and i had a lot of Samsung phones
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
On AOSP roms there are no problems. They appear on 4.3 Samsung Stock roms + Knox bootloader + custom kernel.
oswade said:
Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?
Click to expand...
Click to collapse
Thanks for your input, that is something new man !
In fact, I have just seen a new sourcedrop for our i9305 - might be interesting!!!

Hbohd said:
Thanks for your input, that is something new man !
In fact, I have just seen a new sourcedrop for our i9305 - might be interesting!!!
Click to expand...
Click to collapse
no worries .
Nice, i hope the sources provide us with an easy fix!

Post some of the dumpstate_app_error.txt.gz from data/log after the fcs
Sent from my GT-I9305 using Tapatalk

Edit: forgot to turn on logger

Goldie said:
Post some of the dumpstate_app_error.txt.gz from data/log after the fcs
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
Here is mine, right after AnTuTu FC in 3D test.
I rebooted the phone, forced the FC by doing a 3D benchmark and then uploaded the file. I hope it is what you want

Thanks but you need to turn logging on in boeffla settings first
Sent from my GT-I9305 using Tapatalk

Goldie said:
Thanks but you need to turn logging on in boeffla settings first
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
You're right... My bad! Here it is again, same procedure...

I have an idea how to restore knox-free bootloader, maybe all we need is unbrick SDCARD (like for i9300 http://forum.xda-developers.com/showthread.php?t=1916796) made on i9305 with 4.1.2 room. I have heard of several cases where I9305 came into SDCARD mode and overwrite curent bootloader with data of the sdcard. For go in to SDCARD mode they hold volume up + volmne down + home + power in the same time.
All I need is dd image for unbrick SDCARD for i9305 and I will try.
Sorry for my english.

guys try out boeffla beta 12. i think it has fixed the knox bootloader problems but itll be good if someone else can confirm.

oswade said:
guys try out boeffla beta 12. i think it has fixed the knox bootloader problems but itll be good if someone else can confirm.
Click to expand...
Click to collapse
I have Internet FC, Gapp's FC, my mobile was 2 times down means display black and mobile won't wake up,
no reaktion by long press power button so i have to pull out the battery....!
I have boeffla beta 12 with no tweaks over boeffla app!
regards
Sonic76

Related

[stock firmware][D80020c] recovery friendly D80020c

This is for D800 (AT&T LG G2) users ONLY.
This package will update a phone with D80010d firmware to a "mixed" firmware that boots normally to D80020c (kitkat), but retains the older boot loader and compatibility with loki patched custom recoveries. The "normal" boot is 100% unmodified stock.
This "mixed" firmware is currently the only known way for a stock D80020c (kitkat) system that also allows custom recovery.
What's installed:
rpm, tz, modem, and system partitions from the stock D80020c (kitkat) LG G2 firmware.
LG's D80020c kernel, recompiled by @Savoca, and made compatible with the D80010d bootloader.
That will leave your existing D80010d boot loader (aboot) intact, as well as whatever custom recovery already installed.
This firmware package will (or at least should) refuse to install on ANY firmware other than the D80010d firmware. Please don't reply to this thread if you are using anything else. (That was as polite as I'll be on that issue...)
I STRONGLY suggest doing a full wipe on your device after flashing this. You don't have to, but it'd be a really good idea...
This is NOT my software. This is 100% LG's software and firmware. Don't ask for support in this thread. It won't be provided.
Instructions:
Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
Root the device and install recovery (recovery is required, root is not.) This is a link for rooting instructions. While you are welcome to use CWM for your recovery, this is a link for installing TWRP recovery. (Since cyanogenMod took freely given contributions to their codebasse and went private/for-profit, I have a personal bias against them - so my personal recommendation is for TWRP.)
Copy the d80010d_to_20c.zip package linked below to your phone.
Reboot into recovery and install the d800_to_20c.zip package.
Optionally, also install a superSU or other root package.
Optionally, but suggested, Perform a "factory reset" on your device.
Download Links:
The main package (about 1.7GB): Dev-Host (md5: 7cfe7de4ab31f727b72178b8fb618fd3)
SuperSU: Direct from Chainfire's webpage
Credits:
Several people spent countless hours working on finding a way to get recovery working with LG's kitkat. The kernel used in this package was made by @Savoca - who used the solution found by @JackpotClavin. Others involved are (as far as I'm aware) @AndroidUser00110001 and @jakew02. Of course, @Chainfire for the 'su' package.
Source:
All the images in the recovery package are completely stock with the exception of the kernel and kernel modules. The kernel is modified and recompiled with only the following patch: https://github.com/JackpotClavin/an...mmit/7b6187a0e5fb8ca59888cacf5f5b863baa8d1064. (The installer overwrites the kernel images in /system with those from the kernel compile.) The base kernel source is found on LG's opensource website under the D800 heading.
May 2014 Update:
I'm no longer able to tinker with my G2. My wife took it from me (for her own use), and she gets angry when I mess up all her settings.
(I ended up getting a HTC One M8 to tinker with.)
While I'll leave the thread unlocked so users can assist each other, please don't expect prompt responses from me or maintenance.
switched main package link to dev-host
added "source" section.
As soon as it's done downloading I will let you know that it works unless someone beats me to it that is
EDIT: Finally finished downloading I already flshed back to 10d rooted installed recovery and am now installing kk.zip
Re-Edit: just finished installing also just so you know flashing system only took about 2mins a little bit over that in terms of seconds anyways everything seems to be running fine ill report back tomorrow when its not 1am my time and can test things more thoroughly but I can confirm that everything flashes like its supposed to and also I like the little check you added where it says d80010d bootloader good!
Sent from my LG-D800 using xda app-developers app
XxZombiePikachu said:
... and also I like the little check you added where it says d80010d bootloader good!
Click to expand...
Click to collapse
It's actually checking that loki_patch reports a d80010d bootloader. If not, it'll abort flashing.
Thanks man, now i have kitkat with root and recovery (D80020c)
Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2
DowntownJeffBrown said:
Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2
Click to expand...
Click to collapse
This is the only way for now to have a recovery on kit Kat
Sent from my LG-D800 using XDA Premium 4 mobile app
Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?
FlyingColors said:
Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?
Click to expand...
Click to collapse
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.
Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?
garyd9 said:
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.
Click to expand...
Click to collapse
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.
FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.
Click to expand...
Click to collapse
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app
XxZombiePikachu said:
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
more people asking questions that have already been answered. then when you point out that their question has already been answered they say they are trying to clarify even though it's already been clarified in the OP. it's a phenomenon on xda.
xLordNitro said:
Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?
Click to expand...
Click to collapse
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Click to expand...
Click to collapse
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.
garyd9 said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. So i decided to rewipe everything, ReFlash stock Jellybean and reroot and do everything all over again and then i flashed this, same problem. Bluetooth is completely off, i rarely use it. It went from 100%-60% within 1 hour of just standby, didnt even use the phone. Look at the stats and Bluetooth has been keeping the CPU awake the whole time. So i did what someone suggested, turned it on and off and rebooted. Same problem. Went back to JB, no issues.
Click to expand...
Click to collapse
xLordNitro said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. So i decided to rewipe everything, ReFlash stock Jellybean and reroot and do everything all over again and then i flashed this, same problem. Bluetooth is completely off, i rarely use it. It went from 100%-60% within 1 hour of just standby, didnt even use the phone. Look at the stats and Bluetooth has been keeping the CPU awake the whole time. So i did what someone suggested, turned it on and off and rebooted. Same problem. Went back to JB, no issues.
Click to expand...
Click to collapse
after you went back to jb then rooted and installed custom recovery then flashed this firmware, did you do a factory reset upon first boot? meaning did you get past the initial set up then go to settings/backup and restore and reset the phone? if not then that could be your problem. the factory reset does indeed reset everything after you initially install kitkat. it worked for me also, i had mms issues every time i initially installed kk. after a factory reset the mms is resolved.
Yep, did that. Still same problem. So im assuming its something to do with the files themselves, and maybe the fixes that are being done to keep recovery. I dont know. But im back on Jellybean for now, i cant let my battery take that huge a hit.
xLordNitro said:
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. ... . It went from 100%-60% within 1 hour of just standby, didnt even use the phone.
Click to expand...
Click to collapse
Wow. That's REALLY strange. I wonder why it's impacting only some users, and not all. (It would make sense that if it happens when BT is turned off, it would impact 100% of users.) Something else that's odd is that it happens with this, but not with the OTA. Even more strange is that it happens with that other "stock kitkat" firmware, as that essentially is the OTA with zero changes - it's even using the OTA provided bootloader and kernel.
I'm not really sure how to guide you on troubleshooting this. Anything I might suggest would take a few days of reverting and flashing various things, and I somehow doubt you'd want to spend the rest of your life doing random experiments for me. Perhaps you should try that poweruser firmware with things added one at a time - as you suggested.
Take care
Gary
garyd9 said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.
Click to expand...
Click to collapse
Too late, I've already installed it and successfully have Kitkat. Even though you probably don't like me, thank you.
Problems going back to other rom
I was running flex rom before end flash kk end the motion sensor calibration work but doesn't work on my other roms only work on kk only. please fix

[General] Lollipop Information Thread S4

General Lollipop Information Thread​
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
LastStandingDroid said:
General Lollipop Information Thread​
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
Click to expand...
Click to collapse
Can u port soundcamp to s4 ?
i've flashed cf autoroot and it works perfectly
i did a completly downgrade,also bootloader and no issues
Sent from my GT-I9505 using XDA Free mobile app
i have installed official lollipop 5.0.1. If I root my phone, I will be able to flash official updates from samsung in the future? or I won't because of triggered knox
ViPER4Android
I managed to install Viper as system app but problem is How do I Activate it? In Sound settings there is No Music fx, (although it's installed), so I don't have the option switch Viper on, let only see Adapted Sound and in custom profile doesn't select it either. Am I missing something or is it because this update is so terrible
great info Droid! saw this thread in your signature
Revert from LL 5.0.1 to KK 4.4.2 is possible even if you flashed the Bootloader!
Personaly tested and working like charm!
No IMEI lost, no issues soo far found....
re
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Xain47 said:
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Click to expand...
Click to collapse
yeah..they are the same but i don t know if modems are diferent. i think you should not flash i9506 on E330s

[BS_FREE_Lollipop_5.0_Rom_BOK3_Based]

This is a modified version of @jrkruse stock BOK3 deodexed ROM with all(or most) of the stock BS removed.
This BS_free ROM does not have two different versions like his previous build. I left only the Samsung apps needed for UPSM and HD calling to work.
INSTRUCTIONS:
I've included the links needed if you want to use xposed and Viper4Android. If you chose not to use these features, then skip them in the flashing process.
I personally prefer using safestrap when clean flashing a ROM, but you can use flashfire if you must.
1) WIPE EVERYTHING!
2) Flash No_BS ROM
3) Flash Extra toggles
4) Flash No_Bootloader_Rooting_Tools_For_S5_Lollipop_V3.zip
5) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
6) Flash Viper Policy
7) Flash Viper4Android
8) Flash BOK3 Firmware without bootloader
9) After first boot, open up Viper4Android and install the driver. Note: Sometimes it takes 2-3 times before the driver will install.
I have confirmed that @jrkruse 5-way reboot with Safestrap works on this ROM!!! If you want to use it, add it to the end of the flashing list. 5Way_Safestrap_Reboot_PM. As a side note, if you use 4-way reboot in Wanam Xposed, then that feature needs to be disabled for 5-way reboot to work.
The ROM should boot in about 8 minutes. The music app will force close everytime the device reboots, but it does work normally.
Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
NO_BS_BOK3_ROM_DEODEXED.zip
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.
Update: NO_BS_BOK3_ROM_DEODEXED_V3.zip is now available. The flashing process is the same. I updated busybox and removed SBrowser. I also implemented the signature verification fix by @jrkruse, along with default animation scales set to 0.5x.
Update: NO_BS_BOK3_ROM_DEODEXED_V4 is now available. The flashing process is the same. I updated all apps, except for YouTube(xposed purposes). I added the missing VPN apk as well. Let me know if there is any other issues with VPN related settings.
Update: NO_BS_BOK3_ROM_DEODEXED_V5 is now available. The flashing process is the same. I updated all apps. I added the headphone app notification, voicenote, and SPrintSpooler. I don't use voicenote or SPrint, so let me know if there are any issues with these apps.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.
I am looking forward in seeing how this Rom is doing.
Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?
Snoopy679 said:
Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?
Click to expand...
Click to collapse
First and last will do just fine.
Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.
jjdavis699 said:
Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.
Click to expand...
Click to collapse
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?
CVertigo1 said:
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?
Click to expand...
Click to collapse
That's the one.
I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay
CVertigo1 said:
First and last will do just fine.
Click to expand...
Click to collapse
do i need to do a clean install or just flash over @jrkruse work that i am currently using?
[VZW_Stock Based TW Rom][5.0 Lollipop BOK3 Build Deodexed] by @jrkruse ?
I dirty flashed this over his stock BOK3 and it worked, so you should be good.
CVertigo1 said:
I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay
Click to expand...
Click to collapse
I actually tried that already. It's honestly not great. Oh well. Maybe if I could figure out a way to strip 3minit...
I fell in love with motion features when someone stole my moto g and I had to pick up a Lumia 640. Great phone, but not an android
I'm on BS_FREE_BOG5_GOOGLE_V2_Deodexed and just updated with @jkruse New Root Tools For S5 Lollipop V6. Already enabled Lollipop Safestrap Recovery again and Flashed Most Current OG5 Firmware_No_Bootloader and current OG5_Kernel. Can I just use that and wipe everything flash this aside from 3Minit Battery without losing Root?
Sent from my SM-G900V using Tapatalk
Just to be clear, are you asking if you can run this on BOG5 firmware?
CVertigo1 said:
Just to be clear, are you asking if you can run this on BOG5 firmware?
Click to expand...
Click to collapse
No, I mean using the V6 Root Tools instead of the V3 as indicated in your directions...
Also, I'm hoping that with a new install I will regain ability to work with Accessibility Options in Settings.
Idk if it makes a difference but I have Original GS5 Rooted, never taken OTA, always ONLY used XDA sources for ROM/Firmware/Kernels.
Sent from my SM-G900V using Tapatalk
My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.
CVertigo1 said:
My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.
Click to expand...
Click to collapse
Ok but all the same, I'm trying to avoid another 300mb DL if I can. As long as it is the same stuff then that's all I need to know.
Sent from my SM-G900V using Tapatalk
Version 2 is now available in the OP.
Universal BS ROM
i would like to know if this BS rom is able to be used on any S5 Carriers or would you consider it in the near future making this a universal rom for other carriers to please. my wife is a T-mobile person and she love the work that you have done here. and is asking me to ask this question. i thank you in advance for your reply.:good:
Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.[/QUOTE]
How did you remove the verizon boot animation? id rather not flash this again cause i just got my stuff all installed.
CVertigo1 said:
Version 2 is now available in the OP.
Click to expand...
Click to collapse
I Flashed it last night with @jkruse's No Bootloader V6 Tools and it worked just fine. I also, noticed that my Accessibility Settings works now and a couple other things were fixed as well. I did have a hard time Restoring Poweramp Music Player - I had to reinstall from Play Store but otherwise seems to be working great!
Sent from my SM-G900V using Tapatalk

Working on a Root Tool for S7/Edge T-Mobile that fixes lag, overheat etc! (OnionRoot)

So I rooted my S7 edge tmobile multiple times on 6.0.1 and did lots of testing to push the device to its limits. I soon found out that the device lags like aids when you reboot when you have it rooted. So I'm pretty close to finishing a tool that fixes all those problems. ESPECIALLY when you reboot and the CPU governor switches to performance for no reason.
Have any suggestions on what to add to the tool before release let me know! Also when you are rooting it with my tool, it will install an apk called OnionRoot. This might be added or removed from the root tool idea. Its intent is to fix lag performance and overheating. This may just be a better way of rooting your S7 without lag and what not.
Also if you are experincing any problems I didn't list when you root with the current way by chainfire, let me know to try to fix it before release.
Awesome patiently waiting
Sent from my SM-G935T using XDA-Developers Legacy app
Good ish OP. Cant wait to try it out when it's finished. If you can, try to set it so we can update supersu and its binaries.
Fix the ENGBOOT so that the issues don't exist
Click bait
Sent from my SM-G935T using XDA-Developers Legacy app
so..basically the same thing we have already been doing with kernel aduitor to set the governor then lspeed, and sefix. got ya.
silentwind827 said:
So I rooted my S7 edge tmobile multiple times on 6.0.1 and did lots of testing to push the device to its limits. I soon found out that the device lags like aids when you reboot when you have it rooted. So I'm pretty close to finishing a tool that fixes all those problems. ESPECIALLY when you reboot and the CPU governor switches to performance for no reason.
Have any suggestions on what to add to the tool before release let me know! Also when you are rooting it with my tool, it will install an apk called OnionRoot. This might be added or removed from the root tool idea. Its intent is to fix lag performance and overheating. This may just be a better way of rooting your S7 without lag and what not.
Also if you are experincing any problems I didn't list when you root with the current way by chainfire, let me know to try to fix it before release.
Click to expand...
Click to collapse
The main purpose of your solution is to fix the lag and sluggishness we experience when we use the engineering bootloader to root. If your solution makes it so that we don't have to fiddle around using any other third-party apps and have our phones run fast from the get-go, then by all means please release it ASAP! Any other enhancements can be added in future updates.
uniphase said:
The main purpose of your solution is to fix the lag and sluggishness we experience when we use the engineering bootloader to root. If your solution makes it so that we don't have to fiddle around using any other third-party apps and have our phones run fast from the get-go, then by all means please release it ASAP! Any other enhancements can be added in future updates.
Click to expand...
Click to collapse
Pretty close to finish the basics. Its a tethered root for performance fix but will be untethered before release very close to finishing. I want to make the device run lag free. Thats the goal of this modded root tool.
I rooted my s7 edge many times and the one issue I always had after a few weeks of being rooted was IMS service issue even with the fixes it would still come up which then I had to turn off volte to make calls. If you can get that fixed it would be great. This was always the deal breaker that made me go back to stock.
HiGhDRo3o5 said:
I rooted my s7 edge many times and the one issue I always had after a few weeks of being rooted was IMS service issue even with the fixes it would still come up which then I had to turn off volte to make calls. If you can get that fixed it would be great. This was always the deal breaker that made me go back to stock.
Click to expand...
Click to collapse
I've never had a problem with the IMS service. What exactly happens? Can you explain? Also you're on T-mobile S7/Edge? What processor and android OS ver?
Hurry up man! Lol jk
Sent from my SM-G935T using XDA-Developers Legacy app
So I'm guessing this is basically chainfire's ENGBOOT method with fixes already built in? Would definitely be a nice thing to have, but an unlocked bootloader would still be endgame for us. Have you considered Xposed with this? Xposed makes the phones lag a lot worse than with just root.
silentwind827 said:
I've never had a problem with the IMS service. What exactly happens? Can you explain? Also you're on T-mobile S7/Edge? What processor and android OS ver?
Click to expand...
Click to collapse
T-Mobile s7 edge android 6.0.1. I would set up device as soon as root. All the available fixes and Would work fine for many weeks but then all of a sudden IMS has stopped and could not make or receive calls on volte. Would only work with volte off. Happened 4 different times so I stuck to stock. Now on final beta
HiGhDRo3o5 said:
T-Mobile s7 edge android 6.0.1. I would set up device as soon as root. All the available fixes and Would work fine for many weeks but then all of a sudden IMS has stopped and could not make or receive calls on volte. Would only work with volte off. Happened 4 different times so I stuck to stock. Now on final beta
Click to expand...
Click to collapse
Have you tried to restore to default settings with recovery AND flash AP, BL, CP, and CSC with odin? That should fix it. Maybe try OnionRoot, I dont know how you're rooting your device this might be a fix. I've never had that problem come across, I have the same exactly device.
silentwind827 said:
Have you tried to restore to default settings with recovery AND flash AP, BL, CP, and CSC with odin? That should fix it. Maybe try OnionRoot, I dont know how you're rooting your device this might be a fix. I've never had that problem come across, I have the same exactly device.
Click to expand...
Click to collapse
I tried it all. Went to stock and re rooted 4 times and always happened to me On 2 devices so I stayed stock at the end
HiGhDRo3o5 said:
I tried it all. Went to stock and re rooted 4 times and always happened to me On 2 devices so I stayed stock at the end
Click to expand...
Click to collapse
Try titanium back up and freeze ims service. I don't think that might help but it's worth a shot
CosMiiK said:
So I'm guessing this is basically chainfire's ENGBOOT method with fixes already built in? Would definitely be a nice thing to have, but an unlocked bootloader would still be endgame for us. Have you considered Xposed with this? Xposed makes the phones lag a lot worse than with just root.
Click to expand...
Click to collapse
Didn't mess around too much with engboot. I need to figure out how to fix it to make performance better and battery
ShrekOpher said:
Fix the ENGBOOT so that the issues don't exist
Click to expand...
Click to collapse
I will look into it more and try to solve the problem why the device lags due to engBoot.tar or whatever we call it lol.
CosMiiK said:
So I'm guessing this is basically chainfire's ENGBOOT method with fixes already built in? Would definitely be a nice thing to have, but an unlocked bootloader would still be endgame for us. Have you considered Xposed with this? Xposed makes the phones lag a lot worse than with just root.
Click to expand...
Click to collapse
No fixes in ENGBOOT yet, BUT there are solutions I am working on right now. I know the problem lies in ENGBOOT.tar. Right now the OnionRoot app fixes the governor on start up after a complete boot up sequence.
MorePAIN said:
Hurry up man! Lol jk
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Its released for testers now. OnionRoot early release for testers

Since Android 8.0 its lagging

Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT.
So i just let Google and Samsung restore all my stuff. Then i installed TWRP and root via the no-verity-opt-encrypt-6.0.zip and magisk v16.0.
After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags.
e.g. opening of Snapchat. Like it's closing so hard in background, that all services need to restart.
Instagram and OneDrive are shown many time as stopped working and i don't know why. Maybe Instagram caused by XInsta?
Okay i recognized OneDrive isn't even working anymore. Was already on Android 7 a problem. Does not seem to be compatible to something else.
You have any ideas or need any information? Let me know
try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.
achour7 said:
try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.
Click to expand...
Click to collapse
Antutu Benchmark gives me 164336 points, so it seems literally to be normally, but i know all loading times of Snapchat and Instagram and so on are so much longer.
I will try to flash it again and to start clean. Just the copying of the WhatsApp folder needs so much time.
So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???
CptDayDreamer said:
So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???
Click to expand...
Click to collapse
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3
CptDayDreamer said:
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3
Click to expand...
Click to collapse
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.
achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
achour7 said:
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.
Click to expand...
Click to collapse
Works it without problems? Bro do i just need the kernel or also like I found out this THE GALAXY PROJECT ROM ? It looks like TouchWiz ha?
I have stock phone without root and my phone is getting really extremely hot since it was updated to Oreo.
Even by doing something like being here in the forum is getting so hot that is uncomfortable on my hand
CptDayDreamer said:
Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT... After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags...
Click to expand...
Click to collapse
If on stock then resources being consumed with bloat. If issues began around installation of xposed wouldn't it make sense to uninstall modules and xposed and see if improved over the next day? Restoring apps and data and rooting and moding is a lot of stress on device all at once, then it gets so warm it starts to go glitch. I've been there too. Best thing is to let it sit 30-60 min after set up finishes to cool off. Reboot too once restored data completes.
Almost makes me miss the rip out and replace with cool fully charged battery days of my S4 [emoji91]
Sent from my SM-G930W8 using Tapatalk

Categories

Resources