yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] sun8ross:
its very useful

i use customized settings(option 10)：10 16 24 48 56 72

no launcher redraw,no memory leak,everything smooth
[Galaxy S I9000 General] moegrave:
This is exactly the feedback I was looking for. Thanks sun8ross!

Please, any other users feedback will be also greatly appreciated.
[Galaxy S I9000 General] chue.hsien:
hmm i tried it, but it seems like the improvement is negligible... is it because our SGS already has plenty of RAM? The script was made for low-RAM phones in the first place right?
[Galaxy S I9000 General] moegrave:
So i was playing more with the settings, and finally mine are:

/sys/module/lowmemorykiller/parameters/minfree

[2560, 4096, 6144, 11264, 13312, 16384] [ 10, 16, 24, 44, 52, 64]

/data/SuperChargerMinfree

[2048, 4096, 12288, 18432, 24579, 30720] [ 8, 16, 48, 72, 96, 120]

and, wow! :eek:
[Galaxy S I9000 General] madphone:
I'd wish it would be integrated in roms or kernels. it's simply the best. but it's to complicated, for doing it every time i change the rom (or/and kernel?)
[Galaxy S I9000 General] ZioGTS:
Sorry for the noob question, but why do you list two sets of parameters? I can only set one when running supercharger... :confused:
[Galaxy S I9000 General] moegrave:
As far as I get it, the supercharger script overwrites the stock OS LMK settings, but with that it works on demand and chooses how to act (before and instead of the stock os one)

The values in /sys/module/lowmemorykiller/parameters/minfree are the stock ones, I think..

The ones in /data/SuperChargerMinfree are the ones which the script uses to overwrite.

I listed the two values, because we have a safe backup for playing with the values :D as far as I understand from reading in the original thread.

That's why I listed this thread in General, because I need more opinions. And on the thing if it's only for low RAM phone, I do not agree. This script have massively improved all RAM management that I have ever wanted.

Please feel free to share settings and opinions on those settings in this thread!

P.S.

ZioGTS, not a noob question, but a good remark for me not being clear enough. Thanks :)
[Galaxy S I9000 General] dragonkhan9:
one with failed l' to have on Rom GingerReal but damage
[Galaxy S I9000 General] ZioGTS:
Thanks to you! I'm currently testing MegaRam 1 setting, but I think it's a little bit unbalanced on sgs... Maybe needs some tweaking.
[Galaxy S I9000 General] ZioGTS:
UPDATE: I tried your settings (8, 16, 48, 72, 96, 120) and I feel they are much better than MegaRam 1!!! I'm sticking with these values for some time and see what happens. Thanks! ;)
[Galaxy S I9000 General] moegrave:
I played around and found out that these settings work really nice for me. Not too aggressive and yet I have a lot of free RAM for multi or single tasking. Thanks for the feedback!!
[Galaxy S I9000 General] vitoski:
Hi,

I just thought that I will share my settings for SGS as well. I've already played around with various settings like: Agressive (option 1); Balanced 1.2.3 (options: 4,5,6); MegaRam 1 and 2 and a few my customized settings.

With every setting I had a bulletproof launcher (it was not restarting at all), but I found that after a day of using a phone the applications started to start slower.

Again I made some customized settings and now use the following numbers:

6,8,30,60,80,100

Maybe it will work for some one as well.
[Galaxy S I9000 General] moegrave:
Nice, actually my initial settings were: 8, 12, 40, 60 ,80, 100.

I have two questions for you: 1) what is your normal free ram values

2) have you tried my settings :)
[Galaxy S I9000 General] vitoski:
Sorry but do not remember what settings I had before I applied V6supercharger. Nevertheless my free memory was something around 50 MB. Now with current V6sett I have around 70-80.

What I found is that every time I start "Cut the rope" game, both contacts and dialer get killed.

If I go with balanced settings, there is a high chance they will stay in memory, but the apps start slower after a day or two.

So the best compromise would be to have the settings that prevent our most willing apps to be killed and the other not.

Best of the best solutions would be to have a chance to decide which app is running on each slot of Lowmemkiller. This case we could have our contacts and dialer untouched even with low memory...

Now we can only guess. Somewhere I read that most apps run in slot 3 therefore giving this too high value will cause them to be closed by any further app start.

There is no point to have more free ram if android needs to load the same app over and over again cause it got killed already...

Sorry for making it so long:-)

EDIT:

I had to modify my settings, because when I played high resources consuming game it closing after a short while and I was left with home screen...

