Hey guys... I am sorry to interrupt your work or anything u were doing (which I don't understand) but, could u in next release fix sensivity in home button in the recovery menu? I always press it quickly but it sometimes makes two selections and for example if u want to make a restore, u press Backup/restore and it makes u a backup directly... Would be great to fix that. Im sorry for the offtopic, I imagine u have more important things to develope on.
[KERNEL & CF-root][GB][LE4/Universal] Bam Custom Kernel: BCK beta 15 [07.02.13]
- Thread starter XDA_Bam
- Start date
-
- Tags
- development
I already found a patch for this some time ago, but it cannot be applied directly, because the code is from the i9100 (SII). But I will look into it, now.
As a workaround, you can use the menu key to select an option.
Since you are having issues with the recovery.. I have a suggestion.. Why dont you use Skins Recovery? Everything works in it... I.e ramdisk from ganeshbiyers Cf-Root ..
Sent from my GT-I9003 using xda premium
Legitimate question. The main reason is, that it's not universal by default. We could add this feature, but by now, our modifed version of amit's CF-root should be equally bug-less as Skin's
and we almost fixed all the problems
If you find any bug, post it here.
@XDA_Bam
Now I'm sure it's better to leave "mount --bind", in this way you can umount and mount /emmc from CWM. Doing the change I proposed let you to umount both, but you can't mount them (you can through adb).
Here my doubt. With this config, you are allowed to umount /emmc (internal) and not /sdcard (external). Do you think is good as it is or we should "swap" them?
EDIT:
After I hit "Submit reply" I realized that CWM is primarly designed to work with the external SD, so it's better to leave it like this.
Sorry for the mess with the two posts.
I'm still doing some tests.
Last edited:
i just flashed this a few moments ago and noticed the issue with the home button
just a suggestion? why was touch recovery not used for it? it was somehow useful to avoid over usage of hard buttons
just a suggestion? why was touch recovery not used for it? it was somehow useful to avoid over usage of hard buttons
I'm discovering more and more stuff.
I understood where the mount problem was. vfat doesn't support the check option (=>Invalid argument error).
That's why I could mount /sdcard and /emmc from adb but not from CWM.
CWM uses /etc/recovery.fstab, while if you simply mount from adb, /etc/fstab is the file used (yes, it's generated from recovery.fstab, but the check option is removed).
Does anyone know what is this used for?
https://github.com/XDA-Bam/samsung_...F-root_universal/sbin/postrecoveryboot.sh#L19
I removed it from my ramdisk and I had no problems. Actually I commented all the lines in that file, except the last one (umount /dbdata, I don't know why it's there).
I think amit added this script because without it he couldn't do any backup, at least without mounting /emmc and /sdcard through adb shell.
This is the new res/etc/recovery.fstab
The [decive2] field is not useful for us, so I removed it. If you try to backup into the external SD when there's no SD, it simply won't work. (the backup starts anyway). In this case you should get this:
By the way the first solution (the old recovery.fsta) worked because I swapped /sdcard and /emmc in a tricky way.
Now you can mount/umount and do your backups without problems.
I understood where the mount problem was. vfat doesn't support the check option (=>Invalid argument error).
That's why I could mount /sdcard and /emmc from adb but not from CWM.
CWM uses /etc/recovery.fstab, while if you simply mount from adb, /etc/fstab is the file used (yes, it's generated from recovery.fstab, but the check option is removed).
Does anyone know what is this used for?
https://github.com/XDA-Bam/samsung_...F-root_universal/sbin/postrecoveryboot.sh#L19
I removed it from my ramdisk and I had no problems. Actually I commented all the lines in that file, except the last one (umount /dbdata, I don't know why it's there).
I think amit added this script because without it he couldn't do any backup, at least without mounting /emmc and /sdcard through adb shell.
This is the new res/etc/recovery.fstab
The [decive2] field is not useful for us, so I removed it. If you try to backup into the external SD when there's no SD, it simply won't work. (the backup starts anyway). In this case you should get this:
By the way the first solution (the old recovery.fsta) worked because I swapped /sdcard and /emmc in a tricky way.
Now you can mount/umount and do your backups without problems.
Last edited:
Cool. Gonna include this in the next release.
Request: If you want to test the bluetooth HID support, please flash beta 13rc5. You should be able to connect any BT mouse and keyboard to your phone.
Last edited:
@DooMLoRD
Let users with no external SD to finish their backups without errors (it doesn't matter if you backup into external or internal SD)
The error:
The problem is that there's an error in res/etc/recovery.fstab (check=no - vfat partitions). This error won't let CWM mount /emmc and /sdcard.
amit fixed it forcing the mount with /sbin/postrecoveryboot.sh (as the name says, it is executed right after recovery boot), but I think he didn't consider the users with no external SD. Moreover you can't unmount /sdcard if you first don't unmount /sdcard/.android_secure.
That said, my question is: do we still need this script? https://github.com/XDA-Bam/samsung_...sk_CF-root_universal/sbin/postrecoveryboot.sh
I'm sure the first two lines (mount etc) are useless. The problem is the rest. I think those lines could only give problems (starting from line 12, except the last one).
I don't know what happens if we leave this script as it is, I tried to do a backup with only the last line and for today no more backups and tries.
Let users with no external SD to finish their backups without errors (it doesn't matter if you backup into external or internal SD)
The error:
Code:
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory
Unable to find mounted volume: /sdcard
Error finding an appropriate backup handler.The problem is that there's an error in res/etc/recovery.fstab (check=no - vfat partitions). This error won't let CWM mount /emmc and /sdcard.
amit fixed it forcing the mount with /sbin/postrecoveryboot.sh (as the name says, it is executed right after recovery boot), but I think he didn't consider the users with no external SD. Moreover you can't unmount /sdcard if you first don't unmount /sdcard/.android_secure.
That said, my question is: do we still need this script? https://github.com/XDA-Bam/samsung_...sk_CF-root_universal/sbin/postrecoveryboot.sh
I'm sure the first two lines (mount etc) are useless. The problem is the rest. I think those lines could only give problems (starting from line 12, except the last one).
I don't know what happens if we leave this script as it is, I tried to do a backup with only the last line and for today no more backups and tries.
@XDA_Bam ... could you include touch recovery too on your next release? it might be a solution to the home button problem. or is it causing issues on the kernel thats why you didnt implement it?
I don't know why he didn't use the touch version, but this one is good for me. If you need the touch version just because of the home button read this: http://xdaforums.com/showpost.php?p=24812529&postcount=502
@XDA_Bam
sbin/postrecoveryboot.sh is not needed, even the last line. You can comment everything. /dbdata didn't even exist before my fix_permissions fix, this version of recovery uses /datadata.
It's a video de-/encoding co-processor. It helps e.g. with encoding the video captured by the camera. We had problems with choppy videos when adding the 1.2 GHz step for the first time, because in the original patch, the IVA was clocked down to 65 MHz when OPP5 was engaged. The system couldn't handle the video bitstream and "choked" on it. After adjusting IVA frequency to 840 MHz, everything was fine again.
@All: If you want bluetooth HID support, test it !
is this normal? or is it just me?
i just recently installed this beta 12 kernel with CF root
before i did i flashed to XXKPE then DXKP9 which is standard stock in my country
then i flashed this kernel with CF root
wiped everything ... cache ... dalvik cache ... battery stats
the just installed the basics, go launcher , no games, no heavy apps as i was testing it still
i set everything as is by default
drained the battery yesterday and fully charged it in "off" state
its was full charged around 11:30 pm then i turned on my phone
as it was too late i went directly to sleep
when i woke up this morning 9:00 am
batt is already 81% and wasnt used
so should i changed governors or schedulers?
but from full to 81% in 9 hours 30 mins without use ... it really is draining fast
EDIT:
i notice "maybe" cause of my fast battery drain ... before i was on stock for long time, no kernel and CF.root installations. my network signal is normally 3-4 bars. but after installing kernel i been getting 0-2 bars only on my network. 30 mins ago i tried using the network tweak that goes with the CWM ... still i get 0-2 bars.
i just recently installed this beta 12 kernel with CF root
before i did i flashed to XXKPE then DXKP9 which is standard stock in my country
then i flashed this kernel with CF root
wiped everything ... cache ... dalvik cache ... battery stats
the just installed the basics, go launcher , no games, no heavy apps as i was testing it still
i set everything as is by default
drained the battery yesterday and fully charged it in "off" state
its was full charged around 11:30 pm then i turned on my phone
as it was too late i went directly to sleep
when i woke up this morning 9:00 am
batt is already 81% and wasnt used
so should i changed governors or schedulers?
but from full to 81% in 9 hours 30 mins without use ... it really is draining fast
EDIT:
i notice "maybe" cause of my fast battery drain ... before i was on stock for long time, no kernel and CF.root installations. my network signal is normally 3-4 bars. but after installing kernel i been getting 0-2 bars only on my network. 30 mins ago i tried using the network tweak that goes with the CWM ... still i get 0-2 bars.
Last edited:
because some people didnt like touch CWM, including me
even with touch recovery you could still use the hardware buttons, those small 4 screen buttons doesnt block the screen of CWM Recovery
but it take more space on screen, so i cant see the file name clearly.even with touch recovery you could still use the hardware buttons, those small 4 screen buttons doesnt block the screen of CWM Recovery
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
126BCK - Bam Custom Kernel for i9003 / Galaxy SL
This Kernel is based on the Chinese GB source, released by Samsung on the 18th of November. Last changes to the source were made by Samsung on November 15th. If you still have questions after reading this post, look at the FAQs (including a list of requested features and known issues).
Kernel features:
- No SOD
- Bugfixes:
~ Sync bug fixed. Notifications for new mails and messages should arrive within one minute under all circumstances
~ Bluetooth problems fixed. Your phone now should play nice with bluetooth hosts, i.e. your car audio system
~ Micro stutters nearly completely gone thanks to lowered processor transition latency. It's smooooooooth
~ Home button double presses exterminated - Governors:
~ smartassV2 governor by erasmux (default)
~ interactive governor by Mike Chan - IO scheduler:
~ SIO IO scheduler by Miguel Boton (default)
~ BFQ IO scheduler by Paolo Valente and Fabio Checconi
~ deadline IO scheduler - Extended features:
~ ro.secure=0 (root acces through adb shell - to root the 'clean flavour' of BCK, please follow the instructions)
~ EXT4 support (to convert your file system, use amit.bagaria's ext4 add-on .apk) (Only in CF-Root .tar)
~ Support for init.d scripts (to use scripts, please follow the instructions) (Only in CF-Root .tar)
~ BLN support (to use BLN, please follow the instructions)
~ TUN support for VPN networks built-in (no module needed)
~ Increased SD-card read ahead of 768 kb for improved read speed
~ Available with universal CF-root ramdisk based on amit.bagaria's version, improved by loSconosciuto (Only in CF-Root .tar)
~ Available with universal CWM ramdisk (rooted) based on universal CF-root, but 'tweakless' (Only in CWM .tar) - Overclocking and Voltage:
~ Evolved sysfs interface for variable overclock or underclock (all operating points [OPPs] can be adjusted seperately)
~ Fifth OPP (1.2 GHz) available, device booting up at stock speed (1 GHz)
~ Total frequency control. The device will never run at higher speeds than defined by you, not even on WiFi.
~ sysfs interface for voltages (read only at the moment)
~ Slight undervolt (3%) on all OPPs
Flashing , settings and compatibility:
If you want to use BCK, please flash it on a clean stock ROM. If you want to go back to stock, repartition and reflash the full firmware with ODIN. This kernel will not work on CM or MIUI.
The CF-root and CWM versions (PDA_BCK_CF-root_universal_***.tar / PDA_BCK_CWM_universal_***.tar) can be flashed on any recent Gingerbread firmware. These versions are pre-rooted, which means they include Superuser.
The non-CF-root "clean" version (PDA_BCK_XXKPQ_***.tar / PDA_BCK_XXLE4_***.tar) will only work on XXKPQ / XXLE4. Do not flash this version on anything other ROM than the one indicated in the file name. This will break your WiFi. It's especially risky to flash the clean version of BCK after flashing any CF-root kernel before. Don't do it. This version does not include Superuser, but it is prepared to be rooted. Follow the instructions to do this.
After a kernel update, please wait for the device to boot up and reboot once. There is generally no need for cache cleaning or a full reset. To change the governor and IO scheduler, I use NoFrills CPU Control from the market. It's free and reliable.
I recommend to use the clean XXKPQ version. If you want / need to have root, try the CWM version. If you want the 'full package' with FuGu-Mod and more, use the CF-root. I recommend that you do not apply any further tweaks and use a stock ROM.
>>> Warning: Overclocking may damage your device. <<<
Overclocking instructions:
For overclocking, you will need a shell on your phone, or adb access. I use Android Terminal Emulator. Overclocking is currently limited to certain frequencies (see below) and all operationg points will be set with the stock voltage of the corresponding stock frequency. The frequencies you set have to be within the following ranges:
Remember that your phone uses all operating points depending on the current load. Anything more than 10% higher than the highest stock frequency is likely to be unstable, but you are free to try it. To change the clocks, open Terminal Emulator (or type 'adb shell') and hack inCode:OPP1: 100 - 500 MHz, stock 300 MHz OPP2: 501 - 700 MHz, stock 600 MHz OPP3: 701 - 900 MHz, stock 800 MHz OPP4: 901 - 1100 MHz, stock 1000 MHz OPP5: 1101 - 1500 MHz, stock 1200 MHz, not used by default
as an example. The others are opp5, opp3, opp2 and opp1. That's it.Code:su echo "1100" > /sys/power/overclock_opp4
Settings will be lost at reboot, unless you add them to your init.d scripts. I do not recommend this, as this may cause boot loops if the settings are to high! Be advised that NoFrills CPU Control, SetCPU, or whatever app you use that may adjust clock settings interfers with this. You may wanna update their settings after this. I do not recommend using them to set anything at boot if you overclock any OPP, because they might save the wrong frequencies and crash or do worse.
Changelog:
Credits:
Credits go to the mentioned developers of the cpufreq governors, ganeshbiyer, skin1980 and amit.bagaria for the CF-Root and skin1980 for his repack script. Many thanks to DooMLoRD, amit.bagaria, knzo and loSconosciuto for their help! BCK sources are available on GitHub.
Files:
Attached files:
- ODIN-flashable PDA_BCK_XXKPQ_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXKPQ ROMs.
- ODIN-flashable PDA_BCK_XXLE4_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXLE4 ROMs.
- ODIN-flashable PDA_BCK_CF-root_universal_***.tar with CF-root ramdisk ('Universal CF-root flavour'). For all current Gingerbread ROMs.
- ODIN-flashable PDA_BCK_CWM_universal_***.tar with CWM (rooted) ramdisk ('Universal CWM flavour'). For all current Gingerbread ROMs.
Old releases and release candidates can be found on Dev-Host. Use these with caution!
MD5 sum:
26UPDATE: BCK beta15 is up. This version is mostly identical to beta15rc8, but is compiled with the user_defconfig. That means there is less debug stuff in there than in the rc releases. Go for it!
On a side note, this may very well be my final release. I've had very little time these past months to maintain the kernel. I know there are some annoying bugs left, but I currently do not know how to fix them and probably won't have the time to learn how to. Therefore, I can only encourage everybody to try it themselves! My full sources are on Github and since this is open source, everybody is free to join or take over the development
It was always a pleasure sharing with you. Stay positive
Changelog:
beta 15:
- Universal CF-Root: Modified some permissions to bring it closer to the stock ramdisk
- Universal CWM: Created a CWM ramdisk based on CF-root, without most tweaks. You now have three BCK flavours to choose from
- Updated to newest UPDATE2 sources by Samsung
- Sync bug fix reworked to use new Samsung method from UPDATE2. This may lead to slightly lower standby battery consumption.
- Fixed accidental front camera mirroring
- Editing smartassV2 settings with busybox 1.20.x and newer no longer leads to reboots. Thanks to loSconosciuto for pointing me to the patch.
- Fixed complete crash of WiFi driver when activating WiFi by adapting smartassv2 thresholds
- Reverted to the original Google Android toolchain using gcc 4.4.3
- Because of the toolchain-switch, the compiler optimizations are now back to -O2 instead of -O3
18UPDATE: Beta 13 is up. There are some huge improvements to the user experience in this one, and - also thanks to loSconosciuto's help - some rather annoying bugs are gone. Test it - you won't regret it!
If there are no major issues with this release, the next one's gonna be 1.00.
Changelog:
beta 13:
- Updated sources to GT-I9003_SWA_GB_Opensource_Update1 from the 30th of March
- Universal CF-Root: Backup is not failing anymore when started from CWM. Thanks to loSconosciuto.
- Universal CF-Root: Some small improvements to multiple scripts.
- Home button double press issue fixed. There should be no more unwanted double selections in CWM and you can now reliably long press the home button to bring up the list of previously used apps. Idea and timer function taken from a patch by Tegrak.
- Fixed priority class for CONTENT_PROVIDER not being set, which may have caused apps of this class to be ignored by the autokiller, resulting in less free RAM.
- Lowered OMAP processor transition latency to the value recommended by TI. Subjectively, this brought huge improvements in terms of reducing micro stutters.
- Lowered CFS scheduler latency and granularity to values very close to mainline kernel defaults. This could reduce lags in some critical situations, but it doesn't do wonders.
- Switched to SIO as default IO scheduler.
17UPDATE: beta 14 is up! For everybody using the ValuePack (XXLE4): The CF-root version of BCK will now root your device without breaking the WiFi. For everybody else, I recommend that you read the changelog and update as soon as you're comfortable
Changelog:
beta 14:
- Universal CF-Root: Replaced CWMManager and TweakManager with zipaligned files. Thanks to loSconosciuto.
- Universal CF-Root: The TweakManager is not replaced on install if it didn't change to preserve it's settings. Thanks to loSconosciuto.
- Universal CF-Root: Corrected problems because of too little free space in /system when converting to ext4 by permanently moving InfoAlarm.apk from /system/app to /data/app. Thanks to loSconosciuto.
- Universal CF-Root: Fixed the non-working WiFi on XXLE4 and prevented future problems. Instead of patching the WiFi modules, they are now replaced. Thanks to loSconosciuto.
- Universal CF-Root: Fixed some small mistakes in the CF-root install procedure.
- Switched the compression of ramdisk and kernel from gzip to lzma. This makes the files much smaller and allows us to include more 'stuff'.
- Changed smartassV2 settings to wake up at lower frequencies. Further, it is not locked at 300 MHz anymore when the screen is off. Tests showed that free scaling is more battery friendly.
- Removed InteractiveX and OndemandX governors and added the Interactive governor by Mike Chan (Source: CyanogenMod Crespo kernel). Since free scaling proved to be more battery friendly, the screen off profiles in InteractiveX and OndemandX made them superfluous.
- The device will not scale above 1 GHz for some seconds when booting anymore. It's now safe to use BCK even if your device can't handle 1.2 GHz. Based on a patch by dalingrin.
- Changes in PM to respect cpufreq policy limits when playing or recording video. The device should respect your wishes under all circumstances, now
- Fixed the SmartReflex voltage calibration of the OMAP SoC for OPP5. This could lower power consumption as soon as OPP5 (1.2 GHz) is activated for the first time.
- Slight increase in the OPP5 nominal voltage (1.40 V -> 1.42 V) to allow for some adjustment by SmartReflex (now that it's working...), if necessary. The actual voltage when the device is running will not change for most users! Based on patches by dalingrin and Sanjeev Premi.
Code:stock BCK OPP5: not def. 1.4200 V
PS: If you're missing Lionheart or Lulzactive, look into the FAQ.16UPDATE: Please feel free to test BCK beta 15rc7 in the Universal CF-root flavour or with Universal CWM. I recommend that you flash the flavour you have currently installed (i.e. use CF-root if you currently use CF-root). There are only very small changes compared to beta 15rc6 and so far, no serious problems have been reported with the latter release. A backup is recommended none the less. I hope to have fixed most WiFi problems with this rc, although it might still hang from time to time when acquiring an IP address.
Let me know if this release solves the WiFi problem for you (and if you had it before)
Changelog:
- Possibly fixed complete crash of WiFi driver when activating WiFi
- No SOD
