Hello guys!
I was just wondering if anyone was able to perform the softunlock on Quarx's new builds (New Life ones, with new partitions).
Until this recent versions i was able to do it with Baseband_change(EP93_U_00.59.01).zip and CMX_softunlock_2ndBoot.zip with no problems (this also worked for JB with no issues).
Has anyone found a solution?
rc_nico said:
Hello guys!
I was just wondering if anyone was able to perform the softunlock on Quarx's new builds (New Life ones, with new partitions).
Until this recent versions i was able to do it with Baseband_change(EP93_U_00.59.01).zip and CMX_softunlock_2ndBoot.zip with no problems (this also worked for JB with no issues).
Has anyone found a solution?
Click to expand...
Click to collapse
Haven't tried, but it should not be an issue I think. Are you facing any particular issue?
thekguy said:
Haven't tried, but it should not be an issue I think. Are you facing any particular issue?
Click to expand...
Click to collapse
Couldn't make it work.
I get a sign asking me for the unlock code.
I was able to do it before on Quarx's builds. I guess it has something to do with the new partitions.
Enviado desde mi MB526 usando Tapatalk 2
Related
Hi
has anyone tried the ICS encryption feature yet? Does it work? Performance impact?
It touches your SD card data so not recommended for now...
Sent from my MB525 using XDA App
ace-drink said:
Hi
has anyone tried the ICS encryption feature yet? Does it work? Performance impact?
Click to expand...
Click to collapse
quite nice...and very stable. but there some problems to solution.
many fc no uc browser 8.1 (chinese version)
no wish no photo...
act...
I enabled it on CM9, but no dice.
ace-drink said:
Hi
has anyone tried the ICS encryption feature yet? Does it work? Performance impact?
Click to expand...
Click to collapse
I have tried repeatedly on my new Galaxy Nexus to make it work, but I can never successfully encrypt the device. It fails half way and then everything is lost... so be careful if/when you decide to encrypt. Be aware if it does not work everything will be wiped; backup everything. Sorry I don't have more useful info. If I get it working I will re-post with my comments about speed etc.
The encryption is the only thing that will allow us to use an android device at work...quite sad to see it's still in such infant state...
@nameite The full disk encryption offered in the newer Moto updates seems to work well. I encrypted the NAND only on a d2g and everything worked smoothly.
Hello guys,
I'm using 4.1.1 JB by Quarx (2808 build) for 2 weeks and since then I'm trying to understand what can I do to solve the Chrome problem.
When I try to use it, it opens, hang for 5 seconds and closes. I guess that Chrome thinks I'm a bad, a really bad user, or that I'm Chuck Norris.:laugh:
I'm don't know if theres a solution or not, but, as I said, I'm trying to use it and it doesn't like to be used. :silly:
If anyone knows the solution, please, tell me.!
Thankful since now...
One does not simply uses search?!
Question has been answered and i will tell you now!
Easier step: Delete Chrome and Reinstall it. On installation..first thing when you open it will be setup menu. Make sure you DON'T click Reporting checkbox (first checkbox that appears)!
Thanks and sorry.
Enviado do meu Defy+ 4.1.1 JellyBean usando Tapatalk2!
Since September 4th release of quarx's cm 10 I have had problems with my touchscreen, sometimes a lot of ghost touches, sometimes the screen is not responsive.
Other users have reported the same problem, and to verify I went back to cm 7.2, and then I had no problems at all, so it's not a hardware issue...
Is there anyone who can help me extract the old drivers (pre Sept 4th) and inform me how to install them on the latest nightly of quarks cm10?
Would this cause other problems?
Thanks!
defylerat, via tapatalk och quarxs cm10!
henkaoh said:
Since September 4th release of quarx's cm 10 I have had problems with my touchscreen, sometimes a lot of ghost touches, sometimes the screen is not responsive.
Other users have reported the same problem, and to verify I went back to cm 7.2, and then I had no problems at all, so it's not a hardware issue...
Is there anyone who can help me extract the old drivers (pre Sept 4th) and inform me how to install them on the latest nightly of quarks cm10?
Would this cause other problems?
Thanks!
defylerat, via tapatalk och quarxs cm10!
Click to expand...
Click to collapse
Well, this seems to be a difficult task since noone even dares to take a guess
I just browsed through the zip archive on my computer, and of course found lots of files.... But which file is the driver for the touch screen?
Can anyone advice?
If i just copy the driver file from an older release, and just replace the same file from a newer release i guess i would get the old driver back... BUT - how do i find out which file i need to copy...
Old touchdriver
I think I have extracted old touchdriver from 09.03 build, because this file size is different then 11.28 and other builds, so i think this is old touch driver. Test it, if touch responsibles will be better, I will flash it too.
turffe said:
I think I have extracted old touchdriver from 09.03 build, because this file size is different then 11.28 and other builds, so i think this is old touch driver. Test it, if touch responsibles will be better, I will flash it too.
Click to expand...
Click to collapse
Thanks! ! ! I will give it a try at once!
defylerat, via tapatalk och quarxs cm10!
I have been using 0903 for some time due to the touch problems...
Went back to a backup of 1204 and installed the driver zip, and it seems to be working just fine :thumbup::beer::beer::beer:
defylerat, via tapatalk och quarxs cm10!
I have understood that we are quite a few users experiencing these ghost touches with the new drivers... maybe if we describe our system quarx (or someone else of course) can find the reason to these problems.
I am using a red lens defy.
Have had my screen replaced on a warranty issue...
defylerat, via tapatalk och quarxs cm10!
turffe said:
I think I have extracted old touchdriver from 09.03 build, because this file size is different then 11.28 and other builds, so i think this is old touch driver. Test it, if touch responsibles will be better, I will flash it too.
Click to expand...
Click to collapse
but in the zip isn't the module. Just the init.d script
Can anyone verify if this works? I have been having weird touch issues also. I'll be typing a message and it will pick a letter clear on the other side of the screen. Same thing within the application drawer. I'll go to click on 1 app and it will pick up on some random app no where near where I was clicking
I understand that you dont want me to verify my own sayings, however it is working A LOT better, but still i have a few ghost touches every now and then, I have activated the option to display visual feedback of touches(dont know what its really called in english) under developer options to ease seeing if its just random or there could be hw errors as well...
I really can recommend installing the zip, it has made the rom extremely useful instead of sometimes extremely annoying
Dont ask me why... but the ghosts are back, and just about as bad as they used to be... Havent changed anything in my configuration...
Replace multitouch.Ko located at system/lib/modules/ with multitouch.ko from CM7 using rootexplorer
Sent from my MB525 using Tapatalk 2
This problem is freaking me
I´ve been having this problems since i flashed quarx cm10, too whit the lastest cm9 by elyspon, the latest cm7.2 by eurouskank and the official cm
only when i go back to stock rom the touchscreen works perfectly
i have a bl7 defy+ whit red lense, the screen is a little bit scratched, i really want to have cm10, but whitout the fear that in any moment my screen will have some ghost touches
---------- Post added at 12:22 PM ---------- Previous post was at 12:12 PM ----------
pradeeppk said:
Replace multitouch.Ko located at system/lib/modules/ with multitouch.ko from CM7 using rootexplorer
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
i´ll try
Can someone verify is this solved the problem?
Okay!
Could I just get some sort of final solution, not only me, but the many others on xda that are suffering from the same problem as me. Why am I not getting notifications!? I've tried almost every kernel on here, from Franco to Air kernel and no luck! I've tried using the PNF app, no luck there! Is there just one solution!?
I restored a nandroid from when I fresh rooted my nexus. Is this a kernel issue or a ROM issue ?
Sent from my Nexus 4 using Tapatalk 4 Beta
This is an issue Google needs to fix in the upcoming android release. I believe someone in the android development forum section is trying to fix it so you could try to find and visit the thread if you need more info or can provide help...
Sent from my Nexus 4
+1
I've got to unlock my phone for the notifications to show up. Defeats the purpose of having push notifications
Sent from my Nexus⁴ running CM10.1
Have you tried any of those fixes
http://forum.xda-developers.com/showthread.php?t=2272140
http://forum.xda-developers.com/showthread.php?t=2300873
http://forum.xda-developers.com/showthread.php?t=2072930
http://forum.xda-developers.com/showthread.php?t=2102986
It may work for you, just make sure and be careful to choose which one. I myself haven't tried any of them (keeping stock for sometime)
I've been using a +motley kernel found on his thread that someone modified with newer prima drivers. It has worked fine for me for months now.
Dear XDA-Community,
I have a really strange problem with my ZUK Z1 touchscreen, but only with ROMs with a build date after the 22th of Dezember 2016.
First I thought it's because I didn't wipe my phone fully before flashing the ROMs, but yesterday I tried it after wiping my phone completely.
But didn't work neither.
So after flashing the ROM and rebooting my phone, I "couldn't" control my phone, but then I realized that the touch reply was just in the "wrong place" like I touched in bottom and the output was in the middle of the screen.
I didn't have this problem before, and i researched all over the internet, if it's problem with the ROM but it doesn't seem so. Like I'm the only one with such an issue.
I hope anyone could help me.
Best regards
johannestheg
johannestheg said:
Dear XDA-Community,
I have a really strange problem with my ZUK Z1 touchscreen, but only with ROMs with a build date after the 22th of Dezember 2016.
First I thought it's because I didn't wipe my phone fully before flashing the ROMs, but yesterday I tried it after wiping my phone completely.
But didn't work neither.
So after flashing the ROM and rebooting my phone, I "couldn't" control my phone, but then I realized that the touch reply was just in the "wrong place" like I touched in bottom and the output was in the middle of the screen.
I didn't have this problem before, and i researched all over the internet, if it's problem with the ROM but it doesn't seem so. Like I'm the only one with such an issue.
I hope anyone could help me.
Best regards
johannestheg
Click to expand...
Click to collapse
It was the same for me. Becomes more and more and finally also in twrp the digitizer wasn't working anymore. I don't had a wrong calibration.
strongst said:
It was the same for me. Becomes more and more and finally also in twrp the digitizer wasn't working anymore. I don't had a wrong calibration.
Click to expand...
Click to collapse
Could you fix it? Or did you buy a new phone?
And if you fixed it, how did you do so?
best regards
johannestheg said:
Could you fix it? Or did you buy a new phone?
And if you fixed it, how did you do so?
best regards
Click to expand...
Click to collapse
I sent it back for warranty.
strongst said:
I sent it back for warranty.
Click to expand...
Click to collapse
Damn. Shouldn't have bought it on such a unserious site^^
If someone has a solution, pls tell me
How I said, it's working perfectly on CM 14.1, so it seems like a software problem
johannestheg said:
Damn. Shouldn't have bought it on such a unserious site^^
If someone has a solution, pls tell me
How I said, it's working perfectly on CM 14.1, so it seems like a software problem
Click to expand...
Click to collapse
Few users reported touch issue solved after flashing Radi active kernel in N. Did u try latest NuceaRom or Mokee?
Narasimha12 said:
Few users reported touch issue solved after flashing Radi active kernel in N. Did u try latest NuceaRom or Mokee?
Click to expand...
Click to collapse
No I didn't, but I'll give it a try, thank you mate
But I wonder if the problem is solved then completely, or only if you have installed NucleaRom/Mokee
johannestheg said:
No I didn't, but I'll give it a try, thank you mate
But I wonder if the problem is solved then completely, or only if you have installed NucleaRom/Mokee
Click to expand...
Click to collapse
My understanding is that, something messed in upstream lineage OS, which effected couple of updates of NucleaRom and initial testing builds of Mokee. With the help of Radioactive kernel developers, thankfully Mokee managed to debug it.
Does screen issue happens in lower version of Android too? Like MM & L? if so I'm not sure this is going to help.
Narasimha12 said:
My understanding is that, something messed in upstream lineage OS, which effected couple of updates of NucleaRom and initial testing builds of Mokee. With the help of Radioactive kernel developers, thankfully Mokee managed to debug it.
Does screen issue happens in lower version of Android too? Like MM & L? if so I'm not sure this is going to help.
Click to expand...
Click to collapse
No didn't ever have this problem before, so thanks for the good news, I'll update after testing
So I tried it with the Tesla Rom and it worked fine
Thanks for the help
johannestheg said:
So I tried it with the Tesla Rom and it worked fine
Thanks for the help
Click to expand...
Click to collapse
Bingo
Sent from my Zuk Z1 using XDA Labs
Same problem with my Zuk Z1.
Today I flashed de unofficial LineageOS and the touchscreen don't work.
I flashed again the old ROM (October CM) and the touchscreen worked again.
I tried later with full wipe... Same problem.
From: Me
Via: Huawei Mate 9 (MHA-L09) - Tapatalk
To:
sethnet said:
Same problem with my Zuk Z1.
Today I flashed de unofficial LineageOS and the touchscreen don't work.
I flashed again the old ROM (October CM) and the touchscreen worked again.
I tried later with full wipe... Same problem.
From: Me
Via: Huawei Mate 9 (MHA-L09) - Tapatalk
To:
Click to expand...
Click to collapse
Latest lineage OS doesn't have this problem. If you are still getting the touch screen issues, try NucleaRom
Sent from my Zuk Z1 using XDA Labs