Database Develop

[Q] How to fix Bluetooth on CM7?

Hey there, so i recently just flashed CM7 (cm_captivatemtd_full-133.zip). I used the method shown in the MobileTechVideos, using ODIN as well as the Speedstock kernal for the PDA. Everything worked out great! Backed up my apps via Titanium and got google apps through clockwork. Im loving CM7, but the problem is Bluetooth refuse to turn on! Every time i try and enable Bluetooth nothing happens. The icon gets greyed out and then reappears but nothing changes. Anyone know a fix to this?! Thanks!
I've tried fixing the permissions through Rom manager and rebooted a number of times. Nothing works. Also whenever i reboot the email app just FC on me :/
Edit: The process com.android.phone has stopped unexpectly shows up everytime i reboot as well!

Try to flash it again or try a previous nightly.
Sent from my Captivate

Alright, i'll give that a whirl and keep you posted! Thanks!

Did this work?
I've had the same problem, re-flashed numerous times to try and clear it (wiped my cache, dalvik, etc) but still it always happens, and then the FCs for com.android.phone keep coming intermittently.
So since my last flash, I haven't touched bluetooth, and guess what? No FC's at all.
Anybody have another idea?
I'm on 7.1.0 from 10-10-2011.

[Q] Any reason for ICS to break itself?

Hi there,
Have been using ICS on my galaxy s for a couple of months. However this is the second time out of the blue it's decided not to boot for me.
The first time I thought it was because I dropped it and reinstalled gingerbread through Odin, then went back to ICS which was a very lengthy process.
I haven't installed anything, and now after just using the phone as per normal and it's decided to stop working? Any tricks I can do?
Basically it boots up, gets to the loading screen and just does that forever. I can boot into recovery but not sure what I should be doing next.

You could try reflashing your rom from recovery .

I think it's necessary to know which ICS-rom, for example slim ICS 2.8 needs to flash kernel first and then the rom ...
Sent from my GT-I9000 using XDA

Thanks imgibby123, if that is the last resort I may as well try it.
I've actually forgotton which one it is, I flashed ages ago and was very stable it just literally broke itself (a number of apps where crashing this mornign (reader, gmail etcc), so I held down the power button, turned it off as per normal, now the phone won't get passed the loading boot animation).
It was cynogen something, team platypus - I feel stupid I can't recall the details. But the ROM is still on there so I'll try reflashing from recovery.
Edit: It's ICS 4.0.3 RC3.1, so obviously still a RC but still! It worked flawlessly for months before
Thanks for the help.

Booting problem

Hi
I'm having problems when turning on my galaxy note. I was using Paranoid Android J.B. and was playing Death Trigger happily when suddenly the screen started acting like an old T.V. I got scared so I exited the game and rebooted the phone and got stuck so I re restarted the phone by long pressing the power button but this time it didn't boot but only appeared quickly the galaxy note N-7000 screen and turned off.
At first I charged the phone thinking maybe it was low on battery but happened the same. Then I entered to recovery mode after pressing the buttons a longer than usual time and installed P.A. CM9. Everything was ok but 15 minutes later I ran off of battery and the phone turned off. I charged again the phone and after a few minutes I tried to turn on the phone but I couldn't because again all I got was a quick flash of the galaxy note screen.
I entered again on the recovery mode but this time I only selected the reboot phone option and it turned on as always.
Does someone knows what could it be or how to fix it?
Would you recommend me to install stock rom and unroot the phone just in case?
Thanks four your help

Hello perri.etb, you could first try another custom firmware and see if the exact problem persists. You could then try a stock firmware just to double-check.

YLNdroid said:
Hello perri.etb, you could first try another custom firmware and see if the exact problem persists. You could then try a stock firmware just to double-check.
Click to expand...
Click to collapse
That's why I installed Paranoid Android CM9. I have used it some time and know that it works perfectly but yeah, maybe installing a TW rom could work. I'll try.
Edit
I installed another rom and everything worked fine. Now I installed again P.A. CM9 and everything is fine.
Thanks.

perri.etb said:
Edit
I installed another rom and everything worked fine. Now I installed again P.A. CM9 and everything is fine.
Thanks.
Click to expand...
Click to collapse
Hello perri.etb, I am glad you have resolved the issue.

[Q] My phone won't boot (Not a bootloop problem)

I have been using RemICS 1.3 with Semaphore kernel on my phone for a few months. I had a few problems with bootloop at first, which was solved completely after i flashed the Semaphore kernel and my phone has been running smoothly ever since.
However, today my phone started freezing and giving errors out of nowhere. I open a simple application like alarm clock and it says the application is stopped. I was only be able to open a few applications. So, I rebooted the phone thinking it would go back to normal. Unfortunately, rebooting revealed that my phone no longer can boot. It passes the kernel screen, goes to the RemICS animation and gets stuck there. Since I could go into Recovery Mode I have tried to restore from the backup I had from 10 days ago when my phone was running perfectly. Did not work. I had another backup from July, did not work, actually made things worse by stucking my phone at Samsung screen. Wiped cache, Wiped dalvik cache, did not work.. Made things worse by putting my phone into loop boot. I have tried flashing Devil kernel and another version of Semaphore kernel. Did not work.. Phone back into being stuck at RemICS logo.
Nothing I do seems to work. It just won't boot. I could try flashing a fresh firmware but I have some info on my memo application that i need to save as well as some text messages.
I really don't know how this happened out of nowhere. How can I save my data? Please help?

I've tried lots of ROMs, and been stuck in boot loops many times.
I've always got out of them by using Odin, and trying different kernels until one works, semaphore, devil, and an old GB one. Out of all the boot loops I've been stuck in there's never been a single time that one of those kernels hasn't worked...
Maybe I've just been lucky??
Edit: on reading again tho it looks to me that its your ROM that is the problem not the kernel.
I recommend using SMS Backup+ (free) from the play store next time
Sent from my GT-I9000 using Tapatalk 2

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!

I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.

I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?

Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....

Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.