acrux
-
Content Count
53 -
Joined
-
Last visited
Posts posted by acrux
-
-
15 hours ago, tdm said:
I would be quite interested in building and installing this.
Yes, great idea, but please LineageOS first 😉
-
3
-
4
-
-
1 hour ago, tdm said:
Apparently my last few builds have included GMS (Google Play Store, etc.) I've removed that and rebuilt. test16 is exactly test15 without GMS.
That did the trick - test16 booted OK! So that was the reason for non-booting system for those without gapps...
Thanks a lot! Now to test qwertz keyboard 🙂
-
2
-
-
15 hours ago, tdm said:
I need a logcat of Lineage (trying to) boot in order to figure out what's going on. This will require some tweaks to enable logcat at startup. If you are comfortable hacking on your phone with adb, we can try to do that.
Yes please, guide me - i'm ready to help if I can 😉
-
34 minutes ago, tdm said:
I suspected something like this. AVB is probably unhappy because the Lineage security patch level is less than the stock patch level for the newest devices. Or something like that. I'll need to investigate.
But then test11 is even more older, but installs and boots successfully 😉
-
1
-
-
54 minutes ago, schmittlauch said:
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.
Well, mine is not recent: S/N: fxtec000236. Was shipped in the end of January.
However, in the middle of May, before installing SailfishOS and after reverting to stock, I let the stock to install all ota updates it offered.
But then again, after SailfishOS and before LineageOS test14 i again reverted to stock but this time without ota updates.
-
50 minutes ago, tdm said:
Alternatively, perhaps you can tell me exactly which version of stock you were running and maybe I can reproduce that here.
Exactly the same you get using the here published stock reverting method using the file QX1000_user_20191028191838_0a493a1_Fastboot.rar
Let the first start to go until the first setup screen and switched off there.
-
On 6/18/2020 at 10:02 PM, tdm said:
test14 is up. Changes:
* Fix QWERTZ apostrophe.
* Disable double tap to wake.
Â
Pro1 was reverted to stock using fastboot method published here. First boot went to the stock recovery asking to format/wipe data. After doing that stock booted to android initial setup screen. Switced the Pro1 off.
Followed carefully the test14 install procedure. Result as with test12 - test13 - very long startup animation and then rebooted to recovery screen offering only either to continue or to wipe system data. Tried both with no results.
Additional information: test11 installed and booted just fine.
-
1 hour ago, marmistrz said:
I'm still not sure: if I update test10 to test14 through the LOS recovery & sideload (without fastboot) and test14 doesn't boot, will A/B take revert me back to test10?
Well, my hope was on that too, when I tried to upgrade my test11 to test12 or test13 but the test12 or test13 just did not boot and system was reverted to recovery instead of booting to functional test11...
-
9 hours ago, schmittlauch said:
I just feel a bit uncomfortable flashing something MITMable to my phone, where the verification hash also comes from the same vulnerable site.
The site is not vulnerable. Just the connection between the web server running there and your web browser is not encrypted resulting that somebody along the route could read the information.
-
Does Arch Linux forces you to run fastboot with sudo? Wasn't it even not recommended?
-
12 hours ago, SchattengestaIt said:
Where is the LineageOS keychar file saved?
Since there are many locations and your setup is already very good, this is easier than to create a new one.
(Reason: For Qwertz, the 'FN'+L key outputs ´ instead of '. That means that letters get apostrophes instead of getting separated.)It has been covered here already.
And not apostrophes (if I'm correct here), but the letters are getting accents. apostrophe is a separate key ' not a dead_key like ' and `.
47:0026:802b should fix the L key.
-
1
-
-
7 hours ago, schmittlauch said:
Unfortunately test11 without a proper QWERTZ layout is only slightly useful to me.
Not at all - just flash boot-qwertz-test2.img to the boot partition of the slot you are running test11 (in my case it was boot_b) and you are at the latest layout 😉
-
18 minutes ago, schmittlauch said:
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.
Thank you confirming my situation!
Do you have test11 laying around? Are you able to install test11 and boot it successfully?
-
My case makes me think that LineageOS and SailfishOS could make the Pro1 somewhat incompatible to each other?
The installation of SailfishOS on top of LineageOS ended without any error messages - it just did not boot. After returning to stock with fastboot method, SailfishOS installation was successful. Now the installation of LineageOS (newer than test11) on top of SailfishOS was again without any error message, but it just did not boot. I returned the Pro1 to stock again already, but that also booted only to recovery and asked to reformat data. After that the stock booted ok. Any ideas? It could be helpful if just some partition reflash is sufficient, not the full stock restoration...
If the curiosity wins, then I might try to install LineageOS again, now my Pro1 just lays in the original box...
-
As TMO Forum is somewhat off-topic to the subject, then I post it also here - decided to offer my F(x)tec Pro1 for sale.
Link to the original announcement is here.
-
2
-
-
19 hours ago, tdm said:
test13 is up. Changes:
* Updated QWERTZ keymap.
* Addressed some SELinux denials.
test 13 does not boot like test12. Returns to recovery.
And no way to boot into test11 which worked ok, although the slot a/b thing should be designed for that?
History:
1. Returned to stock and decided to offer my Pro1 to sale...
2. Decided still to test again SailfishOS. Flashed twrp to boot_a and using twrp installed SailfishOS.
3. tdm resumed development and decided to continue testing qwertz layout
4. flashed test12 boot to boot_a and sideloaded test12 to b - did not boot
5. repeated that with test11 boot&zip - test11 booted ok and was able to test qwertz by flashing boot-qwertz-test2.img to boot_b
6. booted to recovery and sideloaded test13 (to slot_a?) - very long startup and then falled back to recovery with no option to boot to test11 in slot_b or perform any other task except formatting data (which I tested when tried to install test12 but that did not help.
-
1
-
-
1 hour ago, tdm said:
No, it has not changed since test2. Can you figure out how to fix it? I am not familiar with the accents vs. apostrophe keys.
47:0026:802b (l and ')
It was in issue 35 and by some reason did not get into qwertz test1 and later in test2...
-
1
-
2
-
-
48 minutes ago, tdm said:
Alright qwertz folks, here's another test boot image. Please try and let me know how the keyboard works. Most keys should be correct, but I may have made a mistake or two...
Thanks a lot! Seems to be mostly correct.
I guess the yellow-key pluss l should give ' (apostrophe), at moment it gives ' (acute accent) if my eyes see them correctly
Also yellow-key pluss ü gives ~ but for it to be really usefull should give dead_tilde...
Thanks again for a great progress!
-
1
-
2
-
-
18 hours ago, tdm said:
7. Our keymap line should be "46:0010:8003".
Does that make sense? Can you test and see if it works?
Unfortunately not. 😞 This generates qQ" eg yellow-arrow + q generates ".
If you look at the current keymap (/sys/bus/i2c/drivers/aw9523b/6-0058/keymap), then you can find a line "60:0003:8003" - it is for key 2 and 8003 generates " as it should do. Actually that kind of problem restricted the keys I was able to adjust to these I posted in issue35 😉
However @ can be generated with the help of Sym key. Sym + q generates @. 😉 And all other these still missing yellow keys which should be mapped to "yellow-arrow"...
Created a file symkey.txt which describes the current Sym key mappings.
-
1
-
-
17 hours ago, tdm said:
I've downloaded your attached file and each line has three symbols on the left and a comment on the right. I presume these three symbols represent what you see from the keypress for (1) no modifiers, (2) shift, and (3) yellow-arrow. Is that correct? If so, then the first two columns seem fine for all keys and there are eleven keys which need the yellow-arrow symbol adjusted. Was this done with my modified qwertz boot image, or with the standard test11/test12 boot image?
Yes, correct - (1) no modifiers, (2) shift, and (3) yellow-arrow.
This is the result with your modified qwertz boot image. Thanks!
Please note that " lLLÂ Â Â Â should be lL' " can be easily fixed with the line "47:0026:802b" which by some reason did not get into that "modified qwertz boot image".
-
17 hours ago, tdm said:
Thanks. Unfortunately, your output.txt does not really help me, as I don't have a qwertz model. If you can just send the changes to the keymap as you did in the github issue report, that would speed up this process greatly.
I tried hard to find the codes (mostly as trial&error procedure) for still missing Fn+ keys, but failed. It seems that the symbols missing are currently tied to the Sym key acting as Altgr key for keys corresponding to pc105 keyboard german qwertz layout not for Pro1 german qwertz layout?
If somebody guides me to the usable keycode table then I'll continue.
It was very easy in SailfishOS to get the keyboard layout you like, but that is Linux... 😉
The original output.txt was missing some corrections. I provided the corrected one in my original post and also here.
-
10 hours ago, acoppens said:
I'm also getting stuck not booting with test12. Recovery helpfully explains Android system can't be loaded and offers a factory reset (doesn't help). Will go back to test 11 to get dmesg for my camera issue. Afterwards I can get diagnostics on the boot issue if given proper instructions....
So it seems, that a fresh install with test12 results a non-booting system, but upgrade from test11 is working OK?
Tried also to upgrade my test11 to test12, but as I flashed also the boot-qwertz-test1.img then the recovery thinks that my test11 with that boot image is newer than test12 and refuses to install... 😄
-
50 minutes ago, EskeRahn said:
You lost me there. If people want to use qwertz would the boot-qwertz-test1.img you linked above then be overwritten from the payload,bin?
boot-qwertz-test1.img just gives some more correctly assigned keys for german qwertz keyboard variant for test11&test12. I guess the changes will be incorporated into the lineageos boot image inside the lineage zip - eg in test13...
-
On 6/1/2020 at 11:59 PM, tdm said:
Please let me know if the keys you noted work properly, and what additional changes should be made. I will incorporate the changes and we can iterate until it is correct. 🙂
Yes, all keys I noted in issue worked properly except Fn+l.
I'll attach here a file output.txt with the keys output and comments.
Thanks for your work!
Â
Ubuntu Touch OS for Fxtec Pro1
in How Tos
Posted
Has anybody tried both: SailfishOS vs Ubuntu Touch? Which one is better suited as everyday phone's platform?