yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] redrubberpenguin:
Okay good to know; thanks. I'll be patient.
[AT&T, Rogers HTC One X, Telstra One XL] lincolnw:
I wouldn't worry about it. Mine turns off anywhere from 5 to 15%. The battery percentage is just an estimate based on the software, it's not an actual indicator. As such there are tons of variables that can affect when the phone is actually out of battery.
[AT&T, Rogers HTC One X, Telstra One XL] mbh87:
TWRP also doesnt report battery correctly and it has nothing to do with the stats. It is taking more of an educated guess as to where it's at. Believe it has something to do with are phones.
[AT&T, Rogers HTC One X, Telstra One XL] henry_gale:
thanks for the info.. i have experienced this issue also
[AT&T, Rogers HTC One X, Telstra One XL] c5satellite2:
Battery percentage is guessed at based on voltage. As the battery drains, voltage decreases slightly. Yes it is an educated guess. Every battery behaves slightly differently and has a unique profile or discharge curve. Some may be steeper than others at the end, but the device should learn this and adjust accordingly. An internal short in a composite battery like this would also exhibit this behavior, only exhibiting itself at certain voltage levels(dependant on location of physical short in battery) where voltage drops to 0 at that moment. I have seen this issue in defective packs where they work fine most of the time, but then zero all of a sudden. I'm not saying this is your problem, but the case design/new soft shell battery(no hard plastic shell to protect against the internal layers from being squeezed together) is wide open to physical damage from the phone being compressed.

Try a stock ROM and verify it works normally. If not, the battery is damaged.

My One X has never shut off before it reached 1%. I unlocked it 4 days after getting it in the beginning of June and have been running CR ever since and never had a steep battery decline.
[Miscellaneous Android Development] vurrut:
CyanogenMod is free, community built, the distribution of aftermarket firmware Android 4.1.2 (Jelly Bean), which is designed to increase performance and reliability in the stock Android for your device.

# include <std_disclaimer.h>
/ *
*
* Not responsible for bricks devices, SD cards dead
* Thermonuclear war, or be fired because of the alarm application failed. Please
* Do some research, if you have any questions about the features included in this ROM
* Before flashing it! You are choosing to make these changes, and if
* You point the finger at me for spoiling the device, I will laugh at you.
* /

CyanogenMod is based on the Android Open Source Project with additional contributions from many people within the Android community. Can be used without any need for any Google software installed. Linked below is a package that has come from another Android project to restore parts of Google. CyanogenMod are still included various hardware-specific code, which is also gradually open source anyway.

All source code is available CyanogenMod Github repository CyanogenMod. And if you would like to contribute to CyanogenMod, please visit our Gerrit code review. You can also see the Changelog for a complete list of updates and features.

Instructions:

The first time you use CyanogenMod 10 on the device or from another ROM?

1-Install ClockworkMod recovery. The instructions are available in the second post .

2-Make a backup nandroid your current ROM. (in the Backup and recovery >> restore >> backup)

3-Format the partition of data and cache device. (in the recovery >> Wipe data / factory reset

4-CyanogenMod to flash (Install zip from sdcard, CM10-(fversion)-UNOFICIAL-rk2918.zip)

5-Optional: Install the Google Apps package addon. (Install zip from sdcard gapps-jb-date-signed.zip)

Upgrading from an earlier version of CyanogenMod 10

Make a backup nandroid your current ROM.

CyanogenMod flash (Google Apps will be a backup and restore automatically).

problems

Experience issues? Please provide the following information to our bug tracker:

If the device was difficult to start the system, please provide the file "/ proc / last_kmsg".

If the device was a soft reset, or "bootlooping", please run a Logcat and provide maximum power.

Please use Pastebin when possible.

Download Links:

CyanogenMod 10:

Latest version: 10_alpha [23/10]

Download: http://www.wuala.com/vurrut/recursos Vurrut/Rockchip/cm-10-20121023-UNOFFICIAL-rk2918.zip/

GoogleApps (supplement):

*Version: gapps-jb

Mirror: http://tinyw.in/poPq

Sources:

https://github.com/organizations/CM9-Pascal2 (Branch jb)

https://github.com/CyanogenMod

Moldels tested:

Bq Pascal 2 (rk2918 7", 1gb ram)

Bq Kepler 2 (rk2918 8", 1gb ram)
[Miscellaneous Android Development] vurrut:
Not working:

-Chrome. Working on it

Minor faults:

Problems with overlay (wallpapper aspect, laucher, dimensions ...)

Not tested (HMDI)

Changelog:

23/10/2012

-First build

-

Installation Instructions for vurrut ClockworkMod recovery(non touch):

For Rktools (windows):

1-Download and extract the file on the desktop recovery_RKtool_winV2.zip.

2-Turn the tablet in any way jtag, (-) and insert the usb.

3-Run the RK29update.exe (should appear under "device connected", if not, repeat step 2)

4-Turn the tablet and turn into recovery mode ((-) and (power)).

Restore to the previous ROM:

1-Reboot in the Recovery.

2-Backup and Restore >> Restore.

3-You choose the date of restoration (if you miss several).
[Miscellaneous Android Development] Oma7144:
Great work again, vurrut!

However, ro.sf.lcd_density=100 is a bit to small for grandmothers ;)

Could you pls compile tablet UI (android.policy.jar, services.jar) for 160 dpi?

Many thanks in advance!

- Oma -
[Miscellaneous Android Development] vurrut:
Dont work with a other dpi.is the major bug.Working on it.

Any ideas?
[Miscellaneous Android Development] Oma7144:
Yes. You will find code here: http://xdaforums.com/showthread.php?t=1780970

- Oma -
[Miscellaneous Android Development] Mardon:
Changed dpi to 120 works.

Gesendet von meinem PASCAL2 mit Tapatalk 2
[Miscellaneous Android Development] Oma7144:
Don't solve the issue. Everything above 120 dpi will give you phone UI.

- Oma -
[Miscellaneous Android Development] Mardon:
Yeah but better than 100 :D

@vurrut

cm filemanager also works.

Gesendet von meinem PASCAL2 mit Tapatalk 2
[Miscellaneous Android Development] Oma7144:
@vurrut:

Current problems, to do:

- Sensor (sensors.rk29board.so)

- Kamera (camera.rk29board.so)

- Stock Browser webGL (libwebcore.so)

Attached sensors.rk29board.so rotates my Loox, but unfortunately 90° wrong. The lib is from your CM9 build, so that should be a easy one.

Attached camera.rk29board.so is from Joaquime's CM10 project and correct the cam, but unfortunately there is a problem to adress the sd drive.

Adressing the cd drive might be a generic problem too.

Problem with WebGL (libwebcore.so) can be solved by enabling CPU upload path in webkit. ChristianTroy did so. Sources are here.

- Oma -
[Miscellaneous Android Development] Mardon:
@vurrut

Chrome is not working in your cm10 build.

View attachment 1478855

Gesendet von meinem PASCAL2 mit Tapatalk 2
[Miscellaneous Android Development] lmemperador:
thanks a lot Vurrut
[Miscellaneous Android Development] Oma7144:
You will need this big baby (lib).

http://www11.zippyshare.com/v/95381649/file.html

- Oma -
[Miscellaneous Android Development] Mardon:
Not working.

Now chrome just force close

Edit: uninstalled chrome wiped all chrome things with sdmaid, reinstalled chrome from market and now it works :thumbup:

Gesendet von meinem Neo-X8@cm10
[Miscellaneous Android Development] whunter:
Airpad

Hi,

Is it possible to use it in the Airpad based on RK2918 ?

Tks:confused:
[Miscellaneous Android Development] Oma7144:
Got the cam working for everything except the ordinary cam ...

The aspect ratio(640x480/10000x10000) is bigger than 2 !

[ 3417 D/hw_jpeg_encode ] RUN INTO JPEGENCDOER.
[ 1630: 3417 E/hw_jpeg_encode ] encodethumb, open /dev/rk29-ipp fail!
[ 1630: 3417 D/ ] JpegEncRelease#
[ 1630: 3417 D/ ] JpegEncRelease: ERROR null argument
[ 1630: 3417 D/hw_jpeg_encode ] JPEGENCDOER: JpegEncRelease fail with : 0
[ 1630: 3417 D/hw_jpeg_encode ] RUN OUT JPEGENCDOER. jpeg len : 0
[ 1630: 3417 E/CameraHal_Util ] hw_jpeg_encode Failed

... any ideas?

- Oma -
[Miscellaneous Android Development] justclimb:
Hallo Oma!

Can you PLEASE post the sensor files of your latest CM10 build?

Thanks in advance.

PD: unless you make a cwm flasheable zip, I can't taste your ROMs, as my laptop is broken...:crying:
[Miscellaneous Android Development] Oma7144:
I don't understand, the sensors.rk29board.so is attached to post #9.

- Oma -
[Miscellaneous Android Development] maverikdj:
hello this rom can work on Mediacom Smart Pad 815i? Specifications are:8.0" Touchscreen; CPU Cortex A8 1 GHz; RAM 512MB DDRIII; OS: Android 4.0 - Ice Cream Sandwich

Internal Memory 4 GB Flash; LCD 8.0" Capacitive Touchscreen Multitouch (800x600 SVGA Standard)
[Miscellaneous Android Development] Oma7144:
Yes, should be.

- Oma -
[Miscellaneous Android Development] Riekr:
this is working great on mediacom 810cex, this is actually the fastest rom i've tried so far

however i've noticed some issue:

- even after flashing libs from post #9 rotation does not work correctly and so camera (i think this is known)

- i can't use the tablet when connected as a mtp device or connect trough adb shell

thanks for your work!
[Miscellaneous Android Development] davduke:
hi all!

I¨m interested to help you to develop a stable version. I have a Aoson M19 based in RK2918. Right now, we have the alpha version from @vurrut and some patches from @Oma7144.

We can try to put everything together in a build and continue working on that dividing problems :).
[Miscellaneous Android Development] anjo88:
is possible to have a oc kernel to this tablet?
[Miscellaneous Android Development] davduke:
I've never heard about that. But could be possible :)
[Miscellaneous Android Development] Riekr:
It's a matter of kernel, cm10 supports it in performance settings if kernel allows overcooking

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Miscellaneous Android Development] Oma7144:
For which tab?

- Oma -
[Miscellaneous Android Development] anjo88:
I ttry to install this rom on my wolder miTab manhattan now don´t boot and can´t revert :( any help?

my tablet is this one
[Miscellaneous Android Development] smoki3:
Ist IT possible to Run this Rom on a RK3066 device?

Gesendet von meinem ODYS-NOON mit Tapatalk 2
[Miscellaneous Android Development] Oma7144:
No.

- Oma -

---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------

Is the kernel still alive (first boot screen)? Do you have the ICS firmware available?

- Oma -
[Miscellaneous Android Development] ck32:
Hello oma,

Do you think this Cm10 ROM will work on my window n90 (cube u9gt2). I am now runing your JB ROM on it and all is OK... Thanks
[Miscellaneous Android Development] Oma7144:
Yes, you can try that. If you like to have tabletUI at 160 dpi check out this.

In both cases you will not have sensor support in laucher (uncheck auto rotate in settings/display).

- Oma -
[Miscellaneous Android Development] vadash:
Hi yesterday I installed this one http://xdaforums.com/showthread.php?t=1734181 and works except for Gsensor and camera, maybe we can achieve 4.1, also im spanish (maybe you too?, beacuse wolder is a spanish company) PM me so we can talk ;)
[Miscellaneous Android Development] Fenisu:
Oma, I've got an Aoson M12 to test anything you want in order to get ICS working. It is frustrsting to have a ICS without touchscreen

:(
[Miscellaneous Android Development] Beatsleigher:
CM itself works like a charm!

The only thing that is bothering me is, when I'm in recovery mode, I cannot mount my SD, and seeming as the GAPPS installation failed, I cannot reinstall :/

I'm driving a 3Q Qoo! Q-Pad RC0710B, with said Rockchip. Hope that helps!

LG familyguy59/Beatsleigher
[Miscellaneous Android Development] CoMiKe:
Hello.

I have an Aoson Wopad M12 and, unfortunately, there has been NO Android 4.0 release for this tablet.

Searching for similar tabs, I found the Arnova 9 G2 was very similar and had an Android 4.0 firmware.

There was nothing to lose, so I flashed it on my M12 and found that everything worked except WiFi. Autorotation was reversed, but I got it fixed by modifying the build.prop file.

I found the problem with WiFi is that the Arnova 9 G2 uses a BCM4319 chip (no bluetooth) and the M12 uses a BCM4329 (WiFi + Bluetooth).

Unfortunately, the chipset driver is compiled against the kernel (and not as a module) in every rom I've checked, so it can't be replaced without the kernel sources (which isn't available on the Arnova website)

I've tested every Android 4 firmware for every existent RK2918, BCM4329 and 9,7" IPS screen ROM, but none worked (most of them won't boot due to screen driver corruption).

To @vurrut and @oma7144, do you think there's any chance to get the WiFi running on the M12 using the Arnova 9 G2 kernel?

Can you give me any clue?
[Miscellaneous Android Development] Oma7144:
No. But maybe we will find an other way.

Have a look to my Kernel Archive. Not all kernel are documented yet, so try all for 9,7" tabs.

Best together with my Jelly Bean Image, which contains drivers for all wifi chips.

- Oma -
[Miscellaneous Android Development] CoMiKe:
I talked too fast.

There's another similar tablet, the Arnova 9 G3. It seems this one uses an RTL8188 WiFi chip.

The good news is that Arnova has released the source code for that tablet, and it even includes the BCM4329 driver in the sources. :)

Let's see what I can do, I never tried to compile anything Android-related, but reading the attached README file, it doesn't seems as hard as I thought:

GPL source code for: A10BG3, A10BG3DT, AN7DG3, AN7DG3ST, AN7DG3ST_CP, AN9G3

to compile the kernel:

1. cd kernel
2. select a device defconfig:

A10BG3: rk29_A10BG3_defconfig
A10BG3DT: rk29_A10BG3DT_defconfig
AN7DG3: rk29_AN7DG3_defconfig
AN7DG3ST: rk29_AN7DG3ST_defconfig
AN7DG3ST_CP: rk29_AN7DG3ST_CP_defconfig
AN9G3: rk29_AN9G3_defconfig

3. make <defconfig> ; make ; make modules

Now I must find where to modify the defconfig of the AN9G3 (or create a new one) to point it to the correct WiFi driver.

---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------

Now, reading your post again I realize that it might work using YOUR Arnova 9 G2 kernel with YOUR Jelly Bean image, isn't it?
[Miscellaneous Android Development] Oma7144:
Using the Jelly Bean Image will give you a good starting point, as it has been rolled out to over 100 different RK2918 tabs.

So try the Image together with kernel from the Archive. Maybe you have luck.

There are also two homebrew kernel, which we can adapt for your tab: Hyundai H900 and Arnova 9G2.

- Oma -
[Miscellaneous Android Development] CoMiKe:
Happy new year!

I flashed your OMA JB system replacing the kernel with your Arnova 9 G2 kernel.

I haven't been able to flash the model fix for the Arnova 9 G2, as I don't have a microSD card and the recovery wasn't able to mount /emmc either.

Anyway, the system booted, touchscreen worked as expected, but WiFi didn't.

ADB didn't work either, so I wasn't able to take a look at the dmesg, although I suppose the kernel was trying to load the BCM4319 driver, which is the oce included.

Let me suggest you to include aLogCat and Terminal APKs on your system images so people is able to take a look at the logs without ADB.

Thank you very much for your help. Reading your post, I realized the reason why my nandroid backups were not restored correctly (due to the flags on the misc partition).

I haven't decided what will be the next step (I've restored my previous ROM as my family need a working tab) :) but I considering modifying and compiling the Arnova ROM to learn how the process works.

Anyway, let me know if you have any other idea to make your system work on the M12.
[Miscellaneous Android Development] Fenisu:
Hi Oma,

I just flashed your JB rom and your Arnova 9 g2 kernel and as CoMiKe said, everything works but WIFI and BT, and USB DEBUG.

I couldn't built the source code that CoMiKe posted with BCM4329 successfully, although I don't know what to do with a zImage file either. I flashed the vanilla Arnova 9 g2 zImage using rkandroidtools, loading only the Kernel, and it didn't even boot.

Any help is appreciated.
[Miscellaneous Android Development] Oma7144:
For adb enable mtp and usb debugging.

@Fenisu: when you have BT then it is a Aoson M12B, right? In this case the Aoson M19 kernel may work.

@CoMikE: flash Technaxx Big Tab and Hyundai H900 Kernel, to see if wifi works. If you don't have touch use a usb mouse.

To flash only a kernel just tick parameter and kernel. When the tab stucks with lights on press reset.

- Oma -
[Miscellaneous Android Development] CoMiKe:
No, M12 uses BCM4329 (Wifi and Bluetooth) and 512MB.

M12B and M19 use BCM4319 (no bluetooth) and 1GB.

Will try to test with your suggested kernels when I have some free time.

---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------

The zImage is the kernel itself, but the boot.img contains the kernel and a ramdisk.

You should unpack the Arnova 9 G2 boot image with abootimg, replace the zImage with the one you compiled, then pack again the boot image and try it on your tab. If it works, let me know!! :)
[Miscellaneous Android Development] Fenisu:
MTP is the default usb setting, and does not work.

Edit: it works now, I had to add the vendor id in the adb_usb.ini like this: http://stackoverflow.com/questions/6484279/detecting-device-for-debugging-adb-does-not-work

and run adb shell with sudo.

M12 as CoMiKe said.

I flashed both of them and here is the results:

Technaxx Big Tab: boot logo screen and freezes.

Hyundai H900: boots, seems to work although no touchscreen, but when I connect a mouse it does not work, or it reboots itself (I tried two different mouses). But what I can see in the screen, the rom becomes a bit laggy but the WIFI ICON is there in the "taskbar".

So, we need in the Arnova 9 kernel, the Hyundai H900 wifi driver.

That's what I did, but my kernel zImage is ~3mb and every kernel.img for this tab is ~7mb, the one I tried is supposed to work.
[Miscellaneous Android Development] CoMiKe:
fenisu, read the last part of my previous post. As I said there, the kernel.img contains the kernel and a ramdisk and you need tools to unpack and repack it again.
[Miscellaneous Android Development] Fenisu:
I thought you meant the boot.img, not the kernel.img.
[Miscellaneous Android Development] CoMiKe:
If I'm not mistaken (and I'm not, I believe :)) boot.img, kernel.img and recovery.img can be unpacked with the abootimg command and contain a kernel and a ramdisk with an initial root filesystem.

I don't know what's the difference between boot.img and kernel.img on our tab, but I believe the kernel used to boot the system is the one inside the boot.img.

Oma7144 will surely confirm us that.
[Miscellaneous Android Development] Fenisu:
boot.img and kernel.img from Oma_Odys_Loox_JB_4.1.1_v1.2.2a.7z give this error. I've been unable to unpack those files.

# abootimg -x boot.img
boot.img: no Android Magic Value
boot.img: not a valid Android Boot Image.
[Miscellaneous Android Development] CoMiKe:
You must try with the Arnova boot.img. Share your compiled zImage with me and I will try to do it, if you want.
[Miscellaneous Android Development] Fenisu:
It seems that the *.img for rk29xx are made in a different way and can't be manipulated with the standard tools.

Here is the zImage of vanilla AN9G3.
[Miscellaneous Android Development] CoMiKe:
Ok, I had only tried with the following Arnova 9 G3 ROM and I thought all worked the same way, sorry. That boot.img can be unpacked with abootimg.

http://www.arctablet.com/blog/featured/arnova-9g3-custom-firmware-google-play-root-face-unlock/

It seems your kernel has most of the drivers compiled as a module and that why it's smaller, in contrast to the original kernel. I'm no expert, but I suppose the modules should have been compiled to a different folder, but I don't know if they should be placed on the initrd (inside the boot.img) or in the system.img.

Another option is trying to statically compile the kernel (I'm not sure if it can be done, I can't help you there).
[Miscellaneous Android Development] Fenisu:
What I could see in the compilation is that there were only 2 modules compiled and none of them were the wifi driver..
[Miscellaneous Android Development] CoMiKe:
Thank's because you had to modify the defconfig of the AN9G3 to include the BCM4329 driver.

Check: kernel/arch/arm/configs/rk29_AN9G3_defconfig

I was doing it now, but it gives an error while compiling the BCM4329 driver. I'm checking it (this ain't gonna be easy). :D

---------- Post added at 02:03 PM ---------- Previous post was at 01:48 PM ----------

Ok, the process is:

make rk29_AN9G3_defconfig

make menuconfig ----> Search for BCM4329 and enable it. This enables some other required drivers.

make

make modules

But it keeps failing when compiling it:

CC drivers/net/wireless/wifi_sys/rkwifi_sys_iface.o
CC drivers/net/wireless/bcm4329/dhd_linux.o
drivers/net/wireless/bcm4329/dhd_linux.c: In function 'rockchip_wifi_exit_module':
drivers/net/wireless/bcm4329/dhd_linux.c:2544: error: implicit declaration of function 'bcm4329_power_save_exit'
drivers/net/wireless/bcm4329/dhd_linux.c: In function 'rockchip_wifi_init_module':
drivers/net/wireless/bcm4329/dhd_linux.c:2615: error: implicit declaration of function 'bcm4329_power_save_init'
make[4]: *** [drivers/net/wireless/bcm4329/dhd_linux.o] Error 1
make[3]: *** [drivers/net/wireless/bcm4329] Error 2
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
[Miscellaneous Android Development] Fenisu:
Here is how I managed to get a successfull compilation:

# diff .config arch/arm/configs/rk29_AN9G3_defconfig
300c300
< CONFIG_WIFI_CONTROL_FUNC=y
---
> # CONFIG_WIFI_CONTROL_FUNC is not set
861d860
< CONFIG_WIRELESS_EXT=y
864d862
< CONFIG_WEXT_PRIV=y
1137,1138c1135,1136
< # CONFIG_WIFI_NONE is not set
< CONFIG_BCM4329=y
---
> CONFIG_WIFI_NONE=y
> # CONFIG_BCM4329 is not set
1579,1580c1577
< CONFIG_BCMA=m
< # CONFIG_BCMA_DEBUG is not set
---
> # CONFIG_BCMA is not set
2440c2437
< CONFIG_BCM_WIMAX=m
---
> # CONFIG_BCM_WIMAX is not set

It can't be compiled as a module.
[Miscellaneous Android Development] CoMiKe:
Yes, I was missing the WIFI_CONTROL_FUNC.

I'm compiling it right now.

Anyway, you can download the Arnova ROM I linked some posts above, replace the kernel on the boot.img and check if it works, if you feel like.

If you do, ckeck first if the stock Arnova 9 G3 kernel works, as I've only tested Arnova 9 G2 ROMs on my tab.

Thanks for your help and sorry if I've said obvious things on previous posts.

Now I see you're far more experienced compiling kernels than I am. In fact, I've never done it before. :)
[Miscellaneous Android Development] Fenisu:
That link needs the user to register and stuff, would you mind mirroring the images somewhere else?

It's ok, I am not that experienced either. I just want this ROM/Kernel rocking on my tablet, that's all. Thanks to you too.

Hopefully Oma will appear sometime and give us a hint. If I am not mistaken, he did compile all those kernels (of his kernel list) so he should be able to compile and repack a new kernel.img easily adding the missing driver.