Test Builds #9

[Mikahlo]

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

[Oleggluk]

From telegrams all were expelled and here there is silence.

[friedensfurz]

New test build of RR online here (https://androidfilehost.com/?fid=962339331459002251)@Oleggluk . Please test and let me know if there are any problems ;)

[Oleggluk]

@friedensfurz Looks pretty stable. I have time 1.40 nights, I can not test for a long time. I moved from RR5.8.5 to RR6.1 without formatting Date section, all applications are saved, except contacts !!! (before the firmware I deleted only Magisk and xposed). I also did a wipe system, cache and dalwick cache. In RR6.1 there are no physical button settings, but my button settings have been saved from RR5.8.5!. The camera does not work at all. Snap camera only takes pictures. The Internet works, wi-fi works, vpn works .. I really want to sleep))

[friedensfurz]

@Oleggluk Thanks for testing that. Is the camera really not working at all? And the main thing, are Apps working fine ? Some people have a new storage issue on Lineage and it is not possible to modify any file, only creating and deleting works. If there is an issue, the call history will be emptied after every call. Thanks for testing and if there's any other issues, just write them here ;)

[Oleggluk]

@friedensfurz Concerning the problems of changing files, I noticed only one problem, in X-plore I can not edit text files, but this is possible with other file managers. The camera in my cell photographs gray squares. Snap camera takes pictures well. Video shooting does not work anywhere. I can not check the history of calls, I'm an Internet maniac)), calls are not for me)).

[Oleggluk]

@friedensfurz There is no problem with the history of the call. But I do not see any advantages from using android 8.1. For me, android 7.1.2 is more suitable and more familiar. I now want to install ResurrectionRemix-M-v5.7.4-BlackMix-20160921-kminilte.zip)) for the sake of experiment. And then I'll return to RR 5.8.5 (android 7.1.2).

[friedensfurz]

@Oleggluk Thanks for testing that out. One last thing if you (or someone else) tests RR-O again, are heavy camera apps like Snapchat etc. working? I'd be interested if they crash the camera or not. Thanks ;)

[Oleggluk]

@friedensfurz The company Samsung announced a new budget smartphone on Android 8.1 Oreo from the Android Go project. The characteristics are similar to our device, only we have the Exynos 3 Quad 3470, and the new Exynos 7570 with a frequency of 1.4 GHz. Maybe it can be ported to our phone? Or use some files to complement the Los15.1 and RR-v6.1?

[Spookcity]

Hey guys! (Assuming anyone still visits these parts) It's been awhile,but I'm still around and am still using my S5 Mini. Just a small update along with some ROM builds I've done in the last week or so that I figured I would share. I've not had time for much Android wise recently,but I did spend a few days trying to solve the video recording problem on Oreo ROMS. I had no luck sadly. I must assume it is a device specific problem as I believe video recording was sorted out some time ago,so thats where I focused,but still no luck.

ROMS AospExtended-v5.8 - AEX 5.8_microG

READ ME I have fully integrated MicroG into this ROM. DO NOT flash a Gapps package! If you do not know what this is or do not wish to use it I suggest another ROM. I have included the Core obviously,but along with that I have also built in the other parts

• MapsAPI
• FakeStore
• NominatimNlpBackend (Address lookup backend)
• IchnaeaNlpBackend These need to be setup with MicroG settings app You also must go to settings -> Apps and Notifications -> App Permissions -> Spoof Package Signature. Click the 3 dot menu -> Show system and the check both FakeStore and MicroG
• If you don't use F-droid and/or APK Pure or similar for your app needs and would like to install the play store you can have a look HERE

Other ROMS XenonHD - XenonHD-180910-Unofficial-kminilte AICP -aicp_kminilte_o-13.1-UNOFFICIAL-20180908 GZOSP - Gzosp-kminilte-8.1.0.Stable.1.1-UNOFFICIAL-20180907-1121

I merged the latest Lineage 15.1 sources into my Hardware/Samsung folder for all of these builds as it was needed to build a few of these. Did it break things? I don't know. I have only tested AEX,but please let me know if so.

Maybe I will have more time in the coming months to mess with Android more. Here's hoping!

Enjoy!

[Mikahlo]

Hey @Spookcity : which filesystem do you use for the internal storage? I can only copy stuff to the external sd-card but not to the internal storage. I use f2fs as internal filesystem and vfat for external.

[Mikahlo]

Can't copy stuff with the file manager or with MiX. Already tried different file systems. Guess I'm SOL xD. The AEX boot animation looks nice btw. 09-21 20:10:54.686 I/MiX ( 4582): ----- Operation started ---------------------- 09-21 20:10:54.688 I/MiX ( 4582): Action: COPY 09-21 20:10:54.689 I/MiX ( 4582): Calculating... 09-21 20:10:54.691 I/MiX ( 4582): Total: 4268787 bytes 09-21 20:10:54.699 I/OperationHelper( 4582): Copy from /storage/emulated/0/Download/Magisk-v17.1(17100).zip 09-21 20:10:54.699 I/OperationHelper( 4582): To /storage/emulated/0/Pictures 09-21 20:10:54.708 D/OH: ( 4582): default 09-21 20:10:54.731 D/SurfaceFlinger( 2097): duplicate layer name: changing com.mixplorer/com.mixplorer.activities.BrowseActivity to com.mixplorer/com.mixplorer.activities.BrowseActivity#1 09-21 20:10:54.731 D/MiX ( 4582): Os Why?! 09-21 20:10:54.743 E/OperationHelper( 4582): java.io.FileNotFoundException 09-21 20:10:54.744 W/GrallocMapperPassthrough( 2097): buffer descriptor with invalid usage bits 0x400 09-21 20:10:54.750 I/MiX ( 4582): Operation failed: No item copied 09-21 20:10:54.754 I/MiX ( 4582): ----- Operation failed. 0s ------------- 09-21 20:10:54.762 W/GrallocMapperPassthrough( 2097): buffer descriptor with invalid usage bits 0x400 09-21 20:10:54.795 W/GrallocMapperPassthrough( 2097): buffer descriptor with invalid usage bits 0x400 09-21 20:10:54.836 E/memtrack( 2253): Couldn't load memtrack module 09-21 20:10:54.836 W/android.os.Debug( 2253): failed to get memory consumption info: -1 09-21 20:10:54.891 W/GrallocMapperPassthrough( 2097): buffer descriptor with invalid usage bits 0x400 09-21 20:10:54.903 W/GrallocMapperPassthrough( 2097): buffer descriptor with invalid usage bits 0x400 09-21 20:10:55.002 W/GrallocMapperPassthrough( 2097): buffer descriptor with invalid usage bits 0x400 09-21 20:10:56.780 I/ActivityManager( 2253): START u0 {flg=0x10804000 cmp=com.android.systemui/.recents.RecentsActivity} from uid 10025 09-21 20:10:56.793 W/GrallocMapperPassthrough( 2456): buffer descriptor with invalid usage bits 0x400 09-21 20:10:56.793 I/MiX ( 4582): MiX paused. 09-21 20:10:56.794 E/BufferQueueProducer( 2456): [unnamed-2456-8] setMaxDequeuedBufferCount: 3 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0) 09-21 20:10:56.794 E/Surface ( 2456): IGraphicBufferProducer::setBufferCount(4) returned Invalid argument 09-21 20:10:56.811 E/BufferItemConsumer( 2456): [unnamed-2456-8] Failed to release buffer: Unknown error -1 (1) 09-21 20:10:56.866 W/GrallocMapperPassthrough( 2097): buffer descriptor with invalid usage bits 0x400 09-21 20:10:56.870 W/GrallocMapperPassthrough( 2456): buffer descriptor with invalid usage bits 0x400

[aelfinn]

Some quick feedback on the AICP, GZOSP, and XenonHD builds: AICP runs pretty well, but hardware button backlight seems to be non-functional; I could get GZOSP to boot only without GApps or Magisk; XenonHD seems to be running really well, with only LiveDisplay apparently not working (selection is not retained) and very little standby battery drain with Magisk module “Enable Doze for GMS”.

[Spookcity]

@Mikahlo Yes,I have only just recently noticed this strange file system issue. I was using AEX nougat until just a week or so ago. I am not real sure where the problem lies,but it seems as if it should be a easy fix,but I'm not real sure. I will try to look into it some when I have a little time.

Also

Anyone with any dev abilities want to help me try to get this going? At this point not much works. I have already fixed a few things and spent a fair bit of my free time on it in the last week. It only builds with a bunch of repo picks and a few hacks at this point. I just don't have tons of time.I may be able to do it alone (or not) but it will take forever if so.We could create a telegram group or something if any others would be willing to help out. I haven't heard from anyone in the other telegram group in a long time. Tobias (hennymcc) included,so I can only guess that after bringing many Android versions to our device he may be done. Not speaking for him of course,just a guess. Either way,if anyone is interested in helping it would be great! I will probably be without internet access for a few days to a week (holiday) So hopefully when I check back here I'll get some replies :)

[friedensfurz]

Nice to have you all back! @Mikahlo From the Lineage 15.1 Thread (https://forum.xda-developers.com/showpost.php?p=77308985&postcount=469). That might be really helpful as it seems to be just a permission issue from android and is (hopefully?) easily fixable

@Spookcity That's really nice! I'd love to give you a hand with that, time is not my primary problem, but I don't have too much knowledge about that stuff.. However, the commits that were made to the devicetree when a new Android version came out were not too complicated. I just don't understand (yet :) ) why there must be any changes to the devicetree. Can't it just work with a new Android sourcecode and unchanged device repos?

Also, I have recently uploaded some patches to the kernel against CVE: https://github.com/friedensfurz/android_kernel_samsung_kminilte with the help of @cschsz

Happy developing ;)

[Mikahlo]

@friedensfurz : Thanks for the hint! I have no clue how to add apps manually to a group in android but it should be possible to "just" install some apps as system apps at least a file manager. Will try that out.

@Spookcity : There is no need to fix this because most users didn't even noticed this strange behavior. Regarding android 9 I'm obviously not able to help. Nowadays time is to short to even get started with compiling stuff :(

[friedensfurz]

@Mikahlo Moving the non-working apps in /system works, but takes up too much space for me, sadly. There is probably an easy fix via kernel commit though.

[Spookcity]

I pushed my Android 9 branches and opened a new issue on here for discussion of this. Please go Here If interested in helping out. Thanks!

[rodman01]

Great and many thanks

[aelfinn]

@Spookcity As I said on XDA, your XenonHD build has been rock solid for multiple people I migrated to it, plus it is fast and smooth. If you could perhaps keep that ROM loosely updated, that would be enormously appreciated! :)

[Spookcity]

@aelfinn Interesting about XenonHD. Thats a ROM I didn't use too much. Glad to hear though. I'm sure I can find some time over the next few weeks to build an update. AS long as there are no issues,it shouldn't be a problem.

[fionnb]

@Spookcity I'd like to support the request of @aelfinn . I installed your XenonHD build on 2 S5minis for my kids and apart from some really, really minor quirks it performs outstandingly stable and well.

[Spookcity]

@fionnb I'm glad you brought this up again. I actually forgot. I may have some time today or tomorrow to grab the sources and attempt a build. If successful I will post it here in the coming days.

[aelfinn]

@Spookcity: Thanks a lot in advance! :)

Give us a shout if you could use some bug-hunting help! I have a spare lying around, and I’d be happy to help.

[fionnb]

Actually I do have an issue on one of the XenonHD minis now: calendar provider and contacts provider are both regularly (about every 2 days on average) locking up and all apps that try to use them, too. Force closing them from the Apps Config immediately makes them work again. I already cleaned their caches and data, no no avail. All their data is synced in via carddav/caldav apps. I have installed gapps nano but disabled everything that would sync any personal data with google (except play store). This combo works for me on numerous other phones. I do not know, however, if those c*-provider apps are from LOS or from the gapps package. Do you know?

[Spookcity]

@fionnb Yes, Calendar Provider and Contacts Provider are ROM related apps I believe. I have built an update,so hopefully those issues will be solved. I ended up needing to build this in virtual box as I use Arch Linux and I suppose since it is a bleeding edge distro that some package(s) are broken for building Oreo ROMS. I couldn't get jack-server to start no matter what I tried. Either way,hopefully it turned out OK. It is completely untested.

DOWNLOAD - XenonHD-190113-Unofficial-kminilte

Enjoy!

[Spookcity]

I built AEX 6.4 a bit ago and kept meaning to post it on here,but forgot. So here it is if anyone wishes to give it a go.

Edit: Forgot this is a microG build,so it has everything needed for that. AospExtended-v6.4

[Spookcity]

I overclocked our kernel from 1.4 - 1.6. I also enabled the lower frequencies (200 and 300mhz) Figured some might wish to try it out.

Download 1.6 overclock

[Oleggluk]

@Spookcity Thank you so much for everything! I broke the Samsung in smithereens (hooray hooray hooray, I'm so glad))). I ordered Xiaomi Redmi Note 7 (4/64) for aliexpress. Good luck to everyone, thank you all, I say goodbye to you.

[Spookcity]

@Oleggluk You are most welcome. I hope I was able to make your experience using our little phone a bit more enjoyable...Or at least more interesting.Haha. Thank you for always being a willing tester! I have been due for a new phone for ages now,but am hesitant because I've just spent so much time messing with this phone. I will probably use it until it breaks in little pieces like yours. Enjoy your Xiaomi Redmi Note 7 and good luck to you in the future too!

[aelfinn]

@Spookcity The Pie kernel seems to work well. Haven’t been able to test extensively, especially not wrt battery life. Your AEX-6.4 build isn’t quite up to scratch, I think. Hardware buttons are not working (and the setting to toggle them on/off is missing from settings, even though searching Settings gives it as a result), Tapping on Ambient Display in Settings crashes the Settings app, and the Quick Settings edit button isn’t working.

[MikeTeh]

Hardware buttons are working for me, but I'm missing the hardware button configuration. I'd configured me navbar with most used functions. I think Digital wellbeing needs a configured microg (use ROM only with f-droid)?

[Spookcity]

@aelfinn I also had no issues with the HW buttons on AEX-6.4. I also had no issues with the quick settings edit button,so I'm not real sure what the issue is for you. The ambient display crash happens on LOS 16 as well. I am still not sure why,but am looking into it. @MikeTeh Yeah, I also noticed that Digital wellbeing doesn't work. Not sure why. I will rebuild in the near future and see if it is solved.

[fionnb]

@Spookcity Thanks a lot for the January XenonHD Update! It works pretty well so far (4 weeks, no problems).

[Spookcity]

I built an update for AEX. Latest sources (device and AEX) Download - AospExtended-6.4

I also built AICP. This used to be based on Lineage,but is now based on GZOSP. Not tested Download - AICP-14.0

Enjoy!

[brAvEiitoOr]

Thank you Spookcity for the ROMs!

I wonder if you can build a no-microG version. I could try to build myself, but I have an old PC

[Spookcity]

@brAvEiitoOr Yeah, I can do that no problem. Sorry,I only use microG, so it's just something I just haven't thought to do. Next time I build AEX ( probably a few weeks) I will build a non microG version. AICP will be longer as I don't have the sources anymore, bit I will do that as well

[Spookcity]

AEX update

• Synced AEX sources
• All recent device changes (including working HWC)
• Standard build and microG build

Download AEX-6.5 Standard build

AEX-6.5 microG build

Enjoy!

[MikeTeh]

Thanks for the new AEX-builds. Short reply, I'd installed microG build dirty over version from march, works fine so far, but two things: -sms-app was gone (restored with TitaniumBackup) -I've soft reboots when device is running under high load, fast actions in browser or gallery ie. If I've more time I'll do a clean install, on the weekend I hope.. AICP 14 works fine at the other device, only home button won't wake the device and volume keys control the media volume instead of the ring tone.

Thanks again for your hard work on our device!

[Spookcity]

@MikeTeh Thanks for the feedback. Yeah,I had a random reboot on LOS 16. I think this is still related to HWC. Perhaps it is worse on AEX? I'm not sure. If it is you can just disable hardware overlays in dev options for now. Strange about the messaging app missing. Perhaps I did something wrong during the build. I'll look into it. I'll also try to rebuild AICP at some point and try to fix the home button wake.

Also,I ran across this ROM a few weeks ago and decided to build. It has pretty much every customization option I think one could want. Anyway,here it is. I've not tested extensively.

Bootleggers ROM - 4.4.1

Standard build

MicroG build

Enjoy!

[MikeTeh]

@Spookcity I hadn't the time for a clean install AEX at my main device (disable hardware overlay in dev options changed nothing, freeze and reboot are still there), but I tried Bootleggers ROM with gapps at the second device. Works really smooth, no reboots, it's a nice ROM, I'd never this ROM before. Only I lost my IMEI, hope stock ROM bring it back... ..tomorrow. Then I'll flash also AEX clean.

[Spookcity]

@MikeTeh I agree,AEX seems to have some issues. I am unsure why. There were no problems while building,but along with reboots (I've had a few while using it too) It also just feels somewhat sluggish to me. I Don't know. I will rebuild sometime in the future and see if these issues are corrected. I also agree about bootleggers ROM. I had never heard of this before either,but have been using it the last few days and I really like. It seems very stable as well. Weird about your IMEI. I hope you can sort that out!

[aelfinn]

@MikeTeh How did you lose your IMEI? And what is it now? I have a device too whose IMEI changed to something that appears to get blocked by phone service providers. Haven’t found a way yet to restore it to the original IMEI… :(

[MikeTeh]

@Spookcity First: Flash from Stock ROM brought me back my correct IMEI. I will try it again on the second device with Bootlegger, maybe with MicroG build. Thanks for your information about AEX 6.5, a clean install probably won't do much. The next two days I am on business, in that time I think about going back to AEX 6.4 or maybe try crdroid for now. ..or try another:) In any case thank you for all your efforts!

Finally two curious side notes: -In all AEX Pie ROMs, a backup with Titanium Backup resets the wallpaper here. -file upload in xenforo only works with Firefox and Opera

@aelfinn I made a clean installation of Bootleggers ROM with Magisk 19.2 and gapps pico. How did you change your IMEI?

[MikeTeh]

Clean install only standard build Bootleggers ROM -> unknown IMEI again :(

[aelfinn]

@MikeTeh – I have no idea how the IMEI of that phone changed. It ran LOS 14.1 for the longest time, then I kind of decommissioned the phone and used it as a testing device. Maybe one or another of the ROMs I tested triggered that change. In my case, it’s a well-known IMEI, though: 350695200123951. I have tried flashing a stock ROM, but that didn’t help. Which stock version did you use, exactly?

[Spookcity]

Man,that's so weird about your IMEI. @MikeTeh I highly suggest if you haven't already that you backup your EFS partition in TWRP. I just wiped and flashed bootleggers ROM again out of curiosity and still no issues with my IMEI. I have never had this happen with all of the ROM flashing that I've done. I Just don't get how we are all using the same device,yet this happens. @aelfinn I remember talking to you awhile ago about your IMEI. I'm sorry to hear that you haven't been able to get that fixed. I wish I could offer you more help,but I really have no idea.

[MikeTeh]

@Spookcity I swim in backups :) Restoring only the efs (with TWRP 3.3.0-0) yesterday didn't bring any IMEI back into Bootlegger ROM, I installed Stock ROM, IMEI came back and did a new Nandbackup. I restored this complete backup after the second attempt, IMEI came back again. I tried it with MicroG build - same result, unknown IMEI, very curious, because it works for you. The problem of the second device- I wrote it here or in xda - it loses the connection to the mobile network after about 10-20 sec after the boot, with luck a call succeeds, so I can't test any SIM functions with it (the IMEI of the device matches the IMEI on the package, I also have a s4mini - one of three - with the same problem). Maybe I'll try it again the next days on my main device, wish me luck :))

@aelfinn My main device had CPL1, later baseband updated to CRG3, the second device was already on CRG3 -CPL1 before - because I had the hope to get rid of the mobile network error by stock ROM flash) I always check IMEI first after the ROM flash, I fear the change to another IMEI as it happened with you. Anyway, I know the IMEI recovery is a bit complicated, but you should only flash the stock ROM in front of it. The IMEI can be changed, but the certificate is crucial. This is readable, but you can lose it by wrong procedure. This is what I know about this problem. Addendum: There are some devices on the net, including SM-G800F with the IMEI you specified. Did you see that?

Translated with www.DeepL.com/Translator

[aelfinn]

@MikeTeh – Yes, I have researched that problem for a while. My device seems to have changed to a blacklisted IMEI. I tried flashing the CRG3 stock ROM (via the latest heimdall on Linux), but that didn’t bring the phone’s original IMEI back. You say that “IMEI recovery is a bit complicated”; do you have any suggestions for what I might try in order to restore the original IMEI?

[MikeTeh]

@aelfinn I think there is nothing you can do yourself, ask here, I know him as really competent in these things, more I can not do for you https://www.mhs-solutions.com/

@all sorry for OT

[MikeTeh]

@Spookcity Update TWRP to 3.3.1-0 and lean install cr droid https://forum.xda-developers.com/galaxy-s5-mini/development/rom-crdroid-5-0-pie-t3880298 and IMEI is allready there. Bootlegger is the first ROM with this issue for me, crazy.

Happy weekend at all!