Wikipedia:Reference desk/Archives/Computing/2016 August 6
Computing desk | ||
---|---|---|
< August 5 | << Jul | August | Sep >> | August 7 > |
Welcome to the Wikipedia Computing Reference Desk Archives |
---|
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
August 6
[edit]Pokémon Go not working on my phone
[edit]So Pokémon Go just became available in my country today, and I downloaded it. My phone is an Android phone (Samsung J1) running Android 4.4.4 and is not rooted and has 500 MB of RAM. Unfortunately for me, it keeps crashing on me after the load screen. I've tried various tricks mentioned online but none have worked. Apparently the game requires at least 2 GB RAM in order to work, but some phones with just 1 GB RAM can play the game. Is there nothing I can do to make it run? Narutolovehinata5 tccsdnew 03:49, 6 August 2016 (UTC)
- Probably not. It's possible a newer version of Android may help as Android 5 was supposed to help with low end devices but there are no guarantees. Similarly performance on low end devices (or if the crashing is simply a bug unrelated to the memory) may be improved with future versions of the app but no guarantees. Nil Einne (talk) 09:05, 6 August 2016 (UTC)
- It probably does not matter, but what are the crash symptoms exactly? (Device freezes for a few seconds then stops the application...?) If the problem is a lack of RAM there is not much to be done, but it could be some version compatibility with the OS or whatnot.
- On a side note, 1GB (let alone 2) of RAM sounds enormous to me. From what I have seen, that game includes neither overly detailed graphics nor huge computations... TigraanClick here to contact me 15:20, 6 August 2016 (UTC)
- @Tigraan: It shows the Niantic/TPCi screen for a few seconds, then shows a black screen, then crashes to the home screen. Something is telling me the problem is phone-related since I tested the game on an iPad mini and it works on it. Narutolovehinata5 tccsdnew 22:19, 6 August 2016 (UTC)
- Did it ever do anything other then that? Well anyway, you could uninstall the app and reinstall. There's always a slight chance something has gone wrong, possibly in cache or stored data only but you might as well just start afresh. BTW you do have some free storage space (in main flash not SD) right? I'd recommend always having at least 1GB if possible. If it isn't I'd at least clear 200-300MB if you're having problems. Anyway for the problem you're having I'd say there's a greater probability a newer Android version may help, but still far from guaranteed. Nil Einne (talk) 17:40, 7 August 2016 (UTC)
- @Tigraan: It shows the Niantic/TPCi screen for a few seconds, then shows a black screen, then crashes to the home screen. Something is telling me the problem is phone-related since I tested the game on an iPad mini and it works on it. Narutolovehinata5 tccsdnew 22:19, 6 August 2016 (UTC)
One font style not working in Word for Mac
[edit]Hi, I'm using Word on a Mac running El Capitan.
I have ITC Bookman installed. It has eight variants:
- ITC Bookman Std Light
- ITC Bookman Std Light Italic
- ITC Bookman Std Medium
- ITC Bookman Std Medium Italic
- ITC Bookman Std Demi
- ITC Bookman Std Demi Italic
- ITC Bookman Std Bold
- ITC Bookman Std Bold Italic
On my Windows 7 PC, all of these styles show up and work perfectly. But on my Mac, although they all show up, it's impossible to select ITC Bookman Std Light. If you select it, it jumps straight to Medium. A document already written in Light will show up in Medium.
All the other styles work OK.
The problem doesn't happen in Excel on Mac but it does happen in PowerPoint on Mac.
I've tried restarting, clearing the font cache, uninstalling and re-installing, etc.
Any ideas? Thanks! — Preceding unsigned comment added by Amisom (talk • contribs) 13:23, 6 August 2016 (UTC)
- Did you install it using "Add Fonts" or Font Book?
- Have you tried clearing the font cache with Font NUke?
- Have you read Microsoft's troubleshooting? Apparently, the problem might not have a solution. Hofhof (talk) 18:36, 6 August 2016 (UTC)