2233 replies to this topic

[cmh714]

ZKK, I know youre working on it all.....just for you and anyone else, I installed the new Google Keep app, and it keeps crashing....

[ZKK007]

Anyone else notice the battery go from 30% to 20% really quickly, or is it just me?

[anuglx]

Hi

I flashed the latest update "cdma_spyder_9.8.2O-72_VZW-16_1ff" with RSD lite... and then Rooted my Phone with razr Blade...

Then i installed Bootstrap 3.11 and i boot into recovery, created a new Rom Slot and did Wiping(Factory Reset, Cahe, Dalvik Cache, System) twice. Then i installed the latest Aviator 3.0.0 , then did a wiping cahce twice. Then Clicked on the reboot. What is happening is its returning to recovery only... Please help.....I need this Rom to b flashed Soon... For that only i updated from .8 to .16

[subzero2000]

Anyone besides me having issues with the latest Google+ update that came out yesterday? It seems like it launches a completely transparent window that keeps me from interacting with anything on the phone until I hit home or back. I've cleared cache and Dalvik, cleared data for Google+, uninstalled and reinstalled Google+, all to no avail. It works fine on my stock slot, as well as on a KEXEC AOKP nightly, so it appears to be an issue with just Aviator...

[subzero2000]

Ok, a slight update on my Google+ issue; launching Google+ yields the following via "adb logcat". Looks like a signature mismatch somwhere to me.

Please Login or Register to see this Hidden Content

[subzero2000]

On the Google+ issue, I just made a nandroid backup and reinstalled Aviator v3.0.0 cleanly, problem persists. I suspect it's a difference in the Google binaries, probably due to signatures. I diffed the stock deodexed to Aviator (specifically the system folders), and noted the following:

Please Login or Register to see this Hidden Content

Do the binaries in /system/app really need to differ / be resigned on a custom ROM? I find that I can replace them without apparent issue, so I am wondering why this is, if anyone has a good explanation.

Thanks.

[ZKK007]

Do the binaries in /system/app really need to differ / be resigned on a custom ROM? I find that I can replace them without apparent issue, so I am wondering why this is, if anyone has a good explanation.

Thanks.

I had to resign the ROM when I added the pulldown toggles. I have just started rebuilding the ROM from a system pull but it will take a few days to get done

[subzero2000]

ZKK007,

Well, as a test, I replaced every APK that differed with the ones from the deodexed 98.72.16 stock ones, and it sure was broken. However, it did allow me to run Google+ long enough for it to be able to tell me that it depended upon "Google Play services" (GmsCore.apk), so I think my next test in the interim will be to replace Phonesky.apk and GmsCore.apk as a test to see what happens. Weird issue, but stellar ROM otherwise. I'm looking forward to the rebuilt ROM you mentioned, this is just as a stop-gap measure, and relatively safe since I have a full nandroid backup.

Thanks again for a great ROM and the hard work you've put into it.

[ZKK007]

Well, good news so far. The set up process currently has no errors! Even when I haven't deleted and re created the ROM slot, but just wiped it. Let hope progress continues like this and I can get this done in the next day or two

[subzero2000]

ZKK007,

I managed to get Google+ to work last night, it was a signature issue. Google+ evidently (now) depends upon Google Play services (GsmCore.apk), and doesn't like the signature that's on GsmCore.apk in the Aviator ROM, so what I had to do was replace every system apk that uses the same shared user id (com.google.uid.shared, which on my phone is user id 10033; being that's it's Unix based, I assume numerical user id could change, but this is what worked for me). I found which packages listed in /data/system/packages.xml were using user id 10033 (NetworkLocation.apk, GoogleServicesFramework.apk GoogleContactsSyncAdapter.apk, GoogleLoginService.apk, and GsmCore.apk), replaced them with the ones from the deodexed stock 98.72.16 release, commented out the shared user com.google.uid.shared in /data/system/packages.xml), rebooted and cleared Cache and Dalvik, then installed Google+. Worked first time. I did have to set back up my Google accounts, but I've had no issues since, and Google+ works just fine now. The shared user com.google.uid.shared was recreated in /data/system/packages.xml during reboot, and may or may not have been necessary, but since I've seen issues come up due to shared user ids already existing, I did it just to be safe.

My gut instinct tells me that the only system APKs that need to be resigned are the ones that use the same shared user id in /data/system/packages.xml, but since I don't know which APK provides the drop-down toggles, I don't know which ones those might be.

I thought my findings might be helpful to you as rebuild the ROM from a system dump as you described earlier. Keep rocking out this great ROM!

[ZKK007]

ZKK007,

I managed to get Google+ to work last night, it was a signature issue. Google+ evidently (now) depends upon Google Play services (GsmCore.apk), and doesn't like the signature that's on GsmCore.apk in the Aviator ROM, so what I had to do was replace every system apk that uses the same shared user id (com.google.uid.shared, which on my phone is user id 10033; being that's it's Unix based, I assume numerical user id could change, but this is what worked for me). I found which packages listed in /data/system/packages.xml were using user id 10033 (NetworkLocation.apk, GoogleServicesFramework.apk GoogleContactsSyncAdapter.apk, GoogleLoginService.apk, and GsmCore.apk), replaced them with the ones from the deodexed stock 98.72.16 release, commented out the shared user com.google.uid.shared in /data/system/packages.xml), rebooted and cleared Cache and Dalvik, then installed Google+. Worked first time. I did have to set back up my Google accounts, but I've had no issues since, and Google+ works just fine now. The shared user com.google.uid.shared was recreated in /data/system/packages.xml during reboot, and may or may not have been necessary, but since I've seen issues come up due to shared user ids already existing, I did it just to be safe.

My gut instinct tells me that the only system APKs that need to be resigned are the ones that use the same shared user id in /data/system/packages.xml, but since I don't know which APK provides the drop-down toggles, I don't know which ones those might be.

I thought my findings might be helpful to you as rebuild the ROM from a system dump as you described earlier. Keep rocking out this great ROM!

Thanks. Yeah, I knew it was the signatures as I had to resign a few and I probably over did it I'm working on getting away with resigning it so hopefully we won't have signature issues again

[mrp0783]

Hey guys, awesome ROM!!! Quick question, my battery life seems to be off a bit. I looked at GSAM battery monitor and I saw the Kernel was sucking a lot of juice. Is there some setting I should change?

[ZKK007]

Hey guys, awesome ROM!!! Quick question, my battery life seems to be off a bit. I looked at GSAM battery monitor and I saw the Kernal was sucking a lot of juice. Is there some setting I should change?

Is your phone going into deep sleep? You can check with CPUSpy (Free). If not, wipe cache and dalvik cache and then check.

I'm not too far off finishing the next build and it looks like this will be a lot more error free. I built the whole thing from a system pull so it will be a fresh start. You might be able to test that and see if that helps if the above doesn't.

[mattkilla]

well MR. ZK i finally made the switch and joined the .16 crew. I had my last version with the pink floyd theme back on .08. It would constantly boot loop, old news! So glad i made the switch because this ROM kicks donkey butt more than the last. To me, everything has been improved. And finally i am back to my regular battery times on Aviator. I couldnt get 24 hrs out of most the others. Loving this man, definitely my DD for now.

Hey guys, awesome ROM!!! Quick question, my battery life seems to be off a bit. I looked at GSAM battery monitor and I saw the Kernel was sucking a lot of juice. Is there some setting I should change?

yea my kernel usually always uses about 10 - 15% of battery for me. I am still getting outstanding stats though!

Please Login or Register to see this Hidden Content

 

Please Login or Register to see this Hidden Content

  132.96KB   5 downloads

[squidward2016]

Has anyone noticed Google keep doesn't work? I wiped dalvik and cache and it still force closes instantly

[ZKK007]

Has anyone noticed Google keep doesn't work? I wiped dalvik and cache and it still force closes instantly

I think it's a signature issue which I'm working on fixing

[squidward2016]

Also I saw you guys talking about beats audio but my problem is that it ALWAYS force closes when I click it... With music playing or not

[fantasticrat]

My stock SMS app disappeared on upgrade to 3.0.0, and I can't send text messages now at all from any 3rd party app either. What's up?

[ZKK007]

My stock SMS app disappeared on upgrade to 3.0.0, and I can't send text messages now at all from any 3rd party app either. What's up?

That's odd. Did you do a clean, fresh install?

[claps1775]

Nice ROM. Is there any way to chance the keyboard back to OEM?