Leaderboard

As far as the GSM protocols, etc., are concerned - I may be wrong, but I believe that this area is nowadays covered by the phone chip rather than the phone firmware. The chip isn't specific for Pro1x. In other words, it doesn't seem to be likely that the issue with radio communication observed by some Pro1x users should be related to missing part of a GSM communication protocol. Yes, it may be related to a particular configuration for the device which influences the behaviour of the on-chip implementation, or it may be related to some hardware issues (antenna), or possibly other factors, but i

Finally got the USB-C port repaired on my Pro1 and it's now up and running on Lineage OS 20.0. I'm loving it so far, that notification LED settings thing is an absolute dream, the text and icon sizing is lovely, the darker look is far more to my taste, I can also be heard on phone calls again... Looks like the Pro1 is replacing my Pro1X as daily driver.

As @MonCon suggests, try another headset before going for sending for repair. Or an extension cord or the like. At some point (not Pro1/Pro1X) I had a headset with similar issues, where a simple L-shaped extension plug fixed it. The problem was that the plug simply could not go deep enough, it lacked a fraction of a millimetre, but worked fine in many other places.

We would be happy to take your unit for repair. We have new PCB's for the headphone jack module and. would believe this can fix the problem. Please send us an email to [email protected] and quote this forum. Thanks

Is it OK to vent a bit? I'm following the discussion on IGG and as I'm one of those who ordered the original Pro1 via the website, I can't comment there, but some takes on that forum are borderline stupid. For one, most people there seem to forget that there are substantial outstanding Pro1 orders which still need to be fullfilled and which for the most part haven't been part of crowdfunding. If anything, these people (including myself) would have a right to sue anyone, not the IGG gang (crowdfunding = risk) In other news, fxtec doesn't seem to be going out of business for now, sinc

I can't replicate this problem at my end, and all I could suggest as a start is trying a few different sets of headphones or earphones to see if you get different results, and also to check if you consistently get the little headphone symbol in the status bar when you plug in.

Hiya folks As the title says, I have a spare USB-C module up for grabs. The only problem is that it has a faulty microphone. I had the USB-C port repaired (so that part is lovely and new) and when it came back, I put it into my phone and nobody could hear me when I made calls, nor could I record my voice. So if someone wants it, you can have it for the cost of postage. Please DM me if you're interested. Thanks Andy *Edit - The part has now been claimed.*

(lineage-20.0-20230619-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-202230408_100653)

lineage-20.0-20230619-nightly-pro1-signed.zip on May 5 security patch installed smoothly using OTA

For other people with this problem, if I play the audio on my speakers and *then* plug in the headphones, it seems to work most of the time.

That's an interesting theory. There was a previous theory discussed that the phone isn't able to handle lower frequency bands very well, but it could be that lower frequency bands somehow kick off more band switching. Be nice if there was software that could show you what bands are available to your phone at the moment and allow you to select one (regardless of signal strength) and lock it in as the one for your phone to use. I think that would create better control for testing. I know that my phone, which works, stays locked onto the same high frequency band even though others are availabl

Glad to hear that it works for you. But I would just love if we at the least could get to the point where we knew WHY it worked / didn't work! For all we know it might be one or more bad batches OR it could be special environments that it can not handle correctly. If we at the least knew the reason we could guide people better than a "sad to hear, hope a firmware fix will help". That is the meagre reply we can 'offer' now. My personal HUNCH (and it is just a hunch) is that it is some particular circumstances where it attempts to switch band and fails. And these circumstances m

I'm guessing they subcontract much of the Android port like they do the manufacturing, possibly to the same company. As long as money flows I guess you can expect Android updates and new devices coming out of the factory. When the money stops flowing everything runs dry... Hardware and software.

Sort of. ... It is an internally completely new product and not a minor upgrade as planned an advertised. Hence A (also) fell. But SURE they ought to have changed their communication material accordingly IMHO. We can agree that for some, indeed key functionality is not working. On the other hand for others it works fine. We have no idea of neither why it works when it does, nor why when it does not. Not even an idea on the size of the two fractions. IF we could say that it only worked under very special condition THEN I would agree on the claim - but again we do not know. I grew u

Allow me to suggest a compromise version of that statements. It is a really really bad for the affected people that it doesn't work for them.... But the big elephant in the room here is that though we have reports from various parts of the world either way we have no idea on fractions affected.I bet it is at the least 10%, but might well be as bad as 90%. We do not even know if the issue is on the specimen or the models handling of the circumstances. That is, we have no Idea if you and I swapped devices if mine would work in your location with your sim, or yours would work here

Strictly we do not know if there are any development/bugfixing going on. But a guess is that there is none, and for the same reason: Money. But as so often before they are not good at communication what is going on. But I would not be surprised if they focus the little funding they got on getting the already produced Pro1X delivered to us. I HOPE that the also have a little funding going to handle the most severe bugs - but we do not know. In more general term, I would just love if phone manufacturers had some model where they after a while went to have support and sof

Funny-- mine isn't. It's my daily driver. Neither are the ones two friends of mine have and are using. I'm curious if that's what you told whoever you sold your Pro1x to. 😉 This phone clearly works for some people. Also, clearly, it doesn't work for some. My two friends never go to this forum nor do they go to the Discord server or the TG channels. How many more are out there? We honestly don't know. It is not a good thing that it doesn't work for some people no matter what the numbers, but that doesn't warrant calling the Pro1x dead. So, I guess we will agree to

@claude0001& @steff The DO have other products than the phones, and they have said that they er using some of the revenue from that....

Exactly. Some while back they told us that they use part of the revenue for other products to have those sent they could, and that that was why they went out 'drip-wise', as they were able to gather the needed funding. Sad story indeed, but the only really alternative I see is that they give up and go bust, and those of us still waiting do not get any phones at all, and they stay and rot somewhere - or is bought from the remains and go out on a flash sale somewhere, with no warranty or support, and the severe bugs affecting some never fixed. (And no I have no idea if the "some" is 10% or

I think there are two really good things here. 1) They have gotten the devices moved out of Expansys' hands successfully. 2) They are finally not trying to make timeline guesses when in fact they don't know. They are just being straight and telling us they don't know, but giving us the update anyway.

On latest patch, still camera issues driving me up the wall.

Has it been 3 years already? I lost track. The whole thing turned into a farse a while ago 🤣 Still have not bothered asking for my money back. Maybe I should though and CC my lawyer too ⚖️

Like they did already in May, they fill their update with information on an alternative OS that is entirely community-developed (besides all this information on Droidian being readily available on this forum anyway). What about the work the community cannot do? What about stock Android? Will we ever get that update towards which we have been "sprinting" for the better part of a year now? Any news on firmware fixes related to LTE connectivity? Battery depletion bug? Anything at all? I wonder if the prawn-X might be the first device to be EoL'd before even all preorders have shipped ..