Related
Can any devoloper make a vulkan API zip which can be flash on our device Redmi 2 prime I have seenRoms gives option in Int.d to render GPU by enabling it open GL es get updated to 3.1 which actually is 3.0 supported on our device App like GL tools also help that but Nothing I found on something which can help to install vulkan API so please if anyone can do this for us it will be amazing
All right let's get some things straight.
API is the abbreviation for "Application Programming Interface", which holds abstraction of using a library. If you're familiar with programming languages, you can think of an API as the header files of C, or the interface of Java. They hide the internal details of how a specific task is performed. Rather, they focus on the programmer use of it.
I don't expect you to by the above paragraph, but you need to understand how close is an API bound to the specific architechture, underlaying software and all that low level things.
Now come to flashing a zip. What the TWRP or other recoveries do is nothing but execute a script in the zip, and place some precompiled bits into some specific folder, or even do some modifications at the block level, but one can never provide an API via recovery flash, because there's way too much going in there besides some bit changing. If we ever have to have Vulkan API support, or any API in that matter, it can never be "flashed and added". It has to be precompiled with the ROM itself, and it can surely be done.
TL;DR
You cannot "install" an API just by flash, your ROM have to be shifted with that already.
I don't think Vulkan would be of any use on our Snapdragon 410 since it is better optimized on SD 8xx . Stick to OpenGL for now
If you can change the GPU though..
Snapdragon 410 won't receive vulkan, only Snapdragon 415 and higher
I have seen Roms like HTC remix for Redmi 2 which gives option to update open GL es 3.0 to 3.1 by simply on int.d so I just I want to request devolopers for work on vulkan based ROM for Redmi 2 I have seen flashablle vulkan zip for Redmi note 3 ported from mi max
And again I am not a developer don't have any knowledge of programming only thing I can do is to count on u guys I have interest in it and one day my dream is to become a programmer
Suvam Mukherjee said:
I have seen Roms like HTC remix for Redmi 2 which gives option to update open GL es 3.0 to 3.1 by simply on int.d so I just I want to request devolopers for work on vulkan based ROM for Redmi 2 I have seen flashablle vulkan zip for Redmi note 3 ported from mi max
And again I am not a developer don't have any knowledge of programming only thing I can do is to count on u guys I have interest in it and one day my dream is to become a programmer
Click to expand...
Click to collapse
First thing you need to know:
-Redmi note 3 has a vulkan supported CPU and GPU
-And Redmi 2 dosn't
---------- Post added at 18:51 ---------- Previous post was at 18:23 ----------
Suvam Mukherjee said:
I have seen Roms like HTC remix for Redmi 2 which gives option to update open GL es 3.0 to 3.1 by simply on int.d so I just I want to request devolopers for work on vulkan based ROM for Redmi 2 I have seen flashablle vulkan zip for Redmi note 3 ported from mi max
And again I am not a developer don't have any knowledge of programming only thing I can do is to count on u guys I have interest in it and one day my dream is to become a programmer
Click to expand...
Click to collapse
Also, how did you enable 3.1 opengl support? if it is a init.d thing, can you upload the file here?
TecnoTailsPlays said:
First thing you need to know:
-Redmi note 3 has a vulkan supported CPU and GPU
-And Redmi 2 dosn't
---------- Post added at 18:51 ---------- Previous post was at 18:23 ----------
Also, how did you enable 3.1 opengl support? if it is a init.d thing, can you upload the file here?
Click to expand...
Click to collapse
Actually I can't I move to MIUI ROM but when I was in that ROM in customization settings there are few options to tweak performance by int.d so there u found an option called GPU renders optimization after enabling it I can have open GL es 3.1 and there are another way is that if u ever used GL tools u can have open GL es 3.1 over on 3.0
Just saying that Qcom is even willing to stop vulkan from working on msm8952 even though its perfectly able to run it. Furthermore, tell me where can I get any vulkan blobs for 32 bit msm8916, please enlighten me.
nicknitewolf said:
Just saying that Qcom is even willing to stop vulkan from working on msm8952 even though its perfectly able to run it. Furthermore, tell me where can I get any vulkan blobs for 32 bit msm8916, please enlighten me.
Click to expand...
Click to collapse
That's right, also, that opengl es 3.1 thing is real? I don't thing redmi 2 gpu support it
nicknitewolf said:
Just saying that Qcom is even willing to stop vulkan from working on msm8952 even though its perfectly able to run it. Furthermore, tell me where can I get any vulkan blobs for 32 bit msm8916, please enlighten me.
Click to expand...
Click to collapse
Sir I don't know anything about programming or coding only a thing I can do is to count for u if in future if it may possible to run vulkan API over on adreno 305 pls make a ROM on that for our device Redmi 2 that's what I am saying don't ask me to put vulkan blobs I can't do this
Currently on hold due to working on Nougat first.
I've got a booting or should I say bootlooping build of Lineage 15.0 for I9000. (galaxysmtd)
I've had to use crazy hacks like adb binary from 7.1 in ramdisk.
Just to get `adb logcat` working.
For now it's stuck at bootlogo. I've attached the logcat here.
I'm looking into it to figure out what needs to be done.
Sources:
manifests and patches I've used.
https://github.com/galaxys1-resurrected/local_manifests
https://github.com/galaxys1-resurrected/android_patches
Kernel:
https://github.com/galaxys1-resurrected/android_kernel_samsung_aries
Device Tree:
https://github.com/galaxys1-resurrected/android_device_samsung_aries-common
https://github.com/galaxys1-resurrected/android_device_samsung_galaxysmtd
Thanks:
@rINanDO for backporting kernel side of things to 3.0
@xc-racer99 and @Coldwindofnowhere for getting the device upto android 7.1
And all others who had worked from beginning till now on this device.
Is there anyone still working on this?
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.
a1shakes said:
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.
Click to expand...
Click to collapse
Unfortunately, no one is really actively working on Oreo. As you've found out, it's an issue with the graphics drivers that is holding everything back. No device (that I've found) that uses a PowerVR graphics chip (we use the PowerVR SGX 540) has working graphics drivers on Oreo. There were rumours that someone had found newer working blobs, but weren't able to release them publicly due to intellectual property laws that they were trying to figure out (but this was months ago).
Our GPU does support sufficient enough OpenGL, but only using BGRA8888 as opposed to RGBA8888. BGRA hasn't officially been supported in Android since ~4.2, but there's been a hack used to make things work. Come Oreo, things have changed and the hack no longer applies cleanly. However, I think the really issue is that the gralloc blobs was extended by PowerVR (see https://github.com/xc-racer99/andro...6.0/exynos3/s5pc110/include/hal_public.h#L119) but with the binderized HALs/VNDK/other low-level Oreo changes something has broken. I had a go at trying to work around things, but failed too.
There are a few ways I can think of getting working graphics:
1) Someone finds some updated blobs for the PowerVR SGX 540 for ARM (I've found x86 ones, but they don't work for obvious reasons)
2) Someone hacks around the source code so that the blobs work - but I'm not sure if it's PowerVR "extension" of the gralloc interface that is causing issues or not...
3) We simply use software rendering, but this would be so slow with our ancient CPU that I haven't bothered to try
4) We work on porting a newer kernel so we have the Samsung DRM kernel driver, use the Linux PowerVR blobs coupled with drm_gralloc/drm_hwcomposer and maybe a wrapper like https://github.com/TexasInstruments/dri3wsegl and somehow cobble together working support
In terms of the mediaextractor crash, that's due to the kernel missing seccomp support. There's a whole bunch of different backports, some more successful than others. Due to our ancient kernel, backporting is no longer very easy...
If we could somehow get the graphics drivers working, we'd have a pretty good base as there are free implementations of all HALs/drivers except for GPS and TV-Out (and, of course, graphics....).
Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?
nailyk said:
Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?
Click to expand...
Click to collapse
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.
xc-racer99 said:
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.
Click to expand...
Click to collapse
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.
nailyk said:
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.
Click to expand...
Click to collapse
If you're serious about trying to mess with graphics drivers, it might be interesting to check out the blobs from https://www.renesas.com/pt-br/produ...ion-boards/renesas-starter-kit-for-rzg1e.html as it's an ARM-based device with the SGX540. It's possible that they're new enough to not run into the same issues as the older blobs (but equally possible that even the kernel part is closed source). The binary blobs are only semi-SoC specific as I've managed to use the OMAP blobs with only having hardware decoding being broken.
Is it for real???
I9000 !!
Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490
Use android go it will be better.
MYEUHD said:
Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490
Click to expand...
Click to collapse
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time
xc-racer99 said:
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time
Click to expand...
Click to collapse
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).
xc-racer99 said:
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).
Click to expand...
Click to collapse
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
ChronoMonochrome said:
In 9.0, to get graphics to work, device is required to support HWC2 (or use either HWC2on1 or HWC2onFb adapters).
Click to expand...
Click to collapse
ChronoMonochrome said:
Yes, HWC has to be at least 1.3, to work with one of aforementioned adapters. With one of those adapters it will work like it was HWC 2 (but actually not exactly same).
Click to expand...
Click to collapse
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung
MYEUHD said:
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung
Click to expand...
Click to collapse
Was unaware of the fact. Are you volunteering to make the patches?
I've uploaded my changes to https://github.com/xc-racer99/proprietary_vendor_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_hardware_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_kernel_samsung_aries/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_aries-common/tree/ddk-1.14 but I think this might be the last I work on this as I don't really have the motivation to work on it anymore. Note the patches are against a custom version of Unlegacy Android 4.4 so you'll need to cherry pick the changes to your ROM of choice if desired.
The changes build, the EGL appears to initialize, but I always get
Code:
E/libEGL ( 471): validate_display:254 error 3008 (EGL_BAD_DISPLAY)
And in dmesg:
Code:
[ 8.509291] init: computing context for service '/system/vendor/bin/pvrsrvinit'
[ 8.509601] init: starting 'pvrsrvinit'
...
[ 8.601890] PVR_K: UM DDK-(4081762) and KM DDK-(4081762) match. [ OK ]
...
[ 8.765955] init: process 'pvrsrvinit', pid 99 exited
...
[ 55.560021] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.563491] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.597577] s3cfb s3cfb: [fb0] video memory released
Whether the issue is in the HWC or the gralloc blob that we've stolen from OMAP, I have no idea.
xc-racer99 said:
Was unaware of the fact. Are you volunteering to make the patches?
Click to expand...
Click to collapse
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??
MYEUHD said:
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??
Click to expand...
Click to collapse
You really do need jdk-7... I used the "reference implementation" available at http://jdk.java.net/java-se-ri/7 and made sure the java executables were in the PATH before the java I actually have installed.
Note that my Unlegacy Android trees will not work for the i9000 (well, they might, but you'd need to install u-boot as well at a bare minimum...)
It's kinda Insane that people are trying to get an 8 year phone to run oreo
@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?
MYEUHD said:
@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?
Click to expand...
Click to collapse
I've got the .repo folder, but don't have the individual files expanded as I don't have the disk space Could run a repo sync and look at things but don't have the disk space for a full build.
The_Pacific_gamer said:
It's kinda Insane that people are trying to get an 8 year phone to run oreo
Click to expand...
Click to collapse
its kinda insane that people are still using this phone.
FiX for MIUi 10 now!! ( xiaomi. eu Beta and global Beta Pie roms fix!!!!) (scroll to the end of post)
Update 23.12.2018. thanks to @dianluitao @EnesSastim and couple more people we have working GCam on MIUI 10 8.1
07.07.2019. *****UPDATE********
So for now cam2api is not buuged anymore on Pie roms (for now only beta) and here I will post how and files to go from 0 to full working GCam.
As usually you will need twrp and magisk or just magisk.
Flash in magisk file attached to enable Cam2api
Install recommended GCam (I am using it it doesn't mean it is the best one for you too)
Also there is file with preloaded GCam settings for easy use. How to load it? Well first open file explorer and make folder >>>GCam than make another inside of it >>>Configs than copy/paste Configs html file in it and not go and start GCam app, click couple of times on black area (around shutter button) option menu named :Choose confog pick the one you copy pasted in GCam folder and click Restore. Just to make sure close GCam clear from memory and open again. Settings is loaded and you are ready to use it.
Also thanks to @uvera we have this fix and thanks to all people involved in making GCam ports of html pre loaded settings for it.
Don't be twat, press that *****Thanks***** button below since I know you are all cheap m.... F.... and there will be 0 donations Cheers mates!
P. S. I have some troubles with attaching the files give me some time to work it out. Will update post during the day.
23.12.2018. Update - You will need china stable or miui.eu rom 10.2.3.0 for this to work ( I personal tested it on eu rom) all yopu need it root explorer, build prop editor and 2 files.
1) Download camera.sdm660.so and copy/paste it via root explorer into vendor/lib/hw/ and replace old file ( I used solid explorer to do so also you will need magisk since you need to give solid explorer root privileges ) (.so file is in zip so yes you need to extract it first than copy that file and replace it with old one).
2)go to build prop editor give it root privbileges and add this line : persist.camera.HAL3.enabled=1 (persist.camera.HAL3.enabled and in value box add 1) save it and restart phone
3) after this you will need to flash front camera fix to make front camera working. fix and rest of the files are at the end of this post !
Once again thanks to @dianluitao @EnesSastim @WebDingo and @Savitar (webdingo and savit for front camera fix) and all people responsable for this fix. :highfive:
Hi, I just want to make guide - simple step by step tutorial that people can follow and install GCam on our Mi Note 3 - Jason device. EVERYTHING you do is your own responsibility and I am not to be blamed if something goes wrong while you do so.
1. You NEED a rooted phone, for now, this ONLY works on rooted phones.
2.You need TWRP since you need to flash magisk and camera2api from there. Link to magisk >>> https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Thanks to @topjohnwu
3.Now when you flashed latest magisk you will need to do the same with camera2api (file will be at the end of this thread). Thanks to @uvera00
4.Now you can restart your device and install GCam apk from here >>>> https://www.celsoazevedo.com/files/android/google-camera/ I recommend Arnova's version 6 since it is the latest and it is working ok (it is not bugless) .
5.Now when you done all this start the camera and as you can see it is not working That is because you need to set it up correctly.
So correct (most stable ) settings are :
Advanced : Config camera HDR+ / Pixel 2017 ZSL HDR+
HDR+ parameters (you can play with this and decide which ones are best for you. I use Medium or Very High.
Disable front HDR+ / ON - THIS IS MUST HAVE
HDR+ image quality / Again this is to your own liking I use 97%
Well, this is basically it. Everything else is up to you to experiment with and share your best stable results. This setting I use every day and so far I didn't have any crashes. Also, a thing I forgot to mention in shooting mode you will see HDR+ icon up on the screen if you press it there is HDR+ enhanced mode and I do not recommend this since it is not working correctly with flash and it tends to crash app. I don't recommend it but it doesn't mean you cant use it
Share your best settings and some interesting pics! We are here to help each other.
GCam wouldn't be possible without Arnova, B-S-G, ivanich, scrubber, skulshady, cstark27, miniuser123, UriKill, Tolyan009, Charles_I, azevedo. This is their work and if you want to donate go to GCam donate link and donate to them. I am just here to make a bit simpler. Test GCam and have a nice day
Ok so there was some development for our device thanks to all GCam developers and @WebDingo for asking them to help us out. The new attacked zip is magisk module and it contains cam2api and front camera HDR fix for Mi Note 3. I tested it with couple of GCam versions and it works well. Flash it thry TWRP and enable (it should be enable by default ) in magisk. Also i there is now Arnova version on which manual focus works. The version is Arnova v7 test10 opt5-5t you can download it from official download page of Gcam ports i provided up in the thread. As always test and report
As you all know Gcam is not working on miui 10 builds. For now, we know "fix for it " i tried it on xiaomi.eu 10 stable build and it is working.
1. Download build pro editor from google play
2. Open build prop editor click on three dots in right up corner press + New - Name : persist.camera.HAL3.enabled and in Value field enter number 1 and click save.
3. in prop editor go to search and type persist.camera find this line - persist.camera.dxo=1 and delete it. Restart the phone. Now boot to twrp and flash camera fix for gcam and boot again.
4. Install Gcam you think will be good ( I tied it with OP6-1.2.1-Gcam and Gcam 5.1.018 by SerJo87)
The problem was (we think) during the broken blobs of OIS so by disabling it gcam works.
All of this wouldn't be possible without @dianlujitao @uvera and all other devs on MN3 telegram group. Special thanks to @rayser ( I don't know how are you signed up here buddy).
Findings so far:
Front camera has screen flash (when will MIUI camera implement this?)
HDR+ enhanced works correctly with flash in my case (MIUI EU 9.2.2.0)
HDR+ doesn't work correctly with flash (the flash is already off when the picture is taken)
HDR+ enhanced has greenish issue
60fps recording records 30fps (more like library issue from the base ROM)
Portrait mode doesn't work for front camera (lens blur works, though)
Are you using same settings as i mentioned above? What version of GCam ?
Video mode is very dark.....
I did intall difrently, because i dont know how to use magisk....but the result is the same.:angel:
Edit:
Forget it, video works normally..
You dont need magisk for GCam as an app. You need magisk to enable camera2api (which you did by fleshing it via TWRP) so you can just install/uninstall GCams apks normally. Also you can have more than one GCam installed on your device. I have currently 3 of them. V3.2 + v5 + v6.
What i did was wright the 2 lines with app Build.ini.
Did follow your sugestions for Gcam. Im at work without time to test....
Queston:
Why there isnt option for 13Mb in 16:9 mode? Only 9Mb....
You mean 13 megapixel and 9 megapixel ? Because 16:9 is cropped image and it is in 9mpx resolution.
dimi89 said:
Are you using same settings as i mentioned above? What version of GCam ?
Click to expand...
Click to collapse
Yes, v6.
Hi!
I'm on Xiaomi.EU 8.2.1 Rom .
When i activate the Camera2Api, Google Camera works, but i can not record 4K video with it, and the default Miui camera app also refuses the video recording in 4K.
I've tried a lot of camera apps, with same result. 1080p ok, but the 4K not at all.
What is the solution?
Another question:
It is possible somehow to achive 1080p with 60fps?
maybe with a modded media profiles.xml?
Thanks!
Good Questions...
Gonna try 4K too
P.S. NO problem on 4K both cameras...didnt see the sound.
is this quide for fully working google camera? or just somethings of it? like touch to focus, no crashing, hdr+? no greenish etc..
As I wrote, this is guide to set up GCam there are different versions with different bugs, in v6 manual focus inst working and hdr+ enhances sometimes crash when using with auto flash. There is version 3.2 where manual focus is working but low light images aren't that good. Also there is v5 where in my opinion are the best details. So you download different versions and try to see which one you prefer.
Послато са Mi Note 3 уз помоћ Тапатока
I tried many versions of GCam and stock camera since 8.2.1. is improved a lot. It makes similar photos (with HDR) to GCam.
But for me, best quality of photos is GCam V1,7. But sometimes it do not want to make photo on HDR+, only with enchanced.
So wich version of gcam should i install if i use all in auto with hdr on?
I'm on lineage
Try GCam 5v1.2 arnova or v6 arnova. But keep in mind that it depends a lot on settings of GCam. For GCam 5v1.2 use Nexus 6P and Pixel 2017 ZSL +
Послато са Mi Note 3 уз помоћ Тапатока
I strongly recommend to try this one https://forum.xda-developers.com/showpost.php?p=75850874&postcount=43
Antretng said:
I strongly recommend to try this one https://forum.xda-developers.com/showpost.php?p=75850874&postcount=43
Click to expand...
Click to collapse
That's the first app + settings I've found with no bugs. Haven't deeply tested quality, but everything works.
Night shoots are black for me. It appears flash isnt helping. Same settings i used as in pictures.
Sent from my Mi Note 3 using Tapatalk
GCam is not working
GCam Arnova v6 is not working. It shows Black Screen only after configuring everything on Mi Note 3.
Is there 1080P 120fps slow-motion video capture available ?
Doesnt work on my note 3, i just get black screen. Version V6 and i'm using miui eu 8.3.8
---------- Post added at 09:15 PM ---------- Previous post was at 08:55 PM ----------
OK i fixed, just enabled "Disable front HDR+"
First Of all.THIS IS NOT A QUESTION OR A CALL FOR ACTUAL HELP.I have seen a few replacements for AOSP and Postmarket OS is one of them.Being in early stages it is very useful if being ported or compiled for Devices with stylus or phablet factor.I am Currently working on the OS after I read the Documentation.I as of Now have managed to Run the Test UI on it.All functions(except GPS ril Bluetooth thermal and maybe MTP)Do work Properly.The Main UI is still un-bootable.I would post it as soon as Possible.The Main Feature of this is THAT IT USES THE MAINLINE LINUX KERNEL.A little crazy to say it but it says it does that and it may take a week to do it.I have compiled it 37 times and it takes a very little time on my machine But the number of fatal errors are in hundreds or Thousands which are all Related to compatibility.
A huge thanks to xda-Website and a shoutout to PMOS(as I would call it) for doing such a great thing.
Again I can't do it myself The only thing I can't seem to make it work is to boot the rootfs for unknown reasons.As Soon as I achieve something I will Post Links.
kernel that works https://github.com/LineageOS/android_kernel_samsung_msm8974
kernel that's official
https://github.com/CyanogenMod/android_kernel_samsung_hlte
zImage that boots(with halium rootfs that works with any rootfs)
https://drive.google.com/file/d/17ksmUn5FTqOuL9mKsOCqrhe3W3mqGwUe/view?usp=drivesdk
the latest linaro 7.3.x toolchain arm for note 3
https://drive.google.com/file/d/1Ld5Nb7rekgbFLAcyW16721_1GITP_2wv/view?usp=drivesdk
zImage that get's to testing
https://drive.google.com/file/d/12sQbEzl4nfK7E3IXwbpxIYy_mKcZ6Q4W/view?usp=drivesdk
common kernel zImage built on nexus 5 model doesn't boot.
https://drive.google.com/file/d/1GyJKCKn9DxynOeTx8Ea4wHSxHm7S1nd1/view?usp=drivesdk
and again help is appreciated.
Sent from my Pixel 3 XL using Tapatalk
Hello all!
Ultimately I would like to install a version of the GCAM on my Xperia Z3, cos the picture quality is just so much better than anything I know from stock.
However I'm already failing at step 1 - Getting the Camera 2 API enabled on my phone. There are some Magisk Modules and other patches floating around which I tried - No luck.
I also tried editing the build.prop file and set persist.camera.HAL3.enabled=1 - No luck
I use the Camera2 Probe App to check if the API is enabled but alas it always shows "Hardware Support Level - Legacy" only.
I'm currently running AOSP Extended (Android 9). Also tried with Carbon ROM and some other custom roms, all with the same, negative result.
Is there any limitation here that I'm not seeing - Does anybody know of a possibility of enabling this API on the Xperia Z3?
Ok, let me try a different approach - The Z3 was launched in 2015, so it's a pretty old phone.
Question1: Is the Camera2 API a pure software API, or does the underlying camera hardware also have a role to play here?
Question2: Is the API part of the ROM, or is it part of some Google framework / GAPPS? If it is part of the GAPPS, which part?
I'm curious because I tried several Android 8 and 9 custom ROMS, installed several versions of GAPPS, fiddled with the build.prop file and none of these measures enabled the Camera2 API on this device.