View Single Post
Old 04-01-2018, 09:28 PM   #18
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
Quote:
Originally Posted by geek1011 View Post
The user agent currently follows the following pattern:

Mozilla/5.0 (Linux; U; Android 2.0; en-us;) AppleWebKit/%1 (KHTML, like Gecko) Version/4.0 Mobile Safari/%1 (Kobo Touch %2/%3)

%1 is the webkit version.
%2 is the last 4 digits of the device id (like 0375 for the KA2, which is the last 4 digits of 00000000-0000-0000-0000-000000000375)
%3 is the current firmware version

This is useful because this means that my firmware downloader will be able to detect the kobo firmware version and device id to support new devices easier. I will add this feature soon.
You are getting people visiting you firmware downloader from Kobo browser? But, I'm not sure that would help support new devices as the device has to actually be out before you will detect them. And of course, you can't actually download the firmware file using the browser as the firmware only downloads e-books.

And to get the support for new devices, there is usually evidence for any new devices in the firmware well before the device is released. Though they do tend to keep the name hidden.
davidfor is offline   Reply With Quote