This modification is ONLY for firmwares with Android 2.2 (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 built-in ext4 and tun modules. (For lagfix and vpn support.) The lights.s5pc110.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 other features are included with?
working recovery 2e (for unsigned/testsigned update.zips - also included in the noroot packages)
ext4 support
tun support (compiled in - no module)
What Galaxy S phones are supported?
The kernel in this thread is only for i9000 and i9000m (Bell Vibrant).
If you are searching for a kernel for your phone have look at this page: Supported phones by BLN (official list)
If your phone is not listed on that page, then you may 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 already been fixed in the eclair build (in v0.9.8rc3).
Measurements on eclair 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?".
For more questions and answers have a look at the Q&A in the second post.
Instructions for installation/update:
If you have any lagfix installed, remove/disable it before installing this BacklightNotification kernel.
New method for rooted phones: 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.
Old methods for not rooted phones:
Odin/Heimdall-method (recommend):
(includes also recovery 2e)
Download:
Android 2.2.1 (JPX and newer): i9000_BacklightNotification_v2.3.2_odin.tar (md5: 8b08af1f946c2fb79d3c41aedf483e21)
Android 2.2 (JPM/JPO/JPP and older): i9000_jpm_jpo_BacklightNotification _v2.3.2_odin.tar (md5: 81e9e80c6a4a501b7d209a35dee0f0d0)
start odin
select the .tar-file for PDA
power off the phone
boot into download mode (by pressing & holding "Vol Down" + "home key" + "power key" together,
when bootlogo appears, release the keys)
plug in the usb-cable to the phone
press start in odin (DO NOT select re-partition!!!)
wait for reboot
see the Q&A "How do i enable backlight notification for ...? and install apps, if needed"
If the liblights is not properly installed you also have to apply this by recovery: bln-liblights-v1-install-update.zip
If you want to have more control over BacklightNotification:
BLN control app - blinking, call notification, scheduler and more to come
Update.zip-method (only with recovery 2e or cwm):
(You wont lose root, if rooted with cf-root or bln root .tar, includes also recovery 2e)
Download for
Android 2.2.1 (JPX and newer): i9000_BacklightNotification_v2.3.1_update.zip (md5: d13ea101a2c9a646350e012626254b99)
Android 2.2 (JPM/JPO/JPP and older): i9000_jpm_jpo_BacklightNotification_v2.3.1_update.zip (md5: 17941a7ebbe791e0599544be8d481ace)
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
see the Q&A "How do i enable backlight notification for ...? and install apps, if needed"
If you want to have more control over BacklightNotification:
BLN control app - blinking, call notification, scheduler and more to come
BackLightNotification with Universal-lagfix:
BacklightNotification v2.2 with Universal-lagfix v0.3
BLN is disabled by default in this build, you need to activate BLN by BacklightNotification settings app OR by cwm recovery.
Please use this build only until sztupy releases a new Universal-lagfix version > 0.3 .
BackLightNotification with Voodoo lagfix(-only):
Download from the project-voodoo.org website.
Support for voodoo lagfix:
xda - Discuss about Project Voodoo / lagfix, color
Removal:
Download for:
JPx and newer: "i9000-remove-bln-froyo -update.zip" (md5: 8463aa118645c5bb94a385d1ba6ff7a7)
JPO/JPM and older: "i9000-jpm-jpo-remove-bln-froyo -update.zip" (md5: 303b8e7f2f3804d3da1f937306460ec0)
(if you have the voodoo package, use the package from project-voodoo)
and continue with step 2. of the instructions above.
Credits:
supercurio (for voodoo lagfix and the kernel-update.zip-template)
chainfire (for the cf-root ramdisk)
sztupy (for universal-lagfix)
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:
ask the author of the app for notification led support
What lagfixes are supported?
Universal-lagfix by sztupy (see the this post for additionally Universal-lagfix sub-build)
"Voodoo lagfix" is compatibleand here is available
Chainfire's CFLagFix is compatible
RyanZA's One Click Lag Fix 2.0 APK is compatible
z4ziggy's z4mod is semi compatible (solution: first install bln, then patch bln kernel with z4mod and flash again)
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.
Could you add a fade feature?
That is not possible, hardware is limited (by controller firmware) to simple on/off.
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:
github: kernel: linux-2.6.32.9 | license: GPLv2
normal bln ramdisk | license: unknown (proprietary?) | author: samsung/chainfire/neldar
rooted bln ramdisk | license: unknown (proprietary?) | author: samsung/chainfire/neldar
voodoo lagfix ramdisk | license: GPLv3 | author: supercurio (Francois SIMOND)
BacklightNotification patch for froyo | license: GPLv2 | author: Michael Richter (alias neldar) | comment: bln is compatible to all Galaxy S phones, no porting needed (just enable KEYPAD_CYPRESS_TOUCH and disable KEYPAD_MELFAS_TOUCH in config)
patch 2.2 -> 2.3, in 2.3.1 a new installscript is added
Liblights for BacklightNotification | license: Apache-2.0 | author: AOSP, Michael Richter | comment: have a look at the NOTICE file (and dont activated bln by replacing liblights, the new app is able to activate bln within android.)
Chancelog:
BLN v2.3.2:
* fixed: install script not working
v2.3 (stable)
* added: blink sysfs file
v2.2 (stable)
* new sysfs interface (/sys/class/misc/backlightnotification/) - recommend update
v2.0 (stable, based on rc1)
v1.1.4 (release candidate 1)
* minor fix (typo)
v1.1.3 (beta2)
* fixed: backlight notification broken in sleep mode
* fixed: recovery broken
* fixed: pixel noise/snow during boot
v1.1.0 (beta1)
* build with Sourcery G++ Lite 2010q1
Voodoo is listed as compatible in the second post, but in the first one it says 'not yet build'. Which one is it?
woeds said:
Voodoo is listed as compatible in the second post, but in the first one it says 'not yet build'. Which one is it?
Click to expand...
Click to collapse
BLN is compatible with voodoo, but there is not yet a build of bln with voodoo available.
neldar said:
BLN is compatible with voodoo, but there is not yet a build of bln with voodoo available.
Click to expand...
Click to collapse
Ok can't wait for one, should be a great combo.
I just got Voodoo to run, and I don't want to redo everything again, so I'll hold off of this for now. But as soon as a Voodoo version is released, I'll be all over it. Thanks a lot for your great work!
just flashed "i9000_BacklightNotification_v1.1.4_RC1_odin _root.tar" on jp6. after the S i get a black screen and the 2 BLN buttons are blinking. ive already tried a reboot.. what shall i do?
/edit: i restored factory settings and now it continue with booting
I flashed the CF-Root kernel on my JP6 official Froyo (updated through Keis), so I have the 2e version Recovery. I have some questions:
1) If I use the update.zip method which you state to be no-root, will my phone be unrooted again? (I suppose so, but I wanted to ask anyway);
2) Which pit should I use to flash the root version with the Odin/Heimdall method?
3) Should I check Re-partition with Odin method and lose data? (And if not, why do we have to specify a pit?)
Thanks in advance and keep up the good work!
I'll flash when bln + voodoo is available
thunderteaser said:
I flashed the CF-Root kernel on my JP6 official Froyo (updated through Keys), so I have the 2e version Recovery. I have some questions:
1) If I use the update.zip method which you state to be no-root, will my phone be unrooted again? (I suppose so, but I wanted to ask anyway);
2) Which pit should I use to flash the root version with the Odin/Heimdall method?
3) Should I check Re-partition with Odin method and lose data? (And if not, why do we have to specify a pit?)
Thanks in advance and keep up the good work!
Click to expand...
Click to collapse
1.) if you have already cf-rooted (or used bln_root.tar) then the phone will stay rooted by using the update.zip.
may be i should rename it, to avoid confusion.
2.) Well, i dont know what happens if you not select a pit. maybe you want to try it? for jp6 i think 803 is the recommend pit file, only use 512 if you also used it to flash jp6/jpm with odin.
3.)NO, DONT select re-partition!
neldar said:
2.) Well, i dont know what happens if you not select a pit. maybe you want to try it? for jp6 i think 803 is the recommend pit file, only use 512 if you also used it to flash jp6/jpm with odin.
Click to expand...
Click to collapse
I'm on 803pit(not 100% sure here), flashed with JPK, then flashed JPM w/o repartition. Working flawlessly.
After that flashed BLN kernel, witout pit selected. Works as expected
neldar said:
1.) if you have already cf-rooted (or used bln_root.tar) then the phone will stay rooted by using the update.zip.
may be i should rename it, to avoid confusion.
Click to expand...
Click to collapse
Oh, thank you, thank you, neldar!
I used the update.zip method: it was very easy and fast and everything went smooth as silk!
I confirm that my phone is still rooted (yippie!) and I'm really really enjoying it!
2.) Well, i dont know what happens if you not select a pit. maybe you want to try it? for jp6 i think 803 is the recommend pit file, only use 512 if you also used it to flash jp6/jpm with odin.
Click to expand...
Click to collapse
Since I opted for the update.zip method, I'm also asking someone else to try it. By the way, when I flashed the CF-Root kernel through Odin I didn't have to specify a pit and, obviously, I did not select re-partition. On the other hand, Heimdall does not support repartitioning yet, but requires you to specify a pit file. I'm still confused a bit.
xan said:
I'm on 803pit(not 100% sure here), flashed with JPK, then flashed JPM w/o repartition. Working flawlessly.
After that flashed BLN kernel, witout pit selected. Works as expected
Click to expand...
Click to collapse
EDIT: Great!
3.)NO, DONT select re-partition!
Click to expand...
Click to collapse
Okie dokie! If I'll decide to upgrade to the next release through Odin, I won't select it! Though, when you already have a rooted phone and 2e recovery, I think the update.zip method is the easiest/safest/fastest!
Finally, here's my feedback: It really does what I expect it to do, and it does it pretty good! I really don't care about all the fuss on the blinking feature, I prefer a battery-friendly/lite kernel that just works. Moreover, you scored a bull's eye by adding the "Super Optimized" kernel! So far, it's a 10 out of 10!
I'm waiting for you to add Voodoo support, once it's released!
Thank you again and keep up the good work!
This works on any 2.2 firmware right?
EarlZ said:
This works on any 2.2 firmware right?
Click to expand...
Click to collapse
Yes.
I did only test jp6/jpm, but the other firmwares should also be fine.
edit: xan wrotes he tested it with jpk and it works.
Does it supported Super Optimized JPM-JP6 Kernel ?
ZaBeY said:
Does it supported Super Optimized JPM-JP6 Kernel ?
Click to expand...
Click to collapse
It says so right in the first post.
Bricked my phone
Your instructions are very confusing
First, you said this version supports FroYo.
Then you said it supports Voodoo and thanked @supercurio.
So OF COURSE i assume that means his froyo voodo lagfix is supported.
Guess what? Later on its mentioned that its not. Too late for me though, its bricked and no way to recover. Have to reflash JPM, redo Voodoo. All data gone.
Correction On Bricking
okay i didnt have to reinstall JPM, i just reflashed voodoo and it came back
aatifsumar said:
Your instructions are very confusing
First, you said this version supports FroYo.
Then you said it supports Voodoo and thanked @supercurio.
So OF COURSE i assume that means his froyo voodo lagfix is supported.
Guess what? Later on its mentioned that its not. Too late for me though, its bricked and no way to recover. Have to reflash JPM, redo Voodoo. All data gone.
Click to expand...
Click to collapse
Which method do you apply? Odin or update.zip?
Used Odin..
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.
OneClickLagFixV2PLUS inside the app is currently in RELEASE status. It has been tested on a fairly enormous number of devices without issue.
This is an APK (Normal Android App) that will install an EXT2 lag fix for you.
The APK itself can support a number of different lag fixes. It currently has the old OCLF V1 fix, which uses symlinks, and it now also has a new V2 fix which uses bind mounts.
This is in a new thead, as the old thread is very very long, and this is now version 2.
New features of the OCLF2+ lagfix vs OCLF1+
- Bind mounts are faster and require less O/S overhead than symlinks, making this fix smoother in everyday use.
- The bind mount allows for Android to report the correct free space available.
- If something goes wrong at boot, and the bind mount does not initialize, you will boot up to a copy of your data from before the lagfix was applied. This makes V2 safer than V1. (copying /system/bin/playlogosnow onto /system/bin/playlogos1 will effectively restore your device to how it was before you applied the lagfix. There is also an undo option, which will copy all of your changed data back to RFS before restoring.)
- As a bonus, an option to set the wifi screen off timeout is included.
How to use this:
Copy over the APK file onto your phone, and run/install it as normal using 'My Files'. There will be a 'One Click Lag Fix' app installed. Run that, and select the option you want!
The app will automatically kill all running tasks, and enable flight mode. You should probably not use the device while the lag fix is running. If you accidentally hit back or home by mistake, re-enter the app and re-select the lag fix. It should still be running.
Known issues in 2.0.0
Some devices with heavy carrier customization cannot install EXT2 Tools. Fix should be in the next version, if possible.
On Froyo (Android 2.2) this lag fix will refuse to install if the apps2sd feature is in use. The error you will see if Apps2SD is in use on installation will be that the loopback cannot be mounted.
Workaround: In order to install the lagfix on froyo, you will need to set each app that is on the external SD back to regular. Once the lagfix is installed, you can move apps back to the SD.
Fix should be included in the next version, if possible.
If you use up more space inside the EXT2 than is available outside the EXT2, you will have to remove apps/delete data until you have enough space to copy your data back when you want to uninstall. To help avoid this, don't set the space bar all the way on the far right.
Supported Devices And Firmwares
Root support is available for:
- I9000 Galaxy S on Android 2.1
- Captivate on Android 2.1
- Vibrant on Android 2.1
Other devices / Android versions will have to use a different method to root
Lagfix support is available for:
- I9000 Galaxy S on All Firmwares
- Captivate on All Firmwares
- Vibrant on All Firmwares
- Fascinate on All Firmwares
2.0.1 - 2.0.4 Changelog
- Fixed WifiTimeout option to work on Froyo
- Fix for OCLFV1 undo.
- Sync is called before bind-mounting, to ensure no data is lost.
- Fix for APPS2SD error (loopback can't be linked error)
2.0.5 Changelog
- Fixed WifiTimeout to work on strange firmwares without a system.system
2.1.0, 2.1.1Changelog
+ Lagfix V2+ has been updated to V2.1+ which features enhanced data security
In order to install it, you must first undo V2 using the option, and then install V2.1+ as usual
- Fixed WifiTimeout to now correctly require EXT2 Tools
- Fixed Cleanup option to now correctly clean up the V2 lagfix as well as V1
- EXT2 Tools will now remount /system as read-write
- Changelog included in app for market users
2.1.2 Changelog
- Fixed 'Restore Bootlogo' option to work correctly when V2 lagfix is installed.
- Fixed 'Restore Bootlogo' option to restore the froyo bootlogo if running froyo.
2.2.3 Changelog
+ Lagfix updated to V2.2+ which contains:
- Fix for new Vibrant, and I9000 JJ1 firmware.
- Fix for the timezone issue.
~ To Install V2.2+, use the undo V2 function, and then re-do with V2.2+
+ Kernel Installer (ALPHA) that allows you to easily flash a kernel to your device
2.2.4 Changelog
- Fix for menu->help button opening kernels page.
- Minfree now shows current settings
- Set scheduler now shows current settings
- Set scheduler now has an option to apply tweaks from hardcore on XDA forums
- Text cleanup
- Fix for occasional crash on fetching kernel manifest
2.2.8 Changelog
- Galaxy Tab Support
- Fix for installing with APPS2SD active
- Fix for set-on-boot for minfree and scheduler/tweaks
2.3.0 Changelog
- Bug fixes for occasional 'Broken Pipe', as well as related failure to copy boot up scripts.
- z4root option added, which opens the market to the z4root app.
- update.zip root option now downloads update.zip instead of having it included.
- Fix for typo in cleanup option, it should now work correctly
Rooting Froyo
Froyo's recovery mode is locked down, so you can't root it from your device.
However, you can use this: http://forum.xda-developers.com/showthread.php?t=803682
Donations
Since a lot of people have been asking, I set up a paypal account and got a donate link: https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
Feel free to donate if you want, but I'm happy if you don't donate too.
Full source code under the GPL is available from http://code.google.com/p/oclf/
Nice work! Will test it soon!
Sent from my GT-I9000 using XDA App
Very nice, thanks, will try it asap
Now downloading to test. I hope it will be great work.
Damn! Just when I decided to try out the stock firmware without any lagfixes. :-| Guess I have no choice but to succumb to your awesomeness now.
Will make a backup of data on my internal memory (just in case) and give this a shot on my brand new JM8 now
Sent from my GT-I9000 using XDA App
Hang on, looks like it has a bug! I did a clean firmware flash, and its just giving a 'disabled' message, because it seems to be erroring on trying to find /dbdata/ext2data/
I'll have a 2.0.1 up within a few minutes with the fix. Sorry! I need a QA department!
Good work!
Do we need to uninstall APK v1 before using this APK?
I guess yes, but you never know.
Thanks
Is this the app version of "voodoo" fix only with ext2 (the one you started testing earlier in different topic) or its old virtual file method?
Hmm, can't find the lagfix
Thx for readding it
lol ^^
Will report back in a few minutes
RyanZA said:
Hang on, looks like it has a bug! I did a clean firmware flash, and its just giving a 'disabled' message, because it seems to be erroring on trying to find /dbdata/ext2data/
I'll have a 2.0.1 up within a few minutes with the fix. Sorry! I need a QA department!
Click to expand...
Click to collapse
2.0.1 is up in the first post. If you downloaded 2.0.0 and noticed that it didn't work, grab that one.
Steephig said:
Good work!
Do we need to uninstall APK v1 before using this APK?
I guess yes, but you never know.
Thanks
Click to expand...
Click to collapse
You don't need to uninstall APK v1 first. It will overwrite it.
V1 lagfix will need to be uninstalled first, but the uninstall can be done by either V1 or V2 APKs.
dupel said:
Is this the app version of "voodoo" fix only with ext2 (the one you started testing earlier in different topic) or its old virtual file method?
Click to expand...
Click to collapse
Virtual file method, but better.
RyanZA said:
You don't need to uninstall APK v1 first. It will overwrite it.
V1 lagfix will need to be uninstalled first, but the uninstall can be done by either V1 or V2 APKs.
Click to expand...
Click to collapse
I phrased my question a bit weird, what I meant to say was if the v1 lagfix should be uninstalled, but you gave the answer anyway.
Nifty!
Can I try it this in 2.2 JPH?
Thanks...
halabibk said:
Can I try it this in 2.2 JPH?
Thanks...
Click to expand...
Click to collapse
It was deved this evening now, completely in JPH. So yeah, JPH works. If anything else works is unknown!
Also, the wifi timeout option does not work in 2.2, only in 2.1 Android. I'll put the fix up with whatever other bugs people find in a bit.
halabibk said:
Can I try it this in 2.2 JPH?
Thanks...
Click to expand...
Click to collapse
Tried it on my sluggish JPH.
Now it's blazing fast!
Very nice RyanZA.
THX!
Now my JPH firmware seems to be as fast as JM6 with Voodoo fix
Dennis
Thanks, another Q? actually I am using CFLagFix 1.80, still can use this?
Got an error (running XXJPH):
"Could not link loopback device /dev/loop0 to /dbdata/rtssdata/ext2/linux.ex2! loseup: /dev/loop0"
Damm i chose to upgrade the app from 1.6.7 but there are no install options am i missing something ? when i open the app no options to install anything
wifi timeout defo not working on 2.2 JPH
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.
[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.
I've created a custom ROM based on the S5660XXKS5 stock ROM that has the following changes / features:
Custom kernel:
Overclocking using SetCPU (stable for me at 883MHz but frequencies up to 1GHz are provided).
TUN driver (for OpenVPN).
EXT3/4 filesystem support (useful for DT Apps2SD).
CIFS (SMB) filesystem support to mount windows shares over WiFi (or 3G + VPN).
Support for swap.
SmartassV2 and interactive cpu frequency governors (enable them using SetCPU).
Other modifications:
DT Apps2SD pre-installed.
Enabled native SIP calling.
The openvpn binary so you won't have to use OpenVPN Installer.
Rooted (includes ChainDD's Superuser 3.0 and the latest su binary).
CRT animation (enable animations from the display settings to enable).
Disabled fully charged notification (still visible on the lock screen).
init.d subsystem.
Juwe11's ram script.
Re-odexed (optional) and zipaligned for speed and save space in /data.
Added busybox and sqlite3.
GPS fix speed fix (hopefully).
Updated/added Chrome to Phone, DSP Manager, Gmail, Maps, Market, Music (from Ice Cream Sandwich), Samsung Apps, Talkback, Voice Search, YouTube.
Removed unwanted Samsung apps (Hangman, Book Store, Music Store).
Distinctive features inherited from the stock rom:
Overscroll glow.
Compass appears to be working without patches.
Notes:
If you're experiencing problems with the new Market application, clear its settings and cache.
This ROM doesn't have a boot animation. Somehow it doesn't stop showing the animation at the end of the boot sequence so I've disabled it. As a positive side-effect, it shaves a couple of seconds off the boot time.
To prevent you from doing silly things, this ROM will wipe the dalvik-cache on first boot and then reboot.
Downloads:
The latest beta is available from my website, Particle Android.
*reserved*
Hello, congratulations for the excellent work you have done and are doing ...
you may also adding to it a "theme chooser" as in Cyanogen? bye
.:AbboZ:. said:
Hello, congratulations for the excellent work you have done and are doing ...
you may also adding to it a "theme chooser" as in Cyanogen? bye
Click to expand...
Click to collapse
I'll look into it but from what I recall this requires some very rigorous changes in the framework.
great rom i wonder why the boot animation wont work/isnt changeable. i've tried changing the boot splash image in the recovery.img (gio.rle) but wasnt sure how to replace the modified recovery.img. anyhow keep up the good work!
.:AbboZ:. said:
Hello, congratulations for the excellent work you have done and are doing ...
you may also adding to it a "theme chooser" as in Cyanogen? bye
Click to expand...
Click to collapse
and maybe cf-root also
hyriand said:
I'll look into it but from what I recall this requires some very rigorous changes in the framework.
Click to expand...
Click to collapse
Thank you. .. if you could do that would be great! again congratulations ... great rom!
bromhexine said:
great rom i wonder why the boot animation wont work/isnt changeable. i've tried changing the boot splash image in the recovery.img (gio.rle) but wasnt sure how to replace the modified recovery.img. anyhow keep up the good work!
Click to expand...
Click to collapse
The problem is not that it won't start (I deliberately disabled it), the problem is that it won't stop.
klebengan said:
and maybe cf-root also
Click to expand...
Click to collapse
cf-root? what's that?
hyriand said:
cf-root? what's that?
Click to expand...
Click to collapse
CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod (CWM3) recovery.
.:AbboZ:. said:
CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod (CWM3) recovery.
Click to expand...
Click to collapse
Why would I want to do that?
hyriand said:
cf-root? what's that?
Click to expand...
Click to collapse
already answered. hehehe
Boh...are all things that are already included
.:AbboZ:. said:
Boh...are all things that are already included
Click to expand...
Click to collapse
i just realized that bro
.:AbboZ:. said:
Boh...are all things that are already included
Click to expand...
Click to collapse
Actually, not everything. I don't enable insecure ADB on normal boot, but that's a deliberate choice. As the name implies, it's insecure.
hyriand said:
Actually, not everything. I don't enable insecure ADB on normal boot, but that's a deliberate choice. As the name implies, it's insecure.
Click to expand...
Click to collapse
and with cf-root kernel we can use the tweak manager.
Hi hyriand, I am loving your Particle Rom so far! However, I am a GT-5660M User (Bell Canada version of Gio). Seeing as the modem that you include in your particle rom isn't really compatible, I made my own ODIN-flashable modem file for use with our Bell phones. It is the AMSS file extracted from the original Bell 2.3.4 firmware.
Perhaps you can incorporate it into a future version of your rom? Since I cannot post links yet.. you will find a PM in your inbox with it
On another note, I have a few suggestions for some features that I think would be very nice to have:
1.) For overclocking, if we had voltage control with setcpu over the kernel, perhaps overclocking to 900Mhz-1Ghz would be more realistic?
2.) BLN (backlight notification) support. Other phones such as Samsung Galaxy S, Nexus S have support for this in the kernel. It would make for a very nice indicator for new notifications while the phone is sleeping.
3.) Voodoo Sound (if the phone has an appropriate headphone amplifier chip?).
4.) Automatic Screen Brightness Dimming (This would require an ambient light sensor, does our phone even have one?).
5.) Battery Percentage Level in Notification Bar. Simplygio 1.3 has this for example.
xspartany said:
Hi hyriand, I am loving your Particle Rom so far! However, I am a GT-5660M User (Bell Canada version of Gio). Seeing as the modem that you include in your particle rom isn't really compatible, I made my own ODIN-flashable modem file for use with our Bell phones. It is the AMSS file extracted from the original Bell 2.3.4 firmware.
Perhaps you can incorporate it into a future version of your mod? Since I cannot post links yet.. you will find a PM in your inbox with it
On another note, I have a few suggestions for some features that I think would be very nice to have:
1.) For overclocking, if we had voltage control with setcpu over the kernel, perhaps overclocking to 900Mhz-1Ghz would be more realistic?
2.) BLN (backlight notification) support. Other phones such as Samsung Galaxy S, Nexus S have support for this in the kernel. It would make for a very nice indicator for new notifications while the phone is sleeping.
3.) Voodoo Sound (if the phone has an appropriate headphone amplifier chip?).
4.) Automatic Screen Brightness Dimming (This would require an ambient light sensor, does our phone even have one?).
Click to expand...
Click to collapse
about BLN, i think we can add it to kernel. squadzone has posted the config of kernal ext3/4 & BLN support.
about auto dimming, i think our phone doesn't have light sensor
can u make kernel with Undervolt feature bro Hyriand?
i think its very usefull for battery life
and i've question about smartassV2.
this governor will automatic reduce the max & min clock when the screen off right?
when i use my phone for 10 min for sms & chat my phone temp reach 40 celcius
and i check the processor clock with setcpu, the clock is often in max clock
i think better conservative governor than smartassV2 for clock management when the phone screen is not turn off
how do u think hyriand?
who have better clock management between smartassV2 and conservative?
I just noticed that this is on GB 2.3.4. I thought I read somewhere that it was at 2.3.5? Just checking in case I FUBARed.
xspartany said:
Hi hyriand, I am loving your Particle Rom so far! However, I am a GT-5660M User (Bell Canada version of Gio). Seeing as the modem that you include in your particle rom isn't really compatible, I made my own ODIN-flashable modem file for use with our Bell phones. It is the AMSS file extracted from the original Bell 2.3.4 firmware.
Perhaps you can incorporate it into a future version of your rom? Since I cannot post links yet.. you will find a PM in your inbox with it
On another note, I have a few suggestions for some features that I think would be very nice to have:
1.) For overclocking, if we had voltage control with setcpu over the kernel, perhaps overclocking to 900Mhz-1Ghz would be more realistic?
2.) BLN (backlight notification) support. Other phones such as Samsung Galaxy S, Nexus S have support for this in the kernel. It would make for a very nice indicator for new notifications while the phone is sleeping.
3.) Voodoo Sound (if the phone has an appropriate headphone amplifier chip?).
4.) Automatic Screen Brightness Dimming (This would require an ambient light sensor, does our phone even have one?).
5.) Battery Percentage Level in Notification Bar. Simplygio 1.3 has this for example.
Click to expand...
Click to collapse
Well, as long as the baseband is sort of compatible, flash the update.zip using ClockworkMod Recovery (CWM works on S5660M, right?). If that doesn't work, I'll create a Particle ROM based on the ROM you sent me.
Voltage control seems to be managed by the CPU itself. I'm already looking into controlling it to undervolt it for the lower frequencies.
I'll look into BLN, Voodoo Sound and brightness control (maybe the proximity sensor can be abused, no idea how that works).
I like the battery level indicator the way it is (I'm not really into theming), but feel free to install the deodexed version of Particle and customize that with uot kitchen.