I'm asking this question because I'm using a Sony Xperia Z1. Due to driver problem it's 20.7MP camera will become near-sighted and unuseable in any ROM with API 23+. What I need is just a stable, lightweight OS with latest security patch and a working camera. So I would like to know will there be any successor of CM12.1 for certain devices like mine?
CAE_ said:
I'm asking this question because I'm using a Sony Xperia Z1. Due to driver problem it's 20.7MP camera will become near-sighted and unuseable in any ROM with API 23+. What I need is just a stable, lightweight OS with latest security patch and a working camera. So I would like to know will there be any successor of CM12.1 for certain devices like mine?
Click to expand...
Click to collapse
Someone i know who asked them this question was told that they will only release LineageOS 14.1 & 13.
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
Related
@Kernel devs,
Please, congregate your forces and build 3.x kernel for our precious Arc. I bet this will be one of the most (if not The Most) appreciated works. I bet this will be one of the most useful ones too. I bet almost every Arc/S user will agree with me.
Sent from nowhere
Absolutely!
What are the features you are waiting for in 3.0?
soo what does the new kernel provide?! I've seen few comments about users wanting the new kernel, and was wondering what improvement will it do to our Xperia?!
Mods please move this thread to general or Q&A. This thread is for android development, not wish lists.
Yes we'd all love a new kernel, why not bump to 3.5, well the answer to that is closed source drivers. While we should be able to theoretically add most of the maintenance patches to get to the latest 2.6.32.xx, porting to different major versions are just unlikely to be possible for our phone. You can't link against something with a different API, it just won't work.
The first request should be made to Sony to release sources for these drivers. Good luck with that.
So instead of focusing on version numbers, instead ask "Is feature X possible with our current kernel" and the kernel devs will try to accommodate and patch it in.
First of all, this isn't for Wishes and Requests, this is where you share you dev work with everyone, if you have a request then go to general or Q&A.
Second, EVERY DEVELOPER ALREADY KNOWS ABOUT THIS. Everyone IS WORKING on Kernel 3.0, ICS was laggy and JB isn't perfect is because the the lack of support in the kernel. So they don't need a "request"
Third, it is not impossible but very very hard. There is a reason why kernel 3.0 was never ported, because even the best devs like FXP and DoomLord CAN'T. Unless Sony releases their hardware sources or some developers open up his own Arc and get it out, no kernel 3.0 can be ported!
Custom msm7x30 3.0 kernels are still really in infancy stages with no major changes. If anything it's just a facelift but still the same purpose-wise.
Well, for those saing that devs can't do something I would argue - there's a 3.0 kernel being developed for HTC Desire (which also has closed source drivers) and guys working on it are pretty close. Same goes for HTC DHD and HD2 if i'm not mistaken. So why not for our device?
Sent from nowhere
tajimura said:
@Kernel devs,
Please, congregate your forces and build 3.x kernel for our precious Arc. I bet this will be one of the most (if not The Most) appreciated works. I bet this will be one of the most useful ones too. I bet almost every Arc/S user will agree with me.
Sent from nowhere
Click to expand...
Click to collapse
+ over 9000!
---------- Post added at 09:49 AM ---------- Previous post was at 09:40 AM ----------
It would be just awesome, beacuse idiots from Sony will pobably never update our kernels. Even HTC Wildfire S (which is little, smarttoy) has 2.6.35.x. It's not big difference, but... It is!
pmdisawesome said:
First of all, this isn't for Wishes and Requests, this is where you share you dev work with everyone, if you have a request then go to general or Q&A.
Second, EVERY DEVELOPER ALREADY KNOWS ABOUT THIS. Everyone IS WORKING on Kernel 3.0, ICS was laggy and JB isn't perfect is because the the lack of support in the kernel. So they don't need a "request"
Third, it is not impossible but very very hard. There is a reason why kernel 3.0 was never ported, because even the best devs like FXP and DoomLord CAN'T. Unless Sony releases their hardware sources or some developers open up his own Arc and get it out, no kernel 3.0 can be ported!
Click to expand...
Click to collapse
Work had already begun (with a lot of help from Jimbo77). It is stopped now (holidays) but for sure it's not abandoned.
tajimura said:
Well, for those saing that devs can't do something I would argue - there's a 3.0 kernel being developed for HTC Desire (which also has closed source drivers) and guys working on it are pretty close. Same goes for HTC DHD and HD2 if i'm not mistaken. So why not for our device?
Sent from nowhere
Click to expand...
Click to collapse
Because there is no Sony msm8255t 3.x kernel released that we can use as a base. There are major changes between 2.6.3x and 3.x kernel so
-all hardware related files (read: cpu, vibra etc) must be updated
-all drivers (read: screen, keys, sound etc) must be updated or rewritten
so it takes a lot of time and learning.
It's done when it's done
Click to expand...
Click to collapse
gen_scheisskopf said:
Work had already begun (with a lot of help from Jimbo77). It is stopped now (holidays) but for sure it's not abandoned.
Because there is no Sony msm8255t 3.x kernel released that we can use as a base. There are major changes between 2.6.3x and 3.x kernel so
-all hardware related files (read: cpu, vibra etc) must be updated
-all drivers (read: screen, keys, sound etc) must be updated or rewritten
so it takes a lot of time and learning.
Click to expand...
Click to collapse
first and bigest major new funcion is ntfs suport(for me there are, also sove with batery iporvents , also ksm is form 3.0.16 or 3.0.8(with used in cm roms))
n1kolaa said:
first and bigest major new funcion is ntfs suport(for me there are, also sove with batery iporvents , also ksm is form 3.0.16 or 3.0.8(with used in cm roms))
Click to expand...
Click to collapse
I had internal functions in mind (like ssize_t(*show) ), not user level.
Why would anyone think that this thread belongs in Development section, is beyond me.
Moreover, why would anyone think that in such community, known for the breakthroughs that its developers are achieving at a daily basis, such a request thread is needed.
I would like to believe that anyone who has been here long enough knows that if something is possible, it is done.
So, all in all, please think twice before clicking the "Start A New Thread" button.
Thanks for your cooperation.
Thread closed.
You might already know about the existence of the beautiful SailfishOS, what if it was possible to port it to our XPERIAS? It would look great on XS! Waiting for suggestions.
Wtf, QT based? MeeGo based? Last time I heard these words was when I was on symbian .
Personally I don't like the UI, and the android app compatibility
Sent from my LT26i using xda app-developers app
Ahh c'mon dont be that agressive! It's just and experiment, Sailfish is open source and can be ported, it only depends on the devs, will they do it or not.
MY BAD!!!
I messed up the pages and posted my thread into wrong section!!! Please remove it, I wanted to post it in the Q&A.
Sorry Sorry Sorry....
Oooohhh yeah, I really love Meego and Sailfish would be one very nice addition to ever growing Xperia S ROM collection
Would love Dual-Boot it on my Xperia S
Hope some friendly dev port it to our Xperia S.
Would love to have this wonderful OS. This is what Nokia essentially could've had instead of that other OS. It looks very well designed and very thoughtfully done.
https://www.youtube.com/watch?v=zxv7iXwIgno
If we can't get it ported, I'd at least love the launcher xD
Sent from my LT26i using xda premium
Would love to have this wonderful OS.
please can we have this
bclub said:
please can we have this
Click to expand...
Click to collapse
i dont think we ever get this bcoz we have only left 1 or two active developers for our xperia s.where other devices have plenty of roms, we just have one rom to play....Thanks to mickybart who is still making Xperia s alive....
In fact Sailfish OS is not 100% open source. All the UI is closed source.
Android compatibility is not supported on "custom" ROM too and it is not possible to buy a licence per device for now.
And last financial situation was not so great :/ (I hope that Jolla will survive and will be able to deliver a new phone in the future)
So that make interest more limited to work on it hardly.
I have already attempt to run SailfishOS and all sources to compile it are available under my github (https://github.com/mickybart/). The main issue is about hwcomposer implementation that is not working for our device. After long hours of troubleshooting I was not able to run the graphical stack. I forced clock initialization on the kernel too to avoid issues and it was better (no more kernel panic) but not enough to fix the problem. In fact the issue seems to be on the GPU driver because hwc initialization is done as it is done by SurfaceFlinger but it fails.
I have an experimental solution that permit me to run interface with SurfaceFlinger. So it is supposed to be possible to adapt lipstick (wayland compositor used by mer-hybris/SailfishOS) to use SurfaceFlinger but I chose to work on plasma mobile for now.
mickybart said:
In fact Sailfish OS is not 100% open source. All the UI is closed source.
Android compatibility is not supported on "custom" ROM too and it is not possible to buy a licence per device for now.
And last financial situation was not so great :/ (I hope that Jolla will survive and will be able to deliver a new phone in the future)
So that make interest more limited to work on it hardly.
I have already attempt to run SailfishOS and all sources to compile it are available under my github (https://github.com/mickybart/). The main issue is about hwcomposer implementation that is not working for our device. After long hours of troubleshooting I was not able to run the graphical stack. I forced clock initialization on the kernel too to avoid issues and it was better (no more kernel panic) but not enough to fix the problem. In fact the issue seems to be on the GPU driver because hwc initialization is done as it is done by SurfaceFlinger but it fails.
I have an experimental solution that permit me to run interface with SurfaceFlinger. So it is supposed to be possible to adapt lipstick (wayland compositor used by mer-hybris/SailfishOS) to use SurfaceFlinger but I chose to work on plasma mobile for now.
Click to expand...
Click to collapse
Hello sir...I am a great fan of yours and it worths...I follow your git everyday..I saw you are working on a project named hybris 5.1.1...can you tell me something about it???asking for my curiosity...sorry for my bad English
Sent from my C1904 using XDA-Developers mobile app
mihirtherocks said:
Hello sir...I am a great fan of yours and it worths...I follow your git everyday..I saw you are working on a project named hybris 5.1.1...can you tell me something about it???asking for my curiosity...sorry for my bad English
Sent from my C1904 using XDA-Developers mobile app
Click to expand...
Click to collapse
In fact the project is gnulinux_support (that include hybris with gnulinux-support-5.1 branch). For now I'm testing and writing the documentation to officially release this new project.
I will create an official xda project really soon (this week or next one if everything is good ! Take me longer time than expected !). The state of the project is very good but it will be reserved for developers to start.
You will know more soon
mickybart said:
In fact the project is gnulinux_support (that include hybris with gnulinux-support-5.1 branch). For now I'm testing and writing the documentation to officially release this new project.
I will create an official xda project really soon (this week or next one if everything is good ! Take me longer time than expected !). The state of the project is very good but it will be reserved for developers to start.
You will know more soon
Click to expand...
Click to collapse
Thank u sir for your reply
MIUIv5 will Jelly Bean, based on GeekyDroid's CyanogenMod 10.
Kitkat will be Source Compiling, and may not be fully functional.
let me Know, So I am working on a more beneficial project.
quakze said:
MIUIv5 will Jelly Bean, based on GeekyDroid's CyanogenMod 10.
Kitkat will be Source Compiling, and may not be fully functional.
let me Know, So I am working on a more beneficial project.
Click to expand...
Click to collapse
Can you see anything related to lollipop on github If you have synchronized resources ???
Sent from my XT1033 using XDA Free mobile app
sachoosaini said:
Can you see anything related to lollipop on github If you have synchronized resources ???
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Due to lack of responses for my present project, I have decided not do.
I also ask the moderator to close this thread
upon you
quakze said:
Due to lack of responses for my present project, I have decided not do.
I also ask the moderator to close this thread
Click to expand...
Click to collapse
well ohk
sachoosaini said:
well ohk
Click to expand...
Click to collapse
I Thought of doing Kitkat, tried with prebuild Kernel but compiler says its deprecated and discontinued.
So trying to compile Kernel with the Kitkat ROM.
To make it happen, Need some support from you guys !
Well i am not developer
quakze said:
I Thought of doing Kitkat, tried with prebuild Kernel but compiler says its deprecated and discontinued.
So trying to compile Kernel with the Kitkat ROM.
To make it happen, Need some support from you guys !
Click to expand...
Click to collapse
you see i don't own a linux ever. i use windows and my laotop is mostly always filled my own stuff. i need a decent RAM for building a machine for ROM And kernel development. so in that case i never able to succeed. IT require a certain amount of knowldge about programming which i don't know. so here everything stops. Well i tried to ask as much as developers in the past to make us a 3.0 kernel. but the issue is that our processor is way too slow and moreover it is single clock. The biggest thing that hampers the development is the non availability of GPU. After 2.3.7 google has introduced hardware acceleration. That was the last that was enough to kill our willy. Now as the code changes and and API changed with the more powerful phones. So at the end of the tunnel i also came to know that arm 6 processor does not support ART. So whati thought that someone will try to port the kitkat for our willy. But most of the devices that are getting the updates of kitkat are having GPU. I closed down my threats because of this. No one want to work on a device in which the power is way too less. so the main issue is not with kernel i saw HTC Explorer got KITKAT on 2.6 version of kernel though it is buggy but still they got it. Now hell it again has GPU. SO GPU is must for anything to happen after 2.3.7.. SASA's last attempt to built 4.2.2 is the last ray of hope for us. Because there the main developer of the arm 6 supported us for a while but then he vanishes. Well now just imagine for a wonder that somebody will post a KITKAT built. :good:
Hi guys,
In the last year I was using a dongle, Wireless Display Microsoft Adapter version 3.0.124.0, with good results with a Samsung Galaxy S4 and a notebook, Toshiba P50-A-14L.
I cannot say the same for OP3.
With OOS 3.2.4 the video lags and the sound is metallic, with others roms, like cm 13 arter kernel pacman op3lite, it doesn't even connect, while the PC and the s4 continue to perform well.
Is there anyone with the same issue or somebody with a solution?
Go to the source code
You are an advanced user. I used to fix Miracast issues at source code level, it seems a good opportunity for you to jump into Kernel driver, wpa_supplicant, android Miracast/WiFi Java framework, and using gdb_client to debug ...
xbing6 said:
You are an advanced user. I used to fix Miracast issues at source code level, it seems a good opportunity for you to jump into Kernel driver, wpa_supplicant, android Miracast/WiFi Java framework, and using gdb_client to debug ...
Click to expand...
Click to collapse
I've never done this before but there is always a first time! I'll try as soon as possibile!! Thank You!
Hello,
I have a question for experienced Armi users. What is the fastest and most responsive mod to date on Armani? (January 2023)
I know it's a very old phone with 1gb of memory, but maybe you have some good experiences with well optimised mods?
What I care most about is that the touch is responsive.
I am currently using LineageOS 18.1 and unfortunately it is very slow. Opening applications and just clicking is laggy, it has a delay of about 5 to 10 seconds
Don't get mad because I don't expect miracles. I want to know your opinion and your experience of using mods on Armani with a focus on speed
I'm using LOS 14.1 official. It's very responsive but quite old.
ehumydkx said:
Hello,
I have a question for experienced Armi users. What is the fastest and most responsive mod to date on Armani? (January 2023)
I know it's a very old phone with 1gb of memory, but maybe you have some good experiences with well optimised mods?
What I care most about is that the touch is responsive.
I am currently using LineageOS 18.1 and unfortunately it is very slow. Opening applications and just clicking is laggy, it has a delay of about 5 to 10 seconds
Don't get mad because I don't expect miracles. I want to know your opinion and your experience of using mods on Armani with a focus on speed
Click to expand...
Click to collapse
[ROM][UNOFFICIAL]LineageOS-14.1 for armani | Android 7.1.2 Nougat [MAY 2023]
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from...
forum.xda-developers.com
ehumydkx said:
Hello,
I have a question for experienced Armi users. What is the fastest and most responsive mod to date on Armani? (January 2023)
I know it's a very old phone with 1gb of memory, but maybe you have some good experiences with well optimised mods?
What I care most about is that the touch is responsive.
I am currently using LineageOS 18.1 and unfortunately it is very slow. Opening applications and just clicking is laggy, it has a delay of about 5 to 10 seconds
Don't get mad because I don't expect miracles. I want to know your opinion and your experience of using mods on Armani with a focus on speed
Click to expand...
Click to collapse
I've been trying so many roms for this device..
And Minimal OS is the most responsive , fast , and nice battery life
https://forum.xda-developers.com/t/...r-minimal-os-for-redmi-1s-2015-10-11.3150539/