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
121
2015/04/01 - 21:33
sp_Permalink sp_Print

OK, some more progress! Cool

Using a 3.0.36+ kernel that properly includes SELinux as described here:

http://superuser.com/questions/253959/where-did-selinux-go

I can boot and connect fine with "adb shell" using "Oma_RK30_Pipo_S1s_KK_4.4_v1.0", but not using "Oma_RK31_Chuwi_V88_KK_4.4.2_v2.3_gen1 loader", which still hangs displaying the boot framebuffer. Next, I tried to flash the boot.img from the Pipo 4.4 build into the Chuwi 4.4.2 ROM, and - success! - the 4.4.2 ROM also boots fine.

Unfortunately, as soon as the "Welcome" screen appears (requiring to select the language), I am stuck, as the touchscreen does not yet work. Some seconds later, adb all of a sudden gets disconnected. Yell

I have attached a dmesg log and a logcat log shortly before adb hangs - see below.

@Oma/Jochen:

Can you please help resolving any of these questions:

  • What could be the difference between the Chuwi 4.4.2 boot.img and the Pipo 4.4 boot.img that causes the hang with the Chuwi boot files?
  • Do you have any idea why adb gets disconnected shortly after the Welcome screen appears on first boot? Is this expected, and I need to switch USB debugging back on via the Settings app once I get touchscreen to work properly?
  • What do I need to change the Chuwi ROM to use landscape (tablet) rather than portrait (phone) mode? Is there also a "tablet UI" patch for KitKat?

Many thanks one more time! Smile

awl

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

Thanks Received: 1
122
2015/04/01 - 21:46
sp_Permalink sp_Print sp_EditHistory

Would it be possible that the following change causes the hang with the Chuwi boot.img?

--- boot_pipo/init.rk30board.rc 2015-04-01 21:38:21.889597942 +0200
+++ boot_chuwi/init.rk30board.rc        2015-04-01 18:38:23.383864739 +0200
@@ -10,9 +10,10 @@
 
 on post-fs
     insmod /system/lib/modules/ump.ko
-    insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200,266,400 mali_init_clock=50
+    insmod /system/lib/modules/mali.ko mali_dvfs=133,160,200,266,400,600,798 mali_init_clock=50

EDIT: Nope - switching to slower clock speeds did not cure the hang... Cry

Thanks,

awl

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

Thanks Received: 1
123
2015/04/01 - 22:04
sp_Permalink sp_Print sp_EditHistory

Update: The difference between the Pipo and Chuwi boot.img causing the hang is in init.rk30board.rc - simply replacing this single file by the Pipo version makes the rest of the Chuwi boot.img work fine...

dmesg and logcat log now look like the following:

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

Thanks Received: 1
124
2015/04/07 - 15:06
sp_Permalink sp_Print

Bump...

@Oma/Jochen (sorry for my impatience in case you are on Easter vacation!):

I still need your help with regards to my questions in #121.

Also, do you see anything in the logs as attached to #123 that could explain why the display goes black after the framebuffer (but only with the Chuwi boot.img)?

I'm still experimenting with making kernel drivers/options more similar to the stock TrekStor 3.0.8+ kernel, but so far, have not succeeded in getting the display and touchscreen to work properly, even though the correct drivers are included in my kernel:

CONFIG_LCD_B101EW05=y
CONFIG_TOUCHSCREEN_GT92X_IIC=y

Unfortunately, in the 3.0.36+ dmesg log in #123, I do NOT see the "GTP-INFO" startup messages from the touchscreen driver that are present in 3.0.8+, where they look like the following:

<4>[    5.555485] <<-GTP-INFO->> GTP driver installing...
<4>[    5.560512] <<-GTP-INFO->> GTP Driver Version: V1.8<2013/06/08>
<4>[    5.568525] <<-GTP-INFO->> GTP Driver Built@21:25:39, Mar  4 2015
<4>[    5.574649] <<-GTP-INFO->> GTP I2C Address: 0x5d
<4>[    5.715059] <<-GTP-INFO->> driver send config
<6>[    5.743715] input: Goodix Capacitive TouchScreen as /devices/virtual/input/input3

What can be the reason for this? How is the touchscreen initialized?

Thanks a million & best regards,

awl


Avatar
JochenKauz

Moderator

Firmware Guru
Forum Posts: 450
Member Since:
2012/11/19
sp_UserOfflineSmall Offline

Thanks Received: 76
125
2015/04/10 - 12:17
sp_Permalink sp_Print

Hi,

could you upload your current kernel source for the 3.0.36+ to github? I have to look at the driver code, perhaps I can help you.

Regarding the TabletUI, perhaps you can find something in the build.prop.

 

Cheers

JochenKauz

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

Thanks Received: 1
126
2015/04/12 - 19:39
sp_Permalink sp_Print sp_EditHistory

Hello Jochen,

sorry it took that long for me to upload the source to github. As a complete newbie to git, I needed to sort out two major issues first in order to be able to successfully push: First, I was running into

https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1111882

(which basically means that using the https protocol from Ubuntu to github does not work due to a bug in GnuTLS and you need to revert to using ssh) and then with ssh I still needed to find out on increasing git client-side ssh timeouts (as my ADSL upload is real slow):

https://confluence.atlassian.com/display/STASHKB/Git+SSH+push+timeout+on+large+changes

Quite a disillusioning first-time git experience... Confused

The repository is finally online now:

https://github.com/awl1/kernel-st10216a-3036

So the most critical questions/issues with regards to the 3.0.36+ kernel (kernel config in arch/arm/configs/st10216-2a_defconfig) currently are:

1) Why does the display go black after the frame buffer with Chuwi boot.img?

2) Why does adb hang after some seconds if I use the Pipo boot.img?

3) Why does the tochpad not work even though there is a display with Pipo boot.img?

4) Why is

<<-GTP-INFO->> GTP driver installing...

