[Q] What is IQFD? - EVO 4G Q&A, Help & Troubleshooting

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...

Related

Arnova 10 G2 (RK2918 based tablet)

Hello all
I just bought Archos Arnova 10 G2 few days ago and till now I would say I kinda satisfied with the device. But since we are here on XDA, enjoyment from this device could be even better
I tried to put a custom rom (here) to my device but unfortunatelly I'm not a lucky guy and device didn't boot at all. So I ask uncle Google for help and found this great tool that allowed me to root the tablet easily and put some extra apps into /system/app. I then encounter endless problems with Maket to even get it to work and found a way here (download the attached .zip, copy it to the device and install .apk's in order posted, reboot the device and you have Market and Google apps up and running ). And this is where my problems started to appear...
Market in that .zip is veeery old (v1.82) so I put there new version (3.3.11) and it seems to work well too but just until I try to install some app from Market => FC.
I read something about permisions set wrong or some another component/app is not installed or incompatible with Market 3+ (btw, only version working is 1.82 and 3.3.11 -with problems. Another version give my FC during loading).
So, now to the point I managed to get some feedback from LogCat when Market FC:
Code:
D/Finsky ( 1912): [1] DownloadRestarterRule.run: Recovering from Market exit when restoring / downloading assets.
D/Finsky ( 1912): [1] SanityChecker.run: # LocalAssets corrected : 1
D/Finsky ( 1912): Sanity check took : 24 ms
D/Finsky ( 1912): [1] DownloadTickleReceiver.onReceive: Received tickle.
W/Finsky ( 1912): [1] DownloadTickleReceiver.generatePackageProperties: Received refund period time end string : null
D/Finsky ( 1912): [1] DownloadTickleReceiver.parseObb: Not generating OBB (patch false)
D/Finsky ( 1912): [1] DownloadTickleReceiver.parseObb: Not generating OBB (patch true)
D/Finsky ( 1912): [1] Installer.downloadAndInstallAsset: Downloading and installing Google Docs.
D/Finsky ( 1912): [1] DownloadImpl.setState: com.google.android.apps.docs from null to UNQUEUED.
D/dalvikvm( 1912): GC_CONCURRENT freed 404K, 52% free 2884K/5895K, external 793K/1051K, paused 4ms+3ms
D/Finsky ( 1912): [1] DownloadQueueImpl.add: Download com.google.android.apps.docs added to DownloadQueue
D/Finsky ( 1912): [1] DownloadImpl.setState: com.google.android.apps.docs from UNQUEUED to QUEUED.
I/installd( 60): free_cache(2618907) avail 195815424
D/Finsky ( 1912): [23] DownloadRecords.initializeAndPrune: Pruned 0 old downloads from the cursor.
D/Finsky ( 1912): [1] DownloadQueueImpl.startDownload: Download com.google.android.apps.docs starting
D/Finsky ( 1912): [1] DownloadRestarter.onPostExecute: Recovering restore of com.stumbleupon.android.app
D/Finsky ( 1912): [1] DownloadRestarter.handleObbResumingOrRestart: No OBB's associated to this asset.
D/Finsky ( 1912): [1] DownloadRestarter.restartAssetDownload: Restarting asset download : com.stumbleupon.android.app
E/DatabaseUtils( 269): Writing exception to parcel
E/DatabaseUtils( 269): java.lang.SecurityException: Invalid value for is_public_api: null
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.enforceAllowedValues(DownloadProvider.java:686)
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.checkInsertPermissions(DownloadProvider.java:624)
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.insert(DownloadProvider.java:442)
E/DatabaseUtils( 269): at android.content.ContentProvider$Transport.insert(ContentProvider.java:198)
E/DatabaseUtils( 269): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:146)
E/DatabaseUtils( 269): at android.os.Binder.execTransact(Binder.java:320)
E/DatabaseUtils( 269): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 1912): threadid=21: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime( 1912): FATAL EXCEPTION: download-manager-thread
E/AndroidRuntime( 1912): java.lang.SecurityException: Invalid value for is_public_api: null
E/AndroidRuntime( 1912): at android.os.Parcel.readException(Parcel.java:1322)
E/AndroidRuntime( 1912): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:160)
E/AndroidRuntime( 1912): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
E/AndroidRuntime( 1912): at android.content.ContentProviderProxy.insert(ContentProviderNative.java:408)
E/AndroidRuntime( 1912): at android.content.ContentResolver.insert(ContentResolver.java:606)
E/AndroidRuntime( 1912): at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:44)
E/AndroidRuntime( 1912): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 1912): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 1912): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1912): at android.os.HandlerThread.run(HandlerThread.java:60)
D/dalvikvm( 1912): GC_CONCURRENT freed 408K, 51% free 3000K/6023K, external 793K/1051K, paused 4ms+3ms
D/dalvikvm( 79): GC_CONCURRENT freed 1041K, 49% free 5163K/10055K, external 1908K/1998K, paused 3ms+12ms
D/dalvikvm( 1912): GC_CONCURRENT freed 540K, 52% free 2994K/6151K, external 793K/1051K, paused 3ms+9ms
D/Finsky ( 1912): [1] Installer.downloadAndInstallAsset: Downloading and installing StumbleUpon.
D/Finsky ( 1912): [1] DownloadImpl.setState: com.stumbleupon.android.app from null to UNQUEUED.
D/Finsky ( 1912): [1] DownloadQueueImpl.add: Download com.stumbleupon.android.app added to DownloadQueue
D/Finsky ( 1912): [1] DownloadImpl.setState: com.stumbleupon.android.app from UNQUEUED to QUEUED.
D/dalvikvm( 269): GC_EXPLICIT freed 58K, 53% free 2654K/5575K, external 793K/1051K, paused 93ms
I/Process ( 1912): Sending signal. PID: 1912 SIG: 9
W/InputManagerService( 79): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 79): Process com.android.vending (pid 1912) has died.
Can somebody advice me in which direction should I look to fix these errors?
Or another thing, /system is not RW on this device, so every change I do I have to flash whole ROM again :/
I tried these command in Terminal Emulator but without luck:
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
Thanks anyone for kick
Regards
Adam
Hi There
I had faced a similar issue this morning. My advise is to install this custom rom and utility 'arctools' to install the google app pack. I did this morning and it worked like a dream.
The link is here
Good luck
Thank for the advice but unfortunatelly I tried put this custom rom to my device for the few times and it just didn't boot (maybe I have some new HW revision?).
But anyway, some guy in the original spanish forum posted updated ROM on page 7 and its working well on my device, only thing missing in RW access on /system
p1ceus said:
I tried to put a custom rom (here) to my device but unfortunatelly I'm not a lucky guy and device didn't boot at all. So I ask uncle Google for help and found this great tool that allowed me to root the tablet easily and put some extra apps into /system/app. I then encounter endless problems with Maket to even get it to work and found a way here (download the attached .zip, copy it to the device and install .apk's in order posted, reboot the device and you have Market and Google apps up and running ). And this is where my problems started to appear...
Click to expand...
Click to collapse
Could you explain what you did with that tool to gain root? Im the thread for the tool it says for step to that I need to "copy the image file into this folder,and rename to wendal.img" What image file do I copy?
I'm not overly concerned about the Market, and I do not want the custom rom that is at arctablet.com because it screws up your storage space among other issues and my tablet work really well right now I just want root. If anyone knows any other ways just to gain root and nothing else it would be greatly appreciated.
Hi,
just DL the official ROM from Arnova, rename update.img to wendal.img and thats it. Then run the Runme.bat with option 1 first and then with option 2. When done, copy wendal_new.img to the root of Arnova internal SD and rename it to update.img before disconnection the USB. After the flash, you should have root (but its just a partial since you cannot write to system parititon :/)
good tablet
p1ceus said:
Hi,
just DL the official ROM from Arnova, rename update.img to wendal.img and thats it. Then run the Runme.bat with option 1 first and then with option 2. When done, copy wendal_new.img to the root of Arnova internal SD and rename it to update.img before disconnection the USB. After the flash, you should have root (but its just a partial since you cannot write to system parititon :/)
Click to expand...
Click to collapse
Any idea if this procedure leaves one able to
1) Use marketenabler to access amazon usa &
2) get a root prompt via terminal ??
sdunne said:
Any idea if this procedure leaves one able to
1) Use marketenabler to access amazon usa &
2) get a root prompt via terminal ??
Click to expand...
Click to collapse
I was able to use the Amazon Appstore if that's what you're talking about. I also have Root Explorer, Titanium Backup, and Rom Toolbox running and get the SU prompt but haven't tried from a Terminal.
Sent from my PC36100 using xda premium
Well I have the R29xxImageTools v2.1, the Rockchip_Batch tools v1.4 and the Setup_google_app.rar file.
I've exploded the original update.img, overlaid system with the 4 subdirs from within the google rar and repacked the image, renamed the wendal_new.img to update.img and reflashed it.
Tablet just sits at arnova splash screen after a yellow recovery message. (this is the same message whether the flash ultimately works or not)
If I don't hack around with the exploded system image, other than what the lua script does itself then the tablet reflashes successfully and comes up, albeit with a non functioning marketplace.
Any idea what I'm doing wrong ??
Hi, try different gapps. It happend to me also, then I DL different zip with google apps and it was working.
try this rom with arctool v0.57 http://www.arctablet.com/blog/forum/arnova-10-g2/arnova-10-g2-improved-custom-firmware-update/
Anybody know how many mAmps the battery is on the Arnova 10 G2? I'm trying to better calibrate Battery Left Pro widget.
finless bob version 1.3
here is version 1.3 by finless bob
http://dl.dropbox.com/u/17806868/arnova10g2_v1_3_market.zip
how to install can be found here
http://www.freaktab.com/showthread....stom-ROM-by-Finless-Version-1-3&p=428#post428
finless bob version 1.3
please delete
another rom arnova 10 g2
http://www.arctablet.com/blog/archos...d-app-storage/
use arctools 0.57 to install google apps
http://www.multiupload.co.uk/EA51XONM9S link for arctools 0.57
I wonder how we can get finless to come over to xda?
laserman123 said:
I wonder how we can get finless to come over to xda?
Click to expand...
Click to collapse
Finless wants to stick to his site, since he supports several different machines, but is okay with us redirecting those looking for his ROMs there.
His current ROM is 1.4, includes the tools for flashing it and the marketplace and all gapps, and is located here. It is currently my daily on the tablet.
I am actually a good member here on XDA. So I am here.
Feel free to ask quetions
Bob
nice to see you on here finlessbob, nice rom you have made i am using it myself.
I also have to add it actually makes a base tablet run really great, plus the arnova hase some good connection capabilities that more expensive tablets lack.
Just need an arnova 10g2 section in development now to make things perfect
finlessbob said:
I am actually a good member here on XDA. So I am here.
Feel free to ask quetions
Bob
Click to expand...
Click to collapse
Hello bob. I've just bought a arnova preloaded with your rom however I'm unsure of the version of atm I'm without a computer.
Basically I've installed magic locker on the device but now everytime I boot I get FC on magic locker and cannot get past the screen.
I've tried to factory reset but it sends me into recovery and I cannot select any options.
I just wanted to know if I could fix this without a computer?
Join me on dropbox http://db.tt/aijaD3Wr
Follow me on Twitter _H88RRY_

[AOSP] ICS Build for Verizon 3G/4G XOOM

Alright, so here is a taste of Android 4.0.3 Ice Cream Sandwich (ICS) for the VERIZON Motorola 3G/4G XOOM. This build version number is IML74K.
This is a "out of box" build of the freshly released AOSP sources from Google. This is a "Stingray" configured build for the 3G/4G Verizon U.S. XOOM. NOT to be confused with "Wingray" - the WiFi specific build.
One ISSUE: No 3G/4G at the moment on my end. I think this is because the build called for an updated baseband version:
These are my current versions on my XOOM:
3G-Baseband: CDMA_N_03.1A.54P
4G-Baseband: LTEDC_U_05.19.07
The build asks for these versions:
3G-Baseband: CDMA_N_03.1A.5CPS
4G-Baseband: LTEDC_U_07.19.00
Update 1: Re-built as flash-able zip (download link below). Still has 3G/4G issue - appears to not recognize the radio. Still trying to find clarification on issue.
I do not know where to get these updated basebands, but when we can get ahold of them, this just might work.
BUT, I was able to flash this build to my Verizon 4G XOOM and it works nicely from what I can see from initial testing.
What is working: (That I can tell so far)
- Wi-Fi
- Browser
- Some report issues with GPS
- Gapps (to an extent, some minor issues with market, etc.)
What is not working:
-3G/4G - baseband issue?
-Camera*
-HDMI*
-HD Video Playback?
*Need binaries from Moto
Updated: 17 Dec 2011: 2216
======> DIRECTIONS <======
Disclaimer: For heaven's sakes, FLASH AT YOUR OWN RISK!
The link below is a compressed folder containing FASTBOOT images. You MUST use fastboot to flash these to your Motorola XOOM.
FASTBOOT Install:
- Extract image files from .zip
Then in cmd, booted into bootloader:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Download FASTBOOT Files:
Link: http://www.mediafire.com/?0vvjzg1dvivtre7
NOTE: Do not FLASH zip file in bootloader (must extract .img files first!) Also, not compatible with CWM (use link below for CWM)
CWM ZIP Install:
- Enter CWM Recovery (Tested on Tiamat version)
- Mounts & Storage >> Mount USB
- Copy .zip to SD Card
- Go back to CWM menu >> Install from sd card >> choose zip from SD card
- After it installs, perform a wipe/reset in CWM, then reboot.
Download CWM zip File:
WARNING: Will replace your recovery image with default recovery! (Not sure how to disable this yet)
Link: <ON HOLD>
Please NOTE: This is my first build so for those who want a taste of ICS on their 4G XOOMs, have at it! This should suffice until a well-experienced developer works out the kinks.
damn yall are getting it done!!
good **** man
Can i flash this on my MZ601?
I'll give it a try now. I suggest, this might be working on the MZ601, as the Tiamat, 2.3, based on the Verizon (http://forum.xda-developers.com/showthread.php?t=1387053) does also work for me.
I'll let You know, if it worked, in some minutes...
ch33f said:
Can i flash this on my MZ601?
Click to expand...
Click to collapse
I've flashed the WiFi version to my 3G MZ601, it works great (although without 3G..) and I think you would be better off with that version - this one is made for the US 3G/4G Verizon model, and so I think there might be some screw-ups if you flash this ROM on a Euro-model Xoom
WOW that was fast. wasn't expecting a 3G/4G version dropping so soon. Thank you.
Allright, at first glance it seems to be working fine for my MZ601. But haven't tried 3G until now. And as to be expected, the camera isn't working as well...
But the rest is really blazing fast!
anybody who have gapps for ics?
or can i flash the gapps from ICS Desire S build.
ch33f said:
anybody who have gapps for ics?
or can i flash the gapps from ICS Desire S build.
Click to expand...
Click to collapse
Here's the GAPPS I used on my Xoom.
is this rom rooted or must i?
This is booting on my Euro MZ601 fine by the way =]
xxspark89xx said:
One ISSUE: No 3G/4G at the moment on my end. I think this is because the build called for an updated baseband version:
These are my current versions on my XOOM:
3G-Baseband: CDMA_N_03.1A.54P
4G-Baseband: LTEDC_U_05.19.07
The build asks for these versions:
3G-Baseband: CDMA_N_03.1A.5CPS
4G-Baseband: LTEDC_U_07.19.00
I do not know where to get these updated basebands, but when we can get ahold of them, this just might work.
Click to expand...
Click to collapse
Yeah, I just built and flashed and having the same issue. Ah well, I'm sure it'll turn up somewhere. I need connectivity though, so I'm going to have to Nandroid back for now.
(... even though I wonder if I check out the RIL layer from HLK75F if that'll get us running?)
This is great.I was starting to think that development for the Xoom was dead!
SantinoInc said:
This is great.I was starting to think that development for the Xoom was dead!
Click to expand...
Click to collapse
me too
Sent from my Full Android on Stingray using xda premium
Calendar sync doesn't work :-( thanks for your hard work by the way. This is brilliant.
I was going to wait until the official release so I've been running stock for a while now, unrooted. Now that this has happened I'm rooting, and its nearly 3:30 in the morning, but I'm too excited haha.
Thanks!
How can i get root?
Sent from my Full Android on Stingray using xda premium
I've been trying to get root by installing an su-binary.zip via cwm. But I think, the current binary doesn't work with ICS 4.0.3.
There's another user on the chainsdd-website, using the NexusS with 4.0.3, complaining, that the current binary refuses to work. Have a look at the bottom: androidsu (dot) com/superuser/ (I'm currently not allowed to post outside links, sorry. )
Edit:
I just had a look at my logcat:
E/su ( 2809): sudb - Opening database
E/su ( 2809): sudb - Database opened
E/su ( 2809): sudb - Database closed
E/ActivityManager( 152): Activity Manager Crash
E/ActivityManager( 152): java.lang.IllegalArgumentException: Unknown URI type: 7
E/ActivityManager( 152): at android.net.Uri$1.createFromParcel(Uri.java:1734)
E/ActivityManager( 152): at android.net.Uri$1.createFromParcel(Uri.java:1723)
E/ActivityManager( 152): at android.content.Intent.readFromParcel(Intent.java:6131)
E/ActivityManager( 152): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 152): at android.content.Intent.readFromParcel(Intent.java:6153)
E/ActivityManager( 152): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 152): at android.content.Intent$1.createFromParcel(Intent.java:6117)
E/ActivityManager( 152): at android.content.Intent$1.createFromParcel(Intent.java:6115)
E/ActivityManager( 152): at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:298)
E/ActivityManager( 152): at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1545)
E/ActivityManager( 152): at android.os.Binder.execTransact(Binder.java:338)
E/ActivityManager( 152): at dalvik.system.NativeStart.run(Native Method)
Hm... For this I would have to stick deeper into the source of the superuser.apk I think: https://github.com/ChainsDD/
I test on mz601 smooth and I wifi ok. It great on browser very fast on ics
Market ok
Gmail ok
Game for tegra nvidia dungeon defenders ok look so fast os
MasterYety said:
I've been trying to get root by installing an su-binary.zip via cwm. But I think, the current binary doesn't work with ICS 4.0.3.
There's another user on the chainsdd-website, using the NexusS with 4.0.3, complaining, that the current binary refuses to work. Have a look at the bottom: androidsu (dot) com/superuser/ (I'm currently not allowed to post outside links, sorry. )
Edit:
I just had a look at my logcat:
E/su ( 2809): sudb - Opening database
E/su ( 2809): sudb - Database opened
E/su ( 2809): sudb - Database closed
E/ActivityManager( 152): Activity Manager Crash
E/ActivityManager( 152): java.lang.IllegalArgumentException: Unknown URI type: 7
E/ActivityManager( 152): at android.net.Uri$1.createFromParcel(Uri.java:1734)
E/ActivityManager( 152): at android.net.Uri$1.createFromParcel(Uri.java:1723)
E/ActivityManager( 152): at android.content.Intent.readFromParcel(Intent.java:6131)
E/ActivityManager( 152): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 152): at android.content.Intent.readFromParcel(Intent.java:6153)
E/ActivityManager( 152): at android.content.Intent.<init>(Intent.java:6126)
E/ActivityManager( 152): at android.content.Intent$1.createFromParcel(Intent.java:6117)
E/ActivityManager( 152): at android.content.Intent$1.createFromParcel(Intent.java:6115)
E/ActivityManager( 152): at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:298)
E/ActivityManager( 152): at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1545)
E/ActivityManager( 152): at android.os.Binder.execTransact(Binder.java:338)
E/ActivityManager( 152): at dalvik.system.NativeStart.run(Native Method)
Hm... For this I would have to stick deeper into the source of the superuser.apk I think: https://github.com/ChainsDD/
Click to expand...
Click to collapse
https://gist.github.com/1489990

[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

LG G3 D855 Wifi authentication problem with CM 12.1 - supplicant connection error ?

Hello everybody,
i'm new to this board as a poster, but been reading over the last ~ 10 years.
I've been searching here (and about everywhere) else for my problem and tried every suggested solution - even putting it in the fridge or restarting it during full moon reciting the most popular quotes from Linus Torvalds backwards... nothing worked. So you guys and girls are my last resort...
I am running Cyanogen Mod 12.1 (most actual nightly builds) on a LG G3 (d855) phone.
Problem:
After scanning for APs, mine (or the ones i have credentials to) are found, but i can't connect. It tells me "Authentication error".
As being an android developer myself i also tried to dig in. According to logcat the following happens after i activate wifi (with filter for "error"):
Code:
11-12 17:59:43.899 814-1537/? E/WifiService﹕ Invoking mWifiStateMachine.setWifiEnabled
11-12 17:59:44.718 814-1079/? E/WifiMonitor﹕ killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
11-12 17:59:44.733 814-1079/? E/WifiHW﹕ Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
11-12 17:59:44.865 814-1079/? E/WifiConfigStore﹕ Error parsing configuration: java.io.FileNotFoundException: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory)
11-12 17:59:44.874 814-1079/? E/WifiHAL﹕ virtual int WifiVendorCommand::create() ifindex obtained:30
11-12 17:59:44.874 814-1079/? E/WifiHAL﹕ virtual int WifiVendorCommand::set_iface_id(const char*) ifindex obtained:30
11-12 17:59:44.875 814-1079/? E/WifiHAL﹕ wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-524
11-12 17:59:44.890 814-1093/? E/WifiHAL﹕ wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
11-12 17:59:44.890 814-1093/? E/WifiScanningService﹕ could not get scan capabilities
11-12 17:59:49.005 814-1079/? E/WifiStateMachine﹕ WifiStateMachine Disconnected CMD_START_SCAN source -2 104, 107 -> obsolete
11-12 17:59:49.008 814-1079/? E/WifiStateMachine﹕ WifiStateMachine Disconnected CMD_START_SCAN source -2 105, 107 -> obsolete
11-12 17:59:54.899 814-1079/? E/WifiStateMachine﹕ WifiStateMachine Disconnected CMD_START_SCAN source -2 106, 107 -> obsolete
11-12 18:00:07.046 814-1079/? E/WifiConfigStore﹕ rewrite network history for "ch4os"-WPA_PSK
After deactivation:
Code:
11-12 18:00:51.844 814-1789/? E/WifiService﹕ Invoking mWifiStateMachine.setWifiEnabled
11-12 18:00:51.869 814-1079/? E/WifiStateMachine﹕ Unexpected BatchedScanResults :null
11-12 18:00:51.885 814-1079/? E/WifiStateMachine﹕ SupplicantStoppingState: stopSupplicant init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
This error appeared without any direct cause but COULD be related to an update to the most recent nightly, i haven't tried wifi for ~ 1 day after updating.
What i did for solving this problem:
Complete Wipe (Factory reset / advanced wipe using TWPR)
Trying another wifi config on the router (works fine for other devices)
The superstitious deactivate-wifi/airplane mode/restart/re-activate wifi without deactivating airplane mode
Note: after this it worked for like 5 seconds; was not reproducable afterwards
Putting it in the fridge, restarting and trying again
Ensuring wpa_supplicant.conf in /data/misc/wifi/ has permission system:wifi or wifi:wifi and chmod 660 (rw-rw----)
Deleting wpa_supplicant.conf
IMHO is this issue not related to my settings, because it even did not work after a full wipe.
This just does not make any sense to me anymore... Any suggestion is very much appreciated!
Kind regards

"Welcome" Screen of ROM Fails to Respond to Touch

I rooted my SGH-T999, running Android 4.3, flashing TWRP recovery w/ Odin.
The rooting was successful.
Now, on to the part where I ran into trouble.
Problem: I can't successfully install any ROMs for Android M or later.
NOTE: I need Android M or later to have more control over individual apps' permissions.
I tried to flash Pac-ROM through TWRP, like so:
(from TWRP home menu)
1. Wipe>Swipe to Factory Reset
2. Go Back to Home Menu
3. Install>Select pac_d2tmo_MM.Beta.Official_20160920-165602.zip>Swipe to confirm Flash
Note: The first time I tried to flash Pac-ROM, I wasn't aware of GApps. So, I didn't flash it.
4. Reboot
The phone booted to the "Welcome/Language Selection" screen, but I couldn't select a language.
It seems that the UI elements belonging to the "Welcome" screen fail to respond to touch, while other UI elements respond normally (as demonstrated at the end of the video at the URL below).
All attempts to re-flash, since, have included the additional step off adding the GApps zip (for ARM, Android 6.0) to the "ZIP Queue".
However, all attempts end the same way.
I've documented the process in the video @ the following URL: youtu.be/EZTwaURkRSs
Another strange behavior (that isn't apparent in the video) is that, immediately after being shown on the display, the "Welcome" screen looks fine for a few hundred milliseconds or so before the screen is drawn with a yellowish-hue. As if blue-light filtering kicks in (even when the system clock is mid-day).
I also tried to flash a different ROM (Oct-OS OCT-M-R3) on a few of the attempts, but again I observed the same exact behavior ("Welcome" screen's yellowish hue and lack of response to touch).
It doesn't seem to be a hardware issue, because touch does work, just not on the "Welcome" screen.
I'm fairly certain I've selected the correct ROM for the model.
So, what did I mess up?
I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again
andynoob said:
I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again
Click to expand...
Click to collapse
Do you mean that you were able to flash a ROM successfully, after flashing stock (4.4.2)?
Or, you were ONLY able to flash stock (4.4.2) successfully?
Thank you for the reply,
Gerald
I just restored my twrp backup of stock os .. Had urgent work so couldn't try to flash those ROMs again.. will try them next week
UPDATE:
So, I successfully restored my stock backup.
With the stock setup I experienced no problems.
Since my original post, I've alternated between restoring stock backup and flashing ROMs.
I tried flashing Oct-OS and Pac-ROM, again and again.
I also tried to install LineageOS, as well.
I am able to install CyanogenMod 12.1, but this doesn't meet my requirement of android version 6 or later.
Installation of any of the custom ROMs has resulted in the same behavior demonstrated in the video (youtu.be/EZTwaURkRSs):
- after boot, device fails to respond to touch input
- however, device does accept touch input on some UI objects. so, I don't think it's a screen/hardware issue
How can I debug further?
I'd like to try to capture some sort of boot log, but adb is "offline" during boot process.
And, since I can't make it past the "language selection/welcome" screen, I can't get to settings and enable USB debugging.
UPDATE:
I managed to enable ADB during boot, by using the ADB shell while the device was in recovery mode.
Code:
[email protected] ~ $ adb push ~/.android/adbkey.pub /data/misc/adb/
[email protected] ~ $ adb shell
~# cd /data/misc/adb/
/data/misc/adb# cat adbkey.pub > adb_keys
/data/misc/adb# cd /
~# mkdir /system2
~# mount -o rw /dev/block/mmcblk0p14 /system2 ## NOTE: for this command, had to figure out which partition was the system partition; here it was /dev/block/mmcblk0p14
~# echo "persist.service.adb.enable=1" >> default.prop
~# echo "persist.service.debuggable=1" >> default.prop
~# echo "persist.sys.usb.config=mtp,adb" >> default.prop
~# echo "persist.service.adb.enable=1" >> /system2/build.prop
~# echo "persist.service.debuggable=1" >> /system2/build.prop
~# echo "persist.sys.usb.config=mtp,adb" >> /system2/build.prop
~# ## now press Ctrl-D to exit the ADB shell
NOTE: thanks to @ErnestChia for the following post forum.xda-developers.com/showpost.php?p=63829295&postcount=27
So, I was able to get a logcat during the SetupWizard.
There were 3 lines, related to the SystemUI, that were repeated over and over.
Code:
W BroadcastQueue: Timeout of broadcast BroadcastRecord{51dfd23 u-1 android.intent.action.TIME_TICK} - [email protected], started 10010ms ago
W BroadcastQueue: Receiver during timeout: BroadcastFilter{a4079bf u0 ReceiverList{4b103de 730 com.android.systemui/10018/u0 remote:448f719}}
I ActivityManager: Skipping duplicate ANR: ProcessRecord{768d889 730:com.android.systemui/u0a18} Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
All I've gathered is that SystemUI isn't responding.
Which seems to have started during boot, with the following output.
Code:
W ActivityManager: Timeout executing service: ServiceRecord{dd2251a u0 com.android.systemui/.ImageWallpaper}
E ActivityManager: ANR in com.android.systemui
E ActivityManager: Reason: executing service com.android.systemui/.ImageWallpaper
E ActivityManager: 4.1% 730/com.android.systemui: 2.2% user + 1.8% kernel / faults: 1246 minor 2 major
SystemUI Stack Trace
Code:
Cmd line: com.android.systemui
Build fingerprint: 'samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys'
ABI: 'arm'
Build type: optimized
Zygote loaded classes=3986 post zygote classes=991
Intern table: 46441 strong; 62 weak
JNI: CheckJNI is off; globals=427 (plus 368 weak)
Libraries: /system/lib/libandroid.so /system/lib/libcompiler_rt.so /system/lib/libjavacrypto.so /system/lib/libjnigraphics.so /system/lib/libmedia_jni.so /system/lib/libsoundpool.so /system/lib/libwebviewchromium_loader.so libjavacore.so (8)
Heap: 5% free, 12MB/13MB; 84371 objects
Dumping cumulative Gc timings
Total number of allocations 84371
Total bytes allocated 12MB
Total bytes freed 0B
Free memory 813KB
Free memory until GC 813KB
Free memory until OOME 179MB
Total memory 13MB
Max memory 192MB
Zygote space size 1972KB
Total mutator paused time: 0
Total time waiting for GC to complete: 0
Total GC count: 0
Total GC time: 0
Total blocking GC count: 0
Total blocking GC time: 0
...
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x745992a0 self=0xb77f9b30
| sysTid=730 nice=0 cgrp=default sched=0/0 handle=0xb6efab44
| state=S schedstat=( 0 0 0 ) utm=64 stm=14 core=1 HZ=100
| stack=0xbe5d0000-0xbe5d2000 stackSize=8MB
| held mutexes=
native: #00 pc 0004290c /system/lib/libc.so (__ioctl+8)
native: #01 pc 00049391 /system/lib/libc.so (ioctl+14)
native: #02 pc 0001e8c9 /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+132)
native: #03 pc 0001eefb /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+38)
native: #04 pc 0001f0b1 /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+124)
native: #05 pc 0001a0b3 /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
native: #06 pc 00089471 /system/lib/libandroid_runtime.so (???)
native: #07 pc 00db9189 /data/dalvik-cache/arm/[email protected]@boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+140)
at android.os.BinderProxy.transactNative(Native method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:421)
at java.lang.reflect.Method.invoke!(Native method)
at android.hardware.camera2.utils.Decorator.invoke(Decorator.java:80)
at java.lang.reflect.Proxy.invoke(Proxy.java:393)
at android.hardware.ICameraService.getCameraCharacteristics(ICameraService.java:-2)
at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:635)
at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:99)
- locked <0x0da89d30> (a java.lang.Object)
at com.android.systemui.statusbar.policy.FlashlightController.getCameraId(FlashlightController.java:126)
at com.android.systemui.statusbar.policy.FlashlightController.<init>(FlashlightController.java:62)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:1087)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3285)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3281)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:619)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:800)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:230)
at com.android.systemui.statusbar.ServiceMonitor.-wrap5(ServiceMonitor.java:-1)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5466)
at java.lang.reflect.Method.invoke!(Native method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
i solved this issue by flashing the pac rom 6.0 from at&t . (Flash only the rom )
Do you have a copy of carbon ROM or Pac man for the d2tmo?

Categories

Resources