Here’s a couple I tried to get the same size on the camera screen. I seemed to have trouble orienting things from the side camera but I think they are fairly close. Both downsized and cropped a little bit but the originals were essentially showing the same width on screen. Note these are being taken on a curved screen monitor.
Kospet:
I’ve found information in that past that cameras for androids have sometimes considerable variance in quality between batches even on the same phone. Maybe I just got a marginal one on the Kospet Prime. In the pictures above I don’t see as much difference but the background ‘noise’ on the Kospet in an area where there is less light looks a lot more ‘noisy’. You don’t see that from taking pictures of a screen as much but it shows up a lot in regular pictures. It also seems to color from the Rollme is a bit more vivid in most pictures.
@none, apparently I need the ‘Pro’ version to create a report but I’ll type in the relevant camera info here that I can see from that Device Info HW app for the Rollme (getting a bit spacey I assume you wanted this for the Kospet Prime? ) I’ll get it for the Prime in a minute:
Camera 0 model: bf2206mipiraw
Camera 1 model: bf2206mipiraw
Camera 0 back: resolution 8.0 MP
focal length 3.5mm
sensor size 4.46 x 3.34
pixel size -1.36 um
view angle 65 degrees
Camera 1: same specs as camera 0
Kospet Prime:
Camera 0
vendor: GalaxyCore
model: gc5025 mipiraw
resolution: 5.0 MP
camera 1 :
vendor: GalaxyCore
model: gc0339 mipiraw
resolution 0.3 MP
Software seems identical to the Rollme except the resolutions are 8.0M and 2.1 MP
The ‘Upload’ function is free, only the local ‘create report’ needs the pro version, but our devices are probably identical, so you can’t upload the same information twice.
For the camera sensor, i guess you either got a really good BF2206 or a rather not so good GC5025, as (just compared to) the pixel difference is noticeable on the test pictures.
I looked at my Kospet Prime build.prop but I don’t see that info in there. Rollme isn’t rooted yet so I don’t think I can get to the build.prop on it right now.
The ‘false’ information like the 8MP resolution or the (almost) never matching battery capacity is quoted from the Android system, they are just some generic hard-coded values in the system framework apk.
Device Info HW pulls the real information (the part that is used for the reports) directly from the kernel, where the loaded drivers need to match the actual hardware.
Edit:
Interesting, someone uploaded information for the Rogbid Brave.
Here is the original Rollme S08 for comparison.
As I have noticed many times over the years…
Even though built in the same factory the components seem to vary wildly - even in the same model.
It seems to be whatever is available or sometimes just about cheaper bulk buying at the factory.
It used to be very common in oled screens.
Different drivers needed as well so firmware versions would vary too.
This is problematic because customers flash wrong screen type firmware and end up with black screen or no touch or inverted display.
Appended with NHH for example to indicate screen type…
@pablo11, Any idea when we might get the firmware for the Rollme S08? If it’s going to be awhile I will try to extract it from mine but it’s a fairly long and complex process to do so (for me anyway ). If you think it might be available in the next couple days I’ll wait otherwise I will try starting the process. If I can just get the boot and recovery image and scatter file I’ll root it and make a TWRP version for it (if the one for the Kospet Prime doesn’t work).
I’ll post the boot and recovery and scatter in a couple of hours.
It’ll be a few days before our agreement is settled though.
The images are basically the same as the LEM12 and Prime but I will post the real ones regardless.
I’m just waiting for them to come over the wire from Shenzhen. Won’t be long.
Hi pablo11, No problem at all - it was late here last night when I saw your previous post and I was off to sleep until now. Thanks so much for sharing these! Cheers
Rooted with Magisk and TWRP installed and working fine. Had a hickup or two along the way as I had tried the Hovatek program for modding the stock recovery into a TWRP recovery but that just boot looped. So I caught it during a reboot with the SP flash tool and put the stock boot back on (was flashed with modded recovery to both boot and recovery slots). Then I flashed the TWRP recovery for the Kospet Prime version and did an adb reboot recovery and then flashed Magisk.zip. All was good after that. Did a successful TWRP backup.
Thanks again for making that possible!
I assume you wanted this for the Kospet Prime? ) I’ll get it for the Prime in a minute:
). If you think it might be available in the next couple days I’ll wait otherwise I will try starting the process. If I can just get the boot and recovery image and scatter file I’ll root it and make a TWRP version for it (if the one for the Kospet Prime doesn’t work).