Hey, I thought that i`d recap the current status of the Augen Gentouch device but then I saw that users cutterjohn42 from mobileread.com forums have already done that so i`ll just quote him
:
I’ve had one of these since Saturday, Augen calibrate update, rooted, Clockwork, setcpu(min 126MHz/max 600MHz left on OnDemand), marketfixed and clockwork update.zip fix(perma fixes market, redoes root, and adss nexus one startup anim. (Raincheck from 7/29) MUCH snappier than the base fw w/above. (We’re pretty sure that it’s a Dawa D7 or cost-reduced variant.)
It’s not bad, I seem to get about 3h or so of WiFi operation after doing all the mods/hacks to it. Probably 4.5 – 6ish hours w/no WiFi. (These are rough as I’ve never run it dry since modding/hacking but it’s NOTICEABLY better than the default shipped fw.)
It DOES run a bit warm, as in it does eventually get to feel warm on the battery side once you’ve been going through several web pages.
Brightness controls don’t work properly, only slightly modified brightness i.e. not the range that you would expect.
No hw volume control, or any virtual vol. control buttons yet.
Only have really tried iReader as a reader app on it so far as I’ve been reading text files and most of the other apps mainly seem to support EPUB, FB2, etc. but not text.
Played a few videos w/the YouTube app. They actually play better than on my nb w/a 4850 mobility! (at least under Ubuntu 10.04, might be close v. Windows, but I’d still give the edge to the Gentouch)
Doesn’t seem to truly suspend either, so I have it power down when not using it for a while. Boots fairly quickly, but I’ve never timed it exactly. Definitely WAY faster to useable than my Sony PRS-505 is from a cold start, but not as fast as my nb booting either Vista or Ubuntu 10.04.
CPU clock speed is still stuck @ 600MHz. This requires a new kernel compile to “fix”.
Touchscreen is MUCH better after the calibrate update and then running the calibration app.
Battery seems to be soldered(by leads) direct to mb, bad IMNHO as I GREATLY prefer easily user-replaceable batteries and look in askance at companies who do not design for this.
Accelerometer (“g sensor”) does NOT function, but various Android system info apps DO list it as present.
OpenGL ES is apparently being reported as 0.0 instead of 2.0 as the datasheet indicates that the TCC8902n + mali(GPU) can support.
Nook, Kindle, FBreader, Aldiko, etc. all work.
Browsing with the builtin in browser is decent, but I’m having a hard time going back to the window oriented approach v. tabs like I have on my desktop although I guess it’s understandable for a machine with limited resources.
Skyfire and Dolphin browsers also are reported to work, but I haven’t tried them myself yet.
Android market works, but google maps won’t update ATM. (Apparently a problem that crops up from time to time with various Android devices and releases…)
User reported a problem with last.fm caching, haven’t verified this myself yet. Another reported Pandora radio working, apparently good enough for his wife.
Apparently all units have the same MAC address assigned to the wireless card. Reports of a second batch(box w/o Android Market support claim) apparently have a different MAC address. Not sure if they’re all unique now or just different from the earlier batch. (Mine must be the original batch as the box still mentions Android market support… and well.. I made it be supported…
)
Note on batt runtime: Apparently some of the units have been shipped w/2100mAh batts while others came w/1500mAh batts. Not sure which is in mine as I may still end up returning it IF Augen is not able to provide better support(we’re still waiting on a more complete fw update and so far they have pushed it back once, now scheduled for 8/20, likely with no accelerometer fix or CPU max frequency unlocking).
i.e. it’s not bad, but w/o better Augen(Dawa?) support and/or source code so that we can fix things ourselves I can’t really recommend it for most users. (Probably could pry the kernel patches out of Telechips(and hope that the Dawa changes are close enough) and then try to build a generic android build would be OK but alot of work/debugging. Already seems to be pretty much base Android 2.1-update1 anyways given what i see in the emulator(SDK) and what the base GT fw looked like minus extra apps are very close.