Leaderboard

Been hacking on the lights HAL this morning (shhh, don't tell my wife). I think I've got the logic figured out so that the keyboard backlight always keeps the proper state (which is, on only when both the screen is on and the slider is out).

Thanks to @Raksura for posting this in another thread, but let me put it here too, for more to see the progress.

Nice timely update about the virus affecting the factory:

Never heard of it..... a must have... Just bought one from ebay for $16 and twice that in shipping(!) *LOL*

I just learned this has been done:

I appreciate people posting these updates as either I've fallen off the email list or people who have received their phones no longer get updates. Lol. I may have my phone, but I'm still interested in what is happening and want to see everyone get their phones.

I just re-measured and they are 5mm indeed. I had measured this earlier today and was fully confident but obviously I'm cross-eyed :-D.

Trust me, you are not alone.... 😇

Got the same problem. Fixed that issue by finding updater app in all applications list and clearing its cache.

I tend to think that things like batteries could be changed without having to recertify the device as it has nothing whatever to do with the radios, as stated. We could always take the approach I used on my old VHS movie camera. I removed the sealed lead battery from its battery pack and turned it into an adapter that went via speaker wire to a lawnmower battery I wore in a backpack while filming. I ran it for days and never EVER ran out of juice while filming. :)

Actually there is an easy way to get the phone to lock and wake upon closing and opening your case. Just use Key Mapper. Unfortunately, it can only lock as admin thus preventing you to use the fingerprint reader. However, the source code is available therefore we should be able to implement normal lock using accessibility service. I'm not sure if wake up could be implemented in the same way. I guess it could: https://stackoverflow.com/questions/2891337/turning-on-screen-programmatically So there you go, someone needs to jump into Key Mapper code and implement those two actions.

He's definitely awesome. I wondered what @tdm's real name was. :P

Oh and I found something very strange in my logs but don't know if it is just a problem with matlog. Just look at the times the messages were logged. 2020-02-20-20-38-39.txt

sounds promising :) checked again, calling with telegram is not a problem but real calls are. No BT or wired headset connected and not on speaker. Just receiving call and holding my hand in front of the proximity sensor to turn display on and off Here Is a log for a call with the audio problem. 2020-02-20-20-59-26rec.txt

haha impulse purchases at it's best 😄 'm guilty of this one https://www.gsmarena.com/yota_yotaphone_2-6959.php turned out to be a solid device lol eink screen implementation a bit poor though.

Just making translingual dad jokes. Not picking on you. :)

If only that phone had real 3G support (not that CDMA2000 stuff) and WiFi It'd be a decent and unique phone for me to keep as a backup...

...and if dumb slider, perhaps with TWO set of rails, so it can slide in either direction, to the benefit of those loving portrait keyboards....

The good news we can read from that link ist that the infection rate has already decelerated and continues to do so, so this epidemic's peak should be reached soon...

I meant that the PreProd unit has a poorly calibrated display, and this was super easy to compensate with no additional programs in Lineage.

Browsing for "Night Light" I found the much more powerful "LiveDisplay". And especially noticed the "Colour calibration". Setting the PreProd unit to RGB=(100%,90%,80%) I get a perfect neutral black to white scale. And then can adjust that with the day/light settings. Awesome!!!

...and I thought I was the only one with enough screws loose to do crazy stuff like this! LOL 😁

@JooJooBee666 yes I'm aware that audio still has issues. I plan to make that top priority for next week. But feel free to poke at it before then. :) The issue with stock vendor is the fstab -- stock uses FDE and lineage uses FBE. You need to do some shenanigans to overlay the lineage fstab to let it boot with stock vendor.

For all the curious, changing the charging state and trying a different USB c cable seems to have solved the issue. The original cable still works, but I'll just leave him in the desk for now.

I did not do a port, I installed a GSI which you can easily download. Because of googles Project Treble thing and the pro1 stock rom being fairly compatible with it, as long as you have their vendor and boot image, other versions of android mostly work by just flashing the system image. At the time I installed it I wasn't aware there are instructions for it but it was reasonable straightforward and went without a hiccup 🙂, if you want to try it I recommend following this guide though https://github.com/phhusson/treble_experimentations/wiki/F(x)tec-Pro1

At least you know where to find the info, thanks to the great people here.

Fixed. Typed on the Pro1. 🙂

Well clearly they're not French. :P

I HAD ONE OF THOSE! XD

I was not a big fan of gesture navigation either until I got myself that awesome Huawei P30 Pro last year. I'm now a gesture convert. You don't have a navigation bar anymore so more screen real estate. Swipe from the edge to go back has the advantage to be accessible from anywhere along either of the screen's edge enabling one handed operations of larger devices.

@tdm After I got called today and audio was gone again, the tries after that were broken too. yesterday my tests were all fine and id did several successful calls with display off and on a few times...

Have you tried Full Screen Gestures? It worked very well on my previous phone but I haven't tested it with curved screen like on Pro1.

I don't understand. What fish? Why don't you just touch the back button?

Hey, can we expect Android 10 and 11 on our phones, or will we have to use custom firmware for that? Does the phone have some kind of custom drivers we need to port, or is everything just "stock"?

In another thread it was mentioned that Qualcom chips don't have a RTC so it has to get it from a NTP server or the Cellular network.

@tdm fair enough. I'll let you know if I find anything of interest.😎

FYI .. I'm heading out of town shortly and won't be back until Monday. No new builds until then. I'll leave you with a Lineage splash that I made just for fun: Lineage Splash Flash this to the "splash" partition with fastboot. Here's the original in case you want to go back: Stock Splash

It still baffles me that THE alternative Android build still has such terrible support of the SIM info menu; it knows it exists, and can show you the settings, but can't authenticate to change them. This is NOT a complaint about @tdm either; I see it as a platform shortcoming that the entire LOS community needs to gather and address. It is DEFINITELY going to come to a head next year as networks start decommissioning their legacy voice bands in favor of new data protocols. For the record, I think swapping voice bands to data is STUPID, but it's what they've decided to do, and they don't ask us

Now he can finally afford to catch up with his relations in Belize! :P

Yeah if screen is off I see no issue in swapping it to KEY_WAKEUP instead of pressed key.

Yeah, I think it was a little gesture appreciating her getting in more than a handful of new orders from her network, If I remember other posts right.

Why not try powering it external to check if it's dud before getting another?

Is the keyboard turned off while closed on Lineage? If not squeezing the device might send a key, and we do not want that to wake in say a pocket. So if it is NOT turned off closed it should be a single key hard to press by squeezing. If it IS off closed, other things should be considered. The modifiers would be good, as there is no 'risk' in tapping those, the same way there is in taping a key that could have a function. If say an incoming call arrives just as you press Enter, so 'any' keys might not be optimal. So safe keys in all scenarios will be the Shift-keys, as neither of t

If there is no downside of using all keys, why not :)

I dont think we can store batteries for 10 years we sure can buy 4 or 5 batteries but the problem is these will died in 3 to 4 years regardless of in use or not. Also i have seen few people here having issues with charging. most likely the problem is usb port as plugin in and out the cable several times a day might hurt the usb port. so i would highly recommend to get the magnetic adapter. i am using one and it saves the usb port from wear and tear

So I've managed to restore my device to the original image. I was following the solution from Tom and using his tool from here: http://files.nwwn.com/android/pro1/factory.html However, I've faced the same problem which some people were posting here: "Connection time out". Have no idea what could be the reason of that. Nevertheless, in the end I managed to successfully reflash the phone. The trick is to have prepared tool for reflashing and to press a button as fast as possible immediately after you reboot the device (power + volume button down). Because device ins completely unrespo

That's weird - I thought a posted (another) response... I got it working by allowing updates over data/the network (instead of just wifi). All sorted. 👍

@Wikiwide Please read my factory restore page here: http://files.nwwn.com/android/pro1/factory.html This explains the function of the xbl partition, which in turn explains why you are stuck in EDL mode. Note that EDL and QDL are pretty much interchangeable. The device is failing to start and entering a state that allows you to restore it to a functional state. This is marked by the USB device ID 05c6:9008 which is the definitive indication that EDL mode is active. Unfortunately, Sailfish seems to be producing a steady stream of bricks and I'm afraid it won't let up u

Nope, I won't send him a bill, he got the refund as requested. 🙂 It's working, so I'm fine. I'll also offer unbrick-services in my shop, probably free for users who bought from me and everyone else can get it reflashed for a little fee. Usually, it's not needed. If tdm finds the problem with the flasher and fixes that, everyone can do it himself 🙂 But in case someone isn't technically able to do that for some reason, I can help. Thanks goes to tdm for his awesome help and work 🙂

F(x)tec confirmed during IFA that Pro1 will be updated to Android 10. I think that it was also mentioned on Twitter also. https://www.trustedreviews.com/reviews/fx-tec-pro-1 "FX Tec has done very little with the software here, instead sticking to a very clean version of Android 9 Pie (with Android 10 coming later)." https://www.mobiflip.de/fxtec-pro1-android-smartphone-mit-hardwaretastatur-im-hands-on/ Translated: "F(x)tec is still covered when it comes to upgrading to Android 10. They are in contact with Qualcomm." This was initial promise but they confirmed that they