• 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 said:
If any devs are seeing the baseband Unknown string, please try to track it down. I suspect it's a race condition. The script to set the baseband string is init.qcom.baseband.sh. It should be run on dev.bootcomplete but maybe that's not the correct place. Make sure it actually runs and see if there's anything that interferes with it. I'll do some testing and also try to look for a way to get it set via the RIL (which is the normal way).
Click to expand...

I dunno if I'm off base here... but in init.qcom.baseband.sh you are setting

target=`getprop ro.product.device`

which, returns "i_vzw" on my device.

I'm not sure if I tweaked this in build.prop or if this was part of pre4, but even on a fresh install of pre4 I was getting "unknown" reported.

I modified line 13 to from "vs920" to "i_vzw" pushed it, rebooted, and my baseband reports fine now.

Might it be better to change line 13 to "vs920" | "i_vzw" ) similar to what you're doing on line 10?

Ultimately, my target variable was being set from build.prop but didn't match either case condition in the script. So, the baseband property was never being set.

So now CM10.1 is reporting VS920ZV8-M8660A-AABQNSZM-3.6.2421 exactly as stock did.
 
Yoinx said:
I dunno if I'm off base here... but in init.qcom.baseband.sh you are setting

target=`getprop ro.product.device`

which, returns "i_vzw" on my device.

I'm not sure if I tweaked this in build.prop or if this was part of pre4, but even on a fresh install of pre4 I was getting "unknown" reported.

I modified line 13 to from "vs920" to "i_vzw" pushed it, rebooted, and my baseband reports fine now.

Might it be better to change line 13 to "vs920" | "i_vzw" ) similar to what you're doing on line 10?

Ultimately, my target variable was being set from build.prop but didn't match either case condition in the script. So, the baseband property was never being set.

So now CM10.1 is reporting VS920ZV8-M8660A-AABQNSZM-3.6.2421 exactly as stock did.
Click to expand...

Awesome that's exactly what I submitted to rmcc:

https://github.com/CyanogenMod/andr...mmit/416105473dc9de3afcf25355e5c690feb8b3b6ec
 
hayneskr said:
I thought so as well which is why I mentioned it. The more info the better is what I say :D

Another strange item, after I powered my phone off I tried to turn it back on, still plugged into the charger. I would hold the power button for around 5 to 7 seconds and the LG logo would flash but I did not feel the vibrate that normally accompanies powering on and the screen would flash LG logo again and then display the battery charging screen. Unplugged the charger and it did it again. Tried one more time and the phone vibrated and powered on as normal. I had something similar happen weeks ago so I think it may not be related to this specific rom.
Click to expand...

this has been a common issue on cm10 and the other cm10.1 ... when off and charging it wont turn on... quickest way to get it on is unplug it pull the battery for a second... pop it back in and power it on... after it vibrates you can plug it back in
 
Also,

I just want to pipe in about the "lower signal strength" issue people are having.

I don't know if people are just saying that the bars are showing lower or if they're actually getting less signal.

I would recommend changing your phone from the bars style to display dbm to diagnose this. (settings>system>status bar>signal status style>text)

My living room is maybe... MAYBE... 300-400 feet from my cell tower. I usually sit between -77dbm and -83dbm which really isnt a bad signal. This correlates to full 5 bars in the bar style on this rom.

I'd be interested to see what dbm level people are seeing when they're saying they were getting weaker signal. It's VERY likely that it just needs to be tweaked what dbm levels the bars correlate to. Like I said, I'm usually at about -80dbm average, and i dont see any way this phone is going is going to report much more than that without being duct taped to the front of a cell tower transmitter.

I'm also curious if the people with lower signal strength are actually seeing the same dbm levels between roms and just basing this off the bars.

...just my 2 cents.
 
  • Like
Reactions: tdm
Updated OP with more results and reported issues.

Merge is looking good...

All the device changes are in. The remaining review is for the kernel to switch from ECM to RNDIS. This is not critical, it should only affect USB tethering. If that isn't committed soon, I'll ping rmcc about it.

I've never been involved in a CM device bringup, but it seems to me the only remaining items are for rmcc to add the vs920 device tree, stash the vendor files wherever CM keeps those, and add the device to the internal build servers.
 
Hey Yoinx, what stock nandroid did you flash to get a lock for your GPS? I am also having GPS locking issues and am hoping your method will fix my issues as well.
 
davidkhwang said:
Hey Yoinx, what stock nandroid did you flash to get a lock for your GPS? I am also having GPS locking issues and am hoping your method will fix my issues as well.
Click to expand...

It was a copy of a stock v7 I had.

Cab flash v7 get a lock in GPS test, run the pwnage tool to get back cwm and you should be able to restore a nandroid of your current system (make it before you cab flash).

That's assuming your issue is the same.

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
I just want to pipe in about the "lower signal strength" issue people are having.
Click to expand...

Looks like I'm getting full bars at -80ish db. Which I would expect and 0 bars at -104dbm. While -104 isn't great it still gets 4g and definitely shouldn't be getting reported as no bars.

I don't know enough about changing apks to look at it... But I believe this may be contoured in systemui.apk

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
Looks like I'm getting full bars at -80ish db. Which I would expect and 0 bars at -104dbm. While -104 isn't great it still gets 4g and definitely shouldn't be getting reported as no bars.

I don't know enough about changing apks to look at it... But I believe this may be contoured in systemui.apk

Sent from my VS920 4G using Tapatalk 2
Click to expand...

Actually I've done quite a bit of looking at signal strength and how it relates to the amount of bars shown on this phone, and have done so since I got it last march. I've noticed that 1x reports a stronger signal strength than 3g, and 3g reports a stronger signal strength than 4g when tested in the same spot. What I mean is that if you are standing in the same spot and you're getting say 100dbm of 4g then you are likely to get around 95dbm of 3g and maybe 90dbm of 1x. This also translates into the bar count. Say 85dbm is 3 bars on 3g it might only show 2 bars on 1x and actually a full set of bars for 4g.

I bring all this up because I've seen my 4g signal at over 110dbm and still getting a bar of 4g service. 110 on 3g would probably not even work really. 3g seems to fade away around 105 or so.


I actually only have about 95-100dbm strength of 3g where I live which translates to one or two bars. But this amount of connection strength is sufficient to give me about 1-1.5Mb download speed
 
IMUcarmen said:
I actually only have about 95-100dbm strength of 3g where I live which translates to one or two bars. But this amount of connection strength is sufficient to give me about 1-1.5Mb download speed
Click to expand...

Yeah. That's why I think is displaying the incorrect number of bars based on signal strength. The dBm to bar loss should start at like-75 to -80 and drop 1 bar per 8-10 db loss.

ie:
-75 to -83 should be 5 bars
-84 to -92 should be 4 bars
-93 to -101 should be 3 bars
-102 to -110 should be 2 bars
-111 to -119 should be 1 bar.
at-120 you have no signal and should be 0 bars

By my estimation anyway. This would make the signal bars more accurately match your real world signal.

As far as 1x 3g and 4g having different signal strengths, you're right. But that is due to the difference in frequencies/bandwidth that the cell signal is using. The phone should only report the mode you're currently in and switch been then one the next higher signal type gets to weak. I have no idea where this cut over happens though. But it shouldn't really affect the correlation between dbm and bars.

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
I dunno if I'm off base here... but in init.qcom.baseband.sh you are setting

target=`getprop ro.product.device`

which, returns "i_vzw" on my device.

I'm not sure if I tweaked this in build.prop or if this was part of pre4, but even on a fresh install of pre4 I was getting "unknown" reported.

I modified line 13 to from "vs920" to "i_vzw" pushed it, rebooted, and my baseband reports fine now.

Might it be better to change line 13 to "vs920" | "i_vzw" ) similar to what you're doing on line 10?

Ultimately, my target variable was being set from build.prop but didn't match either case condition in the script. So, the baseband property was never being set.

So now CM10.1 is reporting VS920ZV8-M8660A-AABQNSZM-3.6.2421 exactly as stock did.
Click to expand...

I just modified line 13 to say "vs920" | "i_vzw" ) and now I have a baseband showing in pre4. Thanks :)
 
  • Like
Reactions: tdm
OK, so I set my text notification to a different sound but its not playing the notification... only vibrating. At first I thought there was a bug in separate notifications, but then I remembered something about mp3's not playing. Has that issue been addressed yet?
 
reeseboy said:
OK, so I set my text notification to a different sound but its not playing the notification... only vibrating. At first I thought there was a bug in separate notifications, but then I remembered something about mp3's not playing. Has that issue been addressed yet?
Click to expand...

I use zedge for my tones and it only uses mp3s. Haven't had an issue with any not playing yet. Are you having a problem setting specific notification sounds for certain events? Or just in general?

Sent from my VS920 4G using Tapatalk 2
 
reeseboy said:
Set a system sound without an issue. Just the MP3 I'm having an issue with.
Click to expand...

So just setting the mp3 from within the testing app? I don't see anywhere within the rom menus for setting a sound specifically for text messages.

Of it's in the texting app. Is it the default one?

Just trying to get enough info to try and reproduce to see if it's a shared issue ;)

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
It was a copy of a stock v7 I had.

Cab flash v7 get a lock in GPS test, run the pwnage tool to get back cwm and you should be able to restore a nandroid of your current system (make it before you cab flash).

That's assuming your issue is the same.

Sent from my VS920 4G using Tapatalk 2
Click to expand...

Cab restore never works on my bootcamp windows 7 partition for some reason. Is there an alternative, or am I stuck with no GPS.
 
davidkhwang said:
Cab restore never works on my bootcamp windows 7 partition for some reason. Is there an alternative, or am I stuck with no GPS.
Click to expand...

I'd recommend starting a new thread to get cab restore under bootcamp help so s to keep this thread from getting off topic to far.

I don't use s Mac... But it may be worthwhile to try installing windows in a virtual machine like virtualbox and pass USB through to it perhaps.

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
So just setting the mp3 from within the testing app? I don't see anywhere within the rom menus for setting a sound specifically for text messages.

Of it's in the texting app. Is it the default one?

Just trying to get enough info to try and reproduce to see if it's a shared issue ;)

Sent from my VS920 4G using Tapatalk 2
Click to expand...

I think I just figured it out... the MP3 file was damaged in the copy lol. You would think I'd check for that, but apparently not :D
 
You must log in or register to reply here.
Back
Top Bottom