I am a Tilt 2 user... I have been playing with alot of the different roms out there and i find them all to be very similar. I dont know what the difference is in Manilla, and Sence. I kinda fingured out what HTC messaging is... Not a big fan of it.
Here is what I am looking for:
SPEED.... when I press a button... i want it to get to that screen fast! I dont use many apps other than basic features. MMS, SMS, EMAIL, PHONE, and Camera. I do sometimes use the GPS. but not often. I could care less about the stocks feautre.
I prefer the windows threaded mesages... not the HTC one.
I do like the Facebook integration on some of the roms but that is not required.
What would you guys say is my best option at this time? Titanium?
I second this. I have never worked with a phone that is so SLOW.
I have no choice but to use this phone as it is supplied by work.
Fast rom needed.
HALP!
yes, go with the energy titanium rom, it's quite zippy if you're looking for that. but realize this phone only has a 528 processor so it still won't be all that fast if you're comparing to other people.
I realize that it wont be as fast as the 1GHz HD2 that is out now... but i just want to squeeze a bit more out of the device i already have.
The phone itself isn't slow... Bad made ROMs make it slow.
Try LBFAR or Simplicity. In my *PERSONAL* opinion they are a lot of faster then any Energy ROM.
Also they aren't bloated with crap...
dragonlord785 said:
yes, go with the energy titanium rom, it's quite zippy if you're looking for that. but realize this phone only has a 528 processor so it still won't be all that fast if you're comparing to other people.
Click to expand...
Click to collapse
If speed is your main objective, give overclocking a shot.
http://forum.xda-developers.com/showthread.php?t=698374
Jackos said:
The phone itself isn't slow... Bad made ROMs make it slow.
Try LBFAR or Simplicity. In my *PERSONAL* opinion they are a lot of faster then any Energy ROM.
Also they aren't bloated with crap...
Click to expand...
Click to collapse
Massive +1 to this. I use Simplicity myself most of the time. It's pretty light and fast. (Not to say that LBFAR isn't light or fast. It is both. It's just a little bit too psychadelically colored for me.)
Also, Jackos's ROMs are pretty nice as well, and are generally what I'm running if I am not on Simplicity. They're not built specifically for speed, but they're really well crafted and end up being faster than many other ROMs because of it. They're also rock solid. Just tossing that out there, as Jackos seems to have passed on the opportunity to toot his own horn.
Jackos
I am downloading Jackos right now... if the silly file host didnt limit me to 1 file per hour i would have already had it.. but its going now. I am going to try a couple of differnt ones... as well as over clocking app.
Jackos said:
The phone itself isn't slow... Bad made ROMs make it slow.
Try LBFAR or Simplicity. In my *PERSONAL* opinion they are a lot of faster then any Energy ROM.
Also they aren't bloated with crap...
Click to expand...
Click to collapse
yes, if your looking for speed improvement with lack of visual effects this is true
Use the standard ROM and disable HTC sense, it won't get any faster or stable.
Mirror in my sig.
Language
Jackos, I just downloaded the rom from your previous post on this thread... once I installed it, It did not apear to be in english? did I download the wrong one? it also did not apear to include the radio from the rom... but that is easy enough to fix.
Dracothearies said:
Jackos, I just downloaded the rom from your previous post on this thread... once I installed it, It did not apear to be in english? did I download the wrong one? it also did not apear to include the radio from the rom... but that is easy enough to fix.
Click to expand...
Click to collapse
you may have downloaded the polish version. Make sure the name of the file has WWE in it and not PLK. Im using Jackos S2 ROM WWE JackFULL v1.7 right now and it is flawless. Also the ROM download includes the Radio 4.49.25.91 and task29. Hope this helps
FL5 said:
If speed is your main objective, give overclocking a shot.
http://forum.xda-developers.com/showthread.php?t=698374
Click to expand...
Click to collapse
+1 to that
Shouldn't a new user first choose a RELIABLE ROM and later try some extreme tools like overclock?!
I disagree with this.
-1 to that
Jackos said:
Shouldn't a new user first choose a RELIABLE ROM and later try some extreme tools like overclock?!
I disagree with this.
-1 to that
Click to expand...
Click to collapse
I didn't say that he shouldn't perhaps pick a new ROM that he likes, first. But I also wouldn't call overclocking an "extreme" tool - OCT seems to work very well and my phone is 100% stable, without dynamic overclocking.
I would never recommended an overclocking tool for a new user.
Firstly, how can you be sure that the tool doesn't deal damage to the processor? It's out for just around 2 months.
Secondly, it does shorten the battery life (it may does dmg to the battery too).
Thirdly, it may cause lockups, power management problems, SoD etc.
Yes I would call the current OCT1.5 tool stable enough running at 710Mhz and yes it does speedup our devices, but I still wouldn't recommend it.
Jackos said:
Shouldn't a new user first choose a RELIABLE ROM and later try some extreme tools like overclock?!
I disagree with this.
-1 to that
Click to expand...
Click to collapse
Jackos said:
I would never recommended an overclocking tool for a new user.
Firstly, how can you be sure that the tool doesn't deal damage to the processor? It's out for just around 2 months.
Secondly, it does shorten the battery life (it may does dmg to the battery too).
Thirdly, it may cause lockups, power management problems, SoD etc.
Yes I would call the current OCT1.5 tool stable enough running at 710Mhz and yes it does speedup our devices, but I still wouldn't recommend it.
Click to expand...
Click to collapse
Yeah, totally valid points. I kinda fired that suggestion out off-the-cuff right before class started last night, and very obviously didn't flesh it out appropriately.
Overclocking IS an advanced tool and it does impact the stability of a device. Some handsets tolerate it much better than others, but without first having a good working understanding and feel for both the hardware and the ROM you're using, it can cause no end of frustration trying to figure out what settings work for a setup individually (it's like voodoo magic; all settings very much have been found NOT to work for all people).
The first step should be to find a stable ROM and become familiar with how it works, and then start dabbling carefully only AFTER reading the bejeezus out of the OC thread (seriously, RTFM), should a person still be interested.
That being said, in my experience the settings that work seem to be more hardware-dependent than ROM-dependent. After pretty thorough experimentation to find the settings that work well for my TP2, I've been able to carry those settings across several different ROMs without issue. Of course, that being said, I will fully admit that I believe that no amount of care will cause an overclock setup to be as stable as a non-overclocked setup.
Also, yes, overclocking definitely burns through battery life, just like turbocharging burns through gasoline, and this almost assuredly decreases the useful lifespan of your battery. While I'm less certain about the potential for processor damage, that does very possibly exist as well.
That being said, I'm a reckless jerk and always load OCT as one of the first steps on a new flash. However, I do so after having taken all of the above into consideration. It was hasty and ill-advised to recommend that a new user jump in uninformed. My bad.
I haven't noticed a big difference with overclock, so I decided not to use it... The truth is that the phone is perfectly fine. The biggest culprit in all of the slowness is HTC "Bloatware" Sense. I'm seriously considering paying for SPB mobile shell or something similiar and scrapping Sense completely right now, it just doesn't make up for how demanding it is.
/rant off.
I am open to the possibility that at least some of what I perceive could be a placebo affect, but I definitely feel that there is a difference when my TP2 is overclocked to 787mhz, and I currently feel no compulsion to discontinue doing so.
Thing is, I have to admit that the perception is primarily felt when trying to feed the Sense 2.5/CHT resource devourer combo, and even then the TP2 falls noticeably short. It is painfully obvious that Sense was not meant for the TP2, and OC is really just the slap-patch that allows it to limp along at an arguably acceptable pace.
I've been internally debating about going back to SPB MS myself. The amount of functionality that it has is incredible considering the scant resources it uses. I actually meant to drop it back in this past weekend before I got swept up in other nonsense, as I found a little app/toggle somewhere here on xda that claims to switch between manila and SPB MS. I've got CHT on right now, because it is oh-so-pretty, and I am quite fond of my current layout's aesthetics, but it is a total dog, even on Simplicity.
Which is in your opinion the best rom to flash on the nexus 6 having stability no bugs and features????
Opinions pls
I think you'll find that for the most part, the majority of the ROMs here are pretty stable, but in the end it's up to you to decide which one you'll stay on. It's a very subjective choice
eggydrums said:
I think you'll find that for the most part, the majority of the ROMs here are pretty stable, but in the end it's up to you to decide which one you'll stay on. It's a very subjective choice
Click to expand...
Click to collapse
At that my friend, answers this question perfectly.
Liquid smooth
Or as stated any.
There is no best Rom like what eggydrums said. Asking this question is like going into a car store and asking what's the best car. One rom doesn't fit everybody's needs. Some people look for minimalism, or features, or whatever. There is no best Rom. Every rom has its own unique features, pros, cons.
But if you're looking for opinions, obviously I'd say my rom chroma. I provide support and literally reply to every reply in the rom thread. But it contains the essentials, nothing more and nothing less. Doesn't fit everybody's needs.
Sent from my Nexus 6 using Tapatalk
There're several ROMs which you can flash in order to see which one do you like the most
zephiK said:
There is no best Rom like what eggydrums said. Asking this question is like going into a car store and asking what's the best car. One rom doesn't fit everybody's needs. Some people look for minimalism, or features, or whatever. There is no best Rom. Every rom has its own unique features, pros, cons.
Click to expand...
Click to collapse
I usually just post this from evernotes
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are you running on your Nexus 5 thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
@rootSU I was thinking about making a copy paste of certain faq. Certainly not a bad idea haha. Usually threads with best are not allowed on xda as well
Sent from my Nexus 6 using Tapatalk
zephiK said:
@rootSU I was thinking about making a copy paste of certain faq. Certainly not a bad idea haha. Usually threads with best are not allowed on xda as well
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
xda let best threads exist as of several months ago
So if we say a rom that is not encrypted and has the ability to recive updates so i dont have to flash everytime , and also has nice features that stock lolipop has not, wich one would you guys recomend?
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.