Hi guys
I've a Samsung Gt-i5510,
Something crashes at the background ramdomly, when wi-fi is on!
I mean it vibrates once, and 3-4 seconds later it vibrates twice, but it doesn't show "force close" warning.
How can I learn what is crashing and how can I fix it.
You can connect to the phone via adb (google it) and issue a "adb logcat" to see a realtime output of what's going on...
NRGZ28 said:
You can connect to the phone via adb (google it) and issue a "adb logcat" to see a realtime output of what's going on...
Click to expand...
Click to collapse
thanks I'll try that and after that I'll share the log in here, if I can't solve the problem.
Related
Hi All,
Not sure if this is the right place to post this but i'm going to try anyway:
I've just recently downloaded adbWireless on my x10 mini but on the load screen of the app i've only got half the page - the part that i actually need is hidden and i can't scroll down... obviously because of the screen size... is there any other way to show the rest?
Surely i can't be the only experiencing this?
Thx.
Nvm, i see they released an update which fixed it.
Has anybody got this to work on the Mini?
I´ve tried the app yesterday, but no success. Display issues commented earlier are fixed, but i can´t connect with the device. Tried to restart the tcpip 5555 port through adb shell when usb connected, but no luck (it always returns an error).
Exactly the same thing happening to me - although every now and then i get a widget popping up in the status bar saying that's it's been enabled.
Still can't connect to it though...
I made a tasker profile to scan face in every 15 seconds by using another plugin (smart stay). Some situations it gives "unable connect camera" error. When I run restart camera app I can fix this issue.
How do I fix "unable connect camera" error by using terminal command. Because I planned to run that command right after (after 5 seconds delay) tasker trigger face scan action.
Any help really appreciate.
Sent from my GT-I9300 using Tapatalk
go to engineer mode (may be *#*#3646633#*#*(dial it) in ur device)
beware to use it.... u can get unwanted outcomes
Hello everybody,
I was playing with SWApp Link when suddenly my watch restarted by itself and got stuck in the Omate TrueSmart logo... I can't turn it off and it's getting hot... isn't a way to restart it like a smartphone?? I don't have the screwdriver with me so I can't pull the battery off, and also I want to avoid that because of the warranty...
Any ideas?
Connect it to adb, type "adb reboot" in a command console.
I left home with the watch fully charged so I didn't bring the charger either...
I guess I'll have to wait until it dies or I arrive home and try to reboot it using adb... the thing is I already tried once to connect it to my Mac and see if adb recognized it but had no luck...
EDIT: Finally, battery's dead... I'll charge it once I arrive home... two days with my TrueSmart and already got a freeze... disappointing...
If that happens again, see if you can get a log while it hangs there with "adb logcat > ts1_freeze.txt"
I'll do that, thanks for the advise.
I now have a worse problem... My Bluetooth isn't working... I turn it on and it turns off immediately, I mean, I barely can see the switch changing from OFF to ON when it changes back to OFF.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Go into settings, disable quick boot under accessibility, and reboot.
This is actually a bug introduced in 4.2.2 and usually requires you to wipe cache to clear it out.
Thanks! :cyclops:
Should I enable it again? What is it for?
BeRniTo said:
Thanks! :cyclops:
Should I enable it again? What is it for?
Click to expand...
Click to collapse
Just keeps the device in hibernate for quick startup. If drivers crash, they can't be recovered without a power cycle.
Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Skytex said:
Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Click to expand...
Click to collapse
Connect the phone to the PC and then open a command prompt window where you installed ADB and run adb in the command prompt window and when it opens then type adb shell reboot recovery and see if it reboots to recovery mode but it requires that you have USB debugging enabled in developer options and if it's not enabled then there's nothing else you can do.
Its totally stock. Never installed adb on this phone
Skytex said:
Its totally stock. Never installed adb on this phone
Click to expand...
Click to collapse
Adb is "installed" on your computer, not phone. Adb/fastboot commands are delivered to the device.
https://developer.android.com/studio/releases/platform-tools
Hi
As title. I am trying g to activate more stars in gsam but adb doesn't see the phone. Any tips?
I install samsung driver and it work fine after that
s3fan said:
Hi
As title. I am trying g to activate more stars in gsam but adb doesn't see the phone. Any tips?
Click to expand...
Click to collapse
Make sure USB debugging is on. Update your drivers in Windows...and restart both phone and PC
Might have a bigger problem. Laptop doesn't even see the phone
You might also find that GSAM no longer loads after activating more stats. Googling around, there seems to be a known issue with Android 13 which prevents it working - I got it working once, but after a reboot it failed again. Developer no longer seems to be active unfortunately.
I might just leave it. Got it connected and seen after third cable. When trying to activate I keep getting exception messages and permissions not granted.
Would have been nice to see what's doing what (although if gsam crashes after more stats that mute anyway)
Cheers
Just got my phone yesterday and one of the 1st apps installed was GSAM Battery Monitor Pro, had NO issues with the adb commands to be able to use "app sucker." I am using Minimal ADB from XDA, am proficient in adb as that's all you could use on the T-Mobile G1 back in the day.