Database Info

[KERNEL] Sense 2.6.32.24+BFS+HAVS+USB HOST+UVOC+CIFS+NFS+NTFS+TUN

Hello,
I have compiled my own version of the bravo froyo kernel, I have mixed the work of kingklick for the incredible and the work of snq- as the 2.2b-sdfix kernel, changing some defaults voltages and add the Sven Killg's usb-host support. I have also added NFS, tun/openvpn, NTFS, UTF-8 and some usb devices I need. This kernel supports HAVS, that is Hybrid AVS that adjust the CPU voltage based the hardware feedback. In my desire is working quite fine, have no time for battery testing but it seems good. More feedback is welcome!
I am still waiting for an USB OTG Cable, so I cannot test the USB-Host part, it should work without problem following the instructions at http://sven.killig.de/android/N1/2.2/usb_host/ but if you find any problem, report it here.
Changelog:
-gg1:
GPU Fix from snq- and change versioning scheme.
v0.3:
Major change, based on official bravo and mix several patches from different sources. Now the kernel version is 2.6.32.24 and includes lots of changes. BFS, HAVS and more from the kingklick incredible kernel.
v0.2:
Remove usb sound support and add tun.ko for openvpn.
v0.1
I have put back IPv6 support, only 100Kb more and Google Googles works again :-D
Of course thanks to snq-, kingklick, LeeDroid, Sven, Koush and everybody here doing such a great job!

Next step should be a kind of toggle for the usb host mode, something userfriendly...
Any chance for something like this?

Diamondback2010 said:
Next step should be a kind of toggle for the usb host mode, something userfriendly...
Any chance for something like this?
Click to expand...
Click to collapse
The problem is that as far as I know once you have the ehci-ucd module loaded the usb mode change, even if you unload it. Doing an app to load unload all the usb-modules should be trivial, once I get the usb-otg cable I'll try it. Maybe I will code some kind of no-gui just a menu switch-on switch-off app, but doing it blindly would not be very easy :-D
Regards,

with ipv6 removed, google goggles will no longer work. any reason why you removed it? just curious.

Does it work.in hd Rom ?

I flashed it, and it works fine (the usual stuff, that is).
I also went to the linked website, and followed the instructions (though some of it made not much sense).
Then i plugged it into my computer over usb and selected mount as storage, and it mounted - so it didnt work?
Which instructions are the ones we need to follow?
Josh.

w.0.o.t said:
with ipv6 removed, google goggles will no longer work. any reason why you removed it? just curious.
Click to expand...
Click to collapse
Trying to save some bytes, I've put it back as it is only 100Kb more :-D

fllash said:
I flashed it, and it works fine (the usual stuff, that is).
I also went to the linked website, and followed the instructions (though some of it made not much sense).
Then i plugged it into my computer over usb and selected mount as storage, and it mounted - so it didnt work?
Which instructions are the ones we need to follow?
Josh.
Click to expand...
Click to collapse
The instructions about usb host-mode you need a OTG cable and a powered usb hub and then using conectbot or adb through wireless you need to manually load the needed modules, they are all at /system/lib/modules. The minimum is usbcore.ko and ehci-hcd.ko but you will need others to do usefull things. I think that we will need to kill some htc process because it seems that it is accessing the usb in slave mode. Once I'll get the OTG cable I'll try to get further, but right now the usb-host is just supported in the kernel, nothing else.
Regards

kahuna0k said:
Trying to save some bytes, I've put it back as it is only 100Kb more :-D
Click to expand...
Click to collapse
thanks very much. i'm flashing the new one in a minute.

Hy , thanks for u'r work, one more thing can u add support for open-vpn? i flashed u'r kernel but openvpn aint working anymore
thanks

tun module not work,please check

miyu-hitori said:
tun module not work,please check
Click to expand...
Click to collapse
littlej said:
Hy , thanks for u'r work, one more thing can u add support for open-vpn? i flashed u'r kernel but openvpn aint working anymore
thanks
Click to expand...
Click to collapse
new version with tun.ko included

Thank you for very good kernel, but WiFi n?

New version including the snq- gpu fix

kahuna0k said:
New version including the snq- gpu fix
Click to expand...
Click to collapse
so this has BFS scheduler? and does it include the SD read ahead fix?

Hmmm...
I've flashed the kernel but I got an error message when I tried to execute insmod ... ehci-hcd.ko, for the usbcore.ko was ok...
The error says something like "Device or resource busy".
Using Modaco R9 with Sub501 mods (CIFS, Undervolt, CFQ IO Scheduler, Custom governor), baked directly from the Modaco online kitchen.
I really need a help to solve this.
Thank you all!

a question: is bluetooth hid working with this kernel ??

Thanks for this, I LOVE a good kernel for my phone! This feels really nice, not sure if it'll beat out Ziggy's as my favourite but after a few hours I'm loving it!
I'll check back with battery life stats after a day at work

Skilling said:
Hmmm...
I've flashed the kernel but I got an error message when I tried to execute insmod ... ehci-hcd.ko, for the usbcore.ko was ok...
The error says something like "Device or resource busy".
Using Modaco R9 with Sub501 mods (CIFS, Undervolt, CFQ IO Scheduler, Custom governor), baked directly from the Modaco online kitchen.
I really need a help to solve this.
Thank you all!
Click to expand...
Click to collapse
I have the same problem. Please help!!!

[GT-P6210][KERNEL][UV/OC]garyd9's GT-P6210 kernel (updated 2012-01-23)

USE THIS AT YOUR OWN RISK. ​
I am not installing this kernel on your device. I've even gone out of my way to not give clear directions on how to install it yourself. If you decide to install this kernel, you are assuming all risks involved with it.
WARNING: THIS KERNEL IS NOT FULLY COMPATIBLE WITH THE LA3 FIRMWARE UPDATE. USING THIS KERNEL WITH THE UPDATED VERSION WILL RESULT IN WIRELESS ETHERNET BEING DISABLED.
Welcome to my custom compiled kernel for the Samsung Galaxy Tab 7.0 (wifi only.) This kernel will ONLY work for the GT-P6210 model.
The kernel should be compatible with any stock firmware or anything custom that's derived from the stock firmware. (I refuse to call it a ROM. It's not Read Only.)
First, proper credit should go to Entropy512 and his SGH-i777 kernels. It's from that work I was inspired to do this, and from that work where I'm pulling ideas and changes (when compatible.) I'd give some credit to Samsung, but they only bothered to post partial source code, and didn't even bother to post it with the proper config flags.
The idea behind this kernel is and will be to make the device more efficient. Longer battery life while running more smoothly is a Good Thing. I don't care about benchmark scores. In case someone missed that, I DO NOT CARE ABOUT BENCHMARK SCORES. Anyone can tweak a system to get a better benchmark, but that doesn't mean it'll actually work better. Concern #1 is and should always be stability. While some tweaks will be added that allow a user to make the system unstable, they won't be the default.
Differences from stock currently include:
Very slight speed increase in bootup, possibly in other areas
Support for init.d script parsing on bootup
A real busybox (with proper links) installed to /sbin (and therefore available to the system)
Undervolting and minor overclocking support (via SetCPU)
android ram_console support (useful for post-mortem of crashes.)
standard boot animation support
quicker charging with iphone chargers
Voltage and Clock Adjustments:
If you choose to tinker with the processor voltages and/or clock speeds, there will be no support in this thread. None. Yes, I'm using it myself, but I won't even support myself if I screw things up. If you find an issue with this kernel, BEFORE you post about it here, re-test after reverting all the voltage and clock speeds back to default. If it works with the default clocks/voltages, then don't waste your time or mine by posting about it to this thread. It's not supported. You can destroy your tablet by messing with the voltages and clocks.
You'll need a separate tool for voltage and clock adjustments. The one I see most frequently used is "SetCPU" (http://forum.xda-developers.com/showthread.php?t=505419.) I'm in no way affiliated with the author of that tool. You should be warned that SetCPU does not seem to be fully compatible with our tablets: There seems to be no way to bring up the menu in the program. If the program is "honeycomb compatible", this is likely due to the author making assumptions about screen dimensions on tablet devices (fairly common error.) Don't tell me about it. It's not my program.
ToDo:
Find source for the ethernet module and replace it (which will also allow adding more generic optimizations to the kernel.)
ethernet adhoc support (not really kernel specific, but not possible without the ethernet module...)
Figure out what samsung changed in the LA3 kernel (and didn't publish) so I can get the kernel working with the firmware update.
Known Issues:
Probably not compatible with stock firmware updates. (won't fix.)
NOT COMPATIBLE WITH LA3 FIRMWARE UPDATE!!
Flashing Instructions:
This is being released as an installable "update.zip" style installer. Stick the .zip file on your device, reboot into recovery, and install it from there. If this isn't enough information, please search and read the forums before changing your device kernel. (Flashing a .zip in recovery is a very basic skill that should be mastered early.)
Firmware Developers:
If you want to use it, please link to this thread and give clear indication of which version of the kernel you are including.
Legal:
This is based on the linux kernel, and therefore I'm including links to the modified source for the kernel (https://github.com/garyd9/linux_kernel_GT-P6210) and contents of initramfs (https://github.com/garyd9/initramfs_normal_GT-P6210)
PLEASE DO NOT MIRROR THE DOWNLOADS. IF YOU WANT TO REFERENCE THE KERNELS, PLEASE ONLY LINK TO THIS THREAD.

Change Log
20120128:
Support for iphone charger detection - pull up to 750mA from detected iphone chargers (1500mA from the samsung charger, and 500mA from everything else including a computer USB port.)
Testing USB "high current" charging. This is currently not enabled by default (and until I'm happy that it's stable and safe, I won't be documenting it.)
20120123: (actually posted on the 24th)
Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
20120107:
disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
20120105:
added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
20120102:
added android ram_console support. After installing this kernel, if you reboot/crash, it should leave a file in /proc called "last_kmsg" that will show the last several kernel messages from before the reboot/crash.
20120101:
undervolting and overclocking support (only up to 1.4GHz)
If you decide that you want to overclock or undervolt your tablet, you are 100% on your own. You can easily fry your tablet's processor by messing with voltages and clock speeds. If you have issues with this kernel, remove all overclocking and voltage adjustments before you even bother posting on this thread.
Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://forum.xda-developers.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
20111231 (initial release):
build compatible with stock ar6000.ko module
init.d script support
busybox in /sbin
cleanup of kernel config to remove excess debugging (when possible)

Frequently Asked and Anticipated Questions
Q: Will this work with the GT-P6200, GT-P6200L, or SGH-T869?
A: No
Q: Can you make a kernel for the GT-P6200, GT-P6200L, or SGH-T869?
A: I probably could if I had the hardware to test with. Without a sample of hardware, I can't even begin to guess if what I've done already will work, or what it might take to make it work. If you really want me to do one of those devices, please feel free to send me one. (Making a recovery kernel is quite a bit easier as it doesn't have to work with the ethernet, sound, modem or any other drivers.)
Q: Why doesn't this kernel include CWM Recovery?
A: On the GT7+ devices, the recovery boots from a completely seperate partition than the normal boot. When the device boots recovery, the normal boot kernel isn't ever loaded (and vice versa.) Therefore, it doesn't make sense to package them together.
Q: Why is the sky blue?
A: Please refer to: http://www.sciencemadesimple.com/sky_blue.html

reserved for even more future use

Nice.... I installed just fine. Will Play around and let you know. Thanks further kernel....
Sent from my GT-P6210 using xda premium

Nice to see! Now have a good reason to install clockwork recovery! Thanks Gary!
PLEASE IGNORE THE SIGNATURE!
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

mike216 said:
PLEASE IGNORE THE SIGNATURE!
Click to expand...
Click to collapse
Wow, that actually made me laugh out loud. (My wife just ran in to ask if I was alright.) Thank you.

I've got a new and improved signature modified especially for you! Glad to have made you laugh! Happy New year Gary and fellow community members! I wish you and your families happiness and good health!
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

I know kernels can have an effect on colors. Gary does your kernel improve color and if not could you possible hack that part of the kernel to improve in future releases, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update? I know that we have to odin back before we can update in kies but not sure about the other two questions, any help would be appreciated, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

mike216 said:
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update?
Click to expand...
Click to collapse
Probably, but I didn't try it. Let us know how it works out.

Thanks Gary! Recovery is up and running and even made a nandroid. I located it to make sure everything worked (took a really long time). I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel? Thanks for your development! Much appreciated
Sent from my GT-P6210 using xda premium

Just flashed and it feels very smooth so far thanks!
Sent from my GT-P6210 using xda premium

mike216 said:
I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel?
Click to expand...
Click to collapse
What framework are you referring to? I try very hard to make the stuff I do "self contained", so if a cache should be wiped, it either gets wiped automatically, or there's a message displayed telling you to do it manually.
In context of this thread, there's no need to wipe any caches before installing this kernel.
Perhaps your question is in reference to something in another thread?

It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

The framework zip I was talking about was the flashable zip you put together for the theme here in the development section.
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

mike216 said:
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
A kernel is not a ROM, two totally different things and you don't need to wipe to install one. An easy explanation of the difference is a kernel is what runs the hardware (cpu, memory, etc.) and a ROM is just a UI (user interface).
With ROMs the general concensus on wiping is you need to do a full system wipe as well as wipe the dalvik cache if you are switching between ROMs, say from ROM A to ROM B but do not need to wipe if it's just an incremental update say ROM A to ROM A.1 unless advised to do so by the dev.

Awesome work Gary. If I had the knowledge to do this I would. Tab feels great.
Just glad to see some little development finally kicking off.
Sent from my ICS'd themed Galaxy Tab 7+

Glad you finally got things working.
Closed-source modules piss me off... Module versioning enforcement can get even some of the best devs (netarchy and I kept missing each other on IRC, it took a week before we figured out why his Infuse kernels wouldn't boot.)
Samsung is good about releasing kernel source in a timely fashion, but they SUCK at fixing broken source releases.
(Edit: WTF? They included BCM4330 source code in your release but NOT the Atheros 6k drivers?)
Edit: This might be useful, not sure - http://linuxwireless.org/en/users/Drivers/ath6kl

After lots of testing I do find its a little quicker! Don't know if its placebo but it sure feels fast. Nice work Gary. Recovery working great but the only odd thing I noticed was how long it took to do a nandroid backup. For a minute there I thought it froze up. All is good thought
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

[9001][KERNEL][GB] SkyHigh V1.5 [Updated 08-02-13] [Additional BigMem edition]

This is the official thread of my SkyHigh kernel for the Samsung Galaxy S Plus aka GT-I9001. V1.5 is my final release, please read the FAQ in post #2 for more details. Please refer to post #3 for changelogs of new releases, all available downloads are at the bottom of this first post. If you don't know how to get back to stock kernel you MUST NOT install this !
Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this kernel and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !
Terms of use: Remember the power of reading ! If you can't find some particular information on the first page use the search function, it is your best friend.
Besides there are even guides and tutorials all over the forum and in most cases your question was already answered.
If you take a moment and read through the WHOLE post below and a few more moments to read some of all the stuff in other device related threads of this forum, you will find ALL you need just there.
It's not invisible so you CAN find it. And forum rules and good manners tell you to do it exactly like this. And I WILL ignore every question that is already answered here.
Obey the rules !
Kernel feature list
- OC up to 1.8 GHz, UC down to 122 MHz (customisable eg. via AnTuTu CPUmaster/SetCPU)
- Undervolted (750 mV minimum) with VDD support (customisable eg. via AnTuTu CPUmaster/IncrediControl)
- many CPU governors included, smartassV2 is default
- many I/O schedulers, SIO is default
- optimized for high performance AND extreme low battery usage
- JFS and CIFS support
- TUN included (VPN support)
- cleancache (up to V1.4d)
- increased loudness
- all useful Thunderbolt and Adrenaline Shot main tweaks combined, optimized for I9001 and integrated
- init.d support (use carefully, because tweaks are already integrated, installing/executing them twice can result in strange failures)
- Thunderbolt's LMK60 addon (aka adrenaline shot's supercharger V6 tweak) already built-in, DO NOT install separately !
- Thunderbolt's remount script integrated
- Thunderbolt's zipalign script integrated
- Thunderbolt's graphics addon integrated
- Thunderbolt's binary addon integrated
- Thunderbolt's sqlite addon integrated
- Thunderbolt's screenstate_scaling script not included but compatible
- enhanced 3D graphics (updated internal kernel drivers)
- I8150 GPU libraries included in CWM package up to V1.4d, optional in V1.5
- custom bootanimation support (animation NOT included, place your own here: /system/media/bootanimation.zip)
- custom bootsound (/system/etc/PowerOn.wav)
- sdcard speed increased
- improved jpg quality for better camera pics
- GPS faster fix in V1.4x only
- in V1.5 stock GPS files are untouched
- and some more which I already have forgotten
​
This kernel is meant for use with ANY Gingerbread stock ROM and custom ROMs as well (i.e. Android V 2.3.x only !). To prevent compatibility problems with custom ROMs that include system tweaks like Thunderbolt and Adrenaline Shot any existing init.d folder will be purged while installing the SkyHigh kernel. This is not a bug but a mandatory feature !
If you think you have an important script you will still need with SkyHigh like the screenstate_scaling script, copy it to your (internal) sdcard first then copy it back to the empty init.d after installing SkyHigh.
init.d support means that SkyHigh kernel will execute any scripts inside a folder /system/etc/init.d automatically but obviously only if these exist.
If you are using a custom ROM without init.d folder or any stock ROM you might have to create the init.d folder yourself. For more details there are tutorials in this forum.
Install instructions:
1. If you don't have CWM (FeaMod Recovery) install this first. If you never heard of that learn all about it here:
http://forum.xda-developers.com/showthread.php?t=1331164
2. Now make a complete nandroid backup of your phone with CWM
3. Download the attached CWM zip package
4. Copy it to your internal sdcard
5. In CWM choose "install zip from sdcard", then "choose zip from internal sdcard"
6. Select the downloaded file "GT-I9001_SkyHigh_kernel_V1.x_CWM_signed.zip"
7. Confirm install with "Yes"
8. Wait till you see the message "Reboot to use SkyHigh kernel V1.x !"
9. Do so like the message says.
10. On first boot this may take a while. You will see the Samsung logo and then a black screen for at least 2 minutes up to 5 minutes. If this happens hang on, don't touch anything and don't switch the phone off or pull the battery. This would most probably break your ROM !
11. Usually many files and databases are optimized on first boot but eventually you will see the lock screen or PIN dialog. Then you are all set and beginning with the next boot this will be much faster, promised
Remark: especially on preoptimized (custom) ROMs this won't happen since there's not much to optimize. So it's no bug but a feature when it doesn't happen and your phone boots up in less than a minute
​
If you want FeaMod Recovery together with SkyHigh kernel just follow the install instructions above. Install desired version of FeaMod first and then SkyHigh. You will end up with the combination you wanted.
If anything went wrong during install just try again.
If you have any issues with your sdcard(s) this is not due to SkyHigh or its install procedure. I will never ever even touch your sdcard(s). But it is always a good idea to have a rather current backup of the sdcard(s) handy. CWM makes no backup of these, so you have to do that manually.
If your phone doesn't boot even after 10 minutes waiting (see step 10.) or you end up with a damaged system because you didn't wait long enough just go back into CWM and restore the backup you made.
If you can't boot into recovery anymore just install FeaMod 1.2 via Odin again.
If you got severe errors AND didn't make a backup because you knew better than the developer don't even dare to beg for help.
If you encounter any other errors report them here but be sure that this is no feature or problem that was already described above or in the FAQ below.
While V1.3 lacks some of the features above (especially the Thunderbolt/AS tweaks) it is totally safe with sd cards, at least I never got a single report on that issue. The older V1.3 is still added as attachment for your convenience although V1.4d already fixes all sd card problems.

FAQ
For personal reasons resulting in a tremendous lack of time I have to pause all my xda development for an indefinite time. Sorry about that, but I also really can't answer all the questions you might have so please stick to this FAQ and otherwise ask other experienced users/developers in Q&A section.
Besides I'm planning to get a new phone device in just some months so this also means that SkyHigh V1.5 is my last contribution to the i9001 development section. So SkyHigh V1.5 is provided AS IS and there will be no further support whatsoever on my behalf. But V1.5 was beta tested thoroughly for about 3 weeks by several experienced users here before it was published so it is very unlikely that there are still any crucial bugs in SkyHigh V1.5.
Last but not least broodplank1337 offered to maintain SkyHigh in the future but since he is also quite busy please don't press him and give him the time he needs to answer any requests.
Thanks to all members who respect the work of the developers and obey the forum rules for a great time and experience, maybe we will see again one day in another device section on xda-devs.
1. Q: I have sd card issues with SkyHigh kernel, what can I do ?
A: This was fixed in V1.4d, don't use any other 1.4 version ! For more details please refer to post #190 (http://forum.xda-developers.com/showpost.php?p=24247858&postcount=190) first, then have a look at the changelog (V 1.4d) below in post #3.
2. Q: What's the status of my CM7 port ?
A: this is a very complex topic and I paused the development in mid March in favor of this improved kernel. I continued on CM7 for about two weeks in April but now I had to stop it permanently (see first sentence of this FAQ).
I lost any contact to YardE since months so I guess he also surrendered his i9001 development. I still supported some very dedicated users with my knowledge and experience to help them to continue the CM7 porting project but none of them is an advanced developer or even coder so they are all still in learning phase.
3. Q: What about the car dock recognition ?
A: The card dock is not recognized correctly in any custom i9001 kernel that is compiled from Samsung's original i9001 source codes (Linux kernel version 2.6.35.7). However the phone will be at least charged in the car dock with kernels that are compiled from Linux version 2.6.35.14. SkyHigh V1.5 is mainly based on 2.6.35.14 (with some exceptions for Gingerbread compatibility reasons) so the charging works with SkyHigh V1.5 (only). This was tested and verified by Rhonin86, thanks mate.
4. Q: How do I provide a log for debugging ?
A: You must be familiar with adb to do so, if you are not you can only read the adb guide and learn everything about it here:
http://forum.xda-developers.com/showthread.php?t=879701
Then use the following commands to generate two different log files:
Code:
adb shell "dmesg > /sdcard/log.txt"
adb logcat > logcat.txt
If the first command results in a permission error try this:
Code:
adb shell su -c "dmesg > /sdcard/log.txt"
5. Q: Is Script Manager needed to run any scripts in init.d or bolt_scripts or somewhere else ?
A: Not at all. You can delete bolt_scripts if you still find that on your sdcard or somewhere else. You can uninstall Script Manager if you like. And screenstate_scaling script (or any other) will run automatically if copied to init.d with correct file permissions (755 or rwxr-xr-x)
6. Q: May I use SkyHigh kernel with my own custom ROM and publish that on xda-dev ?
A: Of course you can if you don't ask for money for your ROM. This is not a piece of proprietary commercial rip-off nonsense and must not be (re)selled. I am glad if you find it useful, but leave it well alone if you don't like it
7. Q: What are the best cpu governors, i/o schedulers, overclocking and undervolting settings and so on ?
A: the default ones ! Don't touch anything here if you are not 100% sure what these settings do and how they will help you. The given settings base on over 5 month experience and testing on my own i9001 and some others. But as stated in post #190 no two phones are exactly the same so not all of our phones work best with the very same settings. Therefore I added the possibility to customise all these settings if really necessary. But you shouldn't change any of these settings at all if you don't have severe kernel related problems with your phone.
8. Q: The feature list says that bootanimations are NOT included but supported. After I installed version 1.4/1.5 I've got a new bootanimation
A: that's not a new animation, that is just one that was already in your ROM before (in /system/media/bootanimation.zip) but never showed up so far. Most probably it got there with a custom ROM or UOT kitchen or any other mod/app that supports the android default animations. This file normally isn't used on the i9001 because Samsung implemented a proprietary bootanimation method. SkyHigh reverts the Samsung bootanimation procedure to the android default one which is also used on AOSP ROMs like CyanogenMod. So this is also one of many necessary modifications to make a kernel AOSP compatible !
9. Q: How do I install a custom bootanimation ? All my attempts failed.
A: look at FAQ #8 above and at kernel feature list in post #1 !
​

Changelog
Final update to V1.5 and V1.5bm [08-02-13]:
- source files updated from original patch level 7 (Linux kernel version 2.6.35.7) to patchlevel 14 (Linux kernel version 2.6.35.14). This can be regarded similar as a service pack release of Windows (more stability and less bugs overall)
- especially kernel GPU drivers for the Qualcomm Adreno 205 chip are more stable on my device (had some issues with one app that was solved by this update)
- also the car dock driver is improved, battery is now charged in Samsung's original car dock (though car dock mode still isn't activated, see also FAQ #3 above)
- EGL graphics libraries that come with SkyHigh V1.4x (these libraries are OUTSIDE the kernel, but included in the CWM install package) are EXCLUDED now and only come in an optional library pack (because these are the only ones that have at least significantly better performance in benchmarks, but some users say they are more laggy in everday use).
This means for V1.5 that everybody can decide for himself if he wants to use the EGL libraries that come with his ROM or the i8150 libraries or even any other versions that he will just install himself. More details can be found in post #566 http://forum.xda-developers.com/showpost.php?p=37391142&postcount=566
- faster GPS fix that comes with SkyHigh V1.4x was also EXCLUDED since it didn't work for some people. SkyHigh V1.5 doesn't even touch any GPS related files or drivers, there is just the original Samsung stock driver inside the kernel, nothing else.
But after installing a new kernel or ROM the first initial sat fix usually takes really long (2-5 minutes). This is normal ! But after that it should be faster, about 5 to 60 seconds depending on factors like position, movement, shielding and so on.
So if you have any GPS issues it is NOT due to the kernel but due to your (custom) ROM or any other GPS related factors (and there are many). Please refer to the following posts to learn more about possible GPS issues. These posts were only meant for V1.4x since only this version replaces gps.conf but they also provide some general details about GPS issues: http://forum.xda-developers.com/showpost.php?p=24301498&postcount=205 and here: http://forum.xda-developers.com/showpost.php?p=24565586&postcount=319
- finally there is a separate BigMem edition of SkyHigh called V1.5bm
This BigMem edition provides 376 MB available internal memory but breaks 720p video recording on some devices. While it still works on some devices there are rumors that it is also still possible on any device but by some alternative method. I never tested nor even used 720p recording on my own device since with such a poor camera it is totally pointless to even try HD recording IMHO. So if you want SkyHigh V1.5 WITH 720p video recording you have actually 3 choices:
1. you are lucky and everything works with V1.5bm anyway
2. try to find an alternative solution for video recording, maybe another camera app or a custom ROM is the solution. BTW: hiej claims that it works on his device with BigMem edition, maybe it's a feature of his GingerRevenge ROM so you should test that one first
3. just use the normal V1.5 of SkyHigh, it has 359 MB available memory which is still better than the stock kernels
Update to V1.4d [06-04-12]:
- sdcard problem fixed
In prior 1.4x versions the external SD card is suspended ("ejected") when the phone goes into sleep mode. On some phones the automatic re-detection of the SD card fails several times at wakeup so that it can't be accessed any longer. No data is corrupted though and reboot of the phone or reinsertion of the card are possible workarounds. As this is not practical in everyday use V1.4d solves this sdcard issue by reverting the sdcard power management routines to the original Samsung source version.
Just to be on the safe side I recommend everyone to use this modified V1.4d instead of V1.4 even if you have no sdcard issues so far. At least I do so
Update to V1.4c [06-04-12]:
- obsolete
Update to V1.4b [05-04-12]:
- obsolete
Update to V1.4a [02-04-12]:
- obsolete
​

Awesome! This is without doubt the best i9001 kernel so far, I really like it in my ROM, thanks for this great kernel
(by the way, is this version different then the one you send me to use in the kernel?)

Sounds amazing! This is the same one in broodrom 4 or is this updated?
So far it is working perfectly for me.
Thanks!
Richie
Sent from my GT-I9001 using XDA

no good for me.. hangs and reboots with simplistic F1

broodplank1337 said:
Awesome! This is without doubt the best i9001 kernel so far, I really like it in my ROM, thanks for this great kernel
(by the way, is this version different then the one you send me to use in the kernel?)
Click to expand...
Click to collapse
The kernel is the same but I fixed the install script

skywalker01 said:
The kernel is the same but I fixed the install script
Click to expand...
Click to collapse
Ok great won't need to change it then for now ^^

carlese said:
no good for me.. hangs and reboots with simplistic F1
Click to expand...
Click to collapse
AFAIK simplistic F1 uses FeaCore kernel nonOC which means your phone doesn't like OC/UV kernels. As SkyHigh is OC/UV you can't use it unfortunately, sorry.

skywalker01 said:
AFAIK simplistic F1 uses FeaCore kernel nonOC which means your phone doesn't like OC/UV kernels. As SkyHigh is OC/UV you can't use it unfortunately, sorry.
Click to expand...
Click to collapse
cranium v6 works good with simplistic..

carlese said:
cranium v6 works good with simplistic..
Click to expand...
Click to collapse
OK, if you can provide me some logs I can have a closer look into that, maybe it also applies to others.
But I will need the output of these two adb commands:
Code:
adb shell "dmesg > /sdcard/log.txt"
adb logcat > logcat.txt
If the first command results in a permission error try this:
Code:
adb shell su -c "dmesg > /sdcard/log.txt"

WOW - THX for your work
Hi Skywalker01,
nice to see the resuts of your intense work. Will try it later due to the fact that work is calling
By the way did you find a way to make the kernel recognize the original charging dock meanwhile ? Or if not is it still in your focus ?
I wish you success porting CM and keep on your good work.
Cheers
Rhonin

thanks for the kernel
i can't mount my sdcard in cwm. i currently use this kernel with brood rom.
first time i had this problem was after installing vitaliys kernel. changing kernel and doing a hard reset via *2767*3855# helped (as you can imagine you can't reset it in cwm since you have to mount the sdcard which doesn't work). so i got the suspicion that this is a kernel issue.
i know you said
If you have any issues with your sdcard(s) this is not due to SkyHigh or its install procedure
Click to expand...
Click to collapse
but i'm not sure if this is what you mean since you made mods on the sdcard.

your kernel is amazing sky. i think you made the best kernel for 9001. my phone is like an f-16 because of your kernel

awesome kernel <3 (i got a little question how is the CM7 development going?) (offtopic)

skywalker01 said:
...
- init.d support (use carefully, because tweaks are already integrated, installing/executing them twice can result in strange failures) ...
Click to expand...
Click to collapse
So this means we don't need SM to run all init.d scripts run at boot?
Sent from my GT-I9001 using Tapatalk 2 Beta-2

Hi
Tq for ur kernel...its very amazing the music sound wad better..keep it up bro...
Sent from my GT-I9001 using xda premium

Seems like i am building a new version of Simplistic afterall. Thanks a lot for the great kernel!
Sent from my GT-I9001 using Tapatalk

Woow this sounds promising. Im gonna use it for my ROM if you don't mind...
Sent from my GT-i9001 @ LionROM

How's the battery like with this one?

[A510][KERNEL][2012-11-18] ThrillsKernel V2 & V3

ThrillsKernel for the Acer Iconia TAB A510
version 2012-11-18, built from source​
Here it is, the first ever non-stock kernel for the Acer Iconia TAB A510, dubbed the "ThrillsKernel"!
What's in this kernel:
Comes in two flavors: V2 for ICS ROMs and V3 for JB ROMs
Removed 'Samsung EMMC brick' bug: This prevents your internal memory from becoming corrupted.
CPU Governors: Interactive, conservative, ondemand, powersave, userspace, performance, SmartassV2 and lulzactive.
I/O schedulers: Noop, deadline, CFQ, Simple I/O, V/R and BFQ.
Removed Acer mount security: Now you can mount system as r/w.
NTFS, CIFS, and MD4 support
Tegra3 optimizations
Various other performance tweaks
Installation:
Step 0:
Check this thread to see if you can help the community before you let us help you!
Step 1:
If you don't have it already, install my CWM-Based Recovery.
Step 2:
Download the kernel from this post, extract the .RAR files and put the .ZIP file on your internal or external SD Card.
Step 3:
Start Recovery by powering down your device, holding the Volume down (**) button and turning it on again.
Step 4:
Make a Nandroid Backup. I can't stress this enough. Select backup and restore and choose one of the backup options.
Step 5:
Install this ROM by choosing install zip from sdcard and then choose zip from sdcard or choose zip from external sdcard.
Step 6:
Wait for the installation to finish (this takes a few minutes). Spend your time reading the text below these installation instructions!
Step 7:
Select wipe dalvik cache from the advanced menu, thenreboot system now, and enjoy!
Please read the following carefully before installing this kernel:
I am not responsible for anything you do to your tablet. Whatever you do, you do it at your own risk!
Which version should I install?
ThrillsKernel2 is built on the 2.6.39 linux kernel and intended for A510 tablets with a ICS ROM installed. That's Android version 4.0.0, 4.0.1, 4.0.2, 4.0.3 or 4.0.4.
ThrillsKernel3 is built on the 3.1.10 linux kernel and intended for A510 tablets with a JB ROM installed. That's Android version 4.1.0, 4.1.1 or 4.1.2. There is no support for 4.2+ yet.
FAQ:
Want to use ThrillsKernel in your own ROM? Go ahead, make my day.
Need ***** added to the kernel? Let me know, and I will try!
Want to remove the kernel from a NoThrills ROM? Although it's not recommended, it's possible. Check the instructions in the respective ROM thread.
Want to give me your first born baby? I'd rather not have that, but if you really want to give me something: Either click the 'Donate to me' button on the left, or simply hit the 'Thanks' button on this post.
Changelog:
The ThrillsKernel has the date as version number, e.g. version 20121118 is November 18th, 2012. You can check the status (or changelog, whatever you will) of the kernel by visiting the commit history of my github page:
Click here for updates to ThrillsKernel2
Click here for updates to ThrillsKernel3
Just check what the date of the ThrillsKernel is, and you can simply look at the dates of the commits to see if it's included in the kernel or not. Example: With the version from November 18th, any commit up untill that date is included in the kernel. With the 20120917 version, every commit up untill September 17th is included in the kernel.
​
Downloads:
The kernel is not released on its own yet, because I haven't been able to test it on many ROMs. If you want it, install any of my ROMs:
NoThrills A510 WorldWide optimized Stock ROM
NoThrills A510 "Franken700" Stock ROM
NoThrills A510 Unofficial CyanogenMod 10
ThrillsKernel is included with these ROMs as of 2012/09/17. Developers, feel free to extract the kernel and use it in your own ROMs.

Great new!

NoThrills said:
[*]Removed Acer mount security: Now you can mount system as r/w.​
Click to expand...
Click to collapse
So it was Acer who was messing with remounting system RW?
Suggestion- maybe switching to TinyRCU is a good idea? It has a lower memory footprint and performs faster​

gen_scheisskopf said:
So it was Acer who was messing with remounting system RW?
Click to expand...
Click to collapse
yep, great catch by nothrills, i should have seen this one

Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...

kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
It might be, never looked into it as I have used Screen Filter since forever

kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
I used to use rootdim on my thrive to get it so low I could use the tab as an alarm clock with the screen on and facing me all night.
But trying the same on this a510, the backlight just goes completely off if I try to set it any lower than default. So I wonder if it is a hardware limitation.
It would be nice though. This thing makes my eyes hurt in the morning on the bus to work.

Overclock possible please? Thanks.
Sent from my Galaxy Nexus using Tapatalk 2

kiteman44 said:
Is it possible to extend the minimum level brightness ?
When i read on night, it's too high.
maybe this can help http://forum.xda-developers.com/showthread.php?t=1644345
or maybe by using an dedicated app but...
Click to expand...
Click to collapse
I would absolutely love this feature. I dont like apps messing with my system...

Working A510 CIFS at last!!!
NoThrills said:
ThrillsKernel for the Acer Iconia TAB A510 version 2012-09-17, built from source
[*]NTFS, CIFS, and MD4 support
The kernel is not released on its own yet, because I haven't been able to test it on many ROMs. If you want it, install any of my ROMs:
Click to expand...
Click to collapse
I'm currently quote happy with the stock ROM apart from the lack of CIFS so I took the modules from /system/lib/modules [NoThrills A510 WorldWide optimized Stock ROM] and copied them to my stock (but rooted) A510.
CIFS works perfectly!
Thanks!:good:

Feedback:
I've tried Smartass v2 and Lulzactive and they seem to eat up more juice.
I then checked System Tuner Pro for my CPU times, and I noticed that my CPU would only go from inactive to 1.3 or 1.4GHz. It doesn't use the values in between.
I then switched to Interactive, and I can see the CPU clocks like 400+ and 600+ used again.
Not sure if it's just me though, but I'm putting it out there for everyone to test. Nevertheless, I love this kernel, I love the optimized A510 that you released as it fixed my screen responsiveness issue entirely. Take that Acer!

Another question, what's the best app to tweak the CPU governor? Or I guess... what do you use NoThrills?

salisbury_steak said:
Another question, what's the best app to tweak the CPU governor? Or I guess... what do you use NoThrills?
Click to expand...
Click to collapse
I'd say NoFrills CPU Control- works fine on ICS/JB
Other one is SetCPU but last time I used it there were problems on ICS (January/February)

I've used SetCPU without problems myself. I do however have the purchased version, which is different from the free version that can be found on XDA. That one doesn't seem to be updated anymore.

I've posted about my touchscreen problems in some games in the Optimized ROM thread.. but no answers there. The problem is only there when I use the NoThrills kernel... the stock kernel works good. Have you got any idea what the problem can be?

I had the same problem with some games too ... so I came back to stock kernel
another bug I noticed: battery can't charge to 100%, always blocking at 99%

meldrak said:
I had the same problem with some games too ... so I came back to stock kernel
another bug I noticed: battery can't charge to 100%, always blocking at 99%
Click to expand...
Click to collapse
I just charged to 100% yesterday, it worked.
Did you try to restart your tablet, then charge again?

salisbury_steak said:
I just charged to 100% yesterday, it worked.
Did you try to restart your tablet, then charge again?
Click to expand...
Click to collapse
I didn't reboot just after being blocked at 99%
but between 2 charges I rebooted it and in both case blocking at 99
I came back to stock kernel so I can't test it again

Aaargh, I hate all this touch problems with this f#@$ tablet. Games only playable with the stock kernel, but a piano app is not usable because it doesn't always detect your fingers. Sometimes it's perfect, you can press up to 10 keys at the same time, and sometimes it doesn't recognize two fingers. So I probably need the custom kernel for this.. but I don't want to flash a different kernel for different apps.
This is really the worst device I've ever bought, I hate this piece of crap. I hope this annoying problem will be solved in some future kernels but untill now there isn't a perfect one out there which solves all the problems. No offence to anyone, I know it's all in your spare time, but it's a rant to Acer. A device of about €450 which is soo bad, that's some really bad engineering!

Maybe this new file format would be considerated (or not ) ?
http://www.muktware.com/4485/samsung-creates-new-file-system-f2fs-linux-good-news-android#.UHPclVFKSVh
How to implement
https://lkml.org/lkml/2012/10/5/205
some benchmark results post by the F2FS author : http://www.mail-archive.com/[email protected]/msg318439.html
1. iozone in Panda board
- ARM A9
- DRAM : 1GB
- Kernel: Linux 3.3
- Partition: 12GB (64GB Samsung eMMC)
- Tested on 2GB file
seq. read, seq. write, rand. read, rand. write
- ext4: 30.753 | 17.066 | 5.06 | 4.15
- f2fs: 30.71 | 16.906 | 5.073 | 15.204
2. iozone in Galaxy Nexus
- DRAM : 1GB
- Android 4.0.4_r1.2
- Kernel omap 3.0.8
- Partition: /data, 12GB
- Tested on 2GB file
seq. read, seq. write, rand. read, rand. write
- ext4: 29.88 | 12.83 | 11.43 | 0.56
- f2fs: 29.70 | 13.34 | 10.79 | 12.82

[KERNEL][9305] HboKernel v0.3 - 02.02.2015 (NamelessRom 5.0)

Hi all​
Introduction
I cannot call myself a developer or a kernel master at all. I'm just good at discovering and learning new things and in fact that's the way my journey with kernels started. At this point I want to start a new thread for something different from my earlier work, porting Boeffla kernel.
Features included:
Compiled with 4.9 Linaro toolchain
CPU OC up to 1600Mhz
ZZmoove as default governor (with moderate profile) - best for smoothness/battery life
Zen and Row I/O schedulers
Undervolting interface introduced
Configurable Touchboost
Configurable Touchwake
Charging interface
Boeffla Sound 1.6.6
Dynamic Fsync
Switchable Sharpness Tweak
Led configurable (fading, strength)
Configurable Android logger
Configurable printk logging
Readable: asv level, CPU temperature
Disabled some debug
Few minor tweaks (check github if interested)
If I forgot something - Github is up !
What kernel features may we expect?
F2FS support
Dualbooting support (if I can handle it properly)
What you say?
Compatibility
Flash only on proper roms!
As for now we have only Lollipop version, compatible with NamelessRom (you may try with others LP).
Download
You can download the most recent kernel here -> Click
Source
Github link - Click
Credits
These men never refused to give me a helping hand, advised me what to do and, more important, without their work this kernel wouldn't even exist (opensource doesn't mean no respect!).
@JustArchi
@Lord Boeffla
@Yank555
@ZaneZam
@arter97
Samsung :good:
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can't and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash anything.

Camera bug info: (hidden, only applies to Samsung ROMs)
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solutions:
Option 1 is good for people that rarely change their ROMs (and it fixes EVERYTHING), whether option 2 is better for people changing their ROMs more frequently (however, it's always good to have backup of your SlimISP on sdcard).
Option 1. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my HboKernel
Option 2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Option 3. Read this thread and follow steps --> click
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong

I say, may good luck be with you accomplishing these features in the kernel :good:

Best of luck with this project Hbohd

Thanks to you, there is some life potential remaining for i9305!
Long life to i9305 and may the (dev) force be with you HboHd!
Thanks for your work!

+1 Nice one.

Hbohd said:
What you say?
Click to expand...
Click to collapse
I say: it's freaking interesting!!!!

Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3

aaz03 said:
Just a supposition , for the future , the MDNIe hijack for more natural colors would be great , i'm waiting the F2FS version to switch to NI3
Click to expand...
Click to collapse
Hmm.. Isn't 'Screen mode' under Display settings enough? It gives a little bit of difference without need of additional kernel's code modification.

New alpha 0.1
Okay, to keep this project alive, to show off some progress step by step and to satisfy flashoholics - I've decided to release my small achievements in form of alpha kernels
Firstly, let's restart naming convention of the kernel. It will be simple x.x now, starting from available below 0.1 version :cyclops:
Small changelog:
removed debugging in many places
compiled with linaro 4.9
few tweaking commits
Let's say that due to my 'stupidity' or magic ability to forget something, I've spent on it many hours today :silly:

Is Insecure ADB fixed?

Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin

This is for old bootloader only?

SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..

@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!

ShonkUK said:
SE disabled on 0.1?
it says nothing in system anymore below build
you should maybe consider a txt file in the zip and jot into it every time you change something before you forget
v0.2
tweaked this
added that
etc..
Click to expand...
Click to collapse
sham79 said:
This is for old bootloader only?
Click to expand...
Click to collapse
I haven't stated anything different from what is true I mean, if I write that you can you use it with new bootloader or SE is disabled - then it would be true
I think that in next release I will disable it (simply forgotten due to my compiling problems mentioned earlier).
Oh, and I don't need another changelog when everything is written in the git I haven't just suceeded in uploading it to the github yet :/
machotecba said:
@Hbohd tks for your excelent work!!!, one notice, the I9305 didnt charge the battery when is off. Only, starts and boots normally, and there starts charge. Its only a detail, but in my case Important. Tks again for your work!!!!
Click to expand...
Click to collapse
Yeah, someone mentioned it already. I will try to fix it for next version, thanks!
djb77 said:
Just gave the new version a flash, insecure adb wasn't set. I've fixed it up and attached it.
@Hbohd if you want to patch this in later veresions, make these changes to the /ramdisk/default.prop
- change ro.adb.secure=1 to 0
- change persist.sys.usb.config=mtp to mtp,adb
then just copy the adbd file from my /sbin
Click to expand...
Click to collapse
Will be in for the next so-called 'alpha'

Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?

fpriot said:
Just to be sure, Is "HboKernel alpha v0.1" an update of previous "HboKernel v2" of boeffla thread ? Same source + small changelog you @Hbohd mentionned in post #10 ?
Click to expand...
Click to collapse
Yep, you are right

If I may suggest @Hbohd... Could you please start with the power features implementation? Charging rates, ignore unstable power and margin...
Because these are the ones I really miss... My chargers and/or cables are not good and I need these mods to charge properly...
Thanks!

Firsty thanks for all your hard work.
The phone no longer charges from the car dock. This was the same for the stock kernels in 4.1.2 & 4.3 - still withold bootloader. 4.1.2's was fixed with Pegasus kernel and 4.3 was fixed by your Beoffia 5 kernel.