The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??
AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.
Jubakuba said:
AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.
Click to expand...
Click to collapse
Yea I see what you mean, im just wondering how Cydia for iOS interacts with the ROM to apply patches then..?? how have they managed to implement this kind of system?
FNV looks interesting but a little dead. On the other hand, I like how actively updated CM10 is, and it doesn't look like support is going to stop there anytime soon which is a big plus.
UKROB86 said:
The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??
Click to expand...
Click to collapse
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2
akash3656 said:
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yea I get what your saying.
Im not complaining about dead ROMs just was trying to think if there was a workaround. But yes I see your point about how a ROM developed from source would be less likely to lag.
I've been on CNA for awhile now, since AOKP slowed right now, and CNA is amazing. I guess CM10 is always a good backup if any of these ROM's stop updates.
thanks anyways.
Dont worry, you'll get your precious roms - this is an aosp device, after all.
Sent from my i9250
Related
Been working on it for a week or so now, and finally happy with what I've got. Still bits to do, but hey-ho!
It's a run-of-the-mill IML74K ROM build from the Master branch from AOSP. I've not used any CM Sources like many of the current crop of AOSP-build ROM's, and only forked specific sections which I do need (such as peteralfonso's vendor tree, and the vendor_samsung tree from TeamKANG), but I've also done some work on my own forks of these too so to suit what I want from them/fix things which were bugging me. So in my opinion, it's quite clean in that respect, other than a few slight modifications I've made to it (very few so far)
Given how many AOSP ROM's are on here at the moment for 4.0.3, and as this is more of a personal-taste ROM, not sure if it's worth putting out there, as it really is going to be built purely to suit my own needs, and I know quite a few people want x feature included, and if I don't want/need said feature, I won't be including it...
It was purely due to this post which has made me think...
Duno... torn... I might just eat cake for dinner instead!
Considering to amount of trolls you will encounter who ***** when they don't get what they want I would just ask people to pm you if they want to ROM to try out.
Sent from my DESIRE using XDA App
Very true!
Main reason I built mine was I wasn't happy with the notification icon's being so dim, and as no other AOSP-built ROM's altered the brightness of the icons, I just decided to build from AOSP with that changed rather than modify an existing ROM. So while I was at it, just chucked a few other items in the mix too.
End of the day, it's a developer phone, so it's always good to have a tinker with it IMO
make a rom with transparent top and bottom to get more screen estate and many will jump on your rom. also, add feauture to adjust soft key buttons colors and give bouncy web browser effect and you are golden.
cordell507 said:
Considering to amount of trolls you will encounter who ***** when they don't get what they want I would just ask people to pm you if they want to ROM to try out.
Sent from my DESIRE using XDA App
Click to expand...
Click to collapse
This ^^^^^^^
Does any one else think that Google should be spending a lot more time here on xda and learning from the devs?
Just little features like being able to hide and unhide the nav bar, and edit the buttons of the nav bar...
Getting the smoothness of the stock launcher sorted once and for all that some custom rooms have managed...
The few extra targets on the lock screen.
You get the idea. Just little tweaks that are missing from stock that I feel should have been added from the start.
A company that large with that much resource should surely b thinking of these things before Joe bloggs comes along and adds it for them.
Sent from my Galaxy Nexus using XDA
zolah said:
Does any one else think that Google should be spending a lot more time here on xda and learning from the devs?
Just little features like being able to hide and unhide the nav bar, and edit the buttons of the nav bar...
Getting the smoothness of the stock launcher sorted once and for all that some custom rooms have managed...
The few extra targets on the lock screen.
You get the idea. Just little tweaks that are missing from stock that I feel should have been added from the start.
A company that large with that much resource should surely b thinking of these things before Joe bloggs comes along and adds it for them.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If I recall correctly some of the new features in ICS from the Cynogenmod team (the only one that I can recall is the swipe away notification menu list).
But yea I agree, those little tweaks that you mentioned would be sweet to have in future releases of android...and who knows maybe they are paying attention and in the next (major) update of theirs we might get new features.
Yes/No.
I'm sure some Google employees might check sites like this from time to time, but more often than not they're aware of bugs before most of the XDA population notices them. Legitimate issues will be reported to their bug tracker quickly I'm sure.
People may get impatient waiting for a fix, thinking, the Big G is oblivious, but the majority of the time they're a few steps ahead of most users here and a fix has been in the pipe for a while. I'm sure it's someone's, or someTHING's job, to harvest pertinent info; Google is in the information biz after all. I doubt any Google (or AOSP) presence would ever be officially declared here; I can't picture that going well.
There is a gerrit for code submissions. If they are not submitted, good luck in seeing them considered for implementation.
However, devs like us tend to introduce problems as well. Unless it can fit into the master branch for all supported AOSP devices and appears to not cause issues with other items, it will be immediately thrown out.
Ever read rom threads? At least half the posts stem from problems that were created from tampering with code/adding features.
..and I don't want to hear "insert rom" is bugless, because it is not true for any rom.
adrynalyne said:
There is a gerrit for code submissions. If they are not submitted, good luck in seeing them considered for implementation.
However, devs like us tend to introduce problems as well. Unless it can fit into the master branch for all supported AOSP devices and appears to not cause issues with other items, it will not be immediately thrown out.
Ever read rom threads? At least half the posts stem from problems that were created from tampering with code/adding features.
..and I don't want to hear "insert rom" is bugless, because it is not true for any rom.
Click to expand...
Click to collapse
Good point for sure. I definitely do not want my phone to ship with the instability custom ROM lol.
And people won't be satisfied either way. They're gonna ROM their phone anyways, not all of these things need to be included in the shipping software.
Um...Google knows man. Come on, they are the largest search engine in the world. They know what CM team has added, they know what people dislike about their products, they know EVERYTHING.
I'm sure they are learning from the devs, also have to realize a lot of the things CM adds and the fact Google doesn't include a lot of the stuff is good for the mass, a lot of my friends have a Android phones.
I always root their phones and add toggles and the extra features and they don't even realize or use them because they don't care, but I'm sure they know what people do want and what people don't based on their search histories.
I thought about this the other day...
If any of these ROMs and Kernels were actually significantly better without compromising stability then the Google devs would be out of a job pretty quickly.
I think the main advantages of custom ROMs and kernels are:
- customization above and beyond standard - but Google wants too keep a uniform ICS theme.. and adding too much detracts from this... not to mention over complicating menus and settings
- performance from overclocking - again something Google doesn't want to do for stability and hardware reasons
- getting new releases and sources before OTA updates - for the phones that are Samsung controlled which have to wait ages for them.. and you can flash a stock image for this anyway.
So custom ROMs don't really add that much that Google would want in its stock builds
I love CyanogenMod, I really do. It is constantly improving and the devs working on it obviously work very hard to keep things running smoothly. However, with a codebase this large, constant improvements inevitably leads to a fairly consistent stream of new bugs amidst the improvements. I understand that nightlies are not intended to be used as daily drivers, although usually they are stable enough for most here at XDA.
Acknowledging all of this: I can't help but wish on some days that I could take the excellent skills/care/devotion of the CyanogenMod team and have them devote a fraction of their work to create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs. This would be an incredible stop-gap between the initial build of a new CM nightlie (say, CM11) and the inevitable stable release.
This is NOT a statement against the added mods/apps to CyanogenMod (File Manager, Apollo, DSP Manager, etc.), I am very much of the opinion that these additions are beneficial, even necessary to the growth of CyanogenMod.
I do not expect this to happen, and I especially do not expect them to go back through CM10 and line-by-line strip all of their adjustments/additions. I understand that they are all very busy at work to keep us happy, and I appreciate that. Think of this as wishful thinking from a big fan.
Am I alone in this opinion?
it is called an AOSP rom. in this case vanilla. get a nexus device for that
Obviously, but I think you're missing my point...or you didn't read my post.
ohfoxxxycole said:
create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs.
Click to expand...
Click to collapse
A vanilla android rom with a custom kernel
Sent from my SPH-L710 using xda app-developers app
XxSilent.NightmarexX said:
A vanilla android rom with a custom kernel
Click to expand...
Click to collapse
Yes, but done by devs that know what they're doing.
Every single dev here knows what they are doing. Plus aosp is easy to compile for any device
Sent from my SPH-L710 using xda app-developers app
I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.
no, thats just because AOSP roms lack features that people crave from CM or AOKP
Alright, so we're back to my initial post now.
In other words an aosp pure android rom is not people look forward to. Cm10 stable rom is there and probably with like one minor bug or two.
Sent from my SPH-L710 using xda app-developers app
I know how you feel; I wish they would release a stable ROM for those that prefer stability over speed/features
EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app
ohfoxxxycole said:
EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.
There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Click to expand...
Click to collapse
this is true, but i'd be using this with mostly stock software + social network feeds and games only
the milestones are a great idea, and probably the closest thing im going to get to this, but they are still snapshots of mostly stable aosp with many many tweaks to keep modifications that i may or may not use stable. not exactly ideal, but thanks for the suggestion. i'll probably stick with the newest m build when it is ready.
im not asking for cms device tree compiled as it is, or anything at all. im just hoping that before or adjacent to cm11 getting going with mods and tweaks that they will release builds tailored to vanilla and nothing else, concentrating only on bugs before adding things and testing them and adding things and breaking things and testing them and so on and so forth. i feel im not communicating this efficiently and im sorry
$MyName said:
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.
Click to expand...
Click to collapse
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.
hayzooos said:
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.
Click to expand...
Click to collapse
I was using m2 for quite a while before I switched over to bb6. In my time playing with m2 I found that video recording was fine and data connectivity took about 10 seconds longer on a reboot. Other than that I've experienced no data drops.
To add to this, YMMV. I'm not sure if my phone is different somehow but I've never had any of these problems that people describe with data drops at random.
Edit:
Also, as far as lte/3g hand off goes, I'm unable to test as I'm not in an lte area. As for GPS, it takes about 7 seconds to lock on in a room with no windows. Tested on slimbean, so again YMMV
Sent from my SPH-L710 using Tapatalk 2
Just try looking into building aosp from source its really not that hard it will just take some time. You could even use the device tree for d2spr from cm so you really will just be using pure stock
Sent from my SPH-L710 using xda app-developers app
ohfoxxxycole said:
I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.
Click to expand...
Click to collapse
You're clearly smoking some good crack. AOSP ROMs for the E3D are awesome right now.
Months ago
Sent from my SPH-L710 using xda app-developers app
What would happen if I build android from source and flash it to my One X?
With the current release, it is possible to build for Nexus 7, for some variants of Galaxy Nexus, for a variant of the Motorola Xoom, and for all variants of Nexus S and Nexus S 4G. The exact level of functionality for each device depends on the availability of the relevant proprietary hardware-specific binaries.
Click to expand...
Click to collapse
- (source)
Will I brick my device? Did HTC basically just take the code and modify it to work on the One X? Any suggestions on how to proceed if I were to build my own ROM?
If you have no experience in this you are likely to f*** things up.
Just stick to aosp roms - same result.
Sent from my HTC One X
TToivanen said:
If you have no experience in this you are likely to f*** things up.
Just stick to aosp roms - same result.
Click to expand...
Click to collapse
Well that is no fun answer. I want to learn. I make apps for a living and want to advance and build my own ROM, because I want an all custom made one. I know I can go with CM and mod their code (or, can I?), but it would be more fun to actually do it from scratch. If it is possible, not build from AOSP at all. I know it sounds retarded but I believe the best way to learn is do as much as possible completely from scratch.
With that said, do you have any suggestion on where to start? Like mod the AOSP source code and get it running on the emulator?
You can branch cm10 and build that, it's a good place to start, you'll learn a lot.
After that, you may want to say, diff the AOSP kernel against a similar HTC kernel to see how many changes you'd be required to make to pure AOSP to get it to work with all the hardware specific bits.
Due to GPL, HTC are required to release the source modifications to the kernel and android (I assume), for any released binaries, but they can be a little slow. The JB stuff should be out soon, in theory. Hopefully that's enough to get everything working, but you will also need any binary drivers from nVidia etc.
It's a long road, and you'd do well to start with something working and work backwards towards AOSP.
I'm not sure what you mean by not even with AOSP, do you intend to create your own OS?
BenPope said:
You can branch cm10 and build that, it's a good place to start, you'll learn a lot.
After that, you may want to say, diff the AOSP kernel against a similar HTC kernel to see how many changes you'd be required to make to pure AOSP to get it to work with all the hardware specific bits.
Due to GPL, HTC are required to release the source modifications to the kernel and android (I assume), for any released binaries, but they can be a little slow. The JB stuff should be out soon, in theory. Hopefully that's enough to get everything working, but you will also need any binary drivers from nVidia etc.
It's a long road, and you'd do well to start with something working and work backwards towards AOSP.
I'm not sure what you mean by not even with AOSP, do you intend to create your own OS?
Click to expand...
Click to collapse
Thanks for the thorough information! If it is possible to create your own OS, then yes, it would be awesome. Actually my idea is to make a ROM similar to the Linux distribution Tiny Core Linux; only the most essential stuff are present and bloatware and other features are removed. It could maybe serve as a good starting point for other ROMs to build on that want a minimalistic base. However, that is very, very far into the future. Now I would just like to compile a ROM that I have developed. But as I said before, if possible, skip AOSP and build my own OS definitely! Is that even possible?
Of course its possible, Android wasn't invented by some higher being or alien lifeform.
Nobody would use it though, because there would be no apps.
BenPope said:
Of course its possible, Android wasn't invented by some higher being or alien lifeform.
Nobody would use it though, because there would be no apps.
Click to expand...
Click to collapse
I see, so I am locked to AOSP then? i better start with the CM branch, thanks a bunch.
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Sarmiento_Luise said:
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Click to expand...
Click to collapse
As of now, Geodev is the only one in development. If you're trying to get your post count up, go to the XDA General section and post in the new members forum or the off topic lounge.
postcount++
imho that geodev thing sounds shady at best.
If you would decide to port a custom rom to a new device, would you really start by porting KitKat if the device
currently only runs jellybean? Wouldn't it be easier to use the stock kernel for now to get cm10 running
and then wait paitiently until htc releases the kernel src to make it a full unofficial cm10 build.
Instead this sounds more like taking the existing source of a hopefully hardware compatible build
and bending it until it brea.. ehm works.
I may be biased, but if you plan to make any kind of release you usually don't go and announce it to the world.
This only encourages the rather impatient endusers to come up with many variations of the same old:
"i need my rls now!", "I am entitled to a release because I found this thread","GIMME RLS!!!11oneeleven"
posts that will just annoy the crap out of every dev I've ever met. Also there is absolutely no point in asking for
beta testers before you even have a working build ready.
Combine that with the recent e-begging post and draw your own conclusions.
DroidTwe4kz said:
[...] I can't continue developing until someone gift me new computer (or motherboard only). [...]
Click to expand...
Click to collapse
In any case, for the time being it might be a good idea to check if there are some services you could deactivate
in order to get a little bit more speed out of your phone. I personally have no problems with lags, but maybe
it's because I don't expect the phone to run every app ever made at the same time since it has only 512MB RAM.