Related
A test/stock anykernel for CM6 inc is up on rom manager under the Koush section. Please test it out and let me know how it compares. I am working on tracking down some instability issues.
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Used it for a day...
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
sucker4pa1n said:
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
Click to expand...
Click to collapse
2.15.00.09 radio literally KILLED my battery. I went back to 2.15.00.07 and battery life is great again. FYI.
Everything is good for me with this kernel. No issues. Flashed it last night.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
At the moment, I'm using Miui but wanted to note that this is the only kernel which allows Pre-9 Wifi tether to work on Miui (in my hands, King's #1 and #2 AOSP kernels gave me errors with Wifi Tether). Thanks for providing this kernel, Koush. Will give it a try with CM and see how that goes.
I had a soft reboot last night with this new kernel while I was on facebook. 0 wifi used.
Radio 2.15.00.07
Not sure if it's the kernel or just the latest nightly, but I'm loosing my data connection quite often. Otherwise, its running great.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
My built in wifi tethering isn't working either....sad day. I was loving how fast my phone charged
New version, number. 11 is online, testing now.
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
mikeacela said:
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
Click to expand...
Click to collapse
Funny, I'm running the test2 on Ruby as well. Been rock stable for 4hours. Practically a record for my phone on Ruby. Hope it makes it through the night.
Using the "test2" kernel.
Built in tethering works for me.
I'm running the 9/27 nightly.
No other issues so far.
P.S. I would love if internal memory was mounted properly in Windows.
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Another question would be, does anyone know if test kernel #1 or #2 is the test kernel in rom manager?
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
showing up as a 245-998mhz one with compcache optional... Not that I put much credence in quadrant scores, but I'm pulling over a 1300 on that. So plenty quick.
Also does anyone know if its undervolted?
Sent from my INCREDIBLE using Tapatalk
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
#2 is running at default clock.
So far looking good on test#2 for me (9.26 nightly). I just had a meeting in a location where the phone has frozen up nearly every time I was running CM 6.02 or any previous build and it worked fine. If I make it out to lunch, then back home later today without a freeze I think we may have a winner. Or at least I'll have a winner...
I grabbed the test kernel on friday night via the ROM manager, am I running the latest test, or is there a new one with the same name? In other words do I have to redo it to get the test #2 I am seeing comments about?
I am running test2 and my only issue is with wifi cutting out and erroring out when running things like streaming media in the background, but no reboots. Tt just cuts out the wifi, and resumes relatively well upon turning the screen back on. For some reason the screen being off sets off a timer that cuts out the wifi after a while. I've tested this with both Pandora and Slacker. No cut outs when running over 1x CDMA (3G doesn't work in my office) except when my signal becomes nonexistant.
I'm having issues with the wifi connection having to be reset every few minutes when used. It seems to outright lose signal and can't even scan for networks until a reset. I'm on CM7 stable, using the latest OC kernel by Dalingrin. Anyone experiencing similar?
I have a similar issue.
From time to time (something like every 5 min), the connection seems ok (in the wifi pannel, it is stated as connected), but I can't access anything anymore by wifi. I have to disconnect and reconnect to my wifi router in order to make it work.
(I also use the last stable CM7... And apart from that, it's gorgeous ! )
So I'm indeed not alone in seeing this... interesting. Thanks for letting me know. As well, I agree, everything aside from the wifi works great and the tablet tweaks incorporated are nothing short of brilliant.
Mine is table with CM7 final and with Philmod 6, both with the 03/31 and 04/04 kernels.
same here - cm7 stable + 4/4 OC
just loaded up nightly 39 + 4/14/11A OC to try that combo
politiclaw said:
I'm having issues with the wifi connection having to be reset every few minutes when used. It seems to outright lose signal and can't even scan for networks until a reset. I'm on CM7 stable, using the latest OC kernel by Dalingrin. Anyone experiencing similar?
Click to expand...
Click to collapse
Is this not the same issue all over about AES? Check your router, if it's WPA2 it's AES, if it's WPA it could be AES.
CM7 and some routers have issues when AES is used, try to disable it.
installed nightly 39 + oc 4/14a no wifi issues so far
khaytsus said:
Is this not the same issue all over about AES? Check your router, if it's WPA2 it's AES, if it's WPA it could be AES.
CM7 and some routers have issues when AES is used, try to disable it.
Click to expand...
Click to collapse
Tanks : that worked for me !
FixB said:
Tanks : that worked for me !
Click to expand...
Click to collapse
You mind Starring this issue on the Cyanogen tracker? Make sure you put all the relevant information as well as your Router HW and FW. Thanks!
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
I posted my remarks in a comment on the tracker.
But I'm afraid I don't know what you meant by "my Router HW and FW" ?
FixB said:
I posted my remarks in a comment on the tracker.
But I'm afraid I don't know what you meant by "my Router HW and FW" ?
Click to expand...
Click to collapse
hardware and firmware, ie brand name and model number and the version of software it's running.
animatechnica said:
installed nightly 39 + oc 4/14a no wifi issues so far
Click to expand...
Click to collapse
Can anyone else comment on this? I might just go down this route, but I'm wondering if there a few more who did similar and are seeing no wifi issue as a result.
Also, I'm surprised to see a CM7 final release with a wifi issue such as this. If it indeed is related to encryption (AES vs TKIP), that's further perplexing. While I could go about changing the settings for my router, I can't go about doing so for many others - particularly in public. As well, if I'm to tether from my N1, I'm going to do it with a password, meaning I'm to do it with AES as there isn't much choice built in.
I hate to say this as I'm impressed with the amount of work that went into (and normally always goes into) CM, but I figure it has to be said. To be fair, I'm not sure how widespread this issue may be (does it affect the version of CM7 on tablets, only?) but I'm surprised it can exist in a version of cm7 considered stable.
politiclaw said:
Can anyone else comment on this? I might just go down this route, but I'm wondering if there a few more who did similar and are seeing no wifi issue as a result.
Also, I'm surprised to see a CM7 final release with a wifi issue such as this. If it indeed is related to encryption (AES vs TKIP), that's further perplexing. While I could go about changing the settings for my router, I can't go about doing so for many others - particularly in public. As well, if I'm to tether from my N1, I'm going to do it with a password, meaning I'm to do it with AES as there isn't much choice built in.
Click to expand...
Click to collapse
I'll try 39 etc but I suspect if they made changes in that regard they would have said to retest in that logged bug.
As far as I know, I've heard reports this happens on some phones as well, not just tablets, not just the NC.
And it doesn't affect most people, in fact I'll bet it affects a minority of folks. If it affected everyone I'm sure CM7 wouldn't have released that way of course.
And yeah I'm with you, I _do not_ want to use my N1 tethered with Open encryption, but not much I can do until this is fixed.
khaytsus said:
I'll try 39 etc but I suspect if they made changes in that regard they would have said to retest in that logged bug.
As far as I know, I've heard reports this happens on some phones as well, not just tablets, not just the NC.
And it doesn't affect most people, in fact I'll bet it affects a minority of folks. If it affected everyone I'm sure CM7 wouldn't have released that way of course.
And yeah I'm with you, I _do not_ want to use my N1 tethered with Open encryption, but not much I can do until this is fixed.
Click to expand...
Click to collapse
Did you try 39 out? This issue is MIGHTY annoying for me as it is kind of hard getting a company with 39 000 employees to back away from AES on the WLAN..
Also going away from AES at home means that I cannot have my access point using 300 Mbit 802.11N which also is a real bummer.
I found this at the CM7 bugtracker, look at the final few posts there is a wifi-driver to try out.
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Also noticed there was a complete guide about pushing the file here: http://forum.xda-developers.com/showpost.php?p=11974146&postcount=22
So if CM7 on my phone works fine on wifi, that means a NC should work the same more or less, correct?
henel321 said:
Did you try 39 out? This issue is MIGHTY annoying for me as it is kind of hard getting a company with 39 000 employees to back away from AES on the WLAN..
Also going away from AES at home means that I cannot have my access point using 300 Mbit 802.11N which also is a real bummer.
I found this at the CM7 bugtracker, look at the final few posts there is a wifi-driver to try out.
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Also noticed there was a complete guide about pushing the file here: http://forum.xda-developers.com/showpost.php?p=11974146&postcount=22
Click to expand...
Click to collapse
I guess you didn't notice who posted in that bug, and posted tiwlan_drv.ko in the bug?
Anywho, for me it did help my own and work AP's, but it's still broken tethering to my phone. So it seems better but not perfect, give it a try. Just make a copy of the original tiwlan_drv.ko and push the single file from that zip up in its place and reboot.
Ok this is not your typical "my wifi wont connect issue"
i have tried a fios router, linksys cisco router w/ dd-wrt and linksys router stock. I first had cm7 on sd and assumed that was the issue so I flashed to emmc. It works great but the wifi stalls after about 3mb of transfer (or a couple of minutes of light usage) and i have to restart wifi with the power widget and it starts working again. EDIT: droid x and moto bravo work perfectly with these routers at the same time of the issue.
I already disabled wifi sleep policy.
I am using CM7 stable installed to emmc. its works fantastic otherwise but this is making it completely ususable for me. I dont think its a bad wifi chip since wifi was solid with HC on sd and seemed fine with stock nook 1.1.0
if i try to install an app it dies 75% through, if i try to play a youtube video it buffers 75% and then dies. it seems anything more than a simple web page lookup kills the wifi stack.
I havent had time yet to really dive in (been porting CWM to the motorola bravo in most my spare time) but hoping there is a simple fix out there, maybe i need to switch to dalgrin's kernel? but it also mentioned wifi issues and seems 2 weeks older than the kerenl supplied w/ cm7 but i am not sure.
This makes the nook completely unusable. Id rather not flash something else, it seems other people are having success w/ cm7 so I would like to work this out.
any ideeas? thanks
that sounds like possibly defective hardware honestly.... But you say it was fine on other ROMs so I dunno. I have had fewer problems on CM7 than Froyo myself. In fact CM7 has been solid with wifi. I wander around a lot with my NC and use many access points.
Do you have a logcat dump per chance?
If nothing is in the log, what is output of dmesg? Anything there that might suggest what's going on?
Also you might try checking out the command line program "wpa_cli". See if it helps you narrow down the issue. You can turn on additional debugging there.
Or, if you know how to rebuild your uRamdisk, appending "-DD" to the wpa_supplicant line in init.encore.rc would also give you more info in logcat...
One last thought-- if you are using dalingrins oc kernel, he took out a lot of debugging stuff (for speed), so if you want more info, revert to cm's stock...
swaaye said:
that sounds like possibly defective hardware honestly.... But you say it was fine on other ROMs so I dunno. I have had fewer problems on CM7 than Froyo myself. In fact CM7 has been solid with wifi. I wander around a lot with my NC and use many access points.
Click to expand...
Click to collapse
I hope its no hardware, its over 30 days old, i didnt get the extended warranty and I have a ghost armor on the screen
good to know your wifi is solid w/ cm7 and its not a general cm7 wifi issue. what encryption are you using?
bandroidx said:
I hope its no hardware, its over 30 days old, i didnt get the extended warranty and I have a ghost armor on the screen
good to know your wifi is solid w/ cm7 and its not a general cm7 wifi issue. what encryption are you using?
Click to expand...
Click to collapse
You have 1 year manufacture warranty.
Hello-
Its very unlikely to be Nook issue. I have had this issue with laptops and its always the ISP or the router.
Hope this helps.
Cheers,
mg
I had almost identical symptoms. I disabled encryption on my router and have had zero issues since.
Sent from my NookColor using Tapatalk
the same thing was happening to me and it just seemed to stop one day.. i think it was after nightly 35 or 36
Sent from my NookColor using Tapatalk
Calla969 said:
I had almost identical symptoms. I disabled encryption on my router and have had zero issues since.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out my thread on wifi http://forum.xda-developers.com/showthread.php?t=959823&highlight=dummies
My guess is that it's something in the wifi chip driver ir the wifi software stack. I have the identical symptom where on youtube, it stops after a few mb of download. (Note for mine it was stock NC with auto-nooter 3.0.0) The fix for mine was to set the router to 802.11 g only. So try this test:
1. set the router to 802.11 g only
2. turn off encryption
Let us know what happens.
I'm thinking that these devices have varying wifi quality.
My Nook Color is rock solid with wireless, regardless of encryption. WPA2 AES works as well as no encryption. I use my NC regularly with about 5 different access points around town. I'm using Dalingrin's 1100 MHz kernel with CM7 stable.
On the other hand I have a Motorola Droid that barely works unless I either turn off encryption or go to 802.11b! Those Droids were rather notorious for poor wifi. It does the same thing the OP mentioned - it stops transferring after a few megabytes although it says it's still connected. The wireless must be disabled and re-enabled.
It's AES, plain and simple. Turn it off on your router. if you're using WPA2, set it to WPA.
Your problems will go away. Now go to this thread, star it, and add your info please: http://code.google.com/p/cyanogenmod/issues/detail?id=3314
khaytsus said:
It's AES, plain and simple. Turn it off on your router. if you're using WPA2, set it to WPA.
Your problems will go away. Now go to this thread, star it, and add your info please: http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Click to expand...
Click to collapse
Lol I was 99% sure of this. I had the same problem on 2.6.29 kernels on my dx. it magically went away on 2.6.32.
I am using AES, I was going to try to turn it off next, now I know
thanks.
Fattire, thanks, I checked wpa_cli and it just fails to find anything and the scans fail once the issue happens.
The one thing all those routers I tried had in common was AES, its the only thing I really trust. I guess i will have to setup a stub network and seperate AP for the nook color
thanks!
After setting the AP to WPA2/WPA Mode the Nook's wifi is working perfectly under CM7 (except for needing to be restarted after the screen is off when sleep policy is on but i beleive this is a common documented issue)
thanks!
I posted on the cm7 thread and hopefully they will get this fixed asap.
My Droid 4 seems to have issues maintaining a wi-fi connection to some networks.
At home, it will connect and work for a while, but eventually stop passing data. It will still show connected, though. It will stay in this state until I turn wi-fi off and back on again.
At work, it often has issues connecting and will show "authentication problem" even though the credentials are correct. With enough trying, it will eventually connect, but won't stay connected.
iPhone, iPads, PCs, Macs and other types of Android phones work OK on these networks.
My old Droid 3 had the same issue.
On some other wi-fi networks, it seems OK.
What gives?
I'm currently a recent build of CM9, but it did the same when it was stock 2.3.6.
kmx2012 said:
My Droid 4 seems to have issues maintaining a wi-fi connection to some networks.
At home, it will connect and work for a while, but eventually stop passing data. It will still show connected, though. It will stay in this state until I turn wi-fi off and back on again.
At work, it often has issues connecting and will show "authentication problem" even though the credentials are correct. With enough trying, it will eventually connect, but won't stay connected.
iPhone, iPads, PCs, Macs and other types of Android phones work OK on these networks.
My old Droid 3 had the same issue.
On some other wi-fi networks, it seems OK.
What gives?
I'm currently a recent build of CM9, but it did the same when it was stock 2.3.6.
Click to expand...
Click to collapse
Ugh, me too and it was driving me absolutely crazy. I'm on AOKP now (think the build from a few days ago) and it (WiFi) works perfectly now. I know this, because mobile data keeps dropping (argh) but I'm still getting e-mail, etc (but I can't send MMS at least).
Most days I am in solid WiFi coverage, so I am dealing with dodgy mobile data in exchange for stable WiFi. Anybody know if eclipse fixes this issue?
Edit: I'm glad you made this post so I know I am not crazy. Part of the changelog for the 219 update was a WiFi fix, and I was very disappointed when it didn't seem to help...
podspi said:
Ugh, me too and it was driving me absolutely crazy. I'm on AOKP now (think the build from a few days ago) and it (WiFi) works perfectly now. I know this, because mobile data keeps dropping (argh) but I'm still getting e-mail, etc (but I can't send MMS at least).
Most days I am in solid WiFi coverage, so I am dealing with dodgy mobile data in exchange for stable WiFi. Anybody know if eclipse fixes this issue?
Edit: I'm glad you made this post so I know I am not crazy. Part of the changelog for the 219 update was a WiFi fix, and I was very disappointed when it didn't seem to help...
Click to expand...
Click to collapse
I've been on Eclipse since it was first ported and I have never had any data issues on 4G/3G or wifi. But I've only connected to 2 or 3 wifi networks so I could just be lucky there. 4G/3G connectivity is perfect.
Sent from my DROID4 using XDA
Yea, I really do have to check Eclipse out. The only thing holding me back is that I'm getting (what I consider) stupid-good battery life with AOKP. Plus, I just did a factory reset on ICS to fix notifications, which means I just set everything back up
Have you spent any time on Wifi using the stock ROM? I'm lucky to get half an hour of Wifi connectivity before it just dies (but still pretends to be connected). No problem with wireless tethering (AOKP or stock). Sometimes I am convinced they don't actually test these things before pushing them out...
podspi said:
Yea, I really do have to check Eclipse out. The only thing holding me back is that I'm getting (what I consider) stupid-good battery life with AOKP. Plus, I just did a factory reset on ICS to fix notifications, which means I just set everything back up
Have you spent any time on Wifi using the stock ROM? I'm lucky to get half an hour of Wifi connectivity before it just dies (but still pretends to be connected). No problem with wireless tethering (AOKP or stock). Sometimes I am convinced they don't actually test these things before pushing them out...
Click to expand...
Click to collapse
I never had any problem with stock either. I would run it on wifi all day at home on a Saturday and never had any drops. I just set up a new router last running dd-wrt so we will see how that goes.
You should definitely check out Eclipse. You lose a few of the ICS goodies but it's totally worth it in my opinion not to have to worry about data dropping out. Battery life has been phenomenal for me on Eclipse. I've been getting through a whole day with 40% - 50% battery left when I finally plug it in a night.
Just backup up your current ROM in safestrap that way, if you don't like Eclipse, you can just restore your backup and your back on AOKP with everything just as you left it!
I've used AOKP for over a week and I don't recall having wifi issues. Which build were you on? I used nightly 29/4. Now I'm back to stock because of BT and Camera. Other than that I had no issues.
Die Bruine said:
I've used AOKP for over a week and I don't recall having wifi issues. Which build were you on? I used nightly 29/4. Now I'm back to stock because of BT and Camera. Other than that I had no issues.
Click to expand...
Click to collapse
Me neither It's stock the OP and I are having issues with
kwyrt said:
You should definitely check out Eclipse. You lose a few of the ICS goodies but it's totally worth it in my opinion not to have to worry about data dropping out. Battery life has been phenomenal for me on Eclipse. I've been getting through a whole day with 40% - 50% battery left when I finally plug it in a night.
Click to expand...
Click to collapse
Wow, that sounds even better than what I'm getting with AOKP! Is that with any special tweaks or...?
podspi said:
Wow, that sounds even better than what I'm getting with AOKP! Is that with any special tweaks or...?
Click to expand...
Click to collapse
I haven't really tweaked it or anything. No undervolting/underclocking or anything like that. I have the 4G toggle installed and switch 4G off when I'm sitting at my desk at work and I'm connected to wifi when I get home in the evening. I don't do anything special other than that. I am still running version 1.3.7 as a couple of people have reported that 1.3.8 broke auto capitalization and not having that would drive me nuts.
Guess I wasn't clear enough. Both on AOKP 29/4 and stock 219 I encountered no WiFi issues. And I use it a lot. I have to because when I switch to 3G for faster internet I loose audio (GSM 3G not working yet). So what I mean to say is, not sure what your problem with WiFi is or where it's coming from. I ran AOKP for at least a week. And I've been running 219 since I got my phone (except for that specific week that is). Not once has WiFi stopped working or glitched for that matter.
Dear XDA HTC Desire C Users,
Let me start off by saying I know that this question has been asked before. I've lurked these forums since 2010, I've flashed many devices with many custom roms and kernels. I just want to know what the deal with CyanogenMod is.
I've recently come into possession of a HTC Desire C. It's a great little phone, not what I was expecting at all when I bought it off a bloke at work for £30. Started it up and it was bogged down with all the normal crap you get when someone has a lock stocked phone. Decided to check out XDA once again, and found that there was a port of my favourite rom; CyanogenMod.
I've previously used CM on my Galaxy Europa, Galaxy S 3, Galaxy S4, Nexus 7 and Xperia Play. Using my phone as a WiFi Hotspot/for Wifi Tethering (however you want to say it) was only ever a problem on the Xperia Play (and possibly the Nexus 7, I haven't actually tried). The checkbox would tick, the writing would say "Turning on wireless..." and then that would be it. It would never complete the action. USB tethering has never been an issue, and I never really needed wireless tethering until I got a Nexus 7 around Xmas. Funnily enough, my Xperia Play broke at the same time, and I went back to using the old Europa (CM7, working wifi tether).
Now I've loaded this Desire C up with CM10 with NOPE Kernel v2.6, tried this wifi fix that a lot of people seem to enjoy linking to (granted, it does make WiFi work, but not tethering). Some other suggestions were to use Barnacle WiFi Tethering app, but it creates an ad-hoc connection which a Nexus 7 can't connect to.
I guess it's really a few questions, which I can summarise here for those of you unwilling to read the above text :
- Why does CM have working WiFi hotspot/tether settings on most of my previous devices and not the HTC Desire C?
- Has anyone actually ever got their Desire C to tether with CM10 (any version for the HTC Desire C)? If so, how?
- Are all JellyBean roms having this issue?
- I've read that Sense based ROMs are the only ones that have functional wifi tethering settings. If so, that means I'd have to use an ICS ROM to be able to use wifi tethering?
- Am I doing something wrong? The past few years I've had to relearn how to do all this stuff to a different device each time, I may have missed something that's more prevalent to someone who is immersed in this regularly. My process was as follows -
1) Downloaded CM10 Build 3, TWRP 2.4.2.0, GApps & Nope Kernel v 2.6 (700mhz)
2) Flashed TWRP 2.4.2.0 as recovery (fastboot flash boot recovery.img)
3) Rebooted into Recovery
4) Backed up, wiped & flashed (Factory Reset, Cache, Dalvik, System)
5) Installed CM10 and Gapps (install .zip from sd)
6) Rebooted to Bootloader, flashed NOPE Kernel (fastboot flash boot boot.img)
7) Rebooted to Recovery, wiped Cache/Dalvik Cache
8) Started phone, set up, tried WiFi Tethering.....nothing happened.
As far as I can see, I've probably missed one detail that is affecting the entire process. I assumed that since this was cute_princes v3 marked as "wifi fix", that I wouldn't have to put the folder I linked to earlier onto my phone (the file contatining p2p_supplicant_overlay, wpa_supplicant and wpa_supplicant_overlay).
To confirm, I tried the boot.img that came with CM10, it was some form of Prometheus and that didn't work either. I have tried MiniCM10 as well, same results there. I have flashed NOPE Kernel v2.6 on both CM10 and MiniCM10, to no avail. I also tried the boot.img that was packed with MiniCM10, same result.
Sorry for the long post, but I feel that it's better to over-explain yourself, rather than leaving people guessing. If anyone could shed some light onto this, I'd be very grateful. It's something that made me curious enough to post after 4 years of silence and lurking in the background. The fact that I've managed to root and flash all the previous devices I've owned without ever having to make a post shows that all the information is available to me on this site, and that XDA is such a great place that this information is readily available for me. But in this case, I can't find what I need, so I call to you for help.
Thanks in advance,
Gordon Freeman
It's a cm10 bug.... I don't know if too many people have looked into this....
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
It's a cm10 bug.... I don't know if too many people have looked into this....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the answer that I hear the most, and I never hear anything more than that. What kind of bug prevents it on certain phones? Why do Sense roms (apparently) have working wifi hotspot?
All my other questions are still open, plus a lot more for discussion. I am only a couple of months away from buying a Nexus 5 anyway, but I need this phone to wifi hotspot in the meanwhile.
Sense ROMs have working Wi-Fi hotspot as they are sort of a modified stock ROM....
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
Sense ROMs have working Wi-Fi hotspot as they are sort of a modified stock ROM....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So you're saying that I have to use an Ice Cream Sandwich ROM if I want to be able to use wireless hotspot/tethering? I'm assuming that if there are no JellyBean ROMs that have working wifi tethering/hotspot, then it has something to do with the phones hardware being unable to work with a newer Android OS. But I'm pretty sure I've read people having success with tethering on JB ROMs.
Maybe someone could point me in the direction of having CM10/any JB ROM with working wifi hotspot/tethering, I'd be grateful.
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
beanaroo said:
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
Click to expand...
Click to collapse
Are you sure that wireless tether is working in Mini CM10? I've flashed this ROM with the provided boot .img and Nope 2.6, and tether did not work. I'm pretty sure I applied that Wifi Fix as well, and nothing seemed to work for me.
Is anyone using a Jellybean ROM with tethering working? I just need to replicate as many possible working combinations of ROM and kernels,so any suggestions of combos would be awesome.
I'm posting this message via WiFi Hotspot. MiniCM10 V3, N.O.P.E. v2.6 850Mhz. No wifi fix applied apart from the WiFi keepalive app (Enabled workaround 2, reselect Always On). USB tether works too, as I use it to install Arch Linux before setting up laptop wireless drivers.
I haven't tried V4 yet. I have a Desire C non-NFC.
beanaroo said:
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
Click to expand...
Click to collapse
First of all, I am a boy! xD...
And yes USB tether works for me...but I didn't try wifi hotspot...
If you can post a screenshot on MINICM 10 forum, then it would be great, so that all people having problems with other also roms come to know...
Thanks!
beanaroo said:
I'm posting this message via WiFi Hotspot. MiniCM10 V3, N.O.P.E. v2.6 850Mhz. No wifi fix applied apart from the WiFi keepalive app (Enabled workaround 2, reselect Always On). USB tether works too, as I use it to install Arch Linux before setting up laptop wireless drivers.
I haven't tried V4 yet. I have a Desire C non-NFC.
Click to expand...
Click to collapse
Thank you for your contribution to the thread. I only have the latest MiniCM10 (V4), but I am also using Nope 2.6, just a lower frequency (700mhz, i have no need for a large OC). I've just clean flashed it back onto my Desire C, and the same results as before. Here are a few screenshots, sometimes screenshots help :
Kernel Version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROM Version
WiFi Working (Worked after turning it on then rebooted phone. WiFi was on once rebooted)
Wireless Tether NOT Working
On the last picture, if I back out into the previous menu then re-select to go back into the tethering sub-menu, the "Turning on WiFi..." message disappears and the checkbox is ticked, yet there is still no hotspot being produced.
So I must be doing something wrong still?
EDIT : So I've just flashed on the same kernel and CMMini version as you've said has worked for you. I've installed the "WiFi KeepAlive" app, but I am yet to launch it, as the description of the app (which is very vague) does not seem to mend the ailment that I am having.
I'm providing screenshots of the latest and current installation on my phone. I am not sure if anything in these is out of the ordinary, but maybe someone can tell me if I've done something wrong by looking at my "About Phone" section. Once again, I've provided screenshots of the wifi tether not turning on correctly :
About Phone 1 (Kernel and Baseband Version)
About Phone 2 (CM Version, Build Date and Build Number)
WiFi Tether (Unresponsive, stuck on screen until pressing Back)
WiFi Tether (Shows after exiting and entering again, produces no hotspot visible to other devices)
Working WiFi (After switching on then rebooting, wifi becomes available, but no hotspot)
So if anyone has anything to add, I'd be grateful once more.
Thanks
So after messing around for a while, I've managed to make a slight amount of progress. I feel like I'm almost there now.
I renamed my hotspot "testet" (meant to type "tested", never changed it) and set up WiFi KeepAlive. Using Workaround 2 and Always Keep Wifi On, I managed to get my Nexus 7 to see the hotspot. That's as far as I got, as trying to connect breeds a varying set of results. Whilst it can see the hotspot, it can never fully authenticate. It will hover on "Obtaining IP Address..." and "Authenticating..." before giving me "Saved, secured with WPA2" but not actually connecting to the Internet, or it will say "Avoided poor Internet connection" (or something to that effect). It's frustrating being so close, yet so far. Here are some more screenshots to demonstrate my finds :
Nexus 7 Wifi Screenshots (Various)
The "Turning on Wifi" thing disappeared on my phone and gave me a solid checkbox ticked for once, without having to back out then back in to the menu
See the edit to my previous post to get up to speed on where I am with kernels/ROMs installed.
Thanks again.
So I guess that no one really has any clue about this? Out of the +1,000 views of this thread, only a couple of people could actually contribute?
@warrior1208 , you ported this version of CyanogenMod, and you seemed to think that wifi tether works. Maybe you could shed some light on what I might be doing wrong? I won't have answers such as "It's a known bug", you've pulled the ROM apart and put it back together again, surely you must have some idea about what's going on? I will try to help as much as I can.
@beanaroo have you seen my responses? I have replicated the same setup as you, and had no success at getting this to work. Since you have confirmed that it works, maybe you could give me some advice on what I may be doing wrong?
Failing that, recommend me a JellyBean ROM for this troublesome little phone that has wireless tethering working. I know the common response would be "look through them yourself", but obviously some ROMs claim to have working wifi tether and they do not seem to work when I try them, so if I could get a recommendation then I wouldn't have to trawl through all the "broken" ones and find one that actually works.
No offence to anyones ROMs, it's just that wifi tether is paramount in my use of a phone, and I really wouldn't like to go back to the childish looking ICS ROMs. I don't want to discard this phone either, it's a nifty little thing and I'm quite fond of it.
Thanks again,
Gordon Freeman
Gordon Freeman said:
So I guess that no one really has any clue about this? Out of the +1,000 views of this thread, only a couple of people could actually contribute?
@warrior1208 , you ported this version of CyanogenMod, and you seemed to think that wifi tether works. Maybe you could shed some light on what I might be doing wrong? I won't have answers such as "It's a known bug", you've pulled the ROM apart and put it back together again, surely you must have some idea about what's going on? I will try to help as much as I can.
@beanaroo have you seen my responses? I have replicated the same setup as you, and had no success at getting this to work. Since you have confirmed that it works, maybe you could give me some advice on what I may be doing wrong?
Failing that, recommend me a JellyBean ROM for this troublesome little phone that has wireless tethering working. I know the common response would be "look through them yourself", but obviously some ROMs claim to have working wifi tether and they do not seem to work when I try them, so if I could get a recommendation then I wouldn't have to trawl through all the "broken" ones and find one that actually works.
No offence to anyones ROMs, it's just that wifi tether is paramount in my use of a phone, and I really wouldn't like to go back to the childish looking ICS ROMs. I don't want to discard this phone either, it's a nifty little thing and I'm quite fond of it.
Thanks again,
Gordon Freeman
Click to expand...
Click to collapse
USB Tethering works flawlessly on MINICM10, whereas, for a working wifi hotspot(which is a CYANOGENMOD BUG), we would have to correct the wifi hotspot modules in the github source, and then produce a new build...
So, since we are not working for achieving that, we would never get wifi hotspot on aosp cm based roms...
I hope this information may clear up your doubts...
Here is a screenshot to prove that usb tether works in my ROM...
Unless someone makes a new build WiFi hotspot won't work and since most of the developers are now focusing on building cm11, it is highly unlikely that someone will create a cm10 build 4. You could try using Bluetooth hotspot as an alternative maybe?
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
Unless someone makes a new build WiFi hotspot won't work and since most of the developers are now focusing on building cm11, it is highly unlikely that someone will create a cm10 build 4. You could try using Bluetooth hotspot as an alternative maybe?
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have been using Bluetooth tethering, but it's far from what I require. It's quite slow, and Bluetooth drains battery pretty quick. The range is also very limited. Fair enough, I keep hearing the same "it's a known bug in CM10", so what about JB ROMs that aren't made from CM10?
warrior1208 said:
USB Tethering works flawlessly on MINICM10, whereas, for a working wifi hotspot(which is a CYANOGENMOD BUG), we would have to correct the wifi hotspot modules in the github source, and then produce a new build...
So, since we are not working for achieving that, we would never get wifi hotspot on aosp cm based roms...
I hope this information may clear up your doubts...
Here is a screenshot to prove that usb tether works in my ROM...
Click to expand...
Click to collapse
I'm fully aware that USB Tethering works on your build, if you had read any of my posts you'd realise that I already knew that. There was never a dispute as to whether USB Tethering was working. My problem is that @beanaroo claims that he has WiFi Tethering working with your ROM, and you seemed to acknowledge the fact that he had it working. So how can one user make something work that you (the builder of this ROM) claim doesn't work? Unless he is lying, then it must work?
So, other JB ROM alternatives to CM10 then?
EDIT : @warrior1208 I just noticed that your screenshot of your phone shows that Portable WiFi Hotspot is ticked. I know you can select it, go back in the menu and then go forwards again and it remains a solid tick, but why would you include that if you just admitted that it doesn't work? Strange.
Since the only source built jb ROM is cm10, all other ROMs are ported using cm10. That's why the bugs of cm10 are there in every ROM. If someone fixes the tethering and makes a patch or something then it would work. But so far no one has really taken it onto themselves to fix the bug..... So maybe if you could do something......
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
Since the only source built jb ROM is cm10, all other ROMs are ported using cm10. That's why the bugs of cm10 are there in every ROM. If someone fixes the tethering and makes a patch or something then it would work. But so far no one has really taken it onto themselves to fix the bug..... So maybe if you could do something......
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Point me in the direction of a ROM building tutorial and I'll happily try my hardest to get it working. I'm not a pro in this kind of thing, but I've been using computers for a couple of decades now so I'm sure I could give it a try. Plus it gives me a reason to get into Android development, as I love Android. I'm totally willing to put some effort into fixing this issue, even if it's just for me. If you could give me pointers on where to look, then I'll give it a shot, although if the CM guys can't do it then I really doubt I'll have a chance.
After all of this, I'm guessing that @beanaroo was lying about his ability to wifi tether on this ROM then?
Gordon Freeman said:
I have been using Bluetooth tethering, but it's far from what I require. It's quite slow, and Bluetooth drains battery pretty quick. The range is also very limited. Fair enough, I keep hearing the same "it's a known bug in CM10", so what about JB ROMs that aren't made from CM10?
I'm fully aware that USB Tethering works on your build, if you had read any of my posts you'd realise that I already knew that. There was never a dispute as to whether USB Tethering was working. My problem is that @beanaroo claims that he has WiFi Tethering working with your ROM, and you seemed to acknowledge the fact that he had it working. So how can one user make something work that you (the builder of this ROM) claim doesn't work? Unless he is lying, then it must work?
So, other JB ROM alternatives to CM10 then?
EDIT : @warrior1208 I just noticed that your screenshot of your phone shows that Portable WiFi Hotspot is ticked. I know you can select it, go back in the menu and then go forwards again and it remains a solid tick, but why would you include that if you just admitted that it doesn't work? Strange.
Click to expand...
Click to collapse
I never mentioned that wifi hotspot works in my ROM...You may ask @beanaroo how he got that working...and yes I was trying in my screenshot to make hotspot stable...But it won't work in any of the Jelly Bean ROMs...So if you want it, you may revert back to a sense ROM as, the sense roms are based on stock rom and hence have everything working...Whereas, all the JB roms for our device have been ported taking cm 10 build 3 as base...I hope this clears up your doubt that YOU CANNOT USE WIFI HOTSPOT ON ANY JELLY BEAN ROM, REVERT BACK TO STOCK OR SENSE BASED ROMS FOR ACHIEVING THAT
You can Google up a 'how to build a ROM from source guide' there are plenty of good ones.
Sent from my HTC Desire C using XDA Premium 4 mobile app
Well I've started looking into some guides now, and once I've installed Ubuntu I'll see what I can do. I think I made some progress, I managed to get the phone to broadcast a signal, there was just a problem with authenticating when connecting. I think once I manage to work out what that problem was, I could make a bit of progress.
In the mean time, I've downloaded a few Sense ROMs which I'll be flashing on to the Desire C until I buy my Nexus 5 next week, which means I'll have the Desire C available for multiple flashes and messing around without having to put my phone out of action for a long time.
Anyway, thanks for the (limited) help. I realised about halfway through that no one really cares enough to try and make it work, I thought people would be up for a crack at this. The lack of enthusiasm was probably down to people not fully reading my posts and checking out all the info I provided, but that's fine. If I get anywhere, I'll let you know.