Related
i was just wondering what these kernels do . need less of that i read everywhere that our devs were waiting for huawei to release official 2.3 so they can get the kernel .
isnt it possible that we can make our own kernels or now as we have new kernel so can we expect new cm7 or xygen or miui to come out with an awesome flawless rom ????? surely the touch is much smoother on official 2.3 n camera has significant improvement ( UI is childish )
mkr17 said:
i was just wondering what these kernels do . need less of that i read everywhere that our devs were waiting for huawei to release official 2.3 so they can get the kernel .
isnt it possible that we can make our own kernels or now as we have new kernel so can we expect new cm7 or xygen or miui to come out with an awesome flawless rom ????? surely the touch is much smoother on official 2.3 n camera has significant improvement ( UI is childish )
Click to expand...
Click to collapse
On the "what these kernels do..." check wikipedia, Android Kernels are based on Linux kernels. In just a few words kernels provide the basic functionality for applications to work (devices, memory management, process management)
Developers wait for the kernel source code (which is a 2.6.35 kernel), not the binary that is included in the official ROM (thankfully, Huawei is obligated to release the source).
When kernel source is released, any developers that want to build, tweak, study, copy, use the kernel source can work their magic *crosses fingers for CM7*
Hi all,
For everyone asking about custom roms ont 2.3.4 here is the situation :
For everyone who have upgraded the MS2 to the Official 2.3.4, no step back is possible to Froyo 2.2 or 2.2.2.
custom ROMs based on Froyo will not work (like CM7/9 from Tezet.)
=> Someone will have to build on based on the 2.3.4 kernel.
custom ROMs based on Chinese GB seems to work...
=> MS2Ginger for exemple.
custom ROMS based on Defy+ ROMs ?
So, who want that the CM or MIUI ROMs are ported to the newer Motorola kernel ? (So everyone could choose between BLUR, CM and others ?)
I say it on an other thread that the ms2ginger and the argen2stone roms are running on an ms2 with stock gb rom. Somebody must make an cm7 with the 2.3 kernel than wie can use customroms.
thanks for your thread.
But my question is, this official rom 2.3.4 does work better than froyo? or the custom rom 2.3.7 de CM7? It might be a dumb question or it's answered in another thread, if that case sorry.
Thanks
Yes i want Miui with the new kernel ! For a better touchsreen sensitivity for eg.
I try Argen2Stone 2.7 RE but i dont see adjust scrips and keep the old dialer from stock rom.
The 2.3.4 brings some bug fixes, and some upgrades.
From the kernel point of view, the same release is used (Linux Kernel 2.6.32.9). So no major bug fixes at kernel level for my point of view. Maybe some parameters changed.
The main point is for the "upgraders" to Gingerbread that can't go back to Froyo.
boorce.com said:
Hi all,
For everyone asking about custom roms ont 2.3.4 here is the situation :
For everyone who have upgraded the MS2 to the Official 2.3.4, no step back is possible to Froyo 2.2 or 2.2.2.
custom ROMs based on Froyo will not work (like CM7/9 from Tezet.)
=> Someone will have to build on based on the 2.3.4 kernel.
custom ROMs based on Chinese GB seems to work...
=> MS2Ginger for exemple.
custom ROMS based on Defy+ ROMs ?
So, who want that the CM or MIUI ROMs are ported to the newer Motorola kernel ? (So everyone could choose between BLUR, CM and others ?)
Click to expand...
Click to collapse
I tryed to flash MS2Ginger but the MS2 doesn't turn on.
I don't know.
could Anyone post how to flash step by step ?
tks
I think that the new kernel can improve MS2 performace so a rom based on the new kernel it's much better than the old modded rom.
Simokill said:
I think that the new kernel can improve MS2 performace so a rom based on the new kernel it's much better than the old modded rom.
Click to expand...
Click to collapse
I have the same idea...waiting for some MIUI or CM7 based on this new kernel.
I'd like someone who knows what they are doing to de-blur it. I have removed as much as I dare but still have too much moto... rubbish on the phone.
yeah agreed with u guys i wish a custom rom based on new gb 2.3.4
diavolobianco said:
yeah agreed with u guys i wish a custom rom based on new gb 2.3.4
Click to expand...
Click to collapse
+1
or new FR
is true. I think it's time to leave the kernel of froyo that is old and start to compile with the new kernel brings improvements and is of GB!
GB kernel is in fact the same linux kernel version as froyo kernel, so there are not any improvements except for some minor patches.... So no reason to leave froyo.
I just don't get why you all guys updated to GB and then you all crying, you can't use custom roms and that froyo kernel is old and why gingerbread isn't used... GB kernel in custom roms isn't high priority in dev right now. Deal with it. GB kernel don't bring any valuable improvements, so only reason to leave froyo and get in GB are you all, who did that mistake and upgraded to official GB without even reading the forum here (because it was already written so many times there...).
No offense please, I'm just sayin' that GB kernel in custom roms don't have high priority, because of missing downgrade capability and because they don't bring nothing so exciting and big or valuable, nothing worth. So when dev update to GB, he can't go back to froyo - and this is quite big limitation...
Actually CM9 does work over Euro GB kernel. It is based on Chinese GB kernel. And I must say Tezet has made some really good progress with CM9.
And Defy ROMs based on Defy+ kernel have also been proved to work on Euro GB kernel.
These ROMs work if we remove devtree.img and boot.img from the update.zip and thus only flash system.
So I guess it is only a matter of time.
Anonymous_ said:
I just don't get why you all guys updated to GB and then you all crying, you can't use custom roms and that froyo kernel is old and why gingerbread isn't used... GB kernel in custom roms isn't high priority in dev right now. Deal with it. GB kernel don't bring any valuable improvements, so only reason to leave froyo and get in GB are you all, who did that mistake and upgraded to official GB without even reading the forum here (because it was already written so many times there...).
Click to expand...
Click to collapse
Good sir, your silver tongue rivals that of our finest bards! Please, travel amongst the populace, spreading joy and soothing woes.
Anonymous_ said:
I just don't get why you all guys updated to GB and then you all crying
Click to expand...
Click to collapse
No crying here, just discussion, which is what the forum is for. What was your point?
may be it's better to find a way to downgrade.
Kangburra said:
No crying here, just discussion, which is what the forum is for. What was your point?
Click to expand...
Click to collapse
I think I said my point clearly... But once again then:
I'm just sayin' that GB kernel in custom roms don't have high priority, because of missing downgrade capability and because they don't bring nothing so exciting and big or valuable, nothing worth. So when dev update to GB, he can't go back to froyo - and this is quite big limitation...
And don't take my words too personal. Easy man, easy...
Sometimes it's cool to have stock ROM. But,it will be much cooler if we can switch to custom ROM's. Stock ROMs are slower and less free RAM than CM7 or MIUI. Now,I'm getting bored with MS2Ginger2.1.
All we have to do is just wait..
hi, did anyone manage to overclock after updated to stock 2.3?
android overclock doesn't work anymore after i updated
I know our device runs on kernel version 2.6.32. But what all improvements benefits would we get if we were able to get kernel 2.6.35 or 3.0 working on our device ?? also is getting 3.0 working on our device much more difficult than getting android 4.0.3 working ???
nishant_713 said:
I know our device runs on kernel version 2.6.32. But what all improvements benefits would we get if we were able to get kernel 2.6.35 or 3.0 working on our device ?? also is getting 3.0 working on our device much more difficult than getting android 4.0.3 working ???
Click to expand...
Click to collapse
I think the new kernel brings bug-
fixes and security patches.Porting it should be much less difficult then porting Android 4.0.3 but you really need someone like mercellusbe with a fair bit of lnowledge in C
I have one question.
Why use the froyo kernel at all?
Upgrading ALL defy/defy+s to the latest (rootable, 1321 or 139 preferred for simpler root) 2.3.6 GB kernel would simplify rom/kernel development for the devs. Since more and more defy+s are in use they can simply drop development for the froyo kernels and focus on the GB kernel, since now all defys, whether the old one or + would be running 2.3.6. Any current devs (if they want to retain current status) would just have to switch to GB kernel support for their rom once and keep it that way.
Because the SOC module (green lens) is compatible only with the Froyo kernel.
Upgrading to the Gingerbread kernel means that the camera will be unusable for those Defys.
Forgot to add: Having a locked bootloader sucks.
Trimis de pe Defy CM9
So all defys are not equally upgradable to GB (kernel)?
What kinda BS policies are these from Moto? Locked BL they have their reasoning about not wanting users to hard-brick the phones, but what reason to not allow officially updating to GB for ALL defys?
Unfortunately, no, not all Defys can be upgraded to the Gingerbread kernel and still be fully functional (exception being the Greenbread mod). And the devs can't do anything about it because of the locked bootloader.
Regarding Motorola and it's policies - it's all about the money. Outdated phone -> unhappy people -> they buy a new, updated phone -> happy Motorola.
Trimis de pe Defy CM9
Using Froyo makes sense for those, who want to keep the warranty and have to stick to the highest officialy available version. I had to update because CM roms work only with Froyo upwards.
vap_66 said:
Outdated phone -> unhappy people -> they buy a new, updated phone -> happy Motorola.
Click to expand...
Click to collapse
They buy a new, updated phone from someone else. By keeping the Defy stuck on Froyo they've made a lot of people decide never to buy any product from Motorola again.
that is true. the bl lock stops us from changing kernel.
Sent from my MB525 using xda premium
This means that there is Froyo source, but not the driver source for the green lens ?
At this moment, if I want to improve my Defy (green lens, original Froyo 2.2.2), what firmware is the best?
It should support everything (3G, 2G, HSDPA, WI-FI, camera for both photos and video recordings, GPS, sensors and so on).
I'm a newbie and for me it's a bit confusing to see a mod called, e.g., "[ICS] CM9 Android 4.0.4 for the Defy (Froyo kernel)" (there are others, this is only the first I've found... )
ICS is ICS, Froyo is Froyo.
What I gain and what I loose with an ICS "Froyo Kernel"?
Is it ICS or Froyo painted with ICS dust ?
vap_66 said:
Because the SOC module (green lens) is compatible only with the Froyo kernel.
Upgrading to the Gingerbread kernel means that the camera will be unusable for those Defys.
Click to expand...
Click to collapse
Well, I've just upgraded to WIUI 2.4.20 (GB) and now I've GingerBread (2.3.7) full working.
My Defy has a green lens and the camera is working, both for photos and videos.
Have I missed something about the thread?
Are you sure WIUI changed your kernel? ROMs and kernels can play mix'n'match.
Motorola has locked the bootloaders of defy
Thus we can only use motorola signed kernels.
Defy has a froyo kernel and defy plus has GB kernel. Both signed by motorola.
Only these to can be used in custom roms. Even in ics and even in jelly bean (Android 5.0) we will have to use these kernels as long as motorola doesnt unlock the bootloader. Froyo build of ics means ics that runs with froyo kernel. GB kernel works only with red lense cameras of defy and all defy+. So only froyo build will work for green lens defy.
^^
This was exactly why i was confused. Do you mean the green lens Defy cannot be officially upgraded (either OTA or RSDLITE) to GB ? And the red lens Defy can be upgraded to GB?
rogier666 said:
Are you sure WIUI changed your kernel? ROMs and kernels can play mix'n'match.
Click to expand...
Click to collapse
Maybe you're right...
Android Version 2.3.7
Kernel Version 2.6.32.9-gb08c3c8
But the 2.3.7 version is GingerBread, whilst the 2.6.32 kernel version is Froyo.
So what's the point ?
The mods are always Froyo but with GB features ?
Defy with green lens can be upgraded to gb kernel but many features inculding cam may not work.
The gb kernel was extracted from defy+. As defy+ has only red lens the gb kernels works with defy red lens also.
Fully functional green lens gb kernel will be possible only when defy gets an official gb update (highly unlikely) or when the defy bootloader is unlocked(higly unlikely too).
---------- Post added at 04:05 PM ---------- Previous post was at 03:58 PM ----------
defy green lens with gb kernel may end up in a bootloop.
so thread with caution.
Flashing an GB sbf will prevent you from coming back to Froyo(Downgrading).
Always try to flash using CWM to keep downgrading options alive
Are there no "fixed" GB SBFs to keep downgrade options alive?
No defy owner should upgrade to gingerbread kernel by flashing an sbf. Our bootloader can load the gingerbread kernel, the gingerbread bootloader can't load the froyo kernel.
So when you flash the sbf you can ONLY use gingerbread kernel based ROMs from then. Otherwise you can just flash the kernel you want from the recovery.
It would even be wise for defy+ owner with bl5 and 6 to flash the bl6 froyo ROM so that they can use both builds by just flashing the right kernel.
About official gingerbread: they are for the defy+. Officially the defy has no gingerbread ROM. For some countries the defy even stays on eclair. Although it would have cost Motorola 5 min to replace the camera and battery drivers. Only problem is money for Motorola and the operators.
Sent from my MB525 using XDA
Hi guys i'm very confused about Cm 9 nightly builds.
Is Eppy's 13/05 Buils is the stable vesion?
As far as I know there is no stable versions for the defy!
CM make stable versions but not for the defy well not the defy+ anyway and epsylon mods the CM version to work on defy with other mods as well. Like tweaks and he may add things and remove things.
So no its not stable. I dont think there is a stable CM9 build, the latest Stable CM build is CM7.1 AFAIK and it may be used by epsylon or quartx or other moders but I dont call that stable.
here is CM lastest stable version for the defy (not sure if it works on defy+ as its just a jordan version and there are no jordan+ versions)
http://download.cyanogenmod.com/?type=stable&device=jordan
Edit: so you know a stable version is considered one that would run like a stock version and one you can trust to put on other peoples device that would not know how to mod it. All the rest come with risks and they could work perfectly fine for you and not so well for others. From what I have found defy can be a real pain to work with and there is no real time support (by real time I mean we have to have modders like epsylon and quartx to mod the ROM's that are made but say CM to work on our devices) and the defy having so many makes and variations then there is alot of conflict and what works on one device may not work on the same one for another person.
Its a real pain and the bootlocked on the moto phones are a real downfall. I found out today that telstra got the defy as it meet there spec for rural service and MOTO changed them specs before shipping it out then telstra got them to change it back to the original. So the same device has so many different changes its not funny. As well as the cameras and batteries and all that so who knows what else has been changed!
Nightly's are not stable..
just try a nightly..if everything wat u need works fine then stick to it..so give it a try for atleast 1 week..
If you meant the latest version then it's Quarx' Version from May 11. Currently I am running this one on my Defy+ and for me it runs pretty reliable, but it's still not called "stable". More like "alpha" or "beta".