Develop Bugs

How can I enable true multitasking in ICS?

I love my Galaxy Nexus, but what's driving me crazy is how it shuts down any app whenever I switch out of it, even if I use the -completely useless so far- multitasking soft key. So for instance I'm waiting for a YouTube video to load, so I temporarily switch out of it to do something else (this is a smartphone isn't it) and come back, and find it reopening the video as if I just did it. Same thing with the browsers. I have 2-3 tabs open, and decided to check out something on the homescreen. Big mistake. When I get back will have to wait for all the tabs to reload.
Anyway to keep apps running in the background?
Sent from my Galaxy Nexus using XDA App

I think YouTube just does that. It has been mentioned before. No problem with the browser.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.

If your using a Verizon nexus, it partly has to do with Verizon's cdma network, not just android. Plus it would slow your phones operation down and you would see more force closes due to limited resources.
Edit— sorry everybody, did a little drunk forum trolling last night. Everything I posted was false. The other poster was correct and I deserve all the shame.
Transmitted from my Galaxy Tab 10.1 via Tapatalk

Most likely you have an app running thats killing processes. If you have any task manager/killer remove it immediately.
As far as youtube goes, youtube will NEVER keep a video paused or continue playing if you leave. It saves what you were on, but thats it. few reasons for that.
Now, my experience today and no issues.
Facebook, Browser (4 tabs), NFL'11, and twitter all running and they all saved what i was doing and none of them ever closed.
in fact, 3 hours after, the 4 tabs were still open. I've actually had tabs open for 3 days straight that i forgot to close and the browser just made new ones.
and these are not just text sites. I had the Battlefield 3 battlelog, nfl.com, battlefield wiki, and the verge mobile all on.

My browser will keep pages open for days if I wanted to...strange! You're using stock browser?
Sent from my NookColor using XDA Premium App

stock browser is awesome. especially the inverted mode.

Pretty amateur thread. Come on
Sent from my Galaxy Nexus using xda premium

Stardate Tab 10.1 said:
If your using a Verizon nexus, it partly has to do with Verizon's cdma network, not just android. Plus it would slow your phones operation down and you would see more force closes due to limited resources.
Transmitted from my Galaxy Tab 10.1 via Tapatalk
Click to expand...
Click to collapse
I can't find one fact in your entire statement. What could CDMA possibly have to do with it? Also, you wouldn't see more 'force closes'. When Android runs low on RAM it selects the oldest cached app and ends it, unless it's active.

once again, amateur thread. **** needs to be closed down

TareX said:
I love my Galaxy Nexus, but what's driving me crazy is how it shuts down any app whenever I switch out of it, even if I use the -completely useless so far- multitasking soft key. So for instance I'm waiting for a YouTube video to load, so I temporarily switch out of it to do something else (this is a smartphone isn't it) and come back, and find it reopening the video as if I just did it. Same thing with the browsers. I have 2-3 tabs open, and decided to check out something on the homescreen. Big mistake. When I get back will have to wait for all the tabs to reload.
Anyway to keep apps running in the background?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Do you have Don't keep activities checked in the development part of settings? Go to Settings>Developer Options, scroll all the way down, and look if you've enabled the option I've mentioned above
Sent from my Galaxy Nexus using xda premium

I have this exact same problem, with the browser and even with games.
I have no task manager. I have watchdog which i believe doesnt kill any processes itself and i have juice defender; could that be whats causing this problem?

I keep hearing about this, am I seriously the only one that can swipe apps away from the recent apps and they actually close?
Sent from my Google phone

ChongoDroid said:
I keep hearing about this, am I seriously the only one that can swipe apps away from the recent apps and they actually close?
Sent from my Google phone
Click to expand...
Click to collapse
possibly you are...
because for me and more than 5 of my friends using the same phone, those swiping aways only close the shortcut regardless of the app running in background or not.

DO THE FOLLOWING
1) go to settings, apps, running apps.
2) with that open, hit the multitask button that shows all apps running.
3) swipe away
4) watch it get killed off your running apps list.
5) grow up

Im not sure what all the *****iness is about but the problen I and i believe the OP were having was quite real and serious.
Any time you switched out of an app or game, even if only for a second, when you switched back it would restart the app or game and in the case of the browser reload the webpage.
Now, ive uninstalled watchdog and the problem seems to have gone away.
Is anybody else using watchdog having this problem?

People need to understand that devs put this code INTO THEIR APPS. Killswitches are hard coded into apps to let the system kill them if they have been in the background. A good example is Opera Mobile. It has a low priority that is coded in BY THE DEV.

schizophrenia said:
possibly you are...
because for me and more than 5 of my friends using the same phone, those swiping aways only close the shortcut regardless of the app running in background or not.
Click to expand...
Click to collapse
Not possibly, I know I am. Home key keeps it running, back key caches/closes it. Certain apps perform differently as foreground tasks and some as background tasks. I think some can't be multi tasked like big games and stuff but as previously said that's on the dev side not androids.
Sent from my Galaxy Nexus using xda premium

Swiping away in task list DOES kill the task

I have seen it posted by many users that swiping away apps in the mutitasking list does not kill the app. This is untrue according to Romain Guy. He states that it does indeed kill the app.
https://plus.google.com/105051985738280261832/posts/GfwRYCC42uX
Neal Sanche - On Ice Cream Sandwich does the swipe gesture in the recent tasks list do anything to the tasks? Does it kill them or just simply remove them from the list?
Jan 5, 2012
Romain Guy - +Neal Sanche It kills them
Jan 5, 2012 +5

Simple way to test this:
Reboot your phone, check your battery %, open Facebook and close it. Check your battery % after around an hour.
Now do the same, but this time swipe Facebook out of the task list, the drain will be much less.
Any time I get abnormally high battery drain, every single time i've forgotten to swipe away facebook.

I had always had my suspicions that people were wrong about it not kill apps because in the browser if you swipe it away then the browser starts over fresh when you open it.

My experience with the phone says otherwise. For example, do this:
- create a play/pause control widget with widgetsoid (free on the market)
- open Google Listen and start listening any podcast
- pause it, and then swipe Listen away from recent apps
- now go to your homescreen and push play on the widget......magic!
I think something still runs at the backstage even if you swipe away the app. Of course that might depend on the app, and who know if also on the Kerne/ROMl you are running.

I've noticed the GPS icon appearing for no reason after running Facebook.
Then when swiping away Facebook the GPS icon stops.
Sent from my Galaxy Nexus using XDA App

the swipe only kills tasks in the foreground, to test, run a music app like Google music, then remove it from the list, it'll continue to play. it's not really a good feature, useful for some apps but if Google wanted the ux to be more consistent and intuitive then this is a prime example of one they failed at
the right way to do this would be to treat it like a force kill, but with a confirmation for ones running a background process

It kills them... Swipe away the XDA app.. Swipe away the browser... It starts fresh..
as for the person that suggested the music not starting over.. You can pause a song, restart your phone and it will be paused at the same spot.. So that's why that doesn't restart when swiped away.
Sent from my GalaxyNexus using XDA App

wonshikee said:
the swipe only kills tasks in the foreground, to test, run a music app like Google music, then remove it from the list, it'll continue to play. it's not really a good feature, useful for some apps but if Google wanted the ux to be more consistent and intuitive then this is a prime example of one they failed at
the right way to do this would be to treat it like a force kill, but with a confirmation for ones running a background process
Click to expand...
Click to collapse
If you read in the link I posted, they go on to explain why things like music can continue to play. Honestly I don't really feel like pulling that information out for you, but the link is there so the information is there for you.

mysterioustko said:
If you read in the link I posted, they go on to explain why things like music can continue to play. Honestly I don't really feel like pulling that information out for you, but the link is there so the information is there for you.
Click to expand...
Click to collapse
you don't seem to get my point, it's not about what Google wants, it's about user expectation. it's clearly a task killer and it doesn't behave the way you expect a task killer yo behave. this is why people love apples crap - it works the way you expect it to. obviously Google wants the function to work differently, so they need to presnt it differently so people aren't confused
that was a big point from duartes, that people don't love android, and yet they still don't really get
it fully. hopefully jelly bean picks up where ics has failed so aaple can go back to the little **** hole it belong in

wonshikee said:
you don't seem to get my point, it's not about what Google wants, it's about user expectation. it's clearly a task killer and it doesn't behave the way you expect a task killer yo behave. this is why people love apples crap - it works the way you expect it to. obviously Google wants the function to work differently, so they need to presnt it differently so people aren't confused
that was a big point from duartes, that people don't love android, and yet they still don't really get
it fully. hopefully jelly bean picks up where ics has failed so aaple can go back to the little **** hole it belong in
Click to expand...
Click to collapse
So basically you still have not read anything on that link.....

I see a debate team in the making whahahaaha
But seriousley.... the artical is inspired on appel ios..... i think its a little different
Then ics...
But i see the general meaning about it,ics recent app key doesnt kil procceses of the android system thus doesnt show it,right? And not important for the user
But in all fairness.... my ics recent app key doesnt kill annything though
Verstuurd van mijn GT-P1000 met Tapatalk

demon2112 said:
I see a debate team in the making whahahaaha
But seriousley.... the artical is inspired on appel ios..... i think its a little different
Then ics...
But i see the general meaning about it,ics recent app key doesnt kil procceses of the android system thus doesnt show it,right? And not important for the user
But in all fairness.... my ics recent app key doesnt kill annything though
Verstuurd van mijn GT-P1000 met Tapatalk
Click to expand...
Click to collapse
lol nah there can't be a debate if a person chooses to ignore the facts. BTW, I didn't mean the article, I meant read the comments on that particular post. They break down how the app killing works from the recent apps list. It doesn't work exactly like killing a task would in the "manage apps" area. It depends on the app that you are killing.

mysterioustko said:
lol nah there can't be a debate if a person chooses to ignore the facts. BTW, I didn't mean the article, I meant read the comments on that particular post. They break down how the app killing works from the recent apps list. It doesn't work exactly like killing a task would in the "manage apps" area. It depends on the app that you are killing.
Click to expand...
Click to collapse
i stand corrected.... download the app......active app... its widget looks like a chip
instal it.... pop the widget on home and open browser,clise it with home key and open market and close it aswell with home key....the widget will show that there are 2 active apps....open recent app key and swype away....when widget refreshes it says 0 apps........voila..it truly is a killer that key.......
oke im confinsed....its realy a killer...now evereyone can check for them selves
Verstuurd van mijn Galaxy Nexus met Tapatalk

mysterioustko said:
lol nah there can't be a debate if a person chooses to ignore the facts. BTW, I didn't mean the article, I meant read the comments on that particular post. They break down how the app killing works from the recent apps list. It doesn't work exactly like killing a task would in the "manage apps" area. It depends on the app that you are killing.
Click to expand...
Click to collapse
difference is i understand the facts, you don't seem to understand at all my point. you talk just like a developer who doesn't understand why the user can't see your way to do something when the reality is, its the end user that's the most important. you even agree that it's not a real task killer but you can't see why that's a bad thing b because you think everyone who uses android really gives a ****. the only thing the end user will see is that it's "broken" for some apps. im fully aware of how the task killer works in android yet you keep thinking that's the topic. feel like im talking to a brick
im not sure why this concept of meeting expectation is so hard to grasp
as i said before, if Google wants it to work a certain way they need to present the function differently so the user doesn't expect differently, such as not showing apps that it won't close anyway, or allowing force close through a confirmation

It actually does kill the apps... sometimes. If anyone would have bothered to search around, this has already been discussed in detail. If an application is dormant, swiping it away from the recent apps screen will kill it. If an application is not dormant and actively using system resources, it will not kill the application.

2 posts up people!!!!
and get the proof for yourselves!
Verstuurd van mijn Galaxy Nexus met Tapatalk

Swiping away Google Talk doesn't kill it.
Swiping away Pandora doesn't kill it.
Swiping away Google Talk doesn't kill it.
Swiping away Groupme doesn't kill it.
Swiping away Terminal Emulator doesn't kill it.
Swiping away Maps doesn't kill it.
Yeah...I think I have convinced myself that its not a task killer. The same tasks killed by swiping away are the same ones that hitting the back button kills in any other Android OS. Business as usual, and depends on how the app is coded. I didn't use a third party anything to check. I looked under running in Manage Apps.

pks check with that app and report back plz
Verstuurd van mijn Galaxy Nexus met Tapatalk

demon2112 said:
pks check with that app and report back plz
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I am not gonna use a third party app for what I can see in Running. For all I know (and its likely) the third party app is incorrect.

adrynalyne said:
I am not gonna use a third party app for what I can see in Running. For all I know (and its likely) the third party app is incorrect.
Click to expand...
Click to collapse
+1. All of you are talking about using crappy third party apps to check if swiping away an app kills it and preaching the results as gospel, none of you even knew how to check if an app is legitimately terminated. Smh. Swiping away apps in recent doesn't terminate it. All apps are coded differently. Learn about the OS before making claims of how a part of it operates in opossition to what its creators have stated.
Sent from my Galaxy Nexus using XDA App

Why don't browser pages stay in memory?

I've been wondering why my browser tabs get kicked out of memory after so long. Usually if I take a phone call or switch into a large app and return to the browser, I have to reload all my pages. I normally have 3-5 tabs open at once. With VZW's slow 3G it's a pain to reload and lose my place. Doesn't this phone have 1GB of RAM? I wouldn't think a phone call would cause the browser to be removed from memory would it? This has been plaguing me for years just wondering if there was anything I could do to prevent it.
Sent from my Galaxy Nexus using XDA App

Yes its just something to do with the latest ICS version, memory management is more aggressive with the browser or something. It drives me mad too. Sometimes ill switch to the homescreen for one second without loading a single thing, go right back to the broeser and it was kicked from memory.

Is the behaviour the same in the new Chrome Beta?

Yup, I find this a bit annoying, too.

DirkGently said:
Is the behaviour the same in the new Chrome Beta?
Click to expand...
Click to collapse
It doesn't seem to be. I've just had a test and it seems to keep all pages open.

Open browser -> load page -> menu -> save for offline reading

lilirose said:
Open browser -> load page -> menu -> save for offline reading
Click to expand...
Click to collapse
But wouldn't you then have to do this for each tab?

Because Android doesn't offer true multitasking. It closes apps you are actively using and caches apps you don't ever use... Poor memory management and aggressive task closing makes for a poor user experience.

EP2008 said:
Because Android doesn't offer true multitasking. It closes apps you are actively using and caches apps you don't ever use... Poor memory management and aggressive task closing makes for a poor user experience.
Click to expand...
Click to collapse
Yep. It's a little too aggressive. It's most annoying when i'm using Spotify or something. I might pause the music for a little while for whatever reason, run a couple apps. When I go back to Spotify I have to restart the whole app.
It should intelligently monitor usage and cache apps based off that...

tweak your VM settings, as well as min free settings.
My pages has always stayed in memory

s2d4 said:
tweak your VM settings, as well as min free settings.
My pages has always stayed in memory
Click to expand...
Click to collapse
Mind providing some examples and/or guidance on how to accomplish this?

s2d4 said:
tweak your VM settings, as well as min free settings.
My pages has always stayed in memory
Click to expand...
Click to collapse
Yeah this is what i want to try and tweak the oom numbers but i just been too lazy...

Hmm. I have never used Spotify before, but that sounds way too aggressive. I use slacker.com and if i pause it there does not seem to ever be a problem going back and having the song pick up right where i left off. Google listen seems to do the same. Now don't get me started on the one or two times per day slacker causes my galaxy nexus to reboot ......

rudolphe said:
Mind providing some examples and/or guidance on how to accomplish this?
Click to expand...
Click to collapse
Need it too...

I never experienced this. I have chrome and chrome beta with bunch of tabs in each of them open and they always stay there. I am on stock 4.1.1 and i have stock android browser disabled.
Sent from my Galaxy Nexus using xda app-developers app

ICS task manager... too much?

So me and my buddy both have a Gnex...
I tend to not really use the task button on the nav bar too much to swipe away tasks.
My buddy on the other hand likes to kill apps off EVERY SINGLE TIME he leaves an app. And i mean EVERY time, as soon as he leaves it he swipes its ass.
I think thats a bit much.
Ive always been under the impression that any kind of task killer can do more harm than good, as it slows things down when you reopen an app as it has to load it from scratch again.
My friend argues that your supposed to do it because thats the the button and feature is there for.
I would have thought that it was just there for in case you want to manually free up ram for what ever reason, or quickly jump between apps.
So whos doing the right thing and whos doing the wrong?

there is no right or wrong for this.. its all personal preference
i usually just keep it there until i kno i have reach like 10+ apps, then i just swipe them away cuz i dont want my list to be that long...
but when u say close every app every time.. i only do that when i kno it keeps running in the background sucking my cpu and battery ex. Facebook app
then i will swipe away every time i dont need it, while others i just keep it there

"task manager" its not a good definition for what it does
in real its show u the list of the last used apps and when u swipe away an app, u ONLY remove it from that list...it doesn't ( correctly ) kill anything
the real important thing, is that when u want exit from an app then press the back button to leave the app...the home button instead leave the app "running" in its state

andQlimax said:
"task manager" its not a good definition for what it does
in real its show u the list of the last used apps and when u swipe away an app, u ONLY remove it from that list...it doesn't ( correctly ) kill anything
the real important thing, is that when u want exit from an app then press the back button to leave the app...the home button instead leave the app "running" in its state
Click to expand...
Click to collapse
swiping away from multi-tasking UI DOES kill the app.. or u can say kill the activity, but if the app has a process, it will still be there.
but it definitely kill the app activity

From a simple test it doesn't kill any app for me.. try checking the apps running with quick system info or a similar app
Inviato dal mio Galaxy Nexus con Tapatalk 2

andQlimax said:
From a simple test it doesn't kill any app for me.. try checking the apps running with quick system info or a similar app
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
its been discussed in here xda (try the search button), AND from google android developer (her g+ post)
IT DOES KILL believe it or not

its purely personal preference when it comes to swiping away the tiles/icons/whatever, but he needs to realize that all he's doing is slowing down the resume/relaunch times of his apps, not to mention wasting minutes of his day swiping them away for (effectively) no reason. He's not going to see increased performance or battery life from constantly OCD closing the apps.

martonikaj said:
its purely personal preference when it comes to swiping away the tiles/icons/whatever, but he needs to realize that all he's doing is slowing down the resume/relaunch times of his apps, not to mention wasting minutes of his day swiping them away for (effectively) no reason. He's not going to see increased performance or battery life from constantly OCD closing the apps.
Click to expand...
Click to collapse
That...
And if there is an obnoxious app that he's killing...one that auto-starts itself again...
It'll waste battery as it restarts.
(These obnoxious apps should be avoided anyway, obviously.)

king23adrianc said:
its been discussed in here xda (try the search button), AND from google android developer (her g+ post)
IT DOES KILL believe it or not
Click to expand...
Click to collapse
it does not kill
u must use the search
its a list of recent used apps..u can remove apps from that list..not killing anything..and this is how should work

andQlimax said:
it does not kill
u must use the search
its a list of recent used apps..u can remove apps from that list..not killing anything..and this is how should work
Click to expand...
Click to collapse
lol whatever u say. i bet u didnt do any search

king23adrianc said:
lol whatever u say. i bet u didnt do any search
Click to expand...
Click to collapse
we can go on forever, but im sure about what im talking about..u are disinformed
are we talking of the same thing? pressing the ics built in multitasking button (on a stock rom) doesn't allow u to kill apps, only to remove it from that list
u can test it urslef in lot of way..also im not sure if u are trolling, but anyone here can confirm what im saying
i'm not going to reply again in this post

andQlimax said:
we can go on forever, but im sure about what im talking about..u are disinformed
are we talking of the same thing? pressing the ics built in multitasking button (on a stock rom) doesn't allow u to kill apps, only to remove it from that list
u can test it urslef in lot of way..also im not sure if u are trolling, but anyone here can confirm what im saying
i'm not going to reply again in this post
Click to expand...
Click to collapse
seems like ur trolling more cuz it has been proved it does kill the activity of an app when u swipe away in multitasking ui
try searching stuff before u say anything
http://forum.xda-developers.com/showthread.php?t=1445065&highlight=kill
edit: there are lots of videos on youtube of people posting it kills from swiping away
showing the difference between pressing home after opening the app, then swipe away, the app has to reload again. cuz it kills the activity

andQlimax said:
it does not kill
u must use the search
its a list of recent used apps..u can remove apps from that list..not killing anything..and this is how should work
Click to expand...
Click to collapse
Umm yeah, it does. It kills activities, but not associated services. Try it out first.

RogerPodacter said:
Umm yeah, it does. It kills activities, but not associated services. Try it out first.
Click to expand...
Click to collapse

galaxy nexus recent menu you button help!!

On my galaxy nexus when I hit the recent button I know when I swipe that it removes the application from the list but does it end it or just get rid of it from the recent menu
Sent from my Sprint Galaxy Nexus CDMA using Tapatalk

General mixed opinions, but if your worried about RAM, don't be. Android natively handles it better then you can possibly attempt to.
Sent from my Galaxy Nexus using XDA

killyouridols said:
General mixed opinions, but if your worried about RAM, don't be. Android natively handles it better then you can possibly attempt to.
Click to expand...
Click to collapse
Bingo.

mkeller96 said:
On my galaxy nexus when I hit the recent button I know when I swipe that it removes the application from the list but does it end it or just get rid of it from the recent menu
Sent from my Sprint Galaxy Nexus CDMA using Tapatalk
Click to expand...
Click to collapse
The recent list has absolutely no bearing one way or the other on whether an app is running in the background or not. They are two completely separate and distinct things.
Sent from my Galaxy Nexus using Tapatalk 2

najaboy said:
The recent list has absolutely no bearing one way or the other on whether an app is running in the background or not. They are two completely separate and distinct things.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Wrong. Try this, open xda app/hit home/now go to manage apps/running tab/at bottom hit "show cached processes"/and you'll see the xda app in that list/now hit recent button and swipe xda away/hit back/and watch xda disappear from the cached process list.
good day.

chopper the dog said:
Wrong. Try this, open xda app/hit home/now go to manage apps/running tab/at bottom hit "show cached processes"/and you'll see the xda app in that list/now hit recent button and swipe xda away/hit back/and watch xda disappear from the cached process list.
good day.
Click to expand...
Click to collapse
Apples and oranges. Cached processes and running background processes are two different things. A cached process is one that is not running, using no CPU or data.
To correctly check whether or not the two are tied merely entails force closing an app and then checking if it is gone from the recents list.
I did attempt to duplicate your observation, but there was no overlap between my recent apps and cached processes.
Sent from my Galaxy Nexus using Tapatalk 2

You know what I don't like? How androids 'Running Apps' screen always says Its using up a bunch of memory but fails to show you all the apps which only total up to about half.

When you swipe an app away, it kills it unless it has a reason to keep it open.
For example, swipe the browser away and it kills it. The last page will have to reload from scratch on launch.
Log in to IMO, then swipe it away and it keeps running. When you re-enter IMO it's exactly where it left off.
At least, that's my perception. Swiping it away tells Android OS that you don't need the app anymore, but it's ultimately up to the app/OS to decide whether or not it will be killed.

najaboy said:
Apples and oranges. Cached processes and running background processes are two different things. A cached process is one that is not running, using no CPU or data.
To correctly check whether or not the two are tied merely entails force closing an app and then checking if it is gone from the recents list.
I did attempt to duplicate your observation, but there was no overlap between my recent apps and cached processes.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not true at all.
"What specifically happens when you swipe away a recent task is it: (1) kills any background or empty processes of the application (see http://developer.android.com/guide/topics/fundamentals/processes-and-threads.html#Lifecycle for what this means), and (2) uses the new http://developer.android.com/reference/android/app/Service.html#onTaskRemoved(android.content.Intent) API to tell any services of the application about the task being removed so it can do whatever it thinks is appropriate.
There are really two major classes of things that run in the background: old processes of previously foreground apps (to speed up task switching), and processes that actively need to run indefinitely because of a service.
The first, background processes, are straight-forward -- they can be kept around, but the system can freely kill them whenever desired to free memory, and doing this basically has no impact on the user experience.
Where things get interesting is with services, which are basically how an application says "hey I need to be kept running in the background to do something." This may be to play some music, to fetch new e-mail, to perform navigation, to download a file, to update an app widget, and on and on. On devices that are tight on memory, it is these application services running that can cause memory pressure that is visible to the user."
https://plus.google.com/105051985738280261832/posts/GfwRYCC42uX