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

[titanic_fanatic]

SlimKat 4.4 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)

[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]

[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]

[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 ;-)

Images

SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.

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)

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.

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)

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

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.

Tips and Tricks

Checkout the second post for some tips and tricks on setting up the ROM.

Changelog

[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

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.

Thanks To/Credits

* 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

 

[titanic_fanatic]

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

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.

 

[iDynamics]

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

 

[titanic_fanatic]

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

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

 

[silva92]

THANK YOU!!!!

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

 

[iDynamics]

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

 

[FuryriderX]

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

 

[Alexander Kalinin]

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

 

[iDynamics]

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

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.

 

[manfromgta]

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.

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

 

[iDynamics]

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

Put it in /System/Priv-App

http://www.mediafire.com/download/s29lianid2y89i6/Settings.apk

 

[sandhu6698]

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

 

[titanic_fanatic]

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

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

 

[sandhu6698]

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

 

[sandhu6698]

Heres a screenshot

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

 

[sandhu6698]

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

 

[manfromgta]

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

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

 

[titanic_fanatic]

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

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

 

[sandhu6698]

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

I did a clean flash now the Roms rocks .....m using it battery life is also great in this slim kat rom .....

 

[JayR_L]

Put it in /System/Priv-App

http://www.mediafire.com/download/s29lianid2y89i6/Settings.apk

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?