yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Accessories] jGroves:
I ordered the front Invisible Shield for my Incredible & it cost me $14. If you sign up to win the free iPad on their site they'll send you a discount code which makes the price of the shield cheaper. When I got it in I had no problem installing the screen; however, when I tried to squeegy it I stretched the screen out a bit and it looks kind of scratched. Since the product is suppose to be indestructible I emailed Zagg and told them about it. They agreed to ship me another one for free! At first the screen feels a bit rubbery, but you get use to it and it's great protection for the screen. I hardly even notice it anymore and I can still flick and scroll just as if the shield wasn't there. I'd recommend the Zagg screen, but I haven't used anything else ever.

I also ordered a pair of Zbuds and they're awesome headphones. Sounds like a theatre in my head.

I love Zagg products.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Incredible Accessories] mpfuzz2:
I have used the ZAGG on my G1, my Droid and now my Incredible. It can be a little difficult to apply, but it works awesome. I even dropped my G1 once on cement and it didn't scratch it up. Just be patient in applying. The liquid doesn't harm the device at all and after a day, you do not notice any "spider cracks" as you mentioned. I would stick to ZAGG so far in my experience.
[Droid Incredible Accessories] TooSlo:
I bought a pair for the phones I bought for my wife and I but I'm really let down with the plastic feeling when you run your finger across the screen.

I'd always loved the matte screen protectors we had for our iphones. They didn't pick up fingerprints and your finger slid nicely across without any tacky feeling.

$.02
[Droid Incredible Accessories] rfarrah:
Best Buy installed mine and did a great job. I kind of messed it up a little on a corner when I tried to put on a silicone case, but it's okay.

Looks like one of my wife's earrings dented the protector over the weekend, but that's what it's there for. Wish it was a little tougher, but overall I'm happy.
[Droid Incredible Accessories] mrchambo:
Steinheil Crystal Clear. Da bomb. No liquid, super easy install. 2 for 13.41, shipped. Fast service, great product.

Nuff said.
[Droid Incredible Accessories] freebirds87:
It's good to hear that! I work for best buy mobile, so I get to install a good bit of Zagg Protectors. Anyone who isn't comfortable doing it themselves should go to Best Buy, because we guarantee our work.
[Droid Incredible Accessories] Xxq TZ pxX:
Just installed my first Zagg full body protector a few days ago, and I love it! It doesn't degrade the touch response, and I don't mind at all how it feels. After studying several Zagg installation youtube videos, it was pretty easy to install. It provides great protection against scratches; better than the standard Verizon screen protectors. Big Thanks to everyone who recommended Zagg.
[Droid Incredible Accessories] gospeed.racer:
so am I the only one that received a shield that is oversized? It hangs over the LCD enough to allow a visible air gap, creating a void that looks like crap. I took it off immediately, as there was no way it was going to shrink. Back to the cheapies until Zagg decides to answer my email.
[Droid Incredible Accessories] elbebo:
50% off Zagg.com!!

50% off site-wide at Zagg.com only for memorial day. I just ordered the full body protection and the Black/Red Zagg-buds for my new Incredible! It doesn't allow you to place any other coupons at checkout (or at least I didn't see anywhere to do it). Check it out here:

http://www.zagg.com/
[Droid Incredible Accessories] mach1man:
Does every best buy install these Zagg protectors and will they also do full body protectors? I like the way the phone looks naked.
[Hero CDMA Themes and Apps] JsChiSurf:
Edit: 6/9/2010, Added OSU themed Rotary Lockscreen (see below)

I put together modified / themed vanilla & rotary lockscreens to show my love for my favorite team, and figured I'd share them with any other Buckeye fans that may be out there.

These lockscreens incorporate the mods I made for removing the text elements on the vanilla lockscreen, and rotary lockscreen as well.

For the vanilla lockscreen, I also modified the Slider Bars to incorporate the helmet sticker, and also modified the text on the slider bars to theme them as well.

Given the nature of the changes, I decided to go ahead and make these available as a MetaMorph files. These are NOT FLASHABLE ZIP FILES. You can download the free version of MetaMorph in the market and apply the theme using the MetaMorph application.

For all you fans of tOSU, enjoy :).

Vanilla Lockscreen Download:

XML MetaMorph Control File <--- Apply using the latest MetaMorph Application

THM MetaMorph Control File <--- Apply using any older MetaMorph Application

Note: MetaMorph tends to have trouble applying changes to multiple framework files in a single morph, which this mod includes, and as such, applying the MetaMorph may require multiple tries. If your phone freezes / reboots when attempting to apply the final step, it may come back up with only some of the mod/theme applied (you'll still see the black taskbar). If this is the case, apply the MetaMorph again, this time, only selecting the final sub-theme, 'framework-res.apk'.

Reference:

Rotary Lockscreen Download:

XML MetaMorph Control File <--- Apply using the latest MetaMorph Application

THM MetaMorph Control File <--- Apply using any older MetaMorph Application

Note: MetaMorph tends to have trouble applying changes to multiple framework files in a single morph, which this mod includes, and as such, applying the MetaMorph may require multiple tries. If your phone freezes / reboots when attempting to apply the final step, it may come back up with only some of the mod/theme applied (you'll still see the black taskbar). If this is the case, apply the MetaMorph again, this time, only selecting the final sub-theme, 'framework-res.apk'.

Reference:

For a matching OSU themed Swype Keyboard (with modified/matching path color), see here.

Reference:
[Hero CDMA Themes and Apps] JsChiSurf:
Come on now, am I the only Buckeye's fan in this forum :)?
[Hero CDMA Themes and Apps] thatjerk:
Yes... yes you are.

Regardless, good job on the lock screen.
[Hero CDMA Themes and Apps] johnsongrantr:
what the hell is a buckeye supposed to be anyway? A nut or something?

I guess so...

http://en.wikipedia.org/wiki/Aesculus_glabra
[Hero CDMA Themes and Apps] aauussttiinn88:
DAAMN i was playing around with one that had a OSU helmet crashing into a michigan one..this looks sweet tho thanks a bunch JA! im from ohio so ive been a buckeye since i came out the womb! OH! :cool:
[Hero CDMA Themes and Apps] JsChiSurf:
Now we're talking, IO.
[Hero CDMA Themes and Apps] JsChiSurf:
:D 10chars
[Hero CDMA Themes and Apps] JsChiSurf:
A Poisons nut, no less.
[Hero CDMA Themes and Apps] aauussttiinn88:
yea hopefully this whole thread is either michigan fans.....or oregon lol because i can still smell those roses :D...on topic your work is sick and much appreciated cant wait to show the boys in the office this one
[Hero CDMA Themes and Apps] thatjerk:
Great now they are breeding.
[Hero CDMA Themes and Apps] Brutus2TheMax:
Good work man! I'd love to see a lock screen with Big Al...
[Hero CDMA Themes and Apps] nebenezer:
Just exactly how do you get by posting 2char posts?

just curious
[Hero CDMA Themes and Apps] pwrmedia:
Completely useless unless you come up with a Wolverine one.

I'm just saying.....would be nice, is all. :D
[Hero CDMA Themes and Apps] JsChiSurf:
Hint, LemonChiffon is your friend...
[Hero CDMA Themes and Apps] thatjerk:
Just like this
[Hero CDMA Themes and Apps] JsChiSurf:
I had a version that had the Wolverines incorporated, but probably not what you were looking for :).
[Hero CDMA Themes and Apps] pwrmedia:
I'll bet...ya bastid. j/k lol
[Hero CDMA Themes and Apps] brian m:
download
[Hero CDMA Themes and Apps] tzbf2006:
O - H! Love this theme!
[Hero CDMA Themes and Apps] JsChiSurf:
That's sweet. Post it up, if you want, and I'll link to it in the OP.
[Touch CDMA Android Development] myn:
[APP] RogueTools v1.1 - [Overclock & Change Screen Density] - [Updated: 04/27/2010]

I now present you with RogueTools v1.1.

Summary:

This application is designed for the Vogue, Kaiser, Polaris and Nike devices. It allows you to dynamically overclock your device as well as change the screen density.

Requirements:

This application requires write access to your /system so this will only work on EXT2 and NAND installations.

Overclocking Notes:

Overclocking results will vary. Based upon the beta test results everyone was able to Overclock to 500mhz and have very stable results. Above this results really were mixed. Give it a try, I'd love to hear your results.

To download, search in the market for "RogueTools"

Screenshots:

Before (400mhz) and After (500mhz) CaffeineMark Benchmark

HUGE thanks to all of the beta testers. You guys did an outstanding job!:

citrit, cp0020, damianiw, DmK75, dzo, GriloVirante, Incubus26jc, inertone, jnadke, mblaster, Millence, mssmison, paipo, pyrator, scouzer, vrflyer

Disclaimer:

As always, I’m not responsible for anything that happens to your phone while using these files.

Future Versions:

I'm looking for some creative ideas on other additions you'd like to see added to this application. So if you have some thoughts, please let me know.

Changelog:

04/27/2010

Added device support for Nike

04/24/2010

Version 1
[Touch CDMA Android Development] myn:
*Reserved*
[Touch CDMA Android Development] fldash:
Overclocking significantly reduce battery life?
[Touch CDMA Android Development] incubus26jc:
sweet, I dont have to keep it secret anymore haha. Great job myn!! I havent had any issues with this in the month ive been using it.
[Touch CDMA Android Development] myn:
I've kept mine clocked at 500mhz for the past couple of weeks and haven't noticed a huge degrade in battery performance.

What's your results been like Incubus?
[Touch CDMA Android Development] incubus26jc:
No difference in batterylife no matter what im clocking at. Do i need to upgrade? Is the final version changed from the version im using?
[Touch CDMA Android Development] myn:
Just a few minor tweaks. Mostly cosmetic. Probably worth the upgrade anyways.
[Touch CDMA Android Development] cp0020:
i didnt have any problems at all. ran faster/ battery life was good. like incubus said....don't have to keep it a secret anymore lol
[Touch CDMA Android Development] scouzer:
oh noes i was forgotten as a beta tester :( lol

my results if anyone was wondering was a stable 550mhz 24/7.
[Touch CDMA Android Development] jnadke:
I see you got the density changing script working?

Cool app.
[Touch CDMA Android Development] cp0020:
550mhz!?!?!?!?! you must not be on a vogue? lolol
[Touch CDMA Android Development] myn:
I am soo sorry scouzer :(. I feel like the biggest idiot.

I've updated the first post accordingly.

Sorry about that.
[Touch CDMA Android Development] cp0020:
im the 2nd name mentioned. i feel special :) lol
[Touch CDMA Android Development] incubus26jc:
its in alphabetical order special boy. lol
[Touch CDMA Android Development] cp0020:
well........shut up!!! lol

thanks for ruining my moment haha
[Touch CDMA Android Development] vinny13:
Will overclocking make my phone crap out any faster then not? Like bringing it up to 500mHz or where still stable won't make it run too hot and stuff? Just wonderin' cause my phone can get pretty warm with good web use and whatever...

Do want, though.
[Touch CDMA Android Development] corypaul:
can someone post this app cuz i dont have data on my xv6900
[Touch CDMA Android Development] inertone:
aww come on i was a beta tester toooo lol

500mhz works wonders!
[Touch CDMA Android Development] cyburke:
very very cool
[Touch CDMA Android Development] corypaul:
plz anybody
[Touch CDMA Android Development] TheKartus:
I third that. Can you host the apk somewhere?
[Touch CDMA Android Development] kallt_kaffe:
First of all, very nice application. What you are about to read is not complaints, it's suggestions.

At what CPU frequencies is the AHB_DIV parameter changed?

I'm a bit of a controlfreak when it comes down to things like this and I wouldn't mind if the AHB_DIV (and why not the calculated AHB frequency) was shown in the app when pulling the slider.

And for the brave (and/or stupid), a checkbox to uncheck to allow manual control over the AHB_DIV?
[Touch CDMA Android Development] myn:
Good suggestions, I really appreciate this kind of feedback.

I was actually originally thinking about adding the busSpeed parameter as a configurable option but I thought it may get alot of questions so I made the decision to calculate this automatically based upon the Frequency chosen.

After talking to dzo about the thresholds the following is what I am using:

try {
// Determine what freqTable divider we should use
String busSpeed = (freq > 400) ? "4" : "3";

..
..

With that said, I would like to accommodate your request. Expect control over this parameter in the next release.
[Touch CDMA Android Development] myn:
I really really feel like a dufus now. I think this past week's vacation has melted my mind away!

I've added your name to the growing beta team list in the first post.

I feel embaressed by it :(

Sorry.
[Touch CDMA Android Development] jlitowitz:
Any benchmark tools available?

Hi,

Can someone point me to a benchmark program to confirm this is doing anything on my Vogue? I see a few in androlib.com but they don't show up in the Market on my device for some reason.

I'm pretty sure this program is having an effect - at least, when I slide the CPU speed scale all the way up to 600, press the red 'end' button, then re-wake the device, it locks up every time, so it does seem to be having that effect. I was just hoping someone could point me to a benchmarking tool so that I can test my device at various speeds to determine stability (I'd rather have it crash on a benchmark than in the middle of a phone call, for example!).

Should it matter, I'm running myn-warmdonut-rls4 at 240x320.

Thanks!
[Touch CDMA Android Development] j8971:
Just downloaded. Thank you for your continued efforts in updating the vogue.:)
[Touch CDMA Android Development] xport:
Awesome, thanks myn!

Anyone else have trouble selecting 500mhz? i can get 499 and 501. Not important really just worth mentioning i thought.
[Touch CDMA Android Development] cp0020:
i had that problem too. till i did a soft reset then i was able to select it. try soft resetting and see if that helps
[Touch CDMA Android Development] cp0020:
are phone run pretty good with it set to 500mhz. but anything past that and the results may vary. some phones are different than others so 1 phone could run much better with it set to 500mhz but the other could have some side affects with it set to 500mhz
[Touch CDMA Android Development] xport:
Nope, still same, Im at density 100.
[Touch CDMA Android Development] cp0020:
hmmmm.... reinstall the app and that should fix it. why are you at 100 lcd? lolol
[Touch CDMA Android Development] xport:
OOps! 110. What are you running?
[Touch CDMA Android Development] cp0020:
well my phone broke last week but i think i was running 160lcd/500mhz
[Touch CDMA Android Development] xport:
160 makes the icons HUGE! am i right?
[Touch CDMA Android Development] cp0020:
if your running 240x320 then yes. but i use 320x480. for 240x320 try anywhere from 110-120
[Touch CDMA Android Development] jlitowitz:
Don't get me wrong, I'm not expecting the machine to run 50% faster than stock speed. I tried bumping it up to 600 expecting it to fail if it was in fact doing something (which seems to be the case). I was more looking to see if there was a tool out there to quantify the improvements when I run at 500, and/or to test stability at higher speeds.
[Touch CDMA Android Development] fldash:
I'm also having trouble selecting exact values. I can't select 500, only 498 and 502. I'm running 320x480 and 160 density. I didn't modify my densite to 165 and I like it better, but I still can't select 500 exactly. It's not that big of a deal.
[Touch CDMA Android Development] cp0020:
reinstall the app and see if that fixes it
[Touch CDMA Android Development] fldash:
Already tried that... it doesn't...
[Touch CDMA Android Development] corypaul:
can some one post me the app plz i need this
[Touch CDMA Android Development] jlitowitz:
Ok well call me impatient - plus, I'm trying to dabble in Android programming - I wrote the attached. It's a stupid little program that calculates Pi to a few digits of precision using the Gregory-Leibniz series... Anyway, if you run the program you get a Start button. Click it and it'll return with a (BAD!!!) approximation of Pi, and tell you the number of milliseconds it took to calculate using 300000 members of the series.

I ran it a total of 12 times on my Vogue, switching between 400 MHz and 501 MHz (I can't get the slider to select exactly 500). My results show a definite effect of RogueTools!

Starting at 501MHz I got 1771, 1824, 1756.

Switching to 400 I got 1978, 1984, 2077.

Switching back to 501 I got 1716, 1736, 1670.

Switching back to 400 I got 2063, 2097, 2108.

I think it's safe to say this overclocker is definitely having an effect. :)

Thanks!
[Touch CDMA Android Development] mssmison:
This uses the overclock code as laid out by DZO, I like it, great job! :)
[Touch CDMA Android Development] GeJohnO:
Thanks for the app myn... it's working great!

As others have said, I can't put the ticker to an exact value on 120 dpi. It fluctuates between 499 and 501. I think it's more of an OCD issue on my part, but maybe on the next build can we have a custom field to enter a numeric value?

Thanks again for all that you do! You never cease to impress!!
[Touch CDMA Android Development] corypaul:
Please Anybody
[Touch CDMA Android Development] kallt_kaffe:
Here you go. Have fun!
[Touch CDMA Android Development] slow88lx:
Maybe you should break out the Android emulator and start downloading the apps yourself.....
[Touch CDMA Android Development] tempe38:
I ran my cpu up to 550, we'll see how that goes. So far so good.
[Touch CDMA Android Development] sshark:
Phone is not sleeping after overclocking...any suggestions?
[Touch CDMA Android Development] cp0020:
hey i was looking for this android emulator. where can i get it?
[Touch CDMA Android Development] GeJohnO:
It is a tool when you download the SDK.

http://developer.android.com/guide/developing/tools/emulator.html
[Touch CDMA Android Development] corypaul:
please tell me how i ask and people said they didnt know how to do it, i already got the SDK and i am running a emulator so how do i put market on it so i can download apps
[Touch CDMA Android Development] slow88lx:
I actually don't know(I have a data plan), I just remember seeing someone post about it somewhere.
[Touch CDMA Android Development] incubus26jc:
myn, is it ok to include your tool in my releases now? Or do you want people to have to download from the market? I understand if you dont want me to.
[Touch CDMA Android Development] tempe38:
Nope, locked up twice now, dropped back to 502.
[Touch CDMA Android Development] josh s:
My Vogue seems to be running just fine at 550MHz. really nice speed/response improvement!
[Touch CDMA Android Development] cp0020:
yes same here. there is no option for market. i just wanna mess with this till i get my phone back
[Touch CDMA Android Development] cp0020:
found something HERE.it will only work with android emulator 1.5 and 1.6. trying it now
[Touch CDMA Android Development] myn:
CaffeineMark is a great tool to benchmark the overclocking. I've used this in my testing.
[Touch CDMA Android Development] myn:
I hear yeah. My conundrum is I wanted to have 1 MHz granularity in a slider control. And with our resistive touch screens it's not 100% accurate all of the time.

Until I come up with a better solution, you can use the dpad (left and right) to adjust the finite MHz and set it to preciously 500mhz.

I think in the next release I'll have a manual override with a textbox allowing you to specify explicitly.
[Touch CDMA Android Development] myn:
Sure, feel free to include it in your release.
[Touch CDMA Android Development] jlitowitz:
Unfortunately, this doesn't show up on my Vogue in the market. :( Oh well. At least I know it's working. Thanks for the great work!
[Touch CDMA Android Development] deltagamer:
soooo ummm I installed this and rebooted my phone and now its stuck on the "x" whispy thing (eclair). It won't load... thanks.
[Touch CDMA Android Development] JM-PDA:
Same here.

No "CaffeineMark" found in my Android Market.

Running Myn's Rlse-4 with Android Market Fix "Tattoo-Market-patched".
[Touch CDMA Android Development] tempe38:
I never got that market fix to work when I needed it. Don't seem to need it on Myn's Warm Donut at 320x480/160. I've been able to find everything I wanted, including this app, since installing it.
[Touch CDMA Android Development] inertone:
ill upload it shortly :)
[Touch CDMA Android Development] mikevillarroel:
Overclocked to 500mhz and it's working well(i don't know what to spect anyways) but what i did notice is that anything over 160 Dpi won't let the beautiful widget animation to show up when you hit the weather.
[Touch CDMA Android Development] myn:
Search for benchmark
[Touch CDMA Android Development] vinny13:
For CaffieneMark, I'm assuming a higher overall score is better?
[Touch CDMA Android Development] jin5:
i'm running at 531mhz and previously 500mhz, no crashes yet.

however i do notice, sometimes my notification bar can't be dragged down but i'm not sure if thats a result of overclocking.
[Touch CDMA Android Development] vinny13:
What kinda results am I supposed to see with this? It seems like every frequency I test over 500 give the same results, which is like the same as 400 :/
[Touch CDMA Android Development] drkow19:
I got 19.5 fps in Neocore before o/c to 510, then I got 22.5 fps. Results may vary depending on what you have running in the background or widgets or if you rebooted recently.
[Touch CDMA Android Development] cp0020:
the most iv'e gotten on neocore was 27.3fps
[Touch CDMA Android Development] drewden123:
I'm running great at 498 atm. Also, when I was low on battery, I underclocked to 306 and my battery at least seemed to last longer and the phone was stable too.
[Touch CDMA Android Development] myn:
In the Kaiser forum some users discovered that if they changed the density to a really low value their roms wouldn't boot.

Has anyone found the lowest threshold for density changing?

I'd like to make this the starting point for the next version so people don't mistakenly put it to low.
[Touch CDMA Android Development] kallt_kaffe:
Well, I tried 107 once while running 240x320 and while it would boot the status bar didn't draw the clock correctly.
[Touch CDMA Android Development] fldash:
myn, have you considered expanding this app to work like setcpu? I really would like to see an option to change the processor speed based on cpu load. Thanks!
[Touch CDMA Android Development] myn:
Yeah I was thinking about cutting back CPU when it sleeps but I have a really really strong feeling dzo has implemented this into the kernel when we gained that huge jump in battery performance a month or so ago.

I will have to check with him when he gets back from vacation.

As far as dynamic CPU throttling based upon CPU load. Unfortunately the only way we can currently commit the clock frequency change is when the phone sleeps.

Is this what you were referring to or ?

Great question.

Thanks.
[Touch CDMA Android Development] berardi:
Myn, just wanted to say this is working great for me. I'm at 510... it definitely seems snappier, and I haven't noticed much difference in battery life.

Awesome work! :)
[Touch CDMA Android Development] fldash:
Cutting back the CPU while the device sleeps would indeed be fantastic. Maybe dzo does this, but if not, it'd be a great addition.
[Touch CDMA Android Development] mrkite38:
I'm pretty sure it's in there. That's why the o/c doesn't take effect until you sleep and wake the phone - if the clock speed was always the same, there'd be no call to change speed on wakeup.