UPDATE/IMPORTANT/README 1ST
I am giving away the SGS and got a new SGS2. This means I won't be able to test updates on this kernel, this I will DISCONTINUE it soon.
I might update this kernel til i'm unable to (in a week prolly) so i'd suggest to switch over to another kernel, choices are, to my knowledge:
- zach's kernel: lots of tweaks, but people seems to have good results. its based on my kernel
- glitch's kernel: less tweaks but close, higher oc. its also based on my kernel
- cm7's stock kernel: i'm based on them of course, its the same as my kernel minus oc/uv and voodoo, but if you want something simple and stable without caring for oc/uv or voodoo color it's pretty good because it's reliable. voodoo sound works via voodoo +
Note that I'm still hanging out on the CM7 sgs channels and will most likely contribute one way or another still
**********************************************************************
Fat visible download link http://kang.project-voodoo.org/
Disclaimer:
These kernels are provided as-is without any warranty. I'm not here to provide support etc although I might when I'm able, but don't count on it. If your phone explode, it's your problem. Updates are not guaranteed as well.
I made a thread only so that it doesn't get lost in spam and have pms asking where to find it
What's included
Sometimes: testing stuff from teamhacksung before it goes into their stable upstream
Various tweaks: such as JPX screen timings, Haptic feedback and general vibration intensity slightly reduced (integrated upstream)
Voodoo sound patch
Voodoo color patch
[*]Led notification: Now integrated upstream
[*]Extra governors: Smartass, Interactive They're not that good.
Overclock/Undervoltage: I use [email protected] and 1.2Ghz max and rest default, change voltage with "voltage control" (market). Default settings to 1Ghz.
Easy building system and clear commits: for other devs, and myself too lol
Click to expand...
Click to collapse
Credits & stuff:
Thanks to Supercurio for making those great enhancement patches and to the Teamhacksung/CMSGS/CM7 contributors for the CM project. Thanks to many other authors who put their source online, they're too many to name. No thanks to the ones who don't, tho
http://project-voodoo.org/
http://forum.cyanogenmod.com/forum/85-samsung-galaxy-s-experimental-mod/
Click to expand...
Click to collapse
Sources (includes non-GT-I-9000 kernels such as Captivate, Vibrant, etc. - always up to date within ~15min of binary upload depending on my upload speed):
https://github.com/kangsterizer/android_kernel_samsung
If there's anything you don't find in the source (missing source or w/e could ever happen, i'm only another noob human)/ doesn't look correct / you don't understand, don't be shy to ask
Binaries & CWMs (aka fat visible download link - what you're looking for ;-):
http://kang.project-voodoo.org
Other goodies
Netfilter/iptables fix: http://kang.project-voodoo.org/f/iptables-cm7-kang.zip
Nexus S windows USB driver (for SGS CM7) - just like to have the link handy for ADB:
https://dl-ssl.google.com/android/repository/usb_driver_r04-windows.zip
Unpack, go into the device manager, look for the "Nexus S" device, click update driver, have disk/search my computer, put the path to the directory..
Tool for OC/UV: http://forum.xda-developers.com/showthread.php?t=1018411
Some more links
IRC: irc://irc.freenode.org/#project-voodoo irc://irc.freenode.org/#cmsgsteam
Twitter: http://twitter.com/kangsterizer (not using it a lot.. but i'm trying lol)
Click to expand...
Click to collapse
Latest changes
-- r25
- upstream sync (use new cm7 nightly!)
--r12
- upstream sync (camera stuff) (use new cm7 nightly)
--r10
- upstream sync (fix battery info/display)
-- CM7_GT-I9000_kernel_kang_20110504_r9_update.zip
- upstream sync
- some fixes for new recovery
-- CM7_GT-I9000_kernel_kang_20110504_r5_update.zip
- upstream sync
-- CM7_GT-I9000_kernel_kang_20110501_r2_update.zip
- test of new scripts x)
- fixed said new scripts since test failed x)
-- CM7_GT-I9000_kernel_kang_20110501_r1_update.zip
- Supports GB 2.3.4 (upstream)
- Reviewed some code
- Removed governors: ondemand is better in their current state anyway
- using "r" release versionning in case i'm uploading more than 1 kernel per hour or make tests etc.. avoids confusion ;-)
-- CM7_GT-I9000_kernel_kang_20110429_18_update.zip
- allocate more memory to FIMC0 / fixes googles goggles FC
-- CM7_GT-I9000_kernel_kang_20110428_23_update.zip
- upstream sync
- requires latest CM7 nightly for compass etc
- supports bml_over_mtd at flash time
-- CM7_GT-I9000_kernel_kang_20110427_02_update.zip
- upstream sync
- Voodoo sound v8
- some touchkey tweaks
-- CM7_GT-I9000_kernel_kang_20110409_17_update.zip
- upstream sync - untested release (don't have phone access this week )
Older changes are not displayed (lack of space) - see GIT for complete change log
Click to expand...
Click to collapse
NOTE: THESE ARE NOT OFFICIAL VOODOO (or CM7) KERNELS. THESE ARE TEST KERNELS INTEGRATING POSSIBLY UNSTABLE AND UNSUPPORTED VOODOO PATCHES
Fat visible download link http://kang.project-voodoo.org/
Support FAQ
Q: Do LED notification require an app, such as BLN, etc ?
A: No. It uses Android's and Cyanogen settings, other apps are not required, although some that are designed for regular LEDs may work.
Q: How to I turn off LED notifications, scheduled or/and complete turn off?
A: Use Cyanogen's Quiet Hours feature (settings>cyanogen>sound>quiet hours) and check "Dim the LEDs during quiet hours" (in reality it will turn them off on the SGS). If you schedule a complete day, then LED notifications will be off all the time.
Q: How do I setup per app, find other LED settings etc?
A: Settings>cyanogen>interface>LED notifications
Q: What to do with LED color settings?
A: We have only one color, so that doesn't work. Use Green as default setting. Some non-bright colors turn off notification, as it's the equivalent as diming LEDs (note that on real LEDs if you dim them too much they look like off too anyway, the difference is that it's gradual. On the SGS the LEDs can be only on or off, not gradual)
Q: How can I troubleshot my system, I can use ADB but...
A: adb logcat | grep lights (on linux) will show you Android requests to turn LED on or off. "status" tells you what we decide will be interpreted as "turn LED on" (1= on, 0 = off)
adb shell cat /proc/kmsg for live view (or adb shell dmesg if you're using adb after the issues occurs - careful the backlog is limited in size so don't be too slow)
notify_led_on and notify_led_off are requests to the kernel to turn LED on or off.
touch key write/read errors (cypress) are non-fatal failures to ask the touch key to do something (eg lit up the LED), when the hardware goes crazy or there's a logical error in the code (can be both)
touch key recovery routine or "stopped responding" are either hardware errors, either a logical error where the driver would try to write something the touchkey doesnt understand. in some occasion lock&unlock fix those as a work around, of course a permanent fix is required
Q: I used another kernel and some things don't work as expected / I'm the only one to have a problem / music skip with screen off / etc
A: Try this cleanup script: http://forum.xda-developers.com/showpost.php?p=13223426&postcount=1312
Features FAQ
Q: Why do you not implement jhash3?
A: This hash function is used in 3 places in the kernel, and mainly iptables. None of them are performance relevant unless you use your phone as router for a thousand of machines (and that is the *only* case). Yes, it is utterly useless.
Q: Why do you not implement XYZ?
A: Usually, same reason as jhash3. Feel free to suggest tho, some features are actually useful and I don't know everything.
It only work with CM7??? Or work in a Froyo or Gingerbread rom??
You just can't read?! CM7.
thx bilboa, it's really good
Keep up the good work
Sent from my Galaxy S using Tapatalk
Flashed cwm .zip getting force closes when trying to adjust headphone volume in voodoo app read about this on the cm7 thread might have something to do with 2.3.3 lol I got no idea, just throwing it out there you can throw it right back
EDIT: found the voodoo app on supercurios page http://dl.project-voodoo.org/apps/
Sent from my Galaxy S using XDA App
quadix said:
You just can't read?! CM7.
Click to expand...
Click to collapse
I read perfect, that's only a question, do you understand???
Medel-Silver said:
I read perfect, that's only a question, do you understand???
Click to expand...
Click to collapse
Its very stupid question, hence the a bit rude, yet truthful, answer. It says in the topic what this kernel is for.
I need to backup the WiFi modules before i get flash that?
Thanks a lot for posting this! Do you still have the "old" voodoo control app with you, that works with the headphone amplifier?
Thank you for providing the source code, that gives me an idea on what i have done wrong while implementing voodoo sound
btw have you guys experienced the volume bug mentioned here and here?
Anybody got a solution?
could not download
Sent from my Galaxy S using XDA App
Thanks heaps - installed it apparently ok - it runs the phone - the voodoo app can see the features and recognises that its a compatible kernal - but whenever trying to change the analogue volume - it force closes the app
is this relating to the broken git stuff for cyanogen - unrelated and just me doing something wrong - or its a bug and i can give you some logs or something to check whats happened?
I'll try doing a clean flash from an old firmware and come back again with the results in a few hours when i get home from work (err - probably shouldnt have tried experimenting with it at work - heh)
^^you need voodoo control app and voodoo app for it to get it to work.
@bilboa1
nice to see it's stand alone.
Edit : Crap, i can't get it to download, i've tried different browsers, using my phone. I even tried it from different computer with no luck
It seems github don't like my computer or my phone. Can anyone attach the .zip for i9000, PLEASE.
Hello, I'm from the Captivate forum, just seeing if any known bugs are found I heard Wi-Fi doesn't work.
Also had problems DL'ing. Attached the SGS i9000 file from the CM7_SGS_2011_03_04 folder. Thanks for the kernel!
sorry if this could be a dumb question, but I wanna be sure of what I'm doing:
If i use the CWM package, do I still need to flash te zImage and push the modules??
^^no need to, just flash it from recovery.
~drz
this is base on the latest kernel from the 02/03 update? it's will affect on the speed / smoothness (for bad)?
I think it was built from the latest commit.
just try it out man, if you don't like it, you can just flashed back to the "official" one.
The non-sgs kernel currently check for SGS model before flashing.. which of course won't work ;-) Ill change that when I get a little bit of spare time.
Related
This modification is ONLY for firmwares with Android 2.1 (eclair)!
if you are searching for a froyo (android 2.2) version: BLN for froyo
What is BackLightNotification?
The BackLightNotification mod converts the touchkey backlights into a notification led.
What is modified?
The BackLightNotification mod replaces the kernel by a modified kernel and it also replaces the lights.default.so in /system/lib/hw/.
In detail:
This kernel includes my backlight notification patch and additionally ext4 and tun modules. (For lagfix and vpn support.) The lights.default.so in /system/lib/hw/ enables android led notification via backlights. This mod does not include any modified app. To enable led/backlight notification for an app/function see the Q&A "How do i enable notification for ...?"
What Galaxy S phones are supported?
This kernel is only for i9000 and i9000m (Bell Vibrant).
If you want BLN for any other Galaxy S phone, then please ask someone who creates custom-kernels for that phone, whether she/he would like to include BLN. The patches are compatible to all already released Galaxy S phones.
Does this mod drain the battery?
No, that issue has been fixed in v1.0. Some blogs are still reporting that, but that is an old news that applies to an early beta version.
Measurements showed, that an ongoing BLN increases battery consumption by 0,18% per hour. The average battery consumption without BLN is 1,04% per hour, so an ongoing BLN results in an overall battery consumption of 1,22% per hour. And by the way: ongoing NoLed results in an overall battery consumption of more than 9,5% per hour. Please see the Q&A "How much does this modification affect battery life?".
How reliable will I be notified with this mod?
With this mod you will get 100% reliable notifications via touchkey backlights.
Why could you state, that this mod is 100% reliable?
The BLN mod activates already available APIs in android. If an application initiates a led notification, it will call the notification manager and that will call liblights (lights.default.so), which enables/disables the backlights by calling the (modified) touchkey kernel driver.
For more questions and answers have a look at the Q&A in the second post.
If you have A2SD or mimocan lagfix installed, remove/disable it before installing BacklightNotification.
Instructions for installation/update:
New method: SGS kernel flasher app:
If your phone is already rooted you can try the SGS kernel flasher app.
Just download&install the app and select any .tar or update.zip that you want to flash from this thread.
If your phone is not rooted and/or you dont want to root the phone, you can use the odin/heimdall method.
Update.zip-method:
Download "i9000_BacklightNotification_v1.6.zip" (md5: 606aa95a2b43be900928cd7a32eb5a7e)
copy the zip-file to /sdcard/
rename the zip-file to "update.zip"
power off the phone
boot into recovery mode (by pressing "Vol Up" + "home key" + "power key" together,
when bootlogo appears, release the keys)
apply update.zip (Vol Up/Down to select and Home key to apply -
you will see strange characters and a flickering screen, that is normal)
wait for reboot
install apps, if needed, see the Q&A "How do i enable backlight notification for ...?"
If you want to have more control over BacklightNotification:
BLN control app - blinking, call notification, scheduler and more to come
BackLightNotification with Voodoo lagfix(-only) beta4/v3.0:
i9000_BacklightNotification_v1.6_with_voodoo_lagfix_beta4.zip (md5: dde016adb2c18182a1bff25bdc6a0048)
Support for voodoo lagfix:
Discuss about Project Voodoo / lagfix, color or http://project-voodoo.org/
Removal:
Download "i9000_android_2.1_remove_backlight_notification.zip" (md5: 9a9baa80b18e24eac19c02e7cb3a153a)
(if you have the voodoo package, use the package from project-voodoo)
and continue with step 2. of the instructions above.
Todo for v2 (sorted by priority):
app to enable/disable bln function (without uninstalling) done
add an option to disable/enable bln (without uninstall) added with v1.1
Twitter:
http://twitter.com/neldar_dev
Credits:
supercurio (for voodoo lagfix, his kernel-update.zip-template and the ct-ng config)
Questions & Answers:
How do i enable led notification for ...?
sms: notification by default
touchwiz email: notification by default
gmail: notification by default
Google talk: notification by default
calendar: download "Calendar notifier" app from market (alternative)
call: my BLN control - Pro from market
any other apps not shipped with stock-samsung firmware:
ask the author of the app for notification led support
What lagfixes are supported?
"Voodoo lagfix" is compatible (see first post for voodoo-enabled update.zip)
Chainfire's CFLagFix is compatible
RyanZA's OneClick LagFix APK is compatible
RyanZA's One Click Lag Fix 2.0 is compatible
Tayutama's "LagFix using update.zip's" is compatible
Mimocan's lagfix is not compatible (solution: remove/disable lagfix)
A2SD is not compatible (solution: remove/disable A2SD lagfix)
How much does this modification affect battery life?
With backlight notification permanently powered on, the battery lasts around 82 hours (around 3,5 days, 1,22% per hour). This means, that activated backlights will increase battery usage by about 0,18% per hour. If there is no backlight notification ongoing, battery life is normal (around 96 hours, 1,04% per hour). Tested with flight mode enabled.
How do you test the battery consumption? This is a common and reliable method.
Can you get this mod working with Android 2.2 (froyo)?
BacklightNotification for Froyo is now available.
Could you add a fade feature?
That is not possible, hardware is limited (by controller firmware) to simple on/off.
Could you add a flashing/blinking light/pulse feature/option?
That is available in the froyo kernel combined with the bln control pro.
I got the message "Cannot open update.zip (bad)". What does this message mean?
That means the file got corrupted, you should delete the update.zip in /sdcard/ and download the zip-file again, copy it again to /sdcard/ and rename it to "update.zip".
Source:
kernel: linux-2.6.29 updated | license: GPLv2
normal bln ramdisk | license: unknown (proprietary?) | author: samsung
voodoo lagfix ramdisk | license: GPLv3 | author: supercurio (Francois SIMOND)
BacklightNotification patches v1.6 for eclair | license: GPLv2 | author: neldar (Michael Richter) | comment: compatible to all Galaxy S phones, no porting needed (just enable KEYPAD_CYPRESS_TOUCH and disable KEYPAD_MELFAS_TOUCH in config)
Liblights for BacklightNotification | license: Apache-2.0 | comment: have a look at the NOTICE file
Chancelog:
v1.6 (stable)
new sysfs interface (/sys/class/misc/backlightnotification/) - recommend update
updated kernel source
v1.1:
added: option to disable/enable bln (without uninstall)
v1.0 (stable, based on rc3)
v0.9.8 (release candidate 3):
removed: wakelock -> (hugely) improved battery life
v0.9.6 (release candidate 2):
improved battery life
fixed: wakelock remains enabled after notification is disabled
v0.9.5 (release candidate 1):
reduced size of initramfs
some lowmemorykiller tweaks
updated proprietary kernel modules
solution for calendar & call notification: "Missed Call for Android 2.x" app
v0.9.1 beta:
improved compatibility with lagfixes
(see Q&A "What lagfixes are supported?")
v0.9 beta:
initial release (first public beta)
Are you sure it's not working with JPC?
Does it drain due to missed call/message or because of the background process?
Bec07 said:
Are you sure it's not working with JPC?
Does it drain due to missed call/message or because of the background process?
Click to expand...
Click to collapse
I'm absolutely sure that this modification will not work with Android 2.2 until Samsung will release their sources for 2.6.32 kernel. Hopefully they will release the sources soon after the official release of Android 2.2 for i9000.
There is a wakelock in the driver, to avoid that the backlight controller will be disabled while the phone is suspending.
BUT that means that a full/deep suspend is suppressed and the battery drains a lot faster. Only screen and touch input is disabled.
This should motivate you to react faster on a notification...
If you dont have a notification, the phone can do a full suspend and the battery last longer.
neldar said:
I'm absolutely sure that this modification will not work with Android 2.2 until Samsung will release their sources for 2.6.32 kernel. Hopefully they will release the sources soon after the official release of Android 2.2 for i9000.
There is a wakelock in the driver, to avoid that the backlight controller will be disabled while the phone is suspending.
BUT that means that a full/deep suspend is suppressed and the battery drains a lot faster. Only screen and touch input is disabled.
Click to expand...
Click to collapse
Technically cool... but this limitation makes it useless for everyday use for now. Hopefully someone can figure it out.
RyanZA said:
Technically cool... but this limitation makes it useless for everyday use for now. Hopefully someone can figure it out.
Click to expand...
Click to collapse
It drains battery less than NoLed, because the amoled screen is completely powered off.
And it is more reliable than NoLed, if the applications support led notification.
At the moment you can only choose between this solution and NoLed, both have their disadvantages...
neldar said:
It drains battery less than NoLed, because the amoled screen is completely powered off.
And it is more reliable than NoLed, if the applications support led notification.
At the moment you can only choose between this solution and NoLed, both have their disadvantages...
Click to expand...
Click to collapse
Does this blink the backlight's or keep em on ? Just wondering before i give it a shot. Also could you give a rough idea as to how much it affects battery life ? (% perhaps).
I mean if all it does is blink the backlight for say once every 10seconds, i doubt its a huge battery loss :S
It turns the backlights only on.
Flashing backlights may be a feature for a future release.
With enabled backlight the battery lasts around 36 hours.
If no notification is ongoing, battery life is normal.
neldar said:
It turns the backlights only on.
Flashing backlights may be a feature for a future release.
With enabled backlight the battery lasts around 36 hours.
Click to expand...
Click to collapse
Wow nice.
Would "flashing backlight" be hard to implement ? Would it require an intermediary android app to send calls ?
Just wondering.
Daneshm90 said:
Wow nice.
Would "flashing backlight" be hard to implement ? Would it require an intermediary android app to send calls ?
Just wondering.
Click to expand...
Click to collapse
Only flashing is not so hard, but to safe some battery life while backlights are off is hard.
Android needs around 200ms to suspend and another 200ms to resume.
And switching repeatedly between suspend/resume state could drain the battery even more, if it is not done right.
Samsung removed the led notification from their touchwiz phone app.
I dont know why they did that. It would not hurt anyone, if they had not removed it....
So call notification could be done by an additional intermediary app or by replacing the touchwiz phone app with the aosp phone app.
I applied the update as described. Unfortunately, it bricked my phone. I can hear the Samsung start-up sound, but the screen doesn't come on. Any ideas?
rpritch said:
I applied the update as described. Unfortunately, it bricked my phone. I can hear the Samsung start-up sound, but the screen doesn't come on. Any ideas?
Click to expand...
Click to collapse
Please refrain from using the word "brick" its very misleading.
A kernel cannot brick ur phone.
Just flash the backup image on ur sdcard this script creates.
rpritch said:
I applied the update as described. Unfortunately, it bricked my phone. I can hear the Samsung start-up sound, but the screen doesn't come on. Any ideas?
Click to expand...
Click to collapse
Do you have a lagfix installed?
If yes and the lagfix requires a specific kernel, in that case you should flash that specific kernel.
Otherwise use this stock-samsung android 2.1 kernel with Odin:
http://www.multiupload.com/G5P9BUF2Q7 (md5: f87e6badf3eedac00e57eb43695cde07)
Put your phone into download mode:
Press "Vol Down" + "menu button" + "power button" together, for at least 6 seconds, until download screen appears.
Start Odin and connect your phone to the pc.
Select the appropriate pit file for your firmware and select Kernel_i9000_android_2.1_stock.tar for PDA in Odin.
DONT check "Re-partion".
Click "Start" to begin flash.
Daneshm90 said:
Please refrain from using the word "brick" its very misleading.
A kernel cannot brick ur phone.
Just flash the backup image on ur sdcard this script creates.
Click to expand...
Click to collapse
sorry about that...ive already tried to reflash my firmware and I still have a blank screen...the indicator light stay on. How do I access the backup image?
Cannot open update.zip (bad)....what does this message mean?
Sent from my GT-I9000 using XDA App
anamika said:
Cannot open update.zip (bad)....what does this message mean?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
That means the file got corrupted, you should download it again and copy it again to /sdcard/. Delete the old update.zip in /sdcard/ before that. I have added md5 sums to the first post.
This is so nice...
I wish curio's voodoo magic was finished and public, so every kernel can be patched, so users wouldnt need to make choice...
The mod got an update, it is now more compatible with lagfixes.
I recommend you to update to v0.9.1 beta, if you are on v0.9 beta.
CLagFix 1.80 is tested and compatible.
OneClick LagFix should also work, but i have not tested it yet.
Would it be possible for a youtube video or screenshots of this in action? I don't understand what this would actually look like
LevitateJay said:
Would it be possible for a youtube video or screenshots of this in action? I don't understand what this would actually look like
Click to expand...
Click to collapse
I dont have a camera to take a photo or make a film.
If some one else could do that, i would appreciate that.
So let me try to explain what it does:
If you get, for example, a sms from your friend on your phone with an unmodified samsung-firmware, you will be noticed only by an icon in the notification bar.
This mod allows now every app to activate the backlights (the two led lights under menu and back button) for notifications.
If you now get a sms on your phone the backlights will be activated while the screen is powered off and this is the signal that you should have a look at your phone.
CleanDROIDFollowing on from my WM 6.5 ROMs for the HD2, I now present my first NANDroid ROM. Built for speed, space and maximum customisability to be decided by you - the users!
Main Features:
- Extreme speed and responsiveness
- Froyo 2.2.1
- CyanogenMOD 6.1.1
- ADW Launcher
- Standard Framework
- Ultra Tiny, 320mb free space after flash on Euro HD2
- Gingerbread Keyboard
- LCD Density is 190 for the true HD look
- Custom initrd for performance
- Custom kernel for max performance and battery life
The ROM is small because it is stirpped of all Google applications and varoius other features, such as wallpapers. No wallpapers are supplied other than the one it comes with so you must provide your own. Everything that has been removed is freely available from the Market, so you can choose what you want and nothing is forced upon you
The ROM is completely rooted and SU is working correctly so you will easily be able to change animations, framework, system APKs etc
Installation:
MAGLDR 1.11 or greater required, Radio 2.12.50.xx is reccommended. Load phone in MAGLDR menu mode, select USB flasher. Connect phone to PC with USB cable (allow it to install drivers if necessary) and flash the ROM with the supplied DFT flasher. Its that simple
Kernel changelog + Download + GPL compliance information:
Kernel : GL_Core_v5b
Built from latest master GIT git://gitorious.org/linux-on-wince-htc/linux_on_wince_htc.git
OC 1190/1536mhz added to acpu file, Added IO optimisation sourced from hastarin, Added latest YAFFS + cpufreq drivers from tytung GIT.
The kernel code is not modified in any way from what is available on the below linked repositories + patch file, the only difference being the custom build configuration. All credits for kernel modifications go to hastarin, tytung, cotulla, DFT, markinus and anyone else listed as contributing on the commit list and changelogs
- Latest Patches
- Automatic overclock scaling up to 1190mhz / 1536mhz
- Interactive governor as default
- No Undervolt 1190, No undervolt 1536 and Undervolt 1190 kernels availbale
- Reverted to no-op (better IO performance)
- Reverted to SLUB (better system latencies)
- Added htcleo.board.c tweaks from hastarin
- EXT 2/3/4 support
- Added netfilter for WiFi tethering support throught 3rd party apps
- Fixed 60ma after call drain
- Fixed LED notifications
- Pulled latest commits and rebuilt
- Improved compatability for more devices with Undervolt_1190 and 1536mhz kernels
- Slight performance increase over v4
You can download the complete patch set i use here http://htcfanboys.com/CleanEx/Kernel/KERNEL PATCH.7z
You can download a complete ready to use build for other roms and chefs to use here http://htcfanboys.com/CleanEx/Kernel/DISTRIBUTION KERNEL.7z
Download:
NAND DFT FLASH >> http://htcfanboys.com/CleanEx/CleanDROID 2.55.7z
Build info
~~~~!!!! IMPORTANT - READ !!!!~~~~
From now on, the rom .7z you have downloaded will contain 3 boot.img files. Choose which one you want to try and delete the other two, then rename the one you have chosen to "boot.img", then flash. If you have windows set to auto hide file extensions (99.9% people do) renaming the file to "boot" will be sufficient, otherwise it will end up being called boot.img.img and DFT wont see it!
The three choices are:
- 1190mhz No Undervolt (most stable)
- Undervolt 1190mhz (battery saver - might not work on all devices)
- 1536mhz No Undervolt (Will consume more battery, but faster, compatible with most devices)
Changelog: v2.55
- Ditched undervolting for all but 1190 kernel (for battery saving)
- Added 1536mhz kernel, will work on most devices but use more battery
- Kernel voltage changes should fix FC for everyone whose phone can handle the undervolt 1190 / 1536 kernel
- Flash keep data supported from 2.51/2.50
Changelog: v2.51
- Kernel changes, increased min voltage on UV kernels
- More devices (almost all) should work with UV1190 and UV1305 kernels
- Some minor tweaks
- lil bit faster
- Battery drain should be improved
Changelog: v2.50
- Added 3 different boot.img files to archive (see above)
- Pulled latest commits from GIT, kernel patches and updates
- Rebuilt rom, stability improved
- Updated to CM 6.1.1 from stock Desire build
- INIT changes for uber fast booting
Changelog: v2.02
- Fixed LED notifications
- Several kernel changes for performance
- Switch to interactive governor for better battery life and improved IO
- INIT changes to decrease boot time slightly
- Added SMU (super mega ultraness)
- Reduced by 2mb
- Fixed netfilter and 60ma after call drain
Changelog: v2.00
- Totally rebuilt from the ground up from latest stable Desire CM build
- Completely removed compcache service for more performance
- Smallest build yet - 321mb free on euro HD2!
- Newer custom kernel + accompanying INIT
- Fastest ROM yet!
Changelog: v1.40
- fixed the broken apps to SD feature
- recompiled kernel with latest GIT commits
- tweaked kernel, rom now more responsive, less battery drain, fixed various issues
- fresh flash required
(old changelogs removed)
Additional Info!
Attached to this post is the "LiveWallpaperPicker.apk" install it to be able to set your homescreen wallpaper to any live wallpapers you may have installed
Also attached is GenieWidget for those that want the standard news+weather widget (which is rubbish IMO)
---------------------------------------------------------------------------------------
Credits and Thanks
OCM7, Fadzy, JoPlayer, The_Scotsman, Jan-Willem, Cotulla, Bepe, DFT team and anybody i have forgotten!
FAQ
Q: How to change homescreen dpi?
A: Install Ted (text editor) from market and edit your build.prop or use LCD Density from market.
Q: I have problem with resolution in games.
A: Uncheck compatability mode in spare parts and reboot.
Q: How to keep all the app and settings of the old version?
A: Use MyBackup Pro from Market.
Q: When will FM radio work?
A: When i can get it to work - thats why it has been removed
Q: How to activate battery %?
A: Go to Settings/CyanogenMod settings/user interface/status bar/then click battery %
Q: I'm noticing more battery drain than usuall.
A: You will need to drain/recharge battery before you get full life expectancy out if it - just like any flash.
Q: If you completely run down the battery, would you be able to charge it with the phone again?
A: If your battery is dead, press and hold Vol Down and plug in USB cable / charger at same time. Phone will boot into bootloader and charge there just fine. Leave for 20 mins, pull battery, reboot and charge normally. If phone has just run down, plugging in the charger will usually turn it on.
Q: does it has htc sense?
A: No.
Q: Screenshots?
A: No need, its standard Froyo with ADW launcher
reserved for later use 2
yayy first!!!
Sorry, I hate people who do that but couldn't resist
Sounds interesting, gunna give this a try later, thnx bud, will report any bugs/issues I fine
yayyy, i'm 2nd..lol...me too, fooking hate it, so couldn't resist...downloading - will report back,,,fanks
Cool, i think that when it's not sense, it should be a cyanogenmod
Don't mind making an SD version, for those that are on Windows Phone 7? That would be awesome.
print screens pls?
Yay! Are the pillars of winmo ROM cooking migrating to Android NAND. Not a surprise at all everyone seems to be jumping on the bandwagon. I won't be surprise to see Dutty Throy, Kwbr and the likes here.
lenarass said:
print screens pls?
Click to expand...
Click to collapse
no need, its standard Froyo with ADW launcher
Can u post the gapps please ? that will be great.. or like mdeejay in his builds when i logged in into market he ask me what i want to install...
seavers11 said:
Can u post the gapps please ? that will be great.. or like mdeejay in his builds when i logged in into market he ask me what i want to install...
Click to expand...
Click to collapse
all of the apps removed are freely available in the MArket, no need to post them when you can get them from there. You dont need any special ones or anything, whats available in market will work just fine
I removed them because not everyone for example will want Google Voice, or Youtube, or Voice Search............ this way you can choose your own preference.
look good from your feature list
i'm downloading and will try
but
is it data.img, App2SD or data2Ext?
Thnx this is all i need will try it tonight and report back
sent from my HD2 Android
seavers11 said:
when i logged in into market he ask me what i want to install...
Click to expand...
Click to collapse
it's a cyanogenmod 7 (gingebread) feature, if i'm not mistaken
kernelbase said:
look good from your feature list
i'm downloading and will try
but
is it data.img, App2SD or data2Ext?
Click to expand...
Click to collapse
standard NAND and the standard Froyo Apps2SD functionality.....bit it is small so you get lotsa space...
Hi .Does this build support the HTC official extended battery? Thanks.
luffyp said:
Hi .Does this build support the HTC official extended battery? Thanks.
Click to expand...
Click to collapse
honestly......i dont know. The kernel is not mine. Regardless, any ROM will work with the extended battery, its just your battery reporting will be all screwey
which screen with green logo goes off and appear a black screen with a green logo and 2 antennas of it flashing around without something happening ?
what should i do ?
is tmous friendly? does mms work?
ct9 said:
is tmous friendly? does mms work?
Click to expand...
Click to collapse
yes, and yes #(i cannot test MMS because im in the uk but its working on OCMs build so should work on mine)
[15.July.2011][ROM][GSM][2.3.3] ◄► Overcome ROM v3.0.1-JUPITER ◄► Kernel v3.3.0 ◄►
DISCLAIMER: You know the drill, I am not responsible if loading this rom makes your Tab melt, explode, disintegrate, or cause harm to anyone near it. (I am fairly certain none of that will happen though )
Change log in second post.
ROM FEATURES
BGJP4 Base Rom - ANDROID 2.3.3
Overcome kernel v3.3.0 included
No Modem is included - due to a variety of personal preference I decided to leave that a la carte
Fully Deodexed
Fully Zipaligned
Rooted with busybox installed
Reboot/Recovery/Download options added to the power menu
Accurate battery mod with gingerbread styling
Blur removed across system (i.e. behind power option menu) - significantly improves performance
Power Off confirmation disabled
Screen off animation enabled
Overscroll Glow effect enabled
Added AppWidgetPicker
CSC set to XEU
Ads Blocked
Updated Market to 3.0.26
Updated Maps to 5.7.0
Flash Player removed due to compatibility issue - install from market and you'll be all set.
Updated GMail to 2.3.4
Updated YouTube to 2.1.6
Updated SamsungApps to 2.5.039
Updated StreetView to 1.6.0.6
Updated Thinkfree Office Suite
Removed Startup/Shutdown sounds
Cool boot animation
A2DP Bluetooth Connection Fix Integrated
SIP calling enabled over 3g AND WiFi
Fugutweaks integrated
Browser mods (enabled "Default Zoom" in settings, added "User Agent" in settings, set plugins to "on demand" by default)
KERNEL FEATURES
Support RFS/EXT2/EXT3/EXT4
OC/UV with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Replaced kernel jhash2 with jhash3
Adjusted kernel HZ value to improve smoothness
Optimized lowmemorykiller values
Optimized compiler flags
Voodoo Sound v10 (courtesy of supercurio)
Voodoo Lagfix (courtesy of supercurio)
Overcome CwM Recovery v4.1.0.9 (Custom built Clockworkmod v4.0.0.9)
Full support of internal/external SD cards in Recovery
Simple I/O Scheduler added and set as Default
Kernel tweaks to VM and Scheduler for better performance
Built in CIFS/TUN/SlowWork support
Touchscreen Undervolting (courtesy Koxudaxi)
RAM Undervolting
Stochastic Fair Blue (SFB) Network Scheduler
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications (Thanks to Neldar for the mod and Koxudaxi for the patch)
INSTALL GUIDE
http://www.teamovercome.net/?page_id=64
DOWNLOADS
http://www.teamovercome.net/?page_id=558
TIPS AND TWEAKS
http://www.teamovercome.net/?page_id=68
FAQ's
http://www.teamovercome.net/?page_id=66
SOURCES
https://github.com/alterbridge86
The best is yet to come!
ROM AND KERNEL CHANGE LOG
http://www.teamovercome.net/?page_id=171
Overcome v3.0.1-JUPITER
Overcome Kernel v3.3.0 Included
Themeing tweaks (Thanks to DarkPal and friends)
Market updated to 3.0.26
CSC Changed back to that from JQ1 (this should resolve the issue with downloading zinio/kobo/etc.)
Overcome Kernel v3.3.0
Built using CodeSourcery 2011.03 toolchain (faster and more power efficient code)
Overcome CwM Recovery Updated to v4.1.0.9 (Based off ClockworkMod Recovery v4.0.0.9)
[CWM] Option under Tweaks to enable/disable shortened backlight fix
[CWM] Nandroid restore no longer borks the kernel
[CWM] No more annoying "back button disabled" (Hooray!)
[CWM] Shortened Yes/No confirmation menus
[CWM] Make /dbdata wipe when executing "factory reset/data wipe"
[CWM] Make /emmc/.android_secure wipe when executing "factory reset/data wipe"
[CWM] Complete restructuring of menus
[CWM] Streamlining of commands and elimination of some never used features that were cluttering the interface
Updated to Voodoo Sound v10
Numerous upstream patches
Add V(R) I/O Scheduler
Increase voltages to pre-Icarus levels
Removed device detection script (should resolve all issues with some users getting hung at Samsung screen or having no conversion/cwm)
Tweaks to lowmemkiller behavior
Added arm enhancement to allow CPU-supported unaligned accesses
New release - new thread! Idea behind this is to keep the amount of posts people have to crawl through down to a minimum. Enjoy!
OH WOW!!!!!!
You're Great AB86 and all the OC team
Thanks
Sent from my GT-P1000 using XDA Premium App
Downloading
So definitely solved the recovery problem?? What was causing such a messy recovery??
Pharaohnough said:
OH WOW!!!!!!
Click to expand...
Click to collapse
thanks friends
Wow, new release? that was really fast.
Thanks again guys.
Just one question, what is the version of the kernel in this new version? Because Kernel v3.3.0 is now on download page but in change logs of Overcome v3.0.1 JUPITER in the second post it says: Overcome Kernel v3.2.0 Included.
theduke89 said:
Downloading
So definitely solved the recovery problem?? What was causing such a messy recovery??
Click to expand...
Click to collapse
I'm assuming you're referring to the "disappearing" recovery...basically the way Voodoo works, since its designed to support a broad range of devices, is it runs a script to identify exactly which device its running on. This script dumps the partition table from the /dev/block/mmcblk0 and compares it to a list of known dumps. From then, it decides how to set up the file system. If it fails to find a match, it just exits out and goes to samsung init. As a result, you will either 1) boot into the ROM with the RFS file system or 2) boot into stock recovery, because that's what the stock init does.
What I've done is just remove the detection part and hard code it to a particular file system structure. The issue should definitely be resolved now.
alterbridge86 said:
I'm assuming you're referring to the "disappearing" recovery...basically the way Voodoo works, since its designed to support a broad range of devices, is it runs a script to identify exactly which device its running on. This script dumps the partition table from the /dev/block/mmcblk0 and compares it to a list of known dumps. From then, it decides how to set up the file system. If it fails to find a match, it just exits out and goes to samsung init. As a result, you will either 1) boot into the ROM with the RFS file system or 2) boot into stock recovery, because that's what the stock init does.
What I've done is just remove the detection part and hard code it to a particular file system structure. The issue should definitely be resolved now.
Click to expand...
Click to collapse
Understood, thanks it was less complicated then I thought
Feedback coming soon for Jupiter!!! You are great, friend
Just drop by to say thanks that the jupiter kernel now works on my set up (DXJPE /w ext4). I'm going to drop off to sleep too as it's over 2am here, will post impression later.
sohrab1985 said:
Wow, new release? that was really fast.
Thanks again guys.
Just one question, what is the version of the kernel in this new version? Because Kernel v3.3.0 is now on download page but in change logs of Overcome v3.0.1 JUPITER in the second post it says: Overcome Kernel v3.2.0 Included.
Click to expand...
Click to collapse
I don't know what you're talking about
(It has the proper changelog now )
This looks and works beautiful. Thanks!
Remember, for every whiner there are hundreds of satisfied users which never say a word.
Awesome rom! Thanks! Can someone tell me how to get my market to log in? I am already logged into google. But it keeps telling me to log into google and crashes. Is there a switch somewhere?
is there away to change the color of backgorund and notifaction bar to white instead of black thanks in advance
chevy383surfing said:
Awesome rom! Thanks! Can someone tell me how to get my market to log in? I am already logged into google. But it keeps telling me to log into google and crashes. Is there a switch somewhere?
Click to expand...
Click to collapse
Had the same problem, made factory reset in CWM and then it worked.
Peter Unger said:
Had the same problem, made factory reset in CWM and then it worked.
Click to expand...
Click to collapse
I just tried a factory reset and it crashed. I just now got done going through the whole procedure again. I did a factory reset under privacy in the settings. Should I be doing a factory reset from within clockwork recovery?
I actually just got it working! Thanks again for the rom!
darkness1414 said:
is there away to change the color of backgorund and notifaction bar to white instead of black thanks in advance
Click to expand...
Click to collapse
Look, theming is really personal preference. Its impossible for us to satisfy everyone's taste. The team thinks that black notification bar rocks so that's that. If you wanna change it to white, you either..
1. Apply stock theme patch
2. Learn how to theme and change it to white yourself
Sent from my GT-P1000 using XDA App
Lovely work, once again, guys. Updated using the no-wipe method. No problems at all everything working fine. Love the signal and wifi icons. Looking forward to your next offering. Thanks heaps.
Sent from my GT-P1000 using XDA App
Thanks Alterbridge and Team.
Just installed JUPITER (no wipe) over ICARUS and everthing seems to be working A-1. Love the new boot screen and the ROM is very fast and very smooth!
Just for those that may encounter the same issue:
Had a little anomaly the first time I flashed. All seem to go as it should and everything worked as it should, however, under 'SETTINGS' > 'ABOUT DEVICE', it said that the kernel was 3.3.0 (#79), but the build number was still 3.0.0- Icarus (Also, on initial boot up the boot screen was still the old Icarus screen). So, I repeated the no wipe flash procedure and everything is now working as it should. Correct kernel and build number in settings.
Thus far everything is working A-1 on this super fast and smooth ROM.
Many thanks again to Alterbridge and the Team.
STEP 1: DOWNLOAD TWRP 2.7.x.x and UPDATE (REQUIRED FOR 4.4):
EDIT: @Dees_Troy has an official 2.7.x.x w/ SElinux support here:
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.7.0.1-otter.img
Flash with the following adb commands:
Code:
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.0.1-otter.img
If you have problems with that file and/or don't want to use adb/fastboot flash method, you can download a flashable .zip from the following locations. Use your existing recovery to flash the update:
Mirror 1: Download (Goo.im)
BEFORE FLASHING ANDROID 4.4: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM TWRP.
STEP 2: DOWNLOAD A BUILD OF CM11.0:
DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM
NIGHTLIES:
http://download.cyanogenmod.org/?device=otter
GAPPS (Use Version "CM 11" row):
http://wiki.cyanogenmod.org/w/Gapps
Older builds are found here:
http://goo.im/devs/Hashcode/otter/cm10/
http://goo.im/devs/Hashcode/otter/cm10.1/
http://goo.im/devs/Hashcode/otter/cm10.2/
GAPPS (For Android 4.3/CM10.2 builds):
http://goo.im/gapps/gapps-jb-20130813-signed.zip
CHANGES:
[05/15] More audio updates to fix low-power states (screen off / background music)
[11/25] Released updated build for cm11.0
[08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)
[07/30] Updated to CM10.2 build
[05/26] Backlight driver update to help w/ SODs
[05/24] Sensor updates (includes light sensor now usable in Android OS
[05/24] Reverted 2 sound driver commits in the kernel to help w/ headset function -- testing needed.
[05/14] New audio driver (WIP)
[03/27] Reboot Recovery mode is now fixed
[01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing [email protected])
[01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
[01/07] Battery life / sleep improvements
[01/06] Update to 3.0.50 kernel
[01/06] Update wifi firmware to R5.SP3.06
[12/16] Fixed Deep Sleep
[12/15] Added multi-profile fix
CURRENT KNOWN ISSUES:
The headphone MIC input is not functioning correctly yet. Work in progress.
KERNEL FEATURES:
[08/12] Mainline version updates to 3.0.72 updated to current with Google's kernel/common
[01/06] WLAN Firmware R5.SP3.06
[11/07] Updated to SGX/IMG DDK [email protected] for Android (via omapzoom)
[11/07] WLAN Firmware R5.SP3.03
[09/05] Updated to SGX/IMG DDK [email protected] for Android
Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire
Uses ducati binary from TI based on rpmsg 1.20.5.11 (replaced Archos ducati binary from ICS 4.0.3)
Kernel audio: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now. (NOTE: that audio recording is still not working at this time. Tho it is very close).
MUCH better standby / sleep function. The device will go inactive for much longer periods of time (80-100 seconds) while still waking up appropriately for wifi events, power button triggers, etc. And this is still going to get even better when I re-implement DPLL cascading and the charger fixes coming later.
Many bugfixes pulled down from TI's omapzoom sources.
RESERVED FOR NOTES
XDA:DevDB Information
Official CyanogenMod 11.0 for Kindle Fire 1st Edition, ROM for the Amazon Kindle Fire
Contributors
Hashcode
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-05-01
Last Updated 2014-05-21
UPDATED 2013-11-25 for CM11.0/CM10.2/CM10.1
DEVELOPER BUILDING:
Several patches are outstanding in CM's review so building this from source is currently not an option w/o some Cherry Picks:
Patch 1: http://review.cyanogenmod.org/#/c/53917/
Patch 2: http://review.cyanogenmod.org/#/c/54562/
And I'll be updating more of the cm11.0 gits tonight w/ changes to the build / extract files processes.
Won't get a decent build till that's all done.
KNOWN BUGS:
1. EHCI USB 2.0 isn't able to be add to the kernel w/o it crashing. Need to fix for higher speed USB transfers.
6. Headset recording via the MIC input jack doesn't work
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire by doing the following:
mkdir android
cd android
(Use main repo for CyanogenMod 10.2)
repo init -u https://github.com/CyanogenMod/android -b cm-10.2
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter
FINALLY!
I'll see if I can help with power button LEDs.
*out-of-topic note: 3rd post!
1. The backlight doesn't sync up well with the screen. Meaning that sometimes when you bootup you won't see anything but a black screen. Once the boot is done, you can hit the power button a few times and eventually the screen and backlight will sync up and you'll get a picture.
Click to expand...
Click to collapse
I can't even get a picture.
animefun135 said:
I can't even get a picture.
Click to expand...
Click to collapse
Power button four or five times, and it'll pop up.
Edit: not having the sync issue in HC, hash, do you have the log posted on your site regarding the back light issue? I know its kernel related but 3.2 is a lil more cumbersome, so it could just be OS lag. Are we using 4.0.3 or 4.0.4?
Sent from my MB860 using XDA
Power button four or five times, and it'll pop up.
Click to expand...
Click to collapse
I tried 30+ times.
Nice job Hashcode.
Sent from my PG86100 using Tapatalk
I don't have time at the moment to pull down the sources and poke around for myself, but it sounds like #4 is a script issue of some sort.
Either one of the scripts that needs to fire for shutdown is hanging up, or the output isn't returning properly so that the master script can continue and finish pulling it all down.
If I get a chance tonight, I'll grab the sources and poke around a bit.
I deal with hanging/incorrectly-terminating script **** at work all the time, so now I might even be able to contribute, yay!
Reserving this for a complete description of the backlight driver/issue and related sources for research.
Sent from my DROID4 using XDA
Hey Hash I wanted to let you know that the charger does work for me. I don't have to boot back into twrp. Don't know if its just me or what but it works.
Edit: Didn't see that you had put its not working well instead off not at all, I'll do some more testing to see if it will give me problems. So far plugged it in about 20 times and its registering the charge.
Sent from my Amazon Kindle Fire using XDA
Let me be the first to say "Does Netflix work with this?"
Just kidding, things are coming along it appears, wish I knew more about hacking kernels, last time I did anything with a kernel I ran "make xconfig"
i just get a lit up black screen 0.0??
symbiiote said:
i just get a lit up black screen 0.0??
Click to expand...
Click to collapse
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
isaiahhhhh said:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
Wait, are you talking about things like large grey rows of pixels appearing on the screen? Sometimes I see gradients of monochromatic tones in addition to this. They only appear as the backlight is shutting off.
isaiahhhhh said:
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
your right, sorry, as for the rom, i noticed when i flashed hashcode's rom then reloaded rom over it youtube worked in HD, and that got me thinking, you think we can get a Flashable ZIP of the kernel?
is this the kernel that everyone was waiting for? 3.0?
@shahabk818
YES!
But it's still in development, so not for daily use!
TuikS2 said:
@shahabk818
YES!
But it's still in development, so not for daily use!
Click to expand...
Click to collapse
so this will fix the hardware acceleration problem, right?
shahabk818 said:
so this will fix the hardware acceleration problem, right?
Click to expand...
Click to collapse
So you can't read the title, right? [WIP][KERNEL][DEV-ONLY] 3.0 Kernel Development for Kindle Fire [04-10]
DEV ONLY!
OK, so compiled an aosp last night from the CM9 tree... I'm still not having a back light issue? Can't adjust brightness, but no sync issues. Could it be the ROM?
Sent from my MB860 using XDA
EDIT: I want to remind everyone DO NOT FILE AN UBUNTU BUG REPORT WITH THIS KERNEL INSTALLED, ALWAYS REVERT BACK TO THE STOCK KERNEL IF YOU HAVE AN ISSUE BEFORE FILING
This is my first actual Kernel project, so please be gentle.
This kernel is ONLY for the Nexus 7 (2013) flo. I do not know if it boots on the deb, theoretically it should as I don't have any flo specific options and there are config options for Deb in the Kernel configuration. It should work for those on stable, rc or rc-proposed and may possibly work on devel (not sure) as long as devel has not released a new kernel package (3.4.0-5-flo+)
I have cherry-picked some battery optimizations from bricked-flo, elementalx-flo (4.4 branch) and some additional commits elsewhere in an attempt to not only improve battery-life but also to bring some Android features (DoubleTap2Wake) to Ubuntu Touch.
Currently it has the following:
- ROW I/O scheduler
- Beginnings of OCing (pulled from ElementalX, I think I'm missing some commits to make this relevant though)
- ElementalX's kernel thermal control
- binfmt_misc support
- CD/DVD Filesystem Support for external optical drives (ISO9660/UDF)
- Some Slimbus enhancements
- Battery life optimizations (changing default MHz, etc.)
- Default CPU governor changed from Performance to Interactive (yes, they had it set to Performance, not sure why.)
- Direct Rendering Interface/Direct Rendering Manager (XFree86 + msm_kgsl_drm)
- and more!
You can check my github for the items cherrypicked into it and there is even a current release which has seen my battery drop 4% in the last 30 minutes with the screen fully on (no autolock), WiFi on and Bluetooth.
The name of the kernel is still up for change, TonoKrnl is not going to be it's final name unless everyone likes it.
Repository is at: http://github.com/ShadowEO/TonoKrnl
Releases can be found: https://github.com/ShadowEO/TonoKrnl/releases
Status of Github Repo: It builds. It boots and it runs. I am trying my hardest not to push changes that break building.
Reserved for future use. Currently the status of the kernel's updates can be found on the issue tracker: https://github.com/ShadowEO/TonoKrnl/issues/5
Be patient, if you don't see new releases right away, it's because I'm still in the process of generating them, check back later.
-- Release 1.0.3-UBports (11/19/2017): A lot was done to bring this kernel back into usable state, see below:
Added OTG Charging
Added initscripts for turning on features (Requires the rootfs to be mounted read/write for manual installation, see my latest post #16 I think...)
Created patches to be applied against a clean UBports kernel tree for certain features (right now, only DT2W and USB Charging)
(USB Host Charging was pulled from flar2's ElementalX source code, it is not turned on by default and can be turned on with
Code:
echo 1 > /sys/module/msm_otg/parameters/usbhost_charge_mode
Feature is tested and does work.
Developers:
1.0.3 brought the kernel tree back into a buildable state and also cleaned up some problems with the previous releases. I am in the process of generating a kernel patchset which will be able to be applied to a clean kernel to bring those features to the stock UBports kernel source. After I complete generating the kernel patchset, I will be rebasing the entire kernel project onto a clean tree (As I am absolutely certain that I have problems like unfinished cherry-picks [missing commits] etc.). Be patient regarding these patches, as I am re-adding the features I pulled in originally by hand rather than cherry-picking them as I appear to have fuxxed up somewhere cherry-picking previously.
If you have any random reboots, try:
Code:
echo 1 >/sys/module/msm_watchdog/parameters/runtime_disable
If you still receive random reboots afterwards or if you received them previously but the above command fixes them, please open an issue on my project tracker with a copy of /proc/last_kmsg attached.
Kernel TODO:
Generate kernel patchset and then rebase onto clean kernel tree
Finish Kernel Feature Documentation and publish (these docs will give information on tweaking the changes to the kernel, such as readahead buffer, turning on/off DT2W, turning on/off usbhost charging, etc.)
Move TonoKrnl initscripts into ramdisk, should make them more robust and reliable.
Create ZIP installer for TWRP recoveries (this is needed for automatic installation of kernel modules, since /lib/modules is a read-only, bound mountpoint for the Android LXC container. To fix this, we just have to move /lib/modules out of the Android container.
Allow me two questions:
Which kernel repository is this branched off? Apologies if that is dumb question, my git and kernel knowledge is cursory at best, but I can't seem to figure this out looking through your github repo.
ShadowEO said:
- Direct Rendering Interface/Direct Rendering Manager (XFree86 + msm_kgsl_drm)
Click to expand...
Click to collapse
What's the intention behind this? Does this have anything to do with enabling the freedreno driver for the GPU and would that pave a way to a setup without Mir, but with wayland or X?
doniks said:
Allow me two questions:
Which kernel repository is this branched off? Apologies if that is dumb question, my git and kernel knowledge is cursory at best, but I can't seem to figure this out looking through your github repo.
What's the intention behind this? Does this have anything to do with enabling the freedreno driver for the GPU and would that pave a way to a setup without Mir, but with wayland or X?
Click to expand...
Click to collapse
This started off with the debian source package for linux-image-flo in the Ubuntu archives which is the kernel for our device. The reason you are having trouble with figuring it out is because I started with the base (Ubuntu's 3.4.0-5-flo+), pulled it into an empty git repo and then started cherry-picking features. It was originally going to be for my own personal consumption as I didn't know how well a custom kernel would be received by the touch community (so far, in all the communities I've posted it, you were the only one to ask any questions ), but since I already had a git repo up, figured that I may as well share it. So here I am, an amateur working on the Linux kernel, and learning a lot.
My full intent was to improve the experience (even marginally) on Ubuntu Touch for the Nexus 7 2013, I wanted to bring the mobile kernel features previously found on the desktop that myself or others may find useful (hence binfmt support for qemu-user), there really is no reason for me to turn on DRI/DRM except to allow playing with Wayland and X, yes, that part is correct, and I have tested the freedreno driver with it (Freedreno does get the KGSL DRI device and does start X)
In addition I found some interesting choices in the kernel in terms of battery life, it would seem that the CPU governor used by the default Ubuntu Kernel is Performance, which would explain why the battery dies so fast, I tried to pull in some battery optimizations from a couple other kernels around the Android scene for the device. So far I'm pleased with the results, and recently found that both the original cherry-picking done for DT2W worked along with the code to add fast charging.
I've had to put the project on hold due to work issues, but once I'm able to work on it again, I'm reverting the last 100 changes pulled in that broke my tree and going from there since my original targets in terms of features actually worked. (I'm pretty sure it was some recent changes to the CPU hotplug driver that killed it, I can no longer compile the kernel without mpdecision on, so that's my likely suspect.)
Thanks for your explanations!
ShadowEO said:
This started off with the debian source package for linux-image-flo in the Ubuntu archives which is the kernel for our device.
Click to expand...
Click to collapse
So something like apt source linux-image-flo? And then to build you use the instructions in the package also?
there really is no reason for me to turn on DRI/DRM except to allow playing with Wayland and X, yes, that part is correct, and I have tested the freedreno driver with it (Freedreno does get the KGSL DRI device and does start X)
Click to expand...
Click to collapse
Exciting!
In addition I found some interesting choices in the kernel in terms of battery life, it would seem that the CPU governor used by the default Ubuntu Kernel is Performance, which would explain why the battery dies so fast
Click to expand...
Click to collapse
I'm really only speculating, but my conjecture to previous mentions of odd govenor choices in android kernels was that the actual android power management magic is happening behind the backs of the governors. But, I'm really just babbling. I don't know much of anything about this. You seem to be getting impressive improvements!
I'm reverting the last 100 changes pulled in that broke my tree and going from there since my original targets in terms of features actually worked.
Click to expand...
Click to collapse
So, that means: "If you want to try it now, don't use v1.0.2, but use v1.0.2-alpha for now." Is that about correct?
doniks said:
Thanks for your explanations!
So something like apt source linux-image-flo? And then to build you use the instructions in the package also?
there really is no reason for me to turn on DRI/DRM except to allow playing with Wayland and X, yes, that part is correct, and I have tested the freedreno driver with it (Freedreno does get the KGSL DRI device and does start X) Exciting!
In addition I found some interesting choices in the kernel in terms of battery life, it would seem that the CPU governor used by the default Ubuntu Kernel is Performance, which would explain why the battery dies so fast
I'm really only speculating, but my conjecture to previous mentions of odd govenor choices in android kernels was that the actual android power management magic is happening behind the backs of the governors. But, I'm really just babbling. I don't know much of anything about this. You seem to be getting impressive improvements!
I'm reverting the last 100 changes pulled in that broke my tree and going from there since my original targets in terms of features actually worked. So, that means: "If you want to try it now, don't use v1.0.2, but use v1.0.2-alpha for now." Is that about correct?
Click to expand...
Click to collapse
I removed the problem download, the only ones available are the source tree downloads and the last known good build I had, I have also tested to ensure that the last build up there works as well as it's the one I'm running on my device until I have time to go through the tree again.
As for building, essentially yes, but you have to build the image separately. Due to how Ubuntu currently has the filesystem set up and with Android's boot images, its not feasible to really package it in a traditional sense. Essentially what I did was create a chroot, apt-get source linux-image-flo and then to get a working defconfig I used the config.* files found in Debian.flo and Debian.master, from there was the tree that I used as my base.
Then run make with the following to customize:
Code:
ARCH=arm make menuconfig
ARCH=arm make -j <number of processors>
To build the image, you'll need to grab the boot image from your device and tear it apart using a abootimg them rebuild it with the Ubuntu ramdisk. If you are using MultiROM, you can just drop it in the folder for your ROM.
Edit: As for the weird choice of governors, I noticed during my investigations (via the cpufreq-info package) that while Android is managing the CPUs that are online (I found it's running it's own version of mpdecision behind the scenes inside the LXC container), it's not doing anything to the CPU governor. That's all managed in the kernel right now through CPUFreq it appears and in the stock kernel it's set to performance, as for the reason for it, I'm not sure myself.. The other governors ARE there though, just unused right now.
ShadowEO said:
This kernel is ONLY for the Nexus 7 (2013) flo. I do not know if it boots on the deb, theoretically it should as I don't have any flo specific options and there are config options for Deb in the Kernel configuration.
Click to expand...
Click to collapse
Jup, it does boot on my deb! I've downloaded the .img, put the tablet in bootloader mode and did
fastboot boot TonoKrnl-1.0.2-flo.img
It booted without problems, and so far it's running for about half an hour or so without any problems. Wifi, sound, video, usb mouse, all work fine.
doniks said:
Jup, it does boot on my deb! I've downloaded the .img, put the tablet in bootloader mode and did
fastboot boot TonoKrnl-1.0.2-flo.img
It booted without problems, and so far it's running for about half an hour or so without any problems. Wifi, sound, video, usb mouse, all work fine.
Click to expand...
Click to collapse
Wow, that's great to hear, I wasn't sure but I was definitely curious since I had seen options for both Deb and Flo in the makeconfig page.
If you can script it in (or edit sysfs.conf) to have it write a 1 to /sys/android_touch/doubletap2wake while it's booting, you can have working DT2W and there's quite some others to mess around with under /sys :3 CPU governors are somewhere there too, just don't have it offhand.
Since you are testing it out, have you noticed any changes in the device's normal battery life? The stock kernel seems to drain 1% every 1 1/2 minutes on my Flo, not doubting that the power optimizations ARE working (I know I'm getting much better life), I'm just wanting to ensure that it's not a placebo effect that I'm experiencing.
ShadowEO said:
If you can script it in (or edit sysfs.conf) to have it write a 1 to /sys/android_touch/doubletap2wake while it's booting, you can have working DT2W
Click to expand...
Click to collapse
After
Code:
echo 1 | sudo tee /sys/android_touch/doubletap2wake
I can indeed (sometimes) wake it with double tapping. I have since quite a while (with the standard kernel) the situation that its really hard to wake up. I have to press the powerbutton many many times. Feels like it is sleeping really deeply.
Since you are testing it out, have you noticed any changes in the device's normal battery life? The stock kernel seems to drain 1% every 1 1/2 minutes on my Flo, not doubting that the power optimizations ARE working (I know I'm getting much better life), I'm just wanting to ensure that it's not a placebo effect that I'm experiencing.
Click to expand...
Click to collapse
Well, I haven't noticed anything. I might just not be in the best position to judge. I rarely have it unplugged for more than a couple of hours at a time and I don't generally monitor the battery status closely. That being said though, I have very definitely never experienced anything remotely close to 1% per 1.5 min!
If you have a particular test/measurement you'd like to see - let me know.
doniks said:
After
Code:
echo 1 | sudo tee /sys/android_touch/doubletap2wake
I can indeed (sometimes) wake it with double tapping. I have since quite a while (with the standard kernel) the situation that its really hard to wake up. I have to press the powerbutton many many times. Feels like it is sleeping really deeply.
Well, I haven't noticed anything. I might just not be in the best position to judge. I rarely have it unplugged for more than a couple of hours at a time and I don't generally monitor the battery status closely. That being said though, I have very definitely never experienced anything remotely close to 1% per 1.5 min!
If you have a particular test/measurement you'd like to see - let me know.
Click to expand...
Click to collapse
I may be exaggerating slightly, but normally my tablet goes from 100% to 95% in about 5 minutes while I'm using it after taking it off the charger (in Ubuntu only, may be an rc-proposed thing too). I haven't seen that behavior since changing kernels. I'm gonna see if I can go ahead and start reverting commits today or possibly reset back to the last known good commit.
As for the screen problems, I think there is a bug in the current doubletap2wake driver, if you look at dmesg after using DT2W for a while, you'll see it being spammed with error messages from the touchscreen driver.
That could possibly be related. Additionally, I think the minimum processor speed defaulted to 384MHz (I didn't touch any processor clock speeds in here) which the Performance governor would never had let the processor hit. So it's likely that the minimum processor speed will need bumped up at least one step there, I get some stuttery behavior on the command line when the screen is off which I hadn't received on the stock kernel.
Edit (07/01/16): I'm not sure what else I can really bring to the table here, mpdecision running in the android LXC container defeats any meaningful changes to the clock speed. I also noticed mention that you shouldn't have two hotplugging daemons running at the same time, effectively that is what the new developments would've brought in. I think my best option to continue this would be to wait until the Xenial transition and see if they make any changes for me to update on.
I'm also quite a novice, so besides cherry picking commits, I'm not sure what else I can do.
ShadowEO, is bluetooth working on your device? With your kernel or with the one from Canonical?
I can't seem to get anything at all to show up on my deb.
I am so embarrassed that I didn't check this thread in so long. Ya, Bluetooth still works on my device with either kernel. Sometimes it doesn't seem to like to power on, so if you are having trouble, try this.
Open Terminal,
do sudo bluetoothctl and see if Nexus 7 (2013) shows up in there. If it does, type power on and hit enter. You should see the bluetooth indicator show up in the status bar. If it doesn't, exit bluetoothctl and do these from a root prompt:
start bluetooth-touch
start bluetooth-touch-flo
Sometimes the commands may take a little bit of time (no idea why honestly), but after those, you should see bluetooth start. At that point, if you still don't, fully power the device down and try again.
For whatever reason, the bluetooth scripts fail every so often, haven't been able to look into it much due to personal things IRL taking up all my time the last few months.
It's been a long while since I touched this project, but I have finally cleaned up the kernel source tree and ensured that it builds properly!
Two features that must remain disabled however are GOVERNOR_ELEMENTALX and MSM_SLEEPER as they are currently broken and do not function as of right now. The defconfig for flo also has sane defaults for the UBports Ubuntu Touch distribution (installable via the UBports installer application) and has DT2W enabled (but not turned on, that requires some extra work) by default.
You should also no longer need to disable the MSM watchdog using the instructions in the OP, running the kernel now and haven't experienced near as many random reboots I used to with the previous version! (I wonder if that was a UTouch problem, because I DO get random reboots sometimes using certain apps, but they're very rare... Then again, I'm not sure if UBports made any initramfs changes for the Flo when they added it to their system-image server, which they may have, since it's in the ubports-touch/15.04 distribution instead of their ubuntu-touch mirror for older, no-longer supported devices)
To turn on DT2W, you must follow the instructions on the github page for the 1.0.2 release.
NOTE: I highly recommend building the kernel from source rather than downloading a release! I have yet to add the current stable release to the github releases page! I also have a zip file with some helper scripts and configuration that can be installed into the UBports rootfs to turn DT2W and Kernel Samepage Merging on at startup. In case that's useful, I'm adding the zip to this post. To install, simply remount your root as read/write, extract the ZIP to / and then "chmod +x /sbin/tonokrnl-init" and reboot. Upon reaching the lightdm greeter, you should be able to shut the screen off, then double tap it to wake.
The files contained in the zip are:
/sbin/tonokrnl-init - Helper Script to start DT2W and KSM
/etc/sudoers/tonokrnl - Allows the user-session upstart config to run the helper script, which requires root.
/home/phablet/.config/upstart/tonokrnl.conf - Upstart configuration to run /sbin/tonokrnl-init using sudo (requires the sudoers file)
Off-topic slightly: The reason this project got set aside, was due to my IRL work, and because I had stopped using Ubuntu Touch and was testing out other ways of getting Linux onto the N7 'flo'. I messed with the Sailfish distribution found in the Nexus 7 2013 forum, then went to postmarketOS and messed with that (it's cool, but rather bare, not enough desktop packages to make it useful [no osk, etc]), then attempted to boot a debian distribution with the Linaro mainline kernel from John Stultz (couldn't even get X11 to start, the system did boot though! Perhaps mesa/libdrm needed recompiling with freedreno support...) and then finally came back to Ubuntu Touch via UBports!
Back on Topic, if you decide to use this kernel (either by building it yourself, or using the new UBports-1.0.3 release that will go up soon!) and install the attached helper scripts (or even find your own solution to on-boot DT2W, KSM, and the Interactive governor) please let me know your experiences! I noticed after turning KSM on that the web browser didn't crash as much, but I'm not sure if it's a placebo effect or not.
(I wonder if @flar2 has a 3.4.0 patchset I can apply rather than attempting to cherry-pick ElementalX into the kernel... That would be amazing to have ElementalX's additions to the kernel under Ubuntu Touch. [Please don't be angry I used a mention flar, I just wanted to ask if you had a patchset for the flo's kernel [version 3.4.0])