NamelessRom [Q&A][Troubleshooting]

Search This thread
By:
Advanced…
B

bzn7

Member
Feb 27, 2013
12
1
İstanbul
axljohn said:
lol optimus white xD dude it's still optimus black, just diff color :) had the same issue with the past, just clean out the accumulated dirt on the port. best to have it cleaned by a technician or something
Click to expand...
Click to collapse

LOLG Optimus White, special version for me xD

What kind of dirt? Just effects latest nameless roms. There is no problem with cm10 and nameless 20140624 or older. I'm using cm10 now.
 
Evisceration

Evisceration

Inactive Recognized Developer
Sep 6, 2012
1,768
4,137
28
Wolfsberg
review.lineageos.org
bzn7 said:
LOLG Optimus White, special version for me xD

What kind of dirt? Just effects latest nameless roms. There is no problem with cm10 and nameless 20140624 or older. I'm using cm10 now.
Click to expand...
Click to collapse
the log you showed contains information about crashes, when there are pending notifications.

i was still unable to reproduce it but ill dig around until i find a possible reason
 
  • Like
Reactions: bzn7
B

bzn7

Member
Feb 27, 2013
12
1
İstanbul
Evisceration said:
the log you showed contains information about crashes, when there are pending notifications.

i was still unable to reproduce it but ill dig around until i find a possible reason
Click to expand...
Click to collapse

Finally i solved problem with complately fresh install.

>Flashed official 2.3.4 firmware with SFT
>rooted via framaroot-1.9.1.apk
>installed twrp 2.6.1.0
>installed [nameless 20140705 + Gapps minimal (Bank's) + AOSP browser sync] with full wipe

I don't know what caused this. Anyway, its gone. Working fine now. Thanks for interest.
 
Q

quberek

New member
Oct 28, 2013
4
1
Sosnowiec
Baseband

Hi there.
I have a lame question that the baseband will be the best for this rom?:confused:
Currently I have v20, v30 again with the release there are some problems.
Sorry for my english.
You make an excellent rom, thanks for your work.:highfive:
Greetings.:eek:
 
S

smy00oo

Member
Jun 15, 2013
37
9
quberek said:
Hi there.
I have a lame question that the baseband will be the best for this rom?:confused:
Currently I have v20, v30 again with the release there are some problems.
Sorry for my english.
You make an excellent rom, thanks for your work.:highfive:
Greetings.:eek:
Click to expand...
Click to collapse
Evisceration said that the best baseband is v20o
 
Q

quberek

New member
Oct 28, 2013
4
1
Sosnowiec
thanks for the clear up doubts.
whether someone else may have problems with ringing? Because the phone application to crash frequently and, for example, I call once and then I have to reboot the phone because another can no longer do.
 
Evisceration

Evisceration

Inactive Recognized Developer
Sep 6, 2012
1,768
4,137
28
Wolfsberg
review.lineageos.org
smy00oo said:
Evisceration said that the best baseband is v20o
Click to expand...
Click to collapse

currently im on v20a and i guess ill stay with it

quberek said:
thanks for the clear up doubts.
whether someone else may have problems with ringing? Because the phone application to crash frequently and, for example, I call once and then I have to reboot the phone because another can no longer do.
Click to expand...
Click to collapse

please provide logs if you can, else its hard for me to see whats wrong :)
 
S

seby24gl

Member
Nov 30, 2011
13
5
Bucharest
nameless-4.4.4-20140706-p970-WEEKLY reboots my phone . I installed clean, wiped everything and still a got 3 random reboots ( 2 directly in recovery mod and 1 in boot loader mode), while I'm setup the phone.
 
R

raduku009

Senior Member
Feb 7, 2012
179
20
how do you get a log? i want to log the twitch app, the streaming videos are lagging and sound doesnt work properly
 
L

lleuname

Senior Member
Jul 17, 2014
103
21
My soft keys (multi task, home, back and search) doesn't work.
I read a lot but anything was able to do them work. They only work with the cellphone plugged in the charger.

I found some solutions, like:
Enable the soft keys on the screen on settings. (But, even on the smallest size, i didn't like the space it toked from my screen)

Nav layer(play store, free)
It adds an invisible layer on the side of the screen(left, right or bottom) that, depending on how you slide it, it does an action. Very simple and useful app.

Those with the same problem, give it a try. ;)

Sent from my LG-P970
 
Evisceration

Evisceration

Inactive Recognized Developer
Sep 6, 2012
1,768
4,137
28
Wolfsberg
review.lineageos.org
lleuname said:
My soft keys (multi task, home, back and search) doesn't work.
I read a lot but anything was able to do them work. They only work with the cellphone plugged in the charger.

I found some solutions, like:
Enable the soft keys on the screen on settings. (But, even on the smallest size, i didn't like the space it toked from my screen)

Nav layer(play store, free)
It adds an invisible layer on the side of the screen(left, right or bottom) that, depending on how you slide it, it does an action. Very simple and useful app.

Those with the same problem, give it a try. ;)

Sent from my LG-P970
Click to expand...
Click to collapse

and for those who dont want to use third party to achieve the same:

1) Force enable navigation bar in settings
2) Settings -> Interface -> Expanded Desktop -> choose "Status bar visible"
3) Enable expanded desktop via power menu or quicktiles

now the navigation bar will automatically hide, until you slide up to show it (it will even tell you what to do when you are in expanded desktop mode)
 
  • Like
Reactions: pkb_always4u and lleuname
T

t3l3m4k0

Member
Jun 19, 2013
48
15
I have some trouble with light notifications. They did not work. Maybe i'm missing settings.

To enable i do:

config > screen & lights > notification light > enabled & default normal + normal
i tried several configs, no one works.

thanks for any idea
 
B

bzn7

Member
Feb 27, 2013
12
1
İstanbul
[20140719] I have a new issue. When using firefox for visitting m.chip.com.tr phone resets.

And have a question about wifi driver. When will be ready new wifi drivers? I really need wifi tethering.
 

Attachments

  • 2014-07-21-12-36-32.txt
    36.4 KB · Views: 5
L

lleuname

Senior Member
Jul 17, 2014
103
21
ART

If we activate running ART on settings, does it cause problems with this rom? ('cause of the cyanogem mod's warning).
Maybe it's a silly question, but is there a chart or something to explain the meaning and what each settings in Settings/Developer do?
I'm after this on google, but is too much things... i was just wondreing.
 
B

bzn7

Member
Feb 27, 2013
12
1
İstanbul
lleuname said:
If we activate running ART on settings, does it cause problems with this rom? ('cause of the cyanogem mod's warning).
Maybe it's a silly question, but is there a chart or something to explain the meaning and what each settings in Settings/Developer do?
I'm after this on google, but is too much things... i was just wondreing.
Click to expand...
Click to collapse

You can use ART but Dalvik is better on this device with this rom. Performance is really poor with ART and system isn't stable enough to use. Apps are crashing etc.

If you want to try, be patient. First boot after choosing ART takes nearly 15 minutes. Don't pull battery :)
 
L

lleuname

Senior Member
Jul 17, 2014
103
21
bzn7 said:
You can use ART but Dalvik is better on this device with this rom. Performance is really poor with ART and system isn't stable enough to use. Apps are crashing etc.

If you want to try, be patient. First boot after choosing ART takes nearly 15 minutes. Don't pull battery :)
Click to expand...
Click to collapse

I was reading a lot of things until now. Some apps that i use don't have full support yet. And, as magical and incredible it seems to be, i think it's better keep it off... Thnks
 
Evisceration

Evisceration

Inactive Recognized Developer
Sep 6, 2012
1,768
4,137
28
Wolfsberg
review.lineageos.org
lleuname said:
I was reading a lot of things until now. Some apps that i use don't have full support yet. And, as magical and incredible it seems to be, i think it's better keep it off... Thnks
Click to expand...
Click to collapse
The version of art which is included in Kitkat is in no way compareable with the version we will see in L.

ART is only included for developers to test if their apps are compatible with the ART runtime as it behaves and works differently than dalvik in many situations.

thus you should not use art as daily driver.

if you do, do it at your own risk and dont report problems caused by it as we cannot do anything against it nor we support it :)
 
  • Like
Reactions: lleuname
You must log in or register to reply here.

Similar threads

Evisceration
[ROM][4.4.4][Official] NamelessROM [NIGHTLIES]
Replies
1K
Views
282K
waheem
waheem
K
  • Locked
[ROM][DISCONTINUED] Nova 2.2 v8 (w/ quasar, oc support & more)
Replies
3K
Views
475K
reinbeau
reinbeau
Evisceration
[ROM][4.3.1] Velox Rom - Codename Nameless | 1.0.6.2
Replies
1K
Views
217K
R
Rexkh
Ilko
[STARTER] Upgrade Kit 3.7.5 | Apps 2 | Root, Flash, Unbrick, Tuts...
Replies
657
Views
533K
J
jimzstone
N00BY0815
[Q] How to root P970 Gingerbread V20N
Replies
500
Views
139K
N00BY0815
N00BY0815

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 9
    Evisceration
    Evisceration
    lleuname said:
    I saw an excelent gain in battery on last WEEKLY rom. Turning only 2G. But when i turn sync and 3G... Although, really awesome work! Unfortunately there are some people that just want to bother... We understand you, man. Thank you for the brilliant work one more time.

    Sent from my LG-P970
    Click to expand...
    Click to collapse

    ptxpaulo said:
    One BIG thanks from here too...
    Click to expand...
    Click to collapse

    dont thank me, Stefan Demharter discovered the faulty patch which caused that drain :)
    he is also working on the ALS and backkeys, awesome work so far.

    sync is always a bit tricky on legacy, ill always look around and try to improve battery, but i am limited, i cant do everything.
    View
    4
    Evisceration
    Evisceration
    progier said:
    I`ve just tested 20141007 nightly and it also has buggy HW composer.
    Click to expand...
    Click to collapse

    could you try tomorrows build please?
    i just did some changes to the p970 HWC
    View
    3
    Evisceration
    Evisceration
    mr_rious said:
    nice idea:good:
    well, then I start...
    any news to fix the gps in the coming days?
    Click to expand...
    Click to collapse

    working on it! GPS and new WIFI Drivers are the only big things left :)

    rellagher said:
    Is there a way to disable horizontal lockscreen?

    EDIT: Found it. You have to enable and then disable again lockscreen rotation for changes to really apply.
    From a clean install the lockscreen rotates.
    Click to expand...
    Click to collapse

    yes, its enabled by default but settings doesnt reflect that, sorry!

    bzn7 said:
    Hi again,

    >installed [20140701 + Gapps minimal (Bank's) + AOSP Browser Sync] with full wipe
    >installed catlog from play store
    >started recording
    >plugged charger in and phone freezed
    >ejected charger
    >pulled battery

    The logs:

    Code: 
    07-02 00:46:57.003 D/AndroidRuntime( 5439): 
07-02 00:46:57.003 D/AndroidRuntime( 5439): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
07-02 00:46:57.019 D/AndroidRuntime( 5439): CheckJNI is OFF
07-02 00:46:57.073 D/dalvikvm( 5439): Trying to load lib libjavacore.so 0x0
07-02 00:46:57.089 D/dalvikvm( 5439): Added shared lib libjavacore.so 0x0
07-02 00:46:57.089 D/dalvikvm( 5439): Trying to load lib libnativehelper.so 0x0
07-02 00:46:57.097 D/dalvikvm( 5439): Added shared lib libnativehelper.so 0x0
07-02 00:46:57.097 D/dalvikvm( 5439): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
07-02 00:46:57.183 E/cutils-trace( 5439): Error opening trace file: No such file or directory (2)
07-02 00:46:57.472 E/memtrack( 5439): Couldn't load memtrack module (No such file or directory)
07-02 00:46:57.472 E/android.os.Debug( 5439): failed to load memtrack module: -2
07-02 00:46:57.644 D/AndroidRuntime( 5439): Calling main entry com.android.commands.am.Am
07-02 00:46:57.644 D/dalvikvm( 5439): Note: class Landroid/app/ActivityManagerNative; has 180 unimplemented (abstract) methods
07-02 00:46:57.691 D/AndroidRuntime( 5439): Shutting down VM
07-02 00:46:57.925 I/Choreographer( 5223): Skipped 40 frames!  The application may be doing too much work on its main thread.
07-02 00:46:59.363 D/AndroidRuntime( 5456): 
07-02 00:46:59.363 D/AndroidRuntime( 5456): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
07-02 00:46:59.363 D/AndroidRuntime( 5456): CheckJNI is OFF
07-02 00:46:59.456 D/dalvikvm( 5456): Trying to load lib libjavacore.so 0x0
07-02 00:46:59.480 D/dalvikvm( 5456): Added shared lib libjavacore.so 0x0
07-02 00:46:59.488 D/dalvikvm( 5456): Trying to load lib libnativehelper.so 0x0
07-02 00:46:59.495 D/dalvikvm( 5456): Added shared lib libnativehelper.so 0x0
07-02 00:46:59.495 D/dalvikvm( 5456): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
07-02 00:46:59.628 E/cutils-trace( 5456): Error opening trace file: No such file or directory (2)
07-02 00:47:00.066 E/memtrack( 5456): Couldn't load memtrack module (No such file or directory)
07-02 00:47:00.073 E/android.os.Debug( 5456): failed to load memtrack module: -2
07-02 00:47:00.323 D/AndroidRuntime( 5456): Calling main entry com.android.commands.am.Am
07-02 00:47:00.339 D/dalvikvm( 5456): Note: class Landroid/app/ActivityManagerNative; has 180 unimplemented (abstract) methods
07-02 00:47:00.534 D/lights  ( 1828): liblights: set_light_buttons: 0
07-02 00:47:00.542 I/Choreographer( 5223): Skipped 77 frames!  The application may be doing too much work on its main thread.
07-02 00:47:00.573 D/AndroidRuntime( 5463): 
07-02 00:47:00.573 D/AndroidRuntime( 5463): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
07-02 00:47:00.581 D/AndroidRuntime( 5463): CheckJNI is OFF
07-02 00:47:00.636 D/AndroidRuntime( 5456): Shutting down VM
07-02 00:47:00.644 D/dalvikvm( 5463): Trying to load lib libjavacore.so 0x0
07-02 00:47:00.659 D/dalvikvm( 5463): Added shared lib libjavacore.so 0x0
07-02 00:47:00.675 D/dalvikvm( 5463): Trying to load lib libnativehelper.so 0x0
07-02 00:47:00.675 D/dalvikvm( 5463): Added shared lib libnativehelper.so 0x0
07-02 00:47:00.675 D/dalvikvm( 5463): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
07-02 00:47:00.800 E/cutils-trace( 5463): Error opening trace file: No such file or directory (2)
07-02 00:47:00.925 D/lights  ( 1828): liblights: set_light_buttons: 255
07-02 00:47:00.941 W/ProcessCpuTracker( 1828): Skipping unknown process pid 5456
07-02 00:47:01.066 I/Choreographer( 5223): Skipped 33 frames!  The application may be doing too much work on its main thread.
07-02 00:47:01.167 E/memtrack( 5463): Couldn't load memtrack module (No such file or directory)
07-02 00:47:01.175 E/android.os.Debug( 5463): failed to load memtrack module: -2
07-02 00:47:01.558 D/AndroidRuntime( 5463): Calling main entry com.android.commands.am.Am
07-02 00:47:01.566 D/dalvikvm( 5463): Note: class Landroid/app/ActivityManagerNative; has 180 unimplemented (abstract) methods
07-02 00:47:02.050 D/AndroidRuntime( 5463): Shutting down VM
07-02 00:47:02.370 D/AndroidRuntime( 5491): 
07-02 00:47:02.370 D/AndroidRuntime( 5491): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
07-02 00:47:02.378 D/AndroidRuntime( 5491): CheckJNI is OFF
07-02 00:47:02.441 D/dalvikvm( 5491): Trying to load lib libjavacore.so 0x0
07-02 00:47:02.441 D/dalvikvm( 5491): Added shared lib libjavacore.so 0x0
07-02 00:47:02.456 D/dalvikvm( 5491): Trying to load lib libnativehelper.so 0x0
07-02 00:47:02.464 D/dalvikvm( 5491): Added shared lib libnativehelper.so 0x0
07-02 00:47:02.464 D/dalvikvm( 5491): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
07-02 00:47:02.558 E/cutils-trace( 5491): Error opening trace file: No such file or directory (2)
07-02 00:47:02.792 I/Choreographer( 5223): Skipped 116 frames!  The application may be doing too much work on its main thread.
07-02 00:47:02.855 E/memtrack( 5491): Couldn't load memtrack module (No such file or directory)
07-02 00:47:02.855 E/android.os.Debug( 5491): failed to load memtrack module: -2
07-02 00:47:03.034 D/AndroidRuntime( 5491): Calling main entry com.android.commands.am.Am
07-02 00:47:03.042 D/dalvikvm( 5491): Note: class Landroid/app/ActivityManagerNative; has 180 unimplemented (abstract) methods
07-02 00:47:03.152 D/AndroidRuntime( 5491): Shutting down VM
07-02 00:47:03.230 W/InputMethodManagerService( 1828): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41e7d488 attribute=null, token = android.os.BinderProxy@41aeaa20
07-02 00:47:03.245 V/PhoneStatusBar( 2179): setLightsOn(true)
07-02 00:47:03.769 I/Timeline( 5223): Timeline: Activity_idle id: android.os.BinderProxy@418df050 time:714463
07-02 00:47:06.542 D/AlarmManagerService( 1828): Kernel timezone updated to -180 minutes west of GMT
07-02 00:47:06.573 D/MobileDataStateTracker( 1828): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
07-02 00:47:06.573 D/MobileDataStateTracker( 1828): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
07-02 00:47:06.589 D/NotificationMgr( 2343): updateNetworkSelection()...state = 0 new network 
07-02 00:47:06.597 D/PhoneApp( 2343): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED
07-02 00:47:06.597 D/PhoneApp( 2343): - state: CONNECTED
07-02 00:47:06.597 D/PhoneApp( 2343): - reason: null
07-02 00:47:06.605 D/NotificationMgr( 2343): hideDataDisconnectedRoaming()...
07-02 00:47:06.605 E/ConnectivityService( 1828): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_use_userconfig: open failed: ENOENT (No such file or directory)
07-02 00:47:06.605 E/ConnectivityService( 1828): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_delack_seg: open failed: ENOENT (No such file or directory)
07-02 00:47:07.855 D/AlarmManagerService( 1828): Kernel timezone updated to -180 minutes west of GMT
07-02 00:47:07.886 D/MobileDataStateTracker( 1828): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
07-02 00:47:07.894 D/MobileDataStateTracker( 1828): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
07-02 00:47:07.909 D/NotificationMgr( 2343): updateNetworkSelection()...state = 0 new network 
07-02 00:47:07.909 D/PhoneApp( 2343): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED
07-02 00:47:07.909 D/PhoneApp( 2343): - state: CONNECTED
07-02 00:47:07.917 D/PhoneApp( 2343): - reason: null
07-02 00:47:07.917 E/ConnectivityService( 1828): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_use_userconfig: open failed: ENOENT (No such file or directory)
07-02 00:47:07.917 E/ConnectivityService( 1828): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_delack_seg: open failed: ENOENT (No such file or directory)
07-02 00:47:07.925 D/NotificationMgr( 2343): hideDataDisconnectedRoaming()...
07-02 00:47:10.792 D/lights  ( 1828): liblights: set_light_buttons: 0
07-02 00:47:30.855 D/lights  ( 1828): liblights: set_light_buttons: 255
07-02 00:47:30.917 I/VisualizerView( 2179): session=0
07-02 00:47:36.355 D/lights  ( 1828): liblights: set_light_buttons: 0
07-02 00:47:36.394 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 5006.8ms since event, 5000.5ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.409 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.519 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 5130.8ms since event, 5124.5ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.527 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.620 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 5236.9ms since event, 5230.7ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.636 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.667 I/Process ( 1828): Sending signal. PID: 2179 SIG: 3
07-02 00:47:36.675 I/dalvikvm( 2179): threadid=3: reacting to signal 3
07-02 00:47:36.761 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 5374.4ms since event, 5368.1ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.769 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:36.886 I/Process ( 1828): Sending signal. PID: 1828 SIG: 3
07-02 00:47:36.886 I/dalvikvm( 1828): threadid=3: reacting to signal 3
07-02 00:47:38.066 E/Sensors ( 1828): poll() failed (Interrupted system call)
07-02 00:47:38.198 I/Process ( 1828): Sending signal. PID: 2359 SIG: 3
07-02 00:47:38.198 I/dalvikvm( 2359): threadid=3: reacting to signal 3
07-02 00:47:38.214 I/dalvikvm( 1828): Wrote stack traces to '/data/anr/traces.txt'
07-02 00:47:38.269 I/Process ( 1828): Sending signal. PID: 2347 SIG: 3
07-02 00:47:38.269 I/dalvikvm( 2347): threadid=3: reacting to signal 3
07-02 00:47:38.355 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 6969.0ms since event, 6962.7ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.370 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.464 I/Process ( 1828): Sending signal. PID: 2343 SIG: 3
07-02 00:47:38.464 I/dalvikvm( 2343): threadid=3: reacting to signal 3
07-02 00:47:38.495 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 7109.9ms since event, 7103.7ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.605 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.714 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 7329.0ms since event, 7322.8ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.745 I/dalvikvm( 2179): Wrote stack traces to '/data/anr/traces.txt'
07-02 00:47:38.745 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.886 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 7502.6ms since event, 7496.4ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.909 I/dalvikvm( 2359): Wrote stack traces to '/data/anr/traces.txt'
07-02 00:47:38.909 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:38.988 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 7605.1ms since event, 7598.9ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.019 I/dalvikvm( 2347): Wrote stack traces to '/data/anr/traces.txt'
07-02 00:47:39.019 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.105 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 7718.1ms since event, 7711.9ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.120 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.206 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 7824.6ms since event, 7818.3ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.222 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.589 I/dalvikvm( 2343): Wrote stack traces to '/data/anr/traces.txt'
07-02 00:47:39.722 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 8334.6ms since event, 8328.4ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.738 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.839 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 8453.6ms since event, 8447.3ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.863 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.948 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 8566.7ms since event, 8560.4ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:39.980 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.050 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 8662.7ms since event, 8656.5ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.066 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.113 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 8730.0ms since event, 8723.7ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.128 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.183 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 8797.9ms since event, 8791.6ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.198 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.238 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 8854.3ms since event, 8848.1ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.253 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.472 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9088.0ms since event, 9081.8ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.488 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.589 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9202.3ms since event, 9196.0ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.605 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.667 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9285.6ms since event, 9279.3ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.691 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.730 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9347.2ms since event, 9341.0ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.753 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.823 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9436.5ms since event, 9430.3ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.831 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.902 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9520.0ms since event, 9513.8ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:40.917 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:41.011 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9625.3ms since event, 9619.0ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:41.027 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:41.230 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9845.7ms since event, 9839.4ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:41.245 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:41.308 I/InputDispatcher( 1828): Application is not responding: Window{419f64a8 u0 StatusBar}.  It has been 9925.3ms since event, 9919.1ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:41.323 I/WindowManager( 1828): Input event dispatching timed out sending to StatusBar.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-02 00:47:41.394 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.738 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.738 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.745 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.745 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.745 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.745 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.745 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.745 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:41.753 I/InputDispatcher( 1828): Dropped event because it is stale.
07-02 00:47:42.894 E/ActivityManager( 1828): ANR in com.android.systemui
07-02 00:47:42.894 E/ActivityManager( 1828): PID: 2179
07-02 00:47:42.894 E/ActivityManager( 1828): Reason: Input dispatching timed out (Waiting because the touched window has not finished processing the input events that were previously delivered to it.)
07-02 00:47:42.894 E/ActivityManager( 1828): Load: 4.15 / 4.01 / 2.71
07-02 00:47:42.894 E/ActivityManager( 1828): CPU usage from 0ms to 6350ms later with 99% awake:
07-02 00:47:42.894 E/ActivityManager( 1828):   51% 4642/kworker/0:1: 0% user + 51% kernel
07-02 00:47:42.894 E/ActivityManager( 1828):   33% 1828/system_server: 29% user + 3.7% kernel / faults: 1960 minor 24 major
07-02 00:47:42.894 E/ActivityManager( 1828):   3.9% 2179/com.android.systemui: 3.4% user + 0.4% kernel / faults: 257 minor 8 major
07-02 00:47:42.894 E/ActivityManager( 1828):   0% 1426/debuggerd: 0% user + 0% kernel / faults: 1906 minor 33 major
07-02 00:47:42.894 E/ActivityManager( 1828):   2.2% 2343/com.android.phone: 1.5% user + 0.6% kernel / faults: 401 minor 15 major

    Thanks, regards.
    Click to expand...
    Click to collapse

    can you get me the file /data/anr/traces.txt ?
    View
    3
    Spaikbes
    Spaikbes
    4.4.4 2014.07.27 WEEKLY
    24 hours in 2g network -- 85% battery left!
    Good ROM :)
    View
    2
    K
    KM7ECZ
    Hi, the latest cwm for p970 what I'ev seen is 6.0.4.5 and worked well for me so far. You can download installer from this section http://xdaforums.com/showthread.php?t=1624565
    Did you miss some feature from higher versions ?

    mr_rious said:
    nice idea:good:
    well, then I start...
    any news to fix the gps in the coming days?
    Click to expand...
    Click to collapse

    I did some GPS testing and there you can see my result:
    Screenshot.png
    I use app GPS Status for downloading A-GPS data from internet. I think GPS in P970 working bad without A-GPS data, downloading them improves lock position speed for few days. The first lock after phone restart (rom update) takes little bit longer about 1-3min, where GPS searching for sattelites and caching information about them. With restart are these informations wiped out and phone need them acquire again. The lock speed could be individual, depending on many things, position, signal strenght (you should be outside with direct view to the sky, behind most new plastic windows is bad signal due present metalic layer on glass), and there could be bad contact with antena onside phone too. If I'm wrong correct me please.

    bzn7 said:
    Hi dear devs,

    I have same issue since 26th (nameless-4.4.4-20140626-p970-NIGHTLY). (Didn't try 25th, 27th and 30th.) I installed 29th today and have same issue again. 24th was clear. Firstly i installed 26th via update center on 24th (so without any wipe) and haven't got any bug. than i installed cm10 with full wipe and than installed 26th directly with full wipe and this issue occured. Same result with 29th. Tried 24th again, worked well. Now i'm using cm10. (cwm 6.0.4.5)

    When i plug usb to phone (charger or pc) it freezes. On booting too. If i plug charger when phone closed, it shows only LG logo. No charge or boot.

    Sorry, i haven't any log. I'm noob.

    Edit: Tried nameless-4.4.4-20140701-p970-NIGHTLY, phone hard locks.
    Click to expand...
    Click to collapse

    I wasn't able to reproduce this issue for get a log of it. Try use app named CatLog -> open it -> in menu press record -> set file name -> make procedure in witch there is problem -> if phone freeze, reboot and see if LogCat was able to save file on your SD card -> if you get that file you have log and you can post it

    Regards
    View

New posts