Related
Great news everyone! </farnsworth>
ADHOC Wifi Support for Nook Color (stock)!
[EDIT] There appears to be an issue reconnecting when wifi sleeps and comes back on. Researching a permanent fix, in the meantime go to settings -> Wireless and toggle wifi off/on to correct it
This fix will allow you to connect to ADHOC wireless networks ( such as to a laptop or with wifi-tether on an android phone )
Like most other fixes, this requires your nook to be rooted and usb adb working, please follow the guides here and/or at the nook dev wiki first!:
Rooting: http://nookdevs.com/NookColor_Rooting
USB-ADB: http://nookdevs.com/NookColor_USB_ADB
HOWTO enable ADHOC tethering:
1. Download and unzip the attached zip file below, this should give you a wpa_supplicant-adhocfix file
2. *DISABLE WIFI ON YOUR NC*
3. Make a backup of your current wpa_supplicant:
Code:
adb pull /system/bin/wpa_supplicant wpa_supplicant.backup
4. Remount the /system partition RW:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
5. Push the new wpa_supplicant:
Code:
adb push wpa_supplicant.adhocfix /system/bin/wpa_supplicant
6. Fix permissions:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
7. Remount the /system partition RO:
Code:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
8. Enable WIFI on your NC, you should now be able to see ADHOC networks in the list! ( they'll be displayed with a (*) prefix )
[edit] Credit where credit's due, this was taken from a wpa_supplicant IBSS patch I found via a Google search, if anyone knows the party responsible, let me know so I can credit them properly!
http://szym.net/android/
This is compiled against TI's Omapedia Eclair sources ( http://omappedia.org ) - since this is a different framework than the B&N stock build, I can't guarantee this will work, won't brick your device, etc. Use at your own risk!
If you encounter any problems, please use this thread to let us all know.
That's all there is to it, enjoy!
I can confirm that this will allow you to connect you Nook Color to an adhoc network created by a Jailbroken iPhone 4 and MyWi.
Works great! Thanks!
WHOEVER made this fix....THANK YOU! This was the biggest thing I was missing on my NC! Works great!
Cool you figured this out! For some reason, I've been able to use the adhoc network on my Androidized HTC Leo (HD2) since the first time I tried, even before rooting.
Sent from my Rooted Nook Color using XDA App and iPhone MyWi adhoc connection.
You guys ROCK!!!!!!!!!!
Works great with my Droid now. Thanks!
Confirmed working with Mobile Wi-Fi Router on my VZW Touch Pro2.
Many thanks! Another big step!
Work perfectly on my motorola droid 1 using Wireless tether or Barnacle. Thanks for sharing this with us
Works great with AT&T Samsung Captivate and android-wifi-tether ver. 2.0.5-pre15.
Thank you very much!
My NC is stuck at trying to obtain an IP address from my Droid 1. I'm using Barnacle.
Any ideas?
*edit*
It took several attempts but it finally connected. Being able to get connected anywhere is awesome. Thanks for posting this!
Working great from my epic 4g.
Pro Tip: If you want a quick way to toggle wifi (and a few other settings) tap the clock in the nook's notification bar for a quick settings dialog.
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Philosophy757 said:
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Click to expand...
Click to collapse
Thanks for noticing, corrected the extra 'o'
As noted in the OP, this is based on TI's omap eclair reference sources, and there *is* a pretty glaring bug.
Basically, if your screen goes to sleep, waking it back up triggers a wifi-reconnect which fails to reinitialize the network properly. Your wifi settings will show 'Connected, no internet' when this happens.
Toggle Wifi off/on to fix this, I'm working on a permanent fix right now and will update when it's working.
Thanks everyone for testing and boosting the ol' ego a little
Some random tips so folks don't repeat the same mistakes I made while doing installing the ad hoc feature.
Don't choose to "forget" a wireless access point because then it doesn't appear again even if the device sees it. You'll have to manually enter the SSID, encryption type, and password to get it to work properly.
While mounting and remounting using adb, if you get a device busy error, disconnect the nook from the computer and come back to it later. Then reconnect and try again. For good measure I also powered down the nook. Not sure what happens if you leave the system folder mounted as RW, but I suspect bad things could happen.
Oh and the fix works like a charm. This is one really nice device.
Works perfect on my NC tethered to my MyTouch 3G ( rooted with CyanogenMod-6.1 )
Many many thanks to the dev. !!
Nice work, and thank you. Working fine with another rooted droid (running CM6.1).
I had the "device busy" error and went ahead and unplugged, then reset to ro with Root Explorer- no problems.
This reminds me of when the Droid first got rooted- took a little while to make progress but every few days that would be another BIG, popular advance.
Thanks so much!!!! Droid1 still has life! Yeah.
Thanks. This works great. One question. Does anyone know where I can get the original wpa_supplicant file? I misspelled it so I don't have a good backup. Thanks.
Original nook wpa_supplicant
Here ya go...
OK. Maybe I can't upload files.
I have been having trouble connecting to my work VPN with the G-Tablet. I have since tried going to ZPad 3.0 in hopes this would fix the issue. However, no luck. The VPN server is reporting an event error of 20209.
After a few hours of looking on other forums it turns out this have been an issue since Android 2.1. They have either intentionally left out the encryption module from PPPD or it was forgotten in the build. The 'fix' is to copy the PPPD file from a version prior to 2.1 (Android 1.5?) and save it to the System/xbin directory. However there is an argument over if should go into system/bin for 2.2.
Does anyone have more information on this - or better yet a fix/update? Any help on this would be appreciated.
which ROm are you using
stock ROM doesn't have VPN at all.
justauser said:
stock ROM doesn't have VPN at all.
Click to expand...
Click to collapse
I'm using ZPAD 3.0 ROM at the moment.
I have narrowed it down to a problem with the MPPE 128 encryption. I have found a PPPD that is supposed to fix the problem (see link below), but I don't now how to get it to the system directory. How do you mount system as R/W?
Alternate PPPD:
H***://melko.hiljanen.com/~qvr/android/ppp/
Root explorer will allow you to mount it that way
Sent from my DROIDX using Tapatalk
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ditto!!!!!!!!
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
The lastest info I have been able to collect on this issue is that it has been known at google since 2.0 was released. They were having a problem keeping a connection using MPPE 128 over PPTP so instead of releasing something that did not work right, they removed support for it until a later date. Said date has not been determined.
I will keep you posted as I find out more.
roebeet said:
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
Click to expand...
Click to collapse
I came across this too. Since the ppp directory exists under system/etc I have made the assumption that there is support for it (at least under ztab 3.0). In order to check using the method above we would need a terminal app or some other way to run the commands. If there is a way to do it natively I am too new to know.
Any devs willing to tackle this issue?
Newanzer said:
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
...
I will keep you posted as I find out more.
Click to expand...
Click to collapse
No luck. The Net Admin decided it would be too much work just for a tablet test (and his iPAD VPN work just fine thank you). Anyone willing to try a L2TP test?
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
nephelim said:
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
Click to expand...
Click to collapse
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
I confirm that the advent vega rom has the same problem.
Unable to use vpn.
Newanzer said:
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
Click to expand...
Click to collapse
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
rcgabriel said:
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
Click to expand...
Click to collapse
That could be worth the check. I would like to see a list of exactly what his kernel supports before I try though.
[EDIT]: Checked change log. VPN module in kernel not mentioned.
Looking over the list of known issues at Google, this problem has been known for a while. The fact that Google hasn't addressed it worries me a bit. It is possible that since phones are the largest part of their OS client, VPN isn't a high priority. They may be waiting for the open source community to solve their problem for them.
Was able to get VPN working
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
there is very easy installation get and run vpn frome purevpn........
brainyjd said:
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
Click to expand...
Click to collapse
Sorry for asking this noob question, but is this VPN fix only for Cyanogenmod, or will work with others, such as TnT Lite?
I'm running TnT lite and there no's VPN setup option.
tnt is missing the vpn shortcut
use VPN Show
Kazuyuki Eguchi/Tools
found in android market to access the vpn menu
i have used with sucess on most roms open vpn and open vpn settings
with out problems just by install them and setting it to auto run at start
with install to xbin and create a folder on internal sd "openvpn"
then place a vpn.conf file there
then connect this cause an error but causes super user to give it root rights
after that all my vpn,s work with out going near openvpn
purevpn said:
there is very easy installation get and run vpn frome purevpn........
Click to expand...
Click to collapse
Please elaborate...
Thanks!
I apologize in advance if this subject is posted elsewhere. Please kindly point me to the thread...
I'm a noob and just bought a viewsonic G-tablet.
I've been searching xda for a day now, and I cannot find a how-to guide on how to make the "adhoc wifi hack" to work on the stock ROM.
I've found this:
http://forum.xda-developers.com/showthread.php?t=754961
But I can't find a definitive answer on how to "flash this in recovery mode" specifically on the G-tab.
I'm assuming to proceed to installing ClockworkMod from (http://forum.xda-developers.com/showthread.php?t=865245)
and then flashing the "adhoc-signed zip file" from there.
I realize ClockworkMod is used to flash ROM's, so I'm wondering if this "adhoc patch" file can be flashed the same way without affecting the stock ROM.
Please let me know if this is the correct path to go down.
Thanks for your help in advance.
what is that
There is an easier solution. Search for the stock enhancement pack in the development forum. You will have to flash the file in CWM or with standard recovery. Instructions are in the post.
Enjoy your AdHoc goodnes.
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Flashed this to my Gtab to test it out. Completely broke my wifi. No longer will see any wifi or adhoc networks. I had to reflash.
I don't have a phone that I can tether to, but my son does, and I just got this working w his phone.
What I did was:
- unzipped the file from that thread above, and got the wpa_supplicant file from the system/bin dir inside the unzipped dir
- turned off wifi
- used z4root to get temporary root and root explorer to make /system R/W
- used terminal to copy the new wpa_supplicant file to /system/bin
- changed permissions of /system/bin/wpa_supplicant to rwxr-xr-x
- turned wifi on
I was then able to see his SSID, and connect using WEP.
Jim
I would like to try this with my tablet and I am having a hard time understanding these instructions. can you please make a detailed set of instructions with more steps? If you would do this I am sure there would be a lot of people that would be truly grateful, I being one of them.
Thanks,
Waspvl1
All depends....
What if you don't have an Android phone?
I use WM 6.5 phone (in my case HD2) to tether to my G-tab.
Using program WMWiFiRouter. G-tab picks it up as another regular router.
Never had a problem and most important for me, don't have to go through all of the trouble configuring AdHoc.
JMO.
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
I just updated my rooted tether on my droid x and now it works. Gtab sees my adhok without the zip.
yelrx8 said:
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Click to expand...
Click to collapse
Have exactly the same problem. Been looking for a solution for quite a while. Can't understand why this should be so difficult.
I went another route, but with the same problem.
I thought the "ad-hoc signed zipped" file install from CWM as I've described about was the issue, so I went back to the stock 3389 ROM with the tnt enhancement pack.
Exact same issue, the ad-hoc connection with WMwifirouter is connected, but no internet data will pass on the connection.
Tethering without root?
I'm definitely a noob to all this, although I have had an android phone for about 6 months now. I haven't found any roms to flash to my samsung transform so I haven't gotten root on it yet. Is there a way to tether to my g-tab (Vegan 7) with out gaining root to my phone? By the way, I really like the new rom.
I'm running a wireless tether app on my rooted Droid X and can connect my gTab to it without any updates or hacks or anything else. I'm running stock VEGAn 5.1.1 without any other tweaks.
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
rosscopicoterry said:
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
Click to expand...
Click to collapse
FWIW, I'm running this ROM and just tried it. It connected fine to my iPhone w/MyWi. No hacking required.
No adhoc transfers with Vegan-Tab Ginger RC1
I've flashed this ROM 5 times now and ran some tests each time. I can connect to my WMWifirouter adhoc network, get an IP, but there is nothing going through...
My understanding is that this rom already has a hacked supplicant. What's my next step? Should I bother trying with the provided wpasupladhoc.6.1.zip above? Thanks in advance.
I cannot figure this thing out for the life of me. Has anyone gone the route of trying to use blutooth to connect from their android phone to the g-tab? I can get it to pair but not connect. G-tab may have to go back if I can't figure this out.
1.2-4349 Ad Hoc tether
lgkahn said:
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
Click to expand...
Click to collapse
Tried it on 1.2-4349 and it appears to work just fine. Immediately detected ad hoc tether on my original Droid running gingerbread.
Does the phone need to be rooted? Or are you putting these files on the g tab?
I think I'm gonna write a small app to enable ad-hoc mode as seen for other android models. Anyone interested ?
Must have:
Single button click to enable ad-hoc wifi mode
Restore option, to revert back to previous state
Check if root is enabled, check if device is supported
Anything missing?
-----------------------------
Update:
App is available in the market.
Reported to work on:
Samung Galaxy Tab GT-P7510, GT-P7500
Samsung GT-I9100 * (Samsung Galaxy S2) reported by PAD
Samsung SPH-D710 Galaxy S2 Epic Touch 4G * reported by Scott
Samsung GT-I9000 * (Galaxy S I)
Nexus S * reported by Arpit
BBK vivo v1 * reported by thesunfei
HTC Desire * reported by Jens
Droid * reported by James
* Requires compatibility check to be disabled.
Probably more devices are supported, I will add them when reported.
Market link: https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Discussion: http://www.arenddeboer.com/wifi
This would be great...post a link when ur done
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
tarekkkkk said:
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
Click to expand...
Click to collapse
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
adeb2 said:
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
Click to expand...
Click to collapse
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
shaolinx said:
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
Click to expand...
Click to collapse
Thanks shaolinx,
It would be great to get all the info for the various devices.
I have started the build and completed the initial verifications, has root, md5hash comparison etc. If anyone can provide details about the location and specific wpa_supplicant files I can add it to this app.
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
AnakTeKa said:
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
Click to expand...
Click to collapse
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
adeb2 said:
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
Click to expand...
Click to collapse
Mine was stable after replacing the original wpa_supplicant file.
Update:
The app is nearing its final stages of completion. I will probably post the link around Sunday. Have to test it first on the stock rom as well as some of the new ICS roms. First version will be raw and unpolished but should be safe and in good working order. I will rewrite it after the initial release to make it easier to add new devices.
Absolutly YES! very interested
The app is ready, I'm currently pushing it into the Market. Will post the link here shortly.
https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Request device support or report bugs in the comments on http://www.arenddeboer.com/wifi
Features:
- Enable WiFi Ad Hoc mode (and keep infrastructure)
- Restore original settings
- Fix WiFi permission issues
Requires:
- Root Access (Superuser)
- BusyBox
Issues:
- No WiFi signal strength visible in taskbar
Please be aware this might potentially brick your device (I have tested the app vigorously on several roms and found no problems). I take of course no responsibility for any real or perceived damage...
Let me know if it works for you so I can improve the app.
Regards
FYI.....Task 13.1 works with adhoc wifi, out of the box!
Thank to the TASK team!
Not sure when they did starting this into the Rom, maybe from Pershoot's kernel?
But thanks anyway. Save me time to copy the WPAsupplicantfile over, which I carry with me from Galaxy tab 7 days!
Hehe, at least it was a nice way of learning root lated tasks in app development But it's still handy as the current kang ics roms do not ship with a modified wpa_supplicant.
when i try to connect it says obtaining ip and after that it disconnects
Ad Hoc Wi-Fi can be a bit tricky to setup, can you create a connection with other devices? I also believe you can make only a single connection between ad hoc devices. So be sure the other device is not already connected.
It was fun working on this app, but is has proven to be difficult to make something that enables Ad Hoc on a wide spectrum of Android devices. Therefor I will no longer be updating the application and will remove the "report to developer" option. My next project: running Linux native on my Galaxy Tab P7510.
Starting point will be this thread by poitee -> http://forum.xda-developers.com/showthread.php?t=1189251
Thanks for the feedback.
Nice! Thanks for the app.
I deleted my apk :-( and it doesn't look like you have a stable version up for download. You think you could hook me up with a link? Thanks man!
CM Wiki, CM Google+, Fireball Wiki, Fireball Google+
Non-development related questions and troubleshooting belong here: [Q&T][ROM] CyanogenMod 10.1 and 10.2
Contents
This Post: Instructions and information - Please read all of this post before installing CyanogenMod!
Post 2 - Restoring a non-functioning radio
Post 3 - Frequently asked questions and workarounds for common problems
Introduction
This is CyanogenMod 10.2 (cm-10.2) for the HTC Droid Incredible 4G LTE (fireball) based on Android 4.3. Usage of this ROM indicates that you understand...
the warranty on your device is void;
the developer(s) are not responsible for any damages that may occur to your device as a result of using this ROM;
there is a significantly higher chance that your device will eat your cat (for which the developer will not take responsibility).
Preparations and Installation
Get your phone ready for a new ROM
You must have an unlocked bootloader or be S-OFF (read here for instructions)
Before leaving your stock based ROM:
Turn on all GPS location services: Settings > Location > (all three location services) = On
Change network mode to CDMA/LTE: Settings > Mobile Data > Preferred Network
Backup the contents of your internal sd card. You can ignore these files/folders: ext_sd, battery_history.txt, .android_secure
Install a custom recovery: CWM or TWRP
Make a backup of your current ROM in recovery - DO THIS!
Install CyanogenMod
Perform the factory reset function in recovery and additionally wipe the /system partition
Flash the CyanogenMod zip (do not flash gapps yet)
a) If you are S-OFF, you can reboot now.
b) If you are only unlocked, and not S-OFF, you will need to flash the boot image through fastboot. Extract boot.img from the zip file and place it in the same directory as your fastboot and adb executables. While still in recovery, execute these commands one at a time:
Code:
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
The first time CM boots, change the following network settings and then reboot:
Select LTE/CDMA/EvDo network mode: Settings > (Under Wireless & Networks) More... > Mobile networks > Preferred Network
Select RUIM/SIM subscription: Settings > (Under Wireless & Networks) More... > Mobile networks > CDMA subscription
(Optional) Reboot to recovery and flash the GApps version corresponding to CM 10.2.x
Note: many apps require Gapps to be installed before GPS will lock-on a location
Updating to a new build
Make a backup of your current build in recovery
Install the new build
If you are S-OFF, reboot
If you are S-ON and HTCDev Unlocked, reboot to the bootloader and flash boot.img using fastboot (extract it from the CyanogenMod zip)
Your settings and data will be preserved. You will get an "Android Upgrading" notice upon reboot which is nothing to worry about.
Special notes about connecting to Verizon's network
Getting the RIL to play nicely with Verizon is tricky. The following quirks should be noted:
Waiting for network...: If you install gapps, the phone might seem to hang at "Waiting for network... Activation can take a few minutes" on the first boot. This takes a long time to timeout (maybe 3-5min). When it eventually fails, choose the SKIP option. Do not choose restart or the cycle will repeat. This is a one-time inconvenience that should not reappear on subsequent reboots.
Borked radio: in the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then see Post 2 for instructions on how to get the radio working again.
Official Downloads
Official builds are available at download.cyanogenmod.org/?device=fireball
Archive of older official nightlies: goo.im/devs/cm/fireball/nightly
There is currently a nasty little acpuclk bug that can cause boot-loops after rebooting the phone. A battery pull remedies this.
Unofficial Builds
These builds are not endorsed by CyanogenMod. They are my personal builds.
Most recent builds: goo.im
Archive/Mirror: mediafire.com
goo.im folder structure: visit the page to read release-specific notes
mdm-releases - Based on CM 10.1.2 stable using linux kernel 3.0
kernels - Enhanced kernels for use only in CM
cm-10.1 - CM 10.1 builds that incorporate experimental patches being considered for inclusion in official CM releases
cm-10.2 - CM 10.2 builds that incorporate experimental patches being considered for inclusion in official CM releases
GApps
Download the GApps version corresponding to CM 10.2.x
Reporting Issues and Getting Help
Policy on bug reports:
You must reproduce the issue in a clean state. i.e. install cm after wiping /data, /cache, and /system
logcat or GTFO
If these steps are not taken, your report will be ignored.
How to gather helpful data for troubleshooting
How to use the issue tracker
Getting help
There is an IRC chat room on freenode.net where you can speak with other HTC s4 and m7 users: #cm-htc. A device maintainer is usually present as well. For reference, the fireball is an s4 device in the same league as jewel (EVO 4G LTE), ville (One S), and evita (One XL), and these are all based on the Qualcomm Snapdragon S4 Plus MSM8960 processor. The various HTC One models for different carriers fall under the m7 name and use a similar but more advanced processor, the Qualcomm Snapdragon S4 Pro APQ8064. The device maintainers on s4 phones are: jewel=deck, evita=h8rift/rohan32, ville=intervigil, fireball=mdmower.
Change Log
CyanogenMod BBQLog
CyanogenMod CMXLog
fireball-specific changes:
20131107 - SMS messages no longer split at 160 characters
20131106 - fade-out animations fixed
20131029 - substantial radio updates, increase speakerphone mic volume, new power managment code in kernel
20131020 - speakerphone and headphone volumes adjusted
20131018 - usb tethering fixed, speakerphone mic fix, wake-on-volume fixed
20131015 - flickering panel fix
20130909 - initial(ish) release
Click to expand...
Click to collapse
Known Issues
Official Builds
Display flickers when brightness is set at max Workaround in post 3
Device boot-loops after restarting Workaround in post 3
High pitch background noise in camcorder recordings (only seems to affect some users)
Auto-brightness is slow to adjust after display-on
Many apps require Gapps to be installed before GPS will lock-on a location
Known Issues that will not be fixed
OTG mounting of USB sticks - Likely no hardware support
FM Radio - Likely no hardware support
MicroSD does not show as a mass storage drive when connected to the computer - UMS was deprecated in Android 3.x
Workaround in post 3
Development Information
The following trees are needed to build CyanogenMod 10.2
CyanogenMod/android_device_htc_fireball
CyanogenMod/android_device_htc_s4-common
CyanogenMod/android_device_htc_msm8960-common
CyanogenMod/android_kernel_htc_msm8960
Use the extract-files.sh script in the fireball device tree while running an official cm-10.2 build to pull necessary proprietary files into vendor/htc.
Credits
The task of bringing CyanogenMod to the HTC Droid Incredible 4G LTE was not a one man effort. I'm indebted to
htc-msm8960-devs: a talented group of developers with lots of patience while I was learning
utkanos, KemoNine, and Jin^eLD for general building questions
jose51197, Linch89, and blazingwolf for early testing reports
squeezyb for selling his fireball at a discount so I can share it with other developers
Restoring a borked radio
In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.
Downloads
Stock ROM
recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391
Instructions
From your preferred recovery, run the factory reset option
Follow the directions in this thread to install the stock ROM
Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash the stock recovery:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
Let the phone reset and boot up
Allow network connectivity to be restored (make a test call)
Turn on all GPS location services: Settings > Location > (all three location services) = On
Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash your preferred recovery: CWM or TWRP
(If you just want to run this stock ROM, you can stop here)
From your preferred recovery, run the factory reset option
Restore your ROM backup and wipe cache again before rebooting
FAQ and Workarounds
The solution to many problems
Before installation, you really need to run the factory reset option in recovery. If you are the only person experiencing a problem, try this first. It cures many problems!
Stuck at the HTC boot screen
If you are only unlocked, and not S-OFF, you need to flash the boot image through fastboot. Extract boot.img from the zip file and run
Code:
fastboot flash boot boot.img
Enable USB debugging or access Developer Options
Settings > About phone > tap 'Build number' 7 times
Boot-loops
There is a known bug in acpuclk which affects all of the htc msm8960 devices. When you reboot your phone, it might crash at the CM logo and start boot-looping. This is the kernel panicking when it continuously fails to bring up cpu1. The workaround is a simple battery pull. It's pretty reliable. After CM loads, this bug doesn't affect the device.
Screen flicker
If you notice the screen flickering rapidly:
1) Make sure you're running build 20131015 or newer
2) Try lowering the brightness a bit or using auto-brightness - this usually only occurs when the brightness is set very high
3) If using auto-brightness, when you turn on the display, let the brightness settle before touching the screen
"SIM card added" or "Waiting on... activation" notice every time the phone boots
SIM card added notice: do not hit restart, just hit back and the notice will go away
Activation notice: just hit home and the notice will go away (if the home button does nothing, just wait it out for 3-5min and then choose the skip option).
"What mobile network settings should I use?"
Verizon Wireless users in the U.S.
Settings > More... (under Wireless & Networks) > Mobile networks:
Network mode = LTE/CDMA/EvDo
CDMA subscription = RUIM/SIM
Usage of this ROM on non-Verizon carriers is unsupported. That doesn't mean it won't work; it just means you won't get support from me to try and make it work. There are several users that use this phone either out of the country on GSM networks, or on prepaid carriers in the US. I just ask that discussion specific to these scenarios be kept in separate threads -- perhaps @jose51197 can start a thread and I'll link to it from here.
Missing menu button in applications
First, set this: Settings > Buttons > Allow custom buttons = True
Option 1: Re-associate the recent apps button: Settings > Buttons > Recents Button > Short press action = Open/close menu
Option 2: Use action overflow: Settings > Buttons > Menu button > Show action overflow = True
Text messages from 6250 with message VZWNM: #
See this thread and this post.
ext_sd doesn't show files on the MicroSD
ext_sd is a leftover folder from the stock ROM. It is not used in CM because it prevents the internal storage from mounting successfully to the computer in UMS mode. File managers for Android should set /storage as their home directory to access internal and external storage.
Examples:
ES File Explorer: Settings > Path Settings: Home Directory = /storage/
Root Explorer: Preferences > General Preferences: Home Folder = /storage/
ADB reports device offline
After connecting the phone to your computer via USB, accept the prompt on the phone to allow connections from your computer.
Sound is distorted when DSP presets and/or bass boost are enabled or
Gapless music playback doesn't work
Set lpa.decode=false in build.prop:
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/lpa\.decode=true/lpa\.decode=false/g' /system/build.prop
exit
adb reboot
To revert this change later, perform the same steps above, but swap true and false in the sed line.
MicroSD will not mount as a mass storage drive when connected to the computer
UMS was deprecated in Honeycomb, so be appreciative that you can access your device at all through this method! You can use MTP connection mode if you need to access both internal and external storage:
Settings > Storage > (menu) USB computer connection > MTP
Windows and Mac recognize MTP devices automatically.
Linux requires a bit more work, here's the quick instructions:
edit /etc/udev/rules.d/51-android.rules to include these lines for adb and mtp:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
install gvfs-mtp; for Ubuntu (or Ubuntu based distributions) this can be done with:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install gvfs
Restart your computer
Phone number, MIN, and PRL do not show in phone status or
MMS messages don't send: "Invalid destination"
Go to Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription. Change the subscription type from NV to RUIM/SIM. Restart the phone.
GPS doesn't acquire a signal
From recovery, make a nandroid backup of CM
Wipe data, cache, and system
Restore a stock-based ROM backup
Enable all location services: Settings > Location > (all three location services) = On
Use a GPS application to get a lock on your position (I use GPS Test)
From recovery, wipe data, cache, and system
Restore CM backup
Wipe cache and Dalvik cache
Internal storage is not accessible by ROM or recovery
This rarely happens and unfortunately only seems to be remedied by formatting the internal storage:
Restart the phone to recovery and connect the USB cable to a Windows computer
In recovery, use the mount USB feature:
ClockworkMod(-based): mounts and storage > mount USB storage
TWRP: Mount > Mount USB Storage
When Windows informs you that it needs to format the drive in order to recognize it, go ahead and format it as FAT32
After the format is complete, use the safe eject feature in Windows followed by unmounting the USB storage in recovery
Your /sdcard partition should now be accessible
Encryption
Pre-requisites: TWRP 2.6.0.0 or newer
Encryption procedure:
Make a full backup in TWRP
Restore /data from your backup - This seemingly odd step will ensure a footer is allocated at the end of the /data partition for encryption information.
Reboot and let phone battery charge to 100%
Turn on Airplane mode
Settings > Security > Encrypt phone
Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.
Reverting encryption:
Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
Wipe your data partition
Restore your backup
Ok, we can finally split up the bug reports between cm-10.1 and cm-10.2 which are rapidly diverging. So, what needs fixin'?
mdmower said:
Ok, we can finally split up the bug reports between cm-10.1 and cm-10.2 which are rapidly diverging. So, what needs fixin'?
Click to expand...
Click to collapse
Running 20130909... I have Interface / Signal Status Style set to text. When rebooting, a number 2147483647 appears next to the antenna for some time before changing to the number representing the db level (e.g. -81). This didn't happen with any of the CM 10.1 builds.
Is there a reason official builds aren't available right now? Link works and I see roms. Looks like there's a new one up since I flashed the test build on that page.
Edit. As far as things needing fixed, lol I honestly can't find anything major. Don't have screen flicker. Focus works on cam and video. Avrcp function works great and sends metadata to cars radio screen and the sound quality over Bluetooth is better than 10.1. Only thing that is minor is my headset button doesn't work with 10.2.
Sent from my Incredible 4G LTE using Tapatalk 2
spectre559 said:
Running 20130909... I have Interface / Signal Status Style set to text. When rebooting, a number 2147483647 appears next to the antenna for some time before changing to the number representing the db level (e.g. -81). This didn't happen with any of the CM 10.1 builds.
Click to expand...
Click to collapse
I think the radio takes a bit longer to initialize in these cm-10.2 builds, so that number is likely just whatever garbage value is in memory (or some strange initializing value) before it kicks on. I'll check to see if I can initialize the signal strength to something more meaningful, like 0db (which will affect all devices, so may take a while to get acceptance). In the meantime, I will put this in the known issues.
MJL99 said:
Is there a reason official builds aren't available right now? Link works and I see roms. Looks like there's a new one up since I flashed the test build on that page.
Click to expand...
Click to collapse
The only official cm-10.2 build available is that "experimental - nodelay" build that intervigil kicked-off when he needed feedback on whether the panel delay patches were effective and/or affecting anything else. I will try to get cm-10.2 nightlies switched on as soon as possible.
mdmower said:
The only official cm-10.2 build available is that "experimental - nodelay" build that intervigil kicked-off when he needed feedback on whether the panel delay patches were effective and/or affecting anything else. I will try to get cm-10.2 nightlies switched on as soon as possible.
Click to expand...
Click to collapse
How about the 9/8 official nightly? The file size is definitely smaller than the experimental build I noticed but newer. Also how are these builds comparable to what you have posted on goo? I see there's a 9/9 build but the file size is bigger than the most recent one on get.cm.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
How about the 9/8 official nightly?
Click to expand...
Click to collapse
No such thing... look closer. I still need to write some summary pages for some of the goo.im folders.
mdmower said:
No such thing... look closer. I still need to write some summary pages for some of the goo.im folders.
Click to expand...
Click to collapse
Doh! Took me a minute. Lol
Sent from my Incredible 4G LTE using Tapatalk 2
mdmower said:
I think the radio takes a bit longer to initialize in these cm-10.2 builds, so that number is likely just whatever garbage value is in memory (or some strange initializing value) before it kicks on. I'll check to see if I can initialize the signal strength to something more meaningful, like 0db (which will affect all devices, so may take a while to get acceptance). In the meantime, I will put this in the known issues.
Click to expand...
Click to collapse
You are right. Apparently that number corresponds to the maximum value of a 32-bit signed integer. http://en.wikipedia.org/wiki/2147483647
Ok, fireball is now on cm-10.2 nightlies.
mdmower said:
Ok, fireball is now on cm-10.2 nightlies.
Click to expand...
Click to collapse
Congrats on this. My apologies, I feel like I jumped the gun releasing the cfxe beta this morning based off of your device tree work. I foolishly misread some posts and thought fireball was on nightlies already. Otherwise I would have held off a bit longer, No disrespect was intended.
Sent from my SCH-i705 using Tapatalk 2
jrior001 said:
Congrats on this. My apologies, I feel like I jumped the gun releasing the cfxe beta this morning based off of your device tree work. I foolishly misread some posts and thought fireball was on nightlies already. Otherwise I would have held off a bit longer, No disrespect was intended.
Click to expand...
Click to collapse
Oh, no worries there. Other projects were already basing themselves on cm-10.2, I just wanted to get things in better shape before flipping the switch here (well, that and a severe lack of time to get things organized).
Installed 10.2 unofficial 9/9. Unable to change nv to ruim/SIM. Tried multiple reboots, fixing permissions, wipes. Also cannot change system select. Running on nv i constantly drop signal. Same thing happened when I tried tachyon rom. Not sure if it's a new change that happened with updates or what. Someone suggested in the tachyon thread to select options in a certain order but that didn't help either.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
Installed 10.2 unofficial 9/9. Unable to change nv to ruim/SIM. Tried multiple reboots, fixing permissions, wipes. Also cannot change system select. Running on nv i constantly drop signal. Same thing happened when I tried tachyon rom. Not sure if it's a new change that happened with updates or what. Someone suggested in the tachyon thread to select options in a certain order but that didn't help either.
Click to expand...
Click to collapse
Can you test the official 20130911 nightly? This should be included, which may help. If the problem persists, re-test in a completely clean state. Btw, fix permissions doesn't do anything helpful anymore. It was even removed from CWM.
mdmower said:
Can you test the official 20130911 nightly? This should be included, which may help. If the problem persists, re-test in a completely clean state. Btw, fix permissions doesn't do anything helpful anymore. It was even removed from CWM.
Click to expand...
Click to collapse
That worked. Initial boot from a flash over previous 10.2 build reverted to nv. Changing it and rebooting saved the settings to ruim/SIM.
Thanks for the heads up about fix permissions too.
Sent from my Incredible 4G LTE using Tapatalk 2
Camcorder feedback
Can I get some reports of audio recording in camcorder? Specifically, is there a very noticable high pitch background noise in all recordings? If you report, can you also let me know whether your panels suffers from the flicker issue (in case there's a correlation).
mdmower said:
Can I get some reports of audio recording in camcorder? Specifically, is there a very noticable high pitch background noise in all recordings? If you report, can you also let me know whether your panels suffers from the flicker issue (in case there's a correlation).
Click to expand...
Click to collapse
No high pitched noise on recordings for me on newest official nightly, 9/11. I also do not have the panel flicker.
Sent from my Incredible 4G LTE using Tapatalk 2