yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S8 Questions & Answers] SebringTech:
I see people asking about flashing their AT&T and TMobile phones to Verizon, but I'm wanting to do the opposite.

I have a sim unlocked S8+ and I recently switched to Cricket who uses the AT&T towers. So I thought it was possible if I flashed the AT&T firmware I would get better reception unless the phones for the different carriers lack the radio capacity but my wife's Pixel switched and gets 4G everywhere. I get 4G in town and it switches to H or H+ when I'm in smaller towns and it doesn't matter which preferred network I have it set to or global mode.

It is the Verizon model though, so I don't know if the boot loader being locked would prevent a different firmware flash from ODIN. I've had plenty of experience with the program from rooting my S7 Edge, S5, and S6. Just the 8 has been a tough nut to crack it seems.
[T-Mobile LG G5 Questions & Answers] Charkatak:
Looks like G5 should support advanced messaging feature on T-Mobile. I had few Samsung phones that had some settings in the messaging app. G5 for some reason doesn't have any settings in messaging app that would point to advanced messaging. I texted my friend who has Galaxy S8, who is also on the same network. He can see when I type a message, but I don't see when he types. Looks like it could be working half way for some reason.

I noticed that on T-Mobile's support page, one of the older updates has: Advanced messaging issue fixed (Software version H83010d)

https://support.t-mobile.com/docs/DOC-30673

What works at the moment:

1) VoLTE

2) Video calling

3) Band 12 support

4) WiFi Calling

5) HD Voice

My phone supposedly has the latest software of H83020i with April security patch.
[T-Mobile LG G5 Questions & Answers] Skipjacks:
Use these steps to set up and use SMS / MMS messages with Advanced messaging on the LG G5.

Change advanced messaging settings

Tap Messaging.

Tap Menu > Settings.

Tap More.

Change settings for Text messages or Multimedia messages as desired.

https://support.t-mobile.com/docs/DOC-30606

It probably won't work with all 3rd party text apps. For instance I use an older version of Handcent (I'm not giving it up!!! Screw you, crappy update!) and it has a built in 1MB limit for photos. But that's an app limitation, not a phone limitation. It still sends an image, but it reduces the size. It also won't support the "see that the other person is typing a message" thing.

But again..app limitation.
[T-Mobile LG G5 Questions & Answers] Charkatak:
I have seen the above doc from T-Mobile and there are no settings about advanced messaging of any kind. I am using stock messages app that was on the phone. As I understand, it should just work, if there are no other visible to the user settings. On Samsung for example, there are chat settings options in the messaging app.
[T-Mobile LG G5 Questions & Answers] Charkatak:
It started working: I went to recovery and wiped cache, then restarted the phone. Advanced messaging options appeared in the app's settings.
[OnePlus 5 Questions & Answers] g-member:
I've been plowing thru the topics and didn't find a working solution...

I can't get stock recovery flashed back for the new OTA, fastboot gives an to big file size error....

Tried diffent cables, usb ports en fastboot versions....

It worked perfect before..

Anyone?
[OnePlus 5 Questions & Answers] 0xTJ:
Are you sure you have the right file? And you don't need stock recovery to get OTA. As long as your build is stock, installing should be fine.
[Galaxy S II Android Development] Saber:
Changelogs:

--UNRELEASED VERSIONS (KERNEL UNDER TEST) --

For live changelogs, see my github:

Kernel: Github Link

Initramfs (Ramdisk): Github Link

--RELEASED VERSIONS (GENERAL AVAILABILITY) --

[B]DorimanX 13.0 b005[/B]
- Pulled updates for tcp, net, uksm, binder and many more from DorimanX OP3T kernel, all thanks to @Realex-fire
- Minor build script improvements
- TCP fast open control added to Stweaks
- HYPER is now the default sleep governor
- Updated busybox from Dorimanx source - Again thanks to @Realex-fire
- Minor fixes to ROM init script

[B]DorimanX 13.0 b004[/B]
- Synced scheduler and block changes from linux 3.16
- Synced security/keys and selinux changes from linux 3.16
- Synced kernel/fork, lmk and other changes from dorimanx
- Temporarily disable playready DRM to fix package manager corruption issues
- Remove powerHAL introduced in lineageOS to remove governor setting conflicts
- Various script improvements thanks to @Realex-fire

[B]DorimanX 13.0 b003[/B]
- Reverted default governor back to HYPER
- Synced ext4 updates from mainline - Thanks to @Realex-fire
- Partition checking will only check for bad blocks now
- Lower cortexbrain auto read ahead values and add 3072KB option
- Stweaks settings will be reset after flashing this build!

[B]DorimanX 13.0 b002[/B]
- Updated exfat from Dorimanx sources
- Reverted the kernel's internal tick rate back to 250
- Changed default governor to Nightmare
- Stweaks profile updates
- Enable adb autostart and insecure adb for debugging purposes

[B]DorimanX 13.0 b001[/B]
- Initial LOS14.1 Support
- Re-added Adaptive LMK and UKMS - Better for RAM usage at the cost of some CPU time
- LZO is now being used as the default compression method for ZRAM - Much better compression, worse decompression. Better for our ZRAM size limitations.
- Synced recent zzmoove updates - New profile, stability updates, some code only for SD devices
- ZEN I/O scheduler updates from Dorimanx
[Galaxy S II Android Development] Saber:
Downloads

--STOP!!! IMPORTANT, PLEASE READ--

It is important that you make a backup before flashing this kernel. If you want to restore the original kernel found in your ROM, you need to restore from a backup or clean flash your ROM.

MAKE SURE YOU'RE DOWNLOADING THE RIGHT KERNEL. OTHERWISE YOU COULD BRICK YOUR DEVICE!

Flashing instructions:

1. Download latest kernel build

2. Reboot to recovery

3. Flash kernel zip

4. Reboot

For TRIM users:

To use TRIM, you can download an app on the app store called trimmer or use terminal commands as directed in the troubleshooting guide.

Isorec (Isolated Recovery)

You can use either TWRP or CWM. It is important to note that the default CWM recovery has kernel specific options within the menus, so if you require to use them, be sure to flash the isorec disabler.

Download for isorec recoveries:

https://www.androidfilehost.com/?w=files&flid=47550

If you have a dualboot setup or if you want to set up dualboot, you should stay on StanTRC recovery. If you want to return to StanTRC recovery, flash the isorec disabler:

https://www.androidfilehost.com/?fid=24369303960682947

Forgot to download backup/older kernel/isorec disabler after flashing TWRP?

Go to download mode and flash a kernel .tar file OR wait until OS boots and copy required files to your phone

Main download link:

https://www.androidfilehost.com/?w=files&flid=201577

Mirror download link:

https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel/releases

In order to tweak the kernel properly, you need to install stweaks from the apk linked here, or from the XDA downloads page
[Galaxy S II Android Development] Saber:
First kernel build for LOS14.1 is up on AFH and github. Enjoy.

Firstly, sorry for the dupe threads. Internet was acting out and now I'll have to get the mods onto it :)

Also, expect bugs with this release. This is a really early build and I'm doing blind builds now.

Don't flash on any other ROM than LOS otherwise you will not receive support. This kernel is only designed for LOS.

No new features will be added because I don't use the S2 as daily driver, so I won't be able to test changes thoroughly.

Regards, Saber
[Galaxy S II Android Development] GreekDragon:
Nice. :D
[Galaxy S II Android Development] TriboDoP:
Hi [MENTION=5811506]Saber[/MENTION]

Thanks a lot for spending your spare time to work on this kernel.

I wish you the best!
[Galaxy S II Android Development] Skyline:
Welcome back [MENTION=5811506]Saber[/MENTION] ;)

EDIT: I am not able to get it work on latest LOS 14.1 build. May be something wrong on my side. Phone going back to galaxy s2 logo from dori kernel logo. This is happening in loop. Anyone???
[Galaxy S II Android Development] Syaani:
Yeah this is cool. Maybe we can make S2 N-builds even better. :laugh:
[Galaxy S II Android Development] Saber:
Can you please detail your flashing procedure? Did you try reflashing the kernel?
[Galaxy S II Android Development] Skyline:
I get it to work after too many tries and now again I am not able to boot.

*Wiped everything other than ext sdcard

*flashed rom and gapps

*flashed kernel zip

Also tried without gapps. Weird thing is that whenever I flash gapps it gives me alot of force closes. I tried 2 gapps packages and AICP but same problem occurs(without flashing kernel) that's why I thought may be something wrong on my side

Edit: I am using I9100g display panel can it be reason for my problem?? Anyways I attached dmesg.
[Galaxy S II Android Development] X_Svyatoslav_X:
Nice

Nice Kernel,Works fine on los14.1 and I also have overclocked up to 1.6 MHz but would not like to add 2.0 MHz in future updates?

And is it possible to add support to the kernel dt2w ?

Sorry if I'm not writing correctly, I'm not an Englishman :laugh:
[Galaxy S II Android Development] Syaani:
If you mean 2,0GHz I doubt it.

I tried F2FS and it seems cache is okay but data makes android.phone process crash all the time. Not sure if it is LOS or kernel's fault.
[Galaxy S II Android Development] Skyline:
What?? 2.0 Ghz is too much and also not safe. Even overclocking more than 1.4 Ghz is not good for our old device. I think we should limit cpu clock to 1.4Ghz max on this kernel for safety [MENTION=7005908]saber.[/MENTION]
[Galaxy S II Android Development] Saber:
This issue is actually kernel's fault as it also exists on my CM13 kernel. A reboot is a possible solution to solve this issue and it shouldn't reappear. I might pull some F2FS updates from the linux git to increase stability, however the only filesystem I recommend is ext4 for internal partitions.

Edit: I was thinking before about a kernel issue where after first flashing the kernel over stock LOS kernel, the phone process would crash where it can be solved by rebooting. Need more reports to see if its just F2FS or if its regardless of fs used.
[Galaxy S II Android Development] Saber:
2.0GHz? Not possible with our SOC. 1.6GHz is about the limits and only a lucky few are able to use this frequency. Any more and I'd suspect our tiny SOC go poof along with some bad electronic smoke.

dt2w is not optimised for our touch panel and as of a result, significant battery drainage will occur. It's the same story with sweep to wake, these features weren't even supposed to be possible with our device.
[Galaxy S II Android Development] Saber:
I've had a quick skim over the dmesg and couldn't find anything too substantial to be the root cause of the issue (may need to go through with a fine comb). Maybe logcat? How about marshmallow? Does the same behaviour occur there?
[Galaxy S II Android Development] Skyline:
If I comment last lines in init.rc then rom boots fine :(

EDIT: [MENTION=5811506]Saber[/MENTION], How can I take logs during s2 bootlogo to dorimanx kernel logo? I tried to take logcat using command 'adb logcat > log.txt' on linux but device is not getting detected.
[Galaxy S II Android Development] Nobby1960:
With 2.0 GHz the CPU will explode :p
[Galaxy S II Android Development] Saber:
Last time I tried it, adb should be working while on the ROM bootscreen (and this feature allowed me to fix a lot of the boot issues when I first started porting the kernel). I don't think it should be too different on linux. Another thing that might be related is that secure adb was enabled during a recent ramdisk update, so I don't know if that would have cause issues with the detection. I'm not on the device so my ability to debug is very limited.

Also, did you comment out the post_init service in init.rc? I find it strange that it would be the cause of your issues, but logcat can show the related errors.
[Galaxy S II Android Development] Skyline:
Yeah. I commented the post-init service.

Good news for me at least now I am able to boot successfully. I don't know how and for how much time it will work bcoz whenever I reboot it stucks in same condition. Thanks for attention though.
[Galaxy S II Android Development] Egyptianator:
Well that is 48 hours testing and the kernel is almost perfect, very smooth compared to an alpha build and hyper governor seems to be lowering the effects of the s2 overheat problem i would like to thank you for that great work :good:

KEEP GOING ON :victory:
[Galaxy S II Android Development] cascabel:
Using ext 4 here. Did a clean flash (rom>gapps>lineage su>this kernel). Never had phone process crash. I'm on latest los, i9100.
[Galaxy S II Android Development] Egyptianator:
I think i found a bug that after powering the device the touch screen don't responx however the buttons did i am on lineage build 26_7_2017 latest
[Galaxy S II Android Development] Saber:
Hi there,

Is it possible for you to provide a dmesg and logcat?

Edit: Could be just kernel panic, but without logs I can't be certain.
[Galaxy S II Android Development] Egyptianator:
I don't think i can because the only way the phone returned back to normal was after I removed the battery

another thing i noticed is that after the second boot the kernel is back to all default setting in Stweaks and not even a single change i made is remaining
[Galaxy S II Android Development] AlexanderDG83:
Flashed dorimanx over latest laos nightly; all work good! Thanks for your work! [emoji106]
[Galaxy S II Android Development] Saber:
The kernel usually resets when there is a problem with stweaks settings (OV, UV), stability issues, etc. It may be just a kernel panic, or even memory allocation issues, but there are many things that can cause this to happen.
[Galaxy S II Android Development] chhapil:
lot of new changes in your git, i'm drooling :) :good:
[Galaxy S II Android Development] Saber:
New kernel build is out, enjoy :highfive:

Changelog:

DorimanX 13.0 b002
- Updated exfat from Dorimanx sources
- Reverted the kernel's internal tick rate back to 250
- Changed default governor to Nightmare
- Stweaks profile updates
- Enable adb autostart and insecure adb for debugging purposes

Fairly minor update compared to previous build, but it does include some worthwhile changes. As always, report any bugs with logs (if applicable) so I can help with the best of my abilities.

Also, if you're wondering why I've changed the default governor to Nightmare, it is because I want to experiment with the governors and see if it helps with stability and battery. I don't mean that HYPER is unstable (in fact, it's the exact opposite), I just want to ensure the best possible experience with my kernel. If you don't like the change, you can always change the governor in stweaks.

Regards, Josh
[Galaxy S II Android Development] kiva1:
Flashed last kernel build, and STWeaks always shows this message. And on every reboot it clear all my app permission, and setting in the play store and few other app including XDA Lab.
[Galaxy S II Android Development] Saber:
Seems like you're experiencing some serious corruption. Try formatting or wiping your cache and reflashing kernel. Unfortunately, if you still have issues, you may need to clean flash your current setup.

On the same note, I'm trying to investigate why the kernel frequently experiences corruption issues. Not too sure if it was as frequent before I started maintaining, but pinpointing the cause is not an easy task unfortunately. I take data integrity seriously so it is up in my priority list.
[Galaxy S II Android Development] kiva1:
Will try later today n report. that happened and with previous version.
[Galaxy S II Android Development] Nobby1960:
I noticed a wipe of cache/dalvik after flashing the kernel doesn't come so well. You land in a boot loop :eek:
[Galaxy S II Android Development] Skyline:
If device shows bootanimation then you will be able get logs through adb and share it here. That will be very helpful
[Galaxy S II Android Development] Saber:
New build is out! :highfive:

Changelog:

[B]DorimanX 13.0 b003[/B]
- Reverted default governor back to HYPER
- Synced ext4 updates from mainline - Thanks to @Realex-fire
- Partition checking will only check for bad blocks now
- Lower cortexbrain auto read ahead values and add 3072KB option
- Stweaks settings will be reset after flashing this build!

Default governor was changed back to HYPER due to scaling issues on Nightmare. ext4 updates should help the (internal) filesystems be more stable. Partition checking should appear less and should only check for bad blocks.

Keeping in the same topic with partitions, the corruption issues are still being investigated. It seems that the corruption (or loss of data) occurs after fixing partitions (or in there whereabouts), which is normally not a completely safe operation on your data. Keep backups on an external sd card for the best experience and also ensure to backup regularly. Bad data blocks can exist before installing my kernel and the kernel might be a little too fussy with insignificant errors (so logs will start appearing), so the kernel really doesn't get all of the blame.

Cortexbrain will set slightly lower read-ahead values for certain sd card sizes in favor of latency over throughput.

Stweaks settings will be reset! This is because of the default setting changes I want reflected on every users device.

Regards, Josh
[Galaxy S II Android Development] Nobby1960:
In my attachment is an adb logcat from the boot loop phase (with bootanimation), after wipe cache/dalvik. It's the latest kernel build from today. Hope it helps. The phone became very hot, you can boil water with it :p
[Galaxy S II Android Development] Oriceles:
Hey Saber thanks for the awesome work, I tried to flash this kernel but everytime I try I get zip corrupt, I even created a .md5 file to compare and added to my sdcard but it keep failing. I'm trying to flash the latest version. Other weird I'm noticing is that after I create the nandroid they don't appear on my sdcard, and the .log file of the recovery which I saved to try to add it here is missing as well
[Galaxy S II Android Development] Saber:
With corrupted zip, does the same thing occur when you download from both links (AFH and Github)?

As for recovery, what version are your running? Does the same issue occur on both internal and external storage? What filesystems are you backing up?
[Galaxy S II Android Development] Oriceles:
I'm sorry for my noobness, I went google and it seems my external sd card has corrupt permissions, so I moved to internal storage and was able to restart to system without a problem :good:

i.imgur.com/fZtPbH5.png (xda won't allow me to hotlink yet)

Now, I have a question regarding lineage os nightlies. Can I have them enabled or I have to manually update and then flash the kernel again?
[Galaxy S II Android Development] Saber:
Best to manually update in-case of any issues. Once the ROM updates, and if you forget to flash the kernel, you'll notice a lot of basic functions will not work. After flashing kernel again, everything should be back to normal.
[Galaxy S II Android Development] Skyline:
How much time you waited until considering as a bootloop? bcoz log shows it's still optimizing apps.

You're using this kernel on aicp??? If so, problem is same as this one https://github.com/gsstudios/Dorimanx-SG2-I9100-Kernel/issues/74

[MENTION=5811506]Saber[/MENTION] did checked the attached logs? I tried but not able to see root cause :(
[Galaxy S II Android Development] Nobby1960:
First I tested to wipe cache/dalvik with the stock kernel, this worked normally. Then I flashed the DorimanX, after this I wiped cache/dalvik again and I did the adb logcat during the boot animation, in approximately 15 min - then the logcat went no further. The phone became so hot that I got doubts. You mean it could be AICP? I will test the whole again with plain vanilla LOS 14.1 to figure it out.
[Galaxy S II Android Development] Skyline:
May be or not aicp but there is something wrong with kernel that caused bootloop on Resurrection Remix MM previously so this can be same case.

Again, from your log this doesn't seems like bootloop and you may get time to try it again.
[Galaxy S II Android Development] Nobby1960:
Okay - new try, same procedure: A working AICP 12.1, flashed DorimanX, wiped cache/dalvik.

Begin of logging: 08-03 21:34

End of logging: 08-03 22:10 (canceled from me)

It seems like a veeeery slow start - you see always the boot animation. The logfile is much bigger - I must zip it ;)
[Galaxy S II Android Development] Saber:
I've checked the previous log but only could find errors with the ROM only supporting PIE (executable blocking security feature), and hence some scripts could not run. If the log is from AICP, then I won't be adding support for that ROM as I will be only maintaining for Lineage.
[Galaxy S II Android Development] Nobby1960:
This is no problem, the kernel works with AICP generally. Only after the flashing of the kernel cache/dalvik should not be wiped anymore. I still did not have the time to test all the nice features of the kernel :)
[Galaxy S II Android Development] braniels2:
bootloop here and i have button power broken xD
[Galaxy S II Android Development] Nobby1960:
Just remove the battery. I have one phone for spare parts here with a broken power button. To reboot the phone: Put in the charger, then the battery and press volume down, there is the warning screen. Now volume down again for reboot. If you want into download mode, press volume up ;)

Edit: Which ROM is on your phone - did you wipe cache/dalvik after flashing the kernel? This could be the cause of the bootloop. Important: The DorimanX is only supported for the plain vanilla LOS 14.1, not for derivates like RR, AICP etc.
[Galaxy S II Android Development] Saber:
New build is out! ;)

Changelog:

[B]DorimanX 13.0 b004[/B]
- Synced scheduler and block changes from linux 3.16
- Synced security/keys and selinux changes from linux 3.16
- Synced kernel/fork, lmk and other changes from dorimanx
- Temporarily disable playready DRM to fix package manager corruption issues
- Remove powerHAL introduced in lineageOS to remove governor setting conflicts
- Various script improvements thanks to @Realex-fire

As you can see, there have been many improvements throughout the kernel since the last build. As always, report any bugs/issues with a logcat or dmesg (with some exceptions inc. ROM compatibility).

Regards, Josh
[Galaxy S II Android Development] sniburn:
ive been using this kernel on my RR latest..seems solid to me excpt some random reboots every 2days or so.usually when im doing nothing(sleeping).it just rebooted haha xD.ill try the latest build then we'll see.thanks for this kernel btw.
[Galaxy S II Android Development] wawa9292:
How to

how did you install this kernel with RR??

I kept getting BootLoop at dorimanx Logo.. never entering BootAnimation at all.. :(
[Galaxy S II Android Development] sniburn:
hmm..ive installed RR then reboot then install Gapps then reboot then flash DXK..dont clear cache after installing the kernel it will lead to bootloop.:good:
[Galaxy S II Android Development] AhmAdDev99:
Hi

I know this kernel is for i9100, But i want to build a kernel based om cm12.1 kernel for i9100g.

I asked in i9100g forum but no one helped. My problem is initramfs, How to get initramfs for my i9100g?

Hope you guys help me, Thanks.
[Galaxy S II Android Development] Saber:
Now the problem isn't just with the initramfs, the kernel base is specific to the international i9100. Initramfs or the (ramdisk) is just the contents of the ROM found in the root directory. Remember, this is a i9100 forum so we don't exactly have the "same" device so to speak (so in other words, this is OT and should be either forum specific post or PM).
[Galaxy S II Android Development] wawa9292:
I've do exactly like what you do yesterday..

But still I can't make it to boot..

Stuck at Dorimanx logo.. btw I use TWRP isorec to install.. were you using another recovery??