Database Develop

[KERNEL][G800F][exynos][G800FXXU1*][TW Only][MM Only]Custom Kernel - Galaxy S5 Mini Original Android Development

hennymcc:
Important notice:
- You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
- Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
- The image is only for S5 Mini SM-G800F (Exynos)
- The kernel is not tested well. It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an OTG device drains too much power)
- Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Side note: Tripping KNOX counter might break some Samsung applications even after a factory reset. This might be due to secure storage(which is fixable), but for now be cautious if you depend on these features! This image will likley damage the Qualcomm variant of the S5 Mini, do not flash if you have a G800H!
Hello! :laugh:
I've been working on a custom kernel for a while for personal use but I thought some of you might like it.
Current feature list:
Patched to Linux 3.4.113
Fading LED notification (default disabled)
Added row I/O Scheduler
Added zzmoove CPU Governor(with temperature export)
Added PIE network scheduler(supposed to reduce latency, default disabled)
DriveDroid support
Universal Control Interface[UCI] (use the Synapse app to configure)
USB OTG
Boeffla sound engine (Only configurable via Synapse! default disabled)
Powersuspend with LCD panel hooks
1.5GHZ clock speed on processors with revision 2 and above
Double Tap 2 Wake
Voltage Control
MDNIE Hijack
F2FS Support
Haptic Feedback for soft keys
Compiled with Self built Linaro 5.3 toolchain
This kernel is currently only designed to work with the corresponding TouchWiz ROM and likely won't be able to boot custom ROMs. KitKat/Lollipop TouchWiz is also not supported!
If you have any questions about the included features (how to enable, what they do) you may ask in the Q&A until I update the thread.
About 1.5GHZ clock speed
So, as it turns out, Samsung had already done the work to push the 3470 to 1.5GHZ. The frequency tables were already there and all that needed to be done was to remove a soft limit set on it and voila! 1.5GHZ! The catch is that these tables only applied to the second revision of the SoC and above.
Possible reasons why Samsung set the limit:
The S5 mini comes out with both the older and newer revisions of the 3470 and Samsung wanted to avoid getting in legal trouble for selling a higher clocked phone as the same product
The higher clock speeds legitimately can damage the phone
As I don't have multiple S5 Mini's at hand I can't prove the first point, but the second point is more likely true. If you don't feel comfortable with the higher clock speeds you may lower the maximum to 1.4GHZ via Synapse, but the default clock is always 1.5GHZ due to the way in which the frequency controller works.
Current status : BETA
Credits:
andip71(Boeffla sound), faux123(Powersuspend), FrozenCow(DriveDroid support), ZaneZam(zzmoove), Linux Foundation(kernel patches), AndreiLux(Voltage patches for INT and MIF bus), Yank(MDNIE hijack), Samsung(F2FS)
On-board BusyBox by meefik https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=en
The authors are not responsible for the way in which their features have been implemented in this kernel. Do not post bug reports to them!
Flashing procedure will be the same as with this kernel.
Download current image here:http://forum.xda-developers.com/devdb/project/?id=10241#downloads
Chaneglog:
Code:
1.0
-Initial Release
1.1
-ZZMoove Update to 1.0 Beta 8
- Linux Update to 3.4.108
- Toolchain update
- 1.5ghz unlock for higher revision SoC's
1.2
- Ramdisk update
- Double Tap 2 Wake!
- UCI update
- USB OTG now permanently enabled
1.3
- Voltage Control (CPU, GPU, bus)
- Fixes for DT2W
- Linux Update to 3.4.109
1.4
- Intelliactive Removed
- Linux Update to 3.4.110
- MDNIE Hijack
1.4_L
- Lollipop Variant Now Live
1.4_L2
- Second Lollipop release
- Fixed OTG
- System partition can be remounted again
- Removed Frandom (Does not work so well in Lollipop)
1.5
- KitKat support terminated
- Fix annoying bootloader warning ("KERNEL IS NOT SEANDROID ENFORCING")
- F2FS Drivers updated and F2FS support improved (/data and /cache)
- Patch to Linux 3.4.111
- UKSM removed due to stability concerns
- SELinux policy support update (Latest SuperSU betas might need this)
- Switch to self built linaro toolchain
1.6
- Update to Linux 3.4.112
- F2FS drivers updated
1.7
- F2FS drivers update
- NTFS support enabled (eg. for reading USB HDDs)
- Kernel side haptic feedback on soft keys added (see second post)
1.8
- patch to 3.4.113
1.9
- Switchable OTG
2.0
- Updated to MM
- No longer need to install BusyBox manually to use Synapse
XDA:DevDB Information
G800F Custom Kernel, Kernel for the Samsung Galaxy S5 Mini
Contributors
CurtisMJ
Source Code: https://github.com/CurtisMJ/g800f_custom_kernel
Kernel Special Features: Boeffla Sound, Fading LED, Linux 3.4.113, row I/O Scheduler, zzmoove CPU governor, PIE netsched, DriveDroid support, UCI, USB OTG, DT2W, Voltage Control, MDNIE Hijack, F2FS, Haptic feedback
YOU MAY NEED TO REFLASH SUPERSU AFTER FLASHING THE KERNEL!
Version Information
Status: Beta EOL
Current Beta Version: 2.0
Beta Release Date: 2017-03-07
Created 2015-06-08
Last Updated 2017-03-07

Reserved

OTG switching
Credit to tobigun for the original code (I actually attempted it at some point but failed miserably).
Execute the commands in a terminal:
Turn on OTG
Code:
su -c echo OTG > /sys/class/sec/switch/otg_cable_type
Turn off OTG
Code:
su -c echo USB > /sys/class/sec/switch/otg_cable_type
(Haven't touched Synapse in forever, cannot make sense of it anymore, so no Synapse switch soz)
Synapse Issues
I had some trouble with colour choosers crashing Synapse under specific conditions. If Synapse keeps crashing when picking colours for MDNIE, please try the custom build available in the downloads section of this project.
IF THE DEVICE IS CRASHING WHEN USING SYNAPSE, THEN YOU HAVE LIKELY SET UNSTABLE SETTINGS! SYNAPSE WILL NOT PREVENT THIS, SO PLEASE BE CAREFUL WHEN CHANGING SETTINGS!
There are two ways to recover:
- Use your recovery to delete Synapse's data folder
- Factory Reset your device (Only in extreme cases)
Using PIE netsched:(likely not working with Android at this point in time)
Run following in root terminal or as init.d script
Code:
tc qdisc replace dev wlan0 root pie
tc qdisc replace dev p2p0 root pie
tc qdisc replace dev rmnet0 root pie
ZZMoove and profiles:
The zzmoove governor is highly recommended. It can be set to various profiles to mimic the benefits of various other governors. It'll even ensure the device doesn't overheat!
The profile can be set by setting the "profile number" tunable in Synapse to one of the number values mentioned here. Setting it will change a bunch of other tunables. You'll need to restart Synapse after setting it and save the changes for future application.
Notes on DVFS
Samsung's DVFS feature in their TouchWiz ROMs seems to get a bit shouty when anything other than the "interactive" CPU governor is active. It could also be the cause of rare kernel panics relating to CPU frequency tables(frequency controller expects something from the governor, governor doesn't deliver, panic). Since it also seems to cause a couple other unrelated issues, I'd recommended simply disabling it altogether(the easiest way being via Xposed)
Double Tap 2 Wake
This feature allows you to wake the device by double tapping on the screen while it is off. NOTE:Deep sleep is near totally inhibited while this feature is active, this means extra battery may be consumed. On a tweaked ROM you'll get 2-3%/hr on full standby, on non tweaked you'll get about 4-5%/hr, please keep this in mind while using the feature! Android OS suspension should be unaffected. The feature disables itself when a Samsung branded flip cover is closed, including S-View covers(no double tapping on the window). The feature makes use of the light and proximity sensors in order to detect whether the device is in a dark enclosed place (eg. A pocket) and disables itself in these situations as well in order to prevent accidental wakes (though that may still happen...)
MDNIE Hijack Example
Profile based of iPhone 6+ screen:
R: FF 00 00 - G: 12 FC 12 - Bu: 00 00 FF - C: 12 FF FF
M: FF 00 FF - Y: FF FF 00 - W: FF FF FF - Bl: 00 00 00
Feel free to post any other nice looking profiles you find
Init.d in Lollipop
I did not add Init.d support when building the Lollipop variant's ramdisk. Instead, /su/su.d should be used to run boot scripts. The functionality is exactly the same as the old Init.d.
Haptic feedback on soft keys
In order to avoid conflict with ROM side solutions, haptic feedback is disabled by default. It can be enabled via the following command which can be run as a boot script (eg. in /su/su.d). Command must run as root.
Code:
echo 1 > /sys/class/misc/abov_touckey/vibrate
NOTE: Above "touchkey" was misspelled in code. It should be fixed in a future update. Sorry for any inconvenience
still not fixed lol
Extra Compatibility Notes:
[url]http://forum.xda-developers.com/showpost.php?p=62226500&postcount=2[/URL]

