Related
Noma kernel for Huawei U8150
I'm introducing my custom kernel for Huawei U8150 IDEOS phones. In Kenyan Swahili noma usually means "tight," as in: "That music is tight!" It can be used in other ways too, but I like this connotation the best.
GoalsMy aim is to learn about Linux kernel internals, practice software development using git, and to share with the community. In addition to that, I want to explore and test tweaks which lead to increased/optimized performance on this bargain phone (it's very popular in Kenya). Some of the areas of improvement I have in mind are:
CPU scheduling (UI responsiveness, reducing lag)
CPU frequency scaling governors (smartass? ondemandX? interactiveX?)
I/O scheduling and filesystems (flash disk performance, throughput, latency, maybe simpleio scheduler?)
Security (network, local)
Newer drivers (mainstream, community kernel sources)
Newer GCC compilers (CodeSourcery, Linaro)
Easy rooting
Integrate ClockWorkMod Recovery
Integrate busybox
Explore different compression algorithms (LZO, gzip, LZF, etc) for zImage...
Compcache (zram) (info, announcement)
SLOB memory allocator for better memory allocation? (info)
Current features
Code:
- multi-touch gestures (on devices with [url=http://mjanja.co.ke/2011/08/does-your-huawei-u8150-support-multi-touch-gestures/]supported hardware[/url])
- over/under clocking of CPU frequencies
- Tiny RCU ([url=https://lwn.net/Articles/323929/]info[/url])
- BFQ I/O scheduler ([url=http://algo.ing.unimo.it/people/paolo/disk_sched/]info[/url])
- simpleio scheduler ([url=https://github.com/erasmux/hero-2.6.29-flykernel/wiki/Smartass]info[/url])
- "ck" patch set, including the Brain **** CPU scheduler (BFS) ([url=http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.32/2.6.32-ck2/]info[/url])
- optimized memcopy/memmove ([url=https://github.com/alanorth/kernel_huawei_u8150/commit/871656cbba8ee70d0896ac5cae35a31c2e0873e3]info[/url])
Downloadsfastboot-flashable boot images:
20120514v1: info, download
20110903v83: info, download
20110827v56: info, download
20110824v49: info, download
20110823v47: info, download
noma_20110711v26_boot.img (the "oops, I messed up my phone" kernel... safe, stable defaults; close to "stock" Huawei)
Possibly more here (on github)
Change logChange logs are a pain in the ass to keep up to date, but you can see changes live in the git repository itself. See the commit history of the below branches if you're curious:
froyo-noma-dev commits (dev, bleeding edge)
froyo-noma commits (stable)
Source code
I respect the GPL (the license covering the Linux kernel), so all the up-to-date source code for this kernel is available on github. My kernel is, in turn, based on the publicly-avaiable Froyo kernel sources from Huawei. You're free to fork, modify, and re-release the code as your own, but you must provide the source code for your resulting work. Doing so ensures you honor the terms of the license, but you're also giving back to the community. Basically, don't be a ****.
Credits
I've written zero lines of C code for this kernel. My work is merely to search for interesting modifications to the Linux kernel and add them to a git repository. The real work has been put in by the following people:
Linus Torvalds and all the other Linux kernel hackers around the world
tj_style (multi-touch gesture support)
Stefano Viola (over/underclock)
Renaud Allard for his Galaxy S awesome sauce (kernel, initramfs, etc)
Erasmux (smartassV2)
Let me know if I've left you out.
Donations
Hahaha! No seriously, save your money; I am gainfully employed and I just do this for fun (and lulz)! Instead, just hit "thanks" on this thread. Or, if you're ever in Nairobi you could always buy me a cup of coffee.
Reserved for flashing instructions...
Could you please post fashing instructions via custom recovery?
Im a bit of a noob.
Thanks.
Use fastboot!
Antownee said:
Could you please post fashing instructions via custom recovery?
Click to expand...
Click to collapse
I usually just flash from fastboot lately, as I'm between ROMs too much and I don't bother installing a custom recovery. I suppose I should modify my build scripts to make recovery-flashable zips... hang tight!
... or, if you can't wait, check out my in-depth blog post about compiling and flashing custom kernels on Huawei 8150. I wrote it a few weeks ago when I was a U8150 n00b.
v47 (20110823)
Changes in 20110823v47 (from the git commit log):
Add new, lookup3-based jhash. See: http://burtleburtle.net/bob/hash/doobs.html
pids: fix a race in pid generation that causes pids to be reused immediately
lib/decompress_bunzip2.c: fix checkstack warning
kbuild: drop unifdef-y support
net sched: fix some kernel memory leaks
net/ipv4: Eliminate kstrdup memory leak
Add noma_defconfig. `ARCH=arm make noma_defconfig` to use.
Mostly security and memory leak fixes. The new jhash implementation is based on lookup3.c, a newer, more-efficient implementation (more info here). It's mainly used in the kernel's ipv4 and ipv6 stacks, so don't expect revolutionary performance increases, but it's backwards compatible with the old implementation, so it couldn't hurt to include it.
Default IO scheduler is now deadline (the same as stock Huawei) until I can do some performance tests of other schedulers on this device. Note: I've included BFQ, Anticipatory, CFQ, and noop as well, so you can use those if you like!
Download: noma_20110823v47_boot.img
v49 (20110824)
Changes in 20110824v49 (from the git commit log):
Default to ZLO compression of kernel and ramdisk. LZO has roughly the same (but worse) compression, but is much faster to decompress.
Add LZO compression support for initramfs and old-style initrd
Add support for LZO-compressed kernels on x86
Add support for LZO-compressed kernels for ARM
Add support for LZO-compressed kernels
LZO compression is not as efficient but should be faster than the default compression (gzip), which should improve boot time. See: http://free-electrons.com/blog/lzo-kernel-compression/.
Download: noma_20110824v49_boot.img
Why are you working on Froyo and not on Gigerbread?
Why I'm still working on Froyo
unknhawk said:
Why are you working on Froyo and not on Gigerbread?
Click to expand...
Click to collapse
As this is basically a research project (for both me and the community), the primary reason I'm still "working" on Froyo is that most U8150s are still running Froyo. It's an incredibly popular phone in Kenya (maybe 250,000 - 500,000 units sold?), but I have a hunch very few of them are running non-stock ROMs. Sure, CyanogenMod 7 has a fairly-active U8150 port in progress, but it's not widely used yet.
Like I said, this is primarily a research project, so I'm experimenting for my own curiosity. A part of that is to help people get into Linux kernel, Android, and open-source software development. I want to help set an example of openness, collaboration, documentation, etc.
Also, a lot of the mods I'm making can just as well apply to Gingerbread when we finally get there.
Custom kernel booting on U8150 CM7
unknhawk said:
Why are you working on Froyo and not on Gigerbread?
Click to expand...
Click to collapse
Fun times... I just got a custom kernel to boot on CM7. It's nowhere near as usable as tilal's kernel, but it is a good exercise. More info here on my blog.
I suppose that whenever I get bored enough with Froyo I could always hop over to CM7. AOSP is where my heart is anyways.
v56 (20110827)
Changes (from the git commit history):
Add su, Superuser.apk, and busybox. This kernel/boot.img will now actively root Huawei stock ROMs.
Remove pre-zipped ramdisks as they are now generated on the fly from the compile scripts.
Correct the name of the compressed ramdisk (mkbootfs technically creates a cpio archive, which I then zip).
Make sure `make clean` doesn't delete our pre-compiled wireless module.
Add mkbootfs for creating ramdisks, and update compile.sh to create ramdisks on the fly instead of using a pre-zipped one.
Add ramdisk from U8150 V100R001C18B842
The build system is now a little more flexible and generates ramdisks on the fly. This should make it more powerful and complete. I've also included su, Superuser.apk, and busybox to enable a very cool new feature: rooting! If you haven't forked or cloned my kernel repository yet, what are you waiting for?
Regarding "rooting," forget what you've heard (it's probably wrong). Here's what it actually means:
Copying the su binary to /system/bin/su
Copying the Superuser.apk application to Superuser.apk
Period. What this means is that Android applications can call on the su binary whenever they want to do perform system administration actions (ie, not normal user actions), such as removing system applications with Titanium Backup. The Superuser.apk application is simply a frontend for su; whenever an application tries to execute su, a Superuser dialog pops up asking you to allow or deny the request. This notion, known as "privilege separation," is a common one in all operating systems.
Download: noma_20110827v56_boot.img
v83 (20110903)
Changes (from the git commit history):
sched: export nr_running symbol for use by smartassV2 CPU governor.
config: sync with latest config
sched_fair: Restore less extereme latency values (latency of 6ms)
sched: enable HRTICK
sched_fair: Enable HRTICK
cpufreq: add smartassV2 governor
Switch busybox, older version (1.18.4) but slimmer, more appropriate for our needs (from https://faramir.eriador.org/r/).
Minimum frequency to 122MHz at boot, as well as smartassV2 governor.
Optimized ARM RWSEM algorithm
Cleanup after installation of su stuff. We're on a ramdisk after all, we need to conserve memory.
Change location of root stuff so it isn't in the $PATH
Add Simple I/O Scheduler
Add V(R) i/o scheduler
Update to latest Linaro GCC 4.6 compiler.
Two major changes are the addition of the simpleio IO scheduler and the smartassV2 CPU governor. The simpleio scheduler is based on/around the noop and deadline schedulers, designed specifically with non-rotating media in mind (flash disks, hello!). The smartassv2 CPU governor controls how your CPU switches between frequencies (from 122MHz at idle to 672MHz when in use). I haven't done any benchmarks, but these should improve responsiveness and battery life (in theory at least!).
Other than that, the latest Linaro GCC 4.6 compiler, some small optimizations to ARM-specific functions, and ramdisk/boot cleanups. If you're curious about smartassV2 there's more info here, on erasmux's github page here.
Download: noma_20110903v83_boot.img
cm7 nightly bugged one ?????? i dnt like it iz there iz n e fixed cm7 for ideos ????
btw your kernel doesnt works with cm7 and can u please make a kernel for samsung galaxy gio with smartass v2 ??
Aorth, I tried flashing you kernal, and unfortunately there is one error when flashing with the latest CM7.1. After the flash, the phone will be stuck at the boot screen. I was wondering if you can get this fixed, that'll be great
This kernel is meant for stock ROMs
Den15 said:
Aorth, I tried flashing you kernal, and unfortunately there is one error when flashing with the latest CM7.1. After the flash, the phone will be stuck at the boot screen. I was wondering if you can get this fixed, that'll be great
Click to expand...
Click to collapse
Yeah, this kernel was really meant for Froyo stock ROMs. It won't work on CyanogenMod builds because the ramdisk's init scripts are not compatible.
My U8160 kernel repo has a kernel which works on CM7... but you'll have to compile it yourself
nice kernel ........... working fine on ideos u8150-B .... I flash it with stock rom ................. battry becomes efficient ...
Good Job!
Hello aorth,
I'm now using the LEANdroidMOD 5 based on your kernel and I have to say the name NOMA suits it to a tee. It's my default ROM now when I'm not testing your or tilal6991's builds. Thanks and you have yourself a happy holiday season!
hello,
will there be any update of your noma kernel? this is my fav because all roms out there eat my battery like mad, so i just use your kernel and i'm happy with it
greetings
oh man please update, this is one nice kernel!
CM7 u8150 april 5th
IS this already built in to your CM7 last updated april 5th rom or is that a diffrent kernel? which one is better? would it be hard to install it on that rom? whats the advantages over the built in cm7 rom? Thanks sounds awsome anything to make that baby faster is great. Good work
SU Binary Outdated notification
flasehd v83 on the stock 2.2.1 kenya 1 mutli touch rom all went good but whenever i restart the phone su binary shows the notifications bout su binary being outdated which i updated , i did it multiplie times but it comes up everytime the phone is rebooted , other than that su binary working ok ,
dont know how to fix it , other than that the phone is working so responsive , enjoying it
when i flashed the kernel , the phone was already rooted
cheeeeeeeeeeers
BCK - Bam Custom Kernel for i9003 / Galaxy SL
This Kernel is based on the Chinese GB source, released by Samsung on the 18th of November. Last changes to the source were made by Samsung on November 15th. If you still have questions after reading this post, look at the FAQs (including a list of requested features and known issues).
Kernel features:
No SOD
Bugfixes:
~ Sync bug fixed. Notifications for new mails and messages should arrive within one minute under all circumstances
~ Bluetooth problems fixed. Your phone now should play nice with bluetooth hosts, i.e. your car audio system
~ Micro stutters nearly completely gone thanks to lowered processor transition latency. It's smooooooooth
~ Home button double presses exterminated
Governors:
~ smartassV2 governor by erasmux (default)
~ interactive governor by Mike Chan
IO scheduler:
~ SIO IO scheduler by Miguel Boton (default)
~ BFQ IO scheduler by Paolo Valente and Fabio Checconi
~ deadline IO scheduler
Extended features:
~ ro.secure=0 (root acces through adb shell - to root the 'clean flavour' of BCK, please follow the instructions)
~ EXT4 support (to convert your file system, use amit.bagaria's ext4 add-on .apk) (Only in CF-Root .tar)
~ Support for init.d scripts (to use scripts, please follow the instructions) (Only in CF-Root .tar)
~ BLN support (to use BLN, please follow the instructions)
~ TUN support for VPN networks built-in (no module needed)
~ Increased SD-card read ahead of 768 kb for improved read speed
~ Available with universal CF-root ramdisk based on amit.bagaria's version, improved by loSconosciuto (Only in CF-Root .tar)
~ Available with universal CWM ramdisk (rooted) based on universal CF-root, but 'tweakless' (Only in CWM .tar)
Overclocking and Voltage:
~ Evolved sysfs interface for variable overclock or underclock (all operating points [OPPs] can be adjusted seperately)
~ Fifth OPP (1.2 GHz) available, device booting up at stock speed (1 GHz)
~ Total frequency control. The device will never run at higher speeds than defined by you, not even on WiFi.
~ sysfs interface for voltages (read only at the moment)
~ Slight undervolt (3%) on all OPPs
Flashing , settings and compatibility:
If you want to use BCK, please flash it on a clean stock ROM. If you want to go back to stock, repartition and reflash the full firmware with ODIN. This kernel will not work on CM or MIUI.
The CF-root and CWM versions (PDA_BCK_CF-root_universal_***.tar / PDA_BCK_CWM_universal_***.tar) can be flashed on any recent Gingerbread firmware. These versions are pre-rooted, which means they include Superuser.
The non-CF-root "clean" version (PDA_BCK_XXKPQ_***.tar / PDA_BCK_XXLE4_***.tar) will only work on XXKPQ / XXLE4. Do not flash this version on anything other ROM than the one indicated in the file name. This will break your WiFi. It's especially risky to flash the clean version of BCK after flashing any CF-root kernel before. Don't do it. This version does not include Superuser, but it is prepared to be rooted. Follow the instructions to do this.
After a kernel update, please wait for the device to boot up and reboot once. There is generally no need for cache cleaning or a full reset. To change the governor and IO scheduler, I use NoFrills CPU Control from the market. It's free and reliable.
I recommend to use the clean XXKPQ version. If you want / need to have root, try the CWM version. If you want the 'full package' with FuGu-Mod and more, use the CF-root. I recommend that you do not apply any further tweaks and use a stock ROM.
>>> Warning: Overclocking may damage your device. <<<
Overclocking instructions:
For overclocking, you will need a shell on your phone, or adb access. I use Android Terminal Emulator. Overclocking is currently limited to certain frequencies (see below) and all operationg points will be set with the stock voltage of the corresponding stock frequency. The frequencies you set have to be within the following ranges:
Code:
OPP1: 100 - 500 MHz, stock 300 MHz
OPP2: 501 - 700 MHz, stock 600 MHz
OPP3: 701 - 900 MHz, stock 800 MHz
OPP4: 901 - 1100 MHz, stock 1000 MHz
OPP5: 1101 - 1500 MHz, stock 1200 MHz, not used by default
Remember that your phone uses all operating points depending on the current load. Anything more than 10% higher than the highest stock frequency is likely to be unstable, but you are free to try it. To change the clocks, open Terminal Emulator (or type 'adb shell') and hack in
Code:
su
echo "1100" > /sys/power/overclock_opp4
as an example. The others are opp5, opp3, opp2 and opp1. That's it.
Settings will be lost at reboot, unless you add them to your init.d scripts. I do not recommend this, as this may cause boot loops if the settings are to high! Be advised that NoFrills CPU Control, SetCPU, or whatever app you use that may adjust clock settings interfers with this. You may wanna update their settings after this. I do not recommend using them to set anything at boot if you overclock any OPP, because they might save the wrong frequencies and crash or do worse.
Changelog:
beta 1:
Added cpufreq governors
beta 2:
Changed smartassV2 settings to fit i9003
Added EXT4 support
Smaller zImage due to .config changes
beta 3 (not released):
Experimented with overclocking (not working, yet)
beta 4:
Finetuned smartassV2 settings
Made smartassV2 governor default
Reverted: Smaller zImage due to .config changes
Switched to linaro 4.6.2 toolchain (also used for ICS)
Activated new, aggressive compiler optimizations (-O3)
Added deadline IO scheduler
Added BFQ IO scheduler (10% higher performance than CFQ in Antutu Database IO Benchmark. This does not mean, that the maximum read or write speed increase! It just means that the throughput under heavy load is higher.)
Made BFQ IO scheduler default
Updated all modules
beta 5:
Variable overclock. Loosely based on the modifications of the Nook Color sources by dalingrin and of course with help from amit.bagaria and DooMLoRD.
beta 6:
Variable overclock for all operating points
beta 7:
Switched to universal CF-Root by amit.bagaria (BCK now should run on every recent GB ROM)
Added correct version information in settings menu, credits to DooMLoRD
Fixed cpufreq stats to correctly reflect frequency changes
Increased SD-card read ahead to 768 KBytes. This results in higher SD-card read speeds.
Major simplifications in overclocking code. Works more robust, now.
Added sysfs interface to show voltages. See /sys/power/overclock_vdd_oppX
Changed all voltages to the mainline Linux kernel defaults. This results in a slight 3% undervolt for each OPP, which saves about 5% power and should have no impact on stability whatsoever. Below you will find an overview of the exact voltages.
Code:
stock BCK
OPP1: 1.0250 V 1.0000 V
OPP2: 1.2000 V 1.1625 V
OPP3: 1.3300 V 1.3000 V
OPP4: 1.3875 V 1.3500 V
OPP5: not def. 1.3800 V
beta 8:
OPP5 (1.2 GHz) now enabled in _1200 version of kernel. Thanks to knzo for pointing me to the right patch.
Fixed video recording bug when running at 1.2 GHz
Fixed power management issues at 1.2 GHz
Small changes to smartassV2 and interactiveX settings
beta 9:
Added simple IO ('SIO') scheduler
Only one kernel version now, which includes OPP5 (1.2 GHz) but boots up at 1 GHz. Be advised that your device may nevertheless be running at 1.2 GHz for five to ten seconds at boot because of software limitations.
Changes in PM to always respect cpufreq policy limits. From now on, the device will never run at higher speeds than defined by you, not even on WiFi. Based on an omapzoom.org patch.
Changes to OPP switching code. May lead to less 'hickups'. Based on an omapzoom.org patch.
Bugfix for framebuffer code. Based on an omapzoom.org patch.
Reduced IVA / DSP frequency when on OPP5 to be on the safe side.
beta 9fix:
Reverted: Changes to OPP switching code. May lead to less 'hickups'. (Patch caused random freezes using WiFi.)
Reverted: Bugfix for framebuffer code. (Patch showed no noticeable benefits.)
beta 10:
Fix for sync bug applied. If you still have problems, please report.
This version is identical to beta 10rc14. No need to flash again, if you already are on that version.
beta 11:
Updated universal CF-Root by amit.bagaria to version 9 (released 1st of February 2012), but NO touch recovery
Slight increase in OPP5 voltage (1.38 V -> 1.40 V), may prevent some reported reboots on 1.2GHz
Code:
stock BCK
OPP5: not def. 1.4000 V
Changes in overclocking code to play nice with your frequency settings. If you overclock OPP5 but have restricted freqs to 300 - 1000 MHz, it won't automatically activate OPP5 anymore. The same is true for the lowest OPP.
If you overclock OPP4 above 1000 MHz and have restricted freqs to 300 - 1000 MHz, it will update the upper boundary to the new frequency of OPP4 so it doesn't get deactivated.
beta 12:
Fixed bluetooth problem with car audio systems (Based on omapzoom patches [1], [2] and [3]). Might resolve other bluetooth issues, too.
Universal CF-Root: Fixed bootanimation. Thanks to loSconosciuto.
Universal CF-Root: Fixed install procedure. It will check the actual kernel version, now. Thanks to loSconosciuto.
Universal CF-Root: Fixed fix_permissions script to work on our device. Thanks to loSconosciuto.
Switched to user_defconfig, to avoid unnecessary debug lines in dmesg.
beta 13:
Updated sources to GT-I9003_SWA_GB_Opensource_Update1 from the 30th of March. This also enables TUN support by default. You do not need any modules for this - it works "out of the box" with any VPN client.
Universal CF-Root: Backup is not failing anymore when started from CWM. Thanks to loSconosciuto.
Universal CF-Root: Some small improvements to multiple scripts.
Home button double press issue fixed. There should be no more unwanted double selections in CWM and you can now reliably long press the home button to bring up the list of previously used apps. Idea and timer function taken from a patch by Tegrak.
Fixed priority class for CONTENT_PROVIDER not being set, which may have caused apps of this class to be ignored by the autokiller, resulting in less free RAM.
Lowered OMAP processor transition latency to the value recommended by TI. Subjectively, this brought huge improvements in terms of reducing micro stutters.
Lowered CFS scheduler latency and granularity to values very close to mainline kernel defaults. This could reduce lags in some critical situations, but it doesn't do wonders.
Switched to SIO as default IO scheduler.
beta 14:
Universal CF-Root: Replaced CWMManager and TweakManager with zipaligned files. Thanks to loSconosciuto.
Universal CF-Root: The TweakManager is not replaced on install if it didn't change to preserve it's settings. Thanks to loSconosciuto.
Universal CF-Root: Corrected problems because of too little free space in /system when converting to ext4 by permanently moving InfoAlarm.apk from /system/app to /data/app. Thanks to loSconosciuto.
Universal CF-Root: Fixed the non-working WiFi on XXLE4 and prevented future problems. Instead of patching the WiFi modules, they are now replaced. Thanks to loSconosciuto.
Universal CF-Root: Fixed some small mistakes in the CF-root install procedure.
Switched the compression of ramdisk and kernel from gzip to lzma. This makes the files much smaller and allows us to include more 'stuff'.
Changed smartassV2 settings to wake up at lower frequencies. Further, it is not locked at 300 MHz anymore when the screen is off. Tests showed that free scaling is more battery friendly.
Removed InteractiveX and OndemandX governors and added the Interactive governor by Mike Chan (Source: CyanogenMod Crespo kernel). Since free scaling proved to be more battery friendly, the screen off profiles in InteractiveX and OndemandX made them superfluous.
The device will not scale above 1 GHz for some seconds when booting anymore. It's now safe to use BCK even if your device can't handle 1.2 GHz. Based on a patch by dalingrin.
Changes in PM to respect cpufreq policy limits when playing or recording video. The device should respect your wishes under all circumstances, now
Fixed the SmartReflex voltage calibration of the OMAP SoC for OPP5. This could lower power consumption as soon as OPP5 (1.2 GHz) is activated for the first time.
Slight increase in the OPP5 nominal voltage (1.40 V -> 1.42 V) to allow for some adjustment by SmartReflex (now that it's working...), if necessary. The actual voltage when the device is running will not change for most users! Based on patches by dalingrin and Sanjeev Premi.
Code:
stock BCK
OPP5: not def. 1.4200 V
beta 14 fix:
Universal CF-Root: Fixed the non-ending row of force closes after flashing the Universal flavour of BCK. The clean XXKPQ version did not show these problems and didn't need a 'fix'.
beta 15:
Universal CF-Root: Modified some permissions to bring it closer to the stock ramdisk
Universal CWM: Created a CWM ramdisk based on CF-root, without most tweaks. You now have three BCK flavours to choose from
Updated to newest UPDATE2 sources by Samsung
Sync bug fix reworked to use new Samsung method from UPDATE2. This may lead to slightly lower standby battery consumption.
Fixed accidental front camera mirroring
Editing smartassV2 settings with busybox 1.20.x and newer no longer leads to reboots. Thanks to loSconosciuto for pointing me to the patch.
Fixed complete crash of WiFi driver when activating WiFi by adapting smartassv2 thresholds
Reverted to the original Google Android toolchain using gcc 4.4.3
Because of the toolchain-switch, the compiler optimizations are now back to -O2 instead of -O3
Credits:
Credits go to the mentioned developers of the cpufreq governors, ganeshbiyer, skin1980 and amit.bagaria for the CF-Root and skin1980 for his repack script. Many thanks to DooMLoRD, amit.bagaria, knzo and loSconosciuto for their help! BCK sources are available on GitHub.
Files:
Attached files:
ODIN-flashable PDA_BCK_XXKPQ_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXKPQ ROMs.
ODIN-flashable PDA_BCK_XXLE4_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXLE4 ROMs.
ODIN-flashable PDA_BCK_CF-root_universal_***.tar with CF-root ramdisk ('Universal CF-root flavour'). For all current Gingerbread ROMs.
ODIN-flashable PDA_BCK_CWM_universal_***.tar with CWM (rooted) ramdisk ('Universal CWM flavour'). For all current Gingerbread ROMs.
Other files (not attached):
Old releases and release candidates can be found on Dev-Host. Use these with caution!
MD5 sum:
Code:
PDA_BCK_XXKPQ_beta10.tar: 83013b2d54c52dddb72deec46b5471de
PDA_BCK_CF-root_universal_beta10.tar: e1e8bcc28c878095618413141b642ec1
PDA_BCK_XXKPQ_beta11.tar: 9eaa6d080f3409c4822e38602bad8efb
PDA_BCK_CF-root_universal_beta11.tar: 93437cf26699dfe595881941b13a6a83
PDA_BCK_XXKPQ_beta12.tar: d9849ae7d9587402aa6465081b4c65a1
PDA_BCK_CF-root_universal_beta12.tar: 2107dfbf33b2838e66007f4319bee14e
PDA_BCK_XXKPQ_beta13.tar: bff3112d3249e951a569148d79643744
PDA_BCK_CF-root_universal_beta13.tar: 1fab51d641a8914e11a81781683d7d7d
PDA_BCK_XXKPQ_beta14.tar: 08cd77964c3d8b54b4c97e59500a0b96
PDA_BCK_CF-root_universal_beta14fix.tar: 6a2cda17362f5a2e6aac7e78dbe94089
PDA_BCK_XXLE4_beta15.tar: 7159e6cd5f2b71bebffcb4d86201b6cf
PDA_BCK_CF-root_universal_beta15.tar: ecfa46b8aec239f1ac246df61dc63477
PDA_BCK_CWM_universal_beta15.tar: 765a5253b0313d41399ea86822cf5f80
Nice i'll try it out ! but m not on clean kpq :\ oh well its worth the shot for thse governors and can u please provide the link to the new source ?
phone boots but the boot animation keeps on repeating ! cf root problem !clean kpq did the trick m in !
Oh!very nice
shriomman said:
Nice i'll try it out ! but m not on clean kpq :\ oh well its worth the shot for thse governors and can u please provide the link to the new source ?
phone boots but the boot animation keeps on repeating ! cf root problem !clean kpq did the trick m in ! but how to root it now ? :\
edit- rooted with soc with psnuter had to instal busybox from stricson and all working just fine
Click to expand...
Click to collapse
Thanks bro for your feedback.
Sent from my GT-I9003 using Tapatalk
over clock to ? ghz?
leongwenjun said:
over clock to ? ghz?
Click to expand...
Click to collapse
it doesnt have oc ! it has special cpu governors which are efficient and fast
tough luck for me mate....
i compile a vanilla kernel which is ~200 kb larger than stock zImage and it doesnt even boot!
also,even i want to update to 2.6.35.14,,,,,,,,,,,,,,how u did it without source?
also(2)lz open an acc. on github!
@sakindia123: Take a look here, update your sources to the new version, and get the new toolchain they use (see readme in the sources).
i followed that link before......
ok i will try with new source
what will happen if we use this ? are there any good feautures ?
it has special cpu governors which are efficient and fast
Now just wait for some days guys. Doomlord, bam, sakindia will show u real power of our device.
This is great! Just one little question, you said this is for a chinese firmware, but you mention KPQ, so it can be put in XXKPQ or not? Anyway sorry for my noob question
vishal24387 said:
Now just wait for some days guys. Doomlord, bam, sakindia will show u real power of our device.
Click to expand...
Click to collapse
U forgot To mention "fuss" dude...
Sent from my GT-I9003 using XDA Premium App
Slynightdark said:
This is great! Just one little question, you said this is for a chinese firmware, but you mention KPQ, so it can be put in XXKPQ or not? Anyway sorry for my noob question
Click to expand...
Click to collapse
It is based on the Chinese source - this includes kernel and android system source. But the kernel is universal (not language specific), and I applied all necessary settings for XXKPQ. Therefore you can flash it on KPQ.
what does a kernel do??
it is the main driving force of a phone that i know.
does it make our phone fast??
how to flash it as i would like to give it a try right away!!
can i roll back to stock kernel after this??
sorry for thr noob question as im new to all this.
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
also do we need to have CWM recovery for this????
or we can do it with the stock recovery menu??
i was just doing some testing and the kernel is stuck at "SAMSUNG" bootanimation after a FRESH FLASH...
any idea?
used on XXKPQ FW
I flash your kernel. From last 5hours no SOD ISSUE. I'm using smartass v2 let's see how will battery I will get from it.
Sent from my GT-I9003 using Tapatalk
Fresh flash of what PDA? Yours, mine, GitHub?
@manrock111: smartassv2 gives me slightly higher battery usage than stock. I want to tweak it, but have problems with my sources at the moment.
XDA_Bam said:
Fresh flash of what PDA? Yours, mine, GitHub?
@manrock111: smartassv2 gives me slightly higher battery usage than stock. I want to tweak it, but have problems with my sources at the moment.
Click to expand...
Click to collapse
sorry... did a fresh install of full XXKPQ FW and now its booting
ok now this is weird... suddenly all of my test kernels have started booting
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678873&postcount=472
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0 ROMs. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
IMPORTANT NOTES:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8.3), CM 10.1.x and CM 10.2 (since 1.8.3) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM, P31xx only: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV
brolee93 for latest P51xx Samsung stock boot image
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch blackhawk version attached, PhilZ Touch 5.08.5 attached at post #3
NEXT kernel beta release attached
NEXT tool: http://forum.xda-developers.com/showthread.php?t=2285366
exFAT support files for CM/CM based ROM: http://forum.xda-developers.com/showthread.php?t=2285366 post #2
Todo:
More features in NEXT tool
Special Thanks:
@behemot24, @shakatu, @ironmaskusa, @tetakpatak
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.4
Created 2014-09-21
Last Updated 2014-10-29
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
21/10/2013 1.8.3 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
10/08/2013 1.6.3 -> 1.8.3:
Initial upcoming Samsung 4.2.2 support
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!
Updated to upstream Linux kernel 3.0.41 (incremental patch)
The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.5 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcahe memory corruption problem fixed!
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 new busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM default zRAM size 26% RAM size. Following CM's standard, user can set zRAM value for example to 30% by typing "setprop persist.service.zram 30" over Terminal Emulator or over "adb shell setprop persist.service.zram 30". CM user can use Settings application: Performance - Memory management - zRam.
Swappiness value changed to 90
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRAM support optimized for Android, utilizing the new lzo library.
cleancache support with working zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-22/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
12/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. You must update both 1st and 2nd ROM to renew both ROM vendor binaries!
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
NEXT users, please update your kernel to 1.3 version to avoid filesystem corruption risk on Samsung stock/stock based ROM! Please read Dual Boot FAQs how to update your kernel!
01/06/2013 beta -> 1.3:
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P31xx, that's way this port version directly jump to 1.3
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz. Non OC version as an addon
Both version tested on P3100 (remember, I have no access to P51xx device). Booted, upscale graphics, touchscreen not work, wrong orientation sensor, swapped volume button, got 1280x800 screenshots :laugh:
30/05/2013: Initial beta release.
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
http://forum.xda-developers.com/showthread.php?t=2285366 post #4.
Was waiting for this :victory:
Sent from my GT-P5110 using XDA Premium HD app
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button or better my DTM button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Dual Boot FAQs #29.
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
brolee93 said:
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
Click to expand...
Click to collapse
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Running smoothly for Zap Blaster.
ironmaskusa said:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Click to expand...
Click to collapse
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:
shakatu said:
Running smoothly for Zap Blaster.
Click to expand...
Click to collapse
Really? And all your init.d scripts removed by NEXT
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
shakatu said:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.
Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK.
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
behemot24 said:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
Click to expand...
Click to collapse
For free A lot of clicks to install NEXT package but why people missed to click my Thanks button
EDIT:
This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
rap3rman said:
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Two apps I never use on my tablet, so I haven't tested them...
ketut.kumajaya said:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
Click to expand...
Click to collapse
yeah ok i see this .
can you add Stweaks support ?
RIN Kernel for D850
Close to stock with some sugar added ... delicous!
Hey guys and girls,
you may have seen my unified stock kernel thread already (or may not, but doesn't matter). This kernel is my attempt to build up on the fixed source and add some additional features for us mod lovers to thinker with and to personalize your device to your usage. For now, I'll keep it close to my stock source and just pull some additional features and fixes in, but not to much. That may change in the future (maybe even soon), but for now, I'll stick to that paradigm.
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve? (Features)
Built with sabermod 4.9 toolchain
IO Schedulers
BFQ
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW (default)
SIO
TRIPNDROID
VR
ZEN
Governors
Adaptive
Conservative
DanceDance
IntelliActive
IntelliDemand
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
TCP Congestion Algorithms
BIC
Westwood
Vegas
Veno
Yeah
HTCP
Cubic (default)
Reno
init.d support
intelliplug
intelli thermal v2
Memutil optimizations
Voltage control
SoundControl
OC to 2.7GHz and UC support
Cpu limiter
2-Way Call Recording support
Simple GPU Algorithm
Simple_ondemand GPU Governor fixed
exFat support
ntfs support (bugged)
Oversharpening fix
DriveDroid support
android logger sysfs toggle (disabled by default)
high priority workqueue
Many under the hood fixes
Stability
More to come
How to apply it? (Installation)
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D850
Custom Recovery
Stock or Stock Based ROM (no AOSP)
How to flash the kernel?
Download zip
Place on internal or external SD
Reboot to recovery
Choose install zip
Search for the downloaded zip
Confirm flashing
Wipe cache
Reboot
Have fun
How to boot unbumped kernels?
Only needed for the img files prior version 1.7
Plugin your device to the PC
Open a terminal and execute
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/stock-laf.img # backup the stock download mode to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-laf.img . # backup the download mode image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf # remove the stock download mode
BEWARE, THIS WILL REMOVE YOUR DOWNLOAD MODE!!! YOU WON'T BE ABLE TO FLASH KDZ FILES BEFORE YOU RESTORED IT!!!!
Turn off the device completely, plug in the USB-cable, if you pulled it out and start the device by holding vol up + power till you see some white text on the screen, fastboot should be written somewhere on the screen, afterwards execute the following command on the PC (while in the directory you've downloaded the kernel image to).
D850:
Code:
fastboot boot D850-rin-1.6.img # boot the kernel
BEWARE, NEVER USE FLASH AT FASTBOOT ONLY BOOT, IT WILL TRIGGER SECURITY OF THE LOCKED BOOTLOADER AND YOU WON'T BE ABLE TO BOOT ANYMORE!!!!
You're done now and booted to the custom kernel!
How to make sure you're running the kernel?
To check if you properly booted into the kernel execute this in the command line (terminal emulater or through adb shell):
Code:
cat /proc/version
it should show
Code:
Linux version 3.4.0-rin-g58903a9-dirty ([email protected]) (gcc version 4.9.1 20140710 (prerelease) (crosstool-NG linaro-1.13.1+bzr2673 - Linaro GCC 2014.07 - Cortex-A15) ) #53 SMP PREEMPT Thu Aug 14 13:26:42 CEST 2014
Once more a warning READ IT!!:
BEWARE, when you reboot you'll boot to the stock kernel, you'll have to boot the custom kernel over fastboot every time, when you boot normally, you'll be on the stock kernel, this won't lead to issues, but you'll miss the benefits of this kernel, I know that's not optimal, but the best we can get with the locked bootloader.
How to restore Download mode?
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf # restore the stock download mode from the backup on your external sd
Changes? (Changelog)
26.11.2014/1.8.5
Less frequency steps to UC (better performance for governors hitting each step)
Oversharpening fix (Credits to @Skin1980)
Kernel now flashed with dd within recovery
Added external radio-iris-transport module to fix fm radio
20.11.2014/1.8
build with sabermod 4.9
Graphite build flags
NTFS support
sysfs interface for android logger (Logger disabled by default)
TCP cong algorithms (BIC, Westwood, HTCP, Vegas, Veno, Yeah)
More frequency steps between 300Mhz and 2.7Ghz
17.11.2014/1.7.2
Raise max microvolt at cpu for pm8941 and pma8084 (Possible Green Screen Fix)
Additional warnings fixed
12.11.2014/1.7
images bumped
flashable zip
init.d support (busybox needed)
AIO optmimizations enabled
intelli plug added (credits to @faux123)
****load of warnings fixed
23.10.2014/1.6
D850 support added
Simple GPU Algorithm Support
Overclocking up to 2.76 Ghz
exfat support
intelli-thermal v2 added
smartmax governor added
memutil optimizations
build with NEON kernel mode
2-way call recording patch
DriveDroid cdrom emulation support
Faux SoundControl
Simple-OnDemand fixed
Cpu Freq Limiter
some small fixes and enhancements
14.08.2014/1.0.1
net/ipv4|include/asm-generic: Enhancement of out of bounds fix
14.08.2014
Initial release
Full list of commits can be found here
Where to get it from? (Downloads)
AndroidFileHost | xda | dev host | google drive | trialsrider1
Let me test!! (Beta Testing Community)
Google+ LG G3 Beta Testing Community
Show me the so(u)rce(ry)! (Source Code)
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
@Dreamxtreme
@guyd
@mosincredible
@tobitege
@AndroidUzer
Credits
XDA
Google
LG
@HolyAngel
@faux123
@KAsp3rd
@myfluxi
@trialsrider1
@Skin1980
@Lord Boeffla
@GuneetAtwal
@DooMLoRD
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel, Kernel for the AT&T LG G3
Contributors
Tectas
Source Code: https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.8.5
Stable Release Date: 2014-11-26
Created 2014-10-24
Last Updated 2015-01-09
Any questions? (FAQ)
How can I toggle the android logger?
File Explorer Method:
Go with a root explorer to /sys/kernel/logger_mode and open the logger_mode file.
Remove everything inside that file and put the number 1 to enable and 0 to disable the logger into it and save the file.
Terminal Method:
Enable the logger
Code:
echo 1 > /sys/kernel/logger_mode/logger_mode
Disable the logger
Code:
echo 0 > /sys/kernel/logger_mode/logger_mode
My internal sd is not working, what to do?
Open adb shell or a terminal emulator and type
Code:
su
restorecon -v -R /data/media
Cool. I am not into kernels UT that KS for extending support to the D850.
Wow nice congrats
Will this be easier to use once the Bump! Support is added?!
I will try it out now, but it will be able to be permanent once it is able to be Bump!'ed right?
Sent from my LG-D850 using XDA Free mobile app
sublimejosh2000 said:
Will this be easier to use once the Bump! Support is added?!
I will try it out now, but it will be able to be permanent once it is able to be Bump!'ed right?
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, as soon as the bump method is released I can build a flashable and you can flash it through recovery like usual and don't have to worry about booting it through fastboot.
Sent from my LG-D855
Thanks for brining your kernel to us. This is a great day for AT&T!!!
Would flash image gui tool be able to flash this for us? I used it before on other devices
Sent from my LG-D850
traesnaidensdad said:
Would flash image gui tool be able to flash this for us? I used it before on other devices
Sent from my LG-D850
Click to expand...
Click to collapse
Not till the bump tool is released.
Sent from my LG-D855
When I flash this one, I end up going to a green screen saying HW Reset. I got options to go into Download Mode or reboot. If I reboot, the Kernel doesn't get booted.
17akota said:
When I flash this one, I end up going to a green screen saying HW Reset. I got options to go into Download Mode or reboot. If I reboot, the Kernel doesn't get booted.
Click to expand...
Click to collapse
Interesting, just out of interest, to which version did you update through ota?
Could you try to remove the laf partition to get to fastboot mode and boot to it?
(just replace recovery with laf at the steps to remove the recovery, to boot to it, shut the device down completely, plug in the USB and boot the device through holding vol up + power)
Sent from my LG-D855
The D850 never got any official OTAs that I'm aware of, but I'm on AndroidNow 1.6.
That's what I did initially, but this time I flashed it by removing Recovery. I'll try the LAF fastboot though.
Great work on this.....
Personally I am going to wait for a bumped version - just to make sure I don't screw something up when trying to flash this.....
On that note, have you tried to reach out to the bump team? Perhaps if you explain that you have a kernel waiting to be bumped, they might manually bump the image for you. I know they are trying to work out a method to automate this process, but they have the ability to manually bump stuff right now!
can we get a flashable zip of this please
bkeaver said:
can we get a flashable zip of this please
Click to expand...
Click to collapse
We cannot get a flashable zip until team codefire gets the bump site up and can bump the kernel! The same thing that is holding up a slew of custom romz. This almost reminds me of a Geico commercial and a caveman being under a rock lol.
Deadly venom rom will posted soon. If you want to check it out when the link is up.
Sent from my LG-D850 using XDA Free mobile app
Would love to use this kernel
Sent from my LG-D850 using Tapatalk
So I can flash this with flashify?
Until some sort of twrp zip is made?
I don't really understand the whole is it bump'd or not thing :-/
Granted I did it. I have twrp
Could you give steps if you successfully flashed it plz?
Sent from my LG-D850 using XDA Free mobile app
jaladhjin said:
So I can flash this with flashify?
Until some sort of twrp zip is made?
I don't really understand the whole is it bump'd or not thing :-/
Granted I did it. I have twrp
Click to expand...
Click to collapse
No, sorry, not yet, the problem is, there is a tool needed (not completely true though, it could be signed without the tool as well, but it'd need the fitting certificate, which has only team codefire) to sign not stock kernel images and make them flash and bootable, this tool is the bump tool, which is not released yet.
Sent from my LG-D855
Q&A for [Kernel][23/10/14][D850]Rin Kernel 1.6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel][23/10/14][D850]Rin Kernel 1.6. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i tried this method I. my att g3
Tectas said:
RIN Kernel for D850
Close to stock with some sugar added ... delicous!
Hey guys and girls,
you may have seen my unified stock kernel thread already (or may not, but doesn't matter). This kernel is my attempt to build up on the fixed source and add some additional features for us mod lovers to thinker with and to personalize your device to your usage. For now, I'll keep it close to my stock source and just pull some additional features and fixes in, but not to much. That may change in the future (maybe even soon), but for now, I'll stick to that paradigm.
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve?
Built with linaro 4.9.1 cortex-a15 optimized toolchain
IO Schedulers
BFQ
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW
SIO
TRIPNDROID
VR (default)
ZEN
Governors
Adaptive
Conservative
DanceDance
IntelliActive
IntelliDemand
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
Voltage control
SoundControl
Intelli-Thermal v2
Many under the hood fixes
Stability
More to come
How to apply it?
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be and wait for the bootloader unlock, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D855/P/K, F400/K/S/L, D850
Root
How to use the command line
PC
working fastboot
working adb
How to boot the kernel?
Plugin your device to the PC
Open a terminal and execute
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/stock-laf.img # backup the stock download mode to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-laf.img . # backup the download mode image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf # remove the stock download mode
BEWARE, THIS WILL REMOVE YOUR DOWNLOAD MODE!!! YOU WON'T BE ABLE TO FLASH KDZ FILES BEFORE YOU RESTORED IT!!!!
Turn off the device completely, plug in the USB-cable, if you pulled it out and start the device by holding vol up + power till you see some white text on the screen, fastboot should be written somewhere on the screen, afterwards execute the following command on the PC (while in the directory you've downloaded the kernel image to).
D850:
Code:
fastboot boot D850-rin-1.6.img # boot the kernel
BEWARE, NEVER USE FLASH AT FASTBOOT ONLY BOOT, IT WILL TRIGGER SECURITY OF THE LOCKED BOOTLOADER AND YOU WON'T BE ABLE TO BOOT ANYMORE!!!!
You're done now and booted to the custom kernel!
How to make sure you're running the kernel?
To check if you properly booted into the kernel execute this in the command line (terminal emulater or through adb shell):
Code:
cat /proc/version
it should show
Code:
Linux version 3.4.0-rin-g58903a9-dirty ([email protected]) (gcc version 4.9.1 20140710 (prerelease) (crosstool-NG linaro-1.13.1+bzr2673 - Linaro GCC 2014.07 - Cortex-A15) ) #53 SMP PREEMPT Thu Aug 14 13:26:42 CEST 2014
Once more a warning READ IT!!:
BEWARE, when you reboot you'll boot to the stock kernel, you'll have to boot the custom kernel over fastboot every time, when you boot normally, you'll be on the stock kernel, this won't lead to issues, but you'll miss the benefits of this kernel, I know that's not optimal, but the best we can get with the locked bootloader.
How to restore Download mode?
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf # restore the stock download mode from the backup on your external sd
Changes?
23.10.2014/1.6
D850 support added
Simple GPU Algorithm Support
Overclocking up to 2.76 Ghz
exfat support
intelli-thermal v2 added
smartmax governor added
memutil optimizations
build with NEON kernel mode
2-way call recording patch
DriveDroid cdrom emulation support
Faux SoundControl
Simple-OnDemand fixed
Cpu Freq Limiter
some small fixes and enhancements
14.08.2014/1.0.1
net/ipv4|include/asm-generic: Enhancement of out of bounds fix
14.08.2014
Initial release
Full list of commits can be found here
Where to get it from?
D850-rin-1.6.img: AndroidFileHost | xda | dev host
md5sum: cd843592764abee8cb03dc701612832e
Show me the so(u)rce(ry)!
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
Credits
XDA
Google
LG
@HolyAngel
@faux123
@KAsp3rd
myfluxi
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel, Kernel for the AT&T LG G3
Contributors
Tectas
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.6
Stable Release Date: 2014-10-23
Created 2014-10-24
Last Updated 2014-10-24
Click to expand...
Click to collapse
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
kpparry0156 said:
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Click to expand...
Click to collapse
Please don't quote whole OPs...
Are you sure you took the right file? Just from saying "that's the procedure I've used" I can't tell, sorry, if that's exactly how you've done it, it has to work, as for anybody else, if you did something slightly different, you need to tell.
guyd said:
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
Click to expand...
Click to collapse
Jup, coming today
bump kernel?
It's coming out today.. So I can bump a custom kernel or the rin 1.6 kernel for the d850 correct
kernel
Nice
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Sinterion said:
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Click to expand...
Click to collapse
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Tectas said:
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Cool! Well if you need a tester for the D850, just shoot a PM my way!
Sent from my LG-D850
Curious why some devices get the green screen and some don't. I installed cloudy, then tried installing the kernel zip and same thing. Let me know if you want me to test anything if you get to a point and need someone that's getting the green screen, I'll be more than happy to help
Kernel Version Info
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
What is the most efficient or favorite setup for Kernal
Thanks for getting a flashable zip file out! I was waiting for this because I didn't want to risk messing something up with the original installation method. From what I have read, people really like the kernel. I'm DLing it now!
OP. Any plans to make custom kernel's for AOSP Roms?
Sent from my LG-D850 using XDA Free mobile app
animator776 said:
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
Click to expand...
Click to collapse
Yes, that's normal. Has something to do with the Linux version.
guyd said:
Yes, that's normal. Has something to do with the Linux version.
Click to expand...
Click to collapse
Ok, thanks. I was wondering because I've flashed kernels in the past that display a custom kernel version i.e. "Dorimanx"
I believe the kernel version that is displayed can be changed in the build.prop
Anyone care to post their stable settings for this kernel? I remember a similar thread for the S4 which really helped guys like me who aren't real familiar with all of the different kernel tune-ables.
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
JediSooner said:
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
Click to expand...
Click to collapse
I'm using Nova with some alternate icons without issue. Don't know what to tell you except it's working fine for me.
Problem solved and it wasn't anything kernel related. I forgot that I was playing with moving apps to SD the other day and moved all of my icon packs. Apparently, regardless of the launcher being used, it will load before the SD card initializes, so the icon packs aren't found. I've moved then back to the phone and all is well. Google is definitely my friend.