I bought my wife a blackberry bold this past weekend and all I can say is WOW. That thing has WAAAY more features (and settings) than my G1. And don't worry, I unlocked the phone so my wife can use it with our T-mobile accounts. In setting up this device, I've come to realize that a LOT of these features should be implemented into other devices, namely, the G1.
Here's a short list
1. Power-based settings (i.e. brightness changes when plugged in and on battery). A very BASIC feature.
2. Hiding folders in the music player. Blackberry gives the options to NOT include certain folders when searching for music. When I listen to music, I don't want to hear 50 ringtones.
3. User Customizable Profiles. Silent, Vibrate, Work, Home...Why not?
4. Alarm based auto-power on. If i set an alarm, and my phone is powered, but not on, it should be able to power on and wake me up. This is a GREAT feature for people that rely on alarms.(like myself)
5. Bluetooth profiles. I'm not new to mobile devices, so I know this is something they're currently working on. But come on...all we have is the headset profile. What come of lame-o **** is that? a2dp and wireless file access would be great, as well as phonebook access and callid and sms info for car kits...
There's more that I'm forgetting, but that's the gist of it. I realize that we're all technically beta testers at this point, but they should have released a more polished product to the masses. It would have helped their word-of-mouth sales greatly. Look at all the vista negativity. I've been using it without any problems since it was RTM, but people hate it because 'they heard' it has tons of problems. The average joe isn't going to want the g1 because 'they heard' it can't do this, or it can't do that. I personally love the device, and it has great potential, but t-mo and google may have shot themselves in the foot on that front.
InGeNeTiCs said:
Here's a short list
Click to expand...
Click to collapse
I'm not trying to be an Android apologist here, but let's run through your list.
1. Nothing exists, but it would take no more than an hours work to code something in Java to handle this.
2. Create a folder named ringtones in the root of the sd card. Nothing in there will be parsed by the default Music Player app.
3. Locale is probably the most popular app to handle this. Get it on the Market.
4. If your phone is in standby (short press red button), Alarm Clock can wake Android up. A more advanced alarm app is Klaxon. Again, get on Market.
5. A2DP support is pending.
No hardware is released perfect. Some imperfections are worse than others, and it's really also a subjective matter. If that above list seems problematic, consider that a competing product has no copy and pasting or support for background apps (making IM apps useless). In that kind of light maybe the fact that your G1 doesn't brighten the screen when you plug it in doesn't seem so bad anymore.
Honestly though if the choice between Blackberry and G1 is a list of periphery features rather than BIS vs Gmail, then you're completely missing the point imo.
Might I also point out that Blackberry OS (and Symbian and WinMo and iPhone) are all very mature OSes. Blackberry being the most mature, and it clearly shows in it's stability and simplistic ease-of-use. The iPhone just has a ton of money backing it, so it's no surprise that it has some superior features, even though its only 18 months old.
Windows is windows... 'nuff said.
Symbian has the backing of Nokia, so obviously it's well developed too.
All of these OSes were CRAP when they first came out. Google has plenty of money backing this project (I hope...) so I plan on giving them another 6 months to work out some of these basic problems before I go back to my good ol' Canadian-made Blackberry.
By the way a new app called simply "Power Manager" has appeared on the Market. Here's the description:
This application is similar to the power mgt apps available on laptops. It allows you to quickly view and change the settings of your phone depending on power states (e.g. turn off the GPS when the battery level drops below 30%, lower the brightness of the screen when on battery power, etc). It also maintains battery stats.
Click to expand...
Click to collapse
I just downloaded the battery program and it does address some of my concerns. It just sucks that all of these features have to be added as apps. Not having root access on an opensource device seems really stupid. It's like going to a ferrari dealership giving away free cars. Free cars! BUT....we took the engines out of them. Enjoy! What the hell are you supposed to do with that?
We've got an awesome platform to work with, almost all the source to create anything we want, but no access. It's beyond lame.
And far as the blackberry thing goes, I'm in NO WAY a BB fanboy. I've never owned one, and I they're a pain in my ass because my clients buy them thinking 'they just work' with MS exchange, when they need the enterprise client which my company doesn't want to shell out the cash for. So they get pissed at me when I tell them it doesn't 'fully' integrate. My frustrations aside, I merely used BB as an example of a device that had features that should be available on the G1.
And I think the whole alarm thing got misread. I realize that the phone will 'wake up' when the alarm activates. But if my phone is completely powered off, it will not turn itself on to activate the alarm. While this is not a totally necessary feature, and will probably be rarely used, it's very important for someone who RELIES on their alarms for scheduling purposes. I usually shut my phone off at night (I have customers in several distant timezones), but I can't do that if I want to use the alarm. I could obviously buy an alarm clock, but I don't see why the g1 can't do what another phone can.
No offense but bad analogy... It is hard to find the correct analogy... I guess it would be buying a hand gun, that you couldn't turn the safety off LOL Remember root is taken away for protection of users who don't know what it is. And as of right now we only know root is taken away on RC30... maybe when 1.0 comes out it will be available. Maybe they are working on a GUI to allow you to enable root. We have a long ways to go so I wouldn't say root is gone forever.
Side note: for your users with BB devices. I run Scalix on linux. Funambol bridges the gap for my users. I think that they even have an exchqange connector. Funambol is also availbe in the market place on the g1.
I have no problem with the actual integration process, the company just doesn't want to pay for it. We have people using windows mobile devices with no problems. I give the device recommendations, but they always come back with blackberries thinking it's the same thing. It's just frustrating. I'm venting. Sorry.
I have now researched the various 'ROMs' (actually firmware), and have narrowed the field to four. I'd like input on these. Priorities are (in order):
1. Complete Stability. I've run TomTom on WM5 for 6 years, and outside of TomTom it's a real mess. WM is so buggy I can't use it confidently for anything other than nav.
2. Good Battery. I have a friend who just got an Evo, and he says battery lasts only ~3 hours. I'm sure that's because of the large display, but also I read that several ROMs and apps really sacrifice battery on the N1. One screen I want to have dedicated to some sort of CPU/Mem/Storage monitor, so I can easily check it.
3. Lots Of Cool Features. It seems that video at 720p might be problematic as I gather it's really 3Mp upsampled, and/or it disables the still camera/flash somehow? Kernel optimizations are nice, although "deodexing" is not defined -anywhere-. I'm unlikely to stray beyond the UI built into the ROM, as it could introduce instabilities.
a. CM6 - The Big Kahouna. This ROM will likely be supported for a long time and is likely to integrate the newest kool features over time.
b. MoDaCo - Its thing seems to be stability, although a feature-by-feature comparison with CM6 leaves me confused, much less comparative usability is impossible to determine. Kitchen allows preclusion of G**gle apps.
c. LeoFroYo - The guy seems to know what he's doing, so under consideration. Comes with G**gle apps tho.
d. Kang-o-rama - an innovator whose improvements have been co-opted by others.
e. RoDrIgUeZsTyLe - I like it, but it is clearly very ill given the thread comments. Rejected.
Really? Nobody knows anything about this?
it depends on which phone u have bro, u didnt even specify that
I have a simple question about Android in which I have not found the simple answer to... (Although I think I know, I just want some clarification). I recently switched over to Windows Phone 7 because of various reasons, I will not name them here as that is an entirely different subject, however one of the reasons i switched was because of overall responsiveness of the OS. Why does Android's touch response feel sooo clunky? Yeah transitions and app launches are nice and quick, but I mean like pinch-to-zoom, and scrolling... I have played with the latest and greatest both rooted (with and without custom rom) and non rooted (with or without OEM UI), Motorola Xoom, Atrix 4G whatever is being claimed latest and greatest. But no matter what they all have the same touch response lag no matter what. This, believe it or not, is a major deal breaker for me, and before the majority of you speak, I'll speak for you; "why is something so simple and small, barely even considered a nuisance, be such a nuisance?" for me, i love fluidity, so, it just is. At this question however i do retort; if its such a "simple" or "small" nuisance, why can't it "simply" be coded to feel as fluid as Windows Phone 7, or iOS?
Luisraul924 said:
I have a simple question about Android in which I have not found the simple answer to... (Although I think I know, I just want some clarification). I recently switched over to Windows Phone 7 because of various reasons, I will not name them here as that is an entirely different subject, however one of the reasons i switched was because of overall responsiveness of the OS. Why does Android's touch response feel sooo clunky? Yeah transitions and app launches are nice and quick, but I mean like pinch-to-zoom, and scrolling... I have played with the latest and greatest both rooted (with and without custom rom) and non rooted (with or without OEM UI), Motorola Xoom, Atrix 4G whatever is being claimed latest and greatest. But no matter what they all have the same touch response lag no matter what. This, believe it or not, is a major deal breaker for me, and before the majority of you speak, I'll speak for you; "why is something so simple and small, barely even considered a nuisance, be such a nuisance?" for me, i love fluidity, so, it just is. At this question however i do retort; if its such a "simple" or "small" nuisance, why can't it "simply" be coded to feel as fluid as Windows Phone 7, or iOS?
Click to expand...
Click to collapse
I will try to answer since I've been using android before. android now as I believe is still in development stage. especially because it started from open source, where many developers get involved to participate in android development. unlike windows or the IOS platform. development is only done by the company itself through microsoft and apple. Except for third-party application development
android is a system (for run smoothly) with very powerful hardware. so that the source code would require a very complicated of encoding. Its a very difficult job to sync between the needs of software with hardware which is available. and vice versa. in an application such as pinching and scrolling there is more than one command which contains a lot of code. and should be remembered that this is a system. which are all related to each other for the overall operations to run smoothly based on the minimum demand of the hardware required. if there is one character in which is wrong of encoding or difference may cause the application not running properly.
for high-end android device such as Xoom, atrik 4G I'm sure the hardware is not an issue. I'm sure it was more caused by the complexity of encoding in one of the applications listed that is running inside in the whole operating system, making it not running smoothly. because so many commands which must be running at the same time is what make pinching and scrolling activity to be "clunky" like you said. you can differentiate by turning off the internet connection or turn off unnecessary applications running in the background. But I'm sure very soon android operating system will have a system which is more stable and efficient in encoding such as those held by the windows or apple.
My answer may be added by other members of the more expert in these matters. as a newbie, i am just trying to help based on the knowledge I had acquired over the years. CMIIW
Yeah I figured it would be something like that, I owned a Droid (1st gen.) and I had multiple setups from completely stock to my favorite, Cyanogenmod (always on the latest stable build, although I've already flashed CM7 RC2 and its probably the fastest its ever been at 800 MHz) everything was perfect except; scrolling and pinch-to-zoom. The scrolling is almost there, it actually lags for a bit but if I leave my finger on the page, it locks on to that position and stays there, but once I lift it to continue scrolling down or up it'll lag a bit again. The pinch zooming is just horrible no matter what. Unfortunately, given the nature of open source, and coding software in general, there is no such thing as "finished" software, so since this is open source, and the software is basically written to run on "nearly" whatever device you choose to flash it on, i don't think that problem will ever be solved. However, if Android does eventually reach that richness of responsiveness, then i will more than gladly switch back.
issues of a system running smoothly is different from one device to another device.
due to the wide variety of different android devices that causes the emergence of issues on the system stability. it was time to google as the main developer sets the standards for the development of next android os. while there is no standardization of hardware is set by google. it will be very difficult for other developers to write code/adjust performance in the operating system command. all this time writing code is must be adapted to the device from vendor itself. This will bring up the differences result of writing the code on other devices from another vendors (competitors). so if we running bencmark test or head to head test on both devices from different vendor the result will not be the same.
and if there will be a standarization set by google i believed it will not againts a spirit of an open source
I think the hardware that the WinCE (well...the shoe still fits) and Android phones are made on is essentially the same, in terms of the CPU power, the actual CPUs, the memory and the various other systems (graphics, etc.). Maybe not identical but overlapping classes and performance.
I haven't played with the new WinPhones but have noticed that every Android phone, no matter how fast and how "bare" factory, sometimes goes out to lunch. Apparently that's just the way the OS is written, it sometimes goes off to do other things internally (loading code? checking hardware states?) and you can't do anything except wait for it to come back.
But then again, almost every OS does that at times, including the main Windows OSes. That's just how they are done these days. If you had a cell phone fifteen year ago, you could turn it on and dial NOW. With any of the new cell phones? Can you do a cold power up and have a functioning phone in less than 30 seconds? Uh, no. But they call that progress, because you rarely have to power them off these days.
Every OS has tradeoffs, if the WinPhone makes you happier, by all means do it.
Rred said:
I think the hardware that the WinCE (well...the shoe still fits) and Android phones are made on is essentially the same, in terms of the CPU power, the actual CPUs, the memory and the various other systems (graphics, etc.). Maybe not identical but overlapping classes and performance.
I haven't played with the new WinPhones but have noticed that every Android phone, no matter how fast and how "bare" factory, sometimes goes out to lunch. Apparently that's just the way the OS is written, it sometimes goes off to do other things internally (loading code? checking hardware states?) and you can't do anything except wait for it to come back.
But then again, almost every OS does that at times, including the main Windows OSes. That's just how they are done these days. If you had a cell phone fifteen year ago, you could turn it on and dial NOW. With any of the new cell phones? Can you do a cold power up and have a functioning phone in less than 30 seconds? Uh, no. But they call that progress, because you rarely have to power them off these days.
Every OS has tradeoffs, if the WinPhone makes you happier, by all means do it.
Click to expand...
Click to collapse
I agree with you, I do like both OS's for their own benefits, currently I do like WP7 better than Android and keeps me "happy". However if you notice; that's not my prime motive in starting this thread, I didn't come here to say one is better than the other. I just want to know why those two simple things (scrolling and pinch zooming) are not fluid on Android. You can't use the excuse that it's different hardware because Microsoft is playing that trick too. You can't use the "its busy doing other things" excuse either, while WP7 doesn't have multi-tasking, iOS does (somewhat) so it can go "do" something else but will still feel fluid. In a multi-OEM environment it is up to the OEM to optimize it for the device it runs on, which is why it baffles me that even Sense and MotoBlur and others make performance decline a bit and still has the lag. Shouldn't it be the opposite?
Nothing? So no one can tell me why Android's responsiveness (scrolling, pinch-zooming) sucks?
Luisraul924 said:
Nothing? So no one can tell me why Android's responsiveness (scrolling, pinch-zooming) sucks?
Click to expand...
Click to collapse
The answer is quite simple (and the above replies are miles off the mark). Hardware acceleration.
WP7 has it, Android doesn't.
FloatingFatMan said:
The answer is quite simple (and the above replies are miles off the mark). Hardware acceleration.
WP7 has it, Android doesn't.
Click to expand...
Click to collapse
So the hardware acceleration runs throughout the entire OS? I thought it was mainly just the XNA and Silverlight stuff that was accelerated (I do believe those are different than native OS code, as Microsoft isnt allowing developers to write apps with native code. Future compatibility issues I guess)
Of course it's the entire OS. Why do you think MS's minimum spec stipulations are so high? This is what Windows Mobile was so plagued with, and how MS fixed that problem.
Luis-
"So the hardware acceleration runs throughout the entire OS?"
It isn't so much that the hardware acceleration runs in the OS, but that the hardware itself has certain routines built into it, on the firmware level, so the OS can just call those routines instead of trying to calculate them.
To oversimplify a bit, for instance, a hardware accelerator for "zoom in" might be programmed into the video chip system to automatically tell it "take the 50 pixels around this spot and blow up up to 250 pixels, refresh screen" where the OS would be saying "OK, let's take this spot, draw a square with a 50 pixel radius around it, now let's take each of those pixels and transpose it over twice the radius and go fill..." sending a long slow string of commands, each computed by the CPU.
When the CPU can offload all of that into a simple "zoom" command to the video chip, the CPU is now free to do other things. Like, respond to your next input, or push the next menu onto the display.
When you have ironclad control over the hardware--it can be a great way to make systems faster. And more stable.
Rred said:
Luis-
"So the hardware acceleration runs throughout the entire OS?"
It isn't so much that the hardware acceleration runs in the OS, but that the hardware itself has certain routines built into it, on the firmware level, so the OS can just call those routines instead of trying to calculate them.
To oversimplify a bit, for instance, a hardware accelerator for "zoom in" might be programmed into the video chip system to automatically tell it "take the 50 pixels around this spot and blow up up to 250 pixels, refresh screen" where the OS would be saying "OK, let's take this spot, draw a square with a 50 pixel radius around it, now let's take each of those pixels and transpose it over twice the radius and go fill..." sending a long slow string of commands, each computed by the CPU.
When the CPU can offload all of that into a simple "zoom" command to the video chip, the CPU is now free to do other things. Like, respond to your next input, or push the next menu onto the display.
When you have ironclad control over the hardware--it can be a great way to make systems faster. And more stable.
Click to expand...
Click to collapse
Great answer. Makes sense, thanks. Now given that this is an Android section lets talk more on that, will it ever be possible to have hardware acceleration on Android, Whether it be through custom ROMs or OEM devices?
"will it ever be possible to have hardware acceleration on Android,"
Possible? Sure, I've seen pigs on the wing.<G> Don't hold your breath for it though. Android is an unruly place where even ordinary hardware is often not supported by the OS and software breaks on every new phone. In order for hardware acceleration to work, the OS needs to have routines and drivers for standard hardware, which means locking down a hardware spec. Which is so very Undroid.
Can't see that happening, unless ten year from now someone invents a "standard universal Android cell phone chipset" and all the manufacturers get paid to exclusively use it. That's the ticket--use our chipset, we'll pay you to use it, and oh, yes, it will play one of "our" ads every time your screen turns on. Or you launch a new app. Or place a call.
(See? Things could get worse!<G>)
Here's an interesting discussion...
http://code.google.com/p/android/issues/detail?id=6914
burtcom said:
Here's an interesting discussion...
http://code.google.com/p/android/issues/detail?id=6914
Click to expand...
Click to collapse
Well as far as I read, it was just a bunch of "me too" and "I agree" lol I got bored reading that I still dont think Google has an official statement on the matter do they?
gee i wonder a special someone will come and close my thread again. i read through the forum rules and just couldnt quite match up the reason he gave
right anyway i've completed my review.
im going to post a few points here... those who want more details feel free to ask or visit my blog..it's in my sig
pluses are Pros and minuses are Cons
+++++ battery life is absolutely solid. 1700mah is no longer considered big these days- just look at the GS3’s 2100mah and the Razr Maxx’s 3000mah. And yet on Low CPU (800mhz) setting, the phone lasted 30 hours. on High (1400mhz) the phone lasted 24 hours. This is with autosync off, native email client synching every 15mins, 3 benchmark tests per charge cycle tested and other normal usage scenarios. in other words, other than gaming, there is no need for any frugality whatsoever.
++++ native browser is very fast, smooth and speedy. feels faster than Chrome, even.
++++ notification area is the most minimalistic and yet the most functional yet- the notification comes down only as much as is needed, and within it, there is quick access to all available wifi signals, 2G, 3G and auto network selection options and you can also toggle wifi on or off, data connection on off, GPS, autosync..
+++ FlymeOS is wonderfully user-friendly. Meizu has gone the extra length to ensure most the unnecessary complexities of Android are left out.
++ excellent viewing angles from the ASV (Advanced Super View) panel. colours are fine and contrast levels are as you would expect of any regular LCDs.
++ the 4 inch display resolution (640x960) may not win any awards for having the highest PPI as is the current unhealthy obsession these days, but it was impossible (without extra equipment) to discern the pixel differences. More so, coming from the One X, I no longer need to zoom and adjust for slightly larger text which is what I’m more comfortable with. This may be something to consider for people who don’t have perfect eyesight.
++ native voicemail (it actually bypasses your network’s if you set if to do so) and automatic call-recording are nice features and works seamlessly. To play them back, you either tap the new vmail notification or open up the Recorder app.
------ OS has stability problems- phone crashes and restarts once a day (when I was looking). At first I attempted to find the app that was causing it but really, there’s no reason why the OS can crash and burn because of one little app. There’s got to be something wrong deep down. Meizu needs to fix this.
----- unable to set defaults- that includes Launchers, browsers etc.
----- native browser does not support sharing to other apps- a very odd but an obviously deliberate decision.
--- audio / system stutters slightly when the phone’s been in use for around a day without a reboot. this happens especially when 3G data is in use. Makes for a rather unpleasant media performance, mostly.
-- FlymeOS is overly user-friendly and hid or moved a lot of the useful under the hood features. Fear not- an official vanilla ICS ROM has been promised.
-- glossy display exhibits excessive glare. it doubles as a mirror very well. (as you can probably see in the embedded hands-on video)
-- no app drawer- FlymeOS plays the iOS card a little too close to the chest by repeating the bane of MIUI (well, and itself?). what compounds the issue is that unlike MIUI, Meizu does NOT let you pick an alternate launcher as the default.
Not Happy with Meizu MX4
I hope someone cooks a new ROM so I can get rid of Flyme. I have the International vesrion (Non-Chinese)
Bad
Their Flyme email client is only in Chinese
Their catalog of software is only in Chinese
Their personalization Icon only displays in Chinese
It does not come with a Manual?
The Meizu website is in Chinese
Their predictive dictionary seems like 5 to 7 years ago (it doe snot display simple words and does not remember when I have already corrected something.
Good
Camera access on first screen and time between photos and taking pictures is great
Speed of phone phone because of the better processor is remarkably fast
PLEASE can someone come up with a way to either roll back to Android 4.4 on this device with Flyme of cook a new ROM?
Thanks
yellowchilli said:
gee i wonder a special someone will come and close my thread again. i read through the forum rules and just couldnt quite match up the reason he gave
right anyway i've completed my review.
im going to post a few points here... those who want more details feel free to ask or visit my blog..it's in my sig
pluses are Pros and minuses are Cons
+++++ battery life is absolutely solid. 1700mah is no longer considered big these days- just look at the GS3’s 2100mah and the Razr Maxx’s 3000mah. And yet on Low CPU (800mhz) setting, the phone lasted 30 hours. on High (1400mhz) the phone lasted 24 hours. This is with autosync off, native email client synching every 15mins, 3 benchmark tests per charge cycle tested and other normal usage scenarios. in other words, other than gaming, there is no need for any frugality whatsoever.
++++ native browser is very fast, smooth and speedy. feels faster than Chrome, even.
++++ notification area is the most minimalistic and yet the most functional yet- the notification comes down only as much as is needed, and within it, there is quick access to all available wifi signals, 2G, 3G and auto network selection options and you can also toggle wifi on or off, data connection on off, GPS, autosync..
+++ FlymeOS is wonderfully user-friendly. Meizu has gone the extra length to ensure most the unnecessary complexities of Android are left out.
++ excellent viewing angles from the ASV (Advanced Super View) panel. colours are fine and contrast levels are as you would expect of any regular LCDs.
++ the 4 inch display resolution (640x960) may not win any awards for having the highest PPI as is the current unhealthy obsession these days, but it was impossible (without extra equipment) to discern the pixel differences. More so, coming from the One X, I no longer need to zoom and adjust for slightly larger text which is what I’m more comfortable with. This may be something to consider for people who don’t have perfect eyesight.
++ native voicemail (it actually bypasses your network’s if you set if to do so) and automatic call-recording are nice features and works seamlessly. To play them back, you either tap the new vmail notification or open up the Recorder app.
------ OS has stability problems- phone crashes and restarts once a day (when I was looking). At first I attempted to find the app that was causing it but really, there’s no reason why the OS can crash and burn because of one little app. There’s got to be something wrong deep down. Meizu needs to fix this.
----- unable to set defaults- that includes Launchers, browsers etc.
----- native browser does not support sharing to other apps- a very odd but an obviously deliberate decision.
--- audio / system stutters slightly when the phone’s been in use for around a day without a reboot. this happens especially when 3G data is in use. Makes for a rather unpleasant media performance, mostly.
-- FlymeOS is overly user-friendly and hid or moved a lot of the useful under the hood features. Fear not- an official vanilla ICS ROM has been promised.
-- glossy display exhibits excessive glare. it doubles as a mirror very well. (as you can probably see in the embedded hands-on video)
-- no app drawer- FlymeOS plays the iOS card a little too close to the chest by repeating the bane of MIUI (well, and itself?). what compounds the issue is that unlike MIUI, Meizu does NOT let you pick an alternate launcher as the default.
Click to expand...
Click to collapse
Meizu had a aosp rom or something back then, I've not kept up with the news so I don't know what happened to that..
battery drain is still a problem to this day, sadly.
Ultimate solution for browsing the "desktop" internet on mobile (dev help request)
Background:
Moto G 2013 running optimized rooted Lollipop 5.1.
Related tweaks:
ro.sf.lcd_density=240 set in build.prop (apparent screen size: 6"). UI Tuner installed.
On Chrome Dev 56.0.2900.3
data/local/chrome-command-line contents:
chrome --user-agent="Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2900.3 Safari/537.36"
Well my dears, lets see if I can wake up a bit of freakin' interest here :fingers-crossed:. As you may know and probably suffer, certain websites serve their content selectively by requesting the client's browser certain specific information, namely screen resolution and pixel density (dpi). In this way, sites can determine the actual screen size of the client and ta-da!: you receive a freaking zoomed-in, crippled pile of sh1tepage. Sorry if this sounds gross, grossman. :silly:
The classic solution I already am using, as you already know. Main problem is that, as a mobile user, I have to deal with how the System UI gets impacted by my dpi/resolution changes. What this chiefly means is that, as a user of a device deprived of physical navigation buttons/bar, if I reduce too much my dpi, at a certain point the system UI gladly decides that it is 0K to misuse one of the most precious resources in this age of stupid, fashionable 16:9 screens (sorry) by relocating the navigation bar "down there", taking up screen width and also completely pissing off (even more) the useable screen aspect ratio. Reducing the dpi actually makes using the device much better in general, as some of you may already know. However...
In order to ride the real thing on the browser, seems to me we need to address this problem, an this is where my developer help request comes in. Chrome, and other browsers, serve our device's dpi setting at the will of requesting sites, is this right? Thus, I've thought some sort of small application/service could be made in order for it to fake our dpi setting to the whatever thing which requests it, and maybe also fake our actual resolution (sorry, already tried the per app settings in UI Tuner: doesn't works without screwing up the whole shebang -system UI- :silly.
Does all of this sounds right? Of course, with regards to how certain system stuff works I am making certain presumptions which may be wrong, yet I'm sure something nice can be done.
I'd gladly like to hear from you, comrades. Android FTW! :victory:
Cheers