Test Builds #8

[Spookcity]

A continuation of #10, #18, #19, #20 ,#21,#22 and #23

[vonico]

Any news about FM radio?

[Spookcity]

@vonico Hey sorry it took me so long to answer this. I've been away. The news is about the same however. The sound does not route properly. It is still being worked on,but from my understanding it's a bit of a guessing game as to what has changed since KK and the last working version of FM radio. Could be many things.Therefor it is rather time consuming. Hopefully it will be figured out. Only time will tell.

[alefello]

Hi Spookcity 1st question: I noticed that fingerprint sensor remains active only for a little while after screen is turned off. Is it possible to keep it active with screen off, so we can have a "fingerprint to wake"? 2nd question: for FM is only the sound that does not route, in your kernel is implemented the right bluetooth driver that at least make FM scanning avaliable? 3rd question: is it possible to have it compiled for android MM? Thank you

[Oleggluk]

On the official RR page in Google +, screenshots appeared with RR v6 android 8.1. https://plus.google.com/communities/109352646351468373340

[Oleggluk]

From the latest news from the Internet: Resurrection Remix (official) Greetings to all RR users First and foremost we would like to thank you all for being patient for the RR-Oreo release.

We , Team RR would like to announce that the wait is finally over . Today we will be releasing first builds for RR-OS based on Android 8.1.0 .

[friedensfurz]

@Oleggluk Yeah, I will release a test build of RR 8.1.0 soon ;)

[vonico]

Does somebody know if there has been some progress on the video recording issue? I mean, if there are so many affected devices it shouldn't take too long for the LOS team to release a patch or something, right? Or is it more difficult to fix it as I'm imagining?

[Oleggluk]

@vonico hennymcc updated the information on the forum in topic LineageOS 15.0. @friedensfurz I think it's already worth trying to build a version of RR v6?

[Oleggluk]

@Spookcity Come back, I will forgive everything :D

[friedensfurz]

@Oleggluk The build will take some more time, @Spookcity how do I fix "could not locate config makefile for product xy" ? It even shows when I try to build for official devices :/

Edit: Nevermind, with the new RR, everything with lineage in its name needs to be renamed to rr.

[friedensfurz]

@Oleggluk Would you be willing to test a RR O build soon? It could be possible that it doesn't boot, is that okay for you? :)

[Oleggluk]

@friedensfurz Always ready). I am for any kipish, except hunger strike.

[friedensfurz]

@Oleggluk Build is almost ready

Edit: Build is ready. Look at my Androidfilehost profile to find it.

Three things:

• Do a full wipe
• Use latest TWRP
• No other zips like Gapps, magisk etc. at least just for this test as it could cause issues

Hope it works ;) If not just write it here !

[Oleggluk]

@friedensfurz This is a horrible morning quest. I can not find the link where to download.

Found! It was complicated)))

Installation was successful without errors. But unfortunately it does not work. Do not load beyond the initial Samsung screen.

[friedensfurz]

@Oleggluk Did you try the TWRP from LOS 15 thread? Otherwise please reflash the rom, ehen it doesn't boot go into twrp>Advanced>copy log>include kernel log and post them here. It needs to be done right after the bootloop. Thanks

[Oleggluk]

@friedensfurz I used TWRP from LOS 15 thread and the latest official version. The result is the same. Now I do not have time, but later I'll try to make a log

[Oleggluk]

@friedensfurz I'm not sure what I did right. At TWRP from Los15 and the last official TWRP, completely different logs and names. recovery1.log dmesg.log

[friedensfurz]

@Oleggluk That's perfect, it seems to be about the old selinux problems. I will build a permissive ROM/boot image the next days as it should fix the issue ;)

[iiziispace]

TWRP 3.2.1-0. Do not load beyond the initial Samsung screen.

[Spookcity]

Hey guys! It's been awhile. I apologize for disappearing for a bit there,but I got the flu for way too long and then my gf got it. So yeah,you can prob imagine the fun times I've had over the last weeks :D Anyway,I'm back and offer XenonHD-8.1 in hopes that all is forgiven lol It is very much untested.It boots and I played with it for about 5 minutes yesterday,so yeah,perhaps things don't work. Basically for those who want to try out an 8.1 ROM. Or until @friedensfurz gets RR going.

@alefello Are you part of the dev group on Telegram? I only ask due to similarities in names. If you are (I am as well. I am Rick there....and well irl too) I have only reported news on FM radio that you and Tobias have talked about and worked on. I have not messed with it in many months. If you're not the same person,please disregard :)

[Oleggluk]

@Spookcity Welcome back. I would like to see from you RR V6

XenonHD-8.1 is already downloaded. There is 1 hour for experiments :D

It's started! I forgive you)) :D

Some problems with the resolution for applications. Does not see the files on the external memory card (you may need to format it). Now there is no time. Tomorrow I will test better. But I'm still waiting for RR v6))

[Spookcity]

@Oleggluk Hehe,thank you :) I'm glad Xenon booted up for you. I will hopefully have some more time tomorrow to test it more as well. I'll pay special attention to app resolutions and external memory.

As far as building RR v6..I have no problem trying to build it when I have some time,but it seems like @friedensfurz is working on it and nearly has it going. I don't want to do my own build if he is working on it. That said,I am more than willing to lend a hand and help out with it where I can if needed,or if he is not planning to work on it I will give it a go.

[Oleggluk]

@Spookcity I will not tell anyone if you build RR, this will be our secret))))).

In XenonHD-8.1 applications do not have access to phone memory and an external memory card. Once upon a time there was such a problem before.

[Spookcity]

@Oleggluk Haha uh huh :)

You're right,apps not having access to the phone memory and memory card was an issue at the beginning with 8.0 ROMS as well. I can't remember exactly what the fix was. I kinda think it may have been a patch by Tobias. I will have a look. I used to browse our device repo as well as other similar devices on github and random gerrit pages to keep up on what was going on,but haven't done so in a couple of months since I got sick. Hopefully I'll find some time to start looking again.

[Oleggluk]

@Spookcity I ran RR v6 from friedensfurz on the core of XenonHD-8.1. So is the problem with memory.

[friedensfurz]

Hey @Oleggluk and @Spookcity, is RR working now? I'm currently building a permissive RR, because I think that was the problem before ;)

[friedensfurz]

New build online at AndroidFilehost!

[MikeTeh]

@friedensfurz Thank you, i'll try it out next days, this build is 8.1? Beste Grüße

[Oleggluk]

@friedensfurz It still does not work. Next to the screen Samsung does not pass.

[alefello]

@Spookcity Hello and welcome back! Yes, I'm alefello on telegram group. In the last few days I had some problems with RR 7.1 on my device (bugs, lagging and so on) so I'm trying to go further with FM radio research and downgrade to MM to see if it's more stable and more reactive. About that... Is there some 1,6GHz MM kernel version still available? Unfortunately I still have had no time to try to setup a build environment to try to compile a kernel or a rom by myself :(

[Oleggluk]

@friedensfurz The version from February 25 could be launched with a kernel from XenonHD-8.1. The version from March 4 does not start, and on the XenonHD-8.1 kernel it does not start either.

[Oleggluk]

the problem is not in the core. I ran XenonHD-8.1 on the kernel from RR-O-v6.0.0-20180304-kminilte-Unofficial

[friedensfurz]

@Oleggluk RR seems to miss some commits that are available in Lineage etc. I will port the boot.img from @Spookcity 's Xenon port.

Edit: LineageOS builds and boots as well, so it is a problem in RR

[Oleggluk]

@friedensfurz Why are you doing it? The kernel in the latest version of March 4 is working! I ran a version of it on February 25th. But it's also a memory problem. And the clean version of March 4 does not start at all.

[Oleggluk]

[friedensfurz]

@Oleggluk Yeah, I will just fix it so there's no need of flashing multiple ROMs etc. I just want it to work as any other Rom, but you're right - there will be no effect otherwise.

What is the memory issue btw?

[Oleggluk]

@friedensfurz Applications do not have access to internal and external memory. They ask for permission, you allow, but no effect. File managers do not see the memory, other applications do not see their backups and can not save anything, some applications do not start because of this.

[friedensfurz]

@Oleggluk Did @Spookcity fix that yet? It sounds like it's not just with RR.. :/

[Oleggluk]

Here in # 22 parts, we have already discussed the problem of memory in Los15

"Spookcity So this storage issue with Los 15 appears the problem of sdcardfs. I successfully downloaded the material with chrome and my memory is now also displayed in MiXplorer. This was achieved by disabling sdcardfs. This, though not a complete solution. Spookcity commented on October 9, 2017 @Oleggluk good to hear! These are good results. Tobias has returned and he already has a complete solution to the issue of storage, because he is a ninja, hehe. It seems like there is not much that actually happens with Los. They have not done too much lately, so I do not know what's going on with this. We hope that they will start adding things, although in the near future. Time will tell."

[Spookcity]

@Oleggluk and @friedensfurz OK,let me see if I have this RR situation straight: The old build boots with the xenon boot.img meaning @friedensfurz was correct and it was just a kernel issue.The build from yesterday doesn't boot no matter what.

If so,in my experience it must be 1 of 2 things,both RR source related.

1. A bad commit(s) that has just broken things and will be fixed by RR soon or
2. A commit that has just broken things for a few devices. I've had this before,but never on a Lineage based ROM. Always AOSP. I would have to guess that its just a bad commit,but who knows.

The memory/storage issue was resolved with This patch on 8.0 ROMS. It should work on 8.1 as well,but may need editing to apply. I'm not sure. If I ever find time I'll try.

@alefello I had a look on XDA and I guess I never overclocked the CPU on the MM kernel. I should be able to do this fairly easily with just a few edits. I will try to do so this week and if all goes well I'll post it up here.

[Oleggluk]

@Spookcity And this has to do with the patch and memory problem? https://github.com/cm-3470/android_device_samsung_smdk3470-common/commit/87c6852ddbbbd943dccecd5019af0cebc05d92ac

[friedensfurz]

@Spookcity Thanks for the patch. However, there is a merge conflict, how do I fix that? ;)

[Spookcity]

@Oleggluk Yes,this patch resolved the memory issue on 8.0 Roms. It or something similar should be the fix on 8.1 as well I would think.

@friedensfurz Hmm,can't really say off hand. If I have some time later I will try to look at the patch and the file thats being patched to see if I can tell whats happening. You can always try to to patch the file by manually editing the sdcard/sdcard.cpp file. Could be a bit of a pain though. You could also try to move the patch to the system/core folder.CD into that folder and run "patch -p1 < 0003-sdcard_setup_read_write_mounts.patch" I am by no means an expert on patches,but have found this to work a couple of times. Why I don't know. If it doesn't work it may at least patch some of the file and output to a .rej file the failed parts. May make it easier to just manually patch those bits to the sdcard.cpp file.

[friedensfurz]

@Spookcity Thanks I will try later @Oleggluk The patch you found seems to work around that problem, it's much easier but no real fix though. So I will try to use the Spookcity way:ok_hand:

[Spookcity]

You're right @friedensfurz . I assumed incorrectly that what @Oleggluk linked was the patch I linked earlier,my bad.

But sdcardfs is now default,so that will stay either way...and it also shouldn't fix the issue as it doesn't disable sdcardfs (which we don't want to do) as it defaults to it,so there's just no need to explicitly call it anymore.

I suppose it's possible that adding that prop back could solve it though. Kinda doubt it,but who knows.

[Oleggluk]

@Spookcity I absolutely did not understand anything with this translator., But I'm glad that the work continues)).

[Spookcity]

@Oleggluk Haha. Well,even native English speakers don't understand me a lot. I often ramble and make little to no sense :) You got the important bit out of it though...The work does continue and it really shouldn't be that difficult to fix as it has been fixed before. Just a matter of making it work with the changes in 8.1.

[friedensfurz]

RR repo seems to be fairly unstable still, since yesterday, the build fails without a real error when compiling the settings app but since I haven't changed anything, it must be s repo issue.

@Spookcity I found out how to read a patch manually, so I was able to add the lines to sdcard.cpp. I also readded the Sdcardfs flags Tobias removed, they don't seem to interrupt the build so I'll leave them in there.

[Yuuji9029]

Hey! I'm currently testing both RR-V6 and XenonHD8.1 as well and here's my Feedback.

RR-V6.0.0; The Version from the 25th Feb. only boots with the XenonHD Boot.img, without the Xenon Boot Image it stays at the "Samsung S5 Mini" Screen forever (That Issue was already reported) ~ The Fingerprint doesn't work at all. ~ Other than that it seems to be working fine, haven't tested it further yet.

XenonHD 8.1; Seems to be working fine as well, haven't faced any serious Issues yet, I'm now downloading 8.1 Gapps to see if it works. ~ Fingerprint is working so far, using it as Unlock Method without any problems.

XenonHD looks like the more stable ROM for now. But as soon as RR starts working better I'll switch to that one :D

[Yuuji9029]

Update: GApps are working, Since Videos still can't be played I tried installing Lucky Kernel, but that results in a Bootloop.