yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] K9100ii:
Wow! I’m not the only one with a brick?

Hi,

So I’m not the only one??? Wow, wasn’t expecting that. Probably not eMMC brickbug afterall. So then, what happened with the ROM, that it is bricking??? Luckily, I have a Nandroid backup on my external SD card, but I’m not going to be able to restore without volume buttons. By the way, does recovery work for you? Maybe you could reflash the 2nd latest build (the one before the latest build)? A dirty reflash would probably work, as it won’t even boot. That one worked perfectly for me with only a few minor issues.
[Galaxy S II Android Development] anton-:
I have tried to repit and install the stable rom version 14.1. The rom works but there is a problem in the partitioning that after install the first app, there is not more space for android. I have tried different repits but without much success.
[Galaxy S II Android Development] Iv4n99:
Hi rlNando

Can you please give us multi-window support?
[Galaxy S II Android Development] philsilvers:
Have you tried this one -

system=1G

data=(you choose)G

sdcard=max+wipe

preload=min+wipe
[Galaxy S II Android Development] maro777:
Hey

thanks, I'll try it out soon and let you know if it works.

---------- Post added at 05:15 PM ---------- Previous post was at 05:08 PM ----------

I also did not have volume buttons.

But I tried to click every second - and the recovery worked.

Unfortunately, the system is still looping.
[Galaxy S II Android Development] bersem:
Had the same after dirty flashing. Endless system looping. Dirty flashed to previous build wipe cache/dalwik and again to latest build.

Maybe something is wrong with latest build.
[Galaxy S II Android Development] bersem:
[MENTION=3742928]rlNanDO[/MENTION] something is wrong with latest build. After putting the phone to charger endless bootlooping with entering into recovery and anymore booting.
[Galaxy S II Android Development] :
I've just installed the latest build with nano gapps and haven't got that issue. So far it is working flawlessly, on and off the charger.

(Clean install)
[Galaxy S II Android Development] wladca:
Bugs (I used version 9):

1. Sometimes the phone reboots (randomly in different situations, e.g. during a conversation or internet suffrage, etc.)

2. The alarm in the clock sometimes does not work (eg how I set the alarm clock for a given hour it rings only when I turn the screen on using the home button, i.e. how I set it at 7:35 and turn on the screen at 7:50, then at 7:50 the alarm is starting to ring and this has happened to me today. I have been testing freshly-grown roms for a week.

3. When I was using the Music Piped application (it supports Youtube) and in the meantime my wife called me, it was not possible to hear the call ringing and talking, only you could hear the music from the music piped.

After these bugs I had to go back to lineage 14.1. There, everything works very well with the same applications.
[Galaxy S II Android Development] rINanDO:
Thanks for the feedback. I can't reproduce the reboot issues, nor the bootloop after dirty flash. My dialydrive s2 is dirty flashed and I have no issues yet... Although I noticed volume control during a call is not working. I'm using the alarm every morning, but my phone is on charger.... I assume yours is not?
[Galaxy S II Android Development] ze7zez:
Have you tried [MENTION=6005084]ripee[/MENTION] build?
[Galaxy S II Android Development] K9100ii:
Are you saying you also have no volume buttons and you got into recovery??? What exactly did you do? Whatever I do, it doesn’t do anything but loop continuously. It would be nice to get my nandroid backup restored and my phone working again. Yes, my phone is still looping. I don’t want it to do it for very long because of AMOLED burn in on the bootloaders start screen.
[Galaxy S II Android Development] Sebastian323:
Hello,

I am new here

I have some questions:

I have installed version 02-24, now the 03-21 is on xda-developers. But in the updater of my S2 I get the message: No

update available. How can I install the newes update without flashing and do all settings again?

I have the Gapps piko on my device. Now I want do Install the google Assistant for using voice-search and dictating.

I can't find it in the playstore and the Playstore-website on my PC sais, google is not available on my S2. I tryed

to register it on the google-Website, but the playstore sais, it is still unregistered. That can I do?

Best regards

Sebastian
[Galaxy S II Android Development] linusdan:
1. The compilation is not official so there is no way to have updates via OTA.

2. Try GApps nano.
[Galaxy S II Android Development] anton-:
I used:

system=1G-data=6G+wipe-sdcard=max-preload=min+wipe-i9100
[MENTION=2222292]rINanDO[/MENTION] I changed to the stable version, not because I am dissapointed with this rom, but because the rom was not usable in my phone. I have not Gapps installed, so this can be related.

I did a dirty install and it was ok, but I had some reboots so I decided to install everything from a clean install and after this, I was not able to boot the phone, all the time was in a loop, like have been described before, I never saw the booting animation of lineage os.
[Galaxy S II Android Development] bersem:
I believe you about that. Had the problem immediately after the first dirty flash. Went back to the old build and again to last build. Everything was in order until yesterday. I connected the phone to the charger and it came back. Endless bootlooping that ended in TWRP Recovery. After a short while, I took another charger and everything was back to normal until the phone was charged. Charger disconnected and the phone began to bootloop again.

It may be that I do not have enough knowledge but I'm not a liar.

Very mysterious the last build.

Should it happen again I have to do a clean installation.
[Galaxy S II Android Development] :
I've no doubt you experienced the problems you described, I certainly wasn't calling you a liar. :)

This is just my opinion, but if problems occur from a dirty flash, I normally do a backup and try a clean flash before submitting bug reports or assuming there is something wrong with a build. Sometimes changes from build to build breaks things when you dirty flash, resulting in strange bugs. A clean flash will often solve these bugs.

I only wanted to provide info that the build seems fine from my experience. Good luck. :good:
[Galaxy S II Android Development] bersem:
Sure.

I do not know if this can help. Here the log file.
[Galaxy S II Android Development] guest4711:
It looks like a crash caused by dirty flashing. Android is looking for providers for FakeBooks and WhatsApp which aren't available. Using the address 0 results in an error 11.

Perhaps you should try booting without simcard inserted. May help.
[Galaxy S II Android Development] philsilvers:
So is it all working well now on 14.1, I'd say 16.0 is awesome in its own right & you should try it again sometime, with the right install method, the right gapps & the right parts, it rocks, don't recommend to dirty flash though, I've always done clean installs, and for the same reason though twrp emu migration recovery is really great, I'd never use it, I use twrp preload compatible recovery by the gangster for all cm's & los's ,this covers everything except cwm for 5.1.1
[Galaxy S II Android Development] wladca:
Yes. My phone is not on the charger. In addition, over night can eat a dozen or so percent of batteries. Linage 14.1 did not have this problem.
[Galaxy S II Android Development] bersem:
I also saw that in the log file, which I found strange. I dont have Facebook APP installed. WhatAPP are installed. Will try :good:

EDIT: The strange thing is that it happens after days.

Hvala u svakom slucaju. Zivio ;)
[Galaxy S II Android Development] a3956978:
Have the same problem with latest build and a clean flash. Did everything from the instructions from the op three times already. Always end up in a boot loop :(
[Galaxy S II Android Development] Sebastian323:
Hello Linusdan,

thanks for your answer.

Is it necessary to wipe everything, or can I only Instal the new Los and the Gapps nano? I would like to keep me settings.

After the thinks I read about the last Version I am not sure, if it is the right rom for me. For me it is importand, that everything works fine. Maybe I wait for the next Update, or is this rom bedder for me?:

https://xdaforums.com/galaxy-s2/development-derivatives/rom-dotos-oreo-t3828987

Would it work with the emulated storage? With rom would you favor? There are so many Roms availlable so it is hard to find the right and the best one.

Best regards

Sebastian
[Galaxy S II Android Development] linusdan:
1. You can do it again with a clean flash and installing the GApps nano.

2. All oreo ROMs do not support emulated storage. You would have to configure TWRP again for physical storage and this involves odin.

I really like Pixel Experience and Resurrection. That's a good start.

If you do not want to go back to the physical because you do not have much time, try Viper ROM.

That is if the clean flash of LOS 16 continues with the problem :)
[Galaxy S II Android Development] ripee:
Or try my lineage 16.0 builds that support physical ;)
[Galaxy S II Android Development] linusdan:
Repartition the memory with the recommended pit (1.5GB + 6GB) that will work
[Galaxy S II Android Development] Gastozz:
3.2.3-0 works with OREO and Nougat?
[Galaxy S II Android Development] ran000:
I have TWRP-3.2.3 working with Oreo. But It is Pie thread and now I am talking about Pie.
[Galaxy S II Android Development] linusdan:
OK! I did the tests with the Android Pie. Here's the List: [MENTION=2222292]rINanDO[/MENTION]

What works beyond the mentioned:

- Sound

- RIL

- ADB

- SDCard

- VSync (i Think)

- Bluetooth

- File Transfer

- GAPPS

- Without Softboots

-Digital Wellbeing

- Battery Life is very good!

- Uninstall applications works!

-Root with the legendary SuperSU works!

Running Partially:

Graphics. Sometimes it gets a blur.

What does not work:

- Camera, Even with Footej

I didn't test MicroG. It should Work.

Tested with TWRP 3.1.0

Pictures anexed :)
[Galaxy S II Android Development] vdhero:
Damn, so impressive. Almost everything works in the first build. Who knows how many build are we away from stable?
[Galaxy S II Android Development] ChronoMonochrome:
[MENTION=8145312]linusdan[/MENTION], [MENTION=2222292]rINanDO[/MENTION],

Hi,

first of all, my congrats for Pie release and thanks for your awesome work!

Can I kindly ask if someone can test if audio recording works properly on this ROM?

In my case (on Ace 2) I've some bug in audioflinger which causes audio not being recorded after second time you try to record it (e.g. first time it works normally but later it doesn't work until reboot).

I've seen some fix in OmniROM gerrit which seems to work around this: https://gerrit.omnirom.org/#/c/android_frameworks_av/+/32302/

It's not merged by LineageOS, btw.

P.s.

Our device has an ancient legacy audiopolicy, whilst this patch is for a non-legacy one, so I'm not sure if it will work properly after porting to a legacy audiopolicy. Anyway, please let me know if you've encountered this bug as well.

Regards!
[Galaxy S II Android Development] rINanDO:
Hi ChronoMonochrome,

I tested audio recording. It works fine with the default Recorder app. Also the second and third time. I just works from Oreo.

I have trouble with WiFi. It connects to WiFi and gets gateway and DNS. I can ping everything in the WiFi network except internet. I got network unreachable when the route of wlan0 is being added. Does it sound familiar?
[Galaxy S II Android Development] ChronoMonochrome:
Ok, thanks, so it's just due to our legacy audiopolicy.

Yeah, I've discovered the same on Ace 2. Also this happens on P preview. For me it was seem to be related to system/netd updates. I've started reverting netd code to lineage-15.1 just to confirm this guess, but I've recently received another phone, S3, and didn't finish this forward port.

[offtop](Quite frustrating to see that for now there are no Oreo and Pie builds for this phone but my main priority is updating an ancient 3.0 kernel to something newer). So dunno when I'll continue working on Pie bringup (now on another phone) and re-encounter this bug (this seems to happen quite likely because S3 is very close to S2).[/offtop]

UPD. About HWC, I've managed to get graphics to work using HWC2OnFb adapter (getting it to work is as simple as removing HWComposer whilst keeping HWC2on1 HIDL, in this case gralloc HAL will be used instead of HWC). This fixed camera (with HWC I'm just getting a black frames in a camcorder preview) for me. Though, some side effects are here - this will cause display getting blank on bootup, unless you remove blank service from system/etc/init (I guess because of unimplemented blank / unblank stuff in HWC2on1 HIDL).
[Galaxy S II Android Development] rINanDO:
I found the commit causing wifi issues! Thanks pointing me to netd. Check my repo of netd for the patch I reverted.
[Galaxy S II Android Development] rINanDO:
New build is up!

Build #2 2018-10-9

Overall state: Stable-ish

Android build: 9.0.0-r10

Updated sources

Fixed Wifi network (by reverting this commit) Thanks to [MENTION=5695278]ChronoMonochrome[/MENTION] pointing me into the right direction!

Fixed Wifi battery drain. (/data/.psm.info stands for PowerSaveMode for Wifi)

Download here: lineage-16.0-20181009-UNOFFICIAL-i9100.zip
[Galaxy S II Android Development] Oxydeme:
I wish you all the possible luck to congrat in this project, personally I only tested r6 and as damn stable ^^

Patiently awaiting for root rights :)

Thanks a lot for Bringing Pie to our old but powerfull device, we are near 2019 and got a Pre Pie rom for our old S2

What else can we ask? :)

See ya.

Oxy'
[Galaxy S II Android Development] GreekDragon:
Dios mio that thing never dies. Still have mine somewhere in the corner, damn OP that thing never dies... damn. [MENTION=2222292]rINanDO[/MENTION] good job.
[Galaxy S II Android Development] xiaoyang2016:
Thx man.It is so smooth:good:
[Galaxy S II Android Development] Zomer123:
Nice!

Very nice to see the good old S2 being worked on to get a piece of Pie. Mine is still running so when root is there (does Magisk work??) I will surely flash.... Maybe root has a problem because of change in partition size does affect this?
[Galaxy S II Android Development] guest4711:
Magisk requires a newer kernel (supporting namespace support e.g.) which we do not have because the proprietary drivers for some hardware are not compatible with newer kernel versions...
[Galaxy S II Android Development] RuKaDa:
I am currently on Oreo of the great S2 Master rINanDO. I have 1GB system partition, to be able to install Pie I will need to repartition with the file you provided, so I just need to flash it with TWRP? No more steps are required?

---------- Post added at 02:24 PM ---------- Previous post was at 02:21 PM ----------

Can you please share this TWRP version? I am still on 3.0.2 and remember that I had some issues with TWRP version (Something regarding with kernel if I recall). I just need to flash 3.2.3-0 as image? Simple as that?

Thanks for your time and help
[Galaxy S II Android Development] ran000:
HOW TO REPIT

make a backup!

get TWRP running on your device.

make sure your battery is mostly charged.

get the zip for your device from the link.

PLUG INTO A POWER SOURCE. this operation might take a long time and must not be interrupted.

flash the zip locally on the phone.

finally, go get a coffee or two. do not, under any circumstance, interrupt this script !!!

in case the script fails to start:

if the script cannot unmount all partitions, it will copy itself to the /tmp directory and ask you to flash it a second time from there.

if it still fails to unmount all partitions, or if it fails to lock the eMMC ('unable to reread the partition table'), then unplug the device from USB hosts such as PCs, reboot TWRP, and reflash the script immediately after boot up. (you may actually need to reflash twice, the second time from '/tmp'.) do not do anything after booting up and before flashing! in particular, do not connect the device to a PC or USB host as this might auto-mount the sdcard via MTP, and do not mount the sdcard as USB mass storage via TWRP's UI. in some rare cases you might need to use TWRP's UI to disable MTP before rebooting and to manually unmount all partitions before flashing the script from '/tmp'.

if locking issues remain, your phone is probably encrypted; this script is not compatible with encrypted phones.

twrp-3.2.3 you can download from: https://xdaforums.com/galaxy-s2/orig-development/recovery-twrp-3-2-1-0-t3740526

or from: https://drive.google.com/file/d/1Qjq2R-xUwsbXtFku2pl5UvCKj2HB0eT4/view?usp=sharing
[Galaxy S II Android Development] RuKaDa:
[MENTION=3331444]ran000[/MENTION]

Thanks for your help and tips. :good::highfive:

Right now I am using Oreo in my S2 and repit (1GB system) was made (with odin files) for old CyanogenMod Marshmallow installation, my current TWRP version is 3.1.0-0 (TWRP-3.1.0-0-recovery-the-gangster-IsoRec-i9100.zip) and what I am asking is if I only need to repit with your zip file in TWRP, wait until finish and flash Pie build?

Do I need TWRP 3.2.3 to flash the repit script or it can be made with my current TWRP version?

Sorry about so many questions, I don´t want to brick my loved S2 :o
[Galaxy S II Android Development] ran000:
Does not matter. In my case events happened in such order:

- flash TWRP-3.2.3 and then work with Oreo some time

- in one session repartition and flash Pie

Good luck
[Galaxy S II Android Development] xywojtek:
Hi everyone!

1. Thank you for this Rom even though I haven't had a chance to test it yet!!! Amazing stuff!!!

2. How to decrypt S2 with Lineage 15.1? I tried to Google this but can't find a proper answer and can't use repartitioning script :(

Regards

xy
[Galaxy S II Android Development] philsilvers:
Just got round to installing build 10 , no problems here, she's sweet, clean installed perfectly, wifi hotspot is perfection, online + offline charging is as fine as ever, fantastic work and thankyou so much dev rlNanDo.
[Galaxy S II Android Development] bersem:
[MENTION=3742928]rlNanDO[/MENTION] Is it possible to reduce the battery consumption? Is a bit high. In addition, the colors are inverted in the screen recording which was not the case in previous builds.

After clean flash had one soft reboot yesterday and the battery was overnight discharged about 60% ( Flightmode ).

Thanks for you hard work :good:
[Galaxy S II Android Development] :
Use betterbatterystats or something similar to find out if an app is keeping your device awake. It may also be a hardware issue.

I have reasonably high battery consumption with data or wifi on, maybe 4-5% per hour, but when I turn data off I'm getting around 1% drop per hour.

I haven't had any random reboots in the week or so since I installed it.
[Galaxy S II Android Development] philsilvers:
Dear rlNanDo or anyone with the knowledge, could someone point me in the direction of phone/settings/calls/call barring, where it is in system? or what apk? so I can strip it down and remove the call barring menu, afaik it's not in the dialer.apk, reason is I don't want it on the phone if it don't work, any help much appreciated, by the way I'm on los 14.1 emulated, but this probably applies to all cm & los ever made.
[Galaxy S II Android Development] :
It would be in system/priv-app/settings/settings.apk, although trying to remove a menu that you never use like that seems to be going to a lot of trouble....

It would probably be easier to modify the settings app before compiling the rom yourself rather than trying to reverse engineer. (but it still seems like a lot of work for no reason to me, just my opinion :) )

Edit: Oh, and please don't post the same question in multiple threads; it's one of the forum rules....
[Galaxy S II Android Development] philsilvers:
Not in Settings.apk, tried that one first, thanks.
[Galaxy S II Android Development] :
My bad, I re-read your post. Try android/packages/services/Telephony
[Galaxy S II Android Development] philsilvers:
OK thankyou, I'll take a look there, regards.

---------- Post added at 10:28 AM ---------- Previous post was at 09:52 AM ----------

Can't find that anywhere in root, unless you mean decompiled settings apk? thanks.
[Galaxy S II Android Development] :
I think that is where the call blocking is in the source code. I didn't have time to look further. It may be that you could remove it from there before compiling the rom, but other than that I'm not sure. Maybe someone else can tell you more.
[Galaxy S II Android Development] philsilvers:
OK, thankyou for your time.
[Galaxy S II Android Development] a3956978:
I think I found the problem, but I am not able to solve it.

When I enter File Manager in TWRP and browse to /data I only see the folders lost+found and media. There is no system anymore. Originally I deleted the storage.xml as described in OP. Could this cause my bootloop?

TWRP failed to restore a backup of my data from LineageOS 15.1. So I used repit to go back to non-emulated storage and then I was able to restore the data backup. But the system folder did not reappear. So it seems this is not part of the backup.

Is there a way to restore the system folder?

Edit: I was able to fully restore my Lineage 15.1 Backup and that booted, too. Now, the system folder is also back in place.

Edit 2: Did the whole process from the OP 1-by-1 again. But still I end up in the boot loop, not even seeing the lineage boot logo once. :( Going back to 15.1 for now.
[Galaxy S II Android Development] philsilvers:
OK I think I found the Call barring title in the TeleService apk but rather than remove the call barring menu, maybe it would be better to shrink the box to 0.0dip, if anyone can help to find the line, it would be great.
[Galaxy S II Android Development] Rendering:
After having installed the ROM, as soon I choose to format microSD card as internal storage, the phone reboots and it is stuck in a boot loop between LineageOS and the bootloader window. Does anybody know why it happens?
[Galaxy S II Android Development] philsilvers:
Did you try installing 16.0 without the backup, installing the backup as well in my view is a sure fail.
[Galaxy S II Android Development] a3956978:
Nope, did a clean install always. No restore of anything on 16.0.

After restored fully to 15.1 and doing repit to non emulated storage, I realized that I had to reformat the internal sd card to f2fs in order to make my phone work properly. Could this be a solution on 16.0 as well? Should I try to format data as f2fs as this contains now also the emulated storage?

Thanks in advance
[Galaxy S II Android Development] philsilvers:
I wouldn't do that, if you have the necessary parts to go back to Stock firmware + Stock repit via odin v3.07 i could tell you my method to come back to los 16.0, i constantly flip from rom to rom on all cm's & los's looking & swapping best parts, and have flashed 16.0 about 20 times now, successfully every time.