yashsingh1/xdaforums huggingface dataset:
[XDA-University] balla48801:
I have created a lollipop rom from source non deodexed and this rom boots fine. Once i deodex the rom it takes forever to load up the first time(I mean over 30min). Once it boots up first time its fine but the first time something is not right. I just got to the point of looking through logcats. Tell me what you think. I know im getting somekind of errors just have to do some searching to find out what they are exactly. Any help would be appreciated. This is a note4 dev edition verizon

LOGCAT
[XDA-University] Stryke_the_Orc:
Honestly, even the stock system loaded on your device is full of errors, and it's extremely hard to pin down something that "just doesn't feel right". Your logs have 2108 Errors, and that's not including Fatal, warnings or Information tags. If you find something specific try to focus on that, but there are just too many unrelated errors to try to fix them all.
[XDA-University] 伝説 地球人ネッ:
Nice guide bro :D Can you link me some reading materials regarding about reading errors in logcat? Or is it based on the literal meaning of the log output? Thanks for your help and your awesome guide. :D
[XDA-University] Stryke_the_Orc:
Well there's no easy fix for this. You're missing calls to various methods (or missing the methods entirely), the paths may have changed, resources may no longer exists, etc..., the best way to fix this is to take each line of errors, one by one and trace the calls back, correcting any that are wrong.

Other than the tutorials on XDA I'm not sure where you could find materials on reading the logs. Everything in the OP of this thread I learned either by myself or through a tutorial on XDA. A good understanding of how computer code is written helps tremendously, for which I recommend cheking out Code Academy or Khan Academy. There are plenty of other resources out there, Google has a guide on how to read logs but it's not quite as user-friendly as ours are here.
[XDA-University] Vivek_Neel:
Error is because of the absence of libdashplayer.so in /system/lib/

Make sure its there in that dir.
[XDA-University] ZduneX25:
Not a real problem I used to see this libdashplayer.so file in logs since my first time with MIUI. Never caused anything bad.
[XDA-University] Stryke_the_Orc:
library "libdashplayer.so" not found

Put this library file in and see if it fixes them all or just creates more.

Edit- And it's MIUI, that ROM is notorious for throwing errors.
[XDA-University] Nasheich Xfiles:
I've been searching for that lib, but i couldn't find it anywhere...

So, can you help me(again) :D , to make this miui v6 booted to my device ;)

have you look at the others logs ?

please tell me what's wrong with it,

tell me how to understanding the logs...
[XDA-University] uwk007:
I am having problem since 3 months my z2 losing network signal and restarting the only way to restore it

Now its happens once a day

I got logcat just to make sure its not hardware problem before i send it to the warranty

Can you help me reading logcat and find whats causing the problem

I also tried to be stock without root and recovery but problem consists

Here's the link :

https://docs.google.com/file/d/0B_iQGjTEn1LwaHp3X0NQR1VVS0k/edit

Appreciate ur support
[XDA-University] Stryke_the_Orc:
This is the major error:

E/MediaPlayerFactory(819): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(819): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
A/libc(819): Fatal signal 7 (SIGBUS) at 0x00000000 (code=128), thread 819 (mediaserver)

So now let's break it down to see what each item means:
[XDA-University] Stryke_the_Orc:
I am unable to download your log (group policy settings, gotta love them), could you please paste it to www.pastebin.com and repost the link?

Thank you.
[XDA-University] BLK♤Ninja:
Awesome piece of info here thanks. I've was asked to post logi log and had no clue until now thanks
[XDA-University] uwk007:
Link 1

http://pastebin.com/hWHrD5ZA

Link 2

http://pastebin.com/dCwD89Ht

and still a lot but hope you can figure out whats causing the problem from those links
[XDA-University] Stryke_the_Orc:
I see nothing that would indicate signal loss in your logs. You have troubles with your NFC service, WhatsApp and Facebook, but no errors concerning the software in your modem. I would guess your issue is likely signal degradation in your area or, more unlikely but still possible, hardware failure.
[XDA-University] Nasheich Xfiles:
Thank you for your answer...

But like i said, i i couldn't find "libdashplayer.so in any folder, can you tell me where ?
[XDA-University] Stryke_the_Orc:
It may not exist for your device, or it may be included in your stock firmware, I'm not sure. Library files will vary depending on manufacturer and OS. I would dig into a stock tar file or look in various gits, beyond that I can't give you more specific information.
[XDA-University] abo hani:
Hi mate .. i’m making 2Lines for facebook , so i have edited all smali files / androidmainfest / apktool.yml and changed the package and eveything related to it to a new package " fb.katanu " , but i have these problems :

Force Close , i have fixed the force close , by editing a smali file ( i forget to edit the package in it ) - Solved .

A Grey screen when opening the facebook app , after opening it crashes without " App FC " , it just exit from it .

Log : http://www87.zippyshare.com/v/LqqZGiPT/file.html

Thanks in advance :) .
[XDA-University] v7:
Great thread.Learned basics of reading a Logcat from here :)
[XDA-University] Stryke_the_Orc:
Hi,

Please do me the favor of pasting your logs here and paste the link rather than creating a file I have to download. Most times I am mobile or on a computer that I cannot accept/download attachments to. It makes life easier to see the log in a webpage and give feedback.

Thank you.
[XDA-University] vuvkar:
Hi , i have problem with logcat, it says netd 1.0 starting, and the same again and again, please help !!
[XDA-University] Stryke_the_Orc:
HI, I'd actually need to see the logs to be of any help. Please post them to Pastebin and share the link here.
[XDA-University] abo hani:
Here u go mate : http://pastebin.com/8sVKhdD2 .
[XDA-University] lacoursiere18:
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.fb.katanu.app.FacebookApplication" on path: DexPathList[[zip file "/system/framework/com.google.android.maps.jar"

Looks like you need to add this to that jar
[XDA-University] Primokorn:
Hi, I'm working on Google Plus app for my CM custom theme.

I have a FC when opening the app:

07-05 13:52:00.561 E/AndroidRuntime(25060): Process: com.google.android.apps.plus, PID: 25060
07-05 13:52:00.561 E/AndroidRuntime(25060): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.apps.plus/com.google.android.apps.plus.phone.HomeActivity}: java.lang.RuntimeException: A TaskDescription's primary color should be opaque

I see that I have to modify a color (no transparency) but how could I know which one it is?

Note (log attached): The package name of my theme is com.primokorn.firepop
[XDA-University] lacoursiere18:
Your more than likely using a semi transparent color for the app's primary color and you can't do that. Best way to do it, is find where it's called and changed it to a drawable, then define the semi trans color there or in a png.

There is a method in framework.jar that checks for this. If you are familiar with smali you can disable it..
[XDA-University] Primokorn:
Yes I know that's why I was looking for a trick to identify the related color. As you know G+ has hundreds of color codes...

No, I'm not :(
[XDA-University] lacoursiere18:
It's a primary color. So look in styles. There will be a attr called colorPrimary. This is more than likely what is causing the issue.
[XDA-University] Primokorn:
I only have one style which uses android:colorPrimary but the color redirections have a 100% opaque color code (#ff).

I also use transparency for the statusbar and navbar and backgrounds.

I'll compare my last modifications with the previous version. Something has become semi-transparent... Maybe in colors.xml.
[XDA-University] Precision340:
Hi All,

I'm having an issue with a wifi driver for an android radio head unit. Can someone please assist or point me in the right direction to troubleshoot the driver loaded? Below is the logcat file.

D/AudioFlinger(108): setParameters(): io 0, keyvalue av_gps_ontop=false, calling pid 468
01-01 06:08:35.650
D/WifiService(468): setWifiEnabled: true pid=2860, uid=1000
01-01 06:08:35.660
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:35.660
E/RkWifiCtrl(468): rk_wifi_load_driver:(insmod)
01-01 06:08:35.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:36.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:37.450
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:37.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:38.780
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:38.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:39.780
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:39.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:40.450
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:40.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:41.780
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:41.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:42.780
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:42.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:43.460
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:43.820
D/dalvikvm(1464): GC_CONCURRENT freed 749K, 22% free 4243K/5388K, paused 3ms+1ms, total 29ms
01-01 06:08:44.080 W/EventLoggerService(1464): Unable to send logs Error code: 262160 | The connection was not attempted due to lack of network connectivity.
01-01 06:08:44.280
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:44.780
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:44.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:45.780
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:45.820
E/RkWifiCtrl(468): Wifi driver is not ready.
01-01 06:08:46.460
E/RkWifiCtrl(468): rk_wifi_load_driver:(rmmod)
01-01 06:08:46.820
E/WifiStateMachine(468): Failed to load driver
01-01 06:08:47.910
E/WifiStateMachine(468): wifi sta open fail, disable
01-01 06:08:47.910
D/WifiService(468): setWifiEnabled: false pid=468, uid=1000
01-01 06:08:47.920
W/Settings(734): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
01-01 06:08:47.920
V/mtc-gps (468): --mtc Received: '$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30

Thanks in advance for any help.

P340
[XDA-University] Stryke_the_Orc:
It looks like your device is in Airplane mode, but the settings have been moved so you can't change it. Can't say as I've ever seen that before...:confused:

E/AndroidRuntime( 1268): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.util.ArrayList.add(java.lang.Object)' on a null object reference

You're trying to instantiate a non-existing member of the array. See the code following the error in red to determine which files need to be changed. The first method you have, it likely just needs to have the resources file assign values to the new icons, the other methods where the error occurs probably need the same. As it looks now, your pointing to a file that is there physically, but not logically.
[XDA-University] tdunham:
What are trying to do?

You're not trying to edit an odexed system are you?

I see a dexopt error and if that is the case you need to deodex the entire build and work from that once you have it booting without issues.

And please zip entire logs and post as file attachments please, not just excerpts.

I think Stryke_the_Orc has offered other online choices for posting logs as well.
[XDA-University] osas514:
I'm trying to port and d rom is already deodexed
[XDA-University] tdunham:
I'm not nearly as good at reading these as he is but looks like framework errors to me since that tends to affect multiple services not loading. Sorry, I couldn't be more specific.
[XDA-University] osas514:
Thanks for d response but any idea where to start looking?
[XDA-University] tdunham:
The only advice I can offer for porting roms is to search for as many of the porting threads as you can for different techniques and what files need to be brought over for your hardware (from builds that are for your phone) to make it compatible.

The best and easiest port is from a phone with as similar hardware/cpu type as possible and also for the same type carrier (gsm/cdma). This is strictly from a touchwiz standpoint I understand that miui can be really tricky but I am a touchwiz developer so can offer no hints either way. I've only personally ported over a single rom and it was a lot of trial and error. I've helped troubleshoot several others.
[XDA-University] osas514:
Thanks for d tip but I'm porting a Touchwiz Kitkat rom to my device (galaxy grand duos ) from core 2 duos both broadcom processor and gpu
[XDA-University] bilgerryan:
It also helps if they are the same resolution (not absolutely necessary, but it makes things easier when doing a whole ROM).
[XDA-University] osas514:
Same resolution too bro
[XDA-University] Stryke_the_Orc:
Your error lies here:

F/SystemServer( 3992): BOOT FAILURE starting Input MethodManager Service
F/SystemServer( 3992): java.lang.NullPointerException

This says that your Input MethodManager Service is being fed a null value. Whatever it's trying to access doesn't logically exist.

Under this hide tag you'll see the actual error and my explanation of what they mean.

[COLOR="Red"]Scroll right to see any comments.[/COLOR]
I/SystemServer(3992): Input Method Service [COLOR="Red"]< The system tries to start this service[/COLOR]
F/SystemServer( 3992): BOOT FAILURE starting Input MethodManager Service [COLOR="red"]Pretty obvious...[/COLOR]
F/SystemServer( 3992): java.lang.NullPointerException [COLOR="red"]This is why...[/COLOR]
F/SystemServer( 3992): at com.android.server.InputMethodManagerService.<init >(InputMethodManagerService.java:1211) [COLOR="red"]Start looking here.
In the folder structure listed you would follow /com/android/server/ then find the file named InputMethodManagerService and finally the method causing the error is <init>[/COLOR]
F/SystemServer( 3992): at com.android.server.ServerThread.initAndLoop(System Server.java:738) [COLOR="red"]Same deal here,
the structure is as follows: /folder/folder/folder/file/method[/COLOR]
F/SystemServer( 3992): at com.android.server.SystemServer.main(SystemServer. java:2224)
F/SystemServer( 3992): at java.lang.reflect.Method.invokeNative(Native Method)
F/SystemServer( 3992): at java.lang.reflect.Method.invoke(Method.java:515)
F/SystemServer( 3992): at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:1283)
F/SystemServer( 3992): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:1099)
F/SystemServer( 3992): at dalvik.system.NativeStart.main(Native Method)

[COLOR="Red"]Scroll right to see any comments.[/COLOR]
W/SystemServer(3992): ***********************************************
E/AndroidRuntime(3992): Error reporting WTF
E/AndroidRuntime(3992): java.lang.NullPointerException
E/AndroidRuntime(3992): at com.android.internal.os.RuntimeInit.wtf(RuntimeIni t.java:395)
E/AndroidRuntime(3992): at android.util.Log$1.onTerribleFailure(Log.java:106)
E/AndroidRuntime(3992): at android.util.Log.wtf(Log.java:418)
E/AndroidRuntime(3992): at android.util.Log.wtf(Log.java:411)
E/AndroidRuntime(3992): at com.android.server.ServerThread.reportWtf(SystemSe rver.java:210)
E/AndroidRuntime(3992): at com.android.server.ServerThread.initAndLoop(System Server.java:741) [COLOR="red"]< Looks familiar yes?[/COLOR]
E/AndroidRuntime(3992): at com.android.server.SystemServer.main(SystemServer. java:2224)
E/AndroidRuntime(3992): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(3992): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime(3992): at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:1283)
E/AndroidRuntime(3992): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:1099)
E/AndroidRuntime(3992): at dalvik.system.NativeStart.main(Native Method)

If you fix the methods that throw the error in the first block, the errors in the second should resolve themselves. Good Luck :good:
[XDA-University] Yashodhan Wagle:
Can someone just tell me the commands to get a logcat via adb on my laptop?? My device gets stuck on a bootloop when I install the xposed framework
[XDA-University] Primokorn:
adb -d logcat > mylogfile.txt

You may also try adb logcat -d -b events | grep "boot" or adb logcat -d | grep preload
[XDA-University] remuntada78:
hi , i added a new method into a file.smali

.method refresh(Landroid/content/Context;)V
.locals 0

invoke-direct {p0, p1}, blablabla/blablabla;-><init>(Landroid/content/Context;)V

return-void
.end method

and i got the following error

void blablabla/blablabla.refresh(android.content.Context) failed to verify: Expected initialization on uninitialized reference Reference: blablabla/blablabla

which is the problem?

how can i solve it?

thanks in advance
[XDA-University] Stryke_the_Orc:
It failed to verify. My guess is (and I haven't proven this one way or another) that the "blablabla/blablabla" is being seen as invalid by the system. Not really sure what you're trying to achieve here, or where you've tried putting this, but without more information that's the best I can do...
[XDA-University] tdunham:
LOL @ the blah blah blah and I know which smali you're looking at because we are talking about it.

Try placing the new method up in the # direct methods instead of in the # virtual methods section because I see the context you are trying to invoke-direct is originally called from that area

.method public constructor <init>(Landroid/content/Context;)V

And not sure if it even matters to the system but also try renaming the new method

.method [B]public[/B] refresh(Landroid/content/Context;)V
[XDA-University] remuntada78:
ok, I'm trying to make work a observer file, the main file is QSTileView.smali where i have a mod into the method

.method public constructor <init>(Landroid/content/Context;)V

so i added a new method in QSTileView.smali

.method refresh(Landroid/content/Context;)V
.locals 0

invoke-direct {p0, p1}, Lcom/android/systemui/qs/QSTileView;-><init>(Landroid/content/Context;)V

return-void
.end method

to try to call that method in the observer file and got the error

I/dex2oat ( 1151): Verification error in void com.android.systemui.qs.QSTileView.refreshCirclesColor(android.content.Context)

I/dex2oat ( 1151): void com.android.systemui.qs.QSTileView.refreshCirclesColor(android.content.Context) failed to verify: Expected initialization on uninitialized reference Reference: com.android.systemui.qs.QSTileView

E/dex2oat ( 1151): Verification failed on class com.android.systemui.qs.QSTileView in /system/priv-app/SystemUI/SystemUI.apk because: Verifier rejected class com.android.systemui.qs.QSTileView due to bad method void com.android.systemui.qs.QSTileView.refreshCirclesColor(android.content.Context)

E/dex2oat ( 1151): Rejecting class com.android.systemui.qs.SignalTileView that attempts to sub-class erroneous class com.android.systemui.qs.QSTileView in /system/priv-app/SystemUI/SystemUI.apk
[XDA-University] Stryke_the_Orc:
Ok, this makes much more sense lol.

Your method is failing because it cannot be verified by the SystemUI. Did you also write this method "refreshCirclesColor"? If this was existing then you have some discrepancy between your call and the systems call for both methods causing the system to reject any changes and not read the file. If you've written this method as well then you need to find a way to integrate it into your SystemUI via the appropriate QSTileView calls. The void appears to be what's causing it to fail.
[XDA-University] remuntada78:
yes the method is

.method refreshCirclesColor(Landroid/content/Context;)V
.locals 0

invoke-direct {p0, p1}, Lcom/android/systemui/qs/QSTileView;-><init>(Landroid/content/Context;)V

return-void
.end method

and in the file observer i have

.method public onChange(ZLandroid/content/Context;)V
.locals 1

.prologue
.line 291[COLOR="Red"]
iget-object v0, p0, Lcom/android/systemui/qs/QSTileView$SettingsObserver;->this$0:Lcom/android/systemui/qs/QSTileView;

invoke-virtual {v0, p2}, Lcom/android/systemui/qs/QSTileView;->refreshCirclesColor(Landroid/content/Context;)V[/COLOR]

iget-object v0, p0, Lcom/android/systemui/qs/QSTileView$SettingsObserver;->this$0:Lcom/android/systemui/qs/QSTileView;

invoke-virtual {v0}, Lcom/android/systemui/qs/QSTileView;->refreshTilesText()V

.line 292
return-void
.end method
[XDA-University] Stryke_the_Orc:
Just a shot in the dark here (and maybe someone with more current experience in the Android system can help) but it looks like the return-void in your methods is what's causing them to fail. Due to life and my own personal scheduling issues I haven't gone into smali code since Kit-Kat first came out. Have you tried [MENTION=1042140]tdunham[/MENTION]'s suggestions above?
[XDA-University] osas514:
Back again..... any help on this

http://pastebin.com/AfeD6A5f

Thanks alot in advance
[XDA-University] Stryke_the_Orc:
The resource errors or the missing files that's causing you're power supply to fail? What problem(s) are you experiencing?
[XDA-University] osas514:
Bootloop problem bro (still on d porting stuff) and d two libs missing does not exist on both base and port rom
[XDA-University] Stryke_the_Orc:
Well from what you've posted, there's the missing resources, which if they exist in the ported ROM should be fairly simple. Make sure that the resources are pointed to in your public.XML file. The lib files, if you can't find them I can't help you with... Have you tried commenting out the lines asking for those libs?
[XDA-University] osas514:
U

Thanks again for d reply..
[XDA-University] justinsalvacion:
Hi, Need help fixing this issue

I was trying to fix this issue :

pastebin . com/rscyhXn8

Home Launcher is Force Closing.

Thanks in advance!
[XDA-University] tapo85:
Can anyone explain this logcat for me. Thanks very much. When my xepria z2 battery below 10%, i charge it and it get freeze. I don't know why. This is log. https://mega.nzMODERATOR EDIT - Removed to protect privacy
[XDA-University] judas1977:
I tried to compile SlimSaber LP using our phone sources. Everything seems good, BUT there is no telephony...

I mean - Phone tells there is no SIM CARD. IMEI is unknow as well...

It strange, because no issue on clean SlimLP (it uses own ril and ril-caf repos, and slimsaber uses ril from CM, but changing to that repos on slimsaber also didn't help).

I heard some devs of my phone (LG L90) here had similar issue on other (slim based?) ROMs...

Maybe someone will find something in logcat (it's radio logcat actually). Thanks in advance.

HERE IS THE LOG:

http://hastebin.com/uxivecuxuf.vhdl
[XDA-University] Stryke_the_Orc:
I'm unable to download your log, I've tried several computers in several locations and only get half of the file before it fails. Please use www.pastebin.com thank you.

Sent from the nether regions of a twisted mind and tarnished soul
[XDA-University] Stryke_the_Orc:
I'm sorry, your link doesn't resolve.

Sent from the nether regions of a twisted mind and tarnished soul
[XDA-University] tapo85:
Thanks for your rep. Sorry, i can't copy log to pastebin, this is link of mediafire, please help me. I want to know what happen with my phone. Thanks very much.

http://www.mediafire.com/downloadMODERATOR EDIT - Removed to protect privacy