[NIGHTLY/KERNEL][USER] UNOFFICIAL CM9 + 3.0.x Kernel for K-Fire [3.0.31+ 06-28]

abarax · May 11, 2012

webdroidmt said:
Would anyone having problems with Play Store apps like to try a little experiment? I'm running Hashcode's current full rom/kernel and I don't seem to be having this issue. Prior to this, I was running gederom 5/7 and even though gapps are included with this rom, I still flashed 0429 gapps.

When I flashed Hashcode's rom today, I just wiped cache/dalvik, installed the rom and all was good. So, how about just repeating what I did to see if that works. Flash gederom, flash gapps, see if you have proper Play Store apps access. If you do, just wipe cache/dalvik and reflash Hashcode's 5/10 full rom.

I realize this not scientific but it is a way of troubleshooting. Maybe gederom leaves something from its install, especially since I'm only wiping cache & dalvik. I've seen something like this before with CM9 on the Touchpad and even the Nook Color. Worth a try....nothing to lose, maybe something to gain.

Btw, I already had Chrome installed but I just uninstalled it and was able to reinstall again from Play Store with no problem. I did make a nandroid beforehand just in case. Also, I'm sure most of you know that changing DPI from 160 will cause Play Store issues, especially with Chrome.

EDIT: I'm just thinking of things that came up with CM9 on the TP & NC regarding Play Store. Check and make sure your date is correct in settings-date & time, sometimes a rom install will knock it out of whack.

Mike T

Tried it, and when I pulled up the Play Store in gedeROM, the apps which had given the option to either install, open, or uninstall were now showing as incompatible. So I tried to flash the 5/10 Hashcode ROM along with gapps, and those apps (Facebook, Facebook Messenger, Chase, etc.) were still showing as incompatible, and missing if you ran a search. One of my friends on here who had flashed the 5/10 ROM and restored his apps and data with Titanium Backup decided to look for Facebook in the Play Market, and it was showing as incompatible.

Modifying the build.prop file to match the Galaxy Nexus was unsuccessful. Same issue. I tried wiping the sdcard and flashing Hashcode's 4/28 ROM (which he has removed from xda for some reason) along with the 4/29 gapps package, and everything was in the Play Market. When I did another sdcard wipe, and installed the 5/10 ROM with the 4/29 gapps package, the apps were gone. I tried again to modify the build.prop file, but no luck.

So the conclusion is that something changed between the 4/28 and 5/10 Hashcode ROMs. It's not the build.prop file, but something possibly in the device tree that may have been changed, and is confusing the Play Market as to what sort of device it's attempting to recognize.

embhorn · May 11, 2012

I flashed over AOKP, wiped caches and rebooted. Play store was not installed, so I just went to goo.im and found the latest version (as described in the dev thread for 3.0 Kernel).

Everything appears to be working as expected. I'm still looking for a volume widget. Also I miss the Trebuchet launcher from AOKP.

(Just saw that Lithium76 built a newer ROM with Hashc0de's latest kernel... Hmmm.)

webdroidmt · May 11, 2012

abarax said:
Tried it, and when I pulled up the Play Store in gedeROM, the apps which had given the option to either install, open, or uninstall were now showing as incompatible. So I tried to flash the 5/10 Hashcode ROM along with gapps, and those apps (Facebook, Facebook Messenger, Chase, etc.) were still showing as incompatible, and missing if you ran a search. One of my friends on here who had flashed the 5/10 ROM and restored his apps and data with Titanium Backup decided to look for Facebook in the Play Market, and it was showing as incompatible.

Modifying the build.prop file to match the Galaxy Nexus was unsuccessful. Same issue. I tried wiping the sdcard and flashing Hashcode's 4/28 ROM (which he has removed from xda for some reason) along with the 4/29 gapps package, and everything was in the Play Market. When I did another sdcard wipe, and installed the 5/10 ROM with the 4/29 gapps package, the apps were gone. I tried again to modify the build.prop file, but no luck.

So the conclusion is that something changed between the 4/28 and 5/10 Hashcode ROMs. It's not the build.prop file, but something possibly in the device tree that may have been changed, and is confusing the Play Market as to what sort of device it's attempting to recognize.

Really weird, man. Especially that when you went back to gederom it still wouldn't work, since I don't think that gederom's 5/7 release had all the same Hashcode commits of 5/10??? I wish I could help but I'm out of ideas at this time. Another member suggested using the "nullifier" app in one of Hellfire's threads here in the dev forum, which will do a thorough cleanup.

Anyway, hope you get it solved.

Mike T

Hashcode · May 11, 2012

After checking differences in the build.prop between 4/28 ROM and the 5/10 ROM this was pointed out:

ro.build.display.id=IMM76D
VS.
ro.build.display.id=cm_otter-userdebug 4.0.4 IMM76I eng.hashcode.20120510.014002 test-keys

Would someone with a Market App download issue do the following to see if this change fixes it:
- change the build.prop setting to: ro.build.display.id=IMM76I
- in Settings -> Apps, change to "ALL" tab and select "Google Play Store". Then click the "Clear data" button
- Reboot the device
- Check market for apps that were previously market incompatible.

Hashcode · May 11, 2012

iesvs said:
I just noticed I'm getting that audio shutoff glitch, and it's really random. It's happened in X-Men and Caustic, if that matters at all. I'm sure there will be more. I remember others mentioning this, but couldn't find the posts. I just flashed Hashcode's new ROM over gedemis' previous build just wiping dalvik and cache, but everything else looks like its running smooth as can be. Just throwing that out there.

When you say audio shutoff bug.. as in the audio goes away till you reboot? or is it temporary? How long does it last?

If it happens again to you, can you grab a logcat via: adb logcat > logcat.txt
And also get dmesg output by doing: adb shell "cat /proc/kmsg" > kmsg.txt

Normally I don't want people to post those logs in a public forum in case there's sensative information in them, so you can use my email if you want: hashcode0f at gmail.com

abarax · May 11, 2012

Hashcode said:
After checking differences in the build.prop between 4/28 ROM and the 5/10 ROM this was pointed out:

ro.build.display.id=IMM76D
VS.
ro.build.display.id=cm_otter-userdebug 4.0.4 IMM76I eng.hashcode.20120510.014002 test-keys

Would someone with a Market App download issue do the following to see if this change fixes it:
- change the build.prop setting to: ro.build.display.id=IMM76I
- in Settings -> Apps, change to "ALL" tab and select "Google Play Store". Then click the "Clear data" button
- Reboot the device
- Check market for apps that were previously market incompatible.

I tried it, and no change. I've tried all of the build.prop files from all of the current ICS builds running the 3.0 kernel, and no luck. That's why I'm wondering if something deeper in the 5/10 ROM is causing the issue.

sthomas38 · May 11, 2012

Hashcode said:
When you say audio shutoff bug.. as in the audio goes away till you reboot? or is it temporary? How long does it last?

If it happens again to you, can you grab a logcat via: adb logcat > logcat.txt
And also get dmesg output by doing: adb shell "cat /proc/kmsg" > kmsg.txt

Normally I don't want people to post those logs in a public forum in case there's sensative information in them, so you can use my email if you want: hashcode0f at gmail.com

Hey Hash

,

Expecting the same bug on SOME games like Cut the Rope, Mega Jump... but for example never on Death Rally

. The sound stops randomly and comes back as soon as you quit the game, no need for a reboot. I can't remember if the sound used to come back IG after stoping. I will try to catch all the logs needed for tomorrow

.

EDIT: Got them, I'm sending you a PM

.

webdroidmt · May 11, 2012

abarax said:
I tried it, and no change. I've tried all of the build.prop files from all of the current ICS builds running the 3.0 kernel, and no luck. That's why I'm wondering if something deeper in the 5/10 ROM is causing the issue.

Take a look at this link: http://www.androidtablets.net/forum...ok-color-your-device-not-compatible-item.html

Check out the reply in post# 2 by one of the mods for this forum. He's of the belief that the problem is on Google's end. He mentions two things in particular that may be of value.

1. signing out of your Google account and signing in. See his post.

2. Clearing data in Google Services framework, as well as Play Store.

Trying to help, so I hope this does the trick. Unfortunately, there was no response from the OP as to whether her/his issue was solved.

Mike T

abarax · May 11, 2012

webdroidmt said:
Take a look at this link: http://www.androidtablets.net/forum...ok-color-your-device-not-compatible-item.html

Check out the reply in post# 2 by one of the mods for this forum. He's of the belief that the problem is on Google's end. He mentions two things in particular that may be of value.

1. signing out of your Google account and signing in. See his post.

2. Clearing data in Google Services framework, as well as Play Store.

Trying to help, so I hope this does the trick. Unfortunately, there was no response from the OP as to whether her/his issue was solved.

Mike T

Just tried that, and same problem. I'm just glad I backed all my apps in Titanium. I just can't update anything until this gets resolved.

Sent from my Amazon Kindle Fire using xda premium

webdroidmt · May 11, 2012

New Google Play Store 3.5.19 available, maybe it'll have some magic for those with device not compatible issues.

Mike T

veeman · May 11, 2012

Battery drain on this is crazy! This morning before I went to school, it was at 72%. 7 hours later, after school, it was at 40%. That was while it was asleep. D:

abarax · May 11, 2012

webdroidmt said:
New Google Play Store 3.5.19 available, maybe it'll have some magic for those with device not compatible issues.

Mike T

Unfortunately, no change. Since Hashcode's 4/28 build and the Play Store were "playing well together (pun intended)," and that modifying the build.prop file hasn't worked, I'm convinced something else is afoot within the build itself.

SarcasticSapien · May 12, 2012

Play Store Issues

For what it's worth, I've been using Hash's ROM since Kernel #4. Flashed ROM to #9 yesterday and no problem downloading apps directly from the KF or sending them to my KF from the play website.

airmaxx23 · May 12, 2012

Which apps are coming up "device not compatible"?

kitsunisan · May 12, 2012

Has everyone with the market issue started clean? Full data/cache/dalvik wipe? And just to try to find some commonality, which rom are those with issues coming from?

rstanaford · May 12, 2012

I did, yes. Full wipe, save for SD Card, of course. Apps that failed to automatically re-install and have since shown as "incompatible" include...

Twitter
Facebook
Weatherbug

Aside from that, awesome work Hash.

DeerSteak · May 12, 2012

I'm upgrading from CM7 - how long should the first boot take? I made a backup and then wiped system, cache, data, and dalvik. Flashed just the ROM, no other ZIPs. It's been on the CM9 boot animation for like 10 minutes now.

soupmagnet · May 12, 2012

DeerSteak said:
I'm upgrading from CM7 - how long should the first boot take? I made a backup and then wiped system, cache, data, and dalvik. Flashed just the ROM, no other ZIPs. It's been on the CM9 boot animation for like 10 minutes now.

If you used CWM to flash it then, possibly forever. You need TWRP to flash 3.0 kernel roms.

scidon37 · May 12, 2012

DeerSteak said:
I'm upgrading from CM7 - how long should the first boot take? I made a backup and then wiped system, cache, data, and dalvik. Flashed just the ROM, no other ZIPs. It's been on the CM9 boot animation for like 10 minutes now.

Flash cm9 again.

Sent from my Amazon Kindle Fire using Tapatalk 2

DeerSteak · May 12, 2012

Oh. That explains it. I have CWM installed. I was able to restore my backup.

So another question then - how can I get TWRP installed without a USB cable? Is that possible?

[NIGHTLY/KERNEL][USER] UNOFFICIAL CM9 + 3.0.x Kernel for K-Fire [3.0.31+ 06-28]

Senior Member

Senior Member

Senior Member

Senior Recognized Developer

Senior Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Retired Forum Moderator

Senior Member

Senior Member

Similar threads

Top Liked Posts