Thank You for your continued support and contributions!
Test builds with frequency scaling enabled but not voltage scaling:http://mit.edu/mgg6/www/rockbox-clipv2_frequency_test.7zhttp://mit.edu/mgg6/www/rockbox-fuzev2_frequency_test.7zhttp://mit.edu/mgg6/www/rockbox-clip+_frequency_test.7zhttp://mit.edu/mgg6/www/rockbox-clipzip_frequency_test.7zSource for just this change:http://gerrit.rockbox.org/r/#/c/1242/Edit: Updated builds.
I am not sure if this is something relevant, but I tested the clipv2 build and experienced a short delay when navigating from WPS to file browser and then to the parent directory with a button press to the left. Music is playing and not paused. This doesn't happen with the current dev build.
The CPU speed is definitely much lower during normal use, on the other hand we used to run on even slower devices so I'm surprised a simple GUI like on the clip lags.
Quote from: saratoga on January 19, 2016, 11:12:37 AMThe CPU speed is definitely much lower during normal use, on the other hand we used to run on even slower devices so I'm surprised a simple GUI like on the clip lags.What should we change in gui boost patch to see it in mainstream?
If I understand correctly, that patches changes the current boost on scrollwheel behavior to boost on any button press and then enables it for AMSv2 targets?
I think enabling boost on scrollwheel for the fuzev2 should happen regardless, all other scroll wheel targets do it, and its probably necessary. I'm not sure about the other change to make boost happen on more types of button press, we should probably talk to other people about it.
Testing on my Clip Zip playing MP3 (fast enough that there is no boosting at all) I notice that menu transitions involving album art are noticeably slower when unboosted, but otherwise everything seems comparable. I don't think boost is really necessary,
but I am ok with enabling it as the cost is very low.
I tested three fuze v2 builds that Oid Maps had provided me (will all saving patches active I believe and varying delays).I have two devices, these are the results:19_5: works with both19_4: works with both19_3: works fine with one. With the second the display shines through for a short time (flickers) when keys are pressed and a few secs afterwards.
Committed frequency scaling.
Do we want to do boost next?
Its probably annoying to use the Fuze V2 without it. Edit: Just realized its already enabled, but only for the scroll wheel.
On the fuze v2 the USB connection seems more unstable (Win10):
Page created in 0.102 seconds with 21 queries.