Something unexpected happened to me today. The Pro1 haddied in my pocket. It had at least 50% of battery remaining, and everything had performed normally before. But then I just found it powered off, and at first it looked like it won't wake up. I pressed power button several times, no response. Then I tried pressing vol up/down (don't remembr which one) and power button simultaneously. Then it finally woke up and gave me some "no command" text with android logo robot having it's stomach opened. It got stuck there, but by pressing only power button for 5s or so, it finally booted to OS. Now it works like charm again, no idea what that was.
Sounds like you booted into recovery or something. I'm guessing it powered off randomly, and to boot it you need to hold the power button for some time which I'm also guessing you didn't do or didn't do long enough.
I've been watching for over 10 years as people try to load various operating systems on different mobile devices. A common theme has become the table that lists which bits of the device are working, partially working, or not working.
I understand this is mostly because hardware components have closed-source drivers, right? Why is this such a large barrier? The lack of documentation on how to interface the binary blob? (assuming a similar kernel)
Yes, the largest (and really the only) problem is that there is no documentation available so people need to try to reverse-engineer the workings of the ABI which is really painful and slow.
This is something which I am always wondering; why so much obscurance since I'd imagine it is in the intrests of chip manufacturers to get as amy users as possible for their products. Opening up the specs and interfaces would increase chances for people to buy the gear, right?
On Sailfish all is working great with the stock jolla app as well as with Adams Advanced Camera.
When you say all is working great in Sailfish, are you including the half-press to focus? This does not seem to work on my Pro1 (worked fine in Android so I don't believe it's a hardware problem).
I asked around on discord how to reliably test the 1st stage with clear result to rule out HW fault.
@Noir suggested to install Open Camera and
"open options and select that lock (screenshot attached),
autofocus is disabled then.
1st stage keypress is then perfectly useable to focus"
(...)
Thank you for asking around. Open Camera is installed on my unit, and I locked the autofocus with the lock icon. When I press the shutter button gently nothings happens. If I long-press the button, the snapdragon app opens.
Sorry to read.
Thats a dilemma...
I imagine you are not eager to send it in for repair since it is still an otherwise working Proš.
Chen has guided at least two users of whom i know into fixing issues by themselves successfully.
The Maintenance Manual is available since those live community repairs.
The Maintenance Manual is available since those live community repairs.
You already have contacted F(x) support?
I already contacted support (about this and other things) and, so far, it has always been a positive experience. Answers take some time, but the response is qualified and the team appreciates feedback.
The autofocus itself works when tipping the screen and the two stage button is not important for me. It's a nice feature I would miss.
Most important is e-mailing, second telephony.
I'd appreciate it, if one could remap the button to other camera apps, without installing keyremapping software first. Maybe that's possible but I didn't figure it out yet.
@AardDevil, ah yes, didn't think of that, and I actually had an impression that I paid in June, but I checked my history and I paid August 6th. But anyways I'll refrain from making mopey posts from now on and just wait 'til I see the phone in my hands (PS: I'm feeling it cannot be that long anymore)
(PS: I'm feeling it cannot be that long anymore)