Leaderboard

Thank you @Waxberry and @Erik -

Serial Number #344 QWERTZ Ship Date: January 21st Delivery Date: February 18th Customs had their great time with it. Unsealed, taken out of the plastic bag and not put back in and full of fingerprints. However, it's totally fine apart from that. Well, physically. Haven't turned it on yet. Edit: Of course I did turn it by now but further posts were moved elsewhere. Nothing atypical. Everything is running as fine as it can in the current software state!

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.

The point is that that the case needs a strategically placed magnet, matching the position of the sensor. It already sends F3/F4 on close/open. So all we need is that F(x)tec alter it from sending KEYCODE_F4 (86h) to KEYCODE_WAKEUP (E0h) and from sending KEYCODE_F3 (85h) to KEYCODE_SLEEP (DFh) YouCut_20200218_095817803.mp4

OKay so I posted this a while ago: https://www.ebay.com/itm/Cartoon-Hello-Kitty-Flip-PU-Leather-Wallet-Phone-Case-Cover-For-Samsung-Galaxy/153051236557?ssPageName=STRK%3AMEBIDX%3AIT&var=452880191076&_trksid=p2057872.m2749.l2649 If you look at the last image, it's white. The seller said that they also have a black - not listed. This is a google drive link that has all the full size pictures as well as a couple videos that show the case being manipulated. It words. My hunt for a phone case is over until they come out with ones designed specifically for the Pro1 It sticks, i

OH MAN are we going to owe you some BEER! You are the greatest!

I believe the core issue is that Android does not have a separate concept of lid/cover and slider. It only has logic for a "lid". We are using this for the slider but it's not really suitable for our usage. Eventually, when some of the more major issues are sorted out, I would like to resolve this by separating the logic for these things in the core Android logic. I'm not sure AOSP would take the patches but I'm pretty sure Lineage will.

I just published what's basically a modified variant of FinQwerty called Fx Qwerty with focus on Pro1 usability.

Only had normal a Xperia Pro and a E-Ten Glofiish M800 (that's some WinMobile thingy) before as far as keyboard phones go. However, I almost religiously watched slow-motion Pro1 clacking videos more often than a normal person would. I went in fully aware what to do to say the least.

I got a cheap case to tests out https://www.amazon.co.uk/gp/product/B07GW2388G/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1 Works well sides are silicone and the back is solid plastic needs the usual holes! 🙂 ofc need something to protect the screen still.

test5 build is up. I've added a changelog section to my lineage page so you can see what is new. Most all the changes from test4 are keyboard related. Please note that in addition to the listed changes: The vendor blobs are unchanged from test4. I got the updated vendor image from @bmccrary but haven't had time to pull in the updated files yet. a2dp is still not working. I looked at it briefly but still can't figure it out. I don't think it's super high priority right now, so I'm not blocking test releases on it. qwertz keyboard users must still set their

It is certainly a big leap between an Iphone and a Pro1. Nice that some variety exists now, so each can find what suit them the best. I for one hope I never have to go back to Ios. Though my magnetically attached landscape&portrait keyboard solution for it worked reasonable well. See here for more images. (Note how it when attached in portrait, is mounted so the device is centred between G and H)

I'd be happy to send you a working SIM card you could use if you would ever want to play around with it.

I've started going through the issues on the github issue tracker. There are relatively few things left to fix to get a good stable build, shown below in rough order of severity (IMHO anyway): * General stability. @Craig reported that test4 was unstable. Please try test6 and report back. * Phone call audio issues. * a2dp does not work. * Virtual keyboard showing and hiding at appropriate times. * FM Radio does not work. * WiFi signal strength does not work. * selinux is permissive. Other less severe issues that probably shouldn't be considered

@EskeRahn yes, just sending KEY_WAKEUP and KEY_SLEEP could work for a simple cover. But if there is a window in the cover, the system needs to know when the cover is opened and closed to show the appropriate information through the window (this is done via the FlipFlap package in Lineage). So I guess we'll see what kinds of covers show up, if any. @mcdinner I'll have to look into the backlight code. It's currently in the lights HAL (this is where @Sean McCreary put it). I don't think the lights HAL will get notified on lid events, so it may need to spawn a thread and listen to

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.

Send me a message with your address and I will send you a few.

Do make sure you have enough key left to press 😂

@Pete I posted this in another thread, but mentioned I would get around to it here, so I'm posting it here as well. I finally got around to doing extensive testing with the Pro1 and both a Motorola Droid 4 and a Samsung S8+ in multiple bands and with multiple carriers. The Pro1 was always 3 to 5 dBm weaker than my Droid 4 in the same band (only B13 on the D4), to the same sites, and from the same locations on Verizon. In regard to the S8+, the Pro1 was always 3 to 7 dBm weaker in the same bands, to the same sites, and from the same locations on AT&T. I used the actual values being repor

....Or someone making a small android program listening on the keyevents, and catching F3 and F4 and convert them to sleep and wakeup. Have you tried if something as simple as the .kcm can do it for us as a temporary measure?

My original batteries for my Sony Ericsson Xperia Pro are still good. The important thing is to remove it from the device (or just insert a piece of plastic as an insulator at a terminal), If the battery is charged and left with only self discharge, it keeps it charge for years, and can still be charged. Just make sure that you charge them say every second or third year, so they do not reach 0V. That is the problem with newer phones, you can not leave them truly off and hence the battery will be murdered, if the phone is just kept in a box, without occasional re-charging. I also got (chea

I've done this with my TV and it was confusing as heck... You need definitely some device that supports chromecast or miracast or whatever (I don't even know which one my TV does), in my case I have a "smart" TV that runs LG WebOS and in the menu i have stuff to enable casting, and then i selected direct cast and when I did that it showed up after pressing the cast thing on the phone, in a small dialog on the phone. And selecting that did nothing. And then I did it again a few times and it started to work xD. I could also tell the TV to do it over the network (it's connected with ethernet cabl

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

I already sent him a few 😄

If you are rooting with Magisk, the first time an app requests superuser access, a dialog will pop up: It defaults to "Forever", but you can tap on that and only have it be active until the app is shut down (Once), or you can limit it based on those time limits in the dropdown list. If you set it to Forever and want to change that later, you can go into Magisk Manager and remove the app. The next time you run the app and it wants superuser access, it will pop-up the dialog again. If you want it to ask you ever time you launch the app, then you can pick Once.

Umm...did you forget the most important thing? It has HK on it! :-)

I found others reporting this same thing online for other phones. It looks like it is just an android bug in how it reports it. It seems to do it with some brands of SD cards, but not others. It only happens when you use it as adoptable (shared with internal) storage. So it seems like nothing to be overly concerned about. You'll just have to mentally subtract half the space when you look at that screen. Apparently other storage tool apps will show it properly, so you could try one of those.

thank you, EskeRahn, the sub-LED test worked just fine, all three colors, that's reassuring - but as observed by others, the notification system for messages and phone calls seems to dead, sadly. perhaps a future software upgrade will help here. or an Fxtec-supported Android 10 install, if/when available ? ADDENDUM : Light Manager 2 finally started to work as described here in this forum (which wasn't the case for me earlier). i guess my recent manipulations with this sub-LED test did something to some permission settings, and now my calls/SMS/etc get their LED spot light attention, fi

To make sure all three sub-LEDs are working, try the first test on the list described in this thread. It turns on Red, Green and Blue one at the time, and then ask if it worked. And if you try oher tests BE CAREFUL! There is one calling emergency with no warning. (see my comments a little down the tread for descriptions in English)

...but if I understand well, I would not have an option to enter a password for root every time. I mean root should not be used automatically in any case... if necessary, some permissions may be granted, but not a general access. If (and when) root access is really needed, one should authorize. ...and not allowing root access (in general) like Android's official behaviour is the opposite side of the horse which is also a really bad restriction. Ps: (falling to the) opposite side of the horse is a Hungarian phrase which I don't know if it is a local phrase or something came fro

I have an LG smart TV with WebOS, but I cast through my Roku box (probably Chromecast works similarly). When I look for devices to cast to, the Roku box just shows up (in fact, mt TV doesn't, but I don't think I ever set anything up on it for casting). So my very uneducated guess is that anything that is on the same network as the phone and provides streaming service to the TV will work. I only cast from one source and that apps built in casting capability works flawlessly. I have no need to cast Netflix or YouTube or stuff like that-- they are already provided by the Roku box.

We actually know the raw production price without paying any licence fees or anything from the customs documents ($300), and we have heard them call these fees "hefty", so let us for a moment assume they at some point have sold enough at current price and have paid all the development costs with interests, I doubt they would be able to ship them even with zero 'profit' for $500, so I don't think there is a huge margin to cut from... So don't hold your breath for it.

That is why I like my QWERTZ keyboard (and would be much happier with unshifted QWERTY anyway). Keys are exactly where I would expect.

Yes - for the USA, the reduced keyboard is fine. However, in other countries, where there are also other characters (in my case áéíóöőúüű and its capitals but other languages have û, è, ê, ë-type characters and so on) there are more buttons needed for proper use. They are similar characters like a,b,c - so o,ó,ö,ő are different alphabetical characters which are not exists in standard US keyboards. As of programming and terminal access - for these purposes, I use a PC... but in a relatively rare case when there is no PC around and I may use my phone instead, it is a life-saver... So

You should try tipping the keyboard against the light, and at the right angle it can be seen that the yellow print (and the green Caps) is a coloured square slightly lifting the black. If you got sensitive fingertips, you can actually feel the slight 'jump' gliding the finger lightly over the key tops with yellow print. NOTE that some got the mat but NOT the print, I guess prepared for different prints. (e.g. the W on qwertY). It is easiest to spot on Caps. I tried to extend the small green dot on the preProd unit, not that succesful, but it clearly shows the white under green under

It sends keycode_home afaik

Sure, I was just trying to figure out a way to implement that without having to wait for OTA update. I guess I'll just wait until FxTec enables it. Thanks for the video, I just installed a magnet in my case. Have to wait for FxTec now 🙂

Yes its very confusing and i havent worked out yet. I have noticed that in a shopping center i by mistake taped cast and it just showed me available devices to connect, thats wired to me. i guess there were some smart tvs there?

I know this is an AT&T topic, but I contacted t-mobile on facebook (t-force) and will report back with my findings, as it pertains to getting it provisioned for wi-fi calling. UPDATE: I now have wifi calling working on T-mobile with the Pro1. As I said I would do above, I contacted them on facebook (that is supposed to be the place to get the best results). They call that group T-Force on there. I sent them a message stating that I'd like to get my new phone provisioned for wifi calling. They said I needed to have an E911 address set up in my account online, for this line. I wen

If wi-fi calling works, then you can place a call in airplane mode, with wifi enabled. Tried and verified with the Pro1 by myself (Telia Sweden). Keep in mind that most operators still require specific phone models in order to provision wifi calling. It's likely that AT&T doesn't allow the Pro1. Most operators have become more lax the last year. The reason why they have been so restrictive is because the lack of standardization and stability of this feature, according to the rumor mill. Telia has however switched to a more lax model recently, as I didn't expect this to work. An

Seems like this is on topic for this thread. Does anyone know where to get spare batteries yet? If the battery was to blame for not charging (probably not as likely as a poor USB port connection), then a replacement could be put in place. Either way, I'd definitely like to find where these are sold and stock up on some for the next 10 (hopefully) years of phone use!

Patriot and it was in my Priv before, formatted by the Pro1 after insertion, set as internal.

Yes, there are two hall sensors. I'm not sure if they are both present and working in hardware though. Supporting both hall sensor may be tricky. I'll have to dig into it if/when someone makes a flip case. But I think there is really only support for one "lid" sensor in the Android framework. And that is used by the keyboard slider. This is oem_hallb in the DT file, and it generates SW_LID. The other hall sensor generates key F3 which seems strange.

As far as other posts goes, the Pro1 does not seem to support exFat, so go for Fat32. There is a thread on SD here as well, so maybe a more relevant place to start. But I see nowhere mentioned that ha can not see the card at all. So Let us keep the camera stuff apart

@tdm Hello Since you're The Pro1 Developer, do you think it might be possible to add kernel support for "battery idle mode" - I mean the state with charger plugged in, when battery is charged to some level, for example 80%, but is neither charged up further nor starts discharging - phone takes energy from charger, but not from battery. There are apps that can utilize this mode to preserve battery life (i.e. ACC: https://github.com/VR-25/acc/ ACCA: https://github.com/MatteCarra/AccA). As for now, with these apps, Pro1 stops charging at given threshold, but instead of keeping this

Thank you for your consideration. 🙂 I generally don't accept donations when I've been given a device for development. But I've spent a lot of time on this device. Here's my paypal: https://www.paypal.me/tdmcode

Those secret special android based apps! I am aware some Android apps are linux based. I mean why not, its not that hard to make an android app out of an existing linux app if you know what you're doing. It's also pretty clear many SailfishOS apps are linux based. I mean, sfos is more linux than android; we have gcc, we can build from source on device and run it. That is a major step closer to real linux than Android. In fact, manhy linux apps just work on sfos already. Like other linux distros. I forgot why I started writing this.

You should quickly buy stock in Aukey, before @EskeRahn buy's all their ultra ultra slow chargers. 🙂

Ah ha! So the prophecy came true! :-)

By the way, thanks @EskeRahn for this neat little trick. I don't usually deplete my Pro1 sufficiently to require it, but it'ds nice to know I don't have to worry.