Re: The new QWERTY device project
 

In the community we already did the work for 64bit arm devices, this was before the work on Sailfish X had even started and was mainly pioneered by Ghosalmartin for the Nexus 5X (bullhead).

The userspace will still be 32bit and indeed that is a feature because there are no aarch64 compiled apps around for sailfish at all.


Bluez is fine, its the kernel HCI driver with the broadcom based BT chips which I already warned Chen against.

The main problem is *always* the drivers, and also the specific android base used to interface with those drivers which Chen probably won't get a huge amount of choice on anyway.

Re: The new QWERTY device project
 

I've completely missed this port.
Thank you for enriching my knowledge.

Well, that's sad.
I was hoping for a full 64bits support.

- Lots of 3rd party apps are "noarch" anyway (QML + Javascript, mostly - same package regardless of the CPU arch).

- Supporting Aarch64 is basically just adding 1 more available target on their OpenBuildSystem compile farm.

- We need multiple archs due to Atom's 486/IA32 anyway

- There aren't that many 3rd party apps with binary code anyway, compared to Android or iOS. Lots of them are opensource and even if the original author is unavailable, someone else could easily fork the repo and recompile.
Only the few closed-source apps, with a binary component, whose dev is unavailable, and that will need a Aarch64 recompile would be affacted by the switch.



Let's hope that by the time of Livermorium, we'll manage to find a way to get it working.

I haven't been paying much attention, is the bluetooth core inside Experia X anyway related to the core in chen's selected PCB ?
i.e.: will the work that Jolla will need to put into Sailfish X's bluetooth driver benefit Livermorium in anyway ?

Re: The new QWERTY device project
 

Anyone know when moto mod is estimated to be completely delivered?

Re: The new QWERTY device project
 

According to the IGG page

Re: The new QWERTY device project
 

There's practically zero apps that install on the Jolla Tablet for this reason, nobody bothered to build for it. Indeed at some point Jolla is going to have to let the community support unmaintained apps on Harbour because sooner or later a Qt upgrade is going to break them. and there's also Alien-Dalvik to consider in this equation.

But so far Jolla hasn't said anything about building or supporting fully 64bit sailfish, and I would expect that they would let us community porters have it first for testing before rolling it out as a fully supported thing.

No idea. My point from mentioning it was basically to say that its a hardware specific problem and mostly likely irrelevant for the Chenphone.

Re: The new QWERTY device project
 

Soon?

(Sorry OT and bad joke...)

Re: The new QWERTY device project
 

When I was discussing the GCC update during one of the Mer meetings, Jolla seemed most concerned about those closed-source applications.

Re: The new QWERTY device project
 

@Chen: Are you planning to update your signature with this here project any time soon, or perhaps are you waiting for your Moto mod to be done with ?

There *might* be people that read your posts on other threads and don't know about the "Chen[s]phone".

The more the merrier.
Strength in numbers.
All that...

Re: The new QWERTY device project
 

Yes thank you! I will need to deliver this Keyboard Mod first.

I have decided to take the time longer to make the product as good as possible, instead of releasing in a hurry. It's about 85-90% of my "ideal product" at the moment but I want to make that 100%...

Once Motorola formally launches this Mod, and I start fulfilling the supporters in IGG, I will close the Keyboard Mod campaign and formally move to this one.

But because of running late with keyboard mod I don't think we can make the hardware end of year anymore. But won't be too long. Building this device (not inc. software) isn't more difficult than Moto mod and I know exactly what to do...

Re: The new QWERTY device project
 

Be careful on that! The last 20% usually need more effort than the other 80%. It might take ages or even kill your project as a whole. Especially if your aim is an "ideal product".