https://forum.pine64.org/ Thu, 16 Apr 2026 06:38:35 +0000 MyBB https://forum.pine64.org/showthread.php?tid=14894 Wed, 15 Sep 2021 10:47:33 +0000 chitranshu_primeos]]> https://forum.pine64.org/showthread.php?tid=14894
I am Chitranshu, co-founder of www.primeos.in, Primeos is an Android-based operating system used by more than 2M users globally. We wish to launch an Android laptop in India with the help of brand partners. For this to happen we need a sample (even used) Pinebook pro and open-source Android build of Pinebook. We will do the rest to build the Android laptop. Currently, PrimeOS is on Android 7 and we are porting it to Android 11 by December end.]]>
I am Chitranshu, co-founder of www.primeos.in, Primeos is an Android-based operating system used by more than 2M users globally. We wish to launch an Android laptop in India with the help of brand partners. For this to happen we need a sample (even used) Pinebook pro and open-source Android build of Pinebook. We will do the rest to build the Android laptop. Currently, PrimeOS is on Android 7 and we are porting it to Android 11 by December end.]]> https://forum.pine64.org/showthread.php?tid=14592 Thu, 05 Aug 2021 08:55:12 +0000 QuinTeknoLife]]> https://forum.pine64.org/showthread.php?tid=14592

Back in den beginning of the age of PBP there was talk about an Android 9 build being put together, however since then I have not heard or seen any more news regarding the Android front (and the android 7 builds that were up on the wiki also seem to have mysteriously vanished from there). Is there anyone who is working on Android related projects for PBP at all?]]>

Back in den beginning of the age of PBP there was talk about an Android 9 build being put together, however since then I have not heard or seen any more news regarding the Android front (and the android 7 builds that were up on the wiki also seem to have mysteriously vanished from there). Is there anyone who is working on Android related projects for PBP at all?]]> https://forum.pine64.org/showthread.php?tid=11909 Thu, 22 Oct 2020 22:44:23 +0000 jiyong]]> https://forum.pine64.org/showthread.php?tid=11909 It's not very fast, but at least it's a start.

I started "Run Anbox" and Anbox, but failed.
After a reboot Anbox works.
I think we need better OpenGL support for games like Super Tux Kart to work in Anbox.]]> It's not very fast, but at least it's a start.

I started "Run Anbox" and Anbox, but failed.
After a reboot Anbox works.
I think we need better OpenGL support for games like Super Tux Kart to work in Anbox.]]> https://forum.pine64.org/showthread.php?tid=11309 Mon, 07 Sep 2020 00:46:14 +0000 bastafari]]> https://forum.pine64.org/showthread.php?tid=11309
Forgot to say, I'm on Manjaro.]]>
Forgot to say, I'm on Manjaro.]]> https://forum.pine64.org/showthread.php?tid=11207 Mon, 31 Aug 2020 19:00:28 +0000 ModemBlaster]]> https://forum.pine64.org/showthread.php?tid=11207
However, I've noticed booting into Android afterwards causes the battery percentage to behave unexpectedly. Earlier today, I was at ~85% in Manjaro, but after rebooting into Android, I noticed the percentage showed 75% with 1:41 remaining on the battery. I continued to mess around with Android for a while, and eventually the percentage rose to 76%...with 1:41 left on the battery. I rebooted into Manjaro and the percentage read 69% (and stayed there for a while,) and at one point while web browsing it said I had 34:44 left on the battery (yeah.......)

Is Android messing up the battery calibration or something? My guess is that is that Android caused the battery percentage to be set lower, and the percentage was frozen because the battery had to catch up to that number.]]>
However, I've noticed booting into Android afterwards causes the battery percentage to behave unexpectedly. Earlier today, I was at ~85% in Manjaro, but after rebooting into Android, I noticed the percentage showed 75% with 1:41 remaining on the battery. I continued to mess around with Android for a while, and eventually the percentage rose to 76%...with 1:41 left on the battery. I rebooted into Manjaro and the percentage read 69% (and stayed there for a while,) and at one point while web browsing it said I had 34:44 left on the battery (yeah.......)

Is Android messing up the battery calibration or something? My guess is that is that Android caused the battery percentage to be set lower, and the percentage was frozen because the battery had to catch up to that number.]]> https://forum.pine64.org/showthread.php?tid=10570 Sun, 05 Jul 2020 19:11:28 +0000 KC9UDX]]> https://forum.pine64.org/showthread.php?tid=10570 https://forum.pine64.org/showthread.php?tid=9777 Sat, 02 May 2020 12:10:34 +0000 Rik]]> https://forum.pine64.org/showthread.php?tid=9777 i would be really interested in buying a pinebook pro with /e/ pre-installed on it. Is this in the pipeline, or can i put in a request for this hereby?
best,
Rik]]> i would be really interested in buying a pinebook pro with /e/ pre-installed on it. Is this in the pipeline, or can i put in a request for this hereby?
best,
Rik]]> https://forum.pine64.org/showthread.php?tid=9431 Sun, 15 Mar 2020 04:55:02 +0000 jaysistar]]> https://forum.pine64.org/showthread.php?tid=9431 https://forum.pine64.org/showthread.php?tid=9428 Sat, 14 Mar 2020 14:38:09 +0000 jaysistar]]> https://forum.pine64.org/showthread.php?tid=9428 https://forum.pine64.org/showthread.php?tid=9205 Tue, 18 Feb 2020 13:34:47 +0000 pin]]> https://forum.pine64.org/showthread.php?tid=9205
i tried everything to get a working android version running on sd card.
All images from 8GB to 64Gb with Etcher, Pine64installer, rm flashing tool with the image and the terminal version from LearnLinuxTV:
https://www.youtube.com/watch?v=mTyBI2PO4I0
won't working!

Only one thing worked! The 32GB Version with the terminal command "sudo dd if=image.img of=/dev/sdcard-path" will boot to the rockchip-screen. 
After this i can see in the left-bottom corner a code that loops everytime.

PS: I'm using the latest version of debian Stretch on the internal memory and with the new touchpad/keyboard update.

What can i do to get android to run?




Advice: It's very good that the images are without google services. fuck google with their data collection. And stop using gstatic on your website!]]>
i tried everything to get a working android version running on sd card.
All images from 8GB to 64Gb with Etcher, Pine64installer, rm flashing tool with the image and the terminal version from LearnLinuxTV:
https://www.youtube.com/watch?v=mTyBI2PO4I0
won't working!

Only one thing worked! The 32GB Version with the terminal command "sudo dd if=image.img of=/dev/sdcard-path" will boot to the rockchip-screen. 
After this i can see in the left-bottom corner a code that loops everytime.

PS: I'm using the latest version of debian Stretch on the internal memory and with the new touchpad/keyboard update.

What can i do to get android to run?




Advice: It's very good that the images are without google services. fuck google with their data collection. And stop using gstatic on your website!]]> https://forum.pine64.org/showthread.php?tid=8952 Tue, 28 Jan 2020 20:03:51 +0000 metcalsr]]> https://forum.pine64.org/showthread.php?tid=8952
I've talked personally with a few people who seem to think android support isn't really necessary for a strong Pinebook community. Even if Android support seems like the most obvious thing in the world to you, there are people who are firmly against using Android on their device. For this reason, I thought I'd try to enumerate some reasons why I think we really need to get it going.


1. Android provides easy access to Microsoft Office.

Linux users might groan at this, but the Android version of Microsoft Office is surprisingly full-featured. It provides much more than Office Online and many people, even Linux users, still have to use Office to some extent.


2. Access to games

The Pinebook will never be a gaming powerhouse, but if we can get Google Play working reliably, the Pinebook is powerful enough to play a wide variety of Android games.


3. Fills a niche

Considering the low-end specs of the Pinebook, one of the best ways to maintain healthy development for the device is to increase it's lateral utility. Being able to boot into a baremetal armv8 android install would be a strong incentive for hobbyists, developers, and mobile gamers who can't really get that experience from another laptop.


4. Access to Google proprietary video codecs

The Pinebook struggles with 1080p video streaming. There are many android devices with far inferior specs to the Pinebook that can manage it just fine on android.

I'm sure there are more, but these are some of the biggest reasons I don't want to see this area of the forum languish with only three posts.]]>
I've talked personally with a few people who seem to think android support isn't really necessary for a strong Pinebook community. Even if Android support seems like the most obvious thing in the world to you, there are people who are firmly against using Android on their device. For this reason, I thought I'd try to enumerate some reasons why I think we really need to get it going.


1. Android provides easy access to Microsoft Office.

Linux users might groan at this, but the Android version of Microsoft Office is surprisingly full-featured. It provides much more than Office Online and many people, even Linux users, still have to use Office to some extent.


2. Access to games

The Pinebook will never be a gaming powerhouse, but if we can get Google Play working reliably, the Pinebook is powerful enough to play a wide variety of Android games.


3. Fills a niche

Considering the low-end specs of the Pinebook, one of the best ways to maintain healthy development for the device is to increase it's lateral utility. Being able to boot into a baremetal armv8 android install would be a strong incentive for hobbyists, developers, and mobile gamers who can't really get that experience from another laptop.


4. Access to Google proprietary video codecs

The Pinebook struggles with 1080p video streaming. There are many android devices with far inferior specs to the Pinebook that can manage it just fine on android.

I'm sure there are more, but these are some of the biggest reasons I don't want to see this area of the forum languish with only three posts.]]> https://forum.pine64.org/showthread.php?tid=8497 Thu, 05 Dec 2019 13:14:17 +0000 tophneal]]> https://forum.pine64.org/showthread.php?tid=8497 (11-08-2019, 05:52 PM)Arglebargle Wrote: RE u-boot: The script to patch u-boot on the eMMC is simple enough that it should just work, I don't think it's doing anything that would fail on chromeOS.

If for some reason it does fail I hacked a copy so I could flash to a specified device instead of the detected root; I used this to patch loopback mounted copies of ayufan's images so they're ready to use again if I need them. Just edit DEVID to point at the device you want to flash updated u-boot onto: https://pastebin.com/raw/EeK074XB.

You don't want to be working in crosh, either switch to the debug shell (ctrl+alt+f2) or drop to a proper shell from crosh by running "shell" and then switch to root. I usually just "sudo -i bash" as cronos (default password is "cronos") and away you go.

--

I tried the ChromeOS build out for a bit last night and it seemed to work well. Netflix video playback seemed significantly smoother compared to Linux, is there better support for hardware accelerated video here vs the Linux builds? My only real gripe with the experience was the touchpad, otherwise the PBP makes a pretty decent chromebook.
I'm toying with the idea of running Android from my eMMC (might circle back to Chromium if we get an updated release,) but first I was wondering if anyone could tell me if the method above should work to update u-boot if performed through a terminal emulator with root. Obviously, I don't want to lose the ability to boot SDs.]]> (11-08-2019, 05:52 PM)Arglebargle Wrote: RE u-boot: The script to patch u-boot on the eMMC is simple enough that it should just work, I don't think it's doing anything that would fail on chromeOS.

If for some reason it does fail I hacked a copy so I could flash to a specified device instead of the detected root; I used this to patch loopback mounted copies of ayufan's images so they're ready to use again if I need them. Just edit DEVID to point at the device you want to flash updated u-boot onto: https://pastebin.com/raw/EeK074XB.

You don't want to be working in crosh, either switch to the debug shell (ctrl+alt+f2) or drop to a proper shell from crosh by running "shell" and then switch to root. I usually just "sudo -i bash" as cronos (default password is "cronos") and away you go.

--

I tried the ChromeOS build out for a bit last night and it seemed to work well. Netflix video playback seemed significantly smoother compared to Linux, is there better support for hardware accelerated video here vs the Linux builds? My only real gripe with the experience was the touchpad, otherwise the PBP makes a pretty decent chromebook.
I'm toying with the idea of running Android from my eMMC (might circle back to Chromium if we get an updated release,) but first I was wondering if anyone could tell me if the method above should work to update u-boot if performed through a terminal emulator with root. Obviously, I don't want to lose the ability to boot SDs.]]> https://forum.pine64.org/showthread.php?tid=8463 Mon, 02 Dec 2019 00:07:18 +0000 TDC_PBP]]> https://forum.pine64.org/showthread.php?tid=8463 https://forum.pine64.org/showthread.php?tid=7748 Thu, 25 Jul 2019 15:53:30 +0000 tophneal]]> https://forum.pine64.org/showthread.php?tid=7748