Actually I figured it out reading all the previous comments - none of the Google services are started by default which is why it couldn't connect to Google.
Now that it's synced, it's actually really good which begs the question - why does nobody make an Android eInk reader ?
I could install Google Play Books no problem and although it's bit slow to startup, it works flawlessly which is just perfect for me because I tend to buy my books from Google Play as they're often cheaper than Kobo or Amazon. So it sync's fine with my other Google Play devices and, of course, you can read on the web or upload ePub's via the web interface.
There's a few apps that I would have liked to install but they're not listed e.g. Twitter, I'm guessing because they don't support such an old version of Android. Also, being rooted, I wouldn't want to do my banking on it.
So how did you create this distribution, was it just a case of building AOSP with the Kobo kernel or is there more to it than that ? I'm guessing that you chose 2.3.4 because of the memory constraints ?
It would be nice to get to KitKat or Lollipop but I'm guessing that the embedded Chrome browser will just be too huge to run comfortably in 512MB.
Fabulous work though - I'm very impressed and grateful for such a useful Android distro !
|