lzb

UPDATE July 18: Sold I am selling my Pro1. The broken promise of stock Android 10, plus the little idiosyncrasies with it have finally done it for me. I really wanted to like this device. The hardware is great. But the software and lack of support from F(x)tec is not what I signed up for. Details: Original Pro1, QWERTY, fully functional running stock Android 9 Includes original box, cable, power adapter, gray sleeve, manuals Extras: Brown fitBAG Rave sleeve Nite Ize Clip Case Cargo Phone Holster Things to know: It has the "bl

I remember all the Facebook ads, showing the Pro1 being used in a business setting, outside at a cafe, with business apps open, etc. This was not marketed for tech enthusiasts. They promised, multiple times, to provide Android 10, and it hasn't happened. I think with the Pro1-X, they are now pivoting to a more tech enthusiast stance. But the original phone was meant to be able to be used with stock, and while the OS is relatively stable, the little issues here and there just make for a somewhat lackluster experience overall. I have half a mind to get rid of it and go back to my Pixel 2 XL, but

I really hope we get Android 10, but I fear I'll be disappointed. The Pro1 is already two versions out of date, and the Android 12 dev preview just dropped, so that's on the way soon. I use stock Android because I am a Google Pay user and that won't work on Lineage etc. Never mind the fact that the Pro1 was advertised as getting Android 10, so not getting it would be yet another ding against the company as discussed elsewhere. On the other hand, if they manage to skip 10 altogether and give us 11, that would make up for a lot 🙂

I'm a bit confused here. Android 10 is mentioned for stock, yet "Android R" is also mentioned. Last I checked that was 11. So which one is it?

I suppose I can ignore it, as long as it doesn't get any worse. It's a retail unit that I've had for awhile, and the issue has only started now (or at least I've only noticed now). Of course if it gets worse the screen will become unusable. The scary scenario is that it's an ongoing issue that gets worse over time, and I've only noticed it now because the spots have "grown" past the boundaries of the screen

I just noticed them recently

I have noticed that the two bottom corners of the Pro1 now have these small "blob" protrusions (see attached). Has anyone encountered these before?

So after almost three weeks, I can say that there is definitely an improvement. I have not had any random reboots at all, even at my work site (which was a known problem area)

I am curious if anyone knows the status of Android 10. We're now officially two versions behind. I realize Android 11 probably won't happen any time soon, but does anyone have insight on the progress of Android 10?

I just received the update yesterday. I'll continue to monitor it and see if it helps.

I have just received the following response from support: So I guess we'll see

Another data point: seemingly every time I come home from being out, and the phone switches from cellular to my home wifi, a reboot occurs. Almost without fail. The opposite, switching from wifi to cellular, does not cause a reboot

I wasn't sure how to capture the logs, but this seems like a major OS-level issue. Not sure how to get it on their radar (other than this forum)

For the record, I just had a random reboot while using my phone as I sat on a bench outside, nowhere near my wifi (on cellular)

I would argue the audio crackling issue was easy to spot, yet it shipped that way, and it took them a very long time to fix. Considering my comment above about their (not) addressing the reboot issue, anything I do would just involve my messing with my network, not really getting any definitive answers, and ending up right back where I am now. Ideally, they should be aware this issue exists, and have a proper development and testing setup to investigate it and fix it.

That is an easier option that would be less destructive to my network setup, but might prevent me from doing certain things, e.g. use Google Home (devices need to be on same network). It would also be difficult to know if it actually helps, since the reboot behavior seems to be random. If I try it for a week, how do I know that on day 8 it wouldn't have rebooted?

Considering that when I emailed them about it, their response was basically "might be a bad app, do a reset," I don't have high confidence that low-level network issues are on their radar. If I did this test, who would I tell? Is someone officially aware of this issue? Do they have an internal development ticket open? Are they collecting data? This is not a new issue, as can be seen by this thread. If they were aware, they would have said something I would think. You're suggesting I do their QA for them, just to have a data point that might be useful down the road, to somebody, if/when they ge

I could try it, but it's a big PITA because I'd have two new SSIDs, and I'd have to reconfigure all my other wireless devices. I didn't use SON in my old router because it was a feature that was added in a software update and I had already had my two SSIDs set up and didn't want to deal with it. But I can't remember if the Pro1 had the same issue then (which might be a hint that it didn't). Also, one buggy device should not dictate my network architecture; it should be fixed in stock.

So it's a massive software failure in stock. I'm a Google Pay user so non-stock is not an option at this point.

I actually got a new router recently that improved my coverage. The only thing I can think of is that the new router utilizes SON (Self-Organizing Networking), which silently switches connected WiFi devices between 5 GHz and 2.4 GHz on the same SSID, might be confusing the Pro1. But still, if that's the case, that is a massive software failure. None of my other devices experience this. With the Pro1, I go for days without issues, and then one day the phone will reboot 3-4 times in the same day, and then it's fine again for awhile.

The random reboots are getting worse. They seem to be much more frequent than when I first got the phone. I don't know what the root cause is, or why they are more frequent now, but it's starting to boarder on unusable. I feel like I need to contact Fxtec but at this point I'm not sure what they can do.

I'll echo some of the reports here. I have a sense that the reboots for me have gotten more frequent lately, can't put my finger on why (maybe the recent OS patches introduced a new bug as @daniel.schaaaf alluded to). Happens during charging sometimes, other times, it's just on a table or the couch or something and it decides to reboot. No idea what triggers it. The only reproducible state in which I noticed reboots was at my work site when the phone was in a particularly weird cell reception area, and moving it from that area stopped the reboots. But I've been working from home for months due

I vaguely remember seeing elsewhere in the forum that Google Pay won't work with Lineage because of SafetyNet, is that so?

In my previous car, I used the iBolt mount system for the device I used before I got the Pro1. It's nice because it holds it at the top edges, so it doesn't interfere with the buttons. It has a universal design, so the holder (I used the sPro 2) itself can be mounted different ways. You can create a custom solution here . I can't speak to its performance when the Pro1 is open, but personally I would never use it that way anyway

Just throwing in my "me too." I sometimes work off-site not too far from my work's main campus in an area with poor cell service, but that has wifi. When I'm up and running everything works fine, and the wifi lets me use Google Voice and WiFi calling with my carrier. I get reboots every so often when I'm here. Always seems to be in the same physical location, not so much in other places (this phenomenon was mentioned earlier in the thread). I'm in the US, on T-Mobile (although considering switching to Mint, which probably won't make much of a difference haha) I will also mention that toda