Possibly yes. But you have to adapt the drivers and values for your device according to dmesg.
hello there am having the same problem but only with the camera
it's upside down
any thing?
great !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
solved thanks
bro can you please tell me how you fixed it.. i have detected model sharp
---------- Post added at 09:02 AM ---------- Previous post was at 08:35 AM ----------
bro can you make a driver for sharp panel with mdw30...
This method will work on Xperia V too ...? A little bit unbelievable...I thought that only TX used such panels.I have a Xperia V, I have followed the guide as written to pag 1
bro can you please tell me how you fixed it.. i have detected model sharp
---------- Post added at 09:02 AM ---------- Previous post was at 08:35 AM ----------
bro can you make a driver for sharp panel with mdw30...
This method will work on Xperia V too ...? A little bit unbelievable...I thought that only TX used such panels.
I have the T and i was wondering if this would fix the issues im having with my back camera? i am on the lollipop ROM for TX.
This is not related to camera problem. And do not try what's said in this thread, since it may lead to hardware damage.
ok is there any way to fix the camera problem?? i used a method and it was not inverted any more however the camera dont focus :/
Pls help me. I think my phone has the same problem.
After run adb, i restart my phone and screen only show blank.
yes. Before that, it show mdx80. Now it can't indentify my panel
Are you using the kernel listed in the post? Sometimes the kernal may fail to install. But if it's the right one, I may not be able to help. There may be another kind of panel that hasn't been found yet.
You may try flashing stock FTFs to see if it fixes the panel, or you have to send it for repair.
1.Download the kernel(c_rtest.elf) and unzip & flash it. We don't need to boot the whole system so no special Android system is required.
2.When the amber light shows up, press Vol+ or Vol- to enter Recovery.
3.Open a terminal and launch "adb shell" on your computer.
4.Type in adb shell
5.Check if the response contains the string "mdx80"Code:dmesg | grep "panel"
6.------If there is no such text,please post the response here , stop immediately,and flash back to previous kernel.(but if you find ACX... in the response,please do not post.That's Screen type B and I don't own such a device. Sorry...)
------If there is "mdx80",just go ahead.
7.Type
-----If you see "mkdir failed: d already exists",just skip the "mkdir d" and "mount" commands(first 2 lines) and go on.Code:mkdir d mount -t debugfs none /d cd /d/msm_fb/mipi_r63306 echo 1 > break_nvm (The screen will go blank.That's normal.Don't be stressed.) echo 1 > recover_nvm (The screen should be working now)
8.Flash the ROM you want to use IMMEDIATELY after the screen starts to work. Just don't stick with this experimental kernel.
1.Download the attached MDX80 driver.
2.Make a backup of (kernel root dir)/drivers/video/msm/mipi_r63306_panels/mipi_tmd_mdx80.c
3.Extract the zip file to drivers/video/msm/mipi_r63306_panels/ and overwrite the original mdx80.c.
4.Modify your kernel config CONFIG_FB_MSM_MIPI_R63306_PANEL_TMD_MDX80=y
5.Compile the kernel and pack it with ramdisk.Then just flash it.
echo 1 > /sys/devices/platform/mipi_dsi.524288/eco_mode
echo 0 > /sys/devices/platform/mipi_dsi.524288/eco_mode
This morning I wanted to find a zImage that could boot 9.2.A.0.278 LT30p leaked firmware on my LT29i.Among the zImages I have,there is one extracted from LT30p CM10.2.But I didn't remember it and flashed it on my phone.Then the terrible "inverted screen" came...
After ~5hrs researching,I found that after cross-flashing,the panel was recognized as MDX80 instead of the correct MDW30_1e.
Maybe RECOVER_PANEL config caused this...The 30p kernel found there was a panel but it couldn't recognize it,so the kernel thought the panel was corrupt and executed the recovering process,after which our MDW30 was overwritten with MDX80 register data.But MDX80 driver fails to initialize the panel with commands required by MDW30 so the panel displays thing upside down...
I think that now that it loads MDX80 driver,why can't we add MDW30 init commands to the MDX80 driver?And there comes the key!
I just copied init_cmds and on_cmds from mdw30.c and replaced the ones in mdx80.c.It works!
And here is my work:
That should do with "Touch Firmware version C" devices.:victory:
A little bug:screen gamma correction and ECO MODE aren't working properly.The color is a bit different from stock kernel.
There is another way:dump the correct register values from a normal TX and write our own NV Recover data using CONFIG_FB_MSM_RECOVER_PANEL.
But I don't know how to dump data.Anyone can help?So that we won't have to re-compile the kernel every time we flash a new firmware...
ok is there any way to fix the camera problem?? i used a method and it was not inverted any more however the camera dont focus :/