Related
Hi, I'm new to this so I hope I'm posting in the right place. I have an HTC Desire running AdamG's Oxygen v1.0.4, but I'd like to put some of the old HTC apps back on the phone, like the music player/widget, news and weather app/widget, etc..
So what I've done so far is extracted the system.img file from my Nandroid backup with unyaffs to get the apk files. I then put the app folder back onto my SD Card and tried to use Root Explorer to copy the apks I wanted back into the system/app folder on my phone, but when I try this, nothing is copied across. I have it in R/W mode and it flashes pasting quickly on the screen but when that disappears, there is no copied app and no less space in the folder.
Is it even possible to install HTC's system apps onto a different version of android? If so, what am I doing wrong? Also, if I do manage to copy the apks into the system/apps folder, do they need the corresponding odex files to work?
Thank you.
I've been trying to do the same thing. I unyaff'd the image, then tried 'adb install HTCAlbum.apk'
This fails with "Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]"
Googling around says this is to do with it not being signed. However checking this with "jarsigner -verify -verbose -certs HTCAlbum.apk" shows it is signed OK. Have tried re-signing it too, but that made no difference.
logcat output from the install:
Code:
D/AndroidRuntime( 1943): >>>>>> Booting Oxygen by AdamG <<<<<<
D/AndroidRuntime( 1943):
D/AndroidRuntime( 1943): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 1943): CheckJNI is OFF
D/dalvikvm( 1943): creating instr width table
D/AndroidRuntime( 1943): Calling main entry com.android.commands.pm.Pm
D/dalvikvm( 1485): GC_EXPLICIT freed 5K, 54% free 2558K/5511K, external 1625K/2137K, paused 24ms
W/ActivityManager( 147): No content provider found for:
D/dalvikvm( 147): GC_EXPLICIT freed 120K, 44% free 6780K/11911K, external 4453K/5026K, paused 75ms
D/AndroidRuntime( 1943): Shutting down VM
D/dalvikvm( 1943): GC_CONCURRENT freed 212K, 71% free 301K/1024K, external 0K/0K, paused 0ms+0ms
D/jdwp ( 1943): adbd disconnected
There are several different provider apk's but they don't seem to install either...
Posting this in the hope this gives you a pointer and you get further.
I was trying to port a Htc Magic ROM with dsi xda's kitchen ..but its getting stuck in a bootloop at the boot animation. Recovery.log is fine, nothing catastrophic there.But logcat had to say this:-
W/PackageParser( 449): Unknown element under <application>: intent-filter at /system/app/com.htc.MusicWidget.apk Binary XML file line #9
I/PackageManager( 449): /system/app/com.htc.MusicWidget.apk changed; collecting certs
D/installd( 81): DexInv: --- BEGIN '/system/app/com.htc.MusicWidget.apk' ---
D/dalvikvm-sfm( 568): Zip inflate: partial write (will retry): (8152 of 32768)
E/dalvikvm-sfm( 568): Zip inflate: write failed: No space left on device
W/dalvikvm( 568): DexOptZ: extraction of classes.dex from /system/app/com.htc.MusicWidget.apk failed
W/installd( 81): DexInv: --- END '/system/app/com.htc.MusicWidget.apk' --- status=0xff00, process failed
E/installd( 81): dexopt failed on '/cache/dalvik-cache/[email protected]@[email protected]' res = 65280
and this is repeated a lot more times for many other apps.
Complete logcat here: http://pastebin.com/6D7BMqE6
does this mean that the system partition is too small for this rom??
Is it possible to move some of the system apps to data/app folder??
Is there any way to expand it or resize the partitions?(Magic and Wildfire both have the same 512 Mb Roms)
What would be the best course of action?
Did you wiped Dalvik-cache ? This is a Dalvik-cache issue. Does the ROM uses Apps2SD ?
h4oxer said:
Did you wiped Dalvik-cache ? This is a Dalvik-cache issue. Does the ROM uses Apps2SD ?
Click to expand...
Click to collapse
Sorry,
The rom uses Apps2SD(Is this a problem)?.But i did wipe the Dalvik-cache.Will try again.
No Dalvik wipe doesnt help.
As I don't seem to have permissions to post in the developers' forum.. here goes:
When installing the OTA patch for MIUI 1.9.23 to 1.9.30 on my Desire, a reboot ended being stuck in the Recovery.
logcat showed me the following:
D/AndroidRuntime( 1503):
D/AndroidRuntime( 1503): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1503): CheckJNI is OFF
D/dalvikvm( 1503): creating instr width table
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/core.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/core.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/bouncycastle.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/bouncycastle.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/ext.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/ext.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/framework.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/framework.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/android.policy.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/android.policy.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/services.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/services.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/core-junit.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/core-junit.jar'
E/dalvikvm( 1503): No valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar'
W/dalvikvm( 1503): JNI_CreateJavaVM failed
E/AndroidRuntime( 1503): JNI_CreateJavaVM failed
These errors returned in a loop.
Looking on the system itself, /data/dalvik-cache seemed to be missing.
After creating this directory, the phone continued booting.
So this would be a quick-fix.
Yet I didn't take into account the necessary symbol links for the a2sd to work properly yet.
Can someone point me to some docs which symbol links I should apply?
Thx for your help.
According to the logcat, your dalvik-cache is missing. Wipe dalvik cache from recovery.
If that won't help, create the following directory and then wipe:
/data/dalvik-cache
If still does not work, check THIS thread.
Hi davebugyi
Thanks for your answer.
That's what I did, and it fixed the problem.
I wanted to write that in the original thread, but I didn't have enough interaction on this forum (10 posts) to allow me to write there directly.
Cheers!
Hello,
today as i was accessing my email on Opera Mobile, the SuperSU window popped up by itself and asked me for root acces for a program called "debuggerd.exynosabuse". I dont know what this debuggerd.exynosabuse is and i didnt open any apk before the SU window suddenly popped up..so naturally i denied it root access...then I went into the SuperSU log file and I saw that it kept trying to get root access for two minutes continuously and about 15 tries... also it doesnt have any icon in the apps section of SuperSU. Any ideas what this is about?
Thanks
Look for the app in app drawer named exynos abuse.
Sent from my GT-N7100 using xda app-developers app
Ok. So I m looking for what exactly? I have already mentioned that it is called debuggerd.exynosabuse. it is not the exynos abuse apk, which I used to root my phone and patch the exploit. It is a different app that has no icon in the SU logfile. This debuggerd is always trying to get root access to modify some root files but I have it denied in SU. It tries to get root access 50 times a day or more. What is this program and where did it come from and what should I do with it. Thanks.
Maybe clear data...
Sent from my GT-N7100 using xda app-developers app
You are not alone
http://www.chainfire.eu/articles/126/ExynosAbuse_APK_released_/
may be malware
Try a full wipe including system cache and dalvik and data.
Then flash latest stock rom and root via cfautoroot.
Also backing up anything using any software is not recommended as malware might have infected it.
Sent from my GT-N7100 using xda app-developers app
I just had the same experience for the first time, unfortunately seeing it was a part of ExynosAbuse, I authorized it...
I then saw a lot going on, and in between SuperSU notifications, I saw Adblock Plus notifications too... Maybe related?
As I said try full wipe and flash latest stock rom.
Sent from my GT-N7100 using xda app-developers app
Well, I'd like to know before I wipe, it's not an easy thing to do for me right now, plus if it's something in the app and I reinstall the app after wiping, I'll have the same problem...
Than you for your input Dr Ketan. I see that this is a relatively new problem and its got people wondering/worried, I appreciate that this issue has come to your attention.
Dear UtkarshGupta, Sure anyone can nuke their phone and wipe all and flash new, but thats not what the xda community is about. We are here to share, communicate, support, enhance, develop, and learn.
Understanding the problem would be the first step in to solving it. When we know what is the size of the problem, we would then know how to deal with it appropriately. It might be something simple that can be cleaned easily, no nuke needed.
As for me, I am happy with my 4.1.1 jb. I dont want to flash any new firmware.
By now I have taken several screen shots of it trying to get root access to many files and even it was trying to change values and commands but all were denied ofcourse because I have it blocked in SU. If it would help the devs or anyone else, I can attach the screenshots if need be.
Well, I have some news.
I removed debuggerd from SuperSU authorizations. Later on, I used Chrome and I got all these requests again. This time, I refused (and took screenshots). At the end, Chrome didn't load the webpage. But mostly, I had no internet connection at all!
Then, I remembered that the first time I had the request, it was when using the web browser. And then, I realized it happened the day after I installed Android Adblock Plus.
I uninstalled it, rebooted, and then my connection worked. I'll try to remove debuggerd from the SuperSU blacklist to see if it still happens.
Anyone can correlate?
Hi,
I had the same problems :
- debuggerd.exynosabuse requested SU privileges
- enter in an infinite loop, use a lot of battery power, automatic reboot of the device more than twice a day
So I tried to remove these files. In order to do that you need :
- a rooted device (su installed and working)
- Android Terminal Emulator installed from Googleplay in the device
Launch Android Terminal Emulator
Enter the commands below :
su (accept su privileges, prompt disappears)
mount -o remount,rw /system
cd /system/bin
rm debuggerd
rm debuggerd.exynosabuse
reboot
It works for me. I hope it will work for you.
debuggerd.exynosabuse
From what I can see, the /system/bin/debugger has been replaced with a script that reads:
#!/system/bin/sh
chmod 0400 /dev/exynos-mem
/system/bin/debuggerd.exynosabuse
Then, debuggerd.exynosabuse seems to launch instead of the normal debuggerd. I suppose some applications may call debuggerd by design, which explains why there are some random popups. Here are the "strings" for debuggerd.exynosabuse which appears to be the renamed original (need to verify). This thread then shows that it appears to do the reported actions.. by design? Would be interesting to trace it down a bit more to determine if the carrier/app developer is sending process dumps back to home for analysis which could contain sensitive data.
ELF
p\4
/system/bin/linker
__aeabi_unwind_cpp_pr0
__dso_handle
__INIT_ARRAY__
__FINI_ARRAY__
memset
property_get
atoi
__stack_chk_fail
__stack_chk_guard
__android_log_vprint
open
close
__errno
strcmp
strlen
vsnprintf
__aeabi_unwind_cpp_pr1
snprintf
strcpy
fprintf
__sF
calloc
free
strdup
fputs
strftime
write
strerror
strtoul
_edata
__bss_start
_end
realloc
memmove
read
socket_local_client
socket_local_server
getsockopt
fopen
fgets
fclose
fcntl
poll
accept
usleep
ioctl
dump_tombstone
dump_backtrace_to_file
getpid
__isthreaded
memcmp
sprintf
__libc_init
fchown
chown
stat
mkdir
sigaction
inotify_init
inotify_add_watch
kill
ptrace
opendir
readdir
readdir_r
closedir
fileno
waitpid
bsd_signal
time
system
fflush
localtime_r
unwind_backtrace_ptrace
demangle_symbol_name
get_backtrace_symbols_ptrace
find_symbol_ptrace
free_backtrace_symbols
format_backtrace_line
try_get_word_ptrace
load_ptrace_context
free_ptrace_context
liblog.so
libcutils.so
libc.so
libcorkscrew.so
/proc/%d/cmdline
%F %T
----- pid %d at %s -----
Cmd line: %s
<unknown>
/proc/%d/comm
"%s" sysTid=%d
Could not attach to thread: %s
Could not obtain stack trace for thread.
%s
ptrace detach from %d failed: %s
/proc/%d/task
----- end %d -----
Sending request to dump task %d.
Error dumping backtrace.
Error dumping tombstone.
Tombstone written to: %s
cannot get credentials
timed out reading tid
read failure? %s
invalid crash request of size %d
/proc/%d/task/%d
tid %d does not exist in pid %d. ignoring debug request
/proc/%d/status
Tgid:
Uid:
Gid:
tid %d does not exist. ignoring explicit dump request
ptrace attach failed: %s
debug.db.uid
failed responding to client: %s
ptrace continue failed: %s
dumpstate -k -t -z -d -o /data/log/dumpstate_app_native -m %d
[email protected]%s
process stopped due to unexpected signal %d
********************************************************
* Process %d has been suspended while crashing. To
* attach gdbserver for a gdb connection on port 5039
* and start gdbclient:
* gdbclient app_process :5039 %d
* Wait for gdb to start, then press HOME or VOLUME DOWN key
* to let the process continue crashing.
********************************************************
/sys/class/leds/red/brightness
/sys/class/leds/green/brightness
/sys/class/leds/blue/brightness
/sys/class/leds/red/device/blink
/sys/class/leds/left/cadence
0,0
255
1,0
debuggerd resuming process %d
debuggerd committing suicide to free the zombie!
logd
android:debuggerd
debuggerd: Oct 4 2012 16:24:21
Usage: -b [<tid>]
-b dump backtrace to console, otherwise dump full tombstone file
If tid specified, sends a request to debuggerd to dump that task.
Otherwise, starts the debuggerd server.
out of memory
/dev/input
could not get event, %s
could not get event
SIGILL
SIGABRT
SIGBUS
SIGFPE
SIGSEGV
SIGPIPE
SIGSTKFLT
SIGSTOP
ILL_ILLOPC
ILL_ILLOPN
ILL_ILLADR
ILL_ILLTRP
ILL_PRVOPC
ILL_PRVREG
ILL_COPROC
ILL_BADSTK
BUS_ADRALN
BUS_ADRERR
BUS_OBJERR
FPE_INTDIV
FPE_INTOVF
FPE_FLTDIV
FPE_FLTOVF
FPE_FLTUND
FPE_FLTRES
FPE_FLTINV
FPE_FLTSUB
SEGV_MAPERR
SEGV_ACCERR
UNKNOWN
pid: %d, tid: %d, name: %s >>> %s <<<
pid: %d, tid: %d, name: %s
#%02d %08x %08x %s (%s+%u)
#%02d %08x %08x %s (%s)
%08x %08x %s (%s+%u)
%08x %08x %s (%s)
#%02d %08x %08x %s
%08x %08x %s
backtrace:
%s
stack:
........ ........
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
ro.build.fingerprint
unknown
Build fingerprint: '%s'
cannot get siginfo: %s
signal %d (%s), code %d (%s), fault addr %08x
cannot get siginfo for %d: %s
memory map around fault addr %08x:
%08x-%08x %s
(no map below)
(no map for address)
(no map above)
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
signal %d (%s), code %d (%s), fault addr --------
/data/tombstones
/data/tombstones/tombstone_%02d
failed to open tombstone file '%s': %s
DEBUG
waitpid failed: %s
unexpected waitpid response: n=%d, status=%08x
timed out waiting for tid=%d to die
timed out waiting for tid=%d to stop
%08x
%08lx
%s %s
memory near %.2s:
code around pc:
code around lr:
cannot get registers: %s
r0 %08x r1 %08x r2 %08x r3 %08x
r4 %08x r5 %08x r6 %08x r7 %08x
r8 %08x r9 %08x sl %08x fp %08x
ip %08x sp %08x lr %08x pc %08x cpsr %08x
d%-2d %016llx d%-2d %016llx
scr %08lx
r0r1r2r3r4r5r6r7r8r9slfpipsp
GCC: (GNU) 4.6.x-google 20120106 (prerelease)
GNU
gold 1.10
aeabi
ARM v7
.shstrtab
.interp
.dynsym
.dynstr
.hash
.rel.dyn
.rel.plt
.text
.ARM.extab
.ARM.exidx
.rodata
.preinit_array
.init_array
.fini_array
.ctors
.dynamic
.got
.bss
.comment
.note.gnu.gold-version
.ARM.attributes
be careful 'RM'ing everything
tcharlier said:
Hi,
I had the same problems :
- debuggerd.exynosabuse requested SU privileges
- enter in an infinite loop, use a lot of battery power, automatic reboot of the device more than twice a day
So I tried to remove these files. In order to do that you need :
- a rooted device (su installed and working)
- Android Terminal Emulator installed from Googleplay in the device
Launch Android Terminal Emulator
Enter the commands below :
su (accept su privileges, prompt disappears)
mount -o remount,rw /system
cd /system/bin
rm debuggerd
rm debuggerd.exynosabuse
reboot
It works for me. I hope it will work for you.
Click to expand...
Click to collapse
should you remove 'debuggerd' & 'debuggerd.exynosabuse' they would simply return from the dead.
i believe they are trying to catch and identify a neardeath experience, in this case relating to exynosabuse. this could be the 4.1.2 upgrade and exynosabuse not sitting comfortably together or it may have been intended to work this way - chainfire is the best source for this answer.
debuggerd is called to examine the problem occurrence point on the source code from a crash dump before the main function is carried out. any prog's with dynamic links can automatically connect to debuggerd and generate crash dumps.
i do find it a bit unsettling when root privileges are asked for something that was never installed as an apk and then devours cpu and battery until nothing is left.
more research needs to be done as to what is really going on...
refer to Koba's blog - 'debuggerd of Android'
No more bugging
Got sick and tired of it requesting su privileges all the time. Copied debuggerd and debuggerd.exy to sd card just in case and then deleted the ones in system/bin, that are doing all the damage, via es file explorer with root access coz couldnt be deleted any other way and its been 3 days since and it didnt come back and all is clean on su logs no more requests from it.
By the way its got nothing to do with 4.1.2 sitting with exynosabuse.apk as im still running 4.1.1.
Problem solved...uptill now.
Noob.Saibot said:
Got sick and tired of it requesting su privileges all the time. Copied debuggerd and debuggerd.exy to sd card just in case and then deleted the ones in system/bin, that are doing all the damage, via es file explorer with root access coz couldnt be deleted any other way and its been 3 days since and it didnt come back and all is clean on su logs no more requests from it.
By the way its got nothing to do with 4.1.2 sitting with exynosabuse.apk as im still running 4.1.1.
Problem solved...uptill now.
Click to expand...
Click to collapse
apologies, i should have been clearer, as i too had root privy requests whilst on 4.1.1 - however the frequency of this increased noticeably once upgraded to 4.1.2. also i have no other apk's title being added to the debuggerd name in system/bin. i had only 2 files in system/bin - the 1st was "debuggerd" and the second "debuggerd.exynosabuse". this seems to be saying that something is specific enough about exynosabuse for the separately titled file to appear.
if anyone finds any other files identified in this way please comment.
so in all, i should have said, for me, that the debuggerd bugged me more, via the massive increase in root requests, when sitting with 4.1.2 than it did when i had 4.1.1 installed.
again, anyone with ideas as to what and why this debuggerd saga is taking place would be greatly appreciated.
I'm having the same issue, denying debuggerd.exynosabuse in SuperSU just causes my phone to reboot when the requests come through. This happens multiple times a day.
It is probably a malware.
Update to 4.1.2 asap.
Sent from my GT-N7100 using xda app-developers app
Noob.Saibot said:
Got sick and tired of it requesting su privileges all the time. Copied debuggerd and debuggerd.exy to sd card just in case and then deleted the ones in system/bin, that are doing all the damage, via es file explorer with root access coz couldnt be deleted any other way and its been 3 days since and it didnt come back and all is clean on su logs no more requests from it.
By the way its got nothing to do with 4.1.2 sitting with exynosabuse.apk as im still running 4.1.1.
Problem solved...uptill now.
Click to expand...
Click to collapse
I am getting "debuggered.exynosabuse cannot be deleted" when I try this method
EDIT: didn't have it set to write, got it to work. Will report back in a few days on whether or not it shows up again.
---------- Post added at 02:39 PM ---------- Previous post was at 02:23 PM ----------
UtkarshGupta said:
It is probably a malware.
Update to 4.1.2 asap.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Others in this thread have said that updating doesn't fix the problem, and that it's actually more persistent on 4.1.2
I appreciate offering your assistance, but does anyone know for certain what's going on or are we all just speculating?
I followed all the instructions for adb and successfully installed twrp, and the firefirefire bootloader, I then went on to make a backup and flash the smoothrom rom and g apps. Everything was fine except that I noticed when the screen would turn off with the 30-second timer, it wouldn't "suspend" the kindle, but completely turn it off; in addition it sometimes happened when clicking the power button. I also encountered that whilst using the stock wall charger either letting it lock, or using the button the screen would go gray and not suspend, which sometimes followed by turning off completely.
I've done a clean install 5 times, and even installed the CM10 Hellfire rom to see if that one was free from the grasp of this bug, but it also shares the same fate. Does anyone have a solution to this, because I've searched the forum, and the threads themselves and it seems like I'm the only one suffering from this.
In also turns off after 30 minutes of not using it?
Do you know how to get a logcat? Get one and put it in pastebin or something similar, and post a link here. Don't post your entire logcat here.
Also, what is your governor set to?
http://pastebin.com/ihqRfzWz
Bowsa2511 said:
http://pastebin.com/ihqRfzWz
Click to expand...
Click to collapse
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
soupmagnet said:
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
Click to expand...
Click to collapse
This has happened on all the roms I've tried, the governor is "interactive-cfq", the minimum is 300 and max 1200. The problem doesn't occur when it's plugged in, but occurs when it's not; what I mean by this is that when the 30 second screen-off timer sets off, instead of just locking the device, it turns off completely and I have to boot the kindle once more. Pressing the lock button on the bottom also triggers this and I've tried clicking "fix permissions" in twrp to see if that does anything, but it doesn't.
soupmagnet said:
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
Click to expand...
Click to collapse
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Bowsa2511 said:
This has happened on all the roms I've tried, the governor is "interactive-cfq", the minimum is 300 and max 1200. The problem doesn't occur when it's plugged in, but occurs when it's not; what I mean by this is that when the 30 second screen-off timer sets off, instead of just locking the device, it turns off completely and I have to boot the kindle once more. Pressing the lock button on the bottom also triggers this and I've tried clicking "fix permissions" in twrp to see if that does anything, but it doesn't.
Click to expand...
Click to collapse
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
twa_priv said:
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Click to expand...
Click to collapse
The computer doesn't even detect the kindle via adb, or any types of mounting anymore; I only followed the instructions, wiped what needed to be wiped, installed the rom, then gapps and rebooted. Even in it's pristine state it still suffers from the problem.
soupmagnet said:
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
Click to expand...
Click to collapse
I've also tried doing that with SetCPU to see if it was the slowness of 300mhz causing the SoD, but the same symptoms occured
Edit: I'm going to download today's build, with the latest g apps then do the following:
•1. Wipe factory reset.
•2. Wipe cache.
•3. Wipe dalvik.
•4. Wipe system.
•5. Flash Rom zip.
•6. Flash gapps zip.
•7. Select reboot, then system if prompted.
Doing that would technically be doing everything in the pristine manner (Unless I have to change a frequency or governor?)
Just in case you missed it...
soupmagnet said:
...try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
Click to expand...
Click to collapse
soupmagnet said:
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
Click to expand...
Click to collapse
soupmagnet said:
Just in case you missed it...
Click to expand...
Click to collapse
Here's the log
twa_priv said:
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Click to expand...
Click to collapse
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
twa_priv said:
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
Click to expand...
Click to collapse
I occasionally get a sleep of death as well. I have had it happen with the CyanogenMod Nightly dated cm-10.1-20130311-NIGHTLY-otter.zip. It did not happen when my kindle was running the stock rom. I'm still working to get fully up to speed on how to chase this sort of thing, and all of you guys posting helpful info is appreciated.
twa_priv said:
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
Click to expand...
Click to collapse
I flashed the stock rom, and the modaco gr9 rom and the problem doesn't persist on either, i'm going to flash CM10 once more and do that
Interestingly enough, this 4.1 build doesn't have the sleep of death, wonder what the difference is
http://goo.im/devs/loosethisskin/otter-cm10/cm-10-20121211-1416-otter-sgt7.zip
Interesting, I may try that one if bumping up the governor to 600 does not solve the problem.
Sent from my Amazon Kindle Fire using XDA Premium HD app
muiriddin said:
Interesting, I may try that one if bumping up the governor to 600 does not solve the problem.
Sent from my Amazon Kindle Fire using XDA Premium HD app
Click to expand...
Click to collapse
Yeah i tried everything from trying out kindle roms, 4 different roms , gapps, permission fixing, dreamscape settings; inactivity settings, governors and clock frequencies, they all have the same problem. That test build i posted has been running perfectly all day now! No bugs with or without charger and no sleep of death! Its 4.1.2, but that is worth not having an unusable kindle
Don't forget to flash the CM10 (4.1) gapps
After one and a half days of testing I have not gotten a SOD with twa_priv's rom from this forum here:
http://forum.xda-developers.com/showthread.php?t=2051331
To be specific, I'm using 20130323-2135-otter-sgt7.zip with gapps-jb-20130301-signed.zip
This is running 4.2.2 instead of 4.1.2. If I do get one I will probably start running soupkits logcat script to chase the issue further.
Okay this morning before work the device appears to be in a SOD. Hopefully I have time to look at it tonight when I get home. It did go for around four days before this happened.
This one was different from the past my battery was down to 0% even though it was on a charger?
I managed to get it recharged only by plugging it into a computer for a while.
Sent from my KFTT using Tapatalk HD