vivaldi is not compatible with tablet
-
I have the Samsung Galaxy Tab S (1st generation) and can confirm that problem.
Could it be that this is an issue specific to the Galaxy Tab S series, since pretty everyone here who confirms it has one of those? -
@moribund said in vivaldi is not compatible with tablet:
I have the Samsung Galaxy Tab S (1st generation) and can confirm that problem.
Could it be that this is an issue specific to the Galaxy Tab S series, since pretty everyone here who confirms it has one of those?hi
its not your fault.
the tab bar(the bar above address bar)cause this problem.
i hope the totally remove this bar.then the problem would go away .and also we have more space in our tablet screen. -
I have to say I just don't get it. I've used Vivaldi since its inception. But this Android tablet issue makes no sense. How is it that Vivaldi can't figure out how to make their browser compatible with tablets. EVERYONE else seems to have figured it out. Its beyond annoying. Its shaking my faith in the Vivaldi project. I used to believe you folks were on top of the game. Now, I'm starting to think you either don't care or you're incompetent.
What the heck are you working on that is more important than having a browser that works on Android tablets? Seriously!
I'm not convinced anyone is even listening. And don't feed me that "we're a small group". Too small to make browser that actually works? That's what you do, make browsers. I thought.
Yes, I'm a bit over the top but I feel betrayed.
-
@Tyrone said in vivaldi is not compatible with tablet:
What the heck are you working on that is more important than having a browser that works on Android tablets? Seriously!
You must be new around here, Vivaldi 1st aim is on PC since few years, Android version is new and not even out of Beta stage. Everything needs time and the small team can't do miracles. And nobody is stealing your money.
-
@Tyrone said in vivaldi is not compatible with tablet:
How is it that Vivaldi can't figure out how to make their browser compatible with tablets.
Assumes facts not in evidence.
NeuOpera, for instance, initially, with its 200 or so developers, had to write three different browsers - one for desktop, one for phone, and one for tablets. After many months, they were able to merge phone and tablets, by causing the installer to detect the environment and install/activate one kind of code for phones, and another for tablets. Writing for tablets is writing for an additional, and separate, kind of environment.
Vivaldi developers may skip the phase of writing a "tablet" version, but they will not be able to skip the phase of writing code that installs/displays differently in different environments - and that is not a trivial undertaking.
-
@Ayespy said in vivaldi is not compatible with tablet:
@Tyrone said in vivaldi is not compatible with tablet:
How is it that Vivaldi can't figure out how to make their browser compatible with tablets.
Assumes facts not in evidence.
NeuOpera, for instance, initially, with its 200 or so developers, had to write three different browsers - one for desktop, one for phone, and one for tablets. After many months, they were able to merge phone and tablets, by causing the installer to detect the environment and install/activate one kind of code for phones, and another for tablets. Writing for tablets is writing for an additional, and separate, kind of environment.
Vivaldi developers may skip the phase of writing a "tablet" version, but they will not be able to skip the phase of writing code that installs/displays differently in different environments - and that is not a trivial undertaking.
Tablet and phone is both just Android with different screen resolutions. A modern dev environment lets you just cycle through many abailable resolutions. No need to create a new code other than fitting layouts to certain resolutions.
-
@DanielHHH For Opera, at least, the UI was actually different between phones and tablets. Tablet UI more like desktop. I don't know how it is now, as I no longer use any kind of Opera for Android.
-
Just some comments about the replies. First I know where Vivaldi started. I was using Opera for years and years. And have used Vivaldi Desktop from the inception. Second, if Vivaldi Android FOR TABLETS is a whole different kettle of fish, why not just say that. Vivaldi for Android PHONES. About not having tons of resources to throw at it. Vivaldi brought out the beta to use. If it hasn't worked right for months, isn't it fair to say it hasn't worked for months. If you are aware that it doesn't work with some types of devices, why not be up front about that and suggest that a beta for Android Tablets can be expected mid-summer 2020. Instead, we just hope Vivaldi takes this seriously and wait to see if the next release addresses this. A very frustrating approach. Maybe its just about transparency. I love Vivaldi (use it regularly on desktop and phone) but please have a little respect for tablet users. Waiting for Vivaldi for Android Tablets!
-
@Tyrone No one is disrespecting tablet users. I frankly don't know how the multiple Android form factors will ultimately be addressed, but I do know that one size does not fit all. If I had to guess, I would say the Android team is maybe two or three people, burning the midnight oil. Recent coding was done to try to get the Vivaldi mobile app more compatible with Chrome OS, which is not a true desktop OS and needs a more "mobile" approach, but would not really work with the Vivaldi mobile app at all. So that's a step in the direction of getting on board with multiple form factors in a "single" app that bundles multiple approaches.
We just have to wait and see how rapidly they can progress - knowing that a browser like Vivaldi is not a single-purpose app. It's not just a dinner salad or ice cream. It's an entire soup-to-nuts affair, and takes time to get to the table, one course at a time.
One thing that might help stuff along is if more Sopranos try to use Vivaldi on a tablet and give feedback. I'm not aware of any of us having it on tablet, tho almost all of us have it on phone. I don't own a tablet that can install it, (mine are too archaic) but I soon will. Then I can bring up such things backstage.
-
It seems esotherical to further discuss workloads and decisions within the Vivaldi team. Question is: Do we have any updates on this topic? Is the team aware that this bug leads to people uninstalling the software?
Barely any website can be used while that bug exists.
-
@DanielHHH The Bug is at priority 2 (usually only crashes with data loss get this priority) and there is a developer assigned.
If he can free up time between bringing Vivaldi out of the Beta stadium, he will fix it, but until that we need to be patient.BTW:
The main photo in this blog entry
https://vivaldi.com/blog/unique-features-vivaldi-android/
is the whole team for Android. Don't expect miracles from them but small steps, one after the other. It may take a little bit longer but will get them there.bug logging monkey
How to write good bug reports -
@QuHno said in vivaldi is not compatible with tablet:
The main photo in this blog entry
https://vivaldi.com/blog/unique-features-vivaldi-android/
is the whole team for Android. Don't expect miracles from them but small steps, one after the other. It may take a little bit longer but will get them there.And I recognize that at least four of those people have other full-time assignments as well.
-
@QuHno said in vivaldi is not compatible with tablet:
@DanielHHH The Bug is at priority 2 (usually only crashes with data loss get this priority) and there is a developer assigned.
If he can free up time between bringing Vivaldi out of the Beta stadium, he will fix it, but until that we need to be patient.BTW:
The main photo in this blog entry
https://vivaldi.com/blog/unique-features-vivaldi-android/
is the whole team for Android. Don't expect miracles from them but small steps, one after the other. It may take a little bit longer but will get them there.Thank you for sharing this information. Is there a way to keep myself informed without bothering you on this forum? Like a link to the dev tracker or the development status of that specific bug that is publicly readable?
@Ayespy said in vivaldi is not compatible with tablet:
@QuHno said in vivaldi is not compatible with tablet:
The main photo in this blog entry
https://vivaldi.com/blog/unique-features-vivaldi-android/
is the whole team for Android. Don't expect miracles from them but small steps, one after the other. It may take a little bit longer but will get them there.And I recognize that at least four of those people have other full-time assignments as well.
You keep repeating that the Vivaldi team might not be capable of delivering a mobile browser that is in line with what the competition has to offer and within a timeline that is acceptable bacause of resource issues. As reasons you name technical difficulties like different platforms/resolutions. That, in the end, would be poor entrepreneurship and poor planning - if this would hold true. Watching the history of Jon for quite some years now and being an entrepreneur in the software business myself, I don't want to believe that Vivaldi mobile has been planned that poorly.
If Vivaldi mobile has been made for mobile phones, not tablets, it should say so in the app description or even the name of the app.Please reconsider the rethoric you use - customers tend to react quite sensitive to that kind of information and might give up on the team instead of developing sympathy and serenity.
Consumers tend not to romanticize a situation but would like to see the issues resolved.What I got from this discussion is that the team seems to be aware of that issue, it's gotten a (relatively) high priority and its being worked on. THAT is the important bit here.
PS: As we are in the middle of the christmas season and people are on leave, realistically and in my humble personal opinion we can expect a fix to this issue between end of January and end of February if a dev starts looking at it in the new year, fixes it and puts it through quality assurance. (If they have access to an affected device that is.)
-
@DanielHHH Nothing would make me happier than to see rapid progress on mobile. It happens Julien, Jarle, Maria and Atle are full-time desktop developers and Julien is also in charge of sync (and therefore invaluable to mobile). I bring this up because looking at a seven-person team, you might think, "They have seven people on this! What could possibly be the hold up?" It's simply that "seven" people is not always seven. Unrealistic expectations are much more harmful, in my view, than realistic patience.
"... there is a developer assigned. If he can free up time between bringing Vivaldi out of the Beta stadium..." What this means is that it could be right away (high priority) (yay!) or it could be a looooooong time. (boooo!!) Either way, users have to be ready to live the WIR (when it's ready) dream.
I think it's great that users hold Vivaldi's feet to the fire. It is a great motivator, and it's part of the overall Vivaldi dynamic. I think this may be the most user-sensitive and responsive team I have ever seen. I think it's terrible when users castigate and vilify the team for failing to execute "quick and simple" tasks that are not at all quick or simple. And we get a lot of that, unfortunately. So I manage expectations.
I love that @QuHno gave/gives you hope. I seek to help you also keep your feet on the ground. You may thank me later. Or not.
Either way, I'll keep trying to manage expectations. I already have egg on my face for writing encouraging things about the pace of M3. Meanwhile, over a year later... You see what I mean, I think.(edit:) BTW, I have it installed on a 10" Android 9 Samsung tablet now, so I will be able to offer the team more direct feedback. Yay.
-
On the one hand, it is such a basic error that I think I could probably find and fix it - and I don't know React.js or even js in general. (As a mathematician I can figure out 3/4 of any program in any language as long as it involves math - and this is just a math error, really.) But I'm sure it's a huge codebase and finding the appropriate sections would take a little work.
-
So now that I have it on tablet, one thing I can see right off is that it knows this is a different form factor. It has a tab bar on tablet, which it does not have on phone. Absent the vertical touch displacement, it is otherwise operating very smooth and fast. Further, it shows me desktop versions of a lot of pages, which phone must otherwise be forced to do.
-
I use it quite regularly, it is usable as long as you scroll the page to hide the address bar. But they need to fix it before they release a "stable" version.
-
@sgunhouse I should think they would.
-
A fix for the tap offset issue has now been released in the latest Android Snapshot.
-
@jane-n Hot diggity! (of course I use a mouse with my tablet and so never saw it. But still... Users are likely to be dancing in the streets.
)
