yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] gm0:
Nope Gello isn't bad, the only real issue with it is that its chromium base is 17 major releases behind the one of the browser I'm posting this with. A lot has happened since then, including a lot of security issues having been addressed. But going by the LOS blog post they are looking into updating Gello as well.
[Galaxy S II Android Development] jazzl:
As some of you may remember, after installing the ROM on topic I had to go back to 4.1.2 because I had not backed up contacts, SMS´s etc., but had a CWM image of 4.1.2. There I managed to get into a bootloop, and then somehow messed up the phone with Odin or because of unplugging the USB cable and there was no way to turn it on again - 100 % dead. Hence I just got another S2, that works fine and also managed to restore my old 4.1.2 CWM recovery with all the data - great beginning.

And this time I didn´t wanna make the same mistake, so since I for some reason can´t get Kies to work anymore on my PC and Samsung nowadays pretends that Kies never existed but offers Smartswitch instead, I installed that on the tablet - PC version is not compatible with i9100 - and backed up everything to the sdcard and checked that it was there afterwards.

Then I happily did what I´d done with my old phone and got a running Nougat - again. So far so good. Then the next step was to install Smartswitch and that´s where the problems started: Smartswitch won´t start on 14.1 because of failed key verification. Right, I went googling and found out that xposed framework has a module which will let me bypass this verification temporarily. Only problem: Xposed is not yet released for API 25 - only goes up to API 23.

Then I found another solution: Happy patcher, it´s called. Happy patcher did alot of things, but smartswitch still won´t start.

So, would anybody know what´s the easiest solution now? I think I have 3 options:

1. Downgrade to Marshmallow and install xposed framework

2. Downgrade to 4.1.2 and do the whole thing over again with another backup method

3. Do something else under Nougat = ?

Obviously the most prefered option is #3, and the least is #2 which could mess up things seriously one more time.

All inputs appreciated!

Thanks in advance
[Galaxy S II Android Development] gm0:
[MENTION=4159955]jazzl[/MENTION] lol man, still on your odyssey? I had told you though that Kies was unlikely to work on LOS and that you should therefore go with #2, which was the entire point of you originally trying to downgrade after all. ;)

Anyway, as to your #3, you could either try to insert the data from the old SQLite contacts database into the new one directly, or - probably simpler - write a script to export to .vcf which you can then import in the LOS contacts app. You can probably find existing code or apps for that, seems like a pretty standard application.

As to importing SMS, the only way seems directly merging the databases.

Other stuff like audio recordings you can just copy over of course and notes depends on the app you decide to go with, LOS has no default app for that as far as I'm aware.

PS: Doing #2 in an Android emulator might be another option btw.
[Galaxy S II Android Development] ale5000:
You don't get the point, when switching to a different ROM (a lot different) do not use any global backup tool at all.

Images, music and videos can be copied manually.

SMS can be backed up to the microSD with SMS Backup & Restore (and restored back with the same app).

Contacts can just be moved to Google contacts and they reappears automatically.
[Galaxy S II Android Development] Boolian:
There's always the Gello modified "Pyrope" browser which is excellent. (available via PlayStore)

Admiitedly this is on older chromium 42, I think.

However, it is in active development and 54 is due.

The dev is also looking at 'Jelly' which is available as an apk.

Catch up on development Here
[Galaxy S II Android Development] jazzl:
Thanks for your inputs, gives me hopes :) Ok, good idea about the emulator - setting up an S2 clone in Genymotion now. Maybe I can simply put the db´s that I previously extracted in there, and then find the right app for import/export across any ROM.

Flashing an emulator image with CWM won´t work, right?

Do you know which app that can handle db´s from the memo app that used to be on the stock s2 4.1.2 ROM?

For the audio recordings, I think I lost them. I actually saw them sitting there at first when I went back to the old recovery, but then I went to settings and told it that they´ll be on the sdcard instead of the phone. This was not a good idea, and switching back to phone didn´t help. Re-recovering the old image didn´t help either - weird.

I think I have a backup somewhere of them anyway, and they´re not as important as the other data.

---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------

I´ll do what I wrote in my post from a few mins ago and remember to check out that app. Thanks!
[Galaxy S II Android Development] gm0:
Not sure if you can find one compiled for an emulator, can't say. But you still have your Titanium Backup that can extract directly from the nandroid backup so it should not be needed.

I don't even remember the stock app so no, not really. Is it a lot of memos? Otherwise opening the database and simply copy&pasting each memo into your new app might be the overall fastest option. ;)
[Galaxy S II Android Development] fireburner-de:
I am just curious: why TERM ist not set abymore in LOS. It was there in the previos CM Versions.

If it is a bug, is there already a bug report?
[Galaxy S II Android Development] jazzl:
It´s aLOT of memos, and sometimes I go back through them to find something I know was interesting that day, that I suddenly needed :D

For my contacts, I´m good now - found this awesome tool:

http://gsmrecovery.ru/db2vc/

Well, if I could put my CWM recovery on an emulator it´d be dead easy to export the SMS´s from there in a way so that they can easily be read on 7.1..
[Galaxy S II Android Development] gm0:
The reason is because in the meantime adb was changed to start with TERM=dumb set so it was removed from the shell itself.

I can't say I disagree, logically the TERM variable should be set by the terminal emulator for only that one knows its capabilities. So talking about bugs I'd say there's a bug in the terminal emulator (both the one built into LOS and the one you were using). However, there's an additional bug in the nano editor for not working correctly with the TERM=dumb setting. And last but not least there's a third bug in the adb interface for the TERM=dumb variable is only set for the initial user context, once you change context you lose that variable.

So many bugs, so little time. I did not yet check whether there are reports already, feel free to do so over at jira.lineageos.org. Bug reporting is only available on weekends, anyway (edit: of course you could report directly upstream).

In the meantime the issue is easily worked around by the command I gave you the other day. If you want to permanently set TERM=xterm for the default shell you can use the attached zip file, flash it via recovery. It will persist through LOS updates (edit: as long as you do not wipe /system manually).
[Galaxy S II Android Development] gm0:
As I said before, your Titanium Backup can restore those SMS and all other settings (your memos) directly from the CWM backup without having to go through CWM at all.
[Galaxy S II Android Development] jazzl:
Titanium didn´t give me a chance to select the location where my backups were.. I read somewhere else here that it´s a Nougat problem.

Also, it´s not till now I get what you mean; I thought you ment that I could just extract the db files and at least access the data that way, and perhaps find a way to change their tables to work with Nougat, but I think I get it now: You´re prolly saying that Titanium has a function to restore the SMS messages directly into my phones SMS app, right?

Anyway, that´s what I just found out can be done with Nandroid Manager, and it worked perfectly!
[Galaxy S II Android Development] gm0:
Nice one. It should have been possible with TB but as long as you're all set now there's no reason to dwell on it. :)
[Galaxy S II Android Development] keretapanau:
Hi....

Noob question here. Is it normal flashing latest build its take long long long time to finish?
[Galaxy S II Android Development] ale5000:
I thought it was already included with this change.

Am I wrong?
[Galaxy S II Android Development] bujjo53:
No i flashed latest build for 3-4 min..
[Galaxy S II Android Development] gm0:
That change just makes Jelly the default browser for LineageOS's "reference" configuration, but at the end of the day it's up to each device's maintainer what you actually get for that device. In our case we're getting Gello:

https://github.com/LineageOS/android_device_samsung_galaxys2-common/blob/cm-14.1/common.mk#L184
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]: Is it possible to have both Jelly and Gello?
[Galaxy S II Android Development] ale5000:
I have a bug report automatically generated by LineageOS.

Is it possible to submit it privately?
[Galaxy S II Android Development] laptopu:
Latest nightly, got problem with JetAudio Plus app on lock screen.

App should be dark but as you can see it's light and the characters are unreadable. I've wiped cache/dalvik, several reboots, tried wiping app cache and also entire app storage, uninstall and reinstall but no change. This is the only issue I've found with latest build. Any ideas please?
[Galaxy S II Android Development] Nobby1960:
[MENTION=4419266]laptopu[/MENTION]

The player worked with the previous build absolutely flawless?
[Galaxy S II Android Development] laptopu:
Yes no problems at all previously :)
[Galaxy S II Android Development] Nobby1960:
If not, you can download Gello from here - but I'm not quite sure if this is the latest version.
[Galaxy S II Android Development] toy_story:
Hello, in JetAudio Plus, follow the path:

Preferences - Screen - Background color - Select any, except Default (I choose Black)
[Galaxy S II Android Development] laptopu:
​

Thanks that fixed it plus if I go back to default it has corrected itself. Strange how wiping data didn't work.
[Galaxy S II Android Development] toy_story:
Always happy to help.
[Galaxy S II Android Development] laptopu:
You might be on dodgy grounds posting that apk :)
[Galaxy S II Android Development] waterboy55:
hi,

has someone high battery drain overnight, too? I bought a new battery, but nothing changed.
[Galaxy S II Android Development] DevisG79:
For me it's good. I've only high battery drain while using, but because my battery is to old. Which did you buy?
[Galaxy S II Android Development] waterboy55:
I bought "mumbi" 1800mAh from amazon.de, before that I had the original Samsung battery, with the same issue.

My Setup:

LineageOS 20170503

TWRP 3.1

Open Gapps Pico (20170506)

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Android Development] Nobby1960:
Did you tried to wipe cache/dalvik?
[Galaxy S II Android Development] waterboy55:
Ok, this I can try. Thx

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Android Development] Boolian:
Picked up on that recently, 65% drain over 8 hour Deep Sleep.

Only started testing yesterday, so can't comment further.

Possibly dying capacitor.
[Galaxy S II Android Development] Nobby1960:
I thought, if this capacitor is defective, the discharge does happen already in the switched-off state?
[Galaxy S II Android Development] Boolian:
Yes.

If that is your problem, there is a capacitor which can be carefully removed which may cure it.

Also check "cmos" battery for leakage, it an also be removed before damage occurs to the board.

There is a simple enough test with a multimeter on the +/-charging terminals which will give you an indication.

I haven't tested mine recently, just got to find my multimeter!

Read Lanchon's hardware thread HERE
[Galaxy S II Android Development] treysis:
I had the huge drain, even when turned off (turned off consumed almost as much battery as when in deep sleep). So I got into it, removed the (already leaked) battery and the the faulty capacitor (under the microscope you could see it was broken). Removed both without soldering, just carefully with a pocket knife. Now, battery consumption is perfect. Lasts 2-3 days in deep sleep without any use (had it lying on my table without touching it). I bought a Polarcell battery off ebay (wannsee_electronic).
[Galaxy S II Android Development] jazzl:
I can´t tell whether if this is i9100 or Lineage specific, prolly the latter, but I got the following problem: The stock browser crashes when I try to do something with webrtc. For instance, googles https://appr.tc/ will crash the browser. I checked the version, and it´s a pretty old one; chromium 42. This should be more like 58 or 59 considering that we´re using the most recent version of Android. Installing android system webview unfortunately didn´t make a difference. I can for sure use another browser, but I want the webview to work because I´m an app developer, where webview is one of the components in my app, and want to use my old i9100 for hardware nougat testing.
[Galaxy S II Android Development] ale5000:
The browser included doesn't use webview (if I'm not worng).

You have to manually install the browser Jelly to use it (recently added to LineageOS but not on i9100).
[Galaxy S II Android Development] jazzl:
Thanks, would that actually update the webview in the phone?

I tried installing it, but get a crash in Jelly too as soon as I try joining the randomly generated room at https://appr.tc/
[Galaxy S II Android Development] gm0:
How should an app update a system component? Also our standalone WebView is at v55, anyway, which is good enough. But more importantly, you should read this: https://developer.android.com/about/versions/nougat/android-7.0.html#webview
[Galaxy S II Android Development] jazzl:
No, exactly - just wondered how that could resolve what looks like a webview issue. I´m starting to think that it´s not though. Could there be an issue with when mic and cam permissions are requested to the browser? Right now I´m not talking about the app I´m working on, so there´s nothing there in the manifest or elsewhere that should be amended. This is in chrome, stock browser and jelly browser that the crash occurs.
[Galaxy S II Android Development] Nobby1960:
Did you tried the Gello browser (from earlier LOS builds)? Okay, it's an older Chromium engine too (42 somewhere...). I was an this page with it and there is no crash. After I was asked for mic/cam permissions I saw myself via front camera and my day was damaged :silly: ;) But: I have not the latest Lineage build on my phone.
[Galaxy S II Android Development] jazzl:
Thanks nobby1960. That one is replaced by Pyrope, it appears, and my phone fails to install it from the market for no given reason. I think it´s an OS version specific bug. Not there on my old Cyanogenmod kitkat.
[Galaxy S II Android Development] gm0:
Did you read what I linked though? You can switch the WebView component the system uses in the developer options, install the latest Chrome dev build to get the most current. That was to address your concerns about the WebView version.

Back to what you wrote: I can't test this because I have neither Gello nor Jelly on my phone, but since you mentioned the cam I have a feeling that this patch might fix your issue: https://review.lineageos.org/#/c/170623/. It's a bug rINanDO introduced with the March 22 build when fixing a bug with the long press for torch option that causes an exception when code creates an instance of the camera2 app without a looper. If [MENTION=7513127]Nobby1960[/MENTION] is running a build older than that it would also explain why it works for him. Just check your logcat to confirm if it's that.
[Galaxy S II Android Development] Nobby1960:
I also wanted to install Pyrope from Play Store and it failed - after I had uninstalled Gello it worked properly. Both browsers probably do not run parallel.
[Galaxy S II Android Development] jazzl:
Sorry, I forgot to tell that I switched from AOSP, but it made no difference. I´m all new to LineageOS, so I´m not aware of how to install the patch. I tried from TWRP but it gave me an error message. Is the patch part of latest nightly? I´m installing that right now, so let´s see..

EDIT: Latest nightly didn´t fix the issue - hoping the patch can do it.
[Galaxy S II Android Development] gm0:
No, the latest official nightly does not include it, and mostly likely neither will the upcoming build. If you want the patch now you'd have to build the camera2 app yourself from the sources while making sure to include that patch (it has not been merged yet). Alternatively, if you still have a pre-March 22nd LineageOS build at hand, you can also use that. Otherwise you'll have to wait for the patch to make its way into an official build.

Mind you, that's assuming my guess was actually correct. Did you check your logcat? Since you're a developer yourself you'll know how to read a stack trace, it'll tell you why Gello actually crashed on your device.
[Galaxy S II Android Development] jazzl:
Thanks, I will check the logcat at some point and try to figure out what every browser has in common when crashing. Not good at logcats, but I´ll share my findings. Otherwise I´ll wait for the patch - it´s not superurgent. When do you think it´ll be out?
[Galaxy S II Android Development] gm0:
Well, they do have the camera app in common, that's what made me think of that bug in the first place. To help your logcat reading, if I guessed correctly you should find an exception thrown by the registerTorchCallback function of the camera2 app.

Can't help you with an estimate, depends entirely on when the other code reviewer finds the time to do it. Should get merged quickly once that has happened.
[Galaxy S II Android Development] toy_story:
Hello, my friend by mistake.

Installed the recovery, from another phone.

The smartphone does not respond to any actions, even the screen does not turn on.

What can be done?
[Galaxy S II Android Development] MigoMujahid:
No action at all?

No download mode?

Have you tried using a usb jig maybe?
[Galaxy S II Android Development] toy_story:
The latter did not try, the phone did not react to anything.
[Galaxy S II Android Development] MigoMujahid:
Try the usb jig, if nothing happens, then I'm afraid you hard bricked your phone.

I don't know how a wrong recovery can brick your phone, i didn't try that before, but i tried it on a s4 once and it did nothing to download mode, all i had to do is flash the correct one again with Odin, that's weird!!

Edit: sorry i forgot something, try also using Samsung 300k tool for pc, it forces the phone to download mode in phones that have buttons not working, maybe it can help in your case.
[Galaxy S II Android Development] gm0:
Yep, if download mode doesn't come up it sounds more like you flashed the boot loader than the recovery, checked the NAND erase option in Odin or something like that. Good luck.
[Galaxy S II Android Development] ale5000:
Have you tried this?
[Galaxy S II Android Development] Nobby1960:
A wrong recovery can hard brick the phone totally. This happened to me a long time ago. It should go quickly and I had overlooked something.
[Galaxy S II Android Development] Sub_Zero2:
Go to dev options and enable multiple asop.

Might be the issue?
[Galaxy S II Android Development] laptopu:
Latest nightly flashes fine, not tested further yet.
[Galaxy S II Android Development] ale5000:
The official build of 20170315 will probably also works, you can found it here.
[Galaxy S II Android Development] rINanDO:
I already made a fix for this, but it isn't merged yet...
[Galaxy S II Android Development] gm0:
Sure, don't see a problem with that.

Yep, I linked that on the previous page already. Saw you bumped it now.
[Galaxy S II Android Development] jazzl:
Ok, the only trace I can find of camera2 is ./system/lib/libcamera2ndk.so so I guess it´s not just a question of replacing this with the same file in the version that you linked to, which I found and downloaded btw, thanks.

I could of course install the whole 1503 version instead of what I have, but I´m a bit worried about introducing new problems, so I´d rather wait for the updated version of Lineage. I have a ton of other things to work on my app, so it´s not really 1st priority to test it on 14.1 hardware, and at least it´s possible for me to do so under genymotion though that´s of course not the same.
[Galaxy S II Android Development] Nobby1960:
Oops, I don't find this point in my dev settings - my build is probably already too old. Is this the point WebView simultaneous processing? Unfortunately, the English language pack is not on this phone.
[Galaxy S II Android Development] the.gangster:
(You should be able to add an additional language to your phone, aren't you? )

:)

Yes, I guess he means the "Multiprocess WebView" option, which is exactly the "WebView-Simultanverarbeitung" in your screenshot.
[Galaxy S II Android Development] Sub_Zero2:
That's it!
[Galaxy S II Android Development] Boolian:
Yes, it is required to uninstall Gello to install Pyrope.

I also found Titanium does not successfully uninstall but Link2SD does a good job of it.

After an OS update Gello does reappear, but I found it is not required to uninstall again. Pyrope continues to work.

I just 'freeze' Gello.
[Galaxy S II Android Development] MigoMujahid:
Did anyone noticed that Gello and Pyrope gives a lot of errors of "oh snap!", i can't even open XDA website in it!:confused:
[Galaxy S II Android Development] Nobby1960:
Yeah - big thanx at all, my phone now speaks English (much better than I) :D Both browsers have the same file names, so it comes to a conflict. Gello says to Pyrope (and vice versa): Hey, I'm already here - go away ;)
[Galaxy S II Android Development] Nobby1960:
You can't open XDA with Gello/Pyrope? This works well for me (with AdAway), see screenhot - other websites too, without errors. Which default browser do you use?
[Galaxy S II Android Development] Boolian:
Hmm maybe just me, but the latest build seems much smoother & responsive overall.

Interesting, I must delve into the changelog a bit more...
[Galaxy S II Android Development] MigoMujahid:
I mis-posted here, I'm actually running AICP 12.1 not LineagoOS 14.1, the browser there is jelly, I'm not sure what is the issue, i can open it but after it opens it never finishes loading and i get the "Aw Snap!!" error, i don't think i can discuss that here, it's considered as spamming...
[Galaxy S II Android Development] Boolian:
As it's being discussed I thought I'd play with browsers. A reminder that [MENTION=6002018]Ninnix96[/MENTION] (Pyrope dev) has made the Jelly apk available

Here

Please read the Gello/Pyrope development thread for updates and advice on installing Pyrope Here

I currently have the three browsers installed - Gello (Browser 42.0.23) can be re-installed after Pyrope and both work fine.

All three are functioning correctly on the latest nightly, I've not encountered issues.

Except to confirm for [MENTION=286453]Jazzi[/MENTION] - that "Jelly" crashes, or rather stalls with an odd "rewind" arrow icon/frame on the 'https://appr.tc/ test site.

Both Gello/Pyrope load the site correctly.

Jelly is OK but a bit basic and I can't work out how to handle multiple tabs (or they don't work) Pyrope is better IMHO.

Anyway, browser discussion is in danger of straying O/T, so I'll leave it at that.
[Galaxy S II Android Development] jazzl:
I did not mention the arrow, but that´s the default until cam is loaded in webrtc. Are you saying that Gello/Pyrope are loading the site correctly in 14.1? I thought it was an issue with the camera2 component, which would cause any browser to crash.
[Galaxy S II Android Development] Boolian:
Yes, site loads correctly in both Gello & Pyrope

(I didn't try to book anything though !)
[Galaxy S II Android Development] gm0:
The camera only gets accessed once you do join a room (it's free and just for testing, don't be scared ;)), you'll likely experience the crash once you do.
[Galaxy S II Android Development] Boolian:
Challenge accepted and confirmed, it does crash.

Apologies for the misunderstanding.