yashsingh1/xdaforums huggingface dataset:
[Optimus V Android Development] mrg666:
I thought with all those options and removals, my slim build got a little confusing. It brought too many questions about missing components. Other builds based on the same code already appeared after my build and the binary page was a little too crowded. It is simpler this way. I will be watching and if I see any need, I will post my build again. The others are the same ROM.
[Optimus V Android Development] DeerSteak:
Mrg666 I like and prefer your slim build. :)

Pbailey212 I haven't seen anything like that. Haptic is ok here.
[Optimus V Android Development] mrg666:
Thanks DeerSteak, I am glad I could contribute to the project. You can still remove the bloat after flashing any ROM using Titanium and a root file manager. Remove the system apps with Titanium, delete the ring tones with a root file manager. You are done :)
[Optimus V Android Development] blarfiejandro:
a.) Read my last post about MidTex (which no longer shows up as MidTex BTW)

b.) This a Microsoft problem, not an IHO problem. I will request further discussion of Bing be cleaned up by a moderator.

c.) Behave yourselves. Personal attacks are not appropriate for this thread or this forum.
[Optimus V Android Development] unloop:
I am also a fan of the slim down version you keep providing. I find it easier to edit the ROM zip file, remove all the ringtones, alarms and notification sounds that I don't like before flashing.

@Jerry - your latest version, it has the android.audio.mp3 boot sound, but it doesn't play on boot, that suppose to be that way or just my phone?
[Optimus V Android Development] mrg666:
Sure, that is an even better way of eliminating the bloat before getting into your phone. For the others trying this method without resigning the zip package, don't forget to disable sign check in recovery.
[Optimus V Android Development] deaver_92:
You have to download bootsnd.sh from eollie. Google it to find it. Make sure you get the one eollie posted. There's some that are a little different. Once you download it follow the exact instructions of the post you got it from. If it still doesn't work let me know and I'll walk you through how to make it work.
[Optimus V Android Development] unloop:
Thanks, I tried that back on the 8-10 build from Jerry, followed it exactly, file was named correctly, but still didn't play. No worries, I'll wait for it to be included in a future build or live without it.
[Optimus V Android Development] metalman1:
Navigation and IHO boot screen

Great rom. The only problem I have is with navigation. If I turn the screen off while navigating, I get a FC with navigation when I turn the screen back on. I have tried locking home in memory, and that helps a bit, instead of FC everytime the screen is off, it only happens every 2 or 3 times with lock home in memory.

Also, how can I eliminate the IHO boot screen now showing up. I typically use Ath3nos bloat remover after every new flash, but it doesn't remove the new IHO boot screen. I prefer the simple android boot screen.

Many thanks,
[Optimus V Android Development] captaincrook:
There was the same problem on one of my older phones, but the maintainer managed to fix it and you were then able to plug the phone in and get that charging screen like you do on the Froyo roms.
[Optimus V Android Development] eollie:
Much respect dude much respect.

I know what your problem is.

You have ran the script more than once right?

Do this and it will fix it.
[Optimus V Android Development] blarfiejandro:
An HTC phone, right? This is a recovery issue. Some HTC phones handle it with a couple of background processes that get launched in the recovery init scripts. LG handled it with the init daemon itself launching some stuff in recovery. LG's initd is not, AFAIK, compatible with CWM.

It's on my list of things to look at, but it's extremely unlikely to be fixed by me anytime soon.
[Optimus V Android Development] deaver_92:
I had issues with it at first too. If you're ambitious you can fix it in 5-10 minutes.

To start go to

/system/etc/unit.local.rc

and open it in the text editor. Delete everything from

###Bootsound - Safe to Delete: Start###

to

###Bootsound - Safe to Delete: Stop###

Delete any instances of it.

Next go to /system/bin/ and delete the file bootsound.

Now go to /system/build.prop and open it in the text editor. Scroll all the way to the bottom and delete any instance of

ro.config.play.bootsound=1.

Now delete build.pro this is an error in the bootsound script. If you don't have this file don't worry about it.

Now open the bootsnd.sh file you downloaded and scroll to the bottom. Find the line that reads

echo ' ' >> /system/build.pro

and add a p at the end so it reads

echo ' ' >> /system/build.prop

and then save and exit.

Now open terminal emulator and type in:

su

cd /sdcard

sh bootsnd.sh

Now go to /system/bin/ and verify that the file bootsound was created and make sure it has full permissions.

If all is well place android_audio.mp3 in /system/media/ if it isn't there already. Reboot and enjoy your bootsound!
[Optimus V Android Development] cornishrefugee:
Hi, I'm using mrg666's latest RC1 built from the 20th of August. This probably isn't a ROM related issue but I'll ask anyway. I've put the ROM on my gf's phone and it's working perfectly, totally blown away by how great it is.

She mentioned to me earlier that the only issues she's having is with text messages. When she types out an sms that's over 160 characters it will not send. If she shortens the length to under 160 it will send correctly. I'm not much of an sms user myself, but is the phone supposed to automatically split the message into 2 and then send those? Is there a phone side option we'd need to select? Or an app related selection? I wasn't sure if this was something that would be determined by the ROM or not.

She's using Handcent as her primary sms app.

Thank you for your time, and thanks also for the wonderful ROMS. Many people are enjoying the fruits of your labors.
[Optimus V Android Development] pbailey212:
Go to the messaging app and go to settings and there will be an option to auto split sms
[Optimus V Android Development] blarfiejandro:
I believe the bug was TWS would report at 50%. If you're not seeing 50%, you're probably not seeing the bug. I can report not seeing any TWS reported when I've had coverage all the time. Unsure when the stats are reset. With some of them it happens when you charge fully and then disconnect (they won't reset until you unplug the phone). 65% TWS certainly doesn't jive with great battery life, so try charging fully, ensure that TWS is not listed and see if you can then reproduce.
[Optimus V Android Development] cornishrefugee:
Thanks for the fast response!
[Optimus V Android Development] LeslieAnn:
Correct, the TWS bug was/is always stuck at 50%, it doesn't change. This was corrected on CM roms well before Froyo roms got a fix.

A restart will reset the stat.
[Optimus V Android Development] ejlmd:
mrg666, I also prefer your ultra-slim builds.

I hope you'll reconsider and resume uploading them to the wiki.

If not, would you consider sharing some sort of a tutorial to build a similar "barebones" version of IHO?
[Optimus V Android Development] 1cewolf:
I think it would be helpful if the wiki had a general tutorial on how to get started making your own version: removing apps, adding things, yadda yadda. It's one of the things on my to-do list.
[Optimus V Android Development] moore.bryan:
@mrg666, maybe you can clear this up... everyone's lauding your "slimmed-down" ROM and I appreciate all your work, but it didn't seem very slimmed-down on my phone; perhaps I did something wrong.

After installing your build and installing six apps, my internal memory was full. With JerryScript's build, I currently have forty-one apps installed to internal memory with no problem.

Me=confused.
[Optimus V Android Development] mrg666:
For the IHO fans asking for a slim build, I have uploaded 08222011 build in the Wiki. There are no changes in IHO branch since 08202011 build but a few changes come from CM7.1 branch. You can see what is removed in the Wiki. I added Email.apk back in after too many questions. The removed parts are not in the optional files section anymore since packaging those removals separately after every build is taking too much time and those are available in the other builds. So, this is slim build from now on. I have only added the stock Android 2.3.5 launcher for replacing the ADWLauncher for the extra purists :) As always, it is tested on my phone.

And, a little bonus which I had cooked in UOT Kitchen for myself and wanted to share with the ones who might like it. Here is a theme that makes the status bar transparent and adds an easier-to-read battery indicator with consistent Gingerbread colors, everything else original. You can see below
[Optimus V Android Development] mrg666:
The internal flash memory of the system is partitioned into fixed size parts. The ROM is flashed into /system partition and /data partition is available for your use. So, flashing a smaller ROM will not give you more space to use on /data. But smaller ROM without the apps, themes, and ring tones you don't need/use will probably make your system use less resources in cache and RAM. At least, I feel good not to have them in my phone :)

I am not sure why your memory filled up after six applications. It should give you about the same space with BACKside with the reason I tried to explain above. I have also not heard such a problem before and never happened to me. Anyway, BACKside is excellent and I would stay with it :)
[Optimus V Android Development] EmuZombie:
I hate your cluttered screen ;)

Personally I think, simplicity is bliss.

