Related
Hello all,
I've started working on CM12 for RedMi 1S. So here I'm going to discuss about the further status and builds for the rom.
For those who wants to join and help out :-
Current Status :-
Tree is now buildable without any sort of errors
ROM doesn't boots stucks at MI logo
So Kernel ain't loading up yet
I'd request to make pull request if you've any fix for anything.
CREDITS :-
armani-dev(fefifofum, Kra1o5 for all their work and base tree)
CyanogenMod
If anyone missed here please pm me
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Tarun93 said:
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Click to expand...
Click to collapse
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
kD said:
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
Click to expand...
Click to collapse
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Tarun93 said:
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Click to expand...
Click to collapse
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
kD said:
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
Click to expand...
Click to collapse
kkkkkkkkk keep me updated i will dig more info i can
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
kD said:
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
Click to expand...
Click to collapse
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Awesome!
kD said:
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Click to expand...
Click to collapse
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
i do agree with jsevi83 pal even i tried with my noob knowledge now m bored
jsevi83 said:
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
Click to expand...
Click to collapse
I went through your changes. I've came to some conclusions.
Add display_config header
Well it adds display_config header at CM11 but at CM12 it is already present.
display_config header at CM12 just add this line at the bottom rest all is same.
Code:
// set the view frame information in hwc context from surfaceflinger
int setViewFrame(int dpy, int l, int t, int r, int b);
This is the only extra part at CM12's display_config header?
So can you tell em do actually need to comment out this line?
Now libmemtrack is already present at CM12.
Now at media
mm-core/inc/QCMetaData.h is edited to disable few components but if i do the same at CM12 it throws the build error?
Build error is already posted above.
Any idea for fix would be really helpful.
good luck
:fingers-crossed: i am not a dev , but i can be a tester for yu guys .. good job friends , i wish to apreciate your effort towards redmi 1s.. hope to seee lolipop on our devices soon
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
thewisenerd said:
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
Click to expand...
Click to collapse
I've done those commits for fixing display. They were applied at CM11 same needs to be applied at CM12. So I need them.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
thewisenerd said:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
Click to expand...
Click to collapse
yeah just figured out you're right. changes at media were just done to override the path because it was changed display-caf-legacy.
Removed those edits.
Now just need to fix display build error.
Building now will post error here soon.
p.s. thank you
Any update ?
I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.
cm11noob10 said:
I'm new to building custom roms and am having trouble brunching CypherOS for marlin. I have the repo synced and have the marlin files but keep running into errors such as a missing makefile that is in the device directory. Any help would be appreciated.
Click to expand...
Click to collapse
Any news on this awesome rom?
Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.
cm11noob10 said:
Having some trouble getting it to build. Getting error: TARGET_USES_UNCOMPRESSED_KERNEL is deprecated..
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk
liam_davenport said:
Try this
Remove this line: TARGET_USES_UNCOMPRESSED_KERNEL := false in: device_google_marlin/marlin/BoardConfig.mk
Click to expand...
Click to collapse
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.
cm11noob10 said:
Thanks, removed a few more lines and got further into the build. Got stopped by INSTALLED_KERNEL_HEADERS needed by 'out/target/product/marlin/obj/EXECUTABLES/ebtables_intermediates/getethertype.o' missing and no known rule to make it.
Click to expand...
Click to collapse
What linux distro are you using?
liam_davenport said:
What linux distro are you using?
Click to expand...
Click to collapse
Ubuntu. I have problems running Arch in a VM without scaling issues.
cm11noob10 said:
Ubuntu. I have problems running Arch in a VM without scaling issues.
Click to expand...
Click to collapse
Try this: sudo apt-get install linux-headers-generic
liam_davenport said:
Try this: sudo apt-get install linux-headers-generic
Click to expand...
Click to collapse
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.
I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).
If you get it working I could try my hand for the sailfish
YTSec said:
I'd be extremely interested in this, mainly for the music recognition. I was actually going to attempt to build this later today (I probably have the same experience as you, so it's unlikely it would work out much better).
Click to expand...
Click to collapse
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
ChongoDroid said:
If you get it working I could try my hand for the sailfish
Click to expand...
Click to collapse
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.
cm11noob10 said:
The main problem that I seem to be coming across in building for marlin is that the CypherOS tree is out of date and bringing it up to date causes several errors. I still haven't gotten past the kernel header error.
Sailfish shouldn't be much different from marlin seeing how they share several build similarities. If at all possible, try getting it to build sailfish. I'm curious if we get the same errors.
Click to expand...
Click to collapse
I'll give it a try tonight when I can, and see if I get anywhere. Would be nice to at least get the music detection working somehow.
U may need to use a newer kernel tree to compile I did but I also had to update toolchain its what I did
cm11noob10 said:
Already installed and up to date. I think it might be a makefile error. Going to check those and see if it is.
Click to expand...
Click to collapse
Have you been able to get it compile and boot?
Zehlek said:
Have you been able to get it compile and boot?
Click to expand...
Click to collapse
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.
cm11noob10 said:
I have not gotten it to finish compiling yet. Still having trouble with the kernel. Will try to use a newer kernel tree, but am unsure how to update the toolchain.
Click to expand...
Click to collapse
Maybe you and @joeeboogz can work together. It would be an awesome rom
U have to update toolchain to ur computer then compile and add zip to tree then add toolchain line to board config I think I forgot which file to edit
Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.
YTSec said:
Tried again all day, having issues after selecting "lunch" and 10 for aoscp_marlin. It shows it's unable to locate aoscp_marlin.mk I did everything I can think of (and find) to try to fix that, with no luck. This is the first time I have attempted anything like this, so I'm probably doing something wrong. Hopefully someone more experienced comes along and can get it working, I'd love to use this ROM.
Click to expand...
Click to collapse
do you have aoscp.mk in your device tree?
i came across this tread because i want to use a prebuilt kernel and im getting the error "ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/sixohtew/bliss/out/target/product/taimen/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it" and saw someone had a previous error.. im trying to build for taimen obv which is the pixel 2 xl and it has an aosp prebuilt kernel and my rom wont compile any other kernels so i was looking for some help
i'm building lineage OS 16 for moto g5 cedric, so and now i get this failure:
Code:
glob kernel/motorola/msm8937/include/**/*
ninja: error: 'prebuilts/lineage-sdk/api/9.txt', needed by '/media/.../AndroidSource/lineage16/out/target/common/obj/PACKAGING/checkpublicapi-lineage-last-timestamp', missing and no known rule to make it
20:38:36 ninja failed with: exit status 1
I have no folder in prebuilts with the name "lineage-sdk" , I have only a folder "sdk" but in this api folder is missing 9.txt too there are only a 9.xml.
I hope anyone help me.
Always search github.com
I presume you are missing this repo
https://github.com/LineageOS/android_prebuilts_lineage-sdk
git clone it to android/prebuilts/lineage-sdk
TheFixItMan said:
Always search github.com
I presume you are missing this repo
https://github.com/LineageOS/android_prebuilts_lineage-sdk
git clone it to android/prebuilts/lineage-sdk
Click to expand...
Click to collapse
Thanks, i don't can check them now, but i think that is the solution, why is https://github.com/LineageOS/android_prebuilts_lineage-sdk not in the source of lineage or have i made a failure by downloading the source?
lucki1000 said:
Thanks, i don't can check them now, but i think that is the solution, why is https://github.com/LineageOS/android_prebuilts_lineage-sdk not in the source of lineage or have i made a failure by downloading the source?
Click to expand...
Click to collapse
I've no idea - I've not build it
You can always do a
repo sync --force-sync
To force overwrite any changes or to download any repos that didn't download due to an error etc
TheFixItMan said:
I've no idea - I've not build it
You can always do a
repo sync --force-sync
To force overwrite any changes or to download any repos that didn't download due to an error etc
Click to expand...
Click to collapse
Okay now I have this:
Code:
error: frameworks/base/libs/hwui/Android.bp:1:1: "hwui_defaults" depends on undefined module "skia_deps"
Thanks for any help.
lucki1000 said:
Okay now I have this:
Code:
error: frameworks/base/libs/hwui/Android.bp:1:1: "hwui_defaults" depends on undefined module "skia_deps"
Thanks for any help.
Click to expand...
Click to collapse
I don't build roms but I'd check your android sdk and build environment
This is what it's referring to but I'm not the person to help you set up a build environment
https://android.googlesource.com/platform/frameworks/base/+/master/libs/hwui/Android.bp
lucki1000 said:
Okay now I have this:
Code:
error: frameworks/base/libs/hwui/Android.bp:1:1: "hwui_defaults" depends on undefined module "skia_deps"
Thanks for any help.
Click to expand...
Click to collapse
Brother, How did you solve this problem "undefined module skia_deps"?
@lucki1000
Hello. I have stumbled upon this too. Here's the link with the fix on xda:
https://forum.xda-developers.com/lineage/help/lineageos-16-0-mka-command-error-t4099789
I have that doubt, until today there is no ROM that can be installed on the J2 which includes Android 7 or at least one Android 6 ROM that is based on AOSP?
Right now, there isn't any AOSP or Nougat-based ROM for the j2lte. Tomorrow, who knows?
TBM 13 said:
Right now, there isn't any AOSP or Nougat-based ROM for the j2lte. Tomorrow, who knows?
Click to expand...
Click to collapse
but I wonder why the other model of the J2, the 3G if it has several roms based on Android AOSP or based on Android 7.1.2 if both have the same processor, greatly changes the shape of its code to make it impossible to use with the J2LTE ?
SharkyBeAre said:
but I wonder why the other model of the J2, the 3G if it has several roms based on Android AOSP or based on Android 7.1.2 if both have the same processor, greatly changes the shape of its code to make it impossible to use with the J2LTE ?
Click to expand...
Click to collapse
You mean the J200H? It has a completly different processor.
TBM 13 said:
You mean the J200H? It has a completly different processor.
Click to expand...
Click to collapse
CPU-Z is my phone (J200M) <J2LTE> and the other screenshot is information taken from the internet that says that the J200H has the same processor as the J200M - J2LTE. Who is lying, Cpu-z or the page where I consulted the information
This is another page that says the J200H has the Exynos 3475.
https://www.sammobile.com/samsung/galaxy-j2/specs/SM-J200H/
More Screenshots of my J2LTE
SharkyBeAre said:
This is another page that says the J200H has the Exynos 3475.
https://www.sammobile.com/samsung/galaxy-j2/specs/SM-J200H/
Click to expand...
Click to collapse
Take a look to this, from https://forum.xda-developers.com/galaxy-j2/development/lineageos-samsung-galaxy-j2-t3659657
Will it work on j200g/gu/BT/F??
Naah.. It won't boot as j200h is sprd but others are ****ty Exynos
Click to expand...
Click to collapse
SharkyBeAre said:
More Screenshots of my J2LTE
Click to expand...
Click to collapse
TBM 13 said:
Take a look to this, from https://forum.xda-developers.com/galaxy-j2/development/lineageos-samsung-galaxy-j2-t3659657
Click to expand...
Click to collapse
Its actually only J200H/DD that is based on spreadtrum SC8830. J200H and J200H/DS is Exynos-based.
afaik, J200H/DD is only sold in some countries like India or here at Vietnam. The rest is available worldwide and therefore more recognizable by most people.
e: further info, codename for J200H/DD (Spreadtrum) is j23gdd, whilst J200H(/DS) (Exynos) is j23gxx.
e2: I can always try to build blindly, considering on5 pro (on5prolte / same Exynos chipset) has Lineage fully functional.
But, *also* considering the lack of time and the mess of J2 Prime RIL I'm making, I cannot guarantee a fully functional one here :<
Prove N. said:
e2: I can always try to build blindly, considering on5 pro (on5prolte / same Exynos chipset) has Lineage fully functional.
But, *also* considering the lack of time and the mess of J2 Prime RIL I'm making, I cannot guarantee a fully functional one here :<
Click to expand...
Click to collapse
Exynos3475 developers already tried. They never managed to get to the boot animation and make logcats work. When they tried the same j2 tree on the on5prolte, it booted without problems.
Basically, the o5prolte got LOS 14.1 with the j2lte device tree.
I managed to get working logs and boot animation in los 14.1 by replacing the init binary with marshmallow one, from the J1XLTE and doing some init.rc fixes
The problem is that zygote crashes.
If i don't replace the init binary, adb detects the device but if i try to do adb shell or adb logcat, i get this:
Exec '/system/bin/sh' failed: No such file or directory (2)
J1XLTE (J1 2016) seems to have the exact same problem. I'm currently working with a developer of that device, because if it boots on it, it boots on ours, and visce versa.
Somehow it isn't able to mount the system partition.
Now, i'm trying LOS 13. It already got more far than LOS 14.1 (i still need to replace the init binary and do some modifications to init.rc). Sensors service seems to be crashing, and there is no boot animation, just black screen.
Prove N. said:
Its actually only J200H/DD that is based on spreadtrum SC8830. J200H and J200H/DS is Exynos-based.
afaik, J200H/DD is only sold in some countries like India or here at Vietnam. The rest is available worldwide and therefore more recognizable by most people.
e: further info, codename for J200H/DD (Spreadtrum) is j23gdd, whilst J200H(/DS) (Exynos) is j23gxx.
e2: I can always try to build blindly, considering on5 pro (on5prolte / same Exynos chipset) has Lineage fully functional.
But, *also* considering the lack of time and the mess of J2 Prime RIL I'm making, I cannot guarantee a fully functional one here :<
Click to expand...
Click to collapse
TBM 13 said:
Exynos3475 developers already tried. They never managed to get to the boot animation and make logcats work. When they tried the same j2 tree on the on5prolte, it booted without problems.
Basically, the o5prolte got LOS 14.1 with the j2lte device tree.
I managed to get working logs and boot animation in los 14.1 by replacing the init binary with marshmallow one, from the J1XLTE and doing some init.rc fixes
The problem is that zygote crashes.
If i don't replace the init binary, adb detects the device but if i try to do adb shell or adb logcat, i get this:
Exec '/system/bin/sh' failed: No such file or directory (2)
J1XLTE (J1 2016) seems to have the exact same problem. I'm currently working with a developer of that device, because if it boots on it, it boots on ours, and visce versa.
Somehow it isn't able to mount the system partition.
Now, i'm trying LOS 13. It already got more far than LOS 14.1 (i still need to replace the init binary and do some modifications to init.rc). Sensors service seems to be crashing, and there is no boot animation, just black screen.
Click to expand...
Click to collapse
than? Does that mean they are trying to work on a LOS Custom Rom for the J2LTE? Forgive me that you don't understand your communication language in front of cell phones, but what I understand is that you are working to get AOSP in J2LTE?
SharkyBeAre said:
than? Does that mean they are trying to work on a LOS Custom Rom for the J2LTE?
Click to expand...
Click to collapse
No, they gave up.
SharkyBeAre said:
you are working to get AOSP in J2LTE?
Click to expand...
Click to collapse
I'm trying, but don't expect something, i'm noob at this.
TBM 13 said:
No, they gave up.
I'm trying, but don't expect something, i'm noob at this.
Click to expand...
Click to collapse
I trust that something good will come out of all the tests you can do being a noob, hopefully, because Samsung's system seems to me the worst, and it takes up a lot of space.
Thanks for all
TBM 13 said:
Exynos3475 developers already tried. They never managed to get to the boot animation and make logcats work. When they tried the same j2 tree on the on5prolte, it booted without problems.
Basically, the o5prolte got LOS 14.1 with the j2lte device tree.
I managed to get working logs and boot animation in los 14.1 by replacing the init binary with marshmallow one, from the J1XLTE and doing some init.rc fixes
The problem is that zygote crashes.
If i don't replace the init binary, adb detects the device but if i try to do adb shell or adb logcat, i get this:
Exec '/system/bin/sh' failed: No such file or directory (2)
J1XLTE (J1 2016) seems to have the exact same problem. I'm currently working with a developer of that device, because if it boots on it, it boots on ours, and visce versa.
Somehow it isn't able to mount the system partition.
Now, i'm trying LOS 13. It already got more far than LOS 14.1 (i still need to replace the init binary and do some modifications to init.rc). Sensors service seems to be crashing, and there is no boot animation, just black screen.
Click to expand...
Click to collapse
That is quite weird? are you sure about the partition layout, compatibility of blobs and some stuff and things?
is system defined correctly in fstab? Is its permissions defined correctly in ueventd?
I see that it is common-ized (and stripped down) in exynos3475-common which might be the cause, as j23gxx/j2lte is 1-year older than on5. Have you tried using stock fstab and ueventd for the ROM? (assuming you are building from source)
e:
afaik/if im not wrong: the dev has only On5 T-Mobile, which should explains why only that device tree (on5ltetmo) is well-configured and why the generic on5prolte is empty.
And, I cant seem to find On5 Pro tree (its ROM is on XDA), so I guess its just a port.
Prove N. said:
That is quite weird? are you sure about the partition layout, compatibility of blobs and some stuff and things?
is system defined correctly in fstab? Is its permissions defined correctly in ueventd?
I see that it is common-ized (and stripped down) in exynos3475-common which might be the cause, as j23gxx/j2lte is 1-year older than on5. Have you tried using stock fstab and ueventd for the ROM? (assuming you are building from source)
e:
afaik/if im not wrong: the dev has only On5 T-Mobile, which should explains why only that device tree (on5ltetmo) is well-configured and why the generic on5prolte is empty.
And, I cant seem to find On5 Pro tree (its ROM is on XDA), so I guess its just a port.
Click to expand...
Click to collapse
Actually, the good device tree is the on5prolte one, cm-14.1-20180513 branch (https://github.com/Exynos3475/android_device_samsung_o5prolte/tree/cm-14.1-20180513) (you can even see Device configuration for the Samsung Galaxy J2 (j2lte) WIP for now in the README.md )
The fstab is working fine, i managed to build TWRP from CM-14.1 source, and it uses the same fstab. TWRP works fine, except for MTP but that is probably because i'm using the nougat kernel.
No, i didn't tried the stock ueventd, but i don't see how that will change something, because the problem is on the init binary itself.
Also, the main j2lte developer (Izzy) has the J2.
TBM 13 said:
Actually, the good device tree is the on5prolte one, cm-14.1-20180513 branch (https://github.com/Exynos3475/android_device_samsung_o5prolte/tree/cm-14.1-20180513) (you can even see Device configuration for the Samsung Galaxy J2 (j2lte) WIP for now in the README.md )
The fstab is working fine, i managed to build TWRP from CM-14.1 source, and it uses the same fstab. TWRP works fine, except for MTP but that is probably because i'm using the nougat kernel.
No, i didn't tried the stock ueventd, but i don't see how that will change something, because the problem is on the init binary itself.
Also, the main j2lte developer (Izzy) has the J2.
Click to expand...
Click to collapse
I did not check the branches .
https://github.com/Exynos3475/android_device_samsung_o5prolte/blob/cm-14.1-20180513/BoardConfig.mk
Is it okey with kernel built with this?
Code:
TARGET_KERNEL_CONFIG := lineage-o5lteswa_defconfig
Prove N. said:
I did not check the branches .
https://github.com/Exynos3475/android_device_samsung_o5prolte/blob/cm-14.1-20180513/BoardConfig.mk
Is it okey with kernel built with this?
Click to expand...
Click to collapse
Maybe they share the defconfig
TBM 13 said:
Maybe they share the ramdisk
Click to expand...
Click to collapse
No. I meant, isnt kernel defconfig defines lots of things (including hardware/software and features of that one phone)?
Is it even possible to use defconfig of other device and it still works?
Prove N. said:
Is it even possible to use defconfig of other device and it still works?
Click to expand...
Click to collapse
If the device is very similar, why not?
---------- Post added at 17:53 ---------- Previous post was at 17:51 ----------
Prove N. said:
Is it even possible to use defconfig of other device and it still works?
Click to expand...
Click to collapse
If the device is very similar, why not?
TBM 13 said:
Maybe they share the ramdisk
Click to expand...
Click to collapse
I accidentally typed ramdisk instead of defconfig lol
TBM 13 said:
If the device is very similar, why not?
Click to expand...
Click to collapse
only with the SoC i guess. I thought On5 has 2GB RAM and J2 has 1, for example. Who knows about driver differences too~
Hey all,
I was trying to watch beacon frames transmitted by my access point, but had no capable hardware in my house to sniff it. Or did I?
Turns out, Pixel 6 / Pixel 6 Pro can do it. Here's my howto.
Getting the BCM4389 in Pixel 6 into monitor mode for tcpdump/Wireshark WIFI sniffing
A little side project to debug a WIFI 6E TP-Link mesh network in my house, went from "This sounds easy!" to "This is impossible!" to "It can...
chrisf4.blogspot.com
Short answer: Flash an aosp_raven-userdebug build from Google, then use wifi_sniffer and some related system properties to configure frequency and bandwidth, and enable monitor mode using a special firmware that is shipped in the userdebug build. Then, use tcpdump on the newly created radiotap0 interface.
Enjoy,
Chris
Is there any real difference from doing it this way?
GitHub - kimocoder/qualcomm_android_monitor_mode: Qualcomm QCACLD WiFi monitor mode for Android
Qualcomm QCACLD WiFi monitor mode for Android. Contribute to kimocoder/qualcomm_android_monitor_mode development by creating an account on GitHub.
github.com
x56x said:
Is there any real difference from doing it this way?
GitHub - kimocoder/qualcomm_android_monitor_mode: Qualcomm QCACLD WiFi monitor mode for Android
Qualcomm QCACLD WiFi monitor mode for Android. Contribute to kimocoder/qualcomm_android_monitor_mode development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Hi x56x, a dependency for that is "3. WiFi chipset that actually uses the QCACLD driver/firmware."
Since Pixel 6 uses a Broadcom WIFI chip and not Qualcomm, you would need my directions for Pixel 6 and 6 Pro.
-Chris
ccfries said:
Hi x56x, a dependency for that is "3. WiFi chipset that actually uses the QCACLD driver/firmware."
Since Pixel 6 uses a Broadcom WIFI chip and not Qualcomm, you would need my directions for Pixel 6 and 6 Pro.
-Chris
Click to expand...
Click to collapse
I actually used these commands for qualcomm on a rooted stock A12 P6P and it worked flawlessly. Never got a chance to mess around with packet sniffing. I am curious as to how you found this? Maybe someone can take a deeper look at the firmware and start working on packet injection.
x56x said:
I actually used these commands for qualcomm on a rooted stock A12 P6P and it worked flawlessly. Never got a chance to mess around with packet sniffing. I am curious as to how you found this? Maybe someone can take a deeper look at the firmware and start working on packet injection.
Click to expand...
Click to collapse
I don't think it could work
raven:/ # ls -l /sys/module/wlan/parameters/con_mode
ls: /sys/module/wlan/parameters/con_mode: No such file or directory
Are you on Android 12, 12.1, or 13? I got it to work on 12 when the phone first came out, so something had to have changed.
I worked on Pixel 6 kernel software and this didn't change..
Just to be sure, you can sniff WIFI packets that the kernel sees, without any changes and just root, using tcpdump. If you want to see other traffic that the WIFI chip would normally filter out, you need monitor mode and you need to load this separate firmware to get into monitor mode.
I pulled the wifi sniffer binary, firmware and .rc files needed to get monitor mode working and packed them into a magisk module. you can find it here on my github
GitHub - Biohazardousrom/nh-magisk-wifi-firmware-gs101-gs201: This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter.
This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter. - GitHub - Biohazardousrom/nh-magisk-wifi-firmware-gs101-gs201: This Magisk module adds the r...
github.com
Duhjoker said:
I pulled the wifi sniffer binary, firmware and .rc files needed to get monitor mode working and packed them into a magisk module. you can find it here on my github
GitHub - Biohazardousrom/nh-magisk-wifi-firmware-gs101-gs201: This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter.
This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter. - GitHub - Biohazardousrom/nh-magisk-wifi-firmware-gs101-gs201: This Magisk module adds the r...
github.com
Click to expand...
Click to collapse
Tried to install today, Didnt see a Release on the Github page, tried to manually compile the magisk module and just get error "Failed to unzip" in magisk. Any ideas? Thanks regardless, been searching up and down for the Wifi_Sniffer binary
try this zip. github is weird sometimes with magisk modules source when you download it.
as for the binaries and the firmware they are located in the system/vendor folder in the zip
Duhjoker said:
try this zip. github is weird sometimes with magisk modules source when you download it.
as for the binaries and the firmware they are located in the system/vendor folder in the zip
Click to expand...
Click to collapse
WORKS PERFECT, THANKS A MILLION!!!!
raven(bear)claws said:
WORKS PERFECT, THANKS A MILLION!!!!
Click to expand...
Click to collapse
on a side note, i am getting "permission denied" while trying to run "wifi_sniffer start". on a rooted pixel 6 pro, factory image but have ro.userdebugging enabled. adb sees the process just does not have access to view it. Could be my goof since i am not using userdebug build
go to data/adb/modules look for the module and go to system/vendor/bin and change the permissions with
chmod a+x wifi_sniffer
chmod a+x wifi_perf_diag
i guess i need to fix that somehow
Duhjoker said:
go to data/adb/modules look for the module and go to system/vendor/bin and change the permissions with
chmod a+x wifi_sniffer
chmod a+x wifi_perf_diag
i guess i need to fix that somehow
Click to expand...
Click to collapse
It starts now!! time for me to fiddle with this "Unable to open /sys/wifi/firmware_path, Failed to up radiotap0" error, surely i made a mistake.
i havent had much time to play with it. i was really hoping someone could figure it out and recount thier steps here.
i noticed some sepolicy stuff reguarding wifi_sniffer while building a few roms for pixel 7, theres an incomplete package to build it. right now adding the package to the device trees to build enables the sepolicy for it but thats it. we may not be able to use them with out using a beta preview until android 14 is released. thats speculation though, cause i dont know.
but please anyone that gets this working please share your steps
Duhjoker said:
i havent had much time to play with it. i was really hoping someone could figure it out and recount thier steps here.
i noticed some sepolicy stuff reguarding wifi_sniffer while building a few roms for pixel 7, theres an incomplete package to build it. right now adding the package to the device trees to build enables the sepolicy for it but thats it. we may not be able to use them with out using a beta preview until android 14 is released. thats speculation though, cause i dont know.
but please anyone that gets this working please share your steps
Click to expand...
Click to collapse
I actually got useful help from ChatGPT. dmesg has an output of [wlan] wl_cfg80211_alert ←[0m: In : error alert eventing, reason=0x6, which indicated firmware corruption. Will start looking at the firmware file its self momentarily.
This is how i get wifi_sniffer to work. first download and install the nethunter firmware magisk module. check permissions of the binaries.
next reboot your device and disable wifi and data. This must be done in order to restart the wlan in monitor mode
now open terminal emulator and either type or copy and paste the commands below
in su shell
Code:
su
# Set bandwidth to 160 MHz for sniffing on 2.4 GHz
Code:
setprop persist.vendor.wifi.sniffer.bandwidth 160
# Set 2.4GHz band
Code:
setprop persist.vendor.wifi.sniffer.freq 2412
# start wifi sniffer
Code:
wifi_sniffer start
#tcp dump to .pcap file
Code:
tcpdump -i radiotap0 type mgt subtype beacon -w /data/beacon-capture.pcap