[Q] Here Maps not working on either available ROM (now with bug report) - Xoom Q&A, Help & Troubleshooting

Hi guys, this is my first post.
I had a Xoom MZ601 EVEREST with stock 4.0.4 and wanted to update it in order to be able to use Nokia Here Maps (android 4.1+ required). I have tried the EOS stable 3.0, Cyanogenmod 10 stable and 10.1 nightly, using always the proper Gapps pack and following the instructions.
I got everything working well but I cannot even open the here maps app, as soon as I open it it closes immediately, this happens with 4.1.1 and 4.1.2. Best I could achieve is a black screen on CM 10.1 4.2.2.
Any thoughts on where could be the problem?
FYI I tried the last version and two old betas, same results.
Thanks!

I am attaching the debug logs:
here.app.maps-debug.txt (events when trying to open here maps)
before_opening-debug.txt (event before opening here maps, the app it is mentioned in some lines).

Related

Galaxy Note N7000 - CM 9.1.0 - GoogleApps 20120429 - no youtube player

Hi guys,
distro: CyanogenMod 9.1.0-N7000 (build 28/08/12 -mmh, i realize it's a bit early :/ )
gapps: 20120429-signed
Country: Belgium
[Just details]
I've just made the jump to CyanogenMod distribution, everything went fine, thanks to the wiki at cyanogenmod. I have first installed the 9.0.0 and then did the update to 9.1.0 via Rom Manager which offers also gapps 2012-04-29 (the latest signed package for ICS).
[/stop with details ]
Play store, Gmail, G+, Talk work fine, I just can't find Youtube player.
I tried then to install it from google.com->mobile->android but I get the message:
This item isn't available in your country which is strange cause I had it in the stock distribution 4.0.4 from Samsung.
Did I missed a news about Youtube and latest Ice scream sandwish?
And the obvious question, is there a way to recover this app?
Thank you in advance!
a little "UP"
only one

CM 10.2 - First Steps done

CM Team will maybe not support us in 4.3, but i just want to say its possible.
The device is faster than 10.1 and have the exact same bugs.
Camera is ok, but we have a common problem with other ics devices about the screenshot system (used to switch between apps).
Also, we need a compatible gapps package... (or maybe an updated one)
To be continued....

[Q] Google Earth Reinstallation Errors on CM 10.2

Dear Forum Members - This is my first post in XDA and so my apologies if I missed any protocols. I have a Samsung Galaxy S2 International Version. Just like many of you, I got fed up with Touchwiz and flashed CM 10.2 using Cyanogenmod Instaaller. While the performance exceeded my expectations by a huge margin, I am facing one small problem with installation of Google Earth. Since Google Earth is not available in my country through Play Store yet, I usually download the apk and install it. I did the same after moving to CM 10.2 amd installed the old app from my backup, but realised there is an updated version of Google Earth V 7.1.3 available and downloaded the same from a popular tech site. The problem is after I uninstalled the old app, I am unable to install either the new version or the old version. I keep getting the Out of Space: Titanium Backup could not be installed error even though there is lot of space still available. When I faced similar trouble with Titanium Backup Pro earlier, I found online that by deleting /system/app for file Titanium....odex. file and it worked flawlessly. However, I cant find any such file for Google Earth. Can someone please help solve this issue? Thanks in advance
Galaxy S2
Cyanogenmod 10.2 flashed through installer

[Q] Problem running OmniNotes

Is anyone successfully running Omni-Notes ( https://federicoiosue.github.io/Omni-Notes/ ) ?
I'm trying to run it on my N8010 (stock rom) but it just keeps crashing. Since there's no response from the developer I wonder if its just me, or Omni-Notes.
It runs fine on my Moto-G (Android 4.4.2) so it looks like a N80xx or Android 4.2.2 problem.
According to the developer:
Actually it seems to be a Samsung customized firmwares bug.
It happens because Omni Notes uses the new Android 4.2 APIs to implement easily RTL support.
Other firmware when encountering unknow tags used for this purpose simply jumps them. Samsung does not.
Click to expand...
Click to collapse
Is there a solution or workaround for this?

Problems CM 12.1 / 11

Hello all,
read from time with great interest your forums, in particular the section of my (old) HTC Desire S. Thanks to you with great pleasure I can still use my phone, with great satisfaction with newer versions of Android, and the phone responds very well!
Last weekend I took advantage of having to format and restore the factory settings, to try to put something more updated rom, compared to the 10.1 CM (andromadus / flinny ver 22).
Unfortunately I had to retrace my steps and return the same version (build 25) for these problems:
- The CM 13 I did not try...
- Tried the CM 12.1 (nightly 20160320), the system starts and everything seems to work, although with considerable slowness. Unwieldy, although nice to see Lollipop on our old device!
- Tried the CM 11 (nightly 20160305) but unfortunately the system will block continuously in the initial setup wizard (which asks for the language) and are not able to proceed.
- Tried the CM 11 (andromadus / flinny alpha 5), ​​better than the point above, but some apps (like whatsapp) not they set it as a "device not supported" ...
then opted to return on JellyBean and CM 10.1
I apologize if these questions have already been addressed above, I apologize for my English "by Google" (!) and if anyone has any advice is welcome!
Greetings to all

Categories

Resources