Pretty simple question; how do I change the screen density on an AMOLED Dinc w/CM7? I used to do it all the time on my D1 through build.prop but it doesn't affect it so I tried some apps which caused some boot loops so I'm in need of direction.
poontab said:
Pretty simple question; how do I change the screen density on an AMOLED Dinc w/CM7? I used to do it all the time on my D1 through build.prop but it doesn't affect it so I tried some apps which caused some boot loops so I'm in need of direction.
Click to expand...
Click to collapse
https://market.android.com/details?id=lv.n3o.lcddensity&feature=search_result
Have you tried that? I use it and have never had any issues with it. It resets itself after a reboot, too, so it's (relatively) safe to play around with.
Thanks for the reply but yeah I've tried it. Are you AMOLED or SLCD?
poontab said:
Thanks for the reply but yeah I've tried it. Are you AMOLED or SLCD?
Click to expand...
Click to collapse
AMOLED. I got mine right before they switched screens. I'm guessing you have an SLCD and that's why it doesn't work?
Are you running a Sense or AOSP rom? I don't see why it wouldn't work on Sense, but I've only ever tried it on CM6 and 7.
Related
I'm sure this is a stupid thing to miss, but when im not looking completly at the keyboad the second vibrate to let me know to release for a number is nice. This works on my AMOLED but NOT my SLCD version. Running CM7 it does work on the SLCD version. THey are running the same software when stock and I can't see to find a setting where this would be turned off on the SLCD version.
I still haven't been able to figure this out. I know it's a stupid little thing, but a feature I miss.
Are you using the stock keyboard?
i8qbert said:
Are you using the stock keyboard?
Click to expand...
Click to collapse
Yes, everything is stock. This SLCD version doesn't vibrate on long press on the keyboard and my AMOLED did.
You are correct! I guess i never noticed. I use better keyboard 8, which IMO is far superior. Still no second vibrate though.
i8qbert said:
You are correct! I guess i never noticed. I use better keyboard 8, which IMO is far superior. Still no second vibrate though.
Click to expand...
Click to collapse
I don't understand how the AMOLED had it there a software difference?
ANyone Anyone?
I wiped EVERYTHING and reflashed the ROM. It seemed to have work, but then I was at the default density. Once I used LCD Density to 220, the error happened again. It forces closes. Any help? CM7.1
mapheG2 said:
I wiped EVERYTHING and reflashed the ROM. It seemed to have work, but then I was at the default density. Once I used LCD Density to 220, the error happened again. It forces closes. Any help? CM7.1
Click to expand...
Click to collapse
It's my understanding that altering the density can breaks things, including applications... looks like you'll have to choose between your desired screen density or Wifi Calling app.
This sucks
not sure why you want to change this, on any LCD display the native resolution (and therefore LCD density) whether on a phone, computer, tablet or whatever, is always the clearest, sharpest and best looking!
The icons and text are just too big to my liking after trying LCD density. At 220, as opposed to 240, everything just looks nicer and there isn't noticeably a decrease in sharpness or clarity.
Open spare parts, enable compatibility mode, reboot. See if that fixes it.
^ Nope, I tried that before. That doesn't help. Thanks for the suggestion though!
mapheG2 said:
^ Nope, I tried that before. That doesn't help. Thanks for the suggestion though!
Click to expand...
Click to collapse
Show me a logcat!
i just wonder is it possible to someone make this
http://forum.xda-developers.com/showthread.php?t=1717079
Nope.
The reason: You need to input the highest DPI which will give you tablet mode, which is gotten by lowering the DPI.
You cannot lower our phone's DPI to that point.
And I really thing tablet apps on a 3.2" screen would just not work properly.
Succesfully got it booting (However i haven't followed that guide)
I'm testing it now.. I will share it if I don't find lots of bugs
elia222 said:
Succesfully got it booting (However i haven't followed that guide)
I'm testing it now.. I will share it if I don't find lots of bugs
Click to expand...
Click to collapse
How do tablet mode apps look?
Lesicnik1 said:
How do tablet mode apps look?
Click to expand...
Click to collapse
Everything seems to work fine, except some dpi changes in framework-res (they cause bootloop, probably something is set wrong in pad.prop), SU works but sometimes keeps asking for su permissions.
I've attached a screenshot for you. It's not that bad, but with a larger screen would be a lot better
Edit: In the next days I will try to fix few things, then I will release it.. Maybe it doesn't have much sense to have tablet UI on a ldpi 3.2 inch screen, but that's why I ported it
elia222 said:
Everything seems to work fine, except some dpi changes in framework-res (they cause bootloop, probably something is set wrong in pad.prop), SU works but sometimes keeps asking for su permissions.
I've attached a screenshot for you. It's not that bad, but with a larger screen would be a lot better
Edit: In the next days I will try to fix few things, then I will release it.. Maybe it doesn't have much sense to have tablet UI on a ldpi 3.2 inch screen, but that's why I ported it
Click to expand...
Click to collapse
I'm surprised!
I thought it would be a ton more squished than it really is!
Lesicnik1 said:
I'm surprised!
I thought it would be a ton more squished than it really is!
Click to expand...
Click to collapse
hehehe we could get a tablet smaller than kindle, note and nexus 7 - this might really confuse the Apple devs
Swyped from my HTC Wildfire (Buzz)
that's a good news, it would be great if you fix those problems, but take your time mate
i got a tablet mode Gmail and it's great, works like charm on Willy
rajko666 said:
that's a good news, it would be great if you fix those problems, but take your time mate
i got a tablet mode Gmail and it's great, works like charm on Willy
Click to expand...
Click to collapse
I will work on the rom on saturday and sunday, this week I've a lot to study for university :silly:
elia222 said:
I will work on the rom on saturday and sunday, this week I've a lot to study for university :silly:
Click to expand...
Click to collapse
good luck with studyng
I finally got my new OP3 but I've noticed some color shifting when tilting the phone. Is this normal? Also I need help with something else. I want to completely remove lockscreen wallpaper on oxygen OS, so that it shows my home screen wallpaper. I'm rooted and I've tried deleting the keyguard wallpaper files, but all it does is show me a black screen unlike on the OP2. Can someone help?
1) there is no colour shifting on my op3, do you have a tempered screen guard on your phone?
2) when on oxygen os launcher long press on empty area of your home screen and select the lock screen wallpaper from there. its annoying that everytime you have to switch to oneplus launcher to change lockscreen wallpaper.
Isn't it possible to straight up get rid of it? I remember doing it on the OP2. By uninstalling the keyguard wallpaper file in system/users. But it keeps coming back after a black screen... And about the color balance, it only appears if I tilt my phone, which I read is a common problem with AMOLED screens all over. Can you confirm?
skyknife93 said:
Isn't it possible to straight up get rid of it? I remember doing it on the OP2
Click to expand...
Click to collapse
The only way is to set the same wallpapers for homescreen and lockscreen, there is no way to get rid of the wallpaper so you'll have to do it manually.
Sent from my OnePlus3 using XDA Labs
I've updated my reply a bit bro. And one final thing, I've noticed a slight lag after rooting it, is that normal too?
skyknife93 said:
I've updated my reply a bit bro. And one final thing, I've noticed a slight lag after rooting it, is that normal too?
Click to expand...
Click to collapse
I'm not seeing any colour issue when i tilt my phone also i dont have any lag on my phone. I'm on stock rom and kernel. I clean flashed the signed rom via twrp and flashed supersu after it. I didnt go through the initial setup process.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
I'm not seeing any colour issue when i tilt my phone also i dont have any lag on my phone. I'm on stock rom and kernel. I clean flashed the signed rom via twrp and flashed supersu after it. I didnt go through the initial setup process.
Click to expand...
Click to collapse
Ok. I'll give that a try and report back... Thanks for you prompt response. Do you suggest I request a replacement if the issue persists?
skyknife93 said:
Ok. I'll give that a try and report back... Thanks for you prompt response. Do you suggest I request a replacement if the issue persists?
Click to expand...
Click to collapse
your device is under warranty so ya you should definitely ask for a replacement.
bonham1988 said:
your device is under warranty so ya you should definitely ask for a replacement.
Click to expand...
Click to collapse
Ok... Thanks... I'm still downloading the zip, and it's quite late here. So I'll update on the prob tomorrow...
I seem to be having an issue when using the QHD+ (doesn't occur while on FHD) option across all roms, rooted and stock. The boot animation glitches right before it's finished and was wondering if anyone had the same experience? I've done a little bit of research on desc.txt, but haven't found anything to remedy it. I've tried changing the fps and resolution within desc.txt. Also tried various custom boot animations to no avail.
I know it's a small thing, but wondering if anyone had a solution to this (besides switching to FHD)?
Android version? Phone model?
TheGhost1951 said:
Android version? Phone model?
Click to expand...
Click to collapse
Sorry currently on A13, WatchDogs custom ROM, LE2125 unlocked
First line of desc.tx should look like this for the bootanimations.zip.......
g w h 0 0 30
W=width in pixels
H=height in pixels
I believe the 0 0 is the x,y coordinates for animation reference position
g I believe is for global
30 is the frames per second
The first line changed with A12+
Should be the same for A13 maybe
TheGhost1951 said:
First line of desc.tx should look like this for the bootanimations.zip.......
g w h 0 0 30
W=width in pixels
H=height in pixels
I believe the 0 0 is the x,y coordinates for animation reference position
g I believe is for global
30 is the frames per second
The first line changed with A12+
Should be the same for A13 maybe
Click to expand...
Click to collapse
Thanks for that, man. Do you know if the FPS matters? Or is it just a visual thing. Also, is it the width and height of the image, or the screen resolution? Will test some things when I get home
kodayoda713 said:
Thanks for that, man. Do you know if the FPS matters? Or is it just a visual thing. Also, is it the width and height of the image, or the screen resolution? Will test some things when I get home
Click to expand...
Click to collapse
You want the w and h to correlate to the screen size for optimal clarity. Fps determines how fast or slow it plays...and it determines how long it will play
TheGhost1951 said:
You want the w and h to correlate to the screen size for optimal clarity. Fps determines how fast or slow it plays...and it determines how long it will play
Click to expand...
Click to collapse
So, I spent the last two hours messing with it and had no luck fixing the glitch. I just don't know what it could be. I've reached out to a few of the rom groups and no response. I also haven't seen anyone else report this problem. I don't think it's a hardware issue, and it seems to happen on every rom I've tried. Any ideas?
Does it happen with any bootanimations?
TheGhost1951 said:
Does it happen with any bootanimations?
Click to expand...
Click to collapse
Yes. Used the stock one on Nameless, WatchDogs, Lineage. All seem to have that issue, unfortunately. I'm thinking it's the implementation of QHD? Or some DPI issue?
kodayoda713 said:
Yes. Used the stock one on Nameless, WatchDogs, Lineage. All seem to have that issue, unfortunately. I'm thinking it's the implementation of QHD? Or some DPI issue?
Click to expand...
Click to collapse
I tend to believe that during boot, it is switching from one mode of display quality to the mode you changed to. You stated that on FHD, it doesn't happen. Possible?
TheGhost1951 said:
I tend to believe that during boot, it is switching from one mode of display quality to the mode you changed to. You stated that on FHD, it doesn't happen. Possible?
Click to expand...
Click to collapse
That's my thought. I guess there would have to be some back end changes made, and not something that could be changed in the boot animation sequence?
kodayoda713 said:
That's my thought. I guess there would have to be some back end changes made, and not something that could be changed in the boot animation sequence?
Click to expand...
Click to collapse
That is my thoughts since it works ok on FHD mode.
TheGhost1951 said:
That is my thoughts since it works ok on FHD mode.
Click to expand...
Click to collapse
Thanks for the help, good sir. I will continue searching
How did you manage to remove orange state text?
lukacarina said:
How did you manage to remove orange state text?
Click to expand...
Click to collapse
Wrong thread.....