Related
Hey guys I saw this post strolling around on the internet. Maybe one of our fine devs could help this ambitious guy out..
http://www.droidforums.net/forum/droid-x-hacks/93955-getting-custom-kernels-running-droid-x.html
freaking sweet ! spread this !
Very interesting! Might want to move this thread (or a copy of?) into the Droid X development section.
For a minute there it looked hopeless..but it seems like this guy is really working hard on this. He has found the problem.. apparently the issue is not kenex but drivers. He needs help from someone that has experience with coding drivers...COME ON guys WE CAN DO IT! Lets get all the milestone and droid x devs on this!
This thread was mentioned in one of the threads on development. I hope he's successful, but I'd be surprised if he succeeded.
This guy needs DZO! DZO is a genius with a PhD in computer science. He's the one that pioneered Android on the HTC Vogue (a WinMo phone) and made it possible for all the other winmo htc's to get android. he rewrote all the drivers and such to work with those phones and I'm sure he is smart enough to do this. However, he lives in new zealand i believe and therefore cannot really get an X. Hopefully something can work out.
I think if he said that he said that he would work on the dx then we could get enough donations together to get him a dx. I don't think he would have to have access to the Verizon network to test wether or not the radio is working.
Sent from my DROIDX using XDA App
I have been SCOURING the web for possible Motorola Bravo ROMs to no avail. I've read everything from the Bravo not possessing the correct files/firmware to the Bravo not having the lack of restriction needed. Point blank, I'm willing to put my phone up for experimental development to jump start this process for the world of Bravo users. I'm an employee of AT&T and I'm tired of the way we kill the freedom of this phone. It's time for the barriers to come down, point blank. Please, developers, feel free to contact me through this post if you are interested. I've heard about making dumb-files for the phone (I'm a moderate noob, to say the least). Therefore, I'm willing, with correct instruction, to create one of these system files to help out or whatever else may be needed.
Thanks
I just got a Bravo and love this guy! I prefer it over my Captivate and Aria. I'm all for some customization to come to this VERY underrated device.
same here. nothing has really been done with this phone. at least we could get 2.2? if nothing else
Hmm
http://community.developer.motorola...RAVO-development-resources-available/m-p/8304
BravoMotorola said:
http://community.developer.motorola...RAVO-development-resources-available/m-p/8304
Development recourses officially available for the Motorola Bravo!
Click to expand...
Click to collapse
What does this mean for us Bravo owners, exactly? Thanks.
What it means?
Just makes it easier I think...if you a Motodev member! So, really nothing.
check out my new thread in this forum, i am porting bootstrap used on d2/dx/dpro to the bravo to get clockworkmod running and then we can get some roms!
DEVS! Would it be possible to use a FroYo Kernel for CM7 like the Droid X Developers did?
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Original Android <3ers! said:
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Click to expand...
Click to collapse
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
daddy_droid said:
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
Click to expand...
Click to collapse
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
And queue take 3... omfg, when will people learn, this is not to debate ETA.
Original Android <3ers! said:
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
Click to expand...
Click to collapse
really not allowed to talk about that? Since when can someone else take away my free speech rights to ask when something is gonna to be released? If you dont want to answer a question for eta then just dont reply to it. After all no one is making you reply to anything.
If you HAVE NOTHING TO SHARE DONT POST IN DEVELOPMENT.
I'm trying to be honest with you and save you from being flamed. Did you even read the first post? The devs don't have the kernel source for the Epic 2.3.3 or beyond, nor do they have it for the Nexus S 4G, so until then, they have to stop developing because they cannot do ANYTHING without it. So an answer to an ETA is never.
lynyrd65 said:
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
Click to expand...
Click to collapse
I think this would be a good idea while we wait for the Kernel source actually...
nullghost mentioned that CM6 would be in the same state as CM 7. Idk why, but yea.
No no, we're saying use the FroYo Kernel for CM7!
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Darkshneider said:
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Click to expand...
Click to collapse
No.
Sent from my SPH-D700 using XDA App
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
The reason being? I dont get how theres source for 2.2 and we cant get CM6, how would 2.3 source help us get CM7 working?
And I got my answer while typing because of Deca. Thnx!
Decad3nce said:
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
Click to expand...
Click to collapse
So you don't like me?
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
I don't mind you, your motives are good, but this environment fosters redundant and pointless poo flingin'. Which usually leads to us responding with the same information, over and over.
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
Great way to lose another Dev.
Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
lynyrd65 said:
Great way to lose another Dev. Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
Click to expand...
Click to collapse
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Decad3nce said:
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Click to expand...
Click to collapse
Developers tend to support developers.
Sent from my SPH-D700 using XDA App
Typical scenario is;
v 0.1 based on this and that.
v 0.2 changed launcher, added ringtones
v 0.3 new wallpapers, added ram script
v 0.4 added new market, added google+
Excuse me!?! This is not development. This is stealing!
I think these people should just wank instead of copy/pasting. Would be more beneficial for both public and themselves.
Rant over.
Thank you.
calyxim said:
Typical scenario is;
v 0.1 based on this and that.
v 0.2 changed launcher, added ringtones
v 0.3 new wallpapers, added ram script
v 0.4 added new market, added google+
Excuse me!?! This is not development. This is stealing!
I think these people should just wank instead of copy/pasting. Would be more beneficial for both public and themselves.
Rant over.
Thank you.
Click to expand...
Click to collapse
Agreed, but if credit is given to original devs you can't really call it "stealing" cause Android is OSP after all...I'm no dev myself but it does seem many ROMs available are CM tweaks achievable with a few market downloads or simply AOSP with extra's...however sometimes certain ROMs begin as "Zip developments" and get later support with real devs and change fundamental features (kernels, code-base etc.) so it's not all bad...
Totally agree..........
But it's not the actual non-development of new roms that is getting on my nerves the most, its the constant *****ing and arguing through lack of understanding different languages etc etc..........
All i have to say is read the threads carefully as i've noticed some people who don't speak english very well get the hump on as they don't understand clearly what people are saying.
I know i've had my rants in some of these threads before and i don't blame anyone else for doing it too. I've managed to restrain myself the last few weeks as our arguments are falling on deaf ears so whats the point, i'll just ignore the idiots making fools out of themselves by bringing us stuff we've already had for a long time and stick to what i know best.
What you've said is true Scratch...even if the ROM cookers do bring something new often nobody knows what that new stuff is because of the poor English. I'm not trying to insult them but I would recommend, especially with a specialized thing such as compiling/ making a ROM, the English needs to be clear and concise so everyone knows what is being released, what changes have been made and what's been modified. More often than not, as you say Scratch, people get upset because of a misunderstanding. Maybe those struggling with the language can consult friends/devs and ask exactly how to express something they've done in their ROM so everybody is clear on what's happening.
Scratch0805 said:
...I've managed to restrain myself the last few weeks...
Click to expand...
Click to collapse
True, I have got quite a lot to say over this entire fiasco over the Android 4.0 "ports" and "source builds" that is currently playing out in the dev zone like a long dragging soap opera, but, its just not worth it, so, just let them argue over themselves who is first and who is the true dev and what not. Besides, it's not a good feeling when these Zip Devs accuse you of various stuffs when you speak out against them. It's extremely childish and irritating to read those posts, but I guess it can't be helped. Zip developers are not a localized phenomenon, they are everywhere, and since Android and ROMs like Cyanogenmod are Open Source, we have nothing to say, and have to live with it.
There's another new phenomenon which is playing out and can be seen on pretty much every ROM. Someone gets a ROM to boot / work at a basic level, create a thread and build up major hype and hoopla on it, and EVERYONE of these "devs" proclaim "I need help to do this and do that./..... bla bla bla". Zip dev is not such a big issue per se, but, the level of intellect is terribly low among the "devs". I believe most of them are what? 12-13 year olds, and, they act their age perfectly, unlike someone like Jacob.
/End Rant
Case in point, after Arco has announced his intentions and the fact he already has a working port in progress:
I was first, it was my idea, I continue and basta.
Click to expand...
Click to collapse
Enough said.
Ahah, doing small things for the buzz (pun intended), acquiring a fame in trolland
Lol, I've made myself clear on this too.
" the ability to read is good,
the ability to understand what you've read is great "
http://www.androidpolice.com/2011/1...om-developers-i-think-we-need-to-have-a-talk/
3xeno said:
dragging soap opera.
Click to expand...
Click to collapse
Don't you mean aosp opera? Hehe...okay, I'll stop with the bad jokes.
And I fully agree with the topic. Anyone can open up any rom .zip paste in some apps, reflash and repackage it as your own.
Agree with this. Sadly I'm one of the offenders, that will have a moan at people developing zip-roms. I accept that this isnt the greatest way to deal with people on forums like theese. But it seems the only good way to get my point across to people that aren't that great at english.
Although, I must add one thing. I've seen roms get tossed around the development forums like mad. It seems to go like this in the dev. forums.
People create a booting rom. Or compile a new one.
People add a few fixes, someone creates a spin off.
Original dev discontinues rom, other 'developers' ask to continue it, even when they have projects in hand.
Someone picks up the pieces months later. After even the re-contiuned rom is given up with.
People spin roms off from there.
All i can say is dear god. I have been reading all that threads last few days and i was frapped how people are shalow in glorifying them selves and their so called development skills. I didnt want to coment anything cauze i have run into such argument once before with someone who was constantly refusing to understand what i am saying and i dont want to do it again, so i leave my thoughts here.
So people should get on the ground for change and start doing something usefull instead of make dozen threads, first when you dig something, than another one when you are asking if it can be done and finaly one when you "do" something. What they have done is nothing. They are just thanks chasers. In last few days there were more new roms than it was for whole Wildfire lifetime.
I remember tje days when there was just three or four roms and they worked, you hear me, they worked. So stop posting such s**t unles u did something that is realy worth it.
Sent from my HTC Wildfire using xda premium
Yes you are right, zip development is horrible. Lately there has been a major rise in "new" roms that have been hitting the development thread. I swear I have seen at least 5 to 10 roms all based on CM7 or oxygen. And what's different? It's "fast and stable" "Is themed to look like ICS" "Has a script that I actually don't know what it does but it must do something good". And its "my" rom because I grabbed a rom.zip from a device that runs oxygen smoothly and added the boot.img and the build prop right from the CM7 rom.zip and then cooked it and I posted it under MY account so its MY rom. There is a problem though, my genius copy/paste skills on my computer that took forever to build up are limited to actually being able to fix problems with things like Bluetooth and GPS, etc. So what do I do then? Hell I request "help" to fix the problems and once a genius like acro or another real dev comes in and fixes it for me, I take the fix and say it was all MY work. AOSP stands for ANDROID OPEN SOURCE PROJECT. The source is open to anyone that can use linux terminal (that's half the problem). The other problem is that no one could be bothered taking the time to actually learn a skill. They want to do something now, and now only. They won't spend hours and days learning how to program in java or C because it takes "too long" and just wants to begin this so called "deving" now. This is a rant about zip development, but wait you say, I do .zip development though? Yes I do, but what I am talking about is .zip development that is based on a .zip that is actually OPEN SOURCE. If something is OPEN SOURCE there is no point in taking a compiled .zip and "porting it" to our device. You do this because its easy for you to hit download and copy and paste, but you don't "have the time" to setup a download of the source and compile it to a rom. Zip development that is for CLOSED SOURCE on the other hand is way different. HTC, MIUI, etc. are all roms that have no open source code so all the work has to be done based on a .zip. Since the code is not available this is the only option. This in my opinion is the only kind of good .zip development since there is no source to build from. I would love to download the source and mess around with the ICS source and try to compile something but my computer is got really bad specs and my internet is so slow. I will just leave that kind of work to acro and the real devs
I agree with this. Looking through the more recent Wildfire ROMS, I can see a pattern for most. So, I have started to come up with a fight back, for individuality and mostly, for a better mobile experience. It would mean a lot if you could help me out with THIS.
Sorry to ask in this thread, but I thought it might be a good idea
Before I get accused of zipfile developing, I only compiled an edited kernel for the ROM to allow touchscreen to work a little.
I am not a "zipfile" developer and I am not going to be, my interest is in kernels.
I happened to come to xda at the wrong time, first thing kaassaus did was ask me to follow a tutorial to get touchscreen working (which took all of 20 seconds).
I think posting an ICS zip is okay FOR NOW because there is no OPEN source for the wildfire for it, and Arco is NOT breaking the GPL because he hasn't redistributed it yet.
Sent from my HTC Wildfire
We are not accusing anyone. My point is dev section is not a learning section. Those who want to learn development can pop into chefs section instead of releasing a rom with 2 zillion bugs.
There is a reason for this forum is not called xda-tweakers. Because our devs are devs. They are not steve jobs like tweakers.
2nd rant over. Class dismissed
Okay, Zip development is not so bad, actualy is needed in some points. For flashing kernels or some other things. But look at some of that AOSP-fast and stable roms. What do they bring us? Nothing. It is just repacked CM nightly or stable. To "develop" such rom you need WinZip and in best case Android SDK if they decide to decompile and recompile few apps instead of treating them with winzip too to change few icons and voila, NEW ROM. Better yet someome will take any theme and implement it into framework.And he will be so proud because his rom has diferent look. What else we can still expect is ES file explorer instead of OI, Miui galery, themed keyborad, different font and unforgetable scripts which do god knows what. They are the main part. Is that a rom? No it isn't my dear friends. Its a disrespect to any real developer here. All that we already have. We have themes, we have scripts we have everything that flashable and we dont need another yet ****y rom to tell us what is fast and stable.
Sent from my HTC Wildfire using xda premium
I don't find anything wrong in updating an already present ROM's with new applications update ,... even though i must say there is a trend in past few weeks that lot of ROM's in buzz section were merely identical and there was no development in them
I was browsing the old threads of the Dev Zone, and came on this:
http://forum.xda-developers.com/showthread.php?t=884659
Amazing, right? It's deja vu all over again.. (PS - Don't bump that please. lol)
I am a noob, and I know I will never be as experienced as other developers.
That is why I do not develop ROMs, and develop things I am good at.
Hi guys,
I am trying to develop ROMs for Android. And I have developed one. This ROM is based on the stock HTC One ROM. Getting straight to the point, I need some Beta-Testers as I don't have the device with me. Sure, I'm gonna buy it soon. But in the meantime, I don't want to waste my precious time. SO< ANYONE INTERESTED? :highfive:
Thanks in advance.
Blind builds like what you did are not encouraged because it magnifies the chances of things to go wrong since you can't test the ROM yourself. Just a not of caution
pandaball said:
Blind builds like what you did are not encouraged because it magnifies the chances of things to go wrong since you can't test the ROM yourself. Just a not of caution
Click to expand...
Click to collapse
yea. I know it is a blind build, but I didn't really do any huge modifications. Just some changes here and there. I have the build ready with me. I just need a guy to tell me surely that this build is safe to work upon further. That's because I am gonna resort to android development in future.
Short of sounding like a D-bag, what you're asking for is a little ridiculous. You sound like you're new to developing, new to the boards (Welcome btw) and don't have the device yourself. Its like asking a random person to test drive a car you just built by reading a "Build-it-yourself Car". If you had more credibility, i.e. More posts, past work, past examples of ROMs or even a list of what was "modified" in this ROM, people might step up to help.
V2IBH2V said:
Hi guys,
I am trying to develop ROMs for Android. And I have developed one. This ROM is based on the stock HTC One ROM. Getting straight to the point, I need some Beta-Testers as I don't have the device with me. Sure, I'm gonna buy it soon. But in the meantime, I don't want to waste my precious time. SO< ANYONE INTERESTED? :highfive:
Thanks in advance.
Click to expand...
Click to collapse
what's so different with your rom and the roms already out ?
ant78 said:
what's so different with your rom and the roms already out ?
Click to expand...
Click to collapse
Everyone's gotta start somewhere, even just doing this is good practice for him.
I'd test for ya op but I rely heavily on this phone and I'm s off. I'd advise any testers to be s on just to be extra safe
Sent from my Tricked out HTC One
Squirrel1620 said:
Everyone's gotta start somewhere, even just doing this is good practice for him.
I'd test for ya op but I rely heavily on this phone and I'm s off. I'd advise any testers to be s on just to be extra safe
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
I do agree you have to start somewhere. But he should get his own device and test it himself. That is better than just creating something that you don't even know it works.
Some "experienced" developers sometimes don't even own the device to create a custom ROM. But the key is that they are already experienced and would know how things work. But for someone who is starting out and have very little experience, they are better off doing the tesing themselves.
I bet he is not really a dev but more like a zip dev if you know what I mean.
OP.. please understand. Your new here, you have no proven track record, your asking people to entrust a €600 device to something that you have 1. not clearly laid out in your opening post 2. have no means to test yourself 3. can not provide support if you feck up other peoples devices.
Sorry but without any past experience here your trust level is 0.
Your request is akin to a nigerian ringing me and telling me I've won a multi-million € win and all they need is my bank account, and credit card info....
At least stick around here, get the device yourself, build up your reputation, and try a few things yourself and then clearly lay out what you have done in any further thread requesting testers because blind faith only goes so far......... unless you are indeed Jesus (or a nigerian with my mulit-million pound win)...
Wow.. so we can't waste his precious time. Lol
Sent from my HTC One using Tapatalk 2
Hey hey hey! Please don't classify me as a ZIP dev..!
N yeah. Here's the change-log of my ROM(though it's not much):
1. Rooted
2. Busy-box added.
3. Changed the boot-animation a bit.
4. changed the power down animation a bit.
And' thats all.
V2IBH2V said:
Hey hey hey! Please don't classify me as a ZIP dev..!
N yeah. Here's the change-log of my ROM(though it's not much):
1. Rooted
2. Busy-box added.
3. Changed the boot-animation a bit.
4. changed the power down animation a bit.
And' thats all.
Click to expand...
Click to collapse
I think everyone has to start somewhere, but I think the people are looking at stuff like what did you change in functionality not just cosmetics. Try playing around with build prop and stuff
Sent from my HTC One using xda premium
Android The Greek said:
I think everyone has to start somewhere, but I think the people are looking at stuff like what did you change in functionality not just cosmetics. Try playing around with build prop and stuff
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, sure. I would work on this ROM further. But somebody has to test this adolescent ROM first, because it could happen that I work upon this ROM without testing it and then it would happen that it won't work. And then I could have to roll-back, only to start from scratch.
And that is why I'm asking you guys to test this out. I guarantee regular updates, fixes, etc.