yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] derride8:
What kernel settings do anyone recommend for note 5 port?
[Galaxy Note 3 Original Android Development] justin1221:
Default settings work great. Smooth and battery is good so far.
[Galaxy Note 3 Original Android Development] jcadduono:
As Ernie was mentioning, you need to plug the phone into a USB port in which the host (the computer) reports USB 3.0 support while using a USB 3.0 cable. This will then allow the ums script & kernel to trigger the SuperSpeed data lanes. Right now, the dwc3 module is coded in a way that it forces USB 2.0 on all new connections, and won't allow USB 3.0 on first connect. I could change that in theory, but I have to wonder if there's a reason Samsung made it that way.

Haha, welcome to the developer section buddy! I probably should be making a Q&A thread but I have trouble keeping track of just two threads already. >< I'm hoping people that can't post here will just send me private messages or add me on Skype. I accept all requests.

As for a note 5 port, well... I'd probably go with [MENTION=744557]oluwaponmile[/MENTION]'s Phronesis Rom - it looks like it has the most time put into it fixing issues.

I'm considering replacing all the mdss code with current Touchwiz sources but keeping KCAL and SUSPEND/RESUME event triggered cpufreq_screen_on. Maybe this would fix the brightness bugs, but I'd prefer to make that a last resort. I'll search around for the issue. To everyone else -- is your auto brightness working alright, and on what ROM?

If using kernel adiutor, I recommend increasing the "Input Interval" touch boost length from 40 ms to 200 ms, and setting "Input Boost Frequency" to 1728 mhz. It will use a bit more battery with screen on, but should help with laggy transition effects and opening menus.
[Galaxy Note 3 Original Android Development] yurmuki:
I have tested some other kernels with idlekernel to compare video camera result. I think idle is not performing well in terms of video.

The video focus is not stable and is a bit blury as well.

May be my findings are wrong.
[Galaxy Note 3 Original Android Development] Freyelis:
I'm on 5Ghz Wifi all the time, it's both working for Touchwiz ROM (aryamod 8.1) and Note 5 Port ROM (Phronesis v3).

I don't know what's the issue with the previous one that 5ghz wifi is not working.. but mine is working fine.

---------- Post added at 05:56 AM ---------- Previous post was at 05:49 AM ----------

also, in new version of TWRP, who here has tried flashing roms with aroma in them? previous one reboots.. hopefully new one is good
[Galaxy Note 3 Original Android Development] Air-真心为你:
I lost root access after flashed latest 6.6.3 on my hlte running temasek cm13.0 v1.4. Reinstall supersu doesnt seem to work. Anyone could give an advice ?
[Galaxy Note 3 Original Android Development] stavca:
I use the same combo and everytime I flash new tema's build I flash SuperSU 2.52 also ;) when updating idle kernel, there's no need to reflash SuperSU again
[Galaxy Note 3 Original Android Development] BillGoss:
I flashed Temasek 1.4, SuperSU 2.46, and idleKernel 6.6.3 all together and it's working fine
[Galaxy Note 3 Original Android Development] jcadduono:
I got it working with supersu 2.52 zip but you could try 2.61. I don't think idlekernel works with built in superuser of temasek's build because of sepolicy & ramdisk contents. I built it for morningstar's builds.
[Galaxy Note 3 Original Android Development] emuandco:
I always use SuperSU 2.52 (See my sig for full list of stuff I use which ALWAYS is recent ^^) and it works super fine. 2.46 btw... does not support MM Android in theory. Btw, your TWRP builds seem to be faster on backing up, too as it seems ^^ And they are GOLDEN :D (Official build sort of forced me to switch to CM13, because my 12.1 backup was not flashable at all, even with the correct MD5... F2FS was used in the past for a few days, so... this might be your mentioned FS bugs I guess ^^) 2.6X is nice for official FW build I would say, but for custom firmware I don't see a reason to use it.
[Galaxy Note 3 Original Android Development] Air-真心为你:
I'm using v2.61. I'll try 2.52 later and report back. The for help
[Galaxy Note 3 Original Android Development] Bushido76:
I'm using Stock TW 5.0.1 (OK6). Auto brightness seems to be battered in 6.6.3. When the environment get brighter the phone brightness increases but it's not working the other way round. Turning screen off and on resets the brightness. Hope that helps a little in narrowing down the issue.
[Galaxy Note 3 Original Android Development] mertcanmusic:
Buddy i use the note 5 port rom from Dark-Au V6.1 and befor i have use the darklord 1.5 kernel but on there was my auto brightness ok. your kernel is not dimming when i stay in my dark room. It's any time to bright and will not dimming

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] kopitalk:
I thought it's just me... seems like the offset for the low brightness value is a bit higher than stock. I notice the same thing in TWRP idle too. Running TW 5.0 based AryaMod here. Could it be only affecting N9005?
[Galaxy Note 3 Original Android Development] CatAlex:
QS-ZSUGOK2 ROM + idleKernel 6.6.3 = Broken Proximity sensor.
[Galaxy Note 3 Original Android Development] saadramiz:
May I know the reason why you have reverted to legacy WiFi driver Coz, I don't see any problems with Wi-Fi since 6.6 not even with 5G.
[Galaxy Note 3 Original Android Development] jcadduono:
I had reports of unstable wifi after upgrading the drivers, but I don't know if it's actually the case. I think I will go back to new wifi drivers in next release.

It's probably due to difference in proximity sensor library on ROM, it's a really tricky situation there because I can either compile the kernel for new proximity libraries that use EV_REL, REL_DIAL and it will for for Gxxx and newer series ROMs or I can compile kernel for old proximity libraries that use EV_ABS, ABS_DISTANCE and it will work for Bxxx to Exxx series ROMs.

One solution might be for me to compile for newest libraries and then provide a flashable zip that replaces all the libraries in the ROM with new ones, but that would break flashing any kernel other than idleKernel, or maybe the ROM won't be compatible with the new libraries.

My solution right now will be to create kconfig options to use legacy drivers or new drivers...you will need to compile the kernel yourself, which is actually quite simple.
[Galaxy Note 3 Original Android Development] CatAlex:
Thx, but I just flash my nand-backup with QS-OI1. ))

I'm absolutely incompatible with the word "compile".
[Galaxy Note 3 Original Android Development] Kamy:
Jake is MTP broken again on 6.6.3?
[Galaxy Note 3 Original Android Development] jcadduono:
I've never actually made any MTP code changes ever. Works fine for me!
[Galaxy Note 3 Original Android Development] Kamy:
Yeah it was working as I reported here and had been updating since then though never tested again, till now on 6.6.3 that I cannot access to sdcard through computer again
[Galaxy Note 3 Original Android Development] jcadduono:
Make sure Micro SDcard is checked as mounted in Mount menu, then unplug phone, disable MTP, enable MTP, then plug back in.

If it's still not working I dunno, is it accessible in TWRP for flashing zips and such?
[Galaxy Note 3 Original Android Development] r-l:
Edit: never mind
[Galaxy Note 3 Original Android Development] ibosilj:
is anyone using cm13 with idlekernel here? can you tell me if you're having crackling notification sounds or first half of notification sound not played?
[Galaxy Note 3 Original Android Development] Air-真心为你:
I noticed one thing. When I 'm using lean kernel v5.2. I'm able to download Vainglory and NBA2K16 from play store. And this kernel changed my model to N900T(Actually it's N9005). All other kernel can't download these games. I've tried to edit build.prop or install Market Helper but still can't help anything. Anyone figured it out ? I have to stick on it for a while as I am a heavy gamer-.-
[Galaxy Note 3 Original Android Development] remowrx:
I can also confirm this..6.6.3 on N5 port with N3 camera.
[Galaxy Note 3 Original Android Development] waplegend:
Please make your kernel work with samsung private mode on the note5 ports
[Galaxy Note 3 Original Android Development] BillGoss:
I am and I haven't noticed any problem with sounds.
[Galaxy Note 3 Original Android Development] FrozenLord:
Have you changed your governor?

I have seen these symptoms when OnDemand and similar governors were used with conservative settings.

The result is that your CPU does not ramp up fast enough to have the processing power for the playback - which is why only the first part of the sound is affected.
[Galaxy Note 3 Original Android Development] Carlos_Bilibio:
Guys... using idle with over a 2,72ghz, win 10,000 points in AnTuTu test, is that right?
[Galaxy Note 3 Original Android Development] newintage:
Kernel has nothing to do with google apps, play store, google account, game sources or anything you talked about mate. It must be about your GAPPS, /system or some other thing.

Flashing old working version may help... but IDK :rolleyes:
[Galaxy Note 3 Original Android Development] Air-真心为你:
Theoretically speaking. It certainly has nothing to do with play store. But I've tried and made this conclusion. It changed the model and make some items available indeed.
[Galaxy Note 3 Original Android Development] andrew.mackew:
[MENTION=5672995]jcadduono[/MENTION]

Brotha, I'm actually trying to build a CM12.1 for my hlte, however I'm stuck at kernel building..

I tried to ask for support on CM thread.. however.. you know.. nobody "in home", so I decide to ask someone else that is building kernels.. Can you share your .confg file for CM kernel? Or, is there any trick to automatically configure the kernel settings? Cuz I'm getting stuck at this:

HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
sound/soc/codecs/audience/Kconfig:40:warning: type of 'SND_SOC_ES_SLIM' redefined from 'boolean' to 'tristate'
sound/soc/codecs/audience/Kconfig:43:warning: type of 'SND_SOC_ES_I2C' redefined from 'boolean' to 'tristate'
sound/soc/codecs/audience/Kconfig:44:warning: choice value used outside its choice group
sound/soc/codecs/audience/Kconfig:41:warning: choice value used outside its choice group
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
/home/admin/android/cm/kernel/samsung/hlte/scripts/kconfig/Makefile:33: recipe for target 'silentoldconfig' failed
make[2]: *** [silentoldconfig] Error 1
/home/admin/android/cm/kernel/samsung/hlte/Makefile:496: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop.

#### make failed to build some targets (3 seconds) ####

(venv)[admin@quarktech hlte]$ make menuconfig
HOSTCC scripts/kconfig/lxdialog/checklist.o
HOSTCC scripts/kconfig/lxdialog/inputbox.o
HOSTCC scripts/kconfig/lxdialog/menubox.o
HOSTCC scripts/kconfig/lxdialog/textbox.o
HOSTCC scripts/kconfig/lxdialog/util.o
HOSTCC scripts/kconfig/lxdialog/yesno.o
HOSTCC scripts/kconfig/mconf.o
HOSTLD scripts/kconfig/mconf
scripts/kconfig/mconf Kconfig
sound/soc/codecs/audience/Kconfig:40:warning: type of 'SND_SOC_ES_SLIM' redefined from 'boolean' to 'tristate'
sound/soc/codecs/audience/Kconfig:43:warning: type of 'SND_SOC_ES_I2C' redefined from 'boolean' to 'tristate'
sound/soc/codecs/audience/Kconfig:44:warning: choice value used outside its choice group
sound/soc/codecs/audience/Kconfig:41:warning: choice value used outside its choice group

Your configuration changes were NOT saved.

#### make completed successfully (03:16 (mm:ss)) ####
[Galaxy Note 3 Original Android Development] Bushido76:
I'm not sure whether I got you right but you can find the config files at GitHUB:

https://github.com/jcadduono/idleKernel-note3/tree/ik-cm12.1/arch/arm/configs

I did not run it myself yet but I would simply start the build.sh shell script in the kernels main directory. It should automatically use the correct config scripts.

https://github.com/jcadduono/idleKernel-note3/tree/ik-cm12.1?files=1
[Galaxy Note 3 Original Android Development] emuandco:
You said you have a N9005, right? Well, same here and it did not change anything. The model is set in build.prop and this is a firmware, NOT a kernel file. My phone (see sig) still says truthfully that it's a N9005, so it's not the kernel's fault.
[Galaxy Note 3 Original Android Development] Air-真心为你:
You guys even didnt get what I said. I wont reply anymore.
[Galaxy Note 3 Original Android Development] jcadduono:
to be honest I couldn't understand what you were trying to say :s they are correct though in that the model number of the phone is not set from kernel in touchwiz roms. In AOSP roms however, the kernel's ramdisk contains a modified init binary that reads the bootloader version from the phone and sets the proper device info (model no, etc.) based on that.

BTW play store app availability is usually DPI based, so make sure your screen dpi is set to something that is popular or use xposed with play store dpi faker module.

sorry this is a question best for the #cyanogenmod-dev channel on freenode irc. idlekernel does not build in the standard android way so i don't really have experience with android builds. (it doesn't even require an android build environment!) in the case of samsung kernels you will need to generate a .config first using the defconfigs. this should already be part of the android makefile so cyanogenmod builder should be doing that automatically.

make -C $KERNEL_DIR O=$BUILD_DIR msm8974_sec_defconfig VARIANT_DEFCONFIG=msm8974_sec_hlte_eur_defconfig

I think would be the command to generate a .config, setting or replacing KERNEL_DIR and BUILD_DIR first.

but really try out the irc channel.
[Galaxy Note 3 Original Android Development] HachiKen:
[MENTION=5672995]jcadduono[/MENTION]

Sorry for this question, I don't know anybody ask this before.

Your kernel is great, i'm using Note 3 Docomo, Blisspop rom based on cm12.1 and cm13 too, but I have a problem with my s-cover, its function doesn't work when i open or close the lid to wake up the display. I test it by myself, change rom and kernel, finally i think it's because idle kernel doesn't support, so can you help, this function is really useful instead of pressing hardware key. Thanks!
[Galaxy Note 3 Original Android Development] Lyokacanthrope:
Hey, [MENTION=5672995]jcadduono[/MENTION].

Any possibility of merging this stuff in? I'm not 100% sure if this is all that's needed.

http://review.cyanogenmod.org/#/c/102988/

http://review.cyanogenmod.org/#/c/104871/

I'm a bit of a stickler for ambient display, and it'd be great if there was a way to decouple interactive mode from the panel being on. I tried merging it myself but I'm not really experienced in driver and kernel work.

There's some other similar commits for other devices, if it helps:

http://review.cyanogenmod.org/#/c/96199/

http://review.cyanogenmod.org/#/c/101495/

Apologies if it's a silly or wasteful request.
[Galaxy Note 3 Original Android Development] jcadduono:
ULPS is already part of stock Note 3 sources, since LP release I think.

It's integrated quite a bit differently though. MDSS drivers differ a lot between LP and KK code.

What really confuses me is I don't see anywhere in CM where they actually use this code or feature.

Same with this guy:
[Galaxy Note 3 Original Android Development] Lyokacanthrope:
Maybe I misunderstood it (which is likely - again, not a kernel or driver dev!), but it should allow for ambient display to be a bit more power efficient by using a lower power screen mode.

https://developer.android.com/reference/android/view/Display.html#STATE_DOZE

Attempting to use the 'doze' screen state in my own CM builds just gives me a black display when ambient display would normally turn on.

EDIT: Checking through dmesg definitely seems to indicate that the panel driver doesn't support the right display mode. when sent the command to set to STATE_DOZE, the panel driver just responds with:

mipi_samsung_disp_send_cmd : panel is off state!!

in dmesg
[Galaxy Note 3 Original Android Development] erniesan82:
Hi there, here I'm on phronesis v3, idle kernel for note5port 6.6.3, my S-view cover works well... Although it hasn't work as it should even in the stock rom and kernel, sometimes I had to, even now, have to take the cover off and replace it, phone on, and it comes back working as it should. I wouldn't blame the kernel on my settings, also not sure if having a non original cover (Anymode brand) has to do anything with the problem but as I said replacing the cover works for me, hope it helps.
[Galaxy Note 3 Original Android Development] abalian:
Any reason why my back and menu keys only work with idleKernel now? I reverted to stock OC4 and OH1 kernel and they stopped working properly. The menu key opens up S Finder (short press) and the back key is unresponsive. The back key works only with Spen and works normally in recovery mode. Tried wiping, reflashing kernels, ROMs, everything. Only reverting to idleKernel made both keys function normally again.

Kernel link: https://idlekernel.com/touchwiz-lollipop/v6.6.3_2015_12_08/idleKernel-hlte-can-6.6.3.zip

Device: N900W8

ROM: Stock 5.0
[Galaxy Note 3 Original Android Development] HachiKen:
Thanks for your help, yes i have an original one, it work fine on Note 5 port rom, but i doesn't work on CM base, that's what i mean, and when I change to an old kernel that i've found on a japanese page for my Note 3 Docomo since a long time ago, it work fine but battery drain like hell :(
[Galaxy Note 3 Original Android Development] Freyelis:
[MENTION=5672995]jcadduono[/MENTION]

I'm uploading the GOK3 boot, bootloader and modem of N900K right now, will post here if it's up :)

