yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Blechd0se:
Thank you, that's actually a bug, forgot to initialize a new Handler() :)

I will also make this error more reasonable, this nullpointer shouldn't be thrown anymore.

About the dialog; yes it should stay there, it should give the user a feedback (100%) that it trimmed successfully.

Btw as long as you get the su-Output you know that it trimmed successful in background, no matter what other logs tell you :)
[Defy Android Development] okij:
Unfortunately, the set on boot function doesn't work for me either. :(

As you remember, I wanted to switch from SetVsel to Aero Control for changing the CPU values after boot. But after a reboot, the CPU settings always are back to default.

I'm using Aero Control 0.9.7 on latest CM11 and also tried wiping app cache and data.

Another bug I that have every time I set my CPU values (300@25, 600@35, 900@50 and 1100@60): when I select "save", the app FCs and after starting it again, Vsel4 is at 62 (the default value). Changing it again to 60 and saving works then - until the next reboot... ;)
[Defy Android Development] Blechd0se:
Are only the cpu oc/uc values are affected or different as well? Root is up and working for aero?

Best thing would be to get me a logcat when android is booted. If you don't notice a small Toast when android boots up

for Aero Control, then something is wrong. Also get me the output of /data/data/com.aero.control/shared_prefs/com.aero.control_preferences.xml

It should save all you values there.

Also get me a logcat of this FC, this shouldn't happen at all! [MENTION=1892363]xdaid[/MENTION] informed me that there is currently a problem with vsel4, if you set

it at the same time you set different values, it won't stick and i have no clue why yet.
[Defy Android Development] TJKV:
Thanks :)

There are more issues I see though, not sure if they are known or not but here they are:

1. In CPU performance the governor is detected as Interactive but no governor specific settings appear below that. If I click on the governor selector entry and "reclick" on Interactive in the popup then the entries appear but most say "unavailable". The only way to make them appear properly is to change the governor to something else and then switch back to interactive. Need to do this everytime I launch the app.

This is probably permission problems for the entries in "/sys/devices/system/cpu/cpufreq/interactive/" in Slimkat, looking at the log here. I will check what the permissions are in CM and change them accordingly. Also boostpulse permissions isn't set properly so it says unavailable no matter what, I have to fix that too. But maybe you should take this into account in your app too, especially since you are designing it for all devices and ROMs and not just Defy/CM?

2. Changing Clock and vsels in bootmenu makes strange values appear in Aero Control, like "62, =4, =8, =5" for vsels 4, 3, 2, 1 respectively. I will get you logs of this (if needed) later though. Gotta go now!

EDIT: At first glance in ramdisk the perms for /sys/.../interactive' entries appear to be the same for cm11 and sk, that is 0660. Only the boospulse entry is missing in sk, will add that.
[Defy Android Development] slimshady76:
I faced this issue earlier. Untick "Set at boot" in Settings --Performance -- Processor. Reboot and then set the values in AeroControl. Looks like SetVsel breaks something in Android. One time I managed to solve the issue by doing what I've described above, but another time I had to start from scratch to get rid of SetVsel's leftovers afer uninstalling it.
[Defy Android Development] Blechd0se:
That's intended. My design goal was to not flood the user with setting she/he don't know about. That's why you first have to

change the governor and then see the governor specific menu.

Now this leads to some "strange" behavior sometimes. When you change a governor, the kernel has to update the dictionaries

and this needs time. I already added a small delay to give the kernel time to update, but sometimes its just to slow, that's when

you get "Unavailable". There are no problems on faster devices.

Maybe i add a dedicated button for this, since its to often "Unavailable" or hide those completely, but then i might break the very generic code,

not sure yet, have to think about it :)

About permissions; don't even think about changing them if you want to ensure your rom works as it currently does. Seriously, i had many troubles

when we started working on 4.4. That's all kernel stuff, don't do anything here unless you really know what you are doing. You can't do anything about

boostpulse, because that's how interactive works. There is only a stub for this parameter, you can't actually change it.

Its only used by interactive itself (i have no clue why google did it that way, but that's how they did it).

I guess, i should explain more how this hole kernel works?

That's strange, but could be how i read those values, i get the hole string and then jump to a predefined position where the vsel value normally is located.

Maybe i need to rework the hole thing a bit, since i added this in a very early version, not sure for now. We even have to think about how to set up OC/UC

properly for our 3.0 kernel and if we have this working i will touch it again :)

Also just some informative post; https://plus.google.com/117941672478859152986/posts/VgLnVCafdxg

That's what i am currently working at :)
[Defy Android Development] TJKV:
Yup that probably explains it, because I OC clk3 to 1000 from 800, so every vsel from vsel3 down gets pushed by 1 character :p

About the rest, okay that makes sense :) And yes something like a dedicated button to load those values is more elegant because now the user might think it isn't working properly :p Anyway you can think about it whenever, it's a small issue really. And +1 for profiles :D
[Defy Android Development] okij:
Both oc/uc values and CPU frequencies get back to default. Root is up and working.

The Toast "Superuser for Aero Control gewährt" pops up during boot process, but after this the CPU still is at the default settings (1000@62 etc.), although com.aero.control_preferences.xml (attached to this post) already contained my preferred user settings. :silly:

Logcat is also attached, as well as a couple of screenshots to show you what happened when:

Screenshot_2013-12-12-08-11-00: CPU settings still at default after boot (although they should be at my user settings)

Screenshot_2013-12-12-08-11-54: I set my user settings and then tapped on Save

Screenshot_2013-12-12-08-12-39: After starting Aero Control again, Vsel4 is still at its default setting (i.e. 62)

Screenshot_2013-12-12-08-13-10: I set Vsel4 to 60 again and then tapped on Save again

Screenshot_2013-12-12-08-13-33: Aero Control then force closes

Screenshot_2013-12-12-08-14-11: I set Vsel4 to 60 again and then tapped on Save again, this time no FC

Screenshot_2013-12-12-08-14-40: Just to show you that "Set at boot" is activated

I hope that this helps you with debugging. :fingers-crossed:

I tried this, but then - after ticking "Set at boot" again and another reboot - the CPU settings are again back to default. :(

For now I decided to set my user CPU settings in Boot Menu, although I prefer to set them later in the boot process, so that TWRP can operate on the safe default CPU settings.
[Defy Android Development] overclockthesun:
[MENTION=4855459]Blechd0se[/MENTION]

A little bug I found in the app. I am now using Aero control for overcloking the cpu. So I selected Live/OC and set my values.... set the upper end for 1200mhz and the lower end for 400 mhz.

Now, after saving ...i can immediately see that the upper end Vsel has changed to 1200mhz as Maximum ...however, the lowest vsel still remains the same at 300 mhz. I have to manually tap and select 400mhz from the dropdown list in the Minimum vsel settings.
[Defy Android Development] Walking dead:
Bug -set on boot

[MENTION=4855459]Blechd0se[/MENTION]

set on boot don't work for me also. I'm in skimkat 4.4.1 (2.6.32 kernel), it used to work on 4.3.the problem may be related to superuser rights which take about a minute or 2 after boot. here is logs 2 times showing app not responding for aero control after boot.
[Defy Android Development] juried:
I have not been able to install the app in slimkat with ART, it shows installing... for ever.
[Defy Android Development] pravarth:
I noticed the color calibration options in the new versions. While they are great, is it possible add more presets or better still, give manual control to RGB and gamma setting?

I'm picturing something similar to what is possible on faux clock app (nexus 4)

Great work on the current version, it looks :good: :)
[Defy Android Development] Blechd0se:
[MENTION=4916555]okij[/MENTION]

Thank you for your logs. It looks like something is wrong with the boot implementation for those cpu values,

i am not sure if its [MENTION=1892363]xdaid[/MENTION] way to load those or mine to store those, but i will rework this.

I've learned enough to simplify the code here.

[MENTION=4194521]overclockthesun[/MENTION]

Thank you for your report too. I will look into it, although the values should update.

[MENTION=4817189]Walking dead[/MENTION]

Thank you for your log too! This one is pretty useful, i could reproduce the same. Looks like CM prevents aero control

from executing and i don't know why exactly. It just kills it. I always tested my app with AOSP & SuperSu and it works

flawless there. Maybe one stupid CM-patch or my app derps by design, anyway i will redesign.

[MENTION=3578300]juried[/MENTION]

No log = didn't happen.

[MENTION=4169325]pravarth[/MENTION]

Yes that was my original approach, but its hard. It took me a while to notice the difference in the kernel for different defy displays.

I don't know if we can something like this working, since there is no code about that in the kernel (and if its done in some closed libs,

well...). I am very happy that we can change the colors at least a bit, maybe time will tell, but its not on my current todo list :)

Those things probably need some time and i haven't had such in the last couple days (work, christmas preparation and other random stuff).

I will go on a small vacation trip this week, so i won't have much time too. Just need to relax a bit, hope you understand.

Btw. if somebody wants to, you can still grab the source code and tweak it for yourself :)

Edit: I already fixed the bugs mentioned above :)
[Defy Android Development] Android_74:
deleted
[Defy Android Development] Blechd0se:
1.0.0 Beta

Hello guys,

i hope you enjoyed the holidays :)

In the meanwhile i prepared the biggest update for Aero Control and yes we are moving finally into beta-stage.

This version features a new profile-management. You can add and define your own profiles. At the moment they are

profiles for the set-on-Boot implementation, so they will only take affect when you reboot your device. I put much efforts

in doing this right so it can be easily extended in the future. I might do also some sort of per-app settings based on your feedback :)

Full Changelog;

Added Profiles - define your own profile with just a couple of clicks!

Added some of the defy parts (no baseband switcher for now.)

Added a root checker - you will be noticed if you have no root installed on your system.

Added a switch to enable/disable the reboot checker

Added a app theme switcher - Aero Control feature now two more themes to choose from.

Added a new tutorial for cpu settings

Fix exception while trimming

Fix set-on-Boot won't execute under some conditions

Fix a bug where vsel4 won't be updated when saved

Fix a bug where Aero Control would crash while saving oc/uc values

Fix a bug where the minimum frequency won't update if overclocked

Fix cpu governor specific menu - its now a new button in the action bar and shows a warning if a parameter can't be changed

Updated translations: chinese (simplified) [MENTION=4572668]struq[/MENTION], [MENTION=3897045]spear1403[/MENTION] for croatian, [MENTION=3777272]marcin[/MENTION]92 for polish, [MENTION=2651354]android74[/MENTION] for italian and german

And many more small cleanups and fixes for a better user experience!

So quite big changelog this time and many things have changed and hopefully improved. This release has around 1600 lines of additions and

around 500 lines of deletions. I hope you guys like it, probably the last release for this year :cyclops:

Download

I also registered myself as a developer for google play and yes, Aero Control is already available on the play store!

The Play Store option has the advantage that you can update Aero Control automatically when there is a new update and also

my server will thank you if you download it via google play :)
[Defy Android Development] frozenwaverider:
[MENTION=4855459]Blechd0se[/MENTION] WOW! fantastic work, thank you!

I think Congratulations is in order :)

Now you are in the Play store you could do a donate app?

I don't use PayPal so that would be a good way for ppl like me to help show our appreciation ;)

Happy New Year!

MB525 RED Lense
[Defy Android Development] ela1103:
Blechd0se

Please Add the Motorola Audio Option In Our Defy Parts Its Useful Other ROM User Like MIUI etc.YOUR DONE GREAT JOB FOR OUR MOTO DEFY
[Defy Android Development] overclockthesun:
[MENTION=4855459]Blechd0se[/MENTION]: Looks like I am the first person to download your app from Play store. Its working great so far. Will report if I see anything.
[Defy Android Development] TJKV:
Lol what makes you say that?
[Defy Android Development] Android_74:
No, you aren't :)
[Defy Android Development] rahul32111:
Hi Blechd0se

Thanks for the aero kernel

I installed V1.00 from play store (apk file fails to install on cm11 29/12 with 03/01 update)

i found that that set on boot works but sometimes it messes gpu and cpu frequencies (like both stuck on 266 and 1000 or cpu at 1000 and gpu at 16)

is anyone else facing this issue?
[Defy Android Development] Blechd0se:
Yes i will consider this when i have more time. Do you just want a donation app or something else?

You mean the audio parts in defy settings? I didn't know anybody uses this since you can tweak sound easily with dsp-manager.

Thank you, but you are not the first person. Google just needs time to update the statistics :cyclops:

If you want to install apk, you need to enable it in the security settings. How did you test that they are both stuck?
[Defy Android Development] frozenwaverider:
[MENTION=4855459]Blechd0se[/MENTION]

A very simple donate app would be great or even better you could have say 3 different one's with varying prices :)

First(just a suggestion) about $1.20? So that everyone can afford it & should have no excuse not to buy ;)

Second, say about $5 to $10? For people that want to thank you for your time but have life bills :)

Third, say somewhere between $8 and $19 for those that want to buy 2 drinks for you :)

And finally if people want to donate more they can buy all 3 or use PayPal?

MB525 RED Lense
[Defy Android Development] arturnet:
Not compatible with MB525 in Play Store

PlayStore says it is not compatible with my MB525, but I can install it on Xoom.

Is it supposed to do?

Greets.
[Defy Android Development] rootdefyxt320:
It's only for CM10 and above. This app was made for Quarx's and Blechd0se's Aero Kernel so you have to be on a 2nd-boot ROM for 100% compatibility.
[Defy Android Development] antarix:
It makes my status bar black.

Using 4.4 2013-12-29 build by quarx.

How to make it transparent?
[Defy Android Development] hotdog125:
Disable low mem flag from the memory tuning section.
[Defy Android Development] frullewulle:
I get not installed error when i try to install this app from play store ...

0.9 beta did instal fine in my cm 10.1 rom
[Defy Android Development] antarix:
Ok

Will try it and report.

Edit:- what settings you use for better performance?

Edit 2:- it works as intended.
[Defy Android Development] hotdog125:
If you have already installed it manually, then uninstall it and then install from the play store.
[Defy Android Development] Blechd0se:
Just pushed a new Version to google play (Google might take a while until they send auto-updates).

While Aero Control should be the perfect debugging/tuning app for user as well as developers there was one thing that was missing;

CPU Statistic. So i added this feature. You can now see how long the cpu spent in each frequency.

I also added auto apply support for profiles (per-app-modes should be really easy to develop now).

Furthermore i fixed this stupid bug that one can't see the cpu governor parameter values.

See for yourself, the changelog;

Added CPU Statistic overview

Added Sweep2Wake Switch

Added a few more tutorials

Fixed a bug when choosing the CPU Governor Parameter

Fixed a bug where profiles won't apply automatically

Fixed perference back-Button behaviour

Optimized a lot of core functions and also reduced memory footprint (Aero Control should now use even less ram)

Updated translations: german, italian (@Android74), croation (@spear1403), chinese-simplified (@struq), portuguese [MENTION=4878609]leandrolutz[/MENTION], romanian (@cyrusct82)

As always you can grab the apk file from my server or if you want to download it directly from the play store.

Thanks to all contributors and also thanks to all users which rate my app on the play store. This really helps me a lot!

If you haven't downloaded it already, what are you waiting for?

Download

Download Play Store
[Defy Android Development] Lord_Flaya:
Love the new version. :) One quickie tho.. Is it possible next version could include theme for black background with white text..? Cheers
[Defy Android Development] niksy+:
Oh, man, these CPU statistics look so nice :D But could you maybe add a "reset counters" button? I don't see one :D An option to "reset when unplugged" would be great, too :)

Thanks for the update, will rate on the play store asap!
[Defy Android Development] L3ibnitZ:
Hi blechdose.

I'm using your app on my milestone2.

Does the defy only have 3 frequency steps? The ms2 has 4.

Is it possible to support 4 frequencies in Cpu statistics and maybe also the deepsleep time?

Maybe a little ot:

I was able to test your sweep2wake feature since czechop supports it in his latest version of cm11. Enabling the display only works if i turn off the display using the powerbutton or if it times out. Turning on the display with s2w doesn't work after turnung off the display with the s2w gesture.

Thanks for your great work!
[Defy Android Development] niksy+:
About the sweep2wake issue, read here - http://xdaforums.com/showpost.php?p=49245859&postcount=1873

Basically, the problem is in our still Moto-bound 2.6.32 kernel. It works perfectly in the 3.0 one that is in development, but it has other issues with more important (basic) functions :( Try pushing any remaining MS2 developers into the 3.0 kernel development, we would all benefit a lot from the switch to it :)
[Defy Android Development] Urdle:
+1

I have the exact same issue : when trimming system, the screen goes black, the backlight (and buttons) are lit, but the phone is completelly unresponsive (20 minutes or so, removed the battery, tried again, still no luck).

