View Single Post
Old 11-19-2013, 04:41 PM   #805
Markismus
Guru
Markismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicing
 
Markismus's Avatar
 
Posts: 959
Karma: 149907
Join Date: Jul 2013
Location: Rotterdam
Device: HiSenseA5ProCC, Cracked OnyxNotePro, Note5, Kobo Glo, Aura
Quote:
Originally Posted by Ken Maltby View Post
Markismus;
I assume that only applies to your new Mark 5 "Aura" and not to your Mark 4 "AuraHD".
My Aura Hd fell and the screen is cracked. No joy. Got the Aura as a replacement, but if it becomes too much of a hassle I'll return it for a AuraHD.

Read the last 5 pages of this thread to get up to speed, but I didn't get from it that Hawhill's effort around the frame buffer had relevance for the touch input.

@giorgio Is there a lua-script I can tweak to see whether it's only an exchange?



On a side note: The font in File Manager is tiny. Could it be that the wrong dpi is set for the Aura? Where could we tune that? Seems to be September all over again!

Found it. Screen.lua was moved from to frontend/ui/device. I changed in screen.lua in function Screen:getDPI() on line 120: return 167 to return 212.
I'll check with a debug command what the respons for self.device:getModel() is and add an elseif.

Found it. Input.lua lines 27 and 28.

Last edited by Markismus; 11-19-2013 at 05:02 PM.
Markismus is offline   Reply With Quote