CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMod's build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
ROM:http://d-h.st/myfiles?fld_id=28773#files (just look for the one with the newest date on it
Gapps:http://forum.xda-developers.com/showthread.php?t=2012857
use what ever gapps you want but i personally use these ones since its just the basic stuff and its art compatible
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
You will finally see a "set_metadata_recursive" status 7 error. That is normal.
Reboot back into recovery (the reboot is required)
Install the ROM again from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
No access to TV-Out menu
Layout issues in lockscreen
Menu soft-buttons appearing where they shouldn't
Some CyanogenMod features a missing - please do not file bug reports for those.
Privacy guard icon not disappearing when exited app
Broken layout of quick message popup (SMS)
Cannot set value via custom brightness "Edit" menu
If back button is pressed during incoming call, you can't answer the call.
FC when changing image sharpness
Pressing "menu" unlocks swipe lockscreen
Browser: FC in incognito mode and Advanced -> Website settings)
Quick Access Ribbon gone when switching from Quick Settings
2G/3G toggle does not work
Cannot flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Is there a changelog for gapps?
I did not create the packages and do not know. (Please don't annoy the original developer of the packages by asking him either.)
Does this ROM support FM radio?
I've checked and the new FM API in CM is not really compatible with our device without heavy modification. Applications using the new API expect to be able to read the FM input as it if were another stream, but FM on our device only does pass-through from FM receiver to speaker/headset, which causes certain functionalities to not work such as volume control. Maybe one can modify the audio routing table in the kernel to have it behave like the API expected, but I'm not really interested in investing time to do that.
TL;DR: No built-in FM radio except if someone else does it and submits a patch.
the above gapps are what i personally use you can use what ever ones you would like though
Thanks to
pawtip
CM team
FaultException
Kasper_h
anyone else who i forgot pm me and il add you
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
n205des said:
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
Click to expand...
Click to collapse
Deleted
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
ankamar92 said:
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
Click to expand...
Click to collapse
Basicly
New build soon with some kernel modifications to make it even smoother
All the post is C&P from Pawitp i9000 post lol (except links and credits)
But, whatever, I'll download the rom right now, and will try it later..
BTW, gapps links doesn't work.
And..
cannondaleV2000 said:
Deleted
Click to expand...
Click to collapse
What do you mean with "DELETED"? Fixed?
Thanks for your work ^^
When i installed this, all i got was the little cyanogen robot with the rotating arrow, that lasted for about an hour until i got frustrated with it and just went back to my old rom, any ideas on why this is happening?
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Link gapp error ,file not found
cannondaleV2000 said:
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ok, ok, but that not answer my question, the problem with the speaker on receiving call, is fixed?
You answered that to another user --> "Deleted", Deleted == Fixed?
Thanks.
should be. i have not run into the isue so far been running since lastnight.
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
cannondaleV2000 said:
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
Click to expand...
Click to collapse
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
OK will fix
Sent from my SGH-I897 using xda app-developers app
Sorry guys I just realized I uploaded the wrong file. Il fix it tomorrow and post a new link
ManaSV93 said:
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
Click to expand...
Click to collapse
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
mohammad.afaneh said:
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
Click to expand...
Click to collapse
Yep noticed that will fix after school. Because I also uploaded the wrong file top
Downloaded first version, and, have to say that the performance is awesome.
Ram: constant 170 mb free, using BBM, and listening some music.
Web Browser performance was better on CM 10.1
And, with all the KK builds I have tried on the cappy, Every time I turn ON the phone, When OS is completely loaded, I get a message, of invalid IMEI, and that, I can have some problems..
How can I solve this? If I go back to stock rom, and then to CM 10.1, I don't have any problem with this, but when I update to CM 11, I have this error, and don't know wich errors can this give me on future.
Any screenshot ?
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
SlimJB4.3 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in Jellybean 4.3, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz6.07.9 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of SlimBean4.2, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D SlimBean4.3 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). This is the latest SlimBean4.3 and has all of the features of a SlimRom that you've come to love. Don't forget to download the special gapps package to get the full SlimBean experience while using "The Real Dark Slim" feature.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THE PAGE
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files. You can still view these mp4 files, but you must open them with a file manager directly into the video player instead of using the gallery to access them.
* The camcorder records just fine, but when playing back the video, it's just a distorted video. Audio is fine, and I have not tested video with a third party app. If you test one and it works, please post that here so that others may benefit from your findings.
This seems to have been fixed as of the 20140121 build
* The latest Google Drive seems to be missing classes and will not open. This may be due to a missing content provider or may be a bug with the Google Drive app itself.
Solution: The solution for this is to uninstall the latest version of Google Drive, then go to Settings -> Security and enable Unknown Sources. Then open the Play Store and turn off automatic updates or it will end up overwriting the older version and you will be left with a non-working Google Drive again. Once all that is complete, download and install this Google Drive instead:
com.google.android.apps.docs.apk (8.4MB)
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 or Philz Advanced/Touch Recovery flashable zip which is compatible with SlimBean4.2/SlimBean4.3
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (or the Philz one) that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140121 (Latest)
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20140121-0353.zip (114MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20140121.zip (147.3MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Build: 20131228
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20131228-1427.zip (126.1MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20131228.zip (160.4MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with SlimBean4.2/SlimBean4.3/SlimKat
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with SlimBean4.2/SlimBean4.3/SlimKat
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with SlimBean4.2/SlimBean4.3/SlimKat
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]January 21, 2014 - Build 20140121[/B]
* Synced with upstream sources (CyanogenMod/SlimRoms)
* Added SystemUI memory management fix
* Removed 91fixoverlays init.d script as it's no longer required
* Implemented fix for the char dev driver - fixes the vibrator not loading on boot
[B]January 03, 2014 - Build 20131228[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. There is a script that has been included with this ROM in the init.d that sets that on every boot so you shouldn't have to.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* SlimRoms Team - ROM Base
Without all of the hard work and efforts of the SlimRoms team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* @dsixda - Initial port of CM9/CM10 for SGH-I757M
* @Strange Peer - Continued development of CM10
* @rukusx7 - Contributor
* @bijon440 - Contributor
* @kj2112 - Contributor
* @Tronith - Contributor
* @Zippy Dufus - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL SlimJB4.3 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: SlimBean
Version Information
Status: Alpha
Created 2014-01-03
Last Updated 2014-01-23
Reserved
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.
Reserved
Yay a slim bean of 4.3! Woot.
Sent from my SGH-I757M using xda app-developers app
Hi Shouldn't this be in the development forum
Awesome! Was hoping for a new slim build! Thanks so much TF! Great job!
Sent from my SGH-I757M using xda premium
68544455 3521
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..
Hey
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!
JayR_L said:
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..
Click to expand...
Click to collapse
I'll add back the mdnie settings. They are supposed give you control of the temperature
GrAt_On said:
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!
Click to expand...
Click to collapse
Only difference is in features and it's been slimmed down.Other than that, it's the same ROM. I just posted it for those who like the slim features check this page out for the list of slim features:
http://www.slimroms.net/index.php/slim-bean-features
Sent from my SGH-I757M using XDA Premium 4 mobile app
The Iron Man said:
Hi Shouldn't this be in the development forum
Click to expand...
Click to collapse
I've only posted or ROM's here since that's where dsixda was told to post them back when he started with this device. If the mods would prefer I post them in the dev section, I'm more than happy to oblige
Sent from my SGH-I757M using XDA Premium 4 mobile app
Amazing
I just flashed it, its amazing! Especially "The Real Dark Slim"! However, I did notice Google + doesn't work properly asking me to re install it at the play store. Had to uninstall using Titanium Backup and then install it back via app store, not sure now whether it has the the real dark slim feature integrated in google +. Other than that, it's really smooth so far Great port.
UPDATE: Google drive also doesn't work as it force closes continuously even after wiping dalvik's cache. I'll try redownloading the gapps tomorrow, might have a corrupt downloaded file.
I Fashed latest slim as well. It is running really well so far. I had the same issue with Google+ until I uninstalled using TB then reininstall from play store.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Can confirm issue with Google+..
Thank you t_f for looking into mdnie. Also, flashing the unmodified lock screen handle available on Slim's website did not work, I still see the Slim logo. Aaah I wish I had time to figure out the android build environment.. I mean its probably just ant lol
Sent from my SGH-I757M using Tapatalk
I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
manfromgta said:
I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
It is intentional. Disabling the hw overlays is a performance hit, and it seemed that slim didn't need that hack because the overlays are working correctly
I know, the latest ROMs are running smooth and battery is much better since I tweaked the kernel for both.
I'm also really enjoying my new computer so much that I'm playing with paranoid android too. Got it booting with a bunch of hacks and to my suprise, it's running quite well. I'll post that after I test it more and clean up the build process. Then we have choice of which ROM too use. That was the problem before, no choice strange though, there is no branch for kk in paranoid android's repo.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Just a word of caution to everyone using philz latest 6.07 cwm recovery. There is a know issue where the update-binary has now been updated as of kk and the recoveries built with kk like the new philz 6.07 are now giving assert errors (error 7).
There are two ways to fix this:
1) Revert to the older 6.01 version of philz.
2) extract the updater-script from the rom zip file, delete the assert lines and replace the old updater-script with the new one.
If you're new to all this, or consider yourself inexperienced, I recommend you go with option 1 and revert to the older philz as it's a less risky method of doing things
Sent from my SGH-I757M using XDA Premium 4 mobile app
Here's the link to the older philz 6.01. You can use either the 6.01.0 or 6.01.2.
http://d-h.st/users/philz_touch/?fld_id=29076#files
Sent from my SGH-I757M using XDA Premium 4 mobile app
Please check out this post if your not flowing the 10.2 thread and provide your opinion if you have one
http://forum.xda-developers.com/showthread.php?p=49171164
Sent from my SGH-I757M using XDA Premium 4 mobile app
ParanoidAndroid for SGH-I757M Released
Alright, for those of you who are waiting for my PA build, it's up. This is a JB4.3 build of ParanoidAndroid and I have added back the performance settings from CM to allow changing the governor and io scheduler as the defaults have sucky performance.
[ROM][PA-JB4.3][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M
Enjoy!!!
It's saying that slim isn't rooted?
PA-JB4.3 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in PA-JB4.2/PA-JB4.3, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz Touch 6.07.9 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of PA-JB4.2, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D ParanoidAndroid JB4.3 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). Among the most notable features in PA is the ability to set on a per/app basis, the colour and dpi. Other sought out features are HALO (onscreen notification and quick app access), and phablet mode which makes apps load as if they were on a tablet. This makes them use the tablet layouts instead of the phone layouts.
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
* USB Mass Storage (UMS Mode)
Click to expand...
Click to collapse
What Doesn't Work
* I haven't found anything as of yet. Let me know if you find something that is not working as it should ;-)
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: 20140410 (Latest)
ROM: pa_celoxhd-3.99-RC2-20140410.zip (157.7MB)
GAPPS: pa_gapps-full-4.3-20140121-signed.zip (221.6MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Build: 20140130
ROM: pa_celoxhd-3.99-RC2-20140130.zip (153.9MB)
GAPPS: pa_gapps-full-4.3-20140121-signed.zip (221.6MB)
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]April 10, 2014 - Build 20140410[/B]
* Added USB Mass Storage
[B]January 6, 2014 - Build 20140105[/B]
* Initial release
* Added CM performance settings
Click to expand...
Click to collapse
FAQ
Q. The UI feels very slow, how do I speed it up?
A. This ROM does not seem to run very well while on the Interactive governor. Go to Settings -> About Phone and tap on the Build Number 7 times to activate the Developer Options and the Performance Settings. Then open Settings -> Performance and change the Governor to "OnDemand" and the I/O Scheduler to "Deadline". This will get you the best operation possible from this ROM.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* Paranoid Android Team - ROM Base
Without all of the hard work and efforts of 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
* @bijon440 - Contributor
* @kj2112 - Contributor
* @Tronith - Contributor
* @Zippy Dufus - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL PA-JB4.3 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-06
Last Updated 2014-04-12
Tips & Tricks
Tips and Tricks
APN
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.
Governor & I/O Scheduler
The Interactive governor does not work well on this ROM, so you must change it to "OnDemand" and the I/O Scheduler to "Deadline". To do this, got to Settings -> About Phone and tap on Build Number 7 times to activate both the Developer Options and the Performance settings. Then go to Settings -> Performance and change the Governor and I/O Scheduler as mentioned above. Do not forget to check the box for "Set at boot" so that it gets set every time you boot the phone.
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.
Awesome! A PA build! This are coming along with this device TF, great work. Ill install as soon as I get bored of your KK build, still using that as a daily driver for now haha
Sent from my SGH-I757M using xda premium
Does this build have the new cache?
formercontra said:
Does this build have the new cache?
Click to expand...
Click to collapse
No, it still has the old cache. I'm working on a way to make it permanent and from first boot.
This will be implemented after I figure out the fstab file.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Well my morning routine of perusing your threads is taking a little longer TF. Lol.
I tried the pa build and no hiccups. I find it somewhat sluggish compared to my preferred slim ROMs.
I was thinking since you seem to be on a roll. What are your thoughts on an AOKP build? I have always enjoyed the features it has. I was messing with porting it with no success. Stuck at boot animation.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
manfromgta said:
Well my morning routine of perusing your threads is taking a little longer TF. Lol.
I tried the pa build and no hiccups. I find it somewhat sluggish compared to my preferred slim ROMs.
I was thinking since you seem to be on a roll. What are your thoughts on an AOKP build? I have always enjoyed the features it has. I was messing with porting it with no success. Stuck at boot animation.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
It's definitely more sluggish. Did you change the governor and io scheduler to "OnDemand" and "Deadline" respectively? These provide the smoothest operation of this particular Rom which is why I had to add back the performance settings from CM which requires fairly extensive porting.
How are you "porting", by building? If so, you should check out my github. All of the code is there for our device and it's proprietary blobs. You will need to modify the build to work with AOKP, but most of the work has already been done by me in maintaining an updated device tree.
You would most likely need to modify the vendor/aokp files to include our device. Best to create a github account for managing that. Abs you would Assisi have to change done things in our device tree tree, such as cm.no probably changes to aokp.mk abs cm.dependencies probably changes to aokp.dependencies. Best to find a skyrocket device tree for AOKP if you can and then you can see how they did it. Then just diff the two folders to see where the differences are and modify as necessary.
I'll see what I can find, but I want planning on an AOKP, but rather an omni when it becomes more stable. And to my knowledge right now, there is an issue with the emmc brick bug code and that has to be fixed before I bother.
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
It's definitely more sluggish. Did you change the governor and io scheduler to "OnDemand" and "Deadline" respectively? These provide the smoothest operation of this particular Rom which is why I had to add back the performance settings from CM which requires fairly extensive porting.
I forgot about changing to on demand and deadline. Much better now.
How are you "porting", by building? If so, you should check out my github. All of the code is there for our device and it's proprietary blobs. You will need to modify the build to work with AOKP, but most of the work has already been done by me in maintaining an updated device tree.
No not building. Not that far advanced yet. I was just doing the amateur cut and paste using an aokp ROM for skyrocket. Thanks for your info. Hope to learn more in days to come.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Hi TF, I just flashed this ROM using philz recovery and the vibration issue from your CM 4.3 build is still haunting me
I've rebooted at least 3 times since flashing and I have no vibration at all
PS thanks for all the hard work you put into this device, its made it worth keeping this phone :thumbup:
Sent from my SGH-I757M using xda app-developers app
B.Moreira said:
Hi TF, I just flashed this ROM using philz recovery and the vibration issue from your CM 4.3 build is still haunting me
I've rebooted at least 3 times since flashing and I have no vibration at all
PS thanks for all the hard work you put into this device, its made it worth keeping this phone :thumbup:
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
I actually found a fix for this (I think) and released a patched kernel in the CM-10.2 thread. I was going to wait a week before updating the other kernels, but since you are in need, I'm building it right now. Please give me a little bit to test it after it's built. About an hour or so and I'll post a link
New Kernel Fixes Vibration Issue
So here is that new kernel I promised. This kernel implements a fix to ensure that all modules get loaded on each boot. It's still in testing phase, so if you experience no vibration at any time please let me know. I've been running the new kernel for almost 2 days now and have not lost my vibration at all, even after aggressively rebooting the phone several times. I'm pretty confident that this is the fix, but as I said, it's still in testing.
Remember to take a nandroid backup before flashing just in case something goes wrong. Then simply flash the new kernel without wiping anything and reboot the phone. You can verify that you are running the new kernel by going to Settings -> About Phone and check that you are running kernel dated Jan. 8, 2014.
DO NOT FLASH THIS ON MY OTHER ROMS. DOING SO MAY GET YOU INTO A BOOTLOOP. NEW KERNEL RELEASES FOR ALL ROMS ARE PLANNED WITHIN THE NEXT WEEK.
boot-ONLY-VIBFIX-cm10.2-20140108.zip (5.8MB)
Thanks for the kernel! I've been running the rom for about 24 hours now with no issues at all
Sent from my SGH-I757M using xda app-developers app
Any and All Video files cause the app to crash stating : "unfortuantely _______ has stopped working" .
Anyone else having this issue? Or ideas to resolve?
oa12 said:
Any and All Video files cause the app to crash stating : "unfortuantely _______ has stopped working" .
Anyone else having this issue? Or ideas to resolve?
Click to expand...
Click to collapse
Which app? The gallery or video player, or both?
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Which app? The gallery or video player, or both?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
YouTube . Google Movies . videos in Browser or Chrome . Gallery can playback recorded videos.
oa12 said:
YouTube . Google Movies . videos in Browser or Chrome . Gallery can playback recorded videos.
Click to expand...
Click to collapse
Cheers, I'll run some tests to see what I can find. Also, a logcat would be helpful. Check out the second post as I have instructions posted on how to take a logcat. You can send that to my email [email protected] and I'll be able to see what's happening on your phone that might be different from mine.
Sent from my SGH-I757M using XDA Premium 4 mobile app
My first bug to report is that my performance settings will not stick after I reboot, I have set on boot checked but it keeps reverting back and memory settings do the same. :banghead: I haven't however had the video player player problem.
Sent from my SGH-I757M using xda app-developers app
B.Moreira said:
My first bug to report is that my performance settings will not stick after I reboot, I have set on boot checked but it keeps reverting back and memory settings do the same. :banghead: I haven't however had the video player player problem.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
This is most likely due to my "port" of the these settings. I will look into this
Sent from my SGH-I757M using XDA Premium 4 mobile app
B.Moreira said:
My first bug to report is that my performance settings will not stick after I reboot, I have set on boot checked but it keeps reverting back and memory settings do the same. :banghead: I haven't however had the video player player problem.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
Please try this new Settings.apk. I see very clearly I forgot to import the boot receiver code which is why it doesn't work, sorry :-\
This is a flashable zip, and remember to take a nandroid just in-case something goes wrong. It will replace your current settings.apk and set the correct perms.
SETTINGSFIX-cm10.2-20140108.zip(6.5MB){/B]
Thanks for your feedback
QUOTE=titanic_fanatic;49477936]Please try this new Settings.apk. I see very clearly I forgot to import the bootver code which is why it doesn't work, sorry is a flashable zip, and remember to take a nandroid just in-case something goes wrong. It will replace your current settings.apk and set the correct
The new settings fix works for me and is appreciated!
As for my video playback problem, I kept wiping for new Rom via the touch cwm and realizedit was not formatting /system . I formatted this manually and the video playback was fixed. My guess mismatch in app data and rom id between
ROM INSTALLS.
Wrote this ntvia phone. Excuse the keypad issues im having .
AOKP 4.4 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2/CM11.0, you are required to update
your recovery to a supported recovery with a version greater than 6.0.39. As of this writing, the latest available
version is Philz Touch Recovery 6.13.2(based on CWM 6.0.47) for the SGH-I757M. There is currently not a
version of regular CWM for this device that will flash Kit Kat ROMs.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
AOKP is a fork of AOSP with many custom additions implemented by the AOKP team. It features most of the same functionality as CM-11.0 with custom features.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera (Camcorder doesn't work right now. Don't select it or you'll mess up the camera all together)
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
* USB Mass Storage (UMS mode)
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new Philz Touch Recovery 6.13.2 flashable zip which is compatible with CM10.1/CM10.2/CM11.0/SlimKat
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the philz_touch_6.13.2-celoxhd.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios (Required before you flash the ROM, unless you already have the new JB radios flashed)
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: Using Philz Touch Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140817 (Latest)
ROM: aokp_celoxhd_kitkat_unofficial_2014-08-17.zip (180.4MB)
GAPPS: aokp-mini_gapps-kk-20140528.zip (75.1.4MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A clean flash is REQUIRED if upgrading from a previous version of android such as CM10.2/SlimJB4.3.
Build: 20140412
ROM: aokp_celoxhd_kitkat_unofficial_2014-04-12.zip (169.3MB)
GAPPS: gapps-kk-20140321.zip (141.4MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.13.2 (CWM 6.0.4.7) compatible with CM10.1/CM10.2/CM11.0/SlimKat
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]August 17, 2014 - Build 20140817[/B]
* Synced with sources
* Added sysfs interface for vibrator intensity control
* Added settings to control vibrator intensity in Advanced Device Settings
* Added Omni Performance Control
[B]April 12, 2014 - Build 20140412[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. Reboot your phone and you should be rooted.
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* AOKP Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod/AOKP teams, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @Socim - Thanks to Socim for pointing me in the right direction a few times ;-)
* @formercontra - Contributor
* @manfromgta
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL AOKP KK4.4 For Bell SGH-I757M, ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic, manfromgta
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: SlimKat
Version Information
Status: Alpha
Created 2014-04-13
Last Updated 2014-08-18
Downloaded and clean install. Went without a hitch including TB app restore. I will let it settle in and report any findings. Thanks Tyler for everything!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Is AOKP better than CyanogenMOD at this moment? or What is your opinion?
Screambloody said:
Is AOKP better than CyanogenMOD at this moment? or What is your opinion?
Click to expand...
Click to collapse
AOKP has the same performance as my other ROMs. It just had different features, some of those are included in other ROMs too like carbon.
My favorite ROM is still carbon, I just want to provide others with a choice of what ROM to run. You can always test it out and restore a nandroid if you don't like it
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
AOKP has the same performance as my other ROMs. It just had different features, some of those are included in other ROMs too like carbon.
My favorite ROM is still carbon, I just want to provide others with a choice of what ROM to run. You can always test it out and restore a nandroid if you don't like it
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks,I'll test this ROM,but,is Carbon more stable than AOKP,CyanogenMOD 11 and Slimkat?
Screambloody said:
Thanks,I'll test this ROM,but,is Carbon more stable than AOKP,CyanogenMOD 11 and Slimkat?
Click to expand...
Click to collapse
No, I just prefer the features that carbon has implemented. Some from cm, some from aokp and some from slim. For me it's the best of all 3 And now I'm playing with the idea of permanently implementing Slim's recents app since I really like it.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Been running this for a few days. Going to try ART later. Excellent job! :good:
I got stuck at the boot animation for almost 15 minutes when I enabled ART . Luckily I had a backup. Oh well, rom is still fantastic.
iDynamics said:
I got stuck at the boot animation for almost 15 minutes when I enabled ART . Luckily I had a backup. Oh well, rom is still fantastic.
Click to expand...
Click to collapse
When this happens, you can boot into recovery, then use the console I'm aroma filemanager and ruin this command:
$ echo "libdvm.so" > /data/property/persist.sys.dalvik.vm.lib
Click to expand...
Click to collapse
Of course you need to mount the data partition before you open the console
This will switch you back to dalvik
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
When this happens, you can boot into recovery, then use the console I'm aroma filemanager and ruin this command:
Of course you need to mount the data partition before you open the console
This will switch you back to dalvik
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks.
I used this to switch back.
http://forum.xda-developers.com/showthread.php?t=2713622
I have a new build of AOKP running right now Hope to post it by the end of the night!
Will the fixoverlays script be needed for this build?
iDynamics said:
Will the fixoverlays script be needed for this build?
Click to expand...
Click to collapse
I assume so, but am not entirely sure until I test it out
Sent from my SGH-I757M using XDA Premium 4 mobile app
There was a whole bunch of build errors when I got home it seems that I synced between important commits that caused the build errors. It's now back to building, and the good news is that I incorporated omni performance controls into this build instead of cm's.
Also, this will be the first of the 4.4.3 builds
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
There was a whole bunch of build errors when I got home it seems that I synced between important commits that caused the build errors. It's now back to building, and the good news is that I incorporated omni performance controls into this build instead of cm's.
Also, this will be the first of the 4.4.3 builds
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looking forward to it
Just fyi, the build is done, but untested because sultanxda posted his fix for the graphical glitches and I've didn't all day porting over those changes to our kernel. I'm working through build errors right now, but hope to test tonight. If anyone is brave enough, your welcome to test the aokp I built, just let me know and I'll upload otherwise, I'll test it after I get this kernel tested out
Sent from my SGH-I757M using XDA Premium 4 mobile app
I'm down for testing.
iDynamics said:
I'm down for testing.
Click to expand...
Click to collapse
Cheers, so I'll upload the zip right now. When it's done, I'll post the link with specific instructions on what to test and how to test it
The only time it becomes really difficult to test and get useful loss if needed is when either it bootloops or android doesn't load. I'll explain how to overcome these situations when I post instructions.
Thanks for the help and support
Sent from my SGH-I757M using XDA Premium 4 mobile app
iDynamics said:
I'm down for testing.
Click to expand...
Click to collapse
alright, it's uploaded to my Aokp folder inside another folder called test.
Flash as usual taking your necessary backups beforehand
Then, first I need you to test if the overlays script is still needed. To check this, go to developer options and uncheck the disable hw overlays checkbox, then pull down the notification shade and if the background goes immediately black instead of starting to dim then it's still needed so disable it again. If that check passed, go to the Homescreen by pressing back and make sure there is no flicker and that the background never goes black. This must be the same for the Homescreen as well, the background cannot go black. If it doesn't then you can open a browser instance and browse to review.cyanogenmod.org specifically and use the input field in the top right corner, this causes the view to zoom and also the keyboard to appear. If nothing happens, click outside of the input field to hide the keyboard or press back one time to do the same and then back into the input field again to pull up the keyboard. Do that allot and if the glitching still remains, this will cause lots of glitching and a reboot.
With that all tested, make sure that the performance settings work as I ported omni's performance control from my carbon build.
Also make sure to check the version information.
Ok, pay close attention here. I know you know how to take a logcat, that's the easy part. What to do if you get a bootloop, this is the tricky part. You must watch the phone boot up the first time which usually takes 130 seconds give or take and depending on the rom. Getting a kernel log can be difficult when in a bootloop because it's cleared each time the phone boots, well that's not useful is it here's the trick, and why you need to watch the bootup. As soon as the phone bootloops, there will be the initial vibration that signifies the device is booting up, you need to press and hold only your volume up and volume down buttons as soon as you feel the vib until you get into cwm. If it boots past into the bootlooping android then the log is gone and you need to try the process again.
Once you get into cwm, open aroma filemanager by double tapping the empty space at the bottom of the menu. Make sure aroma options are set to mount everything and show hidden files. Now browse to /proc and scroll down to the files until you find last_kmsg and copy that file to a spot on your sdcard which you will need to access through /storage/sdcardX where X represents 0 for internal or 1 for external sdcard.
This log is what I would need to see to fix a bootloop let me know if anything doesn't make sense
Sent from my SGH-I757M using XDA Premium 4 mobile app
I will download and test today.
Ok. I downloaded and flashed but i can't get to developer options. I did the tapping in about phone as usual but it does not enable options.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kit Kat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions:
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Issues?
Report them on github:
https://github.com/M1cha/android_device_xiaomi_aries/issues
What's important: if you use xposed - pls disable it and try it again because it can cause problems in some cases.
Also the issue must contain important information like your phone model(mi2(s)(c)), and the exact build version of the ROM.
Download Links:
CyanogenMod:
Nightly:
Download: http://download.cyanogenmod.org/?device=aries
Google Apps addon:
Use 4.4 gapps:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
Sourcecode:
ROM: https://github.com/CyanogenMod
Devicetree: https://github.com/CyanogenMod/android_device_xiaomi_aries
Kernel: https://github.com/CyanogenMod/android_kernel_xiaomi_aries
GENERAL COMMENT AND REQUEST:
We ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"
Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).
We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.
Just clearing data etc. may in fact cause us to never find the bug that caused the issue and just makes for lazy users.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 Nightlies, ROM for the Xiaomi Mi 2
Contributors
m11kkaa
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2014-09-15
Last Updated 2014-09-15
Troubleshooting/ FAQs
I am reading FAQs, am I ok?
You're the best , but I'm not sure how you'll fell after you've read these things...
How can I enable Developer/ Performances Settings?
Go to Settings>Info>Click several times on build
How can I enable 4 way reboot (Recovery, System, soft, Bootloader) ?
Enable developer options, then go to Settings>Developer and enable Advanced Reboot
Why there's no HDR on camera?
Cyanogenmod does not provide closed source software, like drivers for HDR, you need to install Miui camera, or another camera from playstore
Why is there no Play Store or <insert gapp here>?
Since there are 2 system partitions they're small, and kk needs about 800mb to have a rom + gapps. There are 2 things u can do: First: install this gapps package this. Second way: use the repartition script of XiaomiTool to extend them.
Why is performances profile resetted every boot?
You need to enable Settings>performances>CPU>Set on boot
Why the phone doesn't fly if I enable airplane mode?
It's a WIP (work in progress) feature, now it works only if you throw it at 11,2 km/s² toward the space. It looks like there's no fix for this (yet).*
How can I enable adb root?
Go to Settings>Developer>Root access> Apps and Adb
How can I hide apps from trebuchet (launcher)?
Click Menu>Protected Apps> Set a "password"> Hide them
How can I charge my phone?
It looks like the xiaomi charger isn't enough powerful to charge the phone with cm. Here's your fix: buy a small nuclear reactor (you can find a cheap one on amazon or ebay I think), place the phone between the uranium fuel rods, power the reactor on and let the phone charging for about an half hour. It will be charged and it won't discharge again anymore.*
(I'm running art, it's very good and i feel better running it) This app FC... What can i do?
Switch to dalvik
Today I updated the phone and it's in a bootloop now...
Nice to get know you're enjoying art, switch back to dalvik flashing this
Bugs
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_aries
[DEV] How to build
http://wiki.cyanogenmod.org/w/Build_for_aries
Two Releases: Nightlies and Stable/Monthly
Nightlies and Monthlies are very different. YOU CAN NOT UPDATE FROM A NIGHTLY TO A MONTHLY WITHOUT A WIPE /DATA. Why? Simple, M releases uses a different branch and it's much older than the previous Nightly avaible, so this may cause bootloops.
So you can update from a Monthly to newer Nightly, but you cannot update from a Nightly to a Monthly. If you choose unstable branch (aka Nightlies) you shouldn't update via ota to Stable branch (aka Monthly), you need to wipe /data.
Other Info
http://wiki.cyanogenmod.org/w/Aries_Info
I'll be building Slim (and maybe Omni) for this soon, so I was wondering which vendor repo do you use?
Great I use themuppets https://github.com/TheMuppets/proprietary_vendor_xiaomi
Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?
SkaldfraNorden said:
Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?
Click to expand...
Click to collapse
yes
Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?
isaacbh said:
Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?
Click to expand...
Click to collapse
Sdcard format is not working well on cwm cuz of tdb. U have to flash a fastboot package and or flash a stock miui with miflash.
Tdb doesn't affect performances at all.
Tdb doesn't mess with sdcard at all so it probably is a cwm bug.
Good to see we're moving to XDA!
m11kkaa said:
Tdb doesn't mess with sdcard at all so it probably is a cwm bug.
Click to expand...
Click to collapse
Another scenario in which this bug showed for me was this. Maybe this is useful to track the issue.
I installed CWM 6.0.5.0, and then WIUI (4.7.18) based on KK.
After formatting the sdcard from within WIUI, even without rebooting, at that point the internal sdcard couldn't be written any longer from within WIUI.
I'm using this ROM and i'm really impressed.
One thing though is that my battery is going down much faster than on miui.
Any tips?
Check if you have wakelocks and freeze with greenify
does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!
you either have to flash a very small gapps package or resize your system partition(s)
thienquang07 said:
does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!
Click to expand...
Click to collapse
Read FAQs
Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.
Mavamaarten said:
Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.
Click to expand...
Click to collapse
Disable "sound on touch"
linuxxxx said:
Disable "sound on touch"
Click to expand...
Click to collapse
Oh god. I'm glad the fix is that simple. Thanks a bunch, I really didn't think of that.
I even disabled the "Okay Google" hotword because according to some googling the issue was connected to that.
Video camera records video maximum 10 minutes. Could it be changed to unlimited?
And also sound quality is very poor in recorded videos. I looked through spectrums and it appears that they are cut above 8000Hz. Seems like on some stage signal is being sampled with 16000 Hz sample rate and, judging by some bubbling and other artefacts, it is made without prior antialiasing filtering. Output format acc 48000 Hz.