yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] zarere:
Well I also used automatic updater and the zip is still there nothing is removed :)
[Galaxy S III Original Android Development] dzincha:
31.01 nightly is out. Any feedback?
[Galaxy S III Original Android Development] baltics:
Read today's posts ?
[Galaxy S III Original Android Development] zarere:
Well here it is again,as you can see it's not removed for me.
[Galaxy S III Original Android Development] zarere:
You are looking in different folder :)

It's in /data/data/org.lineageos.updater/app_updates/
[Galaxy S III Original Android Development] baltics:
I guessed I must have been. I will search again.?

[MENTION=7496936]zarere[/MENTION], turning off safe access in file manager enabled me to find /data/data etc. Thank you.
[Galaxy S III Original Android Development] Logan:
Go to root folder then data/data.........
[Galaxy S III Original Android Development] zarere:
https://xdaforums.com/showpost.php?p=70813886&postcount=270 ;)
[Galaxy S III Original Android Development] mosqa75:
Google play store is gone after last update. Updated from CM13 acc. to manual from first page. And WiFi connection is turning off and on again randomly.(also for public WiFi) never had this problem with CM13, I tried all CM 14.1 releases, but no success. Any suggestion?

---------- Post added at 04:15 PM ---------- Previous post was at 04:14 PM ----------

Google play store is gone after last update. Updated from CM13 acc. to manual from first page. And WiFi connection is turning off and on again randomly.(also for public WiFi) never had this problem with CM13, I tried all CM 14.1 releases, but no success. Any suggestion?
[Galaxy S III Original Android Development] ripko:
Yes, TWRP 3.0.2-2 is installed but I was talking about the internal updater which doesn't involve TWRP, right?

The internal updater shows me that a new version is available. When I click download it starts getting the file and at the end of the download I get an error message that says file corrupt or insecure.
[Galaxy S III Original Android Development] baltics:
[MENTION=1377065]ripko[/MENTION],Well actually the internal updater advises it only works if you have the correct recovery, otherwise you have to flash it manually.

Edit

Corrupt downloads often arise from a bad wifi or data connection. The file was not corrupt on my device and it was automatically installed
[Galaxy S III Original Android Development] Simon_29:
The updater is using the openrecoveryscript which needs to be run by a compatible recovery.
[Galaxy S III Original Android Development] mbdroidsony:
Is anyone missing enable onscreen nav-bar option?

I can't see an option to turn on navigation bar soft keys.
[Galaxy S III Original Android Development] mohand06:
Go back to pesci2k's 20161207 build then update with experimental and latest weekly. That's how I kept navbar always available on my system. Otherwise I'd have reverted to CrDroid.
[Galaxy S III Original Android Development] Simon_29:
Enable root and just add "qemu.hw.mainkeys = 0" to your build.prop which is located under /system and reboot. Btw google is your best friend
[Galaxy S III Original Android Development] davidvanwijk:
I didn't succeed in installing Magisk (to pass SafetyNet). Is this not possible? (after addonsu)

Verstuurd vanaf mijn GT-P7500 met Tapatalk
[Galaxy S III Original Android Development] qb74:
if someone would be generous enough to pop out of no where and fix hwcomposer for us so that the media playback bug doesn't happen, don't be shy, say hello and link us the fix:laugh:
[Galaxy S III Original Android Development] LuciferIII:
Not as easy as you think it is. But...that actually happened,we got the codes and stuff,now our maintainer has to finish it.

Go to page 253 and read, it can explain some stuff
[Galaxy S III Original Android Development] Noobkid77:
I decided to take the plunge and try out Ressurection Remix and I don't see myself returning to Los for lack of OMS support I wish LOS could get theming but it looks like a far cry for now. Ressurection Remix is where it's at and I'm sure it's the same for plenty other roms
[Galaxy S III Original Android Development] Hamx5:
If now whatsapp calls work, hw composer gets fixed?
[Galaxy S III Original Android Development] ryanpatel122296:
well like i said im kinda new and im new to coding so im not much good at it......the features i would like to request arent too hard and and simply but very helpful like

1. accidental touch prevention

2. pocket lock/mode

3. three finger screenshot
[Galaxy S III Original Android Development] LuciferIII:
Those 2 have nothing to do with each other.
[Galaxy S III Original Android Development] minealex2244:
2. I think there is an option for that but I'm not sure. You can use an app instead.

3. Use an app instead even if it is more simple to use the already built-in screenshot options.

1. Uhm... That's almost impossible. The user should pay attention to his/her fingers ;)
[Galaxy S III Original Android Development] renzreyes21:
Uhmm guys, if you want that screenshot tile just search "screenshot tile" on google play and download it.
[Galaxy S III Original Android Development] LuciferIII:
I think the whole point of requesting features is that you don't have to rely on third party app/mods.

ROMs are there to bring you Features, Customizability (Because this is android) and even a newer Android version with added Security.

Customizability is crucial part of a custom ROM, which LineageOS as one of the most popular one out there lacks imo.

Lineage has it's pros and cons.

Of course i am not forgetting that cyanogen gave us the best theming engine, but its sad that now we can't get OMS which is a pretty neat alternative.

Why not make an official thread for feature requests?

Ps: About that pocket lock screen security, if you double tap the lockscreen it turns it off. Maybe that works like a security feature? Dunno :silly:
[Galaxy S III Original Android Development] forkbomb444:
Here's a quick update on where things are at:

I'm still working on the hwcomposer. This is ultimately turning out to be a full rework of the graphics subsystem. Basically, with the release of the Nexus 10/Exynos 5, Samsung moved to using ION non-contiguous heaps for graphics buffers, which need an IOMMU, whereas on Exynos4 graphics is allocated in carveout heaps (i.e. allocating contiguous memory) - UMP, FIMC, or ION. The fact that the display wasn't using an IOMMU before means that there were some buffers which it couldn't handle (and so which couldn't be directly composed to the screen). This situation also led to some weird stuff in the camera subsystem which seems quite confusing - allocating ION buffers, but then just passing around their physical addresses, instead of the ION handles.

So in summary, what I've been working on is modernising our graphics stack to behave more like the one used on Exynos 5: So far, I've updated the framebuffer driver and the HW jpeg encoder. The back camera can take photos, but I'm still working on chasing some timing issues (or some kind of issue) when loading the camera firmware for the front camera - and then I have to fix the video encoders, and a few more issues with display timing - the IOMMU disables too early sometimes, leading to noise showing on screen, plus the screen initially show noise after the bootloader logo.

TL;DR: I'm still working on it. It's coming...

The source is on my github, under the 'staging/cm-14.1-ion' branches, but most of the exciting stuff (for now) is happening in the kernel
[Galaxy S III Original Android Development] minealex2244:
I totally agree with you. I see that LOS is following a "tradition" and if you want more features you should submit the code for review or to use another custom ROM. They will add only the most popular requested features. If there are only 10 users (for example) which want feature X they won't add it but if 200 users will want it then they will get to work.
[Galaxy S III Original Android Development] LuciferIII:
Good,now we need ~200 users to ask for OMS :D
[Galaxy S III Original Android Development] minealex2244:
There are lots of requests for OMS but the commits which are already submitted to add this support are still unmerged or abandoned. This is that "tradition". They like to use their implementations not the most common things like OMS. They want their own engine. They want to be unique.
[Galaxy S III Original Android Development] nazfalas:
I think it's more about being in charge over what code you're using. Merging in other projects also means relying on them not making mistakes/staying compatible or constantly fixing things on your end to stay compatible.
[Galaxy S III Original Android Development] bezner:
Re-installing gapps (uninstall -> install) made smoother and faster in my case. If you have some problems, try it.
[Galaxy S III Original Android Development] Mirajoo7:
Sorry for OT :o

Is the board of i9305 compatible for i9300?
[Galaxy S III Original Android Development] Tech0308:
No
[Galaxy S III Original Android Development] minealex2244:
I had found an interesting old commit (there are also modern commits like it) which adds Fast Charging to S4 LTE (https://github.com/ausdim/TW-kk-Edi...mmit/8df6f1e20ca2740482944ea33e975a8964dc8f49). I was always curious to see if that would work on our device. The main requirement of fast charging is an adaptive fast charging plug then the commit applied. The commit should come from another Exynos 4 device. :)

Edit: Found it here https://github.com/Pafcholini/Nadia...mmit/e784a3d59ff3d334c9d685f279393ca303d1396f
[Galaxy S III Original Android Development] LuciferIII:
Cool,can you upload it on review,maybe it gets merged
[Galaxy S III Original Android Development] sunny1234590:
I don't think it's the fast charging. It's just a way to charge your phone at a higher ampere. You can tweak this through Boeffla kernel too.

Also, it alters the charging speed when you connect your device to the PC.

Just that on Boeffla you need to turn the thing ON, in this it's already turned ON.
[Galaxy S III Original Android Development] minealex2244:
You are right. As Boeffla kernel is a custom kernel it already has some customisation for charging and voltages. This commit should help the non-Boeffla users to get this feature. It is not like a stock Fast Charging but it is something :)

---------- Post added at 07:50 PM ---------- Previous post was at 07:46 PM ----------

This is just a kernel customisation. I can't submit it but I can do an unofficial build with this commit applied. :) Also I'm not the owner of it. The owner should submit it.
[Galaxy S III Original Android Development] cobrarx8:
Guys, did you ever noticed that the S3 has a greenish touch. Don't know if this depends on the rom but you can try those values under live display -> color calibration:

Red: 95%

Green: 83%

Blue: 100%

For me the white value becomes more natural. Use your phone for several minutes and then reset all values to 100% to see the difference.
[Galaxy S III Original Android Development] LuciferIII:
You ever heard about that s8 screen red ish touch debate. They explained that every screen can be a little different. That probably applies for our device too.

I tried your settings out and it makes my screen look more like ,dunno, Arkam city .

But the white really looks a lot better
[Galaxy S III Original Android Development] minealex2244:
You are right. The screen is a little greenish. I used your settings but it still gives me a weird screen but if I choose R 90% G 83% and B 96% I get clear colors. Lol :) The problem is not found in the ROM but in the screen fabrication.
[Galaxy S III Original Android Development] aldrin3010:
Since our device uses an AMOLED display, that's normal. AMOLED displays use organic compounds which degrade over time as they're used. Also, the organic compound used to produce blue color degrades more than green, and green more than red. Considering the displays in our phones are about 5 years old, it's normal for them to develop a greenish or reddish tint because of higher degradation of the organic compound used for blue. I suggest you read about AMOLED degradation.
[Galaxy S III Original Android Development] lollo.21:
Hello everyone, will you enter the call recording key as in the Marshmallow Times?
[Galaxy S III Original Android Development] cobrarx8:
Thx for the explanation [MENTION=6332758]aldrin3010[/MENTION] :)

Btw I found some interesting settings for those of you, who like the LCD screen look with not so crispy looking colors. If you have boeffla installed under screen use for MDNIE mode and scene both 2 and make your colour correction depending on your RGB degradation.

With these settings my display looks nearly the same as my Z3's
[Galaxy S III Original Android Development] minealex2244:
This won't be ever included! In some countries it is illegal to record a call. In other countries you need to ask for explicit permission from the other person to record the call. There are apps which should work very good.
[Galaxy S III Original Android Development] lollo.21:
Perfect, thanks for the answer :)
[Galaxy S III Original Android Development] LuciferIII:
*Cough* The "Thank you" button *cough*
[Galaxy S III Original Android Development] minealex2244:
Here is an app which I used and was not intrusive https://play.google.com/store/apps/details?id=com.appstar.callrecorder

Also it didn't use so many resources (RAM memory) like other apps, no battery drain and no lag when receiving the call. Imagine having call recording feature added to LOS and then Police catching you with it. You will get a fine. Because of that they can't include a dangerous feature. (No fines :D )
[Galaxy S III Original Android Development] lollo.21:
Ahahah excellent, as soon as possible I'll try the app lol
[Galaxy S III Original Android Development] ryanpatel122296:
whats news and improved in todays build?
[Galaxy S III Original Android Development] AlecSpence:
Er, https://www.cmxlog.com/14.1/i9300/
[Galaxy S III Original Android Development] Nypan sr:
https://download.lineageos.org/i9300/changes/
[Galaxy S III Original Android Development] Kwyjib0:
Trying to sync contacts with an outlook.com account via exchange. Calendars and mails are working fine, but contacts do not sync with a clean install no matter what. Tried the last 5 nightlies, also with 2 different outlook.com accounts. Always clean installs.

When I setup a clean install, configure the outlook.com account and then update via the LOS OTA updater to the next LOS nightly it works fine and all contacts sync! What could be the error in this case?
[Galaxy S III Original Android Development] LuciferIII:
This probably won't be added to our ROM,but i will say it. There is a way to get Xposed on 7.1.2 unofficially. It requires for the ROM devs to make changes.

You can read it on xda news.
[Galaxy S III Original Android Development] minealex2244:
I like that this is just a simple patch to ART and app_process but unfortunately it won't work on 7.0 but only on AOSP 7.1.2 (so not even stock ROMs). LOS and LOS-based ROMs can include it but I think that LOS won't do it.
[Galaxy S III Original Android Development] hashus1:
Hi,

I full wipe my i9300 anda I flash lineage os.

But it doesn't see GSM operator(simkart or GSM card). Please help me!
[Galaxy S III Original Android Development] dana.marivani:
Hi

You must install the modem

If the serial is not intact In that case, you must backup EFS use
[Galaxy S III Original Android Development] hashus1:
I'm sorry I don't understand you.

Where can ı find modem file?

And How can I backup EFS use?
[Galaxy S III Original Android Development] Scorpionea:
Is sim card working on stock official rom? Try flashing back to Samsung ROM and see if u have the same issue
[Galaxy S III Original Android Development] hashus1:
It's working stock rom.
[Galaxy S III Original Android Development] minealex2244:
While being in stock ROM do an EFS backup, then flash LOS and see if the problem persists. If yes then restore EFS an wipe cache. The modem installation instructions are found here: http://xdaforums.com/galaxy-s3/orig...lies-i9300-t3272811/post70222395#post70222395

Also don't worry about a misstake in a statement ("EFS use").
[Galaxy S III Original Android Development] multiwirth:
Clean install some time ago:

Now it starts to lagg as hell again.

14.1-20170621-NIGhTLY-i9300 < not depended on this version.

I don't know why.

The UI isn't smooth, the animations aren't smooth.

In the past the laggs gone away after updating the rom but came back after short time.

I really can't understand why.

No heavy CPU load or something that could explain this behavior.

Unbelievable that I used this phone and this rom as daily driver... Now I'm on a HTC One M8 which runs very smooth on LOS.
[Galaxy S III Original Android Development] Hamx5:
I have the identical problem with this rom, and some previous roms like cm13. I don't know. Initally phone is fast, but after some weeks of usage phone gets slower despite at least the same apps and 2.5 GB of free internal memory. I tried cleaners app (ccleaner) and trim memory (trimmer app), but rom stay laggy.

EDIT: cpu and ram have a normal usage.

Why this happen?
[Galaxy S III Original Android Development] multiwirth:
I never had problems with CM13 was always great.

Slower than CM11 but this depends on the OS version.

Don´t know why.

On my One M8 the performance is like I expected.

After an update in the past it got a little boost but it never had any big lags or something.
[Galaxy S III Original Android Development] Hamx5:
Ok, but why a rom starts became slower without installing too much apps and having enought free memory? I really can't figure out? As I said at the beginning rom is fast and super responsive, then it became less and less responsive and, for example, using google maps became very annoying due to the lag. Neverthelsss ram and cpu usage are not high. I had this problem since cm12 (that was unofficial).
[Galaxy S III Original Android Development] Mirajoo7:
https://review.lineageos.org/181611

Is this related to hwc?
[Galaxy S III Original Android Development] Samofr:
Did anyone try the unofficial xposed ?
[Galaxy S III Original Android Development] Nypan sr:
https://xdaforums.com/showpost.php?p=73029407&postcount=2794
[Galaxy S III Original Android Development] lollo.21:
Personally i do not like it, crash apps and then i is not yet fully compatible with i9300, i did restore and i will be waiting for rovo89,

i hope before the Android O lol
[Galaxy S III Original Android Development] multiwirth:
I don´t know.

For me the device is fast as always but everything is laggy means low FPS system ui and so on.

Sometimes after unlocking the screen (standby) the laggs has gone but come back very fast.
[Galaxy S III Original Android Development] kutysam:
I realized that battery drain happens when bluetooth is turned on and off.

Do go to location settings and disable bluetooth scanning . it will help! the gatt service will be finally stopped
[Galaxy S III Original Android Development] ryanpatel122296:
I too have also experienced this and was wondering if maybe you have an idea as to why this is happening, also is there any possible fixes and if this will ever be fixed in the future.
[Galaxy S III Original Android Development] crisis_trustee:
Dear forkbomb444,

Could you make enable on-screen navigation bar for future lineage-14.1-i930 builds? :confused:

Thank you in advance! :cowboy:
[Galaxy S III Original Android Development] LuciferIII:
There are lots of tutorials that can guide you through that. Just use google
[Galaxy S III Original Android Development] steveengr:
Hello everyone , does anyone else use spirit2 radio?since i install lineageos i can't use the speaker to listen , only the headset.
[Galaxy S III Original Android Development] mohand06:
It works for me, swipe to settings and tick speaker. If that doesn't work, there's a workaround from the app creator: unplug a little the earphone (that works as antenna) so that it still keeps contact with the outlet.
[Galaxy S III Original Android Development] Drollach Gûntar:
Hi guys, this is out of topic.But is there anybody knows how to apply pixel icon pack on pixel launcher ? I'm using latest nightly.Thanks.
[Galaxy S III Original Android Development] minealex2244:
No.

---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------

For those of you who are having lag problems: Do not forgot that you are running Android 7.1.2 on a device made in 2012. That's completely normal. If you want more performance reboot from time to time, enable KSM with 100 pages per 0,5 seconds, enable zRAM with 400 MB. Use Kernel Adiutor for that.

Also clear cache from time to time (from the Settings app). The lag may come from the broken HwComposer so wait patiently for Simon to finish it. There are some commits which are waiting to be merged to get everything working.
[Galaxy S III Original Android Development] crisis_trustee:
Really? Could you give me any links? :confused:

P.S. I asked forkbomb444 about including on-screen nav bar in next lineage-14.1-i9300 builds.
[Galaxy S III Original Android Development] LKHN:
Here is Guide :)
[Galaxy S III Original Android Development] LuciferIII:
You are spoon-feeding him. Something like this can easy be found by anyone. Even someone not familiar with Android, If you have access to the internet it's not that hard.

---------- Post added at 03:41 PM ---------- Previous post was at 03:33 PM ----------

First, this is the i9300 thread, not the i9500 one

Second, our device has physical buttons(and the i9500 too), so we don't need the navbar. But it is included in Android itself, its easily accessible if you search around the internet on how activate it. Anyway, someone already gave you a link.(which imo is spoon-feeding)
[Galaxy S III Original Android Development] dev.xda:
Thanks to all the LOS people!
[Galaxy S III Original Android Development] Drollach Gûntar:
I've found the solution and i'm not a noob.Anyway thanks for your unneeded reply.Cheers.
[Galaxy S III Original Android Development] multiwirth:
Not sure about this.

I think it's caused by the broken hwcomposer and forkbomb's work on it.

As he said he has to do a lot of things to the graphics driver so maybe there's currently something else broken.

I tried to boost the minimal clock speed of the gpu from 160 to 300 Mhz so the gpu can not go under 300mhz but this didn't help.

You also need boeffla kernel to do this.

---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------

A very similar device does not have such lags.

It's the HTC One Mini 2.

It also has only 1GB ram, a 1,2Ghz quadcore cpu and adreno 305 gpu.

It runs an unoffical LOS 14.1 and there aren't such laggs.

It had memory issues in the past which causes unresponsiveness and freezes.

In all still a smooth UI.

It got Zram increased to 400Mb like the galaxy s3 has and some other devices too with 1 gb ram.

There's no reason for the laggs since the s3 has still a little bit more power than the HTC.

---------- Post added at 04:19 PM ---------- Previous post was at 04:09 PM ----------

You just have to edit the build.prop.

Add the line "qemu.hw.mainkeys=0" and do a reboot.

The build.prop is located in /system/build.prop

Open it with an text editor.

Look for an (root) file explorer which has an text editor.

Es File Exploree can do it but I wouldn't recommend it since it got adware in the past.

Only the pro version is useable but still not like the original version (before android 5.0 was released and the developer's switched to material)
[Galaxy S III Original Android Development] crisis_trustee:
Təşəkkür edirik, Baki! :good:
[Galaxy S III Original Android Development] ryanpatel122296:
hello guys my partition got corrupt so i wanted to know how to flash the pit file and if i flash it can i reinstall this rom directly on the phone without flashing the stock rom first and do i have to reflsh the twrp recovery?