yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Q&A, Help & Troubleshooting] gurusux:
I'm having a hard with my battery. I just can't make it last more than 6 to 7 hours. Im trying everything. Can anyone post some advices please.
[Hero CDMA Q&A, Help & Troubleshooting] smolck:
I was having issues until I did the following......(and I am on the same build as you)

Go into recovery and wipe the dalvik cache. Reboot.

Set the automatic screen tweak under CM settings/user interface

These two things have seemed to make a pretty big difference. I am not running any tweaks or anything and with moderate use (some wifi, 10-15 emails, 4-5 texts, gmail sync) I am at 89% after three hours off the charger. While this isn't great (IMO) it is lots better than I have been getting. Hope that helps.
[Hero CDMA Q&A, Help & Troubleshooting] jerry43812:
I had the same issue, but with only 3 hours of life between full charges, and one phone call for 15 mins.

I reverted back to 8/24.
[Hero CDMA Q&A, Help & Troubleshooting] gurusux:
Smolck you mean the automatic back light right?

I wiped kalvic cache... ill see how it goes without batt tweak and no apps running.
[Hero CDMA Q&A, Help & Troubleshooting] smolck:
Yea. I just set it to what I thought were "power saving" settings. It seems the Dalvik cache is what did the main thing to help. All I can say is that I am still over 80% and I have been off charge since 7:00am CST. And this 8/25 build is SMOKING fast on my phone :D
[Hero CDMA Q&A, Help & Troubleshooting] gurusux:
It is fast. Its even faster with launcher pro.

Are you using the batt tweak? Which kernel?

Down from 55% to 50% in 75min
[Hero CDMA Q&A, Help & Troubleshooting] smolck:
Stock kernel (what comes with the .zip) and no tweak.
[Hero CDMA Q&A, Help & Troubleshooting] jinwu57:
Can someone do an analysis of my current battery usage and tell me what I need to do? Me hero won't even last half a day.
[Hero CDMA Q&A, Help & Troubleshooting] smolck:
That screenshot isn't enough info. But go to settings/about phone/battery use and you will get a better idea of what is using the most power.
[Hero CDMA Q&A, Help & Troubleshooting] gurusux:
From 100 to 90% in 2 1/2 hours now. That's pretty good right? Stock 8/25 kernel w no tweak. If it keeps working ill backup and add other stuff and see
[Hero CDMA Q&A, Help & Troubleshooting] gurusux:
Well I think its fixed. Managed 13 hours and still 35% left using Google maps and Pandora plus regular use. Running the same configuration.
[Desire Themes and Apps] O and O:
Can a US user please download the Gilt Groupe app and upload it? Thanks.
[Desire Themes and Apps] O and O:
So many views and not a single response ... all I want is the APK as it isn't available outside of the US ...
[Desire Themes and Apps] AndroHero:
why not just use market enabler?
[Desire Themes and Apps] randopando:
yes plz can someone upload the apk plz. been trying to get this app for awhile and still cannot. even tried to use the market enabler and still nothing. thanks
[Desire Themes and Apps] randopando:
NM i got it to work. htanks for suggesting market enabler
[Galaxy S I9000 Android Development] Biertje_:
Sounds great :D Lets hope you guys can figure it all out.
[Galaxy S I9000 Android Development] supercurio:
I just send a message to Red Bend Software through their site.

Actually it may help to find any other delta file for their software. Without sample we won't go anywhere...

I hope they will be kind and answer!
[Galaxy S I9000 Android Development] raspdeep:
ok it works when i flashed zImage

# redbend_ua restore /sdcard/jm5.zImage /dev/block/bml7
redbend_ua restore /sdcard/jm5.zImage /dev/block/bml7
RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/jm5.zImage
dst: /dev/block/bml7 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 247184 bytes
read finished
[Galaxy S I9000 Android Development] RyanZA:
Wow, this is looking promising. :D
[Galaxy S I9000 Android Development] zygame:
it seems like htc's flash_image,but much more difficult than it.
[Galaxy S I9000 Android Development] supercurio:
Nice raspdeep ;)

How did you do ? Every attempt fails here (in recovery or standard mode).

Which initramfs version do you use ?
[Galaxy S I9000 Android Development] supercurio:
redbend_ua restore zImage /dev/block/bml7
RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: zImage
dst: /dev/block/bml7 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 247184 bytes
read finished

Ok yo don't respond but it works here to, booting on your OC kernel. Now i'll find what is different between our setups ;)
[Galaxy S I9000 Android Development] distortedloop:
supercurio, you are rapidly becoming one of my Android heros...

:D
[Galaxy S I9000 Android Development] supercurio:
Don't know if I can live with that :o

ll */*
-rwxr-xr-x 1 root curio 313888 2010-08-26 21:14 oc128uv1/redbend_ua*
-rwxr-xr-x 1 curio curio 314004 2010-08-26 21:16 XWJM5/redbend_ua*

md5sum */*
74f5793536c3cdc902ec269c3f51a165 oc128uv1/redbend_ua
b1ba258a5d673c537a95167267afd6b8 XWJM5/redbend_ua

Different binaries !

Edit : attached working redbend_ua :D
[Galaxy S I9000 Android Development] Benjamin Dobell:
Whilst we're talking about retrieving information from binaries...

Does anyone know any good disassembly tools. I managed to compile objdump for ARM (ELF) and run it on the Galaxy S secondary bootloader but it only partially works. It doesn't look like it is handling the binary layout correctly. It's unsure how much of the binary is data and how much is actual instructions so it ends up converting the whole thing to instructions (most of which are obviously bogus).
[Galaxy S I9000 Android Development] supercurio:
Under Linux i use the minimalist tool named "strings". You can learn so much just by reading strings extracted ^^.

Otherwise you have IDA Pro (Windows), which is very powerful.

Benjamin, like you i found objdump quite challenging to use.. and.. not that fun.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Unfortunately IDA Pro doesn't seem to work either. IDA Pro Free doesn't support ARM at all and I tried with IDA Pro Advanced but it seemed to have similar issues to objdump, it couldn't determine the entry point etc.

If I could just get the assembler with comments next to it that indicate which pieces of data (strings in particular) are being referenced that would make my day.
[Galaxy S I9000 Android Development] supercurio:
Do you think Sbl.bin is a single unique binary ?

Considering everything that this Second Boot Loader is able to do, i would not be surprised if it's more complex than that.

Anyway I can't say much more about the tools, i'm just a rookie hacker ;)
[Galaxy S I9000 Android Development] Benjamin Dobell:
It wouldn't be a very reliable boot loader if it depended on other binaries (other than data passed to it by the primary boot loader). However the information I'm after, the Loke protocol, is definitely in there cause I can see the handshake strings I send and receive with Heimdall.
[Galaxy S I9000 Android Development] designgears:
working this into SRE RIGHT NOW!!!!

--edit

scripted, and working :D

release coming soon!!
[Galaxy S I9000 Android Development] supercurio:
Nice :)

Remember being EXTRA careful manipulating raw bml partitions. You can easily brick your phone for good writing bad data in place of first and second bootloader.

NON-RECOVERABLE

please say that to every potential redbend_ua users

This was the required warning, now enjoy ;)
[Galaxy S I9000 Android Development] designgears:
I have borked bml17 before.. was able to go into download and restore stock.
[Galaxy S I9000 Android Development] supercurio:
bml17 does not exist. You mean bml7 ? bml7 is the kernel, reflashable by Odin ;)

But let's say that you overwrite accidentally

- bml1 : Primary Boot Loader

- bml2 (maybe) : pit file

- bml4 and/or bml5 : Secondary Boot loader + USB Download mode

Then... youre can send back your phone to factory, opening it to plug a specific usb cable/software will be required to restore bootloaders on the NAND.

As an experienced Linux user, sometimes awake too late, I know for sure that you can sometime mess with your fingers and write on the wrong partition.

Here you risk not only loosing data, but loosing your favorite expensive toy too :D
[Galaxy S I9000 Android Development] designgears:
Yes, I mean bml7, sorry...

Ya, that could be bad :D

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

dont think mine is actually working =/

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

nvm, working now

Is it actually flashing, or just reading?
[Galaxy S I9000 Android Development] supercurio:
restore = writing to NAND

I admit the log is quite confusing, but I don't think this output is meant to be seen by use :D
[Galaxy S I9000 Android Development] supercurio:
First post updated with useful infos ;)

My special top-secret consultant gilsken gave this link for you :D

http://chdk.wikia.com/wiki/GPL_Disassembling

I already saw it before... anyway if ever you didn't read it already here it its!

