Database Develop

Faster BA

It was very annoying to wait opening programs or files, even device was empty, before pocket hack master . You can test speeds than choose . It is very fast and you can change the speed whenever you want . If you dont happy with your BA's speed try it .

I downloaded a trial of it, and can't say i noticed any real difference- what settings do you use? Thanks for any help
Fin

Findus try these : cpu : 531, ram : 133 ,pxbus : 265 , sı : 234 with turbo 1.0x sdram this is the last configration at the speed configuration

Will do!
Cheers,
Fin

It is a very nice tool, been using it for a while now.
Not only can it speed up aplications that need extra power like games or video capturing (increases captured FPS by quite a lot), but it can also downclock your device when the power is not needed to save power.
I've been able to overclock my CPU well over 800Mhz with this tool, yet with lower memory and 'FSB' speed.
But be carefull when trying to push your device to the limit. If you push it too far it can crash and result in a hard reset. The standard listed settings are probably all save, but the real speed is in the manual added configurations.
I found that L:40, M:4, N:1 to be the fastest config. Anything over L:40 will be unstable. This results in 589Mhz CPU speed, 294Mhz PXBus and 147Mhz memory speed. (Default 400, 200 and 100)
I use 3 speed steps.
L:40, M:1, N1 (147mhz CPU) when CPU load is under 15%)
L:40, M:2, N1 (294Mhz CPU) when CPU load is over 15%) (Almost as fast as the default 400Mhz settings because of higher PXBus and memory speed)
L:40, M:4, N1 (589Mhz CPU) when CPU load is over 95%)
AVGN time set to 2sec so it reacts to CPU usage chance nice and fast. If you set it to 1sec it'll switch speed config too often since there are often short peaks over 15%
(all woth turbo enabled altough that doesn't change performance since 'N' is set to 1)
I noticed that if you start increasing the "N" factor the SI (system (performance) index) decreases.
For instance:
L:40, M:4, N1 (589Mhz CPU) = SI 446 on my device
L:40, M:4, N1.5 (885Mhz CPU) = SI 329 on my device
of course i'm not sure how that SI represents real life performance.
The default BA speed gives me a SI of 298.
This tool works better then XCPUscalar because it allows higher overclocks and also reacts to 'CPU usage change' better. Often XCPUscalar would leave the CPU underclocked while it really should have increased the speed.

RELOAD said:
Findus try these : cpu : 531, ram : 133 ,pxbus : 265 , sı : 234 with turbo 1.0x sdram this is the last configration at the speed configuration
Click to expand...
Click to collapse
uhm, on default speeds i get a SI of 298, have you compared default speed SI to the overclocked speed SI?
{
"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"
}
Not sure why this is in 'Blue Angel upgrading etc.'

No not yet , i was trying to find best configration for fastest and stabil device and these settings fine for me .
Because of this topic in Blueangel Upgrade : Tool is upgrading the speed

RELOAD said:
Because of this topic in Blueangel Upgrade : Tool is upgrading the speed
Click to expand...
Click to collapse
Whaha nice!
Oke those settings ore probably nice and stable, but like i said, are they faster then default, that would be nice to know.
BetaPlayer can also do a benchmark test. I'll compare the next to seetings:
L:40, M:4, N1 (589Mhz CPU) = SI 446 on my device
L:40, M:4, N1.5 (885Mhz CPU) = SI 329 on my device
and see if the 589Mhz settings is still faster then the 885Mhz setting to see if that SI can be trusted.
hhmm, when at 589Mhz BetaPlayer sees my system as 592Mhz, yet at 885Mhz BetaPlayer sees it as 564Mhz and the benchmark result is also slower. So i guess the SI is a good indication.
Looks like that 'N' multiplier doesn't work on the BA.
I compared L:40, M:4, N1 (589Mhz CPU) with L:40, M:2, N2 (589Mhz CPU)
Only difference is the PXBus is half the speed with the second setting.
L:40, M:4, N1 (589Mhz CPU) = SI: 446
L:40, M:2, N2 (589Mhz CPU) = SI: 361
Yet at both settings BetaPlayer sees it as 592Mhz, so the 'N=2' multiplier does work.

overclocking our Diamonds (MSM72XXX) to 768 MHz!!!!!!!!

overclocking our Diamonds (MSM72XXX) to 768 MHz
Read this:
"Touch Pro running at 800MHZ???
I swear it’s working, really, see screen shot attached… Short story – I knew that the number of clocks on MSM devices are limited (Actually, that’s a pretty relative term – the MSM has a LOT of clocks for a single chip), the main problem is that there isn’t that much resolution with the clocks, and that there aren’t that many high clocks to choose from – in fact if you look at the clocks available on MSM devices, we have:
TCXO: 19.2 MHz (for CDMA clock)
GlobalPLL: 800MHz
BackPLL0: ? MHz
BackPLL1: 1.056GHz
PLLTest: ? MHz
USB: 48MHz
Sleep: ? MHz
So the standard frequencies for the MSM are obtained by BackPLL1 / 2= 528MHz or GlobalPLL / 2 = 400 (384) MHz.
But just a few minutes ago, a lightbulb lit up in my head, why not just TRY setting GlobalPLL / 1 for the applications ARM? … And to my surprise, the device didn’t freeze.. it worked just fine actually. And there is a noticeable improvement in speed ( ~ 330 integer @ 528 MHz , ~456 integer @ 768 MHz).
{
"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"
}
I guess this’ll be finalized into a tool for some sort. Guess overclocking this thing was possible =p.
Note: Before I get a bunch of stuff about 1.056 GHz, no, it didn’t work on my Touch Pro, it locked up!"
see the comparison
Integrer:
Toshiba TG01: 744.4334 @ 1000MHz
HTC Touch Pro: 456.41 @ 768 MHz
Samsung Omnia: 304.6265 @ 624 MHz
source: http://www.nuerom.com/BlogEngine/post/2009/09/06/Touch-Pro-running-at-800MHZ.aspx

has anyone tried this on their Diamond yet? How badly does it effect battery consumption??

a beta version of the tool is out, I can't test it since my diamond is in service.
Judging by the comments on the original page, it works for some users, although not 100% reliable yet.
http://www.nuerom.com/BlogEngine/post/2009/09/07/nueOverClockTest.aspx

i can´t overclock my diamond - i can set max 528 MHz, of course i can go on lower values....

Just tested on my Diamond and it just restarted. Mine can't handle clock speed of 768mhz.

overclocking is probably due to the use of co-processor that has the function of modem. So, that overclocking is only possible with phone off.
MSM7201a (ARM11) + "ARM9 coprocessor, Embedded QDSP4000 and QDSP5000 DSP (GSM, GPRS/EGPRS Multislot Class 12, EDGE, UMTS/WCDMA, HSDPA, HSUPA, MBMS baseband), Embedded gpsOne GPS module, Qcamera, Qtv, Qcamcorder, Qvideophone"
source http://pdadb.net/index.php?m=cpu&id=a7201a&c=qualcomm_msm7201a
In FPSECE forum , we can see that some users have achieved good results. if you are testing, do not forget to turn off the phone process

marcolero said:
overclocking is probably due to the use of co-processor that has the function of modem. So, that overclocking is only possible with phone off.
MSM7201a (ARM11) + "ARM9 coprocessor, Embedded QDSP4000 and QDSP5000 DSP (GSM, GPRS/EGPRS Multislot Class 12, EDGE, UMTS/WCDMA, HSDPA, HSUPA, MBMS baseband), Embedded gpsOne GPS module, Qcamera, Qtv, Qcamcorder, Qvideophone"
source http://pdadb.net/index.php?m=cpu&id=a7201a&c=qualcomm_msm7201a
In FPSECE forum , we can see that some users have achieved good results. if you are testing, do not forget to turn off the phone process
Click to expand...
Click to collapse
killed the phone process and this time it jost froze. no restart.
i was wondering though if someone could edit the program so it overclocks to say 628mhz??

Overclock working just wonderfully over here Nice speed up.
2 Days on battery now...

Very interesting, but is it safe do this?And is it possible downgrade back to riginal.

dreamdx said:
Overclock working just wonderfully over here Nice speed up.
2 Days on battery now...
Click to expand...
Click to collapse
@ what ROM are you?
Cause any ROM i try, just reboots the device and nothing changed..
very interesting !

hy...how did u do that "why not just TRY setting GlobalPLL / 1 for the applications ARM? "

I did not hope that this overclocking will work- and was proved wrong.
HTC Touch Diamond, happily running at 768 MHz. Opera significantly snappier, iGo8 also faster. The device does not seem to be any warmer.
I would love to know if this overclocking increases the top speed at which the processor will run or shifts up all its frequencies i.e. idle and low load ones?

Not working all on Diamond with ROM KIMERA_v4.4_REVOLUTION_WWE after many attempts, including after deactivating all communication.
It always freeze immediately.

[FIX] Music Playback Crackling/Clicking Issue

First of all, id like to thank Gokhanmoral and Simone for the support... Special mention to TotallydubbedHD and Studiominal for the great contribution and to all who tested and helped...
The idea was first toasted by Gokhanmoral via PM, that it has something to do with idle status and not with hot-plug issue. Then Simone201 also posted about this on "official sound quality thread" which leads me to test dif configurations and combos... Then i came up with this little Fix:
1. You have to be rooted of course...
2. Flash Siyah Kernel (Sorry for this, since i only tested it with Siyah 1.3.3b and 1.3.7b)
3. Download & Install exTweak by Darek.Xan from the Playstore (Free one will do)
4. Grant Superuser
5. Navigate through the CPU Tab and set the CPU idle mode to; IDLE ONLY
6. Reboot
It was first tested with Siyah kernel 1.3.3b and was confirmed by Studiominal thru his "sinewave" that there were no crackling found in the graph. It has also been confirmed that it also work with 1.3.7b... I cant comment on other kernel since the test was thoroughly done with Siyah...
Hope this help... ENJOY!!!
For more info and progress about this finding, please read thru the thread
http://forum.xda-developers.com/showthread.php?t=1633685&page=75

{
"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"
}
Evidence provided
It seems like something in IDLE + LPA, AFTR + LPA, AFTR only causes the audio codec to suffer from power shortage that leads to turning the codec on and off really fast.
And.. to clarify, I only changed the cpu idle mode to IDLE ONLY, and disabled all the audio options that come pre-enabled both to see whether the idle mode is the culprit and wait for the new Voodoo Sound.

Thanks for the graph Pal...

Thanks guys for sticking with this and finding the problem.

Now that the culprit has become more obvious(likely the DAC being not able to perform properly with that low current set by stock setting), we'll see more developers here digging down the kernel with power profiles

Changed the setting to see what the impact on battery life is, i am not sure what lpe and aftr does, so not sure what effect we will see. Probably someone with more insight could clear this up...
–—–—–—–—–—–—–—–—
tapatalked from Galaxy SIII

So far, its been good with mine... Good deepsleep... When playing music, stayed on 200Mhz according to CPUspy..

jaytana said:
Then i came up with this little Fix:
Click to expand...
Click to collapse
Russians found this fix in June)
http://translate.google.ru/translat...howtopic=343482&st=2140#entry13910007&act=url

Hope its been posted here earlier to save our time and effort testing every bit of it...

jaytana said:
Hope its been posted here earlier to save our time and effort testing every bit of it...
Click to expand...
Click to collapse
but this is not the solution, it is a crutch

more of a temporary fix...

Iv never come across this problem but I use player pro and have never tried using the stock player, also, I use it with the lock screen player on which keeps a partial wake lock, perhaps this is what stops me having the problem.
I know the phone is awake because my nfc works when screen is off and player is playing.
Sent from my GT-I9300 using Tapatalk 2

Does this only effect Siyah Kernel?
Cause if its across the board on all current kernel sources what would be the solution to any any other kernel besides Siyah and using exTweak? A Script?
Also, I get choppy audio on almost all games and the same clicks on other audio related apps, could this be the same issue? This behavior almost sounds like latency problems of a low default audio pre-buffer...

JF-GINO said:
Also, I get choppy audio on almost all games and the same clicks on other audio related apps, could this be the same issue? This behavior almost sounds like latency problems of a low default audio pre-buffer...
Click to expand...
Click to collapse
So do I! It comes and goes but it's frustrating
Sent from my GT-I9300 using xda app-developers app

Are u two overclocking your CPU probably? Please give more details on your system, noone can help u this way.
–—–—–—–—–—–—–—–—
tapatalked from Galaxy SIII

