yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] gm0:
You mean gps.conf? I don't know that app so can't comment on that but I am using a customized gps configuration myself and it's something you only really need to do once: just place a script into /system/addon.d to backup and restore the configuration file automatically when you update the system (just take the 50-cm.sh script as a reference if you need).

Probably a simple reboot (maybe pulling the battery first) would have fixed it as well? Not sure if you saw it but a couple of users were saying they also had failing sensors after long uptime or something, was discussed about 2 months back IIRC. At the time I was wondering whether it might be due to apps being installed that might be accessing the sensors in a bad way, but that's a shot in the dark since I never ran into the issue myself.
[Galaxy S II Android Development] Boolian:
Yeah, just a simple app to customise gps.conf (I just did it manually. Flaw in the app with 14.1 I think) Will probably use a customised backup/script in future.

In hindsight, I also thought maybe a simple solution may have worked rather than re-install.

I frequently swap spare batteries and reboot, so maybe not that, but probably the Dalvik/cache wipe would do it.

I recall a lot of the GPS posts (even the static nav discussions) I didn't recall the degredation over time reports though, I must be getting old!

Also, I'm installing nightlies, usually weekly, so I'm not sure about long uptime degradation.

Possibly, it's actually the opposite and it's the low battery shutdown/replace battery up to 3 times per day (!) that's doing it...

I checked a second, test S2, with latest Lineage nightly and it had no issues. Of course it's not used as much and has fewer apps than my Daily Driver.

It could possibly be location based apps, acting up, or as a result of recent international trip - Zone & Region changes etc.

I'll be watching for it on my next trip in a few months. - non rotating screen will be the giveaway.

But as I say, never had a problem previously.
[Galaxy S II Android Development] gm0:
[MENTION=6724217]Boolian[/MENTION] really can't say. I don't think it's traveling since I travel a lot without issues and also the sensors shouldn't care less really (as to the gps receiver I assume you've looked at different basebands - personally I'm just using the most recent one which should be XXMS4) .

Anyway, a quick google back to the old discussion if you want to read up on it although I don't remember any conclusion being reached: https://xdaforums.com/galaxy-s2/general/rom-t3555834/page82
[Galaxy S II Android Development] Boolian:
Thanks for the link.

Tried a few basebands, actually rebooted with a different one before re-install. my go-to are MS4/LS8/BVLP7

Glad I can rule out travel then!

I was thinking more that an app was confused as to where it was and hammering sensors, but I don't think so really.

Something (unrelated) about the proximity sensor in the link rings a bell though, I'm going to trawl through some of my own old posts, memory is terrible!
[Galaxy S II Android Development] gm0:
The lockscreen prox sensor issue is happening to everybody I believe. I have an open bugreport for that on jira at least. But yeah, that's unrelated.

PS: And yes, that's what I thought with respect to apps. Who knows.
[Galaxy S II Android Development] Boolian:
I remembered now, also something about Doze and the accelerometer (possibly other sensors) not coming out of sleep. I think this goes back to CM13, but I'm sure recently (can't find it) there was a commit or workaround for similar issue on 14.1 (or the Unofficial build)

D'oh, I dunno how I forgot that, I'm definitely getting too old!
[Galaxy S II Android Development] gm0:
[MENTION=6724217]Boolian[/MENTION] the only reason you're not forgetting things when you're young is because you don't know anything. ;) Anyway, after what you said I'm wondering if you (and the others with the issue) are using Greenify or other apps with forced/aggressive doze features. Personally I stopped using them with Android 6 so if the issue is doze wake related that might be why I've sailed clear of it.
[Galaxy S II Android Development] Boolian:
Haha thanks for the encouragement, I hit my half century and you're right - so much rubbish in there -Like knowledge of OS/2 & Token Ring networks !

I ditched Greenify after CM13 to see how the "Vanilla" LOS14 handled things, haven't installed it since.

I turned off Battery Auto Powersaver because I couldn"t get lower frequency to stick (still an issue I think despite recent commits) Battery Auto Optimization is on though.

That's really all the tweaks I run.

Though I used to strip out the Google services : "alldynamite" and "droidguard" (ads & safetynet) which I haven't done for LOS...

I think I'll do a clean build next nightly and see how things go.

My GPS is ok at the moment, though a bit sluggish on 'device only' I've still to tweak the gps.conf properly.

Cheers. :good:
[Galaxy S II Android Development] gm0:
Hah, I'm in the process of catching up on that half century, but I sure share that knowledge, in fact I've still had my hands on CP/M if that tells you something.

Reminds me I always wanted to check the sources for that because in my testing the power save mode wouldn't lower frequencies at all, it would use the normal balanced governor without a frequency cap, which surprised me.

I'm only on the nano package with a few apks stripped out of that even if it matters (plus about half the services disabled). At face value none of it should affect sensors though.
[Galaxy S II Android Development] Boolian:
Ahh, those were the days (pulls on slippers, lights pipe) Amstrad PCW wrestling with Locoscript & BBC Micro learning machine code. ARM was designed on them y'know... zzzzzzzzz

:D :good:
[Galaxy S II Android Development] the.gangster:
:)

Just to get you guys back carefully from the glory past to the present day:

Jenkins is currently cooking our next build. So get ready to check out the first 7.1.2 build.

(But be aware that even if it might not be directly related: the first nightlies of the AICP tree that took this step already some days ago obviously boot looped. So better have a recent backup)

Edit: Jenkins finished:

lineage-14.1-20170419-nightly-i9100-signed.zip
[Galaxy S II Android Development] gm0:
I think they fixed that issue yesterday, but I fully support the notion to have a recent backup (update: the build flashed fine for me, no issues).

Besides 7.1.2 this build will also finally bring us to April's security patch level.

Now get off my lawn. :D

PS: Forgot to mention since you already had the link: build is up (it's always around 9 am UTC unless something goes wrong or the build order gets rebalanced again)
[Galaxy S II Android Development] rINanDO:
I'm currently implementing and testing 100Mhz steps from Dorimanx kernel and fully implement PegasusQ governor with modified PowerHAL like the i9300 has. I post my test builds on the unofficial form to keep this one on topic. The power save mode in current official builds uses the conservative governor which doesn't has a freq limit. Its behavior is expected. The new PowerHAL will limit the freq when screen is on, and limit the use to 1 core when display is off to be more powersaving effective.
[Galaxy S II Android Development] gm0:
[MENTION=2222292]rINanDO[/MENTION] thanks for the info and the work. I was not following your unofficial thread but had seen your pegasus implementation was merged into the official.
[Galaxy S II Android Development] rINanDO:
No problem. Some preparations are merged, but it isn't active in the official build yet, nor the new frequencies. I'm still testing these builds and hope for some feedback of users who are also testing this. If everything works fine and there is improvement, I will merge them to official.
[Galaxy S II Android Development] gm0:
No that's fine, I understood that since I had looked at the commit. What I meant was that I'm only following the changelog for the official builds but saw there that you were working on the implementation. Unfortunately I don't have time to test out your unofficial builds, that i9100 is still my daily driver and thus usually in use.
[Galaxy S II Android Development] flamadiddle:
Hey guys, I just clean flashed the 20170412 build on my d710 (U.S. Sprint variant), and incredibly, it boots. Everything seems to function normally, except:

* No Wifi

* Home button doesn't work

* Menu button doesn't work

I suspect these are due to kernel incompatibilities. Can anyone point me toward a kernel or appropriate forum to find one for my d710? I checked the Epic 4G Touch forum already, but there's no activity there since CM12.
[Galaxy S II Android Development] nospamboz:
20170419 is the one!

A big "thank you" to the whole i9100 LineageOS team. If there are any more CM13 (or earlier) holdouts out there, the 20170419 build is the one you've been waiting for. The latest Android 7.1.2, the latest security patches, and all the major quirks ironed out.

(That is to say, it's no more quirky than any other CM build. ;^)

So find that 20170226 "expermental" transition build, get this build, GApps, and the su activator, and start flashing.

Goodbye, CyanogenMod, it was great while it lasted. Hello, LineageOS, the beginning of a beautiful relationship. :)
[Galaxy S II Android Development] gm0:
There's probably more that won't work correctly. The devices, despite being very similar, do not have identical hardware. Generally you are more likely to soft brick your phone by flashing a ROM for another device than to just have a few issues like that.

You already know the appropriate forum to turn to since you say you've been there. This here is not the place, you should not have posted here.

You can look at the old d710 sources from CM12 days and use those to try to build your own unofficial version of LOS. To get you started, if you copy these files here onto your device in the respective folder you'll probably fix your keys: https://github.com/LineageOS/android_device_samsung_d710/tree/cm-12.0/usr/keylayout ;)
[Galaxy S II Android Development] flamadiddle:
Thanks for the response. I know this isn't the right ROM for my device (hence my surprise that it booted), but Lanchon specifically made the TWRP crossflash patcher so we d710 (and other network-specific-variant) owners could try the international ROMs.

Thanks for the link to the d710 repo! Would have taken me forever to find that.
[Galaxy S II Android Development] gm0:
Well in that case I'd probably better link you to this, too: https://github.com/LineageOS/androi...4.1/arch/arm/configs/lineageos_d710_defconfig

Also https://web-beta.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro might help.

Good luck. :D
[Galaxy S II Android Development] Bruno25:
GPS fix vs. SIM card

I managed to circle a little bit more the problem... I thought the issue was related to lineageOS because I tested the GPS with CM11 and it worked. But there was an other difference between both configurations: the SIM card!

Summarizing:

- with SIM card inserted, with both CM11 and LOS14.1 ==> no GPS fix (even disabling data)

- without SIM card inserted, with both CM11 and LOS14.1 ==> very fast GPS fix

:confused:

Sub_Zero2 suggested in this post to change my baseband.

jt12345 indicated how to back up the current modem:

dd if=/dev/block/mmcblk0p8 bs=12583168 count=1 of=./myModem.bin

I did that.

I downloaded my stock ROM from sammobile. I extracted modem.bin from it. I rebooted my phone in download mode and I flashed the modem (I am on Linux)

sudo heimdall flash --MODEM ./modem.bin

My baseband was I9100UHLPH and is now I9100UHMS1. But still no GPS fix when the SIM card is inserted. I also tried with XXMS2, without more success.

Any other idea? Should I test other modems since my issue seems to SIM chip related?

Any start of beginning of any idea is very welcome!
[Galaxy S II Android Development] Nobby1960:
An issue from the GApps, you must take the latest build and the AICP ROM starts up :)
[Galaxy S II Android Development] gm0:
My March 09 opengapps work just fine.

---------- Post added at 17:58 ---------- Previous post was at 17:54 ----------

Try with SIM card inserted, put the phone into airplane mode, reboot, then try the GPS. If that still doesn't work then all I can think of is the SIM card being too thick and somehow pressing down onto the electronics below and causing that GPS issue, but that's rather unlikely.
[Galaxy S II Android Development] toy_story:
Updated through OTA, everything works fine.

From 04/12 to 04/19 LOS.
[Galaxy S II Android Development] suhestvitelnoe:
Install TWRP

Hello, please tell me how via LOS recovery to install TWRP? Install zip in recovery LOS horrible and zip with TWRP also not installed.

P.S. Sorry for my English.
[Galaxy S II Android Development] MigoMujahid:
use Flashify app to install TWRP image file on the recovery partition, it's the first solution that came to my mind, but there should be other.
[Galaxy S II Android Development] the.gangster:
[MENTION=2222292]rINanDO[/MENTION]

What an ancient version in the thread title...

We are already on 7.1.2 for such a looooooong time now.

:) just kidding, take your time.
[Galaxy S II Android Development] suhestvitelnoe:
I need TWRP to install the zip with root and recovery LOS it does not install. And the app Flashify requires root.
[Galaxy S II Android Development] MigoMujahid:
flash that in LAOS recovery and reboot, this will give you root access, if you get some error message in recovery after flashing the file, ignore it, and just reboot.
[Galaxy S II Android Development] todonormal:
I found what now it's possible start up my phone during charge (previously uncharged, in off). It's great.
[Galaxy S II Android Development] Sub_Zero2:
Look at gm0's post..

If that doesn't work, then i would recommend trying other basebands/modems

Edit: i don't have any gps lock myself, but then i rarely need gps.

What modem/baseband that is required, depends on your area and/or your carrier.
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]: Is it possible to enable the Auto Brightness checkbox?
[Galaxy S II Android Development] the negrox:
I´m going to pay special attention to the solution of this issue, because I have the same problem with my i9100 and also a gt-i9295, neither of them fix a stable gps connection with the same SIM card, but when I insert another SIM from a different company, both devices work flawlessly!!! So, as you mentioned, it shouldn't be a software regarding issue, but a SIM issue.... Greetings.
[Galaxy S II Android Development] fubo73:
Hi all,

Coming from MM, I installed latest build together with gapps and did full wipe (not internal SD). Phone booted and started guided procedure, but it is not able to find my wifi network (any other rom before was able to) and cannot access to wifi settings to check why.

Besides, I tried to install supersu addon, but it failed with error:

I am using TWRP 3.1.0-0 isorec with isorec kernel.

Any hint?
[Galaxy S II Android Development] Sub_Zero2:
That's what i meant by carrier (the cell network operator).

It could be that a totally different modem firmware than from your own country might work well for you...

Here is a bunh of them in flashable zip's:

http://veyka.co.uk/sgs2/radios/

Don't forget, some of these radio firmwares are very old (2012).

I'm located in norway, and i use the xxms3 baseband. But this was shipped with Oem Telenor phones. Now i am using Netcom/Telia... Cannot get a lock at gps at all...

But i rarely use gps so i don't care atm. Will try other basebands later on.
[Galaxy S II Android Development] gm0:
The addon-su error is known and can be ignored, it'll work regardless.

As to the wifi thing, are you using the latest gapps? There was apparently an issue with the setup wizard of older versions and the new Android 7.1.2 builds. Not sure if that affected WiFi. If that's not it then simply re-flashing the phone and wiping the caches again could be enough to fix it. Also make sure your download isn't corrupt (md5 hash is on the download page).

Shouldn't make a difference. The basebands can differ in the cellular networks (frequencies) they support but as to GPS that's the same technology worldwide and always has been, there's no regional component there. Make sure your location service is set to "device only" to disable the network aspect of it, that's what may be producing time-outs and thus delays.
[Galaxy S II Android Development] fubo73:
Hi, thanks for answer, I will retry the procedure. I checked zip files before installing.

---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------

Again, no success. I installed everything from scratch, I went through recover of previous backup from google, but then again no request for wifi. Then I selected to configure for a new phone, and wifi configuration appeared! I configured my network, then went back to recover procedure, and it worked...

I can also confirm that I can configure root from developer settings.
[Galaxy S II Android Development] Bruno25:
GPS vs. SIM card => solved (at least with CM11)

