Edited by bassmadrigal, 23 June 2012 - 09:24 AM.
Excessive use of exclamation points extended beyond the end of a 1280 screen resolution
Welcome to CyanogenMod
 |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
Nexus One And Cm9
Started by tinye99, Jun 23 2012 05:21 AM
6 replies to this topic
#1
tinye99
-
- Members
- 33 posts
Posted 23 June 2012 - 05:21 AM
come on cyanogen you and your developers have got to give us nexus one users a official cm9 build i mean come on you gave the g1 official cm6 froyo build wich i used for along time on my g1 before i got my nexus one and if you can give the original android phone froyo when google stoped updateing it after android 1.6 you should be able to give the nexus one a offiicial cm9 build of ics!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! many of us still use the nexus one and im 12 and i rooted my phone the first day i got just to install your cm7 rom i will test all of the beta builds of cm9 for the nexus one if you relese it
#2
bassmadrigal
-
- Administrators
-
- 8659 posts
Posted 23 June 2012 - 09:23 AM
Wow... way to show some respect for the people who gave you CyanogenMod. The developers have been working on getting ICS on the Nexus One, but they weren't able to do so without breaking the ICS Compatibility Test Suite. And that isn't a compromise they are willing to take.
Per https://plus.google....sts/RiRXpWwHRX7
And the reason why they aren't willing to compromise the full compatibility of ICS...
All this information was already posted in the Nightlies thread for the N1, and on the CyanogenMod G+ page.
If you want to try CM9 on the Nexus One, currently, your only options are unofficial builds on xda. This isn't about to change anytime soon, and trying to give the CM team a guilt trip on how long they supported the G1 is NOT a good way to show your appreciation for what they have accomplished. If they can eventually get a build without compromising the CyanogenMod name and support, then it will be released. Until then, please keep your pleading, guilt trips, and comparisons to yourself. The CM team is well aware of how people feel when their phones aren't supported by the latest release.
And I edited your post to get rid of your massive amount of exclamation points. Did there really need to be 113 exclamation points so you could get your point across (which causes a scrollbar on my notebook)?
Per https://plus.google....sts/RiRXpWwHRX7
Quote
# Nexus One: For the time being, the N1 will not be supported. We can get it to build/boot/run, but the hacks required break Google's CTS, so until that is rectified, you won't see any release build with CM's official stamp of approval.
And the reason why they aren't willing to compromise the full compatibility of ICS...
Quote
To piggy back on our comment about the N1 and CTS, Ricardo describes why we don't just shrug off that requirement.
Because it opened a can of worms that can’t be closed again. Getting it to work needed some very ugly workarounds that directly go against Google’s compatibility document for ICS. An app developer targeting ICS as a minimal version for his apps has the right to expect some functionality to be guaranteed on a device that claims to be ICS, that wasn’t (and isn’t) true for ICS builds with these hacks. That’s one the main reasons CM9 does not officially include a bunch of devices that are “working.”
...and some users understand that, but a lot don’t, and they’ll submit error reports on those apps, or they’ll rate it badly at the Play store. This is not a hypothetical scenario, it has happened whether we like it or not, asked for it or not, CM’s userbase is large enough to matter, even if you don’t count derivatives. We have a responsibility not to cause that kind of grief to app developers and we did. With all the mostly bullshit talk about fragmentation, we actively contributed to a break in the platform, no matter how small. That’s not a good thing :X People SHOULD know these builds contain hacks, but you’ve surely realized by now that they don’t.
Because it opened a can of worms that can’t be closed again. Getting it to work needed some very ugly workarounds that directly go against Google’s compatibility document for ICS. An app developer targeting ICS as a minimal version for his apps has the right to expect some functionality to be guaranteed on a device that claims to be ICS, that wasn’t (and isn’t) true for ICS builds with these hacks. That’s one the main reasons CM9 does not officially include a bunch of devices that are “working.”
...and some users understand that, but a lot don’t, and they’ll submit error reports on those apps, or they’ll rate it badly at the Play store. This is not a hypothetical scenario, it has happened whether we like it or not, asked for it or not, CM’s userbase is large enough to matter, even if you don’t count derivatives. We have a responsibility not to cause that kind of grief to app developers and we did. With all the mostly bullshit talk about fragmentation, we actively contributed to a break in the platform, no matter how small. That’s not a good thing :X People SHOULD know these builds contain hacks, but you’ve surely realized by now that they don’t.
All this information was already posted in the Nightlies thread for the N1, and on the CyanogenMod G+ page.
If you want to try CM9 on the Nexus One, currently, your only options are unofficial builds on xda. This isn't about to change anytime soon, and trying to give the CM team a guilt trip on how long they supported the G1 is NOT a good way to show your appreciation for what they have accomplished. If they can eventually get a build without compromising the CyanogenMod name and support, then it will be released. Until then, please keep your pleading, guilt trips, and comparisons to yourself. The CM team is well aware of how people feel when their phones aren't supported by the latest release.
And I edited your post to get rid of your massive amount of exclamation points. Did there really need to be 113 exclamation points so you could get your point across (which causes a scrollbar on my notebook)?
#3
tinye99
-
- Members
- 33 posts
Posted 23 June 2012 - 03:58 PM
what have the developers had to do that breaks ics compatibility
#4
Baloo Uriza
-
- Members
- 7 posts
Posted 23 June 2012 - 06:19 PM
tinye99, on 23 June 2012 - 05:21 AM, said:
come on cyanogen you and your developers have got to give us nexus one users a official cm9 build i mean come on you gave the g1 official cm6 froyo build wich i used for along time on my g1 before i got my nexus one and if you can give the original android phone froyo when google stoped updateing it after android 1.6 you should be able to give the nexus one a offiicial cm9 build of ics!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! many of us still use the nexus one and im 12 and i rooted my phone the first day i got just to install your cm7 rom i will test all of the beta builds of cm9 for the nexus one if you relese it
Wow, the butthurt is strong with this one. I have an idea: How about you get some programming skills and help make it happen? You're dealing with volunteers.
#5
bassmadrigal
-
- Administrators
-
- 8659 posts
Posted 23 June 2012 - 11:47 PM
tinye99, on 23 June 2012 - 03:58 PM, said:
what have the developers had to do that breaks ics compatibility
As far as I know, they haven't said. The only information I know, I posted above.
#6
thnld
-
- Members
- 1 posts
Posted 04 July 2012 - 02:24 PM
I did some studying in the ICS Compatibility Definition document.
Maybe the problem is that the data and cache partitions are too small on the Nexus One (for example, data has to be at least 350mb, but is 220mb in the unofficial ports)?
If this is true, maybe it could be solved by moving these partitions to the sdcard. It's just a wild guess...
Unfortunatly, I don't have the time and skills to try to solve this myself.
Maybe the problem is that the data and cache partitions are too small on the Nexus One (for example, data has to be at least 350mb, but is 220mb in the unofficial ports)?
If this is true, maybe it could be solved by moving these partitions to the sdcard. It's just a wild guess...
Unfortunatly, I don't have the time and skills to try to solve this myself.
#7
tinye99
-
- Members
- 33 posts
Posted 05 July 2012 - 01:21 AM
System and data and cache only needs system 220 cache 60 and data what ever is left even in official cm9 my friend has it on his nexus s and system partition is used is only about 220 mb
