Related
Hello fellow xda members. I need some input.....
What things would you mostly likely want in a rom. Needs ideas to base off of. May start on the development of a rom.
Please state apps, tweaks, commands, builds, kernels, themes; etc.
Give me your top TEN of you would include!!
Somewhat in this format:
1) Vaulty Free- Hides my pictures
2) Hot Reboot, reboot to bootloader/recovery- faster way to get into recovery
3) Firmware 3.30.651.3- updated firmware
4) Transparency theme- Clean looking and smooth.....
Just a random or very anal list like this, I would absolutely appreciate all the devs, flash-a-holics, and every testers opinion. Thanks to everyone who will help in this advancement to possibly providing another ROM to XDA.
(if i need to edit something i miss worded, let me know!)
After accumulating info towards a week or two, i will edit this post with a poll, and we will see how it goes from there.
AGAIN...... thanks
http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )
These are very good news
I already see my Hero running CM 7
:happy face:
Excellent News Lets see who get's their GingerBread ROM out first
Sweet, if the hero really will be supported!
Cooooooooooooooool man very nice go go go go gooooooooooooooogle
Tchuup-tchuup! Hotness train is leaving the stations
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...
Good news
Sent from my HTC Hero
C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress
I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.
Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?
That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project
Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero
I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...
Especially the repo syncing... that just takes ages ;
krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!
Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents
Hi All,
I am relatively new to the whole Android world and love my phone. There are a few complaints that I do have about the phone, but I'm sure that's just being nit picky.
I am currently running LiquidSmooth 1.3 (I believe 1.35 is only available for LTE and not GSM? Someone please feel free to correct me if I'm wrong.) I recently flashed the Trinity Kernel to see if I could get battery life on my phone.
Love the calibration that has been done to it! Here are a few things that I was hoping you could help me out with.
1.)Sometimes when I hop off of WiFi and go back to my mobile carrier, my reception bars grey out, but I can still text message and make calls. However, I cannot access the internet unless I restart / reboot the phone.
2.) What is the difference between a restart and a reboot?
3.) What is the difference between AOSP and AOKP? I read that one is more Google related, while one is a 'Kang Project'.
and finally,
3.) What is the difference in Governors??? Yes obviously experimentation is key, but I would like some advice to know all these terms to help me understand what some of you pros are posting.
Yes I feel foolish for asking these questions, but then I feel like it's essential to understand some of these terms more clearly. I'm making the transition between BB, iPhone. Any help is greatly appreciated!
liquidsmooth has cdma and gsm versions.
1. that may be ROM or kernel related problem. wifi is controlled by the kernel.
2. restart and reboot are same thing.
3. aokp is a rom name compiled off AOSP source.
3. search goes a long way, http://forum.xda-developers.com/showthread.php?t=843406
AOSP (Andriod Open Source Project) is the build of android maintained by google and that all andriod OS phones are based off of. Phone manufactures will use AOSP source code to build their particular rom for their particular phone.
AOKP (Andriod Open Kang Project) is the title of a rom for ICS compatible phones that is a play on words referencing AOSP. 'Kang' is slang for stolen software or source code. In the case of free software, it often means using software from others without giving the creator credit. However, despite the name, Team Kang often does give credit to other developers.
There is no difference between a restart in a reboot. reboot is the more specific term meaning the restart of an operating system. Restart is a general term for doing something over (dictionary definition).
Govenors manage the way the cpu switches between min and max frequency. Often under load, a govenor will scale up cpu cycles to get the task done quickly.
I already saw a lot of kernel developers here, each of them posting their own version.
I don't think that "download sources / fix them / apply patches" by every one of them is ok.
If all could focus on a single source-tree and fix / apply patches to that we would get to a stable/improved version a lot faster.
I can provide a linux machine for the developers interested by this project.
Hardware: 2 x Xeon X7550, 16GB RAM (can be extended to about 60GB), 300GB of storage (can be extended) - RAID6, FC dedicated storage.
Example:
$ time make ARCH=arm clean
[...]
real 0m2.479s
user 0m0.953s
sys 0m1.151s
$ time make -j32 ARCH=arm CROSS_COMPILE=arm-eabi-
[...]
real 1m4.720s
user 19m11.694s
sys 3m23.190s
Click to expand...
Click to collapse
Software:
Slackware 64bit 13.37, gcc 4.5.2, gcc-arm 4.6.1
OS can be changed if you have good enough arguments.
SSH access, no root.
If any developer is interested by an account, pm me with the desired username.
Have fun!
Ok, if no one is interested, I have to start this alone...
BETA
First release - ALiCE Kernel - with patches/tweaks from eternity/franco/bricked kernels and some of my own. Everything seems to work on my HOX.
- Sweep2wake included
- modules built in kernel, no need to flash anything else but boot.img
Attached:
zImage - for including into your own boot.img
boot.img - InsertCoin 5.3.0 boot.img with this kernel.
DELETED ATTACHMENTS - Kernel was virtually unusable.
You can use zImage injector ( http://forum.xda-developers.com/showthread.php?t=1647398 ) to update your own boot.img
I like the idea of this collaboration of kernels.
And I like how the modules are integrated into the kernel.
I'll be testing this out more tomorrow with a battery test for a work day
Keep up the good work
EDIT:
3G Does not work.
As in it shows 3G/H on the top, but no network connectivity.
WiFi does however work.
Great
I'm not a kernel dev, but this seems like a good idea.
Kernel devs working together to create a solid/stable base kernel.
If they want to add specifics they can always release one aside of this.
Also good to integrate modules into boot.img
Keep up the good work.
+1
Good idea, and go on
Good work.
Well I build kernel in 1 minute on i7 920 @4.2 ghz, no need for you machine ;-)
But common git would be nice.. I have zero time to maintain a kernel for HOX
Sent from my HTC One X
It will be nice if we can have a common github repository for the OneX sense kernel with all the patch applies by the devs.
AliceXES, do you have a git link of your repo ?
Because I currently compiling the franco's repo with some config tweek for my own need. And I would like to compiling yours just for testing.
Anyways, thanks for starting your project
Please send me your twitter account it's for helping you
The biggest problems ain't hosting or building times, just version-control. A common Git would be nice, although it seems most changes get picked by eachothers at github.
What about a GitHub organisation? You can have free ones where everyone is admin if you leave the source open. But then that requires a certain level of trust I suppose, heh.
The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.
AliceXES said:
The problem was with modules - for some strange reason, 3G doesn't work with them built-in the kernel.
Also my laptop crashed. The 2nd HP 4520s dead in my hands.
I will probably won't work on this anymore until it's repaired.
Still, if anyone needs access to the compile-server, the offer is still open.
Click to expand...
Click to collapse
Sad happenings. Hopefully it'll be fixed soon so you'll be back on track!
1: 3G problem indeed lies in the modules (linked to one of the binary baseband module)
2: getting collaborators won't be easy; many (apart from a select few) of today's "chefs" (dare not call them devs) prefer to act alone, get the credits, instead of working together, where the progress would've been much faster. This has been discussed too many a time on xda.
It is so much easier to rip someone's work & claim it as your own... Which is why many a dev resorted to "protecting" their roms (for example, from dumping).
Another reason why not many would like to join you, is that then it would come apparent that they don't have any real skills, since they won't be contributing any patches. ;]
Why compare ROMs with Kernels though? Maybe I'm unique at this, I don't know but, I never really cared about moving files around at ROM level or building AOSP ROMs. I prefer the kernel-space just a bit more
If people are afraid that their commits get stolen (which unintently happened just a few days ago, it seems) they should sign-off it properly.
Ányway I'm always interested in collaborating. Atm I'm just foring Franco's kernel and fixing a few compiling warnings.. I think what we really need is one main-maintainer which holds the master-branch, then the rest of our bunch just can push commits to him for reviewing. Who this lad is going to be, is also a tricky one.
I don't think I will have any success with this project
I started my own kernel thread (here: http://forum.xda-developers.com/showthread.php?t=1662781 ), sorry.
Anyway, the invitation is still open.
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
o-k said:
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Click to expand...
Click to collapse
Xda is just an outlet where people choose to post roms.
To check on the latest status of roms, you need to open the threads and read the OP. You also need to spend at least ten minutes reading each thread, That will tell you how stable each rom is and what kind of results people are having.
Sent from my SGH-T999 using xda premium
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
shrimants said:
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
Click to expand...
Click to collapse
Actually that would be a great idea. It would help out the entire community.
Right now the way things exist, you pretty much have to read through an entire rom thread to determine the benefits/bugs of any given rom.
You could, for example, start a list for any particular rom.. read the entire thread, then make your own thread detailing current known bugs and post it in the same forum. Then the OP of the rom thread could post your link in the first post making it easy for everyone to find.
That would serve two purposes - you would learn the information you're seeking and also become an instantly appreciated contributor to the site.
Sent from my SGH-T999 using xda premium
I'm surprised the rom developers dont already have a system in place, though. The scope of the projects are presumably gargantuan collaborative works. i kind of assumed that they must have some sort of a bug tracking thing that they use between them. That bug tracking thing is what i've been venturing to find. There are a ton of user-specific bugs that I have no problem digging through the forums and figuring out myself, but what i'd love to see with roms is a list of "this is what we know isnt working yet. dont talk to us about this. we are working on it." or at the very least, "when you flash this rom, if you would like to help, run this command and upload the output HERE so we can fix some bugs we know about".
I'm coming from a linux world and it is very disconcerting to me to flash a rom, encounter a bug/error, and not be able to look at any sort of an error message or do anything to fix the problem except reboot/wipe/reflash and hope for the best. thats a very windows-y mentality to the whole thing, and i feel like if we're running linux on the phones we should be able to get a bit more involved in fixing our own problems a bit better too.
I guess what i'm trying to say is, i'd like to help and i have no clue where to even begin. with archlinux theres a beginners guide but with these roms its more of a "watch this youtube video and follow this tutorial but god help you if anyone thinks you are complaining about what people are doing for you for FREE".
EDIT: I found CM10's issue tracker, but there isnt anything specific for the GS3 there. The flicker and picasa sync issues arent even mentioned. Obviously Paranoid Android and Kang will have the same bugs as CM10, but im assuming that they'll have their own bugs introduced after they add in their own features and such.
ok.
ingenious247 said:
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
Click to expand...
Click to collapse
thanks! will it be on the CM website or here?
o-k said:
thanks! will it be on the CM website or here?
Click to expand...
Click to collapse
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
i have a question
ingenious247 said:
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
Click to expand...
Click to collapse
i've downloaded the CWM pro and the TB pro. i was wondering what exact ROMS i can use. There is also the difficulty of understanding which rom is exactly which. Is there a way to view the Change log? i'm a super noob. i'm really sorry.
Changelogs won't do you much good.
I recommend flashing everything through CWM (make sure you have 6.0.1.2 Touch - in my signature if not). I wouldn't use ROM Manager at all. Having automated tools is great, but learning how to do it yourself is even better. Plus, if you break something, knowning what you are doing makes it easier to fix. Automated tools hurt more than they help.
As for roms, your options pretty much are as follows:
CyanogenMod: AOSP, the closest thing we have to the stock Google firmware.
AOKP: Pretty much CyanogenMod with some extra options. Nothing extraordinary about those extra options, just some nice things like center clock, swagger toggles, and unicorns.
MIUI: iPhone look for Android.
ParanoidAndroid: Scalable - for tablets (imo).
Then you have the neverending amount of customized stock (TouchWiz) roms.
They are all under constant development. If you want "stable", stay on your stock firmware. All of the roms listed above are stable enough to use as a daily driver. They all have threads in the two Dev forums. But if you don't know what to pick, use CyanogenMod.
I still think ROM Manager is a great tool, it's how I started years ago and I still managed to learn what I needed to over time flashing manually
Sent from my SGH-T999 using xda premium