Database Users

64 bit support for LG Leon

Judging from the build.prop and the instructions provided by LG to build the kernel, and various system information apps, the software on this phone does not have 64 bit enabled. However, the a53 cores used in the chipset DO support 64 bit, as well as armv8-a instructions, which judging from the build.prop, this software does not support either. Does anyone know if building the kernel with a 64 bit toolchain and changing the ro.product.cpu.abilist properties is enough to enable 64 bit support? If not, what modifications to the kernel/OS needs to be made?

Excuse the Necro bump but i've been wondering the same thing, any news? I've found some info over here https://source.android.com/source/64-bit-builds.html#module_definition_in_android_mk

Want vulkan api

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

Android Oreo 8.0 / Lineage 15.0 Dev Discussion

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.

J5 2016 GPU Drivrrs

So here are drivers for adreno 306 https://github.com/Koloses/propriet...mmit/b180bc92d6de3c923974e58f9aba6147595771f7
Can enyone of programers download that repo and take the files which you see in that commit, place them in the correct folders and set correct permissions. Its suposted to be better preformance but i dk will it work with nougat ?

What's API Vulkan version and build drivers date OpenGL ES still on Android 9?

can someone confirm for me what's the version of vulkan and GL drivers date on Custom Rom based on Android P ? Is easy to find, download Aida 64, go to screen and send me screenshot, and to find vulkan, go to "devices" scroll down and find vulkan version, send me screenshot. I will aprecciate if someone give me this, thanks.

hehk1234 said:
can someone confirm for me what's the version of vulkan and GL drivers date on Custom Rom based on Android P ? Is easy to find, download Aida 64, go to screen and send me screenshot, and to find vulkan, go to "devices" scroll down and find vulkan version, send me screenshot. I will aprecciate if someone give me this, thanks.
Click to expand...
Click to collapse
https://www.xda-developers.com/vulkan-graphics-api-1-1-android-p/
Vulkan API is 1.1.66 but i don't know if it's the stock API because i have update GPU Adreno Drivers (269 > 319).
I'm on CrDroid Pie (Treble - Base PR2)
EDIT : API version is only 1.0.61 with the GPU Drivers Stock (269), so i advise to update your GPU Driver for update GPU/Vulkan

Pho3nX said:
https://www.xda-developers.com/vulkan-graphics-api-1-1-android-p/
Vulkan API is 1.1.66 but i don't know if it's the stock API because i have update GPU Adreno Drivers (269 > 319).
I'm on CrDroid Pie (Treble - Base PR2)
EDIT : API version is only 1.0.61 with the GPU Drivers Stock (269), so i advise to update your GPU Driver for update GPU/Vulkan
Click to expand...
Click to collapse
thanks bro, I'm still on Oreo 5.1.4 OxygenOS, vulkan support 1.0.61 and drivers 269.
Can you test for me resident evil 4 from dolphin GameCube rom with vulkan render ? Use latest version of dolphin from repository, and give me feedback if will get the correct texture or blank texture. On Oreo I get blank screen, on SD710 runs the graphics without problems, problably the drivers are buggy or less extension on Vulkan API. Thanks bro

Pho3nX said:
https://www.xda-developers.com/vulkan-graphics-api-1-1-android-p/
Vulkan API is 1.1.66 but i don't know if it's the stock API because i have update GPU Adreno Drivers (269 > 319).
I'm on CrDroid Pie (Treble - Base PR2)
EDIT : API version is only 1.0.61 with the GPU Drivers Stock (269), so i advise to update your GPU Driver for update GPU/Vulkan
Click to expand...
Click to collapse
I'm still on oreo 5.1.4, the vulkan version is 1.0.61 and GL drivers V269. Can you test Resident Evil 4 from emulator Dolphin ? I just want to know if qualcomm give the right extension to render this game, on SD710 Oreo, runs RS4 as well, on Oreo from OP5 I got blank screen (error graphics when I try to use vulkan), some extension are missed, if want to give me this feedback I would aprecciate your little time, use latest version Dolphin emulator and use vulkan API.

Sorry for Double answer, XDA don't update my last answer and I think it don't send.

hehk1234 said:
I'm still on oreo 5.1.4, the vulkan version is 1.0.61 and GL drivers V269. Can you test Resident Evil 4 from emulator Dolphin ? I just want to know if qualcomm give the right extension to render this game, on SD710 Oreo, runs RS4 as well, on Oreo from OP5 I got blank screen (error graphics when I try to use vulkan), some extension are missed, if want to give me this feedback I would aprecciate your little time, use latest version Dolphin emulator and use vulkan API.
Click to expand...
Click to collapse
You can update even on OREO
--------------------[OREO SECTION]--------------------
[README]
* Not compatible for android older than 8.0 (Oreo)
* V313.0 is compatible with android 9.0 (Pie) too
* Tested on Mi Mix on LOS based non-treble ROMs
[DOWNLOAD]
LATEST : v313.0 REV15
https://drive.google.com/drive/folde...mpHtvummFs45Ci
Click to expand...
Click to collapse
Sorry but i don't have the time for take a emulator and download a ISO for try just your personnal thing. Update your Drivers, it's always better.