Database Info

Crocodile keyboard

Found on The Register:
Very cunning idea: "each triangular key has significantly more dead space around it than you’d find on a standard Qwerty layout. Consequently, users are more likely to press the correct key each time they tap."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Essentially the keyboard takes up the same amount of space, but it's easier not to fat-finger more than one key at a time. I would love to see this for touchscreen-only Android phones. It's patented, sadly (and destined for the iPhone), which begs the question: how hard would this be to implement on the sly? Essentially you're just re-skinning the keyboard, after all.

If you were just reskinning the keyboard then the touchable area would be the same and you would still fat-finger touch the other keys. You would also have to make the touch area different.

cruzzade said:
If you were just reskinning the keyboard then the touchable area would be the same and you would still fat-finger touch the other keys. You would also have to make the touch area different.
Click to expand...
Click to collapse
Hell, it might even be worth keeping the visual layout the same and just changing the touchable area; I was thinking of "reskinning" as both, largely because I've seen three different keyboards for the magic so far in different ROMs, at least two of which have different touchable areas due to having different keys.

Personally I just wished that the keyboard looked and behaved the same as the iPhone... In the Google firmware, the buttons are too small and responds differently, mostly it doesn't even recognize me pressing the keys...don't know if it is because it lacks multitouch or something..

bluekieran said:
how hard would this be to implement on the sly? Essentially you're just re-skinning the keyboard, after all.
Click to expand...
Click to collapse
Easy peasy!
Skiing a KB is actually quite easy..... several ways to do it but essentially there is one image for each type of key press- its just a matter of editing them in an image editor program- there is a thread about editing KBs in the dream themes and wallpapers section.

Crocodile Keyboard
Hi there,
Its good to get some feedback on my keyboard, some reports give the idea that I only want to get it put onto the iphone, but in reality, I want to get it used as the default keyboard on every touch screen phone.
The website at www.crocodilekeyboards.com was set up because it is almost impossible to show big companies new ideas as they all seem to hide behind the unsolicited ideas rulebook.
You would think that they would actively encorage inventors with a half decent idea by setting up a simple contact point for evaluation purposes.
I had to go public with the idea just to get it in front of them.
The UK patent covers not just the shape of the keys but also the area around them, it also covers variations of the triangular shape.
There seems to be a real need for this keyboard, everyone seems to hate predictive text and touch screens are definately the way forward.

so are you gonna release it for android any time soon?

dustmonkey said:
Hi there,
Its good to get some feedback on my keyboard, some reports give the idea that I only want to get it put onto the iphone, but in reality, I want to get it used as the default keyboard on every touch screen phone.
[...]
There seems to be a real need for this keyboard, everyone seems to hate predictive text and touch screens are definately the way forward.
Click to expand...
Click to collapse
Good luck! I look forward to trying it out and seeing how it works in practice. It would be nice to be able to move my fat digits a little faster on the screen!

It doesn't matter what the picture of the keyboard looks like. If you don't actually make the space/key bigger, then it won't make any difference. Applephone keyboard is a little easier because the screen is A LITTLE BIGGER.... physically. It has a larger screen. Thats what makes it easier.

Crocodile Keyboard
The actual size of the button is less important than you think.
There is a neat optical effect with the croc board were you see the triangular space around the key which makes it look much bigger, this then gives you a visual clue where the button is as you place your finger over it.
Many people have less than perfect vision and anything that helps determine the button position should help.
As an experiment, put your standard qwerty keyboard on a photocopier and print out a copy. (The full keyboard on my website, www.crocodilekeyboards.com, has a croc version of Apple's aluminium blutooth keyboard)
Then, using a felt tip pen change half the keys on the first few rows to croc keys and compare to the standard keyboard. You will see that you could reduce this on your copier by at least 40% and still easily use the croc keys but start to struggle with the standard ones.

Crocodile Keyboard
I have a question.
Crocodile Keyboards have decided that thier first app will be for the Android powered touch screen phones but have noticed something a bit sneaky in the Android developers agreement.
If you go to:
http://www.android.com/us/developer-distribution-agreement.html
Now look at the last bit of 5.1, "Market and to use the Products to make improvements to the Android platform".
Does this mean that I am about to spend five weeks developing this app and Google can just decide to use it in Android for nothing?
Please somebody tell me I am wrong, I am still waiting for a response from google about this.

From reading it would say that it means they I.E. google can use it for administration and demo.
I'm no legal eagle but i would take it from that they can NOT just steal your idea....... and tbh i dont think it matters what it says i dont think a court would uphold that.

I have seen this keyboard before and the patent is rubbish under prior art.
http://www.ex-astris-scientia.org/gallery/artoftrek/klingon-console-st5.jpg
RIM are trying other similar patents with hardware keyboards and three letters on a triangle key. For me this is a vile abuse of the patent system. To change the shape of a key and claim its a new idea is a pile of nonsense. Maybe I will invent and patent the parallelogram keyboard which is very like a triangle.

Krocodile Keyboard
Well untill Google get back to me saying anything different, then this distribution agreement is a contract to which I would be agreeing with. The courts will not agree to disolve an unfair contract just because one of the parties involved couldnt be bothered reading what they were signing.
I have just been speaking to my solicitor and his view is that they would be entitled under the contract to take my app off the store and use it in Android.
Come on Google, what is this?

I'd be more than happy to test it, outside of the market

I doubt google will be getting back to you. Though maybe the Klingons will be visting their solicitors or just come to blast you.

I bought it today, much better, I think. I was looking for an interface to change colors...is that possible? thanks, Cyn

well not many really people use it because either swype or the modified htc ime are still much superior - IMO none of the paid app keyboards are worth using
Swype Micro Download
XDA Modified HTC IME
as you can see this is dead for a reason
swype is superior to anything because once you learn it, the only thing better is a physical keyboard for speed
run the tutorial from the swype settings and you will see why

[REQUEST] A better landscape typing experience

Okay folks. I am wondering what you guys think about this. I hate to compare to the iPhone....again but there something that I am missing a little bit but not enough to make me jump ship...OBVIOUSLY! Anyway take a look at what I did with Paint.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vs
now the point of this is to make the conversation more....fluid. when im in the stock mode, picture 2, i just feel so disconnected from the conversation. i use google talk, i dubbed it GGM (Google Gmail Talk) just so it sounds as cool as BBM, and when im typing in landscape I cant even see what the other person wrote unless i exit the keyboard. again, this just takes me out of the whole experience. now some might say that the screen is too cramped with this option, others, like myself, say its not that bad and its probably worth it. and perhaps to satisfy both parties, maybe we can implement a double tap feature which will go back to stock mode. honestly, i have no clue if this is even possible but your inputs would be nice.
check out this thread: this guy actually did it but its kinda rough.
http://forum.xda-developers.com/showthread.php?t=672435

I like where you are going with this idea maybe you should pm the dev of the HTC IME mod

I type in portrait 99.999% of the time for this reason. I hate getting an IM/text from someone and not being able to see it without exiting the app.
I like what you did by not taking away from the kb size any, but from the HUGE area they give the text space. The text doesn't need that much room IMO. I hope this can be addressed and something better can from it.

I have to say, I dont like it....had it on my last device and it feels to tight, to small, I prefer to rotate my the device and enjoy the big field to type.

The only time I could really see myself needing to use the stock setup would when writing long responses in a forum. for example, before XDA had an app I would respond to threads using the standard view from the browser in landscape. this nicely moved all the other unnecessary stuff and made quoting someone very clean and easy.
Ayman

I think landscape typing is horrendous on android..I'd love to see it fixed. I'm a landscape lover but usually I stick to portrait for the KB.

I like where you are going with this idea maybe you should pm the dev of the HTC IME mod
Click to expand...
Click to collapse
I wonder if this is really something within the actually keyboard. I thought it was a framework issue, granted tho, I don't know much about that subject. is there anyone out there willing to make this happen?

The easiest solution to this problem is to use Swype, which works better in portrait view, and still type fast.

The easiest solution to this problem is to use Swype, which works better in portrait view, and still type fast.
Click to expand...
Click to collapse
how the heck is that a solution? did you even read the post?

I can't believe google decided that the keyboard and input box should take up the whole screen... sure hope somebody finds a way to do this! or at least make the text box slightly transparent or something

PLEASE I'M BEGGING YOU TO MAKE THIS
i hate how the text box takes up the whole top of the screen i would like to see the last msg that was sent
i hate iphones 2 but they have some good ideas
please

I don't like the way the landscape keyboard takes up the whole screen and covers all the previous msgs/ content. I would love to see this solution implemented or a previous suggestion where the text input area was transparent.

maybe this will he seen by more devs if it was in the development section. is it in the right section?
I have emailed jonasl, hopefully he will email me back.

any development on this yet

ya I doubt this will get developed unless we start spreading the word more. if we can get a dev to see this than maybe we can get somewhere. start tweeting it and it might catch someone's eye.
Sent from my Nexus One using Tapatalk

+100
would love to see this happen!

ayman07 said:
ya I doubt this will get developed unless we start spreading the word more. if we can get a dev to see this than maybe we can get somewhere. start tweeting it and it might catch someone's eye.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Perhaps send Jonasi a PM. he is the keyboard master

ya i did email him but he didnt respond. ill try a PM next.
PM sent. lets hope for a reply.
alright folk, i just had a lil chat with Chris Soyars (the dev who worked with cyanogen on stuff like the cool App2SD feature and who created NexusMod Live) and he says this is wayyyy to complicated. My predictions were correct, this is not something that is found within the HTC_IME or any other keyboard, its something within the framework. He admitted to me that he wouldnt even know where to start! Guess I got a lil over zealous with my request. He is really busy so he cant work on this but he said its all about finding the dev who is willing to put the time in.
with that said, i still think it can be done!! lol we just need the right person.

Hi,
I think you should read android-developers.blogspot.c0m/2009/04/updating-applications-for-on-screen Much of the problem lies not in the keyboard, but in how the applications interact with the keyboard.
Google's algorithm makes sense, but many applications don't specify their input mode, so the keyboards do the best they can.
Different combinations of Keyboards/Applications will yield different results. If you don't like what you have, tell the developer, or change keyboard and/or application.
Cheers!
-I_Artist

I_Artist said:
Hi,
I think you should read android-developers.blogspot.c0m/2009/04/updating-applications-for-on-screen Much of the problem lies not in the keyboard, but in how the applications interact with the keyboard.
Google's algorithm makes sense, but many applications don't specify their input mode, so the keyboards do the best they can.
Different combinations of Keyboards/Applications will yield different results. If you don't like what you have, tell the developer, or change keyboard and/or application.
Cheers!
-I_Artist
Click to expand...
Click to collapse
This is a HUGE help! I think I understand this better. Its not necessarily a framework issue, its the keyboard itself and all the keyboards are roughly identical. So what happens, if i read this correctly, is the keyboard has a predefined algorithm that tells it there isnt enough space on screen to have both the keyboard and app showing. that is why it reverts to covering up the whole screen.
This is used when the IME is too large to reasonably share space with the underlying application. With the standard IMEs, you will only encounter this situation when the screen is in a landscape orientation, although other IMEs are free to use it whenever they desire. In this case the application window is left as-is, and the IME simply displays fullscreen on top of it, as shown here:
Click to expand...
Click to collapse
So if we look at the IME and readjust what it considers to be too cramped of a space to display the full keyboard and part of the app on the same screen then it should work! what u guys think?
did some more digging. this is from HTC_CIME but it should be roughly the same idea:
keyboardBackground="@7F020074"
keyboardPadding="0,2,0,4"
functionKeyBackground="@7F020032"
commonKeyBackground="@7F020031"
pageKeyBackground="@7F02008A"
Click to expand...
Click to collapse
could these be the settings responsible for letting the app appear in the background with the landscape keyboard over it? i dont know what they "@7F02..." mean, what do these values represent?

[APP][4.1+]Simple Mobile Tools

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey people,
I want to introduce you a suite of Android apps I've created under the Simple Mobile Tools brand. As of writing this it contains 13 apps: App-launcher, Calculator, Calendar, Camera, Clock, Contacts, Draw, File-manager, Flashlight, Gallery, Music-Player, Notes, Thank You.
They are all open source, contain no internet access, no unexplainable permissions, no ads. That makes them perfect not only for the casual users, but also for the privacy concerned ones. They are available on f-droid too, sources are on Github. They contain customizable colors (including the app launcher color), dark theme is used by default.
I created them 2 years ago and by now they have roughly 6 million downloads together, so they are fine-tuned for the most part already, it isn't something fresh and rough that just came out of a school project. I'm actually working on them even more than full-time by now, so they can't just disappear or become abandoned. They are translated in up to 32 languages, translations are done by volunteers. The most popular app is the Gallery, the next ones are Calendar and Contacts.
Google keeps pushing developers to be more transparent with handling user data and they will also make their requirements more strict this year. App updates will have to target SDK 26 (Android Oreo) starting November 1 and while my apps are already doing that, it will cause a lot of troubles to other big players. Among many other things they will have to implement runtime permissions and not take every listed permission granted by installing the apps. That is one of the reasons why I think my apps have a tremendous potential.
Even though I have published app privacy policies as needed at Google Play, many people ask me what data do I collect. Well, since the apps are offline, I'm not collecting any data whatsoever. And since there are no ads, there are no marketing companies tracking you either.
The great benefit of using the apps isn't just the security, but also the consistent user experience, that I miss so much in Android. In my apps I'm reusing as much as I can. Not just actual functions, but also icons, actions, sometimes whole screens. Whenever possible, I'm using the Material icons provided by Google, so they should look familiar and you shouldn't be wondering what will happen once you press them.
Instead of typing out everything here, let me redirect you to my Medium article Why did I create Simple Mobile Tools.
I wrote an article about the first 2 years of my journey at Medium too, it is called 5 million downloads on 2nd anniversary. What now?
In case you want to read some user feedback, a Reddit article has been written too by a user (I'm not involved in that at all).
There are many new features/bugs/improvements/apps on the roadmap and while I already have around 20k installs a day, the best is yet to come!
Stay tuned,
Thanks!

( First ? )
Good to see you on XDA, indeed.
Thank you for keeping your software clean, with no analytics, no tracking, no data mining, and also for the enormous amount of work over the years. ( Been following on GitHub for a while. )
(っ´▽`)っ
　

tibbi2 said:
[IMG="Simple Mobile Tools cover image"]!​
Click to expand...
Click to collapse
Hi, I was looking for a substitute for quickpic (best gallery ever unfortunately buy and let die by cheetah mobile). Simple gallery lately have improved a lot but have some big lackness to be good as quickpic.*
Here the problems that quickpic doesn't have:
1- can't rotate image using simply two finger. //*
2- when you move an image from internal storage to SD (and viceversa) it change the date of editing, if you use that to order it will be the first. Make it optional //*
3- when you edit and image it change the edit data and the image became the first if you use it to order. Make it optional*
4- slow loading time. //
I really, really hope this will can be my the sostituite to all people still use quickpic even if it's not updated in years
I also suggest to add the possibility of draw in the photo editing.*
Good luck with this beautiful app.*​

Ye improving those is on the roadmap, stay tuned

tibbi2 said:
Ye improving those is on the roadmap, stay tuned
Click to expand...
Click to collapse
I found this thread after sending you the mail. [emoji28]
Is good to see that the answers are so fast
Tapatalked with A8 2018

Working on Simple Webbrowser?

not really, a browser wont be added anytime soon

Great work on the apps.
One small thing I've noticed, in the Gallery app, list view.. There is a minor misalignment in the thumbnails. Hopefully that's an easy fix?
Otherwise really nice, keep up the great work.

of course, there are Donation links mentioned everywhere. It is at https://simplemobiletools.github.io/donate/
Thanks

Beautiful Icons
Really love those icons. Pretty

the stranger94 said:
Hi, I was looking for a substitute for quickpic (best gallery ever unfortunately buy and let die by cheetah mobile). Simple gallery lately have improved a lot but have some big lackness to be good as quickpic.*
Here the problems that quickpic doesn't have:
1- can't rotate image using simply two finger. //*
2- when you move an image from internal storage to SD (and viceversa) it change the date of editing, if you use that to order it will be the first. Make it optional //*
3- when you edit and image it change the edit data and the image became the first if you use it to order. Make it optional*
4- slow loading time. //
I really, really hope this will can be my the sostituite to all people still use quickpic even if it's not updated in years
I also suggest to add the possibility of draw in the photo editing.*
Good luck with this beautiful app.*
Click to expand...
Click to collapse
Any progress with these?
Tapatalked with A8 2018

Hey, some of those things have already been fixed, but you will have to get the Pro version at https://play.google.com/store/apps/details?id=com.simplemobiletools.gallery.pro . Im working on rotating with gestures already, it just isnt that simple. Im getting there step by step, some initial implementation might be added in 6.5.0 released soon.

Will you be updating Simple Camera or it will turn into a pro app?
Sent from my Sony Xperia XA2 using XDA Labs

I dont really want to work on that app. There are so many things handled differently per manufacturer and per OS version that I just cannot make it work reliably. Now that there are devices coming with multiple cameras, Im actually always further from making it a compelling app.

tibbi2 said:
I dont really want to work on that app. There are so many things handled differently per manufacturer and per OS version that I just cannot make it work reliably. Now that there are devices coming with multiple cameras, Im actually always further from making it a compelling app.
Click to expand...
Click to collapse
Okay I understand.
It just a shame that there are not any other Camera apps which are simple like Simple Camera that I know of.
Sent from my Sony Xperia XA2 using XDA Labs

Great work man, love the philosophy and hard work behind your apps, been a long time user of simple gallery as I used to use quickpic (before cheeta mobile ruined it), and google photos sucks for quick offline use. Got simple gallery pro a little while back and I just got your thank you app too. Anyways, great work, glad to see you on xda, cheers!

thanks, enjoy

First I want to thank you for the apps. I've used most on and off over the past couple years. I currently use calendar and gallery only though.
My suggestion to you, from an end user, is to focus more on the style and layout of your apps. The clock, for example, doesn't resize to be large enough and forces info the user may not wasn't, e.g. PM...and contacts shoves things together, name and phone number, leaving lots of empty space yet cramped together info, calendar widget text size doesn't fit with event list though they're defined by the same setting. In other words, your use of negative space to create a more appealing look & feel to the app could use some work....please don't take this as a negative. Your work is much appreciated! Just constructive criticism.

ye sure, any feedback is appreciated. I will consider it, but for now I generally want to focus on the functionality. It looks not that bad Thanks

Could there be an option to show the actual size of an image in the Gallery application ? ( If there is, I haven't figured it out... )
It particularly affects small images, like pixel art or icons, that are blown up many times their size and distorted.
　

[APP][6.0+] Looxie: Location-based photo requests

Get Looxie from the Play Store!
Looxie is a location-based photo request app that I released back in 2016. The premise is simple: you go on the map, select a location you want a photo from and send your request to that location. Any users within one kilometer will receive the request and they can respond by sending you a photo.
The big twist? They can only send photos by actually taking them with their camera: gallery uploads are not allowed. Practically, this means that any photo you receive was taken seconds earlier and essentially is a real-time depiction of that location. The practical applications are numerous (Is the sea choppy? Is the bar I want to go to packed? Is there a lot of traffic on the A2? What's up in the Mongolian steppe right now?) but it's also really exciting to simply know that the photo you got depicts something at the other side of the world as it is right now.
Late last year, I decided that the app looked positively archaic, so I went ahead and rebuilt/redesigned it from the ground up to make it prettier and faster. I think the redesign is very successful and the app is indeed much faster and much easier to use.
Here is what it looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will probably be adding some premium features as a very cheap subscription (full-res photo downloads, for example) in the hopes that they'll at least cover the Firebase costs but anybody who registers an account by August 9th, 2019 will get all premium features for free.
I will be happy to answer your questions and read your comments!

Bumping the thread with actual links. I'll be around to answer any questions and respond to comments.

Really liking this app. Now I am getting requests one after the other from the same user. It would be nice if there was a cool-down time, I'd say, once every 2hrs between requests times from the same user

Amazing idea but..
1. When I use the search function, I can't actually click on a photo to be able to view it and zoom in. All it does when I click that it switches to the next photo and the same happens with Sent Looxies.
2. No full screen viewing available!
3. Settings is grayed out and I can't access it?
4. I can't view the likes of a certain image!
5. I am getting a ton of requests of user NewbieTown, is it a bot?

When i click the camera button to take a picture it opens the stock camera(xiaomi) but I don't really like the pictures from it so I use a google camera port , do you think it's possible to choose from the camera app?

Hey! You should be able to use any camera app you want. I'm almost never using the stock Pixel camera, instead I use something some effects, like Vignette or Cameringo.

lNOFXl said:
Really liking this app. Now I am getting requests one after the other from the same user. It would be nice if there was a cool-down time, I'd say, once every 2hrs between requests times from the same user
Click to expand...
Click to collapse
Hey, thanks! Totally my fault for not communicating this more clearly in the app but each of these requests are actually from a different user. Whenever a new user signs up, they have the option of sending a first contact request, ie. send a request to every user in the world (just once).
So what happened is that with the sudden influx of users (due to the XDA feature) LOTS of people got to use their first contact requests and everybody was flooded with those things. I should absolutely find a way to combat that but I don't want to take the first contact functionality away from new users. The problem will eventually solve itself, of course, when things go back to normal, with 3-5 registrations per day.

zombiezoom said:
Amazing idea but..
1. When I use the search function, I can't actually click on a photo to be able to view it and zoom in. All it does when I click that it switches to the next photo and the same happens with Sent Looxies.
2. No full screen viewing available!
3. Settings is grayed out and I can't access it?
4. I can't view the likes of a certain image!
5. I am getting a ton of requests of user NewbieTown, is it a bot?
Click to expand...
Click to collapse
Hello there.
You are right on every count, the app is pretty frustrating right now. This is partly down to the fact that it's a ground-up rewrite, so some functionality that was there in the old app is still missing but also due to the fact that I'm a lone developer working on it after 10-hour marathons in my day job, right after I manage to put my 2-year old son to sleep. I still love it, though. Let me answer your questions one by one.
1. All of the functionality you're describing is coming within the month. I'm taking a much-needed two-week off from work so I'll be able to focus on Looxie almost exclusively.
2. Also coming soon!
3. I know I sound like a broken record, but also coming soon. I have quite of bit of stuff to put in there, it won't take too long.
4. At this point you know the answer.
5. Nope, totally not a bot. It's new users signing up and using their first contact request (which they can use only once). Thingss should go back to normal, with about 5 first contact requests per day. Just give it a bit of time.
Thanks for your comment, I wanted to clear some of this stuff up anyway!

Antonis427 said:
Hello there.
You are right on every count, the app is pretty frustrating right now. This is partly down to the fact that it's a ground-up rewrite, so some functionality that was there in the old app is still missing but also due to the fact that I'm a lone developer working on it after 10-hour marathons in my day job, right after I manage to put my 2-year old son to sleep. I still love it, though. Let me answer your questions one by one.
1. All of the functionality you're describing is coming within the month. I'm taking a much-needed two-week off from work so I'll be able to focus on Looxie almost exclusively.
2. Also coming soon!
3. I know I sound like a broken record, but also coming soon. I have quite of bit of stuff to put in there, it won't take too long.
4. At this point you know the answer.
5. Nope, totally not a bot. It's new users signing up and using their first contact request (which they can use only once). Thingss should go back to normal, with about 5 first contact requests per day. Just give it a bit of time.
Thanks for your comment, I wanted to clear some of this stuff up anyway!
Click to expand...
Click to collapse
Thanks for the quick reply, I've edited the Google Play rating of the app to 5 stars.
However, you should've mentioned that the app has features that are still being optimized.

Possible to run on microg?
Love the app, just switched to a phone with lineageos 16 and microg. When I enter my username and password, it just hangs logging in. I then tried backing up the app on my old phone with adb backup then restored it to my new phone. The first time I started looxie, I was logged in and could see the feed. Now everytime I start the app, I get an empty feed that never updates. Also, my username is not displayed in the menu. Any ideas on how to get it working with microg?
Jeff

jebaker said:
Love the app, just switched to a phone with lineageos 16 and microg. When I enter my username and password, it just hangs logging in. I then tried backing up the app on my old phone with adb backup then restored it to my new phone. The first time I started looxie, I was logged in and could see the feed. Now everytime I start the app, I get an empty feed that never updates. Also, my username is not displayed in the menu. Any ideas on how to get it working with microg?
Jeff
Click to expand...
Click to collapse
Hey Jeff! I've never tested the app on a device with microg, unfortunately. Unless the microg package includes an implementation of FirebaseAuth, I cannot see it working. I'll need to check and see though, so stay tuned. If you're the Jeff from the app, it's nice to see you here, thanks for all the awesome photos :good:

Antonis427 said:
Hey Jeff! I've never tested the app on a device with microg, unfortunately. Unless the microg package includes an implementation of FirebaseAuth, I cannot see it working. I'll need to check and see though, so stay tuned. If you're the Jeff from the app, it's nice to see you here, thanks for all the awesome photos :good:
Click to expand...
Click to collapse
Thanks, It looks like microg doesn't support FirebaseAuth currently, there are a few issues in github for it. I'll try agian when they have it supported.
Jeff

Themes / Apps / Mods SamSprung TooUI - Cover Screen Home (FREE) [ZF4]

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 screen timeout, animated wallpapers, and more without recording how you choose to use it. Even our bug reports are filtered with your privacy in mind.
Compatible with Samsung Health and lock screens.
Fingerprint unlock must be used with a secure lock.
Notice: Due to an Android 13 bug, touch is not passed to the stock launcher when TooUI is minimized. Double tap the SamSprung icon to temporarily disable the launcher until the screen is turned off.
See the SamSprung site for setup and usage information​
SamSprung
A complete home experience on the cover screen
samsprung.github.io
Releases · SamSprung/SamSprung-TooUI
A complete home experience on the cover screen. Contribute to SamSprung/SamSprung-TooUI development by creating an account on GitHub.
github.com
SamSprung TooUI - Apps on Google Play
A complete home experience on the cover screen.
play.google.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​

It's still pretty rough, but all the README and Wiki and whatever other nonsense is being repackaged into a single website to make it easier to navigate. It should be up and running in the next day or two.
SamSprung
A complete home experience on the cover screen
samsprung.github.io
I will be going into surgery next week and may not be available for a bit during recovery, so I will try to get everything done ASAP. Thank you to everyone who has supported this project and made it possible to finally take the time off needed to breathe normally again.

SamSprung was released one year ago today as the first app launcher for the cover screen. With nearly 2000 new downloads per version and over 800 builds released, we have reached over 1 million downloads. Cheers!

Just an update - surgery did not kill me and new builds should be filtering through as Google finishes reviewing them.

I love you so much this is my first flip and I am blown away by this neat app. appreciate ya.

Awesome! Anyone can compare this with CoverOS?

BackToAndroid said:
Awesome! Anyone can compare this with CoverOS?
Click to expand...
Click to collapse
There is a thread for that. It's not really appropriate for the individual app threads (since I assume you want an unbiased opinion).

Are the launcher icons too small? I recently received a bug report saying they were entirely too small, but also feel like making them much larger will make the launcher seem clunky on a 1 inch screen. I run a DPI that makes anyone over 40 cringe, so I am a bit partial to smaller icons for person use. Are other people struggling with the app icons?

twistedumbrella said:
Are the launcher icons too small? I recently received a bug report saying they were entirely too small, but also feel like making them much larger will make the launcher seem clunky on a 1 inch screen. I run a DPI that makes anyone over 40 cringe, so I am a bit partial to smaller icons for person use. Are other people struggling with the app icons?
Click to expand...
Click to collapse
To be fair I think it varies on the icons, like personally me I'm a big boy so got big thumbs but I hardly ever misclick something; but that's also as you said, 1 inch screen there isn't much you can do about it. Possibly having an option for size adjustment would be cool but I see no problems with it.

Google Play reviews are a little backed up, but new builds were pushed to improve the overall stability (and reliability) of removing helper views. This should solve a few of the issues with ghost screens preventing input and other bugs.

Is this no longer being developed?

Wiggz said:
Is this no longer being developed?
Click to expand...
Click to collapse
The latest update was today. This thread is not a reflection of how active development is at any given time, though.
I don't really post announcements here because there isn't a whole lot to announce that anyone would come here to find.
Being open source, there is really no reason to explain what goes into each version. Downloads automatically show the changes since the previous version and building automatically happens when there are new changes. Google Play gets updated for every significant change.
Most bugs or requests get submitted through the app, so they aren't being posted here to reply. Any that aren't submitted to the GitHub directly come through email and are converted to GitHub issues.
This app doesn't have a paywall or features to unlock, so there is nothing to sell. It's kind of unnecessary to persuade anyone that a free app is worth trying because the price is already convincing.
Honestly, the lack of posts here is a positive sign that everything is running smoothly.

Yes, I am still here and still actively updating. TooUI now supports the Oppo Find N2 Flip.

twistedumbrella said:
Yes, I am still here and still actively updating. TooUI now supports the Oppo Find N2 Flip.
Click to expand...
Click to collapse
Absolutely love it good sir.

i am using a flip 4. for some reason i can't swipe. i tried enabling/disabling 'gestures' but swiping left/right/up/down doesn't work once samsprung is launched. what am i doing wrong ?

hoolahoous said:
i am using a flip 4. for some reason i can't swipe. i tried enabling/disabling 'gestures' but swiping left/right/up/down doesn't work once samsprung is launched. what am i doing wrong ?
Click to expand...
Click to collapse
Notice: Due to an Android 13 bug, touch is not passed to the stock launcher when TooUI is minimized. Double tap the SamSprung icon to temporarily disable the launcher until the screen is turned off.
Click to expand...
Click to collapse
Android 13 enabled another of Google's brilliant ideas to disable the ability of any window to pass touch to windows below it.
There are a few exceptions. A completely invisible window (so basically malware) is granted the ability to pass touch. A window more transparent than the arbitrary maximum opacity of an overlay (0.8 or 20% transparent) can also pass touch, but results in the window under it being visible through the current one. The last, and my personal favorite, is accessibility. By requesting ANY accessibility feature, such as retrieving notification text, you gain unrestricted access to control the entire device.
Google's only method to control accessibility is to require that at least one use case fits one of the ones they allow and that you notify the user before requesting access to accessibility that you are going to ask them for access to accessibility. Put simply, you need a nag screen.
On top of that stroke of brilliance, they are now planning to add extra permissions and disclaimers for services running in the foreground.
This means that any service that is required to notify you it is running and maintain a notification reminding you it is running will now have to make absolutely sure you know it will be running through a series of nag screens and disclosures.
Google is trying to emulate the security promises made by Apple, but trying to pass all of the work to individual developers. The end result being a platform no less insecure than it was, but with frustrated users and developers doing a lot of meaningless work.

For me the newest github release from yesterday works better than the one on google play. Nice work, my friend.