Hello
I have been working on removing the touchwiz dependencies from the music player apk from JW4 rom.
I have sucessfully removed all of the touchwiz references and gotten the apk to recompile. I have signed the apk and I can get it to install and show up in the app drawer, but when I try to open the apk I just get a black screen and then it goes back to the app drawer and shows the notification 'media scanner starting...'
here are my logcat results, I'm not really that experienced in android development so I dont really know how to read it and fix the problems,
Is anyone able to help me figure out the logcat results so we can get this app up and running?
Thanks in advance.
If anyone is serious about helping me with this I can send you the apk file too
I/PackageManager( 229): /system/app/MusicPlayerJW4v11-sig-plat.apk changed; collecting certs
I/PackageManager( 229): /data/app/com.google.android.music-1.apk changed; collecting certs
W/PackageManager( 229): Application package com.google.android.music already installed. Skipping duplicate.
W/PackageManager( 229): Not granting permission android.permission.ACCESS_DRM to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission com.android.email.permission.ACCESS_PROVIDER to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission android.permission.FORCE_STOP_PACKAGES to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.android.music
W/PackageManager( 229): Not granting permission android.permission.ACCOUNT_MANAGER to package com.google.android.music (protectionLevel=2 flags=0x8be65)
I/PackageManager( 229): Running dexopt on: com.android.music
W/ActivityManager( 229): Permission Denial: receiving Intent { act=android.intent.action.BOOT_COMPLETED flg=0x10 } to com.android.musicfx requires android.permission.RECEIVE_BOOT_COMPLETED due to sender null (uid 1000)
W/PackageManager( 229): Not granting permission android.permission.ACCESS_DRM to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission com.android.email.permission.ACCESS_PROVIDER to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission android.permission.FORCE_STOP_PACKAGES to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.android.music
W/PackageManager( 229): Not granting permission android.permission.ACCOUNT_MANAGER to package com.google.android.music (protectionLevel=2 flags=0x8be65)
I/ActivityManager( 229): Start proc com.google.android.music:main for broadcast com.google.android.music/com.android.music.MediaAppWidgetProvider: pid=1220 uid=10126 gids={3003, 1015}
I/ActivityThread( 1220): Pub com.google.android.music.MusicContent: com.google.android.music.store.MusicContentProvider
I/MusicStore( 1220): Database version: 37
I/AsyncCursor1:1( 1220): Initialized for content://com.google.android.music.MusicContent/playlists, proj:_id#name, sel: 'null', args: null, order: null
I/MusicPreferences( 1220): Waiting for preferences to be fully loaded
I/MusicPreferences( 1220): Waiting for preferences to be fully loaded
I/ActivityManager( 229): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.music/.list.activity.MpMainTabActivity} from pid 474
I/ActivityManager( 229): Start proc com.android.music for activity com.android.music/.list.activity.MpMainTabActivity: pid=1821 uid=10118 gids={3003, 1015, 3002}
I/dalvikvm( 1821): Could not find method android.os.Environment.getExternalStorageDirectorySd, referenced from method com.android.music.list.activity.MpMainTabActivity$16.onReceive
kage00 said:
Hello
I have been working on removing the touchwiz dependencies from the music player apk from JW4 rom.
I have sucessfully removed all of the touchwiz references and gotten the apk to recompile. I have signed the apk and I can get it to install and show up in the app drawer, but when I try to open the apk I just get a black screen and then it goes back to the app drawer and shows the notification 'media scanner starting...'
here are my logcat results, I'm not really that experienced in android development so I dont really know how to read it and fix the problems,
Is anyone able to help me figure out the logcat results so we can get this app up and running?
Thanks in advance.
If anyone is serious about helping me with this I can send you the apk file too
I/PackageManager( 229): /system/app/MusicPlayerJW4v11-sig-plat.apk changed; collecting certs
I/PackageManager( 229): /data/app/com.google.android.music-1.apk changed; collecting certs
W/PackageManager( 229): Application package com.google.android.music already installed. Skipping duplicate.
W/PackageManager( 229): Not granting permission android.permission.ACCESS_DRM to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission com.android.email.permission.ACCESS_PROVIDER to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission android.permission.FORCE_STOP_PACKAGES to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.android.music
W/PackageManager( 229): Not granting permission android.permission.ACCOUNT_MANAGER to package com.google.android.music (protectionLevel=2 flags=0x8be65)
I/PackageManager( 229): Running dexopt on: com.android.music
W/ActivityManager( 229): Permission Denial: receiving Intent { act=android.intent.action.BOOT_COMPLETED flg=0x10 } to com.android.musicfx requires android.permission.RECEIVE_BOOT_COMPLETED due to sender null (uid 1000)
W/PackageManager( 229): Not granting permission android.permission.ACCESS_DRM to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission com.android.email.permission.ACCESS_PROVIDER to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Not granting permission android.permission.FORCE_STOP_PACKAGES to package com.android.music (protectionLevel=2 flags=0x8be45)
W/PackageManager( 229): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.android.music
W/PackageManager( 229): Not granting permission android.permission.ACCOUNT_MANAGER to package com.google.android.music (protectionLevel=2 flags=0x8be65)
I/ActivityManager( 229): Start proc com.google.android.music:main for broadcast com.google.android.music/com.android.music.MediaAppWidgetProvider: pid=1220 uid=10126 gids={3003, 1015}
I/ActivityThread( 1220): Pub com.google.android.music.MusicContent: com.google.android.music.store.MusicContentProvider
I/MusicStore( 1220): Database version: 37
I/AsyncCursor1:1( 1220): Initialized for content://com.google.android.music.MusicContent/playlists, proj:_id#name, sel: 'null', args: null, order: null
I/MusicPreferences( 1220): Waiting for preferences to be fully loaded
I/MusicPreferences( 1220): Waiting for preferences to be fully loaded
I/ActivityManager( 229): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.music/.list.activity.MpMainTabActivity} from pid 474
I/ActivityManager( 229): Start proc com.android.music for activity com.android.music/.list.activity.MpMainTabActivity: pid=1821 uid=10118 gids={3003, 1015, 3002}
I/dalvikvm( 1821): Could not find method android.os.Environment.getExternalStorageDirectorySd, referenced from method com.android.music.list.activity.MpMainTabActivity$16.onReceive
Click to expand...
Click to collapse
you did something wrong
paintball23456 said:
you did something wrong
Click to expand...
Click to collapse
Very insightful of you, thanks
but do you have any idea WHAT I did wrong? or better still, how to fix it
Have you tried symlinking your external sdcard from /emmc to /mnt/sdcard/ext-sd/?
AOSP has the card /emmc and I can see that it is looking to the external SDcard and not finding it? Samsung has it located at folder inside to internal sdcard. Just be aware though that this may cause issues or the media scanner bug going nuts (although I think not as AOSP make it only scan on disconnect from PC but it may take longer cause it does have to scan the ext card (and so it should anyway).
Its got permissions issues obviously haha
Did you push this via adb? If so then go in and just temporarily go and reset its permissions to all 077. Open it up in root browser/explorer and check the boxes
x x x
x x x
x x x
Reboot the phone and reset the dalvik cache. I usually (for testing only) grant permissions on the test app as full, then back to 0644 if all is good and working.
Try them easy things first, however I think that the last part although it may look like a random 1 line not that important compared to what logcat has spewed at you prior, I actually think this is the key thing? I maybe wrong. Basically the app has checked to see if the boot sequence has been completed according to how samsung has it work....and it hasn't.
AOSP doesn't have the same boot sequece and completion like samsung has because of the different vold, vold.fstab, vold.conf (the latter is also where the device tells to mount the sdcard and external sdcards funnily enough). There is also a reference in the build.prop that is in connection to the two binary fines in /system/bin.
vold.fstab (gingerbread)
Code:
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
discard = disable
asec = disable
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
#end line ## keep this line
Build.prop (and fix for media scan?)
Code:
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
[B]dev.sfbootcomplete=0[/B]
Binaries
"/system/bin/samsungani"
"/system/bin/bootanim"
Maybe look into bringing the files in from the gingerbread, but check ove rthe code in the files in system/etc with a fine tooth comb cause I only got incredible bootloops (I have a feeling that CM chipset swapping to nexus style) is driven from within the kernel?
Worse comes to worse I would ask the devs from the SGSII port if you can grab their files and kernel and test and see what happens?
Man I really don't know aye...this is all speculation, not concreate at all
Edit this post by tegrak maybe of some use?
http://forum.xda-developers.com/showpost.php?p=15185207&postcount=139
If you can make this work on CM based roms there is definitely a beer or 2 from me in your future
Sent from my GT-I9000 using xda premium
Jarmezrocks said:
Have you tried symlinking your external sdcard from /emmc to /mnt/sdcard/ext-sd/?
AOSP has the card /emmc and I can see that it is looking to the external SDcard and not finding it? Samsung has it located at folder inside to internal sdcard. Just be aware though that this may cause issues or the media scanner bug going nuts (although I think not as AOSP make it only scan on disconnect from PC but it may take longer cause it does have to scan the ext card (and so it should anyway).
Its got permissions issues obviously haha
Did you push this via adb? If so then go in and just temporarily go and reset its permissions to all 077. Open it up in root browser/explorer and check the boxes
x x x
x x x
x x x
Reboot the phone and reset the dalvik cache. I usually (for testing only) grant permissions on the test app as full, then back to 0644 if all is good and working.
Try them easy things first, however I think that the last part although it may look like a random 1 line not that important compared to what logcat has spewed at you prior, I actually think this is the key thing? I maybe wrong. Basically the app has checked to see if the boot sequence has been completed according to how samsung has it work....and it hasn't.
AOSP doesn't have the same boot sequece and completion like samsung has because of the different vold, vold.fstab, vold.conf (the latter is also where the device tells to mount the sdcard and external sdcards funnily enough). There is also a reference in the build.prop that is in connection to the two binary fines in /system/bin.
vold.fstab (gingerbread)
Code:
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
discard = disable
asec = disable
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
#end line ## keep this line
Build.prop (and fix for media scan?)
Code:
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
[B]dev.sfbootcomplete=0[/B]
Binaries
"/system/bin/samsungani"
"/system/bin/bootanim"
Maybe look into bringing the files in from the gingerbread, but check ove rthe code in the files in system/etc with a fine tooth comb cause I only got incredible bootloops (I have a feeling that CM chipset swapping to nexus style) is driven from within the kernel?
Worse comes to worse I would ask the devs from the SGSII port if you can grab their files and kernel and test and see what happens?
Man I really don't know aye...this is all speculation, not concreate at all
Edit this post by tegrak maybe of some use?
http://forum.xda-developers.com/showpost.php?p=15185207&postcount=139
Click to expand...
Click to collapse
Thanks Jarmez, I'll have a look at what you said, I'm really busy again at the moment with work and I'm going away to Holland for the weekend too, I'll have a look when I get back, hopefully I will be able to fix the problems and get this up and running soon
any news on it?
ken2802 said:
any news on it?
Click to expand...
Click to collapse
Sorry for the late reply,
I though I'd post this here too as I sent you in the pm the other day.
Still nothing, sorry.
The problem is that the samsung roms mount the internal and external sd cards at different places to all other ICS roms (AOKP, AOSP, CM9, etc) and that is hard coded into the smali of the apk. I don't know how to sucessfully edit the smali to get it to change to work in other roms.
So the project has hit a dead end, I don't know how to change it any other way
kage00 said:
Sorry for the late reply,
I though I'd post this here too as I sent you in the pm the other day.
Still nothing, sorry.
The problem is that the samsung roms mount the internal and external sd cards at different places to all other ICS roms (AOKP, AOSP, CM9, etc) and that is hard coded into the smali of the apk. I don't know how to sucessfully edit the smali to get it to change to work in other roms.
So the project has hit a dead end, I don't know how to change it any other way
Click to expand...
Click to collapse
what if you use simlinks to mount the sdcards to those places as well?
I tried that too, it still didn't work.
From what I understand the samsung rom looks for a specific boot sequence (things being in the right places at the right times) and then it will load up properly.
Because the ICS roms are different, the touchwiz apps look for this sequence and dont find it and then they crash.
Every error I tried to fix with logcat came up with another error after I resolved each one. It just seemed to be never ending.
The only thing I could come to was the boot sequence, it has to do with the vold in the rom, I'm pretty sure anyway
Can you upload the apk anyway?
Wanna take a look when I get time
edit: actually PM me with the apk if you can, cause i will forget it :d
Is anyone still working I'm this?
Sent from my GT-I9000 running remICS-UX using XDA premium
I'm not working on it anymore, I've hit a wall with it.
theos0o has asked for the apk and I've sent it to him, he said he'll work on it when he finds some time.
There are no promises that we will get it to work though...
If he can that would be amazing! I love the stock music player and I'm sure aswell as me and many others would be very grateful for this near impossible task as I've bin told
Sent from my GT-I9000 running remICS-UX using XDA premium
Related
Hey Everyone,
Thought i would share what i did to fix up the issues using the market!
Had a fresh install of FRX06, Had done the bluetooth patch (all working, great work guys btw)
Only real issue i had was downloading from the market. Nothing would download.
Every time just download unsuccessful.
So i played around trying to fix it, and ended up being able to upgrade the market to the newer version, and it all works
So steps.
1. Download vending.apk for version 2.2.6 of the market. (attached)
2. plug your phone into your PC and start up droidexplorer.
3. open command prompt in droidexplorer and type "mount -o remount,rw /"
4. go to /system/app and copy the current vending.apk to your computer (for a backup)
5. delete vending.apk from /system/app
6. Rename the new 2.2.6 version to "vending.apk" and copy it to /system/app
7. restart the phone
8. open market and check that it is working
Hope this helps a few of you out and to get your market working
Or to get the newer version of the market.
Cheers
And now something has gone wrong
Was working fine, till my phone had a SOD and wouldnt turn on so i pulled the battery.
Now getting force closes
Code:
I/ActivityManager( 1355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.in
tent.category.LAUNCHER] flg=0x10200000 cmp=com.android.vending/.AssetBrowserActivity }
I/ActivityManager( 1355): Start proc com.android.vending for activity com.android.vending/.AssetBrow
serActivity: pid=2067 uid=10004 gids={1015, 3003}
I/ActivityThread( 2067): Publishing provider com.android.vending.SuggestionsProvider: com.android.ve
nding.SuggestionsProvider
D/vending ( 2067): [1] VendingApplication.onCreate(): Resetting ServiceLocator from app
D/dalvikvm( 2067): GC_FOR_MALLOC freed 1849 objects / 128848 bytes in 80ms
D/dalvikvm( 2067): GC_FOR_MALLOC freed 6969 objects / 520096 bytes in 90ms
D/GoogleLoginService( 1465): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.goog
le.android.gsf/.loginservice.GoogleLoginService }
I/ActivityManager( 1355): Displayed activity com.android.vending/.AssetBrowserActivity: 1790 ms (tot
al 47180 ms)
D/ResourceType( 2067): calling getConfigurations
D/ResourceType( 2067): called getConfigurations size=200
E/DatabaseUtils( 1465): Writing exception to parcel
E/DatabaseUtils( 1465): java.lang.SecurityException: Permission Denial: writing com.google.android.g
sf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=2067, uid=1000
4 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/DatabaseUtils( 1465): at android.content.ContentProvider$Transport.enforceWritePermission(
ContentProvider.java:348)
E/DatabaseUtils( 1465): at android.content.ContentProvider$Transport.insert(ContentProvider.
java:196)
E/DatabaseUtils( 1465): at android.content.ContentProviderNative.onTransact(ContentProviderN
ative.java:146)
E/DatabaseUtils( 1465): at android.os.Binder.execTransact(Binder.java:288)
E/DatabaseUtils( 1465): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 2067): threadid=9: thread exiting with uncaught exception (group=0x400207f0)
E/AndroidRuntime( 2067): FATAL EXCEPTION: Thread-11
E/AndroidRuntime( 2067): java.lang.SecurityException: Permission Denial: writing com.google.android.
gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=2067, uid=100
04 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/AndroidRuntime( 2067): at android.os.Parcel.readException(Parcel.java:1260)
E/AndroidRuntime( 2067): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUt
ils.java:160)
E/AndroidRuntime( 2067): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUt
ils.java:114)
E/AndroidRuntime( 2067): at android.content.ContentProviderProxy.insert(ContentProviderNative
.java:408)
E/AndroidRuntime( 2067): at android.content.ContentResolver.insert(ContentResolver.java:587)
E/AndroidRuntime( 2067): at com.google.android.gsf.GoogleSettingsContract$NameValueTable.putS
tring(GoogleSettingsContract.java:55)
E/AndroidRuntime( 2067): at com.google.android.gsf.GoogleSettingsContract$Partner.putString(G
oogleSettingsContract.java:126)
E/AndroidRuntime( 2067): at com.android.vending.compat.MarketCheckinHelper.updateCheckinDatab
ase(MarketCheckinHelper.java:12)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater.sendContentSyncViaCheckin(Chec
kinUpdater.java:219)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater.performCheckin(CheckinUpdater.
java:176)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater.access$000(CheckinUpdater.java
:38)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater$1.run(CheckinUpdater.java:109)
E/AndroidRuntime( 2067): at com.android.vending.util.WorkService$1.run(WorkService.java:37)
W/ActivityManager( 1355): Force finishing activity com.android.vending/.AssetBrowserActivity
D/dalvikvm( 2067): GC_FOR_MALLOC freed 6230 objects / 580152 bytes in 160ms
D/dalvikvm( 2067): GC_EXTERNAL_ALLOC freed 3710 objects / 318976 bytes in 110ms
E/Tethering( 1355): active iface (usb0) reported as added, ignoring
Strangely enough... I copied the original market back over and its working (not as pretty though )
I don't have a vending.apk on my system. I tried replacing market.apk, but it just force closed.
I won't have time to check that market APK until quite late tonight at the earliest, and maybe not for a few days (really busy week!), but nearly every one I've ever seen is signed with a key incompatible with our gapps distribution, so I suspect that's the problem you are having.
To get it to work without permissions-related force closes, you have to re-sign it with one of the platform test keys. (I forget exactly which one at the moment). I've done this with 2.2.6 on my phone but I haven't had time to write a tutorial on it.
Edit: Looking at your logcat, GoogleSettingsProvider permissions issues are a classic sign of a signing key mismatch.
Entropy512 said:
I won't have time to check that market APK until quite late tonight at the earliest, and maybe not for a few days (really busy week!), but nearly every one I've ever seen is signed with a key incompatible with our gapps distribution, so I suspect that's the problem you are having.
To get it to work without permissions-related force closes, you have to re-sign it with one of the platform test keys. (I forget exactly which one at the moment). I've done this with 2.2.6 on my phone but I haven't had time to write a tutorial on it.
Edit: Looking at your logcat, GoogleSettingsProvider permissions issues are a classic sign of a signing key mismatch.
Click to expand...
Click to collapse
Oh ok, thanks.
How come it would have worked initially then? Thats weird
Shadoxity said:
Oh ok, thanks.
How come it would have worked initially then? Thats weird
Click to expand...
Click to collapse
I don't know - I do remember a couple of situations where it would work for one download and then fail.
For example, I tried a market APK from a tiad8 ROM - it was awesome for one download and then failed. Now that I know more about the download architecture I think the awesomeness in performance was a fluke. Download performance is all about DownloadProvider.apk and our filesystem drivers... And so far, my attempt to improve Market downloads by tweaking DownloadProvider made the browser totally unusable.
I have had the same as Entropy with most roms I tried.
I can download 1 or 2 things from the market, very slowly, and then it fails, sometimes with random reboots
Just as an FYI, I HAVE gotten Market 2.2.6 to work reliably - it isn't any faster though, that's for sure.
I'll try to post details sometime next week on how to do it. I'm basically out all evening every evening until the end of the weekend so don't have time to post it now.
Shadoxity... question if you will... where did you d/l the bluetooth patch from?
BTW.. I had the same issue w/ market. Went into settings>>applications>> manage applications>> clicked on Market and cleared cache. Did it once and I was only able to d/l 1 file... did it a second time and I've been good since Tuesday. Hope it helps
bluetooth
MerlinOfLore said:
Shadoxity... question if you will... where did you d/l the bluetooth patch from?
Click to expand...
Click to collapse
bluetooth was being tested for Rhodiums over at [TESTING] New audio routing for Froyo. Bluetooth info is in 2nd post.
It didn't work for me... After rebooted the phone (topaz) if I try to run the market it seems to load a white window and after a couple of second it says it's not responding...
What I notice about market is that it leaves 1.83MB-sized "orphans" in /cache. Not sure why it is that size, but regardless of the size of the app it ends up with that fragment.
-- Starfox
MerlinOfLore said:
Shadoxity... question if you will... where did you d/l the bluetooth patch from?
Click to expand...
Click to collapse
From this thead
http://forum.xda-developers.com/showthread.php?t=885550
MerlinOfLore said:
BTW.. I had the same issue w/ market. Went into settings>>applications>> manage applications>> clicked on Market and cleared cache. Did it once and I was only able to d/l 1 file... did it a second time and I've been good since Tuesday. Hope it helps
Click to expand...
Click to collapse
Tried that but made no difference on mine
Has anyone bothered to get logs from the original issue (before the known issue of permissions after manually upgrading the apk)? The only one I've seen had out of memory errors spamming their logs, but they couldn't get me a useful set of logs to look at. If someone could get a log from after a failed market download with my app http://forum.xda-developers.com/showthread.php?t=1123129 it would be much appreciated.
I replaced google apps in frx06 on gapps package downloaded here:
http://goo-inside.me/gapps/gapps-mdpi-20110501-signed.zip
Yes is named as mdpi, but 100% compatible with hdpi too.
And it's works perfect on my opinion.
DmK75 said:
I replaced google apps in frx06 on gapps package downloaded here:
http://goo-inside.me/gapps/gapps-mdpi-20110501-signed.zip
Yes is named as mdpi, but 100% compatible with hdpi too.
And it's works perfect on my opinion.
Click to expand...
Click to collapse
But why...? For what purpose did you replace the gapps package?
arrrghhh said:
But why...? For what purpose did you replace the gapps package?
Click to expand...
Click to collapse
Simply i noticed that built-in gapps are quite old, and also market cant be auto-updated
DmK75 said:
Simply i noticed that built-in gapps are quite old, and also market cant be auto-updated
Click to expand...
Click to collapse
Fair enough, thanks for the follow-up.
DmK75 said:
Simply i noticed that built-in gapps are quite old, and also market cant be auto-updated
Click to expand...
Click to collapse
Just to know, how to install this package? Still through droidexplorer?
Hey guys, so I finally dumped moto as my phone of choice (coming from a D3), and got a Samgsung Galaxy Nexus 4g from Verizon. Talk about night and day!
Anywho, before I get too setup on it, I figured why not unlock and get CM9 running.
Then I realized things are a bit different than the old droid 3, and heck even my xoom.
I see there is a separate forum for the Verizon device, and I'm not 100% sure if there is a current stable CM9 release for it or not. Can someone point me in the right direction for a stable release if there is?
Also, for rooting, is it the same general process as the xoom..back stuff up, unlock and then flash a rooted image? No alterate to that that doesn't involve the unlock?
What about restoring images?
I'm very familiar with all of this in terms of using adb, fastboot, moto devices, etc, but this seems to be a bit of a different arena.
Thanks for any help!:highfive:
1) this is a question... so it should be here. http://forum.xda-developers.com/forumdisplay.php?f=1336
2) there is no official stable cm9 period. only nightlies.
3) http://forum.xda-developers.com/showthread.php?t=1529058 - how to root.
4) if you want to restore to complete stock - http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
Zepius said:
1) this is a question... so it should be here. http://forum.xda-developers.com/forumdisplay.php?f=1336
2) there is no official stable cm9 period. only nightlies.
3) http://forum.xda-developers.com/showthread.php?t=1529058 - how to root.
4) if you want to restore to complete stock - http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
Click to expand...
Click to collapse
Zepius pretty much summed it all up. For what it's worth, unlocking and rooting your Nexus is increadibly easy. It can be down in about 10 minutes and from what I've seen, it's almost impossible to brick these devices
Sorry for posting in the wrong forum initially.
Also thanks to you both for your replies!
I ended up using the Galaxy Nexus Root Toolkit to do my dirty work Automation for the win!
Anyhow, again thank you both! I've just installed Gummy so off I go to customize! This seems so much easier in the long haul than with the Droid 3. Seems like everything is going great!
Update: LOL Nyan cat boot screen...just...epic!
CM9 gives me lots of system not responding messages during installation of apps (not the download, but the install).
I did plug in adb logcat to see what errors or issues might occur on install, and installed the free amazon.com app from Google Play. Here's a bit of what I got on Logcat. Can anyone tell me about the errors and whether they might be responsible for the system not responding I often get? And if so, what might be a fix if it's not part of CM9? I didn't get this particular error with AOKP, so I'm wondering what it could be.
Code:
D/Finsky (20063): [1] DownloadQueueImpl.onStart: com.amazon.mShop.android: onStart
D/OpenGLRenderer(20063): Flushing caches (mode 0)
D/dalvikvm( 219): GC_EXPLICIT freed 777K, 37% free 18269K/28867K, paused 2ms+10ms
I/DownloadManager(19976): Initiating request for download 373
D/dalvikvm( 710): GC_CONCURRENT freed 993K, 59% free 9160K/21891K, paused 2ms+3ms
I/qtaguid (19976): Failed write_ctrl(u 68) res=-1 errno=22
I/qtaguid (19976): Untagging socket 68 failed errno=-22
W/NetworkManagementSocketTagger(19976): untagSocket(68) failed with errno -22
D/Finsky (20063): [1] DownloadQueueImpl.notifyProgress: com.amazon.mShop.android: onProgress 4296073/4296073 Status: 200.
D/Finsky (20063): [1] DownloadBroadcastReceiver.onReceive: Intent received at DownloadBroadcastReceiver
D/Finsky (20063): [1] DownloadImpl.setState: com.amazon.mShop.android from DOWNLOADING to SUCCESS.
D/Finsky (20063): [1] DownloadQueueImpl.onComplete: com.amazon.mShop.android: onComplete
D/Finsky (20063): [1] DownloadQueueImpl.remove: Download com.amazon.mShop.android removed from DownloadQueue
I/installd( 138): free_cache(0) avail 7792984064
D/dalvikvm(19976): GC_EXPLICIT freed 1141K, 78% free 2712K/12288K, paused 2ms+6ms
I/ActivityManager( 219): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=20245 uid=10013 gids={1015, 200
1}
W/ActivityManager( 219): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
W/ActivityManager( 219): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
D/dalvikvm( 219): GC_CONCURRENT freed 2932K, 33% free 19366K/28867K, paused 2ms+8ms
D/dalvikvm( 219): GC_CONCURRENT freed 4223K, 33% free 19451K/28867K, paused 2ms+7ms
I/PackageManager( 219): Running dexopt on: com.amazon.mShop.android
D/dalvikvm(20260): DexOpt: load 207ms, verify+opt 1628ms
I/ActivityManager( 219): Force stopping package com.amazon.mShop.android uid=10079
D/PackageManager( 219): New package installed in /data/app/com.amazon.mShop.android-1.apk
I/ActivityManager( 219): Start proc com.amazon.venezia for broadcast com.amazon.venezia/.notification.ClientBroadcastReceiver: pid=20262 uid=10243 gids={3003,
1015}
I/dalvikvm(20262): Turning on JNI app bug workarounds for target SDK version 9...
I/RegisteredComponentCache( 811): ComponentInfo: ResolveInfo{40eb9de0 com.android.apps.tag.TagViewer p=0 o=0 m=0x108000}, techs: android.nfc.tech.Ndef,
I/Launcher( 829): setLoadOnResume
D/dalvikvm( 219): GC_CONCURRENT freed 4022K, 32% free 19657K/28867K, paused 6ms+16ms
D/dalvikvm( 219): GC_EXPLICIT freed 1267K, 37% free 18399K/28867K, paused 47ms+9ms
D/Finsky (20063): [3263] 1.packageInstalled: Package install status for "com.amazon.mShop.android" is 1
I/ActivityThread(20262): Pub com.amazon.appstore: com.amazon.mas.client.contentprovider.ContentProviderApps
V//ContextScope.java:112(20262): 15:09:23.385 main Contexts in the main scope map after inserting [email protected]: com.amazon.ven
[email protected]
D/PackageManager( 219): generateServicesMap(android.accounts.AccountAuthenticator): 14 services unchanged
D//Ln.java:220(20262): 15:09:24.229 main Configuring Logging, minimum log level is INFO
I/ResourceUpdateHandler(20262): finished parsing the manifest list
I/ResourceUpdateHandler(20262): parsing of manifest for en succeeded
D/PackageManager( 219): generateServicesMap(android.content.SyncAdapter): 30 services unchanged
D/libEGL (20262): loaded /system/lib/egl/libGLES_android.so
^C
Might want to start your own thread, this wasn't a thread for that
You could try to fix permissions in CWM recovery, and clear dalvik cache.
Swiftkey'ed on my CM9 Galaxy Nexus
Aha...Got the dreaded System Not Responding during Updates:
I'm thinking, I dunno? Permissions?
W/PackageManager( 219): Unknown permission android.permission.ADD_SYSTEM_SERVICE in package com.android.phone
W/PackageManager( 219): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x9b
e45)
W/PackageManager( 219): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.verizon.android.wifios (protectionLevel=3 flags=0xbe46)
W/PackageManager( 219): Unknown permission com.android.amazon.dcp.ota.permission.INSTALL_PACKAGES in package com.amazon.venezia
W/PackageManager( 219): Unknown permission com.amazon.dcp.metrics.permission.METRICS_PERMISSION in package com.amazon.venezia
W/PackageManager( 219): Unknown permission com.amazon.SYNC_RECEIVER_ACCESS in package com.amazon.venezia
W/PackageManager( 219): Unknown permission com.amazon.permission.RECEIVE_TOP_WINDOW_CHANGED in package com.amazon.venezia
W/PackageManager( 219): Unknown permission android.permission.READ_OWNER_DATA in package com.google.android.setupwizard
W/PackageManager( 219): Unknown permission android.permission.WRITE_OWNER_DATA in package com.google.android.setupwizard
W/PackageManager( 219): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.android.videoeditor
W/PackageManager( 219): Unknown permission android.permission.ADD_SYSTEM_SERVICE in package com.pandora.android
W/PackageManager( 219): Not granting permission android.permission.ACCOUNT_MANAGER to package com.google.android.apps.docs (protectionLevel=2 flags=0x8be44)
W/PackageManager( 219): Unknown permission android.permission.WRITE_SYNC_STATS in package com.google.android.apps.docs
W/PackageManager( 219): Unknown permission com.amazon.dcp.metrics.permission.METRICS_PERMISSION in package com.amazon.mp3
W/PackageManager( 219): Unknown permission com.amazon.permission.SET_FLAG_NOSOFTKEYS in package com.amazon.mp3
W/PackageManager( 219): Not granting permission android.permission.ACCESS_CHECKIN_PROPERTIES to package com.google.android.apps.googlevoice (protectionLevel=3
flags=0x28be44)
W/PackageManager( 219): Unknown permission com.google.android.apps.googlevoice.REMOTE_INTENT in package com.google.android.apps.googlevoice
W/PackageManager( 219): Unknown permission com.google.android.permission.RECEIVE_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 219): Unknown permission com.google.android.permission.SEND_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 219): Unknown permission com.android.providers.voicemail.permission.READ_WRITE_ALL_VOICEMAIL in package com.google.android.apps.googlevoice
W/PackageManager( 219): Unknown permission com.android.providers.voicemail.permission.READ_WRITE_OWN_VOICEMAIL in package com.google.android.apps.googlevoice
W/PackageManager( 219): Not granting permission android.permission.MODIFY_PHONE_STATE to package com.best.wallpaper.background.hd (protectionLevel=3 flags=0xbe
44)
W/PackageManager( 219): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.google.android.videos
W/PackageManager( 219): Not granting permission android.permission.CONTROL_LOCATION_UPDATES to package com.glympse.android.glympse (protectionLevel=3 flags=0x8
be44)
W/PackageManager( 219): Unknown permission android.permission.ACCESS_COARSE_UPDATES in package com.glympse.android.glympse
W/PackageManager( 219): Not granting permission android.permission.SET_ORIENTATION to package com.eamobile.monopoly_full_azn (protectionLevel=2 flags=0x20be44)
W/PackageManager( 219): Unknown permission android.permission.ACCESS_GPS in package com.magnifis.parking
W/PackageManager( 219): Unknown permission android.permission.ACCESS_LOCATION in package com.magnifis.parking
W/PackageManager( 219): Not granting permission com.google.android.gm.permission.READ_GMAIL to package com.google.android.apps.uploader (protectionLevel=2 flag
s=0x8be45)
W/PackageManager( 219): Unknown permission android.permission.ACCESS_LOCATION in package net.fishlabs.SportsCarChallenge
W/PackageManager( 219): Unknown permission android.permission.ACCESS_GPS in package net.fishlabs.SportsCarChallenge
W/PackageManager( 219): Unknown permission android.permission.ACCESS_ASSISTED_GPS in package net.fishlabs.SportsCarChallenge
W/PackageManager( 219): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.android.vending
W/PackageManager( 219): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.vending (protectionLevel=2 flags=0xab
ec5)
W/PackageManager( 219): Not granting permission evernote.permission.READ_DATA to package com.evernote.widget because it was previously installed without
W/PackageManager( 219): Not granting permission evernote.permission.WRITE_DATA to package com.evernote.widget because it was previously installed without
W/PackageManager( 219): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.vlingo.phoenix (protectionLevel=3 flags=0x28be44)
W/PackageManager( 219): Not granting permission android.permission.STATUS_BAR to package cloudtv.hdwidgets (protectionLevel=3 flags=0x8bc44)
W/PackageManager( 219): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package cloudtv.hdwidgets (protectionLevel=3 flags=0x8bc44)
W/PackageManager( 219): Unknown permission com.google.android.providers.gmail.permission.READ_GMAIL in package com.rageconsulting.android.lightflow
W/PackageManager( 219): Not granting permission com.google.android.gm.permission.READ_GMAIL to package com.rageconsulting.android.lightflow (protectionLevel=2
flags=0x28be46)
W/PackageManager( 219): Not granting permission android.permission.BIND_WALLPAPER to package com.gmail.tyf1android1dev.ktb_v2_001_p3rand (protectionLevel=3 fla
gs=0xbe44)
W/PackageManager( 219): Unknown permission com.android.vending.billing.IBillingAccountService.BIND2 in package com.google.android.gsf.login
W/PackageManager( 219): Not granting permission android.permission.STATUS_BAR to package com.verizon.myverizon.activity (protectionLevel=3 flags=0xbe44)
W/PackageManager( 219): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.verizon.myverizon.activity (protectionLevel=3 flags=0xb
e44)
W/PackageManager( 219): Unknown permission android.permission.ACCESS_COARSE_UPDATES in package com.handmark.expressweather
W/PackageManager( 219): Not granting permission android.permission.CONTROL_LOCATION_UPDATES to package com.handmark.expressweather (protectionLevel=3 flags=0xb
c44)
W/PackageManager( 219): Unknown permission android.permission.LOCATION in package com.escapistgames.starchart
W/PackageManager( 219): Not granting permission android.permission.READ_FRAME_BUFFER to package com.google.android.marvin.talkback (protectionLevel=3 flags=0x2
8be44)
W/PackageManager( 219): Unknown permission archos.permission.FULLSCREEN.FULL in package com.herocraft.game.musaicbox
W/PackageManager( 219): Unknown permission android.permission.DIAL in package com.spb.shell3d
W/PackageManager( 219): Not granting permission android.permission.ACCOUNT_MANAGER to package com.google.android.music (protectionLevel=2 flags=0x8be64)
W/PackageManager( 219): Unknown permission android.webkit.permission.PLUGIN in package com.adobe.flashplayer
W/PackageManager( 219): Not granting permission android.permission.SET_PREFERRED_APPLICATIONS to package com.teslacoilsw.homesmack (protectionLevel=2 flags=0x8
be44)
W/PackageManager( 219): Unknown permission com.fsck.k9.permission.READ_MESSAGES in package uk.co.senab.blueNotify
W/PackageManager( 219): Unknown permission com.fsck.k9.permission.DELETE_MESSAGES in package uk.co.senab.blueNotify
W/PackageManager( 219): Unknown permission com.android.vending.permission.UPDATE_MARKET_FAILURE in package com.android.vending.updater
W/PackageManager( 219): Unknown permission com.shazam.android.preloadinfo.provider.ACCESS_DATA in package com.shazam.encore.android
W/PackageManager( 219): Not granting permission android.permission.SET_ORIENTATION to package com.omgpop.dstpaid (protectionLevel=2 flags=0x28bc46)
W/PackageManager( 219): Unknown permission android.permission.HDMI_SUSPEND in package com.mobitv.client.nfl2010
W/PackageManager( 219): Unknown permission mobi.mgeek.TunnyBrowser.permission.READ_HISTORY_BOOKMARKS in package com.dolphin.browser.lab.en
W/PackageManager( 219): Unknown permission mobi.mgeek.TunnyBrowser.permission.WRITE_HISTORY_BOOKMARK in package com.dolphin.browser.lab.en
W/PackageManager( 219): Unknown permission com.dolphin.browser.permission.ACCESS_PROVIDER in package com.dolphin.browser.lab.en
W/PackageManager( 219): Not granting permission android.permission.SET_PREFERRED_APPLICATIONS to package com.dolphin.browser.lab.en (protectionLevel=2 flags=0x
8be44)
W/PackageManager( 219): Unknown permission com.estrongs.android.pop.PERMISSION in package com.estrongs.android.pop
W/PackageManager( 219): Unknown permission com.google.android.providers.gmail.permission.READ_GMAIL in package com.mobisystems.editor.office_registered
W/PackageManager( 219): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x8be45)
W/PackageManager( 219): Not granting permission android.permission.DEVICE_POWER to package com.android.facelock (protectionLevel=2 flags=0x8be45)
W/PackageManager( 219): Not granting permission android.permission.INSTALL_PACKAGES to package com.smarterdroid.wififiletransfer (protectionLevel=3 flags=0x20b
e44)
W/PackageManager( 219): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.google.android.apps.maps
I/ActivityManager( 219): Force stopping package com.google.android.apps.maps uid=10064
I/RegisteredComponentCache( 811): ComponentInfo: ResolveInfo{40e5cbb0 com.android.apps.tag.TagViewer p=0 o=0 m=0x108000}, techs: android.nfc.tech.Ndef,
I/ActivityManager( 219): Start proc com.amazon.venezia for broadcast com.amazon.venezia/.notification.ClientBroadcastReceiver: pid=23979 uid=10243 gids={3003,
1015}
I/RegisteredComponentCache( 811): ComponentInfo: ResolveInfo{40ebd288 com.android.apps.tag.TagViewer p=0 o=0 m=0x108000}, techs: android.nfc.tech.Ndef,
I/dalvikvm(23979): Turning on JNI app bug workarounds for target SDK version 9...
D/dalvikvm(19863): GC_EXPLICIT freed 1276K, 78% free 2730K/12288K, paused 3ms+10ms
D/dalvikvm( 829): GC_EXPLICIT freed 2362K, 29% free 22471K/31235K, paused 3ms+10ms
I/Launcher( 829): setLoadOnResume
D/dalvikvm( 219): GC_EXPLICIT freed 6096K, 37% free 20700K/32451K, paused 3ms+44ms
I/ActivityThread(23979): Pub com.amazon.appstore: com.amazon.mas.client.contentprovider.ContentProviderApps
V//ContextScope.java:112(23979): 16:14:36.170 main Contexts in the main scope map after inserting [email protected]: com.amazon.ven
[email protected]
D/PackageManager( 219): generateServicesMap(android.accounts.AccountAuthenticator): 14 services unchanged
D/Finsky (23084): [3534] 1.packageInstalled: Package install status for "com.google.android.apps.maps" is 1
D/Finsky (23084): [1] InstallerImpl.kick: Installer kick null - starting com.google.android.apps.plus
D//Ln.java:220(23979): 16:14:36.772 main Configuring Logging, minimum log level is INFO
I/ResourceUpdateHandler(23979): finished parsing the manifest list
I/ResourceUpdateHandler(23979): parsing of manifest for en succeeded
D/dalvikvm(23084): GC_CONCURRENT freed 2051K, 32% free 10930K/15939K, paused 2ms+8ms
D/libEGL (23979): loaded /system/lib/egl/libGLES_android.so
D/libEGL (23979): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL (23979): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL (23979): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/PackageManager( 219): generateServicesMap(android.content.SyncAdapter): 31 services unchanged
D/PackageManager( 219): generateServicesMap(android.accounts.AccountAuthenticator): 14 services unchanged
D/BackupManagerService( 219): Received broadcast Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.google.android.apps.maps flg=0x10000010 (ha
s extras) }
D/PackageManager( 219): generateServicesMap(android.content.SyncAdapter): 31 services unchanged
^C
C:\android-sdk-windows\tools>
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
Well, given this only happened moving to CM9 and not on AOKP...I thought it was CM9 related...and this is Q&A after all..
I'm doing 'fixing permissions...' right now on CWM 5.8.0.2....I'll happily nuke the messages, but I thought it might help others if this fixes it...because a system not responding | Wait | kinda sucks.
Note:
This thread started as a discussion for development of a working CM11.0 / KitKat build for GT-I9295 / S4 Active International. At first, with assistance from a CM dev who wishes to remain unnamed and does not want involvement with this, a build was produced for this device, based on work previously done by LeJay on CM10.2. Unfortunately, I have not been able to contact LeJay, which is the primary motivation for starting this thread. Since then, and in a short space of time, xda user @spegelius, has managed to progress this to a fully functional build, which some users are already using as a daily driver.
After much hard work from pretty much everyone except me, it pleases me to write that this device has reached official status, and as such one can obtain nightly builds, updates, and source code, from the official CyanogenMod sources. Congratulations to all involved, and the effort thats been put in to make this happen.
Instructions:
1. Install CWM recovery from TODO: link official CWM here
2. Download the latest official nightly from: http://download.cyanogenmod.org/?device=jactivelte
Left for historic purposes (older pre-official builds): Credit: spegelius: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing
3. Download CM11.0 gapps from here
4. Boot into recovery by holding the Volume Up button as the phone is booting.
5. Back up your current ROM inside CWM recovery.
6. Flash CyanogenMod ROM to your device using CWM recovery.
7. Flash Google Applications to your device using CWM recovery.
8. Do a wipe data/factory reset from within CWM recovery.
9. Reboot system.
Known Issues:
1. None that I'm currently aware of.
2. Report them. Keeping this part up to date has proven to never actually happen, so maybe just read through the entire thread. Convenient right?
Build from source:
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
when you initialize the CyanogenMod repository so you get the source for CM-11.0.
Run 'repo sync' and compile with 'brunch jactivelte'. Proprietary files you can find on github, or extract them from an existing rom.
This is pretty much a word for word ripoff of LeJay's cm 10.2 post. This is where one would say something like, I take no responsibility if your device explodes, catches fire, invades a foreign nation, causes your cat to get run over by a car, etc.
Thanks goes to LeJay for being pretty much the sole reason a thread was created for this device on XDA, and in turn the people he gave thanks to, primarily the CM team. Additional thanks, of course, goes to spegelius, for running with this thread, and creating something that actually works.
Downloads here:
** TODO **
Changelog:
** TODO **
awesome! I look forward to a stable release
Interesting, good to hear there's CM dev helping . I've been playing with the idea of trying to compile CM11 since i got AOSP 4.3 working as daily driver. I'm also using LeJay's work, without it i propably wouldn't even have strated hacking with Android. And i haven't heard from him either, i hope he is okay.
Anyways, my first idea was to try it with same jactiveltexx stuff as cm-10.2 is done and see how far that takes me, but if you have already done it and no display, it's possible that the kenel needs to be updated and newer graphics libs used. Luckily i've done some merging between S4 and S4 Active kernels and i already had a look at CM11 S4 kernel code. There are some changes in the graphics code, so there's a very good possibility to get those merged to Active kernel, to me it looks like S4 and S4 Active have same kernel, except for camera, some gpio stuff and assorted tidbits around the kernel. As for the graphics drivers, i think it should be possible to use libs from S4's CM11 build?
Gotta try this myself later this week
spegelius said:
Anyways, my first idea was to try it with same jactiveltexx stuff as cm-10.2 is done and see how far that takes me, but if you have already done it and no display, it's possible that the kenel needs to be updated and newer graphics libs used. Luckily i've done some merging between S4 and S4 Active kernels and i already had a look at CM11 S4 kernel code. There are some changes in the graphics code, so there's a very good possibility to get those merged to Active kernel, to me it looks like S4 and S4 Active have same kernel, except for camera, some gpio stuff and assorted tidbits around the kernel. As for the graphics drivers, i think it should be possible to use libs from S4's CM11 build?
Gotta try this myself later this week
Click to expand...
Click to collapse
I have tried compiling the stock CM jf common kernel, with s4 active config. SurfaceFlinger fails to initialise EGL libs. I have tried porting LeJay's cm-10.2 active kernel to build on cm11.0, that also fails in the same way. It seems you' are right. The graphics updates for the other s4 devices likely need to be done for active as well, which may require some new props. Jftleatt's props might be worth look at for display props, same cpu/gpu, different lcd panel.. I'm using my phone as a daily, and haven't had much of a chance to test builds.
When big boys does the taking we just wait for candies...
Sent from my GT-I9295 using Tapatalk
snadge said:
I have tried compiling the stock CM jf common kernel, with s4 active config. SurfaceFlinger fails to initialise EGL libs. I have tried porting LeJay's cm-10.2 active kernel to build on cm11.0, that also fails in the same way. It seems you' are right. The graphics updates for the other s4 devices likely need to be done for active as well, which may require some new props. Jftleatt's props might be worth look at for display props, same cpu/gpu, different lcd panel.. I'm using my phone as a daily, and haven't had much of a chance to test builds.
Click to expand...
Click to collapse
Weel i made a build myself, tweaked the makefiles etc. but there;s a problem: i can't get past the initial text. Something goes wrong about the build and i don't quite know what. I think i'll do a clean repo sync, current source tree is from cm-10.2 and even though repo status says it's clean, i have a feeling something might be wrong with it.
I did some kernel source merging and the build process does build it, so now to get that damn thing to boot...
Some testing done:
clean CM11 repo sync, still no go with cm-10.2 jactive kernel or the one with merges from jf kernel i made. No adb connection, last_kmsg: http://pastebin.com/Nj5rStTc
using jf kernel and jactive config, with small mods to get it to build, goes a bit further. Screen turns black after the initial Samsung text, adb connection doesn't show up and no last_kmsg available
In he last_kmsg above, it seems that the kernel doesn't mount stuff properly or something?
Finally figured out why i wasn't getting past the initial boot text; a bad formatting in jf-common makefile left almost all of the qcom init files out of the boot.img so no wonder stuff didn't work... teaches me to proofread stuff...
Ok, now that i got that sorted out, i get it to boot. Display stays back, but loking at the logcat, Surfaceflinger doesn't die. So it seems the problem now is that the panel isn't turned on correctly, but otherwise the thing works, maybe. I'm using a mix of blobs from Active and latest jflte CM11 nighly.
Now i need to go to sauna and drink beer ->
Hrmm, it seems the stuff responsible for panel is crashing. Last_kmsg: http://pastebin.com/jZyDLcXw
Code:
[ 15.869781] ======== dsi clock dump ++++ =====================
[ 15.869781] 0x0130 : 00000005
[ 15.869781] 0x0134 : 00000000
[ 15.869781] 0x0138 : 00002003
[ 15.869781] 0x004c : 00000005
[ 15.869812] 0x0050 : 00000000
[ 15.869812] 0x0054 : 00000003
[ 15.869812] ======== dsi clock dump ---- =====================
[ 15.869842] [<c010badc>] (unwind_backtrace+0x0/0xe0) from [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c)
[ 15.869842] [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c) from [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8)
[ 15.869842] [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8) from [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48)
[ 15.869873] [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48) from [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100)
[ 15.869873] [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100) from [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4)
[ 15.869873] [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4) from [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4)
[ 15.869903] [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4) from [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c)
[ 15.869903] [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c) from [<c0404dd0>] (panel_next_late_init+0x38/0x44)
[ 15.897583] msm_ta_detect_work: USB exit ta detection - frindex
[ 16.067596] mipi_dsi_cmd_dma_tx: dma timeout error
[ 16.067596] dumpreg: =============IT's Fail case ==============
Same thing with cm10.2 Active code and code from S4 kernel...
spegelius said:
Hrmm, it seems the stuff responsible for panel is crashing. Last_kmsg: http://pastebin.com/jZyDLcXw
Code:
[ 15.869781] ======== dsi clock dump ++++ =====================
[ 15.869781] 0x0130 : 00000005
[ 15.869781] 0x0134 : 00000000
[ 15.869781] 0x0138 : 00002003
[ 15.869781] 0x004c : 00000005
[ 15.869812] 0x0050 : 00000000
[ 15.869812] 0x0054 : 00000003
[ 15.869812] ======== dsi clock dump ---- =====================
[ 15.869842] [<c010badc>] (unwind_backtrace+0x0/0xe0) from [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c)
[ 15.869842] [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c) from [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8)
[ 15.869842] [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8) from [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48)
[ 15.869873] [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48) from [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100)
[ 15.869873] [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100) from [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4)
[ 15.869873] [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4) from [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4)
[ 15.869903] [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4) from [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c)
[ 15.869903] [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c) from [<c0404dd0>] (panel_next_late_init+0x38/0x44)
[ 15.897583] msm_ta_detect_work: USB exit ta detection - frindex
[ 16.067596] mipi_dsi_cmd_dma_tx: dma timeout error
[ 16.067596] dumpreg: =============IT's Fail case ==============
Same thing with cm10.2 Active code and code from S4 kernel...
Click to expand...
Click to collapse
Hi sir ... As my experience with dirt porting ... You have fixed everything in kerenl as I see the issues come from different libs in /system/lib...
JFLTE libs differ a lot from ours ... Some how the screen has to with the GPU driver... I am saying this because I have tried porting a jflte cm 4.3.1 ROM using the old cm 4.3 kernel by Lejay... It booted (yay) but the screen looks orangish the WiFi doesn't work the ril doesn't work ...but replacing the nessary libs from your aosp fixed the issues (the ROM didn't boot here) I've known these details from a small debugging event I made ...
BTW is there a way of building a device tree for 4.4 ?? Wouldn't that make it easier on us ??
mythi said:
Hi sir ... As my experience with dirt porting ... You have fixed everything in kerenl as I see the issues come from different libs in /system/lib...
JFLTE libs differ a lot from ours ... Some how the screen has to with the GPU driver... I am saying this because I have tried porting a jflte cm 4.3.1 ROM using the old cm 4.3 kernel by Lejay... It booted (yay) but the screen looks orangish the WiFi doesn't work the ril doesn't work ...but replacing the nessary libs from your aosp fixed the issues (the ROM didn't boot here) I've known these details from a small debugging event I made ...
BTW is there a way of building a device tree for 4.4 ?? Wouldn't that make it easier on us ??
Click to expand...
Click to collapse
Hmm, i was afraid that the GPU drivers would be somehow related to to panel, even though i was thnking that they are separate stuff so if done correctly, one driver doesn't need to stuff that orher driver does...
I did a build with cm10.2 kernel and libs from the AOSP build and suprisingly same results: lcd init fails, Surfaceflinger doesn't die... i need to do more testing with using some qcom stuff from cm10.2 to help pinpointing things.
By device tree do you mean the makefiles etc. like in jf-common? Already done, they are in my github, cm-11.0 branch has been added. No repo for proprietary files yet, though, need to get something working first...
spegelius said:
Hmm, i was afraid that the GPU drivers would be somehow related to to panel, even though i was thnking that they are separate stuff so if done correctly, one driver doesn't need to stuff that orher driver does...
I did a build with cm10.2 kernel and libs from the AOSP build and suprisingly same results: lcd init fails, Surfaceflinger doesn't die... i need to do more testing with using some qcom stuff from cm10.2 to help pinpointing things.
By device tree do you mean the makefiles etc. like in jf-common? Already done, they are in my github, cm-11.0 branch has been added. No repo for proprietary files yet, though, need to get something working first...
Click to expand...
Click to collapse
Why not play with the framebuffer/Screenflinger/ Surfaceflinger in the ramdisk of the kernel i think the init file has to do something for lauching the screen :laugh:
Yes the device tree with all qcom propiretory stuff etc..etc..
mythi said:
Why not play with the framebuffer/Screenflinger/ Surfaceflinger in the ramdisk of the kernel i think the init file has to do something for lauching the screen :laugh:
Yes the device tree with all qcom propiretory stuff etc..etc..
Click to expand...
Click to collapse
Yeah, those init files could be causing this. I tried using cm10.2 device tree (jf-common, qcom-common and msm8960) but there's to much changed and getting it to compile would be too much hassle. I'll see about swapping some init files...
Currently for jactive there are LeJay's devicetree, which contains the jactiveltexx and modified jf-common (some proprietary caera files are disabled). I've updated them a bit and added the cm11 branch. In addition, hardware/samsung, qcom-common and msm8960-common are needed, but these have nothing jactive specific, at least not yet...
---------- Post added at 09:40 PM ---------- Previous post was at 09:24 PM ----------
Holy sh*t, i got visual . Using:
cm10.2 jactive kernel
cm10.2 jactive blobs
hardware/samsung from cm10.2
otherwise all cm11 stuff
But now mediaserver crashes and system can't fully boot due to not being able to starte the service. But nevertheless, looking good! Gonna try audio blobs from jflte
Ok now this is getting plain weird: i can't make a build that has working display anymore. Same sources, nothing is modified. I run brunch as always and the result: no display... wtf? And, if i use the boot.img from the one and only working build with another buil, there's display :silly: . Me no understand...
spegelius said:
Ok now this is getting plain weird: i can't make a build that has working display anymore. Same sources, nothing is modified. I run brunch as always and the result: no display... wtf? And, if i use the boot.img from the one and only working build with another buil, there's display :silly: . Me no understand...
Click to expand...
Click to collapse
spegelius said:
Yeah, those init files could be causing this. I tried using cm10.2 device tree (jf-common, qcom-common and msm8960) but there's to much changed and getting it to compile would be too much hassle. I'll see about swapping some init files...
Currently for jactive there are LeJay's devicetree, which contains the jactiveltexx and modified jf-common (some proprietary caera files are disabled). I've updated them a bit and added the cm11 branch. In addition, hardware/samsung, qcom-common and msm8960-common are needed, but these have nothing jactive specific, at least not yet...
---------- Post added at 09:40 PM ---------- Previous post was at 09:24 PM ----------
Holy sh*t, i got visual . Using:
cm10.2 jactive kernel
cm10.2 jactive blobs
hardware/samsung from cm10.2
otherwise all cm11 stuff
But now mediaserver crashes and system can't fully boot due to not being able to starte the service. But nevertheless, looking good! Gonna try audio blobs from jflte
Click to expand...
Click to collapse
Hahahhaahha... Seams we are getting it near ... Could you post a ksmg/logcat or any thing helpful ...will try to help this has bright future of success if we all join
mythi said:
Hahahhaahha... Seams we are getting it near ... Could you post a ksmg/logcat or any thing helpful ...will try to help this has bright future of success if we all join
Click to expand...
Click to collapse
Yeah, here are the last_kmsg and logcat from a build that has display: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing
I'm uploading the build also and some other last_kmsg's + logcats
Gonna try to create a bootimg with kernel from aosp. I mean, every build i make now doesn't turn the display on. But if i swap the zImage from the only working build, then the build suddenly has display. I also tried building the kernel separately and creating a bootimg with it, no display...
Edit: with aosp zImage, display is shown... so does this mean that the CM11 gcc somehow borks the kernel build? Or wtf? The kernel i'm building has only some filesystem changes vs. aosp kernel...
Edit2: found out why display wan't turning on: when making device tree, i modified BoardConfig.mk to look as much like jfltexx BoardConfig.mk. With that, kernel variant config and kernel config strings switched places. Turns out, in those two kernel defconfig files (jactive_defconfig and cyanogen_defconfig) two different panels are configured. And when configs were switched, the wrong panel config was taken into use... aargh. Damn, i was looking at those lines and thinking if should change them or not...
spegelius said:
Yeah, here are the last_kmsg and logcat from a build that has display: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing
I'm uploading the build also and some other last_kmsg's + logcats
Gonna try to create a bootimg with kernel from aosp. I mean, every build i make now doesn't turn the display on. But if i swap the zImage from the only working build, then the build suddenly has display. I also tried building the kernel separately and creating a bootimg with it, no display...
Edit: with aosp zImage, display is shown... so does this mean that the CM11 gcc somehow borks the kernel build? Or wtf? The kernel i'm building has only some filesystem changes vs. aosp kernel...
Edit2: found out why display wan't turning on: when making device tree, i modified BoardConfig.mk to look as much like jfltexx BoardConfig.mk. With that, kernel variant config and kernel config strings switched places. Turns out, in those two kernel defconfig files (jactive_defconfig and cyanogen_defconfig) two different panels are configured. And when configs were switched, the wrong panel config was taken into use... aargh. Damn, i was looking at those lines and thinking if should change them or not...
Click to expand...
Click to collapse
Okay... the translation ...The display is now fixed ... the rom boots up ... BUT the media thingy is still fcing and you can't get passed the error
seems it is more nearer than i thought will take a look at the files you posted above :angel:
---------- Post added at 06:55 PM ---------- Previous post was at 06:34 PM ----------
could these lines have something to do with the issue we are getting ?
these lines are from kmesg you provided
Code:
[ 0.030975] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
[ 0.031341] MSM_DCVS: msm_dcvs_early_init: Unable to initialize DCVS err=4
[ 0.666229] cont_splash_clk_ctrl: dsi_esc_clk - clk_set_rate failed
[ 0.672607] [mdnie lite] start!
[ 0.672729] [mdnie lite] end!
[ 1.688598] msm8930_audio_init: Not the right machine type
[ 1.693145] msm_audio_init: Not the right machine type
[ 79.400085] msm_ipc_router_create: Do not have permissions
hmmm...
here are some lines from logcat i noticed
Code:
W/PackageManager( 761): Package com.android.browser desires unavailable shared library com.qrd.useragent; ignoring!
W/PackageManager( 761): Package com.android.gallery3d desires unavailable shared library com.google.android.media.effects; ignoring!
I/PackageManager( 761): Time to scan packages: 0.69 seconds
W/PackageManager( 761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.soundrecorder (protectionLevel=18 flags=0x8be45)
W/PackageManager( 761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package com.cyanogenmod.account
W/PackageManager( 761): Not granting permission android.permission.GLOBAL_SEARCH to package com.android.quicksearchbox (protectionLevel=18 flags=0x8be45)
W/PackageManager( 761): Unknown permission com.google.android.gallery3d.permission.GALLERY_PROVIDER in package com.android.bluetooth
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.calendar
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package com.android.providers.calendar
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.calendar
W/PackageManager( 761): Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager( 761): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x49be45)
W/PackageManager( 761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager( 761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.onetimeinitializer
W/PackageManager( 761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.onetimeinitializer
W/PackageManager( 761): Not granting permission android.permission.BIND_WALLPAPER to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)
W/PackageManager( 761): Unknown permission android.permission.INSTALL_DRM in package com.android.mms
W/PackageManager( 761): Unknown permission com.cyanogenmod.filemanager.permissions.READ_THEME in package com.cyanogenmod.filemanager
W/PackageManager( 761): Unknown permission android.permission.MMS_PUSH in package org.codeaurora.bluetooth
W/PackageManager( 761): Unknown permission com.google.android.gallery3d.permission.PICASA_STORE in package com.android.dreams.phototable
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings
W/PackageManager( 761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.settings
W/PackageManager( 761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.settings
W/PackageManager( 761): Unknown permission android.permission.CHANGE_PRIVACY_GUARD_STATE in package com.android.settings
W/PackageManager( 761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager( 761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager( 761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package org.whispersystems.whisperpush
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in package com.android.development
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.development
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in package com.android.development
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in package com.android.development
W/PackageManager( 761): Not granting permission android.permission.DELETE_PACKAGES to package com.svox.pico (protectionLevel=18 flags=0x8be45)
W/PackageManager( 761): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x48be45)
W/PackageManager( 761): Unknown permission com.android.deskclock.worldclock.permissions.WRITE_DATABASE in package com.android.deskclock
W/PackageManager( 761): Unknown permission android.permission.CANCEL_NOTIFICATIONS in package org.cyanogenmod.voiceplus
V/PackageManager( 761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
W/PackageManager( 761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
V/PackageManager( 761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
W/PackageManager( 761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
V/PackageManager( 761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
W/PackageManager( 761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
Edit1:Seems a permissions issue ??
BTW the system loops doing something ...WTF is it ?
mythi said:
Okay... the translation ...The display is now fixed ... the rom boots up ... BUT the media thingy is still fcing and you can't get passed the error
seems it is more nearer than i thought will take a look at the files you posted above :angel:
---------- Post added at 06:55 PM ---------- Previous post was at 06:34 PM ----------
could these lines have something to do with the issue we are getting ?
these lines are from kmesg you provided
Code:
[ 0.030975] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
[ 0.031341] MSM_DCVS: msm_dcvs_early_init: Unable to initialize DCVS err=4
[ 0.666229] cont_splash_clk_ctrl: dsi_esc_clk - clk_set_rate failed
[ 0.672607] [mdnie lite] start!
[ 0.672729] [mdnie lite] end!
[ 1.688598] msm8930_audio_init: Not the right machine type
[ 1.693145] msm_audio_init: Not the right machine type
[ 79.400085] msm_ipc_router_create: Do not have permissions
hmmm...
here are some lines from logcat i noticed
Code:
W/PackageManager( 761): Package com.android.browser desires unavailable shared library com.qrd.useragent; ignoring!
W/PackageManager( 761): Package com.android.gallery3d desires unavailable shared library com.google.android.media.effects; ignoring!
I/PackageManager( 761): Time to scan packages: 0.69 seconds
W/PackageManager( 761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.soundrecorder (protectionLevel=18 flags=0x8be45)
W/PackageManager( 761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package com.cyanogenmod.account
W/PackageManager( 761): Not granting permission android.permission.GLOBAL_SEARCH to package com.android.quicksearchbox (protectionLevel=18 flags=0x8be45)
W/PackageManager( 761): Unknown permission com.google.android.gallery3d.permission.GALLERY_PROVIDER in package com.android.bluetooth
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.calendar
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package com.android.providers.calendar
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.calendar
W/PackageManager( 761): Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager( 761): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x49be45)
W/PackageManager( 761): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.android.browser (protectionLevel=18 flags=0x49be45)
W/PackageManager( 761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.onetimeinitializer
W/PackageManager( 761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.onetimeinitializer
W/PackageManager( 761): Not granting permission android.permission.BIND_WALLPAPER to package com.android.camera2 (protectionLevel=18 flags=0x58bc45)
W/PackageManager( 761): Unknown permission android.permission.INSTALL_DRM in package com.android.mms
W/PackageManager( 761): Unknown permission com.cyanogenmod.filemanager.permissions.READ_THEME in package com.cyanogenmod.filemanager
W/PackageManager( 761): Unknown permission android.permission.MMS_PUSH in package org.codeaurora.bluetooth
W/PackageManager( 761): Unknown permission com.google.android.gallery3d.permission.PICASA_STORE in package com.android.dreams.phototable
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings
W/PackageManager( 761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.android.settings
W/PackageManager( 761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.android.settings
W/PackageManager( 761): Unknown permission android.permission.CHANGE_PRIVACY_GUARD_STATE in package com.android.settings
W/PackageManager( 761): Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager( 761): Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.cyanogenmod.trebuchet
W/PackageManager( 761): Unknown permission com.google.android.c2dm.permission.RECEIVE in package org.whispersystems.whisperpush
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in package com.android.development
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.development
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in package com.android.development
W/PackageManager( 761): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in package com.android.development
W/PackageManager( 761): Not granting permission android.permission.DELETE_PACKAGES to package com.svox.pico (protectionLevel=18 flags=0x8be45)
W/PackageManager( 761): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x48be45)
W/PackageManager( 761): Unknown permission com.android.deskclock.worldclock.permissions.WRITE_DATABASE in package com.android.deskclock
W/PackageManager( 761): Unknown permission android.permission.CANCEL_NOTIFICATIONS in package org.cyanogenmod.voiceplus
V/PackageManager( 761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
W/PackageManager( 761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
V/PackageManager( 761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
W/PackageManager( 761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
V/PackageManager( 761): Disabling com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
W/PackageManager( 761): Unable to disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$Receiver
Edit1:Seems a permissions issue ??
BTW the system loops doing something ...WTF is it ?
Click to expand...
Click to collapse
I compared the las_kmsg lines to AOSP bootup and those lines are there too, so nothing to worry about (well i hope at least. It seems that the kernel spits out a lot of 'errors', hard to tell what is important and what not.
And the logcat... well to me it seems that the mediaserver is SIGSEGVaulting every now and then, causing the boot loop because servicemanager can't get all the required services running. Also the permission problems... i saw those with AOSP too, apparently they aren't bad. And do note that i haven't installed gapps, that's a fresh boot after factory reset/rom flash.
Yesterday i made a build with kernel that has most of the stuff from jf merged and with active/jf mix of blobs. Boots ok, until the same mediaserver bootloop. I added some debug to AudioPolicyManager and to my suprise it boots up to the 'Welcome to Cyanogenmod' screen, but com.android.phone keeps FCing and i can't use the phone...
Also, god damn Cyanogemod... why does it disable ADB after first boot? It's really frickin nice to get up to this point and then lose all the ability to debug the damn thing!
I was looking at this thread and I tried getting these to work but the only one that works is background defocus.
[PORT] [JB][KK] Xperia Z2 & T2 Smart Social Camera Addons
I moved the libs, set permissions, cleared data, installed apks, and rebooted. Can't get 4k video, Timeshift video, or Portrait Retouch to work. I read the entire 54 pages and haven't found anything that works. Just wondering if anyone did and how. Thanks
RevokOne said:
I was looking at this thread and I tried getting these to work but the only one that works is background defocus.
[PORT] [JB][KK] Xperia Z2 & T2 Smart Social Camera Addons
I moved the libs, set permissions, cleared data, installed apks, and rebooted. Can't get 4k video, Timeshift video, or Portrait Retouch to work. I read the entire 54 pages and haven't found anything that works. Just wondering if anyone did and how. Thanks
Click to expand...
Click to collapse
What device are you using?
Blurped from my Xperia V 4.3
Same here, except background defocus does not work either, it starts, takes the 2 pictures and closes.
We are using Z1C, cause ... it's the Z1C forum
Makes my camera module crash and eventually disappear completely beyond repair. Had to reflash my ROM to fix it. I will stay far away from this mod till someone can make a proper, step to step guide for the Z1C.
Sent from my D5503 using xda app-developers app
kind3r said:
Same here, except background defocus does not work either, it starts, takes the 2 pictures and closes.
We are using Z1C, cause ... it's the Z1C forum
Click to expand...
Click to collapse
Flash the unrooted apk for bg defocus, works perfectly. Everything else on the other hand does not.
RevokOne said:
Flash the unrooted apk for bg defocus, works perfectly. Everything else on the other hand does not.
Click to expand...
Click to collapse
Haven't tried that until now because I was rooted ... But seems to work, thanks
I think there is a permission issue.
This is what I see in the logs during install:
W/PackageManager( 1471): Not granting permission com.sonyericsson.permission.CAMERA_EXTENDED to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=2 flags=0x58be44)
W/PackageManager( 1471): Not granting permission android.permission.WRITE_MEDIA_STORAGE to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=18 flags=0x58be44)
W/PackageManager( 1471): Not granting permission com.sonymobile.permission.SOMC_CAMERA to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=18 flags=0x58be44)
W/PackageManager( 1471): Not granting permission com.sonymobile.permission.SOMC_AUTO_UPLOADER to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=18 flags=0x58be44)
W/PackageManager( 1471): Not granting permission com.sonymobile.permission.CAMERA_ADDON_DATA_WRITE to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=18 flags=0x58be44)
W/PackageManager( 1471): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=50 flags=0x58be44)
W/PackageManager( 1471): Not granting permission com.sonymobile.permission.CAMERA_STATUS_PROVIDER to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=18 flags=0x58be44)
W/PackageManager( 1471): Not granting permission com.sonymobile.permission.CAMERA_ADDON_NOTIFY_GA to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=18 flags=0x58be44)
W/PackageManager( 1471): Not granting permission com.sonymobile.permission.IMAGE_PROCESSOR to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=2 flags=0x58be44)
W/PackageManager( 1471): Not granting permission com.sonymobile.permission.SYSTEM_UI_VISIBILITY_EXTENSIONS to package com.sonymobile.android.addoncamera.supervideo (protectionLevel=18 flags=0x58be44)
Click to expand...
Click to collapse
And before it crashes:
D/CameraAddonReceiver( 2411): onReceive() intent:Intent { act=com.sonymobile.camera.addon.action.REQUEST_REGISTER flg=0x30 cmp=com.sonymobile.android.addoncamera.supervideo/.addon.CameraAddonReceiver }
E/DatabaseUtils(29276): Writing exception to parcel
E/DatabaseUtils(29276): java.lang.SecurityException: Permission Denial: reading com.sonymobile.cameracommon.provider.CameraCommonProvider uri content://com.sonymobile.cameracommon.provider/cameraparameters from pid=2411, uid=10241 requires com.sonymobile.permission.CAMERA_ADDON_DATA_WRITE, or grantUriPermission()
E/DatabaseUtils(29276): at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:467)
E/DatabaseUtils(29276): at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:394)
E/DatabaseUtils(29276): at android.content.ContentProvider$Transport.query(ContentProvider.java:194)
E/DatabaseUtils(29276): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:116)
E/DatabaseUtils(29276): at android.os.Binder.execTransact(Binder.java:404)
E/DatabaseUtils(29276): at dalvik.system.NativeStart.run(Native Method)
Click to expand...
Click to collapse
@kind3r
Here I heard it worked on the Nexus 5 ( Try This out )
So, you need a deodexed firmware and superuser mod ....
Any luck getting Google Play Store working, now that we have root? I got it to install using ps4ouya, got signed in to the store, but just get "No Connection". That's the farther than I've gotten with other methods (Play Store usually just crashes).
check logs, report back here
Yep same here no connection.
thrashman69 said:
Yep same here no connection.
Click to expand...
Click to collapse
I worked on this yesterday and it looks like its being rejected permission to the internet .. according to logcat.
mastafunk said:
I worked on this yesterday and it looks like its being rejected permission to the internet .. according to logcat.
Click to expand...
Click to collapse
Is this maybe something we could change with XPrivacy?
I/qtaguid (11598): Failed write_ctrl(u 74) res=-1 errno=22
I/qtaguid (11598): Untagging socket 74 failed errno=-22
W/NetworkManagementSocketTagger(11598): untagSocket(74) failed with errno -22
E/DfeApi (11598): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.c
om/fdfe/toc?shh=zen2II1nK1Sx2swLcCn16w 0xe8d195d1 NORMAL 98]
D/Finsky (11598): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.Runtime
Exception: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload,
but got null
The playstore GUI is bombing for me also. However, I'm able to use the Google Services Framework (for example, Tune In Pro, which I have via the Playstore, and which does a license check on startup, seems to be working.)
I launch Playstore from within XBMC, which is why some of the logcat references here are around XBMC:
I/ActivityManager( 648): START u0 {act=android.intent.action.MAIN cat=[android.
intent.category.LAUNCHER] flg=0x10000000 pkg=com.android.vending cmp=com.android
.vending/.AssetBrowserActivity} from pid 5212
V/threaded_app( 5212): Pause: 0x5aa5df40
V/threaded_app( 5212): activityState=13
V/XBMC ( 5212): virtual void CXBMCApp:nPause():
I/AudioManager( 5212): Cleared FLAG_SHOW_UI in setStreamVolume
V/XBMC ( 5212): CAndroidKey: key up (code: 23; repeat: 0; flags: 0x28; alt: n
o; shift: no; sym: no)
I/Activity( 2338): No ActvityExender defined. Proceed with default activity beha
vior.
V/threaded_app( 5212): WindowFocusChanged: 0x5aa5df40 -- 0
V/XBMC ( 5212): virtual void CXBMCApp:nLostFocus():
W/ContextImpl( 648): Calling a method in the system process without a qualified
user: android.app.ContextImpl.sendBroadcast:1353 com.amazon.internal.policy.imp
l.AmazonPhoneWindowManager$SendTopWindowChanged.run:3294 android.os.Handler.hand
leCallback:725 android.os.Handler.dispatchMessage:92 android.os.Looper.loop:137
V/threaded_app( 5212): NativeWindowDestroyed: 0x5aa5df40 -- 0x56fc2ef0
V/threaded_app( 5212): APP_CMD_TERM_WINDOW
V/XBMC ( 5212): virtual void CXBMCApp:nDestroyWindow():
V/XBMC ( 5212): XBMC_DestroyDisplay()
V/XBMC ( 5212): XBMC_Pause(true)
V/threaded_app( 5212): APP_CMD_TERM_WINDOW
I/qtaguid ( 2338): Failed write_ctrl(u 72) res=-1 errno=22
I/qtaguid ( 2338): Untagging socket 72 failed errno=-22
W/NetworkManagementSocketTagger( 2338): untagSocket(72) failed with errno -22
I/ElegantRequestDirector( 2338): I/O exception (org.apache.http.NoHttpResponseEx
ception) caught when processing request: The target server failed to respond
I/ElegantRequestDirector( 2338): Retrying request
D/libEGL ( 2338): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 2338): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 2338): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 2338): <qeglDrvAPI_eglInitialize:265>: EGL 1.4 QUALCOMM build:
PDAVID_AU_LINUX_ANDROID_JB_2.5.4.04.02.02.073.175+PATCH[ES]_msm8960_JB_2.5.4_CL3
406509_release_ENGG (CL3406509)
I/Adreno200-EGL( 2338): Build Date: 01/06/14 Mon
I/Adreno200-EGL( 2338): Local Branch: master
I/Adreno200-EGL( 2338): Remote Branch: quic/jb_2.5.4
I/Adreno200-EGL( 2338): Local Patches: 8eb510a221aaeae58c0ecdd202385ce404871588
PROFILER: Added proper handling of partially filled mipmaps
I/Adreno200-EGL( 2338): 2e6d0a734aa661addd942fe6f373d55a407591a
6 PROFILER: CL3406509: Compressed texture support.
I/Adreno200-EGL( 2338): fdfb486203fdd417c56d12d68e6997ebd0ae872
6 PROFILER: Check fo
D/OpenGLRenderer( 2338): Enabling debug mode 0
I/ActivityManager( 648): Displayed com.android.vending/.AssetBrowserActivity: +
319ms
W/ContextImpl( 648): Calling a method in the system process without a qualified
user: android.app.ContextImpl.sendBroadcast:1353 com.amazon.internal.policy.imp
l.AmazonPhoneWindowManager$SendTopWindowChanged.run:3294 android.os.Handler.hand
leCallback:725 android.os.Handler.dispatchMessage:92 android.os.Looper.loop:137
E/DfeApi ( 2338): [1] DfeRequest.deliverResponse: Null wrapper parsed for reque
st=[[ ] https://android.clients.google.com/fdfe/toc?shh=zen2II1nK1Sx2swLcCn16w 0
xe8d195d1 NORMAL 6]
D/Finsky ( 2338): [1] ErrorStrings.get: No specific error message for: com.andr
oid.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerExceptio
n: expected receiver of type com.google.android.finsky.protos.Response$Payload,
but got null
Google Drive working?
maybe - Youtube plus signin is working for me.
I don't have the Fire Tv but many Android Tv box. Usually when i have problems with google play in some strange firmwares, is because some files in system/etc/permissions are missing. The files inside system/etc/permissions are all the permissions that an app can request from Android.
I suggest to read the list of this files on your tablet / phone in which google play works and copy the missing files in Fire tv / compare different permissions.
This can solve the problem. I'm not sure but is possible.
GMail - account management
Does everyone else have GMail working?
Have Google Drive access through ES File manager. Is the app needed?
Many play store fixes I've seen involve changes to the hosts file. Could this be the case here?
Is there way to delete account data? Tried 'clear data' in play store and gmail and it's still there. No account management.
I thinks the problem with the playstore is permissions related. Maybe someone knows how to change that so it is granted it may work?
Line 431: Bad package setting: package com.google.android.gsf has shared uid 32054 that is not defined
Line 961: Not granting permission android.permission.ACCESS_CACHE_FILESYSTEM to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 967: Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 973: Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER_ADVANCED to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 979: Not granting permission android.permission.BACKUP to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 985: Not granting permission android.permission.MASTER_CLEAR to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 991: Not granting permission android.permission.REBOOT to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 997: Not granting permission android.permission.SET_TIME to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1003: Not granting permission android.permission.STATUS_BAR to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1009: Not granting permission android.permission.WRITE_GSERVICES to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1621: Not granting permission android.permission.ACCESS_CACHE_FILESYSTEM to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1627: Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1633: Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER_ADVANCED to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1639: Not granting permission android.permission.BACKUP to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1645: Not granting permission android.permission.MASTER_CLEAR to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1651: Not granting permission android.permission.REBOOT to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1657: Not granting permission android.permission.SET_TIME to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1663: Not granting permission android.permission.STATUS_BAR to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 1669: Not granting permission android.permission.WRITE_GSERVICES to package com.google.android.gsf (protectionLevel=18 flags=0x8be44)
Line 3481: Start proc com.android.vending for broadcast com.android.vending/com.google.android.finsky.receivers.BootCompletedReceiver: pid=2099 uid=32055 gids={72055, 3003, 1015, 1028, 9001}
Line 3487: Start proc com.google.process.gapps for content provider com.google.android.gsf/.gservices.GservicesProvider: pid=2114 uid=32054 gids={72054, 3003, 1007, 1028, 9001}
Line 3487: Start proc com.google.process.gapps for content provider com.google.android.gsf/.gservices.GservicesProvider: pid=2114 uid=32054 gids={72054, 3003, 1007, 1028, 9001}
Line 3883: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.services.DailyHygiene in 5000ms
Line 5035: START u0 {cmp=com.google.android.gsf/.loginservice.LoginActivity (has extras)} from pid 5989
Line 5041: START u0 {cmp=com.google.android.gsf/.loginservice.RunSetupWizardActivity (has extras)} from pid 2114
Line 5047: START u0 {flg=0x80000 cmp=com.google.android.gsf/.login.AccountIntroActivity (has extras)} from pid 2114
Line 5059: START u0 {cmp=com.google.android.gsf/.login.ChooseAccountActivity (has extras)} from pid 2114
Line 5083: START u0 {cmp=com.google.android.gsf/.login.LoginActivity (has extras)} from pid 2114
Line 5107: START u0 {cmp=com.google.android.gsf/.login.LoginActivityTask (has extras)} from pid 2114
Line 5119: START u0 {cmp=com.google.android.gsf/.login.ShowErrorActivity (has extras)} from pid 2114
Line 5197: netstack: STAT_HUB - App com.google.process.gapps isn't supported
Line 5305: Duplicate finish request for ActivityRecord{42596260 u0 com.google.android.gsf/.loginservice.RunSetupWizardActivity}
Line 5551: START u0 {flg=0x50000000 cmp=com.android.vending/com.google.android.vending.verifier.ConsentDialog (has extras)} from pid 5989
Line 5941: Not granting permission android.permission.ACCESS_CACHE_FILESYSTEM to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5947: Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5953: Not granting permission android.permission.ACCESS_DOWNLOAD_MANAGER_ADVANCED to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5959: Not granting permission android.permission.BACKUP to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5965: Not granting permission android.permission.MASTER_CLEAR to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5971: Not granting permission android.permission.REBOOT to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5977: Not granting permission android.permission.SET_TIME to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5983: Not granting permission android.permission.STATUS_BAR to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 5989: Not granting permission android.permission.WRITE_GSERVICES to package com.google.android.gsf (protectionLevel=18 flags=0x88be44)
Line 8627: [JavaScript Error: "no element found" {file: "https://checkout.google.com/inapp/frontend/app/log" line: 1}]
Line 16615: START u0 {cmp=com.google.android.gsf/.loginservice.LoginActivity (has extras)} from pid 5989
Line 16641: START u0 {cmp=com.google.android.gsf/.loginservice.RunSetupWizardActivity (has extras)} from pid 2114
Line 16647: Displayed com.google.android.gsf/.loginservice.LoginActivity: +89ms (total +216ms)
Line 16653: START u0 {flg=0x80000 cmp=com.google.android.gsf/.login.AccountIntroActivity (has extras)} from pid 2114
Line 16709: Displayed com.google.android.gsf/.login.AccountIntroActivity: +170ms
Line 16811: START u0 {cmp=com.google.android.gsf/.login.ChooseAccountActivity (has extras)} from pid 2114
Line 16847: Displayed com.google.android.gsf/.login.ChooseAccountActivity: +102ms
Line 16961: START u0 {cmp=com.google.android.gsf/.login.LoginActivity (has extras)} from pid 2114
Line 16997: Displayed com.google.android.gsf/.login.LoginActivity: +143ms
Line 17049: Activity idle timeout for ActivityRecord{4267f948 u0 com.google.android.gsf/.loginservice.LoginActivity}
Line 17055: Activity idle timeout for ActivityRecord{42506800 u0 com.google.android.gsf/.loginservice.RunSetupWizardActivity}
Line 22897: START u0 {cmp=com.google.android.gsf/.login.LoginActivityTask (has extras)} from pid 2114
Line 22951: Displayed com.google.android.gsf/.login.LoginActivityTask: +154ms
Line 23117: START u0 {cmp=com.google.android.gsf/.login.ShowErrorActivity (has extras)} from pid 2114
Line 23129: Displayed com.google.android.gsf/.login.ShowErrorActivity: +98ms
Line 25603: START u0 {cmp=com.google.android.gsf/.login.LoginActivityTask (has extras)} from pid 2114
Line 25651: Displayed com.google.android.gsf/.login.LoginActivityTask: +111ms
zulu99 said:
I don't have the Fire Tv but many Android Tv box. Usually when i have problems with google play in some strange firmwares, is because some files in system/etc/permissions are missing. The files inside system/etc/permissions are all the permissions that an app can request from Android.
I suggest to read the list of this files on your tablet / phone in which google play works and copy the missing files in Fire tv / compare different permissions.
This can solve the problem. I'm not sure but is possible.
Click to expand...
Click to collapse
@zulu99 aka Strauzo LMAO! Funny to see you still around after that epic fail over at freaktab. Im curious to know what type of adverse could possibly be caused by adding permissions related files that do not work properly? Possible boot loop? IDK but sounds risky
Is there an alternative for AppOpps for older Android versions?
It is restricted to 4.3 normally.
alwaysbless said:
@zulu99Im curious to know what type of adverse could possibly be caused by adding permissions related files that do not work properly? Possible boot loop? IDK but sounds risky
Click to expand...
Click to collapse
no boot loop, but the permissions to works should be present also in the framework part. Usually dev that strip down android add new permissions but not delete the original. if so the permissions in general can works otherwise no. but the google play problem can be also very different. We should remember that the greatest interest for amazon is run its own market and destroy at all costs the google play store.
However, with the google play services running even paid apps should work.
play store working here following these instructions.
http://forum.xda-developers.com/showthread.php?t=2787813
nhumber said:
play store working here following these instructions.
http://forum.xda-developers.com/showthread.php?t=2787813
Click to expand...
Click to collapse
For real? Have you tested it?
working google play store
hello
it is really working I tried it
I have to do it twice but every thing is working perfect
Here is my step-by-step guide with screenshots for installing the Google Play Store: http://www.aftvnews.com/how-to-install-the-google-play-store-on-the-amazon-fire-tv/
Play store loads,looks good, I click install for an app and nothing happens or downloads