Still an Android noob but i may get the Captivate but can you get stock android 2.1 in a ROM or is that impossible?
champ0497 said:
Still an Android noob but i may get the Captivate but can you get stock android 2.1 in a ROM or is that impossible?
Click to expand...
Click to collapse
I was a noob a few weeks ago so I will give you some advice:
Read all you can first, then reread stuff all over again. Development Forum is a good place to start.
"Stock" android always has extras - device drivers for a phone, kernel enhancements, etc. If you are looking for a build without AT&T stuff, then there are some i9000 Roms, that can be installed, but you need to install the Captivate kernel. All of these are development builds and have some bugs. They also are for the EU Galaxy, and they have different Samsung software included as well as different menus.
There are guys working on building a plain vanilla 2.1 ROM with the source code, but it will take some time.
Is it possible to install a custom ROM on a tablet that is NOT listed on many of the sites listing customs ROMs for cell phones or on the app ROM Manager list? Is there a way to compare a cell phone ROM (native OS?) with a tablet ROM?
Is there a way to install Android 2.2 (Froyo) on a tablet running 2.1 (Eclair) w/out installing a custom ROM?
cBirdR said:
Is it possible to install a custom ROM on a tablet that is NOT listed on many of the sites listing customs ROMs for cell phones or on the app ROM Manager list? Is there a way to compare a cell phone ROM (native OS?) with a tablet ROM?Is there a way to install Android 2.2 (Froyo) on a tablet running 2.1 (Eclair) w/out installing a custom ROM?
Click to expand...
Click to collapse
You can't install a cell phone rom on a tablet. If you do.. then something bad will happen. You would probably have to wait for the official froyo update for your tablet since you wouldn't want a custom one. If you did, then you could get froyo the unofficial way. And for the cell phone rom.. you would have to be a developer/hacker to modify it (key mapping, resolution, etc.) and customize it to make it able to run on your tablet.
Ugh. Wished I'd have asked two days ago! Wasted hours stumbling around websites. No hope of an official update for the SmartQ T7.
What do you mean, ..."get Froyo the unofficial way"?
Oh, and thanks for saving me more hours and a bricked tablet.
cBirdR said:
Ugh. Wished I'd have asked two days ago! Wasted hours stumbling around websites. No hope of an official update for the SmartQ T7.
What do you mean, ..."get Froyo the unofficial way"?
Oh, and thanks for saving me more hours and a bricked tablet.
Click to expand...
Click to collapse
Glad I helped. Anyways by getting it the unofficial way, is to get a custom built rom from a developer, but the bad news is that your device is not a category around here so no developer would publicly make a custom rom for it here.
Hy,I would like to know more about the android versions and custom roms.
1)Why some devices do not support new versions of Android?
Why is not working as a PC operating system? For example when windows7 appeared most of the PCs could install windows 7.
2) Why is possible using a custom rom like cyanogen to update to a newer version of android although this version is not released by the producer. Ex. install ics on galaxy S.
3) Using a custom ROM can update a device from the first version of Android to the latest one?
Thank you for your help.
Catalin
To answer your questions as best I can...
1. Most phones can support almost any version of android. It all has to do with their chipset.
2. When a custom ROM is created, it is based on a certain version of the OS. It is custom because it is modded by developers to be compatible with different devices.
3. Yes. This is true depending on, again, the device and the developers. For me, I have had many devices that were on froyo 2.2. And would not get an OTA update. Whereas a custom ROM could kick it up to gingerbread 2.3 or ice cream sandwich 4.0.
I hope this helps!
Sent from my HTC Vision using xda premium
1. the problem is with your carrier or manufacturer usually. some push updates through fast, others test updates before letting users update. also older phones get forgotten. a new phone will be more likely to get updated than an old one. they want you to buy a new one
2 and 3 what i337 said. i would just add that using a rom bypasses the problem in #1
Also one of the big issues are the drivers. The open source drivers work but don't use the hardware to the fullest. Also non of the OEM related apps and stuff work on AOSP roms. Then you have app compatibility issues with AOSP roms as well.
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
kostistheo said:
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
Click to expand...
Click to collapse
hey mate
your're actually talking about two different things: porting a ROM and flashing a ROM.
Porting means, you take a ROM from another device and modify it so it works on your device too.
flashing means, you take a ROM which is already optimized for your device
and install it, so you wipe the stock firmware and get a custom rom.
which of the two things is what you want to do? i think its just the flashing.
so you can take any ROM from the "development section", and if you follow the guides that you can find everywhere here im sure you will be succesfull and happy with it.
bytheway
there is no "best" ROM for your device. it all depends on what you need and want. there are alot sense 3.5 Roms, Endymion 3.4 is the one i would recommend. you can also try AOSP ROMs (android open source project, means no sense), cyanogenmod7 could be a good first choice. and you can also try ics right now, since there are at least 3 (?) ICS AOSP ROMs right now:
CM9, Virtuous Quattro RC3, IceColdSandwich
have fun!
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
kostistheo said:
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
Click to expand...
Click to collapse
i would never recommend to flash an official ROM over a custom ROM. But anyways, i think if you would have done a full wipe before flashing the official rom you wouldnt have got a "you call it brick"
a real "BRICK" is a useless phone, where there is no way to use it again.if there is still a way, its no brick.. but who cares about definitions
I recommend you to flash the ROMs only through recovery mode. AND ALWAYS DO A FULL WIPE BEFORE FLASHING A NEW ROM. very important
and dont forget to backup as always
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Start flashing different roms and trying them for a day or two. First
Sens 3.0 and then sense 3.5 roms to see the difference. Only then you will know which rom is best for you.
+1 for Endymion 3.4,
+1 for Endymion
Swyped from my Desire S using XDA Premium
+1 Endymion
Sent from my HTC Desire S using xda premium
edymion, will try it
+1266592.23 for Endymion
kostistheo said:
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Click to expand...
Click to collapse
Each ROM type suits different personal tastes, so there isn't an 'best' ROM for everyone. Trial and Error which ones suit you!
General opinions:
Stock
Pro: Straight from HTC, *newest kernel/drivers*, least likely to have compatibility issues.
Cons: HTC is slow to release updates, and sense interface is usually resource hungry.
Sense-like
Pro: usually keep the Sense interface, but custom kernals offer speed / various other improvements.Runnymead versions are kernals ported across from HTC Sensation (which offer some of the goodies like Beats Audio etc. that were not originally developed for Saga.
Cons: Sense interface is resource hungry...
CyanogenMod based
Pro: offer lots of customisations
Cons: not the most user friendly
AOSP
Pro: Roms from the android source, usually less resource hungry, so lighter and faster.
Cons: Obviously, no sense.
ICS Alpha/Beta
Not strictly a new category, but builds from the new Android 4.0 (ICS).
Currently some things (like camera) isn't fully working yet.
Note: new Desire S may suffer from camera/video lag bug with non-stock / non-sense ROMs, this is due to HTC putting in new hardware / driver into the new DS phones and the other kernels not reflecting this change yet.
Personally, I use SenseMOD Lite V1.2 build 2 as it is one of the few AOSP like builds that don't have the camera bug. Oxygen would have been best choice for me but unfortunately camera bug makes it unusable.
Hey guys. I don't want to drive over your feet, but I think the OP is already very satisfied with all those replies. specially the post above is really trying to help, but you spend much time to type what has already been written on the first page.
I appreciate your intend to help, bit I think the OP isn't gonna read this anymore..
Btw: endy!...
Sent by my fingers to your head
Hi friends,
I am pretty new to this forum and before a couple of days i did a research regarding Flashing Kernals and Roms(Dont knw whether my concepts regarding that is right or wrong) and currently i have installed Cyanogen 9.1 for my device.Now let me ask a couple of questions i have for you guys.
1.Will I be able to update my phone and bring back to old ICS firmware via SUS once i brick my phone(I have already unlocked the bootloader via fastboot method)?
2.Evrytime when i flash the Rom(say CM9) i used to flash kernal(boot.img) for the respective rom.Is this necessary all the time?
Will i able to flash a GB rom on ICS kernal(I am afraid to give it a test)?
3.Regarding CM9.1 which i have installed ryt now,I am satisfied with the performance,but i want a stable ROM wud make me happy with a better battery life unlike CM9.1.So could you pls suggest me a GB/ICS ROM which wud have a stable performance with descent battery life.
4.After using GB for a long time,i was very much addicted with the Phone pad kinda keyboard,but when ICS came into picture everything vanished,Smartkeyboard Pro is no gud,Touchpal is conjusted,i want the exact GB keyboard in ICS.Any ideas?!!
Regards
Hazil A.M.