yashsingh1/xdaforums huggingface dataset:
[Galaxy S3 Neo Original Android Development] Humaxxx:
result is "ondemand"

look at screenshot 1

look at screenshot 2

LOS16 was on ondemand too, but since a few month it was changed to interactive

I flashed my Neo more than 100 times, before i swapped it with one of the devs. But always something can happen...
[Galaxy S3 Neo Original Android Development] Humaxxx:
Normally a sign that bootloader isnt up to date. But with your latest german firmware in background it should be ok..
[Galaxy S3 Neo Original Android Development] Humaxxx:
I have 2 Neos. One has a damaged display / or something else. Colors are displayed too bright, which is causing higher batterydrain. So i use this phone for testing purposes and currently running on stock...

I guess there is something wrong with this app in android 9. I tried this app with LOS16, and most times it showes 2-4 cores running, when doing nothing except having a look at this app?! It never shows only 1 core for me. Then i had a look at my normaly used app (franco kernel manager). This one shows me "correct" values

Dev told me, that they are using same interactive gov settings in his ported tw rom and los16. He tried on his tw rom, and cores 2-4 stays offline... I added his screenshot from his tw rom. He said, maybe some background task from an app causing your cpu staying at max?!

Another dev said that they were using stock values before and you can have a look into it at git history to retrieve them.

I also add 2 screenshot from my LOS16. Yesterday i got a Sot of 4 hours + 36 hours of display off. Today i test which Sot i got when using it all the time, without that much display off.

Its corious, i never got a hot Neo...

Screenshot 1: Is from the Dev using TW-Rom

Screenshot 2: if from me, using LOS16 and Simple system monitor

Screenshot 3 and 4: is from me, using LOS16 and franco kernel manager
[Galaxy S3 Neo Original Android Development] helloyello:
Got some time this evening to investigate and try to gather some logs related to the WiFi 2.4GHz & BT headset issue, where the WiFi simply disconnects when trying to perform a VoIP call through Signal Messenger or Skype Lite and using the BT headset as audio device.

I was using adb over USB and issued: logcat main while attempting the VoiP call.

First log that I captured in the adb console (filled the console buffer):

https://pastebin.com/EhmfbgBT

Second, extensive log - redirected the output in a file, where I believe I captured two VoIP calls attempts and WiFi disconnects:

https://pastebin.com/LG4EULPc

Legend (edit - changes):

ro:ut:er:ma:ca:dd - Router MAC

WI:MA:CA:DD:RE:SS - Phone WiFi MAC

BT:MA:CA:DD:RE:SS - BT headset MAC

org.thoughtcrime.securesms = Signal Messenger App

- hope I didn't forget anything else private in the logs :)

I couldn't catch anything interesting other than observing the WiFi disconnecting and reconnecting back. But maybe some more experienced eyes could find something conclusive (cause).

If there's a way to capture kernel / driver / firmware messages instead of the whole logcat stuff (pretty useless - too generic), please advise.
[Galaxy S3 Neo Original Android Development] steve8x8:
I've been asked to look after (and possibly upgrade to Pie) a S3Neo (I9301I) that currently has bootloader (and PDA) XCSAQE1, and baseband XXUAPG1. Cameras are Samsung type, S5K....

Will I have to flash stock?
[Galaxy S3 Neo Original Android Development] Humaxxx:
No, should be fine, just do a clean flash los16 Samsung cam
[Galaxy S3 Neo Original Android Development] helloyello:
Apparently using the ondemand governor didn't improve too much the battery life, but only didn't allow the phone to get hot.

- see attached screenshot battery,png

Screen on was 2 hours & 17 minutes on adaptive brightness inside the building (low light conditions). Stock ROM provides me almost the double of this battery life - maybe Android 9 is just eating more CPU cycles with all the developments (extra features) since KitKat.

But there are some other settings I need to check with the stock ROM - might need to flash again stock on the S3Neo.

https://github.com/LineageOS/androi...mmit/6f4f23e1127773c87db9e76a2e5e3820074fd5ec

https://github.com/LineageOS/androi...b/lineage-16.0/rootdir/etc/init.qcom.power.rc

These settings are really interesting - might need to put them on the values found in stock ROM (if available):

# Configure the hardware properly
write /sys/module/lpm_levels/enable_low_power/l2 4
# Update foreground and background cpusets
# Reserve CPU 3 for the top app
write /dev/cpuset/foreground/cpus 0-2
write /dev/cpuset/background/cpus 0-2
write /dev/cpuset/system-background/cpus 0-1
write /dev/cpuset/top-app/cpus 0-3
write /dev/cpuset/camera-daemon/cpus 0-3
# Configure the cpu-boost module
write /sys/module/cpu_boost/parameters/boost_ms 20
write /sys/module/cpu_boost/parameters/sync_threshold 998400
write /sys/module/cpu_boost/parameters/input_boost_freq 1094400
write /sys/module/cpu_boost/parameters/input_boost_ms 40
# Set RPS mask
write /sys/class/net/rmnet0/queues/rx-0/rps_cpus 2

Had the chance to test the GPS today and noticed that GLONASS is indeed shown, shown and not considered by any of the GPS apps I'm using.

The GPS Status & Toolbox app that I'm using on all my Android devices for some years now:

https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2&hl=en

Shows the GLONASS satellites with the rx (x - number) but apparently doesn't use/tune on them. Nor does iGO - the actual app I'm using for driving. I don't know if this rx is a standard for satellites naming and on all my older Android stock ROMs, the GLONASS satellites were numbered 65-96 (no r prefix). iGO and other apps are OK with the 65-96, but not with rx.

https://gis.stackexchange.com/quest...icial-mapping-of-glonass-satellites-to-prn-va

- attached picture: glonass.png

Finally, a feature that is not working - or at least I couldn't find a way to activate it - The Cell Broadcasts Emergency Alerts

Actually, I'm sort of happy it doesn't work - had enough of the daily stupid messages related to COVID-19

Under LOS - Android 7 (J3-2016) I can access and enable these Emergency Alerts (and they work) in Settings:

Wireless&networks > Emergency Broadcasts > Cell broadcast settings

- also available as section in the Messaging App (SMS) settings > Advanced > Wireless alerts

Under LOS16 - S3Neo I can enable them (don't work) in Settings:

Apps&Notifications > Notifications > Advanced > Emergency Alerts

- although the Cell Broadcasts App is available and has the permission to receive SMS

Just wanted to report this, don't really care about them.
[Galaxy S3 Neo Original Android Development] windmane:
Hi helloyello! Have you checked htop on your phone? I don't know if that's normal, but I had quite high cpu usage from logd service, therefore I disabled it. I followed the answer found here: https://android.stackexchange.com/questions/205818/how-to-disable-logd-logging

I deleted /system/etc/init/logd.rc because I didn't care (I needed to "mount -o rw,remount /system" first).

My battery is quite old and might not have it's original capacity - and I didn't bother testing it (actually because I'm lazy).
[Galaxy S3 Neo Original Android Development] Humaxxx:
I get easily 4-5 hours of SOT with simply setting max cpu to 1190. I dont change anything else. My Phone also under normal use with continous display on it dont gets hot or warm. Doenst matter if ondemand or interactive.

I only can say, that Glonass is fixed since (if i remember corect) july 2020. I tested it several times an it now works. But GPS was always tricky on Neo. I did really many tests. With Stock, Los14 Los16, also compared with S7 Stock, S4 Stock, S4 LOS. GPS needs a lead time on S3 Neo, using it the first time often needs hours for the first fix, then using it a few days, then after these days it gets its fix within a minute. I guess on Stock rom its (sometimes) much better (even with gnss only) , because i think its using an service from google or something else, which is not used by LOS. With LOS and Gapps and enabled all gps features i got a fix wihtin seconds... I also used gps test, sat stat. And glonass was working, didn't tried in the last month...

Haven tried this yet, but what i can say is that the german app "corona warn" can send my these notifications. I got some in the last days...

But as i said i havent tried with your mentioned settings.

---------- Post added at 20:29 ---------- Previous post was at 20:26 ----------

For Gloanss, look here, its a ticket i opened
[Galaxy S3 Neo Original Android Development] Humaxxx:
Just tried GPS.its working, also glonass satellites are used
[Galaxy S3 Neo Original Android Development] Humaxxx:
Here is a nice thread, maybe its helpful for you.

I use 1190mhz a long time, no lags if you do normal use / tasks. Sometimes i think (but not sure) if browser is a bit laggy. But try at your own if its ok for you...

Yeah GPS on Neo was always a crappy... here is a nice wiki - entry about time for first fix, it good to know.

I never noticed this function :) its enabled for me, but how to test if its working if its not working?! is there a way to force a message this way? I can use my other Neo to check wirh LOS14 or another custom rom

I Wrote in telegram group
[Galaxy S3 Neo Original Android Development] Humaxxx:
Dev said this is only in OFFLINE charging. When doing online charging governor don't change.

I still think talking directly to the devs would be more productive and you will get better answers / help
[Galaxy S3 Neo Original Android Development] helloyello:
Thanks for the link! Very informative, it'll definitely help me in my quest for balancing performance/battery life.

Thing is, according to htop, there are several core processes (audio & UI & sensors & co) in Android 9 that each are eating 2-3% of CPU when the screen is on, summing up to around 20%. These processes on stock KitKat and the other LOS (Android 7) I play with are way lower, summing up to 4-5%. The standby on LOS16 looks linear - OK, it's just when you turn the screen on then all those core processes are starting to load the CPU & drain the battery. Maybe Android 9 (with all the developments & features) is inappropriate for such old devices with smaller batteries - nowadays all phones have a ~ 3000mAh battery capacity, and, maybe Android 7 would do a better job. Unfortunately, Android 7 is already EOL and doesn't receive security updates.

As mentioned above, lowering the highest CPU clock wouldn't bring too much IMO, other than maybe a few percent of extra battery life and definitely some lagginess when the phone needs to perform. The J3-2016 on LOS (Android 7) stays at 300MHz with only one core active on idle - screen on, LOS16 on S3Neo just keeps the core at 900-1400MHz with the high load caused by those core processes.

Actually, I disabled E-Mail & Calendar & Calendar Storage & Exchange Services (they were greenified previously) and it looks to help with the battery life a little. I'm using K-Mail and aCalendar.

Thanks again! You seem very resourceful :)

Well, you cannot test it because it doesn't work in LOS16 and the stock KitKat on S3 Neo doesn't have it implemented (as far as I remember). And then you need to wait for the authorities to send an emergency alert - you cannot simulate it :)

https://en.wikipedia.org/wiki/Cell_Broadcast

I only noticed it on newer phones and on the J3-2016 LOS(Android7).

Thanks!

---------- Post added at 10:34 PM ---------- Previous post was at 10:28 PM ----------

Thanks for the details with the offline charging, makes sense.

I'm talking directly to the devs here in this public forum and specific LOS16 on S3 Neo thread ;)

Sorry to "abuse" you as the "courier". Don't bother if you don't have time, the devs might reply to my posts eventually.
[Galaxy S3 Neo Original Android Development] Humaxxx:
I also have deactivated some System-Apps which comes with LOS, such as Calender / Email, Phone, SMS, using my own favorites...

About Broadcast _Messages. I could use Android 7 (i stil have Backup of AOKP and LOS with Android 7) on my testphone, but as i have only one 1 Simcard , that wouldn't help.

But are you sure, there were some of these Messages in the last time?

About GPS. Its hard to compare. I compared my NEO with LOS16 with S7 with Stock, that was about before 6-8 Months. I tried in my house and my Neo has beaten S7 absolutly clearly, S7 didn't got a fix after hours, And s3 Neo was fast as lightning. But i also did other tests and there had another result. Last time i checked (about 1 month ago). Neo with stock and with LOS16 had no chance againt S6, S7, A5. They had their fix within 10 seconds. These phones can use more satellites, not only gps and glonass... If i remember corectly, they use beidou also. I also compared my two S4 with LOS16 (with broken Glonass), and they were also better then Neo. But using Neo, with gps on daily on, makes also a fast fix.
[Galaxy S3 Neo Original Android Development] helloyello:
Regarding Broadcast Emergency Alerts - LOS16 settings section looks to have only the filtering options available (what messages you want to receive) but misses the actual Broadcast Messages enable/disable menu options. Maybe the devs could look at this. Furthermore, it looks like LOS16 also comes with the necessary subsystem (running apps) for receiving these broadcast messages, it only needs to get enabled - missing setting menu option.

Forgot to mention that I haven't received these messages in Germany, but in another country...

https://www.t-online.de/digital/id_...phone-keine-tracking-apps-in-deutschland.html

GPS - on stock ROM I used the GPS often and I remember that it usually took 1-2 minutes to fix, compared with other devices that did it in 15-30 seconds. And I never kept it on the whole day, just enabled manually when it was required.

Battery Life - I got now 3 days with 1,2 hours screen on and 4 hours of voice calls, battery is at 20%, a little improvement, but still not comparable with stock ROM. Was wondering if there is an older, stable and fully functional LOS/CyanogenMOD based on Android5/6/7 that I could try (I think I could apply the camera patch). I only need at least the Android 5 API for making Firefox work and maybe I can get the desired "normal" CPU load in idle mode and better battery life. ON LOS16 the sleep mode looks good, it's just when the phone turns active, the fast battery drain occurs.

It's a single SIM I9301I Galaxy S3 Neo with a Sony camera, currently running s3ve3gxx LOS16.

On the WiFi disconnect while BT in use issue, I observed some funny thing recently and I don't know the cause but I suspect the core LOS16 is faulty.

Up until lineage-16.0-20200928-nightly or lineage-16.0-20201012-nightly-s3ve3gxx, when I enabled WiFi, the Signal Messenger background service would start automatically and I had to close it manually - annoying but expected behavior. Now it doesn't happen anymore with the WiFi, but instead, it happens only when I enable Bluetooth, like the Bluetooth is considered an available network adapter (ready to connect to Internet). Weird!

I didn't touch the LOS16 settings since March 2020, just performed OTAs and manually updated the apps, then made a backup with TWRP and always restored that backup. The only thing I tried recently (some weeks ago) was to activate and test the WiFi Hotspot on 2,4GHz, but that was for some minutes and never enabled it back. Could that have messed up the system and caused the WiFi & BT issues I'm experiencing?

Will try to see with logcat why is Signal Messenger starting when I enable BT. BT was never used for data transfer/tethering, but only for connecting audio headsets.
[Galaxy S3 Neo Original Android Development] Humaxxx:
Thanks for the link. Hmm, for me there is an option to enable / disable it (i add a screenshot) or do you mean another setting?

There was CM11 and CM12. Should be here on xda. But i am not sure if these are still working, because in CM12.1 (official until decembre 2016 - when CM was dissolved) was a bug which does cause a bootloop when using aapt2. If these bug does also appear in cm11 or cm12 then these roms are unusable. But for CM12.1 there was released a fixed rom in decembre 2017... I can provide if you want it. ALso LOS14.1 was a good one with some minor bugs. It wasn't official because developement goes on further on higher android versions. Also on this 7.1.2 Version there are a lot of on this rom bases roms. I also can provide. Each of them had the same bugs like los14.1 and maybe some minor bugs regarding to their own rom. Best Of 7.1.2 Roms for Neo was ( my opinion) LOS14.1 and AOKP. Regarding to CM12.1 for Neo the most known bug was that emergency calls are not working!. This is also on LOS14.1. CM12.1 and LOS14.1 also has known deep sleep bug (after charging - until you do a reboot). LOS14.1 Videorecording gives you white lines except a special build from June 2018. I also can provide this or newer rom with kernel from 2018-06
[Galaxy S3 Neo Original Android Development] helloyello:
Yep, apparently there is no section where "Cell Broadcasts" are mentioned - or - the emergency alerts actually referring to "Cell Broadcasts"

Took two screenshots from the J3-2016 running LOS (Android 7) - see attached.

Both S3 Neo (LOS16) and J3-2016 were sitting on my desk, on the same mobile provider, with the emergency alerts activated, and only the J3-2016 displayed them.

Actually I was looking to test the [ROM][5.1.1][OFFICIAL] CyanogenMod 12.1 for S3 Neo[LEGACY]

https://xdaforums.com/galaxy-s3-neo/orig-development/kernel-n1kernel-t3208957

But the download page is unavailable (broken):

https://download.cyanogenmod.org/?device=s3ve3g

LOS14.1 - special build from June 2018 - looks OK according to your descriptions, is it clean? Like, no stupid extra features and UI customizations - just clean LOS. Besides, LOS (Android 7) on the J3-2016 looks very good - stable and working very well.

Does it have a thread here on XDA? Just to have a look at the development and reported issues (discussions)?

I'd be thankful if you could provide a D/L link & a SHA256 hash.

Basically, I just want to try it to see if I get better battery life & lower CPU usage while active & idle. Maybe I'll be lucky with the WiFi & BT issues (maybe even connecting to hidden networks works). Don't mind the deep sleep bug - it's also on LOS16 and i got used with it - restarting after full charge.
[Galaxy S3 Neo Original Android Development] Humaxxx:
Ok, i have a look at it and give it to devs. Dont know if its a problem with LOS itself or according to S3Neo.

Yes this is CM12.1 Build

Yes, because CM Website is offline since CM was abandoned in decembre 2016. But doesn't matter because these build wont work good anymore since a about 2017 because new Apps were build with "aapt2" which is causing bootloop after installing an app which was build with "aapt2"

Here is link from new build from 2017-12-23, uploaded to android file host by PythonLimited (Main-Dev of CM12.1 fixed build and LOS14.1)

Yes clean LOS 14.1, i also dont like customations...

XDA-Thread

Here are download links for 14.1 but build from 2018-08. These build will have problems with video recording (white lines in videos). Maybe in xda - Thread are other links. If you dont find needed builds, i cant upload some here, because i have backuped it on my desktop pc. But i cant provide a SHA256 hash.

BTW, LOS 17 is near to get official... With 17.1 you can connect to hidden network. They have to fix one bug before they can go official. I also can upload latest build here.

LOS 14.1 bug (which i remember...)

- time reset after reboot. You need to have a wifi or mobile data connection to get correct time / date... Otherwise i can provide a fix...

- Emergency calls are not working - no fix! (Also CM12.1 has this bug)

- Deep sleep bug (after charging a reboot is needed...) (Also CM12.1 has this bug)

- Offline Charging

- NFC (of course - its only working on Stock rom and stock based rom)
[Galaxy S3 Neo Original Android Development] helloyello:
Good news! Hopefully it also doesn't eat 40% of CPU in idle mode, like LOS16.

Well, with Offline Charging not working that's a No Go! For the rest I might have some workarounds, but depleting the battery by mistake and unable to recharge it is really bad. In the LOS 14.1 thread I also learned that the WiFi Hotspot doesn't work.

Again. if LOS17 has the same high load on CPU and the resulting short battery life, then maybe the devs should focus in fixing LOS14.1 (if that is easy on CPU & Battery, much like the LOS14 on J3-2016) and stop further S3Neo development. As said before, I suspect, Android 8/9/10 are inappropriate for these old devices. I mean, they work, but they kill the CPU&Battery and render the device useless - 1 day battery life under normal (slightly heavy) load is scary - literally :)

I'm always "obsessed" with checking how much battery I have left on LOS16 - does it last until the end of the day ? :)
[Galaxy S3 Neo Original Android Development] Humaxxx:
You can check, by yourself. Download

Only one reported bug (but till now only a few testers...). WhatsApp Videocall doesnt work correctly, but it doesnt seems to affect other apps with video call.

If i remember correctly it was fixed with Toxi Kernel

No thats not possible!. Broken offline charging only means, that if you turned off your phone and plug in the charger it boots up. To be clear.The phone always can be charged, but it will be always turned on, when charging.

Hmm, dont remember if thats true. We had this problem also on LOS 16. and it was easy fixable by editing wifi.conf file

I have always been in favour of making a Rom almost (all that is possible) too stable before venturing into a new version... but I think the topic is done. If all goes well LOS17 for the S3neo will become official in the next days and there are already testbuilds of LOS18...

i don't think, that devs turn back to LOS14.1...
[Galaxy S3 Neo Original Android Development] steve8x8:
Which app is this? I've seen some, but this one looks interesting...
[Galaxy S3 Neo Original Android Development] Humaxxx:
GPS Test
[Galaxy S3 Neo Original Android Development] steve8x8:
Indeed I had missed that one. Thanks for pointing me; I eventually got my old condor flying with GPS again - might have been an issue with one of the antenna connection pogo-pins. Now back to Neo business ;)
[Galaxy S3 Neo Original Android Development] HTC82:
Good morning, is possible to reduce the minimum screen brightness (except with the brightness bar)?
[Galaxy S3 Neo Original Android Development] dicamarques:
I've noticed that my wifi is a bit slow on this phone, even connected to 5Ghz i only get around 10mbps. Also the wifi randomly drops, i notice that when i have the phone on standby and turn on the screen, the wifi is off and reconnects... I dont have any powersaving features enabled
[Galaxy S3 Neo Original Android Development] raichu77:
Model: GT-I9301I

Baseband: I9301IXXUAPG1

Bootloader: I9301IXCSAQE1

Phone/CAM FW: E08QL (not exact value as in manual, but guess it's Samsung cam)

Being new to LOS, I am currently missing some information in the official install guide: Before flashing LOS, how can I flash the Greece stock firmware to update the bootloader to I9301IXCUARA1 for Linux OS?

The firmware itself has already been fetched via Samloader (repo), resuling in a zip itself containing .tar.md5 files - to my knowledge Odin format - (GT-I9301I_2_20180220102440_72jw8gnzla_fac.zip):

View attachment 5157083

I found this gist using Heimdall - which seems to be quite error-prone to me... Is there an easier way, e.g. with TWRP and adb sideload, as also shown in the install guide?

Appreciate any help.