Now I have the following values:

6,8,26,34,60,80

They were already tested with same game and other things. So far so good, however I think apps start a little bit slower.

Just to make everything straight, I am on Galixian GT.

Anyone has some other good configuration? Maybe you use SuperchargerBeta3 with kickasskernel?
[Galaxy S I9000 General] Hawkeye1103:
can you run kickasskernel with galaxian GT? i can't. If you get boot loops try flashing speedmod kernel t10
[Galaxy S I9000 General] ZioGTS:
Same here... Bootloops with galaxian and kak... :-(
[Galaxy S I9000 General] upichie:
I use this script and have nothing but positive comments regarding it. I was having a problem with my launcher redrawing; not only did this script solve that, it made my phone infinitely more responsive. It has substantially aided me in acheiving a phone with no lag... ever.
[Galaxy S I9000 General] ZioGTS:
Which settings are you using?
[Galaxy S I9000 General] swaakx:
I tried 6,8,26,34,60,80 but with my ROM (SURFACE) and default zeam launcher in 182 dpi, first launch is freeeeziiiing then reboot. On second reboot, I had chance to be able to relaunch the script and set these values :

8,16,30,48,56,72

just much better ! lots of free ram around 100Mb while having around 35Mb without supercharger. My home is now unbreakable :) at last it seems to. I will report after a few days.

I'm using Galaxian EE (last version) kernel.
[Galaxy S I9000 General] ZioGTS:
You wrote the same values for before and after...
[Galaxy S I9000 General] swaakx:
Sorry :rolleyes: corrected now

My previous config made my phone fell in a OOM loop after a Cut The Rope session... still responding but always black screen !

I finally set these params :

10, 16, 40, 60, 80, 100

So far it's much better and based on stock values for level 1 and 2.
[Galaxy S I9000 General] swaakx:
It's been a few hours I'm using my previously posted params and I must say that I'm very happy with them.
[Galaxy S I9000 General] ZioGTS:
I'm giving your set a try... I was still with MegaRam 1 (6,10,40,60,80,100), and your set basically brings default Samsung values on slot 1 and 2 while everything else is like MegaRam 1. Could be a winner, let's see! :rolleyes:
[Galaxy S I9000 General] yvrRome:
Thanks, I'll try this too. I'm on balanced1 and works great for me but curious to try your custom if it can get better.
[Galaxy S I9000 General] gsw5700:
Anyone tried this on JVS ?

Sent using geek power
[Galaxy S I9000 General] yvrRome:
So I've been using the params above and everything was working well until I tried to record a video on 720p and got an error that sd card does not support hd recording.

So I went back to my balanced setting and hd recording's working again.
[Galaxy S I9000 General] ZioGTS:
Very weird. I just tried and it works flawlessly here. Do you have a bigmem kernel or cm7 rom? Those are known to make hd recording impossible.
[Galaxy S I9000 General] yvrRome:
I thought it was weird too. Not using bigmem as I need my hd recording. Currently using Milky ROM with Semaphore 1.6 (not bm). It's working again after changing back to balanced.
[Galaxy S I9000 General] ZioGTS:
The third slot in Supercharger sets your free ram. Try using balanced value for slot three and keep every other slot as previously customized.
[Galaxy S I9000 General] Hawkeye1103:
how it the new supercharger script working for you on JVS? i got it on 5 setting and wouldn't boot up:(
[Galaxy S I9000 General] ZioGTS:
Beta 4 doesn't work here... It says I don't have root lol
[Galaxy S I9000 General] yvrRome:
That did the trick, thanks!
[Galaxy S I9000 General] ZioGTS:
Glad to hear it worked! :)
[Galaxy S I9000 General] moegrave:
For the JVS and supercharger, check the version of your busybox installed. I think supercharger does not work correctly with lower than 1.18.2 busybox version -> this is in the supercharger thread :D
[Galaxy S I9000 General] SpaceCaseDave:
+1 for SuperCharger in our Roms!!
[Galaxy S I9000 General] SGS_elko:
I applyed the script and now my phone bootloops :(. First I updated BussyBox from 1.16.x to 1.18.2 and then applied the script as described in the main Thread.

I had stock ROM (JVQ) 2.3.4 with cf-root and I had the TW4 launcher installed.

Now I'm restoring my ROM from CWM :p

What I've do wrong?

Edit: I tried again to implement the script and it fails again(Bootloop at Galaxy S I9000 screen). What I've done:

1. Upgrade BusyBox to 1.18.2

2. Run Script Manager with root permissions (more->Advanced options->config-> Browse as root)

3. Run script as Root

4. In script menu chosed Nr. 6. 512HP UnLeeded //

5. Then Nr. 24. Exit

Only Thing that I skiped is to setup the file /data/99SuperCharger.sh in Script Manager to startup at boot, because I want to test the script first.

Can someone Post step by step instructions how to do it? Maybe I chosed the wrong option in step 4.????

Regards
[Galaxy S I9000 General] claus1953:
I have also an SGS i9000 but with a JVS ROM installed and applied the setting nr. 6. Looks like it worked up to now.
[Galaxy S I9000 General] webwude:
Sounds very interesting as I am having a lot of launcher redraws lately... I will give it a try this evening :D
[Galaxy S I9000 General] nikkpap:
thanks mate but it will help to make a little tutorial with a how to ... its easier for you to explain .... thanks...
[Galaxy S I9000 General] webwude:
What about this one: http://xdaforums.com/showthread.php?t=1126940

Kind regards,

ww
[Galaxy S I9000 General] ferparedes:
Hey another Telcel victim here :)

I also applied option 6, but I started having the dialer close issue (which somehow also affects whatsapp) and the weirdest thing: The screen timeout stopped working. If I didn't lock the phone, the screen would stay on until I came to it and shut it off manually.

So I tried No. 5 and now the screen did shut off after 1 min, but I still got the dialer closing. So now I'm on custom settings (10,16,40,60,80,100) and I'm trying it out.

In general, great improvement in performance. Super smooth and no more redraws.

Edit: I still had the dialer being killed while in background. Checked location and android was killing it because of low memory (or so it thought). So I left the first three slots the same but settled on 55,60, 72 for the last three. Problem solved!
[Galaxy S I9000 General] zeppelinrox:
BulletProofing the dialer with update 9 rc1 works good :)
[Galaxy S I9000 General] ferparedes:
What process am I looking for? I don't see any process with the name dialer in it when it lists the running processes.

Thanks
[Galaxy S I9000 General] zeppelinrox:
You're using the V6 script?

It may say phone instead of dialer...

Anyway, it would be in the first grouping if your lookin at the OOM Stick
[Galaxy S I9000 General] ferparedes:
Got it, Thanks!
[Galaxy S I9000 General] zeppelinrox:
FYI... I have RC1s... :D

http://xdaforums.com/showthread.php?t=991276&page=503

Before Updating,

Wipe Caches!

This is just a precaution in the event that you experience any lag...

Updated October 24

: - V6 SuperCharger Update 9 RC1

Improved - Cust-OOMizer - redid all the code (can now do a quick charge with current minfrees)

Improved - Engine Flush - shows before and after stats (It's really :cool:)

Improved - Re-SuperCharger - won't ever overwrite existing system files with old ones from a different rom and with an easy workaround for that.

Added - Option to wipe dalvik cache and cache partition!

Tweaked - Minfrees - Presets above 256HP are now more multitasking friendly

Tweaked - init.rc support - now optional to copy a supercharged init.rc to root on boot.

More - Lenient busybox recommendations v1.16.2 and up (excluding versions greater than 1.18.2 and lower than 1.19.0)

ReWrote - ALOT of the code - It's ALOT more efficient and smarter :)

Enhanced - the interface all over the place...

Added - something fun... :cool:

Added - something controversial... :eek:

Updated October 24

: - 3G TurboCharger Installer Update 3 RC1

Added - Wi-Fixer - Try and fix wifi issues after applying 3G tweaks...

Added - 6th setting (uses less battery)

Added - Market Link in menu - Opens up to speedtest.net app

Added - something fun... :cool:

Updated October 24

: - Kick Ass Kernelizer Installer Update 3 RC1

Added - Uninstaller

Added - sio scheduler support

Added - vm.oom_dump_tasks=1, vm.laptop_mode=0, vm.block_dump=0, fs.lease-break-time=10

Changed - vm.min_free_kbytes=4096 (was 8192), vfs_cache_pressure=20 (was 10)

Enhanced - IO Scheduler information/display

Enhanced - Interface

Added - something fun... :cool:

Updated October 12

: - V6 SuperCharger Update 9 Beta 6.3

Added - init.rc support! (a supercharged copy gets copied to root on boot - it might not work but it does make for easy baking!)

More - Lenient busybox recommendations v1.16.2 to v1.18.2 (still testing 1.19.2)

Renamed - HTK Launcher to

Die-Hard Launcher!

Added - A 3rd Launcher for Gingerbread roms and higher! (HTK is the 3rd one - no HTK on Froyo and below)

Changed - OOM grouping/adj parameters

Improved - BulletProof Apps routine - loops so you can bulletproof more than one at a time - plus better error handling.

Improved - Test Drive

Mounts - rootfs rw as well as system - should solve some issues :)
[Nexus S Q&A, Help & Troubleshooting] ceven:
Hi everyone, this is my first post here.

I bought for about 1 month Nexus S, and I am extr disappointed with the quality of audio when recording video.

The sound quality of the video, such as concerts out very badly.

Has anyone exeperienciou this, and knows how to get around?
[Nexus S Q&A, Help & Troubleshooting] ceven:
Any sugestion!?
[Nexus S Q&A, Help & Troubleshooting] Rem3Dy:
Concerts are usually way to loud to record with a cell phone microphone.
[Nexus S Q&A, Help & Troubleshooting] sagech:
Flash a kernel that supports voodoo. I use the netarchy kernel. It fixes the low quality audio recording problem.
[Acer Iconia A500] tkak:
I for my iconia rooted through Iconia Root and using root explorer was able to access system/app. I deleted email.apk. Now using the same procedure, I got the email.apk and email.odex from Samsung Galaxy S2. I got it in the SD card. Now using Root explorer, I tried to copy both to system/app. But they are not appearing in the folder. The folder system/app is R/W only. Kindly help me as how to load the same.

My Android version is 3.0.1
[Epic 4G Q&A, Help & Troubleshooting] ThunderOKC:
I was using WiFi tethering and the phone got real hot. I tried everything to keep it cool, then the battery went real low. While trying to text someone before turning off the phone to rest, it went completely dead. Now when I try to turn it back on, it won't load. Keep rebooting over and over constantly. Something about Inconsistent UIDs and being unstable. What can I do to fix it? I've tried everything within CWM (purple), but no luck.
[Epic 4G Q&A, Help & Troubleshooting] BeerChameleon:
You got corrupt data...

Ways to Fix:

1.Restore an old or recent nandroid backup that u may have..

2. Wipe Data/Factory Reset In Clockwork 3 time then reflash the rom

3. Odin to something then reflash rom

I recommended either 1 or 2. ;)
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
David is correct. You can try just reflashing the ROM first but will probably end up clearing data to get rid of the error.
[Epic 4G Q&A, Help & Troubleshooting] rulyskull:
I had the same problem and nothing worked so I just ended up odining and it seem OK now
[HTC Sensation] Joshhedge:
Hey,

HTC state that the Sensation has got the MSM 8260 while Mike ( ARHD developer ) says that the SoC is actually the MSM 8660.

Can anyone prove or disprove this and what difference if any, is there between the two SoCs?

Cheers :)
[HTC Sensation] Bernardos70:
Not to sound like an ass, there is a very recent thread about this, but the gist of it is: The 2nd digit, which is the only different one, determines whether it is a CMDA phone (which the Evo 3D is, because it is on the Sprint network that uses CDMA) or a GSM phone (which AFAIK all sensations are, including the Sensation 4G here in the USA, which is on T-mobile, a GSM carrier).

So 8260 = GSM phones that the whole world has (International Sensation, T-Mobile USA)

and 8660 = CDMA phone which Sprint (CMDA) carries.

Other than that, AFAIK, they're exactly the same.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Hamburg:
Has anyone heard any word out of DFT on a ripe Mango for HD2??

I know there was some speculation that they might not release it until after the official Mango release, so I'm wondering if there's been and rumblings now that the Fujitsu-Toshiba phone was released yesterday.

If I can't get it on my HD2, I'll probably rush to get the first Mango device that hits US shelves, and likely regret it once something better comes out. At lease if I hear something is on the horrizon for the HD2, I'll be much more inclined to wait to see the hardware options.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] temporary_24:
Hi,

There have been some development, although not from DFT,

check this page: http://wmpoweruser.com/wp7-5-mango-rtm-rom-nearly-ready/

regards
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] huismeester:
Everything on this side gentleman

http://xdaforums.com/showthread.php?t=1080950
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] TonyCubed:
SD support is broke so there isn't any actual point in flashing Mango tomorrow, you can play around with it, but you'll have serious data storage problems as you'll only have a couple of MB to actually use.

DFT/Cotulla have said something about wanting to wait for Mango to be released officially before releasing, but I don't know if that is actually a soon release or something in a couple of months time.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] melando:
does anyone have an ETA?
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] nikc0069:
On the thread linked earlier, YukiXDA has implied something will be available tonight. Whether they will have rectified the SD issue by then remains to be seen.

I'd say it is coming soon though (and will be updateable :) )
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] MatchedANDY:
there a way to get 7720. havent be able to do it yet but i have got 7712 fully working without any bugs
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] melando:
7712 - 7720

Is 7712 working with SD including partition (to allow dual boot Android on SD)? How did you get there?

I have seen some other threads suggesting you can update 7712 to 7720 using Zune, does this work on your 7712 build?
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Starfury:
http://xdaforums.com/showthread.php?t=1236027
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] melando:
I think this page covers updating from 7712 to 7720 but there are still unresolved problems with SD card/partition, unless anyone has an update
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Starfury:
This page covers a new rom starting at 7004 and going all the way through to Nodo via Zune and then Mango when MS release it via Zune. Or you can go from Nodo to Mango via the dev route if you can't wait.

Yeh the SD card gets locked to WP7 but seriously why would you want to dual boot Android and WP7... just pick one and go with it, what's the point in dual booting?
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] melando:
(1) I use for both work and home use and

(2) I am confident enough to rely on Android but Mango is not (yet) fully reliable

Pre-Mango WP7 lacks some features so (for now) I am using 6.5 + Android
[Vibrant Q&A, Help & Troubleshooting] kool548:
Need to know how to backup efs folder using root explorer I have tried but am missing something don't know how to copy over to external sd card to save. Thanks
[Vibrant Q&A, Help & Troubleshooting] s15274n:
long press, copy, paste to external sd.

I have a copy on my pc.
[Vibrant Q&A, Help & Troubleshooting] kool548:
I have tried long press and hit paste it does not give me on option to copy over to external sd card
[Vibrant Q&A, Help & Troubleshooting] GreggoryD502:
I use root explorer. After you copy you have to navigate to your ext SD card while still in root explorer then paste.
[Vibrant Q&A, Help & Troubleshooting] s15274n:
with root explorer, if you long press on the folder, a menu option screen will show.... if you are not seeing that, you are doing something wrong.

just mount your phone to your pc, look at your internal sd, copy the folder and move to your pc. It is safer there anyway.
[Samsung Infuse 4G] terryneely:
I started using "Battery Monitor Widget" free by 3c

a few days age.

I noticed that the charging current using the Samsung plug in charger was about 300 ma higher than the charging current using other USB chargers. I read on other battery threads that Data + and - are connected on the Samsung charger to prevent the USB screen from appearing. I wanted to know weather the connection of D+ and D- had any thing to do with this so I opened up one of my other USB chargers and soldered the two middle pins (d+and d-) together. After making this change, I got an additional 300ma out of this charger.

According to Battery Monitor Widget, when charging the battery from 50%, the Samsung charger was putting out around 1180ma. Unmodified USB chargers put out about 820ma. The max current output listed on the charger makes no difference in the result.

The charging time from 50% to 100% was reduced by 25% using chargers with d+ and d- connected.
[Samsung Infuse 4G] Serinety:
This is actually very interesting. I have been trying to figure out how to make the phones charge faster and have been searching for higher ma chargers. I wonder if there is a way to modify the cable to achve he same results.

I've noticed that sometimes plugging my phone into one charger triggers usb mode but other chargers do not.
[Samsung Infuse 4G] Uncle Irish:
Post this up in Entropy512's thread here

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

he's doing battery charging research. This might be helpful to him
[Samsung Infuse 4G] Entropy512:
Nope not useful at all - nothing new.

1) It's not 300 mA more. CurrentWidget has a 1.83x scale factor. Covered in the thread above. It's 125 mA more.

2) I'm fully aware that shorting D+ and D- together puts you in AC charging mode, in compliance with revision 1.2 of the USB Battery Charging specification. I'm also fully aware that iPad/iPod/iPhone chargers get treated by our phone as a regular USB port and not as an AC charger.

USB charging is 475 mA. AC charging is 600 mA, unless you're running one of my kernels with charginghacks - in which case it can hit 800 mA when the battery is below 4.0 volts.

Right now, I don't need any more data from the Infuse. I need someone with a Captivate or i9000 to run CurrentWidget tests, I'm looking for VERY specific things.
[Samsung Infuse 4G] terryneely:
The Forum will not let me post on this thread, perhaps someone could post it there for me.