the only dmesg line written by the touchpad driver (as opposed to the correct drive startup documented in #124 for 3.0.8+)?

I have now put several days of research into this, but without any progress - so I am thinking about abandoning this project and staying with the CM10.1 build for the Ventos... Frown

Thanks a million in advance for your kind help!

awl

Avatar
JochenKauz

Moderator

Firmware Guru
Forum Posts: 450
Member Since:
2012/11/19
sp_UserOfflineSmall Offline

Thanks Received: 76
127
2015/04/12 - 21:53
sp_Permalink sp_Print

Hi,

one step after the other..

And you can not believe how many months(!) we needed for many homebrew kernels to work, so this is normal or... welcome to the homebrew scene.Laugh

It is always not easy to say something about a boot.img you did not build at your own. So regarding the different boot.img's Oma should help, I'm only a kernel guy.

I hope I could have some time in the next days to look at your kernel and perhaps I find something regarding the touch.

Touch and LCD are two different things, if LCD is working, this has nothing todo with the touch.

Cheers

JochenKauz

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

Thanks Received: 1
128
2015/04/13 - 23:42
sp_Permalink sp_Print

Hello again,

some limited progress:

When (only) replacing the init.rc within the Chuwi boot.img by the one from the Pipo boot.img, I can make the display work with the Chuwi image as well, but at the expense of adb hanging some very few seconds after the Welcome screen is displayed.

When looking at the differences between these two init.rc files, there are only three minor (!?) differences:

  • The Chuwi version writes a value for kernel parameter "ping_group_range"
  • The Chuwi version has the "vold" service disabled, while it is enabled in the Pipo version
  • The Chuwi version has an additional service "daemonsu"

--- boot_pipo/init.rc   1970-01-01 01:00:00.000000000 +0100
+++ boot_chuwi/init.rc  1970-01-01 01:00:00.000000000 +0100
@@ -131,6 +131,10 @@
 # This is needed by any process that uses socket tagging.
     chmod 0644 /dev/xt_qtaguid
 
+# ICMPv6 group id range from 0~0x7fffffff for passing cts loopback ping
+       write /proc/sys/net/ipv4/ping_group_range "0 2147483647"
+
+
 # Create location for fs_mgr to store abbreviated output from filesystem
 # checker programs.
     mkdir /dev/fscklogs 0770 root system
@@ -469,6 +473,7 @@
     class core
     socket vold stream 0660 root mount
     ioprio be 2
+    disabled
 
 service netd /system/bin/netd
     class main
@@ -605,3 +610,8 @@
 service whtest /system/bin/whtest.sh
     disabled
     oneshot
+
+service daemonsu /system/xbin/daemonsu --auto-daemon
+    class core
+    user root
+    group root

While at the first glance, I don't see why any of those should cause the differences in behaviour:

  • Screen does properly display (Pipo) vs. stays blank black (Chuwi)
  • adbd hangs some few seconds after displaying the Welcome screen (Pipo) vs. adbd works fine (Chuwi)

Will try to track this down further during the next couple of days...

Thanks & best regards,

awl

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

Thanks Received: 1
129
2015/04/14 - 00:08
sp_Permalink sp_Print

OK, so it looks like the fact whether the "vold" service is disabled or not determines the behaviour as described above:

  • vold disabled: Display stays blank black, but adbd continues to work fine
  • vold enabled: Display shows Welcome screen, but adbd hangs shortly after the Welcome screen is displayed

@Oma:

Do you have an idea why this might be the case? Obviously I need both: adbd and the display... Confused

Thanks again & best regards,

awl

Avatar
JochenKauz

Moderator

Firmware Guru
Forum Posts: 450
Member Since:
2012/11/19
sp_UserOfflineSmall Offline

Thanks Received: 76
130
2015/04/14 - 11:44
sp_Permalink sp_Print

Hi,

daemonsu is for the root service.

Regarding the adb, unpack both boot.img. Then make a grep for adb in both. There should be many different entries for adb and adbd in:

file_contexts, init.rockchip.rc, init.rk30board.usb.rc, property.contexts, init.usb.rc, init.rc, default.prop and uevent.rc.

Perhaps it helps to switch the sepolicy file.

 

Cheers

JochenKauz

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

Thanks Received: 1
131
2015/04/18 - 18:01
sp_Permalink sp_Print

Hello Jochen, Oma, all,

any news from your side regarding my questions in #126 and #129?

I am completely stuck - I had already unpacked (and successfully repacked) both boot.img versions (Pipo and Chuwi), and I've also done a lot of experiments with selinux and vold configurations, but I don't get anywhere...

I still completely unable to figure out why adb - and seemingly the whole kernel - hangs once vold is started, and I don't see any helpful error messages at all until the time of the hang. Also, I have no clues why I don't end up at the Welcome screen (the display stays black such that I don't see anything on the screen) when the vold service is disabled, but in this case, I don't see a hang (and also no signs of any issues in the logs)...

If you have any ideas about what might be going on, or what I should try to change inside the boot images, please let me know - I am at my wits' end and now indeed think about giving up with this... Confused

Thanks & best regards

awl

Avatar
ri9000

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

Thanks Received: 7
132
2015/04/19 - 11:37
sp_Permalink sp_Print sp_EditHistory

Hi Awl, "vold" itself may not be the cause of your problems..

This line should be present in "init.hardware.rc" , at the end of "on post-fs-data" section, and commented out in "init.rc"

# Set indication (checked by vold) that we have finished this action
setprop vold.post_fs_data_done 1

re adb: Try adding this to /system/build.prop, (set perms to 0644)

persist.sys.usb.config=adb

The following users say thank you to ri9000 for this useful post:

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

Thanks Received: 1
133
2015/04/19 - 13:03
sp_Permalink sp_Print

Hello ri9000,

thanks, but unfortunately both your proposals are already included:

I do have "setprop vold.post_fs_data_done 1" in init.rk30board.rc at the proper place, and also in /system/build.prop, I even have "persist.sys.usb.config=mtp,adb"... Cry

Any other ideas?

Thanks again & best regards,

awl

Avatar
ri9000

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

Thanks Received: 7
134
2015/04/19 - 13:45
sp_Permalink sp_Print

i'm thinking the rom config is setting "sys.usb.config=mtp" and killing your adb.

so, at the end of your init.hardware.rc file add this:

on property:init.svc.bootanim=stopped

  setprop sys.usb.config adb

Avatar
ri9000

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

Thanks Received: 7
135
2015/04/19 - 13:52
sp_Permalink sp_Print

ps: your default.prop should also contain something like...

ro.secure=0
ro.adb.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb

Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online:
138 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (101), Phone (37)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

saradavis1

sinan8503

GsmProf

DS13

iyousaf

devikl

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