[ROM+Kernel] Inferior Human Organs unofficial CM7.1

aeroseek

Well-known member
Feb 11, 2011
66
10
0
Visit site
I originally used this recovery but had issues

with frequent updates to these new roms, trying this rom and that rom -
i'd wipe everything, format directories, just in case, and used the 1.3 wiper zip and wiped again -
yet after installing another rom, i would still have stuff appear from last install like wallpapers, status bar icons colors, etc

so i kinda gathered something was cleaning right.

i installed asop cwmod recovery and followed same above procedure and it seems this recovery cleans everything better... not sure if its just an "on my end" issue, but thats my 2 cents

maybe try this recovery? i think its the one recommended for cm7 roms, at least i remember reading that somewhere.

Thank you for the suggestion. I've never had issues with xionia but I DID notice that my old wallpaper showed up after a clean flash. Hmm...I will give it a try!
 

blarf

Well-known member
Jul 8, 2011
176
237
0
github.com
ok, so it seems to be running much better after using clockwork recovery. the only downfall still is that my live wallpaper continues to freeze. otherwise everything else seems to be working well.

thank you!

If your wallpaper is the solar wind one, check the logcat output. It's crashing. While it /could/ be a bug in the graphics drivers... I suspect it's a bug in the app.
 

Growjunky

Well-known member
Mar 24, 2011
49
3
0
Visit site
Blarf has been working for the past week on his kernel, now at v53. You might want to stick with this kerne since it is built specifically for the Optimus V. But, it doesn't take too long to flash a kernel, so why not try them both out? ;)



I've read bug reports on every CM7 ROM for the OV about this, not sure what causes it at this time. I'm guessing a conflict with a CM7 setting, but that's pure speculation. Perhaps you could try grabbing a logcat and dmesg while setting a custom ringtone, and set a custom ringtone to a phone you have handy and call yourself. Then post the logcat/dmesg to pastebin, or just attach here if that's too much trouble. ;)
[i didnt know how to run a logcat i had to look it up] D/alogcat ( 2633): stopping ...
D/alogcat ( 2633): starting ...
D/alogcat ( 2633): stopped
I/AudioService( 176): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
I/HeadsetService( 611): During phone call: disable DSP.
D/AndroidRuntime( 611): Shutting down VM
W/dalvikvm( 611): threadid=1: thread exiting with uncaught exception (group=0x40018560)
D/AudioFlinger( 125): setParameters(): io 1, keyvalue routing=1, tid 171, calling tid 125
E/AudioHardwareMSM72XX( 125): doRouting CALLED, outputDevices = 0x1, mFmRadioEnabled = 0
I/AudioHardwareMSM72XX( 125): Routing audio to Handset
W/AudioHardwareMSM72XX( 125): Routing to 5 really (current: 0)
E/AudioHardwareMSM72XX( 125): Parsing error in AudioFilter.csv.
D/AccelerometerListener( 264): enable(false)
I/PROFILE ( 176): Group: Gmail containing : com.android.phone : false
I/PROFILE ( 176): Group: Phone containing : com.android.phone : true
V/AudioManager( 264): shouldVibrate, group: Phone mode: DEFAULT
I/PROFILE ( 176): Group: Gmail containing : com.android.phone : false
I/PROFILE ( 176): Group: Phone containing : com.android.phone : true
I/PROFILE ( 176): Group: Gmail containing : com.android.phone : false
I/PROFILE ( 176): Group: Phone containing : com.android.phone : true
V/AudioManager( 264): shouldVibrate, group: Phone mode: DEFAULT
D/AudioHardwareInterface( 125): setMode(RINGTONE)
D/AudioFlinger( 125): setParameters(): io 1, keyvalue routing=2, tid 171, calling tid 125
E/AudioHardwareMSM72XX( 125): doRouting CALLED, outputDevices = 0x2, mFmRadioEnabled = 0
I/AudioHardwareMSM72XX( 125): Routing audio to Speakerphone
W/AudioHardwareMSM72XX( 125): Routing to 0 really (current: -1)
V/NotificationService( 176): Active profile: Default
I/PROFILE ( 176): Group: Gmail containing : com.android.phone : false
I/PROFILE ( 176): Group: Phone containing : com.android.phone : true
V/NotificationService( 176): Pkg: com.android.phone group: Phone
E/AudioHardwareMSM72XX( 125): Parsing error in AudioFilter.csv.
E/AudioHardwareMSM72XX( 125): Parsing error in AudioFilter.csv.
W/AssetRedirectionManager( 176): No such resource found for com.upwardspiral.Blue_Bionic:mad:drawable/com_android_phone_ic_in_call_touch_answer
W/AssetRedirectionManager( 176): No such resource found for com.android.phone:color/incall_incall_callTypeSip
V/alogcat ( 2633): save instance
V/alogcat ( 2633): paused
I/InCallScreen( 264): onCreate()... this = com.android.phone.InCallScreen@40552cc8
D/alogcat ( 2633): stopping ...
W/ResourceType( 264): getEntry failing because entryIndex 65 is beyond type entryCount 1
D/alogcat ( 2633): stopped
I/Process ( 611): Sending signal. PID: 611 SIG: 9
I/power ( 176): *** set_screen_state 1
I/ActivityManager( 176): Displayed com.android.phone/.InCallScreen: +1s876ms
I/PROFILE ( 176): Group: Gmail containing : com.android.phone : false
I/PROFILE ( 176): Group: Phone containing : com.android.phone : true
V/AudioManager( 264): shouldVibrate, group: Phone mode: DEFAULT
D/InCallTouchUi( 264): onDialTrigger(whichHandle = 3)...
D/InCallTouchUi( 264): updateState: Too soon after last action; not drawing!
D/InCallTouchUi( 264): updateState: Too soon after last action; not drawing!
I/AudioService( 176): AudioFocus abandonAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface( 125): setMode(NORMAL)
D/alogcat ( 2633): stopping ...
D/alogcat ( 2633): scheduling periodic saves
D/alogcat ( 2633): starting ...
V/NotificationService( 176): Active profile: Default
I/PROFILE ( 176): Group: Gmail containing : org.jtb.alogcat : false
I/PROFILE ( 176): Group: Phone containing : org.jtb.alogcat : false
I/PROFILE ( 176): Group: Calendar containing : org.jtb.alogcat : false
I/PROFILE ( 176): Group: Email containing : org.jtb.alogcat : false
I/PROFILE ( 176): Group: SMS containing : org.jtb.alogcat : false
V/ProfileManager( 176): No active group, returning default: Other
V/NotificationService( 176): Pkg: org.jtb.alogcat group: Other
V/alogcat ( 2633): started
V/alogcat ( 2633): resumed
W/asset ( 241): deep redirect failure from 0x01030068 => 0x0a060003, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000
W/asset ( 241): deep redirect failure from 0x01030067 => 0x0a060002, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000
W/asset ( 241): deep redirect failure from 0x01030067 => 0x0a060002, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000
D/AccelerometerListener( 264): enable(false)
V/NotificationService( 176): Active profile: Default
I/PROFILE ( 176): Group: Gmail containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: Phone containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: Calendar containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: Email containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: SMS containing : com.bel.android.dspmanager : false
V/ProfileManager( 176): No active group, returning default: Other
V/NotificationService( 176): Pkg: com.bel.android.dspmanager group: Other
I/HeadsetService( 2680): Starting service.
I/Effect-Equalizer( 125): EQ_PARAM_NUM_BANDS OK
V/NotificationService( 176): Active profile: Default
I/PROFILE ( 176): Group: Gmail containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: Phone containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: Calendar containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: Email containing : com.bel.android.dspmanager : false
I/PROFILE ( 176): Group: SMS containing : com.bel.android.dspmanager : false
V/ProfileManager( 176): No active group, returning default: Other
V/NotificationService( 176): Pkg: com.bel.android.dspmanager group: Other
I/HeadsetService( 2680): Phone status idle: enable DSP.
I/Effect-BassBoost( 125): New strength: 0
I/Effect-Equalizer( 125): Setting band 2 to 0
I/Effect-Equalizer( 125): Setting band 2 to 1
I/Effect-Equalizer( 125): Setting band 2 to 2
I/Effect-Equalizer( 125): Setting band 2 to 3
I/Effect-Equalizer( 125): Setting band 2 to 4
I/Effect-Equalizer( 125): Setting loudness correction reference to 100.000000 dB
E/AudioHardwareMSM72XX( 125): Parsing error in AudioFilter.csv.
D/Email ( 770): *** synchronizeMailboxGeneric ***
I/ActivityThread( 2690): Pub com.facebook.katana.provider.LoggingProvider: com.facebook.katana.provider.LoggingProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.NotificationsProvider: com.facebook.katana.provider.NotificationsProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.KeyValueProvider: com.facebook.katana.provider.KeyValueProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.ChatHistoryProvider: com.facebook.katana.provider.ChatHistoryProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.CacheProvider: com.facebook.katana.provider.CacheProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.UserValuesProvider: com.facebook.katana.provider.UserValuesProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.PagesProvider: com.facebook.katana.provider.PagesProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.MailboxProvider: com.facebook.katana.provider.MailboxProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.UserStatusesProvider: com.facebook.katana.provider.UserStatusesProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.PhotosProvider: com.facebook.katana.provider.PhotosProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.EventsProvider: com.facebook.katana.provider.EventsProvider
I/ActivityThread( 2690): Pub com.facebook.katana.provider.ConnectionsProvider: com.facebook.katana.provider.ConnectionsProvider
I/dalvikvm( 2690): Jit: resizing JitTable from 512 to 1024
D/alogcat ( 2633): saving log to: /sdcard/alogcat/alogcat.2011-07-24-00-15-30-0700.txt
D/dalvikvm( 2690): GREF has increased to 201
D/Cache ( 2091): Opened database
D/Cache ( 2091): Closed database
I/dalvikvm( 2633): Jit: resizing JitTable from 1024 to 2048
D/Cache ( 2091): Opened database
D/Cache ( 2091): Closed database
. this is my first one so heres my first try.
 

Whyzor

Well-known member
Jul 19, 2011
406
176
0
Visit site
I noticed another interesting problem in logcat (still on kernel #53, 20110722 BACKside build), this message gets repeated every 1-2 seconds when the phone is DISCONNECTED from USB.

I/TelephonyRegistry( 118): notifyServiceState: 0 home Virgin Mobile 209099 EvDo rev. A CSS not supported 2 4155RoamInd: 1DefRoamInd: 1EmergOnly: false
I/TelephonyRegistry( 118): notifyServiceState: 0 home Virgin Mobile 209099 EvDo rev. A CSS not supported 2 4155RoamInd: 1DefRoamInd: 1EmergOnly: false
I/TelephonyRegistry( 118): notifyServiceState: 0 home Virgin Mobile 209099 EvDo rev. A CSS not supported 2 4155RoamInd: 1DefRoamInd: 1EmergOnly: false
...
...

But if I connect it to USB, the message stops, or only reports during an actual event. Full logcat can be found below. I started terminal emulator, 'su', then 'logcat > /sdcard/log.txt' and plugged in USB, wait for a bit, then disconnected USB.

logcat.txt - Pastebin.com
 

larryc

Active member
Feb 11, 2011
35
3
0
Visit site
This is the first CM7 rom I'm trying, so please bear with me. I'm running this rom with kernel #53 (the 7/22 build)

When I plug the phone into my Win 7 x64 PC using USB, I am unable to mount the phone as a USB drive. In device manager, I see "LG Android USB Device", but it has a yellow arrow on it. Not surprisingly, adb does not work either.

Before I installed this rom, I was running Harmonia (Froyo) and it worked fine over USB. Do I need different usb drivers for CM7/gingerbread, or is this a known problem?
 

Whyzor

Well-known member
Jul 19, 2011
406
176
0
Visit site
This is the first CM7 rom I'm trying, so please bear with me. I'm running this rom with kernel #53 (the 7/22 build)

When I plug the phone into my Win 7 x64 PC using USB, I am unable to mount the phone as a USB drive. In device manager, I see "LG Android USB Device", but it has a yellow arrow on it. Not surprisingly, adb does not work either.

Before I installed this rom, I was running Harmonia (Froyo) and it worked fine over USB. Do I need different usb drivers for CM7/gingerbread, or is this a known problem?

I didn't have to update my win7x64 drivers when moving from stock froyo ROM to this. Maybe a reboot of machine and phone, or removing the PC drivers and reinstalling them will fix it.
 

blarf

Well-known member
Jul 8, 2011
176
237
0
github.com
This is the first CM7 rom I'm trying, so please bear with me. I'm running this rom with kernel #53 (the 7/22 build)

When I plug the phone into my Win 7 x64 PC using USB, I am unable to mount the phone as a USB drive. In device manager, I see "LG Android USB Device", but it has a yellow arrow on it. Not surprisingly, adb does not work either.

Before I installed this rom, I was running Harmonia (Froyo) and it worked fine over USB. Do I need different usb drivers for CM7/gingerbread, or is this a known problem?

You might. Do you have the little USB icon in the status bar? If not, you need (updated) drivers. I'm using the official LG drivers (see OP) with XP and no problems. For USB tethering you'll need a newer build and additional drivers (also see OP). If you do, that's how you enable USB mass storage (altho I think XP sees the drive anyhow).

Also what USB vendor and product ID does Win7 see?
 
  • Like
Reactions: larryc

gbeaguilar

Well-known member
Apr 19, 2011
45
0
0
Visit site
Great work on this rom! Much more stable than aosp's for me!

One issue I am having is with long texts... they always fail to send. I have tried enabling the "split message" option and that does not seem to work either. Any suggestions?
 

larryc

Active member
Feb 11, 2011
35
3
0
Visit site
You might. Do you have the little USB icon in the status bar? If not, you need (updated) drivers. I'm using the official LG drivers (see OP) with XP and no problems. For USB tethering you'll need a newer build and additional drivers (also see OP). If you do, that's how you enable USB mass storage (altho I think XP sees the drive anyhow).

Also what USB vendor and product ID does Win7 see?
Ok, I installed the LG drivers from the first post and it works fine now - charging, mass storage, and adb.
Thanks!
 

JerryScript

Daydream Believer
Mar 8, 2011
2,055
1,559
0
Visit site
I noticed another interesting problem in logcat (still on kernel #53, 20110722 BACKside build), this message gets repeated every 1-2 seconds when the phone is DISCONNECTED from USB.

I/TelephonyRegistry( 118): notifyServiceState: 0 home Virgin Mobile 209099 EvDo rev. A CSS not supported 2 4155RoamInd: 1DefRoamInd: 1EmergOnly: false
I/TelephonyRegistry( 118): notifyServiceState: 0 home Virgin Mobile 209099 EvDo rev. A CSS not supported 2 4155RoamInd: 1DefRoamInd: 1EmergOnly: false
I/TelephonyRegistry( 118): notifyServiceState: 0 home Virgin Mobile 209099 EvDo rev. A CSS not supported 2 4155RoamInd: 1DefRoamInd: 1EmergOnly: false
...
...

But if I connect it to USB, the message stops, or only reports during an actual event. Full logcat can be found below. I started terminal emulator, 'su', then 'logcat > /sdcard/log.txt' and plugged in USB, wait for a bit, then disconnected USB.

logcat.txt - Pastebin.com

Have you noticed what your signal strength is at these times? I'm thinking if your signal is low, the phone's first instinct is to search for a better signal, and at some time that search checks the roaming info.
 

Whyzor

Well-known member
Jul 19, 2011
406
176
0
Visit site
Have you noticed what your signal strength is at these times? I'm thinking if your signal is low, the phone's first instinct is to search for a better signal, and at some time that search checks the roaming info.

This was at my home, which usually receives 2/4 signal bars (around -92 to -97 dbm), so I would say it's pretty good. It doesn't explain why when USB is connected, and I'm doing logcat through adb shell, the msgs don't appear. It's only when I'm disconnected and logcat using the terminal emulator app on the phone.
 
Last edited:

blarf

Well-known member
Jul 8, 2011
176
237
0
github.com
I've read bug reports on every CM7 ROM for the OV about this, not sure what causes it at this time. I'm guessing a conflict with a CM7 setting, but that's pure speculation. Perhaps you could try grabbing a logcat and dmesg while setting a custom ringtone, and set a custom ringtone to a phone you have handy and call yourself. Then post the logcat/dmesg to pastebin, or just attach here if that's too much trouble. ;)

Actually this is an issue with EVERY CM7.1 (maybe all CM7 versions) build out there. This /is/ a CyanogenMod bug, and I've opened a code review ticket on gerrit. I realize that the IHO stuff is a very untested codebase, and there are a number of things that are problematic in ways specific to IHO builds as a result. However (this isn't directed at you Jerry), don't underestimate the propensity for bugs to exist in the CM codebase ESPECIALLY the unstable branch. I've made very minimal changes to the CM apps and such so far, and I'd like to keep it that way.

In this case what was really needed was a debug build of Phone.apk... and I'll go so far as to say this bug may very well exist in stock Gingerbread. Given the glaring bugs that Google's left in production releases Gingerbread I wouldn't be the least bit surprised if this broke. Say what you will about Apple, but they put a LOT more effort into UX (both end-user and developer) and it shows.

[RANT]I just had this discussion with a friend of mine. She wanted a smartphone, and I couldn't really recommend anything other than the iPhone at this point. She was wowed with Swype tho.

Android is just so ****ing half-baked with what's considered stable releases... ugh. From a UX standpoint what a joke. The tabview and expandablelistview are both still hopelessly broken. The normal listview. Sigh. Between treating the middle of the list as the end and not letting you scroll past and just sticking mid 'bounce' (even on my friend's stock Triumph!)... no way Apple would ship something that glitchy. Let's not even talk about Android 3.0. FFS. It's a good thing for Google that RIM and Palm are even worse off.

I went with the Optimus V because it's cheap and because I could use a proper (BT) serial interface with it. Well... someone went and built an Arduino breakout kit for the iPhone and got it Apple approved. Now there's a proper Apple sanctioned SDK for accessing serial ports from iOS. There goes that argument. All you MSq guys will likely have a much easier time with that than you will trying to hack up USB OTG on Android (which is on my list of things to think about, but since I've moved the VM670 kernel to a USB gadget framework it should be much more inline with the P500 stuff... and you'd likely have a fairly easy time porting it).

I don't want to give up Swype, but if iPhone data plans ever come down in price, I'm jumping ship ASAP.[/RANT]
 
Last edited:
  • Like
Reactions: Raul720

notown

SAMLOKA
Jun 2, 2011
367
67
0
Visit site
yeah, apple does make some great stuff. it is what it is..this phone is not the best by all means, but i still enjoy mine and thanks to people like you and other talented, great folks from here and all over that dedicate time to code out of passion to make something like this ...its pretty awesome ...for that i thank you again....:eek: i wish i could donate now, though next thurs sounds better because thats when i get paid :p
 

LancasterJames

New member
Jul 25, 2011
1
0
0
Visit site
Actually this is an issue with EVERY CM7.1 (maybe all CM7 versions) build out there. This /is/ a CyanogenMod bug, and I've opened a code review ticket on gerrit. I realize that the IHO stuff is a very untested codebase, and there are a number of things that are problematic in ways specific to IHO builds as a result. However (this isn't directed at you Jerry), don't underestimate the propensity for bugs to exist in the CM codebase ESPECIALLY the unstable branch. I've made very minimal changes to the CM apps and such so far, and I'd like to keep it that way.

In this case what was really needed was a debug build of Phone.apk... and I'll go so far as to say this bug may very well exist in stock Gingerbread. Given the glaring bugs that Google's left in production releases Gingerbread I wouldn't be the least bit surprised if this broke. Say what you will about Apple, but they put a LOT more effort into UX (both end-user and developer) and it shows.

[RANT]I just had this discussion with a friend of mine. She wanted a smartphone, and I couldn't really recommend anything other than the iPhone at this point. She was wowed with Swype tho.

Android is just so ****ing half-baked with what's considered stable releases... ugh. From a UX standpoint what a joke. The tabview and expandablelistview are both still hopelessly broken. The normal listview. Sigh. Between treating the middle of the list as the end and not letting you scroll past and just sticking mid 'bounce' (even on my friend's stock Triumph!)... no way Apple would ship something that glitchy. Let's not even talk about Android 3.0. FFS. It's a good thing for Google that RIM and Palm are even worse off.

I went with the Optimus V because it's cheap and because I could use a proper (BT) serial interface with it. Well... someone went and built an Arduino breakout kit for the iPhone and got it Apple approved. Now there's a proper Apple sanctioned SDK for accessing serial ports from iOS. There goes that argument. All you MSq guys will likely have a much easier time with that than you will trying to hack up USB OTG on Android (which is on my list of things to think about, but since I've moved the VM670 kernel to a USB gadget framework it should be much more inline with the P500 stuff... and you'd likely have a fairly easy time porting it).

I don't want to give up Swype, but if iPhone data plans ever come down in price, I'm jumping ship ASAP.[/RANT]

I was all set to try this Rom until I read this. I cannot with a clear conscience use software developed by an Apple fanboy. An, iPhone? Really?...Really? Besides the slave like conditions they keep their developers, Apple has some of most crippled hardware out there. Without "jailbreaking" (which most fanboys lightheaded thinking about), the iPhone is nothing more than a child's toy. This is coming from 20 years in the software development industry. I have developed for smartphones in particular for 10 years now. By far, the best platform to develop for and use has been Android. I don't know all the details of the CM codebase, but the real android platform has been a dream for me. I also know for a fact that personalized ringtones do work within Gingerbread. It is fairly arrogant to blame Android for a bug introduced by CM. Thanks for all of your work, I know development is a thankless job most of the time. I'm going to hold out for the LG Gingerbread release for the S.
 

Kreatur3

Well-known member
Mar 2, 2011
660
40
0
Visit site
My bttery life ws pretty shotty but I switched from interctive to ondemnd nd it is working much better now.
BTW nnoying s it is my @ key isn't working lol. Not typing out @ everytime I wnt to use n @ sorry. :(