Related
Hi folks,
can i change the device name of my HTC Hero anyhow, so that in my router's overview it shows the name of it, like it does with laptops / PCs?
I know its possible with bluetooth, but i havent found any option for doing that concerning WLAN.
I didnt root my device, otherwise i would have probably tried the commands which i would use for my Ubuntu laptop:
sudo echo "newname" > /etc/hostname
sudo hostname -F /etc/hostname
and edit /etc/hosts accordingly.
Anyone knows a solution for me?
Best regards,
kapen
Please, anyone?
Or could anyone, who has a rooted Hero, go and take a look whether the files /etc/hostname, /etc/hosts and the command "hostname" exist? Or perhaps even write something in these files, i mean it wont do any harm as you are just writing sth to an ordinary text file.
If i'd have root, i'd do it myself, but for now there are no benefits for me which would push me to root and i don't want to lose my warranty for nothing.
Help is very much appreciated!
most routers let you do this on the router....
I know when i hook up to my thompson router and set a static IP address, it lets me name the device... Hardly worth hacking the device for really.
Bump
I'd like to be able to do this as well, without having to use a static IP. This can be done with symbian, winmobile, java and other types of phone not to mention internet tablets, laptops etc. Why not an Android phone?
rhedgehog said:
most routers let you do this on the router....
Click to expand...
Click to collapse
True. But most routers isnt my router, its not able to do that. And neither do i want to set a static IP on my Hero, because i'm using it with several other WLANs.
fair enough.
I just thought as there is no way that anyone seems to know of on the device, that it may be an alternative.
Ya your right.
I just thought anyone knew a solution for me. I mean its a system running on linux and i ought to be able change that kind of stuff... just don't know how :\
Heureka! It worked just the way i suggested
If you have a rooted device with busybox!, get that handy adb file and do:
Code:
1. adb root
2. adb remount
3. adb shell
3.1 cd /etc
3.2 echo "Hero" >> hostname
3.3 echo "127.0.0.1 Hero localhost.localdomain localhost" > hosts
3.4 echo "127.0.1.1 Hero" >> hosts
3.5 hostname -F /etc/hostname
Voila. Though, you'll get an error when you do "hostname" now, because something in busybox is wrongly linked against a library which doesnt allow resolving hostname by IP, but other devices (such as my router) will now display "Hero" as device name.
Side note: my only intend for doing this was, that my router WAG54G2 (Linksys by Cisco) didnt work correctly with my Hero, meaning i got a lot of connection aborts in WLAN and often could not reconnect afterwards. That seems to be solved now!
Edit:
With the method above, you''ll lose your Wlan name after reboot. You need to add a line to the init startup scripts to perform a "hostname -F /etc/hostname" on every boot. This can be done in the file /init.rc or, if you have the MoDaCo Rom, in /data/init.sh
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?
I wonder if you'd be able to use Orbot to be able to gain access to Youtube...
Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.
I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers
Greetings
I have a Nexus 7 (wifi only) with JB 4.2.1 and I'd like to know if there is any custom rom or kernel that supports ad hoc connections, I want to connect the N7 to joikuspot on my nokia 808.
BTW I already tried bluevpn and not all android apps supports it, and already got connectify-me on my desktop computer, I need to connect the N7 with my phone since I travel very often and not everywhere I can find wifi spots.
Thank you in advance
CARUPANBOW said:
Greetings
I have a Nexus 7 (wifi only) with JB 4.2.1 and I'd like to know if there is any custom rom or kernel that supports ad hoc connections, I want to connect the N7 to joikuspot on my nokia 808.
BTW I already tried bluevpn and not all android apps supports it, and already got connectify-me on my desktop computer, I need to connect the N7 with my phone since I travel very often and not everywhere I can find wifi spots.
Thank you in advance
Click to expand...
Click to collapse
Hello? anyone can help me out?
Ad Hoc for Nexus 7
First, being a noob I want to say thanks for all the great info provided on this forum. It's a big help to someone like me who's just learning.
CARUPANBOW,
I need this also. I’ve spent several hours searching for a solution and have found nothing. It’s already been discussed here http://forum.xda-developers.com/showthread.php?t=1787680&page=7 on XDA so maybe that why no one has responded. The links below are to other discussions about this, but so far I have not found a way to force my Nexus 7 to connect to an Ad Hoc network. I’m still hopeful.
http://www.thriveforums.org/forum/t...ment/15959-ad-hoc-patch-3-x-4-0-4-1-cm10.html
http://www.pcadvisor.co.uk/how-to/google-android/3372947/connect-android-phone-ad-hoc-network/
http://szym.net/2010/12/adhoc-wifi-in-android/
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1077704
Maybe someone that’s really experienced can use the information in the links and find a solution.
Thanks,
Ken
Thank you
emgo said:
First, being a noob I want to say thanks for all the great info provided on this forum. It's a big help to someone like me who's just learning.
CARUPANBOW,
I need this also. I’ve spent several hours searching for a solution and have found nothing. It’s already been discussed here http://forum.xda-developers.com/showthread.php?t=1787680&page=7 on XDA so maybe that why no one has responded. The links below are to other discussions about this, but so far I have not found a way to force my Nexus 7 to connect to an Ad Hoc network. I’m still hopeful.
http://www.thriveforums.org/forum/t...ment/15959-ad-hoc-patch-3-x-4-0-4-1-cm10.html
http://www.pcadvisor.co.uk/how-to/google-android/3372947/connect-android-phone-ad-hoc-network/
http://szym.net/2010/12/adhoc-wifi-in-android/
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1077704
Maybe someone that’s really experienced can use the information in the links and find a solution.
Thanks,
Ken
Click to expand...
Click to collapse
Thank you very much for answering my post, I'm a noob too and besides I felt ignored, I have to confess this is my first android device, and I have spent many hours too to figure out a solution.
I checked the post you mentioned, some of those websites too and also checked the android issues #82 and #35629 at code.google.com
So far i've been able to connect to my nokia 808 via joikuspot, but like in bluevpn some apps are not working, here is what I did:
1) I have the JB 4.2.1 rooted on my device
2) I downloaded this kernel and applied it https://github.com/monk-dot/SPAN/blob/master/kernels/ASUS%20Nexus%207/myupdate-nexus7.zip
3) Since the nexus stock rom doesn't include the wpa_cli command I found this one http://pic-e-bank.com/android/Droid/Kernels/Froyo/Slayher/slayher_wifi_fix.zip Extracted the file and copied it into the folder /system/bin (set permissions to 755).
4) Found this patched wpa_supplicant file from this post "[JB] wpa_supplicant for adhoc wifi networks" and copied it into the folder /system/bin (made a backup first of the original file and set the permissions of the new wpa_supplicant to 755).
5) With a terminal app (using adb also works) I followed this guide: http://www.olsr.org/?q=olsr_on_android to set up the ad hoc network to my nexus 7 manually.
And Eureka! I could connect my nexus to my nokia 808 hotspot, however I couldnt see any infrastructure networks anymore, the solution was to revert back to the original wpa_supplicant, so I'm thinking about making two command scripts to set up my ad hoc connection and revert it back whenever I need to connect to a different network (you can check this guide).
BTW, there are some custom roms that include the wpa_cli command, but I tried some of them and they didn't detect my hotspot until I replace the wpa_supplicant file with the patched one.
I'm no android expert but I think the problem with ad hoc connections is a kernel/wpa_supplicant issue, i guess at some point google decided to take out the support for IBSS networks, however the linux kernel still supports it, i really wish some expert could take a look into it.
I hope you find this info useful, but this is not a final solution and I'll still work into it whenever I can.
Ad Hoc for Nexus 7
CARUPANBOW said:
Thank you very much for answering my post, I'm a noob too and besides I felt ignored, I have to confess this is my first android device, and I have spent many hours too to figure out a solution.
I checked the post you mentioned, some of those websites too and also checked the android issues #82 and #35629 at code.google.com
So far i've been able to connect to my nokia 808 via joikuspot, but like in bluevpn some apps are not working, here is what I did:
1) I have the JB 4.2.1 rooted on my device
2) I downloaded this kernel and applied it https://github.com/monk-dot/SPAN/blob/master/kernels/ASUS%20Nexus%207/myupdate-nexus7.zip
3) Since the nexus stock rom doesn't include the wpa_cli command I found this one http://pic-e-bank.com/android/Droid/Kernels/Froyo/Slayher/slayher_wifi_fix.zip Extracted the file and copied it into the folder /system/bin (set permissions to 755).
4) Found this patched wpa_supplicant file from this post "[JB] wpa_supplicant for adhoc wifi networks" and copied it into the folder /system/bin (made a backup first of the original file and set the permissions of the new wpa_supplicant to 755).
5) With a terminal app (using adb also works) I followed this guide: http://www.olsr.org/?q=olsr_on_android to set up the ad hoc network to my nexus 7 manually.
And Eureka! I could connect my nexus to my nokia 808 hotspot, however I couldnt see any infrastructure networks anymore, the solution was to revert back to the original wpa_supplicant, so I'm thinking about making two command scripts to set up my ad hoc connection and revert it back whenever I need to connect to a different network (you can check this guide).
BTW, there are some custom roms that include the wpa_cli command, but I tried some of them and they didn't detect my hotspot until I replace the wpa_supplicant file with the patched one.
I'm no android expert but I think the problem with ad hoc connections is a kernel/wpa_supplicant issue, i guess at some point google decided to take out the support for IBSS networks, however the linux kernel still supports it, i really wish some expert could take a look into it.
I hope you find this info useful, but this is not a final solution and I'll still work into it whenever I can.
Click to expand...
Click to collapse
That’s great! At least you have provided something that works. It’ll take me some time to replicate what you did. I am going give it a try.
Thanks,
Ken
Thank you very much
Also I found out the networks settings are stored in /data/misc/wifi/wpa_supplicant.conf instead of /system/etc/wifi/wpa_supplicant.conf
reading this post Edit wpa_supplicant.conf instead of wpa_supplicant I managed to manually edit my ad hoc network settings, so the wpa_supplicant.conf would be like this
Code:
ap_scan = 2
network={
ssid="JOIKUSPOT"
scan_ssid=1
priority=10
mode=1
wep_key0="12345"
key_mgmt=NONE
}
And you have to give the ownership back to system.wifi using abd/terminal:
Code:
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
For now im trying some customs roms to see if they can detect the ad hoc network out of the box, but so far I can only do it by replacing the wpa_supplicant and flashing the custom kernel from my previous post.
I'll keep posting my findings and try some other custom kernels as well.
So far this is what I got
Hi
So far this is my method to get (partial) ad hoc support for my N7 (wifi):
1) Start by rooting your device (you can use the Nexus 7 Root Toolkit).
2) Install CWM Recovery so you can install custom kernels.
3) Download and install this kernel https://github.com/monk-dot/SPAN/blob/master/kernels/ASUS%20Nexus%207/myupdate-nexus7.zip
4) Download and copy this wpa_supplicant file http://forum.xda-developers.com/showthread.php?t=1806937 into the /system/bin folder, be sure to set your wifi connection off, make a backup of the original file and after copying the file check the permissions to be 755
5) Create a text file with the following commands:
Code:
wpa_cli -p/var/run/wpa_supplicant scan
wpa_cli -p/var/run/wpa_supplicant scan_results
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 2
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"JOIKUSPOT"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 scan_ssid 1
wpa_cli -p/var/run/wpa_supplicant set_network 0 frequency 2412
wpa_cli -p/var/run/wpa_supplicant set_network 0 mode 1
wpa_cli -p/var/run/wpa_supplicant set_network 0 group WEP40
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 '"12345"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key1 12345
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli -p/var/run/wpa_supplicant save_config
wpa_cli -p/var/run/wpa_supplicant reconfigure
wpa_cli -p/var/run/wpa_supplicant enable_network 0
wpa_cli -p/var/run/wpa_supplicant select_network 0
Replace JOIKUSPOT with the ssid of your ad hoc network and set your password on the wep_key0 and wep_key1 variables, if you are using an open network just delete this lines:
Code:
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 '"12345"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key1 12345
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
6) Save the file "adhoc.sh" (be sure to save it in UNIX format, you can use notepad++ for this) and copy it into your device (I saved my script in /sdcard).
7) Turn the wifi connection back on and with a terminal emulator/ADB run the scrit
Code:
#cd /sdcard
#sh adhoc.sh
And now we're done!
You can see in your wifi settings your ad hoc network connected. But there are some issues, I cant see other networks on the list, even when I try to search for new networks, I can browse the web but cant connect to the play store, and with BlueVPN you could browse the store but couldn't download apps, the wifi icon in the notification bar is also gray color, after searching the forums this could mean I cannot connect to google services, but I still receive gmail notifications.
Well, I'll have to research more, but at least I think we're in the right way, to me this is a kernel/wpa_supplicant issue, I really wish some expert could help us out, or else I'll have to get into kernel compiling, I have a little linux experience and its been a while I dont get my hands into programming, but I'm not giving up just yet.
P.S: After checking with the terminal emulator, I started the command wpa_cli and this is the output I got:
Code:
[email protected]:/ # wpa_cli
wpa_cli
wpa_cli v2.0-devel-4.2.1
Copyright (c) 2004-2012, Jouni Malinen <[email protected]> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Using interface 'wlan0'
Interactive mode
<3>Trying to associate with SSID 'JOIKUSPOT'
<3>Association request to the driver failed
>
There seems to be a driver problem, I'll take a look into it too as soon as I can.
BTW I found this wpa_supplicat / wpa_cli files from this post http://forum.xda-developers.com/showthread.php?t=1980021 since the stock rom doesnt come with the wpa_cli command, these files seem to be for ICS but I tried them on JB and they work too.
Just a quick heads up
I've updated my n7 to rootbox v2.0 (comes with JB 4.2.2) and now I cannot connect it to my hotspot with my previous method, after checking my /data/misc/wifi/wpa_supplicant.conf file now shows this line:
network={
ssid="JOIKUSPOT"
.
.
disabled=1
}
What the heck does this mean? seems to be that the more I update my tablet the harder is getting to connect it to my ad hoc network, this makes me think maybe google wants to erradicate ad hoc wifi support from the OS, to me this is dumbest thing I ever heard since this tablet is WIFI only, isn't supposed to support ANY wifi network it finds in order to work properly? other OS like iOS or Symbian does still support it. Just the fact that i cannot use my tablet the way I want it to is very disappointing, and now I face two options: 1) Downgrade the tablet and never let it update again. 2) Install ubuntu and never again install android.
Im very sorry to say this but this is my first android device and my experience with it is very unsatisfactory, sometimes I wish I could get a refund and try the iPad mini or wait for any decent windows rt tablet.
For now I think i'm going for my option 2, tomorrow ubuntu will release the tablet version of their OS for the nexus 7, ill check it out and ill tell you my experience with it.
Please, if someone knows any of the senior contributors/developers of this community, please make them notice this issue, its almost unbelievable that ad hoc support haven't been fixed from android since issue #82, the original linux kernel supports it, and then google stripped it out and nobody got a response about this in the forums/groups, I know this is not an easy task, cause the android SDK doesnt support it either, also that you have to add the IBSS driver into the kernel and patch the wpa_supplicant file to stop filtering ad hoc networks, I still dont know if many people have requested this feature why even the modding community for android havent come with a concrete solution for this, there are a lot of kernel modders out there and I could find only one kernel that would work for me. I have to say that the most frustrating part of this situation is the lack of answers from the forums, I know this post already reached 1000 views, this means there's people still looking for an answer like me.
I have been trying lots of things on my new nexus 7 running 4.2.2 to try and get ad hoc networking working.
I have tried all the wpa_supplicant files I can find and even tried patching and compiling (using modified patches from h t t p://szym.net/2010/12/adhoc-wifi-in-android/) my own with no luck.
There are some musings at h t t p://szym.net/2010/12/prospects-of-ad-hoc-wifi-in-android/ saying we may never got it
I'll keep trying different things as this is something I really want
finally!
I found this custom rom (cm10 - 4.2.2 based) that has full IBSS support:
http://b-real.org/2013/ad-hoc-ibss-mode-support-for-android-4-2-2-with-cyanogenmod/
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Here we provide information, patches and a few system images to support Ad-Hoc (IBSS) mode. We base our additions on CyanogenMod 10.1-M2 (Android 4.2.2 JDQ39).
Our goal is to bring the missing Ad-Hoc (IBSS) mode to Android, in a way that is completely integrated into the Android system API and user-interface. Users should be able to create and connect to Ad-Hoc networks from the standard user interface (Settings – WiFi) and Applications should have an API to configure their “own” Ad-Hoc network. We believe this will help people who need more capability than WiFi Direct and can extend diverse usages of Android mobile devices.
To achieve this, we have modified the WLAN driver “bcmdhd”, extended the Android framework, the public Android API and added the missing parts to the “Settings” application. At this moment only Nexus S, Galaxy Nexus and Nexus 7 devices are supported and tested, but the same kernel modifications can be made to a number of devices and the UI will automatically show Ad-Hoc mode options when the driver supports it.
We have submitted these changes to CyanogenMod and Google AOSP Gerrit and provide this page for further information.
Click to expand...
Click to collapse
I have tested it on my nexus 7 and it can detect my nokia hotspot (joikuspot) flawlessly
Downloaded and installed this last night and it works great. I can connect to my nokia 808 using ad-hoc wifi now from my nexus 7.
Today my Cyanogenmod made an automatic update to 10.1.0 RC1 and the ad hoc wifi works fine
Running CM 10.1.3, I can no longer connect the phone to my PC (Win 7, x64). There is no acknowledgement from either the phone or the PC that a data connection has been made (other than that it was charging). I used to be able to connect okay, but now it's not working.
Searching around, this is apparently a common issue with the S4. I've made various attempts at dealing with this, including re-installing the Samsung drivers, with no success. I don't even know if it's specific to CM, or the phone's hardware/firmware.
Has anyone found a solution for this problem?
Hope this works for u. I had an issue connecting my Galaxy S4 as well. Here's the solution I found.
Click the phone icon to access the dial pad and type *#0808#
A menu will appear once the last character is entered.
Choose : AP on upper section and for USB Setting choose MTP.
Reboot the device. Good luck.
Credits to sucah for this solution.
willieamm said:
Hope this works for u. I had an issue connecting my Galaxy S4 as well. Here's the solution I found.
Click the phone icon to access the dial pad and type *#0808#
A menu will appear once the last character is entered.
Choose : AP on upper section and for USB Setting choose MTP.
Reboot the device. Good luck.
Credits to sucah for this solution.
Click to expand...
Click to collapse
I can't get USSD codes to work. I get an error "Connection problem or invalid MMI code". Adding a comma at the end doesn't fix it. As soon as I can get past this problem, I'll give that solution a try. Thanks!
Haphim said:
Running CM 10.1.3, I can no longer connect the phone to my PC (Win 7, x64). There is no acknowledgement from either the phone or the PC that a data connection has been made (other than that it was charging). I used to be able to connect okay, but now it's not working.
Searching around, this is apparently a common issue with the S4. I've made various attempts at dealing with this, including re-installing the Samsung drivers, with no success. I don't even know if it's specific to CM, or the phone's hardware/firmware.
Has anyone found a solution for this problem?
Click to expand...
Click to collapse
My computer has USB 3.0 equipped with fast charge, ASUS. The app updated and screwed my usb connections to any chargeable device. I wound up having to remove the app and then reinstall the drivers. Don't know if that might be an issue with your computer but it's with a check.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I discovered that those USSD codes are Samsung specific, which means that they only work on the stock ROM. In CM, they are invalid.
Any other ideas?
hello all,
I have installed the GSI Rom crdroid and but also already tested with the ASOP Rom but I always have the same problem! My devices MAC address changes after each reboot, the Random MAC I have switched off but still the same! In a MAC app I have seen your current MAC 02:00:00:00:00, the device MAC changes at every reboot and also apps with which I can change the MAC do not work so really also all the descriptions with BusyBox do not work for me => does anyone have an idea?