Hey there XDA! I need a little help with something. I'm trying to test some new optimizations, and there's one change that could make a huge difference or no difference at all, and I need more people than just me to help test it. The rom used for testing is my build of PureNexus, due to its closeness to stock aosp and assortment of features. Please make sure the rom fits our needs if you are unfamiliar. No user-end features have been changed. Both of the roms are compiled with a custom SaberMod 4.9 toolchain and DragonTC 3.9.
Obligatory "im not responsible if you brick your device"
The Experiment:
There are 2 builds that will be in the link downloads folder, Test A and Test B. There is one change between the two, in fact, it's just one Boolean value. Please help by downloading and flashing them, and reporting your experience.
The Rules:
Run each build for at least 1 day
Use your normal kernel with your normal settings
Please don't use xposed
Include your favorite benchmark and examples of differences (ex. app opening is slower/faster)
The experiment will end April 15th, please submit your results by then
The Downloads:
https://basketbuild.com/devs/frap129/Nexus%206%28shamu%29/Test
Thanks in advanced! The changes I made and the difference between the two will be released after the experiment ends!
Reserved for results and such
I'd love to flash this and test it out, but I'm going to need a bit more info. What are the changes you made? Also, if I do flash, is a full wipe necessary before I try the first as well as in-between the two?
It seems that a lot of what you are trying to test (benchmark, lag, possibly battery life) is a strong function of the kernel and not the ROM. So if your are asking the people to use their own kernel I'm not sure the feedback you get is comparable from person to person.
Also, as mentioned in the past above, it helps if you explain what these roms are, what they are based on, if you have complied them yourself or not, do they have any built in features different from stock, etc.
mrjiggywiggy said:
I'd love to flash this and test it out, but I'm going to need a bit more info. What are the changes you made? Also, if I do flash, is a full wipe necessary before I try the first as well as in-between the two?
Click to expand...
Click to collapse
The point of the experiment is to be a double blind test, therefore I would prefer not to say what change has been made. I have compiled both of these from source using SaberMod 4.9 and DragonTC 3.9, if that helps you at all. Thanks for your interest.
najoor said:
It seems that a lot of what you are trying to test (benchmark, lag, possibly battery life) is a strong function of the kernel and boot the ROM. So if your are asking the people to use their own kernel I'm not sure the feedback you get is comparable from person to person.
Also, as mentioned in the past above, it helps if you explain what these roms are, what they are based on, if you have complied them yourself or not, do they have any built in features different from stock, etc.
Click to expand...
Click to collapse
Your first statement is part of why I want to do this. Because the change was not to the kernel, any increase in performance should be maintained regardless of the kernel, though it may vary. In regards to your second statement, I stated in the OP that they are my builds of PureNexus. Obviously, no features were changed to remain consistent for the sake of the test. Nonetheless, thank you for your input. I will add more info to the OP
frap129 said:
.... I would prefer not to say what change has been made.
Click to expand...
Click to collapse
You should tell !
Will flash A tomorrow and B the day after tomorrow in a MultiROM (need Android N this week)
Also, any interest in a revival of G Watch developing?
NLBeev said:
You should tell !
Click to expand...
Click to collapse
I will once the experiment is over!
konradit said:
Will flash A tomorrow and B the day after tomorrow in a MultiROM (need Android N this week)
Also, any interest in a revival of G Watch developing?
Click to expand...
Click to collapse
Thanks for the help! and not at the moment. I had started working on a new rom, but then 6.0 came out and I had to scrap most of my work. Maybe when I get a little more free time.
frap129 said:
I will once the experiment is over.
Click to expand...
Click to collapse
OK. You are using the 'placebo effect'.
The user/patient may think it works. But in practice more that 50% may become unsatisfied.
Good luck with the experiment!
NLBeev said:
OK. You are using the 'placebo effect'.
The user/patient may think it works. But in practice more that 50% may become unsatisfied.
Good luck with the experiment!
Click to expand...
Click to collapse
Nope, for this to be placebo I would have to say which one should work better for the user to believe that it actually works better. There is a legitimate difference between the two, but one is not necessarily "better"
You are gonna be hard pressed for people to test this out with the vague way you put it. Let alone using those 2 useless tool chains. Many wont look twice just because of those.
Also one boolean change is not gonna make any real diff.
zelendel said:
You are gonna be hard pressed for people to test this out with the vague way you put it. Let alone using those 2 useless tool chains. Many wont look twice just because of those.
Also one boolean change is not gonna make any real diff.
Click to expand...
Click to collapse
Neither of them are useless, and this one boolean actually caused a major difference by changing the way that ART is compiled and targeted for a device. Please don't spread ignorant garbage without a little thought. It only hurts the community.
frap129 said:
Neither of them are useless, and this one boolean actually caused a major difference by changing the way that ART is compiled and targeted for a device. Please don't spread ignorant garbage without a little thought. It only hurts the community.
Click to expand...
Click to collapse
I'm not. Many developers have already called out the so called tool chains making a big diff. Why do you think none of the temp use them?
Either way good luck to you
to avoid all the arguing would it be possible for you to make 2 builds one pure untouched aosp with pure untouched aosp kernel and the other with just your one change based off the first? Seems that would simplify things greatly
adm1jtg said:
to avoid all the arguing would it be possible for you to make 2 builds one pure untouched aosp with pure untouched aosp kernel and the other with just your one change based off the first? Seems that would simplify things greatly
Click to expand...
Click to collapse
Well then I would have to download AOSP source code, which would take about a day with my internet speeds (and im not that patient lol). I honestly don't understand why using PureNexus is a problem.
frap129 said:
Well then I would have to download AOSP source code, which would take about a day with my internet speeds (and im not that patient lol). I honestly don't understand why using PureNexus is a problem.
Click to expand...
Click to collapse
You have to understand that people will not run a rom just to test something that most devs say are placebo.
A few months ago tool chains were all the talk and people found out for themselves.
zelendel said:
You have to understand that people will not run a rom just to test something that most devs say are placebo.
A few months ago tool chains were all the talk and people found out for themselves.
Click to expand...
Click to collapse
As I stated before, the difference between the two builds is not a toolchain, both use the same ones.
I imagine self reporting will be .... Anecdotal and skewed. Unless a person does exactly the same things in the same amount, error will ensue. Also use will likely vary moreso between a typical weekday and a Friday. If he dataset is big and diverse enough, these can be considered nominal but that means many hundreds of instances at the least. How do u plan to normalize the data, will there be measures of dispersion published?.... Don't mean to be that guy but unless u control the controls the results will not be robust and conclusive. I want to see this work and not have people's impressions be skewed by systemic flaws! I'm all about empirical evidence and ROM development and promotion are laden with unverifiable claims about performance and battery life. "Benchmarks don't matter" is all I hear. I would love to see standardized testing with repeatable data producing unbiased comparisons so the mystery is removed and claims are verifiable.
Sent from my Nexus 6 using Tapatalk
Guess the test is over with few to no takers.
Sent from my Nexus 6 using XDA Free mobile app
Nothing
Related
Pick your favorite. If other, please post it.
I've just recently gotten into ROMs (about a month now) and the first one I loaded was Asergs. I have not tried any of the others but I do plan to at some point.
wow you put mine onto the list...
but i hope nobody will vote..
that was discussed many, many, many times before and you cannot know!
EVERY rom fits to one person!
if you like clean ones, or black ones, or biggy, or, or, or!!!
every rom ahs pro and cons!
test them for your own and donĀ“t ask other to decide for you!!
That's exactly why I put the POLL up though. It's so common for everyone to just start asking whats the best ROM. And while I agree with you that they are all somewhat different and one may fit someone better than the next, alot of people would like to see what is making most people happy. Chances are if X amount of people are using one ROM and swear by it that they will like it as well. And maybe not, but it gives people a baseline of what the crowd is pleased with.
You may want to break up a little further. Each rom builder has many different taste of roms, like full, lite and micro etc. I used Touch IT 2.0 full, Open Touch V3 lite and now I'm on Open Touch V4 lite black, those are all great roms, and I'm sure just within open touch people would have a preference for different flavors.
csmall said:
That's exactly why I put the POLL up though. It's so common for everyone to just start asking whats the best ROM. And while I agree with you that they are all somewhat different and one may fit someone better than the next, alot of people would like to see what is making most people happy. Chances are if X amount of people are using one ROM and swear by it that they will like it as well. And maybe not, but it gives people a baseline of what the crowd is pleased with.
Click to expand...
Click to collapse
ok go on with the masses.....!!!
only because most people like a rom it must not be good... hehe.
but if you look deeper into the world of Herlad/wing you will see the difference
good luck
I noticed that most people have ONLY tried OpenTouch and TouchIT ROMs. OpenTouch is leading the favorite by quite a bit.
I guess it's time for Just2Stuffed...
ivanmmj said:
I noticed that most people have ONLY tried OpenTouch and TouchIT ROMs. OpenTouch is leading the favorite by quite a bit.
I guess it's time for Just2Stuffed...
Click to expand...
Click to collapse
Or Just2Linux!!
h4xz0r j00r r0m!
ROM or not to ROM
For me, and many users, the interest in ROM change was to increase available RAM via Pagepool modification. Now that can be accomplished without changing factory ROM, should this not be a choice? It seems the safest route.
pauldeleeuw said:
For me, and many users, the interest in ROM change was to increase available RAM via Pagepool modification. Now that can be accomplished without changing factory ROM, should this not be a choice? It seems the safest route.
Click to expand...
Click to collapse
Even with a great pagepool, it takes quite a few tweaks to get the RAM in a stock ROM to the level that a custom ROM would get. Even then, there are so many files in the windows folder that it causes a considerable slow down to the machine. This SHOULD be a choice, but I don't think it's the best. Depending on your device, though, it MIGHT be the safest route. (Actually, depending on your SPL.)
How much free RAM do you get on the stock ROM?
Problem Solved. Running CM7 Build 40 (or later).
Do you have a condensed version of this post?
PS. My name is HondaCop and I approve this message.
Sounds like you've experienced a mix of software, firmware, and hardware issues and blamed them all on the ROM.
I use Fresh and can do everything that I read (didn't read the entire wall though, you may want to put in some Cliff notes for the lazy.)
I also run launcher pro.
So make one yourself, nothings stopping you, all the pieces and knowledge are free. Your post on here doesn't really serve a purpose.
Tried Calk's EViO 2, Myn's RLS5, Azrael X 2.1-3.1 over the 1st 3 months after I rooted, all had their various issues. Been on Vaelpak for over a month, love it! Dev is quick to respond to problems, even when they're caused by something in my setup. Currently on v 3.1 RC1 (update 2), v3.2 is right around the corner. Gets better every day!
Swyped on my VaelPak'd Supersonic EVO 4G...
It sounds like you want a rom that does what you want and the good news is...you can get it by making it yourself.
Expecting the devs to make something specifically to your tastes especially when most of it is done free of charge is a bit much to be asking.
If you can't make the rom you like on your own then you had better get cracking at fixing the rom with most of your wants working. You said so yourself you are too lazy to fix even a simple font issue yet you want the devs to make all your "i wants" possible. You should at least put in the effort to try to fix the little stuff (font for example) on your own before expecting the devs to do everything for you.
mswlogo said:
I've tried about 10 ROM's over the past couples weeks and if I could put the best features of all them on one it would be great.
This is in no way a report on disatisfaction from efforts from chefs. They are all sharing there time and effort typically on something they want for themselves.
But it seems you have to give up something to get something else.
I'm hoping someone can shed some light on my issues. Like use ROM X but apply this fix or patch.
I know everybody has different criteria for a "Working ROM" some may feel it's critical that Music plays over bluetooth with the phone going half asleep. Another user may want it to look like an iPhone etc.
But I don't need much (IMHO) but I just can't seem to get there.
Keep in mind I could easily live with most of these ROMs. But when you see something working right on one ROM but want it on another you keep hoping you can find a ROM that does everything the way you want or you can make it do so.
What I say I need may be incomplete because some things I take for granted. Like the phone needs to work, LED's for pending messages need to work etc.
1) ASOP Contacts. Why? So I can Click on Navigate to Address with that contact open. If anyone knows how to make HTC Sense Contacts do this I'd love to know. It can only go to stupid Google Maps.
2) Voice and Google Search to Include Contacts (ideally near the top of the list). I think I may have found a reason why it varies. If you shut off "Search As I Type" it behaves much more the way I prefer and Contacts will come right to the top and if you hit search it will then do a google search.
3) BlueTooth. All I use is simple headset that has worked on TP2 and 5 phones before that. It randomly disconnects after a Voice Search. Then leaves Voice Search prompt stuck on screen. Many (All?) sense based ROMs do this. But CM7 ROMs do not.
3a) Bluetooth Volume Resetting. Some ROM's it gets stuck at a low volume. That I can increase each time but it keeps reverting.
4) Solid 100% GPS. All Sense based ROMs work great. CM7 based ones are crap.
5) Battery as good as Stock or better.
6) ESPT (is a very nice to have but not critical).
7) Don't care about 4G or Eye Candy. But I don't want it to be an Eye sore either.
8) As a poor mans confirmation on Voice Search. I noticed on some Rom if you just say Call Fred Smith (WITHOUT saying on mobile) it will prompt Fred Smith on Mobile or Home. This is great !! So at least you know you got the right person. Then you say Mobile (which it rarely gets wrong). It makes the call. This doesn't work on all ROM's.
9) Good support thread. Some ROMs have very little interaction with chef to help get answers and plugs for some things you'd like to see. Some have very good Chef support but and pounded with stupid chatter and you'd have to live in the thread full time to keep up. It's seems the better support a Chef does pulls in more folks that just want to chat about anything.
10) If Click Send Message from a Contact that could actually FILL the To: Phone Number. A lot of ROM's this doesn't work on. Some depend on a Cache that you have an ongoing thread.
I have not tried alternate kernels with Sense Based ROM's perhaps that would solve some bluetooth issues.
CM7 Build 38 looked promising at first glance. But it fell on its face with GPS. Yes I did all the silly tricks. It always finds location and locks quick. But it just refuses to update while navigating. Will occasionally get an update.
NonSense ROM was very close and I may end up going back to it and perhaps with different Kernels because it suffered from Bluetooth issues. Might be time to upgrade BT headset. It's worked so well for so long I hate to give it up.
These are all stock #15 Kernel with lastest Radio and PRL.
Myn - Over themed (Beauty is in the eyes of the beholder I guess) poor contrasts on Fonts. Yes fixable. But I'm too lazy.
NonSense - Bluetooth is really only issue. Battery about same as Stock.
CM7 BLD 38 - Missed calls GPS will lock but not update.
VP3.70 - This really looks quite good but I just didn't have the time to learn which freaken updates to apply. He leans on theming which is low priority for me.
Rainfreak - Not actually installed, he says he addressed bluetooth issues. But he removed EPST and some other critical Sense based things. Might be easy to put back. But he abandoned support
OMJ - I misspoke in other threads this is a pretty nice stock based ROM and I like his thinking. Fine tune the stock stuff. Currently running. Several of the issues listed above (3,3a, 8).
Sprintlovers - Too close to stock, why bother.
Calkulin - Had stability issues with 1.7.7 (even with undervolt removed). 1.8 seems to have fixed that but still has some of my common issues with Sense Based ROM's with none of the pluses of the Hybrid Sense/ASOP ROMs.
MiekFroyo - Too many ROM's I forget what issues I had but I'm sure in the list above.
Click to expand...
Click to collapse
the bold part made me stop reading until i seen the part about miks roms ... HA its imho the fastest most stablest sense based rom out there !
about the lazy part please unroot your phone then ... lol to lazy to flash a simple file
CheesyNutz said:
the bold part made me stop reading until i seen the part about miks roms ... HA its imho the fastest most stablest sense based rom out there !
about the lazy part please unroot your phone then ... lol to lazy to flash a simple file
Click to expand...
Click to collapse
I don't think his ROM would solve many of my issues any way. If I see a ROM "Over themed" then tend to have different priorities. And I don't want to spend time customizing it. I want one that starts close. Also if the doesn't see this a serious flaw then I suspect I would see other flaws.
Again, nothing against different chefs. Different strokes for different folks.
mswlogo said:
I've tried about 10 ROM's over the past couples weeks and if I could put the best features of all them on one it would be great.
This is in no way a report on disatisfaction from efforts from chefs. They are all sharing there time and effort typically on something they want for themselves.
But it seems you have to give up something to get something else.
I'm hoping someone can shed some light on my issues. Like use ROM X but apply this fix or patch.
I know everybody has different criteria for a "Working ROM" some may feel it's critical that Music plays over bluetooth with the phone going half asleep. Another user may want it to look like an iPhone etc.
But I don't need much (IMHO) but I just can't seem to get there.
Keep in mind I could easily live with most of these ROMs. But when you see something working right on one ROM but want it on another you keep hoping you can find a ROM that does everything the way you want or you can make it do so.
What I say I need may be incomplete because some things I take for granted. Like the phone needs to work, LED's for pending messages need to work etc.
1) ASOP Contacts. Why? So I can Click on Navigate to Address with that contact open. If anyone knows how to make HTC Sense Contacts do this I'd love to know. It can only go to stupid Google Maps.
2) Voice and Google Search to Include Contacts (ideally near the top of the list). I think I may have found a reason why it varies. If you shut off "Search As I Type" it behaves much more the way I prefer and Contacts will come right to the top and if you hit search it will then do a google search.
3) BlueTooth. All I use is simple headset that has worked on TP2 and 5 phones before that. It randomly disconnects after a Voice Search. Then leaves Voice Search prompt stuck on screen. Many (All?) sense based ROMs do this. But CM7 ROMs do not.
3a) Bluetooth Volume Resetting. Some ROM's it gets stuck at a low volume. That I can increase each time but it keeps reverting.
4) Solid 100% GPS. All Sense based ROMs work great. CM7 based ones are crap.
5) Battery as good as Stock or better.
6) ESPT (is a very nice to have but not critical).
7) Don't care about 4G or Eye Candy. But I don't want it to be an Eye sore either.
8) As a poor mans confirmation on Voice Search. I noticed on some Rom if you just say Call Fred Smith (WITHOUT saying on mobile) it will prompt Fred Smith on Mobile or Home. This is great !! So at least you know you got the right person. Then you say Mobile (which it rarely gets wrong). It makes the call. This doesn't work on all ROM's.
9) Good support thread. Some ROMs have very little interaction with chef to help get answers and plugs for some things you'd like to see. Some have very good Chef support but and pounded with stupid chatter and you'd have to live in the thread full time to keep up. It's seems the better support a Chef does pulls in more folks that just want to chat about anything.
10) If Click Send Message from a Contact that could actually FILL the To: Phone Number. A lot of ROM's this doesn't work on. Some depend on a Cache that you have an ongoing thread.
I have not tried alternate kernels with Sense Based ROM's perhaps that would solve some bluetooth issues.
CM7 Build 38 looked promising at first glance. But it fell on its face with GPS. Yes I did all the silly tricks. It always finds location and locks quick. But it just refuses to update while navigating. Will occasionally get an update.
NonSense ROM was very close and I may end up going back to it and perhaps with different Kernels because it suffered from Bluetooth issues. Might be time to upgrade BT headset. It's worked so well for so long I hate to give it up.
These are all stock #15 Kernel with lastest Radio and PRL.
Myn - Over themed (Beauty is in the eyes of the beholder I guess) poor contrasts on Fonts. Yes fixable. But I'm too lazy.
NonSense - Bluetooth is really only issue. Battery about same as Stock.
CM7 BLD 38 - Missed calls GPS will lock but not update.
VP3.70 - This really looks quite good but I just didn't have the time to learn which freaken updates to apply. He leans on theming which is low priority for me.
Rainfreak - Not actually installed, he says he addressed bluetooth issues. But he removed EPST and some other critical Sense based things. Might be easy to put back. But he abandoned support
OMJ - I misspoke in other threads this is a pretty nice stock based ROM and I like his thinking. Fine tune the stock stuff. Currently running. Several of the issues listed above (3,3a, 8).
Sprintlovers - Too close to stock, why bother.
Calkulin - Had stability issues with 1.7.7 (even with undervolt removed). 1.8 seems to have fixed that but still has some of my common issues with Sense Based ROM's with none of the pluses of the Hybrid Sense/ASOP ROMs.
MiekFroyo - Too many ROM's I forget what issues I had but I'm sure in the list above.
Click to expand...
Click to collapse
I actually DID read the entire thing and everything you posted works in king's Ultra Froyo, for the most part
carhauler1969 said:
Tried Calk's EViO 2, Myn's RLS5, Azrael X 2.1-3.1 over the 1st 3 months after I rooted, all had their various issues. Been on Vaelpak for over a month, love it! Dev is quick to respond to problems, even when they're caused by something in my setup. Currently on v 3.1 RC1 (update 2), v3.2 is right around the corner. Gets better every day!
Swyped on my VaelPak'd Supersonic EVO 4G...
Click to expand...
Click to collapse
I may just go to Vaelpak again (Definitely high on the list). I might just wait for V3.2. His updates are bit confusing. If they are primarily to fix "theme" issues I don't care. Again he has a high priority on Themes. That's fine, lot's folks love that stuff. I don't care about themes.
If VaelPak did some refinements on bluetooth (like Rainfreak said he did). Then it would be high on the list to try again. He spends lot of time on high resolution DPI stuff on themes. Just extra band with I need to sift through. But other threads say it's the Kernel that matters regarding bluetooth. That's not clear.
CheesyNutz said:
the bold part made me stop reading until i seen the part about miks roms ... HA its imho the fastest most stablest sense based rom out there !
about the lazy part please unroot your phone then ... lol to lazy to flash a simple file
Click to expand...
Click to collapse
Also sense based Contacts is one of my major issues.
My favorite ROMs are the Hybrids that have some ASOP Gingerbread components that IMHO do it a little better even though not as Eye Candy-ish in some cases.
mswlogo said:
I may just go to Vaelpak again (Definitely high on the list). I might just wait for V3.2. His updates are bit confusing. If they are primarily to fix "theme" issues I don't care. Again he has a high priority on Themes. That's fine, lot's folks love that stuff. I don't care about themes.
If VaelPak did some refinements on bluetooth (like Rainfreak said he did). Then it would be high on the list to try again. He spends lot of time on high resolution DPI stuff on themes. Just extra band with I need to sift through. But other threads say it's the Kernel that matters regarding bluetooth. That's not clear.
Click to expand...
Click to collapse
it is the kernel that matters for bluetooth.
i think its time for you to start learning how to make your own rom but wait your to lazy . i have a feeling no matter what anyone says here will be good enough for you .
enjoy rom hopping ill enjoy my 20 + hours of battery life with miks 4.5 and 17 hours on CM7
matt2053 said:
Sounds like you've experienced a mix of software, firmware, and hardware issues and blamed them all on the ROM.
Click to expand...
Click to collapse
Lot of people with broken hardware then because I've seen many of the issues posted by other folks. In fact co-worked has rooted Droid II and he has some very similar issues. Only hardware that may have issues is my headset. But it worked perfect on TP2.
Part of the problems are Froyo 2.2 and some stupid limitation in Google Apps. Which is why I like Hybrid ROMs that have some Gingerbread 2.3 compoents that address some issues.
Full Gingerbread 2.3 ROMs are not ready for prime time yet (for me). I look forward to an official release.
BK553 said:
So make one yourself, nothings stopping you, all the pieces and knowledge are free. Your post on here doesn't really serve a purpose.
Click to expand...
Click to collapse
I might, I used Calkulins Kitchen for TP2 and stuck with the same ROM for 7 or so months. But it did take months of F'in around with it to know what works well with what.
Trying to avoid that time sink. By the time I get it "right" Gingerbread 2.3 will probably be out and solve many issues.
HipKat said:
I actually DID read the entire thing and everything you posted works in king's Ultra Froyo, for the most part
Click to expand...
Click to collapse
Thanks I had that on my list to look at.
CheesyNutz said:
i think its time for you to start learning how to make your own rom but wait your to lazy . i have a feeling no matter what anyone says here will be good enough for you .
enjoy rom hopping ill enjoy my 20 + hours of battery life with miks 4.5 and 17 hours on CM7
Click to expand...
Click to collapse
Well I was kinda under the stupid assumption when I bought the EVO Android worked !!
Now I have to build my own ROM. Geesh.
Again I don't think my list is too demanding. Some issues are pet-peivish, I admit.
Stock battery life is fine with me.
CM7 battery is looking respectable. But the phone fell flat on it's face before it could make it through one battery cycle to really know. When EVERYONE says GPS works I may give CM7 another go. By then my guess is a leaked GingerBread 2.3 will be out.
mswlogo said:
Well I was kinda under the stupid assumption when I bought the EVO Android worked !!
Click to expand...
Click to collapse
Last I checked it does work, maybe not how you want it to exactly, but work it does
Now I have to build my own ROM. Geesh.
Click to expand...
Click to collapse
QQ
Again I don't think my list is too demanding. Some issues are pet-peivish, I admit.
Click to expand...
Click to collapse
I'll address this in a bit
Stock battery life is fine with me.
Click to expand...
Click to collapse
Then run stock...
CM7 battery is looking respectable. But the phone fell flat on it's face before it could make it through one battery cycle to really know. When EVERYONE says GPS works I may give CM7 another go. By then my guess is a leaked GingerBread 2.3 will be out.
Click to expand...
Click to collapse
How did the phone fall flat on its face? GPS issues?
Basically what you're doing is you're "customering" the developers. You're wanting to take the best pieces of all of them and automagically jam pack them into one ROM completely tailored to your needs. The only way this is going to happen is if you dive in and start helping or you build your own ROM. This post would have served much better purposes had you asked if anyone knows of a ROM that does all of these functions instead of going out and slamming each ROM for what it doesn't have. Each dev is going to take their own work their own way and that's the end of the story. If you don't like it, you have a few options, do your own work or quit your *****ing. There are a lot of things that I would LOVE to see in CM but until I bust out my coding chops or start adding to the development table, there's not much I can really do except thank him for his work, donate, and be happy that there are a ton of people out there donating their time to making this **** better.
I've been having the same problem. Calkulin's is the closest I have come
Un-root And update download the file from here: http://forum.xda-developers.com/showthread.php?t=975888 and apply. This will give you stock and S-on.
That simple!
Thanks for the info, but the fun is just beginning. This is always good to have just in case you have to return it.
You should be able to load any stock RUU. As long as the hboot and the recovery exist in the RUU, it should return you to a stock condition.
Jaywan, how about a simple root and s-off?
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
ok ok, I hear yah. I will just bite the bullet and type in all 90 of the commands tomorrow when I get off work.
BTW, I left the MT4G and came over to verizon also. I went to the SGS4G before I left tmobile. Lack of dev support for that phone made me give it up. Thanks for coming over to the Thunderbolt.
also, take a look at this thread I started. Somethings up with this one click unroot deal.
http://forum.xda-developers.com/showthread.php?t=1004567
Jaywan said:
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I heard him meantion he wants people to learn adb so if something happens further down the line they can use it
Seriously I'm with him, the hardest part about adb for me was getting it installed. The root was easy and took 30 min
sent from my Thunderbolt
For what its worth, he said feel free to post the one clicks, just give credit. I dont honestly care however, copy, paste, seemed simple enough. Was no where near as hard as the original root method for the DInc.
Sent from my ADR6400L using XDA App
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
ShanDestromp said:
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Are you a troll or do you really believe all that crock you just posted?
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Either you are a troll, have a personal issue with me, or have a seriously problem.
jcase said:
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
Click to expand...
Click to collapse
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
jesemalave1 said:
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
Click to expand...
Click to collapse
o.m.g.
Dude it doesn't work that way on this phone. It is not the G1, z4/visionary/anyonphoneroot does not work, root REQUIRES adb (even with one click).
Fact is, you can't root this phone, temp or perm, one click or not, without ad.
If you can find a way, please do. We are awaiting your one click, root that does not use adb, and is not dangerous.
fyi one click has been released, hours before your post.
Code:
while (true) {
facepalm();
}
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
jcase said:
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
Click to expand...
Click to collapse
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
jcase said:
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
Click to expand...
Click to collapse
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
jcase said:
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Click to expand...
Click to collapse
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
You are missing the point, and obviously did not read anything. This will be my last time wasting time with you until then.
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them, or hell even better we could really use you to go after HTC (in all seriousness).
ShanDestromp said:
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
Click to expand...
Click to collapse
I agree!! If anyone is in violation of GPL license it is HTC.
And once we have that kernel source in the hands of the community amazing things will happen!!
Once the custom kernels start flying you will see the TB doing crazy things. I can only imagine 2GHz speeds or insanely efficient battery life (to name a few)!
ShanDestromp says "And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault. "
This has got to be the stupidest statement I have read in a long time, I can guarantee, If you used a 1-click method and it bricked your phone you would be screaming " where's the oversight in this forum, I cant' believe that that mods would allow faulty programming to be posted."
Jcase I for one am glad you are stepping up and doing what needs to be done to prevent a potential $750 brick, thank you sir.
jcase said:
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Click to expand...
Click to collapse
I'm not privy to any private conversations, nor do I read every thread here on XDA, so my general impression, which I'm sure is shared based upon what others have said, was of a more explicit "No you cannot," not a "do you mind if I take a peek first". Furthermore, I did not name any one individual "responsible" for any blockade; I only began to interact with you once you brought yourself into the thread. Beyond that, if you go back to my original post, I explicitly thank the people who made root possible at all.
jcase said:
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them
Click to expand...
Click to collapse
For starters I don't know much, if anything about them other than they exist. Unless I personally see something that I think is in violation, I assume good faith. I certainly don't seeking violations.
jcase said:
or hell even better we could really use you to go after HTC (in all seriousness).
Click to expand...
Click to collapse
I'm guessing you're referring to the fact that they didn't release the kernel source as expected this week? I'd mentioned it in another thread, though I don't recall which anymore; but from what I recall of GPLv2 developers have 60 days from the "official" binary release to provide source. To expand on that, HTC has 60 days from when the phone officially went on sale, to provide upon request the source code to any GPL licensed software, however it is version specific. That is to say 60 days from March 17th to make available the source to the firmware that was on the phone when released (since to the best of my knowledge there have been no other OFFICIAL firmware versions released).
Of course any such source will inherently exclude any third party proprietary software, for example if HTC used a closed-source bluetooth stack (not saying they did, just a hypothetical example). Additionally, there isn't any specific method to release stipulated. If HTC wishes they could mail out copies of the source on 3.5" floppies and still be within the rules; and all this assumes GPLv2 is how Android is licensed. If its v3 then I honestly have no clue if any time provisions exist.
I just want to reiterate, I have no ill-will to you nor anyone else. It appears as though the whole issue stems from miscommunication.
Hello again. I have been flirting with the idea of flashing a custom ROM, but never could bring myself to do it, mostly because, up until now, I didn't have a mainstream phone (Milestone X with nTelos). Now that I have a Nexus 4, I know that it's completely feasible. But, I have several questions before I do. Most of them are about comparisons, but some are about topics that I just don't understand. I know that probably every question has been answered on here somewhere, but the problem with finding the answers lies in sifting through hundreds of pages of threads and topics, where people are talking about a hundred different things. It's quite the overwhelming task to even know where to start. So, if you don't mind, I'd like to ask those questions here.
1. What are the 3-4 major, stable custom ROMs available for the N4?
2. What are the benefits, or highlights of each ROM when compared to the others?
3. As long as I have a current Nandroid backup, I really have nothing to fear, correct? I could always go back?
4. What are the really technical things I see people talking about (radios, baseband versions, I think), and do those apply to flashing a custom ROM? Will I have to know anything about them?
5. Will any app downloaded from the Play store work on any custom ROM? The two I'm most concerned with are GV and Messaging + GV.
6. Will my phone operate just as it does now, or will I have to input a lot of settings to get it to work with my carrier?
What I'm really looking for in a custom ROM isn't completely the ability to customize every last detail and setting. Rather, I'm mostly interested in something that just 'pops'.. something that looks and feels awesome compared to a stock ROM. Beauty, speed, responsiveness and most of all, battery life, are what I'm after.
Speaking of responsiveness, I've learned that this community is A+ when it comes to assisting those of us that seek more Android knowledge, so, allow me to say 'thanks' ahead of time!
Btw, obviously, I'm running stock 4.2.2, am unlocked and rooted, and have TWRP recovery.
Regards.
wvcadle said:
Hello again. I have been flirting with the idea of flashing a custom ROM, but never could bring myself to do it, mostly because, up until now, I didn't have a mainstream phone (Milestone X with nTelos). Now that I have a Nexus 4, I know that it's completely feasible. But, I have several questions before I do. Most of them are about comparisons, but some are about topics that I just don't understand. I know that probably every question has been answered on here somewhere, but the problem with finding the answers lies in sifting through hundreds of pages of threads and topics, where people are talking about a hundred different things. It's quite the overwhelming task to even know where to start. So, if you don't mind, I'd like to ask those questions here.
1. What are the 3-4 major, stable custom ROMs available for the N4?
2. What are the benefits, or highlights of each ROM when compared to the others?
3. As long as I have a current Nandroid backup, I really have nothing to fear, correct? I could always go back?
4. What are the really technical things I see people talking about (radios, baseband versions, I think), and do those apply to flashing a custom ROM? Will I have to know anything about them?
5. Will any app downloaded from the Play store work on any custom ROM? The two I'm most concerned with are GV and Messaging + GV.
6. Will my phone operate just as it does now, or will I have to input a lot of settings to get it to work with my carrier?
What I'm really looking for in a custom ROM isn't completely the ability to customize every last detail and setting. Rather, I'm mostly interested in something that just 'pops'.. something that looks and feels awesome compared to a stock ROM. Beauty, speed, responsiveness and most of all, battery life, are what I'm after.
Speaking of responsiveness, I've learned that this community is A+ when it comes to assisting those of us that seek more Android knowledge, so, allow me to say 'thanks' ahead of time!
Btw, obviously, I'm running stock 4.2.2, am unlocked and rooted, and have TWRP recovery.
Regards.
Click to expand...
Click to collapse
1. No
2. No
3. Lots to fear. Can go back though.
4. Search, read, & learn a bit before you start flashing. You need to know EVERYTHING about everything ahead of flashing.
5. Apps are OS version / phone / country dependent.
6. Yes
You have a bit of searching but l o a d s of reading ahead of you.
Good luck!
Vangelis13 said:
1. No
2. No
3. Lots to fear. Can go back though.
4. Search, read, & learn a bit before you start flashing. You need to know EVERYTHING about everything ahead of flashing.
5. Apps are OS version / phone / country dependent.
6. Yes
You have a bit of searching but l o a d s of reading ahead of you.
Good luck!
Click to expand...
Click to collapse
I guess I'm not understanding your answers to numbers 1 and 2. Are you saying you can't answer those questions, or that you won't.
As for the rest, thanks, really. But although I generally always appreciate brevity, it doesn't really help me here. I have done a lot of reading on the topic, but the problem is that everyone that's talking about this custom ROM or that one already knows quite a bit, and is discussing some quite technical (like flashing this radio or that one). Another main problem I have is that I'm not sure which ROM I'd like to flash. If I could narrow it down by features, pros and cons, then I could narrow my attention to that particular ROM, and save myself a lot of trouble.
wvcadle said:
1. What are the 3-4 major, stable custom ROMs available for the N4?
2. What are the benefits, or highlights of each ROM when compared to the others?
3. As long as I have a current Nandroid backup, I really have nothing to fear, correct? I could always go back?
4. What are the really technical things I see people talking about (radios, baseband versions, I think), and do those apply to flashing a custom ROM? Will I have to know anything about them?
5. Will any app downloaded from the Play store work on any custom ROM? The two I'm most concerned with are GV and Messaging + GV.
6. Will my phone operate just as it does now, or will I have to input a lot of settings to get it to work with my carrier?
Click to expand...
Click to collapse
1. Google have yet to release their Binaries to AOSP so many of the AOSP based ROMs are still unstable / nightly
2. This CNET article is a good starting point (here)
3. Maybe ADB backup is better to backup your app APKs and data, and an ADB sdcard pull is better to backup your sdcard. Nandroid is good if your restoring a ROM back to an earlier snapshot, but can become messy going from, say, CM10.1 back to stock
4. search and read, read, read
thats all I got. Good luck.
wvcadle said:
I guess I'm not understanding your answers to numbers 1 and 2. Are you saying you can't answer those questions, or that you won't.
As for the rest, thanks, really. But although I generally always appreciate brevity, it doesn't really help me here. I have done a lot of reading on the topic, but the problem is that everyone that's talking about this custom ROM or that one already knows quite a bit, and is discussing some quite technical (like flashing this radio or that one). Another main problem I have is that I'm not sure which ROM I'd like to flash. If I could narrow it down by features, pros and cons, then I could narrow my attention to that particular ROM, and save myself a lot of trouble.
Click to expand...
Click to collapse
Only you can answer them.
Start with a simple rom, with few modifications so you don't get overwhelmed.
____________________________
I was reading for a week before I rooted and flashed a rom on my n1, can guarantee you many if not most in here started like that.
You want to have it all answered in a thread & spooned to you?
I'm sorry to say but you're starting wrong.
Vangelis13 said:
Only you can answer them.
Start with a simple rom, with few modifications so you don't get overwhelmed.
____________________________
I was reading for a week before I rooted and flashed a rom on my n1, can guarantee you many if not most in here started like that.
You want to have it all answered in a thread & spooned to you?
I'm sorry to say but you're starting wrong.
Click to expand...
Click to collapse
Believe me, I'm not asking for anything to be spooned to me. I mean, if I could at least get some help in figuring out which ROM I'd like to flash, that would be appreciated. I could certainly do the leg work if I could just get help deciding on which ROM. I stated in my OP the type of things I'd like to have in a custom ROM. Didn't what I posted put one or two in your head? If so, may I ask which ones? Even with your opening sentence of this reply, you said to start with a simple rom. Any examples?
http://forum.xda-developers.com/showthread.php?t=2009561
At least he has an op that explains a fair bit.
Roastgoat said:
1. Google have yet to release their Binaries to AOSP so many of the AOSP based ROMs are still unstable / nightly
2. This CNET article is a good starting point (here)
3. Maybe ADB backup is better to backup your app APKs and data, and an ADB sdcard pull is better to backup your sdcard. Nandroid is good if your restoring a ROM back to an earlier snapshot, but can become messy going from, say, CM10.1 back to stock
4. search and read, read, read
thats all I got. Good luck.
Click to expand...
Click to collapse
They are more stable than you think, i wouldnt call some of the better ones unstable or nightlies. i've been running aokp for a few months now and it's very stable no major bugs over stock rom for me.
wvcadle - It's hard to say what the best roms are since that's mostly personal taste but some of the more popular roms are ParanoidAndroid, AOKP, Xylon and slimbean. There is a questions section that has lots of threads comparing roms.
neotekz said:
They are more stable than you think, i wouldnt call some of the better ones unstable or nightlies. i've been running aokp for a few months now and it's very stable no major bugs over stock rom for me.
Click to expand...
Click to collapse
I have tried PA and CM10.1, both of which I liked but some minor issues have me back to stock and waiting for stable releases. I think personally I would go CM10.1 once stable.
Test several ROMs, then decide which one better fits your expectations. Nobody can tell which is the best.
I have tested 3 or 4, then I went back to stock and just added some tweeks to it. But hey, that's me!
JanusDC said:
Test several ROMs, then decide which one better fits your expectations. Nobody can tell which is the best.
I have tested 3 or 4, then I went back to stock and just added some tweeks to it. But hey, that's me!
Click to expand...
Click to collapse
I think I'm going to try Modaco's ROM first. Do you know what Kernel it uses? Is it the stock kernel? I'd like to flash Franco's kernel, as I hear it has improved battery life.
wvcadle said:
I think I'm going to try Modaco's ROM first. Do you know what Kernel it uses? Is it the stock kernel? I'd like to flash Franco's kernel, as I hear it has improved battery life.
Click to expand...
Click to collapse
I wouldn't jump into kernel flashing so fast. I'd try a couple of ROMs first.
irishman103 said:
I wouldn't jump into kernel flashing so fast. I'd try a couple of ROMs first.
Click to expand...
Click to collapse
Well, I just flashed my first Custom ROM. I'm pretty stoked! Even though it's one of the simpler ROMs, it's still pretty cool. Hopefully I don't get hooked!
So, is flashing a custom kernel more dangerous than ROMs? I heard Franco has an app he created to flash his kernels.
I wouldn't say its dangerous. There's just more things to tweak and mess with. Voltages, gamma, CPU speed, etc. I'd just get comfortable with flashing ROMs and finding what you want first. And yes, flashing is an addiction. You will now flash hundreds of times only to find you want to flash a hundred more.
Sent from my Nexus 4 using xda premium
irishman103 said:
I wouldn't say its dangerous. There's just more things to tweak and mess with. Voltages, gamma, CPU speed, etc. I'd just get comfortable with flashing ROMs and finding what you want first. And yes, flashing is an addiction. You will now flash hundreds of times only to find you want to flash a hundred more.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Will the other ROMs not work right out of the box, or would I need to tweak all of those settings to get them to work?
Sent from my Nexus 4 using Tapatalk 2
All the ROMs will work out the box. Developers will not turn over incomplete ROMs to the end users. Like now I'm using Paranoid Android...works beautifully, but there are tons of settings built in to mess with. Other ROMs don't have some of its features and vise versa. With kernels, I use the stock kernel with it. I've flashed other kernels but in MY opinion, I like the stock one. So read up on some ROMs, back up and flash some to see what you will like
Sent from my Nexus 4 using xda premium
TBH it will take you some time to learn everything. All the questions you need answered will come in time with you learning Android. Its best to learn by LOTS of reading but you also need some trial and error. You will learn what Roms work best for you and which dont. You will see that you dont always need a custom kernel, and perhaps your screen only needs to 2 more clicks of saturation to have 2.2 gamma while others need to tweak across the board. Once again you gain that knowledge over time. You will get in trouble from time to time, not have help and possibly brick badly, but you learn to fix and work it out, and THAT is really where you learn lots. When you hit a roadblock READ and you will have your answer and in the process gain the knowledge you need.
Good luck and enjoy the hobby!
irishman103 said:
All the ROMs will work out the box. Developers will not turn over incomplete ROMs to the end users. Like now I'm using Paranoid Android...works beautifully, but there are tons of settings built in to mess with. Other ROMs don't have some of its features and vise versa. With kernels, I use the stock kernel with it. I've flashed other kernels but in MY opinion, I like the stock one. So read up on some ROMs, back up and flash some to see what you will like
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
You've been a great help. Really. And I appreciate it. I just realized there was a 'Thanks' button on this forum, so you've got my first one.
One last question, and I'll leave you be... promise (I think!): The three things I'm most concerned with in a ROM deal with power consumption, speed, and, yes, beauty. I can safely say I will never try to overclock my phone, or change any really deep settings. Do those three items bring any specific ROM or two to mind that you can point me in the direction towards?
Thanks again!
wvcadle said:
You've been a great help. Really. And I appreciate it. I just realized there was a 'Thanks' button on this forum, so you've got my first one.
One last question, and I'll leave you be... promise (I think!): The three things I'm most concerned with in a ROM deal with power consumption, speed, and, yes, beauty. I can safely say I will never try to overclock my phone, or change any really deep settings. Do those three items bring any specific ROM or two to mind that you can point me in the direction towards?
Thanks again!
Click to expand...
Click to collapse
No problem. Glad I could help.
And your last question is the ultimate question...lol. It's all about how you use your phone. One ROM might be more efficient for you than it would be for me. You might watch a lot of videos and don't have good reception. That could drain your battery. I'd go with ROMs that have a good thread. Read and read about the ROM before you flash it. Read the first pages and the last. I personally like Paranoid Android and AOKP ROMs. Look in the original development section and read up on Liquid Smooth, AOKP, and Paranoid Android. They are really great out the box and no overclocking or "deep settings" needed. If you have any questions about the two I like I'll be more than happy to answer any questions. Just PM or email me.
Ok, MoDaCo on my N4 and PA 3.0 on my N7!
Yes, flashing custom roms is becoming a hobby!
UPDATED:
released.
ROM thread
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth and SMS messaging.
Otherwise broken telephony.
only some of the sound works. no camera, nfc, location.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
I'm amazed at your skills. And I have learned a lot from reading this thread. More importantly, my VM 816 is still functional.
Sent from my 710C using Tapatalk
I think you can release it whatever people use or not , but 816 is my only 4G phone.I will test it till the Calling Services worked
Ed128 said:
I'm amazed at your skills. And I have learned a lot from reading this thread. More importantly, my VM 816 is still functional.
Sent from my 710C using Tapatalk
Click to expand...
Click to collapse
A lot of what I do is googling errors, borrowing commits from other cm devices with similar chipsets, (and commenting out lines that throw errors in the build until I figure out workarounds... not the most kosher of methods.)
It's fun, but I often lean heavily on stuff that's already been done by others. Grarak put up really nice device trees to work from on this device for example, and my first tweaks at it were just after it had faded from cm nightlies. Made it comparatively easy next to my Optimus or Evo3d.
frank9184 said:
I think you can release it whatever people use or not , but 816 is my only 4G phone.I will test it till the Calling Services worked
Click to expand...
Click to collapse
Odds are the basic call services will be online way before 4G. Especially since my 4G service is still broken and has ben for quite a while. I'll hassle Virgin Mobile about a replacement sim card soon; research and talking with a Ting rep both imply that would fix my issue.
bigsupersquid said:
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth, possibly nfc, probably no location, totally broken telephony.
only some of the sound works. no camera.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
Read this post and you see that clicking the thanks button counts more than voting...
Click to expand...
Click to collapse
I think you should upload the zip. Legacy devices are getting cm 14. Why we are late?
Tim Cook said:
I think you should upload the zip. Legacy devices are getting cm 14. Why we are late?
Click to expand...
Click to collapse
Well, htc certainly won't be releasing N for my a5_chl (Virgin Mobile variant) since they wouldn't even let M out the door for it.
you can partly name lack of manufacturer support.
And I get tired of complaints about nonworking items from people who don't read the OP, so I'm waiting for adequate interest to post it (big upload on poor isp, couple hours.)
Plus there's inability to test dug/dwg and that's twice the upload bandwidth. But few source changes to build for them, and some dual sim owners would enjoy buggy N too.
Several reasons that N isn't out in the wild yet for the a5. But I'll probably set it free to roam soon.
Question about CM14
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Ed128 said:
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Click to expand...
Click to collapse
yes, and yes. I restore cm13 over messed up cm14 regularly.
Still fighting with ril. location not working at all in spite of the switch working. and nfc probably will work once I get the firmware moved to wherever it's looking. but all the sound seems to be working now.
Ed128 said:
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Click to expand...
Click to collapse
Yes you can just Backup and Restore your previous ROM. Just be careful, wipe system and dalvik cache and cache. CM13 has some problems but mostly everything works on 816.
ajones23 said:
Yes you can just Backup and Restore your previous ROM. Just be careful, wipe system and dalvik cache and cache. CM13 has some problems but mostly everything works on 816.
Click to expand...
Click to collapse
ninja'd you this time.
I've been able to dirty flash 14 over 13, but previously installed apps get denied permissions and stuff like that.
bigsupersquid said:
ninja'd you this time.
I've been able to dirty flash 14 over 13, but previously installed apps get denied permissions and stuff like that.
Click to expand...
Click to collapse
Yup you got me, I usually don't dirty flash always clean flash. Since I use Root Essentials as partition of sdcard. When ever you get it to work,I'll be a tester. Let me know.
That's something I can deal with. Just don't want to go too far past my limited "expertise". And, not trying to hurry things. I'm a happy CM13 customer.
Sent from my 710C using Tapatalk
Ed128 said:
That's something I can deal with. Just don't want to go too far past my limited "expertise". And, not trying to hurry things. I'm a happy CM13 customer.
Click to expand...
Click to collapse
If you need help,just ask,I'm always on and off.
bigsupersquid said:
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth, possibly nfc, probably no location, totally broken telephony.
only some of the sound works. no camera.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
Read this post and you see that clicking the thanks button counts more than voting...
Click to expand...
Click to collapse
Love your work!!!
D816w
what could be the estimated date for the first beta? hunger to flash this CM14.....
Naxym said:
what could be the estimated date for the first beta? hunger to flash this CM14.....
Click to expand...
Click to collapse
Its really not a good idea to ask for ETAs. Specially when not many things work.
Naxym said:
what could be the estimated date for the first beta? hunger to flash this CM14.....
Click to expand...
Click to collapse
ajones23 said:
Its really not a good idea to ask for ETAs. Specially when not many things work.
Click to expand...
Click to collapse
It's ok in this thread, since that's kind of what it's about.
If I can stabilize the radio glitches enough that all the telephony stops force-closing constantly I'll release an alpha, there isn't tons of interest but there seems to be enough.
After all, if I were in your shoes I'd want a release to check out.
bigsupersquid said:
It's ok in this thread, since that's kind of what it's about.
If I can stabilize the radio glitches enough that all the telephony stops force-closing constantly I'll release an alpha, there isn't tons of interest but there seems to be enough.
After all, if I were in your shoes I'd want a release to check out.
Click to expand...
Click to collapse
I sorta may get a flashing bug if you put up a alpha. I just thought I would put my 2 cents in about ETAs. Not a good thing sometimes.
ajones23 said:
I sorta may get a flashing bug if you put up a alpha. I just thought I would put my 2 cents in about ETAs. Not a good thing sometimes.
Click to expand...
Click to collapse
A lot of developers get uppity about ETAs.
I imagine with hot new devices and hundreds of posts a week it would get really old.
I usually just warn people that I have too much on my 'real-world' plate for my own taste and that my hobby work (this) ends up on the bottom of my get-er-done list.
Plus I like to put up it's-almost-ready posts and then take forever to upload:angel: and similar annoying delayed releases. Like I rebuilt for the OV a little while ago, posted about it, and never debugged or released it at all.
Bad dev :cyclops:
I put this thread out in general 816 to encourage comments and questions.
Once the alpha is out I'll open a thread in Original Dev (and post a link to it here) since cm14 is definitely original right now.
About to flash another test build!
Test has sms but no phone.
No Bluetooth.
Close to being uploadable.
assuming the next build isn't in any worse shape than this one (should have working BT, and I'm really hoping for at least 3g data and maybe phone service) then I'll try pushing the zip to AFH. If my landline internet stays connected long enough to get it upstream...