yashsingh1/xdaforums huggingface dataset:
[Android General] jeagoss:
First, I have to agree here. Cyanogen is quite pretty. We tell him all of the time.

Second, before this feature was put in CM, how was the feature distributed? This was done through 3rd party kernels was it not? Breaking compatibility would require us to block usage of 3rd party kernels in CM. We don't do that. What we did do is alter the interface to work across multiple devices. On top of that, we made it so all of our control programs turn off when a 3rd party kernel is detected. This allows for Ezekeels paid app in the market to control the 3rd party kernel.

You say we broke compatibility. We made good effort to stay out of the way of 3rd parties. Kernel developers can implement whatever they want and distribute that kernel to be used on a phone. We don't include speed tweaks or overclocking by default in our kernel. Other kernel developers do. Are we breaking compatibility and causing fragmentation by not doing so?

In the end, we stay completely out of the way of 3rd parties. This is done by decision and design. This situation has highlighted something though. We cannot take 3rd party work anymore. It causes problems.

It is rather sad because this is how CM started. It is our roots. But we can't stick to our roots anymore because we've grown. We can't just take an implementation and stick into our code unchanged. We have to adapt code for more than one device. And this is where the problems lies.

As stated before, we just aren't going to take 3rd party work. Everything will have to go through gerrit so changes that are being made can be discussed. People will know why, from the beginning, changes are being made.
[Android General] Entropy512:
You are using different definitions of fragmentation and unification.

CM's goal - Unified standards that go across multiple devices. e.g. effort is put in to trying to make CM behave the same on Device A from manufacturer Y as it does on Device B from Manufacturer Z.

Your desire for CM - CM behaves the same as Firmware Q on Device A from Manufacturer Y, regardless of any other device. Your definition of unification can't be achieved without fragmentation under CM's definition of the term.

Achieving CM's goal often requires breaking away from device-specific conventions. See, for example, the mount point for the external SD card on Samsung devices. /sdcard/external_sd is NOT a standard way of doing things, so CM doesn't do it that way. Yes, it leads to user whining that CM isn't behaving like their stock firmware (and by their definition is now "fragmented") - but it now IS behaving consistently across multiple devices (unified by CM's definition). (I freely admit that due to lack of time, the GT-N7000 is not yet consistent with other CM devices in this regard, I still need to do all of the internal/external swap work that codeworkx did on I9100/I777. In fact I'll add that to known issues now.)

Edit: Another example, which I know franco will run into if he tries to enable CM9 compatibility on the Note - Samsung added their own broken janky MTP implementation to their ICS kernels. This implementation doesn't work with CM9, but enabling the standard MTP gadget implementation does. So CM9 did that, even though it means that without major hacks involving module loading, it means that a single binary kernel can't target both CM9 and Touchwizz firmwares. No, we won't be changing this, because the MTP implementation we are using is the Android standard one (which basically works with everything from multiple manufacturers EXCEPT for Samsung Touchwizz firmwares), and the fact that moving back to it breaks Touchwizz firmwares doesn't affect us at all. If this bothers you, yell at Samsung, they're the ones who broke that interface.
[Android General] Lento10:
Don't let your ego talk, that's what's wrong with the cm team. Big Egos just like Apple and Microsoft
[Android General] will2live:
+1 to that. Over time it sure as heck seems everyone need to cave to the mighty CM group on what THEY think is best for the Android community. Pass
[Android General] jeagoss:
This is where we are putting egos aside and saying we can no longer please everyone. Due to this, we are now requiring all work to go through and get discussed on gerrit.

This decision puts more eyes on things going into CM and allows for greater discussion. This requirement will prevent situations like this in the future.
[Android General] franciscofranco:
Yes its sad we are all shedding tears of how sad this is and we are the bad guys because we "made" you decide not including more 3rd party work.

Cut the crap. This is simple:

Y kernel and X kernel. Y has Ezekeel implementation and X has CM-hacked implementation.

User J has X kernel and he is able to use the GUI interface on CM Rom Control app, and he is happy, his device looks lots better.

User J wants to try Y kernel so he flashes it. When he boots he looks at the screen and its disgusted by stock colors so he proceeds to Rom Control and thinks how awesome the screen is going to look. But ups, the previous Color interface doesn't work. "What? The Y kernel developer said in the changelog that he added Color Control. Why the **** doesn't this work anymore?". User J goes to the Y kernel OP and reads that he needs to enter linux terminal commands to change the colors. "The **** he thinks, I don't know linux terminal commands.". Only option he has is to either buy the OP app, use terminal commands or go back to X kernel. He doesn't want to pay for an app because he has no credit card or money for that, and he doesn't want to go back to X kernel because it's slow as a turtle. He doesn't want to learn terminal commands because he is 60 years old and doesn't want to wreck his device by mistake. No problem he thinks, "I'm going to install another rom that is compatible with the Y kernel.".

The Color interface is the same on both ends, but creates this unnecessary mess.

See where this goes? It doesn't benefit CM, the kernel developer, nor the community.

How hard is this to understand once and for all?
[Android General] TheDudeOfLife:
Heybro, lemme know when you get that C&D from ValveSoftware.

Since we're, you know, raising awareness and all that.

You're Welcome.
[Android General] ingenious247:
Forgive my ignorance, but isn't that what Android is?

"Stuff on top" would be Sense UI, TouchWiz, etc, right?

So what is essentially the benefit of coding using CM's standards?
[Android General] cyanogen:
Honestly, if you didn't like the way we were doing something and it matters that much to you, you could have just posted a patch on CM Gerrit instead of doing all this backchannel nonsense. That way, we could just evaluate the issues in a public forum based purely on technical merit.
[Android General] franciscofranco:
Explain to me why would any of the affected devs provide a patch to Gerrit fixing something YOU broke after we gave you enough feedback and real solutions to the problem? So Ezekeel coded the interface, took the time fixing his bugs and user support, CM implements it, breaks what has been said to break, then we contact you, get promises that will be fixed and in the end we're the bastards that had to provide the patch to fix it? Awesome.
[Android General] ingenious247:
I do agree with this, regardless of any other comments.

However I thought the OP said he tried that route first (private communication) and was basically stonewalled?
[Android General] ellesshoo:
I understand what you're saying but this user in your example has also managed to install ADB/fastboot/Android SDK/potentially device drivers, boot into their bootloader, figure out commands to unlock said bootloader, likely flash a new custom recovery, download CM (finds only the nightly builds in the case of CM9), boots into recovery and flash CM9, use CM9 and decides there's still something small missing, decides he needs a new kernel, chooses one of many kernels from one of many developers who as far as he can tell is just some random dude coding things alone, flash this kernel, and then finds out he may need to download that dev's special little app which happens to cost $3.99 but he also happens to not have a credit card or ANY form of payment, and then decides it's some great outrage that at WORST he has to punch in some terminal command to achieve the desired result.

I have trouble picturing someone like this existing.

But some people here would prefer CM break compatibility across many different devices and waste time grinding away at solutions for this lone "Sasquatch"? Wow
[Android General] cybik:
So let me get this straight.

The project takes some GPL code (and keeps it GPL'd so people can still take it back), use it and improve it, makes it "neutral" in order to make it usable on many devices (and STILL keep the code open), and CM gets blamed for it?
[Android General] morfic:
Interface B didn't exist and the standard does not exist, Interface B was created new and has or has not been used on further devices after B was created when Interface

B wasn't needed

as Interface A could have been adopted and then used on all supported devices.

Don't take an interface, change it, spread it, then go and confuse the situation by saying "Well, it would affect many devices if we changted it for 'yours' only", the issue is to not change it before calling it a standard across many devices.

What this discussion is missing is that the patches could have existed on multiple devices before CM adopted it and changed it, so the idea that changing it somehow leads to unification is at best....funny.

To get back to your post though: yes, the rom could check which interface exists and use either detected one fairly easy.

The rom could even detect installed applications and disable GUI interfaces if the app covers the same functionality, further avoiding clashes, considering apps for those patches existed before the rom controls.
[Android General] cyanogen:
Perhaps your business model needs refined?

I also suppose that a one-line change to your app could also have accommodated for our changes. It would probably be profitable for you.

What we promised is that we would look more closely into the issue. We did. We actually created some new internal policies because of the incident. We changed our userspace to accommodate for the existence of your tools and custom kernel. You didn't want to work with us at all on coming up with something that everyone mutually agreed upon, but rather insist that it's your way or the highway. Now the drama just keeps continuing, users are left with an inferior solution on both sides, and you accuse us of trying to destroy a community that we helped create?

I call BS.
[Android General] chadouming:
Just want to remember you that most of the devices are plug&play now and taht numerous solution exist to root and install custom rom simply. Android is more and more made n00b friendly. Most of the people don't care about the developement now and just want something working. So they don't want to learn command line to make it work. This "picture" happen probably more often than you can think.

This said, i doubt *****ing each other will bring anything good. Try to respect each other and also saw their point of view. Also, when you don't know what you are talking about, try to not post here as it's useless and i bet people want to have this sorted out soon.

XDA is now the kindergarten of developement and it make me sad.
[Android General] franciscofranco:
One line? You understand that both interfaces are different in how they interact with the colors? I guess you don't even know what you're talking about in the first place. Go check both interfaces first before calling out BS or "one line change". This is not about apps, it's about the community in its whole and how best to serve it.
[Android General] zelendel:
OK guys as we have seen this is not gonna be resolved in this thread. It is just becoming a blame game and not serving a purpose. Anything more should be done by PM.

Thread closed
[Nexus One General] loplachen:
Malfunction " x " appears on the screen !! help me what is going on
[Nexus One General] CrustyMcLovin:
Haha... you'll need more information than that if you want real help.

Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.
[Nexus One General] soloviyko:
Did you flash any ROM if so, did you clean your Dalvic+REgular Cache:cool:
[Nexus One General] dpunx:
If you don't have an Recovery:

- Connect your Micro SD on PC

- Download and insert on SD the stock ROM of your Nexus One

- Power ON your Nexus with Volume Down Pressed.

- Autmotically Restore Nexus (You should say Yes xD)

At this time, you decide if you want to be root and install other ROM
[Nexus One General] GuestX0019:
you better just list your setup info before doing anything

locked/unlocked bootloader

rooted/unrooted

which recovery are you using

what rom are you running stock/custom

what were you doing when this happened

a couple safe things you can do in meantime is to pull battery and reinsert and power on

if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery

the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way

if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked

once you get into recovery do a nandroid if you are rooted

and copy it to pc as a secondary backup

it is possible you may need to try the passimg method in wiki

http://xdaforums.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus

also to do fastboot commands you need usb debugging selected on phone--hope it is
[Nexus One General] stafan:
Hello, i have a similar problem with my n1

the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)

i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X

the phone is rooted

blackrose / hboot 7.35.5017

radio 5.12.00.08

recovery was ext4

i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.

1.)

i tryed to install a new recovery image ->

recovery-clockwork-5.0.2.0-passion &

recovery-RA-passion-v2.2.1

(still get stuck at the X if i try to go to recovery mode)

2.)

i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/

(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)

i also tryed:

3.)

erased boot

flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)

4.)

erased cache

erased userdata

started again with 1.)

5.)

got frustrated and erased system -.-

any ideas?
[Nexus One General] benzking:
study it ,thank you

study it ,thank you
[Nexus One General] stafan:
Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.

Send from my awesome SE K800i ;)
[Nexus One General] GuestX0019:
not sure why you are flashing boot images

do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard

are you flashing thru fastboot in command window

did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids

pwr/vol-/trackball same time, may take 20-30 seconds

if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope

open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:

cd/

cd/ android/android-sdk-windows/tools for me

then on same line type

fastboot devices (it should show your phone H#)

fastboot erase system

fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)

I would use amonra you listed above and check the md5 if possible

hopefully the recovery will flash

if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.

a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
[Nexus One General] stafan:
thank you very much

i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.

Thanks a lot!
[Nexus One General] GuestX0019:
Glad that you got it :)
[Android Apps and Games] pressytcn:
I been looking everywhere for an app that can record video while playing music and record the sound to the video as I record

Is there anything like that out there?
[Android Apps and Games] xBlackDroid:
Screen cast Video recorder

Sent from SGSII//CM9 >>xBlackDroid<<
[Android Apps and Games] pressytcn:
Thanks only it requires root and I'm not sure I will root my one x yet but I will try it out on my Inc s

just checked it out it only records my screen i need somthing that i can use for my camera that allows sound/music to be recorded into the video instead of the sound from the mic like recording af music video without having to overdubb the sound after
[Android Apps and Games] willfck4beer:
SVR PRO and also maybe light but the light has ads in the notification bar so I uninstalled.

SVR PRO works great (Secret Video Recorder).

You can even play youtube video on screen and audio whilst SVR pro records the camera and audio.

:)
[Android Apps and Games] pressytcn:
thankyou:good:
[HTC One X] Aslotproblem:
Hello,

My signal with three UK kept dropping yesterday so i thought i would try a vodafone sim card i have in my HTC one X. I inserted the htc clip to open the sim card slot but it would not open, then i noticed that my three sim card in the phone is not being read anymore.

I'm stuck with a htc one x that i cannot phone with and cannot replace the sim. I'm not sure what to do, has anyone had any problems with the sim card tray not opening?
[Galaxy S II Themes and Apps] JuanitoDog:
¿Anyone port this? Thx!!
[Galaxy S II Themes and Apps] Shomi87:
its ported already use search
[Galaxy S II Themes and Apps] JuanitoDog:
¿I find for the note not for SGSII, is valid this .apk?
[Galaxy S II Themes and Apps] rete:
It is linked several times in this thread...

http://xdaforums.com/showthread.php?p=26424171
[Galaxy S II Themes and Apps] migg1:
http://xdaforums.com/showthread.php?t=1663679
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] wiresquire:
Hi

I'm interested in this question from primarily a battery life perspective. I did some searches, but couldn't find any info on this.

I have an external bluetooth GPS module I could use. If I were to use a Galaxy Ace with bluetooth enabled, but GPS off, would this be more power efficient than using the GPS of the Ace with bluetooth off?

(Assuming all other power factors to be the same).

I guess it boils down to: Which is more efficient on the Ace; using GPS only or bluetooth only? And is it actually significant?

If there are any other aspects that should be considered, please edumacate me!

Thanks

ws
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Soumitra.5693:
Personal experience and logic says Bluetooth consumes lesser battery juice than using GPS
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] eduardito:
Yes you are right wit an expternal GPS you will save battery, I use ana pplication called BlueGPS for pair the GPS and connect with Copilot
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] wiresquire:
Thanks for the replies.

Now I've bought an Ace and had a chance to play a little bit, there's one thing that confuses me.

Once I connect the external GPS via bluetooth, and select it as the GPS source, I still have to enable the internal GPS for GPS to function.

(I can test that GPS is working via the external GPS by putting the bluetooth GPS unit on my window sill, and have my Ace inside where it can't get a GPS lock from inside via internal GPS).

So, doesn't this mean that the Ace is using battery for the internal GPS as well as bluetooth??
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Soumitra.5693:
I guess what's actually happening is that when u "enable the internal GPS", you're basically enabling the phone to use the GPS source you initially selected in the location settings, i.e. the external one.

So all in all, when you have the bluetooth on without switching on GPS, bluetooth is idling, and when you enable GPS, it starts interacting with the bluetooth GPS.

cheers :)
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] jancici:
you vowebt

hi

I am using external bluetooth GPS too.

I did flash my phone two days ago and find out that I don't need another app to use external GPS.

My phone is flashed with CM10-nightly.

Problem is that after each time when I want to used external GPS I need to unpari and then pair that bluetooth device.

example:

a) switch on bluetooth, and pair external GPS device

b) choose that new device in GPS source

c) switch on GPS

perfekt I can use maps ...

after while I switch off GPS and bluetooth and device

then

d) switch on bluetooth, device is already paired

e) switch GPS, external source is already choose

BUT phone is not getting any data from external GPS device

f) I have to go to bluetooth devices and unpair and then pair external GPS device

I think it is a bug, what do you think?
[Samsung Galaxy Nexus] mitchell4500:
Iv been complaining about my battery life on various threads (its 7hrs Max... Minimal use). I keep my brightness at 60% otherwise I get yellow tints.

Ive been told to install a custom rom to hopefully save battery and adjust the colors to remove that yellow tints.

Im using Apex right now. I dont see an option to adjust colors.

Suggestions?
[Samsung Galaxy Nexus] tanner4137:
Some AOSP ROMs and CM9 have the option. Hope that helps!
[Samsung Galaxy Nexus] nodstuff:
I think every rom has them at this stage.

If you use franco kernel the controls for the colours for his kernel are in his app.
[Samsung Galaxy Nexus] mitchell4500:
Thanks. I saw the GlaDOS kernel (love the name). And I was going to try that with its app but its not free.

Ill try your suggestions. I was just curious if any one rom over others had better battery life then expected.
[Samsung Galaxy Nexus] nodstuff:
Franco's app isn't free either but its only like 2 dollars. That's nothing.

Some rooms have colour control built in like cm9
[HTC Incredible S] Mart3n1uk:
http://www.androidpolice.com/2012/0...o-get-android-4-0-ice-cream-sandwich-updates/

HTC Incredible S: June-July :D
[HTC Incredible S] owendesira:
This will be the rebirth of IncS ROMS :D.
[HTC Incredible S] djbenny1:
this is old news, sorry!
[HTC Incredible S] Amar-S:
I have lost all hopes in HTC now...they just want to release new phones every month!
[HTC Incredible S] aerosmith:
I think it is because lot of people want new phones quite often! If there are no buyers then there would not be any new phones.

I think we should be fortunate enough to get an ICS release for IncS. Not many manufacturers provide this kind of support to their 2 old mobile devices.
[HTC Incredible S] Amar-S:
Yea...they should release it or am going to sell my phone now
[HTC Incredible S] djbenny1:
Idiot

Did HTC promise you ICS when you bought your phone?

Didn't think so.
[HTC Incredible S] dannyfranks76:
Great news :) I was starting to lose hope too and like it was pointed out above - can't wait for the new roms and ports when it does hit ;)
[HTC Incredible S] metalheadmike:
Will this for cdma desire
[HTC Incredible S] tpbklake:
No. you have posted on a thread in the Incredible S forum, not the HTC Desire forum.