[ROM] [4.4.4] [Jul-31] AOSB Kitkat v1.3.7 | bravo (GSM) | Battery drain fixed!

Gil- · Aug 9, 2014

Hi Spezi !

Nice to see a new update

.

So I Installed it and performance wize it feels very promissing !
I will test it a few days as always but I don't know why the app restore doesn't work like usual.

It might be a pain in the ass to restore everything by hand and it would be great if the gapps would do it like with other rom.

Except this I have no complain right now

.

Edit :
I removed and added some apk so I have the restore back.
Let's try this rom

I still have some zone in the bottom where the touch doesn't work.
Anyone else experience this ?

Will have to check the option to see if there is something missing there.

Edit 2 :
I installed almost everything.
Will still need to fine tune a few things.

Other than that :
The performance are GREAT !
As smooth as evervolv which is already smooth

.

Just had 2 reboot here is one kmsg (for the last one) :
http://spyzor.be/files/kmsg-2014-08-12-08-44-01.txt

After that reboot Wifi didn't work anymore.
I had to reboot again and everything was ok.

Will report back later after I tested a few options AOSB is giving

Gil- · Aug 13, 2014

Arg.

I have a bug.

Thelephony keeps FC. I'm not trying to do anything to get a FC.
I tried to reboot and format cache and wipe but that doesn't change.
I'm making a backup and go back to evervolv.

Looks like almost the same bug as in PA.
Maybe both are related ?

I can generate a bug report if needed.

spezi77 · Aug 13, 2014

Gil- said:
Arg.

I have a bug.

Thelephony keeps FC. I'm not trying to do anything to get a FC.
I tried to reboot and format cache and wipe but that doesn't change.
I'm making a backup and go back to evervolv.

Looks like almost the same bug as in PA.
Maybe both are related ?

I can generate a bug report if needed.

Yes, please take a logcat, so I can compare it with one from PA.

I guess that it is related to Gapps.

ze7zez has found a nice workaround that works with PA rom and I have updated the installation instructions accordingly.

avalonbr · Aug 14, 2014

Have the problem that the screen often times in terms of alone. Although no new or open message is present. Had now been 3 reboots since I use the Rom. Furthermore, the screen flickers often when opening the camera or in apps as well as in the setting menu. Here is a logcat. Hope it Helps find. For tips, I would be grateful.

Saf98 · Aug 15, 2014

avalonbr said:
Have the problem that the screen often times in terms of alone. Although no new or open message is present. Had now been 3 reboots since I use the Rom. Furthermore, the screen flickers often when opening the camera or in apps as well as in the setting menu. Here is a logcat. Hope it Helps find. For tips, I would be grateful.

Is it like like a glitchy layering type flick cos I have sometimes that problem on carbon ROM.

Sent from my HTC Desire using XDA Free mobile app

Gil- · Aug 16, 2014

spezi77 said:
Yes, please take a logcat, so I can compare it with one from PA.

I guess that it is related to Gapps.

ze7zez has found a nice workaround that works with PA rom and I have updated the installation instructions accordingly.

Here is the bugrepport :
http://spyzor.be/files/bugreport-2014-08-16-17-08-12.txt

(sorry for the delay)

spezi77 · Aug 17, 2014

Gil- said:
Here is the bugrepport :
http://spyzor.be/files/bugreport-2014-08-16-17-08-12.txt

(sorry for the delay)

No problem.

Nice, how did you make this? Looks like a complete system dump.

When looking into it, I could not find the same error message as observed in PA. If you or someone else will face the problem with FC of phone.apk, could you please take a logcat by using this command: "adb logcat"? And then just copy the lines which have the exception message. :good:

Gil- · Aug 18, 2014

spezi77 said:
Yes, please take a logcat, so I can compare it with one from PA.

I guess that it is related to Gapps.

ze7zez has found a nice workaround that works with PA rom and I have updated the installation instructions accordingly.

spezi77 said:
No problem.

Nice, how did you make this? Looks like a complete system dump.

When looking into it, I could not find the same error message as observed in PA. If you or someone else will face the problem with FC of phone.apk, could you please take a logcat by using this command: "adb logcat"? And then just copy the lines which have the exception message. :good:

This is a log you can generate with the Developper Tools -> Create a bug report.
You have got every logs in it (last kmsg etc...)

You can just look for this line :

Code:

08-16 17:07:23.557   585  1268 I ActivityManager: Process com.android.phone (pid 1033) has died

I think that's where the issue should be. And it dies also at line

Code:

08-16 17:07:54.548   585  1022 I ActivityManager: Process com.android.phone (pid 3238) has died

It died 2 times before I was able to create the log. When it dies I have to enter my pin code again.

Tell me if you still need the adb logcat.

spezi77 · Aug 18, 2014

Gil- said:
This is a log you can generate with the Developper Tools -> Create a bug report.
You have got every logs in it (last kmsg etc...)

You can just look for this line :

Code:

08-16 17:07:23.557 585 1268 I ActivityManager: Process com.android.phone (pid 1033) has died

I think that's where the issue should be. And it dies also at line

Code:

08-16 17:07:54.548 585 1022 I ActivityManager: Process com.android.phone (pid 3238) has died

It died 2 times before I was able to create the log. When it dies I have to enter my pin code again.

Tell me if you still need the adb logcat.

Ok, no additional logcat needed. :good:

Here is the issue (which is different from PA):

Code:

08-16 17:07:20.545  1033  1033 E ActivityThread: Failed to find provider info for telephony
08-16 17:07:20.565  1033  1033 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x418b5ce0)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: FATAL EXCEPTION: main
08-16 17:07:20.565  1033  1033 E AndroidRuntime: Process: com.android.phone, PID: 1033
08-16 17:07:20.565  1033  1033 E AndroidRuntime: java.lang.IllegalArgumentException: Unknown URL content://telephony/carriers/current
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at android.content.ContentResolver.insert(ContentResolver.java:1186)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at com.android.internal.telephony.gsm.GSMPhone.updateCurrentCarrierInProvider(GSMPhone.java:1611)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at com.android.internal.telephony.gsm.GSMPhone.handleMessage(GSMPhone.java:1361)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:136)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:5151)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at java.lang.reflect.Method.invokeNative(Native Method)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Method.java:515)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:796)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:612)
08-16 17:07:20.565  1033  1033 E AndroidRuntime: 	at dalvik.system.NativeStart.main(Native Method)

Let's see if it can be fixed in a future release. Maybe for now, you could try to update your APN carrier settings. But don't ask me how this goes.. search the forum, please.

Upgreydd · Aug 26, 2014

ROOT access issue

Hi. Thank you for your work. ROM is great. I have one question about ROOT access. Everything is OK with it? I have problem with LuckyPatcher application. It couses only in your ROM. I've tried reinstall your ROM something about 10 times and always have the sam issue.
Lucky Patcher ask for ROOT access, I grant it and when applying custom patch it stuck with "root access" message. This issue doesn't exist in 4.4.4 Carbon and Beanstalk.

spezi77 · Aug 26, 2014

Upgreydd said:
Hi. Thank you for your work. ROM is great. I have one question about ROOT access. Everything is OK with it? I have problem with LuckyPatcher application. It couses only in your ROM. I've tried reinstall your ROM something about 10 times and always have the sam issue.
Lucky Patcher ask for ROOT access, I grant it and when applying custom patch it stuck with "root access" message. This issue doesn't exist in 4.4.4 Carbon and Beanstalk.

Both, Carbon and Beanstalk have baked in CM's superuser -- whereas AOSB is using ChainFire's superSU. I guess that this is where your problem comes from.

vasili_defy · Aug 27, 2014

hey guys , is anybody getting systemui stopped error??
I think this is due to ,I deleted omniswitch.apk from priv-app folder!!
Spezi is this right??

Note:I have downloaded omniswitch apk from the thread , and now trying again to flash!!
nope still no success!! still getting systemui has stopped error!!

captaindeep · Sep 10, 2014

HEY EVERYONE .
IM CREATING WHATSAPP GROUP FOR ALL AOSB MEMEBERS YOU CAN DISCUSS OR SHARE YOUR PROBLEM
IF ANYONE INTRESTED MESSGAE ME ON WHATSAPP +919988848284 . WITH YOUR NAME .
OUR GREAT DEV Hany Alsamman WILL BE ALSO IN IT

.
THANKS

Sent from my GT-I9100G using XDA Premium 4 mobile app

ze7zez · Sep 10, 2014

captaindeep said:
HEY EVERYONE .
IM CREATING WHATSAPP GROUP FOR ALL AOSB MEMEBERS YOU CAN DISCUSS OR SHARE YOUR PROBLEM
IF ANYONE INTRESTED MESSGAE ME ON WHATSAPP [...cut...] . WITH YOUR NAME .
OUR GREAT DEV [...cut...] WILL BE ALSO IN IT .
THANKS

Why are you yelling?

XDA forum is here to discuss.

.

andy hall · Sep 11, 2014

vasili_defy said:
hey guys , is anybody getting systemui stopped error??
I think this is due to ,I deleted omniswitch.apk from priv-app folder!!
Spezi is this right??

Note:I have downloaded omniswitch apk from the thread , and now trying again to flash!!
nope still no success!! still getting systemui has stopped error!!

Not sure on this ROM but I have deleted Omniswitch APK from other of Spezi77 roma with no issue, have you enabled softkey (navigation bar) by any chance?

kakofonija · Dec 6, 2014

Good rom, for smooth performance I changed few things...
in init.d enable, zipalign apps, clear cache, file system speedup and decrease read ahead values from 2048 to 1024... after reboot rom is much more responsive...

thanks spezi

dado023 · Dec 6, 2014

kakofonija said:
Good rom, for smooth performance I changed few things...
in init.d enable, zipalign apps, clear cache, file system speedup and decrease read ahead values from 2048 to 1024... after reboot rom is much more responsive...

thanks spezi

ej, kako se to sve promini na već instaliranom romu?

eng: would you be so kind and explain how to change that on already installed rom.?

kakofonija · Dec 6, 2014

dado023 said:
ej, kako se to sve promini na već instaliranom romu?

eng: would you be so kind and explain how to change that on already installed rom.?

settings - interface - init.d and there are all of settings you need to change... živio

nonline · Dec 7, 2014

After setting A2SD desire stuck on boot. Any ideas? I cleared cache & dalvik, should I run installation once again?

I did it from the scratch, no luck :|
20 minuts and still counting on AOSB boot logo.

spezi77 · Dec 7, 2014

nonline said:
After setting A2SD desire stuck on boot. Any ideas? I cleared cache & dalvik, should I run installation once again?

I did it from the scratch, no luck :|
20 minuts and still counting on AOSB boot logo.

Pls post logcat to have a look into it.

Sent from my Nexus™4 ?

[ROM] [4.4.4] [Jul-31] AOSB Kitkat v1.3.7 | bravo (GSM) | Battery drain fixed!

Senior Member

Senior Member

Recognized Developer /Inactive RC

Member

Attachments

Senior Member

Senior Member

Recognized Developer /Inactive RC

Senior Member

Recognized Developer /Inactive RC

Member

Recognized Developer /Inactive RC

Senior Member

Senior Member

Recognized Contributor

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Recognized Developer /Inactive RC

Similar threads

Top Liked Posts