yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] phred14:
Does anyone know if Google's Android security updates are still going into Kit-Kat, or if the Cyanogenmod team is backporting security updates to KitKat? There are two pretty significant security issues that Google is releasing fixes for in March:

1 - Stagefright - It turns out that the first fix, last year, didn't really fix it.

2 - Linux kernel - There was an old kernel escalation vulnerability that is only now being fixed.

So once upon a time, it sounded like there was some Lollipop work being done on CM, but that never made it out to nightlies. It sounds like some non-CM images may be Lollipop, but I don't know about the status on those. Now Marshmallow is out, any prognosis? Is this even something doable, or is the Relay too old, and it's binary-only drivers too ancient for the new higher-level code?
[Samsung Galaxy S Relay 4G] cucumbers:
They are doing security updates, yes. The latest CM11 nightly (which I'm running) has the 1 March 2016 security patch.
[Samsung Galaxy S Relay 4G] phred14:
Looks to me that you know something I don't - namely where to look for the changelog. Can you share that arcane knowledge?
[Samsung Galaxy S Relay 4G] cucumbers:
I'm not sure where to find the changelog on the cyanogenmod website, never noticed it on the downloads page & I've never bothered looking at it. I get there is one somewhere, but I have to admit I can't be bothered to find it at this time :)

BUT - on the phone itself, if you go to Settings > About Phone you'll see a Changelog menu item near the top. And if you keep scrolling down the About Phone screen, you'll see "Android security patch level" right below the "Android version" entry.
[Samsung Galaxy S Relay 4G] Xenobio:
My phone is overheating and eating battery like crazy since the most recent 20160320 nightly. Fairly sure it's the only new thing, I haven't installed any new apps recently :(
[Samsung Galaxy S Relay 4G] phred14:
I have not been seeing that problem. I'll ask one thing - you do know not to reboot the phone while connected to a charger, don't you? If you boot while connected to the charger, it never gets into deep sleep states. I do let it reboot right after the flash, so it's connected then and while re-translating all of the apps. But after that I shut it down, and then do a clean boot while disconnected.

I tend to leave my phone in airplane mode most of the time, turning on cell when I feel like calling or when I'm expecting a call. At that rate, my current charge is between 40 and 50 percent, after a bit over three days.
[Samsung Galaxy S Relay 4G] Xenobio:
Thanks, I wasn't aware of that.

Anyway I went back to the last "snapshot" version... 20150831. Not really seeing significant benefits in keeping up with the nightlies.
[Samsung Galaxy S Relay 4G] phred14:
There are the security updates. There are some key updates that postdate that snapshot. I've been quite happy keeping up with the nightlies. That said, I'm leaving for a trip to the UK soon, have temporary SIMs for my wife and me in-hand, so our phones aren't getting flashed again until after the trip. Besides, the one I'm running - 20160320 is still the latest.
[Samsung Galaxy S Relay 4G] ssnsltd:
CM11 nightly ###11.0.0 M11 they "re-introduced Samsung Galaxy Relay 4G (apexqtmo) support" Which i suppose is a good thing. but would be nice to jump to MM
[Samsung Galaxy S Relay 4G] furboom1240:
I always had that issue with my Relay. Good to know and I think my m8 has a worse rendition of that blunder: it bootloops sometimes too.

I'm glad nightlies are still possible for any d2 based device. We're talking straight outta 2012 here...
[Samsung Galaxy S Relay 4G] phred14:
So today I saw the headline, "Google Patches 40 Android Flaws in June Update". It doesn't say if KitKat is getting the fixes or just Lollipop / Marshmallow. Or for that matter, Cyanogenmod might backport the fixes to KitKat.

http://www.eweek.com/blogs/security-watch/google-patches-40-android-flaws-in-june-update.html

Anyone know more, or how to find out CM plans?
[Samsung Galaxy S Relay 4G] furboom1240:
http://www.cmxlog.com/11/apexqtmo

It looks like there's an error04 on the feed. It really is unfortunate they can't cache nightly data up to a week...

Sent from my HTC M8 GPE

? Mass Transit Honchkrow ?
[Samsung Galaxy S Relay 4G] phred14:
I was able to see the feed. It looks as if many of the fixes are marked not to be merged. I wonder if that's a Kit Kat problem, or a Relay problem.
[Samsung Galaxy S Relay 4G] phred14:
Another piece of curiosity... I just noticed that the 20160612 nightly is out, and decided to check your status site. Probably two-thirds of the fixes were marked "DO NOT MERGE", but when I click on those fixes, I see that they have been successfully merged.

Can anyone explain?
[Samsung Galaxy S Relay 4G] furboom1240:
Maybe both. The Relay is quite the crusader. I'm astounded it's lasted this long. I just might re-buy a Relay...

Sent from my HTC M8 GPE

? Mass Transit Honchkrow ?
[Samsung Galaxy S Relay 4G] Zamo007:
Saludos tengo un problema con la instalacion del cm11 en el sgh-t699 no arranca al instalarlo, o se reinicia o se queda atascado en el logo
[Samsung Galaxy S Relay 4G] phred14:
OK, I'll not go into details, but it appears that the nightly builds may have stopped. I've looked into this when Nardholio stepped aside, and I guess I'm looking into it again now. I started "brunch apexqtmo" about an hour or so ago. This is not a horribly fast machine, so I don't really know when it will be done. As you might have guessed, I'm not really qualified to be a maintainer, but I'm willing to help, willing to learn, and willing to run builds. At the moment I'm working off of the "How To Build CyanogenMod for Samsung Galaxy S Relay 4G ("apexqtmo")" page. (I believe I've been given another page - a more vanilla Android page, but forgot about that one.) So for a few specific questions:

1 - The instructions specify using "extract-files.sh", but I got the impression that if I'm using TheMuppets I don't need that. I've got TheMuppets in a local_manifest file and reran "repo sync" after putting it there. Am I mistaken - do I really need to run "extract-files.sh"?

2 - Originally, nightlies all used the same old recovery, then a few months back a new recovery was published with each nightly. Do I really need to re-flash the recovery every time? I'm particularly worried about my first flash of my own nightly, and would rather flash it from a known-working recovery than from the one I'd just built.

3 - As I said, I'm not particularly qualified. Is anyone else willing to help out a bit, particularly someone better qualified? At this point CM11 is pretty stable, so it shouldn't be onerous.

4 - Maybe none of this is necessary, and the picture isn't as gloomy as I fear.

EDIT - By the way, I now have a new, home-built ROM image. Next to muster up the guts to actually flash it.
[Samsung Galaxy S Relay 4G] furboom1240:
I've been able to flash CM12 builds with the discontinued PhilZ recovery for awhile, so I don't think an updated recovery is important.

You can also tick the Dev Option so it can be done for you.

I find the efforts placed into this device by the Dev community admirable[emoji106]

? Eric Shields | #MassTransitHonchkrow ?

THE Hudson Valley's essential Fare-blazer ?
[Samsung Galaxy S Relay 4G] robuser007:
Download: cm-11-20160815-NIGHTLY-apexqtmo.zip (209.71 MB) is the latest build, any chanche for new builds?
[Samsung Galaxy S Relay 4G] phred14:
I have set things up, and have built a few ROM images. I'm not sure if I've done so correctly though, so I've never had the guts to flash one of the images I've built. Since the nightlies have stopped, I've been thinking that I should try building again. Prompted by this post, I'm currently doing a "repo sync", and then I'll see if I can brunch again. Oops, the sync just failed, retrying. I've expanded my xterm, in case there were error messages I was unable to read.

I'm running CWM recovery. (Sync complete) So what I think I'll try later this week is a nandroid backup, the flash my new image and see how it goes. Presumably I can reload my nandroid backup and get back to 20160815 if things fail. ("brunch apexqtmo" starting now)

I'm also almost ready to give up on the Relay, because KitKat looks like the best it's going to do. The hardware isn't capable of Nougat because the graphics chip is too old for the Vulkan API. It also looks like some security stuff won't get backported to KitKat, so I don't think I'd ever trust Android Pay on it. (I already don't trust a lot of things on it.)

At the moment my leading candidate is a Moto X Pure, in case anyone has comments on that. (brunch just said"

/local/home/dale/android/out/target/product/apexqtmo/obj/APPS/SignatureTest_intermediates

find: ‘src’: No such file or directory" but it still appears to be running. Just kicked another similar error, can't see it now, but still running.)

---------- Post added at 07:46 PM ---------- Previous post was at 06:51 PM ----------

-rw-r--r-- 2 dale users 219787724 Oct 16 19:23 cm-11-20161016-UNOFFICIAL-apexqtmo.zip

Now to try it, probably later this week.

Can anyone point me to a changelog for CM11? Someone pointed one out earlier, but that link is dead, and I can only find a CM13 changelog.
[Samsung Galaxy S Relay 4G] phred14:
OK, I've finally done it. I just flashed CM11-20161126-UNOFFICIAL-apexqtmo onto my relay, and so far everything appears to work OK. Amusingly I built it today - actually several times since Nov 26, but that's probably the day the codebase changed. From what I understand, Cyanogenmod no longer updates CM11, but Google updates AOSP 4.4.4, so I'm probably picking up CM11 on top of the AOSP updates. For me, that means Google's security updates, so this is worth it. I'll give this a few days, and if I'm still happy I'll update my wife's phone.

Don't know where to go past here, but at least there is now something newer than the 20160815 nightly.

Is anyone aware of some sort of vulnerability scanner, so I can check what has been fixed and what hasn't?
[Samsung Galaxy S Relay 4G] Bummers:
How have you got in with your ROM? Which one would you recommend for a n00b who wants to extend the life of his relay?
[Samsung Galaxy S Relay 4G] phred14:
I've been running my flashes for over a month now, take a look in "Android Development" under the "Lineage OS" topic, where I posted links to two images on my Google Drive.
[Samsung Galaxy S Relay 4G] xdoza:
Hi mate! Sorry to bother.

Can you tell me which version or REV3NT3CH custom kernel you use with CM11? I'm using CM11 nightlies and have some issues with the microphone in whatsapp voice notes being too quiet, and read that maybe i can do some kind of microphone gain (with apps like FauxSound Sound Control) but i need a custom kernel with sound control enabled for that.

By the way, if you still have the relay with CM11, does voice notes work in your phone?

Thanks in advance!
[Samsung Galaxy S Relay 4G] cucumbers:
D2 v2.3. But I have to admit I haven't tried the Whatsapp voice notes, ever - I don't even have Whatsapp installed on the phone. I don't use the phone much but next time I do I'll give it a try and let you know.
[Samsung Galaxy S Relay 4G] silvermagnet:
Archive.org slurped up two builds of cyanogenmod for apexqtmo.

https://web.archive.org/web/2014092...cted.net/jenkins/57774/cm-10.2.1-apexqtmo.zip

https://web.archive.org/web/2014102...53799/cm-11-20140104-SNAPSHOT-M2-apexqtmo.zip
[Samsung Galaxy S Relay 4G] scotte9999:
I'm seeing the same thing with the 20140729 nightly, doing a dirty flash from a mid-June build.

Any ideas on a solution?
[Samsung Galaxy S Relay 4G] robuser007:
I'm having thr same problem coming from 24/07 (which worked fine).

Will there be any support for cm11 in the future ?
[Samsung Galaxy S Relay 4G] scotte9999:
I see http://review.cyanogenmod.org/#/c/69419/ went in today, which in theory will fix the build. Not sure if that'll actually fix the problem though.
[Samsung Galaxy S Relay 4G] robuser007:
But there aren't new builds so kinda useless. I hope someone will continue the hard work of Nardholio ?

nightly 24/07 is the latest nightly without the wifi bug (no problems with that build).
[Samsung Galaxy S Relay 4G] scotte9999:
Well, building is relatively easy. I put a 2014-08-03 build up at http://d-h.st/BxR . Completely untested.

Update:

Not completely untested. :) Installed on my wife's phone, and confirmed WiFi and Bluetooth work. Looks like a normal nightly build from what I can see. Thanks to Nardholio for keeping the phone alive as long as he did.
[Samsung Galaxy S Relay 4G] robuser007:
Thanks :) Link is a little slow. Could you build new builds now and then ?

edit: without my mobile the link works just fine (adblock issue maybe?).
[Samsung Galaxy S Relay 4G] saurabhsaurabhrai:
Can anyone help me out with a problem I'm facing with my phone after flashing CM11 M8 rom....My phone id not detectable by any computer (MAC/Windows)...I also tried different data cables....But charging well and fast....Plz help :crying: :confused:
[Samsung Galaxy S Relay 4G] orange808:
It could be your hardware. Restore your backup of the stock rom and see if that fixes the problem. You did make a backup, right?
[Samsung Galaxy S Relay 4G] scotte9999:
Detectable as what? No USB device shows up at all? The phone is present via ADB, but not MTP or umass?
[Samsung Galaxy S Relay 4G] gtmaster303:
You're not the only one either. dhacker left for similar reasons too

And now we just got word that hashcode left because he got a new job and doesn't have the time

CM future is looking bleak for A LOT of devices

But if you still want to stick with QWERTY, the LG F3Q seems to be the last hurrah released earlier this year. Other than that, there's no new devices out.
[Samsung Galaxy S Relay 4G] Gibson99:
as has been stated plenty of other times, the f3q actually has WORSE specs than the Relay. Basically manufacturers weren't content to just silently stop making qwerty devices. they wanted to give us the finger on their way out, too.
[Samsung Galaxy S Relay 4G] cucumbers:
Frankly the specs of the Relay are still in line with a lot of "budget" or "mid-range" phones being put out on the market even now. It's a device that's aging remarkably well, I would say. Just with the screen wasn't pentile or had higher ppi...
[Samsung Galaxy S Relay 4G] Gibson99:
agreed. sammy makes some decent phones now and then, and this is one of them. the continuum was NOT. and the relay is still the highest-spec'd qwerty slider you can get today, which is why i just bought one a couple months ago. my only complaints about it is the screen is a little small, and needs to be higher resolution. also the keyboard doesn't feel as good as my droid4, but the relay keyboard has symbols on nearly every key, which the D4 doesn't.

there were some leaked photos of the supposed droid5 almost a year ago now, and obviously that never came out. of course, i probably wouldn't have got it anyway since it would've been verizon-only and i'm not a verizon customer anymore. as it is the droid4 was a cruel joke in terms of radios - it has perfectly functional GSM radios and a sim card slot, but there's something baked into the firmware that prevents you from using any US carrier's GSM sim card in the phone. you can use any international one, but ATT and TMO (and their MVNOs) sims simply don't work. i imagine the droid5 would have been the same if not worse.

i only mention the droid5 since it was one that made it into prototype and looked nearly finished, but never made it to production. i have a feeling the f3q may be the last halfway decent qwerty android we'll ever see. makes no sense to me... why bother wasting a keyboard on a dumbphone, which seems to be about the only other place you see keyboards still coming out on new phones? seems to me a flagship-level android device with a good keyboard would help get those last few customers still hanging onto their blackberries, even though BB is a sinking ship.
[Samsung Galaxy S Relay 4G] robuser007:
You could also buy the samsung galaxy s5 with a bluetooth attached keyboard case ?

But it's really big (almost 3 cm height compared to the relay 4g).
[Samsung Galaxy S Relay 4G] TPMJB:
The bluetooth cases absolutely suck. I got one for my GS4 when I had it. Typing made me want to punch babies and kick puppies. I actually found it faster going key-by-key on touchscreen (shudder). I sold the GS4 and snatched up this puppy :)

I know for the GS4 there was only one slider bluetooth case ever made for it. About ten thousand "companies" bought it up and sold it anywhere from $20-100 on Amazon and across the internet. Had different brand names on it, but it was the same keyboard.
[Samsung Galaxy S Relay 4G] robuser007:
A lot of changes everyday: could someone make new unofficial builds please (weekly build) ?
[Samsung Galaxy S Relay 4G] scotte9999:
I built one just now, and put it at http://d-h.st/0fn . Totally untested.
[Samsung Galaxy S Relay 4G] robuser007:
Thanks :) Tried it but doesn't boot.
[Samsung Galaxy S Relay 4G] scotte9999:
Just stays at the spinning CM logo, or ??

Do you get anything via logcat over ADB?
[Samsung Galaxy S Relay 4G] Magamo:
It is highly unlikely that any builds of CM11 made after July 28th will work at present.
[Samsung Galaxy S Relay 4G] robuser007:
It stays at spinning CM logo.

It is highly unlikely that any builds of CM11 made after July 28th will work at present.

Why ?
[Samsung Galaxy S Relay 4G] scotte9999:
What commit did you see that looks likely to break apexqtmo? I didn't see anything immediately obvious.
[Samsung Galaxy S Relay 4G] Magamo:
proprietary_vendor_samsung/187689ea76effd42b680a147d080512ac62a0fed and proprietary_vendor_samsung/aecee5463eeb1e78001c9b386553f5a47cb981ae

Are the most likely culprits. I know reverting those two allowed TeamApexQ to continue using the old blob structure with OmniToad.
[Samsung Galaxy S Relay 4G] scotte9999:
Huh, those do look problematic, but the prior build I made on August 3rd should have already had those commits, and it seems to work. Oh well, if I get cycles I'll try reverting those and see if things work.

Thanks for the pointer.
[Samsung Galaxy S Relay 4G] Magamo:
I'm not precisely certain when those commits were merged, they may have been merged to the cm-11.0 branch after August 3rd. I'm just going by commit date, which was the 7/28/14
[Samsung Galaxy S Relay 4G] tdm:
Anyone still running apexqtmo?

My wife has one, currently running CM11 M8. I went to look for recent builds and discovered that it's been maintainerless for a few weeks.

I can pick it up, but I'm spread kind of thin. So I'll consider being a maintainer but only if there's some interest. Show of hands?
[Samsung Galaxy S Relay 4G] orange808:
Still running it here.
[Samsung Galaxy S Relay 4G] Gibson99:
yep, nardholio moved on to browner (qwerty-less) pastures a few weeks ago. maybe you two could work together, or he could turn over any goodies he has to you.

I'm still running m7 but only because i haven't had time to back up the phone and load m8. My only comment is i wish there was a way to disable the notification about an upcoming alarm. I know it's upcoming... It's set to go of every day.

meanwhile i WISH i could convince my wife to run cm on her s3. she complains about ads, slowness, bloat and battery life constantly but doesnt want to even try it.
[Samsung Galaxy S Relay 4G] scotte9999:
Yeah, it's been maintainer-less, and fallen into a state of disrepair. Looks like there's only a little breakage due to changes in the prebuilts (if you use TheMuppets, of course), but since it's my wife's phone (not mine), it's not really easy for me to track down what's broken (hard to pry the phone from her hands!). I know I'd appreciate it if somebody else stepped up to maintain.
[Samsung Galaxy S Relay 4G] Gibson99:
i know exactly what you mean about getting it away from her. my wife's always on facebook or bubble witch or whatever but she complains about stuff then doesnt give me any time to troubleshoot and won't consider dumping some of her games. *shrug*

i have neither the time nor knowledge to maintain this myself. they keep me pretty busy at work and now that my wife just had foot surgery, i'll have even less free time.
[Samsung Galaxy S Relay 4G] tdm:
Okay I transplanted my wife's stuff onto my mako and traded her for a few days. I should have apexqtmo back up this week.
[Samsung Galaxy S Relay 4G] tdm:
Got pretty close to a working build today. I'm having an issue with the display freezing shortly after boot. Hope to fix that tomorrow. Once that is fixed, I hope it will be smooth sailing.
[Samsung Galaxy S Relay 4G] tdm:
Didn't fix the display today. Might take a couple more days.
[Samsung Galaxy S Relay 4G] Gibson99:
Quality, not quantity. One good update is way better than 50 buggy ones.

Thanks for your efforts!
[Samsung Galaxy S Relay 4G] tdm:
I ripped out all the "common" proprietary blobs and replaced them with stock ones, then just updated only what is necessary to get things working (namely the display/adreno blobs). Working like a champ. :D

Hopefully I can get this all sorted out and start nightlies again tonight. If not, Monday at the latest. Unfortunately, I think we'll probably miss M10.
[Samsung Galaxy S Relay 4G] tdm:
Looks like camera isn't working yet, everything else looks good.
[Samsung Galaxy S Relay 4G] phred14:
Is that for still, video, or both? For me, still still worked at M8, but video didn't. I saw where someone managed to have video working in a nightly some time around late July, I believe after the last regular nightly, but before the "common commits" that seemed to have killed regular builds.

I also take it that in your prior post when you mentioned "common proprietary blobs" you mean those 2 commits that Magamo mentioned on this thread on "25th August 2014, 02:18 PM"? The other day I finally (a true noob) managed to revert those commits and build a ROM from a repo sync of Sept 4. I haven't tried loading that build first.

I also have the "proprietary/samsung" directory and the rom image both copied from both before and after the revert, so it should be possible to know exactly what changed. (and what was just a move to push more into common-msm8960)

I'm new to Android, and just started down the development path when there was a call for a new developer over on the Q&A thread. I have however run Gentoo Linux for over 10 years and do a decent amount of scripting/support/admin at work. I'll help if I can. There are also 2 apexqtmo phones in the house, though one is my wife's, and I'll probably want to stick to Milestone builds on that one. Right now I'm stuck at M8, and recognize that if I ever want to get more milestones, and get video running again, I'll probably have to help somehow.

Let me know the best way I can help out.

(Edit - corrected M9 above to M8)
[Samsung Galaxy S Relay 4G] scotte9999:
Camera has always been a bit funky. Specifically for Video, I never had anything other than VGA working reliably. Not that big of a deal for the wife though, as she normally only takes stills.

Good job on getting back to a working build though!
[Samsung Galaxy S Relay 4G] tdm:
The camera process dies because the underlying code isn't creating a preview surface. I'll probably need to mix in the msm8960-common camera stuff to fix that, but I haven't had time yet. I'll try to get that done Monday.

I've forked the CM repos to my personal github and pushed the changes to get the build working. They are not final or complete, but they should allow anyone familiar with development to hack around with the camera stuff.

github.com/tdm/proprietary_vendor_samsung

github.com/tdm/android_device_samsung_msm8960-common

github.com/tdm/android_device_samsung_apexqtmo
[Samsung Galaxy S Relay 4G] RodimusConvoy:
Is it at all possible to use an older camera .apk, or get one of those fancy DSLR-ish paid apks from the Play store, to compensate?
[Samsung Galaxy S Relay 4G] TPMJB:
Camera and Video work in Liquid Smooth's rom. I'm not sure if that's relevant, but same Android version AFAIK. Maybe Reventech might shed some knowledge on the issue?

Video still doesn't work in snapchat on his rom, though.