Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge Existing Code Request - USB OTG-Y Charging Support #10

Open
sunbladehub opened this issue Nov 22, 2017 · 1 comment
Open

Merge Existing Code Request - USB OTG-Y Charging Support #10

sunbladehub opened this issue Nov 22, 2017 · 1 comment

Comments

@sunbladehub
Copy link

sunbladehub commented Nov 22, 2017

Would it be possible to include support for OTG-Y charging? The code has already been written by sollapse (source here) and greatly improved by Phoenix Wright (source link is broken)

OTG-Y charging enables people to use OTG devices for long periods of time without draining their battery - instead it charges! I have some experience coding in C++/Java (mostly closed source for work) but no kernel experience. If there is anything you need help with let me know. Thanks!

Background note: I have flashed Phoenix Wright's latest kernel zip on the latest sultanxda CM13 ROM and OTG-Y does work but the UI is janky and feels 10x slower. No jank and fast responsive UI is observed after flashing Phoenix Wright's kernel on top of cm-13.0-20160104-UNOFFICIAL-Sultan-bacon.zip. The jank is present if flashed on cm-13.0-ZNH2K-20160603-STABLE-Sultan-bacon.zip.

@sunbladehub
Copy link
Author

For what it is worth, I performed a bisect to identify the offending cm-13.0-XXXXXXXX-UNOFFICIAL-Sultan-bacon build for stable OTG-Y support. Here are the results after flashing Phoenix Wright's kernel on top:

STABLE: cm-13.0-ZNH2K-20160423-STABLE-Sultan-bacon.zip
UNSTABLE: cm-13.0-ZNH2K-20160430-STABLE-Sultan-bacon.zip

So for anyone who is interested in OTG-Y support you can get it on the OPO with Sultan's ROM, providing you are ok with forfeiting a year's worth of ROM development.

If anybody can identify what code change might have lead to the jank/sluggishness I'd be interested to know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant