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

Root serious FC issues, other things

Hello, again!

So after finally figuring out how the hell to work Odin and whatnot, I flashed my Behold with one of BH_MAN's ROMs in October, the "tweaked OTA" one. It worked gloriously for a few months, and I was so happy.

Lately, however, all sorts of built-in applications like Calendar, Phone, Dialer, etc. are FCing. I'll get Google Talk messages that flash in the notifications bar but when I open up the conversation, the new messages don't appear. I send emails through Gmail in places where I have two or three bars of 3G coverage and they get stuck infinitely in Drafts, where I can't send or delete them (resulting in my opening them on my laptop and dealing with them there). There are other things for sure, I just can't recall them right now. It's driving me up the wall and I'm THISCLOSE to throwing the dang thing out my window.

What do I do? Re-flash? Do I re-flash the same ROM or switch? Whatever it is, I can't use adb because it still refuses to work.

Please help me. I just have to make it to September, and then I can get whatever phone I want (you guys will have to help me decide when that rolls around).

♥
 
Try this first:

Clearning Dalvik-Cache from ADB
Quote:
adb shell
cd /data/dalvik-cache
rm -r *
reboot


Fixing Permissions via rom manager
Quote:
Download Rom manger from the market
click on fix permissions
 
As I said, adb doesn't work with my phone, and it's a completely separate issue from this. It's never worked.

I downloaded ROM Manager and when I attempted to fix permissions, it said, "An error occurred while attempting to run privileged commands!"
 
As I said, adb doesn't work with my phone, and it's a completely separate issue from this. It's never worked.

I downloaded ROM Manager and when I attempted to fix permissions, it said, "An error occurred while attempting to run privileged commands!"

Sounds like you don't have root privileges? You could try a factory reset or reboot to recovery, but of course you would loose your apps and data, something that would happen anyway if you re-flashed the ROM.

Also, correct me if I'm wrong, but I don't beleive BH_MAN released any of his roms based on the official 1.6 OTA kernel. Instead bearsfan85 used some of BH_Man's stuff(framework items and recovery) and tweaked the 1.6 OTA rom.
 
If I were you I would reflash a different rom or try the new recovery. Adb doesn't work for me either. So I try to live without it since I was never able to find an answer.
 
I did that on xp and had ever driver installed but when I downloaded the sdk it did not have adb application in it. So I downloaded it seperate but when I ran it in cmd it sais no devices connected. Idk what im doing wrong.
 
I did that on xp and had ever driver installed but when I downloaded the sdk it did not have adb application in it. So I downloaded it seperate but when I ran it in cmd it sais no devices connected. Idk what im doing wrong.

Just download a program called pdanet its a tethering program that will install the right drivers for adb to work and make sure you have daemon tools lite and of course the android SDK. Now when you open up a command prompt make sure to change directory, a example " cd/AndroidSDK/tools and what every you name the androidSDK folder and make sure your in the tools folder to run adb. Hope this helps..
 
You can also try unstalling a few of your larger applications and see if that settles down the phone behavior. A couple months I was getting "Wait / Force Close" notifications EVERY time that I turned on my phone, on different modules. Removed angry birds and a couple other large apps and the problem went away.
 
The post in which I described my adb problems is here: http://androidforums.com/behold-2-all-things-root/205311-error-device-not-found-adb.html? and nobody ever replied, leading me to believe nobody ever came up with a solution. I've given up hope on adb for now.

I know I didn't use bearsfan's ROM because I tried it but Phone fc'd every single time I opened it. So whatever it was it was definitely a BH_MAN ROM.

I'll try popping Angry Birds off (the Android version is SO SLOW anyway), and if that doesn't help I think I'll just re-flash it with another one. Any other suggestions are welcome...
 
The post in which I described my adb problems is here: http://androidforums.com/behold-2-all-things-root/205311-error-device-not-found-adb.html? and nobody ever replied, leading me to believe nobody ever came up with a solution. I've given up hope on adb for now.

I know I didn't use bearsfan's ROM because I tried it but Phone fc'd every single time I opened it. So whatever it was it was definitely a BH_MAN ROM.

I'll try popping Angry Birds off (the Android version is SO SLOW anyway), and if that doesn't help I think I'll just re-flash it with another one. Any other suggestions are welcome...

I just posted a possible solution to your ADB issue in case nobody has pointed out this option to you. I confess I'm an intermittent forum follower, and abandoned following the forums after BH_MAN initially stopped work on the BH2. Checked back in a couple weeks ago as a fluke to see what was new...
 
I just posted a possible solution to your ADB issue in case nobody has pointed out this option to you. I confess I'm an intermittent forum follower, and abandoned following the forums after BH_MAN initially stopped work on the BH2. Checked back in a couple weeks ago as a fluke to see what was new...

Thanks! I'll try that... next week when I have time to wrestle with it. I'll let you know how it goes for sure.
 
If you need your phone fixed and you can't get it working feel free to mail it to me. I'll have it fixed in about 2 min.
 
Back
Top Bottom