FORUMS

HTC’s New Ad Campaign And What It Really Means

HTC has just released three new blind test adverts comparing app loading … more

XDA Picks: Best Apps of the Week (June 27 – July 4)

Apps are at the front and center of any smartphone experience, and with over a … more

HTC One M9 Developer Edition Android 5.1 OTA

The Developer Edition of the HTC One M9 is receiving an over-the-air update to Android 5.1. … more

Index Project For XDA Device Subforums

Another ambitious project from the collaborative efforts of Recognized Contributors and Forum … more

[APP][4.0+][v1.3] Identiconizer! - Identicons For Your Contacts, [XPOSED] Optional

6,190 posts
Thanks Meter: 8,294
 
By GermainZ, Forum Moderator / Recognized Developer / XDA Portal Team on 15th April 2014, 06:05 PM
Post Reply Subscribe to Thread Email Thread
18th June 2015, 04:13 PM |#181  
Mike B.'s Avatar
Senior Member
/dev/null
Thanks Meter: 1,019
 
Donate to Me
More
Quote:
Originally Posted by breversa

[LIST]
...
BTW, I've also been using use the Clarity Xposed module (http://www.repo.xposed.info/module/c....kmark.clarity) for some time but I'm almost 100% certain that the issues with Iconizer! appeared before that.

To be 100% certain, it might be useful to temporarily disable clarity and DAVdroid (reboot first) and try again, possibly after creating a new non-synced no-icon contact.
 
 
18th June 2015, 04:30 PM |#182  
GermainZ's Avatar
OP Forum Moderator / Recognized Developer / XDA Portal Team
Thanks Meter: 8,294
 
More
Quote:
Originally Posted by breversa

Would that be a permission problem ? I tend to be very restrictive about them.

Which permissions are you blocking? Identiconizer! doesn't need or request access to the Internet, so there should be no need to block any permission.

Quote:
Originally Posted by Mike B.

Looking at a logcat may help you determine what goes wrong when. Sometimes, the logs help recognize a trivial overlooked issue.

Yup, though I doubt anything useful would appear unless I build an APK with extra logging.

Quote:
Originally Posted by breversa

  • I started up Iconizer! and tapped "Remove identicons".
  • The notification area shows my contacts being parsed/processed (I have a few hundred of them, most with identicons). No icon actually gets removed (note that the contacts are synced using DAVdroid)
  • Using CatLog from F-Droid, I get several (about 6) such error :
    Code:
    E/SpannableStringBuilder(5013): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length


---------- Post added at 04:25 PM ---------- Previous post was at 04:14 PM ----------



Could they be related ?

BTW, I've also been using use the Clarity Xposed module (http://www.repo.xposed.info/module/c....kmark.clarity) for some time but I'm almost 100% certain that the issues with Iconizer! appeared before that.

Clarity shouldn't be an issue. If you're going to get a logcat, though, please get an unfiltered one. Thanks
18th June 2015, 06:18 PM |#183  
Junior Member
Thanks Meter: 5
 
More
Quote:
Originally Posted by GermainZ

Which permissions are you blocking? Identiconizer! doesn't need or request access to the Internet, so there should be no need to block any permission.

I use the privacy option to block all access to private data/location to all apps, except the ones I deem legit.

The first time an app request access to such a resource, I either allow or deny it, and check the "remember setting" box. Of course, if Iconizer! asked to read/write contacts, I allowed it.



So, following your and @Mike B.'s advice, I did the following :
- Deactivate Clarity (just to be sure).
- Created a local "Test" contact.
- Started Iconizer!, tapped "Remove identicons : as before, no identicon removed.
- Tapped "Create identicon" : identicon created for the "Test" contact
- Tapped "Remove identicons again : no identicon removed… except for "Test"

Conclusion :
Identiconizer! seem to not batch create/delete contacts synced with DAVdroid, but work fine with local contact.

Please note that I have no other synced contacts accounts, so I can't tell if that behaviour is generic to non-local contacts, or specific to DAVdroid.

---------- Post added at 07:09 PM ---------- Previous post was at 06:50 PM ----------

Also, deactivating DAVdroid syncing doesn't change anything.

And switching "Automatic identicons" on still doesn't work, even on local-only contacts (I tried both with and without the Xposed module on).

---------- Post added at 19:18 ---------- Previous post was at 19:09 ----------

Code:
build.board: tuna
build.bootloader: PRIMEMD04
build.brand: google
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: maguro
build.display: cm_maguro-userdebug 4.4.4 KTU84Q 5ec365e35d test-keys
build.fingerprint: google/yakju/maguro:4.3/JWR66Y/776638:user/release-keys
build.hardware: tuna
build.host: cyanogenmod
build.id: KTU84Q
build.manufacturer: samsung
build.model: Galaxy Nexus
build.product: yakju
build.radio: I9250XXLJ1
build.serial: 014E28480B019016
build.tags: test-keys
build.time: 1416034677000
build.type: userdebug
build.user: jenkins
version.codename: REL
version.incremental: 5ec365e35d
version.release: 4.4.4
version.sdk_int: 19
Logcat (filtered on "iconi", as there is stuff in there I don't feel like showing. I can add specific lines if needed though)
Code:
06-18 18:35:50.711 I/WindowManager(654): Screen frozen for +3s951ms due to Window{42b23308 u0 com.germainz.identiconizer/com.germainz.identiconizer.IdenticonsSettings}
06-18 18:36:13.022 E/ActivityManager(654):   1.8% 5663/com.germainz.identiconizer: 0.7% user + 1% kernel / faults: 385 minor
06-18 18:39:37.709 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.IdenticonsSettings bnds=[0,198][1196,326]} from pid -1
06-18 18:39:37.725 W/ActivityManager(654): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { cmp=com.germainz.identiconizer/.IdenticonsSettings bnds=[0,198][1196,326] }
06-18 18:39:41.834 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 5663
06-18 18:39:57.928 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 5663
06-18 18:40:22.834 I/ActivityManager(654): Force stopping com.germainz.identiconizer appid=10118 user=0: from pid 654
06-18 18:40:22.842 I/ActivityManager(654): Killing 5663:com.germainz.identiconizer/u0a118 (adj 0): stop com.germainz.identiconizer
06-18 18:40:22.842 W/ActivityManager(654): Scheduling restart of crashed service com.germainz.identiconizer/.services.ContactsObserverService in 1000ms
06-18 18:40:22.842 W/ActivityManager(654): Scheduling restart of crashed service com.germainz.identiconizer/.services.IdenticonCreationService in 11000ms
06-18 18:40:22.842 W/ActivityManager(654): Force removing ActivityRecord{4236e2a8 u0 com.germainz.identiconizer/.IdenticonsSettings t8}: app died, no saved state
06-18 18:40:22.850 I/ActivityManager(654):   Force finishing activity ActivityRecord{42d32618 u0 com.germainz.identiconizer/.IdenticonsSettings t8}
06-18 18:40:22.865 I/ActivityManager(654):   Force stopping service ServiceRecord{42a86bd8 u0 com.germainz.identiconizer/.services.ContactsObserverService}
06-18 18:40:22.865 I/WindowState(654): WIN DEATH: Window{42473f70 u0 com.germainz.identiconizer/com.germainz.identiconizer.IdenticonsSettings}
06-18 18:40:22.873 I/WindowState(654): WIN DEATH: Window{4229d750 u0 com.germainz.identiconizer/com.germainz.identiconizer.IdenticonsSettings}
06-18 18:40:35.928 I/ActivityManager(654): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.germainz.identiconizer/.IdenticonsSettings} from pid 8832
06-18 18:40:36.303 I/ActivityManager(654): Start proc com.germainz.identiconizer for activity com.germainz.identiconizer/.IdenticonsSettings: pid=8852 uid=10118 gids={50118}
06-18 18:40:53.365 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 8852
06-18 18:41:21.592 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 8852
06-18 18:49:34.732 I/ActivityManager(654): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.germainz.identiconizer/.IdenticonsSettings} from pid 10052
06-18 18:49:48.522 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 8852
06-18 18:50:09.670 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 8852
06-18 18:51:21.975 I/ActivityManager(654): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.germainz.identiconizer/.IdenticonsSettings} from pid 10052
06-18 18:51:35.522 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 8852
06-18 18:51:54.029 I/ActivityManager(654): START u0 {cmp=com.germainz.identiconizer/.ContactsListActivity} from pid 8852
06-18 19:00:00.295 W/PackageParser(12044): Unknown element under <manifest>: fdroid at /data/app/com.germainz.identiconizer-1.apk Binary XML file line #58
06-18 19:01:39.696 I/ActivityManager(12044): Start proc com.germainz.identiconizer for broadcast com.germainz.identiconizer/.receivers.BootCompletedReceiver: pid=14838 uid=10118 gids={50118}
06-18 19:01:39.977 I/ActivityManager(12044): Delay finish: com.germainz.identiconizer/.receivers.BootCompletedReceiver
06-18 19:01:54.977 I/ActivityManager(12044): Waited long enough for: ServiceRecord{431a6610 u0 com.germainz.identiconizer/.services.ContactsObserverService}
06-18 19:03:51.171 E/ActivityManager(12044):   0% 14838/com.germainz.identiconizer: 0% user + 0% kernel / faults: 136 minor
06-18 19:08:33.554 I/Timeline(17345): Timeline: Activity_launch_request id:com.germainz.identiconizer time:2303930
06-18 19:08:33.554 I/ActivityManager(12044): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.germainz.identiconizer/.IdenticonsSettings} from pid 17345
06-18 19:08:34.913 I/ActivityManager(12044): Displayed com.germainz.identiconizer/.IdenticonsSettings: +967ms
06-18 19:08:34.913 I/Timeline(12044): Timeline: Activity_windows_visible id: ActivityRecord{430bb9f0 u0 com.germainz.identiconizer/.IdenticonsSettings t4} time:2305294
The Following 2 Users Say Thank You to breversa For This Useful Post: [ View ]
18th June 2015, 07:00 PM |#184  
GermainZ's Avatar
OP Forum Moderator / Recognized Developer / XDA Portal Team
Thanks Meter: 8,294
 
More
Quote:
Originally Posted by breversa

Can you see if filtering the logcat for "AndroidRuntime" shows anything?
18th June 2015, 07:02 PM |#185  
Junior Member
Thanks Meter: 5
 
More
Quote:
Originally Posted by GermainZ

Can you see if filtering the logcat for "AndroidRuntime" shows anything?

Sure ! There you go :
Code:
06-18 19:02:00.418 D/AndroidRuntime(15085): 
06-18 19:02:00.418 D/AndroidRuntime(15085): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:00.418 D/AndroidRuntime(15085): CheckJNI is OFF
06-18 19:02:00.925 D/AndroidRuntime(15085): Calling main entry com.android.commands.am.Am
06-18 19:02:15.543 D/AndroidRuntime(15386): 
06-18 19:02:15.543 D/AndroidRuntime(15386): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:15.543 D/AndroidRuntime(15386): CheckJNI is OFF
06-18 19:02:15.574 D/AndroidRuntime(15385): 
06-18 19:02:15.574 D/AndroidRuntime(15385): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:15.574 D/AndroidRuntime(15385): CheckJNI is OFF
06-18 19:02:16.332 D/AndroidRuntime(15435): 
06-18 19:02:16.332 D/AndroidRuntime(15435): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:16.347 D/AndroidRuntime(15435): CheckJNI is OFF
06-18 19:02:16.754 D/AndroidRuntime(15385): Calling main entry com.android.commands.am.Am
06-18 19:02:16.754 D/AndroidRuntime(15386): Calling main entry com.android.commands.am.Am
06-18 19:02:16.808 D/AndroidRuntime(15467): 
06-18 19:02:16.808 D/AndroidRuntime(15467): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:16.808 D/AndroidRuntime(15467): CheckJNI is OFF
06-18 19:02:17.441 D/AndroidRuntime(15435): Calling main entry com.android.commands.am.Am
06-18 19:02:17.629 D/AndroidRuntime(15488): 
06-18 19:02:17.629 D/AndroidRuntime(15488): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:17.629 D/AndroidRuntime(15488): CheckJNI is OFF
06-18 19:02:17.800 D/AndroidRuntime(15467): Calling main entry com.android.commands.am.Am
06-18 19:02:18.207 D/AndroidRuntime(15488): Calling main entry com.android.commands.am.Am
06-18 19:02:18.605 D/AndroidRuntime(15517): 
06-18 19:02:18.605 D/AndroidRuntime(15517): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:18.605 D/AndroidRuntime(15517): CheckJNI is OFF
06-18 19:02:18.918 D/AndroidRuntime(15536): 
06-18 19:02:18.918 D/AndroidRuntime(15536): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:02:18.918 D/AndroidRuntime(15536): CheckJNI is OFF
06-18 19:02:19.316 D/AndroidRuntime(15517): Calling main entry com.android.commands.am.Am
06-18 19:02:19.574 D/AndroidRuntime(15536): Calling main entry com.android.commands.am.Am
06-18 19:02:26.441 D/AndroidRuntime(13306): Shutting down VM
06-18 19:02:27.238 D/AndroidRuntime(13307): Shutting down VM
06-18 19:02:45.957 D/AndroidRuntime(15031): Shutting down VM
06-18 19:02:46.207 D/AndroidRuntime(15085): Shutting down VM
06-18 19:02:49.855 D/AndroidRuntime(15385): Shutting down VM
06-18 19:02:50.066 D/AndroidRuntime(15386): Shutting down VM
06-18 19:02:50.293 D/AndroidRuntime(15435): Shutting down VM
06-18 19:02:50.457 D/AndroidRuntime(15467): Shutting down VM
06-18 19:02:50.629 D/AndroidRuntime(15488): Shutting down VM
06-18 19:02:50.761 D/AndroidRuntime(15517): Shutting down VM
06-18 19:02:50.933 D/AndroidRuntime(15536): Shutting down VM
06-18 19:09:48.968 D/AndroidRuntime(17485): 
06-18 19:09:48.968 D/AndroidRuntime(17485): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:09:48.968 D/AndroidRuntime(17485): CheckJNI is OFF
06-18 19:09:49.101 D/AndroidRuntime(17493): 
06-18 19:09:49.101 D/AndroidRuntime(17493): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:09:49.101 D/AndroidRuntime(17493): CheckJNI is OFF
06-18 19:09:49.241 D/AndroidRuntime(17508): 
06-18 19:09:49.241 D/AndroidRuntime(17508): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:09:49.241 D/AndroidRuntime(17508): CheckJNI is OFF
06-18 19:09:49.351 D/AndroidRuntime(17501): 
06-18 19:09:49.351 D/AndroidRuntime(17501): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
06-18 19:09:49.351 D/AndroidRuntime(17501): CheckJNI is OFF
06-18 19:09:50.007 D/AndroidRuntime(17485): Calling main entry com.android.commands.am.Am
06-18 19:09:50.085 D/AndroidRuntime(17501): Calling main entry com.android.commands.am.Am
06-18 19:09:50.093 D/AndroidRuntime(17508): Calling main entry com.android.commands.am.Am
06-18 19:09:50.093 D/AndroidRuntime(17493): Calling main entry com.android.commands.am.Am
06-18 19:09:51.241 D/AndroidRuntime(17485): Shutting down VM
06-18 19:09:51.413 D/AndroidRuntime(17501): Shutting down VM
06-18 19:09:51.585 D/AndroidRuntime(17508): Shutting down VM
06-18 19:09:51.820 D/AndroidRuntime(17493): Shutting down VM
Nothing very usefull, though ?
The Following User Says Thank You to breversa For This Useful Post: [ View ]
19th June 2015, 03:20 AM |#186  
Senior Member
Thanks Meter: 495
 
More
Quote:
Originally Posted by GermainZ

What do you mean?

If there would be an option to use an image of my choice as contact picture, rather than the included ones

Thanks
19th June 2015, 07:57 AM |#187  
GermainZ's Avatar
OP Forum Moderator / Recognized Developer / XDA Portal Team
Thanks Meter: 8,294
 
More
Quote:
Originally Posted by aalupatti

If there would be an option to use an image of my choice as contact picture, rather than the included ones

Thanks

You can do that through the Contacts app. Identiconizer! is for generating unique icons for each contact, not batch assigning the same "placeholder" image for all contacts. Cheers.
The Following 2 Users Say Thank You to GermainZ For This Useful Post: [ View ]
19th June 2015, 11:29 AM |#188  
Senior Member
Thanks Meter: 495
 
More
Quote:
Originally Posted by GermainZ

You can do that through the Contacts app. Identiconizer! is for generating unique icons for each contact, not batch assigning the same "placeholder" image for all contacts. Cheers.

I have around 1500 contacts and most do not have images. There is no app that would assign a picture to all the contacts with a missing image. Also there is no app that would automatically assign image to a new contact.
Thanks
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes