I found this thread while searching, which is very similar to my issue, but his resolution seems strange, imo.
If you go into Wifi Settings, check to enable Wifi, it looks like it enables, shows scanning, then FC, and it goes back to wireless Settings and Wifi turns back off. When i bought it, it had Amon's recovery, v1.7 iirc, and was running stock FRF91. Whenever tmo pushed FRG83 OTA, it would reboot, but into Amon's recovery, fail to update, and boot back into FRF91. I used universal androot to root and all seemed well, just wifi wouldn't work. I assumed it was a borked restore on previous owner's part, something to do with the kernel and/or drivers.
I finally decided to do a full unroot (stock rom, stock recovery, etc), so I downloaded FRF91 PASSIMG.zip. It wouldn't flash it from the bootloader (wouldn't detect it, and scrolls to fast for me to see), so I extracted each and fastboot flashed all (boot, recovery, system,userdata). Booted up, wifi worked, then OTA upgrade to 2.2.1 (FRG83D?). Since universal androot doesn't work on that, and I didn't feel like searching unrevoked, I just loaded Amon's 2.0 recovery back and loaded a different ROM. Fail on my part here is I didn't test wifi while on 2.2.1 before rerooting & installing Amon's recovery. I updated the radio to 5.08 from 4.06.00.12_7.
I tried LeoFroyo and the app drawer was sluggish, so I switched to This ROM and yesterday Wifi worked fine. Did a full wipe, flashed that ROM, then the black bar add on. I was at one of my work locations with 5+ APs and it detected all of them. When I got home, did a NAND backup, flashed the wifi calling add on, and no more wifi. Restored the NAND backup, still no wifi. I now updated the radio to 5.12.00.08, but still no wifi. I'm at a different work location, but same physical infrastructure (APs, SSIDs, security, etc), no wifi. If I enable wifi either by the check box in wireless settings or the power control widget, it just turns back off. I get the FC if I go into WiFi Setting, then enable it there.
I can enable wifi tethering, it broadcasts fine and I can connect to it. I changed the SSID as well as the PSK, the changes worked. Rebooted the phone, still no wifi. Bluetooth also works fine, as does the 3.5mm jack. GPS works, but seems lacking. In my house, it'll never lock. On my back porch (no patio cover) it'll pick up 2 sats in yellow (gps status). Driving, it'll pick up 4 or 5 locked sats with a small green bar. My mt3g locks in my bedroom with 7+ sats. So far, only the wifi is not working, and the GPS is simply slow/weak. I bought the phone on CL Saturday, so I'm starting to wonder if this is why it was for sale.
Here's the logcat from when I try to enable wifi:
Code:
D/Tethering( 90): eth0 is not a tetherable iface, ignoring
D/WifiService( 90): ACTION_BATTERY_CHANGED pluggedType: 2
D/WifiService( 90): acquireWifiLockLocked: WifiLock{NetworkLocationProvider type=2 [email protected]}
D/LocationMasfClient( 90): getNetworkLocation(): Returning cache location with accuracy 1811.0
E/wpa_supplicant( 859): Failed to initialize control interface 'tiwlan0'.
E/wpa_supplicant( 859): You may have another wpa_supplicant process already running or the file was
E/wpa_supplicant( 859): left by an unclean termination of wpa_supplicant in which case you will need
E/wpa_supplicant( 859): to manually remove this file before starting wpa_supplicant again.
I/wpa_supplicant( 859): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
D/WifiStateTracker( 90): Reset connections and stopping DHCP
W/ActivityManager( 90): Timeout of broadcast BroadcastRecord{46324ef0 android.net.wifi.WIFI_STATE_CHANGED} - [email protected]
W/ActivityManager( 90): Receiver during timeout: ResolveInfo{46503498 com.android.settings.widget.SettingsAppWidgetProvider p=0 o=0 m=0x108000}
I/Process ( 90): Sending signal. PID: 837 SIG: 3
I/dalvikvm( 837): threadid=3: reacting to signal 3
I/dalvikvm( 837): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 90 SIG: 3
I/dalvikvm( 90): threadid=3: reacting to signal 3
I/dalvikvm( 90): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 163 SIG: 3
I/dalvikvm( 163): threadid=3: reacting to signal 3
I/dalvikvm( 163): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 168 SIG: 3
I/dalvikvm( 168): threadid=3: reacting to signal 3
I/dalvikvm( 168): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 820 SIG: 3
I/dalvikvm( 820): threadid=3: reacting to signal 3
I/dalvikvm( 820): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 692 SIG: 3
I/dalvikvm( 692): threadid=3: reacting to signal 3
I/dalvikvm( 692): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 722 SIG: 3
I/dalvikvm( 722): threadid=3: reacting to signal 3
I/dalvikvm( 722): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 711 SIG: 3
I/dalvikvm( 711): threadid=3: reacting to signal 3
I/dalvikvm( 711): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 636 SIG: 3
I/dalvikvm( 636): threadid=3: reacting to signal 3
I/dalvikvm( 636): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 655 SIG: 3
I/dalvikvm( 655): threadid=3: reacting to signal 3
I/dalvikvm( 655): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 599 SIG: 3
I/dalvikvm( 599): threadid=3: reacting to signal 3
I/dalvikvm( 599): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 626 SIG: 3
I/dalvikvm( 626): threadid=3: reacting to signal 3
I/dalvikvm( 626): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 703 SIG: 3
I/dalvikvm( 703): threadid=3: reacting to signal 3
I/dalvikvm( 703): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 454 SIG: 3
I/dalvikvm( 454): threadid=3: reacting to signal 3
I/dalvikvm( 454): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 255 SIG: 3
I/dalvikvm( 255): threadid=3: reacting to signal 3
I/dalvikvm( 255): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 775 SIG: 3
I/dalvikvm( 775): threadid=3: reacting to signal 3
I/dalvikvm( 775): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 766 SIG: 3
I/dalvikvm( 766): threadid=3: reacting to signal 3
I/dalvikvm( 766): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 782 SIG: 3
I/dalvikvm( 782): threadid=3: reacting to signal 3
I/dalvikvm( 782): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 753 SIG: 3
I/dalvikvm( 753): threadid=3: reacting to signal 3
I/dalvikvm( 753): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 378 SIG: 3
I/dalvikvm( 378): threadid=3: reacting to signal 3
I/dalvikvm( 378): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 645 SIG: 3
I/dalvikvm( 645): threadid=3: reacting to signal 3
I/dalvikvm( 645): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 675 SIG: 3
I/dalvikvm( 675): threadid=3: reacting to signal 3
I/dalvikvm( 675): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 175 SIG: 3
I/dalvikvm( 175): threadid=3: reacting to signal 3
I/dalvikvm( 175): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 90): Sending signal. PID: 589 SIG: 3
I/dalvikvm( 589): threadid=3: reacting to signal 3
I/dalvikvm( 589): Wrote stack traces to '/data/anr/traces.txt'
E/ActivityManager( 90): ANR in com.android.settings
E/ActivityManager( 90): Reason: Broadcast of Intent { act=android.net.wifi.WIFI_STATE_CHANGED flg=0x10000000 cmp=com.android.settings/.widget.SettingsAppWidgetProvider (has extras) }
E/ActivityManager( 90): Load: 1.52 / 1.47 / 0.96
E/ActivityManager( 90): CPU usage from 85667ms to 51ms ago:
E/ActivityManager( 90): system_server: 4% = 2% user + 1% kernel / faults: 2647 minor 5 major
E/ActivityManager( 90): akmd: 2% = 0% user + 2% kernel
E/ActivityManager( 90): e.process.gapps: 0% = 0% user + 0% kernel / faults: 61 minor
E/ActivityManager( 90): events/0: 0% = 0% user + 0% kernel
E/ActivityManager( 90): ail.application: 0% = 0% user + 0% kernel / faults: 407 minor
E/ActivityManager( 90): m.android.phone: 0% = 0% user + 0% kernel / faults: 19 minor
E/ActivityManager( 90): d.process.acore: 0% = 0% user + 0% kernel / faults: 54 minor
E/ActivityManager( 90): kmmcd: 0% = 0% user + 0% kernel
E/ActivityManager( 90): ogle.android.gm: 0% = 0% user + 0% kernel / faults: 90 minor
E/ActivityManager( 90): y.mobile:remote: 0% = 0% user + 0% kernel / faults: 82 minor 1 major
E/ActivityManager( 90): oid.voicesearch: 0% = 0% user + 0% kernel / faults: 429 minor
E/ActivityManager( 90): ocs.android: 0% = 0% user + 0% kernel / faults: 396 minor
E/ActivityManager( 90): d.apps.uploader: 0% = 0% user + 0% kernel / faults: 42 minor
E/ActivityManager( 90): d.process.media: 0% = 0% user + 0% kernel / faults: 20 minor
E/ActivityManager( 90): adbd: 0% = 0% user + 0% kernel / faults: 10 minor
E/ActivityManager( 90): ndroid.launcher: 0% = 0% user + 0% kernel / faults: 11 minor
E/ActivityManager( 90): putmethod.latin: 0% = 0% user + 0% kernel / faults: 11 minor
E/ActivityManager( 90): .oneClickWidget: 0% = 0% user + 0% kernel / faults: 147 minor
E/ActivityManager( 90): init: 0% = 0% user + 0% kernel / faults: 7 minor
E/ActivityManager( 90): rpcrouter: 0% = 0% user + 0% kernel
E/ActivityManager( 90): synaptics_wq: 0% = 0% user + 0% kernel
E/ActivityManager( 90): viders.calendar: 0% = 0% user + 0% kernel / faults: 10 minor
E/ActivityManager( 90): droid.gallery3d: 0% = 0% user + 0% kernel / faults: 9 minor
E/ActivityManager( 90): equicksearchbox: 0% = 0% user + 0% kernel / faults: 42 minor 1 major
E/ActivityManager( 90): com.android.mms: 0% = 0% user + 0% kernel / faults: 31 minor 1 major
E/ActivityManager( 90): pps.googlevoice: 0% = 0% user + 0% kernel / faults: 17 minor
E/ActivityManager( 90): pper.gpstracker: 0% = 0% user + 0% kernel / faults: 32 minor
E/ActivityManager( 90): +ndroid.settings: 0% = 0% user + 0% kernel
E/ActivityManager( 90): +logcat: 0% = 0% user + 0% kernel
E/ActivityManager( 90): +iscan_sysioc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): +dhcp_sysioc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): +dhd_watchdog: 0% = 0% user + 0% kernel
E/ActivityManager( 90): +dhd_dpc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): +dhd_sysioc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): -ndroid.settings: 0% = 0% user + 0% kernel
E/ActivityManager( 90): -logcat: 0% = 0% user + 0% kernel
E/ActivityManager( 90): -iscan_sysioc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): -dhcp_sysioc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): -dhd_watchdog: 0% = 0% user + 0% kernel
E/ActivityManager( 90): -dhd_dpc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): -dhd_sysioc: 0% = 0% user + 0% kernel
E/ActivityManager( 90): TOTAL: 10% = 5% user + 4% kernel
D/dalvikvm( 90): GC_FOR_MALLOC freed 9322 objects / 1199272 bytes in 86ms
D/dalvikvm( 90): GC_FOR_MALLOC freed 1711 objects / 250416 bytes in 69ms
I/dalvikvm-heap( 90): Grow heap (frag case) to 8.611MB for 166544-byte allocation
D/dalvikvm( 90): GC_FOR_MALLOC freed 41 objects / 1728 bytes in 80ms
D/WifiService( 90): releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 [email protected]}
D/dalvikvm( 90): GC_FOR_MALLOC freed 51 objects / 460168 bytes in 74ms
D/WifiStateTracker( 90): Disabling interface
W/ActivityManager( 90): finishReceiver called but no pending broadcasts
E/WifiHW ( 90): Supplicant not running, cannot connect
D/dalvikvm( 599): GC_EXPLICIT freed 2207 objects / 172144 bytes in 59ms
D/NativeCrypto( 599): Freeing OpenSSL session
W/ActivityManager( 90): Force finishing activity com.android.settings/.wifi.WifiSettings
I/Process ( 90): Sending signal. PID: 837 SIG: 9
I/ActivityManager( 90): Killing com.android.settings (pid=837): user's request
I/ActivityManager( 90): Process com.android.settings (pid 837) has died.
I/WindowManager( 90): WIN DEATH: Window{46298bd8 com.android.settings/com.android.settings.WirelessSettings paused=false}
I/WindowManager( 90): WIN DEATH: Window{462b1330 com.android.settings/com.android.settings.wifi.WifiSettings paused=true}
I/ActivityManager( 90): Start proc com.android.settings for activity com.android.settings/.WirelessSettings: pid=864 uid=1000 gids={3003, 3002, 3001}
W/InputManagerService( 90): Got RemoteException sending setActive(false) notification to pid 837 uid 1000
I/ActivityManager( 90): Displayed activity com.android.settings/.WirelessSettings: 278 ms (total 278 ms)
E/WifiHW ( 90): Supplicant not running, cannot connect
D/dalvikvm( 820): GC_EXPLICIT freed 943 objects / 53504 bytes in 63ms
E/WifiHW ( 90): Supplicant not running, cannot connect
V/WifiStateTracker( 90): Supplicant died unexpectedly
D/WifiStateTracker( 90): Reset connections and stopping DHCP
D/WifiStateTracker( 90): Disabling interface
D/NetworkStateTracker( 90): setDetailed state, old =DISCONNECTED and new state=DISCONNECTED
D/WifiStateTracker( 90): Reset connections and stopping DHCP
D/WifiStateTracker( 90): Disabling interface
E/Tethering( 90): attempting to remove unknown iface (eth0), ignoring
D/LocationMasfClient( 90): getNetworkLocation(): Returning cache location with accuracy 1811.0
I know it's kind of long, but just trying to provide as much info as possible. I have the traces.txt file, too large to attach, but I dunno what any of it is.
Got it fixed!
Okay, so got it figured out.
After a fresh install, wifi works fine. Then, I'd run Titanium Backup and restore a bunch of stuff, including the Titanium part for the wifi APs and such. A lot of the settings wouldn't take precedence until AFTER a reboot. It's at this point WIFI would fail.
I took a nand backup, full wipe, then re-setup the phone and all good. Flashed the wifi calling add-on and still have wifi.
Also, since google restored the settings, it had the AP's saved anyway, so no need to restore that through Titanium. I rebooted a few times, turned wifi on & off, installed Mobile Defense, which required a reboot, too. In testing, I did find that speeds on the N1's 3G are decent. The upload is almost double that of my RoadRunner.
I still have carpy GPS lock/reception, though.
Hope this helps anyone else who has the problem I had.
Edit, seems there are some brave dev's for the Galaxy 8.9 and its poisike, motley and myself!!
Mod's I'm not sure if I can rename my thread, and I know I definitely can't move it. Can you rename this thread to something like [ROM][ICS][alpha]p4wifi ICS build for Tab 8.9 - WIP, and move to the development forum?
Progress report.
poisike began toying with a xoom build shortly after google dropped the src for 4.0.3
separately (not long after I posted the original thread titled "no brave ICS devs for Galaxy Tabs?", I began setting up my macpro with ubuntu and started tinkering with cm9 and asop sources. last night I got a build compiled and flashed to my Gtab 8.9, and it booted!
Between the 2 of us we have booted ICS on the Galaxy Tab 8.9.
motley recompiled his kernel to get touch screen working.
poiske's version has no green screen, mine does, I have sound, his doesn't etc.
This is very very early on, but it seems we maybe able to combine the builds to get a working rom, seperately it was suggested I contact the CM9 guys about this for help or to work with them.
I will update this post as things progress.
Cheers!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am hoping that once we get ICS source for a tegra device (like the Xoom which should be one of the first), development will take off... For now I am waiting on CM9 since I don't have the time to teach myself enough about Android development.
ICS source for the Xoom was just released today. Hopefully ICS development for all tegra tablets will start accelerating.
https://groups.google.com/forum/#!topic/android-building/mjEzwvc_J4k/discussion
I have played with the Xoom ICS 4.0.3 rom all weekend. Please keep in mind that i'm not a developer, so don't expect a working port from me. I just wanted to see how far i can get...
And this is how far i get. If anyone has any ideas, then please share...
Code:
12-18 12:23:52.489: DEBUG/AndroidRuntime(307): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
12-18 12:23:52.489: DEBUG/AndroidRuntime(307): CheckJNI is OFF
12-18 12:23:52.629: INFO/SamplingProfilerIntegration(307): Profiling disabled.
12-18 12:23:52.639: INFO/Zygote(307): Preloading classes...
12-18 12:23:52.649: DEBUG/dalvikvm(307): GC_EXPLICIT freed 36K, 85% free 409K/2560K, paused 0ms+0ms
12-18 12:23:52.659: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 82% free 473K/2560K, paused 0ms+0ms
12-18 12:23:52.679: DEBUG/dalvikvm(307): GC_EXPLICIT freed 20K, 81% free 509K/2560K, paused 0ms+0ms
12-18 12:23:52.689: DEBUG/dalvikvm(307): GC_EXPLICIT freed 27K, 80% free 536K/2560K, paused 0ms+0ms
12-18 12:23:52.699: DEBUG/dalvikvm(307): GC_EXPLICIT freed 15K, 78% free 576K/2560K, paused 1ms+1ms
12-18 12:23:52.719: DEBUG/dalvikvm(307): GC_EXPLICIT freed 27K, 77% free 603K/2560K, paused 1ms+0ms
12-18 12:23:52.749: DEBUG/dalvikvm(307): GC_EXPLICIT freed 30K, 76% free 635K/2560K, paused 0ms+0ms
12-18 12:23:52.759: DEBUG/TextLayoutCache(307): Using debug level: 0 - Debug Enabled: 0
12-18 12:23:52.759: WARN/Zygote(307): Class not found for preloading: android.media.AudioManager$2
12-18 12:23:52.799: INFO/dalvikvm(307): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
12-18 12:23:52.799: DEBUG/MtpDeviceJNI(307): register_android_mtp_MtpDevice
12-18 12:23:52.799: INFO/dalvikvm(307): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
12-18 12:23:52.799: INFO/dalvikvm(307): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
12-18 12:23:52.799: WARN/Zygote(307): Class not found for preloading: android.media.IRemoteControlClientDispatcher
12-18 12:23:52.799: WARN/Zygote(307): Class not found for preloading: android.media.IRemoteControlClientDispatcher$Stub
12-18 12:23:52.809: DEBUG/dalvikvm(307): GC_EXPLICIT freed 20K, 74% free 672K/2560K, paused 1ms+1ms
12-18 12:23:52.889: DEBUG/dalvikvm(307): GC_FOR_ALLOC freed 217K, 63% free 967K/2560K, paused 8ms
12-18 12:23:52.909: DEBUG/dalvikvm(307): GC_EXPLICIT freed 44K, 61% free 1023K/2560K, paused 0ms+1ms
12-18 12:23:52.939: DEBUG/dalvikvm(307): GC_EXPLICIT freed 27K, 59% free 1052K/2560K, paused 1ms+1ms
12-18 12:23:52.969: DEBUG/dalvikvm(307): GC_EXPLICIT freed 8K, 58% free 1100K/2560K, paused 1ms+1ms
12-18 12:23:52.989: DEBUG/dalvikvm(307): GC_EXPLICIT freed 23K, 55% free 1166K/2560K, paused 1ms+1ms
12-18 12:23:53.029: DEBUG/dalvikvm(307): GC_EXPLICIT freed 48K, 44% free 1445K/2560K, paused 1ms+1ms
12-18 12:23:53.029: WARN/Zygote(307): Class not found for preloading: android.text.TextDirectionHeuristics$CharCount
12-18 12:23:53.029: WARN/Zygote(307): Class not found for preloading: android.text.method.WordIterator$1
12-18 12:23:53.059: DEBUG/dalvikvm(307): GC_EXPLICIT freed 34K, 43% free 1479K/2560K, paused 1ms+2ms
12-18 12:23:53.079: DEBUG/dalvikvm(307): GC_EXPLICIT freed 32K, 42% free 1502K/2560K, paused 1ms+2ms
12-18 12:23:53.139: INFO/dalvikvm(307): threadid=1: recursive native library load attempt (/system/lib/libwebcore.so)
12-18 12:23:53.149: DEBUG/dalvikvm(307): No JNI_OnLoad found in /system/lib/libchromium_net.so 0x0, skipping init
12-18 12:23:53.179: DEBUG/dalvikvm(307): GC_EXPLICIT freed 26K, 40% free 1550K/2560K, paused 2ms+1ms
12-18 12:23:53.199: WARN/Zygote(307): Class not found for preloading: android.widget.EdgeGlow
12-18 12:23:53.239: DEBUG/dalvikvm(307): GC_EXPLICIT freed 25K, 39% free 1579K/2560K, paused 1ms+2ms
12-18 12:23:53.309: DEBUG/dalvikvm(307): GC_EXPLICIT freed 71K, 37% free 1625K/2560K, paused 2ms+2ms
12-18 12:23:53.309: ERROR/PhonePolicy(307): Could not preload class for phone policy: com.android.internal.policy.impl.PhoneWindow$ContextMenuCallback
12-18 12:23:53.339: DEBUG/dalvikvm(307): GC_EXPLICIT freed 33K, 36% free 1646K/2560K, paused 1ms+1ms
12-18 12:23:53.369: DEBUG/dalvikvm(307): GC_EXPLICIT freed 28K, 35% free 1675K/2560K, paused 1ms+2ms
12-18 12:23:53.389: DEBUG/dalvikvm(307): GC_EXPLICIT freed 26K, 34% free 1706K/2560K, paused 2ms+2ms
12-18 12:23:53.419: DEBUG/dalvikvm(307): GC_EXPLICIT freed 32K, 33% free 1731K/2560K, paused 1ms+2ms
12-18 12:23:53.439: DEBUG/dalvikvm(307): GC_EXPLICIT freed 31K, 32% free 1759K/2560K, paused 1ms+2ms
12-18 12:23:53.469: DEBUG/dalvikvm(307): GC_EXPLICIT freed 71K, 30% free 1815K/2560K, paused 2ms+2ms
12-18 12:23:53.489: DEBUG/dalvikvm(307): GC_EXPLICIT freed 39K, 29% free 1831K/2560K, paused 2ms+2ms
12-18 12:23:53.839: INFO/System(307): Loaded time zone names for in 336ms (331ms in ICU)
12-18 12:23:54.109: INFO/System(307): Loaded time zone names for en_US in 268ms (264ms in ICU)
12-18 12:23:54.129: DEBUG/dalvikvm(307): GC_EXPLICIT freed 324K, 24% free 1948K/2560K, paused 2ms+2ms
12-18 12:23:54.149: DEBUG/dalvikvm(307): GC_EXPLICIT freed 15K, 22% free 2009K/2560K, paused 2ms+2ms
12-18 12:23:54.189: DEBUG/dalvikvm(307): GC_EXPLICIT freed 51K, 21% free 2040K/2560K, paused 1ms+2ms
12-18 12:23:54.219: DEBUG/dalvikvm(307): GC_EXPLICIT freed 29K, 20% free 2070K/2560K, paused 2ms+2ms
12-18 12:23:54.249: DEBUG/dalvikvm(307): GC_EXPLICIT freed 37K, 19% free 2087K/2560K, paused 2ms+2ms
12-18 12:23:54.279: DEBUG/dalvikvm(307): GC_EXPLICIT freed 32K, 18% free 2109K/2560K, paused 2ms+2ms
12-18 12:23:54.279: INFO/Zygote(307): ...preloaded 2297 classes in 1641ms.
12-18 12:23:54.299: DEBUG/dalvikvm(307): GC_EXPLICIT freed 22K, 18% free 2114K/2560K, paused 2ms+2ms
12-18 12:23:54.299: INFO/Zygote(307): Preloading resources...
12-18 12:23:54.329: DEBUG/dalvikvm(307): GC_EXPLICIT freed 1K, 16% free 2169K/2560K, paused 2ms+2ms
12-18 12:23:54.349: DEBUG/dalvikvm(307): GC_EXPLICIT freed 1K, 14% free 2220K/2560K, paused 1ms+1ms
12-18 12:23:54.379: DEBUG/dalvikvm(307): GC_EXPLICIT freed 3K, 12% free 2267K/2560K, paused 2ms+2ms
12-18 12:23:54.399: DEBUG/dalvikvm(307): GC_EXPLICIT freed 3K, 10% free 2314K/2560K, paused 2ms+2ms
12-18 12:23:54.419: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 8% free 2362K/2560K, paused 1ms+2ms
12-18 12:23:54.449: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 6% free 2412K/2560K, paused 1ms+2ms
12-18 12:23:54.469: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 7% free 2459K/2627K, paused 2ms+2ms
12-18 12:23:54.499: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 5% free 2505K/2627K, paused 2ms+2ms
12-18 12:23:54.519: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 6% free 2554K/2691K, paused 2ms+2ms
12-18 12:23:54.549: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 6% free 2603K/2755K, paused 1ms+2ms
12-18 12:23:54.569: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 6% free 2664K/2819K, paused 2ms+2ms
12-18 12:23:54.599: DEBUG/dalvikvm(307): GC_EXPLICIT freed 2K, 4% free 2713K/2819K, paused 1ms+2ms
12-18 12:23:54.629: DEBUG/dalvikvm(307): GC_EXPLICIT freed 3K, 5% free 2760K/2883K, paused 2ms+2ms
12-18 12:23:54.649: DEBUG/dalvikvm(307): GC_EXPLICIT freed 6K, 5% free 2808K/2947K, paused 1ms+2ms
12-18 12:23:54.679: DEBUG/dalvikvm(307): GC_EXPLICIT freed 7K, 4% free 2854K/2947K, paused 2ms+2ms
12-18 12:23:54.699: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 4% free 2903K/3011K, paused 2ms+2ms
12-18 12:23:54.729: DEBUG/dalvikvm(307): GC_EXPLICIT freed 9K, 3% free 2947K/3011K, paused 1ms+2ms
12-18 12:23:54.759: DEBUG/dalvikvm(307): GC_EXPLICIT freed 8K, 2% free 3026K/3075K, paused 2ms+2ms
12-18 12:23:54.789: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 3% free 3071K/3139K, paused 1ms+1ms
12-18 12:23:54.819: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 3% free 3121K/3203K, paused 1ms+2ms
12-18 12:23:54.839: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 2% free 3168K/3203K, paused 2ms+2ms
12-18 12:23:54.869: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 1% free 3244K/3267K, paused 1ms+2ms
12-18 12:23:54.899: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 3% free 3559K/3651K, paused 1ms+2ms
12-18 12:23:54.919: DEBUG/dalvikvm(307): GC_EXPLICIT freed 7K, 2% free 3612K/3651K, paused 1ms+2ms
12-18 12:23:54.949: DEBUG/dalvikvm(307): GC_EXPLICIT freed 2K, 2% free 3662K/3715K, paused 1ms+2ms
12-18 12:23:54.979: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 2% free 3711K/3779K, paused 2ms+2ms
12-18 12:23:54.999: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 1% free 3885K/3907K, paused 2ms+2ms
12-18 12:23:55.029: DEBUG/dalvikvm(307): GC_EXPLICIT freed 3K, 2% free 3932K/3971K, paused 1ms+2ms
12-18 12:23:55.059: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 3% free 4992K/5123K, paused 1ms+2ms
12-18 12:23:55.099: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 4% free 6013K/6211K, paused 2ms+2ms
12-18 12:23:55.129: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 3% free 6062K/6211K, paused 2ms+2ms
12-18 12:23:55.159: DEBUG/dalvikvm(307): GC_EXPLICIT freed 7K, 2% free 6106K/6211K, paused 1ms+2ms
12-18 12:23:55.189: DEBUG/dalvikvm(307): GC_EXPLICIT freed 6K, 1% free 6153K/6211K, paused 2ms+2ms
12-18 12:23:55.209: DEBUG/dalvikvm(307): GC_EXPLICIT freed 5K, 1% free 6201K/6211K, paused 1ms+2ms
12-18 12:23:55.239: DEBUG/dalvikvm(307): GC_EXPLICIT freed 2K, 1% free 6253K/6275K, paused 2ms+2ms
12-18 12:23:55.269: DEBUG/dalvikvm(307): GC_EXPLICIT freed 4K, 1% free 6301K/6339K, paused 2ms+2ms
12-18 12:23:55.299: DEBUG/dalvikvm(307): GC_EXPLICIT freed 6K, 1% free 6362K/6403K, paused 2ms+2ms
12-18 12:23:55.319: DEBUG/dalvikvm(307): GC_EXPLICIT freed 3K, 1% free 6427K/6467K, paused 2ms+3ms
12-18 12:23:55.329: INFO/Zygote(307): ...preloaded 379 resources in 1029ms.
12-18 12:23:55.359: DEBUG/dalvikvm(307): GC_EXPLICIT freed 20K, 2% free 6461K/6531K, paused 2ms+3ms
12-18 12:23:55.359: INFO/Zygote(307): ...preloaded 31 resources in 31ms.
12-18 12:23:55.389: DEBUG/dalvikvm(307): GC_EXPLICIT freed 14K, 2% free 6464K/6531K, paused 2ms+2ms
12-18 12:23:55.419: DEBUG/dalvikvm(307): GC_EXPLICIT freed 6K, 2% free 6458K/6531K, paused 2ms+2ms
12-18 12:23:55.439: DEBUG/dalvikvm(307): GC_EXPLICIT freed <1K, 2% free 6457K/6531K, paused 2ms+2ms
12-18 12:23:55.449: INFO/dalvikvm(307): System server process 311 has been created
12-18 12:23:55.449: INFO/Zygote(307): Accepting command socket connections
12-18 12:23:55.509: INFO/sysproc(311): Entered system_init()
12-18 12:23:55.509: INFO/sysproc(311): ServiceManager: 0x14d2a0
12-18 12:23:55.509: DEBUG/SensorService(311): nuSensorService starting...
12-18 12:23:55.529: ERROR/MPLSensor(311): MPLSensor::MPLSensor(): starting
12-18 12:23:55.529: ERROR/MPLSensor(311): MPLSensor: unable to load MPL Library, Cannot load library: load_library[1091]: Library 'libmpu.so' not found
12-18 12:23:55.609: ERROR/Sensors(311): couldn't find 'accelerometer_sensor' input device
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=5, enabled=0
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=6, enabled=0
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=7, enabled=0
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=8, enabled=0
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=9, enabled=0
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=10, enabled=0
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=2, enabled=0
12-18 12:23:55.609: DEBUG/Sensors(311): activate , handle=11, enabled=0
12-18 12:23:55.609: INFO/SensorService(311): BH1721FVC Light sensor
12-18 12:23:55.609: INFO/SensorService(311): MPL rotation vector
12-18 12:23:55.609: INFO/SensorService(311): MPL linear accel
12-18 12:23:55.609: INFO/SensorService(311): MPL gravity
12-18 12:23:55.609: INFO/SensorService(311): MPL gyro
12-18 12:23:55.609: INFO/SensorService(311): MPL accelerometer
12-18 12:23:55.609: INFO/SensorService(311): MPL Orientation
12-18 12:23:55.609: INFO/SensorService(311): MPL Calibrated Magnetic Field
12-18 12:23:55.609: INFO/sysproc(311): System server: starting Android runtime.
12-18 12:23:55.609: INFO/sysproc(311): System server: starting Android services.
12-18 12:23:55.609: DEBUG/SensorService(311): nuSensorService thread starting...
12-18 12:23:55.609: INFO/sysproc(311): System server: entering thread pool.
12-18 12:23:55.609: INFO/SystemServer(311): Entered the Android system server!
12-18 12:23:55.609: INFO/SystemServer(311): Entropy Service
12-18 12:23:55.689: INFO/SystemServer(311): Power Manager
12-18 12:23:55.689: INFO/SystemServer(311): Activity Manager
12-18 12:23:55.689: INFO/ActivityManager(311): Memory class: 48
12-18 12:23:55.699: WARN/UsageStats(311): Usage stats version changed; dropping
12-18 12:23:55.729: INFO/ServiceManager(311): Waiting for service SurfaceFlinger...
12-18 12:23:56.660: INFO/SurfaceFlinger(332): SurfaceFlinger is starting
12-18 12:23:56.660: INFO/SurfaceFlinger(332): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
12-18 12:23:56.729: INFO/ServiceManager(311): Waiting for service SurfaceFlinger...
12-18 12:23:56.809: ERROR/gralloc(332): HDCP: hdcp_open failed, error 1
12-18 12:23:56.809: INFO/gralloc(332): using (fd=15)
12-18 12:23:56.809: INFO/gralloc(332): id = tegra_fb
12-18 12:23:56.809: INFO/gralloc(332): xres = 800 px
12-18 12:23:56.809: INFO/gralloc(332): yres = 1280 px
12-18 12:23:56.809: INFO/gralloc(332): xres_virtual = 800 px
12-18 12:23:56.809: INFO/gralloc(332): yres_virtual = 2560 px
12-18 12:23:56.809: INFO/gralloc(332): bpp = 32
12-18 12:23:56.809: INFO/gralloc(332): r = 0:8
12-18 12:23:56.809: INFO/gralloc(332): g = 8:8
12-18 12:23:56.809: INFO/gralloc(332): b = 16:8
12-18 12:23:56.809: INFO/gralloc(332): smem_start = 0x2e700000
12-18 12:23:56.809: INFO/gralloc(332): smem_len = 0x00800000
12-18 12:23:56.809: INFO/gralloc(332): format = 1
12-18 12:23:56.809: INFO/gralloc(332): stride = 800
12-18 12:23:56.809: INFO/gralloc(332): width = 120 mm (169.333328 dpi)
12-18 12:23:56.809: INFO/gralloc(332): height = 192 mm (169.333328 dpi)
12-18 12:23:56.809: INFO/gralloc(332): refresh rate = 60.00 Hz
12-18 12:23:56.819: DEBUG/libEGL(332): loaded /system/lib/egl/libGLES_android.so
12-18 12:23:56.829: DEBUG/libEGL(332): loaded /system/lib/egl/libEGL_tegra.so
12-18 12:23:56.839: DEBUG/libEGL(332): loaded /system/lib/egl/libGLESv1_CM_tegra.so
12-18 12:23:56.849: DEBUG/libEGL(332): loaded /system/lib/egl/libGLESv2_tegra.so
12-18 12:23:56.849: DEBUG/libEGL(332): [ 12-18 12:23:56.849 332:0x14d F/libc ]
12-18 12:23:56.849: DEBUG/libEGL(332): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
12-18 12:23:57.370: INFO/DEBUG(222): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-18 12:23:57.370: INFO/DEBUG(222): Build fingerprint: 'Android/full_wingray/wingray:4.0.3/IML74K/eng.root.20111216.220306:userdebug/test-keys'
12-18 12:23:57.370: INFO/DEBUG(222): pid: 332, tid: 333 >>> /system/bin/surfaceflinger <<<
12-18 12:23:57.370: INFO/DEBUG(222): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
12-18 12:23:57.370: INFO/DEBUG(222): r0 00018970 r1 100ffca8 r2 100ffcc8 r3 00000000
12-18 12:23:57.370: INFO/DEBUG(222): r4 000dd0c8 r5 00000000 r6 100ffca8 r7 00000000
12-18 12:23:57.370: INFO/DEBUG(222): r8 00000000 r9 00000003 10 00000001 fp 80caf32c
12-18 12:23:57.370: INFO/DEBUG(222): ip 00000000 sp 100ffca0 lr 40b8527b pc 00000000 cpsr 40000010
12-18 12:23:57.370: INFO/DEBUG(222): d0 4329555542700000 d1 0000000043295555
12-18 12:23:57.370: INFO/DEBUG(222): d2 0000000000000000 d3 0000000000000000
12-18 12:23:57.370: INFO/DEBUG(222): d4 3fe0000000009470 d5 3fe0000000000000
12-18 12:23:57.370: INFO/DEBUG(222): d6 3fdffffffffed720 d7 4170000000000000
12-18 12:23:57.370: INFO/DEBUG(222): d8 0000000000000000 d9 0000000000000000
12-18 12:23:57.370: INFO/DEBUG(222): d10 0000000000000000 d11 0000000000000000
12-18 12:23:57.370: INFO/DEBUG(222): d12 0000000000000000 d13 0000000000000000
12-18 12:23:57.370: INFO/DEBUG(222): d14 0000000000000000 d15 0000000000000000
12-18 12:23:57.370: INFO/DEBUG(222): scr 20000010
12-18 12:23:57.469: INFO/DEBUG(222): #00 pc 00000000
12-18 12:23:57.469: INFO/DEBUG(222): #01 pc 00007278 /system/lib/egl/libEGL_tegra.so
12-18 12:23:57.469: INFO/DEBUG(222): #02 pc 0000825e /system/lib/egl/libEGL_tegra.so (eglCreateWindowSurface)
12-18 12:23:57.469: INFO/DEBUG(222): #03 pc 0000d1fc /system/lib/libEGL.so (eglCreateWindowSurface)
12-18 12:23:57.469: INFO/DEBUG(222): #04 pc 000186f2 /system/lib/libsurfaceflinger.so (_ZN7android15DisplayHardware4initEj)
12-18 12:23:57.469: INFO/DEBUG(222): #05 pc 00018b4a /system/lib/libsurfaceflinger.so (_ZN7android15DisplayHardwareC2ERKNS_2spINS_14SurfaceFlingerEEEj)
12-18 12:23:57.469: INFO/DEBUG(222): #06 pc 0001e244 /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger10readyToRunEv)
12-18 12:23:57.469: INFO/DEBUG(222): #07 pc 0002112a /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv)
12-18 12:23:57.469: INFO/DEBUG(222): #08 pc 00021790 /system/lib/libutils.so
12-18 12:23:57.469: INFO/DEBUG(222): #09 pc 00012e2c /system/lib/libc.so (__thread_entry)
12-18 12:23:57.469: INFO/DEBUG(222): #10 pc 00012980 /system/lib/libc.so (pthread_create)
12-18 12:23:57.469: INFO/DEBUG(222): code around pc:
12-18 12:23:57.469: INFO/DEBUG(222): 00000000 ffffffff ffffffff ffffffff ffffffff ................
12-18 12:23:57.469: INFO/DEBUG(222): 00000010 ffffffff ffffffff ffffffff ffffffff ................
12-18 12:23:57.469: INFO/DEBUG(222): 00000020 ffffffff ffffffff ffffffff ffffffff ................
12-18 12:23:57.469: INFO/DEBUG(222): 00000030 ffffffff ffffffff ffffffff ffffffff ................
12-18 12:23:57.469: INFO/DEBUG(222): 00000040 ffffffff ffffffff ffffffff ffffffff ................
12-18 12:23:57.469: INFO/DEBUG(222): code around lr:
12-18 12:23:57.469: INFO/DEBUG(222): 40b85258 e8d0f7fb 69e368a0 05bcf104 01dcf104 .....h.i........
12-18 12:23:57.469: INFO/DEBUG(222): 40b85268 91019500 2300f3c3 f1066905 46310220 .......#.i.. .1F
12-18 12:23:57.479: INFO/DEBUG(222): 40b85278 68e047a8 3014f990 9804b92b 2c60f420 .G.h...0+... .`,
12-18 12:23:57.479: INFO/DEBUG(222): 40b85288 2220f44c 69e39204 6180f443 990761e1 L. "...iC..a.a..
12-18 12:23:57.479: INFO/DEBUG(222): 40b85298 a802b919 f7fb2240 9902e8ae 428a6aa2 [email protected]".......j.B
12-18 12:23:57.479: INFO/DEBUG(222): stack:
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc60 0000001b
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc64 0006fe60 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc68 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc6c 00000002
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc70 100ffca4
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc74 000db1b8 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc78 00000001
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc7c 000dc410 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc80 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc84 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc88 100ffca8
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc8c 000dd0c8 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc90 0000fd68 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc94 100ffca8
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc98 df0027ad
12-18 12:23:57.479: INFO/DEBUG(222): 100ffc9c 00000000
12-18 12:23:57.479: INFO/DEBUG(222): #01 100ffca0 000dd184 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffca4 000dd1a4 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffca8 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcac 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcb0 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcb4 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcb8 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcbc 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcc0 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcc4 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcc8 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffccc 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcd0 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcd4 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcd8 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcdc 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffce0 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffce4 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffce8 000dd0c8 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcec 0000fd68 [heap]
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcf0 00000000
12-18 12:23:57.479: INFO/DEBUG(222): 100ffcf4 40b86263 /system/lib/egl/libEGL_tegra.so
12-18 12:23:57.729: INFO/ServiceManager(311): Waiting for service SurfaceFlinger...
12-18 12:23:57.899: INFO/ServiceManager(219): service 'entropy' died
12-18 12:23:57.899: INFO/ServiceManager(219): service 'power' died
12-18 12:23:57.899: INFO/ServiceManager(219): service 'sensorservice' died
surfaceflinger
Click to expand...
Click to collapse
Graphics drivers need reworking, as Google have said.
Hurrian said:
Graphics drivers need reworking, as Google have said.
Click to expand...
Click to collapse
This rom runs on Xoom and as far as i know, the graphics hardware is the same on GT8.9 and Xoom.
I just read in Xoom forum that the portrait lag in launcher is gone (it's the same problem we have in landscape, because on GT8.9 the screen is rotated 90 degrees), that means we will finally get rid of the lag in launcher if we can port this rom...
And ICS boots on GT8.9... That's all it does of course.
poisike said:
And ICS boots on GT8.9... That's all it does of course.
Click to expand...
Click to collapse
good work what did you do to get past that earlier error?
2 more hours and i still can't get touchscreen working.
I have fixed all errors in logcat and it looks fine to me now. Or am i just too tired?
Code:
INFO/EventHub(280): New device: id=3, fd=122, path='/dev/input/event2', name='sec_touchscreen', classes=0x14, configuration='/system/usr/idc/sec_touchscreen.idc', keyLayout='', keyCharacterMap='', builtinKeyboard=false
INFO/InputReader(280): Touch device 'sec_touchscreen' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.
INFO/InputReader(280): Device added: id=3, name='sec_touchscreen', sources=0x00001002
INFO/InputManagerService(280): Selected default: com.android.inputmethod.latin/.LatinIME
INFO/SystemServer(280): Accessibility Manager
INFO/InputReader(280): Reconfiguring input devices. changes=0x00000004
INFO/InputReader(280): Device reconfigured: id=3, name='sec_touchscreen', surface size is now 1280x800, mode is 1
DEBUG/PermissionCache(223): checking android.permission.ACCESS_SURFACE_FLINGER for uid=1000 => granted (334 us)
WARN/ActivityManager(280): Unable to write /sys/module/lowmemorykiller/parameters/adj
WARN/ActivityManager(280): Unable to write /sys/module/lowmemorykiller/parameters/minfree
INFO/ActivityManager(280): Config changed: {1.0 0mcc0mnc en_US layoutdir=0 sw800dp w1280dp h752dp xlrg long land ?uimode ?night finger -keyb/v/h -nav/h s.1}
Which kernel are you using?
what xoom rom did you use and how did you flash?
poisike said:
2 more hours and i still can't get touchscreen working.
I have fixed all errors in logcat and it looks fine to me now. Or am i just too tired?
Code:
INFO/EventHub(280): New device: id=3, fd=122, path='/dev/input/event2', name='sec_touchscreen', classes=0x14, configuration='/system/usr/idc/sec_touchscreen.idc', keyLayout='', keyCharacterMap='', builtinKeyboard=false
INFO/InputReader(280): Touch device 'sec_touchscreen' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.
INFO/InputReader(280): Device added: id=3, name='sec_touchscreen', sources=0x00001002
INFO/InputManagerService(280): Selected default: com.android.inputmethod.latin/.LatinIME
INFO/SystemServer(280): Accessibility Manager
INFO/InputReader(280): Reconfiguring input devices. changes=0x00000004
INFO/InputReader(280): Device reconfigured: id=3, name='sec_touchscreen', surface size is now 1280x800, mode is 1
DEBUG/PermissionCache(223): checking android.permission.ACCESS_SURFACE_FLINGER for uid=1000 => granted (334 us)
WARN/ActivityManager(280): Unable to write /sys/module/lowmemorykiller/parameters/adj
WARN/ActivityManager(280): Unable to write /sys/module/lowmemorykiller/parameters/minfree
INFO/ActivityManager(280): Config changed: {1.0 0mcc0mnc en_US layoutdir=0 sw800dp w1280dp h752dp xlrg long land ?uimode ?night finger -keyb/v/h -nav/h s.1}
Click to expand...
Click to collapse
For touchscreen, did you try to copy everything from /system/usr from our Galaxy HC 3.2 ROM to the same location on the ICS ROM? (all files and folder, overwrite everything). This is how I got the touchscreen working on the ASUS port I am working on.
Hurrian said:
Which kernel are you using?
Click to expand...
Click to collapse
I'm using _motley kernel.
nycbjr said:
what xoom rom did you use and how did you flash?
Click to expand...
Click to collapse
This > http://forum.xda-developers.com/showthread.php?t=1396251 But it won't work without modifications. Don't try to flash it without modifications, you could mess up your tab.
_motley said:
For touchscreen, did you try to copy everything from /system/usr from our Galaxy HC 3.2 ROM to the same location on the ICS ROM? (all files and folder, overwrite everything). This is how I got the touchscreen working on the ASUS port I am working on.
Click to expand...
Click to collapse
I only copied the files that i saw (in logcat) it tried to load and failed. I will copy all files and try again.
Strangely it seems to configure the touchscreen successfully and i can see outbut in logcat when i touch the screen, so it seems to somewhat work.
I wonder what he tries to write to Unable to write /sys/module/lowmemorykiller/parameters/adj Is this related to touchscreen? Maybe it fails to write the calibration file?
poisike said:
I'm using _motley kernel.
This > http://forum.xda-developers.com/showthread.php?t=1396251 But it won't work without modifications. Don't try to flash it without modifications, you could mess up your tab.
I only copied the files that i saw (in logcat) it tried to load and failed. I will copy all files and try again.
Strangely it seems to configure the touchscreen successfully and i can see outbut in logcat when i touch the screen, so it seems to somewhat work.
I wonder what he tries to write to Unable to write /sys/module/lowmemorykiller/parameters/adj Is this related to touchscreen? Maybe it fails to write the calibration file?
Click to expand...
Click to collapse
Nice progress so far. I figured the 10.1 would get ported first and we would end up with a port from the 10.1. It doesn't even look like anyone in the 10.1 forum is working on ICS yet though.
nkrick said:
Nice progress so far. I figured the 10.1 would get ported first and we would end up with a port from the 10.1. It doesn't even look like anyone in the 10.1 forum is working on ICS yet though.
Click to expand...
Click to collapse
Please don't expect a working rom from me, like i already wrote, i'm not a developer. In fact this is first time i try to port a rom.
About the GT10.1, they are just all waiting for CM9. There is really no point in investing time in porting if there is CM9 coming soon.
_motley: I tried what you suggested and this didn't help. But i found something interesting in another thread here in xda, someone suggested to edit the touchscreen driver and kernel. Unfortunately i don't know anything about kernel, so maybe _motley can find some time?
poisike said:
Please don't expect a working rom from me, like i already wrote, i'm not a developer. In fact this is first time i try to port a rom.
About the GT10.1, they are just all waiting for CM9. There is really no point in investing time in porting if there is CM9 coming soon.
_motley: I tried what you suggested and this didn't help. But i found something interesting in another thread here in xda, someone suggested to edit the touchscreen driver and kernel. Unfortunately i don't know anything about kernel, so maybe _motley can find some time?
Click to expand...
Click to collapse
I don't expect a working ROM, I just think it is great that someone is working on it (looking at it if you prefer). CM9 will be great and I will probably use it (it is highly likely that CM9 will support the Tab 8.9 also), but anything you find playing with ICS AOSP will only help others in the future if someone wants to build other AOSP ROMs.
People just "waiting" for CM9 on the GT 10.1 may be in for a longer wait than they think. It is very likely that Cyanogen got it working quickly due to his access to Samsung binaries and source code (which he can't release to the public unless Samsung plays nice). CM9 for GT 10.1 probably won't be available until after ICS source from Samsung officially drops, and even then we may get stuck with buggy binaries that were built for Samsung ROMs, not AOSP ROMs.
edit: looks like there may be a cm9 build for GT 10.1 before Samsung drops source after all (Dec 14th post): https://plus.google.com/100275307499530023476/posts
So, is Samsung playing nice? or is there sufficient code already available to the public between ASOP and Samsung's current Open Source releases?
very good point, can we start a "no Touchwiz with our ICS" campaign? lol
or "Please don't Wiz on our ICS" rofl
nycbjr said:
very good point, can we start a "no Touchwiz with our ICS" campaign? lol
or "Please don't Wiz on our ICS" rofl
Click to expand...
Click to collapse
LOL
Actually, what I have read indicates that the leaked ICS ROM for the GT 10.1 only has a few "additions" from TW. It seems to be mostly lockscreen, launcher, and widgets right now. That may change as Samsung continues development...
poisike said:
I wonder what he tries to write to Unable to write /sys/module/lowmemorykiller/parameters/adj Is this related to touchscreen? Maybe it fails to write the calibration file?
Click to expand...
Click to collapse
This is a request to sysfs to adjust runtime parameters in the kernel for lowmemorykiller. This is coming the init files in the ramdisk and doesn't have anything to do with the touch screen.
nycbjr said:
very good point, can we start a "no Touchwiz with our ICS" campaign? lol
or "Please don't Wiz on our ICS" rofl
Click to expand...
Click to collapse
LOL...I always thought a good name for a vanilla ROM would be "Don't touch my wiz"
nkrick said:
LOL
Actually, what I have read indicates that the leaked ICS ROM for the GT 10.1 only has a few "additions" from TW. It seems to be mostly lockscreen, launcher, and widgets right now. That may change as Samsung continues development...
Click to expand...
Click to collapse
Where is that leaked rom?
A finding and a question:
1. ksmd is consuming CPU cycles. If I disable ksmd, the loadavg drops dramatically.
Code:
echo 0 > /sys/kernel/mm/ksm/run
It helps reduce battery usage.
2. I am seeing Gmail is consuming a whole lot of CPU cycles and its triggering a media scan. Is anyone else seeing this?
Code:
User 7%, System 36%, IOW 0%, IRQ 0%
User 5 + Nice 11 + Sys 76 + Idle 119 + IOW 0 + IRQ 0 + SIRQ 0 = 211
PID PR CPU% S #THR VSS RSS PCY UID Name
887 1 31% S 4 8564K 2952K fg media_rw /system/bin/sdcard
30426 0 21% S 71 1251556K 132212K bg u0_a123 com.google.android.gm
6735 0 4% R 1 2968K 1180K fg root top
Obviously, killing the process does not help because its system service and will pop right back up.
devsk said:
A finding and a question:
1. ksmd is consuming CPU cycles. If I disable ksmd, the loadavg drops dramatically.
Code:
echo 0 > /sys/kernel/mm/ksm/run
It helps reduce battery usage.
2. I am seeing Gmail is consuming a whole lot of CPU cycles and its triggering a media scan. Is anyone else seeing this?
Code:
User 7%, System 36%, IOW 0%, IRQ 0%
User 5 + Nice 11 + Sys 76 + Idle 119 + IOW 0 + IRQ 0 + SIRQ 0 = 211
PID PR CPU% S #THR VSS RSS PCY UID Name
887 1 31% S 4 8564K 2952K fg media_rw /system/bin/sdcard
30426 0 21% S 71 1251556K 132212K bg u0_a123 com.google.android.gm
6735 0 4% R 1 2968K 1180K fg root top
Obviously, killing the process does not help because its system service and will pop right back up.
Click to expand...
Click to collapse
Cool.. that's good to know. Thanks for the info! Would you say disabling that kernel process reduces battery usage a great deal?
One thing that I have noticed with CM 13/marshmallow builds in general, is that sometimes my device just *will not* connect to the mobile network; sometimes I will get lucky and it will connect just fine, but other times it cannot make a connection to save its soul. When it cannot connect, it persistently tries to connect, over and over again-- even if I'm on Wi-Fi-- and the battery is drained at a very rapid rate. However, when it does connect to the LTE network with no issues, battery drainage becomes a non-issue.
(I'm on Verizon, btw)
devsk said:
A finding and a question:
1. ksmd is consuming CPU cycles. If I disable ksmd, the loadavg drops dramatically.
Code:
echo 0 > /sys/kernel/mm/ksm/run
It helps reduce battery usage.
2. I am seeing Gmail is consuming a whole lot of CPU cycles and its triggering a media scan. Is anyone else seeing this?
Code:
User 7%, System 36%, IOW 0%, IRQ 0%
User 5 + Nice 11 + Sys 76 + Idle 119 + IOW 0 + IRQ 0 + SIRQ 0 = 211
PID PR CPU% S #THR VSS RSS PCY UID Name
887 1 31% S 4 8564K 2952K fg media_rw /system/bin/sdcard
30426 0 21% S 71 1251556K 132212K bg u0_a123 com.google.android.gm
6735 0 4% R 1 2968K 1180K fg root top
Obviously, killing the process does not help because its system service and will pop right back up.
Click to expand...
Click to collapse
I turned the KSM off in the Kernel Auditor and the loadav dropped significantly. It should be removed because it serves no purpose really and changing it every boot is a pain As for the gmail service, I just limited it's wakelocks because it was too damn frequent. But what I am wondering is, how is your loadavg 0.8? mine is 2.28 1.93 2.12 4/1437 4960 ... I think I have a major problem somwhere The lowest it has ever been is 1.60
Sinistersky said:
I turned the KSM off in the Kernel Auditor and the loadav dropped significantly. It should be removed because it serves no purpose really and changing it every boot is a pain As for the gmail service, I just limited it's wakelocks because it was too damn frequent. But what I am wondering is, how is your loadavg 0.8? mine is 2.28 1.93 2.12 4/1437 4960 ... I think I have a major problem somwhere The lowest it has ever been is 1.60
Click to expand...
Click to collapse
The loadavg depends on the apps you run. I have noticed that it spikes whenever gmail is doing the email sync or I am running videos from whatsapp etc.
So, don't worry about a larger value if you have been using the phone. The loadavg for idle phone should be close to 0, but it rarely is, because our phones are always doing something in background. The lowest I have seen it drop is 0.08, and then gmail brings it up whenever it does a sync. I have several accounts linked in gmail (yahoo, hotmail, google, work), so its understandable.
One thing you can do to monitor is to see which processes are eating up the CPU with:
Code:
ps | sort -n -k5 | tail -n 5
top -m 3 -s cpu -n 2 -d 2 | grep -v "^$" | tail -n 6
It will show 5 top memory consumers and 3 top CPU consumers. Put it in a shell script and run it periodically to collect some stats.
I have noticed dhd_dpc taking up CPU cycles. But I need the wifi... So, unless and until someone comes along and optimizes the kernel driver for wifi on M7, that's what we got! I don't think anybody would touch the driver code for m7. So, some things will never get fixed for m7.
On the other hand, the cycles eaten by system_ui and system_server are inexcusable! They can be fixed by CM/Google in non-device specific code. May be that will happen as CM13/Marshmallow matures.
devsk said:
The loadavg depends on the apps you run. I have noticed that it spikes whenever gmail is doing the email sync or I am running videos from whatsapp etc.
So, don't worry about a larger value if you have been using the phone. The loadavg for idle phone should be close to 0, but it rarely is, because our phones are always doing something in background. The lowest I have seen it drop is 0.08, and then gmail brings it up whenever it does a sync. I have several accounts linked in gmail (yahoo, hotmail, google, work), so its understandable.
One thing you can do to monitor is to see which processes are eating up the CPU with:
Code:
ps | sort -n -k5 | tail -n 5
top -m 3 -s cpu -n 2 -d 2 | grep -v "^$" | tail -n 6
It will show 5 top memory consumers and 3 top CPU consumers. Put it in a shell script and run it periodically to collect some stats.
I have noticed dhd_dpc taking up CPU cycles. But I need the wifi... So, unless and until someone comes along and optimizes the kernel driver for wifi on M7, that's what we got! I don't think anybody would touch the driver code for m7. So, some things will never get fixed for m7.
On the other hand, the cycles eaten by system_ui and system_server are inexcusable! They can be fixed by CM/Google in non-device specific code. May be that will happen as CM13/Marshmallow matures.
Click to expand...
Click to collapse
Thanks for the info. I'll try to collect some stats on my device to see what is putting a strain on the battery so much. As for the system, it has always been that way ever since lollipop came. Nobody bothers to fix it, and I am beginning to think that maybe they didn't notice the numbers or the switch from 5.0 to 6.0 happened so fast they just went "meh, we'll leave it and maybe fix it later if we remember". I never understood why most of the ROM and kernel makers try to add more new stuff without even fixing and optimizing the things that are the core of the new optimizations and add-ons. It just makes no sense to try to push something new on a broken foundation to begin with. The M7 is a great phone even now, and I had it for 3 years now. Naturally, the battery is very old now and the moment i start using the screen it drops 20% in an hour or so, making me have at most 3 hours of screen time. But with background usage restriction I get by on a daily basis just barely. Fixing the system cycles would be heavenly for me, but alas, maybe it will never happen, sadly