Related
I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.
Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.
Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.
IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.
I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium
JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.
Can you make a patch for stock root.
Thx
Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.
soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.
Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
mrpoe222 said:
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
Click to expand...
Click to collapse
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
BWolf56 said:
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
Click to expand...
Click to collapse
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
mrpoe222 said:
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
Click to expand...
Click to collapse
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
BWolf56 said:
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
Click to expand...
Click to collapse
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
mrpoe222 said:
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
Click to expand...
Click to collapse
Clearing client database means clearing data and cache in the play store app. That's what worked for me on with that issue...or loading another Google account then deleting it then adding your main one.
Verizon Galaxy S3 running RLS10 - call echo issue
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
the echo is just on your end, correct?
go to settings >accessibility and make sure turn off all sounds is not checked to begin with. now go to settings > sound and make sure your volume levels are correct and sound is turned on.
also, phone > menu > Call settings > additional settings and then uncheck noise reduction. some people have reported less echo and clearer calls with this turned off.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
A few have reported the same issue on the thread but no real solution beyond hit speaker on then off and it goes away. Reason that works ? I have no clue.
These are the few bugs I've come across so far with the Gummy 12/12/13 nightly ROM
When I hit the menu button and then try to hit settings, it does nothing. I have to go to the physical settings app.
Stock calendar app doesn't sync with my Google account.
That's all I really have right now.
ajsab said:
These are the few bugs I've come across so far with the Gummy 12/12/13 nightly ROM
When I hit the menu button and then try to hit settings, it does nothing. I have to go to the physical settings app.
Stock calendar app doesn't sync with my Google account.
That's all I really have right now.
Click to expand...
Click to collapse
Please don't make new threads for this sort of thing. These can go in the ROM thread, preferably with atatched logcats to help the developers fix the issues.
Skipjacks said:
Please don't make new threads for this sort of thing. These can go in the ROM thread, preferably with atatched logcats to help the developers fix the issues.
Click to expand...
Click to collapse
Unfortunately I can't even create a new thread in the ROMS forum since I'm a new member. Also, there is no thread about the Gummy Rom yet so how else can I post it?
ajsab said:
Unfortunately I can't even create a new thread in the ROMS forum since I'm a new member.
Click to expand...
Click to collapse
Not a new thread. A new post in the ROM thread.
Also, there is no thread about the Gummy Rom yet so how else can I post it?
Click to expand...
Click to collapse
You mean like this one?
http://forum.xda-developers.com/showthread.php?t=2527337
That has been available since November 14th?....
The best advice I can give you is that the new Gummy ROM is a work in progress. It's new. It's going to have bugs like this. All the 4.4 ROMs are having oddball issues like this. If you don't want to deal with this stuff the best option is to wait a month or so for these kinks to be ironed out and use a stable 4.3 ROM in the mean time.
[Q&A] [ROM] Euphoria-OS v1.0 [Lollipop 5.0.1][UNOFFICIAL] [D851 ONLY!] UPDATED 12/06
Q&A for [ROM] Euphoria-OS v1.0 [Lollipop 5.0.1][UNOFFICIAL] [D851 ONLY!] UPDATED 12/06/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Euphoria-OS v1.0 [Lollipop 5.0.1][UNOFFICIAL] [D851 ONLY!] UPDATED 12/06/14. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Does the SD card work with this? It's not working for me on D851.
puargs said:
Does the SD card work with this? It's not working for me on D851.
Click to expand...
Click to collapse
External SD works fine. If its not working for you, your SD is not formatted correctly.
Sent from my LG-D851 using Tapatalk
connection
No 4g?not wirking
I've been using this rom for 2 days now and everything works. I've found that swipe on the Android keyboard doesn't work. Other than that great rom and great job!
Charging notification on home screen?
It's not a big deal at all, love the rom, but just today I noticed after I took it off the charger the lock screen still says charging. I don't know if it's just me but I figured I'd mention it.
When I use "quick reply" to respond to a text from the stock texting app, it'll reply fine but it leaves the message that I replied to as unread.
Is anyone else experiencing this?
---------- Post added at 07:13 PM ---------- Previous post was at 06:16 PM ----------
Just got a call then my gf texted me saying she got a call from the same number and they left her a voicemail so I logged into my voicemail and even though I didn't have a voicemail notification, they did leave me a message.
Anyone else not getting notified for voicemail messages?
gapps link
Saw the link to the GAPPs in the 1st post was dead and some people were asking about it
Here is the link to the GAPPS 5 thread: http://forum.xda-developers.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900
multivacac said:
Saw the link to the GAPPs in the 1st post was dead and some people were asking about it
Here is the link to the GAPPS 5 thread: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Click to expand...
Click to collapse
Thanks, updated the OP with the new link.
Sent from my LG-D851 using Tapatalk
Video Playback
Is there any known issue with playback of videos from Facebook? Both in app and on Chrome I get a message saying "sorry an unknown error occurred while trying to play this video." Anything that tries to use the native video player I would think.
sorry, im new, so i do not understand " Flash SuperSU " ????my phone was rooted!!! and i updated this rom, i skipped the step "Flash SuperSU ". and my phone seem to be not rooted completely. so anyone please show me how to Flash SuperSU ??? and i could try again!!
Has anyone reported the "Stay Awake" doesn't seem to... well... work. I mean technically Im not chargging as I'm at 100% but still. Dims, turns off, then I have to unlock.
Sorry if this was already reported.
Battery Style
I know there are lots of other things to work on, but is there any way we can get dotted circle battery or other custom battery icons. Would LOVE it. Hell I'm no sure if CM has this. Also so far so good on the "always on" behavior. Seems to be working as it should! Kudos keep up the good work. Love this rom!
ansohuyet said:
sorry, im new, so i do not understand " Flash SuperSU " ????my phone was rooted!!! and i updated this rom, i skipped the step "Flash SuperSU ". and my phone seem to be not rooted completely. so anyone please show me how to Flash SuperSU ??? and i could try again!!
Click to expand...
Click to collapse
rooting and flashing custom roms is a serious business. When a step is listed it makes no sense to skip. Do you have a recovery loaded and functional? If you do, download a flashable superuser zip and flash in recovery. If not, better sharpen your search skills and find how to proceed.
again, devs list steps for a reason
Google account?
Hey, I'm new around here although not new to rooting phones, and flashing Rom's. However when it came to flashing a CM mod or a euphoria mod, I had no idea as to how to sign in with my Google account to get my contacts and everything into my phone. Must I have GApps downloaded? If so, how do I flash it? Just do a dirty flash? Any and all help is greatly appreciated! Really really love the euphoria mod for the g3 but I MUST be able to sign into Google.
Vengence820 said:
Hey, I'm new around here although not new to rooting phones, and flashing Rom's. However when it came to flashing a CM mod or a euphoria mod, I had no idea as to how to sign in with my Google account to get my contacts and everything into my phone. Must I have GApps downloaded? If so, how do I flash it? Just do a dirty flash? Any and all help is greatly appreciated! Really really love the euphoria mod for the g3 but I MUST be able to sign into Google.
Click to expand...
Click to collapse
I believe the devs list having to flash a gapps program as a part of the steps of installing a CM rom.
Is anyone else having an issue with NFC? I didn't see anything mentioned in the threads, my apologies if this is a known bug.
Everything else seems to be running pretty great.
baked-in density change issue
Hello graig79,
First all thank you for such a great rom.
Small issue i noticed seems baked-in density changer no longer works. It certainly worked on your previous version. I noticed if you set the number then leave the settings menu altogether and come back it doesn't even same what number you set to.
Not sure If this is due to a custom change you applied or a change from cm.
Thought i mention it.
Thanks again.
Downloads?
Loving the ROM! However ive encountered something that might just be a problem on my side but whenever i try to download something from the internet browser, it tells me that it cannot be downloaded. The directory it tries to save files too i believe it doesnt exist. Is there a way i can change where files are being saved? Thanks again.
aareya said:
Hello graig79,
First all thank you for such a great rom.
Small issue i noticed seems baked-in density changer no longer works. It certainly worked on your previous version. I noticed if you set the number then leave the settings menu altogether and come back it doesn't even same what number you set to.
Not sure If this is due to a custom change you applied or a change from cm.
Thought i mention it.
Thanks again.
Click to expand...
Click to collapse
Thanks, I'll take a look at the issue and hopefully have it fixed in the next update[emoji106]
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
really ...anyone who gets a brick because of not reading a thread certainly shouldnt be xda or even messing around with the phone in the first place. just stay stock if you wont read
We survived finely when Nougat was still new, so what makes Oreo special?
There's simply no good point to making a whole section for a particular version of Android. The same thing can be done simply with a proper thread title.
The problem isn't purely on the lack of separation of sections — It's the 5 seconds attention span that most seems to have because they can't read the first post of the thread they're in or they're too busy looking at butterflies and they ended up destroying their device and/or data inside the device.
I know we can't fix people, but that doesn't make for a good argument for creating a new section.
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
As stated. This is not gonna happen. If you cant do the proper research needed for what you are doing then you shouldnt be doing it in the first place.
I disagree with OP - there shouldn't be separate section for Oreo stuff. Ask yourself - what would happen, if released mod would be compatible with Marshmallow, Nougat and Oreo?
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
charackthe said:
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
Click to expand...
Click to collapse
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
zelendel said:
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
Click to expand...
Click to collapse
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
charackthe said:
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
Click to expand...
Click to collapse
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
zelendel said:
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
Click to expand...
Click to collapse
I see you all over the place! You are retired? You post on here like its full time lol
ZVNexus said:
I see you all over the place! You are retired? You post on here like its full time lol
Click to expand...
Click to collapse
I am a retired mod. My job allows for me to always be lurking around. Every couple of hours or so I check my email and catch up.
Been that way for as long as I can remember. Heck I used to be on far more in the early years.