OK, I don't think this thread will get any attention, but I want to document it anyway. All this should work on other devices with qcom WiFi drivers.
TL;DR:
Grab iwpriv binary somewhere (i've got my here: https://github.com/kriswebdev/android_wireless_tools/tree/master/bin)
adb push iwpriv /data/local/tmp/
adb shell su -c chmod +x /data/local/tmp/iwpriv
Code:
#!/system/bin/sh
ip link set wlan0 down
sleep 1
echo 4 > /sys/module/wlan/parameters/con_mode
sleep 2
ip link set wlan0 up
/data/local/tmp/iwpriv wlan0 monitor 1
/data/local/tmp/iwpriv wlan0 MonitorModeConf 9 40 1 111 0
And enjoy your airodump output
NO PACKET INJECTION! (stubbed out in driver, removed previously?)
If you don't receive any packets, issue "/data/local/tmp/iwpriv wlan0 monitor 1" again.
How does this all work?
Some time ago I discovered these strings in wlan_hal_msg.h: (they appeared in google):
Code:
...
/* Monitor Mode */
WLAN_HAL_ENABLE_MONITOR_MODE_REQ = 302,
WLAN_HAL_ENABLE_MONITOR_MODE_RSP = 303,
WLAN_HAL_DISABLE_MONITOR_MODE_REQ = 304,
WLAN_HAL_DISABLE_MONITOR_MODE_RSP = 305,
...
Then I unscrambled some indirections:
WLAN_HAL_ENABLE_MONITOR_MODE_REQ to WDI_MON_START_REQ in WDI_2_HAL_REQ_TYPE
WDI_MON_START_REQ sent in WDI_ProcessMonStartReq <— actual message sents here!
Called from "Request Processing Array" in function WDI_MonStartReq
Wrapped in WDA_ProcessMonStartReq, which is called in WDA_McProcessMsg by message WDA_MON_START_REQ
Which message is posted by wlan_hdd_mon_postMsg if (MON_MODE_START == pMonCtx->state)
Which is called in __iw_setint_getnone with sub_cmd = WE_SET_MONITOR_STATE
Which is set by iw_priv cmd "monitor"
And then figured out that driver works in different modes:
(vos_types.h)
Code:
/// Concurrency role. These are generic IDs that identify the various roles
/// in the software system.
typedef enum
{ /*ON linux maintain 1-1 corespondence with device_mode_t in hdd*/
VOS_STA_MODE=0,
VOS_STA_SAP_MODE=1, //to support softAp mode . This is misleading. It means AP MODE only.
//The constant name has historical reason
VOS_P2P_CLIENT_MODE,
VOS_P2P_GO_MODE,
VOS_MONITOR_MODE,
VOS_FTM_MODE = 5,
VOS_IBSS_MODE,
VOS_P2P_DEVICE,
VOS_MAX_NO_OF_MODE
} tVOS_CON_MODE;
Mode can be changed by "con_mode" module parameter.
(idk why they reinvented the wheel and not used the default "iw dev wlan0 set mode monitor")
Combined all this and... got a kernel panic. You may get it too. Main reasons are:
- You have not disabled WiFi before changing the mode
- The sleep time after disabling interface is short
- Driver is old. Yes, you can get crashes on some kernels. If you are, flash AGNi.
After successful switching you'll get a working monitor (check this with tcpdump -i wlan0), but with ethernet packets instead of radiotap, so airodump will not work. Luckily, this giant crappy driver can work with radiotap, but you need to configure it. This is done by another iwpriv call:
MonitorModeConf: <channel> <bandwidth> <crccheck> <filter> <conversion_required>
Filter: 3 decimal numbers
least to most: management packets, control packets, data packets
Conversion: 1 - ARPHRD_ETHER (802.3 packets), 0 - ARPHRD_IEEE80211_RADIOTAP (802.11 packets)
(again don't know why they implemented these calls instead of default ioctl's for channel switch, etc. This makes airodump unable to switch channels)
As a result you may get something like on a screenshot
Happy sniffing!
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Crayvolt said:
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Click to expand...
Click to collapse
Thanks. I wanted to say that kenzo development is almost dead, we've lost official LOS and keep losing devs.... So it's most likely we'll not see working packet injection (cuz devs who know driver's internals better than me are left), and, possibly, a wrapper library implementing the default ioctl's (like channel switch) used in most programs.
i understand, hopefully we can have new devs. who will continue
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
you dont have permission to capture on that device sokect operation not permitted
aldhi said:
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
Click to expand...
Click to collapse
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
cerg2010cerg2010 said:
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
Click to expand...
Click to collapse
Can you ziping code and flashable instal on twrp?
Khimin said:
Can you ziping code and flashable instal on twrp?
Click to expand...
Click to collapse
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
cerg2010cerg2010 said:
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
Click to expand...
Click to collapse
Thx, im waiting
Khimin said:
Thx, im waiting
Click to expand...
Click to collapse
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Thx dude
thank you you are awsome +thumbsup
---------- Post added at 08:49 AM ---------- Previous post was at 08:03 AM ----------
filter expresion syntax error using command tcpdump -i wlan0
help please
---------- Post added at 09:05 AM ---------- Previous post was at 08:49 AM ----------
can you help me?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Is it safe to flash with magisk in note 5 pro ?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Perinban Parameshwaran said:
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Click to expand...
Click to collapse
Please understand that I don't have any "note 5 pro". You can send me logcat and I can try to identify the problem or ask your ROM developer to take a look (if it's not MIUI lol). Anyway, that's just scripts, so you can copy them to /data/local/tmp or /system/bin manually.
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Op_Flashpoint said:
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Click to expand...
Click to collapse
Sort of. It makes your sniffer to work - you will be able to capture raw WiFi packets from your device without any dongles.
plis whats rom u use ¿
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
thank you man, monitor mode now working on my poco F1, using its module magisk + aircrack-ng
Related
*I'm not updating it, but many users find this useful, so thread is kept as is for now*
Not sure if anyone got so far, to getting the honeycomb showing connection and selectable APN in settings?
anyways,
from my port of honeycomb to folio100, and now experiments with a500.. i got huawei dongle's running using the builtin functions.
you will need to have root'd your device. and this might break a system-update, if any of my files are updated during next OTA..
but back to the working 3G.
Working 3G USB dongles:
Do note, your modem version can be seen on its white label written with very small text.
some modems require zerocd (linuxtool) or commands executed in windows to disable the mass storage part of it. (search google for the commands)
* ZTE MF 639 (might need roaming enabled to get data working)
* Vodafone K3765-H
* Vodafone K3715
* Vodafone K3565 / Huawei E160
* Huawei E169
* Huawai E170
* Huawai E171
* Huawei E173
* Huawei E1550
* Huawei E1692
* Huawei E1750
* Huawei E1752
* Huawei E1820
* HUAWEI K3520
* HUAWEI K3565 -Rev 2
Download View attachment 3g-usb-stock1.zip for 3.0.1 stock release Acer_A500_1.141.01_EMEA_GEN3: (vermagic=2.6.36.3 SMP preempt mod_unload ARMv7)
Download View attachment 3g-acer31stock-usb.zip for 3.1 stock release Acer_A500_3.019.01_COM_GEN1 (vermagic=2.6.36.3-00005-g5dff38c SMP preempt mod_unload ARMv7)
HOWTO:
- first: Backup your /system/build.prop on the tablet , just copy the file to a safe place, as its important if you wish to do a online update later on.
- updated zip, so you can now install the zip as an "update" using ClockWorkMod/CWM if you got this installed.
- download the "system.zip" attached to this post.
- unpack all files to a temporary folder ie. C:\myfiles
- assuming you got adb running
* push files to your tablet with;
adb shell mkdir /data/local/temp
adb push C:\myfiles\system /data/local/temp/
* next run
adb shell
* then run all commands below in the shell
su -
mount -orw,remount /system (i forgot this line, ITS IMPORTANT)
cp -a /data/local/temp/* /system/
chmod 4755 /system/bin/pppd
chmod 4755 /system/bin/rild
chmod 755 /system/bin/rild.run
chmod -R 755 /system/etc/ppp
If you done these steps correctly, and you reboot.
you will now have a working 3G option in Settings -> wireless networks
so you can configure your APN now and connect to your 3G network.
and you got it all automated with honeycomb 3g! no terminal needed to start 3G!
HINTS
- Other reports are to remember to "Disable PIN" on the card.. I have no personal experience on this part, but check up on it, if its not working perfectly, or no data, but network is ok.
- I got reports back about enabling roaming to make it work, and also remember the story from Folio100 with 3G dongles..
so if you cannot get data connection at all, try to enable roaming and see if APN does not appear which matches your isp. maybe read you ISP website to confirm it.
- If you happen to remove the dongle, there is a solution (using as example gscript) to restart the ril daemon.
in a shell you can restart the ril-daemon if you reinsert the 3g usb dongle.
do it like this in the shell:
su -
stop ril-daemon
start ril-daemon
HOWTO FOR RESET'ing ,massstorage on Huawei modems.
tasmak said:
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
You need also put sim card from modem to any phone and disable pin checking.
Click to expand...
Click to collapse
Remember to press "thanks" if you find it useful
you forgot to say to remount the system to rw....
thor2002ro said:
you forgot to say to remount the system to rw....
Click to expand...
Click to collapse
i believe that line is even highlighted and commented as forgotten previously, so its there for sure..
you cannot miss it
or do you mean some other /system mount?
Looking forward to testing this. Mine is a Verizon Novatel Wireless, do you think this will work with it?
JackMetal said:
Looking forward to testing this. Mine is a Verizon Novatel Wireless, do you think this will work with it?
Click to expand...
Click to collapse
it would probably work, if you got the huawei dongles..
the major is if you need different kernel modules.. those are in the other thread if needed, i included those without -gxXXXX version info.. as thats the ones for the latest EU model update and works here.
Thanks Dexter. One question. Can these files be pushed using terminal emulator instead?
Sent from my A500 using Tapatalk
Yes,
this can of course be done in a terminal, if needed.
just forget the part with "adb",
but all the commands should be executed, and the files copied to a sdcard temporily and copy from that location to the /system
Dexter thanks. What Huawei modem do you recommend?
Sent from my A500 using Tapatalk
manfly9884 said:
Dexter thanks. What Huawei modem do you recommend?
Click to expand...
Click to collapse
i use a E1752 model myself, which i have disabled storage on, before using it on my tablets...
Thanks
Sent from my A500 using Tapatalk
this wil break the OTA ... because of the build.prop modifications...
thor2002ro said:
this wil break the OTA ... because of the build.prop modifications...
Click to expand...
Click to collapse
Correct, that is also mentioned in post #1.
custom build.prop can be made if the lines at the bottom are copied to your own version you got with a simple one-liner in a shell.
echo "picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true " >>/system/build.prop
so it works on any new build.prop change..
Dexter_nlb said:
Correct, that is also mentioned in post #1.
custom build.prop can be made if the lines at the bottom are copied to your own version you got with a simple one-liner in a shell.
echo "picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true " >>/system/build.prop
so it works on any new build.prop change..
Click to expand...
Click to collapse
got an idea.... make two scripts for applying and removing....
so we can maintain the OTA capability...
thor2002ro said:
got an idea.... make two scripts for applying and removing....
so we can maintain the OTA capability...
Click to expand...
Click to collapse
ill figure something out.. maybe an actual patch can be made?
i do know how to make the different update.zip's ... just got A500, so not sure what is possible and not, on this semi-blocked tablet..
but also know motorola mobiles, i have had my part of blocked devices, and do workarounds to make something work.
1 update.zip to install? and another to remove?
we dont have custom recovery working.... so update zip wont work... scripts or apk are the only choices i see...
thor2002ro said:
we dont have custom recovery working.... so update zip wont work... scripts or apk are the only choices i see...
Click to expand...
Click to collapse
no no, i dont talk CWM.. i use the builtin tegra recovery for the additional functions.. the recovery is very close to CWM, but uses the old htc way, and do have specific write command for writing images..
ill check it out soon.. a500 is still new to me, although tegra is not...
I know im probably not doing something right, i followed the steps, and when i tap mobile networks it force closes?
Good news. Thanks
manfly9884 said:
Thanks
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
wounderful work!
good point!
Any reason this wouldn't work on the asus transformer?
re: [DEV] Ubuntu on Nexus S (natively)
I'm new so I can't answer to the thread : [DEV] Ubuntu on Nexus S (natively) in the dev section.
I have a root image (based on the HD2 image) and a netarchy kernel (2.6.35) which contain :
- working wifi module : scanning does not work with iwlist but with wpa_cli, it does (cause of driver and combo scan feature).
- working touchscreen : patched mxt224 kernel module to have ABS_X, ABX_Y and BTN_ events + evdev 2.6
I have converted the ext2 image to an ext4 one. I will try to make proper patches and readme if they are people interrested in.
In 2.6.39, there is a bcm driver in staging. Maybe with 3.0 kernel (waiting ICS kernel sources), we can have a working wifi module with wireless-tools such as wicd or iwlist.
This is awesome... I've been waiting for this just to mess with it
Sent from my Nexus S 4G using Tapatalk
Wow this would be awesome. Any chance you could work on something for the NS4G?
Sent from my Nexus S 4G using xda premium
It seems they have the same configuration (instead of wimax support). This may work.
For now, I can't post on the right thread on DEV section and I can't post the link
You can grab files on : http://www.okazoo.eu/~yan/ubuntu_on_nexuss
The root image file is still uploading ... be patient !
Find a way to enable iwlist and wicd scanning using combo-scan bcm4329 feature.
I have written a wrapper, to use it you need to :
- mv /sbin/iwlist /sbin/iwlist.old
- cp the wrapper script to /sbin/iwlist ...
This is a crappy way as this way is not robust to wireless-tools update !
I can connect to my home wireless router with wicd !
Root image file is uploaded !
I found an interesting stuff to control the modem (2G and maybe 3G) :
http://trac.osuosl.org/trac/replicant/wiki/libsamsung-ipc
I will check if I need to write a RIL library to make a simple interface to write/read SMS and make calls.
The next step is to find GUI apps to do those things !
For some reason, i get a kernel panic while booting. The rootfs at http://forum.xda-developers.com/showthread.php?p=10486278 works fine, but still, no touchscreen or anything
Can you give me some details :
- hardware (Nexus S or Nexus S4G and what version S-LCD or Amoled) ?
- last messages (reason of kernel panic) ?
Did you use my boot image file ?
looks cool, but how to use it without a mouse.
It's the i9020A, the non-Sprint 4G one. I placed your rootfs image into the /sdcard/ubuntu/ folder, and used fastboot to boot the boot.img that you provided in initramfs.tgz. The errors themselves, i'll copy the file back and run it again to pinpoint it.
Doing the same thing with the .ex2 that the other thread uses lets me boot to the GUI, but still, no interaction
radianter said:
looks cool, but how to use it without a mouse.
Click to expand...
Click to collapse
I don't understand the question. Is your touchscreen working ?
breakingspell said:
It's the i9020A, the non-Sprint 4G one. I placed your rootfs image into the /sdcard/ubuntu/ folder, and used fastboot to boot the boot.img that you provided in initramfs.tgz. The errors themselves, i'll copy the file back and run it again to pinpoint it.
Doing the same thing with the .ex2 that the other thread uses lets me boot to the GUI, but still, no interaction
Click to expand...
Click to collapse
I am waiting the output. For now, I am working on a i9023 version. I have uploaded new initramfs archive which contain a more generic boot image file. Can you test it ?
can you tell me how to install this? I am waiting for so long for an working Ubuntu or XP on our beloved nexus s
winsys said:
I am waiting the output. For now, I am working on a i9023 version. I have uploaded new initramfs archive which contain a more generic boot image file. Can you test it ?
Click to expand...
Click to collapse
Sure thing, i'll test it for you. Let me download it real quick.
---------- Post added at 02:07 AM ---------- Previous post was at 01:38 AM ----------
It boots and the touchscreen works. Yay. For some reason, there's no option to configure the Wifi. I'm going to snoop and tweak, see if i can't find it.
---------- Post added at 02:32 AM ---------- Previous post was at 02:07 AM ----------
The app launcher loaded on my second reboot, and after switching to "Wifi mode" It still does not detect any wifi networks. Setting up the At&t APN in the 3G settings doesn't work either.
Normal, it's normal, the module bcm4329 provided in the root image file was build for i9023 kernel.
You can download this file : https://www.okazoo.eu/~yan/ubuntu_on_nexuss/bcm4329.ko
After download, issue : adb push bcm4329.ko /lib/modules/2.6.35.13+/kernel/drivers/net/wireless/bcm4329/bcm4329.ko
Wifi should work after that !
---> download new image files !
Still no luck, after a couple reboots. I'm still faced with "No wireless networks found" in the Wicd network manager. I compared the MD5 sums of the file on the device with the file you linked me, and they match, so i know i pushed it successfully.
The Network Tools lists a Loopback device and several unknown devices occupying different ports, (rmnet0, usb0, sit0), with the Loopback device (lo) selected. Are those imperative?
Hum, at your point, do you see eth0 in the iwconfig listing ?
Do you have copy the iwlist wrapper I made ? iwlist-wrapper must be pushed as iwlist. What is the iwlist scan output ?
iwlist
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
I'll mess with it, see if i can't get it working
---------- Post added at 02:53 AM ---------- Previous post was at 02:34 AM ----------
Running iwconfig returns
# iwconfig
iwconfig
lo no wireless extensions.
rmnet0 no wireless extensions.
ifb0 no wireless extensions.
ifb1 no wireless extensions.
usb0 no wireless extensions.
sit0 no wireless extensions.
ip6tnl0 no wireless extensions.
No mention of eth0.
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
looks interesting will give it a crack and see how it goes
thanks for the work. it boots impressingly fast.
castrwilliam said:
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Click to expand...
Click to collapse
if I activate the onboard keyboard ist shows at the bottom of the login screen. login works without password. when beeing logged in the keyboard is gone. I can see the keyboard symbol on the left besinde the speaker symbol but tapping on it doesn't trigger anything. also changing any options in the control center -> onboard settings have no effects. logging in without keyboard activated and then control center -> onboard settings has no effects either.
I cannot "adb shell" due to lack of permissions
Code:
# adb devices
List of devices attached
???????????? no permissions
and I'm not owning a bluetooth keyboard. so right now I can only play minesweeper - oh wait, it's not installed...
is there any way to rotate the screen as its really annoying having it in portrait all the time
Toby0897 said:
is there any way to rotate the screen as its really annoying having it in portrait all the time
Click to expand...
Click to collapse
Yeah it is in the monitor options but it's worthless since Xorg crashes when changing the rotation
Great stuff!
I would remove the KDE plasma etc packages as that desktop seemed to unusable. (Due to broken hw acceleration?).
what's next?
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
hugomc92 said:
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
Click to expand...
Click to collapse
You will need to install busybox for tar to work
daringblaze said:
You will need to install busybox for tar to work
Click to expand...
Click to collapse
Thank you very much!! That make tar to work!!
Gonna try archLinux ASAP!!
Thanks!
updates
Hi, great stuff!
After installing it, I tried to update arch (
Code:
sudo pacman -Syu
) but this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
computer-whisperer said:
this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
Click to expand...
Click to collapse
Make sure you ignore xorg and mesa stuff. Add
Code:
IgnorePkg = glu mesa mesa-dri mesa-libgl xorg-server-common xorg-server-devel xorg-fonts-misc xproto libdrm
IgnoreGroup = xorg
to /etc/pacman.conf.
The list probably contains some extra entries, but works for me
It took xda 2 years, but they finally did it.
In all seriousness, props to you. I've been waiting for this for along time.
castrwilliam said:
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/......
Click to expand...
Click to collapse
Hi castrwilliam, would you mind sharing what step you went through to create arch_flo_20141210_multirom.tar.gz ?
Great work guys! I was looking for this for a really long time and i am writing this on my n7 with linux but i have a few questions:
1. is it possible to overclock(and how) because my n7 runs on 1.89ghz and 477mhz gpu in android with elementalx kernel and it would be nice to have some more power
2. can the screen be rotated so the hardware buttons are on top (i saw a post saying it chrashes but i cant even find the setting xD) because it would be alot easier to use the OTG cable
And thank you guys for making this happen, i love linux on the note 10.1 and im so glad to have this run it too(would be maaad if it can be overclocked )
Thank you for this wonderful package!
I recently updated all packages ) and iam trying to fix the issue without reinstall (challenge accepted)
It seems that the xorg-server 1.17 is the problem. I compiled. Freedreno and the freedreno mesa 10.3 and libdrn packages without success. The xserver is segfaulting when it loads libexa.so.
Now i try to downgrade to 1.16 . ive read that the xf86-video-freedreno-git package is not working with flo. Is that correct? Did youbuild this packages with modificationa?
I believe this is why i love arch. Its like lego for nerds or something
castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
What's NOT working
Hello, is there some instruction howto run (native) arch on nexus 4? I see only for n7, n10...
castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
Having my favourite distro on my pocket is very exciting so thank you very much...
I have to carry only a development lamp server so using a pacman tip I revert to a base, base-devel system removing everything about xorg and DE.
Now I connect using ssh but I've noticed that the tablet screen is simply blank: no tty, no text console.
There is a way to have a text only console at boot to make a login (may be using an usb keyboard) when device is not connected?
Hello, I have some trouble when I boot.
config: rastapop 5.1.1 (AOSP based) + last multirom v32A + Kernel w/ kexec-hardboot patch (Stock 5.1.1)
Installing archlinux correctly from the terminal emulator. Load it --> black screen (about 6seconds) --> Google Logo forever
Someone know what I can do for make it work ?
Cool I will give it a try.
DON'T FORGET TO HIT THE THANKS BUTTON
!!!DISCLAIMER!!!!
You are solely responsible for whatever shtuff happens to your device by installing either of the two files to your device.
!!!DISCLAIMER END!!!
So this still needs a lot of work but I am providing a working boot.img and root filesystem archive for all Nexus 9 variants? (not sure needs others to test and confirm).
Will be edited as things start working
What's working:
WiFi. (Must use 'nmcli dev wifi con "SSID" password "passwd" ')
GPU @ anywhere from 900-2000 FPS
Sound works just needs reconfiguring
Screen rotation works best with minimal issues as desktop taskbar widgets command to turn clockwise into landscape:
Code:
sudo xrandr -o right; sudo xinput set-prop 7 "Evdev Axis Inversion" 0, 1; sudo xinput set-prop 7 "Evdev Axes Swap" 1
&
Code:
sudo xrandr -o right; sudo xinput set-prop 7 "Evdev Axis Inversion" 0, 0; sudo xinput set-prop 7 "Evdev Axes Swap" 0
For normal portrait orientation
However DO NOT USE THE DISPLAY SETTINGS TO ROTATE IT MESSES UP THE LOGIN ROTATION AND SCREEN GOES BLACK AND SOMETIMES SHOW BACK UP IN LANDSCAPE AND WILL NOT DEFAULT BACK INTO PORTRAIT ORIENTATION. SO YOU MUST DO IT MANUALLY!!!!! See screenshot below
Swipe gestures (Chromium-browser only).
Bluetooth: WORKING!!! Install package bluetooth-touch and set this command into a shell script or enter manually the ENTIRE string:
Code:
brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4354.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
Also using a Bluetooth audio sink works by itself without keyboard connected. I've found it still needs work but, connecting to a keyboard still flawless in its function file transfer locks it up when sending not receiving. Pairing and connecting are all good but functionality of Bluetooth is down to one device at a time for best results
What's not working:
Cameras (Neither front nor rear camera works at all. Needs work).
NFC? (I have no idea how to check for this. Needs work).
Probably other things I missed.
What you will need:
Any Nexus 9 with an unlocked bootloader & latest TWRP recovery installed
USB keyboard
OTG cable
Instructions:
MAKE A BACKUP! Just in case.
1.) Enter into recovery go to wipe and format Data partition as Ext4
2.) Reboot into recovery and with the boot.img and rootfs on a flash drive or, push them to device via ADB.
3.) Go to terminal command in recovery issue the commands: cd /data; mkdir linux; cd linux
4.) tar xvjf /sdcard/rootfs.tar.bz2 -C /data/linux
5.) Flash N9boot.img with install image in TWRP Install submenu.
6.) Reboot into the new Linux system.
7.) If the Kernel panics and boot loops, go back into recovery and format the data partition again it will ask are you sure type yes & repeat steps 2-4
You will need to use a USB keyboard & OTG cable to install the necessary packages and connect to WiFi/Bluetooth.
It's much easier to install on device than in a chroot environment as I have had problems in the past. And some people have different favorite Desktop Environment's. However Gnome and KDE both do not work correctly and crash.
Fluxbox, Mate, XFCE, LXDE, all work as they should with Lightdm.
If there's anything I missed you can add it below, PM me and ask, whatever and I'll try to answer as soon as I am able.
If you are interested in building the entire thing from start to finish here are the original sources
https://forum.xda-developers.com/nexus-9/general/guide-linux-nexus-9-t2985958
https://forum.xda-developers.com/nexus-9/general/guide-linux-nexus-9-t2985958/page14
And thanks to @sonicadvance1 for his original guide & @Vartom for his work on porting some of the necessary Kernel drivers. And @Vartom again for his contributions to the Bluetooth and everything else to get us this far :good::good::good::good::good::good::good::good:
Xubuntu-Desktop Preinstalled 21.5 Drivers 1GB username=ubuntu password=ubuntu
https://drive.google.com/open?id=0B8NgGANYGMhOZS1OenNzZl94bEE
rootfs base only necessary packages root password=toor
https://drive.google.com/file/d/0B8NgGANYGMhOMjVObElVVnBWamM/view?usp=drivesdk
boot.img
https://drive.google.com/open?id=0B8NgGANYGMhOZXAwZHVrUUotZ0k
In order to get the preinstalled to fix login if having issues use the command as root in virtual terminal Ctrl+Alt+F1/F2, etc
Code:
chown ubuntu:ubuntu /home/ubuntu
.
This should fix the login issues, if you want you can create a different user and remove the premade user using these commands as root in virtual terminal.
Code:
deluser username
adduser username
addgroup username adm
addgroup username sudo
Additionally if you have an error when running glxgears there is a fix
Code:
xauth list
It should output something similar to this
Code:
localhost.localdomain/unix:0 MIT-MAGIC-COOKIE-1 a4f6256398303725763c5595f404afbb
You will need to export the display and add that MIT-MAGIC-COOKIE you got from xauth list
Code:
export DISPLAY=":0"; xauth add $DISPLAY . a4f6256398303725763c5595f404afbb
This should fix the display error.
And finally,
Enjoy Ubuntu on your Nexus 9
Video of it booting
https://youtu.be/PIGm47pwzj0
Booted fine.... However a username and password would help...lol
---------- Post added at 10:30 PM ---------- Previous post was at 09:45 PM ----------
andyroidking said:
Booted fine.... However a username and password would help...lol
Click to expand...
Click to collapse
Found the root password in the other thread. toor
Now on to getting wifi up so i can get a de installed....
Reserved
andyroidking said:
Booted fine.... However a username and password would help...lol
---------- Post added at 10:30 PM ---------- Previous post was at 09:45 PM ----------
Found the root password in the other thread. toor
Now on to getting wifi up so i can get a de installed....
Click to expand...
Click to collapse
sk1tch said:
Ha! Sorry I updated the guide above to include that little tidbit of info. Sweet I'm excited to read it worked so far. Hope the guide is simple enough for everybody who wants to try it out
Click to expand...
Click to collapse
Yeah now that I got wifi working I'm off to study how to get xfce4 installed. Everyone says Arch is hard but I'll tell you their repo's are extensive. Now I have to learn about ppa's...
Also, I'm over 50 and because we have a 2048 x 1536 display everything is very tiny making all of this more of a challenge... I tried a couple things to bump the font size but they don't work....
andyroidking said:
Yeah now that I got wifi working I'm off to study how to get xfce4 installed. Everyone says Arch is hard but I'll tell you their repo's are extensive. Now I have to learn about ppa's...
Also, I'm over 50 and because we have a 2048 x 1536 display everything is very tiny making all of this more of a challenge... I tried a couple things to bump the font size but they don't work....
Click to expand...
Click to collapse
I knew you were old school. I did get Arch Linux running on the original guide but it was choppy at best and only ran in the framebuffer but this was the aarch64 version. I do think it could be done because it's my preferred distro these days as well. I think we'd have to change a few things in the CPIO init scripts.. You know point to what it needs but, that's a little too advanced for me.
Also try setting a custom dpi in the settings menu if you're using XFCE I know there's the option there
and to install it you need to uncomment all the extra repos in /etc/apt/sources.list then do apt update && apt install xubuntu-desktop
it should look like in the picture
Well, I'm stuck. X won't start... I'll have to pull the log and see what up. Unfortunately I'm back to work tonight so it will be a while before I get to play again. Don't fret, I'll be back. :silly:
Edit: Pulled logs:
As root user:
https://pastebin.com/3bJE7HkJ
As reg user:
https://pastebin.com/ZVBrCAuM
They look the same to me...
andyroidking said:
Well, I'm stuck. X won't start... I'll have to pull the log and see what up. Unfortunately I'm back to work tonight so it will be a while before I get to play again. Don't fret, I'll be back. :silly:
Edit: Pulled logs:
As root user:
https://pastebin.com/3bJE7HkJ
As reg user:
https://pastebin.com/ZVBrCAuM
They look the same to me...
Click to expand...
Click to collapse
They look identical to me as well. Um try apt install xorg xubuntu-desktop lightdm-gtk-greeter.
then reboot it should automatically enable it with systemd while installing
Error 404
The links to the downloads are no longer working.
sk1tch said:
They look identical to me as well. Um try apt install xorg xubuntu-desktop lightdm-gtk-greeter.
then reboot it should automatically enable it with systemd while installing
Click to expand...
Click to collapse
I'll give that a shot. Sounds like solid advice. Probably not until Thursday or Saturday. Busy week kids back to school
a such...
humannequin777 said:
The links to the downloads are no longer working.
Click to expand...
Click to collapse
I fixed the links but the rootfs.tar.bz2 is down as I am uploading a preinstalled image archive with the XFCE4 DE w/ onscreen keyboard, still ironing out Bluetooth made good progress so hopefully I will have that finished soon
Cameras are not included in the kernel. I did not check their performance in this kernel.
Linux Inside... Nice. Well I found a few minutes and got this far.... https://imgur.com/a/VuDEN Xauthority issue? I'll check into it later. I assume suspend doesn't work? I tried once but didn't want to crash it right now. also changed scroll bar width... easier to tap. Border width is next.
Scroll bar width:
Open the .gtkrc-2.0 file, add the following to a new line starting at the bottom of the file:
Code:
style "myscrollbar"
{
GtkScrollbar::slider-width=XX
}
class "GtkScrollbar" style "myscrollbar"
How's the performance ?
Can I use it as a desktop?
Yes indeed it does work as a desktop I got screen rotation down to two three command scripts with desktop widgets. Most things work as of now Bluetooth sucks no matter what I do but, touchscreen works fine WiFi works fine no Cameras yet Sound only through headset. Hardware acceleration works at anywhere from 800 FPS - 2000 FPS. Videos like on YouTube stutter a little if you are doing other things while watching. Swipe gestures work in Chromium browser only. (Still working on installing multifunction swipe gestures) Your best bet would be to buy one of those $11 Micro-B USB wired tablet keyboards or just use the Onboard keyboard if its already in a rugged case or whatever. Those two green arrows at the top of the desktop are my rotate widgets
andyroidking said:
Linux Inside... Nice. Well I found a few minutes and got this far.... https://imgur.com/a/VuDEN Xauthority issue? I'll check into it later. I assume suspend doesn't work? I tried once but didn't want to crash it right now. also changed scroll bar width... easier to tap. Border width is next.
Scroll bar width:
Open the .gtkrc-2.0 file, add the following to a new line starting at the bottom of the file:
Click to expand...
Click to collapse
Yes there is an .Xauthority error when I flashed it as well that was why I said it's difficult to make a working install and that it was easier to install on device but either try chown ubuntu:ubuntu /home/ubuntu as root and it may fix your issue or you have to create a new user
Vartom said:
Cameras are not included in the kernel. I did not check their performance in this kernel.
Click to expand...
Click to collapse
I added the configs for the camera to my custom config to no avail... I dont have a headset jack debug cable so I can't see what going on during boot
sk1tch said:
I added the configs for the camera to my custom config to no avail... I dont have a headset jack debug cable so I can't see what going on during boot
Click to expand...
Click to collapse
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
---------- Post added at 02:14 PM ---------- Previous post was at 02:08 PM ----------
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
For bluetooth work, you need to download the corresponding firmware.
with some similar string
exec /usr/sbin/brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4324.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
this can be added to the nvwifibt.conf config file.
Vartom said:
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
---------- Post added at 02:14 PM ---------- Previous post was at 02:08 PM ----------
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
For bluetooth work, you need to download the corresponding firmware.
with some similar string
exec /usr/sbin/brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4324.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
this can be added to the nvwifibt.conf config file.
Click to expand...
Click to collapse
So just add this too the sbin config file??
sk1tch said:
So just add this too the sbin config file??
Click to expand...
Click to collapse
brcm_patchram_plus this package was not found. Add it to the fast failed.
Hi Guys
So, as you all know, Quick capture is disabled in devices connected to an Indian network and this had me pissed off for a very long time.
I looked into the Emergency Affordance Service which is responsible for identifying Indian SIMs and found a way to disable it (at least on the 5t).
But a word first.
DISCLAIMER: The Govt of India has stated that it is mandatory for all phone manufacturers to add this functionality for the right reasons. By disabling the feature you will NOT be able to use the triple-press power button for emergency call. I do not take responsibility for any damage caused due to the actions described in this post.
Alright, lets jump into it.
Step 1. Install a terminal emulator app (or connect via adb shell)
Step 2. Enter the following command without quotes:
"settings put global emergency_affordance_needed 0"
(You may use the "settings get global emergency_affordance_needed" command to confirm if it worked.)
Step 3. Check the OnePlus Camera app - the Quick capture option should be there.
Step 4. Profit!?
Notes:
My 5t was rooted with magisk, but I ran the command on a normal ($) prompt so I'm not sure if this requires root or not. Please try it on unrooted devices and let me know so I can update this post accordingly. Also, I haven't checked if it persists after a reboot.
Not working on non rooted device.
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
any idea how the phone detects that its india? Could we spoof that?
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
zeeshanonlyme said:
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
Click to expand...
Click to collapse
Use ADB shell instead of doing in on your phone
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Edit: Found It
https://www.reddit.com/r/oneplus/comments/6ur1ma/double_tap_power_button_setting/
The devs name is Mishaal Rahman ...Maybe he could help us out.
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
Sorry for bumping an old thread but has anybody figured out how do get this working permanently with xposed or magisk ? I bought a OP6 and miss this feature coming from a Nokia 7+
MAGISK Module!
Hi,
Was able to create a magisk module to do this automatically every boot and also got wifi auto turn on to work, check out the thread here.
kashyapha1994 said:
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
Click to expand...
Click to collapse
Might be possible to override this with an overlay (non-root Substratum.)