Let's get this started! Unfortunately, all of the devs previously working on this have either left for a new device or given up, but that doesn't mean there aren't others out there with the experience and motivation needed!
@wickedninjalo had the great idea to make a bounty as a reward.
Some requirements (UP FOR DISCUSSION!):
Make it Open Source, preferably with MIT or Apache 2.0.
Doesn't have to look exactly like the stock version, but functionality should be similar.
@USA-RedDragon's original intent) Make it extensible by third parties! ie, other people should be able to write extensions for it. This isn't completely necessary, but it'd be amazing to have.
Don't just rip the current LGSignBoard and related APKs from Stock and force them to work on AOSP somehow. That runs the risk of a copyright strike, and it doesn't satisfy most requirements.
If you think you have something, PM me! I'll give you a link for a Telegram group where you can share what you have and it can be tested out.
Anyone interested in testing potential builds, also contact me for the Telegram link.
Current list of supporters:
$20-$40 -- @wickedninjalo
$20 -- @Gabe2014
$10 -- @AngryManMLS
$20 -- @uppon2
$20 -- @wuwtk
$15 -- @joachim123
$5 -- @askermk2000
$50 -- @sobriquet506
$100 -- @tymestopm
$20 -- @Stonkers
$20 -- @emtownsend
$100 -- @philiptibbs
$20 -- @Aaren11
$40 -- @rholm
$20 -- @slaya811
$25 -- @mdl054
$5 -- @TheHamPimp
$490 -- Total
Current devs:
@Blaises
@Zacharee1
Any test builds that are available will be posted at https://zwander.tk/#losdownloads. These are ARB0 builds!
Zacharee1 said:
There's no second screen mod available yet. This thread is the home of development updates and maybe the future home of the mod itself, once it's complete.
So as most of you probably know, the second screen doesn't work on AOSP-based ROMs. On earlier versions of CMRemix, LineageOS and Resurrection Remix, the main display image even oveflowed into the second screen area. This happened because it's actually the same physical panel, but the top 160 rows don't reach all the way across. In the newer AOSP builds, the second screen is effectively disabled, so nothing overflows into it, but since it's not functioning, the backlight and digitizer are disabled, creating a weird dark area on the main screen and a touch deadzone. The ROMs still work amazingly, though, and if you can live without the second screen or are daring enough for dual boot, go try them out.
But since one of the main features of this phone is that second screen, it's pretty natural that we'd all want it there on AOSP too, right? Well unfortunately, it isn't as simple as copying some APKs from Stock. There's framework stuff, kernel code and maybe more that needs to be recreated without infringing on LG's copyright. Luckily, developers have taken it upon themselves to work together on creating an API for the second screen that will work on AOSP ROMs.
It's probably going to be a rather long process, since we don't really fully know how the second screen works, and its functionality has to be replicated without plagiarizing the source. Patience is going to be key. I've created this thread so that I can provide updates on the progress that has been made. Once there are test builds available, they'll be made available here, and this thread will probably be moved to the Development section.
If you have experience in Android development and you want to help out, send a PM to any of these users:
@Zacharee1
@USA-RedDragon
(I need to ask the others if they are willing to receive PMs. Please don't PM any devs not on this list.)
Thanks to the developes currently working on this project!
@USA-RedDragon
@Dameon87
@albinoman887
@jthrasher47
Click to expand...
Click to collapse
Btw. More than just framework code. It's also binaries that need to be reverse engineered and none of us are too good at reading assembly
Sent from my LG-H910 using Tapatalk
RIght now is mainly just the planning stage. So far, the rough idea is to decompile the second screen source, figure out how it works, get it working on AOSP, and then recreate the code in a way that will probably work better on AOSP and won't infringe on LG's copyright. There's no actual development yet, but there's a path set out to follow.
I hope progress is (slowly) being made on this. I very much hope you succeed. For one I hope what you generate is a great deal more configurable. LGE does provide some ability to configure the second screen, but I'm underwhelmed. Weather I can find by going outside, so that doesn't help much; plus this means a partner of LGE is getting information from the device...
One hopefully useful tidbit. At the head of LineageOS's kernel branch for the V20 they've disabled the second screen. Personally I find the way that change was done rather anti-social, so that is how I address it. This actually provides a bit of insight into how to access the second screen, it is simply one big screen with a separate backlight.
Pretty sure it's been done but due to copyright not being put out.
storm68 said:
Pretty sure it's been done but due to copyright not being put out.
Click to expand...
Click to collapse
No it hasnt been done.
me2151 said:
No it hasnt been done.
Click to expand...
Click to collapse
I disagree ?
storm68 said:
Pretty sure it's been done but due to copyright not being put out.
Click to expand...
Click to collapse
Have you a link to confirm that?
Any more progress? This is the main thing that keeps me from using aosp roms as my primary rom. I mainly use the second screen for notifications and clock at night. Since we don't have a notification led it makes it hard to know when I have a new message etc since I disable sound notifications.
The_Keeper86 said:
Any more progress? This is the main thing that keeps me from using aosp roms as my primary rom. I mainly use the second screen for notifications and clock at night. Since we don't have a notification led it makes it hard to know when I have a new message etc since I disable sound notifications.
Click to expand...
Click to collapse
Nothing yet, sorry.
That's unfortunate :/ you guys that use an aosp rom what do you do about notifications?
Sent from my LG V20 using XDA Labs
The_Keeper86 said:
That's unfortunate :/ you guys that use an aosp rom what do you do about notifications?
Sent from my LG V20 using XDA Labs
Click to expand...
Click to collapse
I use ambient display lol so when I pick up the phone I get shown a screen with notifications. I wish we had the second screen for notifications at least but It's fine without
xxxrichievxxx said:
I use ambient display lol so when I pick up the phone I get shown a screen with notifications. I wish we had the second screen for notifications at least but It's fine without
Click to expand...
Click to collapse
I might look into that thanks. I wish we do too obviously lol. Glad I have more choices than I did with my Note 5 though.
Sent from my LG V20 using XDA Labs
storm68 said:
I disagree ?
Click to expand...
Click to collapse
This is typically an instance where one provides a source/proof to back up their statement. Just stating "I disagree" doesn't cut the mustard.
elijah420 said:
This is typically an instance where one provides a source/proof to back up their statement. Just stating "I disagree" doesn't cut the mustard.
Click to expand...
Click to collapse
No need! I can disagree as a statement of opinion without proving anything... I disagree in my sole opinion. Nuff said. Have a great week and weekend. ?
storm68 said:
No need! I can disagree as a statement of opinion without proving anything... I disagree in my sole opinion. Nuff said. Have a great week and weekend. ?
Click to expand...
Click to collapse
Well sure. You can say whatever you'd like, but when you make assertions that try to carry opinion as fact, be prepared to have someone ask for a source.
elijah420 said:
Well sure. You can say whatever you'd like, but when you make assertions that try to carry opinion as fact, be prepared to have someone ask for a source.
Click to expand...
Click to collapse
Again... My opinion. My allocation to provide them or not. No need to be interrogated. Look! Another opinion! No need to continue in conversation to clog the thread.
Wish there was some headway into getting the second screen working on AOSP. AoD is a clever work around, but the second display was given it's own seperate, low power backlight specifically to get around the drain of powering the main panel.
I'd be happy using just AoD in a pinch if the second display was at least usable as extra screen space during regular operation, there are plenty of apps and launcher tweaks that could provide a taskbar or app shortcuts, if the actual screen real estate was accessible.
Well seems if you flash a stock kernel over aosp the second screen just becomes part of the entire screen so maybe somewhere in the kernel difference can be found as to what's delegating what to where
Sent from my LG-H918 using Tapatalk
whojabacod6 said:
Well seems if you flash a stock kernel over aosp the second screen just becomes part of the entire screen so maybe somewhere in the kernel difference can be found as to what's delegating what to where
Click to expand...
Click to collapse
The second screen is the same physical panel. By default, AOSP treats it all as one and stretches content into the second screen. AOSP developers have added kernel modifiers to prevent that from happening.
Related
I don't want to come out as needy and disrespectful. This is just a request.
Can anyone creat a custome ROM that is as close to stock as possible?
With a few exceptions. Of course remove all the bloat ware, creat a new status bar by removing the t-mobile logo that waists space and the previously used apps (we all know how to hold the home button), and lastly make a numeric battery. Try not to use the circle batterys but stay as close to the original as possible.
Ooh as well fix sence 3.0 and have lockscreen icons.
Also I do use the caller I'd feature T-Mobile provides I don't want $4 down the drain so.please keep that function.
Sent from my mt4gs
patience, young jedi... I'm sure someone will come out with something soon. I'd like exactly what you're asking for, too!
if I ever get some free time (not likely in the next 2 weeks) I will start cooking up some roms for us. I'm in the middle of a big transition right now and just haven't had time to sit down and start tearing roms apart. -____-
op: have you checked out the UOT kitchen? you can accomplish most of the status bar and battery tweaks you want through it.
the bloatware I would just uninstall with TiBu or any other program capable of uninstalling system apps.
the sense 3.0 lockscreen... not too sure. I've always been an aosp guy so I haven't spent much time modding sense.
Im in the same boat as queen I have something in the works also soone as I finish this rom for my epic !
Sent from my myTouch_4G_Slide using XDA Premium App
No rush guys this phone isn't going anywhere. I would love to learn how to cook. I need to get over the big learning curve. The only reasone I ask is because there are specific files I don't know if are usefull or not. Like for example the new caller id feature I don't know witch files are associated with it. I do freeze as much as I can in tibp but I feel like its still slowing the phone down or taking up space. I've been a windows user a long long time and feel like when you uninstall something it's not the same as having a clean install. I can't get over that mindset. BTW thanks for the quick responce.
unclespoon said:
patience, young jedi... I'm sure someone will come out with something soon. I'd like exactly what you're asking for, too!
Click to expand...
Click to collapse
You and I think a like in everything. I'm curious as to how your phone looks like boot screen and what not
Sent from my mt4gs
Sent from my mt4gs
Madblaster6 said:
... create a new status bar by removing the t-mobile logo that waists space and the previously used apps (we all know how to hold the home button), and lastly make a numeric battery. Try not to use the circle batterys but stay as close to the original as possible.
Click to expand...
Click to collapse
Those two changes require a framework hack, which requires another hack in services to disable signature verification. I've always wanted to remove those damn "Recent Apps" from the status bar, but only recently learned how to disable signature verification for when the framework is modified.
We have some amazing devs I'm sure sence 3.0 framework will be easly modified. Although I'm sure you can change the status bar without framwork mods like they did on the MyTouch 4g. Unless I'm wrong. Also thanks for revolution.
Sent from my mt4gs
Madblaster6 said:
I don't want to come out as needy and disrespectful. This is just a request.
Can anyone creat a custome ROM that is as close to stock as possible?
With a few exceptions. Of course remove all the bloat ware, creat a new status bar by removing the t-mobile logo that waists space and the previously used apps (we all know how to hold the home button), and lastly make a numeric battery. Try not to use the circle batterys but stay as close to the original as possible.
Ooh as well fix sence 3.0 and have lockscreen icons.
Also I do use the caller I'd feature T-Mobile provides I don't want $4 down the drain so.please keep that function.
Sent from my mt4gs
Click to expand...
Click to collapse
Until ROMs start coming out, use titanium backup to uninstall any of the bloatware you don't want. I uninstalled just about every app on my phone, and installed better versions of the ones I wanted, and in one case I uninstalled a stock app, then downloaded the same app from the market.
After getting rid of all the bloatware I noticed drastic battery life improvement, so I started looking at other things that were always running in the background, two of them were the preinstalled note pad app and Google Maps. I would stop them, and they would be back running in a matter of moments. I uninstalled both of them, downloaded Google Maps and ColorNote. For some reason, Maps is never running in the background any more. Not sure why that worked, but it did.
Well as I said in the post before I'm using the freeze function for now so I don't ruin anything. It goes into why I don't like doing that.
Sent from my mt4gs
nbetcher said:
I've always wanted to remove those damn "Recent Apps" from the status bar,
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=15417961&postcount=107
I wish I knew what that ment.
Sent from my mt4gs
Madblaster6 said:
I wish I knew what that ment.
Sent from my mt4gs
Click to expand...
Click to collapse
Means you have to copy SystemUI.apk to your computer, decompile it, re-write part of the code, re-compile it back into an .apk, then install it on the phone.
One of those "easier said then done" things, but not terribly difficult if you read through the thread and take the time to install the tools you need to your computer.
I'm intrigued by this, but there are other things on my list for this phone before I get around to something like this.
Is it just me or is the mt4gs forum dead? I know its the summer and all but wow. Not an attemp at anything. I'm not talking about custome roms. I'm talking about everything.
Sent from my mt4gs
Yeah it's awful. I'm at work all day refreshing for new content, and I'm left disappointed about 90% of the time. I need something to flash!!!
I've actually just decided to try recruiting devs from the Sensation forum. Given the similarity between the devices, I'm hoping that it wouldn't be too difficult for someone out there to help us out...
http://forum.xda-developers.com/showthread.php?t=1229985
Madblaster6 said:
Is it just me or is the mt4gs forum dead? I know its the summer and all but wow. Not an attemp at anything. I'm not talking about custome roms. I'm talking about everything.
Sent from my mt4gs
Click to expand...
Click to collapse
I wasn't expecting much dev support here in the beginning. I think ports will start showing up slowly but don't expect it to be anything like the Sensation subforum.
it's a shame because this is a killer device that can run anything thrown at it. with some patience and luck we'll get some devs who are interested in creating things for the slide... maybe from the G2 section once more people start changing over.
at least there's really nothing function-wise on the stock rom that makes it unusable for me. once the bloat is gone and ADW ex (or whatever home replacement you like) is loaded, it's pretty much all I need.. some aosp love would sure be nice though for me.
Yea, but it's a new device...and an expensive one so a lot of people don't have one yet.
For early adopters it's hard sometimes, my approach has just been to try to document everything as thoroughly as possible so that when devs do come, they have less work to do.
Of course, the best way to get something done is to do it yourself - i'd like to make my own ROM for this device, but i'm a long way from that. It'll happen, but i'm pretty positive that by the time I get it all figured out Cyanogenmod will have been ported to this device.
Still won't stop me from doing it though, i'm too curious.
Meantime, posting up everything we can learn about the phone will help in getting a custom ROM when a dev willing to do so comes through here.
I was wondering the same thing. I'm coming from the HD2 and the Galaxy St Vibrant so anyone who knows those phones understands.... I was thinking this forum would be a little more lively.
I've gone from refreshing a lot to refreshing once a day.
Sent from my myTouch_4G_Slide using XDA Premium App
Yeah. Totaly. Look at the phones I've owned in the signature. I remember going back to the razer the forums were packed with hex mods and java games. Maybe not this specific one. Still this is the biggest mt4gs forum.
Someone above noted that the phone is new and expensive. That is definitely a factor. Also, from what I saw, T-Mobile didn't really market this phone heavily before it came out. Right at the launch I saw a good amount of ads but not long before. Like the SGS2 has gotten real advertising saturation. This phone is a real contender but because it doesn't have a huge screen it received, and continues to receive, less attention.
Things will pick up but at this point I have prepared myself for a wait. Devs will eventually get the word on how good it is and then things will pick up but it will take some time. For me, the hardware we have is worth the wait.
I did have a thought. Find out if there are devs working on this phone. If not, we could look at collectively getting a phone to a dev that could get it moving.
Sent from my myTouch_4G_Slide using XDA Premium App
Paul (or anyone who knows)...
How close are you to a Beta version of your ICS port for the OG Transformer?
I think you have done more than anyone in trying to get this stable before Asus releases their version, and definitely offer a way to get Root on the TF101 ICS.
I really just wanted to start a thread that would allow for Version updates to your port, where people can see a status from the developer himself!
Thanks!
Jeff
--
"I've donated to Paul...Have you??"
It's probably close. What's supposed to work, works.
Sent from my Transformer TF101 using Tapatalk
If you are a gamer stay clear for awhile yet or atleast till official comes and devs can kang some parts
Sent from my Transformer TF101 using xda premium
gVibeR said:
How close is Paul Burton to Beta?
Click to expand...
Click to collapse
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
gVibeR said:
How close are you to a Beta version of your ICS port for the OG Transformer?
Click to expand...
Click to collapse
Oh right, the ROM. Beta is a blurry line, I may not even use it and just keep incrementally improving it until it feels like RC time (and when I say RC I mean a build I actually consider suitable for final release, not the linux "release candidate but we'd never actually consider releasing this" terminology). I think once I get libsensors & libcamera written the hardware support will all be there at least in a basic form and then polishing and fixing smaller things will improve it quickly. I'm hesitant to put a timescale on it - I can't spend the time of a full time job on this and the time I do spend on it is a little sporadic. I'd hope to have sensors working within the next week or so, if that helps. I'm also planning to look at doing OTA updates of some sort now that it's basically usable for common tasks (for some people), to keep people updated easier and perhaps lighten the load on my web host by doing deltas.
I apologise for the terrible joke above...
Without access to the full source code for the drivers, any ROM based off of generic Android will never be Beta or better...
Paul's ICS port is from the standard Google ASOP tree, with lashed in binaries from other sources. What Asus deliver will be built for the specific platform.
There is a HUGE difference.
My experience of Paul's ICS was quite good, the biggest gripe for me, was the REALLY choppy sound playback, which was a deal-breaker for me, and I went back to honeycomb.
im not to sure about the binaries just being ported in i think paul is writting a whole lot of his own stuff, i could be wrong tho. i read a txt where he talked about writting his own drivers for everything cuz asus code is sloppy, he said he would prefer write his own than just plug in binaries.
CrazyPeter said:
Without access to the full source code for the drivers, any ROM based off of generic Android will never be Beta or better...
Paul's ICS port is from the standard Google ASOP tree, with lashed in binaries from other sources. What Asus deliver will be built for the specific platform.
There is a HUGE difference.
My experience of Paul's ICS was quite good, the biggest gripe for me, was the REALLY choppy sound playback, which was a deal-breaker for me, and I went back to honeycomb.
Click to expand...
Click to collapse
Umm, with all due respect - you're wrong. Asus aren't necessary. The only things remaining as binaries are the graphics drivers and they're from nvidia.
paulburton said:
Umm, with all due respect - you're wrong. Asus aren't necessary. The only things remaining as binaries are the graphics drivers and they're from nvidia.
Click to expand...
Click to collapse
So Asus have released the sources for ICS Wifi, Bluetooth, Audio, Camera and sensor drivers?
That's news to me, or are using using the honeycomb sources and patching them up with sticking plasters to work with ICS?
CrazyPeter said:
So Asus have released the sources for ICS Wifi, Bluetooth, Audio, Camera and sensor drivers?
That's news to me, or are using using the honeycomb sources and patching them up with sticking plasters to work with ICS?
Click to expand...
Click to collapse
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
paulburton said:
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
Click to expand...
Click to collapse
Paul Burton, serving up wanton coding justice to non-believers like it ain't no thang.
Keep up the good work, but I do think you need to assign a cool name to this project.
paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
Click to expand...
Click to collapse
Too funny, lol. Keep up the good work, and thanks for the posts. Always informative.
paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
Click to expand...
Click to collapse
LMAO a good dev with a great sense of humor! Or great dev with good sense of humor, I can't tell which
paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
I apologise for the terrible joke above...
Click to expand...
Click to collapse
Don't apolgize, that's what i call the so famous british humour . Please keep developping and joking that way Sir Burton.
paulburton said:
People outside of asus can write code too
Click to expand...
Click to collapse
Awesome! !!!
You sir need a TARDIS. That was Brilliant.
paulburton said:
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
Click to expand...
Click to collapse
Just a side note (and I'm not I repeat not complaing about this thread) for those who are asking for updates (nobody asked for updates here) about Paul's releases you should find them when they appear. It does not make it easier for him to complete them if he has to answer a zillion posts about when it will be ready (still not complaining) for release. Think about this...... he could be watching tv or going to the pub or doing stuff that he really needs to do like school (still not complaining) instead of coding.
Again I would like to emphasize that I am not complaining about this.
Oh and Paul how were your exams?
Sent from my Infected Galaxy Y using Tapatalk
Dreamboxuser said:
Just a side note (and I'm not I repeat not complaing about this thread) for those who are asking for updates (nobody asked for updates here) about Paul's releases you should find them when they appear. It does not make it easier for him to complete them if he has to answer a zillion posts about when it will be ready (still not complaining) for release. Think about this...... he could be watching tv or going to the pub or doing stuff that he really needs to do like school (still not complaining) instead of coding.
Again I would like to emphasize that I am not complaining about this.
Oh and Paul how were your exams?
Click to expand...
Click to collapse
It's true, my life contains things other than writing this ROM. Fortunately for you guys I don't own a TV
Exams went well thanks, all are above 70% (so 1st class) and the one I thought went horribly turns out to be my best grade. Odd
What kind of student are you, Paul?
asdfuogh said:
What kind of student are you, Paul?
Click to expand...
Click to collapse
Read his profile.
http://forum.xda-developers.com/member.php?u=4421777
Hey Paul,
Just wanting to keep everyone up to date...
Could you give us a status of what still is not working with your latest release Spark?
Now that you have a name for your rom, and have replaced the original warning with your new one, would you say this release is usable for most things?
Thanks a ton for your work...who needs Asus, we got Paul !!
Is there a multi-window feature MOD for the asus tf700 . It is a feature in Samsung Galagxy Tab 10.1 and newly implemented in the new update of the JB in galaxy S3. I flashed a MOD in my Galaxy s2 and the feature works just fine . So is there any MOD for this feature in asus tf700 ??
I really need it in my tab.
amqz2010 said:
Is there a multi-window feature MOD for the asus tf700 . It is a feature in Samsung Galagxy Tab 10.1 and newly implemented in the new update of the JB in galaxy S3. I flashed a MOD in my Galaxy s2 and the feature works just fine . So is there any MOD for this feature in asus tf700 ??
I really need it in my tab.
Click to expand...
Click to collapse
No, there is not, and there probably will not be. No non-Samsung device has ever been able to do it, so if this is mission critical for you, off to Samsung your dollars go.
MartyHulskemper said:
No, there is not, and there probably will not be. No non-Samsung device has ever been able to do it, so if this is mission critical for you, off to Samsung your dollars go.
Click to expand...
Click to collapse
So, what exactly is it that makes this specific to Samsung devices?
danger-rat said:
So, what exactly is it that makes this specific to Samsung devices?
Click to expand...
Click to collapse
The framework. There's another thread going on about this already. I'm not going into a fork here.
Also, keep in mind what happened to Overskreen. That makes it higly unlikely that anyone is going to invest the immense time and resources needed until Google's stance on the matters softens.
EDIT_BY_INTERJECTION: forgot to say it's in the CleanROM Inheritance thread, as a feature request. And a no-no.
To specifically answer your question, by the way: I guess Samsung feels large and powerful enough to go against Google. Their partnership might help, I dunno.
It's not a technical thing in itself, as we have developers aboard that could pull this off. Hell, we have devs aboard trumping the engineers of the manufacturers themselves, so that says something. It's politics.
So, maybe a link to the other thread would be a more useful and appropriate response?
From your response, it's still not clear what makes this specific to Samsung devices, since all ROMs I've worked on contain a framework, and it clearly isn't specific to TouchWiz.
I realize that Google has quashed attempts at this in the past, specifically Overskreen, but the fact that there are working options out there could be indicative of a change in philosophy, perhaps?
As far as the CleanROM thread, all I saw was sbdags ask for a link and then you (in typical fashion) insert your option in a less than helpful manner. Humble up. If you don't plan on helping, I don't see why you would take the time to be unpleasant...
I was brought up with the understanding that if you can't say anything nice, then don't say anything at all...
EDIT: one long reply with argumentation you wouldn't understand or accept anyway, I think. Thought the better of it. I'll take your post as a shining example of what a constructive post does not look like, stupid motto and such incorporated.
It is a touchwiz thing. Touchwiz is not just a launcher slapped on top it is built into the framework of Samsung firmware, much like sense is built into HTC frameworks. You can't use sense widgets on non sense ROMs and you can't use multi screen on non Touchwiz based ROMs.
I'm not even knowledgeable enough (yet) to concur with you (although I thought the same this morning, I'd dare not put that in writing for sheer terror of saying something so stupid I'd be a "Chinese volunteer" for the first no-return mission to Saturn). Thanks for chiming in, though.
sbdags said:
It is a touchwiz thing. Touchwiz is not just a launcher slapped on top it is built into the framework of Samsung firmware, much like sense is built into HTC frameworks. You can't use sense widgets on non sense ROMs and you can't use multi screen on non Touchwiz based ROMs.
Click to expand...
Click to collapse
Thanks sbdags - I had pretty good idea of the answer, I was just wondering if Marty did...
A few people had Cornerstone running on the Prime earlier in the year, so I didn't think that dual screen was completely impossible, however the odds are stacked up against a daily driver right now...
danger-rat said:
Thanks sbdags - I had pretty good idea of the answer, I was just wondering if Marty did...
A few people had Cornerstone running on the Prime earlier in the year, so I didn't think that dual screen was completely impossible, however the odds are stacked up against a daily driver right now...
Click to expand...
Click to collapse
I have seen the concepts of Cornerstone. I would love to see that being imlemented in a ROM for or Infinities. I do use StickIT to be able to watch videos while still using the rest of the screen but a full on Multi Tasking feature would be awsome if possible. I know that the 1 GB RAM limit might hinder it a bit but who knows, mabey sbdags could look into it for a future feature in his CleanROM Inheritance ROM's.
danger-rat said:
From your response, it's still not clear what makes this specific to Samsung devices, since all ROMs I've worked on contain a framework, and it clearly isn't specific to TouchWiz.
Click to expand...
Click to collapse
sbdags said:
It is a touchwiz thing. Touchwiz is not just a launcher slapped on top it is built into the framework of Samsung firmware, much like sense is built into HTC frameworks.
Click to expand...
Click to collapse
danger-rat said:
Thanks sbdags - I had pretty good idea of the answer, I was just wondering if Marty did..
Click to expand...
Click to collapse
So may I conclude I had a better idea of what the answer was than you? I tell you it's a framework-dependent feature, you say it is "clearly NOT Tochwiz-dependent". Next thing, sbdags tells you TouchWiz is built into the framework, and then you say <chuckle> that you knew that all along, but was just wondering if I knew that. At least I had a good laugh: you twist and turn and twist a bit more. You can throw around your morals all you want, but on the technical side of things, it's either this or that, and there's not that much room to verbally wiggle into being correct. I'd say you have been corrected.
MartyHulskemper said:
So may I conclude I had a better idea of what the answer was than you? I tell you it's a framework-dependent feature, you say it is "clearly NOT Tochwiz-dependent". Next thing, sbdags tells you TouchWiz is built into the framework, and then you say <chuckle> that you knew that all along, but was just wondering if I knew that. At least I had a good laugh: you twist and turn and twist a bit more. You can throw around your morals all you want, but on the technical side of things, it's either this or that, and there's not that much room to verbally wiggle into being correct. I'd say you have been corrected.
Click to expand...
Click to collapse
Wow... almost don't want to add anything to this flaming thread, but am also a user who is looking for some way to do this stuff on the tf700. Here is a thread that explains most of what the "framework" is and what it does. It is worth mentioning that things in android are already built for multiwindow interfaces but the options for the support are not turned on and some of the functionality is broken. The biggest hangup for this working is the app programmers, who have to make their apps compatible. Since google does not want to police what apps are and are not supporting the feature, they just blanket deny the ability.
http://forum.xda-developers.com/showthread.php?t=1937270
or this for all apps http://forum.xda-developers.com/showthread.php?t=1961813
jordanmw said:
Wow... almost don't want to add anything to this flaming thread, but am also a user who is looking for some way to do this stuff on the tf700. Here is a thread that explains most of what the "framework" is and what it does. It is worth mentioning that things in android are already built for multiwindow interfaces but the options for the support are not turned on and some of the functionality is broken. The biggest hangup for this working is the app programmers, who have to make their apps compatible. Since google does not want to police what apps are and are not supporting the feature, they just blanket deny the ability.
http://forum.xda-developers.com/showthread.php?t=1937270
or this for all apps http://forum.xda-developers.com/showthread.php?t=1961813
Click to expand...
Click to collapse
actually I am not sure if it has to do with the app programmers because on my note 2, with jedi x9 rom all apps do work on multiwindow. So all apps by default just resize. for me it is a matter of time before it becomes standard in some sort on the base google code since it is already there not just implemented on anything other than touchwiz. we can already see a bit with paranandroid stuff and the resizing between tablet and phone screen sizes. some apps (cant remember well) already do the floating. .. so guys patience or has someone said treat uncle sammy for the score and get one of those galactic phones. the thing I would want programmer to focus on is multiwindow and multi monitors outputs with my hdmi output on my tf700 or the airplay android equivalent around the corner.
I'm curious how come there are still no AOSP or CM derived ROM's for the Note II that used Cornerstone. It would provide the same features offered by Samsung's own multi-window implementation in touch-wizz.
I've seen several ROM using this on the ASUS tablets.
If anyone doesn't know what I'm talking about , Cornerstone is an open source framework and launcher that offers multi-window support for AOSP and CM based ROMs. http://www.onskreen.com/cornerstone/
Source code here : https://github.com/Onskreen/cornerstone
Corner stone had issues with Google iirc because some apps don't behave well with it an resulting in bad ratings on the play store.. So cornerstone was blamed I haven't seen much progress on it since then..
Sent from my GT-N7105 using xda premium
lgstoian said:
I'm curious how come there are still no AOSP or CM derived ROM's for the Note II that used Cornerstone. It would provide the same features offered by Samsung's own multi-window implementation in touch-wizz.
I've seen several ROM using this on the ASUS tablets.
If anyone doesn't know what I'm talking about , Cornerstone is an open source framework and launcher that offers multi-window support for AOSP and CM based ROMs. http://www.onskreen.com/cornerstone/
Source code here : https://github.com/Onskreen/cornerstone
Click to expand...
Click to collapse
Cornerstone would cause CM to break the Android CTS. Knowingly breaking the Android CTS is a no-no for CM maintainers. (As to PIE - my opinion is that should never have been merged for that reason.)
Samsung worked around this by whitelisting a small subset of apps with the permission of the app developers - as big as CM is, I don't think we'd be able to get app developers to cooperate in this manner, and the end result is the effort to try and integrate Cornerstone just isn't worth it if it can only be used with a small handful of apps.
I'm not talking about official CM as I am aware of the issue it had with the CTS. I was referring to our ROM devs that make custom unofficial builds of AOSP , CM , AOKP and so on.
@Entropy512, I was curious how PIE made its way to CM. Surely there mustve been some debates regarding it. Could you please, if its possible, share some insight as to what points went against it, and in the end what was it that clinched it in favor of adding the feature?
toxicthunder said:
@Entropy512, I was curious how PIE made its way to CM. Surely there mustve been some debates regarding it. Could you please, if its possible, share some insight as to what points went against it, and in the end what was it that clinched it in favor of adding the feature?
Click to expand...
Click to collapse
Much of that is private... I would prefer not to go into detail on it.
What I will say is it was highly controversial and a number of people (including myself) still think it should be reverted if it can't be made not to break the CTS. (There was discussions of possible ways to make it less breaky, such as removing edge/top triggers.)
DAGr8 said:
Corner stone had issues with Google iirc because some apps don't behave well with it an resulting in bad ratings on the play store.. So cornerstone was blamed I haven't seen much progress on it since then..
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Isn't this just like Samsung's Multi-Window? When I flashed the mod that added all apps to Multi-Window, I found that some apps just don't work that well with it- it doesn't stop me from using it, but I've changed the way that I use Multi-Window. If we could adopt that kind of mentality perhaps we could use Cornerstone... What kind of reported bad activity was happening with Cornerstone?
altimuh said:
Isn't this just like Samsung's Multi-Window? When I flashed the mod that added all apps to Multi-Window, I found that some apps just don't work that well with it- it doesn't stop me from using it, but I've changed the way that I use Multi-Window. If we could adopt that kind of mentality perhaps we could use Cornerstone... What kind of reported bad activity was happening with Cornerstone?
Click to expand...
Click to collapse
Samsung's multi-window only works with certain applications that have been tested to work well with it. Anything not whitelisted won't work with multiwindow.
And NO - CM will NOT implement a "whitelist everything" hack like some people here have.
So since any app that gets used with Cornerstone would have to be approved by its author for use with Cornerstone, it then becomes an issue of - too much effort for too little reward. (There were, as I understand it, also some issues with Cornerstone's maintainability in the long-term, but the primary reason was application compatibility issues.)
I use multi window with every app (except games of course) and it is a breeze to use. Apps resize themselves very nicely. For me it is pure bliss to be able to have plume running side by side with tapatalk and use pop up browser for links. My dish anywhere app also works great with it as well. How can there be app compatibility issues if there are android phones with many dif size screens out there, basically the same issue no? The htc chacha had a 2.6 inch screen yet was google play certified. Thats not even half our screen size.
Sent from my SPH-L900 using Tapatalk 2
What entropy said
In the end one Dev can build it.. Get 2 - 300 DL then users move on and the interest fades away I personally been there done that.. Not for corner stone in particular but the idea is dev are building what they wish to run in their device .. Maintaining it becomes lots of effort for minimal results/interest..
Android is moving so fast great things get left behind all the time..
Sent from my GT-N7105 using xda premium
This is reminiscent of the times when webpages slowly started adapting to multiple devices, and thus was born the concept of responsive designs.
Previously they were built as per a definite CSS structure (Fixed-960 Grid it was called) But with analytics pointing to more and more variety in viewports, designers were forced to re-think their strategy towards responsive structures.
There were many who had a penchant dislike for it though. Creativity - they argued - suffered a lot at the hands of flexibility. Not many would know, but the introduction of responsive designs was ALSO one of the major reasons for the demise of flash-based websites.
So again, it boils down to how things pan out in the near future. If something similar comes along the way with regards to multi window development, and the demand/advantages far outweigh the difficulties in adapting code - I see no reason why the project could be back on track.
Sent from my GT-N7000 using xda premium
xopher.hunter said:
I use multi window with every app (except games of course) and it is a breeze to use. Apps resize themselves very nicely. For me it is pure bliss to be able to have plume running side by side with tapatalk and use pop up browser for links. My dish anywhere app also works great with it as well. How can there be app compatibility issues if there are android phones with many dif size screens out there, basically the same issue no? The htc chacha had a 2.6 inch screen yet was google play certified. Thats not even half our screen size.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but the screen size NEVER CHANGED.
It's changes in aspect ratio and dimensions that can do really bad things - and in some cases, the Play Store (I believe) can actually serve up different APKs depending on the device.
With any normal device, the app knows, from the beginning, what environment it will be running in. With multiwindow - it can have its environment changed out from under it.
Entropy512 said:
Yeah, but the screen size NEVER CHANGED.
It's changes in aspect ratio and dimensions that can do really bad things - and in some cases, the Play Store (I believe) can actually serve up different APKs depending on the device.
With any normal device, the app knows, from the beginning, what environment it will be running in. With multiwindow - it can have its environment changed out from under it.
Click to expand...
Click to collapse
the play store cannot let you have different apk for same app but it can let a developer upload app com.app.xhdpi
and com.app.hdpi (technically separate apps) and let the developer make the first one visible only to large devices
and the later one visible to smaller ones. an xhdpi phone will never be able to install the hdpi app and vice versa
Have anyone used CoverScreen OS or Samsprung in Z Flip 3? Which one do you think is better and which one is safer?
Edit : I decided to close the poll so that this thread will not be biased to one side. Let's just share the features and differences between both products and let anyone decide their own choice.
WilliamN40 said:
Have anyone used CoverScreen OS or Samsprung in Z Flip 3? Which one do you think is better and which one is safer?
Click to expand...
Click to collapse
Interesting question
It's difficult to answer because they are both under development and not finished apps
I am trying both of them and both craches from time to time, but as mentioned, beta versions
Personally I prefer Samsprung, there are news every day (several times usually) and I think it's really great, and well done job
Cover OS is way out of proportions regarding price, too expensive for a none working app, and also if it's working
At any time I would go for Samsprung
Just my opinion
Both developers have done a great job! thanks to them!
I'd also go with Samsprung. Way better support, updates, more features ect. The developer is also very responsive.
Cover Os has just entered Beta status and has a price tag that is obnoxious. Yes, i understand lots or blood, tears and work has gone into it, but as it still is, half baked software, the price is out of this world. We have to pay for something that we are testing, no thanks.
i'm totally fine paying when things are up and running as should, and i encourage both developers to put a price for their work. But as of now, no.
Of course Samsprung...
Do a poll, it'll answer you...
A few weeks ago I would have said CoveScreen OS, but the SamSpring suddenly took lead and I now find it superior.
The navbar, the customizable app launcher, keyboard(!), no features behind paywall, compatibility with stock widgets, super quick and responsive developer. It's an easy choice for me.
It's all wrong, trying to compare 2 apps trying to do different things - they are both in beta and developing very fast.
We are very lucky to have 2 very talented developers making that [ex-factory useless screen] into something geniunely useful.
Try each one - for a couple of days, not for 5 minutes. Then you have to reach your own conclusion.
And don't consider pricing for the moment, only once it/they are out of beta.
Please don't make a poll, that could impact development of one of the apps.
paul c said:
It's all wrong, trying to compare 2 apps trying to do different things - they are both in beta and developing very fast.
We are very lucky to have 2 very talented developers making that [ex-factory useless screen] into something geniunely useful.
Try each one - for a couple of days, not for 5 minutes. Then you have to reach your own conclusion.
And don't consider pricing for the moment, only once it/they are out of beta.
Please don't make a poll, that could impact development of one of the apps.
Click to expand...
Click to collapse
I agree with you 100% it's not fair on anyone to choose one or the other, there was a time when the moderators would have taken down a post such as this.
In my opinion this is a valid question.
Should you pay blindly for something that might not function correctly (beta) and you cannot test fully to see if it fills your needs.
or test something that is fully free and you can test all features and if they fills your needs.
But of course, test both. one you can test fully, the other you can.
BWA80 said:
In my opinion this is a valid question.
Should you pay blindly for something that might not function correctly (beta) and you cannot test fully to see if it fills your needs.
or test something that is fully free and you can test all features and if they fills your needs.
But of course, test both. one you can test fully, the other you can.
Click to expand...
Click to collapse
IMO since both are in development it's too early to even make a comparison. Both apps are moving very fast, so stability and functionality are not comparable. They are both moving targets at the moment
Maybe after both of their general availability, since then they are notionally stable.
If you're commenting about the subscription policy of one of them, I have tested its free version and haven't felt constrained. And there is no way that those values would fly in the Google Play universe, so I really doubt they are definitive values (time will tell, just my thoughts).
But still, once they are released and updates are incremental, why not run a poll.
Both applications interest me. I have only tried Coverscreen OS as I use Samsung Health persistently. I'm following both threads at present. Kudos to both developers
Bosbouer said:
Both applications interest me. I have only tried Coverscreen OS as I use Samsung Health persistently. I'm following both threads at present. Kudos to both developers
Click to expand...
Click to collapse
You don't need to uninstall Health anymore
Yeah don't need to uninstall on Android 12
Snurrea said:
You don't need to uninstall Health anymore
Click to expand...
Click to collapse
Thank you for this! Much appreciated.
I'm brand new to this phone and kinda not impressed with it (so far)..I'm a serious gadget nerd, so the flip/fold tech played too big a part in my decision to get it..I'd watched a samsprung video before I'd bought it so did expect a lot more use of the front screen than I get at the minute...like I said I am new to it so hoping to like it more the more I get to do with it but a quick question about samsprung, can it be used on android 12 or no? I updated the phone soon as I got it, then started seeing that it can't be used with A12!? Is there a way/work around?
smallz2k said:
I'm brand new to this phone and kinda not impressed with it (so far)..I'm a serious gadget nerd, so the flip/fold tech played too big a part in my decision to get it..I'd watched a samsprung video before I'd bought it so did expect a lot more use of the front screen than I get at the minute...like I said I am new to it so hoping to like it more the more I get to do with it but a quick question about samsprung, can it be used on android 12 or no? I updated the phone soon as I got it, then started seeing that it can't be used with A12!? Is there a way/work around?
Click to expand...
Click to collapse
SamSprung TooUI - Cover Screen Home (FREE) [ZF3]
Welcome to the original "Z Flip 3 Launcher" A complete home experience on the cover screen. Compatible with all current "Flip" devices. TooUI adds cover screen support for apps, full notifications, widgets, quick toggles, voice launch, custom...
forum.xda-developers.com
Both are pretty cool and somehow useful. Personally I don't use them because I don't need them and everything I'd like to have is just some more widget on the stock cover screen. However we're pretty luck to have those two developers here.
CoverScreen OS ask for way too many permissions, some really strange, i was not to ever able to run it, so yes for Samsprung
For me, the UI/UX of CoverScreen OS is better.