#!/bin/bash
sudo rm -r evolution-ews ; git clone http://git.gnome.org/browse/evolution-ews -b gnome-3-2
sed '/\-Wall/ a \
\t-Wno-error=deprecated-declarations \
\t-Wno-missing-field-initializers' evolution-ews/configure.ac |
sed '/AC_SUBST(SOUP_CFLAGS)/ i \
AC_CHECK_LIB(gthread-2.0, g_thread_init)' >evolution-ews/configure.ac.new
mv evolution-ews/configure.ac.new evolution-ews/configure.ac
cd evolution-ews

./autogen.sh --prefix=/usr --disable-maintainer-mode
sudo checkinstall --pkgname=evolution-ews --pkgversion=3.2 --pkgrelease=git -requires `evolution \(\>\= 3.2\), evolution \(\<\<3.3\)` && sudo mv *.deb ..
cd ..

To overcome this limitation I dug in deep to see how the keyboard is managed under Android, figure out the most elegant solution,  and implement it on my device.

Please note, that this only works on Honeycomb and Icecream Sandwich, as the previously used binary format has been changed! You need a rooted device, terminal emulator, a utf map and file explorer with text editing capabilities and some Linux knowledge.

Keymaps are stored under system/usr and are made up of 3 parts,
Idc specifies which Keymaps and keyboard layout the specific USB device uses, this can be reused to apply the same configuration to several different devices, note the special Generic.idc and Virtual.idc these denote the generic fallback devices that are used when no matching descriptor is found. Device matching is performed from the specifics to the generic. So for each usb device first the vendor+ product+ version is searched, then the vendor+ product combo is searched, then the generic and the virtual falls back. The idc contains the types of device, so it can be used to map any external device like controllers as pointing device, not just keyboards.

Once you identify the USB I’d of your device (i used some application, but it’s far easier to just issue an lsusb command from a terminal.) you can go ahead and create your own descriptor from the generic ones provided. As far as I’ve seen you don’t have to create the idc unless you want to reuse an already existing keylayout. I created mine just in case. As my device’s USB Id is 0e8f:0040 the file I created was named Vendor_0e8f_Product_0040.idc I modified the references in it to use my own layout and character map (keychar) files.

Keychars are basically nothing more than simple keycode to name maps. I’ve stickers with the generic here at first, but soon it turned out my arrow keys are mapped differently, so I actually had to make some minor adjustments here.

Key layouts are the final part of this puzzle. They specify the behavior of the key names when used with the various modifiers. Since I didn’t intend to create a full Hungarian mapping, but only provide a simply way of entering the accented characters in decided to map the special characters to their respective positions with the Alt / Shift+ Alt for capitals. This involved the utf-8 table I mentioned above, which I used to identify the required character codes with.

To test the results you just disconnect / reconnect the keyboard and the new layout is loaded automatically.

It snowing now, so I just have to stop typing, cause the keyboard is all set. If anyone is interested Inn more details drop a comment so I can touch the article up,

It happened after changing my expired password, I tried to sudo with my old one and tallied out after 5 attempts. I couldn’t unlock it even after the timeout has long expired. I’ve changed my password and still couldn’t sudo.

It took me a while to figure out that I was an idiot. The key (literally) was the ssh connection I used. Since it used the certificate to identify myself to the server my login didn’t (and shouldn’t)  reset the tally count. As the ssh session has tallied out it didn’t expire.

The simple solution was to log out and reconnect with password authentication.

Note to self, password change or login through webmin didn’t reset the password tally either.

Disclaimer
This package is provided as-is. It worked for me, but I take no responsibility whatsoever on it’s effects on your device!

IT MAY AS WELL BRICK YOUR DEVICE, OR YOU MIGHT LOOSE ALL YOUR DATA!

Do not use it for any other ROM but the official ZT280_E7_1n_C71_Android4.0_0104_V1.2.rar! It might work, or screw you up
altogether.

(!!! You’ve been warned !!!)

About

This update will install the su binaries and SuperUser application on your
ZT-280.

This is NOT a rom, it’s only a supplement to root the ICS. If your device doesn’t use the ZT280_E7_1n_C71_Android4.0_0104_V1.2.rar ROM, you must install that separately.

