What it meant to say was it will disable access to phone storage while its charging , and use kernel adiutor , it's much more easier to use [emoji6]
Sent from my Moto E using Tapatalk
[KERNEL][Uber-5.3] Clarity [r26][-O3][LP/MM]
- Thread starter rainforce279
- Start date
- Status
Sent from my Moto E using Tapatalk
That's what I wanted to know. And I use kernel adiutor only..?
Sent from my moto e ?
But the screenie you posted is showing trickster mod [emoji53] , anyways , please press the thanks if I helped you
Sent from my Moto E using Tapatalk
Cool , but you could have taken ss in kernel adiutor also right , why download this one [emoji6]
Sent from my Moto E using Tapatalk
Battery Life
Getting 4+ hrs on this phone after 2 years is pretty darn good
Getting 4+ hrs on this phone after 2 years is pretty darn good
Attachments
Nice!Getting 4+ hrs on this phone after 2 years is pretty darn good
What theme is that?
r24 up
bring up:
- Replace Faux Dynamic Fsync with Fsync control by Fransisco Franko.
- Merged to latest branch cm-13.
- etc.
Changelogs
Download
NOTE : if you coming from other custom kernel, please dirty flash you current rom. its for make ramdisk and everythings back to original, and will prevent unexpected bugs and problem.
CM-13.0/AOSP M = [ r24 - Release 2016-04-17 ] : Download Here Use Only for CM-13.0 and AOSP 6.0.x
bring up:
- Replace Faux Dynamic Fsync with Fsync control by Fransisco Franko.
- Merged to latest branch cm-13.
- etc.
Changelogs
Download
NOTE : if you coming from other custom kernel, please dirty flash you current rom. its for make ramdisk and everythings back to original, and will prevent unexpected bugs and problem.
CM-13.0/AOSP M = [ r24 - Release 2016-04-17 ] : Download Here Use Only for CM-13.0 and AOSP 6.0.x
After Installing this kernel everything was fine for almost 7 hours and then device randomly rebooted and device was not recognizing the adopted sdcard and device was factory reset. Dunno what went wrong. had same problem with r23 and now also with r24
ROM : Aicp 11 7th April nightly and also same happened on RR 5.6.6..
Eagerly waiting for reply
Edit : using Enforcing SELinux version..
Ways to. Reproduce the problem: install ROM move some apps to Adopted SD and install the clarity kernel..after sometime either it will randomly reboot. Or reboot the phone multiple times..after that all the data in adopted SD is lost and phone is factory reset ..plz help. Happened 3 times on this kernel ..working fine on stock kernel ...
i love this kernel very much !!
Last edited:
This happened to me on Cyanogenmod using stock kernel. I don't think it's related to Clarity.
If I'm not wrong the theme is 'fa - Layers Theme'
Check more on Play store. Its Free!
:highfive:Ways to. Reproduce the problem: install ROM move some apps to Adopted SD and install the clarity kernel..after sometime either it will randomly reboot. Or reboot the phone multiple times..after that all the data in adopted SD is lost and phone is factory reset ..plz help. Happened 3 times on this kernel ..working fine on stock kernel ...
---------- Post added at 12:01 PM ---------- Previous post was at 12:01 PM ----------
Thanks for the theme name !If I'm not wrong the theme is 'fa - Layers Theme'
Check more on Play store. Its Free!
There have been issues with data corruption when using certain newer versions of f2fs. We recently had a data loss disaster on the MSM8916 family when we tried to use the Linux 4.6 version of f2fs. It worked fine for me and some users, but many others ended up having data corruption issues after a few days and a few reboots. A similar problem occurred when I tried to use the Linux 4.3 f2fs on some builds of CM12.1 for lux last year. I've had issues with the Linux 3.10 ports of f2fs from Linux 4.3 and Linux 4.6. I've had good results with the 3.10 ports of f2fs from Linux 4.1 and 4.5. I haven't tried a recent backport for 3.4.x myself, but I've heard reports from a friend on another device of corruption for some users with the Linux 4.4 backport to 3.4. This kernel is using the Linux 4.4 version backported to 3.4.
I have not heard of any data loss instances on otus (where everyone uses just the Motorola f2fs used in CM13). So if you fastboot erase your userdata partition, then boot with the stock CM kernel installed, it would reformat your userdata partition with the f2fs version used by CM13. If you then stick with just the CM kernel (and your recovery isn't using a problematic f2fs - I haven't checked what your condor TWRP uses), then there should never be any data loss for anyone. Mixing old and new f2fs versions seems to be problematic, and some new versions cause more problems than others.
Last edited:
@squid2
Thanks for the clarification.
I will try fastboot erasing userdata partition. And booting with stock CM kernel installed.
And can you tell me how can I check which port of f2fs is twrp for condor is using ..( I am using official twrp 3.0.2)
Last edited:
@squid2
Can you please answer this.
Aicp and RR track stock cm13 kernel only and if I fastboot erase userdata and boot with either ROM.(as they track stock CM13 KERNEL), and then flash this kernel
There won't be any data loss.
Please reply!
Device needs to be revived and made available for daily use.
@rainforce279
Can you please answer this.
Aicp and RR track stock cm13 kernel only and if I fastboot erase userdata and boot with either ROM.(as they track stock CM13 KERNEL), and then flash this kernel
There won't be any data loss.
Please reply!
Device needs to be revived and made available for daily use.
@rainforce279
- Status
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone