FORUMS

NVIDIA Launches SHIELD Android TV at Google I/O

Since Android TV was announced at Google I/O 2014, there has been very little activity … more

Devs Beware – Automatic Backup Privacy Risks

One new feature of “Android M” (speculation on potential names welcomed … more

Android M to Bring New App Drawer

It has now been seen that Android M will receive a new app drawer as part of the stock … more

Which IO Announcement Are You Most Excited About?

The keynote we had all been waiting for has just ended and it’s time to enjoy … more

[ROM] [UNOFFICIAL] [4.4.4] [CANCRO] [BETA] AOSB V1.3.7 [BUILD1]

Thanks Meter: 2,300
 
Post Reply Subscribe to Thread Email Thread
11th September 2014, 07:57 AM |#21  
OP Recognized Contributor
Flag Mumbai
Thanks Meter: 2,300
 
Donate to Me
More
Quote:
Originally Posted by willster273

Can you update the cm base to the latest build (31/08)? I'm not getting any working sensors but I think the latest cm build rectifies this.

Thanks.

Sent from my MI 3W using XDA Free mobile app

Well it is merged with that tree... But thenprob still seems to happen ... Last me see what I can do
The Following 3 Users Say Thank You to RVR For This Useful Post: [ View ]
 
 
11th September 2014, 04:29 PM |#22  
Member
Flag Manchester
Thanks Meter: 18
 
More
Quote:
Originally Posted by rutvikrvr

Well it is merged with that tree... But thenprob still seems to happen ... Last me see what I can do

Its just that the latest cm version is 08/31 which has the sensors fixes I think and the cm base version shown in settings is 08/30. Is this just an error?

Sent from my MI 3W using XDA Free mobile app
The Following 2 Users Say Thank You to Streuli273 For This Useful Post: [ View ]
13th September 2014, 04:17 PM |#23  
zelendel's Avatar
Senior Moderator / Mod. Cttee. Retired - The Dark Knight
Flag Watching from the Shadows
Thanks Meter: 14,022
 
More
Fair Warning

http://forum.xda-developers.com/show...9&postcount=57
13th September 2014, 05:15 PM |#24  
praveen7682's Avatar
Senior Member
Flag Chennai
Thanks Meter: 166
 
More
Quote:
Originally Posted by zelendel

Fair Warning

http://forum.xda-developers.com/show...9&postcount=57

This is unfair for a device which is just gaining momentum...I understand GPL but we have contacted the OEM for the source code which might take little more time...we need to relax our timeline for newer devices ...
13th September 2014, 05:18 PM |#25  
zelendel's Avatar
Senior Moderator / Mod. Cttee. Retired - The Dark Knight
Flag Watching from the Shadows
Thanks Meter: 14,022
 
More
Quote:
Originally Posted by praveen7682

This is unfair for a device which is just gaining momentum...I understand GPL but we have contacted the OEM for the source code which might take little more time...we need to relax our timeline for newer devices ...


Ill be honest this is not gonna happen. What is unfair is what the OEM is doing to you users. That is unfair. Just because they want to make some money they are willing to break the law. Sorry but that breaks more then just our GPL rules.
13th September 2014, 05:19 PM |#26  
OP Recognized Contributor
Flag Mumbai
Thanks Meter: 2,300
 
Donate to Me
More
Quote:
Originally Posted by zelendel

Ill be honest this is not gonna happen. What is unfair is what the OEM is doing to you users. That is unfair. Just because they want to make some money they are willing to break the law. Sorry but that breaks more then just our GPL rules.

If the deadline is reached ... And kernel sources still not out ...please feel free to close the thread and pull the download links
The Following User Says Thank You to RVR For This Useful Post: [ View ]
13th September 2014, 05:27 PM |#27  
praveen7682's Avatar
Senior Member
Flag Chennai
Thanks Meter: 166
 
More
Quote:
Originally Posted by zelendel

Ill be honest this is not gonna happen. What is unfair is what the OEM is doing to you users. That is unfair. Just because they want to make some money they are willing to break the law. Sorry but that breaks more then just our GPL rules.

Do we have any other alternate for this?...
13th September 2014, 05:30 PM |#28  
zelendel's Avatar
Senior Moderator / Mod. Cttee. Retired - The Dark Knight
Flag Watching from the Shadows
Thanks Meter: 14,022
 
More
Quote:
Originally Posted by praveen7682

Do we have any other alternate for this?...


There are 2 option but neither one is likely.

1. The OEM releases the kernel source
2. A Dev builds and releases an open source kernel.
18th September 2014, 08:04 PM |#29  
Junior Member
Flag Dublin
Thanks Meter: 4
 
More
mi3
Quote:
Originally Posted by zelendel

There are 2 option but neither one is likely.

1. The OEM releases the kernel source
2. A Dev builds and releases an open source kernel.

why dont you just adjust this outdated rules and make maybe a new one when its needed.
The Following 2 Users Say Thank You to KARELLAMAC For This Useful Post: [ View ]
19th September 2014, 05:17 AM |#30  
jackeagle's Avatar
XDA: ASSIST
Recognized Contributor
Flag XDA
Thanks Meter: 3,374
 
Donate to Me
More
Quote:
Originally Posted by KARELLAMAC

why dont you just adjust this outdated rules and make maybe a new one when its needed.

Actually This is not Rule it is By Law All OEM's and Developers Must mandatory Release the Kernel Source under GPL Complience and hence XDA Is strict with GPL Rules this is applicable when OEM has the Source but they dont want to release it .... you can visit below link for further info
XDA-Developers and the GPL
The Following User Says Thank You to jackeagle For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
4.4.4, aosb, cancro, mi3, rutvikrvr
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes