is there any method exist, to run whatsapp on PC without bluestacks and YouWave?
Whatsapppc
Have you tried: whatsappforpcwindows.webstarts
Im a new user and I cannot type urls type in google whatsappforpcwindows webstarts and it will show up
Oops sorry this is with bluestacks my bet I red only the title
---------- Post added at 10:21 AM ---------- Previous post was at 10:11 AM ----------
but I've found another one for you this might work:
newsinitiative org - using whats app without bluestacks pc /type in google (sorry still don't have rights to type urls)/
Related
can someone test the wpa_supplicant provided (which is in system/bin) on galaxy player 5.0 (2.35) to see if any one work and can connect to adhoc View attachment wpa_supplicant.rarnetwork?
first, rename it to wpa_supplicant and test them one by one,thanks!
OK, I'll try it.
their is an app in the market called:
"WiFi Ad Hoc enabler" by AREND
I would try it, but I don't have a SGP rom, so if my wifi config was to get trashed, I'd be in trouble
when i find a rom for the SGP 4.0, I might try this, I've been wanting ADhoc for a while now.
The file wpa_supplicant3 works well on my YP G70 2.3.6. Now I can use ad hoc.
---------- Post added at 06:29 AM ---------- Previous post was at 06:22 AM ----------
Well, you can use a terminal to run each file, and you will see the version number. If there is a "ah" word after the number, it's an ad hoc supported file. Otherwise, you don't need to try it. Besides, you should run your system's orginal file to know the right version for your current system.
noisyfox said:
The file wpa_supplicant3 works well on my YP G70 2.3.6. Now I can use ad hoc.
---------- Post added at 06:29 AM ---------- Previous post was at 06:22 AM ----------
Well, you can use a terminal to run each file, and you will see the version number. If there is a "ah" word after the number, it's an ad hoc supported file. Otherwise, you don't need to try it. Besides, you should run your system's orginal file to know the right version for your current system.
Click to expand...
Click to collapse
How do I run them? I tried copying them to my SD then running with connect bot,
but it said "permission denied" so I tried "chmod +x" and it said bad mode
chmod 755,not +x, that's not original Linux.
I tried that too (see attachment)
What would happen if I was to copy wpa3 and it was the wrong version?
would my SGP still boot? I made a backup, so if it would not cause any serious harm I could just go ahead and try #3.
Of course it will boot. Wrong file only cause Wi-Fi connection failed or nothing. And I suggest copy the files into /system/bin and then run them.
---------- Post added at 09:16 AM ---------- Previous post was at 09:09 AM ----------
By the way, you don't need to reboot after replacing the file. You just need to turn off the WiFi and turn on it. If it works, you will find your adhoc connection point in the list. So you needn't be afraid of not booting.
#3 worked for me too
SGP 4.0.
Thaks a Lot
Congratulations~
I'm wondering whether G70 support wifi tethering and bluetooth DUN. I have a s60 with 3g.
sweet worked perfectly #3
Samsung Galaxy Player 5.0 U.S. Running CM7.2.0-RC0-venturi_usa-KANG Kernel Version 2.6.35.7-G70UEK18-CL56626
Compatibility is a GO!
anyone having issues with overclocking on v2.6? even when i use initcompostbootsh my phone wont oc
Mine is working fine at 1.8 GHz (11 in initcompostbootsh)
I'm running fine at 1.755 -- option 9
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
treIII said:
anyone having issues with overclocking on v2.6? even when i use initcompostbootsh my phone wont oc
Click to expand...
Click to collapse
Did you mount the partition as r/w and then open the file in text editor mode? I was moving too fast and forgot to open it in text editor mode the first time, which didn't save the changes. Did it a second time and chose text editor mode, life was good after the save and reboot.
Its been awhile since i played around with Android, but I cant seem to find the Developer section in settings to enable USB Debugging... Am i missing something???
Settings-about and press build number 7 times
Sent from my VS985 4G
---------- Post added at 06:24 PM ---------- Previous post was at 06:22 PM ----------
Settings about software Press building number 7
Sent from my VS985 4G
When I have USB debugging enable it doesn't seem to survive reboots. When I have USB debugging enabled and I reboot when the phone starts back up USB debugging is turned off. I noticed this behavior because TiBu warns me when USB debugging is disabled. Does anyone else experience this same thing or am I the only one?
I have the same problem. Not sure how to resolve it.
rp201 said:
Settings-about and press build number 7 times
Sent from my VS985 4G
---------- Post added at 06:24 PM ---------- Previous post was at 06:22 PM ----------
Settings about software Press building number 7
Sent from my VS985 4G
Click to expand...
Click to collapse
Thanks.... I always forget how to get to it.
Deuce, you are right ! I set it just now, rebooted, and it is cleared.
I don't think it resets ever on my Nexus5. Nope, just checked on my Nexus5, my Nexus4, and my Verizon MotoG prepaid. USB debugging stays set on them all after a reboot.
Got it, need root shell of course:<br />
<br />
- Remount /system in readwrite mode.<br />
- Add this to /system/build.prop: persist.service.adb.enable=1<br />
- Save, remount as read only.<br />
- Reboot.<br/>
Sent from my VS985 4G
---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------
Not mine. Search adb reboot for original thread. Worked for me.
Sent from my VS985 4G
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
I added the entry using Rom tool box and build.prop editor in it. Very easy
Sent from my VS985 4G
rp201 said:
Got it, need root shell of course:<br />
<br />
- Remount /system in readwrite mode.<br />
- Add this to /system/build.prop: persist.service.adb.enable=1<br />
- Save, remount as read only.<br />
- Reboot.<br/>
Sent from my VS985 4G
---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------
Not mine. Search adb reboot for original thread. Worked for me.
Sent from my VS985 4G
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
I added the entry using Rom tool box and build.prop editor in it. Very easy
Sent from my VS985 4G
Click to expand...
Click to collapse
The build.prop method didn't work for me. I used the script method found by @x86cpu here: http://forum.xda-developers.com/showthread.php?t=2820239
x86cpu said:
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:
#!/system/bin/sh
echo 1 > /data/property/persist.service.adb.enable
This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
Click to expand...
Click to collapse
Just jumping in because I'm confused. My g3 doesn't turn debugging off, but I need to goto Internet Connection to get it working. I know the older LGs had the same thing, any ideas why? That is usually reserved for qualcomm diag stuff.
natalic said:
Just jumping in because I'm confused. My g3 doesn't turn debugging off, but I need to goto Internet Connection to get it working. I know the older LGs had the same thing, any ideas why? That is usually reserved for qualcomm diag stuff.
Click to expand...
Click to collapse
I am on a replacement (refurbished) G3. On my first G3, I did not have an issue with the USB debugging surviving reboot...On the replacement i did. I just added the line in build prop editor in rom toolbox, and I am good to go...
edit Debugging is still turning off for me...not sure why...Thought it was fixed with the build prop tweak...Not so...at least on my G3
I don't know if it will help anyone, but I've restored my Verizon G3 back to stock three times now and used both IOROOT and Stump root to root it. When I used IOROOT, the USB debugging option does not reset after a reboot. I didn't have to touch the build.prop file at all.
I am attempting to compile AOSP code using the new WSL (Windows Subsystem for Linux) aka Bash on Ubuntu on Windows. I have successfully setup my build environment and sync'd AOSP code.
I am unable to get "make" to complete a build for even just a single app.
Here is a strace file. Make seems to hang when reading the file "build/core/clang/TARGET_arm.mk" (this file is initialized on line 1443 of the trace), although this file is successfully read several times prior to the hang.
Any ideas about what is causing make to hang? How can I dig deeper to find out what is causing make to hang?
Bump
up
up
Are you on the 14959 fast ring update ?
Sent from my iPhone 4s using Tapatalk I also own a g900v
---------- Post added at 07:47 PM ---------- Previous post was at 07:45 PM ----------
It is beta if it broken report to Microsoft
Sent from my iPhone 4s using Tapatalk I also own a g900v
Hello All,
I can't seem to find this setting on Android 10 in developer options on my Mate 20 Pro. Has anyone else managed to locate it?
Thanks in advance,
I think you find it in Quick Settings Panel
@pasil.pt thank you, that's dark mode, not override force-dark.
akirainblack said:
@pasil.pt thank you, that's dark mode, not override force-dark.
Click to expand...
Click to collapse
Oh, sorry...I did not understand well
i believe you can force dark mode thru ADB
---------- Post added at 07:23 PM ---------- Previous post was at 07:11 PM ----------
Try this ADB command:
adb shell settings put secure ui_night_mode 2