yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] Jamesyboy:
Devices are getting more and more capable....event more important, is google's recognition of the need for both CDMA and GSM versions of their Nexus line of phones. Its extremely hard for any company to support a policy that extends functionality or availability to a new segment of the market, and then take that functionality or availability away. I'd be hard pressed to believe that they'd move away from supporting GSM (the first standard they supported, one used widely across the world in relevant markets, and one they've continued to support from the first Nexus to the latest), and LTE, when its becoming easier and easier to do so. They did it when it was tough, and required different chip sets, and theyll continue doing it now that hexa band and up--radios are being manufactured. Companies already have their eyes set on supporting GSM and CDMA as well.
[Galaxy S III Themes and Apps] samuel583:
Does anybody know where the default browser icon image is located? I want to change Dolphin Browser beta's thumbnail to the default, because the icon for Dolphin doesn't look that great. Thanks.

EDIT: I found it, for anyone who would like to know it's in /system/app/Browser.apk, open it with a .rar viewer and navigate to /res/mipmap-hdpi/mdpi/xhdpi (depends on your phone), then extract ic_launcher_browser.png.
[HTC Radar] farooqjoyia:
HELLO XDA forum i need a video palyer for my wp7
[HTC Radar] DarkSeL:
Uhh.... Zune?
[Galaxy S III General] F1tty:
okay guys this is not the "real" fix but i think btw a beastly one^^ to get more info about this look trough the hole thread and read my posted link below!

all you do belongs onto your own risk!

New experience (Next Quote):

You also can read out here a bit: www.linuxsa.org

im testing if this command fixes the memory leak

go to an file explorer (Root required) and...

...you can find it in: system/etc/sysctl.conf and if you have no sysctl.conf see the Quotes:

open in editor and make:

vm.oom_kill_allocating_task = 1

vm.dirty_ratio = 50

vm.dirty_background_ratio = 20

vm.drop_caches = 1

vm.vfs_cache_pressure = 20

vm.min_free_kbytes = 153600

you can also look on the link below!

If you want more Info about vm tweaks look here:

http://www.kernel.org/doc/Documentation/sysctl/vm.txt
[Galaxy S III General] copponex:
Try to submit your fix to Gerrit and see if it gets accepted ;)
[Galaxy S III General] sangosnip69:
Nice work, i will try it and report back soon.

EDIT : I can't find the file in system/etc
[Galaxy S III General] F1tty:
who is gerrit? sorry but idk :D

ah okay know i found gerrit ;D

http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit

maybe someone can do this....cause im at work...
[Galaxy S III General] nerotix:
For sammy roms or for CM10?
[Galaxy S III General] F1tty:
this is a global linux command! so it should work on every version of android maybe some roms didn´t have this file and have to add them on another location or create that file...but this is a early fix so idk

i´m using 4.0.4 Slim ICS

This is a screen of my file:
[Galaxy S III General] mattiadj:
I haven't this file. Latest XXLG8

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III General] F1tty:
you can also add the command to your build.prop ;) you got none? ^^
[Galaxy S III General] mattiadj:
Thanks. Added it and reboot. Now let's see.

Also i have mod for swap

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III General] F1tty:
my ram is still stabil :) 260 mb of free internal ram
[Galaxy S III General] mattiadj:
I hope i can have a real multitasking and zero launcher redraw. I hate launcher redraw!

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III General] wbbigdave:
Correct me if I am wrong but the memory leak issue is only present on JB devices at present. This means that with your current ROM (4.04 ICS) you would not experience the memory problems anyway.

I am sceptical about the whole "fix" as it is anyway. As far as I can tell adding this to the build.prop would not do anything as this is only referenced by applications not the OS. Not everyone is going to have sysctl.conf.
[Galaxy S III General] davelinders:
I have the JB SuperNexus build but I wait until someone can confim that mermory leak is

really fixed with this fix.

But I dont noticed any memory leak on this build I used it the whole day and installed many things

and played a lot of games but phone is still freaking fast with 350+ ram free.

And I didnt rebooted.
[Galaxy S III General] F1tty:
Okay Sir but the OS kills Tasks if RAM is needed so it should work or am i wrong?
[Galaxy S III General] wbbigdave:
is the ROM you are running loading the file at boot? otherwise you are gonna need to sysctl -p
[Galaxy S III General] F1tty:
I also had faryabs jb tested but the issue came after 2-3 dass for me...
[Galaxy S III General] qwerty12:
EDIT: I'm an idiot. I thought this was the other memory leak thread.
[Galaxy S III General] wbbigdave:
I think the other problem here is people are assuming the memory leak is coming from games and apps installed. I have like 2 games installed atm and I am getting the leak with system apps crashing and restarting (namely maps by the looks of things, and i can only assume it is to do with positioning data)

OK just been doing some research this single tweak may help, but im wondering what other issues it may introduce.as i said before you will need to get your phone to run sysctl -p at boot, just add a script to init.d
[Galaxy S III General] F1tty:
So your talking about Google ;) so maybe they have to fix & update their apps... We will see
[Galaxy S III General] wbbigdave:
No as this does not affect official Google OTA updates or shipped ROMS (confirmed this is NOT a problem with my Nexus 7) it is something to do with the Kernel on the JB roms for the sgs3 as far as I know
[Galaxy S III General] jhericurls:
Well whatever its done by adding that code, its has worked for me. Normally after an hour of intense usage I would have no more free RAM.

After adding this bit of code, I'm hovering around 140mb.
[Galaxy S III General] F1tty:
Thats What it should Do :cool:

So all the Known kernelcookers had only to add this little **** :D
[Galaxy S III General] nfsmw_gr:
@all who has first heard of it!

This 'fix' is very old mates! :)

What it does is kill the process that triggers the out of memory status so our device can have more free memory!So basicaly it kills the memory hog and gives free ram,but sometimes it can kill other apps like browser!Not really important just to clear things out! ;)
[Galaxy S III General] F1tty:
I think it sort the tasks to kill by Priority levels...should not be a big deal
[Galaxy S III General] wbbigdave:
That's where you are wrong, instead of running through the lists of tasks open and determining the task to kill based on heuristics it will kill the memory hog straight out of the blocks (well the task which triggered the condition) if yo happen to be running this task then it's gonna die, but based on the fact a lot of Kernel Chefs use this tweak I'm gonna guess it won't

http://xdaforums.com/showthread.php?t=1621808

BOOM some explanations
[Galaxy S III General] F1tty:
Okay quiet better xD

I know that global linux command are Known ^^ but this works very well if it's to much for somebody He could add a cronjob to do this every hour...
[Galaxy S III General] rendymulandy:
have taested on CM10 unoficial build temasek..

and now my ram has free with 320mb.. and i'm not get memory leak problemm..

thankss ;)
[Galaxy S III General] davelinders:
Tested on supernexus it looks that it works.

Great work man.
[Galaxy S III General] reidar.ostrem:
Hmm, looks interesting. Have anyone run this through codeworkx and I heard what he thinks? Might give cm10 another try if it really works, I couldn't go 3-4 hours with cm10 before I needed to reboot.
[Galaxy S III General] F1tty:
I hope you can now handle the beast mode^^
[Galaxy S III General] mikebyrne316:
Should I enter this on any particular line in build.prop?
[Galaxy S III General] F1tty:
Should work but im not sure
[Galaxy S III General] Buddha123:
It should not work using build.prob. There is an alternative way: 1) create a script in /etc/init.d (if your kernel supports init.d) and set permission 777 2) enter this line: echo 1 > /proc/sys/vm/oom_kill_allocating_task
[Galaxy S III General] chadouming:
Don't want to burst your bubble, but this as nothing to do with the real problem. Codeworkx found the real problem and it's related to lockscreen. He will see if it's possible to fix it. DON'T BUG HIM WITH STUPID REQUEST, THANKS OR ETA'S ON THAT FIX. This thread should be closed.
[Galaxy S III General] EnemyOfGlaDOS:
What memory leak? I'm running stock based ROM with no issues. Maybe posting in the appropriate thread is a better idea instead of just posting in General considering this only pertains to guys using the unofficial JB builds. Just a thought.
[Galaxy S III General] mariosraptor:
I guess i can use rom toolbox to edit at kernel options

Edit: i added thid using rom toolbox pro. But apps are beeing killed almost instantly you are leaving them. This has no use in real multitasking cause our phone is not an iphone
[Galaxy S III General] F1tty:
Thread was moved by mod ;)
[Galaxy S III General] Safe0716:
Hi, added this code and it work's fine on RR Remix, Thank's

Cheers.
[Galaxy S III General] EnemyOfGlaDOS:
oh. :o :p
[Galaxy S III General] jnr21:
I quess that line need to be in that script too?:

#!/system/bin/sh
[Galaxy S III General] bangrahman:
Seems to be working to a certain extent. I had 49mb memory and after I entered what was said into the build.prop, my memory increased to 160mb as soon as I hit 'save'. So it is clearly doing something.

I'm running Faryaab's supernexus ROM and I will not reboot for about 6 hours and report back. Thanks to the OP :good:
[Galaxy S III General] F1tty:
i guess i have read it somewhere^^ nice to hear :D
[Galaxy S III General] Buddha123:
Not really. On my device, the default shell is sh already so I don't need to include shebang at the beginning of the script.

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

It is weird that you only need to click "Save" to make it work because build.prop will only be loaded when the system boots. So to be sure it is in effect, I think you should use Terminal Emulator and type this

sysctl -a | grep vm.oom_kill_allocating_task

and make sure you have this value equal to 1 on the screen.
[Galaxy S III General] bangrahman:
My apologies. It didn't work and I still have a memory leak. But I can't seem to find the sysctl.conf file in the directory indicated in the OP. Any help?
[Galaxy S III General] Mize:
This seems to be working well for me on the SuperNexus ROM. I used System Tuner Pro to create an init.d script for it (this is actually a built-in tweak for System Tuner Pro). Haven't had to reboot since. My RAM can get down to around 100 MB but I've had no fcs or stalled apps and no homescreen redraw. :good:
[Galaxy S III General] debenham:
The problem with this change is that the kernel will now kill the process that needs memory rather than the process which is using it all up.

This is often okay (since a leaking process is more likely to be asking for more memory) but if there is a leak in a foreground process and memory is near the limit - when you start another process it may get killed off because it was the one asking for memory at that time.

This would be most noticeable in the case of a slow leak.

This could result in thing as such as images not loading properly in gallery (due to mediaserver process getting killed instead of leaking process)

So although it may clear up memory a bit it doesn't really do it in the right way and may have odd side-effects
[Galaxy S III General] nilezon:
Agree. When reading up on vm.oom_kill_allocating_task, this really doesn't seem to be the best solution.
[Galaxy S III General] F1tty:
some people here say this is not the best solution! HAVE YOU TRIED IT? YOU SHOULD! btw the reboots of jb roms with leak issue are not a daily driver without this solution!

my phone runs like a hunted bunny so far! multitask is no problem ive never feel a loose of an app that ive started before!

how many multitask you need? my is up on a min of 10 - 15....
[Galaxy S III General] Mize:
I messed a bit more with it. Is does *not* stop the memory leak, it only keeps the system from going unstable by killing whichever process causes the out of memory error to throw. Things still slow down...
[Galaxy S III General] wbbigdave:
Hey guys, as an aside,

If you want to be able to use this "tweak" with your ROM then the best thing to do is create the file /system/etc/sysctl.conf then create a script called something like 10sysctl in /system/etc/init.d with the contents

sysctl -p

to ensure that you are definitely calling the file in question.

This will change the OOM kill allocation task with non zero meaning it will kill any process which triggers an OOM condition. (this is why the worry about killing foreground processes is brought up) pretty sure this will run on all ROMs and handsets, providing the ROM is set to use init.d scripts, which most of them are.

---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------

[/COLOR]if your ROM does not support init.d then http://xdaforums.com/showthread.php?t=1710980
[Galaxy S III General] F1tty:
ok your gonna think the right way...ass i read a little bit more about these "zombie" tasks and looked a little bit into startupp apps which must be one of them who killed the init process and cause these leak i find out that disabling any location setting like in maps, google now, market and any other my leak issue is definitly gone...but i believe it has more to do with google now and their now-maps.
[Galaxy S III General] :
google now is making some partial wakelocks with network location, but is not causing leak over here. I removed this fix, disabled lockscreen (as per codeworkx fix) and seems much better now, no need to reboot in last 2 days.
[Galaxy S III General] F1tty:
my lockscreen isn´t disabled..it definitly isn´t the process which kills the init!

Edit: Btw it must be a process wich has init as parent!
[Galaxy S III General] :
ah sorry, missed part of the thread.. was talking about something else.
[Galaxy S III General] filflame:
Good day, is there any easier way to fix this of a "noobish" how to please?

I am on paranoidandoid/siya/XXLF5 and I'm having a terrible memory leak. It reaches 0mb free.

Thanks
[Galaxy S III General] pushrodv8:
I keep hearing about memory leak...

...and I don't know what it is. I flashed CM10 since quite some time, and every day after some time of usage the launcher (default, usually Nova) starts flashing. Other apps start flashing too, and this only goes away when I reboot. Is this the memory leak? Note that I never checked the available memory (yet...)
[Galaxy S III General] Manar Aleryani:
Guys, Curious Question

If we keep the value of vm.oom_kill_allocating_task '0'

And change all the other settings, especially "vm.min_free_kbytes"

Will this fix continue to work without the risk of killing foreground apps?????
[Galaxy S III General] gavin-phelan:
Any fix yet these aint working
[Galaxy S III General] joshnichols189:
Don't you think the actual thread would let you know if there was a fix? And these work fine.

Sent from my GT-I9300
[Galaxy S III General] gavin-phelan:
Need a noobs guide
[Galaxy S III General] GabrielSousa:
on the last cm build, this dont work, we have a faster memory leak :(
[Galaxy S III General] filflame:
please a step by step how to guide for us noobs

Thanks
[Galaxy S III General] giajp:
We could have a more clear guide? It's a copy and paste of things. Don't understand anything
[Galaxy S III General] Daelyn:
If you don't understand these things, you really shouldn't fiddle with ROMs etc. anyways. You don't learn by having step by step guides, but, I'm feeling nice today.

Here's a way to do it which involves nothing else than using ADB. If you do not have ADB, then, go back to reading the stickies. Preferably twice.

First, check the file system. If I remember correctly some ROMs back in the day have /etc linked to /system/etc. Some ROMs use plain /etc.

adb shell
ls -l /

Here you're gonna look for a line that says "etc" in the end.

It could show in two ways:

drwxr-xr-x 1 root root 4096 Aug 16 21:26 etc

or

lrwxrwxrwx 1 root root 11 Aug 16 20:41 etc -> /system/etc

If you got the top one, you gotta remove all the /system/etc and replace it with /etc

If you got the bottom one you leave the commands as is.

Then, quit shell, remount system to Read/Write, open a adb shell and become root.

exit
adb remount
adb shell
su

Do it line by line to make sure all is well.

First step, remove your previous attempts.

rm -rf /system/etc/init.d/10sysctl
rm -rf /system/etc/sysctl.conf

Reboot your phone to make sure all is OK.

Then adb remount, shell and root again. After that, enter the following first to see if it reports any "fault"

touch /system/etc/init.d/10sysctl

No fault? Go ahead with these to make the init.d script

echo "sysctl -p" > /system/etc/init.d/10sysctl

To make sure, we reset permissions for root to own it, and root to execute, rest will have to live with read only access

chown root:root /system/etc/init.d/10sysctl
chmod 0774 /system/etc/init.d/10sysctl

Then create your sysctl.conf by doing this

echo "vm.oom_kill_allocating_task = 1" > /system/etc/sysctl.conf
echo "vm.dirty_ratio = 50" >> /system/etc/sysctl.conf
echo "vm.dirty_background_ratio = 20" >> /system/etc/sysctl.conf
echo "vm.drop_caches = 1" >> /system/etc/sysctl.conf
echo "vm.vfs_cache_pressure = 20" >> /system/etc/sysctl.conf
echo "vm.min_free_kbytes = 153600" >> /system/etc/sysctl.conf

To make sure, we reset permissions for root to own it rest will have to live with read only access

chown root:root /system/etc/sysctl.conf
chmod 0664 /system/etc/sysctl.conf

Reboot and init.d and sysctl modifications are done. Worth to note this just modifies the behaviour of Android. Does not actually "fix" the fault, just masks it.
[Galaxy S III General] giajp:
This is a guide :) thank u ;)
[Galaxy S III General] ksilver89:
Hi, first of all many thanks for the information.

I was using the same tweak on S2, but setting min_free_kbytes to 153600 always OOM system immediately, and then the phone will get into bootloop. I'm trying it now with 102400 instead. Memory handling was working very well now (just past 30 minutes after boot), during usage (web browsing) the memory dropped below 100MB, after I left it for idle, the memory recovered to 261MB. Definitely better than before, where the memory hovering around 160MB, accompanied by getting lesser and lesser cache, and eventually render the phone unusable.

Will continue to monitor it for the next 2 hours.

EDIT: Random freeze occurs at low memory (cleaning process?), browser got terminated and restart itself, settings might be too aggressive.
[Galaxy S III General] wilfred_hup1:
Thanx, working for me
[Galaxy S III General] btemtd:
oops wrong post
[HTC Sensation] K900i:
Hi, I wanted to restore my phone to stock as I am planning to sell it.

My settings are as follows.

Cid-HTC__01

Hboot-1.29.000

S-off

Htc sensation XE

Rooted.

Firmware latest - 3.33.401.105

I want to restore this can anyone give me LE version of The stock ICS RUU.

Please help me out!

Thanks

Is it possible to restore with the current set-up or what must I be doing , please suggesst some ideas thankyou
[HTC Sensation] ganeshp:
use this RUU

connect the phone from fastboot/bootloader and then RUN the RUU ..it will restore to complete stock
[HTC Sensation] K900i:
Hi, can you mirror it?

The download is extremely slow and I am not able to download it fully, the download keeps crashing even before its complete.
[HTC Sensation] ganeshp:
here is the mirror
[HTC Sensation] K900i:
Edit :- all working fine..thank you
[Motorola Droid RAZR] jeff_roey:
So, my Maxx suffered a power button failure and I should be receiving my warranty replacement from VZW sometime in the next day or two. Other than the power button not working, the phone is functioning fine. It reboots, runs normally, functions perfectly. I'm running .215 rooted and I want to return the phone back to stock before shipping it back. Problem is I can't access Boot Loader, no matter what I try. It's like it's not there anymore and when I command the phone into it using quick boot, adb, or the built-in menu, the phone just power cycles off. Let me try to explain:

I have Quick Boot installed and I can use it to boot into recovery without a problem. If I try to boot into Boot Loader, the phones powers off and stays off.

I've tried adb shell with the same results. I can connect to my PC and command the phone using shell commands but usin the 'adb reboot bootloader' command results in the same thing: phone power cycles off and stays off.

Even though my power button is AFU, I figured out I can still access the main recovery menu (the vol down to choose, vol up to select one) by holding down the vol up/down and plugging the phone into a charger. Same thing: power cycles off and stays off.

* Funny thing is although my power button doesn't work, I can still soft reset the phone by holding the power button in and vol down - which is what I need to do to exit recovery or other menus I need to input to a prompt using the power button.

Anyone know of this happening? MY guess is since my phone starts and functions normally otherwise, the boot loader is still there in some form. I just don't know how to access it. Any help would be much appreciated.
[Motorola Droid RAZR] dave5777:
I can confirm this app will reboot bootloader

https://play.google.com/store/apps/details?id=org.riceknight.gs2reboot
[Motorola Droid RAZR] jeff_roey:
Thanks Dave but not for me. Same result: phone power cycles off and just stays off when selecting reboot bootloader.
[Motorola Droid RAZR] maarawoe:
If there is no bootloader you won't be able to start your phone at all as its THAT what basically boots the whole hardware and software....

How about adb reboot bootloader or adb reboot recovery commands ?
[Motorola Droid RAZR] jeff_roey:
The bootloader being the phone's "bios" is kind of how I understood it so I'm figuring it's still gotta be there. I just can't seem to access it or get to the "device/battery OK, device disconnceted" menu. I tried adb reboot bootloader and got the same results: power cycle to off and stays off. adb reboot recovery works fine.

Knowing this phone is going to be turned back in, is there any other way I could re-install .211 without having access to the bootloader screen?
[Motorola Droid RAZR] maarawoe:
Try the eternity project flasher or the motorola's rds lite if they will be able to put the phone to the flash mode as they do that automatically...
[Motorola Droid RAZR] jeff_roey:
I posted a thread over at DroidRAZR.com and got some good feedback and troubleshooting help. It looks like the bottom line is the power button failed in the 'on' postion. One of the folks that replied to the DR thread caused his device to show the same 'AP Fastboot power-off' that I was getting by entering the 'Boot Mode Selection Menu' and holding the power button down while he vol+ to select AP Fastboot. It caused me to look a little closer at what the device was doing and that seems to be exactly what's going on - I powered th phone down using the Quick Boot app and was able to soft reset by holding down the vol- key by itself (didn't need to press power in conjunction). After it SR and i released the vol- key, the device rebooted by itself.

For your info, that thread is here: http://www.droidrzr.com/index.php/topic/3782-cant-access-boot-loader-menu-no-matter-what/

I tried working a thin piece of paper in around the button but no luck there.
[HTC One X] kkrazzyyguy:
I heard that the the Google Now on ICS project is completed . I was very confused reading the OP regarding the project . Can anyone help me install Google Now on my HOX running Stock Sense Rom .
[HTC One X] Traniz:
I didn't read so much into it but currently it's only for JB.

Those that have ICS and GNow have written it manually to the ROM.

EDIT:

http://xdaforums.com/showthread.php?t=1749045