okay... lets do this.
phone : galaxy s4
problem : standard default blinking cursor is too thin (cannot see it and it makes me want to put the phone in a blender)
solution : increase the cursor width by 2 - 3 pixels.
questions : Is the cursor width determined by one file, and then is it a constant regardless of application unless the application specifically decides to change it otherwise? if so : Which file generates the cursor, and, where is this file, and where in this file is the width set?
possible exceptions : themes or launchers which increase cursor width across board...
Did I look? I searched diligently through the internet even looking into how to do it at the unix and linux level and basically... I'm either retarded, or nobody else has done this. (or both)
thanks,
-s
Related
I've made an app that has a file browser on the side based of a ListFragment. I've created a custom View called IconTextView which is Basically a linear layout with a drawable for an icon and a text view for text. I also created it's adapter. I use the fragment as a file browser, the user selects a file and sends the string back to the main activity to do something with that file. For reference the class that implements the ListFragment is called FileBrowser.
This is my problem:
In the onCreate() method of FileBrowser First I add two Headers to the ListView Then I set the root directory of my application (which is a Specific Folder of the memory card) to generate the first file list.
While using the app: When the user then touches a folder I browse to it by generating the file list and setting my custom adapter again. What happens here is that the background still retains the original file list. It is obviously inactive but it is there kind of like a wallpaper and it is like the new list in front of it is transparent and the old list is the background. It works just fine, but it looks horrible. I've tried setting the original folder to multiple different folders but it is the same. Also when I scroll the file list, it goes behind the two stationary headers I mentioned.
The work around I found was to set the adapter in the OnCreate Method to null and simply press a button to show the first file list when the application is allready running. This implies that it should be a problem of simply when the setListAdapter is called for the first time. I've tried in the onResume() but the same thing happens. Even with this solution when I scroll the list of items it still goes behind the headers I mentioned just like before.
What I would like to know is if has anyone encountered this before and has found a way to solve it?
Thank you very much for all the help.
PD: The I just realized something else, the color of the headers I define is a custom color with an alpha value. Could it be that the non default alpha value creates the translucency problem?
My old phone has a 4.3" screen, 544x960; the new one is 4.75, 1080x1920. The new phone is about 15% larger, and has 4 times more pixels; but, bue I read emails, or navigate in menus (like parameters), the new phones shows 10% less text and entries (up to 20% less). Both phones have the font set to small. I have compared Android system menus (like params) and setting menu in apps (same app on both). And in every single test case, the large screen shows less than the small one.
Stupid question: is it possible to ask Android to ignore DPI, and use really small fonts so that I don't have just 4 or 5 menu entries per screen, but rather 10-15 ?
Serious questions: which environment would allow me to custom graphical settings ? which ROM ?
I use ADW; it's a good start, but it's just a Launcher. It does not help for system menus, and menus in apps.
https://play.google.com/store/apps/details?id=com.theSushi.dpichanger
Changed from 480, to 390 ... and I am wonderfully happy !!!
The app is tricky to use; think 5 times before you "go". Read carefully options in the menu.
After entering a value, before clicking go, you need to select an entry in the menu on the left of go; the menu is hardly visible; bad contrast; i will complain to author.
This is more a request/plea for help to devs than a question, but basically, I've been playing around with adjusting the DPI (using Xposed + App Settings) of my Edge for 'bout 2 days straight now and because of the way Edge Panels/Cocktailbar service interact with the rest of the UI, it's been a rather rough 2 days. To summarize my findings:
1) Changing the DPI of Android System also adjusts the width of the area allocated to the Edge. *
2) Changing the DPI of cocktailbarservice ONLY changes how various panels are stacked together. *
3) Changing the DPI of individual panels ONLY changes the total size of the panel UI but NOT the area it's allocated. *
*These are all rather confusing so the screenshots below should clear things up.
I'll be working with 6 different things here:
a) Android System
b) Cocktailbar service (com.samsung.android.app.cocktailbarservice)
c) EdgeBoard panel (com.yotsumo.edgeboard)
d) Briefing panel (com.samsung.android.app.catchme)
e) RAM Usage Manager panel (com.samsung.android.app.ramusagemanager)
f) Quick tools panel (com.samsung.android.cocktailbar.quicktool
To simplify things, I'll be changing between only two DPIs: 640 (stock) and 320. Each set of screenshots will be labeled with the letters a-f. Uppercase means it's set at 640. Lowercase means it's set at 320. Also, remember that if you want to reproduce any of these for yourself, that "Apply res to widgets" must be checked for all DPI-adjusted Edge panels.
Set 1 - ABcdef
http://imgur.com/a/BmBTw
Set 2 - AbCDEF
http://imgur.com/a/kh8Y6 (Imgur REALLY doesn't like two of the screenshots here. Just ignore them. You get the point.)
Set 3 - aBCDEF
http://imgur.com/a/74hLH
You can do a few dozen more combinations (well 61), but I the pattern should be clear now. Setting it to abcdef (all 320) does result in an non-glitchy, usable, and thinner panel, but even then, only the EdgeBoard panel (of what I've downloaded) properly adjusts to the full length. The others just leave a blank space under them.
Now what I personally think (and hopefully some of you here will agree with me) would be optimal is if we could adjust the size of the allocated panel area as well as the size of the panel itself, independent of the Android System's DPI (320 works great for me on just about everything, but the Edge panel at this point is WAY too narrow). Could this be implemented somehow either through some hacking away at internals or perhaps an elegant Xposed Module? See link for what my screen looks like currently: http://imgur.com/XpvjkMD
thanks for this post i was looking for this,i am thinking of picking up a note edge next week.i am currently using a note 3 with many modifications like darklord rom 5.0.1 ,360dpi(stock 480),v4a ,system ui mods,about 25 xposed modules etc.
so what about changing the per app dpi like just changing system ui or whatsapp messenger and others?? does it affect the side screen(edge)???i will use nova launcher and definitely not tw launcher.
i saw v4a on screenshots.so its working fine in normal mode with everything convoler??
i am curious because i will be selling my note 3 to go for the edge, so is it worth getting edge and can do all customizations or i must stick with note 4?
thanks.
Anyone else noticed for such a large display the text is overly large, see pics & YouTube clip I have the Samsung tab S 10.5 & more text is filled on the screen than the Huawei 10.8" display (even the nexus 10 shows more text) & that's with the Text size & view mode set to small because of this I would end up scrolling more. This is making me think twice about getting the tablet. The one I reviewed is my parents.
Does not help that the max home screen grid is only 6x5 where as the Samsung tab is 8x6 which is better.
in the landscape picture it mostly is because of the navigation bar you dont need wth the tab s.
I agree with it being slightly less dense than your parents tab s but I only have a old notebook as a comparison (with 1366&768 resolution) and am perfectly happy with the tablet. I suppose this could be changed with a custom rom though.
Edit: btw if it is just the browser you can adjust the scale. in firefox go to about:config and search for font.size.systemFontScale. I've got it on 70 instead of 100 and can fit a lot more content.
First of all which OS is the Tab S running. Is it the old WebView which comes as separate App, or does it already have the new WebView which is integrated into Chrome. Seems as if it is the old one on the Tab S.
Regarding the Launcher grid well yeah EMUI is different to TouchWiz, less rows and columns on the grid, but less lag fest as well. If you want to obtain more rows and columns on the grid change the launcher let's say to Nova Launcher Prime.
Sent from my HTC U11 using XDA Labs
Increase value in system - > dev options - > smallest width
Surethom said:
Anyone else noticed for such a large display the text is overly large, see pics & YouTube clip I have the Samsung tab S 10.5 & more text is filled on the screen than the Huawei 10.8" display (even the nexus 10 shows more text) & that's with the Text size & view mode set to small because of this I would end up scrolling more. This is making me think twice about getting the tablet. The one I reviewed is my parents.
Increase value in system - > dev options - > smallest width
Click to expand...
Click to collapse
BAYMAX T1 said:
Increase value in system - > dev options - > smallest width
Click to expand...
Click to collapse
I agree, I've done the same. For me, it's the non text items that are far too big. It feels like they've taken the 8.4" tablet and just scaled everything up.
I use a value of 950 - if you go smaller than that, the settings pages can become unusable. Note that this gets set on a restart, so you have to go back to Developer Options and set the value again. Still, how often do you reboot the tablet?
This is the first time I am trying: background image covers entire screen. (nice layout delivered to me)
I am placing invisible buttons over the background image to add functionality.
When in design view or layout validator things are in position I want.
However when I run the emulator or deploy to device the buttons shift further down than designed. It seems buttons/items further down the page are shifted more than those at the top (maybe a clue). Seems like a scaling issue but since new to me need a hint. I have the layout designer set to the proper device. I have starting orientation as portrait.
I tried RelativeLayout and ConstraintLayout (same behavior)
I tried placing background image as ImageView with match-parent AND also as android:background on the layout element. (same behavior)
I am fragments and using the following attributes for all buttons (relative to the layout element/the container)
app:layout_constraintStart_toStartOf="@+id/main_fragment"
app:layout_constraintTop_toTopOf="@+id/main_fragment" />
The source file for the background image is not 1024x600 so guess one can say it is being stretched to fit. (not sure if this matters)
Regardless: I need to understand why what I design is not what I get?????
All I want is a fixed screen where nothing ever moves or resizes. I have specific target device 1024x600 mdpi tablet. This seems to be the same as the generic 7" WSVGA tablet that comes in android studio. I tried that and a custom 1024x600 device. (same behavior)
The table specs are: 1024x600 pixels 160dpi (mdpi)
What am I doing wrong? Where is there a tutorial or other help related to this?
THANK YOU!