Database Info

[Q] Porting the Honeycomb sdk - am i on the right track?

I understand that the sdk is nowhere near full featured, but now there are system dumps of the xoom, maybe helpful, right?
Well, i have never ported nor built a ROM before (done some theming and have no problem learning code). I came across these 2 port how-tos:
http://forum.xda-developers.com/showpost.php?p=11546129&postcount=76
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Is that all i really need to get HC to boot? The instructions seem extensive but not impossible or difficult.
Has anyone attempted this or gotten HC to boot on the g-tablet? I'm willing to take a crack at it if a dev could tell me whether i'm on the right track with the tutorials or do i need more knowledge.
When it comes to ROM building/porting, i gotta start somewhere. I've been around these forums for years and its about time I attempt to return the favor (hopefully without bricking my device lol)
Thanks in advance.
If this post needs to be moved, i'm sorry mods, but i figured this is strictly a development question.

Feel free to attempt it. There are people working on it and have come to the conclusion that source is needed plus a couple files from nvidia.
IMO porting the sdk is a complete waste of time tho. You would be much better starting off with a rom that will compile like froyo rather than starting with something that doesnt work yet

thebadfrog said:
Feel free to attempt it. There are people working on it and have come to the conclusion that source is needed plus a couple files from nvidia.
IMO porting the sdk is a complete waste of time tho. You would be much better starting off with a rom that will compile like froyo rather than starting with something that doesnt work yet
Click to expand...
Click to collapse
thanks for the insight. You're right, maybe froyo would be a good place to start so i could get used to the process on something that will compile. I'll probably give it shot in the next couple of days.

jump on the irc channel. freenode channel #tegratab. Lots of help and a willingness to help those that want to learn. I've compiled cm7 several times myself. Not my cup of tea but it was interesting.

Making Roms....

This maybe premature but I figured I would throw it out there; is there any devs who could tell me about the skill level or difficulty level of making new roms or tweaking existing roms? I'm learning about java programming and using j creator and eclipse. I'm still new but I'm a fast learner. I want to help out the charge community by keeping an active dev. I'm still a time away from that but want more insight..... Please no sarcastic remarks.... Thanks.
Sent from my SCH-I510 using XDA App

I'm attempting to start teaching myself this as well. The advice I've gotten is to start ofs theming. That way you can break open the apks and see what's inside, get a feel for how to change things and reassemble packages without doing any major work, and then expand from there. I'm in the process of changing jobs and cities, but I'm going to start playing around with things after I get settled.

a lot depends on what you want to do
developing for oem skin (touchwiz roms in this case) is a lot different than aosp
aosp requires a lot of java knowledge, and depending on the phone can be somewhat easy (nexus phones source will boot without changes) to nearly impossible (this phone)
touchwiz roms require some basic tools (7zip, smali/backsmali, apktool, rom kitchens or terminal knowledge) as well as some smali knowledge and countless hours of just figuring stuff out
many of us got our start as themers, from which you (over time) gain knowledge on rom layouts, where things are located, xml/smali editing, making update.zips and updater-scripts, and the like
you dont *need* to necessarily use linux to work on tw roms, but it certainly helps imo...although most of the tools out there work in windows too
my suggestion?: download a stock rom and download a heavily modded one of the same build (infiniti/gummycharged) and compare them with kdiff and decompile the apks to get an idea of what was changed
its a good starting point

Sweet, thanks for the advice. I am learning java pretty quick but realistically it would probably be a year before I'm proficient. I also just added computer programming as a minor. I would like another phone, the nexus obviously, but I need to chill on buying phones. I love aosp- if that was possible that would be great, but getting started anywhere is good. Thanks for your help fellas.... I'll keep you all posted here on my progress...
I know that the java language will help-but comparing will help me get acquainted with android. So far I've learned everything from forums so this is a new direction...
Sent from my SCH-I510 using XDA App

For those following who may want this information. I had a response from imnuts in RootzWiki where I posted this same question. Here's what he said as well. He complemented the answers already given- I also followed up on a list of software to help get started.
http://rootzwiki.com/topic/11184-new-roms/

Thx for starting up this thread. I'm actually lookin into rom dev as well and this thread has some great starting blocks in it +1 for u dude

Getting Started with ROM Development

I've been around for a while, and flashing ROMs all the time, but I was wondering what it really takes in order to really get going with ROM development. I would really like to put together my own PAC/Rootbox/ReVolt-style ROM, but I don't really know where to get started. I have done a very small amount of Android app development, but I do have experience with Java. Does anyone have any pointers for where to get started, best practices, etc...?
Also included in this question should be this: I have a little experience with Github, but haven't really ever used it do pull requests, forking, and such, and I've only ever really used it for hosting my own projects. Is there a good guide on how to understand that type of stuff, as well as where to do builds, nightlies, and hosting? From what I've gathered from various ROM devs so far is that if you host on Goo.im, that will let you take advantage of GooManager for OTA updates, right?

drinfernoo said:
I've been around for a while, and flashing ROMs all the time, but I was wondering what it really takes in order to really get going with ROM development. I would really like to put together my own PAC/Rootbox/ReVolt-style ROM, but I don't really know where to get started. I have done a very small amount of Android app development, but I do have experience with Java. Does anyone have any pointers for where to get started, best practices, etc...?
Also included in this question should be this: I have a little experience with Github, but haven't really ever used it do pull requests, forking, and such, and I've only ever really used it for hosting my own projects. Is there a good guide on how to understand that type of stuff, as well as where to do builds, nightlies, and hosting? From what I've gathered from various ROM devs so far is that if you host on Goo.im, that will let you take advantage of GooManager for OTA updates, right?
Click to expand...
Click to collapse
As far as the github, you can fork the CM link directly for The GNote 2 as it's supported by them. If it were not you would have to fork a dev that has ported it over. Once you setup your box, ( there are numerous "how to compile custom roms" ) you can compile your rom. Easiest would be to ask somebody that has a "clean" (no customizations) CM build that you can use, and make your own mods. After that. It all counts on how good you are with coding and making your own mods. Hope this gets you started. Youtube and google are good places to start. I always refer Android Dev section for my repos and how-to's.

It takes, above all else, patience. start here
http://forum.xda-developers.com/showthread.php?t=1946481

Chasmodo dev gives me a link where you can see tons of guide and tutorials… good for noobs but also for advanced devs… I would like to compile an aosp for n5100 that is unsupported by cyano team at the moment… so I think that is too hard
http://forum.xda-developers.com/showthread.php?p=41491498
Inviato dal mio GT-N5100 con Tapatalk 2

[Q] Question about maintaining ROMs

I think we all realize that making these ROMs is just a hobby for most, but doesn't anyone want to make a fully stable one? From what I've seen since this phone rolled out, is that someone will make a ROM, update it a few times, and then it's just dust in the wind. Also the only 100% stable ROM is the stock ICS ROM; no? My point is not to criticize anyone for their hard work,but to rather ask the question; what is the point of tinkering with a ROM and never getting it to 100% before moving onto the next one? I know everyone is very appreciative of what goes on in this community, me included. I was just wondering if someone could shed some light on this question for me.
Also, just my two cents; It would be nice for someone to maintain a custom ICS ROM just so there can be an up to date ROM with nice features and wifi calling. =)

Instead of giving your 2 cents, do it yourself. What's your definition of stable. I've been on PAC since it's come out and have zero complaints. Your want stable? Don't root, don't flash, don't modify. There, perfectly stable. Saying "my point is not to criticize" doesn't absolve you from being completely ungrateful for the hard work it takes to do this. Do it yourself. XDA is a development forum, not completely 100 percent stable forum. Don't like it? Go get an iPhone.
Sent from a Blazing PACMAN devouring ALL...

Most of the roms are stable. You can find things to ***** about on any rom, including stock.
When it comes to something not getting fixed it can come down to the dev not enough time, or its not worth the effort, or they moved on to a different device. I mean is it really worth fixing a bug that 2 people are experiencing if it is going to take a few weeks away from your family, I don't think so. And that is about how solid 95% of the roms are. Give some props.
There are probably 25 ROMs over 4 revisions of android... Its our job as USERS to spend the time and effort to find one we like, and that suits us. If a ROM has a bug that is detrimental to the use you need, look at another one. So try not to criticize devs when you haven't done your due diligence as a user.

csssc said:
I think we all realize that making these ROMs is just a hobby for most, but doesn't anyone want to make a fully stable one? From what I've seen since this phone rolled out, is that someone will make a ROM, update it a few times, and then it's just dust in the wind. Also the only 100% stable ROM is the stock ICS ROM; no? My point is not to criticize anyone for their hard work,but to rather ask the question; what is the point of tinkering with a ROM and never getting it to 100% before moving onto the next one? I know everyone is very appreciative of what goes on in this community, me included. I was just wondering if someone could shed some light on this question for me.
Also, just my two cents; It would be nice for someone to maintain a custom ICS ROM just so there can be an up to date ROM with nice features and wifi calling. =)
Click to expand...
Click to collapse
Fully stable is damn near impossible, man. There is sooo much involved in coding these ROMs it's literally staggering. These devs aren't software developers (not most of them) but just regular guys, working regular jobs like you and me. If you want completely stable best to stay stock rooted (so you can drop all that bloatware bull****) Most of these developers have day jobs that don't involve android and do this in their spare time, for us. To be frank, man, you did come across EXTREMELY critical, and the folks around here don't take kindly to that (just breath @njstein) What's the saying? Beggars can't be choosers? My point, if you want to run 4.3 your're gonna have to take the good with the bad, just suck it up and deal with the FEW bugs. I've been on 4.3 for a couple months now with no serious issues.. Just a few bugs. And for future reference, keep this kind of thing to yourself

I had no intention a dragging this into what it has become. Obviously no one understands the point I was making or the question I was asking. I'm not going to further this conversation anymore.

I don't understand why you are making a statement in general to all ROMs. The reason why the older ROMs are unsupported is because there is no reason to waste time updating them as the guy above explained. That's why you will never see halo on ICS. Now, 4.3 roms are supported at the moment. If you like an iPhone then congratulations.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

anactoraaron said:
Because if every dev stayed on ICS we'd have loads of folks asking if 'such and such device' will ever get a jb or kk rom. Seriously re-read the posts about how difficult it is to code. Your post is akin to asking someone to rebuild a car engine multiple times because every 5000 miles the thing misfires. Why did it misfire? Was it a plug/wire? Something in the valves/cylinder? Electrical? Fuel delivery? How many hours do you expect someone to waste tracking and rebuilding (sometimes rebuilding everything) for every bug in a rom- even the bugs properly reported with a log?
And I've yet to see any device from Sammy to HTC to lg or any device at all that's 100% stable - even on stock. And that's from companies that have software development teams.
And don't listen to those folks about getting an iPhone- that platform isn't 100% stable or perfect either. What you are looking for is a dumbphone.
Sent from my BN NookHD+ using xda app-developers app
Click to expand...
Click to collapse
Yup.... Why keep rebuilding that 4 banger (ICS) when with the same amount of work you can drop in a V6 (jb 4.1). And the same when a V8 (jb 4.3) is available to drop in. Then the 4 and the 6 get scrapped for some extra beer money, and you tinker with the latest and greatest again.

Deleted.

Haven't been on in awhile and I see an argument going on? C'mon guys. Okay, about maintaining ROMs, when maintaining there are nightly's based off the latest changes. The more changes lead to more better features (and maybe some bugs). Not all are stable. In fact, there is no such thing as a "fully stable" ROM. Even stock from Samsung isn't stable. And please, don't argue on here. Take it to PM or some other way to communicate. Not on here on a public thread. May I include, that I have an iPhone . Don't hate because the OS is not controllable. Its a nice OS and lots of great apps. But Android is specifacally better in my opinion. Don't hate me for that lol. Also, if you'd like to learn on how to dirty port a ROM just google it and let's see if you can make a "stable" ROM. Move on everyone. lol
Edit: I don't want the mods to come on here and waste their time. Keep it clean next time

xWolf13 said:
Haven't been on in awhile and I see an argument going on? C'mon guys. Okay, about maintaining ROMs, when maintaining there are nightly's based off the latest changes. The more changes lead to more better features (and maybe some bugs). Not all are stable. In fact, there is no such thing as a "fully stable" ROM. Even stock from Samsung isn't stable. And please, don't argue on here. Take it to PM or some other way to communicate. Not on here on a public thread. May I include, that I have an iPhone . Don't hate because the OS is not controllable. Its a nice OS and lots of great apps. But Android is specifacally better in my opinion. Don't hate me for that lol. Also, if you'd like to learn on how to dirty port a ROM just google it and let's see if you can make a "stable" ROM. Move on everyone. lol
Edit: I don't want the mods to come on here and waste their time. Keep it clean next time
Click to expand...
Click to collapse
You're right. It's important to remember that no one here is under ANY obligation to share anything - roms, root, recoveries, mods, etc - with anyone. So lets just appreciate what we have. :thumbup:
Let's also get a mod to close this thread, nothing more good can come of it.

This trollfest has gone on long enough. The sheer amount of disrespect flying around astounds me. Read the rules folks.
Thread closed.

KitKat for HTC Thunderbolt

With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)

frap129 said:
With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)
Click to expand...
Click to collapse
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.

chongbos said:
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.
Click to expand...
Click to collapse
I assume by transplant you mean just try to flash a rom for another device with simmilar specs? (Same MSM8655 CPU, Same amount of ram, etc)

Kitkat would be awesome!
I'll test whatever you throw up here.
That's about all I'm good for. Sorry.

you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:

Ive contacted a few members who have experience with either porting or the thunderbolt, none of wich have responded as of yet.

her you can try :
http://forum.xda-developers.com/member.php?u=4310221
http://forum.xda-developers.com/member.php?u=4471805
http://forum.xda-developers.com/member.php?u=4395946
hope they reply...

guinzo said:
you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:
Click to expand...
Click to collapse
Santod was the reason why I loved my thunderbolt. I still have it but rarely use it. Sadly the screen is cracked but it was always a reliable phone.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk

TtWEAK said:
I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There definitely are, but the difficulty of getting data on AOSP for this device, coupled with the age, current ownership/userbase, and developer interest translates to probably not. It's okay though, it was a great ride while it lasted.