Related
My phone has a 2mm zone where the touchscreen does not work.
what could it be?could it be a software problem?if it's not how much does it coast to replace the touch?I'm out of warranty...
BurningKoala said:
My phone has a 2mm zone where the touchscreen does not work.
what could it be?could it be a software problem?if it's not how much does it coast to replace the touch?I'm out of warranty...
Click to expand...
Click to collapse
This was a known problem with custom kernels for a while. Most kernels have now rectified it, so download a newer version of your kernel, install it and see if it helps.
http://www.youtube.com/watch?v=AKYtCKvOPmg&feature=youtube_gdata_player
this is a video of the problem,you can see it at 1:00...is this the kernel problem?now i don't have the phone,so i can't test...
if you use a spica or swiftextreme kernel, i suggest you change your kernel. you can use a stock mod rom, i would recommend neoblaze kernel. i use spica kernel a few weeks ago and i have same problem with you. i change neoblaze kernel and this problem solved...
I am using spica s latest kernal and everything is fine no dead areas on the screen and great battery too. I am currently using topogigi 2 sr3 rom
Sent from my LG-P990 using XDA App
BurningKoala said:
http://www.youtube.com/watch?v=AKYtCKvOPmg&feature=youtube_gdata_player
this is a video of the problem,you can see it at 1:00...is this the kernel problem?now i don't have the phone,so i can't test...
Click to expand...
Click to collapse
I've watched your video, and it does indeed seem like your touchscreen has a dead-zone 2/3s up on the screen.
Most likely it's a hardware problem, but you can of course try to factory reset the phone first and see if it helps, but I doubt it. And no, this is not related to the kernel-problem.
In the "Optimus 2X Accessories" forum there are threads which mention screen- and digitizer-replacements, you could ask in that forum for the cheapest way to replace it outside warranty. I've no experience with that myself, sorry.
I was using Lg p990 v10f from India.. yesterday unexpectedness phone was shutdown., i try to turn on black screen of death and count.. reboot.., i try to update my phone to 2.3.4 .., its reboot was clear and now working fine., but still phone display blank only.., what can i do.., kindly tell me any solution
BurningKoala said:
My phone has a 2mm zone where the touchscreen does not work.
what could it be?could it be a software problem?if it's not how much does it coast to replace the touch?I'm out of warranty...
Click to expand...
Click to collapse
Since last week I have the same problem. Did you ever solved it? Will try to install the NeoBlaze kernel and afterwards the guestekrnL.
Hi Everyone,
I recently updated my stock version of w8 i.e. 2.1 to GingerDx V 0.22 by doixanh and works everything fine for me.
Also, installed the addons supplied in (http://forum.xda-developers.com/showthread.php?t=1188486) which contains AnDyX's Dualtouch for Cypress, AnDyX's smartass governor, ext3/4, X8Gesture, X8MDDI, X8UV.
i am able to get pinch to zoom but i am not sure if it is fake pinch to zoom or the real one because i read on of the posts and it was written that if the phone support Cypress digitizer then i phone can have a real dual touch. I also followed the steps given there and found out that my phone supports it but how can I get a real dual touch?
Also in the cyanogen settings/ performance/ cpu settings how can i set min CPU and max CPU frequency as per my choice as no option is available. I mean to say how can I overclock my CPU.
Also i want to know that CPU is Undervolted or not?
I am also attaching the screenshot of my kernel version and other information of Ginger DX.
And at last i want to know if my phone has alfs kernel or not? If not, what is the next step to get that?
Thanks in advance
A'ight, your phone has stock kernel, to overclock, just copy the overclock module to system/lib/modules, so that there will be options to set min and max freq. Atlast, if you have fake dual touch, there is NO way to make it "real dual touch"; except replace the digitizer with cypress.
Cheers.
Sentrax123 said:
A'ight, your phone has stock kernel, to overclock, just copy the overclock module to system/lib/modules, so that there will be options to set min and max freq. Atlast, if you have fake dual touch, there is NO way to make it "real dual touch"; except replace the digitizer with cypress.
Cheers.
Click to expand...
Click to collapse
Thanks for the info but how can i get the overclock module and can i replace the digitizer with cypress and if i can, how can i replace that??
And also i heard much about Alfv6 kernel but i am not sure what it is and can i replace my stock kernel..
imailca said:
Hi Everyone,
I recently updated my stock version of w8 i.e. 2.1 to GingerDx V 0.22 by doixanh and works everything fine for me.
Also, installed the addons supplied in (http://forum.xda-developers.com/showthread.php?t=1188486) which contains AnDyX's Dualtouch for Cypress, AnDyX's smartass governor, ext3/4, X8Gesture, X8MDDI, X8UV.
i am able to get pinch to zoom but i am not sure if it is fake pinch to zoom or the real one because i read on of the posts and it was written that if the phone support Cypress digitizer then i phone can have a real dual touch. I also followed the steps given there and found out that my phone supports it but how can I get a real dual touch?
Also in the cyanogen settings/ performance/ cpu settings how can i set min CPU and max CPU frequency as per my choice as no option is available. I mean to say how can I overclock my CPU.
Also i want to know that CPU is Undervolted or not?
I am also attaching the screenshot of my kernel version and other information of Ginger DX.
And at last i want to know if my phone has alfs kernel or not? If not, what is the next step to get that?
Thanks in advance
Click to expand...
Click to collapse
YOU need to unlock your boot loader in order to use a custom kernel, so your first step to installing alfs or any other custom kernel is unlocking your boot loader
AbirXtreme said:
YOU need to unlock your boot loader in order to use a custom kernel, so your first step to installing alfs or any other custom kernel is unlocking your boot loader
Click to expand...
Click to collapse
Thanks for the info. I heard that I need a flashtool or something to unlock the bootloader, right? (I have searched many threads but cant find the download link and how to install it?)
I am using GingerDX v 0.22.So, can i unlock my boot loader when i am using it or shall i have to go to stock Rom to unlock the bootloader.?
be careful to unlock bootloader.. i heard w8 is risk to unlock bootloader
read this if you want to unlock bootloader
8xfan said:
be careful to unlock bootloader.. i heard w8 is risk to unlock bootloader
read this if you want to unlock bootloader
Click to expand...
Click to collapse
What type of risk are you mentioning ??
phone can hard brick..lot of thread mention about it..
read this..but you can try it..
imailca said:
What type of risk are you mentioning ??
Click to expand...
Click to collapse
Take out tthe battery from your phone and read the sticker under it.
It should have a line with 11Wxx
Post here what yours says. If it's 11W29 or newer then DO NOT attempt to unlock your bootloader.
Sent from my X8 using xda premium
IrishStuff09 said:
Take out tthe battery from your phone and read the sticker under it.
It should have a line with 11Wxx
Post here what yours says. If it's 11W29 or newer then DO NOT attempt to unlock your bootloader.
Sent from my X8 using xda premium
Click to expand...
Click to collapse
11w31..if so im so lucky LOL first attempt and sucsess
8xfan said:
11w31..if so im so lucky LOL first attempt and sucsess
Click to expand...
Click to collapse
My X8 has 11W06 so I guess I'm safe but I'm still on stock kernel and bootloader locked...
Sent from my X8 using xda premium
owh..y don't you unlock BL? and flash custom kernel?
I dunno, I guess I'm scared xD
LOL
Sent from my E15i using xda premium
I use Xperia X8 11w25, I unlocked my bootloader and using modul multitoouch.
I've a problem with my touch sensitivity. I cant touch anything on the bottom of my screen. Some people says that my front cover is broken.
Anyone, please explain to me.
1. Is the front cover influence the screen sensitivity??
2. Is it connected to the LCD??
3. How it work? because my screen is going unresponsive since I flash a custom kernel.
Please your advice.
Thx
http://forum.xda-developers.com/showthread.php?t=1364045
It worked for me.
maybe you had a cypress digitizer which often had problem with multitouch module??
Dawoods said:
I use Xperia X8 11w25, I unlocked my bootloader and using modul multitoouch.
I've a problem with my touch sensitivity. I cant touch anything on the bottom of my screen. Some people says that my front cover is broken.
Anyone, please explain to me.
1. Is the front cover influence the screen sensitivity??
2. Is it connected to the LCD??
3. How it work? because my screen is going unresponsive since I flash a custom kernel.
Please your advice.
Thx
Click to expand...
Click to collapse
Its not about the module/Kernel..
flash an updated kernel and use a Good Rom..!
Try change the theme..Isernia stock theme
Sent from my X8 using xda premium
I guess it has nothing to do with screen guard ( isn't it screen guard u mean by front cover actually?).
Since I unlocked BL n flashed custom ROMs my screen reacts uneven to touch (compared to when I was still using stock kernel n semc rom).
Btw I'm from malang too , salam kenal ya sam.
phirman said:
I guess it has nothing to do with screen guard ( isn't it screen guard u mean by front cover actually?).
Since I unlocked BL n flashed custom ROMs my screen reacts uneven to touch (compared to when I was still using stock kernel n semc rom).
Btw I'm from malang too , salam kenal ya sam.
Click to expand...
Click to collapse
nope... i mean the front cover of casing. A girl at SEC said it caused by unworking sensor on my screen. so i must change my frontcover..
salam kenal juga bro...
Sent from my X8 using XDA App
Raz9 said:
http://forum.xda-developers.com/showthread.php?t=1364045
It worked for me.
Click to expand...
Click to collapse
If this doesnt solve your problem then I must say that your phone is defective. If youre using GDX most probably you need alfs kernel for the difficult to pull up issue. If your using nAa cm7 then you must have no problems with this even without nAa kernel.
Maybe the problem is because the rom you've installed is too laggy...... So it delays to reply. Which rom are you testing
Dawoods said:
1. Is the front cover influence the screen sensitivity??
2. Is it connected to the LCD??
3. How it work? because my screen is going unresponsive since I flash a custom kernel.
Click to expand...
Click to collapse
1) It shouldn't affect.
2) We all have the same display
3) It depends't on your ROM/kernel. Try to flash the latest version or even change it.
I'm curious, would it be possible to have dual boot on the Note, I don't mean Android & Linux, but have two different roms like RocketRom and Paranoid?
saqibj said:
I'm curious, would it be possible to have dual boot on the Note, I don't mean Android & Linux, but have two different roms like RocketRom and Paranoid?
Click to expand...
Click to collapse
Currently not possible
And might not be possible in the near future too
warfareonly said:
Currently not possible
And might not be possible in the near future too
Click to expand...
Click to collapse
Thank you for your answer.
Sent from my GT-N7000 using Tapatalk 2
Max from rootgalaxynote mentioned something about dual boot in one of his videos. (paranoid review I.think )
Are you sure its not possible
The developer of the AOKP rom (sixstring) said something at one time in that thread (search for it) about dual boot. It is possible, but whenever he can get to it. We aren't paying for this development, so we can't be so picky.
What would've happend if I tried to flash CM10.1 for N7105 to my i9305?
As far as I know, these devices are basically the same!
And I would flash it after I change the build.prop and mount partition, would this work?
sebbe312 said:
What would've happend if I tried to flash CM10.1 for N7105 to my i9305?
As far as I know, these devices are basically the same!
And I would flash it after I change the build.prop and mount partition, would this work?
Click to expand...
Click to collapse
Maybe, I had been speculating this as well actually. Modify the ramdisk to fit an I9305 and you should be good to go, I doubt it could be damaging to your device but I won't take any responsibility on that.
sebbe312 said:
What would've happend if I tried to flash CM10.1 for N7105 to my i9305?
As far as I know, these devices are basically the same!
And I would flash it after I change the build.prop and mount partition, would this work?
Click to expand...
Click to collapse
Please do not try to flash any boot.img from N7100 or N7105!!!!
You simply burn your melfas touch screen chip!
I allready change a device and there is not any solution for that, we allready try everything with AndreiLux and nothing work's, chip is simply burned!
Rekoil said:
Maybe, I had been speculating this as well actually. Modify the ramdisk to fit an I9305 and you should be good to go, I doubt it could be damaging to your device but I won't take any responsibility on that.
Click to expand...
Click to collapse
The reason the touch screen chip is burned is on the melfas firmware the actual kernel have.
So if you change the ramdisk then your melfas chip it will dead too.
Need to compile a new kernel from the source.
ausdim said:
Please do not try to flash any boot.img from N7100 or N7105!!!!
You simply burn your melfas touch screen chip!
I allready change a device and there is not any solution for that, we allready try everything with AndreiLux and nothing work's, chip is simply burned!
The reason the touch screen chip is burned is on the melfas firmware the actual kernel have.
So if you change the ramdisk then your melfas chip it will dead too.
Need to compile a new kernel from the source.
Click to expand...
Click to collapse
Well good thing I didn't try this then
ausdim said:
Please do not try to flash any boot.img from N7100 or N7105!!!!
You simply burn your melfas touch screen chip!
I allready change a device and there is not any solution for that, we allready try everything with AndreiLux and nothing work's, chip is simply burned!
The reason the touch screen chip is burned is on the melfas firmware the actual kernel have.
So if you change the ramdisk then your melfas chip it will dead too.
Need to compile a new kernel from the source.
Click to expand...
Click to collapse
So we're back to square one then..? :-/
never flash anything not made specifically for your phone
WestAussie said:
So we're back to square one then..? :-/
Click to expand...
Click to collapse
You're a pretty pessimistic Aussie aren't you No, we are not back to square one. Fact is this still helps us a lot, we can now compare the differences between the source trees for the I9300 and the N7105 CM10.1 kernels, cherrypicking what we need for our device.
Rekoil said:
You're a pretty pessimistic Aussie aren't you No, we are not back to square one. Fact is this still helps us a lot, we can now compare the differences between the source trees for the I9300 and the N7105 CM10.1 kernels, cherrypicking what we need for our device.
Click to expand...
Click to collapse
You mean the differences between the i9305 and N7105, right? Since we're struggling to port CM 10.1 from the i9300 to the i9305 as it is anyway...
WestAussie said:
You mean the differences between the i9305 and N7105, right? Since we're struggling to port CM 10.1 from the i9300 to the i9305 as it is anyway...
Click to expand...
Click to collapse
No, the I9305 is basically an N7105 with a different panel and touch layer (note: same type of chip, different power supply due to size of panel), I meant that we can compare the differences between configs for the N7105 and the I9300 because that will tell us how to modify the N7105 tree for our device.