schmittlauch
-
Content Count
13 -
Joined
-
Last visited
-
Days Won
1
Posts posted by schmittlauch
-
-
On 6/13/2020 at 6:00 PM, tdm said:
@acrux @schmittlauch I've never installed SailfishOS, so I'm not sure how that would affect the phone. But I can tell you that Lineage uses a different format for userdata (FBE instead of FDE) and modifies boot, vendor, and system partitions. I also suspect that AVB may have something to do with this. Are either of you currently stuck in a place where you are not able to use your preferred OS?
Sorry for the delay. I have now flashed Sailfish OS, which has its own can of worms but is the reason why there is no urgent need on my side.
Regarding Sailfish modifying the device such that Lineage doesn't work anymore: I had reset my device reset to stock according to this guide by @Waxberry before attempting to flash Lineage, so there should be no remains of anything I've done beforehands, right?
On 6/13/2020 at 6:00 PM, tdm said:@schmittlauch nwwn.com is my domain. I don't bother with a http->https redirect because there is nothing that could be considered private there. But https does work and you can certainly use it.
As others already mentioned, the important issue here is integrity, not confidentiality. I just feel a bit uncomfortable flashing something MITMable to my phone, where the verification hash also comes from the same vulnerable site.
-
9 hours ago, acrux said:
Thank you confirming my situation!
Do you have test11 laying around? Are you able to install test11 and boot it successfully?
Yes, I just successfully flashed and booted test11 and right now trying to update test12 over it (I guess I'm not brave to try test13).
Update: Updating to test12 again made the boot afterwards fail. Unfortunately test11 without a proper QWERTZ layout is only slightly useful to me.
Again this was only possible though from SDcard, not via USB `adb sideload`. Any idea what's going wrong there?
Btw @ whoever runs nwwn.com, could you please set up a redirect from http to https?
-
1
-
1
-
-
So I tried flashing the test13 image of Lineage onto my new Pro1. I am certain that I followed all the instructions to the point where possible and used a USB2 port (as USB3 wasn't working).
While flashing the recovery worked fine, the first issue I encountered was sideloading the image to the recovery: This always failed.
adb sideload lineage-16.0-pro1-test13.zip serving: 'lineage-16.0-pro1-test13.zip' (~30%) adb: failed to read command: Success
As a workaround, I put the zip onto an SD card. Then flashing was successful, but the resulting LineageOS installation just took several minutes to boot before eventually falling back to the recovery again.
Any ideas what I'm doing wrong? While at the first attempt I had Sailfish OS flashed before, just to make sure I reflashed all stock parts before doing a 2nd attempt – which failed in the same way.
-
1
-
-
I am now holding my QWERTZ order #33xxx in my hands \0/
If I understand correctly the first thing I should do is flash LineageOS on it, as the stock ROM has many unfixed bugs, right?
Serial number is 12xx.-
3
-
1
-
1
-
-
Can confirm as well, got my Stock Assigned message for a QWERTZ order #33xxx to Germany.
-
5
-
-
Quote
Hey guys! We hope you are well and keeping safe. The factory has produced a small batch of devices which we expect to ship over the next few days. These Qwertz units have now been allocated to orders, so keep an eye out on your emails for further updates and tracking details. For all remaining customers, we are producing devices as quickly as we can given the continued staff shortages and transport restrictions in China. We should be able to ramp production in the upcoming weeks to increase the number of units ready to ship, so please bare with us! Sincerely, Team F(x)tec
Latest production update from today.
-
4
-
2
-
-
The latest update mail:
QuoteHello there! We hope everyone is staying safe and keeping their heads up following the recent escalation of the Coronavirus Pandemic. This week has seen a number of huge changes taking place across the UK and our hearts go out to anybody who has already been directly affected by the outbreak. With this in mind, we have decided to take a precautionary measure with the health and safety of our team being our number one priority. As of today everyone from F(x)tec HQ will now be self-isolating and working from home for the foreseeable future. We are lucky enough to be able to work and keep operations running without being in the office, which means business will continue as normal. However, please keep in mind that operations may be slightly slower than usual. To all of our remaining customers: as per our email update at the beginning of the week we are still on track to start shipping next week and a will send round another update in due course will the expected shipping schedule. General inquiries: For now, one of us will be going into the office once a week to sort out any returns and make sure we can process refund requests as quickly as possible. However, given the drastic changes that have taken place recently there is a chance that we will eventually go into complete lockdown nationwide. If it does come to this, please be patient with your requests as this could make it extremely difficult to process. For any questions or queries you can continue to get in touch with [email protected] or reach out to us through our social media channels: Facebook: https://www.facebook.com/fxtec/ Twitter: https://twitter.com/thefxtec Instagram: https://www.instagram.com/fxtec/ Remain positive, stay safe and look after your loved ones. We will get through this together! Sincerely, Team F(x)tec
Let's see how many devices they can ship next week.
-
Possibly the same (or at least related) as this: https://community.fxtec.com/topic/2661-slider-wobbleclatterrattleclick-when-tapping-on-the-screen-when-slider-closed/?tab=comments#comment-41643
-
Currently the Pro¹ is only available with a US international QWERTY layout. I'm sure many people are interested in getting their native keyboard layout instead, while at the same time Livermorium probably has to be careful about which layouts to offer at first.
Thus I suggest a possibility to preorder the phone under the condition that it is available with a certain keyboard layout within a certain time. This mechanism can serve as a voting about which layouts are most popular at the same time, providing some data to the Livermorium folks on which layouts to concentrate on.
-
Will do a tear-down as soon as I have one.
Good to know, thanks. I just cannot buy a device before I know how easy or hard it is to repair.
-
Hi,
I want to use my phones as long as possible. If people manage not to drop their devices and keep them away from their toilets, the lifetime limiting factor is the battery (capacity) degradation.
Thus it'd be important for me to know
1. how easy it is to open the device: Just unscrew some screws, or loosen glue with a heat gun, or even worse with rippling metal foils breaking as soon as you try to open it?
2. What kind of battery is used exactly? This involves both its physical dimensions as well as its electrical characteristics. There not only capacity and voltage are relevant, but also what kind of protocol is spoken over the third pin. Example: For the Jolla 1 phone it is possible to find compatible 3rd party replacement batteries, but they can not report the temperature back to the system as their 2rd pin uses a different kind of resistor for that.
If I know beforehand whether and how to replace the internal battery of the Pro¹, then I'm willing to buy one.
LineageOS, Current status : 16.0 Test Builds
in Support
Posted
For completeness sake it needs to be said that recent devices like mine (yours as well, acrux?) seem to have been shipped with a pre-release of an upcoming stock update.
Unfortunately I do not recall the exact build number and date. So if it was possible that the update had updated some firmware of components in a backwards-incompatible way, that could be the cause for just flashing the provided older stock images over it doesn't put us in the same state as it'd be for previously shipped phones.
Maybe @Waxberry can clarify what's the current status of firmware updates and shipped stock ROM builds?