Firefly Open Source Community

Title: Announcement for releasing SDK of PAD version [Print This Page]

Author: Firefly Time: 12/23/2014 17:49
Title: Announcement for releasing SDK of PAD version

In order to provide a better support on Firefly, out team releases the SDK of PAD version.

This version supports the Display, Touch-Screen and so on.

You can download this SDK on Baidu Cloud and Google Drive.

Baidu Cloud

Google Drive

Please check the md5 checksum before proceeding:

$ md5sum /path/to/firefly-rk3288_pad_android4.4_git_20141218.tar.gz

4ba44765fa649bc5cddadd8b349aa8af firefly-rk3288_pad_android4.4_git_20141218.tar.gz

If it is correct, uncompress it:

mkdir -p ~/proj/firefly-rk3288_pad

cd ~/proj/firefly-rk3288_pad

tar xf /path/to/firefly-rk3288_pad_android4.4_git_20141218.tar.gz

git reset --hard

git remote add bitbucket https://bitbucket.org/T-Firefly/firefly-rk3288.git

From now on, you can pull from bitbucket:

git pull bitbucket pad:pad

You can also browse the source codes online at https://bitbucket.org/T-Firefly/firefly ... branch/pad

Author: cappybob Time: 12/24/2014 07:12

Why do we use the old SDK (1211) to install the (1218)PAD SDK. Looked through the build and is this upgradable with just the master bitbucket pull to the (1211) or is this a seperate build. Noticed that PAD was a 4.4.4.r2 revision.
EDIT:
Load went just as explained, Just one question for files seem to be protected. Is this repo by a private group, for would like to change some files and see what can and can't be done. If so are they waiting until they have completed their goals before they will allow us the personalize builds. Just curious.

Author: busybee Time: 12/26/2014 16:26

Hi cappybob, thanks for pointing out the mistake.

I don't really grasp the meaning of your later added message.

The repo in bitbucket is currently maintained by us. Anyone is

free to fork it and add up his modfication. And we welcome

patches, enhancement suggestions, etc.

Author: cappybob Time: 12/28/2014 04:11

@busybee

Redid with newer instructions and works as should. Previous instructions (Wrong) worked, but seem to have a check sum entry for every code entry. Really strange. Ready to load first build, if anything really stands out, I'll give everyone a Yell. THANKS had to change the name (Rename) download to match instructions, not big problem but I am copy and paste as much as I can to prevent errors as much as possible.

Edit:

Android 4.4.4 is the operating system. A good start for someone who wants to personalize their own build. THANKS to the people of PAD.

--cappybob

Author: Astralix Time: 1/3/2015 09:04

Hi!

Could you add a parameter file that is working for the Android image to your wiki or to the SDK git?

I downloaded the pad version of the SDK and build everything according the wiki, but then I discovered that I had a linux system installed on the firefly. But the linux parameter file is not matching the Android version.

I used this one, extracted from the prebuild Android 4.4 from the firefly download section:

FIRMWARE_VER:4.4.2
MACHINE_MODEL:rk30sdk
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
#KERNEL_IMG: 0x62008000
#FDT_NAME: rk-kernel.dtb
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.hardware=rk30board androidboot.console=ttyFIQ0 board.ap_has_alsa=0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00008000@0x0000e000(kernel),0x00010000@0x00016000(boot),0x00010000@0x00026000(recovery),0x0001a000@0x00036000(backup),0x00040000@0x00050000(cache),0x00002000@0x00090000(kpanic),0x00180000@0x00092000(system),0x00002000@0x00212000(metadata),0x00200000@0x00214000(userdata),0x00020000@0x00414000(radical_update),-@0x00434000(user)

I flashed the resulting images using linux upgrade_tool. If someone is wondering how to flash resource.img, you need to know that the upgrade_tool supports the undocumented option to name any kind of image:

upgrade_tool di -p parameter
upgrade_tool di -k kernel.img
upgrade_tool di -b boot.img

upgrade_tool di resource resource.img
...

Thanks to naobsd for the hint!

And last but not least:

After flashing these images and rebooting via "upgrade_tool rd" the firfly didn't start correctly. But the upgrade_tool didn't want to connect again even I pressed reset and recovery button several times.

A power-cycle then brought things back to normal, recovery started and formatted all needed partitions and after that rebooted to Android as expected.

Kind regards

Astralix

Author: cappybob Time: 1/3/2015 11:54
I like the windows version tool 2.1 from RKCrewTablets for their R-box build for it has a 4G parameter and all I have to do is replace the new Kernel and resource, then load with the parameter from their R-Box release. Have had no problems between Kernel and or New Android builds since they are all R-Box. Their is a lot of difference between the Android SDK and PAD SDK, different set of individuals coding the Pad group are I think Poets at time when you compare the both.

Author: Astralix Time: 1/3/2015 19:53

@cappybob,

I am not sure what you want to tell me...

@firefly team

The above comments where meant to be added to the how-to wiki http://wiki.t-firefly.com/index. ... 8/Build_android/en.

And there is another one:

If you develop different Android versions for different devices, you often need to change the underlying JAVA version. But you won't like to switch the basic JAVA for your linux system. And for several Android build it is even unnecessary to switch it, as for instance Android L works fine with openJDK-7.

So here is the solution: Just switch the JAVA version locally for the terminal you use to build Android:

export ANDROID_JAVA_TOOLCHAIN="/usr/lib/jvm/jdk1.6.0_45/bin"

export JAVA_HOME="/usr/lib/jvm/jdk1.6.0_45/bin"

and then add the same directory as first to the PATH:

export PATH="/usr/lib/jvm/jdk1.6.0_45/binPATH"

After that your build runs fine using the correct JAVA version.

Astralix

Author: cappybob Time: 1/4/2015 00:57

@astralix

Basically that I have not had any problem using a uboot file or parameters from any build made for the Firfefly, for any build of Android or Kernel it seems to make little difference of when or build as long as for the Firefly. The PAD SDK seems to be , I guess Not as Dirty as the original SDK.

---cappybob

Author: Astralix Time: 1/4/2015 07:21

cappybob, there are no problems but a missing parameter file.

I had installed Linux on my firefly and the Linux compliant parameter file does not match the needs of Android image.

So I was able to download and unpack an Android image for firefly and then copy the parameter file to the master:master and the pad:pad version. Both worked fine.

I just wanted someone to add a parameter file to the code and a comment in the wiki, so other users do not have to search a matching parameter file.

And the pad version differs a bit from the master branch, cause they have different screen layout and pad version is scanning for a I2C touch screen chip, the master branch is not. However if you use your computer monitor as a screen, you wish a much higher screen resolution setting in build.prop as the icons are large and blurry. If you use the system on a mid size TV, it works just fine.

Astralix

Author: zhansb Time: 1/5/2015 09:46
parameter can find in the pad sdk: FFTools/AndroidTool_Release_v2.33.rar

Author: tedbear Time: 1/5/2015 17:40

Author: Astralix Time: 1/6/2015 07:25

Hi!

I do have a parameter that works fine. I just suggested improvements for the wiki, so other users do not have to search on their own.

Astralix, crewRkTablets

Welcome Firefly Open Source Community (https://bbs.t-firefly.com/)