• 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

Received a reply from rmcc re: the app compatibility and device naming issues:

That's a common problem. Overload the product name (TARGET_PRODUCT) in cm.mk
Click to expand...
I played with this for a while before finally figuring out this is part of the long and cryptic PRODUCT_BUILD_PROP_OVERRIDES line. I've never used that before because I've always had the luxury of simply renaming my device trees. But eventually I figured it all out and set the overrides to match our ICS build (took the values from icy fusion, I hope they are accurate).

So I learned something new today. :)

Anyway, I'll put up pre4 sometime tonight. The only change from pre3 wil be for those overrides, which should in theory only affect app compatibility for picky things like Pandora. It's compiling now and I'll probably need to head out before it's done so it may be a while.
 
tdm said:
But eventually I figured it all out and set the overrides to match our ICS build (took the values from icy fusion, I hope they are accurate).
Click to expand...

Just in case, here's the top of a build.prop from a rooted stock ICS nandroid i have.

[HIGH]# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=VS920ZV7.47e5065f
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Tue Jun 19 17:11:50 KST 2012
ro.build.date.utc=1340093510
ro.build.type=user
ro.build.user=yeoncheol.hong
ro.build.host=potato
ro.build.tags=release-keys
ro.product.model=VS920 4G
ro.product.brand=Verizon
ro.product.name=i_vzw
ro.product.device=i_vzw
ro.product.board=I_VZW
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=i_vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=i_vzw-user 4.0.4 IMM76D 47e5065f release-keys
ro.build.fingerprint=Verizon/i_vzw/i_vzw:4.0.4/IMM76D/VS920ZV7.47e5065f:user/release-keys
ro.build.characteristics=default
gsm.version.baseband=APQ8060/MDM9200
# display lge software version
ro.lge.swversion=VS920ZV7
# end build properties
#
# system.prop for i_vzw
#[/HIGH]
 
  • Like
Reactions: tdm
tdm said:
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...

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

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. :confused: Anyone else see how to select between MTP/PTP/USBMS?
Click to expand...

My wifi MAC looks right, f0:1C:13:...
Baseband also looks right.
The menu button in storage works for me? Menu button, USB computer connection, has MTP, PTP, mass storage options.
 
beddybeezy said:
Yes i've tried it on each build still a no go same with gps!
Click to expand...

I get GPS and several others do also. And I know your device is slightly different from everyone else based on the build_id string. So unless there are other reports of GPS issues, I'll blame your oddball firmware...
 
gps works for me.

I wasn't going to install this until I saw phillip say the lock screen delay is gone and he's right...The lock screen delay is not there in this build. Another thing I noticed that is gone is the animation flicker that I reported in the other cm10.1 thread. So thats awesome those two issues are gone now...But I have noticed that this version is not as smooth as the other cm10.1 Perhaps it's because I ran the other at 1674 and this taps out at 1512. I don't know if thats why I see a difference but maybe someone else who ran the other cm10.1 can report what they see.

I've only been running this for 15 minutes so I'll report later if I notice anything else.

Thanks tdm
 
Psuedo Dirty flashed pre-3 back over itself (wiped cache/dalvik, formatted system) didnt feel like going back through restoring everything....

Baseband is reporting right for me now as well. I must have messed it up somehow before, probably changing my build.prop for the two instance of i_vzw. Might have cause some sort of mismatch.

Still not getting a GPS lock though, i must be on the same hardware version as beezy :p

*edit*
Just did a full clean wipe/reinstall. No GPS in GPS Status or GPS Test. So it's gotta be something specific to a certain revision of hardware/firmware. Personally, I don't care much about GPS, for navigation cell/lte triangulation gets you close enough
 
  • Like
Reactions: tdm
IMUcarmen said:
After using this for a little bit longer I can confirm that is definitely not as smooth as the other cm10.1
Click to expand...

There's not a lot of difference between them really. The removal of over clock. Some display driver updates and fixes. Not much else...
 
tdm said:
There's not a lot of difference between them really. The removal of over clock. Some display driver updates and fixes. Not much else...
Click to expand...

Not sure why then other than the clock speed. I'm not complaining though just trying to report what I'm seeing.

Maybe the display driver fixes is what I'm seeing. The lock screen delay and animation flickers are gone but maybe the trade off is slight lag :-P
 
You could try done of the tweaks in pimp my ROM app. Specifically disabling vsync for more fps... Might give you back some snappiness.

Sent from my LG-VS920 using Tapatalk 2
 
pre4 is up. Note devhost was timing out so I uploaded to a different site.

The only change is updated properties for app compatibility based on data that Yoinx provided:

Added:
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=i_vzw TARGET_DEVICE=i_vzw BUILD_FINGERPRINT=Verizon/i_vzw/i_vzw:4.0.4/IMM76D/VS920ZV7.47e5065f:user PRIVATE_BUILD_DESC="i_vzw-user 4.0.4 IMM76D 47e5065f release-keys"

Changed:
PRODUCT_BRAND := Verizon
 
IMUcarmen said:
After using this for a little bit longer I can confirm that is definitely not as smooth as the other cm10.1
Click to expand...

I've been noticing that too, not so much smoothness as speed, just seems a tad bit slower. I never even installed Pimp my ROM on CM10.1 or changed the animation speeds because it was so fast, thinking about it on this one though.
 
I just finished a full wipe and clean install with Pre3 and I this is good stuff!
GPS Status lock in in less than 30 seconds with 4m error.
Lock screen delay is gone just like phillip.
Bluetooth connected with Plantronics HD Pro with no problem, did have a little wierdness with what seemed like an audio notification in the headset. It kept playing every few seconds. Head set was fully charged. I turned bluetooth off then back on and it connected right up is working perfectly.

D/L pandora with no problems and streaming to my bt headset with no errors.
Not sure about the lag everyone else is experiencing but my phone seems quicker and smoother.

D/Ling Pre4 now, but this rom feels like a daily driver. Thanks TDM!

Update: Guess I spoke too soon. Turned BT headset off and plugged into charger. Now BT on phone is off and won't turn back on. D/Ling Pre4 so will wait for d/l to finish then reboot phone to see if bt comes back.

Ok, reboot phone and BT is working and streaming Pandora. Will play some more, I did have some problems with Pandora and the VS920 with gingerbread so who knows.

Turned BT off on phone and it won't turn back on. Looks like there might be problem. anyone else confirm?
 
hayneskr said:
Update: Guess I spoke too soon. Turned BT headset off and plugged into charger. Now BT on phone is off and won't turn back on. D/Ling Pre4 so will wait for d/l to finish then reboot phone to see if bt comes back.
Click to expand...

This happens on my nitro aokp42 also. I think it's an aosp/cm issue. But I haven't verified with official cm yet.

Interesting that you were able to run Pandora on pre3.
 
Dirty flashed pre4.

Still seeing wierdness with BT. After first booting up I turned BT off then back on several times and it seemed ok. Went to Pandora to stream music via BT but BT was off on phone and I could not turn it back on.

All seems to be ok, unless you turn off BT. Tried turning it off with Settings menu, Quick settings and power widget. I did this separately rebooting in between attempts, yet no glory.

Seems that reboot is the only thing that can get BT working again..
 
hayneskr said:
Dirty flashed pre4.

Still seeing wierdness with BT. After first booting up I turned BT off then back on several times and it seemed ok. Went to Pandora to stream music via BT but BT was off on phone and I could not turn it back on.

All seems to be ok, unless you turn off BT. Tried turning it off with Settings menu, Quick settings and power widget. I did this separately rebooting in between attempts, yet no glory.

Seems that reboot is the only thing that can get BT working again..
Click to expand...

moral to the story...don't turn off bluetooth :]

You said that you noticed it being quicker than before. What are you comparing it to? The other CM10.1 or some other rom?
 
Baseband listed properly in pre3 for me but not currently in pre4. I dirty flashed from 3 to 4 so it might be something to do with that...

Edit: Just noticed that powering off does a reboot.
 
  • Like
Reactions: tdm
You must log in or register to reply here.
Back
Top Bottom