This update is written so the root can be applied AFTER the ROM upgrade, in order to add the root capability without screwing up the actual data and applications already on the tablet.

Usage

• MAKE SURE YOUR SD CARD DOES NOT CONTAIN THE “zt-update” FOLDER. If it does just remove it.

• Extract the contents of this archive in the root of your SD card.

• Move the kernel and ramdisk for your device from the appropiate folder (1n or 1f) to the zt-update folder. If you want to use it with any other ROM than the ZT280_E7_1n_C71_Android4.0_0104_V1.2.rar YOU MUST use the kernel and the ramdisk from the newer version. (see disclaimer!)

• Insert card and reboot the tablet keeping the Vol- pressed (ie. do a   standard update)

li>Update will finish with an error, that it cannot find the system, but   NO WORRIES
! this issue is fixed in the updated version

• Reboot and enjoy root!

Licencing and price

I accept but don’t require donations. Nah, really, it’s just a hack.

The package is available here: ZT280_E7_1n_C71_Android4.0_0104_V1.2-root

Almost a third of our codebase consists of POJOs generated from Xsd descriptors scattered around in our projects. The generation is performed during build, using a Maven plugin that performs the parsing and generation tasks.

These generated classes are no more than simple value objects descending from a common root object, that contains some well-known methods like toString (), that all methods should share. Unfortunately this particular toString does not know about it’s descendants’ inner structure, so it relies heavily on reflection to perform it’s task. This springs the idea of generating the classes with their own toString methods, so the resulting code is more efficient.

To do this to be backwards compatible, I would have to generate all known xsds, invoke their old and generated toString implementation and compare the results. Also I’d have to fill these objects with values, so I’d have data to compare.

So much for the task, but what’s the fuss about? Well I want the testing kept inside Maven, so should the generated or  inherited code change, we can see it in the build process.

There seem to exist a vast number of ways to be used for mojo testing, starting from the blunt get a mojo instance, fill it with values, and run execute (), to running a separate Maven instance and use the generated test results. Given that in this particular case I’d to start the compiler and then the surefire I (eventually ) went for the later approach.

The plugin testing harness is an example of the earlier approach, while it seems from the usage example the former. Avoid if you have to invoke more, than just your own mojo. It only reads the pom.xml you provide, but doesn’t set up the required Maven environment like builders, project, …etc. It doesn’t do the setup of the default values of your mojo (not that it could resolve the non-existing values for that) So all you end up with is using a helper method for setting up your mojos and executing them from your testcase. I went as far as generating and compiling my classes, but when it came to the point of actually testing them with a surefire mojo I gave up on it, as setting that up would really have been impossible.

I then realized that from testing point of view it is in fact an integration test, not a “mere” unit test, as the testing involves interaction with third party plugins (compiler and surefire) as well. So I converted the package from the plugin testing harness’s structure to the maven-invoker plugin’s recommended structure.  It was nothing more than moving a few directories around, but I could simply throw the complicated mojo invocation out and use a well defined and simple pom instead.  This plugin creates a local repository for itself that contains your project’s dependencies and the artifact to be tested. It’s advised to create a settings.xml that points to your local repository, to limit the unnecessary fetching from your repositories. 

So far, so good. You should keep in mind however, the invoker plugin has some disadvantages. It’s way slower than the harness. It doesn’t aggregate the test results, so all you can see on a failed build, that there were errors in a particular run. Also, since it runs the test in a separate Java environment, you cannot debug your test code, which in my case is quite complex.

So you either create a separate test module and refer to it from the test pom, and create a unit test to test your code with known data, or just be brave write well thought out code and do it properly using log messages to trace your work, just like the good old times. After all repeated failure builds character. 

I actually created a small and a full test environment, testing the particularities of the test separately. To debug the test code you’ve got to import the generated Maven project in your IDE and start the test execution with the local repository and the generated settings.xml.

What were the results? I achieved a speedup of about 90% for completely empty classes, about 70% for classes with data, when the output buffer is limited, and around 30% for classes recursively and completely filled in a depth of four iterations. Overall I could say it’s a 50% improvement on the original method, with a proven backwards compatibility. Considering that this is invoked at least 6 million times a day it might bring a favorable impact on the performance of our systems.

