View Single Post
Old 01-14-2015, 08:33 PM   #17
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
And the quick and dirty way to do this is...

Change the line for the Aura HD from:
Code:
AURA_HD_PRODUCT_ID  = [0x4193]
to:

Code:
    AURA_HD_PRODUCT_ID  = [0x4193, 0x4213]
It won't display the correct model name, but everything will work.

As to the non-run-from-source method, my plan is to create a plugin that subclasses the existing KoboTouch plugin. It will basically be a container for the extra code that PeterT listed. While I have done similar things in the past, I don't want to do it until it is needed and can be tested. And yes, I can fake it, but if no-one is around to use it, there are much better uses of my time (reading a book comes to mind). I also don't feel like answering all the "do I need to install this?" questions. Or complaints that it doesn't do anything from those who installed it in the latest calibre.

It will also need changes to the utilities plugin and maybe the extended driver to recognise the driver. Again, I know how to do it, have done it for other reasons, but until there is an actual need, I'm not going to.
davidfor is offline   Reply With Quote