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

Hmm, I have just wanted to see my mail server's log when I have realized I was registered using my Gmail account. 🙂 However, I think they have not sent me this update as I don't have a pending order now, but it is good to keep us updated as I wish them the best and would like to know about it... Anyway, SPF should fail only if they sent that e-mail from an address other than what was written in TXT record or if that e-mail was not sent by them... However, it also fails for e-mails forwarded by another server if that server is not mentioned in TXT record.

Some carriers offers (or at the least used to offer) a service like that. But this might do the trick https://play.google.com/store/apps/details?id=ru.lithiums.autodialer2

Are you sure? I haven't taken one out, but measuring it looks like 5mm in a 5.5mm hole.

Thanks. So the issue isn't calling specifically but something in the audio stack that calling uses.

crApple finally did something smart. :)

Your cat obviously ate the fish... 🤣 I believe he is referring to new Android 10 features he is missing in Pie.

Too bad.... Contact support, If you not already did. There is no guarantee that they read all in here.

@Sean McCreary has been playing around with it already 😉

Well Apple is already moving the earpods production to taiwan

A while back, oandbackup had problems with symlinks. I tied out AppWhereRabbit and came to like the UI and the possibility to categorise data backups. If I hadn't bought AppWhereRabbit, I would probably just use oandbackup today.After all, oandbackup is opensource. All in all, I think things look rather grim when it comes to "offline solutions". Google is pushing the cloud, same as Apple and Microsoft. You are not supposed to have local backups, local contacts storage, local e-mail, or even use something as devilish as an SD-card! 😉

I agree. The only downside of it being a certain key is having to know which key, which is an issue with stock. Took me about a week to figure it out by accident. At least one reviewer mentioned no wake on keypress as an issue, as its not intuitive to think its only esc. But once one knows which key, it doesnt matter.

Born and raised? Is the playground where you spend most of your days? :D

Just tried to install LineageOS, and it went much smoother than I had hoped. The guide was 100% correct, no guessing needing, and everything went perfectly smooth. (Yes yes, a few documented bugs are still there), So big kudos to @tdm and others that have been involved, awesome job. 😎😎😎

As a betting man, I put the blame on the cable. The charging state when off thing just makes functional sense. The cable still works, but it's been relegated to data only usage. Glad I bought a bunch of new cables from amazon before it got here.

So do you think the charging state was the fix? Did you have to charge it when off, before it would charge when on?

Now you mentioned it I think your correct 😉

Do you ever listen to voice-messages send via WhatsApp? THIS sounds so horrible at the Pro1. Hopefully there will be a fix soon...

I just wanted to mention that I don't care about an aged processor. We knew they had no other choice on it and we also know about the problems they encountered. Corona is one of the bigger ones impacting even big companies. I just want to make sure that they will earn some profit to be able to design a Pro2. And seriously, who cares about some cheap headphones in the package? I'd rather have a bugfree system with high usability than headphones that would get replaced soon after receiving them. Wasting fees and shipping costs for headphones really doesn't make sense.

I would like stickers like the round ones for the cases... I have actually planed to ask a friend of mine that makes stickers to produce something like that.

After a half a year of delay I don't really care if my phone comes later. I have managed to get used to my dying phone for now. I was in India for three weeks and could not make photos because my camera on my phone is broken. I can't always have my DSLR with me. That really sucked. However, humans dying is certainly worse. I hope they are all safe. Being on point now doesn't really matter anymore anyway. Please ensure everyone stays healthy.

Always have to ask. :-) But I understand the frustration too. Have you tried enabling the mode where it can charge when off and then powering it off and plugging it in?

Basically it's a standard Qualcomm device. Meaning that data is encrypted and this cannot be disabled. The method of encryption varies: stock uses FDE while my lineage ROM uses FBE. There is currently no TWRP that can decrypt data but it's on my todo list. If you mean a locked boot loader, yes it comes locked by default, and can be unlocked. However, being a device aimed at hobbyists, FxTec chose to disable Secure Boot. Which basically means that you cannot force your device to only run OEM signed code -- it will always allow you to flash a custom ROM

Yes that is what I wrote: Android Market , http://market.android.com/ ...I know i'm old, but I'm not going to use the silly alias

For anyone interested in trying an Android 10 GSI, I highly recommend using my patched boot.img and vendor.img from this thread. The latest versions of both are regularly updated at https://drive.google.com/drive/folders/1ey6g1N1ORYZ34oRXLYsF4zCCL6_KGRCi These patched images include several important fixes for improved Treble compatibility, including a refined key character map, better keyboard slide behavior, and a working keyboard backlight. The latest boot.img also includes the new keyboard driver from @netman and a fix for the swapped stereo channels on the built-in speakers. Please r

I don't recall anyone mentioning when or whether stock will be upgraded to Q. Has anyone official chimed in on this? Lineage is getting close to releasing Q (which will be 17.1). By the time that happens, I should have Lineage running well and updating should hopefully be pretty easy.