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
Related
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
CyanogenMod 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.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=vs985&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your must be on the 35b boot stack. Here's a flashable zip provided by xdabbeb: https://www.androidfilehost.com/?fid=24052804347843993
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/vs985/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_vs985
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Verizon LG G3, ROM for the Verizon LG G3
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly
Created 2015-11-24
Last Updated 2015-11-24
So do we dirty flash over unofficial or clean flash with the nuke it.apk?
rippedwarrior69 said:
So do we dirty flash over unofficial or clean flash with the nuke it.apk?
Click to expand...
Click to collapse
I dirty flashed with no issues.
A quick note for those who want to get Facebook and Messenger working . Delete the following files in your file browser (note that you must enable root access for apps in Developer Options):
/data/app/com.facebook.katana-1/lib/arm/libsslx.so
/data/app/com.facebook.orca-1/lib/arm/libsslx.so
Note that you still won't be able to make phone or voice calls in FB/Messenger.
NedDasty said:
I dirty flashed with no issues.
A quick note for those who want to get Facebook and Messenger working . Delete the following files in your file browser (note that you must enable root access for apps in Developer Options):
/data/app/com.facebook.katana-1/lib/arm/
/data/app/com.facebook.orca-1/lib/arm/
Note that you still won't be able to make phone or voice calls in FB/Messenger.
Click to expand...
Click to collapse
Did you use nukeit.apk
rippedwarrior69 said:
Did you use nukeit.apk
Click to expand...
Click to collapse
Read this post. My guess is that you do not need it. CM13 was unofficial earlier, which meant the official branch had incompatibilities with VS985, which were fixed with the Nuke-it flash. The latest official adoption, and merge, have resolved these already, but Invisiblek would be able to clarify better than I.
Thanks for the Rom. Will report on any undocumented bugs.
Reformat ext sd card?
Does CM13 still require you to reformat any external SD card it recognizes? Sorry, haven't tried this new version, and will have to back up my card if this is still a requirement
TIA
:cyclops:
The ROM itself is running STUPID fast on my phone. Love the speed of everything.
I am having issues with this not maintaining the Connection to my Android Wear device. It seems to disconnect, and then forget the connection. Facebook and Snapchat will not start, even after deleting the folders in the previous posts.
Anyone here tested out Qi Charging yet?
Trouble connecting/authenticating to Enterprise WiFi after flashing. Credentials are being rejected and authentication is failing. Has anyone else experienced this?
This happens with a fresh or dirty install. It's almost as if the cert isn't being accepted/applied.
marnett2005 said:
I am having issues with this not maintaining the Connection to my Android Wear device. It seems to disconnect, and then forget the connection. Facebook and Snapchat will not start, even after deleting the folders in the previous posts.
Click to expand...
Click to collapse
I think this might be a Bluetooth problem in general--I have to re-pair my car to my phone every time I get in.
Icanthelplt90 said:
Anyone here tested out Qi Charging yet?
Click to expand...
Click to collapse
Works fine for me!
I saw in the other thread that there were data issues with some builds. Have those been resolved, or is it still inconsistent?
goldsmitht said:
Does CM13 still require you to reformat any external SD card it recognizes? Sorry, haven't tried this new version, and will have to back up my card if this is still a requirement
TIA
:cyclops:
Click to expand...
Click to collapse
I read somewhere that if you try booting twrp, unmount then remount the sdcard, it may work
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
@invisiblek with the 35b bootstack, can I flash it if I'm on 12.1 still? And then the subsequent radio as well?
goldsmitht said:
Does CM13 still require you to reformat any external SD card it recognizes? Sorry, haven't tried this new version, and will have to back up my card if this is still a requirement
TIA
:cyclops:
Click to expand...
Click to collapse
I didn't have any issues, though it did ask me to configure my sd card. Basically, you can decide to use the "transfer" option, which leaves it alone, or you can format it as internal storage. Note: if you go with the internal storage, it won't work with any other devices and will require a format.
---------- Post added at 06:07 PM ---------- Previous post was at 06:04 PM ----------
Has anyone had any issues with the phone crashing randomly? I dirty flashed over my 12.1 nightly (a recent one), updated all possible gapps, and flashed the new xposed module.
Update: I decided to flash the firmware suggested in the top post, and updated supersu at the same time. Now its stuck on a boot animation loop apparently. I call this progress, because if I call it anything else I might just break down and cry. I'm preparing myself mentally for the inevitable full wipe I most likely face.
ender89 said:
Update: I decided to flash the firmware suggested in the top post, and updated supersu at the same time. Now its stuck on a boot animation loop apparently. I call this progress, because if I call it anything else I might just break down and cry. I'm preparing myself mentally for the inevitable full wipe I most likely face.
Click to expand...
Click to collapse
You don't need supersu cm has it built in.
ender89 said:
I didn't have any issues, though it did ask me to configure my sd card. Basically, you can decide to use the "transfer" option, which leaves it alone, or you can format it as internal storage. Note: if you go with the internal storage, it won't work with any other devices and will require a format.
But will I be able to use the ext sd card if I flash a backed 12.1?
Click to expand...
Click to collapse
Anybody using our tried sending mms? If it worked, then how?
The messaging apps I tried are : stock, textra, Google messenger, hangouts and one called yaati or something.
All failed for me.
ender89 said:
Update: I decided to flash the firmware suggested in the top post, and updated supersu at the same time. Now its stuck on a boot animation loop apparently. I call this progress, because if I call it anything else I might just break down and cry. I'm preparing myself mentally for the inevitable full wipe I most likely face.
Click to expand...
Click to collapse
You have to first change SELinux to permissive, then flash super su.
I didn't see it mentioned as a bug so it might be a new policy for CM but does the advanced reboot option in dev settings always revert to unchecked after reboot?
---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------
a65lopez said:
Anybody using our tried sending mms? If it worked, then how?
The messaging apps I tried are : stock, textra, Google messenger, hangouts and one called yaati or something.
All failed for me.
Click to expand...
Click to collapse
I just sent a picture to test and it went through just fine, my phone was connected to Wi-Fi as well so it actually did the Wi-Fi to data handoff pretty quickly. This was using the stock messaging app.
Joshndroid's UNOFFICIAL CM13.0 BUILDS
DISCLAIMER
Code:
/*
* 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. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.
so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)
New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid
Thanks you for the ROM!
This is This is stable or beta or testing? Thanks
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....
Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.
yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...
New build 18032016 is up on basketbuild and Google shares
Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.
drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF
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
Code:
/*
** 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.
**
**/
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
IMPORTANT INFORMATION
Root is not included by default on LineageOS 14.1. You need to install an add-on via recovery. You only need to install this once. You can download the SU add-on here
After installation go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
LineageOS comes with LineageOS Recovery by default, if you don't like it (like me ) you can flash alternative recoveries using IsoRec. You really need 1GB /system partition. The smallest build-configuration is larger than 512mb. You can use ODIN, but you can also use Lanchon's REPIT.
If you're interested in BLN, check this thread for a complete support of this feature.
If you're interested to go to emulated-storage, check this thread.
Official LineageOS Wiki: http://wiki.lineageos.org/
Changelog: https://www.lineageoslog.com/14.1/i9100
LineageOS official nightly builds
https://download.lineageos.org/i9100
Google Apps:
http://opengapps.org/
XDA:DevDB Information
Lineage OS 14.1, ROM for the Samsung Galaxy S II
Contributors
rINanDO, lysergic acid, serenitys
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-02-13
Last Updated 2017-04-20
Reserved
gapps link dead
[i9100] Useful fixes for LineageOS 14.1 [7.1.2]
[i9100] Useful fixes for LineageOS 14.1 [7.1.2]
I am very glad that you are here!
It may be helpful to you:
Scripts moved here ...
BatyuS said:
gapps link dead
Click to expand...
Click to collapse
I think ist is just a mistake and should mean "open gapps"
http://opengapps.org/
Sent from my ME173X using XDA-Developers Legacy app
In General forum? Why not in Original Android Development?
Which GApps exactly?
Just to prevent from questions like "which GApps architecture and version do I need?"
This link will show you the minimal OpenGapps variant independently of your last visits (cookies never forget you)
http://opengapps.org/?download=false&arch=arm&api=7.1&variant=pico
(so only the variant needs to be changed if you prefer bigger packages)
Edit: Check this post to see how to create a customizable config that allows you to control the OpenGApps installer, e.g. to downsize bigger GApps packages for flashing Pixel Launcher while skipping other components you don't want. Included a sample config-file there as well.
I have questions:
FM Radio?
upgrade of CM 13?
TWRP emuled storage installation and new repit procedure?
from cm-13.0-20161218-nightly to lineageOS 14.1
shkedov said:
In General forum? Why not in Original Android Development?
Click to expand...
Click to collapse
Hi everyone, I am a low-average level user so I wonder if there is a step-by-step guide to upgrade my I9100-international from cm13 to lineageOS 14.1
bepcan said:
Hi everyone, I am a low-average level user so I wonder if there is a step-by-step guide to upgrade my I9100-international from cm13 to lineageOS 14.1
Click to expand...
Click to collapse
Only if you're coming from cm13 without losing data (i.e. your apps installed). Otherwise - wipe clean and install the recent nightly only (and gapps if you wish).
-3. Get a good cup of coffee.
-2. You must have at least 1GB partition of /system. If not, first repartition your storage (see OP) and then come back to here to proceed.
-1. Proceed to oficial download site: "https://download.lineageos.org/i9100 for the current build, https://www.androidfilehost.com/?w=files&flid=154035 for the experimental build, thanks to @ale5000 for uploading this for us.
0. Download the latest 2 following files: Nightly and Experimental (as for now lineage-14.1-20170208-experimental-i9100-signed.zip and lineage-14.1-20170208-nightly-i9100-signed.zip). Verify their md5 checksum to prevent errors, it is vital to do so.
Optional - download gapps from [url]http://opengapps.org/[/URL] for android 7.1, ARM (the nano is fine for me).
1. Boot into recovery. Install the "experimental" zip (Dirty flash! No wipes!).
1.5. You can reboot now into system, just to get a systemUI crash errors and a blank screen. Pretty useless. If you got to here then force reboot to recovery and proceed to step 2.
2. Reboot into recovery! Install the "Nightly" zip and gapps.
3. Wipe cache and boot to system.
There you go kiddo'.
Good luck! :fingers-crossed:
Whats Working Nd Not Working Tell Pls
rowdykumar786 said:
Whats Working Nd Not Working Tell Pls
Click to expand...
Click to collapse
It is relatively very stable to me, most is working! Phone and RIL, audio, GPS, BT, and a lot more!
I believe battery has improved too. Performance is very well.
This is my only phone, I rely on this phone, and on my daily use no problems so far! And yeah this ROM rocks!:good:
Go for it dude!
I experience a problem with libUMP making my own build. Is this : https://forum.xda-developers.com/showthread.php?p=69920779 still a working solution?
Verstuurd vanaf mijn GT-P7500 met Tapatalk
shkedov said:
Without losing data (i.e. your apps installed).
-3. Get a good cup of coffee.
-2. You must have at least 1GB partition of /system. If not, first repartition your storage (see OP) and then come back to here to proceed.
-1. Go to https://download.lineageos.org/i9100.
0. Download the latest 2 following files: Nightly and Experimental (as for now lineage-14.1-20170208-experimental-i9100-signed.zip and lineage-14.1-20170208-nightly-i9100-signed.zip). Verify their md5 checksum to prevent errors, it is vital to do so.
Optional - download gapps from http://opengapps.org/ for android 7.1, ARM (the nano is fine for me).
1. Boot into recovery. Install the "experimental" zip (Dirty flash! No wipes!).
1.5. You can reboot now into system, just to get a systemUI crash errors and a blank screen. Pretty useless. If you got to here then force reboot to recovery and proceed to step 2.
2. Reboot into recovery! Install the "Nightly" zip and gapps.
3. Wipe cache and boot to system.
There you go kiddo'.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
Do you don't include TWRP emu 3.03 https://forum.xda-developers.com/showpost.php?p=71009597&postcount=88 Interesting
Yes I would like to know upgrade path to official using twrp3.0.3 for emulated storage too please
todonormal said:
Do you don't include TWRP emu 3.03 https://forum.xda-developers.com/showpost.php?p=71009597&postcount=88 Interesting
Click to expand...
Click to collapse
People asked for a simple migrating guide from CM13 to LOS14.1, if someone isn't heading to switch to emulated I don't see a reason to send people to install an emu-recovery while they don't wish to.
It should be a decision for users.
Therefore I don't see a reason to include special addtional options besides the basics (exp+nightly+gapps). Whoever wants to expand more should simply read the OP and the links.
As for myself yes, I'm on emu now.
shkedov said:
People asked for a simple migrating guide from CM13 to LOS14.1, if someone isn't heading to switch to emulated I don't see a reason to send people to install an emu-recovery while they don't wish to.
It should be a decision for users.
Therefore I don't see a reason to include special addtional options besides the basics (exp+nightly+gapps). Whoever wants to expand more should simply read the OP and the links.
As for myself yes, I'm on emu now.
Click to expand...
Click to collapse
Could we have a short video to show how to switch to emulated storage?
Regards.
New build lineage-14.1-20170213-nightly-i9100-signed.zip is up
https://www.lineageoslog.com/14.1/i9100
laptopu said:
Yes I would like to know upgrade path to official using twrp3.0.3 for emulated storage too please
Click to expand...
Click to collapse
Hmm, because this phone is my main and only phone, I won't be able to test that soon (reverting recovery and ROM to cm13, reverting repartitioning too, then starting to trial and error).
But I believe that the safest way is to start from the moving to LOS14.1 - flashing the experimental and nightly first, as I guided. Then later flash emu-twrp recovery and proceed with rINanDO's instructions.
I'm afraid doing opposite (emu'ing first and then flash exp+nightly) might not work since Lanchon and the guys warned us that this emu-kernel might not work even with cm13 and maybe even affect it! Maybe repiting manually with Lanchon's magic REPIT would do, then migrate ROM, then change to new emu-recovery.
PLEASE:
- don't direct-link to recoveries that will brick your phone if installed too early.
- read the linked threads in the opening posts to understand the complexity of any of the changes
- if understood the consequences and you still want to do them all at once: know your limits
- if still feeling comfortable until here: go ahead *but do it in the correct order* or your phone will bootloop as all the newer test-recoveries were built with a Nougat ramdrive and thus will very very likely bootloop on your phone if installed on non-Nougat ROMs!
So my advice for your own safety: stay in your lane and read everything first.
EDIT: And by the way: please keep emulated storage discussions in the appropriate thread until it is officially tested and documented to be kind of noob-proof.