Database Develop

slow sms scrolling and viewing...

Hallo,
I'm new to PPC and realised the scrolling and viewing of sms & mms is very slow. . Initially I thought it was normal for PPC, but my friend told me is abnormal after he view it.
Any advise please.
Good day

Most likely related to the lack of drivers for the Kaiser.... but I'm sure someboday else can confirm.

Audio said:
Most likely related to the lack of drivers for the Kaiser.... but I'm sure someboday else can confirm.
Click to expand...
Click to collapse
Mmm. And that's based on what precisely? Actually it's probably unlikely to be due to the drivers. ********* Edited for pettiness.
Some people are tending to attribute problems to video drivers and little help or thought is being put into what the real cause of problems may be.
This is the same kind of mis-information as when folk were saying the PIE scrolling was down to the drivers (and again it was unrelated to them) OR again when the speed of the camera was put down to the drivers (and again newer software shows this was not the case).
In reply to the OP. Please give us some more detail, circumstances when it happens, how slow is it, are you running any other programs concurrently etc.
Mike

ive noticed that after about 2 hours on my phone (with under 45% memory usage) my txt messages also lag. i write the entire message and it takes like 30 secounds for the message to show up for me to be able to send it. its really annoying

Obviously I'm no Kaiser Wizz, which is why I didn't say "Your problem is because of lack of drivers" (I also missed the sms bit, and thought the issue was only related to MMS, which reading again makes my first post sound insane), but thanks for being patronising in your correcting me and thanks for the mindless sheep insult (which although isn't directly poitned at me, clearly shows I'm the intended recipient).
OR again when the speed of the camera was put down to the drivers (and again newer software shows this was not the case).
Click to expand...
Click to collapse
From what I've seen this has not actually been proven yet, a few HTC Camera Cab's have been released which increase FPS a miniscule amount, but hardly a fix, and not really enough to say that poor Camera speeds are not because of lack of drivers. I'm not saying they definately are, but from your statement you seem to have completey dis-regarded drivers from the issue.

try messing around with the cache tweaks, or flash a new rom

should i increase or decrease the cache in this situation?

Audio said:
Obviously I'm no Kaiser Wizz, which is why I didn't say "Your problem is because of lack of drivers" (I also missed the sms bit, and thought the issue was only related to MMS, which reading again makes my first post sound insane), but thanks for being patronising in your correcting me and thanks for the mindless sheep insult (which although isn't directly poitned at me, clearly shows I'm the intended recipient).
From what I've seen this has not actually been proven yet, a few HTC Camera Cab's have been released which increase FPS a miniscule amount, but hardly a fix, and not really enough to say that poor Camera speeds are not because of lack of drivers. I'm not saying they definately are, but from your statement you seem to have completey dis-regarded drivers from the issue.
Click to expand...
Click to collapse
You are right, my apologies - I have edited my post.
You will be interested to know that a Mod cannot ban himself - I know I tried yesterday but it tells me I'm an "invalid user" - I knew there was something wrong with me
Mike

heh ^
on a serious and honest note - i beleive that the lack of drivers might potentially have something to do with this, but not the camera
rendering an sms or an mms is mostly a one time render into a buffer of sorts which is then blitted onto the screen - obviously the blitting could/would be hardware accelerated but on a 320x240 screen you arent really going to see a significant slowdown due to moving memory around (as thats all is what happens - in well written software at least) unless the bandwidth is really small - some software however re-renders things based on the changing view rectangle - ie a browsers (internet exploder) view port or the icons in the scrolling programs list (i think this might be compounded by the actual icons not being cached by the OS, so it has to pull them from memory and process them every time) - the lag in these programs are caused by the program re-rendering things many times as the view rectangle changes - this would no doubt vastly improve if/when hw accelerated drivers come out.
to talk numbers 320*240*2 (the 2 is the 16bit colour) is 192k of data for a fullscreen of pixels (excluding any z/stencil/accum buffering etc) now i dont actually know the refresh rate of the device but im guessing its either 30hz or 60hz - so every second, worse case senario, 192k * 60 = 11.25Mb/s of pixel data is flying through the memory onto the screen. actually thats not worst case - because often with (proprietry, non-OS) z ordered windowing/raster systems, things are rendered back to front, sometimes with significant overdraw - pushing the pixel rate up even higher.
if you look at the camera in a nice light bright setting, its smooth and functional - this tells me that the memory has enough bandwidth.
programs that arent coded well (ie they just assume hw acceleration and cosntantly rerender) will feel crap and slow on software renderers - programs that are optimised will have considerably less lag on software but would be super sprightly on hardware. does any of this make sense?
as for the camera - same thing, its just a fullscreen blit of memory - i beleive the problem with the camera is the software that is controlling it and applying that superannoying constant nightmode filter - i can only assume this is being done because of the severely low quality of the camera especially in low light conditions (they must feel the need to 'beef it up' with software post processes).
anyway thats my tangential 2p

same problem here is there any solution so far?

OR again when the speed of the camera was put down to the drivers (and again newer software shows this was not the case).
Click to expand...
Click to collapse
From what I've seen this has not actually been proven yet, a few HTC Camera Cab's have been released which increase FPS a miniscule amount, but hardly a fix, and not really enough to say that poor Camera speeds are not because of lack of drivers.
Click to expand...
Click to collapse
So there is a slight fix for the camera. Can someone direct me to where it can be found?

[Q] Purchase decision, but many questions unanswered

I currently own a HTC Wildfire, which is decent for the most part, but I'm missing some features...and I saw a heavy price drop for Nexus One, but I cant find enough information about it (all reviews seem to be highly outdated and based on the initial Android 2.1 version)...so I would like to ask a few questions:
What is the latest Android (official) version available for it?
Is it still a supported device (as in will it receive future updates or they declared that it's at it's last one)?
How good is the Flash Player 10.1 support? Is it comparable to desktop use (can play videos on all pages or if the video is high quality it'll freeze and stuff)?
How good are the games on it? Mostly referring to games such as Asphalt, Angry Birds, Order of Chaos and other "quality" games (not just the basic ones)...if possible a compatibility list or examples of the game-quality would be greatly appreciated.
[IMPORTANT] I heard there was mo multi-touch support...is it true?
Any notable flaws or features that make it better than other devices (of the same rank that is, not the latest models)?
The price I'm being offered is 140€, which is still a lot for me (with this economy =| ), so I would like to get informed before making a decision...anyone can help?
Thanks in advance!

Can only answer some of your questions.
1. The latest official version is Gingerbread 2.3.6. Released a few weeks ago
2. Not sure at the moment. I believe Ice Cream Sandwich (future release) can run on the Nexus S, so there is a chance it might show up on the Nexus One. If not, there will probably be a ROM from the devs.
3. Flash gets updated regularly from the market. Not sure it's fair to compare a phone to a desktop. So far it's going fine for me.
6. There are some notable hardware issues. The power button has been known to fail. There's also an issue with touch response that occurs every so often. Turning off the screen and turning it back on solves it. It's the biggest annoyance for me.

[*]What is the latest Android (official) version available for it?
[*]Is it still a supported device (as in will it receive future updates or they declared that it's at it's last one)?
[*]How good is the Flash Player 10.1 support? Is it comparable to desktop use (can play videos on all pages or if the video is high quality it'll freeze and stuff)?
[*]How good are the games on it? Mostly referring to games such as Asphalt, Angry Birds, Order of Chaos and other "quality" games (not just the basic ones)...if possible a compatibility list or examples of the game-quality would be greatly appreciated.
[*][IMPORTANT] I heard there was mo multi-touch support...is it true?
[*]Any notable flaws or features that make it better than other devices (of the same rank that is, not the latest models)?
1. As mentioned by Liko, 2.3.6 is the latest official Android version for the N1. If you go with custom ROMs, the 2.3.7 is available through CyanogenMod on some of their later nightlies.
2. It is unknown how far the support for the N1 will go. People were speculating that it may not receive the Gingerbread update (which, obviously, isn't true). Google has not specified whether or not the N1 will receive ICS, although, I believe that it will get it. But even after official support dies, there will always be custom ROMs that will allow it to keep going (the G1 officially supports 1.6, but through developers, they have gotten it to support a limited version of 2.3).
3. Flash on phones will never be as robust as flash on desktops. There can never be support for mouseovers, and the lack of a mouse can make things difficult. Also, some sites just don't support the on phones (I know roosterteeth.com used to be one, I don't know if it has changed). But 99% of the times I have needed flash support (I enable it only when I need it), it has worked.
4. Gaming doesn't seem to be an issue with a few exceptions. Multi-touch does exist with the phone, but it is a poor implementation that does have issues sometimes. Most of the time I don't have issues with it, but sometimes with a game like SliceIt, when you are trying to use multi-touch, it goes all screwy. Other than multi-touch, the only thing that limits the N1 is a lack of more recent hardware. Some games out there require the Tegra2 processor, so those obviously won't work. But I have played all Angry Birds, Yoo Ninja, SliceIt, Cut the Rope, Death Worm, Fruit Ninja, Reckless Racing and more. I haven't ever come across performance issues other than the touch screen limitations listed above.
5. As I mentioned above, the phone does have multi-touch support. It is there, and 90% of the time it works great. I never seem to have issues with pinch-to-zoom. The main time you run into issues is when you are needing specific points that are close to a straight line on an x or y axis. It can be very spotty then.
6. There is a possibility of the powerbutton failing due to a design flaw. Most people try to find ways to minimize that by using things like Trackball Wake, and widgets and/or apps to turn off the screen and rebooting/shutting off the device. There are the multi-touch issues I mentioned above, along with sometimes the screen will just go "screwy". It is hard to explain, but just turning off the screen and turning it right back on will reset it, and it will work again. And the phone is extremely limited with internal space.
But, I do love my phone. It will be extremely hard to part with it. The AMOLED screen (if you happen to get it) is gorgeous. The phone is still quick even though it is getting close to 2 years old. It is built very well and has taken quite a few drops like a champ. Trackball notifications are AMAZING! I still don't understand why more manufacturers have not used this. The official car and home docks are very solid and I love that they have built-in connectors for those docks. And if you throw a custom ROM on there, like CyanogenMod, the phone gets 10x better.
Now with all that being said, I don't know if I can honestly recommend this phone. The biggest reason is because of its age. It does still hold up well to newer devices, but those new devices are still better. Whether they have better battery life, more internal space, or better performance. The N1 still holds its own, but it is starting to show its age.

developer-friendly AOSP roms?

Can anybody recommend an AOSP-derived ROMs whose developers are enthusiastic about bringing new developers into the fold & have spent some time making documentation and build scripts likely to be relatively straightforward for someone with lots of programming experience (including Android development) and (desktop) Linux experience... but has never managed to actually **build** a ROM from source and make it all the way to a working phone?
Why AOSP (vs Touchwiz) -- there are certain things about Android that have always annoyed me, and I'd love to try and fix. Like implementing "rotate on screen-powerup" (screen orientation normally locked & indifferent to the accelerometer state, but doing an accelerometer read whenever the screen gets turned on by pressing the power button and changing the portrait/landscape orientation at THAT time if appropriate). Or building a hacked browser that prompts to override website directives to not save credentials. Not to mention, fantasies about putting back features that Google took away from us, like ext2-formatted microSD cards. Or jacking up the touchscreen sample rate to the maximum supported by the underlying chipset whenever a Graffiti-like input method is active. Yeah, nothing hard or anything...
The closest I ever came was building CM10 about two years ago for my S3. From what I recall, I managed to get a daily build to compile without errors using a VM somebody made available... but when I finally flashed it to the phone, it just kept rebooting. From what I remember, there were generic instructions for building CM available, but I'm pretty sure there were additional steps specific to the S3 and/or AT&T that were omitted (but mandatory for a working ROM). Or it might have been eMMC-related (I remember that phone was *always* funky about newly-flashed ROMs, and often required multiple flashes before one would "take"). Either way, I ended up badly frustrated & ultimately accomplished nothing.

Wondering if burn-in might be caused by elevated temperature from added case.

https://drive.google.com/file/d/1UO84SCeykrD6Ecb9p3yWfoUe4KN2pJs2Eg/view
Above you can see detectable (under close scrutiny, ideal conditions) burn-in of my Nexus 6 screen after the following usage:
Only 8 weeks since I bought the phone
I'm reasonably sure that this was not present when I got the device because:
1 - it was "new" from Amazon in factory sealed box (although at a bargain price $299 for 64gb which makes me wonder slightly);
2 - inspected it pretty careully when I was reading about burn in shortly after I got my device;​
My screen on time on a typical day is probably 2-5 hours per day over that 8 weeks. (although probably 5-6 hours per day during the very first week!)
Brightness is always in auto with the slider in the middle. And I don't spend a lot of time outside with my screen on.
You can see that's pretty mild usage for a relatively short time. And yet many others are reporting they absolutely can't detect anything whatsoever even after a year of use. . I'm led to believe I'm an outlier.
So what is it that might make me more susceptible than the next guy?
The "easy" answer is device quality. And it might be the right answer, but what if there's something else.
I thought about what it is in my usage (which seems relatively mild) that might possibly cause this.
Then I realized the one thing that struck me odd about this phone. I noticed the screen is warm to my fingers if I use it while charging. I didn't meausre that temperature, but I did download GSAM about a month in and and set a battery temperature alarm at 110F. If I do mild surfing while charging, battery temperature gets up to 110F within a few minutes. I don't let it go above that now, and the screen feels relatively cool compared to how hot I used to let it get. So I'm going to guess that my battery temperature used to routinely get to 115 or 120F while I was using my phone while charging. And although they're not equal, when battery gets hot screen gets hot (again I could feel the heat).
Would heat affect amoled deterioration? We wouldn't think that at first because we normally associate the deterioration with simply being energized brightly over time. But what about being energized causes that deterioration. What if it's the localized heat at the pixel from that brightly energized pixel that causes the damage. In that case, anything else which makes the phone/screen run hotter overall will tend to enhance that local damage mechanism also.
Does my phone run hotter than average? I'm not sure, but since day 1 I've been using this funky case Uniform Supcase Beetle Hybrid Pro.. It's built like an otterbox.... thick and rugged. Up to 1/4" inch thick and surrounds the phone on back, all sides, and even wraps around to cover the front bezel. Imagine that wrapping is an insulator (like a blanket), it helps to keep the heat inside so the phone underneath the blankets is hotter than it otherwise would be.
Is that case why I'm different? I dunno, all I've got is one phone as a data point and a scenario that seems plausible to me.
I'm interested to know if any others have associated elevated temperatures or a thick case with enhanced susceptibility to burn-in . Or if you believe it may be related.
By the way, I have to add my perspective this is a minor and managable thing. I still love this phone. I'm just curious about why...
There are of course many threads on subject of N6 burn-in. The biggest one here:
http://forum.xda-developers.com/nexus-6/general/burn-t2955765

electricpete1 said:
https://drive.google.com/file/d/1UO84SCeykrD6Ecb9p3yWfoUe4KN2pJs2Eg/view
Above you can see detectable (under close scrutiny, ideal conditions) burn-in of my Nexus 6 screen after the following usage:
Only 8 weeks since I bought the phone
I'm reasonably sure that this was not present when I got the device because:
1 - it was "new" from Amazon in factory sealed box (although at a bargain price $299 for 64gb which makes me wonder slightly);
2 - inspected it pretty careully when I was reading about burn in shortly after I got my device;​
My screen on time on a typical day is probably 2-5 hours per day over that 8 weeks. (although probably 5-6 hours per day during the very first week!)
Brightness is always in auto with the slider in the middle. And I don't spend a lot of time outside with my screen on.
You can see that's pretty mild usage for a relatively short time. And yet many others are reporting they absolutely can't detect anything whatsoever even after a year of use. . I'm led to believe I'm an outlier.
So what is it that might make me more susceptible than the next guy?
The "easy" answer is device quality. And it might be the right answer, but what if there's something else.
I thought about what it is in my usage (which seems relatively mild) that might possibly cause this.
Then I realized the one thing that struck me odd about this phone. I noticed the screen is warm to my fingers if I use it while charging. I didn't meausre that temperature, but I did download GSAM about a month in and and set a battery temperature alarm at 110F. If I do mild surfing while charging, battery temperature gets up to 110F within a few minutes. I don't let it go above that now, and the screen feels relatively cool compared to how hot I used to let it get. So I'm going to guess that my battery temperature used to routinely get to 115 or 120F while I was using my phone while charging. And although they're not equal, when battery gets hot screen gets hot (again I could feel the heat).
Would heat affect amoled deterioration? We wouldn't think that at first because we normally associate the deterioration with simply being energized brightly over time. But what about being energized causes that deterioration. What if it's the localized heat at the pixel from that brightly energized pixel that causes the damage. In that case, anything else which makes the phone/screen run hotter overall will tend to enhance that local damage mechanism also.
Does my phone run hotter than average? I'm not sure, but since day 1 I've been using this funky case Uniform Supcase Beetle Hybrid Pro.. It's built like an otterbox.... thick and rugged. Up to 1/4" inch thick and surrounds the phone on back, all sides, and even wraps around to cover the front bezel. Imagine that wrapping is an insulator (like a blanket), it helps to keep the heat inside so the phone underneath the blankets is hotter than it otherwise would be.
Is that case why I'm different? I dunno, all I've got is one phone as a data point and a scenario that seems plausible to me.
I'm interested to know if any others have associated elevated temperatures or a thick case with enhanced susceptibility to burn-in . Or if you believe it may be related.
By the way, I have to add my perspective this is a minor and managable thing. I still love this phone. I'm just curious about why...
There are of course many threads on subject of N6 burn-in. The biggest one here:
http://forum.xda-developers.com/nexus-6/general/burn-t2955765
Click to expand...
Click to collapse
I can notice burn in on mine (I use no case at all) but its very mild and a "burn-in fixer" like the black and white rolling lines from "Display Tester" makes it go away if ever I'm that bored to do so. Also I only ever notice it on a grey background which honestly is rare to appear where the status and button bars are. On the terms of battery temp I really have to get something going to hit >105F for instance downloading videos using multiple streams to make it go faster which requires stitching the video back together at the end which basically pegs the cpu. General browsing reading some news stories etc stays ~85-90F. Differences in temps between phone for this one in particular can swing wildly due to there being upwards of 17 different CPU "bins" (compared to something like 3-4 on the Nexus 5) with each bin being a 10mV shift in the voltage table for the CPU meaning on CPU can have a 300mhz at 810mV (bin0) and another could have it at 650mV (bin16). For reference mine is a Bin 12 or 690mV on the 300mhz and 1110mV on 2.7ghz.

Both of my devices (had the old one for about 2 months, this guy for about 1) both show burn-in similar to yours already. First was caseless, this one I run with a case. I think that burn-in is just a very widespread issue with this panel and the people claiming to not have any simply don't notice it. Maybe I got 2 bad devices fresh from amazon but, I think that's just how it is. Good news is it really doesn't bother me and I can't see it without a gray background.

electricpete1 said:
https://drive.google.com/file/d/1UO84SCeykrD6Ecb9p3yWfoUe4KN2pJs2Eg/view
Above you can see detectable (under close scrutiny, ideal conditions) burn-in of my Nexus 6 screen after the following usage:
Only 8 weeks since I bought the phone
I'm reasonably sure that this was not present when I got the device because:
1 - it was "new" from Amazon in factory sealed box (although at a bargain price $299 for 64gb which makes me wonder slightly);
2 - inspected it pretty careully when I was reading about burn in shortly after I got my device;​
My screen on time on a typical day is probably 2-5 hours per day over that 8 weeks. (although probably 5-6 hours per day during the very first week!)
Brightness is always in auto with the slider in the middle. And I don't spend a lot of time outside with my screen on.
Click to expand...
Click to collapse
That's an interesting theory.
I'm one of those who have absolutely NO detectable burn in, either permanent or latent. I also run a thick case -- Ballistic Maxx.... but... I have (used to, but don't any more) used it very hot. In particular google maps nav used to really make a lot of heat, enough that you could REALLY feel it on the screen, and even through the case. Somewhere along the lines, something changed enough in (firmware? OS? gmaps?) that this no longer gets it to heat up appreciably. Aside from that, I've *never* used it while charging -- kind of difficult to do so with wireless charging. Auto-brightness with the slider at about 1/3. I've owned it for a year now.
---------- Post added at 08:49 PM ---------- Previous post was at 08:39 PM ----------
StykerB said:
I can notice burn in on mine (I use no case at all) but its very mild and a "burn-in fixer" like the black and white rolling lines from "Display Tester" makes it go away if ever I'm that bored to do so. Also I only ever notice it on a grey background which honestly is rare to appear where the status and button bars are. On the terms of battery temp I really have to get something going to hit >105F for instance downloading videos using multiple streams to make it go faster which requires stitching the video back together at the end which basically pegs the cpu. General browsing reading some news stories etc stays ~85-90F. Differences in temps between phone for this one in particular can swing wildly due to there being upwards of 17 different CPU "bins" (compared to something like 3-4 on the Nexus 5) with each bin being a 10mV shift in the voltage table for the CPU meaning on CPU can have a 300mhz at 810mV (bin0) and another could have it at 650mV (bin16). For reference mine is a Bin 12 or 690mV on the 300mhz and 1110mV on 2.7ghz.
Click to expand...
Click to collapse
That operation *should not* be especially hard on the CPU. Its actually a fairly trivial task. Might be that your software is doing something stupid, like keeping all the different pieces separate until the end when it copies them all in sequence into a target file.
You might want to look into better downloader software. The *correct* way to perform this kind of a job, is to allocate the file in advance, and have each stream write to its correct offset in parallel. No final copy.
You might also save a heap of work if you get rid of userdata crypto. Big problem with the crypto on these when doing that kind of glue-job, is that it will be running decrypt on all the different pieces, and simultaneously running encrypt on the target file.

That operation *should not* be especially hard on the CPU. Its actually a fairly trivial task. Might be that your software is doing something stupid, like keeping all the different pieces separate until the end when it copies them all in sequence into a target file.
You might want to look into better downloader software. The *correct* way to perform this kind of a job, is to allocate the file in advance, and have each stream write to its correct offset in parallel. No final copy.
You might also save a heap of work if you get rid of userdata crypto. Big problem with the crypto on these when doing that kind of glue-job, is that it will be running decrypt on all the different pieces, and simultaneously running encrypt on the target file.
Click to expand...
Click to collapse
Well for 360p, 144p, and 720p which are the resolutions you can natively download from youtube as an MP4 do function this way (which if you download these resolutions the software just takes ~5 seconds to finalize the file after downloading). However since youtube is exactly keen on people downloading videos w/o Red (which I do have but I like having 1080p and/or 60fps for gaming style videos which Red does not allow for unfortunately). So those non-standard resolutions have to be downloaded in their little 4096 kb chunks with separate video and audio streams as if it were streaming it from the website itself and stitched together using an actual encoder. A 1080p60 video can put a sizable load ~50-100% i5 5200u laptop processor (depending on the complexity of the scene) while realtime streaming which arguably has more raw power than a N6 (part of the reason youtube still streams AVC codec to android). Now with the phone not having to actually render the video which VP9 codec isn't supported fully either device's GPU so a chunk of the load on the laptop would be rendering. The phone being able to finalize a 1080p60 30 minute video in ~1 minute is why the CPU is 100% while doing so and that just tells me it's using all the power it can to accomplish the task in parallel utilizing all 4 cores.
As for using encryption I've disabled it in the past with varied results (mostly kernel differences) but since I'm sticking with the stock rom and using the monthly ota's I've just left it on to stop any potential accidental encryption which could theoretically lead to data loss and/or the hassle of unecrypting again. In addition to this I see absolutely no gain in speed on the video stitching process which considering it performs the task at a ~15-20 MB/s rate where the limits of the encrypted storage are 200MB/s read and 90 write for sequential reading which is what the encoder is using. Since android 5.1 when the kernel was updated to take advantage of qualcomm's encryption instructions which would otherwise go unused to the OS anyway, encryption doesn't affect this type of workload.
I know this is kinda outside the scope of this thread but I have done some reading on this kinda stuff when I was trying to learn why the app needed an external app when downloading those difference resolutions which most apps wouldn't even do outside of PC software.

StykerB said:
Well for 360p, 144p, and 720p which are the resolutions you can natively download from youtube as an MP4 do function this way (which if you download these resolutions the software just takes ~5 seconds to finalize the file after downloading). However since youtube is exactly keen on people downloading videos w/o Red (which I do have but I like having 1080p and/or 60fps for gaming style videos which Red does not allow for unfortunately). So those non-standard resolutions have to be downloaded in their little 4096 kb chunks with separate video and audio streams as if it were streaming it from the website itself and stitched together using an actual encoder. A 1080p60 video can put a sizable load ~50-100% i5 5200u laptop processor (depending on the complexity of the scene) while realtime streaming which arguably has more raw power than a N6 (part of the reason youtube still streams AVC codec to android). Now with the phone not having to actually render the video which VP9 codec isn't supported fully either device's GPU so a chunk of the load on the laptop would be rendering. The phone being able to finalize a 1080p60 30 minute video in ~1 minute is why the CPU is 100% while doing so and that just tells me it's using all the power it can to accomplish the task in parallel utilizing all 4 cores.
As for using encryption I've disabled it in the past with varied results (mostly kernel differences) but since I'm sticking with the stock rom and using the monthly ota's I've just left it on to stop any potential accidental encryption which could theoretically lead to data loss and/or the hassle of unecrypting again. In addition to this I see absolutely no gain in speed on the video stitching process which considering it performs the task at a ~15-20 MB/s rate where the limits of the encrypted storage are 200MB/s read and 90 write for sequential reading which is what the encoder is using. Since android 5.1 when the kernel was updated to take advantage of qualcomm's encryption instructions which would otherwise go unused to the OS anyway, encryption doesn't affect this type of workload.
I know this is kinda outside the scope of this thread but I have done some reading on this kinda stuff when I was trying to learn why the app needed an external app when downloading those difference resolutions which most apps wouldn't even do outside of PC software.
Click to expand...
Click to collapse
I can't even bother to read that since (a) it is out of scope, (b) is from an end-user point of view, and (c) doesn't actually address anything related to what I've explained to you.

Wanting to switch from OP7P to Pixel 5 - some questions

Hello people,
the last OnePlus OS update disaster was the cherry on the s***cake I call OxygenOS. After years of microphone, display and sensor issues I want to go back to the only brand where I had almost 0 issues: Pixel.
Since I am still very wary I have a few questions for people who had the possibility to use the phone for a while.
1. Are there working TWRP and root methods out there? How about the backup and restore of nandroid in TWRP? Does it work flawlessly?
2. How fast ist the camera? I remember on my Pixel 2 that you could take the phone out, take a shot and put it away. The image will be sharp and clear in 95% of the cases. In other phones I had to stay still for about 1-2 seconds out of fear the image will be blurry or smeared.
3. Does Google still provide OTA .zips and tools to flash, unlock and recover custom roms and images?
4. Is the adaptive brightness on point? OP7 always needs an ever so slightly readjustmet which makes it kind of pointless.
5. Does the microphone in whatsapp voice messages work flawless?
6. Would it be possible to migrate my data partition from OP7P to Pixel 5 without issues? I have 2 authenticator apps that I have a backup for but can't restore on my OP7P without bootloop... (see intro text).
Thank you!

1. I think TWRP was just released but I don't think it's very functional. you can go to that thread to get more information since I don't use it myself.
2. This could be just me but the camera viewfinder will definitely freeze for a few seconds before I can start taking a picture. And because of the mid-range processor, it does take a few seconds for the image to process. However I think this is done after the picture is taken so you should be okay taking a picture and then turning the screen off - since it seems to process the image in the background afterwards.
3. If you do a Google search for Google factory images you'll see there are zips you can download, both full fastboot zips and OTA zips. I normally Flash the OTA zip through stock recovery via adb sideload.
4. The adaptive brightness definitely does favour going dim more than it needs to. I'm guessing this could be fixed in a potential future software update though.
5. I don't use WhatsApp so not too sure about this one
6. Not too sure what you mean exactly by migrating but I personally use the app called Swift Backup to backup and restore my apps. And then I just manually drag and drop my internal storage to my computer as a backup.

anphex said:
Hello people,
the last OnePlus OS update disaster was the cherry on the s***cake I call OxygenOS. After years of microphone, display and sensor issues I want to go back to the only brand where I had almost 0 issues: Pixel.
Since I am still very wary I have a few questions for people who had the possibility to use the phone for a while.
1. Are there working TWRP and root methods out there? How about the backup and restore of nandroid in TWRP? Does it work flawlessly?
2. How fast ist the camera? I remember on my Pixel 2 that you could take the phone out, take a shot and put it away. The image will be sharp and clear in 95% of the cases. In other phones I had to stay still for about 1-2 seconds out of fear the image will be blurry or smeared.
3. Does Google still provide OTA .zips and tools to flash, unlock and recover custom roms and images?
4. Is the adaptive brightness on point? OP7 always needs an ever so slightly readjustmet which makes it kind of pointless.
5. Does the microphone in whatsapp voice messages work flawless?
6. Would it be possible to migrate my data partition from OP7P to Pixel 5 without issues? I have 2 authenticator apps that I have a backup for but can't restore on my OP7P without bootloop... (see intro text).
Thank you!
Click to expand...
Click to collapse
Currently root works fine. There is no function TWRP yet, at least last I looked, but things are fine without it. But more volatile but once things are set up right you're golden. I moved from a OP7P to a P5, as well, so I'll give you the run down.
Biggest, biggest gripe: vibration motor. It's pretty ****ty. Not like, oh god, get this out of my hand ****ty, but the OP7P's vibrator was much, much better. Phone speaker quality is much worse, as well, but for how small the p5 is, and the fact that it has no earpiece speaker, it makes quite a decent effort. Snappines; the op7p was so fast that double pressing the power button from screen off to pull up the camera will actually unlock and relock your screen before it even registers you double clicked the power button, and apps would launch instantly. The P5 isn't quite *that* fast, but it IS nimble. Lower your expectations for snappines, though I do feel that, with the proper modifications to animations, to the kernel, to the os, it could be comparable. That's definitely something OP mastered, that snappines and responsiveness. I think what would really make a big difference in that snappines is just animation tuning. For example, I wish screen on and screen off animations just didn't exist, and instead it was instant. As it is now, currently, it's a quick fade. Small gripes though. Gravity box can solve a lot of complaints, too lol
But, the question remains, what do you gain?
You gain updates. You're now at the forefront of features. You don't know what you're missing until you have a Pixel. Battery Life? It's.. well, let's just say that the op7p sucks compared to the p5. I can easily get 9+ hours screen on time even with heavy, heavy usage, bluetooth on, location, nfc, tons of apps in the background. This phone WILL get you through the day, 100% guaranteed. You get wireless charging, too, which is awesome. Charging is nimble but not dash-charge fast. You get a phone that you can use in one hand.
Overall, will it be for everyone? No. But, I can say with confidence, I'm not looking back. I have my complaints, one of the biggest being that Google Assistant just isn't reliable for me on my p5 compared to how it was on my oneplus, and also that the ding it makes when I use the hotword is just kinda gone for some reason and I have no idea how to fix it.
But yeah, ramble over, there ya go.

Thank you for sharing your point of view!
The thing is, I got the OP7P as a gift when it released and I never got warm with its huge size. I never wanted a huge phone like this but coped with it because it was/is top of the line. But over the time those already stated minor issues started to arise and accumulate.
So basically I don't want to gain anything, I want to get rid of the surplus.
As long as doesn't have issues that bothes me every day or at least less than the OP7P, everything is fine.

anphex said:
Thank you for sharing your point of view!
The thing is, I got the OP7P as a gift when it released and I never got warm with its huge size. I never wanted a huge phone like this but coped with it because it was/is top of the line. But over the time those already stated minor issues started to arise and accumulate.
So basically I don't want to gain anything, I want to get rid of the surplus.
As long as doesn't have issues that bothes me every day or at least less than the OP7P, everything is fine.
Click to expand...
Click to collapse
You'll find it doesn't feel as premium in the hand, as well. The majority of the body is plastic, though it's a very high quality, biodegradable plastic called bio resin. It also can heat up during normal usage, but not to an uncomfortable level. Outside of usual android gripes here and there, there's really not much to complain about. It gets the job done, as a phone, really well. Camera is fantastic, and I tried to see just how quickly you can take a pic from it earlier and you likely won't be disappointed. You can snap a picture before the viewfinder even loads, so it's unlikely you'll run into any issue. It automatically enables night mode depending on the light, but you can disable that auto night mode from a button near the view finder, so that pics are taken instantly. Everything about the phone is like that - very intentional and miticulous design, while still remaining stock android. Not quite custom rom levels of customization, though. No custom OS colors, things like that. OP wins in customization, for sure, but again, you probably won't be disappointed.