Nopes
I dont know what happen, i left my phone idle overnight and when i woke up my phone just blinking led and wont wake (soft brick?). tried to force reboot but my phone didnt boot and stuck in oneplus logo. dirty flash make all normal again. for now still using stock PE kernel.
my device : dumpling, running PE plus a10, lazy kernel 4.4 stable
EDIT : just notice version 4.5, ill try it will give report back tomorrow if above issue still happen or not.
Alright I'm planning to return the underclock and the undervolt.I have returned to v.4.4 to try again. In the pixel experience, this time for lack of time, I have been 10% with wifi and the result has been very good. I am going to take a while and we will see if this is maintained low battery consumption.
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
I dont know what happen, i left my phone idle overnight and when i woke up my phone just blinking led and wont wake (soft brick?). tried to force reboot but my phone didnt boot and stuck in oneplus logo. dirty flash make all normal again. for now still using stock PE kernel.
my device : dumpling, running PE plus a10, lazy kernel 4.4 stable
EDIT : just notice version 4.5, ill try it will give report back tomorrow if above issue still happen or not.
in MSM X rom with version 4.5 i have the same problem. wont wake.
Please try the following if you encounter this problem.
1. Flash the kernel
2. Wipe cache and dalvik cache
3. Power off (Do not restart)
4. Turn on
This method works for me as I continuously test the kernel on my phone. I think one possible reason this soft brick situation occurs is that migrating from a non-LTO kernel to a LTO kernel breaks stuff, although I am not certain that's the case. Another one could be the changes I make in-between versions.
Regardless, I am still learning and I truly am trying to improve the kernel as much as I could.
If you are still interested, can you please try 4.7? I think I finally got rid of the faulty patchthanks for this sir. just suggestion to add this "fixing method" in the first page
How does this cause soft brick , Is this issue still present , i m thinking to flasb 4.7 version?ISSUES:
Soft brick problem possible solution: https://xdaforums.com/showpost.php?p=82201601&postcount=24
- I am fixing the problem and aiming to fix it in v5 or along v4 branch version.
ofc.. so i will try flash 4.7 over stock kernel first without wipe cache/dalvik. i'll give report again asap.If you are still interested, can you please try 4.7? I think I finally got rid of the faulty patch
I'm really thinking it's the LTO patches that I have which is far different from the other kernels here :/. Albeit I'll try to look for the issue still.How does this cause soft brick , Is this issue still present , i m thinking to flasb 4.7 version?
Edit :- i flashed v4.7 but it cause me soft brick got back to rom after flashing weeb kernel but i also lost dash charging on my rom
I am using derpfest rom.
I tried flashing kernel using your method.
Which rom are you using and lazy kernel you flashed?To date I am very happy with this kernel. It has been a long time since I have had a kernel that worked so well with my preferred ROM.
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
sorry.. but, my phone still got soft brick with test version 5.2. this time the issue comes while im using my phone.UPDATE: v5 is currently in the works.
So far:
- There's no soft brick
- It's much smoother and stable
The test builds are in the repo if ever anyone wants to try.
Current working version: Lazy-lto-test-v5.2
Here's an article regarding LTO:What do you mean by lto can I know , I m planning to flash latest test build on my rom.
Alright, I built a non-lto version compiled with Arter GCC. If it doesn't work, then it should be another issue.sorry.. but, my phone still got soft brick with test version 5.2. this time the issue comes while im using my phone.
/*
* Your warranty is not void.
*
* I am not responsible for bricked devices, dead earphones,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/