I have been on the Nexus 6 since early December 2014, and for me, as with many others, the Nexus 6 was my entry point into the pure Google experience, and my simultaneous departure from TouchWiz. From the beginning, I was a noob on this device.
So, after 4 short months, I have found that the rom threads have become congested with endless questions that are not germane to the given rom. The more popular a rom becomes, the problem intensifies.
I can imagine how frustrating it must be for a developer whom has worked hard, flung his or her creation to the xda shadowed wilds, only to return to a thread that has become a thicket of repeated questions.
Compounding the problem is that each developer has a different approach as to how he or she wishes his or her thread to be managed, which in turn can be confusing to any user. Some developers seem happy to remain ensconced in the daily comments, while others have a palpable disdain for off-topic quotes.
Irrespective, I think each has a tipping point, and thus I am sure that none is immune from becoming a bit jaded after a time.
And yet, we still have the very real phenomenon that this device has a learning curve, is available across the globe, and thus the questions still recur. Further, it is in many people's natures to either want to help or at least be cautious prior to rooting their device, etc.
So, I thought it would be fitting to provide a place for all to ask whatever they want. As the title clearly states, this is a noob friendly place, so please feel free to ask whatever you would like about this device. I am certain that all here on these forums would rather you learn what you need prior to availing yourself of the amazing array of resources in the development and themes and apps sections of these forums.
A few preliminary guidelines for this thread:
This is a noob-friendly thread, so ask whatever you like
Read the initial posts of the rom thread, as well as the last 10 or so pages of that thread, before you flash the rom you want. It will give you an idea of how the developer handles his or her thread, the tools you need before you get started, and
Please respect your fellow forum members, developers, and the moderator staff. Moderators have a thankless job, and I can assure you that it is absolutely no fun spending hundreds of hours on what amounts to a volunteer position without benefits.
Towards that end, please read the rules; they are the first post on every forum here on xda.
Thank everyone that develops, and please donate to anyone whom you believe is worthy of your extra gratitude. Donations are never required, but they do motivate those that do the hard work on these forums.
Never downgrade your bootloader. Ever.
I’ve split this into categories so that folks will have some basics right upfront.
1.First Use
1.1:You almost certainly will want to unlock your bootloader, inject root, recovery, etc.
I suggest reading the All-in-One Beginner’s Guide, where you’ll find everything you need to get started.
1.2. Learn Fastboot:
Yes, you have a Google device, and it is very easy to flash anything you want with a few simple command lines. Put bluntly, on Nexuses, the manual steps are very easy.
Hie yourself to this authoritative thread written by the prolific dev and highly respected forum member @rootSU.
1.3:Toolkits: Toolkits are a fantastic way to do all of this from the jump. There's nothing wrong with toolkits themselves; they can be great, useful tools, but please learn to do the steps manually. Why? Simple. If anything goes wrong, and it can, knowledge of fastboot will save you; no knowledge of it, you're waiting on help from others, or learning from scratch that which you should already have learned. Further, should help arrive, that person helping you is bearing two burdens, helping you first learn the basics of command line, and solving your problem. That is downright unfair. OK, onto the toolkits. You can find them in the development sections, specifically:
Wugfresh's Toolkit for Windows Operating System
Nexus One-Click Mac Toolkit for the OSX
Skipsoft Unified Android Toolkit for Windows
1.4: Decrypt or Not Decrypt:
Please note: Decrypting your device will wipe your device, so if you are going to decrypt, please do so before taking all of your time to setup your device the way you like it.
IF you want to remain decrypted, put the zip file located in this thread on your device, throw it in your cloud storage (Dropbox, &c), keep it in your pocket, think well of that file.
IF you want to remain decrypted, that zip should be the LAST file you flash before any new rom or kernel is flashed, or if you are unsure if a rom has a kernel that will force encrypt your device.
There are differing opinions as to the wisdom of decrypting, and I don’t care whether you think it is better or worse; people want to do it.
You can learn more about it here, and can accomplish the task using the link previous link or using any one of the aforementioned toolkits.
1.5: Recovery:
You almost certainly want to make a backup of your device prior to tweaking, flashing an updated nightly, or testing a new rom. Recovery for our device can be found here.
You may want to put a nice theme on that TWRP, go here. Hint: The developer whom does those themes keeps up with each iteration of TWRP, and if a new version requires a new theme, check the theme thread before you update your recovery.
1.6: Starting Over
I believe that this community owes a special thanks to @Q9Nap and @scrosler as each has provided us with amazing tools to return to stock or upgrade your device from 5.01/5.02 to 5.1, sans the need to revert to stock 5.01.
Please go to http://forum.xda-developers.com/showthread.php?t=3066052 thread for flashable zips of entire 5.1 roms or modems ,or this Android File Host page from SCrosler for flashable 5.1 modems + bootloaders...https://www.androidfilehost.com/?w=files&flid=23050
https://www.androidfilehost.com/?w=files&flid=23050
2. Choosing a Rom: Roms generally fall into four discrete categories:
2.1: Stock-Based – these are hewn from Google source, and typically come preinstalled with everything you will need to be up-and-running. Whatever tweaks, performance or otherwise, are added, the rom will most certainly similar to stock, hopefully better than stock.
2.2: AOSP-Based – these are built from the Android Open Source Project, and purists may think of them as closer to what Google intended. You will typically need to flash a Google Apps (Gapps) package separately from the rom itself. Some of these have inline kernels, or stock kernels, but they typically have everything you need baked right into the mix. There is an incredible variety of unique and wonderful roms from which to choose that fall into this category.
2.3: Original Development – Although the lines tend to blur, suffice it to say that roms in Original Development contain something original that merits a rightful place of its own, away from the crowded Development Forum. You will find kernels as well as complete roms in this section.
2.4: Hybrids – The vast majority of roms fall into this category. Much of the joy of Android is customization, and most roms in this category are feature-rich and packed with things, almost more than you will ever use.
Customization - Enhancing the Senses
Rom Customization:
Roms are popular and highly useful, but they are also fun. Instead of using a boring, stock phone laden with what amounts to another's idea of what you should have on your device, you are in control. This starts with how the phone looks. Yes, your phone can and should look exactly how you want it.
Disenthrall yourself from the madness that is a stock looking phone and apps, and stare with wonderment at beautifully themed apps.
1. Hard-Coded Themed Apps:
Anyone can run a themed app, even on a stock, rooted rom. These forums are riddled with themed app threads. Some suggestions to start:
1.1: Team BlackOut, the hardest working devs on xda are there, please go into their thread, enjoy the camaraderie and the beautiful apps they make. Be sure to thank and donate if you are so inclined. You will find themed versions of scores of apps, all available for free from their updater app.
1.2: XDA Recognized Themer @cerj has done a terrific job theming many apps on his own, and of course with the help of other themers. He is a terrific resource and a good friend. Check out his Blue DeLucia and Krome-X apps.
2. Theme Engine and Layers
Many Non-Stock Roms make use of one of these two basic tools that allow you to theme your entire phone. Suffice it to say that these are mutually exclusive means of attaining a beautifully themed rom without much hassle on your end. The CyanogenMod theme engine has its fans, and the fine devs doing the Layers app consider their work stellar (as they should); both are excellent.
2.1: Layers: If your ROM has Layers, and the app is not already on your phone, you'll need to download the free app from the Play Store. You'll find an abundance of themes in the Official MEGA RRO Layers Overlays Collection.
Special mention to one of the finest themers whom I've come to know on these forums; as RRO has had met the steep ramp-up with stunning strides, this terrific dev has been there, every step of the way.. @daveyannihilation, a tosser, wanker, and a very Gary dude, please help...I mean thank this man. He's everything and more. Please help me, inasmuch as I'm far more concerned about the degree to which I'm both a wanker, and a tosser, not to mention completely Gary.
2.2: Theme Engine: If your rom incorporates the CyanongenMod 12.0/12.1 Theme Engine, you can find a ton of beautiful themes in the Official MEGA CM12 Theme Engine Thread.
Please buy the themes you love. Free themes are terrific, but I always believe that people are more motivated to continue delivering these terrific tools if you support their hard work. Buy the damn themes, and don't be a cheapskate...there's enough whining in these forums to make most want to wretch.
Kernels and Tweaking
If you wish to flash a kernel, here are a few guidelines to get you started
Note: Most all of this was written entirely by @wrongway213.
1. Kernel Basics:
1.1: Stock Kernels: You can keep a stock kernel if that is with which you are comfortable. The stock kernel will force encryption, and there are modified stock kernels that will not force encryption.
1.2: Custom Kernels:
1.2.1: Hotplugging: Hotplugging is basically the background process going on telling your phone when it needs to bring CPU cores on and offline. This controls how much power your phone consumes - both how much battery it drains and how snappy it feels. You can use a kernel tweaker app (more below) to set all kinds of things in the kernel, including how hotplugging is done. Different kernels have all sorts of different hotplugging options.
As of 5.1, stock kernel uses all four cores online at all times as opposed to hotplugging. This is said to save power. Some kernel developers have adopted this as the default for their custom kernels, but they are still tuned very differently than stock. The user can still choose to revert back to hotplugging if they prefer it. Prior stock kernel, including 5.0X Lollipop, use something called MP-Decision to scale your frequencies. Some are of the opinion that MP-Decision is entirely too aggressive in how it handles this. It attempts to give the user a snappy and smooth experience, but in the end it mainly drains battery. The same smooth experience can be achieved via hotplugging properly on a custom kernel, and your battery will thank you for it.
1.2.2: Governors: Another awesome thing you can do when you flash a kernel is control the governor it uses. Stock kernel uses an interactive governor, which responds to user input and is generally considered to be a pretty good governor, even for custom kernels, However, it is often modified on these kernels, or at the least assisted with hotplugging in a different way than stock. This governor has been modified by @Imoseyon for leanKernel, one of the most popular kernels for our device, and a great place to start if you want to know if custom kernels are for you or not. Some prefer to use conservative, which is much less jumpy than interactive - meaning it does not scale frequencies up or online cores as quickly as interactive. This governor has been heavily modified for our device by @franciscofranco (Franco Kernel dev), so it is a much more viable option for those whom want to conserve battery and still get great performance. There are many different governors offered with different kernels - you can change your experience on the very same kernel by changing governors sometimes. Or you may find that you flash a new kernel and find a whole new set of governors that are more your style. This is all about trial and learning what you like, as none of us can know what is best for your use.
1.3. Kernel Use and Utility:
1.3.1: Wakelocks, An Example
A kernel can do many things if the kernel dev chooses to make it, or to give the user the option to avail such options, or can be omitted entirely if running stock. Though not the source of your wakelocks, kernels can disable wakelocks can control or disable them. This is a good example of the separation of a kernel's ability and a kernel's use.
1.3.2: The Domain of the Kernel:
Many kernel devs choose to leave the kernel footprint small, and allow the ROM side of things to handle as much as possible. Some kernels use the existing ramdisk that comes with the ROM instead of inserting their own to ensure they will play nice with all roms. Other kernels are highly customized and completely and totally change the feel of your device. Most are somewhere in the middle of these extremes.
1.3.3: What Your Kernel Does Not Control:
Your kernel does not control your radio, your WiFi, etc, so thus your phone calls, your data, your mms and sms messages are not impacted by flashing a kernel. Sometimes flashing a kernel may somehow cause something that is controlled by the ROM side of things not to work correctly - this is not the norm, though. If you are having these issues, you should look to your ROM first.
1.3.4: Random Reboots:
Random reboots are something that may be caused at a kernel level. If you encounter one, you should immediately on boot (ie, right after the random reboot) open your file explorer go to the folder:
sys/fs/pstore
There should be an annotated-ramoops file and a dmesg file (think of these as kernel logcats). Open the files as text, copy and paste to www.hastebin.com and send the link to your kernel developer. This will help him or her determine if it the reboot was caused by the kernel, and if it can be fixed.
1.4: Sound Practices:
1.4.1. Avoid Multiple Kernel Tweaking Apps:
The use of multiple kernel tweaking apps is contraindicated. If your rom comes with a performance app but you like to use your own instead, freeze your rom's performance app in (using the built-in App Manager, or with an app like Titanium Backup) and clear its app data prior to using your app of choice. Most kernels have an app that is either directly associated or supported by them, or recommended to use with them. Find this out in the thread before you tune your kernel, as having the right options available and interfaced correctly makes it much easier to do so. It's also good practice if you have flashed a custom kernel already to re-flash your rom before flashing another to ensure settings stick properly. This is not always necessary, but it only takes a minute and it's better safe than sorry.
1.4.2: Default Kernel Settings or Using Terminal Command Line:
Some kernels don't even require an app at all. A few of them are tuned on initial setup via Aroma installer - you set your values and can leave it at that. Others can be tuned directly via terminal emulator.
1.4.3. Kernel Tuner of Choice:
Most kernels require some sort of an app to set your values. If your kernel does not come with a particular app associated with it, there are a few options for you. A popular option has always been Trickster Mod. This app offers the basics that you need if using a kernel that does not have a whole lot of odd modifications and is good for beginners who are using a kernel with no recommended app. Advanced users often use Synapse - it is a very confusing app and definitely not for beginners, but it gives you control over basically everything your kernel has to offer. Kernel Auditor is something in the middle, as it does not allow you as much control (or confusion) as Synapse, but it can do a lot that Trickster can't. It's a great starting point for those of you using a kernel with needs Trickster does not meet, or a good place to jump to if Trickster is just getting old, but you're not ready for Synapse.
1.5: Afterwards:
To be sure, there is plenty more reading to be done, depending on which kernel you choose to flash and how advanced you would like to get with it. This is just meant to give those of you who don't know why they would want to do something like flash a kernel a starting point. The decision is yours.
Happy flashing!
Thanks for this man! I agree this needed to be done. It will be very helpful!
Войн Дух
So... If I have a OnePlus One can I use the decrypt file you posted in the second post? I'm kind of a noob... [emoji5]
In all seriousness, XDA is better for having someone like you here to help out.
Watch closely people... You might learn something.
Now I just need to get one lol
Awesome work buddy!
If you need more posts added in or want to transfer a post ownership to another person, just let the mod team know (or you can hit me up as well). Anything to reduce the number of non-essential, non-logcat-attaching posts from the Dev threads is most assuredly welcomed.
Good job and keep up the good work.
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
rootSU said:
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
Click to expand...
Click to collapse
I knew you'd pounce on that.
My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things.
Sent from my Nexus 6 using Tapatalk
micmars said:
I knew you'd pounce on that.
My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah sorry I always do.
Its nothing personal. Nothing to apologise for. I just think a little disclaimer could be put in. I can draft a very small sentence if you like... Or not
Excellent idea, this thread is, Mic - thanks for endeavoring to provide a one-stop-shop resource for all. Let me know if I can be of any assistance along the way.
Very useful thread. Will be checking in to help whenever I can. Thanks @ micmars
TaPpEd FrOm My N-sIx
rootSU said:
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
Click to expand...
Click to collapse
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
DebianDog said:
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
Click to expand...
Click to collapse
Yeah i agree. That's why it should be a disclaimer rather than an order
DebianDog said:
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I use folder sync as a plug in to Tasker.
Every time I close my camera app, I use bash shell to look for new files in DCIM and move them to a holding location. I then use folder sync under the same trigger, to open up an SFTP connection to my NAS at home and upload the photos immediately. There is one draw back though. I was taking 4k videos the other day and trying to push 1.5GB over sftp voa hspa is not good for battery, so I need to revise that one.
Also a run a times folder sync every couple of days syncing up my /sdcard with my NAS backup directory, over WiFi whilst I sleep.
Also every Saturday at 3am, my phone reboots, takes a nandroid then syn a that to my NAS too.
As you can imagine, I find it difficult to lose files
DebianDog said:
What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way
Click to expand...
Click to collapse
Same here. Only takes a minute.
DebianDog said:
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
On the go storage, tiny little things, I know many themers, and rom devs, use the crap out if them.
I have seen these things sold at very reasonable prices, at brick-and-mortar retailers or online.
I personally back up my entire card to my computer on a weekly basis, and throw the entire thing into my Dropbox.
Sent from my Nexus 6 using Tapatalk
Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response..
Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo
cerj said:
Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response..
Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo
Click to expand...
Click to collapse
your phones cpu can get to 100C. thats when itll automatically shut down/reboot to cool off. but try as hard as you can, i bet youll never reach it. anything below is normal, depending what you are doing. now you say hot, whats your cpu temp? as feel does not give you any temperature. all feel does is tell you if something is hotter than or cooler than your hand. and if your hand is cooler, itll make the phone feel much hotter. so, when talking about being too hot, we need an actual temp to go with it. i say that because many people report a hot device, when the temp is around 40C, when normal body temps average around 37C.
Related
In the Super D thread, somebody suggested a 'ROM Hall of Fame.' I've decided to do something similar. This thread is about the ROMs that I recommend for different uses. It's difficult to explain, but you'll understand soon enough. Anyway, let's get on with it.
For Newbies/Inexperienced Users
For people who are just getting started with rooted Android, there's only really one recommendation that I can make, and that is, of course, the ever-popular CyanogenMod. This is an Android 1.6 build, and it's probably the most famous of all custom Android builds. Originally built upon JF's build of Android, CyanogenMod has now become a build in its own right. It's incredibly stable, it's fast, and it's really all that you'd ever need for your phone. If you want something that's simple, but still really good, CyanogenMod is the way to go.
For More Advanced Users
There are two builds that I can whole-heartedly recommend for the more advanced Android user. In the same way that CyanogenMod started as a modification of JF's build, these two builds are heavily based upon other popular builds of Android.
The first of these is WG-Build, a modification of CyanogenMod. This is my current everyday ROM, and I really like it. For more information on the exact changes, check out the thread, but the main difference between WG-Build and CyanogenMod is the kernel. Wes has been working hard on his custom WG-Kernel, which is the driving force behind the speed of his build. It comes in several different varieties depending on what you want. I use the CFS with RAM Hack, because CFS is more stable than the faster BFS, and the RAM hack is of great use too. WG-Build is one of the fastest builds you'll find, and it is my personal recommendation.
However, you may prefer Super D. This ROM is essentially a modification of a ROM by Dwang, although it has come a long way since then. This ROM is thought by many to be the fastest available, although from personal experience, there is little difference between Super D and WG-Build. This is more of a personal choice as to which build you prefer, so try them both. I prefer WG-Build, but you may prefer Super D. It is your choice.
Eclair ROMs
TO COME.
Hero/Sense ROMs
Again, TO COME.
Guys, is this a good idea? If you think it is, let me know, but if you think it's a waste of time, then I'll drop the idea.
Yeah man keep it up, im on cyan but if your saying the other roms are quicker ima give it a go!!
Might I add, try and link to as many pages as you can!!!
In my opinion this idea is good. There are many roms for the g1 available atm...
But i would modify it a bit:
I would prefer a kind of table or database with a quick overview about the current ROMs.
Having this, u can still make recommondations.
Example:
ROM: Eclair_2.1-v1.5 G1
dev: manup456
base: 2.1
devices: MT3G 32B
Features: Camera, LWP [...]
Issues: FC latin_ime [...]
.
.
.
In addition, we could maybe collect ratings (poll?) on facts like speed, look, stability... so that everybody can pick his rom according to his personal criterias...
Che123 said:
In my opinion this idea is good. There are many roms for the g1 available atm...
But i would modify it a bit:
I would prefer a kind of table or database with a quick overview about the current ROMs.
Having this, u can still make recommondations.
Example:
ROM: Eclair_2.1-v1.5 G1
dev: manup456
base: 2.1
devices: MT3G 32B
Features: Camera, LWP [...]
Issues: FC latin_ime [...]
.
.
.
In addition, we could maybe collect ratings (poll?) on facts like speed, look, stability... so that everybody can pick his rom according to his personal criterias...
Click to expand...
Click to collapse
Yeah, this is exactly what I'm aiming for. It's sorta similar to the ROM Database at AndroidSpin.com, but it's a different idea. I might actually ask Simon if he can help me with it.
bolmedias said:
Yeah, this is exactly what I'm aiming for. It's sorta similar to the ROM Database at AndroidSpin.com, but it's a different idea. I might actually ask Simon if he can help me with it.
Click to expand...
Click to collapse
But at androidspin there are too many details and no userrating. And it's not up2date
ATM there are daily new roms or updates, and the only way to make rom-overview useful is to keep it updated
Sounds very good and if it's kept simple and informative this will be very usefull - not only for newbies
I will keep an eye on that
Che123 said:
But at androidspin there are too many details and no userrating. And it's not up2date
ATM there are daily new roms or updates, and the only way to make rom-overview useful is to keep it updated
Sounds very good and if it's kept simple and informative this will be very usefull - not only for newbies
I will keep an eye on that
Click to expand...
Click to collapse
I'm gonna ask Simon if he's interested by this idea, just to see if he is or not. But I will try and maintain this myself, for sure.
The idea is good, but, how do you decide which way is more informative? If you settle on a "feature's list" like Che123 suggested, then you take out the actual experiences of people who've used the roms out. On the other hand, if you approach it like you first did, stating your opinion on which roms are best suited for what, then the information is narrow (limited only to the roms YOU've tried), subjective, and (some might argue) possibly skewed. A combination of both, I'm afraid, would ultimately pick up more of the flaws of either method than the benefits.
I personally believe the problem lies in the solution not being so clear-cut. There's just too many roms for all of them to be drastically different, and most often the difference between them is the availability of feature(a) against feature(b). In some cases, the only difference is the developer, or the name of the rom! (but just a few cases.)
I think an approach that might work, maybe, would be to make a list with:
ROM Name:
Feature 1: [X]
Feature 2: [X]
Feature 3: [X]
Feature .: [X]
Feature .: [X]
Feature .: [X]
Feature n: [X]
Highlights:
Opinions:
Features 1-n would be what we consider standard on roms (a2sd, compcache, swap, etc). We'd list highlights with things that actually make the rom different from others, for example, WG's kernel against CM's kernel, or X's themed rom as opposed to Y's un-themed rom, etc.
Opinions is where the meat would be. User experiences would be listed so that we know to expect force-closes, or slowdowns, reboots, or maybe just a smooth-sailing all around. Might even be a long comment section for different users and with an option to separate good opinions from bad opinions from neutral opinions so that we can read all the bad or all the good in one fell swoop rather than have to follow through the usual ranting and fighting that goes on at the forum already.
Anyway, I'm rooting for this, I just wish it were easier.
And to further add to what you suggested in your original post; another field that describes "Target Audience:" (Beginner, Intermediate, Advanced, Multimedia, Professional, Linux Power-User, etc.).
Fount this over in the Sapphire section
http://forum.xda-developers.com/showthread.php?t=618220
It looks nice so far but is still short of data...
Maybe you're interestet in collaborating with him?
jubeh said:
The idea is good, but, how do you decide which way is more informative? If you settle on a "feature's list" like Che123 suggested, then you take out the actual experiences of people who've used the roms out. On the other hand, if you approach it like you first did, stating your opinion on which roms are best suited for what, then the information is narrow (limited only to the roms YOU've tried), subjective, and (some might argue) possibly skewed. A combination of both, I'm afraid, would ultimately pick up more of the flaws of either method than the benefits.
I personally believe the problem lies in the solution not being so clear-cut. There's just too many roms for all of them to be drastically different, and most often the difference between them is the availability of feature(a) against feature(b). In some cases, the only difference is the developer, or the name of the rom! (but just a few cases.)
I think an approach that might work, maybe, would be to make a list with:
ROM Name:
Feature 1: [X]
Feature 2: [X]
Feature 3: [X]
Feature .: [X]
Feature .: [X]
Feature .: [X]
Feature n: [X]
Highlights:
Opinions:
Features 1-n would be what we consider standard on roms (a2sd, compcache, swap, etc). We'd list highlights with things that actually make the rom different from others, for example, WG's kernel against CM's kernel, or X's themed rom as opposed to Y's un-themed rom, etc.
Opinions is where the meat would be. User experiences would be listed so that we know to expect force-closes, or slowdowns, reboots, or maybe just a smooth-sailing all around. Might even be a long comment section for different users and with an option to separate good opinions from bad opinions from neutral opinions so that we can read all the bad or all the good in one fell swoop rather than have to follow through the usual ranting and fighting that goes on at the forum already.
Anyway, I'm rooting for this, I just wish it were easier.
Click to expand...
Click to collapse
I think the soloution is a mix of everything: Facts, general user rating and your recommondation.
A featurelist for the common features, like you mentioned above are a good idea too...
If we got all the features-data in a database we could also build a automatic rom-chooser
i would add following things to the list:
Base: (there are currently 1.6, 2.0, 2.01, 2.1)
Supported Devices: (there are always people flashing a wrong rom and wondering why it's not working )
and a link to the thread of course.
domenukk said:
Fount this over in the Sapphire section
http://forum.xda-developers.com/showthread.php?t=618220
It looks nice so far but is still short of data...
Maybe you're interestet in collaborating with him?
Click to expand...
Click to collapse
I wasn't really intent on doing a piece of software, and besides, it misses the point.
Jubeh, I think that you've hit the nail on the head there. What I'm thinking of with this thread was to eliminate the need for people to read through each individual ROM's thread in order to find out if there are any problems, how fast it is, basically exactly what you've suggested. It's about user experiences.
Actually doing this as a forum thread will be quite difficult, though. Any ideas on how we could do it?
which are the differences between cfs wg build and bfs wg build?
marcocrash said:
which are the differences between cfs wg build and bfs wg build?
Click to expand...
Click to collapse
Stability and Speed. BFS makes for a faster ROM, but Wes himself has said that there is an issue with memory leakage. CFS is not as quick, but it's far more stable.
This is the exact sort of question that I want this thread to answer about each ROM.
i don't really like the idea of an desktop app either.
I would like to see something web-based. But as you said: This won't be very good as forum thread. Maybe you could ask someone from xda, if they are willing to give you same webspace for this project. Maybe in cooperation with other users you could build a database for all kind of devices
Somebody could develop an app thats based on the database of the software maybe?
for afaik his software uses some sort oft sql. maybe eaven mysql. have a look web developers
http://forum.xda-developers.com/showthread.php?t=618220
Stability and Speed. BFS makes for a faster ROM, but Wes himself has said that there is an issue with memory leakage
Click to expand...
Click to collapse
Wes himself uses BFS+Ramhack, according to his signature
OpenVPN
Please add that OpenVPN works out of the box in Cyanogen ROM, just install Tunneldroid or openvpnGUI.
In Dwang, it could support it, but you need to overwrite some libraries and add openssl and crypto libraries, thou Dwang rom has TUN built into the kernel.
I have not tried OpenVPN on super-D or WG.
*deep breath* I apologize in advance to the mods if this starts off yet another ROM flamestorm, but here goes.
I was running the original leaked froyo build, but it was having issues with slowness and just not being responsive, so I decided to look into something more up to date for my phone.
Did a bunch of quick reading and decided that Perception seemed to be rich on features, and being on beta 9 a good history of active dev support, so I loaded it up.
...
what I got reminded me of something a PC warez group would put out for a keygen app. I don't want to see an advertisement for the dev on the lock screen, etc. Don't want to put down the efforts the dev(s) put into the release, but it's got waaaaay too much bling for my taste.
Can anyone give recommendations for a ROM that's solid, and actively maintained to add in new features to benefit it - that doesn't have a bunch of l33t bling?
Once again apologies if this caused headaches for the mods, but asking general consensus that does keep current on dev for this device and explaining what I don't want seems to be an efficient way to do this.
Thanks
Other than that advertisement on the lockscreen did anything else bother you?
you CAN flash different lockscreens
All custom roms have their own personality. I think based on your comments you may like assonance. Be aware though that the top bar had a ginger bread look.
Axura is nice but the boot screen does say axura
Sent from my SAMSUNG-SGH-I897 using XDA App
Assonance. No advertising anywhere that I've seen, and it's a very good ROM.
Sent from my Android using the power of my dreams.
to be honest, the entire procedure of loading up that rom annoyed me from the beginning. Between some female robot voice saying things I couldn't quite understand while it was doing...something. To the huge logo screen that came up during the load/boot process, to the additional of a dozen or so urban-sounding ringtones that weren't part of the original leaked froyo I was running (yes I know I can go in and delete any offending ringtones) to the fact that it seems any stock wallpapers that weren't garish were removed (solid colours, please?) To the animated advertising on the lock screen, which pushed me over the edge.
I admit I was guilty of not researching in depth, I might have known in advance what I was getting in to. My phone was getting so chunky in just navigating screens and attempting to make phone calls, I needed something. And while I was going thru the hassle, I decided I'd try to get something solid loaded on it.
My phone is my workhorse, I just want something solid, functional and dependable. I have no desire to show it off. I have a Viewsonic G-Tablet that is my playtoy that's I customize and put all the bling on.
But my phone, I want it lean, mean and a bit more functional than the stock Android.
All i900 roms have those ring tones.
Wall papers are all over the internet
As mentioned assonance had no advertisement, or branding
The voices on boot are part of voodoo. The lag fix. really it is a comfort thing. as long as she says something every so often you know things are progressing. Without it you will be wondering why your phone is taking 6 minute to boot
Sent from my SAMSUNG-SGH-I897 using XDA App
Try this ROM here. Super stable and very good on battery life.
[ROM][froyo]-di11igaf's Rom v2.5 AND BETA 3.0- 12/16/10
Code:
http://forum.xda-developers.com/showthread.php?t=848066
Dungeon47 said:
Assonance. No advertising anywhere that I've seen, and it's a very good ROM.
Sent from my Android using the power of my dreams.
Click to expand...
Click to collapse
,+1 10 char
Sent from my SAMSUNG-SGH-I897 using XDA App
Give the Devs a break. They put a lot of time into making this ROMs and they don't get paid, they do it cuz they like it. You don't have to rant about it, just uninstall it and get something else. And like mcord11758 said, you can customize the lockscreen and ringtones and you can get any wallpaper you want from the internet. An the voice thing only happens the first time you boot up when its applying the lagfix.
I have only tried Cognition (beta 6). There is a boot screen that says cognition, but that's it. You can change boot screens if you want. I feel its a great mix of vanilla and touchwiz. Its super fast, and been amazingly stable. Those voices only happen once, like others said it let's you know you're not bricked, still working.
Sent from my SAMSUNG-SGH-I897 using XDA App
The whole point to flashing a custom rom...is to have a good working solid base to work with if you choose to leave it as it is... Since these are Android phones that can easily be modified to your liking (after all isn't that what you are trying to do ? )...and since you are loading a custom rom that has tons of people giving their input on how it looks and what features it has in it...it's really time for you take responsibility of what you are posting and to stop expecting a plain vanilla rom when you can easily see how far along it is in development that one is.
Learn to read and research better before you flash a full featured rom with tons of customization in it. They all have change logs on the OP for you to see what is in it...and if you don't understand what your flashing...then perhaps you should refrain from doing anything like that until you are familiar enough with it. You can post questions about all the roms if you don't understand it's features...you can also read the thread and what folks are saying about it...even if it is as long as it is...This way...you become familiar with it..and how it was developed over time.
Complaining about a very popular rom's features or it's designer because you didn't take the time to research what exactly it has in it or does is childish at best.
If you find my post offensive...or flaming you...I am sorry...but no one twisted your arm to modify your phone..just as no one can force you to read and research before you attempt to modify your phone...but you will be better off doing just that and to learn what it is your attempting...and wanting on your phone...before you flash anything. All of the roms have different features..modems..lag fixes..some are over clocked..some aren't...some have talking voices at boot up..some don't...all this information is available to you....BEFORE you do anything...
Mac
Protip: The majority of the custom rom's are not built for use, but for the dev themselves. If they like it that way, and you don't, too bad.
That being said, CyanogenMod is probably the only one that fully fits your requirements, as it's built from AOSP sources, rather than a modified samsung rom.
Sent from my SAMSUNG-GT-I9000 using XDA App
Hello Everyone. I am a long time Android User, new to rooting.
Before I get too deep in this I had a general question....
I have a Droid 3 that I am finding to be slow compared to my stock Google Nexus One. I really enjoy the qwerty keyboard and don't want to go back to my Nexus, However the lag in the contacts autofill indexing and email autofill indexing is Killing Me.
I run my email, calendar, and contacts etc through the gmail/ google apps platform and REALLY want to get the speed I had with my Nexus One on my Droid3.
What would you recommend?
How can I speed this thing up and still have a very reliable phone?
I also need to be able to use the following features (which work now):
wifi hotspot
tethering
hdmi out
bluetooth
calendar
Thank you so much for any insight you can provide. I am really impressed with the knowledge base on this forum.
Much Appreciated.
I am by no means an expert in Android devices but can definitely tell you that the 'slow down' you are experiencing is due largely in part to the poor ROM/Skin that is built onto the phone by Motorola and Verizon.
I would recommend rooting and trying out one of the custom ROM's in the Android Development section.
I have an XT860 so there are no ROMs really available at this point but from my experience with my HTC Desire Z, there was a night and day difference in speed and usability of the phone after I rooted it and began using custom ROMS.
For the Droid 3, 'Steel Droid' seems to be a very popular ROM, but again I don't have any direct experience with it because its not compatible with the XT860 (Canadian GSM variant of the D3)
Hope that helped a bit...
i use steal droid its great. renaming your bloat to .bak will speed up your d3. if you do use steel droid just flash dlna back.
I am reasonably intelligent person, confident with technology, but am finding it difficult to make sense of many of the posts because of the jargon.
Is there a cliff notes version on how to do this?
I rooted my phone with the 1 click root.
I have also installed Droid3 Bootstrapper (but I dont know what it does?)
I believe this helps me build a backup in case the ROM fails?
Where do I go from here?
Thank you!
its also for flashing roms in the form of .zips
Check out this thread in the development section, it is for Steel Droid specifically but in the first post, just after the changelog, he gives pretty good instructions on how to flash the ROM.
http://forum.xda-developers.com/showthread.php?t=1278056
johnniekombat said:
I am reasonably intelligent person, confident with technology, but am finding it difficult to make sense of many of the posts because of the jargon.
Is there a cliff notes version on how to do this?
I rooted my phone with the 1 click root.
I have also installed Droid3 Bootstrapper (but I dont know what it does?)
I believe this helps me build a backup in case the ROM fails?
Where do I go from here?
Thank you!
Click to expand...
Click to collapse
Be like me my friend. Just start searching around the xda forums, on google, rootzwiki, etc. Start absorbing information. I started with a normal Droid 3, and within 3 or 4 days, I found out just about everything I needed to know. You are correct about bootstrap, and it also allows you to install system files, theme files, kernel files, etc.
I would recommend Liberty. It's mostly AOSP (Android Open Source Project) which means it's not bogged down by Motocrap. It flies, you can still have some blur elements and I have not experienced a single bug.
U need to root, install custom recovery, then I recommend installing a stock android rom from the android development section. Also try SetCPU to raise your processing power. But as said, the speed is mosly do to bloatware. You can also remove these without installing a rom, using root unistaller( must find of internet). Must be rooted though.
Please thank me if I helped.
Just my 2 cents, contrary to others I won't necessarily recommend flashing a CUSTOM Rom. But definitely update to the 5.6.890 to see an increase in battery life and performance, and root your phone so you can debloat.
I have seen no real improvement between custom ROMs besides the themes and user experience. however if you are satisfied with how your phone is running and have required apps you need to work, i'd just debloat the stock ROM yourself. it will be a lot faster with the bloatware frozen using an app like titanium backup. a lot of the custom ROMs end up having bugs, especially Liberty seemed to be causing trouble for some folks before the update. but basically all the speed improvements people are seeing is from the apps removed from running in the background that you don't need, so do that and youre good to go.
johnniekombat said:
I am reasonably intelligent person, confident with technology, but am finding it difficult to make sense of many of the posts because of the jargon.
Is there a cliff notes version on how to do this?
I rooted my phone with the 1 click root.
I have also installed Droid3 Bootstrapper (but I dont know what it does?)
I believe this helps me build a backup in case the ROM fails?
Where do I go from here?
Thank you!
Click to expand...
Click to collapse
CHECK THIS OUT http://forum.xda-developers.com/showthread.php?t=1238472 THEN USE THIS http://forum.xda-developers.com/archive/index.php/t-1192795.html TO DELETE THE REST THAT THE FIRST DOESNT COVER. I KNOW THE SECOND IS FOR A DIFFERENT PHONE BUT DONT WORRY IT IDENTICAL. I PERSONALLY DELETED THEM. AFTER I CLLEANED UP DAVLIK CACHE AND MY PHONE FLIES ON STOCK ROM.
THEN DO YOUR SELF A FAVOR AND MAKE YOUR CAMERA BETTER WITH THESE SIMPLE THINGS. http://forum.xda-developers.com/showthread.php?t=1271927&page=2, http://forum.xda-developers.com/showthread.php?t=1326101
techno-update said:
U need to root, install custom recovery, then I recommend installing a stock android rom from the android development section. Also try SetCPU to raise your processing power. But as said, the speed is mosly do to bloatware. You can also remove these without installing a rom, using root unistaller( must find of internet). Must be rooted though.
Please thank me if I helped.
Click to expand...
Click to collapse
What settings have you done in SetCPU??
I was having major issues with SetCPU when I originally set it up...
This was also when the phone just got rooted too though...
I thought we needed a modded kernel to do any CPU clocking things...?
Seirÿu said:
What settings have you done in SetCPU??
I was having major issues with SetCPU when I originally set it up...
This was also when the phone just got rooted too though...
Click to expand...
Click to collapse
Set cpu will only allow you to underclock and change governor. I would only suggest switching the governor to performance, which beware will drain your battery faster, because its reported that other than stock governor and performance cause phone to act goofy.
Cannot overclock yet, we may not be ever be able to because **** bootloader locking.
Just Froze most of the bloat ware using the free Bloat Freezer in the market and am already experiencing improved performance!!! Thank you all so much!
I made this thread based on what i think ROM's must or should have 4 an average use
- STABLE, with no sd unmounting or unespected reboots
- Of course, it must read the SD, also, would be good to have an file manager, light like OI file manager, even if its aosp, cause some of us stores our apps on SD as backups
- All kind of wireless networks, GSM mainly, WiFi, USB and Radio for those who listen!
-Clean Launcher to let the user set it 4 his needs
-mic, dialer, dial UI, messagin working
-BT handset / and jack working ofc
-speaker
-Good or the laster battery it can be
-DSP or louder sound
-Not too laggy UI or ROM
-OC could be added as well, but it is not really needed, unless the ROM its a bit laggy
-Working camera, cause we all need to take a picture often, even when its about our studies (I take pics to ppt )
-LG stock apps like Alarms, calendar, energy control, Google apps, voice, weather and news
-Of course it'd be cool to have youtube to watch somes How-To about anything
-Rooted, its not TRULY needed, but lets face it, we all want it, or some doesn't know how, or just cannot reach it!
All those things should be on any ROM, unless its a BETA or A release with KNOWN bugs which will be FIXED as ppl/users detects then
Suggestions:
-LG IME keyboard
-Astro File Manager (I make apps backups from Astro)
-Docs to go
-Touchpal / Swipe
-XDA forum app to follow our respective roms thread or any thread we want
-OC and Swapp utility/support
Guess thats the bassic things users are looking 4 + performance, i also know not ALL roms will have but it could work as a guide or a task list of what to do with a rom in development, also after making a rom, it'd be cool to get a test period with some users, or all of them to fix possibles bugs and then make it clean!
Feel free to post any other thing u think its needed or any suggestion
Dont see point of this topic... dont rom like, dont use it.
Sent using Tt.
Taking that as main duty, just sug
You sound as though you know how to build a rom without all this probs trust me its alot harder
I do not know actually, just attached them as task to be done or something, if a rom complishes most of the features, and gets real stable, it could be as an Official one! Repeat, its just a suggestion...
Yes I know
Really, this topic makes no sense. You're indirectly saying that you want a fully working ROM. If any ROM has a missing File Manager, tell that respective developer. And Developers know what should be working in their ROMs and even they want their ROMs to be bugless!
If you want any added apps, you can add them yourself. Instead it's better that the ROM is as clean as possible
No sd unmounting or unexpected reboot? i get that with LG's stock kernel.
Developers here aren't LG software engineers, we don't pay them to develop roms etc... We don't have the rights to expect everything working perfectly anyways. LG makes mistakes as well.
LG stock apps require porting because those apps does not work standalone without LG's framework.
Yeah, the camera takes crappier shots than the 'lowest end' 1mega pixel cybershot my parents gave me which was bought in 2001. But I'd agree that some users without image quality expectations would want a working camera
Root is needed by most users for integrating apps into system file, debugging and modify rom itself on phone. If you're the one who plays with your phone and thinking how amazing it is, well...... *no comment*.... 'no life'.
Not going to comment on overclock becouse I don't truly need it and will buy a new phone soon.
Root explorer allows root access, not astro.
In combination, suggesting is; add your own apps. You're not paying the developer neither does your opinion or the way you use your phone apply to everyone else on xda.
@mrandroid
lol nice avatar!
@chaos
don't feel insulted! we are just pointing you in the right way! everyone makes mistakes!
like me when i sent a pm to joost for the first time asking him which is the best rom as i am new to android and confused things like swiftdroid quarx etc.
Im not feeling insult, don't wqorry, i know it must be a senseless thread, d'u think it shal be deleted? :/
I think this topic is in the wrong category. The android development forum is getting more and more crowded. I think this topic should be in the general forum.
Though getting there, how to delete it from here?
fdespotovski said:
I think this topic is in the wrong category. The android development forum is getting more and more crowded. I think this topic should be in the general forum.
Click to expand...
Click to collapse
This is a very small development community anyways. It should be included in development just to grab developer's attention
Enigma GIN & ICE
your specs for a rom done
Sent from my tf101 using xda premium 1.54Ghz
chaosx8 said:
Though getting there, how to delete it from here?
Click to expand...
Click to collapse
You can't delete it and don't worry about it.
chaosx8 said:
Though getting there, how to delete it from here?
Click to expand...
Click to collapse
Since it's already here, you can't do anything about it.
MrAndroid12 said:
This is a very small development community anyways. It should be included in development just to grab developer's attention
Click to expand...
Click to collapse
That's what I made it for, have devs attention so they give their best and take care of users attention so they give their best for to the ROM
Sent from my GT540 using XDA App
I've recently come to the conclusion that I'm a flash-a-holic, and in order to facilitate my need for speed from my device, extended battery performance, and just the best overall experience from my phone (it's been a LONG time since I've ever been completely happy with one of my phones), I have started drawing up specs for an all-around Thrill tool which will incorporate all the tools into a fully automated process (with prompts for certain things of course asking that you confirm the action has been done if it can't be detected) to help speed up the process and take some of the guess work out of it all.
All-in-all I've reflashed my Thrill about 20+ times in the past 3 months, and while I've 'settled' for now, I see that with the hopefully upcoming ICS release, and the daunting task of flashing that is presented to all users currently, a tool which incorporates all steps of the process and attempts to simplify it to "Select which ROM you wish to flash" "it is recommended that you use X baseband for that ROM, however you can choose another at your own risk", and click Go, the rest of the process is handled by the tool, might be desired.
The aim of this tool would be to make first time flashers a little less intimidated by the plethora of steps required by simplifying them down as much as possible and handling as much as possible in the background. However it would also provide flash-a-holics like myself a quick system by which to refresh the ROM on the phone or switch to another to try it out.
Steps I'd like to see the tool perform for folks:
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
I'd like some thoughts on this and some guidance before I start really digging in. Couple of my main questions are as follows:
First, is this even needed anymore with the plethora of information available? Yes, it coalesces most of those steps documented into a simple interface tool, however do people prefer to keep everything broken up, I know I don't, especially when it's all towards one goal.
If there is still a need/desire for a tool like this, how in-depth on options would people like to get?
What would the developers like to see available from a developer's standpoint?
What would the end-users like to see available from the interface?
I would love any feedback on this idea before I move forward so I have a clear picture of what it is that the community would like.
Thank you for your time and feedback folks.
Welllll.
Acidhazard kitchen rom I know you have used. The build interface Is a great format to start with. Has a few automated tools built in. Probably a novice or advanced select. That would appeal to newbie and testers alike . An updatable base and tool would be great. Hunting for base bands is a pain and having it all in one handy tool would be lovely.
This is a good idea. I would make it so it cannot flash a ROM if the correct baseband isn't there to help new people avoid bricks. I think that is the biggest fear for people new to flashing.
Sent from my LG-P925g using xda app-developers app
SithLord2K said:
This is a good idea. I would make it so it cannot flash a ROM if the correct baseband isn't there to help new people avoid bricks. I think that is the biggest fear for people new to flashing.
Sent from my LG-P925g using xda app-developers app
Click to expand...
Click to collapse
The only way you would be allowed to override the baseband is if you were in advanced mode and filled in a checkbox accepting the consequences of your choice. I've had wrong baseband before and had a working phone with no service. It's possible it's not fun but it's possible, and yes, for basic mode it would be forced to only the accepted list of basebands for the ROM you wish to install.
Cab121 said:
Welllll.
Acidhazard kitchen rom I know you have used. The build interface Is a great format to start with. Has a few automated tools built in. Probably a novice or advanced select. That would appeal to newbie and testers alike . An updatable base and tool would be great. Hunting for base bands is a pain and having it all in one handy tool would be lovely.
Click to expand...
Click to collapse
The idea here is not to duplicate somebody else's work, but instead augment it and enhance it further. While his tool is awesome, it's also command line, my tool will end up being a user-friendly GUI. I would love to end up with a multi-ROM kitchen for the O3D and Thrill (P920 & P925 respectively) built into this tool, it's not a priority for the beginning. I will be studying heavily the scripts used by some of these wonderful tools in an effort to duplicate their efforts contained within a GUI. I don't plan on writing something that just runs these tools in the background and makes the selections for you, I'm talking a complete tool from the ground up. I think I may write a helper tool for inclusion to the ROMs it builds which I can use to help facilitate this process in a much more friendly manner. (So you have to touch the phone less.)
Cynagen said:
The only way you would be allowed to override the baseband is if you were in advanced mode and filled in a checkbox accepting the consequences of your choice. I've had wrong baseband before and had a working phone with no service. It's possible it's not fun but it's possible, and yes, for basic mode it would be forced to only the accepted list of basebands for the ROM you wish to install.
The idea here is not to duplicate somebody else's work, but instead augment it and enhance it further. While his tool is awesome, it's also command line, my tool will end up being a user-friendly GUI. I would love to end up with a multi-ROM kitchen for the O3D and Thrill (P920 & P925 respectively) built into this tool, it's not a priority for the beginning. I will be studying heavily the scripts used by some of these wonderful tools in an effort to duplicate their efforts contained within a GUI. I don't plan on writing something that just runs these tools in the background and makes the selections for you, I'm talking a complete tool from the ground up. I think I may write a helper tool for inclusion to the ROMs it builds which I can use to help facilitate this process in a much more friendly manner. (So you have to touch the phone less.)
Click to expand...
Click to collapse
When you ready my scripts, just know, it's in English. Lmao.
Literally, command prompt code.
The Dark Lestat said:
When you ready my scripts, just know, it's in English. Lmao.
Literally, command prompt code.
Click to expand...
Click to collapse
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Cynagen said:
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Click to expand...
Click to collapse
Oh, that's not it. Every time someone opens my script, they ask why they can understand it.
Sent from my Samsung Galaxy S II w/AOKP
The Dark Lestat said:
Oh, that's not it. Every time someone opens my script, they ask why they can understand it.
Sent from my Samsung Galaxy S II w/AOKP
Click to expand...
Click to collapse
LMFAO most languages are surprisingly in english, it's kinda weird, cause I know a couple that were NOT developed here in America or the UK.
Cynagen said:
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Click to expand...
Click to collapse
Then you are also my hero. That came in handy when the rest of us where screaming at our machines having dealt with Vista and any torrent work.
I was under the impression your original plan here was to utilize the tools and data available from various sources "AcidHazard, Megatron and so on" to achieve the wonderful multipurpose and expandable tool you have decided to develop. We are here to help. More especially since your calling upon it. Plenty of communication , feedback, and patience is what I prescribe here. That being laid out :fingers-crossed: we can continue.
Ok so with all respect, credentials, history, contribution, and hero work established and being taken in to consideration as I type lets define a few of your plans further and designs ideas further so we might better contribute to your efforts. This is an awesome idea and I think its something we all need desperately. I realise the following will seem very redundant and you may feel its unnecessary but trust me it will help everyone from this point on.
Question 1
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing? This would initially entail the following core tasks?
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Question 6
Where the heck is Waldo?
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
(continued)
Question 8: Why is this not in General?
Anyway, I think that some bits are pretty much impossible, for example flashing the baseband since you need the LGMobileTool for that or SmartFlash, command prompt or adb or fastboot won't work for this at all. Otherwise I would say it's doable, but it probably won't be from me unless I remember to do it in December and no one else has done it yet :/
Cab121 said:
Then you are also my hero. That came in handy when the rest of us where screaming at our machines having dealt with Vista and any torrent work.
I was under the impression your original plan here was to utilize the tools and data available from various sources "AcidHazard, Megatron and so on" to achieve the wonderful multipurpose and expandable tool you have decided to develop. We are here to help. More especially since your calling upon it. Plenty of communication , feedback, and patience is what I prescribe here. That being laid out :fingers-crossed: we can continue.
Ok so with all respect, credentials, history, contribution, and hero work established and being taken in to consideration as I type lets define a few of your plans further and designs ideas further so we might better contribute to your efforts. This is an awesome idea and I think its something we all need desperately. I realise the following will seem very redundant and you may feel its unnecessary but trust me it will help everyone from this point on.
Question 1
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing? This would initially entail the following core tasks?
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Question 6
Where the heck is Waldo?
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
Click to expand...
Click to collapse
Question 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing?
Yes, with the goal of expanding over time to include such things as a kitchen for all thrill ROMs like the acidhazard kitchen. Possibly even the UOT.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
That's a possibility however it makes more sense to convert most of these tools into the native language of the new tool. For initial purposes this will be AutoIt. Should enough Linux and Mac interest be generated a PHP using GTK front-end with the autoit version becoming depreciated.
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
The goal is to write one EXE to incorporate all tools needed for the basic flashing functionality needed to go from anything to stock and follow the process up to custom ROM and kernel. From there, again with sufficient feedback, development would continue and new features incorporated. Backend tools can change how they operate thus requiring a new patch every version, processes don't change too much and keeping up with developments won't be as hard. This in turn frees up time to design an actual gui over using automated command-line.
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Updates for things such as what you listed? Basebands, ROMs, necessary tools like adb, and the like? Why not all of those wonderful ideas? This will give ease of access during operation and once depreciated for years the option to pack the tool in a zip file with their favorite ROMs and modifications ready to be used once unpacked.
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Many options are available, private hosting, directly submitting to the project website (which will keep the tools files up to date automatically), allowing users to download and select locally.
Question 6
Where the heck is Waldo?
I haven't the foggiest.
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
Do you one better, an email address. I use my forum posts as tech support for the application, so things don't end up cluttered. Yes it means I'm bound to get two or more emails regarding the same suggestion but that's fine by me if it means that the public information is directly useful.
Sent from my LG-P920 using xda app-developers app
moved to general.
Only thing else I can think of that would be a huge advantage would be a theme compiling tool and a debug log that could be used as a resource for you and the Devs who work on the roms. Can't wait to see what you create because even 1/2 of this would be awesome.
Cab121 said:
Only thing else I can think of that would be a huge advantage would be a theme compiling tool and a debug log that could be used as a resource for you and the Devs who work on the roms. Can't wait to see what you create because even 1/2 of this would be awesome.
Click to expand...
Click to collapse
A theme compiling tool is harder to make than you think. Even compiling a theme is hard to do if you don't know what you're doing.
Heck. I had a hard time compiling a theme, but then again, LG borked everything so I had to do the run around.
The Dark Lestat said:
A theme compiling tool is harder to make than you think. Even compiling a theme is hard to do if you don't know what you're doing.
Heck. I had a hard time compiling a theme, but then again, LG borked everything so I had to do the run around.
Click to expand...
Click to collapse
Very true. I have not done it so I can't really offer a valid opinion. Would be awesome though albeit a pipe dream lol.
Cab121 said:
Very true. I have not done it so I can't really offer a valid opinion. Would be awesome though albeit a pipe dream lol.
Click to expand...
Click to collapse
If somebody else has the process mapped out already, I'm looking at you Lestat, I can clone it and present it in an easy to manage fashion that can be adopted by many users. This is only if steps are documented, I don't exactly have time to do any research into hacking an Android.
Cynagen said:
If somebody else has the process mapped out already, I'm looking at you Lestat, I can clone it and present it in an easy to manage fashion that can be adopted by many users. This is only if steps are documented, I don't exactly have time to do any research into hacking an Android.
Click to expand...
Click to collapse
I don't have it mapped out, but I can map it out pretty quickly.
Here's a ROUGH draft.
First, there can be two types of "theme kitchens".
Automatic
Non-Automatic
An automatic theme kitchen is usually going to be for one device.
A non-automatic theme kitchen can be used for a broad range of devices.
Automatic - Not familiar with code
Non-Automatic - Familiar with code.
Here's the draft for the automatic, and yes, I'm typing this as I go. Lol
Automatic
Extract theme files from phone. (usually framework-res.apk & SystemUI.apk for Gingerbread)
Decompile theme files
Choose what theme element you want
Automatically overwrite UI element (.pngs, .xmls, and other files) - Go back to number 3 UNTIL the loop is closed. (Finished with theme)
Compile theme files
Push files to phone
Set permissions
Wipe dalvik-cache and cache
Reboot phone
/End
Here's the draft for the Non-automatic.
Non-Automatic
Extract theme files from phone. (usually framework-res.apk & SystemUI.apk for Gingerbread)
Decompile theme files
USER APPLIES THERE OWN THEME ELEMENTS
Compile theme files
If error occurs while compiling, go back to number 3.
Push files to phone
Set permissions
Wipe dalvik-cache and cache
Reboot phone
/End
Just a simple map of what to do. Of course, putting it into code is a lot easier when you have the correct files.
They need flashaholics anonymous. Then maybe I wouldn't flash people on the streets. >_>
Oops, wait. Wrong subject matter.
P.S. This was just a joke, something to get a laugh out of people.
cmarriner82 said:
They need flashaholics anonymous. Then maybe I wouldn't flash people on the streets. >_>
Oops, wait. Wrong subject matter.
P.S. This was just a joke, something to get a laugh out of people.
Click to expand...
Click to collapse
Dood, back when I had my netbook I used to flash people on the street all the time, the ones with some time and a couple bucks.
P.S. I totally loved your joke and well, had to answer honestly, as a joking response, even though I used to do this exact thing.
Anywhos... I expect to have a test-tool released next week which when you run it, it will allow me to collect some data on the environments (submitted anonymously back to my dev box), ask you a few questions, and collect some data from the phones themselves if they are connected and in debug mode at that time (which I hope everyone does as this is HUGELY important). With the test tool, I'll have it report whether or not your phone will be supported as it stands right now (plug and play), or at least recommend changes (drivers, software, phone version, etc) to make it compatible.
I'm also thinking of the name "Thrilling Toolkit" for the end product, what do you all think?
Sounds good. Can't wait to try it.
Sent from my LG-P925 using xda app-developers app