yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Boolian:
Very odd, not least the ability to force 2G

However, GPS positioning is, at it's basic, just a triangulation problem.

Your Sim card is not required for GPS positioning, if you have the correct local time & timezone to speed things up it helps, but the satellites will, eventually, provide all this information.

Assisted GPS is speeding things up by providing info like "What time is it? Where am I? Where are the satellites?"

So it's possible and IIRC this did happen with an Australian cell provider recently that your provider is passing out erroneous info. Whether that is related to your SIM card or local cell tower broadcast or dodgy modem is only 1 question.

*edit - found link to that Here which is similar to your 2G/3G symptoms

The main question is "can I get GPS position standalone?"

If you can't get GPS position standalone, without any Sim etc then it's a problem. Which is best solved testing with a second reference device and different OS.
[Galaxy S II Android Development] Bruno25:
GPS vs. 2G & 3G

Same issue with two I9100 => not a hardware problem, or I am very unlucky

Same issue with both CM11 (Android 4.4.4) and LOS 14.1 (Android 7.1.2) => not OS related, or both OS have the same issue

SIM card and carrier are the only remaining potential sources of my headaches.

For a while, I will stick to 2G.
[Galaxy S II Android Development] jojobg:
Why don't you test with another sim of another carrier in your region?
[Galaxy S II Android Development] gm0:
Interesting. If it's the network then checking the radio log might provide the explanation as to what's wrong, and possibly tweaking gps.conf/sirfgps.conf accordingly might work around it (in particular the latter has a bunch of network specific options).
[Galaxy S II Android Development] ale5000:
LOS is almost the same of CM.

A better test would be a stock ROM.
[Galaxy S II Android Development] Yurienu:
I see no link with I was talking.

This is not linked to RIL, it's linked to a wakelock with flashlight, regular calls work fine.
[Galaxy S II Android Development] gm0:
yes, and besides being entirely irrelevant to the question that was asked (the question is about messenger apps crashing due to wakelock issues), it's also an outdated fix that he took from the unofficial build and which shortly after was released as part of the official nightlies, as [MENTION=6560258]the.gangster[/MENTION] helpfully reminded us just a few pages back and that thus has no reason to be linked anywhere.
[Galaxy S II Android Development] MigoMujahid:
Oops, sorry i got the words completely wrong, i thought the problem is in Ril, but it turned out that the problem is about wake lock issue.

Sorry.
[Galaxy S II Android Development] todonormal:
Actually working?
[Galaxy S II Android Development] gm0:
All good. I saw there's an open issue for this on jira so it'll eventually get fixed. Looking at the crash log it appears the issue isn't actually with the wakelock directly but with [MENTION=2222292]rINanDO[/MENTION]'s implementation registering a callback in the constructor even when the calling thread has no looper, so an exception gets thrown.

Yes.
[Galaxy S II Android Development] NikosTweak:
It still does not work with the latest version
[Galaxy S II Android Development] gm0:
Must be something specific then. I am connected to a 5 GHz wi-fi as I write this.
[Galaxy S II Android Development] NikosTweak:
I will try again on different 5Ghz networks.
[Galaxy S II Android Development] gm0:
In other news, today's weekly for our device failed to build so we likely get to wait 'til next week for an update.
[Galaxy S II Android Development] todonormal:
What band work for you?

You testing bands different... In Xperia L and SP, low bands works without problems, but high not.
[Galaxy S II Android Development] NikosTweak:
Band 36
[Galaxy S II Android Development] ale5000:
Why the build failed?
[Galaxy S II Android Development] rINanDO:
Seems the buildserver android-kallikrates was suddenly broken during our build.

Edit: however, maybe I overlooked.... I see a lot of errors about this server, but it fails during our recovery image build (lzop). Probably already fixed in this patch https://review.lineageos.org/#/c/170013
[Galaxy S II Android Development] ale5000:
Isn't possible to trigger a new build without wait another week?
[Galaxy S II Android Development] gm0:
Possible yes, likely no. Available server capacity is limited. Missing a weekly build isn't a big deal.

---------- Post added at 02:08 ---------- Previous post was at 02:06 ----------

I don't know actually, that one wasn't my network. I'll try to remember to check next time I'm there.
[Galaxy S II Android Development] dpcdpc11:
Hey guys.. short question... I have an old S2 i9100 running a Kitkat Omnirom and it just works like crap... restarts quite often and gets really hot.

Should I update to an older CM 13 which I found on a some blog post or to the latest LineageOS 14.1? Which one runs better?

I just want a basic stable daily driver with no fancy features... just so I would be able to surf the web and use facebook and similar apps. No gaming, no special apps... just the basics.

Thanks in advance!
[Galaxy S II Android Development] Bruno25:
Downgrade from LOS14.1 to stock kernel for test

In order to troubleshoot my GPS vs. 3G issue furthermore, I want to downgrade to the stock kernel (samsung, 4.1.2), as suggested by ale5000.

Can I just flash this ROM with the install option from TWRP ? Or do I need first to revert to the original partition sizes using Lanchon repit (i.e. lanchon-repit-20160415-system=0.5G-data=2G-sdcard=max-preload=0.5G+wipe-i9100.zip)?
[Galaxy S II Android Development] Boolian:
Yes actually just looking at that just now.

It's a bit bizarre and intermittent.

I did notice initially today "DoNotDisturb" was triggered during a call.

New calls had also oddly been muted (vibrate only)

"Notify of incoming call" (while on a call) was also silent, though there was a visual.

I adjusted various settings and now experience the signal dropout, but no longer have "DND" active.

But have just noticed the Ring Volume has muted again.

So testing... It's the most I've spoken to my mother this year

:D

*Edit Now rings again ok, "DND" active Alarms only' during call but still temporary Mobile Signal dropout and toast error message after call ended (though only for short 5-10s period)
[Galaxy S II Android Development] shkedov:
I'm confirming that DND issue too.

And you killed me (of laughter) with your mother XD
[Galaxy S II Android Development] ko2005pu:
well..i am getting status 7 flash zip error, when i tried to flash 20170213 nightly.....i am lost
[Galaxy S II Android Development] shkedov:
More details man!!! Are you coming from cm13? Clean wipe? LOS14.1 and just updating your nightlies? Any information that might help us understand.

We aren't able to help you like this...
[Galaxy S II Android Development] Pier_89:
Why am I getting 8,77 GB system space full after booting with 20170213 nightly?

Is it all right?
[Galaxy S II Android Development] ko2005pu:
i am sorry. I am coming from Cm13, follwing install guide: exp+twrp+recovery+nightly, then error

:eek:

May i remove assert sentence?
[Galaxy S II Android Development] shkedov:
Buy saying install guide you mean this?

If you have exactly the i9100 (international) and not any other type (such as i9100g or so) i wouldn't rush into removing the assert since there's no reason for that clash to happen and maybe you are forcing a wrong or corrupted file.

Just in case make sure you have a compatible and updated twrp recovery for Nougat.

The order there (that post) is not "exp+twrp+recovery+nightly". It's experimental->reboot->nightly.

Maybe you installed the experimental with the old twrp (for cm13) and scripts didn't match.

Did you check checksum? Maybe zip file is corrupted?

Did you make the coffee?
[Galaxy S II Android Development] ko2005pu:
i am sorry:

yes, this guide.

i9100 international.

i ll try correct order: It's experimental->reboot->nightly.

TWRP version is 3.0.2.0

i do not make checksum

i forget to drink a coffee,

many thanks.:good:
[Galaxy S II Android Development] shkedov:
Checksum is important, it makes sure that you have downloaded the right file without any fragments or bytes missing or going wrong.

Make sure you have at least 1GB /system partition.

And you don't need to apologize all the time, you're cool dude! I'm a total noob, I'm just trying to spare what I know as much as I can.

Everything so far seems fine, maybe it is the coffee...
[Galaxy S II Android Development] Teekanne3000:
:confused:
[Galaxy S II Android Development] shkedov:
3.0.2 and up.

Those below might not support.

Especially on emulated (see OP), you need the special recovery for that.
[Galaxy S II Android Development] Nobby1960:
So much, are you sure? System space is round about 650 MB :eek:
[Galaxy S II Android Development] shkedov:
Yeah, like how can that be, do you have some 9GB /system partition or what? :p

Are you sure you're not confusing with the /data partition?
[Galaxy S II Android Development] Pier_89:
I can see it switching to Setting> Storage. I'm not using any app.

Is it ok or not?

Regards :)

---------- Post added at 01:39 AM ---------- Previous post was at 01:38 AM ----------

How can you see this? I switch to Settings > Storage to see 8,77 GB system space full
[Galaxy S II Android Development] Nobby1960:
Install DiskInfo from Play Store and you are happy. That shows you exact values.
[Galaxy S II Android Development] Teekanne3000:
I have install exp, force reboot, install nightly, gapps and wipe cache, dalvik cache, reboot.

Can't start some apps like k 9, chrome, google maps, whatsapp, f-droid, firefox. Have give permissions to this apps.

Play Store has no connection to google. Failure RH-01
[Galaxy S II Android Development] Jamie_oppo:
Its not on lineage os website anymore did they take it down?
[Galaxy S II Android Development] shkedov:
He is right, diskinfo will show you all partitions. Settings>storage only shows you your personal files partition - /sdcard0 (or the emulated if you in to it), it doesn't show /data nor /system and other "system-hidden" partitions.

---------- Post added at 08:05 AM ---------- Previous post was at 07:54 AM ----------

Dude, read at least two pages before asking, please. You're like the 7th asking the same question, and it is THE topic for 5 pages so far. Thank you friend. :good:

As for myself, I'm ignoring this kind of question from now and on. :cyclops:

Of someone else wants to take the job for answering this question I don't care, have fun everyone!
[Galaxy S II Android Development] gm0:
The problem is more that Settings->Storage simply shows bogus numbers due to incorrectly calculating "System" storage space usage:

That's from a device with a 1 GB system partition, 696 MB of which is in use. The numbers on the second screen do not even add up correctly, there's clearly something wrong.

PS: Funny forums, you cannot post external links with a low post count but you can edit them in.
[Galaxy S II Android Development] MigoMujahid:
Are we damned or what??!

Everytime we go official, things go wrong :eek: :laugh:
[Galaxy S II Android Development] Yurienu:
CM 13 never had a stable version to my knowkedge.

You should not use an old ROM that does not have latest security patches as a daily driver.

LineageOS 14.1 works fine for what you plan to do, you just won't be able to make secure calls with Signal app if you use it.
[Galaxy S II Android Development] ale5000:
I'm still hoping,

there are a lot of interesting changes this week:

- Auto Brightness checkbox

- Fix for Wifi Saturation

- Fix wrong algorithm in WifiPowerPerPacket()

- AC3 audio support

- Don't force enable the prox sensor for incoming calls

- Add 100Mhz cpu step support for 1200Mhz

- Fix internal storage summary for non-emulated storage
[Galaxy S II Android Development] BenjyTec:
I personally prefer downgrading to stock via Odin. In my old Odin version, I just put StockRom.zip into AP, a pit file with stock partitions into PIT after checking the 'repartition' box. Takes only for about five minutes. Then boot Into recovery and format everything. Wipe sdcard0 via Windows format function. The newest Odin it is somehow different​.

Btw I'm not sure if it is necessary to flash isorec disabler zip.
[Galaxy S II Android Development] Nobby1960:
The easiest way: Take my attached Odin version and unzip it plus the pit file. Copy Odin on PC and start it, load your stock ROM in PDA and the pit file in PIT, hit the start button and drink a cup of coffee ;) After a few minutes your S2 welcomes you with the Samsung startup sound.
[Galaxy S II Android Development] Bruno25:
GPS vs. 3G, LOS 14.1, CM11, Stock ROM

I downgraded to the stock ROM using your stock PIT file and Heimdall (I don't have any Windows computer nearby).

I did not remember that there were so many bloatware in the stock ROM :eek:.

Just after the first boot, I downloaded GPS status and get a very fast GPS fix.

But I checked that mobile data was set, by default, to 2G only. Is that a specificity of the stock ROM I used (unbranded, 4.1.2, Brazil)?

Setting it to 3G, no more GPS fix.

Conclusion: GPS vs. 3G issue is definitively not an OS related issue.
[Galaxy S II Android Development] Boolian:
If you still have Stock Rom on, you could try the original modems for your region which were UH prefix for Latin America generally and/or

LP3/LP7/LPF (among others) specific to Brazil.

See This Link for details.

You may have to Google to find the old modems or try Here

I doubt it will fix your issue, but you never know !

I think your symptons are pointing to a problem with your Carrier/Provider

But if other users you know on the same network are not having issues, you're back to square-one.
[Galaxy S II Android Development] jazzl:
Dear All,

My Galaxy was never rooted before, and therefore it´s still a Jellybean ROM running on it, but I decided that now is the time to have some fun and install the 14.1 ROM on topic here.

So I installed CWM 6.0.4.5, SuperSU´d it, backed up everything in recovery mode, wiped system, cache and dalvik cache and everything else that could be wiped, and tried various things. At one point I was told that my device was "." instead of I9100, and another time I was just informed that the installation was aborted. Luckily I had no problem going back and restore my backup.

I´ve found many guides to how the ROM can be upgraded to a newer one, but none explaining exactly what I need to do if going from 4.1.2 to 7.1.2 - I´m thinking that´s where my problem is. Can this be done, or do I need to first install for instance Kitkat or Marshmallow? Is my CWM version number high enough?

Would someone be so kind to give me a bit of guidance here?

I´m not all new to these kind of things.. On my LG G3, I´ve tweaked my own CM12 with custom .ko files in Linux and succesfully installed it on the phone - just so you´re aware that I´m not a 100 % novice :)
[Galaxy S II Android Development] ale5000:
You need to increase the /system partition, the standard size is not enough.

I'm not sure if there is any CWM that work with this ROM, probably no.

TWRP will certainly work.
[Galaxy S II Android Development] MigoMujahid:
You're missing the point, i can see you haven't read the OP, otherwise you would have known that you need to increase system partition size to be able to get the ROM flash, you can follow one of the guides available like this one.

Edit: Seems like you have been answered already, [MENTION=5627087]ale5000[/MENTION] i need to be quicker next time....:silly:
[Galaxy S II Android Development] jazzl:
Ok, admitted - I didn´t increase the system partition yet but will certainly do so.

In the meantime, using Odin 1.85 with CWM worked fine for me, but if I use it with TWRP from the link you sent me, I get "Complete (Write) operation failed". Is there any other way to flash TWRP?
[Galaxy S II Android Development] jt12345:
Hi all.

I've tried clean-installs of both lineage-14.1-20170419-nightly-i9100-signed.zip and lineage-14.1-20170412-nightly-i9100-signed.zip, but while everything *seems* to be perfect for the first hour, within one day I am unable to boot (I get a boot loop where the only thing on the screen for at least 20 minutes is the lineage boot animation).

Is anyone else getting similar bootloop problems, or have you all been using one of the latest nightlies without problems for a few days? If your phone is working well, exactly *which* nightly are you running?

Thanks, J
[Galaxy S II Android Development] gm0:
What are you doing that makes you reboot? For example, a slow boot is normal after a dalvik/art cache wipe because it will be recreated on the next boot then. Or if the phone reboots on its own then the question is what were you doing before it did that, what did you install, etc. If you can still boot into recovery you can grab a logcat to see what happened.

In case of doubt just wipe everything clean again (incl. /data) and start over.

PS: Goes without saying that it's working fine for all of us or we wouldn't be using it.
[Galaxy S II Android Development] rogers11:
I'm running the latest Nightly for over 200 hours now without reboot. Just the Nightly with Nano-GApps, inbuilt root and without idiotic "fixes".
[Galaxy S II Android Development] jt12345:
I'm doing development on the gps susbsystem. Some of the config files are only read at boot-up, so I have rebooted about 40 times per day for each of the last 3 days (that's an approximate figure).

I understand and I agree.

No, the phone is not rebooting on its own - I am rebooting intentionally (see above).

I've got a 10MB logcat dump of the 20-minute boot-up (before I gave up waiting and pulled the battery!), but I can't see what's going wrong i.e. I can't see what exactly is causing the bootloop.

Interestingly, I've tried that. After one of the bootloops, I rebooted into recovery, did a "factory reset" wipe and rebooted. It did *not* (surprisingly) cure the boot loop!

Ooh! I disagree with that on several levels. But rather than putting my "therapist-hat" on, I'll try to stay "on topic"...

Ok, well I only get the boot-loops when I reboot, so that fact that you are *not* rebooting tells me that I don't know whether your boot procedure works or not. It is, however, good to hear that the latest nightly is running stable for you...
[Galaxy S II Android Development] gm0:
It's not a bootloop if you are causing it to reboot. Anyway, see whatever happens last in the log and you'll know what your system was doing at the time you decided to reboot it.

However, since you said you're actually modifying the system and you're the only one with the issue, the face value assumption would be that your own modifications are the cause of the issue. Even default LineageOS can be boot looped just by setting certain parameters to the gps configuration, and if I understood you correctly you're even changing the code so...

I'm fairly certain my childhood has nothing to do with my smartphone not boot looping but yep, let's stay on topic. ;)
[Galaxy S II Android Development] jt12345:
Oh. My mistake. I thought that if I initiated a reboot (into the normal "system" boot-path) but that if, instead of eventually seeing my homescreen, I just saw the lineage boot animation for 20 minutes, then that was called a "boot-loop".

If it's not called a boot-loop, is there a term for what I'm experiencing?

I agree. But I'm not sure that "knowing what my system was doing at the time I decided to reboot it" would help me. I don't want to know what my system was doing at the time I decided to reboot it - I would like to know what's causing my boot procedure to not complete successfully.

I agree entirely. Another few hours of debugging, and hopefully I will have an answer...

This had me laughing out loud. Thank you - I do appreciate good humour!

:)
[Galaxy S II Android Development] gm0:
It's not looping, so no. And since the log kept filling up apparently it didn't crash, either. So from what you told so far it's just a slow boot. :)

Simple answer: the immediate reason it did not complete was you pulling the battery because you did not want to wait anymore. ;)

More helpful answer is in the log.

Good luck. :)
[Galaxy S II Android Development] jazzl:
Ok, I followed the link and went through all steps - very well explained and I got a working nougat - very slow however, but working. Now at the point of waiting for the phone to be 100% charged so I can do the app battery calibration.

In the meantime, I´ve lost all contacts, sms messages and notes taken with the phone. Are these in the backup I mentioned previously made with CWM and can they be extracted from there, or are they gone forever?
[Galaxy S II Android Development] gm0:
[MENTION=4159955]jazzl[/MENTION] unless you transferred that backup to your PC you would have wiped it along with everything else., so if you did not make a backup in some other way (Google sync, Samsung Kies, etc.) that data is gone. If you do still have that CWM backup somewhere then you'll have to go back to your stock ROM when restoring it, although you may have to flash CWM first, not sure if TWRP would handle it.

Also be careful with blindly rooting your phone and installing apps that ask for root access. It means you give them full control over your phone and data.
[Galaxy S II Android Development] jazzl:
Allright, thanks. So, the data are still in the CWM backup? I do have it indeed, and just transfered a 2.4 gb zip containing it over to my desktop.
[Galaxy S II Android Development] Sub_Zero2:
The nougat Lineageos 14.1 is not running slow here... It's actually quicker than 6.0.1 cm13.1
[Galaxy S II Android Development] gm0:
Yes, that backup is basically a full snapshot of your old system. You can mount those backed up partitions directly to access the files within.

I do however have doubts that simply dropping those files into LineageOS would work, I would assume that the database formats have changed in one way or another since Android 4, but I do not actually positively know that it would be incompatible.

Still, restoring the entire backup via CWM and thus going back to your old stock ROM is probably easier than starting to mess around with individual databases. Then on the stock ROM use some other backup solution to first get the contacts and messages and whatever else you need off the phone and then back into LineageOS. If you do not have a lot of them then even storing them on the SIM card may be enough.

---------- Post added at 19:33 ---------- Previous post was at 19:26 ----------

Yep, same for me. Thought he might have been referring to the ART cache generation upon first boot maybe, not sure.
[Galaxy S II Android Development] BenjyTec:
I think the premium version of Titanium backup supports extracting app data out of a nandroid backup. See the picture at this link:

http://www.guidingtech.com/13501/restore-apps-nandroid-titanium-backup/
[Galaxy S II Android Development] jazzl:
Ok, so I got things up and running, slower than before, but running. Bigger problem is that all my audio recordings, SMS´s, contacts and notes are gone. I do have a CWM backup though that´s 2.4 GB big. Will this contain the data I´ve mentioned?

To find out, I backed up the new system, reinstalled CWM and then restored from the backup, but got a bootloop. Then reinstalled TWRP and now trying to restore the backed up nougat - just to get a working phone till I got time to fiddle again with the old backup - but looks like I´m stuck in another bootloop, now with 14.1. Looks like I´ve got to completely reinstall 14.1 over again one more time...
[Galaxy S II Android Development] gm0:
Yes, I answered that above (if those audio recordings were stored to your internal or external storage then they would not be included in backups). As I said, the backed up files are partition images that you can mount directly if you want to (mount command from a terminal window on the phone or via adb shell).

Do your backups include all partitions? If not then you're probably mixing data from different android versions now. Every restore needs to replace /boot, /system and /data, and the caches should be wiped.