yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] mickybart:
I have not a lot of time to work on this project with the release of nAOSP b11 but once done I will rework on it and provides binaries for Devs.

But, I think that this "new OS" powered with plasma is a good choice and I'm happy to see that plasma 5.7 integrate such kind of features :

https://www.kde.org/announcements/plasma-5.7.0.php

https://blog.martin-graesslin.com/blog/2016/05/virtual-keyboard-support-in-kwinwayland-5-7/

Great improvement have been done on Wayland support too.

If some of you are interesting to do some packaging with Archlinux, I'm really interested to get some help to provide a usable system for end user. The work for now is more too package/install user tools (so integration of components). I miss pulseaudio and ofono patching but I'm optimist to solve every issues.
[Sony Xperia S, Acro S, Ion] mickybart:
finally nAOSP 6.0 b11 and b12 took me more time than expected but I'm back on this project.

For information, I updated everything to Qt 5.7.x support.

Some pull request have been done and are in discussion for at least qt5-qpa-hwcomposer-plugin (mer-hybris).

I decided to don't provide binaries for now as there is not a lot of sense to do it except if you are interesting to help the project (mainly to package some stuffs, integrate tools for GPS, ofono, pulseaudio etc).

I just finalized to record a small video. I will cut it and upload it to prove that archlinux arm phone can be a reality with the proposed new architecture (and on our Xperia S).

I will work again on the kwin/libinput issue. Maybe just a logind/dbus/kwin discussion issue. Once fixed that should permit to have a graphical keyboard by default (I know that for iOS or Android this is normal... but not really on a GNU/Linux desktop) !

I continue to look for help on this project and if you can create some packages like the one for plasma-mobile and derived repo let me know in PM or in the thread.
[Sony Xperia S, Acro S, Ion] mickybart:
small video of the project

https://vimeo.com/177893595
[Sony Xperia S, Acro S, Ion] mickybart:
Great achievement today :)

libinput is working and so I'm now able to move windows, plug a keyboard to write a text file, plug the mouse (pointer is not visible) ...

Menus are well displayed now with the good size.

Next steps : pulseaudio, wifi, plasma-mobile... (and bug fix on the kwin backend).
[Sony Xperia S, Acro S, Ion] Seemanthinis:
wow mickybart !. u just struck my interest in coming back to this phone! amazing work. my phone was unusable and parts needed replacement. looking at the activity of yours in this section made me repair the device and try out your work.. cheers mate! keep going with ur awesome work!
[Sony Xperia S, Acro S, Ion] latgarf1:
OnePlus X (onyx) port

I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
[Sony Xperia S, Acro S, Ion] nik012003:
I have a Sony Xperia S and a OnePlus One and I'd like this port!

On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.

I really like this on my "old" Xperia S !
[Sony Xperia S, Acro S, Ion] mickybart:
Hi [MENTION=7243690]latgarf1[/MENTION],

Sorry for my late answer. I'm busy with Android 7.

That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future :).

I will ask a moderator if we can move this thread to a general one.

Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.

But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.

So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.

The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.

I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.

Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync :)).

I'm really interested to have some help to speed up this project and to have more motivation for it :)

You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).

Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop :)).

Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?

For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
[Sony Xperia S, Acro S, Ion] bigsupersquid:
I've not tried arch but have attempted similar to this project with Debian (raspbian) on ancient hardware with partial success.

As free time rears its rare head I'll be trying to adapt your project for my newer HTC based on cm13.

By the way, your work on N ril from github is great, allows my cm14 to get/make calls without rebooting. Now if I can just figure out why rild takes forever to stop dying and respawing and start actually running...
[Sony Xperia S, Acro S, Ion] nik012003:
I don't know how the audio works but I know that it works.

This is the ubports repo https://github.com/ubports?tab=repositories

If you want me to type some commands on the ubuntu touch terminal let me know.

EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.

https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
[Sony Xperia S, Acro S, Ion] mickybart:
Thanks. I will give it a try but to have a more automatic process I will maybe follow what is done in mer-hybris :

https://github.com/mer-hybris/pulseaudio-modules-droid
[Sony Xperia S, Acro S, Ion] abhifx:
accidentally discovered this, and this is absolutely fantastic. a true mobile linux using existing parts. always one of my dream. keep up the good work. i know i cant help here, but surely appreciate what is happening here. huge undertaking, this project needs tons more devs and devices. plasma mobile is perfect for this (but is also on a nascent stage.
[Sony Xperia S, Acro S, Ion] ruleh:
Wow, this actually exists. This is a dream come true :) .

I was trying something similar on my asus zf2 but failed horribly at getting libhybris to work.

Is there any chance of porting this to devices with x86 cpus?

If yes, what are the extra things to be aware of in comparison to arm cpus?

Also libhybris_ext still uses the jb linker (iirc), does it work with an android 6.0 base or is the mm linker needed?
[Sony Xperia S, Acro S, Ion] mickybart:
In therory that can work on x86 too but I have nothing to try it (and unfortunately I have not a lot of time to work on this project despit it is interesting...)

You should not need to work on the GPU part as at my knowledge x86 devices are using intel gpu that is supported by gnu/linux already (mesa/gallium/drm). So all stuff like kwin-hybris should not be needed at all so it is much more easier :)

libhybris_ext should be able to work on android 6.0 but I have not yet done the effort to port and try it.
[Sony Xperia S, Acro S, Ion] mickybart:
Do you know if the thread can be moved in another category to have a better view of this project at Xda ?
[Sony Xperia S, Acro S, Ion] marshel:
This really is a very nice project. Some things reminds me of my old Nokia N800 Tablet, running a Debian derivated MaemoOS that evolved later into MeegoOS and then Tizen. Despite the old ARM processor and 128M RAM, It had the same specs as iphone and a step foward on UI, a beautiful Hardware Design for the time with a turnable webcam, a builtin stand, a clear 800x480 4,3' screen, Two SD slots plus internal storage, USB host, Bluetooth, Wifi. Only the GPU that had not the correct modules because of Broadcom's lack of interest.

I suggest seeing the maemo.org maybe some ideas may come from there ...
[Sony Xperia S, Acro S, Ion] ruleh:
Sadly the powervr gpu on the zenfone2 has no gnu/linux support.

An early attempt to get libhybris_ext working on its x86 cpu resulted in segfaults.

I suspect that this might be related to bionic patch I am using (more specifically the tls slots part of the patch).

However I am now trying to port sailfishos onto this device, maybe libhybris will work from there.
[Sony Xperia S, Acro S, Ion] moe18:
maybe if you contact a moderator he can do it. i would do it but i know no one
[Sony Xperia S, Acro S, Ion] mirhl:
http://blog.bshah.in/2016/12/28/cyanogenmod-lineage-os-and-plasma-mobile/
[Sony Xperia S, Acro S, Ion] mad_fitter:
This project looks awesome! I'd love to try to help port this to the OnePlus 2!
[Sony Xperia S, Acro S, Ion] mickybart:
I have not provided any feedback, but Bhushan Shah contacted me to have some input about the project and to study 2 way of work.

This was an interesting discussion.

For now the project is on hold due to lack of time and devices to dev. But I just fixed a Galaxy S3 supported by LineageOS so I'm thinking to port what is done for AOSP 5.1.1 to LineageOS 7.1.1 and to dedicate this Galaxy to continue the dev during my free time.
[Sony Xperia S, Acro S, Ion] mirhl:
This got me thinking how much XS is far from getting a kernel nudge.
[Sony Xperia S, Acro S, Ion] mickybart:
Bad news but not a so big surprise...

https://insights.ubuntu.com/2017/04...ud-and-iot-rather-than-phone-and-convergence/
[Sony Xperia S, Acro S, Ion] mirhl:
How's that related to an archlinux/kde system?
[Sony Xperia S, Acro S, Ion] mickybart:
For KDE there is nothing relative (wayland / KDE vs Mir / Unity). But for a "lot" of other things you have some common stuff. Ubuntu and Archlinux are both GNU/Linux distribution so they can share some code (ofono, geolocalisation, telepathy ofono, sensors qt plugin, mobile applications, pulseaudio plugin for android mixer path ...). Ubuntu Touch was using Qt for his platform so this is always interesting in a KDE environment.

Now we still have mir-hybris (Sailfish is based on Mir) and nothing else in the attempt to have a GNU/Linux on phone (Yes I don't consider my project enough advanced to include it despite I'm happy of the road already done) so yes this is a bad news because we will have less people to contribute and maintain some common stuff.

But this is not over and I know that plasma mobile team (discussed 2 days ago) are using some part of my archlinux stuff to create an image that will be based on AOSP/Archlinux/Ubuntu Neon.

I have a picture of a Nexus 5X booted and with plasma lockscreen displayed :)
[Sony Xperia S, Acro S, Ion] mirhl:
Uh, cool.

Relevant then.
[Sony Xperia S, Acro S, Ion] mickybart:
It is not official now but as someone leaked the information, a new project "Halium" is in discussion (I joined it, invited by Bhushan).

More detail should be officially available really soon.

https://www.phoronix.com/scan.php?page=news_item&px=New-Mobile-Linux-Base

https://www.generationamiga.com/2017/04/17/project-halium-collaboration-on-common-android-base/
[Sony Xperia S, Acro S, Ion] worlddevelopment:
Just wow! Let's drive this further. Unfortunately can't help with coding due to other project focus currently, therefore donating 5$/month.

As a Void Linux enthusiast, I'd love to ultimately get that going. Could be easier than Arch due to Runit init system.

Any success using ALSA without pulseaudio? (for Void tips see troubleshooters.com/linux/void/voidtips.htm though I use OpenBox which simplifies things even more)
[Sony Xperia S, Acro S, Ion] mickybart:
Project is still alive and I have more motivation with the Halium initiative :)

I'm working on Halium project with great people :)

So I just updated every packages and there is some plasma mobile packages available that I will try soon.

The rootfs builder is now in place and an image can be done automatically :)

Qt virtual keyboard should be able to work.

I will work to change schroot to lxc to fit Halium. If the renderer is stabilized and plasma mobile able to work I hope to release a first real alpha :)

I will integrate fdmem in the kernel too.
[Sony Xperia S, Acro S, Ion] worlddevelopment:
Very great news, [MENTION=6043081]mickybart[/MENTION]! Thank you and Halium team.

Which phone do you recommend to be future proof for Halium| especially your ArchLinux works?

(I have understood, that there is no way around systemd currently. So ArchLinux it is.)

Which are the relevant repositories on Github for a minimalistic non GUI ArchLinux? Is it only GNU_support? Just trying to understand your magic better. :fingers-crossed:
[Sony Xperia S, Acro S, Ion] Darkorn:
What about PostmarketOS? Isn't the goal similar to this project?
[Sony Xperia S, Acro S, Ion] mirhl:
Noble scope and all, but no way you can consider freedreno/mesa usable.

Then perhaps in the future it may even become a thing, on way newer phones. Very hardly on A2xx.

EDIT: just checked gpu/drm/msm better, and A2xx doesn't even seem mainlined at all.

EDIT2: and it makes sense too. That's actually what the wiki was saying.

For some relatively petty reason, A2xx never got support of official DRM/KMS mainline driver.

I.e. we are stuck with the other one, KGSL, that qualcomm in all its infinite almost-openness got refused long time ago.

It's a bit *****y to get to work with freedreno userspace - still it should work too.

Only pity is that since maintainer could never work on it on actual hardware, the thing misses tons and tons of polishing, aside of what I assume mostly guesswork.

So, the proper way forward™ imo seems to be getting whatever it needs for S3 to work on 3.10 (where some branches that didn't drop A2xx even exist and are still getting updated today!) - then hoping that's similar enough to modern kernels not to spoil the fun of coding to good Rob (if he still has some spare dragonboard available)

EDIT3: very, very interesting bases.
[Sony Xperia S, Acro S, Ion] mickybart:
No because PostmarketOS do not use glibc and libhybris so there is not a full Android hardware support. The GPU is not supported and FB is used for example.

In fact Archlinux can works on top of Halium. So any phone well supported by Halium can do the job.

You can use any init but Halium will focus only on systemd as it is used by so many major distribution. Systemd is working fine but of course we can't use every systemd features due to the kernel level.

For a non-GUI archlinux (or maybe you mean non-libhybris), pretty much everything is working for Xperia S already (so I mean, wifi, boot, usb port). Bluetooth is untested.

So you just need the kernel and initrd of the gnulinux_support repository for that.

You can create a rootfs with this project:

https://github.com/mickybart/rootfs-builder/tree/archlinux

This is the one used for Archlinux/Halium but not everything is merged. You just need to remove the halium.list part on customization/halium/package-lists.

You can follow halium website or telegram too.
[Sony Xperia S, Acro S, Ion] bigsupersquid:
I didn't see a direct link for the halium project, so dug one up myself.

https://halium.org/

Nice work, I need to look into Arch on phones. My previous attempts have all been using Debian or Ubuntu. Never did get ofono or libhybris working while I was directly booting Linux, but WiFi and Bluetooth worked ok with a bit of GL acceleration from freedreno libs on the old adreno 200.

Nice that Arch supports armv6 and armv5te as well... Ubuntu stopped long ago and, while Debian supports older chips, it seems harder to configure hardware.
[Sony Xperia S, Acro S, Ion] mirhl:
[MENTION=6043081]mickybart[/MENTION]

https://github.com/flto/linux-next/commits/tenderloin
[Sony Xperia S, Acro S, Ion] worlddevelopment:
Excuse me sir, which commits are you referring to explicitely? Has something happened on linux-next that makes us reach a full easy to use GUI linux on ARM phones soon?

I heard about improvements to lib input related to touch. Reliable open AI comprehension of human-like languages for real voice control might still be unavailable but proper [multi-]touch input on linux looks O.K.

https://elixir.bootlin.com/linux/latest/source/drivers/hid/hid-multitouch.c

https://wiki.archlinux.org/index.php/Touchscreen

mickybart, wifi and serial communication is enough, bluetooth is not important to me. I wondered whether one might create an open phone using beaglebone blue. It has wifi, we can add an XBee with GSM or LTE, sim card slot, Kernel-well supported touch screen and print a nice case or make it fit elegant available ones and there we go ...
[Sony Xperia S, Acro S, Ion] mirhl:
That already happened. Check postmarketOS for other newer xperia devices.

The commits I'm referring to with relevance to fuji are those concerning the adreno 2xx gpu which, obviously, is the elephant in the room.

I don't know what you are over about then. It's not like we are even 1/4 done here.

Mickybart announced his retirement besides, so RIP.
[Sony Xperia S, Acro S, Ion] worlddevelopment:
The GPU is the elephant in the room not to a phone as a communication device.

If you think of a phone like a media device, then this statement is true. Or did I miss something and CPU-rendered minimal Xorg or Wayland + Openbox or other lightweight DE GUI is not possible on a CPU only system?

The idea with Convergence is to have programs written once and run on all devices. Write a bash script that queries your server services or does network analysis and information gathering while abroad or on the road via voice control.

This is the definition of a modern phone to real world applications for real world people. Not playing games to get time pass by. Time is already rare because tech probs are very wide spread nowadays. In this sense it is understandable that Mickybart retired.

Still convergence will not retire at all.

If you say we are 1/4 here, then why not break the problem to the most minimal configuration. Why even deal with an elephant if one can leave it alone in peace and smartly bypass it. This is what ArchLinux is about in the first place. KISS.
[Sony Xperia S, Acro S, Ion] mirhl:
CPU compositing would suck on a desktop, let alone a senior phone.

And I'm totally shocked by whatever regard of "real people" you have - while talking about nuking 90% of what the phone could even afford to do.
[Sony Xperia S, Acro S, Ion] worlddevelopment:
On a desktop with the proper display sizes and input devices just play or 3D create or heavy GPU GUI enjoy in general what you want. Just joking. Has nothing to do with being real or not. That wording I chose was not helpful. I just wanted to provoke people to rethink the convergence goals to start with basics, i.e. GPU optional.

This would make our lives easier because no doubt you are right, GPU is the elephant in the room. Aren't most GPU closed source anyway. Isn't it an illusion to be able to keep up with the pace of GPU companies with freetime effort?

There is a reason why Linux has issues with modern graphics cards.

Any evidence for it sucking btw.? Sucking is application dependent. I have a CPU only PC since decades. No issue even with heavy blender3d use. Maybe it's because I am on slick ArchLinux. :highfive:

Intelligence and speech and other algorithms surely not "nuke 90%" of what the phone could do.

Do you know 0A.D.? It is not the GUI that leads to performance issues. It's the algorithms (like pathfinding) that are costly. And those do not need a GUI. I remember profiling showing the graphics is just a tiny fraction of the time spent. Unfortunately GPU coding is not easy with OpenGL and who really is a Vulcan coding expert?

For many open source efforts nowadays not even full OpenGL support is there and Vulcan is far away. Simply because it is work, a lot of work. ;) And now you tell me the GPU is worth it? Won't we fall far behind and apart. Exhausted resources of some few well-motivated humans. At some point devs abandon projects. That's often because momentum is less than the overwhelming amount of work to be done and thus time to be spent. Consider mickybart?

