Related
In the past several days, as there has been influx in Gingerbread users, I have seen an increase in traffic to one of my all time favorite guide to setup internet calling via Android phones using Google Voice #s and enjoy free calling throughout US with wi-fi as long the Google offer lasts. So I thought maybe I will create a new thread with the link to enable easy access to all the wandering souls looking for the information.
[While you are on the site, feel free to browse around and enjoy interesting ads (considered donation without you having to spend a dime for the help) ]
And here is the link: A Guide to Setup Internet Calling using Google Voice and Android Gingerbread
As was assumed, the same steps for the D3 from http://www.psouza4.com/Bionic/ worked very well to root the phone.
Also following the link on that page http://forum.xda-developers.com/showthread.php?t=1238472 Most of the bloatware is removable. A couple VCast apps remain, as well as the VZ navigator. I haven't taken a look at the script itself, but i'm sure it would be simple enough to add these new additions in.
Thanks a lot psouza4!
I'm rooted and I renamed a lot of bloatware until the SBF is released.
fenixjr said:
As was assumed, the same steps for the D3 from http://www.psouza4.com/Bionic/ worked very well to root the phone.
Also following the link on that page http://forum.xda-developers.com/showthread.php?t=1238472 Most of the bloatware is removable. A couple VCast apps remain, as well as the VZ navigator. I haven't taken a look at the script itself, but i'm sure it would be simple enough to add these new additions in.
Thanks a lot psouza4!
Click to expand...
Click to collapse
Check out this post over at androidcentral.com
http://forums.androidcentral.com/bionic-rooting-roms-hacks/117104-has-any-one-rooted-their-bionic-yet.html#post1227579
wynterend created a list of freezeable bloatware more specific to the bionic.
Worked great for me.
Sent from my DROID BIONIC using XDA App
HHmm.... a one click "root"??? Can someone please speak on this? Last time I tried a "one click" root it was on my Xoom and I almost bricked the damn thing. I was told after that nobody in their right mind uses a "one click" method.
jadkar said:
HHmm.... a one click "root"??? Can someone please speak on this? Last time I tried a "one click" root it was on my Xoom and I almost bricked the damn thing. I was told after that nobody in their right mind uses a "one click" method.
Click to expand...
Click to collapse
One click is easy. Follow the link in op.
Do not freeze Yahoo! Mail authenticator 2.3.4. Your contacts will fc on you. I don't even use yahoo.
I'm trying to use Pete's script with script manager to remove the bloatware but am having an issue. It click run but then it doesn't do anything. If i run the script without checking run with root it acts as it should and takes me through the prompts asking the questions. when I run it as run with root all I get is -
In mgmain JNI_OnLoad
exec sh '/mnt/sdcard/DROID_3_remove_bloat_5_6_890/DROID_3_remove_bloat_5_6_890. sh'
Happening to anyone else?
Anybody know what I'm doing wrong or why it's not working?
I am new at this.
Thank You,
Nick
rooted and bloatware frozen
Got my Bionic on Monday, rooted on Wednesday and used Bloat Freezer ($0.99) to freeze the following apps:
Android Live Wallpapers
Backup Assistant
Backup Assistant Client
Citrix Receiver
City ID
Device Setup
GoToMeeting
Guided Tours
Home Screen tips
Live Wallpaper Picker
Slacker
Social Location
Social Messaging
Social Networking
Social Status
V Cast Media Manager
V Cast Music
V Cast Tones
V Cast Videos
VideoSurf
VZ Navigator
I am coming from an Eris, so I am not able to determine if the device is faster or not and really don't care because the Eris was a dog even when rooted running Cyanogen and overclocked with SetCPU. What I am hoping for is increased battery and stability. The day after receiving the Bionic I lost all data services so I rebooted. Another Droid user at work said that it happens to him every once in a while (not on the Bionic, on whatever phone he is using) and he cycles airplane mode. But mine has been solid since rooting and freezing some of the bloatware. Will give it a couple days to see how my battery life is.
Update March 25, 2013:
Solved!! The folks over at Thinktube Inc. have developed a fix and submitted it to CyanogenMod and AOSP for merging into their code:
http://b-real.org/2013/ad-hoc-ibss-m...h-cyanogenmod/
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Essentially the EASIEST solution is to ROOT your phone, and install the CyanogenMod nightly as of March 25 or later (note: you will have to wait until the nightly is actually BUILT, since as of today it is not ready yet).
I have not tested this solution out myself, however others within this thread have confirmed it working.
Please if anyone develops a easier patch or a step-by-step for people who do NOT want to use CyanogenMod, post and I will update the OP
Cheers!
WiKiD24
-------------------------------------------------------
Update Oct 9, 2012:
- Nexus 7 v4.1.2 did not add Wi-Fi Ad-Hoc Support with the stock update from Google.
To do: Check if any WPA-Supplicant changes previously tested in v4.1.1 now work in 4.1.2
- Workaround (Recommended): Bluetooth Tethering to Nexus 7 Tablet (via Bluetooth DUN Profile). "BlueVPN" from Google Play Store.
Tested successfully on many Nokia Symbian phones (N7, E71, E72), and others.
However, many applications on Nexus 7 Tablet do not support it (without fixes from the developers)
Confirmed working applications:
- Pulse
- Google Chrome
- Dolphin Browser
- Facebook
- Ebuddy
- Youtube
- Others (I am too lazy to add them all)
Confirmed NOT working applications:
- Gmail
- Email
- Google Search
- Google Play Store
- Dropbox
- Words with Friends
- Scramble with Friends
- Others (I am too lazy to add them all)
More details can be found here: http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
Issue: Sometimes the phone/tablet do not connect (randomly), due to issues with either the phone or the tablet.
To resolve: Turn on and off bluetooth on phone, Turn on & off bluetooth on tablet. Try again. If does not work, reboot phone and tablet and try again. Should work.
-Workaround: Android Phone to Nexus 7 Tablet (via "FoxFI" App on Phone, "FoxFi Addon" App on Tablet, or via "PDANet", or via "Wireless Tether App")
http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
- Workaround: USB Tethering ANY Phone to Nexus 7 Tablet (via "PPP Widget" App on Tablet, requires rooted Nexus 7)
http://forum.xda-developers.com/showpost.php?p=32431103&postcount=51
- Workaround: Windows WiFi Laptop Tethering to Nexus 7 Tablet
http://www.youtube.com/watch?v=klHzMyYFGeQ
-------------------------------------------------------
Hi All,
I've just recently gotten a Nexus 7 and need to be able to enable Ad-Hoc wifi on the tablet.
I also own a Asus TF101 and previously had the same problem however there was a fix for that.
The solution was to replace the wpa_supplicant file in the /system/bin folder, however I do not know the code to change it.
If anyone has the technical know-how, they would be able to reverse-engineer it and apply the same fix.
http://forum.xda-developers.com/showthread.php?t=1370955
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/2752...less-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/gitw...upplicant.conf
I posted a possible solution in QnA section. Thread title is similar to this one. Check it out. Doesn't involve any coding. Prime had a similar issue on a few firmware updates. This was solved for us(before Asus came around to enabling it themselves) by adding in a wifi supplicant file and renaming an older one. Then setting permissions on the new file. Here is the link to that thread. There's a good chance it will work without the file needing to be modded. It came from a galaxy tab LR something and worked fine on prime. Its worth checking out.
http://forum.xda-developers.com/showthread.php?t=1438297
thanks for the tip and I tried it out, which is essentially the same type of solution but it didn't think work as there is no wpa_supplicant2 file in the nexus 7.
http://forum.xda-developers.com/showthread.php?t=1777413
here's some more useful information for enabling ad hoc:
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/27522-howto-connect-to-ad-hoc-wireless-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/git...ob_plain;f=wpa_supplicant/wpa_supplicant.conf
I'm doing what I can right now to try and enable it.
Some more experienced android users whom know what they're doing would be better than me trying it out, though!!
Did any of those sources of information get you any closer to enabling ad-hoc?
Just FYI that Nexus S "ad hoc enabling file" doesn't work on NS with Jelly Bean.
nexususer0101 said:
Did any of those sources of information get you any closer to enabling ad-hoc?
Click to expand...
Click to collapse
None yet, I need some help to do so. There is a file called "wpa_cli" that I need copied from another device, because I can't find it on the internet.
If anyone could find it in their "/system/bin" folder and attach it to this tread, I could certainly try it.
I've also requested the same thing in the Q&A forum here: http://forum.xda-developers.com/showthread.php?t=1793437
Bumping; I have the same condition. I'm in Italy and bought an internet package for my laptop--I'm sharing it with all my other devices but the N7 doesn't see the adhoc connection. Like OP said, I had a Transformer TF101 and remember flashing a file to fix it.
Thanks in advance.
Just an FYI: Also checked my GNex for a wpa_cli and came up empty.
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
One more "me too".
I'm here to share my sympathy to everyone else's pain as I have a nexus 7 that I can't connect to my phone's adhoc Hotspot. I have also posted my query in Android Central, but no one seems to have been able to know a fix as of yet. (topic can be found here: Android Forums at AndroidCentral.com > Google Nexus 7 Tablet Forum > Nexus 7 Rooting ROM's & Hack's > *** CONNECTING TO Adhoc WiFi WITH THE NEXUS 7 ***)
As I said in that thread.. not being able to connect to phones hotspot makes my beautiful nexus 7 feel like a handicapped tablet.
wikid24 said:
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
Click to expand...
Click to collapse
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. on prime we had this exact same problem. Then we found the supplicant file to replace one we had and then adhoc tethering worked after that. You only need to be rooted to do this as you need to rename a file and insert new supplicant in there and set permissions. You can always backup and rename original file. So if it doesn't work, you can easily revert back to stock file. I have a feeling this new file will work. Just haven't tried myself yet as I haven't brought tablet outdoors yet to need tethering. I might eventually see if it works if no one else does.
Look at the thread I linked in second post and you will see prime owners had exact same problem and we solved it. It worked for the transformer 300 also. Will likely work for nexus 7 also. The file is, in a sense, universal.
demandarin said:
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. .
Click to expand...
Click to collapse
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
rdelfin said:
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
Click to expand...
Click to collapse
They likely will implement it through a future update. Hopefully that's sooner than later. Ill ask motley, kernel developer.
I toyed with this for a while...
If you install Power Controls (Power Controls) you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Demented-Idiot said:
I toyed with this for a while...
If you install Power Controls you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Click to expand...
Click to collapse
Could you explain exactly what this does? I didn't understand what it is being implied with this being a start? with this you can actually connect to adhoc?
idk if anyone has looked...but has anyone looked into editing the Wifi-Direct api to make adhoc networks visible in there? Since wifi-direct is made for p2p connections. it's android.net.wifi.p2p.WifiP2pManager info about it is here http://developer.android.com/guide/topics/connectivity/wifip2p.html like I said...don't know if it's much help
I also wanted to post a quick reply, since I've been an insomniac yesterday.
From my previous posts I posted this link here as well, I edited the wpa_supplicant.conf file from the /system/etc/wifi folder and modified with the following settings, however I don't think that it even reads the wpa_supplicant.conf file either. Can anyone either confirm or deny that the wpa_supplicant.conf file is being used on the N7??
-------------------
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
ssid="Bondphone"
mode=1
frequency=2412
key_mgmt=NONE
wep_key0="1234567890123"
wep_key1=1234567890123
wep_tx_keyidx=1
priority=3
auth_alg=SHARED
}
------------------------
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
jenda.69 said:
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
Click to expand...
Click to collapse
jenda, I think you may have solved a big piece to the puzzle!!
You can copy the file to another directory, and THAN you can open the file! I noticed I had all my pre-saved wifi addresses in this file!
If someone can please copy the "/data/misc/wifi/wpa_supplicant.conf" file to another directory, modify it, than overwrite the old file, it should work!! *fingers crossed*
(unfortunately I am busy for a few days, don't know if I'll be able to make the change for a while)
I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
Linkies
Changelog
========
2013-07-20
--Added instructions for installing the platform tools on an arch host pc
--Added references to wicd and network manager as alternatives to netctl
2013-10-20
--Updated instructions to reflect new *-grouper.zip naming scheme for MultiROM files
--Added instructions for updating the kernel to include kexec
--Got bluetooth 90% working. Interface comes up and can find devices with scan. Can’t get it to pair yet though.
2013-10-24
--Got the bluetooth device to power up on boot by adding a udev rule. Unfortunately the bluetooth daemon seems to be failing as it starts.
2013-10-28
--My keyboard is pairing on boot now. Ugly ugly things to get it working, but it works.
2013-11-03
--Updated the guide to get X working.
2013-11-04
--Tweaked xorg.conf files to get kde and e17 working.
--Added instructions to get Touchégg working to provide more tablety experience
Todo/Bugs
Problems/Bugs/Todo
The following is a list of things that need to be addressed or that I want to address. These things will be tackled in no particular order but hopefully over time the number bugs and problems will go down relative to the number of features I want to add.
Feel free to comment with your own ideas or bug reports.
Fix slow shutdowns after enabling networking with netctl
Fix whatever extremely verbose crash shows up on shutdown after setting up bluetooth
Get bluetooth working without hacks and under bluez5
Get a graphical login working
On screen keyboard (especially at login screen)
Set up an aur and/or googlecode project to automate some of the scripting required to get things working
Automate the process with some kind of setup tool
Replace the google doc with a wiki page in a relevant place
Make a custom spin that works more out of the box
Sound
GPS
Accelerometer
Magnetometer
Hardware buttons
Any other sensors that I forgot or am unaware of
Auto screen rotation
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
Thanks for the feedback
I don't have arch on my pc at the moment, so it's not a given, but i think you are right that people are probably more likely to have arch if they are looking at this guide. I updated the guide with info on how to install the tools from AUR. Also added links to wicd and Network Manager in the arch wiki so people are aware of some options if they don't like netctl, and mentioned that e17 works.
Xorg with alarm on nexus 7
Okay, got ALarm installed on my nexus 7 8GB.
For Xorg, I used files from "plasma active" nexus 7 distribution.
Just take them from the plasma active and put them into your /etc/X11 and X should work.
(I can't post a link, must wait 10 posts, I'll link the files later or you can PM me)
My only problem now is to put a cross-compile toolchain on my computer to be able to compile e17 with illume modules. Tried to compile on my tablet but it's too slow and I've not enough disk free to finish. If anybody can help on this point…
What distribution are you using on your PC? Also you can pm me the link for the xorg configuration and I'll post it for you
OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?
thecrimsonfukr said:
OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?
Click to expand...
Click to collapse
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium
joeG78 said:
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.
thecrimsonfukr said:
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.
Click to expand...
Click to collapse
Hello
i want install arch linux on nexus 7 , but i confuse about it . is arch linux on nexus 7 fast and stable ?
can i watch hd video in arch linux withot lag ? before days i install ubuntu desktop on N7 but when i open video HD ( not full) with vlc , it somtimes play withot sound and it have lag . unity is heavy for nexus 7 , i want install arch + lxde . is it fater ?
sorry for english .
For me Arch works without any problems but when I type startx xserver freezes after the first image of xfce or e17.
Has anybody a solution?
? How to install e17 ?
joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
e17 is the fast
so , i want to installing to my nexus 7
thanks .
Why ? my bluetooth not work?
not find the device ????
ylixir said:
I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
My bluetooth not working
cannot find the device ??
Nexus 7 32GB Wifi
Click to expand...
Click to collapse
bluetooth
I have bluetooth (almost) working. I've put instructions in the guide. They aren't really a final solution, but maybe people who are running gui's can tell me if they work. I know I have the hardware working because I can see my keyboard when I scan for it, but I can't figure out how to get bluez5 to pair from the command line. Hopefully someone has better luck with a gui?
bluetooth
I've got Bluetooth working. I even have it pairing automatically on boot with a keyboard. Its an ugly solution but it works. The guide has been updated. I'll tackle X next
My Arch Install
Hey just wanted to add my install experience to the thread hopefully to help others. First of all I want say thanks for all documentation from the previous posters. I tried to follow the instructions as close as possible for a kde install, but I ran into some trouble with lightdm, so I tried kdm instead. And I can happily report it has worked swimmingly. Instructions on how to setup kdm, navigate to /usr/share/config/kdm. First edit the kdmrc to turn off the themed greeter. Then add the xvkbd to the XSetup file as in the lightdm setup. Another thing I did was utilize the plasmaboard widget on my main kde panel for my on screen keyboard once I log in. It seems to work much better than xvkbd for me. I can also confirm flash is working great.
So this really close to totally replacing my linux laptop, especially when I am on the go, in fact I am writing this post on the device in arch. However one key piece is still missing for me is sound. I can't seem to coax any sound out the device with my arch install, and amarok crashes on startup, even though both these items were working perfectly in ubuntu. If any one has any ideas how to make audio and amarok work I would be immensely grateful. Also thanks again, I am so happy to be rid of the X11 touch race condition. I have added a screenshot of me editing this post for those interested as well.
Figured out sound!
I think i found a solution to all of my troubles from my previous post. Amarok started working after a pacman update. My general audio problems seem to be caused by the linux for tegra audio drivers lack of head phone jack detection, I found a workaround the ubuntu nexus 7 launchpad bug tracker: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068804/comments/24. For the tldr crowd basically you have to use alsamixer manually mute and unmute the int_spkr channel for speaker audio and the int_mic channel to enable headphones. Then you can use the output and and hp to channels adjust volume for speaker and headphones respectively. It also might help to do a suspend resume cycle i sound still isn't working. Thanks to everyone else, hopefully others will find this useful as well.
Many thanks for your work!!! I'm using it on a nexus 7 with glass and touch broken (unuseless) but now it lives!!! and is a very responsive lxde desktop with xrdp starting on boot which I use with amule or bittorrent all night long...
two questions:
1) for me it does not work shutdown -r now or reboot... it close immediately all network connections but I have to keep power button 10 sec to restart system...
2) using it with an hub usb I'm trying to connect a big hard disk: pcmanfm (lxde file manager) refuse to mount it saying than it is not authorized... (I've followed archlinux wiki: it work on my archlinux desktop but not in nexus 7).
I just downgraded to 4.2.2 and i am try to get my tethering working for ny ps3. I tried barnacle (ps3 ddoesn see it ) i also tried the sqlite editor (didnt work even after i changed the number to 0) and a whole bunch of apps from the play store....any help would be appreaciated and im on d950 att unlocked with T-Mobile sim.
Nevermind i figured out what it was. I was editing the wrong thing in sqlite
I see you got it figured out already. And don't know what widget you're using but I use this one - https://play.google.com/store/apps/details?id=com.sharp_eu.ste.wifihotspot works great and looks good too. And I use a script that executes on boot through SManager.apk that changes the "tether dun required" to a "0" at boot up. Makes it hassle free.