Hello every body...
when I turn on the WI-FI the massage appear Unable to Scan Networks Then the wi-fi turns itself off.
Help me please guys...
i would suggest reflashing the stock firmware with ODIN. I had an issue like this on my Nexus One. Nothing helped. I had to fully wipe the phone and start over.
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
alsatea said:
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
Click to expand...
Click to collapse
Awesome! Many thanks for the tip! You've made my day! That file's gotta be deleted from time to time, as it can get quite clogged. (And when you think I could've re-flashed my phone as per the previous post...!)
I having the same problem as this. after i removed and re entered my wifi login. also i had been on holiday and logged into a few other wifi routers.
when i re entered my home wifi it just kept turning off and saying "unable to scan networks"
its a vodafone UK contract Galaxy S (if that makes any difference)
I tried to root my phone using
[PROGRAM] One Click Root/UnRoot I9000 (Eclair and Froyo) Mac and PC
it seemed to work . i had an extra app for changing a few settings. but i still couldn't find the wifi file i need to delete? Had it not been rooted properly?
I'd really like to fix this without having to do a master reset every time?
What are my options?
Could i take an image of the mobile and remove the file from the image? then restore the image. A bit crazy if routing is not a possibility?
Can anyone help?
Thank you, unable to scan networks solved
How did you solve it?
with master reset?
Latest update to DI07 fixed this issue for me
The update was DI07 for the Samsung Epic 4G, not the Vibrant.
llamaunix said:
This weekend's update to DI07 from DG27 has fixed my "Unable to scan" Wifi issues. Since a few days ago when I would turn on Wifi it would turn itself off after about 10-20 seconds. It would also show a message saying "unable to scan for networks".. Previously I read that a factory reset would fix this problem but I held out for the new update to be pushed to my phone today (9/19) and indeed it fixed my problem. After the update rebooted, my Wifi turned on with no problem and it showed my previously added networks as well.
Good luck!
Click to expand...
Click to collapse
Is this update for the galaxy S?
or is there going to be a similar update?
I haven't logged onto another WIFI since I had to reset the phone (apart from my home WIFI). so i don't have to go through setting it up again.
cheers for the extra info
quick update
I am backing up with titanium backup manger now (free)
so hopefully it will restore the wifi it goes wrong again
(the phone needs to be ROOTED for the Titanium backup to work)
I rooted my phone with
http://forum.xda-developers.com/showthread.php?t=742403
one click rooter ( i couldn't run the "Galaxy S I9000 One-Click Root" file. i ran "rootme" file for 2.1 android, the rootme2.2 is for 2.2 it says dont run both)
And have 'astro file manager'(Free) and can explore more of my phone by pressing the up button a few times.
in astro file manger I searched for the word 'wifi' and got about 3 results. So its probably one of these.
We'll it working for the moment but I'm posting the more info for anyone else.
(I still don't know which file to delete to reset the wifi though.) but the titanium backup should be able to restore the wifi settings
alsatea said:
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
Click to expand...
Click to collapse
hello alsatea,
I have the wifi problem as well, and my galaxy s is rooted by running rootme but I can't find the bcm_supp.conf file. How do I fix the problem without applying factory reset?
thanks
chanXda said:
hello alsatea,
I have the wifi problem as well, and my galaxy s is rooted by running rootme but I can't find the bcm_supp.conf file. How do I fix the problem without applying factory reset?
thanks
Click to expand...
Click to collapse
Hi,
You have first to open 'adb shell' and in the shell enter 'su' (you must allow superuser access on your phone).
Next execute 'rm /data/wifi/bcm_supp.conf' and finaly 'reboot'
Good luck,
Mark
CommanderTux said:
Hi,
You have first to open 'adb shell' and in the shell enter 'su' (you must allow superuser access on your phone).
Next execute 'rm /data/wifi/bcm_supp.conf' and finaly 'reboot'
Good luck,
Mark
Click to expand...
Click to collapse
THANK YOU SO MUCH.
I spent over an hour on the phone with AT&T and then with Samsung trying to resolve the "unable to scan networks" issue. Absolutely worthless.
I rooted my phone just to try this and avoid doing the factory reset, and it worked!
Now if only I knew how to avoid this in the future...
thanks this actually worked for my fascinate as well.. saved me some hassle!
I had the unable to scan networks problem on my Bell Canada Samsung Galaxy S Vibrant.
Have been attaching to static IP in my house using Wifi Static app. (great app, by the way. stores configurations for multiple static ips and then configures wifi and connects automatically when you're in range of one of them. no more manual fiddling with settings for every static IP)
But I guess this precipitated whatever happens to the "conf" file mentioned above.
Initially installed ES Strong file manager to see if I could see the contents of the /data folder. Showed up as empty. (apparently not a high enough level of access to see if there's anything in there)
So needed to go for "root" access.
Rooted my phone with One Click Root:
http://forum.xda-developers.com/showthread.php?t=742403
then installed the "Terminal Emulator" app from Android marketplace.
Ran the terminal emulator to get a command prompt. your soft keyboard should pop up. if not, hit the menu button on your phone and hit "toggle soft keyboard". Then typed in:
'su' and hit 'enter' (do not type quote marks)
to gain superuser access.
The superuser app will pop up to ask you if you want to grant superuser access to the terminal. hit 'yes' or 'ok' or whatever the right button is.
terminal responds with a '#' prompt.
Then I typed in:
'mv /data/wifi/bcm_supp.conf /data/wifi/bcm_supp.bak' and hit 'enter'
to rename the file.
I then typed 'exit' and hit 'enter' to get out of superuser and then I hit the phone's 'back' button to shut down the terminal.
And now my wifi works again!!
The terminal procedure could probably be put into a script.
Next time it happens, I'll just do the same.
Once Bell releases Froyo in Mid-dec, maybe this will be solved. But I'll probably hold off and watch the forums for a while before jumping to Froyo just in case it buggers up something else.
Good luck!
dietrite said:
Now if only I knew how to avoid this in the future...
Click to expand...
Click to collapse
android market
titanium backup
free version
paid is very fast
titanium backup
phone menu button
batch
backup all apps and user data (look for the highest number on the right)
it backs up everything
maybe set a schedule to back up
--
if wifi goes wrong
select backup restore tab
and restore wifi settings
--
xdacalfun said:
I had the unable to scan networks problem on my Bell Canada Samsung Galaxy S Vibrant.
Have been attaching to static IP in my house using Wifi Static app. (great app, by the way. stores configurations for multiple static ips and then configures wifi and connects automatically when you're in range of one of them. no more manual fiddling with settings for every static IP)
But I guess this precipitated whatever happens to the "conf" file mentioned above.
Initially installed ES Strong file manager to see if I could see the contents of the /data folder. Showed up as empty. (apparently not a high enough level of access to see if there's anything in there)
So needed to go for "root" access.
Rooted my phone with One Click Root:
http://forum.xda-developers.com/showthread.php?t=742403
then installed the "Terminal Emulator" app from Android marketplace.
Ran the terminal emulator to get a command prompt. your soft keyboard should pop up. if not, hit the menu button on your phone and hit "toggle soft keyboard". Then typed in:
'su' and hit 'enter' (do not type quote marks)
to gain superuser access.
The superuser app will pop up to ask you if you want to grant superuser access to the terminal. hit 'yes' or 'ok' or whatever the right button is.
terminal responds with a '#' prompt.
Then I typed in:
'mv /data/wifi/bcm_supp.conf /data/wifi/bcm_supp.bak' and hit 'enter'
to rename the file.
I then typed 'exit' and hit 'enter' to get out of superuser and then I hit the phone's 'back' button to shut down the terminal.
And now my wifi works again!!
The terminal procedure could probably be put into a script.
Next time it happens, I'll just do the same.
Once Bell releases Froyo in Mid-dec, maybe this will be solved. But I'll probably hold off and watch the forums for a while before jumping to Froyo just in case it buggers up something else.
Good luck!
Click to expand...
Click to collapse
Had the same problem. Then I was having problems getting Superuser to allow my ADB shell, so I followed the steps above with a terminal emulator and got my Wi-fi on my Captivate back. thx
xdacalfun said:
then installed the "Terminal Emulator" app from Android marketplace.
Ran the terminal emulator to get a command prompt. your soft keyboard should pop up. if not, hit the menu button on your phone and hit "toggle soft keyboard". Then typed in:
'su' and hit 'enter' (do not type quote marks)
to gain superuser access.
The superuser app will pop up to ask you if you want to grant superuser access to the terminal. hit 'yes' or 'ok' or whatever the right button is.
terminal responds with a '#' prompt.
Then I typed in:
'mv /data/wifi/bcm_supp.conf /data/wifi/bcm_supp.bak' and hit 'enter'
to rename the file.
I then typed 'exit' and hit 'enter' to get out of superuser and then I hit the phone's 'back' button to shut down the terminal.
And now my wifi works again!!
Click to expand...
Click to collapse
Beautiful, works great, and I can do this with out a PC, and much more simple. Very nice when you are traveling. Thanks for the tip.
alsatea said:
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
Click to expand...
Click to collapse
Thanks a lot alsatea. Deleting /data/wifi/bcm_supp.conf and rebooting resolved the problem and I got back wi-fi. All the networks remembered previously came back. Thanks mate.
Just in case anyone is reading this topic but is unable to find the bcm_supp.conf file, try this instead:
> adb shell
$ su
# cd /data/misc
# chown wifi.wifi wifi
Then try enabling the wifi again. It should work.
Related
I have an eris running Zen-EXP Rev 7. Up until a couple of weeks ago, everything was peachy keen, and SU was working fine. A few weeks ago I decided to try flashing a newer version of SU (the one found here on the xda forums), and made a Nand backup before doing so. After flashing the updated SU, it force closed on me any time I tried to open it, and programs were unable to gain root access. So I restored my Nand backup, but now I'm having a new issue.
Basically, SU (the restored old version) opens fine from the programs menu, and programs I have already granted SU access to (SetCPU, for instance) work just fine. However, any time a new program asks for SU access, SU hangs at a black screen, so I'm unable to give any new programs root access.
Is there an easy way to fix this, or am I going to have to totally wipe/reflash my phone? I tried updating SU in a variety of ways and reflashing the rom WITHOUT a wipe, but none of those attempts fixed the problem.
Thanks.
Did you wipe before restoring your nandroid? And you're positive you flashed the right SU? The one meant for froyo? They always release TWO SU's, one for froyo and one not.
I didn't read the entire first post but make sure you have usb debugging mode turned on... My SU was hanging last week until I rechecked that.
theEastonator said:
I have an eris running Zen-EXP Rev 7. Up until a couple of weeks ago, everything was peachy keen, and SU was working fine. A few weeks ago I decided to try flashing a newer version of SU (the one found here on the xda forums), and made a Nand backup before doing so. After flashing the updated SU, it force closed on me any time I tried to open it, and programs were unable to gain root access. So I restored my Nand backup, but now I'm having a new issue.
Basically, SU (the restored old version) opens fine from the programs menu, and programs I have already granted SU access to (SetCPU, for instance) work just fine. However, any time a new program asks for SU access, SU hangs at a black screen, so I'm unable to give any new programs root access.
Is there an easy way to fix this, or am I going to have to totally wipe/reflash my phone? I tried updating SU in a variety of ways and reflashing the rom WITHOUT a wipe, but none of those attempts fixed the problem.
Thanks.
Click to expand...
Click to collapse
Some versions and ROMs require you to do this before you use anything that needs SU:
Install Android SDK if you haven't already.
Plug in the phone to the computer with USB Debugging on.
Open up a command prompt and navigate to your tools folder.
C:\android-sdk-windows\tools> adb shell
#
# su
(type adb shell, press enter, then type su, and press enter).
Your phone should pop up with the REAL allow/deny screen, without it being all black. Just for the first time.
Hit allow always, and move on.
Then when you want to use Root Explorer or SetCPU or anything that needs root permission, you WON'T just get that hanging black screen. It'll work.
Some ROMs and versions of SuperUser (or maybe something in bin/xbin, I'm not sure?) require you to use the SDK to use ADB shell, to get SU permissions, before you let any other apps get it.
Strange, yes.
Hope that helps.
pkopalek said:
Open up a command prompt and navigate to your tools folder.
C:\android-sdk-windows\tools> adb shell
#
# su
(type adb shell, press enter, then type su, and press enter).
Click to expand...
Click to collapse
The command "adb shell" doesn't work at all for me. In PowerShell, it just hangs at "Running script/selection".
Can you help me?
WARNING: Make sure your battery is CHARGED before attempting!
Code:
adb pull /rom/devconf/BootCnt
echo -n -e "\x08\x00\x00\x00" > BootCnt
adb push .\BootCnt /rom/devconf/BootCnt
adb reboot
This will set the boot count to 8 and reboot your device sending it into Factory Reset mode. Once your factory reset is complete you can force shutdown (by holding power for 15 seconds). Then hold the "n" button and "Volume +" while powering the unit back on to reset your /data folder. After this is done its like you just pulled the nook out of the box for the first time.
Remove your SD Card and turn on your Nook Color, register your device and plug in the USB cord. Go DOWNLOAD the 1.0.1 update and save it to your "MYNOOKCOLOR" drive's root folder. Reboot your device should start to update your nook to 1.0.1!
Now that your Nook Color is on 1.0.1 firmware you want to root it with Auto-Nooter you can follow this thread to do so.
Enjoy
Updated my Script in the other thread for 1.0.1
rooted Update
I keep reading that a rooted nook will not update. However the other day i noticed a green n and today it is not there but my software version is 1.01 and my nook is rooted. Has this updated caused my nook not to be updated?
jjlxs215 said:
I keep reading that a rooted nook will not update. However the other day i noticed a green n and today it is not there but my software version is 1.01 and my nook is rooted. Has this updated caused my nook not to be updated?
Click to expand...
Click to collapse
If your software is 1.01 your good to go.
Awesome. Bricked (boot-loop) my device.
Will update, but use caution using this method.
I can't read, didn't do the data reset This method appears to work well.
Course it does
Hot damn you rule. I was just thinking I should do this.
What changed in 1.01? Is there a compelling reason to upgrade?
swapdotavi said:
Hot damn you rule. I was just thinking I should do this.
What changed in 1.01? Is there a compelling reason to upgrade?
Click to expand...
Click to collapse
At least twice as much unicorn as the previous release... some are reporting up to 3 times more...
Sent from my NookColor using XDA app
Something about Wifi and use of B&N Store. I dont use B&N Store. I also find Location service works better.
xboxexpert said:
Something about Wifi and use of B&N Store. I dont use B&N Store. I also find Location service works better.
Click to expand...
Click to collapse
Well, I've had some moderate wifi problems so maybe I'll give this a shot.
Thanks again.
I have adb set up on my computer from when I rooted my phone... but I'm not very familiar with it. How do I get it where it needs to be to do this script? Many thanks in advance.
Swypin' left and right on my Hero with 2.2 sense.
The file seems to be corrupted when I download.
I’ve done it downloaded it six times.
The title says it's for Windows. Is there a Mac version? Or can this be used on a Mac?
HELP
How did you fix the boot-loop? I've reset my NC a few times with no problems, and now I can't get it out of the loop!!
Any help would be great!!
Thank you!
Extra info... I tried this from nook devs, but I can't get access to it thru ssh:
" Sometimes an NC will get into a state where it attempts to reflash the factory roms over and over and over. This is usually due to a damaged BootCnt file.
So, to fix it:
* Put in a nooter disk. This will boot the NC to a black screen.
* On your PC you need to use an ssh program to access the Nook.
o On Linux or on a Mac, at a console, type
ssh [email protected]
o On windows you will need to use putty.exe. If you don't already have a copy of Putty, right click that link and save it in the same folder as your adb.exe. Now, navigate to that folder and open putty.exe. It does not need to be installed, it just runs.
+ In putty, in the host name field, type 192.168.2.2
+ In the menu on the left, under connection choose Data, and in the auto-login username type the word root
+ Press the open button.
You will now be in an ssh session connected to the nook running the nooter's operating system.
Now, we will fix the BootCnt file. Type into the ssh screen:
mount /dev/mmcblk1p2 /mnt
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
umount /mnt
* Power off the NC holding the button down for about 10 seconds
* Remove the nooter sd card.
The NC will boot, and will run the factory flash one more time.
After that the NC should boot normally."
*******I'm not a religious girl, but OH THANK YOU JESUS!!******* Ahaha!
Thanks anyways, I fixed it myself. For anyone else who has this problem, here's what I did...
Plugged nc into computer and did "adb devices" and saw it was recognizing it.
Typed this in: adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
My problem that caused it to loop in the first place is that "/rom/devconf/BootCnt" of the above commands is blacked out on the nook devs website by a picture with a black background, so it was almost invisible, so I didn't see it while copy/pasting.
Then when it turned off, I pressed the n (home), +, and power, and it reset itself to factory settings. Phew!!
Your welcome
wrong thread, apologies.
running vegan and i keep getting this message. I think my wife was using it and maybe the battery died? not sure. any thoughts?
thanks
I get this about every 2 weeks. I boot into clockwork, reset to defaults, then restore from backup.
sent from my g-tablet using tapatalk
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Steps
Posting the steps you took might be a little more helpful to anyone reading your thread.....
gpzjack said:
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Click to expand...
Click to collapse
Which data base?
Do you mean perform a clear cache/data?
or are you mentioning the contact database sync from gmail?
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Thank you so much, this worked for me!
gpzjack said:
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Click to expand...
Click to collapse
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
yup the contacts storage got corrupted -> most likely you created an empty contact in the contacts app by mistake. Someone should sticky this - i see one of these threads daily haha. Its a pretty common problem.
many time that error (fc) is due to a contact with blank first and last name as the contact database uses them as index. if you have blanks the probem will keep returning.
thanks for the tip - seems to have helped me out of the
...acore... problem
Mind you, I **Never** touched the contacts app in any
way whatsoever.
The corruption happened "spontaneously"
After playing (it is *only* suitable for play) with android
for a few weeks now, you know what, android is CRAP
Cant get to Manage Apps
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
cassycan said:
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
Click to expand...
Click to collapse
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Norm Minske said:
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
Click to expand...
Click to collapse
I was unable to see the folder described in other peoples solutions, your solution of clearing data through the settings application worked great for me on brilliant corners 1.3.1. Thanks.
simuloid said:
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Click to expand...
Click to collapse
i manage to get tru the issue on adb shell by installing usb deview, n my command bar alrdy shown my device no. after typing adb devices but aft adb shell, came $ and not #, is there any different?
okay i had mine miracle- ly and not realising it done, my force stop no longer appear after downloading the latest busybox apps.=)
Hi - I was getting the acore error too. but I went ahead & did an nvflash. The error is still popping up. Any ideas?
Hi,
When I go to gPlay on the Q and click on "Apps" I only get like 150,000 results available for download, only a small fraction of the total apps available. When I go there on my computer browser to try to download an app to the Q it says "This app is not compatible with this device" for 90% of the apps. So, no dice with either method.
I have been sideloading apps and most of them work just fine. So I want to get around this gPlay restriction on the Q so I can just download apps directly from gPlay rather than having to sideload them.
(I am fully aware that the reason why gPlay keeps track of which devices are compatible is to avoid more "broken" apps than necessary, but in the case of the Q their own system appears to be broken itself, so I want to get around it.)
So, I bought the Device Spoofer app for $1.50USD
https://play.google.com/store/apps/details?id=com.scheffsblend.devicespoof&hl=en
which, despite the reviews worked just fine for me on both the Nexus 7 and on Nexus Q. It changes your build.prop file to spoof Google Play into thinking you are a different device of your choosing. Note that, as it says in the instructions, you need to spoof the device using the app, reboot, go to gPlay, *download an app* (any app), and from then on gPlay will register your device as a different one.
That works for me -- I select for example "Galaxy Nexus", go thru the steps above, and voila, gPlay in my computer's browser has now replace "Nexus Q" with "Galaxy Nexus". Pretty cool.
HOWEVER, and I am now getting to the point, this doesn't allow me to download any more apps than I had access to before! It still says "This app is not compatible with this device ["Galaxy Nexus"]" for the same apps that were incompatible before. Browsing gPlay on the Q also doesn't yield any new opportunities for downloading apps.
I think what is happening is that even though the build.prop file is being changed, the Q is still reporting to gPlay that it doesn't have, for instance: GPS, phone functionality, etc etc, long list of items. And that means that any apps that require any one of those functionalities is "not compatible" (despite the fact that sideloading many of them means they work just fine).
So, my point is, does anyone know how to spoof gPlay so that the Q reports to gPlay that it has all of the bells and whistles? (GPS, phone functionality, etc etc)
Thanks
I downloaded all the .xml files from my Q's /system/etc/permissions folder and compared them to those downloaded from my Nexus 7. There are about half the number of files and indeed many things are not supported, no surprise.
Is it safe to just copy all the .xml files from my Nexus7 to my NexusQ? (plus a few .jar files that are linked to in the .xml files).
And perhaps then gPlay will show more apps?
OK sorry for multiple posts, but what the heck I just tried it. And can't see any more apps on gPlay. Tried downloading one that was visible as I thought it might only report its permissions at download-time, but nothing changed after the download. Drawing blanks here.
FIGURED IT OUT!
That's right folks, you can now download any app directly onto the Q! No sideloading, no adb.
Followed these instructions for a different device. Basically I was on the right track but needed to change the .xml's file permissions back to rw-r-r and then clear gPlay cache, reboot, etc, then it worked.
Pasting the steps from this page http://www.slatedroid.com/topic/34849-guide-to-fix-market-to-get-more-apps-compatible/ below, with the small modification that I got my .xml files from my Nexus 7, not from his/her link, and I only loaded the tablet_core_hardware.xml so far (I have not attempted loading on any of the Nexus 7's other .xmls but most of them don't seem useful). Thanks go out to bosondehiggs of slatedroid.com. I have made a note in square brackets at which point my Nexus Q gPlay started suddenly showing all apps.
A. Backup /system/etc/permissions (just take a copy with ES file explorer or root explorer.recommended just in case)
B. copy the xmlfiles files into /system/etc/permissions (android.hardware.location.gps.xml, android.hardware.location.xml, com.android.location.provider.xml, tablet_core_hardware.xml) agree to over write all of them
C. Make sure the file permission are rw-r-r (with ES file explorer, long tap then change properties on each file..to help you out all files in that directory need to be rw-r-r)
D. Go to settings->apps->all and tap Google Play Store
E. Click on Clear data
F. REBOOT tablet
market still not working
Go to settings->apps->all Go to “Google Play Store” again
‘Clear Cache’ if it lets you then ‘Force Stop’ — DO NOT Clear data
back and Go to “Google Services Framework”
‘Clear data’ then ‘Force Stop’
REBOOT your machine. [After rebooting, the Nexus Q worked with gPlay just fine!]
Then after reboot market is still not working.. then go into..
settings->apps->all google play store again open it but this time clear data if it lets you..
thats it exit open market up, login and you should now have full market access....Youtube...Facebook....
Click to expand...
Click to collapse
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
sonikot said:
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
Click to expand...
Click to collapse
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
Click to expand...
Click to collapse
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
davidnhutch said:
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
Click to expand...
Click to collapse
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
sonikot said:
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
Click to expand...
Click to collapse
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
UKROB86 said:
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
Click to expand...
Click to collapse
Sorry, I assume you have already followed the instructions by kornyone here to root and install a launcher:
http://forum.xda-developers.com/showthread.php?p=28484300
There are other ways of doing this too. Some folks have gotten CM9 working on it.
I just made this quick video which shows Trebuchet and the Google Play showing most apps available, near the middle of this video.
What Can You Do with the Nexus Q? : http://youtu.be/6rb4iQDBom0
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Click to expand...
Click to collapse
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
mrjaymillz said:
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
Click to expand...
Click to collapse
Sorry, I mean the keyboard page on my website: davidnhutch.com/nexusq, click on Keyboard > Special Keys.
Basically, the "menu" button on android is mapped to the same keycode as the "menu" button on Windows keyboards, which usually has an icon that looks like a drop-down menu with a pointer hovering over it. (http://en.wikipedia.org/wiki/Menu_key)
You also can do all this from the command line without ES File Explorer, I'm just trying to make it a bit more visual, plus, ES is useful.
I am very interested in what you described you are working on, as I am hoping to try the same thing when I get some time. Please post your results and steps!
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
Click to expand...
Click to collapse
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
xMemphisx said:
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
Click to expand...
Click to collapse
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
mrjaymillz said:
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
Click to expand...
Click to collapse
I didn't get a chance to play with it too much yesterday, I would imagine that if you install a 3rd party keyboard and set it to your primary input method it (might) work. I'm going to have a better chance to really look at the Q tonight here in a few hours, so I'll report back with what I can figure out.
[Edit]
I still have had no time to test this yet. The company I work for is at deadline with new software and we have been working 65+ hour weeks here recently, so my Q has just been sitting there. I'm still anxious to test it, but it might still be a few days before work slows back down and I can really get after it again.
mrjaymillz said:
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Click to expand...
Click to collapse
Hm, weird that two people have said the .xml file is not downloadable -- I tried today and yesterday and it was available both times. Maybe the hosting site was down or something. Anyway it looks like someone else offered the same .xml file at another link so we're all set. I'll leave the .xml file there for a year or so though.
Steps 6-15: Yes, enter everything as quoted. No extra "adb" or "su" or anything is needed, other than what I wrote there. Just follow one step at a time, typing each one and then hitting enter. Shouldn't need a command prompt code entry as it is already, just without the code tags and with extra double-quotation marks. Please let me know if there are any errors though.
As for your last paragraph, it seems there are two issues. 1) Not being able to open gPlay on the launcher. Can you please provide more info? What happens? Does it try to open then crash? Is the gPlay app missing? 2) Can't get a keyboard to show up on the screen. -- You will never have an on-screen keyboard on the Q. You need an external keyboard, plugged into the USB port. If you want mouse + keyboard simultaneously, you need a "unifying mouse and keyboard wireless receiver" -- just search amazon for that -- what it is is a mouse+keyboard with just one USB dongle that serves both.
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
300k said:
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You're right, you technically don't need Trebuchet. It just makes life easier than launching everything (e.g. gPlay) via "adb shell am start ..." commands from your computer.
Regarding Google updating to JB, perfectly possible. Possible that everything will be standard in the next Q hardware release. However the real questions are, why was this functionality not included in the first place? Why was the hardware so very limited by the software? And the bigger question, why was the public release of the first Nexus Q sales indefinitely postponed? Presumably they are coming out with something better than what they showed at IO. Whether it's much better or just marginally better remains to be seen.
The best app/function in the video is being able to use OnLive (3D streamed games) in my opinion. Now, OnLive is expensive and I did have a few problems with the keyboard mapping, the mouse not working while OnLive was playing, etc, but it works and shows the potential for streamed games. The Q doesn't have to be the core device either, presumably a tablet would work too. I just think they should have done the hardware differently and made an Xbox competitor (Xsphere?) instead of a competitor to precisely no-one.
On steps 8 and 9 I get
sh: cannot create /sdcard/permissionsbackup: Is a directory
I don't think that I am typing it in wrong and I have copied and pasted as well just in case...The directory is made correctly... Thanks for your help.
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.