(I'd take a more recent screen shot, but nothing has changed, so I took the lazy way out)
[Optimus V Android Development] moore.bryan:
Yeah, I switched-back to Jerry's, just thought the space usage was interesting. Keep-up the excellent work any way, though!
[Optimus V Android Development] mrg666:
All of the required information can be found in the following two links.

https://github.com/inferiorhumanorgans/android_device_lge_thunderc/wiki/Source

and

http://source.android.com/source/downloading.html

Blarf's guide in the first link is excellent. It directs you to the second link.

Basically, you download the IHO repository with the following command

repo init -u git://github.com/inferiorhumanorgans/android.git

Before this command, you have to download git and repo packages in a 64-bit Linux system with the required development packages. See the links above for the requirements. I use 32-bit Ubuntu 11.04 (since I already had it configured) but some people say that this does not work for them. So I would stick with 64-bit to be on the safe side if I were you.

Edit: Blarf has commented and corrected in a later post. I have corrected the above post accordingly.
[Optimus V Android Development] mrg666:
Well, thanks anyway:) Yours looks good to me.
[Optimus V Android Development] mustafu:
mrg666, what is that Widget in your screenshot? I like how it has all that info at a glance
[Optimus V Android Development] BobZhome:
I have new build https://github.com/inferiorhumanorgans/android_device_lge_thunderc/wiki/Binary

Changelog

08-22-2011:

1. Sync'd up with CM

2. Updated to Blarf's GPS tweak(faster lock and improved battery life)

3. Update to official LG fingerprint

4. Fix: libaudio - Don't mute in-call audio

5. tweak: recovery - Mount any second partition on an SD card

6. tweak: Increase read ahead buffer

Please don't thank me, instead donate to Blarf for all the great work he has done.

Enjoy!
[Optimus V Android Development] blarfiejandro:
Nope. You don't need to use the AOSP repo at all. Just initialize with the IHO manifest. I believe I've updated the AC thread, but there is an entry on the wiki about building from source:

https://github.com/inferiorhumanorgans/android_device_lge_thunderc/wiki/Source

If it's too ambiguous, please coordinate with 1cewolf and edit.
[Optimus V Android Development] EmuZombie:
New build of IHO-Purity is up.

Changelog:

-Sync'd with current CM7.1

-No other changes on the IHO side.

Download MD5: 2de538d202daf16e035178fd2f214126
[Optimus V Android Development] mrg666:
Sense Analog Small Black
[Optimus V Android Development] mrg666:
The AC thread still mentions about syncing with AOSP first. I will check the Wiki and edit as required. Thanks!
[Optimus V Android Development] captaincrook:
Actually it was a Motorola phone (Cliq XT to be exact). I'm just not sure myself what exactly needed fixing but I remember the earlier versions of CM7 having the same issue.
[Optimus V Android Development] LeslieAnn:
I got my build box working again and this is the first build from it

This follows Harmonia in many ways, hence the working name (subject to change). Everything you need, nothing you don't.

Stripped down but contains (all current as of this afternoon):

Fresh graphics on startup

email, market, gmail

English Spanish languages

No boot animation, or Gallery3D (I recommend Quickpic)

Minor battery tweak

MIUI style icons and Harmonia's large percentage battery indicator (I hate the green and prefer an easy to see battery indicator)

ADW simply because it's a stripped CM rom. May become Launcher pro later.

May be seriously flawed, so use at your own risk.

Download

Harmonia_2b1_22aug_IHO_CM_OUT.zip

MD5: 03107495f8c5e7a7ae19b046026a5659
[Optimus V Android Development] pbailey212:
I got something for you Jerry... at the expense of my battery, I put my phone in my pocket without closing my camera, and my battery went from 39% to 9%
[Optimus V Android Development] LeslieAnn:
I may have spotted a bug today.

While reloading my phone I was re-installing apps through MyBackup Pro, however, the install apps from unknown sources warning never came up and it was not checked.

Can anyone confirm this?
[Optimus V Android Development] pbailey212:
I had that happen too a while back, I rebooted and it fixed its self
[Optimus V Android Development] LeslieAnn:
It didn't fix it for me.

I rebooted, enabled it, and disabled it, no effect.
[Optimus V Android Development] cornishrefugee:
Does anyone use IHO also happen to use a banking app that allows you to take a picture of their checks and deposit that way?

Having a slight issue with the camera. It will focus perfectly well in normal camera mode, but when I try to take a picture of a check in the app the autofocus doesn't work. I've tried changing settings in the camera but that seems to have no bearing on the camera when the banking app uses it.

Thanks for any advice or suggestions.
[Optimus V Android Development] cornishrefugee:
? Not sure if the reply didn't work or you are bumping the thread haha.
[Optimus V Android Development] captaincrook:
Noticing some slowness between transisitions and scrolling but the rest really seems to be great. I will probably try disabling surface dithering and see if it helps but I'm betting its a driver issue since there's no official GB one.
[Optimus V Android Development] PancakeShake:
Mrg666 your 8-22 revival of the email did not work for me? Force close when I try to add email.

Also when I restart it switches back to original theme?

Otherwise muy bueno very smooth and fast!
[Optimus V Android Development] blarfiejandro:
Ya, AFAIK the phone will boot (I think into recovery) when powered up by a USB port... at that point initd checks to see why the phone turned on and then runs some programs. Because it's baked into initd, and not in a shell or init script, I can't quite tell what it's looking at. When I check the obvious sysfs entries, I don't get anything that differentiates between a reboot and a power on. I'd be hard pressed to label this a CM bug because each phone tends to handle this situation differently.
[Optimus V Android Development] blarfiejandro:
Unfortunately I do not. My credit union recently deployed a windows app where you can use a scanner to scan in checks... lol... ALMOST there. *facepalm*

I know that there are some comments in the various isx005 drivers that there are autofocus problems coming in and out of macro mode. If you can get the camera app to take a focused picture of your check, it's probably worth trying to follow up with your bank to get an idea of what they're doing. They may be setting the wrong AF mode. Otherwise try to enable pre-focusing in the camera app or try a half-press of the shutter button, dunno if that'll persist to your bank's app.
[Optimus V Android Development] blarfiejandro:
Have you tried clearing your cache FS and the dalvik cache between ROMs?
[Optimus V Android Development] blarfiejandro:
With the stock MMS app that needs to be configured in an XML file.. Dunno if Handcent is picking up on those settings. Open an issue on Github and I'll take a look at it... but note that I only use the stock MMS app for... well... MMS. Otherwise I use Google Voice which doesn't seem to have such issues.
[Optimus V Android Development] dingermtb:
Ugh...still having same reboot issue. I've tried all the IHO builds with same result. Mostly been trying on mrg666's. I get all of my apps restored using TB. Even used "app only" funtion. Did not reistall any data, system apps, or system data. It'll run beautiful, like new. Then, after my first reboot, it'll go through reboot screen, start to load, then rebooting itself. It'll just keep going through that same cycle. Thought it may have been an app issue, so i kept trying to reinstall them , a couple at a time, in different orders, then rebooting. All worked perfectly. It's only after i install so many that i get the reboot issue, and i have tons of space. Used all the same apps on AOSP ROM with space still left. Also, not overclocked, and tried both, IHO and AOSP recoveries to no avail. Right now, working with mrg666's with link2sd. Any help would be GREATLY appreciated. I really want to get this working since it looks like AOSP's ROM may be abandoned.
[Optimus V Android Development] LeslieAnn:
Quit re-installing everything from TB.

Do a few at a time, rebooting in between until you find the culprit.keep track of what you installed last. Every backup program has programs that give them fits, something you are restoring is the cause. Keep an eye on app space remaining as well. Some programs pitch a fit when you reach the "normal" end of rom, even though the rom recognizes you still have several dozen megs free.

Or, write down all of your apps, and do a clean install of each from the Market, which isn't necessarily a bad thing now and then anyhow. Same goes for data, sometimes it helps to not restore data and actually log in and let it pull the data back fresh.
[Optimus V Android Development] dingermtb:
Yeah, i tried installing a couple at a time and in different orders with reboots in between. That was gonna be my next step, reinstalling all right from the market. After everything was reinstalled, i checked, both, freespace plus and link2sd, and both said 158 MB left for internal storage. Thanks for the quick reply. Off tonight, so I'll have the time to reinstall everything from the market, and already have a list written down :)
[Optimus V Android Development] ejlmd:
IHO Recovery and QPST

Minor issue: when rebooted into current IHO Recovery, QPST sees the open port but doesn't recognize the phone.

QPST does see the phone in recovery mode after switch to latest CWM 3.2.0.1.

Using latest mrg666 8/22 build
[Optimus V Android Development] 1cewolf:
Thanks for the reminder, mrg and blarf. I couldn't remember what specifically was on the Source page since I haven't taken a good look at it in a while.

I left it alone because it seemed suitable for the typical caliber of users you'd expect to develop variants. Looking at the page again, I do see some places where changes would be helpful for someone inexperienced who needs extra assistance to get started.

I'm one of those people. There's no doubt in my mind that some of you know more about this than I do, so if I have to do some background research to bring myself up to speed, why shouldn't I write it down? I'll see what I feel like doing when I'm farther along. I do think blarf's instructions are probably fine for typical devs who know what they're doing.
[Optimus V Android Development] pbailey212:
http://forums.androidcentral.com/op...4423-building-your-own-rom-6.html#post1194756

On the 3rd post Jerry has step by step instructions for dummies (or noobs. To be politically correct) like my self, I found it really helpful
[Optimus V Android Development] mrg666:
Hi, I just tried Email and it worked fine. Also, the theme does not reset after reboot for me. Regarding Email, you can try deleting the data and start fresh in application settings. For the theme, I would make sure the default system theme is selected in theme chooser and there are no other themes interfering. Also, I assume you have wiped cache and the dalvik cache before flashing the latest ROM? That is all I can think of.
[Optimus V Android Development] YouArePoop:
Minor annoyance I've noticed. After flashing new version I can't enable more than one keyboard at a time in settings.
[Optimus V Android Development] moore.bryan:
Yeah, I did a *complete* reflash...
[Optimus V Android Development] mrg666:
Blarf pushed several changes last night. Please see Wiki for the changes. I have flashed 08232011 build to my phone and uploaded to the Wiki. Please report if you find any bugs. Seems to be working fine for me.

Blarf, I still had to remove FM app manually. Thanks!
[Optimus V Android Development] BobZhome:
All he did was sync up with cm.

To stop the radio from building, just comment out FM in bcm_FM_radio.mk
[Optimus V Android Development] mrg666:
Thanks for the insight. I flashed those changes on my phone and sharing with others for testing. Thanks again, for the FM hint too, I do the same way. This is the change I am talking about hoping that Blarf would add for IHO as well.
[Optimus V Android Development] crpeck:
I've seen at least one other post about this - whenever I go into CM Setting's Status Bar tweaks (the 1st time after a ROM flash) and enable the Battery percentage - the 1st time I enable it, it shows only the number. If I toggle it off and back on it has the little thin battery icon. Well, I just picked up a Nook Color refurb, and, have CM on that now - it does the exact same thing - so, I'm thinking this is a CM thingy? Not a big deal, and, probably most folks have a UOT cooked anyways - just thought it was interesting. Has anyone else noticed this behavior?

BTW - the Nook is an awesome little android pad, it's cake to install CM on an SDcard and run it from there, no hacks involved at all - if the card is in it just boots from it - you can optionally install to the internal memory as well.

Sorry for the off-topic on the NC...

Now - I gotta go try Harmonia CM on my OV...
[Optimus V Android Development] mrg666:
I just tried that with Titanium and installation was blocked by the system when unknown sources was not checked, using 08232011 build. Unknown sources check is working for me.
[Optimus V Android Development] daryllh:
This a total embarrassing question:

What version did I install on my phone?

This is what I downloaded on Sunday evening.

VM670-CM7.1-RC1-IHO-08202011

I think it's mrg666's version but there isn't anything in 'about phone' section that says that.

I'm eager to update but I want the update of the one I have on my phone (since I haven't had issue with it so far).

Thanks
[Optimus V Android Development] mrg666:
That file name looks like my build. I don't add anything in phone identification since it is just IHO after some bloat removal.
[Optimus V Android Development] EmuZombie:
New August 23rd build of IHO-Purity is up. Again, nothing major just sync'd with CM

Changelog:

-Sync'd with current CM7.1

-No other changes on the IHO side.

Download MD5: f24a2b5c32f96670b3f0ce805241c974
[Optimus V Android Development] EmuZombie:
I also don't add anything in the id field either since I am trying to remain pure as possible. Maybe mrg666 and I should reconsider this to help prevent confusion like this in the future?

However, yes that would be mrg666's build based on the file name. My filenames will always be VMU670-CM7.1-RC1-IHO-PURE-<DATE>