yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] minealex2244:
Grant all permissions, don't use SD card and remember that Snap is still buggy.
[Galaxy S III Original Android Development] Ghorrim:
Hi everyone,

I did not find anything about this in the thread so far, so I'll just ask: On my S3 with last week's build (2017/03/22) I noticed that the Home button no longer works to close most apps, I have to use the "back" soft button instead (the one ot the right of the home button).

Is there a way to change this back? Is there a reason for this change? (Or am I the only one experiencing this...?)

Thanks in advance for any helpful reply! :)
[Galaxy S III Original Android Development] abelenki:
go to Settings/Buttons and set up any button the way you like it.
[Galaxy S III Original Android Development] LuciferIII:
That explains a lot, Thanks :D
[Galaxy S III Original Android Development] VVMM:
Some games (Two Dots, Dots and Co.) do not work anymore after updating to latest weekly build. They do start, but they are stuck at splash screen. Is this LOS related?

Can anyone test?
[Galaxy S III Original Android Development] mobratga:
Were i can Find The Link of EXPERIMENTAL Rom?
[Galaxy S III Original Android Development] AlecSpence:
The blog post from 20 Jan did say

"Given the EXPERIMENTAL nature of this [experimental update] process, we are going to remove this option in two months time."

While I'm sure there will be copies people have made, why not simply do a wipe and fresh install - always good to have a clear out...
[Galaxy S III Original Android Development] dana.marivani:
The next update is satisfactory Guys show substantial changes we feel
[Galaxy S III Original Android Development] minealex2244:
Can you tell me an example? :) I see only simple fixes, some exceptions handling and string fixes. If you are referring to the HwComposer related fixes then we need to be patient as forkbomb is not a robot, he is a human being and it will take around 1 or 2 months to see all the changes for HwComposer. :)

Edit: I see that forkbomb waits for some confirmations that the patch sets he uploaded are good for the Samsung devices implicated in this fixing process (the whole Samsung repository).
[Galaxy S III Original Android Development] dana.marivani:
Yes, I know he is an honorable man forkbomb many of them thankfull

I guess the things that I see

1-Better battery performance

2-Redundancy Radio

3-Sound quality

4-Fast menu

5-And heavy pressure control applications CPU

And probably in the next update to Android O = 8 near future
[Galaxy S III Original Android Development] minealex2244:
Yep, LOS will get faster and more stable over time, but keep in mind that Android O is 8.0 :D
[Galaxy S III Original Android Development] dana.marivani:
I'm sorry you thought was wrong, I edit text:eek:

I heard it

But I think andriod 7.1.2 the same Changes

andriod 8 :p
[Galaxy S III Original Android Development] minealex2244:
Android 7.1.2 is still a preview. I'm not sure what fixes it will include.
[Galaxy S III Original Android Development] stewazy:
Anyone else having trouble using the back camera in the Instagram app, btw I managed to solve the issue I had with the ring tones, I left the phone alone for a while android the next morning I had the ring tones, wierd bug.

Also just now mu Music died while I was connected via Bluetooth with my laptop, note it won't play any music and there is no sound.

Does anyone have any media service killer alternative, because the one on Google play store keeps telling me my phone isn't rooted even when I flashes su
[Galaxy S III Original Android Development] minealex2244:
Please do not kill mediaserver as it is very sensitive and you will need to reboot your phone in order to restore it's normal state. Killing mediaserver will result in no sounds at all! Your only alternative is to reboot the phone.
[Galaxy S III Original Android Development] tdcfpp:
You'll get it soon ;-P

https://plus.google.com/106192204376661856914/posts/eHKPHrBiZZf
[Galaxy S III Original Android Development] LuciferIII:
Ehhh wait just a second,did someone just out of nowhere gave us all we need to get a working hwcomposer!

Pls tell me this is real!
[Galaxy S III Original Android Development] sunny1234590:
Yes. Nameless ROM has always had the working HWComposer.
[Galaxy S III Original Android Development] tdcfpp:
Yes. I can hide well for some years when I want.

---------- Post added at 11:43 PM ---------- Previous post was at 11:42 PM ----------

First we had the blob working. Now there's no need to use a blob anymore.
[Galaxy S III Original Android Development] LuciferIII:
Simon abandoned a lot of commits.

https://review.lineageos.org/#/q/owner:"Simon+Shields+%3Csimon%40lineageos.org%3E"

---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------

Wait,you fixed it,and hid it ?

Y tho.
[Galaxy S III Original Android Development] stefan.slavici:
Great, so...what next? These commits have to be compiled, right?

Will there be a new Nameless thread?
[Galaxy S III Original Android Development] minealex2244:
Simon Shields abandoned almost all changes for HwComposer :) That means that he will possibly use the sources from Nameless ROM and our HwComposer will get fixed really soon. I think that there are necessary 2 weeks for that to happen.
[Galaxy S III Original Android Development] qb74:
i'll just assume someone has been working on reworking the camera hal in secret and will pop out with the sources, fixing the video call bug forever and making LOS 99% stable..

one can only dream. ;(
[Galaxy S III Original Android Development] LuciferIII:
You never know if life is just gonna trow something at your face.

Now you got a good example from the hwc.
[Galaxy S III Original Android Development] A n d r 0 i d:
Bluetooth Wideband

Hi all,

I've updated the modem to the recommended one but still can't hear bluetooth wideband calls, just get the robotic sound.

Narrowband works fine

i also tried "ro.ril.disable.amr.wideband=0" in the build prop to try and turn off wideband but this doesn't work either

is there a way of fixing this? either turning off wideband or some other way would be fine!

TIA :good:
[Galaxy S III Original Android Development] stewazy:
Where are the long press options for icons on desktop? I'm using the trebuchet launcher, also for some reason the phone won't recognise a flash formatted as NTFS
[Galaxy S III Original Android Development] tdcfpp:
Not really. I started two years ago and I've finished it a couple of weeks ago.
[Galaxy S III Original Android Development] Android-Banjarmasin:
Power saving mode not working, also when activated the auto power save to 5% etc, after a reboot power saving mode got malfunctioned, also the live display screnario not working anymore, and games constantly lag after 10 mins play
[Galaxy S III Original Android Development] tugay12:
Long press option is not available on Trebuchet laucher. You can use Pixel Launcher or others to get this feature.
[Galaxy S III Original Android Development] LuciferIII:
Oh well :laugh: . Thanks a lot for sharing! :victory:
[Galaxy S III Original Android Development] minealex2244:
Today, Simon Shields added a lot of new commits (HwComposer related, HAL, fixes). https://review.lineageos.org/#/q/project:LineageOS/android_hardware_samsung

He added HwComposer oss also :D
[Galaxy S III Original Android Development] DevisG79:
Hi@all. Could someone please help me. I don`t have a Galaxy S3. A friend flashed LAOS 14.1 latest nightly from 22.03.2017(clean flash) and doesn`t have root. Why? He also flashed addon-su-arm-signed.zip, but ended in TWRP with error 4. Is root already included in latest nightly? Or does he have to flash supersu? I am not new in the world of flashing and root but I don`t have this device and he lives in another city. Did I miss something?
[Galaxy S III Original Android Development] Scorpionea:
I haven't felt this good for a long tome ( s3 related stuff ;) )

Awesome news , hopefully some test builds could come around pretty soon
[Galaxy S III Original Android Development] mahe.:
Thanks mate.. [MENTION=2875964]dhiru1602[/MENTION] helped during cm12 time and your now in CM14. Finally we will get smoother UI and little more juice from battery with working HWC
[Galaxy S III Original Android Development] tugay12:
Nightlies are comes with root included. Just needs to be activated from Developer Settings.
[Galaxy S III Original Android Development] Logan:
S3 Legends are showing up from nowhere xD its nice to see this hopefully we see everyone team up with simon to build a beautiful art in cm14.

Thanks all :)
[Galaxy S III Original Android Development] DevisG79:
But in Developer options he can choose only ADB
[Galaxy S III Original Android Development] tugay12:
I just uploaded another su zip. Download it. A clean install is needed right now. Copy all files (ROM, gapps, su zip (mine)) to an SD Card and follow there steps:

Download su zip from here:

https://www.mediafire.com/file/h68gzq20ssizxvd/addonsu-arm-signed.zip

- Reboot into recovery

- Perform factory reset

- Flash ROM zip

- Flash GApps zip

- Flash my su zip (ignore any errors)

- Reboot

(And make sure TWRP 3.1.0.0 is installed)

I hope it works :)
[Galaxy S III Original Android Development] DevisG79:
Ok, I will try it at the weekend when I meet him.
[Galaxy S III Original Android Development] Stayka007:
Just ignore that error su is flashed correctly you don't need another root and no ROM only provide ADB root.
[Galaxy S III Original Android Development] AlecSpence:
There's been some misleading responses to your posting!

Your friend has done the right thing to flash the LOS 14.1 nightly followed by flashing addon-su-arm-signed.zip - ignore TWRP's error 4, we all get that. (this is all well covered from the i9300 device wiki)

The final step, which is probably all he's missing, is in Settings -> Developer Options -> Root Acess -> Apps only (or Apps and ADB).
[Galaxy S III Original Android Development] LuciferIII:
By "HAL" You mean Camera HAL?

And that means the video calls ?

Edit: uh well , i read its something related to cpu freq , not camera ,so nevermind,but still good news to see hwc being almost done.

Simon said he really wants to fix the video calls,so this will probably be his next work he will do. :fingers-crossed:

This ROM is gonna be the best thing that happened to this device. :highfive:
[Galaxy S III Original Android Development] ZjemCiKolege:
What do you mean "video calls" 3g sim ? or other i have G3 and HTC A9S this phones don't have video calls on stock or custom rom..
[Galaxy S III Original Android Development] dana.marivani:
Hi

I did not say major changes are going to happen. just look at what you wanted :)
[Galaxy S III Original Android Development] it'sup:
So what exactly is so special about lineage os? Battery life, flying performance, audio mods?
[Galaxy S III Original Android Development] stewazy:
New bug, I can't play videos in YouTube or Instagram or music after a while, I'm not sure what causes this problem

Edit: I have managed to reproduce the big. After paying a short video on Instagram and leaving the application, I can't play any music or videos on YouTube.

Another example, while music is playing try to play a video on Instagram, and the music stops, but the video on Instagram won't play. Also after that the music can't continue to play.

This is a huge bug, this rom is not stable
[Galaxy S III Original Android Development] minealex2244:
The ROM is stable. I didn't notice this bug but I see that your​ mediaserver is running out of memory. Just reboot your device and wait for HwComposer to be fixed.

---------- Post added at 04:56 AM ---------- Previous post was at 04:55 AM ----------

HwComposer will possibly fix the video calling problems but I'm not sure. It should fix it.
[Galaxy S III Original Android Development] stewazy:
I don't want to restart my device every time I want to swap between Instagram, YouTube and music. And btw every app that uses background is hybernated in greenify
[Galaxy S III Original Android Development] minealex2244:
Do not misunderstand what is memory :) As Android is written so much in Java then it will act like a normal Java :) That means that every process will get a specific amount of memory even if there is free RAM memory (that is the total free memory). This is called memory allocation and for example, mediaserver would get an allocation of 10,4 MB (it is not the real value it's just an example) and it will use 9 MB leaving 1,4 MB free then another process will leave 4 MB free memory from its allocation and so on until it will be more MB and you will see them in the Dev settings as free RAM. What if mediaserver uses its entire allocation? It will run out of memory and will try to restart but other processes are using it leading to another out of memory or a buggy service restart. You don't know which are these processes which are interfering with mediaserver but a reboot should solve the problem.

In conclusion, killing apps or hibernating them won't allocate more memory to mediaserver, only Java can do this. There isn't any command line for internal Java to manually allocate memory to a specific process. Hmm... That should change :) ...
[Galaxy S III Original Android Development] stewazy:
Anyway I didn't have this problem on cm13. I'm gonna try Omega rom now
[Galaxy S III Original Android Development] g104:
literally, i can play spotify, youtube, instagram etc. your s3 have issue not the ROM.
[Galaxy S III Original Android Development] LuciferIII:
No bugs for me either.
[Galaxy S III Original Android Development] stewazy:
Are you on stock kernel?
[Galaxy S III Original Android Development] g104:
i'm using boeffla beta 11 & i think stock kernel also working if not [MENTION=5405215]forkbomb444[/MENTION] won't released for nothing.
[Galaxy S III Original Android Development] Kinsoku:
Hello, i'm having frequent crashes on Facebook, Instagram, Whatsapp and they all happen in the same way. I'm attaching my log with my last crash with Facebook App. I'm using Boeffla Kernel but i had the same problem with the LOS kernel.

Also when i have to give root permission to an app that need to use my storage, i have to force stop that app before it can detect the files in my storage. I flashed the SU from the official LOS site and also gave me the error 4 in TWRP.

Thx for helping.
[Galaxy S III Original Android Development] stewazy:
I was not able to install Omega ROM, but I was able to install a backup of cm 13 and the phone feels a lot smoother
[Galaxy S III Original Android Development] mosheva:
Hi,

I was unable to use the OTG and MHL functions.
[Galaxy S III Original Android Development] Simon_29:
MHL does only work on Sammy based roms.

For me OTG is fine.
[Galaxy S III Original Android Development] Soffio:
Dose anybody know how to install Google camera?
[Galaxy S III Original Android Development] AlecSpence:
No longer findable within the Play Store, but still available there at this link.

There are newer versions, but they're specific to newer Google phones, like the Pixel, and will crash on an i9300, so don't bother looking for the latest version.
[Galaxy S III Original Android Development] Soffio:
Yeah I know, I have already tried.

Which version do you suggest?

Also, do you know which version cames with gapps' aroma installer?
[Galaxy S III Original Android Development] Jack Loos:
After update 22/3 and 29/3 Lineage, the app Super SU askes to update binary.

When I do that, and try to restart my phone, it stays on startscreen with green line and moving circle.

Made a back up by TWRP and after going back to backup, without updating superSU, everything is fine.

Any suggestions ?
[Galaxy S III Original Android Development] Gato177:
Only Flash for recovery SU 2.79 SR3
[Galaxy S III Original Android Development] AlecSpence:
I already suggested the version - it was what I linked to! It installs v2.5.052. No idea what comes with any other installers. But this one works perfectly well for me.

Why are so many people so keen to put on Super SU? Why not simply take the recommended route of flashing addonsu-arm-signed.zip? It works!
[Galaxy S III Original Android Development] Soffio:
Thanks, at first I didn't realized that I can download it ''officially'' from the Play Store
[Galaxy S III Original Android Development] LuciferIII:
Well,its hard to know its there,it doesn't show up in search.
[Galaxy S III Original Android Development] Deymos94:
- deleted
[Galaxy S III Original Android Development] stewazy:
Is the root bug fixed in the latest nightly?
[Galaxy S III Original Android Development] abelenki:
there was no root bug - it was always working fine. there's only error, when flashing addonsu-arm-signed.zip via TWRP, which should be ignored.
[Galaxy S III Original Android Development] Jack Loos:
Sorry,

forgotten.

Had SuperSU still in list of used apps.

Now removed it from Phone and list.

Indeed better use addonsu-arm-signed.zip, as recommended.

in developper: root acces: Apps and ADB.

Works perfect !
[Galaxy S III Original Android Development] stewazy:
It dumb that we have to flash su to get root, what happened to root, why isn't it like on cm 13
[Galaxy S III Original Android Development] LuciferIII:
You don't have to flash every time.(well if you are clean flashing the sys again,you have to do it)

Its better this way because some apps don't work with root. And not everyone likes root.
[Galaxy S III Original Android Development] andrescm:
Last time I read about this here it wasn't working, with the phone ending in a boot loop. But it was a long time ago, maybe you should try and report if you want to.
[Galaxy S III Original Android Development] baltics:
Let Google be your friend

https://www.reddit.com/r/LineageOS/comments/5pvkfl/encryption_failing_on_lineage_os/
[Galaxy S III Original Android Development] zarere:
This topic in reddit is for one plus phone and the last time I tried with unofficial 14.1 build I ended with bootloop that's why I'm asking if anyone is using encryption with this ROM.Thank you for your replies.
[Galaxy S III Original Android Development] Noobkid77:
This ROM is SMOOTH and runs like well oiled engine can't wait for theme support eventually battery consumption decent four hours on fairly heavy usage lasts about 8-10 hours but then again my S3 is 4 years old now
[Galaxy S III Original Android Development] baltics:
Well if it causes problems on one device, it probably does on them all.;

add

Maybe you could make enquires or post a request here.

https://xdaforums.com/lineage/help/features-lineage-cm-didnt-t3529538
[Galaxy S III Original Android Development] The10y:
Afrer installed this rom i cant log in to snapchat. I wonder is this problem caused from this rom ?
[Galaxy S III Original Android Development] TheBone_:
I think it could be a problem with Snapchat. You should wait until theres a patch for Nougat-Devices.
[Galaxy S III Original Android Development] baltics:
I just turned on whatsapp to make a call, and I was invited to choose whether I wanted to make a video call or voice call.
[Galaxy S III Original Android Development] evo_tr:
Ok i made a clean install with the nightly version for the first time on my phone. Everything looks working good but i get a pop up message; MTP Host has stopped error. Any idea why do i get this error and how to fix it?
[Galaxy S III Original Android Development] The10y:
İ dont think so because i've tried on other phone(nougat 7) and there is not problem. İ searched the poblem on google it says because of xposed but i couldnt find xposed on my phone.
[Galaxy S III Original Android Development] LuciferIII:
Aaand...?
[Galaxy S III Original Android Development] baltics:
I had not realised we could now use video in WhatsApp on custom rooted Roms. But my comment had some relevance to the comment about Snapchat. It will not be the ROM blocking it, will it?
[Galaxy S III Original Android Development] LuciferIII:
Dunno,i didnt try the video call yet cause i never call someone,but i had it for a while(beta tester).

Btw ,whatsapp is getting a snapchat like feature,you can try it out with "WA tweak" (not on play store,search on google).

I think you have to be a beta tester to get it to work,but maybe not :D

Edit: Tried video call,semms not to work for me,but i can see the video/cam from my sisters phone(not a custom ROM)

Dont know ,but i dont think its rom related
[Galaxy S III Original Android Development] Scorpionea:
Video call on WhatsApp is broken for our device,same issue with Viber video calls.

If u want video calls to work install cm11 or stock based roms
[Galaxy S III Original Android Development] matiasdelafuente90:
Since CM12.1 i never could use the video call, so i'm agreed with you, maybe it's rom related... I thought that this issue fixed in this rom but no :confused:

---------- Post added at 07:21 PM ---------- Previous post was at 07:17 PM ----------

I see... just for videocalls it doesn't woth go back to CM11. LOS Rules.
[Galaxy S III Original Android Development] umbrokhan:
in recovery i flash Pixel launcher, Google Assistant and Boeffla Kernel...

if i update Lineage OS to new nightly will i loose Pixel launcher, Google Assistant and Boeffla Kernel ?

when the new nightly comes out?
[Galaxy S III Original Android Development] Pasindu88:
If you dirty flash the new nightly you won't loose pixel launcher. Lineage OS is releasing weekly based nightly. So expect next nightly after a week from last release date.
[Galaxy S III Original Android Development] umbrokhan:
do you have to dirty flash Gapps aswell or just lineage OS on its own?
[Galaxy S III Original Android Development] Pasindu88:
Yea need to flash gapps and the kernel too, if you're using other custom kernel.
[Galaxy S III Original Android Development] minealex2244:
No need to flash GApps again.

---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------

You will loose only the Boeffla kernel because you flash the stock LOS kernel. No need to flash GApps again or any other system apps you installed. Also you need to flash SuperSU again if you previously installed it. The LOS .zip file will only patch the files which need to be replaced with the new ones.
[Galaxy S III Original Android Development] AlecSpence:
It's not so dumb if you have apps that need an un-rooted phone, such as many banking and mobile payment apps. At that point, it's actually quite a win. And there are many people who don't want/need root access, for whom it's also potentially safer to be un-rooted by default.

And it's hardly the most onerous process to flash an additional file once when you first install the OS.

The biggest waste of time is having to explain this to the people who don't read the initial information about how to install, and then wonder why they've not ended up with what they wanted. You can lead a horse to water...
[Galaxy S III Original Android Development] minealex2244:
First bug: I see that Facebook Lite (which I use too) is installed along with normal Facebook and this will cause the following error:

03-29 11:41:16.253 13493 13493 W UnifiedSsoLoginUtil: No appinfo found for com.facebook.katana

03-29 11:41:16.253 13493 13493 E UnifiedSsoLoginUtil: com.facebook.katana has no matching signatures

This happens because of a conflict between these two apps.

Second bug is known​ and I think it's AOSP related.

Third bug: Please search this thread next time before posting such a question. This was so discussed. Just ignore that error.
[Galaxy S III Original Android Development] Kinsoku:
1st) I just recently installed Facebook Lite but i already uninstalled the normal Facebook app. Also the same crashes happens with whatsapp and instagram too and also with other apps like mangarock sometimes, so they are all different and i don't see the conflict they could find... SHould i upload also the logs of the crashes with those apps?

2nd) ok and is there a solution yet?

3rd) ye i know i just wrote it because i tought the storage problem of point 2 was SU related.
[Galaxy S III Original Android Development] minealex2244:
1) That's really weird. Try a clean flash (it's not guaranteed but I see some suspicious EGL crashes in your log).

2) Nope.

3) Don't worry even if it shows you an error. I'm using SuperSU.