yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] phred14:
So far, so good...

So the SDK and Eclipse are both installed on my wife's computer, though I'm not really using the latter at the moment.

I've been following the HowTo instructions from the Cyanogenmod page and this morning ran "breakfast", after an overnight repo fetch. At this point it's time to either fetch files from my device or TheMuppets, and the latter has been strongly urged here. I've found instructions for building local_manifest.xml for CM10, as well as a sample file as a start point. Does revision="cm-10.2" become revision="cm-11" or revision="cm-11.0", or is it something else entirely? This sample file looks like it's for the "Toro", though it has lines with "Tuna" as well, which I presume is a similar-enough device. Is there a better source for this file, can someone post theirs, or is it just time to stumble around?

Next question... According to this post http://xdaforums.com/showpost.php?p=55045664&postcount=63 a simple build just isn't going to work. I've never actually used git, and even with what I've done so far it's so deeply buried that I don't really see it except as a name. But it looks as if I have to remove those two commits in order to have a chance of building a working rom. Can someone give me a start? I can RTFM, but I suspect that things are also buried here in android-conventions so that even with the manual, how to do this won't be obvious.

Thanks...
[Samsung Galaxy S Relay 4G] scotte9999:
Yes, you want "cm-11.0". For example, you'll have lines in local_manifest.xml like:

<project name="TheMuppets/proprietary_vendor_samsung.git" path="vendor/samsung" remote="github" revision="cm-11.0"/>

For reverting a specific commit (like the two that [MENTION=4908192]Magamo[/MENTION] mentioned in the post you referenced), you can use git-revert. Check out http://git-scm.com/blog/2010/03/02/undoing-merges.html as a starting place.

Note that for your first build, you don't need to use git (just repo). A breakfast and brunch should work - you should get the UNOFFICIAL-nightly.zip file built, it just (potentially) won't work if you were to flash it. I recommend making sure brunch creates a .zip file with all the bits you expect it to have, before you start messing with git and reverting the commits that potentially broke the device. IMHO anyway.
[Samsung Galaxy S Relay 4G] phred14:
So overnight last night "brunch" built a .zip for me. I presume that it built at all is a good sign, but "with all the bits you expect it to have" is another test. I struggled a bit with local_manifst.xml, and ended up unzipping my cm11-M8 zip, which actually didn't help, because nothing in that list came from TheMuppets. More about that later. In the meantime, I presume I should unzip the rom file I just created and compare it to my unzipped cm11-M8 files?

As mentioned, I have relatively low confidence in my local_manifest.xml file. I found one on the web which was clearly for a different Samsung phone, changed the obvious things to apexqtmo and the "msm8960" that it appeared to be derived from. Then I started removing lines flagged when I started running the "breakfast apexqtmo" command. What I wound up with is this:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remote fetch="http://github.com/" name="gh" revision="master" />

<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-11.0" />

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-11.0" />

<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-11.0" />

<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-11.0" />

<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-11.0" />

<project name="TheMuppets/proprietary_vendor_widevine" path="vendor/widevine" remote="gh" revision="cm-11.0" />

<project name="TheMuppets/proprietary_vendor_nxp" path="vendor/nxp" remote="gh" revision="cm-11.0" />

<project name="CyanogenMod/android_kernel_samsung_t1" path="kernel/samsung/t1" remote="github" revision="cm-11.0" />

</manifest>

Most of it makes sense, but it really depends on vendors imgtec, broadcom, invensense, widevine, and nxp covering the apexqtmo as well, since they originally covered the "tuna", which appeared to be a later phone. It also depends on kernel_samsung_t1 covering the apexqtmo. I did a bit of browsing around on github to get to this point, as well as the manifest unzipped from the cm11-M8 file I'm currently running.

Sorry for being a complete noob about this, but I guess I am. Thanks for your help. I'm also looking at your pointers on reverting commits, but I'm guessing that eventually we'll need a location to fork the affected files.
[Samsung Galaxy S Relay 4G] scotte9999:
Attached is what I use. It's not apexqtmo specific, since I have multiple devices that I like to build for, but if you can afford the disk and bandwidth it should "just work" for apexqtmo. :)
[Samsung Galaxy S Relay 4G] phred14:
The format looked slightly different, but I have a copy, and I grabbed a few of the lines, tweaked to the format I have. Some of those entries looked like phones, and some looked like hardware vendors with components on phones. I was most interested in the latter.

One question... The other night my build went to completion and produced a zip file. Obviously those two commits will prevent it from booting on my phone, but other than that was it probably a good zip. What I'm really asking is, if the process completes, has it run correctly? Or will it continue running in spite of errors, producing a bogus zip file?

It's late tonight, but I think tomorrow morning before I leave for work I'll do another repo sync. This time before I build I'm going to set up ccache.
[Samsung Galaxy S Relay 4G] demkantor:
Once the zip is produced it is good, yes there can be issues like the commits you mentioned but in theory it should be ready to flash
[Samsung Galaxy S Relay 4G] Magamo:
In general, 'breakfast' will produce a very workable local manifest for you, you just need to add the project for the proprietary blobs.
[Samsung Galaxy S Relay 4G] phred14:
Today I scripted the build process and let it whirl away. Other than making the computer more than a bit sluggish for my wife, it completed just find and created a .zip for me. At this point I think it best to let this run at night - what I really need to do is find what suspend command xfce is using, and have it auto-suspend when the job is done.

It's time to revert so I can build a zip that is worth flashing, and after reading your link I have another question... It looks to me as if once I've reverted those 2 commits, they will stay reverted even through repo sync commands, until I decide to revert my revert. (It also looks like it would be a good idea to save away the commit numbers git gives me for the reverts..)

Plus one more question... There is a clockworkmod recovery image file in the directory along with the cm11. Is there any reason to use this instead of the clockwordmod recovery I flashed back around the beginning of this year, when I first started by flashing CM10.2?

Finally, it appears that these are nightly builds I'm getting, basically like the trunk in subversion. At some point I would like to build Milestones, if only for my wife. How does one choose that?
[Samsung Galaxy S Relay 4G] scotte9999:
Yes. You really want to make your own fork, etc., but for a GIT newbie that might be too much to tackle at once.

I *think* you need an updated recovery (I use the latest TWRP, found over in the Development forum) and it works fine. If you like CWM, then I'd update to a CM11 CWM.

If you followed the instructions on how to retrieve the source via repo, then you've actually downloaded the Milestone source as well. To build a milestone, you'd need to check out a specific tag (e.g., "M8") then build. Not that hard, but I recommend baby steps.
[Samsung Galaxy S Relay 4G] Magamo:
There's really little reason to use the updated recovery, if you're only focusing on Android 4.4 builds, unless there's some whizbang new feature included in an updated build. The older one is tested, stable, and very fine. If you're looking to flash anything OTHER than an Android 4.3.X or 4.4.X build, you'll want to update -- I know that the newer TWRPs have made it so that you can flash ancient images with it (I've tested it all the way back with one of the first CM9 alphas TeamApexQ released.) If CWM hasn't included that feature, then you may have some problems flashing the latest baseband and bootloader firmwares, as those are using the old format installer scripts, that google broke with Android 4.4 recoveries until the community fixed them.
[Samsung Galaxy S Relay 4G] scotte9999:
I think you need to be in the directory of the repository to do the git revert (e.g., if you're in android/system then you can only revert commits from whatever repository populated that directory). Is android/system where the commits were to? (I thought they were to somewhere else).

Seems like you are on the right track with everything. For a quick and dirty test, you could just manually revert the commits (read: go edit the files yourself). It'll get blown away on a sync, but would be a way to get a (potentially) working build w/o debugging the git revert.
[Samsung Galaxy S Relay 4G] phred14:
Second attempt:

~/android/system/vendor/samsung $ git revert -m 1 187689ea76effd42b680a147d080512ac62a0fed
error: Mainline was specified but commit 187689ea76effd42b680a147d080512ac62a0fed is not a merge.
fatal: revert failed

This time instead of being at the top of my android tree I went down to what looked like the "relative top" for the changes. It seemed to like where I was running the command, but this time it didn't like the handle I fed it. I'd seen some references to just the first 7 characters and tried again feeding it that, but got the same message, including having my 7 characters fleshed out into the full string. If I read that message correctly, it wants a "merge handle", not a "commit handle", but I don't have one of those. No doubt someone with git-fu can query one to get the other. Never mind - it's

git log 187689ea76effd42b680a147d080512ac62a0fed

but at that point I'm still not sure how to track down the right handle. From that command I get:

commit 187689ea76effd42b680a147d080512ac62a0fed
Author: Ethan Chen <intervigil@gmail.com>
Date: Mon Jul 28 12:36:03 2014 -0700

apexqtmo: Inherit from common msm8960 proprietary files

commit aecee5463eeb1e78001c9b386553f5a47cb981ae
Author: Ethan Chen <intervigil@gmail.com>
Date: Mon Jul 28 11:23:12 2014 -0700

d2lte: Move common d2lte libs into msm8960-common

* Allow apexqtmo and expressatt to inherit these as well

commit d2fdc56232745b32aca5fee7cc0fcb3511a9a503
Merge: 9338358 399f67a

(and then a lot more output, further into the past)

So I figure Aha! 9338358 is the handle I'm looking for. I see that 399f67a seems to get involved with earlier stuff. But now:

~/android/system/vendor/samsung $ git revert -m 1 9338358
error: Mainline was specified but commit 933835865d048a653979cd7a66df7320779e94cc is not a merge.
fatal: revert failed

So that's not it. Incidentally, the root of these changes seems to be a phone called "piranha", for what it's worth.

Especially the second commit touches something like 100 files, so I don't think I want to take that one on by hand.

Over in the Relay developer's forum (where I can't post, at least not yet, because I'm not a developer) I see "tdm" possibly picking up for the Relay. Since I can't post I sent him a PM thanking him and letting him know that I'm interested in helping.
[Samsung Galaxy S Relay 4G] scotte9999:
I don't understand. I just did "git revert aecee5463eeb1e78001c9b386553f5a47cb981ae" in vendor/samsung and it reverted without incident.

Because you're not a developer? WTF? I didn't know XDA had such rules (I'm not a developer by any XDA mark, so far as I know, and can post in that forum). Anyway, looks like [MENTION=4126377]tdm[/MENTION] is making progress, so hopefully he can share what he did to get the build sort-of working.
[Samsung Galaxy S Relay 4G] Magamo:
He needs to have had at least ten posts to post unrestricted in the dev forum.
[Samsung Galaxy S Relay 4G] phred14:
I got it to work. The clue was your git command. Looking at the directions you pointed me to, I thought I needed a "-m 1" in there between the "git revert" and the commit number. Then but it told me I needed to do a git stash or commit for my local changes before I could do the revert. I hadn't thought I had changed anything, but figured a "git stash" wouldn't hurt. Then both reverts worked, and I captured all output for later reference.

After that I built another rom image, which had today's date, even if it's from the same repo sync as my first image. Now I have two things I can directly compare. I also took tarballs of the vendor/samsung directories, both ways.

Not enough time tonight, but hopefully this weekend I can try my first image. Of course I'll also keep an eye on how tld(?) is doing. He's no doubt further along than me, but I can at least test for him.

(This is my 11th post, so maybe I'll add something there, based on what he says next.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] duoblade:
So i was trying to find some new roms for my SGH-i747M and what i did was backed up my original rom running on a avatar nightly build i tried to upgrade my clockworkmod touch to the latest version using the terminal method (cause i was getting status 7 errors from all the other roms). I finally got the install the work then when i reboot the rom doesn't work i tried going back into CMW recovery and it just crashes and for some reason the computer can't recognize the phone so i can't unbrick it.... what do i do now totally scrub
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goddie392:
Have you tried odin

Hey try downloading the stock firmware and used Odin flash it on
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
What stock ROM was on your phone before you update CWM? It's important to let us know so we can help guide you in the right direction.

Can you get into download mode at all? Have you tried the debrick method described in this forum?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] duoblade:
tried everything(mostly)

I've tried odin and stock rom but the thing is i don't think my usb debugging is on so odin and my computer can't access the components inside the phone, i've tried unistalling drivers and trying to reconnect it but no luck... my stock rom on my phone was a avatar 4.0 nightly build or something (4.3 version) and my old CMW was 6.0.3( or something before i tried to get the 6.0.4) now i can't even get it to work when i tried to flash the slimkat rom

i can't get into CMW recovery.... when i try it restarts, when it restarts all i get is a black screen i think i'm screwed here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Try different drivers, cables and usb ports. Usb debugging only matters when you are booted into android. Shouldn't have any effect on download mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Can you get into download? From what I recall with my phone USB debugging was not needed to flash ROMs via Odin or CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] duoblade:
i've tried

i've tried different port different cables different computers i've tried reinstalling the drivers and using different installations nothing seems to be making the phone readable, and yes i can get into download mode but odin or the computer can't detect which port it is on
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
How are you reinstalling drivers? You have to uninstall through device manager. And make sure your cables are data cables. Many out there are not capable of data transfers. Unless the port on the device has gone bad or been damaged, I'm not sure what else you can try. But if it cannot connect on any port on any computer, I think it may be a hardware issue like I just mentioned.

Did you try different driver versions? You can get several from the link in my sig.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
What about trying different operating systems (i.e. WinXP, Win7, OSX, etc.)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Could be worth a shot. Odin is Windows only though. I think heimdall works for the rest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] duoblade:
try what i can

i've tried switching between the two operating system(windows 7(labtop), windows 8.1(desktop)) don't seem to be working neither have worked i tried installing the driver again on windows but the phone still can't read if anything imma try this method http://xdaforums.com/showthread.php?t=2549068 but idk what the results will yield w/e take what i can get btw idk where the samsung driver would be in device manager at least the general heading if it doesn't show up at all...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] duoblade:
wow wtf

never mind guys it was the usb cable it's weird its the stock cable that came with the s3 and it didn't work it was only after i used my bros s4 mini cable that it started to read it wtf...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Cables go bad far more easily and frequently than most people believe. Glad you figured it out!
[General Paranoid Android Discussion] abdurrahmanyildiz58:
hello ben samsung galaxy ace 2 gapps I encountered this problem when installing on phone

unmounting system..

aborting ...

e. error in / storage /sd card 1 / pa gapps stock 4.4.4n 20140620 sinned (status) installation aborted

lütfen yardım edin
[General Paranoid Android Discussion] Pirateghost:
Ask in the gapps thread....

#stayparanoid
[Micromax A110] ponnex:
just want to ask if kernel version affect proximity sensor? mine not working on kitkatian v3 an v2 and other custom ROMS
[Micromax A110] kundan.lohar:
ya kernel affects proximity
[Sony Cross-Device General] Rajeev:
Friends

Here i am sharing you another sexy custom theme named " Moto Love " for devices running Android 4.3+ with a rooted , deodexed and superuser mod installed. I don't know it will work with non-rooted devices. Just test it by your self. Please note. This is not my work. I am just sharing it here. Full credit goes to the original developer.

This theme having some awesome animations. I am sure you will love this new animations... And if u can't find transparent navigation and status bar in 4.3 devices means its not because of the theme. Its because of your SystemUI. Only one bug is call dialer number is not really visual. But its adjustable. And if you don't like this theme means u don't need to comment here. Just leave it as it is..

SCREENS

DOWNLOAD

Click Me !

INSTRUCTIONS

Install It As A Normal APK.

CREDIT

| lolex |
[Sony Cross-Device General] Prabu Fx:
Looks Sexy Nd Cool !

:cool:
[ONE Q&A, Help & Troubleshooting] [armitage]:
Well to be honest you are not wrong there.

Even with the latest fixes (latest .xml) it's still kind of a hit and miss with the "OK Google" command on the OnePlus One.

But, as you probably know, there is already a thread for this issue.

Maybe a friendly mod could move our to posts over there and merge them. :)

http://xdaforums.com/oneplus-one/help/fix-ok-google-low-microphone-problem-t2828980/page3
[ONE Q&A, Help & Troubleshooting] Heisenberg:
If you want your post moved you need to report it. The mods don't just rifle through threads looking for things to do.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] [armitage]:
Well this is weird.

I did not open this thread, someone else did.

I was just making the second post in it and I was telling the OP that there already is a thread for this issue.

Then I reported the thread with an explaination, why it should get moved.

Now I wake up and the OP's post is gone and mine is still here and now I'm the OP. :D
[Ornate TrueSmart] walscobry:
owner icon and name missing from pull down menu. There is no ME contact at the top of the list in the people app. So I guess that this is not the stock 4.2 people app.

How can I set up my profile (the option in the stock app) to get the ME contact?
[Galaxy S 5 Q&A, Help & Troubleshooting] Sizer:
I was wondering if it was possible.to stream movies stored my s5 to an ipad and if so how. I'm hoping to save myself having to buy a 12v tv for my camper!
[JAMin, XDA Neo, S200 Software Upgrading] andrew_sh:
ftp://ftp.xda-developers.com/Upload...4_2207114_024721_QTEK_WWE_Ship_GREEK2.2.0.rar

Use at your own risk

For educational reasons only.
[JAMin, XDA Neo, S200 Software Upgrading] Evans_Prophet:
Andrea thank you SOOOO much! Just a quick question. I updated yesterday (after 7 months) to the Qteks latest WWE rom - (2.20.7.34WWE) 7/10/06

Radio: 2.47.21

ext rom: 2.20.7.114.

So two questions:

a. Is the Greek version newer?

b. Can I have English system menus (I hate the Greek ones) but be able to write Greek on the Phonepad? (this is the only reason I want Greek - I understand that there is no Greek T9 anyway)

Thank you so muh once again!

Vangelis
[JAMin, XDA Neo, S200 Software Upgrading] andrew_sh:
a. It's excactly the same version as the one you mentioned.

It just adds greek support

b. Yes, this is what I do
[JAMin, XDA Neo, S200 Software Upgrading] vasvas:
Andrea I Cannot Enter To Ftp Can You Is There A Reason Can

Youuploaded Somewhere Else ???
[JAMin, XDA Neo, S200 Software Upgrading] Jesterz:
correct link:

ftp://xda:xda@ftp.xda-developers.co...4_2207114_024721_QTEK_WWE_Ship_GREEK2.2.0.rar
[JAMin, XDA Neo, S200 Software Upgrading] Evans_Prophet:
Thank you both! Pitty is, that I just upgraded on Saturday (after 6 months!)...

Btw, do you know what should I back up in order keep only:

a. SMS

b. Call history?

Thank you once again..
[JAMin, XDA Neo, S200 Software Upgrading] Evans_Prophet:
Hi again.. I tried to install the rom, but I ended up with the rainbow screen. Thus, back to the latest qtek rom..

Any ideas?
[JAMin, XDA Neo, S200 Software Upgrading] andrew_sh:
Try this

1) extract nk.nbf using typhoonnbfdecode or a similar one

2) flash 8002000-os.nb using awizard

You will still need to transfer ext.rom and radio rom manually.

If anyone knowledgeable is willing to create an executable for g4, go ahead because i don't have a g4 device.
[JAMin, XDA Neo, S200 Software Upgrading] g.lamprou:
Greek G4 rom

Have anyone G4 greek rom? Plz answare.....
[JAMin, XDA Neo, S200 Software Upgrading] ntinos69:
link not work,please give us the new Greek rom for qtek s200
[JAMin, XDA Neo, S200 Software Upgrading] andrew_sh:
ftp://xda:xda@ftp.xda-developers.co...4_2207114_024721_QTEK_WWE_Ship_GREEK2.2.0.rar
[JAMin, XDA Neo, S200 Software Upgrading] gptg13:
I would like to thank you. I am downloading right now the rom and I will test it tomorrow.
[JAMin, XDA Neo, S200 Software Upgrading] gptg13:
me too and I have a G3 version
[JAMin, XDA Neo, S200 Software Upgrading] gptg13:
I installed the 2.2.0 english version and that saved the day.

Andrea can you please tell me what went wrong?
[JAMin, XDA Neo, S200 Software Upgrading] andrew_sh:
I realy don't know.

I've flashed it thousands of times on g3 models. i've also flashed it many times on g4 models but with aWizard.

What I would do in your case, is to extract the nbf and flash it with aWizard.
[JAMin, XDA Neo, S200 Software Upgrading] Gerigo-Greece:
Andrew,

can you be more detailed on the two steps above?

I am sure some of us if not all will be indebted to you.

Thanks in advance.
[JAMin, XDA Neo, S200 Software Upgrading] Pzachar:
Links dead

Can someone reupload this rom? because the links are dead.. Thanks
[JAMin, XDA Neo, S200 Software Upgrading] the_ar:
Here it is....

http://www.badongo.com/file/2539929

Andrew
[JAMin, XDA Neo, S200 Software Upgrading] pwillis94:
S200 Greek Extrom Only ?

hi is it possible to have just the frrek extrom? I want to try it on wm6 pdaviet 4.0.0.0.6 touch firmware!!!! or if someone kane cook that rom with greek support!!!!!!!!!! many thanks