In the process I found 3 errors in the current code, that proved that the output of method’s not used to heavily in the live system. Since the logging it produces is mandatory for regulatory compliance it might just be a good idea to roll it out in the near future.

Know I’m typing on my brand new ZT-280  I received today.
I can’t say I’m impressed, the tablet is about half the size of the Superpad and is also smaller than the wm8650. The capacitive screen is a bit hectic or oversensitive. It has no haptic feedback, but I can live with that.

It’s exterior is superb compared to the previous mentions, and is bordering on acceptable. I don’t like the reddish metal finish on the sides too much, but it’s not all that bad. I can’t understand the mini USB connectors really. After all micro sockets are taking over, don’t they? Also I don’t get why a separate power input is needed, when it could use the 5v straight from the port. As far as I’m concerned it should have two micro USB and scrap the rest.

The tablet came with the connector cables for both pc to tablet and external device to tablet connection, a power adapter and the usual EU socket adapter. It has a little deep socket for the micro sd card, but it’s reasonable, as I don’t want to change it too frequently anyway.

And so I used the pad for a day or so with the following issues.

The touch is a bit laggy, there are times, when the strength registers a “click ” at a previous position. I seems like a driver issue and I don’t think it would be dealt with anytime soon.

The firmware is definitely based on cyanogen 7 so it promise a relatively long usability period. Unfortunately it doesn’t use clockwork boot loader, and has a legacy package format too. It still begs the question weather it can be used to do incremental upgrades, or only full updates are possible. The supplier released new firmware packs about monthly, and I can only hope they keep it up for the release of the icecream sandwich of cyanogen.

Now again, I’m kind of late on publishing, so here’s an update. A new release is available from the manufacturer ‘s site as of November 4th. I only did a partial update, so a new kernel is running on the pad. This seems to have resolved the touch issues. I’ve also recalibrated the battery, so now it provides a little bit more reliable info. This doesn’t solve the standard charge  issue of the pad. That only affects the charge level display so it only shows the range between 97% (uncharged) to 100% fully charged.  I don’t mind, as I leave office charge overnight anyway.

It does have a five point touch screen which looks nice in Fruit ninja, that I used to test 3d, where I could use 5 blades to slice through tons of fruit in seconds.

I really miss the light sensor. It boggles my mind trying to understand what made the designers think to omit such a cheap, but vital component from this otherwise well built tablet? It also shows that Android heavily relies on its existence. There is only a very limited possibility of customizing it properly, even with the notorious Cyanogen. One cannot set the actual levels to use in the power applet or the status bar, you can only select some predefined level combinations, all of which contain an auto option, despite the missing sensor.

Rooting the device is pretty simple. Connect with the provided cable, remount system with adb, copy su and superuser.apk cynosure the su and done. You can than use all rooted applications. This is required if you want to clean up the crappy preinstalled applications.

Chainfire works out of the box but I’m not a gamer, so I have no idea what’s the point. I did some fooling Around in Fruit Ninja and Angry Birds but I can’t tell the difference.

I wrote this article on the subway, using my ZTE Blade as a Wi-Fi hotspot to publish it.

After spending hours on the net looking for a solution I came over a Swedish forum, which gave away the solution.

1. Reboot the box, either by power cycling or from the remote
2. Press the Menu on the remote when the boot starts
3. Change the output to the resolution your TV can do
4. save and reboot

This was an accident waiting to happen. The length of the charger cord was a concern since the beginning. It was so short, that having an extension cord on the floor I could hardly put it on my lap on my sofa, without accidentally yanking it out altogether. So it didn’t have a safe place. It fell several times, but without any visible results. The battery or the power socket might have loosened as a result, but as I read it on several sites, it might have just been the poor manufacturing.

After the 40cm drop the corner of the touch screen over the LCD shattered. The unit still works, but barely. I’ve tested the screen with a drawing program, and it turns out the shattered section is “untouchable”. So about half of the screen is working the rest is deformed. This and the severe battery problems encountered recently (the charger shows 100%, but when I take it off it turns of in less than a minute, or lasts 4 hours depending it’s mood) render it useless.

So I decided to get a better tablet, with possibly better build quality, more internal memory, and preferably stronger CPU. I’ve decided to double the stakes and get get something under US$200. I spent over 6 hours searching through the vast amount of tablets available at http://dhgate.com and several other wholesale suppliers.

