CyanogenMod 10.2 is a free, community built distribution of Android 4.3 (Jellybean) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of CM10.2 for the Samsung Galaxy Player 4. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Note: Please backup your efs in case of something goes wrong (the zip should backup it but we're never too sure) To do so execute this command:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs
Preview Install instructions:
*** If upgrading from CM9 or CM10 or even CM10.1, it is recommended that you wipe data.
1. Download cm-9-20130402-kernel-preflash.zip
md5: 4a900fcddbc3d81d121a7b9c9d4bb0a0
2. Download cm-10.2-20140210-UNOFFICIAL-ypg1
3. Make all your backups.
4. Make sure your efs is intact (not blank).
5. Boot into recovery, make more backups.
6. Flash cm-9-20130402-kernel-preflash.zip (temporary workaround for first-time install from stock)
7. Flash cm-10.2-20140210-UNOFFICIAL-ypg1
Note: To all those flashing 09/29 build and later, if you're in an old build of CM10.2, PLEASE RESTORE YOUR /EFS AFTER UPDATING!!!!. I moved the /efs partition and some items will get deleted prior flashing the update. It can lead to some issue with touchscreen with US devices.
Installation Notes:
When you install for the first time, there is a conversion to the new MTD partition layout. The installer will flash the new kernel and reboot. It is possible for this process to hang up on the samsung logo (still working that part out). It is normal to see the Samsung logo appear 3 seperate times during this reboot phase. **Please wait at least a minute before assuming you are stuck.** If this happens, you should extract the boot.img from the installer zip and flash it with heimdall (heimdall flash --kernel boot.img, or other appropriate GUI methods). It should boot back into recovery and continue the installation. Once the install finishes, it should reboot once more back into recovery, which gives you the opportunity to flash your gapps.
**Google Apps are not included in these ROMs. You'll need to install those yourself if you want them. Recommended and highly suggested are the 4.3 Gapps
Install video (Thanks Daniel644)
Known Issues:
- Video recording is limited to 800x600.
- Other things
Sources
cm-10.2 branch:
Device tree: https://github.com/bbelos/android_device_samsung_ypg1
cm-10.2-ypg1-dev branch:
Kernel source: https://github.com/bbelos/android_kernel_samsung_aries
Previous builds
cm-10.2-20131203-UNOFFICIAL-ypg1.zip
cm-10.2-20131116-UNOFFICIAL-ypg1.zip
cm-10.2-20131026-UNOFFICIAL-ypg1.zip
cm-10.2-20131014-UNOFFICIAL-ypg1.zip
cm-10.2-20130929-UNOFFICIAL-ypg1.zip
cm-10.2-20130914-UNOFFICIAL-ypg1.zip
cm-10.2-20130908-UNOFFICIAL-ypg1.zip
cm-10.2-20130821-UNOFFICIAL-ypg1.zip
cm-10.2-20130807-UNOFFICIAL-ypg1.zip
cm-10.2-20130731-UNOFFICIAL-ypg1.zip
Notice:
As per previous CM versions, it is recommend to wipe BOTH /system and /data prior installing CM10.2 into your device.
Here it is in case you're searching for it:
Gapps 4.3 Download
Issues:
- Right speaker that sound quieter than the left one (fixed 14/09)
- Front cam can't take pictures (fixed 10/02)
- Focal isn't working too (Use the stock camera app) It works but it's very slow to take a picture (07/08)
Superuser:
As 4.3 landed into our devices, the security into it has been enforced and it's possible that built-in superuser isn't working. As a simple fix, please use either this:
Koush Superuser Download
Or the newer version of SuperSU here:
http://forum.xda-developers.com/showthread.php?t=1538053
Again...
Wow! Just got this on my Gnex, not even official, and you already did it. Nice work. I'll give it a try when I have more time.
wow!
I thought your were gonna wait to perfect 4.2.2 but cant complain about keeping our device uptodate thanks.
does it have the same issues as 4.2.2?
Installed this ROM. ROM feels OK. My 90 DPI setting works. Should phone be missing from the app drawer?
Messaging crashes on boot.
Built in super user seems to be working for me.
Sent from my YP-G1 using Tapatalk 2
messaging FC's on boot and despite doing both links I still don't have a working SU app, aside from that and the lack of governors (can I use Impulse kernel on this?) seems pretty good.
Tobybitch said:
wow!
I thought your were gonna wait to perfect 4.2.2 but cant complain about keeping our device uptodate thanks.
does it have the same issues as 4.2.2?
Click to expand...
Click to collapse
Yep
daniel644 said:
messaging FC's on boot and despite doing both links I still don't have a working SU app, aside from that and the lack of governors (can I use Impulse kernel on this?) seems pretty good.
Click to expand...
Click to collapse
Hmm that's weird, I thought that super su would work. You're sure you're using the 1.51 zip? And CM10.2 is still in the works so expect fc everywhere lool.
Also impulse probably won't work with 4.3. There have been changes in the kernel and the ramdisk which makes it unusable.
Envoyé depuis mon Nexus 7 avec Tapatalk
What would have earned Superuser, you need to unlock developer mode.
Must be pressed several times on the build number in about tablet
zaclimon
You will collect kernel under 10.2 with the capabilities of both the Impulse?
How to swap the internal memory card on the outside?
While it was possible only through init.d, but when connected to the PC all comes back, you need to reboot (.
#!/system/bin/sh
mount -t vfat /dev/block/mmcblk0p1 /storage/sdcard1
mount -t vfat /dev/block/mmcblk1p1 /storage/sdcard0
Click to expand...
Click to collapse
S_m_O_k said:
What would have earned Superuser, you need to unlock developer mode.
Must be pressed several times on the build number in about tablet
zaclimon
You will collect kernel under 10.2 with the capabilities of both the Impulse?
How to swap the internal memory card on the outside?
While it was possible only through init.d, but when connected to the PC all comes back, you need to reboot (.
Click to expand...
Click to collapse
I don't understand your first question (translate must have messed up!). If it's about making a build with some impulse features, no I won't make them. (Impulse features remains in Impulse or any other custom kernel)
Also android 4.3 changes how sdcards are handled so for the moment, you can't switch them.
Well I went back into CWM did a Wipe Data/Factory reset, Wipe Cache and Wipe Dalvick then reinstalled Gapps (don't know if needed) and the Beta 2 from the first link (for superuser app) and rebooted and then enabled developer options and went down to root access and set it to Apps and ADb (was only Apps before) then opened Superuser (the new one not the baked in one) and it came up without issue so I tried to Overclock using No-Frills CPU and BANG the prompt to give Superuser access came up and all is well with the world.
Root is working now, I would not recommend trying the SuperSU 1.51 after this as it will delete the Superuser (that works) while trying to update the binaries, at which it fails to do.
are there plans to make an Impulse like kernel for this? I would really like to have the other governors as an option, I don't like the stock ones. Also for the time being I went in to the app manager and disabled messaging to prevent all the FC messages.
daniel644 said:
are there plans to make an Impulse like kernel for this? I would really like to have the other governors as an option, I don't like the stock ones. Also for the time being I went in to the app manager and disabled messaging to prevent all the FC messages.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44148903&postcount=55
Hope it answer your question.
Envoyé depuis mon Nexus 7 avec Tapatalk
great work!
the next step should be to get official cyanogenmod
theraf said:
great work!
the next step should be to get official cyanogenmod
Click to expand...
Click to collapse
I think the issues such as camera and speakers need to be fixed before we can get official Cyanogenmod.
Official CyanogenMod would be cool.
Sent from my YP-G1 using Tapatalk 2
dorfd1 said:
I think the issues such as camera and speakers need to be fixed before we can get official Cyanogenmod.
Official CyanogenMod would be cool.
Sent from my YP-G1 using Tapatalk 2
Click to expand...
Click to collapse
Speakers isn't that much of an issue but still needs to be fixed. As for the camera definitely needs to be fixed though.
daniel644 said:
Well I went back into CWM did a Wipe Data/Factory reset, Wipe Cache and Wipe Dalvick then reinstalled Gapps (don't know if needed) and the Beta 2 from the first link (for superuser app) and rebooted and then enabled developer options and went down to root access and set it to Apps and ADb (was only Apps before) then opened Superuser (the new one not the baked in one) and it came up without issue so I tried to Overclock using No-Frills CPU and BANG the prompt to give Superuser access came up and all is well with the world.
Root is working now, I would not recommend trying the SuperSU 1.51 after this as it will delete the Superuser (that works) while trying to update the binaries, at which it fails to do.
Click to expand...
Click to collapse
I installed SuperSU 1.51 by flashing the .zip at the same time as installing the ROM. It works straight out of the box as binaries are already updated.
No wipes, just install straight over 10.1 - after the usual rebuild of the dalvik cache (android is updating...) there was a further update of databases.
I used BaNkS Gapps, which I highly recommend as it installs only the core requirement - everything else can be downloaded from Play.
To get rid of the Messaging fc pop ups, I froze the app.
The baked in superuser works fine for me. I did not have to flash super su.
Sent from my YP-G1 using Tapatalk 2
zaclimon said:
Notice:
As per previous CM versions, it is recommend to wipe BOTH /system and /data prior installing CM10.2 into your device.
Here it is in case you're searching for it:
Gapps 4.3 Download
Issues: (Same as CM10.1)
- Right speaker that sound quieter than the left one
- Front cam still wonky
- HDR mode isn't working in camera
- Focal isn't working too (Use the stock camera app)
Superuser:
As 4.3 landed into our devices, the security into it has been enforced and it's possible that built-in superuser isn't working. As a simple fix, please flash either this:
https://plus.google.com/110558071969009568835/posts/bpXwTcHafo1
Or the newer version of SuperSU here:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Out of curiosity, what do you mean focal is not working. Is it that the auto focus function no longer works?
henk5066 said:
Out of curiosity, what do you mean focal is not working. Is it that the auto focus function no longer works?
Click to expand...
Click to collapse
It fcs
Swyped from my xoom
Related
This ROM is for the AT&T SGH-I437 ONLY! It is NOT for the GT-I8730! Just because Samsung named them both "Express" does not mean they have identicle internal hardware!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. Source code for the Samsung Express builds can be found on my github, www.github.com/jt1134. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Unofficial builds? Builds of the latest CyanogenMod source from github. This version is not officialy supported. If you find bugs/issues you can/must discuss here (do not submit bug reports on CyanogenMod issue tracker).
Downloads
Latest build (09/24/2013): http://www.mediafire.com/download/vtb5cyupdso2a84/cm-10.2-20130925-UNOFFICIAL-expressatt.zip
md5sum: 1a6952ced901e3b1be4c745db94c8ec6
Google Apps: http://goo.im/gapps/gapps-jb-20130813-signed.zip
Installation
- First time flashing CM10.2 to your Galaxy Express (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Can I request a feature?
If it is a feature in general CyanogenMod, please post the request at the CyanogenMod bug tracker.
http://jira.cyanogenmod.org
IRC
Join us on #samsung-express on freenode.net.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Please update to the recovery below when using this ROM. It supports compressed backups, and also works with ROM manager.
http://www.mediafire.com/download/dhdudqcl9oxzwj9/CWM-6.0.3.7-I437.tar
md5sum: 29870914ec833e0b07a95143073483f5
Download....Testing
Edit:
What is your--
Phone model: I437
Radio (baseband): MB3
CM version: 10.2 UNOFFICIAL
CM Download url: this thread
Gapps version: this thread
Did you--
wipe: data/cache/ factory
restore with titanium backup: No
reboot after having the issue: No
Are you using--
a task killer: No
a non-stock kernel: No
CMSettings/Performance settings (other than stock): Default
other modifications: No
Bugs:
1- SuperUser native of CM 10.2 don't work
2- maybe it's a bug but if you want to create a second partition on the SD will not let me ride it though is the same as used in Cyanogenmod 10.1 and if it worked
3-by clicking on the SELinux option freezes the phone
4-the video is somewhat blurry and distorted
Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
Everhez said:
Bugs:
1- SuperUser native of CM 10.2 don't work
Click to expand...
Click to collapse
Fixed.
2- maybe it's a bug but if you want to create a second partition on the SD will not let me ride it though is the same as used in Cyanogenmod 10.1 and if it worked
Click to expand...
Click to collapse
I don't know what you are asking.
3-by clicking on the SELinux option freezes the phone
Click to expand...
Click to collapse
Don't click on it.
4-the video is somewhat blurry and distorted
Click to expand...
Click to collapse
Fixed.
jt1134 said:
Fixed.
I don't know what you are asking.
Don't click on it.
Fixed.
Click to expand...
Click to collapse
what happens is that I make a second partition on the sd to spend CM 10.2 apps but will not let me mount
Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
Updated OP. Fixed random bugs, updated to latest code from upstream CyanogenMod.
Love it so far, much better than the stock! Noob question though.. How can I install google apps onto here? I haven't found any way to do so yet. Can you point me towards a google apps package to flash?
Sworder said:
Love it so far, much better than the stock! Noob question though.. How can I install google apps onto here? I haven't found any way to do so yet. Can you point me towards a google apps package to flash?
Click to expand...
Click to collapse
READ! It's sitting right there in the download links.
JDC2389 said:
READ! It's sitting right under the download link, GAPPS is google apps.
Click to expand...
Click to collapse
wow. Thank you.
Seems Koush Su is still unstable in 4.3, I'm on Modem i437UCDMG3. Flashing supersu 1.51 zip and I'll see how it goes.
E: All is fine after switching to SuperSu, as predicted.
Bugs
native superuser is not working this must install the recovery ..Link2SD does not work on android 4.3 for the second partition
excuse my bad English but I use google translator if you do not understand me jt1134 :banghead:
Everhez said:
native superuser is not working this must install the recovery ..Link2SD does not work on android 4.3 for the second partition
Click to expand...
Click to collapse
The issues with Superuser are part of the CM10.2 bring-up process. There's technically a simple fix for it, but is has other implications. The easiest way to correct the issue for now is to go into development settings, and just toggle root access option.
As far as link2sd, I don't understand why you would use that on such a new firmware ? That's meant for outdated devices that had limited internal storage.
jt1134 said:
The issues with Superuser are part of the CM10.2 bring-up process. There's technically a simple fix for it, but is has other implications. The easiest way to correct the issue for now is to go into development settings, and just toggle root access option.
As far as link2sd, I don't understand why you would use that on such a new firmware ? That's meant for outdated devices that had limited internal storage.
Click to expand...
Click to collapse
the detail that is because I use link2sd install heavy games that are memory intensive data, then use this method to switch apps with. ,apk. ,dex. , .lib weighing pretty and so do the games space is impossible to transfer the SD
Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
Games like Subway Surf are not working !!! ! It just shows a black screen ! Please help
Slim Burst !
Samkitpalecha said:
Games like Subway Surf are not working !!! ! It just shows a black screen ! Please help
Slim Burst !
Click to expand...
Click to collapse
I got a logcat with some info on trickstermod interaction and that subway surf blackscreen problem, hope it sheds some light.
The headphone jack does not work, but it still responds when something is plugged into it/removed. When I have music player playing a song, it plays through the speakers fine, then when I plug in an AUX cable, it doesn't come through the headphones. When I remove AUX it stops playing like it normally would.
Sworder said:
The headphone jack does not work, but it still responds when something is plugged into it/removed. When I have music player playing a song, it plays through the speakers fine, then when I plug in an AUX cable, it doesn't come through the headphones. When I remove AUX it stops playing like it normally would.
Click to expand...
Click to collapse
Mine works, try reflashing the OS and make sure you wipe system like 4 or 5 times.
edit: I take it back, it worked for a bit on headphone jack then some weird static and the headphone jack went dead. Here is another logcat, unplugging and replugging the headphone and restarting pandora and trying it again, same dead jack. Maybe I'll get lucky and logcat the jack going haywire in the act.
Weird, I got the headphone jack issue thing randomly, rebooted and I don't know if it did that again. But I have been having this problem with music files failing to play off my sdcard, it gets corrupted randomly. Heres another log, just take a peek at the errors I guess.
The headphone jack started to work after I rebooted my phone, but it stopped when I rebooted again. Also, another thing I've noticed is my app folders I try to create get undone after reboot. I'm not sure if this is a bug or not.
I few apks got corrupted after a reboot and I had to reinstall them, reddit news, and the adobe flash player apk in my browser.
CyanogenMod 11 is a free, community built distribution of Android 4.4 (Kitkat) which greatly extends the capabilities of your phone, tablet or PMP.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
These are CM11 builds for the Samsung Galaxy Player 4.0. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Note: Please backup your efs in case of something goes wrong (the zip should backup it but we're never too sure) To do so execute this command:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs
Download: http://download.cyanogenmod.org/?device=ypg1
Rom Install instructions:
If coming from stock:
1. Download the CM zip
2. Make your backups!!
3. Make sure your efs is intact (not blank)
4. Boot into recovery
5. Flash the CM zip (Note: upon flashing it, your device will hang, IT'S NORMAL. Wait about 10-20 secs then force reboot your device)
6. Let the installer do it's things...
7. The device will reboot a last time into recovery where you can flash gapps if you want. (No wipe is necessary at this point because the zip have wiped it)
8. Reboot
9. Enjoy!!
If coming from a Pre-LVM build: (ALL builds before 28/12 as well as CM10.1, CM10.2)
1. Download the CM zip
2. Boot into recovery
3. Make a nandroid backup
4. Flash the CM zip (You'll receive an warning concerning /data partition, it didn't flashed anything yet so you can make a final check before flash)
5. Reflash the CM zip again (the zip will reboot your device into recovery again and this reboot is needed!!!)
6. After the reboot, reflash for a third time the zip (The real installation begins!!)
7. After the installation succeded, you can flash your gapps and restore your data from an advanced restore with nandroid (IF NEEDED as the zip wipes data for the new partition layout)
8. Reboot
9. Enjoy!!
If coming from an LVM build:
1. Download the CM zip
2. Boot into recovery
3. Flash the CM zip
4. Flash Gapps (If necessary)
5. Enjoy!!
Pre-LVM rom instructions!! (Deprecated)
1. Download cm-9-20130402-kernel-preflash.zip (md5: 4a900fcddbc3d81d121a7b9c9d4bb0a0)
2. Download cm-11-20131208-UNOFFICIAL-ypg1.zip
3. Make all your backups.
4. Make sure your efs is intact (not blank).
5. Boot into recovery, make more backups.
6. Flash cm-9-20130402-kernel-preflash.zip (temporary workaround for first-time install from stock)
7. Flash cm-11-20131208-UNOFFICIAL-ypg1.zip
Installation Notes:
When you install for the first time, there is a conversion to the new MTD partition layout. The installer will flash the new kernel and reboot. It is possible for this process to hang up on the samsung logo (still working that part out). It is normal to see the Samsung logo appear 3 seperate times during this reboot phase. **Please wait at least a minute before assuming you are stuck.** If this happens, you should extract the boot.img from the installer zip and flash it with heimdall (heimdall flash --kernel boot.img, or other appropriate GUI methods). It should boot back into recovery. You need to flash the zip one more time as CWM made some changes since 4.3 and thus, the *smooth* installation isn't working anymore. Once the install finishes, you should be able to flash your gapps.
Install video (Thanks Daniel644)
Previous builds (Pre-LVM)
cm-11-20131201-UNOFFICIAL-ypg1.zip
cm-11-20131121-UNOFFICIAL-ypg1.zip
Click to expand...
Click to collapse
Please do NOT report something related to ART yet, as it is a experimental feature, there's stuff that are expected to break
**Google Apps are not included in these ROMs. You'll need to install those yourself if you want them. Recommended and highly suggested are the 4.4 Gapps
Known Issues:
- You tell me
Previous builds: (LVM)
cm-11-20140917-UNOFFICIAL-ypg1.zip
cm-11-20140824-UNOFFICIAL-ypg1.zip
cm-11-20140811-UNOFFICIAL-ypg1.zip
cm-11-20140707-UNOFFICIAL-ypg1.zip
cm-11-20140610-UNOFFICIAL-ypg1.zip
cm-11-20140517-UNOFFICIAL-ypg1.zip
cm-11-20140421-UNOFFICIAL-ypg1.zip
cm-11-20140323-UNOFFICIAL-ypg1.zip
cm-11-20140312-UNOFFICIAL-ypg1.zip
cm-11-20140209-UNOFFICIAL-ypg1.zip
cm-11-20140115-UNOFFICIAL-ypg1.zip
cm-11-20140107-UNOFFICIAL-ypg1.zip
cm-11-20131228-UNOFFICIAL-ypg1.zip
Sources
cm-11.0 branch:
Device tree: https://github.com/bbelos/android_device_samsung_ypg1
cm-11.0-ypg1-dev branch:
Kernel source: https://github.com/bbelos/android_kernel_samsung_aries
Notice:
As per previous CM versions, it is recommended to wipe BOTH /system and /data prior installing CM11 into your device.
Gapps:
Here's gapps I've been using and it do works with ART, the latest one should work just fine. (Thanks to dhacker29):
http://d-h.st/users/dhacker29/?fld_id=27426#files
There's also BaNkS gapps in which core gapps only weights about 20MB and contains only basic stuff like sync and play store:
http://forum.xda-developers.com/showthread.php?t=2012857
Also here's a website where you can find the ART compatible apps (Thanks @TheTehk17 for the tip):
http://www.androidruntime.com/list
Screenshots courtesy of @ti-pich
Holy mother of god, that's awesome. Now I know what to do, flashing time! Thanks
Edit: Only for the info, what is the size of our system partition? Is it 1.85 Gb?
ti-pich said:
Holy mother of god, that's awesome. Now I know what to do, flashing time! Thanks
Edit: Only for the info, what is the size of our system partition? Is it 1.85 Gb?
Click to expand...
Click to collapse
The actual size of /system is 455,5 MB. I could squeeze other partitions space to get a 10mb more. The other thing I could do is to make like actual Aries device which they merge /system and internal SD card. Which give us a whole lot of space but would take a bit of time to implement because I'm really busy right now. (cegep as you know...)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
zaclimon said:
The actual size of /system is 455,5 MB. I could squeeze other partitions space to get a 10mb more. The other thing I could do is to make like actual Aries device which they merge /system and internal SD card. Which give us a whole lot of space but would take a bit of time to implement because I'm really busy right now. (cegep as you know...)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
Yeah I know what it is, alot of work all at the same time. I only wanted to know the size, for me 455mb is way enought space, I install almost nothing on my player to keep it clean. On the other way, just finished wiping/flashing/repairing everything, running it right now and setting my stuff, so far so good, all is going as it should. One thing I noticed is that the status bar isn't transparent, no big deal, I think it's not in cm for now, or maybe I forgot something.
ti-pich said:
Yeah I know what it is, alot of work all at the same time. I only wanted to know the size, for me 455mb is way enought space, I install almost nothing on my player to keep it clean. On the other way, just finished wiping/flashing/repairing everything, running it right now and setting my stuff, so far so good, all is going as it should. One thing I noticed is that the status bar isn't transparent, no big deal, I think it's not in cm for now, or maybe I forgot something.
Click to expand...
Click to collapse
Transparent status bar is implemented in android 4.4, However, the thing is I set a special flag for our devices here :
https://github.com/bbelos/android_device_samsung_ypg1/commit/f0f6b0f812ea820a581957446b05c36c912c1616
This flag disable all framework fancy stuff (as well as other things you've probably seen) to be sure that it doesn't use as much ram as possible. You can remove it, it's in the build.prop. I do know that I've enabled lockscreen transparent status bar but I don't think I've enabled it for the home screen.
Should the play store apk be missing from the gapps?
.
Found it in priv-app.
Sent from my YP-G1 using Tapatalk
dorfd1 said:
Should the play store apk be missing from the gapps?
Sent from my YP-G1 using Tapatalk
Click to expand...
Click to collapse
No it shouldn't. As I said, you may want to remove some apps because maybe the limitations of the space cause some apps to not install properly... You can try these gapps too. (though I can't confirm their compatibility with ART)
http://forum.xda-developers.com/showthread.php?t=2012857
The core are the lightest ones (about 20 MB but include basically the play store and sync stuff)
Messaging app force closes.
YouTube has issues with HD video.
Sent from my YP-G1 using Tapatalk
dorfd1 said:
Messaging app force closes.
YouTube has issues with HD video.
Sent from my YP-G1 using Tapatalk
Click to expand...
Click to collapse
How do you even get YouTube to play HD? I have to use a modded apk using the old YouTube app
Sent from my YP-G70 using Tapatalk
I set my device DPI to 90 because I prefer the tablet ui experience. I think if you set your device DPI to 213 or lower it should play HD video without the need for a nodded apk.
Sent from my YP-G1 using Tapatalk
zaclimon said:
The actual size of /system is 455,5 MB. I could squeeze other partitions space to get a 10mb more. The other thing I could do is to make like actual Aries device which they merge /system and internal SD card. Which give us a whole lot of space but would take a bit of time to implement because I'm really busy right now. (cegep as you know...)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
Wait, you're going to cegep... you're not by any chance going to Marianopolis, are you? If you are, we've been going to the same college without knowing it since august!
trainman261 said:
Wait, you're going to cegep... you're not by any chance going to Marianopolis, are you? If you are, we've been going to the same college without knowing it since august!
Click to expand...
Click to collapse
Nope, I'm in ahuntsic since the beginning of the year. (Marianopolis, Dawson, etc are a bit too far from my home as I live in the north-east side of the island XD) It would have been funny that we haven't seen each other since the first day loool.
Actually I'm kinda surprised that that there's a 3rd Canadian here!! (even more another qcer)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Wow can't wait to try this out especially for the RAM usage and ART One thing though...is Voodoo Sound included as usual?
-sandro- said:
Wow can't wait to try this out especially for the RAM usage and ART One thing though...is Voodoo Sound included as usual?
Click to expand...
Click to collapse
Try and you'll see.
EDIT: @ti-pich posted screenshots and answered the question even though I wanted you to check the surprise... XD
Envoyé depuis mon Nexus 7 avec Tapatalk 4
-sandro- said:
Wow can't wait to try this out especially for the RAM usage and ART One thing though...is Voodoo Sound included as usual?
Click to expand...
Click to collapse
Yup, voodoo is included in dsp manager. Here are some screenshot for everyone, hope you enjoy them.
Installing right now
zaclimon said:
Transparent status bar is implemented in android 4.4, However, the thing is I set a special flag for our devices here :
https://github.com/bbelos/android_device_samsung_ypg1/commit/f0f6b0f812ea820a581957446b05c36c912c1616
This flag disable all framework fancy stuff (as well as other things you've probably seen) to be sure that it doesn't use as much ram as possible. You can remove it, it's in the build.prop. I do know that I've enabled lockscreen transparent status bar but I don't think I've enabled it for the home screen.
Click to expand...
Click to collapse
So to enable the transparent status bar on the home screen I have to set to false that value and abandon Project Svelte??
BTW it's not transparent in the lock screen:angel:
-sandro- said:
So to enable the transparent status bar on the home screen I have to set to false that value and abandon Project Svelte??
BTW it's not transparent in the lock screen:angel:
Click to expand...
Click to collapse
Well idk about project svelte(maybe, maybe not) but yes it enables transparent status bar.(and you need to reboot your device to take effect. )
Envoyé depuis mon Nexus 7 avec Tapatalk 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This rom is for both the Nook Tablet 512M/8GB and 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A recovery. To install a recovery when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Grab a new recovery (e.g. here https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img) and flash it with fastboot.
If you have a CM 10.1 or CM 11 installed, flash the new recovery and try the updater, otherwise download the zip from nightlies, boot to CWM and flash it.
Once a version is installed (and all bugs fixed), you will be able to use CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
THE NEW NIGHTLIES HAVE EMULATED STORAGE ENABLED. YOU LOOSE ALL YOUR DATA. MAKE SURE YOU BACKUP!!!! THE INTERNAL EMMC 1GB PARTITION IS ALSO NOT ACCESSIBLE ANYMORE. COPY THE CONTENT. THE EXTERNAL SDCARD IS NOT USED ANYMORE AS PRIMARY STORAGE. ALL APP DATA ON THE SDCARD WILL BE LOST. I ALSO RECOMMEND TO WIPE.
BACKUP!
RE-PARTITIONING IS NOT MANDATORY. IF YOU WANT TO RECLAIM THE 1GB PARTITION (called media) YOU CAN TRY TO FOLLOW THE RE-PARTITION GUIDE:
https://docs.google.com/document/d/1wSAaAZfQcnvkiHKlbZ7_H1h67m2kx0mq-p3Wjgue3qA/edit?usp=sharing
PLEASE COMMENT ON THE DOCUMENT IF SOMETHING IS NOT CLEAR.
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to recovery, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg, logcat and audit.log information. If you don't know what this is or how to get them, try to find that out first before posting here.
Thanks:
hashcode, ntemis, kuzma30, fattire, mik_os, chrmhoffmann, and many others that contribute to cyanogenmod and especially this version.
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device. Also many thanks for the L bringup help.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 and L I have copied lots of things from you
DISCLAIMER:
- update the CWM if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- Also you must flash gapps. It can be found somewhere....
ATTENTION: IT SEEMS THAT DHACKER'S L GAPPS ARE TOO BIG TO FIT INTO THE SYSTEM PARTITION. Try to find a smaller one.
- The SELINUX policies are enforced now.
Known issues:
- system partition is too small for full gapps. use a mini gapp package.
- the touchscreen firmware flasher doesn't work on L. Use CM11 to flash it first.
Recently fixed:
- f2fs
- kernel updated to latest 3.0 stable
- developer settings and setup wizard (if you select backup) crash. that's fixed in nightly from 8-FEB-15.
- device encryption does work now (but who wants to do that? the device is laggy enough already )
- cmupdate / cm recovery: adb reboot recovery and cmupdater and auto install. Hopefully this is fixed now (not in nice way, but...). You need sdcard inserted to make this work (but I guess everybody has that anyway).
Get it from
http://download.cyanogenmod.org/?device=acclaim
Get ENG recovery from here. It allows to adb into recovery even when data is wiped.
File: https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img
md5sum: 6136fc49c5e9a32f115d40d762bb6f2d
Reserved
...
Amazing work Chris, Let the flashing begin.
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
chrmhoffmann said:
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
Click to expand...
Click to collapse
ROM: 78f32eb89778b31a569644b21fc1e8f3
Recovery: d37f29808a682e7806fa7b77dc940453
Installed just fine here, even Netflix works!!
thanks for everyone's hard work.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
billy8362 said:
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/acclaim
Download the latest version, rename it to "recovery.img". Flash it in fastboot.
If you'd rather not go that route, download a flashable of an older version of TWRP, use 7zip to delete the recovery.img in that folder, then move this new TWRP into that folder. Then flash that.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Update:
All ok after i format 10+11 partitions.
chrmhoffmann said:
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Click to expand...
Click to collapse
Too busy to play with my Nook this week. I recall it was having issues with signature verification. I wasn't able to locate a way to disable signature verification.
Pepe.II said:
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Click to expand...
Click to collapse
Same issue here ... used TWRP ... everything seems to work except I don't have an SD card ... which is a deal breaker for this tablet.
UPDATE: Used the wrong GAPPS the first time ... working fine now ... sluggish, but nothing seems to be broken ... and I didn't do a factory reset ... just cache/davlik cache clear then flash
Get ready for Bexus-L
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
sagirfahmid3 said:
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Click to expand...
Click to collapse
jerrygarcia4295 said:
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
Click to expand...
Click to collapse
Google's apps come with Google's playstore, sync services, etc, which add overhead to wi-fi and CPU cycles.
F-droid doesn't have those services. It's pretty much like a Linux package manager--you use it to install and keep track of open source packages.
Besides, I only use my phones and tablets for Kodi and phone calls. I'm not into Google Hangouts or YouTube, etc. I don't take pictures, I don't use the GPS...
IMO, I find Android to be completely useless. I wish there was a completely open source and open hardware Linux running phone. With Linux, you can do whatever you want.
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
jerrygarcia4295 said:
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
Click to expand...
Click to collapse
I haven't installed cm12 on my nook tablet yet, but on other cm12 installs, you have to enable superuser in Settings / Developer options / Root access. Click one of the boxes other than the default "Disabled". If that doesn't work, some folks swear by SuperSU, which you can find in the Play Store
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOSdoes still include various hardware-specific code, which is also slowly being open-sourced anyway.
Important information:
This thread is for Unofficial LineageOS 13.0 builds for v2awifi (SM-T900). The following will not be supported here:
Custom kernels
Mods
Xposed
Do not ask for ETAs. If you do, I will ignore you and your post.
SEANDROID ERROR
If you see a message at boot about Recovery or Kernel is not SEANDROID Enforcing, you can ignore it. This is just telling you that you are not running Samsung stock software. It has no effect on recovery or the ROM itself nor related to either.
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Bootloader Information
You need to make sure you have a Lollipop bootloader installed or else your device won't boot. Here you can go grab the latest bootloader and odin and flash it in download mode. Read all the steps before you do this.
Make sure you have a full backup because just in case you something fails.
Here are the steps to flash this via ODIN:
Make sure you have a full backup because just in case you something fails. Here are the steps to flash this via ODIN.
Reboot your tablet into download mode. Do this by first switching off the phone, then pressing and holding the volume down + home button together and then pressing the power button. Press volume up button to enter download mode.
Open ODIN on your computer. You?ll see the ID:COM box turning yellow with a COM port number upon successful connection with the tablet.
In ODIN click the BL button, select the bootloader firmware. It's a tar file.
Make sure Auto Reboot & F. Reset Time options are selected in ODIN
Click on the start button. When the process is completed your phone will reboot.
Installation
Download the zip(s)
Install a compatible Recovery (This will not work with the P900 recovery)
--1.*I have built a new version of TWRP with the MM kernel. MTP, Vibations, ADB now work and there are performance increases. The rom will need to allow v2awifi naming for flashing in recovery. Link
Perform a nandroid backup of your current ROM (optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
Issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs or it didn't happen! You can use this: Syslog App
Downloads
Nightlies
Latest Nightly Date 12/23/16
Device Builds
Google Apps
http://opengapps.org/ - Thanks to the OpenGapps team!
Issues
Lower than stock audio volumes
MHL out to TV not working
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging, & documentation.
Source:
Kernel: Link
Device Tree: Link
Credits
@Valera1978 Initial device tree
@UpInTheAir for his kernel magic and misc fixes
@chhaggerty, @tbjr50 and @titidu3701 for their testing efforts
Exynos5420 Dev Team ( @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart )
XDA: DevDB Information
[6.0.x|SM-T900| Unofficial LineageOS 13.0 (v2awifi), ROM for the Samsung Galaxy Tab Pro 12.2
Version Information
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Status: Stable
Created 2016-10-01
Last Updated 2016 -12-23
Kernel Info:
M Kernel base from the Galaxy Tab S
M GPU driver from Galaxy Tab S
CPU Voltage Control
CPU OverClock/UnderClock (Up to 2.1GHZ)
MIF/INT Voltage Control
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot
Exynos thermal exposed to sysfs
Android Logger disabled by default can be enabled over sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128
Currently Disabled:
GPU Voltage Control/GPU OverClock/UnderClock (Needs to be rewritten for the M driver)
Awesome!
Thank you very much Tom!
Thank you! I would like to report that vibration isn't working. Other than that, everything works great.
c19932 said:
Thank you! I would like to report that vibration isn't working. Other than that, everything works great.
Click to expand...
Click to collapse
I will look into this. I am fairly confident I know what the fix is. Thanks for the feedback.
Hmmm...
I did wipe cache/dalvik cache/system and data with TWRP 2.8.7.0
and installed your cm-13.0-20161001-UNOFFICIAL-v2awifi.zip along with the open_gapps-arm-6.0-pico-20160925.zip (which I got as .ZIP for/from my Nexus 10)
After installing wiping cache/dalvik cache again and reboot system - but then after the SM-T900 Logo the screen is only blank.
No boot animation and no other sign that it will do something.
I could go to TWRP via Power+VolUp+Menue....
Do you got an Idea what went wrong?
[EDIT] also only the cm-13.0-20161001-UNOFFICIAL-v2awifi.zip without Open GApps gives me a black screen.
For now Iam back on CM 12.1 from the 09.07. and pico Open GApps from today.
Why was the SM-T900 files formerly named v2wifixx and now v2awifi? Could this be a problem for me?
guidol, try updating your bootloader, as per the OP.
TP, thanks much for your work on Tab/Note Pro 12.2.
gorgthetroll said:
guidol, try updating your bootloader, as per the OP.
TP, thanks much for your work on Tab/Note Pro 12.2.
Click to expand...
Click to collapse
How to do that? I have the same issue. Thnx
gorgthetroll said:
guidol, try updating your bootloader, as per the OP.
Click to expand...
Click to collapse
Thanks @gorgthetroll
Now it works - didnt read the part before the installtion carefully enough
@kutzman: read the part above the part of the installtion instruction:
Bootloader Information
You need to make sure you have a Lollipop bootloader installed or else your device won't boot.
I did this Bootloader-Part with Odin (Ok, on my device I has it to fo 2 times and 2 times it told me OK, but it did boot with a read Message about the Kernel in the 2nd try.
Now - after the seond try of the BootLoader-Flash my SM-T900 did boot - so I updated the TWRP via Flashify to the latest version (3.0.2.0) - but for that you have to enable root access in the developer options of CM13
thompatry said:
I will look into this. I am fairly confident I know what the fix is. Thanks for the feedback.
Click to expand...
Click to collapse
Does look great the first version of the CM13 for the SM-T900 :good:
Sadly I can confirm the missing vibration.
But as I did promise you - I donated another $30 for the "working" version of CM13 :laugh:
I hope this will encourage your development on the SM-T900-Builds! :angel:
guidol said:
Does look great the first version of the CM13 for the SM-T900 :good:
Sadly I can confirm the missing vibration.
But as I did promise you - I donated another $30 for the "working" version of CM13 :laugh:
I hope this will encourage your development on the SM-T900-Builds! :angel:
Click to expand...
Click to collapse
Thanks a lot to Guidol for being the most generous "facilitator", helping keep our great Tom in great spirit
Glad to see this rom!
Thank you for a working MM build for this amazing tablet, which I lost hope for any development. I appreciate all the hard work you put into getting this working!
I am having issues with the Play Store hanging at times and the File Manager not showing up properly and slowing down the device significantly
Getting a lot of issues regarding "Package Installer"
No Xposed installed*
Edit: tried multiple file managers from the Play Store and each have problems. No way to view files
Neekeet said:
Glad to see this rom!
Thank you for a working MM build for this amazing tablet, which I lost hope for any development. I appreciate all the hard work you put into getting this working!
I am having issues with the Play Store hanging at times and the File Manager not showing up properly and slowing down the device significantly
Getting a lot of issues regarding "Package Installer"
No Xposed installed*
Edit: tried multiple file managers from the Play Store and each have problems. No way to view files
Click to expand...
Click to collapse
Make sure you did a clean install, as mentioned in the OP's original message, and use an up-to-date OpenGapps package (for ARM, 6.0).
Thanks,
Eric
vochong said:
Make sure you did a clean install, as mentioned in the OP's original message, and use an up-to-date OpenGapps package (for ARM, 6.0).
Thanks,
Eric
Click to expand...
Click to collapse
Thanks for the reply
I have a clean installation and the exact same Gapps package installed.
Going to reflash and see keep an eye out for better results
Anyone else notice their tablet getting really hot? near the camera front and back.
Edit: Just reflashed using the Nano Gapps package and everything seems to be working great! will update if i run into anything. I had issues using the Pico version and wonder if that is suspect to the issues I was having. Any ideas?
Neekeet said:
Thanks for the reply
I have a clean installation and the exact same Gapps package installed.
Going to reflash and see keep an eye out for better results
Anyone else notice their tablet getting really hot? near the camera front and back.
Edit: Just reflashed using the Nano Gapps package and everything seems to be working great! will update if i run into anything. I had issues using the Pico version and wonder if that is suspect to the issues I was having. Any ideas?
Click to expand...
Click to collapse
Since the system partition in SM-T900 is quite large, I've always installed the STOCK package so it would remove most of the built-in stock/AOSP apps/tools and replace them with Google ones.
Also, with the STOCK package, I can still have access to useful Google apps even after a configuration reset, and without Google login (to download apps from Google PlayStore.)
Thanks,
Eric
Neekeet said:
Edit: tried multiple file managers from the Play Store and each have problems. No way to view files
Click to expand...
Click to collapse
I didnt got a problem with the EFS Explorer.
But for some access-methods you have to grant access-rights if the app/CM13 did ask.
And I got root-access enabled in the developer options.
---------- Post added at 06:25 PM ---------- Previous post was at 06:16 PM ----------
Neekeet said:
Edit: Just reflashed using the Nano Gapps package and everything seems to be working great! will update if i run into anything. I had issues using the Pico version and wonder if that is suspect to the issues I was having. Any ideas?
Click to expand...
Click to collapse
I didnt got any Problems with the pico Open GApps.
But you have to install something like GMail afterwards to get the actual Google/Playstore Services as Update.
After that I only do install the Google-Appsvthat I want.
Love this feature not having some odd G-Services in the Background or in the System-Partition.
(and I also use the pico on my Nexus 10 with CM13 because there is the /system only 800MB in size)
---------- Post added at 06:51 PM ---------- Previous post was at 06:25 PM ----------
Neekeet said:
Anyone else notice their tablet getting really hot? near the camera front and back.
Click to expand...
Click to collapse
on normal usage I didnt noticed the tablet being really hot.
Which apps do you use at this time? games with much graphics?
Tom did write about the voltage-selector of the gfx-card(?) that the voltage cant set down for underclocking or higher for overclocking....or somthing like this....moment I will copy the part...
"
Currently Disabled:
GPU Voltage Control/GPU OverClock/UnderClock (Needs to be rewritten for the M driver)
"
Dont know if your tablet will be hot about this disabled setting....
Everything is running fine now! thanks everyone
Love having MM on this tablet finally haha
Anyone's tablet feel a bit sluggish? it may be difficult to replicate but bringing down notifications seems to have some lag to it
Neekeet said:
Anyone's tablet feel a bit sluggish? it may be difficult to replicate but bringing down notifications seems to have some lag to it
Click to expand...
Click to collapse
for its fast as before with CM12....the Notifications werent for me the fastest ones....but Iam happy wirh this first build.
guidol said:
for its fast as before with CM12....the Notifications werent for me the fastest ones....but Iam happy wirh this first build.
Click to expand...
Click to collapse
Try to change the speed for windows animations, and the transition and animator duration. You can do that in developer options half way xown deist under drawing. Change the settings from window animation s ale, transition animation scale and animator duration scale from 1 to 0.5. See attached screenshot
pandoraman said:
Try to change the speed for windows animations, and the transition and animator duration. You can do that in developer options half way xown deist under drawing. Change the settings from window animation s ale, transition animation scale and animator duration scale from 1 to 0.5. See attached screenshot
Click to expand...
Click to collapse
I did try these settings - seems to be much better - many thanks