Performance ? - Oppo N1

I just got the device in and i must say pretty impressed with the build quality but did not expect anything less ( Find 5 was the same ).
but after putting all my apps/media content on the device i found that when i'm scrolling in apps/laucher/setting rather choppy and even after flashing omnirom i found that the performance was still the same ?

How many gb do you have left? I was debating to get it and 16 gb not expandable poses a concern.
Sent from my SAMSUNG-SM-N900A using Tapatalk

copualt3 said:
How many gb do you have left? I was debating to get it and 16 gb not expandable poses a concern.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
With all of my apps backed up with Titanium Backup (no compression), three TWRP backups (stock, Omni, and CM), plus a ton of screenshots, pictures, downloaded apps, updates, patches, etc... I still have 3.6GB remaining on my 16GB N1.
yamani.m said:
after putting all my apps/media content on the device i found that when i'm scrolling in apps/laucher/setting rather choppy and even after flashing omnirom
Click to expand...
Click to collapse
What do you mean scrolling? The app drawer? How many apps do you have installed?
On ColorOS I have five pages of apps that are full, and a fifth page that has two apps on it. The only time I get any delay is when I hit the button to Sort alphabetically. That has a little delay when organizing, but after that I never get any delay. I'm actually surprised at how light ColorOS is and how well it performs, being that it's so new.

Related

"Don't keep activities" - anybody use it?

Love the phone but a few times the launcher has redrawn after exiting an app because of most likely memory issues. Anybody using this option? Assuming over time this would keep more memory free and reduce this issue. Any thoughts?
Sent from my Galaxy Nexus using xda premium
mobilehavoc said:
Love the phone but a few times the launcher has redrawn after exiting an app because of most likely memory issues. Anybody using this option? Assuming over time this would keep more memory free and reduce this issue. Any thoughts?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is one of the reasons why I don't like that Google included these developer options pre-installed on this phone. They're developer options for a reason, we can install them if we need to.
This feature is designed so that developers can test their app to be sure that data is properly saved when is no longer in the foreground. For example, if a user receives a phone call or jumps to another app, the app needs to do what is necessary to save it's data. At times, Android can kill a process in the background. If the user plans to go back (perhaps they finished the phone call), they want to see what it is they were working on last. The developer is supposed to handle this case by rebuilding everything as it was before (to provide that seamless experience for the user when switching between apps).
This debug feature helps us test that it works.
For the average user, all you're really more likely to do is slow down your apps. As they will have to rebuild themselves when you resume them, and you may even open yourself to more quirky bugs (for those apps that didn't properly test the above scenario).
So please don't enable it unless you're doing it for development purposes. My 2 cents.
*EDIT* Here's a page from the Android Dev Guide justifying my explanation:
http://developer.android.com/guide/developing/debugging/debugging-devtools.html
Immediately destroy activities
Tells the system to destroy an activity as soon as it is stopped (as if Android had to reclaim memory). This is very useful for testing the onSaveInstanceState(Bundle) / onCreate(android.os.Bundle) code path, which would otherwise be difficult to force. Choosing this option will probably reveal a number of problems in your application due to not saving state. For more information about saving an activity's state, see the Activities document.
Click to expand...
Click to collapse
(and yes, they used to call it "Immediately destroy activities")
Thanks. I turned it off. Did notice some bugs while on. I just wish with 1GB of RAM the launcher wouldnt have to reload. Hopefully things get better. Might just be my apps but it happens quite often when leaving the browser.
Sent from my Galaxy Nexus using xda premium
mobilehavoc said:
Thanks. I turned it off. Did notice some bugs while on. I just wish with 1GB of RAM the launcher wouldnt have to reload. Hopefully things get better. Might just be my apps but it happens quite often when leaving the browser.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
weird.. how many widgets do you have on your launcher? the more widgets you have, the slower the launcher is.
Have you tried another launcher? The stock launcher has never been known for being fast and efficient, although I haven't had any issues with it (whereas I'm a LauncherPro fan on my other devices).
kwazi said:
weird.. how many widgets do you have on your launcher? the more widgets you have, the slower the launcher is.
Have you tried another launcher? The stock launcher has never been known for being fast and efficient, although I haven't had any issues with it (whereas I'm a LauncherPro fan on my other devices).
Click to expand...
Click to collapse
I have quite a few Widgets but nothing too crazy I don't think. I use LauncherPro on my other devices as well but I love this new launcher so I'm going to stick it out. Like I said the most common task that causes the issue is when I'm using the web browser and then come out of it. Otherwise its been stable. I've noticed the same thing with Honeycomb on my Xoom so it might just be one of those things I have to put up with.
Sent from my Galaxy Nexus using xda premium
i'm also noticing some redraw and occasional lag when hitting the home button.
I'm hoping that CM9's custom launcher will have an option to lock it in memory- that may increase the performance by a lot.
also when replacement launchers like go launcher start optimizing more for ICS those might be good options.
Have you tried converting your launcher into a system app? You'll need to use Titanium Backup Pro or something similar to do it for you, or simple copy the APK into your system/app folder... Really sped up my launcher!
shawnshine said:
Have you tried converting your launcher into a system app? You'll need to use Titanium Backup Pro or something similar to do it for you, or simple copy the APK into your system/app folder... Really sped up my launcher!
Click to expand...
Click to collapse
Did you see the date on this thread, almost 8 months old
Sent from my Galaxy Nexus using xda premium
95Z28 said:
Did you see the date on this thread, almost 8 months old
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
... and yet people still continue to discover the thread and benefit from it.
Thanks for clarifying the meaning of "Don't keep activities"
my razr xt910 cannot be counted upon to run smoothly with all the apps simultaneously running and forcing itself to go into reboot. i then fancied an iPhone single styled system (as compared to Android multi-talks) cuz iPhone looks robust and responsive. all the killer that claimed to do the job looked more of a farce and then when i stumbled upon the destroy activity i was like OMG. srsly b4 using it I've only got just inner 100mb of ram, after using it i have a whooping 400mb ram. UI appears faster and all. regarding the relaunching of apps and battery life being used up. i think I'll start to worry about it on a later date. what say any body. ooh yes to add on, even after i deleted 40 apps on my phone it still hanged like fcuked. i guess i can reinstall them back again and not have to worry about it. btw i can't seem to root my xt910 for nuts so i can't custom ROM it along with all other fanciful mods that i hear about what others did to their phones.

Google currents: recent performance issues

I really like google currents and have been using it more than pulse since getting my nexus 7. But just the last few days the performance has been horrible. Sometimes I get the forced close option, even though I select wait as it hasn't actually crashed, just maxing out the cpu for a bit.
Syncing takes a really long time now and when done, most of the articles don't have a screen shot even though I have the option to get images for all articles which has always worked previously. I don't know if I have added one too many news sources? I was going to clear the app cache but I'm concerned if that clears all my selected sources as well? I'm wondering if the sources are stored in the cloud and only the articles are cached.
Not sure what else to try but something is hurting the performance of this app lately.
Btw, previously I have a nook color and I have lots of articles starred in pulse. It's just running cm7 off a sdcard so I never installed titanium backups or anything. Is there a manual way I could take all t he cached stuff for pulse from my nook to the nexus 7?
I can't comment on your problems with Google Currents as I don't use it.
For Pulse, if you create a Pulse.me account, you can restore your selected subscriptions and starred article to your other phones or tablets.
Sent from my Nexus 7 using xda premium
I use Currents also. I find it Sync's in about 5 seconds. You can clear cache, it only clears what has synced. Don't "clear data", that's all your preferences. I get all the photos and is acting no different than when I first started using it. I only have 20 links.
If you're getting below 4g free storage, you might be running into the issues described in this thread:
http://forum.xda-developers.com/showthread.php?t=1776538
Not sure how helpful this may be but I was also having problems with Currents taking a long time to load. I realized that I started experiencing the issue when I had switched my offline reading settings to include all images in all editions. As soon as I changed it to only include it in the first 10 editions I noticed an improvement. Perhaps it may be worth taking a look.
Sent from my Nexus 7 using xda premium
Thanks everyone for the suggestions. I'm going to try them shortly and report back. I noticed I'm getting a little more lag than usual in chrome so maybe it's not just currents but instead I've entered the dreaded lag zone as described in that other thread. But 4gigs? I thought I read there it was 2. Even 2 is ridiculous for a swap file or whatever it needs. But if it's 4 gigs, we lose a few gigs to the OS of the 16 and then we have to keep 4 gigs free for good performance?! And yes I'm below that, I'm a tad below 2 gigs now. Bought nova 3 and MC3 recently which put me below. And I notice both of them have a startup thing running. Or so Autorun manager tells me. That and a few other apps that I think have no business running on startup. Something like pulse (the purpose being to cache articles in the background) I can understand, but Nova 3? Why?
And what irks me more is not having an elegant way of stopping this. I know the android way is the OS should manage apps/memory and not the user and I get that, however I should still have a way of preventing these apps from launching. From what I've read no app really stops them from launching but rather kills them after launch. Or ones that do you need to be rooted.
I do have that option selected to cache all images and not just first 10 editions. What does first 10 editions mean exactly? the first 10 sites I've added? Or the first 10 stories within each? If the former, there's no way I can see of controlling what would be the first 10.
Even though I really like the layout of currents, maybe I'll switch back to pulse just for the simple fact of being able to retain an article.
I hope it's just a currents issue and I don't actually need to retain 4 gigs free.
If these things fail I'm going to uninstall Nova3/MC3 and see.

[Q] Why to Root Note 2?

Hello all, i recently bought Note2. I switched over from my 2 years old HTC desire which i had rooted in the very first month for various reasons.
Just to give you a background i am not against rooting. But i believe, since we are taking this risk, it should really be worth it. For my HTC, it had 128 mb of internal memory, no official upgrades and i loved cm. So it was all worth it.
Looking at Note2 it a better looking version of cyanogenmod. (off-course will a few features missing). Although i was used to reflashing my Desire every month, i havent found any substantial reason for rooting NOTE2. It has regular updates biggass memory and HDD. very fast CPU
Only thing i miss is a more powerful flashlight (Torch) and a stock 5x5 TW launcher (i am using go launcher now to leverage the screen real estate). So apart from this and that i've heard Gmail 4.2 has pinch and zoom. I havent heard of any substantial gains by rooting NOTE2.
Please list what are the advantages of rooting NOTE2. i know the advantages of rooting in genral. i am specifically talking of note 2. Also i dont want to you all to list advantages like nandroid backup CWM recovery etc. since my contacts sms / call logs and apps are already being backed up at google / dropbox / Evernote.. I am loking for something substantial.
I have a post questioning the same thing.
http://forum.xda-developers.com/showthread.php?t=1943960
Baisically the only reason I woukd root is for the following (might not apply to you):
OpenVPN with TAP support.
SSH tunnel
TitaniumBackup
Sent from my GT-N7100 using xda app-developers app
The Note 2 will be the first phone I don't root. There's really no need, IMO.
The Samsung software with it's S-Pen features is a bit too complex to trust "ROM chefs" and such. I'll just enjoy it as-is.
Also other fonts and "adfree" are reasons for me
Greetings.
Sent from my GT-N8000 using xda app-developers app
rumy said:
I have a post questioning the same thing.
http://forum.xda-developers.com/showthread.php?t=1943960
Baisically the only reason I woukd root is for the following (might not apply to you):
OpenVPN with TAP support.
SSH tunnel
TitaniumBackup
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick response. Specially the link. Most folks on the thread state that custom roms or even root has not been a great benefit to them in case of Note2. i do not need the above functionality you mentioned since the only reason i need vpn / ssh is to connect to work. Which i do from my laptop. But i will be on the look out for anything that pops up. Thanks again
My reason for rooting ANY android phone is...
Adaway
I'm sick and tired of flashing custom roms because I have found that after playing around with stock roms, I revert back to "stock firmware" anyway. So i just stick to stock samsung firmware. There really is no need to root for other than getting rid of the adds (i use adaway).
1. Titanium backup
2. Nandroid Backup
3. Debloat the rom with stuff i don`t need with ROMCleaner
4. Adblocking
5. Flashing mods like increae incall volume, brightess.
6. Flashing stock firmware and keep root with Mobile Odin
7. Raise the readahead values to load up apps, webpages, and other stuff faster
8. Overclock for performance or undervolt the kernel to save power.
Other users might also have other reasons so enough reason to do it i guess
Also to increase the internal storage by switch the external sd card with phones internal memory so making bigger internal memory.
Sent from my Nexus 7 using xda premium
The Note 2 is not out in the US yet (I'm so tempted to buy the International version) but when I do get it I plan on rooting it for Titanium Backup and Ad Free and a lot of root apps that I use but I don't see a point in flashing a custom ROM on it.. Its so perfect without it.. Wish it came with Tablet mode.. I love having my status bar at the bottom of my screen...
Sent from my Paranoid A$$ Jellybean eating Galaxy Note
saadi703 said:
Also to increase the internal storage by switch the external sd card with phones internal memory so making bigger internal memory.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
+1. In my opinion, this is ultimately the only reason for rooting - all the rest can be done in other ways.
However, some applications like orange cinema series (in France) check if the telephone is rooted - if so they won't work. Ultimately, rooting is becoming a very debatable benefit today - up to the next release of Android 5.0 on the New S5 processor. At that moment, i am sure that Samsung will delay updates as much as they can, since the hardware improvements become more marginal (with the exception, of course, of LTE) and therefore a differentiating factor between latest models and 1 year old devices. And then, all back to AOKP and CM27...
I say this by experience: my galaxy S I9000 works like a charm with Jelly Bean, and it would still be a froyo telephone if i would follow ORANGE F....
saadi703 said:
Also to increase the internal storage by switch the external sd card with phones internal memory so making bigger internal memory.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Do you really need more than 11 gig of internal memory? Assuming you transfer move your songs videos and other pictures etc in ur external.. why do you need more than 11 gb of internal?
Needs a root for things like sixaxis controller. Pretty cool to be able to use a wireless PS3 DualShock controller to play your favorite games.
For me the most important thing about rooting is themes, i hate stock theme(grey windows etc) and i love transparent status bar, other things wich pusch me to go for a root is basicly posibility to remove stock apps, custom kernels wich give u better performance and battery life and offcorse for my mod sd2extsd wich give u oportunity to save more things on ur phone(games and apps)
Sent from my GT-N7100 using xda premium
I'd have to say solely for themes and removing bloatware with a custom rom to get the most of the ram availability.
11GB is tiny - particularly if you want a coupe of good games (you know you do lol) - apart from the 1-2GB of physical space the app takes (even when storing saves etc on SD) INSTALLING them takes more space and many require several more gigs ONLY during the install process (presume for unpacking etc) so you have to leave a couple of giggs free - leaving you with 8-9GB of usable space - not a lot.
If you use no games at all I agree 11GB might just do but other apps will fill it quick - eg: snote stores all its notes in internal SD (only small but multiply a few notes a day x a couple of years - it all adds up)
My friend has a 16GB SGNI - NO GAMES, but any medical apps (each 20-200M) and he's struggling for space
I just don't want to be limited (that's the whole reason I'm leaving ios for my mobile)
Ad blocking, and Nandroid alone are the main reasons why I rooted my phone..... there's also lucky patcher.....
I think you are confusing rooting with loading up a rom. Rooting is a must for a lot of users who want to customize. For example, let's say you want to use an NFC tag in your car to turn off wifi, turn on bluetooth and turn on GPS. This will work fine all the way up to the GPS part, which requires rooting to make it automated.
As others mentioned, titanium backup and other software needs it as well.
Rooting unlocks possibilities, it isn't loading CM.
Sent from my SCH-I535 using xda premium
Don't worry about rooting until you find a need for it (get tired of ads, overclocking or just a general love for tweaking the build.prop file or any of the various apps requiring root access). Until then, just enjoy your phone
Advantage of rooting galaxy note 2
One of the advantages of rooting Galaxy note 2 is that it will start ready NTFS hdd and usb on-to-go....
It's not really necessary to root this phone in my opinion. Amazing phone and the first one I've owned which has left me wanting for nothing.
Sent from the mighty Note II

Been holding off kk upgrade. Should I let it just go?

On my note 3,i know if 4.4 I will lost root.
My tablet is not rooted but I might like to to get Microsd access and defrost. If looks like if I upgrade, I can still aquire root
True or not, any reason not to?
Sent from my SM-P600 using Tapatalk
Honeybadger said:
On my note 3,i know if 4.4 I will lost root.
My tablet is not rooted but I might like to to get Microsd access and defrost. If looks like if I upgrade, I can still aquire root
True or not, any reason not to?
Click to expand...
Click to collapse
It's like a new tablet performance and function wise. All of Samsung's apps have been refreshed and the browser is especially impressive. Multi Window and Pen Window now support the same apps meaning you can have apps open side-by-side or floating and resizable. Without any modifications I now have 35 apps available in Multi Window. On 4.4 you can also install Hancom Office, e-Meeting, Remote PC, and Side sync bringing the N10.1-2014 up to "Pro" level. People are reporting better battery life and shorter charging times also. I did a dirty flash using a ROM from a different region so I somehow kept the lock screen widgets (which should be gone) and lost Daynote (which should be there). My battery was funky at first; not charging overnight and draining way too quickly. The former fixed itself and the latter was fixed when I deleted my Exchange accounts, cleared app data, and rebuilt them. I think my battery life is better now; it's certainly no worse. I'm going to do a recovery and rebuild my N10.1-2014 (it takes about six hours ) once the 4.4 ROM for my region is out which should clear up any funkiness.
As for external SD, it is what it is. Apps can still use it (individually) for storage so you can keep big files there. Samsung's apps (My Files, Samsung Link, Gallery, Video, and Music) still have universal read/write access and can manipulate all external SD files. So with 4.4 there's some added manual administration and you have to come up with new ways of doing things but it's not the end of the world. And it's not going to change. So you have two choices - stay on 4.3 forever and miss out on a fantastic update or bite the bullet and root. After just four days using the update I can't imagine going back.
BarryH_GEG said:
It's like a new tablet performance and function wise. All of Samsung's apps have been refreshed and the browser is especially impressive. Multi Window and Pen Window now support the same apps meaning you can have apps open side-by-side or floating and resizable. Without any modifications I now have 35 apps available in Multi Window. On 4.4 you can also install Hancom Office, e-Meeting, Remote PC, and Side sync bringing the N10.1-2014 up to "Pro" level. People are reporting better battery life and shorter charging times also. I did a dirty flash using a ROM from a different region so I somehow kept the lock screen widgets (which should be gone) and lost Daynote (which should be there). My battery was funky at first; not charging overnight and draining way too quickly. The former fixed itself and the latter was fixed when I deleted my Exchange accounts, cleared app data, and rebuilt them. I think my battery life is better now; it's certainly no worse. I'm going to do a recovery and rebuild my N10.1-2014 (it takes about six hours ) once the 4.4 ROM for my region is out which should clear up any funkiness.
As for external SD, it is what it is. Apps can still use it (individually) for storage so you can keep big files there. Samsung's apps (My Files, Samsung Link, Gallery, Video, and Music) still have universal read/write access and can manipulate all external SD files. So with 4.4 there's some added manual administration and you have to come up with new ways of doing things but it's not the end of the world. And it's not going to change. So you have two choices - stay on 4.3 forever and miss out on a fantastic update or bite the bullet and root. After just four days using the update I can't imagine going back.
Click to expand...
Click to collapse
Thanks, so OTA then root or root then ROM install? Can I root post OTA?
Sent from my SM-P600 using Tapatalk
Barry how are you getting apps to float. I can't figure it out.
Sent from my SM-N900T using Tapatalk
KitKat on this thing is a beast!! The original software with the note was a joke and I'm glad Samsung fixed everything with kitkat
KitKat looks good, but to me it made my external SD READ ONLY. I can't modify any file, not even copy from the internal to the external.
Luigi14 said:
KitKat looks good, but to me it made my external SD READ ONLY. I can't modify any file, not even copy from the internal to the external.
Click to expand...
Click to collapse
If you are rooted just install "Folder Mount" from play store, run it , it will fix your sd card issues.
Luigi14 said:
KitKat looks good, but to me it made my external SD READ ONLY. I can't modify any file, not even copy from the internal to the external.
Click to expand...
Click to collapse
I thought this was possible with the Samsung My Files file manager?
Sent from my SM-N900T using Tapatalk
aznmode said:
I thought this was possible with the Samsung My Files file manager?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Yes, Samsung My Files will work with ext SD but it doesn't allow you to rename filename extensions so you can rename a .apk to like .zip so you can bluetooth it across and then rename it back to .apk
warboat said:
Yes, Samsung My Files will work with ext SD but it doesn't allow you to rename filename extensions so you can rename a .apk to like .zip so you can bluetooth it across and then rename it back to .apk
Click to expand...
Click to collapse
I'm able to rename any file or move them around from internal to micro sd card, but youre right I can't rename the extension using Myfiles.
Sent from my SM-P600 using Tapatalk
Don't bother! I love Jellybean and I love being rooted...I have so many cool apps ...plus with TB I have frozen all the bloat and get like 14 hours out of my tab...Its super fast, no lag and no headaches with KK. I will never upgrade to KK.
I have everything the Pro series has ..have Milk Music ..etc...
Sent from my SM-P600 using XDA Premium HD app

Phone becomes unstable after taking a picture with the new camera app

My phone just lags for 5 seconds or so after taking a picture with the new Pixel camera app.
If you are seeing similar behavior, pls think about upvoting / staring the reported issue.
https://issuetracker.google.com/issues/118393019
Luinwethion said:
My phone just lags for 5 seconds or so after taking a picture with the new Pixel camera app.
If you are seeing similar behavior, pls think about upvoting / staring the reported issue.
https://issuetracker.google.com/issues/118393019
Click to expand...
Click to collapse
I get your issue.
My intent is not to belittle. or start a war of words.
My question is why would it be expected for Google to be concerned about the performance of an application that was "improperly" ported over to hw it hasnt been made available to yet?
What is the goal?
BTW I have the P3 app and am not experiencing any issues v6.1.013.216795316 if it makes a difference.
Magisk over Stock
Luinwethion said:
My phone just lags for 5 seconds or so after taking a picture with the new Pixel camera app.
If you are seeing similar behavior, pls think about upvoting / staring the reported issue.
https://issuetracker.google.com/issues/118393019
Click to expand...
Click to collapse
The reason is very simple. The Camera use a lot of RAM and RAM is not enough on Pixel 2 XL (or 3)
Right after reboot, I usually have 1.4G of RAM. and after some use, the available RAM will stay around 900MB. Most time when camera APP starts, the available RAM will drop to 300~400M where the phone will struggle and try to kill a bunch of background service, app, etc. This creates the lag and unstable.
The only way to regain all this mess is a reboot.
parakleet said:
I get your issue.
My intent is not to belittle. or start a war of words.
My question is why would it be expected for Google to be concerned about the performance of an application that was "improperly" ported over to hw it hasnt been made available to yet?
Click to expand...
Click to collapse
Idk what you are talking about, the Google camera app was updated to all pixels via the Play store.
lssong99 said:
The reason is very simple. The Camera use a lot of RAM and RAM is not enough on Pixel 2 XL (or 3)
Right after reboot, I usually have 1.4G of RAM. and after some use, the available RAM will stay around 900MB. Most time when camera APP starts, the available RAM will drop to 300~400M where the phone will struggle and try to kill a bunch of background service, app, etc. This creates the lag and unstable.
The only way to regain all this mess is a reboot.
Click to expand...
Click to collapse
Ram usage isn't a bad thing, free ram is wasted ram, and I get that the camera app uses quite a bit of memory, after all, taking a HDR pic means taking a couple of pictures, saving the raw (~40mb per pic or so) in ram and merging it in to a single picture. But 4GB should be enough for this, and the phone shouldn't stutter not should it be closing apps that were recently open, it should be cleaning stuff that's longer inactive.
Luinwethion said:
Idk what you are talking about, the Google camera app was updated to all pixels via the Play store.
Ram usage isn't a bad thing, free ram is wasted ram, and I get that the camera app uses quite a bit of memory, after all, taking a HDR pic means taking a couple of pictures, saving the raw (~40mb per pic or so) in ram and merging it in to a single picture. But 4GB should be enough for this, and the phone shouldn't stutter not should it be closing apps that were recently open, it should be cleaning stuff that's longer inactive.
Click to expand...
Click to collapse
I'm guessing parakleet assumed you were using the recently ported camera app by a dev that enables Night Sight for P2's. That feature hasn't yet been optimized or enabled for phones other than P3's. If you are just using the stock camera app from the Play store using HDR+ or enhanced for a single picture, then no the phone is not supposed to lag and you have a genuine issue. Is the phone getting warm at the same time? If you are taking multiple HDR's close together then maybe... Mine only lags a bit processing Photospheres, but not long. You may start with resetting the camera app settings (or all app settings). Make sure you wipe the camera app data.
lssong99 said:
The reason is very simple. The Camera use a lot of RAM and RAM is not enough on Pixel 2 XL (or 3)
Right after reboot, I usually have 1.4G of RAM. and after some use, the available RAM will stay around 900MB. Most time when camera APP starts, the available RAM will drop to 300~400M where the phone will struggle and try to kill a bunch of background service, app, etc. This creates the lag and unstable.
The only way to regain all this mess is a reboot.
Click to expand...
Click to collapse
Please read up on Linux memory management.
Luinwethion said:
Idk what you are talking about, the Google camera app was updated to all pixels via the Play store.
Ram usage isn't a bad thing, free ram is wasted ram, and I get that the camera app uses quite a bit of memory, after all, taking a HDR pic means taking a couple of pictures, saving the raw (~40mb per pic or so) in ram and merging it in to a single picture. But 4GB should be enough for this, and the phone shouldn't stutter not should it be closing apps that were recently open, it should be cleaning stuff that's longer inactive.
Click to expand...
Click to collapse
I never said RAM usage is a bad thing. I just said what I observed on my phone which behavie very similiar to OP. My 2 XL struggls when the built-in camera running and since I have memory monitor app showing me real-time memory usage status, I can see the 2 XL's RAM become extreme ly (~300M) and my background app (including launcher) got killed all the time.
What you said above is what is INTENDED. But what I said is the real world result.
If you own a 2XL, just use it for couple of hours (this never happens after fresh reboot), then run camera app, taking 2 pictures, then return to launcher, then open camera app and taking some pictures. You will see this real world issue.
---------- Post added at 12:58 AM ---------- Previous post was at 12:45 AM ----------
nomisunrider said:
Please read up on Linux memory management.
Click to expand...
Click to collapse
I believe your reply is neither helpful nor correct. Although Android is based on Linux but Android havily turned the memory management parameters and are running with millions app combinations on millions of machines (phone) with millions of different usage pattern, network status.. The behavior of each phone is bound to be different. What works on one phone is not guaranteed on the other.
Answer like yours assuming other people is lessk nowledgeable on certain topic then yourself is not a good thing on XDA, we are here helping each other here, try to find out answer together.
This is real world, not just some theory nor design guild line. And sure, I do know one thing or two about Linux memory management.
lssong99 said:
And sure, I do know one thing or two about Linux memory management.
Click to expand...
Click to collapse
This is the problem. You just need to do a small amount of reading to understand why looking at free/available memory is not that useful. 5 minutes of reading is all it would take.
nomisunrider said:
This is the problem. You just need to do a small amount of reading to understand why looking at free/available memory is not that useful. 5 minutes of reading is all it would take.
Click to expand...
Click to collapse
Still not helpful. Sigh....
If you cannot provide any useful answer to OP or my real world situation, then please do not reply to this thread further. You are wasting our time.
If you are here just to judge the knowledge of other person you don't know at all, then please leave this forum. You are just being a troll. (a polite one, I admitted though.) We don't need troll here.
I do hope moderator can close this thread since this is getting ridiculous. OP and I have problem on 2XL's camera app issue which might related to memory management issue but troll like you insist we need to read some text book while not providing any explanation nor solution.
And to answer your question, yes, I did read the Linux memory management logic and I also read/experiment a lot more than just that. "Free RAM is bad RAM" is a myth that only applicable in certain situation like data server, since their primary function is providing data and caching data stored in slower disk in RAM is a really a good strategy.
However in modern phone, people not want only data, we want to switch between unspecified APP thus it's important to also have app cached versus data cached (also the data we want is usually changing on the cloud). Beside, Android memory management (at least on my 2 XL Pie) has a arguable bad habit of killing a bunch of even persistent app while available RAM is lower than 350MB (based on my observation). Instead of process my immediate request (the camera app), the phone spend a lot of time killing all other apps which causes the problem of slow performance on my 2XL as well as an explanation on OP's problem.
If you have better explanation or solution please provide, if not, please just shut up.

Categories

Resources