Although the Xiaomi Mi 2 is almost five years old, and it seems there would never be a working nougat/oreo ROM after ivan stopped the development of his AOSP project, but it's not the truth. As the issue of light and proximity sensor have been fixed, I think most of the system components are stable enough for dialy usage after my couple days tests, so I decide to release the AOSP 8.0.0 to you today.
Install:
Please make sure your phone haven't modified the stock partition. It means my rom only work with the latest miui-dev partition table, so you have to Download lastest Mi 2 Developer tar file and flash using fastboot before install my oreo/nougat ROM . This process will earse all data on you phone, so backup all data before you getting start.
1. flash stock miui developer by fastboot update (http://en.miui.com/a-234.html)
2. flash twrp recovery use fastboot and reboot
3. hold power and volume up key to boot into recovery mode
4. install oreo or nougat ota package
5. wipe data and cache (you have to do this even if you are using ivan's aosp marshmallow/lollipop)
Working:
(Note: I use Mi 2SC with CDMA network support, but I don't have an available CDMA SIM card right now for test, so users with CDMA network might have trouble with RIL)
- Audio (bluetooth headset not test)
- Bluetooth
- Camera
- RIL
- WIFI
- FM
- Sensors
- GPS
Credit/Thanks
Special thanks to ivan for the initial device source tree and his preview works on Mi2 device.
Many Thanks to @AdrianDC @Ziyan for their great work to bring Android Oreo to MSM8960 platform.
Also thanks to @m11kkaa (M1cha) @zaclimon for their projects.
- Xiaomi Opensource Project
- Google Android Opensource Project
- Team LineageOS/CyanogenMod
- Team Omnirom and Team TWRP recovery
- Team Unlegacy Android
Source:
device tree: https://github.com/windbellx/android_device_xiaomi_aries
https://github.com/windbellx/android_device_xiaomi_msm8960-common
kernel source: https://github.com/windbellx/android_kernel_xiaomi_msm8960
vendor: https://github.com/windbellx/proprietary_vendor_xiaomi
Screenshot:
Download
https://mega.nz/#F!naRFGQDR!d9Uv-Maw56vyYsphAj00Kw
Known issues
1. APN needs setting manually to use CDMA data network. (?, not sure, need more tests).
2. Selinux status is on permissive status.
Root
1. download all files under superuser
2. reboot to fastboot, flash boot.img
Code:
fastboot flash boot boot.img
3. boot into recovery, mount /system, push su binary and superuser.rc to your phone
Code:
adb push su /system/xbin/su
adb push superuser.rc /system/etc/init/
4. reboot
Gapps
select one way of below
1. flash MindTheGapps-9.0.0-arm-20181119.zip
2. download OpenGapps Pico (Not support other version due to limited space of /system
upload gapps-config.txt and opengapps zip file to the same folder and flash opengapps
Changelog
2019-01-01
* fixed wrong 1080p parameter in AOSP camera, both rear and front camera support 1080P record now.
* fixed wifi hotspot and usb tethering cannot open.
* fixed echo reappear after first call.
* rebase kernel, improve wakeup speed and stability.
* add percent text for offline charging.
* reimport MHL releted code, try to bring up MHL. (not tested)
* QS UI improved for small-size screen.
* keep the crypto name same with AOSP, try to make disk encryption work. (not tested, format /data and storage before encryption if too many files, or get out of memory error and system reboot).
* stop maintaining this device if no critical bug in this update.
2018-11-19
-> Upgrade to Android Pie(CAF 9.0.0), tag: LA.UM.7.2.r1-05300-sdm660.0
-> Features added:1. Privacy Guard(with optional su support, thanks LineageOS)
2. App Firewall(data, wlan and vpn, thanks LineageOS)
3. Showing Network Speed(thanks Jon Haus, ezio84 and other commiters)
4. Launcher with icon pack support(thanks tfitts1212, maxwen, eldainosor and other commiters) -> Fix hidden wireless connection
-> Add DRM support (For Netflix, L3 level, not support HD and higher)
-> Try to fix echo in calls again(not tested, report if not working)
===========================================================
Android Nougat/Oreo start
Download Link:
Only twrp >= 3.2.1 works with ROM >= 20180101
https://mega.nz/#F!VKRggSoL!WAFIK45_IFKhnvlK1eyY4w
Known issues:
1. Hidden network cannot connect.
2. APN needs setting manually to use CDMA data network. (?, not sure, need more tests).
3. Not support 1080P camera record due to outdated kernel driver.
4. Selinux status is on permissive status.
Changelog:
2018-11-01
* md5sum: b957fa0274819a09fd81d2af2958cc69
* echo in calls should fix now, only tested VOIP, need more tests(headset, bluetooth etc).
* with echo fixed, an issue related ES310 chip sleeping that make battery draining fast is also fixed.
- Standby battery time estimate: > 5 days.
- Normal Screen on usage: 5~6 hours.
2018-10-21
*md5sum: 8cbfdceb23c3aa6f382f1a9a79c29004
* fix noise in headset mic
2018-10-19
* md5sum: 9304de676e0dd6428db566b072488e3f
* fix echo audio during calls
* performance tweaks, fix too hot when too many heavy background tasks, now enable all 4 cpu cores by default
* HALs and blobs changes prepare for P
2018-09-01
* md5sum: b7e60c0033b526278468a38cb00f373e
* minor updates and stability improved.
* last update as I'm going to remove all 8.1 source, source will update to github as soon as possible.
* I will try to bring up pie once I get free, but no guarantee and no ETAs.
2018-06-16
* md5sum: da677903b4c5092d57e91f0dc2210a90 aosp-caf-8.1.0-20180616-aries-arch.zip
* bring back Privacy Guard and synchronize to latest LineageOS version.
* fixed sometime the device is too hot while too many background apps and optimize screen-on battery usage.
full battery usage estimated:
>5 hours online surfing with wifi opened(moderate usage, no gaming).
2 days standby (45-50 hours).
3-4 hours(?) using cellular data.
2018-05-06
* md5sum:
- b7121d3f95e91350722da01c8dfdea22 aosp-caf-8.1.0-20180506-aries-arch.zip
- 6988262c9f99c00371a1bc238ffbdf26 aosp-caf-8.1.0-20180506-aries-arch-gapps.zip
* fix gps and compass broken in last build.
* revert media profile changes so screen record now works normally.
* bring back Xiaomi usb otg driver. (Not tested, tell me if it not work)
* enable doze correctly.
* reduce battery usage when WIFI turned off.
* thermal and some kernel tweaks.
2018-04-20
* md5sum: e8fc7f3793d820f279580726f2c34e93 aosp-caf-8.1.0-20180420-aries-arch.zip
* this version is NOT compatible with previous ROM, SO CLEAN DATA/CACHE OPERATION IS REQUIRED.
* switch to CAF source(tag: LA.UM.6.6.r1-07200-89xx.0) instead of Google generic repository. This build contains Qualcomm specific enhancements plus some comunity optimizations, so it gives some improved performanence to this old device (especially pictures slipping and system animation). Thanks to AOSPA and AOSP-CAF.
* fix WiFi hotspot, tethering should work fine now.
* fix audio call volume cannot adjust.
* add firewall(app wifi/data restriction) support to oreo(App info -> Data Usage -> Disable all cellular data access/Disable all Wi-FI data access). Port from Lineage/CM, thanks again for their great works.
* add multiple pointers patch.
* add fake signature patch, for some MicroG users.
* update media profiles, remove 1080p option from camera records.
* now the build type is "user", which will disable adb debugging by default, "adb root" also disabled.
* repatch telephony framework for CDMA users(NOT TESTED).
* it's the final update if no serious issues(this update is to resolve the call volume issue).
2018-03-17:
* This version is expected to be the final version and wouldn't update anymore if no critical issues. I hope you can enjoy this one without obstacles. Source will be updated to github in a few days.
* update to 8.1.0_r17
* update audio configuration files so audio should work flawlessly now.
* update power hal and tweak cpu scheduler, try to make a better battery life.
* remove Privacy Guard (seem have unnormal power usage when data connection opened), revert Apps data path tweak, remove addtion Internet/Sensor permissions(it makes Google Setup Wizard FC).
* fix device hangs while trying power on machine in offline charging mode.
2018-01-27:
(NOTE: new kernel might have problems with some device, please attach your logcat, dmesg and top command result(adb shell -> top -> take a screenshot), plus you device model)
(NOTE 2: If you have installed gapps and don't want to clean data, flash gapps after flash the new ROM, before your first boot, or some app will get a FC, unless reinstall the app)
* Revert to old audio hal so that calling audio works with old configs
* Fix some storage access permission issues. Move all Apps data to /sdcard/AppData, so external storage path that apps got will be /sdcard/AppData/<package name>/
2018-01-19:
* fix system crash when openning gps with IPv6 network
* fix the audioserver crash when using a headphone
* fix app crash when not granted WRITE_STORAGE permission
2018-01-17:
* update to 8.1.0_r7
* switch to new kernel base. After almost one month dialy use test, I decide to abandon the old kernel tree and enable new kernel source tree, so Xiaomi aries now share the same kenel base code with sony huashan(https://github.com/AdrianDC/android_kernel_sony_msm8960t). Adrian DC have been working on AOSP/LineageOS of Sony msm8960 platform for a long time, he also is a recognized and trusted developer of LineageOS. With new kernel, I believe it will be more quickly to bring a features-ready and more stable aries ROM to you. Thanks @AdrianDC for his great work.
* switch to new audio/display/media HAL, report if you have any trouble to aduio, video play and records.
* new kernel support new auto sleep and wakeup (instead of earlysuspend), and many other changes to improve deep-sleep in oreo, so it will be a better battery life when phone is idle.
* adopt some code from Lineage to support CDMA data connection. if you want to report RIL releated issues, please attach both full logcat(adb logcat) and radio logcat(adb logcat -b radio)
* fix power menu not shows correctly
* fix some app cannot open again after force stop
* make lockscreen swipe more easier to unlock
* magisk now can boot properly
2018-01-01:
* fix UI performance. (NEED MORE TESTS)
* port Privacy Guard to aosp-8.1, thanks to team Lineage/CM/SlimROMs (Settings > App & notifications > Privacy Guard)
* superuser now is optional
* isolate app data/files on /sdcard (app now saved data to /sdcard/<package name>/ install of /sdcard/, It make external storage root more neat and more secure in some cases)
* fix alarm not work
* disable permission review, or permissions will reset after every updates
* disable liveshot in case of crashing when touched in video record mode
* secondary try to fix CDMA data connection. (Need feedbacks, plus model)
* fix setting lockscreen pin/pattern nonresponse
* update battery data, try to fix battery value reset. (NEED TEST and FEEDBACK)
* update twrp to 3.2.1
2017-12-09: (Download from here #65)
* Update to 8.1.0_r1
* Enhance security and privacy settings (many thanks to thestinger and CopperheadOS)
** I have added Internet permission and enable permission review for app with targetSdkVersion < 23, If you are not a clean installation, some app might get a FC. Reinstall app and give the permissions(PHONE OR INTERNET) can solve problem.
* Fix Mi2s 32gb with 13MP camera. (NEED TEST)
* Revert kernel gpu driver. Try to solve UI unsmoothly sometime. (NEED FEEDBACK)
* Add CDMA dummy APN patches. Try to solve data connection with CDMA network. (NEED TEST)
* Use old power and charger driver. It works better.
2017-11-19
* initial 7.1.2 and 8.0
Download: OUTDATED! FIND UPDATES FROM CHANGELOG
twrp recovery 3.1.1: https://mega.nz/#!RewDnB5Z!1JaIxJ2-wQpd9BmY1MoqIrt0z9rI2pLg6lKL5Z2lsKg
aosp 8.0.0: https://mega.nz/#!FHpTRCQL!j_Z-XirV12iPhxmnIAWA33W5HB1ca0Mep8lsKSiB10g
aosp 7.1.2: https://mega.nz/#!hTIgGT5a!gfap1JU95VeyfYauYcvlaR-VnHwRLRzklLENMwS2jgs
Great!:highfive:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
lol，cdma 1x can be load ，but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
huo zhuo huda
ziiimy said:
lol，cdma 1x can be load ，but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
huo zhuo huda
Click to expand...
Click to collapse
You are the first one to make the ril work after M. I think this is exciting.
great！
Can't not connected to hidden WiFi
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
Yes
ziiimy said:
lol，cdma 1x can be load ，but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
huo zhuo huda
Click to expand...
Click to collapse
Sorry, it wouldn't be fixed as I don't have a CDMA SIM card right now.
UI is very unsmooth. After installing gapps got 'setup wizard has stoped' error. Can it be fixed?
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
great my big brother
我是中国用户，小米2太厉害了，居然能用上功能正常的安卓8.0，感谢xda论坛
I am a Chinese user, millet 2 is too powerful, actually able to use the normal function of Android 8.0, thank xda forum
duplicated
-Tex- said:
UI is very unsmooth. After installing gapps got 'setup wizard has stoped' error. Can it be fixed?
Click to expand...
Click to collapse
if you open logcat and got error like this:
Code:
I zygote : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.NativeCrypto>: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/com.android.media.remotedisplay.jar", zip file "/system/framework/com.android.location.provider.jar", zip file "/system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk"],nativeLibraryDirectories=[/system/priv-app/PrebuiltGmsCore/lib/arm, /system/lib, /system/vendor/lib, /system/lib, /system/vendor/lib]]] couldn't find "libgmscore.so"
this is a temporary solution.
1. extract Phonesky.apk and PrebuiltGmsCore.apk from Core/vending-arm.tar.lz Core/gmscore-arm.tar.lz (320/priv-app/PrebuiltGmsCore) in opengapps zip file.
2. extract Phonesky.apk to Phonesky and extract PrebuiltGmsCore.apk to PrebuiltGmsCore use any zip software, or you can run:
Code:
unzip PrebuiltGmsCore.apk -d PrebuiltGmsCore
unzip Phonesky.apk -d Phonesky
the Phonesky and PrebuiltGmsCore folders should like this:
Code:
➜ ls Phonesky
AndroidManifest.xml
android-support-multidex.version.txt
assets
build-data.properties
classes2.dex
classes.dex
com
lib
libs
META-INF
org
res
resources.arsc
Code:
➜ ls PrebuiltGmsCore
AndroidManifest.xml
assets
build-data.properties
classes2.dex
classes3.dex
classes4.dex
classes.dex
com
googledata
HACKED-META-INF
lib
META-INF
org
res
resources.arsc
3. then, push the lib to your phone by adb:
Code:
adb root && adb remount rw
adb shell mkdir -p /system/priv-app/PrebuiltGmsCore/lib/arm/
adb push PrebuiltGmsCore/lib/armeabi-v7a/* /system/priv-app/PrebuiltGmsCore/lib/arm/
adb shell mkdir -p /system/priv-app/Phonesky/lib/arm/
adb push Phonesky/lib/armeabi-v7a/* /system/priv-app/Phonesky/lib/arm/
it should works now, tested with gapps nano.
It seem like an uncorrectly odex/install problem, I need more time to investigate it.
windbells said:
it should works now, tested with gapps nano.
It seem like an uncorrectly odex/install problem, I need more time to investigate it.
Click to expand...
Click to collapse
Should i do this after installing gapps or do it instead of installing gapps? What about ui smoothness?
-Tex- said:
Should i do this after installing gapps or do it instead of installing gapps? What about ui smoothness?
Click to expand...
Click to collapse
After installing and reboot to system.
If you are still facing ui Smith less after solve the gapps opening, try clean data and cache, if still exists, please attach logcat log and describe you r usecase in a more detailed way, and also, what's your phone model name? 2? 2S? 2S with 13m camera?
I just tried on my Mi2S 16G with 8MP camera,
Almost everything works well, but UI is very unsmooth.
I have 32GB with 13MP camera, but this is my daily use phone, so I don't want try on it.
Update:
I tried to grab logcat and dmesg to try to find the reason about UI unsmooth.
But the information is too much that I have no idea to find...
So I upload them to my mega.co.nz
logcat:
https://mega.nz/#!KYMVHByT!Mytx_PG8BqhOrMauhr-NtcsqO7Qw7RIw7i2ydJsNj-4
dmesg:
https://mega.nz/#!6UF30KRS!4qzlNs0UFMBHacNX_WsJIrlVmINNsqzVHCYAdkvkaAI
windbells said:
After installing and reboot to system.
If you are still facing ui Smith less after solve the gapps opening, try clean data and cache, if still exists, please attach logcat log and describe you r usecase in a more detailed way, and also, what's your phone model name? 2? 2S? 2S with 13m camera?
Click to expand...
Click to collapse
I will try tomorrow. My phone model mi2sc 16 Gb with 8m camera.
joe820730 said:
I just tried on my Mi2S 16G with 8MP camera,
Almost everything works well, but UI is very unsmooth.
I have 32GB with 13MP camera, but this is my daily use phone, so I don't want try on it.
Click to expand...
Click to collapse
It seems that my kernel not working on 13MP camera, according to the feedback.
I think Mi2S with 8MP camera should work fine as I using 2SC 16GB with 8MP camera. I think it's really smooth after had a data cleaned boot. Even after I installed the opengapps, it's smooth as usual. Can you describe you usecase or record a short video that shows UI stucked.
Related
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
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
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?
Carbon KitKat for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
*** Disclamer ***
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
Click to expand...
Click to collapse
*** NEW RECOVERY REQUIRED ***
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.
Click to expand...
Click to collapse
*** NEW RADIO FIRMWARE REQUIRED ***
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).
Click to expand...
Click to collapse
Introduction
We now have an AOSP (Android Open Source Project) ROM available for our beloved SGH-I757M. This one is called Carbon and boasts many features from CM/PA/Slim/AOKP. It features SlimPie, customizable ribbons, Active display, Screen Recorder, Screencast and more. Please check out the carbon features page for a full list:
Carbon ROM Feature List with Screenshots
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
* 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.
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 KitKat based ROMs
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. You can skip this step if 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: 20140125 (Latest)
ROM: CARBON-KK-UNOFFICIAL-20150125-1436-celoxhd.zip (178.2MB)
PA GAPPS: PA Modular Mini GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Build: 20141121
ROM: CARBON-KK-UNOFFICIAL-20141121-0351-celoxhd.zip (178.2MB)
PA GAPPS: PA Modular Mini 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
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.57.9 (CWM 6.0.5.1) compatible with KitKat based ROMs
[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
January 25, 2015 - Build 20140125
* Increased Kernel version to Titanium 1.2.1
* Added kernel based thermal mitigation sensor - credit: sultanxda
* GPU ion backport from LA.AF.1.1_rb1.7 - credit: sultanxda
* New Bluetooth/WiFi drivers ported from the S5 - credit: sultanxda
* Revert change to camera wrapper that cause photos to be taken in portrait
* Increase low power flash threshold to 60%
* Add Sweep2Sleep (S2S) - credit: Emmanuel U
* Add sensitive option for S2S/S2W - credit: Emmanuel U
* Add settings Advanced Device Settings to control the S2S and S2W/S2S Sensitive settings
* Add Enhanced BLN - credit: sultanxda
* Updated Advanced Device Settings to work with the new Enhanced BLN driver
* Add kernel tab to Advanced Device Settings for kernel control settings
* Moved panel UV setting to kernel tab in Advanced Device Settings
* Removed ROMStats and CarbonDelta since we don't use them and they only consume battery and network bandwidth
* Increased vmalloc size from 400MB to 512MB - credit: sultanxda
* Add Dynamic System Bars from Paranoid Android ROM
November 21, 2014 - Build 20141121
* 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.
NOTE: 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.
September 10, 2014 - Build 20140911
* 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: THIS POST
* Added the necessary audio channels in the audio_policy.conf for screencasting - credit: THIS POST
* 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
July 5, 2014 - Build 20140705
* 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
May 21, 2014 - Build 20140321
* Sync with sources
* Updated Slim Recents
* 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
May 04, 2014 - Build 20140504
* Sync with sources
* Add Slim Recents app (Long press home to show)
* Fixed gesture control for pinch to clear in Slim Recents panel
* Fixed HW Key binding (You can now set the actions for the hw buttons events like longpress)
* Fixed reading of min/max values for cpu in new Omni Performance Control
March 21, 2014 - Build 20140321
* Sync with sources
* Removed 91fixoverlays script
* Fix Settings button on Homescreen overlay
February 25, 2014 - Build 20140225
* 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
* CarbonDev Team - ROM Source
* CyanogenMod Team - ROM Base
* SlimRoms Team - ROM Features
* AOKP Team - ROM Features
* ParanoidAndroid Team - ROM Features
Without all of the hard work and efforts of the CarbonDev team, CyanogenMod team, AOKP team and the Paranoid Android 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 (Donated old phone for Development - Thanks!)
* @bijon440 - Contributor
* @kj2112 - Contributor
* @Tronith - Contributor
* @Zippy Dufus - 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
Click to expand...
Click to collapse
XDA:DevDB Information
UNOFFICIAL Carbon KitKat 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: AOSP
Version Information
Status: Stable
Created 2014-02-25
Last Updated 2015-01-26
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
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.
First! Running it for a bit thismorning and everything seems great. 1 thing, no halo? Not a big deal with the ribbons but I did like that. Good work! Ill buy you a beer yet my friend!
Sent from my SGH-I757M using xda premium
This ROM is the kats meow. Love the features. After a full days use, no lock ups, lag or random reboots. Its early yet for battery stats but so far with on demand/deadline combo I'm at 62% remaining after 15 hours of average use. One thing of note: From home screen- clicking menu/settings is not functional. Settings from app drawer works as it should. This ROM is now my daily driver. Thanks for the continued support. May the S2 live on!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
I might have to try this build out. Battery life is my biggest thing.
I found that deadline for a scheduler is best for this phone with almost any governor. I don't know why.
That's what I'm on, ondemand and deadline yeah, and I'm loving this ROM. It's got some pretty cool features
Sent from my SGH-I757M using XDA Premium 4 mobile app
this rom is great, i was just wondering whats the easiest way for me to leave hw overlays unchecked when loading os?
rukusx7, whats the likelyhood of you making an installable zip of your kernel?
ashfrel1984 said:
this rom is great, i was just wondering whats the easiest way for me to leave hw overlays unchecked when loading os?
Click to expand...
Click to collapse
You can remove the init.d at /system/etc/init.d/91fixoverlays
It will be really speedy after that, but you may still run into some graphics glitching. Possibly enough to cause the kernel to panic and reboot. You can always replace the script at a later time if that becomes an issue.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Took the plunge, just installed this tonight. Hope everything goes well!!
so far ive been lucky (no glitches), but what a speed difference for me. thanks for the info.
Without hw overlays enabled this rom most certainly speeds up. Great job as always t_f.
titanic_fanatic said:
You can remove the init.d at /system/etc/init.d/91fixoverlays
It will be really speedy after that, but you may still run into some graphics glitching. Possibly enough to cause the kernel to panic and reboot. You can always replace the script at a later time if that becomes an issue.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In my hellkat rom, this is usually green lines that glitch across the screen. I tend to have problems with RR's with Disable Hardware Overlays unchecked.
Have you made any major changes to the kernel to help with hardware overlays?
rukusx7 said:
In my hellkat rom, this is usually green lines that glitch across the screen. I tend to have problems with RR's with Disable Hardware Overlays unchecked.
Have you made any major changes to the kernel to help with hardware overlays?
Click to expand...
Click to collapse
No actually, so that goes to show that it might not be entirely related to the kernel which I originally thought the case. I'll have to diff cm with carbon to see what differences there are.
Sent from my SGH-I757M using XDA Premium 4 mobile app
iDynamics said:
Without hw overlays enabled this rom most certainly speeds up. Great job as always t_f.
Click to expand...
Click to collapse
Seriously, some devs had given up on fixing project butter, but I always impressed with what titanic_fanatic brings to our device!!! I might switch to this rom if it works so well. I'll do builds with DIABLO or UBER kernel perhaps, Also dont forget the work that TF is doing to his kernel as well. our kernel diff's slightly from the hercules and skyrocket (which mine is based on), and he will likely have a kernel that is tweaked specifically to our device.
Great work @titanic_fanatic!!
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
titanic_fanatic said:
No actually, so that goes to show that it might not be entirely related to the kernel which I originally thought the case. I'll have to diff cm with carbon to see what differences there are.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, I've been all stuck on the kernel as well. But I agree its starting to not appear as so. You're making some amazing advancements lately!!!
iDynamics said:
Without hw overlays enabled this rom most certainly speeds up. Great job as always t_f.
Click to expand...
Click to collapse
With your hw overlays disabled, do you get graphical glitching in the gallery? I get those lines rukusx7 was talking about.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Might have just found a really easy fix for the graphics glitching... FACE PALM Only time will tell though. Navigate to /system/lib/egl and edit egl.cfg. you will see this:
0 0 android
0 1 adreno200
Click to expand...
Click to collapse
Change this to:
0 0 adreno200
0 1 adreno200
Click to expand...
Click to collapse
This will force the device to always use adreno200 for graphics processing. I don't get those wavy lines in gallery anymore with hw overlays enabled, and I haven't had any screen flickering yet either. Not sure what this means for battery yet, but this might just be a step in the right direction
Please let me know how this works out for you guys.
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Might have just found a really easy fix for the graphics glitching... FACE PALM Only time will tell though. Navigate to /system/lib/egl and edit egl.cfg. you will see this:
Change this to:
This will force the device to always use adreno200 for graphics processing. I don't get those wavy lines in gallery anymore with hw overlays enabled, and I haven't had any screen flickering yet either. Not sure what this means for battery yet, but this might just be a step in the right direction
Please let me know how this works out for you guys.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I made the change this morning. Will report back later. Thanks TF!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Well after 10 hours with your little trick TF the results are positive. No glitches or weird lines through screen. Overlays were unchecked as well. The battery life seems unaffected by the changes in my view. The overlays do not stay unchecked through reboot. I suppose this will be changed if you find this fix to be effective. This is awesome. Thanks once again!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
titanic_fanatic said:
Might have just found a really easy fix for the graphics glitching... FACE PALM Only time will tell though. Navigate to /system/lib/egl and edit egl.cfg. you will see this:
Change this to:
This will force the device to always use adreno200 for graphics processing. I don't get those wavy lines in gallery anymore with hw overlays enabled, and I haven't had any screen flickering yet either. Not sure what this means for battery yet, but this might just be a step in the right direction
Please let me know how this works out for you guys.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just applied the egl.cfg fix to your Slim build, removed the init.d script and rebooted with HW overlays unchecked. Improvement was noticed, and no glitching so far.
To make your external sdcard usable by apps, use the terminal emulator and
$ su
$ chmod 777 /mnt/media_rw
Click to expand...
Click to collapse
Now you should be able to use your sdcard for whatever
Sent from my SGH-I757M using XDA Premium 4 mobile app
EDIT:
You will have to do this every boot for now.
NOTE # I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
# Please do some research if you have any concerns about features included in the products you find here before flashing it!
# YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
# Your warranty will be void if you tamper with any part of your device / software.
UNOFFICIAL BUILD!
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
ALL THE SOURCE CODE IS OPEN SOURCE AND I WILL LINK AT THE BOTTOM OF THE POST:laugh:
CHANGELOG
SEE BELOW POSTS FOR CHANGELOG
BUGS
You Tell
STEPS TO FLASH
1 INSTALL ROM
2 FLASH GAPPS (NANO OR PICO)
3 FLASH MAGISK ( OPTIONAL )
4 REBOOT
5 YOU CAN FLASH ANY KERNEL
NOTE : DIRTY FLASH OVER 03/11 BUILD WON'T BOOT
Telegram http://t.me/LOSUNOFFICIAL
DOWNLOADS
http://bit.ly/2DuyFk2
ROM --> https://drive.google.com/file/d/14VXL_6OAL8DURLO3gByysJb9uf6XAjsp/view?usp=drivesdk
GAPPS --> http://opengapps.org
SPEACIAL THANKS TO : @sreek995 @notallowedontelegram @saladasss @Adwait_001 and @mdeejay for device trees
@shantanu555
SOURCE
DEVICE TREES --> http://github.com/Vince-Beast/device_xiaomi_vince
KERNEL --> http://github.com/Vince-Beast/kernel_xiaomi_msm8953
VENDOR --> http://github.com/Vince-Beast/vendor_xiaomi.git
CREATED : 2019/01/24
LAST UPDATED : 2019/04/24
Deleted
CHANGELOG 2019/04/24
+ April Security Patch
+ Kernel Upstream to 4.9.169 (built with DAB)
+ Wifi Fixed
+ All other minor bugs fixed and build is stable to use as daily driver
CHANGELOG 2019/03/27
> ADDED 4.9 KERNEL
> LIVE DISPLAY FIXED
> COLOUR INVERSION FIXED
> MINOR CHANGES TO IMPROVE PERFORMANCE
> CHANGED BASE DIRTY FLASH WON'T BOOT
CHANGELOG 2019/03/11
>Fixed previous bugs
Lineage Changelog
>It’s now possible to set custom automatic update check intervals in the updater (never / once a day, once a week / once a month)
>Calculator now supports dark mode through Styles API
Added “Mark as read” action in messages notifications
>Exchange support
>Webview has been updated to Chromium 71.0.3578.99
CHANGELOG 2019/02/19
>FEBRUARY SECURITY PATCH
>MINOR BUG FIXES
CHANGELOG 2019/01/31
>SELinux IS NOW SET TO PERMISSIVE
>LOTS OF MINOR BUGS FIXED
>FINGER PRINT IS NOT DETECTED AS TOUCH
>NETWORK STRENGTH IS STRONG NOW
>FIXED READING MODE , LIVE-DISPLAY , GRAYSCALE MODE
>UPDATED SDM BLOBS FROM LA.UM
> PLEASE FLLOW INSTALLATION STEPS IN FIRST POST DON'T FORGET TO FLASH THIS KERNEL http://bit.ly/2sXl8fn AFTER SETTING UP THE ROM OR DON'T REPORT BUGS
CHANGELOG 2019/01/29
>MINOR UI RELATED FIXES
CHANGELOG 2019/01/24
>INITIAL BUILD
Reserved
Great Rom Dev
Smooth , Volte working, all major things are working, battery backup is good, keep making more such roms
Kool, devs are working on Vince, thanks for love, going to try
Nice rome Hitesh .
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
Your ROM developing skill good.
Please make a viper os rom.???????
Azizbagwan said:
Nice rome Hitesh .
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
Your ROM developing skill good.
Please make a viper os rom.???????
Click to expand...
Click to collapse
Thanks I'll try
Keep it up well done
is network monitor work in this los?
ekowanz said:
is network monitor work in this los?
Click to expand...
Click to collapse
No, i will try to fix in next build. This is first build
Great work. At least stable like Rama's builds. I did both a clean and a dirty flash over Rama's build. Works great in both cases.
Will report in a couple of days battery life.
Wifi+BT works, exfat works out of the box.
gardiol said:
Great work. At least stable like Rama's builds. I did both a clean and a dirty flash over Rama's build. Works great in both cases.
Will report in a couple of days battery life.
Wifi+BT works, exfat works out of the box.
Click to expand...
Click to collapse
Thanks for your nice words.
Great rom.
When I switch on the advanced 4g mode in the mobile Network settings, the mobile network ends completely with an error message. Could someone please look there?
hiteshhv said:
Use latest LOS from here this thread won't be updated now and this bug is not there in this build get from below link. RAMA won't update now I'll update
https://forum.xda-developers.com/re...lineageos-lineage-os-16-0-2019-01-24-t3893427
Click to expand...
Click to collapse
Tried this as well, bug appears here too
hyperair said:
Tried this as well, bug appears here too
Click to expand...
Click to collapse
Can you explain the issue a bit better?
Dirty flash over previous ROM from mdeejay also working fine.
Thanks.
hiteshhv said:
Can you explain the issue a bit better?
Click to expand...
Click to collapse
After booting up, the mobile data icon goes in a cycle across these states:
1. No SIM card
2. H
3. H+
4. LTE
5. No SIM card
It does nothing under airplane mode, but if I leave airplane mode off, it cycles for a while, it shows a dialogue that says "shutting down", and then reboots into recovery.
I tried observing the "Settings > Network > SIM cards" section, and it looks like "SIM slot 1" goes empty for a few seconds each time "No SIM card" happens.
`adb logcat` shows some com.android.phone tracebacks, and DeadObjectExceptions in com.android.systemui.statusbar.phone.StatusBar Signal Policy$MobileIcon, as well as some resource not found error with the SIM HD icon (I think the "SIM 1 is HD capable" message that comes from org.codeaurora.ims)
hyperair said:
After booting up, the mobile data icon goes in a cycle across these states:
1. No SIM card
2. H
3. H+
4. LTE
5. No SIM card
It does nothing under airplane mode, but if I leave airplane mode off, it cycles for a while, it shows a dialogue that says "shutting down", and then reboots into recovery.
I tried observing the "Settings > Network > SIM cards" section, and it looks like "SIM slot 1" goes empty for a few seconds each time "No SIM card" happens.
`adb logcat` shows some com.android.phone tracebacks, and DeadObjectExceptions in com.android.systemui.statusbar.phone.StatusBar Signal Policy$MobileIcon, as well as some resource not found error with the SIM HD icon (I think the "SIM 1 is HD capable" message that comes from org.codeaurora.ims)
Click to expand...
Click to collapse
This is not a issue for me i did clean flash and not a issue for other users too! Can you tell me how you flashed this ROM? And which gapps and firmware version to help you more. SERIOUSLY NOT A ROM ISSUE.