Re: [Replicant] i9305: Add support for rt2500usb wifi devices

Hi, Wolfgang Wiedmeyer: > As I understand, this chipset doesn't require firmware to be loaded > as it's already preinstalled. That's correct. > I searched for dongles that have RT2500USB/RT2571 and I had a hard > time finding any that I could buy in my country (Germany). Maybe > there is a

Re: [Replicant] [PATCH v2] Fix "RepWifi connection not correctly reported to userspace apps" Issue #1792.

Hi, thanks for the work Fil. I have couple comments about the patch. Fil: > --- > .../com/android/server/ConnectivityService.java| 68 > ++ > 1 file changed, 68 insertions(+) > > diff --git > a/services/core/java/com/android/server/ConnectivityService.java >

Re: [Replicant] [PATCH v2] Fix "RepWifi connection not correctly reported to userspace apps" Issue #1792.

Fil: > Joonas Kylmälä wrote: >> It is common practice to define them at top of the file. Also the AOSP >> guidelines have it: >> <https://source.android.com/source/code-style#define-fields-in-standard-places>. >> Well, now you might say that that is no reaso

Re: [Replicant] [PATCH v2] Fix "RepWifi connection not correctly reported to userspace apps" Issue #1792.

Fil: > I put them there, close to "getNetworkInfoByInterfaceName()", just to > keep all my modifications together, so that it's easier to locate them > and remove them in the future. > They can be moved above getActiveNetworkInfo() if there's any strong > reason to do so. It is common practice to

[Replicant] kernel_samsung_smdk4412: enable /proc/last_kmsg

Hi, It would be beneficial to have /proc/last_kmsg enabled for the kernel kernel_samsung_smdk4412. Users could then easily send their kernel logs for developers to look at. I included a patch to do this. Tested on i9305. Joonas >From 859a3b0ef5cfb592bd42c735e89fdaed31898921 Mon Sep 17 00:00:00

Re: [Replicant] i9305 kernel menuconfig

Denis 'GNUtoo' Carikli: >> Or is there some program I should run >> after menuconfig so that I can update the lineageos_i9300_defconfig >> changes to the git repository? > ARCH=arm make savedefconfig Thanks, I will try that! ___ Replicant mailing list

[Replicant] Galaxy S3 not booting

Hi, I was playing with resistors on the usb port with the i9305 (galaxy s3) device in order to get the UART serial console working. Then I gave up and took the wires out and flashed replicant to the device. The device would not boot. Then I installed twrp with lineage os to the device. Again, it

Re: [Replicant] i9305: Add support for rt2500usb wifi devices

Joonas Kylmälä: >> How was the performance with low battery charge? > I think there were problems with the performance when I didn't include > that patch #2 that disabled power management. After applying that patch > I think it worked as well with the low battery as with the full ch

Re: [Replicant] Galaxy S3 not booting

Wolfgang Wiedmeyer: > Indeed, this sounds strange. It would have been good to have UART to > see what happens ;) I wish I would have had that. If you or someone else reading this have time it would be very helpful to get instructions on how to do it. So far I have tried with the non-modified

Re: [Replicant] Galaxy S3 not booting

Wolfgang Wiedmeyer: > To add a little to what Denis already wrote: Make sure you have a > USB-to-UART converter that has a separate VCC pin and don't connect > it. Unfortunately, I don't really remember what resistor level I used at > the end to make it work with i9300 and I regret not documenting

Re: [Replicant] sdcard not mounted

See my comment on the Redmine ticket. Joonas Fil Lupin: > Hello again, > since a few months, I encounter a stranger problem: my sdcard is not mounted > by my system. Then I can just use my phone for basic functionnalities : > https://redmine.replicant.us/issues/1864 > I have no clue where to

[Replicant] Work on Replicant 7.1

Hi, I have been working for the past couple days on the next Replicant version. The work I have done is based on the cm-14.1 branches from LineageOS project. Forkbomb (Simon, I guess) said there was no support in LineageOS 15 for the Samsung Galaxy S3 devices so I thought it was better to go with

[Replicant] Compiling Jack for Replicant 7.1

Hi, I was compiling new Jack version for Replicant 7.1 and the new version requires a newer ecj.jar file than what is provided in Debian Stretch or unstable. What to do in this situation? I already sent bug report to Debian so that the version would be updated but it might take some time before

Re: [Replicant] Compiling Jack for Replicant 7.1

n packaged. > > Josh > > On 23/02/18 22:14, Joonas Kylmälä wrote: >> Hi, >> >> I was compiling new Jack version for Replicant 7.1 and the new version >> requires a newer ecj.jar file than what is provided in Debian Stretch or >> unstable. What to do in this situat

[Replicant] Draft patch for "F-Droid signed Repwifi" issue

Hi, I tried to draft patches for the RepWifi ticket over here: https://redmine.replicant.us/issues/1887. Please see them as attachments. What do you think will happen when we update the RepWifi app next time in Replicant and the user has already upgraded it with F-Droid? Also will this just start

Re: [Replicant] Work on Replicant 7.1

Denis 'GNUtoo' Carikli: >> $ repo init -u git://git.putti.space/replicant/manifest.git -b >> replicant-7.1-dev >> $ repo sync -jN > As a potential contributor[1] I'm a bit lost: > - which manifest should I base my work on? Depends what you want to work on. That replicant-7.1-dev branch is for

Re: [Replicant] Work on Replicant 7.1

Hi, I have now committed all my Replicant 7.1 work to git repositories. Again, to get the source code all you need to do is create an empty directory and run the following commands inside it: $ repo init -u git://git.putti.space/replicant/manifest.git -b replicant-7.1-dev $ repo sync -jN Then

[Replicant] git.replicant.us server configuration

Hi there, I was wondering if we could use some configuration management tool for the git.replicant.us server and then have the scripts publicly in a repository. The web interface doesn't load all the git repositories fast and cloning is somewhat unreliable when the server gets multiple

[Replicant] Help with Replicant 7.1 build error

Hi, I'm trying to build the franken Replicant 7.1 that I have and I get the following error that I cannot figure out how to solve: ninja: Entering directory `.' [ 20% 1/5] Ensure Jack server is installed and started Jack server already installed in "/home/user/.jack-server" Server is already

Re: [Replicant] Help with Replicant 7.1 build error

Hi Josh, Josh Branning: > I can't even attempt to help because I can't seem to access git.putti.space There's no HTTP server running there, only git daemon. You can get the source code I use with "repo init -u git://git.putti.space/replicant/manifest.git -b replicant-7.1-dev". However, it's not

Re: [Replicant] [PATCH] fix #1853 "Ecryption" typo in Settings App

Hi, Denis 'GNUtoo' Carikli: > On Sun, 2 Sep 2018 21:17:21 +0200 > Fil wrote: > >> From e17c05cfe9665ff1ec9dffbf46f90be18e44fa3d Mon Sep 17 00:00:00 2001 >> From: Fil Bergamo >> Date: Sun, 2 Sep 2018 16:44:44 + >> Subject: [PATCH] fix #1853 "Ecryption" typo in Settings App > Maybe mention

Re: [Replicant] website and wiki consistency

Hi Fil, send a patch for https://git.replicant.us/replicant/website/tree/supported-devices.php and I can apply it after a review. Joonas Fil Lupin: > Hi GNUtoo, > today, some visitor asked which one is correct between website and wiki >

Re: [Replicant] Changes for 6.0 0004 release

Joonas Kylmälä: > Hi, > > I have made bunch of little modifications to merge latest updates and > security fixes from upstream sources for the next Replicant 6.0 0004 > release. Please review them: > > For https://git.replicant.us/replicant/manifest (branch LineageOS-mirror): &

Re: [Replicant] [PATCH] fix #1853 "Ecryption" typo in Settings App

Hi, I can test it and push after the upstream merges. All the (non-merge) commits to this point have contained the Signed-off-by line but it seems like Replicant project has not formally established a meaning for it? I have taken it's meaning as that one certifies it is originally created by the

Re: [Replicant] Draft patch for "F-Droid signed Repwifi" issue

Denis 'GNUtoo' Carikli: > On Tue, 28 Aug 2018 18:53:00 + > Joonas Kylmälä wrote: > >> Hi, >> >> I tried to draft patches for the RepWifi ticket over here: >> https://redmine.replicant.us/issues/1887. Please see them as >> attachments. > Thanks a l

Re: [Replicant] Creating new repository to git.replicant.us

Thanks GNUtoo! It's probably alright that way too. Denis 'GNUtoo' Carikli: > On Sun, 23 Sep 2018 19:54:00 + > Joonas Kylmälä wrote: > >> Hi Paul and Wolfgang, > Hi, > >> I tried to create a new LineageOS-mirror repository to >> git.rep

Re: [Replicant] Changes for 6.0 0004 release

Hi GNUtoo and others, Denis 'GNUtoo' Carikli: >> [0001-Revert-Point-ResXMLTree-to-a-copy-of-the-asset-buffe.patch > The commit reverted by the patch above is this one: >> commit 953d2a3493aaceb3209afc7eef1ff1e7f7242908 >> (replicant/replicant-6.0, m/replicant-6.0-dev) Author: Wolfgang >>

[Replicant] Creating new repository to git.replicant.us

Hi Paul and Wolfgang, I tried to create a new LineageOS-mirror repository to git.replicant.us but step 3. at https://redmine.replicant.us/projects/replicant/wiki/LineageMirror is not much help. I think I need actual shell access in order to create the repositories we need because the command to

Re: [Replicant] [PATCH] Native Wi-Fi for external dongles

Hi, thanks for working on this! :) Is > +#define DRV_NUMBER_SEQUENTIAL_ERRORS 40 for the errors caused by the insufficient power supply for the wifi dongle? Joonas Belgin ?tirbu: > To be applied in the base source folder. > > patch -p0 < 6.0-wifi-dongle.patch > > > >

Re: [Replicant] Changes for 6.0 0004 release

Hi, just a gentle reminder: if you have time it would be great if you could take a look at the patches so we can get this moving forward. Joonas Joonas Kylmälä: > Hi, > > I can start pushing the merged repositories that didn't require any > additional commits to make it work.

Re: [Replicant] Changes for 6.0 0004 release

Hi, Denis 'GNUtoo' Carikli: > On my side I should improve reviews time. I should also look into > installing a patchwork instance to keep track of the patches I forgot > about. I have an image in my mind that maintaining patchwork for 58 or so git repositories was difficult. If it doesn't turn

Re: [Replicant] Changes for 6.0 0004 release

Hi, thanks for taking a look! :) Denis 'GNUtoo' Carikli: >> I can start pushing the merged repositories that didn't require any >> additional commits to make it work. Is that fine? > I don't understand what that means. I mean pushing those repositories where I did "git merge upstream/" and the

Re: [Replicant] Changes for 6.0 0004 release

Hey, Denis 'GNUtoo' Carikli: > On Sat, 15 Sep 2018 17:00:00 + > Joonas Kylmälä wrote: > >> I mean pushing those repositories where I did "git merge >> upstream/" and the merge worked without any conflicts >> and didn't require any additional commits a

[Replicant] New landing page for Git repositories

Hi, since it is not clear whether git.replicant.us landing page is a piece of copyrightable work and it doesn't have a free license (see https://redmine.replicant.us/issues/1914) I created a new landing page with Creative Commons Attribution-ShareAlike 3.0 Unported License. You can fetch it to

Re: [Replicant] Replicant contributors meeting in Paris (France) in July

Hi, I'm in! We can already decide probably a date for this since in the worst case we can just meet up in some public place. I suggest 27-28 of July. This way people can already get travel tickets for lower price and probably don't have so many other plans yet. Joonas Denis 'GNUtoo' Carikli: >

Re: [Replicant] libsamsung-ril/libsamsung-ipc: delete or sync master branch? Was: [PATCH 6/6] Fix undefined references to MD5_{Init, Update, Final}

Hi, Denis 'GNUtoo' Carikli: > Ah I understand what went wrong. I based my work on top of master > instead of the replicant-6.0 branch which is more recent. > > For now, I've pushed the first Acked patch to replicant-6.0-dev that > was created along the way. We generally have not used those

Re: [Replicant] [PATCH] Remove F-Droid until we can make a FSDG compliant version

Hi, I'm focusing my efforts on Replicant 9, so I just checked the patch doesn't do anything horribly wrong: Acked-by: Joonas Kylmälä Feel free to push. Denis 'GNUtoo' Carikli: > It's been more than one year that Replicant is aware that > shipping F-Droid as-is is not compliant with th

Re: [Replicant] Presentations for the Replicant contributor meeting in Paris (France) the 27 and 28 July

Hi, I was thinking a while back telling something about the porting process of a new device or basically what I did with the i9305 with the initial AOSP work. I will think about it again if I can make some sort of story or presentation about it. I would like to see presentations about the modem

Re: [Replicant] replicant make comment on the pinephone

Hi, ni nhar: > You say, likely there are several new phones > which have the replicant required hardware modem > isolation and therefore qualifies > for getting a replicant version? > Those phones do not get a replicant version > because of lack of money to > get replicant ported? That would be a

Re: [Replicant] Replicant contributors meeting in Paris (France) in July

Hi, the dates are confirmed (https://redmine.replicant.us/projects/replicant/wiki/ReplicantContributorsMeetingJuly2019) and location is somewhere in Paris or nearby. The exact venue will be hopefully decided shortly. I quickly calculated and there will be at least 6 people involved more or less

Re: [Replicant] [PATCH v2 1/3] Add basic gitignore

Reviewed-by: Joonas Kylmälä Denis 'GNUtoo' Carikli: > Signed-off-by: Denis 'GNUtoo' Carikli > --- > .gitignore | 3 +++ > 1 file changed, 3 insertions(+) > create mode 100644 .gitignore > > diff --git a/.gitignore b/.gitignore > new file mode 100644 > index 0

Re: [Replicant] [PATCH v2 2/3] Add a way to generate a static website

If you remove the extra empty line from the end of Makefile then: Reviewed-by: Joonas Kylmälä Denis 'GNUtoo' Carikli: > Signed-off-by: Denis 'GNUtoo' Carikli > --- > .gitignore | 2 ++ > Makefile | 33 + > README.txt | 14 ++ >

Re: [Replicant] [PATCH v2 3/3] supported-devices: Remove Galaxy S and Nexus S

Cool! I didn't notice the previous time but the "Unmaintained devices" row is 4 devices long instead of 3 as in the other rows. Maybe fix this too? Anyways the website scales down nicely even with 4 devices in one row but maybe the images are then not so clear so up to you if you want to fix this.

Re: [Replicant] replicant make comment on the pinephone

Hi, ni nhar: > > > Does it make the pinephone suitable for replicant? > > It looks way more suitable than the phones > already supported by > > Replicant. > > Then we should crowd fund getting you a pinephone. there are already funds for this sort of purchases so I'm sure

Re: [Replicant] pinephone chief wants to ship phones to a replicant manager denis please read this post

Hi, I'm not personally interested at this time (maybe in the future) but maybe adtjm, dllud, GrimKriegor or GNUtoo are? Joonas ni nhar: >  After asking the ceo of pine64, the company which > manufactures the pinephone, some > questions in a pm on the pine64 forum, he answered me. > > He says,

Re: [Replicant] [PATCH][website] index: Lastest images: Remove replicant 4.2 because it's not maintained anymore

Hi, fix the "Lastest images" typo from the commit title then: Acked-by: Joonas Kylmälä Denis 'GNUtoo' Carikli: > Signed-off-by: Denis 'GNUtoo' Carikli > --- > index.php | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/index.php b/index.

Re: [Replicant] Minutes of the 2019 Paris meeting

Hi, yes, the summary and video recordings is here: https://redmine.replicant.us/projects/replicant/wiki/ReplicantContributorsMeetingJuly2019 Laurent F: > Hello everyone, > > Is there a summary available or some kind of report of what have been > discussed during the meeting in Paris in July?

[Replicant] Graphics work progress for Replicant 9

Hi, I wrote a summary on the blog about the Replicant 9 graphics work dllud, GrimKriegor and I have been doing for the last couple weeks. For anybody interested here it is: https://blog.replicant.us/2019/07/graphics-support-for-replicant-9/ Joonas ___

Re: [Replicant] Status of Mesa's llvmpipe for Android

a bit harder. The patches are in our fork that is used with the Replicant 9 work. Joonas Kylmälä: > Hi dllud, > > thanks for the research! As we can see in > https://github.com/maurossi/mesa/commit/f7c2a171a4320a5a713861440f5f3df2611d7b1e > the change in Android build files to mak

Re: [Replicant] Status of Mesa's llvmpipe for Android

Hi dllud, thanks for the research! As we can see in https://github.com/maurossi/mesa/commit/f7c2a171a4320a5a713861440f5f3df2611d7b1e the change in Android build files to make llvmpipe work might be relatively small. Because this doesn't appear a to be huge amount of work and maintanance burden I

[Replicant] Replicant contributor meeting schedule

Hi, few people have now filled in the poll for the contributor meeting in Paris: . So here is my suggestion based on the poll: Saturday 11:00 -> 17:00 (and if possible / there are interested people we can still continue

Re: [Replicant] Replicant contributor meeting schedule

Hi Tiberiu, there is a dinner planned at 18.30: https://redmine.replicant.us/projects/replicant/wiki/ReplicantContributorsMeetingJuly2019#Related-events I'm not coming there myself. Joonas Tiberiu: > Hi, > > Anyone else in town today and also want to meet in this afternoon or evening, > for

Re: [Replicant] [PATCH][kernel/samsung/smdk4412] i9305: enable rt2500usb

Hi, please remove the extra colon ":" in "gnu...@cyberdimension.org:: Added more context in the commit message" and then feel free to add Acked-by: Joonas Kylmälä and push the patch! Denis 'GNUtoo' Carikli: > From: Joonas Kylmälä > > Some compatible Wi

Re: [Replicant] Security fix causing crash that blocks Replicant 6.0 0004 release

count though and don't particularly want one. It might be worth > asking them to provide a different login option so that we can > collaborate with them closer. > > Cordially, > Kurtis > > Joonas Kylmälä: >> Hi, >> >> yeah, this was just linked to #replicant IRC cha

[Replicant] [PATCH] Replicant 6.0 0004 images release

Signed-off-by: Joonas Kylmälä --- CHANGELOG.mkdn | 10 ++ config/common.mk | 2 +- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.mkdn b/CHANGELOG.mkdn index bb654f14..9c9eb960 100644 --- a/CHANGELOG.mkdn +++ b/CHANGELOG.mkdn @@ -1,6 +1,16 @@ Replicant

[Replicant] [PATCH v3] Remove phone number lookup settings in the graphical interface

-by: Joonas Kylmälä --- src/com/android/dialer/settings/DialerSettingsActivity.java | 6 -- 1 file changed, 6 deletions(-) diff --git a/src/com/android/dialer/settings/DialerSettingsActivity.java b/src/com/android/dialer/settings/DialerSettingsActivity.java index 52d91104..8db2e809 100644 --- a/src

Re: [Replicant] [PATCH] Replicant 6.0 0004 images release

This should be applied to vendor/replicant. Joonas Kylmälä: > Signed-off-by: Joonas Kylmälä > --- > CHANGELOG.mkdn | 10 ++ > config/common.mk | 2 +- > 2 files changed, 11 insertions(+), 1 deletion(-) > > diff --git a/CHANGELOG.mkdn b/CHANGELOG.mkdn >

[Replicant] Security fix causing crash that blocks Replicant 6.0 0004 release

Hi, we investigated today a system server crash: . It was bisected to commit . If anybody has suggestions how to fix this please let us know! This is

Re: [Replicant] Security fix causing crash that blocks Replicant 6.0 0004 release

> On Mon, Oct 14, 2019 at 9:38 PM Joonas Kylmälä wrote: >> >> Hi, >> >> we investigated today a system server crash: >> <http://paste.debian.net/plain/1106710>. It was bisected to commit >> <https://git.replicant.us/replicant/frameworks_av/commit/?id=1

[Replicant] [PATCH] Revert "Backport: OMXNodeInstance: use a lock around OMX::freeNode"

Signed-off-by: Joonas Kylmälä --- media/libstagefright/omx/OMXNodeInstance.cpp | 4 1 file changed, 4 deletions(-) diff --git a/media/libstagefright/omx/OMXNodeInstance.cpp b/media/libstagefright/omx/OMXNodeInstance.cpp index 6f1ba9b6b..04d0b258a 100644 --- a/media/libstagefright/omx

Re: [Replicant] [PATCH] Use Replicant's fork of frameworks/opt/net/wifi

This is pushed now. Belgin Știrbu: > >Signed-off-by: Joonas Kylmälä <https://lists.osuosl.org/mailman/listinfo/replicant>> > > Acked-by: Belgin Stirbu > >   Belgin > ___ > Replicant mailing list > Replicant@o

Re: [Replicant] pinephone chief wants to ship phones to a replicant manager denis please read this post

Andrés Domínguez: > I also mentioned the non-free firmware for WIFI, but I tell him that the > display firmware would make a port of Replicant to it impossible. depends how simple the hardware is. We could write free firmware if there is no signature checking. Joonas

Re: [Replicant] How shall we Redmine?

Hi, subprojects (and using any other redmine feature) is okay as long as there is some good use for it, and I think if someone starts to use some feature in some way that causes trouble for others then I think we can make it stop quite quickly. Having a subproject for infrastucture seems good

Re: [Replicant] [PATCH] Hide information leaking phone number lookup settings

Hi, this patch is applied to https://git.replicant.us/LineageOS-mirror/android_packages_apps_Dialer/. That is now a LineageOS mirror repo so if this patch is reviewed and accepted we need to fork the LineageOS repo. Joonas Joonas Kylmälä: > The phone number lookup service leaks priv

Re: [Replicant] release candidate for Replicant 6.0004

Hi, Jozef Macko: > Would like to know if you prepare one day release of Replicate with base of > Android 9 or 10, please? yes, we are working on that, LineageOS 16 based Replicant 9. Joonas ___ Replicant mailing list Replicant@osuosl.org

[Replicant] [PATCH] Use new name of FDroidPrivilegedExtension package

The FDroidPrivilegedExtension package was updated in the manifest to 0.2.8 version. In this new version the package name is F-DroidPrivilegedExtension. Signed-off-by: Joonas Kylmälä --- config/common.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/common.mk b

Re: [Replicant] [PATCH] Hide information leaking phone number lookup settings

Hi, Fil Lupin: > Should we not submit this patch also to LineageOS repo? > Do you think they will not be interested? > This could help making some users/developpers realize that android is not > exempt of privacy issues. I don't think cyanogenmod/lineageos 13 is developed anymore and this patch

Re: [Replicant] [PATCH] Disable phone number lookup settings during upgrade

Thanks, pushed. Denis 'GNUtoo' Carikli: > On Thu, 10 Oct 2019 00:12:56 +0300 > Joonas Kylmälä wrote: > >> This disables during the upgrade settings that cause private >> information leaking through phone number lookup feature. >> >> Signed-off-by: Joonas Ky

Re: [Replicant] [PATCH] Use new name of FDroidPrivilegedExtension package

Thanks, pushed! Denis 'GNUtoo' Carikli: > On Thu, 10 Oct 2019 09:23:59 +0300 > Joonas Kylmälä wrote: > >> From: Joonas Kylmälä >> To: replicant@osuosl.org >> Subject: [Replicant] [PATCH] Use new name of >> FDroidPrivilegedExtension package Date: Thu, 10

Re: [Replicant] [PATCH] Hide information leaking phone number lookup settings

Hi, Joonas Kylmälä: >> Note that I didn't have time to look into the broader context of that >> patch yet, so I don't know if lookupSettingsHeader should be completely >> removed or not. > > I will remove it completely in v2. Thanks for the review! oh actually,

Re: [Replicant] [PATCH 0/7] Per process libagl/llvmpipe

est we push these patches except the last one now even if there is no review as more than one week has passed. I'm still hoping to hear from at least some of you in the To field of this email whether you are okay pushing the patches. Joonas Joonas Kylmälä: > Hi, > > I got thi

Re: [Replicant] [PATCH] Native Android WiFi with external dongle

Hi Belgin, would you be able to make a new version of this patch within this week? We are hoping to make a release candidate for Replicant 6.0004 next Monday and release the following Sunday. Joonas Denis 'GNUtoo' Carikli: > Hi, > > I'm really sorry for the delay. > > Thanks a lot for working

Re: [Replicant] [PATCH 0/7] Per process libagl/llvmpipe

.android.browser Without the last patch: Tested-by: Joonas Kylmälä Joonas Andrés Domínguez: > Selection of libagl or llvmpipe at EGL link time. It's based > on the work of Jookia and JeremyRand, but it uses files for > configuration instead of properties or symlinks. > &

[Replicant] [PATCH] Disable phone number lookup settings during upgrade

This disables during the upgrade settings that cause private information leaking through phone number lookup feature. Signed-off-by: Joonas Kylmälä --- .../cyanogenmod/cmsettings/CMDatabaseHelper.java| 21 - 1 file changed, 20 insertions(+), 1 deletion(-) diff --git

Re: [Replicant] [PATCH] Disable phone number lookup settings during upgrade

Hi, this is to be applied to https://git.replicant.us/replicant/vendor_cmsdk/ Joonas Kylmälä: > This disables during the upgrade settings that cause private > information leaking through phone number lookup feature. > > Signed-off-by: Joonas Kylmälä > --- > .../cyan

[Replicant] [PATCH] Hide information leaking phone number lookup settings

The phone number lookup service leaks private information so hide the option to enable it. Signed-off-by: Joonas Kylmälä --- src/com/android/dialer/settings/DialerSettingsActivity.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/com/android/dialer/settings

Re: [Replicant] [PATCH v3] Add native Android support for external WiFi dongles

Hi, removing the multicast packet filtering is not ideal but I checked the RepWifi code and it doesn't seem to be setting any packet filters either so that seems to be a separate problem to be solved. Otherwise the patch seems okay and I have tested it works: Acked-by: Joonas Kylmälä Thanks

Re: [Replicant] [PATCH v2] Add native Android support for external WiFi dongles

Hi, I'm a bit worried about removing the code about multicast packet filtering. Would this have some sort of effect on the firewall configuration? You also dropped the signed-off-by line and the description why bluetooth and the packet filter needs to be removed, please add those back for v3.

[Replicant] [PATCH v2] Hide information leaking phone number lookup settings

The phone number lookup service leaks private information so hide the option to enable it. The lookup service is by default disabled so this guarantees no information gets leaked if the user would accidentally enable the service. Signed-off-by: Joonas Kylmälä --- src/com/android/dialer/settings

Re: [Replicant] [PATCH v2] Hide information leaking phone number lookup settings

il topic. > > Thanks, > > - Fil Lupin. > > ‐‐‐ Original Message ‐‐‐ > On Saturday, October 12, 2019 7:15 PM, Joonas Kylmälä > wrote: > >> The phone number lookup service leaks private information so hide the >> option to enable it. The lookup service

Re: [Replicant] [PATCH 0/7] Per process libagl/llvmpipe

ult opengles renderer. > > Andrés Domínguez > > El jue., 10 oct. 2019 a las 20:07, Joonas Kylmälä () > escribió: > >> Hi, >> >> so we didn't get anyone to review these patches except the last one: >> <https://redmine.replicant.us/issues/1844#note-13>.

Re: [Replicant] [PATCH] Add libagl override for surfaceflinger

Hi, please explain in the patch what is libagl override for surfaceflinger and add your signed-off-by line. Joonas Andrés Domínguez: > --- > config/common.mk | 4 > prebuilt/common/etc/libGLES_android/system/bin/surfaceflinger | 0 > 2 files

Re: [Replicant] [PATCH] Include F-droid's Offline Calendar as a prebuild

Hi, please send two patches: 1 to remove f-droid and 1 to include offline calendar. Also add signed-off-by line. Also would be nice to have a description why Offline Calendar app and not some other calendar app. And descriptoin for why F-droid is removed. Joonas Andrés Domínguez: > --- >

Re: [Replicant] [PATCH 0/7] Per process libagl/llvmpipe

Hi, pushed all except the last patch. Joonas Kylmälä: > Hi, > > thanks for the reply! > > I'm planning to push these patches tomorrow so if you have any > objections please do that now. > > Joonas > > Andrés Domínguez: >> Hi. >> >> As J

Re: [Replicant] [PATCH v3] Add native Android support for external WiFi dongles

Hi, I have pushed it now here: <https://git.replicant.us/replicant/frameworks_opt_net_wifi/log/?h=replicant-6.0>. It still needs to be added to the manifest which I will submit a patch in a moment. Joonas Joonas Kylmälä: > Hi, > > removing the multicast packet filtering is

[Replicant] [PATCH] Use Replicant's fork of frameworks/opt/net/wifi

Signed-off-by: Joonas Kylmälä --- default.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/default.xml b/default.xml index ca727c1..ed52512 100644 --- a/default.xml +++ b/default.xml @@ -167,7 +167,7 @@ - + -- 2.11.0

Re: [Replicant] [PATCH] Use Replicant's fork of frameworks/opt/net/wifi

Hi, this is for the manifest repo: https://git.replicant.us/replicant/manifest/ Joonas Joonas Kylmälä: > Signed-off-by: Joonas Kylmälä > --- > default.xml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/default.xml b/default.xml > index ca

Re: [Replicant] Replicant 6.0 0004 RC1 on espressowifi

Hi, yeah, the images for RC1 has been signed with GNUtoo's key and for the 0003 release with Wolfgang's key, so since there is signature checking using rc1 zip on 0003 recovery won't work and vice versa. Graham Cobb: > On 13/02/2020 10:11, Graham Cobb wrote: >> Do I need to reload the original

Re: [Replicant] [device_samsung_espresso3g][PATCH] device.mk: fix "libaudio-ril-intierface" typo

Acked-by: Joonas Kylmälä Denis 'GNUtoo' Carikli: > This was introduced by the following commit: > affda81 Add scripts to disable the modem > > Reported-by: Joonas Kylmälä > Signed-off-by: Denis 'GNUtoo' Carikli > --- > device.mk | 2 +- > 1 file changed, 1

Re: [Replicant] Device donation: Nexus 5X

Hi, the Nexus 5X seems to not be a good target for Replicant because of its Qualcomm MSM SoC with integrated modem (https://redmine.replicant.us/projects/replicant/wiki/TargetsEvaluation#Known-to-be-bad-targets). So probably no Replicant developer is interested in that particular device. Sascha

Re: [Replicant] Replicant 6.0 0004 RC1

Hi, modem is not supported for the i9305 so no phone calls, sms or data. Josh Branning: > On 12/01/20 05:11, Kurtis Hanna wrote: >> Heyo, >> >> Here's the link to the Replicant 6.0 0004 rc1 images: >> https://ftp.osuosl.org/pub/replicant/images/replicant-6.0/replicant-6.0-0004-rc1/images/i9305/

Re: [Replicant] Replicant 6.0 0004 RC1 - LineageOS 16 or LineageOS 17 ?

Hi, Jozef Macko: > just quick question which version of LineageOS 16 or LineageOS 17 are used > for Replicant 6.0 0004 RC1? Neither, 6.0 is based on LineageOS/CyanogenMod 13. > One day 10.10.2019 i received answer from Joonas Kylmälä that you are > working on that, LineageOS 16 bas

Re: [Replicant] [PATCH] ipc-test: improve error reporting

Acked-by: Joonas Kylmälä Denis 'GNUtoo' Carikli: > Signed-off-by: Denis 'GNUtoo' Carikli > --- > tools/ipc-test.c | 18 +- > 1 file changed, 9 insertions(+), 9 deletions(-) > > diff --git a/tools/ipc-test.c b/tools/ipc-test.c > index cc8548f..59f9074 100

Re: [Replicant] [PATCH] Replicant 6.0 0004 images release

Hi, if you can wait until Monday I can send a v2. I would like to reproduce this issue myself also. Denis 'GNUtoo' Carikli: > On Sun, 27 Oct 2019 17:26:57 +0200 > Joonas Kylmälä wrote: > >> Signed-off-by: Joonas Kylmälä >> --- >> CHANGELOG.mkdn | 10 +

Re: [Replicant] Introducing ccache to Replicant 6

Hi, Denis 'GNUtoo' Carikli: > Is there an advantage in building ccache when most GNU/Linux > distributions already have it? > > Is it for making the build more reproducible? > Is it to make it more easy and have less dependencies? In my opinion we should just use the distro ccache and that is

Re: [Replicant] Replicant Digest, Vol 351, Issue 1

Hi, I still don't see a reason to include it in the Replicant build process. Why newer version is better? Without any good reason to fork the upstream code we should not do this because it leaves us to maintain it. Although almost nobody is probably working anymore on the replicant 6 upstream

Re: [Replicant] [manifest][PATCH] Move libsamsung-ril and libsamsung-ipc in vendor/replicant

Hi, Just FYI: I will be pushing similar patch for replicant-9 manifest. Denis 'GNUtoo' Carikli: > This unify the naming of libsamsung-ril which is sometimes > called samsung-ril and sometimes libsamsung-ril. > > Using the samsung-ril naming is confusing because it would > imply that it's not a

Re: [Replicant] apAndroid basic apps still are google?

Hey, yes, but there are commits to remove the telemetrics, this is at least what we did recently with the Dialer App since there was one thing we had missed (https://redmine.replicant.us/issues/1827). I have not been developing replicant 6 in its early days so I'm not exactly sure how rigourous

Re: [Replicant] is replicant 6 insecure? does google update android 6?

Hi, there are no security updates / bug fixes for AOSP 6, meaning also no updates for Replicant 6. I think I have seen occasional security fix backported by LineageOS devs for CM13 but that probably doesn't help much. ___ Replicant mailing list

Re: [Replicant] [libsamsung-ril] [PATCH 1/8] ss: remove unused state variable

Hi, Denis 'GNUtoo' Carikli: > Signed-off-by: Denis 'GNUtoo' Carikli > --- > ss.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/ss.c b/ss.c > index 49f3152..59e134f 100644 > --- a/ss.c > +++ b/ss.c > @@ -214,7 +214,9 @@ complete: > return rc; > } > >

  1   2   >