-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][ICSense3.6] Senseless Kingdom.
- Thread starter legmando33
- Start date
-
- Tags
- htc evo design
The informant
Well-Known Member
Happens to me alot and it's very annoying because I don't know who's calling half of the time
I'm thinking the caller id thing might be related to another problem I'm having. In apps that access the contacts list, sometimes it takes over 10 seconds for the contact list to load. So far I've noticed it in DialerOne when I do a T9 search, in gmail when adding email address, and in chomp sms when adding new recipient. Doesn't happen all the time...seems like sometimes it caches the contacts list maybe?
So I did a logcat once when I had the problem. Here's where I started my T9 search in DialerOne:
[HIGH]05-27 17:46:46.748 I/ActivityManager( 2313): Displayed kz.mek.DialerOne/.DialerActivity: +1s178ms[/HIGH]
Then I found this line at about the time it actually returned the T9 results I was waiting for:
[HIGH]05-27 17:46:58.870 W/HtcContactsProvider2(26669): android.content.pm.PackageManager$NameNotFoundException: Application package com.android.htccontacts not found[/HIGH]
So I did a logcat once when I had the problem. Here's where I started my T9 search in DialerOne:
[HIGH]05-27 17:46:46.748 I/ActivityManager( 2313): Displayed kz.mek.DialerOne/.DialerActivity: +1s178ms[/HIGH]
Then I found this line at about the time it actually returned the T9 results I was waiting for:
[HIGH]05-27 17:46:58.870 W/HtcContactsProvider2(26669): android.content.pm.PackageManager$NameNotFoundException: Application package com.android.htccontacts not found[/HIGH]
legmando33
Android Enthusiast
Seems like it calls out for the HTC contacts that were replaced with aosp contacts. Hmm. I might do some poking around. Haven't been able to do anything since I don't have the device anymore. Anyone interested in a little update for this? Anything anyone wants added?
Edit: Also can someone make me a list of the bugs??
The informant
Well-Known Member
If we could get MMS and the contacts fixed that would be great!
Went back through most of the thread...here's what I saw:
1. contacts
2. MMS
3. strange battery readings? (dreamstate83, page 3)
4. req: settings option to disable fast boot (lazyprizm, page 3)
Aside from #1, just compiling what others have said. Personally I haven't had any issues with battery readings. I can receive MMS, don't think I can send...but I don't use mms much.
I'm on Boost, I'd be happy to help test, or help if I can. Best ROM I've ever used!
BTW, I know it's been a while ago, but hope your police test went okay...been through a few of those myself.
1. contacts
2. MMS
3. strange battery readings? (dreamstate83, page 3)
4. req: settings option to disable fast boot (lazyprizm, page 3)
Aside from #1, just compiling what others have said. Personally I haven't had any issues with battery readings. I can receive MMS, don't think I can send...but I don't use mms much.
I'm on Boost, I'd be happy to help test, or help if I can. Best ROM I've ever used!
BTW, I know it's been a while ago, but hope your police test went okay...been through a few of those myself.
legmando33
Android Enthusiast
Alright, I'll see what I can do tomorrow. Thank you
And about the test, got to the oral interviews but didn't get passed that because I live with someone that has a felony. Suuucks, don't even talk to the guy
Awesome, thanks man! I tried playing around with it, but I was pretty lost. I've been programming for years (started on FORTRAN 66 back in the day), but I'm a total noob with android. I was playing around decompiling apks and stuff, but didn't really even know where to look.Alright, I'll see what I can do tomorrow. Thank you
Man, that stinks...and I know the feeling. Hope you at least get another shot at it...they have a hiring age limit here in my state, and I'm over it now.And about the test, got to the oral interviews but didn't get passed that because I live with someone that has a felony. Suuucks, don't even talk to the guy
EDIT: This didn't work after all...started having the delays again the next day.
I *think* I found a solution to the contacts problem. I've been using my phone for several hours since I applied this fix, so far with no problems and no freeze/lag in dialer/sms/etc. (Before I was getting the lag every few minutes) Caller id seems to be more responsive too.
I replaced /system/apps/ContactProvider.apk with the same file from the bluekingdom ROM. From looking at logcat I figured the problem was in com.android.providers.contacts ... and I finally figured out where that code lives. Started comparing that file in different ROMs, found out the one in bluekingdom (also sense-less) was different...so I figured what the heck.
I *think* I found a solution to the contacts problem. I've been using my phone for several hours since I applied this fix, so far with no problems and no freeze/lag in dialer/sms/etc. (Before I was getting the lag every few minutes) Caller id seems to be more responsive too.
I replaced /system/apps/ContactProvider.apk with the same file from the bluekingdom ROM. From looking at logcat I figured the problem was in com.android.providers.contacts ... and I finally figured out where that code lives. Started comparing that file in different ROMs, found out the one in bluekingdom (also sense-less) was different...so I figured what the heck.
jmphillips76
Newbie
very nice rom been using this one with buttered toast and battery life is doubled (only use phone on wifi)
legmando33
Android Enthusiast
Aww that sucks. Well I applied for the CDCR (Corrections) and so far everything has been good. Passed my physical and written. Now they're doing a background investigation. Been pretty busy so sorry for no update.
hoping I get some free time some time this week though.Just wanted to check in on a possible update, and also report some things I've found out on the contacts thing.
1. I tried a straight AOSP 4.0.3 version of contactsprovider.apk. It actually worked pretty good...well, it fixed the lag problem. But one major problem: it couldn't write to the phone log after a phone call. the dialer would crash every time, and no phone log entry. I couldn't figure out why...my smali skills aren't very good yet.
2. Switched back to Fuziion for a while (needed stock dialer for ## stuff), and noticed that the android.process.acore (contacts provider) had an OOM setting of -17! On the senseless ROM it's usually around 7 or so. So acore almost never seems to get closed on fuziion, whereas it gets closed frequently on senseless.
So...since the lag only happens when acore gets closed and then has to be reopened...is that the issue?
I have no idea how the OOM value gets set initially...like when the service is first started. Changing it after the fact doesn't seem to work (i've tried that with autokiller) ... but there has to be a way to do it when the process is started.
1. I tried a straight AOSP 4.0.3 version of contactsprovider.apk. It actually worked pretty good...well, it fixed the lag problem. But one major problem: it couldn't write to the phone log after a phone call. the dialer would crash every time, and no phone log entry. I couldn't figure out why...my smali skills aren't very good yet.
2. Switched back to Fuziion for a while (needed stock dialer for ## stuff), and noticed that the android.process.acore (contacts provider) had an OOM setting of -17! On the senseless ROM it's usually around 7 or so. So acore almost never seems to get closed on fuziion, whereas it gets closed frequently on senseless.
So...since the lag only happens when acore gets closed and then has to be reopened...is that the issue?
I have no idea how the OOM value gets set initially...like when the service is first started. Changing it after the fact doesn't seem to work (i've tried that with autokiller) ... but there has to be a way to do it when the process is started.