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

[Garymeister]

So I downloaded the newest update and the status bar seems glitched still. The top bar, no matter what theme or what window I am in, seems to not exist or is transparent making my icons (normally on the standard gingerbread black status bar) hard to see. Is there a fix for this?

 

[mustafu]

So I downloaded the newest update and the status bar seems glitched still. The top bar, no matter what theme or what window I am in, seems to not exist or is transparent making my icons (normally on the standard gingerbread black status bar) hard to see. Is there a fix for this?

Settings - cm settings - interface - change status bar setting to "Rom"

 

[Eollie]

Okay... So this really didn't have anything to do with me or the issue I was having at all? Cool, I guess.

I downloaded the Chinese version and it seems to be the same app more or less. But then I see you have the app already by going to the Bing site? Huh. And according to the article someone else posted the app was part of an exclusive deal between Verizon and Microsoft...what part of exclusive did you not get?

In fact your issue doesn't seem to have anything to do with anything, other than maybe you using me and my troubles to restart conflict over an issue you've already worked around that has nothing to do with the BACKside rom at all.

Thanks, 'friend'.

--bornagainpenguin


Sent from my LG-VM670 using Tapatalk

...wow.

I guess you missed my post stating I dont want to bring it up. I even said before I didnt wanna get it going again.

To address your smartass statement of exclusive deal between Verizon and Bing...guess you dont understand that you can goto the mobile bing site and download the app. Its not exclusive anymore nor was it at the time. What you are refering to is a old deal with Verizon. It is a moot point now as I have the app installed.

I guess I misunderstood your initial post. I was trying to cover all bases and was truly trying to help. But whatever "friend" (I can do that too) jump to conclusions and assume you know what I was trying to do.

 

[pbailey212]

Well rom managers latest update finally puts a working recovery for our phone, it rolled back to cwm 3.2.0.1 and recognizes the V again... not that I will ever use it, but atleast people "should" stop bricking their phones for the time being

Sent from my LG-VM670 using Tapatalk

 

[JerryScript]

...for the time being

QFT

 

[kcls]

Well rom managers latest update finally puts a working recovery for our phone, it rolled back to cwm 3.2.0.1 and recognizes the V again... not that I will ever use it, but atleast people "should" stop bricking their phones for the time being

Sent from my LG-VM670 using Tapatalk

Does it still give a black screen for newer Hitachi screens?

 

[thewraith420]

Unless it's a different 3.2.0.1 then the Hitachi screens will still be blanked by it. I've used that cwm on a friends new screen v only to find out it didn't work. Then from the rom I flashed bobz's IHO recovery

IHO Unofficial CM7. 2
BACKside IHO 12212011

 

[anthonycr]

Hmm, can't repro.

I let my phone get to 2%. Then I powered it off. Then connected the charger and chargerlogo came up. Then I held the power button and the phone booted normally.

Yeah, it was just weird. I haven't had it happen again either. I wonder if the rom somehow glitched or something, bc like I said, I could boot into recovery on low battery, but not into normal boot mode or chare logo boot. I'm assuming the rom had some sort of hiccup somehow, I haven't had any problems since then. Thanks for taking the time to try to figure it out.

 

[pbailey212]

Does it still give a black screen for newer Hitachi screens?

I doubt it, but atleast people will stop trying to install the recovery for the optimus c, it would be even better if it would just show up as "not compatible for our phones"

Sent from my LG-VM670 using Tapatalk

 

[A.I.]

Annoying bug. Can't get the phone to respect the lowmemoery killer values in IHO. Most apps I can get to run in the background is maybe 4 on a regular basis. Logcat shows the usual memory complaint when it closes apps, but "Free" in terminal and the RAM counter in the Settings apk both tell me I have around 230MB Free before it starts closing my apps.

Just to test I used AutoMemoryManager and set the values close to really low, and still the ROM chooses to end apps way before the limits set.

Either "free"/Settings is lying or there's something deeper.

Happens across all variants.

 

[JerryScript]

The minfree values are set by init.rc, so they will be overwritten on reboot. The only way to keep changes to them is to run a script from init.d to set them at boot.

 

[A.I.]

I don't really test on boot; I hardly let my phone turn off.

I set the values post boot, and they should stick at least until the next reboot but it's frustrating to feel like it's not being applied according to the two "built-in" ways to check your RAM.

I might sound crazy to some for wanting to use more RAM, but I want more apps to sit in RAM so I don't have to keep restarting them. I can browse and return to the home screen, put my phone down for a minute or two, come back and my browser will have closed automatically due to "out of memory" conditions.

And plus, I'm getting like 230MB of RAM free that it just won't use, which is a lot that I can't use.

Forgive me if it isn't a bug, but I don't know how else to classify it as.

 

[Eollie]

I have a semi-bug to report jerry, I'm runnin the latest (1/25) version of backside.
~snip~

Sorry for the long post, but I know details are important when you have a problem

Thanks for the detailed report!

So, it sounds like the phone failed to boot with approx. 15% charge remaining? That seems awfully high for boot failure. Are you sure it really got turned off and didn't just run out of battery overnight?

I'll try to repro this and let you know what I find out tomorrow or monday. If I can repro it, I'll flash the original boot.img and see what it does.

I had something similar. Only I forgot to plug my phone in and it died. I plugged it in it sat on the charge screen for probably an hour. When it dawned on me the phone was still off I powered it up while still on the charger. It booted up notified me I had 3 missed calls and two missed texts. And before I could check them it rebooted back to the charge screen. I power cycled it again this time without being plugged in. Everything seemed fine until the phone rang and it forced closed the android.sound process. Then it force rebooted itself and seemed to be fine until this morning when I took it off the charger. The phone randomly rebooted but no weird force closes since.

 

[BobZhome]

I have new build https://github.com/inferiorhumanorgans/android_device_lge_thunderc/wiki/Binary

Changelog

1-30-12:

1. sync'd up with CM: new ICS transitions
2. Kernel v3.7: Enables a2sd swap and adds BT HID support

Please don't thank me, instead donate to Blarf for all the great work he has done. Special thanks to Jerry, mrg666, thekarven, TDM and all the others that have help to improve this project.

Enjoy!
Bob

 

[JerryScript]

New build is up:

Download via the BacksideUpdater

or

BACKside-IHO-VM670-01312012.zip
md5sum 46b531b924a5042cb121d521ff851c7f

GreenMachineTheme-01312012.zip

Changes:
-- Added Pedlar's CMBootanimation chooser to Settings>>CyanogenMod settings>>Interface>>Bootanimation
-- Added two additional bootanimations to /system/media for use with the bootanimation chooser
-- Update to BobZhome's kernel v3.7 with support for a2sd swap and BT HID, Thanks Bob!
-- BacksideUpdater updated with option to check any downloaded file, option to delete bad download before trying again (prevents download renaming such as file.zip becoming file-1.zip), and updated gui elements

The bootanimation chooser will allow you to preview, change, or reset the bootanimation to default. I switched to my infamous bootanimation as default, and included the CyanogenMod and particle bootanimations as well in the system/media folder.

The BacksideUpdater will now automatically download the manifest when you open the app now. There is a new button at the bottom of the screen that will allow you to check any file against the manifest's md5sum. If the md5 is bad, you have the option to delete the corrupt file and redownload, or to delete the file manually. I also added progress spinners so it doesn't appear as if the app has frozen while performing it's background tasks. Hope you like the new gui elements!

Thanks to Blarf, BobZhome, mrg666, tdmcode, LeslieAnn, thekraven, kermikalelite, Whyzor, bigsupersquid, the CM team, the AOSP team, and a whole lot more!

 

[kwknott]

Jerry,

I keep getting FC'd when I try to select or preview boot animations on your new build. I wiped Cache and Dalvik the first time and then a wipe and flash the 2nd. Any thought's? Using IHO recovery, Verified MD5 with updater.

Edit: Figured it Out!

It's because I had removed file manager with TB because I usually use another program. After another wipe and flash I worked until I removed File Manager. I tried reinstalling from market and even moving APK to system but it wouldn't work again till I reflashed the Rom to get that version of File Manager back

 

[JerryScript]

Jerry,

I keep getting FC'd when I try to select or preview boot animations on your new build. I wiped Cache and Dalvik the first time and then a wipe and flash the 2nd. Any thought's? Using IHO recovery, Verified MD5 with updater.

Edit: Figured it Out!

It's because I had removed file manager with TB because I usually use another program. After another wipe and flash I worked until I removed File Manager. I tried reinstalling from market and even moving APK to system but it wouldn't work again till I reflashed the Rom to get that version of File Manager back

Glad you figured it out! I will look into supporting a general file manager intent structure, but that depends upon all file managers using the same broadcast/receiver structure, and I'm not sure that's true. So for now, the default file manager will have to remain in order to use my mods that require file picking.

 

[kwknott]

Thanks Jerry,

Yeah works great now that I have File Manager back.

Great job on the new build!!! Thanks again!

 

[Whyzor]

I don't really test on boot; I hardly let my phone turn off.

I set the values post boot, and they should stick at least until the next reboot but it's frustrating to feel like it's not being applied according to the two "built-in" ways to check your RAM.

I might sound crazy to some for wanting to use more RAM, but I want more apps to sit in RAM so I don't have to keep restarting them. I can browse and return to the home screen, put my phone down for a minute or two, come back and my browser will have closed automatically due to "out of memory" conditions.

And plus, I'm getting like 230MB of RAM free that it just won't use, which is a lot that I can't use.

Forgive me if it isn't a bug, but I don't know how else to classify it as.

Unused RAM in Android is wasted RAM. In some situations it can speed up loading of new apps, that's probably where the speed boost comes from. For most people, it's more preferable to use the RAM to cache apps in the background so you don't have to reload them every time, it defeats the purpose of a multitasking OS.

 

[a5pe4]

When I choose the boot animation from system/media to preview in file manager and then hit ok, nothing happens. Am I missing a step?

Edit: Fixed. Had disable boot animations selected.