Based on what you say, you already know much about the Second boot loader. I guess this is related to your work on your great multiplatform Odin alternative !

I understand that you'll be able to figure out some situations tricky to manage with the SBL logic than with just reverse-engineering USB sniffing data.

If this part is so hard, do you think it's related to some sort of obfuscation or even encryption to protect IP or signature-controlled boot techniques ?
[Galaxy S I9000 Android Development] designgears:
I am trying to run this in SL4A and I keep getting errors :(

works great thru adb
[Galaxy S I9000 Android Development] anomalous3:
confirmed working on the vibrant through ADB!
[Galaxy S I9000 Android Development] designgears:
Wish I could figure out how to make this work on the phone in a script.
[Galaxy S I9000 Android Development] raspdeep:
ahh.. i didnt know they are different binaries.. sorry, i went to bed after trying out your findings (another great job btw :))
[Galaxy S I9000 Android Development] designgears:
Got this working, flash the update.zip on a stock rom, it reboots, right after the ATT screen it flashes the kernel, reboots and does all the custom scripts loaded by the custom kernel :)
[Galaxy S I9000 Android Development] supercurio:
This bad boy needs to be run as root, of course :)

Nice to see that you figured it out.. usage in an update.zip was the first targeted usage.
[Galaxy S I9000 Android Development] rhcp011235:
where is the src to this binary? It can help a lot of people.

I saw someone say brick. If you brick bl0 or bl1 you are dead :)

The only way to restore is JTAG. And, Im working on it. Havent had much luck.
[Galaxy S I9000 Android Development] raspdeep:
some things you dont want others to mess around unless they know what they are doing.. I would suggest this topic for devs only..
[Galaxy S I9000 Android Development] astralmind:
Well keep it up guys, I'll be honest, I don't get all that's being discussed in here as I don't have the technical knowledge but it's really cool to see the hard work you are putting in.

Any chance this could potentially solve the "No 3 buttons revovery/download mode" by re-writting parts of the BML ?
[Galaxy S I9000 Android Development] supercurio:
Probably a good idea ;)

If the non-functionnal 3 buttons problem is caused by a restricted Second boot loader, yes it will help.

This tool is able to flash anything without being in "download mode".

It provide 2 new abilities :

- rewrite and replace boot loaders

- flash anything without the need to go to "download mode"

With great power there must come great responsibility, you may wait for an integrated / tested solution from an experienced developer ;)
[Galaxy S I9000 Android Development] RyanZA:
Only Samsung has the source to this binary, since it is their OTA update tool. ;)

It should mean that it is pretty safe, though - at least for non-bootloader stuff. :)

It will make creating custom kernels for things like the EXT4 kernel very easy to install on your phone with the proper tools around it. Even putting up custom kernels on the android market becomes quite easy. :D
[Galaxy S I9000 Android Development] morfic:
I See below you got it working anyway, but for others/future reference for getting root with SL4A:

#!/system/bin/sh
if [ "$(/system/xbin/busybox id -u)" == "0" ]; then

#insert the code to execute that needs root privileges here

else
echo -e "Getting root privileges\n"
su<$0
fi

This self promotion suggestion is on the SL4A bug tracker.

Note that if you never installed a busybox proper, the script will fail due to not having [ and ] on the system. Like the root update.zip just gets you the busybox binary, w/o any of the symlinks. Install them yourself or get a proper busybox apk
[Galaxy S I9000 Android Development] supercurio:
− working on a update.zip kernel upgrade clean template −
[Galaxy S I9000 Android Development] RyanZA:
I know that kernels for one variant of the SGS won't work on other variants. I can't think of a sure-fire way to make sure that the flashed kernel will actually work on the device though. Anybody know of a nice way to check that the kernel will work on that specific device?

Will we need to compile a list of all device codes or something similar that are compatible with the same kernels, or has anybody already done something like this?
[Galaxy S I9000 Android Development] supercurio:
assert(getprop("ro.product.brand") == "Samsung" || getprop("ro.hardware") == "GT-I9000" || getprop("ro.build.id") == "ECLAIR");

Still slowly preparing the template ;)
[Galaxy S I9000 Android Development] RyanZA:
This works for sure though? There isn't some strange Spanish or Canadian or Korean or something phone that has these same responses, but needs a different kernel?

Is there also any way to get the kernel version independent of the firmware version?
[Galaxy S I9000 Android Development] supercurio:
Yes it should be like that.

One ro.hardware name == one specific kernel.

But as usual : **NO WARRANTY**

You may follow the new thead : Flashing Galaxy S kernel from update.zip : template update.zip :)
[Galaxy S I9000 Android Development] RyanZA:
I mean can we determine exactly what kernel the device has running?

I'm thinking of maybe md5sum of the currently installed zimage?
[Galaxy S I9000 Android Development] supercurio:
Hello RyanZA, Yes it's possible and easy to check a part of the kernel on /dev/block/bml5 and make a md5 of it, but I don't get the point ;)

You can determine which kernel is running by comparing with known kernel signatures : only if the kernel running is already known.

If the kernel is not int your "kernel signature database", because it's newer or because it's a custom kernel, that's useless.

I see no reason not to stick with the official detection : using the hardware name !
[Galaxy S I9000 Android Development] AllGamer:
just a heads up, maybe you guys should work together with Benjamin Dobell, that is working on Heimdall for the very same purpose to be able to flash the phone without depending on the PC

http://xdaforums.com/showthread.php?t=755265&page=2
[Galaxy S I9000 Android Development] supercurio:
Froyo

I'm testing JPC right now, and it sucks that we can't use update.zip like with Eclair builds.

I hope we will be able to figure it out soon.
[Galaxy S I9000 Android Development] seraphimserapis:
we need a good custom recovery that allows flashing testsigned updates.
[Galaxy S I9000 Android Development] supercurio:
Yeah I agree, a better one than ClockWorkMod who fail on a bit too much update.zip's (or the same improved).

I kind of liked how the stock recovery made software installation easy !

No need for root; Easy !

Is this "test-key compatible" recovery of the Galaxy S an exception ?
[Galaxy S I9000 Android Development] supercurio:
Yep Benjamin Dobell's work is extremely interesting and could prove so much more useful than Odin !
[Galaxy S I9000 Android Development] rafarataneneces:
What happens if I delete the

/data/fota/ files

or if I move (or symlink), the files there to an external /sdcard?
[Hero CDMA General] dbldown768:
when i try to do adb remount i get the following message: remount failed: Operation not permitted

I have search trying to find and answer and dont see much of anything. The device is listed when i do adb devices. I did do some cleanup on my sdcard and saw something about boot img in one of my searches. I'm wondering if accidentally deleted something???
[Hero CDMA General] ipfreelytech:
you are rooted?
[Hero CDMA General] dbldown768:
yeah have been rooted for months. I was using 2.2 froyo, then nandroided back to 1.5. adb remount worked fine the first time. THen i cleaned somethings off my sdcard (not sure if this matters), and since then adb remount doesnt work. if i do an 'adb shell' then su, everything works still?

edit: btw, this is not while in recovery. this is while the phone is fully booted.
[Hero CDMA General] ipfreelytech:
the sd card is irrelevant to the remount command. Something is keeping you from having root privledges via adb. Maybe try Ruu again and then re-root and load up your rom?
[Hero CDMA General] codejunkie78:
it's probably the rom you are using, it my be secured connect the phone to your computer, open a command prompt, cd into the android-sdk/tools folder and enter

adb pull /default.prop

then go into the android-sdk/tools folder and open the default.prop file in wordpad or notepad++

look for the line

ro.secure=

if it is set to 1 it is secured and adb remount will not work, you can still mount the file system temporarily manually though.
[Hero CDMA General] kyouko:
make sure debugging is enabled :p
[Hero CDMA General] dbldown768:
yeah i think it has something to do with this:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0

i tried to change the 1 to 0 in recovery mode, but when it booted back up again it still shows 1???
[Hero CDMA General] codejunkie78:
i think those files are overwritten every time you reboot, if you really love the rom and you need rw support built into the rom, you can take a nandroid backup of that rom and use the kitchen here and add it to the rom rebuild and reflash it.
[Droid X Accessories] GoldenCyn:
Im used to using my iphone headphones with the built-in mix and music controls (lost them). Was wondering if any earphones with these features will work with the DX to answer/hang up calls and control the music player.

Im on my way to best buy for an unrelated purchase but would like to know what options I have before I get misled by a sales agent there.
[Droid X Accessories] jgraham4598:
I have the Motorokr S9. They are bluetooth. I really like them. I have been looking to upgrade and there are a lot more out since I first purchased. I would definitely do some research online before buying from Best Buy.

Update: I went out and upgraded from the S9 to the S9-HD. They are huge improvement from the old model. The sound is so much better. Battery life is still about the same.
[Droid X Accessories] Corey@rabbit:
+1 for the S9
[Droid X Accessories] QQeyes:
V-MODA Vibe Duo Earbud Headset (Gunmetal Rouge)

Try doing an amazon search for those.

I ordered them a few weeks before I got my DX cause I knew I would need some headphones. And was I pleasently surprised! These 26$ earbuds EASILY surpass the quality of my friends' $100 Bose and $60 Skull candy or w/e earbuds. Plus they are very well built, with a braided cord and a cell phone call start/end button. Oh and the color matches the droid x.

Try em out! I guarantee you won't be disappointed
[Droid X Accessories] OneStepAhead:
The Beats line by the Doctor has Control Talk, which may or may not work completely with Android (leaning towards may not). I believe only the pause

and volume control work, not the next/prev track. Not cheap though. I'm looking at getting the Gaga's for my sister. They better tuck her into bed at

night too for $130!
[Droid X Accessories] Corey@rabbit:
I want the beats sooooo bad. Can't justify that kinda $ though.
[Droid X Accessories] HostileJava:
+2, I've had mine since I had my old 6700, they work great.
[Droid X Accessories] SirBrass:
I'd also +1 the S9HD's if those blasted ear bud pieces weren't so prone to falling out and getting lost while being transported in a pocket or getting pulled out of a pocket (I can't use them any more b/c this happened to all 3 sizes of ear buds, and I have yet to find a way to purchase replacements w/o buying the entire headset again).

I have a set of rocketfish over-the-ear BT stereo headphones w/ music and call controls. They work quite well and though they take some adjustment on my head due to me wearing glasses, they are also fairly comfortable..... and they're not at all as expensive as the name-brand motorokr's (motorola if you couldn't tell).
[Droid X Accessories] bobby911:
I got the V-Mode Vibe Duos too! lol

I agree, very good pair of earphones. Only catch is that the default music player wont pic up the control button. No big deal tho cause you got a nice widget on the lockscreen that allows u to pause, forward or rewind.

I got the Dr Monster Beats too but i THINK they are fake. Friend gave em to me, anyways, the v-modas sound wayyy better and have a very nice deep rich bass!

If you go to amazon you will read a lot of negative feedback, to be honest my v-modas still working just fine! :D
[Droid X Accessories] Maxgap1705:
+1 Motorola S9-HD

I use mine every day.

:D
[Droid X Accessories] Roland Deschain:
These are nearly the only headphones/ear buds in existence that will have all the controls work properly on your phone with.

http://www.zagg.com/audio/smart-buds.php

Virtually all headphones/ear buds with audio controls are designed for Apple products. Apple is a terrible company, they make everything proprietary; they switched the mic and ground connectors so they could force manufacturers to make headphones that would only work properly on their bass-ackwards newer Apple products.

Products like these:

http://www.bose.com/controller?url=...mobile_solution/index.jsp&model=mie2i_headset

http://www.sennheiser.com/sennheiser/home_en.nsf/root/private_headphones_sport-line_504603

http://www.skullcandy.com/shop/50-50-black-red.html

http://www.sonystyle.com/webapp/wcs...10151&langId=-1&productId=8198552921666138350

http://www.klipsch.com/na-en/products/image-s5i-rugged-overview/

Will only work on newer-generation iPods/iPhones/etc. because Apple switched the microphone and ground connectors, so when you plug any of the above-linked products into a regular, worldwide standard, normal headphone jack like we have on our Droid X and that a gazillion other devices have, the buttons work sporadically or not at all.

God, I hate Apple. Support Zagg for being nearly the only company in existence to recognize what Apple has done, and accordingly provided a product for everyone else with. Apple would do the same thing with Bluetooth if they could, but they don't own the Bluetooth standard, thankfully; which is why all your audio controls work on any Bluetooth-enabled device out there. (as long as it's not a really old one)
[Droid X Accessories] angryjello:
Another reason to hate Apple... thanks alot man!
[Droid X Accessories] lseaver92:
i have the in-ear beats. They are AMAZING. the controls don't work though.
[Droid X Accessories] FreaKaDroidXYZ:
+1 for S9 as well.