yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChrisG683:
This is not meant to be a complaining post, mostly I wanted to see if anyone else is having my problems.

I am currently running ParanoidAndroid 2.50 (CM10 based ROM) and I absolutely love how all AOSP ROMs look and feel. TouchWiz had some neat things, but it felt really bloated.

My problem is, multi-tasking on AOSP blows, really, really, really, BAD. I mean it's downright as bad as HTC One X's Sense UI multitasking. For whatever reason, I can never get my free RAM to dip below the 600 MB limit. Usually it hovers around 750 MB, and occasionally I can get it down to 650 MB.

I am not a huge multitasker, but I HATE HATE HATE app re-draws and reloads. This was the one nice thing about TouchWiz, it would keep my opened applications running until I was absolutely at the bottom of my free RAM (~150 MB). My frequently used applications almost never needed to be reloaded/redrawn. This is especially big for applications like Youtube and Browser/Firefox, as you lose everything that you had loaded otherwise.

I've tried spamming opening apps, and the most apps I seem to be able to have open at once is around 8-10 depending on the circumstances. As soon as I cross that threshold of open apps, my other opened apps start being force closed, and require a redraw/reload. This is an absolutely pitiful amount of apps, especially with the whopping 600-800 MB of free RAM that I usually have.

I also have the issue that sometimes even when I don't open a lot of apps, some of my apps like to force close for no reason after a few minutes of being idle. My MailDroid and Firefox apps seem to be extra susceptible to this random time based force close compared to GoSMS, which rarely closes after an inactive period of time.

I have tried multiple kernels, multiple ROMS, multiple governers and I/O schedulers, and I even tried zeppelinrox's V6 supercharger + multitask mods. Nothing I do seems to allow me to crack into that 600 MB of unused RAM. I am so flustered by this that I'm actually considering going back to TouchWiz.

Could anyone else provide me with some feedback with their multitasking app limits/free RAM? Is this a known CM10 issue?

TL : DR

-I can never get below around 600 MB (usually hovers around 700MB) of free RAM

-My running app limit seems to be 8-10 with about 6 widgets

-My apps seem to force close after short durations of inactivity

-I experienced NONE of these problems on TouchWiz

-Could someone post their numbers for some of these things, and is this a known problem for CM10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deoxlar:
Same problem here... I think most people like this problem though. Many like to see more free ram, but I prefer faster multitasking. My main concern is my downloads being closed and interrupted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radeon_x:
Yeah definitely a known issue on AOSP. Memory allocation issues I guess. I've never seen a dev comment on it, despite the fact it has been brought up several times. I suspect we won't get a fix until the JB sources are released for the d2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
Post your services.jar

If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.

btw what are your minfree settings?

Did you do the aLogcat test?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChrisG683:
Oh wow it's zeppelinrox! Hi :D

Yes, I used the Windows Jellyscream tool to patch my services.jar. The ICS Service Center in your script insists that it worked, but CM10 does not currently have a "Charge Only" or "No Action" mode when the cable is plugged in, I'm forced to mount the SD card(s). Your tool specifically says do not do that, but I don't really have a choice :/

My current MinFree values are:

8, 14, 40, 50, 60, 75

I have also tried the auto-calculated ones (which in my opinion leaves way too much free RAM theoretically):

8, 16, 325, 358, 390, 423

Both of them didn't seem to make a difference.

I have attached my services.jar to this post as well as requested.

As for aLogcat, I'm not sure what that is or how to do that :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
Hi :)

Well I can't open it up... is the file size correct?

Maybe it's an incomplete upload.

I assume that it's for ParanoidAndroid 2.50 so try upping it again since I haven't cracked one of those open yet lol

The service centre only looks at the supercharged launcher aspect and the windows exe isn't up to date for the multitasking mods.

I've actually just updated the ultimate jar script today... and also has an SGS3 specific edit ;)

However it may be only for the stock rom.

The aLogcat test is described in the ultimate jar thread OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChrisG683:
Weird, I'm also not able to open the one on my phone, that's kinda scary.

Ok, I'll give your new ultimate script a spin, and I'll look into the aLogcat thing as well and try to provide you some information.

Here's the services.jar file that was leftover in the Jellyscream directory (JellyScreamPatcherV6_0.9.0.6/framework/services.jar). I chose not to delete the temp files, so I'm guessing it's the same file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChrisG683:
WOOOOOOOOOOOOOOOOO!!!!

Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!

Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock :D.

Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD

Edit:

My only question now is why oh why do the default AOSP settings suck so bad?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
I think that's to make me look good :cool:

I hope to have it automated somehow like the outdated ics webapp.

btw how did you decompile?

I'll try again when on the PC.

edit: ok that second one you posted opens up fine. I guess that's CM10?

It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752a

Uh yeah... you get a 40 app limit

only if you have 1.5GB of RAM

- otherwise, you're STILL stuck at 15 hidden apps... lol

I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.

I just didn't know where that setting came from lol

So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.

Of course, "sys.mem.max_hidden_apps" was introduced

after

my mucking around :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChrisG683:
Hmm, I'm not sure what you are asking here, could you clarify?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] themadproducer:
hey zeppelinrox....

And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.

My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
OH that's ok.

The second file you posted decompiled fine :)

Yes you were using dorimanx's trick to break the lowmemorykiller on HD2 :)

He asked me to break it on ICS and above, which I did.

But that only lasted a day because I found another way to do it... boost number of running apps without breaking lowmemorykiller.

Needless to say, dorimanx got real happy lol.

See post 2 of the ultimate jar thread for more about that.

So yeah, you still have the app limit and lots of room for more multitasking since you can't get very low on ram.

I've added more mods to reduce the likelihood of apps closing on you. (Check the change log)

Sense users are ecstatic with the latest :D

Anyway, I'm sure that if you try it, you'll notice a difference - it's just a matter of you not knowing how much better it can be ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deoxlar:
What program are you using to put on the app kill exception list?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] themadproducer:
Deoxlar...are you asking me?

With the HD2, I had the OS rigged to NOT kill any apps EVER and used System Tuner Pro as my APP Killer with exceptions checked off. I used Tasker to determine the ram availability each time a window opened or changed, and Tasker would trigger STP when necessary.

But Zepplinrocks' V6 Supercharger as a very unique system for doing similar...but overall, it handles everything to do with ram management and better. Also, for some people's setup, it is a dramatic improvement...a FIX... a LIFE SAVER. (Basically the rom Devs are going to eventually slowly STEAL Zeps ideas. But we will not forget.

My old HD2 memory mngt system was an ALL or NOTHING workaround so it suffered in that regard.. The way my S3 with stock ICS is handling things right now is surprisingly good. I did a test last night opening as many apps as possible until I basically ran out of FREE ram. At that point, the OS was doing it's thing, killing another app or 2 so it could run the new app launched. Multitasking...or switching to newly launched apps and then returning to previously launched apps where they left off....worked near flawless and FAST on my i747m. When I woke up today, 3/4 of the apps were still in memory ready for resuming.

This is why I went from 2 years of OBSESSIVE flashing and tweaking....to using my new S3 with the Stock rom and about 1/100th of the tweaks. Super STABLE and not a slouch. I hope the upgrade to JB...well....is an UPGRADE. yadda yadda yadda...:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is :D

Install aLogcat, run as many apps as you can, run aLogcat and search for longer.

Most people get this before the mod...

The 16th hidden app gets killed because the limit is usually 15.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] themadproducer:
For you Zep, I do about any test you asked me to do! Respect! :good:

Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel". :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
LOL thanks for the kind words man :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] themadproducer:
OK, I used System Tuner Pro's log and guess what....checked a dozen times....

hidden #51

Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.

I cross referenced by reopening the apps and most of them were still in ram memory.

Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.

So these games/apps were not killed off by idle time auto killing.

This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.

What do you think Zep...honestly, have you heard any similar reports?

UPDATE: now i am down to 83mb free...still rock solid smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radeon_x:
So, you're using the "ultimate jars" script in conjunction with which ROM? And did you use in conjunction with the supercharger script?

Just trying to understand exactly what is required to "fix" the multitasking issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
Wow I've never heard of a stock rom having the app limit set to 50.

However when you type free in terminal, how much is system tuner reporting as free?

There is a difference because the free command in terminal is always very low whereas apps like system tuner/task managers always report free ram as "free ram + cached apps" which is a much bigger number.

Can you post a deodexed services.jar (it's probably odex tho since it's a stock rom) or at least the smali files?

The windows patcher should be able to decompile it.

If it's not sense I'd only have to look at ActivityManagerService.smali and ProcessList.smali.
[T-Mobile Samsung Galaxy S II SGH-T989] Andr3s:
Hello I would like to try a ROM based on ICS to do some tests, but I have now a exactablemente Rom 4.1.2 JB, I wonder if there would be any problem if I install another rom based on ICS 4.0.4 exactly.

Greetings and thanks
[T-Mobile Samsung Galaxy S II SGH-T989] ArcticFish:
Nothing will happen, I do it all the time

Sent from my Paranoid SGH-T989
[T-Mobile Samsung Galaxy S II SGH-T989] Andr3s:
Ah ok, thank you very much perfect friend: D

Note: Please Close The Post :D
[HTC One X] ionhide:
Okay, so i upgraded my hboot to the new 1.28.0000, and my phone flew with maXimus rom. Everything went smooth, no issues at all, untill i tried flashing a theme that according to the thread should be working on maximus 5.0.. After installation, system wouldnt boot, so i thought something must have gone wrong during the flash.. I went into recovery mode and flashed again.. Same issue.. And this is where it all went wrong..

Phone wouldnt boot up recovery, said that powerlevel was too low.. Rom wouldnt boot, and i was stuck at bootloader.. Phone refused to boot up recovery, and suddently phone died.. I unplugged the cable, led started blinking and phone booted up in HTC load screen.. Never went anywhere from there.. I tried going into bootloader to power down and let the phone charge when it was off.. Every time cable was connected, phone booted after some seconds and started charging.. After 15-20 minutes the phone died, and i had to unplug the cable.. Led blinked again and phone booted.. In bootloader it kept saying that phone power was to low to flash.. Unable to charge the phone in offline mode - Phone uses too much power in HTC bootup screen, so phone could not load recovery.. I tried booting recovery via fastboot cmds in windows, tried ADB, tried a custom RUU, nothing worked..

Phones has been sent to repairs today, hoping that HTC can fix it, but it might be with a price..

So i urge every one here, to make sure you never flash anything with less than 80% battery on this HBOOT.. If its related to that..
[HTC One X] Mr Hofs:
Move it to General

It's there with a reason. This is the development forum

And this issue has been covered here on xda. You actually can charge your phone when it's died in this situation ......

Verstuurd van mijn HTC One X
[HTC One X] ionhide:
Its not a Q&A or general topic..Its a warning that should be here where the threads about flashing this HBOOT is.. Nobody reads Q&A or general before they flash hboot etc.. If its an issue with the hboot, there should be devs looking at it to see if its either a risk or a fixable issue..
[HTC One X] Mr Hofs:
I edited the post, there is a script somewhere here to charge the phone during constant rebooting or similar.

Verstuurd van mijn HTC One X
[HTC One X] ionhide:
How would it be possible to run a script when you cant get into recovery ? And when you cant see when the phone starts discharging ? Could you find and link the thread or script ?
[HTC One X] matt95:
he's right...there is a script that slowly charges your phone...give me a sec and i'll post it

---------- Post added at 09:14 PM ---------- Previous post was at 09:11 PM ----------

this is for windows

this is for mac

#!/bin/sh
while true
do
fastboot getvar battery-voltage
fastboot reboot-bootloader
sleep 5
done
[HTC One X] Mr Hofs:
And i don't want to be a ass*ole really ! But if a little searching would be done it would probably show up, and it is still not dev-related, it's not about building , compiling , developing roms or android . This is a user thing unfortunately......and i really feel bad for you and your phone . It's a common known fact that when you start with flashing you're battery should be charged, and with all the info here on xda most of the people would agree that a 100% full batt is the best to start with.

This is not a rant against you or whatever don't get me wrong here !!! But there are a lot of people diving into rooting and flashing without ANY knowledge.......so that's my opinion ;)

Verstuurd van mijn HTC One X
[HTC One X] ionhide:
First of all - Look at my signature and you might discover that i am not a newbie at this - Second - Read the story again - I was charged above 70% battery when it happened, but due to the phone not booting, it spend a lot of power in bootscreen stage.. And the charge-drain issue with the hboot could be related to a bad hboot, so this is indeed a developer issue's related thread.. And, i searched for a solution, just didnt search for a battery charge script, since i never heard of that before.. So again, your recognition is not required for me to start this thread..

A litte too much ignorance in your posts, when you dont even read yourself.. See ya..
[HTC One X] Mr Hofs:
I do not share you're opinion. I leave it with that. As I said before the post was not against you. ( I did read but seen no 70 % you are just giving advice that no flashing should be done under 80% but it does not say in what state you're phone was and i don't see signatures on my phone )

Sorry for trying to help.

Verstuurd van mijn HTC One X
[HTC One X] ionhide:
So you dont agree that if there is an issue with the dischage of the 1.28.0000 hboot, and you can almost brick your phone, if there isnt a solution for it, a warning to others, and a chance for devs to look into it, isnt a thread worthy ? There hasnt been a single one here who actually succeeded with it yet, and i read about another in the maXimus thread who had the same issue..

I will see if i can get my phone back tomorrow and test your suggestion, and i thank you for the input.. I will let you know if it works..
[HTC One X] matt95:
stop arguing you two! i would suggest you to change the title into [HBOOT][IUSSE]1.28.0000..... however i had the same iusse when i upgraded the One X to the 1.28, it got stuck with battery low, then i ran this script and i finished the process successfully...
[HTC One X] Mr Hofs:
Thank you, and i'm not saying you are wrong. But everybody seems to be too eager to flash the new hboots and roms, it's not even released official yet. Who decided that the leaked releases are really safe and finished for the masses. Maybe there is something wrong with it. My opinion is to wait for the official hboot and blame HTC afterwards if errors pop up !

I will wait for you're input about the repair. Made me curious :thumbup:

Verstuurd van mijn HTC One X
[HTC One X] kevrae:
this happened to my phone the other day, stupid enough to start flashing a new rom with <40% battery and wouldn't boot. found out about the charging script and ran it, bit my nails for about an hour as i worried and then gained enough charge to boot back into recovery and flash a working rom.

Charging script is a lifesaver, hope HTC dont charge you too much as sounds like what mine was doing and managed to sort at home.
[HTC One X] matt95:
happened the same to me as posted above ;)
[HTC One X] Mr Hofs:
I never experienced something like this, thank god !

Edit : i put my ignorance aside for a moment ;) and try to think with you here

Could a bad download of the theme messed something up ? Just thinking out loud as always !

Verstuurd van mijn HTC One X
[HTC One X] ionhide:
I dont know, i was not able to check, since i lost access to my phone. Will se if i can get it back from the shop today..
[HTC One X] -fluffy-:
my friend i have no problem with Hboot 1.28

im flashing back an forward between ics an JB rom

testing theme an so on no problem at all

---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------

if u get an bad download the recovery will tell u that u have a corrupt file

---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------

i have flashed many rom under 40% off power
[HTC One X] matt95:
flashing roms under 40% and flashing firmwares under 40% is very different ;)
[HTC One X] -fluffy-:
well as fare as i can read it said rom 40%
[HTC One X] matt95:
that's right! but the problem is flashing firmwares under 40% and not roms :) i always flash roms with very poor battery and don't make any difference... if you try to flash the firmware with less than 40% of battery you will get errors and you won't be able to upgrade and you will be stuck at that point till you recharge the phone
[Samsung Infuse 4G] DaMeatMan:
Hey Folks,

So i'm currently on Scott's latest 10/22 of jellybean goodness, and i'm wondering if there are any available tweaks to increase charging current on my device kernel tweaks or app of some kind?

Why i'm asking:

I typically find that when using nav and with screen set to a reasonably low brightness, and with stock clock speeds, my battery drains faster then my charger can charge it. So the end result is that my phone will eventually power off after a long ride. I don't alway's use GPS for turn by turn navigation, but i do like to have the navigation app on, and turned onto the "map page" to display the upcoming traffic congestion in and around where i'm driving via googles traffic colour coding.

What i'm using:

I'm currently using a 1 amp USB car charger, with about 5 feet of USB cable running down the right side of my seat to the far left windshield position. I know longer cable runs are not ideal since it increases current loss due to resistance of cable, however i really don't want to mount the device any place else in the vehicle.

Secondly, after a bit of searching i found that i needed to short out the two data pins D- and D+ in order to get my phone to recognize the charger as a dedicated AC charge port and draw more then 500 ma. This did work and my phone is now drawing more current when charging and it is now showing up as (AC charging) instead of (USB charging), however it does still slowly drain battery, albeit allot slower then before.

So back to my question. Is there anything else i can do from within the device itself to get the phone to draw more current when charging?