Awesome, thanks !
Installed it and testing now

After a few days of testing !!! All I can say is, Great Kernel :good:
Good performance, great battery life
No issues so far.:highfive:

Working fine on G800FXXU1AOE3

And works great on G800FXXU1AOG2 too.

Again big Thanks Curtis ! :angel:
kernel is damn good.
Games running very fast for me with the new updated kernel
The 1.5Ghz CPU overclock is .. awesome
For additional gaming performance you can lock the GPU Frequency like this:
Shell command:
cd sys/module/mali/parameters
echo 533 > mali_dvfs_control
thats it, gpu locked to 533 mhz. Thanks to hennymcc for this commands
for example:
GTA San Andreas running now with maximum resolution+visibility graphical settings
Solid 30+ FPS :cyclops:

Sorry for noob question - can someone show me the exact syntax to enter in Terminal (or procedure) to activate OTG ? I don't seem to figure it out .

seaman5705 said:
Sorry for noob question - can someone show me the exact syntax to enter in Terminal (or procedure) to activate OTG ? I don't seem to figure it out .
Click to expand...
Click to collapse
To turn on:
Code:
su -t echo 1 > /sys/devices/virtual/sec/switch/otg
And off:
Code:
su -t echo 0 > /sys/devices/virtual/sec/switch/otg
Will ask for root.
EDIT: Enter exact commands in terminal emulator or adb shell

Thanks Curtis , but something is wrong in my case . It doesn't work and I don't understand why . After running the script , I granted the root access
, everything seemed to be ok , but nothing happens when I connect and USB key which is recognized in my S4 phone .

seaman5705 said:
Thanks Curtis , but something is wrong in my case . It doesn't work and I don't understand why . After running the script , I granted the root access
, everything seemed to be ok , but nothing happens when I connect and USB key which is recognized in my S4 phone .
Click to expand...
Click to collapse
Does anything else work? OTG also gets reset on boot, maybe it needs to be in an init.d script. I'll admit, I don't have an OTG cable to test, perhaps I should get hold of one, but the code definitely creates the right behavior (exactly the same as the other OTG kernel around here actually). Maybe switchable isn't the right way to go about it and OTG must be enabled permanently. I'll have to look into this, but in the meantime could you perhaps test with the other OTG kernel and see if it works? Also, the stick maybe might not be automatically mounting. Run "mount" in a terminal and see if it pops up. Apologies for the inconvenience.

CurtisMJ said:
Does anything else work? OTG also gets reset on boot, maybe it needs to be in an init.d script. I'll admit, I don't have an OTG cable to test, perhaps I should get hold of one, but the code definitely creates the right behavior (exactly the same as the other OTG kernel around here actually). Maybe switchable isn't the right way to go about it and OTG must be enabled permanently. I'll have to look into this, but in the meantime could you perhaps test with the other OTG kernel and see if it works? Also, the stick maybe might not be automatically mounting. Run "mount" in a terminal and see if it pops up. Apologies for the inconvenience.
Click to expand...
Click to collapse
No, it will not mount . I tested and OTG works with henny's kernel . Otherwise you made a great kernel - thanks for your work and your advices !

seaman5705 said:
No, it will not mount . I tested and OTG works with henny's kernel . Otherwise you made a great kernel - thanks for your work and your advices !
Click to expand...
Click to collapse
Attached is a build of the kernel with OTG enabled on a permanent basis. If you would not mind, could you test to see if it works? If so it will be done this way in future release, if not I will have to have a good look at any related code...
(P.S, sorry for the wait, my dual-boot was giving me issues)

CurtisMJ said:
Attached is a build of the kernel with OTG enabled on a permanent basis. If you would not mind, could you test to see if it works? If so it will be done this way in future release, if not I will have to have a good look at any related code...
(P.S, sorry for the wait, my dual-boot was giving me issues)
Click to expand...
Click to collapse
Yes , OTG works with this kernel . Great !
Note that after flashing, another reboot is needed to have the usb key properly mounting and poping up the file explorer with the key's content on connection .
Thanks !

New Version!
New version of my custom kernel released. Now includes Double Tap 2 Wake.

Is it possible to add voltage control to your kernel ? thanks .

CPU Voltage control is now implemented. Will work on a Synapse interface and the int and mif buses later today.

New Version!
Voltage control, Linux patches and fixes for DT2W waking up the screen while a call is in progress(sorry 'bout that)

Working great - I achieved good undervolting . Thanks
Hope to see a modified kernel for Lollipop too .

Related

NOTICE: This is COMPATIBLE with ALL Vivid Rooted Stock and Custom ROMs
For frequency control use fauxclock from Google Play
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to hack this kernel. If you use my modified kernel source in parts or in its entirety, I kindly ask you mention its origins and to send me a github pull request or PM whenever you find bugs or think you can help improve my kernel hack further. This way the entire community will truly benefit from the spirit of open source. Thank you
​
Hi XDA members and fellow Vivid users:
This is my tenth kernel hack. I want to thank Erasmux, and several others I cannot recall for inspiring me to venture into this unfamiliar territory for me.
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
​
THIS KERNEL is BASED ON HTC Source Code. So it is COMPATIBLE ONLY WITH HTC ICS Vivid Builds.
Please DO NOT use any task killers, they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibilities (Forced Close).
CleanCache (via ZCache backend)
ZCACHE is a new technology I introduced to HTC Kernel. ZCACHE is a compressed cache similar to ZRAM but the similarity ends there. ZCache is meant to provide as many "cleancache" pages (non-dirty or untouched "virgin" memory) to apps that request for new memory. CleanCache is very easy to allocate and no additional penalty are required to hand them out, so having more CleanCache pages will improve performance. Under heavy memory pressure, often times the kernel will NOT have enough CleanCache pages, so the kernel has to do EXTRA work to reclaim dirty cache pages and clean them for the new apps that's requesting for them. The described process creates a performance hit for the kernel and the app, so the idea is to use compression to create more CleanCache pages available for use. Of course there's a penalty to pay for using compression, but the trade-off between compression penalty and the penalty for reclaiming dirty cache pages and allocating them after cleaning is smaller for compression, so in the end, CleanCache should add more performance.
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Joe's RCU (Optimized for Small SMP systems)
Joe Korty has created an RCU for small SMP systems (> 32 cores). His approach is to isolate all the Garbage Collection (GC, a slow time consuming but necessary processing) to a single core, thus allowing other cores to ONLY work on real required processing. This will allow the additional cores to complete their assigned tasks as fast as possible (not bogged down by GC) then immediately go back to a suspended state (saving battery).
Fast No Hz RCU (Optimized for SMP operations)
Fast NoHz is an optimized version of the traditional Tree RCU. Many new kernels are using the Tickless NoHz design. This RCU is tailored and designed to work with the new NoHz kernel system.
SmartAssV2 Governor (Balanced)
This governor has a built-in "profile" similar to SetCPU, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Interactive Governor (Performance)
This governor is designed to put more priority to User Interface (UI aka Apps) tasks, therefore appears more responsive then the traditional OnDemand governor. So if you want the smoothest UI interaction, this governor is for you...
Brain F*ck Scheduler - (BFS)
This scheduler is designed to be simple and speedy tailor specifically for user interface type systems such as desktop/smart phone devices where user interaction is MORE important than serving 1 million web requests (CFS, the default scheduler) at the same time (think of nimble desktop workstations vs large corporate servers).
SLQB - (SLAB allocator with Queue)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate). Not all kernels are using SLQB including CM7 main line...
Fair Budget Queue (BFQ I/O scheduler)
This I/O scheduler is an improvement on top of Completely Fair Queue (CFQ). CFQ is fair in terms of time but not in terms of throughput / bandwidth, so BFQ make sure that both time and throughput / bandwidth are balanced across all requests.
Kernel Files:
******* Ice Cream Sandwich (Android 4.0.x) ******* (Linux 3.0.33)
[ CFS ] (Ultimate Edition) *** S-ON ***
The File ==> Vivid Kernel 007 (1.73 GHz, GPU @ 320MHz, ZRAM) <==
[ CFS ] (Ultimate Edition) *** S-OFF ***
The File ==> Vivid Kernel 007 (1.73 GHz, GPU @ 320MHz, ZRAM) <==
[ Optional: ]
Files to DISABLE Sweep2Wake:
http://forum.xda-developers.com/showpost.php?p=25538084&postcount=6616
[ For Kernel Devlopers ONLY: ]
The File ==> My Global VDD_TABLE for under volt patch <==
The File ==> KGSL Ring Buffer Power Management Patch for Cordy and Ninja Jump <==
Optional Under voltage: Version 0.1.4+ ONLY
Code:
[ to over volt ALL frequencies by 25000 uv (microvolts) ]
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to under volt ALL frequencies by 25000 uv (microvolts) ]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to set a specific frequency (ie 1.18 GHz)
with a specific voltage (ie 1.0875 volts) ]
echo "1188000 1087500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
CPU Frequency Voltage Table Example
Code:
192000: 812500
310500: 812500
384000: 812500
432000: 812500
486000: 837500
540000: 850000
594000: 862500
648000: 875000
702000: 900000
756000: 925000
810000: 937500
864000: 962500
918000: 962500
972000: 962500
1026000: 975000
1080000: 987500
1134000: 1000000
1188000: 1012500
1242000: 1025000
1296000: 1050000
1350000: 1075000
1404000: 1100000
1458000: 1112500
1512000: 1125000
1566000: 1150000
Optional: Stock Clock Frequencies for Dual CPUs
Code:
su
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpu1/cpufreq/online
echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
Optional: ZRAM (Compressed RAM swap space )
Code:
su
mkswap /dev/block/zram0
swapon /dev/block/zram0
Low Voltage - Under Volt the processor, therefore uses Less Battery, but NOT ALL CHIPS can handle Under Volt.. If you experience instability, try the Stock Voltage Version.
Stock Voltage - Uses the voltage values from ORIGINAL HTC Kernel Source.
There are NO PERFORMANCE DIFFERENCE between the Under Volted and Stock Voltage versions!
Installation Instructions:
Here's a step by step instruction to install this kernel:
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
NEWS BULLETIN:
Ice Cream Sandwich Version 007 is out. More intelligent intellidemand! Completely free yourselves from mpdecision, thermald and now with intellidemand, complete CPU/Thermal Management by the kernel.
Please don't hesitate to talk among yourselves and help each other out... The XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
BUGS:
Not All CHIPS ARE CREATED EQUAL
TO DO:
version 1.x.x -- Haven't thought about it yet...
History:
[ Change Log ]
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My Github Complying with GPL and XDA rulez
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below

