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
136
2015/04/20 - 18:02
sp_Permalink sp_Print

Hello ri9000,

bad news: I've tried all your suggestions, but they don't make any difference.

The default.prop already sets the ROM config to "mtp,adb", so no issue here.

Also tried to add/change all properties you mentioned in default.prop, but no change...

Frustrated regards,

awl Frown

 

@Oma/Jochen:

Any news?

Avatar
ri9000

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

Thanks Received: 7
137
2015/04/21 - 00:58
sp_Permalink sp_Print sp_EditHistory

Hi Awl, lets see. . so adb shell, adb logcat, all work fine until some point later in the boot process?

1/: If its rom config sometimes you can snag it with : adb shell setprop sys.usb.config adb

or a better way:

# My Postboot service 
service my_postboot  /system/bin/sh  /system/etc/my_postboot.sh
user root
oneshot

on property:init.svc.bootanim=stopped
class_start my_postboot

my_postboot.sh might contain . . sleep 30s, setprop from above etc.

. . (maybe "run-parts" service is already setup?)

2/: If its boot config you need to compare your init.rc, init.hardware.rc to stock boot image to look for an adb conflict.

. . this can take a while. For example I helped fix this same problem with a kitkat/ kernel3.1 port to a tegra 2 tablet

and this setting was the problem. . 

write /sys/module/cpuidle/parameters/lp2_in_idle 1

I'm happy to help out where I can.

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

Thanks Received: 1
138
2015/04/22 - 18:40
sp_Permalink sp_Print sp_EditHistory

Hello ri9000, Jochen and Oma,

I have made some more progress, but it's only bad news: I am now almost 100% sure that what I am observing when my connection to adb hangs with the vold service enabled is a complete kernel hang.Frown

As long as adb is successfully connected, I can both execute commands from a remote adb shell on my PC as well as press hardware buttons (unfortunately, I have not been able to get the touchscreen to work so far, even though the driver is compiled into the kernel - see above for "GTP-INFO").

When the welcome screen is displayed, pressing the "off" button makes the shutdown dialog show on the display, and I can even make a number of screenshots from the Welcome screen by pressing hardware buttons "on" and "vol+" while the tablet is not yet hung, but all of a sudden - about 3 to 5 seconds after the Welcome screen has appeared - everything (i.e. not just adb) completely hangs, i.e. the hardware buttons also become unresponsive. That's why my current theory now is that the vold service seems to cause a complete kernel hang.

But unfortunately, I am at my wits' end when thinking about ways to debug this hang (other than the serial console, which would destroy the tablet, as the back is very firmly bonded to the screen): While I can still connect, neither dmesg nor logcat log do show anything specific, and once it is hung, I cannot retrieve any information from the tablet any more... Frown

So if the three of you also don't have any new ideas regarding why running the vold service might cause a kernel hang and/or what to do next to further track this down, I'll finally abandon the 3.0.36+/KitKat project and continue to run this tablet with my custom CM10.1 which worked quite well...

Many thanks in advance for your comments!

Best regards,

awl

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

Thanks Received: 1
139
2015/04/22 - 18:46
sp_Permalink sp_Print

@Oma:

BTW, I hope all is well with you and in good order? I just noticed from your profile that you haven't posted for almost 4 weeks...


Avatar
ri9000

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

Thanks Received: 7
140
2015/04/23 - 00:55
sp_Permalink sp_Print sp_EditHistory

Hi Awl sounds like you made some progress. What did you change?

When it locks up is it a kernel panic, bad/wrong version/pretend 3.0.36/ driver?

Is your 3.0.36 kernel stable with your stock rom?

Does your 3.0.36 kernel require that "extra" partition like on most rk kk 3.0.36 setups? (sorry can't remember its name, don't know what its for?)

Is there a vold.fstab file and is it correctly configured?

Inside "framework-res.apk" is "storage_list.xml". Its contents contain the config for "vold" to use with "mtp" access. Is it a valid config?

regards, Richard.

edit: do you have a complete config?.. to compile your own cm11 

Avatar
gylu
New Member
Forum Posts: 4
Member Since:
2015/04/23
sp_UserOfflineSmall Offline
141
2015/04/23 - 16:07
sp_Permalink sp_Print

Hi, I have ST10216-2. I put FW from #6 post. But tablet has these problems:

1. No WiFi 

2. No BT

3. No Camera - No extern SD

Is there a newer patch for drivers? Thanks ;)

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

Thanks Received: 1
142
2015/04/23 - 16:21
sp_Permalink sp_Print

Hello gylu,

unfortunately, there is a difference in hardware between Ventos 10.1 revisions:

  • ST10216-1
  • ST10216-2
  • ST10216-2A

all have different hardware (Wifi, Bluetooth, Cameras, Touchscreen). This explains why you need to do your own kernel customisations (you need your kernel source for ST10216-2 [without "A"] from the Trekstor website and a Linux installation [VM] to do cross compilation for ARM), but I am confident that - with the proper kernel driver support for your hardware, we should also be able to get your ST10216-2 going with the CM10.1 build as done by Oma... Wink

If you are interested, please see whether you can get your kernel source and attach the dmesg and logcat output from your tablet when booting the stock kernel here.

Best regards,

awl

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

Thanks Received: 1
143
2015/04/23 - 16:24
sp_Permalink sp_Print
Avatar
gylu
New Member
Forum Posts: 4
Member Since:
2015/04/23
sp_UserOfflineSmall Offline
144
2015/04/23 - 20:27
sp_Permalink sp_Print

awl said
Hello gylu,

unfortunately, there is a difference in hardware between Ventos 10.1 revisions:

  • ST10216-1
  • ST10216-2
  • ST10216-2A

all have different hardware (Wifi, Bluetooth, Cameras, Touchscreen). This explains why you need to do your own kernel customisations (you need your kernel source for ST10216-2 [without "A"] from the Trekstor website and a Linux installation [VM] to do cross compilation for ARM), but I am confident that - with the proper kernel driver support for your hardware, we should also be able to get your ST10216-2 going with the CM10.1 build as done by Oma... Wink

If you are interested, please see whether you can get your kernel source and attach the dmesg and logcat output from your tablet when booting the stock kernel here.

Best regards,

awl

Hi,

Debian is no problem in Virtualbox. But how do I know witch modules I need to compile?

Thanks

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

Thanks Received: 1
145
2015/04/23 - 21:42
sp_Permalink sp_Print

Hello gylu,

it is quite likely that you need to compile both the main kernel as well as the modules.

This all depends on the hardware that is included in your Ventos version 10216-2. As I don't own this device (but the 10216-2A), I cannot know in advance which drivers are needed.

So, first of all, you need to attach the log output of a successful boot of your stock kernel and stock ROM to this thread using adb: both the dmesg log ("adb shell dmesg > dmesg_log.txt") and the logcat log ("adb logcat > logcat_log.txt").

So please do so first, and I'll then try to guide you through kernel compilation - but I need to see from the above mentioned logs which hardware (Wifi, Bluetooth, Touchscreen) has been built into your device.

Best regards,

awl

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

Thanks Received: 1
146
2015/04/25 - 13:32
sp_Permalink sp_Print sp_EditHistory

Hello ri9000,

When it locks up is it a kernel panic, bad/wrong version/pretend 3.0.36/ driver?

Unfortunately, I don't know why the kernel locks up, and cannot find out without a serial console. No signs of any major issue in neither the dmesg nor the logcat log before it hangs... Frown

Is your 3.0.36 kernel stable with your stock rom?

I cannot use the 3.0.36+ kernel with my stock 4.1.1 ROM. The only thing I can say is that the 3.0.36+ kernel is stable with the Pipo and Chuwi KitKat ROMs, as long as the vold service stays disabled - but in this case, I don't get any graphical output on the tablet, but the screen stays blank black.

Does your 3.0.36 kernel require that "extra" partition like on most rk kk 3.0.36 setups? (sorry can't remember its name, don't know what its for?)

Hmm - I don't have any idea what you are talking about here. The mtdparts entry in my parameter file looks like the following:

rk29xxnand:
0x00002000@0x00002000(misc),
0x00006000@0x00004000(kernel),
0x00008000@0x0000a000(boot),
0x00010000@0x00012000(recovery),
0x00020000@0x00022000(backup),
0x00040000@0x00042000(cache),
0x00800000@0x00082000(userdata),
0x00002000@0x00882000(kpanic),
0x0012a000@0x00884000(system),
-@0x009ae000(user)

Is there a vold.fstab file and is it correctly configured?

Where would you expect the vold.fstab file to reside?

There neither is one in the Pipo nor in the Chuwi system.img, but in the boot.img, there is a "fstab"-style file named fstab.rk30board.bootmode.unknown in the root directory that includes "voldmanaged" partitions:

/dev/block/mtd/by-name/user                    /mnt/internal_sd     vfat      defaults        voldmanaged=internal_sd:auto,noemulatedsd
/devices/platform/rk29_sdmmc.0/mmc_host/mmc    /mnt/external_sd     vfat      defaults        voldmanaged=external_sd:auto
/devices/platform/usb20               /mnt/usb_storage     vfat      defaults        voldmanaged=usb_storage:auto

Inside "framework-res.apk" is "storage_list.xml". Its contents contain the config for "vold" to use with "mtp" access. Is it a valid config?

The storage_list.xml file from the Chuwi framework-res.apk looks like the following:

<?xml version="1.0" encoding="utf-8"?>
<StorageList
  xmlns:android="http://schemas.android.com/apk/res/android">
    <storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:emulated="true" android:mtpReserve="100" android:allowMassStorage="false" />
    <storage android:mountPoint="/mnt/internal_sd" android:storageDescription="@string/storage_nand_flash" android:primary="false" android:removable="true" android:emulated="false" android:mtpReserve="100" android:allowMassStorage="true" />
    <storage android:mountPoint="/mnt/external_sd" android:storageDescription="@string/storage_sd_card" android:primary="false" android:removable="true" android:mtpReserve="100" android:allowMassStorage="true" />
    <storage android:mountPoint="/mnt/usb_storage" android:storageDescription="@string/storage_usb" android:primary="false" android:removable="true" android:mtpReserve="100" />
</StorageList>

Would this be a "valid config"!?

do you have a complete config?.. to compile your own cm11?

No, unfortunately, I haven't, and the kernel I am experimenting with also is a generic Rockchip kernel and not at all specific to my tablet... Frown

Thanks a million one more time & best regards,

awl

 

@Jochen/Oma:

Are you still available to help, or have you given up on me? Wink

Avatar
ri9000

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

Thanks Received: 7
147
2015/04/26 - 05:17
sp_Permalink sp_Print sp_EditHistory

Hi Awl,

I thought you had compiled your own 3.0.36 kernel from downloaded source? . . hence my comment compile your own cm11.

re extra partition: if you compare rk jb partitions to rk's kk partition setup you will notice an "extra" inaccessable partition. I mention it only to be thorough I have no idea what its for. If the "rom config" your kernel came from didn't have it then . .Smile

I'm sure you know what fstab does: vold.fstab ( /system/etc ), was supposed to be depreciated in kk but with rockchips mess . . ? Also I have seen 2 "fstab" files in "/" for different boot modes.

Now for the tricky part, (please correct me if i'm wrong here) the rom you have decided to use requires vold: if vold is disabled adb works but surfaceflinger does not start?

Vold/mtp setup is complicated, it requires a correctly formatted "fstab", fuse mounts, "/system/bin/sdcard . . ", "export", entries in init.rc & init.hardware.rc, & a correctly formatted "storage_list.xml".

 I see storage_list.xml has emulated storage (for mtp, ptp) and mass storage configured. ( I thought this was depreciated in kk? See "kk google source/ storage" for more info. )

Can you keep the boot.img/init.scripts that came with the rom and only modify what you need? Post some files if you like so I can help with the config.

*. .to aid diagnostics try removing "mtp" and just set "sys.usb.config" to "adb" only, as we know adb only config works.

fyi: I found this re unpacking the bootloader: https://gist.github.com/sarg/5028505

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

Thanks Received: 1
148
2015/04/27 - 18:59
sp_Permalink sp_Print sp_EditHistory

Hello ri9000,

I thought you had compiled your own 3.0.36 kernel from downloaded source? . . hence my comment compile your own cm11.

I indeed did so, but from a kernel-3.0.36-only git source, not from the official CM11 source. I neither have a "proper" kernel config for the Ventos (but am rather experimenting with kdiff to see what additional parameters/modules/drivers it might need).

Now for the tricky part, (please correct me if i'm wrong here) the rom you have decided to use requires vold: if vold is disabled adb works but surfaceflinger does not start?

yes, although I don't know for sure that it is surfaceflinger which fails - the only thing I know for sure is that the screen stays black blank. Shouldn't there be any logcat entries for surfaceflinger failures? So far, I haven't seen any... Frown

Here's the logcat log when I get the blank black screen only - no signs of anything wrong with SurfaceFlinger...

root@grouper:/ # logcat | grep Surface
I/SurfaceFlinger(   87): SurfaceFlinger is starting
I/SurfaceFlinger(   87): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
I/SurfaceFlinger(   87): Using composer version 1.3
W/SurfaceFlinger(   87): getting VSYNC period from fb HAL: 16342005
I/SurfaceFlinger(   87): EGL informations:
I/SurfaceFlinger(   87): vendor    : Android
I/SurfaceFlinger(   87): version   : 1.4 Android META-EGL
I/SurfaceFlinger(   87): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_
gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_EXT_create_context_robustness EGL_ANDROID_image_native
_buffer EGL_ANDROID_recordable
I/SurfaceFlinger(   87): Client API: OpenGL_ES
I/SurfaceFlinger(   87): EGLSurface: 8-8-8-8, config=0x60000014
I/SurfaceFlinger(   87): OpenGL ES informations:
I/SurfaceFlinger(   87): vendor    : ARM
I/SurfaceFlinger(   87): renderer  : Mali-400 MP
I/SurfaceFlinger(   87): version   : OpenGL ES 2.0
I/SurfaceFlinger(   87): extensions: GL_EXT_debug_marker GL_OES_texture_npot GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL
_OES_depth24 GL_ARM_rgba8 GL_ARM_mali_shader_binary GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_vertex_half_float GL_
EXT_blend_minmax GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_EXT_discard_framebuffer GL_OES_get_program
_binary GL_ARM_mali_program_binary GL_EXT_shader_texture_lod GL_EXT_robustness GL_OES_depth_texture_cube_map GL_KHR_debug
I/SurfaceFlinger(   87): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger(   87): GL_MAX_VIEWPORT_DIMS = 4096
D/SurfaceFlinger(   87): Screen acquired, type=0 flinger=0x40a92450
D/SurfaceFlinger(   87): Screen acquired, type=0 flinger=0x40a92450
D/SurfaceFlinger(   87):  screen was previously acquired

But indeed in the scenario when I get the Welcome screen (plus the hang shortly afterwards), logcat additionally says:

I/SurfaceFlinger(   88): Boot is finished (18654 ms)

This line is missing when the screen stays blank black, but the surfaceflinger process has not crashed:

root@grouper:/ # ps | grep 87
system    87    1     37372  3556  ffffffff 401037f4 S /system/bin/surfaceflinger

Can you keep the boot.img/init.scripts that came with the rom and only modify what you need? Post some files if you like so I can help with the config.

This has already been my current strategy: I use the boot.img scripts that come with the respective Oma CM11 ROM (Pipo and Chuwi variants)... Frown

*. .to aid diagnostics try removing "mtp" and just set "sys.usb.config" to "adb" only, as we know adb only config works.

Just tried that by changing build.prop in system.img , but unfortunately no change in behaviour... Frown

If I don't hear back from Oma and/or Jochen, I'll probably abandon this at this stage - there has not been any progress and I'm unwilling to simply lose more time with this... Cry

Thanks anyway & best regards,

awl

Avatar
gylu
New Member
Forum Posts: 4
Member Since:
2015/04/23
sp_UserOfflineSmall Offline
149
2015/04/27 - 21:29
sp_Permalink sp_Print

awl said
Hello gylu,

it is quite likely that you need to compile both the main kernel as well as the modules.

This all depends on the hardware that is included in your Ventos version 10216-2. As I don't own this device (but the 10216-2A), I cannot know in advance which drivers are needed.

So, first of all, you need to attach the log output of a successful boot of your stock kernel and stock ROM to this thread using adb: both the dmesg log ("adb shell dmesg > dmesg_log.txt") and the logcat log ("adb logcat > logcat_log.txt").

So please do so first, and I'll then try to guide you through kernel compilation - but I need to see from the above mentioned logs which hardware (Wifi, Bluetooth, Touchscreen) has been built into your device.

Best regards,

awl

Hi,

 I was a little bussy... Here is my Logcat  and dmesg . 

 What is the next step ?

Thanks

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

Thanks Received: 1
150
2015/04/27 - 22:33
sp_Permalink sp_Print sp_EditHistory

Hello gylu,

sorry, but after looking into both files, I fear we still have a misunderstanding:

The log files that you have provided is still also based on the kernel for ST-10216-2A:
Linux version 3.0.8+ (chenwj@tchipserver2) (gcc version 4.4.3 (GCC) ) #42 SMP PREEMPT Mon Dec 2 11:50:45 CST 2013

You need to switch back your tablet to the stock (factory provided) 10216-2 (without A) firmware from Trekstor and then send me the output of the dmesg and logcat logs when the tablet boots with the stock kernel and ROM.

I truly hope that you do have a backup of your stock firmware. Otherwise, as you can see here (sorry, in German):

http://www.android-hilfe.de/surftab-ventos-10-1-forum/620035-ventos-10-1-v2-firmware.html

you might be out of luck, as the firmware seems no longer available for download... Frown

You can of course try to request the file from user "STyLiShEr" in this forum or also contact Trekstor support by phone and ask them to send this binary firmware file to you. As stated in the above thread, what you need should be a file called ST10216-v2_FW_pack.zip.

Hope this helps & best regards,

awl

Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online:
74 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (69), Phone (3), Tablet (2)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

polosoft

keyzoo

qwadro

eliezer48

phuckt

hungariaia

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