Trimming /data gets me a frozen screen, it's still able to light/dim the screen and wakeup if I don't wait to long (except for that, it's completelly unresponsive. Waited 25 minutes before removing the battery)

Trimming /cache did not seem to do anything (nothing on screen, but at least the phone is still usable)

I'm using the version of the app on gplay; and I'm using the last Quarkx build (2014-01-20)

Any suggestions ?

Another completely unrelated stuff : do anyone know a tool to export a dmesg/catlog and other stuffs via google drive ?
[Defy Android Development] hotdog125:
Well, that problem got fixed for me with 0.9.7.
[Defy Android Development] Urdle:
I use version 1.1.0

I tried using fstrim -v /system from TWRP, but it does nothing (directly return to prompt), same with /data. Only /cache worked.

I'll try lagfix...
[Defy Android Development] slimshady76:
I've been playing with the "Low Memory" option under [MENTION=513620]Quarx[/MENTION]'s CM11 and I must reckon I don't understand how it works. Enabling it leaves my MB526 with just 20-30MB of free RAM, while disabling it boasts free RAM to 150-200MB...
[Defy Android Development] Urdle:
Forcing my way to do the "trim", with lagfix, twrp commands, etc, I finally managed... to almost brick my phone (Motologo, not even a blue led, had to flash a sbf all over again). I think i'll stop experimenting it :)

It's a 479MB RAM device, and without the "low memory" option I rarelly go under 200Mb free and it is AFAIK not natural for an android system to have always at least 40% RAM free.

Besides, I didn't notice any drastic boost associated with this great amount of free ram (apps are still closed even with that much free ram)

I think there are 2 ways to see it :

Either the "free RAM" indicator isn't actually accurate and is completly bogus.

Or the "low memory" option, when disabled, makes android kill everything very fast because it expects to have 200MB free at any given time (which means 20% on a 1GB system, that wouldn't be unusual).

So, either way, enabling "low memory" would be best, because I don't think that having android kill all background tasks is a good thing.
[Defy Android Development] TJKV:
Doesn't kill everything fast, just disables some graphical whizbang. Graphic buffers take quite a bit of ram. Your minfrees handle app killing.

That said I find its much more useable when low memory flag is enabled.

Sent from my Nexus 5
[Defy Android Development] erdnuesse:
Talking about minfrees, getting only slightly ot, anyone knows if supercharger script is usable in any way these days? (kk-4.4, krnl-3.0)
[Defy Android Development] Blechd0se:
Hello Guys,

just pushed out a new release of Aero Control!

Just check out the Changelog;

Added a new CardLayout based interface for the overview panel (with a few additions)

Redesigning the CPU Statistics panel a little bit

Complete overhaul of the statistics data structures as well as its calculations

Fixed logcat spam if some files doesn't exist

Fixed a potential reboot during trimming

Fixed theme won't apply immediately

Fixed overclocking values won't show correctly in statistics

Made some base calculations smarter to be more efficient

Much more smaller stuff, check github for details

Updated translations: polish [MENTION=3777272]marcin[/MENTION]92, chinese-simplified [MENTION=4572668]struq[/MENTION], italian [MENTION=2651354]android74[/MENTION], croation [MENTION=3897045]spear1403[/MENTION], romanian [MENTION=2871913]cyrusct82[/MENTION] (thanks guys!)

So all in all many many bug/logical fixes and also a small UI redesign. Some guy said he didn't like the overview panel with

those italic font and since that very moment i started to think about how to redesign this. Also if you overclocked your CPU it should display

those values now correctly. I spend much time on the statistics panel to tweak it as much as possible, basically i did a

complete rewriting of the base data structure and how Aero Control loads those CPU values. Have fun!

As always you can get the apk file from my server or download it via Google Play.

Notice that Google needs some time until they give you the OTA update.

I am also very thankfully if you leave a rating for my little humble app in the Play Store. This really helps

me a lot!

Download

Download Google Play
[Defy Android Development] ldiomedi:
Hi. Thanks blechdose for this updated. I'm on cm11 from 2-15 and overclocked at 1200 with aero control, but CPU statics it's not showing the correct values.. Pic it's attached. In cm11 was reported it's working, but not for me. Any idea why?

Enviado desde mi MB526 mediante Tapatalk
[Defy Android Development] slimshady76:
[MENTION=4293182]ldiomedi[/MENTION], same happens to me. Overclocked my MB526 with AeroControl (300@29, 600@41, 900@51, 1200@65) and the two last frequencies won't show up in AeroControl's Statistics...

EDIT: A reboot made the 1200MHz frequency appear!
[Defy Android Development] Badwater55:
Same here, after reboot all looks fine; cpuspy, nofrills as well.

Thanks for your trouble!