yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] p0nk0:
Eken m035

I actually have a Eken m001 first generation device and had not seen the m035 device listed at the eken website but now that you mention it i went ahead and looked around for it to view the specs, but the website were I originally saw the tablet was

www . ekengroup . com

At this website which had readily the firmware files for the m001 thru the m003 they have the model m006F which has the infotmic x220 chipset and said tablet is currently at 2.2 Froyo, and SOMEHOW they claim they have flash support at a additional license charge. If we could get the firmware for this maybe we could make a froyo build. If anyone knows chinese, dare they ask for the update zip or files for a "clean reformat of this machine" for our cause?

Will keep loking!
[Android Software/Hacking General [Developers Only]] flap:
You're right, this model http://www.ekengroup.com/en/products/show.asp?id=24 looks like a FT2...

Maybe, it could be a solution.
[Android Software/Hacking General [Developers Only]] Jiggity Janx:
Since you guys may not reading the Q&A thread:

Android 2.2 released for Zenithink

http://xdaforums.com/showpost.php?p=10904864&postcount=184
[Android Software/Hacking General [Developers Only]] stragulus:
@Jiggity: So far, the zt-180 kernels do not work with the flytouch2. Also, some hardware is different, and it has turned out that patching that is probably the most work!

The good news is that my froyo build is coming along nicely. I don't have massive amounts of time to hack on it, but I'm getting quicker at understanding the system.

The status so far:

Wifi works, though it consistently fails exactly once after each bootup. No biggy, you can always just select the remembered wifi network manually, and from then on it keeps on working.

I have integrated touchscreen calibration, with a tool that will ask you to do this if you haven't done it yet at startup

I have fixed the g-sensor rotation (by swapping x & y). I've even implemented it such, that the swapping can be reconfigured on the fly, so for games who still get it wrong, it can be swapped differently! This does require an additional simple to write android app to switch between different configurations, but any android app developer can write that in a heartbeat.

I have started to implement audio support. Just booted after a first attempt and it doesn't work, but that will hopefully just be a little research and debugging.

Major things left to do before a first flashable version can be built, see here:

https://github.com/stragulus/Flytouch-2-Device-Config/tree/master/flytouch2

In the same dir, INSTALL.txt explains how to build this froyo build yourself, if you feel lucky (do you, punk?)

Comments welcome!
[Android Software/Hacking General [Developers Only]] m4rkiz:
just read your todo.txt - it does have a microphone ;) , although it is extremely crappy one (really poor hardware and seems like wrong pcb routing [too close to chips, especially speakers - plenty of noise] on my v3.3 board)

successfully replaced it with something much better though, and quality is quite good now

http://xdaforums.com/showthread.php?p=10893832#post10893832
[Android Software/Hacking General [Developers Only]] wahliow:
Looks like a new firmware may be available

Look at the picture

slatedroid.com/index.php?topic=15457.0

model number

SAWEE Pad

firmware version

2.1-update1 v1.9:#2852

baseband version

unknown

Kernel version

2.6.32.9 infotm-sqa@infotm-sqa-desktop #50

Build number

wwe10-eng 2.1-update1 ERE27 eng.infotm-sqa.20110109.165019 test-keys

anyone else has this firmware - say it is a version between ver 2.1 and 2.2.
[Android Software/Hacking General [Developers Only]] dcoelho:
Where is a link to download this firmware?
[Android Software/Hacking General [Developers Only]] super_vasco:
Flytouch 3 Android 2.2 GPS Tablet PC - 4gb Superpad 2 Epad Apad - Flytouch3

What is a Flytouch3 or Superpad2?

chinagrabber.com/flytouch-3-android-2-2-gps-tablet-pc---4gb-superpad-2-epad-apad---flytouch3.aspx

It is the next generation in a long history or 10-inch Android Tablet PCs.

The Flytouch3 (upgraded Android 2.2 operating system - Flytouch2 only has android 2.1.

Superpad 2 is the Upgraded Android 2.2 froyo O/S Version. Previously the Super Pad only had 2.1.

In addition to the Android 2.2 upgrade this apad tablet improves on its predecessors by adding 4gb of Nandflash, instead of 2gb, and 512mb DDR instead of 256mb.

The screen is more fluid and there is no need for the annoying registration number the original Flytouch 2 Required. GPS navigation is pre-installed and it also has the official google android marketplace.

Lastly, Flytouch 3 / Superpad2 has a battery that is the biggest of them all with 6400mah of juice for browsing up to 6 hours!

Flytouch3 / Superpad 2 Hot Spots:

- Android 2.2 Froyo OS

- Built-in GPS Navigator + GPS Antenna

- Dual MicroSD / Single TF Card Slot

- Dual USB Ports for plugging Keyboard Cases

- Larger battery for extended usage time

- Built in Youtube Application for browsing videos

- Android Market Pre-installed

- 1.3MP Web Camera

Superpad 2 / Android 2.2 FlyTouch2 Gps Tablet PC Specs:

*

CPU: InfoTM X220 ARM11 1Ghz

*

Display: 10-inch (1024×600 ) LCD

*

RAM: 512MB DDR2 / ROM: 4GB - Note: only 2gb is available for use as half of memory is used for O/S, Apps, and GPS.

*

Battery: 6400mah - use up to 6 hours!

*

Camera: 1.3M

*

GPS: HopeRF XN203

*

Wifi: 802.11B/G

*

I\O: 2x USB; 1x RJ45; 1x HDMI; 2x MicroSD; 1x Stylus-slot

*

Vibration

*

Accelerometer

*

Dimension: 269.91mm*170.45mm*14.89mm

*

Buttons: Back, Home, Menu, Volume, Wifi, Reset and Power﻿

Note: Unit runs Android 2.2 but only comes with Android 2.1 Manual at the moment. Android 2.2 Manual's will be available after the Chinese New Year.

This is a great Unit!
[Android Software/Hacking General [Developers Only]] Jiggity Janx:
Yeah, I remember seeing you and another try booting zt180 kernels with no luck. Great work thus far on your kernel and build though. Something tells me you are about the only one working on it. Any chance the Flytouch3 (upgraded Android 2.2 operating system) will help any? Unfortunately I am more of a tinkerer and less helpful with full on development.

ANYONE planning on/have the ability to build custom ROMs for any 2.2 kernel?

I see an attachment on the post with the new build... maybe sign in?
[Android Software/Hacking General [Developers Only]] [duno]:
Usefull tool for yaffs2?

Hi, found this:

http://jiggawatt.org/badc0de/android/index.html

ARM version (alternative source) (for creating yaffs2 images)

http://jiggawatt.org/badc0de/android/mkfs.yaffs2.arm.tar.gz

I tried it yesterday and created a system.img on my sdcard with

# ./mkfs.yaffs2 /system /sdcards/system.img

good luck
[Android Software/Hacking General [Developers Only]] stragulus:
This probably doesn't work (to use directly to flash), because the zt-180 and flytouch 2 use a slightly modified version. The zt-180 topics contain a few references to it. It's easy to modify though, so if you're interested I can dig it up.
[Android Software/Hacking General [Developers Only]] Jan Rune:
I can do it. Just tell me whats have to be done..
[Android Software/Hacking General [Developers Only]] flap:
Hi all,

I'm doing the whole process of installation using INSTALL.txt, it's long but running...

:)

Thank you so much stragulus !
[Android Software/Hacking General [Developers Only]] stragulus:
Cool! Mind you, I'm not yet sure if it is required to change the rotation of the accelerometer, but I remember when I still actually used my tablet rathen than hacking it to bits, that some games didn't get the rotation right. While the browser did. So it seemed that they interpreted the values differently.

So, in order to circumvent this, I made the base framework read a system property every X seconds that describes how to swap the values read from the accelerometer.

Normally, the accelerometer produces values for axis x,y,z. Without changes, this makes all apps on the froyo build get the rotation wrong by 90 degrees. So, I created the property 'debug.sensor.swap_accel', which describes how to swap the axes. I fixed the rotation by setting this property to '-y,x,z', which means that x and y are swapped, and y is also inverted.

Let's say that games do indeed interpret it differently, then the user would switch to the android app to be written, and choose a different swap profile which writes the new values to the system property. Switch back to the game, and tadaah, problem fixed.

For extra bonus points, the app would run as a background service, and detect which app is running in the foreground, and change settings based on that (e.g. link a profile to an app). That's more userfriendly. Don't know exactly how/if this would work though.

If you're up to it, I'll obviously add it to the rom :) I'm planning on geting an alpha release out this weekend, even if it's still unpractical for daily use. Hopefully it will inspire people to work on it as well!
[Android Software/Hacking General [Developers Only]] iloveei:
Just a quick question to the developers:

I'm not a dev at all. But I wanna ask you guys what can we expect from 2.2 (or even 2.3?) on your FT2... will it be worth he thrill, or is the 256 Mb Ram to less anyway for froyo?

I'm wondering if i should keep my device or buy myself a "good" 2.2 tablet...

:/
[Android Software/Hacking General [Developers Only]] flap:
stragulus,

I get an error when I try to add tslib... Can you point me to a solution?

vps3:~/src/mydroid/external# git clone git@github.com:stragulus/Flytouch-2-External-TSLib.git

Initialized empty Git repository in /root/src/mydroid/external/Flytouch-2-External-TSLib/.git/

The authenticity of host 'github.com (207.97.227.239)' can't be established.

RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.

Permission denied (publickey).

fatal: The remote end hung up unexpectedly
[Android Software/Hacking General [Developers Only]] unixbob:
You need to create an account on github.com, create ssh-keys on your linux box and then add the contents of the id_dsa.pub to the ssh-keys stored in your github account

Have a look at this:

http://help.github.com/linux-key-setup/
[Android Software/Hacking General [Developers Only]] flap:
Ok, thanx for your help. I'll try asap.
[Android Software/Hacking General [Developers Only]] stragulus:
WTF? I thought it was hassle-free for read-only users. That sucks, sorry to hear that.

Still busy porting sound. I had to reconfigure the build process for that, or it would refuse to use alsa as the audio backend.

Finally figured all that out, but it still doesn't work :mad: Of course the level of debugging logs is about as useful as a bag of sand in the Sahara. The FW1170 firmware logcat.log goes like this:

01-26 20:25:27.995 I/AudioFlinger( 1983): AudioFlinger's thread 0x19030 ready to run
01-26 20:25:27.995 D/ALSAModule( 1983): route called for devices 00000002 in mode 0...
01-26 20:25:27.995 D/AudioFlinger( 1983): Audio hardware entering standby, mixer 0x19030, mSuspended 0
01-26 20:25:28.000 D/AudioFlinger( 1983): MixerThread 0x19030 TID 2016 going to sleep

My build does:

01-29 10:02:11.095 I/AudioFlinger( 1988): AudioFlinger's thread 0x19080 ready to run
01-29 10:02:11.465 D/ALSAModule( 1988): route called for devices 00000002 in mode 0...
01-29 10:03:06.630 D/dalvikvm( 2058): Ignoring duplicate verify attempt on Ljava/lang/Object;

Note the lack of AudioFlinger feedback after the 'route called' message, and the long delay until the next message. No idea what's going on there! Looks like another day of debugging and researching for just a single issue!

Oh, I also tried my hand at getting the camera to work using the binary libs from the original firmware, but that's a no-go. But that's lower on the prio-list, would have been nice if it Just Worked for once though.

Repeat after me: WE NEED SOURCE.
[Android Software/Hacking General [Developers Only]] unixbob:
I'm curious why you are using 1170 as your base. many of the newer firmware's are much more responsive and I had assumed that performance boost was from improved kernels. Just wondering why you are using the oldest version of the firmware for your kernel
[Android Software/Hacking General [Developers Only]] stragulus:
Because I started on this build when fw1170 was the most recent one. I have tried to use 1623 instead, but that crashed all over the place. Given that most things just worked in that FW I don't see a reason why to change just now; debugging is hard enough as it is without changing other variables.

Once the basics work though, I'll definitely give a more recent FW a shot.
[Android Software/Hacking General [Developers Only]] unixbob:
makes sense. was asking because I was looking at your alsa error and when I did an lsmod on my 1623 build there weren't any drivers loaded for the sound card. so assuming it's built into the kernel I wondered if a newer kernel might have the error resolved. but then I'm probably talking out of my hat
[Android Software/Hacking General [Developers Only]] stragulus:
It's possible, but audio worked fine in fw1170. It is however impossible to tell whether they fixed issues in the kernel driver, or in the framework. Judging from the logcat.log output of fw1170, it seems they've been adding debugging info to the external/alsa-lib code, so I bet they modified something there. There's no telling if they didn't change this afterwards.

Could you attach a dmesg and a complete /data/local/logcat.log after a fresh boot of the tablet? I'm interested to see if I can see anything different in there.

I'm currently trying to get all the possible debug messages of alsa-lib to be shown in logcat.log, so that debugging is easier.

I do occasionally get audio working, but AudioFlinger displays messages such as

01-29 18:22:58.375 W/AudioFlinger( 2426): write blocked for 9999 msecs, 5 delayed writes, thread 0x198e0

after which sound doesn't work for 10+ seconds. So..something's fishy somewhere.
[Android Software/Hacking General [Developers Only]] unixbob:
Here you go
[Android Software/Hacking General [Developers Only]] stragulus:
Thanks! Got them. Audio-wise it is exactly the same as fw1170.

Here's a tip: Build the release in DEBUG mode, not in RELEASE mode, if you want (tons of) debugging info. Useful when analyzing problems such as the audio support. Though it still hasn't led to the solution of the problem.
[Android Software/Hacking General [Developers Only]] stragulus:
And another brilliant insight; why not rip the audio libs from the froyo firmware from the zt-180? It's integrated in the CPU, it's bound to be the same. And indeed! With 3 libs from their FW, it works! Could have saved myself half a day of frustration here. But the end result counts!
[Android Software/Hacking General [Developers Only]] kellt:
Does anyone know whether it is possible in software way to be deactivated vibration when turning on or waking up the tablet superpad
[Android Software/Hacking General [Developers Only]] unixbob:
ha. nice piece of lateral thinking. what else isn't working now?
[Android Software/Hacking General [Developers Only]] veryjo:
The settings in the bios are not in the software. I can`t open the bios..?
[Android Software/Hacking General [Developers Only]] stragulus:
Several things, most importantly hardware video decoding, reviving from standby (the screen stays off), better wifi support (display signal strength, no need to restart once), the camera, gps, HDMI-out (I think, never tested).

I update TODO.txt whenever I fix or break something.

Does anyone know something about the hw video decoding? From what I gathered, this is mostly done in opencore, which is in external/opencore. This is where the firmware producers build in the hardware support. There's no reverse-engineering that, so it's gotta be done by copying the right files and changing settings. The question is; which files and which settings. I haven't been lucky enough to get this working.

Things I did do so far:

Set opencore.asmd=1 property

Copy /system/etc/pvplayer.cfg from zt-180 froyo firmware

Copy various libs from /system/lib from zt-180 froyo firmware. This is the (very) tricky bit, as some files generated by the AOSP build wil have to be overwritten. I don't know exactly which ones though. Might also have to change the build a bit to trick it into thinking we're using a h/w accelerated opencore implementation. Maybe just by building the external/opencore with dummy settings?
[Android Software/Hacking General [Developers Only]] stragulus:
Hmm, just tried my first version of a flashable firmware (using burntool). First impression: Whow, it is *fast*! Running it over a network filesystem was dragging it down significantly, so now I finally got an impression of the speed it could run at. Nice! :)

Things didn't really work though. Wifi didn't start, the sdcard couldn't be mounted, there were errors in the logs about not being able to get permissions, and it crashes after a few minutes. I think this is something permission-related, though what I don't know yet. Maybe the root filesystem hasn't been created correctly. Oh well, that's to be figured out for the next week. Still happy about the speed :)
[Android Software/Hacking General [Developers Only]] sykopompos:
Code auroa forums has a open source version of opencore

Btw you have a pm
[Android Software/Hacking General [Developers Only]] unixbob:
could do with some advice on why my build is failing

when I run choosecombo I get the following error:

Before I go trawling through reams of docs and files, is this something basic more experienced builders recognise?
[Android Software/Hacking General [Developers Only]] stragulus:
Looks like something went wrong fetching the git repos. Looking at INSTALL.txt it says:

cd ~/src/mydroid/device
git clone git@github.com:stragulus/Flytouch-2-Device-Config.git
mv Flytouch-2-Device-Config gome

If you already had a dir called 'gome', it would have moved the checkout into gome, but it should be renamed to gome instead. So before you do the mv, just delete any existing gome (shouldn't be there, unless you had checked one out before)
[Android Software/Hacking General [Developers Only]] unixbob:
I've got all of your instructions in the INSTALL.TXT in 3 separate shell scripts so the commands are correct. Tried removing the gome directories and now it can't find flytouch2 as a build target (after running the git clone). I'll go do some more reading. there's something fundamental I'm missing. I just wondered if I was coming accross a known "gotcha" but I think I need to develop a better understanding of the build process and what the repo sync and subsequent git clone is doing to files.
[Android Software/Hacking General [Developers Only]] stragulus:
Yeah, I'm not sure what repo sync will do, I'm afraid the way I switch individual repo's might not work at all with repo. There may be a better way to setup the build system in this regard. I think for now you'll have to manually update the repo's that originate from github, and leave the rest alone altogether.

If you, or anyone else, have a suggestion to do integrate this with repo so it can be a single repo sync, let me know and I'll work that in.
[Android Software/Hacking General [Developers Only]] sykopompos:
Git clone the android platform_manifest then edit the default.xml and git commit your changes on the different repos to pull from and then you can give out the manifest to pull with repo sync and update. If you need help with it just let me know, it is quite easy but extremely frustrating to figure out at first
[Android Software/Hacking General [Developers Only]] wahliow:
Latest firmware for the Flytouch II

link to

http://www.slatedroid.com/index.php?topic=15457.msg126417#msg126417

the links posted below

Burntool

http://www.mediafire.com/download.php?3572bd7zfjo0r0y

Firmware version 2.1-update1 v1.9:#2852 for the Flytouch II

http://www.mediafire.com/download.php?3bkklw36b1414nd

Please use them at your own risk.:) cheers
[Android Software/Hacking General [Developers Only]] modjuh:
Anyone tested this firmware?

What is better? Notice any changes?
[Android Software/Hacking General [Developers Only]] stragulus:
Alright I'll let you know! It will be a couple of days before I'll have play time again.
[Android Software/Hacking General [Developers Only]] l33tlinuxh4x0r:
I am attempting to flash. I think that it might not be working thought because it said board undetected however it appeared to flash correctly. I am now up and it appears that I was right that it did NOT flash. The version number is the same... I'm about to flash a sdcard and see if i can flash that way.

Still no luck... Anyone have any luck flashing this new firmware??

EDIT: flashing instructions... Flash the u0 first then reboot your device will run a 2 minute test. After that it will still be wowpad. Next flash like the instructions instruct. you should now get a very stock android boot screen. That is where I am currently... I will let you know when it boots. First boot takes a while as always.

This is also the most responsive rom that I have used so far. You may have to reflash the U0 to get the camera to work. I flashed 0V2655

One more thing... I was considering getting rid of my tablet due to lag and uselessness but now after flashing this rom I am gonna keep it and use it more. Just my 2 cents letting you know how much batter this rom is.
[Android Software/Hacking General [Developers Only]] l33tlinuxh4x0r:
z4root does not work in this latest rom as you can not enable usb debugging (at least I can't figure out how... I think that they removed it) :(
[Android Software/Hacking General [Developers Only]] wahliow:
With universal root v1.6.1, it shows your device is rooted. Than I use Root Explorer.

Not sure, what is USB debugging is all about.

Have you tried the WEB TV, quite cool.

Market is working but I prefer AppBrain.

wow at least someone tried it and is happy with it.
[Android Software/Hacking General [Developers Only]] ripper1:
Hello can you use disk imager to flash this rom . Never had any luck with burn tool
[Android Software/Hacking General [Developers Only]] l33tlinuxh4x0r:
Once you flash U0 you can flash from sdcard but you need U0 first :( Also you need to make the sdcard with burn tool but the good news is that it is a new version of burn tool.

EDIT: anyone have any ideas on how to extract the ius file so that we can grab the img files from it?