| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,470
» Latest member: pandrhola
» Forum threads: 16,196
» Forum posts: 116,871
Full Statistics
|
|
|
| Some helpful tips! |
|
Posted by: dudemo - 10-04-2017, 02:28 PM - Forum: Android on Rock64
- Replies (10)
|
 |
After disliking how Android appeared on the Rock64, I decided I'd had enough and began searching for a new launcher. I wasn't too surprised when I fired up Google Play and saw that basically no launchers are supported. So I started searching out specific launchers (ADW Launcher, Nova Launcher, etc...) and I was able to find a few launchers that actually work! GO Launcher EX works amazingly well and is highly customizable. I won't go into an advertisement for the software, just letting you know that it is a fast way to change the look of Android. One feature I will tout is the ability to force screen orientation in landscape, so you shouldn't be turning your head 90 degrees to navigate anymore hopefully.
Play store link: https://play.google.com/store/apps/detai...erex&hl=en
An alternative that I found works just as well but doesn't have as many options: https://play.google.com/store/apps/detai...cher&hl=en
Next, if your like me... You don't use the on-screen keyboard because you have a USB mouse/keyboard hooked up. I found it to be annoyingly large and it also required that I push the "search" button on the on-screen keyboard and not just pushing "enter" on the keyboard. I searched around and found that others have had the same problem. And came up with a solution! Null Input Method is an IME that basically is not a keyboard. It just hides the on-screen keyboard and re-enables "enter" on a USB keyboard.
Play store link: https://play.google.com/store/apps/detai...free&hl=en
Some of you may not be aware that Android actually does have provisions built-in for a wired keyboard. Unfortunately, documentation for this is very hard to find. Here are the key bindings I've found to be working. I'm also looking into a way to remap these so we can use more comfortable keyboard combinations. Sadly, the "Home", "Num Lock", etc... buttons do not work on any keyboard I've tried, so just pushing "Home" to go home doesn't work.
Home: Alt+Escape
Back: Escape/Right-Click
Menu: Control+Escape
Reboot (NO WARNING!) Control+Alt+Delete
Caps Lock: Shift, Shift (Twice in quick succession!)
App Switcher: Alt+Tab
When I find a free way to remap these buttons, I will let you all know. Likewise, I'll let you know if more shortcuts are found. Fee free to add to the list!
Edit: Aptoide has a pretty good app for downloading apps you cannot get from the Play Store. For example, I really wanted virtual soft keys (back, home, menu) but I was having a hard time finding any compatible ones in the Play Store. Aptoide let me download the one I wanted and installed it. Which brings me to my next point...
Virtual Soft Keys (no root) works pretty fine for getting navigation keys on screen. Follow the directions, it works great. Added benefit is that it let's you hide the keys when you won't need them (RetroArch, Kodi, etc...) by swiping them down, and then reenable them by swiping up from the bottom.
Now, I've had several apps tell me I'm rooted. Am I? Because no root manager seems to work at all.
|
|
|
|
| What is name of gpio hardware on a rock64? |
|
Posted by: gene83 - 10-04-2017, 12:04 PM - Forum: Linux on Rock64
- Replies (6)
|
|
The driver code checks for it, and will return a valid answer if its a bcm2709, bcm2835, bcm2836, or a bcm2837. Code is:
Code: #define CPUINFO_BUFSIZE (16*1024) // Should be large enough for now
static platform_t check_platform(void)
{
FILE *fp;
char *buf;
size_t fsize;
platform_t rv = RPI_UNSUPPORTED;
if(!(buf = rtapi_kmalloc(CPUINFO_BUFSIZE, RTAPI_GFP_KERNEL))) {
rtapi_print_msg(RPSPI_ERR, "hm2_rpspi: No dynamic memory\n");
return RPI_UNSUPPORTED;
}
if(!(fp = fopen("/proc/cpuinfo", "r"))) {
rtapi_print_msg(RPSPI_ERR, "hm2_rpspi: Failed to open /proc/cpuinfo\n");
goto check_exit;
}
fsize = fread(buf, 1, CPUINFO_BUFSIZE - 1, fp);
fclose(fp);
// we have truncated cpuinfo return unsupported
if(!fsize || fsize == CPUINFO_BUFSIZE - 1) {
rtapi_print_msg(RPSPI_ERR, "hm2_rpspi: Platform detection memory buffer too small\n");
goto check_exit;
}
/* NUL terminate the buffer */
buf[fsize] = '\0';
if(strstr(buf, "BCM2708")) {
rv = RPI_1;
} else if(strstr(buf, "BCM2709")) {
rv = RPI_2; //for RPI 3 too
} else if(strstr(buf, "BCM2835")) { // starting with 4.8 kernels revision tag has board details
char *rev_val = strstr(buf, "Revision");
if(rev_val) {
char *rev_start = strstr(rev_val, ": ");
unsigned long rev = strtol(rev_start + 2, NULL, 16);
if(rev <= 0xffff)
rv = RPI_1; // pre pi2 revision scheme
else {
switch((rev & 0xf000) >> 12) {
case 0: //bcm2835
rv = RPI_1;
break;
case 1: //bcm2836
case 2: //bcm2837
rv = RPI_2; // peripheral base is same on pi2/3
break;
default:
break;
}
}
}
}
check_exit:
rtapi_kfree(buf);
return rv;
}
And all the c style indenting has been stripped, so how do I post code? This sucks.
Thanks everybody.
Cheers, Gene83
|
|
|
|
not able to flash u-boot onto SD Card |
|
Posted by: consoleadam - 10-04-2017, 03:44 AM - Forum: General Discussion on ROCK64
- Replies (2)
|
|
greetings,
I have manged to build u-boot as per http://opensource.rock-chips.com/wiki_U-Boot . However, after burning the images to SD card, booting stops before starting my built version of u-boot, i.e., no u-boot prompt!
Serial console output below, also, further down build details.
Can anyone please shed light whats wrong in the process ?
thanks
consoleadam
serial output
========
DDR version 1.06 20170424
In
LPDDR3
786MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
ddrconfig:1
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, emmc reinit
emmc reinit
SdmmcInit=2 20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=7587MB
FwPartOffset=2000 , 0
StorageInit ok = 48039
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x7b5f4
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):f947c7e
NOTICE: BL31: Built : 09:28:45, May 31 2017
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initiapteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: platng runtime services
WARNING: No OPTEE provided by BL2 boot loadTEE will return SMC_UNK
ERROR: Error initializing runtime sernormal world
INFO: Entry point address = 0x200000
INFO:
-------------------
Build and Flashing in details:
==================
consoleadam@barbarian:~/rock64$ git clone https://github.com/rockchip-linux/u-boot.git
consoleadam@barbarian:~/rock64/u-boot$ make ARCH=arm -j4 CROSS_COMPILE=aarch64-linux-gnu- distclean
consoleadam@barbarian:~/rock64/u-boot$ make ARCH=arm -j4 CROSS_COMPILE=aarch64-linux-gnu- evb-rk3328_defconfig all
BL2 ddr.bin & idbloader.img
-----------------------------
consoleadam@barbarian:~/rock64/u-boot$ dd if=../rkbin/rk33/rk3328_ddr_786MHz_v1.06.bin of=ddr.bin bs=4 skip=1
consoleadam@barbarian:~/rock64/u-boot$ tools/mkimage -n rk3328 -T rksd -d ddr.bin idbloader.img
consoleadam@barbarian:~/rock64/u-boot$ cat ../rkbin/rk33/rk3328_miniloader_v2.43.bin >> idbloader.img
BL3 trust.img & u-boot.img
----------------------------
consoleadam@barbarian:~/rock64/u-boot$ ../rkbin/tools/loaderimage --pack --uboot ./u-boot-dtb.bin uboot.img 0x200000
consoleadam@barbarian:~/rock64/u-boot$ cp ../rkbin/rk33/rk3328_loader_ddr786_v1.06.243.bin ./
consoleadam@barbarian:~/rock64/u-boot$ cat >trust.ini <<EOF
[VERSION]
MAJOR=1
MINOR=2
[BL30_OPTION]
SEC=0
[BL31_OPTION]
SEC=1
PATH=../rkbin/rk33/rk3328_bl31_v1.34.bin
ADDR=0x10000
[BL32_OPTION]
SEC=0
[BL33_OPTION]
SEC=0
[OUTPUT]
PATH=trust.img
EOF
consoleadam@barbarian:~/rock64/u-boot$ ../rkbin/tools/trust_merger trust.ini
flashing
---------
consoleadam@barbarian:~/rock64/u-boot$ sudo dd if=idbloader.img of=/dev/sdb seek=64 bs=512
consoleadam@barbarian:~/rock64/u-boot$ sudo dd if=uboot.img of=/dev/sdb seek=16384 bs=512
consoleadam@barbarian:~/rock64/u-boot$ sudo dd if=trust.img of=/dev/sdb seek=24576 bs=512
|
|
|
|
| eMMC Boots to Recovery Menu |
|
Posted by: Farley56 - 10-03-2017, 01:16 PM - Forum: Android on Rock64
- Replies (3)
|
|
Had a working Android 7.1.2 eMMC. Not sure what I did to it but now it boots to the Recovery Menu but there's no keyboard or mouse response. Can't move to any selection in the menu. Reload the eMMC? Boot to an SD Card linux image and fix it from there somehow? Thanks for any tips.
|
|
|
|
| Mpeg2 playback broken in Android 0.3.6 firmware in Kodi |
|
Posted by: Blinky - 10-03-2017, 09:39 AM - Forum: Android on Rock64
- Replies (1)
|
|
1080p Mpeg 2 video playback is broken in latest Android firmware 0.3.6
It now plays with ffmpeg CPU instead of AMCodec(Mediacodec) hardware accelerated in Kodi 17/18 and use 100% CPU.
Eg. 720x480 DVD resolution videos look much smoother now using ffmpeg to play but 720p/1080p plays with skipped frames since it is not hardware accelerated.
Can it be changed so under 720x480(DVD) resolution mpeg 2 videos play with ffmpeg but the rest play with Mediacodec hardware accelerated?
|
|
|
|
| pcsx rearmed on rock64 debian stretch does not go fullscreen |
|
Posted by: RockyBoulder - 10-03-2017, 05:39 AM - Forum: Linux on Rock64
- Replies (2)
|
|
Hello,
anyone else tried pcsx rearmed on ayfan's debian stretch image?
My experience so far is:
If I compile it on rock64 I get wether neon nor dynacrec support which leads to a working build that is way to slow.
Another approach was to build pcsx reamerd on a raspberry pi 3 and copy over the resulting build. Don't build with neon on raspy, too but at least with the very needed dynarec support. Copied the resulting build over to the rock64: Works and is fast enough thanx to dynarec. (Mulltiarch must be installed, to make it work this way).
One Problem remains:
I only get SDL-Window-Output. No fullscreen. Any ideas?
BTW: Controller works too, tried a Steamcontroller with sc-controller.
|
|
|
|
| Mounting Screws |
|
Posted by: S265 - 10-02-2017, 07:25 PM - Forum: General Discussion on ROCK64
- Replies (3)
|
|
Just wondering how you guys mount your board? I tried to use some of the screws left over from PC motherboards. They were often supplied with a million screws for this or that. Anyway my smallest screws would not fit the tiny ROCK64. Even the small brass nuts for offsetting a motherboard from its surrounding case would not fit. Dare I say it but - can we enlarge the hole a tiny bit? Or is this a big no-no. Looking for ideas on this.
|
|
|
|
my first impressions |
|
Posted by: llornkcor0 - 10-02-2017, 07:05 PM - Forum: General Discussion on Pinebook
- Replies (1)
|
 |
I have had the laptop for over a month or so and my first impressions are: excellent for a ~$100 laptop! My 12 year old son claimed it as his and wanted to use it for his laptop next year at school. I had to pry it from his hands!
There are a few things that bother me, though, and a few software issues are well.
Hardware:
The display/lid section is heavier than the keyboard section and is a bit difficult to open as the hinge needs to be stiff and lifts up with keyboard, so it takes two hands to open. I like the keyboard and actually feels nice, although the space bar seems flimsier than the rest of the keys.
Standby/suspend battery life is quite excellent. I had forgotten about it, and turned it on after a week or two, and still plenty of battery left.
It seems hardier than I had expected it to be.
Software:
Android - I didn't spend too much time with android here, other than to see that it ran and I could do a few things with it.
Linux - My biggest niggle is that I could not get bluetooth audio working. As in a bluetooth speaker. It would always just play through the speakers, which indicates a (hw)routing issue, which a way too quiet. Ok for a quiet room.
Some flickering of the display from time to time, but generally is ok.
I installed LXQT and am happy for the performance, noting that this is not a beefy developers laptop.
|
|
|
|
|
