Okay, I got sick of using Quadrant for benchmarking filesystem improvements, so I spent the last hour or so on this: RealBench!
It's pretty crappy right now, but I plan to add all kinds of different (hopefully) real-world-ish benchmarks.
For now it has just one benchmark -- a benchmark that heavily stresses the filesystem for both reading and writing, as well as heavily stressing ram and the garbage collector. Basically, this is a benchmark designed to do as poorly as possible with the SGS's stock problems. Increases in this benchmark really should correlate with a better, more responsive everyday phone. (Not perfect at this stage though, it still needs work!)
Anyway, it will list the current fps at the top of the screen while it's running. Higher is better! It's also easy to visually see the difference, as it scrolls a bit smoother. If you have any other devices, test this out on them and report back with the scores!
V1.1 Changes
Now writes 1000 files (~30mb of data), and picks randomly from them. This should make it impossible for any caching to occur.
V1.2 Changes
Better cleanup, better initialization.
V1.4 Changes
File writing is now on a separate thread from reading, to give a better estimate of real world usage.
File writing/reading is no longer a 50-50 split, it is now closer to a 80-20 split, for better real world usage.
FC bug fixes.
Black screen on start fixed.
V1.4.1 Changes
Fix for app close.
Notes
Any task which will take focus away from this app will cause it to close. Phone calls, etc.
Please give the version number with any score!
The difference between stock and oclf looks way too big, I hope I haven't made some mistake somewhere!
This benchmark copies a bitmap out of its apk into ram, and then saves it to disk with a random file name. It then reads that bitmap back out of the new file, decodes it into a drawable, and puts it on screen.
This should stress read, writing, and memory usage.
OCLF should not be getting a boost that huge though, I would have thought. Something may be wrong.
Anyway, test this out on other devices such as the N1 and report back, please!
Stock JPC w/o any lagfixes or even root:
Last Minute FPS: 10.92
Longest Period without frames: 1.21sec
Ooooo nifty, giving this a shot
XWJM7 + voodoo beta 1
Last Minute FPS: ~12, Longest period without frames: ~0.93 sec
Almost stock values.
I noticed that in a brief period the current FPS jumps tp 55 and then drops to 11.
cba1986 said:
XWJM7 + voodoo beta 1
Last Minute FPS: ~12, Longest period without frames: ~0.93 sec
Almost stock values.
I noticed that in a brief period the current FPS jumps tp 55 and then drops to 11.
Click to expand...
Click to collapse
OCLF values might be heavily inflated, I'm going to try write a huge whack of files to the disk and pick a random one to read back. That will get rid of any possible caching that might be inflating OCLF scores.
Voodoo being the same as stock is a bit worrying though... hummm...
EDIT: Tried voodoo, and left it running for awhile, and it was getting 13+ which is a pretty good improvement from 10 I guess.
Anyway, new version going up which will get around any caching problems!
JM5 + any lagfix
Last Minute FPS: ~9, Longest period without frames: 0.96 sec
V1.1 is up now! Here is the core of the benchmark for anyone who wants to know what it's doing.
Code:
int rint = r.nextInt() % 3;
int bmpres;
if (rint == 0) {
bmpres = R.raw.blackbar;
} else if (rint == 1) {
bmpres = R.raw.greenbar;
} else {
bmpres = R.raw.redbar;
}
try {
InputStream is = getResources().openRawResource(bmpres);
String Filename = UUID.randomUUID().toString();
FileOutputStream fos = openFileOutput(Filename, 0);
byte[] bytebuf = new byte[1024];
int read;
while ((read = is.read(bytebuf)) >= 0) {
fos.write(bytebuf, 0, read);
}
is.close();
fos.getChannel().force(true);
fos.flush();
fos.close();
FileNames.add(Filename);
int pickrandom = r.nextInt(FileNames.size());
Filename = FileNames.get(pickrandom);
is = openFileInput(Filename);
ByteArrayOutputStream baos = new ByteArrayOutputStream();
while ((read = is.read(bytebuf)) >= 0) {
baos.write(bytebuf, 0, read);
}
byte[] rawimage = baos.toByteArray();
BitmapDrawable bmpdraw = new BitmapDrawable(BitmapFactory.decodeByteArray(rawimage, 0, rawimage.length));
is.close();
convertView.setBackgroundDrawable(bmpdraw);
if (FileNames.size()>1000) {
pickrandom = r.nextInt(FileNames.size());
Filename = FileNames.get(pickrandom);
File file = new File(getFilesDir(), Filename);
file.delete();
FileNames.remove(pickrandom);
}
} catch (Exception ex) {
ex.printStackTrace();
}
So I tried v1.1 on my stock JPC w/o any lagfix.
Last Minute FPS - 12.64
Longest Period without frames: 1.19s
During the initial 15 seconds, it was constantly 15+ FPS. Max I saw was 22.
EDIT: That's weird though. My previous setup - JM5 + CFLagFix (which I believe is almost the same as OCLF) was a lot smoother in certain places. I'd have expected the difference in scores to be bigger.
Okay, OCLF (EXT2) on v1.1 is still giving me 50 fps. I'm stumped.
JM1 Rev3 with Voodoo kernel on Captivate
Last Minute FPS - 12.72
Longest Period without frames: 1.27 s
I9000HVJH1 docmod v4, 1,20 oc, Ryan lag fix 2,3
last min fps 55,37
tot average fps 49,63
longest 10,21s
JPC OCLF apk
Last minute - 54.31 fps
Longest - 2.11
HTC Desire official froyo, unrooted
Doesn't run. Just shows a black screen then forces close after a minute or so
Sent from my GT-I9000 using XDA App
v1.2 on my JPC stays on the black screen at start up for about a minute, runs at 4-5 FPS for a few seconds and then FC's.
v1.4 is up on the first post, with big changes. I'm still a bit confused why EXT2 performs so much better at writing than EXT4. If anybody has any ideas...
Version 1.2. XWJM5 Hackeclair, Project Voodoo beta1. With 54 installed apps.
The results do not look great. The first tests were done without restarting, it's been running quite a while, and I used and installed quite a bunch of stuff since last time I restarted the phone. So a nice worst case scenarie.
It takes 30~60 seconds of black screen before it starts, LMFPS 11.72, LPWF 3.53 sec.
Second time it closed after a 30~60 sec black screen, third time it FCs after 30~60 sec black screen. Fourth attempt it simply closed itself after a duration of black screen. Oh, and a FC error comes like 20 seconds after it actually closed...
I guess that at least this means it stresses the phone really well!
(The first run it was plugged into my PC, with the SD mounted, btw. In case we find out that actually matters.)
Time to try it from a fresh boot.
Meh. Last minute 10.22. Longest without frames 4.62 seconds.
Edit:
Version 1.4.
Starts pretty much instantly. FC after running for about 20 seconds. I did have an orientation change or two during the this, no idea of that's related.
Second run, no black screen, initating takes 5 seconds or so.
Longest without frames started out really well, 0.45 sec. And then it froze for 3.14 sec. FPS is all over the place. Between 1 (displayed after a freeze) and 55. Last minute FPS 34.60. Last minute FPS is 23.90 a few minutes later... Total average FPS went from 32 to 27. No crashes, after running for at least 5 minutes.
Oh, and then it gave me an FC when I used the hardware Back button to close it.
Third run with version 1.4.
Longest withuot frames was 0.82, until I had another 3 second freeze. Several freezes. Last minute FPS 22.65. The whole thing is not running smooth at all. Sometimes it runs fine for a few seconds, and that 'normal' FPS seems to be around 50~60, but then it will start become laggy again (many smaller and larger freezes) resulting in 20~26 FPS averages. And FC at close again.
v1.4 on stock JPC
Last minute FPS: 26.98
Longest without frames: 1.4s
Crashes after a minute and a half.
EDIT:
Tried again. 30.79 LM FPS. Longest time without frames - 0.7s. Crashed after a minute and a half again though.
v1.2 on JM5 + root + voodoo
Last minute: 11-14fps
Longest period: ~0.9s but did jump to over 3s at one point when fps dropped to 1.
From watching the benchmark, as it being a repetative one, I'd expect it give roughly the same fps all the time but it keeps jumping between 7 and +50 fps.
ed10000 said:
v1.4 on stock JPC
Last minute FPS: 26.98
Longest without frames: 1.4s
Crashes after a minute and a half.
EDIT:
Tried again. 30.79 LM FPS. Longest time without frames - 0.7s. Crashed after a minute and a half again though.
Click to expand...
Click to collapse
Crashes are pretty strange, since mine running on JP8 does not crash. Left it running a few minutes. It could be highlighting a bug in JPC for all I know, though.
Anyway I'm going to leave 1.4 up without changes for now, and hopefully people with some time can run it on different phones and post their results. The info from these benchmarks should hopefully prove helpful in the future. Specially when compared with different devices.
CazeW said:
v1.2 on JM5 + root + voodoo
Last minute: 11-14fps
Longest period: ~0.9s but did jump to over 3s at one point when fps dropped to 1.
From watching the benchmark, as it being a repetative one, I'd expect it give roughly the same fps all the time but it keeps jumping between 7 and +50 fps.
Click to expand...
Click to collapse
Looks can be deceiving. Each image you see flying past is chosen randomly from a list of 1000 images. This means that buffering can't be playing a role in the results.
As far as the fps jumping, this is from
a) Garbage collection being very heavily stressed out by this.
b) filesystem caches/other
Related
ok this is the guide from Qzytor
http://forum.xda-developers.com/showthread.php?t=725290&page=120
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device -- (I'm using v.1 becouse with v.2 i didn't get above 700mhz)
Install oruam57s SetCpuSpeed v1.0d on SD card.
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
SKTools Benchmark at 672 MHz:
Intiger = 416.5933 Moves/25 usec.(At stock speed Intiger = 332.6351)
Floating point = 9.56 MWIPS. (At stock speed Floating point = 7.47 MWIPS)
I haven't tested it but this should also work on SEX1 and Touch Diamond.
OVERCLOCK AT YOUR OWN RISK.
ok thats Qzytor post which is really great and i'm very thankfull for this
this is my setting and i try this on energy and valkyrie rom working on xperia
BootTime = 90000
CheckTime = 20
Command = 0
PerfomanceLevel = 39 (thats 744mhz and it's stabel for me )
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
but i'm using msm7kcpuspped v1 not v2 .....
you don't need to plug in the phone especially when the phone boots up (thats was may first mistake i never wait the phone to fully boot up , and i was allways presing some buttons and that's way my phone was freezing so just wait and you will see for yourself
it's working stable but only plug in to ac adapter ....the speed is quite impresive ..
X1 freeze even on AC Adapter
Can't get this app to work on my x1 even on ac adapter.
Each time I try to adjust the speed my x1 will freeze immediately and I had to hard reset it. It's even freeze when I underclock it.
Can anyone tell me what's wrong with it? By the way I'm using WM6.5.3 ROM. Could this be the reason?
Thanks.
NoXsTeR said:
Can't get this app to work on my x1 even on ac adapter.
Each time I try to adjust the speed my x1 will freeze immediately and I had to hard reset it. It's even freeze when I underclock it.
Can anyone tell me what's wrong with it? By the way I'm using WM6.5.3 ROM. Could this be the reason?
Thanks.
Click to expand...
Click to collapse
i'm using energy 17th rom standard...do you have any other software for overclocking , try only conected to your computer ...
[X1 Freeze SOLVED] Connect to AC power from PC
dude!! finally got it running while connected to pc.. thanks for the tip
currently oc speed up to 652.8.. scrolling now a bit smoother.. video playback on wm player almost flawless..
dude what's the highest speed you achieve without ac power?
NoXsTeR said:
dude!! finally got it running while connected to pc.. thanks for the tip
currently oc speed up to 652.8.. scrolling now a bit smoother.. video playback on wm player almost flawless..
dude what's the highest speed you achieve without ac power?
Click to expand...
Click to collapse
691 mhz , then i unpluged and it was working for quite a while , but we must all wait for new version ...and hope for the best
max stable oc is 671mhz.
evryone which would like to overclock xperia ,see this post
#1191
http://forum.xda-developers.com/showthread.php?t=725290&page=120
it really works on battery power no SOD for now (last 4 hours) on 692 mhz ...
i'm using now latest valkyrie rom ...
you must try this if you want to overclock your phone for maximum performance .
if anyone overclock above 692 please post here ....
fil--21 said:
evryone which would like to overclock xperia ,see this post
#1191
http://forum.xda-developers.com/showthread.php?t=725290&page=120
it really works on battery power no SOD for now (last 4 hours) on 692 mhz ...
i'm using now latest valkyrie rom ...
you must try this if you want to overclock your phone for maximum performance .
if anyone overclock above 692 please post here ....
Click to expand...
Click to collapse
Where did u get the setcpuspeed 1.0d?
ok here .... please post your findings here
fil--21 said:
ok here .... please post your findings here
Click to expand...
Click to collapse
Doesnt works for me,they always returns the PerfomanceLevel to 30.
Tell me, any difference running at 692? May i see youtube videos on Skyfire? And the battery drain?
Ok, now it works but my max PerfomanceLevel is 33 (634mhz)
fil--21 said:
691 mhz , then i unpluged and it was working for quite a while , but we must all wait for new version ...and hope for the best
Click to expand...
Click to collapse
What numbers do you use?
BootTime =
CheckTime =
Command = 0
PerfomanceLevel =
ScreenOffPerfomanceLevel =
SettlingTime =
Results
634mhz:
387
9.150
stock:
330
7.756
I dont know what it means
i use
BootTime =90000
CheckTime =20
Command = 0
PerfomanceLevel =36
ScreenOffPerfomanceLevel =27
SettlingTime =10
and i use it for two days without any SOD ...but i think this is the max what xperia can achieve ...becouse any other setting above performance level 36 is SOD or restart ... but performance was quite impressive ...i will post the results later .... i can only say that performance in fpsece was better (playable) around 25-30 fps ..before 15-20
I don't understand this step: "Go to HKLM\Software\Msm7kCpuSpeed"
How to do that?
njerkan said:
I don't understand this step: "Go to HKLM\Software\Msm7kCpuSpeed"
How to do that?
Click to expand...
Click to collapse
Use a registry editor to navigate to that "folder." If you google registry editor, you'll figure it out.
there is another tool for overclocking called OCT 1.5 , but i coludn't overclocked not even for 10 mhz , its allways frezes ,so if anybody can overclocked with this tool please let us know....
i use now xperia overclocked to 692 mhz in i see an improvement but i would like to overclocked to 768 mhz , ....if you have touch pro 2 is that quite easy to achieve (so it looks ) ...
so if anyone can explain to me what's the difference that they overclocked so high ?
Hi! Just to let you know: I OC'ed my xperia to 748Mhz. Running stable for 2-3 days.
Used settings:
BootTime: 90000
CheckTime: 20
Command: 0
PerformanceLevel: 39
ScreenOffPerformanceLevel: 25
SettlingTime: 10
phini said:
Hi! Just to let you know: I OC'ed my xperia to 748Mhz. Running stable for 2-3 days.
Used settings:
BootTime: 90000
CheckTime: 20
Command: 0
PerformanceLevel: 39
ScreenOffPerformanceLevel: 25
SettlingTime: 10
Click to expand...
Click to collapse
?? really which rom do you have ? that's quite immpresive becouse i never get over 700 mhz and i tried a lot of diffrent roms ...
are you using fpsece ? is there any progress on fps ? please let me know
I'm using this rom for a week now, and i have to say, i'm overly satisfied with it.
Apps that installed (wich matters): Lucky Patcher (nos system patches), Freedom (no freecore mode), SuperSU, GLTools, SwiftKey
Bugs(it doesn't really have any), issues:
-I only had 2 random reboots so far, but SwiftKey is force closing time to time(although it's not a problem - it restarts instantly, and you got the keyboard properly in no time).
-Flashlight is not turning on sometimes (maybe low battery could be an issue, i dont know).
-If you enable "Live Display", you'll have a massive framedrop (to be honest, it's not a big deal, i don't need it.)
-The default launcher's app drawer runs on low fps when sliding between pages(i have only 2 pages yet)
-Sometimes Google Play crashes when i browsing descriptions.
Pros:
-Its really smooth, and runs at 60 fps
-EVERYTHING works properly.
-It's 5.1! The perfomance is just great. Max free ram i had is around 460mb, avarage is 380, minimum is 230(when 5 games running in the back).
-In Antutu i'v got 21684, wich is acceptable i think, this was the highest score i got (i used Miui before).
-Heating is not an issue, it handles well, and stays below 50 celsius
-I can't say much about battery, but i think its same as on MIUI
I hope this can help desiding wheter to download the rom, or not.
---[UPDATE]---
The camera is useless in the summer. If the device is heating up, the camera cant set the brightness properly, and it scales from lowest to highest constantly. If the device is cooled down enough, it can be used again.
Also, heating causes massive framedrop (not a surprise though).
-----------------
You can find the ROM on Yirom. (Use Google Translator).
Great Ron
I am also using it for around a week now and totally agree with your view. I love the performance and battery life. BTW I got 22800 in antutu after a fresh boot. :good:
Hello people!
From about one week with normal phone usage after for example 1 to 2 3 hours of usage after fresh restart my phone seems to lag and this lag expresses on laggy everything.When i swipe menus or whatever the animation isnt fluid but more like 10 or 15 fps and this concerns every aspekt of the phone.Even the camera seems to be laggy or choppy.I didnt rooted it nor i have made any drastical changes on it.I cant be sure if it is from an app but i uninstalled apps that are 1 or 2 weeks old.When i restart the phone i get another 2 hours smoothness and then again.I havent noticed any processor or gpu changes when it us smooth and when it is laggy.
Thank you for your feedback!
discoverymen1999 said:
Hello people!
From about one week with normal phone usage after for example 1 to 2 3 hours of usage after fresh restart my phone seems to lag and this lag expresses on laggy everything.When i swipe menus or whatever the animation isnt fluid but more like 10 or 15 fps and this concerns every aspekt of the phone.Even the camera seems to be laggy or choppy.I didnt rooted it nor i have made any drastical changes on it.I cant be sure if it is from an app but i uninstalled apps that are 1 or 2 weeks old.When i restart the phone i get another 2 hours smoothness and then again.I havent noticed any processor or gpu changes when it us smooth and when it is laggy.
Thank you for your feedback!
Click to expand...
Click to collapse
Thats just ram issues that everyone has
Nothing you can do about that
Oh It's certainly not a ram issue every time i check i have between 700 and 1 gb of free ram
Not sure if this is the right thread to talk about it, but recently I flashed the 5.4 version of this kernel http://forum.xda-developers.com/showthread.php?t=2775998 and so far so good, it fixed the 4.4.2 S Pen problem. However, I've noticed that, when I use multitask mode (2 apps open at the same time stacked on top of each other), there is some light stuttering(?). Not laggy, but when I scroll it kinda stutters a bit. Strangely enough, this only happens during multitask mode, not if I have a lot of apps open in the background. This isn't the real problem though, the real problem is that the kernel seems to cause the S Note app to lag so much that it's almost unusable. Another problem i've found was that SOMETIMES when listening to music when the screen is off, the music lags so much that it's inaudible. Not often, though, and I dorn know what specifically causes it, other than the low GPU speed. The kernel specifically states this:
"GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel"
I'm taking a guess here but I think that the low, non editable GPU settings are causing the slowdowns.
Is there any way to somehow increase the GPU, even though it says that it's uneditable? Has anyone used this kernel before and found out how to fix it? Would downgrading to a lower version of the kernel fix the slowdowns? This is the only kernel I found that fixed the slowdown for my device, I can't really install a different one, but I can downgrade this specific kernel, which I think could fix it but I'm not sure. Are there any other fixes?
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.