yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] dhiru1602:
Device Control app has an issue where it sometimes sets the maximum processor clock to the lowest. Make sure it's not the case.
[Galaxy S III Original Android Development] whoadood:
I am honestly not sure. Chrome uses a lot of RAM, right? So it's very very slow to launch and use. That makes sense. What doesn't make sense is that the mobile tries very very hard to keep other apps on the background while Chrome is running. I'd rather see those background apps killed (after all they launch in 3 seconds max...) than see Chrome crawling all the time just to keep everything in memory. I am not sure that's the issue though but this is the way I see it.
[Galaxy S III Original Android Development] rp158:
[MENTION=4893848]whoadood[/MENTION]: try NakedBrowser. Simply for testing.
[Galaxy S III Original Android Development] whoadood:
I know other browsers work well. I was mentioning Chrome as an example of an app that uses a ****load of RAM and CPU.
[Galaxy S III Original Android Development] Vix_Sk:
I have some random reboots when entering in apps this days...

Which is the best browser to use?

Edit: telegram doesn't send video with compressed option...it send the video in full quality also if i tipe to compressed
[Galaxy S III Original Android Development] dhiru1602:
We have already optimised the device as much as we could for ram usage. There is nothing more we can do. Aggressive process killing will affect battery since apps use more cpu if they are relaunched. Its pretty much the same story with all the 1GB ram devices.

Video upload works fine but there is a telegram bug which causes issues with video upload when shot in portrait. Send a video in landscape and it works fine even if you choose to compress it.
[Galaxy S III Original Android Development] Vix_Sk:
Nope same problem...i record the video with the normale camera..and then upload to telegram.. But it send without the compressed option
[Galaxy S III Original Android Development] Alcibiades:
Anyone having problem with low sound volumes? For me are pretty low at maximum. Any solution? Thx
[Galaxy S III Original Android Development] dhiru1602:
What's the size after sending? 1080p video is quite huge. It might be sending with compression after all..
[Galaxy S III Original Android Development] wjneto:
Netflix working???
[Galaxy S III Original Android Development] Vix_Sk:
I tried also other qualities 1080 720 360 telegram doesn't compress it...it sends the video in full size..it says that upload the compressed video..but after a few second it shows that it sends the video in full size...try you too
[Galaxy S III Original Android Development] Scorpionea:
Yes :)
[Galaxy S III Original Android Development] SamuelMaki:
I beg to differ on the already optimized remark. Zram really isn't useful at all on 1gb devices, the Android LMK is more than fine for handling the RAM. Slugginess ended once I flashed the suggested Agni kernel (stock based) and turned off Zram. I got severe swapping to zram even while using the settings before.
[Galaxy S III Original Android Development] jijishthomas:
Good work
[Galaxy S III Original Android Development] whoadood:
I also have a very severe swapping to ZRAM, which is the cause of the slugginess. I'll try to disable ZRAM and if that does not help I'll try that kernel.
[Galaxy S III Original Android Development] dhiru1602:
You don't need to switch kernel to disable zRAM. You can set the vm.swappiness to 0 to prevent swapping. You can make the change from the Device Control app under SysCtl / VM settings.
[Galaxy S III Original Android Development] whoadood:
Does "bootup restoration" work at all? Even if I configure it so it manually asks me to restore the configuration, swappiness is reset to 100.
[Galaxy S III Original Android Development] Noctis Lucis Caelum:
First time i ever tried NamelessRom, i have to say the experience is pretty good.

Very solid Rom.
[Galaxy S III Original Android Development] whoadood:
[MENTION=2875964]dhiru1602[/MENTION]

Just some theory here. Using the Google launcher.

Open WhatsApp.

Open Telegram.

Push the Home button, tap the Google search bar, search for something.

Tap on a result. Chrome will open. It will take it like 10 seconds to open and it will be sluggish as hell.

Go to the apps switcher. You'll see Telegram is still open, and WhatsApp is open too, maybe. (You tap on them and they just resume).

Go back to Chrome. Still slow as hell.

Go to the apps switcher. Manually kill Telegram and WhatsApp.

Go back to Chrome. You'll see it's much better.

So. Is 5 reasonable? Is it reasonable to keep those apps open even if that makes the front app, Chrome, unusable? You mention launching an app is slower and uses more CPU than keeping it in RAM. I disagree, I think paging an app into compressed memory and then uncompressing it is definitely slower and uses more CPU and it makes the front app unusable too. Is it worth it to keep so many apps in memory even if they do not fit?
[Galaxy S III Original Android Development] Gokulbalram:
I don't mean to sound mean or anything, but isn't it obvious
[Galaxy S III Original Android Development] dhiru1602:
Zram for low memory devices is a recommendation from Google: https://source.android.com/devices/tech/config/low-ram.html

Aggressive LMK will totally defeat the purpose of multitasking. What if you are typing a message to someone on Whatsapp and you happen to switch to Chrome to lookup something, just to realize that your friendly "LMK" has killed the Whatsapp app and you end up typing the message again. Imagine if you are playing a game and you happen to get a phone call, switching to the call, aggressive LMK will end up killing your game and you loose your progress. This is when the extra 300mb zRAM will really prove important. LMK is always a last resort to free up memory. It's not designed to be a primary memory management system.
[Galaxy S III Original Android Development] SamuelMaki:
No. 1GB is still medium RAM device, also who talked about aggressive LMK? Edit the LMK to not close the background processes (when you switch with home-button), but close the empty ghost apps instead. I have never had LMK killing the last 3 used normal apps or the last two if counting games. Of course if you insist on running games that eat up all RAM, you are just using this phone for something out of its performance window. Not to talk about the game slowing to crawl if you use 100 swapping ZRAM while gaming...

All in all, there should at least be a working toggle for that if you insist on it. For me it did reset on boot and I don't think it got even deactivated in the first place (no unloading happened).

Unrelated question, F2FS tested to be working?
[Galaxy S III Original Android Development] whoadood:
https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1

Check the "Memory Optimizations" part*, but take into account KSM makes the camera stop working. Maybe you can fix that too?

* I know it tells you to enable ZRAM, maybe a diff configuration works better.

In that case, WhatsApp or that game are poorly coded: app developers should know the LMK can kill any background app at any moment. If they don't store the current state in permanent storage, they're looking for trouble.
[Galaxy S III Original Android Development] shephart:
Rom is great but i noticed some lags, and sometimes phone just reboot and bootloop all time. Cleaning cache help and phone normally work for a while.. Any ideas?
[Galaxy S III Original Android Development] Scorpionea:
Im using 0328 build ever since it was released and not a single issue so far and most importantly no random reboots at all

If u have some issues then leave logs or else no one can help u
[Galaxy S III Original Android Development] Darius15:
Hello guys...first time i want to thank you for this awesome ROM <3, second i have a problem...i can't connect to my mobile data...APN is ok, but i don't have internet...any help please... I'm from Romania and i'm using Telekom..Thank you.
[Galaxy S III Original Android Development] jose181877:
Amazing ROM, using now, i didnt see any bug (i dont use telegram, insta, facebook in this device) wassap works fine,

Only one thing, use a microsd that dont use in the phone in the instalation, the system detected a error with that SD, not with other,

Nice nice battery, it seen like aosp 4.4 battery

Using L speed and undercloking in 1200mhz
[Galaxy S III Original Android Development] azazello22:
Next time upload a txt/zip/doc/whatever-you-want or use a service like pastebin to post your logcat :)
[Galaxy S III Original Android Development] xpduyson:
I was thinking about put it in pastebin, but put the logcat in

make it easier to find the logcat error in google :D I was found some solution via logcat posted directly in xda.

ps: turned off ZRAM today, reloading background app is faster than waiting zram cpu compression process!
[Galaxy S III Original Android Development] monte22:
Just to confirm 28th is the lastest build for this nameless rom right ?? the download section shows only 28th build .
[Galaxy S III Original Android Development] whoadood:
Download Kernel Adiutor, in the Virtual Memory section set swappiness to 0 and ZRAM size to 0 and then check apply on boot.

I would not use the built-in Device Control app, it's very buggy.
[Galaxy S III Original Android Development] Scorpionea:
yes 28th is the latest atm
[Galaxy S III Original Android Development] whoadood:
Is it me or when you add or remove an account (like a Google account) the phone becomes completely unusable for ten minutes?
[Galaxy S III Original Android Development] lucas09pl:
I can't hear anyone at calls. Even changing the volume doesn't work. Installed another 6.0.1 ROM and it works perfect fine.
[Galaxy S III Original Android Development] Samsagax:
Nice rom I have to say. Stable, configurable, clean, fast as it can get.

Things I miss from CM 13:

- Enforcing SELinux (will it be always Permissive? Not a good practice I think)

- Daylight mode in Live Display (CM13 has it and it's working great)

- Battery modes (even CM12.1 had them)

With that sorted out, is a great rom
[Galaxy S III Original Android Development] xpduyson:
is this ROM have doze?
[Galaxy S III Original Android Development] sulacolinux:
I confirm.
[Galaxy S III Original Android Development] Scorpionea:
I've talked few times and didn't have any problems hearing other side

Did u call them or they called you? Cuz I didn't call anyone so maybe that is why I don't have issue
[Galaxy S III Original Android Development] lucas09pl:
I've been calling someone, nobody called me yet.
[Galaxy S III Original Android Development] Samsagax:
Where is the right place to request features and reported bugs?

There are some nice features that are missing from CM13.0 that are also easy to port.

Will this ROM have an OTA updater? The one it has shows as last update from 2015.
[Galaxy S III Original Android Development] Vix_Sk:
[MENTION=2875964]dhiru1602[/MENTION] some option aren't translated like on latest cm13 ..like WiFi tile
[Galaxy S III Original Android Development] SamuelMaki:
To answer myself, F2FS does not work with included kernel, however with Agni 5.99 it works for data and cache like in official cm13.
[Galaxy S III Original Android Development] yoahmad1995:
Sorry for off-topic but what agni kernel works on this ROM? I tried PureCM and ended with black screen.
[Galaxy S III Original Android Development] ASVP_MSFT:
[MENTION=2875964]dhiru1602[/MENTION] sorry for off topic and non related nameless question. I just want to ask first instead of running the risk of bricking. Someone in the cm13 thread suggested that if we transfer /libs/hwc and /libs/omx folders from nameless to cm13 that you'd have a fully working hwc over on cm13, which by the way does work. Do you think it's possible to do the same for cm11 being that it's a lower Android version and all though the files differ in size but they're basically the same names and such. Again sorry for off topic.
[Galaxy S III Original Android Development] xpduyson:
[MENTION=6869286]yoahmad1995[/MENTION] I'm using this one: http://xdaforums.com/devdb/project/dl/?id=16884, everything work great, form zram to f2fs.
[Galaxy S III Original Android Development] yoahmad1995:
Thanks!
[Galaxy S III Original Android Development] Gokulbalram:
I'm very curious to know what you will do with SE Linux
[Galaxy S III Original Android Development] whoadood:
For security reasons, SELinux must be set as enforcing. In fact, if I remember correctly, it's now a requirement by Google.
[Galaxy S III Original Android Development] Gokulbalram:
...

That's for manufacturers.
[Galaxy S III Original Android Development] whoadood:
And what's your point? A manufacturer builds a hardware device and a ROM. Just because these guys are only building a ROM it is magically reasonable not to have SELinux working?
[Galaxy S III Original Android Development] Gokulbalram:
No wonder you get a lot of storm from the CM users.

I don't see the point of SE for root users. It is the least priority for the S3 considering there are more things to be worked on right now.
[Galaxy S III Original Android Development] whoadood:
CM users are at the edge of a civil war over who can defend more the developer who can't fix their phones. Even some of the most veteran shills have started to attack each other now.

SELinux makes all the sense of the world even if you have root. You only give root permission to certain apps, but you definitely don't want somebody to take over your phone by sending a maliciously malformed message to you, for example. That's what SELinux is about.

And yes there's more stuff to work on, but that does not make having SELinux working properly irrelevant. It's of a lesser priority than having calls working fine (if they don't work as some users have said here), but it's not irrelevant.

And peace. Asking for a feature that makes sense is not criticising. :good:
[Galaxy S III Original Android Development] ParanoidA:
Yes! This ROM looks awesome. Unfortunately I have the same issue. Actually the only Marshmallow ROM which had working cellular data was Haxynox, which had other issues.

Anyone have an idea what I can test? Maybe different kernels or configurations.

I'm in Finland using Saunalahti provider which works on Elisa network.
[Galaxy S III Original Android Development] azazello22:
Well, why don't you fix these things by your own? We are waiting the perfect build from you.

...and try CM 13, it has working SELinux, funny...
[Galaxy S III Original Android Development] SamuelMaki:
I have Saunalahti as well, the fix is trivial. Rename the APN and remove the .fi part of it.
[Galaxy S III Original Android Development] dhiru1602:
SELinux is a being worked upon. It's not a priority for us at the moment because Enforced SELinux will just end up breaking more things, atleast on a temporary basis.
[Galaxy S III Original Android Development] Scorpionea:
If u wanna help then start with posting logs so devs can see what the problem is.

Also did u try toggle on and off airplan mode?
[Galaxy S III Original Android Development] ParanoidA:
Great, thanks! It's working now. Any idea if the .fi should be removed from the mms address also?

Wonder what haxynox did differently with apn, and if the changes could be incorporated to Nameless.
[Galaxy S III Original Android Development] SamuelMaki:
I haven't actually tried MMS, so can't say for sure.

The normal behavior was not to include .fi part, but somehow it changed on CM12 I think? Not sure why it has not been reverted.
[Galaxy S III Original Android Development] vinylmeister:
Does any one know why playservice draines three times more battery than display?
[Galaxy S III Original Android Development] DarkPulsar:
Can someone post lib files that fix video upload in cm13? I cants unzip by myself as rom contains dat file... Thanks in advance :)
[Galaxy S III Original Android Development] ParanoidA:
Seems like the MMS should probably have the TLD , so "mms.saunalahti.fi".

Wonder how it works. These should be retrieved automatically from the operator? Or are there also some cached lists included in the roms? I tried to figure it out searching github but don't really understand the structure.

Still seems lika a stable ROM, no further problems with it. Very happy :)
[Galaxy S III Original Android Development] whoadood:
They are included in the ROMs, although your operator can send them to you if you ask them. Some of them do it automatically when they detect you are using a new phone. But in any case if I remember correctly it will ask you for confirmation before storing and activating the new settings.
[Galaxy S III Original Android Development] Waancho:
Hello, i installed the rom but have no mobile data. The APN settings are correct.

What can i do to help you help fix the problemM
[Galaxy S III Original Android Development] UserName_K:
hi nice rom ;) , even if there is a bit lag,as all 6.0.1 roms(maybe it's time to change phone not rom xD) anyway can i use boeffla kernel,or another custom kernel on this rom?
[Galaxy S III Original Android Development] Scorpionea:
U can't use boeffla kernel , few people tried with no success ,most probably this ROM is based on AOSP,with some code from CM and that is why kernel won't work

Maybe with AGNI but don't really know
[Galaxy S III Original Android Development] UserName_K:
no one has tested yet? Agni is the best kernel for AOSP ROM?
[Galaxy S III Original Android Development] Waancho:
Found it

Hi, i found the source of the problem. I was using a nano card in a micro adapter.

edit: no its still not working

edit II: installed CM13, problem persists, now blisspop android 5.1, mobile data works again.
[Galaxy S III Original Android Development] lxender:
This rom work well with agni kernel. Everything working as it should. Non fc. Video uploading work too.
[Galaxy S III Original Android Development] whoadood:
Hello, any chance we'll be getting nightlies or at least a new nightly built by hand?
[Galaxy S III Original Android Development] deadmetaphor:
Anybody in India using this ROM? Are you facing any issues with GPS?

It connects quickly, but seems to have a problem maintaining the lock for more than 20 minutes
[Galaxy S III Original Android Development] linuxer2k:
Hi! My S3 has the SDS (Sudden Death Sindrome), is this rom have the fix code for it?
[Galaxy S III Original Android Development] Scorpionea:
Every custom or official rom since SDS fix was released has this code implemented into kernel
[Galaxy S III Original Android Development] kaviraj14:
Boot looping

How to remove the folder and where ?

I'm new

---------- Post added 14th April 2016 at 12:02 AM ---------- Previous post was 13th April 2016 at 11:59 PM ----------

How to remove the folder and where ?

I'm new .. Bootlooping again and again ?

Pls help
[Galaxy S III Original Android Development] whoadood:
Using TWRP, there's an option called "File Manager", go to /system/priv-app/Velvet/ and remove the entire folder.
[Galaxy S III Original Android Development] Etsyo:
Can Snapchat's inverted color issue be fixed? :(
[Galaxy S III Original Android Development] kanu1and:
Charging Slow message on lock screen

I am also facing the same issue, my phone is not getting charges beyond 35%

I have tried 2 different batteries... its the same in both cases and tried with 2 different chargers... one is original I got with S3 and other one is the one I got with Note 4... both working fine with my Note 4... is there a solution for this error?
[Galaxy S III Original Android Development] whoadood:
Try the AGNi kernel.
[Galaxy S III Original Android Development] kanu1and:
Mate I looked for it... which version would work with this ROM? I could not find Agni Kernel for CM 13.... I did find for CM 11 and 12
[Galaxy S III Original Android Development] whoadood:
Yeah, the AGNi post is a clusterfu​​​ck. You need the last (topmost) one from here: http://xdaforums.com/devdb/project/?id=2502#downloads
[Galaxy S III Original Android Development] arminbih:
This new slither game freezes phone or boot loops it. Can't start it at all
[Galaxy S III Original Android Development] whatsgood:
[MENTION=2875964]dhiru1602[/MENTION] i tested video uploading with snapchat version 9.21.1.0 and rear camera videos uploaded fine, just the front facing camera videos gave that blue tint which is interesting. Not much of a problem for me as I never take front facing videos anyway.

Interesting to note: the latest version of snapchat v9.28.1.0 does give a blue tint with both front facing and rear facing cameras, so this may help in finding what changed between these versions to cause this blue tint to occur.
[Galaxy S III Original Android Development] madnutter:
Thanks for this solved the constant boot loop.

"Using TWRP, there's an option called "File Manager", go to /system/priv-app/Velvet/ and remove the entire folder."

---------- Post added at 08:16 AM ---------- Previous post was at 08:12 AM ----------

Only installed this last night so not sure how good the ROM is but so far looking good. As a bug bear why can i not get a signal bar? is there a fix?

thanks
[Galaxy S III Original Android Development] dhiru1602:
It's an issue with snapchat using the wrong color format. Not something that I can fix with the ROM. It's an app issue.

20 Minutes is quite a long time. GPS satellites are not geo-stationary and that's why you tend to loose satellite locks every now and then.
[Galaxy S III Original Android Development] deadmetaphor:
20 minutes because I'm either driving or tracking a walk on it.

But seems like Nameless is doing better, because it doesn't even get a lock in CM13 nightly

Thanks anyway :)
[Galaxy S III Original Android Development] virgo3456:
I'm still on Version 2.1. Yesterday I got a message that I can Update to 3.0 over the air. Is this really possible or does this end in a mess? I've downloaded the file but didn't start the update yet. Could you please make it clearer for me. Thanks in advance.
[Galaxy S III Original Android Development] ParanoidA:
I'd wait before updating

nameless-3.0-i9300-20160418 looks to be quite buggy.

Updating from nameless-3.0-i9300-20160328 to 20160418 OTA failed for me.

The boot animation takes some time to load and the animation runs very slowly at first, but does speed up.

After it optimizes the apps, I got a message "com.android.phone has stopped", and keeps giving the error after pressing ok.

After clearing all data from data/cache/dalvik partitions and reinstalling, it did start.

Camera did not work. The camera app just froze. A barcode reader app worked for a second, and showed the camera image before the app also froze.

Everything seemed a bit sluggish, but don't have any real data to support that so might just be imagining it.

Reverted back to nameless-3.0-i9300-20160328 which is working very well.

Except that the lock screen has screen rotation on, even when disabled from the menu.

Also my operators (saunalahti) apn setting were wrong with the superfluous TLD, but data worked once the apn was fixed.

But both those bugs are minor, and were also present in the new rom.
[Galaxy S III Original Android Development] JohnSmit268:
Today I installed nameless for the first time. I installed 28 March build. I couldn't boot it with gapps. It would stock on boot animation after app optimization finished. Without gapps it was fine. So sad that I can't use nameless. Any fix to boot it?
[Galaxy S III Original Android Development] whoadood:
http://xdaforums.com/showpost.php?p=66079367&postcount=8
[Galaxy S III Original Android Development] JohnSmit268:
Thanks. How did I missed that post?! I dig the thread for that!!
[Galaxy S III Original Android Development] dhiru1602:
Nighlies are now available. If you are switching to nightlies, please make a full wipe.
[Galaxy S III Original Android Development] lxender:
If already On your MM so we still need to full wipe?
[Galaxy S III Original Android Development] xpduyson:
[MENTION=2875964]dhiru1602[/MENTION] I have a problem with 0421 nightly: the Barcode Scanner inside Google Authenticator make the phone completely freeze, have to hard reboot. Logcat in attachment.