I am still testing under CM11. I tried one more modem (NELS1), as suggested by GNUDroid in this post. I also applied the AGPS patch made by Crypted (that's the TWRP version, but it can also be used with CWM) and cleared the "Google Service Framework" data (Settings / Apps / All / Google Service Framework / Clear data). That last one seems like voodoo to me ;).

Result: very fast fix

By the way, you can note the the compass arrow is a bit way off the north (about 20 degrees towards the west)... Does anybody know why?

I was so happy with my new working GPS that I didn't want to change anything (e.g. CM11 => LOS 7.1.2), fearing to lose it again (the voodoo may not work anymore).

Now I think I am psychologically ready to dare to try with LOS :D. More news in the coming hours.
[Galaxy S II Android Development] gm0:
Discrepancy between magnetic north as returned by the phone's magnetometer and the calculated north based on the GPS data. Might also be the reason the fixing is problematic for you, with the device searching for the satellites in the wrong spot.

Reason could be magnetic interference at your location - it should not persist if you try again while out in the open (without headphones near the phone, etc.). Bad accelerometer and gyroscope data can also throw it off since that's used to adjust the raw magnetometer output - that app you are using has a compass calibration option that tries to reset the latter.

PS: As to google data reset helping you out: make sure you have the location service set to "device only" so it does not even try to use google's location service.
[Galaxy S II Android Development] HutchGuy:
Does anyone have any issues with signal drop? It keeps dropping randomly (mostly when I have my data on), like I'm middle on an online game and the signal drops for like 10 seconds and it backs to normal in 5 seconds. It's really annoying, i'm just 1 step away from breaking my stupid phone...

Could it be sim-card's fault? or Hardware? Rom? How can I see what causes the problem... Also as I said it happens randomly, in 10 minutes, it dropped 3 times but last night it was all fine

_____

I can answer my own question tho, like change the simcard to see if it drops again or change the rom and kernel.. but the main question is anyone have the same problem?
[Galaxy S II Android Development] Bruno25:
[SOLVED] GPS vs. SIM card, LOS 14.1 (7.1.2, 20170419-nightly)

I just installed:

LOS 14.1 (nightly 20170419)

today's pico open gapps

TWRP-3.1.0-0 (since I updated from CM11)

addonsu

AGPS patch by Crypted

GPS Status & Toolbox

Just for the records, I previously installed NELS1 modem.

sudo heimdall flash --MODEM ./modem.bin

As suggested by gm0, I set the location to device only, started GPS Status, reset AGPS, downloaded AGPS data, set the telephone to airplane mode.

I also cleared the "Google Service Framework" data (Settings / Apps / All / Google Service Framework / Clear data). I then rebooted the phone and restarted GPS Status.

In less than 10 s I get a GPS fix.

Then, I switched off the airplane mode and tested again ==> very fast GPS fix.

Then, I changed back the location to high precision and tested again ==> very fast GPS fix.

Then, I switched off wifi (to reproduce driving condition) ==> very fast fix.

I have rebooted the phone between almost each change. I noted huge battery drops at each reboot (not related to the GPS issues, I already noted it before... Time to change my battery?)

Now I will test in real driving conditions :D.
[Galaxy S II Android Development] monrus:
Hi all,

First of all i wish to thank the community for all the huge effort made to keep "old" devices up-to-date!

Well i'm a newbie to the "android world", and i experience some troubles to well understand all the required points to install LOS to my newly acquired S2 device (this one sounds funny). I've installed Replicant 4.0 on it and it work well, except for the .. coughcough .. wifi and bluetooth), and that's why i'm trying to have the last version of LOS on it [/mylife off].

I've read that the emulated storage could lead to complications with the device, and i couldn't find a full complete "how to install last LOS" (witch required at least a 1GB partition) on my S2.

Any help would be greatly appreciated

Thanks in advance

monrus
[Galaxy S II Android Development] NkLAnT:
Hello guys, I installed Lineage OS on my S2 with Gapps Nano. My problem is that this package does not include the Google Assistant module. Is there any way I can enable it or add only the G Assistant module to the Nano package or do I have to reinstall Gapps all together? Can I flash the Gapps Micro over the Nano package or will there be any conflicts? Thanks!
[Galaxy S II Android Development] jojobg:
Try Fuel Gauge procedure from the forum before you go for new battery.

Should work ok.
[Galaxy S II Android Development] the.gangster:
Modifying GApps installations

Yes there is a way to tell the (really powerful) GApps installer what to do. Well, it should be obvious that you can't extend a nano package to install more than it has inside, but you can restrict any package to install less. And no, there will be no conflicts, unless you totally mess up things.

I linked to this description already in post #7. It also contains a sample config that can be taken as a base and another link for further indepth-explainations.
[Galaxy S II Android Development] hedgehog99de:
I did it as you described (but without changing the modem). Only two results: Incredible battery drain and FCs of Google Services. But no better GPS.

[MENTION=5992250]Bruno25[/MENTION]: I think you don't have to change your battery. It's a result of the AGPS patch. Before installing the patch I had normally 20 hours battery time, now I have only 3!

Some tries and reboots later: The battery consumption is so high that the battery looses energy despite connecting the charger. Now I go back to the former configuration...

Heiko
[Galaxy S II Android Development] NkLAnT:
Thanks for the reply guys, I ended up in reinstalling the OS along with the Gapps (I installed the Micro this time) because I had a bootloop because of my stupidity.

Anyways, the phone is fresh now, I entered all of my information but still no Google Assistant. I checked in Settings ->> Apps and the "Assist" option has the Google app as my default app. Everything is up to date etc, but no luck. Have any of you successfully managed to run the Google Assistant? Thank you!

P.S.

Also my language is set to English US, if that's relevant.