Some of you may not notice, but I'm sure there are a few that do. Touch screen responsiveness on custom ROMs or GSI's for Mata is working, but is definitely not as fluid as stock.
Easiest way to tell is just typing on the keyboard and taking note of the shot delay in between touches. For me, I type fast, and this causes spelling mistakes often, because the touch screen (on a ROM or GSI.) doesn't register as it does on stock.
Next is mobile gaming. Touch seems to be a total hit and miss here, and sometimes won't work at all unless one finger is already on the screen. That's not a big deal, because a simple reboot fixes this temporarily. This was fixed a while ago here, if I recall correctly:
https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/198809
Overall I am hoping to find a fix for this touch responsiveness issue. It effects a ton of aspects of this phone and prevents me from staying on ROMs, and resorting to restoring backups to use my phone properly again.
I've tried messing with the build.prop, switching kernels, checked out various forums and attempted things I probably shouldn't have tweaked with, but still have had no luck figuring this out on ROMs or GSI's. Yet on Stock everything functions properly, and touch is no issue.
Can anyone shed any light on this at all? (To clarify there are 2 issues here: general delay in touch, and touch screen not working after a while on games.)
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
lovelock8353 said:
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
Click to expand...
Click to collapse
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
MoistPicklez said:
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
Click to expand...
Click to collapse
Yes,I rooted it. I just checked idc folder of my stock room restore, there are no more but 1 less idc file in the stock rom. I copied the entire idc folder to main storage, restored the gsi room and replaced it. I don't think it makes obvious change,at least did not make the touch screen as good as the stock.
But I did flash elemental-x kernel after flashing gsi. It might have make it better? Maybe I just got used to the sensitivity of gsi but you may try to flash the kernel and replace the folder, see if any changes are noticed.
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
lovelock8353 said:
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
Click to expand...
Click to collapse
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
hx3 said:
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
Click to expand...
Click to collapse
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
lovelock8353 said:
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
Click to expand...
Click to collapse
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Thanks for the input, pretty sure I have already tried the Oct 27th Havoc OS with Neutrino and still had those touch issues with games, but I will give it another shot in case, did you by chance modify a few things with EX Kernel Manager?
hx3 said:
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
Click to expand...
Click to collapse
The status bar is also thin pixelexperience if you care. Aside from the touch screen latency, I haven't noticed any other issue on this rom, so I recommend you give it a try.
Tried Havoc OS paired with Neutrino, and tweaked around with EX Kernel Manager last night for a while, but still had issues with touch on games and keyboard. Literally everything I have tried on custom installations has not helped improve touch responsiveness.
Come on, surely some random dev still lurks these forums who also notices these delays in touch. Would love to help solve this if I knew exactly where to start, and am willing to test or tweak to get this resolved.
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Grip rejection and touch sensitivity aren't available in GSI's unfortunately, but even some ROMs that do include those settings still have delayed touches, and games eventually lose touch until you reboot on occasion.
Compared to stock, the only ROM that had touch working perfectly (like stock) was Kuran's AICP O. I suspect this has something to do with his kernel, but I am just speculating, I can't be sure on that one.
Then even on a GSI with a stock kernel I still get touch issues, so I have a feeling it has something to do either something in /system but then again, I'm still guessing.
But I appreciate the reply thank you for chiming in on this. ?
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
MoistPicklez said:
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
Click to expand...
Click to collapse
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
rignfool said:
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
Click to expand...
Click to collapse
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
MoistPicklez said:
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
Click to expand...
Click to collapse
Sure...
But why for you no have magisk?
rignfool said:
Sure...
But why for you no have magisk?
Click to expand...
Click to collapse
Edit: I think I may have gotten it figured, and at least narrowed down the issue. I Installed Havoc OS 10-27 again with Dec-patched-boot.img, then Neutrino Hercules over that, on both slots, changed CPU to performance and enabled touchboost, then added these lines to my build.prop and rebooted:
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.6
So far so good, touchscreen jank is gone, scrolling isn't bad at all, and best of all games seem way more fluid. Will continue to test it out.
Edit 2: So far so good games haven't lost touch, not even once, games are still fluid and there are literally no touch delays when gaming or typing. So either the kernel (with performance mode and touch boost on) or the entries I added to the build.prop have fixed this finally. Or both. So freakin' happy.
Related
This is a rom I built for myself from cyanogens eclair branch in github.
The kernel is from his github as well w/ the ramhack applied.
Dream only.
Camera does not work. I saw there is a fix but haven't looked at it yet, I don't even use the camera.
Try if you like but Flash at your own risk.
I neither take the credit nor the blame.
None of the work is mine.
First boot takes a bit to settle.
You should probably wipe first.
Two Flavors (purely visual).
No more info for you.
Enjoy or don't
Changelog:
chocolate-1.0.1: fixed bug where contacts pictures didn't show up.
1.1: kernel changes (boot.img only)
1.2: upgraded to 2.1 firmware, removed ramhack
1.2.1: minor changes/additions
1.2.2: fix voice search, minor changes/additions
1.2.3: fix for text showing up black in status dropdown (chocolate)
chocolate-1.0 md5sum d2bb5858a6eda6b2be2e45071b29f799
chocolate-1.0.1 md5sum b413f6f55469dc89325f906a05f86782
vanilla-1.0 md5sum d2975398950052388be365a8d650c4f2
1.1-boot.img
vanilla-1.2 md5sum 40736d8c6bf75adb689f7b8fa34a0ac3
vanilla-1.2.1 md5sum 929f7b26c87ad4e0aa92802231e759c0
chocolate-1.2.1 md5sum e8b1b2284aaff12546436b0ca5c29f1f
vanilla-1.2.2 md5sum 6f68d08e7344761aaf65d184fca7fac5
chocolate-1.2.2 md5sum 2b1e967058dbf0347f9a580d471c855f
chocolate-1.2.3 md5sum 00b8c39be7d7956c05cd4df960f1b9ad
i am going to try this
What's chocolate n vanilla??
big_d093 said:
What's chocolate n vanilla??
Click to expand...
Click to collapse
he said they were just for looks. however, i wouldnt consider flashing this until teh OP gets a CHANGELOG, CAMERA DRIVERS, and a little assurance that this is at least SEMI STABLE, because from reading the first post, i am 100 percent sure it is not stable.
that battery is ugly, no offense, just not my taste
Im going to try it and post my experience about this rom...posting more info on the OP about the roms could be helpfull you know? But anyway, im curious
djluis48 said:
Im going to try it and post my experience about this rom...posting more info on the OP about the roms could be helpfull you know? But anyway, im curious
Click to expand...
Click to collapse
did you flash it yet? if so, is it suitable for every day use in your opinion?
oshizzle1991 said:
did you flash it yet? if so, is it suitable for every day use in your opinion?
Click to expand...
Click to collapse
This rom is fast...its almost stock, except for the look, but all apps are stock..took like 6 or 7 mins to flash and boot the first time.
First weird thing i noticed: For some reason, in some places (like the time on the Notification bar or in the Lockscreen) its showing some weird square symbols.
Synchronization seems to work fine...at least Google contacts...Wifi seems to works fine.
Lockscreen is the rounded one, not the stock Eclair, wich i like more.
Multitouch works weird on the stock browser, but seems to work fine with Dolphin Browser.
When i try to send a SMS with the stock app, it FC.
No camera, its show a blank square, and when you hit "Settings" it FC.
Voice Search FC and Voice Dialer dont work, it dosnt FC tought.
Dosnt have live Wallpaper. 3D apps sucks (as always )
But still, its a FAST rom...not sluggish at all, thats a strong point...and its safe to flash.
I like look, the blue its a little bit too dark and sometimes you can get confused sometimes plus there are some mess up with the letters and background colors. Love the Bootscreen XD.
Tested the Chocolate version of the rom.
Overall look:
Fast and Stable rom, yet lots of things to work, but if he keeps this speed, its going to be a great rom.
For Daily use...i would say NO right now, but when he fix at least the characters mess up, it could be a daily use rom with limitations.
Here are some screenshots:
Hope it helps.
Can you take a pic of the strange square?
Ace42 said:
Can you take a pic of the strange square?
Click to expand...
Click to collapse
Its the numbers, but just in some places.
dumfuq said:
This is a rom I built for myself from cyanogens eclair branch in github.
Click to expand...
Click to collapse
Are you planning on maintaining this rom or is this a one-off venture for you? I love how you and daproy whip out 10mb hacks for CM roms, you kinda made a name for yourself already so I wouldn't mind sticking with this, if there will be updates and refinements.
At any rate.. thanks for your contributions to Android community.
borodin1 said:
Are you planning on maintaining this rom or is this a one-off venture for you? I love how you and daproy whip out 10mb hacks for CM roms, you kinda made a name for yourself already so I wouldn't mind sticking with this, if there will be updates and refinements.
At any rate.. thanks for your contributions to Android community.
Click to expand...
Click to collapse
I will maintain it somewhat as long as I'm using it. Not really sure, cause really I'm just doing it to learn and have fun. I
As to the force closes and box characters, I'm not really sure, its not happening to me.
dumfuq said:
I will maintain it somewhat as long as I'm using it. Not really sure, cause really I'm just doing it to learn and have fun. I
As to the force closes and box characters, I'm not really sure, its not happening to me.
Click to expand...
Click to collapse
Weird, i did a full wipe before flashing the rom...
i was enjoying the very nice and complete theme on chocolate, however i recently switched to hero_over's manup redo. very fast.
upgraded to 2.1
why doesnt chocolate 1.2.1 flash.. i love this rom.. my favorite, no problems but 1.2.1 wont flash..
purpstar said:
why doesnt chocolate 1.2.1 flash.. i love this rom.. my favorite, no problems but 1.2.1 wont flash..
Click to expand...
Click to collapse
You can try 1.2.2 but any info besides "won't flash" might be useful.
I have some questions:
When you say "vanilla" do you mean stock or is it another theme. Have any screenshots?
Have you fixed the camera issue yet?
How many icon columns in the launcher? 4 or 5?
Thanks.
d00m said:
I have some questions:
When you say "vanilla" do you mean stock or is it another theme. Have any screenshots?
Have you fixed the camera issue yet?
How many icon columns in the launcher? 4 or 5?
Thanks.
Click to expand...
Click to collapse
vanilla=stock
camera=no
columns=5 portrait, 6 landscape
Hi everybody,
Here is my first experience with this version :
- Rooted successfuly with OneClickRoot 1.5.5
- GPS : first, it wasn't working properly (slow and not allways working). Then I installed GPS Status (which download an xtra.bin file) and put XTRA option activated in gpssetup2. I also modified the gps.conf file as shown in an other thread. ==> GPS working good and quick ! good news !
*EDIT* : FasterFix doesn't work, application display stays black, no menu scroll down to change location. Octy doesn't improve gps too. Only way for me was to change manually gps.conf.
- Quadrant score : about 350 with some very shorts slow down during test ... I don't know why (I killed every process before runing quadrant)....
- It's smooth to use but ... after "playing" with GPS Status, GPS Test and Maps, system becomes VERY slow during a few minutes, even after killing all process ...
I don't know if LagFix V2 will resolve this problem, I don't think so but I didn't make the test. Quadrant score goes to 570 with LagFix but what is the real effect on the system ?
- No other problem discovered yet but there are a lot of functions to test ...
- Let's see tomorow about battery life ...
What about you ?
Best regards and sorry for my english ...
sambastrakan said:
Hi everybody,
Here is my first experience with this version :
- Rooted successfuly with OneClickRoot 1.5.5
- GPS : first, it wasn't working properly (slow and not allways working). Then I installed GPS Status (which download an xtra.bin file) and put XTRA option activated in gpssetup2. I also modified the gps.conf file as shown in an other thread. ==> GPS working good and quick ! good news !
- Quadrant score : about 350 with some very shorts slow down during test ... I don't know why (I killed every process before runing quadrant)....
- It's smooth to use but ... after "playing" with GPS Status, GPS Test and Maps, system becomes VERY slow during a few minutes, even after killing all process ...
I don't know if LagFix V2 will resolve this problem, I don't think so but I didn't make the test. Quadrant score goes to 570 with LagFix but what is the real effect on the system ?
- No other problem discovered yet but there are a lot of functions to test ...
- Let's see tomorow about battery life ...
What about you ?
Best regards and sorry for my english ...
Click to expand...
Click to collapse
Thanx for the feedback.. also waiting to know the battery life as well.. having hell lot of problem with JPA and JPB (
Installed it a while ago, but haven't noticed any big differences in smoothness or features. No news with GPS either. It still works relatively well after applying modified gps.conf.
The rom still does not include Finnish or Swedish keyboard layouts, but you can install gingerbread keyboard that has them.
Rooting confirmed to work with OneClickRoot 1.5.5.
Also, MusicPlayer.apk from stock android doesn't work anymore. It did with XXJPB, but now it complains about shared libraries missing. Will just have to use the samsung's one.
- It's smooth to use but ... after "playing" with GPS Status, GPS Test and Maps, system becomes VERY slow during a few minutes, even after killing all process ...
I don't know if LagFix V2 will resolve this problem, I don't think so but I didn't make the test. Quadrant score goes to 570 with LagFix but what is the real effect on the system ?
Click to expand...
Click to collapse
This slowness bug after using GPS has was in JPB too. The phone might become completely unusable for few minutes. Reboot of course solves this as well as waiting.
Migzu said:
Installed it a while ago, but haven't noticed any big differences in smoothness or features. No news with GPS either. It still works relatively well after applying modified gps.conf.
The rom still does not include Finnish or Swedish keyboard layouts, but you can install gingerbread keyboard that has them.
Rooting confirmed to work with OneClickRoot 1.5.5.
Also, MusicPlayer.apk from stock android doesn't work anymore. It did with XXJPB, but now it complains about shared libraries missing. Will just have to use the samsung's one.
This slowness bug after using GPS has was in JPB too. The phone might become completely unusable for few minutes. Reboot of course solves this as well as waiting.
Click to expand...
Click to collapse
whats bout music player u got me confused on this one and hows the battery life hows the support for video plyer
desparately want to know abt Battery backup and reading.. is battery indicator fixed? JPA ..JPB dying within 10-12 hours in stead of charged condition.. will wait for further update.
Will flash it this evening when I get home from work Always good to see a new firmware version release I can't imagine they make things worse instead of better
Techie87 said:
Will flash it this evening when I get home from work Always good to see a new firmware version release I can't imagine they make things worse instead of better
Click to expand...
Click to collapse
They make things worse.. and we continue with our download and expectations ...
satyamsit said:
They make things worse.. and we continue with our download and expectations ...
Click to expand...
Click to collapse
You haven't tested it yet Don't blame the firmware before you tested it Then it's allowed
Techie87 said:
You haven't tested it yet Don't blame the firmware before you tested it Then it's allowed
Click to expand...
Click to collapse
m pissed off with the battery issue... hope some improvements can be seen in this build... fingers crossed...
Migzu said:
Installed it a while ago, but haven't noticed any big differences in smoothness or features. No news with GPS either. It still works relatively well after applying modified gps.conf.
The rom still does not include Finnish or Swedish keyboard layouts, but you can install gingerbread keyboard that has them.
Rooting confirmed to work with OneClickRoot 1.5.5.
Also, MusicPlayer.apk from stock android doesn't work anymore. It did with XXJPB, but now it complains about shared libraries missing. Will just have to use the samsung's one.
This slowness bug after using GPS has was in JPB too. The phone might become completely unusable for few minutes. Reboot of course solves this as well as waiting.
Click to expand...
Click to collapse
I'm not having any issues with the stock music player
after flashing and rooting it started to lag out like a mofo but after a restart its been fine ever since.. other than that its been working flawlessly.. now i just have to see how long the battery lasts since i flashed but crossing the fingers
ffcloud2000 said:
I'm not having any issues with the stock music player
after flashing and rooting it started to lag out like a mofo but after a restart its been fine ever since.. other than that its been working flawlessly.. now i just have to see how long the battery lasts since i flashed but crossing the fingers
Click to expand...
Click to collapse
Keep an eye on the battery indicator as well ;-) Hope it doesn't jump from 50 to 15 anymore
Techie87 said:
Keep an eye on the battery indicator as well ;-) Hope it doesn't jump from 50 to 15 anymore
Click to expand...
Click to collapse
Will do.. also one thing i noticed is swype isn't set as a default so you'll see the stock layout at first.. remember seeing some post somewhere about swype not being in this build and assuming it didn't come with it but no worrys just have to change the default
ffcloud2000 said:
Will do.. also one thing i noticed is swype isn't set as a default so you'll see the stock layout at first.. remember seeing some post somewhere about swype not being in this build and assuming it didn't come with it but no worrys just have to change the default
Click to expand...
Click to collapse
This was the case in all previous firmwares as well? Swype was never the default input method for me. Talking about Swype: does it respond quick to the word you swyped? Because With JPA/JPB I always had to wait a few seconds after swyping a word before it would appear on the screen.
Techie87 said:
This was the case in all previous firmwares as well? Swype was never the default input method for me. Talking about Swype: does it respond quick to the word you swyped? Because With JPA/JPB I always had to wait a few seconds after swyping a word before it would appear on the screen.
Click to expand...
Click to collapse
Could have been because my phone didn't clear my old settings when i reflashed.. and nope swype doesn't seem to have any kind of delay on the words.. at least not when it finds the exact word.. if it finds multiple words it has a slight delay tho
ffcloud2000 said:
Could have been because my phone didn't clear my old settings when i reflashed.. and nope swype doesn't seem to have any kind of delay on the words
Click to expand...
Click to collapse
Nice, hope this is the case with the dutch dictionary as well, cause right now, I think the dictionary is causing this delay.
Techie87 said:
Nice, hope this is the case with the dutch dictionary as well, cause right now, I think the dictionary is causing this delay.
Click to expand...
Click to collapse
Swype version is 2.8.50.12867
ffcloud2000 said:
Swype version is 2.8.50.12867
Click to expand...
Click to collapse
Yeah that's still the same version .. But maybe there was an underlying problem. At least, I hope so
ffcloud2000 said:
Could have been because my phone didn't clear my old settings when i reflashed.. and nope swype doesn't seem to have any kind of delay on the words.. at least not when it finds the exact word.. if it finds multiple words it has a slight delay tho
Click to expand...
Click to collapse
That's what I mean And this issue is Froyo only.. I don't have this problem on Eclair.
guys is it worth it to flash to JPF i have jpa/jpb hybrid installed at present and am not facing any issues and will only flash if JPF will bring some major development, so what is your opinion?
P.S DONT YOU GUYS THINK THIS FORUM NEED A CLEAN UP NOW TOO MANY USELESS THREADS LYING AROUND SOME ONE CONTACT ADMN.
How about the phone call pause/blank after every 3secs... Is this fixed?
Test build here:
http://buildbot1.basketbuild.com/~tdm/testroms/aokp_apexqtmo_tdm_build1.zip
md5=89956b113ec67cb9a12496b3d81ac361
Please give it a shake-out and let me know if anything is missing. I'll be submitting for official AOKP support once everyone's reasonably happy with it.
tdm said:
Test build here:
http://buildbot1.basketbuild.com/~tdm/testroms/aokp_apexqtmo_tdm_build1.zip
md5=89956b113ec67cb9a12496b3d81ac361
Please give it a shake-out and let me know if anything is missing. I'll be submitting for official AOKP support once everyone's reasonably happy with it.
Click to expand...
Click to collapse
Everything seems to work fine, I can't test everything of course but the thing I try work fine.
Thanks for your work
I'm seeing a persistent "select keyboard layout" notification. Haven't seen anything else yet.
tdm said:
I'm seeing a persistent "select keyboard layout" notification. Haven't seen anything else yet.
Click to expand...
Click to collapse
When you touch you have to select as physical keyboard apexq qwerty and the message dissapear, its a known "issue".
The weird thing is why have two physical keyboards to select. I set twice as I said and never see this notification again
The notification was able to be dismissed.
tdm said:
The notification was able to be dismissed.
Click to expand...
Click to collapse
why have 2 aokp threads when it could of just been transfered over or discussed....bad lack of communication can lead to stepping on peoples toes
REV3NT3CH said:
why have 2 aokp threads when it could of just been transfered over or discussed....bad lack of communication can lead to stepping on peoples toes
Click to expand...
Click to collapse
I suppose. But the other thread had a few posts and then seemed to die. Which made it clear to me that I'll be the official aokp maintainer, at least for a while. So this is intended to switch to an official build discussion thread.
tdm said:
I suppose. But the other thread had a few posts and then seemed to die. Which made it clear to me that I'll be the official aokp maintainer, at least for a while. So this is intended to switch to an official build discussion threat.
Click to expand...
Click to collapse
either way wouldnt of minded handing it over if you were gonna maintain for it....tbh i'm only gonna be keeping liquid smooth, plain andy, and bringing in AICP...all the others are up for grabs
REV3NT3CH said:
either way wouldnt of minded handing it over if you were gonna maintain for it....tbh i'm only gonna be keeping liquid smooth, plain andy, and bringing in AICP...all the others are up for grabs
Click to expand...
Click to collapse
It's good to see AOKP on this device. If I recall, the previous build ran well but seemed to die off from lack of interest. No matter who maintains this - I hope it catches on. The Relay is a good device and deserves to see some love.
Alright the changes are in progress for official AOKP support. Check gerrit.aokp.co if you are a developer or just curious. I'll try to fix the keyboard notification and double check everything, then submit the changes. apexq should be in the next official nightly.
tdm said:
Alright the changes are in progress for official AOKP support. Check gerrit.aokp.co if you are a developer or just curious. I'll try to fix the keyboard notification and double check everything, then submit the changes. apexq should be in the next official nightly.
Click to expand...
Click to collapse
I noticed something with keyboard backlight, don't turn off when you open it unless you touch any key on it, you can look at it too
Any updates to this? I like AOKP, but the last post was ten days ago :/
Nervous on taking the plunge.
Dirk merged the changes so it's official. Just waiting for the next official build. I just started true nightly builds for select devices on basketbuild a few days ago. Here's the same for apexq: https://s.basketbuild.com/devs/tdm/nightly/aokp-4.4/apexqtmo/
tdm said:
Dirk merged the changes so it's official. Just waiting for the next official build. I just started true nightly builds for select devices on basketbuild a few days ago. Here's the same for apexq: https://s.basketbuild.com/devs/tdm/nightly/aokp-4.4/apexqtmo/
Click to expand...
Click to collapse
Holy crap, I am LOVING this rom! I only found a few minor issues:
-Cannot change the vibrate for incoming messages. I usually have multiple short selected
-Typing out emoticons doesn't turn them into emoticons -p)
-The tiles come out kind of awful. If I set up a good configuration in landscape, you can hardly see them in portrait. Need an option to fit the tiles to one screen instead of simply "4 per row"
TPMJB said:
Holy crap, I am LOVING this rom! I only found a few minor issues:
-Cannot change the vibrate for incoming messages. I usually have multiple short selected
-Typing out emoticons doesn't turn them into emoticons -p)
-The tiles come out kind of awful. If I set up a good configuration in landscape, you can hardly see them in portrait. Need an option to fit the tiles to one screen instead of simply "4 per row"
Click to expand...
Click to collapse
I think there are exposed modules that can fix both of these issues. Not sure about the emoticon thing tho.
tdm said:
Dirk merged the changes so it's official. Just waiting for the next official build. I just started true nightly builds for select devices on basketbuild a few days ago. Here's the same for apexq: https://s.basketbuild.com/devs/tdm/nightly/aokp-4.4/apexqtmo/
Click to expand...
Click to collapse
Everything works fine except the same error trying to enter mobile network settings and I notice battery drains a lot in this new release, the other was good
falle21 said:
Everything works fine except the same error trying to enter mobile network settings and I notice battery drains a lot in this new release, the other was good
Click to expand...
Click to collapse
Seems about the same to me. I'm at 76% after 3 hours. I'm not actively using my phone though.
I don't know what I was doing, but it dropped a good 20% over the next hour after that. Wut?
Nice ROM. Good job.
Questions:
1. Is there a way to set 180-degree rotation mode, in addtion to the others? All I've been able to find is rotation on/off, with "on" always providing 0, 90, and 270.
2. Is there a way to prevent the "Select keyboard layout" notification from showing up at every restart? I already have "sec_keypad" with "ApexQ QWERTY - Relay keypad" selected by default.
Thank you very much.
.
HippoMan said:
Nice ROM. Good job.
Questions:
1. Is there a way to set 180-degree rotation mode, in addtion to the others? All I've been able to find is rotation on/off, with "on" always providing 0, 90, and 270.
2. Is there a way to prevent the "Select keyboard layout" notification from showing up at every restart? I already have "sec_keypad" with "ApexQ QWERTY - Relay keypad" selected by default.
Thank you very much.
.
Click to expand...
Click to collapse
2. You have two to set with apexq qwerty, if you set both as default never see the message again.
falle21 said:
2. You have two to set with apexq qwerty, if you set both as default never see the message again.
Click to expand...
Click to collapse
Oh, OK. Thank you very much.
.
Q&A for CyanideL 02-24-2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CyanideL 02-24-2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Im a noob
.
I have installed twrp and rooted my device
i'd like to install this costum rom, currently i'm on cm11s stock (xnph05q)
however, can i just flash the rom or i should install cm 12 first?
.
Thank you
thomas.bonn79 said:
Im a noob
.
I have installed twrp and rooted my device
i'd like to install this costum rom, currently i'm on cm11s stock (xnph05q)
however, can i just flash the rom or i should install cm 12 first?
.
Thank you
Click to expand...
Click to collapse
Before posting, please use the forum search and read through the discussion thread
Click to expand...
Click to collapse
How is this so difficult to understand? If you can't follow the basic instructions in the OP of the ROM thread then you would be better off leaving your phone alone.
You must be on the latest firmware. You can acquire it by flashing an official CyanogenMod 12.
Click to expand...
Click to collapse
Is this same as blisspop ??.. I see most of the bugs similar to the ones I faced in bliss... Strange...but kuddos to the team for the optimization....
Is anyone having issues with audio on CyanideL? I tend to get brief moments of 'static' when listening to music. Just little fuzz/buzz moments which last half a second or less, appearing to happening at random. Strange thing is that this happens on Spotify Premium and in Poweramp with good quality Ogg music, but not in Soundcloud... Just need to check whether it's the ROM/software or my phone as this OPO is less than a week old!
Edit: appears to be happening on both headphone and loudspeaker output.
No issues with music downloaded to phone I don't use spotify I stream to blue tooth and Use wired head phones no issue.
david72262 said:
No issues with music downloaded to phone I don't use spotify I stream to blue tooth and Use wired head phones no issue.
Click to expand...
Click to collapse
Thanks for the reply.
This seems like a hardware issue then. I suppose I could try and revert to stock and see if the issue persists to be sure of that. I just don't want to put up with faulty audio for the next year and a bit!
xela-yuki6 said:
Thanks for the reply.
This seems like a hardware issue then. I suppose I could try and revert to stock and see if the issue persists to be sure of that. I just don't want to put up with faulty audio for the next year and a bit!
Click to expand...
Click to collapse
I seem to have a similar issue with this. I was watching Netflix or twitch and audio stutters or makes a weird noise randomly.
BlackHoleSlam said:
I seem to have a similar issue with this. I was watching Netflix or twitch and audio stutters or makes a weird noise randomly.
Click to expand...
Click to collapse
That's exactly how I'd describe it actually, it's a bit of a stutter. I wonder if anyone else is having a similar issue. I'll download the stock firmware and flash that I think...
xela-yuki6 said:
That's exactly how I'd describe it actually, it's a bit of a stutter. I wonder if anyone else is having a similar issue. I'll download the stock firmware and flash that I think...
Click to expand...
Click to collapse
Okay I seem to have fixed it. I disabled boefella kernel sound affect and audio fx app is disabled. I also raised my cpu and gpu speeds in the boefella kernel settings since I was underclocking.
Okay, sorry if this is a dumb question but how do you get the lock screen and desktop to have the same wallpaper? I've played around in the settings but can't seem to find it.
How is battery life on this ROM? Any bootloop when using themes?
No boot loops battery is good.
No Sim Signal
Hey guys, flashed CyanL in the Morning.
I come from 5.0.2 with the latest cm firmware, but i get no signal.
Any Ideas?
Dirty Flash
hi, can i dirty flash RC10 over RC 9.7? or do i need to clean install?
System UI Crash
I am getting a system UI crash whenever i am using the phone and i get a notification on Hike Messenger. No crashes whatsoever with any other app. Any ideas?
Also, kudos to @mr-cook for the great ROM. Most stable 5.1 ROM i have used.
First of all thank you for this amazing ROM. It's perfect for my needs.
With clean flash, oxygen modem, no xposed & stock kernel i found few problems:
- For me screen off gesture for flash is not working, but for camera is working as expected
- Also for options to disable privacy guard notifications, it still show notification. So for now i need to hide it one by one.
- And the last thing, i don't know if it's from the ROM or anything else. But for me the cLock widget font for the clock is too small, even after i resized it.
I hope you can take a look for my problems, if there's anything that i can provide please tell me.
And also i have a feauture requests to have options to disable power menu in secure lockscreen. Like the options for quick settings.
Other than that, eveything works perfectly and i believe this is the perfect ROM for me, no FC and very stable.
Once again thank you @rogersb11 @mr-cook @TheGeekyNimrod
Audio FX
Its my first post on XDA, this ROM is beautiful and i also got the previus versions. but with this last, the Audio FX app doesnt work for me. i do a clean installation wiping all .... thanks
Great ROM!
I just started using this ROM since yesterday on the recommendation from my friends on the OnePlus forums.
I've tried quite a few known ROMs out there and am really impressed by this one.
The only feature I am missing is having the option of selecting Priority Only on the sound panel in the power menu or having a tile for it in the quick settings. Aside from that, this ROM has everything one can imagine .
Great job guys! @rogersb11 @mr-cook @TheGeekyNimrod
Kernel Mods
Hi @rogersb11 @mr-cook @TheGeekyNimrod
If you are working on updating the kernel, please consider adding sound tweaks to boost speakerphone. On the OnePlus One the speakerphone volume is really low when using it for a phone call, and the tweak in AK kernel helps it.
I love your ROM, but unfortunately have to use to with AK just because I need this tweak.
Thanks!
Since most of us are pulling their hair out trying to fix this issue. I'd like to share what I did to my Poco F1.
Believe me, I tried everything and nothing works with the FTS panel. So I found a workaround and this is more of blocking the area where ghost touch occurs. It's like creating a DEAD ZONE.
UPDATE: Here's what I use.
- MIUI 10.3.7.0
- POCOF1Global_9.5.25-ven-firm.zip
- kernel-beryllium_global_9.5.25-ak2.zip
- FDE.AI Module from Magisk (search and install it directly in Magisk)
- Build.prop
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
ro.ril.enable.a52=1
ro.ril.enable.a53=0
debug.sf.hw=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
persist.sys.ui.hw=1
view.scroll_friction=10
debug.composition.type=gpu
debug.performance.tuning=1
touch.deviceType=touchScreen
touch.orientationAware=1
touch.size.calibration=diameter
touch.size.scale=100
touch.size.bias=0
touch.size.isSummed=0
touch.pressure.calibration=physical
touch.pressure.scale=0.001
touch.orientation.calibration=none
touch.distance.calibration=none
touch.distance.scale=0
touch.coverage.calibration=box
touch.gestureMode=spots
MultitouchSettleInterval=1ms
MultitouchMinDistance=1px
TapInterval=1ms
TapSlop=1px
Click to expand...
Click to collapse
*Much better build. I even forgot to apply my dead zone and still played flawlessly.
How to create a DEAD ZONE:
1. Install Partial Screen PRO (it's a touch blocker). You can find it on play store. There's a free one but expires within 3 days.
2. Download the Notch Killer v2 module and install it in your Magisk. Reboot.
3. Go to developers options, simulate a display cutout and select 'Notch Killer'. (Why notch killer? Partial Screen doesn't use the notch space where ghost touch occurs. Notch killer will force it to use the space.)
4. Open Partial Screen, Apply permissions (You can cancel the auto analysis by pressing double back.)
5. Add Manual Region and create an area on your Notch. You can adjust it as you like, change color, or make it transparent at Area Manager.
6. Start Manual Service
7. PROFIT.
Click to expand...
Click to collapse
*Please take note that this build and workaround will NOT FIX the ghost touches entirely but will minimize it greatly.
Use it free!
PPPon said:
Since most of us is pulling their hair out trying to fix this issue. I'd like to share what I did to my PocoF1.
Believe me, I tried everything and nothing really works with FTS panel. So, this is more of a blocking the area where ghost touch occurs. It's like creating a DEAD ZONE.
I'm using the latest Global MIUI with Latest Optimus Drunk Kernel (use this to minimize the ghost touch and will make it occur only at the notch) and Magisk installed.
1. Install Partial Screen (it's a touch blocker). You can find this on play store and it's not free. (Believe me, it's more worth it than buying a new display panel)
2. Download the Notch Killer v2 module and install it in your Magisk. Reboot.
3. Go to developers options, simulate a display cutout and select 'Notch Killer'. (Why notch killer? Partial Screen doesn't use the notch space where ghost touch occurs. Notch killer will force it to use the space.)
4. Open Partial Screen, Apply permissions (You can cancel the auto analysis by pressing double back.)
5. Add Manual Region and create an area on your Notch. You can adjust it as you like, change color, or make it transparent at Area Manager.
6. Start Manual Service
7. PROFIT.
There you go. That's how I enjoy my games now. And it's pretty amazing that Notification is still accessible through notch even tho I blocked it.
Click to expand...
Click to collapse
I am using your guide. It seems my problem is solved 80℅. I will update my post after some day and experience
But there is no need to buy this app. The free version can be useful as well.
Yeah sometimes it drops my controls when there's too much ghost touch happening that's why it will not entirely fix the issue but it will improve your gameplay alot.
There's a free one but it will expire in 3 days after using. There's a hidden subscription somewhere in the settings.
Thanks for the tutorial. This has been bugging me for a month. It's a good work around for now.
Glad it works for you. It's really a bummer with our fts panel. At least now you can try and experiment with other roms or kernels and see what's best for your phone.
What's weird is that it hasn't been a problem before which points the finger at a software issue. This gives me hope that it could be resolved through a new release of touch drivers for fts panels but I fear xiaomi is not going to spend time on that. Poco is going out of production.
I feel you. I never had problems before for 3 months after buying this unit. After so many updates and still not fixing the issue, I lost faith to POCO F1 devs.
Heads up! I updated my current build. You can try that and tell me if it works better for you too.
fix FTs_ts only devloper
thanks to many brother best friends, we are both on the FTs screen. I'm also looking for this bug fix.
Why is devloper xioami pocohone f1 so slow? I am disappointed with all this
---------- Post added at 08:41 AM ---------- Previous post was at 08:31 AM ----------
brother, which type of global version are you using MIUi for? thank you by replying to save FTs_ts only
Going back to arter kernel r6 solves it for me, showing that it is an issue with touch drivers. I'll try to find out exactly which driver that is.
mandala04 said:
thanks to many brother best friends, we are both on the FTs screen. I'm also looking for this bug fix.
Why is devloper xioami pocohone f1 so slow? I am disappointed with all this
---------- Post added at 08:41 AM ---------- Previous post was at 08:31 AM ----------
brother, which type of global version are you using MIUi for? thank you by replying to save FTs_ts only
Click to expand...
Click to collapse
I'm using the MIUI 10.3.7.
jackiass said:
Going back to arter kernel r6 solves it for me, showing that it is an issue with touch drivers. I'll try to find out exactly which driver that is.
Click to expand...
Click to collapse
I'll test that later and see if it fix mine. Thanks for letting me know!
Edit: The kernel lags too much on my phone when sending a 5 or more touches and then restart itself. What ROM are you using?
PPPon said:
I'm using the MIUI 10.3.7.
I'll test that later and see if it fix mine. Thanks for letting me know!
Edit: The kernel lags too much on my phone when sending a 5 or more touches and then restart itself. What ROM are you using?
Click to expand...
Click to collapse
Havoc
Try Optimus_Drunk_Beryllium-20190826_2.
jackiass said:
Havoc
Try Optimus_Drunk_Beryllium-20190826_2.
Click to expand...
Click to collapse
does havoc split mode works the same way as from miui? im playing an mmorpg too using 2 accs on split, all of the rom i tried cannot play 2 games at the same time. one will always be paused.
i tried that too, but 20190820 works better for my phone.
I don't know if it would be a thing for you, but hiding notch solves it without needing to install third party apps.
For me, I'm using franco latest kernel, reloaded-caf and notch is enabled. I'm getting ghost touches but only a few per day, because it seems the below build prop add-ins does something close from what OP reports
Code:
********************
touch.presure.scale=0.001
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
ro.ril.enable.a52=1
ro.ril.enable.a53=0
persist.sys.ui.hw=1
view.scroll_friction=10
debug.composition.type=gpu
debug.performance.tuning=1
# advanced touch settings
touch.deviceType=touchScreen
touch.orientationAware=1
touch.size.calibration=diameter
touch.size.scale=1
touch.size.bias=0
touch.size.isSummed=0
touch.pressure.calibration=physical
touch.pressure.scale=0.001
touch.orientation.calibration=none
touch.distance.calibration=none
touch.distance.scale=0
touch.coverage.calibration=box
touch.gestureMode=spots
MultitouchSettleInterval=1ms
MultitouchMinDistance=1px
TapInterval=1ms
TapSlop=1px
Vinnom said:
I don't know if it would be a thing for you, but hiding notch solves it without needing to install third party apps.
For me, I'm using franco latest kernel, reloaded-caf and notch is enabled. I'm getting ghost touches but only a few per day, because it seems the below build prop add-ins does something close from what OP reports
Click to expand...
Click to collapse
Thanks for the advice. I already found this solution but was hoping to keep the notch. The first work around from OP is still giving me issues so I'll guess I'll be notchless until xiaomi solves this (if ever).
latest rom fixed the touch problems for me
Which Rom?
jackiass said:
Which Rom?
Click to expand...
Click to collapse
10.3.7.0
UltraSphinx said:
latest rom fixed the touch problems for me
Click to expand...
Click to collapse
fts panel?
Well, I don't like miui so using it is not a thing to me. Tbh, I think that this fix may only come via Android 10 as I'm quite skeptical about then releasing another pie update
Just tried Twisted-F1-NVT8.12.10-V7.0-B531. It's only been 5 minutes but so far no issues.
PPPon said:
Yeah sometimes it drops my controls when there's too much ghost touch happening that's why it will not entirely fix the issue but it will improve your gameplay alot.
There's a free one but it will expire in 3 days after using. There's a hidden subscription somewhere in the settings.
Click to expand...
Click to collapse
I am using free version. And at day 5 its still working fine
jackiass said:
Just tried Twisted-F1-NVT8.12.10-V7.0-B531. It's only been 5 minutes but so far no issues.
Click to expand...
Click to collapse
I flash it. Didn't worked for me