libGPS for TinkerBoard Android

[fited]

Looks like unpacking for Android M V13.13.0.74 works correctly too!
   
I run all commands successfully and upload newboot.img back to SD Card. Works perfectly!

Note:

After i run command

Code:

gunzip boot.img.gz

boot.img size changed from 33.6mb to 1.9mb

after few steps i call

Code:

path/to/rkcrc -k newboot.img.gz newboot.img

newboot.img size is 1mb,

looks like Android OS works perfectly too this is correct size?
(I ask this question because we have different size of readed boot.img, and newboot.img that we write back to SD Card).
We overwrite only first 1mb boot.img data on out TB Android Image inside SD Card, right?

[lobo]

Great, that it works now. And yes, it is correct, because you read the whole partition 33.6mb, but the real data is only the ramdisk files, and them are packed back to the new boot.img.

[fited]

Great, that it works now. And yes, it is correct, because you read the whole partition 33.6mb, but the real data is only the ramdisk files, and them are packed back to the new boot.img.

Thanks for the explanation, understood! 

I will send question to Asus TB support and also ask about integration of Official Raspberry Pi 7 Display in next Nougat release.

[chino]

Hi,

Can someone please add "/dev/ttyS3" to ueventd.rk30board.rc and upload the image somewhere for me? I am really getting tired of figuring out how to get it done. gunzip doesnt work for me after get boot.img through rkflashtool   even though I unpack it with imgtool, TB wont boot after flash it has been 3 day to get it done and no success

I have NEO-6M and its default baud rate is 9600.
Using 20190515-tinker-board-android-nougat-userdebug-v14.3.2.82

/dev/ttys1 is set to bluetooth in ueventd.rk30board.rc (as I understand) 

May you can help me @lobo

Thanks a lot...

[lobo]

Hello chino, here it is: https://www.dropbox.com/s/7ctjhoj047cz91...t.img?dl=0

I was a little bit confused, if it should be ttyS3 or ttyS1. I made them all, also ttyS0.
It was also needed to remove them from init.connectivity.rc and init.rockchip.rc.

Code:

crw-rw----  1 gps       gps            4,  64 2013-01-18 08:50 ttyS0
crw-rw----  1 gps       gps            4,  65 2013-01-18 08:50 ttyS1
crw-------  1 root      root           4,  66 2013-01-18 08:50 ttyS2
crw-rw----  1 gps       gps            4,  67 2013-01-18 08:50 ttyS3
crw-------  1 root      root           4,  68 2013-01-18 08:50 ttyS4

BTW, why does the gunzip not work? What is the error?
Have you removed the first 8 bytes from the original boot.img, before gunzip?

Code:

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

[chino]

Hi Lobo,

Thank you for the file. I just re-imaged TB with your file and everything seems to be working. I also confused for ttys3 as it was defined under "GPS" but that ttys3 doesnt work within pin 36-37. 

I havent tested it outside yet due to rain/snow in EU but at least I can see bunch of satellites from window (not locking yet). 

Have you removed the first 8 bytes from the original boot.img, before gunzip?

Well yes. That drive me crazy. I read whole conversation here, and tried external forums as well. The error was just "not in gzip format". Tried rktools with Windows and Linux hosts and got same result. I unpacked with imgtool as here. But when I open boot.img in bless hex editor and see 'ANDROID!' again, not 'KRNL'. 

Rooting android with SuperSU didnt work. It just gave me blank screen and I had to re-image it.

Magisk didnt work either, it was boot looping into recovery mode. 

I was about to give up on TB, I never had issues with Android-x86 and Windows 10 in my car. I hope it will work once I go to outside.

[lobo]

To make the modified boot.img I have compiled Nougat from source and flashed to TB. Then I used my in first post method. The extracted boot.img starts with KRNL and can be extracted and unziped as I wrote. 


Now I found that this boot.img from last stock version, that starts with ANDROID!, can be extracted with tool abootimg:

Code:

abootimg -x tb_boot.img

And to extract the root file system:

Code:

mkdir ramdisk
cd ramdisk
gunzip -c ../initrd.img | cpio -i

I haven't found, how I can create the boot.img that starts also with ANDROID!.
But the nice is that the boot.img created with tool rkrc also boots on the last stock version!

[chino]

To make the modified boot.img I have compiled Nougat from source and flashed to TB. Then I used my in first post method. The extracted boot.img starts with KRNL and can be extracted and unziped as I wrote. 


Now I found that this boot.img from last stock version, that starts with ANDROID!, can be extracted with tool abootimg:

Code:

abootimg -x tb_boot.img

And to extract the root file system:

Code:

mkdir ramdisk
cd ramdisk
gunzip -c ../initrd.img | cpio -i

I haven't found, how I can create the boot.img that starts also with ANDROID!.
But the nice is that the boot.img created with tool rkrc also boots on the last stock version!

Hi Lobo,

I am so sorry for late response due to xmas and new year combination that I had
Your latest newboot.img has worked with your library v4. I have tested outside and took me 10min to lock satellites. Second attempt was 1min. 
However, I need  to fix the date and time somehow either with rtc or providing internet. I usually wont do this in the car. 

Other question is that, your newboot.img can be patched through Magisk?

[maartinus]

Hi chino, regarding the acquiring of current time, you can try alternative GPS driver which I wrote about in my comment #70. This driver is able to get and set exact time from GPS satellites.

[lobo]

Hello maartinus, I appreciate if someone manage and support a driver for gps. Maybe you should open an own thread where you can guide the users and maybe upload a prebuilt driver there.
I for myself I decided to go with the Odroid C2 in my car and use this driver without any issue so far. On the Odroid I can edit the uevent.rc without to rebuild the boot.img. And for having the time as soon as possible I use a rtc ds3231.

And @chino, yes you can patch this image with Magisk in the form I described in the other thread.