Root [ROM] CM 10.1 preview

[tdm]

This may be due to the USB composition changes. We need to investigate further.

Wait that doesn't make sense lol. My brain must be fried today...

 

[phillip_viado]

Camera Works:Front & Back
Camcorder Works:Front & Back=720p and 1080p
Sms Works:send and receive
MMS Works:send and receive
Video Playback works
USB Mass Storage Works: had to go into storage settings, its not on by default
Hardware button works

 

[Yoinx]

Something weird with the Mobile Data toggle (not the LTE one) in the notification power widget, it works fine when Wifi is off, but when Wifi is on it doesn't toggle the first time, although it does vibrate and data turns off, then if you press it again, it toggles off but the data actually turns back on. Then if you turn Wifi off, the data toggle turns back on, since data is already on. Hopefully that makes sense.

I think that this may be a display issue for the toggle. As if the toggle isn't really sure what to do while wi-fi is on (really it should probably just gray out and reset to the data connection status when wifi drops)

As I understand, android is supposed to disconnect your mobile data in the background when wifi connects, then reconnect it when wifi drops. As long as wifi is connected, that toggle really shouldn't do anything. Then when wifi drops the data connection is returned.

If you connect wifi with data off, you can turn it on with that toggle and it will stay on after you disconnect wifi. If you have data on when you turn wifi on, the toggle won't turn it off.

You can watch the gprs field change from connected/disconnected while toggling to match this. When you have data on with wifi, clicking it doesn't affect the field even though the toggle does toggle after the second tap. With data off when wifi connects, the toggle will briefly connect data then drop (as it's on wifi) though the toggle stays lit. Then connect your data when wifi drops.


Hopefully, that wasn't confusing and was somewhat on the mark >.>

 

[Yoinx]

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.

Sent from my LG-VS920 using Tapatalk 2

Can't reproduce on pre3.


I hate posting new replies behind myself on a forum... But unsure if each issue should be a new post or not.

Pandora: device model android-vs920 unsupported. Worked fine in q-cm10.1

 

[tdm]

Can't reproduce on pre3.


I hate posting new replies behind myself on a forum... But unsure if each issue should be a new post or not.

Pandora: device model android-vs920 unsupported. Worked fine in q-cm10.1

I was afraid of that.

I'll need to adjust the build properties to use i_vzw instead of vs920.

 

[ortrigger]

Sorry I haven't been very active in helping here. I did want to chime in and say thanks to everybody for making this happen.

 

[Yoinx]

I was afraid of that.

I'll need to adjust the build properties to use i_vzw instead of vs920.

Is there some requirement with the CM guys to use something different?

I just checked my stock ICS nandroid, and the stock build.prop used i_vzw too.

*edit*

Changing
ro.build.product=i_vzw
ro.product.device=i_vzw

Allowed me to get into Pandora. Might be the only two that need changing.

 

[tdm]

Is there some requirement with the CM guys to use something different?

Well, CM chose to name their directories p930 and su640 for the other two supported iproj models. So I'm naming mine vs920 to follow suit. The directory name in the build tree is linked with some of the build properties, so having them inconsistent is a bit of a mess. This is why I named my iproj directories i_atnt, i_skt, and i_vzw. They match the build properties from the stock ROMs.

 

[Nokoko]

I think that this may be a display issue for the toggle. As if the toggle isn't really sure what to do while wi-fi is on (really it should probably just gray out and reset to the data connection status when wifi drops)

As I understand, android is supposed to disconnect your mobile data in the background when wifi connects, then reconnect it when wifi drops. As long as wifi is connected, that toggle really shouldn't do anything. Then when wifi drops the data connection is returned.

If you connect wifi with data off, you can turn it on with that toggle and it will stay on after you disconnect wifi. If you have data on when you turn wifi on, the toggle won't turn it off.

You can watch the gprs field change from connected/disconnected while toggling to match this. When you have data on with wifi, clicking it doesn't affect the field even though the toggle does toggle after the second tap. With data off when wifi connects, the toggle will briefly connect data then drop (as it's on wifi) though the toggle stays lit. Then connect your data when wifi drops.


Hopefully, that wasn't confusing and was somewhat on the mark >.>

If you check the Mobile networks menu after pressing the toggle the first time when Wifi is on it shows data is off, even though the toggle shows it's on. I understand the data disconnects when wifi connects, I just like to leave it off most of the time and the toggle isn't accurately showing whether it's on or off. When the toggle does toggle off after the second tap, if you check the data menu it's actually turned back on.

Again, it fixes itself when wifi is turned off, and the toggle either turns on or off to accurately show whether data is on or off.

It worked fine on CM10.1, and not really a big deal just a weird quirk.

 

[Yoinx]

Gotcha. Wasnt trying to step on your toes or anything. Just figured I'd try a guess at what might cause it. Also, that it was able to be reproduced.





Sent from my LG-VS920 using Tapatalk 2

 

[phillip_viado]

hey i just noticed that there's no delay when you unlock it anymore! YAYY!

 

[Nokoko]

Receiving and making phone calls is working fine.
In-call volume is good and they didn't complain about not being able to hear me.
Speaker phone works.

 

[death2all110]

Since the v8 was a minor update and i dont see any mention of radio/signal improvements I doubt the baseband changed. They don't change on every update.

 

[Nokoko]

Also downloaded My Verizon from the Play Store and opened it and logged in, so does that count for the Verizon Apps Play Store compatibility? It's the only one I've ever used...

 

[Yoinx]

Also downloaded My Verizon from the Play Store and opened it and logged in, so does that count for the Verizon Apps Play Store compatibility? It's the only one I've ever used...

Think they rolled their VZW apps all into that one. You get the data widget, my verizon and all that in one. It used to be multiple apps if I recall correctly. Data widget was fine, and could log in here as well.

The Verizon Fios Remote app also works.

The only other verizon apps I can think of is the one that they offer for their NFL package, but it's not free. As well as the tether app they bundle with the metered bandwidth plans now (thank you FCC). But, that one doesn't matter on custom roms anyway


Also, Netflix crashed the first time I tried to play a video. Works fine after that one glitch.

 

[azoller1]

hey tdm are you still working on doing aosp builds?

 

[beddybeezy]

My gps still doesn't get a lock and i wonder if there is a way to get hdmi working again?

 

[1linuxfreak]

Since the v8 was a minor update and i dont see any mention of radio/signal improvements I doubt the baseband changed. They don't change on every update.

V8 baseband is the same, no change.

 

[tdm]

hey tdm are you still working on doing aosp builds?

I work on aosp41 here and there. Still haven't figured out the front camera issue, which is bugging the heck out of me.

I got as far as cloning aosp42 but haven't even tried building it yet.

 

[tdm]

My gps still doesn't get a lock and i wonder if there is a way to get hdmi working again?

HDMI, as in through an MDP cable? That doesn't work? I'll need to note that in the OP, I'm pretty sure it is supposed to work. I've heard it does work on CM's P930 ROMs.

 

[Uzephi]

I can confirm about lower signal being visual bug only. I drive around a mountain to and from work daily. Tried CM10 and CM10.1.

I usually get 1-2 bars when driving around Camelback Mountain on CM10. in CM10.1 it was at 0 bars the whole time but streaming tunein didn't lose stream at 65kbps AAC stream the whole 10mins drive around the mountain.

Edit: forgot about the call my wife made to me on my way home today. No interference. (We all know 0 bars should at least drop some audio)

Edit 2: wired hands-free works on both ends, no audio or mic issues.

 

[Yoinx]

* Bluetooth: music.
- Works fine through Apollo to windows 7. I'm assuming this is the bundled app, since I've never seen it before. However, double twist wouldn't work to play through to the pc speakers... Could be a problem with that app though or something with my settings for it, it's been finicky for me lately anyway.


* Media playback audio.
- MP3 Plays back fine. 192bitrate



* Proper WiFi MAC.
* Proper Bluetooth MAC
- I can't find either of these recorded on the device anywhere. Short of reverting to a previous rom and comparing, how would you verify that these are being reported correctly?

* Proper Baseband string.
- Not sure how you would verify that the one that is reported is correct.


* Deep sleep.
- CPU spy shows that my phone *is* entering deepsleep. Will have to let it run for at least a day thoguh to see if the amount of deep sleep seems reasonable.

* USB computer connection: MTP.
* USB computer connection: PTP.
- I'm not 100% sure how to tell which mode the phone is in, or how to switch it... Right now It's connecting as LG-VS920 > SD card and shows the phone's info through My computer. I believe that this is MTP, as I'm sure it's not Mass Storage. Can't find anywhere to change it in the rom though.

*Edit*
Pre 3 is defaulting to MTP mode for me. Works fine as far as copying files back and forth, I dont really have anything setup to sync to it as an MTP device. I found where to change the mode (Settings>Storage>Menu > USB Computer Connection). Changing to USB Mass Storage works fine for me as well.

 

[Yoinx]

My gps still doesn't get a lock

Actually... I'm not getting a GPS lock either. Testing using GPS Status. I prefer this over google maps, as that can be misleading since it uses multiple methods to get a position. As far as it shows, it's not seeing a single satellite.

Here's a short logcat, not worth using pastebin. I don't see any errors pertaining to anything but admobs.


I wrapped the code tags in hide tags so that the thread doesn't get all distorted from it.

Spoiler

[HIGH]--------- beginning of /dev/log/system

W/BackupManagerService( 527): dataChanged but no participant pkg='com.android.providers.settings' uid=10040

--------- beginning of /dev/log/main

D/libloc ( 527): loc_eng_init entering

D/GpsLocationProvider( 527): set_capabilities_callback: 7

D/libloc ( 527): loc_read_gps_conf: using /etc/gps.conf

D/RPC ( 527): 3000008c:00050000 sending call (XID 562).

D/RPC ( 527): 3000008c:00050000 received REPLY (XID 562), grabbing mutex to wake up client.

D/RPC ( 527): 3000008c:00050000 call success.

D/libloc ( 527): loc_eng_init created client, id = 2

D/libloc ( 527): loc_eng_ni_init: entered.

D/libloc ( 527): loc_eng_set_server, type = 1, hostname = supl.google.com, port = 7276

D/libloc ( 527): loc_eng_set_server, addr = supl.google.com:7276

D/libloc ( 527): loc_eng_ioctl called: client = 2, ioctl_type = RPC_LOC_IOCTL_SET_UMTS_SLP_SERVER_ADDR

D/libloc ( 527): loc_eng_deferred_action_thread started

D/libloc ( 527): loc_eng_deferred_action_thread. waiting for events

D/BluetoothAdapterService(1087891472)(13461): getState(): mAdapterProperties: com.android.bluetooth.btservice.AdapterProperties@40d7f9b0

D/RPC ( 527): 3000008c:00050000 sending call (XID 563).

D/RPC ( 527): 3000008c:00050000 received REPLY (XID 563), grabbing mutex to wake up client.

D/RPC ( 527): 3000008c:00050000 call success.

D/RPC ( 527): 3000008c:00050000 received CALL.

D/RPC ( 527): 3000008c:00050000 dispatching RPC call (XID 974, xdr 0x1259d50) for callback client 3100008c:00050001.

D/libloc ( 527): loc_eng_ioctl result: client = 2, ioctl_type = RPC_LOC_IOCTL_SET_UMTS_SLP_SERVER_ADDR, RPC_LOC_API_SUCCESS

D/RPC ( 527): 3100008c:327681 sending RPC reply (XID 974)

W/InputMethodManagerService( 527): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@4157e0e8 attribute=null, token = android.os.BinderProxy@41285828

I/ActivityManager( 527): START u0 {act=com.anddoes.launcher.ACTION flg=0x10000000 cmp=com.anddoes.launcher/.Launcher bnds=[296,1164][424,1276] (has extras)} from pid 919

I/ActivityManager( 527): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.eclipsim.gpsstatus2/.GPSStatus} from pid 919

D/libloc ( 527): loc_eng_set_position mode, client = 2, interval = 1000, mode = 1

D/libloc ( 527): loc_eng_ioctl called: client = 2, ioctl_type = RPC_LOC_IOCTL_SET_FIX_CRITERIA

D/RPC ( 527): 3000008c:00050000 sending call (XID 564).

W/SensorFusion( 527): enable(3), EN(1, 0, 0, 0, 0), mEnabled(9), CON(9, 8, 8, 0, 0)

D/RPC ( 527): 3000008c:00050000 received REPLY (XID 564), grabbing mutex to wake up client.

D/RPC ( 527): 3000008c:00050000 waiting for XDR input buffer to be consumed.

D/RPC ( 527): 3000008c:00050000 call success.

D/RPC ( 527): 3000008c:00050000 received CALL.

D/RPC ( 527): 3000008c:00050000 dispatching RPC call (XID 975, xdr 0x1259d50) for callback client 3100008c:00050001.

D/libloc ( 527): loc_eng_ioctl result: client = 2, ioctl_type = RPC_LOC_IOCTL_SET_FIX_CRITERIA, RPC_LOC_API_SUCCESS

D/libloc ( 527): loc_eng_start called

D/RPC ( 527): 3100008c:327681 sending RPC reply (XID 975)

D/RPC ( 527): 3000008c:00050000 sending call (XID 565).

D/libloc ( 527):

D/libloc ( 527): Event RPC_LOC_EVENT_PARSED_POSITION_REPORT (client 2)

D/libloc ( 527): Session status: RPC_LOC_SESS_STATUS_ENGINE_LOCKED Valid mask: 0x1

D/libloc ( 527): Latitude: 0.0000000 (intermediate)

D/libloc ( 527): Longitude: 0.0000000

D/libloc ( 527): Accuracy: 0.0000000

D/libloc ( 527): loc_eng_deferred_action_thread signalled

D/libloc ( 527): loc_eng_process_loc_event: 2

D/libloc ( 527): loc_eng_deferred_action_thread. waiting for events

D/RPC ( 527): 3000008c:00050000 received REPLY (XID 565), grabbing mutex to wake up client.

D/RPC ( 527): 3000008c:00050000 waiting for XDR input buffer to be consumed.

D/RPC ( 527): 3000008c:00050000 call success.

D/RPC ( 527): 3000008c:00050000 received CALL.

D/RPC ( 527): 3000008c:00050000 dispatching RPC call (XID 976, xdr 0x1259d50) for callback client 3100008c:00050001.

D/RPC ( 527): 3100008c:327681 sending RPC reply (XID 976)

W/SensorFusion( 527): setDelay: delay(200000000) for other(2)

W/SensorFusion( 527): setDelay: delay(30000000) for other(2)

W/SensorFusion( 527): setDelay: delay(66667000) for other(0)

W/SensorFusion( 527): setDelay: delay(10000000) for other(0)

W/SensorFusion( 527): enable(1), EN(1, 1, 1, 0, 0), mEnabled(11), CON(11, 10, 8, 0, 0)

W/SensorFusion( 527): setDelay: delay(200000000) for other(1)

W/SensorFusion( 527): setDelay: delay(200000000) for other(1)

W/SensorFusion( 527): enable(2), EN(1, 1, 1, 0, 0), mEnabled(15), CON(15, 10, 12, 0, 0)

W/SensorFusion( 527): setDelay: delay(200000000) for other(3)

W/SensorFusion( 527): setDelay: delay(10000000) for other(3)

V/PhoneStatusBar( 754): setLightsOn(true)

D/dalvikvm(15077): GC_FOR_ALLOC freed 862K, 48% free 5672K/10828K, paused 20ms, total 21ms

I/dalvikvm-heap(15077): Grow heap (frag case) to 7.051MB for 1401872-byte allocation

D/dalvikvm(15077): GC_CONCURRENT freed 50K, 36% free 6991K/10828K, paused 4ms+2ms, total 29ms

D/dalvikvm(15077): WAIT_FOR_CONCURRENT_GC blocked 22ms

D/dalvikvm(15077): WAIT_FOR_CONCURRENT_GC blocked 21ms

