tuna Testing / Issues (Retired)

[Franco's Dev Team]

This is the new issue tracker thread for tuna. This first post will contain dated, active reported bugs/issues - newest at the top, kernel revision, who reported them (here and/or xda) and links to xda posts explaining the issue further or external supporting pics or info. Once an issue is added, the reporting post in this thread should be removed to keep it clean and simple for Francisco.

 

If there is testing to be done on an issue here, test builds, etc., then the general idea would be to do that testing and once the issue is resolved those posts also get deleted. That way Francisco can just tell at-a-glance what's going on for this device without needing to pore through the xda thread. If you have to post up a pic as evidence, you should do it externally rather than attach it here, that way we can just move the link in here with the other info.

 

Active Bugs / Issues:

• Apr. 25, 2013 - r376 - bfq v6 is causing "NULL pointer dereference at virtual address 00000038" errors, resulting in reboots. last_kmsg logs linked via xda. (Khrushy / Culex316)

http://forum.xda-developers.com/showpost.php?p=40635164&postcount=41240

http://forum.xda-developers.com/showpost.php?p=40641268&postcount=41248

• Feb. 8, 2013 - r?-* - The usual Play Store install lag moans and groans. We resolved our exacerbation of it from nomerges 2, and I think this is a universal problem right now, but I thought it deserved mentioning since it's still often reported. fatappel in the AK thread recommended going into Google Play Services with AutoStarts and enabling them all (they're not by default?) and said that worked for him. Kurre found some more info that it might be yet another lockscreen widget related issue. (bat0nas)

http://forum.xda-developers.com/showpost.php?p=38667142&postcount=39788
http://forum.xda-developers.com/showpost.php?p=37734085&postcount=38978
http://forum.xda-developers.com/showpost.php?p=39851821&postcount=23101
http://forum.xda-developers.com/showpost.php?p=39888211&postcount=40717

[Franco's Dev Team]

Much the same concept as above, this is where current ideas / suggestions can go. Whose suggestion things were should be included.
 

Ideas / Suggestions: 

• Screen off minimum frequency to complement screen off maximum. Setting screen off min to 192 MHz while global min is 384 MHz could improve idle drain significantly while keeping screen on more fluid. (osm0sis / yellowdie)
• Remove top two CPU OC slots (1.7 and 1.8 GHz) to protect noobs from themselves (or not)? Nobody uses the top 2 slots as daily dirvers anyway, and it periodically causes people issues. (The Gingerbread Man)
• Native OTG support. (osm0sis)