Hey guys, new to the site and the Tilt, but Ive done a lot of research without being able to get an answer to this issue with setting the background.
The only way for me to set the wallpaper the way i want it is to set it from file explorer, by holding down on the picture and setting it as the background without having to go into Pictures & Video. Doing it this way however the background comes out very faded and it does not ask you for the option of setting the transparency level. However if I do go into Pictures & Video and do it through there the wallpaper gets cut up in Landscape mode and I end up seeing 1 and a half wallpapers.
Does anyone know how to change the transparency level without having to set the background through the Pictures & Video folder???? I mean its not the end of the world but its so frustrating that the wallpaper is either Normal but Faded, or Full Color but distorted. I love the tilt but this particular problem is making me GRRRRRRRRRRGHHHHHHH
Mine doesnt become faded if I go through the way the book that came with the phone tells me to . . . . . . . .
Start----> settings----> today----> check the box that says "Use this picture as the background"
Using the browser that pops up, select the picture you want to use . . . .
i did it that way and the picture is faded but the wallpaper does not get cut up in landscape mode, how did you get it to not fade is there another option to set the today background transparency??
userdv8 said:
i did it that way and the picture is faded but the wallpaper does not get cut up in landscape mode, how did you get it to not fade is there another option to set the today background transparency??
Click to expand...
Click to collapse
easy way to make a landscape and portrait wallpaper:
Let's call base file a "tutor.jpg" (best size is 240x320 - portrait mode)
Now:
1. Copy "tutor.jpg" 3 times, so you get:
-"tutor.jpg",
-"Copy of tutor.jpg",
-"Copy 1 of tutor.jpg",
-"Copy 2 of tutor.jpg",
(or similar),
2. Open "Copy 1 of tutor.jpg" with Windows Picture viewer, and rotate it as you wish but for landscape mode.
3. Do the same with "Copy 2 of tutor.jpg",
4. Change the names of files:
- "tutor.jpg" to "stwater_240_320.gif"
- "Copy of tutor.jpg" to "tdywater_240_320.gif"
- "Copy 1 of tutor.jpg" to "stwater_320_240.gif"
- "Copy 2 of tutor.jpg" to "tdywater_320_240.gif".
5. Copy all files to /Windows directory and overwrite current one.
6. Put the phone to landscape mode, and then again to portrait - it will change all wallpapers.
Hope I'm clear with that.
Side note:
tdywater files are for today background,
stwater filer are for start menu background.
240_320 - portrait,
320_240 - landscape.
Little bit complicated, but best .
Cheers,
Chris
The best way to do this properly is to create a new theme (*.tsk) with ThemegenCE for the PC. Just do a search here or on Google and you will find it (freeware). It's a great app!
Use any image and the app will crop it accordingly for both landscape and portrait.
If this is a bit too dauting for you then use TKCreator which is a freeware app for the device itself and you can create your own themes right on your device. Images should be as close as possible to QVGA dimensions, but the app will allow some latitude for cropping.
Good luck!
MAC
I found this out by watching ZedoMax's video. Just want to repost in case people didn't see it. Sorry, root is required. Also yes I am aware of Paranoid Android, but this method work with all roms. You can set tablet mode per app that you want and not affecting the entire system. You can change font size per app as well.
Instruction:
1. Download Xposed Installer (apk) and App Settings and install both of them.
2. Run Xposed Installer and press "Install/Update". Then also select the "Modules" tab, check the box to enable "App Settings". Then reboot.
3. Run "App Settings", select any app in the list you want to change to tablet mode. Change the value for the "DPI" and resolution (Screen (dp)) to the desired value, then press "Save", then Launch the program. Keep trying different values until it successful set the app into tablet mode.
Tips:
-If you are making change to an app that contain important data, use Carbon or Titanium Backup to backup your data first, just in case.
-I find "DPI" set to 200 or 240 and "resolution" to 1280x800 tend to work. Though not all apps come with a tablet mode.
-You can change the "font scale" value to make fonts bigger or smaller as well.
-If you experienced any app crashing, toggle it off in the App Settings menu and "Save". Also, setting the "DPI" to 0 is equivalent to the default DPI value.
-Some recommended settings to try for the Nexus 7:
Browser: DPI: 200, Resolution: 1280x800
Contacts: DPI: 240, Resolution: 1280x800
Launcher: DPI: 200, Resolution: 1280x800, Font Scale: 120 (bigger icons, tablet mode)
Play Music: DPI: 160, Resolution: 1280x800, Font Scale: 140 (This will fit lots more songs on the screen.)
Play Store: DPI: 200, Resolution: 1280x800, Font Scale: 80
Handy!
Great little tip for people who don't really want to install a custom ROM.
Thanks!
cool! how does this affect performance? does it create any lag or stutter?
Edit: how do you install the zip file? it fails whenever I try to install it through recovery.
edit 2: you actually have to rename the zip file as an apk file, then install it normally in android. Not really sure why he didn't just upload it as an apk to begin with. anywho this is working great!
OrangeFlash81 said:
Great little tip for people who don't really want to install a custom ROM.
Thanks!
Click to expand...
Click to collapse
Except that after you do this, you're not on a stock ROM anymore
It doesn't affect the performance, but I can imagine running apps on higher resolution might require more performance, but I've tried it with plenty of apps.
One thing I notice is it only affect 2D graphic. The resolution setting won't affect 3D games so no chance for getting better fps.
Sent from XDA app
This is very helpful wish I knew about it before i switched to PACman ROM.
Update 30.11.2022
End of life and open source.
Due to lots of changes both in Android and in my life, I do not have the possibility to maintain / update the code any further, therefore I've decided to open source.
Code is accessible: https://github.com/borconi/obd2aa
I will like to thank all of those who supported this project.
App Requirement
Torque Pro
OBD2 Reader
Android Auto compatible headunit or at least a copy of the Headunit Reloaded App (see signature).
This app will have limited functionality if you are using Android Auto on a your phone, the only functions you will be able to use is to see are notification about the speed cameras and street card!
Gauges and torque data will NOT work!
Previous XDA purchases can be reclaimed here: https://www.b3itlabs.com/download.php
How to purchase:
Visit: https://www.b3itlabs.com/prod.php?id=2
Instructions on how to get it running:
Option 1 - Will work on any phone & car/headunit combination, however the following features won't: - AutoPlay Music, 6 Tap limit remover, DPI change
After installing the app from XDA Labs, sign up for beta testing here: https://play.google.com/apps/testing/uk.co.boconi.emil.obd2aa and update the app
Once app is updated, make sure you disable auto-update in PlayStore then please uninstall it and reinstall it from XDA Labs.
With your screen unlocked, plug in the phone to the car, when prompted which app to use make sure you select "Android Auto"
Option 2 - Might NOT work on some device combination (for sure it won't work on Xiaomi phones), but if this method works all functions of the app are available
Install
Make sure you do not have any other 3rd party app Android Auto app installed.
Open the app and hopefully it will be quite self explanatory on how to set it up (choose colours, set gauge number, etc)
Open Android Auto (on the phone), go to About, tap the "About Android Auto" header 10 times, once you are a developer from the 3 dotted right corner menu select "Start Headunit Server" (ROOT users can skip this step!)
Close Android Auto
MAKE SURE YOUR SCREEN IS UNLOCKED and connect to the car, when prompted which app to use select "OBD2AA" and always (this needs to be done one time only) - If you are a HUR user select Android Auto and always! (If you do not see the prompt to chose, please go to settings -> apps -> all apps -> Google Play Services -> Clear Defaults and then try again)
Select the last tab on the right, by pressing it again you should see an app selector and choose OBD2AA
Give it a bit of time to start pulling the data from Torque.
Change log
Version 3.2 and 3.3 released 04/11/2018
Fix "drunk" map effect on Sync 3 units
Fixed rooted devices not being able to start headunit server.
Added option to change DPI for your screen!
Added option to auto play music on start
Added option to select default start screen.
Version 3.1 releases 26/08/2018
Compatibility fix for Pie devices.
Tap limit remover now working on all device
Tap limit remover allows Maps to be searchable even when driving.
Can be used for those who have problem with the parking brake wire.
Freeze issues fixes.
Important notes
Version 3.0 releases 05/07/2018
Compatibility fix for AA 3.0 and above.
Added option for overriding 6 tap limits
Added option for Bluetooth Audio output.
Important notes
Thanks to @slash_m_a_x for the support offered on this.
- Some users have reported choppy audio when using the app, this will mainly be due to the speed of the phone, the buffer on the car/headunit and other factors which are out of my control, if that is the case and you cannot use the app please feel free to contact me for a refund.
- Bluetooth Audio output might not work on all devices, it does depend how the car/headunit handles the Bluetooth. There will be devices which completely disable A2DP/Bluetooth capabilities of the car when Android Auto is running. In this case all the sound will be heard from the phone speaker rather then the car speakers.
- Tap limit will be disabled only for cars/headunits which are equipped with a GPS.
- In rare cases it can happen that after unplugging the phone from the headunit you will see a message which says that you are still connected to Android Auto, simply Force Stop the Google Play Services.
- You always need to make sure that Headunit Server is running on the phone (unless you have root), if the icon bothers you simply hide it.
Change log
Version 2.0 releases 17/01/2018
Added new layout option
Added styled gauged
Option for custom background on each gauge.
Option for custom needle on each gauge
Removed integration for CamSam/Blitzer.de (fully integrated now)
Possibility to change needle color
Possibility to adjust arch (indent, position, length) when using custom bg
Separated speed camera settings
Option to only download speed cam db over Wifi
Fixes for min/max value
Speed camera warnings over car speaker (Thanks @martoreto for the how-to)
Street info card
Added French translation (Credit to @fbike for doing the translation)
Added Danish (Credit to @Gunde for doing the translation)
Added Finnish (Credit to @Pyrres for doing the translation)
Added Spanish (Credit to @madabase for doing the translation)
Added Italian (Credit to @ilgaspa for doing the translation)
Version 1.6a - releases 03/10/2017
Fixed negative input for min/max values
Code cleanup
Added Greek language (credit to @sosimple for translating)
Version 1.6 - releases 29/09/2017
Fixes for custom PIDS
Fixes on Graphics rendering.
Fixed overlapping text
Fixed PSI/BAR conversion
Enhanced the gauge style.
Different approach for torque data pulling.
Moved to service should start work automatically when connected to the car
Added Supports PID alarms from Torque.
Added Toggle/Collapse layout for Pid settings.
Added Preview button with random data
Added Option to toggle units display
Added notification cleanup on exit
Added translation for DE,HU,RO (Credit to @FormelLMS for DE)
Added import/export setting option
Added option for colored text
Added TPMS option/screen
Added option to override car's headlights based on day/night
Added warning screen if nothing is configured to prevent black screen with no information.
Added more settings and move them to separate Settings options.
Added customizable background
Added search for PIDs
Added Support for Heads-Up notification
Added Speed camera warnings (powered by CamSam Plus)
Supported settings/Features:
3 x Colors for each gauge
Text color
Toggle needle, arch,units,scale,decimal and text for each gauge.
Variable number or gauges ( 1 - 15 )
Set warning limit for each gauge (percentage). This will be calculated relative to the given PID max value which is retrieved from Torque at runtime.
Possibility to set gauge in reverse mode. (example fuel tank)
Units will be converted automatically based on your Preferences in Torque
TPMS Screen (if you have PID's for TPMS data)
Possibility to use custom background/needle for each gauge
Low Fuel warning
Warm Engine warning
Speed Camera Heads Up Warning
Option to Overwrite Headlights state based on calculated sunset/sunrise
How to use it?
Open app and select each PID you want to display on your screen, adjust the number or gauges you want to see adjust the preference for each PID. If you want to use custom background/needle and interested on how to, please read HERE
Locking Pid values
On some PID's Torque reports wrong min/max values, by default if while using the application a reported value is higher/lower than the initially reported range, the app will adjust the range to the new values. However in some cases this is not desired and you will like to specify manually what is the min and max value for the give PID. In this case, simple edit the minimum/maximum for the pid and they will become locked, meaning the app won't make any adjustments.
By editing, it means you have to change the min or max value, the lock is triggered by the first keypress on this input fields.
The lock will be automatically removed when you select a different PID for the same gauge.
Preferences menu
Alternative pulling - Only enable this option if you have difficulties getting gauges updated, it uses an old deprecated method of obtaining data so should not really be used.
Enable debugging - Only enable it if you have problems with the app and I requested you to collect a bug report, otherwise it will spam the logs for no reason.
Automatically start Torque on Android Auto - Nothing to explain here
Launch FartKontrol on start - launches a Danish Speed Camera app (useless outside Denmark)
Custom Background (any background you will like to use instead of the black color)
Demo - When enabled random data is generated for the PID's just to see how things will look (in case you do not have an OBD2 adapter), so don't enable it.
Pid Alarms section. You can set up a low level fuel warning (displayed as a heads up notification) and a notification when the engine is warmed up. There a several PID options for both of this, pretty self explanatory.
TPMS Settings
- You set up the 4 PID's for TPMS, this will be used to display the tyre pressure values on the TPMS screen inside Android Auto
Speed Camera
Show current street card - Displays information about current street (name and speed limit if know). This information is updated once in 5 seconds and at a minimum distance of 200 meters so it's not 100% accurate it's more for general information.
Enable speed camera warnings - This will enable the app to display speed camera warning when driving, like any app which does this it relies on a database, which means it does NOT guarantee that it will warn you of all the cameras, and it might also produce false warnings. All options are pretty self explanatory.
Export & Import
- Allows you to export your current app configuration file which can later be imported (grate way of saving time of re-doing everything) after a clean install or so. The format use for Export & Import is JSON so if you want you can manually edit/adjust the values. Please see following post for more details about the sturcture/value/meanings
Permissions
Read notification permission - Only required so the app can read the notifications from CamSam and display them on AA scren
Locations - Only required if you want the app to overwrite the day/night theme based on sunset/sunrise
Storage - Only needed if you want to use your personal image as a background and/or planning to import/export settings
Can I create my own layout for the gauges?
- Yes, see instructions below:
Here is an example of the XML structure required, once you created the XML please send it over by email to [email protected] and I will include it in the next build.
Code:
<FrameLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:tag="wrapper_layout">
<!-- Left column -->
<View
android:layout_width="226dp"
android:layout_height="226dp"
android:layout_gravity="center_vertical|start"
android:tag="gauge_2"
/>
<!-- Middle column -->
<View
android:layout_width="match_parent"
android:layout_height="match_parent"
android:layout_gravity="center"
android:tag="gauge_1" />
<!-- right column -->
<View
android:layout_width="226dp"
android:layout_height="226dp"
android:layout_gravity="center_vertical|end"
android:tag="gauge_3" />
</FrameLayout>
Important
Each view must contain a tag, which is formated like in the example, where the number corresponds to the Gauge number from the setting screen.
The layout which wraps everything together must have a tag called: wrapper_layout
You are free to use any Layout you want, except ScrollView.
How to produce bug report?
Step 1 you need to enabled debugging in OBD2AA app, then follow this instruction set:
2. Enabling Developer Mode
Open Settings > About phone.
Scroll down to the Build number.
Tap the Build number 7 times in quick succession until "You're now a developer" appears.
Return to the Settings menu and select Developer options.
At the top of the screen, make sure 'Developer options' is set to On (green).
Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
3. Capturing a Bug Report
It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
Hold the Power button down until the menu appears.
Select Take bug report. and wait for the device to capture the bug report.
Tap the 'Bug report captured' notification when it appears.
Share the bug report. (I recommend to email it to yourself.)
Download the bug report to your computer.
Send the bug report by email to [email protected]
I have decided to open up my software, meaning I have made the source code available on GitHub, but it's only available for personal use, and you are not allowed (under any form) to redistribute your own version of the app. You can download and compile it yourself if you wish to do so, and you can implement your own changes for your own personal use, but you cannot create clones of the software which you redistribute under your own name. Source can be found here: https://github.com/borconi/obd2aa.
Due to the fact that there are some irresponsible developers out there, who created video apps for moving cars, which was one of the main reasons Google blocked 3rd party apps, I won't be updating the code on github any more, to try to prevent those developers to use my technique to overcome the limits. If you are developing a 3rd party app and you will like to know more about how I have done this, you are always welcome to contact me. If your project is something useful, I will be more then happy to share things with you.
This does not mean it is now a free app and apk can be freely shared!
Amazing work Emil, this along with your (and ofcourse @mikereidis) Headunit Reloaded app is perfect for Android Auto on the cheap ,
Gotta subscribe to this thread! The possibility of custom PIDs would be of huge interest to me.
Seems like its stuck without any option to change on Kmph rather than mph for speed etc, its set to mph in torque
fma965 said:
Seems like its stuck without any option to change on Kmph rather than mph for speed etc, its set to mph in torque
Click to expand...
Click to collapse
Yeap a few things to iron out....
Just to tired to work on it tonight.... it was a long one yesterday to get the alpha done for today but planning to work on it this weekend....
Emil Borconi said:
Yeap a few things to iron out....
Just to tired to work on it tonight.... it was a long one yesterday to get the alpha done for today but planning to work on it this weekend....
Click to expand...
Click to collapse
No worries, i wrote that quickly... other than that seems good, still figuring out what my car supports though. thinking about selling my tablet setup and buying the same car thing as me
fma965 said:
No worries, i wrote that quickly... other than that seems good, still figuring out what my car supports though. thinking about selling my tablet setup and buying the same car thing as me
Click to expand...
Click to collapse
Well I love my setup but I HATE my handsfree, have to come up with some solution for that because it's cr...
Emil Borconi said:
Well I love my setup but I HATE my handsfree, have to come up with some solution for that because it's cr...
Click to expand...
Click to collapse
does it not support external microphones?
fma965 said:
does it not support external microphones?
Click to expand...
Click to collapse
No. I have to try with a USB soundcard (which I use with my Odroid) but haven't got the chance yet, or I might just hook my himbox to the AUX in and use it that way. The built in mic is almost unusable especially over 30 MPH.
And first version of the app is live!
Bought, installed and looking good.
I've got the Prius PIDs plugin installed in Torque so I can see the data on my Prius C.
Only about half those PIDs are available to be selected, it looks like it's hitting the maximum number of allowed items in the "Select PID" list.
Great, could you please tell me, where I can find it?
FormelLMS said:
Great, could you please tell me, where I can find it?
Click to expand...
Click to collapse
The XDALabs app was a pain, I had to:
Install the XDA app from the Play Store
Log in
Install the XDALabs app it prompted me to install
Log in again
Then open Emil's link from the first post in the XDALabs app.
Ok, thank you. Any chance to have this in play store?
Hi.
Sorry for the pain caused by XDA labs, unfortunately Google play rejected the app submission so I cannot make it available trough that channel.
As for custom PIDs yes intending to support them in the future. Currently torque doesn't provide a method to expose them to 3rd parties so I need to speak with Torque developer if that is possible, alternatively I will need to fallback to manual PID configuration.
I will see if I can build a quick webpage to host/sell the app could potentially make it easier to get the app, but it will make it more difficult to keep it updated.
Emil Borconi said:
Sorry for the pain caused by XDA labs, unfortunately Google play rejected the app submission so I cannot make it available trough that channel.
Click to expand...
Click to collapse
Understood, I had a feeling Google wasn't going to allow it.
One of the issues with XDA is that you can get there via the web but it's not obvious at all how to buy it from there.
Then you have to jump through hoops to get the right app.
Emil Borconi said:
As for custom PIDs yes intending to support them in the future. Currently torque doesn't provide a method to expose them to 3rd parties so I need to speak with Torque developer if that is possible, alternatively I will need to fallback to manual PID configuration.
Click to expand...
Click to collapse
It's already showing around half of the Prius custom PIDs, it's like the list just runs out of space for more items.
edit:
Screenshot link
leonkernan said:
Understood, I had a feeling Google wasn't going to allow it.
One of the issues with XDA is that you can get there via the web but it's not obvious at all how to buy it from there.
Then you have to jump through hoops to get the right app.
It's already showing around half of the Prius custom PIDs, it's like the list just runs out of space for more items.
Click to expand...
Click to collapse
I'll send you a logging version at some point this weekend just to see if how much data Torque actually send over. For example it doesn't show any of my custom PIDs for KIA.
Thanks for this, it is awesome..
A magnificent add to the current great app.
Here is photo of my test
too low ISO 320.
My Observation:
1: I added in Gauge 2 : Volts(CM), then put "13.5" in W.Level 1, and 12 in W.Level 2, when I switch to ODB2AA it wont open and switch back to the current tab.
then I changed W.Level 1 to "13" and it works, so looks like it wont accept a decimal value!, don't know if its a bug or error from my side.
2: Each time I switch to the OBD2AA tab it takes 13s for the data to be pulled.
3: Just once "no data pulling", I had to unplug/plug usb to work.
suggestion:
* It would be good if there is a timeout option for the data pulling to stop, so no 13s delay when switch back and forth in that time, I don't know if it is applicable in AA.
Great job Emil.
MAJED.y said:
A magnificent add to the current great app.
Here is photo of my test
My Observation:
1: I added in Gauge 2 : Volts(CM), then put "13.5" in W.Level 1, and 12 in W.Level 2, when I switch to ODB2AA it wont open and switch back to the current tab.
then I changed W.Level 1 to "13" and it works, so looks like it wont accept a decimal value!, don't know if its a bug or error from my side.
2: Each time I switch to the OBD2AA tab it takes 13s for the data to be pulled.
3: Just once "no data pulling", I had to unplug/plug usb to work.
suggestion:
* It would be good if there is a timeout option for the data pulling to stop, so no 13s delay when switch back and forth in that time.
Great job Emil.
Click to expand...
Click to collapse
Check your email The version you are mentioning is the Beta, the release version has all those sorted
Sorry I'm moving too fast
This isn't really a questions, more an answer. Though many questions hide here...
I like to use my Note 4's S-pen to annotate excel files (and others). The app that works best is WPS Office (formerly kingsoft). It has one really annoying "feature": when it detects that the device is a phone, it doesn't allow you to annotate using the pen. Only when the DPI is 480 or lower do you get something like tablet mode, and then the pen works.
(Maybe it has something to do with Samsung dropping Kingsoft?)
I can adjust the DPI by using the Xposed AppSettings module, and the DPI does change, but the detection of tablet/phone does not. I tried to play with various AppSettings setting, but nothing convinced WPS to allow me to use the pen.
Second option is to change DPI via system/build.prop. That works! However, now my phone has small fonts and icons. These I can adjust with AppSettings.
The last thing left is the statusbar. (I need large statusbar icons while driving/navigating, because I'd like to know if the battery is slowly increasing or slowly decreasing...)
I tried various Xposed modules to change status bar size, nothing worked.
Finally, the following worked: in AppSettings, adjust DPI for the app "System UI". That allows the statusbar to be bigger and readable (it also adjusts the Notification bar...)
A long series of problems finally solved... maybe
1. What do you use to annotate documents?
2. Any other way to convince WPS to enable the pen?
3. Is there a better way to change status bar size?
I'm on latest stock Touchwiz 6.0.1, T-mobile.
hi guys... somebody here knows correct values (if possible) of DPI so that on our NOTE 9, apps will simulate the tablet interface?
jd14771 said:
i just set my dpi to 600 and chrome and a few others changed to tablet mode. Not all apps will "change" though.
Click to expand...
Click to collapse
thanx for the reply sir.. you did not have any issues with app crashing at 600?
tried 600.... but gboard and even samsung keyboard is not usable anymore.hahaha
I have always used 576...( I use a larger font size)
The only app that caused trouble is Samsung keyboard but I use SwiftKey anyways... Swift key beta can be resized specifically to your needs...
With 576 I have never seem tablet mode
Just tested.... Default samsung won't turn to tablet mode with any dpi change...
Techvir said:
I have always used 576...( I use a larger font size)
The only app that caused trouble is Samsung keyboard but I use SwiftKey anyways... Swift key beta can be resized specifically to your needs...
With 576 I have never seem tablet mode
Just tested.... Default samsung won't turn to tablet mode with any dpi change...
Click to expand...
Click to collapse
too bad we cannot maximize the use of our screen size... really would love tablet mode....
jd14771 said:
So, usually I use 500 DPI min width because that is the lowest DPI I can set that fools Beautiful Widgets into thinking I have a tablet. That way I can use the larger tablet widget. After comparing things with a screenshot today, im using 549dp now as the keyboard fits better.
But I set my phone back to 600 again and I was able to use chrome beta, chrome, Google phone, settings, Gboard.
Please note I only have Samsung files and Samsung note left installed when it comes to Samsung's apps, the rest have been uninstalled and replaced with googles version. I got tired of using 2 app stores to keep apps updated, and Samsung apps scaled terribly.
At the 3nd I also attached a picture of what 500 DPI looks like 9n google chrome. Seems every app has its own value that transitions design from phone to tablet. I prefer the phone layout of Chrome with DUET enabled so that the menu bar is at the bottom.
Fun Fact, you can force dark more on chrome using chrome://flags on Android.
Click to expand...
Click to collapse
thanx sir for the help... nice find with the tips
at 600 dpi... gboard layout is very much different.which i think is not gud (my opinion)
thanx for the screenshots bdw ?