Anyone is still playing PineCone? I am trying to build blsp_boot2 myself using the bl_iot_sdk tree.
However, the binary that I built is very different from the prebuilt image bl_iot_sdk/tools/flash_tool/bl602/builtin_imgs/blsp_boot2.elf
Here is how I did:
$ cd bl_iot_sdk
$ export BL60X_SDK_PATH=$(pwd)
$ export CONFIG_CHIP_NAME=BL602
$ cd bl_iot_sdk/customer_app/bl602_boot2
$make
The generated binary bl602_boot2.elf contains the main function like a dummy.
230002aa <main>:
230002aa: 8082 ret
230002ac: 0001 nop
230002ae: 0101 addi sp,sp,0
The pre-built blsp_boot2.elf seems to be a valid one, which matches the bl602_boot2 code.
Can anyone point out what I have missed here? thanks so much in advance.
What is the default password for my KDE plasma pine phone? I was never prompted to enter a password, but need it to run sudo commands in the terminal. I found default passwords like 1234, 12345, 123456, linux, on various forum post, but none of them work in my case.
My pine phone stopped making and receiving phone call.
I have full Internet and connection sharing, SMS works fine, both sending and receiving, but I am unable to make or receive phone calls.
I am in Australia, connecting through Telstra.
When attempting to make a call, it immediately goes to call ended, and when anyone calls me I get no indication that a call is coming through, at their end it goes to voice mail, and I receive an sms telling me I missed a call..
For an lshw list of my hardware .. please see attachment
The issue is not related to the recent upgrade, as it occurred prior to upgrading. I was hoping the upgrade would fix the issue..
I cannot flash the modem firmware. I succeeded in flashing ADSP by using ADSP Version EG25GGBR07A08M2G_30.202.30.202 but when I run flashall (with or without sudo), it just displays "waiting for any device". I tried to run each command line one by one and this message appears when running "fastboot oem stay": https://github.com/the-modem-distro/pine...s/flashall
How can I solve this problem?
I'm under Mobian bookwork, I'll switch to Mobian trixie when this problem is solved.
P.S: I'm going to upgrade the operating system first, it had worked with Mobian Trixie once for sure.
Hi,
My sealed Pinetime arrived today, I placed it on the charger, it booted, I set the time, a few seconds later it rebooted and is now stuck at the green pinecone logo at about 75%, nothing is appearing in gadget bridge or nRF Connect, hardware button is unresponsive, is there any way to contact Pine64 as I think I may have received a bad unit?
Currently I'm trying to let the battery completely drain but that is going to take days.
Running a linux OS on android phones Hey, so I just recently bought a galaxy s21 phone and since then I learned about the recent changes android is making, which basically would require third party developers to go through a verification process in order to allow folks to download their apks. I have concerns about this, since I use apks that Google and Android are not happy with to say the least, and I'm worried that this verification process will allow them to pick and choose who to verify and who to block, meaning I and others won't be able to download these apks anymore. So I'm trying to look into alternative OS I can install on android. So far I learned about some of the different linux mobile OS, but I'm concerned that I won't be able to run them on my galaxy s21. What phones should I look for in order to properly run and install a linux OS without potentially getting my phone bricked? I'm very new to this whole ecosystem so any and all advice is appreciated.
As always we need to be spreading the narrative of fully unlocked hardware and FOSS drivers to these people who want to go the libhybris ex-android hardware direction.
Find more posts like this using this link https://redlib.perennialte.ch/r/linux/se...rict_sr=on
I have played around with my pinenote, and all was well. I am uncertain if it was I that messed up, but after a while the on-screen keyboard became unusable because the special keys stopped working.
Here is the problem, which appears in all apps, but let's say in a terminal: all normal keys work (for instance, typing ls). However, backspace does not, Enter does not. The result is that I cannot run any command in the terminal. Ctrl and Alt also seem to be broken
What I suspect is some setting got broken when I added and enabled some other keyboard layouts I use on most computers. I vaguely remember Enter did not work on those layouts, so I reverted back to the preinstalled "en" layout, but that one does not work. But I am not sure. I have been updating it via SSH, hoping for a fix, but only now I got some time aside to look into this.
I would like to recover this, since I have already configured it well. I can operate it via SSH, but I am unsure what to look for. I am mostly a Plasma user, so I am unfamiliar with Gnome applications and settings, but I can manage with gsettings and such.
I’d like to share my experience as a user of the PinePhone beta running Manjaro.
Despite a few imperfections – which I fully expect from a device that’s still close to a prototype – I’m actually very happy with it overall. It’s an exciting project, and I want to sincerely thank and congratulate the developers for the great work they’ve done so far.
If I may add a small remark: a slightly smaller screen might have helped improve battery life.
I understand that large screens are the trend nowadays, but some users like me mainly look for a more compact device, focused on basic daily features.
For me, the essential functions are:
making calls,
saving contacts,
sending text messages.
I find it very important to have a Linux smartphone that respects user privacy. With messaging evolving (and SMS being gradually replaced by RCS), I truly hope there will be a software update or even a future model that can cover this use case as well.
I also read here on the forum that RCS may not be such a good solution, since Google and Apple have basically taken it over with their own servers and apps, which turns it into another data collection system. Honestly, I used to think RCS was a good replacement for SMS, but now I’m not so sure… Does this really mean that traditional text messaging will eventually be fully replaced by RCS, despite all these privacy concerns?
One thing I honestly don’t quite understand is why Signal doesn’t support this project. From an ethical standpoint, a private and Linux-based phone perfectly aligns with the values they promote. It would make a lot of sense if they engaged more with initiatives like this.
Once again, congratulations on this project. Please keep it going – it really answers a real need for many users.
Thank you and best of luck with the ongoing development!
Recently I made the brave attempt to upgrade my PPP bought before 2023, with RK2AW.
The point with installing RK2AW is to get decent behavior in case of battery depletion - before RK2AW, if you deplete the battery, the phone would go into a battery-depleting perpetual loop and the only way to get the phone working again was to remove the USB and battery, push the Maskrom/RE PIN, and then boot the phone, and leave it like that for 10-20 hours.
sudo bash
cd /root
wget https://xff.cz/kernels/bootloaders-2024.04/ppp.tar.gz
sha256sum ppp.tar.gz
tar xvfz ppp.tar.gz
cd ppp
./spinor-flash-initial-setup.sh
And the outcome of this was that RK2AW with the "RKBIN" closed-source memory initialization blob + a recent U-Boot had been installed.
After that, I powered off the PPP, and disconnected USB and battery for 30 seconds. Not sure if all those steps are really needed but, after that definitely RK2AW worked as expected.
The issue came when I booted up PostMarketOS Edge with this new RK2AW-flashed PinePhone Pro:
The phone kept behaving as if I had tapped the volume up or volume down button, while I had not.
And meanwhile, the phone when in PostMarketOS stopped responding to when I actually pushed the volume button up or down.
I'm not sure if the issue is that I stopped using Tow-Boot and use U-Boot now, or if the issue lies in RK2AW.
Googling and asking Perplexity AI, I see that other people have had the same issue.
The quick fix is to disable the OS' event logics for when you push the volume button in the first place.
But, I cannot find any concrete suggestions for this fix.
I have also seen PostMarketOS insert gibberish in both directions into the UART data. It is so bad that the UART at least periodically becomes unusuable, because new gibberish is pushed every second, and often the gibberish is interpreted as special key combinations, that make you get logged out.
I saw some suggestion that at the root of this is a driver issue, so it sounds like it's fixed by including a particular Linux kernel patch into PMOS.
I tried with the latest PMOS Edge dated 20250830 and the problem is there too.
Did anyone have this problem too, can you share exactly how you fixed it?
Do you know any Linux distribution for PPP which has fixed the issue?
