So I'm trying to use chad's AnthraX-CDMA-AOSP-TEST14 kernel with miui 2.2.17 and everything works perfect except wifi doesn't work. I'm on hboot 1.5. I've tried it flashing with flash image gui, booting recovery through command prompt and flashing it there, and several combinations of the two. I've also tried flashing it immediately after doing a super wipe and flashing the rom. Nothing seems to get it working. Any ideas of how I can fix this?
Thanks in advance.
TheLeapist said:
So I'm trying to use chad's AnthraX-CDMA-AOSP-TEST14 kernel with miui 2.2.17 and everything works perfect except wifi doesn't work. I'm on hboot 1.5. I've tried it flashing with flash image gui, booting recovery through command prompt and flashing it there, and several combinations of the two. I've also tried flashing it immediately after doing a super wipe and flashing the rom. Nothing seems to get it working. Any ideas of how I can fix this?
Thanks in advance.
Click to expand...
Click to collapse
if other users with the same kernel are experiencing the same issue, could be something the developer will have to resolve.
regardless, the basic troubleshooting steps you can take start with logcat. i posted some information previous about this here:
using adb logcat is going to be the best way to find out the exact error the Wifi module is giving. When the WiFi module shows "Error" on the android screen, in the background, it usually dumps troubleshooting information into logcat.
By pulling the logcat information, we're able to more specifically troubleshoot the issue.
Click to expand...
Click to collapse
after logcat, looking at kernel output in /proc/kmsg would be another place to check for information.
if you want, post back the information you gather and we can troubleshoot from there! hope that helps!
joeykrim said:
if other users with the same kernel are experiencing the same issue, could be something the developer will have to resolve.
regardless, the basic troubleshooting steps you can take start with logcat. i posted some information previous about this here:
after logcat, looking at kernel output in /proc/kmsg would be another place to check for information.
if you want, post back the information you gather and we can troubleshoot from there! hope that helps!
Click to expand...
Click to collapse
Thanks. I'm checking this out now. In the mean time I thought I'd mention the fact that the wifi doesn't say "error" like it usually does with a bad kernel. What happens is if I try and enable wifi it says turning on forever and my entire phone starts moving extremely slow, even after I disable the wifi, until I restart. From what I've seen no one else appears to be having this issue with this kernel.
Thanks again for the help.
Related
So I am rooted, stock rom, using imoseyon kernal and I noticed the WiFi and tether are not working.... When I go to toggle wifi on it just says Error in the settings and closes. Anyone got any idea what gives? I have searched the forms and have yet to see something relating to my issue... Granted I am at work so I have not searched past the first couple of filtered pages.
Did you download the kernel from Kernel Manager? I know some kernels were having wifi issues when downloaded through there.(I don't know if your specific one was or not) If so, I'd try downloading it from the thread here and re-flashing first.
K I will try that when I get home and post the results.
Sweet thanks man that fixed it!
my wifi worked for awhile then stopped connecting. tried wiping cache/davlik 3 times. tried re-installing the rom. i nandroided back to an older version which wifi worked before and now it doesn't. tried flashing a different rom no success. tried flashing a different kernal anthrax b-02 via recovery no success so i tried flash gui image app in the market. all with no luck. im on h-boot 1.40.
my 4g connects just not my wifi. if anybody can help it would greatly be appreciated.
ro2themax said:
my wifi worked for awhile then stopped connecting. tried wiping cache/davlik 3 times. tried re-installing the rom. i nandroided back to an older version which wifi worked before and now it doesn't. tried flashing a different rom no success. tried flashing a different kernal anthrax b-02 via recovery no success so i tried flash gui image app in the market. all with no luck. im on h-boot 1.40.
my 4g connects just not my wifi. if anybody can help it would greatly be appreciated.
Click to expand...
Click to collapse
The 4G and WiFi drivers are stored in the same directory. Generally, if one is not working due to a mismatch with the kernel, the other one will not work either.
Since you're taken some initial steps to gaurantee the WiFi module definitely matches the kernel version, I would move on two more detailed troubleshooting.
There are two approaches I would suggest to get at the root of the issue quickly without wasting more time/effort.
1) When you toggle WiFi on/off from the Settings screen, what message does it display there? It should also be displaying detailed error out put in at least the logcat if not also in dmesg/kmsg. If you are able to post up these logs, it should help narrow down the issue.
2) Nandroid your current setup, you can revert back later and then flash a completely 100% stock ROM and kernel. Use a modified version of the RUU if needed.
Personally, I would glance at the logs from Step 1, but to make sure the hardware on the device is in deed working 100% and there are no hardware issues, I would revert to 100% stock ROM and kernel. If the WiFi doesn't work with 100% ROM and kernel, this would appear to be a potential hardware issue and I would look into getting the device repaired/exchanged.
If the WiFi works on the 100% stock ROM and kernel, then the issue now lies with either the previous ROMs/Kernels or the methods used to load them.
Hope that helps and appreciate the support!
hey, thanks for the reply and help.
when i try ti connect in the settings, it attempts to connect and obtain the ip address but it doesnt connect and just times out. i dont know how to look at or even find the the logcat or dmesg/kmsg. if you could tell me how to find it, i would post it.
im going to try to flash a stock rom with stock kernal, hope fully its not a hardware issue. i will post my results on the stock rom flash.
i just flashed Shooter_S_Sprint_W...8.651.3_deodex.zip and still no wifi.
am i just screwed or is there another way to fix this problem?
joeykrim said:
The 4G and WiFi drivers are stored in the same directory. Generally, if one is not working due to a mismatch with the kernel, the other one will not work either.
Since you're taken some initial steps to gaurantee the WiFi module definitely matches the kernel version, I would move on two more detailed troubleshooting.
There are two approaches I would suggest to get at the root of the issue quickly without wasting more time/effort.
1) When you toggle WiFi on/off from the Settings screen, what message does it display there? It should also be displaying detailed error out put in at least the logcat if not also in dmesg/kmsg. If you are able to post up these logs, it should help narrow down the issue.
2) Nandroid your current setup, you can revert back later and then flash a completely 100% stock ROM and kernel. Use a modified version of the RUU if needed.
Personally, I would glance at the logs from Step 1, but to make sure the hardware on the device is in deed working 100% and there are no hardware issues, I would revert to 100% stock ROM and kernel. If the WiFi doesn't work with 100% ROM and kernel, this would appear to be a potential hardware issue and I would look into getting the device repaired/exchanged.
If the WiFi works on the 100% stock ROM and kernel, then the issue now lies with either the previous ROMs/Kernels or the methods used to load them.
Hope that helps and appreciate the support!
Click to expand...
Click to collapse
joeykrim, thanks bud for your help. I got it to work. i really do appreciate the quick reply and assistance.
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
yes its a kernel issue. what version of software are you running?
I had the wifi error issue, and i flashed the kernel on top of the rom and it works now
Depending on the ROM you flashed, it may or may not display "Flash Kernel after." In which then you flash it. This'll take care of all Bluetooth and Wi-Fi Issues!
If you're having issues let me know.
I had the same issue I was using stock kernel for tmobile version 1.36.531.6 on mine which I had over the air updated to 1.43.531.3. This created the wifi error and bluetooth issue, I had to try different kernels to try to figure this thing out...It will posted in my read me page when I get a chance
It's a kernel issue, there are actually three different kernels, not two, I posted this in xboarders thread, but He hasn't updated his page.
kernels
1: for tmobile software stock 1.43.531.3, this is not available anywhere on the amaze forums, i had to personally extract this from the rooted stock rom that xboarder provided
2: for tmobile software stock 1.36.531.6 and 1.36.531.5 and lower, this stock i believe is the one xboarder has up as the original boot.img
3: faux's custom kernel, this kernel will work with all versions i believe
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
andy55 said:
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
Click to expand...
Click to collapse
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
I told you rooting is not for you but you thought I was attacking you. But seriously if you do not know what you are doing you will mess up the phone. you still havent because there still is no s-off so pretty much your phone is kinda locked
seansk said:
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
Click to expand...
Click to collapse
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
seansk said:
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
Click to expand...
Click to collapse
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
yes lets wait, with people with lets experience, I tend to dumb things down when asking questions...I am not doing it to demean them, but It's the only way to get any real good answers and being able to help them. Then over time they'll learn
sean, I was running the android revolution 1.1, and tried a couple different kernels and nothing
But I ended up fixing the issue finally. The super wipe zip file I downloaded with AR 1.1 was corrupt, and wouldn't load properly, so I was installing a rom without doing a wipe every time. So, I put a working copy of the zip on the sd card, and did a manual wipe of the caches, re-installed AR 1.1 and all is well.
So, even though I was following all necessary steps, I failed to realize that the wipe zip was faulty, and really messed everything up, and when I changed the rom again to beastmod, I didn't install the correct kernel with it, so yet more issues.
Happy to say that it's all over, and I have a much faster phone with alot less bloat on it. Thanks to everyone!
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Flashed the kernel as xboarder showed in his thread and video.
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Drachen808 said:
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
Click to expand...
Click to collapse
Drachen808 said:
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Click to expand...
Click to collapse
A bad flash can occur but generally they aren't prevelant. The best place to look for feedback on ROMs is in that specific ROM thread. If that specific ROM isn't setup well, or has bugs, these will cause random reboots.
If you're really interested in helping out the devs, the best first step in technically troubleshooting a random reboot is to grab the /proc/last_kmsg file. This is a log of the kernel as of last boot and will indicate whether or not the kernel was involved in the random reboot. If the issue is in the kernel, will narrow down the focus. If the issue is not in the kernel, will eliminate that possibility.
Another common cause of random reboots can be poorly coded 3rd party apps. Unfortunately, depending on the number of 3rd apps installed, this process can take a while to troubleshoot as the best method is to remove all and start installing in batches waiting to see if any random reboots occur.
Hope these few suggestions and some technical information help!
Thank you Joeykrim. I will look into that, but I am fearing more and more that it may be my phone. I have tried probably every sense 3.0 rom (need wimax and camera so no 3.5) and several different kernels, and it keeps happening.
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.