brunoais
Members-
Content Count
292 -
Joined
-
Last visited
-
Days Won
11
Everything posted by brunoais
-
Pro1/SailfishOS stucks at the security code input screen.
brunoais replied to Astaoth's topic in Pro1 - Thoughts & questions
Can you boot your phone into EDL mode? There are some guides here in these forums on how to do that. -
Start with a backup of whatever you have now (in EDL mode, if needed). Try booting your phone into EDL mode then search these forums for more information. I don't know what works and what doesn't. If you can't solve it, make a new topic with your problem and what you tried.
-
Looks like something really screwed up your partitions... This is now beyond what I can think at the moment. I'm currently out of ideas.
-
When was it released? Was it nearby 2020/1? Was it produced by a company with deep pockets? Those two are VERY important to take into account. You need absurdly deep pockets to handle such kind of market offer.
-
Mine has the marks too. This is an issue with the display manufacturer which seem to have a 70+% failure rate at the screen edges. However, they scam buyers by cherry picking the displays for test units, so none of the test units have these visible issues. F(x)tec is scammed and they are incapable and don't have enough money to fight back.
-
I agree. There's no noticeable errors or warnings in the logs. @trahe I found this almost by chance: Does it help you? It shows that restoring some of the partitions worked to unbrick his phone.
-
I don't know if UBInstaller deletes the persistent partition. Look at this guide: Try to do a backup of the partitions and let us know the outcome of it. If you are willing to, show us the full output from the tools used to backup.
-
Did you delete all partitions that came with the phone? The persistent partition is one of the most important ones to keep a copy of.
-
If you can login to recovery, then the phone is not bricked. You can still do things with it. Did you backup the partitions?
-
Just to double-check: Is secure boot confirmed turned off?
-
Pro¹ X – state of production and delivery
brunoais replied to Rob. S.'s topic in Pro1 - Thoughts & questions
That's unexpected. I know someone who has small hands and I borrowed my phone quite some months ago to try typing and she types just fine. She can't overlap the fingers but she can reach the whole keyboard. Can it be that you can have a more pleasant typing experience just by holding it differently? When I hold it, I place my index fingers on the exposed hinge, the phone rests between my index and middle fingers' bone in the palm of my hand. IIRC, that's also how she held it. How are you holding it? -
Pro¹ X – state of production and delivery
brunoais replied to Rob. S.'s topic in Pro1 - Thoughts & questions
So I'm a lucky within the ⅓ they delivered? Also, how unlucky can a company get with all of what happened wow... Pandemic out of nowhere (cannot travel to China) Stolen money for the SoC (which is about half the price of the phone) Need to buy new SoC but completely screwed about its functionalities (China: The land of smokes and mirrors) and Chen couldn't be there to experience himself because air-traveling was restricted Then delivery company starts delivering some phones and selling some of the stock itself. -> Change of company Then the logistics of -
I got 2 friends that asked me, when looking at my phone, how they can get one too. Looking at the website, they appear as "out of stock". Looking at some people here, they are in dire state because they haven't received theirs. Will there ever be more Pro¹-x? Maybe Casey can answer that...
-
Pro¹ X – state of production and delivery
brunoais replied to Rob. S.'s topic in Pro1 - Thoughts & questions
Why not f-droid? You can just use Fenec (a barely modified firefox repackage), for example. For e-mail I use k-9 mail. -
When will stock be available, New Model? Other new tech
brunoais replied to DC's topic in Pro1 - Thoughts & questions
This was more in "behind the scenes" and picking up the data, including the lawsuit in China. If you buy, order and pay for something, you'd never expect the order to not be delivered, don't you think? And even if not fulfilled, you wouldn't expect to not get the money back, don't you think? They knew the SoC was EOL, that's why they ordered the batch with enough time in advance to make sure the stock existed. They are low on cash but they are not broke at this moment. No longer allowed by EU law. Pro¹-X was supposed to be fully delivered by May 2021. 3 months b -
When will stock be available, New Model? Other new tech
brunoais replied to DC's topic in Pro1 - Thoughts & questions
You are missing the part that they had to make a new phone when they didn't even want to. You also are missing the part that each phone is essentially costing twice because f(x)tec paid for SoCs which they never got. They are still waiting for litigation in China courts. -
Pro¹ X – state of production and delivery
brunoais replied to Rob. S.'s topic in Pro1 - Thoughts & questions
Yes. I agree. However, that's what they are reporting to f(x)tec. Who knows what they are REALLY doing. f(x)tec doesn't and they won't share that info with f(x)tec. -
Try reading the server code of scrcpy. It has everything you need to capture. Then you just need to have a receiver and something to convert the signal to HDMI. I have no idea how. I do love scrcpy, though. I use it quite regularly.
-
I'm still waiting for my astro slide. I was just lucky to have one of the first Pro¹-X shipped. Otherwise, I wouldn't have any android usable phone for me. I can't type anything (even swiping) on a flat surface without any texture on where the buttons are at any meaningful speed. I've tested with my Pro¹-X my typing speeds with the on screen keyboard is 30cpm vs 160cpm on keyboard vs 260cpm on my laptop. This is all a terrible timing problem of a triple blow. f(x)tec is just caught in the middle and Planet Computers too.
-
Pro¹ X – state of production and delivery
brunoais replied to Rob. S.'s topic in Pro1 - Thoughts & questions
https://www.fxtec.com/#Linxdot (hopefully) https://www.deckhd.com/ -
Is that your order? They marked it as "Failed"?
-
I'll do that some time shortly. Too late. That happened to me last week. Same with the Pro¹-X. I'm not sure if the command is the same but I activated it on the same day I installed the OS. Thanks anyway 👍 Interesting... I wonder if it's fixed on version 2.1.5. I didn't encounter that when it discharged fully last week.
-
I do. As a phone it works fine for me. I've tried for 1 week some months ago and it did it's work as I'd expect from a phone in which I do calls and SMS. Even the tinny speaker doesn't "broadcast" the call to everyone around you, unlike many other smartphones. I'm in EU. Maybe that's why it just works for me without tweaks. I suppose so. If it's not open-source, I only run sandboxed with limited and tight control on what permissions I provide (inside work profile). They would be useless there. Yeah. I check that (and just re-checked that). The biggest spenders are repor
-
Many hours of screen time, yes. Even then, I'll take the suggestion and see what I can find. I only have open-source apps on my main profile, though. The proprietary apps are in the work profile and they are quite closed down and limited. Got any open-source alternatives? I only take "free" if it's "open-source" (AKA FOSS) 😆. In seriousness, I avoid those or, otherwise, I install on the work profile and they are closed after some minutes of not in use. None of my apps on the personal profile call my attention. Now I notice, I didn't mention that I charge my Pro¹-
-
I have this problem sometimes but I think it's caused by ACC. It appears like there's some bugs in the custom android kernel which doesn't like when some of the settings inside /sys are used. I'm still probing because this only happens to me many hours after I start charging. However, if you have root permissions, this script works well for me: echo 1 > /sys/class/power_supply/battery/input_current_limited echo 0 > /sys/class/power_supply/battery/input_suspend echo 2 > /sys/class/power_supply/battery/charge_control_limit I appear to only need it if I have the phone connect