Related
I previously sorted out the locking up problems with help from you guys on here, and I'm sure that I have seen something about a battery indicator on screen when not using O2active but can't find it. Can someone post a link to the thread if it actually does exist or does the function not exist out of O2active?It's quite possible that I had a "moment" and imagined that I saw this of course - it's an age thing, hopefully!
Cheers. Alan
Why not load up the GPRS monitor program that the device come with and configure that to display Battery status on the screen - after its free, and a damn good utility if you use GPRS to track the cost - Mike
Or download Batti (just search for it - it's free)... I use it, and love it, for various reasons I won't bother to detail here
Thanks for that, I'll do a bit more digging. I don't use GPRS for monitoring (as far as I know) so I'll have a look at batti.
In. Done. What a handy little thing! Thanks again.
There's several, really... I like to classify them graphically as...
A. Applications
B. Today screen/Tray
C. Task bar
D. Top/Bottom overlay
The first group, Applications, I wouldn't even bother with. They tell you what the battery level is, and sometimes more information, but you do need to actually run the application. So there's no quick view of what the battery level is at any time.
The second group is nice if you're on the Today Screen a lot. They typically have nice graphics. However, they'll only be on your Today Screen, and take up space there. Very often the larger "Does everything!" applications that use the Today Screen will have one of these, typically along with indicators for memory and storage space.
The third is a bit nicer already. You can see it on any screen, as long as the task bar is in view. There's just one problem - they take up space on the precious task bar - and there's not a whole lot of space there on a QVGA device when in portrait mode. Some solve this by putting a tiny little bar underneath the clock - so much for getting a readout 'at a glance', though. In addition, any application that hides the task bar, will hide that indicator as well.
The last category, at least for me, is ideal - and Batti belongs in that category. Thes are the battery indicators that are usually just a line of a few pixels (or even 1 pixel, like Batti) high, going across the top/bottom of the screen. They're always visible, and you can easily tell how full your battery is even if it's just a white solid bar (such as what's in MagicButton).
They usually come in two flavors.. a solid bar going from left to right, or individual little bars, so that you can easily count in percentages. One of SPB's products comes with one of these, for example. Which style you prefer is really a matter of personal likings.
What's extra nice about Batti is that you can set it up to change the color of the bar at two percentages (e.g. 33% for 'low' with an orange color and 10% for 'critical with a red color), all user-definable. It can also indicate charging, and has a nice textual read-out of charge, voltage, temperature, etc. if you click on it (optional). The frequency with which it updates can also be setup. Some of the battery indicators poll every second, for example, thereby actually draining the battery a good bit itself more than it needs to. I have mine set up to update every minute, which is more than enough.
The *only* thing I would love to see added to it is alarms for the two percentages - which I've requested from the author, but haven't heard back from him as of yet Some of the other battery indicators may have alarms, so that might be something to keep in mind.
Batti
Where can I download Batti from ?????
http://www.google.com/search?q=pocketpc+batti
Battery meter.
I downloaded Batti and I dont think its very good at all !!!. The battery level indicator that comes with Pocket Hack Master is way better. However what I realy Real Real need is the OLD battery level software from WM2003. You know the one with red and green in the settings folder. Unfortunately I deleated it when I hard reset my phone.
Please anyone out there who has the old WM2002/3 still on file. Can you send me a copy of the file I need to make that work again.
Thankyou
Rob
I guess you'd have to state your reasons for liking the one that comes with Pocket Hack Master better
There's three things that are at play, to begin with...
1. Pocket Hack Master isn't free. Of course, if you are looking into the functionality it offers (CPU clock speed tweaking, etc.), then its built-in battery meter is a nice bonus when you do buy it anyway.
2. Pocket Hack Master doesn't run on all devices. Due to the fact that it is an application mostly geared towards CPU clock speed tweaking, it will refuse to run on unsupported processors such as the TI OMAP processor. I believe this doesn't apply to the Blue Angel, but does to e.g. the Wizard.
I have an HTC Wizard.
3. Personal preferences. Everybody will prefer their own style of battery meter, etc. You didn't fully explain why you like Pocket Hack Master's better, and unfortunately I can't fully review it as Pocket Hack Master refuses to work on my device. However, from some screenshots it appears that you can only set colors for battery or A/C (i.e. no change of color based on the charge level), the size appears limited (though you can make it a small 2px bar or a series of 4px blocks), and you can't set the refresh rate. On the other hand, you can fully control its positioning and hide the border. All in all - though again.. I'd have to actually be able to run it to make sure.. I haven't seen an screenshot of the 'gradient' method for example - I'd still have to stick with Batti on features alone.
Hopefully they'll add TI OMAP support soon, as it would be worth getting for that, for sure
For the curious, Batti was updated to version 1.4.
Added: Sound Events
Added: Option for turning off the frame around Batti
Added: Option for blinking on critical level
Added: Battery status on Info page (Charging, On AC, On Battery)
Added: Custom color for charging*
Some bugfixes
* charging is different from being fully charged. Sound events can be defined for charge start and charge end as well.
And I forgot to mention in my main rant that you can change the strings for localization easily - most of the main languages are already available for download
My question about this utilities, is which takes least memory space and battery life?
I hate to install something very usefu which on the downside slows down the device and makes me go crazy with the battery.
Of course anything that continuously monitors the battery performance will take up extra battery life itself, though it's typically negligable. Batti itself can be configured to poll only every N seconds - I have mine set to 60 seconds, but obviously there's no real reason to even set it to this frequency - the battery won't drop that much in a minute
As for memory use, I can't really report on others, and you have to keep in mind that several of the battery monitors are part of a larger whole; and if you want the larger whole anyway, then you typically won't lose any additional memory from enabling the battery monitor functionality. For example, MagicButton has a battery indicator line as well.
Batti takes up roughly 40KB
If you want a pure battery monitor proggie:
http://forum.xda-developers.com/showthread.php?t=364278
One of the best
This clock is based on Led Clock by David Horn posted on here some time ago. The principle of the clock is minimalism. The left column represents the hous, the next five columns represent minutes and the final column represents groups of five seconds (if you choose the 'show seconds' option). The hours increment upwards, the minutes increment leftwards then upwards and the seconds increment upwards. I have taken David’s original clock idea and bolted on lots of user options purely as an exercise to get up to speed programming for the compact framework.
Features
=======
Set individual colours for many elements such as hour leds, minute leds, second leds, frame, font and background.
Draw rectangular or round leds
Show / Hide seconds
Show digits on hours, minutes, seconds
Change led size – small, medium, large.
Imaging:
Load image as foreground, the image gets drawn piece by piece like a jigsaw as another led gets added to the clock. Watch your image build up on screen as the hour goes by. Alternatively you can set the image as a background image and the clock gets drawn on top.
Image Folders:
You can also specify a folder of images and set the rotation frequency to minute, hour or day. The current image behaves as above and gets rotated so you can have a new image loaded every day, or hour etc.
I am using GDI to draw the clock but it is heavily optimized. The thread only runs every 5 secs or every 60 secs if you choose not to show seconds. The drawing itself only draws what is absolutely necessary at any time. So if we are not refreshing / painting the form, usually we are only drawing a single led therefore this should be light on resources. As evidence of this, consider the fact that I am not using double buffering anywhere and yet the redrawing is always flicker free and stable.
I wrote this clock as a Touch HD owner but tested it on several of the mobile images. It should run on any Windows Mobile device and on most screen resolutions from version 5 upwards. It currently uses .Net 3.5 but I can port it back to 2.0 if required as all the code is legacy written and I am using no libraries from the newer framework. I’d appreciate any reasonable feedback.
Previews
======
Surely this should've been posted in the themes, apps and software section?
MOD EDIT
Moved to themes, apps and software forum
oops, sorry about that.
Thanks for your time. Two questions, #1: I've been around here and throughout other sites, and found (it seems) dozens of different options but none have seemed to work regarding getting an object to follow a CIRCULAR progress bar. In this case, I have a simple clock that I would like to have a sunrise icon and sunset icon (each) move around the outside the clock at the appropriate time. I have tried multiple codes and combos to no avail. I have successfully managed to achieve this result on a straight prog bar using [oy]$(-34+(#BLEVN#*2.70))$[/oy]. Those are, of course, my coordinates plugged in. I've found so many different "Oh, do this, this'll work" codes that don't work, I won't bore you with them (including this one http://forum.xda-developers.com/showthread.php?t=2563932). At any rate, any help would be appreciated.
#2: Is it possible to set up a 12 hour progress bar clock that handles just am and/or just pm?
Thanks again.
#1 Take a look at the Zooper standard analog Clock
#2 Use the 24h. For am use min 0 max 12 and for pm use min 12 max 24
Sent from GT-I9505 via Tapatalk
ibashmuck said:
Thanks for your time. Two questions, #1: I've been around here and throughout other sites, and found (it seems) dozens of different options but none have seemed to work regarding getting an object to follow a CIRCULAR progress bar. In this case, I have a simple clock that I would like to have a sunrise icon and sunset icon (each) move around the outside the clock at the appropriate time. I have tried multiple codes and combos to no avail. I have successfully managed to achieve this result on a straight prog bar using [oy]$(-34+(#BLEVN#*2.70))$[/oy]. Those are, of course, my coordinates plugged in. I've found so many different "Oh, do this, this'll work" codes that don't work, I won't bore you with them (including this one http://forum.xda-developers.com/showthread.php?t=2563932). At any rate, any help would be appreciated.
#2: Is it possible to set up a 12 hour progress bar clock that handles just am and/or just pm?
Thanks again.
Click to expand...
Click to collapse
#1: Moving things circular is a bit different from moving this along a straight line. For circles you need three parameters in Zooper: thie radius of your circle ([ar][/ar]), the sweep angle of said circle ([as][/as]) and finally the rotation ([r][/r]). The first one is static and the other two depend on what you are trying to do. You need to determine the size of your circle in degrees (360 for full, 180 for half etc.) and then determine in how many steps you need to cut that size. For something that moves with the minutes of the hour it would be 60 for instance. Then your amount of degrees per minute is 360/60 and if you multiply that with the numbers of minutes #Dm#, you get your current position and rotation. So for something to move around a circle based on the minutes of the hour you would need these advanced parameters:
[r]<whatever size>[/r]
[as]$(360/60*#Dm#)$[/as]
[ar]$(360/60*#Dm#)$[/ar]To apply this to your idea, you need to figure out in how many steps you want your circle to be broken down to (I would guess 12) and then what's your variable you want to multiply with (#ARK# maybe). With these values it should position the symbol on the hour of the sunrise.
I hope this helps you out and if not, don't hesitate to ask
#2: I think so but you probably would have to work with some advanced parameter conditionals to check whether it's currently am or pm. This depends on what exactly you are trying to do. If you can give me more details I can try to think something up.
kwerdenker said:
#1: Moving things circular is a bit different from moving this along a straight line. For circles you need three parameters in Zooper: thie radius of your circle ([ar][/ar]), the sweep angle of said circle ([as][/as]) and finally the rotation ([r][/r]). The first one is static and the other two depend on what you are trying to do. You need to determine the size of your circle in degrees (360 for full, 180 for half etc.) and then determine in how many steps you need to cut that size. For something that moves with the minutes of the hour it would be 60 for instance. Then your amount of degrees per minute is 360/60 and if you multiply that with the numbers of minutes #Dm#, you get your current position and rotation. So for something to move around a circle based on the minutes of the hour you would need these advanced parameters:
[r]<whatever size>[/r]
[as]$(360/60*#Dm#)$[/as]
[ar]$(360/60*#Dm#)$[/ar]To apply this to your idea, you need to figure out in how many steps you want your circle to be broken down to (I would guess 12) and then what's your variable you want to multiply with (#ARK# maybe). With these values it should position the symbol on the hour of the sunrise.
I hope this helps you out and if not, don't hesitate to ask
#2: I think so but you probably would have to work with some advanced parameter conditionals to check whether it's currently am or pm. This depends on what exactly you are trying to do. If you can give me more details I can try to think something up.
Click to expand...
Click to collapse
Thanks for the response. That's actually the first parameter that I found and tried to work with, and, like then, I still can't get it to work. My "hour clock" numbers are:
x= 60
y= -210
w= 520
Using #Dh#, min 0, max 12
Putting numbers into the codes you gave...
[as]$(360/12*#ARh#)$[/as]
[ar]$(360/12*#ARh#)$[/ar]
...(or even #ARK#) still sends the icon low and to the left, as you can see in the second screen shot (I've enlarged it to show it's position better). I'm living up to my namesake with this, I know, but my guess is I'm missing one small bit that's throwing me off. Apologies, of course.
Morning all.
I am trying to make a fancy battery bar widget using 4 progress bars each curved 90 degrees and rotated to make a full circle, and each individual bar only showing a 25% range of the battery level, so bar 1 is 0-24%, bar 2 is 25-49 % etc.
What I'm trying to do now is split the bars into sections depending on the battery level, so when the battery is below 75% but above 50, I want the 3rd section to split into 5 chunks but have the first two bars stay solid... if you get what I mean.
But I've searched and tried to find the Advanced Parameter for progress bar chunks/splits and I cannot find it. The text on the advanced parameter button in Zooper says "...control almost any aspect of this module...", and I'm not bashing, but is this one option not available or have I missed the appropriate keyword from my XDA/Google searches?
Thanks
Wrong thread
@Mokum020
Thanks for the tip I think that's the way to go.
I'll tell you what as well, trying to get the segments lined up with eachother is a PITA!
Mokum020 said:
How about making two progress bars for each section, one solid and one in chunks and show/hide them with the offset parameter at a certain % level:
Solid
Code:
[ox]$#BLEVN#>=75?1000$[/ox]
Chunks
Code:
[ox]$#BLEVN#<75?1000$[/ox]
Click to expand...
Click to collapse
Very Smart Solution!!!
P.S. I'm a robot
Ratchet_Guy said:
Very Smart Solution!!!
P.S. I'm a robot
Click to expand...
Click to collapse
I thought this was an interesting idea so I built my own version of it, attached. Would like to see the OP's as well if willing to share.
As the OP mentioned getting the segments to line up to the exact pixel/millimeter is easier said than done, but sometimes close enough looks...close enough lol.
Hi,
can somebody please tell me how to add the 3rd row of quick setting toggles in the Oreo update like it was with Nougat?
I've tried Oreo for the third time now but several things simply don't work anymore or got worse in comparison with Nougat.
I could live with a few of those but only having two rows of quick setting toggles is definatily not one of them.
I tried gravitybox (it's missing the option to manage the vibration strength of the virtual buttons and the battery tile now has additional text which takes up all the space so the temperature part isn't visible anymore.)
Furthermore I had to buy a substratum theme to not vomit from the white quick settings panel. With the march security update the installation is now as tedious as with Nougat due to the forced reboot.
The Xposed module HowGiveLolli doesn't work anymore and the centered normal letters instead of all upper case was a real nice feature.
Why are the points in the settings app regrouped so it's harder to find specific settings?
There are simply so many bad design choices in my eyes I can't bring myself to live with Oreo due to not finding substitute functions for the missing ones.
Kind regards
I know you posted this last month so you hopefully figured it out, but either way I thought I'd share the answer since someone else might want to know in the future.
It has to do with the display scaling in Settings\Display\Advanced\Display Size. If set to default or large, you only get two rows of quick settings. If you set to small, the UI shrinks and as a side effect you get three rows of quick settings tiles. You can always increase the font size afterward if it's too small, but reducing the display scaling is the only way to have enough room to display three rows.
ABQNM said:
I know you posted this last month so you hopefully figured it out, but either way I thought I'd share the answer since someone else might want to know in the future.
It has to do with the display scaling in Settings\Display\Advanced\Display Size. If set to default or large, you only get two rows of quick settings. If you set to small, the UI shrinks and as a side effect you get three rows of quick settings tiles. You can always increase the font size afterward if it's too small, but reducing the display scaling is the only way to have enough room to display three rows.
Click to expand...
Click to collapse
Thanks for posting the solution. I simply restored my Nougat backup as I never upgraded my bootloader for that matter. I don't think I'll be using Oreo until I get a new phone which possibly can't be a Moto Z3 because I'm not really convinced they will release anything more than the Z3 play.
ABQNM said:
I know you posted this last month so you hopefully figured it out, but either way I thought I'd share the answer since someone else might want to know in the future.
It has to do with the display scaling in Settings\Display\Advanced\Display Size. If set to default or large, you only get two rows of quick settings. If you set to small, the UI shrinks and as a side effect you get three rows of quick settings tiles. You can always increase the font size afterward if it's too small, but reducing the display scaling is the only way to have enough room to display three rows.
Click to expand...
Click to collapse
Hi and thanks for this trick : as a matter of fact I was always on "small" in Nougat and it worked nice with 3 rows, but with Oreo I needed to switch to "smaller" to switch from 2 to 3 rows :silly: