yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]: Isn't it possible to exclude the MTP components that crash until is fixed?
[Galaxy S II Android Development] rubentkato77:
Hey I noticed that too. :rolleyes:
[Galaxy S II Android Development] Boolian:
Good to know, I'll check it out. Thanks.

I tried other batteries claiming high capacity, they turned out to be just re-wraps. The best tested at around only 100mah+ more than standard, so I gave up on them.
[Galaxy S II Android Development] Nobby1960:
This file was always been here, but hidden. I guess it contains backup infos, if nandroid backups are in this folder.
[Galaxy S II Android Development] max6698:
How did you test? If my battery is just a re-wrap, I'd rather people know that before they spend any money. BTW I found Galaxy S2 batteries on ebay which claim to be 5000mAh.
[Galaxy S II Android Development] rINanDO:
Tried it but the ROM bootloops.
[Galaxy S II Android Development] rubentkato77:
Latest build 19/01/2017 runs great :good:
[Galaxy S II Android Development] the.gangster:
... except for at least the FM (Tuner) driver to be broken here now, too.

Read before already that the same had happened on AICP as well.

Also there are some commits for other devices where FMradio had to be reenabled again. If I saw correctly they all were for QCOM_FM. Not sure (not at all!) but I think to remember we have a Broadcom chip (althogh the spirit-based FM-Tuner-Apps show a menu setting for QCOM Antenna so maybe I'm wrong with Broadcom). So maybe it's just some cherry-picking that is needed to reenable it.
[Galaxy S II Android Development] rubentkato77:
Well, yeah that, I don't use FM Radio. But it was working in AICP
[Galaxy S II Android Development] the.gangster:
So you tell either [MENTION=5495967]p3dboard[/MENTION] or me a liar?

:-/

He tested it out: broken since 20170114.
[Galaxy S II Android Development] rubentkato77:
No mate, my english is bad, did not ment to tell you liars.

I was con AICP and had FM radio 3 installed. But I think after 01-15-2017 it got broken .

Maybe missed under stood me mate.:good:
[Galaxy S II Android Development] laptopu:
[MENTION=2222292]rINanDO[/MENTION] latest rom looking good thanks, like others say spirit for fm radio not working but sure you'll be on that.

I wanted to know if su and superuser flags are same thing and what's different from marshmallow? I'm trying to get helium backup working which is a clockworkmod aop, it gets stuck checking for superuser but the # appears and is definitely enabled. Nexus users say it's working fine on their ROMs from a quick peek over there so I'm wondering if a quick tweak on our ROM would fix things?
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]: The latest build works perfectly.

PS: Trebuchet and CM backgrounds still have the CyanogenMod icon.

PS2: CM Updater and CM backgrounds need name change.
[Galaxy S II Android Development] Nobby1960:
FM radio (Sprit2) doesn't work for me too in this build. Same issue as in AICP.
[Galaxy S II Android Development] jojobg:
You didn't read the information regarding the commit for change for SU right ? Rinando have mentioned it in his post.
[Galaxy S II Android Development] Wachicamo:
Got a few things from [MENTION=2222292]rINanDO[/MENTION] latest build:

1-Battery Icon in Text mode (Not a big deal tho):

When you set for the first time the Battery Icon to "Text mode", it shows like this:

[IMG="Battery_Icon_Before_Reebot"]http://s24.postimg.org/w2yzn3kmt/battery_before.jpg[/IMG]

But, if you reboot the phone, it goes back to normal:

[IMG="Battery_Icon_After_Reboot"]http://s24.postimg.org/m9hsaaiid/battery_after.jpg[/IMG]

2-Backup Settings:

In AICP ROM, when you set up your G Account, all the basic settings (Display, Sound, Saved Networks, etc), are restored, including the App settings. I tried to use it in this ROM, and there's no option to restore your settings, neither the Apps. I checked on Google Drive for backups, and I saw this:

[IMG="Backup_Settings1"]http://s24.postimg.org/lmngyib05/backup_settings_1.jpg[/IMG]

There are multiple backups from different dates, and none were restored. Just for your information, I have the Automatic restore enabled by default:

[IMG="Backup_Settings2"]http://s24.postimg.org/4kumwew51/backup_settings_2.jpg[/IMG]

Is there a way to force the restore settings besides any third party apps? I'd prefer to use the default feature rather than doing a Nandroid backup and restore it manually.

3-Touch to Focus on default camera:

The last 2 builds (3 including Lysergic's build), Touch to Focus has stopped working like it should be. You can't manually focus the image for some reason. If you tap the screen, it does nothing. But, if you use any third party camera (Google Camera), it works ok.

4-Drop down the music volume when a notification arrives (Not a big deal):

In CM13.1, there was an option under "Do not disturb" settings, that you can set if a notification will lowered down the music for a moment. I can't find this option anymore, I know that you guys are adding features gradually, but I hope this one can be added again in the future.

So far, the ROM works as expected. No FC, no random reboots, battery drain is good. Thank you for leaving SU enabled, I'd appreciate the information after I've noticed that SU (Apps only mode), wasn't there anymore.

Keep it up the good work, guys!
[Galaxy S II Android Development] Nobby1960:
Which Google Camera do you recommend? The only one that runs here without problems under Nougat is version 2.1 (photos and videos). You have to disable the default camera in the app settings.
[Galaxy S II Android Development] laptopu:
Yes but that hasn't solved my problem which is why I asked.
[Galaxy S II Android Development] Wachicamo:
I have Google Camera 2.5.052 installed (Play Store installation) + default camera. I didn't disabled the default camera tho.
[Galaxy S II Android Development] MARCOSOFT:
Google Camera from Play Store installation?!

In mine it does not exist!
[Galaxy S II Android Development] Nobby1960:
[MENTION=4296222]MARCOSOFT[/MENTION]

Strangely, all Google Cameras are probably already longer in Play Store no more available. But here you can download them as apk.
[Galaxy S II Android Development] p3dboard:
Hi [MENTION=2222292]rINanDO[/MENTION], I am wondering if this commit in lineageos is the cause of the fm radio issues? It was created on 13th of January and was a kernel compile change for arm kernels.

https://review.lineageos.org/#/c/156252/

Aicp had the FM radio bug since the 14th of January and it uses lineages device sources so aicp and lineages will be experiencing the same kernel bug I assume
[Galaxy S II Android Development] andyhers:
Is it possible to add "double tap to wake" like in miui 8 ? I guess it's kernel things, but if it can be done, then it will be great
[Galaxy S II Android Development] Andrea900:
Next time try Fuel Gauge [Root].

By the way, your experience is sadly useless, because you're still using a very old and (certainly) exhausted battery. There is an Anker battery (1900mAh) on Amazon, try it and share your thoughts/judgments.
[Galaxy S II Android Development] MARCOSOFT:
Google Camera 2.5.052 Android 4.4+ is the best apk for our S2 running 7.1.1 device?

I've tested other newer versions, 2.7, 3, 4 ... and none worked correctly!
[Galaxy S II Android Development] Andrea900:
I can confirm. It's the newest, and fully functional Google Camera version for our device.
[Galaxy S II Android Development] Andrea900:
:good:
[Galaxy S II Android Development] tha_G:
Thanks for the tip about Fuel Gauge but why would you want to do that if you can improve things with just some "smart" recharging?

Useless?

I disagree,

- Firstly, I presume a lot of our colleagues I9100 owners do have an old battery in their phone and might improve things a lot with this simple trick.

-Secondly, all Li-ion batteries do have some circuitry that controls max charging and discharging of the cells, the values it acts upon can also shift with newer batteries so again this trick could really help.
[Galaxy S II Android Development] Andrea900:
A faulty battery could lead to a lot of troubles like yours, your method (and others) is simply unreliable because of that (rom problem? Hw problem? BATTERY?).

Furthermore, FuelGaugeTool is the only sw that can calibrate our S2 battery, because of its particular hardware .
[Galaxy S II Android Development] AchiNo:
According to the LineagesOS Homepage they are about to roll out the first weaklys this weekend. Wipe is recommended, but there will be a experimental migration release for legacy cm users.

[MENTION=6159291]Lysergic Acid[/MENTION] and [MENTION=2222292]rINanDO[/MENTION]:

Since repartition is mandatory and a wipe is recommended too, has there been any progress or any decision about whether or not we are going to migrate to emu storage? Or will it be some form of [MENTION=4141005]Lanchon[/MENTION]'s approach, where those who want emulated storage can choose through a flag in the data partition?

And thank you all for all the awesome work you guys have put into this and for keeping our devices alive and updated till this day! :good:
[Galaxy S II Android Development] rINanDO:
I'm currently testing a new PIT with max data partition, and modified twrp (replacing cm recovery). I will share this experimental build soon. We better wait before we have everything tested and setup for (optional) emulated storage, eg. new isorec builds for twrp, proper migration script or manual, etc.

---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------

Confirmed this commits breaks the radio fix. Thanks!
[Galaxy S II Android Development] Pier_89:
Hi [MENTION=2222292]rINanDO[/MENTION] thank you for your work !

What's the difference between emulated or/and not emulated storage?

Which between the two do you prefer?

Regards.
[Galaxy S II Android Development] laptopu:
Would emulated storage mean no actual storage partition, instead of having system data and storage we would just have system and data? Then storage would be emulated on data? I can see lots of positives to that.
[Galaxy S II Android Development] Pier_89:
I hope it doesn't mean that we've to format sdcard0..
[Galaxy S II Android Development] laptopu:
I may have not understood emulated storage but even if you had to wipe storage it's not a big deal, just connect to a PC or get a cheap otg adapter and move everything into USB stick, or get an SD card to save storage on. Then repit, format and restore.

The biggest advantage of this is not battling with losing space when installing apps to the phone and having to repit when data partition gets low, plus most stuff saves files to storage partition but take videos and they can use data partition.
[Galaxy S II Android Development] Boolian:
Testing the battery capacity is a bit too involved to explain here and is O/T. Battery discharge over time requires a little circuitry and test meters. I think you can find capacity testers online, also Diy build a circuit board.

Old reclaimed original Samsung batteries get rewrapped with different make and hahaha, yeah maybe 5000mah printed on.

Old batteries get rewrapped with Samsung labels showing original 1650mah but maybe with a new date stamp. More difficult to tell, as the cell is still old original.

Peel off wrapper and find laser etched Samsung details.

Also fake test by weight etc. Big difference in weight (lighter) is fake or old reclaimed cells.

No real way of knowing before purchase.

Best discussed/ investigated elsewhere.

---------- Post added at 05:56 PM ---------- Previous post was at 05:52 PM ----------

Lanchon started a good thread Here
[Galaxy S II Android Development] Lanchon:
read this:

https://xdaforums.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651

yes you have to. but this will very probably be an opt-in feature.
[Galaxy S II Android Development] Lysergic Acid:
I'm doing test builds and uploading on AFH, you can use them if you want but be cautious :)

You can flash it over like a nightly
[Galaxy S II Android Development] laptopu:
I think emulated card will be slight annoyance at first having to format but I can see so many upsides to it that it's got to be done, weighing up pros and cons it's a no brainer emulated is the way forward.
[Galaxy S II Android Development] Lanchon:
for those interested, i reply to rINanDO here:

https://xdaforums.com/galaxy-s2/ori...ch-emulated-to-emulated-t3539651#post70661639
[Galaxy S II Android Development] laptopu:
Interesting reading on emulated storage, would [MENTION=414800]arnab[/MENTION] need an update to twrp so a data wipe would leave emulated storage alone?
[Galaxy S II Android Development] the.gangster:
[MENTION=4419266]laptopu[/MENTION]

Yes, for sure. But that's also already explained (and should be discussed) in detail there, isn't it?
[Galaxy S II Android Development] max6698:
Thanks for your reply.

I peeled off the wrapper. There are no etchings. My original battery weighs 32.4g. My Link Dream allegedly 2500mAh battery weighs only 28.5g which is suspicious.

Whatever the real capacity, I'm pretty happy with the 2 days I'm getting out of it at the moment with Lineage OS 14.1. It was never that good with CM 12.1 or any earlier OS.

:)
[Galaxy S II Android Development] Boolian:
Yup, definitely not 2500mah. Just can't squeeze more juice from a much lighter/smaller cell. Modern manufacturing can make them marginally lighter, a gram or two here and there, but not hugely. It's likely to be just 1650 and a copy.

It will probably be good for a while and noticibly better than an old cell (even if less than 1650mah)

But it may degrade quicker.

I agree LineageOS 14 seems better on battery. Probably the more aggressive doze settings and new power profiles.
[Galaxy S II Android Development] FakrudeenAhamed:
Hey guys, check out the most used devices list by lineageos.org ,

https://stats.lineageos.org

S2 is around 60+ (280 plus s2 devices), though old still this phone rocks!!! :good:
[Galaxy S II Android Development] rINanDO:
Yes, twrp needs to be build with additional flags.
[Galaxy S II Android Development] tltan86:
agree, it's been a long while google camera app cannot be found in play store; but if you search through browser, its still there. weird. ha.
[Galaxy S II Android Development] Pier_89:
[MENTION=2222292]rINanDO[/MENTION] I can see Samsung devices here: https://download.lineageos.org/.

Maybe we'll be the next to join it? Sorry for ETA but I can't wait about it ! :D
[Galaxy S II Android Development] reepje123:
I think we will need to wait for another day. They are currently having problems which could last about 9 hours.

And when the servers are running again, the S2 is #79 and they're are currently at #39. So this will take a while..
[Galaxy S II Android Development] Pier_89:
Do you think only one day?

If it's so, it'll be perfect ! The last "UNOFFICIAL" day for our device?

I hope that ;)
[Galaxy S II Android Development] Klaerchen:
It's not a problem of Galaxy S2, but a fault in LineageOS. It will be fixed with:

https://review.lineageos.org/#/c/157099/

I tried it, works very well.
[Galaxy S II Android Development] Pier_89:
Finally we've Lineage Official Rom for our devices!

Someone tell me how do we do with lineage-14.1-20170125-experimental-i9100-signed.zip ?

Can we update from Unofficial ? Even if I don't think so...

However [MENTION=2222292]rINanDO[/MENTION] [MENTION=6159291]Lysergic Acid[/MENTION], could we update with this release, any particular issue for initial startup?

Regards.
[Galaxy S II Android Development] Achi92131:
I flashed official after a full wipe. Device now bricked. I can boot to odin mode but not to recovery anymore :(
[Galaxy S II Android Development] ale5000:
What are the difference between nightly build and the build of rINanDO?

Are there some patches that are present in the build of rINanDO and not in the official build?
[Galaxy S II Android Development] SimonBell:
I tried to install nightly official twice, and twice i had to restore my s2 from bootloader 'cause recovery was bricked

Waiting for fixes
[Galaxy S II Android Development] pronti:
From the lineage website:

Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.

Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.

This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly

This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data

This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.

The process for this installation will be as follows:

Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).

Reboot

Install LineageOS weekly build

Reboot

Re-setup your application permissions

Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.
[Galaxy S II Android Development] Chemudan:
This not working. Even clean install the bricked device.
[Galaxy S II Android Development] Achi92131:
What is the best way to fix it ? Flash kernel and TWRP in Odin again ? Or only TWRP ? Thanks guys !!
[Galaxy S II Android Development] dii86700:
Flash kernel and TWRP in Odin again then back backup from TWRP.

---------- Post added at 10:17 AM ---------- Previous post was at 10:13 AM ----------

What's wrong with official release Linage? Whay recovery bricked?
[Galaxy S II Android Development] Doncra:
Only problem can't get to boot loader message " low battery can't download " and phone will not charge because of no kernel..... thanks official lineage... any suggestions what I should do.......
[Galaxy S II Android Development] Doncra:
To flash with oden I need the tar files and I don't know where they are.......
[Galaxy S II Android Development] Achi92131:
Same problem here [emoji20]

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy S II Android Development] forfriends:
Same problem here. Phone bricked :(

---------- Post added at 23:48 ---------- Previous post was at 23:28 ----------

So to fix it I had to flash back to stock (download from many websites like http://www.sammobile.com/firmwares/) using Odin then reinstalling CWM -> CM13.0 -> TWRP->repit->CM13.0->opengapps...

Really annoying but that's what I gotta do. I think I'll wait a few weeks/months before trying LOS14...
[Galaxy S II Android Development] dii86700:
Go in this site http://galaxys2root.com/cwmtwrp-recovery/ then download cwm recovery for odeon then instal this recovery after that with cwm recovery instal twrp recovery and instal cm13 with gapps if don't have backup
[Galaxy S II Android Development] Pier_89:
Any news about new official build to fix this first one?

Shall we have to wait another week to flash it?
[Galaxy S II Android Development] Andrea900:
Immortal.
[Galaxy S II Android Development] Pier_89:
Are you going to update to official?

I don't think it's possible.

Where are you seeing this screen?
[Galaxy S II Android Development] SerenityS:
Rom status changed into OFFICIAL.

Thanks to [MENTION=2222292]rINanDO[/MENTION]'s effort.
[Galaxy S II Android Development] Nobby1960:
No problem, I attach the needed file - TWRP for Odin. Good luck!
[Galaxy S II Android Development] Shambles22:
Why first 14.1 nightly doesn't work? I had the same issue of other s2's users that tried this first official build
[Galaxy S II Android Development] Lysergic Acid:
Lineage has signing issues right now, I recommend everyone to don't install the first nightlies lol
[Galaxy S II Android Development] Pier_89:
[MENTION=6159291]Lysergic Acid[/MENTION] Any fix about this release?

Shall we wait another week for another build?

I hope there'll be released a new one soon :)
[Galaxy S II Android Development] RedMi92:
Hi, i was using the la test cm13. Today i tried to flash lineage official ROM via twrp: when i rebooted to system i got the Samsung screen with the yellow triangle and stuck. So i used heimdall to flash boot.img kernel of the cm13, and also the officiale twrp.img. lineage then started as you can see in the photo, but it remains stuck on the bootlogo charging.

I have long time ago repitted the phone with lanchon repit (1gb system, 10 GB data, 4gb sdcard). I only do fresh installs with the latest opengapps pico package.

Have you some ideas about what to do? Meanwhile i will roll back to cm13, thanks in advance
[Galaxy S II Android Development] andyhers:
La said don't use the official for now. I'm using 20170119 and seems work fine till now.

I was upgrade from cm13 to this build only with wipe cache/dalvik and so far still good as daily driver.
[Galaxy S II Android Development] betexino:
I have tray to install the last build but stuck at i9100 logo ..... ... flash cwm for kikat with odin + lanchon isorec trim zip with cwm + lanchon isorec 2.8.7..0 also with cwm + reboot twrp installed twrp 3.0 then i restaured my rom backup .... ucan use trianglaway apk to remove the warning message

sorry for my bad english
[Galaxy S II Android Development] I0tacle:
Yap, same with me. Have read the warning about half an hour too late. Let's see how I get the crap back now. I also do not understand why the apparently defective builds are still downloadable. There will be more S2 briked unnecessarily. :(
[Galaxy S II Android Development] max6698:
I've just compiled my own lineage-14.1-20170126-UNOFFICIAL-i9100.zip. It's the first time I've ever compiled android. Given that I used the same source code, or near enough the same source code as lineage-14.1-20170125-nightly-i9100-signed.zip, I would be nuts to install it on my S2 wouldn't I?
[Galaxy S II Android Development] rogers11:
Good question. Noone seems to be responsible.
[Galaxy S II Android Development] max6698:
FYI: the very first post in this thread says:
[Galaxy S II Android Development] SerenityS:
Set link rINanDO's rom temporary.

It will be change when official build working normally.
[Galaxy S II Android Development] rogers11:
A bad excuse to appreciate this type of approach. Just my feeling of course.
[Galaxy S II Android Development] Pier_89:
Will be there official nightlies or weekly? I'm confused about it.
[Galaxy S II Android Development] Syaani:
Weekly I think
[Galaxy S II Android Development] Pier_89:
Just see here: https://www.cmxlog.com/14.1/i9100/

It says "Nightlies". I hope that :)
[Galaxy S II Android Development] Syaani:
Yeah but do they build those builds "every night"? Let's call them RANDOMLY
[Galaxy S II Android Development] kamal.rana:
I want to disable proximity sensor.....I have two questions...

1) how to disable it? .

2) will this affect my ROM performance negatively ?
[Galaxy S II Android Development] Klaerchen:
It's strange.

I build the ROM regularly, also 20170125 from the official repositories. I could update my S2 without trouble. So, I don't understand what's really the reason for all the trouble, why it is working for some, and not for others.

Is there a way, to track the reason of the problem?
[Galaxy S II Android Development] max6698:
Thanks for the info Klaerchen! I'll try installing my build tomorrow, after I have a backout strategy of course :)
[Galaxy S II Android Development] Spyr0s:
Root for whenever official is ready

https://download.lineageos.org/extras
[Galaxy S II Android Development] John D J:
Does anyone know if the ota installation is functional without problems please? Because I downloaded via cmupdater just wondered if it won't crash everything?
[Galaxy S II Android Development] Spyr0s:
don't install, first official nightly will brick your phone
[Galaxy S II Android Development] John D J:
OK thank you good to know.?
[Galaxy S II Android Development] Nobby1960:
Phew - dangerous thing, rename this build as "Killer App" ;)
[Galaxy S II Android Development] MigoMujahid:
You mean "Killer Build" :D
[Galaxy S II Android Development] Noctis Lucis Caelum:
Official support!!!

Well done guys....