yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] eskorpiao112:
He can't do that ...
[Galaxy S III Android Development] mcgi5sr2:
Hmm have you tried the boeffla kernel for CM12 with this? Effectively we are all now building off the nameless rom sources - Dhiru is a magician!

File manager is being worked on by the slim team, I will see what I can do about building one in. Not sure what your preference is but mine is light weight and simple

No latest set is a smash of both Slim and Nameless repos.

Additionally I am uploading latest version with working BT, seems to work well and be stable
[Galaxy S III Android Development] eskorpiao112:
Ahah nice, hope to see this working in the future :D. Maybe you will be the oficial mantainer to the both roms?
[Galaxy S III Android Development] Bodo_1:
it is also possible to install the settings from the slimkat like color picker for the battery,to thank you for your effort in advance
[Galaxy S III Android Development] Rodziac:
I am really enjoying SlimLP, thank you! It is fast, slim, boots easily....

Bluetooth started working after January 14 update, but wifi tethering doesnt seem to be working additional to the "Not Working" list in second post.
[Galaxy S III Android Development] andrescm:
It doesn't work. Acts like it's doing everything but if you exit and open the app again you find it did nothing.
[Galaxy S III Android Development] myshakugan:
You need to set selinux to permissive and then tweak your boeffla sound values, otherwise it won't stick.
[Galaxy S III Android Development] andrescm:
Thanks for the tip! I had no idea!
[Galaxy S III Android Development] thechosenone43:
Gonna download the latest build later and give you guys a feedback. Thanks for everybody for the hard work with this Rom :D;):thumbup:
[Galaxy S III Android Development] karfeef:
Camera working on the latest test build! Awesome work man, many thanks :D

sent from my phone
[Galaxy S III Android Development] thechosenone43:
How can i change the Selinux status to permissive? In devs Option theres no Button to change

. and with Selinux mode changer from Appstore it wohnt change :confused: thanks Buddy :thumbup:
[Galaxy S III Android Development] rp158:
[MENTION=6385792]thechosenone43[/MENTION]: in TerminalEmulator:

su

setenforce 0 {for permissive and 1 for strict}

Simple but gone after reboot.
[Galaxy S III Android Development] thechosenone43:
Srry for asking but i never worked with the Emulator ..what exactly i have to write in the Emulator? I wrote "su" and pressed enger.tgen wrote "setenforce 0" and enger again and rebooted but nothing happend. Plesse instructions
[Galaxy S III Android Development] myshakugan:
If you can't do it using terminal emulator, you can use kernel adiutor from playstore.

Kernel adiutor>plugin> download the selinux plugin and use it to toggle selinux status.
[Galaxy S III Android Development] VictorLapin:
Don't reboot. Type "su" -> enter -> setenforce 0 -> enter -> tweak boeffla sound settings
[Galaxy S III Android Development] softtechiez:
Camera working in latest build thanx..:thumbup:
[Galaxy S III Android Development] Ariano Ângelo:
As a mather of fact there is Galaxy S3's diferent from the others.

Enviado do meu GT-I9300 através de Tapatalk
[Galaxy S III Android Development] reVox_77:
Hi guys, I'm currently on [4.4.4] I9300 AOSP NeatROM v8.0st having been frustrated with CM Lollipop on S3 (Bliss, RR). Many issues: overheating, random reboots, terrible battery, bluetooth issue unless governer change before use, more. 4.4.4 NeatROM is excellent, blazing fast, 100% stable but I'm missing Lollipop.

As this rom is AOSP, is it stable with Lollipop? Will I have a better experience over a CM Lollipop? Is it worth moving over from 4.4.4. NeatRom?

Thanks for your time and direction.
[Galaxy S III Android Development] Gokulbalram:
Hey guys, could any Omni user let me know if this kernel works for you? Thanks
[Galaxy S III Android Development] NVD-INDIA:
How long for the first boot. It's been 30 minutes already and still showing the S with circle animation.
[Galaxy S III Android Development] NVD-INDIA:
Did a factory reset and then rebooted without re-flashing. Now it worked. Will try factory reset and flash again.

-------------

Did a factory reset and flashed again. Worked this time. Will check it out and let you know how it works. Thanks.
[Galaxy S III Android Development] Dragonfail:
SlimLP not working perfect... Soft reebots.. Not stable :(
[Galaxy S III Android Development] mgtroyas:
Clean install, latest Slim build. No problem detected until now. Smooth and perhaps terminal gets hotter than in previous builds.

I have a problem with Google Camera, when trying to do a panoramic photo it fails after 4-5 shots (I place the point in the circle but no photo is taken) and have to discard, then it fails on first shot. But this problem has happened to me on any ROM to some extent for months, so no ROM specific.
[Galaxy S III Android Development] Daniel Bostan:
has anyone tried a different kernel on slimlp 0.8 which actually works without bugs? I tried Archikernel 2.0.1 but when making phone call, I can't hear anything but the other person can hear me. Currently with slimlp 0.8 stock kernel, I'm getting battery life similar to kk.
[Galaxy S III Android Development] andrescm:
Small question: after setting selinux to permissive and changing boeffla sound values, do they stick after rebooting the phone?
[Galaxy S III Android Development] myshakugan:
If you use kernel adiutor to toggle selinux status and enable the 'set on boot' option, the boeffla values should stick. Try it out, it should work.
[Galaxy S III Android Development] Gokulbalram:
Whenever you boot, Boeffla always sets your custom profile (the one you use) on boot.

As for SE Linux on boot, you might want to check in Settings within the app.
[Galaxy S III Android Development] andrescm:
Thanks to both of you. I don't mind selinux reverting back to enforced, I'm just wondering if setting Boeffla sound one time will be sufficient or if I'll need something like kernel Adiutor to keep the new settings in place every time.
[Galaxy S III Android Development] myshakugan:
After a reboot, if the selinux gets reverted back to enforced, the boeffla sound app will also lose its custom hw equaliser values. To avoid that you'll have to keep selinux on permissive on reboot through the kernel adiutor app. If the selinux stays on permissive on reboot, the boeffla sound values will stick, you don't need any other separate app for that. Hope this answers your question.
[Galaxy S III Android Development] andrescm:
Thank you very much and sorry for the off-topic!
[Galaxy S III Android Development] ag43:
Constant reboots with latest test version.reverted to 0.7
[Galaxy S III Android Development] MachOlaf:
Problems with Phone calls and mobile networks

Hello

I was using Omni rom a couple weeks ago. But then i discovered that i can't search for mobile networks. When i tried to search it gave a error "Error while searching for network". So then i removed it and installed SlimLP just for the time untill Omni got updated. But unfortunately i hasn't been updated yet.

But when i was using SlimLP, everytime i got called the incomming caller had a robotic kind of voice. Does this problem still exist because i am now using a other rom and i would really like to switch back to Omni because it has a great equalizer.

Thanks in forward!
[Galaxy S III Android Development] andrescm:
Have you been fiddling with modems?
[Galaxy S III Android Development] MachOlaf:
No i dont think so. I am not sure how to do that, so i dont think ive done that. The only thing i have done is format the data, cache, dalvik cache and the system and then installed the roms so i haven't changed anything..

Verstuurd vanaf mijn GT-P5110 met Tapatalk
[Galaxy S III Android Development] andrescm:
The "modem" or "radio" is the piece of software that controls the wireless communications, that is, calls, 3G, wifi and bluetooth. People can flash a different modem via recovery. Some will provide better signal and others will cause trouble. If you consider it worth the hassle, I'd suggest you flash a stock image via Odin (for example the ROM that came with your phone when you got it). A stock image contains everything incluiding a modem, and if you flash the same ROM that came with your phone, you'll ensure this way you'll have a working one. After that you can reflash a custom recovery with Odin and then install Omni or SlimLP again via recovery.

In Settings -> About phone you can see your modem version under the "Baseband" section.
[Galaxy S III Android Development] MachOlaf:
Thanks for the information and the quick reply. I do want to give it a try but do you think it really necessary because i have done this like a month ago. This because my cache partition was crashed so i couldn't boot anymore.

My current Baseband version is "I9300NUEGND1" and on SlimLP the mobile network search works fine. Do you know any other solution's to get the mobile network search to work on Omni?
[Galaxy S III Android Development] AhmadMarikar:
Don't know if you guys are still looking into this but the last time that app was updated was in 2013 and it isn't by the same developer if I'm correct. Head over to the Boeffla kernel website and under the Downloads section for Samsung phones you get a download link right at the top for the latest Boeffla Config V2 app. As for your SELinux satus, I don't think you have to worry about it at all. I've flashed Boeffla on my S3 many times and it changes by it self once flashed.

Sorry for the off topic post!

Good luck!
[Galaxy S III Android Development] andrescm:
Just a heads up: Boeffla Config will only work if it detects a Boeffla kernel. Since SlimLP doesn't have such kernel (no matter it uses Boeffla sound, it still isn't identified as a Boeffla kernel), the app will point that and exit.
[Galaxy S III Android Development] mcgi5sr2:
Can you provide more information please. This is a developers site, for development, and I'm afraid posts like this don't help. I don't want to be the guy who says LogCat or it didn't happen, as I understand people have different levels of experience. A year ago building a rom off other peoples sources and taking a log was all I could do. BUT please provide more info about what is happening when you got a soft reboot, what you think caused it, whether you clean flashed, what the weather was like at the time, what you had for lunch!

Also there is a tab in the thread to report bugs, I would happily use it if people reported things there.

Thanks for the info, my phone gets hot when running graphically more intense apps like games, also when playing video for a while. I think this is to do with how we handle omx buffers (video codec stuff) and will learn more about it in the hope to improve our situation. I am no HW ninja though, and am back to work on my PhD in VR soon. So no ETAs and no promises of improvements on this anytime soon sorry.

No worries, its providing info to other users! Also I am interested to know how many people use this app and would prefer permissive builds...

See comments above about info...

Yes we have an omx issue until the latest test build which is floating around in this thread, or alternatively you can test it yourself here....

So I had the robot voice a while ago, but it only lasted normally for the first call. Since 0.7 I haven't had it once, I think whatever was causing it was in frameworks_av and has been squished.

As for Omni, sorry my bad. Omni haven't been updating at all recently, which leads me to assume they are now waiting for M source drop. This led me to stop building and adding in some of the marvels that may have been included in my Slim build. I think I know the commit for fixing the network search and will do a build again soon (probably the last Omni 5.1.1 one though). If I forget and you still want Omni 5.1.1 loving please remind me :)
[Galaxy S III Android Development] andrescm:
If it's a different ROM then absolutely not, you must do a clean install or else your phone will not boot. It's not a life or death matter, you'll still have your custom recovery to do wipes and try again, but you will lose time and data. Backup everything you need, then wipe system, data, cache an dalvik and then install this ROM. What you say is named a "dirty flash" and will only work if you flash a newer version of the same ROM (you'll still have to wipe cache and dalvik).
[Galaxy S III Android Development] VictorLapin:
In that case dirty flash should be fine. You may consider wiping /system along with caches, just to be certain.
[Galaxy S III Android Development] MachOlaf:
Thanks! I am looking forward for the update!

Verstuurd vanaf mijn GT-P5110 met Tapatalk
[Galaxy S III Android Development] Amachete99:
I am using the last version of omni. With a clean install.

Everything OK but the Bluetooth

But I do not get the Bluetooth to work...it does not link with any device..even the ones I had previously linked...

Do you have any fix for this issue?

I have tried

rm -rf /data/misc/bluetoothd/*

and

rm -rf/data/misc/bluedroid/*

But It looks like that my device is not able to "listen" any other device...I have reset bluetooth thought settings...but nothing..

Any other idea?...I need to connect my phone to my car-bluetooth as soon as possible!!!

Thank you

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] andrescm:
Mine works fine, and if you ask me, much better than in SlimKat.
[Galaxy S III Android Development] ag43:
What's the downside of permissive build?
[Galaxy S III Android Development] mcgi5sr2:
less secure
[Galaxy S III Android Development] ag43:
Will it allow exposed framework to work ?
[Galaxy S III Android Development] cokesucker:
Yes Xposed works.
[Galaxy S III Android Development] cokesucker:
Sorry I'm an idiot, i thought i was posting on haxynox.

No i couldn't get it to work on slim.
[Galaxy S III Android Development] mgtroyas:
SlimLP Rom is pretty stable but slower tan Haxynox and Omni, lot of lag when switching between Apps, seems to use a lot of RAM for system?

I just had a soft reboot, first since flashing latest versión several days ago, attaching logcat.
[Galaxy S III Android Development] softtechiez:
Hi,

SlimLP is very smooth and responsive.

My friend is on the latest slimLP build (i9300)and he is encountering lots of random reboots. I am attaching a log, this log was taken after the reboot happened. Pls see the log to find the root cause and if it is enough to solve the bug. Thanks.
[Galaxy S III Android Development] MachOlaf:
Thanks for the update! Omni runs verry good but only mobile network search still doesn't work.. Something that i can change manually in de system folder? Or anything else to fix it? Thanks in forward
[Galaxy S III Android Development] Ariano Ângelo:
Found a weird thing in SlimRom. In settings there is a LTE option...

And the network is weird. When I click in quick settings nothing shows. And in settings there is nothing too
[Galaxy S III Android Development] mgtroyas:
Just had another softreboot. I had just connected the pone to my laptop with USB debugging on, as I everyday do. Logcat attached. It was about 9:26.
[Galaxy S III Android Development] mcgi5sr2:
Can you let me know if its a clean flash, what kernel he is on, and whether he is using any non stock apps?

Aware of this issue, and will try and resolve it for the next build. Time is short atm though

What are you using to take your logs? I am gettings just text with no return carriages, makes them pretty hard to read.
[Galaxy S III Android Development] mgtroyas:
I'm using an app called CatLog. Seems the text is being saved with Unix style line break. if in Windows, open it with some text editor other than default notepad, i.e. Notepad++
[Galaxy S III Android Development] ag43:
0210 GPS not working
[Galaxy S III Android Development] softtechiez:
No its a dirty flash from previous slimlp build. The kernel that comes with this rom. He s not using any non stock apps like xposed etc. I hope this helps you.

I own a galaxy tab 2.7.0. Its been a month since i flashed slimLp.. Even with that device occasionally i get reboots.

I suspect it must be frm slimLP source..
[Galaxy S III Android Development] frazzmark:
Cannot see sdcard from MTP

Hi, has anyone got this problem? When i connect the smarthphone to linux ubuntu, I can see the sdcard, but for some reason it's empty. I have to choose "mount sd card" option in usb connection options menu.

BTW: this just happened on a cleanly flashed latest 0.8 build. Not gapps or other stuff.
[Galaxy S III Android Development] frazzmark:
Sorry, this isn't ROM related. Apparently.
[Galaxy S III Android Development] MachOlaf:
Good performance on Omni, camera didn't even crash once. Also did an antutu benmark test and had a good score if you ask me. Is there a fix for the mobile network search yet?
[Galaxy S III Android Development] mcgi5sr2:
I applied the known fixes in the last build, going to take some investigating to confirm what it is.

Get him to do a clean flash, should sort out the issues

Which rom, clean flash etc? How long did you wait for first satellites?

Busted for using windows while on XDA :). Thanks pal, I'll check logs on Linux :)

As some of you may be aware the source of M has been released. I have limited time as always to apply to this project, and although ultimately I will spend my time where I please....

Are the users here more interested in getting what could be a non fully functional M or tidying up what is left to sort out on L?
[Galaxy S III Android Development] ag43:
0210 build. dirty flash. no sattelites at all.
[Galaxy S III Android Development] svbarbosa:
Keep working on L. M will probably be too much trouble right now.
[Galaxy S III Android Development] mgtroyas:
Same opinion.
[Galaxy S III Android Development] rp158:
L needed 10 months to run fine on the most hardware. Have a look at the 1st M-Slim: if you see the same needles and as many as at L-start, I should wait 1/2 year and polish L in the meantime.

I'll use S3 still max for 1 year, thank to your and Gokulbalram's work. But if any hardware dies, I buy a new phone.
[Galaxy S III Android Development] myshakugan:
I would wait for M to get matured enough and in the mean time tidy up remaining things on L.
[Galaxy S III Android Development] Gokulbalram:
Why not both? ;)
[Galaxy S III Android Development] HammDefy:
A preview of M would surely be interesting, but for now i prefer a (nearly or better) stable L .
[Galaxy S III Android Development] Geddd:
Layers app got fc when I tried to open.

Btw, first time to use this rom. Thanks devs!
[Galaxy S III Android Development] mcgi5sr2:
Enable root in dev options. I'll post a special version of layers app that works correctly on slim soon
[Galaxy S III Android Development] svbarbosa:
Download latest version of xposed (75) .

It works.
[Galaxy S III Android Development] Geddd:
Same problem here v74. So does it mean that xposed isn't working in this rom?
[Galaxy S III Android Development] svbarbosa:
I have not tried it myself but saw the same problem in many threads and framework version 75 was the solution. See this.

It is working with Slim 0.9 hlte - check this post.
[Galaxy S III Android Development] SteStanich:
tested V75 on slim 0.9 right now, it never boots..

if anyone succeed in booting up please share the procedure.

thank you
[Galaxy S III Android Development] mcgi5sr2:
anyone tried setting selinux to permissive?
[Galaxy S III Android Development] marono:
does anybody knows if there is a way to enable answer call with menu key and end call with power button on slimlp?
[Galaxy S III Android Development] mgtroyas:
Hi, just wanted to report that with the normal usage the SlimLP ROM settled after some days and now RAM usage is almost as low as Haxynox and the system runs lag free and without bootloops.

Yesterday I dirty flashed latest ROM 07-2134 and no problems at all, pretty awesome ROM, thank you for your effort.
[Galaxy S III Android Development] mcgi5sr2:
Awesome got an idea from those logs, I'll post a test build for you soon.
[Galaxy S III Android Development] karfeef:
How is everyone finding random reboots? Last test version seemed to start with 1 or 2 and then get more frequent

sent from my phone
[Galaxy S III Android Development] aaz03:
Hello folks, i'm here because i need some help , some kernel help to be more precise, I build slim for i9305 and i have this boot.img problem for a while : the boot.img won't boot, it gets or stuck or rebooting on the samsung bootanim. How did i do until today? I managed to get it working with bootimg tools: i decompressed the boot.img, combined new zimage with old working ramdisk (new ramdisks are always faulty) but now it doesn't work anymore.

Then i have this other problem, the --block based builds won't zip anymore i get a 6mb output, everything is ok when not --block but i'd like to know why.

Thanks to anyone who could help
[Galaxy S III Android Development] mcgi5sr2:
Using test versions posted in this thread or proper builds from the First Post (FP)? I don't get reboots anymore, so if you could grab logs or give more of a description about whats happening when it reboots could really help. :)

Where are your device trees? Are you using someone elses kernel, does theres boot? If your kernel booted before how come you haven't gone back to see what made it stop?

In other news MMS got fixed by [MENTION=3877985]prbassplayer[/MENTION] today, so I have included it in this build here for testing https://www.androidfilehost.com/?fid=24052804347833774, also if anyone has time could they test exposed again? I removed a lot of ART optimisation commits which I think were the cause for it failing before.
[Galaxy S III Android Development] Bodo_1:
Come now android 6 for the S3 slimLP?
[Galaxy S III Android Development] aaz03:
all of my device trees + kernel are on github.com/n0aaz

They come from Nameless plus some addings i made, they all used to work great until one day idk why it became a ****storm. I tried to go back when it started but no matter what i reverted it still had the problem. I saw that /system/core could influence ramdisk building so i tried reverting from there, still nope, same thing so i sticked with a mix of old ramdisk/new zimage and it worked quite great until today...
[Galaxy S III Android Development] mgtroyas:
After dirt install of last SlimLP ROM GPS cannot get satellites. AT all. Left overnight but no GPS location. I see some gpslib errors on logcat, attached.
[Galaxy S III Android Development] mcgi5sr2:
Looks like it might be about the dexToOat optimisation parameter. I'll have a further think about this as I like that feature...

Yea thanks for pointing this out. Messed up the vendor files, should all be fixed up now tho. Building new version now
[Galaxy S III Android Development] mcgi5sr2:
https://www.androidfilehost.com/?fid=24052804347834306

Now with extra GPS that actually works :)
[Galaxy S III Android Development] mgtroyas:
And GPS is also fixed, great as always is on the i9300. Thank you very much!
[Galaxy S III Android Development] jamesvinz19:
I like the smoothness of this ROM. However, Titanium backup won't work for me. It can't detect my root access? Any help out there?! :crying:
[Galaxy S III Android Development] simonwil:
I installed supersu from play store, updated the binaries and then all was good.
[Galaxy S III Android Development] jamesvinz19:
I tried updating busybox. Still not working.
[Galaxy S III Android Development] simonwil:
Have you also enabled root access for apps in developer options?
[Galaxy S III Android Development] mgtroyas:
Anybody has tried applying a layer? Layer Manager asks me to reboot but no change is made.
[Galaxy S III Android Development] mgtroyas:
I tried that method some weeks ago but it didn't work. Also downloading a theme from the Play Store which does the same. Today I tried it again using Layers Showcase app to find a compatible one just in case but also fails. Only wanted to know if there was some detail to know or simply it's broken at the moment.
[Galaxy S III Android Development] frazzmark:
Changelog

Where can I find the slimlp changelog? It would be really great if it was in the first posts, since I have to clean install every time I want to update.