search

tmassie / aospx

Automatically exported from code.google.com/p/aospx
0 stars 0 forks source link

Google Play Music 4.3.606.400990 FCs on run on BR4 #82

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Clean Install BR4
2.Install latest Google Play Music from the Play Market
3.Open Google Play Music

What is the expected output? What do you see instead?
Google Play Music should launch. Instead, the app Force Closes.

What version of aospX are you using? And when did the issue first start?
BR4 + InspireMod

Have you performed a full wipe/factory reset? (If not, then do so)
Yes, just today.

Inspire4G or DesireHD? (If Inspire, did you flash Inspiremod?)
Inspire 4g

Please provide logcat ouput and any additional information below.
(logs required or I will discard the ticket.)

Original issue reported on code.google.com by josh.sch...@gmail.com on 18 Jul 2012 at 11:56

Attachments:

GoogleCodeExporter commented 8 years ago 
Additionally, several reviews pointing to this problem occurring on other 
devices, including the Nook Color and HTC MyTouch 4g. May be an app problem 
more than an OS problem.

Original comment by josh.sch...@gmail.com on 19 Jul 2012 at 12:00

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Heres the link to the working 4.1.513 apk until Google releases an update..

http://forum.xda-developers.com/showthread.php?t=1533816

Original comment by robbe...@gmail.com on 19 Jul 2012 at 11:10

GoogleCodeExporter commented 8 years ago

Original comment by robbe...@gmail.com on 20 Jul 2012 at 10:34

GoogleCodeExporter commented 8 years ago 
This problem seems to occur because the system loads a resource from 
"layout-v16".

More info and modified APK's can be found here: 
http://forum.xda-developers.com/showthread.php?t=1799125

Original comment by Rae...@gmail.com on 7 Aug 2012 at 6:45

GoogleCodeExporter commented 8 years ago 
New -> Verified

Until this is actually proven as an app bug, im going to re-label this a rom 
defect so it can be looked into further. Mainly because its reported to work on 
stock Android ICS, so it seems to be something with custom roms only.

Original comment by robbe...@gmail.com on 10 Aug 2012 at 2:10

GoogleCodeExporter commented 8 years ago 
It seems it's an android feature that v+1 resources can get loaded depending on 
the rom codename. (Have not yet been able to verify due to rom crashes).
Details posted on same thread as before: 
http://forum.xda-developers.com/showthread.php?t=1799125

Original comment by Rae...@gmail.com on 11 Aug 2012 at 2:29

GoogleCodeExporter commented 8 years ago 
According to build/core/version_defaults.mk , the default development codename 
is PLATFORM_VERSION_CODENAME := AOSP (which is whats used in aospX, since we 
are based of 'master' branch)..but release builds use PLATFORM_VERSION_CODENAME 
:= REL (ics-mr1 release branch)....which then is used to set 
ro.build.version.codename in the build prop. So are you saying this needs to be 
set as AOSP? or as REL? (which if latest Google Play Music and YouTube work 
fine on stock ICS roms, and im assuming that stock ICS roms are set as REL, so 
shouldnt we need to set it as REL?)

https://github.com/aospX/platform_build/blob/a2c1261e719b4fbac9eee4e348b62936087
0468f/core/version_defaults.mk#L60

Original comment by robbe...@gmail.com on 11 Aug 2012 at 5:08

GoogleCodeExporter commented 8 years ago 
But im compiling a test build now with PLATFORM_VERSION_CODENAME := REL and i 
will let you know how it goes. 

As you mentioned, this cannot just be changed via build.prop, because packages 
are built with this at compile time and when just changing it via build.prop it 
will give the following errors, causing it to erase data

This is a snippet when the build is compiled with AOSP and then trying to just 
change ro.build.version.codename to REL in build.prop..

W/PackageParser( 1757): /system/app/Mms.apk (at Binary XML file line #0): 
Requires development platform AOSP but this is a release platform.

W/PackageManager( 1757): System package com.android.mms no longer exists; 
wiping its data

Original comment by robbe...@gmail.com on 11 Aug 2012 at 5:34

GoogleCodeExporter commented 8 years ago 
Good news..This fixes it. Tested by installing latest Google Play Music from 
the Market and now no FCs. 

Rom devs just need to set PLATFORM_VERSION_CODENAME := REL in 
build/core/version_defaults.mk

Changes have been successfully pushed to ics-devel

https://github.com/aospX/platform_build/commit/a34ffcecc7c237ac9c9e263984f6a74d3
a7c3831

Original comment by robbe...@gmail.com on 11 Aug 2012 at 6:39

GoogleCodeExporter commented 8 years ago

Original comment by robbe...@gmail.com on 16 Aug 2012 at 6:23