Related
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.
My note3 is awesome but the gps is a POS can anyone coming from the note3 to note4 for tell me if the gps function has been improved? Or is it just as unreliable(not locking on satellites) if its any better its worth the upgrade to me.....
I agree that it's worser than the one on my old note 1
If you can send me your gps.conf file I can fix it for you. Have to be rooted and it's in system/etc/gps.conf. Fix would work on any note 3.
606
I stopped rooting my phones because its just to much to maintain and keep up with these days. Initially my main reason for rooting was tethering but since i switched to tmobile and they give me 3 gigs for free. i found no reason to have to do it anymore.. i was always cool with the touch wiz roms anyway.. thank u for the offer though... can anyone else chime in on the difference if any in gps reliability between note 3 and note 4?
GPS receiver is quite deaf, horrible reception.
I just started noticing this weekend that my phone would find a lock no problem at first but can't maintain that lock. The GPS icon would disappear and then restart again after a few seconds to try and find a lock. Would happen every few minutes or so.
Yeah, I'm having an issue too.
It doesn't follow me, but it can pinpoint my location. It also jumps around to different locations around me when I'm driving.
Get this software and set it to auto update A-gps data. https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
I've been doing this since Note 2 and never had to wait more than 3-5 seconds to get full lock. It will entirely solve all your problems, and you don't have to root.
ozaghloul said:
Get this software and set it to auto update A-gps data. https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
I've been doing this since Note 2 and never had to wait more than 3-5 seconds to get full lock. It will entirely solve all your problems, and you don't have to root.
Click to expand...
Click to collapse
I'll give it a try, thanks ozaghloul.
I can confirm 100% issues with GPS on my AT&T Samsung Galaxy Note 4. I bought it Sunday (12/28/2014) and noticed instant GPS inaccuracies, teleporting, not updating correct route information, etc. I got home, OTA'd, tried again the next day, same issues. Took it into AT&T yesterday (12/30/2014), guy instantly swapped, I stood right there and showed him exactly what was happening on the brand new,fresh out the box phone. "Hmmm, I'd give it a couple of days to.....uhhh.....calibrate, then bring it back if it doesn't work." Screw that, wtf is going on? Why do a select few of us have the problem and why does it continue to happen to the same people?
In another forum, a guy took his back not 1, not 2 but 3 TIMES, same gps issues everytime......... Add me to the list of people who've had multiple phones and the same gps issues. SIM related????? Maybe? I can't have another phone, I absolutely love this thing.
**EDIT** Had a Note 2 for close to 3 years, not one GPS problem.
switch mode to gps only. in high accuracy mode it downloads google wifi data and tries to avoid using the gps chip so you bounce around depending on how accurate googles wifi mapping is based on APs googles streetview van saw.
GPS only mode with daily AGPS data will be the best.
I've done everything under the sun. Nothing helps.
I will try zurkx's info tonight and try to remember to turn it on for the foreseeable future and see what happens. The issue is sporadic for me and I don't have it on while I'm driving all the time.
Zer()C00L said:
Why do a select few of us have the problem and why does it continue to happen to the same people?
Click to expand...
Click to collapse
I fear it's a bit different: Just a few people get aware of the problem, many others simply don't notice or don't want to notice it.
Just have a look at my thread - pretty detailled: http://forum.xda-developers.com/note-4/general/gps-close-to-unusable-t2948602
Try rebooting in airplane, it seems to have alleviated the issues. Now I have a horrible download speed problem....
Does anyone know why the action memo often takes more than 10 secs sometimes to launch. Its very annoying especually when I'm trying to.write.something quickly
Sent from my SM-N910P using XDA Free mobile app
What? 10 seconds? Action memo on my Note4 is opened in just about 1 sec.
I was most likely exaggerating the time. Exact length of time but it wasnt instantaneous, which was frustrating when say for example i was saying oh note 4 this is one of the great features and it would be delayed.more than 1 or 2 secs which then would turn into embarrassment. It was a noticeable delay for.me.to post this topic.
Sent from my SM-N910P using XDA Free mobile app
Hi guys. Hope your all well.
I just got my note 4 (SD) a couple of days ago and seem to be having the same issue. All I have done so far is just rooted the device. So I don't even have a custom ROM. Yet, when I take out the s-pen, action memo takes ever so long and trust me, mine is longer than 10 secs. And just to top it up, I tried whilst reading your posts and now I have written this post on my phone, action memo is still not coming up!!! This is annoying.
Have you had any luck? @op
It has seemingly gone away latley. I did update fully to NK2 via ODIN then rooted on stockish NK2 deodexed. I dont know if it was a software bug or what. I was beyond frustrated.
Another issue that annoys me is often at weord times it freezes up when typing then there is a noticeable delay. Already had ot happen while typing this!
Experienced anything like that as well? Its still present was just wondering.
Sent from my SM-N910P using XDA Free mobile app
aburns7487 said:
It has seemingly gone away latley. I did update fully to NK2 via ODIN then rooted on stockish NK2 deodexed. I dont know if it was a software bug or what. I was beyond frustrated.
Another issue that annoys me is often at weord times it freezes up when typing then there is a noticeable delay. Already had ot happen while typing this!
Experienced anything like that as well? Its still present was just wondering.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Action memo update: it never did pop up at the end. So rebooted the phone and tried as soon as it booted. And it worked straight away. So it seems to work ok for a bit after a reboot but then eventually disappears to a world of its own which i cant reach lol. Another thing i noticed compared to my Note 3 , action memo is not listed as "action memo" in root/system/app. It also does not showup in the list of applications via settings. I was checking this to see whether greenify hibernates it. But i cant tell if i cant find the damn app! Lol. Any thoughts on that ?
Regarding your question, i do tend to have a few lags whilst typing or doing certain tasks one after the other. Where i found the most lag with the keyboard is in whatsapp. Sometimes the lag is so bad that i think the phone has frozen and is about to reset itself (have had that before on note 3 a few times) but eventually the keyboard catches up with my fast typing fingers. I have also ,about 20 mins ago ,did the build prop edit regarding secure storage/s health as i have xposed framework installed. So lets see how much difference if any, it makes regarding lags. Btw, I'm on NK4.
18:43 update: action memo does not pop up now. If I reset the phone, it'll pop up. This is really p***ing me off now.
18:46 update: May have figured it out. I believe action memo is now embedded within s note.....which I put in the greenify list to hibernate. I unhibernated it and action memo seems to pop up with no problem. Will monitor it.
Can someone perhaps help me???? Mine doesn't even work!!! I updated my note 4 to lollipop a long time ago and last week I did a factory reset and now the action memo crashes almost 50 milliseconds after it pops up!!!! I looked everywhere and found only one solution that worked for someone having the problem and it was changing the animations in dev tools back to 1x. Mine were 1x but before I changed them to .5 and then back to 1 and I tried changing these several times and it DID NOT WORK. Can someone help??
I don't find solution
I have exactly the same problem. 10 seconds. It is not an exaggeration. Someone has a solution?
rheise
Galaxy Note 4 SM-N910U / Android 5.0.1
Hello.
I enjoy my Nexus 7 2012 (Wi-Fi 32GB) tablet very much, when it is working properly and, unfortunately, that hasn't been often for some time. Android 5.02 helped a bit and the tablet is currently running 5.1 from a OTA update, which seemed to help a bit more. Android 5.1.1 has been mentioned however, I am not sure my issues will be helped by an update. For this reason, I am here to ask for advice or suggestions as to what I should do next (if anything!)
My first issue was the battery. The battery only lasts four hours per charge and since it is the original from 2012, I have ordered a new one and am awaiting its arrival. This tablet was a gift and whatever warranty it had has most likely expired so I am not concerned about invalidating a warranty. I hope that a new battery will make a big difference.
However, it is the second problem that is really annoying. The screen on my tablet freezes often, in any program and at any time. After charging the tablet, I've learned that it is best to restart the tablet to prolong the amount of time before the tablet freezes for the first time. Reading an article, for example, is a problem as I can read the first page but when it is time to slide the screen up to scroll to the next page, I am at risk of the screen freezing and it definitely freezes before page three. When typing a comment on Facebook or Twitter, etc. either they keyboard freezes while typing or if I can type the comment, the screen freezes before I can press the send key. I have other ways that are less portable to access these types of programs however, portability is the reason for a tablet. Using the tablet as a reader, I usually do not have any problems swiping page to page for usually as long as I'd like (although the swiping motion is a potential problem outside of the reading app.)
I backed up the tablet just prior to the 5.1 update and reset it to factory settings and for almost a week the difference was amazing. However, even with 5.1, the tablet is back to freezing again. Regarding the 32 GB internal storage; the actual available space after the OS is 28.17 GB and my available 23.90 GB. Due to the tablet's lack of response, I only reloaded a small number of apps and then, with the screen freezing multiple times in the four hours the battery allows, I uninstalled even more apps to get where I am now; I have never exceeded 50% at any time. In a browser, I often have more than one window open, yet it is the only program open. Sometimes, Facebook and Messenger are open at the same time but not always. If I get an incoming update, such as CNN, etc. if I open that for a few minutes, I'm risking another freeze. I am continuously aware of what programs are open and close them with the bottom square icon on my tablet. I have two frequent errors: SYSTEM UI is shutting down and the Process System is shutting down and they happen often. I am using Nova Launcher and the other Launcher on the tablet has been force stopped. I should probably note that I did the cache cleaning process two different times before I reset the tablet to factory settings.
Would going to something like the Cyanogen Mod be of assistance with this situation? There is an Official CM12 Mod available for this tablet however, the article I am referencing is from January 2015, written by Vinod Yalburgi titled, "Update Nexus 7 2012 (grouper) to Android 5.0.2 with CyanogenMod 12 official ROM." The tablet is already at 5.1 though and, as you have surmised correctly, I am not fluent in Mods of any type so I am unable to determine which mod is the best in this situation or if a mod is not going to be the right answer. I am open to rooting the tablet; the huge benefit I'd appreciate is the ease of creating a full back-up.
Is there another, more appropriate solution? My main concern is that if I wait for Lollipop 5.11, whenever that might be, it will not improve the issue with the screen freezing and I will have waited longer and ultimately gotten nowhere. Going back to KitKat 4.4 as I have read others have done is not appealing but if is the best solution . . .
Thank you for your patience with all of these details. I am hoping that with this info and all of the experience here, you can help me move in the right direction. Your time and any and all of your helpful suggestions are appreciated! This tablet can still work very well and as it was a gift, I want to make it work (on the days I do not want to hit it with a hammer!)
CShirey
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
? Take me to your Leader ?
Not the option I was hoping for but maybe the solution!
eLCruz said:
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
Take me to your Leader
Click to expand...
Click to collapse
Thank you for your suggestion! Does your tablet work well with KitKat 4.4.4? Any problems with freezing and battery drain? I have continued on with my research on this trying to determine what other owners have done in a similar situation. Lots of complaints but not a lot of answers, so far!
CShirey
General surprise at the lack of helpful replies!
I am grateful for the reply I received however, I am disappointed in the general lack of interest. Whenever I come to review posts here, I see that generally, most posts receive multiple answers. I am in the right forum . . . Is my question considered to be too simple . . . or did I miss an unwritten rule? Thanks.
CShirey
Sorry, had turned notifications off and forgot. It's working smoothly on 4.4.4! Should have never updated, IMO. I believe lollipop will be Google's windows vista... Hope every thing works out.
?Here, there be Whales...?