|Latest product reviews|
After several weeks of reading through the forums i decided to give a try to compiling a kernel for the Aoson M12 (the 512Mb version) and got some encouraging results - wifi, sound, battery (most of the time - sometimes it can get "out of sync" if the charger is plugged when the tablet is switched off), touchscreen are now working. I still have some issues which I cannot solve by myself and the following is my experience:
1) First of all I started with the AN9G2 as the base config and started changing modules for the hardware elements. I have very little programming knowledge, so I mostly tweaked and experimented with the config menu, read through some of the code to try and understand some logic, compiled, and then see what works on my tablet.
2) Rotation does not work, Androsensor reports "waiting for event" and dmesg reports
<4>[ 3.049764] mma8452 devid:0
<6>[ 3.053324] mma8452: invalid devid
<4>[ 3.056798] mma8452_probe error -834342208
<4>[ 3.061126] gs_mma8452: probe of 0-001a-1 failed with error -1
3) My tablet has 2 cameras, a front GC0308 and a back GT2005. Setting FCAM or GC0308 in config results in a working front cam (only). The only way I get the back cam to work (although mirrored) is by setting GT2005 (only) in the config. Setting GT2005back or BCAM in the config will make neither front nor back cam work.
4) Leaving the board type as OdysQ (like the AN9G2 config) leaves a bit more than 235Mb ram but changing the board type to a NeoX leaves quite some more precious ram - 295Mb
5) I experimented with some more aggressive (lower) values in board-odys-neox.c for PMEM_GPU_SIZE/UI/VPU sizes and actually noticed this would leave even much more ram. Tablet still booted and behaved normally (actually a bit smoother) and I could not notice any deterioration in graphics from normal usage - can you recommend some tests that could be run to verify this?
6) Physical Buttons are not all mapped correctly on my tablet (Power button works ok, but back is mistaken as "menu" and menu is not even detected). I don't know if this helps but CWM's testkey gives the following results: Under GB CWM the Power button is 116, Back is 158, Menu is 59, while under the 4.2.2 CWM the Power button is 116, Back is 59, Menu is nil.
I would appreciate any help please and can provide dmesg logs (for the old kernel when I was still running GB and also for the new trial one). I am attaching the config I came up with so that other users will be able to use it or experiment even if it is not perfect.
Thanks a lot and please keep up the good work - these tablets are working like new with your help
Great. Which build do you use?
Here we had another try on the M12 kernel ... long ago, but maybe useful.
- Oma -
The following users say thank you to Oma7144 for this useful post:drums
Made some progress.. both cams are now working together, and am getting excellent performance with dmesg reporting 379MB memory and still good 1080 video playback on a 512MB tablet .. i can now also play PVZ2 How can I share changes with you?
Last challenge is rotation and i'm confused.. MMA8452 probe still fails and out of despair i tried compiling with MMA7660 driver instead. I noticed there are different versions and the one ending 'lastversionJK2' actually produces "mma7660 probe ok" in dmesg, but Androsensor still shows no events and continues to say it's an MMA8452Q. Any ideas will be appreciated please!! thanks a lot.
PS: Attaching dmesg from my old GB rom (working rotation) and the new kernel with cm10.1.
if you want to share, use github.
Don't be confused with the mma, the gsensor is often faked, like on NEO X8. Never trust the things that are reported from Android.
If mma7660 probes ok, then it could be a problem in the daemon name. Look at the driver there should be a corresponding name like mma8452_daemon. Depending on the libsensor.so of Android you could try gsensor_daemon.
If you upload your source to github I could have a look at it.
The following users say thank you to JochenKauz for this useful post:drums, admin
Thanks to your valuable advice to not trust the things reported in Android now I did some more progress and nearly solved..
So MMA7660 continued not working and after getting some debugging printed I found other messages saying there was no good probe after all. So I put my attention back to MMA8452 from basics and the problem seems to be a different way this tablet is set up (or rather not set up) to get a succesful probe.. I think it should not be difficult to fix now though I'll be busy for the next few days.
So many thanks and I hope to share soon so that another tablet will be fully working
OK... so I uploaded the mods to a fork on github at https://github.com/drums173/android_kernel_odys_neox_3.0.8 and it works fine now including rotation! Added long-press shortcuts to the buttons with volume-controls, and some other possible tweaks.
One small thing.. after booting i'm seeing just a couple of lines in dmesg at around 39 seconds saying: "_AllocateMemory fail! pool=6->9, Bytes=16384, Type=4". Googling only came up with http://pastebin.com/JnQMYUYe which seems more serious and I have no idea what the context for that user was. As far as I can see everything still works fine, but I can't trace where the msg is coming up from and tried with various memory settings (GPU from 128-32Mb, UI 64-40, VPU 64-40) but it keeps coming up.
Am testing some other small modifications to the battery power_on capacity check since if I leave the tablet charging when switched off, unplug, and then power up, the capacity will remain stuck at the old_capacity value instead of new_capacity. I haven't committed anything there yet.
Please feel free to test, review and adopt any changes too and if the CrewRK team wishes to put the compiled kernel on the CrewRK website. Thanks above all to CrewRK for making this possible!
The following users say thank you to drums for this useful post:admin, Oma7144, JochenKauz
glad to see that it worked!
I merged your fork into our repo on github and added your device to our build script(https://github.com/crewrktablets/android_kernel_odys_neox_3.0.8/commits/master). I also updated our custom kernel thread (http://crewrktablets.arctablet.com/?p=2575) with my build version of your kernel. If you want to give the kernel a try, I would be glad to hear from you.
Regarding the _AllocateMemory fail! error:
Does it happen also before your optimisation of the RAM?
I grepped the code and was not able to locate a partial string.
The following users say thank you to JochenKauz for this useful post:drums
I merged your change into our repo and updated the kernel page. Please try again.
If the kernel does not work, please sync our repo and build it on your own and try that kernel then.
The following users say thank you to JochenKauz for this useful post:drums
Yes the newly built kernel now works fine - I downloaded from your kernel page crewrktablets_kernel_308_aoson_M12v512MB_201409281532_JB422.7z and it boots great..
As to your question about the _AllocateMemory fail! error, yes it occured even before the optimisations. It doesn't seem to be a major problem in practice, but I am attaching logs from the new kernel and also I found a much older log from the GB kernel.
Thanks a lot!
Hello to all the community.
Firstly thank you for the great work you are doing.
I have a "AOSON M19" I tested the kernel from the M12 and unfortunately does not work well after the first reboot.
I do not know if it would be very difficult to adapt to the M19.
It would be very good news to have a "custom kernel" of the M19 supports zram
Thank you and congratulations again
Apparently there are quite some differences between the M12 and M19. But earlier this year another user asked about the M19 in this thread: http://www.arctablet.com/blog/forum/crewrktablets-rk2918-entwicklung-customroms-development-croms/which-build-and-kernel-for-an-aoson-m19/
You could find it useful. But follow the warning in the thread and be careful about making a brick!
Most Users Ever Online: 749
Currently Browsing this Page:
Devices in use: Desktop (62), Phone (9), Tablet (1)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech