Develop Bugs

Developer support?

I've read a news article on Pulse that this phone won't have much developer support due to Samsung keeping some files locked out for developer support, and that Cyanogenmod won't be developing on this phone due to that.
Sent from my SGH-I747 using Tapatalk 2

I don't understand the situation fully, but it sounds like Samsung has committed to releasing the source, so I am hoping that means it will get Cyanogenmod and good dev support.
http://rootzwiki.com/news/_/article...nos-4-series-source-code-by-end-of-2012-r1203

acey_zero said:
I don't understand the situation fully, but it sounds like Samsung has committed to releasing the source, so I am hoping that means it will get Cyanogenmod and good dev support.
http://rootzwiki.com/news/_/article...nos-4-series-source-code-by-end-of-2012-r1203
Click to expand...
Click to collapse
Interesting..hate Touchwiz but it does have some nice features.
Sent from my SGH-I747 using Tapatalk 2

This might be a dumb question, I've just begun researching this but it concerns development. I'm considering jumping from my Verizon contract to AT&T for this phone, based on the virtual certainty that the Verizon version will have a locked bootloader. Are AT&T phones locked on a case by case basis, or is it already a given that this phone will release with devs able to mess with it? I don't want to play a waiting game like the S3 on Verizon despite their huge number of users.

From my understanding there will be NO cm support on any further samsung devices..But then I seen this? so who knows...lol
http://www.theandroidsoul.com/cyanogenmod-10-cm10-for-galaxy-note-2-development-starts/

wish777 said:
From my understanding there will be NO cm support on any further samsung devices..But then I seen this? so who knows...lol
http://www.theandroidsoul.com/cyanogenmod-10-cm10-for-galaxy-note-2-development-starts/
Click to expand...
Click to collapse
Pretty sure that is a port, not the actual CM team doing the work

i know cm10 is cool but i dont understand why people would want this on the note 2 since all the features that make the note 2 are TW related but thats just me.

BLOWNCO said:
i know cm10 is cool but i dont understand why people would want this on the note 2 since all the features that make the note 2 are TW related but thats just me.
Click to expand...
Click to collapse
Personally I agree, but this is xda and people will want to mod. I'll be rooting, but I doubt I'll flash any custom ROM's.

My order is in and I agree,:laugh:
UNLESS...the many features including the S Pen etc. are ported to new ROMS I don't think I'll flash...
BTW ...anyone know of a cure for ORD

gtalum said:
Personally I agree, but this is xda and people will want to mod. I'll be rooting, but I doubt I'll flash any custom ROM's.
Click to expand...
Click to collapse
oh i will be doing the same ill flash customs roms just TW ones as i want to keep the features like spen and all that jazz.
on older devices cm was awesome cause it was fast but now as the phones are more powerful then ever i dont see a need to run them. just me tho

Same. I don't think I'll be flashing any Non-TW ROM on the Note 2. I've been flashing AOKP and CM10 on the Note 1 so I've been missing the TW S-Pen features.

This is why im glad i got the N7100 model, just sayin

wish777 said:
From my understanding there will be NO cm support on any further samsung devices..But then I seen this? so who knows...lol
http://www.theandroidsoul.com/cyanogenmod-10-cm10-for-galaxy-note-2-development-starts/
Click to expand...
Click to collapse
Pretty much all I know is what I read on rootzwiki, but I thought that they were not going to drop all Samsung devices, but only the ones that used Exynos CPU's due to inadequate source or documentation or something. But then I think Samsung has committed to releasing this, so hopefully that means Cyanogenmod will not drop them anymore, but I haven't heard anything official.
links:
http://rootzwiki.com/news/_/article...veloper-support-for-exynos-based-phones-r1151
http://rootzwiki.com/news/_/article...exynos-code-or-is-this-another-pr-stunt-r1176
http://rootzwiki.com/news/_/article...nos-4-series-source-code-by-end-of-2012-r1203
---------- Post added at 01:06 AM ---------- Previous post was at 12:53 AM ----------
BLOWNCO said:
i know cm10 is cool but i dont understand why people would want this on the note 2 since all the features that make the note 2 are TW related but thats just me.
Click to expand...
Click to collapse
I have to admit a lot of the features they added do seem genuinely useful, but I still think I would give them up for Cyanogenmod.
It is my understanding (from what I have read about the Note 1, etc) that android natively supports stylus input since ICS, and so it should be able to still work in Cyanogenmod. It is just that there are very few apps that really make use of it besides the ones from Samsung, Hopefully this will improve over time though.

I am with you guys, I personally will root the device and debloat it for now... But stock rom right now seems to be very nice..lol...
We will have alot of great roms coming out either way with or without cm support. I know a couple devolpers coming here shortly and there work is awesome.

There will be plenty of support. I will be working on a few things myself once I get the device. I helped start the CM development in the original note.
And the reason why we run AOSP vs all the craptastic useless stuff Samsung adds its because I personally like vanilla Google. Samsung changes to much. Android in stock form is beautiful. Just my opinion not trying to start a flame war.
If I run stock it will be stripped down deodexed and debloated likke a mofo.
If I decode to build an device tree and attempt to build CM I will. With the open support from Samsung it won't be difficult.

I know of a few developers coming this way also we will have plenty of support I'm sure

antiochasylum said:
There will be plenty of support. I will be working on a few things myself once I get the device. I helped start the CM development in the original note.
And the reason why we run AOSP vs all the craptastic useless stuff Samsung adds its because I personally like vanilla Google. Samsung changes to much. Android in stock form is beautiful. Just my opinion not trying to start a flame war.
If I run stock it will be stripped down deodexed and debloated likke a mofo.
If I decode to build an device tree and attempt to build CM I will. With the open support from Samsung it won't be difficult.
Click to expand...
Click to collapse
Normally I agree, and my S3 i definitely agree. But this phone is built around samsungs incorporation of the s-pen and related features. If AOKP roms ignore the s-pen, theyre useless to me.. why even get this phone then?
I think the most popular roms on this phone will be stock based, debloated and feature rich roms, much like Ariel rom for the ATT Galaxy s3 out now.

BLOWNCO said:
i know cm10 is cool but i dont understand why people would want this on the note 2 since all the features that make the note 2 are TW related but thats just me.
Click to expand...
Click to collapse
Touchwiz is hideous.
Don't get me wrong, Samsung has done some great things with the multitask and S-pen, but AOSP Jellybean makes Touchwiz look like a featurephone UI from 2003.

xeper said:
Touchwiz is hideous.
Click to expand...
Click to collapse
Which aspects of touchwiz (beyond the launcher, which is easily replaced) are hideous?

theraker007 said:
Normally I agree, and my S3 i definitely agree. But this phone is built around samsungs incorporation of the s-pen and related features. If AOKP roms ignore the s-pen, theyre useless to me.. why even get this phone then?
I think the most popular roms on this phone will be stock based, debloated and feature rich roms, much like Ariel rom for the ATT Galaxy s3 out now.
Click to expand...
Click to collapse
This is exactly how I feel about it. I will root it, but I'm going to take my time about flashing a custom ROM. I want the full functionality of that stylus as designed - as an old Palm girl, this is one of the main reasons I'm getting the Note 2. That plus the excellent GPS - coming from a woefully awful Captivate GPS. I had a Garmin iQue 3600, the Palm OS GPS unit, and am frankly spoiled by that integration. If only Garmin hadn't given up like that.....

Galaxy Nexus Gets Updated GPU Binaries, To Breath Life into the Two-Year Old Phone

As always, XDA is up to some good stuff with a new release of Android now available. Some developers are finding what appears to be updated binaries for the GPU that’s inside the Galaxy Nexus. KitKat was announced last week, and surprisingly, Google decided to drop support for the Galaxy Nexus. It’s surprising because KitKat can run on devices with 256MB of RAM, which the Galaxy Nexus has a full gigabyte of RAM available. We’ve already seen numerous custom ROMs flowing out for KitKat on the Galaxy Nexus. And it’s not just for the GSM Galaxy Nexus, but also the Verizon (Toro) and Sprint (Toroplus) versions.
It appears that Texas Instruments have updated the GPU binaries for the Galaxy Nexus. Now, Google may not have known that TI was going to update it or Google may not have told TI that they had given up on the two-year old device. But either way, developers are hard at work building an updated kernel that might help solve some of the graphical issues with KitKat on the Galaxy Nexus.
If you’re one of those many people out there still rocking the Galaxy Nexus, and not wanting to give it up just yet. It looks like you might get Christmas a bit early. As the new GPU binaries should definitely help out the Galaxy Nexus. Although, if you’ve held onto it this long, you’re probably due for an upgrade, since the device was released in November 2011. Hopefully this will help people get a long a bit more until the device finally chokes.
This is another reason why we love the developer community around Android. You won’t find a developer community like this behind the iPhone or anything iOS related. Back before I started here at AH, I had a couple of devices in which the manufacturer had given up on the device, but developers had continued to support it for years. Which was quite nice.

Is it real? It would be a big deal !
Do any ROM developers confirm it yet?

arshum said:
Is it real?
Click to expand...
Click to collapse
I sure hope its real!

Haven't heard much lately on this just what hashcode said and he didn't sound too promising. One ROM developer I seen tried it but was beyond his skills
Sent from my Galaxy Nexus using Tapatalk

Nothing is impossible ...
Sent from my Galaxy Nexus using xda app-developers app

I'm still very much active on this , its true its beyond my skill but that's how I learn . I'm hands on all the way , my nexus stays with the battery cover off 50% of the time lol , so don't fret , there might be hope yet .......
Sent from my Galaxy Nexus using Tapatalk

Will they solve glitches totaly?

krialix said:
Will they solve glitches totaly?
Click to expand...
Click to collapse
No one knows that

I would like to thank everyone that is working to make this happen!

this is outdated news
http://www.xda-developers.com/andro...possibly-aid-galaxy-nexus-kitkat-development/
please read the hashcode's reply
http://forum.xda-developers.com/showpost.php?p=47160722&postcount=309
new drivers are for Jellybean and not for KitKat

Well, even if it's only for Jelly Bean, i would want that. An Update is better than no-update

Spoderman said:
Well, even if it's only for Jelly Bean, i would want that. An Update is better than no-update
Click to expand...
Click to collapse
I would prefer updated Jellybean with updated drivers and with no WiFi/GPS/connectivity issues... hope Google will release a more stable Jellybean

Spoderman said:
Well, even if it's only for Jelly Bean, i would want that. An Update is better than no-update
Click to expand...
Click to collapse
I was thinking same thing.
Even of they ARE only good for4.2/4.3 improvements, I'd love to see them incorporated

Your thoughts for future GNEX Development

Even though Galaxy Nexus is no more officialy supported by Google and stuck at Android 4.3, KitKat Roms emerged quickly and evolve rapidly - thanks to our crazy devs!!! :victory: So how you all handling this? Still at 4.3... already jumped to a 4.4 rom?
I know it took a long way for 4.3 roms to reach that point where everything works near perfect and I think that Cataclysm or SlimBean are such examples. So, some will prefer the comfort of this instead of jumping into the unknown and start dealing with bugs and the trial and error procedure???
As I write this Android 4.4.2 is rolling to newer Nexus devices, my new Nexus 7 already running this and something tells me, since none of the factory images for 4.4.1 and 4.4.2 are officialy on google's page, that another update maybe coming soon. Since our phone is not officialy supported, devs will strugle merging new code to their sources and adapting it for gnex. How do you see this evolving?
To end this, it's been 2 years after the release of GNEX and our forum still is in the top 5 list. Quite impressive if you ask me. Tell that to Google... Galaxy Nexus is a legendary phone even though it's not the sharpest out there. And I am sure its "endurance" over time, will make it even more legendary!
PS: Working on a cool Zooper Skin. Will let u know when it's out!

It will continue, but the gnex population will gradually move on. The new incomers will not likely join at the rate the existing users leave to upgrade to a new device.
If it's any indication, Nexus One and Nexus S development are still continuing and they are older than the Galaxy Nexus. At some point when newer android versions get too resource intensive (KK tried to improve the memory management) then we will start seeing users preferring to stick with an older version.

I will continue with my Galaxy nexus and I'm still very happy with it especially so because of the talented developers here at XDA. I'm currently using the 4.4 KK rom : [ROM] [UNOFFICIAL] CyanogenMod 11 for the Samsung Galaxy Nexus with gapps 20131207. This ROM is now my daily driver and I won't be going back to 4.3 :good:
Thanks for this post, I'll subscribe!

myself, I've been thinking of sticking with Cataclysm for a while. But can I ask those who already use a 4.4 rom if they noticed any signifcant improvement on battery life or multitasking?

wrong thread. sorry

itasoulas said:
Even though Galaxy Nexus is no more officialy supported by Google and stuck at Android 4.3, KitKat Roms emerged quickly and evolve rapidly - thanks to our crazy devs!!! :victory: So how you all handling this? Still at 4.3... already jumped to a 4.4 rom?
I know it took a long way for 4.3 roms to reach that point where everything works near perfect and I think that Cataclysm or SlimBean are such examples. So, some will prefer the comfort of this instead of jumping into the unknown and start dealing with bugs and the trial and error procedure???
As I write this Android 4.4.2 is rolling to newer Nexus devices, my new Nexus 7 already running this and something tells me, since none of the factory images for 4.4.1 and 4.4.2 are officialy on google's page, that another update maybe coming soon. Since our phone is not officialy supported, devs will strugle merging new code to their sources and adapting it for gnex. How do you see this evolving?
To end this, it's been 2 years after the release of GNEX and our forum still is in the top 5 list. Quite impressive if you ask me. Tell that to Google... Galaxy Nexus is a legendary phone even though it's not the sharpest out there. And I am sure its "endurance" over time, will make it even more legendary!
PS: Working on a cool Zooper Skin. Will let u know when it's out!
Click to expand...
Click to collapse
I'm not one to sit by idly and wait for confirmation of a stable new Android version. When 4.4 was released I flashed it right away. Whats the fun in not "jumping into the unknown"?
I dont think small updates are that hard for developers to merge into our current builds. We are already on 4.4.1 and I'm sure that 4.4.2 will be on our devices soon as well.
KitKat has been running great on my device. I dont know of any issues we have now that havent been fixed yet.

jsgraphicart said:
I'm not one to sit by idly and wait for confirmation of a stable new Android version. Wn 4.4 was released I flashed it right away. Whats the fun in not "jumping into the unknown"?
I dont think small updates are that hard for developers to merge into our current builds. We are already on 4.4.1 and I'm sure that 4.4.2 will be on our devices soon as well.
KitKat has been running great on my device. I dont know of any issues we have now that havent been fixed yet.
Click to expand...
Click to collapse
Well...my GPS could be better. I'm seeing at best 30ft accuracy with about 8 satellites locked in with pretty low SNR values.

Im still on 4.3, Slimbean. Waiting for Slimkat to evolve just a litle bit more :good:

alpha-niner64 said:
Well...my GPS could be better. I'm seeing at best 30ft accuracy with about 8 satellites locked in with pretty low SNR values.
Click to expand...
Click to collapse
I haven't had any issues with GPS. It pinpoints pretty fast for me.
And by the way, cyanogenmod just updated us to 4.4.2.

