Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
Metallice
Old
(Last edited by Metallice; 25th May 2012 at 07:41 AM.)
#41  
Metallice's Avatar
Recognized Contributor - OP
Thanks Meter 3197
Posts: 2,581
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by nphil View Post
I tried AOKP for a while, it crashed quite a bit and CPU usage was really high due to lack of hardware acceleration in the UI. Do developers have everything they need for hardware acceleration on AOSP ROMs? Is it just a lack of people working on it?

BTW,if you need beta testers for your ROM+kernel, I would be happy to help!
I was referring to my phone. I love AOKP on my Gnex, but to be honest AOKP is pretty bad on tablets in general. I believe the drivers and libs are all there from the TW kernel source, but they have tto be hacked and reverse engineered or something. Also asfaik the only person really working on it is xoomdev.

Sure! Thanks. Ill post here when I need testers. I just finished finals so I will actually have time to work on it. It's just so much trial and error to figure out what works and what doesn't. Googling is often unhelpful as a bunch of them only give results in regards to GS3 leaks etc. I still want to theme atleast 50% of what I want to do before id consider posting it. Also working on the kernel for it blah blah blah.

Sent from my GT-P3113 using XDA Premium HD app
 
Metallice
Old
#42  
Metallice's Avatar
Recognized Contributor - OP
Thanks Meter 3197
Posts: 2,581
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by distINCtINC View Post
I would say unlikely. I don't like the idea of building a kernel for an device I can't actually test on to make sure things work. Sorry. Would be happy to help anyone willing to fork my kernel source tho.

Sent from my Galaxy Nexus using xda premium
Yes. You should see a boot.img in the zip.

Sent from my GT-P3113 using XDA Premium HD app
 
denk
Old
#43  
Member
Thanks Meter 0
Posts: 50
Join Date: Mar 2009
Hi there,

Thanks for the kernel - runs great with stock rooted rom.

One question: is it possible to force BT to stay connected when connecting to Wifi? Everytime wifi is connected it drops the BT connection to whatever device it was paired with.

here is a LogCat dump - wifi is connected and attempting to connect with a BT device.

Code:
05-29 23:38:22.085: D/InputReader(187): Input event: value=1
05-29 23:38:22.085: I/power(187): *** set_screen_state 1
05-29 23:38:22.085: D/KeyguardViewMediator(187): onScreenTurnedOn, seq = 2
05-29 23:38:22.085: D/KeyguardViewMediator(187): notifyScreenOnLocked
05-29 23:38:22.085: D/KeyguardViewMediator(187): handleNotifyScreenOn
05-29 23:38:22.085: D/KeyguardViewManager(187): onScreenTurnedOn()
05-29 23:38:22.085: D/SensorManager(187): registerListener :: handle = 1  name= BMA254 Acceleration Sensor delay= 66667 Listener= android.view.WindowOrientationListener$SensorEventListenerImpl@4177d978
05-29 23:38:22.085: D/PowerManagerService(187): Screen__On : userActivity  uid=1000 pid=187   myUID=1000 myPID=187 myTID=237
05-29 23:38:22.085: D/PowerManagerService(187): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=false
05-29 23:38:22.085: D/PowerManagerService(187): enableLightSensorLocked enable=true mAutoBrightessEnabled=false
05-29 23:38:22.085: D/PowerManagerService(187): sendNotificationLocked on=true
05-29 23:38:22.085: D/PowerManagerService(187): mNotificationTask : on
05-29 23:38:22.085: I/WindowManager(187): No lock screen!
05-29 23:38:22.085: I/PowerManagerService(187): Ulight 3->3|1
05-29 23:38:22.109: I/power(187): *** acquire_dvfs_lock : lockType : 1  freq : 1008000 
05-29 23:38:22.109: D/PowerManagerService(187): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT  frequency : 1008000  uid : 1000  pid : 187  tag : ActivityManager
05-29 23:38:22.109: W/ActivityManager(187): mDVFSLock.acquire()
05-29 23:38:22.289: D/InputReader(187): Input event: value=0
05-29 23:38:22.437: D/lights(187): write_int /sys/class/backlight/panel/brightness = 12
05-29 23:38:22.437: D/lights(187): write_int /sys/class/backlight/panel/brightness = 25
05-29 23:38:22.437: D/SurfaceFlinger(94): Screen about to return, flinger = 0x80bac0
05-29 23:38:22.437: I/WifiEnabler(1196): Resume : 3
05-29 23:38:22.445: I/BluetoothPolicyService(187): isBluetoothEnabled 
05-29 23:38:22.453: D/LocalBluetoothManager(1196): setting foreground activity to non-null context
05-29 23:38:22.453: V/AudioHardwareTinyALSA(97): setParameters(screen_state=on)
05-29 23:38:22.453: D/lights(187): write_int /sys/class/backlight/panel/brightness = 38
05-29 23:38:22.453: D/BluetoothPan(1196): getState(BC:B1:F3:7E:73:55)
05-29 23:38:22.453: D/STATUSBAR-NotificationService(187): ACTION_SCREEN_ON
05-29 23:38:22.453: D/STATUSBAR-NotificationService(187): updateLightsLocked() : Turn off notification light
05-29 23:38:22.468: D/lights(187): write_int /sys/class/backlight/panel/brightness = 51
05-29 23:38:22.484: D/lights(187): write_int /sys/class/backlight/panel/brightness = 63
05-29 23:38:22.500: D/lights(187): write_int /sys/class/backlight/panel/brightness = 76
05-29 23:38:22.515: D/lights(187): write_int /sys/class/backlight/panel/brightness = 89
05-29 23:38:22.531: D/lights(187): write_int /sys/class/backlight/panel/brightness = 102
05-29 23:38:22.554: D/lights(187): write_int /sys/class/backlight/panel/brightness = 114
05-29 23:38:22.554: V/AudioPolicyManagerBase(97): getNewDevice() selected device 0
05-29 23:38:22.554: V/AudioPolicyManagerBase(97): getDeviceForStrategy() from cache strategy 0, device 2
05-29 23:38:22.554: D/VolumePanel(187): onVolumeChanged(streamType: 3, flags: 64)
05-29 23:38:22.562: V/AudioPolicyManagerBase(97): getNewDevice() selected device 0
05-29 23:38:22.562: V/AudioPolicyManagerBase(97): getDeviceForStrategy() from cache strategy 0, device 2
05-29 23:38:22.562: D/AudioService(187): getStreamVolume(3)
05-29 23:38:22.562: V/AudioPolicyManagerBase(97): getNewDevice() selected device 0
05-29 23:38:22.562: V/AudioPolicyManagerBase(97): getDeviceForStrategy() from cache strategy 0, device 2
05-29 23:38:22.562: V/AudioPolicyManagerBase(97): getNewDevice() selected device 0
05-29 23:38:22.562: V/AudioPolicyManagerBase(97): getDeviceForStrategy() from cache strategy 0, device 2
05-29 23:38:22.562: D/AudioService(187): getStreamVolume(3)
05-29 23:38:22.562: D/VolumePanel(187): VolumePanel onVolumeChanged index : 0
05-29 23:38:22.562: D/VolumePanel(187): call resetTimeout
05-29 23:38:22.570: D/lights(187): write_int /sys/class/backlight/panel/brightness = 127
05-29 23:38:22.570: D/comsamsungapp(1680): [MSC_Accu]>>> WS:57 [0:0] act:androidintentactionSCREEN_ON
05-29 23:38:22.585: D/lights(187): write_int /sys/class/backlight/panel/brightness = 140
05-29 23:38:22.593: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:437 [0:0] onReceive@ widgetappweatherclockactionSERVICE_SCREEN_ON
05-29 23:38:22.593: D/comsamsungapp(1680): [MSC_Accu]>>> WIM:53 [0:0] AccuWeatherClockWidgetID_Length
05-29 23:38:22.593: D/comsamsungapp(1680): [MSC_Accu]>>> WIM:54 [0:0] getPrefIDs@lngth:1
05-29 23:38:22.601: D/comsamsungapp(1680): [MSC_Accu]>>> WIM:60 [0:0] getPrefIDs@Ids1:1
05-29 23:38:22.601: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:429 [0:0] !!! refreshhandler is null !!!
05-29 23:38:22.601: D/lights(187): write_int /sys/class/backlight/panel/brightness = 153
05-29 23:38:22.609: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:2443 [0:0] cityId:246854
05-29 23:38:22.617: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:1887 [0:0] WthrDt:1 2130903097 false
05-29 23:38:22.617: D/lights(187): write_int /sys/class/backlight/panel/brightness = 165
05-29 23:38:22.617: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:1898 [0:0] mWthrCnt:1
05-29 23:38:22.625: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:1934 [0:0] onReceive cityId:246854
05-29 23:38:22.632: D/lights(187): write_int /sys/class/backlight/panel/brightness = 178
05-29 23:38:22.640: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:2775 [0:0] mainLayoutId:3002, icon : 3, bgID : 2130837710
05-29 23:38:22.648: D/lights(187): write_int /sys/class/backlight/panel/brightness = 191
05-29 23:38:22.664: D/lights(187): write_int /sys/class/backlight/panel/brightness = 204
05-29 23:38:22.679: D/lights(187): write_int /sys/class/backlight/panel/brightness = 216
05-29 23:38:22.695: D/comsamsungapp(1680): [MSC_Accu]>>> WWP:2177 [0:0] ApWdgId:1
05-29 23:38:22.695: D/lights(187): write_int /sys/class/backlight/panel/brightness = 229
05-29 23:38:22.710: D/lights(187): write_int /sys/class/backlight/panel/brightness = 242
05-29 23:38:22.726: D/lights(187): write_int /sys/class/backlight/panel/brightness = 255
05-29 23:38:22.726: I/PowerManagerService(187): Light Animator Finished curIntValue=255
05-29 23:38:23.257: D/Tethering(187): interfaceLinkStateChanged wlan0, true
05-29 23:38:23.257: D/Tethering(187): interfaceStatusChanged wlan0, true
05-29 23:38:23.585: W/PowerManagerService(187): Timer 0x3->0x3|0x0
05-29 23:38:23.820: E/Watchdog(187): !@Sync 11
05-29 23:38:24.132: I/InputReader(187): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.17 ]
05-29 23:38:24.132: I/InputDispatcher(187): Delivering touch to current input target: action: 0x0
05-29 23:38:24.132: I/InputDispatcher(187): Delivering touch to current input target: action: 0x0
05-29 23:38:24.132: E/lights(187): write_int failed to open /sys/class/sec/sec_touchkey/brightness
05-29 23:38:24.132: I/PowerManagerService(187): Ulight 3->7|0
05-29 23:38:24.132: D/PowerManagerService(187): setLightBrightness : mButtonLight : 255
05-29 23:38:24.203: I/InputReader(187): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
05-29 23:38:24.203: I/InputDispatcher(187): Delivering touch to current input target: action: 0x1
05-29 23:38:24.203: I/InputDispatcher(187): Delivering touch to current input target: action: 0x1
05-29 23:38:24.351: D/BluetoothPan(1196): getState(BC:B1:F3:7E:73:55)
05-29 23:38:24.351: D/BluetoothPan(1196): getConnectedDevices()
05-29 23:38:24.351: D/BluetoothPan(1196): connect(BC:B1:F3:7E:73:55)
05-29 23:38:24.351: D/BluetoothPanProfileHandler(187): connect PAN(/org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55)
05-29 23:38:24.359: D/BluetoothPanProfileHandler(187): Pan Device state : device: BC:B1:F3:7E:73:55 State:0->1
05-29 23:38:24.359: D/BluetoothService(187): sendConnectionStateChange - MDM3.0 inside edm TAGS
05-29 23:38:24.359: D/BluetoothService(187): CONNECTION_STATE_CHANGE: device: 0 -> 1
05-29 23:38:24.359: V/BluetoothService.cpp(187): connectPanDeviceNative
05-29 23:38:24.359: D/BluetoothPanProfileHandler(187): connecting to PAN
05-29 23:38:24.359: D/CachedBluetoothDevice(1196): Command sent successfully:CONNECT Address:mDevice Profile:PAN
05-29 23:38:24.382: V/BluetoothEventManager(1196): Received android.bluetooth.pan.profile.action.CONNECTION_STATE_CHANGED
05-29 23:38:24.382: D/CachedBluetoothDevice(1196): onProfileStateChanged: profile PAN newProfileState 1
05-29 23:38:24.382: D/BluetoothPan(1196): getState(BC:B1:F3:7E:73:55)
05-29 23:38:25.117: I/power(187): *** release_dvfs_lock : lockType : 1 
05-29 23:38:25.117: D/PowerManagerService(187): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released 
05-29 23:38:25.117: W/ActivityManager(187): mDVFSLock.release()
05-29 23:38:25.632: W/PowerManagerService(187): Timer 0x7->0x3|0x0
05-29 23:38:25.632: E/lights(187): write_int failed to open /sys/class/sec/sec_touchkey/brightness
05-29 23:38:25.632: I/PowerManagerService(187): Ulight 7->3|0
05-29 23:38:25.632: D/PowerManagerService(187): setLightBrightness : mButtonLight : 0
05-29 23:38:25.921: V/BluetoothEventLoop.cpp(187): event_filter: Received signal org.bluez.Device:PropertyChanged from /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55
05-29 23:38:25.921: D/BluetoothEventLoop(187): Device property changed
05-29 23:38:25.937: D/BluetoothNotiBroadcastReceiver(1196): onReceive
05-29 23:38:25.968: D/Tethering(187): interfaceAdded bnep0
05-29 23:38:25.968: D/Tethering(187): bnep0 is not a tetherable iface, ignoring
05-29 23:38:25.984: D/Tethering(187): interfaceLinkStateChanged bnep0, false
05-29 23:38:25.984: D/Tethering(187): interfaceStatusChanged bnep0, false
05-29 23:38:25.992: D/Tethering(187): interfaceLinkStateChanged bnep0, true
05-29 23:38:25.992: D/Tethering(187): interfaceStatusChanged bnep0, true
05-29 23:38:25.992: V/BluetoothEventLoop.cpp(187): onPanDeviceConnectionResult
05-29 23:38:25.992: V/BluetoothEventLoop.cpp(187): ... Pan Device Path = /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55, result = 1004
05-29 23:38:25.992: D/BluetoothEventLoop(187): onPanDeviceConnectionResult /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55 1004
05-29 23:38:25.992: V/BluetoothEventLoop.cpp(187): event_filter: Received signal org.bluez.Network:PropertyChanged from /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55
05-29 23:38:25.992: D/BluetoothEventLoop(187): Pan Device property changed: address  property: Connected value: true
05-29 23:38:25.992: V/BluetoothEventLoop.cpp(187): event_filter: Received signal org.bluez.Network:PropertyChanged from /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55
05-29 23:38:25.992: D/BluetoothEventLoop(187): Pan Device property changed: address  property: Interface value: bnep0
05-29 23:38:25.992: D/BluetoothPanProfileHandler(187): Pan Device state : device: BC:B1:F3:7E:73:55 State:1->2
05-29 23:38:25.992: D/BluetoothService(187): sendConnectionStateChange - MDM3.0 inside edm TAGS
05-29 23:38:25.992: D/BluetoothService(187): STATE_CONNECTED
05-29 23:38:25.992: V/BluetoothEventManager(1196): Received android.bluetooth.pan.profile.action.CONNECTION_STATE_CHANGED
05-29 23:38:26.000: D/BluetoothService(187): CONNECTION_STATE_CHANGE: device: 1 -> 2
05-29 23:38:26.000: D/CachedBluetoothDevice(1196): onProfileStateChanged: profile PAN newProfileState 2
05-29 23:38:26.000: V/BluetoothEventLoop.cpp(187): event_filter: Received signal org.bluez.Network:PropertyChanged from /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55
05-29 23:38:26.000: D/BluetoothEventLoop(187): Pan Device property changed: address  property: UUID value: 00001116-0000-1000-8000-00805f9b34fb
05-29 23:38:26.000: D/BluetoothPan(1196): getState(BC:B1:F3:7E:73:55)
05-29 23:38:26.015: I/dhcpcd(2533):  dhcp main start  
05-29 23:38:26.054: I/dhcpcd(2533): get_bssidinfo bnep0 failed
05-29 23:38:26.187: I/dhcpcd(2533): list file open Error `': No such file or directory
05-29 23:38:26.406: D/DhcpInfoInternal(187): makeLinkProperties with empty dns2!
05-29 23:38:26.421: D/BluetoothPan(187): getConnectedDevices()
05-29 23:38:26.421: D/BluetoothPan(187): disconnect(BC:B1:F3:7E:73:55)
05-29 23:38:26.421: D/BluetoothPanProfileHandler(187): disconnect PAN(/org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55)
05-29 23:38:26.421: D/ConnectivityService(187): ConnectivityChange for BLUETOOTH_TETHER: CONNECTED/CONNECTED
05-29 23:38:26.429: D/BluetoothPanProfileHandler(187): Pan Device state : device: BC:B1:F3:7E:73:55 State:2->3
05-29 23:38:26.429: V/BluetoothEventManager(1196): Received android.bluetooth.pan.profile.action.CONNECTION_STATE_CHANGED
05-29 23:38:26.429: D/BluetoothService(187): sendConnectionStateChange - MDM3.0 inside edm TAGS
05-29 23:38:26.429: D/CachedBluetoothDevice(1196): onProfileStateChanged: profile PAN newProfileState 3
05-29 23:38:26.429: D/BluetoothPan(1196): getState(BC:B1:F3:7E:73:55)
05-29 23:38:26.437: D/BluetoothService(187): CONNECTION_STATE_CHANGE: device: 2 -> 3
05-29 23:38:26.437: V/BluetoothService.cpp(187): disconnectPanDeviceNative
05-29 23:38:26.445: D/Tethering(187): interfaceLinkStateChanged bnep0, false
05-29 23:38:26.445: D/Tethering(187): interfaceStatusChanged bnep0, false
05-29 23:38:26.453: V/BluetoothEventLoop.cpp(187): onPanDeviceConnectionResult
05-29 23:38:26.453: V/BluetoothEventLoop.cpp(187): ... Pan Device Path = /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55, result = 1004
05-29 23:38:26.453: D/BluetoothEventLoop(187): onPanDeviceConnectionResult /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55 1004
05-29 23:38:26.453: W/Netd(91): No subsystem found in netlink event
05-29 23:38:26.453: D/Tethering(187): interfaceRemoved bnep0
05-29 23:38:26.453: E/Tethering(187): attempting to remove unknown iface (bnep0), ignoring
05-29 23:38:26.453: D/NetlinkEvent(91): Unexpected netlink message. type=0x11
05-29 23:38:26.484: V/BluetoothEventLoop.cpp(187): event_filter: Received signal org.bluez.Network:PropertyChanged from /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55
05-29 23:38:26.484: D/BluetoothEventLoop(187): Pan Device property changed: address  property: Connected value: false
05-29 23:38:26.687: D/BluetoothPanProfileHandler(187): Pan Device state : device: BC:B1:F3:7E:73:55 State:3->0
05-29 23:38:26.687: V/BluetoothEventManager(1196): Received android.bluetooth.pan.profile.action.CONNECTION_STATE_CHANGED
05-29 23:38:26.687: D/CachedBluetoothDevice(1196): onProfileStateChanged: profile PAN newProfileState 0
05-29 23:38:26.695: D/BluetoothAdapterStateMachine(187): BluetoothOn process message: 52
05-29 23:38:26.695: D/BluetoothService(187): sendConnectionStateChange - MDM3.0 inside edm TAGS
05-29 23:38:26.695: D/BluetoothService(187): STATE_DISCONNECTED
05-29 23:38:26.695: D/BluetoothService(187): CONNECTION_STATE_CHANGE: device: 3 -> 0
05-29 23:38:26.695: D/ConnectivityService(187): ConnectivityChange for BLUETOOTH_TETHER: DISCONNECTED/DISCONNECTED
05-29 23:38:26.695: D/ConnectivityService(187): Attempting to switch to WIFI
05-29 23:38:26.703: D/BluetoothPan(1196): getState(BC:B1:F3:7E:73:55)
05-29 23:38:26.710: W/NetworkStats(187): dropping UID delta from unknown iface: iface=bnep0 uid=0 set=DEFAULT tag=0x0 rxBytes=0 rxPackets=0 txBytes=76 txPackets=1 operations=0
05-29 23:38:26.710: V/BluetoothEventLoop.cpp(187): event_filter: Received signal org.bluez.Network:PropertyChanged from /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55
05-29 23:38:26.710: D/BluetoothEventLoop(187): Pan Device property changed: address  property: Interface value: 
05-29 23:38:26.710: V/BluetoothEventLoop.cpp(187): event_filter: Received signal org.bluez.Network:PropertyChanged from /org/bluez/884/hci0/dev_BC_B1_F3_7E_73_55
05-29 23:38:26.710: D/BluetoothEventLoop(187): Pan Device property changed: address  property: UUID value: 
05-29 23:38:26.710: E/WifiP2pStateTracker(187): getNetworkInfo : NetworkInfo: type: wifi_p2p[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false
05-29 23:38:26.718: E/WifiP2pStateTracker(187): getNetworkInfo : NetworkInfo: type: wifi_p2p[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false
05-29 23:38:26.726: E/WifiP2pStateTracker(187): getNetworkInfo : NetworkInfo: type: wifi_p2p[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false
05-29 23:38:26.734: E/WifiP2pStateTracker(187): getNetworkInfo : NetworkInfo: type: wifi_p2p[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false
 
Metallice
Old
#44  
Metallice's Avatar
Recognized Contributor - OP
Thanks Meter 3197
Posts: 2,581
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by denk View Post
Hi there,

Thanks for the kernel - runs great with stock rooted rom.

One question: is it possible to force BT to stay connected when connecting to Wifi? Everytime wifi is connected it drops the BT connection to whatever device it was paired with.

here is a LogCat dump - wifi is connected and attempting to connect with a BT device.
Seems like it might be something more ROM related but I'll look into it. A DMESG or KMSG would be more helpful in regards to the kernel.

Sent from my Galaxy Nexus using xda premium
 
ruebarb
Old
#45  
ruebarb's Avatar
Member
Thanks Meter 11
Posts: 68
Join Date: Oct 2007
I get stuck at the Galaxy 7.0 screen, tried without wipe, then tried with wipe cache partition and dalvik cache. Still no luck.
 
Metallice
Old
#46  
Metallice's Avatar
Recognized Contributor - OP
Thanks Meter 3197
Posts: 2,581
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by ruebarb View Post
I get stuck at the Galaxy 7.0 screen, tried without wipe, then tried with wipe cache partition and dalvik cache. Still no luck.
Model number? Rom?

Sent from my GT-P3113
 
Phatphool
Old
(Last edited by Phatphool; 30th May 2012 at 11:55 PM.)
#47  
Member
Thanks Meter 5
Posts: 59
Join Date: Jun 2011
My bad!! Sorry too many tabs opened!! Wrong post!!
 
ruebarb
Old
#48  
ruebarb's Avatar
Member
Thanks Meter 11
Posts: 68
Join Date: Oct 2007
Quote:
Originally Posted by distINCtINC View Post
Model number? Rom?

Sent from my GT-P3113
GT-P3113TS

Stock Rom

Sent from my GT-P3113 using XDA
 
scottx .
Old
#49  
scottx .'s Avatar
Senior Member
Thanks Meter 592
Posts: 1,808
Join Date: Jun 2011
Location: San Antonio, Texas
Works good with AOKP #38 that was released last night. (06/03/12)

Running it now.
The Following User Says Thank You to scottx . For This Useful Post: [ Click to Expand ]
 
Metallice
Old
#50  
Metallice's Avatar
Recognized Contributor - OP
Thanks Meter 3197
Posts: 2,581
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by ruebarb View Post
GT-P3113TS

Stock Rom

Sent from my GT-P3113 using XDA
It is possible that your tablet just cant handle the gpu overclock. Otherwise without a dmesg dump i cant say for sure. (adb shell dmesg > dmesg.txt)

Sent from my GT-P3113 using xda premium

 
Post Reply+
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...