yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S II SGH-T989] Easy_as_Pi_3.14:
What carrier are you using?

And by the way, there were also 2 S3s on AT&T: The I9300, without LTE, and the I747, with LTE.

Samsung's own Exynos processor didn't support LTE at the time, so they had to make one with a Qualcomm Snapdragon.

Also, a side note, I looked at Bitly statistics and I found this fascinating:

I knew some of you were from different countries, but…wow.

[font="Fira Sans,Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I727 using AWESOME COLORS!!![/font]
[T-Mobile Samsung Galaxy S II SGH-T989] juni12:
What's new in the latest build?
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
Cm14 - 10-09-16

New update is up. Battery life should be improved in this build. Also included are several improvements thanks to javelinanddart, and various misc fixes.
[T-Mobile Samsung Galaxy S II SGH-T989] jansenw95:
How do you OTA update? I dont get a notification and I can't find the CyanogenMod update setting
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
It's not working this update, but it'll be available for the next build.
[T-Mobile Samsung Galaxy S II SGH-T989] jansenw95:
Ok
[T-Mobile Samsung Galaxy S II SGH-T989] nero50:
i want to give thanks to all you guys trying to help me
[T-Mobile Samsung Galaxy S II SGH-T989] draekko:
Hi nice update, i was wondering how hard it would be to implement raw camera support for this device. Also when i run cinema fv-5 (https://play.google.com/store/apps/details?id=com.flavionet.android.cinema.lite&hl=en) it crashes a lot and there is no preview. It's sister app camera fv-5 (this app supports raw camera image support but only if the device has the drivers/support enabled, tested with nexus 5) does show a preview though so not sure if it's app or rom related.
[T-Mobile Samsung Galaxy S II SGH-T989] donjuanelguapo:
I can't get the Gapps to work and other issues

Let me preface this by saying I am a noob at rooting my phone. With that being said, here is what I've done and the issues I've experienced.

-I have the latest version of TWRP (3.0.2-0).

-I partitioned my phone. However, this step: "In TWRP, go to Wipe -> Advanced Wipe -> check Internal Storage -> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute." It won't allow me to "change file system." It errors each time. However, I have flashed some ROMs that need a partitioned drive and they seem to open but they don't run well, if at all. Nevertheless, your rom loads without issues and, sometimes, it opens to the setup (I have been able to get to the clock set up but then it goes back to the 'ANDROID' screen. I'm guessing I partitioned correctly since no errors occur during the ROM setup.

-I wiped everything and even did a factory reset just to make sure the system is clean

-I run your ROM and the Nano 7.1. from the suggested page. This is where I run in to the biggest problem. I get the following error: "Error 64: Wrong architecture to set-up Open GApps' pre-bundled busybox

Updater process ended with ERROR! Error installing zip file '......open_gapps-x86-7.1-nano-20170119.zip'"

-So, when the ROM loads I get the ANDROID screen. Sometimes it goes to setup but most of the time it doesn't. So, the times it does work I immediately start to get all sorts of android/google (android.process.xx) not loading errors. Then it goes back to the android screen and I have to reboot.

I'd LOVE to use this ROM but I can't figure what I am doing wrong. Please help! Someone!

John
[T-Mobile Samsung Galaxy S II SGH-T989] daman261:
When selecting the Open GApps package you're selecting x86, which is not the correct architecture of the chip set in our phones, select 'ARM', then '7.1', and the Nano package and try again. Advise if this does not work.
[T-Mobile Samsung Galaxy S II SGH-T989] osvaldo3091:
me funciona perfecta esta versión escoge la versión que quiera

It works me perfect this version choose the version that you want.

I use scent of this date.

If you just want to download the open_gapps-arm-7.1-pico-20161129.zip.

Look for this name in the list.

https://github.com/opengapps/arm/releases/tag/20161129
[T-Mobile Samsung Galaxy S II SGH-T989] donjuanelguapo:
First of all, thanks SO much for responding. I really appreciate it.

So, good news, bad news. First the good news, the ARM gapp that you had me select loaded perfectly using TWRP. The bad news is that now the OS ROM is 'stuck' (for lack of a better term) on the 'ANDROID' screen. I've rebooted and rebooted over and over and had the same results: It just won't get past the first screen. This seems to happen with other ROMs I've ran. So far the only OS ROM that I can get to run using TWRP is Validus 5.1.1.. But, and it's a big but, when I find a gapp that opens using TWRP it freezes on the front screen. I've tried multiple Gapps and they all seem to freeze whichever ROM I'm running. Even Validus will not run sometimes and when it does I can't get any google apps to work at all. So, downloading programs from the google play store doesn't work at all. It seems to have something to do with Gapp ROMs.

Your OS from what I can see looks AWESOME! However, now that the Gapp ROM loaded I can't even get to the setup page. I'm not sure what I'm doing wrong. When I had CWM on my phone it opened up several ROMS but many here on XDA strongly recommend TWRP. So, I changed to TWRP.

Suggestions? Is there a way to start over so to speak and wipe everything off my phone? Also, I'm using a Mac so I've tried some things with JOdin3 and Heimdall but that is another topic for another day I guess. I just want these things to work for me. HELP a noobie out! What do I try now?

Thanks,

John
[T-Mobile Samsung Galaxy S II SGH-T989] daman261:
Glad to assist, there is a 'Thanks' button by the way. As for the 'initial boot', and by this I mean Rebooting to System from TWRP following the 'Clean Flash' (will define shortly) of this ROM and the correct GApps should not be longer than 10 minutes, but that being said, the first boot may take a little while and all you're doing when you reboot is prolonging the process (to my limited understanding)

We'll start over, I'd recommend reading the OP and verify your system is clean [a normal wipe should do if you are correctly partitioned].

Next I would flash the attached clean_db.zip, then Reboot back to Recovery. Then flash ROM and GApps.

Also, don't interrupt the boot.

http://xdaforums.com/showthread.php?t=1785999&p=29080999

The link above goes to [MENTION=4057370]vincom[/MENTION] 's sticky which is likely how you got here, however near the bottom are a couple good basic guides for some of the concepts we've discussed, and the rest of the issues that are 'ROM-specific' well those my friend you learn as you go.
[T-Mobile Samsung Galaxy S II SGH-T989] donjuanelguapo:
So here is what I tried with results:

Attempt #1-

--I went in and individually re-wiped Dalvik/ART Cache, Internal Storage, System

--Just for good measure I completely wiped my phone by doing a factory reset

--I flashed the clean_db.zip, which ran successfully

--I rebooted to recovery

--I flashed both LineageOS 14.1 and open_gapps.arm-7.1-nano-20170119. Both these flashed normally (no errors--everything looked great)

--I rebooted

--The 'ANDROID' screen appeared and I left it alone to do it's magic but I watched it closely

-- After about 10 mins or less, the 'ANDROID' symbol disappeared, the home key pad on the bottom of the phone lit up and it went to to setup.

--Immediately, errors started to pop up. I wrote them down as fast as I could. "Google service has stopped," "Clock has stopped," and there may be one more I missed.

--It went back to the "ANROID" screen.

--I waited, nothing. I waited more, nothing. It froze on the 'ANDROID' screen.

--I, finally, pulled the battery and rebooted and it wouldn't go past the 'ANDROID' screen.

Attempt #2

--Went through the same process of wiping my phone

--Flashed the ROMs again

--Rebooted

--This time it wouldn't even take me to the setup screen

--I pulled the battery a couple of times and got the same result

Attempt #3

--Wiped the phone again

--Flashed the ROMS

--This time I got to the setup page.

--Immediately, the errors started to popping up. "Framework process.media," "Google Service Framework" and a few others I missed since they disappear so fast.

--However, I was able to get to the set time page, which I clicked on.

--It went right back to the 'ANDROID' screen.

--I waited and waited. Nothing.

--I pulled the battery a few times and it wouldn't go past the 'ANDROID' screen again.

This same thing has happened on other ROMS. I even left it on over night (a different ROM) thinking it was loading and would take some time, only to find the load up page still doing it's thing 8 hours later.

What am I doing wrong? My phone was working fine before I rooted it. So, I think the equipment is fine. I just want something to work here. Any more suggestions?

John
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
i've posted about this several times before. i'll look them up and post them again. similar thing happened to me. need to reformat internal sdcard using non-virtual TWRP, then begin instructions in OP.

---------- Post added at 19:13 ---------- Previous post was at 19:06 ----------

see above. sure would be nice to clarify the OP instructions accordingly.
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
screenshots not working?

i see the animations of the shrinking shots of the screen, but i don't find any screenshots in gallery. that's where they should be, right?
[T-Mobile Samsung Galaxy S II SGH-T989] charmu:
Repartition or not repartition

Should I repartition my phone before flashing the lineage system. The installation method presented on the Lineage site does not recommend partitioning the phone.

Thank you all!
[T-Mobile Samsung Galaxy S II SGH-T989] daman261:
I normally find them in sdcard>Pictures>Screenshots using a File Manager
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
if you have repartitioned, revert the partitioning back to original. then see above about reformat sdcard to ext4 using non-virtual TWRP.

---------- Post added at 07:46 ---------- Previous post was at 07:43 ----------

if you haven't repartitioned, you still need to reformat sdcard as explained above.

---------- Post added at 08:17 ---------- Previous post was at 07:46 ----------

empty. is it only me? does it work for others? does my log give any clue?
[T-Mobile Samsung Galaxy S II SGH-T989] Easy_as_Pi_3.14:
Just to get it out of the way, it will not be on your real microSD card (/storage/xxxx-xxxx/), it is on the internal storage.

The full path is:

/storage/emulated/0/Pictures/Screenshots
[T-Mobile Samsung Galaxy S II SGH-T989] Milan Patel T989:
hi every one,

Can any one help me how to upgrade to lineageOS over CM 7.1.1 ? i have read the thread carefully but still bit confused what to do ? i would like a step by step guide if someone have. because this phone is my daily driver and i dont want to end up without phone. its highly appreciated if some one help me thanks...
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
if you use f2fs, and if you don't have the current recovery you'll need that, but i don't use f2fs so can't comment whether you'd need to reformat anything for that.

other than that, if you're already happily running 7.1.1, as bryan says, for now there's nothing special to do, just flash it.

---------- Post added at 13:09 ---------- Previous post was at 12:58 ----------

/# cd sdcard/Pictures/Screenshots
/storage/emulated/0/Pictures/Screenshots# ls -aFql
total 8
drw-rw---- 2 root sdcard_rw 4096 2017-01-22 08:07 ./
drwxrwx--x 3 root sdcard_rw 4096 2016-11-08 14:16 ../
/storage/emulated/0/Pictures/Screenshots#
[T-Mobile Samsung Galaxy S II SGH-T989] Easy_as_Pi_3.14:
Ok, so I decide to look at the log and it seems that com.android.gallery3d is throwing a FileNotFoundException saying (Permission denied).

01-21 18:39:48.132 18381 18431 W ImageCacheRequest: decode orig failed /local/image/item/383,1482353264,MICROTHUMB
01-21 18:39:48.147 18381 18433 W LocalImage: failed to find file to read thumbnail: /storage/emulated/0/Pictures/Screenshots/Screenshot_2016-11-08-14-16-01.png
01-21 18:39:48.155 18381 18433 W DecodeUtils:
01-21 18:39:48.155 18381 18433 W DecodeUtils: java.io.FileNotFoundException: /storage/emulated/0/Pictures/Screenshots/Screenshot_2016-11-08-14-16-01.png (Permission denied)
...

I just booted up my SR and took a screenshot. It said:

Saving screenshot…

Couldn't capture screenshot for a half second

Screenshot captured.

The screenshot came out.

Could you please reboot and just take a screenshot? There was a lot of logspamming from Firefox.

Speaking of spamming… my Skyrocket is finally catching up on its notifications. You've got mail! You've got mail! You've go—You've—Yo—You've got— …well more like bzztbzzt bzzbzztbzbzbzzbztzbzztzbztzzbztzbzt!
[T-Mobile Samsung Galaxy S II SGH-T989] nero50:
anybody able to record video?
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
ok, fresh boot, several screenshots, log attached, found a notification saying "Couldn't capture screenshot. Can't save screenshot due to limited storage space." jeez really? here's df:

# df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 417M 628K 416M 1% /dev
tmpfs 417M 0 417M 0% /mnt
/dev/block/mmcblk0p13 200M 22M 178M 11% /firmware
/dev/block/mmcblk0p17 200M 24M 176M 12% /firmware-mdm
/dev/block/mmcblk0p21 10M 4.2M 5.5M 44% /efs
/dev/block/mmcblk0p25 1.9G 756M 1.2G 38% /system
/dev/block/mmcblk0p28 11G 9.2G 1.7G 84% /data
/dev/block/mmcblk0p24 589M 10M 579M 2% /cache
tmpfs 417M 0 417M 0% /storage
/data/media 11G 9.2G 1.7G 84% /mnt/runtime/default/emulated
/data/media 11G 9.2G 1.7G 84% /storage/emulated
/data/media 11G 9.2G 1.7G 84% /mnt/runtime/read/emulated
/data/media 11G 9.2G 1.7G 84% /mnt/runtime/write/emulated
0#0#Jan23Mon14:06#@:/storage/emulated/0/Pictures/Screenshots#

i have doubts about the credibility of that notification. i note the following in the log:

*01-23 14:13:51.105 516 531 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1421 com.android.server.policy.GlobalActions.takeScreenshot:864 com.android.server.policy.GlobalActions.-wrap5:-1 com.android.server.policy.GlobalActions$ScreenshotAction.onPress:523 com.android.server.policy.GlobalActions.onClick:908
*01-23 14:13:51.129 516 531 I ActivityManager: Start proc 2151:com.android.systemui:screenshot/u0a29 for service com.android.systemui/.screenshot.TakeScreenshotService
*01-23 14:14:28.738 516 711 I ActivityManager: Killing 2151:com.android.systemui:screenshot/u0a29 (adj 906): empty #9
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
Root or not?

Question for you guys.

LineageOS by default now ships without root. A root package will be available soon which adds root access.

Since, I build on my own unofficially I can choose whether or not to include root.

So, would you guys prefer flashing root separately or have it baked in like it usually has?
[T-Mobile Samsung Galaxy S II SGH-T989] Seguraf13:
I would prefer root by default. Having it built into the dev settings has been nice for the small root applications i use. SuperSu has been said to have problems with f2fs which i use to make things a bit more snappy.
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
<shrug> if i can flash it, i'm happy either way
[T-Mobile Samsung Galaxy S II SGH-T989] Ludacrisvp:
Having it built in is nice, however with the number of apps that now have root detection it may be better to have it as a separate package or have an option to hide the root. With my FireTV which as built in supersu it is able to work with "hide my root" to move the su binary which bypasses directv now root detection.

So I'd vote for a way to hide root and keep it baked it (even if you just make it compatible with hide my root)

If not possible then it would make sense for it to be a twrp flashable package.
[T-Mobile Samsung Galaxy S II SGH-T989] nero50:
i would prefer to flash root separately
[T-Mobile Samsung Galaxy S II SGH-T989] daman261:
What's easier for you [MENTION=2107489]bryan2894[/MENTION] ? For us it's sometimes a necessity to flash a new root anyways pending what we're doing, but most things work with it baked in. I'm for either, but if one is easier for you, do it.
[T-Mobile Samsung Galaxy S II SGH-T989] osvaldo3091:
Integrated is better

Integrated is better
[T-Mobile Samsung Galaxy S II SGH-T989] Bcoates84:
I agree with built in root.
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
screenshots, hello?

hearing nobody else complain about screenshots, i wiped system, did factory reset, reflashed 20170111 alone (no gapps) (and booted, enabled developer options:power menu:screenshots, took screenshots, back to recovery, flashed pico gapps, booted again, installed jackpal terminal&hackers keyboard), tried more screenshots, captured a logcat, and attached it here.

in /storage/emulated/0/Pictures/Screenshots, ls -lA shows nothing, nada, zip, zilch. a notification says "Couldn't capture screenshot. Can't save screenshot due to limited storage space." here's df:

# df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 417M 624K 416M 1% /dev
tmpfs 417M 0 417M 0% /mnt
/dev/block/mmcblk0p13 200M 22M 178M 11% /firmware
/dev/block/mmcblk0p17 200M 24M 176M 12% /firmware-mdm
/dev/block/mmcblk0p21 10M 4.2M 5.5M 44% /efs
/dev/block/mmcblk0p25 1.9G 756M 1.2G 38% /system
/dev/block/mmcblk0p28 11G 8.0G 3.0G 73% /data
/dev/block/mmcblk0p24 589M 10M 579M 2% /cache
tmpfs 417M 0 417M 0% /storage
/data/media 11G 8.0G 3.0G 73% /mnt/runtime/default/emulated
/data/media 11G 8.0G 3.0G 73% /storage/emulated
/data/media 11G 8.0G 3.0G 73% /mnt/runtime/read/emulated
/data/media 11G 8.0G 3.0G 73% /mnt/runtime/write/emulated
#

in which partition is the storage space too limited?
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
here's that logcat
[T-Mobile Samsung Galaxy S II SGH-T989] Oluseun:
Please add root. Please solve the crashing problem in this next build.
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
Can you test the following? Open the file /system/build.prop and change the line:

ro.sys.sdcardfs=true

To:

ro.sys.sdcardfs=false

Reboot, then try taking screenshots again.

What's crashing?
[T-Mobile Samsung Galaxy S II SGH-T989] osvaldo3091:
Someone has problem with the camera's autofocus
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
RAW image support needs Camera2 API support. Our camera drivers are only compatible with the Camera1 API, so it won't work.

The issue with the cinema fv app should be fixed next release.
[T-Mobile Samsung Galaxy S II SGH-T989] Oluseun:
All apps are crashing after heavy usage. That is what I'm complaining about.
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
Are the apps force closing ("process has stopped")? If so, a logcat would help
[T-Mobile Samsung Galaxy S II SGH-T989] Oluseun:
Yes that is how it's happening.

---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------

I'm on cm13 now. I'm waiting for your new update on cm14
[T-Mobile Samsung Galaxy S II SGH-T989] ar_156:
Thanks for the development effort, but my T989 is working very weird since I installed 7.11:

1. Sometimes files can be accessed, sometimes not

2. Battery status shows more than 80%, jump to 40% after restart the phone, and sometimes it is 30% and suddenly goes battery off.

Do I have to do something to flash back to Paranoid 6x? or just factore restore and flash?
[T-Mobile Samsung Galaxy S II SGH-T989] SowahAkai:
Process Crashes and No SIM card errors All of a Sudden

Hi Bryan,

Thank you for your work and contributions to keeping the Skyrocket alive. I've been using your ROM since Celox 6.0. I have an unlocked, rooted AT&T Samsung galaxy S2 Skyrocket i727 running 7.1.1. I use a Claro SIM when I'm in the Dominican Republic and T-Mobile when I'm in the U.S.A. Right now I'm in the Dominican Republic.

I don't know what precipitated the errors I'm now getting. It may be a hardware problem; but, this is what started happening 3 days ago:

1.) On phone boot-up lock screen, I get: "com.android.phone has stopped" with or without SIM card inserted. I have the option to select: "Close app" or "Mute until device restarts". If I select "Close app", I can get access to the lock screen and swipe to the "Home" screen. But when I do, the "com.android.phone has stopped" error box appears again. I can press "Close app" for a 100+ times and it pops up each time I press it. So I have to select "Mute until device restarts" be able to get access to the "Home" screen.

2.) "No SIM card - emergency calls only" message on the status bar with SIM card inserted

3.) It takes a 30 seconds for "Settings" to open

4.) When I try to access "Networks" in "Settings", I get:

"Settings has stopped" and the option to select "Open app again" or "Mute until device restarts" Selecting the "Open app again opens "Settings".

Therefore, I can't make or receive calls or SMS texts. However, I can use WiFi to make VoIP calls and non-call related apps.

I've cleared the "Cache" and "CLEAR DATA" for Phone and SIM Toolkit.

I'm trying to avoid a Factory Reset because I'm concerned that I would mess up the backup process and lose my WhatsApp chat and text messages when restoring. (I'm legally blind and my phone and computer are my links to clients and co-workers here and worldwide.) If it's a SIM socket failure, a Factory Reset will not solve the problem. Is there a way to determine whether this is a SIM socket hardware or some other kind of hardware failure? Or is it possible that something broke in the OS?
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
I need logcat of the crashes or I won't be able to fix your issue.

This should be fixed next release.

For now flashing the file below should fix that issue:

https://www.androidfilehost.com/?fid=529152257862680626
[T-Mobile Samsung Galaxy S II SGH-T989] gregrwm:
[MENTION=2107489]bryan2894[/MENTION] thanks but sorry, that doesn't appear to have helped screenshots any, instead it appears to have partially removed permission to access storage, as you can see in the final ls below:

celox:/ # cd sdcard/Pictures/Screenshots/
celox:/sdcard/Pictures/Screenshots # ls -la
total 8
drw-rw---- 2 root sdcard_rw 4096 2017-01-27 08:18 .
drwxrwx--x 3 root sdcard_rw 4096 2016-11-08 14:16 ..
celox:/sdcard/Pictures/Screenshots # touch sd
celox:/sdcard/Pictures/Screenshots # touch /storage/emulated/0/Pictures/Screenshots/st
celox:/sdcard/Pictures/Screenshots # ls -la
total 8
drw-rw---- 2 root sdcard_rw 4096 2017-01-27 08:18 .
drwxrwx--x 3 root sdcard_rw 4096 2016-11-08 14:16 ..
-rw-rw---- 1 root sdcard_rw 0 2017-01-27 08:17 sd
-rw-rw---- 1 root sdcard_rw 0 2017-01-27 08:18 st
celox:/sdcard/Pictures/Screenshots # mount -o rw,remount /system
celox:/sdcard/Pictures/Screenshots # ls -l /system/build.prop build.prop
-rw-r--r-- 1 root root 4529 2008-12-31 23:00 /system/build.prop
-rw-rw---- 1 root sdcard_rw 4530 2017-01-30 04:24 build.prop
celox:/sdcard/Pictures/Screenshots # cp build.prop /system/build.prop
celox:/sdcard/Pictures/Screenshots # ls -l /system/build.prop
-rw-r--r-- 1 root root 4530 2017-01-30 04:27 /system/build.prop
celox:/sdcard/Pictures/Screenshots # reboot
packet_write_wait: Connection to 192.168.0.41 port 22: Broken pipe
255$90ux$Jan30Mon04:29$k@op755:0.0:/home/k$ ss9
Enter passphrase for key '/home/k/.ssh/id_rsa':
celox:/ $ su
celox:/ # cd sdcard/Pictures/Screenshots/
celox:/sdcard/Pictures/Screenshots # ls -la
ls: ./sd: Permission denied
ls: ./st: Permission denied
total 8
drw-rw---- 2 root sdcard_rw 4096 2017-01-27 08:18 .
drwxrwx--x 3 root sdcard_rw 4096 2016-11-08 14:16 ..
celox:/sdcard/Pictures/Screenshots #
[T-Mobile Samsung Galaxy S II SGH-T989] bryan2894:
Backup your Screenshots directory if there is anything in there then reboot into recovery. Then in TWRP, delete the Screenshots directory using the File Manager or from the terminal. Reboot and then try taking screenshots again