Touch Screen Issues After Kernel Flash - T-Mobile Samsung Galaxy Note5

Hello Guys,
So I have a Note 5 (Canadian/W8). The phone has been pretty good so far. Lately, I dont know what has happened, but I can only seem to get the screen to work with the SkyHigh MM Kernel or Arter97 Kernel. I restored it through kies several times but the screen just does not respond. It only works with the stylus unless I flash one of the two kernels.
Any ideas, why this may be?

Related

[Q] All Kernels Lead to a Black Screen

After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Jakkumn said:
After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Click to expand...
Click to collapse
if i was me after reading what I've found online i think i would look for a more reputable dev when it comes to kernels.
Reputable? Faux and morfic are among the elite devs for our device. They don't get any more reputable than them.
-custom sig.
CM7 should work, whether nightlies or stable. Trinity requires ext 4 support, meaning CWM touch won't work. Previous version 5.0.2.0 (I believe) should be used to install trinity. Faux should have worked so not sure why it failed on other than nightlies.
All CM7 based ROM should work with these kernels.
-- The noob says:
Three in the morning I woke up... it was hot... the g2x had SODd!

[Q] - Ruined for all other ROMs?

So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
frankxanders said:
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
Click to expand...
Click to collapse
What recovery are you using? might pay to try another (Recommended: http://forum.xda-developers.com/showthread.php?t=1759452)
You may want to obtain a kernel compatible with the ROM you want to try and flash both the ROM and kernel at the same time. The wrong kernel could definitely cause both the booting problems and the wifi not turning on.
I think about a kernel problem too, go to your ROM thread and you'll see the best kernel to flash with it...

[Q] Phone stuttering after flashing kernel.

I couldnt post in the kernel thread because I don't have enough posts yet..
I installed clean Rom a month or so ago and have been updating to the new versions ever
Since, everything had been running perfectly on the stock kernel. I got the itch to try a new kernel and
decided to try out the elemental kernel (later tried the beast mode as well). Ever since I flashed the new
kernels in recovery my phone keeps stuttering and the screen jumps a bit every couple of seconds, also the
browser keeps reloading when I am on google.com.
I have tried flashing both kernels with different options as well as clearing cache before and after flashing, plus
fixing permissions but the problem continues. I also did a factory reset and reinstalled clean Rom and both kernels.
Has anyone had this happen to them before and know of a solution?
Thanks in advance.
Are you overclocked? Not every phone can handle oc'ing.
No. At first I tried the kernels with the oc to 1.7 option, but then I tried both kernels with no oc, no gpu oc, no sweep to wake, and no
Under volt but the screen kept flickering and the apps kept having hiccups.
I flashed the stock kernel from viperxl and now the phone is back to normal.
I am on 2.20 with the hboot 1.14 by the way.

Is there a stable ROM right now that doesn't random reboot???

I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Update:
Tried Elemental X, the phone reboots randomly now... And also just googled problem with Nexus 5... it seems like 5.0 and 5.0.1 have TONS of random reboot issues...? Goddamn it Google...
Do any of you have a stable ROM (stock or custom) that doesn't have random reboot issues?
Elementalx
codenamezero said:
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Click to expand...
Click to collapse
i use franco kernel 70 with stock rooted 5.0.1 with no issues. but i don't see any differences between stock and franco. neither performance nor battery life.
This Nexus 5 is just getting worst... it random reboots now.
codenamezero said:
This Nexus 5 is just getting worst... it random reboots now.
Click to expand...
Click to collapse
Sorry to hear that. Could it possibly be a hardware issue since you say it's happening to you across all software? Corrupted storage media could cause random reboots such as that.
I'm not seeing any myself, though I do reboot the phone about once a week just as a precautionary measure with L's RAM management.
Was having this issue with Stock and Custom ROMS ended up going back to KITKAT and no problems. Hopefully they will have this fixed with 5.1 that will be released soon.
Stock one is allways the best choise. You must be aware, that the stock one is build by a lot of good developers and custom ones are made by individual enthusiasts. There is nothing wrong with that, but the pure logic here speaks by itself.
Used a lot of different roms
ordered my nexus on release day, used quite a few different roms and i've never had a random reboot.

[Completed] My note 4 screen touch calibration is off, reads my touches at a different part scree

Hey guys so I was flashing some roms on my note 4 and idk what happened and I ended up with my screen touch not being calibrated. For example when I touch the top part it reads it slightly lower that I touch it, and same with other parts of the screen. However, it reads my s pen perfectly fine and with no issues. I flashed back stock samasung rom and it didn't do anything, so I tried to flash a new rom (cyanogen) and it still didn't work. I am currently on cyanogenmod 12. Please help!
XDA Visitor said:
Hey guys so I was flashing some roms on my note 4 and idk what happened and I ended up with my screen touch not being calibrated. For example when I touch the top part it reads it slightly lower that I touch it, and same with other parts of the screen. However, it reads my s pen perfectly fine and with no issues. I flashed back stock samasung rom and it didn't do anything, so I tried to flash a new rom (cyanogen) and it still didn't work. I am currently on cyanogenmod 12. Please help!
Click to expand...
Click to collapse
Hello, and welcome to XDA! You may have to reflash stock firmware through fastboot in order to get rid of this bug. I am linking you with the help forum for your device in case someone is able to offer another suggestion: http://forum.xda-developers.com/note-4/help. You will need to register in order to post.
Good luck!

Categories

Resources