According to Andreilux
LPA causes the CPU to be clock-gated, meaning the clock to the CPU is cut-off. I imagine that when power resumes, or actually is cut, it either causes a drop or spike in the power supply which interferes with the DAC and amplifier. This is inherently a hardware problem; they could have prevented it if they had put adequate filters on the PMIC, or whatever is in-between them which causes the interference. LPA is idiotically power-efficient and turning it off can cause worse idle battery life, so turning it off it in my opinion not a very viable option. The only options to fix it are already available to everybody already through changing of the idle states. If there's something to be done on the DAC-level itself, I don't know. CPU noise is a pain in the ass and wide-spread (Think about on-board sound on computers) and sadly there's not much to do about it if it's badly designed.
Click to expand...
Click to collapse

thanks for this, finally i've found the solution

Hi, this FIX is featured on the Index of FIXES http://forum.xda-developers.com/showthread.php?t=1674286
Any observation please send me a PM

Thanks...

I have been using, CM9 20120708-NIGHTLY with Ninphetamin3-1.1.1-test + Awesome Beats v3 (just beats boost active). No Crackling/Clicking Issue while listening to music with Apollo player.
I dont OC nor UV.

All cores are at 100% every few minutes

Anyone knows how to see which app is using the most CPU time? I want to throw my new redmi note 9 at the wall already. Hardly any apps installed and every few minutes it freezes and becomes unresponsive.
I got one app and it showed this during freezes
{
"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"
}

Did you install a new app before that started?

No, Even during initial setup it was like this

