Help Issues multitasking (white/black screen, etc) on the HTC EVO 4G LTE

[guywithbluepants]

Biggest issue I had with multitasking is a couple of time when several things were open and I pressed multitasking button to see what was there once I slide up to apps the other apps that were there the icon either didn't show up or it was something else like maps had no icon gmail had phone icon pressed multitasking button again and once more to jump back in and it was fine

 

[Rose4uKy]

Well I just don't like when my sense reloads just cause it did it all the time on my 3D but on this phone since I've had it only a few times recently. So I thought maybe not backing out and going right to home had something to do with it I don't really know. But I'm still having trouble with text not sending sometimes and I am trying to send a picture now and it won't send. At work on my 3D there were always 2 spots i could go to to make my text send and I got text to come through on this phone they won't send and last night all at once after I had just gotten home all my text came through at once. My friend said maybe it's my phone I should trade it in for a new one. I hate to do that since I have everything on it already. But I don't know if an update will fix it or once we get LTE it will be better I don't know what to do.

That looks like a handy monitor and some things, like a cache cleaner or browser history cleaner, are perfectly ok. Just not memory managers or add-on task killers.

Apps use memory in the Linux services - if you go to settings, apps, find your app and Force close it, all memory for the app will be cleared properly - most all add-ons are hacks and don't do it right.

Monitor and task management tools vary wildly in their ability to tell the truth. Some will report actual ram memory used, others are actually reporting cached memory (as when an app is parked and not in ram) - killing or playing with apps that are parked in cache do nothing to help actual used ram at that instant - it just confuses the operating system.

If you don't see a problem hitting home instead of the back key, then don't sweat it. When you hit home, you're leaving many apps running - for some apps, there is no difference between home and the back key. If you home out of an app where it does matter, and you don't go back to it for a while, Android will sense that it's been idle and simply shuffle it out of ram to cache and leave a little ... let's call it an "address card" (very few bytes in memory) that tells the operating system where to go into cache to restore your app to the state it was once in. If it sits unused for too long, even that gets all cleared out.

The point is - Android tries to run as many things at once as it sensibly can. Because it knows it's not running on a PC with big memory and a hard disk, it will move things in and out of ram so that whatever you're running now will run efficiently (unlike Windows, where if you start running enough stuff, everything can slow down a lot) - but it gets that efficiency by putting apps to sleep, caching them and then even auto-killing them.

Android multitasking, as I've just described it above, is controlled by a set of complicated numbers that basically say what to do when and by how much. Those numbers are things that IOWA, myself, others and the dev community are tinkering with. The numbers are like a Rubic's cube - we want to solve as many sides of the puzzle as possible, not just one.

Ok, I hope this is all accessible and makes a lick of sense. If not, it's my obtuse writing style, not you, feedback what's unclear and I and/or others will hope to clarify.

PS - cache is a hidden part of the phone's 16 GB of storage, it's not ram.

 

[EarlyMon]

Texts ought not be affected by any multitasking. To narrow in on that, please if you can, hold down your power button for a good ten seconds - eventually, the capacitive buttons will flash and then your phone will reboot - that's the same thing as a battery pull on this phone. Then, go a day using only the phone and sms, nothing else, see if you can find any change in how texts are working out for you. Let us know what you find.

Meanwhile - news from the root multitasking trenches after hours under the hood on my phone monitoring everything -

As it turns out, it seems one dev is making a mistake on how his settings are for multitasking (his mods are not actually taking hold), and other devs have seem to have some settings that are in conflict with one another on this.

I've contacted those involved, so with a little luck, we may have some solutions to those issues pretty quickly.

I'm testing what I hope could be the final, simple cookbook now.

 

[IOWA]

So here's my relative finds so far.

I've set the android auto memory thresholds to the following, and it's improved multitasking a bit.

Foreground Application : 10MB
Visible Application: 12MB
Secondary Server : 20 MB
Content Provider : 40MB
Empty Application: 64MB

I've also lowered the VM Heap to 96MB from 128MB. (Considered the default VM Heap on my Shift was only 32MB, 96MB is still HUGE.)

There are a variety of ways you can tweak these settings, and if this stays consistent for the next week or so I'll write a batch zip that can apply these settings permanently. If that works, I'll post it on AF.

 

[EarlyMon]

Comparison when we're both at final will prove interesting.

 

[EarlyMon]

By the way - when we talk about multitasking, we're talking about what's apparent to the user.

Android multitasks, and it's often surprising for those unaware of how much is going on under the hood.

At the moment, I'm running a set of tests that involve streaming video with audio on headset, Talk session mirrored from my desktop to see if Talk notifications come in (yep, they do ), two system monitors running, a browser, and another streaming vid from another app all queued up and ready to go. Those are my apps, in addition to the messaging, time, weather and phone services running, as well as the launcher, of course.

Here's the list of processes that that really shakes out to -

Spoiler

[FONT=Courier New]130|root@android:/system/etc # ps
USER     PID   PPID  VSIZE  RSS     WCHAN    PC         NAME
root      1     0     508    376   c022da68 000086e8 S /init
root      2     0     0      0     c019867c 00000000 S kthreadd
root      3     2     0      0     c01810e4 00000000 S ksoftirqd/0
root      6     2     0      0     c01bc248 00000000 S migration/0
root      10    2     0      0     c01945f4 00000000 S khelper
root      11    2     0      0     c01945f4 00000000 S suspend_sys_syn
root      12    2     0      0     c01945f4 00000000 S suspend
root      13    2     0      0     c01945f4 00000000 S monitor_tsense_
root      15    2     0      0     c01945f4 00000000 S perflock_setrat
root      16    2     0      0     c01fa9dc 00000000 S sync_supers
root      17    2     0      0     c01fb9f8 00000000 S bdi-default
root      18    2     0      0     c01945f4 00000000 S kblockd
root      19    2     0      0     c04407a4 00000000 S msm_slim_ctrl_r
root      20    2     0      0     c01945f4 00000000 S msm_slim_sat
root      21    2     0      0     c0467698 00000000 S khubd
root      22    2     0      0     c01945f4 00000000 S pm8xxx-led
root      23    2     0      0     c01945f4 00000000 S l2cap
root      24    2     0      0     c01945f4 00000000 S a2mp
root      25    2     0      0     c01945f4 00000000 S cfg80211
root      26    2     0      0     c01945f4 00000000 S iewq
root      27    2     0      0     c01945f4 00000000 S rpciod
root      28    2     0      0     c01945f4 00000000 S modem_notifier
root      29    2     0      0     c01945f4 00000000 S smd_channel_clo
root      30    2     0      0     c01945f4 00000000 S qmi
root      31    2     0      0     c01945f4 00000000 S nmea
root      32    2     0      0     c01945f4 00000000 S msm_ipc_router
root      33    2     0      0     c01945f4 00000000 S apr_driver
root      34    2     0      0     c01945f4 00000000 S charger_ctrl_ti
root      35    2     0      0     c01945f4 00000000 S batt_timer
root      36    2     0      0     c01f3288 00000000 S kswapd0
root      37    2     0      0     c02503e8 00000000 S fsnotify_mark
root      38    2     0      0     c01945f4 00000000 S nfsiod
root      39    2     0      0     c01945f4 00000000 S crypto
root      53    2     0      0     c01945f4 00000000 S mdp_dma_wq
root      54    2     0      0     c01945f4 00000000 S mdp_vsync_wq
root      55    2     0      0     c01945f4 00000000 S mdp_hist_wq
root      56    2     0      0     c01945f4 00000000 S mdp_pipe_ctrl_w
root      57    2     0      0     c01945f4 00000000 S mdp_cursor_ctrl
root      59    2     0      0     c01945f4 00000000 S mhl_sii9234_wq
root      60    2     0      0     c01945f4 00000000 S vidc_worker_que
root      61    2     0      0     c01945f4 00000000 S vidc_timer_wq
root      62    2     0      0     c01945f4 00000000 S kgsl-3d0
root      63    2     0      0     c01945f4 00000000 S kgsl-2d0
root      64    2     0      0     c01945f4 00000000 S kgsl-2d1
root      65    2     0      0     c01bd788 00000000 S irq/350-tabla
root      66    2     0      0     c01945f4 00000000 S spi_qsd.1
root      73    2     0      0     c01945f4 00000000 S msm_hsusb
root      74    2     0      0     c01945f4 00000000 S f_mtp
root      75    2     0      0     c049e154 00000000 S file-storage
root      76    2     0      0     c01945f4 00000000 S diag_wq
root      78    2     0      0     c01945f4 00000000 S kpsmoused
root      79    2     0      0     c01bd788 00000000 S irq/295-synapti
root      80    2     0      0     c01945f4 00000000 S cm3629_wq
root      81    2     0      0     c01945f4 00000000 S detect
root      82    2     0      0     c01945f4 00000000 S button
root      83    2     0      0     c01945f4 00000000 S HS_PMIC_DETECT
root      84    2     0      0     c01945f4 00000000 S HS_PMIC_BUTTON
root      85    2     0      0     c01945f4 00000000 S cable_detect
root      86    2     0      0     c01bd788 00000000 S irq/298-msm-sdc
root      87    2     0      0     c01945f4 00000000 S tps61310_wq
root      88    2     0      0     c01945f4 00000000 S binder
root      89    2     0      0     c0732b24 00000000 S krfcommd
root      90    2     0      0     c01945f4 00000000 S msm-cpufreq
root      91    2     0      0     c01945f4 00000000 S bam_dmux_rx
root      92    2     0      0     c01945f4 00000000 S bam_dmux_tx
root      95    2     0      0     c0579054 00000000 S mmcqd/0
root      97    2     0      0     c057921c 00000000 S sd-qd
root      98    2     0      0     c01945f4 00000000 S rq_stats
root      99    2     0      0     c01945f4 00000000 S cabc_wq
root      100   2     0      0     c01945f4 00000000 S hdmi_hdcp
root      101   2     0      0     c01bd788 00000000 S irq/111-hdmi_ms
root      103   1     332    200   c022da68 000086e8 S /sbin/ueventd
root      104   2     0      0     c01945f4 00000000 S keychord
root      105   2     0      0     c02b0a40 00000000 S jbd2/mmcblk0p35
root      106   2     0      0     c01945f4 00000000 S ext4-dio-unwrit
root      107   2     0      0     c02b0a40 00000000 S jbd2/mmcblk0p37
root      108   2     0      0     c01945f4 00000000 S ext4-dio-unwrit
root      109   2     0      0     c02b0a40 00000000 S jbd2/mmcblk0p36
root      110   2     0      0     c01945f4 00000000 S ext4-dio-unwrit
root      111   2     0      0     c02b0a40 00000000 S jbd2/mmcblk0p26
root      112   2     0      0     c01945f4 00000000 S ext4-dio-unwrit
log       180   1     780    232   c03cef14 400727b8 S /system/bin/logwrapper
system    181   1     928    248   c05934d8 400489f0 S /system/bin/servicemanager
root      182   1     4200   520   ffffffff 400e6ff4 S /system/bin/vold
radio     185   1     14012  1920  ffffffff ffff0520 S /system/bin/rild
system    186   1     90160  6876  ffffffff 401079f0 S /system/bin/surfaceflinger
root      187   1     297956 36516 ffffffff 400e5b14 S zygote
drm       188   1     12940  1456  ffffffff 401089f0 S /system/bin/drmserver
media     189   1     120668 31124 ffffffff 4017d9f0 S /system/bin/mediaserver
root      190   1     13584  1548  ffffffff 40182978 S /system/bin/htcfs
bluetooth 191   1     1324   324   c022da68 ffff0520 S /system/bin/dbus-daemon
root      192   1     976    316   c06b7dd4 401007b8 S /system/bin/installd
root      193   180   0      0     c017e4fc 00000000 Z busybox
keystore  194   1     1852   340   c06084f0 400c22f8 S /system/bin/keystore
radio     196   1     10860  636   ffffffff 4002cb14 S /system/bin/qmuxd
radio     197   1     5884   668   ffffffff 4009e978 S /system/bin/netmgrd
root      200   1     14452  820   ffffffff 400cb978 S /system/bin/DxDrmServerIpc
root      201   1     344    116   c019d1d4 0000854c S /sbin/tpd
compass   202   1     1244   332   c019d1d4 40105ff4 S /system/bin/akmd
root      203   1     3708   1036  ffffffff 4019c2f8 S /system/bin/dmagent
system    204   1     2224   772   c022da68 ffff0520 S /system/bin/mm-qcamera-daemon
root      206   1     12132  672   ffffffff 40071978 S /system/bin/thermald
nobody    218   1     9456   408   ffffffff 400b3b14 S /system/bin/rmt_storage
root      219   1     8180   888   ffffffff 400249f0 S /system/bin/hdmid
root      220   1     1224   396   c022da68 40038b14 S /system/bin/htc_ebdlogd
root      242   220   852    364   c022da68 40010b14 S /system/bin/logcat2
root      267   1     868    308   c0109558 400961d4 S /system/bin/sh
root      327   2     0      0     c0240008 00000000 S flush-179:0
root      428   2     0      0     c01945f4 00000000 S smd_xprt
root      429   2     0      0     c01945f4 00000000 S msm_ipc_router_
system    494   187   484232 71028 ffffffff 400e59f0 S system_server
root      751   2     0      0     c01945f4 00000000 S hci0
bluetooth 759   1     2292   480   c022da68 ffff0520 S /system/bin/bluetoothd
system    905   187   382576 70756 ffffffff 400e676c S com.android.systemui
app_178   1000  187   380716 51784 ffffffff 400e676c S com.htc.idlescreen.shortcut
app_211   1014  187   331784 50992 ffffffff 400e676c S com.touchtype.swiftkey
radio     1035  187   374736 48036 ffffffff 400e676c S com.android.phone
app_20    1073  187   370708 58668 ffffffff 400e676c S android.process.acore
nfc       1089  187   315288 35792 ffffffff 400e676c S com.android.nfc
app_202   1177  187   344712 80812 ffffffff 400e676c S com.teslacoilsw.launcher
root      1610  1     5320   392   ffffffff 4002a978 S /system/bin/mpdecision
app_206   2967  187   365156 59264 ffffffff 400e676c S org.uguess.android.sysinfo.pro
system    5991  494   0      0     c017e4fc 00000000 Z DumpMemoryInfo
root      7083  1     3744   424   c06084f0 400252f8 S /system/bin/debuggerd
root      7084  1     8412   1084  ffffffff 400e6ff4 S /system/bin/netd
system    7409  494   0      0     c017e4fc 00000000 Z DumpMemoryInfo
root      7629  2     0      0     c0133918 00000000 D kworker/u:2
app_199   8552  187   344392 49300 ffffffff 400e676c S com.imo.android.imoim
app_48    8695  187   316784 40472 ffffffff 400e676c S com.htc.android.htcime:provider_latin
root      9495  2     0      0     c0192d6c 00000000 S kworker/u:3
root      9873  24977 876    388   c0109558 400c31d4 S /system/bin/sh
app_19    10962 187   349860 45120 ffffffff 400e676c S com.google.process.gapps
system    11373 494   0      0     c017e4fc 00000000 Z DumpMemoryInfo
app_20    11478 187   323856 38652 ffffffff 400e676c S com.android.htccontacts
app_188   11584 187   308620 39996 ffffffff 400e676c S netgenius.bizcal
system    11635 187   322856 38348 ffffffff 400e676c S com.android.settings
root      12959 2     0      0     c0192d6c 00000000 S kworker/u:4
app_161   13105 187   422692 114732 ffffffff 400e676c S com.boatbrowser.free
root      13598 2     0      0     c0192d6c 00000000 S kworker/0:1
root      13615 2     0      0     c0192d6c 00000000 S kworker/u:1
root      13616 2     0      0     c0192d6c 00000000 S kworker/0:0
root      13630 2     0      0     c0240008 00000000 S flush-0:18
root      13631 2     0      0     c0240008 00000000 S flush-179:64
app_129   13665 187   308448 35688 ffffffff 400e676c S com.htc.cs
app_36    13741 187   324452 41248 ffffffff 400e676c S com.google.android.apps.maps:NetworkLocationService
app_36    13777 187   318260 40308 ffffffff 400e676c S com.google.android.apps.maps:LocationFriendService
app_192   13802 187   397744 82704 ffffffff 400e676c S com.crunchyroll.crunchyroid
root      13850 2     0      0     c0192d6c 00000000 S kworker/0:3
app_67    13900 187   310496 37776 ffffffff 400e676c S com.redbend.vdmc
app_24    13919 187   316760 41856 ffffffff 400e676c S com.droid27.d3flipclockweather
app_52    14015 187   307448 35780 ffffffff 400e676c S com.htc.HtcBeatsNotify
app_25    14040 187   310692 39568 ffffffff 400e676c S android.process.media
root      14065 2     0      0     c0192d6c 00000000 S kworker/u:0
app_134   14070 187   309052 36068 ffffffff 400e676c S com.htc.task
app_183   14090 187   313612 43232 ffffffff 400e676c S com.coremobility.app.vnotes
app_150   14343 187   326532 48956 ffffffff 400e676c S com.amazon.venezia
root      14397 267   1040   336   c019d1d4 40035ff4 S sleep
root      14398 2     0      0     c01bc248 00000000 S migration/1
root      14399 2     0      0     c0192d6c 00000000 S kworker/1:0
root      14400 2     0      0     c01810e4 00000000 S ksoftirqd/1
root      14401 2     0      0     c0192d6c 00000000 S kworker/1:1
root      14402 9873  1048   380   00000000 4001f7b8 R ps
root      24977 1     4580   260   ffffffff 0000825c S /sbin/adbd
root      31108 2     0      0     bf009480 00000000 S WD_Thread
root      31109 2     0      0     bf00a108 00000000 S MC_Thread
root      31110 2     0      0     bf009c5c 00000000 S TX_Thread
root      31111 2     0      0     bf00984c 00000000 S RX_Thread
log       31116 1     780    248   c03cef14 400c27b8 S /system/bin/logwrapper
wifi      31117 31116 2684   812   c022da68 4000cb14 S /system/bin/wpa_supplicant
dhcp      31144 1     1016   364   c022da68 ffff0520 S /system/bin/dhcpcd
[/FONT]

Anyway - the above shows why I said that tinkering with memory parameters is like playing with a Rubic's cube.

 

[EarlyMon]

So, I took the Evo 3D settings and tweaked the last two, kept the others, not terrible.

I'm able to leave and re-enter video streams without losing my place and also keep 7 web pages open without my browser losing its mind.

 

[ren857]

So an app like this I shouldn't get Android Assistant(18 features) | AppBrain Android Market

I have a habit of hitting my home button alot and not backing out of apps but I should back out right? I love this phone and it just reloaded again when I unlocked the phone just now. I'll deal with it I'm still glad I got this phone it's great. I know to not use task killers but why does out phone come with task like our 3D did? I never have downloaded one but I have used a memory booster to help the memory but then I deleted it also on my 3D after all my reloading problems.

Did you try restarting the phone? I did that and it fixed my reloading issues. I know to do that now when sense starts to act all wonky.

Also from another thread on AF:

settings>developer options and under Application settings make sure Don't Keep Activities is unchecked and Background Process Limit is set to use the Standard Limit option. Once this is done, restart your Evo 46 LTE by holding the power button and choosing restart.

 

[Holeshot88]

It's very frustrating expescially when I'm trying to show off my new phone and getting the loading screen. What gives? I have done a factory reset, cleared the google wallet, just in case. But it happens just about everytime I browse a few pages on dolphin, looking through pulse etc.

 

[Rose4uKy]

I have rebooted my phone but I just checked my developer settings and they were what they were suppose to be. I also didn't know about holding the power button down for 10 seconds and seeing the buttons flash was like a battery pull so I did that. I am still getting an occasional sense reload not sure if I got any today maybe once I forget but all my text have been sending today so that's good.

I still love this phone. I was at a concert last night inside of Belterra casino and I had no signal at all couldn't upload a pic or anything but once it was over and I got to the slot machines it was working fine good 3G. But if I have no 3G signal shouldn't I roam and be able to do stuff? That confuses me I know we roam on Verizon so maybe Verizon people didn't have a signal too I don't know. At my work AT&T people have signals where mine don't. But I love Sprint and there unlimited data so I'll with Sprint. This phone is great!

Did you try restarting the phone? I did that and it fixed my reloading issues. I know to do that now when sense starts to act all wonky.

Also from another thread on AF:

 

[EarlyMon]

It's very frustrating expescially when I'm trying to show off my new phone and getting the loading screen. What gives? I have done a factory reset, cleared the google wallet, just in case. But it happens just about everytime I browse a few pages on dolphin, looking through pulse etc.

I've merged your question here, you may wish to review this thread for the deal on that.

 

[EarlyMon]

I have rebooted my phone but I just checked my developer settings and they were what they were suppose to be. I also didn't know about holding the power button down for 10 seconds and seeing the buttons flash was like a battery pull so I did that. I am still getting an occasional sense reload not sure if I got any today maybe once I forget but all my text have been sending today so that's good.

I still love this phone. I was at a concert last night inside of Belterra casino and I had no signal at all couldn't upload a pic or anything but once it was over and I got to the slot machines it was working fine good 3G. But if I have no 3G signal shouldn't I roam and be able to do stuff? That confuses me I know we roam on Verizon so maybe Verizon people didn't have a signal too I don't know. At my work AT&T people have signals where mine don't. But I love Sprint and there unlimited data so I'll with Sprint. This phone is great!

I think you're in a poor signal area and that's all there is.

 

[dr g]

I hope I'm not going over ground already covered or using the wrong thread, but exactly what happens when you "toss" a card from the multitasking "deck"? It doesn't seem to kill the task like task manager.

 

[EarlyMon]

I hope I'm not going over ground already covered or using the wrong thread, but exactly what happens when you "toss" a card from the multitasking "deck"? It doesn't seem to kill the task like task manager.

In some ways, it works better. It will completely remove a fresh app from memory, and it will remove the stub of one sleeping. The HTC Task Manager doesn't accurately display running apps, and the multitasking deck only shows apps you've opened.

 

[dr g]

In some ways, it works better. It will completely remove a fresh app from memory, and it will remove the stub of one sleeping. The HTC Task Manager doesn't accurately display running apps, and the multitasking deck only shows apps you've opened.

Hm. Well for example, there is a glitch I get with the facebook app. When I take a photo and upload it to facebook using the facebook app (not facebook for sense), it sometimes will show two progress bars in notifications, of which only one will move. It will complete and erase, but the second progress bar will remain indefinitely in notifications. The only way I have found to remove that dead notification is to kill the facebook app with task manager. Flicking it out of the multitasking deck doesn't do it.

 

[Rose4uKy]

Yeah I know that especially in my house and at work. I use wifi always when I can though. But out of town at this casino with no free wifi it really sucked in one spot. But another concert here in town last week it worked better than my 3D and was uploading pics to FB and doing good so it varied I guess. But I am not giving up this phone or Sprint's unlimited data just for a not so good signal in a few spots. LOL! I love this phone. We never got 4G here but it worked in one or two spots by my house it was weird. I really hope LTE gets here at least by next year like they say. Now I know this has been asked but if you don't have LTE your phone should be on CDMA only right? Someone said 3G is better with that on but I think I had it on and then put it back. I do have my NFC still on though was messing with Android Beam and knew I was gonna try the tags here soon so I left it on and haven't noticed a difference in battery drain with it on.

I think you're in a poor signal area and that's all there is.

 

[EarlyMon]

Rose - the CDMA with LTE on/off has some discussion about which speed is better, but those results are anecdotal - and connectivity ought not be affected, but if you find a setting that works better, go for it because we don't know exactly what's going on the hood for radio management. Use what works for you.

Hm. Well for example, there is a glitch I get with the facebook app. When I take a photo and upload it to facebook using the facebook app (not facebook for sense), it sometimes will show two progress bars in notifications, of which only one will move. It will complete and erase, but the second progress bar will remain indefinitely in notifications. The only way I have found to remove that dead notification is to kill the facebook app with task manager. Flicking it out of the multitasking deck doesn't do it.

I think that's part of a known Facebook bug that is addressed in the viperROM for rooted users - sorry, I don't use FB, just passing on my understanding from reading others comments.

 

[dr g]

I think that's part of a known Facebook bug that is addressed in the viperROM for rooted users - sorry, I don't use FB, just passing on my understanding from reading others comments.

I have now seen a couple other glitches that left notifications and required task termination, which tossing from the multitask deck did not solve while killing in task manager did. In particular, I ran into the issue with a Jetcet print task earlier, which glitched out with my printer and was unable to print.

Speaking of which, now I'm on the lookout for a fix there. I like the Jetcet integration.

 

[Rose4uKy]

Yeah I've noticed that too when uploading a pic to FB I see it up top and it says on going and I usually just reboot my phone and it's gone. I also see the one that moves and says 100% and the one stays at the top and it says ongoing.

QUOTE=dr g;4534772]Hm. Well for example, there is a glitch I get with the facebook app. When I take a photo and upload it to facebook using the facebook app (not facebook for sense), it sometimes will show two progress bars in notifications, of which only one will move. It will complete and erase, but the second progress bar will remain indefinitely in notifications. The only way I have found to remove that dead notification is to kill the facebook app with task manager. Flicking it out of the multitasking deck doesn't do it.[/QUOTE]

 

[dr g]

Yeah I've noticed that too when uploading a pic to FB I see it up top and it says on going and I usually just reboot my phone and it's gone. I also see the one that moves and says 100% and the one stays at the top and it says ongoing.

You should be able to get rid of it by killing facebook with the task manager.

 

[Rose4uKy]

Thanks, I saw you wrote that. I was restarting phone where it closed all apps and rebooted. But I guess that's quicker and easier.

You should be able to get rid of it by killing facebook with the task manager.

 

[strider70]

So here's my relative finds so far.

I've set the android auto memory thresholds to the following, and it's improved multitasking a bit.

Foreground Application : 10MB
Visible Application: 12MB
Secondary Server : 20 MB
Content Provider : 40MB
Empty Application: 64MB

I've also lowered the VM Heap to 96MB from 128MB. (Considered the default VM Heap on my Shift was only 32MB, 96MB is still HUGE.)

There are a variety of ways you can tweak these settings, and if this stays consistent for the next week or so I'll write a batch zip that can apply these settings permanently. If that works, I'll post it on AF.

Cool. Does anyone have any links to provide so I get learn how you guys are able to mess with these settings? I'm very intrigued.

Wouldn't lowering the heap in the VM cause garbage collection to occur more frequently?

 

[IOWA]

Cool. Does anyone have any links to provide so I get learn how you guys are able to mess with these settings? I'm very intrigued.

Wouldn't lowering the heap in the VM cause garbage collection to occur more frequently?

The VM heap is what each 'sandbox' is allowed to take up as a maximum.

So by lowering the heap, (in theory anyway) Android will move RAM around inside that application to accommodate that VM heap instead of killing other applications.

This allows more RAM to be left over for other applications by limiting how much RAM an application can have. This is very useful for memory hungry apps like the browsers or games.

The default VM Heap of 128Meg is the largest I've ever seen, and I'm still playing with VM heap sizes to determine the best fit.

Given the VM Heap used on my three phones with 512mb RAM(Epic, OG Evo, and Shift) was between 32 and 48 mb, a VM Heap size of 96mb is still huge by comparison.

With this being said, I have noticed improved multitasking performance with these settings(actually tweaked them a bit more).

Between EarlyMon and I we should be able to find the 'sweet spot' as he's doing his own experiments using his own values. FWIW our current values are very similar, and we're both getting better results than before.

 

[EarlyMon]

Lowering the VM heapsize can increase the number of smaller apps running at once and provide faster response switching between them, but can lead to crashes on memory intensive apps. For those, a larger heapsize is needed to prevent crashing.

Again, it's part of the necessary balancing act.

If you are rooted, make frequent nandroid backups, and don't care about driving your rom to crashing and you're using the stock rom, then you can try Rom Toolbox. If you don't know what you're doing and don't make nandroid backups then you ought not even consider experimenting.

 

[P_Dub]

I just wanted to let people know that i have not had this issue much at all after removing the stock widgets from all the home screens.

Also, the stock browser doesn't always reload open tabs, now. It still does occasionaly, though.

I only have friendstream, gmail, and google search widgets on 3 different screens. One other good thing since doing this is the gmail widget actually updates now. It used to show the same emails from when I first loaded it and would only update when Sense had to redraw, which was getting quite annoying.

I ticked the 2D option and will let you know of anything different that I notice.