yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] daleski75:
I believe you have to wait for s-off so you can downgrade hboot to remove that message.

Flashing back the stock firmware (RUU) will remove the tampered but it will always say relocked if you locked the bootloader again.
[One (M7) Q&A, Help & Troubleshooting] Spacky03:
What does S-off mean? Sorry I'm really new to this, I know it's probably a dumb question. Is going back to the factory firmware a long process?
[One (M7) Q&A, Help & Troubleshooting] Funkym0nkey:
Tampered can be removed when you flash the official RUU.

Relocked cant be as of now. And I have no hopes for it to happen in device's life cycle as well.
[One (M7) Q&A, Help & Troubleshooting] Spacky03:
So how would I flash it? Is there a general way or is it device specific?
[One (M7) Q&A, Help & Troubleshooting] Orcworm:
Take a look through this:

http://xdaforums.com/showthread.php?t=2265618
[One (M7) Q&A, Help & Troubleshooting] vegetaleb:
When you rooted your phone it added tampered and unlocked in bootloader menu.

If you want to take them out you will have to unroot your phone or wait for s-off (it will fully unlock the phone)

I didn't have the tampered message on my rooted OneX,it must be something new as well as the red warning in booting the phone that it's a dev phone that must not be sold :eek:
[One (M7) Q&A, Help & Troubleshooting] Funkym0nkey:
There is a thread with RUU archive for each device. Check for specific RUU for your specific carrier make or model.

But if you install RUU you will have phone that is as good as stock phone. You will lose root and will have to re-root it.

Dont bother with it unless you have to go back to factory condition.

There are also zipped versions of stock ROMs available so you can try those if you have CWM or TWRP installed successfully.

You dont really need to remove that tampered / unlocked status. It does not hinder your phone in any way. You have already lost your warranty and even if you relock your bootloader and remove Tampered message by flashing factory RUU, your phone will still show RELOCKED message. So point going back unless as I said you must have factory condition phone.
[One (M7) Q&A, Help & Troubleshooting] TrueYears:
Hi~!

So does this mean the factory will always know that our phones are rooted with S ON?
[One (M7) Q&A, Help & Troubleshooting] daleski75:
Yes HTC will know for sure the phone has been tampered with and unless s-off is achieved for the masses which does not involve taking the phone apart then it will always say tampered, unlocked, relocked.
[One (M7) Q&A, Help & Troubleshooting] TrueYears:
Oh, okay, thank you, my phone has vibrating problems, with the intensity, in some hits, the vibrating just keeps going slowly fading in. I read somewhere that 1.29 fixes this but its isnt out around my region yet and I dont want to flash this 1.29 stock rom to find out its a hardware issue and lose my warranty
[One (M7) Q&A, Help & Troubleshooting] joshuadjohnson22:
Security-Off if what it officially means. Means you can write to the bootloader and mod things
[Galaxy Note II Themes and Apps] jujuburi:
Download:

https://docs.google.com/file/d/0B3dAMHacbZmtNWtQOHFGYzlCb0U/edit?usp=sharing

Source:

http://www.androidpolice.com/2013/05/14/download-latest-google-play-store-4-1-6/
[Galaxy Note II Themes and Apps] cronus21:
Nice THX !

No Thanks Button here ? ^_^
[Galaxy Note II Themes and Apps] donottouch:
Is it cracked h yet????

Sent from my C6603
[Galaxy Note II Themes and Apps] EXEDROID:
No Crack Needed !

This is ORIGINAL Play Store ! :laugh:
[Galaxy Note II Themes and Apps] orsidoc:
Black?

Inviato dal mio GT-N7100 con Tapatalk 2
[Galaxy Note II Themes and Apps] jioan62:
black me to please please :laugh:
[Galaxy Note II Themes and Apps] iznee:
+1
[Galaxy Note II Themes and Apps] Kney.:
For a black Play Store you just have to press the power button once after starting the Play Store.
[Galaxy Note II Themes and Apps] freco:
Worked for me [MENTION=4990334]Kney.[/MENTION] !!!

