Related
[GUIDE][Nov.6] CM7 Bible - How-To & Fixes - Radio Bootloop Fix, Browser Fix and MORE!
FIRST POST IS HOW-TO, SECOND POST CONTAINS ALL THE FIXES AND WORKAROUNDS
GENERAL INFORMATION AND HOW-TO INSTALL / UPDATE CM7
Alright kids,
We are all very happy that CM7 finally came out to play. And we thank kmobs and the whole CM7 team for all the hard work. They are just... AWESOME!
But while we have that, we also have a lot of people that are either first time android users, or that are just too busy to follow the thread, or just are too lazy (nothing wrong with that, im lazy too )
So here is a guide on how to install CM7, and I will gather all the fixes from the other thread, and will also if I forget something - let me know what I am forgetting and will add it in this thread.
Now here we go:
~~~~~~~~~~~~~I am not to be held responsible if you brick your device following these guides. If you brick it - blame Santa, not me!~~~~~~~~~~~~~~~~~~
INSTALLING CM7
To install CM7 on your device, you need to first download it from HERE. Once you do that - please follow the next steps:
Code:
1. - Put the ROM on your SD card
2. - Reboot into CWM Recovery
3. - Do a Nandroid backup of your current rom. Just in case.
4. - Wipe Data/Factory Reset
5. - Wipe Cache
6. - Go into Mounts
7. - Format /system
----- I always do that, and dont have a single issue..
8. - Flash your Rom
9. - Go into Advanced, Wipe Dalvik Cache, Fix Permissions
10. - Reboot phone
Alright, once you are done with the reboot, it will start loading the ROM. Let it be for around 10 minutes, so its done with everything. Dont set it up, Dont do ANYTHING. Just watch some youtube, or have a beer, or call that girlfriend of yours. Now after the 10 minutes are done (or at least 40 minutes if you talked with the girlfriend ) - reboot the phone again.
INSTALLING GOOGLE APPS
Now its time to get Market, Gmail and all the other goods.
Here is the newest google apps - HERE
Now download the newest Talk with video - HERE
Once you do that - Put them on your SD card and reboot into CWM Recovery and follow the steps:
Code:
1. - Do a nandroid backup of your current ROM. Just in case things go south.
2. - Flash the Google Apps
3. - [B][I][U]AFTER THAT[/U][/I][/B] flash the gapps with new Talk
4. - Wipe Cache
5. - Go to advanced
6. - Wipe Dalvik Cache
7. - Fix Permissions
8. - Reboot Phone
Now set them up, and you are set. You have MARKET!
UPDATING FROM AN OLDER BUILD
If you already had the CM7 on your device, and want to install to the latest Alpha - follow the instructions:
Code:
1. - Download New Update
2. - Reboot into CWM Recovery
3. - DO A NANDROID BACKUP!!!!
4. - Install the new update
5. - Wipe Cache
6. - Go into Advanced, and wipe Dalvik Cache
7. - Reboot and enjoy the newest Alpha!
8. - If it runs worst than the build you had before, and you didnt do a backup - blame yourself and Santa for destroying Christmas, and start over.
RECOMMENDED RADIO
persiansown said:
I recommend using radio 10.56.9035.00U_10.14.9035.01 because this is the radio that we personally tested.
Please note flashing someone else's kernel may ruin your experience with this rom and I advise against it. This rom was a joint effort between Bumblebee, cretin45, toastcfh, defer, myself, and the rest of the CM team.
Click to expand...
Click to collapse
To install it - just put the zip on your SD card, reboot into bootloader, select Bootloader and it will ask you if you want to apply the update. Press volume UP to apply update, dont shut off the phone, and when its done - press Power to reboot.
DO NOT CHANGE THE NAME OF THE FILE
STUCK IN A BOOTLOOP AFTER RADIO UPDATE
If you are stuck in a bootloop after the radio update, all you need to do is the following:
Code:
1. - Open the back cover
2. - Remove the SD Card
3. - Pull the battery out for 5 secs and put it back in
4. - Put the cover back on
5. - Press Vol Down and Power at the same time. Keep holding on Vol Down till you get in bootloader
6. - Select Recovery
7. - Wipe Cache
8. - Put your SD Card back in
9. - Reboot phone and its all working again. Yey.
Here is another solution, thanks to joshndroid for the tip !
joshndroid said:
tony..
may i suggest in your guide thread to cm7 as a possible solution to the radio to flash AFTER you flash the ROM/UPDATE...
also;
maybe can i suggest to take the radio.img file out of the flash zip and flash it with fastboot...
1. Open zip file and place the radio.img into the location of your adb/fastboot (platform-tools or tools, depending how you set your fastboot up)
2. Place your phone into fastboot.. by connecting phone to computer and typing
adb reboot bootloader
OR
by turing your phone off and holding volume down + power on buttons
3. flash radio by typing these fastboot commands
fastboot flash radio radio.img
4. once that is finished restart phone by typing
fastboot reboot
i did both of these things and accrued no problems and as you know im not a TMOUS and it seems that every EU phone owner blames the ROM for being american in region, which we both know that is not a problem..
Click to expand...
Click to collapse
Thank you, sir!
INSTALLING CUSTOM KERNEL
PLEASE MAKE SURE THAT YOU ARE INSTALLING THE CM7/AOSP KERNEL, AND NOT THE SENSE ONE!!!!!!!!!!!
If you are having any issues with the current CM7 build - you can always flash a custom kernel. Head over to Faux123's Thread and download the newest kernel. Just to be on the safe side - download the regular newest kernel, don't go with the extreme edition (if this is your fist time flashing a kernel), as it might be unstable for your device.
How to do that, you will ask?
Code:
1. - Download the kernel
2. - Put the .zip on your SD card
3. - Boot into CWM Recovery
4. - Format Cache
5. - Flash the .zip file
6. - Go into Advanced
7. - Format Dalvik Cache
8. - Reboot your phone, and enjoy your new kernel
Big ups to Faux123 for all his great work, I have been following him since the MyTouch 4G, its always a pleasure to see what he has cooking for us!
FIXING SOUND VOLUME
To fix the sound volume - you need to do the following:
Code:
1. - Go to Settings
2. - Go to Cyanogen Mod Settings
3. - Go to Sound
4. - Scroll down and find "Always play on speaker"
5. - Check Notifications, Ringtones, Alarms
Now you have a full working Sound. People say that right after you connect your headphones - it removes these settings. So you might have to do them one more time. Just do it! There is no known permanent fix right now. Hopefully in one of the nightlies it will be addressed.
HOMESCREEN LAG
If your homescreen is lagging, like mine did - I suggest using a different launcher. I removed ADW and installed Launcher Pro. I havent had a single moment of lag after that.
Or you can head over to the second post, and download the 2D or 3D replacement Launcher, which will make things better. Big thanks to xboarder56 for sharing them with all of us!
BATTERY ISSUES
First - If you have problems with your battery draining too fast - maybe its because you installed another kernel. So try reverting back to stock kernel (Follow the "flashing CM7" guide, just dont wipe anything).
If issues are still there - Try to recalibrate your battery. You can do that by two different ways:
1st - Charge your battery to 100%, drain it all the way till it shuts off. Now dont turn the phone on, just plug it in, and leave it like that for 7-8hrs. Best done overnight. In the morning - turn on the phone, and repeat everything again. That should fix it.
2nd - Download "Battery Calibration" App from the market. Install, and follow the guides
BETTER CAMERA FIX
Alright, thanks to jjdeveau for this fix. If you do not like the camera that comes with CM7 - you can use the MIUI Camera.
Here is how to install it:
jjdeveau said:
Okay so.. For all of you who want a better camera. Here is the miui camera apk.
DO NOT JUST INSTALL IT!
#1 Open rom manager and Back up your Rom
#2 copy to system/app replacing the stock one.
#3 change the permissions but tapping and holding on the app and going to properties then hit change make sure the permissions looks the same as the other aps in the folder.
#4 open app let it install.
#5 I had to reboot phone then it showed up in my aps as miui camera.
The downside is the camera zoom still does not work and it does not support the front facing camera. tap to focus is working as well as the stock effects. it also has the panoramic view and is about as close to the sense camera as you can get right now.
Click to expand...
Click to collapse
Just download it from HERE and follow the instructions above, brought to you by jjdeveau. Thanks buddy!
CORRECT APN SETTINGS FOR TMOBILE-US USERS
camalus said:
Fixed my issues with Wifi-Calling MMS.
I talked to TMobile and they gave me the correct info for the APN settings.
I deleted both of the APNs listed under wireless settings and created a new one.
Just in case any of you are having issues with SMS or MMS using Wifi-Calling.. give this a shot.
Create a new APN.
Name: T-Mobile
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username: leave blank
Password: leave blank
Server: leave blank
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.050
MMS Port: 8080
MCC: 310
MNC: 260
Authentication Type: leave blank
APN: default,supl,mms (Very important to not have a space in there.. just the ,)
hit the menu button and hit save. then use that apn. You should now have working MMS and SMS.
Hope that helps. Cheers.
Click to expand...
Click to collapse
FLASH PROBLEM WITH STOCK BROWSER
There are two workarounds to this issue:
1st one is - just download and install opera mobile from the market. It runs flash with no issues.
2nd one is coming to us, thanks to LSears:
For those of you having problems with Flash, it seems to be happening on a few devices with CM7.1. It can be fixed by altering the config.data file of the plugin within any app using it.
So, with the default browser as an example, you'd need to change directory (in ADB shell or a terminal emulator) to...
/data/data/com.android.browser/app_plugins/com.adobe.flashplayer/.macromedia/Flash_Player/
and then alter the permissions of the config.data with...
chmod 000 config.data
I've also done the same things within the BBC News app and BBC iPlayer. All now work perfectly! I hope that helps those with problems.
Click to expand...
Click to collapse
GPS LOCK FIX / WORKAROUND
For people that have GPS lock issues - I have a little fix/workaround that worked out great for me and my issues. I hope it works for all of yall.
You need to go to the market, and download GPS Test by Chartcross Ltd (its free).
Open the program -> hit the menu button -> select Settings -> hit "Clear AGPS" and after that hit "Update AGPS". Give it a few minutes and you should have a much better reception and lock on more sats. I got 6 sats locked from the inside of my house.
If it stops showing you the GPS icon - thats fine, just reboot the phone and it will all be ok.
It's bit obivious...
but I would add doing Backup before wiping/formating etc... just if something goes wrong.
Why not put this in the cm7 thread in the op just pm the dev
walto said:
but i would add doing backup before wiping/formating etc... Just if something goes wrong.
Click to expand...
Click to collapse
+1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1
daman215 said:
Why not put this in the cm7 thread in the op just pm the dev
Click to expand...
Click to collapse
Cause in my experience - there is NEVER any guides provided by the CM7 team. In every phone sections that you look at - there is always a separate thread for guides and fixes.
Plus all the questions that are answered in this thread are asked over 15329852 times in the ROM thread, and its probably good to have them all in one place, instead of people having to read through hundreds (soon to be Thousands) of pages...
I would add a step for making a nandroid backup. Good writeup though.
Walto said:
but I would add doing Backup before wiping/formating etc... just if something goes wrong.
Click to expand...
Click to collapse
Thanks bud,
Almost forgot about that... Would of been a big mess for some of the new to android people around
dcmtnbkr said:
I would add a step for making a nandroid backup. Good writeup though.
Click to expand...
Click to collapse
Already done
Does Wifi Calling on TMOUS require a separate flash?
Thanks!
psychedelicx said:
Does Wifi Calling on TMOUS require a separate flash?
Thanks!
Click to expand...
Click to collapse
Nope, its already included.
t0ny0 said:
Nope, its already included.
Click to expand...
Click to collapse
Thanks for the guide, very helpful, and I'm sure not only for beginners.
f.
Sent from my HTC Sensation Z710e
Nice post but didn't CM got like a whole wiki website for this stuff?
Any info on a fix it workaround for calls disconnecting when putting phone against your ear, I.e. when proximity sensor kicks in? Mainly affecting uk users.
pr0x2 said:
Nice post but didn't CM got like a whole wiki website for this stuff?
Click to expand...
Click to collapse
They might, but that doesn't really stop the billion questions asked all the time, so that makes me think that people are not going to the wiki, they are looking for answers up in this forum.
t0ny0 said:
They might, but that doesn't really stop the billion questions asked all the time, so that makes me think that people are not going to the wiki, they are looking for answers up in this forum.
Click to expand...
Click to collapse
Just a little anecdotal support-- when I rooted my first Android device (Nexus One, if it matters) I started off in a Guide thread in the Development section. Of course, I did finally end up at the CM Wiki, which I don't think it could hurt to link to eventually.
However, the extra bits at the end about flashing the latest GTalk and workarounds for common bugs in the Alpha version are things that I don't think would necessarily make it to their official Wiki. I think the scope of this thread is perfectly helpful
Very useful guide.
what is the recommended radio for cm7? I searched the cm7 thread and read the question asked several times but no clear cut answer. Might be helpful to add that info for people like me
Also, on reboot I lose network connectivity and have had to flash twice already...full wipe both times. I think it might be radio related.
t0ny0 said:
Cause in my experience - there is NEVER any guides provided by the CM7 team. In every phone sections that you look at - there is always a separate thread for guides and fixes.
Plus all the questions that are answered in this thread are asked over 15329852 times in the ROM thread, and its probably good to have them all in one place, instead of people having to read through hundreds (soon to be Thousands) of pages...
Click to expand...
Click to collapse
THIS. Thanks for your contribution!
Sent from my HTC Sensation Z710e using Tapatalk
Wifi calling FC still on going after following both your fixes ... any other ideas
Sent from my Sensation using XDA Premium App
stanny2k said:
Wifi calling FC still on going after following both your fixes ... any other ideas
Sent from my Sensation using XDA Premium App
Click to expand...
Click to collapse
I am fresh out of ideas..
Maybe go ahead and try Faux kernel, and see if its gonna keep FC after that...
Profondo_Rosso said:
Very useful guide.
what is the recommended radio for cm7? I searched the cm7 thread and read the question asked several times but no clear cut answer. Might be helpful to add that info for people like me
Also, on reboot I lose network connectivity and have had to flash twice already...full wipe both times. I think it might be radio related.
Click to expand...
Click to collapse
I am using 10.42.9007.00P_10.11.9007.15
Seems to be working for me... Added it to the GUIDE and linked to the thread where it can be found, and also that other thread has instructions on how to install it
Issue with call disconnecting resolved.
Confirmed working. Details here :
http://forum.xda-developers.com/showthread.php?t=1261154
I installed the file using es file explorer. Set it to root enabled and to mount the system as read write and then copy file to system/lib
I have very strange problem with my euro 3g xoom. When I bought it it recognized my sim card and network (T-Mobile Hungary). Now I flashed Tiamat 2.2.2 Moray. Of course I had a lot of problems with that one so I went for Hammerhead and flashed 3.2.2 stock rooted too. In every case I did a complete wipe / factory reset and a dalvik cache wipe too.
Now the actual nature of the problem is that I LOST PARTS OF MY 3G SETTINGS. This means I cannot define APN any more nor can I select service provider. Menus are missing. 3g device activation fails with infinite attempt to activate device.
As it appears to me Xoom seems not to recognize my 3g modem at all..
Any suggestion / comment is welcome. Right now I am on 3.2.2 stock rooted with of rogue ran a kernel. Oc 1.5 ghz rock solid, excellent performance no FCs at all, ONLY 3g is not working at all.
Thanks for any support in advance.
My hardware is European Xoom 3g, model nr. MZ-601 - Tegra 250.
-p0rt3r-
UPDATE_1
Tried Rogue Recovery 1.3.0 to see if the Solarnz one based on CWM 3.2.0.0-rc1 is responsible not wiping some faulty settings - no success, still missing menus in Mobile Network settings.u
For ppl who might responde to this rthred: I don't really nee a GUI for setip its okay when u guys tell me which file to edit in order to put in my APN which is very genuine: "internet"
Right now my baseband is "unknown" in the about tablet section....
-p0rt3r-
UPDATE_2
Here is what I have in the Mobile network settings:
Data enabled
Data Roaming
System select
Activate device
And no, I cannot scroll down any further etc.
p0rt3r-
UPDATE_3
Went back to Hammerhead where:
Version 2.1
Fixed all the application signatures - Google applications should update fine now.
All of the language packs are now incorporated into this rom
European 3g support should be 100% working now.
Native screenshot is back
now what I see is:
Data enabled
Data roaming
System select (change CDMA roaming mode) - I am on GSM!
Activate device.
Thats it for Mobile network settings menu.
You need to extract the telephoney files after installation. Bear with me and I will try to find the link. Be back soon.
Ok, here is the thread I think you need: http://forum.xda-developers.com/showthread.php?t=1089695
You should have backed up your original Euro 3G with CWM (Clockworkmod Recovery)
These are the files you need:
settings.db settings.db-shm settings.db-wal telephony.db telephony.db-journal from the data.img (From your original backup) You will need unyaffs.exe (use google search to get it)
1) Copy (not move) your original data.img to the same folder as unyaffs.exe.
2) Open cmd prompt and change directory to point to the folder now containing the unyaffs.exe and the data.img
3) type "unyaffs data.img" without quotes and press enter.
4)Copy all databases from /data/data/com.android.providers.settings/databases/ (above mentioned files)
5) Flash the rom you want i.e. Hammerhead etc. (Best clean install)
6) Then reboot
7) Once booted and signed in etc. open a cmd prompt pointing to adb's location
8) adb remount
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb push settings.db-wal /data/data/com.android.providers.settings/databases/settings.db-wal
adb push settings.db-shm /data/data/com.android.providers.settings/databases/settings.db-shm
adb push telephony.db /data/data/com.android.providers.telephony/databases/telephony.db
adb push telephony.db-journal /data/data/com.android.providers.telephony/databases/telephony.db-journal
adb reboot
If you have followed the instructions properly then on reboot you should have Euro menu for choosing GSM etc.
Hope this helps. Thanks and credit goes to lowtraxx
Phil
diigibio, thank you
diigibio,
thank you. Would be more than happy if you could provide me with som information how to get Hamerhead or any other native Tiamat rom to work on Euro 3g Xoom.
So far I can confirm that
http://forum.xda-developers.com/showthread.php?t=1183416
lowtraxx's solution is fine, all working now except Google aps updates but I do not really care for that 3g and wifi functionality is the most important, any other thing is addiional gift
waiting for your info.
-p0rt3r-
Problem solved completely?
Phil,
excellent. I cannot say how much this gonna help for me in the future. As for lowtraxx's 3.2, now I hv Hungarian market on Hammerhead I had US market... not sure if I do Hamerhead or any other Tiamat I will have my native market so I will leave this thread open for a while to see if anybody has experience with the solution you just sent me.
I also hv to say great community here, in 2 hrs u solved my problem. Thank you for this.
-Zoltan
Glad I could help. Enjoy. All the best for the New Year from the UK.
Same to u too mate from Hungary
I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img
Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.
cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.
cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?
I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!
A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?
Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.
Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly
Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.
sorry for My question but :
How to install this firmware?
Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip
i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?
And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."
many thanks, Cybermaus, netlocation works again after your instruction
Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues
I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.
jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....
I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.
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
When flashing the Motorola Moto G 2015 with any custom ROM (Cyanogenmod, Resurrection Remix, Lineage), the PRL information sticks until a reboot from custom ROM.
When rebooting, the phone has internet access (including Hotspot), however no text messages, inbound/outbound phone calls do not work. The fix has been flashing Virgin Mobile stock ROM in TWRP recovery, programming the phone (##72786#) and then restoring a backup from custom ROM via TWRP recovery. Then the phone will again be able to send/receive text messages and phone calls - until the next reboot.
Would like to know if there is a fix to bypass reflashing stock ROM if phone needs rebooting from custom ROM. This process takes about 15 - 20 minutes. Big nuisance.
Any assistance would be appreciated.
------------
NetSpeedZ said:
Any assistance would be appreciated.
Click to expand...
Click to collapse
Copy this APN (see the attachments), to system/etc and set permissions to 0644 or rw-r--r-- with a root explorer. Reboot. Go to settings>more>cellular networks, select LTE in Preferred network type, and RUIM/SIM in system select. Tap the "carrier settings" option at the very bottom. All the radios will reset and come back on in a few seconds, and everything should work after that. Let me know if you need any more assistance, I'll be happy to help. I've had to deal with this issue since day one.
Edit; You will only have to do this after flashing a ROM, and this includes updates too. It can also be done through TWRP's file manager immediately after flashing before you even boot it the first time, and without root.
Spaceminer said:
Copy this APN (see the attachments), to system/etc and set permissions to 0644 or rw-r--r-- with a root explorer. Reboot. Go to settings>more>cellular networks, select LTE in Preferred network type, and RUIM/SIM in system select. Tap the "carrier settings" option at the very bottom. All the radios will reset and come back on in a few seconds, and everything should work after that. Let me know if you need any more assistance, I'll be happy to help. I've had to deal with this issue since day one.
Edit; You will only have to do this after flashing a ROM, and this includes updates too. It can also be done through TWRP's file manager immediately after flashing before you even boot it the first time, and without root.
Click to expand...
Click to collapse
Cyanogenmod 12.1 does not have the menu - settings>more>cellular networks. Is this done via stock ROM?
Also, don't have RUIM/SIM in system select. Only 'Home Only' and 'Automatic'.
------------
NetSpeedZ said:
Cyanogenmod 12.1 does not have the menu...
Click to expand...
Click to collapse
Try rebooting the ROM without your sim card in. Then put it back and reboot once more. It should reset. I didn't realize you were still using cm12. Those settings are only found in 6.0.1 and up. The apn settings not being visible has something to do with us being CDMA. I think it's the sim cards virgin uses.
You also need to add these lines to the end of your build.prop too. (Not needed on MM+)
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
ro.telephony.default_network=8
telephony.slteOnCdmaDevice=1
Spaceminer said:
Try rebooting the ROM without your sim card in. Then put it back and reboot once more. It should reset. I didn't realize you were still using cm12. Those settings are only found in 6.0.1 and up. The apn settings not being visible has something to do with us being CDMA. I think it's the sim cards virgin uses.
You also need to add these lines to the end of your build.prop too. (Not needed on MM+)
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
ro.telephony.default_network=8
telephony.slteOnCdmaDevice=1
Click to expand...
Click to collapse
While waiting for your reply, I copied the APNS-Conf.xml file attached to your original reply to the system/etc folder on phone and rebooted. Inbound/outbound phone calls and text messages seem to be working now. Even performed a backup in TWRP and then rebooted again. All seems to be operating properly.
I did not add the build-prop text you gave in previous reply. What exactly does this build-prop text do? I'm hesitant in adding it as everything is operational - the old saying 'don't fix what isn't broken'.
I was using Cyanogenmod 13, however, I did not like some of the Cyanogenmod 13 apps, i.e., text messaging app. The Cyanogenmod 12.1 texting app has many features that CM 13 doesn't. Also, CM 12.1 seemed to run smoother on the Motorola Moto G 2015 phone I'm currently using.
Also would be interested in knowing where the apns-conf.xml file was pulled from and what all this file did to make everything work again.
FYI, as standard procedure I always mount system and then flash the Virgin Mobile APNFix (which I've attached for anyone running across this thread in need of this file) in TWRP after flashing a new ROM and associated GAPPS , however, it seems that the apns-conf.xml file became corrupt/unusable somewhere along the line.
Your efforts in helping me solve this issue are appreciated.
------------
NetSpeedZ said:
I did not add the build-prop text you gave in previous reply. What exactly does this build-prop text do? I'm hesitant in adding it as everything is operational - the old saying 'don't fix what isn't broken'. ....
Also would be interested in knowing where the apns-conf.xml file was pulled from and what all this file did to make everything work again.
Click to expand...
Click to collapse
If everything is working properly, then don't worry about adding those lines. I had to add those and the apn to get LTE working on the older test builds of cm12. As far as I know, it just locks you to virgin. It was likely fixed in later builds of cm12.
The APN I pulled from an older build of cm13. When flashing the older ones, the install process would locate and copy virgin's current apn to /system/etc and rename Motorola's default APN to .bak. (The giant 500kb+ APN with all the carriers found in stock.) It would also add a US Cellular APN. I discovered at some point from poking around enough, that deleting the .bak and US Cellular APNs got LTE working if I reset the radio afterwards.
Spaceminer said:
If everything is working properly, then don't worry about adding those lines. I had to add those and the apn to get LTE working on the older test builds of cm12. As far as I know, it just locks you to virgin. It was likely fixed in later builds of cm12.
Click to expand...
Click to collapse
This is a nice and informative thread for anyone that has the same issues that you and I have had with Virgin Mobile APN's. Hopefully it will be added to Google searches soon.
Appreciate all the help.
------------