Database Users

[DEV][WIP][Recovery]PX Custom Recovery 0.3.6[BETA][Last: Mar 16, 2012][Tester Needed]

PX Custom Recovery - For cooper
I am not responsible for any damage to your phone
Tempoary only for devs.
i dont have cooper device to test it.
please report if u found bugs
​
NB: This Recovery is still on beta. maybe not all feature working properly. please report me if u found a problem
NB: IF U A NOOB, DONT FLASH IT UNTIL SOME DEVS SAY IT FULLY WORKING ON COOPER
Well, this is only Modification of ClockworkMod Recovevry with many change, support onscreen button touch, Themes & many more
Feature:
Touchscreen Support thanks to Napstar
Reconfigure & Redesign UI
More color & Better Image quality
Reboot menu
Set brightness level
Charging on recovery
push apk to system (unfinished)
Touch Event only if onscreen button touched
Timezone Settings
auto save & load setting
Partition info
Themes
more (please give me suggesion about new feature)
Here's temporary menu tree this recovery for v0.3.2
Code:
- reboot system now
- reboot menu
- reboot to system
- reboot to recovery
- reboot to download mode
- wipe & factory reset
- wipe cache
- wipe data (factory reset)
- wipe dalvik cache
- wipe battery stats
- mount menu
- mount/unmount /cache
- mount/unmount /data
- mount/unmount /system
- mount/unmount /sdcard
- mount/unmount /sd-ext
- mount/unmount USB storage
- format menu
- format /cache
- format /data
- format /system
- format /sdcard
- format /sd-ext
- Install zip from sdcard
- choose zip
- apply /sdcard/update.zip
- tonggle signature
- tonggle script assert
- backup & restore
- backup
- restore
- advance restore
- advance menu
- report error
- key test
- show log
- partition sdcard
- fix permission
- info
- Disk
- system
- data
- cache
- sdcard
- sd-ext
- Memory
- Settings & Interface
- Enable/Disable Vibrate
- Enable
- Disable
- Enable/Disable Onscreen Button
- Enable
- Disable
- Brightness Control
- Low
- Medium
- High
- Timezone Setting
- Set Theme
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Download:
px-recovery-0.3.6-beta-cooper.zip [New]
px-recovery-0.3.5-beta-cooper.zip [Outdated]
px-recovery-0.3.2-beta-cooper.zip [Outdated]
px-recovery-0.3.1-beta-cooper.zip [Outdated]
px-recovery-0.2.7-beta.zip [Outdated]
Changelog:
0.3.6
update User Interface
Add menu: Set Theme
Ability to set theme (but only text color for now, for icon will added soon), Click Here for tutorial
Change onscreen button & loading icon
gio: fix taking screenshoot from recovery (Using DDMS)
0.3.3 - 0.3.5
Fix bug with menu button
Fix Hour on nandroid backup.
New Feature: advanced backup. u can choose what partition u want to backup. but still have a little bug with ui. if u from advanced backup menu and select some partition and then press back button. when u back to advanced backup again its display wrong status. all should on uncheklist. but not a big deal. no bug when do advanced backup.
Redesign UI. more fresh with transparant bar, selected text & onscreen button
Improve UI code. maybe next release it'll have themeable feature
0.3.2
Better settings algorithm.
Better autoload settings handler. this recovery will auto reboot & use default settings if fail to load settings
New function: Partition Info
New function: Memory Info
0.3.1
Remove unnedded +++Go Back+++ function. u can back use back on key & onscreen button
Time improvement. now you can see true time from recovery. set your timezone first from setting & interface menu
New function: auto save your settings
New function: auto load your latest setting when start recovery
NB: I recommend you to restart recovery after first time use 0.3.1 version (reason: initializing setting)
0.3.0
Add vibrate function. auto vibrate. but u can disable it from setting menu
Remove push apk to system (this feature is not important)
Add disable/enable onscreen button
New menu: setting & interface
wipe data: now not formatting sd-ext. only remove all files on sd-ext to prevent corrupted sd-ext partition
0.2.8
Fix problem with AROMA Installer. now fully working
0.2.7
Remove automount system & data feature (this feature cause trouble with "format" edify script when not unmounted)
Reworking with progressbar.
0.2.6
fix change button color. now only change when onscreen button touched
fix progressbar layout
fix menu set brightness after/cancel applying setting
reverse up & down onscreen button
New onscreen button image
0.2.5
touchevent: only active if onscreen button touched (not all screen provide event now)
add new feature: push apk to system (unfinished)
add new feature: auto mount/unmount system & data before/after install zip
reconfigure User Interface
0.2.1
fix overlap overlap text on onscreen button
update onscreen button
improve color & image quality
0.1.3
fix wipe data problem
split mount & format menu
rearrange menu
0.1.2
basic touchscreen support
added onscreen button
fix overlay onscreen button
added wipe menu
add reboot menu

it's simple & easy to make custom text color on px-recovery.
u only need to create new folder on /sdcard/.px-recovery/themes/(Theme-name) and config file inside it.
For example:
i want to make custom text color theme with name: Red-White
so, i create new folder with "Red-White" name on : /sdcard/.px-recovery/themes/
after that, i make a config file to make custom color.
here's sample of Red-White config:
Code:
255 0 0 255 //This line is for Menu Text Color
255 255 255 255 //This line is for Normal Text Color
255 255 255 255 //This line is for Header Color
255 255 255 255 //This line is for Line Color
255 0 0 255 //This line is for Selected Menu Color
255 255 255 255 //This line is for Selected Row Color
some explaniation for config file:
config file is consist of 6 lines
Every line consist of 4 item
4 item of line is about RGBA (Red, Green, Blue & Alpha (Transparacy)
here's some example of RGBA:
for example i want to make white color without transparent. RGB code for white is = 255 255 255. and for alpha max is 255. more smaller is more transparant.
so the code is:
255 255 255 255
<R> <G> <B> <A>
Here's some screenshoot & themes. u can download it and flash from px-recovery
Download

Special Thanks to:
Koush For Open his work & The best Recovery
CyanogenMod Team For being open. i learn many things from them
Team UtterChaos For open their source for touch recovery Here
squadzone For layout, battery stats, time & format option from Here

For Galaxy Gio?

If i may suggest, how about supporting lzma or xz compression. Both got much higher compression ratio with no much different cpu load then zip when decompressing. Might be useful for the low bandwith users as me
Sent from your phone

Tempoary only for devs.
i dont have cooper device to test it.
please report if u found bugs
​
RadioApoc said:
For Galaxy Gio?
Click to expand...
Click to collapse
this version for cooper
an0nym0us_ said:
If i may suggest, how about supporting lzma or xz compression. Both got much higher compression ratio with no much different cpu load then zip when decompressing. Might be useful for the low bandwith users as me
Sent from your phone
Click to expand...
Click to collapse
lol, later i'll try to add lzma support on it
but for now im working on theming support & full touch screen support

I had some errors at first, didn't have time to see them all, but the first line was "vibrate doesn't work" or something like that. Then I rebooted and it went in fine.
------------EDIT---------
Vibration works, touchscreen works, brightness level works.
Timezone works with reboot. No daylight saving however.

kevinlekiller said:
I had some errors at first, didn't have time to see them all, but the first line was "vibrate doesn't work" or something like that. Then I rebooted and it went in fine.
Click to expand...
Click to collapse
like this??
vibrate setting not found
using default: Enable
onscreen button setting not found
using default: Enable
Brightness setting not found
using default: High
Timezone setting not found
using default: GMT+0
Initialing settings..
Rebooting...
Click to expand...
Click to collapse
thats's not error.
only a warning, u dont have any saved setting to this recovery. since u used it for first time.
this recovery will automatically generate default settings

phiexz said:
like this??
thats's not error.
only a warning, u dont have any saved setting to this recovery. since u used it for first time. and this recovery automatically generate default settings
because this recovery required it to work perfectly
Click to expand...
Click to collapse
Yep, that's what it said.
In case you didn't see my edit :
------------EDIT---------
Vibration works, touchscreen works, brightness level works.
Timezone works with reboot. No daylight saving however (not a big deal , I set it to different time zone ).
----
Still testing so will let you know more.

kevinlekiller said:
Yep, that's what it said.
In case you didn't see my edit :
------------EDIT---------
Vibration works, touchscreen works, brightness level works.
Timezone works with reboot. No daylight saving however.
----
Still testing so will let you know more.
Click to expand...
Click to collapse
thanks for testing it
btw what do u mean with daylight saving

phiexz said:
thanks for testing it
btw what do u mean with daylight saving
Click to expand...
Click to collapse
No problem.
Only bug I found so far is vibration doesn't work on hardware buttons, only on touchscreen keys. Everything else is flawless.
Daylight saving is used in some countries when summer time comes to extend the amount sunlight hours in the night.
http://en.wikipedia.org/wiki/Daylight_saving_time

kevinlekiller said:
No problem.
Only bug I found so far is vibration doesn't work on hardware buttons, only on touchscreen keys. Everything else is flawless.
Daylight saving is used in some countries when summer time comes to extend the amount sunlight hours in the night.
http://en.wikipedia.org/wiki/Daylight_saving_time
Click to expand...
Click to collapse
yup, vibrate wont work on hardware button.
i only make it virate on onscreen button

Time zone fixed only after i made full backup and still correct after reboot.

Lovetz said:
Time zone fixed only after i made full backup and still correct after reboot.
Click to expand...
Click to collapse
time will be correct after u set timezone & reboot recovery
it should be correct after set timezone without reboot it.
but likely i made a little mistake on it algorithm. but its not a big problem i think

Sounds like an excellent project thanks phiexz and the devs who shared the code on the way. Have there been any substantial changes to the nandroid backup and recovery code, or will any bugs we encounter only be related to the changes to the user interface?

I'm installing PX recovery using AIO-Recovery Installer from GIO XDA Forum with AROMA Installer (GUI installer) i hope someone dev porting/using AROMA Installer based for Installing custom ROM method with easly to select what app you want to install on your device...
Sorry for my english..
Sent from my GT-S5830 using XDA Premium App

My question is,
what for?

Amazing work.
There's a stupid thing in CWM, which I hate the most. After the factory reset or formatting sd-ext, it is converted to ext2, but I prefer ext4. So I have to use some scripts or even ADB to do that one simple thing. It irritates me a lot.
So.. I would really like to see some convert-ext options (EXT2->EXT3->EXT4) like in good old Amon-RA-recovery.
And... I know it's crazy idea, but I had HTC Dream/G1 before and i've just loved possibility of access to console in recovery. Is there any possibility that touch-keryboard can be done in recovery? I suppose it will be difficult to do, but it would be incredibly awesome.

iandol said:
Sounds like an excellent project thanks phiexz and the devs who shared the code on the way. Have there been any substantial changes to the nandroid backup and recovery code, or will any bugs we encounter only be related to the changes to the user interface?
Click to expand...
Click to collapse
nandroid: note yet
recovery: a lot changes
antmanPL said:
Amazing work.
There's a stupid thing in CWM, which I hate the most. After the factory reset or formatting sd-ext, it is converted to ext2, but I prefer ext4. So I have to use some scripts or even ADB to do that one simple thing. It irritates me a lot.
So.. I would really like to see some convert-ext options (EXT2->EXT3->EXT4) like in good old Amon-RA-recovery.
And... I know it's crazy idea, but I had HTC Dream/G1 before and i've just loved possibility of access to console in recovery. Is there any possibility that touch-keryboard can be done in recovery? I suppose it will be difficult to do, but it would be incredibly awesome.
Click to expand...
Click to collapse
bad idea to convert ext filesystem from device.
sometimes e2fsck & tun2fs cause trouble on sd-ext
i recommend use your pc to format them to ext4
and this recovery will not format your sd-ext partition in wipe data mode.
its only remove all files on sd-ext to prevent sd-ext converted to ext2/3
but it still on test mode. IDK this methode will cause problem with d-ext or not
but until now no one complain about it
its hard to make onscreen keyboard on recovery
why dont u use adb shell instead??

[ROM][MIUI GB - Final Fixed] [FireKernel]

this rom is based on MIUIXXX v.0.36
i just add some tweak and patch for make it faster and fixing some bugs
Working:
sms
calender syncing is work now
Audio
vpn conection
Dsp Manager
Sensors
Full 2D/3D/HW acceleration
Camera/Camcorder
WiFi
BLN
Bluetooth
Browser
Live wallpapers
GPS (Use fasterfix to set your region)
Deep sleep
FM radio
Wifi and usb tether (using an app from Play store)
And all is working in cm7 or in MIUI
Music Player also gets themed when you change your theme
4-way Reboot
30 Steps Volume Mod
fixed
operator name
thanks & credit
all goes to SmOuuK & LewisGauss for making possible to enjoy miui for our ace
Installation :-
1. Wipe data/ factory reset
2. Wipe cache partition
3. Advanced/ wipe dalvik cache
4. Advanced/ wipe battery stats
5. Mount and storage/ format system
6. Install zip from sdcard/ choose zip from sdcard and select the ROM zip
7. Reboot n Enjoy
Pick it up ringtones to choose from the following:
theme-edit theme-ringtone
download ROM
http://www.mediafire.com/?h838e4azkv9of51
Attention
if u fell lag in rom,i suggest to
*
change kernel and use this boot.img,instead of the same file in rom
now flash rom again
http://www.mediafire.com/?ht8mhw25hwb38fi
*
change the theme,with default one
http://www.mediafire.com/?cbch6uvwht78l7s

no credit? no instruction how to install? no enough information? BUT I hope you have a permission

I hope you have permissions now. But it's looking like your latest share miui final. Just different theme ?

Woow thanks dude
You can take thread of MIUIXXX? Lewis has never released an update. You could give updates to MIUIXXX

no credit ??
have you asking for permission?
plis .... respect...
GT-S5830

Coming soon threads arent allowed following the xda policy
Sent from my GT-S5830 using xda premium

Give big thanks to ahmad safar dude..
Sent from my Nexus S using Tapatalk 2

are you sure?
are you sure this is "final"? is graphic bugs fixed? things like clock widget and launcher edit mode... and yes, "coming soon" is a little bit annoying

Cant see the download anywhere
!!

It will be multilanguage?

Any feedback for this rom, working -not working -issues - is the link still active ????
Sent from my GT-S5830 using xda app-developers app

Where I have to put boot.img?

Dru79 said:
Where I have to put boot.img?
Click to expand...
Click to collapse
Copy the ROM and kernel in a custom folder, then open the rom with winrar drag the rom to the kernel after it replaced the previous

Ringtone starts only after first ring.
Sorry for my english.
Tapatalk 2-vel küldve az én GT-S5830-ről

Did you repair graphic issues (in some games and apps) and slow working on some launchers etc.?

this is gorgeous!

Testing with updated kernel. Any report in this same post, later today or in the next days. First impression: wow! Second impression: (wow!)^3.
To be continued...
UPDATE 1: Ok, here some notes after some tries...
Strange visualization of some apps (e.g. Jrummy's Root Browser Lite) with wrong space and scale between graphic elements. Text in Google Play is near white, almost unreadable, also in Viber's popup windows. Some chinese symbols in calendar. Email's input fields dirtied by strange blue lines. Compass ovalized.
Deleted useless (for now) scripts:
00banner, 01mountsd, 02miuithemeprop, 04 first boot, 05 lagfixer, 07 writeback, 09scardspeedfix, 97swap2sd, net_buffer, remount_fullext4, s99drop_cache.
Also, maybe I'm wrong but it seems to me that swap file function isn't supported by kernel, apparently you cannot have a swap file.
Modified also build.prop but only to meet my needs of mantain scripts as clean as possible!
UPDATE 2: deleted /system/default.prop, the values here aren't well suited for this rom causing instability or reboots. It will be automatically replaced by the default file residing in the ram disk.
UPDATE 3: replacing kernel with that taken from latest LeWa rom (only for test purposes, some devices e.g. bluetooth will not works!) you can activate the swap file. Sorry I cannot try further this rom, I hope that the next version will be better.
This rom is enjoyable although not perfect, needs some work but the path is right! My bests!

Additionally: auto-retrieve MMS doesn't work.

Hello, any progress with bugs removal?

slimohnr said:
Hello, any progress with bugs removal?
Click to expand...
Click to collapse
Ram does not have any particular problems

[ROM][CM10.2][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M

CM10.2 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz5.18.4 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM10.2 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). More desired may be the new privacy manager features that allow you to control, on a per app basis, which information you wish to share. Other improvements include an improved lockscreen cLock and a new integrated Superuser.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera/Camcorder
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* When unlocking the screen, sometimes only the capacitative buttons light up, and the screen doesn't come on. This seems to happen about 80% of the time.
Solution: This can be fixed by locking the screen, then unlocking it again. In about 5% of these cases the screen does not come on again. Just repeat the steps again until it does.
This has been fixed as of build 20131029
* You may notice a screen flicker when you first flash this ROM. This is due to a bug where the system can't decide whether to render the graphics with the cpu or the gpu, thus the flicker.
Solution: This is fixed by turning on Settings -> Developer Options -> Disable HW Overlays (You must first enable Developer Options by pressing 7 times on Settings -> About Phone -> Build Number). This will be reset on every boot. if you install Universal Init.d, my 91fixoverlays script will run on each boot and fix this automatically.
This has been fixed as of build 20131029
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 flashable zip which is compatible with CM10.1/CM10.2
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140224 (Latest)
ROM: cm-10.2-20140224-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20140224-signed.zip (106.5MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A dirty flash should work for upgrading , but a clean flash is highly recommended
Build: 20140120
ROM: cm-10.2-20140120-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20131231-signed.zip (103.8MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with CM10.1/CM10.2
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with CM10.1/CM10.2
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]December 23, 2013 - Build 20131223[/B]
* Revert build.prop to use dyn instead of gpu (less problems)
* Added back 91fixoverlays to /system/etc/init.d to disable hw overlays and fix screen flicker on boot
* Re-worked 91fixoverlays script so that it now runs in it's own shell to stop it from blocking other startup scripts and causing a laggy boot
* Fixed up device tree code including adding the correct definitions for boot animation size and update to the build fingerprint
* Synced latest changes from CyanogenMod
[B]December 1, 2013 - Build 20131201[/B]
* Force gpu rendering in build.prop
* Improve fix for screen on delay
* Synced latest changes from CyanogenMod
* Updated GAPPS
[B]October 29, 2013 - Build 20131029[/B]
* Tweaked build.prop to fix screen flicker and notification drawer lockup
* Fixed screen unlock bug - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/5e163ff0c5d90a4518cbc9e14c86dceec095c70a"]Commit 5e163ff0c5d90a4518cbc9e14c86dceec095c70a[/URL]
* Added SmartAssV2 Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/511e45206bb9a1454a0c43b3d626749c1fa2c241"]Commit 511e45206bb9a1454a0c43b3d626749c1fa2c241[/URL]
* Added Adaptive Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6"]Commit 7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6[/URL]
* Added Lagfree Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/d1392017601d27303fbce9da18d2af718e7e1a65"]Commit d1392017601d27303fbce9da18d2af718e7e1a65[/URL]
* Restore Advanced Device Settings - [URL="https://github.com/titanic-fanatic/android_device_samsung_msm8660-common/commit/3126c17c6165c7d96abde4cd7459769e165aa195"]Commit 3126c17c6165c7d96abde4cd7459769e165aa195[/URL] / [URL="https://github.com/titanic-fanatic/android_packages_apps_Settings/commit/9031ffb1f4e4185f397724a27e3d75afe7fd67e4"]Commit 9031ffb1f4e4185f397724a27e3d75afe7fd67e4[/URL]
[B]October 5, 2013 - Build 20131003[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market, and also make sure you have Universal Init.d installed and active. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. When your phone reboots, recovery will warn you that your device may possibly be unrooted. This is because of the install-recovery.sh script that is required to start the superuser daemon which allows SuperSu to manage superuser permissions. You are not unrooted ;-)
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. This needs to be set on every boot unless you are running Universal Init.d and my 91fixoverlays script is present in the /system/etc/init.d folder.
Q. When I unlock my screen, my menu/home/back/search buttons come on but the screen is black?
A. This is a known bug in this ROM and is on the list of things that need to be fixed. For now, when this happens, just lock the screen, then unlock it again and the display should come back. If it does not, repeat until it does (the most number of times i had to do that was 3).
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM10.2 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-10-05
Last Updated 2014-02-23

Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.

Wow! Thanks so much. Downloading now.

iDynamics said:
Wow! Thanks so much. Downloading now.
Click to expand...
Click to collapse
Wow, you already found it and I wasn't even finished putting everything up... make sure you use the new CWM, very very very important!

Followed the instructions ( to the best of my ability ) but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!

iDynamics said:
Followed the instructions but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
Click to expand...
Click to collapse
I totally forgot to update the build.prop with the build type, it is responsible for the red border. Either use a build.prop editor or open the /system/build.prop with a text editor and change the following line:
ro.build.type=eng
Click to expand...
Click to collapse
Change it to:
ro.build.type=user
Click to expand...
Click to collapse
You will need to reboot after making this change.
In regards to the 91fixoverlays script, I do appologize. I forgot to include it in the zip... Please download the attached 91fixoverlays.txt file and rename it to 91fixoverlays and move it to /system/etc/init.d and change it's permissions to match the other files in that directory.
Sorry for missing these two things. I will update the packages ASAP and will post a note when it's done so you know that there is no need to follow the steps in this post.

Much appreciated! No more red flickering. Thanks!

Wow! Thank you!
Sent from my SGH-I757M using xda app-developers app

This. Is. Amazing!!!!!
Downloading now, will install and report back in a bit with findings.
Thanks so much!!

Awesome. Downloading. Will report back. Thanks!
Sent from my SGH-I757M using xda premium

I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will do more testing.
Thanks

Zippy Dufus said:
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will so more testing.
Thanks
Click to expand...
Click to collapse
I think this is due to our oddly small cache partition. Only 100MB as compared to the skyrocket at 300MB. Currently, I only moved four apps in the gapps package to the data partition do that their dex files don't end up in the /cache/dalvik-cache dir and instead end up in /data/dalvik-cache. I think I need to move others. I also think that it happens only on first boot without side effects because a couple of the installed apps only run on first boot, then their dex files can be deleted (I think this happens automatically).
Sent from my SGH-I757M using XDA Premium 4 mobile app

Thanks titanic_fanatic, you've breathed new life into an old phone
Sent from my SGH-I757M using Tapatalk 2

Only issue I've run into so far is that auto rotate doesn't seem to work :-/
Sent from my SGH-I757M using XDA Premium 4 mobile app

I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app

rukusx7 said:
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
Cool, I'll give that a try. Anyone else having auto-rotation issues?
Sent from my SGH-I757M using XDA Premium 4 mobile app

Rotation is not working for me, though I always keep it on portrait anyway so I am not complaining.

Rotation doesn't work here, and every so often I run into spells where the only button that works is the home button and haptic feedback stops working all around. A reboot fixes it and it seems random. Other than those few things this is soooooo smooth. I'm happy. Thanks so much!
Sent from my SGH-I757M using xda premium

Fix for Sensors
Hey guys, to fix the sensors, download this attachment sensors.default.so.txt and rename it to sensors.default.so, move it to /system/lib/hw and give it the same permissions as the other files in that directory, then reboot and your sensors should be working

Works now! Thanks ya muchly.
Sent from my SGH-I757M using xda premium

[ROM][DEV][SlimKat][KK4.4][KERNEL][SGH-I757M]UNOFFICIAL SlimKat 4.4 - Bell SGH-I757M

SlimKat 4.4 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2/CM11.0, you are required to update
your recovery to a supported recovery with a version greater than 6.0.39. As of this writing, the latest available
version is Philz Touch Recovery 6.57.9 (based on CWM 6.0.5.1) for the SGH-I757M. There is currently not a
version of regular CWM for this device that will flash Kit Kat ROMs.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D SlimKat (Android4.4.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). There is a lot to be said about Kit Kat with it's clean white icons and new launcher. The focus with Kit Kat was to make the device use less RAM and imrove performance, and so far it's running great. Art seems to be fully functional in SlimKat and the device runs smooth ;-)
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera (Camcorder doesn't work right now. Don't select it or you'll mess up the camera all together)
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
* USB Mass Storage (UMS mode)
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* Not only does the camcorder not work, but selecting it will cause the camera to not function at all, so be careful not to select camcorder. There is currently no fix if you accidentally select camcorder mode, so be careful or you may need to reflash the ROM to get the camera working again. I'm working on a solution that will at least not put it into this loop for now.
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new Philz Touch Recovery 6.57.9 flashable zip which is compatible with CM10.1/CM10.2/CM11.0/SlimKat
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the philz_touch_6.57.9-celoxhd.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios (Required before you flash the ROM, unless you already have the new JB radios flashed)
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: Using Philz Touch Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20141126 (Latest)
ROM: Slim-celoxhd-4.4.4.build.8.16-UNOFFICIAL-20141126-1146.zip (142.0MB)
GAPPS: Slim_mini_gapps.4.4.4.build.8.x-385.zip (64.01MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A clean flash is REQUIRED if upgrading from a previous version of android such as CM10.2/SlimJB4.3.
Build: 20141005
ROM: Slim-celoxhd-4.4.4.build.8.2-UNOFFICIAL-20141002-1545.zip (142.6MB)
GAPPS: Slim_mini_gapps.4.4.4.build.8.x-282.zip (60.2MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.13.2 (CWM 6.0.4.7) compatible with CM10.1/CM10.2/CM11.0/SlimKat
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]November 26, 2014 - Build 20141126[/B]
* Increased kernel version to Titanium 1.1.1
* Added cpu input boost framework - credit: sultanxda
* Added cpu OC (The scale goes up to 1890MHz, but you should only put it as high as 1836MHz since I was getting random reboots with 1890MHz. 1674MHz is the default OC and 1512MHz is the default CM OC) - credit: TeamFahQ/sultanxda/titanic-fanatic
* Added low power flash mode which will use a low powered flash when the battery is equal to or below 35%. This should help with the camera causing the phone to shut down when trying to take pictures using the flash. This threshold may need to be tweaked, so please let me know if you still experience shut downs related to using the camera. - credit: sultanxda
* Added sgs2hdbell as a device name to the updater-script to allow all bell i757m devices to flash the ROM without the need to edit the updater-script.
* Added panel undervolt interface. - credit: sultanxda
* More memory optimizations. Some of the extra RAM that the previous optimization gave us has been allocated to other things such as the surface flinger. Available RAM is now around ~760MB.
* Removed vbus_present wakelock for good (it worked it's way back in somehow)
* Added fast charge. Phone will now charge at 1200mA until 95% regardless of your charging source (AC/USB)
* Added exFAT driver to kernel. It's a filesystem like ext4 but is based on Windows FAT filesystem. You can format your sdcard as exFAT as it's supposed to be faster than vFAT which is what our sdcards are formatted as. Make sure you backup your sdcard contents before formatting it as exFAT and keep the backup until your sure you want to stick with exFAT.
* Removed NFC since I don't think anyone uses it and can't figure out how to have it disabled by default so it is removed completely. If someone is using NFC, let me know and I'll add it back but for now, I just see it as a battery drain.
[COLOR="Red"][B]NOTE:[/B] With the overclocking of this kernel, all antutu tests passed up to 1836MHz. At 1890MHz, antutu caused the phone to reboot during the String Sort tests. This is so far the only thing that has caused reboots, but there may be other actions that will cause this too. If you find that your device is randomly rebooting, turn the overclock down by one step (ie: from 1836MHz to 1782MHz which is one step lower). Then go back to using your phone normally. If you still get random reboots, keep turning the OC down until it doesn't happen anymore.[/COLOR]
[B]October 5, 2014 - Build 20141005[/B]
* Kernel now has a custom version number in addition to my kernel name of Titanium
* Optimized kernel memory mapping to increase our physical RAM from ~730MB to ~800MB (a whole 70 extra MB... whoa!)- credit: sultanxda
* Removed mDNIe (it's not supported/working)
* Removed 91fixoverlays script (no longer needed)
* Removed persist.hwc.mdpcomp.enabled from build.prop (hack to fix the hwoverlays because fb drivers are broken somehow) - credit: sultanxda
* Added GPU overclock from 266MHz to 320MHz (helps a lot with the UI lag) - credit: sultanxda
* Added code for 2 phase OnDemand governor - credit: sultanxda
* Added opensource frandom module to help speed up the UI (also helps with the lag) - credit: bryan2894
* Added mdp Color Enhancements (better display color) - credit: sultanxda
* Added color/gamma controls in place of mDNIe (see the tips and tricks section for my already tweaked favorite settings) - credit: bryan2894/titanic_fanatic (I had to integrate it into our display drivers)
* Added Swipe 2 Wake (S2W) support in the kernel (it's actually tap once on each key from left to right). - credit: bryan2894
* Added audio.r_submix.default.so to the build to enable screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary audio channels in the audio_policy.conf for screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary settings in Advanced Device Settings for screencasting and color/gamma control - credit: bryan2894/titanic_fanatic (I added the screencasting settings)
* Fixed the annoying BLN sticking (I think... Please confirm this for me) - credit: bryan2894
* Fixed the sampling rates for A2DP, input and r_submix channels - credit: bryan2894
* Changed both scaling governors to OnDemand - credit: bryan2894
[B]August 16, 2014 - Build 20140816[/B]
* Synced with sources
* Added sysfs interface for vibrator intensity control
* Added settings to control vibrator intensity in Advanced Device Settings
* Moved Advanced Reboot Options to Developer Options
* Fixed FC in Settings app when trying to access Security Settings
* Added Omni Performance Control
[B]April 12, 2014 - Build 20140412[/B]
* Synced with sources
* Fixed network selection dialog
* Added USB Mass Storage mode (UMS)
[B]March 19, 2014 - Build 20140319[/B]
* Synced with sources
* Removed 91fixoverlays script (hw overlays no longer need to be disabled)
[B]February 12, 2014 - Build 20140207[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. Reboot your phone and you should be rooted.
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @Socim - Thanks to Socim for pointing me in the right direction a few times ;-)
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL SlimKat KK4.4 For Bell SGH-I757M, ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
Source Code: https://github.com/titanic-fanatic
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: SlimKat
Version Information
Status: Alpha
Created 2014-02-12
Last Updated 2014-12-09

Tips & Tricks
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.

Anyway to remove the status bar pull down lag? Everything else runs great! :good:

iDynamics said:
Anyway to remove the status bar pull down lag? Everything else runs great! :good:
Click to expand...
Click to collapse
Not currently. Maybe changing the governor will help. Oh also, turn on art in dev options
Sent from my SGH-I757M using XDA Premium 4 mobile app

THANK YOU!!!!
TF ur AMAZING!! thank you so much.... ive benn waiting soooo long for this :laugh::good::victory:

I am very ocd about having a smooth status bar. I will stay with your fantastic 10.2 rom until this issue is fixed.

This ROM is way smoother than the cm11 build. Looking forward to the camcorder fix!
Sent from my Nexus 5 using XDA Premium 4 mobile app

Settings bug.
If enter to Developer options then App error in Security options.
And if enter to Security - error in developer.

Alexander Kalinin said:
Settings bug.
If enter to Developer options then App error in Security options.
And if enter to Security - error in developer.
Click to expand...
Click to collapse
I ripped the settings.apk from the hercules slimkat build on slimbeans official site then put it into this rom's zip and flashed. It solved the security FC.

iDynamics said:
I ripped the settings.apk from the hercules slimkat build on slimbeans official site then put it into this rom's zip and flashed. It solved the security FC.
Click to expand...
Click to collapse
I'm having the same issue with security menu. Would you mind posting the settings.apk you ripped? I'd like to try it out. Thanks in advance idynamics.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

manfromgta said:
I'm having the same issue with security menu. Would you mind posting the settings.apk you ripped? I'd like to try it out. Thanks in advance idynamics.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Put it in /System/Priv-App
http://www.mediafire.com/download/s29lianid2y89i6/Settings.apk

Having Issues in dailer......when i open dialer it says dialer is not Responding report....Plz help me how to fIx it??

sandhu6698 said:
Having Issues in dailer......when i open dialer it says dialer is not Responding report....Plz help me how to fIx it??
Click to expand...
Click to collapse
You will have to learn how to take a logcat to post here after the error occurs. Instructions are in the second post.
Sent from my SGH-I757M using XDA Premium 4 mobile app

Whats logcat sir ?? M just telling u the problem m facing....plz tell me what can i do i will follow you
Sent from my SGH-I757M using XDA Premium 4 mobile app

Heres a screenshot
Sent from my SGH-I757M using XDA Premium 4 mobile app

Sir....why do i see these red colour borders at edges..??? I tired to edit build.prop.type to user but its not changing? ...i mean i change it from eng to user ...but afret reboot it changes back to eng ......m using ROM Toolbox for build.prop.editor
Anyway to fix it ??
Sent from my SGH-I757M using XDA Premium 4 mobile app

sandhu6698 said:
Sir....why do i see these red colour borders at edges..??? I tired to edit build.prop.type to user but its not changing? ...i mean i change it from eng to user ...but afret reboot it changes back to eng ......m using ROM Toolbox for build.prop.editor
Anyway to fix it ??
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Back in late December titanic addressed and fixed this bug in 10.2 rom. Read post #8 from his 10.2 thread to see if it helps.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

sandhu6698 said:
Sir....why do i see these red colour borders at edges..??? I tired to edit build.prop.type to user but its not changing? ...i mean i change it from eng to user ...but afret reboot it changes back to eng ......m using ROM Toolbox for build.prop.editor
Anyway to fix it ??
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is definitely due to the build type, but this roms build.prop already has the build type set to user. Did you do a clean flash if you came from another rom? Did you modify the build.prop at all before this happened?
Your build.prop editor needs root access and by default, this rom is set to root for adb only. You can change that in the developer options to allow both apps and adb to gain root. Then your build.prop edits should stick.
I'm still confused how you have a build.prop with build type set to eng though since the build type is set to user in my rom. My Best guess is that you came from rukusx7's hellkat rom and didn't wipe before you flashed this one. That would save your system files and maybe cause some conflicts which might explain your issue with the dialer. My suggestion to you is to always wipe/factory reset when flashing new roms. This will minimize the potential for problems.
Sent from my SGH-I757M using XDA Premium 4 mobile app

titanic_fanatic said:
This is definitely due to the build type, but this roms build.prop already has the build type set to user. Did you do a clean flash if you came from another rom? Did you modify the build.prop at all before this happened?
Your build.prop editor needs root access and by default, this rom is set to root for adb only. You can change that in the developer options to allow both apps and adb to gain root. Then your build.prop edits should stick.
I'm still confused how you have a build.prop with build type set to eng though since the build type is set to user in my rom. My Best guess is that you came from rukusx7's hellkat rom and didn't wipe before you flashed this one. That would save your system files and maybe cause some conflicts which might explain your issue with the dialer. My suggestion to you is to always wipe/factory reset when flashing new roms. This will minimize the potential for problems.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did a clean flash now the Roms rocks .....m using it battery life is also great in this slim kat rom .....

iDynamics said:
Put it in /System/Priv-App
http://www.mediafire.com/download/s29lianid2y89i6/Settings.apk
Click to expand...
Click to collapse
I replaced Settings.apk in the SlimKat zip with the one you uploaded to mediafire. Booted into recovery, wiped system and cache and flashed the fixed zip. I still FC upon selecting Security. Any suggestions?

[CWM] [Machfive] CWM Philz touch recovery for Karbonn Machfive

Hello friends
Finally After Lot of Struggle And Hard work , I succussfully Ported PhilZ Touch Recovery To Karbonn Machfive
Features:-
Quote:
* Touch Interface
- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- Friendly Log View and pause on logs: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 30 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- time setting is now applied to all recovery session, including timestamp of created/modified files (v4.92.3+)
- capture recovery screen shots with a gesture action
- one file to save all settings
- backup and restore settings file
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
Click to expand...
Click to collapse
Bugs
Screen upside and down (fixed now)
Installation Procedure : -
Requirement :-
1) Rooted Device (Root Method)
2) Mobile Uncles tool (Get it from Play Market)
Procedure :-
1) After Rooting your device and installing Mobile Uncle tools, download the "PhilZ Recovery image" From Below .
2) Rename it to "recovery.img"..
3) Place it in the root of your SD card .
4) Open Mobile Uncle tools and choose the "Recovery Update" option.
5) Choose the recovery image you placed in the SD card and install it.
6) All Done,You have flashed PhilZ Recovery .
Credits :
PhilZ
Yuweng
Downloads http://www.mediafire.com/download/krhin04qn459ycq/philz-touch.img
if u hve any problem contact me in fb chethu00
Press Thanks Button If u Like My Work

Thanks bro. Is it working without any problems.
Sent from my MACHFIVE using Tapatalk

sapthesh said:
Thanks bro. Is it working without any problems.
Sent from my MACHFIVE using Tapatalk
Click to expand...
Click to collapse
Ya bro try now bugs fixed everything is fine

Thanks bro will test it. Between thanks again for your efforts and can i flash xposed installer for this device. Please advise so our device may be fully equipped with awesomeness.
Sent from my MACHFIVE using Tapatalk

sapthesh said:
Thanks bro will test it. Between thanks again for your efforts and can i flash xposed installer for this device. Please advise so our device may be fully equipped with awesomeness.
Sent from my MACHFIVE using Tapatalk
Click to expand...
Click to collapse
ya bro u can flash it witout any problem its working like a charm in my device

Installed Recovery Works like charm. can u give me the list of working xposed modules on this device. It would be great to list out.
Sent from my MACHFIVE using Tapatalk

Thank you! Very much Its working perfectly
ch3than said:
Hello friends
Finally After Lot of Struggle And Hard work , I succussfully Ported PhilZ Touch Recovery To Karbonn Machfive
Thank you! Very much Its working perfectly
Bugs
Screen upside and down (fixed now)
Installation Procedure : -
Requirement :-
1) Rooted Device (Root Method)
2) Mobile Uncles tool (Get it from Play Market)
Procedure :-
1) After Rooting your device and installing Mobile Uncle tools, download the "PhilZ Recovery image" From Below .
2) Rename it to "recovery.img"..
3) Place it in the root of your SD card .
4) Open Mobile Uncle tools and choose the "Recovery Update" option.
5) Choose the recovery image you placed in the SD card and install it.
6) All Done,You have flashed PhilZ Recovery .
Credits :
PhilZ
Yuweng
Downloads http://www.mediafire.com/download/krhin04qn459ycq/philz-touch.img
if u hve any problem contact me in fb chethu00
Press Thanks Button If u Like My Work
Click to expand...
Click to collapse
Thank you! Very much Its working perfectly

Please create custom rom for karbonn mach five
Sent from my MACHFIVE using XDA Free mobile app

Want The Latest Philz Touch Recovery
Please Provide The Latest Version Of PHILZ TOUCH RECOVERY (Ported)