Like many, I have CM installed on the Touchpad, with that frakking wifi problem plaguing me.
I don't mind redoing my connection every time I take the tablet; however where is the wifi settings "kept" in the file system? I need to delete the profile in order to redo the connection.
Can someone help? There are so many bazillion posts mentioning wifi that nothing of value can be found.
you can see the wifi settings in settings>wireless and networks>wifi settings and you can make your touchpad forget the connection settings by holding on the name of the connection and hitting forget on the pop up. after that you connect to your connection as if for the first time.
isanrap said:
you can see the wifi settings in settings>wireless and networks>wifi settings and you can make your touchpad forget the connection settings by holding on the name of the connection and hitting forget on the pop up. after that you connect to your connection as if for the first time.
Click to expand...
Click to collapse
Yep I tried doing that, and I have Force Close problems on the Wi-Fi menu, when the device does not connect. It's as if internally, there is a loop of something happening.
I thought somewhere in the filesystem bowels, there is a way to delete it "directly" without going via the UI. Thanks for trying to help, I appreciate it
Anyone knows if there is such a file somewhere?
i had this problem two days ago. i changed the channel of my router to 2 and restarted my touchpad into webos and back into android and made my touchpad to forget the network and reconnected it and i don't know what happened but that worked. wish i could be of more help to you, hope you get it working sooner so you could enjoy the android goodness.
don't where where it lives on the filesystem, but this app does it: market.android.com/details?id=com.brilliapps.wifiandmorefixer
http://forum.xda-developers.com/showpost.php?p=20963737&postcount=8
HOW DO I CLEAR OUT *ALL* MY WIFI SETTINGS AND START FRESH?
If you find that your wifi is "strobing" on and off, or you wish to completely wipe out all wifi settings, you can do this in one of three ways:
THE "RIGHT" WAY (USING ADB):
adb shell rm -rf /data/misc/wifi && reboot
(this will remove the settings and then force a reboot)
THE "I-DON'T HAVE ADB INSTALLED" WAY:
From the Terminal app.
# rm -rf /data/misc/wifi && reboot
(similar command as above. The # is a prompt-- don't type that part. If you see a $ prompt instead, type "su" (no quotes) and it should become a #)
Click to expand...
Click to collapse
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
speakxj7 said:
don't where where it lives on the filesystem, but this app does it: market.android.com/details?id=com.brilliapps.wifiandmorefixer
http://forum.xda-developers.com/showpost.php?p=20963737&postcount=8
Click to expand...
Click to collapse
Yesssssss. Thanks a lot, it works.
It's a (mini) chore each time to clear up everything, but at least it works.
Again, thanks.
speakxj7 said:
don't where where it lives on the filesystem, but this app does it: market.android.com/details?id=com.brilliapps.wifiandmorefixer
http://forum.xda-developers.com/showpost.php?p=20963737&postcount=8
Click to expand...
Click to collapse
b.huss2 said:
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
Click to expand...
Click to collapse
a benefit of the app i referenced is that no reboot (or worse) required.
speakxj7 said:
a benefit of the app i referenced is that no reboot (or worse) required.
Click to expand...
Click to collapse
true. I'm with ya, just throwing it out there. ADB would be the preferred method but for those that are not familiar with ADB, then an app would be easier, although i don't know if that app is doing the same thing as the ADB approach. if it is then win-win. if not, and problems still exsist, then ADB is an alternative approach.
b.huss2 said:
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
Click to expand...
Click to collapse
What is adb? I activated it in development options, but where do I get it?
deafasheck said:
What is adb? I activated it in development options, but where do I get it?
Click to expand...
Click to collapse
Why not do your own research? A quick Google search reveals:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
https://developer.android.com/studio/command-line/adb.html
Ask only when you really need it.
b.huss2 said:
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
Click to expand...
Click to collapse
Thanks, I got terminal and I typed in all the commands. Do I include the & & reboot in the code? Any spaces or straight type?
Related
Ever since I switched from JF 1.51 to rooted TMO 1.6, my SU app has been broken. It just hangs while staying black and eventually force closes. As you can imagine, this is a big hassle because I can't give any apps permission.
Does anyone have a solution? Thanks.
hettbeans said:
Ever since I switched from JF 1.51 to rooted TMO 1.6, my SU app has been broken. It just hangs while staying black and eventually force closes. As you can imagine, this is a big hassle because I can't give any apps permission.
Does anyone have a solution? Thanks.
Click to expand...
Click to collapse
Are you sure you didn't load the wrong rom and you lost root?
supremeteam256 said:
Are you sure you didn't load the wrong rom and you lost root?
Click to expand...
Click to collapse
Uhh, yeah. I have root, all the apps id already given permission to still work. Its new ones that do not.
Have you tried to push su back or run enable superuser to see if that will help?
supremeteam256 said:
Have you tried to push su back or run enable superuser to see if that will help?
Click to expand...
Click to collapse
I don't know what either of those means. If you could provide some instructions (terminal commands, etc) that would be great.
Thanks in advance.
Try this first.
Code:
turn on your phone by holding the home+end(power) key
press alt+x to enter the recovery console and then press enter when it asks you
next type:
mount data
rm /data/data/com.koushikdutta.superuser/databases/superuser.sqlite
if you have the problem where it says this file does not exist, type:
rm /data/data/koushikdutta.superuser/databases/superuser.sqlite
Alright, I will try that in a little while when I am at a computer. Thanks
hettbeans said:
Alright, I will try that in a little while when I am at a computer. Thanks
Click to expand...
Click to collapse
Also in the mean time you can try the superuser whitelist in the market to see if that will work.
Hey, formatting my SD card seems to have fixed it, but thanks for the help.
no problem
It used to prompt me to unlock with my google account.. now it lets me do it 5 times and reboots. Over and over.
Im kind of stuck.. I dont want to do a hard reset, theres messages in there I need..
redtxstar said:
It used to prompt me to unlock with my google account.. now it lets me do it 5 times and reboots. Over and over.
Im kind of stuck.. I dont want to do a hard reset, theres messages in there I need..
Click to expand...
Click to collapse
I'm not entirely sure, but maybe there's a way to ADB into the phone/Android Commander it and remove the lockscreen apk? Again, just tossing around ideas.
Open command prompt and enter the following:
Code:
adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
Now power off the phone, and turn it back on. Tada! No more pattern lock.
I added this to the Wiki just in case. But its not like anyone ever looks there.
regaw_leinad said:
Open command prompt and enter the following:
Code:
adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
Now power off the phone, and turn it back on. Tada! No more pattern lock.
Click to expand...
Click to collapse
So if someone finds/steals an android phone, that's all they would need to do to bypass the lockscreen?
t-wrench said:
So if someone finds/steals an android phone, that's all they would need to do to bypass the lockscreen?
Click to expand...
Click to collapse
exactly... kinda sad, but i'm guessing the average phone user knows nothing about sqlite lol but then again, it's posted here now thanks to me haha
regaw_leinad said:
exactly... kinda sad, but i'm guessing the average phone user knows nothing about sqlite lol but then again, it's posted here now thanks to me haha
Click to expand...
Click to collapse
Would this work on unrooted phones as well?
t-wrench said:
Would this work on unrooted phones as well?
Click to expand...
Click to collapse
hmmm, actually never tried.. I am actually not sure on this one.. someone want to try?
I think it will since it is located in /data which is R/W
unCoRrUpTeD said:
I think it will since it is located in /data which is R/W
Click to expand...
Click to collapse
well unless the system mounts /data/ as r/w, it's not... you can't do anything with /data/ in adb or any file explorer without root.
regaw_leinad said:
well unless the system mounts /data/ as r/w, it's not... you can't do anything with /data/ in adb or any file explorer without root.
Click to expand...
Click to collapse
That makes me feel a little better.
I will try this on an unrooted Samsung Moment and let you know. I thought that /data is r/w all the time.
Hi all,
trying to get my feet wet with some android hacking and thought getting my AR.Drone to work with my legend would be a good start. It requires connecting to the ad-hoc network created by the drone. The normal way is to edit /system/etc/wifi/tiwlan.ini as described e.g. here: projects.ardrone.org/boards/1/topics/show/1098 but /system doesn't seem writable even though I have root. I then found this app for the desire: code.google.com/p/desire-adhoc/ but the legend has a different wifi chip, so it didn't work. Attempting to reproduce what that app does I did
$ adb shell
# su -c 'insmod /system/lib/modules/tiwlan_drv.ko'
insmod: init_module '/system/lib/modules/tiwlan_drv.ko' failed (No such file or directory)
even though that file definitely exists. Am I missing something here, or is that part of the annoying restrictions still present even on the rooted legend? Ad-hoc wifi must be possible somehow, the wifi-tether guys managed to get it to work. Unfortunately their code is a bit over my head. Any pointers?
thanks
-felix
Do it from recovery mode. We don't have access to /system in normal usage of phone (you get used to it).
okay, I guess I have to learn how to bake my own update.zip.
still curious though, why am I getting "no such file or directory" if it's clearly there (and a similar method seems to work on the desire)?
I also tried this:
forum.xda-developers.com/showthread.php?t=754961&highlight=legend
Which is a quite cleverly hacked wpa_supplicant, but that resulted in no wifi at all any more, even though the patched supplicant is officially the same version. strange.
any clue how the wifi-tether guys do it?
No, those command work. Boot your phone to recovery mode, then mount the /system partition from the ClockworkMOD menu. then you can execute your commands, they should do it.
Also, questions like this shouldn't really be in the development section. Just so you know.
You got it all wrong guys... first you dont need to su -c as you already are root. Second... you need to load sdio.ko prior to tiwlan_drv.ko. And no we do not perform these in recovery mode
I thought he was editing files... Oh well, I'll read more carefully in future. Sorry guys.
EDIT:
Yeah, look:
The normal way is to edit /system/etc/wifi/tiwlan.ini as described e.g. here: projects.ardrone.org/boards/1/topics/show/1098 but /system doesn't seem writable even though I have root.
Click to expand...
Click to collapse
So he could edit from recovery mode. But, I was still an idiot, I said to do the insmod things from recovery. I am very sorry for wasting time here, I'll learn to read carefully and give proper answers.
Sorry
TheGrammarFreak said:
Also, questions like this shouldn't really be in the development section. Just so you know.
Click to expand...
Click to collapse
hmm, okay. I figured since I'm _trying_ to develop something...
well, next time.
BlaY0 said:
you need to load sdio.ko prior to tiwlan_drv.ko.
Click to expand...
Click to collapse
aaaahhh, that got me a bit further thanks! very confusing error message...
so module loading works now, but the phone just reboots a few seconds after I set
"iwconfig tiwlan0 mode ad-hoc"
any further advice?
Also I guess the confusion was my own fault since I rolled three different ways of doing one thing into the same post...
Oh man, I've said all the wrong things today. I'm so sorry. I'll just leave this thread now.
sanktnelson said:
so module loading works now, but the phone just reboots a few seconds after I set
"iwconfig tiwlan0 mode ad-hoc"
any further advice?
Click to expand...
Click to collapse
Yes. Loading modules just isn't enough in our case. You need to load firmware too before you bring interface up otherwise your system will reboot
Check Gratiend ROM thread or look into init.legend.rc for hints on firmware loading...
thanks. found this
/system/bin/tiwlan_loader \
-f /system/etc/wifi/Fw1273_CHIP.bin -e /proc/calibration \
-i /system/etc/wifi/tiwlan.ini
after googling init.legend.rc. doesn't seem to make a difference though. also tried using tiwlan.ini from the wifi tether guys, but no luck. device still reboots after setting ad-hoc mode. I guess I give up, there's no-one answering to my question on the wifi-tether google group either. i guess just because it's open source doesn't mean it's for the uninitiated...
Try sleep for 1 or 2 seconds after you load firmware, then bring interface up or start wpa_supplicant.
I you are using patched wpa_supplicant I guess you will have one more obstacle. It supports only wext aware devices and I guess our driver is not wext aware...
I solved the problem by installing Cyanogenmod (all other tries failed)
Sent from my Legend using Tapatalk
BlaY0 said:
Try sleep for 1 or 2 seconds after you load firmware, then bring interface up or start wpa_supplicant.
I you are using patched wpa_supplicant I guess you will have one more obstacle. It supports only wext aware devices and I guess our driver is not wext aware...
Click to expand...
Click to collapse
I enter the commands by hand, so there's already a delay in between. And I'm doing this by hand precisely because the patched supplicant didn't work on the legend. I guess now I know why. Thanks for all the advice though.
exicar said:
I solved the problem by installing Cyanogenmod (all other tries failed)
Sent from my Legend using Tapatalk
Click to expand...
Click to collapse
I had a CM6 nightly installed and toyed around with it a bit, but I actually use my FM radio (I know, barely anyone else does...) so I need to use a HTC ROM. liked the CM6 in a lot of other respects though. still out of the question for now.
Also I would eventually like to contribute whatever comes out of this to a proper AR.drone app that requires root and nothing else.
Enable USB Debugging and Run the batch file from the attached and follow onscreen Instructions.
75 downloads - no confirmation - files removed.
Doesn't seem to want to temp root my phone. Tried with and without restart numerous times. The phone is rooted, and adb is installed correctly (or at the very least it's always done what I've wanted it to) but the batch times out when checking for temporary root every time. Oh well it was worth a shot.
I think "usb debugging" is not enabled on your phone.
Go to settings, applications, developement and enable usb debugging.
i'm with Canadian Mobilicity ... i am using Bionix V (official Froyo) and its giving me almost instantaneous GPS fix...
Axura worked as well... but this one is damn fast....
What are the commands from the terminal?
This sound good.
Do I install via cwm?
Sent from my SGH-T959 using XDA App
a1jatt said:
I think "usb debugging" is not enabled on your phone.
Go to settings, applications, developement and enable usb debugging.
Click to expand...
Click to collapse
No, USB debugging definitely was on. I always make sure it is. Otherwise straight ADB wouldn't work properly like I mentioned it always has for me
Besides, it tells you in the notifications bar if it's on whenever you plug in, and it's definitely on.
Maybe later I'll open up the batch and try the commands by hand from ADB.
hussarfilms said:
This sound good.
Do I install via cwm?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No, just double click on the install file.
Deathsnapper said:
No, USB debugging definitely was on. I always make sure it is. Otherwise straight ADB wouldn't work properly like I mentioned it always has for me
Besides, it tells you in the notifications bar if it's on whenever you plug in, and it's definitely on.
Maybe later I'll open up the batch and try the commands by hand from ADB.
Click to expand...
Click to collapse
Maybe,
it gave me same error only when i had it disabled.
a1jatt said:
Maybe,
it gave me same error only when i had it disabled.
Click to expand...
Click to collapse
Going through and doing it by hand. Pushing the files now. The line:
"%adb% -d push %gps% /system/etc"
makes total sense, in that it's pushing the gps.conf file to the folder /system/etc
but the lines following it:
"%adb% -d push %f1% /system/csc/WND/system/CSCFiles.txt"
and so on, they seem to be trying to push the txt file to a txt file already on the device. The shell tells me that "/system/csc/WND/system/CSCFiles.txt" isn't a valid file or directory.
There don't seem to be any lines that make directories /system/csc/WND/system/{files}
Should I assume that's still the intended destination and not an error? Go ahead and put some mkdir lines into busy box?
EDIT: DONE. It rebooted, installed packages, etc. Formatted data and cache when it did, so booting was like first boot (took a while, showed the general 'new rom' screens, etc.) Checking GPS now/soon.
Does it work on Mobilicity?
good work！
It should fix gps on mobilicity, i will add apn settings for mobilicity later.
On mobili u dont have to do *#06# or *#272 , just run the file and reboot.
giving me an error too
Just wanna be clear
I run the prog
Let it do its thing- exit
Then reboot?
Sent from my SGH-T959 using XDA App
How do you get it to work for tmobile in usa?
Sent from my SGH-T959 using Tapatalk
sorry but what does this do? I'm on wind mobile
I'm also using a T-Mobile Galaxy Vibrant on the Wind Mobile network.. in Vancouver.
Does this simply change the settings to use something other than supl.google.com?
it doesnt work gives me an error
I'm going to hold off on this until the errors have been addressed.. seems like there is a bug in the script (maybe).
So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?
Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse
alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again
laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...
I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).
Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.
Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX