yashsingh1/xdaforums huggingface dataset:
[Optimus V Android Development] Kolma:
I don't know if it's a hardware problem on my phone, or if it's from the build on the 25th

But i noticed for about a week now that my swype was acting funny

i would swype about and it would randomly add spaces or cut my words up so it just came out all wrong.

I thought, eh, user error would try again and would work after a few time.

Then i tried to do an asterisk, (shift -> hold v)

And it would just spam a bunch of C's v's and space's

So i figured ok.. must be swype. and well i uninstalled and reinstalled swype and same problem

And just today i found out it's not swype at all. it's my entire phone.

on the 4x4 grid on homescreen

if i were to hover around the bottom near the bottom left corner app, and the one to the right of it, the screen would flip out as if i was moving my hand really fast. even though i was staying still.

Not sure if it's my hardware or something messed up with the build on the 25th.

Will wipe cache, dalvik, etc. and install an older build to see if problem continues, will update.

*notes

Using Jerry's build

Op V contains newer screen

*edit, installed the jan 20th build. same problem

Guess my touchscreen just decided to break itself

Anyone have any solutions for this before i go and replace the touchscreen?
[Optimus V Android Development] pbailey212:
I would try this first to confirm its the hardware

https://market.android.com/details?...51bGwsMSwyLDEsIm9yZy5oZXJtaXQudG91Y2h0ZXN0Il0.
[Optimus V Android Development] Kolma:
THANKS SO MUCH

Found out what the issue is, for whatever reason in that area is just really sensitive and will detect two points at once if im not careful

when i hovered around it with my thumb as i normally would, it would flash between the blue and green.

Yet when i was more careful or use my index finger it worked alot better

So my touchscreen isn't broken... just retarded and a tad more sensitive than it should be. That or my thumb is bumpier than it used to be

Thanks again for saving me the hours of work it would have taken me to swap out the touch screen with my old op v (that only has a broken LCD)
[Optimus V Android Development] leolawliet:
I used to have that issue every time I'd charge my device at my bro's house, the issue stops every time I disconnect my phone from the charger. Everywhere else my screen works fine. By the way I plugged in into a Monster outlet. Can anyone else confirm this?
[Optimus V Android Development] BobZhome:
I have new build https://github.com/inferiorhumanorgans/android_device_lge_thunderc/wiki/Binary

Changelog

1-30-12:

sync'd up with CM: new ICS transitions

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
[Optimus V Android Development] startak11:
Thanks!! So glad for ICS transitions.
[Optimus V Android Development] pbailey212:
Ok I kind of know what swap is, but how does it benefit us. I understand it on Linux but I'm kind of confused about androids use for it
[Optimus V Android Development] 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!
[Optimus V Android Development] ajones23:
Wow,Jerry looks like you were pretty busy. This build has a lot of changes,like the bootanimation Chooser. Ur rom keeps getting better all the time. Thanks.
[Optimus V Android Development] badrsj:
Hello, any IHO builds that have fixed the "won't reboot if plugged in" issue that came up after the "power off charging" got fixed.

thank you.
[Optimus V Android Development] JerryScript:
No, that's a kernel issue, it's being looked into though. ;)
[Optimus V Android Development] pandulce1:
There is definitely a lot a love being given here. Thank you for your hard work.
[Optimus V Android Development] Kolma:
Was downloading jerry's 1-31-12 build..

got 75% through, and then mediafire goes down..

http://www.downforeveryoneorjustme.com/mediafire.com

Must be just down for america, it works fine when i use my firefox which contains polish proxies lol

*edit working fine now. weird
[Optimus V Android Development] tvall:
Works fine for me, in America, using both my schools wifi, and vm 3g.
[Optimus V Android Development] mjs2011:
thanks Jerry, i can now safely delete my Boot Animation Changer app. ;)
[Optimus V Android Development] moore.bryan:
Had a strange thing happen today running the latest mirage: a reboot during a phone call. Any ideas?

Oh, and, when I long press in Seesmic--for the retweet menu, for example--the app fc's. That also happens in every other program with long screen presses.

Sent from my IHO phone
[Optimus V Android Development] dingermtb:
Just gotta chime in here. Running Jerry's newest ROM, and i gotta say, it keeps getting better and better. IHO is my new religion and Jerry, Blarf and the rest of the IHO team are my gods :)
[Optimus V Android Development] ajones23:
Same Here. Great Work As Always.
[Optimus V Android Development] DarkenCypher:
I'm running mrg's latest and have none of those problems. Btw great ROM mrg!
[Optimus V Android Development] dxxvi:
Is it normal: I wiped cache, dalvik cache, flashed this zip and rebooted. The first thing I saw after a reboot is a lying battery with green bars running. I had to long-press the power button (sometimes twice) and the Virgin Mobile logo appeared. After that the cyanogen logo appeared. If this is normal, it's very inconvenient because my phone sometimes reboots itself while the google maps is running and i'm trying to drag the map.

Thank mrg666 for all your works.
[Optimus V Android Development] DarkenCypher:
I'd do a full wipe. That sounds like a weird flash problem

Edit: I forgot to add what the user under me posted (tapatalk being dumb again!)
[Optimus V Android Development] pandulce1:
The ability to charge while off was recently added to IHO roms, unfortunately in it's current state it also kicks in during a reboot. On the bright side, the rom you flashed has the new kernel v3.7 which I have been trying out for a few days now and it's been rock solid so far. I too had the random reboots when using google maps with kernel v3.6.
[Optimus V Android Development] mrg666:
Sounds like a bad flash or file permissions problem. You can try resetting the permission in the recovery or using ROM Manager. If those don't help reflashing the ROM after a clean wipe can help. I am not experiencing any FCs with the ROM.

---------- Post added at 01:22 PM ---------- Previous post was at 01:10 PM ----------

Before the off line charging fix, there was a static red LG logo instead of the current animated VM logo. I don't like the VM animated logo either. I have already replaced the VM animation with a static Android logo. I am going to include that change in the next build. But you can use this flashable zip file to make change right now. Just flash it from the recovery without wiping anything. With this change, you will see the silver LG logo, the static Android logo, and the CM boot animation.
[Optimus V Android Development] mrg666:
MiRaGe 02012012

I have uploaded the 02012012 build of MiRaGe with the following changes after syncing with CM repo.

- add option to disable scrolling cache

- 'Blade' style for lockscreen rings

- ADB over network. I have added this just because it was merged in the CM repo. I recommend disabling this and using the USB cable for both safety and security.

- option to disable the new rotation animation through system properties: persist.sys.rotationanimation. This is still enabled by default.

In addition to CM repo changes above, I have also replaced the VM boot animation with a static Android Logo. The sequence is now the silver LG logo, static Android logo, and the CM boot animation.

I have tested on my phone and did not see any problems.

Please thank/donate to Blarf, Bob, Jerry, tdm, LeslieAnn, thekraven, bigsupersquid, Whyzor, and the CM team. Enjoy!
[Optimus V Android Development] tdm:
I found a way to detect warm boot (reboot) yesterday. This means it will be possible to skip the chargerlogo for reboot. blarf has merged this into the IHO code and users can expect this to appear in ROMs in the next few days.
[Optimus V Android Development] mrg666:
Thanks so much for this. Is it the change in init.c? I have added that and it did not help. Is there any other change that needs to be done? (such as the init scripts)
[Optimus V Android Development] tdm:
Yes you'll also need to edit device/lge/thunderc/files/common/init.thunderc.rc. Create a new event trigger boot-cold and move chargerlogo from early-boot to boot-cold.
[Optimus V Android Development] mrg666:
Thanks again! This explains :)

Edit: With that change, I can confirm that phone successfully reboots while connected to charger. However, connecting the charger causes spontaneous boot just like the condition before your off-line charging fix. Also, the "power off" command causes reboot when the charger is connected. I think there needs to be more changes in init.thunderc.rc than just moving chargerlogo from early-boot to boot-cold. I will post if I can make it work.
[Optimus V Android Development] moore.bryan:
Thanks for the help mrg666, it must've been a bad flash!

Sent from my IHO phone
[Optimus V Android Development] JerryScript:
You'll only have to long press when the phone is plugged in.

Tom aka tdmcode just found a solution for the reboot while plugged in bug, expect it in builds released over the next week. ;)

Thanks Tom and Blarf!

---------- Post added at 01:56 PM ---------- Previous post was at 01:30 PM ----------

I'm building with the changes now, but it sounds like expected behaviour with these changes. I'm assuming that plugging in the charger after power off now boots into offline charging mode? Same with the power off, reboots to offline charging? I'll find out in a few, target dex now. ;)

Edit: almost done building, looking thru the code, this would make a crash caused reboot while plugged in to go to offline-charging mode, not something you want if charging overnite. I think the logic needs to be reversed, and another hook added to catch the charger-power-on case.
[Optimus V Android Development] DarkLG:
Jerry with the next build will you be incorporating

'Blade' style for lockscreen rings? :)
[Optimus V Android Development] ajones23:
I'm pretty sure he will.

Sent From VM670 BACKside IHO/ICS Theme
[Optimus V Android Development] JerryScript:
Yes, it's a CM commit, so it will be a part of all IHO. ;)
[Optimus V Android Development] ajones23:
Hey Jerry got a guestion. What would my gallery pics not show up,like wallpapers. If I reboot they show back up.

Sent From VM670 BACKside IHO/ICS Theme
[Optimus V Android Development] JerryScript:
I forgot to post this when I posted the new build with the bootanimation chooser. Here are a few threads with lots of bootanimations to try. Some may need to be resized. You don't need the flashable (cwm) versions with the bootanimation choooser, just download the bootanimation zip files and rename as you like to whatever.zip. ;)

[Boot Animation] [12/04/11] A Huge Collection of Boots ~ Updated - xda-developers

[BOOT ANIMATION] The Droids - xda-developers

Boot Animation Index

What?!?
[Optimus V Android Development] tdm:
Thing is, with this phone, there is no such thing as being truly off with USB connected. The phone is going to boot up. It's just a question of whether it stops at chargerlogo or goes on to android.

The challenges we have are defining exactly what conditions stop at chargerlogo and which don't, and how to implement that. The set of conditions is a grid with rows:

Reboot selected

Power off selected

Neither (phone crashed, battery removed, etc.)

... others?

Each of the rows has a column for USB connected and USB disconnected.

Finally, the only indicator I've been able to find so far is that on a "warm" boot, the file /proc/last_kmsg exists. Really, all this says is that power has not been removed since the last boot. So it means some of the conditions one would expect to stop at chargerlogo don't (eg. power off selected while USB is connected).

I'm really not a hardware guy so if anyone knows where to find a few bits to store the boot reason in a non volatile place that would help tremendously.
[Optimus V Android Development] JerryScript:
Wouldn't the best place be /proc just like last_kmsg, perhaps a file named boot_args? Then we can check for a bit flag that would indicate the proper tail to add via init.c

Reboot mode | USB | noUSB

Power-off | charge | charge

Reboot | boot | boot

Crash | boot | boot

The only instance that needs to go to offline-charging is power off, I believe in both USB and noUSB cases so that plugging in the charger with phone off doesn't boot it up (since it's going to power on regardless of what we do). Crash should always boot to insure the phone doesn't get stuck in offline-charging mode (nite-time charging, alarms, calls, etc).

So all we should need is to write a single bit file to /proc when the user selects power off, and check for it in init.c like the last_kmsg file, I believe.

What I don't understand is why the phone is still booting up upon a power down when usb is plugged in, with the current code. The last_kmsg file is not present after fully booting from a power-off, so what is setting the tail? I can only assume last_kmsg is present, and deleted as part of the init or later processes?

Edit: I imagine the ShutdownThread.java would be a good place to write to the needed file.
[Optimus V Android Development] mrg666:
Tdm, what you have done so far has been awesome. After fixing the offline charging problem, I don't mind holding the power button a little longer to complete the boot or just unplug it before rebooting. Every device has such peculiarities and each of us has a brain to deal with it. Thanks for the explanation.
[Optimus V Android Development] JerryScript:
My concern is that with offline-charging enabled, if the phone reboots while plugged in, it goes into offline-charging mode. So if you charge your phone overnite, and it reboots for whatever reason, you won't receive phone calls, alarms wont go off, etc.

I'm working on a hack-ish fix, Blarf and Tom will probably have improvements to it.
[Optimus V Android Development] moore.bryan:
Me = frustrated

Once again--and for no apparent reason--I'm getting an insufficient space error when trying to update apps. Here's the thing, though: I'm running link2sd with a *huge* sdcard partition for apps.

Help!:-[
[Optimus V Android Development] deaver_92:
Open link2sd > menu > More > Link dalvik-cache files > wait until it's finished. That should solve any market issues. It does for me anyways.
[Optimus V Android Development] moore.bryan:
Thought of this one... It tells me no files are found. Thanks, though.
[Optimus V Android Development] deaver_92:
Have you already tried another method? It shouldn't say that unless the files aren't in the standard location.
[Optimus V Android Development] moore.bryan:
That's what I thought, so I checked /data/dalvik-cache and there were a bunch of dex files in there.

Sent from an IHO phone
[Optimus V Android Development] deaver_92:
Have you linked the files already? I just linked mine and then tried linking again and it said no files found.
[Optimus V Android Development] mjs2011:
choose link dalvik files in lin2sd
[Optimus V Android Development] deaver_92:
read the 5 posts after that.
[Optimus V Android Development] moore.bryan:
Not that I know of. Is there a way to double check?

Sent from an IHO phone
[Optimus V Android Development] moore.bryan:
5 posts after what?

Sent from an IHO phone
[Optimus V Android Development] deaver_92:
Not that I could find. Try this: navigate to /system/etc/init.d and move 01mvdalvik to your sdcard. This should also clear the error.

I was talking to the other person that replied to your first post.
[Optimus V Android Development] AzraelsKiss:
Make sure you're showing user apps in the filter (the thing that looks like an upside down funnel)... Select "multi select"... Then select "select all"... Then select "actions > create link"... Make sure all the things are checked... Then select "OK"...

~Azrael's Kiss~
[Optimus V Android Development] joryb:
I flashed to bobz 1-29 build from his last build and my GPS no longer will work. I cleared dalvik b4 flash and checked md5sum. GPS wont turn on from the scroll down menu or in the settings. I check all GPS settings on and still nothing. Any ideas. Bobz is my favorite rom I really don't wanna have to switch. I rely on my GPS making deleveries.

NM been busy see another build up ill try the 1-30 build. Bob your the man!
[Optimus V Android Development] moore.bryan:
Thanks for all the suggestions guys... I ended-up having to do a full wipe. What I still don't fully understand is why my internal fills-up when I install new programs when link2sd is set to put everything on my external memory.
[Optimus V Android Development] deaver_92:
Now that you've done the full wipe do this (naturally skip the steps you have done already):

-Restore link2sd first.

-Before restoring anything else open link2sd and select the ext type from the pop up to create the mounting scripts.

-Reboot and continue restoring apps.

-When finished open link2sd and set the filter to user apps then press menu, multi select, menu, select all, menu, actions, create link.

-When that is finished press the back button once, press menu, select more, and select "link dalvik-cache files".

You should be good to go from here. If you have any issues let us know.

Sent from the n_visible1's OV on BACKside
[Optimus V Android Development] moore.bryan:
The "link dalvik-cache files" still returns "no files found." On a related note, I had already done what you suggested, so I guess I moved up from noob level. ;-)

Sent from an IHO phone
[Optimus V Android Development] jawz101:
Download total commander for android and drill back down to the dalvik folder you mentioned. It shows linked files as linked. Total commander isn't in the market but it's herehttp://www.ghisler.com/android.htm

In link2sd you can also click on an app that says it's already linked, then hit create link. There it will show you if the dalvik is already linked
[Optimus V Android Development] bennettg:
i am a noob and just put on this rom. thank you to the developers, you have given new life to my optimus v.

one question: when i plug my phone in via usb to my windows computer, it doesnt recgonize it. am i doing something wrong? do i need an app?

thanks in advance/
[Optimus V Android Development] dingermtb:
Make sure Debugging is on. It's under Applications in Settimgs menu. Also may need to reinstall LG drivers.
[Optimus V Android Development] bennettg:
I didnt find debugging, but i'll keep looking.

Do you know where i find LG dirvers? Do I need them on my computer if it recgonizes my phone with the bumblebee rom?

thanks once again. i very much appreciate your help
[Optimus V Android Development] deaver_92:
Strange. Very strange. The only other thing I can suggest is to do what jawz101 said. Or move 01mvdalvik out of the /system/etc/init.d/. Or both. I'm out of ideas. :-P

Sent from the n_visible1's OV on BACKside
[Optimus V Android Development] deaver_92:
Debugging is under settings/applications/development. If you search this forum for "drivers" you should find a link. Or go to the LG website and download them from there.

Sent from the n_visible1's OV on BACKside
[Optimus V Android Development] dingermtb:
Menu-->Settings-->Applications-->Development. Make sure Android Debugging is checked. LG drivers are posted somewhere here or you can get them straight from the LG site. Also, there's a PC app called ROMtools and it'll install the drivers for you. There's a thrwad for in here under the Android Hacking and Developement thead. I'm pretty sure it's under there.

Found the link for ROMtools http://xdaforums.com/showthread.php?t=974621
[Optimus V Android Development] bennettg:
Thanks. Do I need drivers if my windows computer mounts the USB when using bumblebee rom? Or is there something else? I found the debugging and its enabled

Thanks again
[Optimus V Android Development] dingermtb:
If the computer sees your phone and it mounts, you should be good to go. Otherwise, uninstall all LG drivers and reinstall. If you install new LG drivers over previous ones, sometimes you'll get conflicts.
[Optimus V Android Development] a5pe4:
That hasn't worked for me in a while haha. At least every once in a month I'm able to miraculously update an app or two. Frustrating problem but oh well.
[Optimus V Android Development] leolawliet:
I had no idea Total Commander existed for Android, thank you :)
[Optimus V Android Development] mkoyskip:
And now for something completely different...

Came across a new issue lately - sometimes when my stock alarm goes off I lose the lock screen/desktop when I dismiss the alarm. This does not always occur but it has happened about 50% of the time.

It seems to unlock (my wifi or 3g will enable) but I cannot use my phone and must reboot.:confused:

When I press the power button the Phone options menu appears and the desktop appears in the background for an instant. When I press clear/back the Phone options menu disappears, the desktop appears for a moment, and then all I see is the wallpaper & status bar (cannot access).

EDIT:

Ok, just posted this a few minutes ago but I've been working on this for a while now. I've been able to reproduce this problem and it only seems to happen when the phone is in landscape mode, portrait seems fine. Pressing snooze causes the same problem.

I guess next is to try another clock app to see if that also replicates the problem - any suggestions on a good alarm clock app? Also, does anyone know if I need to keep the clock (DeskClock.apk) or can I disable it if using another app?

tanx.
[Optimus V Android Development] moore.bryan:
Thanks to everyone who tried to help out, especially deaver_92 for great suggestions and jawz101 for TC... I'm so happy to see it exists for Android!

I think my issue is either resolved or impossible to fix. No matter what I do--including moving that "special" dalvik file--link2sd tells me there are no files to link; however, when I ask it to clean-up linked files, it does. Perhaps the issue is with link2sd rather than the ROM or Android.

Like I wrote previously, though, I still don't understand why if all my apps are housed on my sdcard--which I can confirm they are, except for the handful of "system apps" I've left on internal--why is my internal storage so full.

Perhaps a question for the ages?

Sent from an IHO phone