Related
Update: New release (RLS 5)
-Comes with 'rogue tools' for overclocking and setting display density will need an update over market to support nike, myn told me he will push it to the market during the next day or so)
-feels smoother, connectivity seems to be a lot better (I never had a faster browsing experiance on my nike than with this build and opera mini), rejoining network after lost signal also seems to be faster
-nice new weather/clock widget
-if you use installd version, the androidupdate.tar from rls4 is still necessary for powermanagement
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
Get it from the vogue forums (SQSH version):
http://forum.xda-developers.com/showthread.php?t=619980
Here is a link to the basefiles I am using:
http://84.23.71.227/kerneloftheday/RootfsBasefiles20100318.zip
The kernels are from dzo's branch with a few minor fixes (vibration, irq-wakeup, red led blinking when in sleep mode). Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
HowToInstallInANutshell:
-delete old android files from sd
-extract basefiles to sdcard
-extract system.sqsh from myns package and copy to sd
-if you are on a nike100 make sure deafault.txt points at the kernel without vibration (included)
-otherwise default.txt should be fine, most parameters are ignored anyway.
-run haret
-be happy
Impressions:
-sleepmode 1 ok, wakes up, red led blinking. Battery life seems ok, but i only tested a few hours...
-very fast
-many locales, not just english like in good ol' ion
-quite stable net, nice apn autodetect (just had to select from two alternatives), working google stuff
-still not working: bt, incall volume, cam
So, give it a shot and leave your impreesions here!
mblaster
********** UPDATE ************
Installation with the NoRootfs Method is now possible with working net and powermanagement. This gives us the possibility to use the Themes and the default font and everything else that can be provided via androidupdate.tar
See the Wiki for installation instructions. Make sure that you have the provided 'androidupdate.tar' (see attachment, file is in the zip archieve) in your andboot folder along with the androidinstall.tar when installing.
To install themes just copy them in you andboot folder (must be named androidupdate.tar), reboot into menu -> update (-> fix permissions).
PS: Doesn't seem to work with eclair builds, but could work with other donuts
PPS: This should also work with ext2, if someone tried successfully please let me know. €: Works with ext2
Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
Click to expand...
Click to collapse
you've added hw3d support? I tried to do that - all that I got is 3D without textures or simply nothing - black screen. I did same as in this commit in repo.
I did the same. The only build i saw it working was aosp eclair for kaiser (gallery3d worked). Otherwise i got the same errors. I read that the other devices suffer from similar problems.
Ps: Writing this on myns donut. Everything stable so far.
mblaster said:
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
...
So, give it a shot and leave your impreesions here!
mblaster
Click to expand...
Click to collapse
Hi mblaster,
works like a charm here. Very fast and stable. This is the first ever Donut Build with stable working Data i've seen....
Only Point is, that icons are really very small. Seem to me even smaller than in the old Cupcake Releases with 320x480...
Tried higher settings for lcd.density, but screens don't fit than anymore.
Have you tried it with a non modded system Image ?
Greetz, lagloose
ECLAIR
because you are starting another section of the eclair?
already has almost no one accessing the other thread ...... I have a question there for two days and no one responds more ..
I am very impressed with the progress of the android in my eclair NIKI100 (20 keys)
is making calls, receiving messages, all volumes of the system are working (calls, music (I had to install another player why that came standard did not work), alarm etc. ..) I'm using it for three days, battery lasts long , it does not heat the unit, since I use it in everyday life.
now I have some questions for you:
is so difficult to operate the headphones?
I love listening to music, especially in the way of work, if possible, please someone do work ....
particularly hate wm, I think one day we niki users, we can get the WM and definitely use the android, (because you can try to do everything, are the gods of HTC ....).
another question, I can change the theme of the eclair? wanted it like this: http://forum.xda-developers.com/showthread.php?t=600154, it is possible??
I'm not charging, just begging! rsrsrsrs
Congratulations XDA....( GODS OF HTC)
Hi there,
together with mblaster's combination of basefiles in the first post of this Thread, the sqsh Version of the image in this thread http://forum.xda-developers.com/showthread.php?t=591104 works also...
mblaster; seem's you've found/made the ultimate combination for Donut Images. PERFECT !
Greetz, lagloose
Theming with Metamorph
I been reading around on Vogue's thread and Metamorph catched my attention. It can style up android theme. Is this apps runs well on this build. I am confused because based on this site http://www.androlib.com/android.application.stericson-xda-metamorph-xnFD.aspx it can only run n Rooted phones. What is rooted phones anyway and can this run well in nike100 with the android build posted in this thread?
When is the nand version available? I think the only thing missing now in nike100 are camera and vibration features. Great job!
More Power!!!
Anyone encountered the "Half Size" icon problem ?
This is, when there's a reload of the Home Screen, all icons are suddenly half the size than normal. I had this after leaving the Browser.
Couldn't find a solution for that behaviour. Any ideas ?
Greetz, lagloose
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
jefins said:
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
Click to expand...
Click to collapse
You have to disable PIN in WinMobile afaik for all builds so far.
About wifi: The stickies say no wifi on nike. Never.
"never ever say never" ;DD
thanks anyway for Pin code tip.
Network problem
got two bugs here.
1. browsed from wm then switchd to android. i cannot connect anymore when in android. even if i reconfigure my apn.
2. switching from phon mode to airplane mode and airplane mode to phone mode will stuck in airplane mode.
@mblaster
how to enable apn autodetect?
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
lagloose said:
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
Click to expand...
Click to collapse
me again...
just got a flash in my brain...
probably a story about the rootfs because of different load types (NoRootFs vs. Classical sqsh File) ?
so what about mounting the original sqsh Image and untaring the update "over" the rootfs ? ...
@lagloose: Might be an issue because the androidupdate.tar files are made for norootfs. Perhaps its time to move on to an installed version without rootfs...
@ebautista: Sorry, but I do not maintain myn's build. Perhaps it would be a good idea to report bugs in myn's thread in the vogue forums. APN detection worked for me right out of the box. Do you use the basefils from this thread?
€: your brainflash was faster than my typing... but perhaps you should at laest try to set the right permissions, it might work
Hi all,
Just tested sqsh Image from http://forum.xda-developers.com/showthread.php?t=628459. Not completely tested but seem to work also with our basefiles.
I'm working on a way to get themed Images for us Nike Users. Still some problems to solve, but shouldn't be that difficult...
As soon as i've found a way, i'll state it here.
Greetz, lagloose
I really would suggest to move on to NoRootFs for various reasons:
The theme packages are already available there
The basefiles are still supported and regularly updated, while SQSH is dying out, and as there are very few devs for nike we should try to profit from the progress made on other devices
There should be no drawbacks, just a few more MB on sd-card for the system
The installer for systems / updates is extremely useful (theming, installing your favourite apps in one shot ...)
Give it a try, you will find a little howto and links to ressources in the wiki
mblaster,
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
mblaster said:
...
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
Click to expand...
Click to collapse
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
hi, mblaster,
i want to download the file as "Get it from the vogue forums (SQSH version):
but i cant aceessed "mediafire"
Could you email to me a file that it can running on nike100, thnks
my mail is [email protected]
See Post 1 for UPDATE!
lagloose said:
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
Click to expand...
Click to collapse
I am quite sure now that the initrd is fine and the problem is in the Rootfs, or better what is left of it. The latest working basefiles include a Rootfs dated to 2009-11-16. There is a newer Rootfs on sourceforge (sometime in december 09) that shows the same problems (net/powermanagement/shutdown). As parts of the rootfs are included in the androidinstall.tar images, thos errors are still there. My update file (now included in post 1) overwrites those files with versions from the 11/16 rootfs. That leeds to a working system (with the new initrd).
Unfortunately the update is incompatible with the newer eclair builds that are around. Seems like they use another rootfs that rejects the old files...
Does anyone maintain a git repo of the rootfs? It would be interesting to patch the problem for good
RECENT NEWS: Fixed wifi tether on newest ICS rom, the problem was the exact same firmware issue from the original GB roms. HTC had two AP firmwares just as with the original GB roms. See notes below about the firmware for GB for more information, attached is a zip file that will replace the non-tether compatible firmware with the firmware that does work for tether. I found it interesting that HTC's firmwares from prior ICS versions worked fine without modifications, but the latest one required this hack just like the original GB HTC roms.
Looking to get your Gingerbread Rezound's wireless hotspot to work in Infrastructure mode?
Having problems with your Ice Cream Sandwich Rezound's wireless hotspot stuttering while playing online games in Infrastructure mode?
You found the right thread!
Con247 suggested I move the quick-start guide to the top of this thread.
WARNING: DO NOT FLASH THE ZIP FILE ON ICS ROMS, DO NOT FLASH THE ZIP FILE ON ICS ROMS!
I am now an official developer and committer for the Android-Wifi-Tether project. Now that is awesome!
See list here
---KNOWN ISSUES BEGINS HERE---
1. The file wifi_tether_v3_2-pre1.apk downloaded as wifi_tether_v3_2-pre1.zip?!?
This is actually a common issue when downloading any APK via a web browser and is a result of your web browser recognizing the file format for a ZIP file and the fix is very easy. Rename wifi_tether_v3_2-pre1.zip to wifi_tether_v3_2-pre1.apk and it will install.
2. When tethering to my phone over my 4G connection, the internet gets very laggy and unresponsive...but on 3G it works fine?!?
This is a common problem among those with 4G phones in 4G areas using tethering apps. Sometimes those devices are unable to operate both the 4G radio and the WIFI radio at the same time...either due to the amount of heat generated...power consumed...or possibly hardware required for both to operate that can not be shared. Unfortunately there is no fix to make it work over 4G without an issue if you are having problems. You maybe one of the lucky ones who can use it in which case this won't apply to you. If you have issues try tethering with a 3G connection, usually this will resolve the problems.
To my knowledge this is an issue that affects all tethering apps including Verizon's Hotspot. Reports on success or failures in this forum are appreciated.
3. Your post has too many words...Lots of words make things useless, can you reduce it to an index card size or just delete it all?
I'm glad you asked. You see as a person inclined to work with things on a technical level I often find myself browsing hundreds of thousands of pages of what the layman would consider "jiberish". While the "jiberish" is of no use to a layman, it is very important to other persons of the technical inclination such as computer programmers, software developers, and the like. We share details of our changes to the "jiberish" with each other openly to help further future discoveries and fixes in the realm of computer science. If I were to say remove half of the development blog attached at the bottom of this post then I would have done the equivalent of starting the next episode of your favorite tv show (ex: Jersey Shore) halfway through an episode you never saw. While missing half an episode of Jersey Shore might not seem very important, it might have been an episode that had Snookie conceiving a child with The Situation before the second half where they all go out drinking and eventually get in a fight over the way The Situation starts grinding on some other chick. Which too any Jersey Shore fan would have been monumental. The development blog is just as monumental to us technical types. I hope that my work in getting wifi tether working on GB Rezound can help others get wifi tether working on their on devices that may be having a similar problem. So in short, no I will not shorten the post.
Click to expand...
Click to collapse
---KNOWN ISSUES ENDS HERE---
---QUICKSTART BEGINS HERE---
Most problems with Wifi Tether not working are related to not replacing the firmware correctly or not uninstalling the old apk before installing the new one. Remember if your Wifi Tether is in system you will have to use a special app like Titianium Backup or Root Explorer to remove it before attempting to replace it with my patched version.
The EasyFix zip file will attempt to remove any original Wireless Tether (having it's original APK name ie: com.googlecode.android.wifi.tether-?.apk) installed if it exist, this will also fix any force close issues you are having from a incomplete or improper install of Wireless Tether as noted earlier in this thread that some have experienced. The script for EasyFix will perform a more complete fix. The update.zip contains the updated firmware and apk. It will copy the apk to your /data/app folder and the firmware to /system/etc/firmware. Enjoy!
WARNING: DO NOT FLASH THE ZIP FILE ON ICS ROMS, DO NOT FLASH THE ZIP FILE ON ICS ROMS!
EASYFIX for GB - How to enable wireless tether on the Rezound GB! In 10 EASY Steps!
1. You need GBOnly-WifiTetherComplete32P1.zip (includes my modified apk - attached) located at the bottom of this post, CleanROM 1.7+, access to terminal/adb, and root.
2. UNINSTALL ALL COPIES OF ANDROID WIFI TETHER
3. Reboot to recovery and flash GBOnly-WifiTetherComplete32P1.zip
4. Reboot back to Android.
5. Open Wifi Tether (That you just installed, It will know you using a Rezound and use NetD by default)
6. Enable encryption if desired (it works)
7. Check MSS Clamping and Routing fix (I used both in my work)
8. Check access control (if you want it)
9. Turn on Wifi Tether
10. PARTY!!!
EASYFIX for ICS - How to fix wireless tether stutter on the Rezound ICS! In 9 EASY Steps!
1. You need to download wifi_tether_v3_2-pre1.apk to your SD card (only the apk - attached) located at the bottom of this post, an ICS ROM, and root.
2. UNINSTALL ALL COPIES OF ANDROID WIFI TETHER
3. Install wifi_tether_v3_2-pre1.apk using your favorite file manager.
4. Open Wifi Tether (That you just installed, It will know you using a Rezound and use NetD by default)
5. Enable encryption if desired (it works)
6. Check Routing fix (Required)
7. Check access control (if you want it)
8. Turn on Wifi Tether
9. PARTY!!!
If for some reason you want AD-HOC tethering, simply change "Setup-Method" to WEXT (remember AD-HOC/WEXT does not support encryption). Typically everyone is wanting AP mode so Auto/NetD is likely what you are wanting.
Click to expand...
Click to collapse
---QUICKSTART ENDS HERE---
Development Blog Begins Here
I noticed that this device has 4 firmware images for the wifi radio in GB and 6 in ICS. I think part of our problem is restrictions placed in the firmware by HTC for VZW. In short you can find the firmware in /etc/firmware/fw_bcm*.bin and if you replace fw_bcm4330_apsta.bin with fw_bcm4330b2_apsta.bin (backup your firmware folder first!) you can now open an access point with wpa2 encryption. I however have not been able to get a complete connection, and it always gives up waiting on dhcp address and iptables shows no packets routed or dropped. I'll look into it further after the weekend is over right now all I have is my phone and development further than this might not be possible without my PC. I think the VZW hotspot is loading firmware b2 of the access point firmware (apsta) for it's work while standard android use loads the first firmware.
#2: ifconfig shows I have a valid interface and traffic on it but forwarding does not appear to be happening. (Packet count increases with attempts to visit website, I setup static Ip on the client to avoid DHCP failure during my tests.) Looks like I'm missing a route as well.
#3: and the interface has not been assigned an IPv4 address so that explains the lack of a route.
#4: I can get the Rezound to communicate to a (both ways if the Rezound initiates the connection/ping) tethered device but I can not get the tethered device to communicate with the Rezound (as if the data just goes into a black hole). But ARP routeing tables show correct information on both sides of the connection. I appear to have a missing route somewhere and it's getting late.
TO REPRODUCE:
You need Wifi Tether 3.1-beta 11, CleanROM 1.7+, access to terminal/adb, and root.
TURN OFF WIFI / TETHER APPS IF ON
Create a backup of /etc/firmware/fw_bcm*.bin
Replace fw_bcm4330_apsta.bin with fw_bcm4330b2_apsta.bin
Open Wifi Tether
Set device as Google NexusOne
Set method as NetD (master)
Enable encryption if desired (it works)
Change Lan (Select 192.168.2.0/24)
I have not determined if MSS Clamping or Routing fix are needed but my tests include routing fix.
Turn on Wifi Tether
in terminal do the following without qoutes:
"su"
"/system/xbin/ifconfig eth0 inet 192.168.2.254 netmask 255.255.255.0 mtu 1500"
On the device you want to connect to the hotspot with do the following
Set static ip information (DHCP will not work at this time)
IP: 192.168.2.103
Netmask: 255.255.255.0
Gateway: 192.168.2.254
DNS1: 192.168.2.254
DNS2: 192.168.2.254
Connect device to hotspot.
Device (not the Rezound) will show connected but have no network access at this time.
On the Rezound in the terminal you can verify the device is connected with ping
"ping 192.168.2.103"
You will see the ping replies! (Press volume down + "C" to stop once confirmed if using terminal)
WOOT! We're half way there! I think if Wifi Tether setup the interface with the IPV4 address properly instead of us having to go back and set it after the fact that this may work without any further trouble.
Once we have Wifi Tether resolved, I will have my dream device! ...at least for the next 6 months \\
#5: I HAVE IT! I will post a working fix/update within a few hours! It works!
#6: FINAL SOLUTION!
The problem was two fold, first the phone has two sets of firmwares and by default loads a non-accesspoint capable version when trying to setup an accesspoint. I've already explained that part in my first post. The second problem, the accesspoint interface firmware operates on eth0, which is NOT what wireless tether expects...so I either had to intercept tether's scripts and fix the interface name OR modify tether to use the proper interface name (which I did both, but the fix I am posting is a modified tether without scripts...it is simpler, and EASY FOR THE WIRELESS TETHER TEAM TO FIX).
ADVANCED FIX - How to enable wireless tether on the Rezound! In 12 EASY Steps!
Please scroll down to EASY FIX 2 for instructions on using con247's zip in recovery instead of moving files around in root explorer yourself.
Download the attached MODIFIED WIFI TETHER APK, it has the interface names for the networking accesspoint corrected to eth0 and not wl0.1 (which was the default for google nexus).
1. You need Wifi Tether 3.1-beta 11b2 (my modified version), CleanROM 1.7+, access to terminal/adb, and root.
2. TURN OFF WIFI / TETHER APPS IF ON
3. Create a backup of /etc/firmware/fw_bcm*.bin
4. Replace (existing) fw_bcm4330_apsta.bin with fw_bcm4330b2_apsta.bin in /etc/firmware
5. Install modified Wifi Tether
6. Open Wifi Tether
7. Set device as Google NexusOne
8. Set method as NetD (master)
9. Enable encryption if desired (it works)
10. Check MSS Clamping and Routing fix (I used both in my work)
11. Turn on Wifi Tether
12. PARTY!!!
For those with trust issues download apktool and decompile wifi tether yourself, open smali/com/googlecode/android/wifi/tether/system/Configuration.smali
using a NON DESTRUCTIVE TEXT EDITOR! I.E. one that will not change anything you do not specifically change! I used JEdit on Ubuntu, I read Notepad++ on windows will work good too.
Under ".method private setupSoftapGoogle()V"
Change line 2707:
.line 327
const-string v0, "wl0.0"
To:
.line 327
const-string v0, "eth0"
Save and rebuild & sign apk.
Have a great day!
This hack is all of my own work, please give me credit if you use this or include it in your rom/mod!
Donations are always welcome as I do appreciate a good beer ;-D
Update:
Questions about will it work on my ROM or Kernel, you will just have to try it. Remember to backup your firmware folder to revert incase you make a mistake. This method should work on any GB rom and should work on ICS as well. So long as the kernel/rom dev has not radically modified their ROM/Kernel in the wifi/tether department. Enjoy!
Also attached some nifty images with my chicken scratch on them to help point out the original file differences (in size) as well as what we are replacing in case there was any confusion.
EASYFIX 1/2 & INSTRUCTIONS REMOVED - PLEASE SEE EASYFIX
Enjoy, Thanks goto con247 who packaged up a recovery zip to move the firmware!
This fix has been updated and is now using Beta12 of Wifi Tether.
The patch is slightly different instead of patching Google's Nexus driver I just copied it to it's own routine patched the device name as indicated in the above patch instructions, renamed it to HTC Rezound GB and added it to the device menu. No more looking like a hack here. The Wifi Tether team could easily add this patch to their base code (I did this using a text editor on the smali code), but it would only benefit HTC Rezound GB users with rooted devices. Oh well...Enjoy Everyone!
Update 04/11/12: Fixed downloads...not sure what was wrong. Re-uploaded the files and all is well. Sorry for the inconvenience.
Update 04/12/12: Really fixed downloads...I do not know what has happened. I tested them when they first went up and they worked fine. Could be a browser issue maybe? I was using Chrome, this time FireFox. Never had any issues uploading before. I downloaded both files again completely to be sure this time, everything looks good. Again I apologize for the inconvenience.
Update 04/23/12: Updated patch to latest beta14.
Update 04/28/12: Corrected firmware/module file locations for Rezound. Removed SoftAP (does not work on Rezound GB profile anyway). Tested Wext on Rezound profile (works for those wanting Adhoc, note: encryption not supported on Adhoc). Added patch notice to App title bar so you know what is installed (default vs patched). Also gave myself credit for the patch in the about box and added a link to this thread for future reference and added a donation button in the about box for those who feel generous (Don't forget about the Wifi Tether team, without which non of this would be possible!). Enjoy! (Fixed Download: I forgot to sign the APK, sorry everyone!)
Update 05/02/12: Moved quickstart guide to top per con247's suggestion. Also note this fix is NOT needed for any ICS variants, only GB.
Update 05/18/12: Per feedback from Kidney Poker I have patched the Wifi Tether Application to include a Rezound ICS profile, in that profile I added correct ICS firmware folder/filenames (The Rezound's firmware/modules are in different locations than Google ICS), the result of which I believe caused some stuttering in the connection was running applications requiring a consistent and low ping (I.E. Online Games). I appreciate any additional feedback anyone would like to add on this matter, let me know if this patch improves your tethering experience or not. Thanks! ICS does not need firmware files moved for AP mode to work so do not flash the zip, you only need the apk of the patched Wifi Tether application. DO NOT INSTALL WifiTetherFixCompleteR14B.zip on ICS!!!
Update 06/01/12: Added beta15 PUBLIC TEST 1 UNOFFICIAL Wifi Tether with my changes that I am submitting to the Wifi Tether team. Give it a try, fiddle with the options, tell me how it works! Post your feedback and Thanks!
Update 06/02/12: Beta15 PUBLIC TEST 2: Fixed bug where Automatic quota shutdown appeared twice in settings. Configure ed keep-alive shutdown timer option to be disabled when keep-alive is set to retry indefinitely.
Update 06/27/12: Android wifi-tether now has an official download with my changes includes and some new features added! Woot Woot!
Update 07/14/12: I am now an official developer and committer for the Android-Wifi-Tether project. Now that is awesome!
Update 08/21/13: Updated post to include fix for latest ICS release, the firmware issue from GB returned to this version of ICS. Simply replacing fw_bcm4330_apsta_b1.bin with fw_bcm4330_apsta_b2.bin located in /system/etc/firmware/ and this change will enable wifi tether using android-wifi-tether. Updated zips to include latest non-experimental version v3.3 beta 2 and attached for direct download. GB firmware zip is intended only for GB roms, and ICS Latest zip is intended only for the latest ICS version v4.03.605.2 710RD. You will need a custom kernel to tether, the stock kernel will not work as it lacks the proper NAT layers to do so.
Click to expand...
Click to collapse
!!! STOP HERE - DOWNLOADS BELOW !!!
Wow. I'm impressed. Keep up the good work. It sounds like you're on to something.
Sent from my ADR6425LVW using xda premium
omg if you get this to work I will give you all the cookies your heart desires!!!
I understood about a total of 6 words in the OP, but I do know that this will be awesome if you can get it working. Nice work
any update on this?
Unfortunately I've not been able to resolve the routing issues yet, communication starting from the client towards the tether point (rezound) arrives but does not seem to get past the interface device (packets are counted but data is getting dropped after reaching the rezound. I am still trying to resolve this.
I got it, will post a working update within a few hours!
#2: MOD COMPLETE! ENJOY!!!
Fantastic work!
will this not work on ineffabilis 1.3?
It should work on GB roms.
will this work If im rooted and have ziggy's oc kernal but still on stock debloated (by me) vzw gb rom?
I looked in the firmware folder and I couldn't find the bcm* file to backup and both of the files I'm supposed to replace each other with are already in there.
antispiral said:
I looked in the firmware folder and I couldn't find the bcm* file to backup and both of the files I'm supposed to replace each other with are already in there.
Click to expand...
Click to collapse
I believe you are supposed to rename the one with the b2 in it to remove the b2 and let it replace the one that is already there WITHOUT the b2. if that makes any sense.
Regards to other roms/kernels:
You will have to try it yourself, but this method should work on all Rezound GB Roms as long as the firmware folder is there and the dev has not modified anything related to tethering/wifi in a radical way.
That is absolutely right! Replace the existing file fw_bcm4330_apsta.bin with the fw_bcm4330b2_apsta.bin file.
con247 said:
It should work on GB roms.
Click to expand...
Click to collapse
Con where's the flashable zip man? J/K but that would be awesome. This may make me go back to GB. Thanks for this
Sent from my ADR6425LVW using XDA
Doddzilla said:
Con where's the flashable zip man? J/K but that would be awesome. This may make me go back to GB. Thanks for this
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
This is one of the reasons I haven't went to ICS yet. I have everything I wanted (minus ICS) with this phone running Gingerbread now. Once ICS source is out, that may change.
SirGatez said:
That is absolutely right! Replace the existing file fw_bcm4330_apsta.bin with the fw_bcm4330b2_apsta.bin file.
Click to expand...
Click to collapse
so can't I just delete the fw bcm4330 instead of replace since the fw bcm4330b2 is already in the folder?
Confirmed working on Ineffabilis 1.3. Tethering to my Mac running Lion and I didn't have to change any settings in the Wifi Prefs. DHCP worked just fine.
antispiral said:
so can't I just delete the fw bcm4330 instead of replace since the fw bcm4330b2 is already in the folder?
Click to expand...
Click to collapse
Yes, delete fw bcm4330 (or backup to another location) and rename fw bcm4330b2 to fw bcm4330
I understand that this ROM was put together mainly for Lexmazter's personal use, so thanks for making it available for us all.
I have been testing it for some time now and decided to post a couple of things I have noticed so far. Maybe some of these points could be added to the first post's FAQ in the development section (if they are of any use)?
WiFi patch: http://forum.xda-developers.com/showthread.php?t=1579585
---
This one was a necessity for me, otherwise the WiFi simply silently died/froze after being idle for some time.
Couldn't erase SD card (Settings --> Storage --> Erase SD card)
---
I managed to fix it by copying vold from DSC ROM and replacing the old one (/system/bin).
I got the idea from: https://code.google.com/p/cyanogenmod/issues/detail?id=4004 (comments 7-9)
Useless/detrimental(?) entries in Build.prop:
---
ro.telephony.default_network=0
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.amr.wideband=1
I had to nuke those entries to get the phone working & staying in 2G, even after a reboot. Is there actually any reason to force the phone to use 3G when it only seems to override the settings that the user could do in Settings --> Wireless & networks --> Mobile networks? The existence of ro.ril.enable.amr.wideband=1 broke making/receiving phone calls in 2G.
The FCing menu in settings + the non-working reboot option:
---
Settings --> CyanogenMod settings --> Display --> Automatic backlight --> Edit other levels... causes a FC. Reboot phone --> Recovery does not work. These are purely cosmetic things, but they could just be removed as they're doing nothing anyway. Basically what lordmorphous did in: http://forum.xda-developers.com/showpost.php?p=24550723&postcount=43
However, I guess that because this ROM uses theming, the framework-res.apk would be needed to be decompiled etc.. in a proper fashion?
I would love to see more versions and possible improvements of this ROM. For me things like being as close to 2.3.7 as possible + CM's permissions management alone make this a keeper.
Merely_an_observer said:
I understand that this ROM was put together mainly for Lexmazter's personal use, so thanks for making it available for us all.
I have been testing it for some time now and decided to post a couple of things I have noticed so far. Maybe some of these points could be added to the first post's FAQ in the development section (if they are of any use)?
WiFi patch: http://forum.xda-developers.com/showthread.php?t=1579585
---
This one was a necessity for me, otherwise the WiFi simply silently died/froze after being idle for some time.
Couldn't erase SD card (Settings --> Storage --> Erase SD card)
---
I managed to fix it by copying vold from DSC ROM and replacing the old one (/system/bin).
I got the idea from: https://code.google.com/p/cyanogenmod/issues/detail?id=4004 (comments 7-9)
Useless/detrimental(?) entries in Build.prop:
---
ro.telephony.default_network=0
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.amr.wideband=1
I had to nuke those entries to get the phone working & staying in 2G, even after a reboot. Is there actually any reason to force the phone to use 3G when it only seems to override the settings that the user could do in Settings --> Wireless & networks --> Mobile networks? The existence of ro.ril.enable.amr.wideband=1 broke making/receiving phone calls in 2G.
The FCing menu in settings + the non-working reboot option:
---
Settings --> CyanogenMod settings --> Display --> Automatic backlight --> Edit other levels... causes a FC. Reboot phone --> Recovery does not work. These are purely cosmetic things, but they could just be removed as they're doing nothing anyway. Basically what lordmorphous did in: http://forum.xda-developers.com/showpost.php?p=24550723&postcount=43
However, I guess that because this ROM uses theming, the framework-res.apk would be needed to be decompiled etc.. in a proper fashion?
I would love to see more versions and possible improvements of this ROM. For me things like being as close to 2.3.7 as possible + CM's permissions management alone make this a keeper.
Click to expand...
Click to collapse
Hi and thanks for the feedback, i would like to begin with the first things.
WiFi patch is not needed if you are using LXdroid Rom 0.2 and baseband 366, i was using it like that a lot and i didn't had any issues with the WiFi...
--
As for erase SD card, i never really tested that feature, but for all i know, it should work just fine...
--
Those useless/detrimental build.prop you put there were left there from the original build.prop of CM7, you can override those settings from Settings, i can assure you that ro.ril.enable.amr.wideband=1 does not break 2G calls as i was most of the time on 2G to save battery, i had the option in power widget to change it ti 3G when i needed internet connection.
The framework-res.apk you provided there will be include in the next update, i think i'm going to release one with small fixes soon.
The framework-res.apk doesn't need to be decompiled in a proper manner, you can use any archiver you like and change the insides of it .
To keep away from any other problems, if you upgraded from 2.3.3 or any other ROM besides CM7 based ones, make sure you fully wipe everything, from dalvik to factory reset from recovery and factory reset from dell (white letters).
--
Will try to update, but it will be only with small fixes
I am able to get the native hotspot working on rooted JUUS06252012 and bypass the "dial 611" message. I'm posting this right now via wifi tethering, on a prepaid plan with a data package.
Before trying to get the native hotspot to work, I did try a few apps first. WiFi Tether for Root works in WPA mode (configured as Epic 4G Touch), but it broke wifi completely after tethering and wifi stayed broken even after a hard reboot. Logcat said a wifi driver file was locked and could not be loaded. I had to factory reset to get wifi working again. FoxFi seemed to work at first, but force closed whenever a client connected.
The mod: I found two values in settings.db to be modified. As we all know, there are many ways to update a sqlite database, but here is one easy way, keeping in mind that the Pantech Burst factory rom lacks many things like BusyBox or the commandline sqlite3. Yes, you need to be rooted:
1. Install Andsen's aShell and aSQLiteManager (not SQLiteManager).
2. Run aShell, check root, tap File Explorer, go to /data/data/com.android.providers.settings/databases, open settings.db, when prompted to open a copy, say yes and open with aSQLiteManager, tap table secure, tap data and tap "edit" for each of the below
softap_free_supported=1 (old value 0)
softap_entitlement_interval=0 (old value1440)
Then tap back twice. When prompted to commit changes, say yes and exit aShell.
3. Reboot and you can now use the native hotspot. Install a toggle widget for convenience.
*EDIT: with this mod, turning on hotspot from the 2nd level "Portable Wi-Fi hotspot settings" page works reliably, whereas turning it on from the 1st level "Tethering & portable hotspot" page would show the "dial 611" message. Many hotspot widgets work reliably as well, such as HotSpot Toggle, Hotspot Widget or many others.
EDIT Read through the thread for ICS
------
Pantech Burst Love, Anyone? Anyone?
Pantech Burst Essentials
ty so much!
I got it to work with sqlighteditor in settings storage,secure and change entitlement_pdp _checked changed from 0 to 1 I have used this on many art phones with.prepaid Sims
Sent from my PantechP9070 using xda premium
lost_ said:
I am able to get the native hotspot working on rooted JUUS06252012 and bypass the "dial 611" message. I'm posting this right now via wifi tethering, on a prepaid plan with a data package.
Before trying to get the native hotspot to work, I did try a few apps first. WiFi Tether for Root works in WPA mode (configured as Epic 4G Touch), but it broke wifi completely after tethering and wifi stayed broken even after a hard reboot. Logcat said a wifi driver file was locked and could not be loaded. I had to factory reset to get wifi working again. FoxFi seemed to work at first, but force closed whenever a client connected.
The mod: I found two values in settings.db to be modified. As we all know, there are many ways to update a sqlite database, but here is one easy way, keeping in mind that the Pantech Burst factory rom lacks many things like BusyBox or the commandline sqlite3. Yes, you need to be rooted:
1. Install Andsen's aShell and aSQLiteManager (not SQLiteManager).
2. Run aShell, check root, tap File Explorer, go to /data/data/com.android.providers.settings/databases, open settings.db, when prompted to open a copy, say yes and open with aSQLiteManager, tap table secure, tap data and tap "edit" for each of the below
softap_free_supported=1 (old value 0)
softap_entitlement_interval=0 (old value1440)
Then tap back twice. When prompted to commit changes, say yes and exit aShell.
3. Reboot and you can now use the native hotspot. Install a toggle widget for convenience.
*EDIT: with this mod, turning on hotspot from the 2nd level "Portable Wi-Fi hotspot settings" page works reliably, whereas turning it on from the 1st level "Tethering & portable hotspot" page would show the "dial 611" message. Many hotspot widgets work reliably as well, such as HotSpot Toggle, Hotspot Widget or many others.
------
Pantech Burst Love, Anyone? Anyone?
Pantech Burst Essentials
Click to expand...
Click to collapse
Did that and my phone is now stuck on boot screen. Removing battery didn't help either
_lost can you check to see if your guide can be updated for the new ICS release? or atleast put a warning up to let people know not to try if they are running ICS on their Pantech Burst?
After a lot of trial and error I have this working on ICS. I tried the free apps first and at first I couldnt even get the change to take. When I did by copying the file editing it then replaceing it the system would just hang on boot. I did get it to work though after having to wipe my device a few times. Now this may still work with the free programs im not realy sure as I figured id give the paid ones a try and got it working. I used the program root explorer. I copied the settings.db and pasted the copy in the same folder. Then I edited the copy in SQLite editor although it still couldnt edit the original.. Then in root explorer I renamed the old file by adding an extension to the end and renamed the new file to replace the old one. Then in root explorer i double checked that the permissions were the same as the old file and also..... (I THINK THIS WAS THE IMPORTANT THING BY THE WAY) I checked the ownership settings in root explorer it was already set to "system" just like the old file. I think the other programs may have been changing the owner of the new file causing issues. Anyway after rebooting it started right up and I can turn on wifi hotspot from either menu. On gingerbread it only worked from the one menu. I hope this works for you guys!!!!!!
by the way i used the original two edits from the first post
jkiwitt said:
I got it to work with sqlighteditor in settings storage,secure and change entitlement_pdp _checked changed from 0 to 1 I have used this on many art phones with.prepaid Sims
Sent from my PantechP9070 using xda premium
Click to expand...
Click to collapse
Hey thanks! This was the setting that did the trick for me on my Pantech Crossover (P8000). I had recently done the vendor upgrade to Gingerbread and lost root, but more importantly, SVTP's Wifi Hotspot & USB Tether Pro stopped working for me.
I rooted using pawaa's excellent guide and thought that would do the trip, but no such luck. Found this thread, bought SQLite Editor and made the aforementioned changes and all was well.
Guess I don't need SVTP anymore, but the widget works well, and I don't mind having paid for it for the month or so that it worked under Froyo. (Also, it was paid for out of my Nexus 7 $25 credit.) Anyways, just wanted to mention this in case anybody else was trying to get tethering working again on the Crossover after upgrading to 2.3.6.
I am having rooted JUUS03122012.
My Root/data folder is empty
lost_ said:
I am able to get the native hotspot working on rooted JUUS06252012 and bypass the "dial 611" message. I'm posting this right now via wifi tethering, on a prepaid plan with a data package.
Before trying to get the native hotspot to work, I did try a few apps first. WiFi Tether for Root works in WPA mode (configured as Epic 4G Touch), but it broke wifi completely after tethering and wifi stayed broken even after a hard reboot. Logcat said a wifi driver file was locked and could not be loaded. I had to factory reset to get wifi working again. FoxFi seemed to work at first, but force closed whenever a client connected.
The mod: I found two values in settings.db to be modified. As we all know, there are many ways to update a sqlite database, but here is one easy way, keeping in mind that the Pantech Burst factory rom lacks many things like BusyBox or the commandline sqlite3. Yes, you need to be rooted:
1. Install Andsen's aShell and aSQLiteManager (not SQLiteManager).
2. Run aShell, check root, tap File Explorer, go to /data/data/com.android.providers.settings/databases, open settings.db, when prompted to open a copy, say yes and open with aSQLiteManager, tap table secure, tap data and tap "edit" for each of the below
softap_free_supported=1 (old value 0)
softap_entitlement_interval=0 (old value1440)
Then tap back twice. When prompted to commit changes, say yes and exit aShell.
3. Reboot and you can now use the native hotspot. Install a toggle widget for convenience.
*EDIT: with this mod, turning on hotspot from the 2nd level "Portable Wi-Fi hotspot settings" page works reliably, whereas turning it on from the 1st level "Tethering & portable hotspot" page would show the "dial 611" message. Many hotspot widgets work reliably as well, such as HotSpot Toggle, Hotspot Widget or many others.
------
Pantech Burst Love, Anyone? Anyone?
Pantech Burst Essentials
Click to expand...
Click to collapse
I even updated to rooted JUUS06252012 but could not find ' /data/data/com.android.providers.settings/databases' folder in root . Please somebody help.:angel:
For Android 2.3.
A simple method for switching on Tethering:
1. Install from market Secret Codes Revealer (play.google.com/store/apps/details?id=com.afp_group.software)
2. Search Codes
3. List Codes
4. Tap on "softapactivation"
5. Launch code
6. Now we on SoftapHiddenMenu
7. Check on all checkboxes
8. Save
9. Reboot
10. Enjoy full tethering
Sorry for my bad english
This works on the new ICS update on AT&T
Sent from my PantechP9070 using Tapatalk 2
Wifi tethering option is working fine with my PantechP9070 normally. I am on stock ICS rooted.
Tapatalking from my hTc Droid Incredible 2 on MTS
phillywiiman said:
This works on the new ICS update on AT&T
Sent from my PantechP9070 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of the methods above in ICS and none of them work. Not only do they not work, but if you try to edit the com.android.provider.settings AT&T will block your incoming calls, disable all notifications for messages, and break the home button. I was not able to find away to fix this without reflashing the ROM. I tried repairing the permissions but it did not help. I could not simply change the settings back since it seems AT&T's program did that for me and nonetheless deactivated me.
I can't get this to work either. My phone was purchased as an unlocked device, I didn't realize some things are still locked. :'(
I tried multiple times. I am running the stock (rooted) Android version 4.04 Baseband version JUUS09032012. Everything was setup fresh, all I did was root the device, get my Google account logged in and install the Superuser app, aShell and aSQLiteManager. I didn't stop, disable or uninstall any apps. Then followed the instructions here carefully.
I also tried the "Secret Codes Revealer" method with no luck. But I did not get any popups requesting root access when trying that method, so I can't imagine it doing anything.
I really love the phone - it is everything I want other than the tethering restriction. Hopefully this will be figured out before I am tempted by the new Nexus phone to be announced soon.
I used root browser to make a copy of the database file, edited it with asqlite, then went back to root browser and renamed the copy to the actual database. Then I booted into cwm and selected fix permissions and it works fine. That was the only way I could get it to work.
Sent from my PantechP9070 using Tapatalk 2
thomasinnv said:
I used root browser to make a copy of the database file, edited it with asqlite, then went back to root browser and renamed the copy to the actual database. Then I booted into cwm and selected fix permissions and it works fine. That was the only way I could get it to work.
Click to expand...
Click to collapse
Thank you so much! That worked.
meivin said:
I tried all of the methods above in ICS and none of them work. Not only do they not work, but if you try to edit the com.android.provider.settings AT&T will block your incoming calls, disable all notifications for messages, and break the home button. I was not able to find away to fix this without reflashing the ROM. I tried repairing the permissions but it did not help. I could not simply change the settings back since it seems AT&T's program did that for me and nonetheless deactivated me.
Click to expand...
Click to collapse
i face the same problem but i decided to try it one more time
here is what I done
i use a sqllite editor premium
do a backup of the files
i use the root explorer and copy the settings.db and paste in the same folder
after that i used sqlite editor and then settings.storage
after that i change the following values
softap_free_supported=1 (old value 0)
softap_entitlement_interval=0 (old value1440)
entitlement_pdp _checked changed from 0 to 1
than sve it and replace the settings.db by deliting or renaming the original one
than change the settings -copy.db to the settings.db
and delete all the other files that exist in that folder except settings.db (delete .db-shm and .db-wal also)
or
replace all the files in the data/data/com.providers.settings/databases from the attachment
Just download the attachment from Post# 17 and use Root Explorer to overwrite/replace all the files in the data/data/com.providers.settings/databases from the attachment.
It works like Charm.
Thanks irbaaz
Hmm... I didn't touch "entitlement_pdp _checked" but it all seems to work anyway.
almark said:
For Android 2.3 and 4.0
A simple method for switching on Tethering:
1. Install from market Secret Codes Revealer (play.google.com/store/apps/details?id=com.afp_group.software)
2. Search Codes
3. List Codes
4. Tap on "softapactivation"
5. Launch code
6. Now we on SoftapHiddenMenu
7. Check on the first 2 checkboxes
8. Save
9. Reboot
10. Enjoy full tethering
This works on rooted AND NON-ROOTED Pantech bursts.
This is so easy. I tested on 4 different bursts including mine. 2 rooted and 2 stock. , 3 on ics, 1 on gingerbread (just arrived) All unlocked. None using AT&T. 3 on Digicel Antigua 4GLte Network.
Thanks Almark for the lead. You're a life saver.
Sent from my PantechP9070 using xda app-developers app
Click to expand...
Click to collapse
Hello all, new to modding devices but having fun with it!! These forums have been a huge help, but still stuck.
situation;
Verizon note 2 4.4.2
-rooted
-used buildprop editor to open apn list
-ED file explorer let's you wright files, so added apn in system/etc apns-conf file
-reboot all that, I added two identical apn scripts in the folder just to test, and I get
Two on my list to choose from.. still no dice. Have tried several things like switching gsm, global etc. Still nada..
I'm sure I am just missing something entirely obvious if anyone can chime in.
Thank you all in advance!!
Well... I really am at a loss here.. I am going to try and go by MetroPCS. Maybe its something on their end. Still, any suggestions greatly appreciated.
Thanks
Soooo.. success!! In case anyone cares, calling up metropcs and setting it up through them did the trick. Done deal