Skip Android 4.3. - Sony Xperia P, U, Sola, Go

The development of 4.3 for our phones began as most of you are aware but I would like to make a suggestion.The next iteration of Android,KitKat is optimized to run smoothly on devices with 512mb RAM (Sola,U,Go),it's called Project Svelte or something like that.I'm grateful that master Munjeni is working so hard for our devices but I say he should just skip 4.3 and go directly to 4.4 and help him by testing,detailing and fixing bugs,etcetera.If this so called Project Svelte really does what it says we're gonna have a new phone! What do you think?

MetalheadAndroid said:
The development of 4.3 for our phones began as most of you are aware but I would like to make a suggestion.The next iteration of Android,KitKat is optimized to run smoothly on devices with 512mb RAM (Sola,U,Go),it's called Project Svelte or something like that.I'm grateful that master Munjeni is working so hard for our devices but I say he should just skip 4.3 and go directly to 4.4 and help him by testing,detailing and fixing bugs,etcetera.If this so called Project Svelte really does what it says we're gonna have a new phone! What do you think?
Click to expand...
Click to collapse
Your wish has been granted.
http://forum.xda-developers.com/showthread.php?p=47010626

MetalheadAndroid said:
The development of 4.3 for our phones began as most of you are aware but I would like to make a suggestion.The next iteration of Android,KitKat is optimized to run smoothly on devices with 512mb RAM (Sola,U,Go),it's called Project Svelte or something like that.I'm grateful that master Munjeni is working so hard for our devices but I say he should just skip 4.3 and go directly to 4.4 and help him by testing,detailing and fixing bugs,etcetera.If this so called Project Svelte really does what it says we're gonna have a new phone! What do you think?
Click to expand...
Click to collapse
I agree with you, and so does Munjeni apparently
He has mentioned in the Go forums that he is stopping development for 4.3 and starting on 4.4 now.

MetalheadAndroid said:
The development of 4.3 for our phones began as most of you are aware but I would like to make a suggestion.The next iteration of Android,KitKat is optimized to run smoothly on devices with 512mb RAM (Sola,U,Go),it's called Project Svelte or something like that.I'm grateful that master Munjeni is working so hard for our devices but I say he should just skip 4.3 and go directly to 4.4 and help him by testing,detailing and fixing bugs,etcetera.If this so called Project Svelte really does what it says we're gonna have a new phone! What do you think?
Click to expand...
Click to collapse
The major problem is for source codes, ST (ex chipmaker of our phones) don't release it! The low ram amount is the minor problem. OUR PHONE ARE SH*T! ..unfortunately :'(

That's good,can't wait to get my hands on 4.4 android! As of the sources I don't think there are big hardware changes except bluetooth,if we have sources for 4.3 we also have sources for KitKat.Google is now doing what Sony and ST-Ericsson failed to do..

it would be great if percy could do the same for xperia p .
android 4.4 seems to be soo goood , can't wait

I heard 4.4 has an expiremental runtime-compiler which is called ART. It's a part from droidbooster. And it's supposed to replace dalvik somewhere in the near future.
I hope the developers here can also make that compiler work, but I don't know if it is possible. for our devices.

AslanFatih said:
I heard 4.4 has an expiremental runtime-compiler which is called ART. It's a part from droidbooster. And it's supposed to replace dalvik somewhere in the near future.
I hope the developers here can also make that compiler work, but I don't know if it is possible. for our devices.
Click to expand...
Click to collapse
Thats part of android framework,nothing much has to be done to get this work expect compile 4.4 rom.
Sent from my Xperia U using xda app-developers app

Related

JellyBean Port?

JellyBean was ported form the Nexus Devices that were given out at I/O, is there a chance that a developer will port this to the maxx and og razr?
oh. my. god. i am going to have to switch to iPhone or go mad.
someone or some people will be allready on it and why not if tyhe source code is out
ICS is nice but i get the feeling its gonna be Androids Vista people might just skip for Jellybean
Some of us my friend still don't have ICS....let alone JB
Sources not available yet... But i think that changes only affects android platform and not kernel. All HW accel was done in 4.0, so 4.1 should only optimize android itself (dalvik, gui underlying libraries, etc).
Nexus and RAZR share same CPU (OMAP4430/4460 - the only difference is CPU freq, so technically we can use libs from nexus without any problem and without recompilation since libraries already optimized for or CPU), same GPU (PVR SGX 540, however nexus's GPU is slightly overclocked) - so H/W accel should not be a problem
So there is a good change that someone will port 4.1 to our devices. Or maybe i'm just wrong
I just played w my buds verizon nexus on the team vicious jelly bean and it is nice! Smooth. Siri like voice assistant that really does a lot. I didn't expect it to be such a large update. I like and of course am hoping to get it on the RAZR soon but as it is ics is very very nice
rlex said:
Sources not available yet... But i think that changes only affects android platform and not kernel. All HW accel was done in 4.0, so 4.1 should only optimize android itself (dalvik, gui underlying libraries, etc).
Nexus and RAZR share same CPU (OMAP4430/4460 - the only difference is CPU freq, so technically we can use libs from nexus without any problem and without recompilation since libraries already optimized for or CPU), same GPU (PVR SGX 540, however nexus's GPU is slightly overclocked) - so H/W accel should not be a problem
So there is a good change that someone will port 4.1 to our devices. Or maybe i'm just wrong
Click to expand...
Click to collapse
Don't give up just yet, I am confident that some awesome developer out there will fix it
Sent from my XT910 using xda premium
iolinux333 said:
oh. my. god. i am going to have to switch to iPhone or go mad.
Click to expand...
Click to collapse
That sounds like an excellent strategy, because as we all know, hearing about a new OS makes our phones turn from great to absolutely unusable piles of junk. And, I want to help. I'll offer you FIVE DOLLARS for your Razr. SIX dollars if it's a Maxx. AND, I'll throw in an additional quarter if it has a 32gb or larger memory card. You can put this money towards a new iPhone 4s!
WOW, it feels great helping people! Yay me!
I'm going to wait a little while long for the OTA for ICS in Canada (rogers), but i'm getting tired of waiting!!! lol for my first android phone, was expecting a little more, but... after a "little while" i'm going to figure out how to push a image of ICS lol
i hope JB comes to the razr, but i'll just be happy with ICS
maniAK- said:
someone or some people will be allready on it and why not if tyhe source code is out
ICS is nice but i get the feeling its gonna be Androids Vista people might just skip for Jellybean
Click to expand...
Click to collapse
We share the same thought. I was thinking Windows Millennium, but Vista also works.
__
€ incognito »
™
Seriously, just because JB has been announced, doesn't make ICS any less awesome. It flies on the Razr, I love it (leaked .211). It seems like now people are starting to get the attitude that just because JB is going to be released soon, makes ICS ancient and unworthy for their device. I've seen people across this, and other forums, talking about selling their phones to get one that JB will be released to at some point. Unless you get a pure Google phone, like the Nexus, you won't be getting an upgrade to JB anytime soon. All manufacturers operate in the same mindset. Ventures that make them money is priority one, followed by other things, then other things, and then upgrading to the latest and greatest for existing devices sits kind of low. If the kernel source turns out to be an ICS based kernel, I'm sure that one of the devs will be cranking out a version for us to flash in SS 2.0.
From the sounds of it we should at least get some sort of port. One thing that concerns me is how the performance boost will affect battery. The whole 60fps thing would surely eat through any power source. My bro has a gnex so I'll see soon enough.
Sent from my XT910 using xda premium
Let's try to keep some perspective... this fall, it's released, then the manufacturers and carriers go through the process to make it work on their own hardware, and it gets pushed in Q1 or Q2 of 2013.
This is not an impending thing.
Do I have too much faith in da devs then? My old device was a desire z and got ics ported to it about 6 weeks after release. The RAZR is much close in hardware to the gnex and ics is much closer in code to jb. I'm not putting money on it but I am hopeful.
Sent from my XT910 using xda premium
MarkyG82 said:
Do I have too much faith in da devs then? My old device was a desire z and got ics ported to it about 6 weeks after release. The RAZR is much close in hardware to the gnex and ics is much closer in code to jb. I'm not putting money on it but I am hopeful.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Who are the "DA Devs" that you're referring to?
the devs at droidrazr.com are already going to be working on porting jellybean to the razr & maxx. as far as an ota since 4.1 is a minor update it shouldn't take moto long to get it going for us.
sRDennyCrane said:
Let's try to keep some perspective... this fall, it's released, then the manufacturers and carriers go through the process to make it work on their own hardware, and it gets pushed in Q1 or Q2 of 2013.
This is not an impending thing.
Click to expand...
Click to collapse
LOOK AT moto with ICS and not only them but every other manufacturer ICS was released over a year ago and now its finally being pushed out to the razr barely. So when JB gets pushed out to the razr and thats a big if I would just hold my breath for about a year or more. Or do like every one else flash a rom based on jb. which should be out by the start of next year or the end of this year.
dligon said:
LOOK AT moto with ICS and not only them but every other manufacturer ICS was released over a year ago and now its finally being pushed out to the razr barely. So when JB gets pushed out to the razr and thats a big if I would just hold my breath for about a year or more. Or do like every one else flash a rom based on jb. which should be out by the start of next year or the end of this year.
Click to expand...
Click to collapse
lmao... it's not going to take a year to get jellybean. nobody would even be on this device by then. 4.1 is a minor update anyways, it's not like motoblur needs to be re-written.
fix-this! said:
lmao... it's not going to take a year to get jellybean. nobody would even be on this device by then. 4.1 is a minor update anyways, it's not like motoblur needs to be re-written.
Click to expand...
Click to collapse
really you really think that verizon and moto will actually push out an ota for the razr with JB whenever the JB source drops this fall or whenever. I highly doubt that.
dligon said:
really you really think that verizon and moto will actually push out an ota for the razr with JB whenever the JB source drops this fall or whenever. I highly doubt that.
Click to expand...
Click to collapse
we may never get as ive said before. but IF we do id say by the end of summer or fall maybe.

4.2.2.. does anyone know what is to come?

I'm really surprised after looking into this phone that it's only running 4.2.2 considering it's being release just a couple weeks before the note 3.. Does have news on whether it will be getting 4.3.. or kitkat?
Kitkat may be far away since nexus five is not yet unveiled, I guess
Sent from my C6603 using XDA Premium 4 mobile app
arctic84 said:
I'm really surprised after looking into this phone that it's only running 4.2.2 considering it's being release just a couple weeks before the note 3.. Does have news on whether it will be getting 4.3.. or kitkat?
Click to expand...
Click to collapse
It will at least get 4.3 I would guess since it doesn't make much sense to have the new OpenGL 3.0 capable 330 GPU and only have an OS that supports OpenGL 2.0 stay on the phone. How quickly we will get this is anyone's guess however. I saw that google is already on 4.3_r3 which means they are still merging tweaks and fixes to the 4.3 release. LG may be integrating these and waiting for a stable code base to release with.
ddg00101 said:
It will at least get 4.3 I would guess since it doesn't make much sense to have the new OpenGL 3.0 capable 330 GPU and only have an OS that supports OpenGL 2.0 stay on the phone. How quickly we will get this is anyone's guess however. I saw that google is already on 4.3_r3 which means they are still merging tweaks and fixes to the 4.3 release. LG may be integrating these and waiting for a stable code base to release with.
Click to expand...
Click to collapse
4.3 on my Gnex screams, I can only imagine on the monster that is the G2!
Im hoping we get KitKat but will settle for 4.3 for now.
LG is also doing all of the multitasking stuff that Samsung has been doing for the note 2 for the first time I believe. They probably started development with 4.2 or 4.2.1 and before release integrated 4.2.2. Integrating 4.3 before release would have pushed the release window too far behind the note 3 for them to stay competitive. They likely decided to release with 4.2.2 while already updating to 4.3 in another code tree, or plan to wait till 4.4 to give us a new OS version based update. All speculation, but it makes sense to me at least .
I'd hate to say it but LG + AT&T ugh I wouldn't hold my breath lol first of the year maybe at the earliest for 4.3
I'm hoping to go direct to 4.4 personally. Hopefully LG has had lots of access with the n5 to get a head start on it.
chrisexv6 said:
4.3 on my Gnex screams, I can only imagine on the monster that is the G2!
Click to expand...
Click to collapse
You're making me excited! My Galaxy Nexus is also super fast on 4.3. I can only imagine how blazing fast the G2 will be with CyanogenMod 10.2. Oh, it makes me quiver with excitement.
I have the T-Mobile variant. They have been on a big "be the best carrier" push, so I wouldn't doubt getting a new firmware update before the other carrier phones
Screw Android 4.3 At this point I want LG to release an update to Android 4.4.2 KitKat next year because we know Android is going to release some minor patches after Android 4.4 is released.
hmm yep you're right
why 4.2.2 at the first position instead 4.3
but since the major changelogs from 4.2.2 to 4.3 are about the bluetooth thingy and open GL thingy
for me it doesn't matter
since this beast can do all the things that a phone should do
who knows maybe after this, the first jump is kitkat
imho
depth_charge said:
hmm yep you're right
why 4.2.2 at the first position instead 4.3
but since the major changelogs from 4.2.2 to 4.3 are about the bluetooth thingy and open GL thingy
for me it doesn't matter
since this beast can do all the things that a phone should do
who knows maybe after this, the first jump is kitkat
imho
Click to expand...
Click to collapse
4.3 re-wrote a lot of behind the scenes stuff. Memory management and garbage collection seem MUCH better. My Gnex has never been so fast as it is on 4.3.
BUT part of the bluetooth rewrite has caused my phone to reboot on re-connection to my car head unit. A few others have experienced the same issue, across different ROMs as well so it very well may be an issue with the Android source code. Hopefully Le Goog fixes it because the rest of 4.3 is awesome. And FWIW 4.3 is the first version that actually streams the bluethooth metadata correctly so I can see artist/album/track info on my head unit now.
chrisexv6 said:
4.3 re-wrote a lot of behind the scenes stuff. Memory management and garbage collection seem MUCH better. My Gnex has never been so fast as it is on 4.3.
BUT part of the bluetooth rewrite has caused my phone to reboot on re-connection to my car head unit. A few others have experienced the same issue, across different ROMs as well so it very well may be an issue with the Android source code. Hopefully Le Goog fixes it because the rest of 4.3 is awesome. And FWIW 4.3 is the first version that actually streams the bluethooth metadata correctly so I can see artist/album/track info on my head unit now.
Click to expand...
Click to collapse
oh i c
then.. my bad to not too well educated with the changelogs
depth_charge said:
oh i c
then.. my bad to not too well educated with the changelogs
Click to expand...
Click to collapse
Heh no biggie, they arent exactly easy to read anyway!
I dont want 4.3 on this phone becuz it gives lg an excuse not to give 4.4. At this point i only want 4.4 becuz i expect more features to be added which includes all the 4.3 features.
Sent from my Motorola Photon 4G using Tapatalk 2

Sailfish OS Port for Galaxy Ace II request [libhybris] [jolla] [sailfishos]

Hello,
First I want to thank everyone that contributed in development of software for our Samsung Galaxy Ace II. Especially Team Canjica, Rox and many many others!
Jolla, the producent of Sailfish OS, has just released the LibHybris 1.0, which allows the devs to build the Sailfish OS for ANY Android device running CyanogenMod 10.1. It is THE BIG CHANCE for our device!
Sailfish OS is a lot faster and smoother OS than Android. Our device with just 768 MB RAM and dual core Novathor CPU should perform a lot better on Sailfish than on Android. And it is possible to run Android apps on Sailfish too!
http://www.jollausers.com/2014/07/sailfish-os-hardware-adaptation-dev-kit-release-1-0/
So I want to ask our great community to try to port Sailfish OS for our device. We have the very good working CM 10.1, so we should try! It can be the second life for our device
I hope we will start the great discussion and the devs will be helpful
Please, port this amazing system to Ace II
Cheers
I dig this! If someone wanted to develop this i would be happy to try this os.
Sent from my GT-I8160 using XDA Free mobile app
Even though I'm migrating to the fastest android phone ever, if SailfishOS is released for the Ace 2, I would be a VERY happy man! Please make it happen! Many of us don't use the Ace 2 for 3D gaming anyway, so a lack of apps on SailfishOS is negligible! :good:
Any response from developers?
Well, i do not know how it's done, but cm 10.1.x is quite slower, than 10.2's, so wouldn't be lost what is gained?
Only the kernel from CM 10.1 is used for drivers purposes. Anything else is just pure Sailfish, and it should be A LOT MORE FLUID AND FAST than any Android version.
rafalo1333 said:
Only the kernel from CM 10.1 is used for drivers purposes. Anything else is just pure Sailfish, and it should be A LOT MORE FLUID AND FAST than any Android version.
Click to expand...
Click to collapse
...if you say so..ok, thx for clarification. but you know , that newer kernels(10.2 minimum) are main source of speed of actual roms? Even not roms itself, you know..
xo.en said:
...if you say so..ok, thx for clarification. but you know , that newer kernels(10.2 minimum) are main source of speed of actual roms? Even not roms itself, you know..
Click to expand...
Click to collapse
I dont think that kernel in CM 10.1 is a lot different than kernel from CM 11. We must ask @Rox, but I think that backporting some features from CM11's kernel wont be too hard. Lets hope so
rafalo1333 said:
I dont think that kernel in CM 10.1 is a lot different than kernel from CM 11. We must ask @Rox, but I think that backporting some features from CM11's kernel wont be too hard. Lets hope so
Click to expand...
Click to collapse
...well, optimist, good luck..
xo.en said:
...well, optimist, good luck..
Click to expand...
Click to collapse
I think they are a realist myself, as this is an old, yet highly dev supported, phone, and due to it's rubbish GPU, will highly benefit from SailfishOS, as 3D games are useless on this device.
http://forum.xda-developers.com/jolla-sailfish/general/hakd-release-1-0-t2820012
Also, this.
Supposedly most android apps should be compatible too so this should be a fun experience
No one is interested in porting it?
up
As far ad I know, android apps work only on the original jolla phone. Porting does not support them yet.
Source: a friend of mine installed it on the nexus 4
Sent from my GT-I8160 using XDA Free mobile app
Hi don't get me wrong IS looks great but don't know about devs.. To be honest here is lack of drugs and I think that for android L wait more people than for this.... On the other hand would be use full to contact someone from other teams that have recently ported the latest versions to ace2 if they don't plan to do it again... But this is not you have asked for.... I know. But the community for android is bigger sorry for that and clean one runs the smoothest yeah not clean but with lot of use full features like from carbon.... But if there is a def that likes this more than android l... Would be happy to try also this out.... But have to pedal for community too to consider the total demand over local projects
just my guess, android 5.0 needs updated binary whilst the sailfish need only binary up to cm 10.1
so there will be a bit performance gap because of driver needed
but well that was just a wild guess :cyclops::cyclops::cyclops:

What's wrong with CyanogenMod?

Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..

Project tango k1 tegra

I got a Project Tango tablet from work, it has k1 tegra chipset and it is stuck on original firmware, which is android 4.4.4 and doesnt performs very well on normal tasks as far as it is very powerfull hardware. Any chance I can upgrade it with custom firmware? Maybe shield tablet which has similar hardware without the special sensors?
Last time I had the tango (back in July 2016) there were no custom firmware/rom for it. I would check out the Tango Devs group on G+ to see if anyone has created an update for it.
Any news about this? Any help would be much appreciated.

			
				
SrAgaporni said:
Click to expand...
Click to collapse
First off you are going to need root the device. Then a custom recovery. Then you can think of customs ROMS if you can work out the hardware and the appropriate drivers.
Just because it has the same processor as the Shield does not mean that all the other hardware is the same.
Sent from my SM-G930F using Tapatalk
ashleyglassel said:
First off you are going to need root the device. Then a custom recovery. Then you can think of customs ROMS if you can work out the hardware and the appropriate drivers.
Just because it has the same processor as the Shield does not mean that all the other hardware is the same.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Thanks, the process is crystal clear, I just wanted to know if anybody already advanced anything in this device, but it feels as there is no progress at all, so It will be worth to sell this nearly new tablet and buy another device with more community working with it. A shame, with 128Gb emmc, 4Gb RAM and a powerfull processor...
It would be great if we could get any assistance from Google on this, I highly am doubtful they will release kernels but it is worth trying to petition them to release them, or anything of value towards this, to the community. The hardware is excellent on the tango Dev tablet, but at this point the software is absimal, and, as is, barely functions. I find most software cannot run and constant glitches make using it worse than a contemporary generic device despite an excellent touchscreen and the tegra processor.
I have rooted my Tango tablet, but what hopes do we have of a community rom running any newer version of Android? (5.1+) The shield tablet has similar hardware and could maybe be used as a base to develop from, as the basic kernel will be similar. anyone determine what wifi/Bluetooth hardware is on board the tango?
Come on Google, help us get full functionality and release the kernels!
Is there any one behind this project?
alexcount said:
It would be great if we could get any assistance from Google on this, I highly am doubtful they will release kernels but it is worth trying to petition them to release them, or anything of value towards this, to the community. The hardware is excellent on the tango Dev tablet, but at this point the software is absimal, and, as is, barely functions. I find most software cannot run and constant glitches make using it worse than a contemporary generic device despite an excellent touchscreen and the tegra processor.
I have rooted my Tango tablet, but what hopes do we have of a community rom running any newer version of Android? (5.1+) The shield tablet has similar hardware and could maybe be used as a base to develop from, as the basic kernel will be similar. anyone determine what wifi/Bluetooth hardware is on board the tango?
Come on Google, help us get full functionality and release the kernels!
Is there any one behind this project?
Click to expand...
Click to collapse
if you want the development of the kernel at least started, make the kernel start logs. use the program syslog from Google Play for example.
I completely forgot that I found and downloaded the source code of the kernel on this tablet. The kernel is there version 3.10.24. With a strong desire, it could easily be adapted to the modern kernel 3.10.96.
I have the possibility of getting this tablet sub $100 and would be extremely interested if a newer Android could be loaded here. Or even maybe something like UBports (formerly Ubuntu Touch)
Vartom said:
I completely forgot that I found and downloaded the source code of the kernel on this tablet. The kernel is there version 3.10.24. With a strong desire, it could easily be adapted to the modern kernel 3.10.96.
Click to expand...
Click to collapse
I can't find this source anywhere, could you upload a copy? I know a few people, myself included are looking for it. Someone else who is looking https://plus.google.com/u/1/+GregWillardr3pwn/posts/V1K5XDBtKig
ShapeShifter499 said:
I can't find this source anywhere, could you upload a copy? I know a few people, myself included are looking for it. Someone else who is looking https://plus.google.com/u/1/+GregWillardr3pwn/posts/V1K5XDBtKig
Click to expand...
Click to collapse
They have been with me for so long that I don’t remember exactly where I downloaded them from. I remember that it was some kind of official site about the project of tango.
1
2
3
Vartom said:
They have been with me for so long that I don’t remember exactly where I downloaded them from. I remember that it was some kind of official site about the project of tango.
1
2
3
Click to expand...
Click to collapse
So you don't know exactly if these were the most recent version of the source?
If these are not the latest, it's better than nothing. I'm going to share these with that other guy and on reddit. Thank you for uploading these.
For anyone following this, the latest kernel appears to be here https://github.com/r3pwn/android_kernel_google_yellowstone
Hi guys, orginal Android 4.4 is still the latest Rom available, correct ?
HI.. I need the ROM stock for this device, Someone?
Hi again.. I found this on github, someone know something about this project?
NVIDIA AOSP device tree for building Project Tango Android 7.0
https://github.com/Project-Google-Tango/android_device_google_yellowstone
Anonikat I looked at that too. How great would that be? A 7.0 N even if I'd loose some Tango functionality. I'd just like it as a regular tablet, personally.
ShapeShifter499 said:
I have the possibility of getting this tablet sub $100 and would be extremely interested if a newer Android could be loaded here. Or even maybe something like UBports (formerly Ubuntu Touch)
Click to expand...
Click to collapse
Closest I've seen so far that seems functional for the most part is LineageOS 15.1 (Android 8.1) that's listed as an unofficial release in this forum.
Here is TWRP recovery project for this device https://forum.xda-developers.com/sh...overy-project-tango-k1-atap-twrp-3-2-t3901519

Categories

Resources