Polaris

Humm... I find your observation very interesting. Why do you think that extra keys inserted between the left edge and the A is constant trouble for you, but the same amount of keys inserted between the right edge and the ; is quickly adaptable? Are you thumb typing, or finger typing? I shifted all my keys using a keymapper and it seemed to provide the same amount of trouble for me (other than the numbers lined up correctly). Either my left thumb wouldn't naturally land on the F as a home key, or my right thumb wouldn't naturally land on the J. Same problem just one side or the other.

Not really because with a symmetrical keyboard your thumbs will automatically land on F and J as your home keys. If you are familiar with a QWERTY keyboard then the rest just comes naturally. At least this has been my experience with every physical landscape keyboard I have used (which have been many, about 10 different devices, and I have never (previously) had trouble acclimating to a symmetrical keyboard).

Will do, I'm just trying to figure out if the problem is common or uncommon.

@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

I'm glad it works for you. If I wasn't using USA English I would probably feel like you do (then again maybe not because the arrow keys can be used for double the characters). For terminal use and programming I use an UMPC not a phone so I'm basically looking for all the alpha character keys, numerical keys, and all the popular punctuation and symbol keys. I only think there are about 3 too many keys on the Pro1. I'm not suggesting they get rid of all of the extra ones, but only three. This would allow those of us who thumb touch type (meaning using thumbs, but without looking at the

The QWERTZ version would still be a problem for me as there would still be extra keys in the mix, just on the right side instead of the left. Personally, I don't see a difference between the two except for the QWERTZ version is more like a full size PC keyboard (which doesn't interest me as I'm not looking for a full size PC keyboard). As for the cell signal strength, I have now done extensive testing with this 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 loc

My notification LED/light suddenly, and inexplicably stopped functioning. There is nothing wrong with the hardware, so it must be a software issue. To be clear, what I mean by this is that if I'm away from my phone and there is a notification, say an incoming text message, the phone used to blink the notification LED/light. When I returned I would notice the bright green blinking LED and know I needed to turn the phone on and respond. However, for whatever reason, it just stopped functioning. I'm using the latest firmware, everything is completely stock, and I haven't yet loaded any 3rd p

Huh?!? Are you saying that you didn't do anything other than the LED test described by EskeRahn and then the LED started working again????

Right, this was bound to happen. There is one sure fire way to know for certain if a device is considered authorized hardware by Verizon. Switch the network preference to CDMA/EvDO auto, and see if it's able to use Verizon's CDMA system. If the answer is yes, then I'll believe it, otherwise it's using a mule account as it's identification.

Very interesting about your phones. I hope it all works out well for you. In my case, I had a phone on order that wasn't shipped. A friend (who I told about the Pro1) pre-ordered much before me and received his last month. He didn't like it, so I offered to purchase it from him. I hate to say it because I really love what the guys at F(x)tec are trying to do, and want to support physical (landscape) keyboard phones, but I can completely see why he wanted to return it. I'm not very impressed with the shifted (QWERTY) keyboard, and the (cellular) transceiver is extremely weak compared to

I must have missed your posts about you needing a replacement phone! Resetting the phone (to the current firmware) is easy, just an option in settings. I don't have much on mine and don't mind doing it so that's an option. I was hoping to be able to find the issue without a reset though to help all of us when it happens again. I'll wait a bit and keep messing around, but if there isn't any other solution, I'll reset.

@VaZso Did your friend ever try a factory reset? Or is he like me and is waiting for more input before going that route?

I should have mentioned that I saw this thread (before you posted the English, thanks for that), and did test the multicolor LED. All the colors, RGB, worked in the test. It also works properly when charging. However, the missed, or incoming, notification flashing/blinking isn't working anymore. Very strange!

Humm... this is interesting... as for the charging, I believe it should be steady red while at or below something like 90% (I haven't monitored the percentage closely), then switch to green when it's adding the final charge and then is fully charged. So you never had the LED flashing to indicate missed calls and incoming SMS/MMS messages. WOW!! That would be absolutely awful, and potentially a deal breaker (as a daily driver) for me as I'm not one to continuously turn my phone on dozens of times per day just to see if I happened to missed something (which is often the case, especially with

Thanks. Mine is the exact same way now (it was working then suddenly stopped) . Sometimes it will actually blink once (green) right when it receives a message, but that's it. Otherwise it's only steady red or steady green when being charged. Anyone have any ideas?

Ok, so just to be certain that I understand you correctly, you are saying that without the app the notification light on your friend's device was acting like mine in that it stopped (or wasn't in the first place) flashing green for missed calls and received messages. Do I have this right? Anyone else experience this with their Pro1? Any recommendations on how to fix it without a factory reset (which I don't mind doing, but would like to experiment before I pull that trigger).

Thank God it's just half a mind because your posts are super informative and I, for one, would sorely miss them. Thanks for all you are doing for us!

@VaZso Per your "Correction" posts above, I have a question... On your friend's phone does the green LED blink correctly for missed calls, and you just want to change the color (which isn't working on his, but is on yours)? Or is the LED not blinking at all? @Everyone: My green LED was blinking for missed calls and new text messages, but that completely stopped recently (not sure of the exact day as it's not a daily driver (waiting on LOS), but it was sometime this past week). Is this a thing, I couldn't find it posted as an issue...? FYI: My phone is back to being completely stoc

I agree with everything you said. I took him to mean that he doesn't want to grant access to an app and then have it indiscriminately be able to access as root at will. If you assign the root permission, but then toggle root off, or switch to ADB only, the apps won't have access until it's toggled back, no?

Understood that as well. I'm certain it hasn't happened, or at least Verizon hasn't been contacted yet.

Sadly, it's not speculation as I am 100% certain that the Pro1 phones are not certified for use on Verizon. I know this due to having an employee check for me on a regular basis. However you can know too by checking the BYOP link. Just plug your IMEI in and it'll deny it because it's not an approved device. https://www.verizonwireless.com/od/prepaid/bring-your-own-device/#/checkDevice

Yet another reason to use LineageOS! You'll have a slider (at least in v.16) that allows you to turn it on and off. There is also an option to select root access for ADB only, apps only, or both ADB and apps. It's a great setup.

You are correct. Verizon hasn't approved a DMD request; thus, as of today, our Pro1s aren't in the DMD database for activation. It's that simple. They probably won't ever be either because F(x)tec would have to request certification, and then pay for all the testing which is required to certify network compliance. As such, there is no way to activate, and provision, a fresh SIM in a Pro1 on Verizon's network, period. You, me, a store rep, a phone rep, a network engineer, or whomever, will need a mule phone for initial activation and provisioning of a SIM card.

Gee Wiz dude, enough with the excuses! Will you hurry up! 😉 😉🤣🤣

I believe QDL mode on this device is just Qualcomm EDL mode. Thus, you are actually in EDL mode and don't have anything to worry about in this regard. However, your problem will be that I don't THINK that @tdm has uploaded his corrected tool yet. I know he was working with @EvilDragon to get a device unbricked and discovered that his tool (thank you again to him for creating it!) wasn't actually writing all the data it indicated it was writing. I believe this to be the case because after he posted about it, I attempted to d/l the tool again, but it appeared to be the same version as the on