Related
Hi, not new to CM10.1 , loving it on my Nexus 4... but just flashed it on my newly bought Samsung Galaxy Note 10.1 GT-N8000 (nightlies 20/4) and I am having trouble with my WiFi, it doesnt seem to be able to connect to WiFi ...
After filling my WiFi password, it is stated there as "Connecting" and then, it becomes "Saved,secured with WPA PSK" instead of "Connected"
Found a number of similar posts but none actually worked for me, tried:
- Changing to Static
- Changing Wi-Fi region code
- Something about deleting a file in directory > data/misc/dhcp , but no file is to be found there
- Something about deleting /data/.cid.info , but again, there's no such file in my note 10,1
A screenshot for a more detailed explanation:
http://i806.photobucket.com/albums/yy341/XhaigeX/Screenshot_2013-04-21-20-11-49_zps7b0d2a5f.png
same problems on photon q
i am experiencing the same problems as you. i can only get it to work after a clean install of cm. And I mean clean. a few nightlies ago i could solve the issue with a permission fix thru rom manager.Skrillax put the rom together but i cant ask him because like you i am a junior. Hope a fix comes soon.
I was running CM 10 with some success on my P506 and decided to try CM 10.1. With all the "stable" versions (now on 10.1.3) I've had an issue with wifi -- specifically, I have to press the WPS button (after wifi is enabled) in order for it to connect to see that any access points are available. Until I do, it only shows APs I've previously connected to as "out of range." Is there something I can do to fix this? (When installing a new ROM, I wiped the caches and /system.)
I ended up getting around this problem. It seems like it was due to an old setting that was restored (through Google) on installation of the rom. I also noticed I was out of space on /system, so that might've been a related issue. I'm now running a trimmed nightly of 10.1.3 with gapps-light (did not restore my saved settings from Google) and do not have this issue any more.
Q&A for CyanogenMod 12.0 for Photon Q
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 CyanogenMod 12.0 for Photon Q. 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!
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
I really wanted to know that everybody has no problem at all in logging in Google+ with the latest version of its client.
I'm having trouble the most recent one that I can download from Play Store, : v5.1.0
I had to restore the backed up version of v5.0
I recently got the multimedia dock for this phone and I've noticed that some things don't work. None of the USB ports on the dock seem to interface with the OS, but any peripheral connected by a USB OTG cable (while not in the dock, of course) works just fine. Also, the device doesn't seem to detect that it is in a dock at all; I have it set to daydream when it's docked, but nothing happens.
Does anybody else have these issues? Is there a known or planned solution?
Thanks!
Hei just another quicky:
I had problems with twrp unable to mount /data on encrypted phone. I was never asked for passphrase also it did not detect data was formated as f2fs and assumed ext4.
After factory reset I reformated data and cache to f2fs again (as I think the performance gain is real) and cleanflashed latest cm12 nightly + gapps.
After setting up my phone it became slugish fast again, also battery did drain fast (also the phone did get real hot)
My circumvention so far is limiting Background processes to 2 within Dev options. Since then phone stays much cooler, everything works as expected normal cpu usage shows 2.5/3.2/3.5.
Before that phone was sometimes at 12/9/8 or so and thus bekame unresponsive/sluggish.
Does anyone know the standard count of background processes? Form Q?
Since i did not discover any strange behavior/lags since i switched to only 2 backgroundprocesses anyone knows what kind of usage could result in problems with lower backgroundprocesses?
Thanks in advance!
CM 12.0 nightlies I/O and issues
So I switched over to CM12 because of the ability to switch the filesystems to f2fs. And so far I have seen a pretty decent improvement in the response, speed, and general performance with CM12.
A few issues have come up though:
CM nightly 03232015
-the cLock widget just randomly stopped functioning. Worked for a day or two, then stopped working. I wasn't able to set the alarm and clicking on the time on the home screen does nothing. Disabled cLock and am using the default Deskclock instead (I need to be able to set alarms).
-the messaging app was not working correctly... I was able to receive texts but the send button was greyed out and would not let me click on it. This is both over Wi-Fi and 3G and 4G LTE. Had to revert to 8sms that I was using on CM10...
-the themes are applied inconsistently... not all apps or system dialogs are themed when I use ThemeDIY to create/apply my own theme.
-equalizer doesn't seem to make a big difference...
-doesn't seem to remember wifi logins... keep getting the "sign in to wireless network" notification (I've already signed in)... the sign in page does not open in Chrome, but rather a separate browser or system page that won't offer to save my password (though it does autofill the username)...
-weird issues using adb... even though I've authorized the computer, and have root access on the phone and am running adb root, it won't let me write to certain parts of the file system (I couldn't adb push bootanimation.zip /system/media/bootanimation.zip error was "read-only filesystem")
I know it's a nightly, just wanted to see if anyone else has these same issues and to make sure the developers are seeing this. For the record, I did a wipe and format (since I was going to change the file system,) and this is a clean install of both TWRP and CM12.
Thanks!
---------- Post added at 06:15 PM ---------- Previous post was at 05:58 PM ----------
breakerwaves said:
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
Click to expand...
Click to collapse
I didn't know what to use either so I left it on NV. Haven't noticed a difference in signal or call quality or anything. I am guessing since we're on Sprint and there is no SIM card that RUIM/SIM won't work?
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
kecksk0enig said:
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
Click to expand...
Click to collapse
I can't speak to the RUI/SIM issue but I don't know how to switch themes off. As far as my SMS and cLocks idk it is possible that I disabled the wrong app I don't like to run more then the bare minimum. As for the theme I ended up downloading a dark theme from the app store which is wonderful looking!! It is called Nicholas' Dark Material. In case you're looking for dark like me.
Do you have issues with the gallery or camera? I think I saw somewhere on the xt897 forum a link to motorola's camera and gallery apps... are you able to change the save location for pictures or no?
I also had an issue where the navigation bar does not render right when I watch full screen video in landscape mode. May have to do with me forcing GPU render under developer options. I'd take it off but I can't remember how I got there lol
---------- Post added at 11:27 PM ---------- Previous post was at 11:21 PM ----------
I cannot set the custom color for notifications in CM12... but there is a post that says the colors were retained on an upgrade from CM11. Well I wiped and did a clean install rather than an upgrade so is there an .xml file or a settings I can edit? I'm comfortable with file manager and editor and adb and shell...
CM 12 update
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
nasch007 said:
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
Click to expand...
Click to collapse
If you only apply the update, it will not wipe the device. You would have to wipe it manually in recovery. It will apply a so-called "dirty flash" as you are not wiping any partitions.
CM12-->CM12, should be fine. Of course before you report any issues try a clean flash (or if it's a single app FC'ing, try clearing data on that single app).
I'm having tons of trouble using this with Sprint.
When I lock it to CDMA and/or EVDO mode, Logcat shows that it's trying to connect using a C Spire APN. If I lock it in LTE-only mode and select Sprint APN, it gets a good data connection. The APN menu is foolishly disabled for CDMA/EVDO so I cannot correct the issue. Why is it trying C Spire? How can I fix 3g and MMS settings to work?
CM11 worked great in all conditions, and MMS worked out of the box.
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Alien987 said:
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Click to expand...
Click to collapse
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Alien987 said:
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Click to expand...
Click to collapse
Yes, that's the correct one.
The CM maintainer clearly states the reasoning in the CM12 thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Adjusting the meta-inf to check for "asanti" instead of "asanti_c" worked perfectly. Thanks for your help!
Now I have to find out why after I flash gapps I start to get multiple crashes related to Google Services and Google Apps.
Edit: Well, just in case someone face the same problem in the future. I updated to the latest TWRP recovery directly from their webpage (initially I used Rashr app) and that solved all my problems, including the initial error when flashing CM12 nightly.
Q&A for CyanogenMod 12.1 for Photon Q
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 CyanogenMod 12.1 for Photon Q. 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!
Boot stuck and Bootlooping -fix
Sweet merciful crap. I just got through a 5 hour fight with my Photon Q trying to bring it up to cm-12.1.
In a nutshell, I figured the advise not to dirty flash 12.1 on top of 12 was defunct once it started showing up in the nightlies. Be warned - it is not. Your experience may mirror mine and you'll get stuck at boot.
What's worse is that when I went into TWRP-2.8.6.0 recovery and attempted to do a wipe of data/cache, it started making a mess of my partitions. Not able to mount /data, not able to mount /cache... No matter what order, or selection in the Advanced wipe, it seemed to be making more and more of a brick out of my device as I tried.
I followed some advise I found that suggested newer TWRP versions had problems with wiping on the Photon Q, and to try CWM recovery or stock recovery. Tried CWM to wipe, no dice, similar problems. Spent a good deal of time trying to find the stock recovery somewhere; I think I reached the end of the internet and it's not there.
Then I started trying older versions of TWRP found here:
http://techerrata.com/browse/twrp2/asanti
Then things got really bad. Every one of the ones I tried with "asanti_c" in the name bootlooped (tried about 5 of them). The battery started getting low and I couldn't flash the recovery any more from the bootloader, and it would seem the phone won't take a charge while in bootloader mode. So I had to let it bootloop while it charged, which of course took a long time because all the bootlooping was keeping the battery taxed.
Finally I flashed this one, 'cause I figured my phone was a brick anyway:
openrecovery-twrp-2.2.2.2-asanti.img
It started up. It was also happy to restore/wipe my data, cache, and system partitions. Back to the bootloader, flash back to TWRP 2.8.6.0, install the nightly cm-12.1 and appropriate gapps. This time no errors about partitions, everything seemed clean. Sure enough, boot it up normally, wait about 8 minutes on the flashy Android face, and it does the fold/drop thing and proceeds with the initial boot sequence.
So be careful everyone! I hope at least someone comes here and finds this if they've "Bricked" their photon Q, and that it saves them from the depths of despair that I found myself in! If only I'd have seen this trick in this thread, I would have been back up and running in 30 minutes or less!
Best wishes with your upgrades/recovery!
kabaldan said:
For now, just a test build before the official cm-12.1 nightlies for Photon Q will be enabled.
Download link (cm-12.1-20150405-UNOFFICIAL-xt897): http://d-h.st/2ul
Gapps (use gapps-lpmr1-...): http://d-h.st/users/dhacker29/?fld_id=27426#files
TWRP 2.8.6.0 recovery for xt897: http://d-h.st/lEHx
(feel free to provide mirrors on other/better file hosts)
Device specific source repos:
motorola/xt897: https://github.com/CyanogenMod/android_device_motorola_xt897/tree/cm-12.1
motorola/msm8960_jbbl-common: https://github.com/CyanogenMod/android_device_motorola_msm8960_jbbl-common/tree/cm-12.1
motorola/qcom-common: https://github.com/CyanogenMod/android_device_motorola_qcom-common/tree/cm-12.1
kernel: https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common/tree/cm-12.1
Please note:
Since CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead. Use xt897 specific builds when you go beyond CM11.
GSM users (SIM card mod):
Please switch the Settings>Mobile networks>Preferred network type to 'GSM/WCDMA auto' or 'GSM/WCDMA preferred' from 'Global' for correct modem functionality on GSM networks.
What's new in cm-12.1 for xt897:
Lollipop turned out to be very RAM demanding. 1GB RAM devices seem to be below the limit of what lollipop actually needs.
To overcome this issue, 256MB of RAM has been dedicated to zram (compressed swap living in RAM). Zram can give us a bit more of effectively usable RAM space.
To speed-up the zram operations, kernel has been updated to the latest zram code with support for the fast lz4 compression.
Another new kernel addition is cpu-boost driver that can boost cpu frequency e.g. when input events are happening (touch screen interaction) regardless of cpu governor in use.
Known issues:
- USB audio output (analogue) via USB>audio Y-cable (Motorola Car Dock/EMU audio) is not working correctly yet
- USB audio DACs/sound cards connected as USB OTG peripheral do not work correctly yet
Click to expand...
Click to collapse
I don't know that my posts are even going to be seen because I haven't made 10+ posts here yet and therefore it keeps throwing me to this Q&A thread. Regardless, I will try.
I'm now running the 12.1 4-21 nightly.
After my first initial struggle to get 12.1 installed/running, I found that I didn't actually have a data connection once I got out of wifi range.
Took many trials and lots of time to figure this out. Turns out that some of the AT&T APN's are missing "hipri" which they apparently need to work. Once I added that, I got my data connection.
Now I'm have a problem reliably connecting to AT&T. This wasn't the case with 12.0 at all, connected quickly every time. After a reboot, it keeps cycling trying to connect and quickly failing. I have to fight with it in the network selection settings. Eventually it'll succeed at a manual scan where I can select AT&T, or it will succeed at an automatic selection. This seems odd because when I run an adb logcat, it does seem to be trying to connect to AT&T on its own. So whether it would eventually connect on it's own and the busy work of me fighting with the network selection settings just makes me feel better some how that I'm fixing it, I'm not sure yet.
I can also confirm that the lock page says "No Service" even when the network is connected including data.
I hope these things help someone else out and perhaps lead to a fix. Happy to try stuff out or run a trace if it would help, just let me know.
I had exactly the same issues when trying to flash CM 12.1 (Not able to mount /data, not able to mount /cache... )
Fixed this by manually formatting each partition at one time. I also changed data and cache to f2fs
No need to go with older TWRP
But I still have the connection issues exactly as you describe in your second post.
I'm running Freedompop (on top of Sprint network)
By manually formatting, what do you mean? Did you use TWRP Wipe-Advanced and just select the partitions one at a time? That wasn't working for me for some reason, it kept on messing up the partitions and failing. What version of TWRP are you using, is it the latest 2.8.6.0 or...?
You're brave to go with f2fs. Do you feel it's performing better?
Just to clarify on the network provider point - I did the simcard hack to my Photon Q, this is how I am able to run it with AT&T. Interesting that the problem I described happens with the native CDMA/Sprint network as well.
I hope we get a fix for the connectivity issue soon. I feel a little uneasy praying that the phone doesn't lose its connection or reboot for fear that I can't get it connected again in a reasonable period of time.
turbozapekanka said:
I had exactly the same issues when trying to flash CM 12.1 (Not able to mount /data, not able to mount /cache... )
Fixed this by manually formatting each partition at one time. I also changed data and cache to f2fs
No need to go with older TWRP
But I still have the connection issues exactly as you describe in your second post.
I'm running Freedompop (on top of Sprint network)
Click to expand...
Click to collapse
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
I have a feeling that your selection of f2fs for your cache and data partitions influenced your success with wiping. I attempted the same process numerous times, but without changing the partition file system, and was unable to get all the partitions to a proper state with TWRP 2.8.6.0.
I didn't see anything in the changelog (http://www.cmxlog.com/12.1/xt897/) that would suggest a fix was included for the connectivity problem in either the 4/22 or 4/23 nightly so I haven't tried updating just yet, preferring instead to try to prolong my existing connection until there is more hope that when I reboot I will be able to connect without struggling with it.
It's too bad we're not able to participate in the main thread as there is a more active discussion going on there. I suspect this is just a parking lot. Perhaps if we keep posting our ongoing findings here for a couple of more days we'll get over 10 posts and be able to generate some more activity on these issues.
turbozapekanka said:
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
Click to expand...
Click to collapse
timekiller_9 said:
It's too bad we're not able to participate in the main thread as there is a more active discussion going on there. I suspect this is just a parking lot. Perhaps if we keep posting our ongoing findings here for a couple of more days we'll get over 10 posts and be able to generate some more activity on these issues.
Click to expand...
Click to collapse
The Q&A thread is no different from the other thread. I don't think the maintainer cares if you post questions in the dev thread, but some maintainers can get annoyed by that. That's the whole point of the Q&A thread, to ask questions... The dev thread is "supposed" to be for development discussion only, although that seems to rarely happen.
Thanks for the tips arrrghhh.
Other than to confirm that others have similar issues and it's not a matter of something I'm doing wrong, I don't really have any questions. There are a couple of pretty serious bugs in CM 12.1 for the Photon Q. I would like to participate in the development of fixes in so much as I can. I'm not likely to be able to pinpoint where in the code things are broken as that would take some pretty serious time familiarizing myself with the layout. That said, I am a systems engineer by trade and feel comfortable running all sorts of tests/traces.
arrrghhh said:
The Q&A thread is no different from the other thread. I don't think the maintainer cares if you post questions in the dev thread, but some maintainers can get annoyed by that. That's the whole point of the Q&A thread, to ask questions... The dev thread is "supposed" to be for development discussion only, although that seems to rarely happen.
Click to expand...
Click to collapse
Hey turbozapekanka,
Check out my latest response in the main (albeit meant for development, it's where the real action is) thread:
http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781/page5
I'm not sure if it'll work for CDMA but you may wish to try it. It would be good data to know if your problem lies elsewhere in any case.
Good luck!
turbozapekanka said:
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
Click to expand...
Click to collapse
wifi
Has anybody problems with Wifi?
i cant turn it on. Its off in the extended Settings is the Message "Wifi ist activating" but nothing happens
Do you guys have any idea on why we got 'no new update' message from settings/update, even though we have an obvious nightly update? http://www.cmxlog.com/12.1/xt897/
palmwangja said:
Do you guys have any idea on why we got 'no new update' message from settings/update, even though we have an obvious nightly update? http://www.cmxlog.com/12.1/xt897/
Click to expand...
Click to collapse
It's a server side issue affecting all cm12.1 devices, should be fixed soon.
Has anyone's 'long press volume keys for playback control' stopped working? When my screen is off the volume keys don't seek tracks like they did in a previous nightly.
Also ,does smart lock work for you guys? I can see the option but can't seem to get it to recognise NFC or my face.
hi.
Will cm12.1 support all f2fs file? It is the system / data / cache all formats into f2fs, thanks.
hhvstp said:
Will cm12.1 support all f2fs file? It is the system / data / cache all formats into f2fs, thanks.
Click to expand...
Click to collapse
CM12 supports it, I would imagine 12.1 does as well...
Heck, there is a CM11 build floating around with support for it.
12.1 Sprint CDMA access
Since I haven't posted much, I could not reply to the thread, but here's what I did to get 3G data back.
Installed the 05/01/2015 12.1 build.
Edited the build.prop file
changed ro.carrier=
to
ro.carrier=Sprint
rebooted - and I now have data.......
Not sure "why" that worked, but It hasn't up until I made that change....
apns-conf.xml issues
Compared to CM11, several of the entries in the /system/etc/apns-conf.xml file from CM12.1 are missing the "default" type. This makes it impossible to actually select the APN settings for Ting, Credo and Sprint MMS. For instance, I'm on Ting and changing:
type="mms"
to:
type="default,mms"
And then deleting /data/data/com.android.providers.telephony/databases/telephony.db and rebooting made it possible for me to select TIng. Previously there was no radio button next to the entry.
I still have the problem where the "Access Point Names" menu usually says "Access Point Name settings are not available for this user" most of the time but now when I *am* able to enter that menu I can at least select the right APN setting.
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
GreeGreeCreedle said:
Since I haven't posted much, I could not reply to the thread, but here's what I did to get 3G data back.
Installed the 05/01/2015 12.1 build.
Edited the build.prop file
changed ro.carrier=
to
ro.carrier=Sprint
rebooted - and I now have data.......
Not sure "why" that worked, but It hasn't up until I made that change....
Click to expand...
Click to collapse
Nice catch. It looks like ro.boot.carrier is set correctly but for some reason ro.carrier is unknown.
hi.
CM12.1 experience to perform part of the game will be LAG, turn off the sound, then you can ease, what is the problem?
millertoo said:
Compared to CM11, several of the entries in the /system/etc/apns-conf.xml file from CM12.1 are missing the "default" type. This makes it impossible to actually select the APN settings for Ting, Credo and Sprint MMS. For instance, I'm on Ting and changing:
type="mms"
to:
type="default,mms"
And then deleting /data/data/com.android.providers.telephony/databases/telephony.db and rebooting made it possible for me to select TIng. Previously there was no radio button next to the entry.
I still have the problem where the "Access Point Names" menu usually says "Access Point Name settings are not available for this user" most of the time but now when I *am* able to enter that menu I can at least select the right APN setting.
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
Nice catch. It looks like ro.boot.carrier is set correctly but for some reason ro.carrier is unknown.
Click to expand...
Click to collapse
I don't have this device but hopefully this post helps those with apn issues. If I toggled network mode to lte only, the apn listings would actually show.
http://forum.xda-developers.com/showthread.php?p=61070073
This is for CyanogenMod 13.0, Android version 6.0.1, unofficial builds whose primary purpose is meant as preview.
Credits: All credits go to kabaldan, stargo and CyanogenMod contributors.
Disclaimer
Code:
Use at your own risk, responsibility is all yours, provided as-is, no warranties...
You know the drill.
What has changed/is new can be viewed at cyanogenmod gerrit: http://review.cyanogenmod.org/#/q/status:merged
Latest change for the January 30, 2016. build is at http://review.cyanogenmod.org/#/c/130563/
Latest change for the February 13, 2016. build is at http://review.cyanogenmod.org/132753
Latest change for the March 21, 2016. build is at http://review.cyanogenmod.org/127971
SELinux is disabled (if you care about security you'd might wan't to wait for an official build)
SELinux enabled in March 21. build
ART preopotimization is enabled: speeds up first boot after wiping dalvik cache: only some of framework, GApps (if present) and user installed apps need to be compiled. It also saves some space in /data as system apps odex/art/oat files are stored in /system partition instead of /data/dalvik-cache. This is the reason for the large size of the update package.
disabled GPU page faults logging in kernel as it only (unnecessarily) spams the logs
Included the new Snap camera app (the old AOSP Camera2 is still kept as a fallback): Both are called "Camera" but you'll be able to easily differentiate between them by the icon.
Keyboard backlight behaviour has been updated to resemble stock-like behaviour. Details can be read in the commit message of the change (Patchset 1, not PS2, or here). Feel free to test and share what you think.
Reverted to old keboard backlight behaviour in March 21 build
All relevant changes (i.e. differences from default/stock CM13) can be viewed at my github repo
Installation (first time install):
1) Download the build
2) Boot into recovery (power button + voulme up)
3) Make a full nandroid backup
4) Flash update package (install zip ...)
5) Wipe data/cache (factory reset)
6) Reboot to system
Update (if you're updating existing cm-13.0 or upgrading from cm-12.1)
1) Download newer update zip file and install it from recovery.
2) Wipe dalvik-cache
3) Reboot to system
It might be useful to enable aplogd logging, especially if you come across some issues.
You can enable aplogd in terminal or adb shell
Code:
su
setprop persist.log.aplogd.enable 1
Logs are saved in /data/aplogd/
In case of a full system reboot include /proc/last_kmsg as well.
NOTE !!! :
Please do make a full nandroid backup! In case anything goes wrong or you simply wan't to go back, you should be able to recover/restore in a jiffy. If, by chance, you have issues restoring system when twrp claims it failed to mount system, a relatively simple workaround is to flash whichever CM update, flash GApps you used previously and then restore only data, wipe dalvik, reboot... hope for the best...
Downloads
March 21, 2016.
Some of changes:
Code:
Enabled SELinux enforcing
Reverted to old-style keyboard backlight behaviour: it won't be brighter than screen but it also won't completely turn off kbd backlight on very bright conditions (I shoud really put some effort into it...)
Using Flo's PowerHAL
Updated interactive governor in kernel
Enabled Motorola memutils in kernel (should improve memory operations)
Quite a bit of other updates/changes/fixes
All details can seen at CM gerrit and my github repo (not very practical but...)
MD5: 96ce2fc03b43c0123fcdc559fb531761
File size: 348,852,931 bytes
Download
February 13, 2016.
MD5: 19d3cb88cdc9a1cf1857b3e263298b19
File size: 348,081,995 bytes
Download
January 30, 2016.
MD5: 454c62323c5e8f93f96ec6a9de580a2f (or use the attached to post md5sum file)
File size: 343,989,482 bytes
Download
So from what I've experienced with using this all day, it runs perfectly. I've had no bugs or anything like that so far. I think service was working too (can't tell now because I just canceled my ting account) but earlier today when it was still active, I had bars. Didn't try data though.
Other than that, everything is running very very smoothly.
u guys probabaly already know this but my service with i-wireless aka a sprint based variant isnt detected at all. Shame cuz it runs likes a dream otherwise. I guess not installing gapps has contributed to this performance boost tho
How are you guys going about installing 13.0? Does it install nicely on top of 12.1 or is a device wipe required? How about your version of TWRP?
timekiller_9 said:
How are you guys going about installing 13.0? Does it install nicely on top of 12.1 or is a device wipe required? How about your version of TWRP?
Click to expand...
Click to collapse
Data wipe is not mandatory.
You can use kabaldan's twrp from cm-12.1 thread
I installed it over CM12.1, and besides some minor glitches (ie. bad version of leftover google services - which can be easily repaired by flashing the latest gapps), the ROM's running well. To be honest, I don't see many differences.
Thanks for great work
Hello.
Can anyone help me with installation CM13 at new phone? Should I root phone, install Safestrap, create new partition and install this rom on it? Or maybe in this phone should I do something else?
I have problem wit bootloader unlock. I try to pass on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
but when I enter a code webpage refuse to generate code :/.
KusioST said:
I have problem wit bootloader unlock. I try to pass on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
but when I enter a code webpage refuse to generate code :/.
Click to expand...
Click to collapse
Please post in one of the many threads related to bootloader unlock issues in Q&A or General... this issue has nothing to do with CM13.
Also, just as an aside - if you can't get the code to work use one of the other methods like motochopper et al.
Sorry for that. I just don't see something like how to install this rom so I ask. I will search information in other parts of forum. You can delete my posts to maintain this thread clear.
mrvek said:
This is for CyanogenMod 13.0, Android version 6.0.1, unofficial builds whose primary purpose is meant as preview...
Click to expand...
Click to collapse
I installed this ROM, but GSM network don't work. There is no option in network setting to change network type like in 12.1 for XT897. In 13.0 for XT894 GSM patch was automatically added. I need to search some fix for this ROM and install it after I install ROM?
My phone have attached additional SIM slot for SIM card and I use it in EU.
KusioST said:
I installed this ROM, but GSM network don't work. There is no option in network setting to change network type like in 12.1 for XT897. In 13.0 for XT894 GSM patch was automatically added. I need to search some fix for this ROM and install it after I install ROM?
My phone have attached additional SIM slot for SIM card and I use it in EU.
Click to expand...
Click to collapse
No such issues here, everything works out of the box.
I remember something like that in the beginning of cm-12.1 when installing clean, there was no signal, no options under mobile network settings in Settings (without factory reset network was fully functional) but it was most likely some local/obscure glitch/derp. The only way around it was to not wipe data. Weird...
Proximity sensor and luminance sensor not working, and bright adjust not modify brightness. more someone with this problem?
mrvek said:
No such issues here, everything works out of the box.
I remember something like that in the beginning of cm-12.1 when installing clean, there was no signal, no options under mobile network settings in Settings (without factory reset network was fully functional) but it was most likely some local/obscure glitch/derp. The only way around it was to not wipe data. Weird...
Click to expand...
Click to collapse
So You said that I need to do second try and have hope that this time it will work?
Installed it on my wife's xt897... Data is currently unknown as due to the bloat of 12.1 she swapped to an iPhone (and boy she hates it). The front camera isn't showing up either. Google Calendar keeps quitting and showing as a pop-up error.
Otherwise it's a nice ROM indeed. Once the kinks are worked out (and I replace the battery) she'll probably use it again.
I have no problems with Google Calendar (but as I mentioned before, I flashed CM13 gapps just after system). Unfortunately you're right: front camera is broken. Hope somebody fixes that.
For me Cell data, calendar, wi-fi and also front camera are working. I have dirty flashed over CM12.1 and also flashed new gapps.
Funny, I dirty flashed over 12.1 and flashed Gapps as well. IIRC the Google calendar glitch, on this phone at least, was also in 12.1. If it were my phone is wipe and retry but beng my wife I'm not sure I can right now.
mrvek said:
No such issues here, everything works out of the box.
I remember something like that in the beginning of cm-12.1 when installing clean, there was no signal, no options under mobile network settings in Settings (without factory reset network was fully functional) but it was most likely some local/obscure glitch/derp. The only way around it was to not wipe data. Weird...
Click to expand...
Click to collapse
I made advanced wipe choosing system, data, cache, and dalvik-cache. Now after installation GSM start to work .
I have question about sms application. Why when i tapped 2 time this same letter i get some special letter (for example n --> ń)? Where can i change it?
KusioST said:
I made advanced wipe choosing system, data, cache, and dalvik-cache. Now after installation GSM start to work .
I have question about sms application. Why when i tapped 2 time this same letter i get some special letter (for example n --> ń)? Where can i change it?
Click to expand...
Click to collapse
Most likely kabaldan's multipress feature from the old cm10 days I keep using. Your system language is Polish?
Anyways, you can configure multipress language and timeout using system properties (terminal emulator or adb shell):
Language property: "persist.sys.keypad_multipress_l"
Timeout property: "persist.sys.keypad_multipress_t"
To setup language (default is "auto", i.e. system language):
Code:
su
setprop persist.sys.keypad_multipress_l {language code (cs, da, de, de2, es, fi, fr, hr, hu, it, lt, nl, no, pl, pt, ro, sk, sl, sv)}
To disable multipress feature use english language (en):
Code:
su
setprop persist.sys.keypad_multipress_l en
To setup timeout between keypresses while subsequent key presses are considered for replacement (default is 200ms):
Code:
su
setprop persist.sys.keypad_multipress_t {timeout value in miliseconds}
You can either experiment or lookup Unicode characters here or here. E.g., for Czech (cs) letter "A" is replaced with unicode "00C1" which translates to "Á", etc.
List of supported languages and the mapping can be seen in the commit: e.g. here for Czech language, etc.
As for everything else: I really have no issues whatsoever with CM13. I no longer use google calendar but had no issues with it, both rear and front cameras are working, led lights, proximity, ambient light sensor are all fully functional. Perhaps enable aplogd...