yashsingh1/xdaforums huggingface dataset:
[Touch HD General] kidcash:
Hi Guys,

I've just got a HTC Touch HD. I've got a few questions.

1. With HTC Interface disabled, on the normal start menu there is a gap at the top, I'm wondering how I can get rid of this

2. The font on the start menu is too big and other menus too, any way to change this via registry? and also the font on dropdown (well drop up) Menus.

3. Any way to get the default windows 6.1 style volume control instead of the HTC One?

4. Getting rid of the HTC Style input selection and replacing with normal windows type.

5. Is there anyway to get the "New" menu on the Today Screen on WM6.1, pretty sure i've had it on other wm6 phones

6. Is there any "must do" tweaks on this device to improve performance and functionality, I've found that it's not much more responsive/fast as my old HTC Himalaya using the classic WM6.1 Screen. Photos seem to zoom in quite jerky on the Touchflo interface etc, just expected a bit more from this quite new device, and the game "Teeter" also seems a bit slow, would have thought the 500mhz processor would be more than enough to play it smoothly, seems the only device that I've seen play it smoothly is the 1.2ghz HD2. Also a HTC HD Fake I had, with a Marvell Monohans chip ran much faster.

7. How Can i Change the fronts on the today screen to the normal type, I have put Clearview off but it's still the "calibri" type font, wondering how to change

to the normal font like this :

8.

Also I'm having a problem with my GPS, my program cant detect it, the program I'm using is called GPS Performance it cant connect to the GPS.

In the "External GPS" Option, what settings should be selected on the Programs port, hardware port, Baud rate and should I use the "Manage gps automatically" checkbox. I find that It doesn't let me change the Hardware port, it's set to none.

Thanks guys, P.S I've read the FAQ's before posting.
[Touch HD General] kidcash:
Hi Tony,

1. Thanks, I just noticed that it fills up with recent programs, anyway to remove this Gap though, it is useful for some people but I don't have much use for it

2. Thanks, Will try that out

5. I want to get this menu at the bottom :

6. Yeah I would think that 528mhz is enough to run Teeter as smooth as possible but on the HD2 its much smoother, I wouldn't think that game would require a very fast processor, I don't know if the Drivers for rendering graphics are bad on some of the Blackstone ROMS? or would it be the Teeter game itself? Anyone found a way to smoothen it up. I don't know if it's true but I've been reading lots of info saying Qualcomm Chipsets are junk for Video/Graphics.

As for the responsiveness of General usage, I don't know if the stock ROM is somewhat a bottleneck.

7. Thanks will try that

8. Ok, I had that set to Automatic, my program asks me which Port and Baud rate? What should I select, I went through all the Ports and it cant connect, I guess it might be a problem with the program, I'll see if the GPS Apps pick it up.

Also I might ask on this thread instead of starting a new one, my computer keeps telling me that I need Flash Player 8 to run the Getting Started disk, but I have already installed flash player and it still asks, other people have had this problem too. I've got Windows 7 Ultimate x64

Really, I am not a fan of Flashy interfaces with clouds descending and vibrating storms to tell me what the weather is, HD tried to copy Apple, but the Touchflo interface is often slow, buggy and non responsive, it's better in the Leo but on Blackstone it's somewhat problematic. I'm just used to the old Pocket PC's wtih the old Interface. The only reason I bought a Blackstone was for a higher res screen, better camera and Wifi

Another question - I've noticed the Blackstone seems to have no dedicated graphics/video accelerator that Coreplayer can support, so the Video playback is pretty appalling for a device named "HD". I have a video that isn't even the resolution of the screen of the HD and it only benchmarks at about 75% playback speed.

Is there any drivers that can make use of the MSM Chipset to give good video performance? I don't know but I thought the predecessor HTC Diamond had a 3D Accelerator. I'm not at all keen on converting every single episode on my computer using the Application for video playback on the HD that is out, so any chance to improve playback on the HD with coreplayer? Again coming from a person who had a Himalaya, it had an ATI Imageon chip that coreplayer supported.
[Touch HD General] raving_nanza:
here dude

Rn
[Optimus One, P500, V General] harshkey:
I need to revert back to stock official tmobile USA rom, Could someone please guide me through it???. Thanks alot.
[Atrix 4G General] Room7:
Is there a way to get just the Mobile Viewer part of the Webtop on my computer when i connect the USB?

I want to be able to control my phone through my computer, I dont need the rest of the webtop stuff.
[Atrix 4G General] diedemus:
use the phone portal app on the phone, it will let you use it via a web interface
[myTouch 4G Q&A, Help & Troubleshooting] Freek91:
has anyone had the issue of the battery dying extremely fast after a stats wipe?

so i wiped battery stats after following the directions for royalginger...but was never able to get the rom to boot...so ive loaded up a backup...but now the battery is losing about 3-5% every 30 minutes with the phone just sitting idle on my desk

this battery normally would normally sit at 100% for at least 9 hours idling just sitting on my desk overnight or just while i work on the computer

so the details...im running IG 1.1.6 with Faux's 0.7.7b kernel...OC'ed to 1209max/368min...watchdog claims to have 49 apps running with 1% used and 95% idle...wifi and wifi calling enabled

so anyone got any ideas? is it normal to see battery drain quicker after stat wipe? should i let this drain and then follow one of the calibrate battery guides?

im at a loss here...i just want my 9 hours at 100% back
[myTouch 4G Q&A, Help & Troubleshooting] grkmano:
I never got 9 hours just sitting I'm trying to get that now...
[myTouch 4G Q&A, Help & Troubleshooting] edru:
From what I gather you really aren't suppossed to do a stats wipe as of now. Since there is a bug in the phone/recovery which powers the phone on while charging there is now way to fill the battery to a true 100% so you could then wipe the stats.

If you did, chances are you wiped when your phone realyl wasnt at 100%, thus now your 100% is really 90.,.
[Samsung Mesmerize] jbrown91:
Hello, my GPS keeps continually running when I have it turned on. It never turns off in the status bar and keeps rotating just like it does when you are using it for GPS related activities. Is this an easy fix? When I turn the GPS off manually, this stops. Thanks
[Samsung Mesmerize] sageDieu:
If it is on, then it is on. If it is off, then it is off.
[Samsung Mesmerize] jbrown91:
I understand that. But after I flashed it again, the GPS continually runs. Not just when an app is using it but ALL the time. It drains the battery quite fast. On 2.1 and 2.2 (1st flash) I never had the problem. I would imagine there is something going on.
[Samsung Mesmerize] droidzach:
If you turned it on it will constantly run and search for satellites because it works in real-time. If you are inside say it has to work harder and constantly search for those satellites because it cannot find then as easily. so it may drain your battery quicker. Your best bet if its really killing your battery is to turn it off until you plan on using it. I personally have my gps on all the time now and dont see much of a difference. Not saying that you aren't having issues, beside I believe you on that. Also are you trying to say that your GPS is on even when you turn it off? That would be an issue. But if its just working in the background that is to be expected. Like I said try turning it off if you dont plan on using it to see if that helps your batt life. If not then you will learn if it's GPS or another app our 2. Also some people have had better battery life on 2.1 and some on 2.2. I personally think that the differences are entirely based on usage and your apps and widgets.
[Samsung Mesmerize] sageDieu:
Lol sorry then, I thought you meant like "I turned my GPS on and now it is on, what do I do"
[Captivate Q&A, Help & Troubleshooting] djsilver666666:
I can't understand why this is happening, but if I send a text and the recipient replies within about 1 minute of my sent text, then their reply is placed above my text to them.

This started happening sometime when I was using Android 2.1, and has persisted with Froyo (2.2).

What my device shows:

(see first attached image)

And what it should look like (corrected with photoshop):

(see second attached image
[Captivate Q&A, Help & Troubleshooting] dingokevin:
Check you settings make time and date age in auto. Had something like this few months back. Hope it helps.
[HTC Inspire 4G] jjjjjk:
got inspire yesterday. will try to root it in the weekend. before I root, what do I need do? shall I write down anything or backup anything?
[HTC Inspire 4G] mudknot2005:
Make a gold card. Most if not all your apps will be synced to your phone through google.
[Droid Incredible General] pianoplayer:
Wow, this is a shocker. I guess I should kill the habit of using higher brightness and be less afraid to OC.
[Droid Incredible General] byrong:
I notice you have an SLCD DInc. It's worth mentioning that mine is AMOLED and I don't know if the two have similar power usage across the brightness scale.
[Droid Incredible General] pianoplayer:
Wow, I didn't notice that. I guess you're right. I read somewhere that darker themes help on AMOLED and lighter themes are better for battery on SLCD. My theme is quite light so I think that makes my on the less-consuming side for the screen.
[Droid Incredible General] ctinsley:
byrong, this is awesome data. Just what I needed to see, thank you. I have the exact same setup and have been trying to figure out the best cpu/brightness settings for my device. With seeing this data its helped me determine some of the values I was going back and forth on. Now I guess I'll have to wait and see how my battery holds up.
[Droid Incredible General] kdb424:
Excellent. Thanks for the data. Even if I never put any of that into use it's still fun for the nerdy part of me (most of it :p) to know! Excellent data, and just goes to show how important screen brightness is over the CPU Speed. Most users would probably get better battery life if they spent more time darkening the screen than installing a CPU governing program haha.
[Droid Incredible General] i8qbert:
Great info! Kinda knew this already but cool to see it all graphed out.
[Droid Incredible General] userjf:
Thank you for the graphs! I have the SLCD... but I think the results would be similiar regardless of screen type, especially in real-world usage.
[Droid Incredible General] Forgetfull:
Awesome work. Gives me some ideas about using setcpu...
[Droid Incredible General] Gorilla*:
Chad give me more description... what new features are in the new kernel....
[Droid Incredible General] phaze one:
Ummm? It will enable you easier entrance/exit from the matrix.

Nice work btw byrong.
[Droid Incredible General] burnmatoaka:
Horay for empiricism!

Thanks for the legwork and for sharing. Impressive.

[I for one welcome our new Android overlords ::: DInc::SLDC::x.7.28::CWM3.0.0.8::CM7::chad's]
[Droid Incredible General] burnmatoaka:
Aren't we calling it "the Grid" now?

[I for one welcome our new Android overlords ::: DInc::SLDC::x.7.28::CWM3.0.0.8::CM7::chad's]
[Droid Incredible General] AdhvanIt:
Byrong,

Fantastic write up as always..

I'm curious if you would care to do one on the effects of a task killer on battery life/CPU and RAM usage?

Since Android launched cupcake, I've been strongly opposed to the use of task killers, as Android handles processes much better than we do.. but I would love to see if fact can back up that opposition or if these apps truly don't cause any harm.

I'm just not nearly as amazing with words and data as you clearly are. :-)

via Incredible Redemption
[Droid Incredible General] TodesEngeI:
Man, I wish I hadn't just given my mom my DInc and instead played with it some more. I would love to help do some more long term tests to help with this.

That and seeing the variation for screen type, mine being an SLCD.
[Droid Incredible General] byrong:
Thank you all for the kind words.

Great idea.

I'm game, but I would have to think long and hard about how to design the testing parameters. In all likelihood, I'd need some suggestions / ideas from you guys to carry out such a test.

I would need recommendations on a reliable logging program for RAM, CPU Freq, and CPU Load.

Unlike most of my other power testing, I would not want to run such a test in Airplane mode. One of the reasons that people give for aggressive task-killing is shutting down processes that may be using data in the background. As such, I would need conditions that actually allowed an observable difference in data usage.

Since the phone won't be in Airplane mode, my controls take a big hit. During a test, for example, I might receive a lot of calls, texts, and emails, all of which will have a major impact on CPU, RAM, and battery. The cleanest solution I can see is running the test across multiple nights: X full nights without a task-killer and X full nights with one.

The other big question is how to set up the task killer. I.E. should I allow it to kill everything, or set up an exclusion list? I'm leaning towards the exclusion list, but then we have to decide what to exclude. We should also think of a designated interval for the task killer.

If you want to help me brainstorm these issues, I'm happy to discuss them right in this thread.

The beauty of this type of testing is that it can be done by any motivated individual, on any device that allows scaling of the CPU. If you already have that new TBolt of yours rooted, you should be able to recreate the tests on that. I'm sure fellow TBolt users would love to see your findings.
[Droid Incredible General] AdhvanIt:
SetCPU has a lot of the logging/current system information that you would need, including:

CPU frequency: Time in state for each freq

CPU load average

Total and available RAM

As well as a number of other things. Screenshots are attached below.

As for controls, I would think auto kill at screen wake is a commonly used setting. Or maybe go at 1/2 to one hour intervals...

If you're going to set up a blacklist within the task-killer, I would recommend not adding too much to it, as the exclusion of too many apps would alter test results. But certainly add any auto-updating widgets you have to it.

I think leaving data on is also appropriate for this test-there are a number of apps that will not start/update (mostly web based like twitter/facebook and such widgets) if there is no data connection.

Edit: Forgot to add images. Lol.
[Droid Incredible General] byrong:
The info tab in SetCPU is indeed helpful for more of a 'snapshot view', but I don't know of a way to make it log that information to a text file over time, do you?

Time in state is helpful, and can be accessed via:

/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

But the problem is that it doesn't tell the story of when the CPU was scaling. It would be far more useful if I could plot CPU load and CPU freq over a time line, rather than just have averages or sums.

Same story with RAM: I want to be able to plot over the course of time.

I like to automate my tests as much as possible, not only to (try to) remove myself as an influence, but so that I'm not tied to the phone for hours at a time, looking at a watch. If I did a screen on/off setting, it would require me to turn the screen on and off at select times, remaining consistent between tests.

So intervals would definitely be the way for me to go. I think I'll start a poll of some sort to get an idea of how most people set theirs.

Agreed that I want to keep the exclusion list to a minimum. I will make this part of my poll as well. I don't want to create a strawman position by setting up the task killer to be more aggressive than anyone actually uses it. For example, I don't want to set it to kill Android OS, Launcher, etc, as that would just be excessive and probably does not reflect how anyone uses them.

This will be an extremely controversial one, and if I don't strike a delicate balance, people will be quick to throw out the data completely on the grounds of, "Well that's fine and all, but that's not how I use my Task Killer."

Thanks for helping me think this through.
[Droid Incredible General] AdhvanIt:
Definitely makes sense to automate...

I'm not really sure of any way to log these things regularly unless you know how to set up a script and have it pull the logs every so often...

Agreed-It will likely get met with debate regardless, as it's always had its fanbase and its opposition. Not sure really how to get a good balance, but I think the polls are a good way to start.
[Droid Incredible General] byrong:
Survey is up: http://www.surveymonkey.com/s/8GD2F2H

(Posted here to reach a wider audience: http://xdaforums.com/showthread.php?t=1032456)

I decided to keep it as simple as possible, both to encourage more people to respond, and to simplify the collection of responses.
[Droid Incredible General] TodesEngeI:
Not yet, just got it two days ago. Playing with a lot of apps as far as battery saving/ 4G LTE disabling / video chat. Lots of fun features to play with. Contemplating waiting for GB release to root, but might get impatient like I did with my DInc.

I think what would be critical for testing is that all phones run the same software as far as background apps and whatnot. While important what ROM will make the most of your battery, we should look at less "extreme" changes first. Airplane mode / WiFi only / stock apps + testing apps / Mobile Data / LTE (if applicable)

All sorts of testing scenarios.

(in the process of formulating the above list, a curious question comes to mind: would a phone with full internal memory deplete battery faster?)

Also please bear with me, just joined XDA with this phone thinking the potential was greater, obviously I should have been here when I got my first Android phone.

Sent from my TBolt
[Droid Incredible General] AdhvanIt:
As far as faster depletion of the battery that's part of the basis for the test. Some feel as though the use of a task killer not only helps battery life by minimizing open applications, but assists with the overall speed of the phone by decreasing RAM usage.

While others believe that the Linux kernel and androids internal process management do a far better job of this than we are able to do with the use of a task killer.

The ROM and settings are less important than you might think. Although having an effect on battery, these are not processes that will be killed, so they would essentially be excluded from the study. Its a test to see the differences between use with and without a task killer-Not just overall performance.

via CM7 Inc
[Droid Incredible General] byrong:
AdhvanIt,

Just wanted to fill you in on my progress, bro:

I'm getting a fair number of responses to the survey (79 so far), but there's already a troubling lack of internal consistency with responses. For example, 52 respondents (65.8%) said on question 2 that they do not use Auto-Kill. Then, on the very next question, 57 respondents (72.2%) said that they do not use Auto-Kill. There should be no reason for this discrepancy.

I'm going to let the survey run for a couple more days before closing it.

I think I've got the necessary level of logging figured out:

Detailed info on memory usage can be logged from /proc/meminfo

Current CPU frequency can be logged from /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

CPU Time in State can be logged from /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

It looks like CPU % can be found through the vmstat command, or calculated manually from values found in /proc/stat. Just reading up on this now, so I'm still looking into which is cleaner/easier. Frankly, with the ability to log current frequency and time-in-state, I'm not sure I'll even bother with calculating CPU %

Of course, that still leaves the design of the test parameters, which will be the next (and biggest) hurdle. Suffice it to say, I'm still a number of days out from even starting the actual tests, much less having hard data in hand :(
[Droid Incredible General] AdhvanIt:
Lol@poll results.

Have you figured out a way to determine when the CPU is ramping up so it can be compared to when the task killer is set to kill apps?

Its cool, man. Take as much time as you need. I know the data collection alone takes several days when done properly.

As for perameters, if you need any more help setting them up when you get to that point, you're welcome to get at me on gtalk. AdhvanIt@Google.com
[Droid Incredible General] c00ller:
As an engineering graduate student, I approve of the quality of your post :) Just noticed that your x-axis "Frequency" labels are missing units, but it's very minor as I think we all know what they should be ;)

The topic of dark themes on an AMOLED and battery life effects was mentioned earlier, and just thought I'd like to clear that up with an explanation.

For equal brightness settings on an AMOLED, darker images (more "black") will result in less power consumption. Why? Because in an AMOLED, every pixel is its own light source and possesses its own on and off state. Therefore, darker wallpapers, images, themes, etc will have more pixels at a low-power state and lead to decreased overall power consumption. On the other hand, LCDs have a backlight that is always on, even when looking at a "pure black" image. To produce the dark image, the LCDs have liquid crystals at each pixel that polarize the light perpendicularly to each other so that (theoretically) none goes through. However this is not perfect, and there is always some leakage of light. This is why blacks on LCDs never look as black as they do on AMOLEDs (and have a lower contrast ratio), whose pixels can turn off to produce true blacks. Basically for dark images, AMOLEDs dynamically go into a lower power state while LCDs are static and maintain one relatively high power state at all times.
[Droid Incredible General] k_nivesout:
Informative post, thank you. I understood the basics of OLED vs LCD but that explained it better than what I've seen.
[Droid Incredible General] Bort76:
SLCD Current Draw

A little while ago I performed a similar test with my SLCD Inc. I used Tasker to gradually increase the brightness and recorded the current with the battery monitor widget. I don't remember what CPU settings I was using at the time, but predictably the current draw is very linear with brightness setting.

View attachment 701044

It has really encouraged me to keep the brightness to a minimum. Just an FYI for the SLCD folks.

EDIT: I looked back over my methods and it looks like the value on the graph is after I subtracted the baseline current. So, if the display was off and the average draw was about 45mA, I subtracted that from the current with the display on. This way, the current on the graph is a pretty accurate estimation of the actual display usage alone. I'm still not certain about the CPU settings, but I think I would have controlled for that.

If you are trying to calculate the contribution of the brightness setting to the overall current draw for an SLCD display, the linear relationship seems to be [0.562*brightness - 70.1] mA. Or, the difference in current draw between two brightness settings would be [0.562*(brightness_high - brightness_low)] mA. You get the idea.
[EVO 4G Themes and Apps] dr69:
i was just wondering if theres suchan app is a game that i played on my iphone is called Plants vs zombies..

is it available for Android? for EVO 4G?
[EVO 4G Themes and Apps] triscuit1983:
The answer is yes. Its a paid app so you won't find it here. But a quick google search should bring you something.