Develop Bugs

[Q] What is IQFD?

I don't know if this question belongs here but I figure a dev might know what this means. Sometimes my phone will become VERY sluggish and when I open the System Panel which is monitoring the phone in the background, it will show the CPU usage pegged at 98-100%... When I check what apps are consuming cpu with this same app, it shows a system service named IQFD as the culprit. I usually have to reboot my phone in other to clear everything up.
Anyone?

Try Advanced Task Killer next time you see that process running. Kill off apps one by one, hopefully if one of those kill the process - you'll be able to identify the offending app

Whatever it is, I doubt it will be stopped by a task killer, but I'm pretty sure it is related to this:
http://en.wikipedia.org/wiki/Quality_function_deployment
If your phone is rooted, you can try freezing the app using Titanium Backup. OSMonitor may work; I don't remember if root is needed for that app, but I don't think so. If it locks up your phone when you stop the app, just pull the battery and reboot. I am not sure if it is essential for the OS to function, but you can try.
Also, I'm pretty sure this should go in the Q&A section.

I've actually have had the same symptoms since flashing kings bfs kernel, I usually reboot to recovery them clear dalvik cache. It also takes an abnormal amount of time for the dalvik to wipe

Bump, this is getting annoying

I started seeing the same thing today - was running netarchy's 4.1.8 BFS for several days and it was great. Today the phone's almost unusable because iqfd is taking all the CPU, which also runs the battery down. I restored back to an earlier kernel (4.0.3 I think) and it's not doing it.
While it was looping, I tried a few things that needed root like Titanium Backup, and an "su" command in Terminal Emulator and they both failed with Permission Denied.
Very Disturbing.

I installed the latest Netarchy kernel yesterday (CFS, IIRC) and it was working great until tonight, when randomly I started having /system/bin/iqfd go to 100%. I noticed the following:
- It came back after reboots
- It seemed to stay gone after I killed it using OSMonitor until I shut off the display. Once I shut off the display, it would always come back.
- I was doing some development of an app when I first started noticing this. Eclipse started acting up when I told it to deploy... this could be unrelated, but just a note.
- I restored to the Stock Froyo kernel, and it seems to be fixed for the moment.

i get this too iw onder if this has anything to do with BFQ of BFS or HAVS. i only starrted getting this issue once these were introduced into the kernels. its really annoying though

It seems that IQFD is one of two CIQ daemons launched by init. I believe CIQ stands for Carrier IQ. This startup company is a provider of intelligence solutions to the wireless industry, using embedded diagnostic software, to give them a real-time picture of network activity. Carrier IQ's client list includes Sprint.

Here's some more information I've found on CIQ.
/system/bin/iqd is the CIQ backend daemon.
/system/bin/iqfd is the CIQ frontend daemon.
The two CIQ daemons are launched by /init.
Code:
# cat init.supersonic.rc
...
# CIQ backend daemon
service iqd /system/bin/iqd
user root
group root system
# CIQ frontend daemon
service iqfd /system/bin/iqfd
user root
group root system
...
I confirmed their parent process is /init and found that com.htc.android.iqagent is launched by zygoyte. com.htc.android.iqagent (possibly com.carrieriq.iqagent.service on other devices?) is the Android Client.
Code:
# ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 348 256 c00cc66c 0000d2ac S /init
...
root 292 1 124020 29572 c00cc66c afd0dd44 S zygote
...
root 306 1 10468 1432 ffffffff afd0dd44 S /system/bin/iqd
root 307 1 4828 780 ffffffff afd0ea5c S /system/bin/iqfd
...
app_29 439 292 157168 22440 ffffffff afd0ebd8 S com.htc.android.iqagent
...
The CIQ backend daemon is an active server on the device running on port 2479.
Code:
# busybox netstat -lp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
...
tcp 0 0 0.0.0.0:2479 0.0.0.0:* LISTEN 306/iqd
...
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node PID/Program name Path
...
unix 2 [ ACC ] STREAM LISTENING 7409 306/iqd /app-cache/iqserver
...
CIQ has some associated libraries, devices, parameters, and a profile. The profile contains a URL to the collector along with some other info probably used to identify the type of device and network.
Code:
# find / -name *iq*
...
/app-cache/iqserver
/data/data/com.htc.android.iqrd
/data/data/com.htc.android.iqagent
/sys/devices/virtual/misc/pmem_ciq
/sys/devices/virtual/misc/pmem_ciq1
/sys/devices/virtual/misc/pmem_ciq2
/sys/devices/virtual/misc/pmem_ciq3
...
/sys/class/misc/pmem_ciq
/sys/class/misc/pmem_ciq1
/sys/class/misc/pmem_ciq2
/sys/class/misc/pmem_ciq3
/sys/module/smd/parameters/ciq_info
/system/lib/libciq_client.so
/system/lib/libhtciqagent.so
/system/lib/libciq_htc.so
/system/etc/iqprofile.pro
...
/system/bin/iqd
/system/bin/iqfd
/dev/pmem_ciq3
/dev/pmem_ciq2
/dev/pmem_ciq1
/dev/pmem_ciq
The following CIQ log entries are extracted from multiple logs (not a single log) that I have seen in various forum postings. These could be application event failures. I don't see these on a healthy device.
Code:
...
D/CIQ ( 116): throwUI04 com.htc.bgp
D/CIQ ( 116): processName com.htc.bgp
D/CIQ ( 116): throwUI05 com.htc.RosieUtility
D/CIQ ( 116): processName
D/CIQ ( 112): throwUI05 com.htc.bg
D/CIQ ( 112): processName com.htc.bg
D/CIQ ( 66): throwUI04 com.newsrob
D/CIQ ( 66): processName com.newsrob
D/CIQ ( 66): throwUI03
D/CIQ ( 66): processName com.coremobility.app.vnotes
D/CIQ ( 3833): throwUI04 android.process.media
D/CIQ ( 3833): processName android.process.media
D/CIQ ( 3833): throwUI04 com.htc.android.iqagent
D/CIQ ( 3833): processName com.htc.android.iqagent
D/CIQ ( 3833): throwUI04 com.google.process.gapps
D/CIQ ( 3833): processName com.google.process.gapps
D/CIQ ( 3833): throwUI04 com.android.wallpaper
D/CIQ ( 3833): processName com.android.wallpaper
D/CIQ ( 3833): throwUI04 com.htc.android.htcime
D/CIQ ( 3833): processName com.htc.android.htcime
D/CIQ ( 3833): throwUI04 com.android.phone
D/CIQ ( 3833): processName com.android.phone
D/CIQ ( 3833): throwUI04 android.process.acore
D/CIQ ( 3833): processName android.process.acore
D/CIQ ( 3833): throwUI04 com.htc.launcher
D/CIQ ( 3833): processName com.htc.launcher
...
Maybe if the IQ Server (iqd) is not responding, then the IQ Client (iqfd) is constantly trying to reconnect. I found the following log snippet from other posts in the forums about similiar issues.
Code:
...
E/com_htc_android_iqagent_Controller( 129): backend daemon was not ready!
D/IQClient( 51): wait for backend daemon ready ...
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
...
That's all I have. Please provide any additional information you have.

Reporting in from unlocked land
Wanted to report I had this same issue this morning, iqfd @ 101.1% (!?!) over the previous 8 hours according to System Panel. But I'm running the stock froyo rom from Sprint.

jazmatician said:
Wanted to report I had this same issue this morning, iqfd @ 101.1% (!?!) over the previous 8 hours according to System Panel. But I'm running the stock froyo rom from Sprint.
Click to expand...
Click to collapse
Wait wait.
So Stock Froyo. As in No Root, No Custom Recovery, and no custom kernel?

a lot of good ifnormation. now we need to figure out a way to try to prevent it from hosing up the phone

Yes. This and "Suspend" drestroy my battery after a few days and requires a battery pull. Because simply resetting doesn't fix it.
...in 1943, I killed a drifter.

any update on this?

I don't know of this will help but it seems to have worked for me so far. It was running away on me as well and I couldn't find any solution on the forum. I cleared the cache and it hasn't done it in four days. It was going crazy at least once a day before that. Running netarchys latest.
Sent from my PC36100 using XDA App

jnewkirk10 said:
I don't know of this will help but it seems to have worked for me so far. It was running away on me as well and I couldn't find any solution on the forum. I cleared the cache and it hasn't done it in four days. It was going crazy at least once a day before that. Running netarchys latest.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
exactly which cache did u clear?

The only way I've been able to avoid this IQFD hang up has been with the 4.1.9.1 CFS build of netarchy's kernel. I'm not saying that it's a BFS issue, but it's just not present while running on this particular kernel. My girlfriend and I both have an evo, one with Fresh 3.2, one with Fresh 3.1.0.2, and both had the same problem.

I also have not had issues using CFS kernels and first noticed it had started happenign to me around the time i switched to the BFS kingxkernel. not sure if it is coincidence but so far have been ok with both kingx 8 and netarchy cfs version.

Having a hell of a time with this process just the last 24 hrs. This is ridiculous - the phone is unusable! Trying to flash a CFS kernel right now to see if that fixes it...

[05-JAN][FIX] Navigon Select on Gingerbread

Hi guys, me again,
i just fixed Navigon Select to work with Gingerbread. It needs the replacement of libmedia because some interfaces got incompatible. Now i can finally use onboard Navigation on my CM7
Download
Just replace the file in /system/lib
cheers

Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks

Cooooooooool !!! THX !!!

Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App

cheezusweezel said:
Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..

pack21 said:
Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks
Click to expand...
Click to collapse
+1 your out of control, dude. Your an 86, just one more than me and you are making some major breakthroughs.. It makes me think I am really doing nothing with my life, lol.. But yeah, keep up the god work, man
Edit: I meant to say "good" work but swype has no problem also praising you it seems
Sent from my HTC HD2 using XDA App

Cool man, you rock!
Going to try to get Navigon to work following your instructions, now that you already fixed GPS.
[OT]:
Do you by chance also know how to fix camcorder for [email protected]?
I'm playing with PPC_SHIFTPDA_V2 [RAM] which i really like. Camcorder is one of the last issues i would like to fix.
[/OT]

Thanks! But no luck for me either!

gauner1986 said:
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..
Click to expand...
Click to collapse
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)

Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread

Could you guys try again with the file i attached? Maybe i uploaded the wrong one.
gnash.s said:
Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread
Click to expand...
Click to collapse
Use GPS Status from Market.

Nope, also the new file won't work (for me) ...

cheezusweezel said:
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
Click to expand...
Click to collapse
So it has to work now.. I checked the .so file, the symbol is definetly present:
Code:
gauners-MacBook-Pro:~ gauner$ strings libmedia.so | grep "_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i"
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_ii
Be sure to replace /system/lib/libmedia.so !
cheezusweezel said:
Nope, also the new file won't work (for me) ...
Click to expand...
Click to collapse
Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.

Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
New logcat:
I/ActivityThread( 2812): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 2812): pn: com.navigon.navigator_select
D/NaviApp ( 2812): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 2812): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051d788
I/System.out( 2812): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 2812): Trying NavinativeD...
I/System.out( 2812): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 2812): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini is up-to-date
W/dalvikvm( 2812): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
I/Process ( 2812): Sending signal. PID: 2812 SIG: 9
And your ROM will be much appreciated !!!

gauner1986 said:
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
I read on mdj's thread that alot of ppl are complaining about lag in CM7, would you consider as AOSP release? Thanks soo much!!!

Had a FC when starting Navigon Select before applying the fixed library.
Replaced with your library now NS (&GPS) works without any problem!
Thx again!

Hopefully you guys did not forget to reboot? Otherwise i don't know!

another tip...
if you got a FC while starting Navigon Select, just remove the Navigon and reinstall it again
Should work afterwards.

Sounds like permission issues, check that the new files have the same permissions as others in the same folder.

Just tried this update with Navigon MobileNavigator on a Nexus S with Gingerbread(2.3.1) It's let me get past the spash screen without a FC. Just downloading the maps now. Hope the rest of the app doesn't have any other problems.
Many thanks for this fix.
(I did change the permissions and ownership of libmedia.so with these commands
chown root.root libmedia.so
chmod 644 libmedia.so
)
Rob
EDIT: Confirmed that this is working on my device. Thanks for a great fix.

Fixing market "download Unsuccessful" - and update to market 2.2.6

Hey Everyone,
Thought i would share what i did to fix up the issues using the market!
Had a fresh install of FRX06, Had done the bluetooth patch (all working, great work guys btw)
Only real issue i had was downloading from the market. Nothing would download.
Every time just download unsuccessful.
So i played around trying to fix it, and ended up being able to upgrade the market to the newer version, and it all works
So steps.
1. Download vending.apk for version 2.2.6 of the market. (attached)
2. plug your phone into your PC and start up droidexplorer.
3. open command prompt in droidexplorer and type "mount -o remount,rw /"
4. go to /system/app and copy the current vending.apk to your computer (for a backup)
5. delete vending.apk from /system/app
6. Rename the new 2.2.6 version to "vending.apk" and copy it to /system/app
7. restart the phone
8. open market and check that it is working
Hope this helps a few of you out and to get your market working
Or to get the newer version of the market.
Cheers

And now something has gone wrong
Was working fine, till my phone had a SOD and wouldnt turn on so i pulled the battery.
Now getting force closes
Code:
I/ActivityManager( 1355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.in
tent.category.LAUNCHER] flg=0x10200000 cmp=com.android.vending/.AssetBrowserActivity }
I/ActivityManager( 1355): Start proc com.android.vending for activity com.android.vending/.AssetBrow
serActivity: pid=2067 uid=10004 gids={1015, 3003}
I/ActivityThread( 2067): Publishing provider com.android.vending.SuggestionsProvider: com.android.ve
nding.SuggestionsProvider
D/vending ( 2067): [1] VendingApplication.onCreate(): Resetting ServiceLocator from app
D/dalvikvm( 2067): GC_FOR_MALLOC freed 1849 objects / 128848 bytes in 80ms
D/dalvikvm( 2067): GC_FOR_MALLOC freed 6969 objects / 520096 bytes in 90ms
D/GoogleLoginService( 1465): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.goog
le.android.gsf/.loginservice.GoogleLoginService }
I/ActivityManager( 1355): Displayed activity com.android.vending/.AssetBrowserActivity: 1790 ms (tot
al 47180 ms)
D/ResourceType( 2067): calling getConfigurations
D/ResourceType( 2067): called getConfigurations size=200
E/DatabaseUtils( 1465): Writing exception to parcel
E/DatabaseUtils( 1465): java.lang.SecurityException: Permission Denial: writing com.google.android.g
sf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=2067, uid=1000
4 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/DatabaseUtils( 1465): at android.content.ContentProvider$Transport.enforceWritePermission(
ContentProvider.java:348)
E/DatabaseUtils( 1465): at android.content.ContentProvider$Transport.insert(ContentProvider.
java:196)
E/DatabaseUtils( 1465): at android.content.ContentProviderNative.onTransact(ContentProviderN
ative.java:146)
E/DatabaseUtils( 1465): at android.os.Binder.execTransact(Binder.java:288)
E/DatabaseUtils( 1465): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 2067): threadid=9: thread exiting with uncaught exception (group=0x400207f0)
E/AndroidRuntime( 2067): FATAL EXCEPTION: Thread-11
E/AndroidRuntime( 2067): java.lang.SecurityException: Permission Denial: writing com.google.android.
gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=2067, uid=100
04 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/AndroidRuntime( 2067): at android.os.Parcel.readException(Parcel.java:1260)
E/AndroidRuntime( 2067): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUt
ils.java:160)
E/AndroidRuntime( 2067): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUt
ils.java:114)
E/AndroidRuntime( 2067): at android.content.ContentProviderProxy.insert(ContentProviderNative
.java:408)
E/AndroidRuntime( 2067): at android.content.ContentResolver.insert(ContentResolver.java:587)
E/AndroidRuntime( 2067): at com.google.android.gsf.GoogleSettingsContract$NameValueTable.putS
tring(GoogleSettingsContract.java:55)
E/AndroidRuntime( 2067): at com.google.android.gsf.GoogleSettingsContract$Partner.putString(G
oogleSettingsContract.java:126)
E/AndroidRuntime( 2067): at com.android.vending.compat.MarketCheckinHelper.updateCheckinDatab
ase(MarketCheckinHelper.java:12)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater.sendContentSyncViaCheckin(Chec
kinUpdater.java:219)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater.performCheckin(CheckinUpdater.
java:176)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater.access$000(CheckinUpdater.java
:38)
E/AndroidRuntime( 2067): at com.android.vending.CheckinUpdater$1.run(CheckinUpdater.java:109)
E/AndroidRuntime( 2067): at com.android.vending.util.WorkService$1.run(WorkService.java:37)
W/ActivityManager( 1355): Force finishing activity com.android.vending/.AssetBrowserActivity
D/dalvikvm( 2067): GC_FOR_MALLOC freed 6230 objects / 580152 bytes in 160ms
D/dalvikvm( 2067): GC_EXTERNAL_ALLOC freed 3710 objects / 318976 bytes in 110ms
E/Tethering( 1355): active iface (usb0) reported as added, ignoring
Strangely enough... I copied the original market back over and its working (not as pretty though )

I don't have a vending.apk on my system. I tried replacing market.apk, but it just force closed.

I won't have time to check that market APK until quite late tonight at the earliest, and maybe not for a few days (really busy week!), but nearly every one I've ever seen is signed with a key incompatible with our gapps distribution, so I suspect that's the problem you are having.
To get it to work without permissions-related force closes, you have to re-sign it with one of the platform test keys. (I forget exactly which one at the moment). I've done this with 2.2.6 on my phone but I haven't had time to write a tutorial on it.
Edit: Looking at your logcat, GoogleSettingsProvider permissions issues are a classic sign of a signing key mismatch.

Entropy512 said:
I won't have time to check that market APK until quite late tonight at the earliest, and maybe not for a few days (really busy week!), but nearly every one I've ever seen is signed with a key incompatible with our gapps distribution, so I suspect that's the problem you are having.
To get it to work without permissions-related force closes, you have to re-sign it with one of the platform test keys. (I forget exactly which one at the moment). I've done this with 2.2.6 on my phone but I haven't had time to write a tutorial on it.
Edit: Looking at your logcat, GoogleSettingsProvider permissions issues are a classic sign of a signing key mismatch.
Click to expand...
Click to collapse
Oh ok, thanks.
How come it would have worked initially then? Thats weird

Shadoxity said:
Oh ok, thanks.
How come it would have worked initially then? Thats weird
Click to expand...
Click to collapse
I don't know - I do remember a couple of situations where it would work for one download and then fail.
For example, I tried a market APK from a tiad8 ROM - it was awesome for one download and then failed. Now that I know more about the download architecture I think the awesomeness in performance was a fluke. Download performance is all about DownloadProvider.apk and our filesystem drivers... And so far, my attempt to improve Market downloads by tweaking DownloadProvider made the browser totally unusable.

I have had the same as Entropy with most roms I tried.
I can download 1 or 2 things from the market, very slowly, and then it fails, sometimes with random reboots

Just as an FYI, I HAVE gotten Market 2.2.6 to work reliably - it isn't any faster though, that's for sure.
I'll try to post details sometime next week on how to do it. I'm basically out all evening every evening until the end of the weekend so don't have time to post it now.

Shadoxity... question if you will... where did you d/l the bluetooth patch from?

BTW.. I had the same issue w/ market. Went into settings>>applications>> manage applications>> clicked on Market and cleared cache. Did it once and I was only able to d/l 1 file... did it a second time and I've been good since Tuesday. Hope it helps

bluetooth
MerlinOfLore said:
Shadoxity... question if you will... where did you d/l the bluetooth patch from?
Click to expand...
Click to collapse
bluetooth was being tested for Rhodiums over at [TESTING] New audio routing for Froyo. Bluetooth info is in 2nd post.

It didn't work for me... After rebooted the phone (topaz) if I try to run the market it seems to load a white window and after a couple of second it says it's not responding...

What I notice about market is that it leaves 1.83MB-sized "orphans" in /cache. Not sure why it is that size, but regardless of the size of the app it ends up with that fragment.
-- Starfox

MerlinOfLore said:
Shadoxity... question if you will... where did you d/l the bluetooth patch from?
Click to expand...
Click to collapse
From this thead
http://forum.xda-developers.com/showthread.php?t=885550
MerlinOfLore said:
BTW.. I had the same issue w/ market. Went into settings>>applications>> manage applications>> clicked on Market and cleared cache. Did it once and I was only able to d/l 1 file... did it a second time and I've been good since Tuesday. Hope it helps
Click to expand...
Click to collapse
Tried that but made no difference on mine

Has anyone bothered to get logs from the original issue (before the known issue of permissions after manually upgrading the apk)? The only one I've seen had out of memory errors spamming their logs, but they couldn't get me a useful set of logs to look at. If someone could get a log from after a failed market download with my app http://forum.xda-developers.com/showthread.php?t=1123129 it would be much appreciated.

I replaced google apps in frx06 on gapps package downloaded here:
http://goo-inside.me/gapps/gapps-mdpi-20110501-signed.zip
Yes is named as mdpi, but 100% compatible with hdpi too.
And it's works perfect on my opinion.

DmK75 said:
I replaced google apps in frx06 on gapps package downloaded here:
http://goo-inside.me/gapps/gapps-mdpi-20110501-signed.zip
Yes is named as mdpi, but 100% compatible with hdpi too.
And it's works perfect on my opinion.
Click to expand...
Click to collapse
But why...? For what purpose did you replace the gapps package?

arrrghhh said:
But why...? For what purpose did you replace the gapps package?
Click to expand...
Click to collapse
Simply i noticed that built-in gapps are quite old, and also market cant be auto-updated

DmK75 said:
Simply i noticed that built-in gapps are quite old, and also market cant be auto-updated
Click to expand...
Click to collapse
Fair enough, thanks for the follow-up.

DmK75 said:
Simply i noticed that built-in gapps are quite old, and also market cant be auto-updated
Click to expand...
Click to collapse
Just to know, how to install this package? Still through droidexplorer?

[ROM] almost pure AOSP 4.0.3 (rooted) (GSM ONLY)

Hi All,
I've just built 4.0.3 from source, copied the su binary and Superuser.apk from the Android Revolution HD Rom (thanks mike1986) and removed the recovery installation (to maintain non-stock recovery).
updated the gapps to a safer gnexus friendly version for flashing
If you would like to test...
1) don't blame me if your phone blows up, crashes, bricks etc etc. USE AT YOUR OWN RISK (GSM ONLY)
2) download the rom here: http://techerrata.com/file/teamwin/onicrom-maguro-4.0.3_3.zip
3) download the gapps here: http://tinyw.in/w8Lg
4) unzip onicrom-maguro-4.0.3_3.zip
5) in a different directory unzip gapps-....zip
6) cd gappsunzippeddir/system/app
7) cp Google* /placeyou/unzipped/onicrom-maguro.../system/app
8) cp Vending.apk /placeyou/unzipped/onicrom-maguro.../system/app
9) cd /placeyou/unzipped/onicrom-maguro...
10) zip -r yournew-aosp.zip .
11) adb push yournew-aosp.zip /sdcard
12) reboot into recovery, full wipe, flash yournew-aosp.zip
These instructions are not for the faint of heart if you don't understand them DO NOT TRY THIS ROM.
--onicrom
UPDATE
camera is now working (link above updated) thanks again dwang and DebauchedSloth
they also mentioned the gapps from a newly ota'd nexus s might be better to use than the initial ics apps pulled by koush i will link to them if i find them
UPDATE2
Superuser updated to the latest version and working just fine.
UPDATE3
new gapps! ripped from nexus s 4.0.3 ota DO NOT FLASH THE ENTIRE GAPPS ZIP MAKE SURE YOU PULL OUT ONLY THE APKS IT WILL REPLACE system/vendor/firmware/libpn544_fw.so
UPDATE4
newER gapps http://tinyw.in/w8Lg safer to flash on the gnex

me me me me me!
I've been dying for some 4.0.3 action.

Do wifi and everything work, because over at rootzwiki that was the case of it now working.
Sent from my Galaxy Nexus using XDA App

Superuser.apk doesn't appear to be working properly in 4.0.3 (and I don't appear to be the only one with the problem https://twitter.com/#!/ChainsDD/status/148096377958834176).
The su binary works though.
Still interested?

Not currently using any apps that need root.

wifi works
camera...not so much
im going to try and restore the camera apk from 4.0.1
mykenyc said:
Do wifi and everything work, because over at rootzwiki that was the case of it now working.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse

onicrom said:
wifi works
camera...not so much
im going to try and restore the camera apk from 4.0.1
Click to expand...
Click to collapse
What binaries did you use to build? I think there are new 4.0.3 binaries for hardware.
Edit: Here are the new 4.0.3 binaries, but I'm not sure if camera is changed....
http://www.google.com/url?sa=D&q=ht...39.tgz&usg=AFQjCNFa4ZsTMI1c2O3e1Q-vq3EvNaVsAA

those are the binaries i used.
matt2053 said:
What binaries did you use to build? I think there are new 4.0.3 binaries for hardware.
Edit: Here are the new 4.0.3 binaries, but I'm not sure if camera is changed....
http://www.google.com/url?sa=D&q=ht...39.tgz&usg=AFQjCNFa4ZsTMI1c2O3e1Q-vq3EvNaVsAA
Click to expand...
Click to collapse

You need extra files from /system/vendor/firmware for camera/Bluetooth
Sent from my Galaxy Nexus using Tapatalk

which i take it wont be available until 4.0.3 rolls out via OTA?
unless you're hinting at knowing where else to get them?!
Romanbb said:
You need extra files from /system/vendor/firmware for camera/Bluetooth
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse

won't the files from the 4.0.2 image work?
onicrom said:
which i take it wont be available until 4.0.3 rolls out via OTA?
unless you're hinting at knowing where else to get them?!
Click to expand...
Click to collapse

dwang said:
won't the files from the 4.0.2 image work?
Click to expand...
Click to collapse
trying that now

onicrom said:
trying that now
Click to expand...
Click to collapse
Yes, they will work. You want to use the binaries that Google posted, then merge in the other vendor binaries that are missing.
If you do this, everything will work.
I have a build here. It was painful to get everything working, but it can be done.

Did you pull the google apps from the nexus s 4.0.3 image instead of from clockwork? I know that at least the very least the gtalk is different between 4.0.2 and 4.0.3. The browser is also changed so the one from clockwork is older and will overwrite the one built from aosp.
DebauchedSloth said:
Yes, they will work. You want to use the binaries that Google posted, then merge in the other vendor binaries that are missing.
If you do this, everything will work.
I have a build here. It was painful to get everything working, but it can be done.
Click to expand...
Click to collapse

i pulled from the gapps koush posted i only pulled the Market and the google login services though
testing the new build now

dwang said:
Did you pull the google apps from the nexus s 4.0.3 image instead of from clockwork? I know that at least the very least the gtalk is different between 4.0.2 and 4.0.3. The browser is also changed so the one from clockwork is older and will overwrite the one built from aosp.
Click to expand...
Click to collapse
I did not, but that is a fantastisc idea. Doing that now.

great success the camera is now working!
thanks dwang and DebauchedSloth

im still struggling with superuser.apk everytime i run an app which requests root i see the following in logcat...the strange part to me is the loading of the openGL drivers:
Code:
E/su ( 1498): sudb - Opening database
E/su ( 1498): sudb - Database opened
E/su ( 1498): sudb - Database closed
E/ActivityManager( 195): Activity Manager Crash
E/ActivityManager( 195): java.lang.IllegalArgumentException: Unknown URI type: 7
E/ActivityManager( 195): at android.net.Uri$1.createFromParcel(Uri.java:1734)
E/ActivityManager( 195): at android.net.Uri$1.createFromParcel(Uri.java:1723)
E/ActivityManager( 195): at android.content.Intent.readFromParcel(Intent.java:6131)
E/ActivityManager( 195): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 195): at android.content.Intent.readFromParcel(Intent.java:6153)
E/ActivityManager( 195): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 195): at android.content.Intent$1.createFromParcel(Intent.java:6117)
E/ActivityManager( 195): at android.content.Intent$1.createFromParcel(Intent.java:6115)
E/ActivityManager( 195): at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:298)
E/ActivityManager( 195): at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1545)
E/ActivityManager( 195): at android.os.Binder.execTransact(Binder.java:338)
E/ActivityManager( 195): at dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 195): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 195): Activity idle timeout for ActivityRecord{417fea28 com.speedsoftware.rootexplorer/.RootExplorer}
W/ActivityManager( 195): Activity idle timeout for ActivityRecord{41876f68 com.speedsoftware.rootexplorer/.RootExplorerPhone}
D/libEGL ( 1480): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1480): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 1480): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 1480): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 1480): Enabling debug mode 0

Try unchecking "use gpu for 2d applications".
/me sent this on a i9250 using tapatalk

onicrom said:
im still struggling with superuser.apk everytime i run an app which requests root i see the following in logcat...the strange part to me is the loading of the openGL drivers:
Code:
E/su ( 1498): sudb - Opening database
E/su ( 1498): sudb - Database opened
E/su ( 1498): sudb - Database closed
E/ActivityManager( 195): Activity Manager Crash
E/ActivityManager( 195): java.lang.IllegalArgumentException: Unknown URI type: 7
E/ActivityManager( 195): at android.net.Uri$1.createFromParcel(Uri.java:1734)
E/ActivityManager( 195): at android.net.Uri$1.createFromParcel(Uri.java:1723)
E/ActivityManager( 195): at android.content.Intent.readFromParcel(Intent.java:6131)
E/ActivityManager( 195): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 195): at android.content.Intent.readFromParcel(Intent.java:6153)
E/ActivityManager( 195): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 195): at android.content.Intent$1.createFromParcel(Intent.java:6117)
E/ActivityManager( 195): at android.content.Intent$1.createFromParcel(Intent.java:6115)
E/ActivityManager( 195): at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:298)
E/ActivityManager( 195): at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1545)
E/ActivityManager( 195): at android.os.Binder.execTransact(Binder.java:338)
E/ActivityManager( 195): at dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 195): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 195): Activity idle timeout for ActivityRecord{417fea28 com.speedsoftware.rootexplorer/.RootExplorer}
W/ActivityManager( 195): Activity idle timeout for ActivityRecord{41876f68 com.speedsoftware.rootexplorer/.RootExplorerPhone}
D/libEGL ( 1480): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1480): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 1480): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 1480): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 1480): Enabling debug mode 0
Click to expand...
Click to collapse
Don't stress, Chains is working on it, it is SU problem!
Sent from my Galaxy Nexus using XDA App

[Q] Taste of Sense ICS / Issues

I had some issues with this amazing rom and couldnt post in development page so i will be posting in here.
Things i flashed after rom :
indian madness from 1.5 stable lord clockan kernel roms option
Problems ive experienced
sometimes its gets very laggy that i could hardly make an option
and when i wanted to choose from options/sound/music effects settings get fc immediately so i cant choose anything and i want to try that beats dsp so much
And last one is desktop folders are not resized thats why i cahnged my dpi to 210 cuz if i stay at 240 folder icons goes out of the screen
if anyone wants any further info (logcat or any type of thing)i would be happy to provide it.
Thank you!
I think this is the treasure in my logcat
E/AndroidRuntime(15307): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(12469): Force finishing activity com.android.settings/.SubSettings
I/Adreno200-EGLSUB( 1301): <CreateImage:1017>: Android Image
I/Adreno200-EGLSUB( 1301): <GetImageAttributes:1226>: RGBA_8888
I/Process (12469): Sending signal. PID: 15307 SIG: 3
I/dalvikvm(15307): threadid=3: reacting to signal 3
W/ActivityManager(12469): Activity pause timeout for ActivityRecord{412aa488 com.android.settings/.SubSettings}
I/dalvikvm(15307): Wrote stack traces to '/data/anr/traces.txt'
I/Adreno200-EGLSUB( 1301): <CreateImage:1017>: Android Image
I/Adreno200-EGLSUB( 1301): <GetImageAttributes:1226>: RGBA_8888
I/Process (12469): Sending signal. PID: 15307 SIG: 3
I/dalvikvm(15307): threadid=3: reacting to signal 3
I/dalvikvm(15307): Wrote stack traces to '/data/anr/traces.txt'
I/Process (15307): Sending signal. PID: 15307 SIG: 9
I/ActivityManager(12469): Process com.android.settings (pid 15307) has died.
W/InputDispatcher(12469): channel '412f25e0 com.android.settings/com.android.settings.Settings (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher(12469): channel '412f25e0 com.android.settings/com.android.settings.Settings (server)' ~ Channel is unrecoverably broken and will be disposed!
W/ActivityManager(12469): Force removing ActivityRecord{4138c8b0 com.android.settings/.Settings}: app died, no saved state
I/WindowManager(12469): WIN DEATH: Window{40ca0510 com.android.settings/com.android.settings.SubSettings paused=false}
W/InputDispatcher(12469): Attempted to unregister already unregistered input channel '412f25e0 com.android.settings/com.android.settings.Settings (server)'
I/WindowManager(12469): WIN DEATH: Window{412f25e0 com.android.settings/com.android.settings.Settings paused=false}
I/WindowManager(12469): WINDOW DIED Window{412f25e0 com.android.settings/com.android.settings.Settings paused=false}

Hello Bro .
Actually im thinking to install this rom on my Device .. i just want to know if there an arabic language or not ?
So Please Help me and Tell me ... Many Of Thanks
Best Regards
GIO Tarakji

GIO Tarakji said:
Hello Bro .
Actually im thinking to install this rom on my Device .. i just want to know if there an arabic language or not ?
So Please Help me and Tell me ... Many Of Thanks
Best Regards
GIO Tarakji
Click to expand...
Click to collapse
Hey Brother,
First of all despite all problems ive experienced i really recommend this rom.Its design is very lightweight and fast also.Ive never flashed an arabic patch on my device and didnt seen anything like that in the post.But here's a screenshot for you.
SS
Hope it helps,
Best Regards

Did you try a clean install when you flashed the ROM? If you did, it might be an issue with the ROM itself, and you want to try some other ROM.

I was on a modified kernel now i flashed latest lord clockans ics kernel and the lag is disappeared but settings fc persists
Sent from my Desire HD using xda app-developers app

ymcc said:
I was on a modified kernel now i flashed latest lord clockans ics kernel and the lag is disappeared but settings fc persists
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
go into recovery flash your dalvick and fix permissions restart and it should be fine

xvicedice said:
go into recovery flash your dalvick and fix permissions restart and it should be fine
Click to expand...
Click to collapse
But i think it'll be fixed when you finish compiling from 8.3!