yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 3 Questions & Answers] Azhery:
post in Q&A section..do not spam in development section..:rolleyes:
[Xiaomi Redmi Note 3 Questions & Answers] Raaj52:
Kate and Kenzo are different, and from your post I can see that your device is Kenzo, and kenzo is common here and all recovery works with it. I must tell you this, you posted in a different section, please ask the moderators to move this to the Q&A section so that you will get more help. Thank you.
[Xiaomi Redmi Note 3 Questions & Answers] AgentBuBu:
please remove this post from this section, thanks
[Xiaomi Redmi Note 3 Questions & Answers] shaca:
sorry for posting in the wrong section, please move this to the correct place.

anyway tnks for the info. its kenzo yes and its already working :D
[JAMin, XDA Neo, S200 General] ednelh:
The built-in contact in wm2005 is very easy to edit, just tap the name and it will launch the edit immediately. Not just like in wm2003se, what ever you tap, anywhere in the screen it will not edit the saved entry. In wm2005 is very very bad, especiallly if you are careless or you are using the hard buttons in your device. Any body have an idea to restrict this thing? Please...

Not Like in wm2006 and wm2003se. The wm2005 is a garbage OS, especially the 2 white curved lines on the upper bar and lower bar which they called as BASE HUE...
[Xiaomi Mi 2] snooker86:
Is it a crazy idea? Find a similar size but powerful battery (for example xperia z3 compact battery) and connect it directly with the phone's battery pins.
[Xiaomi Mi 2] ramir0:
you should check if the pin config are the same in both batterys i think.. (overside volt & amperes)
[Samsung Galaxy S Relay 4G] phred14:
I've been under the impression that the Relay wasn't about to get Nougat support, because it's graphics chip was too old to do Vulkan. However these two sites indicate that Relay support is in the works. http://www.gizmoadvices.com/list-devices-supported-official-lineage-os/ http://lineageosdownload.com/devices-supported-by-lineage-os/

I'd not be prone to trust that, since they seem to essentially be the same list. (echo-chamber?) However this site http://www.theandroidsoul.com/download-lineage-os/ with download links shows some supported Samsung devices of similar vintage to the Relay, perhaps even older.

I plan to look into this more, but in the meantime, does anyone else know anything?

I also plan to upload my Dec 3 and Dec 29 images from last year to my google drive, and will make those known here, once I have. They're not fully tested - I did a bit more explicit testing of the Dec 3 image, but I'm currently running the Dec 29 image.

Edit - some content:

https://drive.google.com/open?id=0B_MKeoY9qBceVGlWV05fUlVObUU

https://drive.google.com/open?id=0B_MKeoY9qBceRDd5elpZbFZETVk

https://drive.google.com/open?id=0B_MKeoY9qBcecmxBR2xzV2N2cTQ

https://drive.google.com/open?id=0B_MKeoY9qBceVWJQSEUwaXpiNFk

(I fear I've lost track of which is which, but two are zips and two are checksums. Two are Dec 4 and two are Dec 29.)
[Samsung Galaxy S Relay 4G] Bummers:
Nice one! i've been running my relay on the stock OS for years. It's running slow as a dog. I really need to learn how to flash it with a nice new ROM.
[Samsung Galaxy S Relay 4G] SinnedNima:
That would be awesome if the Relay would get a second life.... i'm sooo close to drop it and buy the Nokia 6... hope HMD is living up to some customers expectations and is building a new communicator... love my old buddy E7.

---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------

by the way, the Relay is in basic the S III. But I'm quite astonished that they support the Relay (O_o)
[Samsung Galaxy S Relay 4G] cucumbers:
By "E7" you mean the Nokia E7, right? Oh, I have often fantasized about a device in an E7 chassis but with new internals and running Android... except for the weight, that was my favourite form factor ever, keyboard or not :)

---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------

BTW since my Relay is definitely not my daily driver, more than happy to give these builds a whirl...
[Samsung Galaxy S Relay 4G] mrk2815:
so will there bea linage os for the relay 4g. if so I would be interested for afriend of mine . he loves the relay and so he is wondering if there will be development for linage for the relay 4g. please let me know.
[Samsung Galaxy S Relay 4G] xdoza:
I'm updating here the last CM recovery in case someone needs it.
[Samsung Galaxy S Relay 4G] SinnedNima:
The leaks of the soon to be supported devices have the Relay on it. I can't believe it yet but why not? The Relay is the last Android QWERTY with decent hardware. As i stated before in another thread the S III is nearly identical to the Relay and the SoC is/was quite popular and built in many devices. The chances are high (to good to be true)
[Samsung Galaxy S Relay 4G] phred14:
I've done a bit of looking since, and see that Lineage OS is advertising both Marshmallow and Nougat support. I suspect that means that the Relay is going to get Marshmallow, not Nougat. My impression is that Nougat required Vulkan graphics, and the Relay's graphics chip wasn't capable of that. Still, Marshmallow will be newer and presumably more secure than KitKat.
[Samsung Galaxy S Relay 4G] cucumbers:
Even Marshmallow would be a welcome advance for the Relay venerable Relay.
[Samsung Galaxy S Relay 4G] SoulSingin:
I love my Relay so much that I want it keep it forever.

I bought a couple of extras, so I have some hardware for testing and I am eager to assist anyone who wishes to continue development for the Relay.

Please contact me if I can assist you and/or please direct me to someone whom I can assist.

thanks in advance,

- Soul Singin'
[Samsung Galaxy S Relay 4G] gerbilfat:
LineageOS released their list of officially supported devices and the Relay is not on it. I jumped onto the Lineage OS IRC channel to ask the devs what exactly they'd need to get the Relay officially supported. They said they need a working device tree + kernel. I emailed them the info they asked for and will let you guys know how it goes.

My Relay is my daily driver running CM11 and an more up to date rom would be amazing.
[Samsung Galaxy S Relay 4G] SinnedNima:
check out the development area here at xda, i'm sure there was a kernel over there. i do think that for someone like reventech from the validus project that task would be easy as a pie. don't they have the sources of cyanogenmod? the mirrors are down am i right? on that github should have been the source. i'm not able to build android yet. as an administrator my free time is quite limited
[Samsung Galaxy S Relay 4G] phred14:
Would you be willing to send me the device tree, as well. Or perhaps since I have the sources sitting around, I presume there's a device tree there. I've read about the device tree on Phoronix, but have never really walked through one.

Also, since I've got a source tree, I've also got a kernel in there. However will Marshmallow use the same kernel as KitKat? Oh, google was my friend: https://android.stackexchange.com/questions/51651/which-android-runs-which-linux-kernel

Android Version |API Level |Linux Kernel in AOSP

----------------------------------------------------

1.5 Cupcake |3 |2.6.27

1.6 Donut |4 |2.6.29

2.0/1 Eclair |5-7 |2.6.29

2.2.x Froyo |8 |2.6.32

2.3.x Gingerbread |9, 10 |2.6.35

3.x.x Honeycomb |11-13 |2.6.36

4.0.x Ice Cream San|14, 15 |3.0.1

4.1.x Jelly Bean |16 |3.0.31

4.2.x Jelly Bean |17 |3.4.0

4.3 Jelly Bean |18 |3.4.39

4.4 Kit Kat |19, 20 |3.10

5.x Lollipop |21, 22 |3.16.1

6.0 Marshmallow |23 |3.18.10

7.0 Nougat |24 |4.4.1

7.1 Nougat |25 |4.4.1 (To be updated)

So the problem is that we need a new kernel, and need to map the old config to the new. OK, I always save my kernel configs, and one of my home machines goes clear back to 3.7 and up to the present, except that while I have configs for 3.16 and 3.20, I'm missing everything in between. Another system has five different 3.18 kernel configs, but only goes back to 3.16.3. I know these configs are not usable for Android, but I'm hoping they can give me an indication of what changed between the relevant levels. Scratch that, one the first machine mentioned, I have a 3.18.8 kernel config laying around as well as 3.10.0, 3.10.9, and 3.10.10 configs. Sadly, there are 1570 lines of diff between the two. Haven't looked at any details yet.

This looks like a bit of a chicken-and-egg problem. I'm going to presume that I can't just stuff a 3.18.10 kernel into my CM11 build and expect it to work - though that's the way Linus would like it to be, and the two kernels aren't that far apart.

Pardon the rambling.

EDIT: I just checked my source tree, and I appear to have the kernel source there. Actually there seem to be two sources, "samsung/d2" and "samsung/t1". Neither appears to have been compiled, because I only see .c and .h files in there, nor is there a .config file. Luckily I just checked my Relay, and found "/proc/config.gz". Oh, and here's the other oddity: "uname -a" returns "3.4.104-cyanogenmod-g61tc527e", not the expected 3.10. I may have to grab a Validus image, if I can still find one.
[Samsung Galaxy S Relay 4G] SoulSingin:
Attached is my: /cm_repo/kernel/samsung/d2/arch/arm/configs/cyanogen_apexq_defconfig for CM 11, which uses kernel 3.4.95 and android 4.4.4

Does this help? If so or if not, please tell me how I can help.

And thank you for your help!

- Soul Singin'
[Samsung Galaxy S Relay 4G] emaayan:
would to know how it goes as well, any updates?
[Samsung Galaxy S Relay 4G] emaayan:
from what i've been told they have no plans for it either

https://www.facebook.com/LineageAndroid/posts/1499401083412550?comment_id=1499658536720138
[Samsung Galaxy S Relay 4G] mrk2815:
any new news on any development for this device. i know that the s3 has gotten its linage os 14.1 rom and how come the relay whihc is based off of the s3 cant get a 14.1 rom. just wondering.
[Samsung Galaxy S Relay 4G] _mrbrown_:
I know everyone hates a 'me too'. I have been a T699 user for about as long as it's been introduced. I also use a Stratosphere II and a Galaxy S5, but my Relay is still my favorite. I hope the developers at LineageOS will still consider supporting this phone. Thanks in advance.
[Samsung Galaxy S Relay 4G] cucumbers:
Even though it's not my main phone anymore, I love pulling out my Relay now and then. In fact I'm using it as a music & podcast player since the SD card reader in my main phone died. The only thing that stops me from using it more is that the battery drops like a stone when it's got cellular signal/data going, to the point that it almost unusable day-to-day as a connected device. But it's got great standby life so I'm pretty sure it's the OS, not the battery. I would love it if a new OS actually fixed the battery drain...
[Samsung Galaxy S Relay 4G] Pauleberber:
It would be a dream to geht lineage OS in the relay 4g. Any advance Herr???
[Samsung Galaxy S Relay 4G] xdoza:
Anybody knows if there are news about Relay with Lineage OS? Thanks!
[Samsung Galaxy S Relay 4G] phred14:
Last I knew, they had removed the Relay from their plans. I've thought about attempting to step up, but I really don't know enough to be useful in this. I've basically been a button-pusher for what I've done with the Relay, and those "last" ROM images. I should probably get on Reddit, and see if even with those meager skills I offer enough to see the Relay happen.
[Samsung Galaxy S Relay 4G] mrk2815:
any new news on any development as far as unofficial lineage build for the rrelay 4g. just wondering
[Samsung Galaxy S Relay 4G] phred14:
As near as I can tell, LineageOS has dropped plans for the Relay. I don't believe that there are any Relay developers left. I posted the last generated KitKat images for the Relay, at the end of the year. But I did that as a Linux user who can act as a button-pusher and follow directions. I would not consider myself an Android developer, and doubt I could do much to change the status.
[Samsung Galaxy S Relay 4G] xdoza:
Sad to hear LneageOS has dropped plans to support Relay :(
[Samsung Galaxy S Relay 4G] furboom1240:
If you want to port that...

This is the link for those who have commits. The FAQ I linked to also includes T&C's for porting going forward. As a longtime Relay user, I would love to see LineageOS take the mantle.

https://wiki.lineageos.org/submitting_device.html#submitting-your-device
[Samsung Galaxy S Relay 4G] mrk2815:
how about trying to get the relay 4g support for android 8.0 . i am just wondering since with android 8.0 low end devices can get android 8 android o support. i am just wondering if any one is thinking about doing that for relay 4g with android 8.0. in mind.
[Samsung Galaxy S Relay 4G] computerinfo21:
Android 8 for low end devices really does seem like the possile way forward for the Galaxy Relay. The low memory is what wrecked the newer ROMs on it. In fact, I just visited now to see if anyone else was thinking the same thing.
[Samsung Galaxy S Relay 4G] furboom1240:
The Relay falls short when it comes to hardware. It can't support versions newer than KitKat because the hardware wouldn't be able to keep up. Lollipop variants do exist, but they're not suitable for daily use.

If the Relay were reintroduced to Lineage, it would remain a CM11, Android 4.4.x project and it would only receive service stack updates. All other merges would be ignored, which in theory would make it easier.

But I doubt any maintainer would be as adamant as I am. They've probably moved on to the Priv or KEYone.

---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------

Funny you mention that. Because 7.1 and up are compiled differently, maybe it isn't so impossible as it would be less demanding this time around.

It's great to see open minds at work.
[Samsung Galaxy S Relay 4G] fm0:
Did you https://cascardo.eti.br/blog/News_on_Debian_on_apexqtmo/ ?

We might still get a few more years with the relay.
[Samsung Galaxy S Relay 4G] mrk2815:
since google has introduce android 8.1 go for olde devices.i was wondering if we could build a lineage 15.1 go version optimized for the relay and keep the relay alive this way with a more optimized lineage 15.1 go version for the relay an that way the relay could be kept alive . what about htis thought and is there a developer willing to take on this task.
[Samsung Galaxy S Relay 4G] silverhasarelay:
I was able to build a kernel for the relay using teamapexq kernel sources with the postmarketos build chain, and lots of kernel patching. The kernel wasn't suitable to flash and boot, but it DID kick out a vmlinuz image once. I think with some coordinated effort we could get that working.
[Samsung Galaxy S Relay 4G] ingoreis:
I do not know much with Compiling or near Things,but can you upload this compiled Kernel?

My Idea is to Mix the LineageOS from an nearby Device with your Kernel and maybe it will boot then.

Have a T-699 working and using and another T-699 with slightly Damages but good for Testing Things like this :)
[Samsung Galaxy S Relay 4G] fire_qc:
+1 !!! It still my principal phone, even if I have plenty of more recent ones, because of the keyboard! Still running CyanogenMod 11-20160320-NIGHTLY-apexqtmo.
[Samsung Galaxy S Relay 4G] silvermagnet:
Ok I got another build, and this one actually ran all the way through.

Build env:

Ubuntu Bionic server

packages installed: python3-pip (brings in all the py3) and git

postmarketos commit c3d0f421e1be67ea8ab6c772e0ce29c4f2192cd9

kernel android_kernel_samsung_d2

commit 87f5fcaf7afef878914c3fcca2c2fd395f285902

defconfig LineageOS/android_kernel_samsung_d2/87f5fcaf7afef878914c3fcca2c2fd395f285902/arch/arm/configs/cyanogen_apexq_defconfig

boot.img from cm backup March 2017 (I was using a fattoad one before with no luck)

My expectation is that this will not boot, run, connect, or anything. But, it did compile in a modern build env with the old sources. So that's looking real good for the long term life of this device.

notes from this attempt: pastebin N0BMbpxm

The rom did not flash in the latest clockwork recovery. I also attempted to flash with pmos's heimdall wrapper, but that failed when it found no "KERNEL" partition. Checking my other device in /dev/platform/block/storage/by-name, I see it has a "BOOT" partition listed. I'll try to push through with this, but no promises. :)
[Samsung Galaxy S Relay 4G] silvermagnet:
The PMOS guys advised changing the boot and system partition names in aports/devices/device-samsung-apexq/deviceinfo (the file created for the device when starting a new port) to fix the flashable image. I set them to BOOT and SYSTEM, to match the partitions on the phone. Well, that didn't fix the zip. BUT, it did work with the built in heimdall wrappers. After flashing the rootfs and the kernel in download mode, I got a PMOS splashscreen. :D

There are a few other device ports with slider keyboards so I don't think there is anything unique to do here, just gotta muddle through each problem. I've been trying to build for this phone for 2 years, and will keep at it. Again, no promises though. :)
[Samsung Galaxy S Relay 4G] fire_qc:
It's good to know that somedudes are trying instead of nothing... I'll stay tuned with you bro!!! :good:
[Samsung Galaxy S Relay 4G] cucumbers:
I still have a functioning Relay that I use sometimes for a few days when my keyboard hankering gets the better of me. Happy to do some testing if it helps.
[Samsung Galaxy S Relay 4G] silvermagnet:
Thanks, I'll start a new thread soon when I have something that works. The current obstacle is figuring out why dhcpd started and was listening, meaning the kernel worked and the usb ethernet interface for console started, but sshd did not, meaning no access. I'm told that it is caused by the root fs failing to mount. There is a boot mode to stop boot and allow ssh into the initrd (so cool!), so I'm playing with that now.
[Samsung Galaxy S Relay 4G] silvermagnet:
Looks like X is failing to start. Rootfs must have mounted or the logs wouldn't have told me that. Why sshd does not start on boot is still a mystery, but hey, I was able to get into the thing.

I made a Samsung_Galaxy_S_Relay_4G_(samsung-t699) page on the postmarketOS wiki to track progress and eventually serve as a guide.
[Samsung Galaxy S Relay 4G] ingoreis:
Wow a big first Step,thank you for your Effort.

Unfortunaly i cannot help with this Linix/Android Backround Things..

..but i am Curious about how far you will come with Lineage here.

The T-699 is my Favourite Phone :good:
[Samsung Galaxy S Relay 4G] silvermagnet:
So the thing with lineage is the new builds require a newer kernel. I got 3.4 to build, but it's old as heck. What you have to do to make it all "go" is find all the differences between the 3.4 kernel mod I used, and the normal mainline code from that version, AND the differences in newer kernels required for a newer lineageos, and then fix all the inconsistencies to get the old hacks on the new tree. Finally, port the defconfig from the old one to the new one. Then it might work.

I think. I dunno Imma n00b too.
[Samsung Galaxy S Relay 4G] ingoreis:
When you need a Beta Tester..i do have a Spare T-699 here for Testing Things :)
[Samsung Galaxy S Relay 4G] silvermagnet:
My work so far is all bundled up in gitlab and I've got a merge request open. Testers can help by pulling down my branch and installing the samsung-apexq port, and then filling in what works and what doesn't in the info box on the galaxy s relay device page on the postmarketos wiki. gitlab /5ilver/pmaports/tree/apexq
[Samsung Galaxy S Relay 4G] cucumbers:
I've navigated to your gitlab page but I'm not too sure what to download... there's a download icon in the upper right but as far as I can tell it only downloads the source code (I really don't understand these ROM builds so I may be completely wrong...)
[Samsung Galaxy S Relay 4G] ingoreis:
Firstly..a big Thank you :)

I searched a Download Icon on the PostmarketOS Site and in Gitlab too for my Windows Browser but found none.

Do you have only the Source there?

I thought there is a builded One :)

Then i tried to download your Gitlab File with Gitlab but my Linux on the OpenPandora do not have gitlab.

A Compiling Yesterday Evening of Gitlab did not work because big Depencies.

So i did not found a Way to your Files and i do know only a very little about Compiling.
[Samsung Galaxy S Relay 4G] silvermagnet:
The postmarketos port should allow for a flashable update zip to be generated when it is all working properly. Right now if you download the pmbootstrap tool and run it with my aports repo, it can compile a kernel and a root filesystem and flash them with the phone in download mode. It needs a linux machine with a recent python version to run but mostly configures itself (read their wiki). They support other phones more fully so it might be worth looking at what they have done with the galaxy s3 to see where this is going.
[Samsung Galaxy S Relay 4G] ingoreis:
I tried with an Rescent Xubuntu to download your Files.

Gitlab is too complicated for me.

Do you have a direct Link for downloading your Files?

I do not get Gitlab installed,did not get it compiled and found your Files not.

Its a Shame for me because i want to test,want to help but cannot get your Files.

Too complicated to find your Files,please a Direct Link.

Regards

Ingo Reis

Edit: Finaly i found it: https://gitlab.com/5ilver/pmaports/tree/apexq
[Samsung Galaxy S Relay 4G] cucumbers:
I agree, for many of us who are likely to want to help testing this new build, compiling a flashable zip will be too complicated and/or we don't have the means to do it ourselves. If someone could make a zip that's flashable in recovery and share it here that would be great.
[Samsung Galaxy S Relay 4G] ingoreis:
-Downloaded your Files in Xubuntu

-wanted to pmbootstrap it

-pmbootstrap was not installed

-this pmbootstrap is not on the Repos

-downloaded pmbootstrab from git

-building did not work

-python ./setup.py did not work

-gave up

Even on an very rescent Xubuntu18 64Bit Version i cannot get your Files compiled.

I hope for "ready to test Files" Files for testing.
[Samsung Galaxy S Relay 4G] silvermagnet:
Thanks for trying. You don't actually need to run the setup. In the local copy of the repo just run ./pmbootstrap.py instead of pmbootstrap. The instructions don't have very good step by step commands.

If I manage to make a flashable zip I'll post it. I have seen this build a zip that flashed and worked on a galaxy s3 so I know it is possible.

(progress has been made in new thread https://xdaforums.com/galaxy-s-relay-4g/development/postmarketos-t3916178)
[Samsung Galaxy S Relay 4G] alexenferman:
Edit: Wrong thread
[Galaxy S 5 Q&A, Help & Troubleshooting] zarlydoug:
So this is kind of a funny story. I recently bought my son a used S6 to replace his S5. Since he had a new phone I thought I would show him how water resistant his S5 was by putting it into the bathtub filled with hot water right before he got into the tub to take underwater pictures of his Lego guys. Right as I said "we better stop before we push our luck" my son said "Dad the left button isn't lighting up anymore." Poop I said we pushed our luck too far. So yeah, now the capicitve menu key no longer lights up ?

I've torn down other phones in the past for repairs so I watched some tutorials on YouTube, but it's not clear to me which actual component to replace. It looks like the charging port ribbon cable covers the soft keys but they were never mentioned directly in the repair tutorials and the charging port ribbon cable doesn't look like it has any LED's on it. So they light up on the display or digitizer or something like that? Does anyone have a sufgestion?

Thank you in advance for your help.

Doug.
[Galaxy S 5 Q&A, Help & Troubleshooting] Youdoofus:
i wouldnt do it just because of the burned out light. Too risky, might break the glass. Galaxy devices are a PITA to disassemble
[Galaxy S 5 Q&A, Help & Troubleshooting] zarlydoug:
Yeah you're probably right. Then again I haven't checked it today maybe it's magically started working again. :fingers-crossed: