yashsingh1/xdaforums huggingface dataset:
[XDA-University] sbrownla:
I apologize if this is vague but what could this mean?

I can't figure out what the AccountSetupWizard is referring to. For some background I installed, manually, the TouchWiz Email.apk and secExchange.apk on a stock TouchWiz based ROM, fixed permissions and changed back to R/O for its folder. When I try to open the app is just force closes. Usually when starting the app initially, there is a page that shows email account options, like Exchange or Yahoo, and you choose which one then enter the server settings.

The previous apks that came with the ROM work and I was trying to upgrade them to newer versions, manually. I know it was a dumb idea but why not. I rooted for a reason.

Anyway, maybe there is another system file I was supposed to add as well? I ran a google search for the issue and found nothing at all. So I am perplexed.

Sorry I can't figure out what you mean by pastebin format...
[XDA-University] Stryke_the_Orc:
The stock email applications require framework and services edits (among others) to work on other devices and Android versions. What you're experiencing is a FC due to the process ID bring unregistered with the system. You've got a couple of options, you can either modify the apk or the framework, services and other items as needed or stick with what your device came with.

The specific error you're seeing is a binary problem, not an easy fix. Where did you get the newer apps from?
[XDA-University] gamzekal:
Thank you very much bro .issue is solved :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:

Great explaination
[XDA-University] Stryke_the_Orc:
Glad to be of service [emoji2]
[XDA-University] sbrownla:
Wow you seriously know your stuff!!!!

The newer apks are from the stock Note 4 rom (4.4.4). I'm running a stock - based ROM (with the TouchWiz framework) on my Note 2 (4.4.2).

One thing that's interesting to me is that the version of the email app is exactly the same version that came with the ROM I have installed (TouchWiz Email 4.4.2.0400).

I definitely didn't think it would be as easy as swapping the apks, I really just wanted to see what would happen. I've learned quite a bit just leaning how to unpack the .tar.md5 and you've given me a few things to research.
[XDA-University] Stryke_the_Orc:
Lol thank you, the email apps are recycled through virtually all touchwiz implementations with only minor changes to the app itself, the real crux is the changes made to the rest of the system, so it's no surprise that the version number hasn't changed. I'd suggest tearing apart the framework and services of the note 4 and using something like winmerge (windows) or meld(on Linux) to diff the code and see what's changed.
[XDA-University] sbrownla:
Good GAWD man ... you are incredible!

I'm on it!

//Where's the dang donate button ...

---later--

Oh my gosh ... this application (Meld) is better than &%#^$&@ [CENSORED] ... how could I have missed this?
[XDA-University] Stryke_the_Orc:
Lol it's all about knowing how and where to look. As for donations, I don't accept them. Knowledge is meant to be shared freely.
[XDA-University] oldman20:
Can use logcat app on android? It's will similar results?
[XDA-University] lacoursiere18:
Yes you can. Just have to filter through all the junk. But if you know what your looking for it works well
[XDA-University] andykamezou:
Hello, I'm trying to get logcat to run on reboot.

Previously everything works properly.

I run adb -d logcat > logfile.txt , and then reboot my tablet.

And then when the tablet finished loading OS or when it stuck on bootloop for a while, I'll press Ctrl+C to end the adb logcat.

But suddenly it stopped working. Now, when I reboot the tablet, immediately adb logcat ended and exit.

I've tried kill-server, reboot pc, switch usb port, uninstall adb composite driver. Not sure what else to do.

Any idea how to solve this issue?
[XDA-University] BajoPrimate:
Hi andykamezou.

This is the way I do it:

Logcat from starting

you also could get a logcat from starting via adb doing this:

power off your phone

in the Windows' command prompt type

adb wait-for-device && adb logcat -d > boot.txt

connect your phone with your PC (USB )

power on your phone

For finishing taking the logcat:

(after a couple of minutes) click on the command prompt window and press Ctrl +"C" in your PC's keyboard.

Cheers. Good luck.

Sent from my LG P76020p-EUR-XX unlocked and rooted
[XDA-University] andykamezou:
Hi BajoPrimate,

Thanks for the reply. Actually I already know about that.

It's just, it's weird that previously I can just run logcat before reboot without any issue, but now I can't do it anymore.
[XDA-University] BajoPrimate:
You're welcome, andykamezou.

Cheers. Good luck.

Sent from my LG P76020p-EUR-XX unlocked and rooted
[XDA-University] Stryke_the_Orc:
I believe this is due to changes in both the Android system and the tools.
[XDA-University] friguy3:
Ive been running a lollipop roms (2 different roms, same issue, no custom kernel, nobody else is having this issue) on my LG G2 verizon (VS980) and have been getting issues where my phone wont respond, black screen, power button/knock on, nothing works. Sometimes it will just reboot, other times I hold the power button to hard reset. Someone told me to get a syslog so I did but nobody has been able to look and tell me anything. I looked through it but not a lot makes sense. Was trying to see I guess what makes the phone hang and reboot (before I revert to stock and re-root all over again). Thanks!!
[XDA-University] Basche:
Hi, I have been having problems with bbm app since upgrading to lollipop, here is the pastebin link pastebin.com/dyFUjVA3 I would greatly appreciate the help to see what's wrong. I'm using a custom rom and kernel, which the Rom is close to stock aosp with some few features and optimizations. Also the phone was in native ext4 format, which I converted to f2fs for data and cache only leaving system to default ext4. Initially what happens is that I can use the app fine for some time, then suddenly it crashes and every time I open the app, it will keep crashing. A temporary solution is to clear the app data in the main Android settings and use bbm again. Since clearing app data, I would have to sign in again and the app will sync all my contacts and groups again. Please help me identify the issue :(
[XDA-University] Stryke_the_Orc:
Did you mean to post something?
[XDA-University] Preshak:
Re: [UNIVERSAL][LOGCAT]How to get &amp; read a logcat/ Troubleshoot your own issues!

My navbar buttons keeps on changing to default.

Looking for some help. https://docs.google.com/file/d/0B1YWnsOHjBc1SjZzNmhIOUJ6ZlE/edit?usp=docslist_api
[XDA-University] Vivek_Neel:
Oh...sorry

I was trying it when the device was on..lol:D
[XDA-University] Kalpit Nathwani:
Hello Stryke_the_Orc

Can you plese tell me how to take logcat while my phone is stuck at boot loop. I am trying to port Miui Rom.

Thanks

Kalpit Nathwani
[XDA-University] Stryke_the_Orc:
In terminal cd to the tools folder in your sdk directory and type monitor. Watch the upper left hand box for your device to show up and when you see the system partition appear click on it. You should then be able to grab a logcat. To get the logs, click the logcat button in the bottom left box. However, this will only work if your device will boot far enough for the system to become active, be patient as it can sometimes take more than one bootloop cycle for the system to appear.

Slithering from the nether regions of a twisted mind and tarnished soul

Edit - I've logged into my pc and taken these screenshots for you, I will also attach them to the op for future reference.
[XDA-University] Stryke_the_Orc:
If adb is telling you that its waiting on the device, while you're up and running, then its one of two things. Either usb debugging isn't enabled on your device, or you don't have the proper device drivers on your computer. Both of these are absolute MUST HAVE items to grab a logcat.:good:
[XDA-University] Kalpit Nathwani:
Hello Stryke_the_Orc

Sir Thanks for your quick reply.

Can you please help me and clarify few more things:

1) How much time it will take to complete one bootloop cycle.

2) If device is not detected by system then what is the solution for this problem.

Sorry for my noob question but i am new to porting ROM

Once again thanks for your help.

Thanks

Kalpit Nathwani
[XDA-University] Stryke_the_Orc:
How long it takes to complete a bootloop cycle will depend on how far your device gets before it encounters the error. Typically when you see the boot animation begin to replay is when the cycle has started again.

If your device doesn't turn up a system partition using monitor, then you'll need to reflash a working rom. If you read up a few posts, I have linked a tutorial on how to use the android emulator to test custom roms without risking your device. I would try that method and see what information you can gather from the debugging process:good:
[XDA-University] Sloth:
Added to my FAQ Guides HERE and HERE

Thanks for the write up bro :D
[XDA-University] Stryke_the_Orc:
Excellent! Thanks for including this! :D
[XDA-University] Stryke_the_Orc:
Updated OP with instructions on how to filter your logcat for specific apps and processes:good:
[XDA-University] Slimegod:
Can you check this logcat out for me. Im trying to run through it to understand it. http://pastebin.com/KDXzKKVL
[XDA-University] Stryke_the_Orc:
Are you trying to read it, or figure out the error?

I'd love to help, but I need to know what you're trying to do;)

Slithering from the nether regions of a twisted mind and tarnished soul
[XDA-University] Slimegod:
Actually both. Was just looking at it now. I can somewhat see where the errors are but not to sure. It's a lot of "D" and seems like those are errors based off what u said in the op
[XDA-University] Stryke_the_Orc:
"D" is Dalvik logging, You can see some information here that will help you pin down errors, but they are not the errors themselves. Basically, Dalvik is every process your device is running.

Your also showing a lot of "W" (Warnings) for resources, but if you read further into the line you'll see that it says "Changes with Configuration" so this is nothing to worry about.

Your errors are here

E/BatteryService(26335): wirelessOnlinePath not found
E/dalvikvm(26335): ERROR: couldn't find native method
E/dalvikvm(26335): Requested: Lcom/android/server/location/GpsLocationProvider;.
native_agps_set_ref_location_cellid:(IIIIII)V
E/dalvikvm(26335): Candidate: Lcom/android/server/location/GpsLocationProvider;.
native_agps_set_ref_location_cellid:(IIIII)V
E/JNIHelp (26335): RegisterNatives failed for 'com/android/server/location/GpsLo
cationProvider', aborting
F/libc (26335): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 2633
5 (system_server)

Your wireless path looks to be corrupted, but it gives no other information, for this you could find where your battery service resides and compare your files with stock files to see what's missing or changed. (This could also be a partial line of code where something was removed by the provider or manufacturer, usually for a feature your device doesn't have)

The errors that start E/dalvikvm show that your device is looking for a method that doesn't exist. You do however have a method that is close (noted by the Candidate tag) the only difference being cellid:(IIIII)V & cellid:(IIIIII)V. Your device is looking for a method that has extra characters in the method call out. if you change the last part of that line to match the call out.

The last one is something I'm unfamiliar with, sorry :(
[XDA-University] Slimegod:
Ok I see. Well I'm trying to port between carriers. I don't know if your familiar porting at all. Don't want to elaborate about what I'm trying to do if your not familiar with it. So do you know how to correct those errors? If so can you assist me.
[XDA-University] Stryke_the_Orc:
I'm familiar with porting, that's how I taught myself to understand a logcat;)

In my last post I told you how to fix your errors. Except for the last one that I'm not familiar with. The tricky part will be locating the files. That's pretty much a guessing game unless you know which apks these folder paths are in.

Slithering from the nether regions of a twisted mind and tarnished soul
[XDA-University] Slimegod:
Not to familiar where the files are lol. But the ROM I'm porting is miui. My base isn't a existing rom its a brand new cm 10.1.3 base. So yeah it may be some files that have to be put in. From whether it's existing base ROM or a port I don't know. But I'm getting hung on the boot animation. The whole reason why I'm using a brand new cm base is the ROM I ported previous to this the phone would fc when the other person would hang up. Something minor but still wanted to know what the cause was. Was told it was the cm base I was using and it had to be updated so here I am lol.
[XDA-University] Stryke_the_Orc:
Ok well, first places is look is framework.jar and services.jar those will be the most likely places for that file path. Your other option would be to decompile all the apks and search for the smali file named then edit that.

Slithering from the nether regions of a twisted mind and tarnished soul
[XDA-University] Stryke_the_Orc:
Lcom/android/server/location/GpsLocationProvider;.

native_agps_set_ref_location_cellid: (IIIIII)V

This breaks down as smali/com/location/GPSLocationProvider.smali with the method being native_agps_set_ref_location_cellid: (IIIIII)V and you'd edit (IIIIII) to (IIIII)

I'd be willing to bet it's in framework.jar

Edit - I added spaces so that it didn't turn into an emoticon;)

Slithering from the nether regions of a twisted mind and tarnished soul
[XDA-University] Slimegod:
Ok. Does that seem like the only problem?
[XDA-University] Stryke_the_Orc:
The errors I listed a few posts back were all I saw for errors. Was that the entire logcat?

Slithering from the nether regions of a twisted mind and tarnished soul
[XDA-University] Stryke_the_Orc:
I'll try to take at the three logs you guys have posted this week, sorry I'm not around much, life's busy.
[XDA-University] Basche:
I believe my problem was that it isn't compatible with f2fs, went back to ext4 partition and it's fine now. But can you look at it when you're free so I know for certain. Much appreciated
[XDA-University] beeshyams:
excellent thread

Thanks OP and all others who are contributing in making this a great resource for newbies like me

Regards
[XDA-University] :
Can you help me with my logcat trying to port rom but stuck on bootloop. Here is link. https://www.androidfilehost.com/?fid=95916177934519853
[XDA-University] JasDA:
Perhaps someone could help me. I'm trying to get a logcat during boot on my Samsung S3 Mini I8200. But during boot I got only "waiting for device". If the phone has booted up completely logcat runs fine. But that's to late because on some development I get stuck at the boot animation and I must see whats happening. Any advices?
[XDA-University] Goldie:
You could just boot to recovery and pull dumpstate_sys_error.txt.gz or copy it to sdcard. That contains everything you need for info on a bootloop
[XDA-University] JasDA:
That file should be found under /data/log, right? But /data/log is empty.
[XDA-University] Goldie:
I doubt its empty. What are you looking with?
[XDA-University] JasDA:
If I look via Arome File Manager it's empty. If I try to pull with adb directly the following error is shown:

remote object '/data/log/dumpstate_sys_error.txt.gz' does not exist
[XDA-University] lacoursiere18:
Usually modifying the ram disk to allow adb to start before solves this issue.. There are some guides located on this forum that can help you do this. Its fairly simple, especially with kitchen.. Let me know if you can't find anything and I might be able to help you :good:
[XDA-University] JasDA:
You've point me in the right direction :) Installed cygwin, installed kitchen, unpacked boot.img, enabled adb at start, repacked it, flashed it and now I've got my logcat :)

Thanks ;)
[XDA-University] carlos1984:
lg g2 slow system on 4.4.2

Hi everyone

I have a g2 that screen and lcd were broken on it. So I removed them and hooked up the LG G2 D03 to my tv with slimport adapter. Through using a otg and a wired keyboard I was able to hook up a bluetooth mouse. But the video and mouse movements are really slow, I tried doing a benchmark with antutu and it crashes at the 3d test, I have tried install custom roms, custom kernels, overclocking the cpu and gpu but nothing seems to make the video normal, All I want to do is use the G2 as a way to watch youtube and netflix, I want to put it to good use.

I have attached a logcat, I tried to recreate the issue with antutu but when I run catlog at the same time antutu crashes when I hit test. I have also noticed really hige cpu temps so I attached a screenshot of CPU-Z temps.

Any help would be greatly appeciated.
[XDA-University] Stryke_the_Orc:
My first guess, even without seeing the log, is that you have too many peripherals attached. The OTG cable and wired keyboard are likely making your GPU run constantly, then add in the Bluetooth mouse and thats even more drain. To minimize this, try installing Greenify or Titanium Backup and freezing/hibernating everything that you know you won't need to use (be careful with system apps). This should take some of the other resource hungry players out of the equation.

Edit - Your log has got a lot going on. There are indications that the power source is not being recognized, the external display isn't either at times, and the ThermalEngine errors indicate that the temperature spike is the reason for the crashes, the GPU is working too hard.
[XDA-University] carlos1984:
thanks for replying

I have tried using task manager to kill all background tasks but still same result , also tried to do fresh installs but same . Theonly things plugged in is the slimport and bluetooth mouse.

I think from yuor edit that this is a hardware issue, maybe the board was damaged when the screen was broken..

I have tried the same setup on my wifes nexus 5 and it runs fine, so frustrated, thank you for your help.

I just noticed the screen does flick at intervals, that cool you can read that from the log.
[XDA-University] JaydenH:
URGENT help!

My phone rebooted suddenly - don't know why, I was not using it at that time, and it was the very first time when it did that. I'm using a Samsung Galaxy Mega 6.3 running on Android 4.4.2.

I pulled the logcat from my phone after about 11 hours. Here is the link to the logcat: Dropbox

I also pulled the adb bugreport. Here is the link: Dropbox

Can you tell if the error shows up or anything like that? Any info will be very much appreciated!
[XDA-University] Stryke_the_Orc:
Sorry that I wasn't able to resolve the issue for you. It's possible that the board was damaged, but it's probably more likely that the GPU on your device is just weaker than the GPU on the nexus. Different manufacturers and different QA tolerances allow for quite a lot of variation in quality.
[XDA-University] Stryke_the_Orc:
Can you give me a bit more info about your device? It will help narrow down what I'm looking for. Are you rooted? Running a custom ROM or stock with Xposed? I see 2306 errors in your log so if I can filter them I'd like to.
[XDA-University] as9333:
trying to port

I was trying to port ROM and finally I got a logcat

Here is the link of logcat

https://drive.google.com/file/d/0B9vWPIDVPkgkeC02dEQyOGpjajA/view?usp=sharing

Thanks
[XDA-University] Stryke_the_Orc:
Warning (dlopen failed: library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library

You're missing the Interface Controller
[XDA-University] as9333:
Can u say what is a interface controller

I am trying to port a rom

Libnetcmdiface.so is not found in base Rom and port rom

Anyways thanks for the replay
[XDA-University] tdunham:
Search all of xda or google the Libnetcmdiface.so file.

There are multiple references from a search and you might find a resolution within one of those other threads.
[XDA-University] Stryke_the_Orc:
The interface controller is what allows your hardware to work with the software. It is being called by some process, either in the base or in the ported ROM so I'd keep looking. Use a program like fileseek to search for any reference to that .so in the apk's you have decompiled and see what comes up.
[XDA-University] SovPanda:
Is there a way to log a bootloop without a computer?
[XDA-University] Stryke_the_Orc:
Unfortunately, no.
[XDA-University] tdunham:
Try looking at the dumpstate error logs in data/log.
[XDA-University] as9333:
Pls help me with this logcat

http://pastebin.com/NK1YSwBm

Note: rom is in bootloop stage (showing ROM animation)
[XDA-University] Stryke_the_Orc:
From what I see, you're missing partitions or it's not partitioned correctly. What are you porting and what are you porting to? Also, how did you pull this log? I don't believe I've ever seen a reference to the MBR on an android device...
[XDA-University] as9333:
Thanks for u r answer

I am portion slimkat (moto g) to redmi 1s

I just copied the adb-keys to data to get logcat otherwise it shows device offline

Does changing the updater script make any changes

Thank u
[XDA-University] Stryke_the_Orc:
Changing the updater script shouldn't cause that sort of issue, unless you used the wrong script. If you used the script of the image you were porting you've partitioned your memory in a way that it wasn't meant to be done. Also, a friend of mine showed me this that might be useful to you. Otherwise there just isn't enough information in that log for me to be able to help you. Sorry.
[XDA-University] Rikkardo92:
Hi Stryke_the_Orc, You have any advice for me? Please, I think is a problem of partition, but controlling it seems alright.

The device is a clone s5 mtk. It lights up the screen, run the splash screen or boot logo, but it does not reach the bootanimation. Here only black screen (backlit screen; no backlit keys, nothing else), and I have to wait a bit to ensure that interfaces with adb.

Here the logcat: http://pastebin.com/Qxnqx1Sp

Here the updater-script: http://pastebin.com/9P6Re3PX

Here the build.prop: http://pastebin.com/JvQkGu8B

Here the recovery.log: http://pastebin.com/i0XJTAia

Firmware.info about to MTK Droid Tools: http://pastebin.com/qkcKLz5f

Could you help me out? Other files you need to control? Thank you.
[XDA-University] Rikkardo92:
Hi, thank you for your reply.

Aside from the mistakes committed by me and you noticed, I tried to copy the file KERNEL (contained in bootimg of the rom port) in the bootimg of stock. Then the phone starts. Unfortunately I have problems with drivers lcd / touch (I tried to flash the file lk.bin of "rom port", but unfortunately it is not compatible, and it does not show anything on screen once flashed.). Using a program to display the screen of the device via USB debugging I could see that everything works. :(

PS: I'm not doing a port from rom to rom, but from stock to stock :)
[XDA-University] Stryke_the_Orc:
Kernels from other devices won't work with your device due to then being created for specific hardware, carriers and vendors. You'll need to use your kennel from your stock firmware.
[XDA-University] Rikkardo92:
Hi Stryke, I started back to port, this time in the right way. At first I had a bootloop, but editing the framework.jar I solved and it has started. After all downhill, except for the camera. Sometimes it starts, 1 time out of 50 times, and it works well. While frequently (always) says "Unfortunately, room and imageview has stopped." "Room and imageview" is nothing but the app gallery, which, however, works well, but we know that the camera and the gallery are the same apk. I tried to install the camera lenovo, and tells me that the camera is used from the app primary, to close it before continuing. What to do? I already tried to replace libraries of libraries ... but nothing. I'm going crazy, days and days, and soon I will have rinconsegnare the phone to my client, having to then publish a port not working :(

Thanks

A part of my logcat (orig: 639KB, limit 512KB; so I've cut it): http://pastebin.com/fZv9sY2m