[Guide] Installation Tips for LSZ + Rooting Methods [Lag Free]

[Guide] Installation Tips for LSZ + Rooting Methods [Lag Free] - Galaxy Note GT-N7000 General

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
I'm trying to help the 10% Who are suffering from "Lag" and not so Buttery Experience with the latest Official Release of JB From SAMSUNG.
This is merely a Guide of How I managed to install LSZ and how to achieve the smooth experience of jelly bean.
The Rooting tools used here are not my work, and I thank everyone contributed into making them for the community
(Thanks to XDA Community for the great efforts and constitutions)
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
:: Disclaimer :: This Thread is Explaining solely how I Like to install this ROM or any future ROM to ensure Perfect Combination of Stability and Permanence and everyone might have his own Preferences and methods as well ::
How to Install (Coming from Leaked JB, ICS or GB) :
1. Make a Backup of your Applications and Data using Go Backup or Titanium Backup;which ever you Like.
3. Make a Backup of your Internal Storage to your PC.
Note: Mount Your Internal and External Storage to your PC by Either "USB Utilities" or "USB Switcher App *Root*" in case you only have "Media Server USB".
4. Format your Internal Storage from your PC to : FAT32 with File Allocation Size: 4KBs.
a. Right Click on Internal Storage (Usually the one with 11GB) and select "Format".
b. Select type: FAT32 and Allocation Size :4096 Bytes, Untick Quick Format.
5. Install a Safe Kernel From here:
http://forum.xda-developers.com/showthread.php?t=1901191
6. After Installing the Kernel, reboot into Recovery and Do a Factory Reset, and head to Phills Advanced and Look for "Clean For new System Installation" thing and Click it, after finish, shut down the phone.
To Boot into Recovery, Shutdown the Phone : Hold Vol (+) and Home Button and Power Button, release power button when you see Samsung Logo.
7. Now install JB LSZ using PC Odin, you can find the instructions on this Link:
http://forum.xda-developers.com/showthread.php?t=1424997 (Thanks to Dr.Ketan) .
PS: after the phone restarts, leave it until it finishes the Boot, and installs the applications of the system (The Bloatware) and then until it boots to the home screen.
8. Reboot to Download mode and install the latest safe Kernel for LSZ (search for it by this name: XXLSZ-OXA ) from this link on the third post:
http://forum.xda-developers.com/showthread.php?t=1901191
9. After rebooting when completion, go to Settings on the phone and select Factory Reset, and make sure to select to erase internal Storage.
This will ensure a clean system with Aligned memory storage, will kill LAG factor.
10. After booting again, check for lag, and leave it to settle, and then restore your apps and data, and copy your data from PC to Internal again, and leave it for a while to settle again. should be good to go now!
A side tips:
a. I have Uninstalled all the Bloatware using Titanium Backup, which i believe helped in my cause of presuing better speed of LSZ (Like Google+,G music, G magazines, etc).
b. Formatting the External SD card is a must also, to make sure Media Scanner is not having errors on it.
This Hopefully should give you the best Install procedure for LSZ, i have had many lags but after doing this method, I have achieved superb speed. Though, expect few to little lags on the first few boots until the system finishes Media Scanner and making cache files etc.
How to Root LSZ?
1. Install This Kernel using Odin in case you don't have it : XXLSZ-OXA from this link on the third post:
http://forum.xda-developers.com/showthread.php?t=1901191
2. Reboot into Recovery and install the File I have attached here, and you will have root ready, Good luck.
Note: download the zip version of the kernel LSZ to external sd and flash it using stock recovery to avoid yellow triangle if you want.
To clear Yellow Triangle and Counter count on Galaxy Note, please download "Triangle away" by Chain Fire, from this Link and rest it:
http://forum.xda-developers.com/showthread.php?t=1494114
I have gathered this Information though my experience with my Galaxy Note and the information I have found and the tools available on XDA, I don't claim owner ship of any of the Root Tools or Rom it self, If you need help I would try to help you if i can. Best regards

Cool.
Posts like this are always the best world when it comes to help more people in a simple way.
Fortunately, my installation went pretty well, just like the JB running after that.

Just helping the troubled minds and glad you had no issues.

You know that there is a PIT file for Odin which formated all memory on Note? And it can be done in JB installation process,all at once...
Sent from my GT-N7000 using Tapatalk 2

zviki said:
You know that there is a PIT file for Odin which formated all memory on Note? And it can be done in JB installation process,all at once...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
The Pit method can be risky, and ive learned from my older device to not play with Pit files much,... )

AW: [Guide] Installation Tips for LSZ + Rooting Methods [Lag Free]
Sorry, but 2x factory reset, and formating storage? Flashing a kernel with Odin, that will lead to a triangle and increased flash counter? Correct me, If I'm wrong.
Cheers, Markus

in OP, is steps 4 & 5 really necessary?
By what the Dr says here:
http://forum.xda-developers.com/showpost.php?p=38183950&postcount=5587
I would think not..

Perfect way to flash LSZ
Yes brother, for LM5 there is no issue, but in LSZ if you dont do it as in OP you may get bootloops.. i tried..
if you use mobile odin for flashing lsz then need to flash bootloader separately as mobile odin cant flash bootloader.
My way of perfect installation is
Flashing instructions
1. flash any 4.x Philz Kernel
2. reboot recovery
3. Go to Philz settings
4. Select Clean Before Flash new rom
5. Wipe Dalvik Cache
6. reboot to download (advanced)
7. flash the new in using PC Odin (select PDA tab and browse .tar.md5 file)
for just rooting flash supersu as in OP
for a safe kernel, flash Philz LM5 Kernel.
if anyone want to try LSZ custom or cwm versions then first flash any 4.x philz kernel and
Go to Philz settings
Select Clean Before Flash new rom
Wipe Dalvik Cache
Flash rom, then after rom installation reboot to recovery and do flash bootloader separately in cwm.
jeffs99 said:
in OP, is steps 4 & 5 really necessary?
By what the Dr says here:
http://forum.xda-developers.com/showpost.php?p=38183950&postcount=5587
I would think not..
Click to expand...
Click to collapse

very useful. Thanks
Sent from my GT-N7000 using xda premium

installation
i instaled the ROM usig Mobile odin Pro which rooted the device...even got all the application, SMS, contacts back but i guess i am not on (safe Kernel)Philz kernel....everything is good for me except the battery is draining like 1% every min....no air view..or smart rotation..guessing its not included for galaxy note 1......while browsing through EFS to external card folder it shows it to be empty...but My files shows the external card content..through Storage/external card...and camera shortcut through lockscreen seems to be not working for me...what troubles me the most is the battery problem....i need a good batter life....as i am constantly reading books on the note...is there any workaround for the battery?

Gugelhupf said:
Sorry, but 2x factory reset, and formating storage? Flashing a kernel with Odin, that will lead to a triangle and increased flash counter? Correct me, If I'm wrong.
Cheers, Markus
Click to expand...
Click to collapse
Yes bro, to get rid of the triangle just install 'triangle away' and get rid of it, but this will ensure 100% no bootloops.
Sent from my GT-N7000 using xda premium

prajjwal said:
i instaled the ROM usig Mobile odin Pro which rooted the device...even got all the application, SMS, contacts back but i guess i am not on (safe Kernel)Philz kernel....everything is good for me except the battery is draining like 1% every min....no air view..or smart rotation..guessing its not included for galaxy note 1......while browsing through EFS to external card folder it shows it to be empty...but My files shows the external card content..through Storage/external card...and camera shortcut through lockscreen seems to be not working for me...what troubles me the most is the battery problem....i need a good batter life....as i am constantly reading books on the note...is there any workaround for the battery?
Click to expand...
Click to collapse
I believe you should do a clean install to fix your drain issue, as i had that while upgrading from ics to jb with out wipe, now my drain is very minimum like this image.
Sent from my GT-N7000 using xda premium

thanks for the guide.
was about to move from leaked JB rom to the new official release.
already did a nandroid backup
i'll make sure to use a safe kernel.

Welcome

I am a beginner of rooting my Note. I have updated my Note to 4.1.2 from the Samsung Rom
I would like to ask if my note baseband version is N7000XXLSO and the build number is JZO54K.N7000ZSLM5
then i can use your method to root my Note Thank You very much!

can you post the list of all the bloatware apps.?

tangoscar42 said:
I am a beginner of rooting my Note. I have updated my Note to 4.1.2 from the Samsung Rom
I would like to ask if my note baseband version is N7000XXLSO and the build number is JZO54K.N7000ZSLM5
then i can use your method to root my Note Thank You very much!
Click to expand...
Click to collapse
Yes you can use. Better, download the zip version of the kernel LM5 to external sd and flash it using stock recovery to avoid yellow triangle.

