Related
I'm new to Android but not new to Linux and wondering what is necessary to get these ROMs (and others) working on the CDMA Hero. What are the major differences, proprietary drivers? Kernel modules?
New Cyanogen ROM, just released
http://forum.xda-developers.com/showthread.php?t=567610
In other words, what's stopping us from running these ROM's right along with G1/Dream users?
I'm curious also... would love to try his roms...
Since Android 1.6 was supposed to add CDMA support I would think they should work as well as 2.0 unless the developers have taken the cdma support out of the code in their roms to shrink the size to fit on the G1's.
If I had a Hero I would be giving it a try most likely. I might try picking one up this week since Best Buy has them down to $99. I just wish it had a keyboard.
I'll try when I get home from work.
On a side note, even if this rom doesn't work, I should be able to boot into the recovery rom no matter what... riiiiiiight?
herzzreh said:
I'll try when I get home from work.
On a side note, even if this rom doesn't work, I should be able to boot into the recovery rom no matter what... riiiiiiight?
Click to expand...
Click to collapse
Correct! The recovery image isn't touched by normal ROMS typically.
I'm tempted. Can this be applied right over the MoDaCo ROM?
I have tried a couple things with these. I tried flashing it outright. Wouldnt get past the initial htc boot screen. So I replaced the kernel in the boot.img of Cyans rom with ours, that still didnt work. Then I tried replacing the entire boot.img and still no boot working. I think Donut uses the 2.6.29 kernel or whatever it is. Ours is .27 so I think we would need to recompile the .29 kernel and pray our drivers work with it. Please, someone else try it too and see if they can get it working. I would love you forever if you could. If not, we will just have to wait until HTC gets us Eclair.
Thanks
Thanks for trying this, chuckhriczko and others.
I'm mainly coming at this from the pure Linux point of view: shouldn't these ROM's run anywhere (barring proprietary bits)? Shouldn't we be able to "share and share alike" between platforms, Hero/Dream/G1/whatever? If there is a chip architecture difference, fine then we need a recompiled kernel. Obviously there is also the question of firmware, but that's a given on all phones.
Otherwise, shouldn't these ROM's be fairly universal? Or if they are not, I'd like to know what makes ROM building such a unique endeavor for each phone.
5tr4t4 said:
Thanks for trying this, chuckhriczko and others.
I'm mainly coming at this from the pure Linux point of view: shouldn't these ROM's run anywhere (barring proprietary bits)? Shouldn't we be able to "share and share alike" between platforms, Hero/Dream/G1/whatever? If there is a chip architecture difference, fine then we need a recompiled kernel. Obviously there is also the question of firmware, but that's a given on all phones.
Otherwise, shouldn't these ROM's be fairly universal? Or if they are not, I'd like to know what makes ROM building such a unique endeavor for each phone.
Click to expand...
Click to collapse
I believe it's mostly the proprietary drivers for some of the hardware as well as needing a kernel recompile...once HTC releases the CDMA kernel, I'm sure we'll see a lot more (that or some genius will reverse engineer it...either way!)
The other thing to consider is that most of these ROMs are based on something...they take what's existing and tweak the heck out of it (I'm willing to bet that the vast majority of ROMs can trace their roots back to an official vendor image at some point).
I'm actually trying to setup a build environment and poke around but I'm starting from ground zero on the mobile platform side of things so I wouldn't hold out for me (and finding a Java 1.5 runtime is surprisingly hard these days ).
I'm noticing that we're seeing more and more ROM's pop up (primarily gutted ROMs focussed on eeking more speed as opposed to MoDaCo who went for more features).
thecodemonk said:
I believe it's mostly the proprietary drivers for some of the hardware as well as needing a kernel recompile...once HTC releases the CDMA kernel, I'm sure we'll see a lot more (that or some genius will reverse engineer it...either way!)
The other thing to consider is that most of these ROMs are based on something...they take what's existing and tweak the heck out of it (I'm willing to bet that the vast majority of ROMs can trace their roots back to an official vendor image at some point).
I'm actually trying to setup a build environment and poke around but I'm starting from ground zero on the mobile platform side of things so I wouldn't hold out for me (and finding a Java 1.5 runtime is surprisingly hard these days ).
I'm noticing that we're seeing more and more ROM's pop up (primarily gutted ROMs focussed on eeking more speed as opposed to MoDaCo who went for more features).
Click to expand...
Click to collapse
What OS are you using? If your using a Debian based linux then you can get it from the Debian Lenny repositories. One word about this though, it killed my existing Java 1.6 so I had to reinstall it when I needed it. Otherwise that works.
And yeah, we are primarily doing gutted roms because that is all we know up to this point. It is very difficult to find help from those who know all about recompiling a kernel and things like that. Like I said, I couldnt get Cyanogen to even boot on my phone but obviously, it should at the very least do that. But only one dev on these forums ever helped me with my CDMA roms and that was Mlign from the Dream forums. Everyone else (understandably busy) ignored me. Im not saying anything bad about them but it's just harder for people to learn. Patience will give us what we desire though.
vendor tree for cyanogen heroc
im a noob and dont know how to build it but its here:
http://github.com/darchstar/vendor_cyanogen_heroc
Thread gravedigging much?
yes haha i want cyanogen on my hero lol
Since Android has graced our amazing HD2s, I have grown a strong interest in learning more about and experincing Linux.
Recent releases of Android for HD2, while good and getting better, seem to have gone backwards in some areas. I have spent countless hours experimenting, reading, etc. So now, I seek the assistance of the community; specifically that of the Android Chef's - for lack of a better term.
I am asking for a little guidance in how I may become self sufficient and build my own Android ROMs for our HD2s. I am hoping I can solve some of my own issues, and in turn provide my experiance and ROM - if it's up to snuff - back to the community here.
TL;DR
Would some kind soul point me to the location to Read, download applications, etc or provide some minor instruction on building my own Android ROM. I do not have an aversion to reading and learning on my own, I have just hit a road block as to the direction I should take.
Thank you in advance.
Hatefly.
You can use coffeeshop to make your own android build.
http://forum.xda-developers.com/showthread.php?t=738770
buzz killington said:
You can use coffeeshop to make your own android build.
http://forum.xda-developers.com/showthread.php?t=738770
Click to expand...
Click to collapse
Unfortunately, Coffeeshop isn't working at the moment. I'm experimenting with something else. I basically am trying to create an android rom the normal way in hopes i'll pick something up from that.
Got my Ubuntu / Virtualbox running and just finished installation. Now to get the Java.jde and .bin working.
Whole thing makes my head spin. Trying to figure out how to get our Kernal involved in the whole thing. I'm pretty sure i got the module thing "kinda" figured out.
Nothing still?
Makes me think these builds magically appeared out of nowhere
I like Linux, but it really depends on what your gonna use it for. I don't have it on my comp as a daily driver but its good if you like to tinker with.
As far as android, is there a kitchen for it? I had a kitchen for my HC Vouge and it was nice..just point and click. I just got my HD2 today and I love it.
Id really like to dive into dev for the Hd2 as far as themes and such go, but general dev,ill leave that for the pros.lol
sent from my backup
smurfgod said:
I like Linux, but it really depends on what your gonna use it for. I don't have it on my comp as a daily driver but its good if you like to tinker with.
As far as android, is there a kitchen for it? I had a kitchen for my HC Vouge and it was nice..just point and click. I just got my HD2 today and I love it.
Id really like to dive into dev for the Hd2 as far as themes and such go, but general dev,ill leave that for the pros.lol
sent from my backup
Click to expand...
Click to collapse
I'm not really sure how to theme with the android builds on the HD2 quite yet.
And yes, there are a couple kitchens for Android. They say they are not compatable with our HD2, but that has not stopped me from tinkering around with them and trying to learn as much as possible.
Trying to figure out how to actually build my own bootable Android ROM, problem is there is little to know info on how the few people who offer their ROMs actually performed this feat. if there is, I sure as hell have not found it.
I've spent 7+ hours reading and searching today alone. Not counting the last couple weeks.
As it looks like no one is really willing to offer me any help - must be an exclusive club or something - I'm prying I stumble upon a way to make it work.
/sigh... back to Ubuntu I go...
Hi friend, I do just want build my own rom for my hd2.
Unlike u, I even dont know how to start.
If u got any idea of cooking your own Rom, would you assist me at the time.
Dont take this Silly.
Today a new HTC ACE dump file has been released.
shree.cse said:
Hi friend, I do just want build my own rom for my hd2.
Unlike u, I even dont know how to start.
If u got any idea of cooking your own Rom, would you assist me at the time.
Dont take this Silly.
Today a new HTC ACE dump file has been released.
Click to expand...
Click to collapse
Sup Shree,
Once I figure it out, or someone gives me a little help with it, i'll let you know. So far I have created two custom ROMs, but they only work for native android devices as far as I know.
I'm confused with the whole file structure and how to integrate our custom kernels and modules into the ROM so we can actually use our hardware.
Oh, and I got coffeeshop to work. Had a problem where ./start.sh wouldn't run from terminal. I got it to run another way though. Now, I'm left with a System.ex2 file I'm not sure what to do with yet, lol.
Some links that may help you get started:
http://htc-linux.org/wiki/index.php?title=HaRET/Documentation
http://htc-linux.org/wiki/index.php?title=Rootfs/Userfriendly
http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide
NOTE: Not that I've gone to the trouble of building my own ROM... yet.
ok so we are all aware of all the various android builds out there for different phones. some with sense, some stock. all the chefs have their own basic formula for the perfect rom when they try to cook them for us. now most builds we apply to our phones are mod's of builds for other phones. After working with so many builds and liking certain features of each, but only available to each, i found myself asking the following question.
Companies like htc, etc. are assigned to build a certain phone with a certain android build with certain features activated/deactivated (ex. some builds have tethering, but tmobile said to cut tethering option out of g2. or some builds have a 2g/3g on off option where as others don't) this must mean that there is a general android build they start with that has all features and they just decide to keep/omit things they want or things carriers don't want. (or add some version of sense ui to it or touchwiz). My question is, is there a general ultimate android build that is available that has every feature there? i'm not a developer so i've never cooked a rom, but it would be awesome to have one build with everything and a simple way for users to decide which options they want or to omit. i know it sounds simple in theory and will never be that easy. but it would be awesome to have one general build with all options and can choose which ones i want to use or not to use vs. a developer selecting them for me.
this is a major problem with many winmo builds i've worked with compared to android builds, but its still something that bugs me when i try a rom and say damn i wish there was a 2g/3g on off in the network options vs having to dig for gsm/wcdma options. like i said in theory it sound easy and i'm sure its not, thats why i give all the chefs credit. but just throwing it out there in case something were to exist like that. thanks
I think I understand what you mean.
I've played with the Android SDK and the BASE 2.2 (what we know as Froyo) has all you mention (tethering etc), but looks kinda bland, this may be that I'm now so used to Sense and it's niceties that anything less than Sense to me just looks wrong.
If you want to see Android as Google intended for us all to use just download the SDK and start a 2.2 session with no modifications and you'll see the differences that carriers and the cooks here do, it's amazing work.
Also, almost all cooks here in XDA will try and give you access to everything the phone itself can do, that's part of the fun of running a rooted OS.
thanks for the tip about trying out the sdk Reno, i'm gonna check it out this weekend. Don't get me wrong, i love all the fun of flashing and its an addiction since 2007 on my HTC 8525/G1/HD2 lol. and i give mad props to all the chefs, god knows if i started messing with code, my phone would be a brick an hour later lol. Android chefs are really good and don't tweak much like winmo chefs do at times which i like. so many builds for winmo you'll find are scraped down to bare minimum because the chefs wanted a bare rom that gave u the "most space and fastest speed" which all went to hell once u install crap you want on it anyway, but half of the features and options have been deleted! thank God android chefs are good with keeping things there.
woohoo sdk fun friday night! will i become a chef? do chefs need to wear the silly hat?
I'll be perfectly blunt you'll need more than just the SDK to get a build made. I only downloaded it out of pure curiosity. You'll hopefully see in the attachments exactly what default Froyo looks like and realise even more what a godsend these guys here are.
I would honestly love to make my own build (more for my own fun and use than for general consumption) but I realise after many hours of reading and research that it's ridiculously hard work and these guys deserve every penny we can afford to donate for their toil.
Going back to the original point though: I think to create one overarching build that upon install you could pick: stock/sense/launcherpro or whatever other flavour there is available out there would actually be impossible. The look of the build is so deeply embedded in the build itself and requires so many different parts of the operating system itself to be changed you would need several copies of each file with the different variations for each look/style you'd end up with HUGE download sizes and it would be more difficult to keep up with when there is an update.
As things stand now, I know I could never drop my Sense builds, I love hastarins kernel tree, and I have my favourite small group of cooks that I follow, and that helps me limit what builds I download and test. Having a couple of small spare memory cards helps and only cost me £20 or so to give me that choice.
Reno i feel that you are correct. i couldn't resist and went to download the SDK after replying to your post. its still downloading a bunch of things and as i read the android developer page i'm enticed to hit the cancel button! I think i'll just go back to picturing the chefs as the magicians and let them entertain, instead of being the guy who tries to figure out all the tricks lol.
I have been learning new things on a almost daily basis since I got my first android phone (fascinate). After getting familiar with the flashing processes and testing out a few roms, I decided to try and get the satisfaction of ripping apart my non rooted original DI01 system to build a flashable rom.
I always had a few problems with some of the roms that I did try. These problems included market stalls, data connection being lost completely (no 3g icon), missing puzzle lock then when you install it back in it acts sluggish and boot lag.
Out of curiosity, is this something that would potentially be used by others?
If so would anyone care to school me on the rules for posting such files?
Haha, sorry but I got to say it. I am a complete newb to this and android phones in general. I have on of those attention issues and this seems to be fitting the bill nicely.
With that said I have no idea what my potential is and how far I will go with this, but I am a very quick learner if the subject interests me. I have tested this several times on my own device but that is only one phone. I would prefer an experienced user from this forum do some exclusive testing for me if at all possible. (I don't use gps or some of the extra features of this phone, they are included but not extensively tested)
It's based purely of stock as I personally prefer the stock appeal with an after market launcher. ie: puzzle lock, clock, music player. It will need to be personalized as it should be considered a stock base with some upgrades. At least for now. Plus it all depends on when froyo comes.
I have included a version.txt that contains more detail but still lacking complete information.
If this is of interest and perhaps an experienced user would like to take on testing, please let me know. I did not work with anyone so I just want to be certain.
I have no idea what to compare this to but idle is around 150mb and best quadrant was a 910 with stock kernel and not using any tweak apps. It actually skips past the verizon logo upon boot as well. Your mileage may vary...
Hey guys, just a quick question. Please please excuse me for I am definitely a noob, but I've done some research about rooting and what it offers yet I still don't know how to use it. It feels much like learning how to drive a stick... understanding in theory, but difficult in application until practice. My note 3 is rooted, but I still have no idea what and how much I can do from here. Not to mention, while I'm doing research and trying to educate myself, there are some names and terms I do not understand. Anyway, let me just write some of the questions I have in a list:
1) Cyanogenmod. Is it available for verizon note 3 running 4.3? I keep getting search results that there are while the cyanogenmod website itself doesn't offer it? I also got a Nexus 7 to try to expand my knowledge in this field, and it does have cyanogenmod installed. Now, to my understanding, it runs side by side with the Android OS while it basically strips the device's bloatware, giving you the pure, simple, raw experience of Android OS. If I were to install cyanogenmod to the note 3, how would it affect the camera functions and the s pen functions? The reason why I ask about the camera is because using my Nexus's camera and looking at some youtube videos of note 2's with cyanogenmod, it seems like it would actually be a downgrade from the note 3's stock camera. And as far as the S pen goes, I've realized that I would lose the action notes, s notes, and sketchbook for galaxy apps, wouldn't I? How could I go around that?
2) Flashing ROMS. What exactly does this do? All I can find is that it allows me to customize my phone, but I don't seem to understand to what extent.
3) Kernels. What are these?
Lol, so sorry for such basic questions. But I would really really appreciate your patience and information!
CyanogenMod is unofficially available for the Note 3. Not everything works. CyanogenMod is a ROM that changes the software on the phone. It's a more customized version of Android, and very close to "stock". If you use CyanogenMod however, you will lose your S-Pen and it's features, along with all of the other TouchWiz features of the phone (gestures, split screen, etc.). The S-pen will act as a basic mouse pointer. CyanogenMod is not pure AOSP, it's quite far from it. It's similar, but very different from a pure Google experience. It's really a beast of it's own in my opinion, and is now a stand alone company that will seek to profit off of the ROM (likely by coming standard on some devices). That's not to say it isn't good, I run it on most of my other devices but on the Note 3, without the S-Pen it's just a big phone.
ROM's are customized versions of Android typically created by a developer or group of developers. The features of each ROM will change. A 4.3 TouchWiz rom might remove all of the carrier bloat (applications not likely used, but run in the background and offer little no actual use to anyone). They'll also provide enhancements and tweaks that make life a little easier like a quick-access flashlight tied to your volume up button, or the ability to remove certain icons from the notification panel, a batter percentage indicator in the notification panel, removing the exchange security permissions, or just general speed improvements over the factory settings. There are many advantages to a ROM and once you use them you'll likely never go back to stock. The ROM features are typically listed in the ROM's topic.
There are many ROM's out there for many different devices, so make sure you only install one that is made for your phone. You'll also hear about AOSP ROM's, these are stock or close-to-stock versions of Android, typically found on Nexus devices. The way Google intended Android to be used.
Android uses a Linux Kernal. It's a customized version of Linux. It's the base operating system behind Android. Similar to ROM's, different kernals can offer different levels of customization, however they won't be as prevalent as a ROM since they deal more with the core of the operating system. The Kernal will manage the drivers for all the different components of the phone, like your radios (how you receive a phone signal), your sensors, camera, CPU, etc. Be especially careful when changing Kernals, it can drastically affect your phone, and possibly permanently.
I'll put in the caveat that this is my understanding, and may not be 100% accurate. People are welcome to correct my mistakes and misunderstandings I may have =)
I hope you find it helpful!
Thank you for your response and information!
Okay, so I guess Cyanogenmod for the Note 3 is not an option for me since I enjoy using my S pen (I mean, why else would I have gotten the phone in the first place haha)
Could you direct me to some useful ROMs or recommend me some? The thing is, I had the Motorola Droid as my first smartphone and never really got into rooting or anything, and when I got the iPhone 4s, that's when I started learning about jailbreaking and got pretty good at it too. Now that I'm back to Android and learning about root, I've realized just how.. simple and basic jailbreaking is compared to rooting. So, would these ROMs be similar to tweaks you can get from the Cydia store in, let's say, behavior of the phone?
I don't think I would want to mess with kernels for a long while either, not until I get more acquainted with rooting in general.
ch0i said:
Thank you for your response and information!
Okay, so I guess Cyanogenmod for the Note 3 is not an option for me since I enjoy using my S pen (I mean, why else would I have gotten the phone in the first place haha)
Could you direct me to some useful ROMs or recommend me some? The thing is, I had the Motorola Droid as my first smartphone and never really got into rooting or anything, and when I got the iPhone 4s, that's when I started learning about jailbreaking and got pretty good at it too. Now that I'm back to Android and learning about root, I've realized just how.. simple and basic jailbreaking is compared to rooting. So, would these ROMs be similar to tweaks you can get from the Cydia store in, let's say, behavior of the phone?
I don't think I would want to mess with kernels for a long while either, not until I get more acquainted with rooting in general.
Click to expand...
Click to collapse
Well first thing you need is safestrap so you can actually flash a ROM link here
This allows you to create limited size slots to flash a ROM to without effecting the stock ROM. There is a way around the size limitation of the slots, but I wouldn't worry about that yet. Just get a feel for it first before you risk bricking.
As for a ROM, head on over to the android development section and pick one. They all have great descriptions of what they have and what they don't. Personally I run hyperdrive and it makes a great daily driver. Still has enough of the original Samsung stuff to look like a Note 3 but allows you to tweak it much further. There are plenty others, and that's the beauty of safestrap, flash to your heart a content until you find one you like.
Kernals aren't something to worry about yet because the boot loader is still locked, limiting our ability to flash a kernal or a custom recovery at that. Unless something has changed that is... Has it? Did it get unlocked while I was asleep.
I you ever get stuck, search then ask. You might also want to read about ODIN here. since you're already rooted some of this doesn't pertain to you, but is still a good read as ODIN will help you recover from some problems.
Hope that helped.
blksprk said:
Well first thing you need is safestrap so you can actually flash a ROM link here
This allows you to create limited size slots to flash a ROM to without effecting the stock ROM. There is a way around the size limitation of the slots, but I wouldn't worry about that yet. Just get a feel for it first before you risk bricking.
As for a ROM, head on over to the android development section and pick one. They all have great descriptions of what they have and what they don't. Personally I run hyperdrive and it makes a great daily driver. Still has enough of the original Samsung stuff to look like a Note 3 but allows you to tweak it much further. There are plenty others, and that's the beauty of safestrap, flash to your heart a content until you find one you like.
Kernals aren't something to worry about yet because the boot loader is still locked, limiting our ability to flash a kernal or a custom recovery at that. Unless something has changed that is... Has it? Did it get unlocked while I was asleep.
I you ever get stuck, search then ask. You might also want to read about ODIN here. since you're already rooted some of this doesn't pertain to you, but is still a good read as ODIN will help you recover from some problems.
Hope that helped.
Click to expand...
Click to collapse
It did! Thank you very much!
ch0i said:
It did! Thank you very much!
Click to expand...
Click to collapse
The only option with Safestrap and therefore on newer Verizon Note 3's is a ROM based on stock, so Cyanogenmod isn't an option at all.
I would consider Hyperdrive. Enhanced app windowing options, Xposed framework to get rid of earphone hearing damage warning and never ending reminder about how to clear default apps and tons of little customizations. Getting rid of boot sound is reason enough for me.
Other things on your checklist whether you get a custom ROM or not is Adaware, which you can download on xda to block ads. Need Titanium Backup to back up apps with data, something you can't do without root and very useful when switching ROMs or phones. Lots of other useful tools like Root Explorer on Google Play. If you stick with your stock ROM, do the mod to allow free tethering for Wi-Fi.
Since you like your S Pen, you need Pen Window Manager, available on Play to choose for yourself which apps can run in a pen window. That was one of the big reasons I wanted to root this phone.
By the way, once you find a ROM you like, it's best to nandroid back it up, backup the stock ROM for safety, then restore your custom ROM to the Safestrap stock slot. The ROM 1-4 slots have limited storage so not great long term solution if you have a lot of apps, etc.
Sent from my SM-N900V using Tapatalk