Hello everyone,
today i started experimenting with my tab2 10.1. Rooting was ok. But then I decided to change the lcd density setting. I looked for the /system/build.prop and opened it but the "ro.sf.lcd_density = 240" line which should be there was missing. So I decided to add the following at the end of the file ro.sf.lcd_density = 180 (the setting I use on my HTC HD2). After the following reboot the tab got to the point where the first logo (samsung galaxy tab 2 10.1) dissapears and the samsung short "video" and logo should appear. But it didn't. So the tab hang with a lit black screen with nothing on it.
And then I had to flash the ROM I found here - P5110XWALD2_P5110PHNALD1_PHN so that I can get it back to life (which I think was not my original one).
My question is if I did something wrong here and what exactly. Now I am afraid to try it again
p.s. please move to Q&A
I believe that the default LCD Density should be 160 for the tablet. Changing it to anything else can cause issues, like you saw with it not booting properly.
I run my 7 at 145dpi. Gives me the extra room I need.
240 will cause crashes and sometimes boot loops.
I don't think you can change it without issue on the stock rom. I recommend cm for this.
I changed mine to 145. Looks better that way.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Hello developers let me start off by saying thank you for the work you put in to what you do it's helped me enjoy android and feel proud of owning these devices. Now I have been a lurker for a while and have rooted and rom'd my previous phone (HTC glacier) and it was wondrous. I recently bought a nexus 7 and am amazed with the machine but I did have a slight screen issue when I got it
The screen had a black line going horizontally when held in portrait mode that only showed up on the home screens and in google maps (but only in portrait mode it did not appear in landscape mode) This caused me to do a bit of research and i found people who had the same problem that said it was all gravy once a new kernel was installed.
This of course led me to rooting installing the MadaCo Custom Rom Jr2 (have a 3g 32gig model) and running the motley kernel 3.1.20. Installed overclocked but nothing happened and was confused.
after installing some games and talktone i found that once the games got faster paced white started flashing through the colors and when connected through talk tone a white diagonal line appears on the screen. Not only that but i also noticed that if i put apps on the top row in my home screen, when i go to slide over to the next page the colors of the app shows up in the black line.
I was wondering if this is hardware issue or if their is something i can do on the software end. If it's hardware and i have to return it to google i'd appreciate any info i should know about warranty as well as being pointed in the direction i need to go in order return in to stock 4.2 and locked (I'm a noob whose only rooted twice when trying to push the motley kernel onto my nexus 7 i accidentally went into the the side load in cwm and had about 10 failed attempts before i could give it the proper push command to install the kernel)
any advice or help would be greatly appreciated sorry to take your time out with something so basic but I'm doing what I can to learn
During the first boot screen (the one where "Samsung galaxy S IV - I9505" is displayed) there is a vertical green line of pixel in the left of the screen who runs across the entire screen from top to bottom.
It disappears immediately after during the boot animation from my carrier and it never appears anywhere else when using the phone. Besides that everything is working fine and I haven't got any issue with the phone, no dead pixels or other problems I can think of.
I'm just wondering if it's an hardware issue and I should be worried about it and change the phone at the shop or if it's just some weird kernel bug who could easily be fixed.
I could already have checked by installing another rom but I don't really want to tinker with the phone because of warranty issues...
My phone carrier is Orange France.
HI.. I bought Nexus 4 about a month ago. It has very low touch sensitivity. I checked PRS value. It only stuck at 0.80. I had a Stock ROM when i bought, then i tried another Custom ROM based on CM11. Still i have same issue. It's very irritating. It's very hard to type even a single sentence. I even tried many touch fix of application.
I found another weird problem. when i put my phone on Table or something It completely stop giving touch response but when i put back on my hand it gives touch response. When i remove my hand behind from back of phone it again stop touch (While holding my phone with two finger from side, Like while Taking picture) and when i put back my hand behind phone it again start working touch.
I tested it on Stock rom, CM11 and also another XperiaZ mod rom. so please don't say me that i have problem in ROM.
Exact same issue
Hey dear, I've the exact same issue including the 'weird' one.
Do inform me if u find a solution.
I've attached a screenshot.
I had a Korean LG G2 for a week a while back. However, on the 7th day the screen exhibit some strange problems. Which I returned it to the seller.
I've tried to google this problem but I (1) cannot find the right search terms and (2) do not see anyone with this problem. I was on a custom rom and flashed it back to stock rom but the problem persists. It feels like a mix of overheat and faulty screen.
As you can tell the clock widget is "stuck" on several screens (even recovery). If I put the phone in the fridge or leave it untouched overnight it reverts back to normal and usable for 15 mins then the problems comes up again.
I want to ask what is this problem and is it prevalent in korean LG G2?
I really like LG G2 but fear of buying another one that has this same problem.
Anyone has any ideas?
Yesterday I've noticed similar problem, I use swiftkey with a red theme and white letters (I don't think it's app's fault) and after displaying it for some time and then switching to other screen it looks like the keyboard is "burned" on the screen. It's not visible on color background but on medium light gray it's easy to seen. After some time without using keyboard it disappears.
ekion said:
I had a Korean LG G2 for a week a while back. However, on the 7th day the screen exhibit some strange problems. Which I returned it to the seller.
I've tried to google this problem but I (1) cannot find the right search terms and (2) do not see anyone with this problem. I was on a custom rom and flashed it back to stock rom but the problem persists. It feels like a mix of overheat and faulty screen.
As you can tell the clock widget is "stuck" on several screens (even recovery). If I put the phone in the fridge or leave it untouched overnight it reverts back to normal and usable for 15 mins then the problems comes up again.
I want to ask what is this problem and is it prevalent in korean LG G2?
I really like LG G2 but fear of buying another one that has this same problem.
Anyone has any ideas?
Click to expand...
Click to collapse
It seems that this is similar to the black line issue some people had. If you have warranty send it back. I think only way to fix is to change the panel and/or digitizer
Before you send it back, have you downloaded any new ROMs? Flashed CWM/TWRP? Because when I did the following I had a problem similar to that. It appeared that whatever my phone was running did not support my type of screen, therefore I downloaded a specific type of Kernel that fixed it right up. If you think this applies to you I will try to dig up what Kernel it was.
Hi everybody.
Yesterday, I replaced the screen of a LG G2 which was broken.
Everything in the procces went okay, but when I turned on the device, the screen had white lines across the screen. The main fact and more strange thing is that it only shows white lines when the device is on the Launcher or some system apps, when it goes to Settings, Twitter...or any app, the screen works perfectly.
I've tried upgrading to Lollipop, coming back to Jelly Bean, upgrade to KitKat...and the problem doesn't go away. Don't forget to say one important thing: I'VE TRIED THE KERNEL FOR JDI DISPLAYS, and that doesn't fix nothing at all.
I don't think the screen is broken because as I have said, it works perfectly in the apps.
Best regards, waiting for answers! :good: