yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] minealex2244:
Where did you get that info? :) HwComposer is not abandoned but it is really hard to be fixed and ported for our device. It is closed source so we need to use other sources and to adapt them for modern days. I was always curious what is changed with the new HwComposer. Anyone can cherry-pick forkbomb's commits regarding HwComposer and then to build it. I think I'll try to build it.

Edit: The plan is simple: clone LineageOS/android_kernel_samsung_smdk4412, fetch forkbomb's repo, cherry-pick the commits from 'fix_hwc' branch then building the kernel. I'm not sure how stable this will be but you never know.

---------- Post added at 09:37 PM ---------- Previous post was at 09:27 PM ----------

There is some work on LineageOS 15.0 for our kernel :) It is updated with the lastest commits from cm-14.1 branch.
[Galaxy S III Original Android Development] aser_elhbayeb:
That was a personal guess as I said before, as for building a test build, I would have learnt how to do it and did it if I had a PC in the first place, so I guess I will kindly be waiting your testimonial :D .

As for LOS 15, do you think that the fix will be migrated to be released on LOS 15? of course no one can tell for sure, so all these are speculations.

Eventually, Waiting a month or two is nothing for those who waited years to get it.
[Galaxy S III Original Android Development] qb74:
if you actually expect HWC & LOS15 to be both released, fully stable and working in that time frame, you're quite wrong.

still wondering why nobody bothers making a MM ROM w/ LOS14.1 CamHAL fixes & Nameless HWC (which is 99% stable i'd say, the 1% is because im not entirely sure how to test it. would have to edit the latter though to cooperate with the CamHAL fixes).
[Galaxy S III Original Android Development] aser_elhbayeb:
Although it was just a hope, but it's OK for it to be more than that time period as long as we know for sure that it will eventually be here. As for you wondering, I also add my voice to yours, though it looks it won't happen.
[Galaxy S III Original Android Development] minealex2244:
The fix will be already included in LOS 15.
[Galaxy S III Original Android Development] zarere:
Is that what we are waiting for ;)
[Galaxy S III Original Android Development] Hesham Sleem:
is there anyway to odex apps in this rom.... it will save more storage
[Galaxy S III Original Android Development] Nintendraw:
Is this the right place to ask this? I recently installed LineageOS onto my brother's phone (GS3 Int'l, i9300), and the screen occasionally glitches out during normal usage. He hasn't told me if there's a particular app that causes it, but while using apps, his screen occasionally blacked out and/or showed horizontal rainbow bands. I just reinstalled LineageOS, GApps, and Magisk one at a time (the first time I did it, I did all three at once), but I'm not sure if that fixed it. The phone will turn on and be used normally and can definitely reach TWRP Recovery (it should be able to enter Download Mode too).

Another question (probably should be posted in the more relevant thread): After both times installing LineageOS and co., the phone doesn't pass SafetyNet check. I hit the "run SafetyCheck" option and two X's appear instead. What is the best way to fix this? I also didn't see a Busybox option in the app.
[Galaxy S III Original Android Development] Ashley david:
Magisk doesn't pass safety net because our s3's kernal doesn't support it and the kernal is old that's why:)
[Galaxy S III Original Android Development] eriol1:
It was a known issue on cm13 iirc, no idea if it was ever fixed though
[Galaxy S III Original Android Development] Nintendraw:
Ugh. So does that mean my i9300 won't be able to run Pokemon Go, FE Heroes, or other apps that do a Google SafetyNet Check?
[Galaxy S III Original Android Development] Ashley david:
Yes.you can give it a shot but the safety net won't pass
[Galaxy S III Original Android Development] minealex2244:
The kernel only needs a little patch in cmdline.c for SafetyNet bypass support. I'm not sure if it will work but who knows. I want to build it tomorrow with HwComposer fixes too. :D

Also that visual glitches are possibly caused by the display. If it was dropped hardly on the ground it is possible that the connectors are damaged leading to a failure. Just open the phone up and see if motherboard and connectors are Ok.
[Galaxy S III Original Android Development] ZjemCiKolege:
For me with magisk no any problem with safetynet ._.

[MENTION=6371648]minealex2244[/MENTION]

I9300 have open bootloader.. patch is no needed

https://review.lineageos.org/#/c/155563/
[Galaxy S III Original Android Development] minealex2244:
It doesn't matter if bootloader is unlocked. S6 has unlocked bootloader too but it needs a patch in kernel for SafetyNet bypass. By having that patch in S3's kernel it would possibly make SafetyNet work for everybody.
[Galaxy S III Original Android Development] ZjemCiKolege:
Okey im waiting for this build with these change.. im not sure this work... ;]
[Galaxy S III Original Android Development] multiwirth:
Could you share the best hwcomposer after testing?
[Galaxy S III Original Android Development] galen2:
Magisk will not work without upstream kernel to 3.8 and my guess is that no one will do that. Suhide also dont work. I tested myself both.

EDIT: I talk about safetynet pass
[Galaxy S III Original Android Development] Samofr:
Concerning battery life, this one is very bad (using hwc provided by aser elhabayeb cm13). I got 15% drain when sleeping with everything turned off.

So far imo, i guess that the one from archi 3.1.5 is the most stable when it comes to both performance and battery..

Concerning video playbacks issue i didnt really test it because i usually dont watch videos on my phone.

I think everyone should try all hwc before making judges.
[Galaxy S III Original Android Development] schwatter:
https://github.com/ArchiDroid/ArchiDroid/blob/i9300-cm-stable/system/lib/hw/hwcomposer.smdk4x12.so

Here. I would say, rename it and test.
[Galaxy S III Original Android Development] aser_elhbayeb:
CM13's HWC fix consists of two files: hwcomposer.exynos4.so

hwcomposer.vendor.exynos4.so (which is the same as ARCHI's).

So I guess it won't make a huge difference in performance or battery life.
[Galaxy S III Original Android Development] minealex2244:
I see that everyone is omitting the complete list of HwComposer fixes. Yes, we have these files but the video driver is also included in this game ;) You can't fix HwComposer only by fixing that lib. You need a fix into the kernel too.
[Galaxy S III Original Android Development] Logan:
Been lurking and waiting for a while to hear this specially from you as it's 100% correct.

If it's that simple by replacing the hwc solves the issue then all cm/los based roms should have it working from years.
[Galaxy S III Original Android Development] Noobkid77:
Does this mean we should see a HWC soon ? Sorry for the noob question I am a Noobkid after all
[Galaxy S III Original Android Development] minealex2244:
Uhm maybe but not from forkbomb. I'm using his commits to build the fixed HwComposer. But it is completely wrong to say "HwComposer" because it's more than that.

Here is the complete list of all affected files: hwcomposer.exynos4.so, libhwjpeg.so, gralloc.exynos4.so and gralloc.default.so, libhwconverter.so, libfimc.so, libfimg.so and then the kernel.

When I saw some "clever" people saying: "Oh hey guys. Just use the CM13 hwcomposer.exynos4.so file and you fixed HwComposer" I started laughing like crazy. Did you know that .so means shared object? Why is it shared? Because Android is generous? No, but because that .so file is used by a process to get some necessary functions from it. They are interconnected. Replacing a new file with an old one doesn't help. Also someone claimed that there weren't so many updates for HwComposer. False! Just because you compare HwComposer from CM13 with CM14.1 and you see that the size is almost the same it doesn't mean that nothing was done to HwComposer. The current size of HwComposer is 34 KB. My compiled HwComposer is 33,50 KB. It all depends on the compiler. I'm using a different compiler that the compiler used by the LOS team on their build masters.

In conclusion, stop doing such tests because you will fail for sure. And always remember about placebo effect after replacing a file and then a reboot (reboots cause the RAM to free and the device will become responsive again, pure placebo).

Edit:

Here is an useful link: https://github.com/fourkbomb/android_hardware_samsung/commits/staging/cm-14.1-ion

We are interested in the commits since July 12 (everything from "power: Temporary logging fix" excluding it until the last commit).
[Galaxy S III Original Android Development] Noobkid77:
The reply is highly appreciated and thanks for volunteering on working on the new files. Yeah I guess swapping wasn't the most smart thing but hey when you're desperate you tend to do desperate things lol. Cannot wait until the complete Hwc is ready I won't even ask for ETA because we've waited so long already.
[Galaxy S III Original Android Development] minealex2244:
The things are not guaranteed. My first test failed with this result: after replacing HwComposer with the new one nothing graphical appeared on the display :) Clearly I need to fix the dependency in the other files and in the kernel.
[Galaxy S III Original Android Development] Noobkid77:
It's a pity but whatever happens we'll all surely be waiting patiently.
[Galaxy S III Original Android Development] LuciferIII:
Pressing the "Thank you" button is not enough. Everyone in this thread should appreciate the amount of testing and information you gave us.

If i recall you now have a s6 and you still test out the good old s3. :good:

Thank you for clearing up the hwc dilemma, most of us (i assume) don't know much about how the android system and his inner components work,i didn't even know what hwc is until i joined this thread a few months ago. We thought that it was as simple as replacing a single file, which wasn't the case as you explained.

Anyways, Thank you for everything you've done!
[Galaxy S III Original Android Development] abelenki:
lineage-14.1-20171004-nightly-i9300-signed.zip is available at:

https://download.lineageos.org/i9300
[Galaxy S III Original Android Development] yoahmad1995:
Did anyone try lib and omx folders from Nameless MM? It's the best for me so far tho.
[Galaxy S III Original Android Development] Option58:
Lineage already has everything worthy. Last thing was that screencast fix. Now it's unfortunately only on developers to impove a rom. Copy-pasting files is (while maybe fun lol:D) pointless as you can't achieve anything.
[Galaxy S III Original Android Development] minealex2244:
Hahaha. :) Oh my God, again this kind of stuff.

---------- Post added at 09:20 PM ---------- Previous post was at 09:14 PM ----------

I managed to build and try all the files I already mentioned in my other post but unfortunately I got into a bootloop. The last thing I need to do is to build the kernel. But I did it. Unfortunately the kernel binary size was 11,5 MB instead of around 3,5 MB so something is not ok. I need to shrink it.

Using the new HwComposer taken me to a "dark" world (no graphics shown on the screen at all) and the new gralloc.exynos4.so gave me the bootloop at Samsung logo.

Just a question: Are videos working for you guys? :) I didn't play any video on my S3 for 1 month so I'm not sure whether I broken something or it was already broken.
[Galaxy S III Original Android Development] LuciferIII:
Never had any video issues on this ROM.

Also Simon updated some commits 2 times the past 3 days and I think they are hw related
[Galaxy S III Original Android Development] ttayyab:
My observations on CM 11 and ArhiDroid 3.1.5 HWCs

CM 1 1 is slightly less smooth but causes very little battery drain on standby (1-2% per night over 9 h period)

Archi's drains on average 10-15% at night (same 9 h period) but supposedly, although I'm not too sure of the difference, feels a bit more smooth

Note that both were tested without gapps, with zzmoove - optimal governor in Boeffla

Honestly, I didn't have any issues with LOS default HWC except for an increased frequency of media playback stoppage which I largely attribute to Instagram and Whatsapp
[Galaxy S III Original Android Development] minealex2244:
:)) Yet again... HwComposer myths.
[Galaxy S III Original Android Development] Option58:
You're right :)

Guys, go to the terminal or adb shell.

Type in:

su
dumpsys SurfaceFlinger

And you'll see that non of the hwc you are trying actually got activated :)

GLES - means OpenGL for the embedded systems (your GPU)

HWC - means...well you know what it means :)
[Galaxy S III Original Android Development] dana.marivani:
Hi guys, News from Oreo is not ?
[Galaxy S III Original Android Development] minealex2244:
No one worked on it for some time. There are still some pending commits which would change everything (I mean, we will get 8.0 then). I think that Simon needs to fix HwComposer before the 8.0 update. Maybe they have local changes and they are testing the things. Let's have some patience :)
[Galaxy S III Original Android Development] rocciacoraggiosa45:
hello, i have 3 problems, first random my phone show "no services" and i not have line (i change modem but nada), second i have random reboot ( in july rom i not have reboot), and third nova launcher say me , random, to set default launcher, i not know if 3 problems is related to performace profile (i/o is busy?) or not and why i can't power on wifi with aereo mode? and when simon add a togle for switch battery profile? thank you all for reply
[Galaxy S III Original Android Development] minealex2244:
1. Check your SIM card. Maybe it is faulty. Go to your carrier shop and change it with a new one. You will notice a better performance when enabling mobile data. Also I'm not having that issue.

2. Are you using any kernel manager like Kernel Adiutor or maybe Boeffla kernel? A clean flash is recommended. I didn't notice any random reboot except when I had Boeffla. Also I didn't do any clean flash for months.

3. Install Nova in system (priv-app folder) and it should not bother you again. ;)

* I can enabled WiFi while in airplane mode. I'm not sure what you did... :/

*"When Simon will add XYZ". First of all, Simon won't add anything at the request of an user. It's LineageOS! Everything is organised here! There is nothing custom just for one device. Every device will get the same things. Secondly, that feature is already there, in the battery settings!
[Galaxy S III Original Android Development] LutherH:
Hi, I flashed the official Lineage OS on my i9300, but the camera does not seem to open. Just get a blank screen with the camera icon. Not working with other apps neither.

Is anyone able to assist please?

thanks
[Galaxy S III Original Android Development] rocciacoraggiosa45:
first in lineageos 21/06 with boefla 6.0 stable i not have any of this bugs and now i have 04/08 with last boefla

1- my sim card work fine in other phone only in this random show "no services" i have gna2 modem

2-yes i have boefla but "in lineageos 21/06 with boefla 6.0 stable i not have any of this bugs"

3- ok i try this but in old rom this bug not show

4- when i active airplane mode i can't active wifi rom say me "in aereo mode"

5-in cm13 have a toggle like a speedometer
[Galaxy S III Original Android Development] minealex2244:
You need courage to report this!!! Did you know that Lord Boeffla didn't update the sources for his S3 kernel since July 29? No, why would you care? You only want to confuse Simon so he won't know what's the problem!

1. Try other modems as well. Mine is LFB. It is working well.

2. Do not compare the days when it was updated with these days when it's outdated.

3. Things changed...

4. "Aereo" what's that? It's airplane mode. I switch it again and again and WiFi can still be enabled while it is ON.

5. The same is present in the battery settings. Just listen to me: go to settings then battery and you will see the menu to change the battery profile. Yes there isn't any quick setting for now. Maybe there will be :)
[Galaxy S III Original Android Development] minealex2244:
Are videos working for you? If not then if you configured your kernel either by using Kernel Adiutor or Boeffla kernel set all the read aheads to 128 KB.
[Galaxy S III Original Android Development] RudeYute:
Videos play fine. I did not touch the kernel - Flashed default Lineage, and did not modify the kernel.
[Galaxy S III Original Android Development] aryan79:
I've the last version and I can't restore the whatsapp backup in Drive. Unfortunately I haven't the old folder. How can I do? :(
[Galaxy S III Original Android Development] minealex2244:
Do this:

- go to TWRP and wipe system, data, dalvik-cache and cache

- flash latest build then GApps and if you want root then flash SuperSU

- after boot up and configuration of everything in Setup Wizard check camera. Do not install any app and report if it works or not.
[Galaxy S III Original Android Development] Elton47:
Official Xposed is live now! Cheers!
[Galaxy S III Original Android Development] kosmasgr:
Are there any modules work on Nougat ?
[Galaxy S III Original Android Development] rocciacoraggiosa45:
wtf?!!

Version 6.1-beta2

13.09.2017

Update: Updated with latest official LineageOS kernel commits as of 13.09.17, 08.00 CET

Change: Internal kernel busybox updated to latest version 1.27.2 (self-compiled from sources, www.busybox.net)

Change: Improve safetynet handling (credits to SultanXDA)

1-can you post your modem without ril?

2-what?!

4-yes sorry airplane mode, when i try to active wifi when i stay in airplane mode, phone say me "in airplane mode" and not active wifi

5-i hope togle add in future
[Galaxy S III Original Android Development] minealex2244:
Flash my modem using Odin. I got it with the motherboard replacement and I didn't change it. :)

Also Boeffla kernel is still outdated.
[Galaxy S III Original Android Development] Elton47:
I do not know, it is been some years since I lastly used Xposed. I am very excited to use it again but I have to flash RR back because I was checking out ViperOS. I will let you know as soon as I find any.
[Galaxy S III Original Android Development] dana.marivani:
Guys,I'm a curious question,Display brun-in protection into Display what is his duty to what is?
[Galaxy S III Original Android Development] LuciferIII:
Xposed + sensor disabler = No more proximity sensor on lock screen.

Disadvantage : when calling your proximity sensor wont work.

But i don't care :D
[Galaxy S III Original Android Development] Cr0n0s:
Xposed Additions, Youtube Background Playback and Greenify Experimental Features work great. Haven't tried anything else.

I wasn't able to find Youtube Background Playback in the module download list. So I had to download the .apk from somewhere else.
[Galaxy S III Original Android Development] kosmasgr:
Which version of Greenify ? On 3.7 , when I tap something on experimental settings , it says me to enable the module but its already enabled :(
[Galaxy S III Original Android Development] rocciacoraggiosa45:
[MENTION=6371648]minealex2244[/MENTION]

it's possible a correlation of sim "no service" and reboot with micro sd?
[Galaxy S III Original Android Development] minealex2244:
Wow! No.

---------- Post added at 07:15 PM ---------- Previous post was at 07:10 PM ----------

I would like to help you if I could understand your sentence correctly :( Correct me if I'm wrong: "Guys,I'm curious about one question, Display burn-in protection, what is its scope?"

For this question the answer is simple: to prevent the burning of the pixels because of the static icons in statusbar and other sensitive areas this option will enable the periodical movement of these icons. You won't notice it. It is silent. :)
[Galaxy S III Original Android Development] rocciacoraggiosa45:
[MENTION=6371648]minealex2244[/MENTION]

But i have read that micro sd is a possible cause of random reboot and micro sd card and sim have same connector to motheerboard
[Galaxy S III Original Android Development] multiwirth:
Typed in your command and it tells me

h/w composer state
h/w composer present and enabled
Hardware Composer state (version 01000000):
mDebuForceFakeVSync=0
Display[0] configurations (*current):
* 0: 720x1280

There are much more lines but in all it says hw composer is present, enabled and works
[Galaxy S III Original Android Development] H4RTI3:
Scroll further down, then the hard reality will hit you :D

( I also tried the command)
[Galaxy S III Original Android Development] multiwirth:
What will i see there?

L

All other lines are package names.

I've just tried this command on my htc and got a different result but there are things on the galaxy s3, missing on the htc and things on the htc, missing on the galaxy s3.

But some lines are nearly identical
[Galaxy S III Original Android Development] dana.marivani:
Thanks for your help and advice But I feel this Display brun-in protection Newly added And I did not know what it was

Anyway, I'm grateful to you
[Galaxy S III Original Android Development] H4RTI3:
h/w composer state:
h/w composer present and enabled
Hardware Composer state (version 01000000):
mDebugForceFakeVSync=0
Display[0] configurations (* current):
* 0: 720x1280, xdpi=304.799988, ydpi=306.716980, refresh=16666111, colorMode=0
numHwLayers=3, flags=00000000
type | handle | hint | flag | tr | blnd | format | source crop (l,t,r,b) | frame | name
-----------+----------+------+------+----+------+-------------+--------------------------------+------------------------+------
GLES | 41da9c60 | 0000 | 0000 | 00 | 0100 | RGBA_8888 | 0, 0, 720, 1280 | 0, 0, 720, 1280 | com.android.systemui.ImageWallpaper
GLES | 41da9900 | 0000 | 0000 | 00 | 0105 | RGBA_8888 | 0, 0, 720, 1280 | 0, 0, 720, 1280 | com.google.android.googlequicksearchbox/com.google.android.launcher.GEL
GLES | 408a2820 | 0000 | 0000 | 00 | 0105 | RGBA_8888 | 0, 0, 720, 48 | 0, 0, 720, 48 | StatusBar
Allocated buffers:
0x408a0cc0: 3600.00 KiB | 720 ( 720) x 1280 | 5 | 0x00001e02 | FramebufferSurface
0x408a2760: 135.00 KiB | 720 ( 720) x 48 | 1 | 0x00000f02 | StatusBar
0x408a27c0: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x00000f02 | com.google.android.googlequicksearchbox/com.google.android.launcher.GEL
0x408a2820: 135.00 KiB | 720 ( 720) x 48 | 1 | 0x00000f02 | StatusBar
0x408a2ca0: 3600.00 KiB | 720 ( 720) x 1280 | 5 | 0x00001e02 | FramebufferSurface
0x41da95a0: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x00000f02 | com.google.android.googlequicksearchbox/com.google.android.launcher.GEL
0x41da9900: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x00000f02 | com.google.android.googlequicksearchbox/com.google.android.launcher.GEL
0x41da9c60: 7200.00 KiB | 1440 (1440) x 1280 | 1 | 0x00000f02 | com.android.systemui.ImageWallpaper
0x41daa0e0: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x00000f02 | com.google.android.googlequicksearchbox/com.google.android.launcher.GEL
0x41daa140: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x00000f02 | org.lineageos.jelly/org.lineageos.jelly.MainActivity

In the table, it says GLES for the rendered HwLayers (no HWC)!
[Galaxy S III Original Android Development] multiwirth:
However I found another thing:

I tried many different devices.

All are reporting the GPU vendor and model for example my HTC HD Mini but not on the galaxy s3
[Galaxy S III Original Android Development] H4RTI3:
On mine it works:

GLES: ARM, Mali-400 MP, OpenGL ES 2.0
GL_EXT_debug_marker GL_OES_texture_npot GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL_OES_depth24 GL_ARM_rgba8 GL_ARM_mali_shader_binary
GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_EXT_blend_minmax GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8
GL_EXT_multisampled_render_to_texture GL_EXT_discard_framebuffer GL_OES_get_program_binary GL_ARM_mali_program_binary GL_EXT_shader_texture_lod GL_EXT_robustness
GL_OES_depth_texture_cube_map
[Galaxy S III Original Android Development] Elton47:
pastebin.com please
[Galaxy S III Original Android Development] davidvanwijk:
Thanks for feedback.

Verstuurd vanaf mijn GT-P7500 met Tapatalk