Jump to content

fear_4.008.08.EMEA.VFIT_v1.1 - custom rom


Recommended Posts

Guest gnufabio
Posted
can i flash it on top of 4.002.14?

How's the overall speed of the system?

Yep. The speed is awesome with choco kernel, it looks like cm7 :P

Guest gnufabio
Posted (edited)
news on 1.0?

News about what?

Edited by gnufabio
Guest zorginho
Posted
News about what?

on the 1.0 final... now we have only the beta... or not? :P

Guest gnufabio
Posted
on the 1.0 final... now we have only the beta... or not? :P

It works great even if it's a beta

Guest zorginho
Posted
It works great even if it's a beta

yeah i know... but I asked whether it was abandoned or not

[iT] lo so, ho domandato solo per accertarmi che non fosse abbandonata [/iT]

Guest gnufabio
Posted (edited)
yeah i know... but I asked whether it was abandoned or not

[iT] lo so, ho domandato solo per accertarmi che non fosse abbandonata [/iT]

Don't worry, we will update the rom when we have time to do it :P There is not too much to update since it's based on acer bin, we can only update the apps and try to make the rom faster :rolleyes:

Edited by gnufabio
Guest TheodoreTBag
Posted

Hello, little problem

I installed the rom with the recommended Kenel

- gnufabio choco's kernel - best choice for now, choco-acer-kernel-110511-1108.zip (8.78 MB) http://www.multiupload.com/T1DS5R3Y00

... but the proximity sensor is not working well: (

sometimes works, sometimes not!

I've disabled for now .. can be depended on the kernel I made​​?

Guest gnufabio
Posted (edited)
Hello, little problem

I installed the rom with the recommended Kenel

- gnufabio choco's kernel - best choice for now, choco-acer-kernel-110511-1108.zip (8.78 MB) http://www.multiupload.com/T1DS5R3Y00

... but the proximity sensor is not working well: (

sometimes works, sometimes not!

I've disabled for now .. can be depended on the kernel I made​​?

The kernel you flashed is old, flash this one: http://goo.gl/j7FTU

Enjoy choco kernel :D

Edited by gnufabio
Guest TheodoreTBag
Posted (edited)
The kernel you flashed is old, flash this one: http://goo.gl/j7FTU

Enjoy choco kernel :D

therefore this will solve the problem of the proximity sensor?

I do the flash even though I have already installed the choco-acer-kernel-110511-1108.zip?

ok, I put the new kernel right now, but the sensor still does not work, I tried to put as sensitivity is high or low, but none of it, even after you restart the terminal ..

a curiosity, how do I see that I'm using kernel in the rom?

Edited by TheodoreTBag
Guest gnufabio
Posted
therefore this will solve the problem of the proximity sensor?

I do the flash even though I have already installed the choco-acer-kernel-110511-1108.zip?

ok, I put the new kernel right now, but the sensor still does not work, I tried to put as sensitivity is high or low, but none of it, even after you restart the terminal ..

Too strange, are you using fear custom rom? =|

a curiosity, how do I see that I'm using kernel in the rom?

I'm sorry, what do you mean?

Guest TheodoreTBag
Posted

@gnufabio

i have found in batista!! era una scemenza!

thanks! grazie 1000!

Guest fear_factory84
Posted
yeah i know... but I asked whether it was abandoned or not

[iT] lo so, ho domandato solo per accertarmi che non fosse abbandonata [/iT]

as gnufabio said changes are not so much... I'm preparing an rc1 patch to be flashed on top of beta1.

I've moved some apps from /system/app to /data/app, optimized gps.conf to have agps enabled, and finally I'm thinking to include by default gnufabio's choco kernel as now the battery drain problem is gone... stay tuned!!!

Guest zorginho
Posted
as gnufabio said changes are not so much... I'm preparing an rc1 patch to be flashed on top of beta1.

I've moved some apps from /system/app to /data/app, optimized gps.conf to have agps enabled, and finally I'm thinking to include by default gnufabio's choco kernel as now the battery drain problem is gone... stay tuned!!!

Tnx u're great

Guest TheodoreTBag
Posted (edited)

Hello, today I had a very strange thing ..

the terminal while I was in my pocket, it was restarted, I found out because I heard the opening music phone, which unlike all the times I rebooted voluntarily, the jingle was repeated ad infinitum, I had to remove the battery , and then when I opened the phone, the widget colornote, they gave me error ..

happened to you?

use fear with the latest kernel gnufabio.

ITA

ciao, oggi mi è capitata una cosa alquanto strana..

mentre avevo il terminale in tasca, si è riavviato, me ne sono accorto perchè ho sentito la musica di avvio del telefono, che a differenza di tutte le volte che riavviavo io volontariamente, la musichetta si ripeteva all'infinito, ho dovuto togliere la batteria, e poi quando ho avviato il telefono, i widget di colornote, mi hanno dato errore..

capitato anche a voi?

uso fear con l'ultimo kernel di gnufabio.

Edited by TheodoreTBag
Guest gnufabio
Posted
Hello, today I had a very strange thing ..

the terminal while I was in my pocket, it was restarted, I found out because I heard the opening music phone, which unlike all the times I rebooted voluntarily, the jingle was repeated ad infinitum, I had to remove the battery , and then when I opened the phone, the widget colornote, they gave me error ..

happened to you?

use fear with the latest kernel gnufabio.

ITA

ciao, oggi mi è capitata una cosa alquanto strana..

mentre avevo il terminale in tasca, si è riavviato, me ne sono accorto perchè ho sentito la musica di avvio del telefono, che a differenza di tutte le volte che riavviavo io volontariamente, la musichetta si ripeteva all'infinito, ho dovuto togliere la batteria, e poi quando ho avviato il telefono, i widget di colornote, mi hanno dato errore..

capitato anche a voi?

uso fear con l'ultimo kernel di gnufabio.

Yeah, it happened to me too when i did a nandroid restore...don't know the problem =\

Guest TheodoreTBag
Posted
Yeah, it happened to me too when i did a nandroid restore...don't know the problem =\

I'm glad I am not alone, at least it means that my liquid works well!

Guest fear_factory84
Posted
Yeah, it happened to me too when i did a nandroid restore...don't know the problem =\

that happens (rarely) when app2sd script cannot mount the partition. Partition is not unmounted correctly when phone crashes or reboots. Sometimes fsck gives errors and a2sd script tries to fix them and to fix them it does some reboots.

Using a journaled filesystem for app2sd could fix recovery times, but on sd it's not recommended since it writes more on the sd.

Guest TheodoreTBag
Posted (edited)
that happens (rarely) when app2sd script cannot mount the partition. Partition is not unmounted correctly when phone crashes or reboots. Sometimes fsck gives errors and a2sd script tries to fix them and to fix them it does some reboots.

Using a journaled filesystem for app2sd could fix recovery times, but on sd it's not recommended since it writes more on the sd.

but tell me one thing, this problem of restarting, it is only if I put the kernel

- choco-acer-kernel-110511-1108.zip

- choco-acer-kernel-110527-1501

or even with the base kernel fear_4.008.08.EMEA.VFIT_v1.0_stock_kernel.zip?

ITA

ma spiegami una cosa, questo problema del riavvio, lo fà solo se metto il kernel

- choco-acer-kernel-110511-1108.zip

- choco-acer-kernel-110527-1501

oppure anche con il kernel di base fear_4.008.08.EMEA.VFIT_v1.0_stock_kernel.zip ??

Edited by TheodoreTBag
Guest fear_factory84
Posted
but tell me one thing, this problem of restarting, it is only if I put the kernel

- choco-acer-kernel-110511-1108.zip

- choco-acer-kernel-110527-1501

or even with the base kernel fear_4.008.08.EMEA.VFIT_v1.0_stock_kernel.zip?

ITA

ma spiegami una cosa, questo problema del riavvio, lo fà solo se metto il kernel

- choco-acer-kernel-110511-1108.zip

- choco-acer-kernel-110527-1501

oppure anche con il kernel di base fear_4.008.08.EMEA.VFIT_v1.0_stock_kernel.zip ??

it doesn't matter which kernel you use in theory.... practically I need a logcat to tell you what happens...

Guest TheodoreTBag
Posted
it doesn't matter which kernel you use in theory.... practically I need a logcat to tell you what happens...

hello fear, I wanted to inform you about the problem of restarting, I'm recording the logcat, when you post it shows the log ..

Now, I kindly ask you if you plan pending some updates soon, so I can help solve my problem ..

However, great rom, I've come to only 3 reboots sudden, we hope that you restart again,-P

Guest fear_factory84
Posted

where is this logcat?

hello fear, I wanted to inform you about the problem of restarting, I'm recording the logcat, when you post it shows the log ..

Now, I kindly ask you if you plan pending some updates soon, so I can help solve my problem ..

However, great rom, I've come to only 3 reboots sudden, we hope that you restart again,-P

Guest TheodoreTBag
Posted (edited)

hello, here isfinal part of this logcat

at the end of the phone has restarted! :-(

06-03 17:18:49.283 E/Tethering( 156): active iface (usb0) reported as added, ignoring

06-03 17:18:49.293 D/WifiService( 156): ACTION_BATTERY_CHANGED pluggedType: 2

06-03 17:18:54.283 E/Tethering( 156): active iface (usb0) reported as added, ignoring

06-03 17:18:54.283 D/WifiService( 156): ACTION_BATTERY_CHANGED pluggedType: 2

06-03 17:19:04.293 E/Tethering( 156): active iface (usb0) reported as added, ignoring

06-03 17:19:04.293 D/WifiService( 156): ACTION_BATTERY_CHANGED pluggedType: 2

06-03 17:20:04.283 E/Tethering( 156): active iface (usb0) reported as added, ignoring

06-03 17:20:04.293 D/WifiService( 156): ACTION_BATTERY_CHANGED pluggedType: 2

06-03 17:22:34.313 E/Tethering( 156): active iface (usb0) reported as added, ignoring

06-03 17:22:34.313 D/WifiService( 156): ACTION_BATTERY_CHANGED pluggedType: 2

06-03 17:22:40.373 D/KeyguardViewMediator( 156): onScreenTurnedOn, seq = 99

06-03 17:22:40.373 D/KeyguardViewMediator( 156): notifyScreenOnLocked

06-03 17:22:40.373 D/KeyguardViewMediator( 156): handleNotifyScreenOn

06-03 17:22:40.373 D/KeyguardViewManager( 156): onScreenTurnedOn()

06-03 17:22:40.423 I/ActivityManager( 156): No longer want com.android.vending (pid 3443): hidden #16

06-03 17:22:40.453 D/Tethering( 156): InitialState.processMessage what=4

06-03 17:22:40.473 D/WifiService( 156): ACTION_BATTERY_CHANGED pluggedType: 0

06-03 17:22:40.503 D/Tethering( 156): sendTetherStateChangedBroadcast 0, 0, 0

06-03 17:22:40.723 D/StatusBarPolicy( 156): updateDataIcon mDataState:0

06-03 17:22:40.863 D/WifiService( 156): ACTION_SCREEN_ON

06-03 17:22:40.863 D/WifiService( 156): [updateWifiWakelock] Wifi(On), Connection(no AP), Sleep Policy(0), Idle(not idle) Reason:ACTION_SCREEN_ON

06-03 17:22:40.863 D/WifiService( 156): [updateWifiWakelock] Lock

06-03 17:22:40.913 W/ActivityManager( 156): Activity pause timeout for HistoryRecord{304a88d8 com.fjsoft.myphoneexplorer.client/.MainActivity}

06-03 17:22:41.403 V/HeadsetObserver( 156): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=0, DEVPATH=/devices/virtual/switch/acer-hs, SEQNUM=6980, ACTION=change, SWITCH_NAME=No Device}

06-03 17:22:41.403 W/Vold ( 70): Ignoring unknown switch 'No Device'

06-03 17:22:41.413 I/ActivityManager( 156): Start proc com.nullsoft.winamp for broadcast com.nullsoft.winamp/.MediaButtonIntentReceiver: pid=3879 uid=10075 gids={3003, 1015, 1007}

06-03 17:22:41.703 I/ActivityThread( 3879): Publishing provider com.nullsoft.winamp.media: com.nullsoft.winamp.MediaSearchProvider

06-03 17:22:41.723 E/Wifi_Pair( 3879): Error occured while reading paired Winamp Ids.

06-03 17:22:41.773 I/ActivityManager( 156): Start proc com.android.music for broadcast com.android.music/.MediaButtonIntentReceiver: pid=3886 uid=10037 gids={3003, 1015}

06-03 17:22:41.993 D/DxDrmJavaWrap( 3879): enter JNI_OnLoad()

06-03 17:22:41.993 D/DxDrmJavaWrap( 3879): Pool was allocated at address: 0x30582720

06-03 17:22:42.013 D/DxDrmJavaWrap( 3879): exit JNI_OnLoad(65540)

06-03 17:22:42.043 E/PlayerDriver( 76): Creating Non-Tunnel mode playback - uncompressed MIO

06-03 17:22:42.073 I/AudioService( 156): Remote Control registerMediaButtonEventReceiver() for ComponentInfo{com.android.music/com.android.music.MediaButtonIntentReceiver}

06-03 17:22:42.093 W/MediaPlayer( 3879): info/warning (1, 44)

06-03 17:22:42.113 D/MediaPlaybackService( 3879): restored queue, currently at position 32806/149764 (requested 32806)

06-03 17:22:42.123 D/TelephonyManager( 3879): listen=android.telephony.PhoneStateListener$1@305741c0 event=32

06-03 17:22:42.233 I/MediaPlayer( 3879): Info (1,44)

06-03 17:22:42.403 V/HeadsetObserver( 156): Intent.ACTION_HEADSET_PLUG: state: 0 name: No Device mic: 0

06-03 17:22:42.413 D/PhoneApp( 649): mReceiver: ACTION_HEADSET_PLUG

06-03 17:22:42.413 D/PhoneApp( 649): state: 0

06-03 17:22:42.413 D/PhoneApp( 649): name: No Device

06-03 17:22:42.413 D/PhoneApp( 649): ril.HeadsetPlugged set 0

06-03 17:22:42.413 D/PhoneApp( 649): updateProximitySensorMode: state = IDLE

06-03 17:22:42.413 D/PhoneApp( 649): updateProximitySensorMode: lock already released.

06-03 17:22:42.433 D/PhoneApp( 649): handleQueryTTYModeResponse: TTY enable state successfully queried.

06-03 17:22:42.433 D/PhoneApp( 649): handleQueryTTYModeResponse:ttymode=0

06-03 17:22:42.433 V/AudioHardwareQSD( 76): setParameters() tty_mode=off

06-03 17:22:42.433 V/AudioHardwareQSD( 76): Routing audio Device from 0x8 to 0x8

06-03 17:22:44.263 E/Tethering( 156): attempting to remove unknown iface (usb0), ignoring

06-03 17:22:44.263 D/WifiService( 156): ACTION_BATTERY_CHANGED pluggedType: 0

06-03 17:22:50.413 W/ActivityManager( 156): Launch timeout has expired, giving up wake lock!

06-03 17:22:50.923 W/ActivityManager( 156): Activity idle timeout for HistoryRecord{304a88d8 com.fjsoft.myphoneexplorer.client/.MainActivity}

06-03 17:22:57.613 D/WindowManager( 156): I'm tired mEndcallBehavior=0x2

06-03 17:22:57.643 I/PowerManagerService( 156): 0 TAG: WifiService, TYPE: PARTIAL_WAKE_LOCK, activated, (minState=0, uid=1000, pid=156)

06-03 17:22:57.643 I/PowerManagerService( 156): 1 TAG: KeyInputQueue, TYPE: PARTIAL_WAKE_LOCK, activated, (minState=0, uid=1000, pid=156)

06-03 17:22:57.643 D/KeyguardViewMediator( 156): onScreenTurnedOff(2)

06-03 17:22:57.643 D/KeyguardViewMediator( 156): doKeyguard: showing the lock screen

06-03 17:22:57.643 D/KeyguardViewMediator( 156): showLocked

06-03 17:22:57.643 D/KeyguardViewMediator( 156): handleShow

06-03 17:22:57.643 D/KeyguardViewManager( 156): show(); mKeyguardView==null

06-03 17:22:57.643 D/KeyguardViewManager( 156): keyguard view is null, creating it...

06-03 17:22:57.693 D/LockPatternKeyguardView( 156): LockPatternKeyguardView ctor: about to createUnlockScreenFor; mEnableFallback=false

06-03 17:22:57.733 D/LockPatternKeyguardView( 156): createUnlockScreenFor(Pattern): mEnableFallback=false

06-03 17:22:57.793 V/LockPatternKeyguardView( 156): Gone=com.android.internal.policy.impl.PatternUnlockScreen@309a4b48

06-03 17:22:57.793 V/LockPatternKeyguardView( 156): Visible=com.android.internal.policy.impl.LockScreen@309742b0

06-03 17:22:57.803 W/WindowManager( 156): Key dispatching timed out sending to com.fjsoft.myphoneexplorer.client/com.fjsoft.myphoneexplorer.client.MainActivity

06-03 17:22:57.803 W/WindowManager( 156): Previous dispatch state: {{KeyEvent{action=1 code=24 repeat=0 meta=0 scancode=115 mFlags=8} to Window{3088cca8 com.android.phone/com.android.phone.InCallScreen paused=false} @ 1307108516792 lw=Window{3088cca8 com.android.phone/com.android.phone.InCallScreen paused=false} lb=android.os.BinderProxy@30838f08 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{3088cca8 com.android.phone/com.android.phone.InCallScreen paused=false}}}

06-03 17:22:57.803 W/WindowManager( 156): Current dispatch state: {{null to Window{3073d018 com.fjsoft.myphoneexplorer.client/com.fjsoft.myphoneexplorer.client.MainActivity paused=false} @ 1307114577805 lw=Window{3073d018 com.fjsoft.myphoneexplorer.client/com.fjsoft.myphoneexplorer.client.MainActivity paused=false} lb=android.os.BinderProxy@307c2280 fin=false gfw=true ed=false tts=0 wf=false fp=false mcf=Window{3073d018 com.fjsoft.myphoneexplorer.client/com.fjsoft.myphoneexplorer.client.MainActivity paused=false}}}

06-03 17:22:58.073 D/KeyguardViewMediator( 156): adjustUserActivityLocked mShowing: true mHidden: false

06-03 17:22:58.073 D/LockPatternKeyguardView( 156): No updateUI-> Pattern

06-03 17:22:58.093 D/StatusBar( 156): DISABLE_EXPAND: yes

06-03 17:22:58.263 D/GoogleLoginService( 710): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }

06-03 17:22:58.293 W/ActivityManager( 156): Activity pause timeout for HistoryRecord{304a88d8 com.fjsoft.myphoneexplorer.client/.MainActivity}

06-03 17:22:58.303 D/WifiService( 156): ACTION_SCREEN_OFF

06-03 17:22:58.423 D/skia ( 156): purging 238K from font cache [9 entries]

06-03 17:22:58.535 W/IInputConnectionWrapper( 655): getExtractedText on inactive InputConnection

06-03 17:22:58.544 W/IInputConnectionWrapper( 655): getExtractedText on inactive InputConnection

06-03 17:22:59.173 E/ActivityManager( 156): ANR in com.fjsoft.myphoneexplorer.client (com.fjsoft.myphoneexplorer.client/.MainActivity)

06-03 17:22:59.173 E/ActivityManager( 156): Reason: keyDispatchingTimedOut

06-03 17:22:59.173 E/ActivityManager( 156): Load: 0.0 / 0.0 / 0.0

06-03 17:22:59.173 E/ActivityManager( 156): CPU usage from 410188ms to 30ms ago:

06-03 17:22:59.173 E/ActivityManager( 156): sensorserver_ya: 4% = 1% user + 3% kernel / faults: 1 minor

06-03 17:22:59.173 E/ActivityManager( 156): system_server: 3% = 1% user + 1% kernel / faults: 1749 minor 10 major

06-03 17:22:59.173 E/ActivityManager( 156): anlawson.logcat: 0% = 0% user + 0% kernel / faults: 106 minor

06-03 17:22:59.173 E/ActivityManager( 156): com.jim2: 0% = 0% user + 0% kernel / faults: 134 minor

06-03 17:22:59.173 E/ActivityManager( 156): explorer.client: 0% = 0% user + 0% kernel / faults: 29 minor

06-03 17:22:59.173 E/ActivityManager( 156): oid.inputmethod: 0% = 0% user + 0% kernel / faults: 75 minor 3 major

06-03 17:22:59.173 E/ActivityManager( 156): vold: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): com.whatsapp: 0% = 0% user + 0% kernel / faults: 62 minor

06-03 17:22:59.173 E/ActivityManager( 156): liquid.settings: 0% = 0% user + 0% kernel / faults: 9 minor

06-03 17:22:59.173 E/ActivityManager( 156): suspend: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): droid.apps.maps: 0% = 0% user + 0% kernel / faults: 69 minor

06-03 17:22:59.173 E/ActivityManager( 156): netd: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): LocationService: 0% = 0% user + 0% kernel / faults: 44 minor

06-03 17:22:59.173 E/ActivityManager( 156): zygote: 0% = 0% user + 0% kernel / faults: 154 minor

06-03 17:22:59.173 E/ActivityManager( 156): m.android.phone: 0% = 0% user + 0% kernel / faults: 36 minor

06-03 17:22:59.173 E/ActivityManager( 156): events/0: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): wfreak.launcher: 0% = 0% user + 0% kernel / faults: 12 minor

06-03 17:22:59.173 E/ActivityManager( 156): mediaserver: 0% = 0% user + 0% kernel / faults: 111 minor

06-03 17:22:59.173 E/ActivityManager( 156): zygote: 0% = 0% user + 0% kernel / faults: 46 minor

06-03 17:22:59.173 E/ActivityManager( 156): logcat: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): ksoftirqd/0: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): port-bridge: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): d.process.media: 0% = 0% user + 0% kernel / faults: 23 minor

06-03 17:22:59.173 E/ActivityManager( 156): kbatt_cbclntd: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): logcat: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): facebook.katana: 0% = 0% user + 0% kernel / faults: 19 minor

06-03 17:22:59.173 E/ActivityManager( 156): d.apps.uploader: 0% = 0% user + 0% kernel / faults: 10 minor

06-03 17:22:59.173 E/ActivityManager( 156): init: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): rpcrotuer_smd_x: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): rild: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): d.process.acore: 0% = 0% user + 0% kernel / faults: 15 minor

06-03 17:22:59.173 E/ActivityManager( 156): com.acer.tasks: 0% = 0% user + 0% kernel / faults: 16 minor

06-03 17:22:59.173 E/ActivityManager( 156): oid.voicesearch: 0% = 0% user + 0% kernel / faults: 18 minor

06-03 17:22:59.173 E/ActivityManager( 156): epad.color.note: 0% = 0% user + 0% kernel / faults: 16 minor

06-03 17:22:59.173 E/ActivityManager( 156): +nullsoft.winamp: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): +m.android.music: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): -android.vending: 0% = 0% user + 0% kernel

06-03 17:22:59.173 E/ActivityManager( 156): TOTAL: 3% = 2% user + 1% kernel + 0% iowait

06-03 17:22:59.183 W/WindowManager( 156): Continuing to wait for key to be dispatched

06-03 17:22:59.183 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:22:59.183 W/WindowManager( 156): No window to dispatch pointer action 0

06-03 17:22:59.183 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:22:59.183 W/WindowManager( 156): No window to dispatch pointer action 0

06-03 17:22:59.183 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 0

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 0

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 0

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 0

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:22:59.193 W/WindowManager( 156): No focus window, dropping: KeyEvent{action=0 code=4 repeat=0 meta=0 scancode=158 mFlags=8}

06-03 17:22:59.193 W/WindowManager( 156): No focus window, dropping: KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8}

06-03 17:22:59.193 W/WindowManager( 156): No window to dispatch pointer action 0

06-03 17:22:59.203 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:23:03.073 D/KeyguardViewMediator( 156): onWakeKeyWhenKeyguardShowing(26)

06-03 17:23:03.073 D/KeyguardViewMediator( 156): wakeWhenReadyLocked(26)

06-03 17:23:03.073 D/KeyguardViewMediator( 156): handleWakeWhenReady(26)

06-03 17:23:03.073 D/KeyguardViewManager( 156): wakeWhenReady(26)

06-03 17:23:03.073 D/LockPatternKeyguardView( 156): onWakeKey

06-03 17:23:03.073 D/LockPatternKeyguardView( 156): poking wake lock immediately

06-03 17:23:03.095 D/KeyguardViewMediator( 156): onScreenTurnedOn, seq = 100

06-03 17:23:03.095 D/KeyguardViewMediator( 156): notifyScreenOnLocked

06-03 17:23:03.095 D/KeyguardViewMediator( 156): handleNotifyScreenOn

06-03 17:23:03.103 D/KeyguardViewManager( 156): onScreenTurnedOn()

06-03 17:23:03.813 W/SurfaceFlinger( 156): received signal 31 in thread 160, resending to 165

06-03 17:23:04.953 D/KeyguardViewMediator( 156): keyguardDone(true)

06-03 17:23:05.013 D/KeyguardViewMediator( 156): handleKeyguardDone

06-03 17:23:05.013 D/KeyguardViewMediator( 156): handleHide

06-03 17:23:05.013 D/KeyguardViewManager( 156): hide()

06-03 17:23:05.023 D/KeyguardViewMediator( 156): adjustUserActivityLocked mShowing: false mHidden: false

06-03 17:23:05.113 W/WindowManager( 156): No window to dispatch pointer action 1

06-03 17:23:06.893 W/ActivityManager( 156): Force finishing activity com.fjsoft.myphoneexplorer.client/.MainActivity

06-03 17:23:06.893 I/ActivityManager( 156): Killing com.fjsoft.myphoneexplorer.client (pid=3861): user's request

06-03 17:23:06.923 I/ActivityManager( 156): Process com.fjsoft.myphoneexplorer.client (pid 3861) has died.

06-03 17:23:06.923 W/ActivityManager( 156): Scheduling restart of crashed service com.fjsoft.myphoneexplorer.client/.ClientService in 5000ms

06-03 17:23:06.923 D/BluetoothService( 156): Tracked app 3861 died

06-03 17:23:06.923 D/BluetoothService( 156): Removing service record 10003 for pid 3861

06-03 17:23:06.933 D/WifiService( 156): releaseWifiLockLocked: WifiLock{wifilock type=1 binder=android.os.BinderProxy@30753f08}

06-03 17:23:06.953 I/WindowManager( 156): WIN DEATH: Window{3073d018 com.fjsoft.myphoneexplorer.client/com.fjsoft.myphoneexplorer.client.MainActivity paused=true}

06-03 17:23:07.033 W/InputManagerService( 156): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@3073d748

06-03 17:23:07.033 I/System.out( 655): UPDATINGCOUNTERS: com.fjsoft.myphoneexplorer.client = 0

06-03 17:23:08.293 W/ActivityManager( 156): Timeout of broadcast BroadcastRecord{309fd8c0 android.intent.action.SCREEN_OFF} - receiver=android.app.ActivityThread$PackageInfo$ReceiverDispatcher$InnerReceiver@309860e8

06-03 17:23:08.303 W/ActivityManager( 156): Receiver during timeout: BroadcastFilter{30986350 ReceiverList{309862d8 156 system/1000 local:309860e8}}

06-03 17:23:08.333 D/ActiveCollector( 3633): state now IDLE

06-03 17:23:11.943 I/ActivityManager( 156): Start proc com.fjsoft.myphoneexplorer.client for service com.fjsoft.myphoneexplorer.client/.ClientService: pid=3904 uid=10060 gids={3003, 1007, 1015, 3002}

06-03 17:23:12.613 D/TelephonyManager( 3904): listen=android.telephony.PhoneStateListener$1@303866a0 event=51

Edited by TheodoreTBag
  • 2 weeks later...
Guest mAdkoE
Posted

screenshot1eh.jpg

This is the astonishing battery consumption of this rom.

I did about 60 minutes of call, about an hour of 3G,an hour with wifi, several sms (at least 50).

I got light sensor ON, gnufabio kernel@998 (setcpu slows it @768 only when battery is <35%, and @245 with screen off).

Uninstalled all Acer stuff, and used a2sd.

fear_factory you rock ;)

Guest fear_factory84
Posted
screenshot1eh.jpg

This is the astonishing battery consumption of this rom.

I did about 60 minutes of call, about an hour of 3G,an hour with wifi, several sms (at least 50).

I got light sensor ON, gnufabio kernel@998 (setcpu slows it @768 only when battery is <35%, and @245 with screen off).

Uninstalled all Acer stuff, and used a2sd.

fear_factory you rock ;)

If you disable proximity sensor on call (of course you need to disable manually screen), you will get even less battery drain. The high "android system" value is due to the prox sensor usage..

If you like it, you must live with higher battery drain on call..

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.