• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Something wrong with my Behold 2


Android Enthusiast
Dec 9, 2009
Just for starters I have not rooted my phone or done anything of that nature. I've only had the phone for about two weeks. I've had an issue with it rebooting on me, though it was due to Locale since the first time it rebooted on me, that was the only thing I had done to the phone. The developer said there was an issue with the api's from samsung.

Well since then I havent used Locale, removed it, yet its rebooted just a couple of times(compared to 3 times in an hour when I had locale). Now today, I found my phone completely unresponsive. Black screen, no lights, dead. I pulled the battery, reinserted and tried to power on. It charged overnight so it cant be a dead battery.

When I plugged in, the battery charging logo didnt show up, so I did a reset(vol down+call+power), got the behold ii boot logo with Recover text, so I hit the home button. I then got a logo I've never seen. It was a logo of the phone with the warning exclamation point inside a triangle. I left the phone alone for a while but it was still there. I pulled the battery again, reinserted and powered on to a normal boot and the phone came on.

I'm going to talk to Tmobile about replacement as this is really weird and I havent seen anyone else say thing like this. And just for info, my battery does have the same serial number that others have found to have an issue with. I'll update with any other info I find out, but I'll probably just get a straight swap without any feedback.
I've been having soft reboots fairly frequently (average of once a day or so). I just got the frozen vibrating for the first time, I thought it was due to the locale sync plugin I just installed. I don't think having the phone replaced will do you any good. I'm pretty sure all of the problems with this phone would be resolved if Samsung just left it with a stock install of Android rather than f-ing everything up with TouchWiz.
Upvote 0
... I just got the frozen vibrating for the first time, I thought it was due to the locale sync plugin I just installed. ...

Yea that was the first thing I did that I thought was the cause of the issues, Locale. I did contact the developer, said Samsung confirmed the issue was with the api's they built. Also if anyone has tried the bluetooth file transfer program, that crashes also. Again probably due to bad api's. Hopefully the update fixes it. I would think thats probably why its taking a while to hear anymore about it.

I'm curious since Android is linux based, any apps out there to read log files?
Upvote 0


We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.