Develop Bugs

Update! nueDynamicClock v1.3 - Tool to change Clockspeed of your Blackstone

A friend founds this at pocketnow.com.
nueDynamicClock allows you to change the clock speed of your Touch Pro, Touch Diamond or Touch HD based on certain parameters.
Update: nueDynamicClock v1.3 has been released
Changes: Display issue fixed, fixed slow clock change, stability fixes, ensure all threads running in Kernel mode, set profile on save, WM6.5 hi-res icon
Here is the link:
http://www.nuerom.com/BlogEngine/page/nueDynamicClock.aspx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Does this work??

how safe i to use that

Awesome. Need to be careful though.

Anyone tested?? we may have something big here!!! (if its working..!!)
Max values..?? Performance improvements?? Some benchmarks?
Because after some research i did , i saw that our processor is capable even for speeds almost double its original value!! (some say 850 and report fast and stable!!)
Lets see!!

What the hell?
800MHZ on the HD?
thats crazy!

Yeah it works
you need to install the cab and soft reset
after in All settings > System
a new icon appear : processor
set it there .
you can't overclock speed actually with this tool
but, you can slow down a lot the cpu to save a lot's of battery during idle process.

Does anyone know what these value are by default? We could actually make battery life worse if we set higher values for backlight off, etc than the factory settings...

It is not working. I try it again and again.
Set all values to 256.00 and it loose this settings after exit or if the device go to sleep.
Under "Current processor speed:" it shows 256.00 and if I go again to this setting it shows the "normal" 528mhz.

geistteufel said:
Yeah it works
you need to install the cab and soft reset
after in All settings > System
a new icon appear : processor
set it there .
you can't overclock speed actually with this tool
but, you can slow down a lot the cpu to save a lot's of battery during idle process.
Click to expand...
Click to collapse
Don't tell me the Touch HD actually doesn't manage it's CPU speed on its own!?!? Even my old Axim x51v did that!!!

there is another thread
http://forum.xda-developers.com/showthread.php?t=507212

I ' have try this :
Default :528mhz
After 5s 256mhz (this doesn't work I think, but not sure)
When backlight off : 82mhz
When suspend : 19mhz
So after all night of sleeping, my battery haven't lose any bare.
I will test it more, I think they greatly improve battery life.
so just keep testing.

MAMeingast said:
Don't tell me the Touch HD actually doesn't manage it's CPU speed on its own!?!? Even my old Axim x51v did that!!!
Click to expand...
Click to collapse
Qualcomm is not Intel-Marvel !

I tested the tool from April 21th to April 25th. 5 days without recharge!
Otherwise i was charging my Blackstone every two days and i've running ICQ in backround around the clock. So i'm online once i turn on my telephone. It works perfect for me!
Setup:
idle after 5000ms: 384 MHz
on backlight of: 122.88 MHz
on suspend: 122.88 MHz
Sorry for my bad english

hi, first of all, thank yu for sharing.
second: Ihave put the exe file on my HD and run it from my phone but it keeps saying:
"your phone is preventing installation, we can try to automatically fix this, but we need to restart your device. continue?"
and when I cic yes, it restarts and nothing happens. so I run the programm again, and get the same message.
anyone have any idea wha the problem might be?
thank you in advance

Installed v1.2 and changed profile to "Power saving", but the cpu clock is still at 528MHz?

For me resulted in more battery drain (version 1. BTW 1.2 doesn't work)
See here: http://forum.xda-developers.com/showpost.php?p=3692764&postcount=77

@jouh:
Click on "File" -> "Reset Active Profile". The value of "Active Profile" should change from "Default" to yours and you can see the de-/increasing CPU speed now.

kostasalfa said:
Anyone tested?? we may have something big here!!! (if its working..!!)
Max values..?? Performance improvements?? Some benchmarks?
Because after some research i did , i saw that our processor is capable even for speeds almost double its original value!! (some say 850 and report fast and stable!!)
Lets see!!
Click to expand...
Click to collapse
Can you tell us, where did you read about this overclocking to 850 MHz. I would like to learn more about it. Like others say, this program cannot overclock but only underclock.Please give us some links. Thanks

Version 1.2 results excessive battery drain to me too (8-12% per hour, in suspend mode).
Back to version 1...

[APP] RogueTools v1.1 - [Overclock & Change Screen Density] - [Updated: 04/27/2010]

[APP] RogueTools v1.1 - [Overclock & Change Screen Density] - [Updated: 04/27/2010]
I now present you with RogueTools v1.1.
Summary:
This application is designed for the Vogue, Kaiser, Polaris and Nike devices. It allows you to dynamically overclock your device as well as change the screen density.
Requirements:
This application requires write access to your /system so this will only work on EXT2 and NAND installations.
Overclocking Notes:
Overclocking results will vary. Based upon the beta test results everyone was able to Overclock to 500mhz and have very stable results. Above this results really were mixed. Give it a try, I'd love to hear your results.
To download, search in the market for "RogueTools"
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before (400mhz) and After (500mhz) CaffeineMark Benchmark
HUGE thanks to all of the beta testers. You guys did an outstanding job!:
citrit, cp0020, damianiw, DmK75, dzo, GriloVirante, Incubus26jc, inertone, jnadke, mblaster, Millence, mssmison, paipo, pyrator, scouzer, vrflyer
Disclaimer:
As always, I’m not responsible for anything that happens to your phone while using these files.
Future Versions:
I'm looking for some creative ideas on other additions you'd like to see added to this application. So if you have some thoughts, please let me know.
Changelog:
04/27/2010
Added device support for Nike
04/24/2010
Version 1

Awesome. Can't wait to try.

Will this affect the battery life?
Right now the battery is bad enough with android, but it does sound really nice.

Nice,
will try it out

Overclocking will always effect battery life negatively. Under-clocking will increase it.
You don't always need your Kaiser running at 400 Mhz, but I think Android throttles it anyway.

Dukenukemx said:
Overclocking will always effect battery life negatively. Under-clocking will increase it.
You don't always need your Kaiser running at 400 Mhz, but I think Android throttles it anyway.
Click to expand...
Click to collapse
When sleeping it underclocks to ~200Mhz (it seems that "cat /proc/cpuinfo|grep BogoMIPS" displays something around the clock value).

nice work bro...works great on my tilt

could you upload the update.tar ?

Tukang PDA said:
could you upload the update.tar ?
Click to expand...
Click to collapse
Can't You read?
To download, search in the market for "RogueTools"!!!!

Awesome.
Kaiser
Benchmark
400MHz : 91 points
475MHz : 130 points
500MHz : 140 points

Nice!
Appears to work on my tilt!
Nice Job!

liveskelet said:
Awesome.
Kaiser
Benchmark
400MHz : 91 points
475MHz : 130 points
500MHz : 140 points
Click to expand...
Click to collapse
600Mhz : Called fire brigade....

zenity said:
600Mhz : Called fire brigade....
Click to expand...
Click to collapse
Are you serious?
I may have to raise the max threshold for you Kaiser users. 700???

Holy crap this works awesome. Tried it on Polymod 2.1d and it kinda blew my mind. I've only overclocked to 450mhz so far, but it's a night and day difference. Thanks a ton myn, great work.

tonyc0642 said:
Holy crap this works awesome. Tried it on Polymod 2.1d and it kinda blew my mind. I've only overclocked to 450mhz so far, but it's a night and day difference. Thanks a ton myn, great work.
Click to expand...
Click to collapse
I've set mine to 500 Mhz, any chanche for overheating (when going higher then 500)?
(I've deleted some .apk packages (voice dialer,...) and together with this tweak it runs really great, almost 40MB free ram whe killing all apps)

Great app. Can someone give a bit more info about the "increase screen dpi" option? When and why would I want to use this feature? What is a "good" value?

robuser007 said:
I've set mine to 500 Mhz, any chanche for overheating (when going higher then 500)?
(I've deleted some .apk packages (voice dialer,...) and together with this tweak it runs really great, almost 40MB free ram whe killing all apps)
Click to expand...
Click to collapse
I can't say for sure since I'm not the one that developed this, but it seems to me that it should actually save your battery since it underclocks when the phone is sleeping, unless of course you're actively using it a lot while at 500mhz or more, in which case you'd use your battery quicker and run the risk of overheating. Like I said, I can't be certain, so you may want to wait for a reply from myn himself on it.
jt131 said:
Great app. Can someone give a bit more info about the "increase screen dpi" option? When and why would I want to use this feature? What is a "good" value?
Click to expand...
Click to collapse
It should be set at 120dpi by default, at least it was for me. The dpi is "dots per inch," which is pretty much what it sounds like. If you make the value higher, it will make things larger. If you make it smaller, well you get the idea. I played around with it some to check it out, but I'm happy with the default dpi.

Thanks tony. I guess it could be useful for applications that do not work correctly in Kaiser's QVGA, like iGO for example. Would a lower dpi setting compensate for iGO's larger resolution design?

Reducing the DPI makes everything small so iGO might work but it will make reading everything harder.
jt131 said:
Thanks tony. I guess it could be useful for applications that do not work correctly in Kaiser's QVGA, like iGO for example. Would a lower dpi setting compensate for iGO's larger resolution design?
Click to expand...
Click to collapse

Who needs to read, so long as you can see the map and hear the voice commands?

[Q] Why is the newest Netarchy Kernel making my Stock Root Rom's FPS WORSE?!

Can anyone help me out?
I'm running stock rooted 2.2 (deodexed) and flahsed over the 4.0 zip... and the scrolling is choppier than all hell. I re flashed the stock kernel, and it was back to being fine again. So, I tried again, with wiping the caches first, and still choppier than all get out when I flashed the kernel.
It's definitely the right kernel, but what the hell am I doing wrong here? Any help would be appreciated.

And, I'll even throw in 5-10 dollrs for someone who can give me an answer that works.

This could be because of the new settings he just changed. Try the download that is 4.0.2 and not 4.0.3, or try overclocking your processor to 1.2GHZ with OC widget or SetCPU.

What kind of screen do you have? If you have a Nova panel, you may need to adjust T2 values to get the best performance. Just my 2 cents.

Ok, so I installed 4.0.2, and it seems to be running better, but still some choppiness on the menu up and down scrolling when "all apps" is opened.
I have no idea how to use SetCPU (noob yep... graphics guy... not a tech guy_, so I took a screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wpould you mind just telling me where the sliders should be?

nukedukem said:
What kind of screen do you have? If you have a Nova panel, you may need to adjust T2 values to get the best performance. Just my 2 cents.
Click to expand...
Click to collapse
I have a Nova, but, I have no idea what T2 panels are and how to adjust them. If you could point me to the right app or direction, that'd be awesome. I'll donate to you as well if it helps.

There's an app floating around here called NovaFreq formerly evoswitch. It allows you to change the panel frequency to improve fps. Everyone gets different results. 450ish was usually the best for me. Basically trial and error. Most haven't needed it with recent kernels though. As for setcpu, the higher the max frequency the better fps performance, but overclocking comes with some risks. Im usually underclocked at 576max / 245min. You can also set profiles to run certain speeds when screen off, charging, etc. Helps a lot with battery life. I would move your max down to 998 or 1113 and min to 245. Ondemand is usually a good scaling setting. Hope this helps.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
There's an app floating around here called NovaFreq formerly evoswitch. It allows you to change the panel frequency to improve fps. Everyone gets different results. 450ish was usually the best for me. Basically trial and error. Most haven't needed it with recent kernels though. As for setcpu, the higher the max frequency the better fps performance, but overclocking comes with some risks. Im usually underclocked at 576max / 245min. You can also set profiles to run certain speeds when screen off, charging, etc. Helps a lot with battery life. I would move your max down to 998 or 1113 and min to 245. Ondemand is usually a good scaling setting. Hope this helps.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
Wow thanks. I downloaded nova frequency, but just left it at default, and changed the setcpu, bc I was getting random reboots with the overclock. I also set profiles to way lower when the screen is off and the phone is at lower battery percents.
This phone officially runs like it's on crack now. Good stuff.
Guys, PM me ur paypals, and I dont' mind donating a few bucks tomorrow.

Glad to help. Feel free to send my donation to one of the developers on this forum. Without them I wouldn't have known any of that.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
Glad to help. Feel free to send my donation to one of the developers on this forum. Without them I wouldn't have known any of that.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
Good ****
Sent from my PC36100 using XDA App

TJDuckett said:
Wow thanks. I downloaded nova frequency, but just left it at default, and changed the setcpu, bc I was getting random reboots with the overclock. I also set profiles to way lower when the screen is off and the phone is at lower battery percents.
This phone officially runs like it's on crack now. Good stuff.
Guys, PM me ur paypals, and I dont' mind donating a few bucks tomorrow.
Click to expand...
Click to collapse
LOL bro. Not only did I tell you to use NovaFreq, but I also told you not to use SetCPU. You were getting reboots b/c it was set too high and you don't want to set it below 245 when screen is off. I don't think SetCPU is so great for *most* people. I could have helped you on GTalk and taken your money...gladly would have

[APP] Simple Barometer for Galaxy Nexus

Hi all,
I just wanted to present you a very simple application,
that shows the barometric pressure in the environment.
It simply reads out the sensor value and also calculates
the approximate altitude based on standart atmospheric
pressure at sea level of 1013.25 hPa and at a standart
temperature of 288.15 K.
Why I made this application, if it was so simple?
There was no such application, that shows the barometric
pressure in a nice way, so there we go:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions for improvement are welcome =)

Very cool, thanks. Only suggestion would maybe to have a graph so we can keep an eye on the trend.
Sent from my Galaxy Nexus using xda premium

Looks nice in the screenshot but the gauge doesn't display for me. Just the numbers.
Sent from my Galaxy Nexus using xda premium

cmac86 said:
Looks nice in the screenshot but the gauge doesn't display for me. Just the numbers.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same here - Image is not displaying...

Works great for me, very nice app thx!

Works great. My only suggestion is, can you down a little the scale of the barometer?. I mean I'm in Bogota, Colombia (2600 m over the sea level) so my barometer is always down before 960 hPa

I like the screenshot but as already said I only get the numbers on bigxies build 4.0.3 and Franco's 12
Sent from my Galaxy Nexus using xda premium

Awesome app lol
Sent from my Galaxy Nexus using XDA App

allen2oo3 said:
Very cool, thanks. Only suggestion would maybe to have a graph so we can keep an eye on the trend.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
+1
10 chars

Working fine on mine.
---------- Post added at 02:49 PM ---------- Previous post was at 02:41 PM ----------
Working fine on mine.

gpu
folks finding it dont work try switching forced gpu rendering off and then restart the app
seems to be a common fault of bar preasure apps - i tried this out on the app i use on my xoom and that too requres gpu rendering to be switched off.
just a thought
.
.
.

terminal 7 said:
folks finding it dont work try switching forced gpu rendering off and then restart the app
seems to be a common fault of bar preasure apps - i tried this out on the app i use on my xoom and that too requres gpu rendering to be switched off.
just a thought
.
.
.
Click to expand...
Click to collapse
That fixes it for me.

Yeh. My rendering is that way by default.

Thank you for this App.
I also have one suggestion. Could you add a relative height? I mean that it is possible to set the current height as a reference and make the difference visible. Then it would be possible to meassure the approximately height in a big building or an elevator.
I've already done this in my own app and it works great. Unfortunately I couldn't find time to improve my app, it's very simple and not so nice as yours .

SophîaPêtríllo said:
Thank you for this App.
I also have one suggestion. Could you add a relative height? I mean that it is possible to set the current height as a reference and make the difference visible. Then it would be possible to meassure the approximately height in a big building or an elevator.
I've already done this in my own app and it works great. Unfortunately I couldn't find time to improve my app, it's very simple and not so nice as yours .
Click to expand...
Click to collapse
I doubt the barometer is precise enough to measure the height of a buiding

Thanks, good app.
Improvment : possibility to compute the QNH (sea level pressure) by adding known altitude (inserting altitude in meters, feet or hPa).

Change the graphic to show stormy/fair weather icons for people like me who don't know what a barometer does or how to read one, relatively. Make it fun!

Great app. I love simple apps!

drtrmiller said:
Change the graphic to show stormy/fair weather icons for people like me who don't know what a barometer does or how to read one, relatively. Make it fun!
Click to expand...
Click to collapse
Barometric pressure alone does not reliably predict the weather.

SophîaPêtríllo said:
Thank you for this App.
I also have one suggestion. Could you add a relative height? I mean that it is possible to set the current height as a reference and make the difference visible. Then it would be possible to meassure the approximately height in a big building or an elevator.
I've already done this in my own app and it works great. Unfortunately I couldn't find time to improve my app, it's very simple and not so nice as yours .
Click to expand...
Click to collapse
Could you provide me the formula to calculate the relative height? Would make it much easier for me ^^
Works great. My only suggestion is, can you down a little the scale of the barometer?. I mean I'm in Bogota, Colombia (2600 m over the sea level) so my barometer is always down before 960 hPa
Click to expand...
Click to collapse
Will add this feature aswell.
Change the graphic to show stormy/fair weather icons for people like me who don't know what a barometer does or how to read one, relatively. Make it fun!
Click to expand...
Click to collapse
Will add it, but that won't be accurate for people, who are not living in west european latitudinal lines.
EDIT: There you go =)

[APP] SU Root Tools

***THIS APP NEEDS A ROOT PHONE***
This app includes root tools that you can use with a simple click. Its currently under development, this means that it will get new things added.
***INCLUDES***
Reboot
Reboot in Recovery Mode
Reboot in Bootloader Mode
Quick Reboot
Power off your device
Wipe cache and dalivk-cache
Wipe dalvik-cache
Wipe battery stats
wipe cache
Free up RAM
backup bootanimation
install bootanimation
Save a LogCat
Save App specific LogCat
Turn On/Off CPU2
Kernel mods:
1. Overclock
2. Select Governor
3. Governor Settings for:
---EVERY GOVERNOR (PLEASE REPORT IF IT DOESN'T WORK)
***ONLYE FOR GALAXY NEXUS AND GALAXY SIII***
CPU temperature notification.
I will add more and more features.
Download now from PLAY STORE!!!

Looks good thanks. Will helping testing as much as possible.
Sent from my Galaxy Nexus using Tapatalk 2

Really nice stuff! If I were you, I'll add extra features that no other competitors have
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

very good work, compliments!!

Version 1.5
Changed orientation to portrait. Added a bootanimation preview button. Easier file chooser for bootanimation. Completely different look for kernel mods. App more user friendly. Fixed some minor bugs. Removed some unused toast messages.
Need some test for bootanimaton preview. Please report back

Updated to latest, Version 1.6, with many fixes

unforgivenmercy said:
Looks good thanks. Will helping testing as much as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Could you try the cpu temp notification, just turn it on and off like 10 times and tell me if you get any FC or if its not showing.
Thanks

Version 1.7
A lot of bug fix. Fixed governor settings not applying, added a check box to set governor at boot, fixed clear cache for ROMs that doesn't support it, fixed crash for CPU temp notification, fixed loop when device can't reboot, clear cache, etc. Added GSF id and System id info, (Will just show it to you).
Click to expand...
Click to collapse
If anyone get any other FC when enabling CPU temperature read, please report it again, since it should be fixed. Thanks.

New version with Rom management. Only available for CWM Recovery!!

I think you have a minor typo in OP 'turn off CPU 2' should be 'turn off CPU 1' as cores are CPU 0, CPU 1 (duel core) then CPU 2 and CPU 3 (for quad core device)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus

The Gingerbread Man said:
I think you have a minor typo in OP 'turn off CPU 2' should be 'turn off CPU 1' as cores are CPU 0, CPU 1 (duel core) then CPU 2 and CPU 3 (for quad core device)
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes I know that, but for not developers people seeing a number 1 is like the first CPU will be off. Since you normally start counting with the number 1. I did name it number 1 in one of the tests and I received a lot of e-mails asking me if its safe to turn off the first CPU and why I'm not doing it with the second CPU. So I decided to change the number so that way people wont get confused.
So basically you are right, but I did it on purpose.

Rotary Heart said:
Yes I know that, but for not developers people seeing a number 1 is like the first CPU will be off. Since you normally start counting with the number 1. I did name it number 1 in one of the tests and I received a lot of e-mails asking me if its safe to turn off the first CPU and why I'm not doing it with the second CPU. So I decided to change the number so that way people wont get confused.
So basically you are right, but I did it on purpose.
Click to expand...
Click to collapse
I see and no worries I was just checking, I don't intend on using this but just wanted to make sure you knew the correct labeling for the cores
Sent from my Galaxy Nexus

The Gingerbread Man said:
I see and no worries I was just checking, I don't intend on using this but just wanted to make sure you knew the correct labeling for the cores
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks anyway