Hello everyone, i saw something weird with omni torch privacy and device access .Have a look at the attachments below .
Now can @XpLoDWilD @pulser_g2 explain this ???
I recommend omni users to disable these access or remove this app until omnirom devs fix this . There MIGHT be more apps like this
I guess most of these permissions are not need for the app to work. Correct me if I'm wrong.
Sent from my Nexus 4 using Tapatalk
CallMeAldy said:
I guess most of these permissions are not need for the app to work. Correct me if I'm wrong.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
yes .
there hell lot of apps out there take cm torch for exactly it's better than omnitorch in terms of privacy but it also have camera access (images and videos) . below is cm torch permissions .
Sent from my Nexus 4 using Tapatalk
percy_g2 said:
yes .
there hell lot of apps out there take cm torch for exactly it's better than omnitorch in terms of privacy but it also have camera access (images and videos) . below is cm torch permissions .
View attachment 2794271
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I maybe wrong but i think the camera access is okay cause that's the thing which turns flash on and off, but the omni torch permissions are way beyond acceptance.
Sent from my Nexus 4 using Tapatalk
CallMeAldy said:
I maybe wrong but i think the camera access is okay cause that's the thing which turns flash on and off, but the omni torch permissions are way beyond acceptance.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
yes :good: right , but omnitorch is taking too much access
percy_g2 said:
yes :good: right , but omnitorch is taking too much access
Click to expand...
Click to collapse
The developers should have a say on this as soon as possible. Those permissions could be a mistake too let's see.
Sent from my Nexus 4 using Tapatalk
Um, please don't claim that this is OmniTorch. It isn't.
Why?
OmniTorch is preinstalled with Omni, if you're installing it, then obviously you got it from some unofficial source.
https://github.com/omnirom/android_packages_apps_OmniTorch/blob/android-4.4/AndroidManifest.xml
You will see that OmniTorch is not requesting any of those permissions. The only permissions in the manifest are:
CAMERA (this is needed to control the LED on many devices)
WRITE_SETTINGS
WAKE_LOCK (many devices behave badly if the device suspends when torch is on)
BROADCAST_STICKY
You can also look at the source code to see everything that OmniTorch actually does, and there isn't anything there that could violate your privacy.
Entropy512 said:
Um, please don't claim that this is OmniTorch. It isn't.
Why?
OmniTorch is preinstalled with Omni, if you're installing it, then obviously you got it from some unofficial source.
https://github.com/omnirom/android_packages_apps_OmniTorch/blob/android-4.4/AndroidManifest.xml
You will see that OmniTorch is not requesting any of those permissions. The only permissions in the manifest are:
CAMERA (this is needed to control the LED on many devices)
WRITE_SETTINGS
WAKE_LOCK (many devices behave badly if the device suspends when torch is on)
BROADCAST_STICKY
You can also look at the source code to see everything that OmniTorch actually does, and there isn't anything there that could violate your privacy.
Click to expand...
Click to collapse
first of all i used omnitorch android-4.4 branch from omnirom github .
i have checked the source's and i know what you are trying to say .
"
OmniTorch is preinstalled with Omni, if you're installing it, then obviously you got it from some unofficial source."
really ???? funny statement . actually you knowm what we can open the omnirom zip and strip out OmniTorch.apk from it .
try your self and i'm done helping out.
and yeah don't tell me that you can't install it in your next post . push it to system/app and rw-r-r .
thank you.
Sent from my Nexus 4 using Tapatalk
Entropy512 said:
Um, please don't claim that this is OmniTorch. It isn't.
Why?
OmniTorch is preinstalled with Omni, if you're installing it, then obviously you got it from some unofficial source.
https://github.com/omnirom/android_packages_apps_OmniTorch/blob/android-4.4/AndroidManifest.xml
You will see that OmniTorch is not requesting any of those permissions. The only permissions in the manifest are:
CAMERA (this is needed to control the LED on many devices)
WRITE_SETTINGS
WAKE_LOCK (many devices behave badly if the device suspends when torch is on)
BROADCAST_STICKY
You can also look at the source code to see everything that OmniTorch actually does, and there isn't anything there that could violate your privacy.
Click to expand...
Click to collapse
APK from the LATEST mako nightly.
Maybe this should satisfy you, I'll leave everything here now.
Sent from my Nexus 4 using Tapatalk
CallMeAldy said:
APK from the LATEST mako nightly.
Maybe this should satisfy you, I'll leave everything here now.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
see still instead of checking and explaining the cause of it ,he just(XDA SRD LOLOLOL) replied with his silly answers.
I actually i saw the sources and asked for explanation .
percy_g2 said:
see still instead of checking and explaining the cause of it ,he just(XDA SRD LOLOLOL) replied with his silly answers.
I actually i saw the sources and asked for explanation .
Click to expand...
Click to collapse
We shall wait for the OMNI developers to have a final say on this
Below screenshots are from Official Mako nightly omni-4.4.3-20140611-mako-NIGHTLY.zip
my friend says it might be because
omnitorch runs on system user id ,so it has same permissions as any shell logged as system .
Now i'm really surprised with omnirom dev (Entropy512) attitude .
did you guys do it to avoid chmod of sysfs in every device ?
percy_g2 said:
Below screenshots are from Official Mako nightly omni-4.4.3-20140611-mako-NIGHTLY.zip
my friend says it might be because
omnitorch runs on system user id ,so it has same permissions as any shell logged as system .
Now i'm really surprised with omnirom dev (Entropy512) attitude .
did you guys do it to avoid chmod of sysfs in every device ?
Click to expand...
Click to collapse
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.
Entropy512 said:
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.
Click to expand...
Click to collapse
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.
Sent from my Nexus 4 using Tapatalk
percy_g2 said:
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.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
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.
Entropy512 said:
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.
Click to expand...
Click to collapse
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.
Sent from my Nexus 4 using Tapatalk
CallMeAldy said:
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.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
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.
Entropy512 said:
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.
Click to expand...
Click to collapse
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
Sent from my Nexus 4 using Tapatalk
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 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?
percy_g2 said:
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
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
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.
Related
Found this thread reading through the Fascinate subforum, they had this stickied, for good reason.
Here's the original thread: http://forum.xda-developers.com/showthread.php?t=977154
Rodderik said:
Who is affected? All phones pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post or use one of the alternate methods down there
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Link to publishers apps here. I just randomly stumbled into one of the apps, recognized it and noticed that the publisher wasn’t who it was supposed to be.
Super Guitar Solo for example is originally Guitar Solo Lite. I downloaded two of the apps and extracted the APK’s, they both contain what seems to be the "rageagainstthecage" root exploit – binary contains string "CVE-2010-EASY Android local root exploit (C) 2010 by 743C". Don’t know what the apps actually do, but can’t be good.
I appreciate being able to publish an update to an app and the update going live instantly, but this is a bit scary. Some sort of moderation, or at least quicker reaction to malware complaints would be nice.
EDIT: After some dexing and jaxing, the apps seem to be at least posting the IMEI and IMSI codes to http://184.105.245.17:8080/GMServer/GMServlet, which seems to be located in Fremont, CA.
I asked our resident hacker to take a look at the code himself, and he’s verified it does indeed root the user’s device via rageagainstthecage or exploid. But that’s just the tip of the iceberg: it does more than just yank IMEI and IMSI. There’s another APK hidden inside the code, and it steals nearly everything it can: product ID, model, partner (provider?), language, country, and userID. But that’s all child’s play; the true pièce de résistance is that it has the ability to download more code. In other words, there’s no way to know what the app does after it’s installed, and the possibilities are nearly endless.
Click to expand...
Click to collapse
The offending apps from publisher Myournet:
* Falling Down
* Super Guitar Solo
* Super History Eraser
* Photo Editor
* Super Ringtone Maker
* Super Sex Positions
* Hot Sexy Videos
* Chess
* ????_Falldown
* Hilton Sex Sound
* Screaming Sexy Japanese Girls
* Falling Ball Dodge
* Scientific Calculator
* Dice Roller
* ????
* Advanced Currency Converter
* App Uninstaller
* ????_PewPew
* Funny Paint
* Spider Man
* ???
Click to expand...
Click to collapse
http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
Now, on to some more details of the virus. We should point out that this vulnerability was patched with Gingerbread, meaning any device running Android 2.3+ should be fine. In other words, if you’re looking to play the blame game (which I’m not, but having read all the comments on the original post, many people are), then there’s plenty to go around. The hole was fixed by Google, but it’s relatively useless since many phones aren’t yet running a version of Android that is protected. It’s noteworthy that some manufacturers released updates that patched the exploit for devices without updating to Gingerbread; unfortunately, it appears that minority is quite a small one.
Perhaps most important is the question of what infected users can do about their situation; unfortunately, the answer is not much of anything. Because the virus opens up a backdoor and can bring in new code at any time, the only way to really rid an infected device of any damage is to completely wipe the device – not exactly the optimal solution, but it looks like the only one available, at least for now.
Finally, Justin notes that ROM developers working with pre-Gingerbread versions of Android can prevent the virus from backdooring in code by putting a dummy file at /system/bin/profile.
Click to expand...
Click to collapse
As you can see androidpolice.com reports on this backdoor and roots and steals personal information. The apps are removed from the market but that doesn't mean they got them all. Attached is a flashable fix as suggested by androidpolice.com
So users can flash this .zip or simply create a blank file called profile and place it in /system/bin/ (developers are encouraged to include this file in future releases. A blank file is not going to affect performance at all)
Alternate methods:
Using 'adb shell' or terminal emulator (should work on any ROOTED phone) as suggest by xaueious here
Code:
$ su
su
# remount rw
Remounting /system (/dev/stl9) in read/write mode
# touch /system/bin/profile
# chmod 644 /system/bin/profile
#
Alternate 2:
Download blank profile file from here (or create one and name it profile)
Use a program like Root Explorer to copy it to /system/bin/
Then longpress on it and check the permissions should be read/write for user, read for group, and read for others.
Alternate 3:
cyansmoker has put together an apk for the patch here https://market.android.com/details?id=com.voilaweb.mobile.droiddreamkiller
Thanks for pointing this out photoframd and androidpolice.com for investigating and reporting!
UPDATE: I renamed the .zip file and reuploaded it (350 hits wow). Also in the edify scripted version I added 644 permissions to the file (but if you already flashed it then it should have defaulted to that). I also added a pre-edify version of the patch thanks to xaueious for people using a recovery that does not yet understand edify.
Click to expand...
Click to collapse
thankyou for bringing this to our attention.
Fretless said:
thankyou for bringing this to our attention.
Click to expand...
Click to collapse
I second that! many thanx!
Of course. It surprised me that I hadn't seen this earlier.
I've already committed this to the Incredible S rom base, I suggest other devs do so as well.
How would someone without root plug the hole??? or does this only effect the root users?
The Malware uses rageagainstthecage to root the phone, then does all the dirty work. So I'd guess that it would leave your phone rooted.
Apparently the infected phones are already clean according to Google. They have a way to remote wipe the affected app from your phone and clean up any traces it left, as well as hopefully plugging the whole in the process.
So wait..... I had Cyanogen 7 RC1 running.... And I had Spider man (infected app) installed.... but since then I've changed roms....
Since RC1 is 2.3 am I safe???
Zerox8610 said:
So wait..... I had Cyanogen 7 RC1 running.... And I had Spider man (infected app) installed.... but since then I've changed roms....
Since RC1 is 2.3 am I safe???
Click to expand...
Click to collapse
Well, seeing as the article says that the vulnerability only applies to pre-gingerbread roms, yes. You are safe.
wdfowty said:
Well, seeing as the article says that the vulnerability only applies to pre-gingerbread roms, yes. You are safe.
Click to expand...
Click to collapse
Google pushed out an market update with the mal-ware plug a couple of days after the problem showed up. i forgot where i read the article and if i find it i will post.
the apps that had the back door sniffer built in were reversed engineered and the made the patch according to there findings.
synisterwolf said:
Google pushed out an market update with the mal-ware plug a couple of days after the problem showed up. i forgot where i read the article and if i find it i will post.
the apps that had the back door sniffer built in were reversed engineered and the made the patch according to there findings.
Click to expand...
Click to collapse
I think it's one of the articles linked in the original thread qoute.
wdfowty said:
I think it's one of the articles linked in the original thread qoute.
Click to expand...
Click to collapse
lol. yeah your right. i should have checked the op before speaking.
Lol it's all good
Kinda unclear? Ifi have cm7(2.3) and installed one of those apps am i good?
sent from dinc
Rom-Addict said:
Kinda unclear? Ifi have cm7(2.3) and installed one of those apps am i good?
sent from dinc
Click to expand...
Click to collapse
As they said, the problem is for any software version below Gingerbread. And since you're running GB (2.3), you don't have to worry about it. You're safe.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
changed the title to ease the confusion...
that sucked, that spider man game was actually kinda cool ;P
Zerox8610 said:
that sucked, that spider man game was actually kinda cool ;P
Click to expand...
Click to collapse
I believe it was a developer that kanged an app, and smali'd in some malicious code. Just use gingerbread or a rom with a dummy /system/bin/profile
I noticed this bug within an hour of running 4.4.1 last November. Now it seems that main stream android news experts, lol, have noticed too.....
http://www.androidpolice.com/2014/03/07/bug-watch-stopping-apps-on-android-4-4-2-can-silently-kill-related-background-services-a-fix-is-on-the-way/
"Google's own apps are unaffected". <<<< This tells all.
I personally think it's a disgrace that this 'bug', cough cough, was ever let through 'testing', cough cough again, and how long it's taken to be acknowledged.
edit.. basically imo, this makes 4.4.2 a broken OS
meangreenie said:
I noticed this bug within an hour of running 4.4.1 last November. Now it seems that main stream android news experts, lol, have noticed too.....
http://www.androidpolice.com/2014/03/07/bug-watch-stopping-apps-on-android-4-4-2-can-silently-kill-related-background-services-a-fix-is-on-the-way/
"Google's own apps are unaffected". <<<< This tells all.
I personally think it's a disgrace that this 'bug', cough cough, was ever let through 'testing', cough cough again, and how long it's taken to be acknowledged.
I'll just wait now for the 'shills' and 'Google fairies' to tell us how this 'bug', damn I've got a bad cough, doesn't affect their phone.
Click to expand...
Click to collapse
Found the change they made that I guess caused the issue:
https://android.googlesource.com/platform/frameworks/base/+/ddc19e9
New change to fix it:
https://android.googlesource.com/platform/frameworks/base/+/2ed1e93bc963c8b779481a1db2d9f0bec8039907
This bug does cause issues. It's something I've seen a lot and more noticeable with gaming and long up times on my devices.
Is there a way to get this new activeservices.java file and incorporate into stock 4.4.2 rom manually?
As you mention.. this bug causes many problems
edit.. from my limited understanding we just need an updated am.jar file with the fix?
It seems still not merged in here or am i wrong?
https://android-review.googlesource.com/#/c/81970/
Even if it could be already fixed in google internal branch, and not yet on AOSP
Anyway I found it absurd how much google care about some kinds of bugs..Its a little bug that can have a lot of annoiance for a user and google doesn't care at all to fix it as soon as possible..there are tons of other bug under the hood, that are ignored since years...
yeah, looks like Google have not verified it.. hmmm
anyway I found the activeservices.java file in services.jar... might have a go later on my pc with apktool and change that one line of code
though last time I messed with that tool it didn't like my 'amd' pc and borked the keys from framework resources file.. it was a year and a half ago or so, hope I can remember how I got it working
Do any of the custom ROMs here have the fix mentioned above?
Is this why most of the 3rd party apps I close remain "running" with 0.00B instead of caching the process?
It has been happening with Google apps as well. GPM and Hangouts for instance, which still manages to sleep through messages sometimes.
Sent from my Nexus 5 using Tapatalk
I had always wondered if this was a bug or done on purpose. Noob question, but can these "0 byte" processes also have an effect on battery?
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
bblzd said:
Is this why most of the 3rd party apps I close remain "running" with 0.00B instead of caching the process?
It has been happening with Google apps as well. GPM and Hangouts for instance, which still manages to sleep through messages sometimes.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same thing with google plus. A lot of the roms I've been using (omni, purity) have fixed that issue it seems. Some others haven't however.
Sent from my Nexus 5 using xda app-developers app
It's good to hear custom roms have this fix.
I'm running stock 4.4 atm to avoid the error. It's nice to have apps such as bbm working properly again, without the fear of missing notifications.
Anyone has any ideas to jailbreaking chromecast?
bisbal said:
Anyone has any ideas to jailbreaking chromecast?
Click to expand...
Click to collapse
Chromecast has been rooted. You have to have specific devices, as Google locked the device down and is unrootable after a certain point. Check to see if your serial number is listed in the "Rootable Serial Numbers" thread, and make sure you've never updated it over WiFi, as it will automatically install Google's updates and render your device locked permanently. All of this information is covered extensively in the threads around this one you started, use the information that is present.
http://forum.xda-developers.com/showthread.php?t=2537022
http://forum.xda-developers.com/showthread.php?t=2529903
http://forum.xda-developers.com/showthread.php?t=2578653
Also Google has open sourced Chromecast's API's so anyone can develop app support for it. The question is what you plan on doing once you root/jailbreak it. Whatever it is will still require development and app support.
borxnx: Thanks, but I already knew that, obviously I am talking about the *NEW* devices that have a protected bootloader! :-/
xlxcrossing: I knew all that too, I am not asking for API's or anything else, I am specifically asking for jailbreaking and being able to install my own ROM!
bisbal said:
borxnx: Thanks, but I already knew that, obviously I am talking about the *NEW* devices that have a protected bootloader! :-/
xlxcrossing: I knew all that too, I am not asking for API's or anything else, I am specifically asking for jailbreaking and being able to install my own ROM!
Click to expand...
Click to collapse
At the very least @rekids is working on a hardware method...
http://forum.xda-developers.com/showthread.php?t=2746636
http://forum.xda-developers.com/showthread.php?t=2698446
http://forum.xda-developers.com/showthread.php?t=2703327
I'm sure there are other threads, but that was just a quick few-minute search.
Likely you won't see anything open-public until it actually works, as it's a cat-and-mouse game with Google. Tip your hand early and Google could just roll out an update to stop you before the exploit is usable by a significant number of folks.
Maybe its because the exploit was patched very early but i fail to see any benefit from rooting.
And i say this as someone that used to flash 5 ROMs a week.
This device is very limited and i doubt root would allow much
Sent from my One X using Tapatalk
drivenby said:
Maybe its because the exploit was patched very early but i fail to see any benefit from rooting.
And i say this as someone that used to flash 5 ROMs a week.
This device is very limited and i doubt root would allow much
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Yet... Now Team Eureka has added native screen cast. That's definitely a bonus. Say that again in a year, after the chromecast2 comes out and Google changes everything, again.
Sent from my SCH-R530U using Tapatalk
borxnx said:
Yet... Now Team Eureka has added native screen cast. That's definitely a bonus.
Click to expand...
Click to collapse
It's more like early access for that, as it should get released to all (supported configurations) once Google declares it ready.
IMO, Team Eureka's web panel adds a whole lot, but I'm the type that likes control over things like DNS and being able to remotely reboot things.
-= this post enhanced with bonus mobile typos =-
I am quite sad that only those in the US got chance to root on early devices.
Im in the UK and just bought mine but cant install custom roms.
Hope some genius finds a workaround.
Presuming no Xposed framework will ever be available for Android N or later, what hardware would you buy today? I will not run an Android version without Xposed (due to the need for XPrivacy). Therefore, I seek opinions on the best available, future-proofed hardware to run Xposed. For example, it seems I should still be able to buy a new OnePlus 3T, nuke the Nougat it presumably ships with, and "upgrade" down to Android 6 w/ Xposed. I doubt that path will be an option with later hardware releases.
What's the best, cutting edge Xposed-compatible hardware—presuming I might still be running it 5 years from now?
None.
Also hardware isnt the issue. Software is.
A one plus will stipl run great after 5 years.
But probably new security issues will arise and there won't be bug fixes to those things from anyone.
Maybe there will be other alternatives to exposed, but personally speaking, my current nexus 6 wipl be my last smartphone.
I will either not use one in the future or simply continue using this phone until it dies.
Appart from being utterly disgusted by the regression of technology (removable batteries gone, headphone jacks gone, lack of support),
I also cant stand the privacy issues.
shadowcore said:
hardware isnt the issue. Software is.
Click to expand...
Click to collapse
I disagree, unless you were making a reference to Wirth's law. My Nexus 5 crawls today in comparison to how it ran years ago, and I'm constantly short on RAM when I wasn't in the past. Most of this is the bloat caused by apps. It will help, of course, that the OS wouldn't be upgraded.
A one plus will stipl run great after 5 years.
Click to expand...
Click to collapse
I also perform the hardware repair on my N5 myself, so that's a factor. Things like battery replacement come into play after years of use.
But probably new security issues will arise and there won't be bug fixes to those things from anyone.
Click to expand...
Click to collapse
That's effectively where I'm at now. The OTAs won't apply, and I don't care enough to go through the gyrations to update the OS with the patches.
organophosphate said:
I disagree, unless you were making a reference to Wirth's law. My Nexus 5 crawls today in comparison to how it ran years ago, and I'm constantly short on RAM when I wasn't in the past. Most of this is the bloat caused by apps. It will help, of course, that the OS wouldn't be upgraded.
I also perform the hardware repair on my N5 myself, so that's a factor. Things like battery replacement come into play after years of use.
That's effectively where I'm at now. The OTAs won't apply, and I don't care enough to go through the gyrations to update the OS with the patches.
Click to expand...
Click to collapse
Agreed I have Nexus 5, Redmi Note 3, Redmi Note 4, Moto G5 Plus, Mi5 at home
Nexus 5 feels ancient now though I love the form factor and the occasional times when it runs smooth off late
Im guessing EMMC might be degrading
Then I should buy more Android Phones, at least one for shopping, one for apps at sixes and sevens. I am in China and most of the apps don't want to obey the rules...
Plus: less pleasure for personalizing
Guys !
Please keep on topic and refrain from xposed lifespan assumptions , the OP is asking for a different opinion
thread cleaned and be nice one with the other
thanks for understanding
Dan - forum moderator
you pretty much already have my suggestion.... a OnePlus 3T. since you seem to need xposed (imho, just move on) all new phones will obviously be shipping with android 7.xx+, the 3T is the best phone to get. i doubt there will be an update to xposed so eventually you will need to update and its obvious that later android version will have superior memory management to make use of the 3T's memory.
if by chance, xposed does somehow live you will still be left with a great phone that is only further made better by whatever android version is available. a few weeks ago i helped several classmates switch ROM's. they all bought 3T's due to my recommendation. all are very happy. i suggest you get one while they are still available. i hope this helps! cheers!
droidbot1337 said:
you pretty much already have my suggestion.... a OnePlus 3T.
Click to expand...
Click to collapse
Thanks.
since you seem to need xposed (imho, just move on)
Click to expand...
Click to collapse
Well, I *need* XPrivacy and not only is that dependent on Xposed but I subsequently found out that development likely won't support anything later than Marshmallow. So, that's where I'll be indefinitely until someone replicates that.
they all bought 3T's due to my recommendation. all are very happy. i suggest you get one while they are still available. i hope this helps! cheers!
Click to expand...
Click to collapse
It does. Thanks. The largest concern is battery replacement, as it seems there are no genuine replacement batteries. Maybe that will change in a few years, though.
Well, I *need* XPrivacy.......
Click to expand...
Click to collapse
well, if privacy is your concern their are many apps that can help. your familiari with AFWall+ so there's that. you could also use Island by Oasisfeng. i mostly use it to hide my friends titpics and my snapchat, kik accounts but the app will eventually be able to do so much more.
i dont know what type of privacy concerns you have but a firewall should be enough unless your either a spy or just paranoid.
The largest concern is battery replacement....
Click to expand...
Click to collapse
you can find parts for this phone with an easy google search. i purchased a replacement screen for a friend that accidentally dropped her 3T from a balcony at school.
i truly suggest you move on to N. soon there O will be released and with it so many worthwhile features. if your lucky enough to get the chance to use it i suggest you do and not pass due to the lack of xposed. while i agree that xposed is great, its not worth passing over on updating to a better android release.
btw, now that there has been more info on the 1+5, i suggest you wait. give island a try and then i hope you go for the 1+5. cheers!
droidbot1337 said:
well, if privacy is your concern their are many apps that can help. your familiari with AFWall+ so there's that.
Click to expand...
Click to collapse
In addition to XPrivacy, I'm already using AFWall+, AppOps Xposed, and an always-on VPN.
you could also use Island by Oasisfeng. i mostly use it to hide my friends titpics and my snapchat, kik accounts but the app will eventually be able to do so much more.
Click to expand...
Click to collapse
Cool, I'll check it out for consideration to be added it into the mix. Thanks.
i dont know what type of privacy concerns you have but a firewall should be enough unless your either a spy or just paranoid.
Click to expand...
Click to collapse
A firewall is necessary but insufficient due to in-band privacy leaks. I require XPrivacy to intercept calls and feed apps fake data. There is really no substitute for Xposed for this type of approach; you may remember PDroid and how clunky that was.
you can find parts for this phone with an easy google search.
Click to expand...
Click to collapse
Hm. I was unable to find a genuine OnePlus 3T battery. I found a few obviously counterfeit batteries from dodgy ebay vendors, but I would certainly appreciate it if you could point me to a source for a genuine new replacement battery for a 3T.
i truly suggest you move on to N. soon there O will be released and with it so many worthwhile features.
Click to expand...
Click to collapse
Thanks for sharing your perspective, but I'd rather not have a smartphone than to go without XPrivacy or its equivalent. I certainly need XPrivacy a lot more than I need some new UX. I already disable all the "cool" creepy google **** like google now cards and I deny the google app access to my mic & location (well, location services is disabled altogether, but you get the point). My smartphone on MM does what I want it to do, and I really don't need it to do anything more—especially if it comes at the cost of losing the fine-grained control over apps one has via XPrivacy.
Hijacking the thread, since you posted some nice alternatives. What about us that can't live without Amplify and Greenify?
FenrirMX said:
Hijacking the thread, since you posted some nice alternatives. What about us that can't live without Amplify and Greenify?
Click to expand...
Click to collapse
Greenify doesn't require Xposed to work, just for the "boost" features. It works just fine on my 6P running 7.1.2, which means I have no Xposed.
another thread hijack since someone mention xposed module alternatives
can someone create a thread specifically list down all the alternatives for xposed modules? I am switching to S8 which is nougat only so I need to find alternatives for my xposed modules
- app settings: no alt
- appopsxposed: no alt
- boot manager: no alt
- nekosms: samsung default messaging app block feature (although not as complete)
- rootcloak: magisk
- xtouchwiz: manually deal with csc xml
Garock said:
another thread hijack since someone mention xposed module alternatives
can someone create a thread specifically list down all the alternatives for xposed modules? I am switching to S8 which is nougat only so I need to find alternatives for my xposed modules
- app settings: no alt
- appopsxposed: no alt
- boot manager: no alt
- nekosms: samsung default messaging app block feature (although not as complete)
- rootcloak: magisk
- xtouchwiz: manually deal with csc xml
Click to expand...
Click to collapse
Does Magisk directly replace Rootcloak? Doesn't Magiskhide only hide Magisk, not root?
ldeveraux said:
Does Magisk directly replace Rootcloak? Doesn't Magiskhide only hide Magisk, not root?
Click to expand...
Click to collapse
Magisk hides its root.
josephcsible said:
Magisk hides its root.
Click to expand...
Click to collapse
Right, not SuperSU though.
ldeveraux said:
Right, not SuperSU though.
Click to expand...
Click to collapse
not sure but I thought magisk hide will also hide root from other apps
but you're correct, magisk hide needs magisksu and cannot work with supersu
Okay, here we go...
Hey!
After about a month of endless cycle of try & scrap designs I think I'm ready present my redesign of the Magisk Manager. At this point I have covered every main screen that you (user) will come in contact with, now it's time to start implementing (or rather rewriting) code from the old app to the new one.
Don't get me wrong, I'm far away from from done; but! I have a sneak-peek of what's to (hopefully) come - considering John will ultimately accept my pull request, lol.
Rationale:
I'm an android (app) developer by occupation and I use Magisk almost every day. I love my work and everything I do, so I decided to help John with a redesign - so the app is less generic and additions (as far as features go) are easier to implement with less of a boilerplate. I have no idea if anybody would even care about the redesign so I would love to hear your thoughts!
At work I'm kinda more appreciated as a developer than a designer so I was never actually allowed to design any production app.
Structure:
The apk is work of about 10 days and roughly 40 commits.
It's mainly written in Kotlin (yey!) with a help from databinding, which makes everything much cleaner.
On top of that I use a "framework" which is actually more of a anti-boilerplate collection of libraries (jetpack wrapper) for all Android stuff - such as activites, fragments, viewmodels and interaction between them. (Can't post links since >that's whatchu get for mainly using reddit< I guess.) Nevertheless bye bye recyclerview and viewpager adapters, bye bye littering code with animations and other UI stuff.
Warning:
Few of my friends reported that the app is marked as malicious by Google Play Protect, maybe because it contains johns original package name + "debug". I know what it looks like, new user, no posts, malicious app warning. Meh. It's not, build it from source, inspect it on GitHub if you don't trust me.
Also it contains Manifest permission for connecting to the internet - this is not implemented yet and does not connect to anything. Everything you see is offline mock data or your own installed apps. Again, inspect source if you don't trust me.
It might crash on APIs<21 due to some unresolved xml setters and usage of vector resources. I'll fix that once everything else is done, don't mind that.
Some visual bugs might occur, refrain from reporting it please.
This is just a preview. DESIGN PROTOTYPE
Screenshots:
https://imgur.com/a/BRd40cg
Download:
NO DOWNLOAD. Already working on a official manager. Stay tuned.
Source:
https://github.com/diareuse/magisk
So what now?
Well, tell me how you like it!
What really bothers you in the new redesign that could be changed for the better?
What do you really like?
And yeah! almost forgot. I was wondering if redoing preferences would be better or worse. Do you prefer standard (support library-based) or entirely custom (with the super fancy dialog ripped from Android Q that you can preview while selecting Dark Mode in settings)?
I really like the redesign of the app. You should definitely get in touch with the Magisk dev to take it up a notch and implement it in the official app.
Sent from my ONEPLUS A3003 using Tapatalk
CrashOverride1995 said:
I really like the redesign of the app. You should definitely get in touch with the Magisk dev to take it up a notch and implement it in the official app.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Thanks I appreciate that!
I was trying to but he seems to successfully ignore all of my PMs here or on Reddit. I can only imagine how much spam is he getting so I don't blame him
diareuse said:
Thanks I appreciate that!
I was trying to but he seems to successfully ignore all of my PMs here or on Reddit. I can only imagine how much spam is he getting so I don't blame him
Click to expand...
Click to collapse
Try to use Twitter, he seems active there.
Sent from my ONEPLUS A3003 using Tapatalk
Nice work:good:
How does this work when it comes to hiding MM?
hshah said:
How does this work when it comes to hiding MM?
Click to expand...
Click to collapse
The whole app does not work yet see OP. This is just a design prototype.
Hiding will be probably somewhat tricky, I have no idea how will the new code features reflect in john's hiding mechanism.
Check PM mate, sent the code for your download to be a word link :good:
Honestly I feel in love with the design. I think John should adopt the design. You and John together can make some more modifications and bring this design (or improved) into official versions. Nice work bro, highly appreciate it.
Looks really nice, very in keeping with the new oneui. The newest official is really dated looking with too much advertising. Looks like a dang NASCAR lol I themed 6.0.0 for myself and just used that apk since pure black or pure white
Hi i just install the app on my rooted pixel 1gen running android Q i like the design but i dont know why i cant see the modules and should i uninstall the original magisk app ?
diareuse said:
The whole app does not work yet see OP. This is just a design prototype.
Hiding will be probably somewhat tricky, I have no idea how will the new code features reflect in john's hiding mechanism.
Click to expand...
Click to collapse
I know @topjohnwu doesn't really enjoy the app development part of Magisk, so having someone improve on it is likely gonna be appreciated. But, you absolutely have to make sure that you do not break features like hiding the Manager... That is a key feature that has taken a lot of work to implement and has to work.
Kurtlestat said:
Looks really nice, very in keeping with the new oneui. The newest official is really dated looking with too much advertising. Looks like a dang NASCAR lol I themed 6.0.0 for myself and just used that apk since pure black or pure white
Click to expand...
Click to collapse
Wait, what? Advertising? There's no advertising in the Magisk Manager...
Didgeridoohan said:
Wait, what? Advertising? There's no advertising in the Magisk Manager...
Click to expand...
Click to collapse
Sorry I just meant the links etc on the home page.
I use adaway and haven't seen an advert in years ?? this is my effort on v6.0.0 (pic) no previous experience in android at all, so not too bad ?
ParadoxTheDevil said:
Honestly I feel in love with the design. I think John should adopt the design. You and John together can make some more modifications and bring this design (or improved) into official versions. Nice work bro, highly appreciate it.
Click to expand...
Click to collapse
I think "should adopt" sounds like you'd force him to do so. That's not what I'm trying to do though I can only propose and it's completely up to him whether he accepts it or nah.
Didgeridoohan said:
I know @topjohnwu doesn't really enjoy the app development part of Magisk, so having someone improve on it is likely gonna be appreciated. But, you absolutely have to make sure that you do not break features like hiding the Manager... That is a key feature that has taken a lot of work to implement and has to work.
Click to expand...
Click to collapse
As far as I can tell, the hiding mechanism relies only on renaming package name within the system so the app should be just fine. Reflection that is used within my version will probably not be touched.
But I'd be sad to scrap the whole work if the hiding does not work - nevertheless if it pulls through with the community (and it seems like it) I'll make my absolute best to make the transition as seamless as possible. That's why I created separate module which can be built alongside the current version for (hopefully short) transition period.
My intention is of course not to break sh*t, but to improve on design and functionality of current app. Would be really d*ck move to do otherwise, I think.
I just did this in art app, changed the green header/footer colours to black and white and put radio buttons instead of checkbox. The colour scheme looks a little more like the oneui. You could maybe get a hex colour picker and get the proper colours and do it more professionally. Keep up the awesome work by the way.
Omg this is fancy as f**k
If this would also allow us to use AROMA like on flashfire am i totally in! Great Redesign!
Oh damn, this is beautiful redesign! I love it very much.
Kurtlestat said:
Looks really nice, very in keeping with the new oneui. The newest official is really dated looking with too much advertising. Looks like a dang NASCAR lol I themed 6.0.0 for myself and just used that apk since pure black or pure white
Click to expand...
Click to collapse
Advertising? Everything there is needed for functions.
madbat99 said:
Advertising? Everything there is needed for functions.
Click to expand...
Click to collapse
I would guess he's probably taking about the social media links at the bottom of the main screen. Which are not actually advertising anything but linking places to access support and updates.