Related
CM10.2 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz5.18.4 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM10.2 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). More desired may be the new privacy manager features that allow you to control, on a per app basis, which information you wish to share. Other improvements include an improved lockscreen cLock and a new integrated Superuser.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera/Camcorder
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* When unlocking the screen, sometimes only the capacitative buttons light up, and the screen doesn't come on. This seems to happen about 80% of the time.
Solution: This can be fixed by locking the screen, then unlocking it again. In about 5% of these cases the screen does not come on again. Just repeat the steps again until it does.
This has been fixed as of build 20131029
* You may notice a screen flicker when you first flash this ROM. This is due to a bug where the system can't decide whether to render the graphics with the cpu or the gpu, thus the flicker.
Solution: This is fixed by turning on Settings -> Developer Options -> Disable HW Overlays (You must first enable Developer Options by pressing 7 times on Settings -> About Phone -> Build Number). This will be reset on every boot. if you install Universal Init.d, my 91fixoverlays script will run on each boot and fix this automatically.
This has been fixed as of build 20131029
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 flashable zip which is compatible with CM10.1/CM10.2
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140224 (Latest)
ROM: cm-10.2-20140224-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20140224-signed.zip (106.5MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A dirty flash should work for upgrading , but a clean flash is highly recommended
Build: 20140120
ROM: cm-10.2-20140120-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20131231-signed.zip (103.8MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with CM10.1/CM10.2
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with CM10.1/CM10.2
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]December 23, 2013 - Build 20131223[/B]
* Revert build.prop to use dyn instead of gpu (less problems)
* Added back 91fixoverlays to /system/etc/init.d to disable hw overlays and fix screen flicker on boot
* Re-worked 91fixoverlays script so that it now runs in it's own shell to stop it from blocking other startup scripts and causing a laggy boot
* Fixed up device tree code including adding the correct definitions for boot animation size and update to the build fingerprint
* Synced latest changes from CyanogenMod
[B]December 1, 2013 - Build 20131201[/B]
* Force gpu rendering in build.prop
* Improve fix for screen on delay
* Synced latest changes from CyanogenMod
* Updated GAPPS
[B]October 29, 2013 - Build 20131029[/B]
* Tweaked build.prop to fix screen flicker and notification drawer lockup
* Fixed screen unlock bug - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/5e163ff0c5d90a4518cbc9e14c86dceec095c70a"]Commit 5e163ff0c5d90a4518cbc9e14c86dceec095c70a[/URL]
* Added SmartAssV2 Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/511e45206bb9a1454a0c43b3d626749c1fa2c241"]Commit 511e45206bb9a1454a0c43b3d626749c1fa2c241[/URL]
* Added Adaptive Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6"]Commit 7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6[/URL]
* Added Lagfree Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/d1392017601d27303fbce9da18d2af718e7e1a65"]Commit d1392017601d27303fbce9da18d2af718e7e1a65[/URL]
* Restore Advanced Device Settings - [URL="https://github.com/titanic-fanatic/android_device_samsung_msm8660-common/commit/3126c17c6165c7d96abde4cd7459769e165aa195"]Commit 3126c17c6165c7d96abde4cd7459769e165aa195[/URL] / [URL="https://github.com/titanic-fanatic/android_packages_apps_Settings/commit/9031ffb1f4e4185f397724a27e3d75afe7fd67e4"]Commit 9031ffb1f4e4185f397724a27e3d75afe7fd67e4[/URL]
[B]October 5, 2013 - Build 20131003[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market, and also make sure you have Universal Init.d installed and active. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. When your phone reboots, recovery will warn you that your device may possibly be unrooted. This is because of the install-recovery.sh script that is required to start the superuser daemon which allows SuperSu to manage superuser permissions. You are not unrooted ;-)
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. This needs to be set on every boot unless you are running Universal Init.d and my 91fixoverlays script is present in the /system/etc/init.d folder.
Q. When I unlock my screen, my menu/home/back/search buttons come on but the screen is black?
A. This is a known bug in this ROM and is on the list of things that need to be fixed. For now, when this happens, just lock the screen, then unlock it again and the display should come back. If it does not, repeat until it does (the most number of times i had to do that was 3).
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM10.2 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-10-05
Last Updated 2014-02-23
Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Wow! Thanks so much. Downloading now.
iDynamics said:
Wow! Thanks so much. Downloading now.
Click to expand...
Click to collapse
Wow, you already found it and I wasn't even finished putting everything up... make sure you use the new CWM, very very very important!
Followed the instructions ( to the best of my ability ) but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
iDynamics said:
Followed the instructions but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
Click to expand...
Click to collapse
I totally forgot to update the build.prop with the build type, it is responsible for the red border. Either use a build.prop editor or open the /system/build.prop with a text editor and change the following line:
ro.build.type=eng
Click to expand...
Click to collapse
Change it to:
ro.build.type=user
Click to expand...
Click to collapse
You will need to reboot after making this change.
In regards to the 91fixoverlays script, I do appologize. I forgot to include it in the zip... Please download the attached 91fixoverlays.txt file and rename it to 91fixoverlays and move it to /system/etc/init.d and change it's permissions to match the other files in that directory.
Sorry for missing these two things. I will update the packages ASAP and will post a note when it's done so you know that there is no need to follow the steps in this post.
Much appreciated! No more red flickering. Thanks!
Wow! Thank you!
Sent from my SGH-I757M using xda app-developers app
This. Is. Amazing!!!!!
Downloading now, will install and report back in a bit with findings.
Thanks so much!!
Awesome. Downloading. Will report back. Thanks!
Sent from my SGH-I757M using xda premium
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will do more testing.
Thanks
Zippy Dufus said:
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will so more testing.
Thanks
Click to expand...
Click to collapse
I think this is due to our oddly small cache partition. Only 100MB as compared to the skyrocket at 300MB. Currently, I only moved four apps in the gapps package to the data partition do that their dex files don't end up in the /cache/dalvik-cache dir and instead end up in /data/dalvik-cache. I think I need to move others. I also think that it happens only on first boot without side effects because a couple of the installed apps only run on first boot, then their dex files can be deleted (I think this happens automatically).
Sent from my SGH-I757M using XDA Premium 4 mobile app
Thanks titanic_fanatic, you've breathed new life into an old phone
Sent from my SGH-I757M using Tapatalk 2
Only issue I've run into so far is that auto rotate doesn't seem to work :-/
Sent from my SGH-I757M using XDA Premium 4 mobile app
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
rukusx7 said:
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
Cool, I'll give that a try. Anyone else having auto-rotation issues?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Rotation is not working for me, though I always keep it on portrait anyway so I am not complaining.
Rotation doesn't work here, and every so often I run into spells where the only button that works is the home button and haptic feedback stops working all around. A reboot fixes it and it seems random. Other than those few things this is soooooo smooth. I'm happy. Thanks so much!
Sent from my SGH-I757M using xda premium
Fix for Sensors
Hey guys, to fix the sensors, download this attachment sensors.default.so.txt and rename it to sensors.default.so, move it to /system/lib/hw and give it the same permissions as the other files in that directory, then reboot and your sensors should be working
Works now! Thanks ya muchly.
Sent from my SGH-I757M using xda premium
CM11.0 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2/CM11.0, you are required to update
your recovery to a supported recovery with a version greater than 6.0.39. As of this writing, the latest available
version is Philz Touch Recovery 6.57.9 (based on CWM 6.0.51) for the SGH-I757M. There is currently not a
version of regular CWM for this device that will flash Kit Kat ROMs.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM11.0 (Android4.4.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). There is a lot to be said about Kit Kat with it's clean white icons and new launcher. The focus with Kit Kat was to make the device use less RAM and imrove performance, and so far it's running great.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera (Camcorder doesn't work on 1080, swith it to 720 for recording)
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
* USB Mass Storage (UMS)/MTP
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new Philz Touch Recovery 6.57.9 flashable zip which is compatible with CM10.1/CM10.2/CM11.0
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the philz_touch_6.12.8-celoxhd.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios (Required before you flash the ROM, unless you already have the new JB radios flashed)
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: Using Philz Touch Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20141122 (Latest)
ROM: cm-11-20141122-UNOFFICIAL-celoxhd.zip (213.2MB)
PA Mini GAPPS: PA Mini Modular GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A clean flash is REQUIRED if upgrading from a previous version of android such as CM10.2
Build: 20140910
ROM: cm-11-20140910-UNOFFICIAL-celoxhd.zip (211.3MB)
PA Mini GAPPS: PA Mini Modular GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
DADOES ROM:
Build: 20140424
ROM: cm-11-20140424-DADOES-UNOFFICIAL-celoxhd.zip (469.18MB)
GAPPS: INCLUDED
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.12.8 (CWM 6.0.4.7) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* I no longer upload files to XDA because it takes way to long to manage, so I only use androidfilehost.com. All files can be found under my profile: https://www.androidfilehost.com/?w=files&flid=7547
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]November 22, 2014 - Build 20141122[/B]
* Increased kernel version to Titanium 1.1.1
* Added cpu input boost framework - credit: sultanxda
* Added cpu OC (The scale goes up to 1890MHz, but you should only put it as high as 1836MHz since I was getting random reboots with 1890MHz. 1674MHz is the default OC and 1512MHz is the default CM OC) - credit: TeamFahQ/sultanxda/titanic-fanatic
* Added low power flash mode which will use a low powered flash when the battery is equal to or below 35%. This should help with the camera causing the phone to shut down when trying to take pictures using the flash. This threshold may need to be tweaked, so please let me know if you still experience shut downs related to using the camera. - credit: sultanxda
* Added sgs2hdbell as a device name to the updater-script to allow all bell i757m devices to flash the ROM without the need to edit the updater-script.
* Added panel undervolt interface. - credit: sultanxda
* More memory optimizations. Some of the extra RAM that the previous optimization gave us has been allocated to other things such as the surface flinger. Available RAM is now around ~760MB.
* Removed vbus_present wakelock for good (it worked it's way back in somehow)
* Added fast charge. Phone will now charge at 1200mA until 95% regardless of your charging source (AC/USB)
* Added exFAT driver to kernel. It's a filesystem like ext4 but is based on Windows FAT filesystem. You can format your sdcard as exFAT as it's supposed to be faster than vFAT which is what our sdcards are formatted as. Make sure you backup your sdcard contents before formatting it as exFAT and keep the backup until your sure you want to stick with exFAT.
* Removed NFC since I don't think anyone uses it and can't figure out how to have it disabled by default so it is removed completely. If someone is using NFC, let me know and I'll add it back but for now, I just see it as a battery drain.
[B]September 10, 2014 - Build 20140910[/B]
* Kernel now has a custom version number in addition to my kernel name of Titanium
* Optimized kernel memory mapping to increase our physical RAM from ~730MB to ~800MB (a whole 70 extra MB... whoa!)- credit: sultanxda
* Removed mDNIe (it's not supported/working)
* Removed 91fixoverlays script (no longer needed)
* Removed persist.hwc.mdpcomp.enabled from build.prop (hack to fix the hwoverlays because fb drivers are broken somehow) - credit: sultanxda
* Added GPU overclock from 266MHz to 320MHz (helps a lot with the UI lag) - credit: sultanxda
* Added code for 2 phase OnDemand governor - credit: sultanxda
* Added opensource frandom module to help speed up the UI (also helps with the lag) - credit: bryan2894
* Added mdp Color Enhancements (better display color) - credit: sultanxda
* Added color/gamma controls in place of mDNIe (see the tips and tricks section for my already tweaked favorite settings) - credit: bryan2894/titanic_fanatic (I had to integrate it into our display drivers)
* Added Swipe 2 Wake (S2W) support in the kernel (it's actually tap once on each key from left to right). - credit: bryan2894
* Added audio.r_submix.default.so to the build to enable screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary audio channels in the audio_policy.conf for screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary settings in Advanced Device Settings for screencasting and color/gamma control - credit: bryan2894/titanic_fanatic (I added the screencasting settings)
* Fixed the annoying BLN sticking (I think... Please confirm this for me) - credit: bryan2894
* Fixed the sampling rates for A2DP, input and r_submix channels - credit: bryan2894
* Changed both scaling governors to OnDemand - credit: bryan2894
[B]August 15, 2014 - Build 20140815[/B]
* Sync with sources
* Added sysfs interfaces for vibrator intensity
* Added Settings in Advanced Device Settings for vibrator intensity
[B]July 11, 2014 - Build 20140708[/B]
* Sync with sources (Update to Android 4.4.4)
* Vibrator module now built into kernel
* Added sysfs for vibrator intensity to allow user control of the vibrator intensity
[B]May 21, 2014 - Build 20140321[/B]
* Sync with sources
* Switched to using media-caf
* Updated kernel with sources for media-caf
* Fixed issue with Google Camera resolution preferences FC
* Added back 91fixoverlays script due to graphics glitches with the new kernel
[B]April 10, 2014 - Build 20140410[/B]
* Synced with sources
* Added USB Mass Storage Mode (UMS)
* Fixed network type selection menu. It now includes LTE as an option.
[B]March 29, 2014 - Build 20140329[/B]
* Synced with sources
* Added overlay items to enable homescreen/lockscreen rotation
* Set Camera as default Scene Mode to partially fix camcorder recording
* cherry-pick display-caf commits to fix some of the graphical glitches
[B]March 21, 2014 - Build 20140321[/B]
* Sync with sources
* Remove 91fixoverlays script
[B]February 6, 2014 - Build 20140206[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. Reboot your phone and you should be rooted.
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @Socim - Thanks to Socim for pointing me in the right direction a few times ;-)
* @formercontra - Contributor
* @Sultanxda - Many bug fixes and improvements for the msm8660 kernel
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM11.0 For Bell SGH-I757M, ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
Source Code: https://github.com/titanic-fanatic
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-02-06
Last Updated 2014-11-24
Tips & Tricks
Tips and Tricks
Here are my settings for the color/gamma controls!
Color:
Red -> 60%
Green -> 45%
Blue -> 45%
Gamma:
Red -> 0
Green -> -5
Blue -> 5
Why does the color/gamma controls get set to a value other than what I've set?
This is something I have not yet resolved, but I have noticed that it seems to jump up by 5. So if you want 50% for example, try setting it to 45%.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
How do I take a dmesg (kernel log)?
It's fairly simple, open up your terminal then type the following:
$ su
$ dmesg > /storage/sdcard0/dmesg.txt
Click to expand...
Click to collapse
This will save the log to the root of your sdcard as dmesg.txt. Just post that or send it to [email protected] if it's to large to post here
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Flashing Recovery for the First Time
Flashing CWM for the First Time
This is a pretty simple step once you get past the install recovery script which I'll explain how to accomplish. Make sure you follow the instructions closely because Odin, the program the we use to bypass the security, can do some serious damage to your phone if your not careful.
1) Download the latest CWM tar.md5 to your computer from my androidfilehost.com repo here:
http://www.androidfilehost.com/user/?w=settings-dev-files&flid=12461
2) Download Odin 1.8.5 zip and extract all the files to a folder on your computer (i use my desktop):
http://www.androidfilehost.com/?fid=23501681358544719
3) The drivers are very touchy on windows computers, so I recommend that you install Samsung Kies which will ensure that the drivers are installed and setup correctly. You can download kies from here:
http://www.samsung.com/ca/support/usefulsoftware/KIES/JSP
4) Be careful now that you have kies installed, it does not play nicely with Odin, so whenever you use Odin, you should ensure that kies is completely closed and not open in the system tray by opening your Task Manager and "End Task" to any kies process such as "Kies.exe" and "KiesTrayAgent.exe"
5) Now, with kies closed, open Odin and do not change any settings. It should look like this:
6) Now click on the Bootloader button and search for the CWM tar.md5 you downloaded from my androidfilehost.
7) Now turn off your phone, and when it's powered off, press and hold the volume down and power buttons at the same time until you see the warning message about Download mode. Press volume up to enter download mode.
8) With Kies closed on your computer and Odin open cwm tar.md5 loaded into the bootloader section and your phone in Download mode, plug your phone into the computer with your micro usb cord and wait for odin to display a "Device Added" message which tells you that odin sees your phone.
9) This is the tricky part and is all based on timing, so pay close attention.
10) You will now press the "Start" button in odin and wait for it to complete. It will display a green "Pass" message in the first box when it's done. At this time, the phone will reboot and will start with a slight vibration to notify you that it's booting up. It's exactly at the time that the phone vibrates that you need to immediately remove the micro usb cord and press and hold the volume up and volume down buttons simultaneously until cwm loads. If you miss this mark, android will boot, the install_recovery.sh script will run and overwrite the cwm you just flashed with the old stock 3e recovery (arghhh) and you will have to go through this process again.
If CWM complains about the install_recovery script, let it fix/remove it.
Once you have CWM flashed, you can use it to backup/restore your system, flash custom ROMs and you can even flash our CWM upgrades through CWM itself.
First Wood Woot !! And many thankyous.
Update-
This Rom is flawless so far. I have no issues that existed for me in CM10.2JB . Status Bar doesn't freeze. Apps aren't killed mid use. Calender sync was fixed by installing Google calendar from play store and then removing it. (I use Cal app). There's almost no lag in multi tasking. I'm very happy.?? kit Kat!
Let's all hit TFs donate button with a few bucks, eh?
Much appreciated. Downloading now.
Sweet, a thread here instead of g+!
Sent from my SGH-I757M using xda premium
For me the gallery issue was gone after switched to the next branch.
Crossbreeder won't install (it did on the earlier 4.4 builds).. but Adaway works just fine and everything's working smoothly. Love the music in the lockscreen! also noticed there's even more governor parameters to tweak, which is always a good thing
formercontra said:
Crossbreeder won't install (it did on the earlier 4.4 builds).. but Adaway works just fine and everything's working smoothly. Love the music in the lockscreen! also noticed there's even more governor parameters to tweak, which is always a good thing
Click to expand...
Click to collapse
That's due to the new recovery. If your on a Windows system, download 7zip if you don't have it already.
Here's what you do, open this roms zip file and extract only the update-binary from META-INF/com/google/android to a location on your computer. Then you can close the ROM zip. Now open the crossbreeder zip with 7zip and browse to META-INF/com/google/android and simply drag the extracted update-binary into the crossbreeder zip file replacing it's update-binary with the one from cm-11. Then close the zip and upload to your phone and flash away
Sent from my SGH-I757M using XDA Premium 4 mobile app
After running ROM for a few hours, I'm quite impressed. No issues so far. I will continue using it and report any findings. Thanks titanic for all your time and effort.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Phone won't boot
I flashed the rom and the gapps but I get no boot screen. I waited about five minutes and nothing happened. Any ideas on what went wrong??
Amazing
It's is so smooth, I am ecstatic to see how it'll be when ART becomes functional!
Thanks again!
omar.kassam97 said:
I flashed the rom and the gapps but I get no boot screen. I waited about five minutes and nothing happened. Any ideas on what went wrong??
Click to expand...
Click to collapse
Did you wipe and factory reset? Did you use the wipe to install new rom option?
This ROM must be flashed clean. No dirty flashing unless you already had cm-11 flashed.
Sent from my SGH-I757M using XDA Premium 4 mobile app
I am curious, in your 10.2 thread you said the calendar could not be assigned a gmail account in cm 11.
Was this resolved? For me it's a deal breaker (loving your cm10.2 anyways).
If it hasn't been fixed could we add it to the OP in the what doesn't work section?
Sent from my SGH-I757M using xda app-developers app
slushee said:
I am curious, in your 10.2 thread you said the calendar could not be assigned a gmail account in cm 11.
Was this resolved? For me it's a deal breaker (loving your cm10.2 anyways).
If it hasn't been fixed could we add it to the OP in the what doesn't work section?
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
No, it's unfortunately not fixed and will definitely add that to the op
Sent from my SGH-I757M using XDA Premium 4 mobile app
Way to go Titanic! I will flash tomorow and try this one out.
Sent from my SGH-I757M using xda app-developers app
Philz touch cwm was just updated and now uses a new exfat module for mounting the sdcards. It's supposed to be faster than the fuse alternative. This version also fixes the resolution of the background image, the software buttons and the vibration.
http://forum.xda-developers.com/showthread.php?t=2552634
Sent from my SGH-I757M using XDA Premium 4 mobile app
The calendar works in slim. I think the calendar sync adapter is missing in cm-11. Can I get someone to add this apk to your /system/app dir give it the same permissions as the others, then reboot and try connecting the calendar to your Google account. I'm out of the house right now so can't test it myself.
titanic_fanatic said:
The calendar works in slim. I think the calendar sync adapter is missing in cm-11. Can I get someone to add this apk to your /system/app dir give it the same permissions as the others, then reboot and try connecting the calendar to your Google account. I'm out of the house right now so can't test it myself.
Click to expand...
Click to collapse
Yep, that worked. My Google account syncs now and i can create events. Thanks TF!
Sent from my SGH-I757M using xda premium
bijon440 said:
Yep, that worked. My Google account syncs now and i can create events. Thanks TF!
Sent from my SGH-I757M using xda premium
Click to expand...
Click to collapse
Excellent, I'll update the gapps package when I get home thanks for testing
Sent from my SGH-I757M using XDA Premium 4 mobile app
SlimKat 4.4 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2/CM11.0, you are required to update
your recovery to a supported recovery with a version greater than 6.0.39. As of this writing, the latest available
version is Philz Touch Recovery 6.57.9 (based on CWM 6.0.5.1) for the SGH-I757M. There is currently not a
version of regular CWM for this device that will flash Kit Kat ROMs.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D SlimKat (Android4.4.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). There is a lot to be said about Kit Kat with it's clean white icons and new launcher. The focus with Kit Kat was to make the device use less RAM and imrove performance, and so far it's running great. Art seems to be fully functional in SlimKat and the device runs smooth ;-)
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera (Camcorder doesn't work right now. Don't select it or you'll mess up the camera all together)
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
* USB Mass Storage (UMS mode)
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* Not only does the camcorder not work, but selecting it will cause the camera to not function at all, so be careful not to select camcorder. There is currently no fix if you accidentally select camcorder mode, so be careful or you may need to reflash the ROM to get the camera working again. I'm working on a solution that will at least not put it into this loop for now.
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new Philz Touch Recovery 6.57.9 flashable zip which is compatible with CM10.1/CM10.2/CM11.0/SlimKat
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the philz_touch_6.57.9-celoxhd.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios (Required before you flash the ROM, unless you already have the new JB radios flashed)
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: Using Philz Touch Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20141126 (Latest)
ROM: Slim-celoxhd-4.4.4.build.8.16-UNOFFICIAL-20141126-1146.zip (142.0MB)
GAPPS: Slim_mini_gapps.4.4.4.build.8.x-385.zip (64.01MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A clean flash is REQUIRED if upgrading from a previous version of android such as CM10.2/SlimJB4.3.
Build: 20141005
ROM: Slim-celoxhd-4.4.4.build.8.2-UNOFFICIAL-20141002-1545.zip (142.6MB)
GAPPS: Slim_mini_gapps.4.4.4.build.8.x-282.zip (60.2MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.13.2 (CWM 6.0.4.7) compatible with CM10.1/CM10.2/CM11.0/SlimKat
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]November 26, 2014 - Build 20141126[/B]
* Increased kernel version to Titanium 1.1.1
* Added cpu input boost framework - credit: sultanxda
* Added cpu OC (The scale goes up to 1890MHz, but you should only put it as high as 1836MHz since I was getting random reboots with 1890MHz. 1674MHz is the default OC and 1512MHz is the default CM OC) - credit: TeamFahQ/sultanxda/titanic-fanatic
* Added low power flash mode which will use a low powered flash when the battery is equal to or below 35%. This should help with the camera causing the phone to shut down when trying to take pictures using the flash. This threshold may need to be tweaked, so please let me know if you still experience shut downs related to using the camera. - credit: sultanxda
* Added sgs2hdbell as a device name to the updater-script to allow all bell i757m devices to flash the ROM without the need to edit the updater-script.
* Added panel undervolt interface. - credit: sultanxda
* More memory optimizations. Some of the extra RAM that the previous optimization gave us has been allocated to other things such as the surface flinger. Available RAM is now around ~760MB.
* Removed vbus_present wakelock for good (it worked it's way back in somehow)
* Added fast charge. Phone will now charge at 1200mA until 95% regardless of your charging source (AC/USB)
* Added exFAT driver to kernel. It's a filesystem like ext4 but is based on Windows FAT filesystem. You can format your sdcard as exFAT as it's supposed to be faster than vFAT which is what our sdcards are formatted as. Make sure you backup your sdcard contents before formatting it as exFAT and keep the backup until your sure you want to stick with exFAT.
* Removed NFC since I don't think anyone uses it and can't figure out how to have it disabled by default so it is removed completely. If someone is using NFC, let me know and I'll add it back but for now, I just see it as a battery drain.
[COLOR="Red"][B]NOTE:[/B] With the overclocking of this kernel, all antutu tests passed up to 1836MHz. At 1890MHz, antutu caused the phone to reboot during the String Sort tests. This is so far the only thing that has caused reboots, but there may be other actions that will cause this too. If you find that your device is randomly rebooting, turn the overclock down by one step (ie: from 1836MHz to 1782MHz which is one step lower). Then go back to using your phone normally. If you still get random reboots, keep turning the OC down until it doesn't happen anymore.[/COLOR]
[B]October 5, 2014 - Build 20141005[/B]
* Kernel now has a custom version number in addition to my kernel name of Titanium
* Optimized kernel memory mapping to increase our physical RAM from ~730MB to ~800MB (a whole 70 extra MB... whoa!)- credit: sultanxda
* Removed mDNIe (it's not supported/working)
* Removed 91fixoverlays script (no longer needed)
* Removed persist.hwc.mdpcomp.enabled from build.prop (hack to fix the hwoverlays because fb drivers are broken somehow) - credit: sultanxda
* Added GPU overclock from 266MHz to 320MHz (helps a lot with the UI lag) - credit: sultanxda
* Added code for 2 phase OnDemand governor - credit: sultanxda
* Added opensource frandom module to help speed up the UI (also helps with the lag) - credit: bryan2894
* Added mdp Color Enhancements (better display color) - credit: sultanxda
* Added color/gamma controls in place of mDNIe (see the tips and tricks section for my already tweaked favorite settings) - credit: bryan2894/titanic_fanatic (I had to integrate it into our display drivers)
* Added Swipe 2 Wake (S2W) support in the kernel (it's actually tap once on each key from left to right). - credit: bryan2894
* Added audio.r_submix.default.so to the build to enable screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary audio channels in the audio_policy.conf for screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary settings in Advanced Device Settings for screencasting and color/gamma control - credit: bryan2894/titanic_fanatic (I added the screencasting settings)
* Fixed the annoying BLN sticking (I think... Please confirm this for me) - credit: bryan2894
* Fixed the sampling rates for A2DP, input and r_submix channels - credit: bryan2894
* Changed both scaling governors to OnDemand - credit: bryan2894
[B]August 16, 2014 - Build 20140816[/B]
* Synced with sources
* Added sysfs interface for vibrator intensity control
* Added settings to control vibrator intensity in Advanced Device Settings
* Moved Advanced Reboot Options to Developer Options
* Fixed FC in Settings app when trying to access Security Settings
* Added Omni Performance Control
[B]April 12, 2014 - Build 20140412[/B]
* Synced with sources
* Fixed network selection dialog
* Added USB Mass Storage mode (UMS)
[B]March 19, 2014 - Build 20140319[/B]
* Synced with sources
* Removed 91fixoverlays script (hw overlays no longer need to be disabled)
[B]February 12, 2014 - Build 20140207[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. Reboot your phone and you should be rooted.
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @Socim - Thanks to Socim for pointing me in the right direction a few times ;-)
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL SlimKat KK4.4 For Bell SGH-I757M, ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
Source Code: https://github.com/titanic-fanatic
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: SlimKat
Version Information
Status: Alpha
Created 2014-02-12
Last Updated 2014-12-09
Tips & Tricks
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Anyway to remove the status bar pull down lag? Everything else runs great! :good:
iDynamics said:
Anyway to remove the status bar pull down lag? Everything else runs great! :good:
Click to expand...
Click to collapse
Not currently. Maybe changing the governor will help. Oh also, turn on art in dev options
Sent from my SGH-I757M using XDA Premium 4 mobile app
THANK YOU!!!!
TF ur AMAZING!! thank you so much.... ive benn waiting soooo long for this :laugh::good::victory:
I am very ocd about having a smooth status bar. I will stay with your fantastic 10.2 rom until this issue is fixed.
This ROM is way smoother than the cm11 build. Looking forward to the camcorder fix!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Settings bug.
If enter to Developer options then App error in Security options.
And if enter to Security - error in developer.
Alexander Kalinin said:
Settings bug.
If enter to Developer options then App error in Security options.
And if enter to Security - error in developer.
Click to expand...
Click to collapse
I ripped the settings.apk from the hercules slimkat build on slimbeans official site then put it into this rom's zip and flashed. It solved the security FC.
iDynamics said:
I ripped the settings.apk from the hercules slimkat build on slimbeans official site then put it into this rom's zip and flashed. It solved the security FC.
Click to expand...
Click to collapse
I'm having the same issue with security menu. Would you mind posting the settings.apk you ripped? I'd like to try it out. Thanks in advance idynamics.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
manfromgta said:
I'm having the same issue with security menu. Would you mind posting the settings.apk you ripped? I'd like to try it out. Thanks in advance idynamics.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Put it in /System/Priv-App
http://www.mediafire.com/download/s29lianid2y89i6/Settings.apk
Having Issues in dailer......when i open dialer it says dialer is not Responding report....Plz help me how to fIx it??
sandhu6698 said:
Having Issues in dailer......when i open dialer it says dialer is not Responding report....Plz help me how to fIx it??
Click to expand...
Click to collapse
You will have to learn how to take a logcat to post here after the error occurs. Instructions are in the second post.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Whats logcat sir ?? M just telling u the problem m facing....plz tell me what can i do i will follow you
Sent from my SGH-I757M using XDA Premium 4 mobile app
Heres a screenshot
Sent from my SGH-I757M using XDA Premium 4 mobile app
Sir....why do i see these red colour borders at edges..??? I tired to edit build.prop.type to user but its not changing? ...i mean i change it from eng to user ...but afret reboot it changes back to eng ......m using ROM Toolbox for build.prop.editor
Anyway to fix it ??
Sent from my SGH-I757M using XDA Premium 4 mobile app
sandhu6698 said:
Sir....why do i see these red colour borders at edges..??? I tired to edit build.prop.type to user but its not changing? ...i mean i change it from eng to user ...but afret reboot it changes back to eng ......m using ROM Toolbox for build.prop.editor
Anyway to fix it ??
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Back in late December titanic addressed and fixed this bug in 10.2 rom. Read post #8 from his 10.2 thread to see if it helps.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
sandhu6698 said:
Sir....why do i see these red colour borders at edges..??? I tired to edit build.prop.type to user but its not changing? ...i mean i change it from eng to user ...but afret reboot it changes back to eng ......m using ROM Toolbox for build.prop.editor
Anyway to fix it ??
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is definitely due to the build type, but this roms build.prop already has the build type set to user. Did you do a clean flash if you came from another rom? Did you modify the build.prop at all before this happened?
Your build.prop editor needs root access and by default, this rom is set to root for adb only. You can change that in the developer options to allow both apps and adb to gain root. Then your build.prop edits should stick.
I'm still confused how you have a build.prop with build type set to eng though since the build type is set to user in my rom. My Best guess is that you came from rukusx7's hellkat rom and didn't wipe before you flashed this one. That would save your system files and maybe cause some conflicts which might explain your issue with the dialer. My suggestion to you is to always wipe/factory reset when flashing new roms. This will minimize the potential for problems.
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
This is definitely due to the build type, but this roms build.prop already has the build type set to user. Did you do a clean flash if you came from another rom? Did you modify the build.prop at all before this happened?
Your build.prop editor needs root access and by default, this rom is set to root for adb only. You can change that in the developer options to allow both apps and adb to gain root. Then your build.prop edits should stick.
I'm still confused how you have a build.prop with build type set to eng though since the build type is set to user in my rom. My Best guess is that you came from rukusx7's hellkat rom and didn't wipe before you flashed this one. That would save your system files and maybe cause some conflicts which might explain your issue with the dialer. My suggestion to you is to always wipe/factory reset when flashing new roms. This will minimize the potential for problems.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did a clean flash now the Roms rocks .....m using it battery life is also great in this slim kat rom .....
iDynamics said:
Put it in /System/Priv-App
http://www.mediafire.com/download/s29lianid2y89i6/Settings.apk
Click to expand...
Click to collapse
I replaced Settings.apk in the SlimKat zip with the one you uploaded to mediafire. Booted into recovery, wiped system and cache and flashed the fixed zip. I still FC upon selecting Security. Any suggestions?
Carbon KitKat for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
*** Disclamer ***
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on
Click to expand...
Click to collapse
*** NEW RECOVERY REQUIRED ***
Due to the addition of user control in CM10.1/CM10.2/CM11.0, you are required to update
your recovery to a supported recovery with a version greater than 6.0.39. As of this writing, the latest available
version is Philz Touch Recovery 6.57.9 (based on CWM 6.0.5.1) for the SGH-I757M. There is currently not a
version of regular CWM for this device that will flash Kit Kat ROMs.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.
Click to expand...
Click to collapse
*** NEW RADIO FIRMWARE REQUIRED ***
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).
Click to expand...
Click to collapse
Introduction
We now have an AOSP (Android Open Source Project) ROM available for our beloved SGH-I757M. This one is called Carbon and boasts many features from CM/PA/Slim/AOKP. It features SlimPie, customizable ribbons, Active display, Screen Recorder, Screencast and more. Please check out the carbon features page for a full list:
Carbon ROM Feature List with Screenshots
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new Philz Touch Recovery 6.57.9 flashable zip which is compatible with KitKat based ROMs
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the philz_touch_6.57.9-celoxhd.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios (Required before you flash the ROM. You can skip this step if you already have the new JB radios flashed)
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: Using Philz Touch Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140125 (Latest)
ROM: CARBON-KK-UNOFFICIAL-20150125-1436-celoxhd.zip (178.2MB)
PA GAPPS: PA Modular Mini GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Build: 20141121
ROM: CARBON-KK-UNOFFICIAL-20141121-0351-celoxhd.zip (178.2MB)
PA GAPPS: PA Modular Mini GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A clean flash is REQUIRED if upgrading from a previous version of android such as CM10.2
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.57.9 (CWM 6.0.5.1) compatible with KitKat based ROMs
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* I no longer upload files to XDA because it takes way to long to manage, so I only use androidfilehost.com. All files can be found under my profile: https://www.androidfilehost.com/?w=files&flid=7547
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
January 25, 2015 - Build 20140125
* Increased Kernel version to Titanium 1.2.1
* Added kernel based thermal mitigation sensor - credit: sultanxda
* GPU ion backport from LA.AF.1.1_rb1.7 - credit: sultanxda
* New Bluetooth/WiFi drivers ported from the S5 - credit: sultanxda
* Revert change to camera wrapper that cause photos to be taken in portrait
* Increase low power flash threshold to 60%
* Add Sweep2Sleep (S2S) - credit: Emmanuel U
* Add sensitive option for S2S/S2W - credit: Emmanuel U
* Add settings Advanced Device Settings to control the S2S and S2W/S2S Sensitive settings
* Add Enhanced BLN - credit: sultanxda
* Updated Advanced Device Settings to work with the new Enhanced BLN driver
* Add kernel tab to Advanced Device Settings for kernel control settings
* Moved panel UV setting to kernel tab in Advanced Device Settings
* Removed ROMStats and CarbonDelta since we don't use them and they only consume battery and network bandwidth
* Increased vmalloc size from 400MB to 512MB - credit: sultanxda
* Add Dynamic System Bars from Paranoid Android ROM
November 21, 2014 - Build 20141121
* Increased kernel version to Titanium 1.1.1
* Added cpu input boost framework - credit: sultanxda
* Added cpu OC (The scale goes up to 1890MHz, but you should only put it as high as 1836MHz since I was getting random reboots with 1890MHz. 1674MHz is the default OC and 1512MHz is the default CM OC) - credit: TeamFahQ/sultanxda/titanic-fanatic
* Added low power flash mode which will use a low powered flash when the battery is equal to or below 35%. This should help with the camera causing the phone to shut down when trying to take pictures using the flash. This threshold may need to be tweaked, so please let me know if you still experience shut downs related to using the camera. - credit: sultanxda
* Added sgs2hdbell as a device name to the updater-script to allow all bell i757m devices to flash the ROM without the need to edit the updater-script.
* Added panel undervolt interface. - credit: sultanxda
* More memory optimizations. Some of the extra RAM that the previous optimization gave us has been allocated to other things such as the surface flinger. Available RAM is now around ~760MB.
* Removed vbus_present wakelock for good (it worked it's way back in somehow)
* Added fast charge. Phone will now charge at 1200mA until 95% regardless of your charging source (AC/USB)
* Added exFAT driver to kernel. It's a filesystem like ext4 but is based on Windows FAT filesystem. You can format your sdcard as exFAT as it's supposed to be faster than vFAT which is what our sdcards are formatted as. Make sure you backup your sdcard contents before formatting it as exFAT and keep the backup until your sure you want to stick with exFAT.
* Removed NFC since I don't think anyone uses it and can't figure out how to have it disabled by default so it is removed completely. If someone is using NFC, let me know and I'll add it back but for now, I just see it as a battery drain.
NOTE: With the overclocking of this kernel, all antutu tests passed up to 1836MHz. At 1890MHz, antutu caused the phone to reboot during the String Sort tests. This is so far the only thing that has caused reboots, but there may be other actions that will cause this too. If you find that your device is randomly rebooting, turn the overclock down by one step (ie: from 1836MHz to 1782MHz which is one step lower). Then go back to using your phone normally. If you still get random reboots, keep turning the OC down until it doesn't happen anymore.
September 10, 2014 - Build 20140911
* Kernel now has a custom version number in addition to my kernel name of Titanium
* Optimized kernel memory mapping to increase our physical RAM from ~730MB to ~800MB (a whole 70 extra MB... whoa!) - credit: sultanxda
* Removed mDNIe (it's not supported/working)
* Removed 91fixoverlays script (no longer needed)
* Removed persist.hwc.mdpcomp.enabled from build.prop (hack to fix the hwoverlays because fb drivers are broken somehow) - credit: sultanxda
* Added GPU overclock from 266MHz to 320MHz (helps a lot with the UI lag) - credit: sultanxda
* Added code for 2 phase OnDemand governor - credit: sultanxda
* Added opensource frandom module to help speed up the UI (also helps with the lag) - credit: bryan2894
* Added mdp Color Enhancements (better display color) - credit: sultanxda
* Added color/gamma controls in place of mDNIe (see the tips and tricks section for my already tweaked favorite settings) - credit: bryan2894/titanic_fanatic (I had to integrate it into our display drivers)
* Added Swipe 2 Wake (S2W) support in the kernel (it's actually tap once on each key from left to right). - credit: bryan2894
* Added audio.r_submix.default.so to the build to enable screencasting - credit: THIS POST
* Added the necessary audio channels in the audio_policy.conf for screencasting - credit: THIS POST
* Added the necessary settings in Advanced Device Settings for screencasting and color/gamma control - credit: bryan2894/titanic_fanatic (I added the screencasting settings)
* Fixed the annoying BLN sticking (I think... Please confirm this for me) - credit: bryan2894
* Fixed the sampling rates for A2DP, input and r_submix channels - credit: bryan2894
* Changed both scaling governors to OnDemand - credit: bryan2894
July 5, 2014 - Build 20140705
* Sync with sources (Update to Android 4.4.4)
* Vibrator module now built into kernel
* Added sysfs for vibrator intensity to allow user control of the vibrator intensity
May 21, 2014 - Build 20140321
* Sync with sources
* Updated Slim Recents
* Switched to using media-caf
* Updated kernel with sources for media-caf
* Fixed issue with Google Camera resolution preferences FC
* Added back 91fixoverlays script due to graphics glitches with the new kernel
May 04, 2014 - Build 20140504
* Sync with sources
* Add Slim Recents app (Long press home to show)
* Fixed gesture control for pinch to clear in Slim Recents panel
* Fixed HW Key binding (You can now set the actions for the hw buttons events like longpress)
* Fixed reading of min/max values for cpu in new Omni Performance Control
March 21, 2014 - Build 20140321
* Sync with sources
* Removed 91fixoverlays script
* Fix Settings button on Homescreen overlay
February 25, 2014 - Build 20140225
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. Reboot your phone and you should be rooted.
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
* CarbonDev Team - ROM Source
* CyanogenMod Team - ROM Base
* SlimRoms Team - ROM Features
* AOKP Team - ROM Features
* ParanoidAndroid Team - ROM Features
Without all of the hard work and efforts of the CarbonDev team, CyanogenMod team, AOKP team and the Paranoid Android team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* @dsixda - Initial port of CM9/CM10 for SGH-I757M
* @Strange Peer - Continued development of CM10
* @rukusx7 - Contributor (Donated old phone for Development - Thanks!)
* @bijon440 - Contributor
* @kj2112 - Contributor
* @Tronith - Contributor
* @Zippy Dufus - Contributor
* @Socim - Thanks to Socim for pointing me in the right direction a few times ;-)
* @formercontra - Contributor
* @Sultanxda - Many bug fixes and improvements for the msm8660 kernel
Thanks guys you've all been so awesome to work with
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated
Click to expand...
Click to collapse
XDA:DevDB Information
UNOFFICIAL Carbon KitKat For Bell SGH-I757M, ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
Source Code: https://github.com/titanic-fanatic
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: AOSP
Version Information
Status: Stable
Created 2014-02-25
Last Updated 2015-01-26
Tips & Tricks
Tips and Tricks
Here are my settings for the color/gamma controls!
Color:
Red -> 60%
Green -> 45%
Blue -> 45%
Gamma:
Red -> 0
Green -> -5
Blue -> 5
Why does the color/gamma controls get set to a value other than what I've set?
This is something I have not yet resolved, but I have noticed that it seems to jump up by 5. So if you want 50% for example, try setting it to 45%.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
First! Running it for a bit thismorning and everything seems great. 1 thing, no halo? Not a big deal with the ribbons but I did like that. Good work! Ill buy you a beer yet my friend!
Sent from my SGH-I757M using xda premium
This ROM is the kats meow. Love the features. After a full days use, no lock ups, lag or random reboots. Its early yet for battery stats but so far with on demand/deadline combo I'm at 62% remaining after 15 hours of average use. One thing of note: From home screen- clicking menu/settings is not functional. Settings from app drawer works as it should. This ROM is now my daily driver. Thanks for the continued support. May the S2 live on!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
I might have to try this build out. Battery life is my biggest thing.
I found that deadline for a scheduler is best for this phone with almost any governor. I don't know why.
That's what I'm on, ondemand and deadline yeah, and I'm loving this ROM. It's got some pretty cool features
Sent from my SGH-I757M using XDA Premium 4 mobile app
this rom is great, i was just wondering whats the easiest way for me to leave hw overlays unchecked when loading os?
rukusx7, whats the likelyhood of you making an installable zip of your kernel?
ashfrel1984 said:
this rom is great, i was just wondering whats the easiest way for me to leave hw overlays unchecked when loading os?
Click to expand...
Click to collapse
You can remove the init.d at /system/etc/init.d/91fixoverlays
It will be really speedy after that, but you may still run into some graphics glitching. Possibly enough to cause the kernel to panic and reboot. You can always replace the script at a later time if that becomes an issue.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Took the plunge, just installed this tonight. Hope everything goes well!!
so far ive been lucky (no glitches), but what a speed difference for me. thanks for the info.
Without hw overlays enabled this rom most certainly speeds up. Great job as always t_f.
titanic_fanatic said:
You can remove the init.d at /system/etc/init.d/91fixoverlays
It will be really speedy after that, but you may still run into some graphics glitching. Possibly enough to cause the kernel to panic and reboot. You can always replace the script at a later time if that becomes an issue.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In my hellkat rom, this is usually green lines that glitch across the screen. I tend to have problems with RR's with Disable Hardware Overlays unchecked.
Have you made any major changes to the kernel to help with hardware overlays?
rukusx7 said:
In my hellkat rom, this is usually green lines that glitch across the screen. I tend to have problems with RR's with Disable Hardware Overlays unchecked.
Have you made any major changes to the kernel to help with hardware overlays?
Click to expand...
Click to collapse
No actually, so that goes to show that it might not be entirely related to the kernel which I originally thought the case. I'll have to diff cm with carbon to see what differences there are.
Sent from my SGH-I757M using XDA Premium 4 mobile app
iDynamics said:
Without hw overlays enabled this rom most certainly speeds up. Great job as always t_f.
Click to expand...
Click to collapse
Seriously, some devs had given up on fixing project butter, but I always impressed with what titanic_fanatic brings to our device!!! I might switch to this rom if it works so well. I'll do builds with DIABLO or UBER kernel perhaps, Also dont forget the work that TF is doing to his kernel as well. our kernel diff's slightly from the hercules and skyrocket (which mine is based on), and he will likely have a kernel that is tweaked specifically to our device.
Great work @titanic_fanatic!!
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
titanic_fanatic said:
No actually, so that goes to show that it might not be entirely related to the kernel which I originally thought the case. I'll have to diff cm with carbon to see what differences there are.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, I've been all stuck on the kernel as well. But I agree its starting to not appear as so. You're making some amazing advancements lately!!!
iDynamics said:
Without hw overlays enabled this rom most certainly speeds up. Great job as always t_f.
Click to expand...
Click to collapse
With your hw overlays disabled, do you get graphical glitching in the gallery? I get those lines rukusx7 was talking about.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Might have just found a really easy fix for the graphics glitching... FACE PALM Only time will tell though. Navigate to /system/lib/egl and edit egl.cfg. you will see this:
0 0 android
0 1 adreno200
Click to expand...
Click to collapse
Change this to:
0 0 adreno200
0 1 adreno200
Click to expand...
Click to collapse
This will force the device to always use adreno200 for graphics processing. I don't get those wavy lines in gallery anymore with hw overlays enabled, and I haven't had any screen flickering yet either. Not sure what this means for battery yet, but this might just be a step in the right direction
Please let me know how this works out for you guys.
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Might have just found a really easy fix for the graphics glitching... FACE PALM Only time will tell though. Navigate to /system/lib/egl and edit egl.cfg. you will see this:
Change this to:
This will force the device to always use adreno200 for graphics processing. I don't get those wavy lines in gallery anymore with hw overlays enabled, and I haven't had any screen flickering yet either. Not sure what this means for battery yet, but this might just be a step in the right direction
Please let me know how this works out for you guys.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I made the change this morning. Will report back later. Thanks TF!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Well after 10 hours with your little trick TF the results are positive. No glitches or weird lines through screen. Overlays were unchecked as well. The battery life seems unaffected by the changes in my view. The overlays do not stay unchecked through reboot. I suppose this will be changed if you find this fix to be effective. This is awesome. Thanks once again!
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
titanic_fanatic said:
Might have just found a really easy fix for the graphics glitching... FACE PALM Only time will tell though. Navigate to /system/lib/egl and edit egl.cfg. you will see this:
Change this to:
This will force the device to always use adreno200 for graphics processing. I don't get those wavy lines in gallery anymore with hw overlays enabled, and I haven't had any screen flickering yet either. Not sure what this means for battery yet, but this might just be a step in the right direction
Please let me know how this works out for you guys.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just applied the egl.cfg fix to your Slim build, removed the init.d script and rebooted with HW overlays unchecked. Improvement was noticed, and no glitching so far.
To make your external sdcard usable by apps, use the terminal emulator and
$ su
$ chmod 777 /mnt/media_rw
Click to expand...
Click to collapse
Now you should be able to use your sdcard for whatever
Sent from my SGH-I757M using XDA Premium 4 mobile app
EDIT:
You will have to do this every boot for now.
Hi XDA! I'm the developer of VRTV, a video player for Cardboard. I'm running an open beta of my latest release, and I was hoping I could get some feedback here. Hope this doesn't count as me spamming. The app is free, with a banner ad, but there is a paid version available.
Anyway, here's a small description of the news in 3.0 beta:
Big news:
Uses libVLC backend, with support for replacing the decoding library.
Regular 2D video player UI.
Configurable bluetooth controls.
Smaller news:
Support for 220/270 degree panoramas.
Audio track selection.
Guess video config from filename.
Setting for phones/headset in reverse landscape configuration.
Like MX Player, I've disabled support for DTS/AC3, but you can build and load your own libvlcjni.so from the libvlc source code if you are not under the jurisdiction of software patents. To get the correct version I recommend using the same source as I used to build the version that's distributed with the app. Link below.
The other big new thing in 3.0 is that I've implemented a simple "normal" video player UI, so ideally you would get by with VRTV for all your videos and can set it as the default video player. Something that's been bugging me with VRTV for a while (and with most other players I believe). Uncheck "VR Player" to use the regular player.
I use the beta functionality in the Play Store, so to join, click the appropriate link below to join the beta with your Google account, then find VRTV in the Play Store to update to the beta.
https://play.google.com/apps/testing/se.chai.vrtv.free
https://play.google.com/apps/testing/se.chai.vrtv (requires buying/owning the paid version)
Follow the link below to get the source code for libvlc used in VRTV. Let me know if you would be willing to help me test loading a self-built library!
https://github.com/svenhenrik/vlc_vrtv_1.7.x
Any feedback is valuable, and if you have the ability to provide logs for crashers I will love you forever! Especially Nougat seems to be a bit troublesome, and I don't have a device to test with myself.
Hi Sven,
I bought the pro app in the Play store and I am willing to build my own libvlcjni.so. From all the players I have tried so far your app had the best results for non-VR 3D-movies by far.
I will install an Ubuntu on an usb stick tonight and have a couple of questions since I am not familiar with developing in Linux.
- Will it compile correctly under 64-it linux?
- What settings do I have to change to enable AC3/DTS?
- Do I need the Android SDK or just the libraries mentioned at https://wiki.videolan.org/AndroidCompile/?
So I will just do a
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install zlib1g:i386 libstdc++6:i386 libc6:i386
sudo apt-get install automake ant autopoint cmake build-essential libtool \ patch pkg-config protobuf-compiler ragel subversion unzip git
git clone https://github.com/svenhenrik/vlc_vrtv_1.7.x
./compile.sh --release -l -a armeabi-v7a
Copy the new libvlcjni.so to data/app/se.chai.vrtv-1/lib
?
Thank you for your help.
OK, I ran into a couple of issues (some URLs where additional packages were being fetched were dead, you need to use NDK 10e because newer versions are missing the required release.txt, you need to install Oracle Java and set the JAVA_HOME variable).
ColinMacLaren said:
OK, I ran into a couple of issues (some URLs where additional packages were being fetched were dead, you need to use NDK 10e because newer versions are missing the required release.txt, you need to install Oracle Java and set the JAVA_HOME variable).
Click to expand...
Click to collapse
Hi, so sorry for not checking in here sooner to help. Did you manage to get it all to compile? Let me know if you have more questions, I'll check a little more often
I'll update the patch later today with the new contrib links. I really should upgrade VLC since they released a new version recently, I used the one that was released when I started adding support.
I'll add the part about needing NDK r10e to the instructions, thanks!
ColinMacLaren said:
- What settings do I have to change to enable AC3/DTS?
Click to expand...
Click to collapse
Missed this part. You basically want to revert my changes relating to the a52 library. These are the modifications I've made:
- Make sure to use the last tested SHA of VLC instead of the latest checkout, to get some stability in what VRTV is using.
- Disable GPL, and fix building without GPL libraries (all changes relating to -lmad and -lpostproc
- Disable a52, in both the vlc build script and in the ffmpeg config.
The latter two are mixed and spread over two commits unfortunately so you can't just revert them.
https://github.com/svenhenrik/vlc_vrtv_1.7.x/commit/39bfc574661484f3d6e6f4371c1582aec57dbe35
Here you need to remove the --disable-a52 lines and add back the linker flag -la52 that was removed.
https://github.com/svenhenrik/vlc_vrtv_1.7.x/commit/961142382010ef3bb74028163cd66e11244d139a
Remove the --disable-decoder lines the patch added to vlc/contrib/src/ffmpeg/rules.mak
I think I might have had to add --enable-a52 to the compile script to get it to pick up the changes when rebuilding, try that if it doesn't download the a52 contrib lib or doesn't link.
By the way, the latest beta supports reading zip:ed libvlcjni.so files (make sure it's the only file in the archive).
Also gave this a shot. The developer still hasn't updated the source with new links to libraries, but I managed to get it to build and load after some tinkering.
If anyone else wants AC3/DTS support but can't build it themselves, PM me, new account so I can't post links.
Where do I put the zipped library and what are the naming restrictions?
ColinMacLaren said:
Where do I put the zipped library and what are the naming restrictions?
Click to expand...
Click to collapse
Haven't tried zip, but if you pick "load library" in the menu in VRTV you get a file browser so just put the file anywhere on the phone.
Instructions
A paid customer and also joined the Beta testing team.. Want to say thank you for this great Video player. Took me a while to land on it after trying so many VR players.
Two questions.
Are there better instructions anywhere?
1.) How / where to find Codec's for this? Trying to play .MKV files (no audio)
UPDATE: used VLC codec, thanks..
2.) Is there a way to have the filename syntax , pre-configure settings on video type, VR DOME etc.., so it starts without having the non-3D menu first ? Does this make sense?
Using;
Note 5 -Samsung Gear VR, streaming videos from Local NAS
sounds cool. will give it a try
Cool. Will give it a try
[WIP] Docker Build Steps
This isn't working but I thought I'd post anyone, I will edit when I figure out what I'm missing.
If you already have a build environment setup these steps may or may not be helpful, but here's what I did to build the library file with docker:
Code:
# Grab a docker image that's has the NDK and SDK install for you
docker pull dbndev/android-ndk-r12b-build-samples
# Grab the source for building VRTV's VLC Lib, and checkout the version before any changes were made
git clone https://github.com/svenhenrik/vlc_vrtv_1.7.x
cd vlc_vrtv_1.7.x
git checkout 58181046e79112450a3362df7195cc35dd332096
# EDIT compile.sh, otherwise gradle don't download, the url changed, and redirect isn't caught. Note change xxxx to http, I can't post links with my account
# ORG: GRADLE_URL=xxxx://services.gradle.org/distributions/gradle-${GRADLE_VERSION}-all.zip
# NEW: GRADLE_URL=xxxx://downloads.gradle.org/distributions/gradle-${GRADLE_VERSION}-all.zip
docker run -it --rm -v $(pwd):/build_vlc -w /build_vlc dbndev/android-ndk-r12b-build-samples bash
# Install needed tools and setup the environment for building
apt-get update
apt-get install zlib1g:i386 libstdc++6:i386 libc6:i386
apt-get install automake ant autopoint cmake build-essential libtool patch pkg-config protobuf-compiler ragel subversion unzip git
export ANDROID_SDK=/opt/android-sdk-linux
export ANDROID_NDK=/opt/android-ndk-r12b
echo "r10 (64-bit)" > $ANDROID_NDK/RELEASE.TXT
./compile.sh --release -l -a armeabi-v7a
exit
There should now be a libvlcjni.so around xKB in the root of the vlc_vrtv_1.7.x directory, copy to android and enjoy audio!
Here's the error I'm having now, it looks like I'm trying to build a 32bit library on a 64bit OS, and looks like I need to set some other envs to get past this.
Code:
configure: error: in `/build_vlc/vlc/contrib/contrib-android-arm-linux-androideabi/fribidi':
configure: error: C compiler cannot create executables
See `config.log' for more details
../../contrib/src/fribidi/rules.mak:26: recipe for target '.fribidi' failed
make: *** [.fribidi] Error 77
contribs: make failed
Getting the same thing on mac when trying the following. Hope someone know's how to fix this issue.
Code:
------ NATIVE MAC ------
Download Android studio
Configure / SDK Manager / SDK Tools / NDK
Open the vlc_vrtv_1.7.x folder (maybe not needed who knows...)
echo "r10 (64-bit)" > $HOME/Library/Android/sdk/ndk-bundle/RELEASE.TXT
brew install automake ant cmake libtool patchutils pkg-config protobuf ragel subversion
ANDROID_SDK=$HOME/Library/Android/sdk ANDROID_NDK=$HOME/Library/Android/sdk/ndk-bundle ./compile.sh --release -l -a armeabi-v7a
Hi.
Also using the paid version and I really like the app, it's the best yet!
Two things I'd like to see and it would be even better:
1. support for web streams. Youtube, vimeo, etc.
2. automatic switch off for locked view when browsing your videos in app. It's impossible to click on the X when the image follows your head.
- Mik
Version 3.2 beta / vc61
Not sure what happened since last update, but the back button does not exit from VRTV back to anymore. The only way to exit player is through VR mode and clicking on the small X on top left side.
Also, Gear VR controls don't seem to work anymore.
Also there is a serious drift now.
Future function; a way to save settings or backup settings. I lost my config of my gamepad controls and can't get them back.
---------- Post added at 11:50 AM ---------- Previous post was at 11:37 AM ----------
ColinMacLaren said:
Hi Sven,
I bought the pro app in the Play store and I am willing to build my own libvlcjni.so. From all the players I have tried so far your app had the best results for non-VR 3D-movies by far.
I will install an Ubuntu on an usb stick tonight and have a couple of questions since I am not familiar with developing in Linux.
- Will it compile correctly under 64-it linux?
Click to expand...
Click to collapse
An actual 64bit Android support would be cool, not sure if it would be needed if Hardware support works... just an idea that was triggered from above.
Hi. I am just a noob in this, but please help me. I love VRTV player, but I can't
in VR mode in cinema choose another video to play. Have to pull off my phone, go to another movie tapping it, then pull phone back and watch. very uncomfortable.
Wilsonb said:
A paid customer and also joined the Beta testing team.. Want to say thank you for this great Video player. Took me a while to land on it after trying so many VR players.
Two questions.
Are there better instructions anywhere?
1.) How / where to find Codec's for this? Trying to play .MKV files (no audio)
UPDATE: used VLC codec, thanks..
2.) Is there a way to have the filename syntax , pre-configure settings on video type, VR DOME etc.., so it starts without having the non-3D menu first ? Does this make sense?
Using;
Note 5 -Samsung Gear VR, streaming videos from Local NAS
Click to expand...
Click to collapse
Hi, can you explain how did you install VLC coded? Thanks.
--- deleted by user ---
Reason. This has been answered in the very first post of this thread.
I have a nexus 5X and I can't find a good setup to have a quality like in another app.
Trying to play with shader and opengl 3.0 or Vertex hq, but I can't reproduce a good image quality.
What do you suggest ?
Envoyé de mon Nexus 5X en utilisant Tapatalk
Could you revert back the exit behavior as it was 4-5 revisions ago? If it was launched using a File Manager, then backing out brought it back the the app that launched it, instead of now it exits to the launcher.
Hope this make sense. I was able to select movies while closing one eye using my file manager.
This would be important at least until SMB authentication is working.
Thanks
Wilsonb said:
Could you revert back the exit behavior as it was 4-5 revisions ago? If it was launched using a File Manager, then backing out brought it back the the app that launched it, instead of now it exits to the launcher.
Hope this make sense. I was able to select movies while closing one eye using my file manager.
This would be important at least until SMB authentication is working.
Thanks
Click to expand...
Click to collapse
What is your rendering settings plz ?
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk