Google and other shady IPs in Lollipop/Kitkat Sources - Security Discussion

Here are about 30 instances of Google IP, Level 3 communication, AT&T, Department of Defense and other curious IPs in Lollipop and Kitkat sources. Those could be changed to your liking before compiling a rom:
development/scripts/reverse_tether.sh
development/samples/ToyVpn/server/linux/ToyVpnServer.cpp
development/apps/Development/src/com/android/development/Connectivity.java
bionic/libc/dns/net/getaddrinfo.c
bionic/libc/upstream-openbsd/lib/libc/net/inet_addr.c
frameworks/base/tests/BandwidthTests/src/com/android/tests/bandwidthenforcement/BandwidthEnforcementTestService.java
frameworks/base/services/core/java/com/android/server/connectivity/Tethering.java
frameworks/base/core/tests/coretests/src/android/net/RouteInfoTest.java
frameworks/base/core/java/android/net/ProxyDataTracker.java
hardware/ril/reference-ril/reference-ril.c
hardware/ril-caf/reference-ril/reference-ril.c
external/android-clat/clatd_test.cpp
external/koush/AndroidAsync/AndroidAsync/src/com/koushikdutta/async/dns/Dns.java
external/chromium_org/chrome/browser/ui/webui/options/chromeos/internet_options_handler.cc
external/chromium_org/chrome/browser/extensions/api/proxy/proxy_apitest.cc
external/chromium_org/chrome/browser/net/dns_probe_service.cc
external/chromium_org/v8/tools/testrunner/server/presence_handler.py
external/chromium_org/native_client_sdk/src/tests/nacl_io_test/host_resolver_test.cc
external/chromium_org/chromeos/dbus/debug_daemon_client.h
external/chromium_org/net/dns/dns_config_service.cc
external/chromium_org/net/dns/dns_config_service_win_unittest.cc
external/chromium_org/net/dns/dns_config_service_unittest.cc
external/chromium_org/net/dns/address_sorter_unittest.cc
external/chromium_org/net/dns/dns_config_service_posix_unittest.cc
external/chromium_org/net/base/net_util_unittest.cc
external/chromium_org/third_party/skia/gm/rebaseline_server/server.py
external/skia/gm/rebaseline_server/server.py
external/bash/lib/sh/inet_aton.c
external/valgrind/main/none/tests/amd64/redundantRexW.stdout.exp
external/openssh/openbsd-compat/inet_aton.c

Nice one mate, you've been hard at work (unlike some "great" self proclaimed chefs that spend their time moving air and criticizing others, but never bring anything to the community)!
Just out of curiosity, do you mind telling us which IPs you found?
I had found such stuff in JB (like google's DNS and google web addresses), but not as many, one more reason not to update to KK or LL

unclefab said:
Nice one mate, you've been hard at work (unlike some "great" self proclaimed chefs that spend their time moving air and criticizing others, but never bring anything to the community)!
Just out of curiosity, do you mind telling us which IPs you found?
I had found such stuff in JB (like google's DNS and google web addresses), but not as many, one more reason not to update to KK or LL
Click to expand...
Click to collapse
Here is what I remember:
1.1.1.1; 2.2.2.2; 4.4.4.4; 5.5.5.5; 6.6.6.6; 7.7.7.7; 8.8.8.8. Those are simple ones easily remembered. There were more with larger numbers. Next time I do a rom, I will write down everything...

Related

Enough tablet apps...?

how come there aren't alot of tablet apps? How difficult is it to upscale or modify the app to be tablet native? (not being sarcastic)
kanyewest said:
how come there aren't alot of tablet apps? How difficult is it to upscale or modify the app to be tablet native? (not being sarcastic)
Click to expand...
Click to collapse
Not all the devs have xooms yet,
Wait till IO and we will see a bunch of new and existing apps for honeycomb
If you download Spare Parts and disable compatibility mode it will full scale the apps that are fixed to phone dimensions
Most of the time, its not as simple as the developer getting a new SDK and rebuilding with it. New SDK's cause new bugs and new instabilities.
They have to remake all new art work for larger screens and high resolutions so that takes time.
And the Android Tablets aren't exactly "readily available" like Android phones are. Guys who are coding at home on weekends may not have the cash to pick one up right now. (That accounts for a lot of apps) Big companies also want to see how the market reacts to tablets before they invest in development of software for one when the entire market could flop (Doubtful, but not without its risk).
I'm an android developer in my day job and I promise you, if you want apps that really take advantage of honeycomb they have to be rebuilt from the ground up in the interface department at least. There are some exceptions but on the whole...
Be patient and the updates will come.
I'm even working on a couple of apps at home specially for the XOOM.
Sent from my HTC Desire using Tapatalk
Since this is the first tablet that dropped with Honeycomb, it might be a bit for everyone to catch up. The same thing happened when Windows computers went from XP to Win 7 OS. It took a bit for the software developers to remake newer versions.
Its strange that we dont even see support (right now) for big companies like facebook or twitter. or even some other google apps dont have that support yet.
jerses said:
Its strange that we dont even see support (right now) for big companies like facebook or twitter. or even some other google apps dont have that support yet.
Click to expand...
Click to collapse
I'm guessing Google hasn't given them the AOSP before the public? Or maybe there wasn't any incentive for them to develop an app for something they didn't think would have the market share.
I remember when I first got my HTC Dream a couple of years ago, that there wasn't even a Facebook app out yet for it (it was still on stock Donut ROM from Rogers).
Sejanus said:
I'm guessing Google hasn't given them the AOSP before the public? Or maybe there wasn't any incentive for them to develop an app for something they didn't think would have the market share.
I remember when I first got my HTC Dream a couple of years ago, that there wasn't even a Facebook app out yet for it (it was still on stock Donut ROM from Rogers).
Click to expand...
Click to collapse
10.1 inches of web browser not reason enough not to call this a "mobile"?
I sure wouldn't write an app for something already fully functional.
Sent from my HTC Desire using Tapatalk
alias_neo said:
10.1 inches of web browser not reason enough not to call this a "mobile"?
I sure wouldn't write an app for something already fully functional.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
True, a lot of these sites work just fine with the browser (Stock, Dolphin). One thing that is a little bit off topic is the ability to hide the status bar (or go fullscreen with the browser) so we can really get the 10.1 inches rather then the 8 or so that we get with everything on the screen.
Sejanus said:
If you download Spare Parts and disable compatibility mode it will full scale the apps that are fixed to phone dimensions
Click to expand...
Click to collapse
It worked! Thanks

[Q] How close is Paul Burton to Beta?

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 !!

[Q] Multi-Window feature ??

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.

Cornerstone

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

Question CoverScreen OS vs Samsprung

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.

Categories

Resources