yashsingh1/xdaforums huggingface dataset:
[Optimus V Android Development] Whyzor:
I don't use any themes, I just like the stock gingerbread look, so I just fatfingered and removed anything theme related.

GenieWidget, dunno what it is, but my phone's fine without it.

LatinIMEtutorial is when Android boots up for the first time there's a tutorial on how to use the keyboard.

OneTimeInitializer & pacman, removed and din't have problems, latest BACKside build didn't have it included, kept it in case future builds it pops back on.

I realized I never use VPN on the phone either, so removed that too now.

Email.apk, I think K9 email is supposed to be better. Either way I believe anything that can be downloaded from the appstore should not reside in /system/app, because updated versions will take up additional space in /data/app.
[Optimus V Android Development] Whyzor:
I didn't know the camera had the wrong exposure to start with. Just checked mine (BACKSide 0803 build), it's set at 0. Setting it to 1 brightens it, but I'm afraid that would blow a lot of highlights (like an outdoor sky). Small sensor digital cameras like the one on the OV don't have have a lot of dynamic range, if bright spots are all at max, it loses a lot more detail. If a picture is overall darker, it can be somewhat recovered digitally by increasing gamma, but if a photo is too bright, then there's no way to recover the blown areas.
[Optimus V Android Development] jawz101:
that cyanogenmod link you posted helped explain some of them. made a rev2 and rev3. I think I'm going with my rev3 version. I guess if someone has changes they want to make they can use that link of instructions to sign again.

Edit: the reason I keep email.apk is it looks like it's for the corporate email setup option (ie- MS Exchange server connections) and you can also use it to configure a connection to Hotmail- which is what I use it for. per these instructions
[Optimus V Android Development] moore.bryan:
Went to flash the new img and discovered all letters "I" are automatically capitalized; any ideas how to stop that?

EDIT: Never mind... turns-out terminal emulator doesn't play nice with swype...
[Optimus V Android Development] bleichtman:
How do I flash the IMO recovery? Currently have rom manager installed with that recovery.
[Optimus V Android Development] BobZhome:
I felt that my pic's were on the dark side, so I used this tweak http://code.google.com/p/cyanogenmod/issues/detail?id=3625

Which was used on the zte blade.

BTW my git is github.com/BobZhome
[Optimus V Android Development] moonknightus:
Thanks for the init.thunderc.rc tweak. I will test this in the morning to see if it alleviates my wifi issues.
[Optimus V Android Development] Asadullah:
Do your fixes get added to blarfies repository?
[Optimus V Android Development] YouArePoop:
In terminal emulator ->

su

flash_image recovery whatever_file_name.img
[Optimus V Android Development] AndyOpie150:
Download a terminal emulator from the market. Make sure the recovery.img is unzipped. Rename the recovery.img to vrecovery.img. Move it to the Root of your SD card(somewere near the the bottom of the list of file folders). Open up the terminal emulator and type in su(hit enter key). You should see a # on the next line under su. Then type in: flash_image(space)recovery(space)/sdcard/vrecovery.img(hit enter key)

reboot(space)recovery(hit enter key). It will now boot into your new recovery.

If your not rooted let me know. There's a way to do it that way as well. EDIT: I must have been typing when YouArePoop beat me to it. Oh well, now you got two versions.
[Optimus V Android Development] bleichtman:
Thanks to both of you for the help. While waiting, I read another post that said to rename the original img in the cwm folder and then use the original name for the new img. I did that and reflashed. It seems to have worked.
[Optimus V Android Development] blarfiejandro:
No. I've mostly been out all day. I'm also doubtful that a DHCP watchdog is what's needed or if it addressees the root cause.

I'll probably dig through the CAF stuff to get an idea about the camera stuff. The tech sheet on the Sony sensor is woefully lacking in useful information and I'd like to find the proper exposure values.
[Optimus V Android Development] 83thomas:
Damn... I get no credit for my camera fix suggestion. lol. Just kidding. Nice work. Will this camera fix also be added to Jerry's build?

http://androidforums.com/optimus-v-...om-cm7-green-machine-theme-4.html#post3041273
[Optimus V Android Development] mrg666:
I just built an image from Blarfie's IHO repository and flashed on my OV. The phone is not bricked or exploded yet. It is just working so I assume the image is safe. This is straight from the git repository as it is on 08/05/2011. Please see the first post for changes.

If you want to try, you can download at the following link (replace _dot_ with .)

www_dot_mediafire_dot_com/?g0uadldevypgknp

MD5 sum: C58E13AB23AF1C13C9D30D3C44F9277D

I will keep building for myself but I will not post here unless there is a need or request. Jerry, Blarfie, you can send me a PM if you need help with building.
[Optimus V Android Development] blarfiejandro:
Yah, I'm not watching AC anymore (don't think I was watching that thread in the first place :P). Dunno what Jerry's going to do, but I'm going to do a bit of digging before incorporating the camera fix. I agree my pictures seem a little bit underexposed. If the Blade uses the same sensor I might as well just gank the thing unmodified (except for the white space :P). If it doesn't I'd like to make sure the full range of exposure settings are exposed (heh) in the Camera app.

In the future tho I'm going to see about bringing libcamera more in line with the CAF code (if that's possible — Qualcomm seems to have abandoned the MSM7k mostly).

Bob, Jerry, etc: Pull requests are the one big thing that makes Github bearable. If you open one and the two repositories are close enough it's a one click merge for me. To get the repositories close enough you might have to create a temporary branch and rebase it to include only the relevant commit(s).

I also tend to /really/ like having attribution in the commit log. If you cherry pick something from gerrit or another proper Git repo the author information is typically maintained when you push to Github. If you're taking a patch a URL to the patch in the commit message is ideal.

The good/bad thing about Git is that history is mutable. You can edit the last commit message simply with 'git commit --amend', and then a forced push to github. If you need to modify a commit before that you'll have to rebase to a few commits earlier, edit the commit in question, and then do a forced push.
[Optimus V Android Development] JerryScript:
ROM Manager has been a total fiasco on the Optimus V. There have been a large number of people soft-brick their phones using it. While I realize this was due to an incompatible recovery, which has been fixed, I don't believe it is necessary. The process for flashing a ROM is barely made easier by ROM Manager, and there are options in recovery that are not covered by RM.

There is also the issue of frequency of updates. At this time, IHO is in a rapid development stage. Insuring the proper builds are in ROM Manager could be a nightmare. Maybe once development slows down we will consider it.
[Optimus V Android Development] JerryScript:
Probably not till Blarf determines the proper settings. I don't like adding fixes that are a shot in the dark. Even if they work, they usually don't work as intended. ;)
[Optimus V Android Development] JerryScript:
I'll be keeping BACKside pretty much 99% IHO. I do a clean repo when there are lots of commits (by clean I mean delete everything and sync fresh), and I just do a repo sync on a daily (sometimes more often) basis.

I think this is the best way to insure that the repository and build process themselves are not causing any issues. Once development slows down a bit, I'll start working on turning Green Machine into a proper ROM of it's own. At that time, I'll delete the non-used JerryScript repository and create a GreenMachine repository forked off IHO.
[Optimus V Android Development] blarfiejandro:
Excellent! Obviously Jerry has been working on his theme, but I think he had his eyes on slimming the stock build down a bit.

The big void now is in support for the /other/ phones (Vortex, U, M, and C). I got a PM here about building an Optimus U ROM, but no follow through. There are a few people interested in a native port for the Optimus M, but few with the technical knowhow. Getting someone to pick up the pieces would be /killer/. Right now MMS and a GPL compliant kernel are the big two things left (eventually getting an IHO recovery set up would also be nice).

In the short term I'm going to gut the OP and move most of the info to the Github wiki (and either open it for all or open it to the three or four people building and distributing ROMs). That way there will be a really convenient place for people who want to build and distribute new ROMs to chime in... and people who figure out answers to the more frequently asked questions can post them in a prominent location... and more technical discussion can remain here.
[Optimus V Android Development] blarfiejandro:
Running 'make clean' should be more than enough and it will save the build tools (saving about 40 minutes off of a build for me).

I know Drew's been working on OTA updates for his builds (but he's also maintaining a stable and unstable branch). That may be something to look into. I think maybe he's using the built-in CM updater? Once the wiki is setup hopefully that'll be a better place to have a master list since ya'll can update it instead of waiting for me. Honestly however you guys want to distribute the ROMs is up to you. If you want to integrate with RM, do it. You will have to manually check out the binaries from Koush's repo and then tweak the build files to actually include it (but those are simple steps).

If I wanted absolute control over how this is distributed I'd be distributing binaries myself and wouldn't have published the repos on Github. The beauty of this is that there are now three actively maintained ROMs for the the Optimus V (two semi-active), and 2 or 3 for the Optimus S. People get to pick and choose what they want. Awesome.

Plaster RadioShack with flyers for all I care :-P

Edit: Sorry... "The Shack". :-(

As far as ROM Manager and I go, ROM Manager is a piece of crap. I know Koush has a lot of blood, sweat, and tears in CyanogenMod but ROM Manager is crap. Beyond recovery issues the ads obscure UI elements making it difficult to use on the Optimus phones. With the ads come user tracking that you can't opt out of (vs CMStats which is very prominently opt-out — and I would encourage people making ROMs to not cut CMStats... using it will let the CM folks know that people are using CM on our phones). Sure, you can *gag* pay for ROM Manager but it's still not open source and not really in the (purported) Android/CM spirit.
[Optimus V Android Development] mrg666:
I only have an OV. I can still build for other targets but will not be able to test them myself. Just let me know. I don't have any intention to modify the code or create a binary distribution. I am just building straight from your repository and offering help.

It would be great to have GPL kernel without the binary modules and in sync with Google's kernel version. I assume the main obstacle is open-source wireless/cell drivers. Are they available?
[Optimus V Android Development] mrg666:
Thanks, this is good to know. :)
[Optimus V Android Development] blarfiejandro:
Oh a full GPL kernel? Not likely.

I meant something for the MS690. Right now there's a guy that's been hacking aospCMod to work with that phone, and he's got a custom kernel but will/has not released the source.
[Optimus V Android Development] Whyzor:
Using the latest 0803 BACKside build, the native VoiP client & Groove IP both work a lot better over 3G. Is there a URL to the SIP fixes that went in? To satisfy my curiousity.
[Optimus V Android Development] blarfiejandro:
The big thing /I think/ was that Jerry switched to using the final zip generated by make bacon instead of one of the intermediate ones. There were some fixes to the built-in GB VoIP made to the CM tree as well.
[Optimus V Android Development] moore.bryan:
This is more a kitchen question, but is anyone else experiencing not being able to install themes cooked-up? No matter what I do, I can't use anything I make in the kitchen...
[Optimus V Android Development] pbailey212:
Are you using the system file uploads or the cm7 upload? I can't get the cm7 one to work, but I have no problems with system files. What recovery are you using? I did have some issues flashing uot zips with cwm 3.2.01
[Optimus V Android Development] moonknightus:
This build fixes my wifi problem. Thanks, BobZHome.
[Optimus V Android Development] moore.bryan:
System file...

Yeah, same here... that's why I thought to use the system file, but what do I know! ;-)

The one blarf posted earlier... his.
[Optimus V Android Development] pbailey212:
Are you getting any errors when trying to flash?
[Optimus V Android Development] mrg666:
Blarfie, I am monitoring the public activity on IHO github to see if a new built is required. Is it sufficient to see the changes in repository? Thanks!
[Optimus V Android Development] kayrypee:
AMAZING

i couldnt agree more (about rom manager) i was frickin stupid enough to buy rom manager a couple days ago and im pissed. i got the exact same thing as the free version. i know its just six bucks but its the fact of the matter. i am still kinda new to all this and of course, i find out that rom manager dosnt work that well with optimus v after i *gag* payed for it,and i didnt find out from koush....that pisses me off even more. instead of saying how great rom manager is, he should be saying what phones its compatible with and more importantly what phones will get the same thing from as the fee version if they buy.

anyway, the rom is great for me. only problems ive had is you cant charge with the phone powered off (just turns the phone off), the browser (only on xda's site, not sure if this is rom related) loads the page every time u move scroll or zoom or anything. battery seems to drain a little faster but not that bad. i did have trouble connecting with wifi the first time i connected after flashing, but a simple reboot fixed this (i am using a netgear router). i am using the 3.2.0.1 version of clockwork mod, i didnt restore any apps got them fresh from market. I didnt format the sd card either (everything but). the rom is working like an "out of the box" rom for me and i absolutely love it. it looks and feels great. i did a "clean" install and just followed the in structions from jerry scripts post on the first page and everything went flawlessly. i didnt flash green machine theme or the new recovery. and i still have 758mb external memory and 161mb internal. jerry, blarf, zhorneand everyone and anyone who i did not mention, thank u for this wonderful creation. the stock rom was getting pretty boring and felt way to "corporate" YOU GUYS ARE THE S#!T OH AND THE GPS DOESNT WORK, IT ALWAYS SAYS IM FACING NORTHWEST, EVEN AFTER THE LITTLE FIGURE 8 CALIBRATE THING. NOT THAT BIG OF A DEAL FOR ME ANYWAY.
[Optimus V Android Development] blarfiejandro:
That and the CM repos are the big ones. I think there are a few that are still pulled directly from the AOSP repositories too.
[Optimus V Android Development] moore.bryan:
Nope... just says something about installation failing, that is all.
[Optimus V Android Development] eollie:
This isnt a good idea. Rom Manager doesnt install gapps for you before the initial boot. Therefore people will be pitching a ***** because they dont have market. And other things.

The biggest problem Jerry is what I stated above. The rest can be worked out. Like Blarf said you would have two feeds a stable and nightly. However since you cant include gapps in your rom build and have to post it separately Rom Manager will just create more problems then necessary.
[Optimus V Android Development] eollie:
Remember anything you buy from the market will transfer to ANY phone you have tied to your google account even new phones.

It works just like it does on any of the other phones.

Rom Manager is compatible with any android phone.

The biggest misconception of Rom Manager is that Koush is the one responsible for pushing the proper things for the various phones to the database. He covered this a while back when he had half the android development community pissed off at him for a comment.

If you want to be upset with somebody be pissed at the devs that push roms and stuff and dont get the manifest setup properly, or when a phone is added they dont change the manifest to point to the proper place.

Im not a fan boi of Koush's I just know the real problem isnt so much him as its the community not maintaining there end of pushing stuff in to the deploy.fu branches.

All this said I am sorry Rom Manager has left you feeling used and abused. Did you learn anything from this? I know I bought a app on my old Droid X and found out I didnt need nor could I use it at the time because of the locked bootloader. It sits in my market account right now gathering dust. You live and learn.
[Optimus V Android Development] EmuZombie:
First I'd like to say thanks to JerryScript and blarfiejandro and everyone else for their awesome work on this.

I have an Optimus V running Jerry's backside rom. I recently jumped ship from aospCMod due to lack of development, source availability, and most of all Rom Manager requirement, but that's not the point of this post. Moving on....

I notice that under Settings | Pirvacy, "factory data reset" is still present. Will this soft brick the phone? aospCMod (and other roms) have had it removed to prevent accidental soft bricks. I plan to also flash this on my wife's phone however I do not want her be able to accidently use that option.
[Optimus V Android Development] YouArePoop:
Isn't there a window in which you can "return" a market purchase?
[Optimus V Android Development] blarfiejandro:
You can also ask the developer for a refund.

As far as ROM Manager goes, the biggest Optimus problem I have is that the ads just cover up too much of the screen. Items at the bottom can only be tapped on if you've got the paid version. I also don't like something that sits in the background and constantly phones home (not checking for updates, it sends usage stats back to Koush). Being closed source means we can't fix that.

What Drew did was integrate with the stock GB updater (under 'Settings -> About phone' I believe). That might be a more palatable option for all involved (maybe not).

As far as Google apps, they're not included by default because Google was being "open" (insofar as open is doublespeak to them) and sent the CM crew a cease and desist letter for including them. The knobs to include the Google apps with your own personal build are still there, and you can still do so if you want (Harmonia includes a few Google apps by default). If the big sticking point is the Market, you can certainly add just that to your build (altho IANAL and don't know if Google will send nastygrams to you).

'Course if you want to have an OTA updatable build, I'd encourage you to build one and distribute it (and update the wiki). GitHub will give you ~300MB of storage with a free account, so you can certainly use them for hosting the blobs.
[Optimus V Android Development] blarfiejandro:
Fifteen minutes... lol.
[Optimus V Android Development] Whyzor:
This has been fixed, so builds after Jerry's 0803 shouldn't have it anymore.
[Optimus V Android Development] BobZhome:
I believe the "knobs" were taken down a little while back, but I could be wrong.

If they were taken down...It's an easy fix :)

I may start including the top 3 Gapps(market, facebook, and twitter) with my next build :p

Thanks for the idea :D
[Optimus V Android Development] dwgjr330:
so will this be essentially replacing AOSp? and i read the how to with backing up stuff, but contacts and all my apps will be backed up with titanium backup? or is there anything else i should worry about when switching... the rom looks schweeett :D
[Optimus V Android Development] YouArePoop:
Swype made me re-validate. Thought I was on a different phone I guess. Titanium will let you get all apps back, minus some potential incompatibilities, etc. contacts I believe are synced to your google account and show back up one you do the initial login.
[Optimus V Android Development] dwgjr330:
yupp i am now on IHO- so far looks awsome!! with green machine (the dropdown needs a lil cleaning w/ CM7 covering half the buttons) but looks great :D cant wait to start messing with it once all my apps are back.

I can install other themes just by flashing them correct?
[Optimus V Android Development] punkmaxx:
still going well on 08/03 build of Backside ROM after three days. Love it guys!! super stable!!! Much snappier than the pre-07/25 builds.

EDIT: I OC to the max always so my phone is set at 864-480 performance maybe one random reboot in 3 days (that's impressive) i am usually trying to do stress tests because i like to abuse my electronics. LOL
[Optimus V Android Development] ajones23:
Yes I agree both mine and my sons OV,run very stable and smooth. Mine a little more OCed than his but no reboots.
[Optimus V Android Development] bohalloran95:
My home screen resets after reboot. Anyone else having this issue or know of a fix?
[Optimus V Android Development] mrg666:
I added 08062011 IHO build for VM670.
[Optimus V Android Development] punkmaxx:
WHeeeeee! YAY! EXcited
[Optimus V Android Development] eollie:
Blarf I hope your not misunderstanding me and blaming you or Jerry for not pushing something. What I was talking about happened back in January I think it was. Maybe longer Im not sure. But Koush posted on twitter about how the issues with Rom Manager were not his fault but teh dev communities for not pushing the proper repos and updating manifest I believe it was. I happened to see a exchange of tweets from birdman and koush and then they went to gtalk and discussed it. birdman tweeted a bit later the confusion was cleared and explained the problem even more so. The problems were very similar to what we have with Rom Manager not working properly for our phone. Also the fact the only way to see a rom is to be on GB is a issue of the manifests. Im lazy or I would find the tweet from koush.

I remember the C&D from google on the gapps. They claim a licensing to certain apps because they arent open and you have to get permission IIRC to use them. But they are included in stock roms from the carriers and manufacturers. I do believe that is correct right? I know many rom devs include the basic apps like market and a couple others in their roms but everything that can be downloaded from the market is not included.

If Jerry incorporated a update tied tot he CM one that would be super. I could get behind that. I just dont think sending the rom to RM is a good idea right now.

If you purchase Rom Manager from the market its fifteen minutes. If you buy it directly from Koush's site via paypal you can request a refund for like 24 or 48 hours IIRC.
[Optimus V Android Development] Kreatur3:
You can also mount in recovery and use the sdcard. Just so you all know you don't HAVE to use a card reader.
[Optimus V Android Development] brooksyx:
Thats not the point..

Its just easier to wait until its supported so I don't have to jump through all these hoops to connect my phone to my pc, which I do alot.
[Optimus V Android Development] blarfiejandro:
The fix to vold got merged into CM last night (http://review.cyanogenmod.com/6816).

Ext2/4 support was built into the latest kernel.

The next build should fix these issues for you guys. In the interim you can also use adb (without going booting into recovery) to get/put files onto the SD card in a pinch.
[Optimus V Android Development] punkmaxx:
24hrs+ on this ROM with no big hiccups. Speed and battery have me sold on using this. Thanks blarfie