tangoscar42 said:
I am a beginner of rooting my Note. I have updated my Note to 4.1.2 from the Samsung Rom
I would like to ask if my note baseband version is N7000XXLSO and the build number is JZO54K.N7000ZSLM5
then i can use your method to root my Note Thank You very much!
Click to expand...
Click to collapse
Yes, you can use my method very safely to root your device.

nokiamodeln91 said:
Yes you can use. Better, download the zip version of the kernel LM5 to external sd and flash it using stock recovery to avoid yellow triangle.
Click to expand...
Click to collapse
I have updated the OP with your word about the .zip version of the Kernel file, should have included it in the first place, thanks a lot lad.

YuE0529 said:
can you post the list of all the bloatware apps.?
Click to expand...
Click to collapse
There are many, But I will tell you which ones I removed:
Google+
Google Magazine
Google Movies
All German Apps
Allshare Play
Music Hub
Video Hub
Readers Hub
Learner Hub
Crayon physics
Polaris Office
Maps (I like to download latest one from Market as this one is old )
YouTube (I like to download latest one from Market as this one is old )
Swype Keyboard
Those all That I can remember at the moment.

Related

[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][SlimJB4.3][SGH-I757M][KERNEL]UNOFFICIAL SlimJB4.3 For Bell SGH-I757M

SlimJB4.3 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 Jellybean 4.3, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz6.07.9 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 SlimBean4.2, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D SlimBean4.3 (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). This is the latest SlimBean4.3 and has all of the features of a SlimRom that you've come to love. Don't forget to download the special gapps package to get the full SlimBean experience while using "The Real Dark Slim" feature.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THE PAGE
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera
* 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. You can still view these mp4 files, but you must open them with a file manager directly into the video player instead of using the gallery to access them.
* The camcorder records just fine, but when playing back the video, it's just a distorted video. Audio is fine, and I have not tested video with a third party app. If you test one and it works, please post that here so that others may benefit from your findings.
This seems to have been fixed as of the 20140121 build
* The latest Google Drive seems to be missing classes and will not open. This may be due to a missing content provider or may be a bug with the Google Drive app itself.
Solution: The solution for this is to uninstall the latest version of Google Drive, then go to Settings -> Security and enable Unknown Sources. Then open the Play Store and turn off automatic updates or it will end up overwriting the older version and you will be left with a non-working Google Drive again. Once all that is complete, download and install this Google Drive instead:
com.google.android.apps.docs.apk (8.4MB)
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 or Philz Advanced/Touch Recovery flashable zip which is compatible with SlimBean4.2/SlimBean4.3
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (or the Philz one) 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: 20140121 (Latest)
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20140121-0353.zip (114MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20140121.zip (147.3MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Build: 20131228
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20131228-1427.zip (126.1MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20131228.zip (160.4MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with SlimBean4.2/SlimBean4.3/SlimKat
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 SlimBean4.2/SlimBean4.3/SlimKat
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 SlimBean4.2/SlimBean4.3/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]January 21, 2014 - Build 20140121[/B]
* Synced with upstream sources (CyanogenMod/SlimRoms)
* Added SystemUI memory management fix
* Removed 91fixoverlays init.d script as it's no longer required
* Implemented fix for the char dev driver - fixes the vibrator not loading on boot
[B]January 03, 2014 - Build 20131228[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
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. There is a script that has been included with this ROM in the init.d that sets that on every boot so you shouldn't have to.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* SlimRoms Team - ROM Base
Without all of the hard work and efforts of the SlimRoms 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.
* @dsixda - Initial port of CM9/CM10 for SGH-I757M
* @Strange Peer - Continued development of CM10
* @rukusx7 - Contributor
* @bijon440 - Contributor
* @kj2112 - Contributor
* @Tronith - Contributor
* @Zippy Dufus - 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 SlimJB4.3 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: SlimBean
Version Information
Status: Alpha
Created 2014-01-03
Last Updated 2014-01-23

Reserved

Yay a slim bean of 4.3! Woot.
Sent from my SGH-I757M using xda app-developers app

Hi Shouldn't this be in the development forum

Awesome! Was hoping for a new slim build! Thanks so much TF! Great job!
Sent from my SGH-I757M using xda premium

68544455 3521
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..

Hey
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!

JayR_L said:
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..
Click to expand...
Click to collapse
I'll add back the mdnie settings. They are supposed give you control of the temperature
GrAt_On said:
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!
Click to expand...
Click to collapse
Only difference is in features and it's been slimmed down.Other than that, it's the same ROM. I just posted it for those who like the slim features check this page out for the list of slim features:
http://www.slimroms.net/index.php/slim-bean-features
Sent from my SGH-I757M using XDA Premium 4 mobile app

The Iron Man said:
Hi Shouldn't this be in the development forum
Click to expand...
Click to collapse
I've only posted or ROM's here since that's where dsixda was told to post them back when he started with this device. If the mods would prefer I post them in the dev section, I'm more than happy to oblige
Sent from my SGH-I757M using XDA Premium 4 mobile app

Amazing
I just flashed it, its amazing! Especially "The Real Dark Slim"! However, I did notice Google + doesn't work properly asking me to re install it at the play store. Had to uninstall using Titanium Backup and then install it back via app store, not sure now whether it has the the real dark slim feature integrated in google +. Other than that, it's really smooth so far Great port.
UPDATE: Google drive also doesn't work as it force closes continuously even after wiping dalvik's cache. I'll try redownloading the gapps tomorrow, might have a corrupt downloaded file.

I Fashed latest slim as well. It is running really well so far. I had the same issue with Google+ until I uninstalled using TB then reininstall from play store.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

Can confirm issue with Google+..
Thank you t_f for looking into mdnie. Also, flashing the unmodified lock screen handle available on Slim's website did not work, I still see the Slim logo. Aaah I wish I had time to figure out the android build environment.. I mean its probably just ant lol
Sent from my SGH-I757M using Tapatalk

I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

manfromgta said:
I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
It is intentional. Disabling the hw overlays is a performance hit, and it seemed that slim didn't need that hack because the overlays are working correctly
I know, the latest ROMs are running smooth and battery is much better since I tweaked the kernel for both.
I'm also really enjoying my new computer so much that I'm playing with paranoid android too. Got it booting with a bunch of hacks and to my suprise, it's running quite well. I'll post that after I test it more and clean up the build process. Then we have choice of which ROM too use. That was the problem before, no choice strange though, there is no branch for kk in paranoid android's repo.
Sent from my SGH-I757M using XDA Premium 4 mobile app

Just a word of caution to everyone using philz latest 6.07 cwm recovery. There is a know issue where the update-binary has now been updated as of kk and the recoveries built with kk like the new philz 6.07 are now giving assert errors (error 7).
There are two ways to fix this:
1) Revert to the older 6.01 version of philz.
2) extract the updater-script from the rom zip file, delete the assert lines and replace the old updater-script with the new one.
If you're new to all this, or consider yourself inexperienced, I recommend you go with option 1 and revert to the older philz as it's a less risky method of doing things
Sent from my SGH-I757M using XDA Premium 4 mobile app

Here's the link to the older philz 6.01. You can use either the 6.01.0 or 6.01.2.
http://d-h.st/users/philz_touch/?fld_id=29076#files
Sent from my SGH-I757M using XDA Premium 4 mobile app

Please check out this post if your not flowing the 10.2 thread and provide your opinion if you have one
http://forum.xda-developers.com/showthread.php?p=49171164
Sent from my SGH-I757M using XDA Premium 4 mobile app

ParanoidAndroid for SGH-I757M Released
Alright, for those of you who are waiting for my PA build, it's up. This is a JB4.3 build of ParanoidAndroid and I have added back the performance settings from CM to allow changing the governor and io scheduler as the defaults have sucky performance.
[ROM][PA-JB4.3][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M
Enjoy!!!

It's saying that slim isn't rooted?

[ROM][DEV][CM11.0][KERNEL][SGH-I757M]UNOFFICIAL CM11.0 For Bell SGH-I757M

CM11.0 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.51) 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 CM11.0 (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.
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 on 1080, swith it to 720 for recording)
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
* USB Mass Storage (UMS)/MTP
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.
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
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the philz_touch_6.12.8-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: 20141122 (Latest)
ROM: cm-11-20141122-UNOFFICIAL-celoxhd.zip (213.2MB)
PA Mini GAPPS: PA Mini Modular GAPPS
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
Build: 20140910
ROM: cm-11-20140910-UNOFFICIAL-celoxhd.zip (211.3MB)
PA Mini GAPPS: PA Mini Modular GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
DADOES ROM:
Build: 20140424
ROM: cm-11-20140424-DADOES-UNOFFICIAL-celoxhd.zip (469.18MB)
GAPPS: INCLUDED
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.12.8 (CWM 6.0.4.7) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* I no longer upload files to XDA because it takes way to long to manage, so I only use androidfilehost.com. All files can be found under my profile: https://www.androidfilehost.com/?w=files&flid=7547
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 22, 2014 - Build 20141122[/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.
[B]September 10, 2014 - Build 20140910[/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 15, 2014 - Build 20140815[/B]
* Sync with sources
* Added sysfs interfaces for vibrator intensity
* Added Settings in Advanced Device Settings for vibrator intensity
[B]July 11, 2014 - Build 20140708[/B]
* Sync with sources (Update to Android 4.4.4)
* Vibrator module now built into kernel
* Added sysfs for vibrator intensity to allow user control of the vibrator intensity
[B]May 21, 2014 - Build 20140321[/B]
* Sync with sources
* Switched to using media-caf
* Updated kernel with sources for media-caf
* Fixed issue with Google Camera resolution preferences FC
* Added back 91fixoverlays script due to graphics glitches with the new kernel
[B]April 10, 2014 - Build 20140410[/B]
* Synced with sources
* Added USB Mass Storage Mode (UMS)
* Fixed network type selection menu. It now includes LTE as an option.
[B]March 29, 2014 - Build 20140329[/B]
* Synced with sources
* Added overlay items to enable homescreen/lockscreen rotation
* Set Camera as default Scene Mode to partially fix camcorder recording
* cherry-pick display-caf commits to fix some of the graphical glitches
[B]March 21, 2014 - Build 20140321[/B]
* Sync with sources
* Remove 91fixoverlays script
[B]February 6, 2014 - Build 20140206[/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
* @Sultanxda - Many bug fixes and improvements for the msm8660 kernel
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 CM11.0 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: CyanogenMod
Version Information
Status: Alpha
Created 2014-02-06
Last Updated 2014-11-24

Tips & Tricks
Tips and Tricks
Here are my settings for the color/gamma controls!
Color:
Red -> 60%
Green -> 45%
Blue -> 45%
Gamma:
Red -> 0
Green -> -5
Blue -> 5
Why does the color/gamma controls get set to a value other than what I've set?
This is something I have not yet resolved, but I have noticed that it seems to jump up by 5. So if you want 50% for example, try setting it to 45%.
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
How do I take a dmesg (kernel log)?
It's fairly simple, open up your terminal then type the following:
$ su
$ dmesg > /storage/sdcard0/dmesg.txt
Click to expand...
Click to collapse
This will save the log to the root of your sdcard as dmesg.txt. Just post that or send it to [email protected] if it's to large to post here
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.

Flashing Recovery for the First Time
Flashing CWM for the First Time
This is a pretty simple step once you get past the install recovery script which I'll explain how to accomplish. Make sure you follow the instructions closely because Odin, the program the we use to bypass the security, can do some serious damage to your phone if your not careful.
1) Download the latest CWM tar.md5 to your computer from my androidfilehost.com repo here:
http://www.androidfilehost.com/user/?w=settings-dev-files&flid=12461
2) Download Odin 1.8.5 zip and extract all the files to a folder on your computer (i use my desktop):
http://www.androidfilehost.com/?fid=23501681358544719
3) The drivers are very touchy on windows computers, so I recommend that you install Samsung Kies which will ensure that the drivers are installed and setup correctly. You can download kies from here:
http://www.samsung.com/ca/support/usefulsoftware/KIES/JSP
4) Be careful now that you have kies installed, it does not play nicely with Odin, so whenever you use Odin, you should ensure that kies is completely closed and not open in the system tray by opening your Task Manager and "End Task" to any kies process such as "Kies.exe" and "KiesTrayAgent.exe"
5) Now, with kies closed, open Odin and do not change any settings. It should look like this:
6) Now click on the Bootloader button and search for the CWM tar.md5 you downloaded from my androidfilehost.
7) Now turn off your phone, and when it's powered off, press and hold the volume down and power buttons at the same time until you see the warning message about Download mode. Press volume up to enter download mode.
8) With Kies closed on your computer and Odin open cwm tar.md5 loaded into the bootloader section and your phone in Download mode, plug your phone into the computer with your micro usb cord and wait for odin to display a "Device Added" message which tells you that odin sees your phone.
9) This is the tricky part and is all based on timing, so pay close attention.
10) You will now press the "Start" button in odin and wait for it to complete. It will display a green "Pass" message in the first box when it's done. At this time, the phone will reboot and will start with a slight vibration to notify you that it's booting up. It's exactly at the time that the phone vibrates that you need to immediately remove the micro usb cord and press and hold the volume up and volume down buttons simultaneously until cwm loads. If you miss this mark, android will boot, the install_recovery.sh script will run and overwrite the cwm you just flashed with the old stock 3e recovery (arghhh) and you will have to go through this process again.
If CWM complains about the install_recovery script, let it fix/remove it.
Once you have CWM flashed, you can use it to backup/restore your system, flash custom ROMs and you can even flash our CWM upgrades through CWM itself.

First Wood Woot !! And many thankyous.
Update-
This Rom is flawless so far. I have no issues that existed for me in CM10.2JB . Status Bar doesn't freeze. Apps aren't killed mid use. Calender sync was fixed by installing Google calendar from play store and then removing it. (I use Cal app). There's almost no lag in multi tasking. I'm very happy.?? kit Kat!
Let's all hit TFs donate button with a few bucks, eh?

Much appreciated. Downloading now.

Sweet, a thread here instead of g+!
Sent from my SGH-I757M using xda premium

For me the gallery issue was gone after switched to the next branch.

Crossbreeder won't install (it did on the earlier 4.4 builds).. but Adaway works just fine and everything's working smoothly. Love the music in the lockscreen! also noticed there's even more governor parameters to tweak, which is always a good thing

formercontra said:
Crossbreeder won't install (it did on the earlier 4.4 builds).. but Adaway works just fine and everything's working smoothly. Love the music in the lockscreen! also noticed there's even more governor parameters to tweak, which is always a good thing
Click to expand...
Click to collapse
That's due to the new recovery. If your on a Windows system, download 7zip if you don't have it already.
Here's what you do, open this roms zip file and extract only the update-binary from META-INF/com/google/android to a location on your computer. Then you can close the ROM zip. Now open the crossbreeder zip with 7zip and browse to META-INF/com/google/android and simply drag the extracted update-binary into the crossbreeder zip file replacing it's update-binary with the one from cm-11. Then close the zip and upload to your phone and flash away
Sent from my SGH-I757M using XDA Premium 4 mobile app

After running ROM for a few hours, I'm quite impressed. No issues so far. I will continue using it and report any findings. Thanks titanic for all your time and effort.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

Phone won't boot
I flashed the rom and the gapps but I get no boot screen. I waited about five minutes and nothing happened. Any ideas on what went wrong??

Amazing
It's is so smooth, I am ecstatic to see how it'll be when ART becomes functional!
Thanks again!

omar.kassam97 said:
I flashed the rom and the gapps but I get no boot screen. I waited about five minutes and nothing happened. Any ideas on what went wrong??
Click to expand...
Click to collapse
Did you wipe and factory reset? Did you use the wipe to install new rom option?
This ROM must be flashed clean. No dirty flashing unless you already had cm-11 flashed.
Sent from my SGH-I757M using XDA Premium 4 mobile app

I am curious, in your 10.2 thread you said the calendar could not be assigned a gmail account in cm 11.
Was this resolved? For me it's a deal breaker (loving your cm10.2 anyways).
If it hasn't been fixed could we add it to the OP in the what doesn't work section?
Sent from my SGH-I757M using xda app-developers app

slushee said:
I am curious, in your 10.2 thread you said the calendar could not be assigned a gmail account in cm 11.
Was this resolved? For me it's a deal breaker (loving your cm10.2 anyways).
If it hasn't been fixed could we add it to the OP in the what doesn't work section?
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
No, it's unfortunately not fixed and will definitely add that to the op
Sent from my SGH-I757M using XDA Premium 4 mobile app

Way to go Titanic! I will flash tomorow and try this one out.
Sent from my SGH-I757M using xda app-developers app

Philz touch cwm was just updated and now uses a new exfat module for mounting the sdcards. It's supposed to be faster than the fuse alternative. This version also fixes the resolution of the background image, the software buttons and the vibration.
http://forum.xda-developers.com/showthread.php?t=2552634
Sent from my SGH-I757M using XDA Premium 4 mobile app

The calendar works in slim. I think the calendar sync adapter is missing in cm-11. Can I get someone to add this apk to your /system/app dir give it the same permissions as the others, then reboot and try connecting the calendar to your Google account. I'm out of the house right now so can't test it myself.

titanic_fanatic said:
The calendar works in slim. I think the calendar sync adapter is missing in cm-11. Can I get someone to add this apk to your /system/app dir give it the same permissions as the others, then reboot and try connecting the calendar to your Google account. I'm out of the house right now so can't test it myself.
Click to expand...
Click to collapse
Yep, that worked. My Google account syncs now and i can create events. Thanks TF!
Sent from my SGH-I757M using xda premium

bijon440 said:
Yep, that worked. My Google account syncs now and i can create events. Thanks TF!
Sent from my SGH-I757M using xda premium
Click to expand...
Click to collapse
Excellent, I'll update the gapps package when I get home thanks for testing
Sent from my SGH-I757M using XDA Premium 4 mobile app

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

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

AOKP 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.13.2(based on CWM 6.0.47) 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
AOKP is a fork of AOSP with many custom additions implemented by the AOKP team. It features most of the same functionality as CM-11.0 with custom features.
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.
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new Philz Touch Recovery 6.13.2 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.13.2-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: 20140817 (Latest)
ROM: aokp_celoxhd_kitkat_unofficial_2014-08-17.zip (180.4MB)
GAPPS: aokp-mini_gapps-kk-20140528.zip (75.1.4MB)
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: 20140412
ROM: aokp_celoxhd_kitkat_unofficial_2014-04-12.zip (169.3MB)
GAPPS: gapps-kk-20140321.zip (141.4MB)
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]August 17, 2014 - Build 20140817[/B]
* Synced with sources
* Added sysfs interface for vibrator intensity control
* Added settings to control vibrator intensity in Advanced Device Settings
* Added Omni Performance Control
[B]April 12, 2014 - Build 20140412[/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:
* AOKP Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod/AOKP teams, 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
* @manfromgta
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 AOKP KK4.4 For Bell SGH-I757M, ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic, manfromgta
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-04-13
Last Updated 2014-08-18

Downloaded and clean install. Went without a hitch including TB app restore. I will let it settle in and report any findings. Thanks Tyler for everything!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

Is AOKP better than CyanogenMOD at this moment? or What is your opinion?

Screambloody said:
Is AOKP better than CyanogenMOD at this moment? or What is your opinion?
Click to expand...
Click to collapse
AOKP has the same performance as my other ROMs. It just had different features, some of those are included in other ROMs too like carbon.
My favorite ROM is still carbon, I just want to provide others with a choice of what ROM to run. You can always test it out and restore a nandroid if you don't like it
Sent from my SGH-I757M using XDA Premium 4 mobile app

titanic_fanatic said:
AOKP has the same performance as my other ROMs. It just had different features, some of those are included in other ROMs too like carbon.
My favorite ROM is still carbon, I just want to provide others with a choice of what ROM to run. You can always test it out and restore a nandroid if you don't like it
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks,I'll test this ROM,but,is Carbon more stable than AOKP,CyanogenMOD 11 and Slimkat?

Screambloody said:
Thanks,I'll test this ROM,but,is Carbon more stable than AOKP,CyanogenMOD 11 and Slimkat?
Click to expand...
Click to collapse
No, I just prefer the features that carbon has implemented. Some from cm, some from aokp and some from slim. For me it's the best of all 3 And now I'm playing with the idea of permanently implementing Slim's recents app since I really like it.
Sent from my SGH-I757M using XDA Premium 4 mobile app

Been running this for a few days. Going to try ART later. Excellent job! :good:

I got stuck at the boot animation for almost 15 minutes when I enabled ART . Luckily I had a backup. Oh well, rom is still fantastic.

iDynamics said:
I got stuck at the boot animation for almost 15 minutes when I enabled ART . Luckily I had a backup. Oh well, rom is still fantastic.
Click to expand...
Click to collapse
When this happens, you can boot into recovery, then use the console I'm aroma filemanager and ruin this command:
$ echo "libdvm.so" > /data/property/persist.sys.dalvik.vm.lib
Click to expand...
Click to collapse
Of course you need to mount the data partition before you open the console
This will switch you back to dalvik
Sent from my SGH-I757M using XDA Premium 4 mobile app

titanic_fanatic said:
When this happens, you can boot into recovery, then use the console I'm aroma filemanager and ruin this command:
Of course you need to mount the data partition before you open the console
This will switch you back to dalvik
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks.
I used this to switch back.
http://forum.xda-developers.com/showthread.php?t=2713622

I have a new build of AOKP running right now Hope to post it by the end of the night!

Will the fixoverlays script be needed for this build?

iDynamics said:
Will the fixoverlays script be needed for this build?
Click to expand...
Click to collapse
I assume so, but am not entirely sure until I test it out
Sent from my SGH-I757M using XDA Premium 4 mobile app

There was a whole bunch of build errors when I got home it seems that I synced between important commits that caused the build errors. It's now back to building, and the good news is that I incorporated omni performance controls into this build instead of cm's.
Also, this will be the first of the 4.4.3 builds
Sent from my SGH-I757M using XDA Premium 4 mobile app

titanic_fanatic said:
There was a whole bunch of build errors when I got home it seems that I synced between important commits that caused the build errors. It's now back to building, and the good news is that I incorporated omni performance controls into this build instead of cm's.
Also, this will be the first of the 4.4.3 builds
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looking forward to it

Just fyi, the build is done, but untested because sultanxda posted his fix for the graphical glitches and I've didn't all day porting over those changes to our kernel. I'm working through build errors right now, but hope to test tonight. If anyone is brave enough, your welcome to test the aokp I built, just let me know and I'll upload otherwise, I'll test it after I get this kernel tested out
Sent from my SGH-I757M using XDA Premium 4 mobile app

I'm down for testing.

iDynamics said:
I'm down for testing.
Click to expand...
Click to collapse
Cheers, so I'll upload the zip right now. When it's done, I'll post the link with specific instructions on what to test and how to test it
The only time it becomes really difficult to test and get useful loss if needed is when either it bootloops or android doesn't load. I'll explain how to overcome these situations when I post instructions.
Thanks for the help and support
Sent from my SGH-I757M using XDA Premium 4 mobile app

iDynamics said:
I'm down for testing.
Click to expand...
Click to collapse
alright, it's uploaded to my Aokp folder inside another folder called test.
Flash as usual taking your necessary backups beforehand
Then, first I need you to test if the overlays script is still needed. To check this, go to developer options and uncheck the disable hw overlays checkbox, then pull down the notification shade and if the background goes immediately black instead of starting to dim then it's still needed so disable it again. If that check passed, go to the Homescreen by pressing back and make sure there is no flicker and that the background never goes black. This must be the same for the Homescreen as well, the background cannot go black. If it doesn't then you can open a browser instance and browse to review.cyanogenmod.org specifically and use the input field in the top right corner, this causes the view to zoom and also the keyboard to appear. If nothing happens, click outside of the input field to hide the keyboard or press back one time to do the same and then back into the input field again to pull up the keyboard. Do that allot and if the glitching still remains, this will cause lots of glitching and a reboot.
With that all tested, make sure that the performance settings work as I ported omni's performance control from my carbon build.
Also make sure to check the version information.
Ok, pay close attention here. I know you know how to take a logcat, that's the easy part. What to do if you get a bootloop, this is the tricky part. You must watch the phone boot up the first time which usually takes 130 seconds give or take and depending on the rom. Getting a kernel log can be difficult when in a bootloop because it's cleared each time the phone boots, well that's not useful is it here's the trick, and why you need to watch the bootup. As soon as the phone bootloops, there will be the initial vibration that signifies the device is booting up, you need to press and hold only your volume up and volume down buttons as soon as you feel the vib until you get into cwm. If it boots past into the bootlooping android then the log is gone and you need to try the process again.
Once you get into cwm, open aroma filemanager by double tapping the empty space at the bottom of the menu. Make sure aroma options are set to mount everything and show hidden files. Now browse to /proc and scroll down to the files until you find last_kmsg and copy that file to a spot on your sdcard which you will need to access through /storage/sdcardX where X represents 0 for internal or 1 for external sdcard.
This log is what I would need to see to fix a bootloop let me know if anything doesn't make sense
Sent from my SGH-I757M using XDA Premium 4 mobile app

I will download and test today.
Ok. I downloaded and flashed but i can't get to developer options. I did the tapping in about phone as usual but it does not enable options.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

Database Users

welcome