david

Thanks for the information. It is appreciated. Just an idea, but for the Pro2, maybe you could put indents/slots in the 4 sides of the keyboard part of the phone. This way, a case could be made that has fingers that clip into those slots instead of needing to have fingers that wrap around the top of the keyboard and interfere with the opening mechanism (creating a gap and getting in the way of the user opening the phone). Secondly, it would be great if you could release the 3D models of the Pro1. This would allow 3rd party case makers to design cases and, probably more likey, woul

I was referring to the corners of a certain phone that found some rocks recently. 😉

I don't think that is how this one works. I could be wrong, but I think it is part of the case.

And might end up with "Wow, I bet that was a really slick looking device before all the plastic pieces were missing and screen was cracked from dropping it." 😉

I couldn't resist posting this one from the USA ebay site: SAMSUNG LED Wallet Cover Case for Samsung Galaxy Note 7/Note FE EF-NN930PBEGUS https://www.ebay.com/itm/SAMSUNG-LED-Wallet-Cover-Case-for-Samsung-Galaxy-Note-7-Note-FE-EF-NN930PBEGUS/143430310894?hash=item21651cdbee:g:m~IAAOSwaShdvd3b:sc:USPSFirstClass!55025!US!-1 That's a flip case with a built in LED clock. 😄

Thanks for that tip on the other model name. "Note 7" produces a lot of false positives, because other companies have "borrowed" the name. I've started including "samsung" in the search terms to counter this. I'm not a flip case type of guy, but thanks for the link to that one. I appreciate it. For someone who does like those cases, that seems like a nicely priced solution. I do have a question about flip cases. How is the phone held in place? Update: Nevermind. I figured it out. I was wondering why you had one of the other cases on the bottom of the phone while it was in th

Thanks @EskeRahn! It looks like Note 7 cases are the best fit. I wish there were more of them available in the USA. I'll have to check out ebay here to see what is available. I couldn't find them on Amazon.

Okay, after *many* hours of fighting with this, I finally fixed the tablet. That was quite the challenge. If anyone wants more details, feel free to ask, but I'll try to explain what I tried that failed and then what finally worked. First off, I had a stock ROM, with Android 5.1.1, that was rooted before I began all this fun. This is a Samsung Galaxy Note 10.1 2014 Edition (SM-P600 = Wifi version, not cellular). The method I used to root this previously is this: https://www.droidviews.com/root-galaxy-note-10-1-sm-p600-and-install-twrp-on-it/ I did flash TWRP 3.3.1.0 and then

I'm guessing the people who tested the phones are still under NDAs for some things, but I have wondered this same thing. Hopefully we'll find out in the next week, when people start getting their phones. It certainly can't be worse than the Pixels! I should preface that by saying that when Pixel phones get a couple years old, the batteries are horrible. When they are brand new, they are okay. However, I really can't believe what they did with the Pixel 4 (regular sized, not XL) phone battery size. With all the trouble they have had with batteries failing (which again causes them to n

I have Linux virtual machines that I can use, but thanks for the help. I decided to keep trying to get it working without flashing the stock firmware over the top, partly in an effort to see what could be done if I get stuck in the future. I'm still fighting it and will fight it a while longer before doing the firmware flash. I'll say it again: Be very very careful if you decide to mess with changing resolutions. On the Pro1, it might not be a big deal. I guess it depends on whether their launcher was made to handle multiple resolution devices. It seems like every bit of Samsung

I considered that build.prop might have different cases for the 2 copies. Windows apps that work with tar aren't the most robust. Most of them didn't even show the duplicate when browsing the .tar (without extracting). Also, it appears there is a way to add true duplicates to tar files, so that could have been done too by TWRP. Since my data should be intact if i reflash the firmware, I'm just going to do that. I'll take a nandroid backup of all existing partitions first, just in case the new one doesn't boot. If I have to revert back to the existing system, I'll try transferring t

Update: The tablet is still messed up. I've been at it for hours. I took a nandroid backup with TWRP of the system partition and then extracted the build.prop file with 7zip in Windows (after changing the file extension to .tar). Unfortunately there are 2 duplicate filenames in the tar file, with one containing the security information for the file. This means that I couldn't put the file back with 7zip, due to the duplicate file. I deleted the file containing the security information and then restored the backup in TWRP, but it got stuck in a boot loop. I tried creating a local.prop fi

I remembered that I have a tablet that is rooted. It sort of worked, but it wasn't perfect. I told it to pad 200 pixels on the top and right. With the tablet in portrait mode, that was the right and bottom. It was correct when held in landscape. So it is not relative to how you are holding it. You would have to trim all sides by the amount that you want the curved sides to be trimmed. Some apps still had a background that went past the trimmed part, but the user interface of the applications were still within it. The launcher cut off the icons of the app icons too. If it was only done

I wasn't overjoyed with the size, but am glad it wasn't 7", like @EskeRahn commented on. I would have bought it, but I would have been very upset at that being my only option for a keyboard phone. I really was, and still am, disappointed at the curved screen. It may have been the only type of screen available at the time and in that size range and they could have tried to spin it as looking better, but didn't pick it for aesthetics. But if it was hand picked, then I don't agree with the choice for a phone that doesn't have bezels and will be very naked when opened and where peopl

The Nov 8 tweet stated that the phone still needed to clear customs in the destination country(ies). They could have been at the 3rd, 4th or 5th tick above. It should be an interesting week.

What is being referred to is that on Nov 6, a tweet went out that stated the phones were past destination customs and at the destination warehouses and it was just a matter to get them to the shippers and send out tracking codes. 2 days later, another tweet was sent out that stated the phones had not cleared destination customs yet.

<refrains from comments about private delivery services> I'll await your comparison of all these options! Thanks for the hint about the camera opening in the case too. I wondered how that matched up with these cases.

😂😂😂

When will the Master Tester be testing those? *grins*

My guess is that some people who are upset about the delays fear that there is a chance of losing their money. They'd rather get their money refunded now, since that appears to be a sure thing, rather than risk it later (if it turned out to be a scam or fxtec were to go bankrupt...and to be clear, I don't think it is a scam, but some people from some countries do have that fear). The other reason could be that they need a phone sooner rather than later (due to issues with their current phones), and have been in that state for a number of months, so they are reaching their limit for wait

If anyone is able to find something like this on the USA Amazon site, please post. I searched around and couldn't find something like it. More Note 8 and Note 9 cases and cases for a Note 7 by a different company (not Samsung).

When I saw "gapps", I remembered that was a separate install. I completely forgot about that. I haven't had to install it for years. I just used nandroid to move everything from one phone to another. I'm on CM11 too. That was the last one made for the Relay 4G.

I believe this pre-dated that type of processing. I know current camera apps do a lot of that after they get the raw data from the sensors. Back then, I think it was mainly in how the drivers talked to the hardware. Hopefully, the google camera app ports will cover this issue for the Pro1 on LineageOS *if* the fxtec camera app doesn't work there for some reason. I don't see their camera app not working there though, unless they feel there is more value in keeping it to themselves. To be honest, I've always assumed the google camera app ports would work better anyway, since they have

Or the room sized version, where it takes 2 people to type on it:

I've never had any issues with Cyanogenmod on my Relay 4G. LineageOS might have changed a bit since their Cyanogenmod days, but if not, then you should be able to run everything there that you could on regular Android. The only problems I had when I went to Cyanogenmod were: 1) The camera quality went way down. 2) The GPS quality went way down. The drivers for those two things were proprietary, from Samsung, and whatever they replaced them with were not very good. I'm hoping that won't be the case with the Pro1, since fxtec seems to be very good about opening things up