yashsingh1/xdaforums huggingface dataset:
[Captivate Themes and Apps] Vik_92_Sandhu:
Great work, could you get some corresponding sound aswell.
[Captivate Themes and Apps] evolution36:
I'm guessing just run this through clockwork?
[Captivate Themes and Apps] evolution36:
nevermind I got it to work. If it runs too slow do I make the last set of numbers in the .txt higher or lower?
[Touch HD Android Development] farukb:
Hi guys, let's see which android port/version/kernel give best results on htc our blackstones,so the community can see which ports are generally better than others

download linpack from market and post results here

DEVICE: blackstone

PORT: xdandroid

SYSTEM: FRX03

KERNEL(zImage/modules): 2.6.27.46-01253-gd53ddf6

CLOCK: 528 MHz

MFLOPS: 1.991

TIME: 42.11

PERSONAL NOTES:

stability: its ok,although i get occasional hang which either resolves itself or FC window, in which i choose to wait and problem resolves very quickly if not instantly

battery: can survive a day with moderate use (wifi,phone,etc)...unplugged the device 6 hours ago, have wifi turned on for about 4.5 hours,downloaded a few apps,made a few calls and it is at 70% i will post more info later today though

bug: wifi won't work after you twice turn it on and turn it off,and 2D is choppy and somehow blinks,but 3D can run up to 15fps on quadrant

cheers

EDIT:i'd like to see latest neopeek and spige's one,though i'll try them myself later

UPDATE: battery: it's been about 15 hours since i plugged out the charger. wifi has been turned on for about 12-13 hours,i downloaded some apps,opened a web page or two,made several calls,ran a few benchmarks,rebooted two times (one was necessary because i accidentally turned wifi off and couldn't turn it on again(the bug i mentioned),and the other wasn't caused by some bug or anything, i just needed the sd).so far so good i believe...15 hours is fine for me...i'll post when the phone dies out

UPDATE 2: battery: blackstone is dead...battery went out after exactly 16 hours,wifi was on for about 13-14hours...everything else remained pretty much as posted above

EDIT 2: is it just me,or the clock stays 10 minutes behind overnight...my alarm rang 10 minutes later than it should 2-3 times already,day after day,and the time was ok every time i checked it before going to bed...weird

EDIT 3: oh yes, i forgot occasional calls without sound,which happen just once in a while, so they're kinda acceptable,the solution is to finish the call over speakerphone or to make the call again

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

DEVICE: blackstone

PORT: froyo x 1.12.

SYSTEM: (the one provide with 1.12)

KERNEL(zImage/modules): 2.6.27.46-01232

CLOCK: 528 MHz

MFLOPS: 3.721 :O

TIME: 22.53

NOTE: wifi turns on,but can't scan because mac address is missing - can be solved

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

DEVICE: blackstone

PORT: froyo x 1.21.

SYSTEM: (the one provide with 1.21)

KERNEL(zImage/modules): 2.6.27.46-01255 (found in thread: http://xdaforums.com/showpost.php?p=10829216&postcount=27)

CLOCK: 528 MHz

MFLOPS: 2.26

TIME: 37.09

NOTE: have been using it for a while and everything works,although it could be a bit faster (wish it was as quick as 1.12)
[Touch HD Android Development] afr33s:
So many views and no reply! So I thought I'd reply and say good luck. I would like to know which Android build works best on the Blackstone so I hope you get some feedback.
[Touch HD Android Development] farukb:
thank you mister turtle-guy :) i was thinking that people might be willing to find out which one is "the best"...and i thought that there will be some feedback....BUT nevermind,i'm gonna take another sd and put other ports...and let you all know :)

cheers
[Touch HD Android Development] mcmaus:
Hi,my result

DEVICE: Touch HD

PORT: xdandroid 2.2.1

SYSTEM: FRX03

KERNEL(zImage/modules): 2.6.27.46-01222-g9825e75

CLOCK: 528 MHz

MFLOPS: 1.94

TIME: 43.22

Booted to android at 57% of battery.

30 minutes of calls

WiFi-4 hours

E-mails,Web,playng etc

2 times booted back to WinMo and than back to android(Need to take photos in WinMo)

The Battery indicator is jumping up and down like a goat.Phone is turned off all of a sudden.

The phone has drained after approximately 9 hours off use :D

Sorry for bad English.

(my 1 post )
[Touch HD Android Development] moharu:
DEVICE: Touch HD/Blackstone

PORT: FRX03

SYSTEM: Huawei U8150/Froyo X/Sense X/Neopeek CM barebone (with 2 sd card) 2gb normal micro sd card and 8gb hc micro sd

KERNEL(zImage/modules):2.6.27.46-01231-gfca2168 (wifi works as well froyo/sense X

CLOCK: 600 MHz (620000Khz)

3d drivers:11.26 and 11.30

Longest Battery LIfe: 16h 44mins (Froyo X/Huawei U8150)

hmmmmmm

you can ask me for more information

just quick reply
[Touch HD Android Development] farukb:
could you separate the results for each one,and do linpack benchmark for each one as well,plase? and by the way what froyo x versiona re you using? 1.12.?

and did you try the trick that tiag8 did for the camera on rhodium (double kernel)...can it work with our hardware
[Touch HD Android Development] moharu:
i dont what a linpack benchmark is

i am using 1/17 version and 1/12 i just deleted Sense X (need space)

no i havent tried the camera as it is pointless as no one has done it yet

the camera app works but i dont see nothing (i havent tried the camera kernels as it crashes when i boot to android
[Touch HD Android Development] jeanfrederic:
DEVICE: blackstone

PORT: XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE

SYSTEM: FRX03.21.11.10

KERNEL(zImage/modules): 2.6.27.46-01226

CLOCK: 528 MHz

rootfs-20101115-42b44e2

MFLOPS: 1.714

TIME: 48.91

1Gb µSD no class

Fast battery consumption

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

DEVICE: blackstone

PORT: XDAndroid 2.2 (rel 1.6)

SYSTEM:

KERNEL(zImage/modules): 2.6.27.46-01219

CLOCK: 528 MHz

rootfs-20100903-120206

MFLOPS: 2.951

TIME: 28.41

2Gb µSD no class

Normal (not benchmarked) battery consumption
[Touch HD Android Development] farukb:
yeah,that's what i thought too...does the 1.17 necessarily have the "mute call" bug

linpack: http://www.appbrain.com/app/linpack-for-android/com.greenecomputing.linpack

pretty sweet score
[Touch HD Android Development] darker01:
DEVICE: Blackstone

PORT: Neopeek Barebone CM 6.1

KERNEL(zImage/modules): 2.6.27.46-01245

CLOCK: 528 MHz

MFLOPS: 2.762

TIME: 30.35

BATTERY: About 18 hours
[Touch HD Android Development] farukb:
updated first post with froyo x 1.12...downloading froyo x 1.21

EDIT: still trying to enable wifi on either of these two :/

anyone has any ideas...i did some searching but found nothing (yet)

EDIT2: wifi partially solved...new kernel did the job (1253),it can turn on,but it's unable to scan for networks
[Touch HD Android Development] mcmaus:
My next test and score

DEVICE: Touch HD

PORT: Neopeek 2.1

SYSTEM: Neopeek Team Eclair by Kenia 2.1

KERNEL(zImage/modules): 2.6.27.46-01215-g0d9a989

CLOCK: 634 MHz

MFLOPS: 2,468

TIME: 33,97 sec

Battery-Testing

Post later my result

(sorry for bad English)

Update- Battery 9Hours.After discharged battery i switched back to WinMo.

I will test other builds.

(sorry for bad English)
[Touch HD Android Development] Spige:
Froy FRX04

Blackstone

710mhz

MFLOPS 2.518

Time 33.3 sec

Battery 13Hours 42% left no wifi allmoust stanby only few calls few messages

Kernel 2.6.27.46-01219
[Touch HD Android Development] farukb:
arrrghhh says froyo x is as almost as rip off of the xdandroid port,but it seems to be faster,especially 1.12 version,it just files.the score i posted in first post is without overclocking,just plain 1.12 with zeam launcher...
[Touch HD Android Development] Laestel:
DEVICE: blackstone

PORT: FRG83 by neopeek

SYSTEM: R5

KERNEL(zImage/modules): modules-2.6.27.46-01221-g2e4a607-dirty

CLOCK: 620 MHz

MFLOPS: 2.611

TIME: 32.16
[Touch HD Android Development] Spige:
Froy x

Device:Blackstone

Mflops:3.49

Froy x

Kernel 2.67.27.46-01231

Clock:528mhz

Battery= ??
[Touch HD Android Development] farukb:
which version?
[Touch HD Android Development] Spige:
andboot froyo x.2011.01.12
[Touch HD Android Development] mcmaus:
DEVICE: Touch HD

PORT: 2.3.1

SYSTEM: XDAndroid

KERNEL(zImage/modules): modules-2.6.27.46-01255-g68e3665

CLOCK: 528 MHz

MFLOPS: 2,265

TIME: 37,02

Wifi works more then 2 times on/off switching:)

3,5 jack-ok

You need other keyboard app....like better keyboard or swype...

For my da BEST :D Still testing and i will post more info next time.

Sorry for bad English
[Touch HD Android Development] olsly:
Device: Blackstone

System: Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)

Kernel:modules-2.6.27.46-01276

Clock: 633

Zimage: from here http://xdaforums.com/showthread.php?t=653387

MFLOPS: 3.67

Time: 22.84

Battery: testing...
[Touch HD Android Development] olsly:
Another test

Device: Blackstone

System: Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)

Kernel:modules-2.6.27.46-01162

Clock: 633

Now everything is working!

MFLOPS: 3.5

Time: 23.95

Battery: testing...
[HD2 Android Q&A, Help & Troubleshooting and Genera] FirefighterDown:
Like I honestly don't understand it. They are obviously doing something wrong. I am running NAND with the SD card for applications (Stock 16GB) with gauner1986's HD-FI 0.3 with 2.15.50.14 and I have only 2-5ma battery drain on standby. But here's what I noticed:

Certain applications from Market increases battery drainage. If you install an app, begin to experience high battery drain, uninstall it.

It's a 3G phone for godsakes. Why disable the speed of it by going 2G?

Disable WiFi/Bluetooth/GPS when not needed.

Don't disable AutoSync or Background Sync. I've noticed no increase with both of them except when it pushes email, updates

Keep the brightness UP to 100 percent. I saw no difference upon lowering it.

Don't disable APN either. This isn't your dumbphone, it's meant to have internet. Internet won't drain your battery life if it isn't active.

SetCPU is pointless. I don't even touch it as the risk to damage your phone using it is great. There has been no solid evidence this helps your battery life other then to SLOW down your phone.

Don't use a TaskKiller - Common sense, it eats battery. Android is programmed to kill apps.

On standby, it can last for freaking days even under light/medium usage. Constant heavy usage will make you last at-least a day.

Seriously. If you get drain, you have the wrong radio or application. I even tried uninstalling stock applications like Calender and removing widgets and they had no effect on my system. If you have to disable MAIN smartphone features, you might as well go back to:
[HD2 Android Q&A, Help & Troubleshooting and Genera] jonny68:
I agree with most of what you say here but not this

Personally i think your better off keeping the brightness as low as possible as i did experience battery drain when i had it up to 100%.
[HD2 Android Q&A, Help & Troubleshooting and Genera] hello00:
I have a taskkiller and I don't notice any difference at all. Having the brightness to 100 does drain your battery that's just common sense.
[HD2 Android Q&A, Help & Troubleshooting and Genera] OrionCarl:
have no probs with batt drain, i dont use appkillers, brightness on about 45%, play music most of the day, internet on all day with updates, txt and call daily, still on 75% now, not a problem
[HD2 Android Q&A, Help & Troubleshooting and Genera] StephanV:
True.

Because it really is a battery consumer. Actually, surfing on 3G is more power consuming than on WiFi, and Edge is fast enough for a fair amount of uses. Having a 2G/3G toggle widget is probably best, indeed no need to dumb down your phone too much.

WiFi & BT are obviously true, GPS is bullocks. As long as there's no GPS app running (i.e. there's no GPS icon in the status bar), your GPS is not active and is drawing zero current. It's just a setting.

For some people, with certain apps behaving in a certain way (for example business people getting emails every minute), this can really be a serious battery hug. Again no need to dumb down your phone too much, but it if you really need to squeeze out those extra hours of juice this is a valid option.

That's plain rubbish. More brightness = more emitted light = more emitted energy. Read a physics book someday, this really makes no sense. Display is one of the biggest battery hogs, especially when actively using your phone. Leaving it on a low brightness level sure helps heaps.

First part is true, enjoy the features your phone has. It does drain your battery though, even when inactive. There's no such thing as a free meal. Disabling mobile data won't double your battery life, but is a very valid option when you really need your phone to last just that little bit longer.

Bullocks again. First of all, underclocking cannot damage your phone in any way. Obviously no scientist has done research (actually, someone probably has but I don't feel like googling any right now) to provide solid evidence on the matter of cpu clocking affecting battery life, but any tech-guy with some experience will disagree with you. No need to clock down your CPU to 245Mhz obviously, but a 900Mhz clock speed will still more than suffice for most users. Again this won't significantly boost battery performance, but all the small bits help.

Probably the most valuable information in this thread - spot on!

Define heavy usage. How about playing Angry Birds at 100% brightness, while listening to Pandora with your Bluetooth headset/headphones, through a 3G connection obviously. Not a very far-fetched setup eh!

I'll buy you a cookie if you last more than, say, 6 hours. You probably won't last 4 hours either but I really don't feel like buying you a cookie.
[HD2 Android Q&A, Help & Troubleshooting and Genera] dan138zig:
fixed ;)

ten char
[HD2 Android Q&A, Help & Troubleshooting and Genera] wineds:
As other posters have said that is nonsense mate. You can easily see with current widget that the consumption is higher with higher brightness.
[HD2 Android Q&A, Help & Troubleshooting and Genera] slk-A4:
Bluetooth battery drain is the only issue

Coming from Windows 6.5 -as we all do- we all discuss the battery drainage.

All reasons for battery drainage given in this thread are true (bright screen sucks battery, 3G does etc etc.).

BUT WHY DOES THIS HD2 on ANDROID SUCK MORE BATTERY THAN THE SAME HD2 ON WINMO?

The bluetooth drivers obviously are not the right ones. On Winmo there was no significantly higher battery drainage with bluetooth on than with bluetooth off.

In all Android Roms that I have tried (and I tried them all), bluetooth empties the battery with about 60mA.

Who knows a rom that does not have this bluetooth problem? :confused::confused::confused::confused:
[HD2 Android Q&A, Help & Troubleshooting and Genera] FirefighterDown:
I work outside in direct sunlight, where low settings makes it not viewable. I have it to max and even at home at 40 percent, I see no changes. Probably because of my usage pattern.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FirefighterDown:
Taskkillers have been proven to drain your battery. Google themselves have said it and admitted it in complex details. There's a thread on it that Ill pull up later at home. Like I said I see no differences in my battery report.
[HD2 Android Q&A, Help & Troubleshooting and Genera] MattOG:
Sorry for this post.... but this made me laugh hard..... :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] TheATHEiST:
So why when I run a task killer I get over a dozen apps running in list and when I close them my free RAM goes up, surley if they are using ram they are using energy?

Also surely the energy that these apps are using is MORE then the energy of the task killer itself?

There is ****loads of apps that just seem to run themselves in background and have no need to, I set my killer to kill every 30 mins or whenever screen is off aswell as manually when I choose to.

Can you provide any evidence that the task killer uses more energy then all the apps running in background combined as I seem to get much better battery with it then without it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] StephanV:
No, just being in RAM memory does not (or maybe very little) use energy. When idle, they're just stored there. A lot of apps simply restart soon after you kill them, consuming a lot more power than just leaving them be, and on top of that you may experience bad app behaviour.

Well, if those apps do stuff they shouldn't be doing, they're badly developed and should be removed or updated, simple as that. Chances are though that those apps really need to be running (and their battery consumption doesn't necessarily have to be high), in which case killing them is even worse.

A lot of well known devs have very clearly pointed this out multiple times (Cyanogen for example is one of them), even Google twittered about it. Do some research, there's plenty of info on it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] gamecore:
It was good to know that info, i never knew that app killers could do more damage and use more power than none at all.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FirefighterDown:
No. Android kills applications to free up RAM usage when i needs them.

Also incorrect, most applications are killed upon exit/back key hit. Or put into a suspended mode that eats no battery (Android Browser, Facebook etc)

If only that was true. Killing applications will restart them which uses RAM to restart them which can also slow down your system. Applications don't run unless they are continuously fetching/streaming data or providing a service.

Ha, I don't believe you.

tl;dr version at the bottom.

The following diagram illustrates these loops and the paths an activity may take between states. The colored ovals are major states the activity can be in. The square rectangles represent the callback methods you can implement to perform operations when the activity transitions between states.

tl;dr version

- Android is hard coded to automatically kill a task when more memory is needed.

- Android is hard coded to automatically kill a task when it's done doing what it needs to do.

- Android is hard coded to automatically kill a task when you haven't returned to it in a long time.

- Most services (while possibly running in the background) use very little memory when not actively doing something.

- A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.

- Killing a process when it isn't ready only causes it to have to reload itself and start from scratch when it's needed again.

- Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.

- Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.

- The only true way to prevent something from running at all on your phone would be to uninstall the .apk.

- Most applications will exit themselves if you get out of it by hitting "back" until it closes rather than hitting the "home" button. But even with hitting home, Android will eventually kill it once it's been in the background for a while.
[HD2 Android Q&A, Help & Troubleshooting and Genera] StephanV:
I'm not sure I'm with you here. I do have push email enabled, and it's one of the things I like about Android. What does Blackberry have to do with this? Missing your point.

Well, in your case, it may not be a noticeable difference. It does for people who get a lot of emails. Exactly like I said in my previous posts. What is your point?

Well, I'm 100% sure it affects you too. You can't just create energy out of nothing. Upping the intensity from lowest to highest easily adds in an extra 80mA, and that's just a rough and probably too low estimate.

Have you ever compared you HD2's battery with a laptop battery? Not quite in the same league of size now is it. Moar size = moar powers (well, kind of). Dumb laptop comparison, sorry to put it like this.

You can go ahead and try to reinvent battery usage all you want, but a 4,3" screen is and always will be one of the major battery hogs on a phone like this.

Are you? I haven't even used the word 'overclocking' in my entire post, of course that's bad for your hardware. Underclocking isn't gonna do **** though. I'll buy you another cookie if you find a valid source backing that statement up. But let me give you a hint: ain't gonna happen José. Just sayin'. (Disclaimer: I'm talking about realistic/plausible underclocking situations here, applicable to comparable hardware)

Uhm actually there has. Moar CPU = moar heat = moar power loss = moar battery loss. Again, conservation of energy, which could be found in the book I advised you earlier (well actually a thermodynamics book would be more appropriate).

Sounds like some very valid empirical proof you got right there. I'm sorry, but I could care less about your 1 comparison with that unknown phone of your unknown buddy, whom I have no clue about if he can even properly configure SetCPU or has a properly configured battery.

150-200mA while playing Angry Birds @ 100% Brightness, while listening internet radio through 3G and BT headphones? Sorry, that's just physically not possible, hardware-wise. Not ever ever ever ever gonna happen, so you are either lying your ass off or have no clue how to check your current usage properly.

I think I'm sounding like a major douchebag here, but I don't really get it how you feel like you know all about this stuff when very clearly your technical knowledge on this matter is really limited. I'm very happy for you that you're happy with your battery life, but don't try and preach this like t3h l33t battery solution, because put simply: it's not.
[HD2 Android Q&A, Help & Troubleshooting and Genera] overshadowss:
[*]Keep the brightness UP to 100 percent. I saw no difference upon lowering it.

actually this is so funny dude .. :D

more light NEEDS more power .. this is so simple.. like 1+1=2
[Desire HD General] daniello8:
When I try to select the contacts for my phone I only have "all contacts" offered for my gmail active sync connection. I don't want to sync all contacts but just one category which I have set up especially for my phone's phone book.

Is there any way to facilitate this?

My current workaround is: sync contacts with google sync instead of active sync. Then I can select exactly the category I want to "see". This way I have to live without "push" though - which I don't really like.
[HD2 Android Q&A, Help & Troubleshooting and Genera] jkolner:
Sorry if im blind or just stupid - or both - but is it true that there isn't any new MAND ROM from 2011 with HTC Sense?

And another question - what do you prefer: Gingerbred or Froyo with HTC Sense?
[HD2 Android Q&A, Help & Troubleshooting and Genera] stevar:
Mand? If you are talking about a nand build with sense i'm using this:

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

And it's working better than wm 6.5 for me.
[HD2 Android Q&A, Help & Troubleshooting and Genera] jkolner:
Thanks, ill try.

And its ofcourse NAND and not MAND ;-(
[HD2 Android Q&A, Help & Troubleshooting and Genera] stevar:
He's uploadin a new version right now. It's going to be even faster managing data files from sd.
[Android Q&A, Help & Troubleshooting] marclais:
I lose phones... habitually. Sometimes they find their way back to me and sometimes they don't, It is unsettling to me that even if I have a security app installed, or a GPS tracker that anyone with the ability to perform a google search can simply factory wipe my phone and make it their own.

So the question: Is it possible to include a password requirement to access the bootloader or recovery? I realize that if you forget your password there would likely be no way to save your phone in the event you need to, but I don't forget my passwords so this does not affect me.

Just wondering if this is even possible or worthwhile. Any input will be appreciated.