Database Users

[Q] changing radio and kernels

hello
i am hoping someone can point me in the right direction.
after installing "no signal alert" from the market.
i found my signal would drop anywhere from 4secs-30+secs and come back every minute or so it would repeat this randomly as far as i can tell. it seems to be the cause of my high battery drain.
i have a strong -63dbm reception here.
so i have been changing radios to see if i can notice a difference,
however i am confused as to if the type of kernel would react differently with the radios? does the kernel tell the radio what to do, or does the kernel just react on what the radio is saying?
i hope this question makes sense to someone else

i just edited my sig,
but i am trying to run
[02.MAR.2011][CWM]TyphooN CyanogenMod 7 v2.4.5[GRI40/2.3.3/RC1+][A2SD/RAM][tytung r6]
i have also tried different kernels before trying to change radios and they all seemed to have a similar result

sounds like youre having the same problem i was having. im also running Typhoon with the tytung r6 kernel and 2.15 radio. try what i posted in this link... it gave me almost perfect reception everywhere and dropped my time withot signal from 76% to 4%
http://forum.xda-developers.com/showthread.php?t=975282

thanks
i did see that post, i didnt want to sacrifice using 2g speed as i use data a lot,
but maybe thats what ill try just to have a decent battery.

so i have noticed some things and wanted any input as to what could be the problem?
When in an area with 3g the phone will loose signal and do this constant data loss/reconnect as mentioned above
however when in an area where 3g isnt avialable and im using edge network i dont seem to have any problem with data loss and my problem goes away. this is the same when i am on wifi
i did a logcat where i have good signal (but i dont have a copy of it at the moment) and the problem is occuring, i cant remeber exactly what it said
but something to the sort of
"phonydialer....... rmnet=0 ...=null.......disconnect"
i know thats a awfull description and i hope to post a logcat of it tomorrow.
can anyone tell me how things work as far as radio and kernels and 3g data and maybe what area i could research to narrow down to possible be the cause?

the radio is probably switching between hsdpa and regular 3g, each time it does so it disconnects and reconnects, with the radio on full power, hence teh signal drop and battery use. (At least this was my conclusions on a winmo rom, i assume the radio works the same regardless of the OS)
I turned off hsdpa (again this was on winmo) and i still got 3g, but never H, and teh signal became much mroe stable.
also, i noticed this behavour was far more pronounced in the later radios, 2.14 and .15.
Im now using 2.11.50 with typhoon and all seems well.

man i see talk about this everywhere and ive tried a few times to bring it up to some devs who always shoot down the idea that theres an issue.. but i have a theory.. does anyone have these issues on roms that use ppp and not rmnet? cause i remember that the only way that cotulla was able to get rmnet working on android with magldr was by inserting a chunk of code form the desires radio into magldr to enable rmnet to work, i wonder what the chances are that just maybe, that little bit of code doesnt work 100% stable and causes signal and data issues... hmmm?
It seems to be a common thing amongst all roms ( i dont know about ones that use ppp and not rmnet, which in theory would bypass the rmnet code inserted into magldr) so anyone think there might be the possibility of something going on with that?

adb logcat
D/SystemClock( 337): Setting time of day to sec=1299149817
D/dalvikvm( 219): GC_EXTERNAL_ALLOC freed 299K, 46% free 5698K/10375K, external 5009K/5146K, paused 75ms
I/TelephonyRegistry( 219): notifyServiceState: 1 home null null null Unknown C
SS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 219): notifyDataConnection: state=2 isDataConnectivityPossible=false reason=null interfaceName=rmnet0networkType=0
I/TelephonyRegistry( 219): notifyServiceState: 1 home null null null Unknown C
SS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 219): notifyDataConnection: state=2 isDataConnectivityPoss
ible=false reason=null interfaceName=rmnet0 networkType=0
I/TelephonyRegistry( 219): notifyServiceState: 0 home null null null HSDPA CSS
not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 219): notifyDataConnection: state=2 isDataConnectivityPoss
ible=true reason=null interfaceName=rmnet0 networkType=8
this seems to be the cause of signal loss/ reconnect
anyone have any more input?

[Q] "Dim of death"

Has anyone experienced, what I'm calling the "Dim of death"?
Basically, it only seems to happen in the browser. Things will seem ok and then the screen will go dim... basically the device freezes, but not completely. For example, I can return to the lock screen, but cannot enter my lock pattern. Pressing "play" on my bluetooth keyboard will start up a song.
The problem is, there's no recovery from the "dim of death" other than to restart the device. It's the only reason why I have to restart my transformer and the one thing that makes me affraid to use the stock browser (which I do only if I need to play flash content)
Anyone else have this problem?
Sent from my Transformer TF101 using XDA Premium App

Among all the build quality issues I have also had this too. One more reason besides light bleed dust under screen and under camera glass and bad creaking with raIr sharp ports, to send it back.

Canadoc said:
Among all the build quality issues I have also had this too. One more reason besides light bleed dust under screen and under camera glass and bad creaking with raIr sharp ports, to send it back.
Click to expand...
Click to collapse
That's a little extreme. Light bleed and dust ARE legitimate warranty issues. The rest is not really that much of a problem, unless you're looking for a reason to *****.
I have no light bleed or dust under the screen. I do have a small creaking and the occasional "dim of death". I wouldn't dream of returning this device for that.

woah! I think you guys are missunderstanding what I wrote. When the browser "crashes" the entire screen goes dim... it's a software thing and the OS becomes unresponsive. I'm not talking about dust or light bleed! LOL
Sent from my Transformer TF101 using XDA Premium App

Backlight Bug?
I have seen something similar, but not in the browser... there are times where the unit seems to lock up, but music will continue to play, and if I hit the "home" button (which isn't visible, but you can kind of guess where it is), you can VERY VAGUELY see the home screen (especially the weather lettering). You can also 'swipe' sideways from screen to screen.
I can usually duplicate this problem by adjusting the brightness, which seems to turn off the backlight (but the device is still running - you just can't see what's on the screen). Setting the brightness to "auto" seems to help a little bit.
Also, when I do a "reset", the startup display screens show properly but it will usually not startup properly - the backlight is still off. A reliable fix for me, though, is to plug the device in to charge and restart, which seems to work every time.
I'm really torn on this... this is getting very frustrating and I'm not sure whether to RMA (who knows how long that will take) or wait for a fix... (the fact that the display screens illuminate properly make me think that it's not a hardware issue...)

Do you guys have it set to auto brightness? I have it set to manual and have never seen this yet (knock on wood).

Kilmar said:
Do you guys have it set to auto brightness? I have it set to manual and have never seen this yet (knock on wood).
Click to expand...
Click to collapse
Yes, I've got mine set to auto, but I believe the dimming is more related to the OS crashing more than anything else. I just avoid the stock browser and I don't get the problem
Sent from my Transformer TF101 using XDA Premium App

EP2008 said:
Has anyone experienced, what I'm calling the "Dim of death"?
Basically, it only seems to happen in the browser. Things will seem ok and then the screen will go dim... basically the device freezes, but not completely. For example, I can return to the lock screen, but cannot enter my lock pattern. Pressing "play" on my bluetooth keyboard will start up a song.
The problem is, there's no recovery from the "dim of death" other than to restart the device. It's the only reason why I have to restart my transformer and the one thing that makes me affraid to use the stock browser (which I do only if I need to play flash content)
Anyone else have this problem?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I heard about that the newest FW-V8.2.3.13 solve this problem.

kimi_Q said:
I heard about that the newest FW-V8.2.3.13 solve this problem.
Click to expand...
Click to collapse
Nope, happened yesterday.... only in the stock browser.
Sent from my Transformer TF101 using XDA Premium App

kimi_Q said:
I heard about that the newest FW-V8.2.3.13 solve this problem.
Click to expand...
Click to collapse
I'm on FW8.2.3.13 and its happened to me as well. It happened on 8.2.3.9 as well. It only happens in two scenarios both of which involve high brightness; 1) try turning the brightness all the way up and the backlight shuts off and 2) let auto brightness turn the brightness up and it turns off.
The first three days I was on 8.2.3.13 (rooted Prime 1.3) it worked fine to where I could adjust brightness to any level. I installed some games and a task manager after that so I guess ill start by removing the task manager.
Its happened in Google books and the browser for me.
Sent from my Transformer TF101 using Tapatalk

This has happened to me once before, but I can't remember if it was before or after the update. The browser went dim and was unresponsive, but then I think it either gave me the option to force close or I let it sit for a minute and hit back and managed to get to the home screen and then force closed the browser through the application settings page.

I just bought the 32GB model (and keyboard dock) and this happens right from the box. During the initial setup it wants to create a Google account. As soon as the browser inits the screen goes black. Holding the power button for 10 seconds causes a reset and it reboots to the same point. I had to create the account on my PC and then was able to go past. Then the OTA tried to spawn the browser and tanked. Grrr! I just did a factory reset; hopefully the restore ROM they have is clean otherwise I'm going to frisbee this bloody unit across the room!

Worth mentioning? The screen blacks out when running Android Market as well, but _not_ the YouTube app. Is it just segfaulting on a shared lib?
Firefox, DolphinHD, and Angry Birds all cause the screen to go black. In the case of Angry Birds, the music continues to play so the machine isn't frozen; it has merely turned off the display. logcat seems to bear this out as you can see it setting display brightness to 0. Why, I cannot say.

haven't had this yet.

seshmaru said:
haven't had this yet.
Click to expand...
Click to collapse
Your post is entirely unhelpful.
Anyways...I uninstalled "taskpanel" but now i'm too afraid to turn up the brightness because i'm not sure if it will go dim or not.
The backlight turns off even when i'm on the homescreen and set the brightness to max.

I installed Firefox and it will make the screen black out as well. Dmesg shows Tegra_pwm going into pwm and setting the display to 0 but it doesn't show the caller! I either have to press the power key multiple quick presses in a row or hold for 10 seconds. Gratingly, the "Power Off" dialog will illuminate the screen but immediately blackout again when I click Cancel. ACV, terminal basically any app that doesn't use a library common to browsers and Android Marker (Gmail app as well.) As above, the YouTube app functions perfectly, so I know both the unit and the networking stack is functional to a point. I am curious as to how these units paint the screen; is it a WM on X or a binary-blob to the framebuffer?
A factory reset did nothing, sadly. Given that I cannot scan the filesystem (I'm thinking a corrupt node exists) I need a way to wipe the internal flash and put a fresh image down (after scanning the MTD.) Any ideas?
Cheers,
Todd.
(PS: I've been lurking for a while so I'll pre-answer some common questions. I've minor light bleed from lower left at extreme angles, no obvious creaking, sound appears balanced and I've yet to get zapped by the charger. Without the web its difficult to install test apps! )

Weird. I have the screen timeout set to "never" and the brightness manually set to 60% and it still turns off the screen, even when idle at the homescreen. I have it docked; does this alter how it does power management?

Finally got logcat going
I tapped the browser icon and the screen blacks out as expected. The following entries are written to the log:
Code:
05-20 10:43:37.220: INFO/ActivityManager(127): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.browser/.BrowserActivity bnds=[144,645][240,741] } from pid 223
05-20 10:43:37.250: DEBUG/SurfaceFlinger(127): screenshot: sw=230, sh=143, minZ=0, maxZ=21005
05-20 10:43:37.280: DEBUG/SurfaceFlinger(127): screenshot: result = OK
05-20 10:43:37.330: DEBUG/dalvikvm(127): GC_CONCURRENT freed 595K, 7% free 9490K/10183K, paused 3ms+4ms
05-20 10:43:37.350: INFO/ActivityManager(127): Start proc com.android.browser for activity com.android.browser/.BrowserActivity: pid=786 uid=10054 gids={3003, 1015}
05-20 10:43:37.390: DEBUG/WindowManager(127): readLidState, sw:1
05-20 10:43:37.390: DEBUG/WindowManager(127): adjustConfigurationLw, config:{ scale=1.0 imsi=0/0 loc=null touch=3 keys=2/1/1 nav=1/1 orien=L layout=0x10000014 uiMode=0x0} mLidOpen:1 config.hardKeyboardHidden:1
05-20 10:43:37.410: DEBUG/dalvikvm(86): GC_EXPLICIT freed 12K, 6% free 6202K/6531K, paused 8ms+1ms
05-20 10:43:37.440: INFO/ActivityThread(786): Pub com.android.browser;browser: com.android.browser.provider.BrowserProvider2
05-20 10:43:37.450: DEBUG/dalvikvm(86): GC_EXPLICIT freed <1K, 6% free 6202K/6531K, paused 1ms+1ms
05-20 10:43:37.450: INFO/ActivityThread(786): Pub com.android.browser.home: com.android.browser.homepages.HomeProvider
05-20 10:43:37.490: DEBUG/dalvikvm(86): GC_EXPLICIT freed <1K, 6% free 6202K/6531K, paused 1ms+2ms
05-20 10:43:37.520: INFO/BrowserSettings(786): Selected search engine: ActivitySearchEngine{[email protected]}
05-20 10:43:37.600: DEBUG/dalvikvm(786): GC_CONCURRENT freed 135K, 4% free 6563K/6791K, paused 3ms+2ms
05-20 10:43:37.980: DEBUG/dalvikvm(786): GC_CONCURRENT freed 51K, 3% free 7015K/7175K, paused 2ms+1ms
05-20 10:43:37.990: DEBUG/dalvikvm(786): GC_FOR_ALLOC freed 1K, 3% free 7014K/7175K, paused 14ms
05-20 10:43:38.000: INFO/dalvikvm-heap(786): Grow heap (frag case) to 7.420MB for 513744-byte allocation
05-20 10:43:38.010: DEBUG/dalvikvm(786): GC_FOR_ALLOC freed <1K, 3% free 7515K/7687K, paused 16ms
05-20 10:43:38.030: DEBUG/dalvikvm(786): GC_CONCURRENT freed 4K, 2% free 7540K/7687K, paused 1ms+1ms
05-20 10:43:38.040: INFO/SqliteDatabaseCpp(786): sqlite returned: error code = 1, msg = index cookie_times already exists, db=/data/data/com.android.browser/databases/webview.db
05-20 10:43:38.070: INFO/SqliteDatabaseCpp(786): sqlite returned: error code = 1, msg = index cookie_times already exists, db=/data/data/com.android.browser/databases/webview.db
05-20 10:43:38.100: DEBUG/dalvikvm(786): GC_FOR_ALLOC freed 505K, 9% free 7039K/7687K, paused 15ms
05-20 10:43:38.140: DEBUG/dalvikvm(786): GC_CONCURRENT freed 2K, 2% free 7548K/7687K, paused 2ms+1ms
05-20 10:43:38.220: INFO/ActivityManager(127): Start proc com.google.android.gsf.login for service com.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginService: pid=805 uid=10022 gids={3003, 1015, 2001, 1007}
05-20 10:43:38.260: WARN/TestFlashPlugin(786): support: true
05-20 10:43:38.260: VERBOSE/TLINE(786): new: [email protected]
05-20 10:43:38.290: INFO/ActivityManager(127): No longer want com.google.android.gm (pid 561): hidden #16
05-20 10:43:38.300: DEBUG/libEGL(786): loaded /system/lib/egl/libGLES_android.so
05-20 10:43:38.310: DEBUG/libEGL(786): loaded /system/lib/egl/libEGL_tegra.so
05-20 10:43:38.320: DEBUG/libEGL(786): loaded /system/lib/egl/libGLESv1_CM_tegra.so
05-20 10:43:38.320: DEBUG/libEGL(786): loaded /system/lib/egl/libGLESv2_tegra.so
05-20 10:43:38.340: DEBUG/OpenGLRenderer(786): Creating OpenGL renderer caches
05-20 10:43:38.340: DEBUG/OpenGLRenderer(786): Enabling debug mode 0
05-20 10:43:38.340: DEBUG/OpenGLRenderer(786): Layers will be composited as regions
05-20 10:43:38.430: INFO/ActivityManager(127): Displayed com.android.browser/.BrowserActivity: +1s91ms
05-20 10:43:38.450: DEBUG/PhoneWindow(223): couldn't save which view has focus because the focused view [email protected] has no id.
05-20 10:43:41.850: DEBUG/dalvikvm(786): GC_CONCURRENT freed 299K, 5% free 7733K/8135K, paused 2ms+2ms
05-20 10:43:43.500: DEBUG/dalvikvm(223): GC_EXPLICIT freed 162K, 18% free 15729K/19143K, paused 3ms+3ms
05-20 10:43:46.120: WARN/webcore(786): Can't get the viewWidth after the first layout
05-20 10:43:46.130: DEBUG/BrowserLogin(786): Finished login attempt for [email protected]
05-20 10:43:46.180: DEBUG/webviewglue(786): nativeDestroy view: 0x272e60
05-20 10:43:46.210: DEBUG/dalvikvm(786): GC_FOR_ALLOC freed 281K, 6% free 7786K/8199K, paused 16ms
05-20 10:43:46.230: DEBUG/dalvikvm(786): GC_FOR_ALLOC freed 25K, 6% free 7981K/8455K, paused 16ms
05-20 10:43:47.200: INFO/TextType(210): TextType = 0x0
05-20 10:44:02.270: ERROR/Tab(786): onReceivedError -6 The connection to the server was unsuccessful.
05-20 10:44:02.340: DEBUG/dalvikvm(786): GC_CONCURRENT freed 198K, 5% free 8316K/8711K, paused 2ms+2ms
When I attempt a screen shot (through Eclipse) I get a "Screen Unavailable" message and then this in logcat:
Code:
05-20 10:45:00.000: INFO/dalvikvm(127): Jit: resizing JitTable from 4096 to 8192
05-20 10:45:04.890: DEBUG/dalvikvm(786): GC_CONCURRENT freed 678K, 10% free 8270K/9095K, paused 3ms+2ms
05-20 10:45:12.710: DEBUG/SntpClient(127): request time failed: java.net.SocketTimeoutException: Try again
05-20 10:46:07.920: DEBUG/SntpClient(127): request time failed: java.net.SocketTimeoutException: Try again
05-20 10:46:14.160: DEBUG/SurfaceFlinger(127): screenshot: sw=1280, sh=800, minZ=0, maxZ=-1
05-20 10:46:14.310: DEBUG/SurfaceFlinger(127): screenshot: result = OK
05-20 10:46:19.350: INFO/DEBUG(85): debuggerd committing suicide to free the zombie!
05-20 10:46:19.360: INFO/DEBUG(853): debuggerd: May 11 2011 22:26:41
05-20 10:46:27.930: DEBUG/SntpClient(127): request time failed: java.net.SocketTimeoutException: Try again
05-20 10:46:30.050: DEBUG/BatteryService(127): level:96 scale:100 status:5 health:2 present:true dock_status:4 dock_level:68 voltage: 8 temperature: 270 technology: Li-ion AC powered:true USB powered:false icon:17302692 invalid charger:0
05-20 10:46:30.060: DEBUG/WifiService(127): ACTION_BATTERY_CHANGED pluggedType: 1
05-20 10:46:30.060: DEBUG/UiModeManager(127): Display mobile dock notificaiton, level:68 status:4
05-20 10:46:30.070: INFO/fdhttpd(646): battery level:96 plugged:1
05-20 10:46:30.070: DEBUG/PowerUI(190): closing low battery warning: level=96
Any takers?

When clicking the power button twice, the screen flickers (on press #2) but remains off. The following is emitted:
Code:
05-20 10:52:20.800: DEBUG/PowerManagerService(127): @PowerManagement: Sleep state requested, reason:2
05-20 10:52:20.800: DEBUG/PowerManagerService(127): @PowerManagement: Screen Bright {true -> false}
05-20 10:52:21.100: INFO/power(127): *** set_screen_state 0
05-20 10:52:21.100: DEBUG/SurfaceFlinger(127): screenshot: sw=230, sh=143, minZ=0, maxZ=21010
05-20 10:52:21.100: DEBUG/PowerManagerService(127): @PowerManagement: Screen turned off mScreenOnTime=1700988ms Battery<C,V>: <96,8>
05-20 10:52:21.100: DEBUG/PowerManagerService(127): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
05-20 10:52:21.110: DEBUG/SurfaceFlinger(127): About to give-up screen, flinger = 0x135fc8
05-20 10:52:21.120: DEBUG/SurfaceFlinger(127): screenshot: result = OK
05-20 10:52:21.130: DEBUG/PowerManagerService(127): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
05-20 10:52:21.130: DEBUG/WifiService(127): ACTION_SCREEN_OFF
05-20 10:52:21.140: DEBUG/AlarmManager(127): Added alarm Alarm{4098c8e8 type 2 com.google.android.gsf} type:ELAPSED_REALTIME_WAKEUP when: After 0h:4m:59.0s
05-20 10:52:21.150: DEBUG/PowerManagerService(127): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
05-20 10:52:26.190: DEBUG/dalvikvm(223): GC_EXPLICIT freed 77K, 19% free 15652K/19143K, paused 4ms+2ms
05-20 10:52:46.030: INFO/power(127): *** set_screen_state 1
05-20 10:52:46.030: DEBUG/PowerManagerService(127): @PowerManagement: Screen Bright {false -> true}
05-20 10:52:46.030: DEBUG/PowerManagerService(127): @PowerManagement: Screen turned on mScreenOffTime=24929ms Battery<C,V>: <96,8>
05-20 10:52:46.030: DEBUG/PowerManagerService(127): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
05-20 10:52:46.040: DEBUG/WindowManager(127): readLidState, sw:1
05-20 10:52:46.140: DEBUG/WindowManager(127): adjustConfigurationLw, config:{ scale=1.0 imsi=0/0 loc=null touch=3 keys=2/1/1 nav=1/1 orien=L layout=0x10000014 uiMode=0x0} mLidOpen:1 config.hardKeyboardHidden:1
05-20 10:52:46.180: DEBUG/PowerManagerService(127): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
05-20 10:52:46.180: DEBUG/WifiService(127): ACTION_SCREEN_ON
05-20 10:52:46.190: WARN/TestFlashPlugin(786): support: true
05-20 10:52:46.220: DEBUG/PowerManagerService(127): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
05-20 10:52:46.470: DEBUG/SurfaceFlinger(127): Screen about to return, flinger = 0x135fc8

I wish I understood what that stuff means Todd. I should note that for me, this problem only happens in the browser. I have Flash "always on" and it seems to only happen when I'm viewing flash content. I do have auto brightness on with a 5 minute timeout on my device.
Sent from my Transformer TF101 using XDA Premium App

[HELP] accelerometer hardware revisions that are unsupported in android

Hi,
lately I stumbled upon two cases on some serbian android forum with users who dont have working accelerometers on android....any rom. While in windows it works.
I tried to helped them, but in any rom, freshly instaled it doesn't work. One user flashed windows via SD card method and then started installing android again from scrath (hspl, task29....) but it is the same.
Both users has regular europe leo.
In both cases the latest radio is installed, also magldr 1.13.
This is part of the logcat I found that has something related to sensors.
E/Sensors ( 282): Couldn't open /dev/akm8973_aot (No such file or directory)
E/Sensors ( 282): ECS_IOCTL_APP_SET_XXX failed (Bad file number)
E/SensorService( 282): Error activating sensor 0 (Bad file number)
E/Sensors ( 282): Couldn't open /dev/akm8973_aot (No such file or directory)
E/Sensors ( 282): ECS_IOCTL_APP_SET_XXX failed (Bad file number)
E/SensorService( 282): Error activating sensor 1 (Bad file number)
I/Compass (12159): Unregistering Sensor Event Listener for ShakeSensor
I/Compass (12159): Calibration is complete.
D/dalvikvm( 282): GC_CONCURRENT freed 1388K, 40% free 7968K/13063K, external 70K/573K, paused 5ms+8ms
I/Compass (12159): Compass onPause
D/PersistentEventStore/putEvent(12159): Row ID: 58, Event ID: 58
I/Compass (12159): Unregistering Orientation Listener
I/Compass (12159): Unregistering Magnetic Field Listener
I/Compass (12159): Removing GPS Location Updates
I/Compass (12159): Removing GPS Status Listener
I/Compass (12159): Removing Network Location Updates
I/Compass (12159): Stopping AsyncGeocoder thread.
I/Compass (12159): There are no pending preference changes
I/Compass (12159): All sensors are now Paused
D/gps_leo ( 282): gps_inject_location() is called
D/gps_leo ( 282): latitude=44.863907, longitude=20.476783, accuracy=1691.000000
I/Compass (12159): Compass onStop
I/Compass (12159): Compass onDestroy
Click to expand...
Click to collapse
I know that akmd is responsible for sensors, so it probably dont have that specific hardware supported.
Any help or information to resolve this is apritiated. I will ask the users to provide any information from their phone, but that is mostly all I can do to help.
I found several post on XDA regarding this but without any answer.

[Q] Touchscreen doesn't work after using the power button

So I boot up that N7 and everything works great. Until I press the power button once to lock it and then again to unlock it. After that, the touchscreen does not respond to anything. The rest is good - ADB works and it shows that it's charging when I connect it to the PC or the charger.
What could be the possible issue?
I tried reflashing the tab, problem persists on both 4.1.2 and 4.2.2 stock ROMs.

Spaqin said:
So I boot up that N7 and everything works great. Until I press the power button once to lock it and then again to unlock it. After that, the touchscreen does not respond to anything. The rest is good - ADB works and it shows that it's charging when I connect it to the PC or the charger.
What could be the possible issue?
I tried reflashing the tab, problem persists on both 4.1.2 and 4.2.2 stock ROMs.
Click to expand...
Click to collapse
Very wierd issue that almost seems hardware related. You have tried a factory reset correct?

I would guess that flashing the stock ROM through fastboot is more or less a factory reset. I will try to do that from Android too.
I'm pretty sure this is software related bug - TWRP doesn't have any problems with waking up.
Problem persists even on a custom kernel - LeanKernel. I will try to flash a custom ROM soon if that factory reset won't help.
[edit]
So I used logcat and it gave me this:
Code:
I/PowerManagerService( 481): Going to sleep by user request...
D/SurfaceFlinger( 128): Screen released, type=0 flinger=0x405ca318
I/WindowManager( 481): No lock screen!
D/dalvikvm( 481): GC_CONCURRENT freed 946K, 21% free 11856K/14860K, paused 4ms+5ms, total 62ms
D/dalvikvm( 481): WAIT_FOR_CONCURRENT_GC blocked 24ms
D/dalvikvm( 481): WAIT_FOR_CONCURRENT_GC blocked 34ms
D/NfcService( 843): NFC-C OFF, disconnect
D/dalvikvm( 481): GC_CONCURRENT freed 468K, 16% free 12484K/14860K, paused 3ms+3ms, total 47ms
D/dalvikvm( 481): WAIT_FOR_CONCURRENT_GC blocked 44ms
D/dalvikvm( 481): GC_FOR_ALLOC freed 139K, 17% free 12475K/14860K, paused 72ms, total 72ms
D/dalvikvm( 481): GC_FOR_ALLOC freed 132K, 17% free 12452K/14860K, paused 72ms, total 72ms
D/dalvikvm( 481): GC_FOR_ALLOC freed 104K, 15% free 12635K/14860K, paused 71ms, total 72ms
D/PhoneStatusBar( 731): disable: < expand icons alerts ticker system_info back home RECENT* clock search >
V/TAG ( 481): bug 7643792: fitSystemWindows([0,33][0,0])
V/TAG ( 481): bug 7643792: fitSystemWindows([0,33][0,0])
D/libEGL ( 481): loaded /system/lib/egl/libEGL_tegra.so
D/dalvikvm( 1983): GC_CONCURRENT freed 262K, 5% free 7433K/7820K, paused 1ms+2ms, total 23ms
D/libEGL ( 481): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/libEGL ( 481): loaded /system/lib/egl/libGLESv2_tegra.so
D/OpenGLRenderer( 481): Enabling debug mode 0
D/PhoneStatusBar( 731): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT clock search >
I/PowerManagerService( 481): Waking up from sleep...
I/WindowManager( 481): Lock screen displayed!
D/PowerManagerService-JNI( 481): Excessive delay in autosuspend_disable() while turning screen on: 262ms
D/SurfaceFlinger( 128): Screen acquired, type=0 flinger=0x405ca318
(turned logcat a bit earlier [lots of different stuff there, just ignored it], used the power button to get the device to sleep, pressed it again to unlock, touchscreen does not respond, ctrl+c'd from logcat.)

Spaqin said:
I would guess that flashing the stock ROM through fastboot is more or less a factory reset. I will try to do that from Android too.
I'm pretty sure this is software related bug - TWRP doesn't have any problems with waking up.
Problem persists even on a custom kernel - LeanKernel. I will try to flash a custom ROM soon if that factory reset won't help.
Click to expand...
Click to collapse
So the touchscreen does respond in TWRP? Im not sure what to suggest. Thats very wierd. I hope a solution arises. Good luck

Yeah. Neither a new kernel (tried franco's too), nor CM10.1 seem to solve the issue. It still works good after the boot for practically infinite amount of time and it works great.
I just got the tab to fix that issue, and talked to my friend who has a N7 too (but fully working of course) - he said he had a similar issue with his magnetic cover. I guess that the magnetic sensor could be damaged in some way. It's not my N7, I'm not going to open it to check.

Spaqin said:
Yeah. Neither a new kernel (tried franco's too), nor CM10.1 seem to solve the issue. It still works good after the boot for practically infinite amount of time and it works great.
I just got the tab to fix that issue, and talked to my friend who has a N7 too (but fully working of course) - he said he had a similar issue with his magnetic cover. I guess that the magnetic sensor could be damaged in some way. It's not my N7, I'm not going to open it to check.
Click to expand...
Click to collapse
This thread has a solution to disable the magnetic sensor and this link talks about google currents as a possible culprit (even though the issue doesn't exactly match yours, it may be worth a try).

Yeah.
Shame that nobody introduced that thing into their kernel :X and CM10.1 is google app-less unless I install them.
Thanks for your advice though! I will give the tab back to the owner, maybe he will want to disassemble it and try to fix the issue.

Spaqin said:
Yeah.
Shame that nobody introduced that thing into their kernel :X and CM10.1 is google app-less unless I install them.
Thanks for your advice though! I will give the tab back to the owner, maybe he will want to disassemble it and try to fix the issue.
Click to expand...
Click to collapse
No problem at all :good:

Yet another "phantom touch"/"Screen not working" thread.

As the title says, I have this issue on my N4.. It started on Tuesday night. I am on Slimkat at the moment because I cannot be bothered to flash yet another ROM anymore but it started as a problem on Paranoid Android BETA 2. However, it has persisted over Slimkat ROM and others along with different kernels such as franco's. I am not sure if it is a hardware issue although it is restricted to the bottom ~5% of the screen (i.e. the navbar) but it works fine when I am using the keyboard. Any other time, that bottom part of the screen is unusable. Over the past 24 hours it has become noticeably worse. I have the screen touch pointer enabled in developer options and I can see it slide left to right extremely fast at the bottom and doesn't stop unless I lock the screen and it happens randomly no matter what app I'm in! It also tends to get stuck in the bottom right corner quite a lot and if I touch the screen anywhere else, it zooms in so it is acting as though I am holding the bottom right corner with my thumb. Locking the screen and unlocking it fixes the issue for around 30 seconds but the bottom part is still unusable. After that 30 seconds it starts over again with the touch pointer going crazy.
I really hope it isn't a hardware issue as I have never dropped the phone nor had this problem prior to earlier this week. The logcat from paranoid android shows powerHAL is acting up and that touch_boost does not exist on my phone which should be there apparently. I have pasted a part of my logcat below and attached the full file if anyone is interested - scroll down about 3/4 of the way and it's all errors.
[ 05-06 02:17:04.118 793: 793 V/DeadZone ]
consuming errant click: (372.5,9.5)
[ 05-06 02:17:04.219 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.219 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.229 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.229 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.399 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.399 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.399 793: 793 V/DeadZone ]
consuming errant click: (179.5,9.5)
If anyone can help I'd appreciate it tremendously. I feel like this is mostly a software issue but I could be wrong. Thanks in advance!

Same problem mate since yesterday....my phone is 1year old too....and now the Navy bar isn't working....no idea what's the problem....I am on pa 4.3; beta 3....I think it's mostly the hardware....if someone could help us it would be great
Sent from my Nexus 4 using XDA Premium 4 mobile app

And you guys reverted to stock rom to see if It persist?, i had my bottom left of the navigation bar not working half a year ago with pa so I went to stock to make sure, it worked again and haven't had the issue since

same to me, same day, same issue. I also have no sensibility to the upper right corner of the screen.
I reverted to stock, the problem persists. I think it's hardware, as it appeared also in the touch recovery