Hello,

This thread is a fork from another thread, as requested by the OP.  First, here's a sum-up of what's been already discussed:

(03-09-2021, 11:15 AM)dsimic Wrote: When the phone is connected to the official dock, and a charger is plugged into the dock, shutting down the operating system causes the phone to power off and, unexpectedly, power back on immediately.  I've tested it more than a few times, and it always (mis)behaves like that.

(03-09-2021, 11:15 AM)dsimic Wrote:

(03-01-2021, 12:24 AM)GregH Wrote: Another side effect is that the device will not stay off with DCIN powered - no charging while switched off, it keeps booting up again :-(

This is pretty much the same behavior as with the official dock connected to the phone, which I've described earlier in this post.

After reviewing the relevant part of the available documentation for AXP803 (i.e. the PMIC), it's clear why this happens with 5 V applied to the DCIN pogo pin.  Basically, the PMIC detects the presence of valid input power voltage, which is satisfied in this case, and automatically begins the power-on procedure.  However, this doesn't explain the same behavior with the official dock plugged into the phone.

(03-14-2021, 08:29 PM)bokomaru Wrote: Phone -> USB C to A cable -> old "dumb" power brick -> AC wall outlet: Connecting the first time causes the phone to power on. But I can power the phone off from software, and then it stays "off".

Phone -> convergence dock -> USB C to a cable -> old "dumb" power brick -> AC wall outlet: Connecting the first time causes the phone to power on. After powering off the phone from software, the phone powers back on; won't stay "off".

(03-14-2021, 08:29 PM)bokomaru Wrote:

(03-14-2021, 07:42 AM)megous Wrote: anx7688 doesn't do anything unless the pinephone is powered on, so there's some fun to be had when charging via USB-PD chargers when the phone is off.

Maybe that's related to this, i.e., maybe the phone powers on by design, so that USB-PD can be negotiated if applicable.

I also remember reading that, for similar reasons, while charging, Android phones tend to be booted up. At least into the bootloader, and then the bootloader maybe knows to enter a different "charging indication" mode or to "stop here" until X or Y event happens.

Anyways, my point is that either of the two conflicting observations can happen, depending on which hardware you connect. If you want to reproduce my "off" test cases, try using a "dumb" brick without USB-PD.

If you follow the Mobian blog you may know there is an unstable branch now for those who want to test the cutting edge.

https://blog.mobian-project.org/posts/20...le-distro/

Some of you may be afraid to switch because you needs your phones to work and can't take the risk of something unstable upsetting that.

You can have your cake and eat it too. You can clone your drive via Balena Etcher onto an SD card or create an ISO image of it (back up) using Disks in Linux and burn it to an SD card. Even an encrypted drive. You should have a back up anyway. Use Jumpdrive on an SD to allow your computer to see the Emmc and don't decrypt it before cloning. Then you can use the SD card image for unstable and leave the Emmc alone. If things break you can just remove the SD card and still have a working phone in a pinch just by removing it. Make a change in the order of your favorite apps so you know what you are booted into. (exaple, put your phone on the left on the SD card image) The reason why is sometimes after an update on the Emmc your phone will only boot to the newer boot Image (the Emmc) but you can over ride that temporarily because some type of temporary FEL mode must be activated. Power and volume down will boot back into the SD card. Power and volume up will boot into the Emmc until the next update on the SD card. Then it will be normal boot priority with the SD card.

I'm trying to run OpenTTD on mobian pinephone and it doesn't work. I see that error above when starting it from the terminal. Trying to set a resolution manually with the -r flag didn't helped.

However if I run it with:

Video for Pinephone/Pinetab operating systems covering default pin numbers and showing why it is important to change them. 
[starting with small nmap/Hydra demo] Includes most common pin list.

Afterwards make some basic sshd_config file/pin recommendations to prevent it. 


Suitable for beginners and doesn't go into further key options: https://youtu.be/GAvGKlvKouY

Given so many are using SSH and not all familiar, thought it could be helpful. 

I'm currently trying to activate my phone with a att sim card but having issues activating it

Hi folks,

My phone arrived last week and, the anticipation was palpable. I was so happy to be rid of google / apple.

Everything seemed to work out of the box - except calls (microphone). No problem its probably the OS right?

I spend a few hours trying out different OS's, each having the same problem. Finally, by chance, I discovered that the microphone does indeed work when you hold / persuade the charging port towards the screen. It fails if you don't hold it.

Contacting support, I requested information on:
- the procedure to return the item, and
- the progress of the rest of the order (docking bar).

The not very prompt reply was to download the diagnostic OS and run the microphone test. The question regarding the rest of the order was completely ignored.

The Microphone failed the diagnostic test. (SURPRISE!!!)

Reporting this to support and waiting another day, I was advised to unscrew the phone and check that the cable connecting the charging port board was seated.
(Even though it still charged perfectly normally, but ok whatever, I'm talking to an expert right?)

Upon examining the interior of the phone, the charging port cable was indeed already seated (SURPRISE!!!)
I noticed that the charging port board was able to 'move' slightly around one of the screw mount points.

Reporting this to support, I was asked to provide a photograph.




After sending the photograph, I was advised that the photo would have to be sent to an engineer for examination.

Days later, I receive a request for my address, so a new charging port board could be sent for me to install myself.

At this point I advise support that I do not have the tools for any micro-soldering, and have no experience doing such phone surgery and would rather not risk it.

Support sends the link to a video of the operation, which I again advise I am not confident to do.

Support has now, advised my of an address in California to ship it to for examination... (I'm in Australia)



At this point I want to ask you guys... am I being unreasonable that I just want to get a refund now? this is turning into a time and money wasting poopshow.

I really just wish I could have got a phone that worked


Best regards all,
John

I've been running and old ayufan rock64 build of OMV (v4) - I set it up 2020-01

I had been getting the occasional issue with the un-powered USB3 HD (only USB device plugged in) where it needed to be remounted.

About a two weeks or so ago, ssh sessions would consistently freeze when I tried to "ls" a specific directory and/or issue "df". SD access seemed.

I tried with a powered USB hub, with no change.

I had a small collection of rock64's that I picked up cheap and swapped out the board from the case (with fan) and the same SD card/OS, case, PSU, USB HD and it immediately worked fined. Its been running fine for 11 days now - with no incidents.

I suspect there is something going on with the USB ports (I'm guessing damaged).

Any suggestions on how to test the ports? Other than "df" and try accessing random directories?

I have another rock64 that I deployed with Armbian and Docker (with Pi Hole in a container) its been running solid for 4 months (NOTE this only has a USB2serial device on it) so I suspect I either got a flakey board originally or something in my environment has damaged the USB ports.

NOTE I'm planning on using Armbian for all my boards, I just haven't made the time to move OMV to Armbian+OMV5 yet.

I have Rock64 that I want to use with this HDMI display by Waveshare: https://www.waveshare.com/wiki/7inch_HDM...with_case). It has native resolution of 1024x600 and that is the main problem.
I tried latest Armbian and latest Ubuntu 18.04 Bionic by ayufan. In first case it runs only 1080p and I can't set any other resolution, and haven't found any help on their forum, with the second image I can chose between multiple standard resolutions, but there is no native one and the image looks bad (obviously).
I tried to set native resolution with xrandr:

Hello everyone,

I just updated a cluster of Rock64 4G boards I have and they all forgot their MAC address now and have defaulted to 82:57:28:5d:f7:9d (no idea where this MAC comes from, the ones I had set where very different and started with "da:19:c8").

I was setting the MACs in the bootloader script via boot.txt and ./mkscr using this guide (wiki tab) but now that evidently does not work.

Asking that the OS side (forum post) did not produce much so I came here to ask:

How can I set the MAC of my Rock64s in uboot?

Thanks,
K

I am trying to make something like RockProBox, it means TV box using RockPro to replace my aging RockBox.

I guess it is more difficult than I thought.

First, it is impossible to find some working Android with Play Store AND working from EMMC. I found some Slash TV, but it does not boot from EMMC.

I was able to install PlayStore to Android 9, but Kodi does not run, it crashes just after start.

Ok, let me try Linux. Armbian looks good, it is fast and stable. It runs Kodi. It does not run RetroArch, because it is arm64 and Retroarch does not have the cores for arm64. Bang.

Ok, let me try Linux armhf. I chose Ayufan's Ubuntu Focal. It runs Kodi and Retroarch with the cores, but after a while the network is disconnected and I see the profgram crashed. So it is not stable.

Yes, there are some obscure OSs like Twister OS or Armbian Reforged, I tried that too, but there are still the OS in beta or development and I cannot even update them without breaking the things.

So, is there any working OS (Android with Play Store running from EMMC supporting Kodi)?
Or, is there any Linux distro armhf version that is stable?

I do not want to insult anyone, RockPro is surely great SBC, but it seems it is not suitable as a TV box replacement.