Hello friends,
since i've bought my Desire S, i'm playing with CustomRoms and like to try new one's. So i'm not totaly unknown in this section. I know that we need the new Kernel 3 for get ICS working in our device. But yesterday got my wife her new phone, a Sony Xperia Ray (which is realy great, btw!). I've updated via SEUS (Sony Ericsson Update Service) to official Android 4.0 and saw, that this phone still use the 2.x Kernel, instead of 3.x! I'm just wondering about that and i'm a bit confused. Can anyone explain?
The second one is about compiling / creating a own kernel. I've saw in Desire Section, that they try to create a costum 3.x Kernel. And for Samsung S1, they are finished to create them and got many ICS Roms working. So, is it so much hard to create / compile a 3.x Kernel for our Device? Is it possiple to compile a Kernel from Kernel Source Code: http://www.kernel.org/ ??
Best greetings.
Bulkatos
Bulkatos said:
Hello friends,
since i've bought my Desire S, i'm playing with CustomRoms and like to try new one's. So i'm not totaly unknown in this section. I know that we need the new Kernel 3 for get ICS working in our device. But yesterday got my wife her new phone, a Sony Xperia Ray (which is realy great, btw!). I've updated via SEUS (Sony Ericsson Update Service) to official Android 4.0 and saw, that this phone still use the 2.x Kernel, instead of 3.x! I'm just wondering about that and i'm a bit confused. Can anyone explain?
The second one is about compiling / creating a own kernel. I've saw in Desire Section, that they try to create a costum 3.x Kernel. And for Samsung S1, they are finished to create them and got many ICS Roms working. So, is it so much hard to create / compile a 3.x Kernel for our Device? Is it possiple to compile a Kernel from Kernel Source Code: http://www.kernel.org/ ??
Best greetings.
Bulkatos
Click to expand...
Click to collapse
I'm not sure as to why the current devices with factory ICS or updates to it have kernel 2.6 (because I had the chance of playing with a one x and it had kernel 2.6) but the samsung galaxy s devs could make the kernel work because the exynos processor ( or as it was called back then hummingbird) is open source, unlike the snapdragon in our desire s. Also the original desire also had a snapdragon processor, which unless htc released the source, makes it almost impossible to make a custom3.0 kernel. We have kernel 3.0 on the DS because it was leaked and apparently it cannot be modified to work with vanilla ROM's(it only works with sense). So, I hope I cleared your misunderstandings as best as I could
Related
Hi all,
Sorry 'bout the n00b question - but are there any of the custom ROM's out there which can be used for the Samsung Spica? I think my Spica is so darn slow, so really want to spice it up a little.
Just come off a SE Xperia X1, and used to flash it every other day - which I kinda miss on my Android device.
So - how is my outlook here?
Happy new year!
No one knows anything about this?
millen said:
Hi all,
Sorry 'bout the n00b question - but are there any of the custom ROM's out there which can be used for the Samsung Spica? I think my Spica is so darn slow, so really want to spice it up a little.
Just come off a SE Xperia X1, and used to flash it every other day - which I kinda miss on my Android device.
So - how is my outlook here?
Happy new year!
Click to expand...
Click to collapse
Not going to get much help here. After all this is a forum for HTC devices. AFAIK there is'nt a lot of custom ROm development for the spica apart from Leshak's ROM. you could google it.
Cheers
Try samdroid.net. There are active forums for samsung spica rooting, kernals and custom roms alongwith lots of tweaks and mods/
Hey
I have the following
Baseband version-i570EJXJC2
Kernel 2.6.29 [email protected] #2
build eclair jpjd7
Questions-
1. Which of these is the PDA or CSC etc
2. what should i do..i have jc2....I cant use spica jc3.ops
3.all i want is to root my phone and use app2sd since my phone memory is always full.
I cant use LESHAKS........... lk2 mod without being on lk mod i guess...also this firmware is what i got here in dubai. please help me root my phone...I am so confused with this firmware. only after i flash a good european firmware and root it can i use custom roms right?
AFAIK, the only stable and popular ROM, is the one from Leshack.... lets hope cyanogen releases something... i think both can take profit of each other's work and release something wonderful (froyo + multitouch + overclock + 3D driver.... etc...)
Hello everyone,
I'm trying to compile my own source ROM for my Sensation 4g (TMOUS) My HBoot is 1.17.000 revolutionary unlocked. My compile from google source gingerbread 2.3.4 (to match version htc is using) went ok however with no lunch or envsetup option for the Sensation my full-user make showed compiling for generic. I have tried fastboot flashing my compiled userdata and system img files to my phone along with my default sense kernel (kernel from TMOUS rom 1.5 made from clockwork recovery) to find that it doesn't get past the white htc screen. I'm interested in compiling and sharing this ROM with the public however finding I'm a little lost on next steps.
In the court of public opinion, what would my next steps be? Is my lack of booting due to the sense kernel and instead should I try using a kernel like trinity cm7/asop kernel? Is my lack of booting even kernel related?
Any advice I would greatly appreciated and once I can get this thing running I will be glad to give credit where due and distribute any modified files. Also, if I run across any additional information that might help anyone I will update this post.
PS - I know ICS is out and it might seem odd to try with gingerbread to start (along with using 2.3.4 instead of 2.3.7) however my rationale is that by trying to stay as close to the gingerbread rom HTC provides version wise I might have the best shot at compatibility.
Thanks everyone.
Various ROM developers have IRC channels. It might be worthwhile trying and asking a developer on there, just don't bug them too much.
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
:fingers-crossed:
Hi I am new to this forum so hope I have finally got this in the right place. I have a rooted samsung s2 mobile which I have flashe dthe ICS 4.0.4 I am interested in learning more about Kernels, which ones can I use, how do I know which each one does and how do I understand the language of the Kernel. If anyone can help / advise dummies guide required......
thanks in advance
Pluto
ysigina practically
You should be able to find several kernels suitable for your SGS2 right here (XDA). Search for 'kernel collection sgs2' on google. The 3rd link from the top should be useful and have current ICS kernels (which are compatible with your device).
To name just a few:
N.e.a.k.
Siyah
CF-Root
Phenomenal
Make sure that, whatever kernel you decide to try, it's compatible with your ROM (in your case ICS 4.0.4).
best kernel for galaxy s3
Hi Guys,
can someone recommend me a good kernel for SGS3 based on JB?
Thx
morskipas
Hi,
Without having any (ROM) development skills I have tried to copy/port/compile a Android 4.4 ROM myself. I did not succeed but in the process I have learned a lot in general about ROM development. I'm not aspiring to be a ROM developer, but at this moment I am eager to know what exactly are the bottlenecks in creating a 4.3 or 4.4 ROM.
I have copied, dissected and altered the work of the guys who have 4.4 (partially) running on HTC Desire HD and HTC Incredible S. To my knowledge these devices have a lot in common (for the most part) and, in my mind, should work on SAGA with some tweaks (ACE -> SAGA / VIVO -> SAGA). Replacing text is off course a simplification, but hey, besides the camera, it is almost the same hardware. I guess there is more to it, because I tried several times, but did not get it to work.
I do not expect to solve these issues, but I wonder what holds the (stable) development of a 4.3 or 4.4 ROM. Outdated source code of drivers or kernel or ....
I was thinking of contacting some of the DEVS who are working on the 4.4 ACE and VIVO ports, but I hope someone on this forum can enlighten me.
Regards,
Michael
Ace and Vivo are indeed closest models to saga and very similar,..when ported to saga,
the roms seems ussualy faster,lighter,cleaner, much less bugy than those, ported (especially directly) from other devices,
.. What- most possibly holds the development for this device is the kernel (or its absence)-as often,..
very likely,-when there was a possibility to boot the port, without jumping also, to self porting/modding its kernel,
we would have seen yet quite a few stable KitKat ports,..
Kernel devs for desire s were briliant- but never many,
now, only @kylon remains active- pardon me if i`m not correct ,,