yashsingh1/xdaforums huggingface dataset:
[Optimus V Android Development] ganggreen30:
JERRY 1 ISSUE 1 QUESTION. Lots of times I listen to music on the music player and screen goes off when I turn screen back on its froze showing the player. I can still unlock phone and do stuff under the half frozen music player but in order to correct I have to reboot. This has been going on for months now with the Roms. Also can u add a search function in the music player for us that have alot of music.! Thanks.

LG optimus v jerryscript backside iho 3/13/2012
[Optimus V Android Development] mkoyskip:
I'm happy things worked out for you. I started formatting my ext4 partition on my own when I was having issues formatting my partition for data2ext using recovery. Never had any trouble in the beginning but it might have been related to which recovery I had installed at the time - I switched recoveries off and on (and haven't always been the best at documenting my research/results...) Sometimes after formatting to ext4 I would check it on my pc and find that I still had an ext3 partition.

BTW I'm not positive about the 4k cluster size in general but that's what I was using for data2ext4, and I just kept it when I switched to link2sd. Also I don't know what ext partition you are using but if you want an ext4 partition through recovery you still need to format it again after creating it through recovery because it won't format an ext4 partition natively (as far as I know).

EDIT: I also experienced a lockup today while editing my calendar (calengoo, swype) - had to yank the battery.
[Optimus V Android Development] JerryScript:
Sounds like the ICS rotation animation bug, but I'm not sure. Please be sure ICS rotation animations are disabled.

As for a search feature in the music player, that's google's music player, not something I mess with since it's dealing with drm stuff. However, I'm sure there are some great music players on the market that include search somehow. ;)
[Optimus V Android Development] Liath:
Hey Jerry, just got this: http://virginmobileusa.custhelp.com/app/answers/detail/a_id/5662

Is cyanogen mod, and iho vulnerable to this?

Actually kinda wondering if it is just a patch our they got heads out of assess and pushed out the Android update...lol

Anyhow, if we do have the same bug, wanted to give you a heads up.
[Optimus V Android Development] tdm:
First, don't install it. It's a full update complete with radio, kernel, and and Android Froyo system. We don't know if the new radio bits are compatible with IHO yet. You might wind up with a device which is only capable of running their version of Froyo.

That page is very vague. It doesn't say what vulnerabilities have been addressed and I don't see any sources published yet to look for changes.

I believe IHO is built with the VM670 Froyo kernel as a base so it's probably going to be vulnerable to any kernel issues. I'm not familiar with all the Froyo kernel issues so I can't really speak to that.

IHO is built with Gingerbread (modified by CyanogenMod) userspace as a base, so it's not necessarily going to be affected by the same issues. We really don't have much of a choice but to trust that CM keeps up to date on any critical security vulnerabilities. I think the trust is well placed though.

All that said, keep in mind that rooting your device usually involves exploiting a security issue of some sort. So if all the known issues are fixed, someone needs to go find another issue to exploit. As a Linux kernel maintainer for a company that provides enterprise solutions, I can assure you that there's always another issue hiding somewhere to exploit. It's just a matter of time. :)
[Optimus V Android Development] Liath:
Well, if you hear anything, I'm sure cm, or you, would try to get it resolved. Hopefully it's just some minor vulnerability, or vm is catching on that we're rooting/missing because they've been lax updating to latest LG release. It could just be a move to prevent rooting?
[Optimus V Android Development] VannMann:
Sup guys, haven't been on in a while. Weird bug with my sons phone. He used the lense lockscreen and now can't get into the phone. It's like it won't pull down all the way. So I was going to go into recovery, and now it has the blank screen issue. Can't see anything in recovery. Was there and an issue with that, I can't be sure right now what build he was on, but wanted to post this before I took off to work to see if anyone could point me into the right direction or to a thread that might help me get a new recovery from adb or any other way. Any ideas would be awesome. Like I said, I can't get past the lockscreen, im stumped, lol.
[Optimus V Android Development] tdm:
Maybe, maybe not. But I'm sure they would consider that a benefit of the update if not. A benefit to them of course, not you. ;)
[Optimus V Android Development] JerryScript:
Sounds like you have one of the newer screens. Download the the recovery from the BACKside post at the beginning of this thread, then open terminal and type in these lines:

su
flash_image recovery /sdcard/NAME_OF_RECOVERY_FILE
reboot recovery

This will install the recovery, and reboot you into it to test. ;)
[Optimus V Android Development] dwgjr330:
maybe this update may explain the issues with a few of us and our texting bit haha will be interesting to see whats inside (no i wont be installing the update haha)
[Optimus V Android Development] VannMann:
From terminal of the phone? I can't get into the desktop of the phone, the lense lockscreen will not open all of the way. I am sure I could get the img to the sd card by some means, but need another way to flash it.
[Optimus V Android Development] tlgraber:
Take it from me; DON'T DO IT! I decided to flash it just to see what it was. I did a Nandroid backup first so I could revert (I'm running Jerryscript's ROM). Well, to make a long story short it bricked my phone. When I flashed the update.zip it said it completed successfully, but when it rebooted it stopped at the LG logo screen. I was eventually able to get it into Emergency Mode, and I probably ended up messing it up playing with it in EM.

Since we're on the subject: any suggestions for getting it going again? (I bought a new one so I'm not phoneless) I'm not sure the state it's in qualifies as "bricked." When I boot into Emergency Mode my computer recognizes it, but the connection comes and goes and I can't do anything with adb or with LG's recovery program. I bought it just under a year ago so it's still under warranty. VM diagnosed it as a bad battery and they're sending one (I know it's not the battery because I charged it with my wife's phone and it's good), and they also said they'll take care of the phone if it turns out to not be the battery. Thank goodness they never asked if I modded it! Now that I have a new phone I'm not sure they'll replace the bad one.
[Optimus V Android Development] Grosskum:
HELP

For some reason I have been getting random freezes, I was running an ICS rom and I thought it was jsut because it was in Alpha but now I'm getting it on this rom now that ive switched back. does anyone know what could be causing this?
[Optimus V Android Development] tvall:
Overclocked too high? What do you have it set at? (You are only guaranteed 600mhz)
[Optimus V Android Development] Grosskum:
thats what I originally thought but it continued after i put it back to 600
[Optimus V Android Development] JerryScript:
Did you do complete wipe/format between installing ICS and other ROMs?

--wipe cache

--under advanced wipe dalvik cache

--under mounts and storage format boot, data, system, and cache

Also, once you have rebooted at least once, allow the phone to fully boot (don't touch it for a full 10 minutes after boot up). Then open terminal and type in the following:

su
fix_permissions

Once it's done running, reboot one more time, and again, give it a full 10 minutes after booting to fully load up.

One common issue people have after installing a ROM package is not allowing it to fully load. The first boot does a LOT of stuff, rebuilding the dalvik cache, running first boot scripts, etc. Attempting to use the phone before this process completes can cause issues. ;)

---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------

You can use adb from your pc to install in much the same way. Once connected to your phone with adb, type the following:

adb remount
adb shell
(note you should now be in the phone's shell with a # sign for a prompt)
cd /sdcard
flash_image recovery NAME_OF_RECOVERY_FILE_HERE
reboot recovery

Once the phone begins to reboot, you may need to press cntrl+c in the adb window to shut it down, but usually it will shut down automatically. ;)
[Optimus V Android Development] tdm:
I just looked at the update zip again. I don't really understand exactly what they are doing for the recovery but it looks like a patch type thing instead of a full image flash. So I'm wondering if that hozes up your recovery if you don't have the official recovery image.

One would expect that the normal android update would have been done cleanly though. Don't have any ideas why that didn't work.

So there you go .. this just underscores the advice never flash both recovery and android at the same time. Even if you're the vendor. Unless you want to start giving away free devices under warranty.

If someone could figure out that the new radio bits worked and were somehow useful and/or improved, perhaps we could figure out a way to extract that portion of the update. But other than that, I don't see anything useful in it for users with custom ROMs or recoveries (eg. everyone reading this). The only thing you're gonna get out of the update is playing russian roulette with bricking your phone.
[Optimus V Android Development] VannMann:
I will try that, thanks jerry. It will be monday before	I get to though. I will respond back to let you know how it goes.
[Optimus V Android Development] JerryScript:
I think something went wrong with the download or flashing process in this user's case. There have been a dozen or so reports in various forums of others installing the update without bricking their phones. They loose root, and are stuck with a stock OV, but it does function properly.

Perhaps the updater-binary wasn't compatible with the particular recovery this user had installed?
[Optimus V Android Development] mrg666:
MiRaGe 03172012

I have uploaded a new MiRaGe build 03172012 to the IHO Wiki.

The followings are the changes after syncing with the CM repo

- Improve toast strings in Phone

- Hide SSN toasts by default in Phone

- Create Kineto-compatible AudioTrack::set and AudioRecord::set methods

- Show PIN entry screen even if lockscreen is disabled (not sure if this works)

Thanks to Blarf, Bob, Jerry, LeslieAnn, tdm, thekraven, gannon5197 and the CM team.
[Optimus V Android Development] b.roid:
i recently switched to a mirage build. i was wondering how do i disable the dumb voicemail notifications in the status bar? i was using BobZhome and never saw it. i know there not actual voicemails just missed calls.

thanks
[Optimus V Android Development] mrg666:
I would dial my voicemail and delete the messages ;) The notification for missed calls are different and they won't reappear once they are dismissed.
[Optimus V Android Development] ajones23:
IHO Wiki

Is the github for IHO down,cant access it.
[Optimus V Android Development] kwkbnk:
I flashed to my OV that i'm returning for warranty due to a hardware issue and it installed with no problem. Returned me to wonderful stock condition :( It did leave my recovery untouched so was no problem flashing back to backside. I did try rooting with gingerbreak just for the heck of it and wouldn't work. Just hoping new phone coming from VM doesn't have this update installed or I won't like it.

I am gonna reflash this to return to stock but can I reinstall stock recovery without root? If not I'll have to restore my backups and remove root the old fashioned way.

And something that just crossed my mind.... Is there a way to determine what the original MSL code would have been????? cause I changed mine to all 0's and did write down old one but lost it.
[Optimus V Android Development] Tekone:
I have ClockworkMod recovery 5.0.2.7 and manually install this rom by boot in recovery by press down vol + home and power to boot in recovery. Somehow I didn't backup my old rom and now i can install this rom in OV and stuck in recovery mode all time. How can i change my ClockworkMod recovery 5.0.2.7 to different recovery without boot in the rom?? I heart i need to run ADB and How? can anyone give a old flash link with instruction to update-grade recently old clockworkmod recovery to different recovery please.
[Optimus V Android Development] b.roid:
same here :eek:

---------- Post added at 03:29 PM ---------- Previous post was at 03:25 PM ----------

its weird. ive had vm disable my voicemail because i use google voice. still when i miss a call it seems to make it a voicemail? there is never a message its just blank? says the number that called and that's it.

its very odd.

i have deleted all the messages and they just keep coming back?
[Optimus V Android Development] BobZhome:
blarfiejandro is working on getting his git inline for CM and ICS, so the link has changed.

Try: https://github.com/inferiorhumanorgans/android_device_lge_thunderc_common/wiki/Binary
[Optimus V Android Development] mrg666:
Problem is with your voicemail account/configuration. It is not related to ROM.
[Optimus V Android Development] blarfiejandro:
That.

Hopefully that's the extent of the intrusive changes. One of the CM guys will vet the proposed changes and hopefully we'll get official CM support in short order. I've since updated the Wiki link on the first post.
[Optimus V Android Development] drm1992:
The recovery wont flash because its a txt file. Changing file type...would that work?
[Optimus V Android Development] Grosskum:
I have no idea where I downloaded it but there is a romtools program for the computer that can flash the recovery to your phone through usb, its easy to use but REALLY basic, if I find where I got it I will post a link. That is how I got my recovery on the first time and its worked many times after that, I would not recommend clockwork, IDK why but it works like **** for me (controls just stop).

---------- Post added at 11:57 PM ---------- Previous post was at 11:54 PM ----------

has anyone been having charging problems? It seems to work with usb but not my wall charger, it may just be broken but I'm curious if anybody has had problems. It will say charging for about 5 seconds and then it goes away and is back on battery.
[Optimus V Android Development] a5pe4:
Who's barf? ;)
[Optimus V Android Development] JerryScript:
That was an auto-correct fail! ;)

