libGPS for TinkerBoard Android

[sobrinho]

Thinking on this, maybe you can provide the details as an alternative 3 for compiling the android from source code.

I'm using those steps to compile: https://tinkerboarding.co.uk/forum/threa...ht=compile

Maybe I can put any required changes on my source code to compile and not worry about that anymore!

[lobo]

Hi, have you already unlocked your TB? If not, it does not boot into the bootloader. You need to unlock with fastboot. Refer to this wiki:  http://opensource.rock-chips.com/wiki_Fastboot
I think the behavior of the TB with u-boot from Nougat is different as before. I found that with 'reboot bootloader' th TB reboots into fastboot mode. Then you can do the unlock and with this command you will get into bootloader:

Code:

sudo fastboot -i 0x2207 reboot bootloader
rebooting into bootloader...
OKAY [  0.000s]
finished. total time: 1.202s

Your other question I can't answer yet. I still don't know where is the uevent.rk30board.rc located. Normally it would be in 'device/rockchip/rk3288', but it's not there...

[edit]
I found this in the build log: 'device/rockchip/common/ueventd.rockchip.rc:root/ueventd.rk30board.rc', so I think you must edit the ueventd.rockchip.rc file in 'device/rockchip/common' to have it ready in the compiled image.

[sobrinho]

It fixed, thanks!

[kisyabrus]

Lobo, Hello. Can you compile a driver for android 7 for ublox 7 and 8?
Now i can run ublox 8 only if it runs with gnss commander and active function in dev options with fictive locations.
P.S. and now i can't run script with autorun when system starts. May be you know how run it?

[lobo]

Hello kisyabrus, the driver only work with GPS nmea messages. So you would need to use the ublox software to switch oft all other satelite systems except GPS.
BTW. I will not develop further,  as I don't use the TB any more in my car. I use a Odroid C2 and it runs with the same driver since long time without any problem.

[maartinus]

Hi All. On my TB, I am using this version of GPS driver: (google for 'kconger android-serial-gps-driver'). I am a contributor of this project and I modified it especially for Android 7 and u-blox chipsets. So, if you have problems with lobo's version you can try this, but there is one diference: it uses properties written in build.prop file instead of gps.conf - please look at readme.md.

You can use files from GIT or zipped project with description "how to build it" attached to the issue "How to use it". And of course, you should rename built gps.rpi3.so file to gps.default.so.

As I wrote, I am using Android 7 and I was not able to permanently change permissions of ttyACM0 device. On my TB model 'S', I tried both lobo's methods but without success. So I added 'chmod 0666 /dev/ttyACM0' to the file /system/etc/init/atrace.rc to the end of chown/chmod list. I know, this method is not very nice, but it works at least on my TB 'S'.

[fited]

Change the permission permanently alternative 2 (uevent.rk30board.rc):

Hi, dear lobo! Thanks for the great contribution of tinker board!

Yesterday I follow your second approach for repacking of boot.img, but i stuck at unpacking step.

From my terminal:

Code:

$ dd if=boot.img of=boot.img.gz skip=8 bs=1 count=100000000000
33554424+0 records in
33554424+0 records out
33554424 bytes (34 MB, 32 MiB) copied, 1222.61 s, 27.4 kB/s

$ gunzip boot.img.gz

gzip: boot.img.gz: not in gzip format

Issue with archive, i.e. i can't fetch data and change anything.

I connect power the TB over the 40p header and connect it to PC through micro usb.

I try also read boot.img and then write it back to TB like this:

Code:

sudo path/to/rkflashtool r boot >boot.img
sudo path/to/rkflashtool w boot <boot.img
sudo path/to/rkflashtool b

works fine, device loaded correctly.

I.e. in my case looks like issue in next command:

Code:

dd if=boot.img of=boot.img.gz skip=8 bs=1 count=100000000000

Wrong parameters?

My android image is TinkerOS_Android V13.14.0.95 (currently it's last android 6 release for TB).

[lobo]

Hello fited,
I don't see any wrong parameter. The boot.img is the image you have read from the TB with rkflashtool, right?
Maybe you can upload boot.img.gz to a cloud store and give the link? Then I could try to gunzip and look if I have the same error or not.

[fited]

Hello fited,
I don't see any wrong parameter. The boot.img is the image you have read from the TB with rkflashtool, right?
Maybe you can upload boot.img.gz to a cloud store and give the link? Then I could try to gunzip and look if I have the same error or not.

All right! Thank you for answer.

I switch to bootloader

Code:

adb reboot bootloader

And then read boot.img

Code:

sudo path/to/rkflashtool r boot >boot.img

After that i call 'dd' operation and receive boot.img.gz.

My
boot.img.gz (http s://drive.google.com/open?id=1FqmCyZs2zcJ71baDJUG_InQC1RKiM7BO)
and 
boot.img (http s://drive.google.com/open?id=1cfTZTIN3H3Fdj9qURWYz9FawLyAqi8aY)
attached.

[lobo]

Hello fited, something wrong with your boot.img, it is not the boot.img of the TB. Pls. see the screenshot of Bless Hex Editor:

your boot.img
   

TB boot.img
   

Seems that your rkflashtool doesn't read the right data. Do you have a TB S? From where do you have downloaded rkflashtool? The original version is here: https://github.com/linux-rockchip/rkflashtool