EskeRahn

I highly doubt that we will get anything that are not community driven for our beloved Pro1s I think they will be focussing on the Pro1X (and any possible future successors)

Ah yes, how things could have been different had they not been swindled...

Please do not put too much weight on my simple tests. It MIGHT be that not all bands work equally well, so if some depends on a frequency where it does not work well, their results would clearly be worse. We would need some more scientific approach to this with some suitable box that can act as an access point, and 'browse' through all supported channels of 2.4 and 5GHz, and then we should measure the time a band change takes, as well as the speed in each band. And all this at different distances... And with the device in different angles. Without a systematic approach we could easily be

I can only say: Patience. I'm in the first dozen from IGG in October 2020, and still no shipping info from FedEx.... Expansys/FedEx seem to handle the parcels from FxTec within each batch by country (in some unknown order). So depending on your country, it could be soon or weeks for a device in batch 2.

Nope, have not seen that. A guess, could Nova be shot down by something? Try another alternative, to see if it is Nova-specific. (I'm currently trying "Action Launcher")

Are you sure it is not IMX582? https://www.techarp.com/photo-video/sony-imx586-imx582-comparison Both should be able to do 4K@30fps though - the 586 even more. Could it be the rest of the device that is not fast enough to do the 4K@30?

I took the liberty to edit the original post, as a new guide can be found here

Thanks. But a bit strange you also see oddities - though minor. Maybe this update is one where people should be certain to make a backup first! (Obviously always a good idea, but extra so this time....=

meant the boot image, and sorry just three lines of output

lineage-19.1-20220815-nightly-pro1-signed.zip Strange things happens! I was unable to boot into recovery mode after flashing the recovery image. Flashed it again and retried a few times. Flashed recovery back to 0807, And it requested me to factory reset the userdata(!) to be allowed to boot the recovery???? Retried flash and boot to recovery a few time, gave up and reset. Then flashed boot image 0815 and all went as usual through the flashing. The wizard is new and improved (compared to last I reset) - BUT after the fingerprint it jumped back and asked me to confirm my

Thanks for the step-by-step guide. You might want to add the step on saving the "persist" image before flashing, as not doing so should prevent turning back to stock android (and most likely LineageOS also) without lost functionality. In Windows 11 it has been allowed (again) to install an unsigned driver, without test-mode, some months back. (About a year ago we could not)

Cosmo might have similar problems getting their devices from China to the rest of the world. This is certainly not a problem limited to FxTec and Pro1X for the time being. I know from dialogue with FxTec that the Pro1X I perked for is in Batch 1, and is long delivered from FxTec and they can see that it has been 'processed', but yet it hangs in the shipping so I have not even got a shipping info mail yet.... I guess Expansys/Fxtec awaits enough parcel for Denmark to actually send it? 🤬

If they got it for the Pro1. Things have changed slightly for the Pro1X. The fingerprint-reader is new, and I believe they said the antennas are changed too. Obviously these could be backwards compatible.

I guess it is a matter of what aspects you will discus. If they are general UT questions they will easily be lost in here, only seen by Pro1X/Pro1 users. if they are specific to the Pro1X/Pro1, this could be a fine place.

On the speakers issues several has mention I frankly still doubts it is hardware connections that is the issue. It could not explain the popping sounds, and it certainly should not just go away increasing the volume. Though you specimen could of course have another speaker issue related to the contacts. If/when you have the bug again, try increasing and decreasing the volume(!). At mine (though not a retail unit) the sound vanished completely below about 50%, and was not affected at 100% In between it was partially chopped and with popping sounds. Later it worked normally also at low volu

AFAIK the standard TWRP does not support the Pro1 - have a look in this thread or search the forum for "twrp" and see what can be found.

Note that mine is not a retail unit, so could have been improved since 🙂

Frankly I think we have a better chance in patching in the keys binary in a working image, than trying to mount and fiddle inside a not functioning image with the right keys.

If you run the Camera2 app, it reports for both the Pro1 and Pro1X that it ought to be able to do raw. The biggest difference reported seems to be on video where the Pro1 apart from the QFHD (or 3840x2160) as the highest, it also reports it can do 4000x3000 - does not sound very likely though... So maybe the information reported through the Camera 2 API is simply incorrect.... And that can obviously confuse an app trying to use it.

What an odd bug. Reminds me of a bug between A Huawei Band 7 and an ancient Iphone 6, where I had to in BOTH ends say that it shall forget the other end.

Sounds likely when modifying inside the volume. Copying the whole image seems to work. Just tried with 108GB userdata, via recovery and adb, and it worked just fine. Updated this.

Split works just fine here, both portrait and landscape. With the android limitation of only offering one 50:50 split in landscape, and 30:70, 50:50, 70:30 in portrait

Interesting. I doubt that the sensors are calibrated, to some standard source, so not surprised the numbers are not correct. The two devices could also have a difference in how wide they are getting light . The main purpose of the sensor is to allow for adaptive brightness. But sure would be nice if they (or we?) could calibrate them correctly.

We also have post talking on the issue over here (though no known fix yet) Oddly it does not seems to be always, I do not think it is a contact-issue though - but could be wrong.

(added this, on doing it through the Recovery rather than a running android, that might not go well with all partitions, especially restore)