i`m not sure if i`m breaking any rules by posting this but i`m new on this forum and i have only one problem .. when i`m trying to search for a rom i have ten's of results and onlyt 10 % of them give me what i want .. and sometimes not even thoes... i found a thread in the themes and app section whit known apps working on the touch hd etc ..
could someone make something like this for the roms ..
it`s a nightmare to search for a rom ..
this could be verry helpfull .. just "stick" the thread to the top of the forum and there a moderator or anyone who wants the job could post every existing rom and the link to it ..
no description .. just something like this :
name(dutty`s r4),(miri`s etc) win 6.5 .. build 2****
link (or something close to this)
the reason for wanting this is because whenever i`m trying to search for something i`m spending literaly hours trying to find the rom, app etc ..
thank`s for the answer .. what ever that is
first, let me welcome you to xda! what information are you searching for? your best bet is to read the 1st-10th posts of each ROM thread for details on the the ROM. reading the first few posts of each thread and then posts after the posted ROM release date (usually in the thread title) is the approach i use to get feedback.
cortez.i said:
first, let me welcome you to xda! what information are you searching for? your best bet is to read the 1st-10th posts of each ROM thread for details on the the ROM. reading the first few posts of each thread and then posts after the posted ROM release date (usually in the thread title) is the approach i use to get feedback.
Click to expand...
Click to collapse
i`m starting to get my way around .. but it`s still a bit confsing sometimes .. because it seems that every chef after releasing a new rom he is just posting it in the previews threat without starting a new one .. and sometimes it`s quite confusing .. in the same threat you find 2 3 5 roms everyone diferent builds and it`s not always easy to gues witch is what .. anyway this could be a good ideea .. at least 50% of the users here don`t use english as their base language and it`s not easy for all to find what they are looking for... i started this thread because it was trying to find miri`s build 23053 test .. i was hoping to find`it in a new title but i found`it in a older thread .. somewere at the bottom of the post.. realy hard considering i had screenshots from older builds and the title was saying something else .. anyway .. i would startit myself but i`m away form my pc about 12 hours a day (not counting the sleep )and don`t have the time
thanks for the reply and please excuse my bad english
scoutish said:
i`m starting to get my way around .. but it`s still a bit confsing sometimes .. because it seems that every chef after releasing a new rom he is just posting it in the previews threat without starting a new one .. and sometimes it`s quite confusing .. in the same threat you find 2 3 5 roms everyone diferent builds and it`s not always easy to gues witch is what .. anyway this could be a good ideea .. at least 50% of the users here don`t use english as their base language and it`s not easy for all to find what they are looking for... i started this thread because it was trying to find miri`s build 23053 test .. i was hoping to find`it in a new title but i found`it in a older thread .. somewere at the bottom of the post.. realy hard considering i had screenshots from older builds and the title was saying something else .. anyway .. i would startit myself but i`m away form my pc about 12 hours a day (not counting the sleep )and don`t have the time
thanks for the reply and please excuse my bad english
Click to expand...
Click to collapse
Its not a bad idea, but it would also be very time consuming. You have to remember that a benchmark thread already exists which gives some information on each rom already, but not to the extent your seeking. Why not have a go at creating this thread yourself and add to this site. I'm sure a lot of people would appreciate your effort.
Fallen Spartan said:
Its not a bad idea, but it would also be very time consuming. You have to remember that a benchmark thread already exists which gives some information on each rom already, but not to the extent your seeking. Why not have a go at creating this thread yourself and add to this site. I'm sure a lot of people would appreciate your effort.
Click to expand...
Click to collapse
love to .. but like u said it would also be very time consuming .. and i don`t really have the time .. i will give`it a try .. but don`t be surprized if the thread apears after 2-3 months ...
im away from home 12 - 13 hours a day and that`s why i invited someone else to give`it a go .. i just came with the ideea
so who ever reads this and wants the job .. go ahead .. a lot of people will love you after the thread`s release
I've re-opened this thread.
Hopefully others want to help and assist this quest. I'll watch thread closely and if it develops I may sticky it. But its a long way off this for now.
Good luck
Hello
I am willing to give this a try.
I would first like to hear how it would be best to do it because it could quickly get messy.
So feel free to post your suggestions.
I would then be able to asess if i can really manage it.
Jay
j1978 said:
Hello
I am willing to give this a try.
I would first like to hear how it would be best to do it because it could quickly get messy.
So feel free to post your suggestions.
I would then be able to asess if i can really manage it.
Jay
Click to expand...
Click to collapse
I would suggest making a google documents account, and setting up a spreadsheet. Make it open access to all, and arrange with ROMs down the side and details along the top. You could have sections for different authors with their ROMs all in one place. Once you have a bare bones structure, invite people to contribute and publish the address of the spreadsheet.
Good luck, it's a great idea. I would also invite proposals for what column headings you have (eg it would be good to have votes so particularly successful ROMs could be identified.)
I'm also lost in the world of rom's
for a start:
what should be in the spreadsheet?
Name of the rom
Language
Version
On what WM is it based
Date of release
programs installed
Known problems and if they're solved
stormyb said:
I'm also lost in the world of rom's
for a start:
what should be in the spreadsheet?
Name of the rom
Language
Version
On what WM is it based
Date of release
programs installed
Known problems and if they're solved
Click to expand...
Click to collapse
Hi
everything ok besides the last suggestion that would be to difficult i think.
Will post back on updates
Jay
Hello
ok Here is a barebone first try. Please view and suggest improvements. If you would like access to edit and add roms please post here or Pm me.
Jay
There was a page on the Wiki that was kept up to date:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_cookedroms
This doesn't seem to have been updated for some time.
Surely this is the best solution, a sticky in the forum which links to the Wiki, and that page is kept up to date.
Maybe the Wiki main page should have details and links to the latest ROM version for each ROM out there, and each one has a link to a page which has previous links in there. These ROMs could be grouped by Chef, and give the Chef an oppotunity to write something brief if they wish.
I do agree that is it very annoying that new threads are not started when a new version of a ROM appears as all the comments relate to when the thread was first started.
I would be happy to be in a group of people to keep the Wiki up to date...
Maybe we need to make it easy as well for the Chefs to notify moderators of the Wiki cooked ROMs page they have release a new version.
Jason
I wouldn't mind allowing someone access to editing Wingster and adding a Touch HD section to my website. I need someone who is dedicated and has time to keep it updated though.
Any takers? The website is (www.thewingster.com)
Jason1978 said:
There was a page on the Wiki that was kept up to date:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_cookedroms
This doesn't seem to have been updated for some time.
Surely this is the best solution, a sticky in the forum which links to the Wiki, and that page is kept up to date.
Maybe the Wiki main page should have details and links to the latest ROM version for each ROM out there, and each one has a link to a page which has previous links in there. These ROMs could be grouped by Chef, and give the Chef an oppotunity to write something brief if they wish.
I do agree that is it very annoying that new threads are not started when a new version of a ROM appears as all the comments relate to when the thread was first started.
I would be happy to be in a group of people to keep the Wiki up to date...
Maybe we need to make it easy as well for the Chefs to notify moderators of the Wiki cooked ROMs page they have release a new version.
Jason
Click to expand...
Click to collapse
Hmm indeed the wiki seems to be the most logical solution.
Jay
I had just picked up on this thread and was about to comment on the spreadsheet and the fact that I'm sure a Wiki page was updated once upon a time and low and behold, it's been posted!
The fact is whilst many people are fluent with cooked ROM's, there are MANY more that have a number of valid reasons for being sceptical and wanting specific information before trying.
My personal belief is that the Wiki would be the best solution for this as it can be edited by all.
However I think a mandatory standard should be introduced. Something along the lines of:
ROM Name|OS Ver|Win Release|Manila Ver & Build|Features (top 5?)|Known Bugs (Cooker) | Community common issues|
Just something like this to get some sort of understanding.
For instance, in most of the recent ROMs there seems to be an issue with MMS but the cooker doesn't necessarily agree that it's a ROM issue, hence the community common issues section.
I'm working off my own experiences here however. I personally want to know what device it will work on, what the OS and Manila versions are, what the features are but what the tradeoff to known bugs are if I flash this ROM.
One last thing - Whilst I understand that many of the cookers have other things that are ongoing and therefore get to their ROM's as and when they can and again provide support where they can, I have seen very little support for their ROM's as they know there is another around the corner. That to me is the biggest issue for people wishing to jump into the world of cooked ROMS - the ability to know exactly what they are and aren't getting. Standard ROMs provide that and hence the comfort it brings.
Comments & thoughts?
Wiggz said:
However I think a mandatory standard should be introduced. Something along the lines of:
ROM Name|OS Ver|Win Release|Manila Ver & Build|Features (top 5?)|Known Bugs (Cooker) | Community common issues|
Just something like this to get some sort of understanding.
I'm working off my own experiences here however. I personally want to know what device it will work on, what the OS and Manila versions are, what the features are but what the tradeoff to known bugs are if I flash this ROM.
Click to expand...
Click to collapse
Hello
A mandatory standard is definitly needed for the Wiki.
I guess we now need to form a team/group of people who are willing to invest some time in updating the wiki.
As for what you say on rom support, the rom thread gives you a lot of info it would also add a lot of work on an already ambitious project.
The main goal here is to provide a single place where you can see and find all available roms.
Jay
j1978 said:
Hello
A mandatory standard is definitly needed for the Wiki.
I guess we now need to form a team/group of people who are willing to invest some time in updating the wiki.
As for what you say on rom support, the rom thread gives you a lot of info it would also add a lot of work on an already ambitious project.
The main goal here is to provide a single place where you can see and find all available roms.
Jay
Click to expand...
Click to collapse
Well count me in - I'm willing to be a part of this. I really feel that for the "average user" there is very little that they can get at quickly and effectively. If you are a power user you can go through the whole "editing of manila files" and the other titbits in the threads but the fact is most people don't expect "normal" functions to be interrupted by new ROMs...they expect enhancements with no reduction in usability. I understand that there is a trade-off, but i think that trade-off should be immediately understood and available for all users to see.
Same here....
I have started tonight compiling some of the ROM details...
I could add a new table into the Cooked ROMs Wiki page with where I am up to and so people can get an idea of the layout I am proposing?
Personally I think there should be a table per WM version, and also per language, although I have concentrated efforts firstly on WWE.
I also would group in the table by Chef, listing their variants next to each other, each on a different line, but light, standard, heavy builds of the same variant that are usually on the same thread should be on one line, I think we can span the lines in the table on the Wiki so it looks right. The main table should only have latest links, and maybe another Wiki page with previous links, that we move when a new one comes out, so a record is kept where possible.
The column where the name of the ROM series is will link to the thread, with the download links having its own column if possible (maybe with light, standard, heavy if applicable)
Mods: Can you advise on posting links to other sites, i.e. with Dutty etc going to HTCPedia. Some of these Chefs generate a lot of interest, dont really want to exclude these...
Thanks
Jason
EDIT::
I have updated the cooked ROMs page, added a new table near the top, only WM6.5 ROMs WWE versions.
Not an extensive list yet, and some missing information as threads dont have some detail:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_cookedroms
Need to decide on whether the columns are suitable and whether there is more information that would be handy, and/or any other revisions to the layout. If anyone is aware of any of the missing information, that would be great, just go ahead and fill it in...
MODS: Could do with a new thread with a sticky, pointing to the cooked ROM Wiki page once we have sorted it out please.
Chaps,
Now I have put an example table on the cooked roms wiki page, can everyone who is interested take a look and see if we can make this wiki useful...
Thanks
Hello
Nice work! but as you might have noticed there is allready a wm 6.5 section so now we have two.
altough anyone can edit the wiki i was advised by the Mods to first compile the data and then when we have most of the info edit the wiki .
so i suppose we should focus on editing the google spreadsheet i set up.
If anyone wants access please post here.
P.S Jason and Wiggz please PM me a google username so i can add you to the list.
Jay
hi everybody with good mood
i'm new to this forum, new owner of D2....
is here anybody, who will advice me how to tweak my WM?
- touch3d somehow doesn't offer too much user comfort
- colours are too sad
- there are no shortcuts for favourite contact (i would prefer 9x9 matrix)
- facebook missing
- is there possibility to have actual info about currency trade market? (i can see only stocks)
- etc.
i'm really new and i believe, that many of those features i've written is available, but i don't know how to achieve it..
also, I would appreciate some list of apps, which you prefer to install (which are usefull or/and can make fun)
i've read few contributions from this forum.. but i'm lost
what is ROM? Radio? is it safe to change the ROM?
thanks for any tip in advance..
and please stay in good mood
klopotnik said:
hi everybody with good mood
i'm new to this forum, new owner of D2....
is here anybody, who will advice me how to tweak my WM?
- touch3d somehow doesn't offer too much user comfort
- colours are too sad
- there are no shortcuts for favourite contact (i would prefer 9x9 matrix)
- facebook missing
- is there possibility to have actual info about currency trade market? (i can see only stocks)
- etc.
i'm really new and i believe, that many of those features i've written is available, but i don't know how to achieve it..
also, I would appreciate some list of apps, which you prefer to install (which are usefull or/and can make fun)
i've read few contributions from this forum.. but i'm lost
what is ROM? Radio? is it safe to change the ROM?
thanks for any tip in advance..
and please stay in good mood
Click to expand...
Click to collapse
..have a look her. There are a lot of roms: dutty, udk, tom with the new htc sense!
Well, let's see what we can do for you.
Firstly there is a rich mine here of information about all your queries and the way to find the answers is to first and foremost use the search function.
I know it can be a chore and easier to just ask in a genera way, but, members get somewhat weary of answering the same questions over and over again.
Read everything you can and then re-read. It really will pay dividends in the long run.
You will become an established knowledgeable member in your own right and earn respect from other members.
Now on to some of your issues.
My TD2 is (was!) T-mobile branded and out of the box it's a pile of s**t!
Having got that out of the way, I have over 9 years experience with wince (yes the core OS is still wince) and over the last 3 years I have come to know that whatever HTC devices are capable off will be attained by the great work of the more senior and knowledgeable members here.
Leave it to the network carriers and it will never happen or if it does it will be way down the line.
So, you will have to look for a stable cooked ROM that will be tweaked to the balls and really show what the TD2 can do. For that you need to know all about flashing and in the correct manner. Learn about SPL and HSPL and the different versions and what they are for. Read other comments and reviews and then try different ROMs with different radio ROMs. The performance will be enhanced and the device will become more usable
ROMs are the OS (operating system) packages that are flashed to the permanent non volatile memory area of the phone. Radio ROMs are the additional packages that are flashed either along with or separate to the main OS ROM. (to do the latter you need to understand HSPL and SPL). They provide the GPS, WiFi and phone funcionality. A good one will improved operational sensitivity.
If you can progress to that level of understanding then all your other queries will be answered by the knowledge accumulated along the way.
If you get to a brick wall with anything by all means ask. There will be someone who can help, but, use the search first!
Welcome aboard.
believe me or not, you helped me more, than you thought..
I just needed to know the correct keywords..
one more time, thank you
Hi,
Firstly, I don't want to sound unrespectful to developers. It is just a few complains but I admire the time each one spend for creating new roms. There are lots, lots of roms/kernels in the android development section. It's a complete jungle! For a non technical user, I find it really difficult to choose a rom because:
There are no standard table stating what is different with the other. The list described by each developer is not always clear. Especially when he or she sees "aroma", "CRT", "ram hack", "zipalign" without explication. Wouldn't one nice and small sentence be sufficient to explain these terms?
The issues for each rom are not tracked. I think there should be a tracking system like JIRA so that we can confirm if a bug is already described and if it is still present in future release.
It should be clear if a rom is based from stock or AOSP rom (edit: it's not always obvious).
There is no centralized topic explaining the differences. But I have seen there is topic listing roms.
To my mind, there should be in each rom description something like a history, a short sentence like "I have based this rom on this other rom because I feel it lacks this and that." (not always the case), instead of just throwing "hi, [screenshot], how to install this rom?". ^^
I believe what happen is that one user will check the 3 or 4 first roms and will get confused.
Generally speaking, I feel that when you read a rom description from the author, it is addressed to technical people. I think a centralized JIRA (each rom = one project) idea would be very helpful to compare but I don't know if it is easy to implement.
What do you think?
ergosum said:
Hi,
Firstly, I don't want to sound unrespectful to developers. It is just a few complains but I admire the time each one spend for creating new roms. There are lots, lots of roms/kernels in the android development section. It's a complete jungle! For a non technical user, I find it really difficult to choose a rom because:
There are no standard table stating what is different with the other. The list described by each developer is not always clear. Especially when he or she sees "aroma", "CRT", "ram hack", "zipalign" without explication. Wouldn't one nice and small sentence be sufficient to explain these terms?
The issues for each rom are not tracked. I think there should be a tracking system like JIRA so that we can confirm if a bug is already described and if it is still present in future release.
It should be clear if a rom is based from stock or AOSP rom (not always the case).
There is no centralized topic explaining the differences. But I have seen there is topic listing roms.
To my mind, there should be in each rom description something like a history, a short sentence like "I have based this rom on this other rom because I feel it lacks this and that." (not always the case), instead of just throwing "hi, [screenshot], how to install this rom?". ^^
I believe what happen is that one user will check the 3 or 4 first roms and will get confused.
Generally speaking, I feel that when you read a rom description from the author, it is addressed to technical people. I think a centralized JIRA (each rom = one project) idea would be very helpful to compare but I don't know if it is easy to implement.
What do you think?
Click to expand...
Click to collapse
Actually always or it is baseed on stock or aosp or cyanogenmod it's pretty much in every thread i see. it's always described in the information they write.
and a centralized topic where is everything written well. it's for everybody else some like Lg stock ui and some like more clean android
Issue tracking jira i dont really understand i only know that developers are just wanting a catlog if there is a problem so they can see from what the problem is coming from or what it is related.
and that from a short sentence well. every rom misses something it's for everybody different and in almost all roms they are describing where it is based on and they have permission to use other work (the base) but some people are not asking it like the miui team who just took kowalski kernel without permission and they don't even give credit or something like that.
this post is just my opinion how i think it is
ergosum said:
...
Generally speaking, I feel that when you read a rom description from the author, it is addressed to technical people.
Click to expand...
Click to collapse
I do support the idea of asking the developers for more detailed info of their ROM / kernel features, however keep in mind that this is an Android development site - members are expected to have some level of knowledge and / or the will to learn stuff by themselves.
On the other hand, I've seen developers who care enough to spend time writing detailed documentation about their work and yet you'll find people asking questions or posting stuff without even reading the OP or using the search function. This obviously discourages the developer. Who will want to spend hours or even days writing how their stuff works or what are its main features if people won't take the time to read it?
DrummerMuppet said:
I do support the idea of asking the developers for more detailed info of their ROM / kernel features, however keep in mind that this is an Android development site - members are expected to have some level of knowledge and / or the will to learn stuff by themselves.
On the other hand, I've seen developers who care enough to spend time writing detailed documentation about their work and yet you'll find people asking questions or posting stuff without even reading the OP or using the search function. This obviously discourages the developer. Who will want to spend hours or even days writing how their stuff works or what are its main features if people won't take the time to read it?
Click to expand...
Click to collapse
I understand, but I don't ask for hours of well descriptions. One sum-up sentence and one link to a topic where other people has already spent the time should be enough. Example: an developer says "here are the 3 kernels [links]" and the only difference you can tell when looking at the links was "32rh", "16rh", "0rh". I had to guess that "rh" is ram hack and search for what it is. While with just "the ram hack is taking memory from GPU for the CPU", it's a clean and quick explanation. Otherwise people are bound to ask questions when they see this.
As for the JIRA system, it's just more obvious to see, for a newcomer:
how much issue a rom has at the moment
if a troubling issue important for you is described and prevent you from using the rom (so you don't waste time)
help the developer to see easyly what is wrong (instead of navigating through all the post)
help the developer by centralizing all the relevant information for one issue in one page, instead of having these spread everywhere
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.