yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Lanchon:
is this bug in CM11 too or just CM12.1? i guess by CM11 i mean using one of my crossflash kernels because no official.
[AT&T Samsung Galaxy S II SGH-I777] pg1980:
CM11 works fine. This issue started with Lollipop.
[AT&T Samsung Galaxy S II SGH-I777] Lanchon:
i see. i don't have the device, can you test a CM12.1 kernel if i make one?
[AT&T Samsung Galaxy S II SGH-I777] Lanchon:
so i went ahead and made a try at it

please report

EDIT: changes here:

https://gist.github.com/Lanchon/094d9d93abd33f30d018
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
This kernel can be installed with the stock 12.1 kernel ?? And Which are the differences with the stock one ??Does this kernel fix the call issue ?
[AT&T Samsung Galaxy S II SGH-I777] Lanchon:
it's a kernel for CM 12.1.

i don't know!!! you tell me
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Thanks for developing for the I777. I am going to test this kernel to see if the call issue is fixed . But tell me is there any risk of hard brick by installing it or performing a factory reset in the recovery ?
[AT&T Samsung Galaxy S II SGH-I777] Lanchon:
thanks! no risk of bricking of any type.

but why a factory reset? if you are running CM 12.1 just flash this kernel on top and that's it, no wipe necessary.

what OS are you running?
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
This one 5.1.1 cm 12.1
[AT&T Samsung Galaxy S II SGH-I777] Lanchon:
so just flash the kernel and reboot, no wipes or anything.
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Ok

---------- Post added at 08:01 PM ---------- Previous post was at 07:13 PM ----------

The bug is istill present, and the cm is still stock I thought it would include the TWRP Recovery how I see in your thread
[AT&T Samsung Galaxy S II SGH-I777] Lanchon:
oh, still there, well thats too bad.

no, this kernel -and now official CM12.1 too!!!- suports IsoRec, which means you choose the recovery you want. go read the IsoRec thread (see my signature).
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Yikes, after seeing the mess going on in the i9100 CM13 thread, probably good we haven't switched over yet.

On a related note, when you switch over, [MENTION=6159291]Lysergic Acid[/MENTION], it might be a good idea to do a snapshot build of CM12.1 before so that people at least have a base to go back to if not happy (and it might save you a lot of grief if you could do on for the i9100 as well). Of course, people who don't know what they are doing shouldn't be riding the nightly train anyway...
[AT&T Samsung Galaxy S II SGH-I777] Lysergic Acid:
There probably won't be another snapshot of cm-12.1. They're actually planning a snapshot of cm-13 soon :)
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Well, that's good to know. I thought the maintainers could kind of push a snapshot whenever they wanted, since not every device gets a snapshot at the same time.

Oh well, we'll just have to download a CM12.1 image right before you turn us over to CM13. Thanks for all the ongoing work for this ancient yet capable device.
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
So, I went to use the GPS for the first real time since switching from Omni (not that I used it much there either). And it was pretty janky. It was slow to lock (slow as in a couple of minutes) and kept dropping lock every so often. Having it side by side with my Nexus 4 showed a very big difference.

Is there still problems with the gps.conf setup in CM, or is it just general GPS suckiness in the S2 family?
[AT&T Samsung Galaxy S II SGH-I777] tora67:
is there a "... Kitkat Compatible Recovery" for i777? I can't find it. I have phiz cwm 6.0.2.x. I believe a kitkat compatible recovery would be 6.0.4.x+
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Recoveries are built into the kernel for the i777 (or using IsoREC). So, if you have a kitkat+ kernel, you'll have a kitkat compatible recovery.
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Just noting that the 20160303 build now has TRIM enabled by default in the default kernel.
[AT&T Samsung Galaxy S II SGH-I777] tora67:
oh I failed to mention I currently have shostock3-v3.0.2 which has a JB kernel with an older CWM. I thought I would need a KK-compatible CWM in order to flash cm13-kernel then flash cm12-rom. should I just use use what I have and flash cm13-kernel, boot back into recovery then flash cm12-rom? or I should flash a KK-compatible kernel first?

thank you
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Hi again only install the KK-compatible kernel then reboot the recovery and install the rom cm12. Is not necessary install cm 13 kernel first . The ROM includes its own kernel.
[AT&T Samsung Galaxy S II SGH-I777] tora67:
how do you guys get TitaniumBackup to work? I believe I made the mistake answering "yes" to "fix root?" question.

Now even I flashed from CyanogenMod recovery the BETA-SuperSU-v2.68-20160228150503.zip (or UPDATE-SuperSU-v2.65-20151226141550.zip) su binary never got update. I had "apps and adb only" for root access set in {} developers options too.

what else could I do?

thank you
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Well, CM has root built in. That is what the "apps and adb only" setting in system settings is for. It has nothing to do with SuperSU. So, you probably have conflicting root methods setup.

And you'd be better off flashing from an IsoRec'ed TWRP than using the horrid CM Recovery. That could be part of the problem as well.
[AT&T Samsung Galaxy S II SGH-I777] tora67:
I reflashed CM nightly and all is well now. TB just warned that it works better with SuperSU. I personally prefer to use whatever come with the ROM to avoid adding more stuff.

if you guys flash the nightly once in a while, how do you deal with your apps? I move my apps to SDCard as much as possible, it starts to get a bit tedious if I flash the ROM often (nightly builds).
[AT&T Samsung Galaxy S II SGH-I777] radoo7701:
If you use the OTA updater then your apps won't be affected. I try to update once a week if my kids let me have it back.
[AT&T Samsung Galaxy S II SGH-I777] tora67:
So OTA updater won't affect the apps but flashing through recovery would?

it's amazing the old S2 can run lollipop. But I do realize I would need a newer smart phone to get on 4G network.
[AT&T Samsung Galaxy S II SGH-I777] radoo7701:
I'm guessing the OTA does the equivalent of a dirty flash and only wipes System, Cache, and Dalvik Cache. I'm not sure if it does the wipes automatically if you just flash in recovery, because I've never tried it that way.

My only real complaint about using the S2 versus the newer phones it the screen is dimmer and colors are not as rich.
[AT&T Samsung Galaxy S II SGH-I777] tora67:
I sometimes feels lucky that I am not that picky on the color. But then again, after I have seen LG's OLED 4K TV I was blown away.

Hey, I notice some issues with CM:

* Initially Data network does not exist, it seems to require wifi to download the network list because when wifi is off, data on, data does not get on any network.

* I have set "hide sensitive notifications on lock screen" but now notifications are not visible even when screen is unlocked.

* cast youtube to chromecast, the youtube control shows up on lock screen, but the controls do not work. pressing the "fast to end" behaves the same as close ("x")

---------- Post added at 07:29 PM ---------- Previous post was at 07:23 PM ----------

oh btw, there is no longer Dalvik Cache because lollipop uses a new runtime called ART. This is also why on the CM recovery there is no option to wipe Dalvik Cache.
[AT&T Samsung Galaxy S II SGH-I777] SamuEDL:
Are you going to realize one cm13 for i777? [MENTION=6159291]Lysergic Acid[/MENTION]
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Some one knows if the incoming call issues is fixed in the last nightly of this ROM ??
[AT&T Samsung Galaxy S II SGH-I777] yosmokinman:
^No it's not and I wouldn't expect a fix. It's not that bad unless you make a lot of calls. Then it would be annoying. Seems we don't have any i777 devs to look into it.

At this point with the i777 I'd take what we can get. Minus the callbug CM13 works as good as on the i9100.

So I'd also ++ the move to 13 for the i777 [MENTION=6159291]Lysergic Acid[/MENTION]

Lanchons repit is working as well for an easy way to repit to fit gapps.

Edit: Ohh you said incoming call, I don't know anything about that. I have no problem receiving calls. I was talking about the outgoing callbug.
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Yes, outgoing a mistake [emoji1]
[AT&T Samsung Galaxy S II SGH-I777] Lysergic Acid:
That call bug is annoying me too much, that's the main reason I'm not pushing it to CM13
[AT&T Samsung Galaxy S II SGH-I777] yosmokinman:
[MENTION=6159291]Lysergic Acid[/MENTION]

That's understandable, not going to the next version with the bug there. I think I said that at the beginning of this thread, seems we've flipped sides lol.

But.. I haven't seen any commits to fix it in the official 12.1 builds and they're going..

I guess none of those logcats posted had any good info. That sucks.

Oh well the i9100 roms and Lanchons crossflash work fine, until there's a kernel change that is.

Thanks for your work man. :good:
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Thanks Man for bring us this amazing ROM to our old I777 but loved device. It would be great see Android 6.0 on it.
[AT&T Samsung Galaxy S II SGH-I777] XDA_Mod:
Willingly to see the CM13 on our i777 soon it's a good update, dunno why it's on i9100 and not on i777.
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
Agree. It is the same bug for the current cm12.1. Since cm12.1 can be released, why not cm13.

Also, cm12.1 nightly/weekly has had build-failure since April 24.
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
I have faith that Lysergic will bring us CM13 for the i777
[AT&T Samsung Galaxy S II SGH-I777] yosmokinman:
One thing yall niggaz didn't do was call him with @. He ain't readin this **** otherwise.

Edit: **** it I'll do it [MENTION=6159291]Lysergic Acid[/MENTION]

I wouldn't fault him for not pushing it and imo it shouldn't have gone official 12 with that bug. But it did. So go 13.
[AT&T Samsung Galaxy S II SGH-I777] mmystere68:
The bug is easily fixed by replacing telecom.apk. i wonder why they dont include the modded telecom.apk directly into the rom. Also i sure hope we get cm13 too.... Just flashed cm13 on my nexus 7 2012 and its great so far....
[AT&T Samsung Galaxy S II SGH-I777] Lysergic Acid:
In theory, I should have dropped the device from the nightlies because of that bug, but since no one reported the bug officially I left it as is.

I'll start pushing some changes to the i777 to keep it at the same level as the i9100, and then try to sneak it in CM 13. No promises tho :)
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Thanks [emoji2]
[AT&T Samsung Galaxy S II SGH-I777] spacescreamer:
This msg gladdens me so much :)

With today's manufacturers

just not catering to reg sized device

, posts like these are priceless. Hope floats :angel:
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
Will this patch allow the weekly build of cm12.1 for i777 going through this weekend? [MENTION=6159291]Lysergic Acid[/MENTION]

Avoid accidentally using the host's native 'as' command.
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
No. All builds (cm13 and cm12.1) in cm jenkins succeeded today except i777 (http://jenkins.cyanogenmod.com/job/android/buildTimeTrend).

Looks like something went wrong at:

Docs droiddoc: /opt/jenkins/android/workspace/android/cm-12.1/out/target/common/docs/api-stubs

Error: inflate failed [invalid block type] at file offset [2535921]

imgdiff only supports gzip kernel compression, did you try CONFIG_KERNEL_LZO?

failed to break apart target image

make: *** [/opt/jenkins/android/workspace/android/cm-12.1/out/target/product/i777/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Error 1

make: *** Waiting for unfinished jobs....
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Yes, you can run the phone without a sim. You can still dial 911 as well. But you will have a big banner along the top that says "No Sim -- Emergency Calls only".

I just keep a nonactive sim in there to shut it up.
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Hey, can any of you wonderful, kind devs fix what's blocking the nightlies for the i777 for the past month? Or even flip the switch to CM13.1? :D;) (I know there's a concern about a calling bug, but if we already have it, might as well be on the newest everything else.)
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
CNBLACK has unofficial builds of cm12.1 and cm13. You will find his threads at "AT&T Samsung Galaxy S II Android Development" (one level up) . I am using his cm12.1 7-14-2016 build now. It works fine.
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
Thanks to whoever fixed the nightlies.
[AT&T Samsung Galaxy S II SGH-I777] XDA_Mod:
[MENTION=6159291]Lysergic Acid[/MENTION] are we having a way to...

1- have an stable 12.1 version for our i777?

2- or having in a very near future a nightly for CM 13?
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Great job, thanks so much for this! Works beautifully.

---------- Post added at 07:08 AM ---------- Previous post was at 07:03 AM ----------

This version is actually QUITE stable my friend. Or atleast IMO it is. I also flashed Lanechon 's Trim Kernel and I'm using that with this. You can find that hereif you're interested. I also use Mini OpenGapps package found here But you may need pico not sure, I've already repartitioned my /system /data and /preload partitions to be larger. If you need help with that I'd be glad to post exactly what I did to achieve that.

**Edit** I forgot to mention, there's a very easy way to fix the outgoing call bug and I just wanted to make everyone aware of it, IF you didn't know. I'm assuming by now most do, but in case not, here is what I do when I flash. Download this file here to your phone. On your phone go to settings-->developer options--->root and grant apps only root access. Using the stock File Manger built into the ROM, grant it root access and then go to the file you just downloaded and rename it Telecom.apk. Change the permissions of the file to 644, or Read/Write for user and Read for the other two lines. So it would look like Read/Write on one line, Read on the next two lines. Copy the apk file so we can paste it somewhere else. Go to /system/priv-app/telecom and delete the telecom.apk file, then paste in the downloaded version. Now restart the phone and be amazed at outgoing calls working. If you need any help with this it's actually much easier than it sounds trust me.
[AT&T Samsung Galaxy S II SGH-I777] Tmobilefan906:
Call fixed?
[AT&T Samsung Galaxy S II SGH-I777] Tmobilefan906:
Which recovery. Cwm 6.02 doesn't work.
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Here you can find the recovery

http://galaxys2root.com/cwmtwrp-recovery/
[AT&T Samsung Galaxy S II SGH-I777] Tmobilefan906:
Yes I knew this one...lol I wanted twrp
[AT&T Samsung Galaxy S II SGH-I777] Tmobilefan906:
OK. Got it partitioned. I have a i777 device...but when I flash cm 12 i777.zip, it returns with an error saying I have gti900.. can I flash roms from gti900 threads? Thanks.
[AT&T Samsung Galaxy S II SGH-I777] AnotherFreakinNoob:
The call bug isn't that big of an issue for me. Just created a profile in Tasker to toggle speaker on, wait 500 MS, turn speaker off. Probably the easiest profile I've ever executed.

ETA: Found what I was looking for. Thanks for the ROM.
[AT&T Samsung Galaxy S II SGH-I777] kulldox:
Hi, Is there any mirror of the last build? The cyanogenmod.org website is no-longer available.
[AT&T Samsung Galaxy S II SGH-I777] TeutonJon78:
I'm uploading the 20161031 (which I think was the last one) and 20161002 builds.

https://mega.nz/#F!ZRs2jZgI!QgEG-NBj8g1SI2hzUODpUg
[AT&T Samsung Galaxy S II SGH-I777] kulldox:
OK, cool. thanks. appreciate it.
[AT&T Samsung Galaxy S II SGH-I777] userwaldo:
Wrong Thread.
[AT&T Samsung Galaxy S II SGH-I777] syarif agil:
sir why i after install this rom twrp or cwm i lost
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
It is because the kernel and the recovery are in the same partition In the Galaxy s2
[AT&T Samsung Galaxy S II SGH-I777] pepe100:
Thanks for the link this rom keep my galaxy S2 live, the battery is great and is super stable. Thanks Dev for this Rom.
[Galaxy Tab S Q&A, Help & Troubleshooting] molitar:
Brand new S only day old and it will be charging than the screen will turn on to a greenish gradient screen as if a screensaver turned itself on. Took me a while to figure out where to turn off the default screensaver app but now I am getting this weird behavior. Any know reason or how to fix?
[Galaxy Tab S Q&A, Help & Troubleshooting] ashyx:
Pics? Probably faulty.
[Galaxy Tab S Q&A, Help & Troubleshooting] Tinderbox (UK):
I would do a reset from the settings menu, if you still have problems straight after that your tablet is faulty and you should return it.

John.
[Galaxy Tab S Q&A, Help & Troubleshooting] alialexali:
check this one

http://xdaforums.com/galaxy-tab-s/help/screen-flashes-device-reboots-smt705-t3128391
[Galaxy Tab S Q&A, Help & Troubleshooting] Tinderbox (UK):
His tablet is only a day old, I suppose he has not flashed it, I would return it and get a refund or replacement, I would not mess about with it.

John.
[Android Apps and Games] lenover9000:
I remember playing a game with samurais, mainly in black and white. It was a Japanese game called Iai something (cannot remember the whole name, that is the problem). It was like a reflex game, I played double player with my friend. The game starts with two samurais approaching each other, and their respective players should touch the screen at the right time to land a hit on the opposite player. Anyone recognize this game ?

Thanks.
[Sprint LG G2] Abu Nazir:
Hello. I have been having major problems with my touchscreen as far as a dead spot up top and whenever i hit the home button it automatically activates the button right beside it at the same time. So by hitting the home button it actually presses two buttons at the same time. Hope that makes sense. Anyway i remember reading somewhere awhile ago about being able to update touchscreen firmware and i was wondering if anyone knows how or if i can do this. I tried looking but not having much luck. Im on the latest ZVG stock. LS980 sprint. Thanks for any help u could give.
[Sprint LG G2] mac01843:
Same problem here; the Sprint store tech told me that it "sometimes happens", although I've NEVER seen, nor heard of a phone, less than two years old, having such a problem. Sprint tech suggested I have it fixed, for $75. Insurance or not, it will still cost the same (deductible). Cheapest option: If you've got the expertise and patience; buy a new digitizer on ebay, for about $8, and replace it... next option, buy a new phone, and sell the defective, disclosing the touch screen digitizer issue.
[Sprint LG G2] galets:
Digitizer is more like 40 bucks
[P3600 Software Upgrading] freakdahouse:
Hello, I was playing arround changing skins (dialpad, comm manager), and when I restored to default again, I noticed that I was stuck with this comm manager:

Can anyone host the original files?

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] Zephilinox:
I wanted to completely reformat my phone as my phone was buggy with Cyanogen Mod 12, so I formated everything.

The problem is that my PC was not detecting the drivers when in recovery mode, so I couldn't side-load with ADB, and I have no way of getting a .zip on to it.

I tried re-installing the clockwork mod using ODIN but it would just crash the application. I then tried heimdall and that said it installed it (I was hoping that it would fix adb)

Now I can't boot in to the clockwork mode recovery as it just instantly turns the phone off, however I can just boot normally in to the Galaxy S4 logo screen.

When I'm in the logo screen I do have access to ADB, however my phone is unathorised and I have no way to authorise it.

How can I A) fix clockwork recovery so it works again and B) put a zip on the phone or fix ADB detecting my device in recovery?
[Galaxy S 4 Q&A, Help & Troubleshooting] DSA:
If you can get into download mode, flash a full stock ROM via Odin and start again
[Galaxy S 4 Q&A, Help & Troubleshooting] Zephilinox:
That worked great, thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] DSA:
no probs, i find it to be a pretty good fall back in case of issues (just annoying reinstalling games etc..)
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ykjae:
Is it possible to flash xposed to my phone with FlashFire?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ldeveraux:
How about going to the xposed forum specifically the Samsung section. There's an 800 page thread that will answer your question
[Android Q&A, Help & Troubleshooting] robinchvers:
Hi! This is my first post here on xda, I wanted to know if there's an option to customize my nav bar with only two icons, I thought of asking here 'cause its been long time checking all your threads and learning from them, you are an excellent comunity!

Anyhow... As I said I wanted to know if there is a way to just put in the nav bar the "back" button (keeping its same function) and "recents" button so when I press it it shows the recent apss and when I long-press it it takes me straight to home (or the other way round, doesn't matter).

I also wanted the back button to look like an arrow (like the one of the picture i attach, similar to the windows phone ones) and the recents button to look like the normal square in the android lollipop stock version.

I've got a Nexus 6 runnig CM12.1 and even though I installed it myself, my "dev-skills" aren't great.
[Android Q&A, Help & Troubleshooting] Durion:
Hello! I currently have a rooted Alcatel One Touch Fierce 2 that is running on stock recovery and stock ROM, android version is 4.4.2 and kernel version is 3.4.0-gbadcb71 and build number is C2CUMC3. It has a Qualcomm processor and I have managed to pull the stock recovery and boot images with flashify, the bootloader is also locked. I tried to use the cwm recovery builder, but that appears to be offline. Any recovery would work CWM/TWRP/PHILz/etc. I tried looking if there were guides that I could find and sadly they were all about MTK devices. Any help would be appreciated.

Stock Recovery

Boot Image
[Android Q&A, Help & Troubleshooting] ferid_bha:
hello

Envoyé de mon S330 en utilisant Tapatalk
[Android Q&A, Help & Troubleshooting] mrjabol61:
We need more informations:

run: "cat /proc/mtd" in terminal emulator or adb shell and put here the results

run: "cat /proc/emmc" the same as above

put exact CPU model, i.e. msm8226

put GPU model, i.e. Adreno 305/306
[Android Q&A, Help & Troubleshooting] QA Bot:
Q&A for [Tutorial] How to make Second Partition on SD-Card of ext3

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Tutorial] How to make Second Partition on SD-Card of ext3. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Android Q&A, Help & Troubleshooting] Android R Us:
I'm getting the same issue. I'm on lollipop using a note 3 rooted.

I've tried ext3 and ext4.

Any other info needed please ask.
[Android Q&A, Help & Troubleshooting] arckingpin:
try ext2 if it still dsnt work...fat32 will work for sure
[Android Q&A, Help & Troubleshooting] CollisionFactor:
Do you have to have a rooted device in order to partition and use your SD card?