yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] jsmith8858:
Install Google Voice from the market, and then run it. Just follow the steps.
[AT&T Samsung Galaxy S II SGH-I777] K Rich:
Don't know why I didn't install this earlier cause it freaking rules.:D
[AT&T Samsung Galaxy S II SGH-I777] SuperEd:
Google voice is the best out the bunch. Especially love the transcripts, always makes for a great giggle. :)
[AT&T Samsung Galaxy S II SGH-I777] ChocolateSnow:
How do i select my greeting for google voice? I set it so that my regular calls get forwarded it to its voicemail, but i dont see any setting for greetings
[AT&T Samsung Galaxy S II SGH-I777] GalaxyMaster:
From a web browser www.Google.com/voice then go into the settings.
[AT&T Samsung Galaxy S II SGH-I777] Edgarhighman:
you can use google voice for free texting from your actual number? I used heywire for free texting, but people that texted my real # weren't notified that I couldn't receive texts, then I split an "unlimited" with a friend for $30/mo

Google voice does it for free from your real # without error?
[AT&T Samsung Galaxy S II SGH-I777] Enzopreme:
yup. Or you can choose a new gvoice number, like having 2 lines, but ones is totally free! And people can call and text that number, and you will receive it on your device, also you can choose before each call whether to call from your g voice number or your reg number.
[HTC Sensation] player4lifeov:
Anyone plan on jumping ship??
[HTC Sensation] swiftinmotion:
No
[HTC Sensation] kpjimmy:
No. Because 1. I used my upgrade already. And 2. I bought too much accessories already to let go of the phone.
[HTC Sensation] player4lifeov:
I ordered mine today but I'm keeping my sensation. Will see how the two compare when I get my nexus
[HTC Sensation] suprakarma:
We'll. Get ics soon or later, and just for the firmware updates some wouldn't pay, plan cancellation fees, then go to an overcharging carrier, nfc chip? Ask anybody who owns a nexus s used it properly, and constantly, every dual core device now has same aspecs yet in a different way, different flavor, different. Everything
[HTC Sensation] The-Nazgul:
No cause it is just a little to big for me. Coming from the N1, then the Sensation, but the Galaxy Nexus screen seems to me just to big for my pocket!
[HTC Sensation] jhobert:
I'm on tmobile us, is there any galaxy nexus that will.work with my carrier?
[HTC Sensation] player4lifeov:
The unlock version can support the T-mobile bands but you'll pay about $700
[HTC Sensation] hello00:
Samsung aint my thing
[HTC Sensation] jhobert:
$700??? That should be worth the money and I hope its not just as the same as any other smartphones lol.
[Samsung Galaxy Nexus] Crazy CS:
My phone seems to be using 2% battery every 15 minutes on standby, worse when its on.

When I check what is running, it says Android OS 50%...... what can I do? I usually charge my phone three times a day.
[Samsung Galaxy Nexus] Tubes6al4v:
I use a variety of apps to check what is going on with my phone.

Watchdog - monitors apps for excessive cpu usage

Cpu spy - see how long your phone stays at each frequency, but more importantly in deep sleep.

Battery monitor widget - monitors battery usage

System tuner pro - get detailed analysis of a recorded system usage.

Also, when in battery usage, I click android os to see how long it has kept your phone awake. Have you made any changes to your phone? Installed a custom ROM?
[Samsung Galaxy Nexus] burningembers:
Also...give it a few days of charge-ups. It really does make a difference.

FWIW, with moderate use, my Droid Charge 4G does about 10-15% every hour. So I don't even think 8%/hr is that bad... :/
[Samsung Galaxy Nexus] Crazy CS:
no changes to the phone, its all stock. Any benefits moving to a custom ROM on the nexus?

I've had the phone for two weeks, battery has deteriorated. Now charge it three times a day.
[Samsung Galaxy Nexus] KiNG OMaR:
You probably never calibrated it properly to begin with. Charge to 100% > unplug > wipe batterystats.bin > let the battery drain completely until the phone powers off. Then charge it continuously over night and in the morning unplug and let the phone drain completely until it powers off.

I am a pretty heavy user as I text literally every 2 minutes all day (girlfriend :o) and I manage to get 20-25 hours easily.

I also drain my battery out completely every day for good measure :)

Charging in between screws up your calibration, try not to charge unless you are below 15%. And do not disconnect it until it is fully charged (98-100%).

Note: I've also noticed wifi saves you a lot more battery juice than being on 3G/4G, so keep your wifi active if you are in range ;)
[Samsung Galaxy Nexus] krohnjw:
This is just not accurate for Lithium Ion batteries, which have no cell memory and gain more from frequent shallow charges than deep charges.
[Samsung Galaxy Nexus] sishgupta:
Not to mention draining a Li-ion past 5% can shorten the life of the battery.

Further Li-ion's have a lifespan measured in cycles. You get about 500 cycles on a typical Li-ion. A cycle is a drain and charge. If you use 50% of the charge and then recharge to 100% you only use half a cycle. By needlessly draining the battery you are using up limited cycles reducing the life span of the battery.

While I'm sure android's calibration needs to know the upper and lower boundaries of a charge I'm certain it would be smart enough to handle charges when the battery isn't completely drained. Most battery calibrations work this way. Every once in a while you need to charge to 100% drain to 5% and recharge without using to 100%
[Samsung Galaxy Nexus] Crazy CS:
Wheres battery stats.bin located?
[Samsung Galaxy Nexus] zephiK:
Clockwork Recovery -> Advanced.

.. file is in /data/system i believe
[Samsung Galaxy Nexus] leyvatron:
its probably a bad app working with ICS.

Use watchdog and it will tell you.

Check your widgets that they aren't constantly refreshing.
[Verizon Droid Charge] HTCluva:
Anyone know any news on the new gummycharged/ liberty Rom? Or any other roms for that matter?
[Verizon Droid Charge] shrike1978:
GunnerMike just posted on Rootz today that Kejar was working on the Liberty base.
[Verizon Droid Charge] HTCluva:
Cool shouldn't be too long then
[Kindle Fire Android Development] ECOTOX:
This is gonna be the thread where I post the CWM I've been working on

First things first, here comes a newb question

Its my first time working with CWM, do i need the entire android source to compile it ? or just the source from koushs github. Also here is my nifty solution for navigation

The linux kernel has a few different types of events, the main two that CWM uses are

EV_KEY which is key event

and

EV_REL which is the trackball usually

the trackball even reads the movement and past a certain threshold fakes an up or down key event.

what I'm doing is adding in EV_ABS (touch event) to the input thread so that when it reads a screen touch it will fake a down key event similar to how the EV_REL works.

Now this is just the initial idea, in the future I want to make the touch event work like the trackball so to go up/down you swipe up/down, but this will do for now.

Controls will be as such

Tap = Move Down

Power = Select

Also once navigation is workin im going to be modifying it to set bootmode before exiting recovery so as to get rid of the current problem of not being able to exit recovery.

correct me if im wrong but here are the bootmodes i need

idme bootmode 0x4000 (normal boot)

idme bootmode 0x5001 (reboot recovery)

update 12/16 9pm

working on fixing some bugs with touch input and fixing rebooting from recovery

system is recognizing touch input properly and recovery boots properly, and when bootmode value is set to normal also boots the system correct.

Update 2

Got Reboot Working correctly from recovery and still workin out some touch nav bugs, will finish up tomorrow hopefully

UPDATE 12/17

Havent had time today t work on it like i planned, still issues with the touch input moving the cursor too far. Working on it now

UPDATE 12/18 1:30am

Touch Icons are drawn and in the correct position, working on mapping to correct functions

update 10:50pm

For some reason cannot get the touch coordinates to line up with the icons, even though the icons should be right over them.....not sure whats going on =/ gonna have to redo a few things to see what might be happening and why a key event isnt being injected

UPDATE 12/19

ReWriting the the input get for my touch controls to simplify it and make it easier to debug. Got work though till 4 so its gonna have to wait
[Kindle Fire Android Development] smirkis:
awesome, I was sitting stuck in recovery on my mytouch today and using the trackball thinking of this as well. bravo my friend. seems very feesable
[Kindle Fire Android Development] ECOTOX:
Thats the idea, and though there are other touch recovery in development, I've been using CWM for a long time and like and trust its (at least for me) reliability
[Kindle Fire Android Development] death2all110:
You have to have the full android source code. it goes in the bootable directory.
[Kindle Fire Android Development] ECOTOX:
i figured...syncing now...will let you guys know the progress when there is some.
[Kindle Fire Android Development] pyrostic:
idme bootmode 4002 is fastboot
[Kindle Fire Android Development] Epix4G:
If you got questions ask koush he is always on twitter , but you can always go to CyanogenMOD irc on freenode
[Kindle Fire Android Development] teookie:
My understanding is that you need the whole source, but you can build just the recovery by typing: make recoveryimage.

There is a guide here:

http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html

Hope you get farther then I did. I must have missed a step somewhere because I cant get it to build.
[Kindle Fire Android Development] death2all110:
tecookie whats the issue you're having?
[Kindle Fire Android Development] ECOTOX:
ok guys....touch recovery working...let me work out the kinks then we are good =]
[Kindle Fire Android Development] teookie:
It's weird. Seems like yesterday I was getting a different error.

I was following this guide and everything seemed to be going well up to the "build/tools/device/mkvendor.sh..." point. I got the "Done" output from that command but also a bunch of other stuff, some of which looked like they might have been errors.

I think I might just re-sync and try again.

---------- Post added at 06:22 PM ---------- Previous post was at 06:17 PM ----------

Wo! Awesome! Looking forward to it.
[Kindle Fire Android Development] dubt17:
WHAT?! This is great news! I'm very excited to hear this! I don't even have a kindle fire yet, but plan on getting one for christmas and I was worried I might not be able to hack it as well as other devices without a usable recovery. But this is great news! Glad to see many talented devs working on the fire, just makes that 200$ a great investment :D
[Kindle Fire Android Development] Poler166:
TWRP

you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://xdaforums.com/showthread.php?t=1356425
[Kindle Fire Android Development] ECOTOX:
I know, I'm not doing this just for a recovery, i want to see if i can do it =P Also I like CWM
[Kindle Fire Android Development] kjwalker:
Any estimates when it'll be ready for release?
[Kindle Fire Android Development] ECOTOX:
Earliest tomorrow
[Kindle Fire Android Development] death2all110:
I can help you out if you want?
[Kindle Fire Android Development] brett10:
TWRP is a little better choice in recovery for tablets, but it never helps to have several options :)
[Kindle Fire Android Development] ECOTOX:
Nah, thanks though, you've been alot of help already. I'm exhausted and need to sleep, so when I wake up i'm guessing around 4 more hours work and the initial release will be ready
[Kindle Fire Android Development] smirkis:
u mean never hurts? how can u claim twrp is a better choice when its not out. cwm is known by many and some just feel comfortable using it. stop trolling, development is development. even if they both got released the same day, people with choice will choose whatever recovery they wanna use. I personally like cwm, but would use whatever is available to our devices that's stable.

Congrats on the progress, can't wait to test it out.
[Kindle Fire Android Development] DooMLoRD:
so we (Team UtterChaos) are also working on touch based recovery...

here is a live demo:

[YOUTUBE]QGc1WL19VNs[/YOUTUBE]

right now we have it working for one of the devices we support (Ideos X6)...

we will soon be porting it to other supported devices (Xperia X10, Xperia ARC, Xperia Play, Samsung Galaxy SL (i9003))...

BUT right now i dont have the Kindle Fire with me to do testing/work on it...
[Kindle Fire Android Development] smirkis:
still? I could have over nighted u one! =p

appreciate your work buddy!
[Kindle Fire Android Development] DooMLoRD:
hehehe...

didnt u guys read this:

http://xdaforums.com/showpost.php?p=20492849&postcount=104

i cant afford a new device right now.. KF costs 300$ here in India...
[Kindle Fire Android Development] abhishekagrawal:
i ordered one from ebay india for 12.5k. thats only slightly more than 200$ in us with the current rupee vs dollar conversion!
[Kindle Fire Android Development] smirkis:
nooooooo!

sad to see u go, hope to see u poke around.

sent from my kindle fire
[Kindle Fire Android Development] teookie:
So, I know the urgency for this is gone now that we have TWRP2.0, but I'm still trying to get it built anyway. I get an error when trying to run "lunch full_blaze-eng". Everything seamed to go smooth up to this point, I'm not sure what's wrong. Can anyone point me in the right direction?

trent@trent-P50IJ:~/cm7repo$ build/tools/device/mkvendor.sh amazon blaze /home/trent/kf-backup/6.2.1-boot.img/boot.img
Output will be in /home/trent/cm7repo/device/amazon/blaze
593 blocks
Done!
Use the following command to set up your build environment:
lunch full_blaze-eng
And use the follwowing command to build a recovery:
. build/tools/device/makerecoveries.sh full_blaze-eng
trent@trent-P50IJ:~/cm7repo$ lunch full_blaze-eng
build/core/product_config.mk:198: *** device/amazon/kindle-fire/device_kindle-fire.mk: PRODUCT_NAME must be a valid C identifier, not "full_kindle-fire". Stop.
Device blaze not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for blaze not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:198: *** device/amazon/kindle-fire/device_kindle-fire.mk: PRODUCT_NAME must be a valid C identifier, not "full_kindle-fire". Stop.

** Don't have a product spec for: 'full_blaze'
** Do you have the right repo manifest?

trent@trent-P50IJ:~/cm7repo$
[Kindle Fire Android Development] :
I'm still working on it, just trying to enjoy my holiday =) did you sync the full cm source before hand? Also make sure you have you're system setup correct, check the cm wiki on how to build cm. i'm assuming its saying they is no kindle fire lunch? You make the necessary make files? Also the name is blaze so any make files should be under Amazon/blaze when you make them =)
[Kindle Fire Android Development] a2296455:
Yes I like CWM recoveries instead. Work with Koush to incorporate it into his official app! I think he just bought one...
[Kindle Fire Android Development] teookie:
Well, I ran makevendor.sh without errors, and it said to type "lunch full_blaze-eng" to set up my build environment. But when I type this in it gives the errors in pasted above. :confused:
[Kindle Fire Android Development] teookie:
Ok I got lunch to work. I had to make my own vendorsetup.sh file for some reason. After doing that and running envsetup.sh again lunch worked.

Now I'm trying to determine if the recovery.fstab file is ok or if it needs any tweaks.
[Kindle Fire Android Development] :
It should be fine =)
[Kindle Fire Android Development] FroyoShark:
Not trying to sound rude or anything, but why not just stick with TWRP?
[Kindle Fire Android Development] DooMLoRD:
because this is android and everyone should have a choice to use what ever they want :)
[Kindle Fire Android Development] FroyoShark:
I agree with that to an extent. Everyone should be able to choose their ROM but what's the advantage of choosing your recovery?
[Kindle Fire Android Development] DooMLoRD:
why not?

FYI have a look here: http://xdaforums.com/showthread.php?t=1278318

choice of 3 recoveries ;)
[Kindle Fire Android Development] FroyoShark:
That looks pretty cool, but my point is they all do the same thing. It's not like you look at your recovery constantly like you do your ROM.
[Kindle Fire Android Development] :
Its a learning experience more than anything. I've never worked on

the recovery of any device, I've only done Kendell and some bits of ROM.
[Kindle Fire Android Development] DooMLoRD:
ok so i got it working (even though i dont have device with me ;) )

doing some testing...

it will be released soon after testing is complete...

as of now what all works/has been tested:

TouchBased navigation menu (those white buttons on right side)

adb works in recovery mode

mounting USB storage (sdcard) to PC while in recovery

mounting/unmounting of various partitions

nandroid backup/restore

lots more to test

need a few testers

will keep informing u guys
[Kindle Fire Android Development] animefun135:
Really want to try this... I wanna be a tester.
[Kindle Fire Android Development] smirkis:
great work so far doomlord! more testing today :)

I honestly prefer cwm and can't wait til it's ready for the rest of you!
[Kindle Fire Android Development] kyleco:
Definitely want to be a tester. Just got my fire, and I'm coming from many rooted phones.
[Kindle Fire Android Development] B3L13V3:
I don't mean to be "that guy" but ive come from devices that have more than a clockwork recovery, don't get me wrong I support koush, and what he does with so many devices is amazing but I always preferred other revoverys. What will this bring that is different than twrp, meaning speedwise, etc....
[Kindle Fire Android Development] DooMLoRD:
well this is CWM recovery with some minor changes (which help users) and a touch based interface...

some changes from standard CWM5:

revamped layout for recovery menu (to improve navigation) [renamed few options and changed their order]

changed "wipe data/factory reset" option to just "factory reset", and detailed the partitions which will be wiped

added reboot options

reboot into system

reboot into recovery

reboot into fastboot mode

"Partition SDCard" is disabled for this device

add confirmation to "backup" option in Nandroid menu... it used to keep getting pressed by mistake and start making backups immediately... now it will ask u before starting backup ;)

removed tons of "NO"s from some menus...

may be some more but i forget ;)
[Kindle Fire Android Development] animefun135:
how it work? with FIREFIREFIRE Bootloader like TWRP ? where we can get "test" version of this recovery?
[Kindle Fire Android Development] smirkis:
twrp is lacking support. the reboot option in twrp is broken and hasn't been fixed. lots of people get stuck in bootloops which shouldn't be happening. the cm7 rom had to be modified and remove the reboot to recovery option. with this recovery it can be reimplemented.

this recovery will fix that. and bring a more familiar look to users who normally use cwm. speedwise, twrp was based off cwm, so it should be the same.
[Kindle Fire Android Development] smirkis:
anime, u get into cwm using firefirefire still. so this just replaces the recovery. getting into it still requires a method such as fff.
[Kindle Fire Android Development] B3L13V3:
when i had my Eris we had a cwm scare which users reported being bricked by it so i usually stayed away from it on all my devices but since there isnt much support from twrp and doomlord is taking unto himself to support this and make it available for us i think i will go for cwm recovery. I didnt say it (but i clickd the button) thank you doomlord for making this available to us and for supporting the kindle fire!
[Kindle Fire Android Development] androidcues:
I use ROM Manager for all my other devices.

I would like to use ROM Manager for my in-house KF management so therefore I would like to see ClockworkMod for the Kindle Fire it just keeps everything simple for me.

I prefer to flash my recoveries from fastboot rather than inside system.

I am available to test.
[Kindle Fire Android Development] smirkis:
it would be nice if koush supported this version doomlord is porting. I'm not sure if rom manager will play nice with this port of cwm but ill test all that as well.
[Kindle Fire Android Development] theholyfork:
Looking forward to seeing this finished!

I say we reopen a thread in general to get DooMLoRD a KF, I'm willing to donate this time since I actually have money now haha.
[Kindle Fire Android Development] DooMLoRD:
i am using same sources for my custom recovery for various devices ARC, PLAY, X10, Flyer, SGS-SL, etc and ROM Manager works properly with this custom recovery as it is CWM5 based

i am not sure if koush will directly support this...

but it will play nice with ROM Manager...
[Kindle Fire Android Development] smirkis:
that is great to hear. as far as support, I just mean it would be nice if he hosted the recovery so everyone COULD flash this via rom manager. just so noone gets stuck in fastboot.
[Kindle Fire Android Development] teookie:
I'm willing and able to help test if you need more help. Direct me to a download and I'll flash and start looking for bugs.