f.Ku Suggestions / Issues (Retired)

[Franco's Dev Team]

This is the new suggestion / issues thread for franco.Kernel updater (f.Ku). This thread will be a little less strict than the kernel issue threads since it's really only for suggestions. It will still probably be a good idea for us to clean it up once in awhile though. A lot of these came from the tentative "to-do" list Philip (yellowdie) and I brainstormed and Francisco worked from during the f.Ku rewrite. So, for the newly formed F-Team, have a read and see if there's anything you want to add or comment on. Suggestions and issues will be added in a similar format to the other issue threads, with this first post containing the current suggestions on the table until Francisco decides about them. Who originally suggested the idea should be included.

 

Keeping all the suggestions and any active bug / issue reports in these first two posts will keep it clean and simple and allow Francisco to see what's going on at-a-glance. If you have to post up a pic as evidence/mockup, you should do it externally rather than attach it here, that way we can just move the link in here with the other info.

 

 

Ideas / Suggestions: 

• The suggested kernel backup name is ʺboot-#342ʺ - is it possible to change the # to an r, or is it more trouble than it's worth? That way it would match the ones from minooch.com. (osm0sis)
• Share settings could also have the Governor settings, TCP CAA, plus Trinity contrast, OMAP4 gamma, and CAB settings added in too for completeness sake since people always include those when they share their color settings. (osm0sis)

http://pastebin.com/pWhzB0Ec

• Adding Screen off min(?), Governor control settings to Powermodes. And also fsync and tcp c.a.a. added too for good measure, since they are also performance options. GPU freq and hotplug settings should be in Power modes for the N7. (osm0sis)
• Add governor tunables to presets and add support for other Nexuses. Put preset selection as a submenu? (yellowdie)
• The ability to backup and restore all f.Ku settings to file. (yellowdie)
• Add custom LMK exclusion to the f.Ku boot service for use with 3rd party launchers. Users would select their launcher from an app list - this way it remains future compatible with every launcher. (osm0sis)
• Folks would like some widgets, including cpu temps, voltages, one to cycle powermodes and to toggle Fast charge. (osm0sis)
• Tasker integration for changing power modes, and maybe Fast charge. (osm0sis)
• Ability to edit Power modes and color profiles once created would be awesome, just not sure if it's worth the trouble. (franciscofranco)
• Bring Device Monitor back to its former glory, with voltages, etc. It would be cool if you had the kernel write the current IVA frequency out to userspace like suggested before, that way you could reorder the stats by the more logical MHz - mV. Maybe space them into pseudo-columns? (osm0sis / yellowdie)
• Currently I take it Powermodes are done with a directory of files that the app option just copies into the main directory? Maybe you could just have a subdir that the main preset list wouldn't read but a preset submenu would be hard coded to each inside. That way you'd keep the main list uncluttered but not have to really change any functionality for set on boot or anything. (osm0sis)
• My idea for attractively handling a long list of Powermode options if/when governor tunables get added in; in my screenshot you can see by the scroll bar that things don't fit, and that's fine, since this dialog is a short list at the moment. Only problem I see is that when it does become longer, the button to "Create a custom Power Mode" would be way at the bottom and you'd have to scroll down to it. So my idea here is that the button (and name) not be part of the scrollable area. It could be outside of it; part of the "frame" of the dialog. I attached a visual aid/mockup in case that's still not a very good explanation, hopefully it can get the idea across better. (osm0sis)

http://i.imgur.com/b4f8RH1.png
http://i.imgur.com/YPI4nK6.jpg

• A cool feature is under Device Monitor to have the ability to check the live cpu freq per core not just a global value. (joaquinf)
• A graph or pie chart for how much time is spent using the different cpu cores. Also something to display time spent at different CPU speeds (like how CPU spy works). (The Gingerbread Man)
• read_ahead_kb, nr_requests / other queue settings. vm settings too for good measure so we're one up on Trickster again. (malaroth / osm0sis)

[Franco's Dev Team]

Much the same concept as above, this is where issues will go since there are generally fewer of them, newest at the top. Important information to include will be date reported, f.Ku version, who reported them (here and/or xda) and links to xda posts explaining the issue further or external supporting pics or info.

 

 

Active Bugs / Issues:

• May 29, 2013 - v9.0+ - Implement a way to avoid the Google Play license check (opt out of the system monitor functionality?).  I was recently vacationing in an area with no data/Google services connection, and I could not change my power mode / underclock, or even open the F.ku app.  I doubt most paying customers feel this is acceptable - at least I know I was pretty upset. (pkgnex)
• Mar. 18, 2013 - v* - The sound options in f.Ku should have a disclaimer, like the Power Modes do on first run, that explains the bugs present and workarounds required for the interface. (osm0sis)
• Feb. 17, 2013 - v8.6+ - Governor Control and IO Scheduler Tunables should populate in proper alphabetical order to match Trickster and prevent ongoing confusion. (osm0sis)
• Dec. 15, 2012 - v* - When SR is disabled Device Monitor should pull the corresponding MPU voltages from the custom voltage table rather than showing 0mV - provided this gets re-implemented. (osm0sis)
• Dec. 1, 2012 - v8.0+ - Kernel backup/restore backup list should only populate with .img files and ignore anything else in the kernel_backups directory. (osm0sis)