yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] treysis:
You didn't understand my problem. The file transfer itself works fine. With a file manager I can open the APK and install it, no problems! Only accessing the file from the notification bar drop down results in an error. And I would be okay if it says "Sorry, due to security reasons you cannot run this file from here", alright. But instead there's a crash. Well, THAT's a security problem. Because crashing means unhandled exception, and that is potentially exploitable by an attacker.

Also, there is a feature to prevent execution: It's under settings, where you can disable the installation of third party apps! I still can't believe you consider a crash as a security feature *sigh* I mean, you're a senior member, you should know better?! (also, I know what I'm doing. I'm running 15+ years without antivirus, and never had any issues).

So, anybody having this eorror on his S2 as well?
[Galaxy S II Android Development] nospamboz:
You should suggest to the powers-that-be that they consider the global G930F, or the Canada-specific variant the G930W8, both of which run LineageOS herolte. I considered the G930W8 myself because it supports T-Mobile AWS 3G (the G930F doesn't), but T-Mobile has been obsoleting that 3G as well, so it's not a real advantage.
[Galaxy S II Android Development] Acid0057:
Good point. I'll see what I can do.
[Galaxy S II Android Development] zSyntex:
Shutting down 3G? Seriously? I'll be going to Galaxy S7 (herolte) ad suggested above.
[Galaxy S II Android Development] Acid0057:
Well in Canada at least, you must be on an LTE compatible device by law at the end of 2019. This is due to our wireless alerts bring delivered over LTE only. Now most people here are already on LTE so the carrier's are shutting down 3g and 2g to force upgrade you. They are offering basic smartphones for no cost upgrades.
[Galaxy S II Android Development] the.gangster:
Cool, does that also apply for travellers to Canada?

[emoji2]

I have that mental picture already:

a new question on the ETA form:

* Do you already own a LTE capable smartphone or would you like one for free

(Answering 'No' will void your request if your planned journey starts or ends after 2020/01/01)
[Galaxy S II Android Development] Acid0057:
Not sure but yes I could see that happening on the ETA form [emoji16]
[Galaxy S II Android Development] Kurt Krummbein:
LOL in hightech-germany we hardly have LTE network spanning all regions. Just in citys, not on the country-side.

Gtz

Kurt
[Galaxy S II Android Development] toshibashi:
I understand German telcos will switch from 3G to 4G asap but will still stick with 2G since a lot of machine-to-machine communications (IOT applications like car tracking, fleet management etc.) depend on it.
[Galaxy S II Android Development] Acid0057:
Wow I think we have 3g (Soon to be retired) and LTE only in Ontario Canada. Most of the province, even in the rural areas have good coverage now.
[Galaxy S II Android Development] davide.slb:
The GPS is hard to find satellite(only 5) and after 10min never fixed at any satellite. Is that working in this rom?

Enviado do meu iPad usando o Tapatalk
[Galaxy S II Android Development] DomeD13:
ROM is extrem laggy and slow.

Came from CM13 which was very fast and smooth.

What can I do...it's so slow, I cant use it as daily driver

Please help
[Galaxy S II Android Development] toy_story:
Look here - https://xdaforums.com/showpost.php?p=74765957&postcount=87
[Galaxy S II Android Development] rsap:
[MENTION=2222292]rINanDO[/MENTION]:

I uploaded a bugfix for the Bluetooth SIM Access Profile, it would be kind if you could merge it.

Will somebody merge my changes to the LineageOS 15 branch or can I do it somehow...?
[Galaxy S II Android Development] robby2107:
Sorry, but the GPS isn't working.

It's absolutely impossible to navigate with the I9100 and this ROM.

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Android Development] Sub_Zero2:
You might be able to fix the gps problem yourself...

Have a look here (and read 3 or 4 pages to see the solution): https://xdaforums.com/galaxy-s4/i95...eos-15-1-unofficial-galaxy-s4-t3747831/page37
[Galaxy S II Android Development] Boolian:
Was just passing and noted comment about LTE networks.

I recently inherited a Z3C (Sony) and if anyone really misses the S2 form factor,the Z3C is a great cheap substitute.

The downside is that its a real pain to root and development is perhaps not quite as broad as the S2/i9100 though very admirable

No official LOS and currently perhaps only Omni & Carbon active on 8.1.

Sorry it's a bit O/T for our S2 but thought I'd mention it.
[Galaxy S II Android Development] ibebak:
thx and BLE

to devs, you are amazing for work you did here. stable / fast / longlasting (2days with new baterrry )

Even radio app is working fine, but how about bluetooth BLE? I suppose it did run on cm 11. Is there any

quick solution for reworking or is it far behind priorities and interests?
[Galaxy S II Android Development] ale5000:
He merged it today.
[Galaxy S II Android Development] lallolu:
My navigation button is always on even when the phone is not being used. Does anyone know how to fix this.
[Galaxy S II Android Development] Acid0057:
I haven't used Lineage for a while but if memory serves me I think it was something about toggle the BLN on and then off again. Worth a try.
[Galaxy S II Android Development] Teekanne3000:
Go to settings > buttons > backlight.

Greetings

Teekanne
[Galaxy S II Android Development] toshibashi:
[MENTION=2193982]lallolu[/MENTION]

You mean your navigation button is backlit?

I've got two Galaxy S II i9100, none of them has ever shown a backlit navigation button. Must be blown LEDs or something missing?

Best regards,

Toshibashi
[Galaxy S II Android Development] ale5000:
Has anyone tried TWRP 3.2.1?

Does everything work properly again?
[Galaxy S II Android Development] guest4711:
I use it since may 3rd. I did not try encryption, everything else worked well (filemanager, terminal, wiping, flashing ROMs, flashing mods like NanoMod or f-droid.ota).
[Galaxy S II Android Development] ale5000:
Haven't you tested a more recent version than may's one?

There is version 3.2.1-0 (with date 2018-06-18) on the official TWRP site and here.
[Galaxy S II Android Development] guest4711:
No, my version is 3.2.1-0, downloaded and installed on may, 3rd. It works well even for flashing O, so there was no need to search for an update. As I read now, it should be similar to the (now) current official one, while the newer one (-2) will become the official -1 (see https://xdaforums.com/galaxy-s2/orig-development/recovery-twrp-3-2-1-0-t3740526/post76429114 ff.)
[Galaxy S II Android Development] ale5000:
Thanks for the reply but I would like to know if someone have tested the latest official TWRP 3.2.1-0 with date 2018-06-18 with a Nougat ROM.

There are these changes that seems important:

* Fix internal storage

* Mount it properly in MTP

* Various fixes

* Proper mapping of internal storage

* MTP and ADB

* Compatibility with SD cards formatted in FAT32, exFAT, and NTFS

* Update Android.mk
[Galaxy S II Android Development] noobgs2:
Hi to all of you,

I have a question, I don't no if i can ask it here, but anyway,

Can anyone tell me if with this ROM, the maximum sd card capacity of 32GB changed?, and if so, Will it work with Samsung MicroSD Evo Plus 128G?

Thanks for any response.
[Galaxy S II Android Development] vdhero:
I got a 64GB SDcard working on this device. On any ROM actually. But the larger the sdcard is, the more battery drain you get on every boot as the phone has to scan more on the sdcard. I read some where that the 128GB SDcard works but I can't find it anymore. Give it a try.
[Galaxy S II Android Development] noobgs2:
Thanks for the response,

I'll buy a 128GB, and give it a try, I can always use the sdcard with one of my other phones.
[Galaxy S II Android Development] sky321:
I tested the version today but had trouble with updates via official updater. The update installation stuck in twrp with an error. After I changed back to 3.1.0 all went well again. I‘m running the official Los14.1 with microg.
[Galaxy S II Android Development] officiallyme:
I only just switched to this ROM and really like it :)

Only problem is the GPS fix. Does anybody know of a solution to get a GPS fix? I was outside for 30min today and did not get a fix.
[Galaxy S II Android Development] Sub_Zero2:
gps.conf file.. Try to turn down the accuracy (search google)
[Galaxy S II Android Development] mithic:
Same situation happen to me.

Solved by reinstalling older twrp 3.1.0.
[Galaxy S II Android Development] officiallyme:
I will try to play with the gps.conf again file, thank you.
[Galaxy S II Android Development] toshibashi:
i9100 GPS reception is generally poor (as with most smartphones) since the antennas are rather small, see images. I'd like to attach a piece of wire working as an inductively coupled half-wave dipole antenna adjusted to the GPS frequency. It could easily be fixed to the back cover of the phone with a piece of Scotch tape.

I'm looking for an app to immediately display GPS signal level changes to optimize my antenna.

Best regards,

Toshibashi
[Galaxy S II Android Development] Acid0057:
GPS status should work for you. It's on the Google Play store.
[Galaxy S II Android Development] ale5000:
What happened to the build of this week?
[Galaxy S II Android Development] toshibashi:
Thanks for the hint. I discovered I already got a similar app, GPS Test. It takes a couple of minutes to get a GPS fix with both apps. I couldn't see a signal strength indicator with GPS status so I'll keep on trying with GPS Test. Thanks anyway.
[Galaxy S II Android Development] Acid0057:
Np glad you found something that works for you.
[Galaxy S II Android Development] asia559571:
Ooooh!!! Any screenshots and how is running on i9100????
[Galaxy S II Android Development] vdhero:
Google is free. Why don't you just do a research. You'll get lots of result for "LineageOS 14.1 Galaxy S2" on youtube.
[Galaxy S II Android Development] asia559571:
OK! but please can you share thoughts on the battery life, some time ago I tried an acip 14 Rom, ( nice:) ), but battery drain for me was a little too much so I went back to CM 11, 2 years since so if you came from CM 11 perhaps you share thoughts on battery. I've never tried the Lineage before that's why I ask, I did try Youtube but most of the vids were about install and not review.

Many Thanks and Kind Regards:)
[Galaxy S II Android Development] vdhero:
I switched to LOS 15.1 since build 13 but I still can remember a little bit about its battery life. It's pretty good. Back then, I installed the ROM twice. Then first time was with Gapps. It works fast, but the battery drain about 5% every hour. After I'm bored with G-Apps, I reinstalled the ROM with microG. The battery only drain about 3% every hour without G-apps. Why don't you just start using LOS 15.1? It's nearly bugless now. The battery is pretty impressive. I install build 14 with Full G-apps package and Xposed. Then,open trust, privacy protection and just decline the run in background permission for all Google apps. Also, I used greenify and Prevent running xposed module and powernap. The battery is really good.
[Galaxy S II Android Development] asia559571:
Thank You! On my S2 CM 11, I use Xposed and I can get days of battery, with airplane mode and standby I've had 34 hours with 1% battery drop, it's great for battery and ample memory hence the questions, wondering whether to take the plunge or stick with what I've:confused:

Thank you again for the info and Kind Regards :highfive:
[Galaxy S II Android Development] mithic:
some posts back i wrote:

"Same situation happen to me.

Solved by reinstalling older twrp 3.1.0."

....and the same ( :confused:) ) with the newest twrp 3.2.2.0 when try installing nightly of 05.07.2018!!!

back to twrp 3.1.0.0 and the automatic ota update worked great!!!!
[Galaxy S II Android Development] marzametal:
When "[ROM][I9100][UNOFFICIAL][8.1.0] LineageOS 15.1 [WIP][BETA]" becomes full stable, is this 14.1 ROM still going to receive security updates?
[Galaxy S II Android Development] vdhero:
It should still be updated weekly so We wouldn't worry. Besides, most devs use jeskin or something like that so the ROM will be built automatically.
[Galaxy S II Android Development] toshibashi:
USB OTG mode and charging simultaneously?

Does the current kernel allow USB host mode (OTG) and charging at the same time? Does it sense the ID pin (4) for the presence (and value) of a mode coding resistor?

I connected a powered USB OTG hub with a switched 68 kΩ resistor intended to trigger the charge function but the phone won't charge, no matter if the resistor is witched on or off. I've seen others using 36 - 40 kΩ. resistors. Should I try this or is the OTG+charge mode disabled by the kernel?
[Galaxy S II Android Development] toshibashi:
I connected an adjustable resistor to the ID sensor (pin 4) and carefully tuned its resistance. Here's what I found out:

--- 0 - 20 kΩ activates OTG

--- 234 kΩ gives a plug-in beep and starts charging, but unfortunately OTG host mode stays disabled

--- 330 - 400 kΩ opens screensaver display (only on my old Jelly Bean stock ROM model)* ps

--- 36, 68, 100 or greater than 400 kΩ does nothing at all

I did these tests using a powered USB hub so maybe the hub's circuit is blocking the host function. I think I should try a Y-cable instead: USB Micro plug (+resistor) to the phone, USB micro jack to inject power, USB-A jack as the OTG host port - all soldered in parallel.

ps

not only on my old Jelly Bean stock ROM model but on Lineage 14.1 too
[Galaxy S II Android Development] Klaerchen:
The i9100 uses the max8997-muic chipd to handle charging and detecting the ID pin of USB.

In the driver sources you find the table

enum {
ADC_GND = 0x00,
ADC_MHL = 0x01,
ADC_DOCK_PREV_KEY = 0x04,
ADC_DOCK_NEXT_KEY = 0x07,
ADC_DOCK_VOL_DN = 0x0a, /* 0x01010 14.46K ohm */
ADC_DOCK_VOL_UP = 0x0b, /* 0x01011 17.26K ohm */
ADC_DOCK_PLAY_PAUSE_KEY = 0x0d,
ADC_CEA936ATYPE1_CHG = 0x17, /* 0x10111 200K ohm */
ADC_JIG_USB_OFF = 0x18, /* 0x11000 255K ohm */
ADC_JIG_USB_ON = 0x19, /* 0x11001 301K ohm */
ADC_DESKDOCK = 0x1a, /* 0x11010 365K ohm */
ADC_CEA936ATYPE2_CHG = 0x1b, /* 0x11011 442K ohm */
ADC_JIG_UART_OFF = 0x1c, /* 0x11100 523K ohm */
ADC_JIG_UART_ON = 0x1d, /* 0x11101 619K ohm */
ADC_CARDOCK = 0x1d, /* 0x11101 619K ohm */
ADC_OPEN = 0x1f
};

In my opinion, only the modes MHL, CEA936, DESKDOCK, CARDOCK are candidates for an operation with external power supply and charging of the battery.

But all are intended to somehow deliver audio signals to an external system (except MHL which is for video). So I don't see, that you could find a way, to have USB host and also charging of the battery.
[Galaxy S II Android Development] toshibashi:
Thanks for the table. Didn't help me, however, sorry. I read a lot of different numbers and approaches.

USB.ORG sez:

Battery Charging Specification, Revision 1.2 December 7, 2010
[CENTER]Table 5-3 Resistances[/CENTER]
. . .
Dedicated Charging Port resistance across D+/- R DCP_DAT 200 Ω
D- Pull-down resistance R DM_DWN 14.25 .. 24.8 kΩ
D+ Pull-down resistance R DP_DWN 14.25 .. 24.8 kΩ
D+ Pull-up resistance R DP_UP 900 .. 1575 Ω
ACA ID pull-down, OTG device as A-device R ID_A (Note 1,2,4) 122 .. 126 kΩ
ACA ID pull-down, OTG device as B-device, can’t connect R ID_B (Note 1,2,4) 67 .. 69 kΩ
ACA ID pull-down, OTG device as B-device, can connect R ID_C (Note 1,2,4) 36 .. 37 kΩ
ACA ID pull-down when ID_OTG pin is floating R ID_FLOAT (Note 2,3) 220 kΩ
ACA ID pull-down when ID_OTG pin is grounded R ID_GND (Note 2,3) 1 kΩ

Notes
1) The ACA shall meet this parameter requirement when VBUS_CHG is at V ACA _ OPR .
2) The ACA shall meet this parameter requirement when its ID_OTG pin is at V DAT _ LKG .
When detecting these resistances, an OTG device shall allow for an additional leakage current
of I ID_LKG_CONT due to contamination.
3) The ACA shall meet this parameter requirement when its VBUS_CHG pin is at V BUS_LKG .
4) Nominal values for these resistors are R ID_A = 124k, R ID_B = 68k and R ID_C = 36.5k

(ACA: Accessory Charger Adapter)

These resistances don't work neither. I guess my Lineage 14.1 kernel (is it the same as with CM14?) simply doesn't allow OTG charging. Is it possible to run Lineage 14.1 with a CM13 or even CM9 kernel?

One other idea:

I'm using a simple 5 V source. Do I have to use an Accessory Charger Adapter or a special cable as specified above with 20 kΩ and/or 200 Ω resistors at the D+/D- lines as specified above?

Best regards,

Toshibashi
[Galaxy S II Android Development] lallolu:
I eventually found the cause. The button was used for notification light. This was why the light was always on and killing my battery. The notification light is now disabled and my phone can finally sleep when not in use. I am surprised though that no one else has complained about this.
[Galaxy S II Android Development] PackElend:
This process didn't get along smooth at all but I'm quite happy that latest LOS 14.1 runs on my S II. There were some events during this process which haven't been answered yet. May some of you can answer some of them, e.g. why I could flash only with TWRP 3.1.0 EMU.

-----

I case the quote don't gets you to the referenced post: 22th July 2018, 09:34 PM |#92
[Galaxy S II Android Development] BatyuS:
friends network problem appeared when I returned to version 4.1.2 when I returned to lineage the phone does not see the sim card again. do you help?
[Galaxy S II Android Development] davavab:
Is it possible to enable CONFIG_JOYSTICK_XPAD in defconfig/kernel (LOS 14.1) by default so controllers like xbox 360 get automatically recognised?

Or how can I enable it manually?
[Galaxy S II Android Development] DevisG79:
Am I the only one having this Error message when installing latest nightly with TWRP 3.2.2.0?
[Galaxy S II Android Development] davavab:
I had problems with TWRP 3.2.2.0 too but then it worked with an older version twrp-3.1.0-0
[Galaxy S II Android Development] EngineJoe:
I also got the "fail to map" error when I tried TWRP 3.2.2.0 so returned to 3.1.0.0.
[Galaxy S II Android Development] vdhero:
TWRP 3.2.XX are for oreo, you can't use it to install nougat
[Galaxy S II Android Development] andreoide:
Thats the biggest BS bogus noncence i ever read anywhere. Its completely not true.

I succeeded install lineage 14.x and 15.x for i9100 with latest so its total nonsence you put here.

//EU.DL.twrp.me/i9100/

Latest TWRP is always quality update and not OS- based!!

Why you write such noncense?

Give us links and not your own words, but links from 3rd OFFICIAL party here wich prooves that you say should be true.

Or else stop feeding this thread with noncense no one had anything from!!!
[Galaxy S II Android Development] DevisG79:
So, you are right. Thank`s a lot. Flashed back to TWRP 3.1.0.0 and then lineageOS 14.1 20180726 and it works. :victory:
[Galaxy S II Android Development] Cymrodor:
The Setup Wizard strings (CM 13.0 and 14.1) have now all been completed and proofread a few months ago. Welsh still does not appear in the list of languages available during LineageOS setup.

Welsh (Cymraeg) does appear and can be selected under "Languages & input" once LineageOS has been installed, but this doesn't change the OS language. It only appears to have an effect when set as the only language, i.e. English is removed, but it still doesn't set the OS language to Welsh. The only parts which appear in Welsh are dates, times, days of week, etc.

I wonder what needs to change for Welsh to appear in the language list upon setup?
[Galaxy S II Android Development] PackElend:
At least I can confirm that OTA is working but the other problems/question still persist/exist

Anyone willing to give me a hand?

I desperately need it
[Galaxy S II Android Development] doctor-who:
im getting random reboots all the time and some mtp service stopped at start, did clean flash followed all steps came from jb stock
[Galaxy S II Android Development] doctor-who:
Solution?
[Galaxy S II Android Development] Midaa:
I just installed LOS 14.1 and it works great, beside some rare MTP crashes. However, I noticed that the battery drops 3%/hour without any usage (network ON) Are you guys using DorimanX kernel or any other tips to reduce usage ?
[Galaxy S II Android Development] doctor-who:
There's deep sleep issue which causing battery drain
[Galaxy S II Android Development] vdhero:
Deep sleep is working totally fine in this ROM, just may be because he installed gapps and has mutiple email syncs in the background
[Galaxy S II Android Development] doctor-who:
how to use phone normally without gapps?? are u kidding me? And yes there is deep sleep inactive. Also cant restore efs backup from stock, tried many ways i still dont have imei imei sv baseband and thats it. EFS Pro for pc says cant list partitions, whats going on here?
[Galaxy S II Android Development] the.gangster:
LOL...

You "found" the cause?

You got 2 or 3 answers almost immidiately after posting your question. All were hinting you on exactly that. Maybe next time read the replies to your questions and if you don't understand them, simply ask for more details.

That notification light (called BLN btw) does not necessarily prevent the device from deep sleep. But you probably will not read this answer here anyway so why should anyone explain...

Why so rude?

If you were right at least, but you are not. Simply search/read the posts yourself here and in the TWRP thread and you'll find many users reporting such problems and even the developer himself advises people prior to OREO to stick to the older TWRPs.

Solution for what? A vanished IMEI? Going back to stock Samsung ROM where it's often possible to recover IMEI information again.

Had to go through it long time ago and started by reading this thread. It wasn't 100% accurate if I remember correctly, but if you understand the logic behind it you might be able to fix it manually that way.

Is there??? How come my phone kind of runs (sleeps) for ever if not in use?

EDIT: and I am using almost stock version of OpenGapps (with some exclusions)
[Galaxy S II Android Development] doctor-who:
[MENTION=6560258]the.gangster[/MENTION] I have flashed stock firmware few times via odin and still no IMEI, IMEI sv, baseband. The backup I have when restore on lng 14.1 there's again same thing. If you have solution that will somehow give back that info's I would be grateful alot. About deep sleep I use cpu spy says deep sleep is in unused state, and yes I use Google account and all possible synchronisation with it. That guy who mentioned buttons light is wrong, will check tomorrow which apps causing deep sleep to be inactive
[Galaxy S II Android Development] vdhero:
Have you ever heard of MicroG? Lots of people use it and they don't need gapps anymore. try to go back to stock rom and restore your imei
[Galaxy S II Android Development] doctor-who:
Now turned on laptop... Have original stock nandroid backup with cwm, there was damn IMEI just to try and will see..
[Galaxy S II Android Development] guest4711:
No, I did not install any g-apps on any of my devices. I'm using f-droid to install the needed apps (e.g. k9mail, fennec droid, telegram) and the location services of microG (for privacy and for offline navigation). If I really need an app not available on f-droid I use yalp. Contacts and calendars are synced to my notebook via usb using MyPhoneExplorer.

And I never missed g-apps til now...
[Galaxy S II Android Development] doctor-who:
Here nothing helps, restored whole efs folder it's all same now even power button not opening menu it turns off phone, have full desktop with efs backups of many ppl I will eat this phone and chew it until all teeth I broke!

---------- Post added at 11:27 AM ---------- Previous post was at 11:27 AM ----------

Wish can be that easy on other phones which can't be even rooted