yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] arkatis:
I get 10mA and after some time 150mA without doing anything...:( Huge drain than yours guys!
[HD2 Android Q&A, Help & Troubleshooting and Genera] buzz killington:
Doesn't seem very different while it's on, but in standby it's been awesome. From half past midnight to 6:30 it used only 3% in 6 hours, with wifi and sync on.

I also tried leaving gps on and put the phone to standby, current widget reported 3ma. I'll test that fully tonight. It'd be nice to not have to ever worry about having to turn off your gps again.
[HD2 Android Q&A, Help & Troubleshooting and Genera] impaziente:
crash when charging

why when i charge my phone it

Why when I recharging my phone it crashes? can not turn on unless you first remove the battery, and the red LED remains constantly lit even when off the power..
[HD2 Android Q&A, Help & Troubleshooting and Genera] chris_ah1:
TBH I think the NAND is much better than running from SD card - however, RAM builds were pretty good too.

The one crucial difference are not in the range of figures as I could get 6-8ma idle on Darkstone 1.5 RAM and Mdeej HD4.6 - however, after half a day or so of use it would start idling consistently at 60ma.

So far with Gauner's HD 0.3 NAND build it has ALWAYS been idling at between 4 and 8ma - also you save your SD card.....but I must admit nowhere near as fast as running it from RAM.

In use NAND does not save much battery, but it does make the idle profile far more consistent and dependable. I know I can leave it on without charging overnight and still be able to use it the next day as I did with winmo6.
[HD2 Android Q&A, Help & Troubleshooting and Genera] lude219:
just curious, isn't it a bit counter-intuitive to have all these battery monitor pulling every x-amount of time? Wouldn't that drain the battery as well? How are the processes get carried out?
[HD2 Android Q&A, Help & Troubleshooting and Genera] chris_ah1:
I used current widget to poll every ten seconds - seems ok. no logfile.
[HD2 Android Q&A, Help & Troubleshooting and Genera] ei05035:
My thoughts exactly. Furthermore, 1 minute polling and saving to the SD will actually consume more energy than that of the indicated energy by the widget (as the writing on the card will occur AFTER the reading of the value). Even when not logging, it is another thread that is running, although it possibly doesn't drain that much, as it only triggered by time events.

And remember, since SD has a rather high latency and high power consumption, logging it to the SD every minute can and WILL hurt the battery life.

Kudos!
[HD2 Android Q&A, Help & Troubleshooting and Genera] chvvkumar:
There is a rather nice widget on the market called "Battery Uptime" which keeps track of how long since the phone has been last charged and the overall longest period.

I am going to charge up the phone tonight and see how long it would last.
[HD2 Android Q&A, Help & Troubleshooting and Genera] buzz killington:
Usually I only log frequently when I'm playing with a new build - which is quite frequent :) Generally when I settle into a build I only keep it polling every hour, that's in case the battery drain spiked up, which sometimes happen with the sd card builds either because something that happened back in windows or if I just left gps on. I don't think I'll need to worry about those anymore. Might not run anymore battery widgets after a couple of more days to make sure.
[HD2 Android Q&A, Help & Troubleshooting and Genera] chris_ah1:
I wouldn't bother with logging - I know when something is wrong when I unlock the device and the standby figure is 60ma or higher. In that case it is an errant process or sync gone wrong.

With 10s polling interval it is long enough for the device to be unlocked and the last standby reading to be captured.

Syncs are generally short and can be controlled - but baseline standby is the really important one as that needs to be as low as possible for as long as possible.
[Nexus S Themes and Apps] Sim-1:
Hello everybody!

Has anyone done a battery percentage mod to be used with Nexus S yet? I have done a research but couldn't find anything..

I prefer to see the percentage of battery left right there in the middle of the icon, instead of placing a widget on my desktop.
[Nexus S Themes and Apps] NexuS87:
That would be a nice little touch to the display, Im sure it will come out soon , I havnt seen it yet...
[Nexus S Themes and Apps] sonnysekhon:
My theme has battery percentage built in. I will try to do the same MOD for a non themed ROM.
[Nexus S Themes and Apps] theimpaler747:
See my app, there's a test version for the Nexus S CM7
[Nexus S Themes and Apps] MikhailCompo:
Is the battery indicator app no good? It shows numerical percentage at the top of screen
[Nexus S Themes and Apps] pendo:
lol...

Yeah, the battery mod is available, had it just a few days after the N-S came out even. I've got one running on my aosp build (n1), as well as on cm7 alpha. No problems. Now, the custom low battery images I normally do.....well, haven't found that one yet. It's not like before.

Just the statusbar stuff, no problem.
[Nexus S Themes and Apps] KidCold:
This^^^ theres an app called battery indicator that puts in at the top.
[Nexus S Themes and Apps] theimpaler747:
I still need a tester on the NS for my app ;)
[Nexus S Themes and Apps] Dallas Johnson:
Ill test an app
[Nexus S Themes and Apps] theimpaler747:
Awesome! Ok, so first, make a backup of your device from recovery, let me know when you've done that :) Then go to the app thread and post there when you're done for me :D
[Nexus S Themes and Apps] jabbawalkee:
Same here - just posted in the app thread (main Android Themes and Apps thread) :)
[Nexus S Themes and Apps] theimpaler747:
Saw it, thank you so much for testing! :)
[Nexus S Themes and Apps] bone2006:
I just tested it for the nexus s 4G, it comes up and I can only select mod button, then it's a black screen after it says retrieving list of mods
[HTC Cavalier] sherifrasheed:
I Managed to install Rom wm6.5 with Arabic support for both devices CAVALIER and EXCALIBER,

the rom i used is (RUU_Cavalier_WM65_3VO.1.30.070109) from Mr.ookba from this post:

http://xdaforums.com/showthread.php?t=520756

for arabic support refer to the TWO files attached to this post

http://xdaforums.com/showthread.php?p=10237219#post10237219
[HTC Cavalier] fre4evr2:
HTC S-630

Hi Shareef, so how is wm6.5 for HTC S-630 is it pretty stable? all functional?

thanks
[HTC Cavalier] sherifrasheed:
all functioning good
[myTouch 3G, Magic Android Development] hayer:
I know this is going to get moved but what the heck heres a new year to the great developing. Thanks for keeping our devices up to date and good night.

Happy New Years!:D
[myTouch 3G, Magic Android Development] Serris:
Thank you, and happy new year to you too =)
[myTouch 3G, Magic Android Development] johmir:
All the very best to everyone thanks to all DEV's wishing all a prosperious NEW YEAR:)
[myTouch 3G, Magic Android Development] white^rabbit:
Happy new year.. Enjoy your life..
[myTouch 3G, Magic Android Development] lesa0208:
Happy New year to all people from this forum
[myTouch 3G, Magic Android Development] _spire:
thanks xda devs

thank you all xda devs i would be without a cell right now if it wasent for your wonderful forums and great advice happy new year
[myTouch 3G, Magic Android Development] bengongboy:
haha...the same wishes to all of ya here

Happy New Year
[myTouch 3G, Magic Android Development] mhc19881010:
dreams come true!!!!
[myTouch 3G, Magic Android Development] dimchris:
Happy new year !
[myTouch 3G, Magic Android Development] Binary100100:
I left this on here to make the developers feel special.

Now it's getting reported.

So I suppose it's not New Year anymore so it's time to close it up.
[Nexus S General] AllGamer:
NOTES:

It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.

This is due the build in protection in 2.3

As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.

If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else

To simplify things with the Command Line, it's best to copy and paste the contents inside ..\android-sdk-windows\platform-tools to ..\android-sdk-windows\tools

that way you'll have all the necessary files in the same location to prevent errors

MIRROR:

since CW website seems to be down, here's a mirror for the Image file.

download the 7zip attachment, unzip and flash recovery.img (recovery-clockwork-5.0.2.0-crespo.img)
[Nexus S General] lordjone:
Good guide but i have a question,

didn't you miss the step about renaming the install-recovery.sh script

that reflash recovery if crc is wrong?
[Nexus S General] Cubfan185:
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
[Nexus S General] sinatosk:
Nice guide.

The only thing that's making me hesitate to do root on my NS is reversing the whole process...

stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...

I'll wait until google releases a firmware that contains everything :p
[Nexus S General] AllGamer:
thank you, that was the idea.

many of the GUIDEs we have here are usually aimed at people that already knows what to do, which usually leaves out all the 1st time owners of the phone.
[Nexus S General] AllGamer:
it's fairly simple, the instructions are as simple as this

http://xdaforums.com/showthread.php?t=884097

and you can choose any stock ROM to flash back
[Nexus S General] Cubfan185:
Alright, just did it successfully. I had a few problems when installing the SDK and using fastboot. The recovery image must have been corrupt a few times for me. I had to take the battery out because it was stuck at the Google screen. My heart skipped a beat at that point, I didn't want to brick anything. Also had to put a required .dll file in the tools directory and the drivers were giving me problems, but got it all figured out. Thanks again.

Edit: Any reason why root required apps are saying they don't have root access?
[Nexus S General] KidYing:
Will Google definatly release a full restore firmware of the current ROMS, something simular to an HTC RUU, or is it just something we're hoping they'll do?
[Nexus S General] onicrom:
silly question... which fastboot binary did you use? the one from the htc developer site?
[Nexus S General] AllGamer:
it is included in the Android SDK 2.3 ... read the step by step guide again
[Nexus S General] jvblack82:
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.

So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.

I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.

I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.

Thanks in advance,

JB

Nexus S, stock rom just want root access for backup.
[Nexus S General] sinatosk:
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?

If so. I'm rooting RIGHT NOW!!!

Thank-you :p

edit: I did some searching and found the answer :p... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again :p
[Nexus S General] AllGamer:
yes, i actually like it this way, it keeps your original safe
[Nexus S General] AllGamer:
Titanium Backup and few other apps are why i ROOT the phone as well.

after you fastboot over the CW recovery image and rooted, were you able to install Super User?

there is another trick, you can Install Super User first from Market

then repeat the steps to fastboot the clock work recovery image and get root access
[Nexus S General] Cubfan185:
Followed the guide to a T as well and did not get root access. But unlocking the bootloader, installing the SDK and learning about fastboot and such was very helpful. Using that, I used the automated batch file posted in this topic http://xdaforums.com/showthread.php?t=882333 and it worked.
[Nexus S General] ykphuah:
What to do if my Device Manager showed Android 1.0?
[Nexus S General] AllGamer:
you select the correct driver to install the ABD support or Bootloader support, depending in which screen you have the phone on

just review the step by step guide, it is mentioned there
[Nexus S General] knytphal:
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
[Nexus S General] sinatosk:
... yeah I know. Made a post earlier today about it in this thread...
[Nexus S General] j0hnZ:
I had to fastboot flash recovery again, from the computer. Since then it's been working every time. Though it really doesn't matter since the screen is terrible and I'll be returning it. This red tint is terrible, and makes any cyan look like crap.
[Nexus S General] enragedpaza:
I'm on GRH78C

Will it effect if I can use this method?
[Nexus S General] Jonathon Grigg:
It worked for me on GRH78C so yes you will be fine.
[Nexus S General] enragedpaza:
I'm also on 2.3.2
[Nexus S General] rpritch:
Cant seem to find the fastboot driver...nothing like that is available in my google usb driver folder. Am i missing something?
[Nexus S General] AllGamer:
it's a manual install

you have to select which driver to install, re-read the part 1 of the Guide
[Nexus S General] enragedpaza:
For people having problems updating the drivers do the following.........

When you go to update driver software have it look in "google-usb_driver"

click-let me pick from a list of driver

then have disk

then click browse

go back to the folder "google-usb_driver"

there should be a file called "android_winusb" click that and hit ok

then you should get the option to pick in between the 3 drivers

Is this safe for 2.3.2?
[Nexus S General] AllGamer:
yes, as it works on 2.3.2 as well
[Nexus S General] rpritch:
Thank you!

i now have the driver installed...next problem...

When I type "fastboot oem unlock" I get a message that says "AbdWinApi....is not installed". Any suggestions.

Thanks in advance.
[Nexus S General] j0hnZ:
Do it from platform-tools, not the tools folder. Which means updating your path in system variables to platform-tools.
[Nexus S General] rpritch:
thanks...that gave me an idea...i copied the files in the "tools" folder to the "platform-tools" folder and it worked!
[Nexus S General] jltyler:
I need some help....

After installing the drivers and trying to then use cmd to fastboot i only get "is not a recognized as a internal or external command" I read through the thread didn't find anything. Uninstalled everything and started at square one but still cannot figure it out.
[Nexus S General] AllGamer:
you have to switch to the directory where the fastboot command is located
[Nexus S General] jltyler:
I have 2 program file directories one regular and a program files(x86) I can get to the first but not the second...

thanks for your help...

***okay i got to the folder let me do some more reading because im getting an error now that some others were getting. thanks all gamer
[Nexus S General] jltyler:
I'm getting an error of app has failed to start AdbWinApi.dll not found.

I tried to steps in one of the other posts about using the older ADB drivers. For some reason I'm not able to extract them into the tools-platform folder.

What am I doing wrong here?

*also I'm trying to run fastboot from platform-tools and not just tools
[Nexus S General] enragedpaza:
For some reason they moved some stuff to platform tools and not all. Easiest way to fix it is, get anything labeled fastboot.... and move it to platfrom tools were adb is
[Nexus S General] AllGamer:
as enragedpaza, and many other mentioned before

just copy all the commands into 1 folder, then you will have all the .EXE and .DLL all in one place
[Nexus S General] jltyler:
Thanks for the help and being patient guys I'm now rooted.
[Nexus S General] AllGamer:
Congrats!

that's what this topic is for, all new people joining the Nexus S world
[Nexus S General] jimsey:
non of the links to the cwm recovery image seem to be working, can anyone upload and post a link?

thanks
[Nexus S General] AllGamer:
the problem is his website seems to be down

http://koush.tandtgaming.com/

http://tandtgaming.com/

some one will need to post a mirror

and check post #2 for our own local mirror

http://xdaforums.com/showpost.php?p=10238348&postcount=2
[Nexus S General] RonnieRuff:
I rooted successfully with your instructions. After installing ROM Manager and flashing the Clockwork Recovery MOD the phone will only boot into the stock recovery. Sometimes if I flash again it will boot into Clockwork recovery then eventually back to the stock one. I was able to do a BU in Clockwork and now when I choose to boot into recovery to install CM7 back to the stock recovery. Any ideas? Never had a problem with my N1
[Nexus S General] j0hnZ:
I had to flash the recovery through fastboot 3 times for it to work every time the first Nexus. Flash it a few times testing in between, if that doesn't work try to download it again and do the same thing.
[Nexus S General] Mujja:
After the clockwork flash you need to rename the install.recovery.sh file found in /etc to something else.
[Nexus S General] RonnieRuff:
Thanks -- THAT DID THE TRICK!

Good to go now :-)
[Nexus S General] rob77:
I've done all the steps in the guide and put the phone in to bootloader. When I enter 'fastboot oem unlock' in to command prompt I just get a message saying 'waiting for device'. Im using windows 7 x64 and have installed all the relevant files I think, could anyone help me out? Cheers
[Nexus S General] AllGamer:
does the phone shows up in Device Manager?

did you verify all the steps in Part 1 of the guide?
[Nexus S General] rob77:
Hi. Yeah the phone shows up in device manager just as is pictured in part 1 of the guide. its the command prompt screen when the problems start.

Ive downloaded the android sdk from the link in the first post. I then when to the tools folder and ran fastboot from command prompt from there. First it gave me an error of I had adbwinapi.dll missing from my computer. I noticed that the adbwinapi.dll was in platform tools so I moved it from there in to the tools folder. Is this correct? After that I could get it to run just wont go any further than the waiting for device message.
[Nexus S General] j0hnZ:
You can run the fastboot commands from platform-tools where the files are instead of moving files around. The guide is based on the older version of the sdk which was updated a few weeks ago.

Shift right click in the platform tools folder and type adb devices, if the computer can't see it then either your drivers are wrong or your phone isn't in usb debugging.

You check that with your phone booted into the os first, it won't show a device in bootloader mode by typing that.
[Nexus S General] Haizum74:
Ok after a bit of mucking about I have got to the point of typing fastboot oem unlock it just says 'waiting for device' and the Nexus does zip. Am I supposed to select an option on the bootloader screen as the screen hasnt changed at all.
[Nexus S General] Jonathon Grigg:
Ok sounds like a driver issue there. Could you tell us what drivers you installed for the Nexus S? And also what version of Windows. Just as a guess you may need to install PDAnet just for drivers, as it worked for me but there could be other ways.

When it is working typing that command should execute something on your Nexus S and I think it reboots but I can't quite remember. However you know it has worked when in the bootloader interface it reads 'Lock State: Unlocked'
[Nexus S General] AtomicPC:
On the NS does it throw an error? Look at the bottom of the screen. Mine will say in grey font: FASTBOOT STATUS - FAILInvalid Command

If it says something like that then turn off PDANet in your task bar.

Just tested the fastboot boot command and that's what mine says <waiting for device> so that leads me to believe that's your problem... Turn off PDANet.
[Nexus S General] :
Will does this guide still apply to android 2.3.3? Girl friend doesnt like the constant bothering of the OTA update on her rooted NS so she wants me to update it.
[Nexus S General] Jonathon Grigg:
I imagine it might... what is the build number of 2.3.3? Im running CM7 now so I can't check myself. If it is GRH78* then I believe it should work. Not confirmed though, anyone else?
[Nexus S General] Haizum74:
Yeh I think it is a driver issue, I am running W7 64bit. I think it might have been your reply nearer the start of the post that mentioned this. I tried installing PDAnet drivers but it said that there were Android drivers already installed (I assume from my previous attempt at updating Android 1) and it still nothing. Going to try again from scratch and see what happens.

I will try your guide in your sig
[Nexus S General] Jonathon Grigg:
When I installed PDAnet it also mentioned something about already installed drivers, however I ignored it and continued anyway. Seem to work for me. Maybe try that, see how it goes. I have 32bit Vista though, so there may be some difference between 32 and 64.
[Nexus S General] Haizum74:
Well, it worked yet I dont know how as PDA froze when trying to install onto phone. Decided to try the fastboot command but that just hung on 'waiting for device'. Rebooted NS into bootloader and next thing I notice its on the screen requested a yes or no. So, it worked but it was a bit of a bugger getting there lol. Cheers
[Nexus S General] diesel2k:
Finally got it working. The steps are fairly easy the hard thing is getting your computer to recognize your phone during fastboot.

I tried on two win7 64 bit and one 32 bit. Downloaded the SDK and google v. 4 usb drivers. The google usb driver was only able to find my phone when it was in usb debug mode not in fastboot mode. I read a lot of places about trying to install pdanet but on my win7 machines no luck.

My last shot was installing a windows xp in a virtual machine with vmware workstation. I installed it with clean xp, the SDK and downloaded the google drivers. During fastboot my device was still not being detected and devicer manager just sat at "android 1.0" device. After installing pdanet I got it working!
[Nexus S General] Jonathon Grigg:
Yeah, I also found having USB debugging on seemed to help solve some problems. Maybe try that if anyone is stuck for ideas. I can't remember what it helped with exactly though.
[Nexus S General] ripperrs:
so i used this guide to root my phone. now that a new update is coming how i am going to install it to my phone?? ( i use cw recovery)