Hi,
I'm using Paranoid Android (latest BETA3) and Mokee kernel, but this problem happened to me on EPRJ CM and on Omni too (Android 4.3) and on all other kernels too.
The thing is that all my calls get answered automatically on speaker (if someone calls me, not if I call someone), I first thought that it was an Xposed Framework problem but after deactivating it I still have the bug. I also thought it could be a Viper4Android one, but without installing it, it remains.
Anyway, if you have an idea about what can be causing it please reply. If there's no way to fix it, can I install CM RIL on PA (although I prefer EPRJ RIL).
Thanks in advance
SOLVED: I was using a profile app (similar to CM profiles and it was causing it), sorry opening the thread but it was turning me crazy.
Hello!
I'm new in the forum and also in Xposed. I have a gt-i8160 with a custom ROM called Mokee (4.2.2). Okay, I know it's not the best ROM by far, but I had a problem with another one and just installed it to get through temporally.
Now, I installed last version of Xposed yesterday and downloaded some modules. Didn't get any kind of error, it just went as expected. But after checking it many times, I noticed that it's not working. Tried with other modules, which didn't work as well.
What can I do? Is there any way to solve it?
I was wondering if installing another ROM like cyanogenMod10.2 would solve the problem. Could you guys give me your point of view, please? As I'm new in this world I dunno many things
Thank you :victory:
Not all modules support all ROMs. So you might just have picked some that don't support yours. Try one that will give you obvious results and check in the "logs" section in Xposed Installer whether the module has been loaded and whether there have been any errors.
Using a different ROM can definitely make a difference, but check first if it's supported on your device.
Solved!
Okay I found what was wrong with it!
I actually have version r4 of Mokee, and searching on the internet I noticed that this version doesn't support Xposed Framework.
Mokee version r7 supports it perfectly, but I think I'm going to give a try to CyanogenMod 11 on my gt-i8160
Just saying in case someone has the same problem
Thank you!
Hi, since I get my D4 i'm using CM12, but the perfomance is... very poor.
I'm getting a lot of freezes and low ram free... Sometimes lost calls and, in some situations, my D4 vibrates and the sound appear 2/3 seconds after....
What do you think about CM11?
anyone tries other ROMs?
what is the best ROM?
I think that uses the latest Android vers isn't very important...
I really like CM12 but I want a good stability...
thanks
I didn't get any freeze on CM12 (i used nightly edition)
Ofc. you can use CM11, it still works, but don't upgrade system (it automatically install CM12)
Fervi
ferviverus said:
I didn't get any freeze on CM12 (i used nightly edition)
Click to expand...
Click to collapse
really? maybe the freezes could be caused by Xposed framework or Custom OC Kernel....
but I read other users that had similar issues...
What Nightly vers are you using?
Are you using Xposed or custom kernel?
are you using safe slot?
thanks for your reply!
I don't have now CM12, but I used it week ago on CM12-Overclock kernel
But on "normal" slot (idk how to unpack ramdisk.img (all programs gave error)) and without Xposed
Fervi
I don't know why but it seems that wifi works better in stock ROM. My wifi signal usually drops while running CM 10.2.1 (stable one) or LiquidSmooth but runs smoothly on stock ROM
In CM13 and CM13 based ROMs it's impossible to disable one of the sims from the settings menu. Is there any way to disable one of them?
Ok, so someone (Martin_MotoG2014) answered this in another thread. All CM and AOSP are unable to have one sim disabled, the only solution is using a stock based ROM, such as Radium Redefined M.
Does anyone know how to fix the Ok Google voice function in android 7? It only works in the Google app and not everywhere.
tApPeD fROM mY nExUs 6
This works, if not try to do it with an older version of google app, and then update to latest beta
http://forum.xda-developers.com/showpost.php?p=69190540&postcount=82
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Strephon Alkhalikoi said:
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Click to expand...
Click to collapse
Just installed cyanide and it works very well
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Strephon Alkhalikoi said:
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Click to expand...
Click to collapse
No, i don't think so, it runs on aosp too, nitrogen
for example
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Strephon Alkhalikoi said:
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Click to expand...
Click to collapse
i actually think its a google now issue. both my lg k7 and lg blahblahblah both had it working on any screen, then it stopped working, and options disappeared. a few days later, the options reappeared, i enabled them, and now works again on any screen.
I guess I didn't word things quite right, as I meant to say the interaction between the Google app and ROM was causing the issue. Hopefully you're right about it being app related so I can move back to Pure Nexus.
I'll give it a shot... I'm running Chroma MM and it works but not in Nitrogen OS. I think it was working on the sky dragon ROM but I was having corruption issues on boot with it while using multirom.
tApPeD fROM mY nExUs 6
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Strephon Alkhalikoi said:
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Click to expand...
Click to collapse
Sorry to rehash this but it's a bit of a bump. It's actually not Google's fault. OoenGapps made a change back in September, changing HotwordEnrollment.apk. okGoogle anywhere has been broken ever since. It's only happening to AOSP Roms like the person above stated. The maintainers of CM for the 6P are trying to get to the bottom of it to see if they can do anything to fix the issue.
MrBrady said:
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Click to expand...
Click to collapse
Try to freeze the hotword enrollment apk.....I use ROM Toolbox Pro for this. It is a system app.....froze it and then followed the directions around the forums and google assistant worked for me on nitrogen on screen off, it seemed to me to be a little more "finicky" at starting from screen off then on stock, but that could just be me and how my voice training was saved or whatever....good luck