I have plenty of other issues with pixel density, but the most intolerable one is regards the signal. I'm actually a Vibrant user (sorry I'm spilling into your forums, but you guys generally have all the answers I need for questions regarding the underlying issues in Android). On 2.1 and 2.2 ROMs alike, I've had issues with RIL resets occurring when I change the density with a program such as LCD Density (I've tried others, too; same result).
On CM7, it's much worse. I'm not sure if it was due to the pixel density, but 2 weeks ago I had a scare and the phone somehow re-locked itself, and wasn't unlocking when I flashed custom ROMs. I had to use a beta of Galaxy S Unlock (had a 'Signal Fix Problem' tab), which resolved the issue. However, I'm having severe signal issues now. Also, the com.android.phone kept force closing on my previous flash, and I had to reflash.
Anyone know if the pixel density affects the EFS at all?
Related
Hi.
Since I made a huge mistake of buying LG Optimus 3D, and I finally managed to get out of it, I'm considering S2 or Note, but before shelling out so much cash for a phone, I'd like to ask a few questions to avoid possible frustration (damn, I should have thought about that before buying the LG...) So, here goes:
1 - Does it work with DPI (ro.sf.lcd_density=) other than stock? I'd like to use 160 since I hate huge icons, but the Optimus 3D bootloops with anything other than 240, so this time I ask.
2 - Any problems with WiFi, does it respect "wifi sleep policy" set to "never"?
3 - Any chances for CM7 for the Note? I'm not too crazy about ICS, I'd much prefer a well-refined Gingerbread ROM that works without bootlooping , graphical glitches, DPI problems and whatnot.
I would be very, very grateful if someone took a few minutes to check if it works with DPI set to 160 or 120, as this is what completely ruined the O3D for me.
Thanks in advance.
Answering here what I experienced so far.
1- U can change pixel density very easily down to 240 at least (using the qemu.sf.lcd_density=), I never tried lower, but I wouldn't go under 240 anyway, things get wayyy too small, I use at 280 which is perfect I think.
2- Wifi always on 24h a day without drops for me independent of screen on or off
Hey guys, I've been off the forums for about a week or so now...can anybody briefy bring me up to speed regarding the issues of the wifi bug, and the auto rotation bug? From what I very hastily just skimmed, I didn't see anything indicating there has been a fix yet. Is there at least any news regarding the status of these issues, and when they may possibly be fixed?
I'm quite fond of ROM flashing, and we all know our small Droid 4 following is pretty limited in the amount of dev support it recieves, compared to several other phones; and continue to appreciate the few devs that have remained faithful to providing the Droid 4 with the few ROMs it does have. So, the not being able to use any custom ROMs because of these few critical glitches has been horrible.
Any insight from anyone on the status of these issues would be much appreciated. Thanks.
Hello,
Sorry to but in, but I'm also experiencing an issue with the Accelerometer not producing any data. I can only switch to landscape mode by sliding the phone open, but I have to turn the screen off and back on to restore back to portrait. Not a huge problem, but one I'd love to see a fix to. Any updates on this would be appreciated. Thanks.
if your on CM10 download his latest version. This should have a fix
Hey there everyone, I got my Mi5 a couple of weeks ago. I flashed Slim7, but right now I use the latest Lineage OS as my daily driver.
Although, user experience has been great I faced a bug in both ROM which I believe is firmware related, but I don't really have a solution. I am not sure if it happened in stock, but in both custom ROMs that I used, sometimes the capacitive keys (back and recents) would stop working. This happened every 5 minutes or so and it only gets fixed if I lock and unlock the device or if I navigate to somewhere else, hence the reason I believe this is software related.
I did a bit of digging around and some people who were also affected by this concluded that might have to do with certain panels being incompatible the kernel, since Xiaomi uses both LGD and JDI panels for the Mi5.
Has anybody managed to solve this issue? A workaround would to enable on screen navigation but I would prefer not to.
Cheers!
I often play rhythm games with my Note 5 so it's pretty noticeable when I get misses because of this.
I am not particularly sure what's causing this. Stock rom or not (I have LineageOS right now, I even tried the ported S8 Edge rom) the problem is still there.
I can make guesses that it could be input lag, general lag, or something else processing related. Is this a common problem? Could this be more on the hardware end?
Tronitus said:
I often play rhythm games with my Note 5 so it's pretty noticeable when I get misses because of this.
I am not particularly sure what's causing this. Stock rom or not (I have LineageOS right now, I even tried the ported S8 Edge rom) the problem is still there.
I can make guesses that it could be input lag, general lag, or something else processing related. Is this a common problem? Could this be more on the hardware end?
Click to expand...
Click to collapse
https://forum.xda-developers.com/note5/help/fix-regions-display-responding-to-touch-t3862955
milance92 said:
https://forum.xda-developers.com/note5/help/fix-regions-display-responding-to-touch-t3862955
Click to expand...
Click to collapse
Thanks for the suggestion. I actually tried your method but, sadly, no improvements whatsoever.
The problem is still present and I can't keep a combo at all in my game due to random unregistered taps.
EDIT: 12 hours after I did your method, things seem to have improved at least. I'm not certain if the problem is completely solved or it's just my own mistakes in the game now. I think I did more shocks to the phone than what you recommended, though.
Hi, sorry if this was posted before, but with XDA moving to XenForo, search seems messed up, i did several searches and nothing comes up for "flicker" in this whole Pixel 4 XL Forum...
Has anyone else dealt with the low brightness screen flicker? I know it can't be just a bad phone, since i just bought three pixel 4 XL phones and they all exhibit this same behavior.
They are all running LineageOS (Official builds) so I don't know if this just affects the ROM or stock as well (although I've read it might affect stock phones too elsewhere).
It makes the phone pretty difficult to use in very low light situations, the screen will constantly flicker (more noticeable on darker backgrounds).
At first I thought it was just the Opera browser (as that's what I prefer), but it's operating system wide... Apps like "Darker" help.... because you can crank up the phone brightness and use a filter to dim the screen.... but it doesn't get the top & bottom menu/buttons, so those remain like spotlights in your eyes with that workaround.
Just curious if anyone knows whats up with this... it's the only phone I've ever seen this behavior on (and i've used Pixel 1,2,3 XL phones all with Lineage, and a myriad of other devices back in the Cyanogenmod days.... I've never seen a screen flicker issue like this).
Thanks for any help
edit / update-
the pro version of "darker" app works to fix this.... you crank the phones brightness to 100% and with the pro version you can dim the rest of the interface.
hopefully this helps anyone else suffering from this HUGE flaw (again i don't know if its just LineageOS or not, i didn't run stock on these except to unlock bootloader etc)
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
edwinek said:
Hi,
I've seen it once and solved it by switching off smooth display. Not a real solution of course, but I never really noticed the difference between 90Hz and 60Hz anyway.
Click to expand...
Click to collapse
hmm.... you running stock i guess? i don't see smooth display option in lineage