![]() |
debian+phosh running on PinePhone - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120) +--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121) +---- Forum: Mobian on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=139) +---- Thread: debian+phosh running on PinePhone (/showthread.php?tid=9016) |
RE: debian+phosh running on PinePhone - a-wai - 03-22-2020 New release time, version 20200322 is available ![]() This one comes with a bunch of small but useful improvements: - upgrade phosh to latest version - ambient light and proximity sensor now works and is used by phosh to set the display's brightness and disable touch/display when relevant - hacked geary's account dialog in order to make it usable on the PP - headset microphone is now supported - added a "headset" button to Calls in order to switch between headset and earpiece+internal mic There is a small issue with the Speaker/Headset buttons in Calls: the state of the audio routing is normally the same used for the previous call, but this isn't reflected in the UI For example, if you make a call using the headset, the next one will use the headset too, but the "Headset" button will show as if it was disabled. In order to revert to internal earpiece+mic, you'll have to press it twice (force headset routing then revert to internal routing). Also, the Geary account dialog might take a few seconds to react when selecting the mail provider, please be patient and don't frenetically select your provider again and again ![]() (03-21-2020, 02:30 PM)buffer Wrote: Checking alsamixer again (press F6 - select 1- Pinephone sound card), I see that when I change mic profile from Default to Phone, or from Phone to Default, in phosh sound settings, both Mic1 and Mic2 are muted. However (press F6 again - select 0- Default) on the main menu the capture device remains unmuted. However, unmuting the mics does not help make sound get recorded.Well, I think I understand your issue, and really, when saying "out of the box", I mean "out of the box": you shouldn't need to fiddle with alsamixer or other more or less hidden settings, all the necessary configuration is already built-in. In order to check whether it's a hardware issue with your phone's mic, flash the latest image to an SD card and boot it, then plug a headset in, and make a call. Touch the "Headset" button, and try talking into the headset's mic; if it works this way, then your phone's internal mic is probably dead, sorry... bcnaz Wrote:Wanted to add : I am pretty much just a GUI driver, so I would like to find ways to contribute , you guys are putting some excellent efforts into this project. Contributing with no technical skills is a bit difficult for now as a lot still needs to happen under the hood, but you can help by keeping the wiki section up-to-date or improving it, answering to others on this forum, and so on... Regarding donations: I never considered that aspect for this project, but for those really wanting to donate, I have an old Liberapay account I never really used so far... Thank you all for your support, bug reports and kind words, every one of those is highly appreciated ![]() (03-22-2020, 05:38 AM)buskmann Wrote: Did a "sudo apt upgrade" for more or less one hour ago, and it stopped at 84%. Last thing it put out was: e2scrub_all.service is a disabled or a static unit not running, not starting it.Hmmm, I had a similar issue, could you share the full apt log so I can double-check with mine? RE: debian+phosh running on PinePhone - buskmann - 03-22-2020 (03-22-2020, 06:06 AM)a-wai Wrote:(03-22-2020, 05:38 AM)buskmann Wrote: Did a "sudo apt upgrade" for more or less one hour ago, and it stopped at 84%. Last thing it put out was: e2scrub_all.service is a disabled or a static unit not running, not starting it.Hmmm, I had a similar issue, could you share the full apt log so I can double-check with mine? Dont know if this works, but i Attached the logfile to this post.. Its a bit to big to post here ![]() Just in case, heres the last part: (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 69240 files and directories currently installed.) Preparing to unpack .../00-libasan5_9.3.0-6_arm64.deb ... Unpacking libasan5:arm64 (9.3.0-6) over (9.3.0-5) ... Preparing to unpack .../01-g++-9_9.3.0-6_arm64.deb ... Unpacking g++-9 (9.3.0-6) over (9.3.0-5) ... Preparing to unpack .../02-gcc-9_9.3.0-6_arm64.deb ... Unpacking gcc-9 (9.3.0-6) over (9.3.0-5) ... Preparing to unpack .../03-libstdc++-9-dev_9.3.0-6_arm64.deb ... Unpacking libstdc++-9-dev:arm64 (9.3.0-6) over (9.3.0-5) ... Preparing to unpack .../04-libgcc-9-dev_9.3.0-6_arm64.deb ... Unpacking libgcc-9-dev:arm64 (9.3.0-6) over (9.3.0-5) ... Preparing to unpack .../05-cpp-9_9.3.0-6_arm64.deb ... Unpacking cpp-9 (9.3.0-6) over (9.3.0-5) ... Preparing to unpack .../06-gcc-9-base_9.3.0-6_arm64.deb ... Unpacking gcc-9-base:arm64 (9.3.0-6) over (9.3.0-5) ... Preparing to unpack .../07-libibus-1.0-5_1.5.22-2_arm64.deb ... Unpacking libibus-1.0-5:arm64 (1.5.22-2) over (1.5.22-1) ... Preparing to unpack .../08-gir1.2-ibus-1.0_1.5.22-2_arm64.deb ... Unpacking gir1.2-ibus-1.0:arm64 (1.5.22-2) over (1.5.22-1) ... Preparing to unpack .../09-gnome-session-bin_3.36.0-2_arm64.deb ... Unpacking gnome-session-bin (3.36.0-2) over (3.36.0-1) ... Preparing to unpack .../10-gnome-session_3.36.0-2_all.deb ... Unpacking gnome-session (3.36.0-2) over (3.36.0-1) ... Preparing to unpack .../11-gnome-session-common_3.36.0-2_all.deb ... Unpacking gnome-session-common (3.36.0-2) over (3.36.0-1) ... Preparing to unpack .../12-libcom-err2_1.45.6-1_arm64.deb ... Unpacking libcom-err2:arm64 (1.45.6-1) over (1.45.5-2) ... Preparing to unpack .../13-libgtk3-perl_0.037-1_all.deb ... Unpacking libgtk3-perl (0.037-1) over (0.036-2) ... Preparing to unpack .../14-libss2_1.45.6-1_arm64.deb ... Unpacking libss2:arm64 (1.45.6-1) over (1.45.5-2) ... Preparing to unpack .../15-pci.ids_0.0~2020.03.20-1_all.deb ... Unpacking pci.ids (0.0~2020.03.20-1) over (0.0~2020.02.22-1) ... Preparing to unpack .../16-sudo_1.8.31p1-1_arm64.deb ... Unpacking sudo (1.8.31p1-1) over (1.8.31-1) ... Preparing to unpack .../17-pinephone-modem-scripts_0.4_arm64.deb ... Unpacking pinephone-modem-scripts (0.4) over (0.3) ... Preparing to unpack .../18-pinephone-base_0.2.4_arm64.deb ... Unpacking pinephone-base (0.2.4) over (0.2.3) ... Preparing to unpack .../19-pinephone-multimedia_0.2.4_arm64.deb ... Unpacking pinephone-multimedia (0.2.4) over (0.2.3) ... Preparing to unpack .../20-pinephone-tweaks_0.4_arm64.deb ... Unpacking pinephone-tweaks (0.4) over (0.3) ... Setting up pci.ids (0.0~2020.03.20-1) ... Setting up pinephone-multimedia (0.2.4) ... Setting up libibus-1.0-5:arm64 (1.5.22-2) ... Setting up gnome-session-bin (3.36.0-2) ... Setting up libcom-err2:arm64 (1.45.6-1) ... Setting up libgomp1:arm64 (10-20200321-1) ... Setting up pinephone-modem-scripts (0.4) ... Setting up libatomic1:arm64 (10-20200321-1) ... Setting up libss2:arm64 (1.45.6-1) ... Setting up sudo (1.8.31p1-1) ... Setting up logsave (1.45.6-1) ... Setting up libubsan1:arm64 (10-20200321-1) ... Setting up gnome-session-common (3.36.0-2) ... Setting up gir1.2-ibus-1.0:arm64 (1.5.22-2) ... Setting up libcc1-0:arm64 (10-20200321-1) ... Setting up liblsan0:arm64 (10-20200321-1) ... Setting up libgtk3-perl (0.037-1) ... Setting up libitm1:arm64 (10-20200321-1) ... Setting up libpython3-stdlib:arm64 (3.8.2-2) ... Setting up gcc-9-base:arm64 (9.3.0-6) ... Setting up libtsan0:arm64 (10-20200321-1) ... Setting up pinephone-tweaks (0.4) ... Creating boot script... Image Name: pinephone Created: Sun Mar 22 10:57:41 2020 Image Type: AArch64 Linux Script (uncompressed) Data Size: 811 Bytes = 0.79 KiB = 0.00 MiB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 803 Bytes = 0.78 KiB = 0.00 MiB Setting up e2fsprogs (1.45.6-1) ... Installing new version of config file /etc/mke2fs.conf ... update-initramfs: deferring update (trigger activated) e2scrub_all.service is a disabled or a static unit not running, not starting it. RE: debian+phosh running on PinePhone - a-wai - 03-22-2020 Hmmm, nothing really stands out as to why it crashed... Did you try "sudo dpkg --configure -a" after rebooting ? RE: debian+phosh running on PinePhone - buskmann - 03-22-2020 Did it now. Heres the output: Setting up python3 (3.8.2-2) ... running python rtupdate hooks for python3.8... running python post-rtupdate hooks for python3.8... Setting up libasan5:arm64 (9.3.0-6) ... Setting up pinephone-base (0.2.4) ... Setting up cpp-9 (9.3.0-6) ... Setting up libgcc-9-dev:arm64 (9.3.0-6) ... Setting up gcc-9 (9.3.0-6) ... Setting up libstdc++-9-dev:arm64 (9.3.0-6) ... Setting up g++-9 (9.3.0-6) ... Processing triggers for desktop-file-utils (0.24-1) ... Processing triggers for mime-support (3.64) ... Processing triggers for initramfs-tools (0.136) ... update-initramfs: Generating /boot/initrd.img-5.5-pinephone Processing triggers for libglib2.0-0:arm64 (2.64.1-1) ... Processing triggers for libc-bin (2.30-2) ... Processing triggers for systemd (245.2-1+pinephone1) ... Processing triggers for man-db (2.9.1-1) ... Setting up gnome-session (3.36.0-2) ... I have just built my first image now, so gonna flash it today.. RE: debian+phosh running on PinePhone - visiblink - 03-22-2020 I gave the new image a try today. It looks good. I love being able to run Debian on my phone. I didn't try the phone functions, but was listening to music with mplayer in the terminal, tried out a little browsing with Midori and Lynx, etc. The battery life seems relatively good too. RE: debian+phosh running on PinePhone - bcnaz - 03-22-2020 The Contact book and the texting work ok, but when I click on 'start chat' there are double entries of every name in the contact book ? The second one of each has the name but no phone number. The other has all the info entered. Not a big deal, but thought I would mention it. RE: debian+phosh running on PinePhone - buskmann - 03-22-2020 I was trying to change the username, so i logged in via ssh as root, and did: pkill -9 -u `id -u debian` usermod -l buskmann debian usermod -m -d /home/buskmann buskmann Now the phone wont log in and start phosh. I assume that some auto login file that has the username "debian" in it or something. If so, what file should i edit to get my username in there? And is it maybe possible to use "uid" instead of username? RE: debian+phosh running on PinePhone - rico - 03-23-2020 (03-22-2020, 08:34 PM)buskmann Wrote: I was trying to change the username, so i logged in via ssh as root, and did: Please have a look : https://forum.pine64.org/showthread.php?tid=9016&pid=62245#pid62245 RE: debian+phosh running on PinePhone - buskmann - 03-23-2020 Thank you for directing me. I havent read threw all the pages of this forum, but now i read everything. So I installed gdm3, and setup auto login, and now it works. ![]() But i think im going to reflash and keep the user to "debian". Im writing my own little afterinstall script to make the changes i want on it, like pwfeedback is sudo, growpart and keyboard layout. But the part with changing the user seems like its not worth it. Im learning a lot from this now, and its really fun. I live in Spain, where we have nationwide quarantine, so i have to have something like this to occupy me, or else i would go crazy.. RE: debian+phosh running on PinePhone - rico - 03-23-2020 Ok, This message for @a-wai I think it works ![]() Send from my 5mn hotspot //Edit a 10mn But PP charging. Gonna unplug in one minute. //Edit Unplugging //Edit Ok Still on battery.. //Edit Just cut the hotspot |