[ROM]COLD AS ICE-CM9+Paranoid Android LS670 11/20 ZVD basesband Alpha19

[and_man]

Optimus S
CAI 19E

ZVJ baseband:
radio doesn't work, but i didn't really try to get it working - using the ZVJ baseband was accidental anyway as i intended to convert to ZVD but i missed the 2nd reboot step
all is ok on ZVD

missing icons:
i'll repost if/when i can duplicate this and pull the logs, but i noticed once after a cold start there are no icons in the notification area other than battery and clock and no radios would work (no service) - anyone else experience this?

overall this seems like a really nice ROM - thanks kraven!

 

[and_man]

haven't been able to reproduce this consistently, but regarding the icons going AWOL in the notification area (i.e. all radio toggle icons and such), hopefully this may help...

E/CameraHAL(  459): CameraHAL_GetNum_Cameras:
E/MediaProfilesJNI(  457): native_init
E/MediaProfilesJNI(  457): After native_init lock
E/MediaProfilesJNI(  457): Guru : native_init profiles
E/MediaProfiles(  457): getInstance
E/MediaProfiles(  457): Guru :Else 1
E/MediaProfiles(  457): Guru : quality = 0, index = 1
E/MediaProfiles(  457): Guru : quality = 1, index = 0
E/MediaProfiles(  457): Guru : quality = 0, index = 1
E/MediaProfiles(  457): Guru : quality = 1, index = 0
E/MediaProfiles(  457): getInstance f20c0
E/MediaProfilesJNI(  457): retun sProfiles
E/MediaProfilesJNI(  457): native_init
E/MediaProfilesJNI(  457): After native_init lock
E/MediaProfilesJNI(  457): retun sProfiles
E/PhonePolicy(  457): Could not preload class for phone policy: com.android.internal.policy.impl.PhoneWindow$ContextMenuCallback
E/ExtendedExtractor(  459): Failed to open MM_PARSER_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser.so' not found 
E/ExtendedExtractor(  459): Failed to open MM_PARSER_LITE_LIB, dlerror = Cannot load library: load_library[1120]: Library 'libmmparser_lite.so' not found 
E/CommandListener(  453): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
E/WifiStateMachine(  529): Failed to disable IPv6: java.lang.IllegalStateException: Unable to communicate to native daemon for disabling ipv6
E/ConnectivityService(  529): Ignoring protectedNetwork 10
E/ConnectivityService(  529): Ignoring protectedNetwork 11
E/ConnectivityService(  529): Ignoring protectedNetwork 12
E/MobileDataStateTracker(  529): default: Ignoring feature request because could not acquire PhoneService
E/MobileDataStateTracker(  529): default: Could not enable APN type "default"
E/BandwidthController(  453): runIptablesCmd(): failed /system/bin/iptables -D INPUT -m owner --socket-exists res=256
E/BandwidthController(  453): runIptablesCmd(): failed /system/bin/ip6tables -D INPUT -m owner --socket-exists res=256
E/BandwidthController(  453): runIptablesCmd(): failed /system/bin/iptables ! -i lo+ -I INPUT -m quota2 ! --quota 2097152 --name globalAlert res=256
E/BandwidthController(  453): runIptablesCmd(): failed /system/bin/ip6tables ! -i lo+ -I INPUT -m quota2 ! --quota 2097152 --name globalAlert res=256
E/BandwidthController(  453): runIptablesCmd(): failed /system/bin/iptables ! -o lo+ -I OUTPUT -m quota2 ! --quota 2097152 --name globalAlert res=256
E/BandwidthController(  453): runIptablesCmd(): failed /system/bin/ip6tables ! -o lo+ -I OUTPUT -m quota2 ! --quota 2097152 --name globalAlert res=256
E/BinaryDictionaryGetter(  664): Could not find a dictionary pack
E/ActivityThread(  664): Failed to find provider info for com.android.inputmethod.latin.dictionarypack
E/WindowManager(  529): Window Session Crash
E/WindowManager(  529): java.lang.IllegalArgumentException: Requested window null does not exist
E/WindowManager(  529): 	at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7185)
E/WindowManager(  529): 	at com.android.server.wm.Session.setWallpaperPosition(Session.java:360)
E/WindowManager(  529): 	at android.view.IWindowSession$Stub.onTransact(IWindowSession.java:419)
E/WindowManager(  529): 	at com.android.server.wm.Session.onTransact(Session.java:111)
E/WindowManager(  529): 	at android.os.Binder.execTransact(Binder.java:338)
E/WindowManager(  529): 	at dalvik.system.NativeStart.run(Native Method)
E/WindowManager(  529): Window Session Crash
E/WindowManager(  529): java.lang.IllegalArgumentException: Requested window null does not exist
E/WindowManager(  529): 	at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7185)
E/WindowManager(  529): 	at com.android.server.wm.Session.setWallpaperPosition(Session.java:360)
E/WindowManager(  529): 	at android.view.IWindowSession$Stub.onTransact(IWindowSession.java:419)
E/WindowManager(  529): 	at com.android.server.wm.Session.onTransact(Session.java:111)
E/WindowManager(  529): 	at android.os.Binder.execTransact(Binder.java:338)
E/WindowManager(  529): 	at dalvik.system.NativeStart.run(Native Method)
E/Launcher.Workspace(  691): The screen must be >= 0 and < 1 (was 2); skipping child
E/Launcher.Workspace(  691): The screen must be >= 0 and < 1 (was 2); skipping child
I/ActivityManager(  529): Start proc com.cyanogenmod.settings.device for broadcast com.cyanogenmod.settings.device/.BladePartsStartup: pid=822 uid=1000 gids={1015, 3002, 3001, 3003}
E/DefaultVoicemailNotifier(  786): No voicemails to notify about: clear the notification.
I/Vold    (  450): Device /dev/block/vold/179:1, target /mnt/sdcard mounted @ /mnt/secure/staging
I/ActivityManager(  529): Start proc com.android.exchange for broadcast com.android.exchange/.service.ExchangeBroadcastReceiver: pid=911 uid=10028 gids={3003, 1015}
W/MediaScanner(  651): Error opening directory '/mnt/sdcard/.android_secure/', skipping: Permission denied.

 

[vector84an]

For ZVJ baseband you need the 3 libs from the ZVD to ZVJ patch - libgstk_exp.so, libpbmlib.so, libwms.so (they go in /system/lib/)
http://forums.androidcentral.com/lg...zvj-zvd-zvd-zvj-flashable-zips-optimus-s.html

the patch also contains other things which might be better to remove - apns, audio_policy.conf, some sort of apps2sd script, and a keypad layout.

I think thekraven also mentioned there might be some ril changes you'd want to make in build.conf, but I don't have a link for that handy...


not sure if it's related, but I can say that I've been using ZVJ baseband and getting pretty bad clock lag on the status bar, no matter what kernel I use - system time doesn't seem to actually drift too badly from what I can tell, but the status bar will at times refuse to update to the correct time for a very long time.

 

[vector84an]

(For anyone that has Tasker) I wanted to share a little something that seems to really help my clock lag - in theory with less overhead than ClockSync running every 30s...
(in reality Tasker probably has more overhead... but if this works for other people, a hack to accomplish the same ought to be possible with far less overhead?)

Anyhow, I made a Tasker profile on screen off, set exit task to run a shell script "am broadcast -a android.intent.action.TIME_SET" with root permissions

and my clock lag seems almost as fixed as it is in CM10.1 - occasional lag but updating to the correct time once the screen is on only takes a few seconds, rather than several minutes at times.

(I feel like the CM10.1 builds I've tried push out a correct time faster, but this is a decent improvement imo... and I'm guessing some of that delay is Tasker, then a root shell script, then finally the intent we're looking for? ie a proper built-in hack would probably go faster? but don't mind my musings, I'm a total noob...)


And for those that are particularly interested... as I noted above, my system time doesn't seem to drift too badly - but my status bar time would take several minutes to update, and my lock screen time would stall until turned off and on again (as has been mentioned several times in this thread already, of course). ClockSync set to debug interval fixed the lock screen issue most of the time for me, but generally I would still have to keep my screen on for 30 seconds to get an update to the status bar time.

I'd been playing with Tasker profiles for awhile now, trying to find something better - calling an ntpd sync when leaving screen off worked reasonably well for me, for example, but I wasn't satisfied... then I noticed that fiddling with the (relatively correct) system time would push a (relatively) immediate update to the status bar... a little more research on how intents work and a global broadcast of the time_set intent later... and my clock annoys me far less...


I have NOT extensively tested this yet - but my clock lag was quite consistent (3+ minutes of screen off = clock lag for me) and so far all my short duration tests update very quickly, though I still have ClockSync running every 6 hours, so I'll try to remember to add some commentary on how much my clock is drifting once I've had it running like this for awhile.

I can say that for me at least, different components (different clock widgets, the status bar, and the lock screen, for example) all take differing amounts of time to update when I have this profile running - which can be a bit odd, but everything seems to update within a few seconds.


Update: Does android.intent.action.TIME_SET need root? I changed my task to Send Intent, action=android.intent.action.TIME_SET, target=Broadcast Receiver - seems to work a bit faster?


Another update: This fix breaks my battery / deep sleep stats - best I can tell my phone is still sleeping and waking just fine, but it never registers deep sleeps as lasting more than a few seconds - which I suppose is to be somewhat expected all things considered...
I'd like to figure out how to target just the status bar and lock screen with this intent, or perhaps force an update to battery / cpu state stats before sending out the time_set but I haven't figured out how to do that yet...

 

[leftysrevenge]

Been amazed by this ROM. Fluid and easy to use. However, after resolving my constant reboots with the relatively simple clocking adjustment, I've hit a snag with Bluetooth.

It seems that every time I disable Bluetooth, the ROM restarts. I'm not sure what's causing it but it is infinitely repeatable. Haven't really had any other issues, and the only real solution at the moment is just to leave Bluetooth enabled (haven't checked battery drain yet), but this is obviously not ideal, especially in the case where i need to restart bluetooth capability for some reason.

Thoughts?

Thanks for all the help; this community rocks!
AC

 

[upconvert]

Which kernel are you using? Try some of the other ones. Test 20 works well for me.

Sent from my LG-VM670 using Android Central Forums

 

[_alexkta]

I'm having little to no time lag on 21

Sent from my VM670 using Tapatalk 2

 

[vector84an]

Kernel 21 reads kernel 20 when you install it btw (and 21 is usually the recommended kernel)... but clock lag is a fickle mistress - I thought I had clock lag nailed down with kernel 21 for awhile, maybe it's the fact that I'm using ZVJ baseband though...

As far as Bluetooth issues:
1) "bluesleep fix" - try it (google it, first link, yes, I know it say atrix)
it's silly, just some pointless forced root permissions or some such... I've been flashing it every time recently and it "seems to help" ...


Anyhow, I experienced a variety of issues with Bluetooth, including occasional reboots when toggling Bluetooth off - in an attempt to solve it I went through a pretty good sized sampling of kernels - kernel 40 will probably break Bluetooth for you btw...
I ended up settling on using kernel 39 for sustained use - Bluetooth very rarely crashes unless I repeatedly cycle it, though toggling it will sometimes crash my wifi

Kernels 39 and prior should have working bluetooth (40 contains new bluetooth drivers that afaik no one has managed to get to work?)
Most still crash wifi when turning bluetooth off, and sometimes crash the phone too...



Also, I decided to turn this rom into my daily driver after working out the kinks, and I just finished a new clean rebuild... and I noticed a bit of an oddity with kernel 39...

Seems like I can't get accurate battery stats on a clean build (of Paranoid Android) using kernel 39... all my battery stats on a clean build of kernel 39 look the same as turning on my clock lag fix (invalid deep sleep times) - I previously had working battery stats with kernel 39 on several of my test builds... which generally involved first booting under 21 or 38...

Of course, assuming my understanding of how these things go isn't too terribly flawed... my phone seems to still sleep wonderfully
Currently 15 hour run time so far, battery is at 86%, phone reads ~1 hour of run time - so that's about 14 hours of deep sleep, not 5 minutes?

So I'm not sure how concerned I really am, but y'know... the more you know, or some such...



PS: If you're going to use kernel 39... things might be better on ZVD baseband - I haven't tried, still using ZVJ - but clock lag will probably be an issue...
(clock lag remained an issue for me even with kernel 21 though so... your mileage may vary I suppose?)

Anyhow, I don't know much about Tasker, but if anyone wants to try this fix without Tasker, I think I should be able export a small(ish?) app to accomplish the same thing?
I'll try to post up something a little later...

 

[jayleekay]

You can fix the Bluetooth issue with a different kernel. I just did it recently. However I'm not 100% sure which one I used.
It was either test21 or test40
Sent from my LG-VM670 using Tapatalk 2

 

[leftysrevenge]

Purring like a champ now. Thanks all for the suggestions.

[Edit: I grabbed test39 and so far so good.]

One new minor question: How do I modify the status bar, specifically the Wifi/3G icons? I like that they give realtime up/down traffic, but the dark grey arrows inside the grey/blue is hard to see in some lighting situations. I'd like to make them a white or lighter blue, if possible, just to make it higher contrast.

Thanks again.
AC

 

[vector84an]

I think there's supposed to be some way to do that through themes or some such... but I don't know much about that...

What I can tell you is that you is that they should be in SystemUI.apk - to make changes to it, decompile with apktool, change things, recompile, and drop the compiled versions of the altered files into (a copy of) the original SystemUI.apk (using 7zip or similar zip tool).

for just editing icons, I think you might be able to just pull them out with a zip tool and drop them back in?
but to change xml and such you need to decompile and recompile...

I think it also needs to be zipaligned again after being altered? but most custom roms do that on boot so... might not be something you really need to worry about.

 

[ahagge]

You can fix the Bluetooth issue with a different kernel. I just did it recently. However I'm not 100% sure which one I used.
It was either test21 or test40

I too was suffering from the "lockup/reboot when Bluetooth is turned off" issue with the default kernel included with the ALPHA 19E build. I can confirm that the 9/25 Test 21 kernel fixed the problem for me. I tried the "1/16/03 test kernel 40" from the second post of this thread as well, but it was worse than the stock kernel. It locked up when Bluetooth was turned on, not just when it was turned off.

Thanks for the pointer!

 

[leftysrevenge]

I found and tried a number of methods and finally landed on NinjaMorph from a forum post. Very cool, didn't even need do anything on the computer besides edit the images, which you can still do in the app. Made the changes and it works beautifully. Exactly as I was hoping and a massive improvement over the original theme. Even modified the Bluetooth to be more distinct between active and connected.

So far this is the most impressive ROM I've installed. Can't wait for CM10 to get a little more stable. But I'm loving that I'm still getting life out of my OV this long after I got it.

Cheers!

I think there's supposed to be some way to do that through themes or some such... but I don't know much about that...

What I can tell you is that you is that they should be in SystemUI.apk - to make changes to it, decompile with apktool, change things, recompile, and drop the compiled versions of the altered files into (a copy of) the original SystemUI.apk (using 7zip or similar zip tool).

for just editing icons, I think you might be able to just pull them out with a zip tool and drop them back in?
but to change xml and such you need to decompile and recompile...

I think it also needs to be zipaligned again after being altered? but most custom roms do that on boot so... might not be something you really need to worry about.

 

[3ud1]

Hello,im from indonesia and use local provider for optimus s,the version is 2.3.3 baseband ls670mvj_6150.kernel 2.6.35.7-perf lg-electronic@si-rd10BLD165 #2.
Then i try this rom,working good except i lost signal,about phone in settings is empty,no MEID.
Whats wrong with this,may i made mistake,or this rom can't use in my country?
Sorry for my english,and this my first android cdma.Now i'm back to ginger.

 

[upconvert]

That's odd. The ROM shouldn't have any effect on the meid, as far as I know. Can you see it in the settings of your GB ROM?

Sent from my GT-P7310 using Android Central Forums

 

[vector84an]

the version is 2.3.3 baseband ls670mvj_6150.kernel 2.6.35.7-perf lg-electronic@si-rd10BLD165 #2.

Ehm, you're running ZVJ, this rom is built for ZVD - no service is 100% normal...

Just finished going over this over here:
http://forums.androidcentral.com/lg...-jb-4-2-2-jbc-alpha-build-20.html#post2829327

 

[3ud1]

Ehm, you're running ZVJ, this rom is built for ZVD - no service is 100% normal...

Just finished going over this over here:
http://forums.androidcentral.com/lg...-jb-4-2-2-jbc-alpha-build-20.html#post2829327

Oh..thanks for advance.
Ok i will try and read about rom-cm10-1-pac-rom-jb-4-2-2-jbc-alpha-build-20

 

[upconvert]

Has anyone noticed that the weather widget on the lockscreen is broken? It used to work last year when I was on this ROM. I switched back to this ROM a few months ago, and now it just says "no data tap to refresh." I've also noticed that it was broken on one or two other ROMs, I think. Anyone have any ideas?

 

[_alexkta]

Upconvert I've noticed the same & I don't think it's the rom because I've tried other roms

Sent from my VM670 using Tapatalk 4 Beta

 

[djchru]

This is a CM issue... Yahoo changed their weather API