yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] YetAnotherForumUser:
I won't do that either, at least not while there still are other things to try.

Things I've tried as well:

writing changed configuration data to /sys/devices/i2c-0/0-0055/ctpconfig

without documentation it is more or less guesswork as to what these data mean. Thusfar I've succeeded in making the digitizer stop working many times (but fortunately it comes back to life after a reboot) but otherwise I've not noticed any difference whatsoever.

I'm digging through the amlogic source code to see whether it is possible to change the panel refresh frequency. It would be better to change the digitzer refresh, but from the limited amount of info I found about the GT801 it seems to have a fixed refresh frequency of 60 Hz, unlike its successors which do allow variable refresh rates. Maybe they learnt a lesson?

Things I still want to try:

if we're lucky the interference comes into the GT801 through the analog ground or power connections. It might be possible to improve these.

... any ideas?

If nothing else works, I'll rewrite the goodix_touch driver, add some filtering code, compile it as a module, unbind the built-in driver and load that module. Theoretically this should work. A puritan might complain about having filtering code in kernel space, but it is much easier to maintain a single driver than a whole host of different Android distributions.

Even further along the line of daydreams lies the idea to port the essential bits from the amlogic kernel to a more recent kernel, especially now that parts of the Android patch set have been merged in the 3.3 series. That will take time though, and time is precious.
[Miscellaneous Android Development] $$pasquale:
Could someone (or together!) try to ask the kernel to Ainol?

Persuade them that it would be good publicity...

By license should do it, shouldn't?
[Miscellaneous Android Development] MrRimmer:
People have tried but they don't respond. Chinese companies are not too worried about complying with licence terms...
[Miscellaneous Android Development] kinterinho:
I have a Chinese friend who is a provider of Ainol, maybe he can do me the favor of asking the kernel. But that is exactly what you have to ask?
[Miscellaneous Android Development] MrRimmer:
It can do no harm to ask them. The latest official kernel source I can find is here but as you can see this is over a year old.

Someone grabbed a later copy and put it here.

We have no patches or other code from Ainol, as far as I know.
[Miscellaneous Android Development] YetAnotherForumUser:
Amlogic openlinux code still 'officially' available

Amlogic have not taken down their source code, it is still there on the 'openlinux' wiki, just follow the Download links to the most recent (2011-12-20) GPL code release bits. They have more stuff on there, have a look around.

Of course this is Amlogic code, not Ainol code. It is Linux code, not Android code. Then again, to fix many of the problems we have with these tablets, and to fix them for other tablets than Ainol's, Linux code is just what we need. It also helps in getting other types of Linux-based operating systems running on these tablets.
[Miscellaneous Android Development] MrRimmer:
Indeed, it is Ainol that is the problem, not AMlogic. Without the work that Ainol did to get it working on their hardware it is going to be hard going getting other kernel versions (3.3.x) to work or to do things like solve the touchscreen jitter issues.
[Miscellaneous Android Development] daniel.eriksson:
its awesome to see guys like yourself owning an ainol novo 8 pad!

i mean professionals with insights of the kernel.

To tell a noob, why is there a huge difference in android 2.3 and ics? when it comes to the pad support.

Only that the driver isnt complete or something?
[Miscellaneous Android Development] hillbeast:
A while back I started a project of getting the Amlogic kernel to work on our tablet.

Currently this is what I can tell isn't working:

* Touchscreen

* Trackball

* MTD (NAND)

Maybe someone with more time on their hands can work on it.

The touchscreen and trackball don't work because the IRQs are all messed up or something. It receives data for the trackball and thinks it's a touchscreen and it just comes up with errors.

And I haven't booted Android on it because I have no NAND. I suppose I could boot an image from the SD card as that works nicely.

https://github.com/hillbeast/Kyorakernel
[Miscellaneous Android Development] urkelz:
guys i charged tablet to 100% then let it go standby. Now i'm trying to start it and it doesn't power on. It looks like its dead. No vibration when i press power no nothing. any ideas?

never mind found reset button :D
[Miscellaneous Android Development] nurdyn:
Dear psquare,

thanks for your lovely ROM on ICS 4.0.3.

I really like it and has made some mod on build.prop and my 3G MODEM AND ETHERNET workingv smoothly.

I would like to share my modification
[Miscellaneous Android Development] $$pasquale:
I would like to share your modification, nurdyn :)
[Miscellaneous Android Development] xd_1771:
So is this seriously so bug-free that you want to push it to Ainol? :D

I'm going to flash it tomorrow now that my Novo 8 is back in service :o (shattered touch screen prevented me from using it the past few)
[Miscellaneous Android Development] MrRimmer:
I'm not so sure it's that safe! There are still many glitches to be sorted out, and I have gone back to Cheeyee 2.3.4 (again) as that is by far the most stable version.

On the other hand, 4.0.3 is the way to go and I'm sure it will come good eventually.
[Miscellaneous Android Development] popos1:
ICS ainol novo 8

how to install gapps, becouse i can't do that?
[Miscellaneous Android Development] xd_1771:
I see, looks like some powerpack options are still separated due to instability.

I'm a bit confused as to how to install Clockworkmod?
[Miscellaneous Android Development] hillbeast:
The only issues I have with it are the lack of USB mode (that will be figured out shortly and not a big deal really), and the poor kernel handling of the SD card which sometimes requires you to remove the SD card after waking up the tablet and putting it back in.
[Miscellaneous Android Development] MrRimmer:
In addition to the above, I have lack of working Bluetooth and an unspecified instability (I seemed to need to reboot the tablet quite often). But it is very close.
[Miscellaneous Android Development] hillbeast:
Is this instability caused by the SD card, or is it something else?
[Miscellaneous Android Development] xd_1771:
Who else is getting a laggy Angry Bids experience? It shouldn't be like this at all. Quite jittery.

Other animations appear smooth. High quality Google Earth is smooth.
[Miscellaneous Android Development] daniel.eriksson:
ICS 4.0.4 Released today! contains correct touchscreen drivers?? :)
[Miscellaneous Android Development] WWeltmeister:
Browsing one of the sony xperia forums I came across this (http://xdaforums.com/showthread.php?t=1570374) thread.

I was feeling lucky and tried the settings on my novo. Maybe it is the lucky feeling, but I actually think the jitter is almost gone and the touchscreen is more responsive.

Then again, I don't have much knowledge about the settings I've changed, so maybe there's little effect.

Hmm, second opinion. Selecting an app or widget is still a pain in the arse. Jitterjitterjitter. I do think it's a bit more responsive though
[Miscellaneous Android Development] hillbeast:
Of course not. It'll be bugfixes.
[Miscellaneous Android Development] cheeyee:
I have this idea to implement a userspace program that would grab exclusive access to the Goodix Touchscreen. And then create a uinput device that minics the touchscreen. In this userspace program we would read the touch inputs from Goodix TS apply the dejiter filters and then send events through the uinput device.

This should be a workaround the problem not able to modify the kernel goodix driver.

Here is the what the program with do.

call ioctl(fd_goodix_ts, EVIOCGRAB, &grab);

create uinput device

read events from goodix_ts

apply filter on ts coord.

send filtered events to uinput device.

The userspace program will be started in init.rc before starting android.

Do you think this will work?
[Miscellaneous Android Development] $$pasquale:
powerpack rc2 released. please test bluetooth and report!
[Miscellaneous Android Development] xd_1771:
I noticed something about the touch screen jitter.

For me it only happens when the device is charging. When unplugged, there is no jitter.

I do, however, have a replacement touch screen (i.e. not the original) installed.
[Miscellaneous Android Development] Hgshgs:
Hi cheeyee, according to this atmel whitepaper, I guess should work. http://www.atmel.com/Images/maXTouch_S_Series_whitepaper.pdf

The basic difference is that you are filtering in userspace. I guess this could be the ultimate solution not only to Novo 8 jitter problems, but any other "closed kernel" tablet with high jitter. It will drain resources from system and maybe can affect responssiveness, but this could be tamed modifying parameters for battery operation / wall charge operation, just like you did in your 2.3.4 ROM.

Looks like goodix driver in this kernel is very poor implemented, and Ainol AC charger is bad.

---------- Post added at 09:45 AM ---------- Previous post was at 09:30 AM ----------

Hi, Did you change (increase) the gap between your touchscreen and tft when you changed your touchscreen?
[Miscellaneous Android Development] cheeyee:
Thx YetAnotherForumUser for providing the method to mod the kernel. My method was just a workaround if kernel couldn't be modded.

With this I'll try to add some filtering code to the driver.

Thx again for the great work.

Update: I have been studying the output of the co-ordinates and found that we need to apply variance also to the co-ordinates to remove the sudden spikes. That will help the averaging to be more smooth. I'm making changes to InputReader.cpp since it is easier for me that way.

Update2: I've implemented variance + averaging in 2.3.4 ROM and it's useless without a good sample size to remove jitter. For me I need at least sample size of 10 before results start to show. Unfortunately the bigger the sample, the responsiveness of the Move action decline. Therefore the sample size needs to be adjustable by user. If you need "Move" action to be more responsive when you play games like Fruit Ninja then decrease the sample size. If you need "Accuracy" when you play games like Angry Birds, then increase the sample size.
[Miscellaneous Android Development] xd_1771:
It is possible that the gap increased. I read that interference may be the cause of this problem. It may be interface from the 9V power feed that corrupts this and regardless.

EDIT: Is anyone else getting intermittent wi-fi disconnection? For me it happens after the screen is off for a period of time (adatper shuts off?). I have to reboot to be able to connect to anything again, after wake-up.
[Miscellaneous Android Development] YetAnotherForumUser:
Another option would be to make sample size dependent on movement speed. The faster the detected (average) movement, the shorter the sample queue. Since every touch event starts with an empty queue, this should provide a workable alternative provided that the variance filter is capable of getting rid of the spikes. For slow movements the queue can be allowed to build up to a given maximum. If faster movements are detected the queue can be shortened.

As said this scheme stands or falls with the quality of the input. If there are two or three samples which jitter in the same direction the filter would have to assume a fast move, otherwise response time will suffer. Goodix claims the GT801 provides a fixed sample rate of 60 Hz, in practice I seem to get around 66 samples per second (leading to the question whether it is run at to high a clock rate...?). To test sample rate:

# getevent -t /dev/input/event5|grep '0003 0035' > /sdcard/events
[I]...let this run for a few seconds while holding finger to the screen, then stop it with CTRL-C[/I]
# grep $(cat /sdcard/events|cut -d '-' -f 1|uniq|tail -2|head -1) /sdcard/events |wc|awk '{print $1}'
[B]66[/B]
[Miscellaneous Android Development] :
original beta

Can you please repost the original betas? One of the betas you posted worked better. THANKS!
[Miscellaneous Android Development] YetAnotherForumUser:
A picture says more than a thousand words: jitter charted

Both series: finger held in place on tablet, events recorded using getevent, app. 66 samples/second. Raw sensor data, no filtering.

Blue (column A): charger and USB connected, battery empty.

Red (column B): USB connected, battery empty, tablet running off USB power (yes, it can do that).

Will make more of these once the battery is full.

--- edited ---

The battery was full so I did some more experiments. The second chart shows:

Blue (column A): battery charged, charger and USB connected

Red (column B): battery charged, USB connected

Orange (column C): battery charged, tablet not physically connected to any external device

Judging by these charts there is no clear relation between the jitter level and the presence or absence of the charger.

The lowest jitter was observed with an empty battery while the device was powered through USB - interesting?
[Miscellaneous Android Development] cheeyee:
Hi YetAnotherForumUser,

When I tried to compile goodix driver as a module I got the following error. You know what is wrong?

ERROR: "lookup_symbol_address" [drivers/amlogic/input/touch_screen/goodix_touch.ko] undefined!
[Miscellaneous Android Development] urkelz:
When I click the microphone icon on top left of screen to use voice search it gives me a error. How can I fix this? I installed GAPPS for cyanogenmod9. Did many wipes and reinstall of custom firmware too but same result.
[Miscellaneous Android Development] YetAnotherForumUser:
lookup_symbol_address is defined in symsearch.h (through a macro) and exported from symsearch.ko.

Did you configure symsearch to be built as a module? Is the include directive for symsearch.h (#include "../../../misc/symsearch/symsearch.h") in goodix_touch.c correct? If your kernel tree looks different from mine you might have to adjust this path.

UPDATE:

Check the Makefile under symsearch, I forgot to include symsearch there when I packed up the tarball:

Last line in drivers/misc/Makefile should read:

obj-m += symsearch/

If it is missing, include it.

A new tarball, with this Makefile included, is attached to this message.
[Miscellaneous Android Development] buggatti:
Hey Guys

i have the rc3 and i tried to flash the powerpack rc2 but it say installation aborted
[Miscellaneous Android Development] Liqourish:
RC3 rom works great, but makes games that were playable on 2.3.4 very slow like the samarai vengeagence (btw coudnt get past the main screen but was jittery)

youtube app doesnt work, but it does a heelluva job on the browser!:D

lookin forward for more improvments

thanks

---------- Post added at 06:40 PM ---------- Previous post was at 05:44 PM ----------

merimobiles claims to have ICS from ainol.....i emailed them for it, hopefully they will respond

www merimobiles.com/Ainol_NOVO_8_ICS_4_0_3_8GB_Cortex_A9_HDMI_8_0_inch_p/meri0647.htm

read the comments
[Miscellaneous Android Development] $$pasquale:
I don't trust. Also, the price is high...
[Miscellaneous Android Development] mrbender666:
Hi,

is this custom rom working also on zt-280 c91 upgrade ?

maybe this is a stupid question , but seems the hw is almost similar.....

thank you
[Miscellaneous Android Development] MrRimmer:
Price seems OK, but I have not found ICS on Ainol website for Novo 8 so I would also be suspicious.

What we really need is a bug-free kernel to solve problem of SD card rejection after coming out of standby and to use the settings from 2.3.4 touchscreen driver (which does not seem to suffer from jitter).
[Miscellaneous Android Development] urkelz:
Yeah. I used Cheeyee's firmware and the touchscreen was very good and responsive. If that could be put in psquare's custom firmware for ICS would be great.

I also mailed merimobiles for the firmware but I think it's not OEM firmware or they made mistake.
[Miscellaneous Android Development] MrRimmer:
Perhaps they got it from this thread!
[Miscellaneous Android Development] daniel.eriksson:
Link removed.

cant i delete posts here?
[Miscellaneous Android Development] xxGMTxx:
Source confirmed its the TFT

Hello guys. I can confirm the TFT panel as the source of the Jitter.

I dismantled the backlight, the TFT panel and the Touch panel. Using 2mm of spacing between Touch panel and TFT panel the jitter is gone completely.

I'm trying to post a video in youtube to show it.
[Miscellaneous Android Development] buggatti:
Hey

i emailed merimobiles for the ics on novo 8 and they have send me a link to the file

here is the link

http://115.com/file/e7w1vjr9
[Miscellaneous Android Development] h055:
I can confirm that the above link Novo8_ICS4.0.3_W13_sHAOgE_V1.3 is not official ROM but an adaptation from the works in this thread by a self-proclaimed newbie. It was based on Ramos W13 instead of Ramos W6HD which aimed at solving the touch screen jitters. Refer bbs.imp3.net/thread-10581430-1-1.html

I recalled that it was mentioned sometime ago in this thread with Google translated introduction.

It seems that merimobiles' staff are not so keeping up themselves with the latest development in forums.
[Miscellaneous Android Development] YetAnotherForumUser:
How's that post going along, and can you show us the results of the following command after your modification (hold one finger stationary on the screen and capture the output):

getevent -t /dev/input/event5|grep '0003 0035'

Since increasing the gap between the screen and the digitizer means the shell won't fit the device any more I wonder if there is a better solution. I sent off a message to a supplier of ITO PET film to see what they'd say about using said material to shield the TFT panel. The minimum order quantity for this film is enough to pave the average urban vegetable plot, but they told me I could order a sample of two standard size sheets, 457mm x 595mm, for ₤50 each. Given that these tablets go for around ₤99 each that is rather steep, depending on how many tablets can be fixed using one sheet. The representative guessed 6 to 8 tablets, leading to a material cost of around ₤6-£8. Still rather steep, especially given the fact that those prices don't include shipping etc. Still, if it would work it might be worth it.

Of course ITO PET film is just one of the potential shielding materials. In principle any conductive, transparent, thin material should work. Maybe car window film would work as well? If it sparkles in the microwave it is conductive, and it is transparent.

Any more ideas on this subject?
[Miscellaneous Android Development] $$pasquale:
New version online.

2.0 RC1

please test bluetooth!

Touchscreen is more comfortable but less responsive.

bye
[Miscellaneous Android Development] xd_1771:
I'm having trouble with the wi-fi connection. I keep getting "avoided poor internet connection" on my home wi-fi connection (next to router) and elsewhere. I'm curious whether it's a fault of the ROM? But not much has changed on my tablet. The last time I used it for wi-fi was at UBC for a major conference and everything worked fine. Gets to obtaining IP address and no further. I will try again after the new ROM though. It seems the signal suddenly dies (goes to 1 bar) when attempting to connect.
[Miscellaneous Android Development] $$pasquale:
wifi works fine
[Miscellaneous Android Development] YetAnotherForumUser:
That looks promising...

A company called LLumar made something called 'signal defense film', a plastic film to be stuck to windows to block EM transmissions. I sent around a few messages to see whether this stuff is available, it should be a bit less expensive than ITO PET film (or not... it was made for 'the government and defence market' after all...)
[Miscellaneous Android Development] xd_1771:
To RC2 from RC1.... is there a need to do a full wipe?

By the way: Same problem as this - I'll reflash and work on my router when I get home. Happens at my school too though.
[Miscellaneous Android Development] cheeyee:
Here's my crack at the touch screen jitter filter in driver code. Just basically took what I implemented in 2.3.4 ROM and modified goodix_average method.

Here is what is does.

1. Applies averaging filter only when finger is not moving or moving slowly. Filtering is ignore when moving quickly. The threshold for quick move distance is 75.

2. By default it uses the last 15 coords to calculate average. This can be changed by writing the sample size into /sys/bus/i2c/devices/0-0055/avgsample. Min=3, Max=30. If you write anything else it will default to 15.

3. Averaging filter does not include the pressure in calculating the average x,y coords.

4. Averaging algorithm does not need to loop all coords to total up in every call to goodix_average.

http://dl.dropbox.com/u/69619046/goodix_driver_mod.tar.gz
[Miscellaneous Android Development] Hgshgs:
The biggest problem for me is that a lot of apps that try to access internet like Zinio, Youtube, etc don´t work, at least with 1.0 RC2. I´m using 2.3.5 and wouldn't like to reinstall everything just to see if Zinio works. Could someone that installed ICS 2.0RC1 please test if Zinio is working? Is there any fix for those issues?

Ramos released W19, it´s another AML8627-M3 tablet with ICS 1024x600 7" screen 512mb RAM. This could be another good firmware to use.
[Miscellaneous Android Development] cheeyee:
Here is my second shot at the dejitter code.

I've tested on 2.3.4. It performs well to quick and slow movement and also dejitter is at approx +-3 points when finger is not moving in most areas of the screen.

To use this in ICS, we may need to unbind and insmod in init.rc

http://dl.dropbox.com/u/69619046/goodix_driver_mod_v2.tar.gz
[Miscellaneous Android Development] xd_1771:
Reflashing the ROM fixed that.... reflashing again to try RC2 now

By the way, when I "Clear cache" in recovery (still stock recovery) the tablet enters boot loop upon next reboot and does not work again until I reflash the ROM. Just a warning, guys, if you're trying to troubleshoot. Perhaps CyanogenMod fixes it, but I do not have CyanogenMod installed at the moment (not sure how actually).