I will be continuing to use my Galaxy Nexus until the 'Nexus 6', it can totally hold up to most of the competition. Currently using the last 4.4.1 Galaxy Nexus Maguro CM11 ROM with ASKP/Franco/Mpokang/Fancy/Stock kernel.

[Q] Which one is the latest Android generation with working FM radio?

Hello, guys!
Can somebody please tell me, which one is the latest Android generation with working FM radio for Arc?
Is it CM9 or CM10 and with which radio apk is FM radio working? Spirit FM or some other app?
Is any chance to have working FM radio in Android KK?
Thanks for the info in advance!

Since there is no answer on my first question, let's ask you another way - is there any chance to compile a fully working Kit Kat ROM with 2.6 kernel, with FM radio working?

Upto 4.1.2 almost every rom has radio working with 2.6 kernel, no fm radio with 3.++ kernel

KK will not work on 2.6xx kernel, you will need kernel 3.xx which does not have FM radio due to no driver support from the chipset manufacturer.
僕のLT18iから送られてきた

popthosegaskets said:
KK will not work on 2.6xx kernel, you will need kernel 3.xx which does not have FM radio due to no driver support from the chipset manufacturer.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
That's pretty poor to read and to know. A friend of mine, owner of the Samsung Galaxy S3 just got an official update to Jelly bean, expecting a new one to Kit Kat, and Sony leaves their flagman phone's users without support and with unofficial releases from CM only. Poor, Sony, poor experience from you!

novicebg said:
That's pretty poor to read and to know. A friend of mine, owner of the Samsung Galaxy S3 just got an official update to Jelly bean, expecting a new one to Kit Kat, and Sony leaves their flagman phone's users without support and with unofficial releases from CM only. Poor, Sony, poor experience from you!
Click to expand...
Click to collapse
It's not fair to compare an arc and a s3...
Sent from my Xperia Neo V using Tapatalk 2

novicebg said:
That's pretty poor to read and to know. A friend of mine, owner of the Samsung Galaxy S3 just got an official update to Jelly bean, expecting a new one to Kit Kat, and Sony leaves their flagman phone's users without support and with unofficial releases from CM only. Poor, Sony, poor experience from you!
Click to expand...
Click to collapse
I don't trust Samsung when it comes to software, their ROMs have always been buggy and full of problems.
You can't blame Sony as well, the update window is well past the 18 month period since the phone's release. They may have the obligation to fix bugs, but not the obligation to update the phone to a newer Android version.
That's the main problem with most of the users here; they expect the manufacturer to update the phone to the latest version of the OS, which is not 100% feasible due to hardware restrictions and some other PRBS by the company. Sometimes having an old but more stable ROM is more beneficial long term. I have been using a custom 4.2.2 ROM for almost a year and I find it good and stable enough for daily use. There's no rush to update to KK and face more problems with the OS since older ROMs are able to meet the demands of the end user.
The only issue with Sony is that I would have liked them to release the sources publicly so it can save the developers time and effort to develop custom ROMs.
Just my 2 cents on the issue.
僕のLT18iから送られてきた

So what about that:
http://developer.sonymobile.com/2012/03/07/fm-radio-module-released-as-open-source-and-sensor-hal-updated/
it was quoted in another topic but no one answered whether exactly this are the drivers needed?

Already discussed here:
https://github.com/M66B/cm-xtended/issues/1
Sent from my Xperia Neo V using xda app-developers app

with so many people creating roms, there will not be a soul here that applies to get the FM radio to work, sure it was well compensated! Greetings to all!
Sent from my Xperia Arc S using xda app-developers app

popthosegaskets said:
I don't trust Samsung when it comes to software, their ROMs have always been buggy and full of problems.
You can't blame Sony as well, the update window is well past the 18 month period since the phone's release. They may have the obligation to fix bugs, but not the obligation to update the phone to a newer Android version.
That's the main problem with most of the users here; they expect the manufacturer to update the phone to the latest version of the OS, which is not 100% feasible due to hardware restrictions and some other PRBS by the company. Sometimes having an old but more stable ROM is more beneficial long term. I have been using a custom 4.2.2 ROM for almost a year and I find it good and stable enough for daily use. There's no rush to update to KK and face more problems with the OS since older ROMs are able to meet the demands of the end user.
The only issue with Sony is that I would have liked them to release the sources publicly so it can save the developers time and effort to develop custom ROMs.
Just my 2 cents on the issue.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
I'm on KitKat already and it's actually not half-bad, aside from a few random glitches here and there. Still too fresh to be perfect I guess.
I think that Arc's hardware is the main reason for the lack of further official upgrades. It'd take too much work to get it to work perfectly with all of Sony's additional apps and branding required to make it flashy enough for an official rom, if it would even be possible at all. Short on ram as well as internal memory as it is, I'm honestly amazed what developers are managing to port to our beloved phone.

Google keeps the Galaxy Nexus alive

...well, at least here: http://www.google.com/mobile/
(must visit from desktop)
Nothing special, but it's funny how we are close to the third GNex successor and they still won't update such an important web page.

Ahahahahah very funny!

Good news!
But GN will not have Android L

smilezou said:
But GN will not have Android L
Click to expand...
Click to collapse
I have ShinyROM on my GNex, but I'm prepared for the eventuality that this trusty phone will stop getting development support when Android L hits...
Should be just in time for me to get an upgrade anyway...

rjspring said:
I have ShinyROM on my GNex, but I'm prepared for the eventuality that this trusty phone will stop getting development support when Android L hits...
Should be just in time for me to get an upgrade anyway...
Click to expand...
Click to collapse
G1 got development up until jellybean. Grant it, it was not even close to daily driver, just a proof of concept. I suspect gnex will get support until the phone refuses to boot thev latest os

md1008 said:
G1 got development up until jellybean. Grant it, it was not even close to daily driver, just a proof of concept. I suspect gnex will get support until the phone refuses to boot thev latest os
Click to expand...
Click to collapse
I'd be happy if that is the case, the phone still works great. With the main ShinyROM developer starting to concentrate on other life tasks, hoping that OmniROM or Paranoid Android continue to carry the GNex flag.

All the devs are doing an amazing work on this phone. Today, MWisBest has updated the 3.0 kernel with the latest gpu driver for the OMAP chip, and the users that tried the FML rom beta with this trick are all entusiast!
Gnex will live for a long time yet!

Cyanognen MOD ROM
smilezou said:
But GN will not have Android L
Click to expand...
Click to collapse
You can have KitKat with Cyanogen Mod 11. Works fine. I ma enjoying it.

CyanogenMod will continue to support the international version of the galaxy nexus (maguro) but it have left the support of toro and toroplus
Sent from my Galaxy Nexus using XDA Free mobile app

I always thought that was a Nexus 4... Well I guess Google is just laughing in our faces

jackie_alden said:
All the devs are doing an amazing work on this phone. Today, MWisBest has updated the 3.0 kernel with the latest gpu driver for the OMAP chip, and the users that tried the FML rom beta with this trick are all entusiast!
Gnex will live for a long time yet!
Click to expand...
Click to collapse
I was among the enthusiasts and apart from camera [which i dont use a lot] everything else seems to be working fine even xposed and viper4android , and i am using ext4 fs FYI . My daily driver , pretty smooth and doesn't crash a lot

md1008 said:
G1 got development up until jellybean. Grant it, it was not even close to daily driver, just a proof of concept. I suspect gnex will get support until the phone refuses to boot thev latest os
Click to expand...
Click to collapse
ScardracS said:
CyanogenMod will continue to support the international version of the galaxy nexus (maguro) but it have left the support of toro and toroplus
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Doesn't matter. I'm still seeing almost daily updates for my Toro

Mini victory for gnex?