I dont know if it is due to my device being a qualcomm however i cant seem to play any of my games that was previously playable.i have also read that nvidia shield devices are also affected.any help is appreciated thanks
Thread Rating:
android latest builds problems
|
(01-25-2015, 07:30 PM)bobbydazzler1985 Wrote: I dont know if it is due to my device being a qualcomm however i cant seem to play any of my games that was previously playable.i have also read that nvidia shield devices are also affected.any help is appreciated thanks Try build 3950 I find it to be the most stable atm, later builds have problems loading homebrew dols too. A constant i've found is the builds that have problems are the ones that don't display the settings and about tabs properly, the newest builds for instance have the tab columns width set too high instead of just being wide enough to display the text. 01-26-2015, 10:44 AM
(01-26-2015, 04:45 AM)Q8-V08 Wrote:(01-25-2015, 07:30 PM)bobbydazzler1985 Wrote: I dont know if it is due to my device being a qualcomm however i cant seem to play any of my games that was previously playable.i have also read that nvidia shield devices are also affected.any help is appreciated thanks Those pictures are huge, it would've been better to just link to them. The tabs are displaying correctly, they were just changed to use a PagerTabStrip because the previous method was deprecated in Android Lollipop.
I'm still running kitkat for the time being, tried 5361 and now it crashes back to game selection menu everytime I try to use the JIT ARM Recompiler, Interpreter still works as normal, maybe it's trying to run using the JIT ARM64 Recompiler by mistake or something.
01-30-2015, 01:00 AM
It's physically impossible for an ARMv7 device to attempt to run the AArch64 recompiler.
Worst case, which is if you somehow manage to get the INI file to the selection of the AArch64 recompiler, it will drop to interpreter as your CPU core. 01-30-2015, 02:23 AM
Code: 01-29 16:16:14.737 I/ActivityManager(581): Process org.dolphinemu.dolphinemu (pid 23926) has died. 01-30-2015, 02:30 AM
Looks like it's failing to find a stub now.
Probably due to some recent buildbot changes which has made it start building AArch64 native libraries. So unrelated to AArch64, but caused by changes to the buildbot for AArch64. 01-30-2015, 06:53 AM
That log doesn't show what actually caused the crash. The first line says the process died (go back further to see why), then it restarts because one of the Activities is still up, but Binder throws a NullPointerException because it's trying to communicate with the original PID.
01-30-2015, 02:26 PM
Code: 01-29 16:16:01.014 I/ActivityManager(581): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/com.android.launcher2.Launcher} from pid 581 |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)