fxtec-preorder-47xx
-
Content Count
51 -
Joined
-
Last visited
-
Days Won
1
Posts posted by fxtec-preorder-47xx
-
-
Hallo F(x)tec Pro1 community,
it has been awhile since I last posted, and my Pro1 was lying somewhere in a box. Now I tried it again, but the issue remains. See below:
Well, I dropped the fully working phone into water. At the end, display is dark, but everything else is still working (as far as I can tell).
The phone is charging, switching on, LED is doing its LED thing, keyboard is backlit, phone is connecting, I can connect via computer and did download all my stuff. When I remember correctly, also wireless connection worked, but it's difficult to tell after all this time... but anyway. Display was dark. (Touch... hmm, I can't tell.)What I tried:
- I switched the display/digitizer itself (aliexpress). I did that before (when screen once scattered, and back then: repair worked), but this time: still dark. So I disassembled the phone a bit more, and checked on the LCD connector correctly set on the main PCB etc...
What I did not try:
- I did not replace the small PCB inside the display half. This is merely some interface connecting the display to the cable that goes to the main PCB, I don't even know if something is on there, that can be hurt by water making the display fail. (Yes, the earpiece-speaker and front camera is also on there, but that's not the issue right now.)
- I did not swap out the flat ribbon cable, that goes from display-side PCB to main PCB. Sure, could have happened that I bend this to hard while replacing screen, but there's no visible issue.
What can it be?
- Perhaps the display side and the cable is fine. That would mean, the problem is on the main PCB. As the phone generally seems to work, perhaps the GPU or something graphics related fried due to water damage? 🤷♂️
Is that likely? Has anyone here experienced this? What do you recommend? My possibilities are limited... I may not be able to reliably check if all the lanes on the flat ribbon cable work, as they are damn small 🔬 Does anyone perhaps have a destroyed Pro1 where I can scavenge some of those parts/cables from?
I'll appreciate you comments... As for now, have a good time! 👋
-
1
-
4 minutes ago, Rob. S. said:
Then again, history is just repeating itself here.
If you put it like that, one may hope things will work out at the end.
Anyway.... apologies to everyone for my rude posting here. 😙
-
2
-
-
Ok, you (@claude0001 and @VaZso) are right. I used the forum in a wrong way. I am really glad you corrected that. So, now that everything's nice here again, we should not bother the fxtec.com website's outdated information.
Thanks for your time, everyone.
-
12 minutes ago, VaZso said:
I don't know why you are addressing this to me, I am also a simple customer here...
It's OBVIOUSLY not meant for you.
-
On 3/14/2022 at 12:34 PM, VaZso said:
March update has been released here:
"Whilst we do not expect this to significantly impact our manufacturing and shipping timeline, there may be a one-week delay before we can start shipping your Pro1-X’s."
Don't you think you should finally update or remove the statement in F(x)tec Shop saying: "SHIPPING IN FEBRUARY 2022".
I recommended the Phone to friends, now they laugh at me, and I'm standing here like an idiot. How could I recommend trusting a company that is not even able to keep basic stuff straight. Covid related delays are nice, but update your website or just delete it. Nothing on twitter either. I don't know what's wrong with you guys. This is so embarrassing.
-
On 1/12/2021 at 11:30 PM, Slion said:
Dude that's some serious wear on that Pro1 🤣 good luck with the sell.
Naaa... mine looks even worse. And I already have my third screen. I mean, you are outside, slightly miss your jeans pocket and boom! 50/50 chance it falls display down onto the concrete.
Fortunatly the plastic frame around the screen still holds (I only swapped the touch+screen itself), but it already has some impact traces. And the keyboard slide mechanics also hold, though I often use it to clip the phone ontop of my notebook screen. Great quality!!1 Anyway... I don't know how you guys canNOT trash your phone that you use daily. Plush handbag? Rubber floors? 😉
Normally I save money by buying used stuff, it's usually 'new' to me 😄 If I buy new, then the stuff is in used condition the moment I unpacked it.
Edit: The edge of the keyboard part is quite sturdy... but you have to focus, when you open your bottle.
-
2
-
-
But Kelloggs on the left are more crisp than their cheap knockoffs on the right, no surprise.
-
5
-
-
Fair enough...
-
@tdmWhat do you think about the differing values of android.lens.info.focusDistanceCalibration? Do you think you could add this to the LOS code? Or try if it improves focus?
-
i got something! I got some system info using this App:
https://f-droid.org/en/packages/com.oF2pks.kalturadeviceinfos/I did this on freshly flashed Stock ROM, and also on freshly flashed LOS official.
The resulting JSON files were mostly identical, but with a perhaps problemrelated difference:
LOS-official:
"#CAMERA2API=": { "0=back<LEVEL3>4048x3040([100, 800])": { [...] "android.lens.info.focusDistanceCalibration": "1",
Pro1-Stock:
"#CAMERA2API=": { "0=back<LEVEL3>4048x3040([100, 800])": { [...] "android.lens.info.focusDistanceCalibration": "2",
See? Difference? 1 vs 2? Also, the similar section for the front camera has the same value on both systems. (Front cam working for me fine on either ROM.)
Can you guys run this app and export that json on your LOS Pro1, please?So, I think THIS IS IT! How do we fix this?
(I HOPE the value did not change as I might have used the cam app on the one rom before exporting the json, but I think this is a fixed value... Well this sort of testing woud be a lot easier if I had TWO pro1...)
According to docs "2" stands for "CALIBRATED" and "1" for "APPROXIMATE".
-
I just tried UbuntuTouch, that does not have that problem. Focus is fine, but slow, or sometimes off, seems stuck, due to the app perhaps, or whatever. (I find the touch gestures hard to use, need serveral tries to get stuff right, not feeling good... but thats off topic.)
I just say: Focus is generally working on UbuntuTouch but is kinda unsteady.
-
1
-
-
Tried again, first doing some
fastboot format system fastboot format userdata ...And then it flashed and started up.
Nice.
Anyway, camera focus is kinda fine here. (Camera app not sooo good it appears.)
-
I mean, if there was an 'issue' at LOSes git, saying 'Camera bug on Pro1: unusable blurry' then I would probably settle, trusting the problem will be taken care of.
But all I get is 'there is no problem', 'its working fine for me, but i am just taking closeup pictures and am blind and never visit places where the walls are more than 5 ft away'...
Hello @chen , I want a refund!!!!!! -
59 minutes ago, claude0001 said:
Did you try switching the scene mode to something else than "Auto" as suggested?
Yes, I tried everything.
Weird enough, when reverting to Stock ROM, and then using the very same OpenCamera, API2, ... it works on auto. (Like in any other app, it just works.)
Still, on OpenCamera app's infinity or manual>infinity setting it is blurred, but thats not a problem, as you also noticed - I just pull manual back to 100m or so, and it is fine.Problem is that with my phone on LOS, there is no way to get focus right, even manually like "really close but not quite infinity." Always blurry.
As you (and others) do NOT have this exact problem, I wonder if there are different cameras in the early Pro1 models. I have preorder <5000. Perhaps there was something they managed to bugfix/workaround in their stock ROM but FAILED to commit to LOS codebase. (SHAME SHAME SHAME!)
I have no other explanation.
How can I get HW info on the camera built into my phone? Anyone?
I really think, I MUST have early-model hardware. I flashed SailfishOS on my Pro1 also, and there was NO CAMERA (black screeen in camera app) at all. (According to others, it should have been there and working normally.) So WTF is up with my hardware? Can someone recommend a tool that reads the camera specs from my system??? lsusb/lspci and alike seem not to be an option. I am about to smash this thing into the wall!-
1
-
-
Just to update this:
@mcdinner made an extra build for me, with both imgs. That flashed fine and worked nicely.
But still, main camera does not focus!!
Thanks to everybody anyway, I'll go buy an iPhone...
-
1
-
-
On 6/20/2020 at 5:55 PM, order#10248 said:
In TWRP go to Wipe -- Format Data (Warning: All your data will lost.) --- type yes, and click blue tick
It complains with stuff like:
Failed to mount '/data' (Invalid argument) Failed to mount '/vendor' (Invalid argument)When I continue with install, it aborts with repeating the above errors and
Updater process ended with ERROR: 7 Error installing zip file '/external_sd/ubports-fxtec-pro1-v0.5.zip'Then I say "reboot" and get stuck at Pro1 logo.
So, all this doesn't work.
Edit: I did all this after I successfully reverted to stock ROM, if that is a problem, using:
-
38 minutes ago, claude0001 said:
In the worst case, you can even disable auto-focus in OpenCamera and adjust the focal length manually. I agree that one would expect this not to be necessary in 2020.
I dont know how everyone can experience this different from me or not at all. Perhaps everyone has eyes issues.
I DO try this with OpenCamera, Camera API2 and so on, but it just does not work.
If I go to manual focus, or select infinity focus, either way, everything thats not like 50cm in front of me is blurry.
Just flashed back again to fxtec stock ROM: everything is SHARP.
So using the tools you mentioned to focus manually do not help AT ALL, at least in my case.
You mentioned "driver". What is this driver called? Who maintains it? What do you know bout it? 🙂
-
2 hours ago, _DW_ said:
driver issue been discussed in the other thread
Which thread? Never read about anything 'driver' concerning the camera?! Can u point me to it?
-
So, I tried SailfishOS....
NO CAMERA, both cameras BLACK!
Was that supposed to happen?And another issue that might be related to a display repair (swapped to Elephone U)... the round edges don't register touch. So with Sailfish I cannot swipe from the very edge, which renders the whole thing even more useless. (Thankfully landscape mode works, where the edges are behaving normally.)
This is all so frustrating... Lineage4MicroG doesn't work. Camera focus on LineageOS doesn't work. Camera on SailfishOS doesn't work at all... I'm about to go back to stock.
-
Ok, thanks. I tried, see PM. Didn't work out (though it flashed).
Thanks anyway. -
I just tried LineageOS nightly 17.1 ... still no proper focus. This is f##ked up. I cannot even scan my invoices with LOS like that. With stock, everything fine. I don't get it why no one gives a s##t.
How can anyone use the Pro1 with LineageOS like that?! Can someone explain this to me?
-
11 minutes ago, mcdinner said:
If you want I can give you my boot.img and you can test if it works for you installing the official builds.
Ok, if this does even make sense. (I think I could choose 'ignore signature' or something...)
Lets try!If you can upload this, I'll try.
If it does not work, I'll be going back to stock. (Mainly because this freaks me out:
)
-
5 minutes ago, mcdinner said:
As far as I understand you would need my builds i you don't want to lose any data.
I switched to building everything by my own with several packages included. If you have enough space left its easy to do, even if you have no idea what you are doing (look at me as proof)
Do the pre-built lineage4microg images still not work?Ok..., thanks anyway.
I won't build, I only got a i7-3667U with 8GB here, and I don't want to have that busy for some days and swapping? 🙂 or so... or even multiple tries...
With the probuilt images its still the same, just tried...
Anyway, perhaps someday the Lineage4MicroG-guys will provide a fitting boot img... or TWRP will... or whoever...Until then, I'm with plain LOS.
-
1 minute ago, mcdinner said:
Sure, I can upload it but it is signed with my personal keys, so that could be a problem.
So then we would need your LIneage4Microg-build as well?
Those keys are just fitting those two? Nothing device specific, isnt it?
Looking for a replacement Screen Flex cable or a broken phone to salvage.
in Support
Posted · Edited by fxtec-preorder-47xx
Hi there. I guess, me too. I have 3 replacement screens, but all of them stay black. While phone boots up and touch works. So I guess its perhaps the flex cable?
Edit: I tried the following: I connected the "Camera" part of the flex cable to connect the LCD, and teh screen is at least flickering now on startup. But not working. So I guess, camera part is broken too, but at least it somehow hints that the cable is the problem.
Can anyone tell me what those connectors/sockets/plugs are called, so I could but that part somewhere and rig some fat cable at least to try it out?