Develop Bugs

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] Kitkat on TouchWiz

Need Rom Touch Wiz based Kitkat or 4.3 :/
Possible?

Not possible... if you can't live without dual SIM and still want the Kitkat goodies, you can always download Google's apps on Play Store and apply some cosmetic mods to make your stock ROM feels a lot like Kitkat.

naufalhadyan said:
Not possible... if you can't live without dual SIM and still want the Kitkat goodies, you can always download Google's apps on Play Store and apply some cosmetic mods to make your stock ROM feels a lot like Kitkat.
Click to expand...
Click to collapse
Its possible actually..but no devs today i think will take interest to develop/port the whole OEM...it will not just be buggy..but also alot of time consuming..as all it needed is a base rom and port rom of same android versions (we got 4.4.2 cm11 as base already),there is a mere possibility to do this..
But i dont think anyone will do that mahn..
#reference from thread "port OEM's of same android version", many cases shows successful results (at least OP do)....
Sent from my GT-I9082 using Tapatalk

raghavsharmaxda said:
Its possible actually..but no devs today i think will take interest to develop/port the whole OEM...it will not just be buggy..but also alot of time consuming..as all it needed is a base rom and port rom of same android versions (we got 4.4.2 cm11 as base already),there is a mere possibility to do this..
But i dont think anyone will do that mahn..
#reference from thread "port OEM's of same android version", many cases shows successful results (at least OP do)....
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Dude he was talking about "Touchwiz-based" Kitkat. Basically a CM11 on stock ROM. This is like wearing shoes on your head. Not possible.
But what you're talking about is "Kitkat-based" Touchwiz, which is possible but not feasible due to massive amount of work needed to convert the whole Touchwiz framework to Android 4.4 API...
Even Samsung itself (which is a giant company with hundreds if not thousands of coders) still need 3 months to port Note 3 Touchwiz to Kitkat... with our manpower here (about 4 active developers) this will take forever..

naufalhadyan said:
Dude he was talking about "Touchwiz-based" Kitkat. Basically a CM11 on stock ROM. This is like wearing shoes on your head. Not possible.
But what you're talking about is "Kitkat-based" Touchwiz, which is possible but not feasible due to massive amount of work needed to convert the whole Touchwiz framework to Android 4.4 API...
Even Samsung itself (which is a giant company with hundreds if not thousands of coders) still need 3 months to port Note 3 Touchwiz to Kitkat... with our manpower here (about 4 active developers) this will take forever..
Click to expand...
Click to collapse
His words are still confusing brother .. Touchwiz based kitkat ..KitKat which is based on tw...
Aaaahhh..confused like hell ..
Thanks for clear bro..as always u do
Sent from my GT-I9082 using Tapatalk

well no but if you want a rom (4.4.2) with dual sim i sugest to you pawitp's cm 11 (http://forum.xda-developers.com/showthread.php?t=2563557) its the only one with 4.4.2 others like gennxt are just the official rom with extra features

[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.

6.0 port

NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious

cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.

cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.

Source already available
We should wait for devs to build it ?

AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.

Yap, waiting for you too @joel.maxuel for working on it

allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.

Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0

Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk

The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,

What's hindering the development of CM13 for this device?

Does anyone know the exact reason why z1c doesn't have a CM13 build by now?

karamancho said:
Does anyone know the exact reason why z1c doesn't have a CM13 build by now?
Click to expand...
Click to collapse
Don't know for sure, but I wouldn't be surprised if there was no official CM 13 for Z1c, since there will apparently be no official MM from Sony, so the device is as good as dropped, (actually a recent article said that Sony is basically dropping the Z series - http://www.xperiablog.net/2016/02/24/confirmed-xperia-z-series-is-no-more/) However, I would bet we'll see a CM build at some point. We already have several CM/AOSP variants available. It's hard for devs to spend much time on devices that seem to be on their way out...

levone1 said:
Don't know for sure, but I wouldn't be surprised if there was no official CM 13 for Z1c, since there will apparently be no official MM from Sony, so the device is as good as dropped, (actually a recent article said that Sony is basically dropping the Z series - http://www.xperiablog.net/2016/02/24/confirmed-xperia-z-series-is-no-more/) However, I would bet we'll see a CM build at some point. We already have several CM/AOSP variants available. It's hard for devs to spend much time on devices that seem to be on their way out...
Click to expand...
Click to collapse
well didn't Sony include z1c into the "Open Devices" project? and don't they already release the necessary LP and MM binaries or am I missing something here?

karamancho said:
well didn't Sony include z1c into the "Open Devices" project? and don't they already release the necessary LP and MM binaries or am I missing something here?
Click to expand...
Click to collapse
Maybe it will come, I don't know... I just know that there's dozens of new devices all the time, and development requires someone to put in time and energy and money, and if the demand is shrinking for a certain device as it falls into the shadows of up-and-comings, then the motivation might fade too. I'm sure there are devs out there who would be happy to build for someone if you provide a device and a donation...

It's probably because it's not a very popular device for developers and there's nobody willing to maintain CM13 on it.

But it is a very good device
Sent from my Xperia Z1 Compact using XDA-Developers mobile app

yeah it's still a beast hardware wise.
I was asking because my old phone, galaxy s2 plus that I gave to my mother, has had CM13 since 06.12.2015. and samsung hasn't released anything for that phone since android 4.2.2 JB - no ROMs, no drivers, no binaries... nothing. yet the phone had excellent ROM support despite all that. bear in mind that this isn't the ex-flagship galaxy s2 - the s2 plus version I'm talking about here had nothing in common (hardware wise) with the s2 except the looks.
on the other hand, sony is constantly releasing MM binaries for the z1c and all I see in the dev forums are half a dozen tweaked sony stock roms but 1 or 2 AOSP based roms.
I was asking if there are some technical difficulties in building AOSP MM roms, otherwise I believe that it's impossible that a 2014 SD800 device has a better dev support than a 2012 device with a Broadcom SoC.

Hi,
the sources for CM13 are up and they build fine. I tested one a couple of weeks ago and it seemed to be running OK. Keep in mind, that pretty much all Sony devices are now based on the new 3.10 kernel, which requires quite a bit of work. Also, the camera isn't working very well yet, probably requires some more blob updates from Sony.
In case you want to give it a try, I made a quick build last night. I haven't flashed it myself but I would assume not too much has changed since the version I tried.
https://www.androidfilehost.com/?fid=24499762636006153
I'm not taking any dev credit, I just built what's already there.
Cheers

derf elot said:
Hi,
the sources for CM13 are up and they build fine. I tested one a couple of weeks ago and it seemed to be running OK. Keep in mind, that pretty much all Sony devices are now based on the new 3.10 kernel, which requires quite a bit of work. Also, the camera isn't working very well yet, probably requires some more blob updates from Sony.
In case you want to give it a try, I made a quick build last night. I haven't flashed it myself but I would assume not too much has changed since the version I tried.
https://www.androidfilehost.com/?fid=24499762636006153
I'm not taking any dev credit, I just built what's already there.
Cheers
Click to expand...
Click to collapse
Thanks for the work. There was a recent update to camera sources. @CLINTZ9 mentioned it in his AOSP thread and included in last build. With a good camera app and manual mode, you can get some pretty good pics.

Hi,
yes, I saw that the CM blobs are (from what I can tell) 3 versions behind the ones released from Sony. There was a new one released just yesterday.
If I get the chance, I can try to update them to the most recent release this weekend. No promises though, seeing as I'm quite busy these days
Has anyone tried this build? Is it booting/working OK?

derf elot said:
Hi,
yes, I saw that the CM blobs are (from what I can tell) 3 versions behind the ones released from Sony. There was a new one released just yesterday.
If I get the chance, I can try to update them to the most recent release this weekend. No promises though, seeing as I'm quite busy these days
Has anyone tried this build? Is it booting/working OK?
Click to expand...
Click to collapse
Can't right now, but definitely will...

derf elot said:
Hi,
the sources for CM13 are up and they build fine. I tested one a couple of weeks ago and it seemed to be running OK. Keep in mind, that pretty much all Sony devices are now based on the new 3.10 kernel, which requires quite a bit of work. Also, the camera isn't working very well yet, probably requires some more blob updates from Sony.
In case you want to give it a try, I made a quick build last night. I haven't flashed it myself but I would assume not too much has changed since the version I tried.
https://www.androidfilehost.com/?fid=24499762636006153
I'm not taking any dev credit, I just built what's already there.
Cheers
Click to expand...
Click to collapse
Using now. So far so good. You should start a thread...

Yes, running fine here. Thanks!

derf elot said:
Hi,
yes, I saw that the CM blobs are (from what I can tell) 3 versions behind the ones released from Sony. There was a new one released just yesterday.
If I get the chance, I can try to update them to the most recent release this weekend. No promises though, seeing as I'm quite busy these days
Has anyone tried this build? Is it booting/working OK?
Click to expand...
Click to collapse
will try to get a cm13 build up by next sunday if possible

derf elot said:
Hi,
the sources for CM13 are up and they build fine. I tested one a couple of weeks ago and it seemed to be running OK. Keep in mind, that pretty much all Sony devices are now based on the new 3.10 kernel, which requires quite a bit of work. Also, the camera isn't working very well yet, probably requires some more blob updates from Sony.
In case you want to give it a try, I made a quick build last night. I haven't flashed it myself but I would assume not too much has changed since the version I tried.
https://www.androidfilehost.com/?fid=24499762636006153
I'm not taking any dev credit, I just built what's already there.
Cheers
Click to expand...
Click to collapse
wow, finally CM 13 for the Z1 compact, some bugs?

CLINTZ9 said:
will try to get a cm13 build up by next sunday if possible
Click to expand...
Click to collapse
I'm in the process of updating the blobs right now and then make a new build. In case it works, would you be interested in sharing the load to keep it up-to-date? Like I said, I'm kind of busy these days.

derf elot said:
I'm in the process of updating the blobs right now and then make a new build. In case it works, would you be interested in sharing the load to keep it up-to-date? Like I said, I'm kind of busy these days.
Click to expand...
Click to collapse
Yeah sure
Do you compile on a pc or do you have a build server ?

I build on my PC, have you got one?

Thanks to @CLINTZ9 and @derf elot to bring us cm13 for this device
Sent from my Xperia Z1 Compact using XDA-Developers mobile app

karamancho said:
yeah it's still a beast hardware wise.
I was asking because my old phone, galaxy s2 plus that I gave to my mother, has had CM13 since 06.12.2015. and samsung hasn't released anything for that phone since android 4.2.2 JB - no ROMs, no drivers, no binaries... nothing. yet the phone had excellent ROM support despite all that. bear in mind that this isn't the ex-flagship galaxy s2 - the s2 plus version I'm talking about here had nothing in common (hardware wise) with the s2 except the looks.
on the other hand, sony is constantly releasing MM binaries for the z1c and all I see in the dev forums are half a dozen tweaked sony stock roms but 1 or 2 AOSP based roms.
I was asking if there are some technical difficulties in building AOSP MM roms, otherwise I believe that it's impossible that a 2014 SD800 device has a better dev support than a 2012 device with a Broadcom SoC.
Click to expand...
Click to collapse
Remember me from S2 Plus community? SAZY Rom, Slim Rom?