Leaderboard

I've been working on an app to restore the backlight functionality on LineageOS builds (It will NOT work on stock). It's called KB Backlight Manager. It runs as a foreground service to monitor the system for the slider events and turns the backlight on or off depending on it's state. It also includes a QuickSettings tile so you can easily turn it on or off from there and an option to disable the backlight completely as well as an option to enable/disable the QuickSetting tile. You can get the latest builds over on the Github page for it here: https://github.com/JooJooBee666/KB_Backlight

In these kinds of situations it may be worth sending the insurance company in question an e-mail and asking what they can do, I think.

Well, a full answer to that question would be quite lengthy. The brief overview is that there are different parts of the (cell) radio stack and certain parts are subject to vendor changes while others are not. Generally speaking, Google and Qualcomm rarely agree on things outside basic things in the system and will implement them in different ways. This leads to AOSP hardware support for Qualcomm devices (eg. used in Nexus/Pixel) having one set of code while the Qualcomm BSP code is different. This is most apparent in things like advanced audio (compression, offloading) and the radio stack

Essentially, there is no difference. One needs a mule phone to make this work (see the original pages of this thread) because Verizon won't activate the Pro1 directly. Your mule was the S10 (which I know works, because I did it for a friend with his S10, and I have also used an S8, both work fine -as should just about any other phone that supports VoLTE with a SIM that is also compatible and provisioned for it). That's all that is needed (hardware wise) to get your Pro1 up and running (sans the CDMA network). The only difference between what you did and cfeltych's experience is that he

Forgot to add, the Verizon tech who got my Pro 1 working was extremely impressed by it and said she's going to order one herself.

I noticed that there is a very limited (read - stock) support for dual SIM operation. One would expect at least a couple of functions every other manufacturer implements for dual SIM: 1. ability to assign the SIM to use for a contact (e.g. I use my personal number to communicate with my family and friends, but use my business one for everything else. 2. ability to select the SIM to make call before the call is made (stock option is to have the default SIM for calls defined and a button to switch SIM during the call, which is inconvenient and most of the time expensive. Moto Z ha

Unbelievable! I'm getting it tomorrow. Assuming it actually arrives, that's 8 days from ordering it to getting it (29th Jan to 4th Feb). If anyone is in the UK (or possibly Europe?) and wants the phone soon, it seems that ordering from Clove is the way to go. I only ordered it on Wednesday 29th Jan. I now have to get my refund back from FxTec... (I have already asked for it, but have only had an autoresponse so far.)

...Sometimes when printing wears off stickers it leaves an 'inverse' image that can be viewed with certain angles/light sources. Have you tried shining various lights at it and seeing if anything is visible? ...And now I'm glad I removed my sticker and stuck it on the packaging.

Hi there, Don't know if it's the right place. If I may, I have 1 potential bug and a request. It happens time to time that 4 specific keys, once pressed, are repeating themselves until I press another one. Such as the 'Key pressed' event is recorded but not the 'key release' event. It concerns keys [6][7][n][m], and it is not always the case. It give a text like "mmmmmmmmmmmmmmmmm" or "66666666666". It happened maybe 10 times this past week. This behavior can disappear if I close the keyboard and switch the phone to sleep, but not always. I have the stock android, with last update.

If I'm understanding what you are saying... your DMD request would have been denied, and, yes, the SIM card (and account) would have needed to be provisioned for VoLTE.

Oh, if it were only that easy! A request to put a block of IMEIs into the DMD database needs to be requested by the manufacturer of the device, and that's only after they have a signed contract with Verizon saying they will pay for the necessary hardware testing to verify compatibility on/with the CDMA network. Should the device pass all of Verizon's requirements and tests (and the manufacturer is financially current), the DMD request will then be accepted, reviewed, and processed. It is possible to submit a request for a single IMEI, but it's only taken seriously if the device has already

In Germany we call them Teledoof (Tele-dumb) or Telekomiker (Tele-comedian). While they probably got the best network,their support sucks big times.

So I finally took some pictures of the holder and wireless charging pad I'm using. There are thinner and smaller wireless pads available. But I already have this one, so I haven't bothered yet looking for a smaller/thinner one. If I had a bumper, I would definitely keep it on there. That's how I used it on my Sony XZs. I don't really need the physical port. The pictures show it works just fine. Both holder and pad are from Baseus. The holder has a sensor but also operates on touch. I'm stil contemplating on how to provide power via the air duct, so the cable isn't visible anymore. The wire

Oh I'm on the 3.dk network, and have no networks issues either.

I experience distorted sound from ear speaker due to high volume which can't be lowered any further. I bet it will get better when the high volume bug is sorted.

You are right about this and I fully agree with the influenza comparison. But this doesn't change the fact that the factory is closed.

I do not expect to here anything on the subject before general availability of the device. If a Scandic mat was available and easily user replaceable I would also buy some of them. But as I understand it, the keyboard is the only thing glued on, needing a heat gun. So not super user-replaceable, and I assume swapping it our selves would void the warranty... (Though I bought a heat gun for the purpose already....)

Ah yes, the claim and then if challenged the other person should just google it themselves, and with an implication that that other person isn't that smart with a passive aggressive tone. Language changes by the way, and there's no reason to believe it's currently sexist.

@david I'd like to explain Germany when it comes to politics and european rules. If we are lucky, they will indeed be implemented in time. In this case, since the frequencies weren't used before, it's easy to do. But then comes the usage. In Germany, frequencies are sold when new technology is introduced (I guess that's the same everywhere). The last auction had the previously named frequencies, 3-4GHz and I think 6-12GHz. Higher frequencies could be sold later, I haven't read anything about a MHz range (although that doesn't mean that it couldn't come). The EU goal meanwhile is

I would, but I have the distinct honor of having serial number #999, which I quite like, and thus may want to show it off at some point. Unless all the labels say 999, in which case 😕

Curiously, I've been using it on my device. Works great! The backlight was finicky but this fixes it.

First of all, thanks to everyone for this post (and especially the quoted block from @windraver)! Long time lurker, first time poster 😁 I managed to get my Pro1 up and running on Verizon, bringing my SIM over from a Galaxy S10. When I initially inserted my SIM, I had no data connectivity. To get data working I did the: *#*#4636#*#* + enabling all toggles on Phone 1 + setting to LTE Only I'm trying to better understand the difference between what I've done, and what @cfeltych got done at the Verizon store. @cfeltych: did you or the Verizon agent do the step above? If not, maybe folks can

Hey, if Veri$on employees start using the clack, maybe it will get supported officially! Well, I can dream LOL. But another clack sold is another brick in the future of clacks! Yay!

I live out in the country in an area with a lot of hills. The Pro 1 has held a solid signal no matter where I've taken it. I even get a ghost of a signal in "farmer Faraday cages," AKA windowless metal pole buildings. Voice call quality is excellent, and using speedtest.net I'm getting 30-40 Mb down/10 Mb up consistently. In rural areas around here Verizon has repeaters set up every two or three miles that my S5 could never use. The Pro 1 finds them all. Now all I need is a stable Lineage build...

I completely agree. However, there are times where I see it as just fine to return a product that didn't work for me in an application I was testing as long as (1) it is in perfect condition and able to be resold, and (2) I pay for the return shipping. Furthermore, I also don't ask for a refund of the original shipping out to me as it isn't the merchant's fault, or responsibility, to absorb the outbound shipping cost so I can test an item at his/her expense.

Bad SJW troll. No cookie. 🙂

Thats insane! ... hope it arrives with no more issues ... I ordered 2 weeks ago, still waiting (which I know isn't too bad compared w/ pre-orders)

Gboard AND (Pie OR Pro1) 🙂 Testing on another Pie device with Gboard could provide a useful data point. Either way, I've filed in-app feedback from Sheets on Pro1, maybe something will come out of it.

Yeah, tried that, and it deletes characters as well.

Just had a great experience with a video call through facebook messenger. Even got wows about the front camera wide angle and quality being so cool. Audio was working fine too.

I merged the threads... See about 6-7 hours back where we were looking at these double-cases, what is important for us is whether the display part goes over or under the bottom part.

The way it worked with my Huawei P30 Pro was just fine for me. You just select the SIM once for a contact and it sticks, both for SMS and Call. I still need to confirm it but it looks like it works the same on Pro1.

IMO, the problem here is that you are purposefully ordering cases for a phone that you don't have and aren't intending to use the cases on for the purposes of testing in hopes of finding something for the Pro1. With a shirt, you would be ordering it for yourself based on prior knowledge of your size, colors/patters you like, etc. For example, If you are a size small, and your experience is that most small shirts fit you, so you ordered it and it didn't fit, then that's on the manufacturer (with the seller sharing a portion of the burden) for not sizing it properly. That's very different th

I don't know about the magic phrase. I called T-Mobile and (because I have been a customer since 1998) was transferred to my special support team. I asked them to turn it on and they did. Wish I could help you more.

The Verizon tech did everything. I handed her my phones and she took care of it right there at the counter in front of me. I think provisioning a new SIM in an established phone originally purchased from Verizon, then moving it to the Pro 1, made a difference. The only adjustments made after the SIM was moved was to the network configuration in Settings. I asked if *#*#4636#*#* was necessary on the Pro 1 and she said no. She said she would submit a DMD request form for the Pro 1, it's an initial step for Verizon to approve the device.

Yes, inner slot is for SIM1 and dual slot is for SIM2. When I remove the SIM2 and reboot there's no warning, SIM1 is still in slot and is working fine. But as soon as I reinsert the SIM2 it says "SIM 1 not provisioned" SIM1 is still in slot and is working fine. On the Keyone it correctly says "SIM2 not provisioned" as my SIM2 is not activated or connected to network.

It would also be elegant if you could choose based on country code. If you are inserting a local secondary SIM abroad, it might well be the cheapest to use your standard SIM to call home, but the local SIM to call locally and data. A bit spinning off from your topic: It is odd that more things are not per contact. E.g. when you text with a contact you are quite likely to do that in the same language each time! So assigning an active spelling/typing language to a contact seems bleeding obvious - they could even offer to set the default by the country code unless you override.

If you enable Developer Mode you can force APTX or any other codec for that matter under developer options... Try forcing it, maybe it will succeed. It could be just a handshake issue.

My pleasure. The relationship is purely a logical software one. It reads the RSRP (received power) & RSRQ (received quality) and then converts it to a bar graph and numerical and/or percentage. Simple as that. The Pro1 is being more honest about things, not sure if there is intent to deceive with the BB or not, but it's not even close to being accurate with 4 bars. I don't think lying is the correct phrase to be used with the LTE Discovery app (as lying implies intent), but the app is often incorrect, and most people don't know because they don't really have any other wa

Did you try peeling it off? 😁

I just noticed that not all the soft front and back cases have the edges front over back, some have back over front... So this might work for the display part. Though the edge part could be an issue.

Well, it can't be disabled; however, in the case of Verizon, (if you could flip it off) it would then mean voice calls couldn't be placed or received over their network (since there isn't CDMA access).

@silversolver It has been my experience that, regardless of the hardware/phone, LOS has those switches grayed out and just uses the provisioning of the SIM card. Recently I helped a friend setup a LG phone (he was on the list for a Pro1 and his current phone died so he bought one for $15 on ebay to solve the problem. I found it to be a simple and elegant solution to the longer than expected wait times of the Pro1, but anyway...) and the LG was the same way (I have done others too). So if the mule isn't running LOS (or a version of LOS where they aren't grayed out), and the switch for VoLTE

Yeah it seems broken here also. I must have broken it yesterday, possibly with my audio prop change. I'll get that fixed and the fingerprint data fixed for Monday.

Same here! Mine doesn't rattle in open position. Only noise that I can hear comes from flat cable (in closed position) and SIM tray. I am very satisfied about the quality.

Hi community, I don't have yet the phone, and my apologies for coming back with that. I'm using a QWERTY keyboard all the time, typing different languages, and one is french. I really like the "dead-key" approach, as it allows all combinations for accents. I notices on most keyboard layout the è or È, à or À, ç or Ç are missing. With dead keys it is intuitive to get them. Do you now it this is implemented on a software or with finQWERTY ? Thanks !

It really doesn't have to be certified by Verizon anymore. It has to be certified as meeting the Open Development LTE requirements. The problem is that the idea of Verizon-certified phones is so ingrained in their system and their culture that it has to be done manually, and very few Verizon employees know how to do it (nor even that they're allowed to). The easiest way for a manufacturer to avoid hassles is to get their phone certified as meeting OD LTE requirements first, and then submit it to Verizon for approval. If it has the right radios, it should be a rubber stamp approval that wi

A. Both Verizon & Sprint use CDMA for 2G/3G. This doesnt' even require sim card. In the US we started with AMPS (first generation, "1G"), then when digital came around (2G) we had two choices of technology, CDMA & GSM - what did you have for 1G and 2G? ( 0 choices for analog and 1 choice for digital I'm guessing). Regardless, sim cards weren't needed until AT&T and T-Mobile decided to go GSM . The other two carriers, sprint & verizon, chose another technology. Until 4G LTE came around, which uses SIM cards, Sprint/Verizon didn't care about SIM cards, and even now, if you

Thank you for the quick replies and communication. I appreciate it!

I'd like to reassure you the device has actually passed the Google certification, which it wouldn't have if any of the suspicions mentioned here were correct. Adups, in this scenario is simply the name of our OTA provider - http://www.adups.com/index.php?lang=en, not the virus conveniently named "com.adups.fota.MyApplication" and others, neither of which match the files used for running our OTA software. I believe that particular virus known as "com.adups.fota.MyApplication" was only named this way to mimic a legitimate system app. com.adups.fota is flagged perfectly clean on