Awesome!! Can't wait to try it!
Sent from my HTC PH39100 using XDA

Thank you so much.. faux123~

Faux your a god.

Sweet....
Anyone install yet and have feedback to report?

Boot Loop
No go for me.
It gave me a reason to update to the new AT&T RUU.
May try again after clean install.

Going to flash stock rooted cwm then maybe this will report back.

ismoore said:
Anyone install yet and have feedback to report?
Click to expand...
Click to collapse
Well it's fast in quadrant scores. I got like a 3560 and in that test CPU scores are significantly higher. Antutu benchmark scores with no overclock are the same as stock. All else felt the same. I'm running this kernel with WC's 3.6 Vivid ROM. Still appreciate the contribution faux! I have run your kernels on other phones and they are always the best!

Now why would Window XP forget my android 1.0 drivers for hboot? can't flash anything in hboot now...

Great, thanks for the info. May try this tonight when I get home. Thanks for your efforts faux.
brwnohno said:
Well it's fast in quadrant scores. I got like a 3560 and in that test CPU scores are significantly higher. Antutu benchmark scores with no overclock are the same as stock. All else felt the same. I'm running this kernel with WC's 3.6 Vivid ROM. Still appreciate the contribution faux! I have run your kernels on other phones and they are always the best!
Click to expand...
Click to collapse

My wifi isn't working, it just says "turning on...". Other than that, it works great

**** mines bootlooping its get the att and loops what should i dooo? I got the latest cwm, and hboot, stock rooted rom. Is it because I let it try to boot right after I flashed the boot.img and didn't flash cwm strait after?

haloXgod117 said:
My wifi isn't working, it just says "turning on...". Other than that, it works great
Click to expand...
Click to collapse
Brand New said:
**** mines bootlooping its get the att and loops what should i dooo? I got the latest cwm, and hboot, stock rooted rom. Is it because I let it try to boot right after I flashed the boot.img and didn't flash cwm strait after?
Click to expand...
Click to collapse
You shouldn't be flashing via cwm. I've included a script for pc tethered flashing. Just run flash.bat on pc with USB cable connected to the phone. You may need to run it twice if it failed to load the modules.
Sent from my HTC Sensation 4G using Tapatalk

faux123 said:
You shouldn't be flashing via cwm. I've included a script for pc tethered flashing. Just run flash.bat on pc with USB cable connected to the phone. You may need to run it twice if it failed to load the modules.
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
So I could of flashed this on stock ICS? I didn't think you could OC with a non-rooted phone And I was bootlooping on the stock rooted rom not because of the your kernal I believe
iff this will help
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
D:\Documents and Settings\Noah>cd D:\Documents and Settings\Noah\Desktop\New Fol
der
D:\Documents and Settings\Noah\Desktop\New Folder>flash.bat
D:\Documents and Settings\Noah\Desktop\New Folder>adb kill-server
D:\Documents and Settings\Noah\Desktop\New Folder>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb push Modules/system /syste
m
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb shell mv /system/bin/mpdec
ision /system/bin/mpdecision_dis
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb shell mv /system/bin/therm
ald /system/bin/thermald_dis
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb reboot bootloader
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>fastboot flash boot Kernel-Her
e/boot.img
sending 'boot' (4348 KB)... OKAY [ 0.875s]
writing 'boot'... OKAY [ 4.984s]
finished. total time: 5.859s
D:\Documents and Settings\Noah\Desktop\New Folder>fastboot reboot
rebooting...
finished. total time: 0.188s
D:\Documents and Settings\Noah\Desktop\New Folder>pause
Press any key to continue . . .
D:\Documents and Settings\Noah\Desktop\New Folder>

can you make a aosp kernal

Nevermind Faux I figured it out! I just need to flash the boot.img that came with the stock rooted rom, then yours! I can't wait to test my battery now, games fly to!! Thanks for your support!!

SetCPU voltage tables are still nonfunctional, just like every other kernel I've tried.
come at me bro said:
can you make a aosp kernal
Click to expand...
Click to collapse
It would be easier to do so if we had a booting AOSP build right now, I think.

Having no issues here. Kernel is definitely smoother and faster than stock. Running fine on WC ROM. Hitting about 3350 on quadrant afer 5 consecutive runs. I haven't made and changes with setcpu, I'm assuming 1.5MHz from initial flash.
Sent from my HTC PH39100 using xda premium

Aus_Azn said:
SetCPU voltage tables are still nonfunctional, just like every other kernel I've tried.
It would be easier to do so if we had a booting AOSP build right now, I think.
Click to expand...
Click to collapse
thecubed's build boots but just barely and someone is working on a build right now I believe, so one day we might have working rom

Brand New said:
thecubed's build boots but just barely and someone is working on a build right now I believe, so one day we might have working rom
Click to expand...
Click to collapse
it boot loops with the proper builds , the one that boots is hacked up to hell

