after an reboot after an update my screen kept black after the kde logo. After messing around a rogognised that the backlight was of but the screen was working. With a strang lamp I was able to see enough to check the display brighness seams like it was set to zero. after setting it to a higher value everything was normal but setting the slider to a low value makes the phone unusable again.

It would be fine to make the allowed minimum high enough to actually see anything without an external light source.

Hello Community,

I am looking to buy a Pinetab with keyboard if anyone is interesting in selling one. I am in the USA.

Thanks,

As the title suggests, my problem is not related to any modem management software.

The first incoming call after the modem starts up works fine.
But after that first call, regardless of whether I answer it or not, new incoming calls won't go through - They won't even do the ringing tones on the other phone that I'm calling the PinePhone with.

If I had to guess, I'd say the modem is announcing to the network that it is busy or something like that, causing it to not receive any calls, because for what it seems, the call isn't even reaching the modem. Again, I'm just guessing, I don't really know how cellular networks work.
Is there any AT command that would set/unset some busy state like that?

If not, then I was hoping somebody could test to see if you get the same results:
1. Boot an OS and stop ModemManager (I suggest using an sxmo image, not sure how easy it would be to completely stop modem management on other UIs).
2. `sudo screen /dev/ttyUSB2` (or just use atinout or minicom if you prefer)
3. Unlock the SIM (AT+CPIN=<YOUR_SIM_PIN>)
4. Give yourself a call from another phone.
5. You should hear the ringing tones on the calling side.
6. The caller's number should show on the output of "AT+CLCC"
7. Hang up
8. Repeat from step 4. Does the call go through? Can you hear the beeping on the calling side? Does it show up on "AT+CLCC"? Cause for me it doesn't ;-(
9. If everything works without a problem, try again a couple more times just to be sure. It does have some unexpected behavior for me sometimes.

My firmware revision (AT+GMR) is EG25GGBR07A08M2G
Restoring the factory defaults with "AT&F" didn't fix it

Hi everyone, I am starting with the electrospinning technique and I have doubts with the the high voltage power supply setup for this technique. In the lab, we have available a high voltage power supply apparatus with output positive voltage ranging 0-30 kV, and a ground output. Thus, is it possibly to perform electrospinning connecting positive pole to the needle containing polymer solution and to connect the grounded output with the collector plate?



Thank you very much and I await your response,

I'm unable to flash Manjaro to my Pinephone.

I've flashed JumpDrive (pine64-pinephone.img.xz) to a MicroSD card inserted it into my PinePhone (I received the PostMarketOS Edition from last year).
The phone boots fine, and the eMMC flash is detected in my (Ubuntu 20.04) computer.

I'm then trying to flash Manjaro-ARM-plasma-mobile-pinephone-20210807.img.xz to the eMMC flash through USBImager, but it fails with the error "error opening device /dev/sdc: Device or resource busy".

I switched to balenaEtcher but it also fails with an unspecific error.

I think it may be because of the encryption on PostMarketOS, as I'm asked the passphrase to access the driver from either USBImager or balenaEtcher. So I went to Gparted to try to delete the partition and/or clear the encryption part, but it won't allow me to do either. What I could do is format the rootfs partition, but I did not help, and I'm still unable to flash Manjaro.

It looks like I'm the only one with this problem, and I'm stuck right now. Any idea?

Attached Files

Thumbnail(s)
       

Hi there,

for some time now, in bright environments (outside), I see pairs of horizontal lines on my screen, no matter if it's active or not.
They are interrupted in the area of about the analog watch face. Or maybe that's the area in which I touch it mostly. Can anyone tell me, if that is supposed to be like that or what it is and where that came from? Is it a hardware issue?

I tried to take a picture, but since the display's glass reflects pretty much, this was the best I could get:



Hopefully you can recognize those lines. That's pretty annoying, disturbing and simply doesn't look good.
Thanks for your answers!

Hey everyone!

I'm working on an iOS companion app for PineTimes running InfiniTime (and probably other similar watches/watch OSes, but I haven't tested anything yet). It's pretty bare bones right now, but so far it can:

• Scan nearby devices and allow the user to select a device to connect to
  
• Connect to a PineTime running InfiniTime 1.3.0
  
• Set time and date immediately after connection
  
• Read heart rate, and subscribe to HRM's notifier for updated values
  
• Read battery level, and subscribe to battery level's notifier for updated values
  
• Display heart rate, battery level, and connection/bluetooth/scanning status to app main page
  
• Write test notifications to the PineTime (I'm working on proper notifications right now)
  
• Listen for button presses in the InfiniTime music control app (so far I'm just printing button presses to console, but assuming I can figure out how to expose the app to the iOS music controls it should be pretty easy to tie in!)
  

I'm now using my Mobian/Phosh Pinephone as my daily driver and one thing I've noticed is that it's difficult to pick up a call in a timely manner when the phone is in suspend mode. Default for my carrier is to go to voicemail after 4 rings. In testing I found the Pinephone takes 2 rings to wake up and become responsive, but then you have to swipe the screen and put in your passcode to log in and take the call. By that time the call is going into voicemail.

I think if the swiping/passcode coming out of suspend could be eliminated it should be (just) possible to pickup calls before voicemail kicks in. Is there a way to do this?

Good Morning!  So it has been a few months and I have just about got the Pinephone where I want it.  It is used as my daily driver but regrettably when driving I must also bring my android wiretap with me for its GPS functionality.  I have seen people who seem to have been able to get their phone to work for navigation with a combination of GPS and puremaps however I never found a great tutorial on what they did to get to that point.  So now I must ask the question.  Which Distros work with GPS?  Which do not?  So far I have tried Manjaro Phosh as well as Plasma and Mobian and according to the maps app, I live in Columbia MO.  This tells me that the phone is not using GPS or cell tower but my ISP alone to determine my location. (About 100 miles or so off from where I actually am)  When driving it seems to get a lot more accurate.  Maps can at least tell that im on the correct highway but it is also a little bit off so I think in this scenario it is using the towers as the towers are close to the highway.  I have heard that Ubuntu Touch has GPS functionality so I was considering giving it a whirl but was curious if others knew of other Distros that worked as well?  How about UBports?  Also, of the Distros mentioned above, has anyone gotten Mobian or Manjaro to work with puremaps?  If so, what had to be done?  Are there any terminal commands that will get the GPS to print out my Lattitude and Longitude?  (I have attempted installing packages that would communicate with the Modem and GPS but in the end was unsuccessful)

Thoughts would be appreciated.
Thanks

I currently write a blog post about Podcast apps for the Pinephone and thought who would be a better help then the Pine64 community. I will keep a list here which I will update with the help of your comments later on so here is what I have so far:

• Kasts: The Plasma mobile and if I had to guess soon general KDE podcast app and my personal pick.
  
• GPodder adaptive: There is a branch of GPodder that aims to adapt to mobile screens and while the interface feels a bit rough around the edges I really like it!
  
• Gnome Podcasts: The Gnome podcast app.
  
• Pyrocast: A very nice Podcast app focused on streaming instead of downloading that sadly seems dead.
  
• Pods: I can't say I fully understand the interface but it's still heavily WIP so probably subject to change.
  
• PineCast: A nice very much WIP podcast app for the Pinephone.