Related
Hi,
Thanks for all the devs, and also people who started to post nightlies..
I have started to use the Kang CM9 Nightly 20120116 for some time, and I am quite satisfied with it.
However, there are of course bugs/glitches, and I think there should be a thread about what is good/missing/whatever, and when to flash a newer nightly.
Problems I encounter are:
1- Wifi: After sleep, I have to turn Wifi off and then on so that the Nook will scan the wireless networks.
2- Android keyboard: I cannot use the Turkish characters.
3- Some apps are not working: Google Earth, skyscanner
4- Touchscreen lags more than CM7.
5- ADHOC wireless does not work; NC did not see the tether wireless from my phone. (The same phone I used with CM7)
There IS a thread to discuss the nighties. It's the 20-page long thread where the nightlies are posted, in the development subform.
Samiam303 said:
There IS a thread to discuss the nighties. It's the 20-page long thread where the nightlies are posted, in the development subform.
Click to expand...
Click to collapse
Hi,
Well there are actually two nightlies, Kang & Samiam303. I do not know if they are same or has some minor differences. I also do not know if the differences matter at all.
Why I chose the Kang is only coincidence, and also I thought this thread was more a user thread, not a developer thread.
I for myself follow that thread too.
I'm on 0118 and screen feels great to me. wifi after sleep is fine. not going to try a different keyboard because i dont know if i will be able to get it back. google earth and skyscanner both crash due to a java problem. and my phone is dead so i can't test out the adhoc.
If you built your own kang then read through the dev forum and see if they talk about any of your problems. if you use the rom from Samiam303 then you need to post the info in his thread with details. there is no guarantee that any of the devs will see this post.
Hmm, interesting.. I somehow lost the ability to boot into recovery by using the power and N switch.
ROM Manager does the job though..
This thread should be closed
Sent from my NookColor using xda premium
velizet said:
Hi,
Well there are actually two nightlies, Kang & Samiam303. I do not know if they are same or has some minor differences. I also do not know if the differences matter at all.
Why I chose the Kang is only coincidence, and also I thought this thread was more a user thread, not a developer thread.
I for myself follow that thread too.
Click to expand...
Click to collapse
I didn't mean to imply that you're only allowed to talk about my nightlies -- but there are already plenty of threads for discussing CM9. There's the 174-page development thread, the 28 page thread I started for my builds, Eyeballer's "installing CM7/CM9" guide which has 63 pages of discussion, and a 29-page general ICS/CM9 user discussion thread. Starting yet another thread to discuss the nightlies is just going to make discussion of issues even harder for people to find/keep track of than it already is.
Samiam303 said:
I didn't mean to imply that you're only allowed to talk about my nightlies -- but there are already plenty of threads for discussing CM9. There's the 174-page development thread, the 28 page thread I started for my builds, Eyeballer's "installing CM7/CM9" guide which has 63 pages of discussion, and a 29-page general ICS/CM9 user discussion thread. Starting yet another thread to discuss the nightlies is just going to make discussion of issues even harder for people to find/keep track of than it already is.
Click to expand...
Click to collapse
Hi,
That's OK. But when a thread goes lots of pages long, it is not easy to get the information you are seeking, especially when lots of things are happening quickly. Yesterdays info is already very old.
Besides, I think, some issues may be build specific, your nightlies, and eyeballers are different. Which means, if I ask about something about eyeballer's nightly I can not get an answer in the thread about your nightlies, etc. etc..
MODS PLEASE MOVE THIS POST. I AM SORRY FOR POSTING IT IN THE WRONG SECTION.
I don't mean to be a downer on people who've done the hard work in porting or making a working custom rom but is there point to AOSP Roms if there is no working camera? I mean isn't it a pretty big functionality that needs to be working for the ROMS to be actually released as working?
Perhaps maybe its just me who thinks if you buy the Z1 based on the fact that it has a good camera you'd want that one minor feature.
Just a thought I decided to share.
(PS: When I say camera isn't working I mean complete functionality not "It just can't focus. It does work!"
Now you have seen the point of the Q&A thread (i.e. its a place for posting questions that is better than the original dev forum) I think its time to answer your question.
the point is this is a developers forum, for developers and by developers. Not every single rom in this forum is a finished article but are works in progress. They are not here for you to be able to pick through and make your phone "cool"
They are here as on going pieces of work for people to help develop and work on.
Please read this
This is the highlight of that post and should be the last word in this thread
XDA-Devs is about developers & hackers helping each other and working together to get the most out of our devices by understanding them better than most.
XDA-Devs is not about helping everyone who wants a "Kewl bit of kit" make their phone better than the guy next to him.
Click to expand...
Click to collapse
Well, work done now doesn't have to be done in the future anymore so if they iron out all the issues already that saves a lot of time in the future right? Sure, without a working camera there will not be a lot of people using them, but I still hope sony fixes this issue in the future and when they do we at least have a bit to choose from already.
That and the fact that it might be more for themselves, to develop and get some experience or work on things, then for the end user.
gregbradley said:
Now you have seen the point of the Q&A thread (i.e. its a place for posting questions that is better than the original dev forum) I think its time to answer your question.
the point is this is a developers forum, for developers and by developers. Not every single rom in this forum is a finished article but are works in progress. They are not here for you to be able to pick through and make your phone "cool"
They are here as on going pieces of work for people to help develop and work on.
Please read this
This is the highlight of that post and should be the last word in this thread
Click to expand...
Click to collapse
Well said my friend.
THREAD CLOSED
I wanted to download the ROM "j00m Kitkat 4.4.2 optimized bionic" for the Nexus One. But the user j00m has been disabled and the thread is deleted. Anyone know what happened?
I can't say for sure but as I've seen his Roms posted they appeared to be little more than rip offs of the couple nexus1 devs left, also the op of the threads pandered for money and thanks. My best guess is the real developers got annoyed and finally had a word with moderators.
This is all just speculation though
Sent from my Nexus 7 using XDA Premium 4 mobile app
I think he doesn't have accept from developers to port their ROMs...
Ok, thanks.
I thought: "His ROMs would Malware? And for that reason have expelled"
nickdimoni said:
Ok, thanks.
I thought: "His ROMs would Malware? And for that reason have expelled"
Click to expand...
Click to collapse
No malware, I was using his rom [edit: and am using it now as my daily driver]. I actually thought it was [and still is] the best post-Gingerbread rom available. It was basically Evervolv slimmed to 210mb system and a few tweaks for "lazy people" - details here. The mod who closed his thread cited 2 reasons:
j00m's rom wasn't "different" enough (tho I don't know how he can make that call as it was clearly different enough for me and others to prefer it),
j00m didn't get permission from texasice (isn't everything open source? why is permission necessary?)
Ok, thanks for all.
In your explanations I'm calmer
Rules are rules.
too bad, he was one of the best in here, his rom is amazing,
but rules are rules
Just to clear up some stuff I saw:
abemore said:
[*]j00m's rom wasn't "different" enough (tho I don't know how he can make that call as it was clearly different enough for me and others to prefer it),
[*]j00m didn't get permission from texasice (isn't everything open source? why is permission necessary?)
[/LIST]
Click to expand...
Click to collapse
The ROM was removed because it was essentially Evervolv taken from another developer and called his own. We do not allow that without permission as that is taking someone else's work, slapping on a few tweaks and calling it your own. No credit to the original developer, no mention of where the base came from, nothing. It's disrespectful, and is akin to someone taking the lunch you painstakingly made, adding pepper and then proclaiming it's his, with big donation banners around the plate of food. Not what the original developer would like, yes? That was why his ROM was removed. As for the bit about open source, j00m did not post the kernel sources he used, which was violating GPL and against the spirit of open source. While Evervolv is indeed open source, credit must be given if it is used as a base, and permission must be granted for that by the original developer, as we must respect the work of others as well. Without that, or if permission is not granted, the ROM will be removed from XDA.
TL;DR:
Credit the developers of the base
Ask for permission
Post kernel sources
I hope this clarifies some of the issues I saw. Due to the nature of this thread, I will have to close it as I already saw instructions on evading the ban. My PM is however open to anyone with further queries. Thanks
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.
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Same feeling here..!
Yes,.. well said,
Need support for Official TWRP. need adb sideload feature.
Please developers and maintainers, consider lineage 16.0 and omni rom, these two are major famous os distro, but not maintained for our device.
All the points are true and devs should at least try to fix the recovery. I remember once my old device had a problem with Cwm when reboot to recovery was performed the phone bootlooped so a stable recovery is a basic need for development.
Also now a days devs seem to make telegram groups and post their work there by giving reason that xda has a lot of rules, the rules are for everyone's good and if you find a rule which should be changed or modified ask the community they'll help.
On xda devs get to show their skills in front of an open audience instead of a closed group. It's like driving on a empty track vs driving in a formula league. The league has more rules than no rules empty track but one can outshine only in a league.
So try to support the xda community and also have great time. Happy developing.
navjottomer said:
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Click to expand...
Click to collapse
Very thoughtful! Resonate the same things brother.
Most annoying - 'Bugs - you tell me' when they are crawling around about to eat your eyes out!!
Oh and the spammers - next level entitlement for free stuff.
Note - Same as OP and with all due to respect to devs/contributors.
Can we request the developer community to focus on quality and not on quantity, found more than 20 roms, but not one which can maybe support OTA and be used as a daily driver for non flashoholic community?
Ie flash once (or dirty flash forever) and forget type of use cases, we had during resurrection remix days.
Other than that I completely agree with the opening comment of the thread.
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
Due to the insane quantity we find similar bugs on different roms, that's kinda futile..
Not one is working on lineage 16 i absolutely don't understand why.
I just bought a new ZF MPM1 and roaming around the forms ,i feel like you are absolutely right!
navjottomer said:
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Click to expand...
Click to collapse
bro...devs are also humen, they also have life...
they are doing what u cant do..
building a rom take about 10-12 hrs ( if not using gclouds), with gclouds 3-4 hrs(if less error occurred).
they are developing when they get free time.
give them time, not a big thread to read.
And it will be great if you provide them LOGCATS, so that they can look and fix those bugs.
saurabh1234 said:
bro...devs are also humen, they also have life...
they are doing what u cant do..
building a rom take about 10-12 hrs ( if not using gclouds), with gclouds 3-4 hrs(if less error occurred).
they are developing when they get free time.
give them time, not a big thread to read.
And it will be great if you provide them LOGCATS, so that they can look and fix those bugs.
Click to expand...
Click to collapse
first of all i thank my dear X00TD's ROM developers for the quick and active development.,
Bro,
we are not pesking developers to add this thing and that thing. we are requesting necessary thing that needed for stable development. every month we are getting new rom project or port rom. but nothing is different.
I am custom rom user since samsung galaxy pop( galaxy mini). previously every community build the cwm recovery (project closed) and make it stable and make it compatible with all the roms. and parallely start developing CyanogenMod (now lineage). then otherr rom developers are uses cyanogenmods sources to build their own custom rom.
firstly,
stable recovery needed. our twrp is still in beta stage.
and still in unofficial release. the following problems i faced, adb sideload, otg support not stable, aroma also not working.
secondly,
lineage os is traditional one and best aftermarket os. and the root for the many custom roms. but we are not concentrating on this os.
nxp amplifier not yet fully supported for current release of pie custom roms. i dont know what is the problem behind this issue. but none of the thread mentioned about it. may be asus not released source for it(idk).
anyone can build rom and fix bugs and release here. sorry to say, most of us don't know this android custom rom development.
and telegram groups are not worth. mostly some guys talking off topics. and i mostly ignore if unread msg is more than 500( mostly it goes above 1000 per day). so i miss what developers told and published news.
anyone,
please make a thread to how to take a logs, because most of us dont know how to take logs.
please make a index thread for list roms and kernel and about their present bugs, last release, current development status.
please make a single thread for noob guide/new user, and mention all the common problems and its solutions,
please make a thread for common bugs in roms and kernels and talk there for what we need to do solve this bugs.
if possible, update possible reason for the bugs
sorry i dont know english much. ya i know did more grammer mistakes.
i'm really sorry if i hurt anyone.
#OnlyRequesting
#NotDemanding
What else can you expect? Phone has been marketed as a mid-to lower middle tier device (price <$200/€180) i.e. it will not attract big (known / reputed) devs. phone was released in few countries so lower economic tier ppl in these countries will flock to this phone....natural to expect slovenly behaviour, rude attitudes in the community and lack of stability and direction of growth for the phone's rom development, since these ppl (students, mostly) have little knowledge of ethics, professionalism, and are likely to throw the device away for the next shiny fondleslab in the same price range within a year. Some devs are there, but the general populace they pander to is reckless, raging, mercurial youth with little respect for their work and little concern/care for whom they offend, so they can't stick to these guidelines as you speak of....after all they too hold some other work/profession as their main job and rom development is just an after-work thing....
Eat whats on table coz you aint paying ****.
I agree with what you said.
I've been longing for a stable Pie LineageOS or stable AOSP for months. But so far it's been no news.
well, it can't be helped
My actual plan was to just use the stock rom (since it was pure aosp, kinda), but since the pie version still buggy I have to use the custom version, which is pretty meh than my previous devices (xiaomi)