Database Develop

[Q] Gallery FC even after revert to stock (attached Logcat)

Code:
I/ActivityThread( 3979): Publishing provider com.cooliris.picasa.contentprovider
: com.cooliris.picasa.PicasaContentProvider
I/Launcher( 2669): onWindowFocusChanged(false)
I/global ( 2466): Default buffer size used in BufferedInputStream constructor.
It would be better to be explicit if an 8k buffer is required.
D/dalvikvm( 3979): GC_EXTERNAL_ALLOC freed 7840 objects / 437048 bytes in 36ms
D/TEST ( 3979): getIntent().getExtras()null
D/SensorManager( 3979): ====>>>>>Num Sensor: 1
D/SensorManager( 3979): ====>>>>>Num Sensor: 2
D/SensorManager( 3979): ====>>>>>Num Sensor: 3
D/SensorManager( 3979): ====>>>>>Num Sensor: 4
D/SensorManager( 3979): ====>>>>>Num Sensor: 5
D/SensorManager( 3979): ====>>>>>Num Sensor: 6
D/SensorManager( 3979): ====>>>>>Num Sensor: 7
D/SensorManager( 3979): ====>>>>>Num Sensor: 0
E/SensorManager( 3979): ####### akmd2 started!!!
I/Gallery ( 3979): onCreate
D/StatusBar( 2466): manageDisableList what=0x1 pkg=com.cooliris.media
D/StatusBar( 2466): DISABLE_EXPAND: yes
E/SensorManager( 3979): registerListener 1:BMA150 delay:120
D/Sensors ( 2466): open_input open fd = 148
D/Sensors ( 2466): open_input leave
D/Sensors ( 2466): sensors_control_open_data_source: fd=148
D/DiskCacheSEC( 3979): [SE Lab.] index file will be loaded..
W/DiskCacheSEC( 3979): loadIndex /mnt/sdcard/Android/data/com.cooliris.media/cac
he/local-image-thumbs/index
W/dalvikvm( 3979): Exception Ljava/lang/ArrayIndexOutOfBoundsException; thrown d
uring Lcom/cooliris/media/LocalDataSource;.<clinit>
E/SensorManager( 3979): =======>>>Sensor Thread RUNNING <<<========
D/Sensors ( 2466): sensors_control_activate active=00000012 sensor=00000002 new_
sensors=12 changed=0
I/Sensors ( 2466): set AK daemon delay=60 fd=147
W/dalvikvm( 3979): threadid=15: thread exiting with uncaught exception (group=0x
4001d7d0)
W/SensorManager( 3979): Delay Candidate Listener 0 Sensor:1 delay:120
I/Sensors ( 3979): sensors_data_delay handle=1 delay=120 mMinDelay=120
E/SensorManager( 3979): registerListener 1:BMA150 delay:120
D/Sensors ( 2466): sensors_control_activate active=00000012 sensor=00000002 new_
sensors=12 changed=0
I/Sensors ( 2466): set AK daemon delay=60 fd=147
W/SensorManager( 3979): Delay Candidate Listener 0 Sensor:1 delay:120
I/Sensors ( 3979): sensors_data_delay handle=1 delay=120 mMinDelay=120
E/AndroidRuntime( 3979): FATAL EXCEPTION: Thread-16
E/AndroidRuntime( 3979): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 3979): at com.cooliris.media.Gallery$3.run(Gallery.java
:372)
E/AndroidRuntime( 3979): Caused by: java.lang.ArrayIndexOutOfBoundsException
E/AndroidRuntime( 3979): at com.cooliris.media.DiskCacheSEC$ChunkFile.set
Alloc(DiskCacheSEC.java:171)
E/AndroidRuntime( 3979): at com.cooliris.media.DiskCacheSEC$FreeList.setA
lloc(DiskCacheSEC.java:225)
E/AndroidRuntime( 3979): at com.cooliris.media.DiskCacheSEC.loadIndex(Dis
kCacheSEC.java:699)
E/AndroidRuntime( 3979): at com.cooliris.media.DiskCache.<init>(DiskCache
.java:57)
E/AndroidRuntime( 3979): at com.cooliris.media.DiskCacheSEC.<init>(DiskCa
cheSEC.java:386)
E/AndroidRuntime( 3979): at com.cooliris.media.LocalDataSource.<clinit>(L
ocalDataSource.java:43)
E/AndroidRuntime( 3979): ... 1 more
W/ActivityManager( 2466): Force finishing activity com.cooliris.media/.Gallery
I/ ( 2466): dumpmesg > "/data/log/dumpstate_app_error.log"
D/GoogleLoginService( 2643): onBind: Intent { act=android.accounts.AccountAuthen
ticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
W/GoogleLoginService( 2643): Device has no accounts: sending Intent { act=com.go
ogle.android.gsf.LOGIN_ACCOUNTS_MISSING }
I/CacheService( 3979): onHandleIntent Intent { act=com.cooliris.cache.action.CAC
HE cmp=com.cooliris.media/com.cooliris.cache.CacheService (has extras) }
I/CacheService( 3979): restartThread() threadRef = null, name = CacheRefresh
I/CacheService( 3979): Refreshing cache.
E/DiskCache( 3979): Delete All Cache Files!!!
I/dumpstate( 4000): begin
W/Sensors ( 3979): Reader thread open Accelerometer = 32
I/CacheService( 3979): Building albums.
D/VoldCmdListener( 2356): asec list
I/dumpstate( 4000): done
W/ActivityManager( 2466): Activity pause timeout for HistoryRecord{47c54090 com.
cooliris.media/.Gallery}
I/dalvikvm( 3979): Rejecting re-init on previously-failed class Lcom/cooliris/me
dia/LocalDataSource; v=0x0
I/RenderView( 3979): OnPause RenderView [email protected]
W/dalvikvm( 3979): threadid=18: thread exiting with uncaught exception (group=0x
4001d7d0)
E/SensorManager( 3979): unregisterListener: [email protected]
70
I/Process ( 3979): Sending signal. PID: 3979 SIG: 9
I/Launcher( 2669): onResume(). mIsNewIntent : false
D/WeatherClock( 2669): Main Clock resumed
I/Launcher( 2669): Clearing the Status Bar lock in onResume function
D/StatusBar( 2466): manageDisableList what=0x0 pkg=com.sec.android.app.twlaunche
r
E/Launcher( 2669): setWindowOpaque()
I/Launcher( 2669): onResume() ended
I/ActivityManager( 2466): Process com.cooliris.media (pid 3979) has died.
I/StatusBar( 2466): binder died for pkg=com.cooliris.media
D/StatusBar( 2466): manageDisableList what=0x0 pkg=com.cooliris.media
I/WindowManager( 2466): WIN DEATH: Window{47d40ba8 com.cooliris.media/com.coolir
is.media.Gallery paused=false}
I/Launcher( 2669): onWindowFocusChanged(true)
E/Launcher( 2669): setWindowOpaque()
W/InputManagerService( 2466): Window already focused, ignoring focus gain of: co
[email protected]
E/InfoAlarmWidget( 2669): AllDay Event Count = 0
^C
Gallery fc's when i try opening it

delete the datas from application management.

I've been running into this issue as well, even after clearing the data and rebooting. This all has started to occur following a reflash to the stock ROM on my Verizon Galaxy Tab. Thanks for any additional insight!

I ran into the problem of the Gallery app force closing every time I opened it on my Samsung Galaxy Tab and have a solution!
The problem is that com.cooliris.media (the Gallery app) has corrupt cache files on the sdcard.
Oddly, using the Menu, Settings, Applications, Gallery and clearing data does not work.
Rather than formatting the sdcard (which would also work), you can remove just these files.
Either mount the sdcard to your computer, and remove them from /sdcard/Android/data/com.cooliris.media/cache or if you are rooted then you can do this:
adb shell
su
cd /sdcard/Android/data/com.cooliris.media/cache
rm -r *

[Android 2.2-3+] Killswitch for tablets and phones with cases [12 May]]

MOD EDIT: links removed
Killswitch for tablets and phones
Fahrbot Mobile presents Killswitch, a utility made specifically for devices with cases.
What does Killswitch do?
The app uses a combination of sensors to control the sleep state and screen lock of any device.
At the moment, it uses the proximity sensor, light sensor and accelerometer.
Killswitch now has a night mode for weak sensors - if you find there are errors working in low light conditions on your device, simply set up a schedule!
Killswitch has the added advantage of removing your lockscreen via two different methods if you so wish. If you have a case, it really isn't necessary and can be annoying.
Why use Killswitch?
Killswitch will save you battery - putting your device to sleep is as intuitive as shutting your case or turning your phone face down.
And, of course, Killswitch will show all your ipad and iphone loving mates why android is just that much more awesome
After upgrading to a newer version, please go into the settings dialog and enable Killswitch again. This is not optimal, but it saves battery and cpu time by removing the necessity for a constantly running service!
In order to uninstall the app, untick "Admin privileges" in Killswitch or via the Accessibility page of your device's settings.
sleeplessninja video review:
Thanks bud.
Android Market link:
The app is available right now on the Android Market.
Screens:

Killswitch 1.0.5
+ Added scheduling
+ Added night mode
+ Fixed bugs on many devices
Killswitch 1.0.4
+ Verbose debugging mode added
Killswitch 1.0.3
+ Bigger buttons
+ Sensitivity tweaks for Samsung 2.2 devices
+ Bug logging
Killswitch 1.0.2
+ Minor layout tweaks
+ Added new icons
Killswitch 1.0.1
+ Fixed orientation-related problems
+ Tweaked default activation delay value
+ Cleaned up Help and Tips dialog
+ Added license check delay to fix caching problems on Google's end
Killswitch 1.0.0 RC
+ Added license check, nag screen, functionality restrictions for unlicensed copies
+ Alternative no-lock mechanism reintegrated
+ About page added
+ Issues related to ProGuard fixed

reserved for suggestion list

Just a heads-up for those who have not managed to work out how to use Killswitch - despite very clear instructions in the Help and Tips dialog.
On a tablet with case the settings should look like this:
Enable Killswitch: tick
Admin Permissions: tick
Confirmation time: 10sec
Activation delay: 6sec
No-lock: Disable screen lock
Use proximity: no tick
Use light sensor: tick
Sensitivity: 10%
Use accelerometer: no tick
For a phone the settings should be exactly the same, except with "Use proximity sensor: tick". These are the settings Im using right now and they work perfectly.
The point of the app is also to avoid accidental sleep mode in a dark room through the popup dialog. Do not choose "Use accelerometer" unless you plan on using both light sensor and facedown at the same time. Instead, choose "Enable facedown mode only" if you see the popup dialog while using the tab in a dark room - this will disable the light sensor but enable facedown until you next swich on/ off.
Please read the Help and Tips section before giving up!

I've bought and installed Kill Switch for my galaxy tab, used the exact same settings shown above but it doesn't appear to be doing anything on my tab. I'm on overcome 1.2.3 and have the fugutweaks applied

After upgrading to a newer version, please go into the settings dialog and enable Killswitch again. This is not optimal, but it saves battery and cpu time by removing the necessity for a constantly running service!
Im using overcome 1.2 and its working just fine... also, its tested to work on JK5 and up stock roms.
Decrease activation delay in settings to 2 seconds, then try putting your finger over the light sensor to check whether its working - its just to the right of the front facing camera.
If not this is a kernel-related problem, so please send logcat!

Hmm...I appear to be having a problem with the light sensor. I can get the accelerometer to switch it off. I think I'm going to undo the fugutweaks, see if that's the problem.

Could you please post a logcat? This would be the easiest way to check what the problem is.
You can get the app aLogcat for free from the market. Use it after youve turned on killswitch and just post the resulting text here.

Sorry, I undid the fugutweaks before I read your reply and this appears to have cured the problem

OK, no problem! I hope you find the functionality useful!

mrgrey1701 said:
Sorry, I undid the fugutweaks before I read your reply and this appears to have cured the problem
Click to expand...
Click to collapse
I spoke too soon...its very temperamental with the light sensor - sometimes it works, most times it doesn't. Installing logcat and will post results here shortly:
D/alogcat ( 4511): stopped
D/alogcat ( 4511): starting ...
W/InputManagerService( 2829): Window already focused, ignoring focus gain of: [email protected]
D/dalvikvm( 2917): GC_EXPLICIT freed 15 objects / 536 bytes in 77ms
D/dalvikvm( 2917): GC_EXPLICIT freed 7 objects / 288 bytes in 71ms
D/BatteryService( 2829): update start
D/BatteryService( 2829): updateBattery level:77 scale:100 status:4 health:2 present:true voltage: 3874 temperature: 323 technology: Li-ion AC powered:false USB powered:false icon:17302168
D/WifiService( 2829): ACTION_BATTERY_CHANGED pluggedType: 0
D/dalvikvm( 4449): GC_EXPLICIT freed 17829 objects / 1823232 bytes in 448ms
D/dalvikvm( 2924): GC_EXPLICIT freed 2942 objects / 120712 bytes in 274ms
W/PowerManagerService( 2829): Timer 0x7->0x3|0x0
I/PowerManagerService( 2829): Ulight 7->3|0
V/WindowManager( 2829): onOrientationChanged, rotation changed to 1 false mLockedRotation=-1
E/WindowManager( 2829): Overwriting rotation value from 1
V/WindowManager( 2829): Rotation changed to 1 from 0 (forceApp=-1, req=1)
I/WindowManager( 2829): Setting rotation to 1, animFlags=0
E/SurfaceFlinger( 2829): Surface Flinger::setOrientation mIsRotationPossible = 0, nBackupOrientationValue = 1
I/TvOut-Observer( 2829): setTvoutOrientation rotation = 1
E/TvOut-Observer( 2829): SetOrientation
I/ActivityManager( 2829): Config changed: { scale=1.0 imsi=234/20 loc=en_GB touch=3 keys=1/1/2 nav=1/1 orien=2 layout=35 uiMode=17 seq=6 FlipFont=0}
D/PhoneApp( 2921): updateProximitySensorMode: state = IDLE
I/UsageStats( 2829): Unexpected resume of org.jtb.alogcat while already resumed in org.jtb.alogcat
V/alogcat ( 4511): save instance
V/alogcat ( 4511): paused
D/alogcat ( 4511): stopping ...
V/alogcat ( 4511): destroyed
D/alogcat ( 4511): stopped
V/alogcat ( 4511): created
D/alogcat ( 4511): canceling periodic saves
V/alogcat ( 4511): started
V/alogcat ( 4511): restore instance
V/alogcat ( 4511): resumed
D/alogcat ( 4511): starting ...
V/Thumb Keyboard( 2917): HAAALLLOOO widht: 1025
V/Thumb Keyboard( 2917): HAAALLLOOO height: 272
V/WindowManager( 2829): onOrientationChanged, rotation changed to 2 false mLockedRotation=-1
E/WindowManager( 2829): Overwriting rotation value from 2
V/WindowManager( 2829): Rotation changed to 2 from 1 (forceApp=-1, req=2)
I/WindowManager( 2829): Setting rotation to 2, animFlags=0
E/SurfaceFlinger( 2829): Surface Flinger::setOrientation mIsRotationPossible = 0, nBackupOrientationValue = 2
I/TvOut-Observer( 2829): setTvoutOrientation rotation = 2
E/TvOut-Observer( 2829): SetOrientation
I/ActivityManager( 2829): Config changed: { scale=1.0 imsi=234/20 loc=en_GB touch=3 keys=1/1/2 nav=1/1 orien=1 layout=35 uiMode=17 seq=7 FlipFont=0}
D/PhoneApp( 2921): updateProximitySensorMode: state = IDLE
I/UsageStats( 2829): Unexpected resume of org.jtb.alogcat while already resumed in org.jtb.alogcat
D/dalvikvm( 2917): GC_EXPLICIT freed 1479 objects / 99312 bytes in 137ms
V/alogcat ( 4511): save instance
V/alogcat ( 4511): paused
D/alogcat ( 4511): stopping ...
V/alogcat ( 4511): destroyed
D/alogcat ( 4511): stopped
V/alogcat ( 4511): created
D/alogcat ( 4511): canceling periodic saves
V/alogcat ( 4511): started
V/alogcat ( 4511): restore instance
V/alogcat ( 4511): resumed
D/alogcat ( 4511): starting ...
V/Thumb Keyboard( 2917): HAAALLLOOO widht: 606
V/Thumb Keyboard( 2917): HAAALLLOOO height: 462
D/dalvikvm( 2917): GC_EXPLICIT freed 2064 objects / 123784 bytes in 98ms
D/dalvikvm( 2917): GC_EXPLICIT freed 581 objects / 23088 bytes in 69ms
D/dalvikvm( 2917): GC_EXPLICIT freed 7 objects / 296 bytes in 60ms
D/UpdateService( 3192): rotation (new config = { scale=1.0 imsi=234/20 loc=en_GB touch=3 keys=1/1/2 nav=1/1 orien=1 layout=35 uiMode=17 seq=7 FlipFont=0})
I/DBG_WSS_DM( 3338): [wssTelephonyData.java Line:153] getInstance PHONE_TYPE_GSM
V/AlarmManager( 2829): set: Alarm{48f8a5d0 type 2 com.google.android.apps.maps}
D/dalvikvm( 2829): GC_EXPLICIT freed 19940 objects / 871280 bytes in 288ms
D/dalvikvm( 4177): GC_EXPLICIT freed 272 objects / 14272 bytes in 108ms
I/DBG_WSS_DM( 3338): [wssTelephonyData.java Line:153] getInstance PHONE_TYPE_GSM
V/AlarmManager( 2829): set: Alarm{48faf1a0 type 2 com.google.android.apps.maps}
D/dalvikvm( 3049): GC_EXPLICIT freed 14292 objects / 815880 bytes in 159ms
W/PowerManagerService( 2829): Timer 0x3->0x3|0x0
V/WindowManager( 2829): onOrientationChanged, rotation changed to 0 false mLockedRotation=-1
E/WindowManager( 2829): Overwriting rotation value from 0
V/WindowManager( 2829): Rotation changed to 0 from 2 (forceApp=-1, req=0)
I/WindowManager( 2829): Setting rotation to 0, animFlags=0
E/SurfaceFlinger( 2829): Surface Flinger::setOrientation mIsRotationPossible = 0, nBackupOrientationValue = 0
I/TvOut-Observer( 2829): setTvoutOrientation rotation = 0
E/TvOut-Observer( 2829): SetOrientation
V/AlarmManager( 2829): set: Alarm{48e73de8 type 1 android}
D/dalvikvm( 2829): GC_EXPLICIT freed 2694 objects / 116128 bytes in 259ms
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
I/PowerManagerService( 2829): Ulight 3->7|0
V/WindowManager( 2829): Dsptch to Window{48f9bc90 org.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
W/KeyCharacterMap( 4511): No keyboard for id 0
W/KeyCharacterMap( 4511): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
V/WindowManager( 2829): Dsptch to Window{48f9bc90 org.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
V/VibratorService( 2829): vibrateImmVibe: 13, magnitude: -1
V/VibratorService( 2829): setVibeStrength = 10000
V/WindowManager( 2829): Delivering toWindow{48d4a768 AtchDlgrg.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
V/WindowManager( 2829): Delivering toWindow{48d4a768 AtchDlgrg.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}

There is nothing about fahrbotapps in this logcat!
Try opening the Killswitch properties, unticking and again ticking "Enable Killswitch" and then running aLogcat.
Once its running put your finger over the light sensor and see what happens. Even if nothing happens within 10 seconds, pause the logging and then post here!

Sorry, quite new to this. After rebooting again it now appears to work well, as you should see below.
Thanks for your time. Very useful app
D/alogcat ( 4342): stopped
V/alogcat ( 4342): paused
E/WindowManager( 2829): Overwriting rotation value from 0
I/Zygote ( 4377): Zygote: pid 4377 has INTERNET permission, then set capability for CAP_NET_RAW
I/Zygote ( 4377): Zygote: pid 4377 has CALL PRIVILEGED permission, then set capability for CAP_SYS_ADMIN (21)
I/ActivityManager( 2829): No longer want com.android.mms (pid 3178): hidden #16
W/ResourceType( 2829): Skipping entry 0x7f040006 in package table 0 because it is not complex!
W/ResourceType( 2829): Skipping entry 0x7f040005 in package table 0 because it is not complex!
I/ActivityManager( 2829): No longer want com.android.settings (pid 4377): hidden #16
D/alogcat ( 4342): stopping ...
D/alogcat ( 4342): stopped
V/WindowManager( 2829): Delivering toWindow{48deb1a0 com.fede.launcher/com.fede.launcher.Launcher paused=false}
V/WindowManager( 2829): Delivering toWindow{48deb1a0 com.fede.launcher/com.fede.launcher.Launcher paused=false}
D/dalvikvm( 2917): GC_EXPLICIT freed 14 objects / 584 bytes in 50ms
V/WindowManager( 2829): Delivering toWindow{48deb1a0 com.fede.launcher/com.fede.launcher.Launcher paused=false}
V/WindowManager( 2829): Delivering toWindow{48deb1a0 com.fede.launcher/com.fede.launcher.Launcher paused=false}
V/WindowManager( 2829): Delivering toWindow{48deb1a0 com.fede.launcher/com.fede.launcher.Launcher paused=false}
V/WindowManager( 2829): Delivering toWindow{48deb1a0 com.fede.launcher/com.fede.launcher.Launcher paused=false}
I/ActivityManager( 2829): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=fahrbot.apps.killswitch/.activities.ConfiguratorPreferenceActivity }
I/ActivityManager( 2829): Start proc fahrbot.apps.killswitch for activity fahrbot.apps.killswitch/.activities.ConfiguratorPreferenceActivity: pid=4384 uid=10136 gids={}
W/Process ( 2829): Unable to open /proc/3178/status
D/dalvikvm( 2637): GC_EXPLICIT freed 307 objects / 11648 bytes in 28ms
E/WindowManager( 2829): Overwriting rotation value from 0
W/ResourceType( 2829): Skipping entry 0x7f040007 in package table 0 because it is not complex!
W/ResourceType( 2829): Skipping entry 0x7f040008 in package table 0 because it is not complex!
D/dalvikvm( 2637): GC_EXPLICIT freed 52 objects / 2480 bytes in 81ms
D/dalvikvm( 2637): GC_EXPLICIT freed 2 objects / 48 bytes in 49ms
I/global ( 2829): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
D/SensorManager( 4384): ====>>>>>Num Sensor: 1
D/SensorManager( 4384): ====>>>>>Num Sensor: 2
D/SensorManager( 4384): ====>>>>>Num Sensor: 3
D/SensorManager( 4384): ====>>>>>Num Sensor: 4
D/SensorManager( 4384): ====>>>>>Num Sensor: 5
D/SensorManager( 4384): ====>>>>>Num Sensor: 6
D/SensorManager( 4384): ====>>>>>Num Sensor: 7
D/SensorManager( 4384): ====>>>>>Num Sensor: 0
E/SensorManager( 4384): ####### akmd2 started!!!
I/ActivityManager( 2829): Displayed activity fahrbot.apps.killswitch/.activities.ConfiguratorPreferenceActivity: 448 ms (total 448 ms)
V/WindowManager( 2829): Delivering toWindow{48f0bef0 fahrbot.apps.killswitch/fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity paused=false}
D/dalvikvm( 4384): GC_EXTERNAL_ALLOC freed 2659 objects / 185288 bytes in 31ms
V/WindowManager( 2829): Delivering toWindow{48f0bef0 fahrbot.apps.killswitch/fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity paused=false}
V/WindowManager( 2829): Delivering toWindow{48f0bef0 fahrbot.apps.killswitch/fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity paused=false}
V/WindowManager( 2829): Delivering toWindow{48f0bef0 fahrbot.apps.killswitch/fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity paused=false}
I/EventLogService( 3073): Aggregate from 1300117279446 (log), 1300117279446 (data)
W/EventLogAggregator( 3073): Unknown tag: contacts_upgrade_receiver
V/AlarmManager( 2829): set: Alarm{48f72778 type 0 com.google.android.gsf}
V/WindowManager( 2829): Delivering toWindow{48f0bef0 fahrbot.apps.killswitch/fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity paused=false}
V/WindowManager( 2829): Delivering toWindow{48f0bef0 fahrbot.apps.killswitch/fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity paused=false}
E/SensorManager( 4384): registerListener 41 LightSensor delay:240
D/Sensors ( 2829): open_input open fd = 98
D/Sensors ( 2829): open_input open fd = 98
D/Sensors ( 2829): open_input leave
D/Sensors ( 2829): accel :: open_input open fd = 99
D/Sensors ( 2829): accel :: open_input open fd = 99
D/Sensors ( 2829): accel :: open_input open fd = 99
D/Sensors ( 2829): open_input_accel leave
D/Sensors ( 2829): gyro :: open_input open fd = 100
D/Sensors ( 2829): open_input_gyro leave
D/Sensors ( 2829): sensors_control_open_data_source: fd_compass=98 fd_accel=99 fd_gyro=100
E/SensorManager( 4384): =======>>>Sensor Thread RUNNING <<<========
D/Sensors ( 4384): event_fd_compass = 38 fd_acc = 39 fd_gyro = 40
D/Sensors ( 2829): sensors_control_activate active=00000012 sensor=00000010 new_sensors=12 changed=0
I/Sensors ( 2829): set AK daemon delay=60 fd=95
E/Sensors ( 2829): +sensors_control_delay: acc ms=60
E/Sensors ( 2829): Write acc delay /sys/class/input/input3/poll_delay <---60
E/Sensors ( 2829): +sensors_control_delay: gyro ms=60
E/Sensors ( 2829): Write gyro delay /sys/class/input/input5/poll_delay <---60
W/SensorManager( 4384): Delay Candidate Listener 0 Sensor:4 delay:240
I/Sensors ( 4384): sensors_data_delay handle=4 delay=240 mMinDelay=240
E/SensorManager( 4384): unregisterListener: [email protected] P1 LightSensor
I/Sensors ( 2829): set AK daemon delay=60 fd=95
E/Sensors ( 2829): +sensors_control_delay: acc ms=60
E/Sensors ( 2829): Write acc delay /sys/class/input/input3/poll_delay <---60
E/Sensors ( 2829): +sensors_control_delay: gyro ms=60
E/Sensors ( 2829): Write gyro delay /sys/class/input/input5/poll_delay <---60
I/Sensors ( 4384): sensors_data_delay handle=4 delay=2147483647 mMinDelay=2147483647
E/SensorManager( 4384): registerListener 41 LightSensor delay:240
D/Sensors ( 2829): sensors_control_activate active=00000012 sensor=00000010 new_sensors=12 changed=0
I/Sensors ( 2829): set AK daemon delay=60 fd=95
E/Sensors ( 2829): +sensors_control_delay: acc ms=60
E/Sensors ( 2829): Write acc delay /sys/class/input/input3/poll_delay <---60
E/Sensors ( 2829): +sensors_control_delay: gyro ms=60
E/Sensors ( 2829): Write gyro delay /sys/class/input/input5/poll_delay <---60
W/SensorManager( 4384): Delay Candidate Listener 0 Sensor:4 delay:240
I/Sensors ( 4384): sensors_data_delay handle=4 delay=240 mMinDelay=240
E/WindowManager( 2829): disableKeyguard() : [email protected] tag==KillSwitch
D/KeyguardViewMediator( 2829): setKeyguardEnabled(false)
W/Sensors ( 4384): report Light 22
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
V/VibratorService( 2829): vibrateImmVibe: 9, magnitude: -1
V/VibratorService( 2829): setVibeStrength = 10000
I/ActivityManager( 2829): Start proc com.android.settings for broadcast com.android.settings/.widget.SettingsAppWidgetProvider: pid=4393 uid=1000 gids={3003, 1015, 2001, 3002, 3001, 1006}
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
I/Zygote ( 4393): Zygote: pid 4393 has INTERNET permission, then set capability for CAP_NET_RAW
I/Zygote ( 4393): Zygote: pid 4393 has CALL PRIVILEGED permission, then set capability for CAP_SYS_ADMIN (21)
D/StatusBar( 2829): manageDisableList what=0x1 pkg=android
D/StatusBar( 2829): DISABLE_EXPAND: yes
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
I/ActivityManager( 2829): No longer want com.osp.app.signin (pid 3310): hidden #16
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
E/WindowManager( 2829): isHomeNeglecting pkgName:fahrbot.apps.killswitch
E/WindowManager( 2829): className:fahrbot.apps.killswitch.activities.ConfiguratorPreferenceActivity
V/WindowManager( 2829): Delivering toWindow{48f098d0 paused=false}
V/WindowManager( 2829): Delivering toWindow{48f098d0 paused=false}
I/ActivityManager( 2829): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10100000 cmp=org.jtb.alogcat/.LogActivity }
D/StatusBar( 2829): manageDisableList what=0x0 pkg=android
D/alogcat ( 4342): stopping ...
D/alogcat ( 4342): canceling periodic saves
V/alogcat ( 4342): started
V/alogcat ( 4342): resumed
D/alogcat ( 4342): starting ...
D/dalvikvm( 2917): GC_EXPLICIT freed 26 objects / 1016 bytes in 63ms
W/InputManagerService( 2829): Starting input on non-focused client [email protected] (uid=10136 pid=4384)
W/Sensors ( 2829): report Light 5
D/PowerManagerService( 2829): onSensorChanged: light value: 5
W/Sensors ( 4384): report Light 5
D/dalvikvm( 3073): GC_EXPLICIT freed 6075 objects / 559920 bytes in 186ms
I/ActivityManager( 2829): Starting activity: Intent { flg=0x10000000 cmp=fahrbot.apps.killswitch/.activities.ScreenOffActivity (has extras) }
W/Process ( 2829): Unable to open /proc/3310/status
V/alogcat ( 4342): save instance
V/alogcat ( 4342): paused
E/WindowManager( 2829): Overwriting rotation value from 0
E/WindowManager( 2829): Overwriting rotation value from 0
D/alogcat ( 4342): stopping ...
D/alogcat ( 4342): stopped
D/alogcat ( 4342): stopping ...
D/alogcat ( 4342): canceling periodic saves
V/alogcat ( 4342): started
D/alogcat ( 4342): starting ...
I/ActivityManager( 2829): Displayed activity fahrbot.apps.killswitch/.activities.ScreenOffActivity: 367 ms (total 367 ms)
D/PowerManagerService( 2829): lightSensorChangedLocked 5
W/Sensors ( 2829): report Light 22
D/PowerManagerService( 2829): onSensorChanged: light value: 22
W/Sensors ( 4384): report Light 22
V/alogcat ( 4342): resumed
W/PowerManagerService( 2829): Timer 0x7->0x3|0x3
I/PowerManagerService( 2829): Ulight 7->3|0
D/PowerManagerService( 2829): lightSensorChangedLocked 22
W/Sensors ( 2829): report Light 5
D/PowerManagerService( 2829): onSensorChanged: light value: 5
D/dalvikvm( 4342): GC_FOR_MALLOC freed 24065 objects / 3041640 bytes in 116ms
W/Sensors ( 4384): report Light 5
D/dalvikvm( 2962): GC_EXPLICIT freed 9058 objects / 480888 bytes in 180ms
I/ActivityManager( 2829): Starting activity: Intent { flg=0x10000000 cmp=fahrbot.apps.killswitch/.activities.ScreenOffActivity (has extras) }
V/alogcat ( 4342): save instance
V/alogcat ( 4342): paused
I/ActivityManager( 2829): Displayed activity fahrbot.apps.killswitch/.activities.ScreenOffActivity: 333 ms (total 333 ms)
D/PowerManagerService( 2829): lightSensorChangedLocked 5
W/Sensors ( 2829): report Light 22
D/PowerManagerService( 2829): onSensorChanged: light value: 22
W/Sensors ( 4384): report Light 22
W/PowerManagerService( 2829): Timer 0x3->0x3|0x0
V/alogcat ( 4342): resumed
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
I/PowerManagerService( 2829): Ulight 3->7|0
V/WindowManager( 2829): Dsptch to Window{48dc34f8 org.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
W/KeyCharacterMap( 4342): No keyboard for id 0
W/KeyCharacterMap( 4342): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
V/WindowManager( 2829): Dsptch to Window{48dc34f8 org.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
V/VibratorService( 2829): vibrateImmVibe: 13, magnitude: -1
V/VibratorService( 2829): setVibeStrength = 10000
V/WindowManager( 2829): Delivering toWindow{48eda210 AtchDlgrg.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}

Yep, that looks like its working as it should... enjoy!

Cheers op!

My pleasure, if you like the app, please rate it on the market and tell your friends!

I am done with the Norwegian translations. I have sent you a pm with the file.

Thank you for the translations! Ill be sending you a free copy in a minute!
And to anyone interested in doing their own translations, dont hesitate to pm me!

ftgg99 said:
Killswitch for tablets and phones
Fahrbot Mobile presents Killswitch, a utility made specifically for devices with cases.
What does Killswitch do?
The app uses a combination of sensors to control the sleep state and screen lock of any device.
At the moment, it uses the proximity sensor, light sensor and accelerometer.
Killswitch has the added advantage of removing your lockscreen via two different methods if you so wish. If you have a case, it really isnt necessary and can be annoying.
Why use Killswitch?
Killswitch will save you battery - putting your device to sleep is as intuitive as shutting your case or turning your phone face down.
All this will use no more power than any Android device does on default settings, as all of the pertinent sensors are already on all the time.
And, of course, Killswitch will show all your ipad and iphone loving mates why android is just that much more awesome
Settings for tablets should look like this:
Enable Killswitch: tick
Admin Permissions: tick
Confirmation time: 10sec
Activation delay: 6sec
No-lock: Disable screen lock
Use proximity: no tick
Use light sensor: tick
Sensitivity: 10%
Use accelerometer: no tick
After upgrading to a newer version, please go into the settings dialog and enable Killswitch again. This is not optimal, but it saves battery and cpu time by removing the necessity for a constantly running service!
Android Market link:
The app is available right now on the Android Market, at an introductory price of $1.99.
https://market.android.com/details?id=fahrbot.apps.killswitch&feature=search_result
Screens:
Click to expand...
Click to collapse
Did a Video Overview of the App. Great App. Great Idea. Works Well on the Xoom.
http://www.youtube.com/watch?v=cUceEI-A8vw

Thank you kindly, we will be subscribing to your channel asap

Network problems on ics based roms

First of all sorry for my bad english , second I have a problem with every CM9 based rom and i tried many , tried to change baseband , ril's but I don't have any idea why is this happening . On every gb ( cm7 or miui ) based rom there's no problem ... to be more precise I have network so it's not that i dont have it at all but it's coming and going from 3g to h to without network than again all the time . thanks in advance

Hi,
please state the ROM you are using right now as well as the baseband and RIL. Makes helping you a lot easier...
Right now I am using ParanoidAndroid (great ROM!) In combination with the 218 BB and RIL. Network reception is good.
Some people report having good network stability with other BBs as well: 725 or the new BBs from 2012. It also depends on the country you are living in and the features your network provider supports. (Fast dormancy, etc,) If you are using CM-ROMs then you should usually use a RIL with version number 10(e.g. v10b)
Last but not least: jumps from 3G to H or E or even G are normal when the area where you are in has bad network coverage.
Hope that helps.
Have a nice day!

Now I'm using WajkIUI 2.5.25 with 725 bb and matching ril ( v10d ) but used cm7 builds without problems too , but when I use the same bb with cm9 ( I tried paranoid , nova hd builds , mr hyde's ... with different kernels ) network comes and goes . Thanks

Hi
Normally try to keep RIL and BB separated from the different versions (GB, ICS etc), same with kernels.
You can try to flash new version of WAJK 2.5.25, which is GB based and work wonderfully on our O2X. When you do so, remember to do full wipe (dalvik, cache and factory reset).
let it work with preinstalled settings, before you start to tweak all these little parts of the engine and remember to reboot a few times.
Remember all developers has carefully described how their specific contributions work, so read read read, then try try and enjoy.
BR
Mike

I missed the point in last post ... WajkIUI ( gb based ) is working just fine , cm7 roms too ... it's ics roms i have problem with . I wrote what rom , bb and ril I'm using at the moment but i would like to find a combination of bb , ril , ics based rom and kernel that has no network issues .

best ROM is always subjective. The one, that I am most fond of and works like a charm is NOVA HD 1.1.0 with the NOVA kernel 3.0.36 pure edition. you will have to experiment with the RIL, but when you have a good match, this ROM works like a charm.
It comes with LG UI 3.0 that is real eyecandy and easy to use.
I find batteryconsumption on this one to be low, which is good.
If you like WAJK and MIUI, bihariel has just released his MIUI v4 2.7.20. It is also a real beauty, though I find it too hard on the battery.
Have fun, finding the ones you like and remember to show your appreciation to the developers, they work for us!
BR
Mike

You can try disable automatic time from system settings. I had similar problem at some point with ICS and after I disabled automatic time is all OK. I use SNTP app to sync my clock.
Sent from my LG-P990 using xda premium

beowolf_46 said:
I missed the point in last post ... WajkIUI ( gb based ) is working just fine , cm7 roms too ... it's ics roms i have problem with . I wrote what rom , bb and ril I'm using at the moment but i would like to find a combination of bb , ril , ics based rom and kernel that has no network issues .
Click to expand...
Click to collapse
Hi beowolf_46!
Just try the following:
Use GetRIL to change your RIL to something different. To 218 v10b for example. Never mind if you are using BB 725 and the RIL does not match. As long as you have access to WLan you can always change it again. Then reboot and check whether your network issues are still present. If they are, then change the RIL again to another one and check again.
In case this doesn't help at all:
Backup your system using recovery. Then change the BB completely to something that might work. I recommend the old 218.
After the BB operation: Enter recovery mode. Then do a full wipe and do not forget to format your system partition too. You can find this in the cwm recovery menu where you can also mount/unmount partitions. Then, without reboot, flash the downloaded ICS-ROM of your choice as well as the newest ICS-GAPPS. At the moment I recommend tonyp's ParanoidAndroid #5 and his GAPPS with Google Now included. Then Reboot. Try to avoid to restore anything from backup solutions like Titanium or MyBackup as this complicates finding the error in your system. Don't make any changes to the system. Just check whether your network problems still exist (with a matching Gingerbread RIL - v10x - of course).
Hope this helps.
Have a nice day!

beowolf_46 said:
First of all sorry for my bad english , second I have a problem with every CM9 based rom and i tried many , tried to change baseband , ril's but I don't have any idea why is this happening . On every gb ( cm7 or miui ) based rom there's no problem ... to be more precise I have network so it's not that i dont have it at all but it's coming and going from 3g to h to without network than again all the time . thanks in advance
Click to expand...
Click to collapse
hello,
your problem is generally known.
this device is made in 2 country's: Germany and Korea.
So if your phone is made in korea, you probably have a korean baseband and RIL
this is what you can do:
>shut your phone down.
>remove the battery.
> if you see "Made in Korea" on the label,
you can try to install a su660 ported baseband and RIL
go to this post if you want more information about Baseband, RIL, etc.
http://forum.xda-developers.com/showthread.php?t=1658047
if you want to try to install the Su660 ported baseband, go to this link:
http://forum.xda-developers.com/showthread.php?t=1500443
BUT I HAVE TO WARN YOU: INSTALLING A SU660 BASEBAND CAN LEAD TO LOSING YOUR IMEI, SO FOLLOW THE STEPS !
And please press the "Thanks" button if you found this verry helpful.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
New on xda, but not new on Android
Sorry for my bad English, i'm Dutch
Donate if my post/reply was very helpful.
I'm saving for a new device
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=2T3CLL6G5VRD4

... under battery it says " made in korea " but i couldn't get signal with any of su bb's and tried all of them ( with matchin ril's ) automatic time was of already , unfortunately . right now im on 218 bb with matching ril , nova hd rebuild 1.1.0 with nova kernel and still have the same issue . I don't think it has anything to do with rom itself as long as it's cm9 based problem is there , all cm7 and gb miui roms work just fine ... thanks guys for all the answers .

Then try to reinstall the whole system and use the format system command from cwm as I described it before. It sounds as if you are carrying your problems with you from one ROM to the next. Full wipe and formatting the system will help you to get rid of these problems.
Have a nice day!

After every bb change I did a full wipe ( reset , dalvik , cache , system and data ) and nova hd has aroma installer that offers full wipe before install so it's double wiped and still the same issue ... I evend turned off saving and restoring things from google servers like passwords and prevented installing previously installed app's from market automatically but same old problem . I formated the internal sd card so theres no files from previous roms and apps but that didn't helped .

OK, you did everything. I get that now. Sorry for bothering you with procedures you already knew.
One last idea: Since your network problems are just appearing on ICS and not on GB ROMs maybe it is apn related. Have you checked the apn file on your system? Something might have changed. Check /system/etc/apns-conf.xml Compare the file from GB with the one from ICS. Search for your provider in the file. See, if something changed there. Best way to do this is on a PC and not on the small screen of your smartphone.
Have a nice day!

... well on miui it's apn's version 6 and on cm9's it's version 7 so it is different although lines for my provider are the same maybe version 6 is somehow better ... is ti possible ( probably not , but ... )

sharvan97 said:
hello,
your problem is generally known.
this device is made in 2 country's: Germany and Korea.
So if your phone is made in korea, you probably have a korean baseband and RIL
this is what you can do:
>shut your phone down.
>remove the battery.
> if you see "Made in Korea" on the label,
you can try to install a su660 ported baseband and RIL
go to this post if you want more information about Baseband, RIL, etc.
http://forum.xda-developers.com/showthread.php?t=1658047
if you want to try to install the Su660 ported baseband, go to this link:
http://forum.xda-developers.com/showthread.php?t=1500443
BUT I HAVE TO WARN YOU: INSTALLING A SU660 BASEBAND CAN LEAD TO LOSING YOUR IMEI, SO FOLLOW THE STEPS !
And please press the "Thanks" button if you found this verry helpful.
Click to expand...
Click to collapse
Under my battery is : Made in brazil.. so wich baseband is good for me?

beowolf_46 said:
First of all sorry for my bad english , second I have a problem with every CM9 based rom and i tried many , tried to change baseband , ril's but I don't have any idea why is this happening . On every gb ( cm7 or miui ) based rom there's no problem ... to be more precise I have network so it's not that i dont have it at all but it's coming and going from 3g to h to without network than again all the time . thanks in advance
Click to expand...
Click to collapse
A couple users are having this problem.
I've been trying to track that down for a while now but as I personally don't suffer from it it isn't easy.
But I recently had a talk with the Eaglesblood team who sent me a fix they did at their ROM.
I passed it to XXMrHyde who has already implemented it into his newest build 15.
Please try that and reply if it fixes the issues for you. So far I got some promising feedback.

Hello tonyp.
This is interesting, indeed. What is the solution EB has provided you with? Even more interesting because of the fact that EB doesn't have the p990 for any tests. What an effort! If you don't mind please share the nature of this fix.
Have a nice day and thank you for your time building and maintaining this very nice ROM of yours.

Raum1807 said:
Hello tonyp.
This is interesting, indeed. What is the solution EB has provided you with? Even more interesting because of the fact that EB doesn't have the p990 for any tests. What an effort! If you don't mind please share the nature of this fix.
Have a nice day and thank you for your time building and maintaining this very nice ROM of yours.
Click to expand...
Click to collapse
I posted that fix here: http://forum.xda-developers.com/showpost.php?p=29590907&postcount=482
The fix basically tells the radio to fully reset it's state if it's stuck during connecting instead of trying over and over again.

Thank you tonyp for all the work you're doing for p990 community ... I'm downloading XXMrHyde's rom now and will try it , fingers crossed . I'll post if it works but thanks in advance .
update : had to restart phone 'cause it lost signal , tryed to put it in airplane mode and than in normal again but had to res ... signal drops are still there but it looks like it's picking it up faster so I can live with it ( 'cause it's not on official rom and i don't expect it to be 100% stable ) but it's not complete fix to this anoying problem .

I'm experiencing a very similar problem, however it only occurs in bihariel's MIUIv4 Rom. Any other ICS based Rom works perfectly. i'll try to give as complete a picture as possible.
The network loss issue occurs in versions v2, v3 and v4. However, it was most prominent in Version 3. I've tried numerous Basebands, have done full wipes and formated the /system partition.
Additionally to the network loss over time ("no service" displayed in the status bar, a few bars on the signal indicator), which sorts itself out over a couple of minutes, or is fixed by a reboot, i lose the signal in the following instances:
whenever i make an outgoing call
when i send a SMS
[*]when i enter *#*#4636#*#* in the dial pad and select phone information*
when i select "3G only" in the network options
An oddity of my operator: "3" or "drei" austria only provides a 3g network. In low coverage regions, the 2g network of T-Mobile austria is used. All of the above issues only occur, when i'm connected with 3's 3g network. When i select 2g only, everything is perfectly fine. So the issue could either be related to the operator(-settings) or the network type.
*Here's a logcat of what happens, when i tap on phone information in the *#*#4636#*#* menu:
Code:
--------- beginning of /dev/log/system
W/InputManagerService( 1636): Window already focused, ignoring focus gain of: [email protected]
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 5(GSM) 16(CDMA)
--------- beginning of /dev/log/main
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(mute=1)
D/CAT ( 1774): CatService: ril message arrived
D/CAT ( 1774): CatService: SESSION END
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 6(GSM) 16(CDMA)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(force unmute)
D/ ( 1107): @@(WM8994)@@ ACWM8994SetPowerMode(), CurrPowerMode = 1, PowerMode = 1
D/TwelveKeyDialer( 4691): Starting query
V/DataCursor( 4691): [0]ms to fillWindow
V/PhoneStatusBar( 1711): setLightsOn(true)
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=10055 pid=4186)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
D/TwelveKeyDialer( 4691): Starting query
V/DataCursor( 4691): [0]ms to fillWindow
D/TwelveKeyDialer( 4691): Starting query
V/DataCursor( 4691): [1]ms to fillWindow
I/ActivityManager( 1636): Start proc com.android.settings for broadcast com.android.settings/.TestingSettingsBroadcastReceiver: pid=4988 uid=1000 gids={1015, 3002, 3001, 3003, 3006, 3007}
I/ActivityThread( 4988): Pub miui_settings: com.android.settings.provider.MiuiSettingsProvider
D/CAT ( 1774): CatService: ril message arrived
D/CAT ( 1774): CatService: SESSION END
I/ActivityManager( 1636): START {act=android.intent.action.MAIN flg=0x10000000 cmp=com.android.settings/.TestingSettings} from pid 4988
D/OpenGLRenderer( 4691): Flushing caches (mode 1)
V/PhoneStatusBar( 1711): setLightsOn(true)
D/libEGL ( 4988): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 4988): loaded /system/lib/egl/libEGL_tegra.so
D/libEGL ( 4988): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/libEGL ( 4988): loaded /system/lib/egl/libGLESv2_tegra.so
D/OpenGLRenderer( 4988): Enabling debug mode 0
I/Process ( 1636): Sending signal. PID: 4988 SIG: 3
I/dalvikvm( 4988): threadid=3: reacting to signal 3
I/dalvikvm( 4988): Wrote stack traces to '/data/anr/traces.txt'
I/ActivityManager( 1636): Displayed com.android.settings/.TestingSettings: +550ms
D/OpenGLRenderer( 4691): Flushing caches (mode 0)
W/SurfaceTexture( 1112): freeAllBuffersExceptCurrentLocked called but mQueue is not empty
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=10000 pid=4691)
D/OpenGLRenderer( 4691): Flushing caches (mode 2)
D/OpenGLRenderer( 4691): Flushing caches (mode 0)
I/ActivityManager( 1636): START {act=android.intent.action.MAIN cmp=com.android.settings/.RadioInfo} from pid 4988
D/OpenGLRenderer( 4988): Flushing caches (mode 1)
D/OpenGLRenderer( 4988): Flushing caches (mode 0)
D/phone ( 1774): updateImsRegRequiredState isImsRegRequired()=false
D/phone ( 1774): updateSmsOverImsState isSmsOverImsEnabled()=false
D/phone ( 1774): updateLteRamDumpState isLteRamDumpEnabled()=false
I/phone ( 1774): [RadioInfo] onResume: register phone & data intents
V/PhoneStatusBar( 1711): setLightsOn(true)
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=1000 pid=4988)
I/ActivityManager( 1636): Displayed com.android.settings/.RadioInfo: +479ms
D/OpenGLRenderer( 4988): Flushing caches (mode 1)
D/ConnectivityService( 1636): ConnectivityChange for mobile: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 1636): Attempting to switch to WIFI
D/ConnectivityService( 1636): Attempting to switch to BLUETOOTH_TETHER
D/NetUtils( 1636): android_net_utils_resetConnections in env=0x18f9458 clazz=0x49f00001 iface=vsnet0 mask=0x3
D/ConnectivityService( 1636): resetConnections(vsnet0, 3)
W/Smack/Packet( 4250): notify conn break (IOEx), close connection
I/qtaguid ( 4250): Failed write_ctrl(u 89) res=-1 errno=22
I/qtaguid ( 4250): Untagging socket 89 failed errno=-22
W/NetworkManagementSocketTagger( 4250): untagSocket(89) failed with errno -22
D/ConnectivityService( 1636): handleInetConditionChange: no active default network - ignore
D/OpenGLRenderer( 4988): Flushing caches (mode 2)
D/OpenGLRenderer( 4988): Flushing caches (mode 0)
D/CAT ( 1774): CatService: ril message arrived
D/CAT ( 1774): CatService: SESSION END
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 7(GSM) 16(CDMA)
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(mute=1)
D/Tethering( 1636): MasterInitialState.processMessage what=3
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 7(GSM) 16(CDMA)
I/ActivityManager( 1636): Start proc com.miui.backup for broadcast com.miui.backup/com.miui.milk.auto.AutoBackupReceiver: pid=5061 uid=9800 gids={1015, 3003}
I/ActivityManager( 1636): Start proc com.cyanogenmod.stats for broadcast com.cyanogenmod.stats/.ReportingServiceManager: pid=5076 uid=10030 gids={3003}
I/dalvikvm( 5076): Turning on JNI app bug workarounds for target SDK version 10...
D/CMStats ( 5076): CONNECTIVITY_ACTION: noConnectivity = true
V/PushService( 4699): onStart() with intent.Action = com.xiaomi.xmsf.push.network_status_changed
E/PushService( 4699): no network, disconnect!
D/AlarmManagerService( 1636): Kernel timezone updated to -120 minutes west of GMT
D/SystemClock( 1774): Setting time of day to sec=1344025625
V/PhoneStatusBar( 1711): setLightsOn(true)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/ActivityManager( 1636): Timeout of broadcast BroadcastRecord{41d24880 com.android.internal.telephony.gprs-reconnect.0} - [email protected], started 10002ms ago
W/ActivityManager( 1636): Receiver during timeout: BroadcastFilter{4151aa48 ReceiverList{41747ca8 1774 com.android.phone/1001 remote:4176c848}}
I/Process ( 1636): Sending signal. PID: 1774 SIG: 3
I/dalvikvm( 1774): threadid=3: reacting to signal 3
I/dalvikvm( 1774): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 1636 SIG: 3
I/dalvikvm( 1636): threadid=3: reacting to signal 3
I/dalvikvm( 1636): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 1711 SIG: 3
I/dalvikvm( 1711): threadid=3: reacting to signal 3
I/dalvikvm( 1711): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 1783 SIG: 3
I/dalvikvm( 1783): threadid=3: reacting to signal 3
I/dalvikvm( 1783): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm( 1636): JIT code cache reset in 4 ms (1048496 bytes 1/0)
D/dalvikvm( 1636): GC_CONCURRENT freed 2511K, 20% free 21232K/26503K, paused 4ms+15ms
D/dalvikvm( 1636): GC_EXPLICIT freed 682K, 20% free 21218K/26503K, paused 3ms+5ms
I/Process ( 1636): Sending signal. PID: 4250 SIG: 3
I/dalvikvm( 4250): threadid=3: reacting to signal 3
I/dalvikvm( 4250): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 4691 SIG: 3
I/dalvikvm( 4691): threadid=3: reacting to signal 3
I/dalvikvm( 4691): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1636): Sending signal. PID: 5061 SIG: 3
I/dalvikvm( 5061): threadid=3: reacting to signal 3
I/dalvikvm( 5061): Wrote stack traces to '/data/anr/traces.txt'
E/ActivityManager( 1636): ANR in com.android.phone
E/ActivityManager( 1636): Reason: Broadcast of Intent { act=com.android.internal.telephony.gprs-reconnect.0 flg=0x14 (has extras) }
E/ActivityManager( 1636): Load: 2.16 / 2.65 / 1.6
E/ActivityManager( 1636): CPU usage from 10030ms to 0ms ago:
E/ActivityManager( 1636): 5.9% 1636/system_server: 4% user + 1.8% kernel / faults: 249 minor 1 major
E/ActivityManager( 1636): 3% 353/ksmd: 0% user + 3% kernel
E/ActivityManager( 1636): 2.9% 1711/com.android.systemui: 2.6% user + 0.2% kernel / faults: 825 minor
E/ActivityManager( 1636): 1.1% 1112/surfaceflinger: 0.6% user + 0.4% kernel / faults: 1 minor
E/ActivityManager( 1636): 0.6% 335/cpufreq-dvfsd: 0% user + 0.6% kernel
E/ActivityManager( 1636): 0.2% 11/kworker/u:1: 0% user + 0.2% kernel
E/ActivityManager( 1636): 0.1% 545/tegra_touch_thr: 0% user + 0.1% kernel
E/ActivityManager( 1636): 0.1% 1107/nvrm_daemon: 0% user + 0.1% kernel
E/ActivityManager( 1636): 0.1% 4250/com.google.process.gapps: 0% user + 0% kernel / faults: 2 minor
E/ActivityManager( 1636): 0% 1052/mmcqd/2: 0% user + 0% kernel
E/ActivityManager( 1636): 0% 1710/motion: 0% user + 0% kernel
E/ActivityManager( 1636): 0% 4652/kworker/0:1: 0% user + 0% kernel
E/ActivityManager( 1636): 15% TOTAL: 7.9% user + 6.4% kernel + 0.3% iowait + 0.3% softirq
E/ActivityManager( 1636): CPU usage from 473ms to 993ms later:
E/ActivityManager( 1636): 7.5% 1636/system_server: 1.8% user + 5.6% kernel / faults: 43 minor
E/ActivityManager( 1636): 5.6% 1651/ActivityManager: 0% user + 5.6% kernel
E/ActivityManager( 1636): 1.8% 1643/Compiler: 0% user + 1.8% kernel
E/ActivityManager( 1636): 1.8% 1894/Binder Thread #: 0% user + 1.8% kernel
E/ActivityManager( 1636): 3.4% 353/ksmd: 0% user + 3.4% kernel
E/ActivityManager( 1636): 1.3% 1052/mmcqd/2: 0% user + 1.3% kernel
E/ActivityManager( 1636): 1.5% 4250/com.google.process.gapps: 1.5% user + 0% kernel / faults: 7 minor
E/ActivityManager( 1636): 1.5% 4250/e.process.gapps: 1.5% user + 0% kernel
E/ActivityManager( 1636): 1.5% 4268/MCS WorkerThrea: 1.5% user + 0% kernel
E/ActivityManager( 1636): 1.5% 4691/android.process.acore: 0% user + 1.5% kernel / faults: 16 minor
E/ActivityManager( 1636): 1.5% 4715/Binder Thread #: 0% user + 1.5% kernel
E/ActivityManager( 1636): 1.5% 5061/com.miui.backup: 1.5% user + 0% kernel / faults: 57 minor
E/ActivityManager( 1636): 92% TOTAL: 9.4% user + 15% kernel + 66% iowait + 1.8% softirq
V/PhoneStatusBar( 1711): setLightsOn(true)
W/ActivityManager( 1636): Force finishing activity com.android.settings/.RadioInfo
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(force unmute)
D/ ( 1107): @@(WM8994)@@ ACWM8994SetPowerMode(), CurrPowerMode = 1, PowerMode = 1
I/ActivityManager( 1636): Killing ProcessRecord{416eceb0 1774:com.android.phone/1001}: user's request
W/InputDispatcher( 1636): channel '422ae660 com.android.settings/com.android.settings.RadioInfo (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 1636): channel '422ae660 com.android.settings/com.android.settings.RadioInfo (server)' ~ Channel is unrecoverably broken and will be disposed!
I/ActivityManager( 1636): Process com.android.phone (pid 1774) has died.
W/ActivityManager( 1636): Scheduling restart of crashed service com.android.stk/.StkAppService in 5000ms
W/ActivityManager( 1636): Scheduling restart of crashed service com.android.phone/.MiuiBluetoothHeadsetService in 15000ms
W/InputDispatcher( 1636): Attempted to unregister already unregistered input channel '422ae660 com.android.settings/com.android.settings.RadioInfo (server)'
I/WindowManager( 1636): WIN DEATH: Window{422ae660 com.android.settings/com.android.settings.RadioInfo paused=true}
D/LBE-Sec ( 2033): Service lbesec.loader.com.android.phone is dead
I/ServiceManager( 1104): service 'sip' died
I/ServiceManager( 1104): service 'simphonebook' died
I/ServiceManager( 1104): service 'isms' died
I/ServiceManager( 1104): service 'phone' died
I/ServiceManager( 1104): service 'iphonesubinfo' died
I/WindowManager( 1636): WINDOW DIED Window{422ae660 com.android.settings/com.android.settings.RadioInfo paused=true}
D/LBE-Sec ( 2033): Unable to locate com.android.phone, retry in 5 seconds
I/ActivityManager( 1636): Start proc com.android.phone for restart com.android.phone: pid=5110 uid=1001 gids={3002, 3001, 3003, 1015}
V/PhoneStatusBar( 1711): setLightsOn(true)
I/ActivityManager( 1636): Start proc com.android.calendar for broadcast com.android.calendar/.widget.CalendarAppWidgetService$CalendarFactory: pid=5122 uid=10006 gids={3003}
W/InputManagerService( 1636): Got RemoteException sending setActive(false) notification to pid 1774 uid 1001
I/ActivityThread( 5110): Pub telephony: com.android.providers.telephony.TelephonyProvider
W/TelephonyProvider( 5110): onCreate: confFile=/system/etc/apns-conf.xml oldCheckSum=-1
I/ActivityThread( 5110): Pub firewall: com.android.providers.telephony.FirewallProvider
I/ActivityThread( 5110): Pub mms: com.android.providers.telephony.MmsProvider
I/ActivityThread( 5122): Pub com.android.calendar.CalendarRecentSuggestionsProvider: com.android.calendar.CalendarRecentSuggestionsProvider
I/ActivityManager( 1636): Start proc com.android.providers.calendar for content provider com.android.providers.calendar/.CalendarProvider2: pid=5142 uid=10007 gids={3003, 1015}
D/MmsSmsDatabaseHelper( 5110): [MmsSmsDb] tableName: threads hasAutoIncrement: CREATE TABLE threads (_id INTEGER PRIMARY KEY AUTOINCREMENT,date INTEGER DEFAULT 0,message_count INTEGER DEFAULT 0,unread_count INTEGER DEFAULT 0,recipient_ids TEXT,snippet TEXT,snippet_cs INTEGER DEFAULT 0,read INTEGER DEFAULT 1,type INTEGER DEFAULT 0,error INTEGER DEFAULT 0,has_attachment INTEGER DEFAULT 0) result: true
D/MmsSmsDatabaseHelper( 5110): [MmsSmsDb] tableName: canonical_addresses hasAutoIncrement: CREATE TABLE canonical_addresses (_id INTEGER PRIMARY KEY AUTOINCREMENT,address TEXT) result: true
D/MmsSmsDatabaseHelper( 5110): [getWritableDatabase] hasAutoIncrementThreads: true hasAutoIncrementAddresses: true
I/ActivityThread( 5110): Pub sms: com.android.providers.telephony.SmsProvider
I/ActivityThread( 5110): Pub mms-sms: com.android.providers.telephony.MmsSmsProvider
I/ActivityThread( 5142): Pub com.android.calendar: com.android.providers.calendar.CalendarProvider2
I/ActivityThread( 5110): Pub icc: com.android.phone.MiuiIccProvider
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type default,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type mms,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type supl,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type dun,current state IDLE
D/ ( 5110): [ApnContext] set reason as dataEnabled, for type hipri,current state IDLE
D/CAT ( 5110): CatService: Running CAT service. STK app installed:true
D/CAT ( 5110): CatService: NEW sInstance
D/CallManager( 5110): registerPhone(GSM Handler (com.android.internal.telephony.PhoneProxy) {41535fd8})
W/ActivityManager( 1636): Unable to start service Intent { act=com.android.ussd.IExtendedNetworkService }: not found
I/ActivityManager( 1636): Start proc com.android.deskclock for broadcast com.android.deskclock/.AlarmInitReceiver: pid=5187 uid=10013 gids={}
D/CAT ( 5110): CatService: SIM ready. Reporting STK service running now...
D/NetworkLocator( 4250): null cell state delivered
D/Bluetooth HSHFP( 5110): Starting BluetoothHeadsetService
D/CAT ( 5110): CatService: ril message arrived
D/CAT ( 5110): CatService: SESSION END
D/MccTable( 5110): updateMccMncConfiguration: mcc=232, mnc=10
D/MccTable( 5110): locale set to de_at
D/MccTable( 5110): WIFI_COUNTRY_CODE set to at
I/WifiService( 1636): WifiService trying to set country code to at with persist set to true
I/ActivityThread( 5187): Pub com.android.deskclock: com.android.deskclock.AlarmProvider
D/dalvikvm( 1636): GC_EXPLICIT freed 1775K, 21% free 21163K/26503K, paused 3ms+8ms
V/AlarmClock( 5187): AlarmInitReceiver finished
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
I/ActivityManager( 1636): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.miui.home/.launcher.Launcher} from pid 1636
D/PhoneStatusBar( 1711): disable: < expand icons alerts ticker system_info back home recent clock >
D/OpenGLRenderer( 4988): Flushing caches (mode 0)
V/PhoneStatusBar( 1711): setLightsOn(true)
D/OpenGLRenderer( 4988): Flushing caches (mode 1)
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=1000 pid=4988)
V/SipBroadcastReceiver( 5110): start auto registration
D/CAT ( 5110): CatService: Return current sInstance
I/CalendarProvider2( 5142): Sending notification intent: Intent { act=android.intent.action.PROVIDER_CHANGED dat=content://com.android.calendar }
W/ContentResolver( 5142): Failed to get type for: content://com.android.calendar (Unknown URL content://com.android.calendar)
D/CAT ( 5110): CatService: ril message arrived
D/CAT ( 5110): CatService: SESSION END
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(mute=1)
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 4(GSM) 16(CDMA)
D/LBE-Sec ( 2033): Injecting to com.android.phone at pid 5110
D/LBE-Sec ( 2033): Attached to process 5110, original registers
D/LBE-Sec ( 2033): Info: current register set:
D/LBE-Sec ( 2033): R0 =0xFFFFFFFC R1 =0xBEB664F8 R2 =0x00000010 R3 =0x000018F3
D/LBE-Sec ( 2033): R4 =0x0173B1F8 R5 =0x0173B20C R6 =0x00000000 R7 =0x000000FC
D/LBE-Sec ( 2033): R8 =0x00000000 R9 =0x00000014 R10=0x00000000 R11=0xBEB6668C
D/LBE-Sec ( 2033): R12=0x4013C264 SP =0xBEB664D0 LR =0x4013440B PC =0x40033520
D/LBE-Sec ( 2033): CPSR =0x20030010 Orig_R0 =0x00000027
D/LBE-Sec ( 2033): Allocated memory located at 0x50f7a000
D/LBE-Sec ( 2033): Info: new SP for inject code 0x50F7DC00
D/LBE-Sec ( 2033): Injected registers
D/LBE-Sec ( 2033): Info: current register set:
D/LBE-Sec ( 2033): R0 =0xFFFFFFFC R1 =0xBEB664F8 R2 =0x00000010 R3 =0x000018F3
D/LBE-Sec ( 2033): R4 =0x0173B1F8 R5 =0x0173B20C R6 =0x00000000 R7 =0x000000FC
D/LBE-Sec ( 2033): R8 =0x00000000 R9 =0x00000014 R10=0x00000000 R11=0xBEB6668C
D/LBE-Sec ( 2033): R12=0x4013C264 SP =0x50F7DC00 LR =0x4013440B PC =0x50F7DC00
D/LBE-Sec ( 2033): CPSR =0x20030010 Orig_R0 =0x00000027
I/LBE-Sec ( 5110): Successfully loaded from remote process 2033
D/LBE-Sec ( 1104): Added loader service lbesec.loader.com.android.phone, handle 74
I/LBE-Sec ( 5110): bootstrap loaded
D/LBE-Sec ( 2033): Done.
D/StatusBar.NetworkController( 1711): updateTelephonySignalStrength: mSignalStrength == 3(GSM) 16(CDMA)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
D/SystemClock( 5110): Setting time of day to sec=1344025648
W/NvAudioDevice( 1115): @@(Device.cpp-hal)@@ setOutputMute(force unmute)
D/ ( 1107): @@(WM8994)@@ ACWM8994SetPowerMode(), CurrPowerMode = 1, PowerMode = 1
D/PhoneStatusBar( 1711): disable: < expand icons alerts ticker system_info back home recent clock >
D/OpenGLRenderer( 1802): Flushing caches (mode 1)
D/LBE-Sec ( 2033): Registered death notification for lbesec.loader.com.android.phone
D/LBE-Sec ( 2033): notification dead
D/LBE-Sec ( 2033): Injection success
D/OpenGLRenderer( 1802): Flushing caches (mode 0)
W/SurfaceTexture( 1112): freeAllBuffersExceptCurrentLocked called but mQueue is not empty
D/dalvikvm( 1802): GC_EXPLICIT freed 26K, 7% free 21448K/22855K, paused 2ms+33ms
W/InputManagerService( 1636): Starting input on non-focused client [email protected] (uid=10033 pid=1802)
V/PhoneStatusBar( 1711): setLightsOn(true)
W/HapticFeedbackUtil( 1636): vibrate: null or empty pattern
D/LBE-Sec ( 1636): getcache uid=10055 pid=0 perm=6 map=0x00000000 action=0
D/ ( 5303): 10026 com.lbe.security.miui executing 0 /system/bin/sh
I/InputQueue-JNI( 4186): Sending finished signal for input channel '41705918 AtchDlg:org.jtb.alogcat/org.jtb.alogcat.LogActivity (client)' since it is being unregistered while an input message is still in progress.
I/InputQueue-JNI( 4186): Ignoring finish signal on channel that is no longer registered.
W/InputManagerService( 1636): Window already focused, ignoring focus gain of: [email protected]
*EDIT: oh, and com.android.phone dies
I hope the information was somewhat usefull
Cheers

LG 4x HD - CM11 - Gyroscope, rotation, accel., Magnetic sensor not working

Hey guys. I need some help with my phone. I have LG 4x HD and few days ago I flashed CM11 SNAPSHOT M10. I really like this OS and I'm amazed how fast it is (compared to stock JB from LG), but I noticed my GPS won't lock on satellites. After I compared my GPS status results with my sister's stock LG 4X test results (which were pretty much the same as mine) I got to a conclusion that there's probably no "signal" for gps to lock.
While I was running this test, I noticed something else. Her compass was showing correctly while mine was just sitting in place, not rotating what so ever. I also noticed my gyroscope isn't working, nor screen rotation or even magnetic sensor.
To answer some of your questions you might ask:
Did you do factory reset?
Yes, I did factory reset, wiped data, wiped cache, wiped dalvik, flashed ROM for 3 more times. Nothing's changed.
Did you do a clean install?
Once I had CM10 installed (like a year ago), but I restored my phone back to stock after a month or so. After a year, since I restored my phone, I installed CM11. I deleted data, cache and dalvik before installing it
Did gyroscope, accel., compass, etc. work before you installed CM11?
I'm pretty sure they worked. Since screen rotation worked and I havent noticed any other issues.
So, would you guys know what could be done to fix those problems? And no, I dont want to go back to STOCK.

ALSO:
I checked /sys/devices/ and I cant find Gyroscope folder. I did /format/system and restored stock OS but nothing has changed. Gyroscope still doesnt work (I still can't find gyroscop folder, even on stock OS). This issue is getting really annoying so I'd really ask you if we can resolve it asap. thanks

BTW, After installing latest CM11 NIGHTLY from 27.10.2014, sensors worked again. Next morning, they stopped working?
Is there really no one that might have a clue what the hell is going on with my phone?

wort11 said:
BTW, After installing latest CM11 NIGHTLY from 27.10.2014, sensors worked again. Next morning, they stopped working?
Is there really no one that might have a clue what the hell is going on with my phone?
Click to expand...
Click to collapse
Give logs or better send your phone to service center

LGaljo said:
Give logs or better send your phone to service center
Click to expand...
Click to collapse
Where can I find logs? And since my warranty is void, I'm not spending a dollar for repair.

wort11 said:
Where can I find logs? And since my warranty is void, I'm not spending a dollar for repair.
Click to expand...
Click to collapse
Use app syslog (https://play.google.com/store/apps/details?id=com.tortel.syslog) save log while using app where sensors doesn't work and post it here. I might take a look but I am no a developer.
I didn't pay anything when my audio jack stopped working and I have unlocked and rooted phone. I had just reflashed official JB rom. EDIT: and they repleaced whole motherboard

LGaljo said:
Use app syslog (https://play.google.com/store/apps/details?id=com.tortel.syslog) save log while using app where sensors doesn't work and post it here. I might take a look but I am no a developer.
I didn't pay anything when my audio jack stopped working and I have unlocked and rooted phone. I had just reflashed official JB rom. EDIT: and they repleaced whole motherboard
Click to expand...
Click to collapse
Here, I ran syslog while using CPU-Z. Modemlog is not included because it warned me it may include IMEI or phone number in it.

wort11 said:
Here, I ran syslog while using CPU-Z. Modemlog is not included because it warned me it may include IMEI or phone number in it.
Click to expand...
Click to collapse
Code:
10-29 21:47:00.396 E/SensorService( 530): Error activating sensor 0 (Invalid argument)
10-29 21:47:00.406 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.406 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.406 D/Sensors ( 530): Sensor_enable:1 1
10-29 21:47:00.406 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.406 E/SensorService( 530): Error activating sensor 1 (Invalid argument)
10-29 21:47:00.406 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.406 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.406 D/Sensors ( 530): Sensor_enable:2 1
10-29 21:47:00.406 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.406 E/SensorService( 530): Error activating sensor 2 (Invalid argument)
10-29 21:47:00.406 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.406 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.406 D/Sensors ( 530): Sensor_enable:3 1
10-29 21:47:00.406 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.406 E/SensorService( 530): Error activating sensor 3 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:4 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 4 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:5 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 5 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:6 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 6 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:7 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 7 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:10 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 10 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/ProximitySensor( 530): ProximitySensor-enable EN(1), newState(1),mEnabled(0)
10-29 21:47:00.416 V/ProximitySensor( 530): [PROX]APDS PROX SET ENABLE: flags = 1
10-29 21:47:00.426 W/ProximitySensor( 530): ProximitySensor-[setInitialState], value(0.000000)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.416 D/ProximitySensor( 530): ProximitySensor-enable EN(1), newState(1),mEnabled(0)
10-29 21:47:00.416 V/ProximitySensor( 530): [PROX]APDS PROX SET ENABLE: flags = 1
10-29 21:47:00.426 W/ProximitySensor( 530): ProximitySensor-[setInitialState], value(0.000000)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:04.166 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:04.166 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:04.166 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:04.166 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:04.166 D/ProximitySensor( 530): ProximitySensor-enable EN(0), newState(0),mEnabled(1)
10-29 21:47:04.166 V/ProximitySensor( 530): [PROX]APDS PROX SET ENABLE: flags = 0
10-29 21:47:04.166 W/ProximitySensor( 530): ProximitySensor-[setInitialState], value(0.000000)
This is the thing you can read from logcat...

LGaljo said:
Code:
10-29 21:47:00.396 E/SensorService( 530): Error activating sensor 0 (Invalid argument)
10-29 21:47:00.406 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.406 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.406 D/Sensors ( 530): Sensor_enable:1 1
10-29 21:47:00.406 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.406 E/SensorService( 530): Error activating sensor 1 (Invalid argument)
10-29 21:47:00.406 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.406 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.406 D/Sensors ( 530): Sensor_enable:2 1
10-29 21:47:00.406 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.406 E/SensorService( 530): Error activating sensor 2 (Invalid argument)
10-29 21:47:00.406 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.406 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.406 D/Sensors ( 530): Sensor_enable:3 1
10-29 21:47:00.406 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.406 E/SensorService( 530): Error activating sensor 3 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:4 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 4 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:5 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 5 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:6 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 6 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:7 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 7 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/Sensors ( 530): Sensor_enable:10 1
10-29 21:47:00.416 E/Sensors ( 530): mInitSuccess=0
10-29 21:47:00.416 E/SensorService( 530): Error activating sensor 10 (Invalid argument)
10-29 21:47:00.416 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.416 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:00.416 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:00.416 D/ProximitySensor( 530): ProximitySensor-enable EN(1), newState(1),mEnabled(0)
10-29 21:47:00.416 V/ProximitySensor( 530): [PROX]APDS PROX SET ENABLE: flags = 1
10-29 21:47:00.426 W/ProximitySensor( 530): ProximitySensor-[setInitialState], value(0.000000)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.416 D/ProximitySensor( 530): ProximitySensor-enable EN(1), newState(1),mEnabled(0)
10-29 21:47:00.416 V/ProximitySensor( 530): [PROX]APDS PROX SET ENABLE: flags = 1
10-29 21:47:00.426 W/ProximitySensor( 530): ProximitySensor-[setInitialState], value(0.000000)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:00.426 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:04.166 V/Sensors ( 530): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
10-29 21:47:04.166 V/Sensors ( 530): int sensors_poll_context_t::setDelay(int, int64_t)
10-29 21:47:04.166 V/Sensors ( 530): int poll__activate(sensors_poll_device_t*, int, int)
10-29 21:47:04.166 V/Sensors ( 530): int sensors_poll_context_t::activate(int, int)
10-29 21:47:04.166 D/ProximitySensor( 530): ProximitySensor-enable EN(0), newState(0),mEnabled(1)
10-29 21:47:04.166 V/ProximitySensor( 530): [PROX]APDS PROX SET ENABLE: flags = 0
10-29 21:47:04.166 W/ProximitySensor( 530): ProximitySensor-[setInitialState], value(0.000000)
This is the thing you can read from logcat...
Click to expand...
Click to collapse
and these values mean what?

wort11 said:
and these values mean what?
Click to expand...
Click to collapse
Something is wrong, while sensors are being activated. I can't help I don't know. I really suggest you to send it to service centre. This is one of a kind error here...

Thank you for your time and help. BTW, do you know if if do "Upgrade Recovery" in LG Mobile support software, does my bootloader gets locked, and phone rooted again? does it install stock recovery tool (uninstalls CWM)?

wort11 said:
Thank you for your time and help. BTW, do you know if if do "Upgrade Recovery" in LG Mobile support software, does my bootloader gets locked, and phone rooted again? does it install stock recovery tool (uninstalls CWM)?
Click to expand...
Click to collapse
It gets to the state like it was when you bought it and bootloader stays unlocked.

Thanks!

[Q&A][ROM][6.0] CyanogenMod 13 - Unofficial CyanogenMod 13

Q&A for [m7] Unofficial CyanogenMod 13 / Official CyanogenMod 12.1 Nightlies
As I have searched Original Android Development and Q&A forums and haven't found nothing about the thread above and questions related to it, so creating this one. Please use search before posting in here.

cm-13.0-20151219-UNOFFICIAL-m7 bugs
Hi,
A few things about "Unofficial CyanogenMod 13" for HTC One M7 Int. (cm-13.0-20151219-UNOFFICIAL-m7)
1. Cannot change preferred network type from "LTE (recommended)" to 3G or 2G. If I try, it just closes the choice window and that's it. Here is logcat for each choice:
a) 3G:
12-21 09:59:24.642 W/InputMethodManagerService( 602): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-21 09:59:24.643 D/NetworkSettings( 1354): onPreferenceChange
12-21 09:59:24.643 D/NetworkSettings( 1354): buttonNetworkMode: 0
12-21 09:59:24.643 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:24.666 D/NetworkSettings( 1354): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
12-21 09:59:24.666 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:24.666 D/NetworkSettings( 1354): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
12-21 09:59:24.666 D/NetworkSettings( 1354): isWorldMode=false
12-21 09:59:24.723 W/System ( 1088): ClassLoader referenced unknown path: /system/framework/tcmclient.jar
Click to expand...
Click to collapse
b) 2G:
12-21 09:59:30.415 W/InputMethodManagerService( 602): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-21 09:59:30.416 D/NetworkSettings( 1354): onPreferenceChange
12-21 09:59:30.419 D/NetworkSettings( 1354): buttonNetworkMode: 1
12-21 09:59:30.420 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:30.440 D/NetworkSettings( 1354): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
12-21 09:59:30.440 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:30.440 D/NetworkSettings( 1354): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
12-21 09:59:30.440 D/NetworkSettings( 1354): isWorldMode=false
Click to expand...
Click to collapse
c) LTE (the same as marked):
12-21 09:59:36.671 W/InputEventReceiver( 1354): Attempted to finish an input event but the input event receiver has already been disposed.
12-21 09:59:36.677 W/InputMethodManagerService( 602): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-21 09:59:36.678 D/NetworkSettings( 1354): onPreferenceChange
12-21 09:59:36.678 D/NetworkSettings( 1354): buttonNetworkMode: 9
12-21 09:59:36.678 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
Click to expand...
Click to collapse
2. Get random reboots. One thing I noticed, I get rebooted somewhere about the time when "SMS Backup and Restore" runs a scheduled backup. I get somewhere about 1-3 reboots per days as much as I have been using this ROM.

cm-13.0-20151219-UNOFFICIAL-m7 random reboots
A minute ago happened a random reboot, here's the output of logcat:
12-21 12:56:14.583 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:56:26.837 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:56:36.862 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:56:56.846 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:57:07.062 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:58:34.807 I/perfprofd( 233): initiating profile collection
12-21 12:58:34.844 W/perfprofd( 233): type=1400 audit(0.0:9): avc: denied { write } for name="property_service" dev="tmpfs" ino=7181 scontext=u:rerfprofd:s0 tcontext=ubject_rroperty_socket:s0 tclass=sock_file permissive=0
12-21 12:58:34.858 E/perfprofd( 233): setprop ctl.stop mpdecision failed
Click to expand...
Click to collapse

accesspc said:
A minute ago happened a random reboot, here's the output of logcat:
Click to expand...
Click to collapse
As a workaround done this:
Code:
adb shell su -c setenforce 0
And since then - no more reboots. As a result found these AVC message in DMESG:
Code:
adb shell dmesg | grep -i avc
[33691.839812] type=1400 audit(1450776153.729:35): avc: denied { write } for pid=232 comm="perfprofd" name="property_service" dev="tmpfs" ino=7215 scontext=u:rerfprofd:s0 tcontext=ubject_rroperty_socket:s0 tclass=sock_file permissive=1
[33691.840362] type=1400 audit(1450776153.729:36): avc: denied { connectto } for pid=232 comm="perfprofd" path="/dev/socket/property_service" scontext=u:rerfprofd:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket permissive=1
Click to expand...
Click to collapse
Anybody? Help?

accesspc said:
As a workaround done this:
Code:
adb shell su -c setenforce 0
And since then - no more reboots. As a result found these AVC message in DMESG:
Code:
adb shell dmesg | grep -i avc
Anybody? Help?
Click to expand...
Click to collapse
Seems to be this has been fixed in cm-13.0-20151223-UNOFFICIAL-m7.zip build - no more random reboots, but Preferred network type still can't be changed...

Hello
How smooth is it with this rom?

sacaitu said:
How smooth is it with this rom?
Click to expand...
Click to collapse
Hi, the rom is really quite good, only bugs that I have noticed were:
* after fresh install of Facebook and Messenger they force closed - need to start each app at least once, then delete these files:
** /data/data/com.facebook.katana/lib-xzs/libssl*
** /data/data/com.facebook.orca/lib-xzs/libss*
* Still cannot change Preferred network type, either via settings menu, nor via dialpad *#*#4636#*#*. This is set to auto LTE/3G/2G, which drains battery a lot if connection is not stable (many handovers or switching between LTE and 3G)
Other than that - awesome, fast, pretty

Just installed cm-13.0-20160103-UNOFFICIAL-m7 from http://forum.xda-developers.com/showpost.php?p=64632124&postcount=129.
Installation sequence:
1. TWRP -> Wipe -> Advanced: Dalvik Cache, Cache and System
2. Install cm-13.0-20160103-UNOFFICIAL-m7.zip
3. Install open_gapps-arm-6.0-nano-20151225.zip
4. Flash boot.img from cm-13.0-20160103-UNOFFICIAL-m7.zip
Issues that still persist:
* Flashligh FCs after a few seconds from start
* Camera FCs after picture taken, video capture works fine
* Preferred network type cannot be changed, get the same error as before
Haven't tested Facebook and Messenger, as I did not do a full wipe.

How is the battery life? CM is notorious for bad battery life on this device.
With 5.1 GPE ROM, m7 has a very good battery life, with about 2% per hour drain with normal day use and 0.5% per hour drain at idle at night. Does this ROM close to that?
Also, did you collect logcat for those FCs?

I haven't tested the battery life a lot, because before this CM I was using stock latest rom, so the battery drain is about the same, might tell you more tomorrow.
As for Force Closes, here are logcats (to not clutter the forum, put all logs to pastebin:
Flashlight:
1st try: http://pastebin.com/kE1vvdkd
2ndtry: http://pastebin.com/n5WizzmS
Camera:
1st try: http://pastebin.com/HzLXJVKv
Preferred network type change:
To LTE (the same as selected):
Code:
01-05 12:05:53.466 W/InputEventReceiver( 1379): Attempted to finish an input event but the input event receiver has already been disposed.
01-05 12:05:53.467 W/InputMethodManagerService( 620): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
01-05 12:05:53.473 D/NetworkSettings( 1379): onPreferenceChange
01-05 12:05:53.473 D/NetworkSettings( 1379): buttonNetworkMode: 9
To 3G:
Code:
01-05 12:06:04.297 W/InputEventReceiver( 1379): Attempted to finish an input event but the input event receiver has already been disposed.
01-05 12:06:04.298 W/InputMethodManagerService( 620): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
01-05 12:06:04.307 D/NetworkSettings( 1379): onPreferenceChange
01-05 12:06:04.308 D/NetworkSettings( 1379): buttonNetworkMode: 0
01-05 12:06:04.360 D/NetworkSettings( 1379): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
01-05 12:06:04.372 D/NetworkSettings( 1379): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
01-05 12:06:04.372 D/NetworkSettings( 1379): isWorldMode=false
To 2G:
Code:
01-05 12:06:08.476 W/InputMethodManagerService( 620): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
01-05 12:06:08.476 D/NetworkSettings( 1379): onPreferenceChange
01-05 12:06:08.482 D/NetworkSettings( 1379): buttonNetworkMode: 1
01-05 12:06:08.508 D/NetworkSettings( 1379): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
01-05 12:06:08.521 D/NetworkSettings( 1379): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
01-05 12:06:08.522 D/NetworkSettings( 1379): isWorldMode=false

devsk said:
How is the battery life? CM is notorious for bad battery life on this device.
With 5.1 GPE ROM, m7 has a very good battery life, with about 2% per hour drain with normal day use and 0.5% per hour drain at idle at night. Does this ROM close to that?
Also, did you collect logcat for those FCs?
Click to expand...
Click to collapse
Now that you asked about battery drain, I measured about 30 % drop (from 100%) in 12 hours (7 normal usage and 5 night time) which equals to 2,5% per hour. That isn't bad, considering that WiFi always on, made a few calls, used GPS for about 15 minutes, Titanium backup ran at night (backing up 5 Apps) and SMS Backup & Restore at night. Oh, and 5 alarms early in the morning.