LOL
[Galaxy Note II Themes and Apps] Kney.:
Glad to hear!

This Mod kicks ass!

It woks with almost every app!

Even if its black themed already! It'll become much MORE black! :)
[One (M7) Q&A, Help & Troubleshooting] jezzba:
Want to root but.. i am worried about warranty i have rooted other phones and tablet before (HTC Legend, Sensation and Nexus 7) I just got my HTC one recently i am on a contract only thing thats keeping me away from rooting is because when i rooted my Nexus 7 the usb port actually stop working twice got it replace luckily the guy who looked at it had no clue what he was doing. How will i restore my warranty afterwards rooting
[One (M7) Q&A, Help & Troubleshooting] Guich:
If you will unlock your phone, you will lose warranty.

Because in bootloader you will have "unlocked" and "tampered".

You can delete "tampered" with an official ruu for your phone, but for the unlock you have to wait the s-off...
[One (M7) Q&A, Help & Troubleshooting] jonny68:
Even if you need to leave it back for repairs and you've unlocked the bootloader and rooted nothing will likely be said, I know as i only got my phone back last week and it had to be sent to HTC direct in the UK (bad flash ****ed up the phone) it was sent back to me with nothing said.
[Android Apps and Games] atridhr:
Hi all,

I just released my Android Live Wallpaper inspired by War Thunder, World of Warplanes and similar games. If you would like to check it you can find more info below.

And its FREE!

Link to Google Play

Bring the dogfights to your mobile phone home-screen.

Made for all fans of WW2, Planes, War Thunder and World of Warplanes games.

This is a highly interactive live wallpaper with a lot of cool features and settings. Watch some of legendary ww2 planes battle each other or engage early jet fighters.

Simply tap a plane to make it shoot. Aim other planes to damage and destroy them. Each plane can receive maximum 3 hits.

All action is followed by pretty audio/video effects. Planes can be firing deadly bullets, damaged with different smoke effects or falling down with nice explosions. Audio effects include plane shooting, hitting another plane and plane falling. Phone vibration can be activated when plane is shooting, is hit, or destroyed.

Each plane has its own random calculated path and acts differently. Maximum plane speed is configurable from settings.

This wallpaper also supports Death-Mach mode where planes will fight automatically. Only one will be the winner at the end.

By enabling a pilot ranking option, pilots will earn achievements for every enemy plane they take down.

Main features

• 22 planes (more coming)

• Sound on/off

• Clouds on/off

• Gray-scale mode

• Hight quality option

• Max Plane speed setting

• Pilot rankings (up to 18 ranks)

• Death-match mode

• Show FPS

• 7 Backgrounds (more coming)

• Custom background setting

• Vibration for shooting, hit and crash

Youtube link:

Some screenshots:

Let me know what you think of it. Any suggestions are welcome.
[Galaxy S 4 Q&A, Help & Troubleshooting] palsp:
Got my shiny s4 the other day, all working well.

Now I did get an ota yesterday, don't know if this has anything to do with my issue.

The first day I could pull down the notifications area with two fingers to get all the quick settings.

Then there was all twenty or so toggles.

Now it's just the 7 basic ones.

And I can't add more from the settings, unless there is some hidden menus...

Any help appreciated!
[Galaxy S 4 Q&A, Help & Troubleshooting] donovan2123:
I also have this issue. I had loads of toggles when first got phone then all of a sudden I only have 7. No toggle for air view, ect
[Galaxy S 4 Q&A, Help & Troubleshooting] palsp:
Okay, good to know I'm not they only one...

But what to do?

Going for root and a custom Rom as soon as there is somethin stable out there.
[Galaxy S 4 Q&A, Help & Troubleshooting] @xDeepS:
Wild guess, have you turned on Talkback under Accessibility?
[Galaxy S 4 Q&A, Help & Troubleshooting] palsp:
Nope, no talkback...
[Galaxy S 4 Q&A, Help & Troubleshooting] 380AU:
Mine all disappeared once, and I had no toggles at all.

A factory reset brought them back up again.
[Galaxy S 4 Q&A, Help & Troubleshooting] palsp:
Did you root and backup?
[MDA, XDA, 1010 Software Upgrading] Musicmaster:
I downgraded my XDA to 2002 inorder to unlock it. i like 02, but i noticed my battery life now goes down 30-50% every day, were with 2003, it went down 20-30% in a week (with no usage, or very little for both). also, the phone doesnt have as many features with 02'

IS THERE A VERSION OF 2003 THAT DOES NOT HAVE THE SD CARD FORMAT/CORRUPTION PROBLEM???
[One (M7) Q&A, Help & Troubleshooting] darenas:
Hello everybody. My phone is bought with contract on Orange in UK, software is 1.28.61.7, but the phone isn't carrier locked. May it be the reason why I don't get update to 1.29... with new camera update and so on? Maybe the phone may be different form international version in this way? Is there any way of making my phone to international eupopean version (if it isn;t now)? After everything i want to have my phone not-rooted, and get updates from htc ota with everybody else... Don't know, if i asked correctly and everybody understand me, but thanks in advanced anyway.
[One (M7) Q&A, Help & Troubleshooting] Guich:
Umh, also in germany O2 One aren't branded, but the update is released from O2, in fact, O2 phone can't see and don't have 1.29.401.12 version...

They have 1.29.209.xx version, i don't remeber which with precision.

However, i resolved this problem with root and flashing a custom rom :)
[One (M7) Q&A, Help & Troubleshooting] Orcworm:
EE seems to be the slowest of all the UK carriers at pushing out updates, you'll probably be waiting for another good few weeks yet. Might want to try this rom since apparently you can keep OTA updates with it:

http://xdaforums.com/showthread.php?t=2224752
[One (M7) Q&A, Help & Troubleshooting] darenas:
The link for downloading don't work odexed. Would my phone will be unrooted after that, and will get updates as everybody unbranded? And how to flash it? its my first htc, always had samsung earlier..
[One (M7) Q&A, Help & Troubleshooting] Orcworm:
If you flash stock boot.img and recovery.img it should, yeah. Coming from Samsung myself it was a bit weird getting things going initially, read through this: http://xdaforums.com/showthread.php?t=2265618
[Nexus 4 Android Development] Daniel_GT:
There have been two submissions to CM code review (31787 here and 31039 here) that have not been merged for various reasons. The first allows for sysfs gamma control (at kernel level) and the second provides an additional menu in settings containing RGB display controls and vibration settings. At present there is no support within the CM vanilla system UI settings to modify gamma values (with or without MakoParts), though there are apps (notably Faux123's) that will provide this in concert with a kernel including a sysfs interface that allows it. These are potentially very complex adjustments and not really of interest to the majority of device users, however there does seen to be an appetite for a slimmed down alternative. I (and others) have been cherry-picking the two code commits and using init.d to provide a simple solution, though on top of that it does seem that a GUI setting method would be of value, if only to fiddle with levels prior to settling on values to include in a boot script.

Consequently, I have extended the original MakoParts (MakoParts+ if you will!) in adding a basic 6 value gamma (amplitude) control UI within the existing 'Advanced' menu.

To implement it in your own builds you will need to;

Cherry-pick the two code review commits (see above), if you haven't already (UPDATE 24/05/13 - Use Patch Set 6 for change 31039). Alternatively, you can get them from my repo here for the kernel and here for the device. This gives you the original MakoParts and the gamma support.

Cherry-pick MakoParts+

Cherry-pick hev88's commit here (UPDATED 09/07/13 - redirected link) to allow your settings to stick following reboot.

and then make.

Gamma settings will not stick following a reboot so once you've found some you like you'll need an init.d/ userinit.d script. There's a good guide on _motley's thread here though do make sure that you refer to kgamma_r. kgamma_g and kgamma_b rather than kgamma_red, kgamma_green and kgamma_blue (those are franciscofranco's interface variables I believe).

(UPDATE 04/06/2013 - Thanks to hev88 for spotting my original omission. His commit (now 3. above) will stick your settings following reboot.)

As I mentioned, gamma control can be very in-depth and this is not intended as an alternative to a full blown control app. Saying that, there is valuable reading to be done and user comments in Ngo93's thread here and tested settings in the accompanying spreadsheet (Basic tab) here

Thanks and acknowledgement to all mentioned.
[Nexus 4 Android Development] Daniel_GT:
Evaluation Build

I have provided a download link to a (fairly) vanilla CM10.1 build of my own including the modifications - https://www.dropbox.com/s/ebb7iteqo1ov5yn/cm-10.1-20130514-UNOFFICIAL-mako.zip
[Nexus 4 Android Development] CMNein:
Have never CP'd from Github before. Using https://github.com/Daniel-GT/android_device_lge_mako/commit/8793e557c1acba7b7f951fced0a4eae25d28a6f4 as an example, after repo sync, would I do the following:

cd ~/cm10.1/android_device_lge_mako
git remote add https://github.com/Daniel-GT/android_device_lge_mako
git fetch
git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4

Cheers.
[Nexus 4 Android Development] Daniel_GT:
Easiest way is;

git fetch git://github.com/Daniel-GT/android_device_lge_mako.git && git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4

As Andrew said on Google+ you could also patch with git am... if you get really stuck you could apply the following;

git apply <your-path-to-the-attached-file>/MakoPartsPLUS.patch

All should be run from a terminal opened in your source "mako" directory. Make sure you have the original MakoParts in your source already or it won't work.
[Nexus 4 Android Development] hev88:
needs rebase now to go with new patch set http://review.cyanogenmod.org/#/c/31039/
[Nexus 4 Android Development] Daniel_GT:
I'll look at it and review. I had thought the original commit was done with changes.
[Nexus 4 Android Development] hev88:
Yeah. So did I. Just a name change really and dropped a few strings. I tried to mod your patch but I keep getting an error on strings.xml

Sent from my Nexus 4
[Nexus 4 Android Development] Daniel_GT:
On initial inspection I can't see anything fundamentally "new" in Patch Set 7 or 8. I've asked the committer for his rationale on Gerrit. I don't think there are any conflicts with any/ all recent CM commits so you should be OK if you pick set 6 (or the commits from my repo) for the timebeing until I've looked at it properly - OP temporarily updated.
[Nexus 4 Android Development] Daniel_GT:
I've compared Patch Set 6 side-by-side with 7/8 and the update does nothing more than clean up a bit (which I've already done within MakoParts+), re-base (basically reference it against the current CM repo timeline, the original is from January) and change the package name and a UI heading. I'm not minded to apply the changes to MakoParts+, I see little point in doing so until the committer tells me what he had in mind other than change for changes sake, so please either;

Stick with patch 6 and disregard 7/8 entirely. This will effect the functionality of MakoParts and MakoParts+ not a jot.

Cherry-pick the original commits from my repo as before, and forget all about this.

I've attached the two diffs if anyone wants to have a look and see what I mean.
[Nexus 4 Android Development] hev88:
im sure its not just me but it seems you have to add some code to DeviceSettings/src/com/cyanogenmod/settings/device/Startup.java in order for settings to stick on reboot:

GammaTuningPreference.restore(context);

not sure if more is needed but i just noticed today that settings today that it doesnt stick after reboot and decided i woud take a look.
[Nexus 4 Android Development] hev88:
Just made a fresh build and adding that keeps your settings after a reboot.

Sent from my Nexus 4
[Nexus 4 Android Development] Daniel_GT:
Well spotted, sometimes you get so close to these things you can't see the wood for the trees. Have you added the line via a separate commit on your own repo, and are you still using the MakoParts project name (you mentioned DeviceSettings)? If so I'm happy to update the OP with a link to your work.
[Nexus 4 Android Development] hev88:
It was a copy pasta error on my part I still use the patch you made and just now manually added the fix to survive a reboot to source code. I started to make a new patch for DeviceSettings but I got stuck on one part... I am not to great at git Lol, I got stuck on strings.xml and kinda gave up... But it is just a one line fix on top of your patch that you made.

Sent from my Nexus 4
[Nexus 4 Android Development] Daniel_GT:
OK Don't worry, I'll add the change as a new commit and credit you.
[Nexus 4 Android Development] hev88:
https://github.com/hev88/android_device_lge_mako/tree/cm-10.1-var1/MakoParts

i just added the one line to keep settings after reboot... im exploring right now trying to figure out how to git around here lol... but if you dont get to it anytime soon ill try to make your patch play nice with the most recent patch set on CM's gerrit... gotta start learning some time, this will be my new project on my days off. i just stomped out a bug on ubuntu so this will keep me occupied for the time being

#VinoIsEvil
[Nexus 4 Android Development] Daniel_GT:
OP updated.
[Nexus 4 Android Development] hev88:
sent you a pull request on github. repo works fine but it wont let me cherry-pick it my commit... might have missed something while adding commit from terminal but it builds fine
[Nexus 4 Android Development] Daniel_GT:
You have been busy! I'll have a proper look over the next few days... I don't really follow your cherry-pick problem? Are you trying to fetch from the SSH address, not the public git/ HTTPS URL?
[Nexus 4 Android Development] hev88:
i have it the same as you do on the previous page. if i remember right it said something about cherry-pick failed no HEAD?

idk i gave up on that and just forked cm, cherry-picked latest mako parts commited it to repo edited it based on your patch and just replaced cms device repo with my in my build directory now its two less cherries i have to pick before i build. like i said im still new at this whole github deal so it could just be me not being patient
[Nexus 4 Android Development] negroplasty:
Not sure if you're talking about something else but I've been cherry-picking your commit with no problem using

git fetch git://github.com/hev88/android_device_lge_mako.git && git cherry-pick 17dfcbdc60719bb0147240efcbb906f4987c95fa
[Nexus 4 Android Development] Daniel_GT:
Not sure what happened there, there should be no problem. It seems to me you'd benefit from using a local manifest, in your case something like;

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

<remove-project name="CyanogenMod/android_device_lge_mako" />

<project path="device/lge/mako" name="hev88/android_device_lge_mako" remote="github" revision="cm-10.1"/>

</manifest>

if you create a new file "x_local_manifest.xml" and put it in your ~/<path-to-source-folders>/.repo/local_manifests/ folder along with roomservice.xml you can forget all about cherry-picking and copying folders from now on. The "x" in the filename seems to be important as I believe repo reads the manifests in alphabetical order, so the CM project is added by roomservice then removed and replaced with this one... it prevents sync errors. Do remember to keep your project up-to-date with the upstream CM one, changes there will need to be merged into your fork manually as repo will not follow it anymore... it'll follow yours. If you ever want to stop and return to "stock" builds just delete x_local_manifest and repo sync... you'll be back to normal with no more fiddling required.
[Nexus 4 Android Development] hev88:
Yeah that's what I decided to do. Just seemed logical. Oh well as long as it works for everyone else I guess that is what matters. I just replaced cyanogenmods device_leg_mako line and pointed it to my repo and its been working fine

Sent from my Nexus 4

---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------

+negroplasty that's a different commit I redid my git page and have my repo inline with the latest patch set and brought Daniels inline with the latest patch set on gerrir

Sent from my Nexus 4
[Nexus 4 Android Development] Daniel_GT:
That'd do, though you will probably find over time that you need to do more and more and keeping it in one distinct file is easier to manage and probably best practice. For example, my local manifest contains the device repo, the kernel, frameworks, Linaro toolchain and I'll fairly often switch branches or add and remove projects. It's a lot easier to keep on top of things.
[Nexus 4 Android Development] negroplasty:
Getting "fatal:" bad object" when I try to CP this for some reason now...

tim@nv1-vm:~/cm-10.1/device/lge/mako$ cd ~/cm-10.1/device/lge/mako && git fetch git://github.com/hev88/android_device_lge_mako.git && git cherry-pick 17dfcbdc60719bb0147240efcbb906f4987c95fa
From git://github.com/hev88/android_device_lge_mako
* branch HEAD -> FETCH_HEAD
fatal: bad object 17dfcbdc60719bb0147240efcbb906f4987c95fa

Any ideas?
[Nexus 4 Android Development] hev88:
I got the same thing, Idk why... I just added my repos to the local_manifests And built that way. Less cherry picks that way. Its mostly stock cm too just with mako parts added

Sent from my Nexus 4
[Nexus 4 Android Development] Daniel_GT:
Looks like hev88 doesn't have that commit in his repo anymore? I think it was applied on a branch that's been deleted. Have a look in his github public activity (about a month ago) and you'll find the details.

Try

git fetch git://github.com/Daniel-GT/android_device_lge_mako.git && git cherry-pick da9ea6ec2f12fb1766b93ff122a041f04e925741

Should be the same, OP updated.
[Nexus 4 Android Development] negroplasty:
Many thanks!
[Galaxy S III Q&A, Help & Troubleshooting] mrirfan555:
Hello XDA Memeber.

i Have recently bought a used s3 from market and it is already rooted.And it has v4.0.4 and i want to update it to JB.

I am Able to Update With Samsung Kies.

Here are My Device details:

Model:GT-I9300

Android version:4.0.4

Baseband Ver: I9300BVLE4

Now My Problem Is That:

I found on some websites that my baseband:I9300BVLE4 is relates to Orange cell phone carrier.

Now i Am afraid to update because may be after update my S3 become Sim locked.I live In Pakistan

So Please Galaxy S3 Experts Help Me.Any Guidance Will Be Appreciated. Thanks In Advance.
[Galaxy S III Q&A, Help & Troubleshooting] KayKrate:
Its probably rooted , download a 4.1.2 firmware from sammobile (make sure its for i9300) and flash thru Odin :)
[Galaxy S III Q&A, Help & Troubleshooting] mrirfan555:
Thank You bro but i need to update via Kies because i have option to do that.And if i use your method to download a firmware from sammobile .which one i choose because there are too many.?
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
The firmware that matches your location and network .

Just update via Kies and read the faqs and guides .

Updates cannot lock sim .

jje
[Galaxy S III Q&A, Help & Troubleshooting] lelinuxien52:
As [MENTION=3095420]JJEgan[/MENTION] said, no link between firmware update and SIMlock.

If the phone is unlock properly (free by default or unlock with samsung codes) you have no chance (zero !) to simlock the device.

If the phone is unlock with a third-part software (like Voodoo Unlocker), an update to jelly bean will relock the phone.
[Galaxy S III Q&A, Help & Troubleshooting] mrirfan555:
Thanks to all Who Helped Me.

i have successfully updated my s3 to Jb 4.1.2 with Samsung Kies and without any single problem.
[Oppo Find 5] eliaspizarro:
here's a poll for the first CM10.2 device, vote for oppo, obviously ;)

http://xplod.fr/poll/index.php?
[Oppo Find 5] munchy_cool:
done
[Oppo Find 5] KaminoReal:
Cool and Done!
[Oppo Find 5] Linum-23:
done