Do you have root right now ?
Basically the miui doesn't kill the app when you close/ leave it.Download something like avast cleaner in the Playstore and close/force the apps listed.Hate to say it but don't expect wonderful things from this phone.Mtk cpu and the biggest problem the miui interface atm.

Dokrak99 said:
Do you have root right now ?
Basically the miui doesn't kill the app when you close/ leave it.Download something like avast cleaner in the Playstore and close/force the apps listed.Hate to say it but don't expect wonderful things from this phone.Mtk cpu and the biggest problem the miui interface atm.
Click to expand...
Click to collapse
Can I leave it unrooted?
I checked battery stats and it says 75% is taken by screen time. Is there any app that works without rooting and can show the tasks occupying CPU time?

Mmm let me see what ROM are you on global,EU, and what version.
This phone especially some roms are famous for a heavy load off bloatware,ads,tracking, collection off data.mix that with a very in my opinion really bad miui software.
Because you're screen takes the most battery drain most likely we could rule out a third party app.leaves us with system apps.
I had the same as you're phone out off the box freezes.
I debloat my phone installed a alternative launcher with addquard.its not a rocket but it's most off the time ok only use it as back up.
Basically I can't think off a very easy way to get detailed information right now.Even you have root system dump log .even then you have a load off info.system tracing is available but takes time to learn and understand.

I'm on global rom, 12.0.6.
I thought chrome was the problem and disabled it but I still have these 100% cpu spikes every few minutes.

Global ROM is not the cleanest ROM out there.i am not at home right now so I can't check on my other phone if we can get some information out of a non rooted phone.
I would like to point out this page.
Saki EU tool Szaki used it on global 12.03
You don't need root just read the page and run.chrome is no light weight but a mi browser with adds and tracking is no joy either.

Well because I did use this phone only for work.Testing,sharing I only do in emulators.So dropped in the phone with my son to kill it basically what we found out.its not the CPU it is android 10 what request around 2gb of ram ideally.So we got 1gb left normal it should kill processing apps if it runs out of memory.
Now the mi shell miui is holding on 2,2 GB if you play games like asphalt 8,9 zombie hunter,armor god,af arena it is killing itself.
Disable miui or/and give the miui a order to automatically close apps he really don't like that.
So the CPU runs at 100% because off the shortage in memory so in theory we only have 2gb of ram.A android 10 runs idle already around 1,6 gb.So it's no wonder why it lags big
time on a lot.
The fix create a swap file on you're android device.ram expended root ,swapper root,link2sd with gapps root.there is a APK available what create a swap file on you're sd card ,take a good card do.no root.
A video to give you idea how it can run with an without a 3 GB swap file.Even with a 1gb swap file you should walk out the woods

1 to 8 minutes testing 4 games
8 to 11 minutes FPS test .
Last part starting without v memory stuck at boot screen.

Question How to increase the clock speed of the GPU?

On the stock Chinese ROM, I noticed that the GPU is locked to 305 MHz. Can we change some settings to increase this? For reference, the GPU's max speed is 650 MHz.

I'm 90% sure this works. Search for "manage my games" in the settings, and check your games. That will boost the GPU clock speed. With the stock rom you can use the time widget with cpu/cpu clock speeds, and if you open a game and then go back to the home screen you'll see the gpu/cpu at a higher clock speed.
Oh, there's also a bar at the top when you're playing a game and it shows cpu/gpu clock speeds, temp and fps. Even at the stock clock speeds I have great game performance.
{
"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"
}

I already use Legion Assistant but did not see the GPU increase its speed. I guess the game isn't supported, or the increase in GPU speed won't help (the game relies on CPU power more than GPU)

seiferfury said:
I already use Legion Assistant but did not see the GPU increase its speed. I guess the game isn't supported, or the increase in GPU speed won't help (the game relies on CPU power more than GPU)
Click to expand...
Click to collapse
the cpu and gpu increase in speed. Even if you choose beast mode you don't see a cpu increase?

The CPU changes its speed but the GPU is constant at 305MHz, even in beast mode. I guess the game doesn't need it. I haven't tried other games sine I only play one android game right now, and the tablet's other uses are for videos and manga reading.

seiferfury said:
The CPU changes its speed but the GPU is constant at 305MHz, even in beast mode. I guess the game doesn't need it. I haven't tried other games sine I only play one android game right now, and the tablet's other uses are for videos and manga reading.
Click to expand...
Click to collapse
Ok, what if you turned on disable hw overlays in the developer options?

ou2mame said:
Ok, what if you turned on disable hw overlays in the developer options?
Click to expand...
Click to collapse
Didn't work. Anyway I've tried another game and the GPU Mhz increased.. So the game (Ragnarok Origin) really doesn't need the extra GPU power.

It goes up to 670 Mhz in CODM if I set it to beast mode...