yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] aschejcm:
EDIT: I did a data format and reinstall, I can now boot.

Thanks a lot for your work!

I have been using your rom since it was released without issue. Yesterday I had my first major problem while using the 2019-08-11 build. While listening to audio books via bluetooth earbuds I attempted to connect my tablet to a wifi hotspot served from the phone. The connection succeded but broke cellular data connection. I did a quick airplane mode toggle on/off which re-enabled cellular data, after which I re-connected my earbuds and started the wifi hotspot. When connecting the tablet again, the phone screen froze, and the phone sub-sequently turned off.

Now I cannot boot into system anymore, the phone reaches the LOS blue horizon-icon, and stays there forever. I can reach recovery and have attempted system+data+dalvik+cache wipe and system reinstall, but still cannot boot. Do I need to do a a data format (or even a repit), or what could be the problem?

Thanks for your help.
[Galaxy S II Android Development] mirhl:
So.. I see that the "plain simplicity" of repit might have been foregone in the past to push for the dandy TWRP-EMU-MIGRATION...

But in the OP you shouldn't now just advertise either that (or its update) for the already on emulated storage case, or the odin freshest of the fresh way for stock. There are also people with middle of the line roms or that would prefer not to need a computer.

Further having "Upgrade from Build 7-13 to Build #14 and higher" first and foremost in the page, and linking somehow an old rom version that nobody should use anymore at the end of the day, is pretty confusuing tbh.

Also, why in 2019 can't we simply delete useless partitions (mmcblk0p11 and mmcblk0p12)? I'm not saying there should be some dynamic selection of the storage scheme (even though, with the magic that primaryStorageUuid is, I guess like it should be possible without much fuss) but every other phone that I know didn't have this issue.

Is it because, again, the kernel is bugged and it crashes down in fire when mounting fails?

Last but not least, would it be possible to have some easy-to-access property to have offline charging be replaced by a simple boot into recovery?

Having to tinker with init.smdk4210.rc on every kernel update would be a PITA.
[Galaxy S II Android Development] abdulhkeem:
is the sim puk issue resolved in 13-09-2019 build?
[Galaxy S II Android Development] S2 Freak:
Hello, great work you're doing. I installed the build from 0707 and it had occasional reboot´s for no apparent reason. I have enabled the double click function on the status bar to standby. After executing this function, the system occasionally restarted. With the build from 13. 09. this was not so far. But with the 11. 08. and the 13. 09. now always the inquiry comes after the PUK and the input after a desire PIN. The only thing that helps is to switch off the PIN query. It would be great if you could fix that. I've been using this as my daily driver since my S5 unfortunately doesn't work anymore. Keep it up.
[Galaxy S II Android Development] GeneV1:
There were no answers so far for the above issue, although there is a lot off traffic on this thread.

Maybe somebody can tell me what the point is.
[Galaxy S II Android Development] noobgs2:
Hi,

As I mentioned a little earlier, I use my GS2 only as music player, but I also got a sim card in it, just in case I need to make a quick call.

I also got the PUK code problem.

Please try to fix it.

Thank you.
[Galaxy S II Android Development] ze7zez:
The explanation is very simple:

Android 9 is not the same as any previous Android.

Security is increasing, and you need to be aware of it.

On Carbon 7.0, Orbot-VPN works fine, so why wouldn't it work on Lineage 16.

The key setting is to enable the "Reachable ports" option.
[Galaxy S II Android Development] Little Rooster:
Hello,

thanks for this rom. It works pretty well. Better than other roms from android 6. to 8. But not as good and fast as the original 4.12 rom. (btw I don't like android 9 because there are too many security restrictions which makes it impossible to automate tasks perfectly.)

Some issues:

1. HDMI / MHL output is not working.

2. Samsung Driving mode is not included.

3. Screen streaming to chromecast breaks immediately

4. Screen streaming to dnla devices not possible

5. No notification access e.g. for task automation a.s.o. (settings: cogwheel is missing?!)

6. Backgound processes of some older apps are terminateing.

7. After disableing "Find my device" it always re-enables silently.

8. NovaLauncher badges counter doesn't work.

9. Downloads stopp when screen goes off (e.g.PlaystoreUpdates)

10.. Phone shuts down in different situations.

11. sometimes message: System UI doesn't response

12. some more I don't remember yet …

build#2019.08.11

So all in all this rom is fine only for using some recent apps which doesn't work on my 4.1.2 system.

Kind regards,

Rooster
[Galaxy S II Android Development] K.D.A:
Dear rINanDO, please forgive me for this question, but I really hope that you will answer it. In the distant month of March, you wrote this message.

Please tell me how are you doing in this direction? The latest firmware versions are very good and thank you so much for the work done! She is really priceless !!! All users of Samsung Galaxy S2 in Russia are very grateful to you! Just like all Samsung Galaxy S2 users on the planet.

I'm just worried that with LineageOS 16 the same thing will happen with LineageOS 15, because LineageOS 17 will be released soon.
[Galaxy S II Android Development] hagadus:
Amazing Rom! Works fine, THX! Best greetings from Düsseldorf
[Galaxy S II Android Development] boscorama:
Hi,

I tried this ROM following instructions in first post and was coming from your LOS 14.1 ROM. I had massive heat and drain issues and sluggish UI. I figured I'd wait a little bit for another update to try again.

Surprise! I re-pit'd back to what I had for 14.1 and now LOS just hangs on the boot animation. Is there something I need to do additionally/differently in my re-pit to allow me to revert to my LOS 14.1 nandroid?

Thanks for all your work and I look forward to using this ROM too. :good:
[Galaxy S II Android Development] Catfish78:
Hello,

i've installed it on my four i9100 from different versions an builds. It must work on your phone :) . Just retry it and don't be shy for asking for help if something won't work while flashing. Did you do exactly the steps as described in Rinandos post?

Regards
[Galaxy S II Android Development] Matombo:
How do i undo the changes made by the pid file of this rom?

even after i pushed my backuped original pid and flashed the stock rom again, i still have sdcard0 and sdcard1
[Galaxy S II Android Development] ze7zez:
Back to stock

>Here< you will find a detailed step-by-step description of how to get back to the stock ROM.
[Galaxy S II Android Development] rINanDO:
Unfortunately I haven't been able to focus on making it official due my private situation. Don't worry about new ROMS. I still post monthly updates here I still use a S2 as my daily drive phone.
[Galaxy S II Android Development] kipphebel3:
Thank you so very much for your work and yur detailed instructions!
[Galaxy S II Android Development] rINanDO:
Great... I just try to investigate the pin code issue but before I got started, my SIM was already unrecoverable locked.... Can anyone give a logcat of the radio ( logcat -b radio) with the pincode issue? It should give me some hints what changed since build #13. Now I wait for new SIM to arrive.
[Galaxy S II Android Development] S2 Freak:
-------------

Hi, after a few more days of using the build from 13. 09. I can say that it runs very stable - without reboots and problems. The only two small errors I noticed are the PUK error and the fact that you don't get a notification when you receive an SMS when your phone is in standby. Only when the display is reactivated. Is that generally the case with Android 9? (I use the PICO-Gapps) Otherwise TOP - keep up the good work.

Because of the logcat: does this have to be executed during startup (when the query comes) or is that enough during running operation? Sorry about the question - but I'm only a beginner. Greetings
[Galaxy S II Android Development] boscorama:
Yes, I followed his first post religiously ... several times. Apparently the 4th or 5th time was the charm. :p

Still seeing some sluggishness in the UI and slightly elevated battery usage but it seems like it is behaving now. [MENTION=2222292]rINanDO[/MENTION] is there anything we can report to help address the usage? Reports from BBS or WLD or ... something else?

BTW, thx [MENTION=8941925]Catfish78[/MENTION] for helping me pull my head out of my "you-know-what" and actually get this running. :highfive:
[Galaxy S II Android Development] SethGeckoXDA:
Instructions can be found here. You should catch the log as soon as possible after the issue occurs.
[Galaxy S II Android Development] SprigPlantar:
Just asking, are you working/planning to work on LOS 17 for this amazing device?
[Galaxy S II Android Development] GeneV1:
Thanks for the reply.

I took a look at the "Reachable ports" option in Orbot and found the entry "*.80;*.443".

Unfortunately, I have no idea what else could be entered here.

Regarding Carbon 7, I don't habe any experience. Maybe I'll find the time to test it.
[Galaxy S II Android Development] mirhl:
No version of anything is the same of its previous version, the explanation is pretty bogus.

VPNs working only up to nougat makes me suspect Tethering Hardware Offload may be involved (you should be able to disable it from developer settings)

Also, yes Q is already in the work if you check OP's github. He started to work on it basically as soon as he released the last build.
[Galaxy S II Android Development] S2 Freak:
PUK Issue Radio Logcat

Hello rINanDO. I got the Logcat. Can I attach it somehow - like an e-mail? I didn't find this. The text is too long to insert.
[Galaxy S II Android Development] K9100ii:
On "quick reply", choose the option "go advanced". Reply there with the logcat uploaded by using the "attach attachments" option in the options under the message feature.
[Galaxy S II Android Development] ze7zez:
You just have to check the box next to "Reachable ports". And that's it.
[Galaxy S II Android Development] S2 Freak:
Hello again. Now I have the problem that only the normal "Replay"; is shown where no extended options are available. But I think I've seen "quick reply"; before? A

Browser Problem? I'm using Firefox. Any tips?
[Galaxy S II Android Development] K9100ii:
No, don't worry, it's not a browser problem. :) I use Firefox for Linux here and have no issues. If you use the "normal" "Post reply" function, there will be no "Go Advanced" reply option as it is an option only on the "Quick reply" function and if you're using the "normal" "Post reply" function, you will already have the equivalent of "advanced mode", the "manage attachments" option would be under "Additional options" which is below your usual options where you input your message, title and so on.
[Galaxy S II Android Development] GeneV1:
Sorry, there is no checkbox next to "Reachable ports".

"Rechable ports" kann be tapped on and an input line for text opens.

The current entry is "*:80,*:443".

---

Update: After freezing and unfreezing Orbot (weanwhile testing successfully another VPN) it suddenly works.

Maybe because I also activated the checkbox "Rechable Adresses".
[Galaxy S II Android Development] ze7zez:
Sorry, my mistake. It should be "Reachable

Addresses". I don't use Tor and I only did the test

for you.
[Galaxy S II Android Development] Xanth0k1d:
Hi, was trying to compile as well, but facing some errors, wonder if anyone can help me out.

I suppose its because of a new gcc version....

Here's some of the errors,

ALOGE("Could not ion_unmap %s", strerror(errno));

^

hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:184:45: error: use of undeclared identifier 'strerror'

ALOGE("Could not unmap %s", strerror(errno));

^

hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:160:50: error: unused parameter 'module' [-Werror,-Wunused-parameter]

static int gralloc_unmap(gralloc_module_t const* module,

^

hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:195:10: error: use of undeclared identifier 'strcmp'

if (!strcmp(name, GRALLOC_HARDWARE_GPU0))

^

hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:197:15: error: use of undeclared identifier 'strcmp'

else if (!strcmp(name, GRALLOC_HARDWARE_FB0))

^

hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:364:49: error: unused parameter 'module' [-Werror,-Wunused-parameter]

static int gralloc_lock(gralloc_module_t const* module, buffer_handle_t handle,

^

hardware/samsung/exynos4/hal/libgralloc_ump/gralloc_module.cpp:365:40: error: unused parameter 'l' [-Werror,-Wunused-parameter]

int usage, int l, int t, int w, int h, void** vaddr)

build env is lxss ubuntu 16.04 lts on windows 10

thnx

^
[Galaxy S II Android Development] kipphebel3:
Hav never compiled for Android, but that sounds a bit like you forgot to include "string.h"
[Galaxy S II Android Development] Xanth0k1d:
I'm a real newbie to this kind of thing, I only played around with linux before...

Never compiled any softwares before.

How do I included string.h btw?
[Galaxy S II Android Development] kipphebel3:
Linux is no different in this respect. This is a C issue. Did you follow the instructions setting up the project? What is the command you type when compiling? Running make?

Did you follow the build guide for your device? What device?

https://wiki.lineageos.org/build_guides.html
[Galaxy S II Android Development] GeneV1:
Thanks for your support.

But it looks like my previous success message was premature.

Working VPN can not be reproduced.

So I'm stuck with the problem again.

I have no idea, what else to try (except changing to a different ROM).
[Galaxy S II Android Development] ze7zez:
Orbot Tor in Android 9 on Samsung i9100

I don't want to dirty this thread.. Read >this<.
[Galaxy S II Android Development] S2 Freak:
PUk Issue Information

Hi rinando, I just want to mention that the PUK error was already present in the build from 11.08. if it helps with the search. I had installed this only one day before the one of 13.09. and therefore did not report any more. Both I had installed "dirty" - that is via TWRP with clear cache and dalvik. So from 07.07. to 11.08. and then to 13.09.

By the way, the battery life is very good by now. Greetings and many thanks for your excellent work.
[Galaxy S II Android Development] Xanth0k1d:
Yup I did, but the guide was only for 14.1 so I changed the branch number accordingly and cloned the required repos on my own...

After including string.h in the cpp it still does not work, anyone have any idea what's going on?
[Galaxy S II Android Development] Sub_Zero2:
Have a look at a lineage-16 guide for another device. It might be that you are just missing a linux package that has changed since lineage 14. (If you compare the guides, you will see that some of the required packages to build lineage has changed).
[Galaxy S II Android Development] K9100ii:
[MENTION=8145312]linusdan[/MENTION] has already made manifests for building 16.0: https://github.com/linusdan/lineage_manifests This is what you need to use unless you want to make your own manifests. The device configuration files, kernel and so on have been updated/changed for 16.0 in several of [MENTION=2222292]rINanDO[/MENTION]'s repositories, using a guide from LineageOS means that these things will be for 14.1, even if you use parts of a guide for a device on 16.0. A lot has changed in 16.0 since 14.1.
[Galaxy S II Android Development] Xanth0k1d:
Okay, much thanks:laugh:
[Galaxy S II Android Development] Xanth0k1d:
Thanks guys, got it going until 80% now.

My goal is to eventually compile my own version of aosp haha

---------- Post added at 04:31 PM ---------- Previous post was at 04:25 PM ----------

By the way if I want to pass a low ram property I just list it in system.prop?

Yup, build complete, thanks guys

---------- Post added at 04:37 PM ---------- Previous post was at 04:31 PM ----------

Just one more question, why won't the lineage repo for i9100 work though, they had branch # lineage 16.0:confused:
[Galaxy S II Android Development] rINanDO:
The lineage repo doesn't work by itself because android_hardware_samsung is not updated with my commits. You should use my version.
[Galaxy S II Android Development] :
[MENTION=2222292]rINanDO[/MENTION]

I apologize if this forum is not of this device.

try flashing i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img on my S2 D710 and it worked, but before flashing this kernel, (kernel-Lanchon-TRIM-IsoRec-20160112-cm-11-d710) and it works fine and I'm going to try the rom LOS 16 to see if it starts.

basically this device has the same chipset as I9100:D

edit:

picture
[Galaxy S II Android Development] Trev@s:
Hi all; tanks to Rinando for the great work.

Yesterday and today i have a new issue, after a call to the same contact my phone stay freez, i must have to reboot and after the reboot i have the puk code back.

Please Rinando continue your fantastic work, I9100 never die.
[Galaxy S II Android Development] cikenkari:
Last build with Blutooth not able turned ON, hope will be fix on next build
[Galaxy S II Android Development] ze7zez:
If you look at the end of the report

adb bugreport> i9100_bugreport.txt

then the last action is

DUMP OF SERVICE usb:

which indicates the reason for the restart.
[Galaxy S II Android Development] rINanDO:
That is weird... Are there more users with this issue? I'm using Bluetooth daily with Spotify. Can you provide a logcat?
[Galaxy S II Android Development] DevisG79:
Bluetooth works good for me. Tested with different Bluetooth boxes and all is fine. Also performance is good for me. I disabled security alerts from trust. When using the phone battery drain is a bit high. I think that's normal for this 8 years old phone. But when not using the phone battery life is very good.:svetius:
[Galaxy S II Android Development] rINanDO:
Good to hear. Dunno if we can improve better battery in use. Already disabled ksm so it should be slightly better. Further we use zram fully because we need more memory. Can't disable this. ;)
[Galaxy S II Android Development] DevisG79:
Don't worry. All is fine. You made and make a very good job. Disabling ksm and using zram is a very good idea. Don't disable zram. In normal usage battery is ok. I think it's only in high usage. Let's say when you do many things at the same time. I will watch it. Because of the age, I would say it is more important to keep performance alive.
[Galaxy S II Android Development] MaRtYy01:
Hi guys,a few weeks ago I decided to revisit android 9 after messing around with older android versions for a while and I must say the latest build with microg feels so much better than the one I used 2 month ago. Animations don't lag anymore,system feels much more responsive as it barely slow downs. The video recording bug is fixed as stated in the changelog and I must also report that online video playback is greatly improved-it still works slowly but it eventually play whatever I wanna watch properly,unlike last time. I think it works slowly due to low ram or something related to hardware limitations but thats fine. Multitasking works fine. I just can't find anything wrong to report. A small thing,when I scroll through fb lite and youtube and video previews start playing it gets a bit laggy but whatever,I don't mind it. It's probably due to hardware limitations as well. Here is a link to the microg flashable package that I used:

https://xdaforums.com/android/development/microg-unofficial-installer-t3432360/amp/

Please don't bother with gapps just to get the google play store working. It just screws up the performace quite a lot. With microg google stuff still works,only google play doesn't work. If you have the knowedge to install this rom you probably know how to sideload apps anyway(apkmirror,etc.). Also for browsing I can only recommend the built in browser and opera mini. Mozilla and chrome run significally slower. Currenly typing this from the S2 with yt vanced(playing music),fb lite and messenger lite in the background without any problem.

---------- Post added at 07:42 PM ---------- Previous post was at 07:37 PM ----------

Forgot to add,I picked up a second hand extended battery-kinps 4500mah for 2.5 euros,right now I easily get 6 hours of sot with normal usage or more if I just watch videos(with original one and the garbage bluestar one I got just above 2h). So my advice if you see a similar battery for a reasonable price dont think twice to get it.
[Galaxy S II Android Development] kienvoc2k3:
someone give me a link of repit 1.5gb

someone please give me a link of repit 1.5 gb system plzzz
[Galaxy S II Android Development] ran000:
Look thread, please: https://xdaforums.com/showpost.php?p=77809531&postcount=18
[Galaxy S II Android Development] guest4711:
Have a look at [TOOL] Lanchon REPIT: The Data-Sparing Repartitioning Tool For Android - https://xdaforums.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036/post66344372 how to rename the archive to adjust the parameters ...
[Galaxy S II Android Development] ran000:
Hello

My subj playing unlimited loop music notification when switch on/off USB/power cable. Does anyone know the setting for this notification and a way to stop it? Only reboot - the way I find at moment.
[Galaxy S II Android Development] ran000:
Another interesting observation of my subj: I found that wi-fi is switched on!!! after I have switched it off!!! ( I have checked the situation some times ). Which application switched wifi on and how I can switch wifi off fully?
[Galaxy S II Android Development] rINanDO:
It is the Wifi location switch in Wifi settings which keeps it active. Turn it off.
[Galaxy S II Android Development] ran000:
Thank for pointing me in right direction, I find the setting, it is - Setting, Network&Internet,Wi-Fi,Wi-Fi preference,Turn on Wi-Fi automatically
[Galaxy S II Android Development] ran000:
I find the setting, it is - Setting, Sound, Advanced, Charging sounds, Enable. So I could disable the setting, however, I could not find a way to stop play music notification if it is enabled. Any suggestion?
[Galaxy S II Android Development] blobbo_Oo:
FM radio

Hi, thanks for your work.

FM radio app is working?

If not, any chance to port it?
[Galaxy S II Android Development] mirhl:
At least up to cm12 it was all perfectly smoothed and working.

Then a lot of framework changes happened in android of course, and spirit fm dev (the only aosp fm radio application dev) is no more.

With him, I don't think it's all that far fetched to say the whole field died.
[Galaxy S II Android Development] rINanDO:
Spirit FM is working but you need to copy the radio kernel module Si4709_driver.so from /vendor/lib/modules to /system/lib/modules.
[Galaxy S II Android Development] mirhl:
I see.

How difficult would it be to add it officially to the rom fixed?

Or.. I mean, I know LOS already has its own official application, but afaiu that's only compatible with qcom api.
[Galaxy S II Android Development] ChronoMonochrome:
Hi,

I've been working on i9300 LOS 15.1 bringup recently, and I've noticed a camera breakage after commit https://github.com/ChronoMonochrome...518bd1b#diff-b7ed115ff8ee236aa7e748778b8062d8 . Seems that i9300 gralloc and other drivers heavily rely on some legacy mmap implementation (I've been facing various similar issues with camera when I've been working on LK 3.4 too).

Forcing kernel mmap to use a legacy implementation (surprisingly) fixed it:

https://github.com/ChronoMonochrome...mmit/16695f7ed8406b6ca47dc95ad83376ff8681b19a

I don't know if it's related to those changes to display drivers (I'm trying to merge these changes to LOS 15.1), but maybe that can help.
[Galaxy S II Android Development] rINanDO:
Thanks for the info.For i9100 camera's including video recording is already fully functional in LOS 15.1. In LOS 16.0 I already fixed front/rear camera preview picture and rear take picture.