Thread: Aura Install Android apps through built-in browser?
View Single Post
Old 07-06-2017, 12:13 AM   #8
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 GuyDoodles View Post
Thank you. I kept searching these forums to see what the heck they were. I couldn't find anything. Any clue why they call it that? If there is a separate thread or something that explains it all? It would be greatly appreciated.
There is discussion on some of the components, but not much. They are all part of the firmware and hence are just there.

As to the names, I don't know. Why is anything called what it is? There is a pattern, so I would say someone named one of the components, and then when they needed another, they named is something similar.

But, I'm curious, why do we care? The firmware is a package that works together. It doesn't matter what the bits are called so long as they work. The only reason to look at any of this is because you want to fiddle.
davidfor is offline   Reply With Quote