I have followed some threads regarding Bluetooth problems, but could not fix it.
I tried:
1. Flashing a new kernel (TheAceKernel-beta4) using the overclocked option when prompted.
2. Copying the files from Bluetooth.zip in Nooblar's post (http://forum.xda-developers.com/showthread.php?t=1657310&highlight=bluetooth)
to /system/etc/bluetooth folder in the root directory.
3. Tried but could not understand how to use the information and files for "CyanogenMod / android_device_samsung_cooper" on the following link (https://github.com/CyanogenMod/android_device_samsung_cooper) which seam to be related to the problem I have and are provided in the process I followed when flashing a new ROM to be able to get more internal space (http://forum.xda-developers.com/showthread.php?t=1543521)
I'm ok with how the phone works in general. My only problems are I cannot connect to Kies and BT will not start. The first I don't mind, but I use the BT to connect to the handsfree while driving the car and I use it a lot. Without it I'm bound to be one of those one-hand drivers out there who is going to crash into your car, so you better help me fix this... jajaja
I have a Samsung Ace GT-S5830LUBKPA with Android 2.3.7, Build Gingerbread
Installed:
- recovery-clockwork-5.0.2.6-galaxyace-fix
- AceGingerRoot
- CronMod-INT2EXT+_signed
- cm-7-20120930-NIGHTLY-cooper
- gapps-gb-20120317-237-signed
- cm-blackhawk-kernel and then TheAceKernel-beta4
Hope someone knows where I can find the solution if there is any. I am trying not to go through the hole process of reinstalling a different ROM since I barely made it last time and I don't want to mess up my phone again. But if that is the only solution, I'll do it.
Thanks!!
Solved! thanks anyway.
mushatrusha said:
I have followed some threads regarding Bluetooth problems, but could not fix it.
I tried:
1. Flashing a new kernel (TheAceKernel-beta4) using the overclocked option when prompted.
2. Copying the files from Bluetooth.zip in Nooblar's post (http://forum.xda-developers.com/showthread.php?t=1657310&highlight=bluetooth)
to /system/etc/bluetooth folder in the root directory.
3. Tried but could not understand how to use the information and files for "CyanogenMod / android_device_samsung_cooper" on the following link (https://github.com/CyanogenMod/android_device_samsung_cooper) which seam to be related to the problem I have and are provided in the process I followed when flashing a new ROM to be able to get more internal space (http://forum.xda-developers.com/showthread.php?t=1543521)
I'm ok with how the phone works in general. My only problems are I cannot connect to Kies and BT will not start. The first I don't mind, but I use the BT to connect to the handsfree while driving the car and I use it a lot. Without it I'm bound to be one of those one-hand drivers out there who is going to crash into your car, so you better help me fix this... jajaja
I have a Samsung Ace GT-S5830LUBKPA with Android 2.3.7, Build Gingerbread
Installed:
- recovery-clockwork-5.0.2.6-galaxyace-fix
- AceGingerRoot
- CronMod-INT2EXT+_signed
- cm-7-20120930-NIGHTLY-cooper
- gapps-gb-20120317-237-signed
- cm-blackhawk-kernel and then TheAceKernel-beta4
Hope someone knows where I can find the solution if there is any. I am trying not to go through the hole process of reinstalling a different ROM since I barely made it last time and I don't want to mess up my phone again. But if that is the only solution, I'll do it.
Thanks!!
Click to expand...
Click to collapse
Solved! thanks anyway.
Related
Hi! Just to share what happened to me recently.
My Legend is now sent to service. Don't know exactly what went wrong, but anyways.. I rooted it a couple of weeks ago. Been installing and trying out some ROMs ju find "the one" for me (I'm not new to this, been using rooted Magic and Hero earlier). Finally, I installed a ROM with busybox..so far so good. Then I rebooted my phone - FAIL! It didn't wake up again!
Finally I managed to reinstall a ROM by running "step1" from unlockr's "how to root a legend"-Guide.. But the phone complained about me removing the SD-card. Figured, maybe it was because of unlockr's (Pauls??) testimage, so i ran the official RUU 1.31 and it installed fine (it didn't before). But no, sd-card was still "removed". tried a secont sd-card, same problem. Bought a new 16GB Class 10 card (previous cards were 2GB/8GB class 4) - No go. So - the conclusion is - my sd-card reader is gone. Not to worry, warranty will take care of it - but has this happened to others? If it has, maybe busybox isn't such a great idea on the legend for now.
Hi, nothing wrong with your phone, just an glitch in software that controls usb.
Happen twice for me after flash/root
quite easy to fix with adb and fastboot and terminal software.
se other post and howtos for usb bricked
just make sure that you got same HTC_xxx number to match your device.
http://forum.xda-developers.com/showthread.php?t=733713
/snakehult
snakehult said:
Hi, nothing wrong with your phone, just an glitch in software that controls usb.
Happen twice for me after flash/root
quite easy to fix with adb and fastboot and terminal software.
se other post and howtos for usb bricked
just make sure that you got same HTC_xxx number to match your device.
http://forum.xda-developers.com/showthread.php?t=733713
/snakehult
Click to expand...
Click to collapse
Oh, thanks.. then maybe I should try it before I send it in I actually read the posts before, but I didn't get how to hexedit the file :s I need the how-to for dummies maybe you can help me with that part?
Edit: I can try this later, need to re-root my phone first.. I have my goldcard at home, I'll do it later tonight (I get off work in 6 hours). I'd appreciate if you could help me with the hexedit thou. Now I get "INFOCID is HTC__Y13"
Edit2: since I no longer have root, is it even possible to root the pgone with the sd-controller disabled? :s
Edit3: This is gonna be a loooong post. sorted out the hexedit anyway, I'll se what I can manage :9 Thanks
Problem solved! Thank you for your help! Got back root, now it's just the flashing part left The problem was, I couldn't see my Sd card - at all. but that was easily fixed with the help of this forum! You're great!
I´m glad to help
Hi guys,
I'm in real need of someone who can help me out, a friend at work asked me to give him my phone (we both have the same galaxy s I9000) because he had a lag fix for it that was really easy... ok i thought... he ran it and now the phone is really fast!! great I think! The then problems started.
When it boots up it shows a new screen that says vibrant (this isn't a vibrant phone its a aussie model i9000)the first sign that things were wrong, then the headphone detection wasn't working, and worst of all i can connect it to a usb or even a power charger without the phone turning off and the battery icon appearing then turning off again indefinably. ohh shiiiit!
I think he may have run the vibrant file not the correct one for the international i9000 i have, so i find the voodoo website and rerun the update with the correct one (used a removable sd card get the files from my pc to the phone) BUT still have the same problems I also tried the “disable lagfix” to roll back but no luck.
SO if anyone can tell me how to dig myself out of this ever deepening hole I will be hugely indebted to you...BIG TIME!!
Are you sure he didn't switch his phone with yours.The lagfix doesn't need a new rom.
From my pov.
He installed vibrant firmware, then installed Voodoo.
Browse flash guides. You still have boot.
flash a new firmware, 2.1 imo. is the best, add voodoo and/or oclf v1.
Must ofc have root priv.
.hacker
Before I start this short tutorial let me say I'm no expert, but I am quite tech savvy (I work in IT and have done so for over 20 years).
I've been having major problems rooting my Galaxy Tab after it came back from Samsung following a Newbie mistake I made....
I have figured out how to root it after much searching and so decided to post this in the hope it might help someone else. Because I'm a new user I can't post links but the things you need are easy to find with Google if you follow my instructions below.
First some background....
When I first rooted my Galaxy Tab everything went perfectly, using SuperOneClick and following directions I found on one of the many forums.
Then after doing much reading I decided to jump into flashing a custom rom.
That too went perfectly.
Then I made a silly mistake and bricked my phone :-(
Fortunately Samsung here in Thailand fixed it whilst I waited in 45 minutes under warranty
So I had a virgin phone again and needed to root it again but this time everytime I tried nothing would happen... SuperOneClick would just sit there saying waiting for device.
This is what I did to fix the problem and gain root access to my Galaxy Tab once more.
1) Forget the instructions that start off with syncing to Kies
2) Go to Control Panel - Add Remove Programs - look for the Samsung USB drivers - Uninstall them.
3) locate and download these Samsung USB Drivers by searching google - Samsung_P1000_USB_Drivers.rar.html
4) Open the archive and find the setup file, run that to install the drivers.
5) Search Google for this page on Lifehacker - the-always-up+to+date-guide-to-rooting-any-android-phone - and follow their instructions for rooting with SuperOneClick. You will note they make no mention of connecting with Kies and disconnecting then reconnecting then..... blah blah blah.
They just say to connect in USB Debugging mode and run SuperOneClick.
This method worked for me first time after trying and failing with various versions of SuperOneClick, 2 versions of Kies, uninstalling and reinstalling....
Hopefully it will work for someone else that is having problems with the 'Waiting for device' message.
Good luck!
Sean
I wanted to connect my galaxy note to my iPad's Mywi for wifi (ad hoc) connection.
Thus i did the following steps:
- root galaxy note using zergrush
- downloaded xda's replacement wpa_suppliant
- downloaded root explorer
- uploaded the replacement wpa_suppliant file to the phone and replaced the original one at /systems/bin
After this, my phone was able to connect to iPad's Mywi, BUT connection is VERY unstable and gets disconnected every 5-10mins. Also it takes really long to get it connected back, like about 10-15mins for it to try to get connected.
I've tried re-doing the WHOLE of the steps above, INCLUDING re-rooting my phone, but to no avail. My Wifi function was working perfectly fine prior to this.
Can some kind souls out there please advice me if I've done anything wrong in my steps? Or if there's any way to solve this? thanks!
stock rom using very well.
I forgot to include, I've also flash stock rom, but to no avail. hope some kind souls can help me out
skylurker said:
I forgot to include, I've also flash stock rom, but to no avail. hope some kind souls can help me out
Click to expand...
Click to collapse
plz upload ur wpa_supplicant
Hi!
I have problem with my i9070. All starts with auto-rotation problem. It works only for few minutes on new system, or till I will turn on move functions. Then my g-sensor freeze. On GPS-status it shows nothing - no magnetic field, rotation, acceleration. When I start searching google about this problem I found that all HTC have similar problem (like this ) I tried to use that tips on my phone and figure out what's wrong. Unfortunately Samsung don't have files like /data/misc/AK8973Prms.txt . I start research and found files /etc/calib.dat /etc/sensor.dat /etc/param.dat wich seems to be related to the g-sensor. I watch how these files look like when g-sensor works on fresh system, and how they look like when g-sensor is corrupted. Again unfortunately nothing happened - the same permissions, the same values. Then I started to flash different roms, different kernels. I have 2.3.6 than 4.1.2, than back to 2.3.6 (by this tutorial ) than again 4.1.2. Than I installed this Kernel. My auto-rotation works for an hour without move functions (the best score). Now it's corrupted again.
I have a guess, that it's the driver faults, calibration problem, or sth in /etc folder. I'm not a dev, I can use terminal, give you all data I have. I wipe my phone hundreds times. One of my solution is to copy ALL data from another device (I don't know is it possible) and watch what happens. Maybe with this tools.
What I should do? Please help me, I will be very grateful!
Martin
martinan said:
Hi!
I have problem with my i9070. All starts with auto-rotation problem. It works only for few minutes on new system, or till I will turn on move functions. Then my g-sensor freeze. On GPS-status it shows nothing - no magnetic field, rotation, acceleration. When I start searching google about this problem I found that all HTC have similar problem (like this ) I tried to use that tips on my phone and figure out what's wrong. Unfortunately Samsung don't have files like /data/misc/AK8973Prms.txt . I start research and found files /etc/calib.dat /etc/sensor.dat /etc/param.dat wich seems to be related to the g-sensor. I watch how these files look like when g-sensor works on fresh system, and how they look like when g-sensor is corrupted. Again unfortunately nothing happened - the same permissions, the same values. Then I started to flash different roms, different kernels. I have 2.3.6 than 4.1.2, than back to 2.3.6 (by this tutorial ) than again 4.1.2. Than I installed this Kernel. My auto-rotation works for an hour without move functions (the best score). Now it's corrupted again.
I have a guess, that it's the driver faults, calibration problem, or sth in /etc folder. I'm not a dev, I can use terminal, give you all data I have. I wipe my phone hundreds times. One of my solution is to copy ALL data from another device (I don't know is it possible) and watch what happens. Maybe with this tools.
What I should do? Please help me, I will be very grateful!
Martin
Click to expand...
Click to collapse
Just know this - NEVER FLASH FIRMWARE FROM OTHER PHONE. You will get not just problem with sensor, but with everything.
And other thing, files that work on other phone will not work on our. You can copy/paste those file but it will mean nothing.
If it work like you think, we would have CM10.1 long time ago...
And you tried it with lot of software, you do not think it is some hardware issue? You have warranty?