As in the title, I recently purchase a new HTC phone, and it's built for ChinaTelecom(carrier). So i think most here haven't even heard about it and it's called:
--------HTC new Desire VC
--------aka HTC t238d
Now comes the problem!!
Before this phone which i got it nearly free, i always relied on my oldold milestone. Quite old fashioned but really good phone and the most important thing is that Milestone is a WORLDWIDE POPULAR phone, so cm7, miui, anything else, worked hard with it~ Long casual years with Milestone, even after some 3rd-party rom groups stopped supporting it, it still has got lots lots of fans and hackers work on it. Until the day i change my phone, i was extremely using almost-perfect ICS on my oldstone...
But the stone finally get exhausted at everything, everything is not smooth, not one more app is installable or the phone became veryvery not-usable... And this new one mentioned above is great at these points, quite good hardware, stock ics etc.
The main thread comes: I hate Chinese carrier stock roms, and I hate HTC Sence also... And I have been using cm7~9 nearly all the time and of course, it's my favorite. But i can't find my SPECIAL phone in the cm10(or 9) support list without doubt. And no foreign hackers works on it without doubt again. There do exist some Chinese developers making t238d custom roms but they are not good.
Let me explain, in China, both developers and customers prefer a thing they called Chinaly I suppose... They don't like stock android, i mean the google one, they split out the gapps with nothing left but lots of Chinese things instead, i.e the huge Tencent Empire products maybe you have heard. Even they hate holo style!! Millions and Millions of apps are fake-ios themed. I am totally minority so not a single locale developers like my idea indeed.
I like google, like cm, like HOLOed apps, like fake-vanilla things even. And CM becomes my last hope. I have to port it to my phone on my own...
What I got
--------totally pure Linux OpenSuse(i686/x86-64 both)
--------openJDK, gcc things
--------SDK,NDK thins
--------the great kitchen
--------repo init -u git://github.com/CyanogenMod/android.git -b jellybean , repo init -u git://github.com/CyanogenMod/android.git -b ics both (jb prefered, i love cutting-edge toys... but no suitable develop skill sadly)
--------primodd kernel sources from here: h t t p://htcdev.com/devcenter/downloads (search desire vc you will also find them)
Then i think i have got a prepared environment and both clean complete cm src and htc stock kernel src, that means i can port cm to my phone!
But, if I really can, what shall i do now.....Just a little advice will be very very appreciated, cause i've struggled with those problem for quite long time.
And if i suck, which means i just can't do what i want because of any reason, please tell me too.
Thank you guys anyway！
Everyone that asks this gets the same response. There are many basic porting guides all over the web. Google for some of those. Find a phone with a similar build type. Might get lucky and find a device you can build and it boots, then you just have to fix device specifics. You are attempting to embark on a new journey. I don't have your device. I can't really help. You need to figure out a lot of this on your own.
What lithid said also applies to the rest of us. We can't say "Oh right, edit this file, that file, and the other file, and viola you'll have a perfectly booting CyanogenMod." It takes some experience, a lot of reading, and a lot of trial and error. Also expect the device to be unusable/unbootable 90%+ of the time so if this is your primary device I suggest holding off on the development.
So short story: Google it.
Related
Hey there, everyone.
I'm just looking for some advice. I've been using my Verizon Samsung Fascinate since November, and for the most part have been a very happy user. Ever since I installed a Gingerbread-based ROM, I have been extremely happy with both the device's performance and new features (nothing says cool like the Old TV Shutoff animation). Lately, I have been wanting to try my hand at modifying and packaging my own Android ROMs for the Fascinate. Obviously, I have never done something like this before, so I'm looking for some advice.
I've been programming in Java for over a year now and I'm very familiar with the language as a whole. I've used it in various programming competitions through school along with building some applications and tools for the company I'm currently interning with. Right now, I feel that I have the basic programming skills required to look through code and understand what the logic behind it is (at least I hope).
My question for you all is this: should I jump right in and start poking through the AOSP code, or would it be more beneficial for me to start off as an Android App Developer, slowly working my way into Android hacking? I have some ideas for potential apps (which I'll probably end up developing regardless, but at a later date), so if it would be more beneficial to just develop apps, I certainly have a basis for my ideas.
Any personal stories/recommendations would be excellent. Thanks in advance for any/all answers!
This article appeared today on the main page of XDA and I feel that it's a very important lesson for any/all new ROM devs.
Sage Advice from Cyanogen Still Valid Today
http://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/
Excerpt:
He had this advice to offer for those looking to make their own Android ROMs:
Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works….. Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that s**t on your resume. There is a *ton* of information out there but any kind of “step-by-step rom cooking guide” is going to be a complete fail- it’s too broad of a subject.As XDA has grown right along with the meteoric rise of Android, so has a desire of users to create their own ROMs, kernels, themes, and so on. Much of this work classifies as “original development,” but there’s been a growing trend to what many are calling “derivative development.” This category covers most of ROMs based on stock releases from the manufacturers, applying patches and scripts aimed at optimization, theming and/or removing stock applications, and using “kitchens” that run a stock release through a list of scripts and then repackage as a recovery-flashable update.zip. This is what Cyanogen was expressing frustration about—shortcuts being taken to achieve a product that differs only slightly from stock (derived) and pushed out instead of building from source and delving into the core of Android and making something truly original.
XDA-Developers exists first and foremost for developers. It’s at the core of who we are; it’s in our blood; and it’s in the air we breathe. There is a place for derivative works—they provide an entry to the scene which can help to introduce people to the wonders of Android. But let’s not stop there. Don’t be satisfied with just creating yet another derivative of someone else’s work. Instead, follow Cyanogen’s sage advice and learn about Android from the ground up, and create something truly original and innovative.
Click to expand...
Click to collapse
Guess I should continue with this hello world app... haha
Op just explained 99% of our roms lol
Repackage, rename, reskin and ask for donations. Rinse lather and repeat. Now your a dev!
Ha.
True software developers understand the wisdom of code reuse.
So ,in my opinion, if a fledgling developer takes a set of code and applies addons, makes a few setting changes then calls it a ROM and provides users benefit...then they are on the path.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
andrawer said:
Ha.
True software developers understand the wisdom of code reuse.
So ,in my opinion, if a fledgling developer takes a set of code and applies addons, makes a few setting changes then calls it a ROM and provides users benefit...then they are on the path.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Even if they fail to write a single line of original code?
I'm with cyanogen on this one...
saddly alll this is sementic
if the world of android was perfect then this would be true .by perfect i mean everything being open source ...
but if everything was open source we woudlnt have things like arc touchwizz blurr or sense , it is my opinion and shared by many others that android would be very boring if we only had aosp .
what does a coder brings to touchwiz sense or blurr device ?
the market is filled with cool apps and launcher .. 99% of them coders will make apps for android and wont bother with anything else
that brings me to my next point . building from source means on top of aosp , or in my terms vanilla android .. many devs love vanilla and its fine but what about those who dont ?
99% of the rom on xda are just that : either source compiled with apps added or stock deodex rom with a theme and apps added ..
here is the but , and before i say it i wanna say everyone is entitled to his opinion and im not bashing anyone ,
without guys like me who just hack the code and spend countless hours looking at what the code is actually doing and port the nice stuff from sense to TW or form CM to TW and RE (reverse engineer all these nice codes) 99% percent of the android devices would be boring because lets face it there is only one aosp device / year..
so from what Cyanogen is saying we should all buy a gnex and stop supporting those that make android close source,
but wait without them , many things woudlnt be in CM in the first place , what is cm without all these kangs? a glorified aosp ?
ok maybe im pushing but you get my drift...
how many true innovations by Cyanogen vs them Proprietary UI ?
fun fact the head (or ex ) of Cyanoen now works at samsung and help make touchwiz better (close source)
what about miui , they have so many innovations , and they dont share any of there code ..
so as I said there is no black or white here
thats what android is all about make your own thing play with it call it yours and make it a hobby , and maybe just maybe others will like it ...
I have seen way to many devs get god like status on xda for deodexing a rom and injecting voodoo in there kernel (for example)
i ve seen crazy talented themers have there work taken by others be ignored by the community and then vanished , and everyday we see a kik ass true developper on here and treat him like hes a nobody , because he doesnt have or because we havent heard of his rom .....
i completely understand where cm is coming form but my opinion differs slightly ..
@op kik ass thread (as I never read the front page)
Hard to build an i717 ROM from scratch with all of the proprietary bits, Samsung framework, etc, as most of that is proprietary as DAGr8 says. AOSP/AOKP works, but lacking some SPen functions and still relying heavily on a binary kernel as there are no kernel sources for ICS yet.
Hopefully the kernel situation changes, and we're back to the normal business of everything except the proprietary blobs that have to get copied from a stock ROM......
It'd be nice if all required code was released, but for some reason such things tend to be considered proprietary. Oh well.
Thanks OP. I also don't read the frontpage near often enough.
I like what Cyanogen is saying, and agree with his points from his developer point of view. I also agree with DAGr8 and his points. The fact is that Android gives us so many choices and has so many options for exploration. I think that's why so many of us have moved to the Android ecosystem. There is enough room for everyone. Android is the most prevalent mobile OS in the world for a reason. We can all have our opinions. We can all have what we want on our devices. And there are more and more people willing and able to jump in and try to build. Call them developers, or hackers, or derivators. It doesn't matter to me. They all add value to Android.
As the title says, is there no developer interested in porting PACman to this phon, not to be disrespectfull or anything cause i really apreciate the work and time you are givind to this phone, but I'm kinda angry when i see that even my dad's phone (HTC Desire HD) has android 4.2.2 PACman, and most other phones for that matter, and this phone didnt even have android 4,1,2 or 4.2.1 PACman, I meant i know there was a Paranoid build, but Paranoid Android is missing too many features i need (or want) from AOKP and CM (like lockscreen shortcuts), so my question is if isn't there any developer working or porting PACman to this phone, or at least adding Paranoid Settings to one of the allready existing AOKP or CM roms?
The devs get requests like this every day. I think it's a little unfair, devs are people too, they have lives, jobs and families just like us. Still they have brought us many roms. And they promise even more like ubuntu os. I think we should all be grateful for what we have. And if a dev does decide to port one of our favourite roms.... Bonus . If not, maybe it's time to do a little research on rom development, maybe try building a rom. If a dev see's "a normal" user putting alof of effort into a certain project, theres more chance they will step in and try to help
Sent from my HTC One X+ using Tapatalk 2
honestly Pacman is not worth doing.... it creates issues with other devs apps on the market, and i honestly don't fancy getting the rage from app devs
-Lloir
AndroHero said:
The devs get requests like this every day. I think it's a little unfair, devs are people too, they have lives, jobs and families just like us. Still they have brought us many roms. And they promise even more like ubuntu os. I think we should all be grateful for what we have. And if a dev does decide to port one of our favourite roms.... Bonus . If not, maybe it's time to do a little research on rom development, maybe try building a rom. If a dev see's "a normal" user putting alof of effort into a certain project, theres more chance they will step in and try to help
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
lol, first as I tryed to say it was not a request, more of a question if its comeing or not, and also i allready tryed to build my own rom, did a try with something easyer, and i was thinking i learned all i needed and downloaded the sources for cm9 and then tryed and it took me 5 days to manage to figure out how to get it build a flashable zip, cause it wouldnt build a zip file (not talking about this phone, and was long ago for my dads htc desire hd), and after that it ofc failed when i flashed it as in 1st i forgot to sign it and it didnt flash, then i did sign it and flashed, then flashed boot.img and ofc got a fail, wouldnt even get after the htc boot screen, so yah, if i could belive me i would try to build PACman, atm i only know the basic android things, like decompiling, compiling, smaling, backsmaling and signing apks, dont even remember how and what i did in my try to build cm9, and yah, im preety sure id fail again, plus at the time i tryed that i had a bit of time, now i have exams every week, so i totally understand the devs are bussy people and as i sayd or at least tryeing to say this was a question and not a request, i can live without it, even if i will silently hope it will happen one day
Lloir said:
honestly Pacman is not worth doing.... it creates issues with other devs apps on the market, and i honestly don't fancy getting the rage from app devs
-Lloir
Click to expand...
Click to collapse
I dont really understand what you are trying to say, you meant some apps are not working on PACman, cause thats what I understand, also sorry for takeing your time?
EDIT: NVM this question/request, i just found the xposed framework and the xposed app settings and those make exactly what i want, im so happy now, for those that want to know what im talking about: http://forum.xda-developers.com/showthread.php?t=1574401 (for the xposed framework) and http://www.villainrom.co.uk/forum/threads/xposed-app-settings.5486/ (for the app settings)
Hi XDA,
first of all, let's introduce myself. I'm a greenhorn at an indian outsourcing company working in the netherlands. my job is primarily 'being dutch' which happens to be a 24h a day job but something i can very easily multitask
so in a moment of 'what the coitus are they paying me for' i decided that i wanted to use a 'controlling-parent-or-boss-friendly' version of android. but it doesnt exists because android doesnt really allow such 'control' apps to work properly if they are 'only' an app (I tried a few to combat my infobesitas which is also the real reason why i'm doing this).
so why not. i'm a developer, i've got time. i know next-to-nothing about android, but i'm young and naive and terribly optimistic. lets get the source, modify it so it has baked in 'parental' controls, build it, use it, be happy with my lack of infobesitas, maybe sell it to my boss-and-other-evil-people?
so i tried to build AOSP using googles guidelines
i installed the latest ubuntu. i downloaded the packages (one didn't when i tried first but it worked when i downloaded it apart), created the working directory, got repo, repo-ed the source, ran the source configure.sh thing ran lunch and ran make.
my disk ran out of pizza space (i thought a 66gb partition would be enough, but not so much) so i enlarged my petition, throw the entire working directory away and repeated the process
only i get this error
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_instrumentation_entry: error: undefined reference to 'art_quick_instrumentation_exit_local'
googled this to no avail. put some post on my fb wall if anybody could teach me Android OS/ROM development for 150 euro (or more if i needed the person more than the ammount justifies). but i guess my 'friends' dont make roms in their free time (which is reasonable sinds im the 1337est h4ckz0r i know),
please help me with this.
so now i'm here. bounty is up for you too but for it ill expect a bit more than getting android to build. a teacher would teach me the ropes of rom dev using skype or something.
Hi,
I have flashed custom ROMs on my HTC Desire, my HTC One, Samsung Galaxy ACE, ... But all of them had plenty of resources...
I've got this tablet (it came free with a TV) and I can't find any info on it anywhere.
It's extremely sluggish and bloated (there's three system browsers - Android Browser, Chrome and Opera ) so I was thinking I'd find a vanilla ROM or a better ROM, but I can't find any info and I don't know how I would go about flashing since I can't find a ROM designed for this particular device, nor can I find a recovery for this specific device. Can I use resources from other devices (which? what to look for?)?
I'd even give building AOSP source code a try if that's neccesary since I'm a programmer and that would come with the benefit of actually modifying Android code to suit my needs like for instance deleting parts of code pertaining to GSM functionality since it's not a GSM tablet and every CPU tick counts
I am not, however, familiar with the exact hardware so stuff like drivers, kernels, etc... are uncharted territory for me and, even though it cost me less than bubble gum and the device itself is really not something that would be a shame if I bricked it, I still would like to not brick it since I already have the thing and it could be convinient every now and then, but not enough for me to actually pay for a better tablet
Note: I'm not actually looking to build AOSP from source, that's only a last resort since it's not a simple app, it's a whole lot of magic there Just saying that that's a last resort possibility.