Most offers were bogus, the name and the make of the table sometimes doesn’t match the description of the item, several items are listed multiple times, under the same name and price. Whenever I tried to search for brands I ended up with results for MID7 and lookalikes (WM8550 and WM8650 series processors with 7″,8″or 10″ resistive displays) These things you can get as low as $90, and as high as $200 (at the high end of my range ) Countless times I thought I found something good then it turned out it’s an overpriced MID.

After lots of searching I ended up with this. The EM73. It features a Telechips 8803 Cortex-A8 1GHZ CPU,  512M DDR RAM with a 4GB internal storage (of which I presume 1G is reserved for the OS only), it comes with Android 2.3 pre-installed. It has a promising 3400mA battery. It supposedly has a mali GPU, so some games might even run on it.  It has some features I will not use for sure, like the ethernet adapter, 2M camera, HDMI output (seriously, who really expects HDMI from a device with 800×480 resolution?) It has no built-in 3G, GPS, Bluetooth, but I don’t care much about those anyway, it’s meant to be a couch tablet.

At the time of writing it costs US $164.32 apiece, with free shipping.

Based on the XDA developer forums, I should be able to mod it anyway I like, should I feel inclined to.

Based on my previous order, it should be delivered around August, so expect some follow up then!

Any suggestions on what to do with the broken one? I don’t feel like throwing it in the bin as is.

I was not surprised to receive it in three weeks time, even though it had 30 working days to arrive.

It came in a rather unimpressing package, with my name and address printed on a piece of paper torn on the edges, affixed with liberal amounts of tape.

The box is just plain white with a very low quality picture of the device. It is called MID (this week probably) but it’s one of those cheap things you get rebranded under several aliases.

The tablet feels plastic, and quite heavy. The rear cover feels empty and hollow. The buttons on the sides are quite small. The painted arrow on thevback button on the front panel scratched off in mere hours! Well, one can’t expect to get a Galaxy Tab for this money.

As it came with the Chinese market and complete lack of Google apps, I decided to flash it as soon as possible. It took 4 hours after receiving it, that I just killed the original firmware and replaced it with a version of the Uberoid release found here.

After the upgrade, and the market fix described on the page, the device suddenly  became more interesting. The icons seem to be oversized on the market, and so are several icons on the screen resulting in a broken feeling. I really want to change the icon packs back, as the “Honeycomb theme” makes me puke.

Titanium backup does not seem to work on the rooted device, so I guess I’ll have to live without. The image comes with a so far unknown AppMonster to do it’s job. I’ve replaced ADW Launcher, and Prolauncher that came in the image with the GO Launcher Ex, I use on my ZTE. As it turns out it is faster on this piece as well.

It will still take some time for me to see if it was a sensible idea to get it or not.

Update

The resistive display is very unresponsive, but it might be because of the capacitive display of my phone. Talking of which, the cheap ZTE Blade is far superior to this tablet in both manufacturing and performance wise. There’s a significant lack of responsiveness on the display edges caused by the ignorant design.
I forgot to mention, that there was a stylus included in the box, that is very obviously designed for a mobile phone, there is no place to stick it in the tablet however. The power supply comes with an attachable European socket adapter, but with a cord no longer than 50 cm.
I’ve reverted the ROM to the Vestinous 1.3 release, that’s not infested with the Honeycomb wannabe theme,now the icon sizes are normal, and I can still see the market. The performance is still tragic, it should be able to run at 800MHz but feels less, maybe it’s just the limited memory.
I’ve later updated to the more stable Singularity ROM.

I got bored of the old theme, and decided to finally change the looks of the site, but since I want themes to be changeable, I could not let the old fashioned theme spoil my plugin.

I’ve gathered a few manuals and rewritten the plugin as a widget using the guides found here and here, and found the 21st comment of the later article useful, explaining why the widget cannot be simply registered.

The whole thing didn’t take more than half an hour to put together. I’m not sure the initialization code is optimal, or works at all, as data was already in my DB. So if anything goes south, just leave a comment, so I can fix it.

To use the widget, you can supply the widget title on the admin interface, other than that you can add the ‘bofh’ style to your CSS, and customize it’s appearance.

.bofh {
...
}

If you are interested the plug-in is available here.