Hi,
Thank you guys (and girls of course) for pushing the android experience more than just-another-smart-phone for the curious users.
I have searched a lot by moving around in this forum for last couple of days, looking for a cool ROM for my first ever (but not last, only the beginning) ROM upgrade.
I have read the wiki and have explored all the given links. But I couldn't find few simple answers. Please help me by answering my following questions-
1. Is there any list of currently available ROMs with pros and cons of each ROM? Is there any benchmark for stability, performance,supported features for all the available ROMs ?
2. What's there any matured stable 2.x.x ROM for HTC magic 32A which is not-slow and does well what it is supposed to do?
3. What's the pros and cons for older versions and newer versions? In another way of asking- why you developers still working on the 1.5 and 1.6 ROMs? Why not 2.x.x for HTC magic?
4. (lame question) Which of the ROM versions does have flash 10 (so that flash videos or files will work on webpages)?
Please ignore my lack of knowledge and enlighten me and other newbies as well.
Thank you very much once again
1. No but you may have a look at this.
2. Manup456's Eclair is what I'd go for. It isn't slow nor buggy but keep in mind that there are things that still don't work properly and probably won't until HTC or some operator releases an official 2.1 update for the Magic. You'll also need a port to install it on a 32A.
3. 1.5 and 1.6 have been officially released for the Magic while 2.xx hasn't yet. That means everything works as it should on 1.5 and 1.6. On 2.1 you get the new Android features but you lose some functionalities as well so it all depends of what you need and don't need (if you can live without camera recording and hardware acceleration you'll be fine). People also stick to some 1.5 ROMs because of SenseUI (there are a few 2.xx ROMs with SenseUI but none of them is really ready for prime time).
4. Flash 10 isn't available to us yet. There is a version of Flash Player included in the HTC Browser (meaning you need a ROM which includes the HTC framework) but it's not that great as it doesn't support the newer Actionscript 3/FP 10 Flash files. It can play Youtube videos though.
My personal advice would be to avoid 2.xx ROMs for the moment and to try a good stable 1.5 SenseUI ROM like Cursorsense or GyD... and if you then feel that 1.5 is too old you can try Amon RA's Donut or Ahmgsk's.
Hope this helps... you could have posted this in the general forum though
Hey there... just wanna ask you geeks here how hard is to port Android 2.2 to a 2.1 Device?!
i've just ordered the new aPad or gPad (G10) today with TeleChip and Android 2.1 onto...
also have the "old" 1.5 aPad with the RockChip, but no 3D acceleration and with no official support für 2.x !!
But theres already a quit big custom rom scene there...
but i think my question is better repealed here!
how hard is it to port 2.2 ??
what does i ned ?! Source of the 2.1 ?!
thx for any Help!
You can't port 2.2 to 2.1, you port it to the device
Sent from my Nexus One using XDA App
GlobaL_TroTTer said:
You can't port 2.2 to 2.1, you port it to the device
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
??? read what i wrote!!
port Android 2.2 to a 2.1 Device
Click to expand...
Click to collapse
... i have a 2.1 Device and want to Port 2.2 to it ?? Port Android 2.2 to a 2.1 Device...
don't needs to be device specific... a generall statemate is allready more than i have now!
I think the point that is trying to be made is that you have a device. It happened to have come with 2.1 on it. It's not really a 2.1 device. It's just a device with 2.1 on it. You just need a kernel and device drivers that are compatible with 2.2 and your device. That's very much a summary though.
If I had to guess, you should be able to get most things working under 2.2 with the drivers from 2.1. However, I only have 1 device (a Droid Eris), so I have no experience with the devices that you mention.
gnarlyc said:
I think the point that is trying to be made is that you have a device. It happened to have come with 2.1 on it. It's not really a 2.1 device. It's just a device with 2.1 on it. You just need a kernel and device drivers that are compatible with 2.2 and your device. That's very much a summary though.
If I had to guess, you should be able to get most things working under 2.2 with the drivers from 2.1. However, I only have 1 device (a Droid Eris), so I have no experience with the devices that you mention.
Click to expand...
Click to collapse
i'm awar of that the device is "not a 2.1" device only... and it could be possible to get an official ROM in future.. but i wanna try to do it earlyer on myself!
so that is the point...
i saw this from HD2 Android Development...
there where firstly only 2.1 available..
but shortly after that there was a 2.2 Port too!
i pretty guess that they didn't have to rewrite the hole modules (drivers) the just edited somethin in the Nexus/Desire 2.2 File so to match the HD2
thx
futureshock said:
i'm awar of that the device is "not a 2.1" device only... and it could be possible to get an official ROM in future.. but i wanna try to do it earlyer on myself!
so that is the point...
i saw this from HD2 Android Development...
there where firstly only 2.1 available..
but shortly after that there was a 2.2 Port too!
i pretty guess that they didn't have to rewrite the hole modules (drivers) the just edited somethin in the Nexus/Desire 2.2 File so to match the HD2
thx
Click to expand...
Click to collapse
Understood.
It's quite possible, I'm sure. There has not been an official 2.2 update for the Eris (and won't be), but there are several CM6 (2.2) ROMs out for it. The same for the Hero and probably several others.
I have a partially working AOSP (non-CM) 2.2 ROM, but have yet to get the audio to work. (I really like to hear the phone ring, so it's not quite usable yet.)
ok sounds good so far...
now the question is, whats the general process of gooing such a port on?
to get the system dump is not the problem... that should be done easily...
Are you talking about below device ?
Apad iRobot Telechip TCC8902 7" Android 2.1 Tablet PC 4GB a.k.a Haipad M701
Apad telechip TCC8902 packs a Telechip CPU clocked at 720MHz and based on the ARM11 core, replacing the ARM9-based 600MHz Rockchip RK2808. The CPU also includes a DSP co-processor and 3D graphics acceleration with support for 1080p full HD video. Tthe CPU upgrade will be compatible with Android 2.1, upgraded from android 1.5 of the original Moonse E7001.
http://www.shenit.com/apad-irobot-telechip-tcc8902-7-android-2-1-tablet-pc.html
I also purchased this device months back, and interest looking for upgrade to Andriod 2.2 Froyo.
Also recently, I purchased below device as well, just because my 7" apad become much of game playing for my kids at home, so need to find myself a better working apad.
Utopia Apad iMX515 8 inch Android 2.2 Tablet Freescale ARM Cortex A8
The Utopia Apad iMX515 runs Android 2.2 OS with Freescale iMX515 Cortex A8 Chip, support Flash Player 10, 512M RAM with Built-in 4G Nand Flash. Now you can surf the real web and watch all your favorite Flash video or play Flash game on this affordable android tablet.
http://www.shenit.com/utopia-apad-imx515-8-inch-android-2-2-tablet-freescale-arm-cortex-a8.html
However, it will be nice to be able to upgrade them with better OS, the shop tell me not upgradeable.
Am I the only one who is unhappy with the slim pickings of ROMs that are available for the SK4G?
Does anyone know anything about an ASOP ROM?
It's AOSP (Android Open Source Project) and you're not the only one not happy with the current SK4G options. I personally want MIUI or CM7, but seeing as we're currently stuck with Froyo, we'll have to see what the devs can cook up.
Sent from my SGH-T839 using XDA App
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
sduvick said:
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
Click to expand...
Click to collapse
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
ayoteddy said:
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And so anticipation had set in, i can't wait ayoteddy. im very excited. SMX was great, and SMGC was awesome, and now with this? whewwww. think i better go lay down, lol.
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Thank you for joining the Sidekick 4G section , & we welcome you but if you want you could pause the game's for the ROM if anything & Question 1 is a no & Question 2 no cause they have to be compiled with the 2.3 kernel .
- Said by Sduvick
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
Revolution, thanks for relaying my responses.
jmpz, I tried building the source before, but was unable to build it completely, but that was possibly because of some errors with my dependencies. The kernel compiles fine from source, you just need to pull initramfs, or you can get it from Dr. Honk's github.
Thank you for your answers.
So, can anyone enumerate the list of drivers which we should extract from kernel?
I can name these:
1) Keyboard
2) Mic
3) 2 speakers
4) buttons
5) front camera
6) rear camera
7) trackpoint
8) lcd
9) digitizer
10) 3.5 jack
Please correct me and add missing
If I understanding it rightly the key problem is getting proprietary drivers from the kernel. Right?
nope, the key problem is trying to build the system entirely, without any errors, which may be easier with someone following a stock designed build environment. I don't use Ubuntu which is what has the listed dependencies for every tutorial I can find. You can get the drivers out of Dr. Honk's voodoo kernel ramdisk here: http://forum.xda-developers.com/showthread.php?t=1145139
There shouldn't be any problems if you just set up a build environment following the directions in any of the tutorials, then add the platform from the samsung source.
I'm a linuxoid - so these tutorial are for me. Thank you for the link.
By the way, drivers are in Linux Kernel, so I don't think that I need to use Samsung Platform from the source. Instead I wanna use platform from AOSP or Cyanogen. Correct me if I'm wrong.
I think that grabbing drivers from kernel source from samsung would be enough to build the rom.
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
I 100% support your efforts. I want Cyanogen on the SK4G badly, but I'm not sure what kind of help a non-programmer like me could do, but do have some experience with flashing phones and such, so if there is anything you need let me know.
If you do get rolling heavily on this, I'd be willing to donate monetarily to your efforts.
If anyone can get CyanogenMod 7 on the Sidekick they would definetely get a donation from me. Id be thrilled. Glad to see its going to be worked on.
Sent from my Sidekick 4G using XDA Premium App!
Any windows based universal rom customizers?
i have searched google and can not find any thing, just wondering what do most devs use to make basic changes to pre made roms thanks
hi,
as the title suggests, i would like to make a custom rom for this device... either modify the current 2.1 rom and make it app2sd compatible or make a 2.2 or higher rom that natively supports it...
i just need some info... firstly, which would be the easier thing to do?
if modifying the stock rom, what would i need to do 2 make it app2sd compatible?
if making a custom rom, how would i go about doing that?
i would imagine its possibly like getting a windows os and adding drivers for a specific machine before instalation... except in this case i think its a custom build.prop right? any help is much aprieciated...
oh and a final thought, if i make a mirror of the stock rom which bits can ibuse from it 2 aid me in the making of a new rom? id ideally like a 2.3.7 cyanogenmod7 rom just coz my current device (hd2) has a cyanogenmod7 rom and it works flawlessly... i do have a few hd2 android builds, can i disect these and modify them from what i have on the cyberjam?
basically i have a lot of apps and would like 2 have hardly any limitation on how many i can have as opposed to having 4-5 n gettin the memory getting full warning...
again, thanks in advance...
better still, add a forum for this device and have a big long list of compatible roms lol...
and finally, (another p.s)
there is a device which is very simmilar called a bsense 383.
now this does have a 2.2 rom available, only difference i can see is the cpu in the bsense is dual core aparently... the other hardware appears to be the same (haven't seen a list of every part inside both but the few parts i have seen are the same minus the aforementioned cpu)
so i look forward to your reply and hope that this is possible and plausable...
thanks, luke
31 views and noone can help me? come on xda community... surely someone can help me out...
Just read up on dsixda kitchen and once you get it installed in the right environment you can run pretty much any Rom through it and add that feature along with many other things. As long as you don't redistribute someone else's work, its ok.