Related
Hello!
Has anybody managed to get Sygic fully functioning on ICS ROM? I have tried to install Sygic 11.2.1 on Alba and Criskelo ROMs, but without success. It installs, but acts weird, does not show map and usually crashes.
I am running the ICS stunner Rom and i can confirm that sygic is working for me.
Had to go through the trouble of installing the app and download the maps just for you!!
Work great hear too No problems at all
video61 said:
Work great hear too No problems at all
Click to expand...
Click to collapse
No problems on imilkas CM9v3, too.
Thanks!
Problem solved. Just had to buy the correct version, 11.2.6. This one works flawlessly.
Im Glad it worked out for you
I remember seeing a Sygic changelog several weeks ago and there was "Android 4.0 compatibility". So just choose the latest version.
Hi everyone.
I bought galaxy mini GT-S5570 couple of days ago especially to use programs such as viber or nimbuzz. But when I installed viber on my phone I had the problem that i can hear the person who calls but he cannot hear me . Obviously it is not a hardware issue. Coz the mic works perfectly on both phones when using regular calls. I saw a thread on this website on same issue but it was for Galaxy S i9000. But it did not work on my mini.
My device is rooted*
Anybody knows to solve this issue please let me know otherwise this android device will be useless to me.
Thank you
Hi,
This is a member of the Viber R&D team.
We are aware of this issue on some devices, and we are making the required adjustments to the new Viber voice engine.
We will release the new build 2.2 really soon, and we welcome you to keep us updated on the overall performance of Viber.
Let us know if you have any more questions.
Thanks,
Viber team
Hi guys anyway of fixing this problem ?
As we mentioned, we would recommend you to try out the upcoming version 2.2, and let us know if the problem persists on it.
All that while, please note that at this stage we don't officially support custom ROMs (or rooted devices) with Viber. Running Viber on a custom ROM results in various side effects (sometimes total lack of functionality), but we can't afford to support all custom ROMs out there. We are continuously working to adapt Viber to more and more ROMS, but meanwhile - you might want to contact the ROM developer for further support - they may be able to resolve this issue.
Viber Team said:
As we mentioned, we would recommend you to try out the upcoming version 2.2, and let us know if the problem persists on it.
All that while, please note that at this stage we don't officially support custom ROMs (or rooted devices) with Viber. Running Viber on a custom ROM results in various side effects (sometimes total lack of functionality), but we can't afford to support all custom ROMs out there. We are continuously working to adapt Viber to more and more ROMS, but meanwhile - you might want to contact the ROM developer for further support - they may be able to resolve this issue.
Click to expand...
Click to collapse
Hahaha...sorry but why don't support rooted devices?!? what it has to do the root with viber?!?
It is only a hypothetical, official statement that we make. Basically, you are right - it shouldn't have anything to do with Viber at all, however if Rooting is done badly, it could affect the whole phone's functionality.
And with the case of Custom ROMs - it's obvious how it can affect Viber
Viber Team said:
It is only a hypothetical, official statement that we make. Basically, you are right - it shouldn't have anything to do with Viber at all, however if Rooting is done badly, it could affect the whole phone's functionality.
And with the case of Custom ROMs - it's obvious how it can affect Viber
Click to expand...
Click to collapse
For the custom rom's i know is obvious in fact i don't i've asked, but the root don't can be made bad, basically are only some files that give the access to system, than the root it has nothing to do with viber.
I can't instal viber, play store says incompatible device...i downloaded apk from another site but installation doesn't work: application not installed!
oniemjan said:
I can't instal viber, play store says incompatible device...i downloaded apk from another site but installation doesn't work: application not installed!
Click to expand...
Click to collapse
Hi,
We apologize for our late response.
Have you tried the direct link our official HelpDesk? http://bit.ly/rqbZEw
Which device are you using?
Hi Guys !
I have an Optimus Black (P970H).
Recently I installed the Stable version of Cyanogen Mod 10 (10.0.0-p970)
My problem is, using the LG Stock ROM, my GPS works fine.
The version that I'm using is the Brazilian version of the Gingerbread ROM (V20A)
When I installed CM 10, the GPS stoped working.
It doesn't fix do any sattelite and using softwares like GPS Test, shows no sattelites at all.
Tomtom doesn't work at all and Google Maps keeps "Waiting for Position"
I wish to know if there's any fix that I can try.
I know that on the folder /etc resides the configuration files for the GPS (gps.conf and gps_brcm_conf.xml).
Can I use the stock files to make the GPS on CM 10 work ?
If you guys know something that can help me I will be glad.
I'm on Brazil, South America.
Thanks to everyone!
Help!!
I have the same problem! I kinda really need GPS. And I don't wanna reveert back to ICS. Can anybody please help me please!!!
If you used the search, you would find several threads about that...
http://forum.xda-developers.com/showthread.php?t=2205560
On CM10 it doesn't work properly, and it won't work later, as there are no new nightlies of CM10. So nobody is developing this rom (its core).
dcop7 made some files that can help a bit, but it's still far from the performance you get on LG's ICS or CM10.1-based roms.
On CM10.1 though, it's working fine now, as the issues with gps were fixed a few months ago.
You can get some info about the issue here:
http://forum.xda-developers.com/showthread.php?t=2230395
I would suggest you to try CM10.1-based roms, as they improved a lot lately.
Sent from my LG-P970 using Tapatalk 2
no matter what i do i can t install google play services:silly:
i only need it for youtube and mytracks,those apks need this app to work .
i reinstalled my rom,clear caches,data,changed gmail account,searched the web for this case, but no success.2 days before i changed my gmail password,that s the last thing i did,phone was working right till then...
situation starts hitting on my nerves..
anyone can think of something,my mind is stuck!
ROM?
stock light by galaxy mini,and in general i have the same problem in all stock based roms.
& with custom roms like CM!?
i prefer stock based rom,but i should give it a try...
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