Latest product reviews
ARCHOS 50 Diamond
ARCHOS GamePad2
ARCHOS
Smartphones
ARCHOS
TV Connect
ARCHOS 101 XS

A A A
Avatar

Please consider registering
Guest

Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Register Lost password?

ClockworkMod (CWM) Recovery easy install for RK3066 and RK3188 -- TWRP/CWM Flash-Tool and root for RK3288

 Please donate to support OMA and CrewRKTablets firmware work, thank you !

sp_Feed sp_TopicIcon
Updating TrekStor Ventos 10.1 (ST10216-2A) to Android 4.4?
Any way to update this device to a more recent ROM/kernel/Android version?
Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
46
2015/02/21 - 01:51
sp_Permalink sp_Print sp_EditHistory

Hello Oma and Jochen,

thanks again for your help! There is good news to share:

I have now succeeded in building a 3.0.36+ kernel which boots fine:

Linux version 3.0.36+ (android@android-build) (gcc version 4.4.7 (Ubuntu/Linaro 4.4.7-1ubuntu2) ) #1 SMP PREEMPT Sat Feb 21 01:06:20 CET 2015

My merged preliminary kernel config file for the Ventos (ST10216-2A) as well as dmesg and catlog log files with this "my" kernel are included below for your reference.

This new kernel makes better use of the Ventos display, although still in portrait mode. Touchscreen, WLAN and Bluetooth are not yet functional, most probably because they are either accessing devices for which the device nodes below /dev are not yet existing, or still using wrong drivers (such as WLAN, which - maybe due to CONFIG_RKWIFI=y - still states that it were to detect MK903 although MT5931 is included in the Ventos).

So it looks like now the tedious task of finding the right device drivers is the next step...

More to follow, but probably Sunday night at the earliest... Wink

Best regards,

awl

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1378
47
2015/02/21 - 09:09
sp_Permalink sp_Print

For justification, this is Genio:

Odys Genio 7", 1024*600 (16:9) aka PiPo P793 aka PiPo S3

Specs:
- Screen: Samsung LMS700JF04-0
- Touchcontroller: VTL ct36x
- Wifi/BT: RK903 = module, based on BCM40183 Chipset, which main chip is the BCM4330
- Audio: RTL5631
- Sensor: MMA7660 (daemon MMA8452)
- Keypad: Power = 116, Vol+ = 115, Vol- = 114
- Akku capacity: 3000 mAh
- Cams: sp0838 front, sp2518 rear
- HDMI: RK30
- Clock: TPS65910

Your dmesg shows:

<4>[    1.227264] ct360_ts_init

<6>[    1.227476] stk831x_probe: driver version:1.5.5
<6>[    1.227494] STK831x_Init: Initialize stk8312
<6>[    1.228912] input: accelerometer as /devices/virtual/input/input1
<6>[    1.229121] stk831x_probe successfully
<4>[    1.229259] i2c-core: driver [gs_mma7660] using legacy suspend method

<4>[   26.709800] Current WiFi chip is RK903.

Touch support is clearly kernel.

Sensor support is in first instance kernel. Aditionally there may be a problem with the daemon (nameing conventions).
If Android gets an event, then we can manage orientation by the sensor HAL in the build.

The wifi driver is in the build and gets loaded by Android (libhardware_legacy). KK sources for MT5931 are not available, so best would be we switch to a build which includes the complete MT5931 footprint: http://crewrktablets.arctablet.com/?p=2736

Use boot, recovery and system from that pack. And yes, a rk31 build will boot on a rk30board with a 3.0.36+ kernel.

- Oma -

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
48
2015/02/22 - 23:26
sp_Permalink sp_Print

Hello again,

unfortunately, no progress, but rather the opposite - much worse than before:

Any attempt to boot into the "Oma_RK31_Chuwi_V88_KK_4.4.2_v2.3_gen1 loader" system.img from http://crewrktablets.arctablet.com/?p=2736 with my custom kernel build always hangs bfore I am able to connect with adb.

So I reverted to the "Oma_RK30_Pipo_S1s_KK_4.4_v1.0", but for an unknown reason, using the exact same kernel.img that I used before when it successfully booted into KK 4.4 (just newly flashed after the failed 4.4.2 attempt), now this custom kernel still boots, but the system cannot mount any partitions any more: even the root partition is read-only. I am able to connect with adb ("adb properly devices" lists the device), but "adb shell" returns:

c:\adb>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -

c:\adb>adb push testfile /system
failed to copy 'testfile' to '/system/testfile': Read-only file system

c:\adb>adb push testfile /
failed to copy 'testfile' to '/testfile': Read-only file system

so I can neither have a look at dmesg output nor logcat. Confused

I have even tried to Erase IDB, restore the stock 4.1.1 system with RKBatchTool (which worked fine) and then freshly flash the Pipo S1s 4.4 build again including Erase IDB, but to no avail: All partitions/file systems are still consistently read-only...!?

What the heck has happened now? Why did this work before I tried the Chuwi 4.4.2 build?

Do you have any ideas? Could that be a SELinux type of issue?

I am at my wits' end and think of abandoning the idea of trying to update this tablet...

Many thanks for any feedback, ideas and pointers about what might have happened all of a sudden after I was already able to boot into my custom kernel... Cry

Best regards,

awl

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
49
2015/02/22 - 23:48
sp_Permalink sp_Print sp_EditHistory

Almost forgot: Here's some more detailed hardware information - to the best of my knowledge:

Trekstor Ventos 10.1 ST10216-2A

Specs:
- Screen: AU Optronics B101EW05 1280x800 (or 1200x800)
- Touchcontroller: Goodix GT92x (CONFIG_TOUCHSCREEN_GT92X_IIC=y)
- Power Management: AXP152
- Wifi/BT: MT5931/MT6622
- Audio: ES8323
- Sensor: AL3006 Digital Light+Proximity Sensor, AK8975 Orientation Sensor
- Cameras: GC2035 (front and back), 2MP each
- HDMI: RK30
- Clock: HYM8563
- DMA Controller: PL330


Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
50
2015/02/23 - 19:37
sp_Permalink sp_Print sp_EditHistory

Hello again,

just did some more experimentation, and I have one more request to you:

It turns out that your stock kernel as included in Oma_RK30_Pipo_S1s_KK_4.4_v1.0

Linux version 3.0.36+ (root@alex-System-Product-Name) (gcc version 4.4.3 (GCC) ) #2 SMP PREEMPT Tue Jun 4 18:16:21 CST 2013

still boots fine on my tablet ("adb shell" works fine), while all my new kernel compile attempts based on the configuration of Odys Genio:

https://crewrktablets.arctablet.com:8081/crewrktablets/rk3x_kernel_3-0-36/blob/wip/genio/arch/arm/configs/odys_genio_defconfig

do show the unfortunate behaviour that "adb shell" does no longer work:

exec '/system/bin/sh' failed: No such file or directory (2)

So what I would like to do now is to compare (with kernel tool "diffconfig") the kernel configurations of the above kernel from the Pipo S1 KK 4.0 build and the below Odys Genio kernel:

There must be a difference between these two that causes the second Genio-based kernel to boot, but to be unable to properly access even the root filesystem in read-write mode and subsequently mount /system.

So can you please provide a link to the kernel config file that has been used for "Oma_RK30_Pipo_S1s_KK_4.4_v1.0"?

Many thanks & best regards,

awl

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
51
2015/02/25 - 10:13
sp_Permalink sp_Print

Hello Oma, Jochen, All,

hmm - no replies so far... Frown

Would it help to donate another 10 EUR in order to motivate you to dig up the old "Oma_RK30_Pipo_S1s_KK_4.4_v1.0" kernel configuration? Or should I simply forget about the idea of updating this tablet to anything more recent than stock 4.1.1?

Thanks in advance for a short feedback!

awl

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
52
2015/02/28 - 12:14
sp_Permalink sp_Print

Bump - anybody able to help!?

Thanks & best regards,

awl

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1378
53
2015/03/01 - 09:11
sp_Permalink sp_Print

As said before, the Pipo S1s kernel is a stock binary for which we do not have a kernel config. Sorry about that.

- Oma -

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
54
2015/03/01 - 11:29
sp_Permalink sp_Print

Hello Oma,

thanks for the unfortunate confirmation...

And you don't have any assumptions or ideas regarding what difference in the kernel configuration might be the culprit why a kernel might boot fine, but then "hang" somehow in the boot process such that the root filesystem does not get monted read-write and therefore /system filesystem cannot be monted at all, such that adb service is running, but the attempt to run adb shell just shows:

exec '/system/bin/sh' failed: No such file or directory (2)

(due to the fact that / is read-only and /system therefore cannot be mounted).

Many thanks one more time & have a nice Sunday!

awl

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1378
55
2015/03/01 - 11:52
sp_Permalink sp_Print

Unfortunately not. To get debug info a serial adapter is helpful.

- Oma -

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
56
2015/03/01 - 16:03
sp_Permalink sp_Print

Hello again,

one more major riddle seems resolved: It finally turned out that it is the compiler/toolchain version that seems to make all the difference:

Using this (cross) compiler, for "some" kernel config combinations (not generally, but only for some - but I'm not going to investigate further!!!), I get the "hanging" boot, unable to mount root filesystem in read-write:

arm-linux-gnueabihf-gcc-4.8 (Ubuntu/Linaro 4.8.2-16ubuntu4) 4.8.2

while using this one, it boots fine, such that I can connect using "adb shell":

arm-linux-gnueabihf-gcc-4.4 (Ubuntu/Linaro 4.4.7-1ubuntu2) 4.4.7

This is just unbelievablly sad - I have wasted several hours now only to finally detect that there seems to be a subtle bug in Ubuntu's gcc 4.8 toolchain that indeed affects my kernel compilations... Arrgh! Yell

So I should be back shortly with more questions regarding device drivers (Wifi/Bluetooth)... Wink

For now, I have concentrated on getting CM 10.1 to run fine first (which seems easier because I can use my existing 3.0.8+ kernel source), before I might then switch back to try a KitKat build and kernes 3.0.36+...

Best regards,

awl

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
57
2015/03/01 - 17:35
sp_Permalink sp_Print

OK, on we go... Wink

In order to get rid of the following in dmesg output:

mt5931: exports duplicate symbol rockchip_wifi_exit_module (owned by kernel)

I have compiled a kernel without statically linked mt5931 driver, and rather built a module from it. Now this error is gone, and rather:

Current WiFi chip is MT5931.

as well as a successfully loaded mt5931.ko module:

mt5931 324613 0 - Live 0x00000000

But still WiFi does not work, and I now have these in logcat output:

I/WifiService(  431): WifiService starting up with Wi-Fi enabled
D/WifiService(  431): setWifiEnabled: true pid=431, uid=1000
D/WifiHW  (  431): Read wifi chip type OK ! wifi_chip_type = MT5931
D/WifiHW  (  431): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/mt5931.ko, DRIVER_MODULE_ARG =
E/WifiStateMachine(  431): Failed to reload STA firmware java.lang.IllegalStateException: command '3 softap fwreload wlan0 STA' failed with '400 3 Softap operation failed (No such file or directory)'
E/WifiStateMachine(  431): Unable to change interface settings: java.lang.IllegalStateException: command '5 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 5 Failed to set address (No such device)'
I/PowerWidget(  647): Button list: toggleWifi|toggleBluetooth|toggleGPS|toggleSound
I/QuickSettingsController(  647): Tiles list: toggleUser|toggleBrightness|toggleSettings|toggleWifi|toggleMobileData|toggleBattery|toggleAirplane|toggleBluetooth
I/PowerWidget(  647): Button list: toggleWifi|toggleBluetooth|toggleGPS|toggleSound
E/WifiHW  (  431): Supplicant not running, cannot connect

Note that I neither have a /dev/wlan0 so far (who is responsible for creating this? init.rc code?), nor does the firmware file seem to be found - although I have successfully applied the model fix, which has successfully put it into /system/etc/firmware/WIFI_RAM_CODE.

So how do I move on from here?

Thanks a million!

awl

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
58
2015/03/02 - 22:10
sp_Permalink sp_Print

Update: It seems that I need to find a way for CM 10.1 to insmod TWO kernel modules: first mt5931.ko, and only then, wlan.ko. Unfortunately so far, CM 10.1 on boot only does an automated insmod for mt5931.ko, but not wlan.ko. Also, the order is important: wlan.ko can only be loaded after mt5931.ko is already loaded.

If I insmod wlan.ko manually after mt5931.ko is already active, I then get these new lines in dmesg:

<4>[   63.165081] =======================================================
<4>[   63.171467] ==== Launching Wi-Fi driver! (Powered by Rockchip) ====
<4>[   63.177876] =======================================================
<4>[   63.184508] MT5931 SDIO WiFi driver (Powered by Rockchip,Ver 2.07) init.
<4>[   63.191201] initWlan
<4>[   63.193383] ## Calling platform_driver_register
<4>[   63.198004] ## wifi_probe
<4>[   63.200622] wifi_set_power = 1
<6>[   63.203717] rk29sdk_wifi_power: 1
<6>[   63.407457] wifi turn on power
<4>[   63.410507] wifi_set_carddetect = 1
<6>[   63.414008] rk29sdk_wifi_set_carddetect:1
<6>[   63.418102] mmc1: slot status change detected(0-1)
<6>[   63.422923] rk29_sdmmc_change_clk_div..1945..  newDiv=42, newCLK=294Khz [sdio]
<4>[   63.430516] wl_android_wifictrl_func_add success.
<6>[   63.623669]
<6>[   63.623680] drivers/mmc/core/core.c...1827..  ===== mmc_rescan Begin....[mmc1]
<6>[   63.667735]
<6>[   63.667746] mmc_attach_sdio..800..  ===== Begin to identify card as SDIO-card. [mmc1]
<6>[   63.705684] rk29_sdmmc_change_clk_div..1945..  newDiv=0, newCLK=24750Khz [sdio]
<6>[   63.715898] mmc1: new high speed SDIO card at address 0001
<4>[   63.723701] wireless_dev prWdev(0xe6841600) allocated
<4>[   63.728913] wiphy (0xec580120) allocated
<4>[   63.732929] net_device prDev(0xeca4a800) allocated
<4>[   63.740030] Open FW image: WIFI_RAM_CODE done
<4>[   63.753978] Allocating 4096 bytes for COMMON MGMT MEMORY POOL.
<4>[   63.759900] Virtual Address = f8c99000 for COMMON MGMT MEMORY POOL.
<4>[   63.766269] Allocating 11136 bytes for SW_RFB_T.
<4>[   63.770917] Virtual Address = f8c9b000 for SW_RFB_T.
<4>[   63.775891] Allocating 13312 bytes for MSDU_INFO_T.
<4>[   63.780813] Virtual Address = f8c9f000 for MSDU_INFO_T.
<4>[   63.786712] gwl =-==============> sdio_writel retry 1!
<4>[   63.803605] gwl =-==============> sdio_writel retry 2!
<4>[   64.109283] Using embedded MAC address[wifi] wlan%d netif_carrier_off
<4>[   64.117735] tx_thread starts running...
<4>[   64.125999] MAC address: 00:e6:08:00:80:79*********wlan_early_suspend************
<4>[   64.144199] *********wlanEarlySuspend************
<4>[   64.149066] ip is not avaliable.
<6>[   64.152401] mmc_rescan_try_freq..1678..  ===== Initialize SDIO successfully. [mmc1]

and netcfg now finds a wlan0 interface, but it is not yet configured:

root@android:/ # netcfg
netcfg
lo       UP                                   127.0.0.1/8   0x00000049 00:00:00:00:00:00
sit0     DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00
ip6tnl0  DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00
wlan0    DOWN                                   0.0.0.0/0   0x00001002 00:e6:08:00:80:79

So what can I do to make this happen automatically on boot?

Does it make any sense to try and copy the libhardware_legacy.so from my stock 4.1.1 to the CM 10.1 install?

Thanks again for your kind help!

awl

Avatar
awl
Regular Member
Forum Posts: 90
Member Since:
2015/02/11
sp_UserOfflineSmall Offline

Thanks Received: 1
59
2015/03/02 - 22:25
sp_Permalink sp_Print sp_EditHistory

After netcfg shows a "wlan0" device, I tried to start wpa_supplicant (the version we copied from the stock 4.1.1 ROM) from the command line:

root@android:/ # wpa_supplicant -Dwext -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf

which results in this in logcat:

E/wpa_supplicant( 1547): wlan0: Unsupported driver 'wext'

So I tried again with:

root@android:/ # wpa_supplicant -Dnl80211 -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf

which seemed to get wpa_supplicant up and running once I had created a directory "/data/misc/wpa_supplicant" mentioned in my /data/misc/wifi/wpa_supplicant.conf (copied from my stock ROM).

I am now looking for a way to get the automated "WifiHW" process start wpa_supplicant using these parameters: Am I correct looking into modifying init.rk30board.rc in boot.img now?

Thanks again,

awl

Avatar
ri9000

Contributor
Forum Posts: 29
Member Since:
2014/09/07
sp_UserOfflineSmall Offline

Thanks Received: 7
60
2015/03/03 - 10:22
sp_Permalink sp_Print

the original modules are probably insmod /system/lib/modules/xxx.ko 

from init.rc , early on just after the partitions are mounted.

..assuming they don't run a service called "readahead" to do it.

I have been following your efforts with much interest...don't give up now!!

best regards.

Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online: eugeniom
264 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (91), Phone (174)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

mikado71

ibrokavali

eugeniom

leroro35

Q3253

Felis

Forum Stats:

Groups: 10

Forums: 185

Topics: 6037

Posts: 60500

 

Member Stats:

Guest Posters: 43

Members: 262194

Moderators: 5

Admins: 1

Administrators: admin

Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech


CrewRKTablets moderators: JochenKauz and Astralix