Related
I have an i760 smartphone with a cracked screen that I want to turn into a sort time-lapse camera. The idea is to get it all set up using EveryWAN, start snapping shots and just let it run until I stop it or it runs out of battery. The result should be a continuous record of whatever event I leave it running at. It would be a cool way to record parties and events like that without having to run around with a camera in your hand all night.
I searched for a program/hack to do this and came up with a few things that will be similar (tinycam on this board) but I would like to try the continuous shot thing anyway as it has its own cool factor.
What do you guys think? Is this something that can be altered within the system files or is it set in stone with the OS? Looking forward to your thoughts!
No one has any ideas? I would think this would be a fairly simple mod though I'm not sure how this stuff works.
Bump Bump Bump It up!!!
So I've done some playing around and here's what I've come up with...
If TinyCam or VIO for windows mobile had better/ongoing support and were modified to use higher camera resolutions and effects, etc. I would use one of those in an instant. The problem is they're both limited to picture resolutions of under 200x200 and have no support for low light shots.
I played with the registry keys on the i760 but can't get any changes to take effect or remain changed.
HKEY_CURRENT_USER>Software>Samsung>Camera
I set,
PictureShotMode = 2 (multishot/continuous)
MultiCount = x (Works for 3,6,9 but nothing above the defaults)
This makes the camera start up in multishot mode but inputing values higher than 9 resets the shot count to the default 6 in the camera settings menu. So something is obviously handling this in a different way. Can camera.exe check these settings as it is launched and revert anything back to default that is out of its set range?
Anyone have any ideas on where I can go from here?
Is there any speed-governor app for the Xoom that can be configured to lock the CPU to 1000MHz whenever the soft input area is active (or better yet, whenever Graffiti input is active), and/or a way to increase the digitizer sample rate?
Historically, Graffiti has been totally unusable on my Xoom. Literally, so low of a sample rate, and so many errors, that I just couldn't use it. I finally got around to unlocking and reflashing my Xoom to CM10 last night, and locking the CPU to 1000MHz makes it work a lot better... but the accuracy is still a cruel joke compared to even my creaky, old Hero overclocked to 711MHz.
It's pretty sad, actually. On the Hero, the digitizer seems to be reporting samples at least 4-16 times as often, and I can get nearly 100% accuracy without even trying. On the Xoom locked to max speed, it seems to do a tiny bit better than my S3 gets with stock, but the sample rate still appears to be absurdly low compared to what it was on the Hero, and feedback seems to lag the actual touch by at least 100-200ms. On the Hero, feedback was literally instant... stroke, and see the pixels turn white INSTANTLY under my fingertip. On the Xoom (locked to max), they start turning white a fraction of a second after I touch the screen, and I can see the last bit of the stroke render a fraction of a second after I lift my finger away. With the stock Xoom rom, it was more like, "draw the character, and see a jagged impression of it sputter into existence about a half-second later... maybe, MAYBE even getting recognized correctly about 70% of the time".
I'm guessing that either the Xoom's digitizer has a limited sample rate, or something in the kernel or driver is limiting the sample rate... but I'm still trying to find a straight answer somewhere about whether/how you can build a custom kernel without losing your ability to run paid Market apps. Or whether it's even necessary to go to that extreme, as opposed to something like a setting that tells Android to increase the sample rate, or not throttle the CPU when an input area is active, or maybe a way to let something like SetCPU identify "soft input area active" as a profile-triggering condition. I'm also pretty sure that the Xoom's kernel (if not recent versions of Android itself) try to treat the existence of a soft input area as an excuse to massively throttle the CPU, on the theory that it's just displaying a picture of a keyboard and waiting for a blunt press. HOWEVER, I'm SURE there HAS to be an equally-official way of defeating that behavior, if only because it would also screw up Android's ability to handle east Asian input methods.
I got my Note 20 Ultra back on November and encountered an annoying issue when Adaptive refresh rate is turned on and watching YouTube videos. When YouTube first starts the display will run at 120hz, but after a few seconds it will drop to 60hz. When the refresh rate drops, the first touch of the screen is interpreted as a touch and hold instead of a single press. The display will then jump back to 120hz, but the display still thinks I'm pressing and holding the screen when I've already let go. If I then touch the screen again while in 120hz the phone thinks I've done a double tap (presumable completing the first tap and then immediately registering the second tap), which causes the video to seek forward or backward, depending on where I pressed on the screen the second time. If I tap the screen the one time but allow the screen to drop back to 60hz after it jumps to 120hz from the first tap, then the first tap seems to be ignored as my second tap acts like a tap and hold again.
What's interesting is that as long as the display stays at 120hz, all taps after the scenario above work fine. A single tap will open the playback overlay (pause/play button, seek arrows, etc) like it's supposed to, but once I leave the display alone and it drops to 60hz this whole problem starts all over again. Since adaptive refresh is tied to the brightness sensor, this problem does not present itself in a dark room since the display stays at 120hz in a dark room. Also, if I turn off adaptive refresh rate and have the display stay at 60hz all the time then the problem is not present either. I also will occasionally get non responsiveness on Brave Browser but I can't say for sure if they are related.
This has frustrated me so much I did a factory reset and interestingly the issue did not re-appear at first with a fully updated YouTube. Once I updated/installed other apps (including Galaxy store apps) the problem returned. I don't have display overlay apps installed, so I suspect it's a Galaxy store app but I can't pinpoint which one. I don't believe this is a hardware issue, so I'm curious if anyone on the thread has had a similar issue. I'd like to report this to Samsung but I have no idea where to even report this.
Sounds like you've figured it's a software program. You should update one at a time and see if you can pinpoint the issue. Try to not to install 3rd party software until all you need to update gets updated and phone is working fine.
Or
I would say try using a package disabler and try disabling the apps you suspect to see if any improvements. It might not be a Samsung app as others would be facing the same issue you're having.
As always don't restore settings/app data from backup etc other than media, messages, logs.
I'm using adaptive and everything is working fine on my end. Snapdragon variant here. Albeit I keep a number of Samsung apps disabled as i don't use or need them running in background for no reason.
lennie said:
Sounds like you've figured it's a software program. You should update one at a time and see if you can pinpoint the issue. Try to not to install 3rd party software until all you need to update gets updated and phone is working fine.
Or
I would say try using a package disabler and try disabling the apps you suspect to see if any improvements. It might not be a Samsung app as others would be facing the same issue you're having.
As always don't restore settings/app data from backup etc other than media, messages, logs.
I'm using adaptive and everything is working fine on my end. Snapdragon variant here. Albeit I keep a number of Samsung apps disabled as i don't use or need them running in background for no reason.
Click to expand...
Click to collapse
Can you provide a list of apps which you have disabled through adb?
have you tried diff version of youtube that can help
RISHI RAJ said:
Can you provide a list of apps which you have disabled through adb?
Click to expand...
Click to collapse
I use package disabler pro bought from their website. It gives me a great on demand enable/disable option.
My use case might be a bit different from yours as I have about 160 packages disabled at a given time. I guess I can provide a list and you chose what you want from it.
I'll try uninstalling apps again to see if the problem can be resolved that way. On the latest version of Youtube it worked fine before I started installing more apps. I kind of don't want to do a full factory reset but if I have to so I can narrow that my be my only option. I'm wondering if there is another software I can run on my phone to see if any apps are interfering with the display or adaptive refresh rate?
I ended up doing a factory reset on my phone. The issue went away for the most of the day but returned again by night time. Same issue - when at 120hz and drops to 60hz the issue is present. It's not just Youtube, it's on any app, including the home screen. The first tap is always interpreted as a tap and hold, so single tapping an app icon brings up the tap and hold menu, and single tapping on the home screen brings up the home screen customization screen. Another test I did was turn off auto brightness, then turn my brightness down to the lowest setting. After that the display stayed at 120hz and the issue did not return until I either set the brightness up manually or turn auto brightness back on. I also tried in safe mode, and the issue was not present there either, but I can't tell if the device every went into 120hz or not since all 3rd party apps are disabled. At this point I have no idea what it is. The app setup was fine during the day, no new apps were installed, but the issue returned. Seems like I have no choice to but turn adaptive smoothness off and leave it at 60hz.
Just to add a little more interesting information here. I had someone else use the refresh rate monitor app on their Note 20 ultra (Tmobile variant), and their display operates differently than my Verizon variant. On the Tmo variant, when the screen drops to 60hz and the screen is tapped, the refresh rate drops to below 60 (12, 34, 48, etc) but then goes back up to 120hz after the app opens. Mine just goes immediately to 120hz and then gets that tap-and-hold behavior. So clearly the screens software or firmware is behaving differently here. I'm wondering if we have any other Verizon variant Note 20 Ultra users on this forum that could also test?
Hi,
anyone noticing lag in the rotation animation? Most of the time the first time is pretty smooth. When changing rotation a few times thereafter the animations look more like 60 fps (although 120 is activated). Tried it in different apps. Always the same and really annoying and ugly.
Can anybody confirm this?
This issue goes way back. Even my 10+ does it.
Might have to do with the sensor refresh rate and/or degree of tilt/time at tilt/yaw.
If it takes more then a second there's definitely a fault issue.
Mmh. Actually I didn't recognize this when using my S20 with 120hz. At least not that much. So there's nothing that can improve the experience? I even thought the phone didn't have this behavior from the start which led to the question if I have something fishy installed. But there's nothing out of the ordinary. It's the same when using stock launcher or Ruthless launcher.
Be interested if there was a way to make it more responsive. This aspect of the device's behavior is slow by comparison to it's otherwise snappy performance. It is irritating... I hate waiting.
It's about .5-1 second on the N10+ in Brave browser and elsewhere.
I'm going to go through accessibility settings again. It's likely a user hidden setting though.
Have y'all dug into Developer Options & set the animation speeds to 0.5 (or 0)?
It might help some, if you haven't already done so. However, I've experienced it as well on occasion,getting "stuck", if you will.
KOLIOSIS said:
Have y'all dug into Developer Options & set the animation speeds to 0.5 (or 0)?
It might help some, if you haven't already done so. However, I've experienced it as well on occasion,getting "stuck", if you will.
Click to expand...
Click to collapse
Yeap, no joy
KOLIOSIS said:
Have y'all dug into Developer Options & set the animation speeds to 0.5 (or 0)?
It might help some, if you haven't already done so. However, I've experienced it as well on occasion,getting "stuck", if you will.
Click to expand...
Click to collapse
For me the problem is that it looks sluggish as if the phone struggles to display the 120 Hz. Setting the transition scale to 0.5 or 0 doesn't do it for me. Makes it even more unsatisfying.
Cris7ianO said:
For me the problem is that it looks sluggish as if the phone struggles to display the 120 Hz. Setting the transition scale to 0.5 or 0 doesn't do it for me. Makes it even more unsatisfying.
Click to expand...
Click to collapse
It has nothing to do with your refresh rate or does it? It so there may be some hope.
Like I said though both my N10+'s behave this way, it's normal... and irritating.
blackhawk said:
It has nothing to do with your refresh rate or does it? It so there may be some hope.
Like I said though both my N10+'s behave this way, it's normal... and irritating.
Click to expand...
Click to collapse
Honestly it looks like the phone is struggling to keep it on 120hz when rotating. When I choose 60hz and rotate the phone it looks the same way constantly. That's why I'm thinking it has something to do with the frame rate. So in my case it's not about a delay for the animation it's about the smoothness.
Cris7ianO said:
Honestly it looks like the phone is struggling to keep it on 120hz when rotating. When I choose 60hz and rotate the phone it looks the same way constantly. That's why I'm thinking it has something to do with the frame rate. So in my case it's not about a delay for the animation it's about the smoothness.
Click to expand...
Click to collapse
What I'm talking about is how long it takes to flip the screen to landscape once the phone's flipped. Close to 1 second.
I always disable all animations as it wastes resources plus I like the snap.
Lol, if it needs animations, it's too slow.
Cris7ianO said:
Hi,
anyone noticing lag in the rotation animation? Most of the time the first time is pretty smooth. When changing rotation a few times thereafter the animations look more like 60 fps (although 120 is activated). Tried it in different apps. Always the same and really annoying and ugly.
Can anybody confirm this?
Click to expand...
Click to collapse
Sounds like something might be bogging it down.
I have the obligatory delay when rotating (because you have a ton of redraws happening on top of the actual animation itself, not some accessibility setting), but it is minimal. That aside, the rotation is smooth with animation set to 0.5 and adaptive motion smoothness.
The difference between your previous S20, my previous Note 20, and the Z Flip 3 is the lost RAM. This is an 8GB device, compared to 12GB or 16GB from last year. After some time getting used to being able to launch a bunch of stuff, it is easy to forget that this one can't run quite as much at once.
The only sure way to stop that completely without having to keep tabs on how much is running would be Developer options -> Don't keep activities or setting Background process limit, both of which come with some downsides.
If it is happening with a single app running after multiple turns, that could indicate an issue with the GPU. It could be as simple as poor cache handling that will be resolved with an update or a clean start. It could also be a hardware issue.
twistedumbrella said:
Sounds like something might be bogging it down.
I have the obligatory delay when rotating (because you have a ton of redraws happening on top of the actual animation itself, not some accessibility setting), but it is minimal. That aside, the rotation is smooth with animation set to 0.5 and adaptive motion smoothness.
The difference between your previous S20, my previous Note 20, and the Z Flip 3 is the lost RAM. This is an 8GB device, compared to 12GB or 16GB from last year. After some time getting used to being able to launch a bunch of stuff, it is easy to forget that this one can't run quite as much at once.
The only sure way to stop that completely without having to keep tabs on how much is running would be Developer options -> Don't keep activities or setting Background process limit, both of which come with some downsides.
If it is happening with a single app running after multiple turns, that could indicate an issue with the GPU. It could be as simple as poor cache handling that will be resolved with an update or a clean start. It could also be a hardware issue.
Click to expand...
Click to collapse
This sounds like a reasonable explanation to me. The S20 with 12 GB indeed hadn't any of those issues, at least not to that extent. In addition I don't have that issue permanently. It only occurs from time to time. Haven't got an update since release. Hopefully it gets an improvement in the near future as it is disturbing. Nevertheless it is a joke that something like that happens even with 8 GB of RAM.
Cris7ianO said:
This sounds like a reasonable explanation to me. The S20 with 12 GB indeed hadn't any of those issues, at least not to that extent. In addition I don't have that issue permanently. It only occurs from time to time. Haven't got an update since release. Hopefully it gets an improvement in the near future as it is disturbing. Nevertheless it is a joke that something like that happens even with 8 GB of RAM.
Click to expand...
Click to collapse
Do you use split screen apps? The only time i've really come across the issue was trying to run both a game and the browser with a couple other apps still in the background.
I think an update will definitely help, though. It seems like the 8GB on this is a larger step down than it should be right now and it is supposed to be a much better GPU.
twistedumbrella said:
Do you use split screen apps? The only time i've really come across the issue was trying to run both a game and the browser with a couple other apps still in the background.
I think an update will definitely help, though. It seems like the 8GB on this is a larger step down than it should be right now and it is supposed to be a much better GPU.
Click to expand...
Click to collapse
No, I don't really use split screen apps. Hopefully an update will help. The device definitely has some obvious tradeoffs but in general it feels fresh and I really like it.
Just an update from my side: Indeed my inner feeling wasn't wrong. I just encountered the sluggish rotation again. Thereafter I went to developer settings and enabled show refresh rate. I went back and tried rotation again. The first time all is fine and it shows 120, but the times thereafter it jumped to 60 Hz when rotating. And if course my eyes will notice this behavior as they are used to 120. Hopefully this will get fixed. This has to be software related.
So this behavior is due to the adaptive refresh rate. It's there a way to force 120 all the time?
Cris7ianO said:
Just an update from my side: Indeed my inner feeling wasn't wrong. I just encountered the sluggish rotation again. Thereafter I went to developer settings and enabled show refresh rate. I went back and tried rotation again. The first time all is fine and it shows 120, but the times thereafter it jumped to 60 Hz when rotating. And if course my eyes will notice this behavior as they are used to 120. Hopefully this will get fixed. This has to be software related.
So this behavior is due to the adaptive refresh rate. It's there a way to force 120 all the time?
Click to expand...
Click to collapse
[App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)
About this app: Refresh Rate Control: Easily control the max refresh rate (Hz) of android devices with multiple refresh rates (e.g. note20 ultra, s20/S20+/S20Ultra, z fold 2, s21/s21+/s21Ultra, tab S7/S7+, z fold 3, z flip 3). This app can limit...
forum.xda-developers.com
Pretty sure that would be able to handle it for you.
twistedumbrella said:
[App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)
About this app: Refresh Rate Control: Easily control the max refresh rate (Hz) of android devices with multiple refresh rates (e.g. note20 ultra, s20/S20+/S20Ultra, z fold 2, s21/s21+/s21Ultra, tab S7/S7+, z fold 3, z flip 3). This app can limit...
forum.xda-developers.com
Pretty sure that would be able to handle it for you.
Click to expand...
Click to collapse
I tried this app and I am not fully satisfied with the outcome. Of course forcing 120hz will train the small battery even more and I don't want to be dependant on a 3rd party solution. Just to confirm the behavior is not only on my end, can you please test the following on your device?
1. Go to developer options and enable show refresh rate
2. Go in following apps: e.g. Whatsapp, Facebook, Google Play, Samsung Internet, Amazon Shopping (cause I don't face this issue on all apps)
3. In each app wait a few seconds four the refresh rate to go down to 60 and then rotate the screen (In my case the refresh rate stays at 60 when rotating in the mentioned apps and this looks horrible when the rest is running on 120hz)
If you could borrow a few minutes of your time to check that would be awesome and is very appreciated Thanks in advance!
Update: Just to be sure I did a factory reset. Still no improvement...
Further investigation gave me more information. There is something weird going on. When display brightness is low (around 10-15%) there is no issue for the phone keeping 120 while rotating. When I go up in brightness the 60hz rotation is back again. This is horrible. I've had a look on the new iPhone 13 pro and Apple doesn't have these issues with their adaptive screen. As I had the S20 before and skipped the s21 with the adaptive one this Flip is my first Samsung device with an adaptive screen. The experience is horrible. I just want a compact android device without such a compromise. This is ridiculous.
I just noticed that my Pixel 4 XL (currently has the newest Android 12/November patch) does not cycle between 60 and 90 hz anymore. I just noticed an unexpectated and new drain on the battery and finally found the culprit.
Yes, I checked developer options, the phone is NOT forcing 90hz. I checked with developer options (show refresh rate) and the phone is constantly, meaning 100% using 90hz, it never changes to 60. No matter what I do - Youtube, phone, scrolling, doing nothing, idling, homescreen, newspaper app, Audible - it matters not. It is constantly forcing 90hz WITHOUT having ever clicked the 90hz force toggle. This is putting a drain on the battery that is just unacceptable.
Can you guys confirm this?
Try clearing the system cache.
A factory reset maybe be needed after a major OTA firmware upgrade but there's no guarantee it will resolve it.
Updates tend to break things...
blackhawk said:
Try clearing the system cache.
A factory reset maybe be needed after a major OTA firmware upgrade but there's no guarantee it will resolve it.
Updates tend to break things...
Click to expand...
Click to collapse
The phone was - actually - already factor reset. After doing the Android 12 update, I factory reset it and gave it to a family member, that one set it up new. So it's not a "remnant" of Android 11.
Morgrain said:
The phone was - actually - already factor reset. After doing the Android 12 update, I factory reset it and gave it to a family member, that one set it up new. So it's not a "remnant" of Android 11.
Click to expand...
Click to collapse
I would re-flash with the latest full image, leaving the script intact (allowing the data partition to be wiped). This may be inconvenient but it's the only way you will know if there is a hardware issue with the phone. I'd also like to know what led you to the refresh rate. In other words, what made you look there. The stock battery monitor is not very good and even looking at system apps (screen, ambient display) you only get time and a percentage of the battery.
is the same on 12 and 11, i just installed 11 and is always 90hz
yes i can confirm, i had the same issue and i just boght my pixel 4 xl 10 days ago. updated to android 13 beta now and it still has the same problem. really weird but i think that google just decided that its best for google pixel 4 owners to have 90hz all the time now cause u know its "more common" now
Google changed how Smooth display works during the cycle of the phone. IIRC it was the same on A11 too. Basically the only time it goes 60hz is during battery saving mode & in some specific apps that prohibit it. It also disables it when HBM is on.
That doesn't make a lot of sense, you can save much more energy by just raising to 90hz for touch and animations and otherwise reduce to 60hz independently of the battery state.
I had the pixel 7 Pro for a while and can confirm that it works there as expected (60 for static content & no touch events, otherwise raises up to 120hz), just not for the pixel 4 XL.
This does seem like a bug to me and explains why battery life (SOT) got so much worse. I wonder if it's an intended degradation to get people to upgrade..
Fix it with adb, set minimal refresh rate
adb shell settings put system min_refresh_rate 1.0
adb shell settings put system peak_refresh_rate 90.0
Tested that, does not work either unfortunately. Display stays on 90Hz all the time
onemandivision said:
Tested that, does not work either unfortunately. Display stays on 90Hz all the time
Click to expand...
Click to collapse
Confirm you have extra dim disabled, and brightness 60%
Confirmed, does not make a difference
Out of nowhere it started working. The only thing I changed in between is brightness and extra dim, ending up with the same setting as before (full brightness, extra dim disabled). Didn't work straight away, but after leaving the phone for 5 minutes and picking it up again, I immediately noticed (display refresh rate setting was still enabled)
Thank you for your help, Hamid!
onemandivision said:
Out of nowhere it started working. The only thing I changed in between is brightness and extra dim, ending up with the same setting as before (full brightness, extra dim disabled). Didn't work straight away, but after leaving the phone for 5 minutes and picking it up again, I immediately noticed (display refresh rate setting was still enabled)
Thank you for your help, Hamid!
Click to expand...
Click to collapse
No problem, glad i helped!
Feel free to visit my optimization threads, it might help improve your battery life and performance.
One last remark: It didn't really work well at first, at least not as consistently as on the pixel 7 that I've tried. After some trial and error, playing around with various settings, the culprit seems to have the "increase touchscreen sensitivity" setting that I had enabled. Since turning it off, the switching between 60 and 90Hz is much better. Brightness and extra dim don't seem to play a role.
Battery life also seems to have improved a lot (now at ~50% at the end of the day compared to <20% before)