Hey
I installed this rom yesterday, my applications are much smoother, but i have a huge problem, which makes almost every game unplayable. When i try to play the game with 2 fingers, it doesnt respond well. Is there any way to fix this?
Rucsok said:
Hey
I installed this rom yesterday, my applications are much smoother, but i have a huge problem, which makes almost every game unplayable. When i try to play the game with 2 fingers, it doesnt respond well. Is there any way to fix this?
Click to expand...
Click to collapse
That's not a problem with the ROM as much as it is a general problem with the HD2 unfortunately. It only supports 2 points on the screen, and I've found it does that terribly as well.
Nigeldg said:
That's not a problem with the ROM as much as it is a general problem with the HD2 unfortunately. It only supports 2 points on the screen, and I've found it does that terribly as well.
Click to expand...
Click to collapse
I dont think so, in my previous rom (Typhoon CM7) multitouch worked flawlessly in the games. After all these updates, how isnt it a priority to fix this?
Rucsok said:
I dont think so, in my previous rom (Typhoon CM7) multitouch worked flawlessly in the games. After all these updates, how isnt it a priority to fix this?
Click to expand...
Click to collapse
Because it's working for almost everyone, so it isn't really a 'known problem' as such. What version of the ROM are you on? If you're on 2.1 it'll be a bit shady, but multitouch works as well as it did on Typhoon for me on v2.2 (haven't got round to the 2.3 update yet).
Nigeldg said:
Because it's working for almost everyone, so it isn't really a 'known problem' as such. What version of the ROM are you on? If you're on 2.1 it'll be a bit shady, but multitouch works as well as it did on Typhoon for me on v2.2 (haven't got round to the 2.3 update yet).
Click to expand...
Click to collapse
2.2
I'll reinstall the rom (now the 2.3 version) hopefully this will fix the problem.
Rucsok said:
2.2
I'll reinstall the rom (now the 2.3 version) hopefully this will fix the problem.
Click to expand...
Click to collapse
Hmm, try going into the settings>developer options and enabling 'pointer location', then see if both the points are detected. Don't worry if the two points sometimes 'lock together', this is normal for the HD2's outdated screen
Nigeldg said:
Hmm, try going into the settings>developer options and enabling 'pointer location', then see if both the points are detected. Don't worry if the two points sometimes 'lock together', this is normal for the HD2's outdated screen
Click to expand...
Click to collapse
I tried this, i can certainly feel the "lock together"-effect. Is that supposed to be normal? If thats a HD2 related problem, how come i havent experienced this before?
Rucsok said:
I tried this, i can certainly feel the "lock together"-effect. Is that supposed to be normal? If thats a HD2 related problem, how come i havent experienced this before?
Click to expand...
Click to collapse
As far as I know that's a HD2 problem, yes. You probably have experienced it before, but haven't noticed it because you don't have the visual feedback to show you that it's happening. It doesn't have much of an effect during gaming (surprisingly)
omethek
it is a problem, because any game with a joystick is unplayable.
edit: besides the 'lock together', sometimes when the touch points are close to eachother, they are detected "inversed". is that normal too?
I agree that our device is outdated, but I've never experienced such issues.
I played multitouch games on WP7, Android GB & (Currently) ICS .. Even GTA 3, the movements are precise.
Not sure what you two are facing, but it's definitely not "too-old" related.
The only thing that the HD2 can't do is handling more than two finger points, other than that, everything seems to be fine for me.
There are lockups, but they are rare.
Rucsok said:
it is a problem, because any game with a joystick is unplayable.
Click to expand...
Click to collapse
Rucsok said:
edit: besides the 'lock together', sometimes when the touch points are close to eachother, they are detected "inversed". is that normal too?
Click to expand...
Click to collapse
I'm beginning to agree with Marvlesz here, these issues aren't that normal. I've never had the points becoming inversed and I can play games with onscreen 'joysticks' (i.e. GTA3) fine, so I think you might need to take a look at some of those threads with the digitizer issue and check if others are experiencing the same issues.
Related
Hi guys!
I'm totally new to this forum and I apologize if this issue has been discussed/explained earlier, but here goes:
I recently purchased a new HTC P3600/Trinity , as I have been using Qtek/HTC pocketpc's the last years and have been very satisfied with them. One of the main reasons I bought Trinity was because of the 400mhz Samsung CPU which I thought would be fairly faster than the 200mhz TI CPU on my previous S200. But, what I don't understand is that, when I try to for example play NES games with PocketNES or PocketNester on the Trinity, the emulation runs sooo slow, even with sound disabled. On my S100 and S200, NES emulation was flawless with sound enabled. I have also noticed some other slowdowns when running apps/games as well. Why is this? I do hope this is a bug that can be fixed somehow with a hack/tweak or a rom upgrade.
I am also wondering if there is, per date, any overclocking apps that work with the Samsung 400mhz CPU?
Any help/comments appreciated, thanks!
- Stian
CPU MHz isn't the sole determinant for the overall application performance. I bet you are not running number crunching application in your Trinity, don't you?
Playing games inevitably involves the graphics chip, in Trinity's case - the ATI Imageon chip, which unfortunately is not too well supported by these apps. You don't get decent playback of video until recently.
And speaking about overclock - I still don't see any proper app to really overclock that Samsung CPU....
Alright thanks for the input! I really thought that the previous HTC devices had sort of the same graphics chip. I sure hope there will be software enhanced for the ati chip in the future though. More comments appreciated as well!
Its mainly because of the stupid ATI Accelerator
Please take a look at a wiki. Its a known issue , whenever you play a game (that uses stylus input) , you'll notice that fps drops dramatically but then if you just use the buttons , it works fine..I am not sure why or what. But it seems that ATI Graphics chip is the culprit
Yeah, I've heard about the thing with the touchscreen slowing it down. But even if I'm not even close to using the touch screen, it's already slow..
prasys said:
Its mainly because of the stupid ATI Accelerator
Please take a look at a wiki. Its a known issue , whenever you play a game (that uses stylus input) , you'll notice that fps drops dramatically but then if you just use the buttons , it works fine..I am not sure why or what. But it seems that ATI Graphics chip is the culprit
Click to expand...
Click to collapse
so has there been any fix for this? i know that wm6 certainly doesn't make the situation better.
More comments on this issue is greatly appreciated.. As far as I have experience by now.. Every game and/or application I use that requires holding the stylus to the touchscreen suffers from major slowdowns. . I will definitely send an e-mail to HTC complaining about this issue and I hope that others will do the same. They should really fix this issue in the next ROM release ..
pcprono said:
More comments on this issue is greatly appreciated.. As far as I have experience by now.. Every game and/or application I use that requires holding the stylus to the touchscreen suffers from major slowdowns. . I will definitely send an e-mail to HTC complaining about this issue and I hope that others will do the same. They should really fix this issue in the next ROM release ..
Click to expand...
Click to collapse
You can try XCPUScalar to overclock your device (paid software) http://www.immiersoft.com/, tried it on mine (HTC P3600). Works.
Good luck
pcprono said:
More comments on this issue is greatly appreciated.. As far as I have experience by now.. Every game and/or application I use that requires holding the stylus to the touchscreen suffers from major slowdowns. . I will definitely send an e-mail to HTC complaining about this issue and I hope that others will do the same. They should really fix this issue in the next ROM release ..
Click to expand...
Click to collapse
I haven't used any NES emulators on Trinity - but does it involves the touch screen at all?
If you are talking about raw video performance, I guess those software like emulators will sooner or later support the ATI video chip, which would then provide better video speed.
But I doubt there's any fix from HTC regarding the stylus performance hit problem.
Besides the problem with the touchscreen...have you tried to upgrade to WM 6?
Mine is much faster since the upgrade.
R_S_4 said:
Besides the problem with the touchscreen...have you tried to upgrade to WM 6?
Mine is much faster since the upgrade.
Click to expand...
Click to collapse
Really?
Is it stable and all with the WM6 upgrade? I would prefer a Norwegian WM6 rom though, considering the norwegian special letters and all .. I'll might upgrade to WM6 then, can anyone else confirm this?
simonuca said:
You can try XCPUScalar to overclock your device (paid software) http://www.immiersoft.com/, tried it on mine (HTC P3600). Works.
Good luck
Click to expand...
Click to collapse
What version are you using. According to the developer Samsung support is on his "to do" list and not yet implemented.
Ce said:
What version are you using. According to the developer Samsung support is on his "to do" list and not yet implemented.
Click to expand...
Click to collapse
I thought that too....
http://www.technologyatplay.com/main/forums/thread-view.asp?tid=4868&posts=3&start=1
I'm running PDAVIET's 02.07.07 with Radio 1.46.00.11 and it is absolute stable. Never had any problems with it and the gps works fine too (since the radio update). I have it installed for about 2 weeks...but it is in english.
I've tried a lot of android builds whilst the development has been going on and found that Bangster's 1.4 coupled with Michy's R11 was the best for me with regard to screen sensitivity and keyboard accuracy.
I recently had a dabble with m-deejay's next-gen builds Desire HD/Z etc (which are excellent by the way, credit to him), and found that I was getting a lot of screen bounce, missed button presses and a very frustating keyboard experience (Hastarin R7.1). Pressing and holding the delete key for example would result in keypresses bouncing all over the place, sometimes several keys removed from the delete key. I tried a plain Froyo Sense build and found the same thing, although not quite as bad.
So, I decided to try the bare kernel from Michyprima's R11 (AXI, Desire, OC) on my current Froyo Desire build just to see if it was down to the kernal 100%. Instant bounce removal... keyboard is accurate and now when I press & hold on the home screen, I don't get the screen wobbling from side to side as the software thinks that I'm moving my finger around rapidly.
To recap; it seems like I was getting more bounce with Hastarin's R7.1 than any other, but certainly Michy's R11 (Desire based) is making my phone usable again. It really was bad before.
More messing required methinks... I may re-load the Desire Z build on to my SD card and try R11 to see what it's like. One thing I remember is whilst trying m-deejay's Desire HD 3.1 (which had an Evo kernel IIRC), keyboard bounce was almost non-existant. It wasn't until I changed to D-HD 3.3 that the keyboard became a pain to use (Hastarin R7.1).
Hastarin if you read this, please note this is by no means a dig, I have the greatest respect for all the guys posting builds here, these are just my obvservations.
As with all things Android/HD2 related, YMMV. Your thoughts are welcome.
---------------------------------------------------------------------
---------------------------------------------------------------------
Edit: I've taken a couple of quick videos of m-deejay's brand new 3.4 Desire HD build showing this phenomenon (kernal is huanyu's #21). Replacing the zImage with Michy's R11 virtually eliminates it.
Video 1 - homescreen
Video 2 - keyboard
Could this be Windows ROM related? Might flash another WinMo ROM to see if it's any different.
Edit 2 Sent my HD2 back to HTC today, hopefully for TS replacement... see relevant post here.
Edit 3 Received my HD2 back from HTC's repair department. Problem fixed. No more bouncing Relevant post here.
No-one else with similar experiences?
Me too!
previously was using M-deejay's froyo sense 2.2 and the keyboard was a great improvement from my old stock HD2 Windows keyboard, which was oversensitive and jumps alot, making typing a hassle. I did not have any problems with the froyo sense 2.2 keyboard, it was accurate and sufficiently responsive, and even have my essential chinese input.
However, after the 2.4 version was released, i updated it, and noted that the browser's bookmark crashes. So i though, why not give EVO Sense 1.6 a try?
Btw, i did not realise any problems with the 2.4 keyboard, so it's probably as good as the 2.2 version.
Then i ran EVO sense 1.6, and i feel that the keyboard is different. Firstly it's the additional arrow buttons below, which is useful, and more like the original HD2's keyboard. Then it also has chinese input.
BUT i experience alot of the "bouncing" problems, if not more than my original HD2 windows rom. tried calibrating a few times, and deleting the calibration, but it doesn't help.
i want to emphasize again i am very grateful to all the developers like M-deejay, Hastarin, for developing all these builds that are effectively working. this is likewise, just my observation.
Anyone else? I can't believe it's just us two!
Videos added to 1st post.
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
have the same prob!
yep...and I get phantom touches also.
jaka.erc said:
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
Click to expand...
Click to collapse
What WinMo ROM are you running?
JanssoN said:
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
Click to expand...
Click to collapse
CleanEx DsE GTX 6.5.x
anoschka666 said:
have the same prob!
Click to expand...
Click to collapse
muzicman0 said:
yep...and I get phantom touches also.
Click to expand...
Click to collapse
Try changing your zImage to Michyprima's R11 and post your findings
Major_Sarcasm said:
No-one else with similar experiences?
Click to expand...
Click to collapse
OK ! very common HD2 touchscreen failure! ...ur touchscreen is defective ....there are many threads already on xda regarding this ...but could not be solved because this is a hardware problem ...this even happens in winmo ! here are the youtube videos having same problem
http://www.youtube.com/watch?v=DhhrA3u4rcI
http://www.youtube.com/watch?v=3rJJ1eyM9FM&feature=related
http://www.youtube.com/watch?v=QEHn9CaHFpk&feature=related
http://www.youtube.com/watch?v=hY60I9Z0RU0&feature=related
http://www.youtube.com/watch?v=TSvAlqw6HJw&feature=more_related
http://www.youtube.com/watch?v=6hIE_wV4djs&feature=more_related
and here is my thread about this in detail - http://forum.xda-developers.com/showthread.php?t=745255
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Got it to but not in my homescreen. When I am typing with swype ... When I try to delete a word it will write 10 :X nice feature but its really anoying. But lets wait I thing dev know about it let wait for nand and the bother them with this. I heard It is a long way to nand
coolbeer1990 said:
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Click to expand...
Click to collapse
Thanks for your reply. However, my screen isn't defective as I don't have this problem in Windows and using a different kernel fixes it.
major_sarcasm said:
thanks for your reply. However, my screen isn't defective as i don't have this problem in windows and using a different kernel fixes it.
Click to expand...
Click to collapse
that's great my friend
Well.. i have the same thing in hastarins latest kernel
I dont have this on DesireZ out the box.
I have MDeejay's latest Desire HD build and have this problem, how do I fix it? If I need to replace the Kernel how do I do it? What side effects will it have?
Thanks in advance
keyboard bounce also experienced by me when i am trying to type fast, using hastrin r7.1 as well, maybe is caused by the touchscreen delay?
have you tried keyboard calibration?
in the setting menu ..
it ask you to type that ..lazy brown fox jumps..
it helps me alot.. well some of it i guess
and also try the schrub bartome build. the keyboard is perfect-iphone like. im using this build for day use
I experience the same issue with the new kernel releases. But with hastarin #3 the touchscreen works normally.
Sent from my HTC Vision using XDA App
Hi all,
as stated in the past days by oneplus, a new touch firmware has been released and will be in cluded in 5/15 cm12.1 nightly. this should (i hope so) resolve all the remaining touch issues that affects many opo
Here is the coomit: http://review.cyanogenmod.org/#/c/98287/
05/18: The touch firmware has been reverted to the old one because of battery drain caused by dt2w
sub.
Looks like working very good. Flashing Nightly and screen is more responsible ever sinde the failure occured. waitung für Lord Boefla or slimkat to include it
Tested and feeling much better
bigheadlyf said:
Tested and feeling much better
Click to expand...
Click to collapse
can you please test if two finger on the same X axys are now registered correctly? my opo is through the RMA process so i can't test
Certainly seems to be working for me. Typing fine, and x-axis multitouch is working great.
effry said:
can you please test if two finger on the same X axys are now registered correctly? my opo is through the RMA process so i can't test
Click to expand...
Click to collapse
Yes, working fine for me.....
The question now is.... will be forever?
multi touch on mine phone on x axis is still jerking from time to time
sometimes it works normally, detects 2 fingers, then on the other hand detects one or none
will see how it will perform through the day, but since i made a clean flash, i doubt that it will be better...
I have the grounding issue with my ONE. No problems with higher temperatures though.
I flashes Franco Kernel r43 boot.img on my stock cm12s. Fo rme the issues are gone.
x-axis touching is working good. Swiping texts is finally possible again!
Thanks to synaptics!!
I will probably switch to cm12.1 nightlies again when I have some spare time left.
Any way this could be a flashable zip for all ROMs or is this something that is baked into the ROM/Kernel?
JJHunterx said:
Any way this could be a flashable zip for all ROMs or is this something that is baked into the ROM/Kernel?
Click to expand...
Click to collapse
You can flash Franco's kernel below if you are on CM12s/CM12 (5.0.2). Or the alternative is to flash the 5/15 nightly (5.1) or wait for it to be rolled out OTA.
http://forum.xda-developers.com/showpost.php?p=60747459&postcount=8989
gsmyth said:
You can flash Franco's kernel below if you are on CM12s/CM12 (5.0.2). Or the alternative is to flash the 5/15 nightly (5.1) or wait for it to be rolled out OTA.
http://forum.xda-developers.com/showpost.php?p=60747459&postcount=8989
Click to expand...
Click to collapse
No chance for CM11s? I'm just not a fan of 5.x right now.
JJHunterx said:
No chance for CM11s? I'm just not a fan of 5.x right now.
Click to expand...
Click to collapse
I think you may be in luck! If you take the plunge let us know how you find it.
http://forum.xda-developers.com/showpost.php?p=60755103&postcount=4637
gsmyth said:
I think you may be in luck! If you take the plunge let us know how you find it.
http://forum.xda-developers.com/showpost.php?p=60755103&postcount=4637
Click to expand...
Click to collapse
Nice! Thanks for the link. Flashing now.
I had only mild touchscreen issues so I'll see if it gets rid of them.
I've never had touch issues thus far, but I am a bit disappointed at the fix. Although I do notice a better touch response, the fix isn't a fix and is a workaround. PPPreferences has a huge battery drain (com.qualcomm.display) which basically, like I've seen written somewhere, means they're just keeping an app open to recalibrate the screen constantly.
Spider-Vice said:
I've never had touch issues thus far, but I am a bit disappointed at the fix. Although I do notice a better touch response, the fix isn't a fix and is a workaround. PPPreferences has a huge battery drain (com.qualcomm.display) which basically, like I've seen written somewhere, means they're just keeping an app open to recalibrate the screen constantly.
Click to expand...
Click to collapse
Not for me. Nothing changed in terms of battery usage with today's nightly. Also it isn't even listed under Apps in the battery screen on my device.
This app is only used for post processing (Live Display) and has nothing to do with the new firmware.
I was suffering from pretty bad heat related issues, all gone now.
I just flashed Boeffla-Kernel for CM11s. I can definitely tell a difference. There was one app that I could make it jump when swiping up or down and holding it toward the bottom-middle of the screen, no longer have that issue. I also constantly had trouble with it "clicking" things when all I wanted to do was scroll up or down on something. Have not had that issue since flashing.
AcmE85 said:
Not for me. Nothing changed in terms of battery usage with today's nightly. Also it isn't even listed under Apps in the battery screen on my device.
This app is only used for post processing (Live Display) and has nothing to do with the new firmware.
I was suffering from pretty bad heat related issues, all gone now.
Click to expand...
Click to collapse
Hmm that's pretty interesting then, but I don't seem to be the only one reporting a difference in the CPU time of something which includes the Qualcomm services. We'll see with more usage though.
Do you need root to install?
nokmond said:
Do you need root to install?
Click to expand...
Click to collapse
Yes, until it gets pushed officially, as you need to either flash a custom kernel or the latest nightly.
While using this phone randomly the phone touch seems normal but while playing games like pubg I'm having lots of issues the touch is very slow and screen jumps here and there. Anybody else having this issue? I saw a video which mentioned this issue.
this problem already exists when google update to oreo, this problem is on google source code, so wait for them to fix it, but for some custom rom developer have fix it
@SidDev said:
While using this phone randomly the phone touch seems normal but while playing games like pubg I'm having lots of issues the touch is very slow and screen jumps here and there. Anybody else having this issue? I saw a video which mentioned this issue.
Click to expand...
Click to collapse
Common issue for all oreo phones. Even persists on Marlin and sailfish .. so don't worry man
arthuurro01 said:
this problem already exists when google update to oreo, this problem is on google source code, so wait for them to fix it, but for some custom rom developer have fix it
Click to expand...
Click to collapse
I was worried if it was problem of the device. I hope it gets fixed soon, didn't know it was Oreo related issue.
@SidDev said:
I was worried if it was problem of the device. I hope it gets fixed soon, didn't know it was Oreo related issue.
Click to expand...
Click to collapse
Will be fixed in source.. may be in Android p
anisgvr said:
Will be fixed in source.. may be in Android p
Click to expand...
Click to collapse
Can you give me a link so that I can read more about it? I googled already but couldn't find.
@SidDev said:
Can you give me a link so that I can read more about it? I googled already but couldn't find.
Click to expand...
Click to collapse
I don't remember the source man .. Android police maybe
@SidDev said:
While using this phone randomly the phone touch seems normal but while playing games like pubg I'm having lots of issues the touch is very slow and screen jumps here and there. Anybody else having this issue? I saw a video which mentioned this issue.
Click to expand...
Click to collapse
I feel you man, not only in pubg... It happens when i play Mobile legend or any landscape games with dual finger to play.... really pain in the **, so annoyed by those random touch
@SidDev said:
While using this phone randomly the phone touch seems normal but while playing games like pubg I'm having lots of issues the touch is very slow and screen jumps here and there. Anybody else having this issue? I saw a video which mentioned this issue.
Click to expand...
Click to collapse
Yep, same here brother. For me it was in pubg. For a moment I thought that maybe mine's a defective unit. But turns out it is software issue.
Thank god its the software issue not the hardware/device. The bug really sucks.
---------- Post added at 11:04 AM ---------- Previous post was at 11:03 AM ----------
Instagram, mobile legend, pubg.
try turn on the auto rotate, it works for me
Multitouch bug fix by Google
This issue was to be fixed in June security update. However, Google decided to fix this in May security update itself. OEMs were supposed to merge these changes to utilize it. Now that we've already got May security update without the fix, the only way for X00TD to be rid of this bug is the June security update.
Oreo Multitouch bug
Me too, while playing ping. I thought multitouch problem
Yeah i am having this issue while using phone. Screen stucks and it keep doing up and down and just touch dont work at that time. I got serviced my phone two times but it still persist. At service centre they said there is no issues but in reality it has. Is it a defectIve piece i am using? I am distressed
Has anyone else here played this game on the essential phone? I have a couple of strange glitches. I initially thought they were associated to my original faulty device, but after receiving my warranty replacement that is not faulty the same issues still persist on PUBG Mobile. So I am assuming it's something with this phone in general.
First glitch is some artifacting during the loading screen on the notch end of the phone. I am assuming this is because of the screen resizing to accommodate for the notch. It seems like it starts to attempt to resize the screen a few times in a row every once in a while resulting in what looks like some screen glitching. I've noticed this in other apps while using them too like chrome and OfferUp. Looks like every once in a while the app suddenly attempts to resize back to full screen mode for a split second, then immediately shrinks back down again to cut out the notch area.
Other issue is while using both fingers on the screen at the same time. Moving while aiming for instance it will spin my character around a little bit.
Doesn't display any of this behavior on any other phones I've ever had. I already contacted the publisher of the game but Wondering if anyone else has these issues and knows a workaround.
Android P fixes all of the touch related bugs. Game is running flawlessly on my phone
crixley said:
Android P fixes all of the touch related bugs. Game is running flawlessly on my phone
Click to expand...
Click to collapse
I'm on P also, but I still get the glitch that I got in Oreo
Thomas Cloutier said:
I'm on P also, but I still get the glitch that I got in Oreo
Click to expand...
Click to collapse
Strange, I don't at all. I full wiped and flashed from fastboot though. Did you ota?
So you still have the graphical glitches?
How do I get P?
Also is it possible to force games and other apps to utilize the full screen pace around the notch? As much as I don't like apple I do notice in YouTube videos that it does fully utilize the notch area on the iPhone X.
Alright nevermind found the settings in developer options from YouTube video to force all apps to use the notch area.
crixley said:
Strange, I don't at all. I full wiped and flashed from fastboot though. Did you ota?
Click to expand...
Click to collapse
I flashed the ota through adb, did not factory reset though. I think the issue is involving the multi touch that was broken in and 8.1, and I don't think Google has fixed the issue
Thomas Cloutier said:
I flashed the ota through adb, did not factory reset though. I think the issue is involving the multi touch that was broken in and 8.1, and I don't think Google has fixed the issue
Click to expand...
Click to collapse
Yes they have. Lol I'm using it fine right now.
crixley said:
Yes they have. Lol I'm using it fine right now.
Click to expand...
Click to collapse
Well I'm still having issues with mine
Thomas Cloutier said:
Well I'm still having issues with mine
Click to expand...
Click to collapse
Like I said before, I flashed the full fastboot file, not just the ota. It is fixed completely. You could try that.
Yes! God, I thought I was the only one with the multi touch issue..but I'm too lazy and stupid to get P so I suppose I'm out of luck.
There's a fix for the multi touch glitch bug. It's a magisk module called "Pixel 8.1 multi-touch fix".
Let me warn you, DO NOT install it if you are on the stock essential ROM, because it will fail to boot. It is only safe on AOSP based ROMs. I can only vouch for myself that it works flawlessly with lineage. If you are on stock ROM you'll have to wait until essential releases a fix.
I just read up on it a little. Apparently it's an issue with all phones running 8.1.0 Oreo witch I did not know. My original essential PH1 was faulty, kept crashing and rebooting so I thought this was part of the faulty device.
Looks like they plan to release a fix in June security update.
Nickvanexel said:
I just read up on it a little. Apparently it's an issue with all phones running 8.1.0 Oreo witch I did not know. My original essential PH1 was faulty, kept crashing and rebooting so I thought this was part of the faulty device.
Looks like they plan to release a fix in June security update.
Click to expand...
Click to collapse
So then are you on Android 9 aka P or not?
No. Just going to wait until they release the fix for 8.1.0
i thought the pixel now has the fix from the May patch... maybe our June update will fix this? How is P ? stable enough for daily driver.. cause i like my chicken dinner!!
Sent from my PH-1 using Tapatalk
Incredible... P preview makes this phone amazing.. touch response is way better.. pubg is soooo much more playable.. no more touch issues or screen jumping around.. got me some chicken just a few minutes ago
Sent from my PH-1 using Tapatalk
stinger4321 said:
Incredible... P preview makes this phone amazing.. touch response is way better.. pubg is soooo much more playable.. no more touch issues or screen jumping around.. got me some chicken just a few minutes ago
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The difference is insane right? Night and day. Even if there were any bugs, which I haven't noticed any, I still wouldn't be able to go back I don't think.
Way smoother, all touch bugs fixed, better battery life... What's not to like?
crixley said:
The difference is insane right? Night and day. Even if there were any bugs, which I haven't noticed any, I still wouldn't be able to go back I don't think.
Way smoother, all touch bugs fixed, better battery life... What's not to like?
Click to expand...
Click to collapse
Yep.. only bug I have seen is that wifi isn't on when phone is restarted..
Sent from my PH-1 using Tapatalk
crixley said:
The difference is insane right? Night and day. Even if there were any bugs, which I haven't noticed any, I still wouldn't be able to go back I don't think.
Way smoother, all touch bugs fixed, better battery life... What's not to like?
Click to expand...
Click to collapse
Yep, everything is great for a dev preview. I fixed my PUBG, by just uninstalling, then reinstalling the game. Runs flawlessly