raymo

Hi @claude0001 In order to experiment and gain freedom in my SD card I've installed your (non official) LOS 16 on my old Pro1. Unfortunately I had some hassle bug in my phone (who remains me the beginning with LOS in a new pro1) -No camera (app crashed at launch on day 2) -When receiving (or doing) a phone call, screen is stupidly dark, with absolute no chance awaking as I'm in a phone call, it's funny but not for a long time. -Strangely keyboard is...slower, with often ghosts touch. What a pity, it was so nice to freedom access to SD card, but as pro1 is my only phone, I can't li

Back to LOS20, really my best "android" experience on pro1 so far. And wait : fingerprint is working, ok, a bit slow, but it works all the time. Unbelievable.

I have here two spare battery for the Pro1 (not x of course). I need only one, and I plan to replace it in this summer. EDIT : sold ***So if someone is interested in a spare battery, I would be happy to sold it for 50 euros and I can send it in EU or Switzerland. ...*** @SchattengestaIt Also if you need some measurement or test on it let me know, I doubt I can dig in internal regulation without break it, but it could be (carefully) doable with the old battery as far as I've replaced it. I guess the regulation circuit is (relative) standard, and will be fun digging into small chipset a

Agree with you, I haven't received the pro1x yet but I'm afraid about reported connectivity problems, especially if it means hardware or firmware problem. I'm not very interested in a keyboarded brick, wich means I will have to dismantle it completely to see what happens. Without guarantee but for the sake.

Ok I've this option to disable it, and it's good now. Thanks !

Also I found in thread : this can be a debouncing issue, will dig into that...

ouch Hardware problem is what I was a bit afraid about. Maybe I will have to remove dust from here, it's true that the clicky power button feels sometimes weird in my finger.

Same behaviour on mine with LOS18.1, this happens a few months ago, not every time. I've planned to reflash it to stock android (screen replacement) and move to LOS16.1 maintained by @claude0001. When I find a bit time to do this... So not sure I can help here.

Thanks for sharing your experiences here, much appreciated. I'm waiting for a pro1x who could or should be my next daily driver (hopes !), then I will have to reflash my pro1 in order to change the screen, and then...I'm very curious about Droidian. Wait and see !

@Noob : click sound, yes. I would say no mecanic problem here. I glue one touch with cyanocrylate a few months ago as he felt, and had no issue since. I test with three press on different touch like 'aaa eee ddd ccc sss ooo mmm....' and see what happens, then I found this : when pressing the bottom part of the keyboard the bug disappeard. As far as I understand @veRYANgry solve the problem with tightening the two bottom screws, wich could be related to my problem.

I must say with more as one intensive month of use, my keyboard feels perfect now. I forget all double-press, I had two or three ghost keys (like th*'˜is or something like that with weird characters who suddenly appears) but so rarely that I didn't notice it as a real issue. Edit : I suddenly found a post concerning quadratic equation on this forum but I don't think it's related with any keyboard issue 😄

Well I was all wrong.

As far as I understand, you can put your phone model in the "about me" field. But the title (with your phone model, as expected) only appears in the "computer version" of the webpage. In android you will have to "click" fist on the user profil to see more information, or switch your page in "computer version".

This update looks correct in my opinion. Community is sharing high knowledge, some powerful users/developpers are working in alternative OS, fxtec work hard on debugging issues with components manufacturer...what else ? Delays aren't really a problem according to backing such of niche hardware. Most important is the follow-up here. (one more time : in my opinion 😄)

So I fixed my keyboard issue. Hastily way. Since beginnings I had to press hard on several keys, wich is incompatible with a real use of the keyboard. Mainly letters 'a', 'e', 'm', 'h' (and mny more)...are swallowed. But sometimes it has worked as expected (not often), and sometimes it's a real pain (often). Average : a bad experience Example with taping this as fast as possible : "Les chiens aboient la caravane passe" Ls cins aboint la caravan passe Ls chiens aboint l crvane passe Ls cins abint la caaravan pass Digging into software doesn't help to find a workaround

I use my pro1 as daily phone with LOS, and an archlinux container for LibreOffice and Python / C arduino coding on the go. It could be very useful, for example I had to share a bios dump in discord, impossible in android as the discord app filters all weird files extension (renaming it with *.txt or *.jpeg didn't match here) so I had to do this in the container with a "pc" version. Also I often edit Libreoffice document, and it works great with keyboard, as in android it's a pain to edit and modify such of files without data connections. Gimp is useful too for weird picture format. LO

I have not understand all things here, but should it means that indiegogo perks are money lost ? Or should I expect a new pro1-x in 2023 ? (...wich would be ok for me)

I was interested in the titan pocket, but the lack of alternative OS and my androids allergy is a deal breaker here. However I had a titan in hands and it feels very solid.

So, after one week of use, it seemed not related with auto-rotate settings. It works, but sometimes felt one or two characters, then it works perfect, then it doesn't... Also the next things I would try is to dismount the keyboard, but I have to wait for a possible Pro1x replacement, wich doesn't happen yet as I have a great allergy with android and google's stuffs and LOS is not ready (...yet ? I hope...) also SailfishOS looks really interesting, either droidian...sure I'll have to try at some point. Sure I definitely don't give up, I agree with @claude0001this keyboard is probably and

On my side, it's really strange. The keyboard works really (quite) perfect....since I completly disabled the auto-rotate screen in LOS18.1 as I never use it, as 'clacky keyboard on' automatic set the pro1 in landscape mode. I think it's the first time I write here without a keyboard bug. Too good to be true, so I will test a few days and report here. (...I write still a few words because of murphy's law and fatality of life to be sure....incredible...)

Thanks, this option disappear when using mozilla with the phone. Had to use "computer version" button

aw9523b: key press: key_nr=38 keycode=0012 ff=0000 gpm=0000 glm=0000 aw9523b_irq_work: enter polling mode: p0_mask=ff aw9523b: key release: key_nr=38 keycode=0012 gpm=0000 glm=0000 aw9523b_poll_work: enter irq mode aw9523b_irq_handler: enter If I understand correctly, the process with the aw9523 chip is so : 1-key press, 2-enter polling mod, (the CPU repeatedly asks the keyboard for it's state) 3-key release 4-enter interrupt mod after polling 5-send an interrupt to the CPU via i2c When

I dig a little into this (not sure that a solution will be found, but as understanding can bring a deeper insight about reality....) But first.... Could anyone pointing a silly noob the correct syntax to insert code please as I can share my results here ?🙈 [code] [/code] doesn't match, ...incapable... Sorry, thanks !

Agree with this, I tryied this possibility but even with heavy load or quite no load it works with same behaviour. It could be relative long time without issue, and sometimes it's quite useless. AFAIK a hard reboot don't really affect this. strange...

Sadly I've flashed LOS16, 17, 18 and 19 and be back in LOS18 at this moment. With full wipe data at every flash, and the keyboard has always this sort of strange behaviour (but not every time of course...) - I wonder me if it could be a debouncing problem, also digging a little in internet I found this : "The keyboard works with a mixture of interrupts (the keyboard notifies the CPU about a keypress) and polling (the CPU repeatedly asks the keyboard for it's state). Most of the time interrupts are being used, but for some situations (I think they involve multiple keys being pressed at th