Related
Windows Edition - v0.9.11.0 - MD5 : A0F880F3CF420A31D86026F49A2013D7
Updated on 12/06/2013 ©2011 by Androxyde
More information at http://androxyde.github.com/
Flashtool Release Notes:
* 0.9.11
This version is a big split with every previous ones.
And not fully featured as previous can be.
I changed the UI framework from Swing to SWT because of a better integration with Mac UI.
Here is what is missing from previous releases :
- No multilingual UI
- No recovery installer
- No kernel installer (for 2010 devices)
- No ROM cleaner.
- Cannot Add/Edit/Remove devices.
No TA hex editor (in pro mode)
Version fully compatible with all 2013 devices (Z/ZL/Tablet Z etc etc)
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
As for flashing, BLU is available even without any connected device, even with
unrecognized devices.
Updated SuperSU package. Added servicemnu root hack
(works with Z/ZL for all FW up to .434)
Known working for Xperia T/V too
Added TA partition backup/restore. Using this feature, you can backup TA before unlock.
Restore TA will relock the devicee and get DRM back as well as BE2
(full complete relock). You cannot count on this feature if ever your device is
already unlocked. Missuse of this feature can brick the device
Introduction to Flashtool:
Flashtool is a flashing software that can be used to :
1. Flash original Images (Android 1.6, 2.1, 2.3 Images)
2. Root your phone
3. Install Recovery, Busybox, custom kernels
4. Clean your Rom (remove /system/apps apps of your choice)
(Be careful, unless you really know what you do, do not modify the default list.
This can make your phone stuck at the SE Logo)
5. Clear dalvik cache
6. Optimize (install of JIT v2)
(Disabled in 0.4, will readd it as a plugin for 2.1 phones only)
7. Customize (installs apps found in the custom/apps folder of the flashtool)
8. Clean uninstalled (remove any references to system apps removed in the
Clean (root needed) step)
9. Edit any text file on the device
10. Rebrand your device
Download Link
MOD EDIT: Not authorized mirror links.
MD
HIT THANKS BUTTON IF IT HELPED
This is not yours, and you are unable to support it. Moving this to General.
I'm pretty sure the devs of flashtool don't want it mirrored.
Sent from my Xperia Tablet Z using xda developers app
Thread Closed
As this is an info post to somebody elses work, the following actions have been taken.
1. Mirror download link removed.
2. Thread is closed as there is no need to post replies.
MD
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
WARNING #1: CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
WARNING #2: BECAUSE THERE ARE NO ODIN FILES FOR MF3, DO NOT FLASH THE STOCK ROM AT ALL. PLAY IT SAFE AND USE ROM-SLOTS.
CURRENT PROJECT STATUS:
v3.72 (TW4.4): Beta testing, no rom-slots
v3.65 (TW4.2): Stable
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for different sizes of /data partitions. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR KK/v3.73] Install Busybox via the Play Store (Busybox Free Installer)
[NEW FOR KK/v3.73] Remove XPOSED framework for the Safestrap install. It causes conflicts sometimes. Can re-install afterward.
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
KNOWN ISSUES:
[v3.73] ROM-SLOTs aren't supported yet
[v3.73] "Reboot Recovery" doesn't work in the APK (? -- need verified)
NEW TO v3.73:
TWRP 2.7.0.x update for the base recovery. This includes vibration support, backup time/date fixes and more.
ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY S4 ACTIVE
MAKE SURE IF YOU ARE UPGRADING TO v3.7x FROM v3.65 THAT YOU USE THE "UNINSTALL RECOVERY" BUTTON IN THE v3.65 APK BEFORE INSTALLING v3.7x.
NOTE: USE ONLY ROMS THAT MATCH UP WITH YOUR TOUCHWIZ VERSION. IF YOU'RE ON TW4.2 USE SS3.65 AND ONLY USE TW4.2 ROMS. IF ON TW4.4 USE SS3.73 AND ONLY USE TW4.4 ROMS
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
FOR USERS OF KK/TW4.4:
USE 3.73+:BETA Safestrap-JFLTEATT-ACTIVE-3.73.apk (updated 2014-06-02)
FOR USERS OF MF3 (TW4.2):
LATEST FILE: Safestrap-JFLTEATT-ACTIVE-3.65.apk (updated 2013-11-15)
Main XDA Downloads Page
Mirror 1 (Goo.im): http://goo.im/devs/Hashcode/jflteatt-active/safestrap
Mirror 2 (Crackflasher): http://downloads.crackflasher.com/?dir=Devs/Hashcode0f/jflteatt-active/safestrap
HOW TO MANUALLY REMOVE SAFESTRAP:
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
As of version 3.7x, Safestrap Recovery is now based on TWRP 2.7.x.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
This thread is a development ONLY thread.
For discussion go here:
http://forum.xda-developers.com/showthread.php?t=2447764
XDA:DevDB Information
Safestrap Recovery v3.65 (JB) / v3.73 (KK), Tool/Utility for the Samsung Galaxy S 4 Active
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Stable Version: 3.65
Stable Release Date: 2013-11-15
Current Beta Version: 3.73
Beta Release Date: 2014-06-02
Created 2013-09-18
Last Updated 2014-06-02
Reserved
MAIN MENU:
Boot Options: This area is for managing your virtual ROM-slots. You create a new ROM-slot by clicking on one and if it doesn't exist you will be prompted to create it. Follow the on-screen guides. Once a ROM-slot is created you select that slot to activate or delete it. Under each ROM slot (once created) you can:
Activate: Makes the chosen ROM-slot the "current" one, where almost all of the features of TWRP affect that slot. This will also be the ROM that is booted.
Set Nickname: For convenience you can set a small name for each ROM-slot. This is limited to 10 characters as it will eventually be added to the beginning of backup names. This name is shown on the ROM-slot button once it is set.
Check FS: This performs a file system checks on the ROM-slot and fixes any errors found.
Delete: Delete the ROM-slot files (disabled if the ROM is active — please choose another ROM-slot to activate and then come back) USE WITH CAUTION, THERE'S NO GETTING THESE BACK UNLESS YOU HAVE BACKUPS.
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Backup / Restore: This should be self-explanitory, but you use these options for making backups of the currently selected system. Or restoring a previously made backup to the currently selected system (regardless of where you backed it up from). DON'T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
Mount: You can manually manage mounts here. NOTE: the "system", "data" and "cache" mounts will use the currently selected ROM-slot.
Wipe: Manually erase portions of the device. NOTE: You only have 1 internal and 1 external SD card. These are not "virtual" if you erase them. They are gone. Use with caution. Wiping the "system" when "stock" ROM is selected will try and keep the Safestrap hijack in place.
Advanced:
Copy Log to SD: Experienced something odd and want to report it? DO THIS and include the log when you send me the report. Otherwise, the recovery.log will disappear when you reboot.
Fix Permissions: This can fix up ROMs which are displaying odd force close issues, etc. You will probably never need to do this.
Partition SD Card: You can add ext3 partitions to the external SD card if you want. I'm not sure we have much of a need for this on our devices.
File Manager: This works like any other file manager inside Android. You can thank the TWRP people for this, because it is quite possibly one of the best features I've ever seen in a recovery.
Terminal Command: Also very handy for those once in a while moments when you have to do something via terminal but don't have adb handy. USE WITH CAUTION
Settings:
Here you can turn on and off signature verification of .zip files
Force MD5 sum checks on .zip files prior to flashing
"Use rm -rf instead of formatting" this may or may not be checked in Safestrap, but the key partitions which are signed and cannot be truely formatted will automatically use this feature
There are a few other checkbox options in here. Please know what you are doing.
Simulate most actions for theme testing. If you have this checked, Safestrap/TWRP will not perform most actions but show the dialog boxes so you can review theme elements. If you turn this on, it STAYS ON till you turn it off. And will show "SIMULATING ACTIONS" up top.
Set the Time Zone (use "Set Time Zone" button after choosing which time zone you want)
Restore Defaults. Use this to reset all options back to default as it came when you installed for the first time. Does not erase backups or ROM-slots, tho it might change the active slot.
Reboot: Choose from 2 options for rebooting "System" which performs a reset/reboot of the device and "Power Off" which turns the device off.
Reserved
KNOWN ISSUES:
Bluetooth remote control isn't working on rom-slots.
CHANGELOG:
[2013/11/13] TWRP updates
[2013/11/13] "toolbox" binary / symlinks in recovery fixed
[2013/11/11] Uninstall from the APK fixed
[2013/09/17] /sdcard mounting bugfix
[2013/09/17] Hijack improments to support default rootfs files
[2013/09/17] ROM-slot image creation bugfix for size > 2gb
[2013/09/12] Much improved block device handling
[2013/09/11] Bugfix in script translation
[2013/09/11] hijack / init.rc tweaks
[2013/09/11] Bugfix for display lag / buffering issue (WIP)
[2013/09/10] Adjust "ROM-slot" display in UI
[2013/09/10] /data/media handling changes
[2013/09/06] custom twrp.fstab files
[2013/09/06] /data/media handling changes
It's like Christmas... Testing now!
Edit: No camera or wifi (didn't test much else), but I successfully booted this: http://forum.xda-developers.com/showthread.php?t=2406177
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Bleh, just realized this isn't a discussion thread, my mistake. Mods, delete this is necessary, sorry, sorry, was just excited to see some progress.
Go Hashcode go!
Thanks you soon much OP. Testing now.
Sent from my SAMSUNG-SGH-I537 using Xparent BlueTapatalk 2
Added the ATT ACTIVE MF3 stock kernel modules to the downloads section.
http://forum.xda-developers.com/devdb/project/?id=681#downloads
If you're on the locked MF3 build: Keep these on the device and flash them after any ROMs that are installed. They will sync up the kernel modules and restore wifi, bt, etc.
Do we need those modules for MF1?
Hashcode said:
Added the ATT ACTIVE MF3 stock kernel modules to the downloads section.
http://forum.xda-developers.com/devdb/project/?id=681#downloads
If you're on the locked MF3 build: Keep these on the device and flash them after any ROMs that are installed. They will sync up the kernel modules and restore wifi, bt, etc.
Click to expand...
Click to collapse
@Hashcode I modified your zip with the modules for MF1. You can add it to the d/l page if you want. Confirmed wifi fix for AOSP port.
http://db.tt/4uMS68Xy
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Anyone have a mirror to the MF3 kernel modules? I cant download it for some reason.
Edit N/M finally got it. Here is a mirror if someone has issues like I did. https://www.dropbox.com/s/5xdeag03qu90r92/jflteatt-active-MF3-modules.zip
And here's another mirror just in case meaning the kernel modules for build MF3 in a flashable zip as provided by Hashcode; these are necessary for people wishing to install other ROMs using Safestrap to ensure the hardware works, for the most part (Wi-Fi, Bluetooth, etc - but the camera will probably always have issues with other ROMs till someone figures it out):
https://dl.dropboxusercontent.com/u/19019338/jflteatt-active-MF3-modules.zip
br0adband said:
And here's another mirror just in case meaning the kernel modules for build MF3 in a flashable zip as provided by Hashcode; these are necessary for people wishing to install other ROMs using Safestrap to ensure the hardware works, for the most part (Wi-Fi, Bluetooth, etc - but the camera will probably always have issues with other ROMs till someone figures it out):
https://dl.dropboxusercontent.com/u/19019338/jflteatt-active-MF3-modules.zip
Click to expand...
Click to collapse
Has anybody tried contacting @LeJay about the camera issue? He was able to get the camera working on Cyanogenmod so he might be able to work his magic again.
Devo7v said:
Has anybody tried contacting @LeJay about the camera issue? He was able to get the camera working on Cyanogenmod so he might be able to work his magic again.
Click to expand...
Click to collapse
Not sure how safestrap works and I haven't tested it myself, but something along the lines of this patch + maybe a 3rd party camera app should work.
Posted specific instructions by @TreyLWalker for flashing Safestrap + Google Play Edition ROM and the camera patch in #3 post:
http://forum.xda-developers.com/showpost.php?p=45694084&postcount=3
Procedure for my Samsung S4 Active i537 MF3 - I537UCUAMF3 - US, AT&T:
Installed Safestrap Recovery v3.5x Safestrap-JFLTEATT-ACTIVE-3.5x-B08.apk
Installed Recovery, Rebooted into Recovery, Pressed Settings Key on Splash Screen Load
Created ROM Slot-1, Set it to active, Installed with the following:
AOSP Port GT-I9295 - Official 4.2.2 - I9295-PORT-GoogleEdition-V1.zip (worked for i537 despite saying otherwise, I still wouldn't flash stock ROM....)
MF3/MF1 Kernal Modules - jflteatt-active-MF3-modules.zip / jflteatt-active-MF1-modules.zip (in same downloads area)
LeJay's S4 Active Camera Patch - SGS4A_CamPatch.zip
Working Phone, Bluetooth, Wifi, Stock Camera App /w Flash (video-recording preview is low-res, but records normal)
If this was made to work on the i9295 would we then be able to flash roms without needing to use Odin to get Wi-Fi working?
Sent from my GT-I9295 using XDA Premium HD app
Hashcode said:
Posted specific instructions by @TreyLWalker for flashing Safestrap + Google Play Edition ROM and the camera patch in #3 post:
http://forum.xda-developers.com/showpost.php?p=45694084&postcount=3
Procedure for my Samsung S4 Active i537 MF3 - I537UCUAMF3 - US, AT&T:
Installed Safestrap Recovery v3.5x Safestrap-JFLTEATT-ACTIVE-3.5x-B08.apk
Installed Recovery, Rebooted into Recovery, Pressed Settings Key on Splash Screen Load
Created ROM Slot-1, Set it to active, Installed with the following:
AOSP Port GT-I9295 - Official 4.2.2 - I9295-PORT-GoogleEdition-V1.zip (worked for i537 despite saying otherwise, I still wouldn't flash stock ROM....)
MF3/MF1 Kernal Modules - jflteatt-active-MF3-modules.zip / jflteatt-active-MF1-modules.zip (in same downloads area)
LeJay's S4 Active Camera Patch - SGS4A_CamPatch.zip
Working Phone, Bluetooth, Wifi, Stock Camera App /w Flash (video-recording preview is low-res, but records normal)
Click to expand...
Click to collapse
Already had the MF3 AOSP up and running but the camera was the sticking point, just flashed that zip provided by LeJay and it's working - it's not the same as the stock GS4A camera (which I was getting pretty used to) but it does allow for photos and video presently so that's better than not having that ability in any respects.
Thanks, LeJay...
Yeah thanks for the camera fix. I'm wondering if I can grab the camera apk from stock and bring it over. Would love to have that aqua mode. Its one of those look what I can do kinda features. Oh and the reason we all got the active over the regular s4
Sent from my GT-I9295(AOSP GS4A) using xda app-developers app
Diablo2424 said:
Yeah thanks for the camera fix. I'm wondering if I can grab the camera apk from stock and bring it over. Would love to have that aqua mode. Its one of those look what I can do kinda features. Oh and the reason we all got the active over the regular s4
Sent from my GT-I9295(AOSP GS4A) using xda app-developers app
Click to expand...
Click to collapse
I doubt it since the camera app is built on Samsung's TouchWiz framework (much like you can't use their widgets on Nova Launcher and such).
Unless someone were to replicate what "aqua mode" does, you may just have to live without it, or find an app on the play store that allows button assignment.
Wow I've been busy with work and to see this on XDA WOW
Once again Hashcode has saved me from a locked boot loader. I used safestrap with my RAZR and now I'm running the Google edition it put my active into Beast Mode.
If you want to use the camera underwater just reboot into your stock system.
Sent from my GT-I9295 using XDA Premium 4 mobile app
mrmartin86 said:
I doubt it since the camera app is built on Samsung's TouchWiz framework (much like you can't use their widgets on Nova Launcher and such).
Unless someone were to replicate what "aqua mode" does, you may just have to live without it, or find an app on the play store that allows button assignment.
Click to expand...
Click to collapse
True.. Its not that big of a deal i was just curious. Thanks for the info!
dave5777 said:
Wow I've been busy with work and to see this on XDA WOW
Once again Hashcode has saved me from a locked boot loader. I used safestrap with my RAZR and now I'm running the Google edition it put my active into Beast Mode.
If you want to use the camera underwater just reboot into your stock system.
Sent from my GT-I9295 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Duh I can't believe I didn't think of that, haha. Problem solved. Although I will say I may not bother at this point. This AOSP ROM running on SS is so fast and smooth, I don't think I'll be going back to stock anytime soon heh
Sent from my ATT SGS 4 Active running AOSP
CM10.2 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz5.18.4 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM10.2 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). More desired may be the new privacy manager features that allow you to control, on a per app basis, which information you wish to share. Other improvements include an improved lockscreen cLock and a new integrated Superuser.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera/Camcorder
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* When unlocking the screen, sometimes only the capacitative buttons light up, and the screen doesn't come on. This seems to happen about 80% of the time.
Solution: This can be fixed by locking the screen, then unlocking it again. In about 5% of these cases the screen does not come on again. Just repeat the steps again until it does.
This has been fixed as of build 20131029
* You may notice a screen flicker when you first flash this ROM. This is due to a bug where the system can't decide whether to render the graphics with the cpu or the gpu, thus the flicker.
Solution: This is fixed by turning on Settings -> Developer Options -> Disable HW Overlays (You must first enable Developer Options by pressing 7 times on Settings -> About Phone -> Build Number). This will be reset on every boot. if you install Universal Init.d, my 91fixoverlays script will run on each boot and fix this automatically.
This has been fixed as of build 20131029
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 flashable zip which is compatible with CM10.1/CM10.2
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140224 (Latest)
ROM: cm-10.2-20140224-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20140224-signed.zip (106.5MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A dirty flash should work for upgrading , but a clean flash is highly recommended
Build: 20140120
ROM: cm-10.2-20140120-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20131231-signed.zip (103.8MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with CM10.1/CM10.2
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with CM10.1/CM10.2
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]December 23, 2013 - Build 20131223[/B]
* Revert build.prop to use dyn instead of gpu (less problems)
* Added back 91fixoverlays to /system/etc/init.d to disable hw overlays and fix screen flicker on boot
* Re-worked 91fixoverlays script so that it now runs in it's own shell to stop it from blocking other startup scripts and causing a laggy boot
* Fixed up device tree code including adding the correct definitions for boot animation size and update to the build fingerprint
* Synced latest changes from CyanogenMod
[B]December 1, 2013 - Build 20131201[/B]
* Force gpu rendering in build.prop
* Improve fix for screen on delay
* Synced latest changes from CyanogenMod
* Updated GAPPS
[B]October 29, 2013 - Build 20131029[/B]
* Tweaked build.prop to fix screen flicker and notification drawer lockup
* Fixed screen unlock bug - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/5e163ff0c5d90a4518cbc9e14c86dceec095c70a"]Commit 5e163ff0c5d90a4518cbc9e14c86dceec095c70a[/URL]
* Added SmartAssV2 Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/511e45206bb9a1454a0c43b3d626749c1fa2c241"]Commit 511e45206bb9a1454a0c43b3d626749c1fa2c241[/URL]
* Added Adaptive Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6"]Commit 7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6[/URL]
* Added Lagfree Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/d1392017601d27303fbce9da18d2af718e7e1a65"]Commit d1392017601d27303fbce9da18d2af718e7e1a65[/URL]
* Restore Advanced Device Settings - [URL="https://github.com/titanic-fanatic/android_device_samsung_msm8660-common/commit/3126c17c6165c7d96abde4cd7459769e165aa195"]Commit 3126c17c6165c7d96abde4cd7459769e165aa195[/URL] / [URL="https://github.com/titanic-fanatic/android_packages_apps_Settings/commit/9031ffb1f4e4185f397724a27e3d75afe7fd67e4"]Commit 9031ffb1f4e4185f397724a27e3d75afe7fd67e4[/URL]
[B]October 5, 2013 - Build 20131003[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market, and also make sure you have Universal Init.d installed and active. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. When your phone reboots, recovery will warn you that your device may possibly be unrooted. This is because of the install-recovery.sh script that is required to start the superuser daemon which allows SuperSu to manage superuser permissions. You are not unrooted ;-)
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. This needs to be set on every boot unless you are running Universal Init.d and my 91fixoverlays script is present in the /system/etc/init.d folder.
Q. When I unlock my screen, my menu/home/back/search buttons come on but the screen is black?
A. This is a known bug in this ROM and is on the list of things that need to be fixed. For now, when this happens, just lock the screen, then unlock it again and the display should come back. If it does not, repeat until it does (the most number of times i had to do that was 3).
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM10.2 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-10-05
Last Updated 2014-02-23
Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Wow! Thanks so much. Downloading now.
iDynamics said:
Wow! Thanks so much. Downloading now.
Click to expand...
Click to collapse
Wow, you already found it and I wasn't even finished putting everything up... make sure you use the new CWM, very very very important!
Followed the instructions ( to the best of my ability ) but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
iDynamics said:
Followed the instructions but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
Click to expand...
Click to collapse
I totally forgot to update the build.prop with the build type, it is responsible for the red border. Either use a build.prop editor or open the /system/build.prop with a text editor and change the following line:
ro.build.type=eng
Click to expand...
Click to collapse
Change it to:
ro.build.type=user
Click to expand...
Click to collapse
You will need to reboot after making this change.
In regards to the 91fixoverlays script, I do appologize. I forgot to include it in the zip... Please download the attached 91fixoverlays.txt file and rename it to 91fixoverlays and move it to /system/etc/init.d and change it's permissions to match the other files in that directory.
Sorry for missing these two things. I will update the packages ASAP and will post a note when it's done so you know that there is no need to follow the steps in this post.
Much appreciated! No more red flickering. Thanks!
Wow! Thank you!
Sent from my SGH-I757M using xda app-developers app
This. Is. Amazing!!!!!
Downloading now, will install and report back in a bit with findings.
Thanks so much!!
Awesome. Downloading. Will report back. Thanks!
Sent from my SGH-I757M using xda premium
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will do more testing.
Thanks
Zippy Dufus said:
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will so more testing.
Thanks
Click to expand...
Click to collapse
I think this is due to our oddly small cache partition. Only 100MB as compared to the skyrocket at 300MB. Currently, I only moved four apps in the gapps package to the data partition do that their dex files don't end up in the /cache/dalvik-cache dir and instead end up in /data/dalvik-cache. I think I need to move others. I also think that it happens only on first boot without side effects because a couple of the installed apps only run on first boot, then their dex files can be deleted (I think this happens automatically).
Sent from my SGH-I757M using XDA Premium 4 mobile app
Thanks titanic_fanatic, you've breathed new life into an old phone
Sent from my SGH-I757M using Tapatalk 2
Only issue I've run into so far is that auto rotate doesn't seem to work :-/
Sent from my SGH-I757M using XDA Premium 4 mobile app
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
rukusx7 said:
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
Cool, I'll give that a try. Anyone else having auto-rotation issues?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Rotation is not working for me, though I always keep it on portrait anyway so I am not complaining.
Rotation doesn't work here, and every so often I run into spells where the only button that works is the home button and haptic feedback stops working all around. A reboot fixes it and it seems random. Other than those few things this is soooooo smooth. I'm happy. Thanks so much!
Sent from my SGH-I757M using xda premium
Fix for Sensors
Hey guys, to fix the sensors, download this attachment sensors.default.so.txt and rename it to sensors.default.so, move it to /system/lib/hw and give it the same permissions as the other files in that directory, then reboot and your sensors should be working
Works now! Thanks ya muchly.
Sent from my SGH-I757M using xda premium
SlimJB4.3 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in Jellybean 4.3, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz6.07.9 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of SlimBean4.2, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D SlimBean4.3 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). This is the latest SlimBean4.3 and has all of the features of a SlimRom that you've come to love. Don't forget to download the special gapps package to get the full SlimBean experience while using "The Real Dark Slim" feature.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THE PAGE
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files. You can still view these mp4 files, but you must open them with a file manager directly into the video player instead of using the gallery to access them.
* The camcorder records just fine, but when playing back the video, it's just a distorted video. Audio is fine, and I have not tested video with a third party app. If you test one and it works, please post that here so that others may benefit from your findings.
This seems to have been fixed as of the 20140121 build
* The latest Google Drive seems to be missing classes and will not open. This may be due to a missing content provider or may be a bug with the Google Drive app itself.
Solution: The solution for this is to uninstall the latest version of Google Drive, then go to Settings -> Security and enable Unknown Sources. Then open the Play Store and turn off automatic updates or it will end up overwriting the older version and you will be left with a non-working Google Drive again. Once all that is complete, download and install this Google Drive instead:
com.google.android.apps.docs.apk (8.4MB)
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 or Philz Advanced/Touch Recovery flashable zip which is compatible with SlimBean4.2/SlimBean4.3
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (or the Philz one) that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140121 (Latest)
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20140121-0353.zip (114MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20140121.zip (147.3MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Build: 20131228
ROM: Slim-celoxhd-4.3.build.2.1-UNOFFICIAL-20131228-1427.zip (126.1MB)
GAPPS: Slim_AIO_gapps.4.3.build.2-20131228.zip (160.4MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with SlimBean4.2/SlimBean4.3/SlimKat
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with SlimBean4.2/SlimBean4.3/SlimKat
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with SlimBean4.2/SlimBean4.3/SlimKat
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]January 21, 2014 - Build 20140121[/B]
* Synced with upstream sources (CyanogenMod/SlimRoms)
* Added SystemUI memory management fix
* Removed 91fixoverlays init.d script as it's no longer required
* Implemented fix for the char dev driver - fixes the vibrator not loading on boot
[B]January 03, 2014 - Build 20131228[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. There is a script that has been included with this ROM in the init.d that sets that on every boot so you shouldn't have to.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* SlimRoms Team - ROM Base
Without all of the hard work and efforts of the SlimRoms team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* @dsixda - Initial port of CM9/CM10 for SGH-I757M
* @Strange Peer - Continued development of CM10
* @rukusx7 - Contributor
* @bijon440 - Contributor
* @kj2112 - Contributor
* @Tronith - Contributor
* @Zippy Dufus - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL SlimJB4.3 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: SlimBean
Version Information
Status: Alpha
Created 2014-01-03
Last Updated 2014-01-23
Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.
Reserved
Yay a slim bean of 4.3! Woot.
Sent from my SGH-I757M using xda app-developers app
Hi Shouldn't this be in the development forum
Awesome! Was hoping for a new slim build! Thanks so much TF! Great job!
Sent from my SGH-I757M using xda premium
68544455 3521
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..
Hey
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!
JayR_L said:
titanic_fanatic, I just bought a pawned SGH-I757M and flashed your ROM on my device.
I love it, but there is one problem with my device. I find that the AMOLED screen is much too warm for my eyes. I know that CyanogenMod has in color modifier sliders but in this case, the kernel doesn't support it.
Is there any chance you may point me in the right direction in order to get this feature working? Or am I at lost with the SGH-I757M?
Thank you very much for your hard work, much appreciated!!!
---
first post... long time lurker..
Click to expand...
Click to collapse
I'll add back the mdnie settings. They are supposed give you control of the temperature
GrAt_On said:
Is this any different from the Cyanogenmod 10.2 iteration other than aesthetics? Does the battery and performance offer more seeing that it is supposed to be a much smaller and compact kernel?. I really have to urge to flash this, but I don't know if its worth my time considering I have already flashed CM10.2 recently and am very happy with it. Thanks!
Click to expand...
Click to collapse
Only difference is in features and it's been slimmed down.Other than that, it's the same ROM. I just posted it for those who like the slim features check this page out for the list of slim features:
http://www.slimroms.net/index.php/slim-bean-features
Sent from my SGH-I757M using XDA Premium 4 mobile app
The Iron Man said:
Hi Shouldn't this be in the development forum
Click to expand...
Click to collapse
I've only posted or ROM's here since that's where dsixda was told to post them back when he started with this device. If the mods would prefer I post them in the dev section, I'm more than happy to oblige
Sent from my SGH-I757M using XDA Premium 4 mobile app
Amazing
I just flashed it, its amazing! Especially "The Real Dark Slim"! However, I did notice Google + doesn't work properly asking me to re install it at the play store. Had to uninstall using Titanium Backup and then install it back via app store, not sure now whether it has the the real dark slim feature integrated in google +. Other than that, it's really smooth so far Great port.
UPDATE: Google drive also doesn't work as it force closes continuously even after wiping dalvik's cache. I'll try redownloading the gapps tomorrow, might have a corrupt downloaded file.
I Fashed latest slim as well. It is running really well so far. I had the same issue with Google+ until I uninstalled using TB then reininstall from play store.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Can confirm issue with Google+..
Thank you t_f for looking into mdnie. Also, flashing the unmodified lock screen handle available on Slim's website did not work, I still see the Slim logo. Aaah I wish I had time to figure out the android build environment.. I mean its probably just ant lol
Sent from my SGH-I757M using Tapatalk
I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
manfromgta said:
I noticed while testing the latest slim that hw overlay is disabled by default. Is this by design or necessary with this rom? I know this issue is addressed in your other ROMs but not sure about this one. BTW with fairly heavy use I am currently at 40% battery over 20 hours. Quite acceptable.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
It is intentional. Disabling the hw overlays is a performance hit, and it seemed that slim didn't need that hack because the overlays are working correctly
I know, the latest ROMs are running smooth and battery is much better since I tweaked the kernel for both.
I'm also really enjoying my new computer so much that I'm playing with paranoid android too. Got it booting with a bunch of hacks and to my suprise, it's running quite well. I'll post that after I test it more and clean up the build process. Then we have choice of which ROM too use. That was the problem before, no choice strange though, there is no branch for kk in paranoid android's repo.
Sent from my SGH-I757M using XDA Premium 4 mobile app
Just a word of caution to everyone using philz latest 6.07 cwm recovery. There is a know issue where the update-binary has now been updated as of kk and the recoveries built with kk like the new philz 6.07 are now giving assert errors (error 7).
There are two ways to fix this:
1) Revert to the older 6.01 version of philz.
2) extract the updater-script from the rom zip file, delete the assert lines and replace the old updater-script with the new one.
If you're new to all this, or consider yourself inexperienced, I recommend you go with option 1 and revert to the older philz as it's a less risky method of doing things
Sent from my SGH-I757M using XDA Premium 4 mobile app
Here's the link to the older philz 6.01. You can use either the 6.01.0 or 6.01.2.
http://d-h.st/users/philz_touch/?fld_id=29076#files
Sent from my SGH-I757M using XDA Premium 4 mobile app
Please check out this post if your not flowing the 10.2 thread and provide your opinion if you have one
http://forum.xda-developers.com/showthread.php?p=49171164
Sent from my SGH-I757M using XDA Premium 4 mobile app
ParanoidAndroid for SGH-I757M Released
Alright, for those of you who are waiting for my PA build, it's up. This is a JB4.3 build of ParanoidAndroid and I have added back the performance settings from CM to allow changing the governor and io scheduler as the defaults have sucky performance.
[ROM][PA-JB4.3][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M
Enjoy!!!
It's saying that slim isn't rooted?
** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
** DoPa5 (AOSP - Kitkat) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa v2.7 is a ROM for Sero 7 Pro owners everywhere. Whether bought in the US, Britain, Australia, Germany, or elsewhere, your tablet is supported.
The ROM starts with well-tested AOSP code and adds core functions where needed but skips the frills that are easy to add on - and remove when they cause problems. It's aimed at people who want to choose their own features and not have them imposed by the developer.
New / Improved
International Support - a single ROM for all Sero 7 Pros sold worldwide
New in v2.7 - support for the German model of the Sero 7 Pro (m470bsg)
Speed Control - a unified kernel provides speed when you need it and stock performance when you don't.
Use the new Performance page in the Settings app to control it
exFAT - support has been moved into the kernel for improved performance
Boot Animation - a handsome new DoPa animation thanks to @mikembley, our first-ever UK user
To get you started customizing your ROM, v2.7 offers these add-ons:
built-in: SuperSU, Xposed Installer GravityBox, Phab7
optional: have your tablet claim it's a Nexus7 to get more apps in PlayStore
The package does not include any Google apps (e.g. Playstore). See this thread for links to the latest GApps packages.
Installation
UK / AU / DE / First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install Philz Touch Recovery
Users outside the US must use this version of Philz to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use it just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip sero7pro-philz6.58.0-dopa-v2.7.zip and put the file philz.img in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then the Philz menu
CWM
If you have CWM installed, copy sero7pro-philz6.58.0-dopa-v2.7.zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the Philz menu
Regardless of how you install Philz, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
ROM
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
on Philz main menu, select "Backup and Restore"
next, select "Backup to /storage/sdcard1" (the 6th item on that menu)
if there's enough space on the card, the backup will start without any further prompt; it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
Internal SD card
This is optional but worthwhile if you have files you value stored on the tablet:
on Philz main menu, select "Backup and Restore"
next, select "Custom Backup to /storage/sdcard1" (the 9th item on that menu)
on the next screen, deselect everything, then select "Backup /data/media" (the next-to-last item)
finally, select "Start Custom Backup Job"
STEP 3: Install the DoPa ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See this thread for a selection of packages. To avoid complications, I'd suggest choosing the "Nano Modular Package" to get just the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
on Philz main menu, select "Wipe and Format Options", then "Custom Format Options"
select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice
back on the main menu, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp444-dopa-v2.7.zip, then OK your choice - the install process should take about 40 seconds
next, install your Gapps package
return to the main menu, select "Reboot System Now", then hold your breath for the next 3-4 minutes
the Hisense screen should be up for less than a minute, followed by the DoPa boot animation for another 2-3 minutes
when the Google setup screen appears, you'll probably get a warning that "Bluetooth Sharing" has stopped - after you clear it, you'll never see it again
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
While any SELinux-enabled version of CWM or TWRP can be used to install the ROM, the companion Philz Touch CWM-based recovery is highly recommended if you use exFAT-formatted SD cards.
from DoPa AOSP Kitkat ROMs (v1.0-v2.6) - no need to wipe or format anything!
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp444-dopa-v2.7.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa-v2.7.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed Philz Touch Recovery, please do so first. Philz has gotten complicated, so read this carefully!
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Notes
Speed Control - this version uses a redesigned kernel that caps processor speeds at stock levels during start-up, then adjusts them once the tablet is up and running. Go to Settings->Performance to enable this feature, and to set the top speeds for the CPU (1.0-1.5ghz) and GPU (448-520mhz). When disabled,the processor will remain at stock speeds (1.2ghz/448mhz) unless changed by a 3rd-party app.
Encryption - the first time you formatted your /data partition, you lost the ability to encrypt your tablet's data. Using the companion Philz Touch Recovery to reformat /data (using either filesystem) will restore that ability. To preserve your existing data, do a backup first, then restore just /data when done. Note: you must select "format /data and /data/media (/sdcard)" when reformatting.
OTG Charging Support - this kernel supports charging the tablet while an external device (flash drive, keyboard, etc.) is attached to the USB port. This feature requires either an OTG 'Y' cable or an OTG USB hub, and the AC adapter that came with the tablet. For this to work, power must be connected to the cable or hub before plugging it into your tablet. The OTG device(s) can be attached/detached at any time.
WiFi Display (a.k.a. Miracast) - video works but its performance may depend upon your TV; audio does not work.
Bluetooth Sharing - on the initial boot, this service will FC due to a timing issue. The system will restart it and you should never see this error again.
Added/Changed in v2.6
International Support - added support to the kernel for the British and Australian models of the Sero 7 Pro
Overclocking - replaced separate standard and overclocked kernels with a unified kernel that uses less power when overclocked; added a new Performance page to the Settings app to control it
exFAT Support - moved exFAT support to the kernel for improved performance
Boot Animation - added a custom boot animation created by @mikembley
Added/Changed in v2.51
Flexible Formatting - added F2FS support for the /thirdparty and /mnt/modem partitions
Bug Fix - enabled Philz Touch Recovery to format the /thirdparty and /mnt/modem partitions using EXT4
Added/Changed in v2.5
Flexible Formatting - enabled use of either F2FS or EXT4 for any of the built-in partitions
External Storage - added support for F2FS, and for devices formatted without a partition table (i.e. Windows-style "super-floppies")
Android version - upgraded from AOSP 4.4.4_r2 to AOSP 4.4.4_r2.0.1
Recovery - added a DoPa version of Philz Touch Recovery
Added/Changed in v2.1
SD Cards - added support for SD cards formatted with the NTFS or exFAT filesystems
Android version - upgraded from AOSP 4.4.4_r1 to AOSP 4.4.4_r2
Added/Changed in v2.0
Google Now - voice activation (i.e "OK Google") now works in the Google Now launcher
kernel - added OTG charging support.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp444-dopa-v2.7.zip the full ROM
sero7pro-nexus7spoof-dopa-v2.7.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-philz6.58.0-dopa-v2.7.zip a customized version of Philz Touch CWM-based Recovery v6.58.0
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to previous versions (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
Thanks man been running it since day one no problems and very stable.
Can We call these the Semi OFFICIAL ROM ?
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
How much free space should there be on a system after a fresh install?
datboy143 said:
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
Click to expand...
Click to collapse
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Click to expand...
Click to collapse
Ok will do thanks
Sent from my SGH-I777 using xda app-developers app
GPS and Google music
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
gotshores said:
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
Click to expand...
Click to collapse
Don't use Google music but I do use scanner radio and whenever I switched streams the tablet would freeze and I would have to hold the power button to turn the tablet off.
Now its working like it should. So this latest build might fix Google music.
Another issue I was having is when I opened the calendar it would not close hitting the back button. Its closes fine now.
The GPS doesn't seem to load any slower for me than it did with the stock ROM but I don't use it much.
Anyway I would recommend trying this latest build. Just make sure you wipe cache and dalvik cache and flash the latest gapps. Everything should still be the same as before when you boot with the new ROM and hopefully you will notice some improvements.
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in.
Click to expand...
Click to collapse
Just want to thank you for fixing the sound bug. V4A is working perfectly and as far as I can tell so is everything else. I will keep testing and if I run across anything strange I will post here. Your work on this is very much appreciated
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in. The only changes to the AOSP and kernel code are those needed to ensure compatibility or to enable standard features Hisense omitted (e.g. USB-OTG support). Because it relies on well-tested AOSP code, it is likely the most stable KitKat ROM available for this tablet. For the same reasons, it is almost certainly not the fastest KitKat ROM either.
To make it more functional, the package includes a handful of apps most people find useful: SuperSU, ES File Explorer, Xposed Installer, GravityBox, and my Phab7 UI switcher. To avoid the wrath of Google, it does not include any GApps; see this thread for links to the latest packages.
Installation
Having an SELinux-enabled version of CWM or TWRP installed is a prerequisite. You can find versions built by randomblame here or by davepmer here.
If you're upgrading from v0 of this ROM, clearing cache and dalvik-cache should suffice. Otherwise, do a full wipe of both your data and cache partitions. As always, a backup of your existing setup is recommended.
Notes
All features should be present and work as expected with these exceptions:
WiFi Display (a.k.a. Miracast) - video is enabled but very slow; audio is disabled because it doesn't work and generates 45 error messages per second when enabled
SELinux - the kernel runs in permissive mode due to missing entries in its configuration.
As these issues are resolved, the ROM will be updated accordingly.
Credits
randomblame
davepmer
the CM team
Download
sero7pro-aosp442-dopa-v1.zip
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
Click to expand...
Click to collapse
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
This is normal..
Sent from my Sero 7 Pro using XDA Premium 4 mobile app
enfermo said:
Can We call these the Semi OFFICIAL ROM ?
Click to expand...
Click to collapse
Generic, yes - (semi-)Official, no.
datboy143 said:
I installed v1 after it booted up play store wasn't installed.
Click to expand...
Click to collapse
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that.
Click to expand...
Click to collapse
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
gotshores said:
I noticed on version 0 [...] an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build?
Click to expand...
Click to collapse
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
I ran into that too - and something even odder. SuperSU's su and daemonsu program files should have a flag that marks them as authorized to give root access. That flag is now missing but I can still get root whenever needed. I don't know if this is to be expected with SELinux in place or just something specific to SuperSU. I'll investigate...
tinybeetle said:
How much free space should there be on a system after a fresh install?
Click to expand...
Click to collapse
After installing the ROM, the "Gapps Standard" package, and Antutu, Settings->Storage says I have 5.48gb available. This is the free space on your /data partition and includes the space used by your emulated SD Card (which is actually just a subdirectory of /data).
"Smart ass alert"
Not only was playstore not installed, it doesn't give me the winning lottery numbers for next week! What gives?
Ok, being serious, Thank you for your time and effort. This weekend I am going to finally give this a try.
Dolorespark,
I haven't messed with any sound effect settings, so it must be Google Music messing with things. Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all. Anyway, thanks for all you do. I'll keep testing, and keep my trusty backup of DOPA v2.
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
envygreen said:
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
Click to expand...
Click to collapse
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping? also had a root fix need after rebooting, did yes and everything is ok... thanks DOPA....
dolorespark said:
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
Click to expand...
Click to collapse
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
dolorespark said:
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
Click to expand...
Click to collapse
No it was gmail. It would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
I played with the tablet extensively last night and did not experience any problems. Even movies, streaming or local using XBMC play using a bluetooth headset. There is no stuttering as there was in all of the previous Jelly Bean roms, stock....DoPa1 and DoPa2. I don't know if that was a KitKat fix or what but I am very happy with the stability of this rom and the fact the XBMC bluetooth bug was fixed is icing on the cake. Of course V4A makes it even better.
I will continue to run the rom and will post if I find any bugs. Thanks again.:good:
Been running since v1 was posted. Have to say the music bug is no more! Listening to lucky mixes all day today and email, g+, and everything my wife and kids have done on it. No problems! Thanks You have really taken your time to make this rom perfect!!!!
Gazoo119 said:
[gmail] would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
Click to expand...
Click to collapse
nccruz said:
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping?
Click to expand...
Click to collapse
Did you use the latest GApps package? As Gazoo119 noted, that fixed a problem with another app that uses Google Play Services. If the problem persists, you may want to go to Apps->Google Play Services, then tap the "Manage space" button. On the next screen it lets you clear all data.
gotshores said:
Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all.
Click to expand...
Click to collapse
I hadn't tried GPS at all until you mentioned it. I installed Google Maps but couldn't get a lock at all. It's raining here, so I couldn't get fully in the clear. Instead I sat in my car and it still did nothing. Finally, I forced-stopped the app, cleared data and cache, then retried. This time it only took a few seconds to find me. I then turned off GPS, rebooted, and moved to my semi-covered patio. After getting everything going again, it took 10-15 seconds to get a rough fix (off about 70 feet) and it continued to hold it even after I went inside. You may want to try clearing Maps' data (if that's what you're using) to see if that helps.
unomar said:
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
Click to expand...
Click to collapse
Whatever crash you're seeing isn't the one that I fixed. That one was produced a full-blown hardware crash with a register dump. Your logcat doesn't show a register dump or even a Java runtime exception dump. There were two errors that caught my eye but I don't know if either would cause an "Unfortunately..." popup.
Code:
04-08 09:40:24.213 E/DownloadTaskImpl( 3156): Download failed because of IO Error: Socket closed
04-08 09:40:24.213 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[7871, DEFAULT] mTrackTitle="Le onde" mRemoteId=9ea5817b-9753-348e-af52-ea7c0947c6cb mSourceAccount=1954430662 mPriority=3 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_7871.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=false]
Here, the (software) communication link being used to download "Le onde" was broken. Later on, you got this error:
Code:
04-08 09:40:57.133 I/wpa_supplicant( 618): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1a:30:e4:64:00 reason=0
[...]
04-08 09:40:59.803 E/DownloadTaskImpl( 3156): Download failed because of IO Error: recvfrom failed: ETIMEDOUT (Connection timed out)
04-08 09:40:59.803 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[363, DEFAULT] mTrackTitle="Black Hole Sun" mRemoteId=8076a782-8454-3fd8-899d-213bb23836ac mSourceAccount=1954430662 mPriority=0 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_363.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=true]
This download failure is a lot easier to understand: your WiFi connection had dropped. I don't know that either of these is something I can fix. As above, you may want to try the obvious fixes if you haven't done so already: use the most recent GApps package, clear the app's cache and data, and play with the app's caching options.