Yet A beginner's question to sort the versioning out:

Mobian is a versioned release, right?
So if I go to the image site, the image is currently named

"mobian-pinephone-phosh-12.0.img.gz"

This means I get mobian 12 (which is bookworm) with phosh as a GUI.
And this is also what the Installer-version provides.


But if I download a weekly build (installer or not), I currently get the trixie/sid version which is a rolling release.
But is this rolling release just within trixie? Or can I update this release forever? I mean was there a bookworm/sid before?
And if so, did bookworm/sid automatically become trixie/sid by updating or is that again kind of versioning.
Like there's a rolling release within one big versioned release...?


Thank you!

I keep an eye on #PineTab2 on Mastodon. This week there have been a couple of really interesting posts from people summarizing how they set up the PineTab2 to make a daily driver that works for them. Probably they should be linked to the wiki. Maybe they already are. But I want to make sure they're seen on the forum, too:

@KelsonV shared a blog post entitled PineTab2 Notes: Getting Things Working that I found helpful. I want to play with lxqt -- I've always liked simpler/faster window managers, especially on non-cutting-edge hardware. If anyone has more detailed information for this Arch-newbie on how to build nm-tray, I'd be all ears!

Today @Jordan posted hist setup process. Again, I'm tempted to try it sometime. He actually re-installs an OS; I've not really been inclined to do that yet on my PineTab2. In part I'm concerned about not knowing the process for getting kernel upgrades from from @danctnix outside of the default Arch distro. 

My hope is, someday, to find a good step-by-step tutorial for getting debian (with an effective touch interface) onto the PineTab2. With a procedure for porting over kernel updates!

Forums have been quiet. But I appreciate the occasional tidbits of information or discoveries or experimentation that get posted up here.

I'm reading the install instructions for rk2aw and it says to run rk2aw-spi-flasher. Where do I run this though? Do I boot something on the pinephone and run it inside the pinephone? Or do I plug it into usb and run it on a computer?

Does anyone have any mirrors for the images that were posted? All the links on the wiki for Android images are dead.

I've been running GloDroid, Android 14 2023w46, on the Pinetime beta for awhile now. Here are some of my discoveries in the hopes that they will help others. I hope we see more from the GloDroid team as this has been a fun build to play with. 

Touch response is great/better than most Pinetime distrobutions I've played with.
Battery performance is really good, standby power consumption can get you 3–4 days before charging, which is impressive!
Headphones work!
The phone speaker works too!
F-droid takes a while to update the repositories, so be patient the mirrors can be busy.
The messages app can view messages but not create them. I've been using SMSdroid since then, with good success.
I love the sound effect when you hook up a charging source. The good old days of having a old Nokia are back. ;-)
Tapping 7 times on the build number in the settings->about gives you the developer options. Good for debugging.
I downloaded GadgetBridge from F-droid and was able to pair both of my Pinetime watches. Awesome!

Phone service is a little sketchy, 50/50 chance the phone will boot and recognize the SIM. When I get no service, a workaround I found is to plug the phone into a charging source and open the Messenger app. The phone will reboot on its own, and then the phone SIM is recognized, this may take a couple of reboots to take effect.

WiFi will not connect to my new T-Mobile router. Though if I bring up a hot-spot on my other phone, it will connect with no issues. Funny, because my very old iPod has the same issue.

I do get some random reboots every once in awhile, that's where I'll try to debug the cause so I'll keep playing and making new discoveries and sharing.

Have fun out there!

Gary

Hi,
I am new to this site and would like to ask some questions.
I would appreciate if someone could point me in the right direction.
I have been using Debian on my laptops for over 5 years.
Anything i want to do in the command prompt, i use instructional videos.
It has worked out fairly well.
I installed Ubports on a nexus 5, and it works well...as a mp3player
I would use it as a device if it had encryption.
I see that Mobian is gaining traction in the Pine64 Community.
Is Mobian functional enough for a GUI junkie like me?
Can someone like me buy a pinephone pro and get decent funtionality out of the device?
Would I be better off with a regular pinephone, pinetab2, or pinebook pro?
I like to travel, and i like to segregate my tasks.
I would like multiple devices.
Eg:  one device for browsing the web and torrenting, one device for business, and one device for banking.
I dont need the device to be an actual voice phone, but I would like to have secure, steady browser functionality.
Are there any plans on shipping the devices with an preordered os iso image ready to install?
That might be a way to earn extra revenue for pine64
Thanks for any advice you can give,
Greg

I have interest in the Pinephone only because of the LoRa case:
https://pine64.com/product/pinephone-pin...d-on-case/

This is to my knowledge the first and only phone product that can run mainline linux and have lora kind of build in thanks to this case.

When would this case be available again to order? Without this case i am also not really interested in the phone itself.

I took my broke pinephone pro in to a cellphone repair store with a community edition basic pinephone to hopefully get the sim tray replaced from the community edition to the pro.

The tech said that they were slightly different and moved some stuff around.

How true or accurate is this?

He said he was looking around to see if he could find a replacement tray.

But I thought the main boards and modems were basically pretty all the same, only difference was storage size.

Good day everyone,

I just purchased a new RockPro64 + official aluminium case + 128GB eMMC flash + rtc battery holder but the mistake I made is that I did not know in advance to order an usb serial console or an usb adapter for eMMC.

Now the big challange is to install OpenBSD into eMMC flash without these.
I connected the device to my computer(windows 10) USB port using usb A to RockPro64 USB c OTG port and after installing windows driver assistant I can successfully see it successfully detected with AndroidTool_Release_v2.38 in Maskrom mode.

I am thinking that this might help to flash OpenBSD required files and install it to eMMC card without having a physical serial console.

I downloaded already from OpenBSD official link(https://cdn.openbsd.org/pub/OpenBSD/7.5/...s/aarch64/) the required files:
the bootloader binaries named: u-boot-aarch64 and and dtb binary packages
from u-boot-aarch64-2021.10p10.tgz:
- idbloader.img
- u-boot.itb
- u-boot-rockchip.bin
and from dtb-6.5.tgz
- rk3399-rockpro64-v2.dtb

And of course I downloaded OpenBSD img file.

Your help would be really appreciated if you can provide me some tips on how should I flash these without serial, only using AndroidTool_Release_v2.38 downloaded from https://wiki.pine64.org/wiki/ROCKPro64_S...e_Releases , Miscellaneous tools section.

Is there a way to power up into bios? ... mine works fine [well except the things we all know about] and I am rapidly getting to really like it - just wondering if there are bios settings I can see