Related
[REF] █▌█▌█▌█▌THE ANDROID WALK>THROUGH - Guides, Explanations, Fixes & Tips █▌█▌█▌█▌
Find here and EXTENSIVE collection of every single information available on Android : Kernels, Builds, Updates, Fixes and much much more...
Posts Guide
Post 1 : Android Encyclopedia
Post 2 : Complementary Guides
Post 3 : Problems, and Fixes
Post 4 : How-to's
WARNING : This post needs updating, formating, typo-checking. Please be patient, as i'll need to collect a lot more data, and rest a little as well
Mods, I made a typo in my post ^^ Can somebody help there? Can't find how to edit a poll Thanks!
A big THANK YOU to all the contributors of this thread, who are helping me, and the others!
This is a GUIDE/LINKS Thread. Suggestions are welcome, but :
PLEASE DON'T ASK QUESTIONS HERE Please check this (How to post a good question and maximize answers)
USE THE THREAD LINKS PROVIDED INSTEAD ON POST 3
You will save yourself double the time : On DEDICATED THREADS you will have more experienced users and more traffic, thus a faster and/or better answer!!!
Why this threadI've been reading a lot lately, but still haven't found an updated thread for basic questions, or just a welcome stop-by.
I'd add I'm not a cook neither a developer, but came to understand a few things by myself that weren't precisely told
(A common flaw of computer advices : Do this to solve that - You don't need to know how or why)
This brings pros, as I'll be more oriented towards the end users, but cons as I'll sometimes lack the necessary skills to go further. As a whole, I do believe this may still help understand the basics, and help get rid of a few misunderstandings. This is why there'll be a lot of "seems" and "mays" but in the end, most of the "basic" data here is accurate, and i'll get better as time goes by.
My current hardware and software
- HD2 Europe FR
- Hastarin 7.6 on PhireMod Sense 1.5
- Dutty CDC V11 COM2 FR
- Radio 2.15.40
However, this post covers Android as a whole, and lots may apply to other devices, be it with or without Haret "emulation"
Legend:
-
Simple Explanation
->
A parameter or file you may change/trigger in order to enhance/solve problems/your Android build (yes, this works both ways)
[file]
An actual Windows Mobile/Windows XP/Seven file. You can see them using a SD Card reader/usb cable/etc
root/
This is Android C:\ drive
A file or directory present/visible ONLY when under Android on the phone.
/
Same as root/, but with some laziness included
(exe)
Means this is a Windows XP/7 Program
(apk)
Means....!
A. Android itself
There are a few things you need to know on android on HD2.
What an Android build is made of :
- A "sound enabler" [CLRCAD.exe],
- An Android Bootloader for WM6 [HARET.exe],
- A startup command [startup.txt], Touch-screen Calibration Instructions [ts-calibration], a boot logo [initrd.gz]
- An Android Kernel [zImage],
- An Android Root Filesystem [rootfs.img]
- A ROM image [system.ext2]
- A data container [data.img]: This holds your texts, contacts and everything else. Sometimes provided BLANK by some chefs to avoid high boot times (cf Updating Android)
All of these should be on the "Android" folder of your SD card.
Note : For an easy launch of your Android, I recommend Exceller Multiple Boot Loader (link here), that you can set on autoboot (or not)
When you launch Android via EBL on WM6:
- [CLRCAD] enables sound
- [Haret] is launched, then totally closes Windows Mobile (all resources shut down)
- Kernel+Drivers, ROM and Data are loaded
What to learn about this:
- There are hardware/software interactions happening when Haret "closes" WM6 and it's own drivers take place.
-> It may be useful to activate "Airplane mode" in Windows to avoid pieces of the radio chip to stay indefinitely on without Android being able to shut them off (cf Power consumption problems)
-> Full charging may not be achieved under Android, this because of Android drivers not being able to correctly write the battery status (yet). To get to 100%, charge when the phone is off or under WM6 (although i do manage to have a 100% under Android under certain circumstances)
-> It may as well be useful to launch Android with Keypad lights on in order to ensure that lights are working properly. This depends on hardware and software, and varies from people to people.
->Flashing a radio under WM6 has the same impact over Android, as the radio chip instructions are shared between Android and WM6 (cf Robo Voice)
->The WM6 ROM used, while seemingly not worthy of attention (as it is "shut down" by Haret), seems to handle some important work when closing itself or interacting with the hardware. That's why changing from "Stock rom" to a "custom one" may resolve a few problems too.
B. Android's Internals
First, at the current state of development, Android is ENTIRELY run through the SD card.
-> Class 2 cards have been reported to being a source of annoyance, still being able to correctly run Android, but slowing a lot of problems. T-MO USA users have different experiences with the bundled microSD card provided. However, i'd advise using AT LEAST a Class 4 microSD, with correct formating.
- File explorers under Android are reporting a "root/" directory with several files and folders, and a "root/sdcard" folder. In fact, the [data.img] of the SDcard IS (some part of) the "root/" (unzipped for you to see) whereas the SDcard is...the SDcard. That's why removing the SDcard with android running may freeze the whole file-system.
- The actual NAND work is approximately for the devs to put the [rootfs.img and system.ext2] inside the phone flash, to ensure that Android still runs when removing the Sdcard. The problem is : the [data.img], that holds Android's data, may still be on the SDcard (as EU HD2 only have 512mo of ROM, and Android already takes 300 just for booting)...To be continued.
Kernel, Libraries, Modules, File-system, and the like...
Ok, I know little about them, as I'm not a developer or a cook, but here are the basics
Kernel bundles
-> [zImage] : It is the main kernel file, it seems to contain the primary drivers using for controlling the phone. You can update this file by downloading a "Kernel" like Hastarin 7.6, by powering the phone in WM6, and replacing the [zImage,Haret,initrd.gz] in the Android folder of the SDCard
- [Initrd.gz] seems to be the logo launched when Haret is loading Android (needs confirmation)
- [rootfs.img] : It handles the basic file-system
Android Builds Bundles (further explanation)
- [system.ext2] : It contains the Android files described there-under, also provided in a build
Modules
Located in /system/lib/modules, they are here to handle the Bluetooth and Wifi. They sometimes need to be replaced manually (aka "pushed" via the shell/terminal)
Libraries
Located in /system/lib/ or /system/lib/hw, they handle other elements, like lights and so on. They can also be uploaded manually when needed.
File-system Organisation
- root/acct, root/bin, root/cache, root/config, root/dbgfs, root/sbin, root/dev, root/mnt, root/proc, root/sys, root/tmp seems to contain files used for Android. Never went there.
- root/data/etc and root/data/system holds some system files. Don't mess!
- root/data/app/ is the main location for user installed apps (.apk)
-> root/data/data/ is the location for each apps' storage (like some sort of registry), like scores for games, etc
-> root/data/data/ seems to also be the place where the "hosts" file of android is located (The other ones across the file-system are usually empty ones)
- root/system/app/ is the main location for cooked (pre-installed) apps. Removal is at your own risk!
-> root/system holds the build.prop file, responsible for some of the phone behavior. This folder seems to be physically hosted in Android's [system.ext2] file, and is dependent of the chef providing it. You can configure alternate DNS in this file (BACKUP first).
Kernels' flavors (MichyPrima Kernel Thread)(Hastarin Kernel Thread)
- There are two branches : EVO and Nexus1. They mean different libraries, drivers and modules. Nexus1 is the most stable, but the least capable. EVO, although less stable, is the most able, and thus has been selected to be at the base of the NAND development.
- There are two data approaches : RMNET and PPP. Both have their pro's and con's: Speed(PPP) vs Stability(RMNET). (Learn more here)
- There are several kernel chefs, and several available tweaks for each branch.
- There are several capabilities, such as Overclocking or Not, etc. Usually, each Kernel chef delivers its Kernel with or without these additions. Find the one that suits you best.
To summarize / To Update Android :
- A downloaded "Build" provides a FULL working Android system, you need NOTHING ELSE
- A downloaded "Kernel" provides : An updated [Haret, initrd.gz, zImage] that you just "paste" over an existing Android "Build" and sometimes updated "Modules/Libraries" that you need to manually push
->Note : There seems to be a workaround, like a [root] folder, containing many sub-folders, that is placed in the [Android] folder. The files included in this [root] folder seems to be copied by Haret into the root/ folder of Android on boot. That is why, when you "update" an entire "build", chefs ask that you deleted everything on your [Android] folder, to ensure nothing from an old "build" or "Kernel" will be copied to the new "build" upon booting Haret.
->Note on updating "Builds" : I personally erase everything but the [data.img] on my android folder, then unzip the content of a new "build". WARNING : Some chefs include [data.img] in their "builds", so be sure to CHECK to avoid an override!
How to choose a build/a kernel:
- Check what are your needs : Sense implementation, Basic but blazing Android, HTC Sense.com services.... Each come with a price
- Again, choose what do you want from your phone, cutting-edge but unstable or basic but sure...(You may have both )
-> I personally don't recommend going out of binded paths. Each chef, in each build, uses a specific Kernel dev, and adapts its ROMS to it. I chose to only update a similar Kernel, when the cook or chef just didn't have the time to implement it yet (usually, unless Kernels are really faulty, new ones come with new builds, so just wait for a wholesome upgrade)
C. Basic Android Tools (Survival Starter Kit)Some tweaks will require "Super-User Access" or stuff like that. Again, here are the basics.
First, "Droid Explorer" (exe).
No, don't look on the market, it's a WINDOWS XP/7 PROGRAM.
(Why the capitals? For the story, a few months ago, it took me HOURS to figure that, as there is also a "Droid Explorer" on the market, free as well. When you're told, "Go into ADB mode with Droid explorer and push that file in the rootlib" you're starting to think you took the wrong spaceship )
-> ADB Mode : Short for "Android Debugger Mode". You can switch this in "Parameters/Application/Development, Check the USB Debug). You need to enable ADB mode to use Droid Explorer.
- Droid Explorer basics : If already on ADB, click on "Connect device" at the right corner, and select the only device shown.
- Warning : I've personally got increasing problems accessing/pushing files to Android using Droid Explorer. I'm currently using the "root folder update" method. (Handle with caution!)
Other useful programs (most are free, some very useful may not, and some are included in builds):
System Apps
- Root explorer (Apk) : A useful Android program, to access files currently not available trough ES Filexplorer or Astro, although some other file explorers may possibly retrieve SU privileges to access the entire file-system. "root/data" is a typical folder not accessible with "traditional" file explorers.
- Super-User (apk): It's an Android Program, provided with your build. It enables programs to access some privileged code/areas...(To investigate)
- Terminal Emulator (apk) : It's Android's cmd.exe, used to input commands like in DOS-Mode
Usually Bundled Apps
- Astro (apk): Beautiful File Explorer
- Drocap2 (apk): Screenshot app. Push start, and shake HARD
- DSP manager (apk): Manages that crackling speaker bad bass rendition
Must-have Apps
- Adfree (apk) : Similar to winhelp2002 for windows, this block some ads while on the Internet. Doesn't block GoogleAds (developers need to survive through free apps too!)
- BatteryLevel (apk): Inputs a permanent notification, which shows the battery percentage. Lightweight and useful, albeit not always properly refreshed
- DroidWall (apk): The only? firewall for Android. Need Busybox (cf TitaniumBackup) in order to function properly. Warning : May block genuine apps from accessing Internet. And no, your cracked apps won't be prevented from calling "home", as license verification goes through the Android system itself.
- GPS Status (apk) : Handles the A-GPS, compass and other stuff
- SetCPU (apk+widget) : This is used to tweak the CPU. (see Hastarin's recommendations, a shame I can't export my settings). Install the apk, then place a widget in order for it to work (mandatory? need to investigate...)
- Shazam (apk)
- SMS Popup (apk) : Great program, pops sms and enables quick management. SMS notifications have to be handled solely by either the program, or the system. Disable one or the other accordingly.
- Startup Cleaner Program (apk) : Manages starting programs. Handle with care.
- SwitchPro (apk+widget) : Almost similar to Cookie's switches for WM6. Can't live without. Weird implementation though.
- Taskiller (apk+widget) : Selective task killer. Has been reported to cause wake-up lag when set on "autokill on sleep" (and I do, but use it on other occasions)
- TeslaLED (apk) : Ke$ha's favorite tool for impromptu parties!
- CurrentWidget (widget) : report power consumption. Helps reporting battery drain problems (I got 3ma on standby ). Don't set to "update" on less than 1 minute. Use it to log when on sleep, then check power consumption on standby.
- DolphinBrowserHD (apk) : Very configurable, personal choice.
Very Nice Addition
- Swype (apk) : Provided on the forum, or sometimes implemented on Builds, can't live without either.
Is there a developer in the room?- Taintdroid (needs implementation/compiling?)
Unusual stuff coming from me, but this program recently came to my attention. It detects every ID/IMEI/etc Internet leakage and reports to the user. It visibly need some kind of integration into the kernel in order to work. With a firewalling program, we could prevent our phones from spying hard on us (I have a dream, i know ^^)
>>>Hastarin, MichyPrima, ElBartoMe and the others, anyone there? <<<
Thanks for all the devs, chefs and forum users, i'll link when available and when free
Complementary guides
This is post 2 :
Complementary guides
Complementary guides:
> How to flash an android build, and boot issues/solutions
http://forum.xda-developers.com/showthread.php?t=732380
>A good explanation of the different terms
http://forum.xda-developers.com/showthread.php?t=774859
>Frequently asked questions (although pretty much technical to me) (Tips and Apps)
http://forum.xda-developers.com/showpost.php?p=7088391&postcount=3
Main Problems, Concatenated Solutions, Original Threads
This is post 3 :
Main Problems, Concatenated Solutions, Original Threads (When available):
Main Problems and Solutions (compilation)Some filenames aren't correct, i'll check that later
(One general thread)
Battery Drain (One thread there) (Another Thread here)
May be the main problem out there, although Touchscreen freezes are competing for #1 as well
- Try tweaking WM6 power management (Thread here)
- Use CurrentWidget log mode to verify
- Remove root/data/system/batterystats.bin
- Try the Airplane mode in WM6. For daily Android users, set to airplane, then switch the phone off and on without a reboot app. The airplane mode should stay indefinitely on. For constant switchers, launch haret after airplane mode. On next reboot, WM6 shouldn't have airplane mode on.
- Try checking the "lightslib.q8sk"(?) file/problem. Try replacing it with the newer "lights.htcleo.so" provided on the forums
- Try flashing a different radio or WM ROM (test radio first of course)
- Try booting Haret with the keys' lights on
Robo Voice
This issue seems to be hardware+software related. AKA It is different for everybody, and same build+rom+kernel may produce different results on similar phones.
- Current state of resolution is : FLASH RADIO and CHANGE WM ROM ^^
PPP Stuttering (no Edge/HSPA icon warnings)
- Try the libhtc_ril_wrapper.so fix provided by noellenchris (Another thread there)
- Try updating your kernel
- Try removing Taskiller Autokill feature (not the kill on sleep feature)
PPP Freezes (icon going on and off, etc)
- Try tweaking the build.prop (GSM or WCDMA prefered via "ro.telephony.default_network=" parameter ) (See "Tweaks" Section)
- Try changing the DNS inside "root/system/build.prop" (Link of your mobile provider DNS here)
- Try tweaking the APN in "root/system/etc/apns-conf.xml"
Screen of Death (Thread)
As Robo Voice, this issue seems to be hardware+software related. AKA It is different for everybody, and same build+rom+kernel may produce different results on similar phones.(Proof)
- Try flashing a new radio
- Try formating your SD with the largest FAT32 Allocation Unit Size possible (Thread Here)
- Try changing your SD-Card
Touch-screen Freezes
- Try disabling g-sensor in Parameters/Display/Auto-rotation
- Try offset change. Still haven't understand... (Thread Here)
Music Stutter
- Try updating or Changing Kernel (Thread Here)
- Try this workaround
Background Noise
See this thread
Camera "Moon picture" Preview
- Temporary fix : Disable preview
Camera : HTC 5Mpx (EVO/Desire Roms ONLY) (No Desire HD, No Desire Z...)
See thread here
011 International Dialer issue
Fix can be found here
T-MO USA MMS Issues
Thread Here
Tweaks i'm aware of
Boost DATA Speed
-> Edit your "root/system/build.prop" and check for correct values (These ones seems "overboosted") -> (Thread Here)
- Here are the "HSPA network" values explanations (See here), these seems more moderate
Build.prop Configuration
ro.telephony.default_network=
-> "0" is WCDMA/UMTS Prefered, even when network is very low
-> "3" is GSM/WCDMA Auto Mode, switch 2G/3G according to highest network
How-To's
This is post 4 : How-To's
HOW TO REQUEST FOR HELP ON XDAAgain, personal point of view here, but there are a lot of "unsaid" things around there....
1. Nothing more annoying than a "noob" (and we've ALL been through there, but...) that didn't (at least) try looking for himself.
-> Use wisely the "Search on this thread" button. It's WORKING. Tip: If you're not on a specific thread, but rather in the Development of General sub-forum, tick the "Post" button to avoid going through entire threads for a single answer.
2. Do remember: you're not alone.
-> DON'T BE RUDE, BE POLITE, SAY HI, THANK PEOPLE, we all have to be patient. It's XDA Community. Plus, some threads are moving real fast, and may have flooded your question. Ask again, and just don't complain!
-> EDIT YOUR SIGNATURE. Insert your ROM, Radio, Phone model, etc etc etc. Most common answer to noob problems: "WHAT'S YOUR ROM"
->Try asking GOOD QUESTIONS, starting with (Hi!) "I've been looking for this, found this, understood this, but need help about that" (Thanks) and you'll see how people will be more inclined to answer ^^
Flash a WM6 ROM (compatible with Android)> Need-to-Know : HSPL, RUU, WM6 Roms
1. Install the HSPL
- A HSPL is needed in order to "flash" custom roms, as well as new radios, and then Android Builds. Most up-to-date HSPL is HSPL 3 (found here).
- Plug your WM6 phone to your computer using the USB cable provided on activesync mode (SDCard Flash method here)
- Launch the "Mobile Manager" in Vista/Seven, or wait for activesync in Windows XP, and establish a connection (Connection failure : Look here)
- Launch "HSPL3_PKG.exe", and follow the instructions
- Reboot phone
2. Download and Install a WM6 ROM
- Hint: Choose and download a recent WM6 rom (advices here)
-> Your phone needs its battery to be charged at a minimum of 50%, else flashing won't occur
- Again, plug your phone in USB-Activesync mode
- Unzip the archive, and launch "CustomRUU.exe" ("ruu_signed.nbh" is the WM6 rom file)
Flash a new Radio (under WM6 only)- Choose a recent radio, minimum required is 2.08, 2.12 recommended (radio thread here)
- Again, plug your phone in USB-Activesync mode
- Sometimes, only the radio (ruu_signed.nbh) is provided in zip files. "Pick" the "custom_ruu.ex"e of a WM6 ROM, and copy it in the unzipped radio folder, it'll work just as well.
- Launch and follow the instructions
Install Android on a SD Card
Update an Android Build (with a new build)
Update an Android Build (with a new kernel)
Yes, I did find this useful - Thank-you !
RedWave31 said:
A.Android itself
There are a few things you need to know on android on HD2.
>What an Android build (like mdeejay NextSense.zip) is made of :
- An Android for Windows Mobile emulator (HARET),
Click to expand...
Click to collapse
HaRET is not an emulator. It is a Linux bootloader.
A Really good guide, actually explains quite a lot about the filesystem that I wasn't aware of. Well written and a great idea.
msoler8785 said:
HaRET is not an emulator. It is a Linux bootloader.
Click to expand...
Click to collapse
Thanks, updated!
Feel free to submit ideas or whatever!
Wow, good idea on putting it all in one thread, few things, however:
As another poster suggested, haret is not an emulator (handheld reverse engineering tool)
As far as the filesystems: rootfs.img is the linux rootfile system, startup.txt are commandline arguments for the linux startup, system.ex2 is the root android filesystem, etc. So to avoid confusion, think of it this way: system.ex2 would be closer to the android "rom image", where as rootfs, startup.txt, ts-calibration, and initrd are for the linux kernel side, so you can boot up android. (Very oversimplified I know, just trying to help)
When you install a linux box, typically it's installed on more than one partition (keeping the /home directory on a seperate one is always good practice, and some people even keep /var on a seperate one for log files as well.) data.img and system.ex2 would be like different partitions of the android filesystem. When you buy a phone that isn't "rooted", it means you don't have access to the root file system, aka in this case, system.ex2.
*edit* oops you already saw the thing about the haret. Didn't notice.
You may also want to add that for where apps are located after install, /data/app is for user installed apps, /system/app are for pre-loaded apps that are installed with the system. If you wanted to remove any app that came with the system (like the amazonmp3, for example), you'd delete it out of there. (Delete files out of the system/app at your own risk, don't delete it if you don't know what it is)
Added HSPA Values and DNS and APN files location. Enjoy
This is a very nice guide. Has a lot of the necessary stuff that the other guides leave out.
Good job. Maybe I will just link folks to this guide in the future instead of directly answering them. (probably just do both though - I was pretty noob at one point)
Oh, and .apk = Android Package (android apps are .apk / android package file)
Added 5mpx Fix, hope the HD Roms will have camera too
- Try the Airplane mode in WM6. For daily Android users, set to airplane, then switch the phone off and on without a reboot app. The airplane mode should stay indefinitely on. For constant switchers, launch haret after airplane mode. On next reboot, WM6 shouldn't have airplane mode on.
Click to expand...
Click to collapse
For my phone, turning on Airplane mode in WM6. then booting into Android with Haret without restarting, then coming back to WM6...it is still in Airplane mode.
Great Job man...keep this thread up to date...We appreaciate your hardwork....thanks a lot...
Top work dude!
Spelled "through" wrong in the title
OCedHrt said:
For my phone, turning on Airplane mode in WM6. then booting into Android with Haret without restarting, then coming back to WM6...it is still in Airplane mode.
Click to expand...
Click to collapse
Damn I spent a lot of time trying to figure this one, as I'm not using WinMo anymore. Are you using Cookie HomeTab's switch? Or directly in the Com Manager?
>I remember using Cookie Switch didn't stay at next reboot
- BTW, maybe it has to do with your launcher, or even the rom
jetsetwilly said:
Top work dude!
Spelled "through" wrong in the title
Click to expand...
Click to collapse
LOL This is the "Walk-true-shame"
Thanks for reporting
Added "How to post a Good Question", personal joke of the day, but REAL INFO
A question and a few suggested tools-
First, where in the Android file structure are the logs stored?
Second, another way to access the phone from Windows, one I use for working on Linux systems-
1) install QuickSSHd from the market. It will open an SSH (secure) tunnel into the phone
2) Install on your windows system Winscp and Putty (both Windows XP and up applications and both free. Winscp allows you to transfer files to and from the phone and Putty gives you a root shell and your desktop/notebook keyboard.
While these tools are not real simple, if you have an understanding of basic Linux and get this far you can then log into the phone over your home WiFi network with full root access and get into a lot of trouble if you aren't careful. It also seems more stable than Droid explorer.
Excuse this potentially silly question...
How do you quit Android? I'm running the Runnymede/Rhyme/Bliss one and long holding power doesnt do anything.
Is it just a battery pull?
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
My Initial Post:
Just recently, I added build.prop tweaks and when I rebooted, I have got network problems. I am connected to wifi but there is "no connection". I tried deleting the ro.mod.version line, added the tweaks in airplane mode and even added the tweaks 4 spaces down the last line but to no avail. I am using Maclaw's ICS Rom, Beta 8, (Thank You). Luckily I had a backup build.prop.bak. Most people on the forums said that ICS build.props are not supposed to be edited... Anybody know the source of the problem? In advance, thank you.
A Day After:
I tried many solutions and this is the best and most tedious so far. It works for me. For every ONE line you add, reboot twice. So, I am now looking for a less tedious method.
Possible Solutions
Possible Solutions extracted from my first post:
- Add a line every two reboots
- Add the tweaks in airplane mode
- Remove the ro.mod.version line
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
Hey xda-developers,
It's me Gio, and I made a tutorial for you guys on how to get Android 5.0.2 on Samsung Galaxy Pocket Neo but then the correct way.
First of all, me or the developers that made this ROM and the developers who made the other stuff are not responsible for any damage, this is completely your choice if something screws up. I don't think that something will happen but you will never know what happens. And second, I would like to thank the developers (flex1911, MatheusAlves and the others who made the project).
Tutorial:
1. Make a backup of all your data that is laying in your device. Think for example about important text messages, contacts, photos, or something else.
2. Make sure that you will be able to restore that backup after. So put it in your microSD card or on the computer.
3. Download the new ROM from the link which you can locate below this tutorial.
4. Place it in your device and boot your device into TWRP or CWM. Personally I find TWRP much more handy but your choice.
5. Wipe data, cache and dalvik.
6. Flash this ROM and if you have any other zip to flash (like a Dolby extension or Google Apps), do it after flashing this ROM.
7. Wipe cache and dalvik one more time to avoid errors.
8. Reboot your device and wait till you see the homescreen.
9. Download Wake Lock and install it on your device. (If you are going to install it from APK4Fun for example, you probably need to accept unknown sources from Security in Settings).
10. Open Wake Lock when it is installed and tick the PARTIAL~WAKE~LOCK. This is important to avoid numerous reboots, don't forget to enable it again after every reboot since it may dropout when your turn off your device.
11. Download keylayout.rar from the link which you can locate below this tutorial.
12. Unrar it, and copy the keylayout folder to your device.
13. On your device, open up the Files app.
14. Go to the hamburger menu left above and then go to the gear icon which is the settings.
15. Go to General and then scroll to advanced, and then tick on the first setting of advanced and change it to root modus.
16. SuperUser is going to ask you for permission, accept it.
17. Locate now your keylayout folder and then copy the whole folder.
18. Go back to the hamburger menu and you will see home with under it this symbol "/", tick it and go then to /system/ and then /usr/.
19. You will probably notice that there is already a folder named keylayout, just do nothing with it, you will now paste the folder you copied earlier just there and if it askes to merge and overwrite, just accept it.
20. When it is done, reboot your device and your home button will work again.
Download links:
1. ROM
-- ht tps://goo.gl/KnXXsP
2. Google Apps
-- ht tps://itvends.com/gapps/gapps-lp-20141212-signed.zip
3. keylayout.rar
-- ht tps://goo.gl/l04S6x
4. Wake Lock
-- Google Play -> search for Wake Lock PowerManger
-- ht tp://dl3.apk-dl.com/store/download/details?id=eu.thedarken.wl
What works?
- EGL
- Touchscreen
- RIL
- Internal Storage and microSDcard
- Sensors
- Bluetooth
- Wi-Fi
- Camera
- Hardware keys (after changing keylayout)
- Wi-Fi tethering
- Audio
What does not works?
- Microphone
- Mobile Data (2G and 3G)
- and some more stuff but did not across them
Thanks for reading and I hope that you are helped after reading this. Again, if you want to thank me, only do it for the cleared up tutorial, the people who made the ROM and the fixes are the ones who you should thank actually!
Whuuuuu
Thank you man !!
but this Rom is different from Flex rom !?
waiting for the stable version
we want to fix the sound recorder problem :'(
waiting for more success : الضحك:
Well, something it's something. Do you have can fix any other bug? Like the problem with theming or App2sd, you should also find a solution to those bugs.