Hi,is there an app or a process to calibrate the accelerometer under android?I have typhoon rom,but even in mdj s one i had problems with the accellerometer.Everything tend to go left,and so I have problems with many games and programs (most of times those programs does not have a calibration menu).Thank you for the help
Try a sense ROM. Those always have a calibration app under settings in display or something.
Sent from my HTC Glacier using XDA App
So the only way is to change rom?It s incredible that in cyanogenmod there is not a sensor calibration menu,it s really strange
No one with the same problem? So do i have to think it s an hardware problem?
Download "Bubble" by Ben Zibble from the Market, and use the Calibrate function on it.
Calibrate for each side & laying flat down too, obviously making sure the surface you are calibrating on is Flat too.
Mine was off by a bit and was awkward when playing some games, this worked great.
Gushfevah said:
Download "Bubble" by Ben Zibble from the Market, and use the Calibrate function on it.
Calibrate for each side & laying flat down too, obviously making sure the surface you are calibrating on is Flat too.
Mine was off by a bit and was awkward when playing some games, this worked great.
Click to expand...
Click to collapse
Are you sure that you can fully calibrate the phone withthis program? I tried but the calibration seems to have effect only in bubble program
I'm not totally sure. But that's one thing I would try. Do a nandroid first, calibrate, then restore your backup
Axel85 said:
So the only way is to change rom?It s incredible that in cyanogenmod there is not a sensor calibration menu,it s really strange
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
G sensor Calibration
Try the Calibrate Pitch and Roll function under GPS Status & Toolbox App [Free App under Market] , also while your at it might as well calibrate the Compass as well,
regards.
i tried to calibrate the phone with this program,but it seems to not calibrate all the phone.Is it possible to delet the files that contain the calibration data,and overwrite it with the one taken from the rom?
After searching for 2 days in any language i ve found the solution in a old xda thread.This is the only solution that work for me to recalibrate the gsensor for all the system,not only in gpsstatus or level programs.Since this thread has 450 views,i think that other peoples has my same problem.This is the thread link:
http://forum.xda-developers.com/showthread.php?t=803242
and this is the solution
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Install an app that displays sensor information along with pitch and roll. (such as SensorDebug from Android market)
Put your phone on a level surface such as the floor or a table.
Note your pitch and roll values.
Use rootexplorer or similar file manager to edit /data/misc/AK8973Prms.txt file. (open in text editor) (For ASTRO CHECK POST 70 in page 7)
You will see AOFFSET.x and AOFFSET.y at the bottom. (May be on top if you autocalibrated previously)
y affects pitch and x affects roll, there is about 4 to 1 ratio.
What you are trying to do is make pitch and roll 0 with minimum flicker.
Press and hold home button to switch between rootexplorer and sensordebug. Your changes will be reflected in realtime (with most builds). Go back and forth a few times to get perfect result. (You can press and hold home button to go back and forth) If you think changing values don't have an affect, try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting, use different sensor app and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
For example:
If pitch is 3 and roll is -1
you may start by
AOFFSET.x=4
AOFFSET.y=-12
Then adjust with 1 increments to get rid of flicker.
It is best to adjust one value at a time.
EDIT: IF YOU WANT TO CALIBRATE Z AXIS, CHECK POST 61 in page 7
Calibrated AOFFSET values for my phone are x=2 y=-9 z=12
You can use gpsstatus or bubble app (to find bubble app search the market for bz.ktk.bubble and enable "show angle" from bubble apps settings.) for visual check of orientation calibration. Because of the protruding camera lens of hd2, there can be 1 degree difference between sideways and normal orientation. (It seems you can adjust in about 0.25 degree increments by each 1 increment of AOFFSET and compansate by lowering AOFFSET=y by 2 that gives 0 degrees in both normal and sideways orientation in bubble app)
- You don't need to reboot for most builds (if there is no affect check post 11)
- You don't need to kill/restart akmd
- You don't even need to close sensor app
- Because of not perfect kernel/build support for sensors, you may see them freeze when you move the phone (TS will also freeze). With evo kernels, just wait a few seconds and it will resume. (With nexus kernels they may freeze until sleep/wakeup) Interestingly the values of AK8973Prms.txt affect shake/move freezes. I wrote about this in post 10 and 11.
IT IS A GOOD IDEA TO BACKUP COMPLETE ANDROID FOLDER BEFOREHAND just in case something goes wrong. Chefs say you shouldn't auto calibrate your g-sensor under Android because with many people it gets messed up. Also good idea to backup your /data/misc/AK8973Prms.txt
You may have trouble accessing data folder with a file manager other than rootexplorer. Your build must be rooted. (most are) It is a good idea to update your su binary inside superuser app settings TWICE. If you change permissions of /data /data/misc folders you may access them even with standart astro file manager. Try chmod 777 /data from terminal emulator.
This procedure is also possible with adb or droidexplorer. But my way of doing is practical and it is in realtime. If your build has different file name, please tell us.
This IS a development thread, please don't tell me to post in generic section or clutter.
This is manual workaround for non-working auto calibration. If auto-calibration works in the future, it may very well fix your freezes.
Values of AK8973Prms.txt file may solve touch screen/sensor freeze problems with your games. Feedbacks are always welcome. We should find out what the other values do exactly. Also check post 10 & 11
I had to try many times,but finally i ve found the right value for my device.With thyphoon rom you have to reboot after any change to take effect,so the process takes a little long...But great,now i can play asphalt 6 and use google sky map without any issue
It would be cool if someone with,programming experience,could build a program to make this process more user friendly,so we don t need to use a sense rom to calibrate the full system
I wish i helped with this post all the user with my same problem.I m sorry for my english,if it s not soo good
Related
I am on CM 4.0.2. All my apps seem to work fine, but there seems to be some slight hesitation when lifting the app drawer - just slightly choppy. I saw a lot about the fix_permissions in console, does this address that? Or is that solely for apps that are not working? I am under the impression it does NOT help this.... but wanted to be certain. Does this mean I perhaps need to adjust my SD partitions?
Should one run that code even if all of the apps appear to be working correctly?
I did not see steps for running the script in all of the posts I saw... any help on this?
This will not help. You fix permissions to possibly help with FC.
Choppiness comes from not enough memory. Check what's running in the background and adjust accordingly. Check your comcache settings, adjust. Check your swap settings, adjust. Be advised though... there's only so much you can do, we are working with very limited hardware here.
FYI... I would really look into what's running in the background first. I run cm 4.02 with default comcache, no swapper. I have 7 widgets and it only stutters occasionaly, I barely notice. I would REALLY look into your backgrouds. Also, don't forget about GPS/Wireless location issue, that may be causing it too.
Good luck
Interesting... i use advanced task killer prior to rooting and when apps were killed i was around 55MB. Now, after root i can only get around 41MB. I never understood what made this lower... i assumed it was stuff cyan added to make his rom open. I do not use many widgets (3 maybe) and generally leave wifi and gps off.
Thoughts?
I have the sprint vogue that I ran Android 1.5 from my sd card with sprint network. I updated to eclair on the sd card but find my phone says T-Mobile, don't think its a big deal.When I was running 1.5 I was able to find apps like pandora to down load, know on t-mobile network and eclair a lot of apps are missing? Is their a way to unlock the market.
You need market enabler.
http://code.google.com/p/market-enabler/
Edit: This pretty much just adds paid apps.
skipbarker said:
You need market enabler.
http://code.google.com/p/market-enabler/
Click to expand...
Click to collapse
I don't know if that will work cause he was able to download Pandora before and that's a free app, market enabler just to gives you paid apps
My bad. I misunderstood.
http://forum.xda-developers.com/showthread.php?t=628353
Read #5
It's a problem with the Android SDK.
Starting with 1.6, Google introduced screen sizes: Small, Medium, and Large. Our devices have Small Screens (along with the HTC Tattoo). The G1/Dream has a Medium screen, and the Droid/Nexus a Large screen.
The problem is the SDK defaults to Medium and Large screens. It's up to the application developer to test the application for Small screens and proactively add the indicator for Small screen support.
Most developers never bother to indicate the app can run on Small screens, so it gets excluded from your view.
I'm not sure if the small screen thing is linked to the /data or your Google user account. If I knew which, I'd figure out some way to spoof it, so we can get the full market on small screens. If it's on the /data somewhere, then that's a much easier fix.
The fact that clearing your /data and booting up a 480x320 fixes it, seems to indicate it's a value in the /data. It'd be interesting to do a dump of two /data directories with only the market resolution changed and see how they differ on a binary level. Then perhaps we can add a patch to the menu of NoMoRootfs (or a patch that's applied every bootup... or lock down the file that's modified).
If it's on the account, then either you'd have to intercept the Market App's data packet that indicates screen size and modify it proactively, or you'd have to change parts of the SDK to report the screen size as larger than it really is (this would be hard to do because apps use that interface too... you'd have to be able to detect if the request is coming from the Market App).
jnadke said:
It's a problem with the Android SDK.
Starting with 1.6, Google introduced screen sizes: Small, Medium, and Large. Our devices have Small Screens (along with the HTC Tattoo). The G1/Dream has a Medium screen, and the Droid/Nexus a Large screen.
The problem is the SDK defaults to Medium and Large screens. It's up to the application developer to test the application for Small screens and proactively add the indicator for Small screen support.
Most developers never bother to indicate the app can run on Small screens, so it gets excluded from your view.
I'm not sure if the small screen thing is linked to the /data or your Google user account. If I knew which, I'd figure out some way to spoof it, so we can get the full market on small screens. If it's on the /data somewhere, then that's a much easier fix.
The fact that clearing your /data and booting up a 480x320 fixes it, seems to indicate it's a value in the /data. It'd be interesting to do a dump of two /data directories with only the market resolution changed and see how they differ on a binary level. Then perhaps we can add a patch to the menu of NoMoRootfs (or a patch that's applied every bootup... or lock down the file that's modified).
If it's on the account, then either you'd have to intercept the Market App's data packet that indicates screen size and modify it proactively, or you'd have to change parts of the SDK to report the screen size as larger than it really is (this would be hard to do because apps use that interface too... you'd have to be able to detect if the request is coming from the Market App).
Click to expand...
Click to collapse
That is a great idea.
Do you have the capacity to perform the differential on the two directories?
I have deodexed the 1.6 Vending.apk and can post the source for everyone to review. I think the more eyes on this the better.
The only reason I run 320x480 is because I want a full market 100% of the time.
All is working, I used the link that PacyWhitter gave, followed Tatnai directions and know have full market!!!
myn said:
That is a great idea.
Do you have the capacity to perform the differential on the two directories?
I have deodexed the 1.6 Vending.apk and can post the source for everyone to review. I think the more eyes on this the better.
The only reason I run 320x480 is because I want a full market 100% of the time.
Click to expand...
Click to collapse
Yeah, I can do it, though it'd be easier to do it on two data.img files (might have to go back to WinMobile for that). Or I guess I could flash the kernel and wipe my data and export the result each time to a binary file. I'd still be interested in seeing the Vending.apk.
I already know where the Market apk is getting its info from. In android.utils there's a class called DisplayMetrics. The Market apk is likely getting its info from there. It'd be possible to spoof it by recompiling the source with a hardcoded value, but that'd affect applications as well. It'd be much harder to do it for only the Market/Vending apk.
The thing I'm interested in, is that obviously if the "boot up at one resolution, switch back" trick works, then it's not sending the resolution to the server every time. This means it has to be storing the data, or a hash of the data, somewhere.
This guy has a fascinating website on similar subjects:
http://strazzere.com/blog/
There's also a way to use the Market from the emulator:
http://www.anddev.org/viewtopic.php?p=28991
Perhaps I can start there and see if I can reproduce the problem, then produce the solution in a controlled environment.
graphic914 said:
All is working, I used the link that PacyWhitter gave, followed Tatnai directions and know have full market!!!
Click to expand...
Click to collapse
People seem to indicate it resets after a few days, so you will have to redo it until I have time to see if I can fix it.
jnadke said:
This guy has a fascinating website on similar subjects:
http://strazzere.com/blog/
Click to expand...
Click to collapse
That is one of my fav sites for Android dev. Great site .
Started Community Market Project here
heya fellas
going thru my battery history on daily basis i find those 5 culprits abusing my battery.
Gallery: uses a lot of batt due to sensor usage ( def bugged )
Dialer: what in gods name is Dialer doing to abuse the partial wake/net connection(3G) ?
0: some freaky app i guess that uses a lot of batt under net connection usage(a click on this to see any more info FC the batt history app, wow)
UID 10007: no idea what this is but its right there under 0 using net connection too
Email: i doubt its something wrong but since i have it on a 10 min refresher i dont mind it being up there since i was the one who chose a 10 min interval. but still its sucking my batt
need pics? i could post em if anyone could help.
now id love to know if anyone knows of any solution to those huge battery suckers?
what in gods name is 0 ? or UID 10007 ?
Gallery 3d sensor still bugged? im guessing my only solution here is to delete this by titanium and use another gallery app instead of the original ? any recommendations ? has anyone been down this path ?
any info is much appreciatted ^_^
anyone ?
anything ?
Sorry for late reply.
You probably already have this fixed, but for others that still get this problem the fix is to remove the original Gallery 3D app with Titanium Backup and then install the same Gallery 3D from the Android Market.
Ah yes, and for all this to work you need to Root your phone, with something like z4root.
Hope it helps!
I've looked around about the 0 think, and came to the conclusion that it's probably the process for network standby (ie staying on the network). If anyone knows otherwise/can confirm that'd be great
Yes, 0 process seems to be an internal loopback for connections. All should go trought 0. Is fine, do not care about it.
An even easier way to get the updated gallery (with better resolution photos) is to install SGS Tools (not toolbox, tools), pick 'upgrade stock apps' then 'modded 3d gallery'.
The Email battery drain bug is a known one, maybe try using k9 mail instead? Or you could try the galaxy tab app, it worked fine for me (after a little fiddling, mostly to fix the camera FC issues) but it doesn't support HTML emails, which is a bit disappointing.
Or just set the update interval to something like an hour.
The dialer thing has been bugging me too lately, i havent nailed the problem yet.
Hi,
I have recently upgraded from my 3yr old beloved HD2, the most amazing device ever to play with to Motorola Atrix HD which is THE ONLY Motorola device that is compatible with Tmobile 3G and of course 4G since it support 1700 bandwidth along with 1800 and 2100. Anyways...as I was playing with this phone like rooting, installing apps and removing ATT bloatware....I wanted to share some of the things with you all. I hope you find it useful......
-If you want your phone to be rooted....My first advice is not to upgrade this phone to Jelly Bean as it is harder to root it with JB than it is with ICS. I have used every single Android version in my good old HD2 and I can tell you this there is not any striking difference between these to versions as I have used both and using ICS was better to play with for me...what really made me mad was that my purchased Copilot live 8 app does not recognize my purchased Svox US Grace tts anymore...it did in ICS ...Again, I am not a developer, and developers may argue otherwise
-If you willfully or accidentally upgraded to JB please follow this thread(courtesy of DAN ) for rooting instructions...
http://forum.xda-developers.com/showthread.php?t=2143437
It make may not be a very simple for some of you but be patient, read all the posts and keep trying and you will succeed. This is the only option to root Atrix HD with JB and unfortunately there is no way you can rollback to ICS to get the easy root. For instructions on rooting Atrix HD ICS see here(Also THANKS to DAN )
http://forum.xda-developers.com/showthread.php?t=1940594
Without rooting you can't really do much to make your device more efficient....since all utility apps require root access!!!
Now, if you are rooted......AND you have stock ICS or JellyBean....follow my tips if you will, you will see more efficiency in terms app fluidity and power saving....
-Install System App Remover or Titanium Backup Pro to uninstall all the bloatware that are useless and just sitting on your device and memory for no apparent reason....here is hint: if you have not used an app in last 4-6 weeks, chances are you will never use it/them. You will better success with Titanium backup pro in removing them than System app remover....but be very careful what you delete if are not sure just leave it alone!!! HINT: freeze app first see the effect, be sure then uninstall
-Install Startup manager or any app that does this, to block unnecessary process or app to load up...again if you are not sure leave it alone!!!
-Install any task manager/killer and set it auto kill every 30/15mins or when device is off...closes running apps, frees memory and saves battery.
-Optional: install Rom manager or Rom tool box and fix permission if you have a lots of apps installed in your device. As the claim, this should make the apps run smoother.....No offense to the developers, I personally have not seen and practical effect of this step(it may be just in theory), not in my HD2 and not in Atrix HD...but I like to be on the safe side..it does not hurt!!!
-If you are not a heavy gamer then, install SetCpu or Antutu or something of your choice to scale down the CPU a bit...you don't really need that much speed for normal stuff and you will save a lot of battery this way.
-More battery will be saved if you configure built-in app called SmartActions to a profile that suits you. You can also install auto on/off 2G/3G/4G. I personally don't use it...as it takes long time to switch back to 3G/4G when you wake up your device and you need to use internet right away...not after 10mins..lolll
-If you are in ICS install Widgetlocker app and set it up to Easywake mode to wake your device by pressing volume key....it will save the torture on your power button any time you want to wake up device...NOTE: This App option does not work on JB....so your only substitute is to install WakeUp Screen app to wake up device by shaking instead....TIP: set up threshold to as low as possible so that you don't destroy the inner structure of your Atrix or let it slip out of your hand or smash it on the ground by shaking it too hard....you should not sacrifice your phone over the power button, right???
-Install Lux auto brightness app and adjust/lower your brightness to your choice...I personally think it is too bright in stock mode...saves battery.
WELL........I guess that's all the utility apps you need as far as I can think of and your device will be more efficient......all of these can be installed from the infamous google play....
If you use custom rom via safestrap method...many/some of these features are/may be built in or customizable within the rom...you won't need third party apps...I myself have not installed custom rom although I am flashaholic and I still have my HD2 for that...but I like to wait the custom roms to mature a bit more since I see complaints of buggy camera or sound or bluetooth etc......And since I have customized and cleaned up the stock rom via above stated apps....I don't think I will ever try or need to flash my Atrix HD since it run perfectly up to my expectation....for flashing rom matter I have my HD2 lolllll
NOTE FOR THOSE WHO WILL SCREW UP REGARDLESS: I AM NOT RESPONSIBLE AND IF YOU ARE NOT SURE. DON'T DO IT...SIMPLE!
PS: If you have any tips or tricks please join in and share!!!!
I hope you find this helpful...if you do, hit the thanks button...and if you don't...I wish there was a unthank button...xda should work on that
What do you think?
Our CPU is of 1.5 ghz, how much shud we set it at?
I set it up up at 1024...fast enough for me...see for itself you can always change it also make sure to check set at reboot option...I use antutu CPU control. You can also also use diff profile option like...at screen screen set it up around 600 or so...will save even more juice...
Sent from my Atrix HD
NYSEAN1 said:
I set it up up at 1024...fast enough for me...see for itself you can always change it also make sure to check set at reboot option...I use antutu CPU control. You can also also use diff profile option like...at screen screen set it up around 600 or so...will save even more juice...
Sent from my Atrix HD
Click to expand...
Click to collapse
Yea the good old underclocking when the screen is off i have been doing since i had my HTC Incredible saves so much battery nice tips btw.
So this is a huge discovery I made! Myself and many others are annoyed at the fact that Snapchat drops to 60Hz whenever the camera is activated. I found a workaround that allows it and other applications to remain at 120Hz even when the camera is in use! (One UI 3 only)
** BYPASS ADAPTIVE REFRESH RATE WITH CAMERA / GAMES **
(Guide 1 of 2)
For my friends over at Samsung Members looking to fix 120Hz, scroll down until you see Guide 2 of 2!!
What you'll need:
* Set Edit (free on the playstore)
Make sure you are not using power saving mode, and you have your refresh rate set to adaptive. Now launch Set Edit and enter the system table in the selector at the top right of your screen.
Look for the first line: "min_refresh_rate"
Tap that line and hit "Edit Value". Enter very specifically: 24.0
Hit "Save Changes"
Do the same exact thing for the next line: "peak_refresh_rate"
If for whatever reason these lines are missing, you can add them by scrolling all the way up and hitting "Add new setting". I'm not sure why it varies for some users..
And we're done! If you open Snapchat, Instagram, or an app that uses the camera, the refresh rate will stick to 120Hz.
I hope these instructions were clear enough!
The way I believe this works, is the adaptive refresh rate breaking because the minimum and maximum values are set to an unsupported value, thus causing the system not to be able to adjust the refresh rate.
Samsung made some changes on One UI 4, and it still does drop to 60Hz when you don't use the screen, or use Google Maps / Stock Camera. This does not occur on One UI 3.
** FIX 120HZ BUG ON ONE UI 4 **
(Guide 2 of 2)
What you'll need:
* Set Edit (free on the playstore)
Make sure you are not using power saving mode, and you have your refresh rate set to adaptive. Now launch Set Edit and enter the system table in the selector at the top right of your screen.
Look for the first line: "min_refresh_rate"
Tap that line and hit "Edit Value". Enter very specifically: 120
Hit "Save Changes"
Do the same exact thing for the next line: "peak_refresh_rate"
Set the value to: 120
If for whatever reason these lines are missing, you can add them by scrolling all the way up and hitting "Add new setting".
After you get an update that fixes the bug, it's important you change min_refresh_rate back to 48 , and peak_refresh_rate to 120 !
I created an account just to express my gratitude miss / mister !!
One known issue: Screen Brightness set to low causes it to be stuck at 60Hz regardless of the setting. Minor tradeoff at low brightness
You can use galaxy Max hz app for this too.
P-KAY 2323 said:
You can use galaxy Max hz app for this too.
Click to expand...
Click to collapse
I've used this, but it's not able to override the 60Hz cap when launching an app that uses the camera.
MochaVex said:
I've used this, but it's not able to override the 60Hz cap when launching an app that uses the camera.
Click to expand...
Click to collapse
Oh. Ok, gottha check it out then. Thanks for the guide
P-KAY 2323 said:
Oh. Ok, gottha check it out then. Thanks for the guide
Click to expand...
Click to collapse
Of course! Glad to help
MochaVex said:
So this is a huge discovery I made! Myself and many others are annoyed at the fact that Snapchat drops to 60Hz whenever the camera is activated. I found a workaround that allows it and other applications to remain at 120Hz even when the camera is in use! (excluding the stock Camera app)
What you'll need:
* Set Edit (free on the playstore)
* A computer that has ADB installed
* A charging cable.
I'll leave out the details on how to set up adb, we should know how to do this is 2021.. There are also plenty of detailed guides out there!
Make sure you are not using power saving mode, and you have your refresh rate set to adaptive. Now launch Set Edit, and grant the permission it tells you to with the adb shell command (it'll show you what to enter if you tap a line, and hit Edit Value).
After the secure settings permission is granted, enter the system table in the selector at the top right of your screen.
Look for the first line: "min_refresh_rate"
Tap that line and hit "Edit Value". Enter very specifically: 24.0
Hit "Save Changes"
Do the same exact thing for the next line: "peak_refresh_rate"
And we're done! If you open Snapchat, Instagram, or any third party app, the refresh rate will stick to 120Hz. It's unknown as to why the stock Camera still switches to 60Hz, but I don't care about that too greatly..
I hope these instructions were clear enough!
The way I believe this works, is the adaptive refresh rate breaking because the minimum and maximum values are set to an unsupported value, thus causing the system not to be able to adjust the refresh rate.
It still does drop to 60Hz when you aren't using the screen, so don't worry about that.
It's worth noting that this works on both One UI 3.0 and One UI 4 beta 2!
Works with most games and apps I've tested that previously reduce the refresh rate.
Google Maps is still stuck to 60Hz for example.
Click to expand...
Click to collapse
Not able to find min refresh rate and peak refresh rate in the system table ...
I so want to fix the 60hz lag in snapchat
aj7400 said:
Not able to find min refresh rate and peak refresh rate in the system table ...
I so want to fix the 60hz lag in snapchat
Click to expand...
Click to collapse
Try adding them as new lines. You'll see that option at the very top. Reboot after you finish. For whatever reason, not everyone has these..
MochaVex said:
Try adding them as new lines. You'll see that option at the very top. Reboot after you finish. For whatever reason, not everyone has these..
Click to expand...
Click to collapse
I dont know how to do abd .. can help?
No problem! If you go into your phone settings, scroll down and tap About Phone > Software Information > Tap the Build Number until it says Developer Options turned on.
Now go back to your settings and look for Developer Options at the bottom. Carefully scroll down and look for USB Debugging. Turn it on.
Now you'll need a laptop or computer for this next part! Go on XDA and look for a decent ADB tutorial. After adb is installed, you can plug your phone in. Open adb on the computer, and type adb devices.
You're phone should prompt you to allow that computer's signature, just tap allow.
Then you can type adb shell, and then input what the app tells you to.. If you encounter any more issues, don't hesitate to message me!
Hey ! I just found your post today... and tried it immediately on my Galaxy S21+. I searched something like that for so long!
You're an absolute genius! It's working perfectly for now, yet I'm a little surprised : it seems to work even in Google Maps and the stock camera. I didn't reboot the phone though, maybe it won't work after a reboot. It seems to work in low brightness too for the moment! By the way, SetEdit didn't ask me to do anything with adb. I just added the two lines you mentioned. Is that normal?
Thank you so much for that! I hope it'll stay like that even after a system update... we'll see!
brhb said:
Hey ! I just found your post today... and tried it immediately on my Galaxy S21+. I searched something like that for so long!
You're an absolute genius! It's working perfectly for now, yet I'm a little surprised : it seems to work even in Google Maps and the stock camera. I didn't reboot the phone though, maybe it won't work after a reboot. It seems to work in low brightness too for the moment! By the way, SetEdit didn't ask me to do anything with adb. I just added the two lines you mentioned. Is that normal?
Thank you so much for that! I hope it'll stay like that even after a system update... we'll see!
Click to expand...
Click to collapse
SetEdit (usually) asks me. Maybe it's able to edit that line without the adb permission (all I know is it asked me lol).
Glad it's working for you!!
And it should work after updating. I've updated twice in the One UI 4 beta and it still works
Yes it works even without adb ...
Wow thanks .. now i can use snapchat without a problem
aj7400 said:
Yes it works even without adb ...
Wow thanks .. now i can use snapchat without a problem
Click to expand...
Click to collapse
Ok cool! It seems to be hit or miss with needing adb so I'll leave it in the instructions. Have fun!
MochaVex said:
Ok cool! It seems to be hit or miss with needing adb so I'll leave it in the instructions. Have fun!
Click to expand...
Click to collapse
Working even after a restart.
I was wondering what would happen if min refrest rate is set to 1 and max refresh rate is set to 120 .. ( thats what the screen is capable of )
The system won't lower it any lower than 48. If you're using my custom values, it'll vary from 60 to 120 until you restore stock values.
Not sure what anyone would want to force to 120 when the smart refresh rate LTPO works very well. There's also noticeable battery savings.
You will see slightly better smoothness at the cost of battery life.... but LTPO is more than adequate where it stands now, IMHO.
Edit: I didn't see some users were having problems with apps like Snapchat. I see this might be the only temporary solution until that's fixed.
Burt Squirtz said:
Not sure what anyone would want to force to 120 when the smart refresh rate LTPO works very well. There's also noticeable battery savings.
You will see slightly better smoothness at the cost of battery life.... but LTPO is more than adequate where it stands now, IMHO.
Edit: I didn't see some users were having problems with apps like Snapchat. I see this might be the only temporary solution until that's fixed.
Click to expand...
Click to collapse
Yea I intended this fix for that very issue with Snapchat / any app that accesses the camera. Interestingly enough, it still uses adaptive refresh rate, my guide just breaks the 60Hz with camera applications restriction somehow.
Burt Squirtz said:
Not sure what anyone would want to force to 120 when the smart refresh rate LTPO works very well. There's also noticeable battery savings.
You will see slightly better smoothness at the cost of battery life.... but LTPO is more than adequate where it stands now, IMHO.
Edit: I didn't see some users were having problems with apps like Snapchat. I see this might be the only temporary solution until that's fixed.
Click to expand...
Click to collapse
For me, it didn't even impact battery life. But my S21+ (Exynos) wasn't really good to begin with, so I didn't notice any major battery drain with that "fix". And yes, it was mainly because of apps that used the camera (like Snap or even Google Messages) that I applied this workaround.
By the way, it's still working after the November security patch. Still amazed by this device after many iPhones!