Related
I have flashed some AOSP ROMs like CM and Kang and the although the camera works the quality of pictures especially in low light is terrible.
I have tested a couple of times taking pictures with CM and then the same picture with stock Sense. The ASOP pictures come out with a greenish hue.
This leads to my question, is this something the Devs can improve with time or is this a trade-off of not using a ROM based on the Sense framework?
malimal said:
I have flashed some AOSP ROMs like CM and Kang and the although the camera works the quality of pictures especially in low light is terrible.
I have tested a couple of times taking pictures with CM and then the same picture with stock Sense. The ASOP pictures come out with a greenish hue.
This leads to my question, is this something the Devs can improve with time or is this a trade-off of not using a ROM based on the Sense framework?
Click to expand...
Click to collapse
It can be improved, but there are much more important things to do/fix as of now. And it may require a lot of work. It is at the bottom of a lot of developer's lists.
yeah I totally respect the Devs work and for the most part just wondered if it was technically possible.
thanks for the answer.
Will wait patiently..lol
Same I am very thankful to the Dev's.
Curiously though, so it seems that my best bet is to root my phone but to keep the stock ICS android on it becuase otherwise I lose sense4 and the supposedly better camera software htc preinstalled on it?
Thanks so much! cheers.
RepusJonathan said:
Same I am very thankful to the Dev's.
Curiously though, so it seems that my best bet is to root my phone but to keep the stock ICS android on it becuase otherwise I lose sense4 and the supposedly better camera software htc preinstalled on it?
Thanks so much! cheers.
Click to expand...
Click to collapse
If you like sense, then stick with the Sense-based ROMs. As for the camera, the hardware is still fully capable of taking the same quality pictures whether you are using AOSP or Sense ROMs.
The camera software is different in AOSP and may not have all of the features included in Sense (yet) and the picture quality might be a little worse off in AOSP, but the AOSP ROMs are still in alpha. The developers are working hard to create a stable, fully functional AOSP ROM... it's just going to take a little time. It doesn't hurt to try the AOSP roms out and see for yourself, just don't expect everything to be working flawlessly.
There seems to be quite a few jelly bean roms right now, and without an official leak, I am sure each one has its ups and downs at this point.
I am coming from synergyrom, and want to give JB a try. Since theres is still "beta" I am not sure I wanna try that right away.
Which is the most stable at this point??
Definitely liquid smooth...I've tried others and always revert back to touch wiz stock based roms, and i despise touch wiz...liquid smooth jb is the best I've flashed
Sent from my SCH-I535 using Tapatalk 2
liquid smooth is awesome for aosp JB, but touchwiz there's not much thats super stable imo
thanks for the input so far!
Please note if there are known issues, that might help make decisions too.
Thanks all!!
I like codename. Super smooth, frickin' fast and barely believable battery life! Some apps don't stream audio over bluetooth and you have to enable a couple of Developer options to address screen flickering, but those are truthfully very minor annoyances you'll be happy to overlook when you get a taste of that ROM.
Seriously, try it. http://forum.xda-developers.com/showthread.php?t=1900479
I've tried both liquid and codename. They are both very very similar. I can't find cant difference in customization between the two.
Codename ran a little warm for me, not saying liquid runs cool but still.
The reason I jumped to liquid is because in codename (for me anyway) the 160 character MMS bug still persisted, it does not in liquid.
Sent from my SCH-I535 using xda app-developers app
duarian said:
I've tried both liquid and codename. They are both very very similar. I can't find cant difference in customization between the two.
Codename ran a little warm for me, not saying liquid runs cool but still.
The reason I jumped to liquid is because in codename (for me anyway) the 160 character MMS bug still persisted, it does not in liquid.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can respect that. Haven't tried liquid as the CNA ROM got posted around the time I got this phone. I've heard the 160 character error msg is a bit of a red herring, that the msgs actually do get sent but just say they didn't. Was that your experience or did they actually not get sent?
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
bc760 said:
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well said.
Sent from my SCH-I535 using Tapatalk 2
bc760 said:
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There is a fix for this now but just has not made it's way into all AOSP roms yet. There are in most of the newer AOKP builds right now.
The biggest issue still is the low volume when recording video's. This is an issue in all AOSP roms and has not been fixed yet. I know I also read a lot about speakerphone and in call volume problems but not sure to much about the actual issue.
This is why I am still sticking to an ICS TW Rom. I like knowing everything on my device just works.
The only major thing that keeps from moving to CM10, or Liquid Smooth is the lack of USB Audio. I leave my phone on my dock at work and stream Pandora through the dock's usb audio. I've been using SynergyROM for awhile now, and will probably stick with it until the USB Audio issue is fixed.
AOKP's new build has been great for me. No real issues to report yet...been on it since 3 came out a week or so ago?
i haven't been too impressed jb at all tbh.
Well there's two routes you can go to get your JellyBean fix, and that's either AOSP or TouchWiz.
Touchwiz: You've got two choices.
- You could go with Synergy JB 0.2 beta which is based off the AT&T leaked JB touchwiz build. I personally have not ran it so i can't comment on how well it works, but i use synergy as my touchwiz choice of roms, and was never disappointed by there work, so i'm sure the JB build is working great.
- There is also Jellywiz which is made by Incubus, he's been basing his off the latest leaks, and has a few builds out. One of them is a custom build which just has a few theme changes, and a few other things added in/changed. There's a lot of praise in that thread for his rom, the only bug i had when trying it was that i could not get voice and data to work at the same time (phone calls and web browsing at the same time) But that is because its not based off a verizon leak and until then probably will not work.
AOSP: We'll you've got a lot of options, there's a few here on XDA and then some more on Rootzwiki, so i won't be giving detail on all of them, just a few. But they will all generally 'look' the same, by that i mean because they are all based on AOSP source it'll have the same look to it, since source looks the same.
-CM10: Well it's your basic CM that you've grown to love (or hate ) you can expect nightlies, and things to get fixed in a timely matter. If you used CM7 or CM9 on previous devices then you'll know exactly what to expect. Its built directly from source and you can expect it to be speedy quick.
-AOKP: It's built from source as well just like CM10, but has more options in it, and generally more customization as well. If you use it it'll look a lot like CM10, but it'll have added in bonuses
-CodeNameAndroid: Again built from source, but with codename you've got a ton of customization thrown in, there's a lot of stuff from different AOSP options thrown into it. Right now the Navbar doesn't work without flashing a separate file, but that's not a huge problem since its just a little file to flash. I personally am using it right now and its been great to me, can't really complain about it at all
-LiquidSmooth: Built from source, those that have used a liquid rom before will know exactly what to expect. It will be speedy quick and smooth as hell. You'll find plenty of butter in it as well, they've got there own liquidsettings that'll allow you to do even more customization, and i give them major props, i've currently got them going on my old thunderbolt which is my backup phone, but also used them on my OG Droid and i can vouch that they will provide an amazing rom for users
There are more AOSP Roms over on rootzwiki, but its again the same general thing, each AOSP rom comes from source, but each developer will theme/modify/add/remove/customize to there own liking to provide you with what they feel is the best user experience. The biggest difference between the Touchwiz JB roms and AOSP is that with AOSP you'll have a lot more options going and it'll be stock jellybean, no touchwiz nonsense to hold you back. Some people love the touchwiz stuff and that's fine, but some will love having pure jellybean on there phone and being able to take advantage of that. I'll tell you honestly 100% that AOSP will be faster no matter what touchwiz rom you run.
Oh and kernel wise, i fully stand behind imoseyon's lean kernel for AOSP roms, i've always used imoseyon's kernel's and have always gotten amazing battery life on my GS3 and thunderbolt.
Phew i really hope this helps you with any decision you may have
***If i missed any Touchwiz or AOSP roms i do apologize, i don't know them all off the top of my head, so please don't think that just because i left yours out that i meant it in a bad way***
What are the general downsides with using these JB roms weither it be TouchWiz or AOSP. I'm going to take the jump soon but whats fixed or unfixable? I hear some people say screen flicker and no 3G etc.
Neverendingxsin said:
Well there's two routes you can go to get your JellyBean fix, and that's either AOSP or TouchWiz.
Touchwiz: You've got two choices.
- You could go with Synergy JB 0.2 beta which is based off the AT&T leaked JB touchwiz build. I personally have not ran it so i can't comment on how well it works, but i use synergy as my touchwiz choice of roms, and was never disappointed by there work, so i'm sure the JB build is working great.
- There is also Jellywiz which is made by Incubus, he's been basing his off the latest leaks, and has a few builds out. One of them is a custom build which just has a few theme changes, and a few other things added in/changed. There's a lot of praise in that thread for his rom, the only bug i had when trying it was that i could not get voice and data to work at the same time (phone calls and web browsing at the same time) But that is because its not based off a verizon leak and until then probably will not work.
AOSP: We'll you've got a lot of options, there's a few here on XDA and then some more on Rootzwiki, so i won't be giving detail on all of them, just a few. But they will all generally 'look' the same, by that i mean because they are all based on AOSP source it'll have the same look to it, since source looks the same.
-CM10: Well it's your basic CM that you've grown to love (or hate ) you can expect nightlies, and things to get fixed in a timely matter. If you used CM7 or CM9 on previous devices then you'll know exactly what to expect. Its built directly from source and you can expect it to be speedy quick.
-AOKP: It's built from source as well just like CM10, but has more options in it, and generally more customization as well. If you use it it'll look a lot like CM10, but it'll have added in bonuses
-CodeNameAndroid: Again built from source, but with codename you've got a ton of customization thrown in, there's a lot of stuff from different AOSP options thrown into it. Right now the Navbar doesn't work without flashing a separate file, but that's not a huge problem since its just a little file to flash. I personally am using it right now and its been great to me, can't really complain about it at all
-LiquidSmooth: Built from source, those that have used a liquid rom before will know exactly what to expect. It will be speedy quick and smooth as hell. You'll find plenty of butter in it as well, they've got there own liquidsettings that'll allow you to do even more customization, and i give them major props, i've currently got them going on my old thunderbolt which is my backup phone, but also used them on my OG Droid and i can vouch that they will provide an amazing rom for users
There are more AOSP Roms over on rootzwiki, but its again the same general thing, each AOSP rom comes from source, but each developer will theme/modify/add/remove/customize to there own liking to provide you with what they feel is the best user experience. The biggest difference between the Touchwiz JB roms and AOSP is that with AOSP you'll have a lot more options going and it'll be stock jellybean, no touchwiz nonsense to hold you back. Some people love the touchwiz stuff and that's fine, but some will love having pure jellybean on there phone and being able to take advantage of that. I'll tell you honestly 100% that AOSP will be faster no matter what touchwiz rom you run.
Oh and kernel wise, i fully stand behind imoseyon's lean kernel for AOSP roms, i've always used imoseyon's kernel's and have always gotten amazing battery life on my GS3 and thunderbolt.
Phew i really hope this helps you with any decision you may have
***If i missed any Touchwiz or AOSP roms i do apologize, i don't know them all off the top of my head, so please don't think that just because i left yours out that i meant it in a bad way***
Click to expand...
Click to collapse
thanks a bunch for the big write-up. I do live in an area that is partly 3g, part 4g, so I am a little concerned about these data drops.. Has this been fixed in the AOSP roms mentioned above?
I would hold out a few more weeks for a touchwiz based rom - I tried Incubus' and got a number of random reboots. Cleanrom 2.5 has been working great!
Currently, all the AOSP roms have the same issues -
- data drops, esp on 3g/4g handoff. There were some recent commits that claim to have fixed this, I'm not sure if it did and which rom's include it
- potential for IMEI loss or brick. Again, you should back up IMEI before any flash, I don't think these issues are present on TW
- TW camera is better. There's an AOSP JB camera mod but hasn't been updated for the newer builds yet
- GPS locks. I keep reading about this in the AOSP rom's, I don't know how common this is.
AndyMan386 said:
thanks a bunch for the big write-up. I do live in an area that is partly 3g, part 4g, so I am a little concerned about these data drops.. Has this been fixed in the AOSP roms mentioned above?
Click to expand...
Click to collapse
your welcome. It ended up being a lot longer than I had originally planned. As for data drops, I'm testing a fix right now and I can confirm it works fine
ECrispy said:
Currently, all the AOSP roms have the same issues -
- data drops, esp on 3g/4g handoff. There were some recent commits that claim to have fixed this, I'm not sure if it did and which rom's include it
- potential for IMEI loss or brick. Again, you should back up IMEI before any flash, I don't think these issues are present on TW
- TW camera is better. There's an AOSP JB camera mod but hasn't been updated for the newer builds yet
- GPS locks. I keep reading about this in the AOSP rom's, I don't know how common this is.
Click to expand...
Click to collapse
Data drops were indeed fixed
Imei issues can happen when flashing anything from radios to kernels to roms both touchwiz to aosp. It can also easily be restored.
Tw camera only has a few more features, but in terms of quality their both equal to me. Once the aosp mod is updated it'll be even better.
GPS lock is simple, just get a full lock before flashing aosp and then while having it locked boot into recovery and do your thing.
Neverendingxsin said:
your welcome. It ended up being a lot longer than I had originally planned. As for data drops, I'm testing a fix right now and I can confirm it works fine
Data drops were indeed fixed
Imei issues can happen when flashing anything from radios to kernels to roms both touchwiz to aosp. It can also easily be restored.
Tw camera only has a few more features, but in terms of quality their both equal to me. Once the aosp mod is updated it'll be even better.
GPS lock is simple, just get a full lock before flashing aosp and then while having it locked boot into recovery and do your thing.
Click to expand...
Click to collapse
link to CM10 data fix?
Hello folks.
I am curious if anyone knows of any regularly updated decent kernels / ROMs that have 2-way call recording capability? (Not recorded through the mic.)
As far as ROMs...Jellybean only please.
zath said:
Hello folks.
I am curious if anyone knows of any regularly updated decent kernels / ROMs that have 2-way call recording capability? (Not recorded through the mic.)
As far as ROMs...Jellybean only please.
Click to expand...
Click to collapse
It will never be a kernel issue. This would be done through a ROM or an app.
None of the Jellybean ROM's for the Sensation currently have this as a standard option as far as I know.
Thanks for the response.
Are you sure though? I was under the impression that the kernel was the only thing that mattered.
Based on the information found in these threads:
http://forum.xda-developers.com/showthread.php?t=1441643
http://forum.xda-developers.com/showthread.php?t=1287544
http://forum.xda-developers.com/showthread.php?t=1287544
...and others I have come across in the past.
These are quite old though. I would rather not use a super old kernel. =P
I realize that I will need an app to record phone calls. However if you have ever tried out apps that are designed to record calls on a sensation they only work when you use speakerphone (basically the mic records what the speakerphone pumps out). Last I tried most kernels were incapable of grabbing the audio data internally for some reason.
I think the reason was something along the lines of the initial developers did not include that functionality and it would be a lot of work to include after the fact, tons of extra code etc.
Also! I like your sig!
zath said:
Thanks for the response.
Are you sure though? I was under the impression that the kernel was the only thing that mattered.
Based on the information found in these threads:
http://forum.xda-developers.com/showthread.php?t=1441643
http://forum.xda-developers.com/showthread.php?t=1287544
http://forum.xda-developers.com/showthread.php?t=1287544
...and others I have come across in the past.
These are quite old though. I would rather not use a super old kernel. =P
I realize that I will need an app to record phone calls. However if you have ever tried out apps that are designed to record calls on a sensation they only work when you use speakerphone (basically the mic records what the speakerphone pumps out). Last I tried most kernels were incapable of grabbing the audio data internally for some reason.
I think the reason was something along the lines of the initial developers did not include that functionality and it would be a lot of work to include after the fact, tons of extra code etc.
Also! I like your sig!
Click to expand...
Click to collapse
Well I'll be a son of a gun.....I guess I was wrong about the kernel not being involved. I knew the kernel controlled the audio at the very basic level, but I never realized it would have to be involved in sending that audio to another app.
DO NOT using one of those old kernels you linked though. They are for another phone. It will screw up your ROM and you'll have to restore a back up.
As far as I know all ICS/Sense based kernels can be used for 2WCR. For Gingerbread they needed a patch, but for ICS I think it comes enabled in the source code. Personally I use a Kernel from a banned dev, but I think you could use Faux or Bricked and have 2WCR. Don't worry about them not being updated, there is not much development you can do on a platform that had been out for so long (and I mean ICS 4.0.3).
For 4.1+ and AOSP I have no idea...
papete said:
As far as I know all ICS/Sense based kernels can be used for 2WCR. For Gingerbread they needed a patch, but for ICS I think it comes enabled in the source code. Personally I use a Kernel from a banned dev, but I think you could use Faux or Bricked and have 2WCR. Don't worry about them not being updated, there is not much development you can do on a platform that had been out for so long (and I mean ICS 4.0.3).
For 4.1+ and AOSP I have no idea...
Click to expand...
Click to collapse
I didn't know that. Thanks a bunch!
Recently I had a bit of time on my hands (lack of time is most often my biggest problem ><) so I started trying out some ROMs to see if any had 2WCR. What I was looking for in order of importance: Jelly Bean, ROM that was upgradable to Pdroid 2.0/OpenPdroid, and 2WCR. I ended up using [ROM][CM-10.1][JB 4.2.1][KANG] NameLess Bean [05.02.2013] so far it's a great ROM. Doesn't bench quite as high as my last ROM. I plan on installing some of the performance / battery mods out there once I have been rocking this ROM a week or two and know which bugs it already has =P (so that I can know if any of the mods create bugs heh).
I ended up using the app CallRecorder (skvalex) after trying several other apps which didn't work so well. CallRecorder only has one problem I've noticed, the files it saves do not show up within the app. If you go to the saved directory they are all there and work fine though. /storage/sdcard0/voix by default.
Hopefully this post will be helpful for sensation users looking for 2WCR in the future. Thanks again papete!
good
good innovative feature
I use CallRecorder app too but its very hard to hear what other people are saying, you need to use speakerphone.
I really don't understand why is this feature not fully implemented on all android phones, i often forget what i talked with someone few minutes before, so i need to recheck.
mladen8 said:
I use CallRecorder app too but its very hard to hear what other people are saying, you need to use speakerphone.
I really don't understand why is this feature not fully implemented on all android phones, i often forget what i talked with someone few minutes before, so i need to recheck.
Click to expand...
Click to collapse
One of the reasons it's not implemented on all phones is because it's illegal to record calls without consent in a lot of places.
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
sandys1 said:
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
ImagioX1 said:
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
Click to expand...
Click to collapse
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
sandys1 said:
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
Click to expand...
Click to collapse
What hardware compatibility do you mean? I don't know whether a bounty is going to work, the devs we have working on these ROMs are already doing their absolute best to bring us the best software possible. Also, some of these issues are caused at an upstream level and are completely out of their control.
Sent from my Evita
Now, lemme explain. I've seen this question asked in other forums as well, but I haven't seen an answer from a dev who would really know more about those specifics.
No, I'm not talking about AOSP theme flashed on TouchWiz. I mean, back on KitKat this WAS something I did often, and will probably do it again, but I'm talking totally swapping out some frameworks/libraries/under-the-hood stuff? Nexus 5 is the fastest device I've ever laid my hands on, and it's pure AOSP, but it camera was behaving... odd... from time to time.
I guess camera behavior scripts are really not easy, I've got a friend who's working precisely that, and he has a lot of headaches.
I'm talking probably nonsense, because TouchWiz is closed source except for the kernel, and modding AOSP frameworks to work with the TouchWiz ones (without knowing the code behind the latter) would be a lot of guessing and flashing again and again until it happens that the AOSP code you wrote is compatible with TouchWiz.
But mostly: the Nexus family is fast as hell, the Samsung firmware might be somewhat slower (not so sure after their take on Lollipop, DAMN dat thang actually can be fast!), but due to it's closed source it has more features (the stock camera, the S-Pen frameworks and software).
And last, but not least, if a dev reads this discussion and the thought of having to write a kernel for that passes through his head, he would probably react this way:
Code:
#define true false //Happy debugging suckers
...and do something actually useful with his time.
Your thoughts on the matter?
What you say is true, i was thinking of this three days ago when i flashed dirty unicorns rom, fantastic rom, fast as hell, but the camera on AOSP is soooo bad, and s-pen and s-view cover dont work, It's really so hard to port the stock camera app on AOSP??
I recall on the S2 there was an attempt to get the stock TW camera onto non-TW roms. If I recall rightly they had moderate success, with just a few of the features not working.
For me getting SPen features on non-TW roms is far more important. It's the only reason I won't go near non-stock roms on the Note 3.
The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has.
There was a TW based for for the s2, i9100. I think it was called chameleon rom? It was basically just Stock TW with the samsung camera app, but aosp dialer contacts, systemui etc
Beefheart said:
For me getting SPen features on non-TW roms is far more important. It's the only reason I won't go near non-stock roms on the Note 3.
Click to expand...
Click to collapse
THIS WOULD BE IDEAL.
Weirdly, i have seen the SPen SDK Nearly in all Lollipop Samsung roms, even on S4/S5, WHY?
celderic said:
There was a TW based for for the s2, i9100. I think it was called chameleon rom? It was basically just Stock TW with the samsung camera app, but aosp dialer contacts, systemui etc
Click to expand...
Click to collapse
Is it possible to bring AOSP systemui to a TW ROM? I mean, not just a theme, for example, the notifications panel behaviour, lockscreen, settings menu, etc.
WideBRs said:
Is it possible to bring AOSP systemui to a TW ROM? I mean, not just a theme, for example, the notifications panel behaviour, lockscreen, settings menu, etc.
Click to expand...
Click to collapse
^ this is precisely what I'm talking about.
A dev would have to get the AOSP frameworks and libraries and modify them in such a way that they'd work with the TouchWiz frameworks AND kernel.
@Morningstar said it a couple of posts above yours:
"The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has."
sirobelec said:
^ this is precisely what I'm talking about.
A dev would have to get the AOSP frameworks and libraries and modify them in such a way that they'd work with the TouchWiz frameworks AND kernel.
@Morningstar said it a couple of posts above yours:
"The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has."
Click to expand...
Click to collapse
but what would be simpler and more efficient? AOSP features to TW rom or vice versa? I think, from user side, i would be more interested in getting TW (like Spen) to AOSP I dont use many TW features
As someone who used to make hybrid ROMs, I can tell you porting touchwiz to aosp is near enough impossible. Porting aosp stuff to touchwiz is easier. Tw camera to aosp just won't happen
Certain Touchwiz apps rely on code implemented across nearly all the framework files
Libs as well? No chance
Reverse engineering thousands of individual files and even more lines of code makes it a task comparable to setting up your own os...and smali is nothing like Java...so its not an easy way of getting touchwiz source code at all
DSA said:
As someone who used to make hybrid ROMs, I can tell you porting touchwiz to aosp is near enough impossible. Porting aosp stuff to touchwiz is easier. Tw camera to aosp just won't happen
Certain Touchwiz apps rely on code implemented across nearly all the framework files
Libs as well? No chance
Reverse engineering thousands of individual files and even more lines of code makes it a task comparable to setting up your own os...and smali is nothing like Java...so its not an easy way of getting touchwiz source code at all
Click to expand...
Click to collapse
Just for the record, back when I had an S4, the phone spent the most time with BlackBox, and it's exactly your ROM which made me ask this question, but I didn't have much hope you'd answer yourself.
Huge thanks for the input.
This thread could be very much eased down with the release of the Galaxy S6.
Sammy agrees for less bloat and less distance from AOSP, quoting the "rumours", it will be 99% Google, which most probably is a result of their cross licensing deals for patents.
March seems definitely exciting, even 5.1 can be in sight if Sammy gets a bit Nexus-ish, which will most definitely be the only reason i would go for Exynos, otherwise, no Sammy without openly documented hardware.
PlutoDelic said:
This thread could be very much eased down with the release of the Galaxy S6.
Sammy agrees for less bloat and less distance from AOSP, quoting the "rumours", it will be 99% Google, which most probably is a result of their cross licensing deals for patents.
March seems definitely exciting, even 5.1 can be in sight if Sammy gets a bit Nexus-ish, which will most definitely be the only reason i would go for Exynos, otherwise, no Sammy without openly documented hardware.
Click to expand...
Click to collapse
They say it will be as _fast_ as a Nexus, not that they're going AOSP. No one here thinks Sammy would leave their beloved TouchWiz.
Of course, if come Sunday I receive the biggest plot twist in recent Android history and the S6 ships close-to-AOSP, I'll be one of the happiest people alive, but I don't believe it will happen. xD
WideBRs said:
Is it possible to bring AOSP systemui to a TW ROM? I mean, not just a theme, for example, the notifications panel behaviour, lockscreen, settings menu, etc.
Click to expand...
Click to collapse
not impossible but really hard to do hence why nobody has done it
sirobelec said:
^ this is precisely what I'm talking about.
A dev would have to get the AOSP frameworks and libraries and modify them in such a way that they'd work with the TouchWiz frameworks AND kernel.
@Morningstar said it a couple of posts above yours:
"The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has."
Click to expand...
Click to collapse
Im using part of applications AOSP on TW ROM like contacts, Phone Dialer, MMS, wisard and some mods on framework styling but we can t get the receptive calls and provider and UI for example
Sent from my GT-I8552B using XDA Free mobile app
sirobelec said:
They say it will be as _fast_ as a Nexus, not that they're going AOSP. No one here thinks Sammy would leave their beloved TouchWiz.
Of course, if come Sunday I receive the biggest plot twist in recent Android history and the S6 ships close-to-AOSP, I'll be one of the happiest people alive, but I don't believe it will happen. xD
Click to expand...
Click to collapse
So far we havent seen anything software wise from the S6, seems like they are hiding things well, the moment N4/S5 got released we straight away knew how the UI looked like.
I think Sammy knows that the only way to sell exynos and not load other brands ARM adaption is by being more open. I know this is "wishful thinking" up to a point, but there is no way (most) Snapdragon N3/S5 users will upgrade to Exynos S6, and i hope they are aware of that.
to summarize:
Slighlty Debloated
TouchWiz Optimised
It's not that the links say much, but as i mentioned earlier, there has been a weird Patent agreement between Google, Cisco and Samsung (and Microsoft to a point), and S6 might be the first device to use them properly.