I think it's in our open, free community's interest to keep things simple and target command line + CPU usage. Then attack GPU support as a bonus once all the rest works reliably and epic and can spread to a big enough developer community to not only survive at the edge of existence but have the GUI LinuxPhones live as useful ethical device in the center of our world and values.

Of course I agree GPU is extremely useful for algorithms so it does no harm supporting it in general. I am not saying it's nonsense to support a GPU. My point is to reduce the problem to exclude the GPU and get all else going to finally be 3/4 there and get convergence happen to reach final audience.

Because convergence would be a major plus for Linux/Android.
[8125, K-JAM, P4300, MDA Vario General] thedreco:
Hi all,

I am looking for a pedometer application for my wizard. My wife's got one such app on her Sony Ericsson phone that counrs her daily steps, automatically reset every day and keeps track of it all, allowing for graphs, average and many stats to be looked at. I am thinking: if it exists for a Sony phone, surely it exists somewhere for a WM pocket phone.

Do any of you know of a similar application for my WM6 wizard?

Cheers

Oliv
[8125, K-JAM, P4300, MDA Vario General] hanmin:
I'm not sure.. but does that require supporting hardware? or you just key in your steps?
[8125, K-JAM, P4300, MDA Vario General] thedreco:
Am I stupid?

Oh, i never thought about that. Yes, maybe you're right, maybe it reauires some kind of hardware. That would explain why i can't find anything but an app to log in the steps measured by a proper pedometer...

hmmmmm maybe I'm just stupid then...
[8125, K-JAM, P4300, MDA Vario General] hanmin:
do a google on "pedometer Sony Ericsson", I thinkt thats the phone you are referring to. It seems to be a special phone which they've include.. something into the phoen to sense motion.. and I think you probably can (say) change to the next track (playing music) by shaking it? It is like the iPhone.. which will rotate the screen when you have it in landscape mode.
[8125, K-JAM, P4300, MDA Vario General] fzzyrn:
Yes, i'm pretty sure the phone in question has a built-in accelerometer, for those at a loss for words.
[8125, K-JAM, P4300, MDA Vario General] urbanlegend213:
hey, i was gonna get that same sony phone b4 i got my blackberry, and yes there is a certain piece of hardware that is inside the phone, they have to version sof that same phone which ppl interflash because of certain features, and there is only one that can acutally use the pedometer, becuase that one has the hardware....
[OnePlus 3 Accessories] fix-this!:
Couldnt find much yet on amazon. I did find one tempered glass lcd protector I bought but sadly not many cases yet. Only cheap rubber ones. Personally I only buy from diztronic or supcase.

Post your finds in here.
[OnePlus 3 Accessories] _PrEzi_:
a few of them in the official store >

https://oneplus.net/uk/store/cases-protection
[OnePlus 3 Accessories] joe123321:
Post where you found the temepered glass screenie.

Case for pre-order on amazon.ca TUDIA Slim-Fit HEAVY DUTY [MERGE] EXTREME Protection / Rugged but Slim Dual Layer Case for OnePlus 3 (Matte Black)
[OnePlus 3 Accessories] fix-this!:
https://www.amazon.com/gp/aw/d/B01G86RF0W/ref=ya_aw_od_pi?ie=UTF8&psc=1