Hello guys, I'm having a problem.
Since I've tried out a couple of 8.1 Oreo Custom Roms on my phone, I'm having the same problem when typing with Swiftkey.
There is a delay from when I type the letters, to the showing of the predictions and actually the performing of that action. (You can hear that from the sound it produces from the video I've uploaded below).
This happens randomly all the time, but more often when I try to type a bit faster.
I'm using the "Redmi Note 4 Global Version, 4GB ram, 64 GB internal memory - MIDO/Snapdragon" version
I have tried a couple of 8.1 Oreo roms from AOSPExtended, to Cardinal-AOSP, Pixel Experience etc.
I have even opened a bug thread over at the swiftkey support forums, but they don't accept bugs from custom roms:
https://support.swiftkey.com/hc/en-...about-typing-speed-glitch-in-Android-8-1-Oreo
I use the swiftkey a lot and it's pretty important to me. That's the reason that I've been going back to the the 8.0 oreo (Aosp Extended v5.0) every time.
To better see the video, please download it in the pc or the smartphone.
Video: https://drive.google.com/file/d/1pkbo7l4DUxVANlqsmETNzu3NIwjGMkq1/view?usp=drivesdk
Can anyone of you guys who's using a 8.1 oreo rom (and uses the swiftkey) please test the problem?
Please write to this thread if you are having the same issue or not.
Thank you.
I don't have any such problems, always used swiftkey on Oreo and there has never been a issue.
Superblazer said:
I don't have any such problems, always used swiftkey on Oreo and there has never been a issue.
Click to expand...
Click to collapse
Are you talking about the 8.1 oreo or about the 8.0?
Because I don't have any problems in 8.0, just on 8.1 custom roms.
And another thing, please try to use it the swiftkey without the "Key press vibration" and just WITH the "Keypress sound" like the photo I've atached in this reply. I'm saying that because the "Key press vibration" hides this problem.
Can you please test again (If you are on 8.1) like the settings in the picture?
8.1 Oreo, I keep up to date and also shift between roms. I have no such issues with Swiftkey even with the sound.
Superblazer said:
8.1 Oreo, I keep up to date and also shift between roms. I have no such issues with Swiftkey even with the sound.
Click to expand...
Click to collapse
That's weird.
What kind of model do you have? Redmi note 4, 4x?
How manny language do you use at the same time in SwiftKey? And roughly how manny words have you added to your personal vocabulary in SwiftKey?
I'm asking these things Because I have added nearly 9500 words,and mabye that might slow down the typing process in oreo 8.1
I have redmi note 4 4/64gb snapdragon version typing with SwiftKey and no problem here at all 8.1ROM I tried.
2WildFirE said:
I have redmi note 4 4/64gb snapdragon version typing with SwiftKey and no problem here at all 8.1ROM I tried.
Click to expand...
Click to collapse
Which rom have you flashed right now?
And what other 8.1 roms have you tried till now?
been using swiftkey on several 8.1 roms. no issues for me so far.
abhiM525 said:
been using swiftkey on several 8.1 roms. no issues for me so far.
Click to expand...
Click to collapse
What 8.1 rom are you using right now?
Have you seen dhe video and adjusted the sound setting in SwiftKey like above?
Related
How to fix annoying crashing of Google camera in oreo ROMs -> used two ROMs
->Pixel experience 8.1
->NitrogenOS
Build - BSGs latest build of 14-1-2018 (also happens on older other versions by aronova and BSG)
Viewfinder lags and instantly crashes on when clicking a photo. Then it keeps on crashing for 2-3 times.
After that it becomes stable for sometime when used in one go. It doesn't happen in low light conditions
No such crashing issue was witnessed by me on nougat
Also how Can I get slo-mo on my MIDO
Moto camera used to give me nice slo mo videos on Nougat Paranoid
But it doesn't seem to work on Oreo
And the third thing . How to get MIUI camera on an oreo custom ROM.
SamP1298 said:
How to fix annoying crashing of Google camera in oreo ROMs -> used two ROMs
->Pixel experience 8.1
->NitrogenOS
Build - BSGs latest build of 14-1-2018 (also happens on older other versions by aronova and BSG)
Viewfinder lags and instantly crashes on when clicking a photo. Then it keeps on crashing for 2-3 times.
After that it becomes stable for sometime when used in one go. It doesn't happen in low light conditions
No such crashing issue was witnessed by me on nougat
Also how Can I get slo-mo on my MIDO
Moto camera used to give me nice slo mo videos on Nougat Paranoid
But it doesn't seem to work on Oreo
And the third thing . How to get MIUI camera on an oreo custom ROM.
Click to expand...
Click to collapse
You probably have an OmniVision sensor. Old drivers used in custom ROMs are very buggy in Oreo. That’s about to change soon.
For now, look here.
https://forum.xda-developers.com/showpost.php?p=75209096&postcount=273
Thanks man !! I'll check it out soon and report back to you .
Dr. Hurt said:
You probably have an OmniVision sensor. Old drivers used in custom ROMs are very buggy in Oreo. That’s about to change soon.
For now, look here.
https://forum.xda-developers.com/showpost.php?p=75209096&postcount=273
Click to expand...
Click to collapse
Your version seems quite stable to me
But photos are not clicking with flash on.
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
I know our device supports Treble but I didn' t see any successful installation with 9.0 GSI roms, always bootlooping..
phone bootloops so do not try it
TurkO546 said:
phone bootloops so do not try it
Click to expand...
Click to collapse
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Click to expand...
Click to collapse
Do you contacted @phhusson ?
SGH-i200 said:
Do you contacted @phhusson ?
Click to expand...
Click to collapse
I reached out for him in his thread so he should be aware, but I got no answer back probably because I couldn't provide logs of the bootloop (my device isn't unlocked yet). If you got any logs that you could provide him, please do so either in his thread in the treble forums or his github issues page.
https://github.com/phhusson/treble_experimentations/issues
Redcalibur said:
I reached out for him in his thread
Click to expand...
Click to collapse
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
SGH-i200 said:
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
It isn't anything special really. I just asked him if he might know any reason why it doesn't boot for our devices.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device?
Click to expand...
Click to collapse
Redcalibur said:
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
Click to expand...
Click to collapse
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
SGH-i200 said:
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
Click to expand...
Click to collapse
I think nearly every Pie Treble rom is based on this rom, so you got to wait for this one to get updated before the other ones also get updated. Most people are pretty happy with how they perform. We also need to get it to run first before he fixes device specific bugs, so if anyone can get him the logs of the bootloop, please do so.
Pontential solution
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Generic123. said:
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Click to expand...
Click to collapse
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
lilbrat said:
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
Click to expand...
Click to collapse
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Generic123. said:
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Click to expand...
Click to collapse
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Riskypedia said:
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Click to expand...
Click to collapse
You should first flash a stock firmware using newflasher or flashtool, then flash TWRP. Then factory reset or format using TWRP, and flash the GSI(AOSP ROM) and Magisk right after.
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
manxp85 said:
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
Click to expand...
Click to collapse
Are you still using one? Which one do you prefer? Resurrection Remix seems to do it for me.
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
manxp85 said:
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
Click to expand...
Click to collapse
Thanks for the info! Scrollable widgets seem to work for me(using calendar right now). The battery light does not work, like you mentioned. Auto update is also broken. Can't really test Bluetooth car audio right now. I'm bummed out by the lack of auto brightness.
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
manxp85 said:
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
Click to expand...
Click to collapse
Yeah, I'm using this month's build. I'll check car Bluetooth later when I get home.
Hi, its October 2019, and I'm still rocking this phone as my daily driver. With Lineage 15.1 installed it feels brand new and snappy, tho occasionally some apps will crash but nothing major.
What I want is a better camera experience and gcam comes up a lot.
After going round and round through threads I landed on this page
https://www.celsoazevedo.com/files/android/google-camera/
But which latest version of gcam works, using both camera modules and night sight?
The best I can come up with is to use version 6.1, but not exactly sure where to start on that.
Appreciate any input.
davestuarts said:
Hi, its October 2019, and I'm still rocking this phone as my daily driver. With Lineage 15.1 installed it feels brand new and snappy, tho occasionally some apps will crash but nothing major.
What I want is a better camera experience and gcam comes up a lot.
After going round and round through threads I landed on this page
https://www.celsoazevedo.com/files/android/google-camera/
But which latest version of gcam works, using both camera modules and night sight?
The best I can come up with is to use version 6.1, but not exactly sure where to start on that.
Appreciate any input.
Click to expand...
Click to collapse
I use this exact version:
NoHex_MGC_6.1.021_MI8_V2a+
You can enable switching cameras in settings. Everything works fine for me.
jc9896 said:
I use this exact version:
NoHex_MGC_6.1.021_MI8_V2a+
You can enable switching cameras in settings. Everything works fine for me.
Click to expand...
Click to collapse
I don't see that one myself in the link. Is NoHex the dev? I though cstark did the LG ones or has that changed now?
jc9896 said:
I use this exact version:
NoHex_MGC_6.1.021_MI8_V2a+
You can enable switching cameras in settings. Everything works fine for me.
Click to expand...
Click to collapse
Awesome, thanks for your input after a trying again a new day I finally figured it out. And installed Arnovas advanced 1.7 with a g5 config file and it works in most ways
ezzony said:
I don't see that one myself in the link. Is NoHex the dev? I though cstark did the LG ones or has that changed now?
Click to expand...
Click to collapse
I downloaded Arnovas oreo version from here under
Google camera 6.1 section. Version : Arnovas advanced 1.7 from here :
https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/
Then opened the configs link and searched for g5 and downloaded the xml file . I installed the apk and installed the g5.Xml as described on the page.
Most things work, except slow motion..it crashes.
If you go to settings, aux camera switch method.
I changed that to long press, so doing so will switch between wide and normal.
Hope this all makes sense.
Side note.. There's so many options in this Gcam version.
ezzony said:
I don't see that one myself in the link. Is NoHex the dev? I though cstark did the LG ones or has that changed now?
Click to expand...
Click to collapse
If I'm not wrong, that apk comes from cstark.
davestuarts said:
Awesome, thanks for your input after a trying again a new day I finally figured it out. And installed Arnovas advanced 1.7 with a g5 config file and it works in most ways
I downloaded Arnovas oreo version from here under
Google camera 6.1 section. Version : Arnovas advanced 1.7 from here :
https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/
Then opened the configs link and searched for g5 and downloaded the xml file . I installed the apk and installed the g5.Xml as described on the page.
Most things work, except slow motion..it crashes.
If you go to settings, aux camera switch method.
I changed that to long press, so doing so will switch between wide and normal.
Hope this all makes sense.
Side note.. There's so many options in this Gcam version.
Click to expand...
Click to collapse
On the version I suggested (not sure if present on Arnova's mod) there is a setting for switching the slow motion FPS which resolves the crashes.
jc9896 said:
On the version I suggested (not sure if present on Arnova's mod) there is a setting for switching the slow motion FPS which resolves the crashes.
Click to expand...
Click to collapse
Oh excellent. Yes, theres the option to change fps 120, which now works. Thx
incidentally arnova's 1.7 was crashing more than I liked, so I tried arnova's 1.6, which seems more stable.
I wonder what the difference is between your suggestion and the MGC_6.1.021_MI8_V2e.apk listed
I don't understand what the Nohex means, unless thats a developer too.
I'm just waiting for Lineage 16 to be more stable and want to try the next gcam versions.
davestuarts said:
Oh excellent. Yes, theres the option to change fps 120, which now works. Thx
incidentally arnova's 1.7 was crashing more than I liked, so I tried arnova's 1.6, which seems more stable.
I wonder what the difference is between your suggestion and the MGC_6.1.021_MI8_V2e.apk listed
I don't understand what the Nohex means, unless thats a developer too.
I'm just waiting for Lineage 16 to be more stable and want to try the next gcam versions.
Click to expand...
Click to collapse
Cstark is the developer of the one I suggested.
NoHex has something to do with the Hexagon DSP hardware components, though I'm not sure what.
jc9896 said:
Cstark is the developer of the one I suggested.
NoHex has something to do with the Hexagon DSP hardware components, though I'm not sure what.
Click to expand...
Click to collapse
Oh OK. Well, the G5 has the hexagon dsp, unless gcam was causing issues with it, hence a nohex version.
Thx for your input again
jc9896 said:
Cstark is the developer of the one I suggested.
NoHex has something to do with the Hexagon DSP hardware components, though I'm not sure what.
Click to expand...
Click to collapse
Wondering if the "best" (most current/feature-rich) suggestion for the LG has changed in the last 6+ months? I've finally gotten my TMO LG G5 H830 flashed with LOS 17.1 and everything (basically) is working as desired with the one notable exception of no GCam port yet.
Would *really* appreciate any feedback on the current best option?
mgreig said:
Wondering if the "best" (most current/feature-rich) suggestion for the LG has changed in the last 6+ months? I've finally gotten my TMO LG G5 H830 flashed with LOS 17.1 and everything (basically) is working as desired with the one notable exception of no GCam port yet.
Would *really* appreciate any feedback on the current best option?
Click to expand...
Click to collapse
Not very sure, my G5 has gotten some rather nasty battery issues so I'm not using it now. You can try some of the Android 10 compatible apks (7.2.x and up) here:
https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2-beta/
Hi. I'm using Liquid Remix Bloody 10.0.13 (Pie) on my Redmi Note 3 Pro 3/32. This rom and basically all ROMs based on Android 9 have problem with delayed notifications. If someone is sending me message on Facebook Messenger I'm not receiving it. No reaction from phone. At most cases message is displayed when I turn on the screen. I've tried many ROMS based on Android 9 and this happens every time. Yesterday I've tried AOSP based on Android 7.1 and messages was showing instantly. On MIUI everything was good too. I don't want to use this old ROMs, because I have nice version of GCam, which works only in Android 9 (or maybe in Oreo too?). Moreover, in my case AOSP 7.1 has a bug with SIM Carrier - it shows 0 or 1/2 of range.
So my question is: Is there a ROM based on Android 9, which you use daily and have no problem with notifications? Or maybe there is a setting which can "unlock" notifications? I've tried turning off battery optimization for system launcher and Facebook Messenger, but this didn't help.
kamasz222 said:
Hi. I'm using Liquid Remix Bloody 10.0.13 (Pie) on my Redmi Note 3 Pro 3/32. This rom and basically all ROMs based on Android 9 have problem with delayed notifications. If someone is sending me message on Facebook Messenger I'm not receiving it. No reaction from phone. At most cases message is displayed when I turn on the screen. I've tried many ROMS based on Android 9 and this happens every time. Yesterday I've tried AOSP based on Android 7.1 and messages was showing instantly. On MIUI everything was good too. I don't want to use this old ROMs, because I have nice version of GCam, which works only in Android 9 (or maybe in Oreo too?). Moreover, in my case AOSP 7.1 has a bug with SIM Carrier - it shows 0 or 1/2 of range.
So my question is: Is there a ROM based on Android 9, which you use daily and have no problem with notifications? Or maybe there is a setting which can "unlock" notifications? I've tried turning off battery optimization for system launcher and Facebook Messenger, but this didn't help.
Click to expand...
Click to collapse
Did u try Android 9 aex latest selinux enforced ?
Hey there,
Recently I have installed few custom ROMs in my LG V30+ Joan. In my stock ROM (pie) AOD automatically turns off in dark room or when sensor is covered like it is in pocket or something but in these custom ROMs, AoD is available but it does not go off when it is in pocket or covered.
I have also installed (currently using) lineage OS (official one) but it seems it also does not support this function!
So, is there anyway to solve this issue ?
And btw, sorry for my English!
Zeeshan722 said:
Hey there,
Recently I have installed few custom ROMs in my LG V30+ Joan. In my stock ROM (pie) AOD automatically turns off in dark room or when sensor is covered like it is in pocket or something but in these custom ROMs, AoD is available but it does not go off when it is in pocket or covered.
I have also installed (currently using) lineage OS (official one) but it seems it also does not support this function!
So, is there anyway to solve this issue ?
And btw, sorry for my English!
Click to expand...
Click to collapse
Ask on the LineageOS thread to report bug/ask for features
As far as I know, AOD has never worked properly on LOS. I've always used the Always On AMOLED app from the Google Play Store, instead. I believe that it has pocket detection.
Osprey00 said:
As far as I know, AOD has never worked properly on LOS. I've always used the Always On AMOLED app from the Google Play Store, instead. I believe that it has pocket detection.
Click to expand...
Click to collapse
i recently discoverd that its AOD is working alright! After few seconds it goes off not like others custom roms (almost unofficials) that i tried where AOD kept alive even in pocket or when was in dark or sensor was covered.
Yeah, I saw that in the other thread after I already replied to you. I'm on an older LOS, so it's good to hear that AOD works on the newer ones and I may not have to continue using a store app if I update.
Osprey00 said:
Yeah, I saw that in the other thread after I already replied to you. I'm on an older LOS, so it's good to hear that AOD works on the newer ones and I may not have to continue using a store app if I update.
Click to expand...
Click to collapse
I just saw new update of lineageOS 20. Recently i was on 404 where everything was working fine except that you cant install miui zips except gallery. now im tryin to install 411 update and lets see what surprise is there for me.