Hi guys, I've just got a Milestone, and I think that I should 'port' the TastyFroyo ROM that I already released for the Hero and make it available for the milestone. But I do have two questions:
1. I know we have leaked 2.6.32 kernels for froyo, but I really don't like the battery life that they provide. AFAIK we have the 2.6.29 kernel sources for our device. Do CM6 based ROMs work properly with the 2.6.29 kernel? We've got all hardware working on our Heros without any substantial modifications, using the 2.6.29 kernel.
2. Can someone point me to a functional vendor tree for Milestone?
Thanks,
Radu
see http://android.doshaska.net/cm6build
the first 0.01/0.02 versions of CM6 for Milestone were based on 2.6.29 kernel and 2.1 proprietary libs (as at that time, Motorola haven't started the work on froyo yet, 2.1 was all that was available).
My repos are of course currently based on use of the 2.2 proprietary leaked libs & executables/2.6.32 kernel.
https://github.com/nadlabak
Please note that on Milestone, there are more proprietary closed source files in use than on Hero, and the biggest issue is the very complicated ril implementation, as the ril functions are partly realized in BP and partly in AP (gkisystem etc). The main issue of the 0.01/0.02 CM6 for MM based on 2.6.29 kernel were occasional BP panics...
Thanks for your answer.
This is pretty unfortunate, as the leaked 2.2 and CM6 based ROMs work decent performance-wise, but the battery life is awful. Are the guys from Motorola supposed to release an official 2.2 update soon? Because that means that the kernel sources will have to be released too, making our life easier.
Dunno.
Meant to be released end of 2010.
Still waiting.
http://forum.xda-developers.com/showthread.php?t=920177
I think battery life of last CM mod is good almost like the official 2.1
Related
Hey guys, been out of the loop for a while as I've been settled on JPY for a few weeks now. However, I saw a friend flash his Desire today with Oxygen, a gingerbread-based AOSP ROM. All the SGS ROMs I can find so far are based on the stock Samsung firmware - is there any work being done on a full AOSP ROM like Oxygen or Cyanogen? I can't find any details about this anywhere.
I am very curious about this question. Because if answer is simply no, it's time to sell Galaxy S. Gingerbread will be the last update from Samsung and AOSP could be the future of this phone then CM7 for SGS seems to have big problems and it's the only AOSP ROM for SGS which I'm aware of...
What big problems?
I'm using CM7 for a month right now and it's pretty stable if i can say. Yes, it lacks some features and some bugs are not fixed yet (theres a workaround tho), but if you follow it's thread the progress they make are great. They're already into mainline, so probably it will reach RC status in a month/maybe less, who knows.
After the devs are done, i think there will be a custom ROM based on CM7/AOSP.
~drz
CM7 is getting there. And with Gingerbread coming out, that should make things easier for the dev.
Yes, but with no source then there is nothing big. GB leak, only helped them with "less" important stuff (FM radio, etc.)
~drz
i just looked at this video http://www.youtube.com/watch?v=j4NqT6u_ODk and started looking at honeycomb. When i first looked at the froyo video the the gingerbread video i noticed how fast our devs started working on the project i was just curious if this is already being worked on or if its even been seen thanks for any replys
AFAIK, the source hasn't been released yet. Supposed to be today.
Honeycomb is for tablets only. I don't think it will work on any phone.
pfrederickjr said:
Honeycomb is for tablets only. I don't think it will work on any phone.
Click to expand...
Click to collapse
from what ive heard it will be for phones as well
It's supposed to have some smartphone support...
http://www.engadget.com/2011/01/28/android-3-0-honeycomb-emulator-has-traces-of-smartphone-support/
Dude before we start hoping and dreaming for a honeycomb update to our phone why not lets see the gingerbread one get at least one stable release. Plus like others have said honeycomb is for tablets, for now.
From what i know, google is going to release android 3.0 as honeycomb for tablets and then later on work in and refine the smartphone side and release android 3.2 as honeycomb for smartphones.
Also, before we continue to build android updates for our hero we need a newer and more stable kernel.
S0be has been working on 2.6.35 and he's done a lot of good work, i'm pretty sure deca has also contributed to that as well and deca also maintains a 2.6.29.5 kernel.
S0be kernel
once that kernel is done then the likely hood of having honeycomb running on the hero is good.
By then there will be no devs left
--------
Sent from my Sprint SuperHero
Pocker09 said:
Also, before we continue to build android updates for our hero we need a newer and more stable kernel.
S0be has been working on 2.6.35 and he's done a lot of good work, i'm pretty sure deca has also contributed to that as well and deca also maintains a 2.6.29.5 kernel.
S0be kernel
once that kernel is done then the likely hood of having honeycomb running on the hero is good.
Click to expand...
Click to collapse
Notice: Don't take this as gospel truth, I'm not a rom modder, just a kernel hacker
The hard part in getting up and running on a new Android release has very little to do with the kernel. For the most part, the Kernelspace/Userspace APIs have stayed the same. Where the problems lie are in the Kernelspace Helper Libraries and their connection with userspace. We do not have the source code for all these libraries, which is why it's not just *POOF* it works every time a new android release comes out. My 2.6.35 kernel just means that any direct kernel dependence new android adds will be provided, but it does NOT solve these intermediary layers. There is, in fact, the possibility that a new android release won't be compatible with our libraries, and we'll be proper focked.
Hi,
i am new to Nexus One Android Development and i am a bit confused.
There are so many Gingerbread ROMs out there and i cannot decide.
I firstly wanted to install MoDaCos Sense Build but that is buggy for me - so now i want Gingerbread on my N1.
Unfortunately there are CM7 based/stock ones/google AOSP's/GRI40s/2.3.2's/2.2.3's/pure google mods/OFIICIALS/Devs onlys etc. - Versions!
Can anyone be so kind to filtrate that a bit?
This shouldn't be a "Best GB-BUILD"-Thread - I just want a clean and stable Gingerbread running with my purchased launcherpro plus!
I don't want it bleading edge, but fast and stable!
Which one of the thousands out there should i run on my N1?
Hi bunnahabhain,
I have tried various gingerbread roms, most have had some annoying bugs like hspda freezing, random FCs. The one that works the best for me is the CM7 RC2 which is the equivalent of Gingerbread 2.3.3. It is yet to bug out on me and it runs very smooth. In fact i havent had to restart the phone since I installed the rom. Surprisingly it also takes less space on the phone then most roms I've tried.
Hope this helps. It is bleeding edge but it is very smooth and hasn't been buggy at all for me.
I am using the stock gignerbread, with launcher pro plus/setcpu and automatic task killer.
It runs very well, no crashes, no bugs, it's fast, I sugest you do the same.
Add a poll to thread and list available options for people to vote?
DONE - 8 by number
just chose the most favorite ones
Stock/Official/Vanilla are the same. Just what the names suggest really.
Cyanogenmod is by far the most widely used custom ROM. Many of the others are based off this, with various alterations being made to them. Close to Stock appearance but feature filled and very fast. Version 7 is in development now and two of the polled ROMS are in fact from this development.
There have been two Release Candidates which are considered 'stable', and there are ongoing 'Nightly' builds, (experimental), but which are really just a daily evolution of the development. As it stands the latest Nightly builds are very stable, very fast and well worth trying.
I am on this one:
http://forum.xda-developers.com/showthread.php?t=968396
Modified GRI40 (2.3.3 Gingerbread) ROM*
Rooted, De-odexed, Busybox, Apps2SD, Cache2SD, ZipAligned, Disabled Stock Recovery
THE BEST ROOM EVER ! No WONK !
m_mitashki said:
I am on this one:
http://forum.xda-developers.com/showthread.php?t=968396
Modified GRI40 (2.3.3 Gingerbread) ROM*
Rooted, De-odexed, Busybox, Apps2SD, Cache2SD, ZipAligned, Disabled Stock Recovery
THE BEST ROOM EVER ! No WONK !
Click to expand...
Click to collapse
Trackball wake?
rzak said:
Trackball wake?
Click to expand...
Click to collapse
No trackball wake on any Gingerbread ROMs derived from stock. No modification has been found to enable it.
On the other hand, they don't suffer from wonks like CM7 and any CM7-based ROM.
I was loving stock gingerbread but switched over to cm7 after missing trackball wake
MIUI gets Gingerbread on Friday, that will be my choice.
I am on pure googlemod now!
But don't think just that i chose a ROM that nobody voted for would leave this POLL ad absurdum
It seems that the base of that ROM is CM7-NIGHTLY, which is the thing to go for if you want more speed in the ROM with a custom kernel (otherwise no camera).
Because i wanted the stock GB style i firstly chose GEOs stock deodexed one, but switched after i got the mentioned camera probs.
Now, with redstars custom kernel it is the fastest ROM i have ever used on my N1 (42 Mflops in Linpack)
Unfortunately it is still miles away from this insane ROM for the HD2:
http://forum.xda-developers.com/showthread.php?t=918899
You can't imagine how fast and stable that ROM is, really!
Since it is open source the N1 DEVs could look into the code couldn't they?
sense or nothing
I am on the Geo build but I am waiting for a Sense UI gingerbread release. I am following this thread http://forum.xda-developers.com/showthread.php?t=995445 but hoping Evil D can bring his magic to a GingerSense build
I've been using CM7 RC 2 after having been using enom's roms for froyo. It is pretty damn stable and lets you use trackball wake which lots of gingerbread roms don't support.
If we have CM7 and kernels for 2.3, and leaks of 2.3 from the i9000 and are able to use gingerbread base from nexus s ( think thats what cm7 uses? i cant remember...so if its wrong just insert name of correct phone back there), why is it that we havnt seen anything other than Cyanogen mod and MIUI (which doesnt even count cause its still just the CM7 base) on the 2.3 homefront? I am by no means complaining, just kind of confused. I would think that devs would be chomping at the bit to get their hands on 2.3 for their phones and start their rom modding magic. Anyone have some insight on this other than some sort of sarcastic remark or derogatory comment? lol
we only have the aosp source. and with that why port a basic aosp rom if you can have cyanogen? also there is miui. these are probably the most requested roms on any android version on any phone. an m9 port would be nice but i think the devs that can make the aosp ports better are part of these two projects. so rather than waisting time porting aosp and doing something original and asking the cm7 guys how they fixed this or that they are helping the cm7 and miui projects. also there are still problems and limitations with cm vs samsung. cm7 cant use the camera to it's full abilities. also samsung music player supports more codecs. plus the samsung roms are easier to port allowing time to work on features and tweeks. the reason the i9000 gingerbread hasnt bee built into a captivate rom is that without kernel source the roms would not be as functional as a 2.2.1 port or even cm7 because they would have problems reorienting the sensor mapping and remapping the headset. when samsung source drops there will be much more gingerbread roms and when cm7 is official there will be spinoffs
No source, no kernel, no ROM.
Sent from my Captivate
Let me start by saying Thank you to any developer making these things possible. I'm enjoying my phone more then before!
We get used to take fast pictures on our phone's... For every little nonsense...
It's a thing we expect on our phones we buy these day's.
I am having issues with CM7 to get the camera working and i saw somewhere they have removed the camera from their rom.
Now, Froyo has the cam working but the speed of my phone is very slow with Froyo. I like CM7 for it's simplicity and speed and ofc it's way better then that crappy stock rom that come's with the X8.
Now for my questions;
Why did Cyanogenmod remove support for the camera?
Why does it work in Froyo and not in Cyanogen?
And, if possible, could i speed up Froyo by overclocking or tweaks?
Froyo cant run some of my app's like swiftkey x for example...
Do i have to make a choice between speed/camera?
Thank you!
(sorry for bad grammar, English isn't my first language .)
Why did Cyanogenmod remove support for the camera?
The CyanogenMod by FreeXperiaTeam is being built from sources, which means they are writting all drivers from nothing, not just modifying them from some other ROMs. As Sony Erricson didnt gave FXP camera drivers so they couldnt finish up that ROM. They also droped a support for our X8 as well as for X10 mini/pro because of their old hardwer.
Why does it work in Froyo and not in Cyanogen?
Froyo that our X8 has is also custom ROM based on CyanogenMod but version 6. For a long time we hadnt had working camera on Gingerbread based ROMs. The thing is developers used patched Stock 2.1 drivers in Froyo and that wasnt possible until our great dev Doixanh managed to patch that drivers to work on 2.3 (Gignerbread) as well.
And, if possible, could i speed up Froyo by overclocking or tweaks?
Of course you can. But I would sugest you to install GingerDX by Doixanh. It is fully working and really smooth CM7 ROM and it will even run on stock kernel.
Froyo cant run some of my app's like swiftkey x for example...
Probably because they are not compatible. Using older versions might solve that problem.
Do i have to make a choice between speed/camera?
GingerDX.
Godra said:
Why did Cyanogenmod remove support for the camera?
The CyanogenMod by FreeXperiaTeam is being built from sources, which means they are writting all drivers from nothing, not just modifying them from some other ROMs. As Sony Erricson didnt gave FXP camera drivers so they couldnt finish up that ROM. They also droped a support for our X8 as well as for X10 mini/pro because of their old hardwer.
Why does it work in Froyo and not in Cyanogen?
Froyo that our X8 has is also custom ROM based on CyanogenMod but version 6. For a long time we hadnt had working camera on Gingerbread based ROMs. The thing is developers used patched Stock 2.1 drivers in Froyo and that wasnt possible until our great dev Doixanh managed to patch that drivers to work on 2.3 (Gignerbread) as well.
And, if possible, could i speed up Froyo by overclocking or tweaks?
Of course you can. But I would sugest you to install GingerDX by Doixanh. It is fully working and really smooth CM7 ROM and it will even run on stock kernel.
Froyo cant run some of my app's like swiftkey x for example...
Probably because they are not compatible. Using older versions might solve that problem.
Do i have to make a choice between speed/camera?
GingerDX.
Click to expand...
Click to collapse
Thank you, sir!
I've just installed GingerDx v022-update.zip as a custom zip over CM7. Camera has small problems but that isnt a big issue. Menu is fast enough.
Even swiftkey is working on Ginger while i got massive error's using it with Froyo.
I think ill stick to GingerDx. Thanks for the info!