yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] CatAlex:
QS-N9005-LP-FINAL-OI1 + idleKernel-hlte-eur-6.5.4 (SELinux Permissive) = Viper4Android doesn't work.

With Audax Kernel 2.7 everything is OK/
[Galaxy Note 3 Original Android Development] jcadduono:
Have you previously flashed arter's kernel? Looking inside the zip file, I can see it replaces a bunch of the audio libraries in whatever ROM its flashed onto. These audio libraries and mixer path settings will still be there after flashing idleKernel. I am against using modifying ROMs and idleKernel will never replace anything except the boot partition where a kernel should be. I'm looking for some scenarios here...

Backup /system and /data.

Install arter97's kernel, does v4a work?

Install idleKernel over that, does v4a still work?

Wipe system entirely, install ROM, then install idleKernel, does v4a work?

Restore /system and /data if necessary.

I'm sorry if these steps could take some time and effort to diagnose the issue.
[Galaxy Note 3 Original Android Development] danerrickcuba@gmail.com:
How Disastrous will it be if one flashes idle_kernel cm12.1 on unofficial CM13, I mean this version of Android M it's using the kernel v1.33+ by Temasek , same kernel used on CM 12.1!

Has anyone played with that?
[Galaxy Note 3 Original Android Development] jcadduono:
Nothing bad could happen but it likely won't boot. It probably only needs a few ramdisk changes mainly in init.environ.rc if anything. I'll try it out myself.

If I can get some changes going to make it work, I'll post it as an official kernel build.

Edit: I LIED ITS A LOT OF RAMDISK CHANGES.
[Galaxy Note 3 Original Android Development] Gggggas:
Will try out when I get back to temasek rom, I'll let you know.

Thanks for the input [emoji106]
[Galaxy Note 3 Original Android Development] danerrickcuba@gmail.com:
Next time champ!!!
[Galaxy Note 3 Original Android Development] jcadduono:
I got it to boot but it's crashing every few minutes so now I just need to track down some errors with logcat. :D

You can watch me push every once in a while @ https://github.com/jcadduono/idleKernel-note3/commits/ik-cm13.0

So far it's rebooted like 12 times through the ART compilation thing.

Okay so it's not a super terrible error...

[ 46.618535] SMSM: Modem SMSM state changed to SMSM_RESET.
[ 46.619225] Fatal error on the modem.
[ 46.619640] modem subsystem failure reason: dog.c:1503:Watchdog detects stalled initialization.
[ 46.620055] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
[ 46.620510] Rebooting in 5 seconds..
[ 51.623594] msm_restart: Going down for restart now
[ 51.624153] Going down for restart now
[ 51.625488] Calling SCM to disable SPMI PMIC arbiter
[Galaxy Note 3 Original Android Development] smaiarif:
[MENTION=5672995]jcadduono[/MENTION] hey mate which app i should use with your idlekernel to enable usb fast charging.
[Galaxy Note 3 Original Android Development] piats:
Kernel adiutor
[Galaxy Note 3 Original Android Development] jcadduono:
there's an app called fast charge by mathew winters that can turn it on but can't change the specific settings.

as can kernel adiutor as piats said.

you can use terminal emulator or adb to change fast charge settings like max charge rate etc.

cat /sys/kernel/fast_charge/info

shows fast charge info

echo 0 > /sys/kernel/fast_charge/failsafe

that will allow you to change fast charge settings to unsafe speeds

ls /sys/kernel/fast_charge/

those are the options you have to edit/echo x to, just be careful

i guess if you want to keep those settings you can create an file in /system/etc/init.d by doing (as root in terminal emulator or adbputty)

mount -o remount,rw /system

nano /system/etc/init.d/do-whatever

in text file add like

#!/system/bin/sh

commands here

then ctrl+x, y, enter

mount -o remount,ro /system

but only crazy people do that

keep in mind that idlekernel sets usb charge rate to 1200 mah by normally so fast charge is not really necessary unless youre crazy about killing your battery
[Galaxy Note 3 Original Android Development] kopitalk:
Hi James, for f2fs do you think it has something to do with encryption or fstab? I realise that after converting data to f2fs in twrp and reboot, it somehow force data back to ext4.
[Galaxy Note 3 Original Android Development] dkonect:
Hello ,Before make a mistake,i want to ask ,the version 2015-11-14 6.5.4 is for note 5 port (darklord 5.1.1) ??

thanks

Good to see a new kernel for our note 3 because ,they dont have a lot of choices
[Galaxy Note 3 Original Android Development] friedCELLS:
This is my new record. Never seen this before. 9 hours SOT. Original Samsung battery. CM 12.1. Uhhhhmazing! No xposed, no battery saving apps. I just disable most apps from startup using System Tuner Pro, and disable a lot of apps from having wake lock permissions using built in CM tools. Also, I don't have Google anything on my phone. Not even Play Store. I use Amazon app store instead and for those apps that I need from Play, I'll restore those from backups and every few months, I'll install Play momentarily to update them, then uninstall Play again.
[Galaxy Note 3 Original Android Development] AM.8:
[MENTION=5672995]jcadduono[/MENTION] can i flash your kernel on CM13??

Thanks

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] rayman95:
it's a fact google eats the most part of battery..just one question, can you use you tube or maps even without google services???and do you remove all google services or just playstore and contacts synchro???
[Galaxy Note 3 Original Android Development] japoco_poz14:
Original cm or temasek 12.1 rom?

The "world" of Google is a most part of battery drain

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Original Android Development] jcadduono:
You can now! My CyanogenMod 13.0 builds have just started now. Find them at the download section on first post. :)

Keep in mind CyanogenMod 13.0 is totally broken atm.

Android M source changed the radio and sdcard interfaces in some weird way, so Cyanogen team needs to create a legacy modem/radio service to support current hlte blobs as far as I can tell. Not sure what the sdcard issue is about!

These issues are not kernel related, so keep up to date with the CyanogenMod 13.0 unofficial thread by [MENTION=293887]Morningstar[/MENTION] !

American region users such as hltetmo, hltecan, hltespr will have battery issues with the hlte build of Cyanogenmod due to constant NFCService restarting. This is probably not as big as an issue as the not working modem though. :P
[Galaxy Note 3 Original Android Development] Bushido76:
Today I spent some time to narrow down the F2FS problem. I did change the selinux.rc file in the idleKernel ramdiks in several ways to set enforce at early-boot, boot, early-init, init and early-fs instead of using the trigger property:boot_completed. All of them were working ok until the enforce-flag is changed at the end of the boot process again. Unfortunately logcat is not very informative at this point. I can see the following SELinux audit which changes the enforcing mode from 0 to 1:

E/audit ( 2809): type=2000 msg=audit(0.700:1): initialized

E/audit ( 2809): type=1403 msg=audit(1409186721.290:11): policy loaded auid=4294967295 ses=4294967295

E/audit ( 2809): type=1404 msg=audit(1409186721.300:12): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295

E/audit ( 2809): type=1400 msg=audit(1409186723.550:13): avc: denied { setenforce } for pid=1 comm="init" scontext=u:r:init:s0 tcontext=u:object_r:kernel:s0 tclass=security permissive=0

As you can see - during the init-process something triggers the change of the enforcing mode from 0 to 1. Concerning to the logcat the change occurs shortly after the killing of the bootanimation process and near some keyguard messages. But it's very hard to find out, which process (keyguard, medialibrary, su mount) triggers the audit event.

Because of the statement, that everyhing is working ok with lean kernel I did some comparisons of the source code. One main difference is the linux update number which introduced some new extended selinux filesystem permissions (comparable with the ones in Samsungs Lollipop source). In the init.rc-files I can't find any noticable difference which could explain the issue.

---------- Post added at 10:35 PM ---------- Previous post was at 10:25 PM ----------

Just a short addition (maybe the solution) to the F2FS problem.

There is one difference in the init.rc file between idleKernel and leanKernel:

# SEC_SELINUX

on property:init.svc.bootanim=stopped

start auditd

So idleKernel seems to trigger the audit itself. Maybe there are other dependencies but this is a good starting point for further analysis.
[Galaxy Note 3 Original Android Development] mircea89fzr:
This kernel is amazing! Never have i had so much battery life. I get 7 hours SOT with the original battery, 2 years old, just with -0.25 underclock. Antutu score ~45k. Usually I eagerly await for updates on other kernels, but with your kernel I hope by every update that it will not ruin this great battery life.
[Galaxy Note 3 Original Android Development] NBAPwns:
What rom do you use?Do i just offset the global voltage to -25? Cause on this kernel i dont know what to undervolt to cause if i do my phone just reboots

---------- Post added at 02:30 AM ---------- Previous post was at 02:27 AM ----------

Does anyone have any tweaked settings for better battery life on this rom? Im using Kernel Adiutor.
[Galaxy Note 3 Original Android Development] wild wadi:
[MENTION=5672995]jcadduono[/MENTION]

This is really amazing. It beats all my records of battery life. WOW!

Could you please suggest a good setting for Kernel Auditor; CPU-I/O Scheduler for N9005 32/Darklord-AU. Currently I'm on default

Man if XDA had a prize system, you'll be way up there.

Thanks a million.
[Galaxy Note 3 Original Android Development] mircea89fzr:
I use audax rom, but I've further removed a lot of bloatware. My mistake, I set the undervolting globally to -5 (I had an S3, that's where mistake comes from). For 300Mhz I go lower with additional 5mV.
[Galaxy Note 3 Original Android Development] jcadduono:
I wonder if the undervolting instability is due to the compiler optimizations (-O2 combined with native arch & tuning optimizations made by Christopher83's toolchain). This is certainly a scenario that happens on x86-64 hardware, when AVX and AVX2 instructions tend to break bad overclocks.

Also keep in mind that each Krait cpu has been stressed for stability at each level of voltage and given a binning stability number.

With idleKernel you can do this command:

su

cat /sys/devices/system/soc/soc0/soc_pvs

It will show you a number, usually between 0 and 6. The closer to 6 you are, the more stable your chip will be at lower voltages.

Each number corresponds to a voltage table in the flattened device tree which is part of the kernel (tagged onto the end when compiling).

The voltage table for 0 is somewhat higher than the voltage table for 6. My phone's chip was binned as 4, luckily. I'd say 2 is the average.

Sometimes the stress test used to give the chip a binning number might find an issue early on, and give it a lower number than it could handle in day to day use. This is often what gives you the opportunity to do big undervolts.

Keeping all this in mind, I do not recommend undervolting at all. Your chip has been measured to be stable at the voltages it is assigned from factory through the FDT. While it could seem stable after an undervolt, you might eventually run into instability even if you don't notice it, and this could result in corrupted data or worse.
[Galaxy Note 3 Original Android Development] Bushido76:
Sad news concerning F2FS and touchwiz from my side. After changing several paramters and init files in the ramdisk everything points to the extremely strict SELinux policy of Samsung touchwiz roms. It seems to be compiled as enforcing during init and does "neverallow" setenforce changes during this time. It would be possible to overrule some of the restrictions in the kernel code, but to be honest, that would be a very dirty solution.

Is anyone in this thread who could recommend a stable AOSP 5.1.1 rom which provides ANT+ functionality?
[Galaxy Note 3 Original Android Development] jcadduono:
I need to figure out how to compile my own SEPolicies using the files given by Samsung. That would be nice. I can start with taking the SEPolicy generator from CyanogenMod's github repo.
[Galaxy Note 3 Original Android Development] Bushido76:
I don't know the policy generator but you need the policy (project) files to make/compile the SELinux-binary. Unfortunately I have no access to a samsung sourcecode tarball at the moment, but maybe you could find the files in then vendor directory. Otherwise you could try to generate a more "generic" policy model which allows most of the applications to run as supersu i.e. But in touchwiz roms there are still some knox relicts which could interfere with such an approach.

Edit: I meant platform directory.
[Galaxy Note 3 Original Android Development] friedCELLS:
Sorry for delay. Not on XDA often. I use YouTube (or the app TubeMate) and maps in the browser. But no, none of the Google branded apps will work without play services always running or without play store installed. There's even several non Google apps that won't work. For the ones that I encountered, I just found alternatives elsewhere like Amazon app store. For navigation, I use Waze which is on the Amazon app store too. Quite different than Google maps but over time, you adjust. But when I want detailed info about places, I use Google maps in the browser (saved as a bookmark) and then copy/paste addresses over to Waze. There are sacrifices to being Google free but for me, it's worth it....

---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------

Original CM 12.1.
[Galaxy Note 3 Original Android Development] jcadduono:
THEN WE TAKE THE FIGHT TO SELINUX SOURCES!

https://github.com/jcadduono/idleKernel-note3/commit/e42c0c933b487c334cb694befd7b8942c68db07b

If I use the above approach and separate my builds into force permissive and force enforcing, would people be against that?

It would say no thanks to everything that tries to change the selinux mode, and it would be impossible without flashing a different kernel.

By the way guys, if you go into google settings and disable everything from syncing, or submitting data, then you shouldn't lose any battery to google services and have all the google access you want lol.

UPDATE: The above commit was a bunch of work for pretty much nothing, I could have just disabled SELinux development mode and forced selinux_enforcing to 0 using #define :|

Here is an updated commit, allowing forcing of selinux mode outside development mode! https://github.com/jcadduono/idleKernel-note3/commit/72e992a2c2669cfb82d5d1c289b22f43479c34e7

UPDATE 2: I've now successfully booted with f2fs /system /cache & /data on touchwiz :)

UPDATE 3: Touchwiz kernel 6.5.5 coming soon. I'm going to rearrange the folders on my download site so that permissive is the norm, and enforcing can be grabbed from enforcing folder. BTW it sucks having to compile twice for permissive and enforcing versions!!!!!!!
[Galaxy Note 3 Original Android Development] imixslash:
NFC issues

Hi, Since 5.0 upgrade to N900W8 (Canadian note) with custom roms, i haven't been able to get NFC working. Is there a reason behind it? I'm using the latest 6.5.4 Canadian version of kernel. I did originally upgrade to official LP via Odin to get my bootload/radio/etc updated. Then after custom from flash i install the NFC/BT/WIFI fix to get the BT/WIFI working, but still no luck with NFC. I"m not sure if this was asked previously by others.

Thanks for the great work. Very good battery life and stability with this kernel.
[Galaxy Note 3 Original Android Development] ithehappy:
I used this kernel first time today, and I really liked it, except some lags I encountered. I mentioned about it on Arya topic, so you can see it here, http://xdaforums.com/showpost.php?p=63882151&postcount=14352

Asking here as well, as this is the kernel specific thread. I don't really care about battery life, so if someone be kind enough and mention what to change to have the smoothest performance I'll be really grateful.
[Galaxy Note 3 Original Android Development] jcadduono:
Grab terminal emulator and do su then ik

In there you can change a variety of things. The only thing there worth changing though is probably cpu frequency -> screen off to 1.2 GHz which could fix some audio streaming issues with the screen off. I should probably change default back to that.

For higher rendering performance, consider using an app like Kernel Adiutor to disable adreno idler and/or change gpu scaler from msm-adreno-tz to performance if desired.
[Galaxy Note 3 Original Android Development] AM.8:
[MENTION=5672995]jcadduono[/MENTION] can i flash your kernel on this Rom??

Tazzy aurora rom 5.1.1 v4.

The link : http://xdaforums.com/showthread.php?p=62862159

Thanks in advance :)

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] jcadduono:
Try note5port. v6.5.5 of note5port coming in an hour.
[Galaxy Note 3 Original Android Development] dakemin22:
Will the new kernel fix the camera flicker issues....
[Galaxy Note 3 Original Android Development] jcadduono:
no I'll never fix it, ask the rom dev to fix it

version 6.5.5 fixes f2fs on touchwiz, and nfc for N900P/hltespr on note5port and touchwiz
[Galaxy Note 3 Original Android Development] kopitalk:
Touchwiz /data conversion from ext4 to f2fs is WORKY now.. the trick is the modded TWRP? I can restore my nandroid data backup in ext4 to f2fs in your bug-squashed twrp-2.8.7.0-hltecan-4.4-f2fs (my device is hlteeur). How to make this work in TWRP hlteeur as well? Awesome job!
[Galaxy Note 3 Original Android Development] jcadduono:
I don't think there is any difference between twrp versions, have you found one, besides showing hltecan instead of hlteeur?

The only thing my modded twrp does is fix the error that happens when formatting /data to f2fs and restoring f2fs images.

The f2fs working on touchwiz is because I made a selinux override option in the kernel to permanently force permissive mode that silently denies any app that tries to switch it.
[Galaxy Note 3 Original Android Development] fbzong:
changelog can not open;

changelog can not open;

can you write it this title;
[Galaxy Note 3 Original Android Development] kopitalk:
I tried some operation in twrp-2.8.7.0-hltecan-4.4-f2fs, nandroid backup of /data in f2fs was completed however restoring it failed with this error.

E:extracTarFork() process ended with ERROR=255

Then I restored back the backup that I made earlier with twrp-2.8.7.0-hlte-4.4 in ext4 to the /data f2fs, and it was successful.

Minor issue in hltecan, the screen brightness setting is broken.
[Galaxy Note 3 Original Android Development] jcadduono:
arghh twrp is broken all over the place I hope 2.9.0.0 comes out soon and fixes everything but it seems unlikely considering the amount of issues opened on github for it.
[Galaxy Note 3 Original Android Development] azlav:
so the flickering issue is gone after all? :D
[Galaxy Note 3 Original Android Development] kopitalk:
Please stop the nuisance... [MENTION=5672995]jcadduono[/MENTION] has mentioned a few times that he won't do anything with whatever flickering issue you have. Please spam your ROM thread instead :good:

I have a little discovery here...

Nandroid backup /data (ext4) using TWRP hlteeur --> format /data to f2fs in TWRP hlteeur --> restore backup image (ext4) to /data (f2fs) using TWRP hlteeur --> Restore successful but can't boot to system.

Nandroid backup /data (ext4) using TWRP hlteeur --> format /data to f2fs in TWRP hltecan --> restore backup image (ext4) to /data (f2fs) using TWRP hltecan --> Restore successful, boot successful.

Nandroid backup /data (f2fs) using TWRP hltecan --> wipe /data --> restore backup image to /data (f2fs) using TWRP hltecan --> Restore failed in TWRP.

Nandroid backup /data (f2fs) using TWRP hlteeur --> wipe /data --> restore backup image to /data (f2fs) using TWRP hlteeur --> Restore successful, boot successful.
[Galaxy Note 3 Original Android Development] AM.8:
Can anyone share the best settings for this awesome kernel??

Thanks :)

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] Bushido76:
Thank you very much for your effort - I really appreciate that. ?

Don't you think that we can go with one version? Maybe with a custom default.prop parameter or a version which is permissive during boot up and can be set enforcing after boot? In my case there is no need for an enforcing version at all.

Btw. you could eliminate the following lines from init.rc

# SEC_SELINUX

on property:init.svc.bootanim=stopped

start auditd

It prevents the auditing service from starting all eliminates all auditing messages in the logcat.
[Galaxy Note 3 Original Android Development] 6h0st:
ikconfig stopped working after updating to 6.5.5
[Galaxy Note 3 Original Android Development] kopitalk:
Both "ikconfig" and "ik" are working in terminals. Make sure you have root privilege (type "su") before invoking the command, otherwise you'll get /system/bin/sh: ikconfig: not found.
[Galaxy Note 3 Original Android Development] antt00:
It really is not there for n9005 note 5 rom version 6.5.5
[Galaxy Note 3 Original Android Development] 8xfan:
Same with me on darklord n5 port [emoji17]
[Galaxy Note 3 Original Android Development] kopitalk:
Have you disabled verify PATH entry in Terminal preference and restart Terminal?
[Galaxy Note 3 Original Android Development] antt00:
Thanks got it back that way.
[Galaxy Note 3 Original Android Development] core7x:
IdleKernel work so nice. Keep up a good work.
[Galaxy Note 3 Original Android Development] Racharg:
I've the same issue with nfc. I too hope it's kernel related since it appears that the dev fixed nfc issues on the n900t. He's got a n900w8 son here's hoping!
[Galaxy Note 3 Original Android Development] hamada samir:
Yes

Work perfectly
[Galaxy Note 3 Original Android Development] kpirnie:
[MENTION=5672995]jcadduono[/MENTION]

Hey mate, trying to diagnose some "hot" reboots that keep happenning to me.

Wondering if you can help me interpret the kmsg log (attached)... it is mostly greek to me.

I started the 'cat' post-boot, and pre "hot" reboot, then hammered until it did the hot reboot.

n900t - Dominion s6 ;) - idleKernel 6.5.4
[Galaxy Note 3 Original Android Development] bailey2408:
Ive also tried using this kernel on aurora s6 port but random reboots galore.. on a n990t.. other kernels fine.. looking at my kmsg seems having problem mounting/ reading emmcblk25.. [MENTION=5672995]jcadduono[/MENTION] i can attach log if you want.. leankernel 6.5.3 no reboots at all.. wanna use this badboy but cant
[Galaxy Note 3 Original Android Development] kpirnie:
Sorry mate, this partition? mmcblk0p25
[Galaxy Note 3 Original Android Development] bailey2408:
That would be the one.. i looked quickly at your log and didnt see that error.. appears reboots are isolated to n900t.. havent seen anyone else saying getting reboots.. no matter the rom i get constant reboots.. clean installs
[Galaxy Note 3 Original Android Development] kpirnie:
Aye, ditto.

Which is odd to say the least considering the n900w8 is identical LOL

Yeah, was digging into it a bit, and now that you mentioned that partition,

I wonder if it's even needed

. There aren't too many roms out there that use the preload. :D I know I don't, and if I use a rom that isnt one of mine, I debloat the snot out of it before I flash...

I am glad to see it's not my mods causing the issue tho LOL

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------

Did you convert to f2fs?