yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] tobitege:
[MENTION=4804871]DerRomtester[/MENTION]: just some very happy feedback as a data point:

- MultiROM setup

- running Temasek v3 F2FS as primary (still on AK)

- v55(SM) (F2FS-packaged by [MENTION=5736293]fredzen14[/MENTION]) on current secondary ROMs "Resurrection Remix" and "SlimSaber" with intellimm gov. @ 1.72GHz (SD 2MB+fiops).

Since I have always installed 3C Toolbox and since a couple of days also Trickster Kernel Mod Pro, I'm in the process of testing further my setup to correctly enable intelliplug instead of MP etc. (just to avoid app clashes).

But, so far, I'm extremely happy with how everything works and a well deserved donation is coming soon... :)
[ONE Android Development] 530farm:
Just switched to intellimm governor. Don't have much battery feedback yet, but ui performance is very fluid
[ONE Android Development] S1ay3r666:
Stock settings and just switched to intelimm! About 2 hours of gaming still a good result!
[ONE Android Development] zaphodbeeb:
Tyr v55 as primary on multirom

Hi, I have been trying to get either the linaro and Saber versions of the Tyr 55 kernel to run as a primary rom using multirom. I have them both running as secondary roms fine, but even when I "swap" them to primary they fail to run and bork back to recovery. Im using Termasek v3.0 in f2fs mode. They seem to install perfectly fine. The only change I have made is the regular changes necessary to the fstab.:confused: Tyr 54 runs fine as a primary.
[ONE Android Development] DerRomtester:
Sry i dont know anything about multirom. Maybe sth is ****ed up with lollipop. Maybe someone who is using multirom is able to help you.
[ONE Android Development] Rycon33:
Der, I actually returned back to a normal F2FS setup(not Multi-ROM) and it's the same error as "permission denied" on logcat while stuck in bootanimation. I think F2FS works only with kernel on "permissive" mode.

Anyway, I still got the re-packed v54 working fine here.
[ONE Android Development] cerealguy:
Linaro or Sabermod version? :)
[ONE Android Development] zaphodbeeb:
It also fails as a stand alone with f2fs regardless of recovery so it can't be multirom related issue.
[ONE Android Development] DerRomtester:
Hmm weird. I will change selinux to permissive again in next version.

Or if you have time you can do it yourself in the ramdisk: https://github.com/DerRomtester/ramdisk_one_plus_one/commit/9ecbedca29adbb1a7e5d50393ef7c58222004674

split_img/boot.img-cmdline

I dont know what the problem could be. I can upload a f2fs version if you want. The only thing i can do is editing fstab.bacon myself or change selinux. I could changes selinux to permissive but on kitkat enforcing worked fine for me. But it is christmas and i am busy at the moment dont expect it this week.

There are also some problems with my test kernel i am testing at the moment. I dont know if these reboots are kernel or rom related. I need some testers just pm me if you are interested in.

P.s.

Added a donation link on the first page if you consider a small donation.

Kind regards

DerRomtester
[ONE Android Development] tobitege:
[MENTION=4804871]DerRomtester[/MENTION]: the donate link works (sooner than expected ;) ) ... 65578532EX719151M :D :D
[ONE Android Development] DerRomtester:
Thank you very much. I really appreciate your donation. :D
[ONE Android Development] Rycon33:
I don't know if I'm doing this correctly but I tried this:

Edited the bootimg.cfg

From:

bootsize = 0x79e000
pagesize = 0x800
kerneladdr = 0x8000
ramdiskaddr = 0x2000000
secondaddr = 0xf00000
tagsaddr = 0x1e00000
name =
cmdline = console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3

To:

bootsize = 0x79e000
pagesize = 0x800
kerneladdr = 0x8000
ramdiskaddr = 0x2000000
secondaddr = 0xf00000
tagsaddr = 0x1e00000
name =
cmdline = console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.selinux=permissive

Afterwards, also edited fstab then repacked.

Installed but same error on bootanimation like before:

- exec '/system/bin/sh' failed: Permission denied (13) -

I guess I'll stick with v54 atm while waiting for your next release. :D
[ONE Android Development] DerRomtester:
This is correct. Now selinux is permissive on boot. If the new kernel is working without any problems i can realease on friday. :)

Edit: more than 300 downloads (linaro and sabermod)

Guys you rock. Thank you very much for using my kernel.
[ONE Android Development] Rycon33:
Using Tyr v54 on my F2FS, here's another configuration where you guys music lovers like me will have a smooth music playback. And mind you, my music files are high resolution(FLAC format).

MSM_hotplug with minimum 2-cores at anytime.

From the graph, the darker area is when my phone is on screen-off. You can see that it still maintains the two-core hence the music playback is very good.
[ONE Android Development] DerRomtester:
V56 will have many new f2fs commits inside. If i have time i will upload 4 kernels on next release.

2*f2fs

2* normal (latest linaro and sabermod of course)
[ONE Android Development] zaphodbeeb:
Hi,

got it sussed. Thanks for your help. Goes like stink and seems to run on little battery.
[ONE Android Development] Rycon33:
Mate, care to share the modified Linaro v55 for F2FS. I didn't have any success modifying it.
[ONE Android Development] zaphodbeeb:
Sure, try these.

fstab

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait

/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbdisk:auto

and also (for the cm12 selinux prob) add

androidboot.selinux=permissive

to the end of the boot.img-cmdline file and repack.;)
[ONE Android Development] Rycon33:
^^ Thanks

That's what I did already but never managed to get it past the bootanimation still. Must be the tools I'm using.
[ONE Android Development] zaphodbeeb:
are u linux? If so I use this.

its ok but has one little prob. Its not very good at cleaning itself after you have used it, so the purge it I just "bash unpackimg.sh" without a file, you get a page of error but its cleaned the old files out. If you forget it causes pain and woe.
[ONE Android Development] Rycon33:
Using Ubuntu, going to try it. Just noticed the tools I'm using, the dt.img is missing so that explains the lower boot.img size on mine.

Going to try the tools you posted. Thank you.

EDIT: Got it working now using the same tools I'm using, just another facepalm moment. Thanks Der and Zap for the guidance.

https://www.dropbox.com/s/o1unhavjdbmictv/Screenshot_2014-12-23-10-07-58.png?dl=0
[ONE Android Development] EasyGoingXD:
[MENTION=4804871]DerRomtester[/MENTION] just a question so please dont hate me...i am going to upgrade to 5.0.2 today and my question is..do you have any update for today or tomorrow because your kernel sounds really interesting :)
[ONE Android Development] tobitege:
You can use the current versions on 5.0.2 without problems.
[ONE Android Development] EasyGoingXD:
I know but i am just asking the dev because if he will say that he will bring a new update lets say tomorrow i will wait for the newest one :)
[ONE Android Development] DerRomtester:
Just flash V55

No sry no new cm Kernel patches. Saturday new release.
[ONE Android Development] HaTrED_:
V55 is such a milestone mate! ;)
[ONE Android Development] EasyGoingXD:
Ok thank you :)
[ONE Android Development] DerRomtester:
Good news for cm11/cm11s users: i am currently working on anykernel ramdisk and kernel booted up fine (thx to [MENTION=3685904]ak[/MENTION] for his source.) New kernel will work on cm11/cm11s and cm12.
[ONE Android Development] ak:
You have finally bring up the future [emoji12][emoji12][emoji12]

Sent from my A0001
[ONE Android Development] S1ay3r666:
Linaro
[ONE Android Development] DerRomtester:
Merry Christmas from Germany :D
[ONE Android Development] gianton:
Merry Christmas everyone, wishing you the best from Greece!
[ONE Android Development] pa.pn2:
Flashed linaro 55.what a great kernel. Ultra smooth and bat friendly

Ill stay here. Merry Christmas to all:)
[ONE Android Development] TheQuarterMile:
Truck load of governors in the kernel but I guess only a few among them seem to be popular.. Staring of with Intellimm Just flashed the kernel :)
[ONE Android Development] azsl1326:
Trying your kernel for the first time on Temasek's F2FS ROM (zaphodbeeb). Really like the amount of customization available in Synapse. Very nice.

Think I will stay awhile :)
[ONE Android Development] nikeman513:
What's the best governor? I use Allucard and runs great, but battery life could be better (and has been).
[ONE Android Development] OmegaBlaze:
Ondemand or Smartmax.. Really depends on what your doing though.

Those two are the best for smooth scrolling in my opinion.
[ONE Android Development] pa.pn2:
Indeed

I use smartmax with fiops 1024 and its amazing
[ONE Android Development] OmegaBlaze:
Anyone know why I can't flash TYR on any of the latest Cm12 Roms?

TWRP will flash the kernel successfully in recovery, but when the rom boots, its still stock kernel.
[ONE Android Development] DerRomtester:
Are you sure? Settings Kernel Version?

You have to restart Synapse.
[ONE Android Development] OmegaBlaze:
v55... nOOB mistake on my be half.

I restarted synapse and everything is good now :good:
[ONE Android Development] SchmilK:
I noticed the ukm unintstall script did not remove the files in /system/etc/init.d or /system/addon.d
[ONE Android Development] DerRomtester:
To use f2fs with my kernel you have to follow these steps

1. Download latest CM nightly

2. Download my kernel zip file

3. Unpack the boot.img of my kernel

4. Replace fstab.bacon content with this one

5. Repack the boot.img of my kernel

6. place it into the the rom you want to flash

7. than follow step 9 on the link below

http://xdaforums.com/oneplus-one/general/howto-f2fs-filesystem-t2857139

That should work. Anyone tried that?
[ONE Android Development] Setting.Out:
Yes, but with Mahdi rom... ;) and it's running great!!.. Way too early for battery life, but stability is much improved.. :)

---------- Post added at 05:03 PM ---------- Previous post was at 05:00 PM ----------

I didn't check that, I just trusted the uninstaller, this may have been some of the problem?
[ONE Android Development] Setting.Out:
**update**.. Well my battery still hasn't died after 43hrs on, 11hrs screen on time and 12% remaining.. No reboots, and is silky smooth..

Thanks for build.. You're making it hard to want to flash anything else.. ;)
[ONE Android Development] OmegaBlaze:
Damnnn.. Still have the same ROM and settings that you posted above?
[ONE Android Development] Setting.Out:
For clarification on setup, I'm on 8/30 Mahdi f2fs conerted, this kernel, 1574/268 MHz using Fku to set per app frequencies to 1958/268 on XDA app and a few others that don't act smooth at the lower frequencies.. I use greenify and battery save mode for the screen off state that stops WiFi/data/GPS.. ;)

**

Here's a link to the screen shots.. :)

http://xdaforums.com/showpost.php?p=55215810&postcount=776
[ONE Android Development] DerRomtester:
Is normal Version booting up?
[ONE Android Development] Setting.Out:
F2fs version booted fine.. ;)
[ONE Android Development] patmannyc:
How will OTA updates work? I know I have to re-flash stock recovery but will I need to re-flash stock kernel? Sorry if answered before
[ONE Android Development] DerRomtester:
OTA updates for Rom?

Which Rom ?

F2fs or ext4?

If there is an Rom update flash Rom and after that the kernel
[ONE Android Development] patmannyc:
Stock, CM11s
[ONE Android Development] DerRomtester:
This kernel is not working with CM11s only for CM11 or other aosp or cm11 based roms.
[ONE Android Development] patmannyc:
Wow, I'm in the wrong thread. Sorry to waste your time, but thanks for the replies
[ONE Android Development] edgarf28:
I've flashed V4 F2FS version on the MIUI patchrom from 30-8 (CM M9 based ROM), everything is working (F2FS formatted) except Wi-Fi :( It won't turn on...

with the AK kernel Wi-Fi is working on the same ROM.

But I want to use this kernel, because it has the newer F2FS version.

Do you have any idea why WiFi isn't working?
[ONE Android Development] Setting.Out:
WiFi works on Mahdi...
[ONE Android Development] DerRomtester:
I did not update f2fs in the uploaded kernel.

Dont know whats wrong with wifi. Can you try to flash another kernel and check if wifi works?
[ONE Android Development] edgarf28:
Yes, Wi-Fi is working on the the latest AK nightly with the same ROM.

Can't test any other kernel since I'm using F2FS at the moment.
[ONE Android Development] Setting.Out:
You can test with this one too..

http://xdaforums.com/showthread.php?p=55020706
[ONE Android Development] edgarf28:
That one works also (WiFi)

I will try to make an Anykernel flashable zip of this kernel, and see if it then will work.

Will report here if that did work...
[ONE Android Development] Spaulding89:
[MENTION=4804871]DerRomtester[/MENTION] you post the wrong link in OP for the new version. This one is the correct: https://www.androidfilehost.com/?w=files&flid=23207

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Android Development] DerRomtester:
There are two links now take care :D

V55 and before

and V56 and higher (with anykernel ramdisk)
[ONE Android Development] Spaulding89:
Send you a pm in German. It's much easier :p

Sent from my lollipopped Bacon with loaded AK Kernel

Edit: this is what I get when I click on your link:
[ONE Android Development] truth77:
What rom were you experience reboots? Hope not temasek!?
[ONE Android Development] DerRomtester:
Ups thank you very much. Should be correct now.

My mistake i was logged in there.

I had reboots on all cm12 based roms. But you do not notice them becaue when the device reboots there is no vibration. I only see a wcnss and a modem crash in last kmsg and the device reboots.

At the moment i am running temasek last two days and everything seems to be fine.
[ONE Android Development] azsl1326:
Running v55 along with Temasek F2FS multirom v3.3.1 and getting phenomenal battery life - lost 2% overnight. Thanks!

So I decided to switch to v56 and followed your instructions but I must be doing something incorrect as I got a boot loop. I flash the ROM, then v56 along with gapps, etc. Rebooted and I get the bootloop. Is this correct?

Thanks!!!
[ONE Android Development] DerRomtester:
Which kernel is inside the Rom?
[ONE Android Development] rani9990:
May I ask what settings you used to attain that battery?
[ONE Android Development] azsl1326:
v55 Linaro (https://www.androidfilehost.com/?fid=95864024717069660)
[ONE Android Development] DerRomtester:
Do not flash over V55. Because anykernel ramdisk does not support lz4. Ask your Rom dev for another f2fs kernel.
[ONE Android Development] parth132:
If I m using v55,

SO now i have to again full wipe and install rom , Gapps and v56

Is there any other way then full wipe ?

i Dont want to do full wipe and install rom

Thanks
[ONE Android Development] DerRomtester:
No just dirty flash your rom and after that my kernel. This will take 3 mins.
[ONE Android Development] parth132:
aha great :) Thanks :) ;):)
[ONE Android Development] hewlett2008:
V56 works great on KitKat Slimsaber! Thx
[ONE Android Development] chikiro:
I used it right now(v56) working great on cm12 daily ?
[ONE Android Development] azsl1326:
Okay, so I could use stock or AK68. Will either of these work?

---------- Post added at 07:14 PM ---------- Previous post was at 07:08 PM ----------

Got a random reboot on v55

Last_kmsg:

https://app.box.com/s/dbkd0lsq7ivsfjo16r66

Logcat:

https://app.box.com/s/ha37o9g202dmg7wigsj3
[ONE Android Development] DerRomtester:
These reboots are Rom related. Yeah just flash over ak but clean init.d
[ONE Android Development] Svid:
Using the kernel for like 5 hrs on Candy5 RC, works solid.
[ONE Android Development] azsl1326:
This worked. Thank you!
[ONE Android Development] Rycon33:
Der, not sure if it's kernel related or ROM or other things but I encountered sudden reboot just now. Kernel on default, I didn't touch anything on synapse. Attached last kmsg.

http://www.mediafire.com/download/qx34f3d7597wgd3/last_kmsg
[ONE Android Development] Fenvarien:
The kernel is working rockstable here with Temasek's ROM. I'm using V56 Linaro version with moderate UV (-65mv) and interactive/bfq.
[ONE Android Development] gianton:
Rock stable here too with msm hotplug/smartmax/bfq -50mV UV and over clock at 2726MhZ.

V56 linaro on temasek latest build.
[ONE Android Development] hewlett2008:
One little issue with V56: sound over earphones is poor....KK Slimsaber
[ONE Android Development] gianton:
I can confirm this too, settings stick but quality of audio over headphones is not good.
[ONE Android Development] DerRomtester:
I will check that but i can't promise anything. We have two options.

Faux sound (does not stick)

or franco sound
[ONE Android Development] Alin CG:
No sound is better :D:)). It will definitely work :D
[ONE Android Development] gianton:
Sound in boeffla kernel is the best for me, don't know if you can implement it in yours.
[ONE Android Development] Svid:
Had the same issue this morning. Sudden reboot on Stock settings (Didn't changed anything in Synapse).
[ONE Android Development] DerRomtester:
I can implement but which app should we use for that ?

boeffla app does not work for my kernel.
[ONE Android Development] gianton:
Yes you're right, but even with default settings in boeffla kernel the sound is brilliant. Maybe faux sound eventhough not sticking is superior to franco's regarding headphones playback.
[ONE Android Development] DerRomtester:
Sry guys at the moment i dont know a solution for that.

I already have an idea. It could be a cm12 rom problem.

I am currently running cm11 nightly and not a single reboot so far. I will keep testing and report back. Anyone running this kernel on cm11? Any reboots on cm11 or cm11s so far ?
[ONE Android Development] Rycon33:
Flashed awhile ago. I'm going to have two weeks to test your kernel on CM11s as I'll be needing my phone for lots of quick photo shots during my vacation with my family.

Having a time off away from CM12.
[ONE Android Development] DerRomtester:
Sry i am a bit confused now. Was your reboot on cm12 or cm11s ?
[ONE Android Development] Rycon33:
My reboot was on CM12.

Then only awhile ago I returned back to CM11s in preparation for my vacation as I need a more stable ROM when away from home for long.
[ONE Android Development] Svid:
Might be an ROM issue.

On CM11S not a single reboot aswell.
[ONE Android Development] HaTrED_:
Haven't tried v56 yet but I've been running v55 since it's first day under Temasek's rom and without a single reboot... None! Zero! Null!

I think that for now I'm just gonna stay right there...
[ONE Android Development] truth77:
Yup! [MENTION=4804871]DerRomtester[/MENTION], think you can revert some and just give hotplug & gov updates? you're probably already in the process of doing that lol.
[ONE Android Development] DerRomtester:
At the moment there are no hotplug or governor updates.
[ONE Android Development] vikrant82:
Coming from ark kernel. I have been testing this now and then and it's starting to look very solid (and performant). Only thing holding me back now is low headphone sound. I have been testing V56Linaro on CM12 temasak nightlies. Any workarounds ? Thanks again!
[ONE Android Development] DerRomtester:
What do you mean with low headphone sound ? Not loud enough or bad ?
[ONE Android Development] vikrant82:
The sound output from headphone jack is very low. It doesn't seem bad. It's okayish if I bump the volume from Synapse (but that distorts it a bit).
[ONE Android Development] Rycon33:
Just wanna say that it's been pretty solid on CM11s. 29 hours uptime and hasn't encountered any issue like sudden reboot or something.
[ONE Android Development] gb_Texas:
awesome, and thanks

running your v56

started on v55

very fast and efficient

thanks for sharing.

Running on TeamBliss Blisspop v1.5 now... screams

again, thanks.
[ONE Android Development] DerRomtester:
Yeah me too 30 hours uptime and no single reboot. I think we can say now that these reboots are cm12 rom related.
[ONE Android Development] azsl1326:
Random reboot on Temasek 3.3 with 56 linaro. Last_kmsg attached.

https://app.box.com/s/zzc1ogbf5d91letarp34
[ONE Android Development] DerRomtester:
Like i said few posts before. I am pretty sure that these reboots are rom related. If you need a stable device use cm11 (like me) or cm11s.
[ONE Android Development] tobitege:
Looks like modem panic, not kernel?
[ONE Android Development] DerRomtester:
Yep sth with modem and wcnss (wifi driver)
[ONE Android Development] azsl1326:
Was off WiFi for an hour and kept getting reboots when I was on data. Back on Wi-Fi now and no reboots.
[ONE Android Development] erad1:
Or v55 and under when using CM12?!
[ONE Android Development] DerRomtester:
No V55 wont fix any problems that are rom related. CM12 seems to be buggy at the moment still not released. CM11/CM11s = stable

CM12 = not stable and buggy
[ONE Android Development] adinkwok:
[MENTION=4804871]DerRomtester[/MENTION] Your disclaimer in OP is incorrect!! Warranty ain't void :silly:. Great kernel btw
[ONE Android Development] tobitege:
[MENTION=4804871]DerRomtester[/MENTION]: I'm running v55 on multiple roms (MultiRom) since it came out and have had only a single panic screen. Great work!
[ONE Android Development] parth132:
Thank you

Using v56 from 2 days on cm12 temasek v3.3

Not a single reboot, working good

Great battery life

All settings are stock, didn't installed synapse
[ONE Android Development] HaTrED_:
I'm going migrate my setup to v.56!

Gentlemen, start your engines!!
[ONE Android Development] [zozi]:
This is my results using your kernel

All stock no tweaks only with one charge... And i flashed the kernel when my batterry is in 60%

Tonight i will do a full charge and see the results with 100% full battery and using the kernel

And using blissrom

Good bless you and keep the amazing work i ser here!
[ONE Android Development] parth132:
So after one cycle of full charge 100%

1 day 20 hours passed

Screen on time 5 hours 15 minutes

Still 15% left

Thanks :)
[ONE Android Development] DerRomtester:
Wow Guys impressive results. :)
[ONE Android Development] [zozi]:
More then 5h of SOT is my goal and i think with this kernel is not hard! :)
[ONE Android Development] OmegaBlaze:
Sooo close to hitting 50k on Antutu with your kernel using stock settings.

Governor: Performance.

I/O BFQ w/ 1536 read ahead time.
[ONE Android Development] LeroViten:
Anyone's using v56 with LS LP v.4.0 ROM? ??
[ONE Android Development] [zozi]:
I saw today, my wifi disconnects after a while the display is off! is related to kernel?
[ONE Android Development] OmegaBlaze:
ROM related. I've used this kernel on several lollipop ROMs with no problems my friend.
[ONE Android Development] TeChNoC4AzY:
Does this kernel have oc support?
[ONE Android Development] DerRomtester:
Yeah CPU OC only for now. Next time use search function V56 Changelog :D
[ONE Android Development] TeChNoC4AzY:
Link?