Related
I am running android L on my Nexus 7 but i just wanted to know when will Xposed support the android version??
Or will it ever support android L
Android L is a preview version. So you shouldn't wait Xposed for this version. Maybe in few weeks or months we will have Android 4.5 or Android 5.0 with Xposed support :good:
Yeah.. I'm currently playing around with it a bit, trying to get adb working in root mode and stuff which makes it easier to develop.
It's indeed still a preview release, and it's a moving target (there are very strong signs that Google will update the preview before the final release). Root apps and even some normal apps don't work well at the moment. It's good that I can try what is necessary to get Xposed running, but I haven't decided yet whether I will work on a Xposed preview release for this preview ROM. I'll share some more thoughts once I had the chance to look deeper into it.
rovo89 said:
Yeah.. I'm currently playing around with it a bit, trying to get adb working in root mode and stuff which makes it easier to develop.
It's indeed still a preview release, and it's a moving target (there are very strong signs that Google will update the preview before the final release). Root apps and even some normal apps don't work well at the moment. It's good that I can try what is necessary to get Xposed running, but I haven't decided yet whether I will work on a Xposed preview release for this preview ROM. I'll share some more thoughts once I had the chance to look deeper into it.
Click to expand...
Click to collapse
if you can get xposed running in android L developer preview it will make xposed available to kitkat with art ?
PedroM.CostaAndrade said:
if you can get xposed running in android L developer preview it will make xposed available to kitkat with art ?
Click to expand...
Click to collapse
How about you just let him work on it and see how it's goes.
There's literally no reason at all to bother him with questions, when he has something new to share he will, when he doesn't those questions will be just annoying to him. Not yours personally, but the sheer amount of people bombarding him with all kinds of art related questions just add up.
PedroM.CostaAndrade said:
if you can get xposed running in android L developer preview it will make xposed available to kitkat with art ?
Click to expand...
Click to collapse
"Getting it running" is one thing, whether it's good to publish it is another question. I've had a prototype of Xposed for the ART preview in December already. Barely tested, needed manual installation, probably failing here and there, but generally it did what it should. But already back then, I've seen that Google is still working actively on improving ART. They have made huge internal changes since then. Last weekend, I made my prototype compile against the master branch of AOSP and I had to introduce lots of conditionals. That's without knowing whether it will actually work, I just changed declarations, calls etc. to avoid compile time errors.
The ART preview in KitKat and the ART almost-final in the Android L preview are different pieces of software. Maintaining support for both of them means basically twice the work, especially for testing. That, and the fact that ART in KitKat was just an optional preview (with potential bugs that may be incorrectly blamed on Xposed), makes it less likely that I will publish Xposed for the KitKat variant of ART. That's not a final decision, it depends on how ART development continues and how well I can support Android L. It's important that Xposed works fine on upcoming Android versions where ART is the only runtime. KitKat support would be a bonus if it's not too much effort to maintain in parallel.
Oh, and for everyone who thinks that posting "pleeeeease" or "you have to support it" will increase the chances of publishing something: It won't. It will just annoy me and make it less likely.
tonyp said:
How about you just let him work on it and see how it's goes.
There's literally no reason at all to bother him with questions, when he has something new to share he will, when he doesn't those questions will be just annoying to him. Not yours personally, but the sheer amount of people bombarding him with all kinds of art related questions just add up.
Click to expand...
Click to collapse
Indeed. I have received lots of hints "hey, Android L is out now" - yes, I know. So for now, I have disabled PMs...
By the way, I have just read the "How to Report Bugs Effectively" essay by the PuTTY developer. It's so true!
I just wanted to say how incredibly awesome it is that you're already working on Xposed with this early preview version of Android L. I for one am very happy with my current 4.4.4+Xposed setup, and would rather stick with that than use a newer Android release without Xposed. It's a truly great piece of software that I have come to depend on. Keep up the good work and ignore those who would try to pressure you. We can wait!
rovo89 said:
"Getting it running" is one thing, whether it's good to publish it is another question. I've had a prototype of Xposed for the ART preview in December already. Barely tested, needed manual installation, probably failing here and there, but generally it did what it should. But already back then, I've seen that Google is still working actively on improving ART. They have made huge internal changes since then. Last weekend, I made my prototype compile against the master branch of AOSP and I had to introduce lots of conditionals. That's without knowing whether it will actually work, I just changed declarations, calls etc. to avoid compile time errors.
The ART preview in KitKat and the ART almost-final in the Android L preview are different pieces of software. Maintaining support for both of them means basically twice the work, especially for testing. That, and the fact that ART in KitKat was just an optional preview (with potential bugs that may be incorrectly blamed on Xposed), makes it less likely that I will publish Xposed for the KitKat variant of ART. That's not a final decision, it depends on how ART development continues and how well I can support Android L. It's important that Xposed works fine on upcoming Android versions where ART is the only runtime. KitKat support would be a bonus if it's not too much effort to maintain in parallel.
Oh, and for everyone who thinks that posting "pleeeeease" or "you have to support it" will increase the chances of publishing something: It won't. It will just annoy me and make it less likely.
Indeed. I have received lots of hints "hey, Android L is out now" - yes, I know. So for now, I have disabled PMs...
By the way, I have just read the "How to Report Bugs Effectively" essay by the PuTTY developer. It's so true!
Click to expand...
Click to collapse
Thanks for the answer it's what imagined and I understand, I just wanted to make sure that i was right xD
You have done a really great job, and you and all of the good developers of XDA are our heroes!!! Take a beer you deserve it! [emoji106]
Any chance of a sticky and close on this thread? I was fortunate to find it quickly enough on the second page but I was checking the General and FAQ threads first for this exact info. I'm sure a lot of people are coming to see it.
Thanks for the hint. I have extended the FAQ item about ART with a link to this thread.
I use Xposed on stock GPE 4.4.4. Its great, and for my use actually better than some of the more customised ROM's. I find i dont actually want a lot of customisation, just a few things that Xposed with a couple of modules does well.
From what i am reading at the moment, ART wont be a really viable alternative until the release of Android L. Hopefully the GPE ROMs will be early releases.
So, i would think that if you choose to continue Xposed releases (if you dont the sobbing from XDA will keep you awake nights!!) then developing for Android L which NEEDS to be ART compatible, and forgetting a version for KK which can use Dalvik anyway is the way to go.
Many thanks for all you efforts.
Hi @rovo89 I have a quick petition for you. Please release your art KitKat "alpha" of xposed so somebody interested can complete it. I think that is pretty fair and it shouldn't take you too much time. Please consider it.
resadent said:
Hi @rovo89 I have a quick petition for you. Please release your art KitKat "alpha" of xposed so somebody interested can complete it. I think that is pretty fair and it shouldn't take you too much time. Please consider it.
Click to expand...
Click to collapse
You mean the source code, so interested developers can compile it themselves? I'm indeed thinking about publishing some work-in-progress code because I'm getting more and more frustrated with L (currently uninstalled it again, I need my phone). Not yet though, I would at least like to get L booting with it (if necessary with permissive SELinux). *If* I ever support ART on KitKat, then I wouldn't want to maintain two totally different codebases.
rovo89 said:
You mean the source code, so interested developers can compile it themselves? I'm indeed thinking about publishing some work-in-progress code because I'm getting more and more frustrated with L (currently uninstalled it again, I need my phone). Not yet though, I would at least like to get L booting with it (if necessary with permissive SELinux). *If* I ever support ART on KitKat, then I wouldn't want to maintain two totally different codebases.
Click to expand...
Click to collapse
Thanks for your answher, that's mostly what I meant. I read in the last page you had a prototype running in kitkat+art, so I thought you could publish that work in order for other devs to have the possibility to keep working on it if you don't want to for whatever the reason or even help you with the code. Also, it would be good for any user who wants to use it even if he knows it may fail here or there as you say.
resadent said:
Thanks for your answher, that's mostly what I meant. I read in the last page you had a prototype running in kitkat+art, so I thought you could publish that work in order for other devs to have the possibility to keep working on it if you don't want to for whatever the reason or even help you with the code. Also, it would be good for any user who wants to use it even if he knows it may fail here or there as you say.
Click to expand...
Click to collapse
Never underesimate the stupidity of the users
They will install it, run into all kinds of issues and then come complaining and whining at xda.
This will just cause issues, so I don't think it should be released in any way to endusers.
But I do think the release of the source code is a good idea when it comes with the request kindly not to share any compiled versions.
Each developer who could seriously help working in that complex field (which aren't too many I suppose) won't have a problem compiling it, so it might help in speeding up the development or producing new ideas.
tonyp said:
Never underesimate the stupidity of the users
They will install it, run into all kinds of issues and then come complaining and whining at xda.
This will just cause issues, so I don't think it should be released in any way to endusers.
But I do think the release of the source code is a good idea when it comes with the request kindly not to share any compiled versions.
Each developer who could seriously help working in that complex field (which aren't too many I suppose) won't have a problem compiling it, so it might help in speeding up the development or producing new ideas.
Click to expand...
Click to collapse
May be the stupidity is on your side! I don't have a problem to flash 98% done xposed on my KitKat and give feedbacks to the developer.
I am sure that there are many users like me who will agree to do it, don't forget that hundreds of users still using Dalvik because of xposed!
Some module won't work or other small bug isn't a reason not to use it.
So, if you think you are so smart-you are wrong!
yanleites said:
May be the stupidity is on your side! I don't have a problem to flash 98% done xposed on my KitKat and give feedbacks to the developer.
I am sure that there are many users like me who will agree to do it, don't forget that hundreds of users still using Dalvik because of xposed!
Some module won't work or other small bug isn't a reason not to use it.
So, if you think you are so smart-you are wrong!
Click to expand...
Click to collapse
Don't get me wrong, as soon as it's in a functional beta state I'm with you there, but what rovo had wasn't even close to an alpha stage afaik. At that point users feedback is hardly ever useful for developers as it's quite obvious what's working and what isn't. Here you need useful logs and no general feedback (and usually you're testing a new version every other minute, so it doesn't really make sense to make testing releases and wait for feedback).
Please don't read my post as offense, the fact that you're actually reading here means you're not in the scope of "users" I was referring to.
It's sad, but unfortunately xda(-developers) usually isn't the best place to do and discuss actual development. There are loads of people who fail to read instructions, the OP or a couple pages back before posting, which results in lots of redundant bug reports of well known problems.
The situation has improved in the last years and the staff is doing a great job at keeping it within boundaries, but still loads of development threads (see e.g. the N5 section) are getting spammed with stupid and redundant posts.
tonyp said:
Don't get me wrong, as soon as it's in a functional beta state I'm with you there, but what rovo had wasn't even close to an alpha stage afaik. At that point users feedback is hardly ever useful for developers as it's quite obvious what's working and what isn't. Here you need useful logs and no general feedback (and usually you're testing a new version every other minute, so it doesn't really make sense to make testing releases and wait for feedback).
Please don't read my post as offense, the fact that you're actually reading here means you're not in the scope of "users" I was referring to.
It's sad, but unfortunately xda(-developers) usually isn't the best place to do and discuss actual development. There are loads of people who fail to read instructions, the OP or a couple pages back before posting, which results in lots of redundant bug reports of well known problems.
The situation has improved in the last years and the staff is doing a great job at keeping it within boundaries, but still loads of development threads (see e.g. the N5 section) are getting spammed with stupid and redundant posts.
Click to expand...
Click to collapse
Ok, First of all there are always be "stupid and redundant posts", because when I see "franco kernel" thread for N4 - it's thouthends of pages, not many people will search inside to find simple answer to question like "how to flash", it's much easier to ask again and get an answer in 5 minutes.
About Rovo, I think if it works on his phone, there is no reason not to let other users WHO WANT to use the new Xposed version, again, few modules less didn't kill anyone, so f I use 5 instead of 10 modules - it's OK by me.
I tried to change to ART (ofcourse disabled Xposed), but I had to install 6 other apps instead to make phone look/work as with Xposed, I think it's not worth it, but ART working better... After 1 day I changed to Dalvik and Xposed.
In coclusion, I prefer almost ready Xposed + ART then Dalvik with 100% working Xposed.
yanleites said:
Ok, First of all there are always be "stupid and redundant posts", because when I see "franco kernel" thread for N4 - it's thouthends of pages, not many people will search inside to find simple answer to question like "how to flash", it's much easier to ask again and get an answer in 5 minutes.
About Rovo, I think if it works on his phone, there is no reason not to let other users WHO WANT to use the new Xposed version, again, few modules less didn't kill anyone, so f I use 5 instead of 10 modules - it's OK by me.
I tried to change to ART (ofcourse disabled Xposed), but I had to install 6 other apps instead to make phone look/work as with Xposed, I think it's not worth it, but ART working better... After 1 day I changed to Dalvik and Xposed.
In coclusion, I prefer almost ready Xposed + ART then Dalvik with 100% working Xposed.
Click to expand...
Click to collapse
LOL. Translated - "Give it me now! It's not fair that rovo is keeping it to himself!" No offence, but that is how your posts are coming across. There's also no need to be insulting to someone that has contributed many things to the users of this site.
The reasons for not releasing the experimental version in a precompiled easily installable state were explained clearly by tonyp. The Xposed framework is a hugely complicated project to begin with and the fact that rovo has a test version does not mean that it's anywhere near ready for end users to install on their devices. If it didn't work properly, there would be many, many people with unusable devices flooding this section complaining that rovo broke their phone. Even if the experimental framework itself worked perfectly on the multitude of devices people have, it may break some modules, which would cause complaints and headaches for the module developers, because most people wouldn't mention they were using the test version.
As for it only being released to people that agree that it may not work. What normally happens here is that people that just want the latest version apply, then disappear without ever providing any feedback apart from complaints that "It doesn't work", with no useful logs etc provided.
The source being made available is the correct way to go here. It ensures, in the most part, that only people that have knowledge and understanding of the risks involved and are able to collaborate properly with development are able to install the experimental version. Not impatient people that just can't wait to make their phone cool and don't read or search threads before modifying their expensive device.
Sent from my C6603 using Tapatalk
rovo89 said:
You mean the source code, so interested developers can compile it themselves? I'm indeed thinking about publishing some work-in-progress code because I'm getting more and more frustrated with L (currently uninstalled it again, I need my phone). Not yet though, I would at least like to get L booting with it (if necessary with permissive SELinux). *If* I ever support ART on KitKat, then I wouldn't want to maintain two totally different codebases.
Click to expand...
Click to collapse
Why don't you keep L as a secondary rom(with MultiROM)? By doing so you can test xposed on L, and then switch to kitkat when you need your phone.
Well guys, looks like Xposed for 5.0 won't ever happen.
REVISION: This edit was added on 2.13.14
The above statement was purely a joke when Xposed for LP was merely a dream. To clarify, as of now there is no ETA for Xposed. Ever. Don't ask. Stop. Don't think of it. If you ask, you shall be banned as of the words of the moderator.
I know it may be hard to read sometimes, so I started a new paragraph. If you are confused, look up. ETAs don't exist on this developer website. Thank you.
Xposed is IN THE WORKS and no, there is no beta version. If you beg to differ, post a comment. Don't flame me or anybody.
=D have a WONDERFUL, hate free day.
The full comment posted at https://github.com/rovo89/Xposed/issues/18 is:
Thanks guys. Actually, there is no need to worry about alternative approaches. It's not easy to "hack" ART in a similar way as Dalvik, but it's generally working.
What most people forget:
a) ART isn't the only new thing in Lollipop. SELinux requires a lot of extra code and even more thoughts to work around the restrictions. And 64 bit breaks the assumption that everything starts in a single process, as there are two Zygote processes now. I think it's important to consider this right from the start.
b) The actual (net) time required to write code is far away from the time that passes. It's not like I work on Xposed every evening. There are weeks when I don't look at the code at all. Yes, I do have other things in my life, and some have a higher priority. So even if something would take just a few evenings to code, it might take me a couple of weeks to actually do it. And once I publish something, you probably wouldn't like it if I took off for a few weeks.
If it was just about coding, pushing the source could be helpful. But that works best if there's already a clear concept of what is needed and an idea how this can be split up into work packages. Often it takes hours to come up with a concept that can be coded in 20 lines. Remember how many people are using Xposed meanwhile. We don't want to have some quick code that works by accident, so it's vital to think everything through carefully, and that takes time.
So yeah. It will take more time, I still don't give any ETA, but I'm quite confident that we'll have something nice some day.
Click to expand...
Click to collapse
No new "work in progress" sources = no help from other contributors. That's it.
pyler said:
No new "work in progress" sources = no help from other contributors. That's it.
Click to expand...
Click to collapse
You can probably count the people who really understand Xposed and how it works at one hand (and you'll basically have to start from scratch for lollipop).
It's not like there were hundreds of contributors in the past, so what you're trying to say here is invalid.
Yes, there would probably be some people who could help out, but keep in mind that every minute rovo is helping others to better understand what's going on isn't available for him to do some actual development (which includes research and drafting ideas).
I'm sure that any top tier dev who feels confident to actually bring xposed for lollipop forward can contact rovo anytime and get his wip code, but so far no one has spoken out.
The sad truth is that 95% of the xda users are people without any real technical knowledge - and the only thing they do is to offer to "test" something to gain access to something before it's release.
Unfortunately those testers are rarely ever needed, at least not within the core development phase, here it takes way more time to explain people what is needed than to just test it yourself.
When you're rolling something out to production and want to make sure that the last little bugs within different usage cases and configurations are squashed, sure you'll need testers, but not before.
But for now that's not the case, so it might be better to keep the unhelpful comments to oneself
KevinDixson said:
Well guys, looks like Xposed for 5.0 won't ever happen.
(To all you downers out there, its called a joke. Laugh about it. Next thread.)
Click to expand...
Click to collapse
Liar
So yeah. It will take more time, I still don't give any ETA, but I'm quite confident that we'll have something nice some day.
Click to expand...
Click to collapse
If you can't offer something better then be patient.
Primokorn said:
Liar
If you can't offer something better then be patient.
Click to expand...
Click to collapse
Just like the op stated.... Its a JOKE
He had 666 Followers and I thought it was funny and would lighten up a few peoples stress filled days. The only reason I saw this was because I was going through his posts and READING all of them to get an update as to where we stand.
KevinDixson said:
(To all you downers out there, its called a joke. Laugh about it. Next thread.)
Click to expand...
Click to collapse
I found it for you ^ since sometimes I know its REALLY hard to understand the concept of a joke.
KevinDixson said:
Just like the op stated.... Its a JOKE
He had 666 Followers and I thought it was funny and would lighten up a few peoples stress filled days. The only reason I saw this was because I was going through his posts and READING all of them to get an update as to where we stand.
I found it for you ^ since sometimes I know its REALLY hard to understand the concept of a joke.
Click to expand...
Click to collapse
Yep sorry I misread your post. I feel a little bit stressed with all this story lol
Anyways, 666 is the patience and Rovo the angel
Primokorn said:
Yep sorry I misread your post. I feel a little bit stressed with all this story lol
Anyways, 666 is the patience and Rovo the angel
Click to expand...
Click to collapse
Hahaha no worries bro just keepin the haters out of this thread :bruh:
just for waiting...
Hope xposed will be ported to lollipop eventually!!!
Hi guys! Yeah, I'm part of those 95% (I'm a lawyer), but I'm very grateful to rovo for his work. I have Nexus 5, but I'm still on Android 4.4.4 because of Xposed, and I'm not going to update to 5.0 until the new version of Xposed is done. You can see how important it is for me. @rovo89, I'm pretty sure that many people would pay you to complete your work. I understand that you have higher priorities and you are doing all of this for fun, but have you thought that you have almost 3 millions of downloads? If you create your team of software engineers and sell Xposed at 2$ (2€), you work on it every day for several months, and we assume that most of the current users buy your product, you will have enough money to pay your team and dedicate all of your time at what you want. It's just a suggestion of one of these 3 millions of users, that would pay more than 2$ and appreciate your work so much! Best regards from Spain!
rovo has said on multiple occasions that he won't take money for working on Xposed as he does not want it to become a job where he feels obligated to work on it full time.
He's working on it already. Offers of monetary gain won't make that work go any faster. Everyone will just have to be patient.
Sent from my C6603
We don't know if he is really doing on it (I hope yes but..) since we have no proofs (only claims) and no documentable code progress since August 2014. Plus, rovo89 was active here last year till August or so. Then he left.
If there are people who want work on it and have enough skills to port it, they should fork it and not wait. I saw some guys on github who want to work on ART port.
He flat out stated he would not post progress publicly either on GitHub or here and to wait until he had something worth publishing (that real contributors could help with) without bothering him. Comments on issues on GitHub do show he is/was working on it.
The real problem is that people are impatient and feel entitled to updates on progress, even though rovo explicitly stated that he wouldn't be doing that.
As for others *wanting* to work on it; nobody is stopping them forking the project and doing so. If they get it working then that would be fantastic and I'm sure everyone including rovo would be happy and grateful. That's the great thing about open source.
Sent from my C6603
1. Work hard to create something really, really useful.
2. Make it (and all the resources for re-creating it) available for free.
3. Millions of people use it.
4. Decide not to work so hard on it.
5. Get hounded day in and day out for months by thousands of people.
This is a classic example of "No good deed goes unpunished".
Rovo is a saint. In his shoes, I would have told all of the "hounders" to f**k off a long time ago.
In other words, people, learn how to be grateful, get off of Rovo's case, and move on.
.
This is sad, I would donate to help the dev, especially since all this is free
i'm a user and for me is normally this long time...the system of cache is completaly changed....and see it immediately in the booting process and the loading apps process.
Be patient!
Go On Rovo u can do that =)
I hope you are wrong
KevinDixson said:
Well guys, looks like Xposed for 5.0 won't ever happen.
(To all you downers out there, its called a joke. Laugh about it. Next thread.)
Click to expand...
Click to collapse
It is already 2015 and there is still no support for lollipop. It was working fine with jelly bean. I just installed a custom lollipop rom and I wanted to user xposed with greenify. It seems I have to wait and your saying will just be a conspiracy. You should really stop creating this kind of threads. Value people's creativity. That fact that, there is a delay doors not mean it will not be made. If for anything at all, give them some morale
Lollipop is a completely new system. The difference between KitKat and Lollipop is almost the same as between Windows 95 and Windows XP, if not larger... Lollipop looks like ordinary Android, acts like it, but it is NOT it...
Hi!
I've been exploring the Xposed Framework for quite a while. There's rich repository of modules based on the framework api.
But I feel that there is quite a dearth of learning resource for people who want to learn about it.
hamzahrmalik has a great tutorial for developing modules although the setting up part is outdated. Also there are very less example for using Helpers, common errors solving and hooking method with parameters(seriously there are loads of posts asking about hooking with parameters but none have a clear answer). Going through source codes to find answers is pain in the bum since most of them have almost no documentation.
Honestly there ought to be a better documentation for the api seeing as how very popular and awesome it is.
Yes, fully agree. I created similar topic to discuss about new project "Xposed Wiki" where we can collect docs, examples but I received no feedback. Maybe such reaction is related to actual state of Xposed at all. Basically dead, no visible (and mainly documentable) progress since August 2014.
I also gave up and built my custom Xposer Installer build with some useful features which will never be implemented in official version since Xposed dev refused it (official statement: due to poor Xposed server - I believe many people would donate some money for better one but... Everything depends on dev's (in)activity).
This project needs the big PSA about its future. Maybe my post sounds too pesimistic but I see no reasons to be optimistic at the moment.
That's it
INDEX:
Background
Purpose
General Recommendations
When You Post in a Thread
Credits
Themes (at post #2)
Tutorials, Help Threads & Guides (at post #3)
Reports about Battery Life or Endurance (at post #4)
Possible WiFi Drops (at post #5)
Background: Following some threads in this forum I've pretty early realised that quite a few bug reports, requests and questions are raised without sufficient information to allow developers (dev), recognised contributors (RCs) or other members to easily provide solid answers and recommendations or a possible fix. Everybody should remember even the highly professional dev cannot read your mind.
Purpose: To provide some recommendations how to best phrase a request to receive the most suitable answer.
General recommendations:
Please read the XDA Forum Rules provided by @MikeChannon; from my personal point of view a definite MUST READ for everybody who intends to post on XDA or to contribute to this great site. Other MUST READ's I certainly recommend to everybody who wants to "breathe" what I believe the spirit of XDA is, are the following posts:
Forum Etiquette by @TheByteSmasher,
http://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441 by @zelendel, and last but not least
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=44 by @kyphur.
Do me the favour and really inhale what I just linked above!
Remember: Before you flash anything take a NANDROID backup or ensure you've an up-to-date one!
Before you post your issue or request, reboot at least once and try to replicate your problem. If it doesn't persist any longer the reboot might already have been the solution.
Read, read, and read again, read the OPs (first post of each thread) and scan the respective thread. Use the search function of XDA (in-thread search is so good). Also, you can use a web search. It means you have to read and study but I've no doubt you don't mind to do that for your device. With all this, you'll probably find your answer without having to post something.
A lot of OPs already contain hints how to solve commonly known issues, e.g. the [ROM][6.0.1][i9305 OFFICIAL] Resurrection Remix® M v5.7.3 OP by @rodman01 provides at the very end information and workarounds for random reboots during calls, camera crashes (see also post #43) or how to convert filesystem Ext4 to F2FS and vice versa.
You have first to know by yourself if your issue could be ROM or Kernel related. If you don't, post and see how it goes. Occasionally, the issue seems to be ROM or kernel related on the first glance but it isn't. For example, MMS sending or receiving issues are mostly related to somehow wrong or bad APN settings, or the baseband/modem isn't suitable for the respective local region or the desired carrier. A guide in regard to fixing of MMS issues is linked at post #3.
Before you post in a ROM development thread, be sure you do not run a custom kernel or Xposed (you should disable all Xposed modules and see if your issue still persists). Despite this, if you use a custom kernel or use Xposed and you're 100% sure it's ROM related, maybe you could post.
Last but not least: Don't ask what e.g. the best ROM or kernel is! All ROM, kernel, etc. available at xda are great but each one has its different specification, capabilities, pro's and con's. The best one for you is the one, which meets your desires and expectations.
When you post in a thread:
Post questions in Q&A forums or threads instead of DEV forums. But if you have a solid bug report (never reported before and fulfilling all the required criteria, check below) with all needed info, you can post in a DEV thread.
Don't make a dev, RC or anybody else to read your mind.
Don't have a dev, RC, or anybody else to make assumptions. As soon as an assumption fails the whole solution is going to become void.
Please post your issue or request by using the English language as mentioned in the XDA rules to allow everybody to understand the post and hopefully to contribute to or at least to learn out of it. Don't be afraid if English isn't your native tongue - that's certainly the case for most of the xda users. English isn't an issue here - as long as we all at least try to use this language. Even if your English skills aren't too developed just use simple wording; nobody is going to blame you; however, try to be as precise and unambiguous as possible.
Always run a logging tool to be able to augment your post by a log (logcat) file. Add the log as an attachment to your post or upload it on the cloud and paste the public link in your post. It doesn't matter, which logging tool you use but familiarise yourself with its use and where it saves the log. I'm e.g. using an app called "Catlog" that saves logs to the internal memory. Also you can use the MatLog app or use adb commands (HERE is a guide/tutorial)
If you're running Xposed uninstall it, and take the log again (while Xposed is running, the log even states that it's useless because of Xposed).
Take screenshots (quite often via buttons "Vol-" & "Pwr" or "Home" & "Pwr" depending on the ROM you use) or if more suitable a screen record (quite often via buttons "Vol+" & "Pwr") and attach them/it to your post. Before you take a screenshot or record, change your system language to English to allow everybody to understand the content of the screen. Some ROM provide these functionalities in the menu of the power button, too; however, they must be enable within the ROM settings.
Always provide exact and precise information about your issue. Write a description and, if possible, steps to reproduce.
Always provide exact and precise information about your device, the ROM, the kernel, your recovery, and specify the versions of the latter three. Occasionally information about your modem (or even bootloader) might also be helpful e.g. if you've problems with the RIL, mobile network or making phone calls. If you're on F2FS please mention.
If your issue or problem occurred immediately after you freshly flashed a ROM or kernel, please describe your installation procedure (clean, dirty, or describe when you wiped and/or formatted what). Please provide information, from which ROM or kernel you came.
If you have issues with anything from Google, specify the GApps version you flashed.
If you're using Xposed (not recommended when reporting bugs), please provide this important information including version and its developer as well as the modules you use.
Credits:
@Wood Man for commenting the initial draft and the highly valuable contributions.
@西村大一 for providing helpful comments to keep this thread valuable.
and to everybody who I mentioned in this OP or the subsequent posts. If I forgot someone I apologise. Please let me know in this case or if you want to be more prominently given credit; I'm happy to immediately follow such a request!
EDIT (2016-09-11) Reports about battery life or endurance:
Moved to post#4.
Off topic comments are allowed as long they are generally related to the overall topic, are in the general interest of the followers of this thread and add value to the thread. The ultimate decision rests with me as the OP!
Themes
In addition to all statements in the OP, themes might be able to heavily influence system/ROM performance and behaviour; however, all pending on the used ROMs. Themes could mess things up on specific ROMs.
I personally got black screens on my GT-I9305 in the combination of a specific theme used, Resurrection Remix (MM) and Xposed. Switching to a different theme (PitchBlack | DarkRed CM13/12), which was developed by a Resurrection Remix dev (Altan KRK (westcrip)), solved the issue. Another RC experienced and reported to have had issues related to themes when he tested CM12.1 and CM13.
On the other hand, e.g. some Sammy stock based Android 4.4.4 ROMs (e.g. AMCHA ROM, N4 ELITE, TGP, etc) even don't have a theme engine, and shouldn't make the above mentioned trouble.
As said, it depends on the used ROM! But if you experience issues I suggest at least to consider your theme to be possibly involved. Guess it's pretty easy to switch to the stock design, probably to reboot, and to check if the issue persists. However, I like to stress again, it depends on the used ROM!
Thanks to @[I]Wood Man[/I] who first pointed me to the solution to my above mentioned issue, and second who doesn't get tired in providing hints for this thread!
Tutorials, Help Threads & Guides
What is? Boot loader, custom ROMs, CWM, modem, kernel, flashing, rooting, ADB, baseband?? by @esimon311. Thanks to esimon311 for this great overview.:good:
[GUIDE] Most up to date guide on CPU governors, I/O schedulers and more! by @Saber. Thanks to Saber (formerly gsstudios) for this great guide.:good:
[Tutorial] How To Logcat by @paxChristos. Thanks to paxChristos for this great tutorial.:good:
[HELP THREAD][i9300][i9305] Ask any Question. Noob friendly. by @limjh16. Thanks to limjh16 for providing great support.:good:
[HELP THREAD] Galaxy S3 - Ask any question. by @tommypacker. Thanks to tommypacker for having set up this great help thread.:good:
[Q&A] to [INDEX] Samsung Galaxy S3 LTE - ROMs, Kernels, MODs, Recoveries, Themes established by the "QA bot".
[GUIDE][26-07-2016]Extreme Battery Life Thread(Greenify+Amplify+Power Nap) by @v7. Thanks to v7 for having set up this great guide.:good:
Idle Battery Drain on Stock ROM (XPosed & Amplify Required!) by @Celestial Fury. Thanks to Celestial Fury for having set up this great guide.:good:
[HOW TO] Fix GPS location/locking to satellites issue by @Maho_66. Thanks to MaHo_66 for this great procedure.:good:
[GUIDE] SIM-unlock your i9305 by @西村大一, formerly known as "Alexander_the_B0ss". Thanks to 西村大一 for this useful guide.:good:
[GUIDE] [HOW TO] [FIX] MMS sending error on 5.1 to 7.1 AOSP and CM based ROMs by @alias_ z3d. Thanks to alias_z3d for this useful guide.:good:
How did I enhance the battery duration of my SGS 3 LTE (GT-I9305)? by me.
A short story by me how I installed microG and related application on my GApps-free device is available here.
If any of the above information has been of help for you please hit the thanks button in the respective OP!
Reports about Battery Life or Endurance
If you observe abnormal battery performance, duration or life from your point of view, please take and check battery statistics yourself!
Please do NOT post anything beforehand (e.g. in the Q&A thread)!
From my personal point of view, a recommendable application to check battery stats is “BetterBatteryStats” but there a lot of similiar apps available. The OP of “BetterBatteryStats” provides you with good information about wakelocks and battery life in general, too.
Take your stats for some hours or even better a few days (and nights). Try to figure out if wakelocks persist that are triggered by apps or processes. If you are able to identify e.g. such an app, try first yourself if the issue gets fixed by de-installation of such an app. Think about getting in touch with the app's developer.
ONLY if it’s finally ROM or kernel related, post in Q&A section or dev section but observe these prerequisites:
Battery stats screenshots, AND logs, AND as many details as possible.
Good battery endurance paired with a "smooth" system behaviour seems to be priority number one for everybody for obvious reasons. However, regularly nobody clearly defines what a good battery endurance or life means. Is it the 24+ hrs, which satisfies the one, but 16 hrs already the other? Discussions about the battery seem to continue just knowing the type of device and probably the ROM but ignore the overall system and especially personal behaviour and preferences of the device's owner.
Besides ROM and kernel, a lot of different things are obviously effecting the battery:
How do you use your phone? Heavy load gaming? Screen permanently on while staring on "grimacebook" or "whogivesa..."?
What are the application running on the device, and which have permission for auto-start at boot or to stay awake? Which and how many applications do run in the background, and are eating fuel?
Age, capacity, and type of the battery.
Mobile data always ON or not.
WiFi always ON or not.
Cell network coverage and reception.
Screen brightness level.
Abnormal wakelocks triggered by crappy apps.
etc. etc. etc.
Prior to a decision for a specific tariff plan, analysis of the consumer behaviour in regard to number, duration, network of calls, text messages, and data consumption is desired. In turn, evaluation of battery life appears to require a similar approach by assessing the topics stated in the list above. Literally, at least I personally deem to be unable to advice anybody else but me how good battery life is or how to improve it.
It's somehow useless for different users to compare or ask for battery life between ROMs / Kernels since we all have different behaviours, different ways to configure the phone, and different apps installed.
For completeness, I'd like to mention there're multiple applications and Xposed modules around, which are supposed to extend endurance of a battery, e.g. Greenify, Amplify, or Power Nap in order just to mention a few. A web search might drag you to the ones that are best suited to you, and you always need to evaluate for yourself if they serve the advertised purpose and your requirements. Be also aware that some of them require the Xposed framework to function or for full functionality. Some guides are linked at post#3. If interested in privacy I suggest to thoroughly read the reviews of the respective tool, have its point or country of origin in mind, and search the web. Nearly all are requesting root privileges and/or use the Xposed framework i.e. are going to have more or less unlimited access to your device. Good news are many of them are open source, and at least the ones I mentioned above don't require access to the internet to function. I'd personally ensure that they mustn't pass the firewall (e.g. AFWall+ by @ukanth or NetGuard by Marcel Bokhorst (@M66B).
(edited with the help of and thanks to @Wood Man):good:
EDIT (2016-10-11): In this thread, I tried to explain how I did enhance the battery duration of my SGS 3 LTE (GT-I9305); however, maybe it's also suitable to other devices (I'm convinced it is).
Possible WiFi Drops
@Wood Man allowed me to quote him reagrding WiFi drops that occured to him several times. It never happened to me because my setup was (just by accident) always different; however, if WiFi drops occur to you please have a look below. The explanation is so reasonable and makes so much sense from my point of view. Thanks very much to Wood Man for sharing his knowledge.
Wood Man said:
...
Here is a feedback about an old issue I've reported about wifi drops: previous reports HERE and HERE.
I can say the problem is not the ROM neither the kernel. Everything is OK on your side rodman . The problem is just because I use Wi-Fi 2.4ghz and bluetooth at the same time. Since bluetooth uses the same 2.4 ghz frequency, it explains the problem: INTERFERENCES while streaming on both wifi and bluetooth at the same time!
It's a known and common issue with wireless devices. One culprit should be wifi or bluetooth drivers which not handle perfectly both connections at the same frequencies. Some devices well built, with good drivers, can handle this well AFAIK. It's never perfect because other sources of interferences exist.
One solution should be to use wifi 5ghz (if available on router, and device).
Another solution is to use better bluetooth devices which handle better bluetooth/wifi protocol, using the same frequency.
...
Click to expand...
Click to collapse
About drainage, I don't know. But could be...
The interferences happen only while streaming. I mean we can connect both wifi 2.4 and bluetooth at the same time without problem, the connection stays, but inteferences happen only when sound goes to audio bluetooth device.
Click to expand...
Click to collapse
Forgot to say that even if wifi 2.4 doesn't drop, the wifi transfer speed could very very slow in case of interferences with bluetooth streaming. (It's my case with my P9 Lite).
Click to expand...
Click to collapse
UPDATE (2017-05-26): Please find some additional, new information of @Wood Man at post #59:
...
I did a house moving recently and now I can use both Wifi 2,4 ghz and bluetooth at the same time without issues. The differences between my previous flat and my new one are:
1- A new router,
2- Less Wifi networks around me.
I bet point #2 above is the key because there are less interferences now in my flat ...
Click to expand...
Click to collapse
Aminewolf said:
#Outoftopic
Feels good to give the freshly joined juniors a lesson on how to use the search function doesn't it
Click to expand...
Click to collapse
Actually not; I don't want to appear as a schoolmaster. That's the reason why I decided to create this thread.
I already asked FLooDW, but I'm also looking forward to your opinion?
Hi @noc.jfcbs,
Thanks for your thread, your time, your recent contributions and credits you gave to me
This is a good idea, I really hope a lot of members will read and apply your recommendations.
As you requested my opinion, I've done some modifications in your OP here below within the HIDE tags. Maybe some more adjustments will be necessary, I don't know yet.
FLooDW said:
Hi @noc.jfcbs,
Thanks for your thread, your time, your recent contributions and credits you gave to me
This is a good idea, I really hope a lot of members will read and apply your recommendations.
As you requested my opinion, I've done some modifications in your OP here below within the HIDE tags (sorry for XDA Labs users who will see the the whole modified OP). I will for sure update my post once the OP is modified (if you want to do so). Maybe some more adjustments will be necessary, I don't know yet. ...
Click to expand...
Click to collapse
@[I]FLooDW[/I], your suggestion is at least 10x better than my (let's call it) initial draft. Thank you very much for taking your time and having a look. ...actually it was much more than that. I did appreciate it.
OP is modified and waiting for further adjustments. Guess you can update your post now. CU
noc.jfcbs said:
@[I]FLooDW[/I], your suggestion is at least 10x better than my (let's call it) initial draft. Thank you very much for taking your time and having a look. ...actually it was much more than that. I did appreciate it.
OP is modified and waiting for further adjustments. Guess you can update your post now. CU
Click to expand...
Click to collapse
OK thanks for including my changes
My post is now edited.
Also, I've already added your thread in my signature
This is a very good thread, contribution and idea. The only problem to me is that it is in a secluded forum (quite) you may want to ask a moderator to move this to general forums or such.
Sent from my GT-I9305 using XDA Labs
limjh16 said:
This is a very good thread, contribution and idea. The only problem to me is that it is in a secluded forum (quite) you may want to ask a moderator to move this to general forums or such.
Click to expand...
Click to collapse
Yes I was thinking quite the same. I'm not sure this thread is at the right place. But in another hand I think it could be a good idea to keep it in dev forum because the purpose is to advertise members to post the right way in dev threads. It could be discussed
FLooDW said:
Yes I was thinking quite the same. I'm not sure this thread is at the right place. But in another hand I think it could be a good idea to keep it in dev forum because the purpose is to advertise members to post the right way in dev threads. It could be discussed
Click to expand...
Click to collapse
Let me give you my 2cents:
The thread, no doubt, is in the wrong forum, but it should be pinned and given the highest priority. It is so effin useful.
The idea behind it is so good. Really. It makes me jealous. I will try and formulate some examples for @noc.jfcbs to add to the OP to further help newbies.
Alexander_the_B0ss said:
Let me give you my 2cents:
The thread, no doubt, is in the wrong forum, but it should be pinned and given the highest priority. It is so effin useful.
The idea behind it is so good. Really. It makes me jealous. I will try and formulate some examples for @noc.jfcbs to add to the OP to further help newbies.
Click to expand...
Click to collapse
Well, good point
---------- Post added at 09:14 AM ---------- Previous post was at 08:41 AM ----------
However if we move this thread in Q&A section, I think it won't be read that much before newbies post in DEV forum... Even if it's pinned in Q&A section.
I really think it should be pinned in dev forum so newbies read before posting there, but it would also be inappropriate for dev forums...
Or it should go to general forum and pinned and linked to all dev forums. But then again if we link it some may not see (I'm guilty of this sometimes :silly: ) should I page a moderator? Or I think we should wait for noc.jfcbs to make his own decision
Sent from my GT-I9305 using XDA Labs
limjh16 said:
I really think it should be pinned in dev forum so newbies read before posting there, but it would also be inappropriate for dev forums...
Or it should go to general forum and pinned and linked to all dev forums. But then again if we link it some may not see (I'm guilty of this sometimes :silly: ) should I page a moderator? Or I think we should wait for noc.jfcbs to make his own decision
Click to expand...
Click to collapse
In any case we have to wait noc.jfcbs's point of view and then we'll ask a moderator.
@[I]FLooDW[/I], @limjh16: I've got to know both of you as very experienced and highly motivated Android enthusiasts in xda. Just looking at my joining date, I'm still a newbie on this site, and I personally rather take advice from guys with more experiences.
However, before I opened this thread I certainly thought of its right place, and I had all location you mentioned above under closer consideration but I finally decide to open the thread in the current forum for this reason: I remembered which the first forum was that I used when I initially came to xda. It wasn't any "general forum" or "Q&A" but the current one. I was in interested in ROM, kernel etc. for my specific device. Additionally, I thought if the thread doesn't fit here a mod is certainly going to move it to the right place.
Having followed your discussion I meanwhile believe the topic of this thread is much more generic and not at all related to a specific device and therefore should deserve a different location on xda. On the other hand, and that's a bit selfish, I'd like to support the forums and threads I'm used to mainly monitor by qualified posts of "newbies". Currently two hearts are beating in my breast; probably I'd rather be egoistic.
noc.jfcbs said:
@[I]FLooDW[/I], @limjh16: I've got to know both of you as very experienced and highly motivated Android enthusiasts in xda. Just looking at my joining date, I'm still a newbie on this site, and I personally rather take advice from guys with more experiences.
However, before I opened this thread I certainly thought of its right place, and I had all location you mentioned above under closer consideration but I finally decide to open the thread in the current forum for this reason: I remembered which the first forum was that I used when I initially came to xda. It wasn't any "general forum" or "Q&A" but the current one. I was in interested in ROM, kernel etc. for my specific device. Additionally, I thought if the thread doesn't fit here a mod is certainly going to move it to the right place.
Having followed your discussion I meanwhile believe the topic of this thread is much more generic and not at all related to a specific device and therefore should deserve a different location on xda. On the other hand, and that's a bit selfish, I'd like to support the forums and threads I'm used to mainly monitor by qualified posts of "newbies". Currently two hearts are beating in my breast; probably I'd rather be egoistic.
Click to expand...
Click to collapse
in that case, do you think it will be a good idea to include this in every rom thread? I will definitely quote this OP in all my rom, kernel etc threads with your permission. And we can always page for rodman
Allow me to make a suggestion, even or although it might be, that this couldn't be implemented in the forum system. Because of the reason that the 10 post rule seems to be cancelled (?), what do you think about, when ever a new member is willing to post a comment in a dev thread, he would get a pop up with a link to your, will say this post. Or in that pop up the message is already included. It might be a bit strict, but its mentioned without offense. I can understand, that most of the people and new users, want to get an answer soon or even at once, to their individual questions or problems and this without doing something of themselves. They want it presented or spoon feeded (@FLooDW ). And this also a matter of our current life style , in my opinion. But on the other hand, for example you and FLooDW and several others are taking their time to find solutions, to answer again and again and individually and user friendly. Porters or devs, if they are not also and additionally answer regularly in their threads, are spending their time with the roms they provide. So I think, if you/we request a bit time from the other users, that would not only be fair. It would also show a kind or certain respect to the time and effort other users are spending to support the others in which way ever....
Beside of that I personally would appreciate and prefer that this thread would be pinned here in the dev section...
Just my thoughts....
I'm just going to go ahead and ping @Trafalgar Square
I have an idea (not a very good / original one) that there is a pinned post in dev section that links to this thread. Not exactly this thread goes onto every forum, more of the pinned post redirects here
or if possible, rodman 's suggestion
Alexander_the_B0ss said:
Let me give you my 2cents:
The thread, no doubt, is in the wrong forum, but it should be pinned and given the highest priority. It is so effin useful.
The idea behind it is so good. Really. It makes me jealous. I will try and formulate some examples for @noc.jfcbs to add to the OP to further help newbies.
Click to expand...
Click to collapse
@Alexander_the_B0ss: I'm getting shyly by your kind words but looking forward to your highly appreciated advice and suggestions.
So I'm surprised this isn't Priority One across the board for development with Android.
Now that it looks like John's gone, I'm actually shocked that no one is tried to take over or step forward to try and come up with an alternative. This should be all hands on deck Priority One as not having root is far sh1tt1er than having it. Maybe I just I'm not up to the newest dev news. Does anyone have any information on possible development about that?
The vvb2060 Alpha builds are still getting updated, and as that had been a trusted collaborator with John, that seems to be the current path for continued development.
Why does everyone assume that development of Magisk has stopped? Until we hear anything from John there's zero need for "fear mongering" and speculation...
FUD is what keeps forums running
Theraze said:
The vvb2060 Alpha builds are still getting updated, and as that had been a trusted collaborator with John, that seems to be the current path for continued development.
Click to expand...
Click to collapse
Yes I've been running the alpha build since earlyJune. However I worry/sneaking suspicion and inclination that his intention or competency level is to tweak existing technology rather than flat out create compatibility for Android 12 for example. These are my fears.
Burt Squirtz said:
Yes I've been running the alpha build since earlyJune. However I worry/sneaking suspicion and inclination that his intention or competency level is to tweak existing technology rather than flat out create compatibility for Android 12 for example. These are my fears.
Click to expand...
Click to collapse
You need to step back, take a chill pill, and unclench
73sydney said:
You need to step back, take a chill pill, and unclench
Click to expand...
Click to collapse
trying to look cool? Not sure why you bothered to type this - as absolutely nothing in my post would indicate that I'm not calm.
Surprised more people are asking this question about having root in the future.
Well.
It is better to think ahead but it may happen that demand will create supply.
It is basic market rule.
I hope & pray that current Magisk will continue to work even if site where it checks updates and modules disappears.
Burt Squirtz said:
trying to look cool? Not sure why you bothered to type this - as absolutely nothing in my post would indicate that I'm not calm.
Surprised more people are asking this question about having root in the future.
Click to expand...
Click to collapse
Because the FUD was boring a month ago
The only prospecting you should be doing should involve a gold pan
p.s. My default setting is humour, sometimes people get it, some dont, the clue would have been the 2 smilies i put in to try and make certain it was taken that way
p.p.s. Casting doubt on someones abilities (vvb2060) isnt cool, just saying, they guy is working largely on his own to add features/fixes from the original Magisk repo issues, so maybe cut him some slack? or help out?
i really like vvb2060 magisk lite approach
i hop he adds control to it throw a terminate
Didgeridoohan said:
Why does everyone assume that development of Magisk has stopped? Until we hear anything from John there's zero need for "fear mongering" and speculation...
Click to expand...
Click to collapse
Back in May, topjohnwu had already confirmed that Google is forbidding him from working on Magisk.
misterlink said:
Back in May, topjohnwu had already confirmed that Google is forbidding him from working on Magisk.
Click to expand...
Click to collapse
Since that screenshot is taken out of context from a longer conversation, that was private and not shared by John himself, it doesn't show the whole truth.
My statement still stands: wait until we hear anything official from John...
Game Over.
State of Magisk: 2021
Ever since my employment at Google, crazy speculations has been spreading like wild fire all over the Internet. The out-of-context private…
topjohnwu.medium.com
Game over? I think we read that text and came to two very different conclusions...
It's far from game over.
So as far i understand he is allowed to continue working on magisk but is not allowed to do any work on magisk hide or any hide module he claims that is just 5% of the work so if he does magisk and someone else adds magisk hide function it is all good right ?
mstrnemo said:
So as far i understand he is allowed to continue working on magisk but is not allowed to do any work on magisk hide or any hide module he claims that is just 5% of the work so if he does magisk and someone else adds magisk hide function it is all good right ?
Click to expand...
Click to collapse
This sounds simple enough, but Magisk without MagiskHide will be relatively useless since most apps that aren't a web browser will refuse to run because they detect root and/or an unlocked bootloader. This is the core problem that Magisk solves. The rest of the Magisk modules are nice to haves.
Until the apps try to detect modifications to themselves rather than simply seeing if there is a possibility of modification they are not doing anything for security but instead further locking users into their ecosystem.
l7777 said:
This sounds simple enough, but Magisk without MagiskHide will be relatively useless since most apps that aren't a web browser will refuse to run because they detect root and/or an unlocked bootloader. This is the core problem that Magisk solves. The rest of the Magisk modules are nice to haves.
Until the apps try to detect modifications to themselves rather than simply seeing if there is a possibility of modification they are not doing anything for security but instead further locking users into their ecosystem.
Click to expand...
Click to collapse
I would imagen magisk would not be useless as i would assume magisk and a hide module would be in development in paralell to each other so magisk by the creator and hide by other developer who is kind innof to help out so yeah.
unless people ditch magisk alltogether and fork it and do it difrently who knows
i just read the article about this on the xda homepage and read through the comments people seem to be freaking out and spell doom to custom roms and everything about it pretty funny though but i geuss the signs are on the wall....
mstrnemo said:
I would imagen magisk would not be useless as i would assume magisk and a hide module would be in development in paralell to each other so magisk by the creator and hide by other developer who is kind innof to help out so yeah.
unless people ditch magisk alltogether and fork it and do it difrently who knows
i just read the article about this on the xda homepage and read through the comments people seem to be freaking out and spell doom to custom roms and everything about it pretty funny though but i geuss the signs are on the wall....
Click to expand...
Click to collapse
Ok, useless might have been too strong. If a hide module is developed and maintained then things will largely stay the same. That said, until that materializes, it is the end of Magisk as we know it. Anyone who claims that nothing will change is going to give rise to a lot of disappointment. Don't get me wrong, there are lots of talented developers and one could very likey pick up where TJW leaves off but I certainly wouldn't bet on it.
IMO rather than fight with the our small community, Google/Android should provide us a way to self sign our devices and absolve themselves of any responsibility to keep our devices "secure".
l7777 said:
Ok, useless might have been too strong. If a hide module is developed and maintained then things will largely stay the same. That said, until that materializes, it is the end of Magisk as we know it. Anyone who claims that nothing will change is going to give rise to a lot of disappointment. Don't get me wrong, there are lots of talented developers and one could very likey pick up where TJW leaves off but I certainly wouldn't bet on it.
IMO rather than fight with the our small community, Google/Android should provide us a way to self sign our devices and absolve themselves of any responsibility to keep our devices "secure".
Click to expand...
Click to collapse
Yeah agree on your first part
now about that second part..
never going to happen why ? because what do you think we are to those companys? what do you think they would call us people who dont buy a new phone every year and keep older phones working for a couple years with the latest software huh ? we cost them money it is in their best interest that none of all this works and or is capable because if it wasnt everyone here would have to get a new phone ergo bringing in the bacon for those said companys...
I wish we could send out a message a reqeust to all the developers on this site and be like oke guys lets ditch android it is not worth the ffort anymore lets get together all of us and work on alternitives of wich we have 2
ubuntu touch linux os for phones (there are otheres but noone as far developt as this one) also it is stil not entirely their yet but it is very close.
sailfish wel basicly also linux this is next best thing to android it is based on nokia/intel meego project it is like i said linux based and open source this is what the developers should work on it is just rough araund the edges but works great one downside while it is opensource the ability to run android apps is properity software so developers would have to come with their own thing forexample maybe try and get wine to work on sailfish so u can use android apps as normal phone.
what do you think? developers unite in a avengers style and the ones who cant do code like myself help by donating ?
mstrnemo said:
Yeah agree on your first part
now about that second part..
never going to happen why ? because what do you think we are to those companys? what do you think they would call us people who dont buy a new phone every year and keep older phones working for a couple years with the latest software huh ? we cost them money it is in their best interest that none of all this works and or is capable because if it wasnt everyone here would have to get a new phone ergo bringing in the bacon for those said companys...
I wish we could send out a message a reqeust to all the developers on this site and be like oke guys lets ditch android it is not worth the ffort anymore lets get together all of us and work on alternitives of wich we have 2
ubuntu touch linux os for phones (there are otheres but noone as far developt as this one) also it is stil not entirely their yet but it is very close.
sailfish wel basicly also linux this is next best thing to android it is based on nokia/intel meego project it is like i said linux based and open source this is what the developers should work on it is just rough araund the edges but works great one downside while it is opensource the ability to run android apps is properity software so developers would have to come with their own thing forexample maybe try and get wine to work on sailfish so u can use android apps as normal phone.
what do you think? developers unite in a avengers style and the ones who cant do code like myself help by donating ?
Click to expand...
Click to collapse
Oh I would never expect #2 to happen either, that is why it's only my opinion.
A phone OS not managed by a large corporation would be great, but it couldn't survive without the app stores of the large corporations. That is what they are making money off of, not the devices. I think most of us already realize that so I'm just stating the obvious.