yashsingh1/xdaforums huggingface dataset:
[General Omni Discussion] Entropy512:
Well, you're claiming that we're invading your privacy when if you look at the sources, it's obvious we're not.

You claim there's a privacy problem - show me where in the source we're collecting information. Put your money where your mouth is.

The shared system UID might be causing some weird display issues - but there are lots of system apps with those permissions. If it is your belief that users should disable OmniTorch merely because of the shared system UID even though you can look at the source and see that there is no privacy issue, then you need to remove the kernel, the frameworks, the HALs. Oh wait, you'll have nothing left.
[General Omni Discussion] percy_g2:
looks like you don't deserve to hold SRD .

1. I didn't say/write that omnirom is collecting user data.

2. If you don't have any proper explanation then don't reply

3. Now coming to your point ,in indirect way you are saying every system app should have all permissions which are not needed .

Great explanation and please don't reply now , it's better if someone with more knowledge explain it.
[General Omni Discussion] Entropy512:
You said, and continue to maintain, that there is a privacy issue. For there to be a privacy issue, data collection has to be occurring.

Is data collection occurring? NO. Therefore there is not a privacy issue.

Also, for the time being, those permissions are needed, otherwise torch crashes when accessing the sysfs nodes to control torch on devices that need it. (we can't do shared system UID on a per-device basis). https://gerrit.omnirom.org/#/c/3758/ would be the preferred solution if it worked, but it doesn't.

Is there a potential security risk? Maybe, if someone were to somehow "attack" Torch. It's pretty easily to analyze the intent handler to determine if a torch enable/disable broadcast could be used for "other" purposes though.

Is it ideal? No. I would prefer to figure out why the above gerrit commit doesn't work as expected but I haven't had the time.

But you've come here and are claiming there is a privacy issue and that everyone should disable/remove Torch because of some arbitrary privacy issue THAT DOES NOT EXIST.

The whole premise of your thread is that there is a privacy issue, but:

THERE IS NO PRIVACY ISSUE. IF THERE IS ONE, PROVE IT. SHOW WHERE THE DATA COLLECTION OCCURS.
[General Omni Discussion] CallMeAldy:
Please don't waste your 'precious' time here. Somebody else could surely explain things in a better way and not assume that anyone is blaming omni for collecting data.

Cheers.
[General Omni Discussion] Entropy512:
See the title of this thread. "privacy issue". Also see percy's recommendation that people remove/disable the app because of this "privacy issue"

"privacy issue" means that data is being collected that shouldn't be collected. He has no proof that anything of the sort is happening (because it isn't happening!) but he immediately stated that everyone should be removing this app because of "privacy issues"

If he weren't coming here trying to gain glory as a whistleblower and a name for himself, he would've fixed the commit referenced above, or merely asked what the rationale was for the shared system UID. No, instead, he came here claiming there's a huge privacy issue and everyone should remove the app.
[General Omni Discussion] percy_g2:
thanks for explanation

now some of my points

1. I asked for explanation from omnirom devs instead of posting funny post you could have posted this earlier.

2. I wrote " users please remove those access or remove omnitorch app until omni rom devs fix it" because there are many unofficial ports and someone might take advantage of omnitorch app permission issues . (There are many Way's to take advantage without letting user's know about it as official torch app already have those permissions ).

3. You guy's can learn how cm managed to avoid the issues you are having .

4. For future learn how to explain and post .Someone who hold SRD doesn't reply like this .

" OmniTorch is preinstalled with Omni, if you're installing it, then obviously you got it from some unofficial source."

This ^

5. I'm not here to bash and claim anything .

learn to accept your mistakes .

THERE IS POTENTIAL RISK and again thank you for explanation
[General Omni Discussion] gigsaw:
Guys please calm down :) xda is a community, we are here not to fight each other but we are here to learn. So, if you see a problem, why don't you try to fix it? Omnirom is an open source project, so everybody can help. I am not an expert and I only think that omnirom is one of the few projects really carefull about the privacy and security, so would be strange that they collect informations trough the torch app :p I'm not here to argue but I would like to try, from my little point of view, to guess a "solution": If I disable the not needed torch's permissions trough the settings menu, would it be a good idea?
[General Omni Discussion] Entropy512:
It makes no sense that someone would install an APK that is already there. The only sensible explanation for someone "installing" OmniTorch is that they're trying to replace it with something.

And you didn't ask for an explanation, you came out and said there was a privacy issue and people should remove/disable the app.

Your comment about unofficial ports is nonsensical - There's no way to take advantage of the permissions issues without modifying the app. If they're modifying the app, they're either distributing it as a standalone APK - in which case the user should be proceeding with care, or they're distributing it as part of a prebuilt firmware package - and there are plenty of far better ways to violate someone's privacy (like adding hooks to the frameworks themselves) if someone is distributing a complete package.

Or another way of saying it is: When it comes to privacy/whatever, all bets are off if you're flashing a complete system firmware package, since that includes a kernel (e.g. whoever provided you the package can obtain kernel-level access to do whatever they wish with your device). If you don't trust whomever provided the package, you shouldn't be using ANY component of it. There is no way that OmniTorch can be used to invade privacy that can't be more easily done in another way by someone with nefarious intent.
[General Omni Discussion] percy_g2:
1. I didn't mention to disable . I wrote remove app or disable not needed permissions .

2. I don't wanna make any name for myself . mod edit- comments removed, I asked for explanation .

3. I don't wanna commit to OmniROM ( Personal Reasons ) , i posted this for an explanation and i think OmniROM user's must know about.

4. Look at your posts again what you replied to me first.

Now Stop posting your assumptions about me as i made myself clear in above points .
[General Omni Discussion] percy_g2:
1. Read my first post again "Now can XpLoDWilD pulser_g2 explain this ???"

2. I already showed Official Nexus 4 Omni ROM latest Nightly privacy guard ss of OmniTorch not needed permissions. There is a fault and if you can't attack using OmniTorch then don't think other can't also.

I'm done wasting my time explaining you .
[General Omni Discussion] Entropy512:
1) Still, you are telling people to remove the app when there is no justification for doing so.

2) BS. If your intent was to ask for an explanation, your post would have been, "Why does the package have a shared system UID? Could this be abused?" - But you didn't. What you did is come out and say there was a privacy issue and everyone should remove the app - even though there is no privacy issue and no reason for people to remove the app. Since you refuse to commit to Omni, it's clear that you don't want to have a positive role in improving it and came here to stir up trouble/drama.

3) Must know about what? Nothing? You have yet to indicate any way in which this can have any negative effect on a user, except if someone takes our source and modifies it. If they do that, they can modify it to do whatever they want - even if we removed the shared system UID, someone could readd it and add privacy-invading features to OmniTorch in an unofficial build, although that would be a poor/inefficient way of doing it - easier to just modify the frameworks or an APK that already has (and requires) access to the data in question like the dialer (plenty of ways someone could abuse privacy with a hacked dialer...)
[General Omni Discussion] Naddict:
Passing through, members are reminded that respect in the debate and discussion of development is an expectation and a rule here.

Be civil, lets not start making this personal....
[General Omni Discussion] CallMeAldy:
Just to cut this crap short.

He just said to disable the permissions not to disable the app.

He wanted a clear explanation from someone with good knowledge, unfortunately he got a reply from you which made things even more complicated cause of your assumptions.

His point was if not OMNI then somebody else could exploit this and get access to everything with a bad intent and hence he posted everything here so incase OMNI developers ain't aware of it they could take necessary actions.

Cheers ;)
[General Omni Discussion] maxwen:
Oh how I missed all of those "XDA drama queens" :)
[General Omni Discussion] tilal6991:
I'm not sure if either of you two are understanding Entropy512's point.

There's two points to consider:

1. Would people be able to exploit this prebuilt app directly? No because of the way Android permissions/framework works, no other app would be able to access/exploit these permissions.

2. OK suppose we disable the permissions. Would sort of barrier would that put up to stop other from distributing bad APKs? Absolutely none because it would be one line of code to add back in.

So in either case it's meaningless to talk about removing the sharedSysteUid. If we do that, we lose access to sysfs which would break torch which is obviously bad news for a torch app. Either that or we can ask for root in which case we could do a lot worse than even these permissions.

EDIT: BTW this is the commit which you might want to look at https://github.com/omnirom/android_...mmit/c09f5b47ddaec430b9d0e0d11131301935110203
[General Omni Discussion] Entropy512:
BS. "or remove this app" is right in his initial post. e.g. if you can't disable the permissions, he is telling users to remove the whole app.

He is telling users to remove the app with NO VALID JUSTIFCATION WHATSOEVER for doing so. The subject line of the post is worded so as to get users scared there's a privacy issue by implying there is one - when there isn't.

He also posts a pile of scary-looking permissions screens that no users will ever see in a normal scenario because it's a preinstalled system app which you'd see for other apps like KeyChain and Settings, claiming there's a privacy issue because of these screens. By his logic for claiming there's a privacy issue with OmniTorch and that users should remove it, there's a severe privacy issue with Settings and users should remove it too. If it's preinstalled in system, it could do anything and the user would never know. If you're flashing a complete system firmware package, you have to trust that whomever is publishing the package doesn't have nefarious intent because when you flash a complete package to /system - whatever you flashed has complete control to do whatever it wants.

Don't forget that the frameworks don't even get granted permissions - because they're the ones GRANTING the permissions. If someone putting out an unofficial build wanted to invade your privacy, that's where they would put the code, not in Torch. Torch is a poor place to put something like that because even with the extra permissions, it's harder to access a lot of the information.

Also, as I've said before, unofficial builds, just like official builds, contain a replacement kernel. Disabling OmniTorch because someone MIGHT put bad code in there in an unofficial build is just nonsensical - because the build also contains a kernel and if the kernel can't be trusted, GAME OVER.

Or another way of saying it: If someone wanted to compromise an unofficial Omni build with privacy-invading code - they would be utter idiots if they did it by putting the offending code in OmniTorch. Telling users to remove OmniTorch if they can't disable its permissions if they don't trust the source of the package is completely ridiculous. If you can't trust the person to provide a non-compromised OmniTorch, why are you trusting them to provide a non-compromised kernel or frameworks?

He now claims he just wanted an explanation - but his entire post is crafted/worded to scare users and prey on their fear and ignorance.
[General Omni Discussion] percy_g2:
Yeah i saw that commit , BTW how CyanogenMod is avoiding the issue Omni torch is having without using share system user id ?

I want to know more about this issue nothing more .

Please ask Entropy512 to be more civil and edit his post . BS BS everywhere ,i know what BS means .
[General Omni Discussion] percy_g2:
You didn't even knew when i posted the first post that OmniTorch is using shared system user id , your silly posts showed what's your knowledge .You Directly said its not official app then when i showed the official app and told it's using shared system user id might be the cause of it. Then you started picking on me .

If you want me to go on then come at me but just think like an mature person which you aren't judging by your previous post's .So STOP no one is asking about your assumptions , if you want to explain then do it in proper way or else don't . If XDA is a place to fight then go on.
[General Omni Discussion] maxwen:
most prolly chmod 666 the sysfs file or even make it

world writable in the kernel

so you dont know how Entropy512 is related to omni? :cool:
[General Omni Discussion] Naddict:
Can't be nice or respectful to each in replies and posts + have to be childish in replies and make XDA look like it is a playground with all this verbal judo + even after warning from moderating staff about said unneeded drama = Thread closed.

Be nice, or get out of XDA...pretty easy rules to follow.
[Xperia Arc Themes and Apps] alinolaw71:
hi guys.

i fix and themed xperia overlays rom to black.

i want fully make this rom fully black.

in this times i themed more apps to black.theys so prrty and increase my battery life.

just i cant themed phonebook.(i themed phone book succss but not worked)

i themed to black dialer but i cant themed phone book.

if any body can do this help me in for this.

phone.apk and semcphone.apk for who want help.

.
[Xperia Arc Themes and Apps] alinolaw71:
screenshot :

for more screenshots click here

.
[Xperia Arc Themes and Apps] pepitoff:
What did you exactly fixed in XO ROM?

I have a copy of it, but I like white more...
[Xperia Arc Themes and Apps] allanlhdz:
Bro upload this settings in white version with color themes for xperia overlay rom please :) thanks in advance
[Xperia Arc Themes and Apps] alinolaw71:
I will do this.

.
[Xperia Arc Themes and Apps] Quisland:
Hello,bro

Can this semcphone.apk work on mike's cm11 rom?

And I hope that you can make a port of white semcphone for mike's CM11 ;)
[Xperia Arc Themes and Apps] yash989:
can anyone give me xperia overlay ROM link
[Xperia Arc Themes and Apps] allanlhdz:
Deleted

---------- Post added at 06:35 PM ---------- Previous post was at 06:34 PM ----------

Is available in xperiaoverlay.com and is pay, shared download links broken the rules of xda forum, a user shared links and moderators of forum removed links because is a pay and is posted without permission of developer.

---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------

When you upload settings with theme accent color?

Thanks in advance!
[Xperia Arc Themes and Apps] Quisland:
So sad to see it FCs on Mike's CM11 :(

Maybe it is in need of some files,but I actually can't find any solutions...
[Xperia Arc Themes and Apps] Ambor:
Bro try to change these values: in styles.xml

for semcphone

Theme.DeviceDefault.Light to: Theme.DeviceDefault

Theme.DeviceDefault.Light.Dialog to Theme.DeviceDefault.Dialog

change this:

<style name="incall_top_button" parent="@android:style/Widget.Button">

<item name="android:textAppearance">?android:textAppearanceSmall</item>

<item name="android:textColor">#ffffffff</item>

<item name="android:gravity">center_vertical</item>

<item name="android:padding">0.0dip</item>

<item name="android:layout_width">0.0dip</item>

<item name="android:layout_height">fill_parent</item>

<item name="android:layout_weight">1.0</item>

</style>
[Xperia Arc Themes and Apps] alinolaw71:
bro i hvnt problem with semcphone i just problem with phonebook.

.
[Xperia Arc Themes and Apps] Ambor:
<style name="PhoneDialogWhenLarge" parent="@android:style/Theme.DeviceDefault.Light"> to Theme.DeviceDefault etc

heme.DeviceDefault.Light.Dialog to Theme.DeviceDefault.Dialog

change this

<style name="incall_top_button" parent="@android:style/Widget.Button">

<item name="android:textAppearance">?android:textAppearanceSmall</item>

<item name="android:textColor">#ffffffff</item>

<item name="android:gravity">center_vertical</item>

<item name="android:padding">0.0dip</item>

<item name="android:layout_width">0.0dip</item>

<item name="android:layout_height">fill_parent</item>

<item name="android:layout_weight">1.0</item>
[Xperia Arc Themes and Apps] allanlhdz:
Any news bro?
[Xperia Arc Themes and Apps] alinolaw71:
bro just w8 soon coming new version of xperia overlay with theme support
[Xperia Arc Themes and Apps] pepitoff:
Are you sure?!?! Because I'm not sure that this new version will be realised. As you know today is 29th but still nothing :D
[Xperia Arc Themes and Apps] allanlhdz:
Nothing news of update in Facebook fan page!
[Xperia Arc Themes and Apps] allanlhdz:
V2 of xperia overlay don't have theme support :(
[Xperia Arc Themes and Apps] alinolaw71:
ok bro i will share my theme acent
[Galaxy S 4 Q&A, Help & Troubleshooting] terminator1983:
Can someone share qcn file for s4 i9505 4.4.2.

Thanks
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] 0v3rl0rd:
Hi,

I entered the recovery menu on my i9195 with volum up + home + power, and there is no sign of knox.

I have the following displayed:

Android system recovery (3e)

Volume up/down to move highlight:
power button to select.

reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache

and below that menu there is:

" MANUAL MODE "
-- Appling Multi-CSC...
Applied the CSC-code : VIP
Successfully applied multi-CSC.

How should I check for KNOX?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Razvan:
Enter in Download Mode with V- - Home - Power ans see if your knox was tripped.

Read this thread: http://xdaforums.com/showthread.php?t=2750744
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] 0v3rl0rd:
Hehe, tnx dude ;)

I owned Nexus'es before, and the default recovery was with V+,., tnx ;)

Knox still untouched, awwww :D
[Samsung Galaxy Mini] kr1pt:
So, my uncle gave me bricked phone (basicly, he could only boot to recovery and download) so I installed stock 2.3.6 from sammobile through Odin. I also installed new CWM through odin aswell. But phone not won't boot to recovery. I use every single button combination, but won't.

I get CWM logo with Samsung logo but nothing happens after that.

EDIT: Can somebody move this thread to Mini 2
[Android Q&A, Help & Troubleshooting] Dirili:
Hope those are enough buzzwords for everyone else to find that thread.

Long story short, I'm looking for an android upgrade for my runbo x5+. Had an old defy for ~5 years now and quarx, that crazy son of a *****, always kept me up to date. Bless his soul. Downgrading to 4.0.4 really feels weird now.

So, if anyone else out there got a ranbo x5+ with an up to date android, please, enlighten the plebs. An URL would be enough, I can google the rest. Thing is, I find nothing about my x5+. And paid too much to just throw on CyanogenMod 10.1 and hope it doesn't break my ****.

Love and kisses! <3
[Android Q&A, Help & Troubleshooting] Dirili:
Just a friendly bump. Theeere.
[Android Q&A, Help & Troubleshooting] HTCDreamOn:
What's the difference between the runbo x5 and the x5+ king, is it completely different hardware? There's a root exploit for the x5 but no roms i can see, but if all the drivers sources etc. Were released you could build CM yourself as long as you had root.
[Android Q&A, Help & Troubleshooting] Dirili:
It's sturdier, slightly bigger screen with a slightly higher resolution, slightly better buttons, rest's mostly cosmetic.

-> outdoor-handys . com / runbo-x5-vs-runbo-x5-plus

How do I build my own CM with root?

edit: different / newer firmware and drivers, too.
[Android Q&A, Help & Troubleshooting] HTCDreamOn:
http://true-android.blogspot.co.uk/2013/12/how-to-root-runbo-x5-running-on-android.html try this, it's a one click root app so hopefully it won'tvbreak anything but instead will tell you if it will work or not

If the specs are exactly the same aside from the screen, then if the x5 already has CM then it should be easy. If it doesn't then you're stuffed, especially if there are no driver sources either.
[Android Q&A, Help & Troubleshooting] Dirili:
That captcha's really getting on my nerves.

It's rooted, framaroot 1.7 did the trick. 1.8 might work, too. 1.9.x doesn't work.

Just to get it straight, as long as my phone is rooted, I can simply slap on any CM and be fine? 'Cause my old defy needed some really specific nightly builds.
[Android Q&A, Help & Troubleshooting] HTCDreamOn:
No, you can't just slap it on. What I'm saying is that if the x5 has CM then you can port the source code easily or zipkang it even more easily. You might need an unlocked boot loader as well anyway. Search for device trees, kernels, drivers, etc. and if you can find that then there's a hope. If not then it's impossible.
[Xperia Z2 Q&A, Help & Troubleshooting] rmig825:
Since I have used the sony Z2 on us T-Mobile I have not seen the phone roam at all. Here is where my question is. Last Sunday I was fishing in international water and I noticed I lost signal about 12 miles off shore. My friend who had an Att phone still had signal. At one point I did a "mobile network" check. Roaming was checked off. And then when I searched verizon and att both came up but it would not let me connect to any of those networks. So it is almost like the phone will not let me roam. Am I missing something? Is there a way to check for international roaming? Is it because my phone is rooted with boot loader unlocked. Or is this something with t mobile. Phone model is d6503 and I am on the simple choice (credit check) plan. I will be traveling internationally throughout the year and I want to make sure I am not going to have any issues connecting to networks. Thank you in advance for your help on this
[JAMin, XDA Neo, S200 General] DoCtOr_X:
My Charmer is stuck at bootloader due to prophet ROM.

Now its having G4 SPL on G3 chip.

i am unable to get DOC Unique ID and witout it when I insert SD it says "Download not allowed"

What should I do?

Is there anyway to convert (90000000-IPL_1.nb) from origional ROM to a BIN file so that I may be able to use I c:\.....bin.

Thanks in advance.

Or any other suggestion............?????
[One (M8) Q&A, Help & Troubleshooting] KinetiClutch:
Hi All.

Having an issue with Bluetooth and the Music Player.

Basically, if I click play it only plays like 5 seconds then cuts off and disconnects from bluetooth and then re-connects but then doesn't play.

Spotify works flawlessly over bluetooth.

Is there an inherent issue? Does it clash with Google Play Music?

Any ideas?
[Galaxy S 4 Q&A, Help & Troubleshooting] Albe95:
Someone know where is located the overflow icon for some of the Samsung apps?

Inside the singular apk I didn't find anything so probably PNG for overflow is inside some framework apk.
[One (M8) Q&A, Help & Troubleshooting] muppetmaster916:
Is there a way to change the touch sound, that pop/click is terrible
[One (M8) Q&A, Help & Troubleshooting] vosg:
Just replace /system/media/audio/ui/effect_tick.ogg with something you like more.

Note that you'll need root.