Hey I have a desire Z and my logcat says that the Wifi driver isnt loading. I want to replace it with one that works so my wifi actually turns on.
If you have a bcm4329.ko for the desire z could you please let me know?
Thanks
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
KCRic said:
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
Click to expand...
Click to collapse
Yeah I think it is normally part of a kernel but I cant seem to get this damn wifi to work no matter what I do, so I was thinking if anyone had one of the files kicking around I would just ADB overwrite the old one and see if it works.
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
theSpam said:
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
Click to expand...
Click to collapse
Still doesn't work
Really have no more ideas to fix my wifi.
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
ilostchild said:
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
Click to expand...
Click to collapse
I tried that too and it didn't do anything. Im really pulling at straws. Is there a program to test to make sure the hardware is actually good?
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
ilostchild said:
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
Click to expand...
Click to collapse
Yep, tried that twice. I even went back to stock between the reload.
One time I flashed it using the PC10IMG method and the other I used Clockwork (rom manager).
I really have no idea where to go at this point. I think I've exhausted all my ideas. Ive tried reflashing roms, kernels, and radios.
Was hoping someone had some diagnostic software that would test the hardware of the phone or something so at least then I would know if my actual hardware for the WiFi and Bluetooth was shot or not.
Thanks anyways.
Wow, I forgot about this thread over the weekend
Anyway, have you tried changing the permissions for the file? You can use 'fix permissions' in ROM Manager or clockwork or use Root Explorer to change the permissions. Of course if you're a terminal kind of guy you can chmod it.
Sometimes the permissions don't set correctly or, on some systems running linux, the permissions get changed for some reason. Maybe that's what's going no here, sounds like it anyway. Btw, make sure to reboot after changing the permissions because it won't work until you do.
has anyone fixed this issue where wifi stops working?
wifi not turning ON
Hello Everyone,
During the process of getting IP address from WiFi network, I received a "Error Massage" on my Alcatel OT-990. After this massage, WiFi started behaving abnormally. Sometimes it turned ON another time it did not. Now after a few weeks later, WiFi is not turning ON at all.
I have Tried following Solutions but nothing worked:
1. Did factory reset, erased system, cache etc and Flashed different ROMs (JB ot 990, ICS QME, QLTsar, 2.3.4, Telenor One touch 4.0.04) using Recovery many a times(From different Sources).>>Problem not solved
2. Updated my phone using alcatel update manager to 2.3.4>>> Problem not solved
3. Tried by changing permissions of BCM4329.KO, wpa_supplicant.confg etc every file related to wifi/wlan>>Problem not solved
4. Used WiFix Manager>>>Problem not solved.
Bluetooth and FM radio working all right.
If anybody knows about its solution ..please help me out.
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.
mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!
cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:
cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.
g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks
abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".
Hi guys... First post here as i seem to be stuck.. My phone is a DHD.
I'm not new to rooting or custom ROM's as i often change the ROM on my phone easily without any problems.. Done it 40-50 times now. Never had a problem. I'm used to the AAHK and know what i'm doing.. However, last night i got fed up of the ROM i had, been having some teething troubles lately so figured i'd put it back to stock and then root again and flash a new ROM, this always solves my problems. Now i always have a few others stored on my SD card incase one won't work (i sometimes get the bad installation, aborted) message and i'm not left without a working ROM, but wanted to unroot and put back to stock so opened the AAHK and proceeded as normal to do so ..
Everything was running fine, writing codes as it should, then when it came to the radio downgrade, it got to a part where it usually moves on to the next stage fairly quickly, but this time it just hung.. I left it a few mins to see if it would carry on, no such luck.. I had no choice but to remove the cable and try again.. Now i'm not a fan of removing cables midway through, but it would have just hung forever so i had no choice..
Anyway.. I can still access the CWM screen and have tried every option to get it to do something, but no matter what i do, i can't get past either the white HTC screen or the Black background with the red triangle.. The files are still there on my SD card obviously, i can access them via a card reader, it's just the phone won't move on as i'm guessing the downgrade being interrupted left it with corrupt data... I would have thought running the AAHK again would have started from scratch and just re-run, but this obviously isn't the case.. Any ideas what to do?
RyanH77 said:
Hi guys... First post here as i seem to be stuck.. My phone is a DHD.
I'm not new to rooting or custom ROM's as i often change the ROM on my phone easily without any problems.. Done it 40-50 times now. Never had a problem. I'm used to the AAHK and know what i'm doing.. However, last night i got fed up of the ROM i had, been having some teething troubles lately so figured i'd put it back to stock and then root again and flash a new ROM, this always solves my problems. Now i always have a few others stored on my SD card incase one won't work (i sometimes get the bad installation, aborted) message and i'm not left without a working ROM, but wanted to unroot and put back to stock so opened the AAHK and proceeded as normal to do so ..
Everything was running fine, writing codes as it should, then when it came to the radio downgrade, it got to a part where it usually moves on to the next stage fairly quickly, but this time it just hung.. I left it a few mins to see if it would carry on, no such luck.. I had no choice but to remove the cable and try again.. Now i'm not a fan of removing cables midway through, but it would have just hung forever so i had no choice..
Anyway.. I can still access the CWM screen and have tried every option to get it to do something, but no matter what i do, i can't get past either the white HTC screen or the Black background with the red triangle.. The files are still there on my SD card obviously, i can access them via a card reader, it's just the phone won't move on as i'm guessing the downgrade being interrupted left it with corrupt data... I would have thought running the AAHK again would have started from scratch and just re-run, but this obviously isn't the case.. Any ideas what to do?
Click to expand...
Click to collapse
Why are you running the Hack Kit being S-OFF? there is no use in doing that. You could have flashed a different rom from recovery after doing a full wipe and everything might have been solved, if it was a software issue.
glevitan said:
Why are you running the Hack Kit being S-OFF? there is no use in doing that. You could have flashed a different rom from recovery after doing a full wipe and everything might have been solved, if it was a software issue.
Click to expand...
Click to collapse
Yes i realise that.. That's how i always flashed new ROM's. i could have a new ROM installed in minutes that way, but the reason i was running the hack kit was to put it back to S-ON and stock RUU.. As far as i was aware you had to run the hack kit to put it back to stock, that's the only way of doing it is it not?..
But that's not the problem, my problem now is, getting the phone to show some signs of wanting to get past either screen.
RyanH77 said:
Yes i realise that.. That's how i always flashed new ROM's. i could have a new ROM installed in minutes that way, but the reason i was running the hack kit was to put it back to S-ON and stock RUU.. As far as i was aware you had to run the hack kit to put it back to stock, that's the only way of doing it is it not?..
But that's not the problem, my problem now is, getting the phone to show some signs of wanting to find get past either screen.
Click to expand...
Click to collapse
Are you still S-OFF? then flash recovery again and then a custom rom. Problem solve. If you want to revert to stock, then do that first and the set S-ON the second time...just in case.
glevitan said:
Are you still S-OFF? then flash recovery again and then a custom rom. Problem solve. If you want to revert to stock, then do that first and the set S-ON the second time...just in case.
Click to expand...
Click to collapse
Yes it is still S-OFF, but it won't let me flash anything, run bootloader, access the SD card or i wouldn't have the problem i have..
If i hold volume down and power, i get the usual screen with fastboot, recovery, factory reset, simlock and image crc.. I've tried every one of these apart from the simlock with the same results.. Nothing.. If i select recovery, it flashes the white HTC screen as if it's going to boot, then i get the black phone with the red triangle and it won't go any further.. If i hold volume up and power at that stage, it gives me the apply sdcard:update.zip (which i can't seem to access or just don't have, i'm not sure) and the wipe data/factory reset and cache options..
The only thing it tells me on the screen is E:Can't open /cache/recovery/command
I fear i can't do anything with this phone, even trying to get the hack kit to run is a pain and keeps giving me several errors including the ECHO OFF message. I presume this is because having done the wipe cache and data, i've removed the usb debugging priviliges..
RyanH77 said:
Yes it is still S-OFF, but it won't let me flash anything, run bootloader, access the SD card or i wouldn't have the problem i have..
If i hold volume down and power, i get the usual screen with fastboot, recovery, factory reset, simlock and image crc.. I've tried every one of these apart from the simlock with the same results.. Nothing.. If i select recovery, it flashes the white HTC screen as if it's going to boot, then i get the black phone with the red triangle and it won't go any further.. If i hold volume up and power at that stage, it gives me the apply sdcard:update.zip (which i can't seem to access or just don't have, i'm not sure) and the wipe data/factory reset and cache options..
The only thing it tells me on the screen is E:Can't open /cache/recovery/command
I fear i can't do anything with this phone, even trying to get the hack kit to run is a pain and keeps giving me several errors including the ECHO OFF message. I presume this is because having done the wipe cache and data, i've removed the usb debugging priviliges..
Click to expand...
Click to collapse
You have to flash a recovery in fastboot.....no other way will work.
glevitan said:
You have to flash a recovery in fastboot.....no other way will work.
Click to expand...
Click to collapse
How do i do that exactly?? If i select fastboot, it takes me to the next screen which has bootloader, reboot, reboot bootloader and power down, and again, no matter what i press it won't open any external folders or do anything..
RyanH77 said:
How do i do that exactly?? If i select fastboot, it takes me to the next screen which has bootloader, reboot, reboot bootloader and power down, and again, no matter what i press it won't open any external folders or do anything..
Click to expand...
Click to collapse
ok, if it is ok with you, I can connect over teamviewer and do it for you to show you how to do it....send the ID and PASS in a PM.
glevitan said:
ok, if it is ok with you, I can connect over teamviewer and do it for you to show you how to do it....send the ID and PASS in a PM.
Click to expand...
Click to collapse
What ID and PASS?? I don't understand? Where would i find them??
RyanH77 said:
What ID and PASS?? I don't understand? Where would i find them??
Click to expand...
Click to collapse
Are you reading what I wrote?? if you are interested, I can connect to your PC via teamviewer (http://www.teamviewer.com) but I need the ID and PASS to do it.
RyanH77 said:
What ID and PASS?? I don't understand? Where would i find them??
Click to expand...
Click to collapse
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
glevitan said:
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
Click to expand...
Click to collapse
You've misread the situation.. I didn't lie to you about anything, ok, i was unsure of what i'd done, but i certainly didn't ask for help to mislead you and help break my phone. Why would i do that??? I genuinely got stuck with a problem that i didn't know how to get out of.. To be honest i've never had a problem with it before and didn't realise you had to know every single piece of info about it, most of which you forget whilst trying to sort it anyway, and i can't remember if it was flashed previously with a stock ROM or not, but what you mentioned sounded familiar which is why i said i think it might have been, but i can't be 100% certain on that..
I feel bad that you saw it as misleading, as i didn't feel i had been, and that certainly wasn't my intention.. But even though you are unwilling to help me again, i thank you very much for the help you gave me, without you it would still be in a useless state. Thankfully, i have managed to get it working perfectly again and will be more careful in future..
glevitan said:
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
Click to expand...
Click to collapse
What's wrong with you dude?
If someone doesn't have a knowledge on something (misunderstoods, etc..) it doesn't mean hes lying, lol.
-SmOgER said:
What's wrong with you dude?
If someone doesn't have a knowledge on something (misunderstoods, etc..) it doesn't mean hes lying, lol.
Click to expand...
Click to collapse
Maybe you don´t have a clue on what happened. What's up with me? I will tell you what is going on...i spend many hours of my life helping people in here and in the Hack Kit IRC Support Channel for free, I do it because I enjoy it and don't expect anything in return.
But the worst thing ever is to come accross someone that lies about what he did to his phone. I have been around this site for about 2 years now and never made a brick, do you know why? because I always make sure to follow instructions and ask people what they did in order to provide the best fix, if possible.
When you spend and hour trying to figure out what is going on and trying to flash something and then find out that a froyo RUU might have been flashed (perhaps, I don´t know, not sure...WTF???) and what you did might have scr*wed his phone, it really makes me angry and feel cheated.
To sum up, my time...my decision...maybe you can help him yourself instead of questioning me.
glevitan said:
Maybe you don´t have a clue on what happened. What's up with me? I will tell you what is going on...i spend many hours of my life helping people in here and in the Hack Kit IRC Support Channel for free, I do it because I enjoy it and don't expect anything in return.
But the worst thing ever is to come accross someone that lies about what he did to his phone. I have been around this site for about 2 years now and never made a brick, do you know why? because I always make sure to follow instructions and ask people what they did in order to provide the best fix, if possible.
When you spend and hour trying to figure out what is going on and trying to flash something and then find out that a froyo RUU might have been flashed (perhaps, I don´t know, not sure...WTF???) and what you did might have scr*wed his phone, it really makes me angry and feel cheated.
To sum up, my time...my decision...maybe you can help him yourself instead of questioning me.
Click to expand...
Click to collapse
Like SmOgER said before you Glevitan, i wasn't lying, you just got annoyed with me because i didn't give you 100% of the info you needed, and the only reason for that was because i didn't know it!! When you think you're phone is playing up, you try various ways to get it right again, i'm sorry i don't keep track of every little step i did and i'm sorry this displeased you. But a liar i am not.. The term more appropriate would be clueless!!
You have to accept that us newbies just don't know anywhere near as much about these phones and how they work as you do.. It doesn't mean i lied.. What you see as a misrepresentation of facts doesn't mean i am a liar, it just means i didn't give you the info you wanted, simply because i didn't know it, not that i was withholding it on purpose, THAT would have been bad!!
I am no expert like you, i just root and ROM like most people and hope that it goes right...
Like i said before, i really appreciate the time you took to help me and didn't go unnoticed, and it's great that you help people like me for free, but maybe you should take it a bit easier on the newbies if they're not so expert.. My 1st post asking for help and i already feel like i'm not welcome anymore.. That's pretty bad for such a big community!!
SmOgER.. At least YOU understood where i was coming from..
1. Flashing a Froyo RUU is an important stop on the quick path to bricking your phone, and that warning is splashed all over AAHK and other documentation. That's why glevitan is so upset about not being told of the possibility that you might have done it: it's very bad, and users should know that it's very bad, and it wastes a lot of time.
2. Not knowing what you're doing and messing with your phone, and then not keeping track of what you're doing, is extremely unwise. When helping out on XDA, I personally don't expect everyone to know everything, but taking basic precautions really does seem like common sense.
3. Next time, read similar threads that came before you and ask the community. For example: I have X problem. I have researched and found Y and Z thread links with similar symptoms. I am considering trying what A suggested in Y. Is that the wisest course of action? Then you show that you have done your part in solving your own problem, and the community will respect that, even if you're way off base.
Obviously, I personally wasn't there on teamviewer, so I have no idea about the clueless v. lying thing.
bananagranola said:
1. Flashing a Froyo RUU is an important stop on the quick path to bricking your phone, and that warning is splashed all over AAHK and other documentation. That's why glevitan is so upset about not being told of the possibility that you might have done it: it's very bad, and users should know that it's very bad, and it wastes a lot of time.
2. Not knowing what you're doing and messing with your phone, and then not keeping track of what you're doing, is extremely unwise. When helping out on XDA, I personally don't expect everyone to know everything, but taking basic precautions really does seem like common sense.
3. Next time, read similar threads that came before you and ask the community. For example: I have X problem. I have researched and found Y and Z thread links with similar symptoms. I am considering trying what A suggested in Y. Is that the wisest course of action? Then you show that you have done your part in solving your own problem, and the community will respect that, even if you're way off base.
Obviously, I personally wasn't there on teamviewer, so I have no idea about the clueless v. lying thing.
Click to expand...
Click to collapse
Yes i understand what you're saying, and i appreciate most of it. However, it's not often practical or even possible in some cases to write down or note everything you do in a documented fashion.. And like you might have previously missed, i have flashed various ROM's 40-50 times, and the AAHK has worked perfectly for me everytime except the last where it took it upon itself to just freeze on me, it was a computer issue, not a human error.. Also, why would reflashing a Froyo RUU to a phone that was originally shipped as a Froyo unit cause any problems??
I don't understand that part..
One final note, i did have a look through similar threads, but there are so may threads with similar symptoms that it's hard to sift through them all for a definitive answer, and even when you do read them, only one or two parts might be relevant, if any.. So it's quicker to come straight out and ask rather than waste hours trawling through them all to no avail i think.
Whatever happened doesn't matter anymore. Lesson learned.
You seem like a nice guy. Let's back on topic.
Is the issue solved or not?
Try to state what is the current issue. What was the state of the phone when it was working. What happened or what were you trying to do when it got messed up. What have you tried so far. Etc, etc, etc. The more the info the better.
Edit: Nevermind. You *******, you flashed a froyo hboot on your HTC Inspire/DHD after we’ve warned NOT to for over a year. Here’s the fix:
Sent from a dream.
RyanH77 said:
Yes i understand what you're saying, and i appreciate most of it. However, it's not often practical or even possible in some cases to write down or note everything you do in a documented fashion.. And like you might have previously missed, i have flashed various ROM's 40-50 times, and the AAHK has worked perfectly for me everytime except the last where it took it upon itself to just freeze on me, it was a computer issue, not a human error.. Also, why would reflashing a Froyo RUU to a phone that was originally shipped as a Froyo unit cause any problems??
I don't understand that part..
One final note, i did have a look through similar threads, but there are so may threads with similar symptoms that it's hard to sift through them all for a definitive answer, and even when you do read them, only one or two parts might be relevant, if any.. So it's quicker to come straight out and ask rather than waste hours trawling through them all to no avail i think.
Click to expand...
Click to collapse
It is not about if you are an expert or not...I am not, belive me. But I am wise enough to read and try to learn. Doing things like a monkey will not excuse you.
If you don't understand, maybe it is time for you to buy an Iphone. Hacking is not for the lazy b*stards who don't even know what they do. And belive me, your story is hard to belive, running the Hack Kit with a custom rom is not possible...you should have got stuck, that is how it works.
YOUR PHONE....YOUR PROBLEM...I don't give a penny for it.
glevitan said:
It is not about if you are an expert or not...I am not, belive me. But I am wise enough to read and try to learn. Doing things like a monkey will not excuse you.
If you don't understand, maybe it is time for you to buy an Iphone. Hacking is not for the lazy b*stards who don't even know what they do. And belive me, your story is hard to belive, running the Hack Kit with a custom rom is not possible...you should have got stuck, that is how it works.
YOUR PHONE....YOUR PROBLEM...I don't give a penny for it.
Click to expand...
Click to collapse
I wouldn't be seen dead with an iPhone.. I hate Apple and Apple products for that specific reason. They don't give the freedom of open source and don't allow real control. But i will be more careful in future and learn from my mistakes.. However, i'm not a lazy bastard hacker as you so put it, and i don't care for the accusation of being one either, please be careful what you say in future as statements like that are completely uncalled for ..
I understand you are somewhat unhappy with me, but please don't resort to slating me. I wouldn't do the same to you if you were wrong.
And yes Teichopsia.. I am a nice guy, thank you for noticing.. I realise now i made a mistake and i just got stuck, but the phone is now running absolutely flawlessly thank you..
I have been having this issue for weeks now. Any time I try to turn on my bluetooth, it flashes on for just a split second, then turns right back off. I was able to pull some info from logcat, I don't know if it would be of any help but hopefully you all can help me figure this out. Thanks in advance!
Logcat seen here (quite long)
JustAk said:
I have been having this issue for weeks now. Any time I try to turn on my bluetooth, it flashes on for just a split second, then turns right back off. I was able to pull some info from logcat, I don't know if it would be of any help but hopefully you all can help me figure this out. Thanks in advance!
Logcat seen here (quite long)
Click to expand...
Click to collapse
What ROM and what kernel did you flashed?
FcoEnrique said:
What ROM and what kernel did you flashed?
Click to expand...
Click to collapse
That's the weird part, I'm only running stock right now. I was going to flash cyanogen later but this bluetooth thing started up and I'm not sire what caused it
JustAk said:
That's the weird part, I'm only running stock right now. I was going to flash cyanogen later but this bluetooth thing started up and I'm not sire what caused it
Click to expand...
Click to collapse
Rooted and unlocked bootloader? What method?
Freegee likes to mess with the bluetooth. There should be a bluetooth fix flashable zip in the freegee thread for the ls970. I don't know if you can flash it on stock so make sure you read thoroughly.
Rooted yes, unlocked bootloader no. I rooted with fiddy619's batch file.
I'll take a look at their fix. As far as bluetooth suddenly breaking, is there anything that typically causes this or that I can look into? I've checked over all my settings, and none of my apps seem to be interfering (as far as I can tell), and I can't make sense of the logcat, so Idk what else to look at.
JustAk said:
Rooted yes, unlocked bootloader no. I rooted with fiddy619's batch file.
I'll take a look at their fix. As far as bluetooth suddenly breaking, is there anything that typically causes this or that I can look into? I've checked over all my settings, and none of my apps seem to be interfering (as far as I can tell), and I can't make sense of the logcat, so Idk what else to look at.
Click to expand...
Click to collapse
Freegee is to unlock the bootloader, if you're not unlocked and did not use freegee then you have no need for the fix. Do you have a recovery installed? What one?
you should definitely read this thread and maybe complete the process. There are tons of roms out there an as long as you follow the steps in this thread, you shouldn't mess anything up.
http://forum.xda-developers.com/showthread.php?t=2050582
dopy25 said:
Freegee is to unlock the bootloader, if you're not unlocked and did not use freegee then you have no need for the fix. Do you have a recovery installed? What one?
you should definitely read this thread and maybe complete the process. There are tons of roms out there an as long as you follow the steps in this thread, you shouldn't mess anything up.
http://forum.xda-developers.com/showthread.php?t=2050582
Click to expand...
Click to collapse
Regarding Freegee, I saw that after responding and then felt quote stupid. But I'll probably be doing that soon now so I can get a properly working phone.
Thanks for the suggestion, I'll probably be doing this tomorrow and will update the thread when I do.
For those still subscribed to this, I solved the problem. I am using SmartApp Locker, and in the Settings menu under System Lock I had Bluetooth checked. This should only have been locked when the app locking service was turned on, but it was interfering with all usage of bluetooth with the app lock service on or off.