• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] CM 10.1 preview

tdm

tdm

Android Expert
Official CM support is complete

The first official CM build rolled out on March 4, 2013.

Everything below is outdated. It is only saved for posterity, to remind future users of what we went through.

Official VS920 builds can be found here: CyanogenMod Downloads

Preview Builds for official CM10.1 support

This thread is intended to provide users with preview builds for CM10.1 so that any issues with the code can be found and fixed prior to submitting reviews for official support.

Please keep comments on topic. Try to limit needless chatter and stick to reporting issues with the build. Both success and failure reports are welcomed, particularly if someone has previously reported an issue that can't be reproduced.

How to test

Do a full wipe before installing. It is preferable to format /system also. This ensures everyone is testing the same "clean" bits.

Install gapps immediately after the ROM, prior to first boot. Use gapps-jb-20121212-signed.zip.

Thoroughly test all device specific features. Things that should be checked include:

* Proper WiFi MAC, Bluetooth MAC, and Baseband string.
* Hardware buttons.
* Deep sleep.
* Call, sms, and mms functionality.
* Data functionality, including 3G and 4G/LTE.
* WiFi, Bluetooth, and GPS functionality.
* Audio, including calls, media playback, speakerphone, etc.
* USB computer connection, including MTP, PTP, and mass storage.
* App compatibility, both generic apps and VZW apps available via the Play Store.
* Tethering of all types (USB, WiFi, Bluetooth).
* Front and back cameras, including camcorder.
* Media playback.
* Other suggestions...?

Differences from an official build

* Terminal and vim are not present.

Differences from Quattrimus

* Many of the device specific build.prop entries have been dropped. These will be added back on an as-needed basis.

* USB compositions follow generic devices, not VZW. This may affect how computers see the device, particularly under Windows. The compositions may be tweaked if necessary, depending on feedback.

Known issues

* Pressing the power button while the camera app is active instantly reboots the phone. This is a longstanding known issue in all jellybean ROMs for the iproj family (VS920, P930, SU640).

* Accepting a WiFi-P2P request may instantly reboot the phone. This is specific to the VS920. I have been assured that it will not delay acceptance for CM support. However, I would like to find and fix the issue eventually.

Download

(removed)
Code synced at: Feb 21, 2013, 2:00am PDT.

Changelog and Status

pre1
* Initial release
Result: FAIL: No mobile data.

pre2
* Removed custom install/upgrade/addon scripts, all install stuff should be pristine CM now.
* Added many radio related properties from working Quattrimus CM10.1 build (thanks Nokoko).
Result: FAIL: No mobile data.

pre3
* Fixed apns-conf.xml.
* Removed netmgrd related properties.
* Synced to latest code (no big changes).
Result: FAIL: App incompatibilities

pre4
* Updated build props for app compatibilities.
* Testing results:

* PASS: Proper WiFi MAC.
* PASS: Proper Bluetooth MAC.
* FAIL: Proper Baseband string. [Fix is known and trivial]
* PASS: Hardware buttons.
* PASS: Deep sleep.
* PASS: Basic phone calls.
* PASS: SMS send and receive.
* PASS: MMS send and receive.
* PASS: Mobile data, including 3G and 4G/LTE.
* PASS: WiFi.
* PASS: Bluetooth: music.
* Bluetooth: headset.
* PASS: GPS.
* PASS: Internal mic/speaker.
* PASS: Speakerphone.
* PASS: Media playback audio.
* USB computer connection: MTP.
* USB computer connection: PTP.
* PASS: USB computer connection: mass storage.
* PASS: Play Store generic app compatibility.
* PASS: Play Store VZW app compatibility.
* PASS: Tethering: USB.
* PASS: Tethering: WiFi.
* Tethering: Bluetooth.
* PASS: Camera: back.
* PASS: Camera: front.
* PASS: Camcorder.
* PASS: Media playback video.
​
Reported issues:

* LTE toggle off/on cycle loses 4G (workaround: reset mobile networks preferences).
* HDMI out may be broken.
* Bootloader reboot item may be useless.
* Signal strength indicator may be reporting incorrectly.
* Deep sleep may be interrupted (wake lock issue?)
* Bluetooth may have issues turning off then on again.
​
 
Can't get data to work, the Toggle Mobile Data on the Notification drawer power widget doesn't seem to do anything, shows it's on all the time even when it's off in the mobile networks menu. Didn't even connect as 3g. Network mode is LTE/CDMA/EvDo. Did a full wipe, format/system and flashed Gapps before 1st reboot. Good news, GPS works!

UPDATE: Reflashed, same problem, will try the build.prop changes
 
  • Like
Reactions: tdm
Nokoko said:
Can't get data to work, the Toggle Mobile Data on the Notification drawer power widget doesn't seem to do anything, shows it's on all the time even when it's off in the mobile networks menu. Didn't even connect as 3g. Network mode is LTE/CDMA/EvDo. Did a full wipe, format/system and flashed Gapps before 1st reboot. Good news, GPS works!

Will try reflashing...
Click to expand...

That's surely from the radio properties changes. Are you willing and able to edit /system/build.prop to test some changes? You'll need adb access and, if using Windows, an editor that can save in Unix line endings.
 
No data here either TDM.

Did a full wipe (factory reset, cache, dalvik, format system) then installed the rom and gapps before rebooting. First boot restored everything (besides system items) and rebooted.

On reboot it took A LONG time to get cell signal. Eventually, it did get it though.

Here's a logcat filtered to error level and higher. I'm not sure if filtering it like that helps or hurts though.

Logcat - Pastebin.com

I've set this pastebin to expire after a day.

This is on i_vzw


On a side note... I did have like a hundred or so of this line:
E/Trace ( 2280): error opening trace file: No such file or directory (2)
 
  • Like
Reactions: tdm
Try adding these lines to the end of /system/build.prop:

ro.config.svlte1x=true
ro.ril.gprsclass=10
ro.ril.hsxpa=1
persist.radio.apm_sim_not_pwdn=1

To do this:

1. Backup build.prop and fetch a copy:

adb shell mount -o remount,rw /system /system
adb shell cp /system/build.prop /system/build.prop.orig
adb pull /system/build.prop

2. Edit build.prop and add the above lines at the end

Make sure to use Unix line endings!

3. Save your build.prop and reboot:

adb push build.prop /system
adb shell chmod 644 /system/build.prop
adb shell sync
adb reboot

4. If anything goes wrong, restore like this:


adb shell mount -o remount,rw /system /system
adb shell cp /system/build.prop.orig /system/build.prop
adb shell chmod 644 /system/build.prop
adb shell sync
adb reboot
 
I don't want to de-rail the thead... But a couple quirks I wasn't aware of.

After enabling development options (clicking the build number repeatedly). You have to enable root access for adb right above the debugging section. I also had to restart adb as root "adb root" in order to obtain root access for these commands.

This is again filter to error and higher, but i didnt remove any of the repeat lines this time. Nothing about the phone pops out at me.

Phone signal was obtained quickly. Still no data. Phone info shows mobile network disconnected and Mobile Network Type as "LTE:13"

Interestingly... in the hidden phone menu (I use pimp my rom to get it, but I think its one of those ### numbers) The Cellinfo is showing my CellSignalStrength Lte: ss 25 rsrp:-86 rsrq:-7 rssnr:234
So, its apparently seeing the LTE signal.
GPRS service shows disconnected though.

logcat - Pastebin.com

Sorry for the delay, pastebin was taking forever to post.
 
If those properties don't fix data, I'll need to investigate further. A radio logcat of a working cm10.1 (quattrimus) vs. a non-working one (preview1 plus the properties shown above) would be helpful.
 
I'll send you the radio logcats via PM. Not sure what all's in there and don't want to tie things up trying to make sure nothing personal is in there ;)
 
BTW, anyone who can do without data for the evening please chime in with any other results.
 
I can't place any phone calls either. com.android process keeps crashing when I try to make a phonecall or when an incoming call happens.
 
Oh and any devs out there please diff the working cm10.1 props against this one and try to find the fix. I'm working blind without service.
 
I do remember someone saying that their data wouldn't work if they had it on LTE/CDMA, but on LTE/CDMA/EvDo they did have data. That option is not available here for me but my data worked on LTE/CDMA on quatrimus from the get go.
 
Unless I mis-typed something...

The preview build shows my baseband version as:
VS920ZV7-M8660A-AABQNSZM-3.6.2421

The last quattrimus showed it as:
VS9200ZV7-M8660A-AABQNSZM-3.6.2421

Unless I typo-d it, I had an extra 0 in that first section.
 
Yoinx said:
Unless I mis-typed something...

The preview build shows my baseband version as:
VS920ZV7-M8660A-AABQNSZM-3.6.2421

The last quattrimus showed it as:
VS9200ZV7-M8660A-AABQNSZM-3.6.2421

Unless I typo-d it, I had an extra 0 in that first section.
Click to expand...

Highly doubtful but anything is possible...
 
WiFi works fine.
GPS, accelerometer, magnetic sensor all look to be working.
Screen looks fine.
Mtp seems fine. I assume that this is why it shows as my phone then storage instead of just the storage.
Deep sleep also activates.

Odd thing though. Ran antutu just to strain the CPU a little. I could check the CPU info in CPU spy plus prior to. However CPU 0 was doing all the work cpu1 was prey much not going anything. After running benchmarks the file to check for cpu1 time in state was missing. Seemed odd.

Haven't bothered with tethering since data's out at the moment.

Sent from my LG-VS920 using Tapatalk 2
 
Nokoko went through the build.prop for both ROMs and most likely found the settings that affect data service. I will let her (?) post that info for testing since I'm busy putting kids to bed now.

Note changing radio settings may require a full wipe to "stick".

Thanks Nokoko!
 
I compared the build.prop files but don't know enough about it and don't have time to experiment right now.

There are 2 lines that seem to conflict with others:
ro.telephony.default_network=9
telephony.lteOnGsmDevice=1

The ro.telephony is down farther but =8 (which matches the working CM10.1) and the telephony.lte is also down farther but as telephony.lteOnCdmaDevice=1 (also matches the working one)

And then these lines are in the working CM10.1 but not in the test and look like they might have something to do with it:

ril.subscription.types=NV,RUIM
keyguard.no_require_sim=true
ro.config.svlte1x=true
ro.ril.enable.dtm = 0
ro.ril.disable.power.collapse = 1
persist.radio.add_power_save=1
persist.radio.snapshot_disabled=1
persist.radio.apm_sim_not_pwdn=1
persist.gps.qmienabled=true
ro.telephony.call_ring.multiple=0
ro.ril.transmitpower=true
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=16
persist.data_netmgrd_mtu=1428
persist.cne.UseCne=false


From Tdm:
"Note that changing ro.telephony.default_network and perhaps some others may require a full data wipe to "stick"."
 
tdm said:
pre2 is up, check the OP for details.
Click to expand...

downloading now..

finished download and full wipe, data, dalvik, cache. Installed pre2 then gapps.

Still no data...

Looking at the build.prop from pre1, it looks like it was including some P930 specific settings. I see the board and devices are different from 10.1 beta 3 and 4...

Wifi is working well :) and it does say Verizon wireless with Pre2.
 
  • Like
Reactions: tdm
Noticing that CM 10.1 M1 was released almost exactly a month ago. I wonder if we can get this done before M2 is released? And if so, would it show up as an M2 build, or does a device need some magic blessing to get M status?

Me, I'm anxiously awaiting M3 so my phone can match my car. :p
 
You must log in or register to reply here.
Back
Top Bottom