Zamasu
-
Content Count
218 -
Joined
-
Last visited
Posts posted by Zamasu
-
-
I'm still on LOS 16 because I was too lazy to manually update when it said I couldn't automatically update. Could I go from 16 straight to 18.1? I'd rather not lose data, but it's not critical.
-
1
-
1
-
-
Any idea what this means for security updates for the 835 and LineageOS for example?
-
1
-
-
13 hours ago, claude0001 said:
In all honesty, I find that the Pro1 is some "in-between" solution that seeks to be compatible with, both, thumb-typing as well as multi-finger operation (when the phone sits on a table). As a result, it fulfils both roles pretty badly (for me at least): I could thumb-type much faster on my (smaller) N900, and I am not really able to use more than two fingers in "desktop-mode" either.
I find the Pro1 pretty good for thumb-typing. The keyboard is approaching the limit of how wide it should be to be comfortable, but for me it's not too wide yet. I don't think it's a "jack of all trades, master of none", to me it seems like they chose to focus on thumb-typing, with desktop-typing being more of an afterthought. And the Astro Slide looks to be significantly worse for thumb-typing.
They seem like different devices accomplishing different things, and I'm not interested at all in the Astro Slide. I like the keyboard to quickly flip it out and type something, on the Astro Slide it seems like more of a commitment.
-
3
-
-
I think you're mostly right. I don't think you should consider this a "normal" pre-order or even order, there are huge red flags that indicate to me that you might not get your product or your money back. It's not a malicious company or anything though, I fully believe F(x)tec wants to supply these products and refund the people that want refunds (though they probably want you to enjoy the product instead), this just seems to be a fact of a pretty small company trying to do something very ambitious. There's a risk that's normally not present when buying products, however if you approach it from a crowdfunding perspective I think the risk is pretty low. They have shipped products, they're still shipping products, they have issued refunds, and there are no huge issues with the hardware. Compared to other crowdfunds this is a pretty safe bet I think.
Regarding the repair support, that's also a risk you'd need to factor in. Personally I'm just hoping I won't be needing it ever, which is obviously not something you can actually count on. You can try to mitigate it by being extra careful, but accidents happen and manufacturing defects can also happen. Judging from this forum it seems that manufacturing defects are slightly higher than on something like a Samsung, but thinking logically that's to be expected and I don't know if that's actually true because you obviously don't have the full picture from just looking at a forum. In my personal experience I don't think I experienced any actual manufacturing defects, sometimes the battery doesn't seem to want to charge but I also have some root software installed that's mucking with that and magnetic plugs instead of just plugging in cables, so I can't rule out if that's something I caused. Aside from that it seems to work fine. There are a lot of moving parts though, and some parts feel a bit wibbly wobbly but I think that's expected behaviour. I could see this being more difficult to assemble than a lot of other phones though, and thus I could see manufacturing defects being higher for this. Again a risk you need to consider.
So my thought is that the risk is somewhere between a regular pre-order and a crowdfund. Not bad, but not great. And this is something you'd need to evaluate yourself if this is worth it.
-
3
-
2
-
-
I appreciate F(x)tec trying to supply an official Android version that supports Google Pay and the like, but from what I've seen the updates for that are pretty slow. This seems mostly due to their partners, and there are probably costs involved, but the latest update (including security updates) was months ago. Meanwhile LineageOS seems to be getting almost weekly updates. Granted I don't think I've ever really noticed a change between versions, but there are still security updates in there. It's probably fine to not have those security updates, plenty of people go through life just fine without updating their phones, but still the option to get them is there.
There's also AICP, which seems like LineageOS but slightly more flexible. While LineageOS has more manpower behind it to be pretty buttoned up regarding update schedule and presentation, it's also maybe a bit too rigid in what you can do with it. From the little I've read of AICP it seems a bit more open, but personally I don't think the support would be as good. Still good, but comparing the support to LineageOS just seems unfair to me. I could be wrong about this though, LineageOS just looks like Firefox while AICP looks like Waterfox or something, supported, but not as well supported.
-
1
-
-
2 hours ago, FlyingAntero said:
Apps are using different ways to detect if the phone has been modified. Some apps check root and others bootloader or SafetyNet status. See my post earlier for more information.
Some even resort to exploiting bugs in the system, see https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20 it's quite amazing to see the lengths some apps are willing to go through just to know if you have more access to your phone or not. But yeah, root detection methods are plentiful.
-
1
-
-
3 minutes ago, OKSun said:
The problem is that this lack of guarantee is a big obstacle to the investment in a pro1 - X (which is not the cheapest phone on the market). Imho, fxtec needs to develop a better answer there...
Well, that's sadly part of the deal for not shipping with certified Android like the original Pro1. You don't have a guarantee that things like that work, that you can even use them is more an exception since it's accomplished by slightly shady stuff. I do think that if you do everything right, the chances of being to use your bank app is pretty high. But anybody saying they can guarantee it is lying I think. If that's a dealbreaker, than a device that ships with LineageOS isn't for you I think.
-
1
-
1
-
-
Individual apps can be more perceptive to detecting root, sometimes even exploiting privacy invading bugs in the system. I'm by no means an expert on hiding root (I just don't use apps that complain about that), but have you done everything listed here? https://www.didgeridoohan.com/magisk/MagiskHide For example I didn't know some apps detect other apps that require root.
Otherwise it might be a new detection method and you're only hope is for Magisk to be updated. But considering how the maintainer of the github doesn't want issues opened for MagiskHide problems, I'm assuming it's almost always possible to hide root if it's within the scope of MagiskHide.
-
1
-
1
-
-
5 minutes ago, Slion said:
I think on the blue proto pictures it is still the original Pro1 layout but the layout designs are clearly changed, that can't be a mistake.
I spend like a good minute doing spot the difference on the proto pics and wondering what I was missing 😅
-
2
-
-
5 minutes ago, ToniCipriani said:
I just want FXtec to fix the current one, be it update the current one convert us to an official LineageOS build. And before someone says "flash Lineage yourself", I need the phone to be validated as stock for BYOD purposes.
This does raise a point, what's the bootloader like on this new one? The current one has a locked bootloader that can easily be unlocked. But you can't just lock it with LineageOS I think because it checks if the original ROM is on there or something (not sure). I am guessing that for BYOD policies they check if the bootloader is locked, or if the safetynet thing passes (which checks the bootloader among other things). This isn't possible to pass on LineageOS without rooty shenanigans, which I'm sure would be even worse for BYOD situations. The reason the Pro1 has a locked bootloader is to pass safetynet and have Google Pay among other things.
The only way I can see this phone being valid for BYOD is if it has a locked bootloader, which would be neat for LineageOS. However, that would also fly in the face of the marketing for you having "options". I think you're hoping for something that's impossible, on this new phone and even more impossible on the Pro1.
-
2
-
-
4 minutes ago, SteffenWi said:
Am I missing something here? The tech stats for the Pro1-X are the exact same as for the Pro1. Is this a relaunch? Same CPU, same RAM, same screen, same camera, same (shitty) spot to put a fingerprint sensor at.
2GB more RAM, and (possibly) twice the storage (256GB). And it's blue.
-
So basically the same hardware, with some added storage and RAM. Biggest differentiating factor is the software. This seems like good news for LineageOS support on the original at least, I'm guessing a lot of that overlaps. But this doesn't bode good for "official" Android support, that was already subpar I think, and now that seems to be dropped even further. I do hope firmware and the like will be kept up to date for longer now.
The similar hardware is also good and bad. Good in that repair support is likely to be possible for longer since the hardware is similar. But on the other hand, I do feel like this is possibly going to cannibalize the current pre-orders. Pro1 is still not "generally available", people are still waiting (far past the original delivery date), and the last time a group of people that ordered later were given preference it wasn't a good look either. If these start to ship before general availability, then I'd be pissed if I didn't already have my phone.
Also, I'm not sure what XDA has to do with this aside from branding? It's being posed as the reason for LineageOS, but I don't see that link? And apparently it's currently running 17.1, which is further than the current Pro1? And that early Christmas edition gives me some bad flashbacks.
Fancy look by the way, but I prefer plain black.
-
3
-
-
On 10/24/2020 at 2:32 AM, Linkandzelda said:
Thanks for the info, do you know how I can make a full backup before doing anything?
Short answer, no I don't know. Long answer, I use oandbackup from f-droid to create a backup of all apps, but I never tested it so I don't know if the backup actually works. There should also be a backup function in adb I think, and there's titanium backup, but I haven't really used both of those.
On 10/24/2020 at 2:32 AM, Linkandzelda said:Also did you have to reinstall magisk?
No. Only when I went from unofficial to official, when I used adb to flash it. I'd assume it works the same with gapps by the way.
-
On 10/22/2020 at 5:18 AM, Linkandzelda said:
I'm currently running the first LOS official build with Magisk installed. How can I update to the latest OTA? I am worrying about bricking or something. Thanks
That's almost my setup, and I just use the build in OTA updater. I used one of the first official builds, had magisk installed, and no gapps or microg. I used the OTA to update to a build a couple of weeks later without issues, and have since just updated weekly without issues.
There were some other comments a bit earlier about methods that should have a bit more backups. So if you're worried I'd recommend to check those out. But it's probably fine, and any "brick" from using the OTA should be relatively easy to fix I'm guessing. Hoping some others would chime in though.
-
On Lineage this seems to be build in. Under Settings -> Apps & notifications -> Notifications -> Notification light. Then you can apps you want to control the light for with the plus on the upper right if you enable "Use custom values".
-
2
-
2
-
-
I think I've also had this problem. GPS seems to just decide to not do anything, and doesn't get a lock for sometimes days. But it's very infrequent, so that's extra fun. No idea what it is, but I have LineageOS without any gapps replacement, so I don't think I have any AGPS replacement. That could be an explanation for my problem.
-
I have a question. In settings under Security & Location and then under Trust it warns that the "Vendor" is out of date. What does this mean, and is there something I can do to fix it? Or is everybody's vendor technically "out of date" or something?
Some info that might be relevant: When I got the phone I immediately went to Lineage test builds, and went from test build 12 or so to the September 05 official build.
On 9/11/2020 at 10:39 AM, auvo.salmi said:Already feeling myself an annoying noob to even ask, but I have been using the first official since it was published. The reason I haven't updated is that I have everything working. Everything refers to Magisk stuff mostly. I know that if I sideload the update, I have to flash and configure Magisk manually after that. But does the OTA update also overwrite those parts of the system?
I had the September 05 official build with Magisk flashed and working, and I used OTA to update to the September 14 build, and then the September 21 build. Magisk just kept working, I had zero issues updating.
-
I could definitely be wrong yes, just wanted to share my experience with wireless chargers. In my experience they were also extremely fickle and not consistent at all. Sometimes it would just charge fine, other times I'd return to a hot and nearly empty phone. Again guessing here, but I think it might've been some slight differences in what software was running in the background. This was an LG G3 on a LG charging dock by the way, so even more reason for it to just work.
-
1
-
-
My guess is that the wireless pad just won't supply enough power to charge the phone, but enough to trigger the LED. That was often the case on my previous phone, with the added bonus of still heating it up... They're really not that efficient, and depending on what you plug it into it might just not be enough to offset the power needed to keep the phone on.
-
1
-
-
I'm pretty sure there's only 1 microphone in the Pro1, unlike the N900 which has a microphone at either end it seems?
-
12 hours ago, Craig said:
And although tdm implied magisk can workaround, I do not believe this to be the case any longer.
Really? I thought that was the whole point of magisk, to hide root from the system and make it so that apps that require safetynet just see an unrooted and valid system. Then again, I haven't tried it myself. I don't use any apps that require safetynet.
-
I'd recommend just peeling it off first thing anyway, IMEI isn't really something you should flaunt about. Just stick it in the box or something in case it is needed, but apparently it's not.
-
5
-
-
13 hours ago, Jerrykaisler said:
Even though I destroyed my phone with a hammer, I want a refund for the time and trouble this phone put me through.
That's hilarious.
-
1
-
-
21 hours ago, SchattengestaIt said:
after they informed us that they ramped up production entirely
I don't think they've said that. Last update spoke of having almost 100% of our factory staff back to work. And that they can ramp up, but not to where. No indication that they're at full capacity I think.
LineageOS 18.1 Official Release for Pro1
in Pro1 - Thoughts & questions
Posted
Wow, that looks terrible. Seems like you should be able to add options to it according to this article? Though it mentions a three dots button, which I'm not seeing in your screenshot.
This is like Windows 8 all over again, why make it huge and occupy the whole screen? The small 4 options on the side in LineageOS 16 were great.