The Ultimate kernel for the HTC Desire 500, both one sim and dual sim!
Software version 1.32/1.26 only! It probably won't work on earlier versions, but it might work on later versions (1.34), I haven't tested that.
Use at your own risk!
Features:
/system write protection removed
two new frequencies added: 1300 and 1400 mhz
init.d support
intelli_plug
sweep2sleep
sweep2wake and doubletap2wake, both with pocket detection
ntfs read/write support
Governors added: SmartassV2 and Lulzactive
ioschedulers added: sio and fiops Default: sio
Fastcharge
Unsecure (ro.secure=0)
Click to expand...
Click to collapse
If you don't want to overclock your device, then simply choose the download link with no overclocking.
Requirements:
Unlocked bootloader
Custom recovery (cwm or twrp)
Fastboot installed
Click to expand...
Click to collapse
Installation instructions:
Download the latest boot.img
Boot your phone into fastboot mode
Open up your commandline
cd to the directory containing the boot.img
In the command line type: fastboot flash boot boot5.img
Boot into cwm/twrp
Wipe cache and dalvik-cache
If you don't have it yet (your phone is not rooted), flash SuperSU or superuser
Click to expand...
Click to collapse
Downloads:
Version 8: Not overclocked: boot8_no_oc.img, Overclocked: boot8_oc.img
Version 7: Not overclocked: boot7_no_oc.img, Overclocked: boot7_oc.img
Version 6: boot6.img
Version 5: boot5.img
Version 4: boot4.img
SuperSU: SuperSU
Click to expand...
Click to collapse
If your phone does not boot after installing an overclocked kernel, then try installing the not overclocked kernel.
Changelog:
Version 8:
Removed the underclocking, it was way too low, and caused wakeup issues
Added 1300 mhz frequency
Updated intelli plug from faux123's github
Updated to 1.34, many thanks to @0lvin
Little fixups on sweep2wake/doubletap2wake
Version 7:
Added overclocking up to 1400 mhz
Underclocking down to 19 mhz
Added sweep2wake and doubletap2wake
Added intelli plug, a replacement for Qualcomm's closed source mpdecision
Enabled perflock again
Version 6:
Add fastcharge
Version 5:
Disabled -O3 optimization
Version 4:
-O3 optimization
ntfs read/write support
Governors added: SmartassV2 and Lulzactive
ioschedulers added: sio and fiops Default: sio
Version 3 and below:
Check the Ultimate Thread
Click to expand...
Click to collapse
Kernel source:
https://github.com/dummie999/android_kernel_htc_z4u
Click to expand...
Click to collapse
Credits:
@flar2 for sweep2sleep
@xpirt for helping me with Smartass
@GreatEmerald for helping me with kernels in general
@eexter for testing for 1.26
@0lvin for updating to 1.34
To the devs:
Feel free to include this kernel in your rom/rooting tool. Just give proper credits and put a link to this thread in your rom thread (Required for GPL).
XDA:DevDB Information
The Ultimate Kernel, Kernel for the HTC Desire 500
Contributors
dummie999, 0lvin
Kernel Special Features: dt2w | s2w | intelli_plug | fastcharge | oc | init.d
Version Information
Status: Stable
Created 2014-10-14
Last Updated 2014-10-14

Reserved

Reserved

Upcoming features
* Intellidemand (implemented - needs tweaking)
* F2FS

Tips
How to change sleep/wake options:
The options for sweep2sleep, sweep2wake and doubletap2wake:
sweep2sleep: 0 - disabled, 1 - enabled, both directions, 2 - enabled, left->right only, 3 - enabled, right->left only
sweep2wake: 0 - disabled, 1 - enabled, both directions, 2 - enabled, left->right only, 3 - enabled, right->left only
doubletap2wake: 0 - disabled, 1 - enabled, full screen, 2 - enabled, bottom half screen, 3 - enabled, center down of the screen (hope you get it)
To change the options, put a script in /system/etc/init.d:
Code:
#!/bin/sh
echo "0" > /sys/android_touch/sweep2sleep
echo "0" > /sys/android_touch/sweep2wake
echo "0" > /sys/android_touch/doubletap2wake
This setting disables all the sweep/wake options
Code:
#!/bin/sh
echo "1" > /sys/android_touch/sweep2sleep
echo "1" > /sys/android_touch/sweep2wake
echo "2" > /sys/android_touch/doubletap2wake
This setting enables sweep2sleep and sweep2wake, and enables doubletap2wake bottom half of the screen
Click to expand...
Click to collapse
How to use fastcharge:
If you charge your phone via usb (from your computer) then it will only charge at 500mA even while most usb ports are capable of supplying 1000mA. Enabling fastcharge will allow your phone to charge at 1000mA via usb.
!!! Warning: you must be sure your usb can supply 1000mA !!!
Fastcharge is disabled by default. You can enable it in 2 different ways:
1. Writing a 1 to /sys/kernel/fast_charge/force_fast_charge. You can do this with a text editor, or with a script in init.d (see above)
2. Or you can simply install an app. I tested Fast Charge by Mathew Winters and Fast Charge by Chris Conley, both worked.
Click to expand...
Click to collapse
To hard? Use this app by Ufonek: Kernel Settings
A word about governors:
Some governors lower the frequencies to fast. For example, when I play angry birds when using lulzactive, the phone laggs a lot. This is, however, not the fault of the kernel, but the fault of the way the governor is tweaked. It is the price you pay for the better battery life you have. If you want to do something about it, tweak your governor, there are a lot of tutorials about this.
Don't come here complaining the phone laggs, and that I should fix it, I won't, because I can't. Everyone has his own preferences, and if you can't live with this, then I recommend you use the ondemand governor.

Compilation instructions
Instructions for compiling the kernel yourself.
Prerequisites:
1. A linux computer
2. Basic bash knowledge
3. ~120 MB free space
4. The android-eabi toolchain:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 for 4.6
(use darwin-x86 instead of linux-x86 for mac)
And then add it to your $PATH (You need to have the arm-eabi-4.6/bin folder in your path)
Instructions:
1. Download the kernel source
2. Open the cmdline and cd to the directory with all the files (Documentation, arch, block etc.)
3. type: make dummie_z4u_defconfig
4. type: make menuconfig
........A menu will open, and you can change some settings. If you want everything to be the way I built it, then skip this step.
5. type: make
The actual building will begin.
Troubleshoot:
If you run into a python problem, you might want to change, in android_kernel_htc_z4u/scripts/gcc-wrapper.py this:
"#! /usr/bin/env python" into "#! /usr/bin/env python2", credits @svalo
If the building succeeds, then you will find the file zImage in arch/arm/boot.
Next step: turn the zImage into a boot.img
1. Download imgtools, and add it to you $PATH
2. Download my boot.img
3. Open cmdline, cd to the directory containing boot.img and type: unpack boot.img
........You will end up with: ramdisk.cpio.gz, ramdisk and zImage (and the boot.img that was already there)
4. Replace the zImage with the zImage you build earlier (arch/arm/boot)
5. Rebuild the kernel:
Code:
repack_ramdisk ramdisk initramfs.cpio.gz
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x3b00000 --cmdline 'no_console_suspend=1 console=null' -o new_boot.img
You will now see a file called new_boot.img, containing your own kernel, which you can install the very same way
Good luck:good:

Note that -O3 does not work for the kernel, at all, and never has. You can set it but it won't do anything. The compiler will still use -O2, because all the parts where performance matters are written in assembly or through GCC-specific extensions already. There is nothing that automatic code optimisation would improve. Meanwhile -O3 enables non-safe options that can result in imprecise calculations, which can lead to disasters in things that are as important as the kernel. So you should disable that.

GreatEmerald said:
Note that -O3 does not work for the kernel, at all, and never has. You can set it but it won't do anything. The compiler will still use -O2, because all the parts where performance matters are written in assembly or through GCC-specific extensions already. There is nothing that automatic code optimisation would improve. Meanwhile -O3 enables non-safe options that can result in imprecise calculations, which can lead to disasters in things that are as important as the kernel. So you should disable that.
Click to expand...
Click to collapse
Then why do people use it?

dummie999 said:
Then why do people use it?
Click to expand...
Click to collapse
Placebo. It makes them think they're gaining something, even though in truth they aren't (but are not certain).

so i need to flash the boot image than flash the kangbang kernel????

joe-khalil said:
so i need to flash the boot image than flash the kangbang kernel????
Click to expand...
Click to collapse
No, you don't need to flash the kangbang kernel. This is a replacement of the kangbang kernel, for 1.32

Replacement?? That means if i flash the boot image i'll have the kernel installed?

Dual SIM doesn't have the 1.32 update, so i don't think this kernel would work on the dual sim version.

joe-khalil said:
Replacement?? That means if i flash the boot image i'll have the kernel installed?
Click to expand...
Click to collapse
yes, lol

I have installed.. It works fine. Thanks !!!

gayTony said:
Dual SIM doesn't have the 1.32 update, so i don't think this kernel would work on the dual sim version.
Click to expand...
Click to collapse
1.32 for Single SIM = 1.26 for Dual SIM (kernel is the same)

dummie999 said:
Fastcharge
Overclocking?
If you have any requests, post them!
Click to expand...
Click to collapse
Overclocking would be nice!

And don't forget to add a link to your kernel sources, to prevent unfortunate things from happening to this thread

GreatEmerald said:
And don't forget to add a link to your kernel sources, to prevent unfortunate things from happening to this thread
Click to expand...
Click to collapse
lol, I knew I had forgotten sth

dummie999 said:
lol, I knew I had forgotten sth
Click to expand...
Click to collapse
any news about CM @dummie999

NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk

Damn this looks complicated as hell haha. Good job OP

Very nice job

Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me

I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks

One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.

elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?

Did you disable APK signature checking?

elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?

Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works

Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?

For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.

My rom is stock 4.4.4
I will try again with disabled optimization.

kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.

elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.

kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference

Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.

I tried again but this time booted upto lock screen and rebooted.
I tried with new build.

after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english

Android Open Source Project 6.0
Marshmallow
for
Samsung Galaxy Tab 10.1
(P7510, P7500, SGH-T859)
(p4wifi, p4, p4tmo)
​
Customizations:
busybox
init.d scripts
CMFileManager
Kernel features:
CPU overclock (1.2Ghz - 1.6Ghz)
CPU voltage control
CPU temperature readings
GPU overclock (400Mhz)
L2 cache optimization
F2FS
SELinux
Voodoo Sound
USB Charging
Updated WIFI driver
ZRAM backports
sdcardfs
Working:
Video
Audio
WIFI
Cellular
GPS
Bluetooth
- Audio playback: working
- File transfer: working
Encryption
Not working / buggy / needs testing:
Camera
- Pictures: working
- Video recording: (not working)
Dock audio
Keyboard dock (untested)
- Likely the same status as Lollipop
Tethering
- USB tethering: working with WIFI
- Bluetooth tethering: (not working)
- WIFI tethering: (untested)
Wireless Display / Miracast
- No compatibility with the outdated video blobs
Installation:
Backup all data
Install TWRP 2.8.7.0 or newer
Wipe cache, dalvik cache, system, data
Install the ROM
Optional step:
- Install gapps pico
- Install Supersu 2.52
Boot the ROM
Enable on screen keyboard by toggling "Show input method"
Downloads:
p4wifi (GT-P7510): WIFI only tablet.
aosp-6.0-p4wifi-20160806.zip
p4 (GT-P7500): Cellular / 3G tablet.
aosp-6.0-p4-20160809.zip
p4tmo (SGH-T859): T-Mobile tablet.
p4wifi and p4 users do NOT install this.
aosp-6.0-p4tmo-20160809.zip
mirror: AndroidFileHost
GApps
http://opengapps.org/
root: SuperSU
BETA SuperSU v.2.52
Mirrors:
Android File Host
​
Changelog
Code:
August 9, 2016
decatf/android_kernel_samsung_p4
e602201 defconfig: Fix typo while enabling CONFIGFS_FS
August 6, 2016
Update to android-6.0.1_r59
decatf/android_kernel_samsung_p4
2c421f2 fuse: O_DIRECT support for files
3bb1d41 fuse: remove the second argument of k[un]map_atomic()
acf44b5 fuse: verify all ioctl retry iov elements
1b17d75 fuse: postpone end_page_writeback() in fuse_writepage_locked()
d88af9d fuse: break infinite loop in fuse_fill_write_pages()
33c337c fuse: support ioctl on directories
37bb785 FUSE: Notifying the kernel of deletion.
f7c8478 fuse: Add support for shortcircuited read/write for files
d5c6ade Revert "fuse: Add support for shortcircuited read/write for files"
04ed83b fuse: Add support for shortcircuited read/write for files
ab0b217 fs: fuse: Ensure update of fuse inode attributes in shortcircuit
b653a54 fuse: Use iocb->ki_pos instead of pos for shortcircuit writes
b79cfba fuse: Use BUG_ON to check pos validity in fuse_aio_write
786913d fs: fuse: Disable shortcircuit when mmap is called on a file
bfc19a7 vfs: add d_canonical_path for stacked filesystem support
fb6bb3e inotify: Fix erroneous update of bit count
8bae312 Initial port of sdcardfs
568217e get rid of kern_path_parent()
7233db3 sdcardfs: Port to 3.4
a5d5845 sdcardfs: Port to 3.1.10
4cede1c sdcardfs: Changed type-cast in packagelist management
3f69353 sdcardfs: Bring up to date with Android M permissions:
dfc2ff3 sdcardfs: Add support for d_canonicalize
1f80a89 sdcardfs: remove effectless config option
dd5eccf sdcardfs: Remove unused code
1b8979a sdcardfs: remove unneeded __init and __exit
1c16f89 sdcardfs: Truncate packages_gid.list on overflow
560043c ANDROID: sdcardfs: fix itnull.cocci warnings
d3e1021 vfs: change d_canonical_path to take two paths
e587970 fuse: Add support for d_canonical_path
434e90b defconfig: Enable sdcardfs
e7b5ee2 BACKPORT: perf tools: Document the perf sysctls
90bd458 FROMLIST: security,perf: Allow further restriction of perf_event_open
1ccaa78 defconfig: restrict access to perf events
android_device_samsung_p4-common
8404df3 p4-common: Enable sdcardfs
913957d p4-common: Disable EGL_WORKAROUND_BUG_10194508
5f67070 p4-common: sepolicy: Allow kernel to rw wifi efs file
android_vendor_decatf
6bbd9c6 sepolicy: remove BOARD_SEPOLICY_UNION
91f8dc2 sepolicy: Add rule to allow sdcardfs to read package list
8209b59 sepolicy: Fix MTP for sdcardfs
android_bionic
546aae2 bionic: Sort and cache hosts file data for fast lookup
platform_frameworks_base
0454407 mountservice: Shut down volumes before restarting framework
9baa27d mountservice: Don't nuke all volumes when decrypting
android_frameworks_opt_net_wifi
d21014b Revert "Revert "wifi: Set the mode at native layer""
platform_system_core
a052e68 sdcard : Use the fuse shortcircuit option
86faebc sdcard: Allow fuse shortcircuit for all platforms
e06eb06 sdcard: Add support for sdcardfs!
d3a24ca sdcard: Fix sdcardFS check
6ff0e73 sdcard: Pass the umask to sdcardfs correctly
android_external_sepolicy
5d57d80 sepolicy: Add policy for sdcardfs and configfs
July 8, 2016
Update to android-6.0.1_r50
Restore previous WIFI driver
June 15, 2016
TRIM is now merged into this ROM. You don't need to install the TRIM kernel from the other thread.
Update to android-6.0.1_r46
74f7de9 p4-common: TCP buffer settings
93ca209 p4-common: Wifi is no longer built as a module
2133d24 p4-common: Enable dlmalloc
b6808c6 p4-common: Remove unused flags
4692beb tcp: drop SYN+FIN messages
cf415a5 misc: uidstat: avoid create_stat() race and blockage.
3f791c1 usb: gadget: f_fs: Fix enumeration in fullspeed mode
0469e56 usb: gadget: accessory: Fix section mismatch (again)
30fbe2f USB: remove duplicate out endpoint creation in MTP mode
c607c37 pipe: limit the per-user amount of pages allocated in pipes
8e01cbe power: max17042: Reduce logspam
5565950 Revert "Staging: android: binder: Allow using highmem for binder buffers"
bf9b28a Reduce logger size
9c3a8ec mmc: fix integer assignments to pointer
d7bfd4c mmc: sdio: Workaround for dev with broken CMD53
74032a4 mmc: sdio: Fix to support any block size optimally
3f9da59 mmc: sdio: Use multiple scatter/gather list
ed4849d genirq: Always force thread affinity
b1bb34f genirq: Avoid deadlock in spurious handling
c4cb3ae genirq: Fix can_request_irq() for IRQs without an action
aeaeb4de mmc: Restore MMC_CAP_ERASE
fd6a17d mmc: Add sdio_ctrl_power
8bd4f0d arm: tegra: p4: Allocate static dhd info buffer (section 7)
ec9b234 arm: tegra: p4: Built-in wifi
cfb0ab2 arm: tegra: p4: Set wifi chip id to 0x4330
ce80b1b arm: tegra: Conditionalize builtin wifi
2477c3b Revert "net: wireless: Sync with grouper android-5.1.0_r0.4"
e32e74d arm: tegra: p4: Fix build when not builtin wifi
a0d37af net: wireless: Import CFG80211_REG_NOT_UPDATED from klte kernel
62151e1 defconfig: disable loadable modules
a5cf304 net: Backport wireless stack from Galaxy S5 kernel
88d16a6 net: Fix net/wireless backport for 3.1.10
7dbf92b bcmdhd: G900FXXU1CPD7
abf9e8c bcmdhd: fixup for p4
e3c843a bcmdhd: Restore tegra specific irq wake
aa99d0d defconfig: bcmdhd builtin
716bd9c defconfig: Enable CONFIG_CFG80211_ALLOW_RECONNECT
946d13f mmc: tegra: Don't set MMC_PM_KEEP_POWER by default
9a40b65 mmc: host: sdhci: abort suspend if host suspend fails.
8d5d16f mmc: host: sdhci: Don't set MMC_PM_KEEP_POWER when suspending
6f689f2 mmc: Remove Samsung WIFI hacks
April 28, 2016
Fix headphone detection
April 14, 2016
Update to android-6.0.1_r30
March 26, 2016
project art/
20c3c84 Revert "Optimize double/float immediate loading on arm."
8037a8d Re-enable VFPv3-D16 register definitions
d53de19 Disable clang for art compiler on target
project device/samsung/p4-common/
f19dec3 p4-common: Use dalvik.vm.dex2oat-flags to specify backend
0cc66dc p4-common: Remove unused flag
84f022f p4-common: Tweak ksm settings
project frameworks/av/
111a9b9 Revert "mediaplayer: remove use-awesomeplayer developer option"
project frameworks/native/
f1b88cd Configure tablet dalvik heap for 1GB mdpi device
project kernel/samsung/p4/
2b12c4b pipe: iovec: Fix memory corruption when retrying atomic copy as non-atomic
16a60d8 Squash revert Android timerfd support
24bcc61 Android alarm-dev from android-3.4
f519a62 defconfig: enable android-3.4 alarm-dev
4ab42f7 p4_battery: Fix timer slack
7dbdfb5 ARM: 7006/1: Migrate to asm-generic wrapper support
f2b70ff ARM: 7493/1: use generic unaligned.h
33e4372 asm-generic: allow generic unaligned access if the arch supports it
a998f78 Revert "Revert "video: tegra: remove free memory check""
project packages/apps/Settings/
98144ac Revert "developer settings: remove "Use deprecated AwesomePlayer" settings"
project system/core/
6b5492a healthd: increase healthd fast timer to 10mins instead of 1min
March 14, 2016
Fix WIFI driver
March 10, 2016
Update to android-6.0.1_r17
ca6770d Align machine_kexec restart sequence with soft_restart()
b4c0a36 ARM: 7476/1: vfp: only clear vfp state for current cpu in vfp_pm_suspend
f847946 cfq-iosched: fix the setting of IOPS mode on SSDs
a74f780 arm: tegra: Restore tegra2 core/cpu voltage relationship
868ba34 Revert "bound cpu cores to same speed"
c4877ab include/linux/poison.h: fix LIST_POISON{1,2} offset
9c3f030 pagemap: do not leak physical addresses to non-privileged userspace
February 7, 2016
Update to android-6.0.1_r10
February 1, 2016
Add init.modem.rc for p4 and p4tmo
January 31, 2016
hwrotation for Galaxy Tab 8.9
January 28, 2016
Update to android-6.0.1r7
Switch to ICS audio wrapper HAL
Update to latest f2fs-stable
Frequently Asked Questions and Other notes:
Can I upgrade / dirty-flash from Lollipop to Marshmallow?
- You cannot. It must be a clean install.
Can I dirty flash over a previous Marshmallow build?
- Yes.
I thought you said Marshmallow wouldn't work.
- The problem with ART is not solved. The Optimizing compiler backend is producing binaries that crash on the Tegra 2. The Optimizing backend is the new default dex2oat compiler in Marshmallow. The Quick compiler is default backend in Lollipop. It is still in the Marshmallow source so this ROM is using the Quick compiler backend.
SELinux enforcing mode
- The default SELinux mode is permissive mode. The Set_SELinux_enforcing.zip will not work with Marshmallow. That script was setting a system property to toggle SELinux early on in boot. Google has removed the use of this system prop so that method won't work anymore.
- For now you can find some app on F-Droid to set the SELinux mode after boot. It's not ideal but it will do until some better solution arises.
Doze
- This device does not meet the hardware requirement to support Doze.
Themes
- Marshmallow supports RRO (Layers) themes. I will not add CM-12 themes, CM-13 themes, or any other theme engine.
HD video playback issues and Camera issues.
- The video and camera stack are proprietary NVidia software. This means there is no chance of fixing bugs within.
Browser crash when downloading files
- Settings > Apps > Browser > Permissions > Enable Storage permission
Google App force close
- Install GApps Pico.
- Google App now uses the NEON instruction set which the CPU on this device does not support. The pico package does not include the parts of GApps which use the NEON instruction set.
- reference post
Non-NEON Google Apps
Chrome 49.0.x
​
Donate:
Via Paypal
XDA:DevDB Information
Android 6.0 Marshmallow, ROM for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/decatf
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Alpha
Created 2015-12-08
Last Updated 2016-12-19

Problem reporting steps:
Got an error? Is something not working for you?
I cannot see what your problem is from here. Save and upload the system logs from your device so that I can see what happening on your device.
How to save system logs:
Root the device by installing SuperSU.
Install SysLog.
Reboot the system.
Reproduce the problem.
Open Syslog app and save the Kernel Log and Main Log.
Send me the log files stored in /sdcard/Syslog.
Share the files on Dropbox or another similar site.
Then PM me a link to the files. Please describe exactly what the issue is.

Some comments to start off.
The ICS audio HAL is not working right in Marshmallow and I think I'd rather try another run at getting the rest of the stuff in the open souce HAL working rather than keep trying to find hacks to keep the old blob alive. Recall that only voice calls and dock audio are not working with the open source audio HAL.
- Voice calls are just passing off audio to the Samsung cellular blobs so I don't think it's that much of a stretch to get working. But this will have to wait until cellular stuff is working in the first place.
- I found some patch for Samsung dock audio. It looks like it might apply to this device as well seeing as it seems to have a similar dock implementation. The patch is in the ROM already so that needs testing.
Cellular probably won't work for at least the first few builds. Other devices on M with a similar cellular radio needed a few new patches to get it working on M. I have put in the patches from L but we will have to trial and error what is needed for M based on other devices as a reference.

Thank you!

I know it's early on, but do you have any expectations as to how well it will run compared to previous Android version?
I appreciate all you've done, but mine never ran that great on the newest roms. It is passable and I appreciate it though.
Sent from my XT1094 using XDA Free mobile app

thank you very much for betting on this tablet , and download and I'll try ... I'm sure you will be able to tune it as we did with lp...

sflesch said:
I know it's early on, but do you have any expectations as to how well it will run compared to previous Android version?
I appreciate all you've done, but mine never ran that great on the newest roms. It is passable and I appreciate it though.
Sent from my XT1094 using XDA Free mobile app
Click to expand...
Click to collapse
The OS appears to perform the same as Lollipop. It's a four year old device. There is nothing that will make it run as well as a modern Android device. You could try setting animation times to zero and set ro.config.low_ram=true.
For Marshmallow I have added L2 cache improvements in the kernel that improves RAM speed benchmarks. That's around 1k score in Antutu.

I understand that. And again I appreciate it. I was just curious what the performance level was. I expected at best it might be similar, but more likely it would, as is typical, use more resources.
I never expected much from my Tab. Finding your ROM was an unexpected surprise. I will try those tweaks. From all of the posts I read, I got the impression that many other tablets ran better than mine. I know fully well that each tablet is different and I don't blame you or the ROM, just my tablet.
Sent from my XT1094 using XDA Free mobile app

decatf said:
The OS appears to perform the same as Lollipop. It's a four year old device. There is nothing that will make it run as well as a modern Android device. You could try setting animation times to zero and set ro.config.low_ram=true.
For Marshmallow I have added L2 cache improvements in the kernel that improves RAM speed benchmarks. That's around 1k score in Antutu.
Click to expand...
Click to collapse
Thank you for keeping this Mastodont alive. I will be doing the switch soon enough... I have been following and installing your Lollipop releases for quite a while now and appreciate very much all the time and effort you have put into these projects...
Sent from my p4wifi using XDA Free mobile app

Definitely wasn't expecting this tbh. You're doing a damn great job at keeping this tab alive decatf. Thank you for that.

Mmmh, I just did the following steps (coming from your version of 5.1.1) :
1) Installed TWRP-2710 from previously installed TWRP-2610
2) Rebooted into 2710 Recovery
3) Full Wipe
4) Install Android 6.0 ROM
5) Install OpenGapps (nano)
6) Install SuperSU 2.52
7) Reboot
Now the P4 is stuck at the Samsung boot logo, so it does not boot up.
Any ideas what I did wrong?
Regards, mistersixt.

mistersixt said:
Mmmh, I just did the following steps (coming from your version of 5.1.1) :
1) Installed TWRP-2710 from previously installed TWRP-2610
2) Rebooted into 2710 Recovery
3) Full Wipe
4) Install Android 6.0 ROM
5) Install OpenGapps (nano)
6) Install SuperSU 2.52
7) Reboot
Now the P4 is stuck at the Samsung boot logo, so it does not boot up.
Any ideas what I did wrong?
Regards, mistersixt.
Click to expand...
Click to collapse
Me too, ive installed twrp 2.8.7.0. Full wipe, install android 6 rom (P4) and use openGapps (pico), install superSU beta 2.52.
My P4 is stuck at samsung boot logo

Anyone able to install the rom successfully?
Anyways thanks decatf for all u have done for our device!

maybe don't use OpenGapps Pico?
on different devices, had issues with OpenGapps Pico versions;
especially on 5.1 and 6.0, pico may be -too- light?
I've had success with slim gapps zero on different devices;
size is similar to OpenGapps nano.
- maybe try WITHOUT any gapps?
- assuming it works, try Open nano, or slim zero?
i'll try myself and report later if I can
cheers
---------- Post added at 10:45 AM ---------- Previous post was at 10:37 AM ----------
I haven't read -too- thoroughly,
but in addition to the 'regular' supersu beta (currently 2.52),
chainfire has a separate "WIP" thread where, at least check,
2.61.. for Marshmallow+.. systemless?.. discussion is still in the 2.52 / beta thread
a) link to the WIP thread: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
b) that said, maybe for our system , 2.52 may be more appropriate?
can anyone compare?
c) hmm.. more reading.. may want to stick with 2.52 for now,
until 2.62 is ready (currently 2.61, but with planned features/fixes for 2.62)
cheer

Same thing, just did another full wipe and installed the p4 ROM only (no gapps, no supersu), and it is still stuck at the Samsung boot logo.
Regards, mistersixt.
spamam1 said:
on different devices, had issues with OpenGapps Pico versions;
especially on 5.1 and 6.0, pico may be -too- light?
I've had success with slim gapps zero on different devices;
size is similar to OpenGapps nano.
- maybe try WITHOUT any gapps?
- assuming it works, try Open nano, or slim zero?
i'll try myself and report later if I can
cheers
---------- Post added at 10:45 AM ---------- Previous post was at 10:37 AM ----------
I haven't read -too- thoroughly,
but in addition to the 'regular' supersu beta (currently 2.52),
chainfire has a separate "WIP" thread where, at least check,
2.61.. for Marshmallow+.. systemless?.. discussion is still in the 2.52 / beta thread
a) link to the WIP thread: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
b) that said, maybe for our system , 2.52 may be more appropriate?
can anyone compare?
c) hmm.. more reading.. may want to stick with 2.52 for now,
until 2.62 is ready (currently 2.61, but with planned features/fixes for 2.62)
cheer
Click to expand...
Click to collapse

It works on my p4wifi. Somebody with an actual p4 needs to try booting it then reboot directly into TWRP and grab the last_kmsg.
Code:
adb pull /proc/last_kmsg
Or
Go to Advanced > File Manager > Go to /proc/ > Tap last_kmsg > Copy File to /sdcard/

P4: wrong updater binary?
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------
spamam1 said:
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
Click to expand...
Click to collapse
hmm. .. donjuan10 on P4 was able to at least flash the files.
what am i doing wrong?

Hope I grabbed the right file:
http://144.76.203.117/tmp/last_kmsg
regards, mistersixt.
decatf said:
It works on my p4wifi. Somebody with an actual p4 needs to try booting it then reboot directly into TWRP and grab the last_kmsg.
Code:
adb pull /proc/last_kmsg
Or
Go to Advanced > File Manager > Go to /proc/ > Tap last_kmsg > Copy File to /sdcard/
Click to expand...
Click to collapse

spamam1 said:
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------
hmm. .. donjuan10 on P4 was able to at least flash the files.
what am i doing wrong?
Click to expand...
Click to collapse
more info..
before the error message (in red), a message about mount/symlink:
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-num/p4 at /system: Device or resource busy
symlink: some symlinks failed
?

It might just be some kernel cmdline options I missed. The reason it boots on my p4wifi is because I'm testing it on multirom which passes off some cmdline options from the host ROM so the problem was not apparent due to that.
Just install the ROM then the kernel. And the rest of the stuff as usual.
p4-kernel-aosp-6.0-20151209.zip
p4tmo-kernel-aosp-6.0-20151209.zip

ALL CORES WORKING FULLY WORKING 3 g935 KERNELS TO CHOOSE FROM LOOK BELOW
THAT THIS IS FULLY WORKING AND UPDATED TO NETHUNTER 3.1.0
ZIP MODDED FOR S7 EDGE FOR 1440X2560 WITH NEWEST BUSYBOX AND SUPERSU
WARNING: This is completely untested, highly theoretical, and possibly dangerous. Flash at your own risk.
Back up your original boot image in TWRP before attempting to flash this! If it doesn't boot, you can simply restore your previous boot image.
This is Kali NetHunter 3.1.0 for the Galaxy S7 Edge.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-securit...nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The updater zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
DOWNLOAD
https://mega.nz/#!3QIHzQ5b!x77Wad9OUAyQqAtJJucak3C_3twfFFwZqJ77Wt1j6-c
Current version: 3.1.0 (beta, 07/03/2016)
Please be careful to download the right version based on this table:
SM-G935F, SM-G935FD, SM-G935X, SM-G935W8: hero2lte
SM-G930F, SM-G930FD, SM-G930X, SM-G930W8: See proper forum.
All others be sad.
Download is available at: kernel below
Grab the 700 MB+ zip.
Kernel-only zip is for upgrading your kernel, or just using the NetHunter kernel by itself. (yes, you can do that!)
BEFORE INSTALLING
Currently, Samsung encryption is not supported by TWRP, so we have to disable it.
Sorry security freaks! There's a lot of irony here, isn't there?
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU (2.76) in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
Also included is an extra Busybox that gives you full large file support and some extra applets.
FULL FRESH INSTALL STEPS
Install Team Win Recovery Project to your recovery partition.
If your data partition doesn't mount in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
If you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
Download Kali NetHunter.
Without exiting TWRP, transfer the NetHunter installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery and wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just flash the ~700+ MB update-nethunter-* zip again.
THE KERNEL
The NetHunter kernel for the Galaxy S7 Edge is based on Samsung's OSRC G935FXXU1APF2 kernel sources.
It has the following changes:
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted system, data, and cache partition support
UKSM Ultra Kernel Same-page Merging KSM support
Updated and enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
Simple IO (SIO) scheduler as default IO scheduler
USB HID Gadget keyboard support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption changed from forced to optional (disabled during installation)
Disables dm-verity and allows you to boot modified system partitions
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (it better not be something other than G935F, dangit!)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
NetHunter Terminal - It doesn't automatically set the columns/rows, so you need to type "resize" sometimes to fix the display.
DEVELOPMENT
You can see branch of the installer development here:
Alternatively, the main branch is also available on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Kernel source: https://github.com/BoostFlash/nethunter_kernel_herolte
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDAevDB Information
Kali NetHunter for the Galaxy S7 Edge, Kernel for the Samsung Galaxy S7 Edge
Contributors
jcadduono, The Kali NetHunter team ,ohap
Source Code: https://github.com/BoostFlash/SuperKernel
https://github.com/BoostFlash/nethunter_kernel_herolte
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 3.1.0
Beta Release Date: 2016-07-03
new links :
jcadduono nethunter patcher with new superkernel plus nethunter patches , make sure your on a kernel thats fully working before flashing this as it only patches ramdisk
https://mega.nz/#!LR4BgbyJ!vezMFaob3mIETH__mVMd9WjCXwLCFvzouObX7f72wmY
my kernel compiles from superkernels source with makeshift ramdisk + nethunter patches
https://mega.nz/#!rEQDBD4B!v_4JRruBe6exR-O40ax5DECJA7nLikSpbIbEDI7YVyM
superskernel with his modded ramdisk plus nethunterpatches added by me synapse support <--best one
https://mega.nz/#!qcYnBAoT!KSHvaX7EtJLDeQq0kPmZHK4N200cnyirHP4X7-jUavg
Kali nethunter
https://telegram.me/kalinethunter
must thanks and credit to:
lucu/Tkkg1994 superkernel dev
jesse for fp patch
jcadduono for his help with github and patcher scripts
webhost420/hayden for brainstorming with me

So I'm good to just flash this with TWRP over the current one I'm using?
CPU core 6 and 7 still stopped as with previously used kernel.
Kali still working, everything seems the same so far. Will see with time.

umKthxbye said:
So I'm good to just flash this with TWRP over the current one I'm using?
CPU core 6 and 7 still stopped as with previously used kernel.
Kali still working, everything seems the same so far. Will see with time.
Click to expand...
Click to collapse
ya i cant seem to get them to work as i dont know , this is compiled from a old source , me and a other are trying to fix it no , BUT this is way faster then ael kernel , and im no way a professional kernel dev so this is my first shot at kernel i compiled my self which was a pain

ohap said:
ya i cant seem to get them to work as i dont know , this is compiled from a old source , me and a other are trying to fix it no , BUT this is way faster then ael kernel , and im no way a professional kernel dev so this is my first shot at kernel i compiled my self which was a pain
Click to expand...
Click to collapse
Are you using that AEL kernel as a base or the stock kernel?
Since the stock kernel or even Jesse kernel have all cpus active maybe use those and add support for the USB wifi adapters.
I'm also working on this with stock kernel but fixing compiling errors.

umKthxbye said:
Are you using that AEL kernel as a base or the stock kernel?
Since the stock kernel or even Jesse kernel have all cpus active maybe use those and add support for the USB wifi adapters.
I'm also working on this with stock kernel but fixing compiling errors.
Click to expand...
Click to collapse
No not using ael anything as there $%&$ , message me on telegram we have a group working on it . My name on there is Boostflash

ohap said:
No not using ael anything as there $%&$ , message me on telegram we have a group working on it . My name on there is Boostflash
Click to expand...
Click to collapse
Just post when there is a new one to test, the current one seems stable other then the 6 core problem.

Fixed the cores being off line they all come online at boot , but now facing maybe CPUFreq driver initialization failed ?? Which causes now all cores to go offline and stay off after a few seconds . And makes kernel unusable

ohap said:
Fixed the cores being off line they all come online at boot , but now facing maybe CPUFreq driver initialization failed ?? Which causes now all cores to go offline and stay off after a few seconds . And makes kernel unusable
Click to expand...
Click to collapse
Did you upload it for testing? Or not reliable enough to bother?

umKthxbye said:
Did you upload it for testing? Or not reliable enough to bother?
Click to expand...
Click to collapse
I thought the unusable kernel term would explain that , its not good for upload if you want to join group on telegram you can test if you want

good news jcadduono back working on this again , he first trying to fix his patcher zip , i told him how i got mine working but its different then what he doing , so once he gets that fix we see if its a issuse with original Samsung source or nethunter patches the core issues

The best way to use terminal in this since Hacker keyboard has so much **** on it you can't type properly.
1. Open Nethunter, Menu, Kali services, add check mark to SSH start at boot, and check it to turn on.
2. Go into Kali terminal(last time you'll need to use this crap) type; passwd "whateveryouwant", this will be used for your user in the next step.
3. Download Juice SSH and add user root with password what ever you made.
4. Create a connection using IP 127.0.0.1 (this is the local loopback address) leave port blank, it will use 22 by default.
5. Connect with one click and enjoy using any keyboard with bonus juice addon keys for terminal use.
JuiceSSH also give you a nifty little extra keyboard ontop of the one you use with the tab function, making bash autofill work.
I use swiftkey keyboard and have been using JuiceSSH for years to access my CentOS 7 servers and its been a dream to work with.
The one packaged with Nethunter is just terrible, and most of the other one found on app store are terrible as well.
Also, Ohap, you don't have to reboot after formatting the /data, just go back and clear the dalvik, cashe, etc, and other stuff like the guide I posted in your other thread.
Feel free to use the one I posted in the last thread.
Great work so far. The last kernel is still going strong, with no random reboot or other problem other the the 2 cores we all know about.

umKthxbye said:
The best way to use terminal in this since Hacker keyboard has so much **** on it you can't type properly.
1. Open Nethunter, Menu, Kali services, add check mark to SSH start at boot, and check it to turn on.
2. Go into Kali terminal(last time you'll need to use this crap) type; passwd "whateveryouwant", this will be used for your user in the next step.
3. Download Juice SSH and add user root with password what ever you made.
4. Create a connection using IP 127.0.0.1 (this is the local loopback address) leave port blank, it will use 22 by default.
5. Connect with one click and enjoy using any keyboard with bonus juice addon keys for terminal use.
JuiceSSH also give you a nifty little extra keyboard ontop of the one you use with the tab function, making bash autofill work.
I use swiftkey keyboard and have been using JuiceSSH for years to access my CentOS 7 servers and its been a dream to work with.
The one packaged with Nethunter is just terrible, and most of the other one found on app store are terrible as well.
Also, Ohap, you don't have to reboot after formatting the /data, just go back and clear the dalvik, cashe, etc, and other stuff like the guide I posted in your other thread.
Feel free to use the one I posted in the last thread.
Great work so far. The last kernel is still going strong, with no random reboot or other problem other the the 2 cores we all know about.
Click to expand...
Click to collapse
This was a poorly edited post for newbies , i know hacker keyboard sucks , and you dont have to wipe ect .. thanks for support & feedback

awsome update coming i have fixed the core issue !!! with the power of superkernel "luca" source ,plus nethunter patches, and a make shift ramdisk !!!! i got it to boot and all cores online plus all the goodys of superkernel !!
Now Need to just include patch for hid keyboards now I do that latter

umKthxbye said:
The best way to use terminal in this since Hacker keyboard has so much **** on it you can't type properly.
1. Open Nethunter, Menu, Kali services, add check mark to SSH start at boot, and check it to turn on.
2. Go into Kali terminal(last time you'll need to use this crap) type; passwd "whateveryouwant", this will be used for your user in the next step.
3. Download Juice SSH and add user root with password what ever you made.
4. Create a connection using IP 127.0.0.1 (this is the local loopback address) leave port blank, it will use 22 by default.
5. Connect with one click and enjoy using any keyboard with bonus juice addon keys for terminal use.
JuiceSSH also give you a nifty little extra keyboard ontop of the one you use with the tab function, making bash autofill work.
I use swiftkey keyboard and have been using JuiceSSH for years to access my CentOS 7 servers and its been a dream to work with.
The one packaged with Nethunter is just terrible, and most of the other one found on app store are terrible as well.
Click to expand...
Click to collapse
Hacker's Keyboard is there for use with USB keyboard app and editing configs and stuff in the NetHunter app.
As for terminal in NetHunter...
As you said, I recommend JuiceSSH as well. You can create a Local Terminal profile to get into Android console, then type:
Code:
su -c bootkali_login
You can also purchase JuiceSSH premium features and create a snippet that does all of that for you!
This way, you don't need to use SSH and waste battery!

ohap said:
awsome update coming i have fixed the core issue !!! with the power of superkernel "luca" source ,plus nethunter patches, and a make shift ramdisk !!!! i got it to boot and all cores online plus all the goodys of superkernel !!
Now Need to just include patch for hid keyboards now I do that latter
Click to expand...
Click to collapse
fixed hid

umKthxbye said:
The best way to use terminal in this since Hacker keyboard has so much **** on it you can't type properly.
1. Open Nethunter, Menu, Kali services, add check mark to SSH start at boot, and check it to turn on.
2. Go into Kali terminal(last time you'll need to use this crap) type; passwd "whateveryouwant", this will be used for your user in the next step.
3. Download Juice SSH and add user root with password what ever you made.
4. Create a connection using IP 127.0.0.1 (this is the local loopback address) leave port blank, it will use 22 by default.
5. Connect with one click and enjoy using any keyboard with bonus juice addon keys for terminal use.
JuiceSSH also give you a nifty little extra keyboard ontop of the one you use with the tab function, making bash autofill work.
I use swiftkey keyboard and have been using JuiceSSH for years to access my CentOS 7 servers and its been a dream to work with.
The one packaged with Nethunter is just terrible, and most of the other one found on app store are terrible as well.
Also, Ohap, you don't have to reboot after formatting the /data, just go back and clear the dalvik, cashe, etc, and other stuff like the guide I posted in your other thread.
Feel free to use the one I posted in the last thread.
Great work so far. The last kernel is still going strong, with no random reboot or other problem other the the 2 cores we all know about.
Click to expand...
Click to collapse
New kernel out built from superkernel check it out . Recommend the super ramdisk ver I posted

Yes I saw. I'm using it already. I like seeing the 8 cores back. Time will tell how stable it is. Good work guys.

is it work with superman rom?
please tell me how to flash

mdrobiulhasan said:
is it work with superman rom?
please tell me how to flash
Click to expand...
Click to collapse
How to flash is in first post . It should work with any rom with system root not systemless

Anyone having issues with call forwarding? Since I flashed King rom my call forwarding has been messed up, even going back to stock. Not sure if it's cuz of root, rom, or kernels.
Still running stable btw.