Barf = Blarf = Blarfiejandro = our fearless leader of the IHO dev team. ;)
[Optimus V Android Development] VannMann:
Hey JerryScript, I tried getting into the phone through adb but get device not found, can't bring up a shell. And I can't get into the phone to turn debugging on. Might just have to match motions with my daughters phone (I can see her recovery, lol). I do have to have debugging on for adb to work, right?
[Optimus V Android Development] dwgjr330:
off topic but im goin there anyway- what is your opinion of t-mobile phones/ service- i am thinking of switching... (i would def miss jerry's rom for sure)
[Optimus V Android Development] JerryScript:
Yes, you do need debugging on. Try one of the screen cast apps from the market, there are a couple that will allow you to view your phone's screen on your PC, so you can see what you are doing. ;)
[Optimus V Android Development] DarkenCypher:
Jerry I'm on your latest and I'm getting a lot of freezes/lockups requiring a battery pull.

Do you think I need a full wipe?

Sent from my LG-VM670
[Optimus V Android Development] JerryScript:
First, try running fix_permissions in terminal:

su
fix_permissions
reboot

If that doesn't fix it, first try wiping cache and dalvik cache and reflashing. Then if you still have issues, do a full wipe/format (boot,system,data,cache), and reflash the ROM and gapps.
[Optimus V Android Development] mikesting:
JerryScript i tryed

fix_permissions in terminal

and

wipe/format (boot,system,data,cache), and reflash the ROM and gapps.

but did not fix it for me but it's ok im just back on BobZhome ROM for now

but thanks for the info.
[Optimus V Android Development] JerryScript:
If you were switching from BobZhome to BACKside, I believe you have to do a full wipe/format. That's possibly what caused your issues. ;)
[Optimus V Android Development] mikesting:
i did a full wipe/format but no luck but its ok maybe your next ROM ;)
[Optimus V Android Development] joryb:
whats going on with the rom downloads page on github ? I'm getting a 404 not found
[Optimus V Android Development] jawz101:
Check a few posts back for a working link. Blarf's doing a little house cleaning. Here's the linkhttps://github.com/inferiorhumanorgans/android_device_lge_thunderc_common/wiki/Binary
[Optimus V Android Development] JerryScript:
There has been a post or two asking about having the ability to change system icons. While I don't have the time to add the option right now, I wanted to point out that NinjaMorph from the market works on the OV. It may close the first time you use it saying not enough space on sdcard, but open it again and it should work fine.

https://play.google.com/store/apps/details?id=stericson.ninjamorph.free&hl=en

To test it, I changed my alarm clock icon:
[Optimus V Android Development] dingermtb:
Ninjamorph works like a charm. I use this all the time to create my themes. I'll take elements from 5 or 6 different themes to create 1 theme. If you search here on Xda, there's a nice tutorial for it by the dev

Sent from my AlienFusion-VM670 using Xparent Blue Tapatalk
[Optimus V Android Development] workdowg:
SMS not working, vm issue? Anyone else today?
[Optimus V Android Development] mkoyskip:
Saw this from JerryScript on androidforums:

I haven't seen anything else about it.
[Optimus V Android Development] JerryScript:
VirginMobile has confirmed they are having sms/mms issues today. ;)

---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------

There were a half dozen phones bricked using the touch-recovery while attempting to flash the new ZV9 radio update patch.

For now, stick with BobZhome's IHO recovery. ;)
[Optimus V Android Development] Grosskum:
so thats why I cant text, I was wondering what was going on
[Optimus V Android Development] mkoyskip:
ok thanks, just went back to xionia.
[Optimus V Android Development] YouArePoop:
does the new radio really make any difference?
[Optimus V Android Development] JerryScript:
YMMV! ;)
[Optimus V Android Development] YouArePoop:
this something that's just going to make its way into next backside anyways? don't see a need in removing touch recovery if I'll just end up getting it by default soon enough anyway.
[Optimus V Android Development] tvall:
Roms dont (well.. shouldn't) touch radio or recovery
[Optimus V Android Development] YouArePoop:
alright cool. thought everything was either in recovery portion or rom portion (minus sdcard stuff). didn't know there were even more sections to phone.
[Optimus V Android Development] drm1992:
Has any one been experiencing constant adw launcher fc? Or am I doing something wrong
[Optimus V Android Development] tvall:
The internal memory is divided up into 8 mtd partitions plus space for the radio and stuff.see
[Optimus V Android Development] JerryScript:
Right after boot, the sdcard has to be loaded, so if you have a lot of apps on the sdcard, ADW is waiting for their info to load. During this initializing period, ADW is prone to freezes and fc's if you attempt to use the launcher (swiping screens, etc). And the period last a lot longer on the first boot after flashing a new build.

What I do for a startup procedure:

--wait for it to boot to lockscreen

--watch till screen timeout begins (screen dims)

note - during this time, I'm watching for the sdcard to be mounted, and the network to connect

--unlock the phone just as screen dims preventing it from going off at that moment

--now I leave it alone for 2-5 minutes (longer if first boot after installing rom update)

--now I unlock it again, and check to see that all the icons are showing properly

--if not, wait till they do appear

--once all icons are showing, I can use it without issue

This has worked for me for the past year using ADW on several different ROMs. Bear in mind, I keep just shy of 200 apps on my phone, with most on my sdcard, so it takes a while to load.

You might want to try a different launcher. There are three or four excellent ones that are much faster, and two or three of them even support ADW themes!

We stick with ADW because it's the CyanogenMod default, but you are not forced to use it. ;)

Note- If you are experiencing launcher FCs even long after boot + 5 minutes, try running fix_permissions in terminal, then rebooting.
[Optimus V Android Development] Whyzor:
I just installed Mirage 0317 build and am glad to see new updates on this little wonder phone still going strong. I have a few improvement suggestions:

1. Since ICS Roboto font is replacing DroidSans, the file /system/fonts/Clockopia.ttf should also be Roboto based for the lockscreen clock, I've attached a Roboto Clockopia.ttf.

2. I've made some tweaks to /system/etc/media_profiles.xml to use higher quality AAC audio encoding (64 kbps @ 44khz). Also using h264 instead of h263 for video. These are just what I think work well, haven't spent a lot of time to find the optimal setup, just a starting point.

+++ media_profiles.xml
@@ -80,15 +80,15 @@
<CamcorderProfiles>

<EncoderProfile quality="high" fileFormat="mp4" duration="60">
- <Video codec="h263"
- bitRate="1500000"
+ <Video codec="h264"
+ bitRate="4000000"
width="640"
height="480"
- frameRate="24" />
+ frameRate="30" />

<Audio codec="aac"
- bitRate="96000"
- sampleRate="16000"
+ bitRate="64000"
+ sampleRate="44100"
channels="1" />

</EncoderProfile>
@@ -138,10 +138,10 @@
minFrameRate="1" maxFrameRate="24" />

<VideoEncoderCap name="h264" enabled="true"
- minBitRate="64000" maxBitRate="1500000"
+ minBitRate="64000" maxBitRate="4000000"
minFrameWidth="176" maxFrameWidth="640"
minFrameHeight="144" maxFrameHeight="480"
- minFrameRate="1" maxFrameRate="15" />
+ minFrameRate="1" maxFrameRate="30" />

<AudioEncoderCap name="amrnb" enabled="true"
minBitRate="5525" maxBitRate="12200"
@@ -150,7 +150,7 @@

<AudioEncoderCap name="aac" enabled="true"
minBitRate="8192" maxBitRate="96000"
- minSampleRate="16000" maxSampleRate="16000"
+ minSampleRate="16000" maxSampleRate="44100"
minChannels="1" maxChannels="1" />

</MediaSettings>

3. In my Triumph kernel hacking adventures, I noticed SIO (Simple IO) scheduler provides the best user response and good performance overall. Is this the default scheduler in BobZHome 3.7 kernel? Noop is also another good choice, but from what I've learned, SIO allows other threads to interrupt during long IO operations.

4. In my experience, cpufreq_interactive governor gives the best performance and battery (using CPUSpy). There's a newer version that could be ported from here:

https://github.com/CyanogenMod/htc-...-2.6.35/drivers/cpufreq/cpufreq_interactive.c

Or at least use more battery-conserving timings "#define DEFAULT_GO_MAXSPEED_LOAD 95" and 20ms timer (from 80ms) so it can ramp down quicker when there is no load:

https://github.com/CyanogenMod/htc-kernel-msm7x30/commit/7ad56df8df971b2f67a2e94543bef20be7a78c5f
[Optimus V Android Development] JerryScript:
Well look who just blew back into town. Glad to see you haven't abandoned your little OV completely! ;)
[Optimus V Android Development] drm1992:
Thank you jerry. Really appreciated. Keep up the good work.