E/Ads (15077): JS: Uncaught ReferenceError: AFMA_getSdkConstants is not defined (http://media.admob.com/:1)

E/Web Console(15077): Uncaught ReferenceError: AFMA_getSdkConstants is not defined at http://media.admob.com/:1

I/ActivityManager( 527): Displayed com.eclipsim.gpsstatus2/.GPSStatus: +793ms

W/iNemoEngineAPI( 527): delta time 0.010753,11170,15346.379883,65.161949

D/RPC ( 527): 3000008c:00050000 received CALL.

D/libloc ( 527):

D/libloc ( 527): Event RPC_LOC_EVENT_PARSED_POSITION_REPORT (client 2)

D/libloc ( 527): Session status: RPC_LOC_SESS_STATUS_ENGINE_LOCKED Valid mask: 0x1

D/libloc ( 527): Latitude: 0.0000000 (intermediate)

D/libloc ( 527): Longitude: 0.0000000

D/libloc ( 527): Accuracy: 0.0000000

D/libloc ( 527): loc_eng_deferred_action_thread signalled

D/libloc ( 527): loc_eng_process_loc_event: 2

D/libloc ( 527): loc_eng_deferred_action_thread. waiting for events

D/RPC ( 527): 3000008c:00050000 dispatching RPC call (XID 977, xdr 0x1259d50) for callback client 3100008c:00050001.

D/RPC ( 527): 3100008c:327681 sending RPC reply (XID 977)

W/iNemoEngineAPI( 527): delta time 0.010753,10865,11160.889648,89.598595

W/iNemoEngineAPI( 527): delta time 0.010753,10925,11204.830078,89.247223

W/iNemoEngineAPI( 527): delta time 0.010753,10742,11154.480469,89.650078

W/iNemoEngineAPI( 527): delta time 0.010753,10895,11253.049805,88.864799

W/iNemoEngineAPI( 527): delta time 0.010753,11353,11210.940430,89.198586

D/RPC ( 527): 3000008c:00050000 received CALL.

D/libloc ( 527):

D/libloc ( 527): Event RPC_LOC_EVENT_PARSED_POSITION_REPORT (client 2)

D/libloc ( 527): Session status: RPC_LOC_SESS_STATUS_ENGINE_LOCKED Valid mask: 0x1

D/libloc ( 527): Latitude: 0.0000000 (intermediate)

D/libloc ( 527): Longitude: 0.0000000

D/libloc ( 527): Accuracy: 0.0000000

D/libloc ( 527): loc_eng_deferred_action_thread signalled

D/libloc ( 527): loc_eng_process_loc_event: 2

D/libloc ( 527): loc_eng_deferred_action_thread. waiting for events

D/RPC ( 527): 3000008c:00050000 dispatching RPC call (XID 978, xdr 0x1259d50) for callback client 3100008c:00050001.

D/RPC ( 527): 3100008c:327681 sending RPC reply (XID 978)

W/iNemoEngineAPI( 527): delta time 0.010753,11139,11296.389648,88.523857

W/iNemoEngineAPI( 527): delta time 0.010753,10589,11226.190430,89.077415

[/HIGH]

 

[tdm]

* Proper WiFi MAC.
* Proper Bluetooth MAC
- I can't find either of these recorded on the device anywhere. Short of reverting to a previous rom and comparing, how would you verify that these are being reported correctly?

You can't determine your exact MAC addrs except by going back to a stock ROM. But you can tell that the MAC addrs are reasonable if you know what you're looking for. They should probably begin with F0:1C:13, or at least one of the prefixes in this list. Things like all zeros, 01:02:03:04:05:06, and such are obviously bogus.

* Proper Baseband string.
- Not sure how you would verify that the one that is reported is correct.

Doesn't matter too much as long as it has the ZV# part in it.

* USB computer connection: MTP.
* USB computer connection: PTP.
- I'm not 100% sure how to tell which mode the phone is in, or how to switch it... Right now It's connecting as LG-VS920 > SD card and shows the phone's info through My computer. I believe that this is MTP, as I'm sure it's not Mass Storage. Can't find anywhere to change it in the rom though.

Well, it used to be that you went to settings->storage and hit the menu button to pop up a selection of different connection types. I don't see that at the moment, though. Anyone else see how to select between MTP/PTP/USBMS?

 

[Yoinx]

You can't determine your exact MAC addrs except by going back to a stock ROM. But you can tell that the MAC addrs are reasonable if you know what you're looking for. They should probably begin with F0:1C:13, or at least one of the prefixes in this list. Things like all zeros, 01:02:03:04:05:06, and such are obviously bogus.

Gotcha. They both look reasonable. i have 00:aa:70 starting wifi and 00:AA:70 starting bluetooth, the other ocetets are different between the two (good) and look legitimate.

Doesn't matter too much as long as it has the ZV# part in it.

Interesting... On pre-1 I had a value showing for the baseband (see this post). Today it's showing as "Unknown"

Well, it used to be that you went to settings->storage and hit the menu button to pop up a selection of different connection types. I don't see that at the moment, though. Anyone else see how to select between MTP/PTP/USBMS?

I did end up getting that menu. But I had to force it using:

su
setprop persist.sys.usb.config mass_storage
reboot

after I did that it's letting me change it back and forth. That value was in the original build.prop as "persist.sys.usb.config=mtp,adb" Which still exists in my build.prop... Not really sure what roundabout way that setprop fixed it (found it in a thread off google. Either way, that gave me back the ability to change the usb mode....