******************* AUTOREPLY *****************************
Vielen Dank fr Ihre Nachricht. Ich bin bis einschlielich 28.10.2023 im Urlaub. Whrend dieser Zeit bin ich per E-Mail erreichbar. Bitte haben Sie Verstndnis, wenn ich erst nach dem Urlaub antworte. Im Notfall bitte ich Sie unter der Telefonnummer 05823/953997-0 anzurufen. Herzlichen Dank! Elena Richter ____________________ HOPLIT - IT Consulting DESAG-zertifiziert als EU-Datenschutzbeauftragte IT-Security Auditorin (TV) 2020 ID0000043604 Uferstrae 8, 29553 Bienenbttel Tel: 05823/953997-4 Mobil: 01590-2211786 FAX: 05823/953997-9 Web: http://www.hoplit.de e-Mail: richter.el...@hoplit.de Unsere Hinweise zum Datenschutz finden Sie hier: https://hoplit.com/wir/impressum.php#mail Send Replicant mailing list submissions to replicant@osuosl.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.osuosl.org/mailman/listinfo/replicant or, via email, send a message with subject or body 'help' to replicant-requ...@osuosl.org You can reach the person managing the list at replicant-ow...@osuosl.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Replicant digest..." Today's Topics: 1. Re: Failed attempt at tcpdump/wireshark/tshark sniffing usb modem on i9305 (report) (J05HYYY) 2. Re: Replicant Digest, Vol 467, Issue 1 about cpu's (p db) ---------------------------------------------------------------------- Message: 1 Date: Sun, 15 Oct 2023 20:57:11 +0100 From: J05HYYY <lovell.josh...@gmail.com> To: replicant@osuosl.org Subject: Re: [Replicant] Failed attempt at tcpdump/wireshark/tshark sniffing usb modem on i9305 (report) Message-ID: <20231015205711.5e1da0f4@devuan> Content-Type: text/plain; charset=US-ASCII Note: I got the same result (that I was unable to sniff the modem) when I set selinux "setenforce 0" before repeating the steps. Josh ------------------------------ Message: 2 Date: Tue, 17 Oct 2023 14:32:31 +0200 From: p db <id3r...@gmail.com> To: replicant@osuosl.org Subject: Re: [Replicant] Replicant Digest, Vol 467, Issue 1 about cpu's Message-ID: <cam_1ou6xebcxeokaguhk7+knmoknyxcxncmxilbtgl26o3r...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" these are the cpu's of Samsung: https://en.wikichip.org/wiki/samsung/exynos/4412?utm_content=cmp-true Exynos 4412 General Info Designer Samsung <https://en.wikichip.org/wiki/Samsung>, ARM Holdings <https://en.wikichip.org/wiki/ARM_Holdings> Manufacturer Samsung <https://en.wikichip.org/wiki/Samsung> Model Number 4412 Market Mobile Introduction April, 2012 (announced) May, 2012 (launched) General Specs Family Exynos <https://en.wikichip.org/wiki/samsung/exynos> Series Exynos 4 Frequency 1,600 MHz Microarchitecture ISA ARMv7 (ARM) Microarchitecture Cortex-A9 <https://en.wikichip.org/w/index.php?title=samsung/microarchitectures/cortex-a9&action=edit&redlink=1> Process 32 nm <https://en.wikichip.org/wiki/32_nm_process> Technology HKMG Word Size 32 bit Cores 4 Threads 4 Multiprocessing Max SMP 1-Way (Uniprocessor) Facts about "Exynos 4412 - Samsung <https://en.wikichip.org/wiki/Special:Browse/:samsung-2Fexynos-2F4412>" RDF feed <https://en.wikichip.org/wiki/Special:ExportRDF/samsung/exynos/4412> base frequency <https://en.wikichip.org/wiki/Property:base_frequency> 1,600 MHz (1.6 GHz, 1,600,000 kHz) + <https://en.wikichip.org/wiki/Special:SearchByProperty/:base-20frequency/1600-20MHz> core count <https://en.wikichip.org/wiki/Property:core_count> 4 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:core-20count/4> designer <https://en.wikichip.org/wiki/Property:designer> Samsung + <https://en.wikichip.org/wiki/Special:SearchByProperty/:designer/Samsung> and ARM Holdings + <https://en.wikichip.org/wiki/Special:SearchByProperty/:designer/ARM-20Holdings> family <https://en.wikichip.org/wiki/Property:family> Exynos + <https://en.wikichip.org/wiki/Special:SearchByProperty/:family/Exynos> first announced <https://en.wikichip.org/wiki/Property:first_announced> April 2012 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:first-20announced/April-202012> first launched <https://en.wikichip.org/wiki/Property:first_launched> May 2012 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:first-20launched/May-202012> full page name <https://en.wikichip.org/wiki/Property:full_page_name> samsung/exynos/4412 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:full-20page-20name/samsung-2Fexynos-2F4412> instance of <https://en.wikichip.org/wiki/Property:instance_of> microprocessor + <https://en.wikichip.org/wiki/Special:SearchByProperty/:instance-20of/microprocessor> isa <https://en.wikichip.org/wiki/Property:isa> ARMv7 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:isa/ARMv7> isa family <https://en.wikichip.org/wiki/Property:isa_family> ARM + <https://en.wikichip.org/wiki/Special:SearchByProperty/:isa-20family/ARM> ldate <https://en.wikichip.org/wiki/Property:ldate> May 2012 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:ldate/May-202012> manufacturer <https://en.wikichip.org/wiki/Property:manufacturer> Samsung + <https://en.wikichip.org/wiki/Special:SearchByProperty/:manufacturer/Samsung> market segment <https://en.wikichip.org/wiki/Property:market_segment> Mobile + <https://en.wikichip.org/wiki/Special:SearchByProperty/:market-20segment/Mobile> max cpu count <https://en.wikichip.org/wiki/Property:max_cpu_count> 1 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:max-20cpu-20count/1> microarchitecture <https://en.wikichip.org/wiki/Property:microarchitecture> Cortex-A9 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:microarchitecture/Cortex-2DA9> model number <https://en.wikichip.org/wiki/Property:model_number> 4412 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:model-20number/4412> name <https://en.wikichip.org/wiki/Property:name> Exynos 4412 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:name/Exynos-204412> process <https://en.wikichip.org/wiki/Property:process> 32 nm (0.032 ?m, 3.2e-5 mm) + <https://en.wikichip.org/wiki/Special:SearchByProperty/:process/32-20nm> series <https://en.wikichip.org/wiki/Property:series> Exynos 4 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:series/Exynos-204> smp max ways <https://en.wikichip.org/w/index.php?title=Property:smp_max_ways&action=edit&redlink=1> 1 <https://en.wikichip.org/w/index.php?title=1&action=edit&redlink=1> + <https://en.wikichip.org/wiki/Special:SearchByProperty/:smp-20max-20ways/1> thread count <https://en.wikichip.org/wiki/Property:thread_count> 4 + <https://en.wikichip.org/wiki/Special:SearchByProperty/:thread-20count/4> word size <https://en.wikichip.org/wiki/Property:word_size> 32 bit (4 octets, 8 nibbles) + <https://en.wikichip.org/wiki/Special:SearchByProperty/:word-20size/32-20bit> Others SOC's: Exynos 3 https://en.wikichip.org/wiki/samsung/exynos#Exynos_3 Exynos 4 https://en.wikichip.org/wiki/samsung/exynos#Exynos_4 Exynos 5 https://en.wikichip.org/wiki/samsung/exynos#Exynos_5 There is not on the website https://en.wikichip.org/wiki/samsung/exynos#Exynos_3 the pubblicazione of the Exynos 6, so from Exynos 5 people migrate to Exynos 7 !!! Exynos 7 https://en.wikichip.org/wiki/samsung/exynos#Exynos_7 Exynos 8 https://en.wikichip.org/wiki/samsung/exynos#Exynos_8 Exynos 9 https://en.wikichip.org/wiki/samsung/exynos#Exynos_9 I hope that these informations, can help you in any way. Best Regards Paolo Del Bene [17bdP] Il Gio 12 Ott 2023, 22:54 <replicant-requ...@osuosl.org> ha scritto: > Send Replicant mailing list submissions to > replicant@osuosl.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osuosl.org/mailman/listinfo/replicant > or, via email, send a message with subject or body 'help' to > replicant-requ...@osuosl.org > > You can reach the person managing the list at > replicant-ow...@osuosl.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Replicant digest..." > > > Today's Topics: > > 1. [libsamsung-ipc] [PATCH 1/2] configure.ac: fix typo with > code_coverage_tests variable (Denis 'GNUtoo' Carikli) > 2. [libsamsung-ipc]: Autotools typo and copy/paste fixes > (Denis 'GNUtoo' Carikli) > 3. [libsamsung-ipc] [PATCH 2/2] configure.ac: fix lcov detection > (Denis 'GNUtoo' Carikli) > 4. Re: PROBING AUDIO LINES USING i9305. RESULTS. (J05HYYY) > 5. Re: [libsamsung-ipc]: Autotools typo and copy/paste fixes > (Denis 'GNUtoo' Carikli) > 6. ADB Problem (Eren Kaplan) > 7. Failed attempt at tcpdump/wireshark/tshark sniffing usb modem > on i9305 (report) (J05HYYY) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 22 Sep 2023 03:17:37 +0200 > From: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > To: replicant@osuosl.org > Cc: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > Subject: [Replicant] [libsamsung-ipc] [PATCH 1/2] configure.ac: fix > typo with code_coverage_tests variable > Message-ID: <20230922011813.19861-2-gnu...@cyberdimension.org> > > Signed-off-by: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > --- > configure.ac | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/configure.ac b/configure.ac > index 2c24e89..64d6e2b 100644 > --- a/configure.ac > +++ b/configure.ac > AC_ARG_ENABLE( > > AM_CONDITIONAL( [WANT_CODE_COVERAGE], [test x"$code_coverage_tests" = > x"yes"]) > > -AS_IF([test x"code_coverage_tests" = x"yes"], > +AS_IF([test x"$code_coverage_tests" = x"yes"], > [AC_CHECK_PROG([CODE_COVERAGE], [lcov], [lcov]) > AS_IF( > [test x"$VALGRIND" = x""], > -- > 2.41.0 > > > > ------------------------------ > > Message: 2 > Date: Fri, 22 Sep 2023 03:17:36 +0200 > From: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > To: replicant@osuosl.org > Subject: [Replicant] [libsamsung-ipc]: Autotools typo and copy/paste > fixes > Message-ID: <20230922011813.19861-1-gnu...@cyberdimension.org> > > Hi, > > Here are two fixes for typos/copy-paste error. They were also fixing > the same code that was merged by accident. > > In addition to the patches that will follow in a response to > this mail, here's an URL to the see the patches in a web interface: > > https://git.replicant.us/contrib/GNUtoo/hardware_replicant_libsamsung-ipc/commit/?id=81a412cb235a4fd1e769f2275ee3e30cec7b46db > > And here's how to get them in a git repository: > git clone > https://git.replicant.us/GNUtoo/hardware_replicant_libsamsung-ipc > cd hardware_replicant_libsamsung-ipc > git show 81a412cb235a4fd1e769f2275ee3e30cec7b46db > > Denis. > > > ------------------------------ > > Message: 3 > Date: Fri, 22 Sep 2023 03:17:38 +0200 > From: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > To: replicant@osuosl.org > Cc: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > Subject: [Replicant] [libsamsung-ipc] [PATCH 2/2] configure.ac: fix > lcov detection > Message-ID: <20230922011813.19861-3-gnu...@cyberdimension.org> > > Signed-off-by: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > --- > configure.ac | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/configure.ac b/configure.ac > index 64d6e2b..501a386 100644 > --- a/configure.ac > +++ b/configure.ac > AM_CONDITIONAL( [WANT_CODE_COVERAGE], [test > x"$code_coverage_tests" = x"yes"]) > AS_IF([test x"$code_coverage_tests" = x"yes"], > [AC_CHECK_PROG([CODE_COVERAGE], [lcov], [lcov]) > AS_IF( > - [test x"$VALGRIND" = x""], > + [test x"$CODE_COVERAGE" = x""], > [AC_MSG_ERROR( > [code coverage tests are enabled but lcov was not found in PATH > ($PATH)])])]) > > -- > 2.41.0 > > > > ------------------------------ > > Message: 4 > Date: Fri, 22 Sep 2023 17:01:47 +0100 > From: J05HYYY <lovell.josh...@gmail.com> > To: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > Cc: J05HYYY via Replicant <replicant@osuosl.org> > Subject: Re: [Replicant] PROBING AUDIO LINES USING i9305. RESULTS. > Message-ID: <20230922170147.402db...@gmail.com> > Content-Type: text/plain; charset=US-ASCII > > On Thu, 21 Sep 2023 17:40:26 +0200 > Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> wrote: > > > On Wed, 20 Sep 2023 18:22:56 +0100 > > J05HYYY via Replicant <replicant@osuosl.org> wrote: > > > > > I then installed scintill's version of Replicant 6, dialled a call > > > and ran set_control_values. Unfortunately I did not get audio. Here > > > is the output. > > Do you also have tcpdump or tshark on the device? > > > > If I recall well the modem is USB, so maybe an option would be to try > > to see if there is a difference between Replicant and LineageOS with > > what is being sent to the modem to make a call or during the call. > > Hi Denis, I will try my best and and do this, but can't guarantee if / > or when it'll get done (I have limited time and a lot to get seen to) > ... Will report back here if/when there is any progression. Cheers, > > Josh > > > > > If I remember well, devices that use libsamsung-ipc, > > libsamsung-ipc/libsamsung-ril sends an extra command to the modem to > > make it send its audio. > > > > Without it you would correctly route the audio with ALSA but nothing > > would arrive. > > > > Denis. > > > > ------------------------------ > > Message: 5 > Date: Mon, 2 Oct 2023 00:25:18 +0200 > From: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > To: Denis 'GNUtoo' Carikli via Replicant <replicant@osuosl.org> > Cc: Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> > Subject: Re: [Replicant] [libsamsung-ipc]: Autotools typo and > copy/paste fixes > Message-ID: <20231002002518.42577c75@primary_laptop> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > I've pushed this patch serie. > > Denis. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 833 bytes > Desc: OpenPGP digital signature > URL: < > http://lists.osuosl.org/pipermail/replicant/attachments/20231002/bc96f51d/attachment-0001.asc > > > > ------------------------------ > > Message: 6 > Date: Sat, 9 Sep 2023 13:50:38 +0300 > From: Eren Kaplan <ek.xcodeproj...@gmail.com> > To: replicant@osuosl.org > Subject: [Replicant] ADB Problem > Message-ID: > <CAAhPxVb76_uGZhDboHs0k0rXF36UEXummpR3ENE+Zhw7hi8= > a...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello. I did a successful installation on my N7000. adb did not work in > recovery mode, I installed via sdcard. When I got to the main screen, it > was very delayed, so I looked at this guide ( > https://redmine.replicant.us/projects/replicant/wiki/Graphics). When I > connected my phone via USB (Macbook Air 2017) it did not pair with adb. I > tried setting root access to adb and apps, android debbugging on, usb > settings to ptp, mtp and charging, none of them worked. Is there anything > extra I need to do or I'm starting to think it's a hardware problem. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.osuosl.org/pipermail/replicant/attachments/20230909/a2a7fe5b/attachment-0001.html > > > > ------------------------------ > > Message: 7 > Date: Thu, 12 Oct 2023 21:54:00 +0100 > From: J05HYYY <lovell.josh...@gmail.com> > To: replicant@osuosl.org > Subject: [Replicant] Failed attempt at tcpdump/wireshark/tshark > sniffing usb modem on i9305 (report) > Message-ID: <20231012215400.6a5e5...@gmail.com> > Content-Type: text/plain; charset=US-ASCII > > I run > sudo adb root > > I compile tcpdump for android (it turns out is not needed on Replicant 6 > as tcpdump is already included) I push tcpdump to the device using > sudo adb push tcpdump-4.99.4/tcpdump /data/local/tcpdump > You will notice the version I used. This was the last version I could > successfully compile (but not run) When I run my compiled version of > tcpdump I get error: only position independent executables (PIE) are > supported. > > I run (in "adb shell"): > lsusb > > I get: > > Bus 001 Device 001: ID 1d6b:0002 > Bus 002 Device 001: ID 1d6b:0001 > Bus 001 Device 002: ID 05c6:904c > > You will see that Bus 001, Device 002 is the usb modem. > > I run: > tcpdump -D > > ... to list devices: > > 1.nfqueue (Linux netfilter queue (NFQUEUE) interface) > 2.usbmon1 (USB bus number 1) > 3.wwan2 > 4.usbmon2 (USB bus number 2) > 5.any (Pseudo-device that captures on all interfaces) > 6.lo > > I incorrectly try usbmon2 because I was reading the device number > instead of the bus number and get listening on usbmon2, link-type > USB_LINUX (USB with Linux header), capture size 65535 bytes and 0 > packets captured > > I then try "usbmon1", like a proper hacker lol. > > tcpdump -i usbmon1 -vvv -XX -s0 -w modem_replicant.pcap > > with tcpdump running I > - dial a call > > for some reason, when sniffing with tcpdump, the call is automatically > answered. Either way I hang up on the calling phone. > > To try and dissect the file on my computer, I use: > > sudo apt-get install tshark wireshark tcpdump > git clone https://github.com/dnlplm/WiresharkQMIDissector > git clone > https://gitlab.freedesktop.org/mobile-broadband/libqmi.git cd > WiresharkQMIDissector python3 generate_lua.py ../libqmi/data/ > tshark -T json -r ../modem_replicant.pcap -X > lua_script:qmi_dissector_gen.lua | tee > modem_replicant_dissected.json > > I grep the json for "qmi" and "QMI" but receive no results. I also > search for the number I dialled and recieve no results. > > I then try wireshark with the GUI because I am actually a novice. > > wireshark -r ../modem_replicant.pcap -X > lua_script:qmi_dissector_gen.lua > > As with tshark, I don't see any qmi fields. > > Regarding "Info" section of wireshark when reading the pcap file with > the lua dissector... There are "GET_STATUS Request" for [Port 1] to > [Port 3] There are "CLEAR FEATURE Request" > There are "CLEAR FEATURE Request [Port 2: C_PORT_SUSPEND]" > There are "GET STATUS Request" > There are "GET_STATUS Response" [Port 1] to [Port 3] > There are "SET FEATURE Request" > There are "SET_FEATURE Response" > There are "SET_FEATURE Request [Port 2: PORT_SUSPEND]" > There are "URB_BULK in" > There are "URB_CONTROL in" > There are "URB_INTERRUPT in" > > The protocols are all either > "USB" > or > "USB HUB" > > The source seems to be either > "host", > "1.1.0", > "1.1.1", > "1.2.0", > "1.2.1", > "1.2.3", > "1.2.8", > "1.2.9" > The destination (likewise) seems to be either > "host", > "1.1.0", > "1.1.1", > "1.2.0", > "1.2.1", > "1.2.3", > "1.2.8", > "1.2.9" > > As I could see no QMI fields in wireshark or tshark, I decided not to > reinstall LineageOS yet and get a tcpdump for that to compare with. I > only try on scintill's branch of replicant 6 so far. > > I could possibly PM you Denis the pcap file but I don't believe it > would be worth it. I may try the pmos thing now less anyone has any > other suggestions. > > Josh > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Replicant mailing list > Replicant@osuosl.org > https://lists.osuosl.org/mailman/listinfo/replicant > > > ------------------------------ > > End of Replicant Digest, Vol 467, Issue 1 > ***************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20231017/9f18433f/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ Replicant mailing list Replicant@osuosl.org https://lists.osuosl.org/mailman/listinfo/replicant ------------------------------ End of Replicant Digest, Vol 468, Issue 1 ***************************************** To: replicant@osuosl.org Reply-To: replicant@osuosl.org
_______________________________________________ Replicant mailing list Replicant@osuosl.org https://lists.osuosl.org/mailman/listinfo/replicant
