yashsingh1/xdaforums huggingface dataset:
[Droid X General] bouchigo:
You can try using "Battery Left Widget" from the market, it's free. It does 1% increments and decrements.

It uses algorithms to calculate the battery reserve as you use charge and discharge your battery and gets more accurate as you go along. You want the bar to be full green and not have any red under the "Accuracy" tab.

Screenshot of battery reading (Note: I still have a lot of red on the accuracy bar):
[Droid X General] Enndr:
Awesome..! Thanks for this! :D
[Droid X General] bouchigo:
No problem, hope it also helps out others. :D
[Droid X General] jayinla:
Sorry to go off topic but does anyone know which weather clock widget is in the above picture?
[Droid X General] bouchigo:
It's called "Moxier World" but I switched to "WF & Clock widget", I like it better.
[Off-topic] Senax:
DOS 6.2 Tutorial in a Command Line Interface;

At the risk of revealing my age, ...

Once, a long, long time ago (unpack it and you can start guessing :) ) a good digital_friend send me this directory. I think I obtained it at first via

FidoNet

:o Then later I obtained this newer attached version via

BBS

:p

Though zipped it before upping it of course. ;)

[TUT] A nice compiled dos Tutorial :) 2010-August-8th here on xda-developers.com :D

Screenshots;

Of course one can unpack it and run it, though ...

Maybe this ADMiN at WORK method is something to write down <g>

@ECHO OFF
REM below the dos screen is set to show 50 lines in a box (15" CRT monitor). Don't go about and fill in a ridiculous value; you'll get to reboot your precious session! Because you can 1st read the provided manual ;-)
[COLOR=Red]MODE 80,50[/COLOR]
C:
CD C:\PROGRA~1\DOS6T\
HTUTOR.EXE
:END
EXiT

This batch file assumes you have unpacked this zip to C:\Program Files\*

1. Copy and paste the above code in a text editor and save it with a short (8.3) name of your choice.

2. Then rename the *.txt file to *.bat and double click it. (Mine's called Htut6.bat)

3. Press a key to continue...

4. Go to the Advanced Topics for a nice overview.

When you're done and quit the program, I advice to make a shortcut to your *.bat file;

LongPress_RightMouseButton the *.bat file - wait for context menu and select Create Shortcut (move/rename it to your liking)!

Q: Are there still people using DOS? And batch files??!

A: Chef's do! Don't you? :p

Note;

I never used this tutorial, due to the fact that I used Novell DOS (NDOS) and later moved to JPSoftware its 4DOS (which was a collaboration between NDOS/4DOS) later it was called 4NT command line interpreter (which was making overall dos operations go so much more faster, due to batch files which could/(can) be compiled easily).

Have a nice day/night,
[EVO 4G Q&A, Help & Troubleshooting] foxgrey:
Pretty much what the title says, Does the evo have any RFID capabilities? I've tried searching but haven't unearthed any solid info as to yes or no.

I'm assuming not, but I'd love to be able to read and emulate a few of my rfid enabled pass cards.
[EVO 4G Q&A, Help & Troubleshooting] Iceman5000:
No rfid hardware on the evo.
[EVO 4G Q&A, Help & Troubleshooting] manooti:
jesus christ are you kidding me!!! rfid?!?!?! wow man, im sorry but im totally against rfid and if people start asking for rfid enabled phones im out of the android scene.

i dont mind being tracked with gps because we know what we're getting into and we can turn it off or leave it at home but man.. wow rfid.. youre nuts. im sorry

no trolling intended :x

putting on my tin foil hat now
[EVO 4G Q&A, Help & Troubleshooting] foxgrey:
*Thanks Iceman thats what I thought, but wanted some confirmation.*

Better make a really big hat then...

Seriously though its coming, having the ability to read a rfid tag on the phone would open up huge possibilities. I know Apple was rumored to have played around with it, and I swear I saw some phones over in japan and possibly in the netherlands that have this.

Now I certainly understand the desire to not have a passive tag on your phone, especially if it stores your info.

But having the option to switch the tag(what info it has stored), and an option to enable or disable it would rock!
[EVO 4G Q&A, Help & Troubleshooting] manooti:
i see the pros and cons of rfid but the cons outweigh the pros.

nys was going to be the first with rfid license but from what i remember, dont quote me if im wrong, was that it was taken down because no one accepted it.

i wouldnt be in favor of a true rfid be it in our new passports, licenses, implanted or not. the drivers license was called "real id act".

the rfid brings back a memory from 2001. after 9/11 a family opted in to be the first with the "rfid implants". the mother was on tv and speaking for the family saying how "safe" she feels now being monitored 24/7.

verichip was on cnn years ago and if you google you will find more info on it..

verichip was merged with positive id corp, http://www.positiveidcorp.com/about-us.html

virginia delegates pass bill banning implants, feb 2010:

http://rawstory.com/2010/02/virginia-passes-law-banning-chip-implants-mark-beast/

rfid chip with cyanide lol: http://www.youtube.com/watch?v=JmhjffYxspg

verichip implant commercial http://www.youtube.com/watch?v=hButF_Effn0

im going into hiding now lol.

rfid pffffft :cool:
[EVO 4G Q&A, Help & Troubleshooting] JackDaniels7:
Govmet Came and took ma baby. lol

bust out lead hat (cause tinfoil is for the wanabees) and starts chanting BIG BROTHER!!

but in all seriousness there is no way in hell i want an RFID in my phone

in my dog fine but not my phone
[EVO 4G Q&A, Help & Troubleshooting] frogomatic:
Um, I think the OP was talking about an RFID reader.

I don't want an RFID chip in my phone. I'd love to have an RFID reader though. The non-paranoid among us could use it for inventory control, keeping track of where our keys are (assuming there's signal strength), etc. And the paranoid among us could periodically scan ourselves to see whether Big Brother had slipped a microchip into our nether regions while we slept. :D
[EVO 4G Q&A, Help & Troubleshooting] JackDaniels7:
don't you know the nether regions are to obvious they stopped that a long time ago you know those sinus headaches you get. yeah thats right it's behind the eyeball now cause no one would go digging it out from behind the eye (wow i actually sound like a metal hat wearing crazy. i need some soap i have to wash off the redneck back in 20 lol)
[EVO 4G Q&A, Help & Troubleshooting] manooti:
im tellin you man.. we gotta head for the hills!!!!

a reader would be cool though, hack that and impersonate anyone ;)
[EVO 4G Q&A, Help & Troubleshooting] sprink0281:
Gotta love the family guy quote!
[EVO 4G Q&A, Help & Troubleshooting] JackDaniels7:
ok i'm back (note to self steel wool does not help wash off redneck the blood only makes it redder)

but in all seriousness a scanner wouldn't be bad it would be interesting to see whats Rfided. (< to live in a world where thats a word) though i wonder how many crazies it would have running around scanning everyone lol.

hold on sir i cant pay you tell i check to see if the govmet tagged you. What! No I'm not psychotic don't make me chase you tinfoil doesn't stay on real well in a breeze!
[EVO 4G Q&A, Help & Troubleshooting] manooti:
anyone willing to get chipped so the devs can have a go at hacking it? lol
[EVO 4G Q&A, Help & Troubleshooting] flyingwolf:
Are you kidding PLEASE PLEASE PLEASE put active chips and readers in the phones.

Then XDA can hack the hell out of em and we will be getting free cokes and snickers bars at the mall all day long, wave your phone and "some cash machine in bumsville Idaho spits out money all over the ground" muahahahahahaha, just call me ultralazer!

/goodnight.
[EVO 4G Q&A, Help & Troubleshooting] JackDaniels7:
and then every phone would get a brick chip like the droid x and we would never get to play with our root(<see what i did there :D) again
[EVO 4G Q&A, Help & Troubleshooting] flyingwolf:
Amd then XDA would own the brick chip as well, if it can be made, it can be broken. It just takes time and skill.
[EVO 4G Q&A, Help & Troubleshooting] JackDaniels7:
the point is that what was once an open dev community would turn into a media nightmare sure it would be cool for a week then every govmet agency would be on google to lock it down and another fun playground would be forever destroyed
[EVO 4G Q&A, Help & Troubleshooting] flyingwolf:
I still belong to MANY forums that were supposedly destroyed, and we thrive just fine, it just takes a little more than googling our names to find us now.
[EVO 4G Q&A, Help & Troubleshooting] JackDaniels7:
first of all that doesn't impress me at all most of us here belong to atleast one (dead) forum or somthing. but the point is that should not be how it is. ruining something good and making it so only the people braking the rules get it is messed up
[EVO 4G Q&A, Help & Troubleshooting] flyingwolf:
I'm not trying to impress you, just stating that "having the guvment" come in is not going to kill the forum.

And the forums and groups I belong to are not dead, just not nearly as well known anymore. And we like that just fine.

As for breaking the rules, um, we do that every single day here, unlocking your phone for use with unapproved roms is breaking the rules. Get used to that.
[Captivate General] rrrrramos:
Trying to do some push/pull and do the new lag fix to no avail. After adb devices, the phone shows up as attached, but after adb remount I get "remount failed: No such file or directory" I'm not able to execute a push or pull command, and therefore I'm not able to run the lag fix.

I have USB Debugging selected, and I was able to delete the bloatware via adb shell, but none of the other commands go through for me...
[Captivate General] NOSintake:
Which version of Windows are you running?
[Captivate General] rrrrramos:
Windows 7 64 bit
[Captivate General] rrrrramos:
Still haven't found a fix to this, so I'll post up what I'm inputting and what I'm getting in return.

Here is the code I use to get into ADB and then attempt a remount:

cd C:\android-sdk-windows
cd tools
adb remount
remount failed: No such file or directory

When I try to push and/or pull, I get this:

adb push ./smoothcalendar.apk /system/app
failed to copy './smoothcalendar.apk' to '/system/app/smoothcalendar.apk': Permission denied

I've tried adb kill-server, then adb remount with the same issues.
[Captivate General] Bighurk:
currently experiencing the same problem...
[Captivate General] BretR574:
Do you have BusyBox Installer installed on your phone? I believe you have to have it installed in order to use Android SDK.
[Captivate General] rrrrramos:
I've got Busybox 1.17.1 on mine.
[Captivate General] rrrrramos:
I'm wondering, is this a problem at the computer level or at the phone level? I know the Vibrant had some issues with push/pull, but I see some stuff here in the dev thread (lagfixes, sideloader stuff) that if I run from my computer attempt push/pull commands that fail and therefore the thing I'm running (lagfix most recently) doesn't actually work and I'm stuck with a slower phone.

If its a phone issues, I can just exchange it under warranty, since I'm out of my 30 days. But I'm hoping it's not as I'd like to keep this one that other than this has worked great for me.
[Captivate General] BretR574:
When I first starting using ADB, I was connecting my phone like when I was using Windows Explorer to muck around on it. I had mounted the usb connection in the notification window. I kept getting errors when I tried to push/pull. I reconnected once and forgot to mount the usb connection and everything worked perfectly. Make sure the usb debugging is check marked in Applications in settings. Try to do the push/pull without using remount command and don't click on the USB connected notification option when you plug it in. I'm really new at this linux stuff so I could be wrong. I'm just trying to share my experience in hopes that maybe you're doing the same things I was doing before I stumbled onto the right way to do it.
[Captivate General] rrrrramos:
Hmm, odd, I've tried that very method many times before, to no avail.

I try it just now, and having no problems with push or pull. Works for me! Thanks!
[Nexus One Q&A, Help & Troubleshooting] SiNJiN76:
Anybody having this problem or have experienced it? If you have or know of a solution, could you help me out? Thanks.

All calls made to my GV goes straight to Voicemail. Not a single ring on the phone.

Oh, one weird thing is that I used to have my wife's number on GV as a secondary and weirdly all calls went to her number. I have since taken it off. could this be a clue?
[Nexus One Q&A, Help & Troubleshooting] oklahomatulsa:
I would try to look in your GV "settings. Check under "calls" tab and groups tab. Good luck:cool:
[Nexus One Q&A, Help & Troubleshooting] crachel:
I bet 'do not disturb' is enabled
[Nexus One Q&A, Help & Troubleshooting] SiNJiN76:
Yeah...checked all the settings...they all look good. 'Do Not Disturb' is unchecked. I did a bit of searching today...and it seems to be a GVoice bug.

WTF?!?! What the point of using it then? LOL.
[Nexus One Q&A, Help & Troubleshooting] ilostchild:
go to google voice on pc and set your phone number to it.. it could be still set on your Wifes, also try to make call with it then try to call it and see if that will help out
[Nexus One Q&A, Help & Troubleshooting] SiNJiN76:
Cool...I actually haven't made a call with it in a while...(maybe that's why...it's butt-hurt about me not using it to make calls?...LoL). My wife's number has been deleted off of it since I've been having this problem, but I'll try to make a call with it and see if that will make it work.

Thanks for the tips.
[Nexus One Q&A, Help & Troubleshooting] SiNJiN76:
Okay. I had google voice for international calls only. I figured that it was for out going calls only. I guess that because of that setting the calls weren't getting through? I understood it as all calls would come through if my google voice number was called...hmmm...guess they should fix that
[Motorola Droid and Milestone General] antonyfl:
http://xdaforums.com/showthread.php?t=679707&highlight=htc+music

so far the app works on the Milestone, but it doesnt fit on the native resolution, being that it was made for the G1. Wondering if anyone can port?
[Motorola Droid and Milestone General] mssmison:
probably better to use apktool on a hdpi version of htcmusic from the sense build.

I'd suggest either giving it a shot yourself, or pm the op of the linked thread and ask him if he'll do it for you.
[Desire Android Development] teppic74:
Normally you would be able to root the phone after downgrading to 0.80/1.21 from fastboot using this method:

http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/

It seems this fails though. If it can be made to work then the misc partition could be fixed, allowing the RUU update.
[Desire Android Development] Myshkinbob:
I'm not really a dev, in fact i only got my first android phone on saturday, but i'll add the info i discovered today.

Phone is an SLCD on non-rooted OTA official froyo (0.92 hboot). Like the OP points out, I needed to enable usb debugging on a 0.83 or lower hboot so that i could install a rooted recovery image. To enable usb debug you need a working screen, so that limits it to 0.83 hboot.

First i tried the 1.21.405.2_T2 RRU installer on my 0.92 hboot. It's installer window showed i had 2.09.405, and then trying to proceed into the bootloader resulted in the patch failing just after the signature check.

Next up i installed the recent 0.80 hboot rom that's been signed as 2.09.405 to enable downgrading. Killed my screen naturally. The earlier windows 1.21.405.2_T2 RRU gave a different result against it, equal version numbers of 1.21.405, but the bootloader still cried foul just after comparing signatures.

I was curious, so i broke out adb and fastboot, and snatched the rom.zip from the RUU installer, then used fastboot to reboot the phone into RUU mode. Manually flashing the rom.zip showed the signature passed fine, but there was an error 43 on the main version check. I did a getvar all on my phone and there it was, version-main=2.09.405.

So i rebooted the phone and loaded the windows RRU installer to get a response to 'adb devices' from my blank-screened phone, and had a look in the shell using adb. I haven't used linux in years but a little googling caught me up to speed that the 'vars all' values i'd seen are stored in the misc partition of the memory found at /proc/mtd, and misc itself can be altered through /dev/mtd/mtd0 (if my shell had root privileges, that is, bugger).

So i got a little out of my depth, but before i quit, i tried flashing the 0.80 engineering rom in that modaco thread using fastboot via the pc (r6-desire-root-alt.zip), and no joy with that either.

The short of it is the misc nand partition's version-main value is blocking any HTC signed sub-2.09.405 rom install progressing beyond the main version check in the bootloader/recovery. So far as i can tell it's comparing the misc partition value to android-info.txt within the zip?

So the 4 possible solutions i can think of would be either a mysterious signed-as-2.09.405 version of a 0.83hboot rom just like the 0.80 one, or a method of messing with the misc partition via an exploit, or thirdly enabling usb debug mode in a way other than using the phone menu, or lastly finding a way to install a rooted recovery rom directly on a 0.92 hboot.

Sorry that's a little long, feel free to move this post out of the thread.

P.S. forgot to mention i flashed back to the official OTA froyo as an upgrade.zip when i was done.
[Desire Android Development] teppic74:
Yeah, that sums up the situation. The r6 rooting method is blocked for the same reason as the RUU uploads, the wrong value in the misc partition.

It may somehow be possible to boot the phone from fastboot in a way that enables usb debugging, but I don't think it is. Alternatively it may be possible to install unrevoked3 after downgrading while in stock recovery mode, but that's unlikely (I can't try that, I have custom recovery).

Hopefully at some point 0.92/froyo will be rootable by unrevoked, which seems the most likely way of sorting this out.
[Desire Android Development] NChief:
Does the phone even boot up if you "brick" the screen..? if so you can use the trackpad to navigate the menus, kind a hard, but it possible.

Make sure you have disabled checking for SIM pin code. (possible to enter with trackpad, but extremely hard)

boot - wait - wait(wait long enough for sense and and usb menu do disappear but not the screen lock) - menu - down - left - down - down - trackpad - 10x down - trackpad - 3x down (bottom) - 2x trackpad
[Desire Android Development] SavageCore:
I was thinking about that NChief, maybe someone can test. But surely the downgrade re flashes the rom so it will be on the first run setup thing? need the steps to get through that?
[Desire Android Development] :
So you're saying step 1 from r6 root doesn't work either?

Mysterious 0.80 downgrade method was achieved by the chinese. Maybe they could do the same for the 0.83 .zip?
[Desire Android Development] :
I have a great idea, but it needs r6 root to work.

1. Downgrade from 0.92 to 0.80.

2. Use r6 to root the phone (an SLCD version of fake-flash ClockworkMod would be handy).

3. Extract rom.zip from 0.83 RUU.

4. Use fake-flash to get to recovery.

5. Flash rom.zip from step 3.

6. Root using unrEVOked.
[Desire Android Development] teppic74:
r6 won't work as it fails the version check. If it did it would all be very easy.

1. Downgrade to 0.80.

2. Use r6 to root the phone.

3. Apply update.zip misc partition fix in stock recovery.

4. Apply RUU.
[Desire Android Development] :
Let me flash a stock 1.21.405.2 ROM and write up instructions on how to enable USB debugging.
[Desire Android Development] teppic74:
As you said though, it will boot you into the setup screens. I think it does that each time you restart until you finish it. Also it will boot up with a locked screen, though I think the menu key will get rid of that in 2.1.

The downgrade method seems to be a leak from a friendly person at HTC, since it's a signed ROM. That's the only way to get by the version check without rooting. Another one which is based on the SLCD-compatible RUU instead would be perfect.
[Desire Android Development] :
I have an AMOLED screen. I will write up the steps, which will be the same for SLCDs.
[Desire Android Development] teppic74:
I understand, but what I mean is that someone without a screen won't be able to complete the setup screens (unless this is possible using the trackpad too?)
[Desire Android Development] :
I thought that the screen doesn't display anything, but touchscreen still works. Isn't that the case?
[Desire Android Development] teppic74:
I wouldn't imagine it would work.
[Desire Android Development] :
AFAIK the touchscreen is kept the same. Only the screen is changed.

layer 1 ____________________ <-- touchscreen

layer 2 ____________________ <-- screen (AMOLED/SLCD)
[Desire Android Development] teppic74:
If the touchscreen is the same then it may be ok, but I don't think anyone with an SLCD phone is going to risk downgrading to test the procedure...
[Desire Android Development] :
I have managed to do it without the touchscreen.
[Desire Android Development] teppic74:
That should be enough to fix it then.

Now we just need someone on stock froyo and an SLCD screen who wants root again to test it :)
[Desire Android Development] SavageCore:
It's tempting! ;)
[Desire Android Development] teppic74:
The updated custom recovery image for unrevoked3 will hopefully provide a working screen with HBOOT 0.80, but there's no way to find out without testing. Otherwise the recovery to fix the misc partition would be blind.

edit: though the fact that clockwork recovery without SLCD support doesn't work on HBOOT 0.83 suggests that the updated version will work fine on HBOOT 0.80.
[Desire Android Development] :
Ok, the instructions are here:
[Desire Android Development] teppic74:
I know it's a bit late after you've done all that work, but I think you may be able to get out of the setup screens by just pressing the home button.
[Desire Android Development] :
Tried, didn't work :).
[Desire Android Development] SavageCore:
On stock 2.2 after pressing menu it's down 1, right 3 to bring up menu?

Instead of
[Desire Android Development] :
What does Android 2.2 got to do with this :S? After flashing PB99IMG we get Android 2.1 and HBOOT 0.80 ;).

EDIT: I get it now. Thanks for the tip. Didn't think of that one :). but it has to be down x2. Once to highlight all programs, then once again to scroll to the bottom row.
[Desire Android Development] SavageCore:
Yeah I was just trying it out with a screen to verify the steps before the downgrade etc.
[Desire Android Development] :
Yes, we have a tester. I will contact you through PM.
[Desire Android Development] battletank:
Silly Questions

Forgive me if these questions have already been answered elsewhere, but I'm just looking at the problem and trying to assess alternative possibilities.

1. If you enable debug mode before downgrade, does the setting not stay set? Is a downgrade necessarily a complete factory wipe?

2. Would a simple app to toggle debug mode make this easier? Again, could it be installed prior to downgrade? Could it be automatically run from an SD card?

3. Would an app allowing remote control of your phone allow you to see the blank screen? Do all the apps providing this functionality require adb access?
[Desire Android Development] teppic74:
The downgrade does a complete wipe of the phone. It doesn't just downgrade HBOOT.
[Desire Android Development] teppic74:
One potential problem for this method. I installed the stock RUU (SLCD version) on my phone, but when it first starts up it asks which SIM settings I should use. This is before the setup wizard begins.
[Desire Android Development] SavageCore:
Surely at this stage you have a working phone at hboot 0.83 and a screen? so you follow the sim settings and reroot with unrevoked?
[Desire Android Development] teppic74:
I was doing a test run of the procedure - so I just flashed the safe stock RUU (I never upgraded to OTA froyo so I can do this).