[26/09/2019] /e/ on pinebook, lineage derivative - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: Pinebook (https://forum.pine64.org/forumdisplay.php?fid=76) +--- Forum: Android on Pinebook (https://forum.pine64.org/forumdisplay.php?fid=78) +--- Thread: [26/09/2019] /e/ on pinebook, lineage derivative (/showthread.php?tid=7954) Pages:
1
2
|
RE: [26/09/2019] /e/ on pinebook, lineage derivative - tophneal - 12-10-2019 @Phie I thought I'd follow up, after charging up the PB and booting this last night, that this new image has major improvements! I didn't play with the camera at all, mostly because I saw on your site that it's still a WIP. So far the only things that have stood out to me are: 1. When I was on your site, reading the post about /e/ for the Pinebook and phone, you should a screenshot of the PB1080 with a Taskbar setup for the home screen, but the image uses the original launcher (which works much better with the trackpad now!) If the use of Taskbar is more of a "down-the-road" intention, I full-heartedly back this! 2. MicroG still has a problem somewhere. When going through settings to add my Google account into MicroG, it gets stuck at the last step, after signin and authorization. I did see a few emails go to my recovery email, and another to my Gmail, telling me I was now logged into my Samsung Galaxy 9, and ready to go. I didn't see any references in the system info to the Galaxy 9, but figured it was related to the image. Regardless of the email, I let the PB sit on the screen, "trying," for several hours, but it did not complete. I backed out of it later on, and despite the emails from Google, MicroG showed no account linked. I haven't had much time to play on it otherwise, but cursory impression is that it's a good build! Question: will you, or are you, considering including root for the user in any future builds? I know it's available to adb, but I think for the PB1080 it will drastically increase the usability as an Android laptop. RE: /e/ on pinebook, lineage derivative - Jeremiah Cornelius - 12-10-2019 (09-18-2019, 06:37 AM)Phie Wrote: Thanks for this feedback ! I build and maintain a non-supported image of /e/ for US variants of the Samsung S6 Edge, so this is really of interest to me. I won't touch ChromeOS or AndroidTV, because of the Play On libraries, but having microG built in as a replacement is fantastic. Between this and the advancement of a Debian Buster bootstrap build, I will have too many things to do once my PBP arrives. Thank you. — Jeremiah (09-17-2019, 12:09 PM)tophneal Wrote: After using this quite a bit since posted, I thought I'd give some impressions for anyone interested in this img. I maintain a phone build for /e/, and I'm pretty confident that you can't upgrade builtin apps and libraries like microG or the Camera app, without building a new image from source and specifying your customization in /srv/local_manifests/roomservice.xml of your build tree. That doesn't prevent alternatives from being installed on an existing image for apps, and changing the default handler actions. But microG would obviously need alternative sources provided on Github for an earlier version. The branch you pull from would also have to be labeled with the right version "lineageXX" tag, so you probably have to fork your own branch. A side note, /e/ and the foundation are headed by @gael_duval, who many may remember as the founder and original maintainer of Mandrake/Mandriva Linux, originally intended as a RedHat fork with full default KDE v1 desktop. He has a great Open Source ethic, and I'm glad for this vision being driven for a fully supported AOSP effort. — Jeremiah [26/09/2019] /e/ on pinebook, lineage derivative - tophneal - 12-10-2019 Thanks for that insight to why i couldnt do get microg to work. I didnt feel like messing with it much more on the more recent build, so im going to try pushing the play store over. I saw in your post what looked like potentially mistaking this image for the Pinebook Pro. Its not, Pinebook only. Just wanted to make sure it didnt get your hopes up and not work, since youve got a PBP on the way. One more question for @Phie , of the 2 USB ports on the PB1080, which should be used for adb access? I've got the debugging over USB enabled, but adb devices does not show the PB1080. RE: [26/09/2019] /e/ on pinebook, lineage derivative - Surehand53 - 03-22-2020 Hi all. There is a new (March 2020) version of /e/ available on their web site. https://doc.e.foundation/devices/pinebook/ (Dont't forget to edit the file for your pinebook version (batch1, batch2, 1080p) I use it from a micrSD card and it works really well. There are ocasional glitches with the display driver, but it seems this is just inconvenient and not a ign of immediate doom. In standard /e/ Bliss launcer only shows one page of apps, so all the other apps that are actually there can only be accessed via search screen and then type the name of the app. e.g. camera or task The Bliss launcher does not usilise the whole screen yet, but I guess that might come in later releases ? The app store works nicely and you can also add F-Droid as an additional pure open source app store. All in all this version is quite usable, the camera works and so the OG Pinebook is a super Jitsi conference computer. There is a bit lag though. All in ll it works surprisingly well. Android does not provide many keyboard shortcuts out if the box, but it is usable. Great update EDIT: For first time users, the first boot takes quite some time to come up. You will be looking at a blank screen for a while (depending on the speed of your SD card). This is the same behavior as other /e/ first boots have on mobile phones and seems to be normal for /e/. Next boot is faster. RE: [26/09/2019] /e/ on pinebook, lineage derivative - e-minguez - 03-22-2020 (03-22-2020, 07:50 AM)Surehand53 Wrote: Hi all. I tried that build yesterday in a sd card but the graphical glitches made the wizard impossible to finish RE: [26/09/2019] /e/ on pinebook, lineage derivative - Surehand53 - 03-23-2020 Hi I had these glitches as well, If it is of any help, just press skip to all questions, you can do everything later. The only thing I have set up was the localisation. That was a bit messy but eventually worked. I use a 1080 Pinebook. The only help I can offer is that these graphic glitches are not the first steps of a crash, it sometimes comes and then quickly also goes. I have used /e/ for hours now and there are some problems, mostly because I don't know how to use Android with Keyboard and Mouse, but it hasnever crashed in that time. So the graphic problem usually only stops you for a few seconds and then goes away. I have not found a pattern yet. Switching apps with Alt-Tab seems to calm things down. But if you want to try again, it should actually work. RE: [26/09/2019] /e/ on pinebook, lineage derivative - Surehand53 - 03-29-2020 # E on the Pinebook Here is a short summary for /e/ on the Pinebook 1080p and what works, some glitsches and most importantly, how to navigate /e/ on the Pinebook with touchpad and keyboard. If anyone else has more shortcuts or mouse gestures that work I would be very interested. ## What works nicely - Sound - Video - Keyboard - Touchpad - Camera - Wifi - Bluetooth (tested with a loudspeaker) ## Some niggl - Graphic glitshes, every now and then the screen flickers. However, this seems to always go away without consequences [Issue #1092](https://gitlab.e.foundation/e/management/issues/1092) - Only one home screen, no additional screens are shown, that means not all apps are directly accessible [Issue 1093](https://gitlab.e.foundation/e/management/issues/1093) - Menu key has no clear function on home screen, in my case it opens Firefox most of the time. This seems a missed opportunity for more keyboard shortcuts, however I don't even know if Android and /e/ support that. - SOMETIMES THE KEYBOARD THINKS IT IS IN CAPS LOCK MODE. I have not found out what triggers that or what turns it off. This seems unrelated to the actual Caps Lock key. ## Keyboard shortcuts: As the touchpad is not a complete substitute for a touchscreen, the keyboard operation of /e/ is more important. Here are the keyboard shortcuts that I have figured out to work so far. ### /e/ Keyboard shortcuts: Navigation - Alt-Tab : Switch between apps - Menu button: In a app it activates the App Menu - Menu button: On the Homescreen (Launcher) the function is less clear, in my case it opens Firefox when you press a bit longer. ### /e/ Keyboard Shortcuts: Typing - Alt + Del: Delete an entire line - CTRL + X: Cut text (will cut all text on-screen unless specific characters are highlighted) - CTRL + C: Copy text to clipboard (will copy all text on-screen unless specific characters are highlighted) - CTRL + V: Paste text from clipboard - CTRL + A: Select all text in the current field - Alt (no other key): Get the menu for emojies ### /e/ Keyboard Shortcuts: Scrolling - Spacebar: Page down in any Web page/document view - Shift + Spacebar: Page up in any Web page/document view ## Mouse gestures The touchpad emulates some touchsreen gestures to use /e/. This is what I have found so far - Swipe Screens: On the home screen (launcher) click and hold, then swipe left or right to get to different screens on the Bliss Launcher. - Spell correction: If a word is underlined red, click with one finger to see the context menu - Two finger scrolling works, however it not natural scrolling, so it feels the wrong way around - Shift + Touchpad-Left/Right: Highlight text for cutting or copying ## Starting an app If the app is on the home screen, you can start it from there. However, if your app is not on the Home screen and you cannot see it you can still start it from the Search screen. To get there double tab the touchpad to create a left click, keep your finger on the touchpad and move it to the right, so essentially swiping to the Search screen. |