CM7 source and issue

[Guest t0mm13b]

Okie,

Have a look at this issue that cropped up recently - this is in gingerbread and is preventing me from moving forward from froyo to gingerbread for my day-to-day job.

What do you think are the chances of CM7 sticking up two fingers at google and re-implement this fix into gingerbread for ALL devices?

As CM7 broke my apps, I had to ditch it and revert back to SS5 Gen2 in order to concentrate on continue working on it.

[Guest Victor von Zeppelin]

Okie,

Have a look at this issue that cropped up recently - this is in gingerbread and is preventing me from moving forward from froyo to gingerbread for my day-to-day job.

What do you think are the chances of CM7 sticking up two fingers at google and re-implement this fix into gingerbread for ALL devices?

As CM7 broke my apps, I had to ditch it and revert back to SS5 Gen2 in order to concentrate on continue working on it.

I suppose it'd either be "IF you want it, do it yourself" sort of thing, like most of CM, or, if you get enough support, someone with more time may try it. But I dunno. Anyway good sir, you know there are far better places to ask this! And you spend more time on IRC with better qualified people.

[Guest t0mm13b]

I suppose it'd either be "IF you want it, do it yourself" sort of thing, like most of CM, or, if you get enough support, someone with more time may try it. But I dunno. Anyway good sir, you know there are far better places to ask this! And you spend more time on IRC with better qualified people.

Okie... just thought I'd give it a shot by posting here to hear others opinions despite some may not even bother to read on this forum :P

[Guest Victor von Zeppelin]

Okie... just thought I'd give it a shot by posting here to hear others opinions despite some may not even bother to read on this forum :P

Ah, I didn't want to put you off, it's not like i'm the voice of the forum, man :rolleyes:

I suggest looking over the CM7 thread, and seeing any unrecognised members who are making the best technical contribution, and maybe PM-ing them?

[Guest ThrashMan]

Have Google refused to correct this issue?

[Guest t0mm13b]

Have Google refused to correct this issue?

As it stands, yes, google are refusing to correct it.... :P

[Guest Grain]

Have a look at this issue that cropped up recently - this is in gingerbread and is preventing me from moving forward from froyo to gingerbread for my day-to-day job.

What apps does this break/what capabilities are we speaking about here specifically?

[Guest t0mm13b]

What apps does this break/what capabilities are we speaking about here specifically?

MODIFY_TELEPHONY_STATE is a permission that allows those specializing in telephony features to access certain parts of it for low level stuff pertaining to intercepting calls and sms/mms.

Really, I do think that CM7 as a whole - should break from google's direction, but at the same time, share the sources, and even better, any issues that are flagged in Google's issues relating to the AOSP sources, should be fixed up in CM7 code base and say to those who have been affected by the stock rom coming from google "hey, switch over to CM7, that is fixed in there but Google are too slow to respond to fix the issue".

Ideally that would be nice to have... if Google don't bother to fix whatever issues in their AOSP, take for example apart from my issue, SMS Bug, this has been around for about a year - where the SMS is being sent to some random recipient, and still not dealt with AFAIK/IIRC - Why don't CM7 say, "Ok, we'll fix it." and give it a good enough reason to switch from stock to CM7 :P

Still, I could be dreaming here yeah?

[Guest ThrashMan]

I'm not convinced it's something that needs "fixing". Why would I want apps intercepting calls/sms/mms? What sort of legitimate apps need/want to do that?

[Guest Grain]

MODIFY_TELEPHONY_STATE is a permission that allows those specializing in telephony features to access certain parts of it for low level stuff pertaining to intercepting calls and sms/mms.

In the AOSP changeset that disabled that permission it is said that Google is working on proper public telephone APIs. I can understand that reasoning. I guess CM should just keep the permission in order to stay backwards compatible. CM coming up with own APIs will not achieve anything since CM market share is very small. This would only increase fragmentation.

Ideally that would be nice to have... if Google don't bother to fix whatever issues in their AOSP, take for example apart from my issue, SMS Bug, this has been around for about a year - where the SMS is being sent to some random recipient, and still not dealt with AFAIK/IIRC - Why don't CM7 say, "Ok, we'll fix it." and give it a good enough reason to switch from stock to CM7 :rolleyes:

There's many things CM could do certainly. Look at the changelogs though - CM people are mostly caught up in small fixes, often in own code, theming stuff, and reverting own commits that turned out to be buggy. I don't know how many Java pros are in the CM team but it looks like they are not quite abundant. The SMS bug was not easy to find and for a long time it was not even clear that it's actually a bug and not only an erroneous bug report.

From a Blade point of view, in any case, I'd say one of the most annoying things in CM7 is the abysmal performance of ADW. Again, a problem that is specific to CM7, and again a problem that no one in CM7 seems to be working on :P .

@ThrashMan: For example WheresMyDroid.

Edited May 20, 2011 by Grain

[Guest t0mm13b]

In the AOSP changeset that disabled that permission it is said that Google is working on proper public telephone APIs. I can understand that reasoning. I guess CM should just keep the permission in order to stay backwards compatible. CM coming up with own APIs will not achieve anything since CM market share is very small. This would only increase fragmentation.

There's many things CM could do certainly. Look at the changelogs though - CM people are mostly caught up in small fixes, often in own code, theming stuff, and reverting own commits that turned out to be buggy. I don't know how many Java pros are in the CM team but it looks like they are not quite abundant. The SMS bug was not easy to find and for a long time it was not even clear that it's actually a bug and not only an erroneous bug report.

From a Blade point of view, in any case, I'd say one of the most annoying things in CM7 is the abysmal performance of ADW. Again, a problem that is specific to CM7, and again a problem that no one in CM7 seems to be working on :P .

@ThrashMan: For example WheresMyDroid.

@Grain: this is the app that I am working for in my day-to-day job here. This app which I've spent a good deal of time, is not a malicious or malware app, more for parents and teenagers, imagine my disappointment and frustration at running it under CM7 which broke literally.... hence the thread topic :rolleyes: