Related
(99% DISCONTINUED)
See MotoIncred/MotoFroyoSense for new versions
MotoSense, an adaption of the HTC 2.1 SenseUI(version 1.6) from HTC Desire
Image is only compatible with this a milestone A853 , and cannot be installed on other variants of "Milestone" XT720/A854/A855 branded models (yet).
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
me a Red bull, and you're sure i stay up working on this mod.
LATEST RELOAD PATCH for MotoSense MotoSense v0.51 patch
Old releases :
LATEST FULL MotoSense DOWNLOAD MotoSenseV05
MotoSenseV03
a image folder goes into /nandroid/adbrecovery on your SDCARD its required to have OpenRecovery on your phone to install this image.[/COLOR]LATEST PATCH FOR DOWNLOAD
MotoSense v0.51 patch (see top of post)
WIPE YOUR PHONE BEFORE ANY FULL IMAGE IS INSTALLED! (Recovery menu - factory reset)
If you don't you might get constant reboots with the M logo
INSTALLATION:
Use G.O.T Recovery / Open Recovery to install this rom.
Currently require you to install a 2.36 stock rom, before you install this one.
Radio Band Requirements for different countries
Some countries require the original 3G files of your current ROM to work ie.
Canada, Brazil, Venezuela, Germany and some others countries uses a different band for 3G. If u dont backup the 4 original 3G Files and restore it over this nandroid once installed u gonna have poor signal, sms problems and HSDPA loss (even if u set apn and get conection its gonna be crappy one).
Files should be in the /system/etc/motorola/bp_nvm_default/ of your phone.
This can be done using OpenRecovery and a adb shell.
You might check this thread , if a update-nosign.zip file exists for your model. which makes it easier for you to install.
Filenames are:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
STATUS of the functionality in image
WorkingRadio (Calls,GPRS,HSPA)
USB
Milestone bootup AC charging
Wireless
Bluetooth (limited but works, only with a few functions)Not Working- PINCODE (will not be able to enter any pincode or boot normal)
Changelog history
v0.51 1-november-2010
- Finally beat the reload issue with SenseUI, it should work alot better now
v0.5 12 august 2010
- Corrected WorldClock bottom slider icons
- update HTC Camera to support more resolutions and moto recording.
- Changed Motorola VideoCamera & VideoRecorder to work with HTC framework for optimal use of Moto Camera.
Changed Moto Gallery for proper playback of your recordings.
- SDCard is now always "on", so you will notice status is "0 bytes" when you connect to pc. No conflict with wifi anymore.
- Apps2SD support, EXT2 supported.
Use G.O.T recovery or other application to partition your SDCARD Partition no. 2 should be EXT2 formatted
(G.O.T will do this automatically)
- Apps2SD remaining space can be seen in settings -> SD & Phone storage. Look under "Internal Phone storage" which is your EXT2 partition.
- optimized internal storage space. Most apps are now in /system. leaving your with 171MB free internal storage on your milestone.
- WIPE is 100% supported but you loose the following apps, if you do.
(Dock , GreekIME , Maps , MotoCarDock , PersonalPortal , VSuiteApp , QuickOffice , teeter )NOT SOLVED
- Reloading of Rosie (HTC Launcer)
Reason for not fixing it is that Motorola Milestone simply do not have enough memory for HTC SenseUI to run stable with only 256MB.
the launcher is very memory hungry for all its plugins and graphics.. so sorry, no fix, unless you add 256MB more memory to your phone.
- Bluetooth headset
v0.42 29 july 2010 (MotoSensev042-update-nosign.zip - attached to this post at the bottom) (type: nosign-update.zip)
build.prop correction (hopefully solves too many sense restarts)Keyboard light enabledHTC Camera fix (5M pixel)
OLD REVISION DATA DELETED, OBSOLETE and not worth writing anymore
WARNING: Use this image at your own risk and i take no responsibility if
you brick your phone.. Image has been tested on a UK milestone and works fine if all files in ADB recovery image is used.
woah, nice work buddy. just got a question, if i apply this rom to my North American Milestone, do i lose the ability to access 3g/hspa network from rogers?
is gps working
i got one guy on IRC from Canada(im from europe, so im not sure on networks you got overthere), he tried it, and it works fine for him
You should try to only flash the system+data image of it, as the cust.img contains telephone info, which might be what you need to keep.
GPS is not working atm..
im new to the motodroids , will this work on the motorola droid or just the milestone ? ive had the droid eris so im not sure if there is a difference between the droid and milestone, sorry for the dumb question,
tazzpatriot said:
im new to the motodroids , will this work on the motorola droid or just the milestone ? ive had the droid eris so im not sure if there is a difference between the droid and milestone, sorry for the dumb question,
Click to expand...
Click to collapse
there is already a senseui for Droid, look for Zeusdroid they made that image.
Dexter_nlb said:
there is already a senseui for Droid, look for Zeusdroid they made that image.
Click to expand...
Click to collapse
ok ill google it to see if i can find it , it is much easier to find eris roms , ive only had this moto droid for to dayz and im lost lol
edit well i found it but it doesnt look like its very functional , if its the one i found
tazzpatriot said:
edit well i found it but it doesnt look like its very functional , if its the one i found
Click to expand...
Click to collapse
Porting is no easy task, when its not about development, and zeusdroid actually do have some customized wireless driver.
But i managed to use the existings drivers from Milestone..
And im probably not going to do programming to make the port perfect, as that not so easy, although i got some experience.. but none within driver programming.
im really happy with the progress dext3r, this is awesome.
just curious, any ETA for GPS fix?
gemini002 said:
is gps working
Click to expand...
Click to collapse
ive just tried to fix this, and GPS will be working in the next release.
as it works now
Dexter_nlb said:
Porting is no easy task, when its not about development, and zeusdroid actually do have some customized wireless driver.
But i managed to use the existings drivers from Milestone..
And im probably not going to do programming to make the port perfect, as that not so easy, although i got some experience.. but none within driver programming.
Click to expand...
Click to collapse
i know , ive ported some roms for the eris , i understand its not easy to make it all work, trust me im not disrespecting any1
crap need gps gunna wait until next update fak really miss sense ui
if i install this rom what happend to my apps also i have app2sd applied is this gunna be a problem???
Dexter_nlb said:
ive just tried to fix this, and GPS will be working in the next release.
as it works now
Click to expand...
Click to collapse
awesome pls release this on the weekend would love to try it out also if this is htc sense ui does it have flash lite and if it does have flash lite would the 10.1 flash that works for 2.1 roms work with this...
SplitSnake said:
im really happy with the progress dext3r, this is awesome.
just curious, any ETA for GPS fix?
Click to expand...
Click to collapse
if you know your way on a few linux commands,
then you're welcome to make it work yourself.
1 . copy the /system/lib/libgps.so from the original milestone 2.36.0 image.
2. flash motosense image.
3. mount /system
and copy libgps.so into the flashed image into /system/lib
and GPS works after a reboot.. So fixed!
of course all done from adb shell.
gemini002 said:
awesome pls release this on the weekend would love to try it out also if this is htc sense ui does it have flash lite and if it does have flash lite would the 10.1 flash that works for 2.1 roms work with this...
Click to expand...
Click to collapse
10.1 for 2.1 senseui roms are not real, it just looks like 10.1,
but the flashlite already reports that number.
and yes, flashlite works fine. tested on a few flash websites.
I have a Telus Milestone and I will consider trying this ROM at some point.
Just to crosspost from the other thread... in another thread I was told the following. Could be useful for keeping 3G.
DAGr8 said:
cmstlist , there is an easy way to retain your baseband just flash the HK sbf , then , copy paste these files and make sure you set the permissions correctly .
Probably safest to do via adb if you dont make sure you reboot ...
for the 3G baseband Hack/Swistch it 5 files from /system/etc/motorola/bp_nvm_default
File_Audio , File_Audio2 , File_GSM , File_Seem_Flex_Tables , generic_pds_init
Click to expand...
Click to collapse
So perhaps if you want to try Motosense on your Telus Milestone, then you should backup these 5 files (and take note of the permissions) before flashing the nandroid image. Then afterwards if 3G doesn't work on the Motosense image, restore the same 5 files.
Ok I wasn't able to flash only certain parts of the nandroid backup so what I did was make 1) a full nandroid backup of the Thai firmware (leaked from GOT) on my Telus Milestone unlocked for Fido, 2) a partial nandroid backup using the options --backup --nodata --nocache --nosystem
Then 3) I flashed all of the motosense backup. Trying a first boot. Will report on whether my NAM 3G is gone.
All I get after the M boot logo is a black screen, followed by a force close notification for system. Nothing else comes up. Long-press Home and I get no recent applications. Oh wait - spoke to soon! Wow, just got the HTC lock screen. Unlocked and now I have the setup screen. Asks me to insert SIM to place calls as if I don't have one inserted. My only option seems to be to press "Skip". Okay, home screen loading up now after the tutorial.
So yeah it's not seeing any phone service and I get "Unable to start Wi-Fi". I'm going to try a second reboot. This time the Droid eye shows up promptly (BTW this is very odd to see because Milestones don't usually have that animation). The phone boots up considerably faster than on the Motorlola firmware. *This* time, I do see cell service. In fact I just got a text message. Wait it just dropped again.
Trying to search for network operators. None showing. Strange! It does see wifi though this time. As the OP implied, DHCP not coming through. Meanwhile my Fido service just came back... VERY weak. Dropped again. Normally both EDGE and 3G are quite strong at my apartment so it's odd. Is it possible this ROM has weaker RF somehow?
Ok trying to set up the APN. Noticing the keyboard doesn't light up. APN set up but still no service. Reboot #3: Yes, wifi works now. Mobile network still very weak. Briefly connected to mobile data and it was EDGE. Test phone call fades in and out. Maps manages to wifi-geolocate me.
Alright, so I'm obviously having connectivity problems and only getting 2G. Let's try flashing back the partial I took from the Thai firmware. To be continued next post.
Okay! Flashed back my partial backup from Thai 2.1. Rebooting. Droid eye comes up, glares at me a couple times, back to the homescreen. Connects to Fido. Disconnects, connects again. I am still connected via EDGE, not UMTS. I try going to *#*#4636#*#* and selecting WCDMA only - no dice.
Alright well this has been fun. But obviously I need my phone service to work so this ROM is not for me. Despite having dutifully pasted the info up above about the 5 files to backup... I neglected to do so. So it's back to the full nandroid of my Thai firmware. But one thing for sure, Sense is very pretty!
Before doing this, I made one attempt to install Superuser.apk using the app installer, and then to install Root Explorer. Root Explorer was unable to get root. Maybe if I installed Superuser via OpenRecovery it'd be happier.
Okay back to normal. Goodbye for now Sense!
Backup restored successfully. I used Root Explorer to back up the 5 files in question to SD. Then I restored MotoSense one more time, and before even booting it up the first time I applied root from OpenRecovery. This time it booted much faster. (Is there any way the stock ROM can be hacked to boot this fast? Wow.)
Again, wifi fails to start on boot #1; succeeds but no DHCP on boot #2; works on boot #3. Signed into my Google account and installed Root Explorer (previously purchased). This time Superuser pops up like it should and we're in. I entered Airplane mode. I pasted in the 5 backed up files from the Thai firmware to /system/etc/motorola/bp_nvm_default after mounting read/write. Then I made sure to fix the permissions. Rebooted without exiting airplane mode.
After reboot I disabled airplane mode. Hey, FULL SIGNAL BARS! I did it. But now it's telling me unable to start wi-fi. Let me add in the APN next. Done.
YES! The little H pops up. I'm getting 3G data! But as soon as the icon pops up, it drops out again. In any case I know I'm connected to UMTS because my cell tower ID in Maps > More > About is 1957869 which is my local UMTS tower. Test phone call is *much* clearer and signal isn't dropping anymore. One more reboot.
On the next reboot, wifi is back. Upon disabling it, the lovely "H" shows up and then flits down to "3G". Testing in browser... hmm nope. Something still missing, don't know what. One more reboot, trying again. Internet works on wifi, but not on HSPA (even though the 3G/H icon comes up).
Sanity check: Dialed *#*#4636#*#*, Phone information. Run ping test.
Ping IpAddr: Fail: IP addr unreachable
Ping Hostname (www.google.com): Fail: Host unreachable
One more sanity check: Switched to GSM only, verified in Maps>About that it's connected to a 2G cell ID (57322). Full signal bars, good call quality. So swapping the files improved both 2G and 3G voice performance.
Since I had a bit more success with this approach, I'm saving a backup for future reference, and on my rare moments of idle time I'll play with it again. But back to stock for now.
Hello,
I am using CM-10.1 RC1 on my rooted and CWM smartphone xt925 which I installed
wiping data, cache et Dalvik before and after the flash. Beforehand I used one
07/14 Skrilax's nightly which didn't create any problem. When I switched over to
August's nightlies, I started having problems of connection to the network
(france SFR). What is happening : A pop-up message in the top left of the screen
tells me "the limited access has been modified", then I am asked to enter my pin
of the sim card. In this moment I loose the connection to the network even when
the signal is strong enough with 3 or 4 level indicated. I think the same thing
happened with the GPS. I precise there wasn't system reboot and after entering
my pin code everything works well, I find the actual application where I left
it.Exactly the same problem happened with the RC1 and the CM-10.2.
THX for giving me any hints on solving this problem. If in can't find the
solution, I would appreciate if someone can point out to me the version of 07/14 and around this date
Skrilax nightly so that I can re-install it.
Hey there, first post and the search function wasn't working so if this problem has been posted elsewhere just let me know.
I just flashed the Sept. 28 AOKP for the A2 along with 4.3 GAPPs and everything seems to be working swimmingly...
Except the mobile data.
I've enabled and disabled data, enabled and disabled airplane mode. Reflashed the firmware and GAPPs and still the data doesn't seem to want to work. I'm getting 5 full bars and for whatever reason it just won't connect.
Anybody else had issues like this?
sammanzhi said:
Hey there, first post and the search function wasn't working so if this problem has been posted elsewhere just let me know.
I just flashed the Sept. 28 AOKP for the A2 along with 4.3 GAPPs and everything seems to be working swimmingly...
Except the mobile data.
I've enabled and disabled data, enabled and disabled airplane mode. Reflashed the firmware and GAPPs and still the data doesn't seem to want to work. I'm getting 5 full bars and for whatever reason it just won't connect.
Anybody else had issues like this?
Click to expand...
Click to collapse
You have to manually put in the APN 's for the ROM
Goto system settings mobile networks Access Point Names and manually input the settings depending upon your carrier the setting will differ...
Google your carrier specific APN settings and input them it should do the trick....:laugh:
darth_nihar said:
You have to manually put in the APN 's for the ROM
Goto system settings mobile networks Access Point Names and manually input the settings depending upon your carrier the setting will differ...
Google your carrier specific APN settings and input them it should do the trick....:laugh:
Click to expand...
Click to collapse
You are the best! Post won't let me change title to solved just yet, but for all intents and purposes my data problem is fixed! :laugh:
sammanzhi said:
You are the best! Post won't let me change title to solved just yet, but for all intents and purposes my data problem is fixed! :laugh:
Click to expand...
Click to collapse
Glad to help a fellow A2 owner ........:laugh:
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.
------------