yashsingh1/xdaforums huggingface dataset:
[Galaxy S3 Neo Original Android Development] Humaxxx:
Build-in-function "Cast Screen" was working for me on LOS14.1. On LOS16 it seems to be broken or as i read on the web, it seems to be removed by google!? I tried casting on LOS16 on S3Neo, S4 and S7. It was always searching, but didn't find any device. Casting only worked with an app from Playstore. I tested also on LOS17.1, on S3Neo, there it was also not working with the build in function. If its neccessary for you to use the build in function you can write a bug report on LOS "bugtracker"

With "Wifi direct" i can connect my devices like S3Neo and my Samsung TV or S3Neo and S4. But it seems there is no option for doing more than just connecting?! MAybe you need a file explorer or something else to transfer files...
[Galaxy S3 Neo Original Android Development] helloyello:
Thanks for the tests and reports. I can't find a record stating that Google removed Cast Screen and it's available in all new smart phones. Furthermore, you have it also in LOS16, but, as you already noticed, broken. :(

You could use some third party app, like Samsung Smart Connect, but that is just an overlay for helping users identify and connect, it still uses the underlying (Android) implementation, which again, is broken in LOS16.

Now, we are again in the situation as with the WiFi issue not connecting to hidden networks. Why bother registering a bug report if no none gives a damn about. I already stated that my impression about this LineageOS development is that it is driven by hobby/fun and it lacks seriousness. Kind of, lets build a pile of crap that works somehow and don't bother with any issues, affecting basic functionalities in this case, that could be maybe easily fixed, just perpetuate the crap from version to version...

Well, I'm still using LOS16, and appreciative about the half-work done by the Devs, but seriously considering dumping the S3 and buying a new Samsung A40. A pity, the S3 Neo is still a nice and powerful phone that can handle all my activities, even now, 4 years after the purchase.
[Galaxy S3 Neo Original Android Development] Humaxxx:
The third party app i tried was working. i could stream videos from my S3Neo to my Samsung TV, but didn't try to "just" cast my screen of my S3Neo to the TV...

Yes its a pitty, that often no one of the devs of LOS responds to reported issues...
[Galaxy S3 Neo Original Android Development] josch85:
Yes, I'm using the minimum brightness and a black background.

I'm grateful for the time all developers are investing in keeping old devices running on new android versions. Don't underestimate the efforts needed to port a new android version to a device. I investigated a lot of github repositories trying to understand the way custom roms are created. With every new android version you have to start again fixing and adapting stuff. For me the real crap are non open driver/binarys which run only on a specific kernel version. Even a 12 year old Eee PC can run with the latest kernel.
[Galaxy S3 Neo Original Android Development] helloyello:
Which is irrelevant for a normal usage scenario.

If you follow my posts, a little more carefully, you'll learn that I'm always appreciating the efforts the devs put in this LOS. However, I cannot respect the final product, simply because it's not finished, there are Android subsystem related issues that (according to my understanding and knowledge) have nothing to do with the device support (drivers / kernel).

Additionally, if you read the "LOS manifesto", you'll learn that devs commit to care and fix functionality issues. I'm not impressed TBH, just look at the WiFi issue - not connecting to Hidden Networks and now the Cast Screen function - both presumably needing some fixes in the Android connectivity subsystem and not related to device support.

Finally, I was looking for an alternative to stock ROM on my S3 Neo, because I started to get concerned that Apps won't be available anymore for KitKat. Providing the device "a last chance" before giving it to the kids to play with and ... destroy it, while I'm already considering buying a new phone. The S3 Neo is still keeping up with my demands and the stock ROM is still OK - I cleaned and secured it pretty good and the Apps & personal usage (Firefox / Signal / Skype) were working just fine.

If LOS doesn't provide a viable alternative and is just built to work somehow, in a hobby/fun way, then I'm afraid the whole effort doesn't make much sense. And this is my own PoV about it, considering the reliability and seriousness I expect from a phone I use as my primary device on daily basis.

Well, LOS (and the formerly defunct Cyanogenmod) is against the mobile development business model, in English - just pissing against the wind. None of the major mobile manufacturers are interested to support old devices and focus only on growth through new models releases.

What bothers me is that Google itself is using the experience gained in the LOS development (that's according to Wikipedia) and they should maybe "return the favor" get a little more involved and help the LOS devs in fixing generic Android issues.
[Galaxy S3 Neo Original Android Development] josch85:
I read your post and I know that you appreciated the efforts of the devs. What I wanted to say is, that the developers are probably trying to finalize version 17.1 before they care for bugs on 16.0. I totally understand your point, that it's annoying that you report a bug and no one cares about it. I know the LOS manifesto, but how should you test that bluetooth is working? I mean there are so many devices out there with different bluetooth revision that you can't test everything. If they don't have any headset, then they can't test it. In the end you need automated tests. Google provides VTS (vendor test suite) on AOSP, but I don't know if you could use them on an old kernel. In the end LOS is a hobby/fun project as you call it, because no one pays money for it. On Cyanogenmod there where plenty devices supported by developers. Now the number of LOS supported devices is quite small. I think most of the developers lost the motivation to provide users with custom ROMs and hearing only when will I get a new update, new feature etc. Maybe they still working on ROMs but quit sharing them.

Well the major smartphone producer want to sell as many devices as they can. If they support old devices to long they won't sell new phones. In the end I don't understand customers playing that game. I mean buying a flagship smartphone costs a lot of money and you only get 3 years updates for it? As you see it on your S3 Neo for yourself, the hardware is still capable of running new android versions.

Google is interested in running as many phones as possible on new versions and they're ashamed that even KitKat is still running on let's say 10% of all android phones. That's why they no longer report how many phones are running a certain android version. But ignoring is the easiest way of dealing with the current situation. I will try to stay on the S3 Neo as long as I can. In case it breaks before a mainline kernel is running on new phones, I will buy one of the latest and cheapest android one phones. Buying a smartphone listed in LOS doesn't mean that it will be supported for a certain time.
[Galaxy S3 Neo Original Android Development] andriodking:
When will 17.1 arrive?
[Galaxy S3 Neo Original Android Development] asheesh131:
new updates for I9300I dual sim phones........https://mirrorbits.lineageos.org/full/s3ve3gds/20200418/lineage-16.0-20200418-nightly-s3ve3gds-signed.zip.....everything's working besides NFC....which is not included in the rom
[Galaxy S3 Neo Original Android Development] helloyello:
I just performed an OTA with lineage-16.0-20200420-nightly-s3ve3gxx-signed.zip and everything looks all right.

Looking over the changelog at:

https://download.lineageos.org/s3ve3gxx/changes/

Noticed that there were some Android Security Fixes in the Bump Security String to 2020-04-05 section:

https://review.lineageos.org/c/LineageOS/android_build/+/272560/

But then, noticed that Google released many more fixes, including platform related ones (Qualcomm):

https://source.android.com/security/bulletin/2020-04-01

Qualcomm:

https://www.qualcomm.com/company/product-security/bulletins/april-2020-bulletin

I believe I asked this already and haven't got a conclusive answer. Are those HW (Platform) security fixes, the ones that apply for the S3 Neo, ignored? I'm focusing on driver fixes, firmware files ... etc.

In the details of LOS 16 on my phone I can read - Vendor security patch level August 1, 2017 - what's that all about? Is that referring to the drivers/firmware?

Besides, I'm experiencing Bluetooth Input (microphone) disconnections even with the new Plantronics BT Headset. Usually somewhere between 20-50 minutes into the conversation, totally random and only in the Phone App. So, something is broken there (BT subssystem/drivers/PhoneApp) but I got used with it now, keeping the calls short - it's not a bug, but a feature ;)

And, there's a weird thing I'm experiencing in the Signal Messenger (Open Whisper Systems) - tried already a few versions back to the one I was using on stock ROM and was working fine, without success. In a video call, every now and then, I start to see macro blocks (to the extent that the whole image gets corrupted) on the video coming from my correspondent. It's pretty stable when the image is static, but it gets worse when there is a lot of movement (increased complexity/higher bandwidth (~1,5Mbit)).

In comparison, on an older Android phone I'm running stock and latest Signal release, everything works OK.

I believe it's something wrong in the decryption engine / Android - LOS16 subsystem.

Noticed that there were 2 fixes that were not merged in the latest Update and wondering if they are related?

https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/272360/

https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/272359/
[Galaxy S3 Neo Original Android Development] asheesh131:
i'm currently using this rom and i'm facing relatively low volume on the speaker during video calls and sometimes overheating issues too....are you having this kind of issues?
[Galaxy S3 Neo Original Android Development] Humaxxx:
As S3Neo is no longer supported by Samsung, there will be no newer vendor security patches. If you open "Trust" then you'll see, that vendor security is "outdated". . I already asked about that a dev in February. Here is his answer: It tells you the security patch date of the blobs. That we extracted from the stock. It says that they are outdated because the latest stock from were we pulled the blobs is like from 2017 if I'm not wrong.But we can do nothing as Samsung does not releases newer updates for the phone.
[Galaxy S3 Neo Original Android Development] Merftj:
My device: S3 Neo Duos i9300i

Rom version in use: s3ve3gds

Error: Photos normal; movie error, Msg: 'Error on camera cannot connect to camera'. To return to normal and use to take pictures, it is necessary to restart the device.
[Galaxy S3 Neo Original Android Development] helloyello:
Thanks for the quick reply. Not sure I understand what has Samsung here to do, given the vendor is Qualcomm. Now, even if the driver cannot be updated, at least the firmwares (blobs) should, as those are the ones filled with vulnerabilities that can be exploited from outside the OS (WiFi&BT&etc) and used to do really nasty stuff (kernel - root access & even worse).

AFAIK, from the normal Linux world (kernel), it is recommended to upgrade both driver and firmware, but you can upgrade only the firmware, because it's usually backwards compatible (with an older driver).

[MENTION=5087738]asheesh131[/MENTION]

It went warmer compared with the stock ROM before I disabled the overclocking, which, again, I'm considering a dumb decision. :eek:

Haven't noticed lower volume, but you could try increasing it in the Sound Settings for all outputs.
[Galaxy S3 Neo Original Android Development] helloyello:
I was investigating a little bit on the Signal Messenger issue I reported before - video getting corrupted and found some other, maybe related, issues with the Apps performance in LOS16.

I'm using OpenVPN on Android and the server is running on a Raspberry Pi2. The maximum throughput I can achieve is around 25MBit/s. Note that OpenVPN (due to security concerns) doesn't run multi-core, meaning only one armv7 core on both Android & Raspberry Pi is handling that traffic, on one OpenVPN instance, at 100% CPU usage.

I own another Android device having the exact same SoC as the S3 Neo (Qualcomm MSM8228 - quad-core armv7) that is running stock KitKat and the same OpenVPN client version, on which I can achieve the 25Mbit/s. On the S3Neo with LOS16 maximum OpenVPN bandwidth peaks at 13-15Mbit/s and it looks like the CPU isn't used at 100% (1 core).

On the S3 Neo running latest LOS16 I tried the following fixes without success:

- disabled firewall (afwall+) - didn't make any sense, since the same version is active and running on the other Android device

- disabled Battery Manager - fearing it could throttle the performance

- set the Device Performance from Balanced on Performance

- disabled my workaround to set the SoC on stock Frequency and left it overclocked (default LOS16)

- checked what CPU frequency governor is active on LOS16, learned that it was set on ondemand (should be OK)

and forced it manually on performace (root console)

- played in the OpenVPN config with different MTU sizes (useless too, but just wanted to be sure I ruled everything out)

And there's another performance issue I noticed in Firefox while playing Youtube videos (I only use Firefox and not the Google Youtube App). On stock ROM I'm able to play 1080p Youtube videos in Firefox without any glitches, whereas in LOS16 even 720p are barely watchable (looking like slide shows).

Preliminary conclusion, either LOS16 is eating too many resources and the apps are left with insufficient processing power, I highly doubt it, as it looks like LOS16 is light and fast, or, there are some throttling settings in LOS16 itself, not allowing Apps to use too much CPU power & drain the battery too fast. I wish I knew how to dig deeper, but both my Android skills and time limitations don't allow me.

If I can't get to the bottom of this performance issue , I'm honestly (and sadly) considering to ditch LOS16 and return to stock. :( Sorry, it's interesting but far too "unfinished"/"unpolished" & time consuming

Found out that the Eset Antivirus is light, good and still running on KitKat (running it now on LOS16 after noticing that the latest Avira releases behave like malware, eating battery and constantly trying to go online and tell Avira what's inside my underwear), I could substitute Avira. As for the rest of the apps I'm using, there are still newer versions supporting KitKat.
[Galaxy S3 Neo Original Android Development] asheesh131:
Fixed it...

[MENTION=10525319]helloyello[/MENTION] ya i've fixed it....i replaced the mixer_paths.xml from the stock rom and its working gr8 now...

the latest lineage build had bluetooth f/c's so had to download the previous build to run my phone normally
[Galaxy S3 Neo Original Android Development] Humaxxx:
Are you using the stock cam cam from Los 16? Can you take photos from front and backcam ? Was cam (video recording) ever working on Los 16 for you?
[Galaxy S3 Neo Original Android Development] Merftj:
Are you using the stock cam cam from Los 16? YES

Can you take photos from front and backcam? YES

Was cam (video recording) ever working on Los 16 for you? This was the first test
[Galaxy S3 Neo Original Android Development] Humaxxx:
Hmm OK, weird!

I dont really know how to help you. Did you a clean flash? Are you on latest baseband/bootloader? Normally i guessed that couldn't be related to that, but outdatet bootloader can cause courious behaviour...

As some first steps, you can try to

- make a backup and again clean flash the rom

- use another cam app
[Galaxy S3 Neo Original Android Development] helloyello:
Related to my performance observations and investigation from some posts above, I've been trying to figure out if the LOS16 binary code is actually optimized properly for the S3Neo SoC.

I have some experience with compilations on the Raspberry Pi ARM SoCs and both the toolchain (the latest GCC8 & GCC9 have also great optimizations and performance improvements for the ARM platforms) and the compiler flags that I use for both C & C++ - respectively: -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard (basically telling the compiler to use proper platform code, enable NEON SIMD (if available in the source code) and produce HardFloat code for the VFP), provide huge performance improvements.

I'm wondering if LOS16 is properly optimized when compiled?

I tried to investigate this myself, but the Microsoft Windows like crippled Linux called Android doesn't allow me to get too much info. The file utility is useless:

https://imgur.com/2ixxShS

I might need to take some binaries out of LOS16 and investigate the ABI & compilation optimizations on a full fledged Linux.

Anyways, I believe it's easier if the devs could check & answer these concerns.

The kernel is floating point "agnostic", which means no binary floating point instructions are generated during the build. But the ARM code (platform) - ARMv6/ARMv7/ARMv8/etc. is important and because of that only native builds (or, properly configured and capable cross-compilers) are advised - the toolchain needs to be able to produce platform specific code.
[Galaxy S3 Neo Original Android Development] Humaxxx:
I really think you should bring your knowledge/experiences directly to the Devs of S3Neo. But they are not here. The only "channel" I know for you to contact them are some telegram groups. If you don't like telegram I can ask if there is another way, if you want.
[Galaxy S3 Neo Original Android Development] helloyello:
I believe it will suffice if you point them to my posts. They'll read them and maybe take some actions / answer the concerns.

BTW, related to bluetooth, I' running now the fresh lineage-16.0-20200420-nightly-s3ve3gxx-signed.zip and today I got disconnected twice with the new Plantronics Headset, pretty early in the conversations - first 10-15 minutes by using the PhoneApp. Funny enough, now I was also unable to hear the other party and, while still in the call, I had to switch the audio in the PhoneApp on Phone and then back on bluetooth in order to make it work again.

So things have changed now, they got worse, I get a total audio bluetooth loss, both ways and not only the microphone, like before. :silly:
[Galaxy S3 Neo Original Android Development] Humaxxx:
Alright, I have pointed to the posts 732, 737, 742
[Galaxy S3 Neo Original Android Development] trancero:
Hello!

whats the overall opinion for this rom, battery wise and usual use?

Important! is otg enable? Would it be possible to connect controllers without using 3rd party apps?

Thanks a lot!
[Galaxy S3 Neo Original Android Development] Humaxxx:
In my opinion, this rom is good.

With set max cpu speed to 1190mhz I have a standby time of several days and sot of about 5 hours. It's fully charged in about 2,5 hours. Otg can be used with 3 party apps. But there are still "minor" bugs:

1) Charging prevents Deep Sleep (fixed after Reboot - until next time charger plugged in (LOS16 fully charge)

2) No Deep Sleep, when Wifi is enabled but not Connected

3) Glonass-Satellites are not used for location-services ( since Los 14.1, also for other devices like S4,S5)

4) Connecting to hidden network is not possible.

5) Casting screen via in-built-cast is not working - seems to be a generally problem of LOS16 - you can use 3 party apps.

And maybe some more bugs.

If you can life with these, it's a good rom. Otherwise LOS14.1 / AOKP is good and CM12.1 was / is really good, but older roms...
[Galaxy S3 Neo Original Android Development] Humaxxx:
[MENTION=1972627]helloyellow[/MENTION]

One guy on telegram group reported, that he have no problems with bluetooth - connection loss.

He told, he uses stock phone app like you. He calls for hours and have no (never had) problems with loosing connection.

So maybe you "freezed" some neccesary services? He is using this bluetooth equipment: Maybe you can compore the used chipset in your earphones and them

1) Boat - Rockerz 225

---------- Post added at 11:39 ---------- Previous post was at 11:04 ----------

Another guy is analyzing the wcnss crash issue, as bluetooth and wifi uses same chipset, it can be related...
[Galaxy S3 Neo Original Android Development] asheesh131:
i've been using it for a week now i have not face any big issues with Bluetooth or connecting problems....but i think battery drains a little bit more compared to stock and the phone too overheats sometimes...... it's definitely a great rom indeed
[Galaxy S3 Neo Original Android Development] Humaxxx:
Have you updated your baseband / bootloader before flashing LOS16? An outdated bootloader can cause overheating and other strange behavior.
[Galaxy S3 Neo Original Android Development] alexenferman:
Quick question,

Is this ROM stable? does offline charging work? Battery life is good? What are the unfixed bugs?

I don't have a s3 neo but I am planning to convert one of my dead US/CAN s3 with a broken display to a s3 neo with new screen with the neo board and frame while reusing the smaller parts that I already have. Is the s3 neo worth it or should I skip it?
[Galaxy S3 Neo Original Android Development] Humaxxx:
Look at #747
[Galaxy S3 Neo Original Android Development] trancero:
How did you flash it?

I did it through twrp and it failed. Have u also tried Lineage OS unofficial with android 10?

Cheers
[Galaxy S3 Neo Original Android Development] Humaxxx:
Update baseband/bootloader via flashing latest stock ROM with odin.

Flash twrp 3.3.1.1

Then in twrp do a clean flash.

---------- Post added at 08:10 ---------- Previous post was at 08:02 ----------

but

Many of your info is to "technically" for a "normal" user like me. But for you to better understand why there are problems with los16 is reason because the original drivers etc won't longer work with newer Android versions. So the Devs of S3Neo used sources similar phones... I think also froms5 mini. By the way yesterday arrived a new test build Los 17.1.
[Galaxy S3 Neo Original Android Development] asheesh131:
yes i upgraded my BB/BL yesterday..... everything's is good until now but was having problems while listening to music via my galaxy buds...music wasn't playing smoothly so i had to remove the rom's music player and i've instead pushed the pulsar plus music player and now it's working gr8 and super smooth
[Galaxy S3 Neo Original Android Development] Reedu:
After update to lineage-16.0-20200420 every time when i'm powering off s3 it's going into bootloop.

System cannot start even when i'm restarting it again through twrp.

I had to revert to lineage-16.0-20200325
[Galaxy S3 Neo Original Android Development] Humaxxx:
After reverting to 20200325, did you agin try to re-update?

I am on 2020-04-19 (Samsung - if you have Sony its the same like 2020-04-20 or do you have dual sim) . Everything is working fine.
[Galaxy S3 Neo Original Android Development] mariocaraf:
i also have samsung sensors and everything is fine with 2020-04-19, which is the same for sony 2020-04-20.
[Galaxy S3 Neo Original Android Development] Reedu:
Hi. I've got GT-I9301I with sony cam. It's single sim.

Previously i've used Lineage 2020-04-13 when problem first appeared. After it, i've tried to install clean version 2020-04-20 (two times really).

After powering down phone was in bootloop as before. Then i've done clean 2020-03-25 - now it's working properly.
[Galaxy S3 Neo Original Android Development] Humaxxx:
No

Hmmm, i don't know. Is your baseband and bootloader up to date? It should be:

baseband: I9301IXXUAPG1

bootloader: I9301IXCUARA1
[Galaxy S3 Neo Original Android Development] mariocaraf:
I with Italian firmware (I9301IXXUAPG1), the last one, I had continuous reboots, I tried the Greek firmware, and I no longer had reboots, it seems that the latest firmware are not all the same!