I know there are a few kernels/boot.img to force native 4K all the time on AOSP based ROMs, but are there any for Stock or Stock based ROMS?
*Dang! Thought I was in the Q&A and just realized I posted this in the wrong section and can't delete or move it.
You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.
Sepo190 said:
You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.
Click to expand...
Click to collapse
Could You share the Image with us?:angel:
Miustone said:
Could You share the Image with us?:angel:
Click to expand...
Click to collapse
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?
Sepo190 said:
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Click to expand...
Click to collapse
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?
iArvee said:
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?
Click to expand...
Click to collapse
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.
Sepo190 said:
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.
Click to expand...
Click to collapse
If it's not too much trouble, can you do the .235? I'm most likely not going to be updating to 270 any time soon. Willing to try it out without a fresh install.
This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?
gaijin1% said:
This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?
Click to expand...
Click to collapse
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.
Sepo190 said:
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.
Click to expand...
Click to collapse
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated
Watching gravure will be so much more satisfy ing, thanks
gaijin1% said:
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated
Click to expand...
Click to collapse
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?
gaijin1% said:
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?
Click to expand...
Click to collapse
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?
Sepo190 said:
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?
Click to expand...
Click to collapse
So if this actual 4k?? Like native 4k?? How's battery life/performance??
Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I tried several things but couldn't get 235 to root for the life of me.
Now I really want the new ROM [O][8141/8142][.270] M-ROM: Xposed, Daydream compatible so I hope that a .270 based 4K kernel will work with it. Really want that Daydream in 4K. I wonder if your .235 kernel will work with it or if your .270 version will get the drm fix using the Kernel Patch from JanJan.
Sepo190 said:
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?
Click to expand...
Click to collapse
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in
saved-j said:
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in
Click to expand...
Click to collapse
Sorry I haven't given an update in a while. I haven't been on here in a while. I had an unexpected move, so my server wasn't hooked up and then I didn't have internet for a while. Just got it hooked up today actually. I have one with the drm fix working for the newest update using the ramdisk from JanJan's kernel. I can take another look at .270 probably this weekend if you want. I don't have a manual or anything, I'm just removing the 1080p configs from the dts file. I don't remember the file path off the top of my head and I'm not home right now.
It's not possible to enable 4k just édit build prop?
Envoyé de mon G8141 en utilisant Tapatalk
16.20 kernel
Here is a 4k 16.20 kernel that has been working for me for the past week if anyone wants it. I used the ramdisk from JanJan's kernel. Flash it and then everything in his drm-patching zip. The file I have been editing is dsi-panel-maple.dtsi btw, since someone asked earlier.
https://mega.nz/#!R5UhhKjA!U2kp2Zl4gYGddiSIkpJMaOlVYuAcakb514CwHq3jEH4
Related
I can give ABSOLUTLEY no gurantee!! All you do with your phone will be on your own. I'm not responsible if your phone will brick or whatever...
Attation! This kernel is for the I8200 variant ONLY... the I8190 is absolutley not compatible !!!
Kernel should be work also for I8200/I8200Q/I8200L-Variants, but can not be gurateed as the basis was I8200! If it works then a notice will be fine!
If you are not sure about the process, the data are important on your phone or you need it as a daily phone, then LET IT BEE, and wait for the messages that it is safe to use. Its important at the beginning that users with knowledge tried it at first !
Changelog:
12.02.2016: Long time ago, but now after a lot of investigating some new things comes up. Check what was done
05.01.2014: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was. not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more main.tained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possibility to include also selinux what is needed for a kitkat-rom. Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to get a contact...
Baroni-V0.1 contains:
Basis of opensource from Samsung with some bugfixing
fixed recovery-boot-loop with a config-setting which must be used special in the Recovery zImage
Loglevel pushed down to minimum
Uber-Toolchain 4.9
set onDemand-Governor to standart. just to check how that works
start implementing SmartAssV2-Gonernor, but leave it inactive, due to some compile-errors.
bringing SELinux to work for future kernel releases if needed for > 4.4
Planned:
new govenors at the moment not established (will come later)
more other stuff (depending on learning-curve
Installation:
Install a recovery for safetyreasons (I prefer TWRP https://www.dropbox.com/s/d3rnfp3vabz9ee8/twrp_i8200_corrected.7z?dl=0
Read carefully the hints of the usage in the following firts post: http://forum.xda-developers.com/galaxy-s3-mini/general/s-iii-mini-ve-i8200-n-t2826565 (There also the needed Odin (3.09) can be get)
Make backups of the complete phone, and be sure that you know what you do!
Download the right Firmware for your phone from http://www.sammobile.com/firmwares/ (just to have a other safety fallback in your hand!)
Download the file, start odin as usual (all kies-tasks closed!)
extract the file, and put it to AP
put the phone in Downloadmode (Vol-down,Home-key and powerbutton), and connect the phone with PC
flash the kernel, and let the phone reboot
pray
If things go wrong, please give everytime the following information's:
what you did before
what exactly happened (its not easy to help if you say: it did not work )
which rom in which version, which recovery and which version of my Kernel you use
try to get a /proc/last_kmsg (if a unknowen reboot appears) and/or Logcat, Build prop, CPU info, Sysctl, Kmsg, Dmesg and send it to me (or as a attachment to the post) for further analyse (you can use that tool for it: https://play.google.com/store/apps/details?id=com.bassel.andylog )
Attention: First checks seem to be that I8200 (without N or L or Q) did not work atm.
Download:
kernel_i8200n-Baroni:
https://www.androidfilehost.com/?w=files&flid=47763
kernel_i8200n-Stock.7z (to getting back to stock kernel via Odin):
https://www.dropbox.com/s/xfhufcpxl5kxmue/kernel_i8200n-Stock.7z?dl=0
Recoverys (with fixed recovery boot loop):
https://www.androidfilehost.com/?w=files&flid=49834
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
One question.
SolarPlexus said:
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
Click to expand...
Click to collapse
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Danh23 said:
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Click to expand...
Click to collapse
Attention with TWRP-Recovery. Data-Partition restore seems to be not right. At the moment please did not use it, because it can delete your data-partition. We have to investigate it further! Other partitions seems to be ok, but its a good Idea if you copy your important data also manually to a other storage (like PC) while you trying things of this thread.
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
KwstPap said:
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
Click to expand...
Click to collapse
Did you made a backup with twrp (as described)? If yes, then make a restore only with boot marked in the list.
Otherwise, which version did you have? Plain n/l/q? Than I can make a package for Odin...
send with my Oneplus One (bacon) SlimKat Tapatalk
About the data recovery, use aroma FM to restore. Out worked for me
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
KwstPap said:
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
Click to expand...
Click to collapse
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
hahahahaha always forget to take a backup .but i am very stypid .i had a backup on my pc.hahah in one weak i have reflashing the stock formware 5 times and the root recovery and other staff again hahaha
thanks for the stok kernel
SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
¿which brings benefits to install this kernel?
RodsonBorja said:
¿which brings benefits to install this kernel?
Click to expand...
Click to collapse
Atm nothing... Its alpha and not working. Unfortunately I'm a little bit blocked by illness and x-mas and was not able to work on it... Maybe next week...
send with my Oneplus One (bacon) SlimKat Tapatalk
Hi to all followers of this thread.
Just to give an update: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more maintained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possebility to include also selinux what is needed for a kitkat-rom...
Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to invite him/her. To ask in forums (also in xda) is something what I do, but unfortunately the responding are not every time safe...
So I wish you all a happy new year, and lets work together to bring our device a little bit forward
SolarPlexus
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
VallNAr said:
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
Click to expand...
Click to collapse
Ask MARDON he made the kernel for Galaxy Ace - maybe he support Your work.
Any progress on the kernel? Is it on github?
Why does this not suport usb flash drives or can the function be ported
Gershy353
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
SolarPlexus said:
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
Click to expand...
Click to collapse
How is this done i have the sandisk dual flash drive but its useless on my device
Gershy353
Ah, you mean otg support, not sdcard seen as USB instead of mtp?
send with my Oneplus One (bacon) SlimKat Tapatalk
https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha.223252/
ALPHA STAGE GUYS, EXPECT BUGS, MAKE A BACKUP IN RECOVERY BEFORE FLASHING!!
THIS ROM IS MADE BY ONEPLUS, NOT ME.
Here we go, official L for the oneplus one (made by oneplus) is here, there are a few bugs which can be found in the main link above.
Happy flashing!
And Happy new year!
All credit goes to oneplus. I'm just sharing the link!
It's not cyanogen mod though!It's an alpha build but no one at the OPO thread hasen't installed it yet!
Sent from USS Intrepid NCC-1631
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
At least they are building their own rom!And happy new year guys!
Sent from USS Intrepid NCC-1631
I tried it but had an error about updater script. When i time i will try again
störte said:
I tried it but had an error about updater script. When i time i will try again
Click to expand...
Click to collapse
I haven't tested it yet, I'm not sure that I will. Cause of the bugs I am seeing on the OPO thread.
guys you need to unmount system before you flash otherwise the updater script will fail.
Great will retry
I'm using it right now. No real problems noticed so far except for a couple of crashes at first boot. It's really smooth. Pure AOSP.
Yes very pure.
Strange cant get into recovery anymore
Does anyone know if they're using the same sources as Cyanogen? (It had a weird name. CM started to suck when they started using it.)
Or is it PURE AOSP?
dugzino said:
Does anyone know if they're using the same sources as Cyanogen? (It had a weird name. CM started to suck when they started using it.)
Or is it PURE AOSP?
Click to expand...
Click to collapse
Pure CAF AOSP.
I can only recommend not to use it. My Recovery was deleted and i cant get into any Recovery anymore. I get only a chinese fastboot.. Tried to flash my Recovery via adb. On first boot it worked but then not anymore. So be very carefull
störte said:
I can only recommend not to use it. My Recovery was replaced and i cant get into any Recovery anymore. I get only a chinese fastboot.. Tried to flash my Recovery via adb. On firsat boot it worked but then not anymore. So be very carefull
Click to expand...
Click to collapse
Works perfect for me.
Thats strange. Anyway i flashed a recovery and deleted the system in order to restore a backup. It looks nice but the Recovery Problem must be solved in order for me to try again.
BUt i like the Wallpaper
störte said:
Thats strange. Anyway i flashed a recovery and deleted the system in order to restore a backup. It looks nice but the Recovery Problem must be solved in order for me to try again.
BUt i like the Wallpaper
Click to expand...
Click to collapse
I think you need to reflash recovery when you install it, which is easy to do from fastboot.
I did that. But even then i was not able to enter recovery
very very different modem, compared it against all the five I've got here (not all the previous modems) and can't see anything like it.
sha1 DD7A19EA09FF60485A6D8469F25C750A9AE627AE
md5 BA7C0A93BB63955408459ACA88BAAFFC
TeChNoC4AzY said:
I think you need to reflash recovery when you install it, which is easy to do from fastboot.
Click to expand...
Click to collapse
You would be correct. In fact, they specifically mention that in the instructions directly before Step 1.
This build does not have a built-in recovery
Click to expand...
Click to collapse
Well consider that it's build from their own source it's normal that it's asop-like but gonna give it a try tomorrow. Of course hope they will merge latest 5.0.3 that will come in these week and all other feature of cyanogenmod11S
confed said:
You would be correct. In fact, they specifically mention that in the instructions directly before Step 1.
Click to expand...
Click to collapse
rudi_j7 said:
guys you need to unmount system before you flash otherwise the updater script will fail.
Click to expand...
Click to collapse
How is that done?
(6/30/15) Newest LLFK for T-Mobile Note EDGE N915T Lollipop.
Now has TCP congestion control options with default TCP Westwood
This version is flashable using TWRP.
Features:
SELinux=Permissive option
init.d support
adbd insecure
TCP congestion controls: TCP options include Westwood, cubic, reno among others: default is Westwood
Modifications that need to be made when using LLFK kernel
1)In build.prop set
ro.securestorage.support=false
2)For those that use AllShare Cast you will need to do two things.
First, add the following line at the end of build.prop
wlan.wfd.hdcp=disable
second, you need to have the Xposed module Wanum Xposed installed. In Wanum select "security hacks" then check box of Fake system status
Download link:
https://www.dropbox.com/s/6bg9l8qqcmmh83x/llfk_permissive_initd_adbd_tcp_lpop.zip?dl=0
Check below for other information that might come in handy and good luck!
(06/11/15)New Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (lollipop)
I've added adb insecure to kernel. This gives you root access to modify /system on phone from a pc
Features:
SELinux = Permissive option
init.d support
adb insecure
download link
https://www.dropbox.com/s/kr7xb22449p497w/llfk_permissive_initd_adbd_lpop.zip?dl=0
(06/10/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T)
Two new flashable kernels. One for Lollipop the other for Kitkat.
Lollipop: This new version has init.d support so, for example, you can write scripts that run on boot up. (more below).
Features:
SELinux = Permissive option
init.d support
https://www.dropbox.com/s/k8w423ecoj1covs/llfk_permissive_initd_lpop.zip?dl=0
Kitkat:This version now has TCP congestion control options available (e.g. Westwood)
Features:
SELinux = Permissive option
init.d support
adb insecure (allows you to have r/w access to phone's /system from you pc)
TCP congestion control options
Thanks to JT man for testing
https://www.dropbox.com/s/jbifzsuztb73wpg/llfk_permissive_initd_adbd_tcp_kkat.zip?dl=0
Example of init.d script to automatically set SELinux=permissive given here
https://forums.oneplus.net/threads/how-to-selinux-permissive.314120/
couple notes on how-to-selinux-permissive
1)You only need have permissions of /sys/fs/selinux/enforce set to 644
2)Make sure permission of init.d script is 775
One more thing, knox based warnings can be silenced using wanum.
(05/27/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T) running Lollipop.
For those that miss having SELinux=Permissive on their T-mobile Note Edge running lollipop, here is a kernel
that supports this setting. The kernel is based on the Tmobile Note Edge Lollipop source code. The only thing that was
changed was a setting in the kernel's Makefile to allow the user to choose whether they want to have SELinux=Permissive
as described for the previous Kitkat version of LLFK below.
NOTE: This time around, the kernel is packaged as a zip file than can be directly flashed in recovery.
But before I go any further I need to give credit to @TEKHD for providing a zipped
version of the T-Mobile kernel I could modify and, in addition, for testing it.
Please buy him a well deserved cup of coffee!
Once you have flashed the kernel and rebooted you are ready to set SELinux=permissive by opening a terminal and typing
su
and
setenforce 0
To check it worked, go to settings > About device and you should see, under SE for Android status, that it is now set to Permissive.
An alternative way to change the setting with this kernel is to use the apk SeLinuxModeChanger. Unfortunately this apk is no longer
available at the play store but you can still download it from the F-Droid site.
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
A third option would be to set up an init.d script if your rom permits it.
I must admit, at the time of this writing, I'm still on KitKat and have yet to try this on my phone. I'll be checking out lollipop soon
but till then, let me know if/how it works. If successful I'll start adding a few more low lying fruit I've picked!
Remember to do a full nandroid back-up before trying this so your phone can return to its original state before trying llfk if needed.
The usual disclaimer applies!
Good Luck!
lollipop LLFK download link:
WAIT! Only one person has tried this version and although it worked for him, I still consider it beta at best. You have been warned!
WAIT! WAIT! One more thing: You need to do the following otherwise you may experience problems with WIFI:
Download the apk BuildProp Editor and use it to set
ro.securestorage.support=false (thanks @TEKHD for checking this)
WAIT! WAIT! WAIT! May be an issue with private mode not working (see http://forum.xda-developers.com/showpost.php?p=61033627&postcount=109 ). I did not have this problem on kitkit. I am unable to test till next week so if someone can check it out that would be great.
http://www.4shared.com/zip/Z8g1u3FHba/llfk_permissive_lpop.html
dropbox link
https://www.dropbox.com/s/ud84t2fc3n9sqdg/llfk_permissive_lpop.zip?dl=0
Below only applies to the KitKat version.
(04/07/15) Update:
Well, I had a little time and decided to add a feature to LLFK. So for now it has the following three capabilities.
1)Allows you to set SELinux = Permissive
2)adb insecure
3)init.d support
Here is the link for the tar file. (follow same instructions given below to install via ODIN):
http://www.4shared.com/archive/2PepSJcPce/llfk_permissive_initd_adbtar.html
Let me know if/how it works...
New features:
The kernel is now adb insecure. This was accomplished by replacing the adbd file in ramdisk with one due to @freeza. Big thanks to him (as in buy him a cup of coffee!) for giving me permission to use it. With adb insecure you can now remount system as r/w from your pc which can come in handy at times.
The kernel has init.d support (Allows you to run scripts from boot) by modifying the ramdisk using the instructions in STEP 1 (Making kernel ready) of the following post
http://forum.xda-developers.com/showthread.php?t=2287540
So this part is done for LLFK
For it to work, the user still needs to make some minor modifications (add a file and create a directory) in their rom. To do this, please follow all 4 parts of STEP 2 (Making Rom Ready) in the same post.
Once you have completed STEP 2 you are ready to try some scripts.
You can search the Internet for init.d scripts to try.
For example there are some init.d scripts in the later half of the following post to give you an idea.
http://en.miui.com/thread-5685-1-1.html
If folks can experiment to see what scripts work I will make a list and post it here.
Seems to work OK on Hyperdrive and Lab Rats (let me know otherwise).
CAVEAT: When testing whether init.d support was successfully implemented I had tried some scripts (like echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb; ) that should have modified some kernel settings at boot up. But as it turns out there are a set of scripts that run after boot up that supersede these settings. These scripts are in the file /etc/init.qcom.post_boot.sh. (some other neat stuff to play around with in there!) If you want those scripts to not take effect you can simply comment them out and then your init.d scripts will work.
The usual disclaimer and Good Luck
Original post 1/30/15
**********************************************************************************************************************************************************************
Hi. I thought I'd give out this kernel which allows one to set SELinux=permissive for a rooted T-Mobile Note Edge with base NK3. This setting is needed if you would like to run Linux on Android and, I believe Viper4Android if you are so inclined, as well as some other specialized apps (for future reference, let me know what apps you use that need this setting). Once you have loaded this kernel you can use the app SELinuxModeChanger, found in the play store, to set SELinux=Permissive and back to Enforcing. Note, this setting is maintained until you change it back in the app (rebooting will not change the setting). Anyways, what I am providing is a gzipped tar file that you can download, gunzip and then load on your phone using ODIN (version 3.07 worked fine for me, goes in PDA). Remember, this kernel is ONLY for the T-Mobile N915T NK3 rom. Actually, I have only tested it on the Lab Rats rom so hopefully it will work on other roms for T-Moble N915T with NK3 base.
As most folks like to have a name for their kernel I've decided to call this the "Low Lying Fruit Kernel" (LLFK) because it only has a minor change made to it. Indeed this kernel is about as low as it goes (lol) as not a single line of code is changed. I only changed an option in the Makefile from true to false. Details are given at the following github site.
https://github.com/mscion/Permissive-Kernel-N915T-EDGE/
Anyways, I've been using this kernel for over 10 days with no problems, but, of course , for those that try LLFK, the usual warnings apply! I am not responisble for anything that happens to your device as a conseqence of
using this kernel. Indeed you have to be crazy to try it as I have zero experience at this! You also might want to read this before you try setting SELinux=permissive:
http://en.wikipedia.org/wiki/Security-Enhanced_Linux
One more thing, while my preference is that an experienced dev make a kernel worthy of the N915T EDGE, I am open to suggestions to make some more modifications assuming the request are somewhat consistent with the philosophy of LLFK.
Thanks to @jimmydene84 for boot.img and @deeznutz1977 for testing!
Don't forget to do a full back up! Good luck!
Kernel Download link: For SELinux=Permissve option only
http://www.4shared.com/archive/oH5fE053ba/llfk_permissivetar.html
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
VenpaCasa said:
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
Click to expand...
Click to collapse
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Awesome @mscion
deeznutz1977 said:
Awesome @mscion
Click to expand...
Click to collapse
Thanks! What would be even more awesome is if someone tries it and it works! lol.
I'll flash it now kind sir
mscion said:
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Click to expand...
Click to collapse
Omg dude if ur really serious, hell yeah I'm willing to test. I'm extremely greatful n lost for words right now. Thanks so much for just attempting ?? at least. Made my day lol
deeznutz1977 said:
I'll flash it now kind sir
Click to expand...
Click to collapse
I hope you mean Odin it! Drum roll please....
mscion said:
I hope you mean Odin it! Drum roll please....
Click to expand...
Click to collapse
kernel is not se android enforcing
@mscion you still had to use the selinux changer app correct?
deeznutz1977 said:
kernel is not se android enforcing
Click to expand...
Click to collapse
Hi @deeznutz1977. Depending on rom, I think when you boot up you will get that message. Please check in settings > about device and see what SE for android is showing. For now I have pulled the kernel because I unwittingly used the boot.img from lab rats rom to pack in my zImage file that allows permissive setting, cause I thought it was not modded. I am currently waiting to hear from @jimmydene84...
deeznutz1977 said:
@mscion you still had to use the selinux changer app correct?
Click to expand...
Click to collapse
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
mscion said:
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
Click to expand...
Click to collapse
Stock deodexed. And sorry about not reading the op. Don't you know that all of the cool people don't read ops
Sent from my SM-N915T using Tapatalk
@mscion I asked jimmydene to pm you ...
deeznutz1977 said:
@mscion I asked jimmydene to pm you ...
Click to expand...
Click to collapse
Thanks very much! We're all good. I'm putting the link back up shortly.
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
VenpaCasa said:
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
Click to expand...
Click to collapse
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
mscion said:
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
Click to expand...
Click to collapse
Honestly your awesome. I was starting to regret my purchase too. I'll assume you weren't asking me if it's ok but if you were, yeah that's fine. I'm actually any using that ROM
EDIT: Just saw your edit n thanks (to both) that's so awesome! I owe you guys!
When ubr done are you going to post here or a new thread?
VenpaCasa said:
When ubr done are you going to post here or a new thread?
Click to expand...
Click to collapse
Just pm'd you with link. If it works I'll post it in this thread.
Port is not my work. It's by @kavatzas7, originally posted here - http://forum.xda-developers.com/showpost.php?p=69580000&postcount=214. That one only works on unlocked bootloader, so I swapped the boot img with stock Sony one, for use on locked. I also made many framework and system app mods, (shown in screensshot), including menus, toast, backgrounds and scrolling navbar, by @Ticklefish. If you want the rom and don't like my mods, just download both and replace boot img.
Notes...
- Flashing rom with stock boot img will remove your recovery, so you'll have to reflash recovery.
- Attempting to flash kavatsaz7's rom with locked bootloader will result in black screen, with no boot, even to recovery. You'll have to use Flashtool to get kernel/rom back on your phone.
https://mega.nz/#!Is0ShbCY!8fLKUYPmFt7is0M7jyjLr_ApiK7maL-Ydg5zuYMv0Ec
1/16
Updated with some fixes. Not so messy looking anymore. Update does not include scrolling navigation bar. Let me know if you want it, and can't do it.
Few more...
Is now all problems göne ?
Murtie said:
Is now all problems göne ?
Click to expand...
Click to collapse
I didn't change anything in the build, but I worked out most of the visual bugs with 3rd-party apps, like black-on-black menus, etc. You can use Holo Themer per app if you need to. For fm radio, use a different app from Play Store. I tested out RadioFM, and it works fine.
Can i instal this port for so-02f docomo with locked bootloader??
zanahar said:
Can i instal this port for so-02f docomo with locked bootloader??
Click to expand...
Click to collapse
Sorry, I don't know much about that phone. From what I remember in other threads, it is the same, but I can't say for sure...
levone1 said:
Sorry, I don't know much about that phone. From what I remember in other threads, it is the same, but I can't say for sure...
Click to expand...
Click to collapse
It means this port use stock boot img??
zanahar said:
It means this port use stock boot img??
Click to expand...
Click to collapse
Original port has modified boot img, but I replaced it with stock one for locked bootloader, (read op).
levone1 said:
Original port has modified boot img, but I replaced it with stock one for locked bootloader, (read op).
Click to expand...
Click to collapse
ok thank... i will try ... and give riview soon
levone1 said:
I didn't change anything in the build, but I worked out most of the visual bugs with 3rd-party apps, like black-on-black menus, etc. You can use Holo Themer per app if you need to. For fm radio, use a different app from Play Store. I tested out RadioFM, and it works fine.
Click to expand...
Click to collapse
Which radio application you used and it's worked?
kavatzas7 said:
Which radio application you used and it's worked?
Click to expand...
Click to collapse
Radio Fm - https://play.google.com/store/apps/...app&pcampaignid=APPU_1_M6ZjWIibG4bXmAGN05PIBQ
Ah, ok...because i thought that you talking about a real "fm radio" app based on fm mobile antenna resever, not in an internet radio app...
I just installed the ROM and it already restarts a few times, the phone currently is installing all the apps from Google Play Store..
edit:
It happens randomly or if I open/select certain settings that provided..
BTW can I change the transparent notification off?
@levone1 : Flashed your modded ROM but it's getting restarted repeatedly between bootanimations...
giriz1c said:
@levone1 : Flashed your modded ROM but it's getting restarted repeatedly between bootanimations...
Click to expand...
Click to collapse
OK, I'll check it out. I've been messing with Dstrikers rom for a while now, so can't remember issues exactly. First question always did you do a full wipe, (data, system, and caches)?
I'll try to flash today and see...
thesims2customs said:
I just installed the ROM and it already restarts a few times, the phone currently is installing all the apps from Google Play Store..
edit:
It happens randomly or if I open/select certain settings that provided..
BTW can I change the transparent notification off?
Click to expand...
Click to collapse
It's been posted about this port that you will get reboots at first, but they will stop. I didn't port it, so can't help with technical stuff.
For notifications you can try LPThemer from Xposed, or replace your system ui with stock one, (you will also lose other systemui mods) or decompile systemui apk, and search xml files for color b32c3539, and change it to ff2c3539.
BTW, if anyone wants to try, I made a similar mod with some improvements for latest Dstrikersz1 build.
https://forum.xda-developers.com/showpost.php?p=70387004&postcount=2062
giriz1c said:
@levone1 : Flashed your modded ROM but it's getting restarted repeatedly between bootanimations...
Click to expand...
Click to collapse
Just flashed with full wipe and clean install and everything good...
levone1 said:
It's been posted about this port that you will get reboots at first, but they will stop. I didn't port it, so can't help with technical stuff.
For notifications you can try LPThemer from Xposed, or replace your system ui with stock one, (you will also lose other systemui mods) or decompile systemui apk, and search xml files for color b32c3539, and change it to ff2c3539.
BTW, if anyone wants to try, I made a similar mod with some improvements for latest Dstrikersz1 build.
https://forum.xda-developers.com/showpost.php?p=70387004&postcount=2062
Click to expand...
Click to collapse
Ah, I see.. But it will start restart by itself if you click certain settings.
Thanks for answering. I found another problems tho, the internet speed seems so slow, it takes minutes to download small files from Play Store, even restoring things from WhatsApp took ages. And it seems killed app in the background because, once I open a messenger, it will flood by notifications.
thesims2customs said:
Ah, I see.. But it will start restart by itself if you click certain settings.
Thanks for answering. I found another problems tho, the internet speed seems so slow, it takes minutes to download small files from Play Store, even restoring things from WhatsApp took ages. And it seems killed app in the background because, once I open a messenger, it will flood by notifications.
Click to expand...
Click to collapse
It's a port, so not surprising to find bugs. The best part about eXistenZ is probably the customization, which is all there. Overall, it's a solid ROM, and the bugs are, for the most part, in the realm of extras, (although slow Internet is more of a real problem, but I haven't experienced that). If you want more of stability and less of extras, go for dstrikersZ1 ROM.
BTW - I never did quite finish modding this one, it's kind of messy looking. I got sidetracked with dstriker... I'll probably revamp this one and re-post.
levone1 said:
It's a port, so not surprising to find bugs. The best part about eXistenZ is probably the customization, which is all there. Overall, it's a solid ROM, and the bugs are, for the most part, in the realm of extras, (although slow Internet is more of a real problem, but I haven't experienced that). If you want more of stability and less of extras, go for dstrikersZ1 ROM.
BTW - I never did quite finish modding this one, it's kind of messy looking. I got sidetracked with dstriker... I'll probably revamp this one and re-post.
Click to expand...
Click to collapse
So it is just me who have the problem with internet, is it because "doze" mode or something because I find that my phone will go to its deep sleep often, it does save battery but I don't quite like it, I keep missing phone calls or texts from people. Guess I will go back to DstrikersZ.
Can someone who has knowledge on kernels inject KCAL on the 10q kernel please. All that's needed. I tried learning. To complicated for my bones.
i want this too
I will gladly pay for your efforts. No joke! Thanks again.
Just asking, why do you want this?
Still_living714 said:
Just asking, why do you want this?
Click to expand...
Click to collapse
To use color control and get rid of the burn in the stock kernel gives. I like the stock kernel I'm fine with it in reference to performance. Just want to cure the screen with KCAL injected into it.
storm68 said:
To use color control and get rid of the burn in the stock kernel gives. I like the stock kernel I'm fine with it in reference to performance. Just want to cure the screen with KCAL injected into it.
Click to expand...
Click to collapse
I'm starting to get the ghosting affect since I run my phone on maximum brightness all the time. How would kcal take care of that? I've read if you activate comfort view you can get rid of it but I don't like how it looks....
Still_living714 said:
I'm starting to get the ghosting affect since I run my phone on maximum brightness all the time. How would kcal take care of that? I've read if you activate comfort view you can get rid of it but I don't like how it looks....
Click to expand...
Click to collapse
Not the same. It's a saturation issue.
storm68 said:
Not the same. It's a saturation issue.
Click to expand...
Click to collapse
Have you tried using CF Lumen to adjust the colors. It only does RGB channels but I've gotten my values to look pretty good to me and I don't notice any retention anymore with the settings I'm using.
Give them a shot and see.
KUSOsan said:
Have you tried using CF Lumen to adjust the colors. It only does RGB channels but I've gotten my values to look pretty good to me and I don't notice any retention anymore with the settings I'm using.
Give them a shot and see.
Click to expand...
Click to collapse
Yeah I've tried. Not the same. Can't adjust saturation
anyone get kcal on stock 10q
storm68 said:
Can someone who has knowledge on kernels inject KCAL on the 10q kernel please. All that's needed. I tried learning. To complicated for my bones.
Click to expand...
Click to collapse
I am attempting to do so now, it's compiling as I type this. Hopefully it will go smoothly without any errors.
I'm using the v10q sources from LG and copied the patch from USA-RedDragon's github.
The kernel compiled fine.
I have never repacked a boot image before, so not sure if I did that correctly. - Apparently it is working :good:
Also removed the root checker service.
Remember to flash root again afterwards.
Edit: I have added boot image for 10k as well, after request from @dimm0k
askermk2000 said:
The kernel compiled fine.
I have never repacked a boot image before, so not sure if I did that correctly. That's why I uploaded the kernel itself as well.
I used the kernel-dtb image, if that was the correct choice... it was the closest match in size of the old zImage.
Also removed the root checker service in ramdisk.
Remember to flash root again afterwards.
Edit: I assume the dtb image is the correct one as I don't see the device tree anywhere else. So I'll upload that as well in case anyone wants to repack their own boot.img
gz-image.zip is simply kernel without device tree blobs. Probably of no use to anyone.
Click to expand...
Click to collapse
This is great. I'll try it after work.
askermk2000 said:
The kernel compiled fine.
I have never repacked a boot image before, so not sure if I did that correctly. That's why I uploaded the kernel itself as well.
I used the kernel-dtb image, if that was the correct choice... it was the closest match in size of the old zImage.
Also removed the root checker service in ramdisk.
Remember to flash root again afterwards.
Edit: I assume the dtb image is the correct one as I don't see the device tree anywhere else. So I'll upload that as well in case anyone wants to repack their own boot.img
gz-image.zip is simply kernel without device tree blobs. Probably of no use to anyone.
Click to expand...
Click to collapse
Just tried it, I had one major screw up and forgot to flash magisk and it force encrypted my device and i had to format my internal storage, but after a fresh flash with magisk this time the kernel seems to work right with kcal, thanks!
ivoh95 said:
Just tried it, I had one major screw up and forgot to flash magisk and it force encrypted my device and i had to format my internal storage, but after a fresh flash with magisk this time the kernel seems to work right with kcal, thanks!
Click to expand...
Click to collapse
odd when I tried it said invalid flash can I get a new link
---------- Post added at 08:05 PM ---------- Previous post was at 07:59 PM ----------
askermk2000 said:
The kernel compiled fine.
I have never repacked a boot image before, so not sure if I did that correctly. That's why I uploaded the kernel itself as well.
I used the kernel-dtb image, if that was the correct choice... it was the closest match in size of the old zImage.
Also removed the root checker service in ramdisk.
Remember to flash root again afterwards.
Edit: I assume the dtb image is the correct one as I don't see the device tree anywhere else. So I'll upload that as well in case anyone wants to repack their own boot.img
gz-image.zip is simply kernel without device tree blobs. Probably of no use to anyone.
Click to expand...
Click to collapse
I tired this but when i went to flash it said invalid file format could you please give a new link
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
okay i extracted the zip and in twrp said install image and then selected boot and flashed magisk
ivoh95 said:
Just tried it, I had one major screw up and forgot to flash magisk and it force encrypted my device and i had to format my internal storage, but after a fresh flash with magisk this time the kernel seems to work right with kcal, thanks!
Click to expand...
Click to collapse
dudeawsome said:
okay i extracted the zip and in twrp said install image and then selected boot and flashed magisk
Click to expand...
Click to collapse
Ah so it worked, nice. You're welcome
askermk2000 said:
Ah so it worked, nice. Your welcome
Click to expand...
Click to collapse
Yep it works great thanks rctd and kcal just put that you have to extract the zip and in TWRP click image then the IMG and select boot and flash then flash magisk or Sunday bc I was confused at first.
Also the battery and smoothness seems much better then the weta kernel
dudeawsome said:
Yep it works great thanks rctd and kcal just put that you have to extract the zip and in TWRP click image then the IMG and select boot and flash then flash magisk or Sunday bc I was confused at first.
Also the battery and smoothness seems much better then the weta kernel
Click to expand...
Click to collapse
Yes not everyone is aware of that option in twrp.
I pretty much just took the official sources from LG and added Kcal, nothing else, and it compiled flawlessly with google gcc 4.9 - I guess that something, is it not common for these android sources from certain companies to be botched or incomplete..?
Anyway. If anyone wants to use it in their ROM then that fine by me. @texasaggie1 or anyone else
@askermk2000 slightly off topic, but would you be able to also do this for the 10k kernel too or maybe provide some instructions on how to compile this to try on my own?
dimm0k said:
@askermk2000 slightly off topic, but would you be able to also do this for the 10k kernel too or maybe provide some instructions on how to compile this to try on my own?
Click to expand...
Click to collapse
I'm downloading the 10k sources now - or can I use 10n ? I already have that, but maybe it's arb 1... seem to recall that 10n or 10o was arb1