Display upside down or no touch #5
Comments
Hi stylefish, Regarding the touchscreen, this is defined in default.conf https://github.com/AsteroidOS/meta-mtk6580-hybris/blob/master/recipes-asteroid/asteroid-launcher/asteroid-launcher/default.conf#L3 |
Hey @FlorentRevest thanks for your input, i tried to build asteroid (without changes at first) on my local ubuntu VM (disco) with and without docker, clean repository. i cloned i freshly from the asteroid repo ( i attached a log, maybe you can point me to a fix? thanks :) |
little update on this:
the mentioned log is attached. i will try to figure this out on my own in parallel, but if you have a hint it would be much appreciated. |
Hi stylefish, |
nice, touchscreen is working, but the touch is still inverted. so my current situation:
another hint where i can tweak the touch orientation? in the meantime i will have a look what i can do. EDIT: greetings and thanks for your help so far :) |
You can change the orientation for everything by changing CONFIG_MTK_TOUCHPANEL_PHYSICAL_ROTATION I got Asteroid working on the Lemfo Les1 using that (and a code fix for 90 degree orientation). |
great! watch is working now! thank you guys. @FlorentRevest do you want me to create a PR for this? i think it would break the other harmony watches that are working now because of the change allan175 suggested? |
The reason I've not done a PR for this fix is partly due to having to get a fresh install to build and it's currently not building. |
@allan175 yeah, i think thats the biggest problem... when the conf file could be changed only for inharmony i could create a PR that contains your fix for the rotated touch behavior and the fix for the non-working touchscreen. lets wait for FlorentRevest, maybe he can share his opinion or a solution for this and then you or i can create a PR according to his suggestions :) |
Thanks a lot for your work and patience guys... :) Yes, please do send a PR! In a yocto recipe, you can make changes depend on the platform name using a "_deviceName" suffix to the variable you set. For instance, if you want to apply a kernel patch only for inharmony, you can use this: If your PR only affects inharmony I have got no problem merging it as inharmony has actually never been tested before so you can only improve the situation there... :) |
Hey, |
ok update: i THINK i got it working. i built this and flashed it successfully to my watch and am able to control the screen via touch in the correct orientation. i cant really test because battery died on my KW88 and the cable is so loose that it resets all the time... and the button oddly seems not to work... but i'm pretty sure is was with that config... may be my hardware... |
Correct orientation and touch control fix for inharmony on KW88 #5
This looks fine, thank you! :D |
Hi, thanks, yes i have tested this in all conscience, but as noted my watch died and so i had to test with the magnetic charger attached. to my knowledge it works like the manual change i did before (set rotation to 180 degree). thanks for merging, and thanks for an awesome watch OS :) |
How can I flash the patch solution that allan175 made for LES1 ? For fixed 90 degree touch |
…entation Correct orientation and touch control fix for inharmony on KW88 AsteroidOS#5
Hi AsteroidOS Team,
first: thanks for all the work to bring this project to life! :)
i have a problem on my KW88 (recently bought from GearBest) but i think this might be a newer hardware model? i read sth about a 2018 model. SP Flash says:
when i flash the "harmony" images i'll get a 180 degree flipped "upside down" view of AsteroidOS with touch working. but completely flipped (e.g. top left touch initiates a press at bottom right).
When i flash the "inharmony" image the watch is in correct orientation but touch does not work.
so i thought it might be just a little issue with a config file mix of both images, but i'm unable to determine at which files to look, otherwise i would've tried to fix this myself :)
what can i do about this, do you have any hints for me where to look or do you maybe know what the issue might be?
thanks for any help, and keep up the great work! :)
The text was updated successfully, but these errors were encountered: