nvram wifiaddr=XX:XX:XX:XX:XX:XX
This is the method I used on my i5 ios6 to change my wifiaddr. Everything was smooth.
As this solution is permanent, I would like to know if there a way to revert to the original wifiaddr?
I have tried using the same method as above for recovery. However my wifiaddr is stucked with "XX:XX:XX:00:00" and it did not change to the original wifiaddr as desired no matter how many times I tried with the original address.
I have did a little research and found out that using 'nvram -d wifiaddr' may help.
Currently my phone is not jailbroken now so I have no way to test it out.
Would be helpful if anyone could enlighten me with this issue
If you execute 'nvram -help' in terminal you will see this
-d delete the named variable
I just did it myself and it worked. Original Wi-Fi MAC was restored. Although, I did it on my old iPhone 2G. Don't want to try anything like this on iPhone 5.
Related
This question might be trivial, unfortunately I haven't found the answer I was looking for.
I used dpct migration tool to port some cuda code to Intel DPC++ and then I further optimized everything I needed and eventually got rid of everything related to dpct expect the super handy
dpct::get_current_device();
which basically solves all the previous pain I had to put compile options to select the appropriate device and control them with Makefiles and so on.
Is there any way to do this without using dpct ?
I had a look at how dpct does this (here) but it looks pretty non-straightforward and it relies on other internal functions.
Is there any way to avoid this ?
I'm not totally clear from your question whether you want to 1) grab a handle to your device or 2) select a device on which to run stuff, so I'll try to answer both. Note that dpct::get_current_device() isn't actually selecting a device, it's just returning the device which you have already selected earlier in your program.
Typically when using SYCL we start with a sycl::queue, which we use to submit kernels, memory copy operations etc. From a sycl::queue you can access your device with:
sycl::device d = q.get_device();
But it seems like you may instead be asking for the simplest way to select a device. In this case, the simplest approach is to construct your queue with one of SYCL's provided device selectors:
sycl::queue q{sycl::gpu_selector()};
sycl::queue q{sycl::cpu_selector()};
sycl::queue q{sycl::default_selector()};
Note that the last option (sycl::default_selector()) is probably what dpct is currently doing for you.
at first: I'm not a BLE expert so I try to describe my problem as good as I can and I apologize in advance if I don't use the right terms or definitions.
I've bought a BLE-Energy-Harvesting button of type PTM 215B (1).
I've installed node-red on Raspberry-Pi 2b (2)
Locally on node-red the package node-red-contrib-generic-ble was install with npm (3)
when node-red is started I can see the elements of generic-ble-package and so I tried to configure the "Generic Ble In"-Item.
When I scan for devices, I have to push and release the button several times till it is shown in the list - that's no wonder because without these actions the button has no energy.
But then it gets complicated. When I click on "Apply", the item tries to get the GATT(ributes) from the button.The problem is - as far as I understood - the button doesn't have any.
From the CLI I've used bluetoothctl to scan for devices and I've seen that the button is always recognized by the system (on-button-pressed and on-button-released).
I've also tried with different other node-red packaged but they had even more problems ( e.g. noble (4) could not be installed properly and it looks like abandoned )
I assume the problem is sitting in front of the screen but this is the second Saturday I'm trying to "install a button" and I really don't know how to proceed.
I've read (somewhere) that one of the strength of BLE is the possible usage of energy-harvesting -sensors. But does the "general-ble"-package do the job?
-If yes, how?
-If no, which package should I use?
I'd really like to use a node-red-package because I want to expand an already existing flow.
I appreciate any help and/or link.
Thank you in advance.
Regards,
Mr P
Additional info:
Raspbian: VERSION="10 (buster)"
npm --version: 6.14.8
node-red: 1.2.6: Maintenance Release
Ref.
(1) https://www.enocean.com/en/products/enocean_modules_24ghz_ble/ptm-215b/
(2) https://nodered.org/docs/getting-started/raspberrypi
(3) https://flows.nodered.org/node/node-red-contrib-generic-ble
(4) https://flows.nodered.org/node/node-red-contrib-noble
I found the way to do the job:
I installed the ble-beacon-scanner (1) and that works fine for my purpose.
As I understood: Beacons use ble-notifications, which don't share attributes and don't need a continuous connectivity.
The generic library unfortunately doesn't offer this part of the ble-protocol.
Thank you all.
Regards,
Mr P
(1) https://flows.nodered.org/node/node-red-contrib-blebeacon-scanner
I am trying to really diagnose an awful battery consumption issue with my jailbroken iOS device and I believe a random spike in CPUis causing this. Is there a way to chart/graph out the output from top -u in MobileTerminal so I can analyze to see if anything is causing that spike?
Appreciate the input here or if anyone has another tool. I have used iCleaner Pro to disable tweaks as well as run a semi-restore. I would like to be able to troubleshoot this without loosing my jailbreak.
Thanks!
Folks,
Environment: Ubuntu 12.04 minimal + openbox.
In our C-based application, the information can be displayed only on approved display devices. We rely on EDID to get the information for the connected display device.
Everything works as expected. However, occasionally EDID returns us some garbled characters. For example, SAMSUNG may come out as SAMSyNG.
The programming logic to obtain EDID information is straightforward. It makes me feel that EDID itself is not as reliable. I am wondering if anyone else has faced such a problem and what you have done programmatically to overcome the problem.
Thank you in advance for sharing your thoughts.
Regards,Peter
Im new to this forum so be nice ;) i have followed rules :)
I am helping the dev for my kernel that I use. Since the mod I want is mainly only for me i figured its my duty to get it working myself.
The problem:
I have edited my *.kl files to disable the five front facing hardware buttons from waking the device and only allow the volume up / down buttons to wake the device as the front facing buttons get pressed when its in my pocket.
However, even though the front facing buttons no longer turn on the device , when they get pressed they light up adding an extra 6mA drain .
What I've tried:
I wrote an apk to change the permissions of the /sys/class/leds/button-backlight/brightness file to keep them off. Despite the program working , permissions allow the file be edited, causing them to light up.
What i need help on:
I downloaded my dev's kernel using git and I want to edit the kernel myself to keep the button lights off during sleep . However kernel code is not my comfort zone .. so i need help .
Thanks everyone for helping and simply just reading !
1) Messing with code is a bad idea (especially if you lack skill and don't know C and UNIX).
2) what you are probably looking for is script that will run on startup (initrc) and there you need to set it and change permissions using chmod command.
Thus you need to Setup what you want (with echo command presumably) -> change permissions so file can not be rewritten (chmod) -> put two commands in initrc.
Kernel can be like any other configured using make menuconfig and then compiling it, in that case you just disable stuff that you don't like.
[OT] I may be off though, your (original) question (there was no question mark) did not make too much sense here and there. Read this howto: How To Ask Questions The Smart Way from Eric Steven Raymond. Thanks.