I picked up a OnePlus 9 Pro, nice phone, and I wanted to run SDR on it but couldn't find a ROM to fit my needs. So, I modified a Lineage 19.1 build to support NetHunter and figured I would share it here in case anyone else was also wanting to do the same.
OnePlus 9 Pro Lineage 19.1 NetHunter Enabled
If you wish to extract the kernel alone, please keep in mind that the VintF compatibility checks were left intact. The compatibility matrices are stored on the System image and you may need that to accompany the kernel.
perelax.
Nice. I just got my OnePlus 9 Pro yesterday and this is exactly what I was hoping for. Perfect timing. I'll check it out and let you know how it goes. Thanks!
Pretty cool work man. Maybe you can edit the topic from Question. I'm sure a lot of people missed this thinking it was another person asking for Nethunter. Good work
Woww!!! Thx man!!! I cant believe that.... It's awesome
Appreciative said:
Pretty cool work man. Maybe you can edit the topic from Question. I'm sure a lot of people missed this thinking it was another person asking for Nethunter. Good work
Click to expand...
Click to collapse
Sorry for the late reply, thanks for the compliment. I thought that the topic might be ambiguous, but its a lot to mention in a title.
Did you try the build? If so, is it working ok?
When I modified the kernel, I checked to make sure that the required dependencies were also selected, so it should be good to go. NetHunter kept crashing before I made the modifications, but it works on my device now.
perelax said:
Sorry for the late reply, thanks for the compliment. I thought that the topic might be ambiguous, but its a lot to mention in a title.
Did you try the build? If so, is it working ok?
When I modified the kernel, I checked to make sure that the required dependencies were also selected, so it should be good to go. NetHunter kept crashing before I made the modifications, but it works on my device now.
Click to expand...
Click to collapse
No, I haven't. Maybe when I get another 9P I'll give it a shot. My daily OS is parrot so I don't think I'd ever need NH on the go but it's still cool. It has been asked about a bunch of times on here, reddit and github for other devices.
And I just meant the "flair" on the post is set to Green "Question". Most people glance over those if they don't think they have the answer. If you can't change it any longer, I'm sure a mod would be happy to change it for you. And then you can get the proper feedback from multiple people on it also.
Is the 9P included wifi card capable of monitor mode or injection, or are you using an external card for those? I remember installing some stuff in one of my Nexus phones to get my Alfas recognized but I never did finish the job on that device.
Also, do you know if it's possible to take advantage of the Adreno gpu for hashcat? Or if there's a mobile equivalent? I'm not sure if there's an API available for the depth needed for something like that. It would be neat to have the onboard gpu increasing hashcat rates tho . Or for someone to make a pcie adapter and I can just carry a spare battery and a 1080ti around with me when I need cracking on the go
Appreciative said:
Also, do you know if it's possible to take advantage of the Adreno gpu for hashcat? Or if there's a mobile equivalent? I'm not sure if there's an API available for the depth needed for something like that. It would be neat to have the onboard gpu increasing hashcat rates tho . Or for someone to make a pcie adapter and I can just carry a spare battery and a 1080ti around with me when I need cracking on the go
Click to expand...
Click to collapse
Even if you had a PCIE adapter... getting any video card, 1080ti or otherwise, working on an ARM chip is not realistic as there are no drivers. And even if you could use the GPU for hashcat it would still be very slow.
Why not just spin up a cloud server with an RTX 4090 or few? You can rent them by the hour. For a full day is only around $30. No need to do it locally... you can just use the phone to capture the handshake, crack it in the cloud via the phone and have the cracked password sent back to your phone. Achieves the same thing you're after but much much faster and without the need to crack it locally on very under powered hardware.
not_the_droid_ur_lookin4 said:
Even if you had a PCIE adapter... getting any video card, 1080ti or otherwise, working on an ARM chip is not realistic as there are no drivers. And even if you could use the GPU for hashcat it would still be very slow.
Why not just spin up a cloud server with an RTX 4090 or few? You can rent them by the hour. For a full day is only around $30. No need to do it locally... you can just use the phone to capture the handshake, crack it in the cloud via the phone and have the cracked password sent back to your phone. Achieves the same thing you're after but much much faster and without the need to crack it locally on very under powered hardware.
Click to expand...
Click to collapse
Carrying around a 1080 otg was a joke. I thought I made that clear when I said carry around a battery, sorry for the confusion or missed sarcasm.
I have been using pooled resources for cracking for ages. We set up hashtopolis and had a bunch of 1080s. I have a different resource now but that wasn't the question anyway. The question was whether someone had a way to use the onboard Adreno gpu to speed up any calculations on mobile. Something similar to hashcat for mobile.
A full day of 4090 for $30 is super interesting tho, I may look into that and compare some speeds of that vs my current pooled resource.
Appreciative said:
Carrying around a 1080 otg was a joke. I thought I made that clear when I said carry around a battery, sorry for the confusion or missed sarcasm.
I have been using pooled resources for cracking for ages. We set up hashtopolis and had a bunch of 1080s. I have a different resource now but that wasn't the question anyway. The question was whether someone had a way to use the onboard Adreno gpu to speed up any calculations on mobile. Something similar to hashcat for mobile.
A full day of 4090 for $30 is super interesting tho, I may look into that and compare some speeds of that vs my current pooled resource.
Click to expand...
Click to collapse
Ok sorry. Sometimes I take things a bit too literally.
Was almost going to mention hashtopolis but was trying to keep it short. That's cool though.
To at least half answer the actual question... it would seem 3d hardware acceleration is possible on a rooted device in a linux chroot. See mesa 3d library / Turnip + Zink https://github.com/Grima04/mesa-turnip-kgsl
Discussion about it here:
[Guide] Running Linux on Android with 3D Acceleration / OpenGL (Root Required)
All credits go to: Hentacler for making Sparkle Meefik for making Linux Deploy Now on to the tutorial! Requirements: Sparkle Linux Deploy Termux Now you have all those apps installed lets continue Open Termux then enter: su Once in root...
forum.xda-developers.com
That doesn't answer if it works with hashcat, but probably it will.
Awesome work! I was hoping this would come out soon. Anyone try out any of the features and see what’s working yet? Injection, monitor mode, internal Bluetooth, etc? I’m debating upgrading to an 8 Pro or 9 Pro, but I wanted to see if the stuff from the unofficial 8 Pro kernel was working here yet.
Thank you for building this ROM and kernel. I have tried many times to get the wireless adapters to work with this. Monitor mode works natively if you find the right version of nethunter or install the nethunter lite zip. But it stops working after update && upgrade. I haven't tested the desktop version yet to see if packet injection works in that mode. But testing injection mode by typing sudo aireplay-ng -9 wlan0 doesn't find any APs and injection doesn't work. If someone has gotten it to work can you help me out.
I got the wireless adapters to work after using the firmware module for magisk. Injection works also. Thank you for making this build
NameIsOptional said:
I got the wireless adapters to work after using the firmware module for magisk. Injection works also. Thank you for making this build
Click to expand...
Click to collapse
Nice! Way to go, dude. By chance did you test HID interfaces? Are you still able to use everything after update && upgrade since you installed the Magisk module?
DomDomPop said:
Nice! Way to go, dude. By chance did you test HID interfaces? Are you still able to use everything after update && upgrade since you installed the Magisk module?
Click to expand...
Click to collapse
I didn't test the hid interfaces or the bluetooth. I did test the packet injection using an Alfa AWUS036NHA. The adapter also still worked after running update and upgrade. After installing the firmware module and restarting. I plugged the adapter in but it didn't light up. So I went to custom commands in the nethunter app and chose start monitor mode on wlan1 and the blue light came right on.
NameIsOptional said:
I didn't test the hid interfaces or the bluetooth. I did test the packet injection using an Alfa AWUS036NHA. The adapter also still worked after running update and upgrade. After installing the firmware module and restarting. I plugged the adapter in but it didn't light up. So I went to custom commands in the nethunter app and chose start monitor mode on wlan1 and the blue light came right on.
Click to expand...
Click to collapse
Aha! Thanks for the update. So this is strictly on external Wifi adapters or was both internal and external working? Sorry, I’d test this stuff myself but I haven’t decided whether I’m gonna get a 9 Pro or just get an 8 Pro and use the official release.
Both worked for monitor mode but I don't know if the internal is capable of packet injection. I tried aireplay-ng's injection test and it didn't say injection mode was working, but it did work with the adapter. Are you certain that the internal can inject on the 8 pro? I've been told that the 7 pro was the last that it worked with. But I could be wrong.
NameIsOptional said:
I got the wireless adapters to work after using the firmware module for magisk. Injection works also. Thank you for making this build
Click to expand...
Click to collapse
Can't you install the Nethunter mod on any device w/Magisk?
I ask bc I've installed it and got chroot installed successfully with different devices as I'm interested in learning to use Kali (been lacking on it tho) but have had problems with newer ROMs on 1+7pro, haven't tried the 9 pro yet but have the device. I like custom heavy OS like crDroid and stuff (certain features I gotta have), so I'm wondering if there is anything specific about this ROM and Nethunter compatibility?
You need the nethunter kernel for packet injection to work properly. This ROM has the kernel built into lineage 19 and everything seems to work fine. The internal WiFi doesn't do injection. But it can be put into monitor mode.
I've got a question:
Is the USB arsenal present on the nethunter app drawer? I'm on Nameless AOSP with nethunter chroot installed and yet I can't access it...
David_#27 said:
I've got a question:
Is the USB arsenal present on the nethunter app drawer? I'm on Nameless AOSP with nethunter chroot installed and yet I can't access it...
Click to expand...
Click to collapse
I got the USB arsenal to work after installing USB gadget tool from f-droid.
Related
no autoration and sound on both devices so i think it doesn't work on any bay trail devices i use last version of remix os 2.0.403 DEVELOPERS PLEASE, make drivers for bay trail devices
arteezy123 said:
no autoration and sound on both devices so i think it doesn't work on any bay trail devices i use last version of remix os 2.0.403 DEVELOPERS PLEASE, make drivers for bay trail devices
Click to expand...
Click to collapse
Did you get a working desktop for the VivoTab Note? Are the only issues rotation and sound?
UnAbsoluTe said:
Did you get a working desktop for the VivoTab Note? Are the only issues rotation and sound?
Click to expand...
Click to collapse
yep, the only issues with rotation and sound
Hi. Can you tell how you did it? Booted from a USB pendrive or from MicroSD?
Does the stylus digitizer with pressure sensitivity work?
Thx!
fpereira_pt said:
Hi. Can you tell how you did it? Booted from a USB pendrive or from MicroSD?
Does the stylus digitizer with pressure sensitivity work?
Thx!
Click to expand...
Click to collapse
I found this on the Goog last night after seeing this thread.
https://groups.google.com/forum/#!topic/remix-os-for-pc/D67FhZpMAvQ
I haven't gotten any further than wiping the Vivo as of yet, but I'm hopeful. Some say the stylus works. We'll see I guess. Also, the post is from March so I assume this is for Remix 2 but I'm going to be bold and try it with Remix 3. Let me know how your attempts go.
3.0 wouldn't even begin to install for me but I was trying to install onto a SD card. I WAS able to load 2.0 onto the SD card but it wouldn't boot. I finally installed 2.0 onto the internal storage and it booted right up. So far WIFI worked and I just jumped back into Windows to finish off the fixes outlined on the google page. It looked pretty and ran smoothly for the limited amount of time I had it running so far.
Hi guys,
I would like to know if there's a possibility to display the battery status of a connected Bluetooth device on the Oneplus 3? Natively or via a third party app? Ideally for me, it should work on the stock ROM but if necessary I would flash a custom one if it would only be possible that way.
Thanks in advance :good:
Joshinho. said:
Hi guys,
I would like to know if there's a possibility to display the battery status of a connected Bluetooth device on the Oneplus 3? Natively or via a third party app? Ideally for me, it should work on the stock ROM but if necessary I would flash a custom one if it would only be possible that way.
Thanks in advance :good:
Click to expand...
Click to collapse
lineage os and others support this natively thou unlike the iphone way we just have a small icon next to the bluetooh icon displayying the amount of battery left
Joshinho. said:
Hi guys,
I would like to know if there's a possibility to display the battery status of a connected Bluetooth device on the Oneplus 3? Natively or via a third party app? Ideally for me, it should work on the stock ROM but if necessary I would flash a custom one if it would only be possible that way.
Thanks in advance :good:
Click to expand...
Click to collapse
Hi
Check an app called BatON (by limitium)
Have not used it personally though.
pvramk said:
Hi
Check an app called BatON (by limitium)
Have not used it personally though.
Click to expand...
Click to collapse
Thanks for the suggestion but it doesn't seem to work with my specific pair of headphones :/ If that means that they don't send battery information to the phone I probably can't get it to work with any solution.
Joshinho. said:
Thanks for the suggestion but it doesn't seem to work with my specific pair of headphones :/ If that means that they don't send battery information to the phone I probably can't get it to work with any solution.
Click to expand...
Click to collapse
Sorry to hear that.
FWIW after suggesting the app to you, I did try it out. It seemed to work with my pair of blue tooth headphones during the limited time I used it..
Going by the comments about the app in the play store, it looks like the usage is limited based on the manufacturer of the blue tooth device....
Just to close this topic: This feature was released in Open Beta 19 and for me it works great!
how to enable that??? by default its not showing when connected......... im on latest beta
Joshinho. said:
Just to close this topic: This feature was released in Open Beta 19 and for me it works great!
Click to expand...
Click to collapse
How do you activate it? I have a watch connected and it's not showing anything
I didn't have to activate it. For me it just worked. Your Bluetooth device still has to support sending its battery information to the phone. In this months Open Beta update there were some fixes for this feature. Maybe it works for you now?
Edit: grammar
This is not my creation, but it took me a long time to find this and it actually works, so I am going to post a link to the other XDA thread to make it easy to locate.
https://www.google.ca/amp/s/forum.x...neageos-15-1-note-5-android-8-1-t3737405/amp/
My WiFi and calls work. The camera was glitchy but if that bothers you, remove it with a system app uninstaller and replace it with one you prefer. I also did not care for lawnchair or trebuchet launcher so I replaced them with pixel launcher(also here on XDA).
I have not noticed any other bugs so far in the past 24 hours I've been using the ROM. Make sure you flash all the zips, there are a couple of zips with the ROM that fix things. Also take a moment to give the developer a thank you, its a fully functional oreo on s6 edge +!
Thanks for reading, enjoy the upgrade to Oreo
Zenlte moddified lineage 15.1/nexusOS for s6e+ done by myself. I did some stuff to get the camera going a bit better. Lower res to 1080p. The full thread is in the s6e+ t mobile forum under android development the original rom and kernel are in the link above at the top.
https://mega.nz/#F!aaIDmT5D!FG9QpMYPcNCjlDiIkGCX4g
godkingofcanada said:
This is not my creation, but it took me a long time to find this and it actually works, so I am going to post a link to the other XDA thread to make it easy to locate.
https://www.google.ca/amp/s/forum.x...neageos-15-1-note-5-android-8-1-t3737405/amp/
My WiFi and calls work. The camera was glitchy but if that bothers you, remove it with a system app uninstaller and replace it with one you prefer. I also did not care for lawnchair or trebuchet launcher so I replaced them with pixel launcher(also here on XDA).
I have not noticed any other bugs so far in the past 24 hours I've been using the ROM. Make sure you flash all the zips, there are a couple of zips with the ROM that fix things. Also take a moment to give the developer a thank you, its a fully functional nougat on s6 edge +!
Thanks for reading, enjoy the upgrade to Oreo
Click to expand...
Click to collapse
Forgot to mention pixel has an app you can get that allows you to install icon packs and change names of apps.
A peek at the about.
That rom is still not stable enough.
El Solido said:
That rom is still not stable enough.
Click to expand...
Click to collapse
I haven't had anything crash or anything serious go wrong yet.
godkingofcanada said:
I haven't had anything crash or anything serious go wrong yet.
Click to expand...
Click to collapse
Well i tried it, rom was little laggy for me, camera is unstable, high definition videos lags, batter life is bad and other minor things, but can be used no crashes or anything
El Solido said:
Well i tried it, rom was little laggy for me, camera is unstable, high definition videos lags, batter life is bad and other minor things, but can be used no crashes or anything
Click to expand...
Click to collapse
I fixed the battery life with kernel auditor and replaced the video/camera with s different one. Then I removed the init.d and reinstalled it to get proper access, also used a different super user then the one provided. I've got xposed running with busybox and amplify. I'm not a dev but I am in college studying computer programming. My take on this ROM is if you know your way around your droid well and can invest some time any bug in it is fixable. The battery could be improved more by using a different kernel or editing the one contained in this ROM to add more governor settings and tweeks. I reached out to the ROM developer on that subject, with any luck they will look into it.
godkingofcanada said:
I fixed the battery life with kernel auditor and replaced the video/camera with s different one. Then I removed the init.d and reinstalled it to get proper access, also used a different super user then the one provided. I've got xposed running with busybox and amplify. I'm not a dev but I am in college studying computer programming. My take on this ROM is if you know your way around your droid well and can invest some time any bug in it is fixable. The battery could be improved more by using a different kernel or editing the one contained in this ROM to add more governor settings and tweeks. I reached out to the ROM developer on that subject, with any luck they will look into it.
Click to expand...
Click to collapse
I know i tried other camera again unstable camera, sometimes works without issues, sometimes its ****, i got also xposed running, bluetooth music play was little stuttering, and you cant fix high definition lag yet, so not worth for me
El Solido said:
I know i tried other camera again unstable camera, sometimes works without issues, sometimes its ****, i got also xposed running, bluetooth music play was little stuttering, and you cant fix high definition lag yet, so not worth for me
Click to expand...
Click to collapse
Mine stutters a bit but not too bad. I removed the camera and then flashed the s6 edge camera instead of the s6 and it improved a fair bit. Luckily I do not use Bluetooth audio so in my case only recording videos has a bug still and its not a deal breaker as I walk around with my s6 e+ as my surfing and calls device and my s7 is my music and gaming device. So for me I just record with s7 if I need video while I try to fix it. Once I figure it out I will share the details.
godkingofcanada said:
Mine stutters a bit but not too bad. I removed the camera and then flashed the s6 edge camera instead of the s6 and it improved a fair bit. Luckily I do not use Bluetooth audio so in my case only recording videos has a bug still and its not a deal breaker as I walk around with my s6 e+ as my surfing and calls device and my s7 is my music and gaming device. So for me I just record with s7 if I need video while I try to fix it. Once I figure it out I will share the details.
Click to expand...
Click to collapse
If its your second device then it can be used, but as primary device rom is not stable enough.
Error logs for camera.
Logs
I'm not an expert but this seems to be a Java runtime error. I have to really get down to the core and look now. The only time I encounter an error with parsing an int is when the syntax is wrong, like trying to parse an invalid type to an int. I'm starting to believe I'm going to need to remove all traces of the camera from the droid 100% and try flashing zips from different models until it works. Or sit down with eclipse and go through line by line and solve the exceptions Java is throwing.
El Solido said:
If its your second device then it can be used, but as primary device rom is not stable enough.
Click to expand...
Click to collapse
I got HD working for photos and videos but now the video frame freezes like its a photo and only audio records. Argh
OK I got it. If you edit the settings in the native app and drop video recording from 4k to 1080 it improves a lot. And open camera from the play store looks / sounds a bit better for video. I can now record videos in HD and its not choppy or laggy. VoIP is also working. Besides the Bluetooth issue that you mentioned which I can not test to troubleshoot I don't know of any remaining issues. Have you tried removing Bluetooth drives and files reinstalling it?
Bluetooth-audio doesn't work on my SM-G928F. NFC, WiFi-Direct and AndroidBeam are also not working.
DGB100 said:
Bluetooth-audio doesn't work on my SM-G928F. NFC, WiFi-Direct and AndroidBeam are also not working.
Click to expand...
Click to collapse
Yeah because you install remove nfc zip so ofcourse, and who use nfc anyway
DGB100 said:
Bluetooth-audio doesn't work on my SM-G928F. NFC, WiFi-Direct and AndroidBeam are also not working.
Click to expand...
Click to collapse
Have you tried not removing the NFC and seeing if it boots?
So the pre installed camera works on and off due to runtime errors and conflicts stemming from Exynos camera3. The files are named camera 2 but logcat shows camera 3. I tried cyanogen but I get the error that it can't find media recorder. I'm going to try installing media recorder and seeing if it works with the cyanogen camera. Fingers crossed
El Solido said:
If its your second device then it can be used, but as primary device rom is not stable enough.
Click to expand...
Click to collapse
I'm hearing camera 2 API is not fully supported on the s6 devices. This could be the issue. However if I am correct that sucks. Because I can not just swap API. I would have to talk to the dev and he or I would have to reduild the ROM using media recorder API if that's possible in Oreo. I assume it would still work despite being depreciated by Google and it's java.
Since there is no way in a GSI (without recompiling stuff) to add proper support for the screen slider, I'm going to see if I can write a shell script to run on update of the value for the sensor that detects the position of the display, however,I don't actually know what sensor this is.
After a bit of testing, I believe there's a magnetic field sensor that detects the change in the field as the screen moves (since moving a magnet over the device can activate the slider detection ) however I am unsure about this.
ambitiousButRubbish said:
Since there is no way in a GSI (without recompiling stuff) to add proper support for the screen slider, I'm going to see if I can write a shell script to run on update of the value for the sensor that detects the position of the display, however,I don't actually know what sensor this is.
After a bit of testing, I believe there's a magnetic field sensor that detects the change in the field as the screen moves (since moving a magnet over the device can activate the slider detection ) however I am unsure about this.
Click to expand...
Click to collapse
I'm not sure how useful it will be to identify the hardware. Somewhere, there must be a driver, and there must also be some way, in the stock rom/kernel, to register an action associated with that driver.
It's a magnetic sensor
and I know this because when i slide it into my magnet dash holder, it activates the slide.
then I tried just sliding a magnet across the back, and yes it activates the slider lol
invisiblewave said:
I'm not sure how useful it will be to identify the hardware. Somewhere, there must be a driver, and there must also be some way, in the stock rom/kernel, to register an action associated with that driver.
Click to expand...
Click to collapse
if i can identify the sensor, i can try to find the file associated with its value in the 'sys' partition, and read this to detect changes, when it changes, this can be used to assign an event etc...
in the same way that i did my flashlight fix for huawei phones with GSIs, this would just be a bash script running accessing the specific files associated with the hardware, as remember android is linux (is unix), so everything is a file, this includes the state of the sensor, so it can be read
ambitiousButRubbish said:
if i can identify the sensor, i can try to find the file associated with its value in the 'sys' partition, and read this to detect changes, when it changes, this can be used to assign an event etc...
in the same way that i did my flashlight fix for huawei phones with GSIs, this would just be a bash script running accessing the specific files associated with the hardware, as remember android is linux (is unix), so everything is a file, this includes the state of the sensor, so it can be read
Click to expand...
Click to collapse
i understand. I'm not an Android developer, but i work in a similar industry
There is also the possibility that the magnetic switch actually pushes some sort of "button" inside the phone, it could even be some sort of magnetic film where a magnet pushes two membranes together to complete a physical circuit like a button.
would "show input touches" or some sort of log viewer be able to see what that input is?
i killed tupac said:
i understand. I'm not an Android developer, but i work in a similar industry
There is also the possibility that the magnetic switch actually pushes some sort of "button" inside the phone, it could even be some sort of magnetic film where a magnet pushes two membranes together to complete a physical circuit like a button.
would "show input touches" or some sort of log viewer be able to see what that input is?
Click to expand...
Click to collapse
judging by the teardown, there's no physical switch.
ive tried aida64, but it doent list all sensors, there is however a hall sensor that does not display a value, that looks somewhat promising, i will investigate this more.
the input is over gpio or similar so show input touches wouldn't work, however, a logcat output might
It's in kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/perseus-p-oss/drivers/halls/halls.c
AndroPlus said:
It's in kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/perseus-p-oss/drivers/halls/halls.c
Click to expand...
Click to collapse
Thanks! As I suspected. All we need now is a kernel programmer who can merge it into the AOSP kernel for the MM3!
I'll still see if I can 'hack' a temporary solution, I'm not a kernel dev (and know very little C) so will try my bash script solution.
Anyways, flashing a GSI doesn't alter the kernel, it's down to the system to communicate with kernel modules, if the system doesn't implement the features, even if it's in the kernel, it won't work.
ambitiousButRubbish said:
I'll still see if I can 'hack' a temporary solution, I'm not a kernel dev (and know very little C) so will try my bash script solution
Click to expand...
Click to collapse
But without the driver in the kernel, there'll be no external notification.
invisiblewave said:
But without the driver in the kernel, there'll be no external notification.
Click to expand...
Click to collapse
True for a custom kernel, but not if you flashed the GSI onto a stock kernel since the driver already exists, it's down to Android to communicate with the kernel, if the communication methods don't exist in the Android system then it doesn't work, conveniently it may however be possible to read the value of the hall sensor through a bash script, and subsequently an app. In the same way that you can turn on an off the flashlight by changing the values in /sys/class/LEDs, regardless of what system (stock kernel though) you are running, will work the same for the hall sensor.
I just need to find what file the system uses as it's interface with the kernel driver, looks like it's over GPIO, which means finding it will be 'fun'
ambitiousButRubbish said:
I just need to find what file the system uses as it's interface with the kernel driver, looks like it's over GPIO, which means finding it will be 'fun'
Click to expand...
Click to collapse
Would the event not be logged in dmesg or kern?
invisiblewave said:
Would the event not be logged in dmesg or kern?
Click to expand...
Click to collapse
i can view events written to logcat, but its simply a log stating the sensor was polled when the screen slides, not what io is being checked, though, looking at the kernel source, gpio 49 and 113 are used, which i cant find in /sys/class/gpio, there is a 'halls' folder under /sys/devices/virtual/misc, which corresponds to the sensor, but it doesn't contain anything of any use, apart from the uevent details, which i cant do nything with anyway
ambitiousButRubbish said:
i can view events written to logcat, but its simply a log stating the sensor was polled when the screen slides, not what io is being checked, though, looking at the kernel source, gpio 49 and 113 are used, which i cant find in /sys/class/gpio, there is a 'halls' folder under /sys/devices/virtual/misc, which corresponds to the sensor, but it doesn't contain anything of any use, apart from the uevent details, which i cant do nything with anyway
Click to expand...
Click to collapse
That's one step further, at least you know the kernel knows about the sensor. I checked dmesg on mine (non-GSI) and I don't see any sign of it. The "everything is a file" mantra is great, but I spend half my life trying to find files in Linux when I have a problem...... I wish IBM would take it and rework it all to make it logical and useable, or better yet, make the IBM i run Linux apps.
invisiblewave said:
That's one step further, at least you know the kernel knows about the sensor. I checked dmesg on mine (non-GSI) and I don't see any sign of it. The "everything is a file" mantra is great, but I spend half my life trying to find files in Linux when I have a problem...... I wish IBM would take it and rework it all to make it logical and useable, or better yet, make the IBM i run Linux apps.
Click to expand...
Click to collapse
im on stock checking all of this, but since im looking in /sys, flashing a GSI or any other system image doesn't affect that, so i know, if i can make it work on stock, chances are, it will work on non stock too, however, should your system flash overwrite /sys, then you may have an issue.
ambitiousButRubbish said:
im on stock checking all of this, but since im looking in /sys, flashing a GSI or any other system image doesn't affect that, so i know, if i can make it work on stock, chances are, it will work on non stock too, however, should your system flash overwrite /sys, then you may have an issue.
Click to expand...
Click to collapse
Yes. Hence my previous comment about merging the driver into the AOSP kernel. It'll be a cold day in hell before I go back to MIUI.
invisiblewave said:
Yes. Hence my previous comment about merging the driver into the AOSP kernel. It'll be a cold day in hell before I go back to MIUI.
Click to expand...
Click to collapse
i understand your point now, theres quite a bit more than just the slider implementation you need though for the device to function correctly with an AOSP kernel. To be fair to MIUI, having come from an honor 9, i only suffered EMUI for a month before i got rid of it, becasue it was so unbearable, MIUI, i dont really mind that much, its actually designed well, and is pretty nice to look at, obviously i still prefer stock android, hence the idea of this, because i could just flash a GSI and still have a somewhat semi functional slider.
ambitiousButRubbish said:
i understand your point now, theres quite a bit more than just the slider implementation you need though for the device to function correctly with an AOSP kernel. To be fair to MIUI, having come from an honor 9, i only suffered EMUI for a month before i got rid of it, becasue it was so unbearable, MIUI, i dont really mind that much, its actually designed well, and is pretty nice to look at, obviously i still prefer stock android, hence the idea of this, because i could just flash a GSI and still have a somewhat semi functional slider.
Click to expand...
Click to collapse
Yes, I know, but the work has already been done on the AOSP kernel, since we have a bunch of non-GSI roms now running (I'm assuming they don't use the OEM kernel, otherwise the driver would be present and the interrupt would work). With the driver merged into the whatever kernel the non-GSI roms are running, we'd then be at the same point with the non-GSI roms as we are with the GSI, at least as far as detecting the slider action goes. Then your app/script would work on either.
invisiblewave said:
Yes, I know, but the work has already been done on the AOSP kernel, since we have a bunch of non-GSI roms now running (I'm assuming they don't use the OEM kernel, otherwise the driver would be present and the interrupt would work). With the driver merged into the whatever kernel the non-GSI roms are running, we'd then be at the same point with the non-GSI roms as we are with the GSI, at least as far as detecting the slider action goes. Then your app/script would work on either.
Click to expand...
Click to collapse
as i said earlier, the GSI (im talking about where you just flash the SYSTEM image, nothing else) ROMs wont detect the event since its handled by the MIUI framework, so whilst the event does take place, the only way of knowing it takes place is having something poll the data the kernel outputs for the event, which would either mean a third party program, or somehow getting the MIUI framework working on AOSP, but you then have the issue of it being MIUI, which you want to get rid of. maybe its worth me looking a the code for the slider implementation in the MIUI framework, if its open source.
ambitiousButRubbish said:
as i said earlier, the GSI (im talking about where you just flash the SYSTEM image, nothing else) ROMs wont detect the event since its handled by the MIUI framework, so whilst the event does take place, the only way of knowing it takes place is having something poll the data the kernel outputs for the event, which would either mean a third party program, or somehow getting the MIUI framework working on AOSP, but you then have the issue of it being MIUI, which you want to get rid of. maybe its worth me looking a the code for the slider implementation in the MIUI framework, if its open source.
Click to expand...
Click to collapse
You've already proved that it's not the ROM detecting the event, it's the kernel. GSI - Xiaomi kernel, slider event detected, no framework in ROM to handle the event. Non-GSI - AOSP kernel, slider event not detected, no framework in ROM to handle the event. If the driver is merged into the AOSP kernel, then GSI & non-GSI roms are in the same boat, needing either an app or your script to handle the event.
Xperia 10 III is now officially supported by Sailfish OS: https://blog.jolla.com/xperia-10-iii/
From Wikipedia:
Sailfish OS is a Linux-based operating system based on free software, and open source projects such as Mer as well as including a closed source UI. The project is being developed by the Finnish company Jolla.
Click to expand...
Click to collapse
Anyone in here tried it yet?
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
According to its readme file, Newflasher runs on Linux too: https://github.com/munjeni/newflasher
So I think it should be possible to flash an Android 11-based firmware from here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/ using this tool. But I never used it (neither on Windows nor on Linux) so I can't say for sure whether that works.
As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?
As for the issue with unlocking your bootloader, at the risk of stating the obvious, did you enable "OEM unlocking" in developer options?
Click to expand...
Click to collapse
Ha! Yes I did do all the required steps. I found an Android 11-based build on the Sailfish forums which worked, after doing it twice with Newflasher. Once this was done the OEM unlock command did its thing without a hiccup. Sailfish OS is now running nicely on the 10 III - hopefully Jolla are able to provide some more complete instructions for those who have managed to upgrade themselves into a documentation loop!
I've been using the X10III with Sailfish for several days now, and the experience is quite smooth. There is no green tint visible, but the "color space" gets really smashed and mangled in low light + low brightness situations... I think it's more or less the same bug. The best way to describe is that the dark areas of the screen are rendered with 8-bit color palette and way too high brightness. I created a bug report for it over at Sailfish OS Forum for those who wish to keep an eye on that.
There are three known issues: Camera API doesn't support the three back cameras (Camera2 API does support it, so it's very fixable), the indicator led is way too green (driver issue), and issues with noise cancellation during phone calls (seems to be fixed in git).
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
direc85 said:
Despite the above, SFOS on X10III a hugely net positive! VoLTE works now - finally - so spring 2023 can now arrive (killing 3G here in Finland). 5G support is not there (yet?), which is a tiny bit unfortunate.
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
I have a hard time understanding why it is necessary to repair a thing that is not broken?
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
And in general, calling is the least used feature of the phone lately.
ksuuk said:
I have a hard time understanding why it is necessary to repair a thing that is not broken?
Click to expand...
Click to collapse
What exactly are you referring to? 3G, the OS in the device, or something else..?
ksuuk said:
VoLTE calls? Why? Today, almost every phone subscription includes if not all free, then at least thousands of minutes of free calls. In addition, there are available all sorts of apps that you can use for voice calling.
Click to expand...
Click to collapse
Why shouldn't I use what I already paid for?
But yes, phone calls are getting rarer; for me it's something between daily and weekly. But still, it's the official method to be reached, supported by pretty much every device, so why not just use it instead of apps.
Also, if I wanted to use only apps to talk with my friends, I'd have five chat apps installed, some of them analyzing me, and all of them draining my battery. No thanks...
But let's get back to topic. Does anyone know how to solve the color banding issue on AOSP?
direc85 said:
I didn't realize that the AOSP firmware is so far away from Android firmware... I somehow assumed before that they were the same... Oh well, live and learn.
Click to expand...
Click to collapse
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.
Aranornen said:
Tell me, are there any battery charging settings in this OS? Android in Xperia 10 III has settings to limit charging to 80, 90% a very nice option.
Click to expand...
Click to collapse
I can't say anything about features built into the OS (as I've never used it), but I was able to find two 3rd party apps which let you limit the maximum battery charge level:
Battery Buddy | OpenRepos.net — Community Repository System
openrepos.net
takimata / harbour-battery-charging-control · GitLab
SailfishOS application which allows to stop battery charging at user-defined levels.
gitlab.com
Piecer said:
I've bought my license and am trying to get this going - I've been unable to use the fastboot command to unlock the bootloader, which I assumed was due to the Android version being 12, and I'm now struggling to downgrade this to 11 as it seems all the tools for doing so are Windows only.
Has anyone done this process on Linux successfully? I understand some people on the Sailfish forums have managed to get it to flash over an Android 12 base but I can't even get to that stage because of the OEM unlock command failing.
Really looking forward to going back to Sailfish after a bit of a hiatus though!
Click to expand...
Click to collapse
hi can you help me o i have an Xperia 5 phone running sailfish os same as your Xperia 10 mark 3 i cant buy license to run apk app you can extract aliendalvik file can you give it to me, i will keep it from sharing to anyone, because it is the source of life jolla , i will transfer you a small amount of money, i come to sailfish os full of passion but not enough money , hope you can help, thank you very much