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
76
2015/03/05 - 20:13
sp_Permalink sp_Print sp_EditHistory

Hello again,

thanks a million - looks like we're getting really close!Smile

BT device MT6622 is now properly recognized and initialized with the firmware patch. Still, BT does not yet stay enabled - full log excerpt is attached, but here are the important errors:

E/[BT]    ( 1834): set_bluetooth_power: Open /dev/bthwctl to set BT power fails: Permission denied(13)
(...)
W/[BT]    ( 1834): load_custom_bt_conf: Failed to open /data/BT.cfg!
W/[BT]    ( 1834): mtk_fw_cfg: No custom BT config
W/[BT]    ( 1834): load_internal_bt_conf: No internal BT config, generate from default value
E/[BT]    ( 1834): load_internal_bt_conf: Try to create internal BT config, error
E/[BT]    ( 1834): mtk_fw_cfg: Load internal BT config failed!
(..)
E/bt_h4   ( 1834): [h4] Unknown HCI message type drop this byte 0xd1
E/BluetoothAdapterState( 1834): Error enabling Bluetooth

/dev/bthwctl exists, but looks like this:

root@android:/ # ls -l /dev/bthwctl
crw------- root     root     249,   0 2015-03-05 19:31 bthwctl

so I assume I need to add some permission changes to the init process in boot.img. Correct?

Also, do you have any idea where to get a BT.cfg from?

Many thanks!

awl

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

Thanks Received: 1
77
2015/03/06 - 00:32
sp_Permalink sp_Print

Hello Oma,

great news: Bluetooth is working fine! Cool

Two more things were needed:

Firstly, the file "libbt-vendor.so" needs to reside in /system/vendor/lib, not system/lib for things to work fine.

Secondly, I needed to change init.rkboard.rc to change the "bthwctl" device as follows:

    chmod 0660 /dev/bthwctl
    chown bluetooth radio /dev/bthwctl
    mkdir /data/bluetooth 0711 bluetooth bluetooth

Now WiFi is working perfectly fine, as is Bluetooth! Great - we're nearly there...

Only some small things left, most prominently sensors (and some other interesting errors in logcat with lowest priority). The portrait/landscape detection sensor (STK8312?) does not work, neither does the light sensor. Here is the messages from dmesg and logcat:

<6>[    2.568807] STK831x_Init: Initialize stk8312

E/SensorsHal(  420): couldn't find 'proximity' input device
D/SensorsHal(  420): Couldn't open /dev/psensor (No such file or directory)
E/SensorsHal(  420): couldn't find 'gsensor' input device
D/SensorsHal(  420): Couldn't open /dev/mma8452_daemon (No such file or directory)
E/SensorsHal(  420): couldn't find 'compass' input device
D/SensorsHal(  420): Couldn't open /dev/akm8975_aot (No such file or directory)
E/SensorsHal(  420): couldn't find 'gyro' input device
D/SensorsHal(  420): Couldn't open /dev/gyrosensor (No such file or directory)
D/SensorsHal(  420): GyroSensor::GyroSensor():No such file or directory
I/SensorService(  420): MMA8452Q 3-axis Accelerometer
I/SensorService(  420): AK8975 3-axis Magnetic field sensor
I/SensorService(  420): AK8975 Orientation sensor
I/SensorService(  420): ST 3-axis Gyroscope sensor
I/SensorService(  420): AL3006Proximity sensor
I/SensorService(  420): AL3006 light sensor
D/SensorService(  420): nuSensorService thread starting...
D/SensorsHal(  420): Couldn't open /dev/mma8452_daemon (No such file or directory)
E/SensorService(  420): Error activating sensor 0 (Operation not permitted)
D/EventHub(  420): No input device configuration file found for device 'lightsensor-level'.

How does one resolve these sensor issues? Is it possible to copy some libs from /system/lib/hw from the stock 4.1.1 to CM10.1/4.2.2? And what about the missing devices?

Once we have finished, I will then provide the final model fix for the Ventos ST10216-2a, the modified boot.img and my custom kernel.img (and kernel source if you like) to you to complete your kernel collection. Wink

When I have plenty of spare time (not likely for the next couple of weeks), I will then possibly look again into whether a 3.0.36+ kernel build and a KitKat build for the Ventos seems feasible to me...

And I fully agree: Indeed "per aspera ad astra"... Laugh

Thanks again & best regards,

awl

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

Thanks Received: 1
78
2015/03/07 - 18:48
sp_Permalink sp_Print

Hello again,

shortly reverted to stock 4.1.1 today for finding out how things look like with the stock image:

With the stock image, I have /dev/stk831x:

crwxrwxrwx root     root      10,  55 2015-03-07 18:08 stk831x

But I cannot find how this device is created: What component is responsible for creating this? Can I create this device manually using mknod in CM 10.1 init.rk30board.rc?

Also, the output of "grep -i sensor" run against logcat output looks like the following:

$ grep -i -e sensor logc_411.out
D/SensorService(  334): nuSensorService starting...
E/SensorsHal(  334): couldn't find 'proximity' input device
D/SensorsHal(  334): Couldn't open /dev/psensor (No such file or directory)
E/SensorsHal(  334): Load stk8312 pass (1), -1, 38
E/SensorsHal(  334): couldn't find 'compass' input device
D/SensorsHal(  334): Couldn't open /dev/akm8975_aot (No such file or directory)
E/SensorsHal(  334): couldn't find 'gyro' input device
D/SensorsHal(  334): Couldn't open /dev/gyrosensor (No such file or directory)
D/SensorsHal(  334): GyroSensor::GyroSensor():No such file or directory
I/SensorService(  334): STK8312 3-axis Accelerometer
I/SensorService(  334): AK8975 3-axis Magnetic field sensor
I/SensorService(  334): AK8975 Orientation sensor
I/SensorService(  334): ST 3-axis Gyroscope sensor
I/SensorService(  334): AL3006Proximity sensor
I/SensorService(  334): AL3006 light sensor
D/SensorService(  334): nuSensorService thread starting...
D/EventHub(  334): No input device configuration file found for device 'lightsensor-level'.

I will try next to copy /system/lib/hw/sensors.rk30board.so from my 4.1.1 system to CM 10.1 and see whether this improves things...

Thanks again for any hints and advice... Wink

Best regards & have a nice and sunny Sunday,

awl

Avatar
Oma7144

Moderator

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

Thanks Received: 1378
79
2015/03/07 - 19:48
sp_Permalink sp_Print

Your tab does not have all this sensor's.

- Oma -


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

Thanks Received: 1
80
2015/03/08 - 00:48
sp_Permalink sp_Print

Hello Oma,

interesting news one more time:

My tab indeed does not have most of these sensors, but it clearly has an orientation (portrait/landscape) detection sensor (I think "gsensor" is the correct name): STK8312/AK8975 and a light sensor: AL3006.

I have made some progress: Having copied sensors.rk30board.so from stock 4.1.1 to /system/hw/lib of the CM10.1 build and created the /dev/stk831x and set 0777 permissions on this device in init.rk30board.rc, the orientation sensor has started to work fine, but currently my display is wrongly rotated 90 degrees in clockwise (to the right) direction: i.e. when I hold it in landscape mode, picture is portrait mode and top is on the right hand side, bottom on the left hand side. When I rotate it, it properly follows the rotation movement, so the sensor as such works fine, but always with the offset of 90 degrees clockwise, so the picture is always wrongly orientated (as if the tablet were a phone).

You have created a number of "orientation fixes" for CM 10.1, but for the original sensors.rk30board.so lib that does not work for me as it comes without support for STK8312. What do I have to change/patch in my STK8312-aware sensors.rk30board.so in order to rotate the picture by 90 degrees counter-clockwise (to the left)?

Thanks again for pointing me to the right action to take in terms of patching the sensor library to counteract this 90 degrees rotation offset?

Also, I know from the stock install that my tab has a light sensor (AL3006) to automatically control display brightness that works fine on 4.1.1, but seemingly it needs to be configured somehow: "No input device configuration file found for device 'lightsensor-level'." Any ideas?

Thanks again for your help! Smile

Best regards,

awl

Avatar
Oma7144

Moderator

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

Thanks Received: 1378
81
2015/03/08 - 08:47
sp_Permalink sp_Print

Negative. Remember what I said about nameing conventions. Use one of prebuild sensor fixes from the blog.

For brightness there is also some stuff on the blog, which may help.

- Oma -

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

Thanks Received: 1
82
2015/03/08 - 11:09
sp_Permalink sp_Print

Hi again,

I had tried all so-called "sensor fixes" available first (before I started looking into using my stock version), but they don't work for me: None of the sensors.rk30board.so libraries in those sensor fixes has support for the STK8312 sensor which is the sensor that it built into my tablet and its support is needed to make things work.

Here is why:

android@android-build:~/stock $ strings system/lib/hw/sensors.rk30board.so | grep 8312
Load stk8312 pass (%d), %d, %d
Load stk8312 failed (%d), %d, %d
STK8312 3-axis Accelerometer
android@android-build:~/stock $

which means that the stock library from 4.1.1 has been changed by the vendor to explicitly support this sensor type.

When I run the same command against the sensors.rk30board.so included with CM10.1 - or any of the "sensor fixes" that you provided - none of them produces any output:

android@android-build:~/cm101 $ strings system/lib/hw/sensors.rk30board.so | grep 8312
android@android-build:~/cm101 $

So all these versions clearly do not support this "STK8312 3-axis Accelerometer" sensor chip, and consequently they do not work for me at all.

Any other ideas?

Thanks,

awl

Avatar
Oma7144

Moderator

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

Thanks Received: 1378
83
2015/03/08 - 11:33
sp_Permalink sp_Print

Correct. We don't know other then mma sensors on a rk30baord. In any case the daemon is called mma8452 (doesn't matter what is physically there).

When you'd like to use your stock sensor HAL the only way is to change orientation in the kernel.

- Oma -

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

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

Thanks Received: 1
84
2015/03/08 - 11:38
sp_Permalink sp_Print

Thanks for your super-fast reply.

When you say: "When you'd like to use your stock sensor HAL the only way is to change orientation in the kernel.", how can I do so?

I do have the kernel source for the STK8312 device (see attached!), but what exactly would I have to change?

Thanks a million one more time! Smile

awl

Avatar
Oma7144

Moderator

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

Thanks Received: 1378
85
2015/03/08 - 11:46
sp_Permalink sp_Print

I will ask Jochen to give you advice on that.

- Oma -

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

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

Thanks Received: 1
86
2015/03/08 - 12:48
sp_Permalink sp_Print sp_EditHistory

Hello Oma, hello Jochen,

one more update: When looking at the sensor values from STK8312 shown through AndroSensor, I think these values suggest why auto-rotation is off:

Tablet lying flat on a table (I think this is OK):

X: 0 m/s^2
Y: 0 m/s^2Z: +10 m/s^2

Tablet standing 90 degrees on table in landscape mode (should be the standard orientation for a tablet):

X: +10 m/s^2
Y: 0 m/s^2
Z: 0 m/s^2

... but shouldn't we expect X = 0 and Y = 10 here (vertical)?

Tablet standing 90 degrees on table in portrait mode (should be the standard orientation for a phone):

X: 0 m/s^2
Y: +10 m/s^2
Z: 0 m/s^2

... but shouldn't we expect X = 0 and Y = 10 here (vertical)?

So I assume that X and Y would "simply" need to be swapped...

Thanks & best regards,

awl

Avatar
Oma7144

Moderator

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

Thanks Received: 1378
87
2015/03/08 - 12:50
sp_Permalink sp_Print

Yes.

- Oma -

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

Thanks Received: 1
88
2015/03/08 - 13:46
sp_Permalink sp_Print

And one more intersting finding: Just rebooted into the old stock Trekstor 4.1.1 ROM, and verified that the sensor output in this environment is exactly the same as it is on CM10.1 (i.e. X and Y are also swapped like they would be correct for a phone, but not a tablet).

Nevertheless, the Trekstor 4.1.1 build still somehow seems to "know" that it needs to always rotate the display by 90 degrees counter-clockwise...!? Any ideas? Is there any global Android property value that can be set to cause this?

Thanks & best regards,

awl

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

Thanks Received: 1
89
2015/03/08 - 13:50
sp_Permalink sp_Print

Update:

I will try and see whether this:

http://android.stackexchange.com/questions/10808/how-is-the-default-screen-orientation-in-android-specified

might help, i.e. experiment with several values for "user_rotation" in the sqlite settings.db...

Sounds like this might be the correct way of addressing this...!?

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

Thanks Received: 1
90
2015/03/08 - 14:05
sp_Permalink sp_Print

Netxt update: This does not work, as user_rotation is only taken into account when accelerometer_rotation=0, i.e. when I switch off "Auto-rotate screen", which exactly is what I would NOT like to do (but rather fix auto rotation)...

Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online: NOnoS
110 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (94), Phone (16), Tablet (1)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

NOnoS

ammie

Andreasse

richard0085

saradavis1

sinan8503

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