yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] Tiger Shark:
I'm one of those that really needs the slider keyboard, so this is the phone I'm considering. I'm also on AT&T with grandfathered voice and data plans and don't want to mess things up getting a phone from them.

My current phone is an LG Expo. It's Windows Mobile 6.5, stock ROM and just some tweaks. I went with WinMo because of the seamless integration with my work contacts and calendar. Employer does not allow use of cloud to sync these. I understand there is the Kies app that allows you to directly sync these (though I also have seen that many have trouble with it). I really, really need pop-up reminders of my appointments.

I don't use my phone for games, I don't tweet or facebook, and I don't listen to music or watch videos on it

. I do text a lot, Google, Wikipedia, check sports scores, occasionally use the camera or video, and , of course, make calls. I do occasionally need to sneak in some tethering via WiFi (for which I plan t use PDANet/FoxFi). So, I'm not very demanding. If my eXpo would do better on web sites, I'd probably just stick with it. But even the "mobile" sites have so many graphics these days that they often won't load completely on my phone.

After Microsoft left us WinMo 6.5 users high and dry, taking down the apps store well before it's time, I swore I's never get another Windows phone. No removable battery kills the iPhone. So, Android it is.

With new phones going for around $160 on eBay and the ICS upgrade available (stock AT&T or a few here), this seems the right phone to move to Android. I'm not sure I'm going to like a phone that's an inch longer and half an inch wider, but that seems to be the only real choice these days.

I know a lot of folks here are into getting the most from their phones with the hottest new ROM, but I think there might also be some less experimental that can help me determine if I'm making a good choice.
[Samsung Captivate Glide] Gab1288:
Well, its been out for quite a while now. Not that its outdated, it is still fast and usable. But the ROMS for it are quite limited, i suggest you stay with stock ICS if you dont want any trouble, but you will lack some features.

Other that that, i still have that phone, using it everyday, still working good, the battery died so i bought a new one (extended). The keyboard and mechanism is still working fine with no sign of it breaking soon.

The tegra 2 chipset is fast enough for any apps to run at a decent speed on it.

The only thing i hate about that phone is the wake-up bug, in a hurry, it can be frustrating that the phone doesnt turn on at the exact moment that i press the button (it normally takes 1-2, even 3 seconds to turn on the screen).

I would recommend it since its gone quite cheap and its been reliable for me.
[Samsung Captivate Glide] rad30n:
I bought mine new very recently (2 months) from a seller on amazon, and I haven't been disappointed.

I also love slider qwerty, so the combination of specs and price sealed the deal. Unlike Gab1288 I can't say I recommend the stock ICS rom, it was unstable for me -- I had multiple freezes per day in the 3 days I used it right after I bought the phone.

I've been using spyke555's CM10.1.0 RC2 rom and never been happier with an Android rom. I can't get gps to work right with Sygic maps, which is a bummer, but apart from that, I highly recommend this phone and this rom.

Since I've gotten it, and learning how much I paid for it, I've had two people ask me to buy them one when I visit the US again.
[Samsung Captivate Glide] Nowaker:
This is my 3rd Captivate Glide in the row. The first had a damaged physical keyboard - the "s" key was very so hard to press that it caused me a pain. The second one had a damaged microphone - sometimes people could barely hear me. After being hit, it worked for a moment. The third phone finally works. So I'm not happy with I927 in terms of the overall quality. But I enjoy the working phone, 512MB RAM in my previous phone (HTC Desire Z / Vision) was not enough. Thus it was extremely slow and unresponsive. 1 GB RAM is not that much but unfortunately there is no 2 GB phone with a physical keyboard on the market. There's also Motorola Photon Q which I would probably prefer better, but I couldn't find a way to get it imported to my country.

EDIT: The third does not work either. After some time IMEI disappears as if there was no /efs. To get it back I need to reconnect the battery...
[Verizon Samsung Galaxy S 4] Euroskank:
Download: http://fitsnugly.euroskank.com/?rom=cm12&device=jfltevzw

Cherry pick list

* CyanogenMod's latest merges: http://review.cyanogenmod.org/#/q/status:merged+branch:cm-12.1,n,z

* CyanogenMod's Github: http://github.com/cyanogenmod

This is a kang of CM12 with cherry picks from CyanogenMod’s Gerrit Instance, compiled by a group of volunteers that enjoy learning about building CyanogenMod & Android in general. All credit goes to cyanogen, #teamdouche and the coders who submit to Gerrit. Thank you to @RyanMacG for providing Euroskank hosting.

These builds are bleeding-edge, most comparable to a nightly build, and are not meant for inexperienced users. Things will be broken and crash from time to time, you need to accept that this isn't stable by any means before flashing. Nandroid as often as possible.

How to post useful, informative bug reports:

Sometimes dev's actually check out our threads, or sometimes we have a good relationship with a dev or two. These bleeding-edge builds will have issues, and having good information on what's broken is great feedback before a feature is merged. Here are some good bug reporting tips:

* No bug reports while using custom kernels or add-ons:

CyangenMod's own bug reporting tool does not accept bug reports from people using non-stock kernels for a reason, so why should we? CM can merge changes to their kernel causing custom kernels to break things until they catch up. Therefore, please do not post any bug reports while using a custom kernel or add-on such as Xposed Framework. Post your issues with custom kernels in their own respective threads as they are the ones who need to play catch up. Any bug report posted in this thread should be while running CM's stock framework and kernel, as this prevents unnecessary clutter.

* Gapps are not a CM issue:

CyanogenMod is built to run without the assistance of Google's proprietary apps (gapps). Having issues with your Google account and syncing is a gapps issue, not a CM issue. Please do not post about any gapps related issues, just wipe data and try a different gapps package.

* Posting about the same bug every build:

Beating a dead horse with "bug X still isn't fixed" posts just adds unnecessary clutter and provides no help into actually fixing the issue. Some bugs take days to squash, some take weeks. Please don't report the same bug every time a build is uploaded.

* Logs:

Provide logcats when applicable. Use a service like Pastebin and put a link to the log in the post. Please do not post logs directly to the forum.

If these requests are too demanding, there's good news! CyanogenMod is open source, so please feel free to download the source code, compile your own builds volunteering your time and resources, then start a thread and run it however you see fit. All we simply ask is that people post good, reliable information that can be passed on to a developer that can actually do something with it, making CM a better product for everyone involved.

ROMManager ----- GooManager ----- Lollerpop RSS Feed​
[Verizon Samsung Galaxy S 4] Cruiserdude:
Awesome, thanks Euroskank, your builds are always the best for me of all the versions, even official nightlies!
[Verizon Samsung Galaxy S 4] 17akota:
Trying this out right now!
[Verizon Samsung Galaxy S 4] juanzho11:
Nice. Dling.
[Verizon Samsung Galaxy S 4] kvirus11:
Smooth! Man I miss Skank from my GNex days!

This is magically delicious!
[Verizon Samsung Galaxy S 4] SellswordShev:
Any gapps zip you recommend or just use the ones in this thread? http://xdaforums.com/showthread.php?t=2384470
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Gonna flash this when I get home, thanks.

Sent from my Time Machine
[Verizon Samsung Galaxy S 4] docnok63:
Bugs to report:

1) Focal FC's with every pic taken and the image is completely blank and black in the Gallery.

2) There's two DeskClock apks causing the error message when you first boot. I deleted the smaller one out of system\app to fix it.
[Verizon Samsung Galaxy S 4] ruben8448:
Is there a way to enable notifications to always expand?
[Verizon Samsung Galaxy S 4] dadoc04:
Nice!! dl'ing and flashing soon as i get home
[Verizon Samsung Galaxy S 4] GreenXSniper:
Does this have the IR Remote functionallity added like invisiblek's unnoficial nightlys?
[Verizon Samsung Galaxy S 4] ahatzz11:
Is this just cm, or are there other roms code merged into the build? Is it different than the other cm unofficial nightlies?
[Verizon Samsung Galaxy S 4] Pixelation:
Nice! I run this on my Fascinate, great ROM, great support.

Makelegs?!?!?
[Verizon Samsung Galaxy S 4] Dubbsy:
Yeah my ir remote works
[Verizon Samsung Galaxy S 4] reinert012:
Backing up and flashing now...
[Verizon Samsung Galaxy S 4] GreenXSniper:
Can you let me know if the ir remote works? if you use it.
[Verizon Samsung Galaxy S 4] reinert012:
I don't use it...sorry man. If you can tell me how to test it, I will. I'm not familiar with it.
[Verizon Samsung Galaxy S 4] GreenXSniper:
Ahh ok it seems the poster above you has confirmed it works. Guess i'll be flashing this tonight. Thanks guys :D
[Verizon Samsung Galaxy S 4] reinert012:
For ****s and funnsies...how do I test it?
[Verizon Samsung Galaxy S 4] HowardZ:
I can not get IR to work.

How did you do it?
[Verizon Samsung Galaxy S 4] dlongb13:
8/6 build has BT data on my '13 Subaru. Everything is running awesome besides focal.
[Verizon Samsung Galaxy S 4] Jeremiah_1988:
Ir?
[Verizon Samsung Galaxy S 4] dlongb13:
No IR from my testing. I don't use it so no biggy to me.
[Verizon Samsung Galaxy S 4] rustynutzz:
Working for me on build 8/5. Smart IR remote app.
[Verizon Samsung Galaxy S 4] ITGuy11:
I should have mentioned that this was with Google Music that avrcp didn't work.
[Verizon Samsung Galaxy S 4] kdogg78:
I so want to daily drive this but the dialer and BT are killing me.. going to try the 8/5 build as stated back a page or two.

Other than that I stoked to have this ROM :good::good::good:
[Verizon Samsung Galaxy S 4] dadoc04:
8/8 build is up.....
[Verizon Samsung Galaxy S 4] chad24taylor:
Anyone having graphical glitches on today's build? EX: artifacts when swiping/scrolling.
[Verizon Samsung Galaxy S 4] rustynutzz:
Negative. I am however using Nova Launcher and not stock.
[Verizon Samsung Galaxy S 4] chad24taylor:
Ahh, apparently this build doesn't like Chronic kernel. All good now.
[Verizon Samsung Galaxy S 4] rustynutzz:
Everything seems to be running good on today's build except BT. It works, just a little wonky when trying to answer calls.
[Verizon Samsung Galaxy S 4] Seano.:
same thing is happening with the ktoon kernel. they will need to update them.
[Verizon Samsung Galaxy S 4] Elvis_Marmaduke:
Is 4.3 aosp photosphere working yet?
[Verizon Samsung Galaxy S 4] rustynutzz:
Yes. Not baked in yet though. Have to flash it separately.
[Verizon Samsung Galaxy S 4] Elvis_Marmaduke:
Awesome thanks, that's the only reason I flashed back to 4.2.2 :)
[Verizon Samsung Galaxy S 4] reinert012:
I'm still not able to get Titanium Backup to work, it just sits at 0%. I have checked and unchecked verify apps to no avail and enabled SU. Any idears fellas?

EDIT: Updated superSU (previously was downloading superuser) and is now working great.
[Verizon Samsung Galaxy S 4] e46ci:
has anyone tried this ROM w/the s-view smart cover?

I'm currently running another version of 10.2 that doesn't have the s-view functionality and I'm curious if it make cents to switch to this version. If not, i minus whale stay w/my current ROM.

TIA
[Verizon Samsung Galaxy S 4] norman1080:
Where is this flashable 4.3 photosphere you speak of?

Thanks in advance!
[Verizon Samsung Galaxy S 4] loldi:
Anyone elses WiFi not working? Mine won't switch on. Using newest ktoonz kernel
[Verizon Samsung Galaxy S 4] reinert012:
This I would also like to know.
[Verizon Samsung Galaxy S 4] gonzlobo:
So both the 1/13 & 1/14 build have the same issue with Google Play and Hangouts FCing. Back to my 1/12 nandroid.
[Verizon Samsung Galaxy S 4] stoicwood:
Installing 1/14 now, but I have not seen an FC from anything in days. I used 1/13 for about 20 hours.

Edit: I did notice the pulsing LED on boot is missing this time (paying attention). Stock kernel, gapps from http://fitsnugly.euroskank.com/?rom=cm12&device=gapps
[Verizon Samsung Galaxy S 4] Alarbus:
The system partition size fix is not yet merged. Also, they did remove the pulsing light on boot, because it's inconsistent and can stay on until you screw around with notifications to get it to finally shut off. Not that I'm irritable about it or anything. I swear.

(So happy it's gone)

Edit: partition fix merged a few minutes ago. Next build should be in good shape.
[Verizon Samsung Galaxy S 4] .Ejekt:
It really seems like all of my stability issues root from KT's kernel. The past few nightlies I've flashed only the ROM and tested stuff, then once I've confirmed everything is functioning I flash the kernel. WiFi/BT start to get inconsistent, random FCs, etc. Looks like I need to find a stable combination of ROM/Kernel or just abandon KT's work all together. Unfortunate.
[Verizon Samsung Galaxy S 4] stoicwood:
Does anyone else use the on-screen nav bar (Settings > Buttons > Enable on-screen nav bar)? It looks like 1/14 broke them, so my run of no FC ended with a System UI FC any time a button is pressed. Disabling this option, the hardware keys work fine.
[Verizon Samsung Galaxy S 4] nanodan:
Have you tried redownloading the kernel zip? Maybe something goofed up during download.

Also, can you share your KT profile? I use Undisputed 3 profile and script (under balanced), no issues. It's very possible that KT's source is now just too out of date and he needs to bring it up. If this is the case my phone will start exploding too. Time will tell.
[Verizon Samsung Galaxy S 4] Silentgray:
Does anyone else have the issue when running daydream the the screen turns off when touched instead of waking up?
[Verizon Samsung Galaxy S 4] Vaporsilver:
All the time.

Everyone else able to write to the SD?
[Verizon Samsung Galaxy S 4] nanodan:
Yup.
[Verizon Samsung Galaxy S 4] FernBch:
I have been having some very strange behavior today (running 1/11).

First was the phone started acting up. I had signal but couldn't place a call. Kept getting a message saying cellular network not available. A reboot fixed it.

Group messaging and MMS was being weird. If I receive a group message AND have a separate message from a recipient contained in the group message the group message will stay marked as unread until I delete any separate messages from the list. If this happens and I receive any MMS I cannot download or view them until the group message issue is cleared (deleted).

Earlier I was viewing posts on G+ and had severe lag when selecting a message on the notification list to actually viewing the message.

Also, there is this annoying bar right above the keyboard with an exclamation point, question mark, comma, colon, and semicolon in it. If you touch one of them it will delete a whole and/or part of one or more words. How the #$*@ do you turn it off. This alone is enough to make me want to get off this build.

---------- Post added at 11:17 PM ---------- Previous post was at 10:59 PM ----------

Edit:

Having a bunch of random momentary freezing of the display/UI/whatever as well.
[Verizon Samsung Galaxy S 4] gonzlobo:
yes
[Verizon Samsung Galaxy S 4] Vaporsilver:
I cannot figure out why I can't write to my SD. It baffles me.
[Verizon Samsung Galaxy S 4] .Ejekt:
Sounds like you need to do a fresh install. This happens to me every couple of weeks - not the same problems exactly, but a loss of stability definitely.
[Verizon Samsung Galaxy S 4] gonzlobo:
Third straight build with Google play and hangout FCs. I'll restore and do a thorough investigation this weekend.
[Verizon Samsung Galaxy S 4] .Ejekt:
Flashed 1/15 over 1/11 today. System UI FC loop. Yay! Back to 1/11 *sigh*

Do y'all wipe anything in between flashes? Typically I do dalvik/cache, but if that's not really necessary I'll start skipping it.
[Verizon Samsung Galaxy S 4] stoicwood:
I don't wipe anything or flash anything beyond the ROM unless I am doing a clean install. I'll try 1/15 in a bit. Do you use the on-screen nav buttons?
[Verizon Samsung Galaxy S 4] nanodan:
Cache gets wiped by the CM12 install script.

Have you tried my build?
[Verizon Samsung Galaxy S 4] stoicwood:
The only way I get a System UI FC is if I have the software nav buttons enabled and try to use them. With them off, I haven't gotten any on 1/14 or 1/15.
[Verizon Samsung Galaxy S 4] .Ejekt:
Oh, that's good to know!

No, I have not.

No, I do not. I'm thinking it might be a compatibility issue with the PA Gapps package that I use.
[Verizon Samsung Galaxy S 4] gonzlobo:
I don't recall which gapps I installed, but I know they were from the cm page's recommended, plus I use a really minimal gapps. Not sure why I use them as I freeze most unused apps.
[Verizon Samsung Galaxy S 4] nanodan:
Do you use these?

I run the stock PA package, but that's preference. Not many people report having issues with any of the packages. Give them a shot, if you currently use GApps from elsewhere.

Problems can quickly arise from an out of date Play Services module. If every other GApp is updated and PS isn't, often times it'll goof up everything including the Play Store so you can't even update Play Services. I had a problem with this a few months ago; I used an out of date GApps package on a clean flash - Everything started complaining to update Play Services, but the Play Store wouldn't even work. Pretty soon everything was force closing.
[Verizon Samsung Galaxy S 4] 760hacker:
I use PA gapps with zero issues
[Verizon Samsung Galaxy S 4] .Ejekt:
That I do. I use the Google stock package. I'll redownload the latest and see if it fixes things.
[Verizon Samsung Galaxy S 4] nanodan:
If you still have problems, play around with KTweaker, in particular your CPU's clock speed. My phone is an oddball and will spectacularly explode if I clock the CPU above 2106 MHz. Every phone is different, and your phone might not agree with whichever clock speed you have set for it, if it's overclocked.
[Verizon Samsung Galaxy S 4] gonzlobo:
[MENTION=2419035]fitsnugly[/MENTION] says we get themes tomorrow (my interpretation).
[Verizon Samsung Galaxy S 4] nanodan:
The code is being tested, Euro will probably pick them. But I doubt it'll be a stable build.
[Verizon Samsung Galaxy S 4] fitsnugly:
1) it got merged. 2) stop spamming your builds in my thread, it's rude, start your own thread if you want to post builds.
[Verizon Samsung Galaxy S 4] nanodan:
Alright, by your request. It was hardly spamming, but /shrug. The dude was having problems with yours, I was trying to help him out and offered an alternative. I was in no way trying to be rude. Oh well.

Glad the code got merged, didn't know it was that far along.

Good luck .ejekt, maybe fitsnugly will help you out.

If anyone wants to try mine, feel free to PM me.
[Verizon Samsung Galaxy S 4] brasewel:
Just flashed 1/15 and getting the System.UI infinite loop error *sigh*. I did use the latest PA Gapps. I'm going to try the Gapps from CM to see if that might resolve this.
[Verizon Samsung Galaxy S 4] Loop4zil:
What recovery are you using? I had trouble with CWM. Switched to the latest TWRP... No more issues with FCs.
[Verizon Samsung Galaxy S 4] mcconvict:
Tried 1/16. Constant systemui fc. Anyone else?
[Verizon Samsung Galaxy S 4] brasewel:
TWRP 2.8.1 . It looks like 1/16 also has this issue. 1/11 and below were fine

EDIT: I'll update twrp to 2.8.4 and see if that makes any difference
[Verizon Samsung Galaxy S 4] mcconvict:
I'm on 2.8.4...I think the themes are conflicting with something
[Verizon Samsung Galaxy S 4] brasewel:
You might be right. I had to go back to 1/11 unfortunately :(
[Verizon Samsung Galaxy S 4] gonzlobo:
I had the same issue with builds newer than 1/12. I factory wiped and started over. Everything's fine.
[Verizon Samsung Galaxy S 4] FernBch:
I have the feeling the 1/16 build is hosed across the board. None of the official nightlies built successfully either.
[Verizon Samsung Galaxy S 4] stoicwood:
Installed 1/16 dirty. Nav buttons no longer cause System.UI FC. No issues I can see so far.

TWRP 2.7.1.0

GAPPS from the same place as the rom.
[Verizon Samsung Galaxy S 4] crossen0:
I'm still on 1/11. Did 1/15 work for anyone? Or should I just stay where I am?
[Verizon Samsung Galaxy S 4] stoicwood:
I'm not sure where the crashes are coming from for everyone else, but the only issues I had with 1/14 and 1/15 were System.UI crashes on the software nav buttons and an infrequent Bluetooth share crash when connected to my OBDII in my car. The System.UI crashes could be bypassed by turning the software buttons off. Now, with 1/16, I see no crashes, but I have not tried BT.
[Verizon Samsung Galaxy S 4] crossen0:
No crashes on 1/16 either but I haven't had the chance to try BT yet.
[Verizon Samsung Galaxy S 4] mcconvict:
You guys without fc's ...are you on dirty flashes?
[Verizon Samsung Galaxy S 4] crossen0:
Yes I was. But I had some serious sporadic lag when using apps and then a text message wouldn't send so I gave up and restored 1/11.
[Verizon Samsung Galaxy S 4] FernBch:
I was having some serious lag within apps, an occasional FC of com.process.android.phone, and a random reboot on 1/15. I clean flashed it and most has been pretty good since. The only issue I have had was an occasional non-auto connect of WiFi after extended periods of deep sleep. I have two saved WiFi networks and it happens to both. Cycling WiFi off/on and all is good.
[Verizon Samsung Galaxy S 4] crossen0:
I dirtied today's build over 1/11 and I haven't noticed any lag yet. Been only a little while so I'll keep messing around with my phone to see if I can reproduce any. Fingers crossed!
[Verizon Samsung Galaxy S 4] mcconvict:
I worked thru the systemui FC's. It was only thru the setup. The last screen said your tablet is ready for use...maybe that's the ui problem. But installed the first cm12 theme! Works great!
[Verizon Samsung Galaxy S 4] crossen0:
What theme? I can't find any!
[Verizon Samsung Galaxy S 4] mcconvict:
https://plus.google.com/101536628079394146024/posts/6uKA7X56Zio

As far as I know, its the first available
[Verizon Samsung Galaxy S 4] Loop4zil:
Experiencing system ui crashes on the 1/17 build too. I'm not patient enough to work thru them.

Check that...

I powered thru the setup screen... And all is well
[Verizon Samsung Galaxy S 4] mcconvict:
Expanded desktop the day after the theme engine...amazing!
[Verizon Samsung Galaxy S 4] Alxoom33:
1/17 build working great for me with PA Stock gapps package 1/17 version.
[Verizon Samsung Galaxy S 4] .Ejekt:
Flashed 1/19 over 1/11. System UI FC loop. Returning to 1/11.
[Verizon Samsung Galaxy S 4] stoicwood:
I've had some lag with some recent nightlies, but I wouldn't say serious with my normal use. Normally it seems like it is slow to come out of deep sleep. I haven't noticed it in the last 2-3 nightlies I have tried. No issues texting, but I use Hangouts more often.

FernBch, are you leaving WiFi on always or turning it off while asleep? I played with leaving it off while asleep and had this issue for a while, but never while always on if I leave an area and come back. I haven't noticed any random reboots or phone crashes.

I still haven't had any FC loops. I dirty flashed 1/19 earlier, and while I haven't used it much since, I have seen no issues. I have been dirty flashing for weeks now, and I have never seen an issue bad enough to go back. So other than no jumps in flashing, I can't imagine what would be different.

FYI: TWRP 2.7.1.0, gapps from fitsnuggly, stock kernel, no mods, no clean flashes in over a month probably.