---------- Post added at 04:44 PM ---------- Previous post was at 04:37 PM ----------

[MENTION=5672995]jcadduono[/MENTION]

Here it is, the latest BL, Modem, Boot of N900K Variant

AP_N900KKKU0GOK3_KERNEL: https://drive.google.com/file/d/0B6kB2D6Z9bbjMGtOVnhnRnRLNHM/view?usp=sharing

BL_N900KKKU0GOK3_BOOTLOADER: https://drive.google.com/file/d/0B6kB2D6Z9bbjWnZHbFJqNkkwV3c/view?usp=sharing

CP_N900KKKU0GOK3_MODEM: https://drive.google.com/file/d/0B6kB2D6Z9bbjNUhjY2V5ZmdpcGM/view?usp=sharing
[Galaxy Note 3 Original Android Development] L0nelyE4rth:
Accident stuck mhz problem.
[Galaxy Note 3 Original Android Development] jcadduono:
Oh but you do. http://www.xda-developers.com/xda-developers-and-the-gpl/

;)

Also, can you please include in the CSC section of DarkLord Note 5:

https://adduono.com/note3/canada-csc.zip

All Canadian CSCs stripped of apks + TBT for my local TBayTel customers.
[Galaxy Note 3 Original Android Development] darkera13:
I know about GPL, but i dont share my kernel at XDA. I only share my kernel at samsungviet.vn. CekMTL dont public his kernel source, so i need respect him. I dont want increase more misunderstanding with him.
[Galaxy Note 3 Original Android Development] kouros17:
After installing this kernal (touchwiz-lollipop v.6.5.1) i get the error code 942 when downloading from play store. Can you fix it please? (Aryamod 7.3, twrp 2.8.7.0)
[Galaxy Note 3 Original Android Development] AM.8:
[MENTION=5672995]jcadduono[/MENTION] mate, can i flash your kernel on tazzy Aurora rom N5 port 5.1.1 ???

SM-N9005

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] jcadduono:
No idea, try -darklord-n5 version. I'm thinking of renaming it to -n5port though since the changes *should* be compatible with all Note 5 environments. I'm working on a few fixes right now and should have a new version up later today.
[Galaxy Note 3 Original Android Development] jcadduono:
Sorry you need to upgrade Aryamod. Are you using the selinux_permissive version of my kernel or not?
[Galaxy Note 3 Original Android Development] AM.8:
Video recording flicking will be fixed too??

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] r-l:
Unlock brightness bug found. Same as in shinto kernel.

When unlocking the lockscreen the brightness stays dimmed.
[Galaxy Note 3 Original Android Development] jcadduono:
I don't know, I'm testing some things. I'm hoping I can find the fix for the video recording in latest Note 4 kernel source.

Worst case scenario, I've reported DarkLord Note 5 thread for copyright violations and we can get the camera fix by forcing a GPL kernel source release from darkera13. Very inconvenient method, and I'd prefer to find the fix by myself.

Even more worse case, if he's refusing to release GPL kernel sources he would have to take his project off XDA lol.

Best case scenario, by rummaging through Note 4 and 5 kernel sources I might be able to find fixes for other bugs present yet unknown in DarkLord N5 and other N5 ports.
[Galaxy Note 3 Original Android Development] :
No video flickering here. Idle kernel, Darklord RC2.1, Note 3 camera.
[Galaxy Note 3 Original Android Development] jcadduono:
Thank you very much, this helps a lot and explains why I have no flickering either!

It has to be related to Note 4 camera interface updates, missing API in Note 3 camera drivers.
[Galaxy Note 3 Original Android Development] AM.8:
You flased this one??

SM-N9005 or other version? ?

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy Note 3 Original Android Development] peped94:
I noticed when i turn off adreno idler, scrolling is much better and smooth
[Galaxy Note 3 Original Android Development] :
Of course, the one for Darklord N5, my phone model N9005 hlte eur. ;)
[Galaxy Note 3 Original Android Development] patek:
I am on qaraqumus qf3 ROM and at dowload from playstore I receive error 492...

This kernel is very fast and battery friendly.

Thank you.
[Galaxy Note 3 Original Android Development] jcadduono:
New rule: In order for me to help you, you have to put a link to the exact kernel zip/tar you downloaded, state your model (N9005, etc), and link me to the ROM you're having trouble with.
[Galaxy Note 3 Original Android Development] patek:
You are totally right, (and I made a mistake in the name of the ROM)

So,

Error: at dowload from playstore I receive error 492

device: N9005

ROM: QS-N9005-LP-FINAL-OF3 ROM (made by qaraqumus)

https://www.androidfilehost.com/?fid=24052804347794978

Kernel version: idleKernel-hlte-eur-6.5.1.zip
[Galaxy Note 3 Original Android Development] r-l:
Also system force closes sometimes with s-view cover.

Don't know if that's rom or kernel related. Haven't had it with dark-au rom + darklord kernel.
[Galaxy Note 3 Original Android Development] jcadduono:
I need you to give me the link to the kernel, the full link. That way I know if you are using permissive or enforcing.
[Galaxy Note 3 Original Android Development] patek:
Error: at dowload from playstore I receive error 492

device: N9005

ROM: QS-N9005-LP-FINAL-OF3 ROM (made by qaraqumus)

https://www.androidfilehost.com/?fid=24052804347794978

Kernel:

Index of /touchwiz-lollipop/selinux_permissive/v6.5.1_2015_11_05/idleKernel-hlte-eur-6.5.1.zip

To tell the truth, at reboot I see on the top of the screen

"enforcing"

by your opinion which one should I use?

Is there N9005 EUR enforcing version?

I could not find .
[Galaxy Note 3 Original Android Development] rapozaum:
I'm on AryaMod 8.1 with this Kernel and I'm having a hard battery time. Something like 2hrs of SoT.

Maybe there any settings I should be using?
[Galaxy Note 3 Original Android Development] eseregin:
Default settings pretty the best.

I doubt this is kernel problem, that lead to 2 hs sot... At least if you has not changed the default settings...