[Q&A] [ROM][Unofficial] CM12 / CyanogenMod 12 (pollux/pollux_windy) - updated JAN 19
Q&A for [ROM][Unofficial] CM12 / CyanogenMod 12 (pollux/pollux_windy) - updated JAN 19
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][Unofficial] CM12 / CyanogenMod 12 (pollux/pollux_windy) - updated JAN 19. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Found bugs/defects:
1. There is no way to take a screenshot. Volume down + Power not working, must not add screenshot button on power menu, or on long tap to home button.
2. Quick setting panel setup contains bug: if you want configure tile, you need to tap left of tile. Also, quick settings contains very few settings.
Also, most features of CM missing. Probably because of this ROM is so stable?
Screenshot capturing works for me just fine.. But i can confirmm quick titles bug.
Sent from my LG-D802 using XDA Free mobile app
31.01.2015
AudioFX config has no effect on Speaker !
IR Transmitter seems to do nothing
BenniG said:
Screenshot capturing works for me just fine.
Click to expand...
Click to collapse
How you do it?
I was nosy and looked for the moment when the nighties will start...
http://review.cyanogenmod.org/#/q/o...uer+%3Cgeorg.veichtlbauer%40gmail.com%3E",n,z
http://review.cyanogenmod.org/#/c/87613/
What is Projekt Hudson ?
thanks great rom
but i cant install any custom recovery just cm recovery boots .
and how can i use this rom in multirom ??
one other question : how can i move my stock sony rom into secondy rom . i m tried swap rom in the multi rom in TWRP but it doesnt works .
thanks
sorry for my BAD ENG
Guys, what is this icon?
Mr.Beetle said:
Guys, what is this icon?
Click to expand...
Click to collapse
No interruption. See https://support.google.com/nexus/answer/6111295?hl=en
I have installed the latest "cm-12-20150217-UNOFFICIAL-pollux_windy."
As much as I love the Android L rom, I might need to go back to cm-11 roms. This is because the latest "Folder mount 2.7.1" is not working well with Android L in Tablet Z WIfi.
Also, the inbuilt "move to sd" under settings/apps is not working well yet.
I hope developers of "Folder mount" can fix their application to run on Android L soon.
Going back to cm-11 when qsnc has cooked such a nice cm-12 ROM for Tablet Z WIFI is really a hard decision to make.
Does anyone know why in cm-12 , changing application datas to external microsd is not working? Or is it just me?
Under /settings>apps> Move to external sd ------> error message : not enough storage space ?? (My microsd is 16gb class10 and has more than 10gb free space.)
Also, has anyone tried using "foldermount 2.7.1?" It is not possible to pair from internal emulated storage link to external microsd. Any way to solve this issue?
Thanks
Foldermount works fine on March 1st release
cantenna
Thanks for the good news. I have actually went back to cm-11. I've also tried to notify the developer of 'folder mount' by leaving a feedback in Google play apps store. But it looks like "qsnc" did a great job with cm-12 for our lovely polux windy (Xperia Tablet Z sgp311 wifi).
It's time for me to flash cm-12 again.
Unfortunately, I have not been able to get folder mount to work properly in latest cm-12 march.
Folder mount can move files from internal sdcard to external sdcard1 (microsd) but when I click to mount the icon doesn't turn green which means it fails to mount and bind the paired folders.
I have some luck with directory bind application but still not working as well as I hope. As long as I don't umount sdcard1, the binding can be maintained. Unfortunately, the binding can be lost randomly.
I really prefer to have application's data go to my microsd because if I happen to erase all files in my internal data partitions, the data's in my microsd will still be safe and can easily be restored. In the worst scenario , if the tablet for some reasons cannot turn on, my datas on microsd will still be safe and I can insert the microsd into PC for backup or into insert into a new android device to continue work.
Cm-12 is really nice but because folder mount is not working well yet, I have to make a hard decision as to whether to use cm-11 for now. I miss archos 70 days when it was possible to swap the micro SD with the internal emulated sdcard. No need for any applications.
There is a script
by tanjung269 for xperia v to swap the microsd and the internal emulated sdcard1.
http://forum.xda-developers.com/showthread.php?t=2466590
Maybe someone can modify the script for xperia tablet z?
cphilip said:
Maybe someone can modify the script for xperia tablet z?
Click to expand...
Click to collapse
there are xposed modules with similar functional.
Rootk1t said:
there are xposed modules with similar functional.
Click to expand...
Click to collapse
Thanks for introducing me to xposed modules.
I've never used xposed before and I am really new to the world of xposed framework.
I did some reading. Tried the latest xposed for lollipop but unfortunately didn't work with cm-12.
I decided to go back to cm-11 and install xposed framework with the "xinternalsd" module.
I must say i am very surprised indeed. it worked beautifully. My micro SD became the data partition where apps store their data's. Wow! This, to me is a better solution than foldermount although folder mount is still a very good application. Before this, I was kind of intimidated by this new thing called "xposed framework." Sure, I heard about it all over the forum and even on apps like greenify but I thought it was too advance in android hacking for me to figure out how to use it. Thank God, the developer has made it so easy to install.
Thanks Rootk1t once again for getting me interested in xposed. I hope that the developer will make xposed usable for lollipop soon. But for now, I think I can live with cm-11 and xposed!
Foldermount and Xposed works perfectly fine on this ROM CM12 March 1st release, I have in my tablet an ext 128g SanDisk card. I don't know why you are having problems but try what I did, after you install ROM (march 1st release) install SuperSu binary via recovery search it via google and XDA, then make sure you you flash this zip by danaff37 via recovery found
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118/page324
** PAGE 324, be sure you flash "On another device try this"**
its loosely found by browsing the q&a thread for Xposed, but its an awesome tweak that sets the kernel to permissive early on pre boot instead of post boot, this zip is also key to making Xposed alpha fully functional on lollipop. I suspect foldermount may not be working for you because selinux is not set to permissive but is more likely due to not having SuperSU installed. You may also have to format internal storage as a last resort if all else fails but probably not. I did format internal storage because I wanted to take advantage of f2fs, but anyways I have foldermount working perfectly on both my GS4 and my Pollux windy both devices f2fs, lollipop, both devices have sandisk micro SD 128g, 100+ games
Oh, most important of all, you need to install twrp via fota, instructions are in the main thread how and on twrp website on how to do this via terminal. You need to do this to flash zips via recovery
cantenna,
Thanks for the sharing.
I tried to download March 1 cm_12 from cyanogen download website but unfortunately, the rom is no longer available.
I didn't know that I had to install SuperSu because I usually enable cyanogen built-in SU in the developer settings.
Although, cm-11 with xposed framework with xinternalsd module works ok for me, out of curiousity, I wanted to see if folder mount worked in the march 1 cm-12 rom. The last 2 cm-12 rom that i used was the March 8 and a later version Foldermount didn't work in those nightlies. Of course, the other thing is, I didn't install SuperSU because I relied on the built in su that is usually provided by cyanogen roms.
I also tried to install xposed in another device, the xperia V using the latest cm-12. Unfortunately, even after using the patch for the link you provided to make selinux permissive, xposed failed to flash using cwm recovery loader or TWRP loader. It is reported that the current xposed for lollipop will work only in Android 5.0 and not in Android 5.02. i wonder if the March 1st cm-12 rom is Android 5.0. If I could download that march 1st cm12 rom, I might just give Xposed a try. Then again, I am not sure if the xinternalsd module will work in lollipop or not.
The xinternalsd xposed module is good enough for me at the moment although I did notice that some apps still managed to send their datas to the device emulated SDCARD instead of my microsd. I don't know why.
For this reason, I am still interested if there is some way to tweak the vold.fstab file to get a proper swap between the device emulated sdcard and the external microsd.
I just checked the march 1st version of the ROM is indeed 5.02. Let me know of you want me to send you a copy of the ROM, its still in my downloads folder, send me a pm.
Why pollux-windy uses source-code for telephone functions ?
http://review.cyanogenmod.org/#/q/s...ackages_services_Telephony+branch:cm-12.0,n,z
Allways in changlog for windy ?!
Related
Q&A for CM 12 (L - Lollipop) for Nook Tablet (acclaim)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CM 12 (L - Lollipop) for Nook Tablet (acclaim). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CM12 on Nook Tablet
I downloaded your build and recovery last night. It installed without issues. I then installed PA Gapps Micro 5.0.1 (1/31 build). The system partition is at 91% with the micro Gapps. The only issue I have encountered so far is Titanium backup cannot get root access. I'll figure that one out so I can restore some of my apps.
Thanks and great work!
Nook Tablet with Lollipop, but no root
Hello,
I have nook tablet 16GB and rooted and installed Liquid Smooth 4.4.4 and CM10. It worked fine, but only problem was, it was saving file and everything to external sdcard. Internal memory wasn't gettign used.
Today, I installed CM12 and updated the system to Lollipop from the following forum.
http://forum.xda-developers.com/nook-tablet/development/cm-12-l-lollipo-nook-tablet-acclaim-t3019125
It initially gave errors on Launcher3, I cleared the cache and cleared data and forced closed. in few minutes the launcher started worked fine.
Now, I went to Titanium backup to try restoring and to my surprize there is no 'Root' access. Did this ROM has no root access?
Please help.
supersu ...
had to flash supersu in recovery (file below)...love this rom!! thanks
supersu ...
mastermind_24 said:
Hello,
I have nook tablet 16GB and rooted and installed Liquid Smooth 4.4.4 and CM10. It worked fine, but only problem was, it was saving file and everything to external sdcard. Internal memory wasn't gettign used.
Today, I installed CM12 and updated the system to Lollipop from the following forum.
http://forum.xda-developers.com/nook-tablet/development/cm-12-l-lollipo-nook-tablet-acclaim-t3019125
It initially gave errors on Launcher3, I cleared the cache and cleared data and forced closed. in few minutes the launcher started worked fine.
Now, I went to Titanium backup to try restoring and to my surprize there is no 'Root' access. Did this ROM has no root access?
Please help.
Click to expand...
Click to collapse
.......................
supersu ...
had to flash supersu in recovery (file below)...love this rom!! thanks
confirmation of Developer Options setting bug on official nightly
I did send a bug report... For me, developer options were working properly on unofficial.
Thanks to everyone for CM-12 on tablet.
USB host
Did this ROM support USB host for OTG, or any ROM support it???
Contribute/Issues
Are your github acclaim repos the best place to contribute, open issues, etc.?
Feb. 9th nightly
I have the latest recovery installed with the Feb 9th nightly. I can now reboot to recovery from the power-off menu. Yea!
I did have initial problems with the Feb. 9 nightly, I seem to have wiped out my gapps when I initially installed it (which I had to do manually). Clearing the cache and reflashing the Feb. 9th update and gapps fixed everything.
CM12 Rocks
I installed CM12 last night. I have the occasional hang->reboot, and there are some sluggish times but on the whole it's pretty sweet. I'm using my chromecast with netflix from the nook. For some reason CM11 with netflix wouldn't let me chromecast... not sure why but oh well.
My question is: when I hit the "settings" menu and tap the "buttons" option it causes the settings menu to crash with an "Unfortunately settings has stopped". Is this expected? I thought maybe it was because I originally tried a dirty-flash so I tried a factory-reset and wipe cache and then installed but the crash still occurs.
Thanks,
-Greg
too slow to respond
My NT is very very slow after install lastest CM12 (via OTA update) and about 10 apps, It spend 5-10s to open an app. Eventhough, turn off the screen also spend 2 seconds.
I can confirm that happens for me on the Feb. 9th build also. I did submit the bug report.
Just updated to Feb 11 nightly using cmupdater. Updated with no problem EXCEPT AOSP keyboard keeps quitting and lost gapps again. (pa_gapps-modular-micro-5.0.1-RC3-20150201-signed.zip) Reinstalled gapps. Note that "buttons" in setting still causes setting to close. I can't seem to view the recovery log through recovery (I see a few words of sup small tiny tiny type) and am not sure where it lives on the system. Does anyone have any ideas about why this is happening (loss of gapps) ? Could someone let me know where to find the recovery log?
thnx
mastermind_24 said:
Hello,
I have nook tablet 16GB and rooted and installed Liquid Smooth 4.4.4 and CM10. It worked fine, but only problem was, it was saving file and everything to external sdcard. Internal memory wasn't gettign used.
Click to expand...
Click to collapse
I also had/have this issue.
Now, I went to Titanium backup to try restoring and to my surprize there is no 'Root' access. Did this ROM has no root access?
Click to expand...
Click to collapse
According to this post in the dev thread, you can enable root in Settings/Developer Options. Attempting to open Developer Options causes Settings to crash here, currently.
You could flash SuperSU in the meantime
Additional Permission Problem?
belfastraven said:
Just updated to Feb 11 nightly using cmupdater. Updated with no problem EXCEPT AOSP keyboard keeps quitting and lost gapps again. (pa_gapps-modular-micro-5.0.1-RC3-20150201-signed.zip) Reinstalled gapps. Note that "buttons" in setting still causes setting to close. I can't seem to view the recovery log through recovery (I see a few words of sup small tiny tiny type) and am not sure where it lives on the system. Does anyone have any ideas about why this is happening (loss of gapps) ? Could someone let me know where to find the recovery log?
thnx
Click to expand...
Click to collapse
Found the recovery log--
Obviously the backup of gapp apps that is done during recovery failed--
e.g.
grep: /tmp/gapps.prop: No such file or directory
mkdir: can't create directory '/sdcard/tmp-gapps//': Permission denied
cp: can't create '/sdcard/tmp-gapps//system/app/GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk': No such file or directory
mkdir: can't create directory '/sdcard/tmp-gapps//': Permission denied
cp: can't create '/sdcard/tmp-gapps//system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk': No such file or directory
mkdir: can't create directory '/sdcard/tmp-gapps//': Permission denied
cp: can't create '/sdcard/tmp-gapps//system/app/GoogleHome/GoogleHome.apk': No such file or directory
mkdir: can't create directory '/sdcard/tmp-gapps//': Permission denied
etc.
Could this be an issue with the recovery mg itself? I can install gapps with flashify with no problem.
---------- Post added at 03:33 PM ---------- Previous post was at 03:09 PM ----------
I just noticed in the recovery log where gapps was not recovered:
persist.sys.root_access=0
Shouldn't it be persist.sys.root_access=3?
How I can install ADB driver for Nook Tablet?
belfastraven said:
Found the recovery log--
Obviously the backup of gapp apps that is done during recovery failed--
I reflashed TWRP 2.8.4.0 and then used cm updater to update to Feb. 12th official nightly. Updated automatically and didn't lose gapps.
For me, the closing of setting on trying to use developer settings was fixed 2 or 3 roms ago. I don't have titanium backup installed so don't know whether that will work now.
"buttons" still causes settings to close.
Click to expand...
Click to collapse
AlexBreems said:
How I can install ADB driver for Nook Tablet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994129
At the bottom of that post you will find a zip with the drivers. Using the posters suggestion I have found it much easier to use a wireless app (WIFI ADB in my case) then installing the windows drivers on my Windows 10 tech preview..
Hope this helps.
What's the issue with needing a new recovery? I flashed successfully using CWM 6.0.4.8 and the full sized GApps, and found virtually no errors, and barely any sluggishness.
recovery question
jay_xander said:
What's the issue with needing a new recovery? I flashed successfully using CWM 6.0.4.8 and the full sized GApps, and found virtually no errors, and barely any sluggishness.
Click to expand...
Click to collapse
When I flashed with the OP's latest recommended recovery (I think 6.0.5.1) I lost gapps twice. Didn't happen before that. Earlier than feb. 9th nightly, I could not get into recovery from shutdown menu and CMupdater couldn't get into recovery. (I updated manually). Now with twrp 2.8.4.0. everything is working "automatically" for me.
I find tablet to be pretty responsive, too. Hitting "buttons" in setting still closes settings (not something I use, but was just testing)
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!
Since Android 6.0, we have the option to adopt microSD storage as internal storage, the so called Adoptable Storage. It gives you the benefit of being able to install apps on it natively.
Many OEMs have disabled the functionality in their firmware builds, including Sony.
It seems that their disabling has not actually removed the functionality from Android, but just hidden the controls to it. Recently, several attempts to restore the functionality have been made successfully. I just came across one done by MoDaCo on the Samsung Galaxy S7.
Can someone o the Z4 Tablet MM firmware try this out? It seems to be pretty easy and done using ADB. Might be interesting for some.
If no one else has I might give it a try later I don't really need it but just for research reasons really. I have a lot of apps but I really don't need the extra internal
Sent from my Xperia™ Z5 using Tapatalk
it gets a bit weird... but I like the convenience
I have enabled it on my Marshmallow (CM13) SAMSUNG Galaxy S5.
I find it quite useful when dealing with my space eaters like OSMand and my mp3-collection and especially seafile.
I could not get the latter to store its downloaded contents on my 64GBytes card. Now I do not care anymore.
BUT:
There is some behind the scenes magic going on.
TWRP 3.0 sees the filesystem quite differently than you will see it under Marshmallow even with a root enabled file manager. Maybe it needs an update for these merged partitions.
example:
DL a new nightly with cmupdater and tell it to update the ROM -> TWRP boots and does not find the nightly.zip.
No big deal you think, just open the file manager of TWRP and find/move the file from /sdcard/cmupdater
surprise: /sdcard/... is not accessible or it does not contain the files you have just seen under Marshmallow.
My workaround: move the nightly.zip with a filemanager to /data, then boot into TWRP and install from /data
Was dissapointed to see that it was disabled, seeing as i have a 128 gb micro sd card installed I'm not qualified to fix this at all, but i hope there are some legends out there that can
andy0208 said:
Was dissapointed to see that it was disabled, seeing as i have a 128 gb micro sd card installed I'm not qualified to fix this at all, but i hope there are some legends out there that can
Click to expand...
Click to collapse
One of those being @AndroPlus He just released an update to his Xposed module SystemUI Patcher for Lollipop (that could use a name-change) adding support for it:
WHAT'S NEW
Added option to enable adoptable storage on Android 6.0 Marshmallow
Click to expand...
Click to collapse
jelbo said:
One of those being @AndroPlus He just released an update to his Xposed module SystemUI Patcher for Lollipop (that could use a name-change) adding support for it:
Click to expand...
Click to collapse
Nice! I'm not sure i am all for rooting the device though, but it is nice to know that there are solutions.
Just tried on my z4 tablet and works fine. I had to however force adoptable for it to work. using 32GB with ration of 30%. Just finished migrating and everything seems fine.
Official CM13 ROM, by Nikita Pro Android is availabe here:
http://forum.xda-developers.com/g2-mini/development/cyanogenmod-13-0-lg-g2-mini-t3260495
Preamble
Why am I doing this guide?
The main, developer's post has about 100 posts and it's really annoying to find useful information in this mess... The same questions appear all the time (I also had to ask them again). I decided to gather the important things in one place. Besides - ROM is quite unique and differs from others. If I wrote something wrong, tell me, I'll fix it. Sorry for my not perfect English.
I will look at the whole case as a simple user (who I really am! lol).
Stability
It is a subjective topic, so please take it with a pinch o salt. If I would have to rate the stability it will be 4 out of 6 (where 1 is a bricked phone and 6 is the flawless system work). System apps (like Documents or Themes) rarely can crash, but the system reboot fixes it. Generally every day usage is completely fine and you'll never get a random reboot on the go. What users have been reporting are problems with crashing default music player (confirmed by me). I personally noticed, that while using ProPlayer (IMO one of the best music players) songs rarely are randomly muted or skipped. Another thing reported is a signal losing (I haven't experienced it). GPS for me is going like crazy.
Storage mysteries
I don't know, if it's a bug or a feature, but there have been done serious changes to storages' permissions. It's probably an effect of allowing convertion of external SD Card, to internal memory. But let us start from the begginig...
When you'll first boot to the system, you will be asked, if you want to keep your SD Card memory as mass storage device or if you want to format it as internal memory.
1. If you won't format
Apps will be only able to use the internal memory. They will have no permissions to change anything or write to SD Card. It means, that you won't be able to download files to it or even manage it with file manager (even if it will have root permissions!).
You will be able to access internal and external memories from TWRP.
2. If you will format
You won't have access to old internal memory from system (practically it will disapeare), but instead you will gain full access to your SD Card.
Internal and external memories will be still available through TWRP.
Remember to make a backup to your PC, before formatting ;P
TWRP
You will have to flash TWRP 3.0.0 to get full access to SD Card after formatting.
http://forum.xda-developers.com/g2-mini/development/unified-twrp-recovery-3-0-0-lg-g2-mini-t3311316
Super SU
If for some reasons you don't want to use build-in root (for example I really don't like this hash sign on the statusbar), here's what you do:
1. Turn OFF build-in root in Developer Settings (if you don't, you'll get bootloop)
2. Flash Super SU through TWRP with the flashable ZIP from the Official thread (don't use Super SU App for this!) http://forum.xda-developers.com/showthread.php?t=1538053
3. When you boot to system, Super SU with root will be ready.
4. Reboot again to fix the Super SU app (it can crash)
XPosed
XPosed works with official version for SDK 23 arm.
http://forum.xda-developers.com/showthread.php?t=3034811
SELinux
If you want to change it from enforced to permissive, look here
http://forum.xda-developers.com/g2-mini/general/guide-how-to-set-selinux-to-permissive-t3329439
Release information
ROM is being developed on two channels: Nightlies with everyday (beta) updates, and with Release channel (with more stable versions).
Changelog can be found here http://www.cmxlog.com/13/g2m/
If you want to change channel from Nightly to Release - here's the official information what to do:
Update scenario 3: CM 13.0 nightly user
Update steps: Stop. Step away from the phone. Do not flash these builds, you are already on a newer codebase (Android 6.0.1_r22). Attempting to flash these release builds will result in crashes due to attempted database downgrades. Don’t do it.
If you want to swap off nightlies and stick to our release channel, you will have to wipe to take these builds.
Click to expand...
Click to collapse
Source: http://www.cyanogenmod.org/blog/cm-13-0-release-1
Download page: http://download.cyanogenmod.org/?device=g2m
Rest of the information is in the main Nikita's post.
PS
If you think I skipped something important, tell me...
XDA:DevDB Information
[ROM][7.1.1][Unofficially | LineageOS 14.1 For Huawei Ascend G760], ROM for the Huawei Ascend G7
very very thanks for:
dianlujitao
desalesouche
and others
Contributors
mparus
ROM OS Version: 7.x Nougat
Manifest: https://github.com/mparus/g760_lineageos-14.1
Downloads: https://forum.xda-developers.com/devdb/project/?id=19186#downloads
Mirror: https://androidfilehost.com/user/?w=settings-dev-files&flid=118309
Latest:
Check downloads page.
Previous: https://forum.xda-developers.com/devdb/project/dl/?id=23171 fix wifi reboot problem, fix move to sdcard apps problem, latest LOS commits
https://forum.xda-developers.com/devdb/project/dl/?id=23097 remove Gello browser - more space on /system partition, latest LOS commits, some wifi modifications
https://forum.xda-developers.com/devdb/project/dl/?id=23064 edit2: Please test the rom, maybe my tests were wrong
edit: this build is bad, random reboots often
disable CMUpdate app, update prima wifi driver in kernel (maybe fix random reboot after enable/disable airplane mode), latest LOS updates, please delete /data/misc/wifi/WCNSS_qcom_cfg.ini and /data/misc/wifi/WCNSS_qcom_wlan_cal.bin files or clean install recommended
https://forum.xda-developers.com/devdb/project/dl/?id=22978 fix restart to recovery and bootloader, latest commit from LineageOS
https://forum.xda-developers.com/devdb/project/dl/?id=22956
for root use: https://download.lineageos.org/extras (arm version)
stable twrp: https://www.androidfilehost.com/?fid=24421527759884484
new beta twrp: https://www.androidfilehost.com/?fid=529152257862699744
small google apps: https://github.com/opengapps/opengapps/wiki/Pico-Package
Issues: no gyroscope and USB otg
Version Information
Status: Stable
Created 2017-02-01
Last Updated 2018-02-18
Reserved
Having just issue with gyroscope not working properly so far everything else all good can't use file manager as won't let me access SD card so use root browser and no problem whatsoever
Thank you for your work!
So to continue from the other thread.
Seems large apps can't be moved, while small apps can.
I have 30gb free on the sdcard, but Final Fantasy 7 or 9 can't be moved there, giving the error "insufficient storage". However big files can be moved between location manually.
(Final Fantasy 7 doesn't run at all, and just instantly crashes when open. That game was always sensitive to where it was stored. It did work on your cm13, but not very well, its a bad port of the pc version I think
*Edit that, updated just got pushed by play store. What's changed state it doesn't work in 7.x Android).
Again, I am providing feedback as things happen. Not particularly asking for a solution, although maybe anything I come across can indicate issues to help with development.
Ooh another thing. In the expanded notification panel, pressing the pencil icon in order to rearrange the icon causes the phone to freeze for a minute or two, then brings up the lockscreen. Seems like SystemUI having issues but there is no error messages indicating that (but its that kind of behaviour from older Android versions that makes it seem like the case). It does not happen every time, but happens more than actually opening the rearrange page happens.
Sent from my Huawei Ascend G7 using XDA Labs
@mparus
Please always keep the first post up to date with the link for Latest Stable ROM, Latest Nightly ROM, Known Issues, Latest Recovery, Latest Kernel, etc.
Previous topic was not suitable for a new member or even an old member that didn't follow the topic for couple of days.
SD card working perfect on my G7-L01 in the 131 build.
Everything (so far) works great. Great ROM ?
Does anybody have mtp connection problem on latest build lieage rom ??
wish gapp i have to install ? lineage gapp or whatever??
Sent from my HUAWEI G760-L01 using Tapatalk
Sparko612 said:
Does anybody have mtp connection problem on latest build lieage rom ??
Click to expand...
Click to collapse
I got no problems (SD card not formatted as internal).
Although in some earlier builds when I formatted the SD card as internal storage I couldn't access internal memory from my PC.
So specify your problem a bit please?
NAJI23 said:
wish gapp i have to install ? lineage gapp or whatever??
Sent from my HUAWEI G760-L01 using Tapatalk
Click to expand...
Click to collapse
GApps 7.1 Arm.
NAJI23 said:
wish gapp i have to install ? lineage gapp or whatever??
Click to expand...
Click to collapse
Install 7.1 GAPPS on the ARM platform.
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Sparko612 said:
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Click to expand...
Click to collapse
Plug your phone to your PC. Then when it connects to the PC you'll have to open your status bar and see a notification saying "USB Charging this device". Click on it and you'll get a small menu with 4 options. Click on " Transfer files" (which is the second option) and then your phone will reconnect with your PC automatically and you'll be able to access the internal and SD card data from your PC.
And a feature has been added to Android ever since the 6.0 version where the users can configure the SD card to be able use it as Internal Storage. You can find that in the settings of your device?
Sparko612 said:
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Click to expand...
Click to collapse
This is the notification
kamilb365 said:
This is the notification
Click to expand...
Click to collapse
Yes I get the notification but when I select transfer files nothing comes up and don't really know what else to do
How about lis3dh sensor devices? - working properly or have problems with gryro or screen rotation?
Sparko612 said:
Yes I get the notification but when I select transfer files nothing comes up and don't really know what else to do
Click to expand...
Click to collapse
Well what build are you running right now?
And did you clean or dirty install it?
kamilb365 said:
Well what build are you running right now?
And did you clean or dirty install it?
Click to expand...
Click to collapse
Clean install on latest lineage ROM build 131
Sparko612 said:
Clean install on latest lineage ROM build 131
Click to expand...
Click to collapse
This might be able to fix it. Go to developer options, scroll down to "select USB configuration" and change whatever setting you have to MTP. You might wanna switch modes a few times and then connect to PC with MTP active..
The bug has been active since cm13 in some cases and I personally never had the issue so I can't go into full depth of this.
kamilb365 said:
This might be able to fix it. Go to developer options, scroll down to "select USB configuration" and change whatever setting you have to MTP. You might wanna switch modes a few times and then connect to PC with MTP active..
The bug has been active since cm13 in some cases and I personally never had the issue so I can't go into full depth of this.
Click to expand...
Click to collapse
Gonna re download it tomorrow might be bad download anyway ive restored back to stock for now will look into it thank you all your tips
Edit: my model of device is G7 - L01 not sure if that may be the problem why im getting all this atm