In light of the controversy over Nexus S I thought I would see what everyone else thought a phone branded Nexus should be. Before anyone gets to crazy, here are the guide lines:
1) who builds it
2) nothing that is not produced or not going to be produced: aka- "Star Wars in true 3D holograms and a transporter from Star Trek" talk about things that DO exsist like 10 megapixel cameras with flash, accepts 32g class 10 cards, front facing camera, roms, android version, etc.
3)Why
4)Try to explain why there is not this device
That's it, build your Nexus fantasy, and question why we can't have it!
My Dream Nexus
Okay, well I have been thinking about this for a while now, what I would like in a phone, not necessarily a Nexus, and this is what I have come up with. Please understand that I haven't used an Android phone (although I am getting a Galaxy S for Christmas, have found them cheap on eBay from people giving them up for Nexus S' ) so some of this may be irrelevant.
1) Well, to be honest, I don't care who makes it, as long as it is reliable and sturdy. I love the design of the HTC 1 (concept by Andrew Kim, Google it, I can't post links or pictures unfortunately), and it seems to fit HTC's recent designs, so I may as well go with HTC, having played with a Desire and Wildfire, I can't fault the quality.
2) In my mind, I can't see much technology that could be incorporated into a new device that isn't out currently. I think an 8MP camera (large sensor size of course) is about as much as most people will need. A choice of 32/64 GB internal storage seems reasonable, with the option of using a MicroSDHC card up to 32GB. As for processors, I would probably choose that tri-core processor I heard about a while ago (can't remember it's name for the life of me) that had 2 multimedia/powerful cores and one lower clocked core for other tasks, paired with 1GB of RAM, allowing for the future, because with all of this, hopefully it would be at the top for a long time. A screen size of about 4 inches seems perfect, having used an iPod Touch and tested out a Galaxy S and a HD2, preferably with SuperAMOLED(2?). A front facing camera (1.3mp), and all the current sensors would be included. As for connectivity, Wireless N is standard, but you could get this phone in several versions, a HSPA+ version, LTE or WiMAX, to cater for your network of choice, and at a stretch, combine them all into one to have a mega-worldwide phone . Now, the biggest improvement area: batteries. I would definitely have a large capacity battery, at least 1500ma, but possibly even using new technology to make it last longer, such as using Tobacco Mosaic Virus to boost battery life 10x (I read this on Gizmodo today). Thats about all I can think of for hardware, with all of that, you really need decent software, and that's where the fun really begins.
Software is a tricky area in my mind for the Nexus line, being more of a developer type of phone, it should be easy to root and customise everything, installing new ROMs should be painless, and safe, with no risk, similar in a way to an iOS jailbreak (just hit restore in iTunes etc). But, as Andrew Kim mentioned when he did his HTC 1 concept, hardware and software need to be unified. This is where a Nexus could excell, being a Google phone and running stock Android. But to do that, I think the UI needs to become more consistent, much more consistent. Go and look at the HTC 1 concept now on the Design Fabulous website/blog, and find the messaging app mockup. It uses similar shades of grey and black to the phone itself, making it appear seemless, and even beautiful. Yes this would mean giving Android a completely different look, like going from WM6.x to WP7. And remove those buttons, for crying out loud, you have a beautiful touchscreen just there, it should be used! Have 2 buttons, a Home and Menu, integrate the Back option into the UI like in iOS, search could be accessed by holding down/double tapping Home and then the Menu key could be used for the next major shift.
(EDIT: Can't post images, sorry, but please search Google Images for 'windows phone 7 app associated press' and it should be the first image there)
Yes, this is a picture of an app in WP7, but that's not the point. I tried out WP7 the other day, and I found it a refreshing way of using a device. It looked good and was consistent. But I am drifting off, the Menu key. Look at the picture above, look to the left, and see the categories. Imagine that as all the app's options/menu, like pressing the Menu key currently does, as well as anything else. You could swipe through the different screens to get to it (using the screen, like I went on about before), or, similar to getting back to the first page of apps on iOS, press the Menu key to zoom back there. Simple and elegant in my opinion. Implement a similar look and feel across the whole system, and you have some mighty fine software indeed, but for those who wouldn't like it, with the option of installing one of the many ROMs available without any risk.
3) Why? Well, we are a consumer society, with many phones getting replaced in a year or less, and sometimes just being thrown out, we waste so many materials. By providing solid, useful and top of the line hardware, the need to upgrade becomes less as it would take longer to become outdated. I believe software is the key to a platform, and I am not alone in thinking that. That is where the real innovation comes from, so with a standardised Nexus there could be so much innovation coming from users such as the people here at XDA. Most of the hardware is probably available today, if not in the near future, so it is more an evolutionary step, but I will say that the tri-core processor is for more battery life and more power when needed, and the RAM allowing for better multitasking and futureproofing. And I would just love to own a phone looking like the HTC 1 concept, it is awesome and many friends I have shown it to think the same (they aren't techies either).
4) Why can't we have it? Well, I don't actually know why. The only things I can think of which probably isn't in production are: a) the tri-core processor, but dual-cores are in production now or in the next few weeks I imagine, b) SuperAMOLED(2?), mainly because it's Samsung's tech and this would be built by HTC and c) the multiple connectivity radio with HSPA+, LTE and WiMAX probably isn't being developed as of now, maybe not for another year until these networks become more common.
It is the software side of things which puzzles me, but I'm sure it is coming. Someone just has to take this idea with them, and go for gold. I would like to do that personally, but I need to learn how to code better, a lot better. (I joined XDA for inspiration ) I think this UI would work well, and be powerful, elegant and simple at the same time, helping to bring Android into the public as being easy to use and better than Apple's offerings (a tough task, but I would like to think it possible, note I am not an Android fanboy, neither do I hate Apple, but change is good).
Wow, that is a lot of writing... I hope this is acceptable, I would love to have a device like this myself, I think it would be possible in the next 6 months maybe? I am curious to see what others would like, bring on more ideas!
mcsinny99 said:
In light of the controversy over Nexus S I thought I would see what everyone else thought a phone branded Nexus should be. Before anyone gets to crazy, here are the guide lines:
1) who builds it
2) nothing that is not produced or not going to be produced: aka- "Star Wars in true 3D holograms and a transporter from Star Trek" talk about things that DO exsist like 10 megapixel cameras with flash, accepts 32g class 10 cards, front facing camera, roms, android version, etc.
3)Why
4)Try to explain why there is not this device
That's it, build your Nexus fantasy, and question why we can't have it!
Click to expand...
Click to collapse
I believe thats this is just a useless post. U ask people to xplain their fantasies but dont include phones not or never will be built?!
plainly put there is n never will be any ultimate phone since whatever u buy now is obsolete in 2 months.
@ OP
Post something more productive. There are other places u can go to post ur wishes n dreams.
kaivish said:
I believe thats this is just a useless post. U ask people to xplain their fantasies but dont include phones not or never will be built?!
plainly put there is n never will be any ultimate phone since whatever u buy now is obsolete in 2 months.
Click to expand...
Click to collapse
I'm sorry, but I think you may have misunderstood the point about no Star Trek stuff. Reasonable fantasies would probably be a better way of thinking of it, maybe something you could get within the next few years. Yes, phones will be obsolete within months of release, but as I mentioned in my post, I think software is the real contender in the future, so once you have a decent specced phone, the software can do the rest.
I'm personally interested in what people want from a phone which isn't out already. So if you think this isn't productive, you don't have to read it. I think some good stuff could come out of here, and you never know, Google or HTC could be listening
1) built by samsung
2)3.8" super AMOLED screen with a resolution of 1024x720 for a true HD display and 329 PPI(pixels per inch). a 1.2Ghz dual-core orion processor, Nvidia GPU,samsungs own NFC chip included in the nexus S, 2.3 Gingerbread ,10MP continual Auto-focus camera that can record at 720p, maximum microSD card is 32GB class 6, 16GB on-board storage,unlocked bootloader for easy loading of ROM's,1.3MP front facing camera, hardware camera shutter button, contour display, choice of stock 2.3 launcher or Touchwiz 3.0 launcher.
3) because why shouldnt we have tech this awesome , and if you think about it , most laptops would e obsolete if this were true , along with point and shoot cameras
4)Cost, cost of manufacture , cost of retail, too much R&D would be needed , to many other products would become obsolete, this to would need to be released quickly , or have 3.0 loaded onto it when it becomes readily available.
and can i have it by christmas please santa ??
CPU:
Snapdragon QSD8672 (1.5GHz Dualcore)
RAM:
1024MB DDR2 Mobile RAM (Elpida Produced)
GPU:
256MB nVidia Tegra GPU
Storage:
OS/Applications: 2048MB SSD
External Storage: 32GB MicroSD
Imaging
5MP Main Camera (Any does me tbh)
Sound
Bluetooth Cochlear Implant w/ Induction Charging Circuit
Screen/s
Wrist Display - Subdermal LCD w/ Single Action Touch Sensor and Induction Charging Circuit - http://www.gearfuse.com/subdermal-implant-watch-tattoo/
Main Screen - WSVGA Touch Screen
Power
5x 250A Lithium Ion Polymer Cells using Cell Balancing
Location Services
GPS
Accelerometer
Digital Compass
Altimeter
Connectivity
Micro USB 3.0
WiFi
HSDPA
3G
GPRS
the usual basically...
Would be my ultimate like
dom.l said:
2)3.8" super AMOLED screen with a resolution of 1024x720 for a true HD display and 329 PPI(pixels per inch). a 1.2Ghz dual-core orion processor, Nvidia GPU,samsungs own NFC chip included in the nexus S, 2.3 Gingerbread ,10MP continual Auto-focus camera that can record at 720p, maximum microSD card is 32GB class 6, 16GB on-board storage,unlocked bootloader for easy loading of ROM's,1.3MP front facing camera, hardware camera shutter button, contour display, choice of stock 2.3 launcher or Touchwiz 3.0 launcher.
Click to expand...
Click to collapse
Sounds decent I like your thinking!
dom.l said:
1) built by samsung
2)3.8" super AMOLED screen with a resolution of 1024x720 for a true HD display and 329 PPI(pixels per inch). a 1.2Ghz dual-core orion processor, Nvidia GPU,samsungs own NFC chip included in the nexus S, 2.3 Gingerbread ,10MP continual Auto-focus camera that can record at 720p, maximum microSD card is 32GB class 6, 16GB on-board storage,unlocked bootloader for easy loading of ROM's,1.3MP front facing camera, hardware camera shutter button, contour display, choice of stock 2.3 launcher or Touchwiz 3.0 launcher.
3) because why shouldnt we have tech this awesome , and if you think about it , most laptops would e obsolete if this were true , along with point and shoot cameras
4)Cost, cost of manufacture , cost of retail, too much R&D would be needed , to many other products would become obsolete, this to would need to be released quickly , or have 3.0 loaded onto it when it becomes readily available.
and can i have it by christmas please santa ??
Click to expand...
Click to collapse
Sent from my Liberty using XDA App
@3) That is my theory as well. But why not fire a shot across the bow of other manufacturers? Set the bar higher and watch them scramble to catch up?
2) In my mind, I can't see much technology that could be incorporated into a new device that isn't out currently. I think an 8MP camera (large sensor size of course) is about as much as most people will need. A choice of 32/64 GB internal storage seems reasonable, with the option of using a MicroSDHC card up to 32GB. As for processors, I would probably choose that tri-core processor I heard about a while ago (can't remember it's name for the life of me) that had 2 multimedia/powerful cores and one lower clocked core for other tasks, paired with 1GB of RAM, allowing for the future, because with all of this, hopefully it would be at the top for a long time. A screen size of about 4 inches seems perfect, having used an iPod Touch and tested out a Galaxy S and a HD2, preferably with SuperAMOLED(2?). A front facing camera (1.3mp), and all the current sensors would be included. As for connectivity, Wireless N is standard, but you could get this phone in several versions, a HSPA+ version, LTE or WiMAX, to cater for your network of choice, and at a stretch, combine them all into one to have a mega-worldwide phone . Now, the biggest improvement area: batteries. I would definitely have a large capacity battery, at least 1500ma, but possibly even using new technology to make it last longer, such as using Tobacco Mosaic Virus to boost battery life 10x (I read this on Gizmodo today). Thats about all I can think of for hardware, with all of that, you really need decent software, and that's where the fun really begins.
Software is a tricky area in my mind for the Nexus line, being more of a developer type of phone, it should be easy to root and customise everything, installing new ROMs should be painless, and safe, with no risk, similar in a way to an iOS jailbreak (just hit restore in iTunes etc). But, as Andrew Kim mentioned when he did his HTC 1 concept, hardware and software need to be unified. This is where a Nexus could excell, being a Google phone and running stock Android. But to do that, I think the UI needs to become more consistent, much more consistent. Go and look at the HTC 1 concept now on the Design Fabulous website/blog, and find the messaging app mockup. It uses similar shades of grey and black to the phone itself, making it appear seemless, and even beautiful. Yes this would mean giving Android a completely different look, like going from WM6.x to WP7. And remove those buttons, for crying out loud, you have a beautiful touchscreen just there, it should be used! Have 2 buttons, a Home and Menu, integrate the Back option into the UI like in iOS, search could be accessed by holding down/double tapping Home and then the Menu key could be used for the next major shift.
(EDIT: Can't post images, sorry, but please search Google Images for 'windows phone 7 app associated press' and it should be the first image there)
Yes, this is a picture of an app in WP7, but that's not the point. I tried out WP7 the other day, and I found it a refreshing way of using a device. It looked good and was consistent. But I am drifting off, the Menu key. Look at the picture above, look to the left, and see the categories. Imagine that as all the app's options/menu, like pressing the Menu key currently does, as well as anything else. You could swipe through the different screens to get to it (using the screen, like I went on about before), or, similar to getting back to the first page of apps on iOS, press the Menu key to zoom back there. Simple and elegant in my opinion. Implement a similar look and feel across the whole system, and you have some mighty fine software indeed, but for those who wouldn't like it, with the option of installing one of the many ROMs available without any risk.
3) Why? Well, we are a consumer society, with many phones getting replaced in a year or less, and sometimes just being thrown out, we waste so many materials. By providing solid, useful and top of the line hardware, the need to upgrade becomes less as it would take longer to become outdated. I believe software is the key to a platform, and I am not alone in thinking that. That is where the real innovation comes from, so with a standardised Nexus there could be so much innovation coming from users such as the people here at XDA. Most of the hardware is probably available today, if not in the near future, so it is more an evolutionary step, but I will say that the tri-core processor is for more battery life and more power when needed, and the RAM allowing for better multitasking and futureproofing. And I would just love to own a phone looking like the HTC 1 concept, it is awesome and many friends I have shown it to think the same (they aren't techies either).
4) Why can't we have it? Well, I don't actually know why. The only things I can think of which probably isn't in production are: a) the tri-core processor, but dual-cores are in production now or in the next few weeks I imagine, b) SuperAMOLED(2?), mainly because it's Samsung's tech and this would be built by HTC and c) the multiple connectivity radio with HSPA+, LTE and WiMAX probably isn't being developed as of now, maybe not for another year until these networks become more common.
It is the software side of things which puzzles me, but I'm sure it is coming. Someone just has to take this idea with them, and go for gold. I would like to do that personally, but I need to learn how to code better, a lot better. (I joined XDA for inspiration ) I think this UI would work well, and be powerful, elegant and simple at the same time, helping to bring Android into the public as being easy to use and better than Apple's offerings (a tough task, but I would like to think it possible, note I am not an Android fanboy, neither do I hate Apple, but change is good).
Wow, that is a lot of writing... I hope this is acceptable, I would love to have a device like this myself, I think it would be possible in the next 6 months maybe? I am curious to see what others would like, bring on more ideas![/QUOTE]
Great post, I agree with most of what you have to say, but I feel wp7 is behind in ui. Take that home screen that just plainly wastes 1/3 of the screen. Sure, android phones could loose those buttons, but I still think it's a step ahead of the competition. The slick ui concept http://phandroid.com/2010/10/25/slick-ui-promising-look-at-an-android-home-screen-replacement-app/ may be a step towards that htc 1 concept (WOW, btw, had not seen that- http://designfabulous.blogspot.com/2010/07/htc-1.html) that we will get soon. Seems people just don't like the idea of those permanent screen buttons. I am coming around myself.
mcsinny99 said:
Great post, I agree with most of what you have to say, but I feel wp7 is behind in ui. Take that home screen that just plainly wastes 1/3 of the screen. Sure, android phones could loose those buttons, but I still think it's a step ahead of the competition. The slick ui concept http://phandroid.com/2010/10/25/slick-ui-promising-look-at-an-android-home-screen-replacement-app/ may be a step towards that htc 1 concept (WOW, btw, had not seen that- http://designfabulous.blogspot.com/2010/07/htc-1.html) that we will get soon. Seems people just don't like the idea of those permanent screen buttons. I am coming around myself.
Click to expand...
Click to collapse
I have to agree the homescreen doesn't make total use of the space, but I guess it helps make it look less cluttered, however that is personal. What I meant about WP7 was the different approach to apps, specifically the side scrolling nature of everything.
I love watching the reactions of people who look at the HTC 1 concept, every single person I have shown it to so far has just kinda said either I want one now or wow... Rather interesting to see
As for the buttons, I am undecided personally. I can see the use of having more, but I am starting to like simpler, less cluttered looks myself. I guess in that respect the Galaxy S International is half ground, having one hard button and two capacitive, which you don't really notice too much if they're not lit up.
1. Does not matter, until it is high quality and not cheap plastic.
2.
- [at least] 4" sAMOLED display (or even IPS) with standard 480x800 resolution
Buttons should be:
- Camera and power on the right side
- Volume on the left side
- Menu, back, home buttons under the screen (preferably touch buttons)
- The latest Tegra2 dual-core CPU what performs at 2GHz max, and the best mobile 3d acceleration too
- High capacity but thin battery (1600mAh)
- 12Mp camera on the back, at least 3.2Mp camera on front (or something like the Adam, a rotate-able camera ontop) with dual xenon-led flash (and of course separate control, so they can be used separately)
- Projector on top part of the phone
- 1024MB RAM, 1024MB ROM(formatted for 512-512MB), dedicated 256MB SWAP, internal 16/32GB memcard, support for SDXC cards (capacity up to 2048GB)
- Bluetooth 3.0, USB 3.0, NFC, WLAN b/g/n, DLNA support, 4G support, USB Host functions
- Android OS of course, bumped with a nice slick UI, made by real designers, not some manufacturer (actually, Samsung is pretty good in these stuffs)
- Open system (no secure bootloader, etc) if you want it
3. Why? Because as a dev phone, developers needs the BEST device to test. If the stuff runs OK on the best, it should run properly on all other. Of course, device spec fragmentation is huge, we can't make all manufacturers to use the same CPU, motherboard, radio part, etc. That's where WinPhone7 failed great.
And also, let's provide something for the money they ask for a "smart phone". My current ZTE Blade knows a lot more than the HTC Legend, but costs half or even third of the money (here in Hungary a Legend costs around 90.000HUF, what is approx. 400-500$. The Blade, while it has more cocoa in it, costs around 200$). That's not right!
4. Why can't we have it?
That's easy. Manufacturers want people to buy their new phone when it comes out. Even if it costs a lot. They won't make an "Ultimate Phone", because then after everyone bought his/her own one, there would be no need of new stocks, and done. This way, they always keep up the interest for a slightly new phone (like Nexus S, a dumber Galaxy S, with Gingerbread), just to earn the highest profit with the lowest cost involved. The manufacturer who makes the "Ultimate Phone" would get rich at first sight, then until something more Ultimate is released, they just don't have income. See what I mean? Manufacturers use the first, big boom to earn back all the money they spent for "improvements" while selling almost the same phones. Just like Samsung as I said, or Nokia (N97 and N97 Mini, N8 and E7), or Sony Ericsson (X10, X10 pro; X10 mini, X10 mini pro; Vivaz, Satio, Vivaz Pro). Slight improvements, huge incomes.
fonix232 said:
4. Why can't we have it?
That's easy. Manufacturers want people to buy their new phone when it comes out. Even if it costs a lot. They won't make an "Ultimate Phone", because then after everyone bought his/her own one, there would be no need of new stocks, and done. This way, they always keep up the interest for a slightly new phone (like Nexus S, a dumber Galaxy S, with Gingerbread), just to earn the highest profit with the lowest cost involved. The manufacturer who makes the "Ultimate Phone" would get rich at first sight, then until something more Ultimate is released, they just don't have income. See what I mean? Manufacturers use the first, big boom to earn back all the money they spent for "improvements" while selling almost the same phones. Just like Samsung as I said, or Nokia (N97 and N97 Mini, N8 and E7), or Sony Ericsson (X10, X10 pro; X10 mini, X10 mini pro; Vivaz, Satio, Vivaz Pro). Slight improvements, huge incomes.
Click to expand...
Click to collapse
That's definitely a solid reason, and as much as we/consumers don't like it, the big companies will undoubtedly keep doing the same, just to stay in business. Still, I can see it being half possible if a manufacturer like made half-ground or something
Read these old posts made me lol 1600mAh high capacity lol I do not that was even high capacity when this topic was made!,OK here is my Ultimate phone for 2010 5.2in 940x560 LCD IPS display,SoC a custom One we well call t186 it has 4 A9-cortex core clocked at 1.6Ghz and a powerVR SXG543MP6 GPU with 2GB of LPDDR2 RAM,battery a 3500mAh battery,OS android honey comb 3.4,camera 10 megapixel rear camera 2mp front camera now that is a phone my friends!
Sent from my Z970 using XDA Free mobile app
tech_yeet said:
Read these old posts made me lol 1600mAh high capacity lol I do not that was even high capacity when this topic was made!,OK here is my Ultimate phone for 2010 5.2in 940x560 LCD IPS display,SoC a custom One we well call t186 it has 4 A9-cortex core clocked at 1.6Ghz and a powerVR SXG543MP6 GPU with 2GB of LPDDR2 RAM,battery a 3500mAh battery,OS android honey comb 3.4,camera 10 megapixel rear camera 2mp front camera now that is a phone my friends!
Sent from my Z970 using XDA Free mobile app
Click to expand...
Click to collapse
That's not even close to the s5 and note 4... lol... year old phone.
eloko said:
That's not even close to the s5 and note 4... lol... year old phone.
Click to expand...
Click to collapse
And actually the GPU would be more powerful the SGS5...
Sent from my Z970 using XDA Free mobile app
Why is the scroll stutter in sensation or in Android in general? WM7 or iPhone has it smooth from their first phone release.. is it something to do with screen refresh rate? Or its more OS related? Dont tell me that your android is smooth as hell..
For example when i scroll the app drawer or the settings page, i see stutter. I admit that some places (in some ROM) its smooth but most places its not. For instance, if you pan photos, its smooth.. but you scroll settings it stutters.
From a noob perspective i am guessing iphone handles "everything" like a image.. so scrolling, zooming, panning is smooth like we do on photos.. and i guess android renders as text or something else... just my wild stupid guess..
And, is there a way to fix this? or the android OS needs to be re-written? I am upset because sensation is much higher configuration than iphone 3gs. But the stutter present in sensation (even with any ROM) is not in 3gs. So i dont beleive its hardware..
Is it the screen and the capacity touch technique used by apple? i saw one video where the iphone screen is performed almost 99% close to maximum touch accuracy and sensitivity than any other phones..
see the video below..
http://www.engadget.com/2010/03/24/moto-touchscreen-comparison-recruits-robotic-implements-for-heig/
so what do you developers think?
1) Touch screen itself
2) capacitive touch technique / code used by apple
3) screen refresh rate
4) GPU rendering
5) the way OS handles the screen and images
I cant think anything else from my noob brain.. but you developers can.. anything can be done to fix this? From OS perspective.. not like my 'contacts' scroll smooth but not the browser?!
its a matter of display, its well known fact that iFail has top notch displays, whats on the other hand, basically the only possitive fact on that thing. So yes it is Apple's screen, same goes for iPad. Btw as for WP7, i own HD7 and its even worse then old Touch Cruise
shammanCZ said:
its a matter of display, its well known fact that iFail has top notch displays, whats on the other hand, basically the only possitive fact on that thing. So yes it is Apple's screen, same goes for iPad. Btw as for WP7, i own HD7 and its even worse then old Touch Cruise
Click to expand...
Click to collapse
If its all about display, how come cheap replacement display units from online can achieve the same thing in iPhone?
It got a be something else...
It's because of hardware acceleration. Too lazy to explain it now
Swyped from my HTC Sensation
iPhone uses the graphics processor to handle everything, not just games/videos/flash. The whole front end (UI) uses the GPU (graphics processor) in order to make everything look smooth. In a way, this is sort of a limitation of android. Hopefully Ice Cream Sandwich fixes it (it is rumoured to).
Bernardos70 said:
iPhone uses the graphics processor to handle everything, not just games/videos/flash. The whole front end (UI) uses the GPU (graphics processor) in order to make everything look smooth. In a way, this is sort of a limitation of android. Hopefully Ice Cream Sandwich fixes it (it is rumoured to).
Click to expand...
Click to collapse
idavid_ said:
It's because of hardware acceleration. Too lazy to explain it now
Swyped from my HTC Sensation
Click to expand...
Click to collapse
Had to disagree. If its GPU rendering why the scroll is smooth in gallary? why not in other text related lists? Android uses GPU only in image and videos?
Im going to take a guess here but i think its to do with hardware acceleration, coding infact of the operating system like apple code all their interfaces to be bosted from the gpu, however with android i would say that not everything is coded to run with the gpu and actually id say there isn't anything but if someone could list the support for what is that would help. From what i can find only things like the internet browser and games are in sync with cpu and gpu.
Maybe it's not only related to GPU acceleration because I'm running InsertCoin 2.2.2 ROM and ADWLauncher EX. With the stock kernel that comes with IC 2.2.2 the appdrawer and pretty much everything else (with some exceptions) is "iPhone-smooth" but when I tried the Unity 7.0 kernel I saw much more stuttering.
A lot of it has to do with the fact that Android is multi-tasking, real multi-tasking that is. iOS and WP7 (I think, haven't touched it in forever cause it's complete trash) do some save-state multi-tasking crap. Should scrolling be affected by this? I don't think performance should ever be sacrificed. But I think a lot of stuttering in the Android UI comes from it thinking about so many things at once.
I think the gallery is hardware accelerated.
Some things are, some things aren't. Comparison for ya: use Opera then Use the stock browser. Opera is hardware accelerated (uses GPU for rendering). See how smooth it is? Now use the stock browser and compare.
Don't quote me on this, but I'm quite sure that is one of the biggies ICS is supposed to fix.
Somehow, I think Samsung has implemented hardware acceleration for the Browser on their Galaxy S and S II line of phones. This was first noticeable when the Galaxy S got upgraded from Eclair to Froyo: the browser was much smoother (albeit glitchier.... mind you, these don't necessarily go hand in hand, you can certainly make a hardware accelerated browser without the glitches).
I think that's as far as that goes. Try a hardware accelerated video player like diceplayer (free 14 day trial in the market). Try playing a 720p or even 1080p video with it. It'll be smooth. Now go into options and change the renderer to software. Now it won't be hardware accelerated. And it'll be a slideshow.
It seems to me more of an issue of software optimization. Try scrolling with Sense 3.0 and then compare it to a sense-less rom, completely different. And then things change again depending on which launcher you choose to use. The Sensation's hardware is completely capable of buttery-smooth scrolling, it's just a matter of time till developers iron out the small kinks in their roms.
it looks like everyone thinks GPU is the reason for ios smooth scrolling. well, do you really think the first iphone released in 2007 has a powerful GPU and used for everything ios does? the 2007 first iphone does the scrolling smooth and the 2011 sensation cannot. i strongly believe its not the hardware!!! i guess there something wrong in the basics and google let samsung and htc finding their own solutions for some of the apps they create on top of android.
something else is wrong and since the users are not greatly concerned (or expressed) about this, this is not fixed yet. I wish and hope ICS fix this issue somehow..
I have been trying to find additional information about this issue and the truth is that this is the only thread that people have actually started to talk about it. If i got this right you are refering to the periodic stutter within scrolling in android and not any asynchronous glitches. Even though many blame GPUs, non HW acc. interfaces and so on, to me its a clear cut situation of refresh rates/fps clashes. Its the same scenario of outputing a 24fps movie to 60Hz monitor where ull get the same kind of periodic stutter (something almost eliminated when u switch to 50Hz). Its got nothing to do with wether the monitor is CRT or LCD, it all comes down to refresh rate vs fps. Ive clearly seen that on my O2x where, hdmi mirroring (on a 60Hz FullHD TV) is perfectly fluent while there are some visible periodic stutters everywhere within the android enviroment, except 3D applications. And what do you know.. The O2X's display has a 72Hz refresh rate! Isnt there anywhere within the android OS where devs/users can have a go with this? Changing the ' transmiting' fps of the whole OS? Let me know what u think sundar
So I have read and watched a lot about the i3 5.5, probably too much. In short it's a great in almost all aspects, save from
the performance, rendering it laggy/slow/choppy at times. Is it really that bad, or is it exaggerated, or perhaps downplayed?
I'm interested in intel of day-to-day use and how the i3 5.5 handles the OS, browsing, video and gaming.
Hopefully it's more a software issue than a hardware issue, which would make sense. Hopefully the 5.1 update will be out
soon. Are the European i3 5.5's also getting the last updates, or is it only the U.S?
Hopefully these relatively small issues will be a thing of the past soon. I am planning on leaving my Z Ultra (qualcomm 800,
adreno 330) for this device and that says a lot I think of how much faith I have in it
:good:
I have definitely experience lags here and there during day to day usage but haven't really found them annoying to the point where it is impossible to use the device.
Sure, the phone could have been fitted with a slightly more powerful GPU but overall the pros outweigh the cons. Only thing left is how commited Alcatel is with regards to software updates.
Power Users should definitely stay way. However, I have no qualms recommending this phone to anyone who is looking for big screen multimedia mobile device on a budget.
Thanks for your answer. A guy at Youtube said that after a couple of updates he received from Alcatel the phone performs much better, thus implying it is not a hardware issue, but a software one. He reported a perfectly lag free i3, with maybe once in a while a minor hiccup. Did you get any of those updates yet and if so, what is the difference in performance lag wise?
We have had only one update , that has resulted in a minor improvement in the UI response. Remember, the phone is still on 5.0.2 and that is responsible for the lag to a large extent. Plus - at the end of the day, its a 1.5 Ghz quad core with 2 GB RAM - The performance will be limited to whatever that means. If you are a power user , need a phone for an year or so, and are spending $250 for the Idol3 - you might want to see if you can score a OnePlus One 16GB for the same price. From a sheer performance perspective, it will come out ahead owing to a faster processor and more RAM . There are other drawbacks , that you should consider of course.
Thanks for your insight. The thing is that the i3 runs almost an all Vanilla Android, whereas other heavier skinned phones with the same cpu run perfectly fine, no hiccups either. Mind you, 33000 in Antutu is quite substantial and should be enough to run the i3 flawlessly. I guess you're on point by saying it's still on 5.0.2 and that is probably the main culprit. Hopefully Alcatel will tackle the issue soon, then they truly have a device they can be proud of for 100%, something the bigger brands and their "flagships" can learn from, imo. Did you see any improvement after the update?
My big issue was scroll lag that was in every browser, any page that had those menu overlays would stutter like a mofo. After the update it largely fixed it but still left stutter in ad laden pages. Once I installed Adguard my browsers became butter smooth. The Adreno 405 pushing 1080p res isn't doing well in 3D demanding games... if you need a phone for that get Zen2.
Thanks for the heads up. I just installed Adguard for the lulz on my old Samsung S3, quite nifty. I think the i3 will continue to impress and possibly get even better with coming updates.
Why on earth does your thread require I be in XDA 2015 theme to view it when none of the other threads do?
Good question. Probably because this thread is made of pure win
My guess is the idol using more of the 1ghz CPU to run a little cooler and save power, and when it is slow to switch to the 1.5ghz CPU is when we experience lag. Kind of like your using a 1ghz quad core phone. The idol has been proven to run cooler than its other 615 brothers, so it may be set to run on the slow CPU more.
It will definitely get better if they ever release 5.1.1. I'm not holding my breath.
I am already on the latest update, there is slight ( not sure if placebo ) improvement when scrolling web pages with mulitple images. Overall, I think it is fine unless you are power user.
Anymore input from users? What is your experience between before and after the update regarding to smoothness?
I found enabling gpu rendering for 2d made the phone run a lot smoother.
I was barely able to view this forum on it now I can scroll up and down and its buttery smooth (with the occasional hiccup here and there)
Changing default keyboard for Fleksy fixed all for me
Sent from my 6045Y using xda-developers.com, powered by appyet.com
Funny, I love that keyboard. Fleksy all the way, looks really clean too!
Try clearing your cache and/or doing a factory reset. Worked for me after the update slowed me down a little
no more lag since 10 06 update, this phone is finally totally great
When was it released? Is there a changelog?
there was a changelog when i got it, it's about stagefright and stuff
Hello everybody
I recently picked up new shield tablet k1 and played with it a bit until i noticed something strange i didnt experience with my other tablets - banding. Everything looks OK if you browse photos, websites etc, but any 3D game shows horrible banding in place of gradients. Im running stock kernel with OTA 1.2, no idea if it happened with 1.1 because i updated right away after first booting my tablet. Also checked every possible colour settings, force gpu rendering, wipe erase data and reinstalling it all also makes no difference.
It doesnt look like screen issue because gradients on lcd test websites look great. I'll pick some screenshots later when im back home to show my issue, just wondering if anybody else had the same problem and any tips are very welcome.
Could you give us some examples of games that show this problem? I personally haven't ever noticed this, but I'll try some new games (to me anyway) and let you know if I have the same thing.
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
Could you give us some examples of games that show this problem? I personally haven't ever noticed this, but I'll try some new games (to me anyway) and let you know if I have the same thing.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
It happens for example in Simcity Buildit, where its most noticeable on loading screens, but with closer look also on gui elements. Also in games like Rayman Adventures, Marvel Contest of Champions or Modern Combat
Here's screenshot from Simcity loading screen
Code:
oi66.tinypic.com/28lgem9.jpg
Same here but I only notice it when using full brightness.
I think the developers use only 16 bit graphics. That in combination with the large full hd screen makes that more noticable than on larger screens.
edisso10018 said:
Same here but I only notice it when using full brightness.
I think the developers use only 16 bit graphics. That in combination with the large full hd screen makes that more noticable than on larger screens.
Click to expand...
Click to collapse
This makes no sense as those games are supposed to be optimized for shield, developers would have to forcre 16 bit rendering for Tegra exclusively. Those games look better on much weaker devices.
Hi, I have also this problem playing Minecraft, Geometry Dash and the same Rayman Adventures. I thought it could resolve with a wipe but nothing. Strangest thing I noted is that is a software problem, since you can see those bands also in a screenshot or in a screen cast.
Probably we have to report to nvidia as an issue of the last ota
Did you contacted them?
I didn't contact them yet because im trying to gather more information, at first i thought its issue with my device but it seems this affects more tablets.
I did some tests. Seems like grey scales are more affected, but also other colours have this banding. I tried the same tests on Motorola Moto E and LG G3 and there aren't band. But doing a screenshot i can see the band in other phones too.
I don't know if this happens also on other firmware version or on custom ROMs.
I tested this with stock Android 5.1.1 and there was the same issue, so it's not ROM specific. Also worth noticing is the fact that all gradients look very good on images or websites. I'll try to test this with GLTools faking GPU info, the same trick allows Tegra to run properly XCOM: Enemy Within without graphical glitches.
If your tab is rooted, can you test if this happen in custom ROM too, or with a custom kernel? Maybe is nvidia fault.
However that is the weirdest. If I remember right, photos and web navigation aren't drawn by GPU, differently from games and particular test images, I don't want to say a stupid thing though.
Since I didn't rooted yet, principally for warranty reason, I have to wait any fixing ota, hoping that it isn't hardware fault
I tested it with GLTools faking GPU info with no positive result, so the last possible test is custom kernel and custom rom.
EDIT
Unofficial Kernel changed nothing. Didn't try with custom ROM yet and at this point i think its pointless. All seem that its Tegra driver behavior and unless it gets updated we have to stick with what we've got.
I believe I have the answer : the precision of the hardware (or firmware) texture interpolators is way lower than on other platforms. Maybe something like fixed point 24.2 instead of 24.8. See for details first result on google (I can't post url...) : "iq hardware interpolation"
I had extreme banding on a bloom FX on HP Slate 7 extreme only (tegra, was working fine on Nexus 5 (adreno gpu) and PC (GTX970)), on a dark orange gradient. I switched to manual interpolation in the shader, and the problem was gone. So I doubt the issue can be fixed with an android update, maybe a driver update, or maybe not at all as it could be hardware design, to improve performance (but at what cost !).