yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] kadov:
My too :(
[Galaxy S II Android Development] Nobby1960:
Try an update to the latest build from 05/17, you find it here. Perhaps it solves this problem.
[Galaxy S II Android Development] Boolian:
If you find it's not build or app related, read through posts on this page of the thread for suggestions.

Page131
[Galaxy S II Android Development] jazzl:
Just wanted to confirm problem solved with webview after updating lineageOS to latest build - thanks to whoever should be creditted in any way for this :)
[Galaxy S II Android Development] EmmaWLove:
LineageOS 14.1 is best rom. thanks

1- Please replace the pixel launcher with default LineageOS launcher. pixel launcher is Very good.:

https://play.google.com/store/apps/details?id=com.google.android.apps.nexuslauncher&hl=en

2- Messaging app LineageOS 14.1 Do not allow to be disabled .I've installed Messaging apps from Google Play but Messaging app LineageOS 14.1 can not be disable.I currently have two Messaging app :D
[Galaxy S II Android Development] MigoMujahid:
For the launcher suggestion, he can't, it's LineageOS sources that can't be changed, unless he made an unofficial build and did that.

Anyway, you can download pixel launcher and use it, and disable trebuchet from settings>apps>(press menu button and choose "show system"), but remember, don't move pixel launcher to system app if you're going to disable trebuchet, or you will get in a big issue after you update the ROM.

Btw. Aroma Gapps package may have an option to replace stock massaging app with google messenger, never tried it though, so I'm not sure.
[Galaxy S II Android Development] gm0:
But that's not the reason. You can change LineageOS' sources just fine, but what you cannot do is replace them with Google's copyrighted content. So nope, no Google launcher in the LineageOS distribution. ;) But a you said, the end user can always install one themselves.

I have a feeling you may be confusing LineageOS' messaging app, which is for SMS/MMS messages, with text chat apps. They do not replace each other because they serve different purposes.
[Galaxy S II Android Development] the.gangster:
Don't use Playstore for that.

I explained it already several times, how to modify your GApps installation and even used Pixel launcher as an example here.

It will be installed in /system and without any issues.

You can also control googles app-replacement behavior or can additionally tell the installer which stock apps to remove. It will also survive ROM updates.
[Galaxy S II Android Development] MigoMujahid:
I tried installing Pixel as a system app once, and disabled trebuchet, after updating i didn't have a home launcher because Pixel was removed, i used playstore back then.

A small question, how does GApps install apps in system and they don't get removed on ROM updates?

What is the difference between GApps installing to system and the user's installing to system?

Always wondered about that :rolleyes:
[Galaxy S II Android Development] the.gangster:
the small answer: it's already explained :)

No, honestly, the longer answer:

OpenGApps has a very powerfull installer which also creates the according add-on.d scripts to make the GApps survive ROM updates.

(Plus it checks all the dependancies and only performs the given config if they are met and safe. If you follow the links you should finally be on the project's page where all the logic, behavior, keywords, ... gets explained.)
[Galaxy S II Android Development] gm0:
Maybe to expand a bit on that: TWRP will execute all shell scripts placed into /system/addon.d before wiping /system and installing a ROM. This allows you to e.g. backup any file from /system to another partition (typically /tmp) and restore it to /system after the ROM has been written. Of course you can also have it perform more complex operations where necessary (like make modifications to files from the new ROM, e.g. build.prop).
[Galaxy S II Android Development] nospamboz:
Stay awake catlogs

I used "catlog" to record the logs, extracting the relevant time spans. Phone is set to lock on sleep, then put to sleep with the power button. Plug phone into charger, bringing up lockscreen. For the wall charger, it goes back to sleep after ten seconds. For computer charger, it doesn't.
[Galaxy S II Android Development] Imphinium:
Nope, it doesn't.
[Galaxy S II Android Development] Nobby1960:
Have you also a battery drain, if the phone is turned off? If yes, there is a broken capacitor on mainboard. First check this.
[Galaxy S II Android Development] Imphinium:
Well, another ROM named XenonHD solved both problems. I think there might be an issue with the CPU, because when the trouble started, the apps took minutes to start (specially youtube)
[Galaxy S II Android Development] a666:
Can you to add this one line patch to enable more wifi settings on our device:

https://github.com/dorimanx/Doriman...mmit/f88f0217a4e5d53d421338ae8bad2eff55adfa01
[Galaxy S II Android Development] the.gangster:
I really doubt that changing Mac addresses should be a standard option.

It can cause a lot of trouble in networks.

And honestly most use-cases may have a flavor of being considered barely legal.
[Galaxy S II Android Development] ale5000:
Is there a place where are explained all the subprojects inside Lineage OS?

For example I see they have added LineageOS/slackbot but I have no idea what is it for.
[Galaxy S II Android Development] gm0:
It's quite possible that there is an issue with the CPU governor. On Sunday I had my CPU going crazy while the phone was supposedly idle, sucking my battery dry in about 2 hours and burning a hole in my pocket as hot as it was getting. A reboot didn't fix things. . Since I didn't have time yet to investigate further I ended up just flashing a previous build and things went back to normal.

---------- Post added at 20:31 ---------- Previous post was at 20:25 ----------

Well, as it says, "rtmbot plugins for lineageos slack instance". But what does it matter to you?

---------- Post added at 20:48 ---------- Previous post was at 20:31 ----------

Agreed about a standard option exposed via UI, but that's not what that was about, it was just about patching the kernel to support MAC address changing at all, which I support. And since you would not be able to change your MAC while connected to a network there's no risk of causing trouble in networks. At most you could cause trouble for yourself if your network authenticates via MAC.
[Galaxy S II Android Development] a666:
This is low level setting, provided by broadcom, why not make advatages of this feature little more accessible?

To use it you need to edit text file in system folder. there is very similar feature in nexus device, so even Google think its ok
[Galaxy S II Android Development] cal002:
Static MACs are privacy risk since they can be used for tracking.

The IEEE explores he possibility to move to random MAC addresses.

And wpa_supplicant already seems to supports it.

And spoofing a MAC address is so easy, thus they are already not reliable.

Probably it's enough to put

"ip link set dev wlan0 address 12:34:56:78:9a:bc" into /data/local/userinit.sh

(but I haven't tried).
[Galaxy S II Android Development] ale5000:
I'm curious :)
[Galaxy S II Android Development] Nobby1960:
Uhh - take care, I see a big headline in all newspapers:

Samsung SII exploded - one suspects operating system

After the failure with the Note 7, Samsung has again a problem ... etc.:p :laugh:
[Galaxy S II Android Development] gm0:
edit: post removed. Wrong place, wrong time.
[Galaxy S II Android Development] nospamboz:
Maybe too soon for that joke? :(
[Galaxy S II Android Development] laptopu:
Yes poor taste joke given what's going on in UK this week.
[Galaxy S II Android Development] MigoMujahid:
yes indeed, what happened in UK either made by ISIS or not is just against all manners and against all religions.
[Galaxy S II Android Development] Kurt Krummbein:
For a human beeing, this is just insane.

Commiting suicide is not a sign of mental health, but pulling down innocent people, children !!!, is insane! Branewashed!

All religions deal with life and how to spend his life in a society with other people. None with killing himself or other people!

Inocent people go to heaven, their murderers to hell. May they burn until infinity.

Gtz

Kurt
[Galaxy S II Android Development] gm0:
Apologies if I offended. I didn't mean that reference as a joke - killing people can never be funny no matter the context - it is rather that in the suggested event of a code change leading to exploding smart phones I consider the likelihood of this being due to malicious intent to be just as likely as mere accidental causes. In particular given recent events.

However, in hindsight I'll agree this was neither the time nor the place to make that statement, and I hope it will never have to be. In the meantime I removed my above post.
[Galaxy S II Android Development] the.gangster:
Last 20170524-Nightly running good so far.

(btw: don't give "them" a platform here and let's continue considering obvious (even if bad) jokes a joke instead of bashing people here)
[Galaxy S II Android Development] rINanDO:
Hi everyone,

As some of you know I'm currently working on the BLN code. The new code is ported in the original touchkey code. However some cleanup of depricated code needs to be done also. So I have to disable BLN support temporary. The chances are that the next official build doesn't have BLN support. Don't worry, it will return.
[Galaxy S II Android Development] Draky50110:
Is it normal if Yahoo weather can't connect ?

I'm using it with LOS (weather settings).
[Galaxy S II Android Development] MigoMujahid:
install this as an update to current clock app, and you will find built in weather providers, no need to install anything from play store ;)
[Galaxy S II Android Development] ale5000:
Does this fix our export issue?
[Galaxy S II Android Development] MigoMujahid:
Happy Ramadan to all of you guys.
[Galaxy S II Android Development] dpcdpc11:
Hey guys... short out of topic... I'm trying to update TWRP on my old S2 from 2.8.1.0 to the latest or to at least version 2.8.7.0 so I can repartition the system using REPIT so I can finally install LinageOS.

I've tried everything including Odin and Heimdall Suite and nothing worked.

I would appreciate any help... thanks in advance!
[Galaxy S II Android Development] the.gangster:
You're right. Kind of off-topic here.

You've tried everything, but reading.

Read (and post) here

The key-word is you need an IsoRec-kernel to launch the IsoRec-Recovery. Forget ODIN to flash the recovery. Use my Zip (signature!) instead or take the "flash img"-way described in the OP there. Find more background-info and temporary kernel-downloads there.

EDIT: If you just wanna go to a TWRP2.8.7.0 (like Nobby1960 described in the next post) you can also flash that kernel with this ZIP. But that kernelembedded TWRP will be gone after flashing a ROM again.
[Galaxy S II Android Development] Nobby1960:
Try to flash the attached stock kernel with built in TWRP via Odin and then repit again. After the first running of Repit you get an error message. Then jump to the tmp folder and flash it again from there.
[Galaxy S II Android Development] Sub_Zero2:
It's normal for me after some time here on my s2 and s4...

A reboot fixes it
[Galaxy S II Android Development] Boolian:
Bit of a bizarre crash there.

On reboot it had reset my Status Bar battery icon to default, removed Developer Settings & set Privacy Guard notifications back on.

Well, that's all I found so far. Bizarre.

No logs of any worth either... no panics, nada.

Meh - Clean build in a few days I think.
[Galaxy S II Android Development] gm0:
Sounds like the system settings stored in /data got lost one way or another (is it cmsettings that stores this stuff? not sure off the top of my head). Since you probably didn't wipe them intentionally that's a bit strange, indeed (could be due both to software or a data loss on the flash memory itself). Check your app permissions and in particular data usage limitations (if any), those might have been lost, too.
[Galaxy S II Android Development] Boolian:
Yeah, Finally trawled through the event log etc. Missed a bit last night as the date/timestamps were defaulted 01/01.

Anyhoo, yes, much of it was screwed permissions and Compatibility Test Suite chatter (I'm not familiar with)

Can't really pinpoint exact cause, a few pointers to specific memory address errors. Just the weirdest thing.

Seems to be primarily the default CM settings as you hinted.

Most, menu settings defaulted. Other than that, all other functions were recovered.

Privacy Guard permissions seem to have recovered as well, but I haven't time to trawl em all.

I'm not too worried. I'm just going to rebuild on my spare test device and test the dodgy one when I have time, I think there are hardware issues...

Cheers.
[Galaxy S II Android Development] Draky50110:
Can't install because conflict :(
[Galaxy S II Android Development] Nobby1960:
Yes - in the folder system/app/LockClock exists a file named LockClock.apk. You first must delete or rename this with a root file manager (ex: Root Explorer).
[Galaxy S II Android Development] ale5000:
Well, you can just get Weather providers here.

I'm using OpenWeatherMap and it is working perfectly.
[Galaxy S II Android Development] Nobby1960:
You can also try to flash the attached file - the script is not from me, credits are going [MENTION=8052153]toy_story[/MENTION]. I only zipped in the latest LockClock.apk (from Ressurection Remix).

Hint: The weather widget often doesn't refresh in deep sleep mode. In Settings/Battery/Battery optimization set it on "Don't optimize", see screenshots.
[Galaxy S II Android Development] Draky50110:
Ok, thanks for all help about weather providers :)

Another bug :/ : can't download anything in Chrome on my i9100 be cause "no sd card" o.O
[Galaxy S II Android Development] thearczoro:
Thank so much you guys {devs and i9100 users}. Nice to learn about custom roms in SGS2 section. My first SGS2 (dead already) then my second SGS2 (totally is dead too, tonight). Keep develop good rom for i9100. :) I got my new one.
[Galaxy S II Android Development] MigoMujahid:
just curious..

as far as we all see, the S2 lives for a long time, did u lose the 2 phones in a short time?

enable the storage permission and then force stop Chrome then open it and try again.
[Galaxy S II Android Development] thearczoro:
Nope, I lose the fisrt one in early 2016. Yeah, I'm glad my second S2 can use 7.1.2.
[Galaxy S II Android Development] MigoMujahid:
well, you should make sure you bought a good one, the S2 is a "business phone", it can stand heavy using for a bit long time.

the boards might have been faulty in your case... assuming they died on their own without any outside damage (falling, breaking...)
[Galaxy S II Android Development] thearczoro:
Yeah, that's why I stayed with my S2 for a long time. Because, I like this phone. True, mainboard fault no other damages.
[Galaxy S II Android Development] Ansgar​:
Hi guys, thx for the great rom development since CyanogenMod :good:

I got a problem with recovering Whatsapp Database (Backup) from Stock Android 2.3 to LineageOS newest.

I saved Folders from old Whatsapp (actual Version), database[..].crypt12 and media files.

Pasted Files in internal Memory on LineageOS, where whatsapp created the folder.

Now i got Media and backup database, deleted every database except newest and removed data from file title.

Cleared Data/Cache, reinstalled Whatsapp.

Whatsapp has permission to read Files, granted at app startup.

It doesn't recognize the Backup, just verifies mobile number normal and old chats arent there.

Also I cant create new local backup, get an error.

- Are there any Logfiles which could help u to recognize the problem?

- Anyone an Solution?

Regards,

Ansgar
[Galaxy S II Android Development] todonormal:
Because you don't work with Google Drive? https://www.whatsapp.com/faq/en/android/28000019
[Galaxy S II Android Development] gm0:
[MENTION=8309476]Ansgar​[/MENTION] why not ask WhatsApp support about it? This thread here is about LineageOS.

As a general piece of advice: Cherry picking only some application data files and even renaming them (at least I assume that's what you meant by changing their title) and then wondering why the app does not recognize them should not come as a surprise.
[Galaxy S II Android Development] ale5000:
[MENTION=8309476]Ansgar​[/MENTION] [MENTION=8075440]gm0[/MENTION] [MENTION=4121808]todonormal[/MENTION]

It is a backup done by the app, it should work and it always worked before.

I had the same problem but I think Whatsapp won't give any support for custom ROMs (it say something in a message on first run).

So someone should replicate the problem with a stock ROM.
[Galaxy S II Android Development] gm0:
Should they have broken something in a recent version just revert to an earlier version. Either way, entirely unrelated to LineageOS, that's all I'm saying. I can recommend Titanium Backup for your backup & restore needs by the way, helped me transition my app data across various ROMs numerous times and saves me the trouble you are describing.
[Galaxy S II Android Development] Nobby1960:
WhatsApp doesn't even support if a phone is rooted. [MENTION=393855]ansgar[/MENTION] [MENTION=5627087]ale5000[/MENTION] - it's important to install exactly the WhatsApp version with which the backup was created. The encryption of the database changes with newer versions and you have no more access.
[Galaxy S II Android Development] gm0:
[MENTION=7513127]Nobby1960[/MENTION] nice to see you mention [MENTION=393855]ansgar[/MENTION], thought I was seeing things when the same thing happened to me earlier (because that's the wrong user, right one is [MENTION=8309476]Ansgar​[/MENTION]). Apparently the site's user names are case-sensitive (terrible idea!) but the code parsing the mentions when you post doesn't know that and converts to the first case-insensitive match it finds. Interesting bug. ;)
[Galaxy S II Android Development] MigoMujahid:
granting storage permission in startup doesn't actually "Grant" it, you need to restart WhatsApp after the permission is granted.

to avoid that do the following:

1- clear WhatsApp data and cache.

2- enable all WhatsApp permissions from the app info.

3- force stop the app then Open it.

---------- Post added at 10:19 PM ---------- Previous post was at 10:15 PM ----------

i wouldn't consider it a bug, i would consider it a "Second chance" or maybe a third, fourth, or fifth....

if you're a new user and your favourite user name was already taken, you can capitalize a litter or two to pass the registration, that's cool btw ;)
[Galaxy S II Android Development] gm0:
I wasn't calling the case sensitive naming system as such buggy (just a terrible idea), just the lack of case sensitivity in the @ mention parsing (i.e. if you type @ Ansgar it will automatically convert to @ ansgar when you post it - that's quite certainly a bug).
[Galaxy S II Android Development] MigoMujahid:
oh, really?

i didn't know that this is what happens, yes that's definitely a bug.
[Galaxy S II Android Development] Nobby1960:
Thank you, I was wondering - after saving, the first letter was small again and again, I typed Ansgar :)
[Galaxy S II Android Development] ale5000:
This remind me another bug, when I grant permission to record audio to the screen record app the first time it still say that it is missing.
[Galaxy S II Android Development] MigoMujahid:
yes, actually it still happens to me in a lot of apps.
[Galaxy S II Android Development] Nobby1960:
I noticed it by chance after I flashed a stock ROM, I could not remember exactly the original background lighting of the two LED buttons. Only if you touch the LED buttons there is a short backlight, not if you touch the screen. LineageOS has not managed this trick yet. Is it possible to fix this? If you flash the BLN mod, there ist a timeout function for the LEDs, but only over the whole screen.
[Galaxy S II Android Development] Switch123456789:
Good news, a fix has been merged yesterday :)

https://review.lineageos.org/#/c/174642/
[Galaxy S II Android Development] rINanDO:
Yes, I noticed that too. I have even implement this behaviour already in my experimental kernel code under led_on_touch-file.
[Galaxy S II Android Development] ale5000:
New build.
[Galaxy S II Android Development] rINanDO:
Edit: Touchkey brightness lights settings are not working yet in this build. The option is available but not yet operational. The LEDs are still working
[Galaxy S II Android Development] ale5000:
The lights are just disabled?

Is it safe to use or it can cause problems?
[Galaxy S II Android Development] rINanDO:
I updated my incomplete post. It is safe to use. Under settings->buttons you have a new slider for button brightness, but it is not fully operational. You can only turn the buttons on or off.
[Galaxy S II Android Development] the.gangster:
:)

Even if [MENTION=2222292]rINanDO[/MENTION] replied already while I was still taking screenshots.

It's safe to use and button lights are now working within their regular use. (just brightness not working yet)

So even without bln-mod you can now control again the timeout by the settings-menu.

What he did was to remove BLN support to completely rework on it.

So if you used it so far be prepared to currently see errors in Synapse.
[Galaxy S II Android Development] bersem:
Can anyone confirm download problem trough updater ? It stops many times at download end. After 4-5 try it successfully download the update file

Gesendet von meinem GT-I9100
[Galaxy S II Android Development] Boolian:
Yes, I had similar problems.

I decided just to wait for next weeks build.
[Galaxy S II Android Development] aminya:
Hello guys, I use cm12.1 and it is as stable as hell and great battery. how is the state of this rom? is there any specific issue? battery?
[Galaxy S II Android Development] Boolian:
It's a daily driver - I gave my opinion to the same question Here

(*Root not neccesarily required* )

There are more sophisticated battery saving and handling options. I wouldn't return to CM12, more up to date security releases for starters!

Just type "Stable" into the thread Search Bar and there are many results with useful info. You could also try searching "Issues" (the latest primarily about the new "Jelly" browser)

OTA Nightlies are resolving bugs and improving the Rom weekly.

Join the LineageOS family, it's the future...
[Galaxy S II Android Development] jojobg:
Small amendment from my side. It is the present :) what is the future about we will see around the corner ;)
[Galaxy S II Android Development] todonormal:
Excuse me
[Galaxy S II Android Development] MigoMujahid:
yes, what is it?
[Galaxy S II Android Development] todonormal:
I need confirm because i have problems with the last version and camera... only my 9100?
[Galaxy S II Android Development] gm0:
That's a bit unspecific to be of help. But no, I have no camera problems that I know of with the latest build.
[Galaxy S II Android Development] gm0:
Question of my own: Does anybody know of a way to use a POSIX file system on the external sdcard when mounted as portable? It seems parts of the ROM including the entire storage API are hardcoded to expect a non-POSIX file system and thus choke on the permissions. adb works fine though, seems it comes with its own code. Found one bug report on Jira that was brushed off rather rudely with basically a "we don't care if it works or not".

Was wondering if anybody knows if there is a way around this without having to fix the code itself.
[Galaxy S II Android Development] dwarf_hero:
Last Rom is working great.

Is there any change that in near future we will get new funcionality - privacy controlling and blocking numbers for phone/text like in cm 13? I like that very much. It gives me full control with blocking unknown/private numbers and gites info about potencial fraud
[Galaxy S II Android Development] gm0:
That's already in, it's called call blocking in the phone app's options. I don't think you can blanket block all unknown numbers though, just individual numbers.