Android "L" Dev Preview Support

[jaredmorgs]

So, throwing caution to the wind (but not before a nandroid, which I transferred off the device before updating), I successfully installed Android "L" on my tablet.

Overall, the L preview is very stable software. I didn't have any issues with the OS itself. Apps on the other hand were a different story.

Apps that don't currently work (or displayed issues):

• [FIXED] Zen Pinball HD - can't restore purchases - https://forum.zenstudios.com/showthread.php?t=6641 opened.
• [WORKAROUND] SixAxis - Can't start bluetooth stack due to a permissions issue - tried chmod on the file but the issue persists - email sent. Will experiment with using PS3 controller connected by USB cable.
• PinWar - holy moly - all the graphics are completely screwed up when you first run the game. After restarting the game, it works fine.
• Momonga Pinball Adventures - gets to the loading animation and crashes out - emailed Devs and they are onto it.
• Colossatron - the game runs slower and not smoothly. It runs though, but if you are used to playing the game, it is definitely not right (it's like a clock speed issue). Reported to Halfbrick (who are in the same town as me).

Now, I'm sure you're all wondering how TPA plays on the tablet.

Well...








...it's not much different.

I didn't notice improvement with audio streaming, [update] however there is a thing called nuAudio in the developer settings. I've got that set now and will see what happens with audio latency.[/update] Perhaps it was because I was re-installing all my apps at the time. I'm not sure. Maybe this is something developers will need to code into the app to take advantage of the improvements.

 

[MonkeyGrass]

Zen needs to update so that their app will recompile under ART. I've had the same issue with ZP2 and SW not "authorizing" the download since I converted from Dalvik to ART. They are usually pretty up on their stuff so I expect it should be updated shortly. They have to anyways, to get ready for "L" - might as well go ahead and do it now!

 

[Indy99]

Very interesting info Jared. Its very disapointing that it looks like there will have to be a code change to reduce audio lag. Hopefully its something relatively easy like changing which API's get called for audio. Im glad Google is correcting this long running Android problem. Too bad its not an automatic fix though.

 

[jaredmorgs]

Zen needs to update so that their app will recompile under ART. I've had the same issue with ZP2 and SW not "authorizing" the download since I converted from Dalvik to ART. They are usually pretty up on their stuff so I expect it should be updated shortly. They have to anyways, to get ready for "L" - might as well go ahead and do it now!

Ahh, well. That explains the issue then. I had issues waaay back when Android 4.4 was released because I switched to ART immediately. I reported it back then in the Zen Studios Android forum, but nothing has been done yet.

I'll update the post with this observation, MonkeyGrass. Thanks for reminding me.

 

[jaredmorgs]

Zen needs to update so that their app will recompile under ART. I've had the same issue with ZP2 and SW not "authorizing" the download since I converted from Dalvik to ART. They are usually pretty up on their stuff so I expect it should be updated shortly. They have to anyways, to get ready for "L" - might as well go ahead and do it now!

https://forum.zenstudios.com/showthread.php?t=6641 is the thread should you want to weigh in and add support for ART (sooner rather than later).

It will be interesting to see what Xposed does regarding ART being mandatory. The framework is not currently compatible with ART, so a lot of modders will not like that at all (me being one of them).

 

[MonkeyGrass]

https://forum.zenstudios.com/showthread.php?t=6641 is the thread should you want to weigh in and add support for ART (sooner rather than later).

It will be interesting to see what Xposed does regarding ART being mandatory. The framework is not currently compatible with ART, so a lot of modders will not like that at all (me being one of them).

Xposed will have to update, and get with the program (pun intended) like Zen and everybody else. If they truly abandon Dalvik for good in "L", then any dev who wants to release a current-gen android app has to get up to speed with ART, or get left behind. I don't think it'll take too terribly long. Out of all my apps, ZP2 is the only one that won't compile under ART. Seeing as how I rarely play ZP2 on my phone anyways, and my Note 10.1 is still on JB, it's not a big deal to me right now.

 

[jaredmorgs]

Very interesting info Jared. Its very disapointing that it looks like there will have to be a code change to reduce audio lag. Hopefully its something relatively easy like changing which API's get called for audio. Im glad Google is correcting this long running Android problem. Too bad its not an automatic fix though.

I've found something else hidden in the dev settings called nuAudio which is experimental and replaces AwesomeAudio (I'm not making these names up). Google nuAudio for some interesting, and promising specs about the technology.

 

[jaredmorgs]

Zen needs to update so that their app will recompile under ART. I've had the same issue with ZP2 and SW not "authorizing" the download since I converted from Dalvik to ART. They are usually pretty up on their stuff so I expect it should be updated shortly. They have to anyways, to get ready for "L" - might as well go ahead and do it now!

Interestingly, after I reported the issue on Zen Studios forums, the community manager let the devs know and it turns out it was a specific issue relating to the Nexus 7 2013 (probably also in part with the implementation of Google Play Games transition). I am restoring purchases successfully now. And I can confirm Zen HD plays perfectly fine under ART.

If you choose to upgrade to Android L, you have to do a full wipe anyhow. So the issues with app recompile from Dalvik to ART are not present.

 

[MonkeyGrass]

Interestingly, after I reported the issue on Zen Studios forums, the community manager let the devs know and it turns out it was a specific issue relating to the Nexus 7 2013 (probably also in part with the implementation of Google Play Games transition). I am restoring purchases successfully now. And I can confirm Zen HD plays perfectly fine under ART.

If you choose to upgrade to Android L, you have to do a full wipe anyhow. So the issues with app recompile from Dalvik to ART are not present.

Hmmm.. not just confined to Nexus 7. My brand new S5 was having the same issues. After the last update, ZP2 is now working again on the S5 (with ART) but Star Wars Pinball is not - it's FC'ing all over the place before the table can load. My primary issue with ZP is the way they allow multiple, incompatible versions of the same tables for sale - and it all depends on how you do the in-app purchases. For example - on PS3, it doesn't matter *how* you purchase the tables - they all show up in the parent ZP2 app as tables. On Android - they released a separate "Star Wars Pinball" app, and even though the same tables are available as add-ons for ZP2, if you actually purchase them thru the SW app, they will not authorize in ZP2. As a result of this, my first mobile purchase was Darth Vader, and I did it thru the SW app since that's what popped up first when I searched on Play. When I went back later to get a couple more - I found the parent ZP2 app and bought them thru that. Now, I have two separate (large, multi-MB) apps, SW only having one table, and ZP2 having the rest. I contacted customer service and they best they could do was give me some PSN codes for some PS3 tables. I appreciated that and all, but I've still got two separate apps taking up space on my phone, and eating ram - for essentially, ONE app. And now, the SW pinball won't even load. ZP2 will, but I'm still missing a table because of this.

Despite all that, I will probably just buy the dang table (again) in ZP2 to quit having to mess with this. Although, it sure would have been nice had they been able to correct the problem and give me the table in ZP2, instead of futzing around with credits and still leaving me with a messed up installation.

As for Developer "L" - I love the new stuff, but I stay away from the bleeding edge. I won't be upgrading until it's released. I need my phone to work, 100%, first and foremost. I might install it on my old GS3 for kicks, but heck that device *just* finally got KitKat!!

 

[jaredmorgs]

Hmmm.. not just confined to Nexus 7. My brand new S5 was having the same issues. After the last update, ZP2 is now working again on the S5 (with ART) but Star Wars Pinball is not - it's FC'ing all over the place before the table can load. My primary issue with ZP is the way they allow multiple, incompatible versions of the same tables for sale - and it all depends on how you do the in-app purchases. For example - on PS3, it doesn't matter *how* you purchase the tables - they all show up in the parent ZP2 app as tables. On Android - they released a separate "Star Wars Pinball" app, and even though the same tables are available as add-ons for ZP2, if you actually purchase them thru the SW app, they will not authorize in ZP2. As a result of this, my first mobile purchase was Darth Vader, and I did it thru the SW app since that's what popped up first when I searched on Play. When I went back later to get a couple more - I found the parent ZP2 app and bought them thru that. Now, I have two separate (large, multi-MB) apps, SW only having one table, and ZP2 having the rest. I contacted customer service and they best they could do was give me some PSN codes for some PS3 tables. I appreciated that and all, but I've still got two separate apps taking up space on my phone, and eating ram - for essentially, ONE app. And now, the SW pinball won't even load. ZP2 will, but I'm still missing a table because of this.

Despite all that, I will probably just buy the dang table (again) in ZP2 to quit having to mess with this. Although, it sure would have been nice had they been able to correct the problem and give me the table in ZP2, instead of futzing around with credits and still leaving me with a messed up installation.

As for Developer "L" - I love the new stuff, but I stay away from the bleeding edge. I won't be upgrading until it's released. I need my phone to work, 100%, first and foremost. I might install it on my old GS3 for kicks, but heck that device *just* finally got KitKat!!

I think your approach with table management is the only sensible approach, unfortunately.

Separating the tables out was a marketing decision for Google Play search visibility.

Nexus devices are the only ones with preview builds at the moment. All except the Nexus 7 2013 and Nexus 5 require you to build from source.