Related
Guys,
Browsing the web I stumbled up on to this article:
It describes how you are able to get a good performance out of your Hero, Hence that it's just a experiment so not sure if it will work!
http://www.majicware.com/HTC-Hero-Speed-Issues-Experimenting?vzWMwp
I'm going to post updates as I will test it.
The article actually sounds quite interesting...I've also noticed that killing tasks doesnt necessarily get rid of some of the lag (although I dont have that much lag to begin with).
I think I'll give this a try for a couple of days too.
Well lets keep us posted on this case. I will give a update tomorrow.
I'll see if that works for me =)
sounds promising =D
thanks for sharing
ill give it a try!
If the phone is syncing then it is definitely very laggy. This is also the case when the memory us low. Obviously if u have apps like task panel or the,music player running at the same time things will slow down too.
For me task panel has worked well. If I keep the free memory at around 50megs then there is almost no lag. I'll keep an eye out for other things as well
If the phone is syncing then it is definitely very laggy. This is also the case when the memory us low. Obviously if u have apps like task panel or the,music player running at the same time things will slow down too.
For me task panel has worked well. If I keep the free memory at around 50megs then there is almost no lag. I'll keep an eye out for other things as well
I have been using the Hero for a few days. On day one I hated it, it was so slow. Then I started using Taskiller to kill tasks like weather, clock, mail, peep etc that are running in the background. Not much help. In fact, it seemed the more frequent that I killed these tasks, the slower my Hero ran.
After a few days of use, I realized the trick to speed up the Hero (or android in general) is DO NOT kill tasks unless you are running our of memory. By running out of memory, I mean really out of memory. My Hero is using 160MB memory right now, which may seems a lot, but it is running very smoothly. Killing some tasks reducing memory usage to, say 90MB, wont' really speed it up. Unlike Windows Mobile, as long as your memory usage is not 99% and have memory left for additional apps to open, just leave it. Remember the Hero has 288MB memory, 100 MB is already reserved for the OS to run, and android memory management will kill unnecessary tasks for you when you run out of memory anyway.
Now, the important part. Do not kill tasks manually too frequently. You have to understand when does the Hero slow down: when it is fetching data. If you use an HTC widget, do NOT kill the relevant app that the widget requires it run in the background. For example, if you used the HTC music widget, don't kill the music app running in the background. If you killed it, you would notice a very significant lag when you go from another page to the page with the music widget. This is because the music widget is trying to open the music app and access the music on your micro SD. Once it is done, the music app will just become idle until you start playing music and there is no more lag. But if you killed it, the widget had to open the app every time you reach that page after killing the app. This causes lag.
The same go for the twitter widget. If you killed Peep running in the background, you will notice a lag when you go the page with the twitter widget. This is because the twitter widget is starting up Peep again and has to connect to your twitter account to check for new stuff. But if you leave Peep running, it will do so only at the regular time interval that you set.
I am now running the HTC clock widget, music widget, bookmark widget, twitter widget and full of stuff on all of my 7 pages home screen. I have clock, weather, music, peep, mail and many other apps running in the background. My Hero run very smoothly.
I hope this helps.
Hmmm... Well, I think it is pretty obvious and common sense that the apps used for active widgets should surely not be killed. For the others, I find that I am better off killing them. Even if this should not be the case, and the effect only "psychological", I still fail to see what would be a benefit of not killing the applications.
Android market should define some criteria that applications must meet before they're made available. Applications should also be benchmarked and rated wrt connectivity requirements, CPU-load etc. This would be a deterrent against applications that load automatically even when there's no config (like peep when there's no twitter account), or puts such load on device that it runs out of juice in a few hours (power manager). If this is done on android market one could also hope that vendors also would put a bit more effort into optimising their own stuff.
've stopped obsessively killing Apps...running smoothly. Android Dev video posted on similar thread reassured me that the OS is meant to take care of all that anyhow
phel21 said:
Android market should define some criteria that applications must meet before they're made available. Applications should also be benchmarked and rated wrt connectivity requirements, CPU-load etc. This would be a deterrent against applications that load automatically even when there's no config (like peep when there's no twitter account), or puts such load on device that it runs out of juice in a few hours (power manager). If this is done on android market one could also hope that vendors also would put a bit more effort into optimising their own stuff.
Click to expand...
Click to collapse
Well, I dunno; that way madness lies, or at least iTunes Appstore madness, where new apps, and upgrades, take weeks to get approved, and are still equally buggy. And new apps often get refused, for no good reason.
I like the timeliness of the Android store; and I'm suffering with dodgy apps too - my Hero currently won't last overnight on standby - but it's still miles better than the iPhone nonsense
Well I stopped using the task manager to kill apps for a couple of days....but there is no real speedup and its just the same.
BUT it also means that its pointless to kill the tasks to begin with since it didn't make a difference either (like other people are now saying). If anything, the browser and apps like people/contacts load up faster beacause they are still somewhere in the background (I used to always constantly kill these apps).
The part about not suspending the phone straight away has made a slight difference. Before, when I turned the screen on I constantly had a lag especially sliding the screen left and right and going to the messages page. But if I let it go into standby by itself, when I wake up the phone, it barely stutters (and if it does, its only for like a split second on the first slide).
...if only there was a shortcut to just lock the screen....
I found uninstalling 'Power Manager' sped my phone up massively. I shall try this and see if he's onto anything.
...if only there was a shortcut to just lock the screen....
Click to expand...
Click to collapse
Aren't there apps for locking in the market?
don't know will this speed up things and to whom it may apply, but until today i never ran my Stocks app, seeing as i don't care about stocks so i opened it, opened settings and found out it was set to update every 1h with 4 preset stock somethings....so those not using it might also wanna check that the thing is switched to Manually, one less task that shows up for no reason :/
Tone-Fu said:
I found uninstalling 'Power Manager' sped my phone up massively. I shall try this and see if he's onto anything.
Aren't there apps for locking in the market?
Click to expand...
Click to collapse
I've only come across the likes of lock 2.0 but I thought that was an alternative lockscreen...
cdmackay said:
Well, I dunno; that way madness lies, or at least iTunes Appstore madness, where new apps, and upgrades, take weeks to get approved, and are still equally buggy. And new apps often get refused, for no good reason.
Click to expand...
Click to collapse
Apple's problem is politics. I wasn't hinting towards any such subjective valuation for Android. What I'd like is a clear set of technical requirements (example: an application that auto-starts during boot even without necessary configuration data should not be accepted), and a site back-end with numerous emulators that runs applications through their paces to obtain performance/power/network rating before they are made available for download. Extensive testing would require manual configuration, test and monitoring, but even some simple automated tests could sort out the worst offenders. Ratings should be displayed with application descriptions on the site, and would also work as a simple form of tech feedback to developers about things they may need to improve.
good points.
I've since discovered that any app that registers to receive async alarms will be started at boot, even though it doesn't necessarily need to be. not really a problem, but the cause of a lot of processes running at boot for no obvious reason.
Hi Guys,
I'm Adam Saunders, author of the original article.
Just a thanks to everyone that is also trying the experiment. So far I've had a lot more positive results from people than negative, so the hunch is somewhere on the right track.
I was going to try and find an exact reason as to why killing tasks repeatingly will slow the device down. It's been said its the way that Android kills apps but saves the state, so the process isn't actually running, and by killing that off, the orphaned state is possibly the problem. Sounds feasibly, but not read anything official to back up that claim.
Confirmed, it's been three days since I stopped killing the processes and any lagging (which was very slight for me in the first place) is gone. Thanks for the tip, Adam!
Same page same wifi,
Notebook HTC desire
2.2GHz dual core 1GHz
4GB DDR3 576MB ram
added better video with more sites, and still, HTC Desire wins
Show a video erasing the cache on each browser before doing the test which would be fairer.
Sent from my HTC Desire using XDA Appwo
i did this before video, i cleaned all task, cache and history, also htc desire was fresh boot.
You can try yourself...
well ... although i agree that the desire browser is really fast ... i have to say, your pc's chrome is terribly slow.
when i compare loading engadget in my chrome it doesn't even take half the time to load and it's way faster than my phone can do it
core2duo 3ghz
4 gb ddr2 ram
Mondaro said:
well ... although i agree that the desire browser is really fast ... i have to say, your pc's chrome is terribly slow.
when i compare loading engadget in my chrome it doesn't even take half the time to load and it's way faster than my phone can do it
core2duo 3ghz
4 gb ddr2 ram
Click to expand...
Click to collapse
maybe you are using desktop computer (and your cpu is 1,6GHz faster ) and faster internet, and also, you in Germany, so closer to server than me.
There's no doubt a PC or laptop is faster than the Desire. Comparing them makes no sense.
Tips to OP: try Opera Much faster than Chrome (on PC)
Oooh yeah here it comes... yes of course, opera is faster then Chrome.... of course....
Sent from my HTC Desire using XDA App
Zhypr said:
There's no doubt a PC or laptop is faster than the Desire. Comparing them makes no sense.
Click to expand...
Click to collapse
Well, computer can do tones of jobs.
But phones are optimized to do certain jobs better, and browser is one of optimized programs. (This would be my guess)
Opera is faster than chrome and webkit
You don't have the same computer then he has, and chrome is faster. Next you probably didn't use same connection, and even if you did, your pc had privileges over the phone.
It would be completely fair if you'd compare 2 same speed wi-fi connections, and use slower PC. You simply can't put 2,86TFLOPS PC versus 40MFLOPS phone, right?
EDIT:
And by the way, your desire is loading pages slower then his and mine.
Just to add to the conversation I have done some testing with browsers recently (Mainly Chrome/IE and Firefox)
And I must say Chrome is has some serious issues. For instance Firefox will load a page in less than a second and on the same machine Chrome will take about 20 seconds.
Also another bug I have noticed with Chrome it will intensivley hog the Ram useage and even CPU useage on certain machines. I first noticed this because one of our computers at home is rigged up to our 32" TV for watching stuff using WMP on the TV. Now the computer isn't high spec but reasonable and plays all these videos fine (from local hdd) but as soon as 1 Chrome page is open (1 tab) you will notice the video keeps pausing/jumping/skipping and in places become un-watchable and simply closing Chrome (without restarting the video) fixes the problem and you can see the ram and cpu drop dramatically even while still playing the video.
I don't know what is about Chrome but I have tested it on a few machines and got similar results (apart from one seemed to be ok) and Firefox has been the quickest out of my tests. Although IE sometimes (rarley) opened quicker the FF most of the time IE just crashes when you open it for the first time. Chrome opens very fast and normally the fastest to open but web browsing not always that quick and hogging system resources I stick to FF with no issues what so ever (apart from one crash in the last 2 months and when it re-opened all of my (10) tabs where open within 30 seconds and ready to go.
kilohercas said:
Well, computer can do tones of jobs.
But phones are optimized to do certain jobs better, and browser is one of optimized programs. (This would be my guess)
Opera is faster than chrome and webkit
Click to expand...
Click to collapse
Opera on PC FTW
Opera mobile FTL
max_carpenter said:
Just to add to the conversation I have done some testing with browsers recently (Mainly Chrome/IE and Firefox).
Click to expand...
Click to collapse
First of all I'm very happy with my stock browser in Desire.
As to the desktop browsers; I am totally agree with your comment on Chrome, it has issues and besides a ram and cpu monster. Firefox is working well but is slow especially at first launch. Have you ever tested Safari? It is my default browser since the day I hv installed and begun to use it.
Sent from my HTC Desire using XDA App
I have never had any of these issues you are talking about. my chrome is ridiculously fast, and does not eat more then 50MB RAM. By the time writing this(4tabs) it uses 8-11% of the CPU, and that's because of that annoying flash ad here -.-' (Now it's 0-4% when I scrolled down a bit)
There are only four problems I have experienced are these:
1.) Since first beta chrome starts up MUCH slower, but still MUCH MUCH faster then other browsers. But he can do now much MUCH more things of course
2.) The omnibox sometimes takes time to detect the site I want. Rarely.
3.) Sometimes(rarely) it "forgets" to auto-fill my login details, rarely but unfortunately on my most visited forums, that's these too =/
4.) It is too good for some people
Well, i am using only firefox, and it use just 20% of cpu (opening page)
So it would be like 0.9GHz 100% loaded cpu
HTC desire load pages by using 80~99% of cpu, so it same as desktop computer.
That's why HTC desire some times will load it quicker.
But if website is flash based, or have lot of java, it becomes quite slow.
Dany0 said:
It would be completely fair if you'd compare 2 same speed wi-fi connections, and use slower PC. You simply can't put 2,86TFLOPS PC versus 40MFLOPS phone, right?
Click to expand...
Click to collapse
Sorry mate, but Intel i7 extreme (6 cores) has only 0.1TFlops peak performance, not 2.86TFlops (with HT )
We are talking about overall PC performance. Besides, Core i7 may, maybe, have 0,1TFLOPS in linpack, but it's real performance is about 2,86TFLOPS. That perfectly fits with the 5TFLOPS HD5970
I can live with the Nexus 5X' relative sluggishness when compared to the Nexus 5, but what really stops me from doing my work is the phone killing apps when I switch between them.
Example: I may be filling out a form on a website in Firefox for Android. I need to look up a word in the dictionary, so I switch over to the dictionary and look up the word. When I switch back to Firefox, the application has obviously been killed, as it reloads the page.
Example2: I'm listening to the Audio version of the Economist via the Economist app. The speaker mentions a certain placename and I open the Google Maps app in order too find where it is on the map. Suddenly the audio will stop playing - the app has been killed.
The above gets considerably worse when switching between more than two apps and is really hindering my work and productivity.
Now this almost never happened on the Nexus 5, which also only had 2 GB of RAM. So is it the power saving feature of the Nexus 5X kicking in? Is there a way to stop it from happening?
Marshmallow simply has very bad RAM management from what I've seen. I used to have the Nexus 5 too and as you said, multitasking was a very good experience on it (especially on Kitkat). Google's OS takes more of the phone's resources after each update (with no major new features or improvements). Marshmallow looks exactly the same as Lollipop, except for the tiny feature of apps permissions, and the Now on tap that I barely use (same for Android pay which I'm sure most of Nexus 5x owners won't even be able to use it outside the US). So I still don't understand why they had to jump so fast to a new version of Android while Lollipop still had a ****load of bugs that need fixing, they could've worked more on Lollipop to perfect it first then give us Marshmallow after 2 years maybe, we're not in a hurry.. I just hope they don't stop again at Marshmallow 6.1/6.2 or something and introduce Android N *sigh*
Sounds like you have more user installed apps with constantly running background services installed that the phone can comfortably handle with 2GB memory.
Check the memory stats in Settings - if the average over all the time options is 1.6GB or above used then your phone is going to struggle and cached apps are going to be getting cleared out when switching regularly. Look down the list particulary for apps running close to 100% of the time with a big RAM fingerprint. Also check running services in developer settings to get an idea of what is running a service all of the time.
Once you've identified the worst offenders make that difficult decision - is the apps utility worth it for the impact on performance. Consider reporting the memory use to the developer, particularly if it's much lower after a reboot and increases over time. Plenty of playstore apps ship with clear memory leak issues.
Other than that the other option is reasonably regular reboots to keep the system fresh and clear out any memory leaks.
thanks for the suggestion. Well here's the top 5:
Android operating system 524 MB
Wechat 156 MB
Firefox 117 MB
System UI 105 MB
Android system 99 MB
Clearly it's mostly the system using all resources. Firefox and Wechat, sure, I find them rather essential to my life, but together they don't even use as much as the OS.
Thing is, I can't remember this happening on the Nexus 5.
Sounds like you may have some apps using up a lot of your memory. I haven't been seeing any redraws with my apps, even 24+ hours of sitting in the background. The other day I was switching between gaming, streaming a live sporting even, and text messaging and the phone didn't drop a beat despite the game alone using 600MB of RAM.
Are those the average RAM or peak?
that's what shows up when I get the details of the RAM usage through settings
still this never happened on the Nexus 5, at least I can't remember
Yeah, I have a hard time believing it's the apps. I never had this issue come up in my Moto X 2013 (also 2 GB of RAM) using the same apps. We're seriously talking about one app open, switching to another app. No reason switching back to the first app should have everything reload.
Unless by "some apps," you mean that they have somehow not been optimized for Marshmallow in some way or other. But the apps simply running a process? A smartly-made OS (Lollipop, KitKat) will know "Hey, we have to kill something to free up RAM? Why don't we kill an app that hasn't been used in a while?" and a less-smartly-made OS (perhaps Marshmallow...?) will think "Hey, we have to kill something to free up RAM... why don't we kill the app the user just used?"
And there are two figures there - average and peak - which are those?
If there are the averages rather than peak then both Firefox and Wechat have got a problem.
---------- Post added at 06:42 AM ---------- Previous post was at 06:34 AM ----------
Marshmallow and Lollipop low RAM behaviour is pretty much identical and quite aggressive (the OS tries to preserve quite a chunk of free memory which is uses on the sly as a display buffer), KitKat was less aggressive.
I don't have any problem multitasking on my Nexus5x, but then again for the apps I've got when I check the memory tab I'm normally averaging 1.2-1.4GB used and 400-600MB average memory free so there is plenty of space for the OS to gracefully cache and uncache processes. If the phone is normally running at 1.5GB-1.6GB used and 200-300MB then the LMK is going to be kicking in frequently. It kicks in at around 250MB free on a Nexus5x.
It was the default setting, i.e. average. HM ok good to know. It's happening quite often when listening to the Economist too. Which is really bull****, it should treat it as audio playing. Why would Android kill your music.
I agree music players don't get the priority they should, although that particular 'bug' at least gives a clear symptom that lack of free RAM is an issue, if not the cause of the issue e.g. the OS, to many running services from user apps, or a particular user app with memory leak issues.
I came to the Nexus5x from a 1GB Moto G where it was almost impossible to keep background music running in combination with navigation after Lollipop without uninstalling pretty much everything else user installed and have got used to monitoring the RAM footprint and behaviour of apps as a result.
I've suffered the problem once since I've had the Nexus5x and that was due to the music player (Soundcloud) being a memory hog (120MB+) with it's background music player service coupled with a memory leak in the driving app I was testing at the time - Automate - it was peaking at 460MB use.
I'm not so precious about what is installed now but anything that wants to run a constant service either has to be tiny when running that service or absolutely fundamental to my use of the device.
I find this to be the worst problem .We want to kill our apps like we are use to.Switching between email and chrome is horrible especially when you have to start your application all-over again (submission request) Hopefully some XDA member will figure out how to solve this issue. For now I am testing DEVELOPER OPTIONS allow running
apps in background ? Anyone know what the default value is??
Hello there! I have ASUS Zenfone 2 and I want an android browser that has AdBlock and is also capable to Sync bookmarks and tabs with browser on PC and other devices (so Adblock Browser isn't being considered). The two options I come across are Maxthon and Firefox.
I have used Maxthon in the past (both PC and Android Versions) and have preferences for it, but I want to now between Maxthon and Firefox, what has the best CPU, RAM and Battery Usage (mainly battery usage since Zenfone has the long known issues with battery life).
I have found an article on PhoneArena showing the advantage to Maxthon on page rendering and loadtime, however no word is said about the hardware performance.
So, anyone knows which one is better?
PS: I won't be using Chrome because no.
PS²: Sorry for my english, I'm not native speaker
Link to the article on PhoneArena
phonearena.com/news/Best-Android-browsers-2015-edition-design-features-and-performance_id67848
colddyshadow said:
Hello there! I have ASUS Zenfone 2 and I want an android browser that has AdBlock and is also capable to Sync bookmarks and tabs with browser on PC and other devices (so Adblock Browser isn't being considered). The two options I come across are Maxthon and Firefox.
I have used Maxthon in the past (both PC and Android Versions) and have preferences for it, but I want to now between Maxthon and Firefox, what has the best CPU, RAM and Battery Usage (mainly battery usage since Zenfone has the long known issues with battery life).
I have found an article on PhoneArena showing the advantage to Maxthon on page rendering and loadtime, however no word is said about the hardware performance.
So, anyone knows which one is better?
PS: I won't be using Chrome because no.
PS²: Sorry for my english, I'm not native speaker
Link to the article on PhoneArena
phonearena.com/news/Best-Android-browsers-2015-edition-design-features-and-performance_id67848
Click to expand...
Click to collapse
Whichever you feel is faster! If you are a numbers man try this app and see which launches faster.
https://play.google.com/store/apps/...o.androidbenchmarkaccessibilityrecorder&hl=en
blazzer12 said:
Whichever you feel is faster! If you are a numbers man try this app and see which launches faster.
Click to expand...
Click to collapse
Oh, thanks for the reply, but what I mean is which one consumes less CPU, RAM and Battery.
There is an APP with I can test those parameters?
I tried both today again after months and I personally hate Firefox on Android, it is so slow (maybe only on Intel X86?)..I tried also Maxthon but I'm not impressed..I will suggest you Maxthon, Firefox is too slow! There are anyway a lot of ad-blocking browsers, Lightning Browser (only pro) for example, you can also try latest Asus Browser (I don't know if now is stable or you still need to join beta on google plus, anyway they added ad-block support).
hi there
i can confirm, firefox (not beta) has a lot better
some sites when using maxthon is dissaponted
e.g, try browse 'kumpulbagi.com' or 'kumpulbagi.id' without quote using maxthon and firefox, set to the desktop mode..you can see maxthon can't zoom out as firefox do
and firefox has several filter adblocker you can choose, i have to admit firefox too slow at the past than maxthon but im impressed with firefox now
anyway, other browser that you can consider is asus browser, now has adblocker, you can do compare how fast and see the RAM consume
hope you can choose the best and match
colddyshadow said:
Oh, thanks for the reply, but what I mean is which one consumes less CPU, RAM and Battery.
There is an APP with I can test those parameters?
Click to expand...
Click to collapse
GSam Battery Monitor does give you CPU and Battery usage of an app.
For RAM usage you can goto : Settings - > Apps - > Running.
Firefox beta has some experimental features for x86 that make it run pretty smooth for me
Installed it about an hour ago (UK) and in general the phone seems a noticeably zippier for browsing and opening apps etc.
I am not a tech head, and the update is small, only 13 ish megabytes, but feels like the sluggishness I had been experiencing the last six months has gone somewhat. I had really set my mind and wallet on getting a Pixel 4a, but may stick with this a bit longer if the sluggishness has improved.
Wonder if others are finding the same ?
DonkeyKonk said:
Installed it about an hour ago (UK) and in general the phone seems a noticeably zippier for browsing and opening apps etc.
Click to expand...
Click to collapse
You rebooted to install it and that is known to temporarily solve the "ram issues" that android 10 has on this phone.
It's not the update.
a1291762 said:
You rebooted to install it and that is known to temporarily solve the "ram issues" that android 10 has on this phone.
It's not the update.
Click to expand...
Click to collapse
Ohh, it is the update. This one really made the phone feel snappier, and visibly improved performance. Usually it slugs down to a crawl while I'm testing to see if it's still usable after the update, and even after 24hrs after the update it still works just fine, no hogs, no slow downs, minimal stuttering while heavy multi-tasking.
For example, on 11.0.7, go to Chrome, access fast.com (internet speed test) - it downloads and uploads a test file, so intensive i/o memory usage, and try closing the tab and chrome while still downloading... it's slow, it stutters a lot, it occasionally freezes the device, that doesn't happen anymore in august update. Also the speed limitation I was talking about in my review of 11.0.9 is now gone.
TeoXSD said:
Ohh, it is the update. This one really made the phone feel snappier, and visibly improved performance. Usually it slugs down to a crawl while I'm testing to see if it's still usable after the update, and even after 24hrs after the update it still works just fine, no hogs, no slow downs, minimal stuttering while heavy multi-tasking.
For example, on 11.0.7, go to Chrome, access fast.com (internet speed test) - it downloads and uploads a test file, so intensive i/o memory usage, and try closing the tab and chrome while still downloading... it's slow, it stutters a lot, it occasionally freezes the device, that doesn't happen anymore in august update. Also the speed limitation I was talking about in my review of 11.0.9 is now gone.
Click to expand...
Click to collapse
Well I think these ss weren't automated replies after all.
TeoXSD said:
even after 24hrs after the update it still works just fine
Click to expand...
Click to collapse
Apparently I rebooted this morning so I only have 16 hours of uptime. But I have been rebooting weekly so I feel it is still a bit early to be celebrating.
That said, I did just have XDA stay in memory while I downloaded podcasts, updated apps and opened some pages in both Firefox beta and Firefox (opening pages to copy urls over without sync).
Maybe it was a build.prop tweak. That would be small...
a1291762 said:
Apparently I rebooted this morning so I only have 16 hours of uptime. But I have been rebooting weekly so I feel it is still a bit early to be celebrating.
That said, I did just have XDA stay in memory while I downloaded podcasts, updated apps and opened some pages in both Firefox beta and Firefox (opening pages to copy urls over without sync).
Maybe it was a build.prop tweak. That would be small...
Click to expand...
Click to collapse
Actually what I want to say is I am using l speed and I have changed the RAM management profile to multitasking and that fixes my issue and basically it is it editing the build prop my question is if Xiaomi did the same thing and fix the issue isn't it good I mean I can do it with root but all they did was changed this thing which they could have done a long time ago but do keep in mind whenever I use this profile my battery drains a bit faster not like a lot faster only a little bit faster.
Aadil Gillani said:
I am using l speed and I have changed the RAM management profile to multitasking and that fixes my issue and basically it is it editing the build prop my question is if Xiaomi did the same thing and fix the issue isn't it good
Click to expand...
Click to collapse
I found lspeed and friends to extend the time I could run before reboot, not fix the problem.
But now I'm curious so I'm gonna diff the partitions to find out what they changed.
a1291762 said:
I found lspeed and friends to extend the time I could run before reboot, not fix the problem.
But now I'm curious so I'm gonna diff the partitions to find out what they changed.
Click to expand...
Click to collapse
Please do tell what they changed
I'm ... not seeing anything obvious
build.prop changed, but it's just timestamps and versions (ie. normal "make a release" stuff)
only boot, system and vendor were modified
I've attached the diff report (not changes, just modified files), minus a large number of .odex files.
Looks like some media lib bugs got fixed.
I dunno... also, I tried to run the diff on my phone and killed it so my uptime was reset again (finished the comparison on my computer, after converting and mounting the images).
TeoXSD said:
Ohh, it is the update. This one really made the phone feel snappier, and visibly improved performance. Usually it slugs down to a crawl while I'm testing to see if it's still usable after the update, and even after 24hrs after the update it still works just fine, no hogs, no slow downs, minimal stuttering while heavy multi-tasking.
For example, on 11.0.7, go to Chrome, access fast.com (internet speed test) - it downloads and uploads a test file, so intensive i/o memory usage, and try closing the tab and chrome while still downloading... it's slow, it stutters a lot, it occasionally freezes the device, that doesn't happen anymore in august update. Also the speed limitation I was talking about in my review of 11.0.9 is now gone.
Click to expand...
Click to collapse
I have downgraded to android 8.1 version 9.6.11.0
Tried that thing with fast.com no stutter nothing! I would suggest everybody who is tired with xiaomi updates on this phone to downgrade to android 8.1 like i did and it will remind the reason why you purchased this phone in the first place! Its super fast, super responsive, the statusbar icons dont take to much space, everything is working and games will be in ram even if you minimize at morning and reopen at midnight! I thought i would change my phone because it was useless and now it is faster than i ever remembered!
Nearly 4 days of uptime and my phone is once again killing apps as soon as I leave them.
Well nearly been a week now since the update, and definitely feels to me.that things have improved at lot in general use.
Not as good as it was brand new, but nowhere near as bad as it was getting the previous few months, and very usable.
Battery life seems to have gotten back to where it was before too.