Hi there.
Could the mods pleace establish what defines a ROM or development ?
At the moment we see a lot of claimed "new" roms, when in fact they are only stripped s/e roms, loaded with a bunch of other apk's instead...
Nothing special at all, and no development...
These self claimed "developed ROMS" just clouds up the dev. section with nothing new at all...
In fact only the thread from J & Z, should be there as they actually develop something...
All the other "roms" should eigther be in a "modded Rom" section, or in the theme and app section, as they dont offer anything other than a "theme"...
Most of them is fine looking themes for shure !, but nothing more...
Sent from my Commodore VIC20...
With the bootloader locked up still, only partial custom roms are being released because we cannot flash the custom kernel yet. (You can crank up the screen to 16M i.e. with the kernel.) - So these so called custom roms are only partial custom. We still need to wait till the bootloader get cracked. (Witch i think is still a long road ahead for us)
Still J and Z, are able to actually do some development...;-)
The other are not with any development...
Perhaps the people making the theme-roms then should put a [Modded stock] sign in the header of the threads of those "roms" so every one know for shure, what is what...
Sent from my X10i using XDA App
pshdo said:
Still J and Z, are able to actually do some development...;-)
The other are not with any development...
Perhaps the people making the theme-roms then should put a [Modded stock] sign in the header of the threads of those "roms" so every one know for shure, what is what...
Sent from my X10i using XDA App
Click to expand...
Click to collapse
not a bad idea actually. My thoughts and interpretations.....
[ROM] denotes a flashable ROM - stock or custom
This heading is for any type of rom, as it differentiates it from threads on [HACKS], [MODS] or other.....so therefore in our SE context.....
[CUSTOM ROM] denotes a custom ROM
This heading is not for use with a custom ROM. If the ROM is based on the SE ROM, no matter how customised it is....it is still a SE ROM at heart. If the ROM is based on something else, or brewed completely, use this heading
[SE ROM] denotes a ROM that is based on the SE 2.1 ROM
This heading is to be used for ROMS that are based on the SE 2.1 Official ROM. If you started with this as a base, then use this heading.
The formatting could also be as follows.....
[ROM - CUSTOM] AOSP 2.3 "MrTim123" - Rev 0.0.2 [xRecovery]
or
[ROM - SE] 2.3 "MrTim123" - Rev 0.0.2 [xRecovery]
Thoughts? Does it make it needlessly complicated?
pshdo said:
Perhaps the people making the theme-roms then should put a [Modded stock] sign in the header of the threads of those "roms" so every one know for shure, what is what...
Click to expand...
Click to collapse
To be fair, no one who has uploaded a modded ROM has classed it as "custom", and most, I think, have clearly stated what it is in their descriptions.
Developer
I fear that the x10 will end up like the new psp chipsets... unhackable..
pshdo said:
Hi there.
Could the mods pleace establish what defines a ROM or development ?
At the moment we see a lot of claimed "new" roms, when in fact they are only stripped s/e roms, loaded with a bunch of other apk's instead...
Nothing special at all, and no development...
These self claimed "developed ROMS" just clouds up the dev. section with nothing new at all...
In fact only the thread from J & Z, should be there as they actually develop something...
All the other "roms" should eigther be in a "modded Rom" section, or in the theme and app section, as they dont offer anything other than a "theme"...
Most of them is fine looking themes for shure !, but nothing more...
Sent from my Commodore VIC20...
Click to expand...
Click to collapse
One could say it's a Modded Rom or a Back-Up
Related
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
hi guys i was looking around and saw a galnetmiui ICS build
it states " to mark our success at merging ICS with MIUI frameworks we have officially taking it on board to support all 17 official MIUI China Roms. We will be supporting all 17 roms from now on, and better still our stable builds will now include the ICS framework as standard."
after flashing is says i have 4.0.1
so does that mean i "have" ICS ?
so far its the smoothest thing that has ever been in my phone better that cm7 or official miui builds
thanks
good question, i was also a bit confused by this statement
i also want to know this
It's how the frames make it all work, bro.
LMGTFY:
frame·work/ˈfrāmˌwərk/
Noun:
An essential supporting structure of a building, vehicle, or object.
A basic structure underlying a system, concept, or text: "the theoretical framework of political sociology".3
It's like the house's foundations. It's what everything else is based upon.
So do you have ICS? In terms of content, no, you don't. You don't have ICS launcher, apps, etc. What you have is the ICS framework, the base.
and what's all included in this framework?
kernel, baseband, modem, ...
do i have the new functions of ICS?
thanks for answers
thanks 10 char
There's a link to Galnet website+forums in my signature. You might want to ask there, since XDA doesn't want to let Galnet make a ROM thread.
In this forum i can see two threads:
"Galaxy S II Original Android Development"
and
"Galaxy S II Android Development"
What's the difference?
Thanks!
Brgds,
M.
Bad move. Anyway, read this http://forum.xda-developers.com/showthread.php?t=1219612
Original Android = Stock Roms
Android Development = Custom Roms
custm_made said:
Original Android = Stock Roms
Android Development = Custom Roms
Click to expand...
Click to collapse
WRONG WRONG WRONG .
jje
seriously I always wonder about the right answer even I read the original post of the difference, I am not very good in english maybe thats why I didn't fully undertand the main difference, but I guess the below:
Original android: after sometime the ROM is being stable so it goes to that forum
Android: still under development and not proved to be usable as stable version
NOTE: I am not sure at all, and please if any one knows the right answer to confirm it ... we are not all good english speakers
In all honesty, why does it matter ? It's not important. However...Original Android development is exactly that, a forum for stuff that is original. Whereas Android development has pretty much 'everything else' development-wise & stuff that is often based on/contains parts of someone else's work.
I still don't get why knowing this is so important to you ? Besides, if you'd read & followed the link you were given (which lead to other links and an eventual answer), you would have got the answer I just gave you.
ahm_salloum said:
seriously I always wonder about the right answer even I read the original post of the difference, I am not very good in english maybe thats why I didn't fully undertand the main difference, but I guess the below:
Original android: after sometime the ROM is being stable so it goes to that forum
Android: still under development and not proved to be usable as stable version
NOTE: I am not sure at all, and please if any one knows the right answer to confirm it ... we are not all good english speakers
Click to expand...
Click to collapse
Enter on both sections an see it yourself.
Sent from my GT-I9100 using Tapatalk
parazitul80 said:
Enter on both sections an see it yourself.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I must be stupid but...
If we look at Original ROM index we've got Sammy, AOKP & AOSP based ROMs for both ICS & GB.
If we then take a look at Android ROM index we have Sammy, AOKP, AOSP & MIUI ROMs, also for ICS & GB.. and a new one for JB
Plus custom kernels in both sections aswell.
If by original we're talking about pure original as in not a modified/port of an already existing ROM then shouldn't it only be official Cyanogen, Kang, MIUI ROMS and maybe official Sammy releases in Original section?
Always Original Android best google experience
This is a call out to all existing and future developers of Xperia MDPI Devices.
For about a month now there is an app called Update Me Smartphone, which basically gives OTA update functionality for our Custom Roms.
From 01/05/2012 the developer of this app has given it a very interesting feature. You can view all Roms compatible with the Update Me Smartphone application. Even though you get a list a bunch of irrelevant devices, I suppose if we all "help" him with our suggestions he can make an application that will be on par with the Rom Manager app for devices that are fully supported by CWM.
To make this as simple as possible....
User "A" wants to download a new Rom for his Xperia MDPI Device. He has already downloaded and flashed a custom kernel (whether this is a Stock Kernel, or a CM kernel), then proceeds to download the app, install it and browse any compatible Rom's with his device... From then on his device will stay updated, through the Update Me application providing OTA updates of the Rom he has installed. If he wished to download another rom (compatible with the kernel he has - there are 3 Different Kernels AFAIK: GB CM, ICS CM, GB-ICS Stock Sony Kernel) he will just proceed to download the latest version of the rom he has selected straight to his device. No need to download to your computer, then connect the device, then copy it, then flash it. If you have the compatible kernel already installed, then its easy as pie.
Please let me know of your thoughts on this...
Edit: Link to the application's thread http://forum.xda-developers.com/showthread.php?t=1590170
Edit 2: Apart from Rom's we can also implement various mods, tweaks, fixes, etc for our devices. Even though that would be extremely hard, due to the fact that all these files need to be stored in a direct download location like Dropbox, its is a viable option.
OMG I love the idea, that would be awesome!!
It's very interesting, thanks a lot for the info I will try it!
Some modification: In GB we have 3 different kernel (Stock Based, CM Based, MIUI Based [not released yet]). In ICS we don't have Stock based to Xperia MDPI, because Sony don't released yet the stock for us. So we have CM9 based, AOSP based (it's work with CM9 ROMs btw), and ported Stock based.
Some another notice: I saw a lot of thread (not only in this forum), but sooo many people trying to make ROMs. It's not a problem, but some guy don't know some full minimum things... So who will help this guys to add this app to their ROMs?
Are you using a different Kernel for the Sony ICS rom port? I mean the Ramdisk is the same size and you're using the same zImage from a stock GB rom correct?
Well nobody is forced to do this. All we have to do is provide the app developer a link with the update_me_check.xml so that he will sort of add a link for that in the application.
By the way, i now got my goo.im account, and this have own OTA app. I will try it, and I will report.
But I know, this is not only OTA app... Hmm... I need to think in it
So the only developer checking the thread is Expeacer?
Ok...
dumraden said:
So the only developer checking the thread is Expeacer?
Ok...
Click to expand...
Click to collapse
What makes you think like this?
Well, it's been a couple of days since I posted this, either people dont have an opinion of their own, or they don't care...
dumraden said:
Well, it's been a couple of days since I posted this, either people dont have an opinion of their own, or they don't care...
Click to expand...
Click to collapse
I also read quite a lot of topics, but I don't respond in every topic.
plz some one port miui rom for galaxy alpha
thanx:highfive:
common no one don eny thing yet?
line____ said:
common no one don eny thing yet?
Click to expand...
Click to collapse
Honestly who would want THAT on their phone ?? If you want a bad rom supercharged with crap and bloatware, you can stick to TouchWiz... and for everyone else, you can pretty easliy tweak it to look like you want.
Not worth the work and time at all IMHO. xD
line____ said:
common no one don eny thing yet?
Click to expand...
Click to collapse
The reason no one is replying you is because this is NOT the right place to post for requests
Only the following topics are allowed in DEVELOPMENT area:
[DEV] - Development for any special projects or Apps
[ROM] - Custom ROMs
[KERNEL] - Custom Kernels (usually found in Original Development)
[MOD] - Hack & Modifications for the phone with code only, zips go in themes and apps
[FIX] - Fixes for known issues & bugs
[R&D] - Research & Development for Devs only, when gathering data for a new projects
[HOWTO] / [GUIDE] - How to instructions and Guides (Most of the time should be in General)
Note: If you are unsure where your new topic should go, then please post it to General
Click to expand...
Click to collapse
Maybe read the rules next time and post in the right sections and MAYBE someone will reply you.
no need to raplay this is the topic..... where all the rom developers are to gather.....i hope they make taht...the rom has a meny good nice ability like is oreng and black and good for battry and hase good music player and perfomanc profile....and it has a best music and watther software....very very cool rom