Which one is better overall? Basic or Natural? Does anyone have a colorimeter to measure the S22 Ultra's screen calibration on basic and natural? Basic can be enabled via adb using this command:
adb shell settings put system screen_mode_setting 2
Here is a link discussing color saturation and accuracy for the S21. This is where I got the command from. The same command works on the S22 Ultra.
https://forum.xda-developers.com/t/color-saturation-accuracy.4191115/
For best color rendering in most lighting leave it in natural mode.
For viewing in sunlight (which isn't a good idea) vivid mode will lessen the wash out effect.
https://www.reddit.com/r/samsung/comments/jlik2w
It doesn't work on my S22 Ultra Exynos model (I already used ADB mode with this phone and it worked so it's not that)... When i put your line on ADB with the choice 1 at the end of the line, i got this :
/system/bin/sh: adb: inaccessible or not found
Any idea ?
Can confirm that does work for me. I used to like the AMOLED Photo profile on my S10. It's a good balance between Vivid and Natural.
Thanks, I've got AMOLED Photo on my S22 Ultra now.
Maybe @dr. Ketan will build it inside as default in his ROM:
"AMOLED Photo" Mode - why not, when it looks best?
or at least a nice way to choose ourselves.
gregou said:
It doesn't work on my S22 Ultra Exynos model (I already used ADB mode with this phone and it worked so it's not that)... When i put your line on ADB with the choice 1 at the end of the line, i got this :
/system/bin/sh: adb: inaccessible or not found
Any idea ?
Click to expand...
Click to collapse
Are you writing the "adb shell" line on the pc ? This is a error when trying to run adb on the mobile itself, which is wrong.
||||| said:
Maybe @dr. Ketan will build it inside as default in his ROM:
"AMOLED Photo" Mode - why not, when it looks best?
or at least a nice way to choose ourselves.
Click to expand...
Click to collapse
If you have root you are the king. Then you can change the system settings database yourself very easily. No need for adb at all. Adb is needed when you don't have Root.
DaOldMan said:
Are you writing the "adb shell" line on the pc ? This is a error when trying to run adb on the mobile itself, which is wrong.
Click to expand...
Click to collapse
No i'm writing it from my PC
gregou said:
No i'm writing it from my PC
Click to expand...
Click to collapse
Show a screenshot of how it's written.
blackhawk said:
For best color rendering in most lighting leave it in natural mode.
For viewing in sunlight (which isn't a good idea) vivid mode will lessen the wash out effect.
https://www.reddit.com/r/samsung/comments/jlik2w
Click to expand...
Click to collapse
Thanks so much for this. I like AMOLED photo, a nice balance between vivid and natural.
DaOldMan said:
Show a screenshot of how it's written.
Click to expand...
Click to collapse
Here it is :
gregou said:
Here it is :
Click to expand...
Click to collapse
Can you type adb devices? Does it report back your device?
blackhawk said:
For best color rendering in most lighting leave it in natural mode.
For viewing in sunlight (which isn't a good idea) vivid mode will lessen the wash out effect.
https://www.reddit.com/r/samsung/comments/jlik2w
Click to expand...
Click to collapse
Yes, but my question was whether basic or natural was better overall? On the S21, the colors were more accurate on basic but the gamma was the same as natural.
IrrelevantUsername said:
Can you type adb devices? Does it report back your device?
Click to expand...
Click to collapse
Yes it does, i did it already.
I'm on Windows 11, maybe ADB commands doesn't works perfectly.. don't know lol
IrrelevantUsername said:
Yes, but my question was whether basic or natural was better overall? On the S21, the colors were more accurate on basic but the gamma was the same as natural.
Click to expand...
Click to collapse
Natural is pretty much spot on with my N10+.
I used a color calibration chart to check the throughput from cam to display. Vivid blows out the red channel especially.
The only way to tell if basic is better than natural is to test it but I doubt Samsung wouldn't put their best foot forward with the normal selection modes.
gregou said:
Here it is :
Click to expand...
Click to collapse
Your error is obvious. You decided for whatever weird reason to use "adb shell" as the first command and then IN THE ADB SHELL do again the "adb shell settings put system screen_mode_setting 1". This is TOTALY wrong.
You should not use "adb shell" at all. It's already included in the command line. If you enter the adb shell you are already in ADB so you can't try to use a command that starts with "adb shell" again inside to run itself .
I hope this is understandable. So connect the mobile, open cmd, go to the "c:\users\Longs\S22.....\platform-tools" directory as before. There just type "adb shell settings put system screen_mode_setting 1". You will be surprised as now it will work. Again don't type "adb shell" before using the full command at all .
If you like using adb shell by it's own then you can try typing inside "settings put system screen_mode_setting 1". This should work as well.
Cheers !
DaOldMan said:
Your error is obvious. You decided for whatever weird reason to use "adb shell" as the first command and then IN THE ADB SHELL do again the "adb shell settings put system screen_mode_setting 1". This is TOTALY wrong.
You should not use "adb shell" at all. It's already included in the command line. If you enter the adb shell you are already in ADB so you can't try to use a command that starts with "adb shell" again inside to run itself .
I hope this is understandable. So connect the mobile, open cmd, go to the "c:\users\Longs\S22.....\platform-tools" directory as before. There just type "adb shell settings put system screen_mode_setting 1". You will be surprised as now it will work. Again don't type "adb shell" before using the full command at all .
If you like using adb shell by it's own then you can try typing inside "settings put system screen_mode_setting 1". This should work as well.
Cheers !
Click to expand...
Click to collapse
Yes it worked ! thanks for the advice Dunno why i did this mistake... silly me
DaOldMan said:
Your error is obvious. You decided for whatever weird reason to use "adb shell" as the first command and then IN THE ADB SHELL do again the "adb shell settings put system screen_mode_setting 1". This is TOTALY wrong.
You should not use "adb shell" at all. It's already included in the command line. If you enter the adb shell you are already in ADB so you can't try to use a command that starts with "adb shell" again inside to run itself .
I hope this is understandable. So connect the mobile, open cmd, go to the "c:\users\Longs\S22.....\platform-tools" directory as before. There just type "adb shell settings put system screen_mode_setting 1". You will be surprised as now it will work. Again don't type "adb shell" before using the full command at all .
If you like using adb shell by it's own then you can try typing inside "settings put system screen_mode_setting 1". This should work as well.
Cheers !
Click to expand...
Click to collapse
Exacly
gregou said:
Yes it worked ! thanks for the advice Dunno why i did this mistake... silly me
Click to expand...
Click to collapse
I was sure this is your error and that's why I asked for the screenshot to be sure. I am happy it works. Have fun mate !
Related
Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App
RPK925 said:
Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.
kam333 said:
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.
Click to expand...
Click to collapse
Then you have to go to folder where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)
I
pigeonaras said:
Then you have to where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App
pigeonaras said:
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
Have you done this .....??????
RPK925 said:
I
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Before you can use adb command, you have to direct the terminal to the location of the folder where adb is located.
If the location of the file adb is at C:\\windows\androidsdktools\tools\adb
In your terminal type
cd \
Press enter, then type,
cd windows\androidsdktools\tools
Now the terminal should be in the folder where adb is located.
adb devices
A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
"On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path."
Click to expand...
Click to collapse
tmspyder said:
A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
Click to expand...
Click to collapse
This Works!
install adb driver first£¬turn your phone in ¡°charge only mode¡±£¬then find the adb floder£¬hold ¡°shift¡±and right click the floder.choose ¡°run in cmd line mode¡±£¬yeah£¬you done it
Need some help please!
I recently rooted my Xoom using the one click method and wanted to put a new kernel on but in order to do that I need ADB to work which it doesn't seem to be
I've installed the motorola drivers and my computer can see my Xoom and I can do stuff to it. But when I open a command window and enter and ADB shell, when I type 'adb devices' nothing comes up! and I can't do anything! eventhough the adb will only work when the thing is plugged in!
I've re-installed the drivers and SDK and adb stuff many times and still nothing. Also tried a few things I found on other boards but again nothing. This is reallly starting to get my nerves, please help!
In device manager what does it show? I have:
Android Phone
Android ADB Interface
its just "ADB Devices" not ADB Shell Devices
in device manager my one comes under
portable devices
MZ604
higher up there is also
ADB interface
MOT composite ADB interface
and yeah I type adb shell then adb devices and nothing comes up
ulicquel said:
in device manager my one comes under
portable devices
MZ604
higher up there is also
ADB interface
MOT composite ADB interface
and yeah I type adb shell then adb devices and nothing comes up
Click to expand...
Click to collapse
Well as you can see your device manager and mine say two different things. Mine works. Again its just "ADB devices" I do not type adb shell then devices that works for me yours doesn't seem to. So you might want to try changing to what I have posted and see if it works for you like it works on mine.
right! now I see! and it works lol Thanks alot!!!
don't know why I had to go into adb shell first, anyway one more question for you if you wouldn't mind
I want to put the recovery thing on there so where do I put the recovery.img to push it onto the xoom?
thanks again!
I put it directly in the SDK/Tools folder in other words the same folder as adb.exe
okay cool, thanks again! you're a life saver!!!
ulicquel said:
okay cool, thanks again! you're a life saver!!!
Click to expand...
Click to collapse
No problem man enjoy the rest of your Sunday. Take care..
Hello
I am trying to flash stock recovery, since then I have gotten a few problems, but not there is a new one mad. I am using this thread. Whenever I enter "adb devices"
This comes up:
emulator-5554 device
(my phones serial number) device
And that is why I can't do anything because if i try "adb reboot bootloader", it says one to many devices or emulators are running.
I would be grade full if somebody could help me.
Either remove your virtual device from the emulator or issue every adb command with the -d option if you want to target your only usb connected device and -e if you target the command at the emulator virtual device.
In your case adb reboot bootloader will become adb -d reboot bootloader
Note that this options only apply if you only have a single device of each type, if you have more of the target type (usb or emulator) you will need to identify the devices by their serial numbers using "-s <serial>" option.
Thanks for the answer But magically the emulator despaired when i was about to do it.
Won't go away
How did you get it to go away I'm trying to unlock my Nexus and I could use the -d command but I want to just get rid of this ghost AVD anyway! Thanks
thank you so much!! finally is he installing ! First I needed to install the adb drivers manually from android_winusb.. then he saw mine device in cmd.. bu then there was also that emulator.. when you sais 'adb -d......... it worked al ou on my nexus 10!! thanks mate
easy way
i did a "adb -e reboot" and the emulator never showed up again
shreyas1122 said:
i did a "adb -e reboot" and the emulator never showed up again
Click to expand...
Click to collapse
thanks.... i tried what you did and it works... :good:
shreyas1122 said:
easy way
i did a "adb -e reboot" and the emulator never showed up again
Click to expand...
Click to collapse
i know this forum is so old but i tried that and it didnt work
sawdu said:
i know this forum is so old but i tried that and it didnt work
Click to expand...
Click to collapse
It happens
Hi everyone, just trying to get ADB working with the Galaxy S2 Skyrocket, anyone want to point me in the right direction? I have android SDK but when I launch adb a command line pops up for a second and closes before I can do anything, and where can I find the ADB drivers? If you could help, that would be great, thanks!
If your using windows. Click start type in cmd hit enter
Open the directory where adb is. You can type adb start-server then press enter
Make sure you have debugging turned on in your phones settings.
So that's how you launch it! thanks, can I run it by just opening it with command line?
saying daemon started, but not doing anything, but my phone is running CWM at the moment, should I try again after?
If its running then abd is running. What are you trying to do with adb theres a ton of dfferent commands
Yea the command is going through but nothing is happening
silver03wrx said:
If its running then abd is running. What are you trying to do with adb theres a ton of dfferent commands
Click to expand...
Click to collapse
No command line is coming up, or something it just goes through
nsilverman15 said:
No command line is coming up, or something it just goes through
Click to expand...
Click to collapse
Oh I got it, use it right in command line
Hi,
I don't see my device both on 'adb' mode or in 'fastboot' mode.
What can I do to see it or put it in either of these modes?
Thanks!
-ChipX
For ADB you obviously need to enable ADB debugging from the developer settings or to be in a recovery with ADB enabled. For Fastboot you need to be in bootloader mode (fastboot).
If your device is not recognized in either of these, check your drivers/cable/USB port.
Correct.
I have ADB debugging enabled from developer settings.
My device is not being recognized now in either mode (it was earlier).
I was trying to flash a new build/AP on the phone.
fastboot erase misc
fastboot -w
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update xxx.zip
I have done this countless times on multiple phones without any issues. It doesn't work today on this device
Just before the last instruction above, after I issued 'fastboot reboot bootloader', and when I tried check whether the device has come up in 'fastboot' mode by giving 'fastboot devices', I don't see it.
I can try re-installing the USB drivers again.
ChipX8 said:
Correct.
I have ADB debugging enabled from developer settings.
My device is not being recognized now in either mode (it was earlier).
I was trying to flash a new build/AP on the phone.
fastboot erase misc
fastboot -w
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update xxx.zip
I have done this countless times on multiple phones without any issues. It doesn't work today on this device
Just before the last instruction above, after I issued 'fastboot reboot bootloader', and when I tried check whether the device has come up in 'fastboot' mode by giving 'fastboot devices', I don't see it.
I can try re-installing the USB drivers again.
Click to expand...
Click to collapse
Try updating your SDK platform-tools. They may be out of date.
I had this on my previous phone, it wasn't a big deal for me I just needed to add a ./ to each command and it would work. Hope it helps.
OzBoy1 said:
I had this on my previous phone, it wasn't a big deal for me I just needed to add a ./ to each command and it would work. Hope it helps.
Click to expand...
Click to collapse
That's why sometimes it's a better idea to run the adb/fastboot commands from CMD versus PowerShell (CMD shouldn't need "./") -- I'm assuming you're using windows as Linux & Mac OS require the ./ regardless...
I'm sure platform tools needs to be updated (for the OP), but 2 things to keep in mind is to be sure not to be using anything like "minimal adb and fastboot" and there has been reported issues on the updated platform tools (r34), so maybe there's that to consider...
Not to sound silly but have you CD'd to the Android/platform-tools directory
Have you run
adb kill-server
adb start-server
adb devices
and hit OK on the popup that shows up on your phone after start-server?
HipKat said:
Not to sound silly but have you CD'd to the Android/platform-tools directory
Have you run
adb kill-server
adb start-server
adb devices
and hit OK on the popup that shows up on your phone after start-server?
Click to expand...
Click to collapse
Kill server is usually enough. No need for start server. I'm wondering why OP is using fastbootd though.
Also, you don't need to use ./ With PowerShell if you enter "cmd" (without quotation marks of course) as your first command. After entering that, PowerShell works like command prompt.
xunholyx said:
Kill server is usually enough. No need for start server. I'm wondering why OP is using fastbootd though.
Also, you don't need to use ./ With PowerShell if you enter "cmd" (without quotation marks of course) as your first command. After entering that, PowerShell works like command prompt.
Click to expand...
Click to collapse
I can't seem to find where OP is specifically using fastbootd versus regular ol' fastboot mode...
but thanks for the tip of typing "cmd" in powershell! It's good to know! I'm always wary of using powershell and am in a lot of situation counseling other users on it, so this will come in handy versus attempting to get them to switch to cmd and/or with administrative privilages....
simplepinoi177 said:
but thanks for the tip of typing "cmd" in powershell! It's good to know! I'm always wary of using powershell and am in a lot of situation counseling other users on it, so this will come in handy versus attempting to get them to switch to cmd and/or with administrative privilages....
Click to expand...
Click to collapse
In case you didn't know, you can also just type "cmd" in the address bar of your Platform Tools folder and skip PowerShell altogether.
Lughnasadh said:
In case you didn't know, you can also just type "cmd" in the address bar of your Platform Tools folder and skip PowerShell altogether.
Click to expand...
Click to collapse
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
simplepinoi177 said:
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
Click to expand...
Click to collapse
Yeah, I've never needed admin privileges when using command prompt for any flashing I've done so it works fine for me.
simplepinoi177 said:
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
Click to expand...
Click to collapse
I do the same, run cmd as administrator. Actually, I toggle every app to run as administrator when I use Windows
HipKat said:
I do the same, run cmd as administrator. Actually, I toggle every app to run as administrator when I use Windows
Click to expand...
Click to collapse
exactly....especially when counseling & troubleshooting others through adb/fastboot related operations...
You never know what set up they have on their (Windows) system, and it's always a headache and a hassle "in the field" when you run down dozens and dozens of troubleshooting steps and it ends up having nothing to do with operations or execution but simple stuff like permissions or attributes. That's why I just like to get it "out of the way" so to speak and have it established at the onset before going down a whole road (dozens of steps taken)...
simplepinoi177 said:
exactly....especially when counseling & troubleshooting others through adb/fastboot related operations...
You never know what set up they have on their (Windows) system, and it's always a headache and a hassle "in the field" when you run down dozens and dozens of troubleshooting steps and it ends up having nothing to do with operations or execution but simple stuff like permissions or attributes. That's why I just like to get it "out of the way" so to speak and have it established at the onset before going down a whole road (dozens of steps taken)...
Click to expand...
Click to collapse
Exactly. Now if Windows stopped making me go in and retoggle Run as Administrator after every update... >: