yashsingh1/xdaforums huggingface dataset:
[Nexus One Q&A, Help & Troubleshooting] dalingrin:
Okay here is a video. http://www.4shared.com/video/lZHlb64B/VID00015.html

-Notice the Nexus one is displaying less elements. It has flash disabled and ads are blocked. Nexus One is running froyo and has an overclocked kernel for good measure.

-The iPhone 3G (not even an iPhone 3GS) is displaying more of the webpage at once and is displaying ads that the Nexus One is not.

Not only is the frame rate much much faster on the iPhone 3G but it also doesn't lag behind my fingers motion. It almost feels like there is a perfect 1 to 1 scrolling with my finger whereas the Nexus One is lagging behind my fingers input.

I'm not talking about the launcher. See the video.
[Nexus One Q&A, Help & Troubleshooting] rjhay22:
Nicely said... And I couldn't agree more. Only thing I wasn't satisfied with was the N1's launcher. Stock launcher clearly isn't as refined as the IPhone. But after launcher pro, everything is perfect.
[Nexus One Q&A, Help & Troubleshooting] attn1:
Are you asking OP out on a date? :D
[Nexus One Q&A, Help & Troubleshooting] xManMythLegend:
Lol....no..he'll probably take me somewhere lame like an Apple store.
[Nexus One Q&A, Help & Troubleshooting] shrub:
of course. because i've pointed out a genuine issue with Android it makes me an apple fan. :rolleyes:

And thanks to the few people who can see this is a genuine issue and i'm not just some n00b who wants to troll and say the iphone is better.

that video demonstrated perfectly what I am saying. I really do defy anybody to load up a large web page (actually any web page) on the 3gs and and nexus one and tell me the iphone doesn't handle all the scrolling much smoother.

And the "iphone can't multitask so it will be smoother" argument is silly, because that isn't the reason for the choppy performance on the N1, it's the lack of hardware/gpu acceleration.

the launcher as well does just sum up how bad it is, although launcher pro fixes this. why isn't the stock launcher like that out of the box?

and thanks for the link staples17 i've seen that before when I was researching into this issue, i've gon ahead and starred it now.
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
I just went and tested the same page.

Granted, it's not 100% smooth, but nothing like your video. Moreover, my Nexus shows more of the screen, yours shows 2 photos on the moving row, iPhone shows 3, mine shows 2.5. Moreover, the "lag behind fingers" that you see is because of your jumpy scrolling - I see roughly the same lag as iPhone. And I have no ad blocker.

Your Nexus is screwed, and that's not a good starting point.

Also, it looks like iPhone shows the top of the page - moving row - as a static picture. Which is simplifying things for it, and screwing up the internet. But who cares...

And I'm on Eclair, not even Froyo.
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
It's great when people talk with great aplomb, but without having a basic clue in how things work. I won't even start explaining the splitting of work between SW and HW, between CPU and GPU, etc. I'll just suggest you stop writing things you don't have any idea about, and stick to user experience explanations, without trying to guess, what causes this or another part of this experience.
[Nexus One Q&A, Help & Troubleshooting] dalingrin:
Its not static on the iphone.

There is nothing wrong with my Nexus One. I've tried nearly every rom and kernel and its always the same. It is a fundamental difference between iOS and Android architecture.
[Nexus One Q&A, Help & Troubleshooting] Clarkster:
Ok, just checked out your video. I know you don't want to admit it, but there must be something really wrong with your Nexus One. I went to the same site on mine and it was a silky smooth as the iPhone in your video.

I am still stock 2.1, using the stock browser. Perfectly smooth. Don't know why yours is jerky like that.
[Nexus One Q&A, Help & Troubleshooting] rsm86:
I agree wholeheartedly with the OP and xManMythLegend.

I love my Nexus One, but scrolling just isn't as smooth as on "the other side". Which isn't to say this phone is any lesser, or that I would rather be eating apples. I love my phone and android and wouldn't trade it for anything right now, but that doesn't change the fact that with the hardware we have, we can and should get better scrolling. There used to be a post on this thread I believe, which I'm not finding anymore, linking to this:

http://code.google.com/p/android/issues/detail?id=6914

I already went and starred the issue.
[Nexus One Q&A, Help & Troubleshooting] dalingrin:
Its only jerky at the top section of that webpage. If you scroll slightly past some of the dynamic content then it is much faster. It is also faster if use a flicking motion rather than keeping your finger on the screen. Further, a webpage like XDA is also much smoother.
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
I see, people always want a proof for their eyes. OK, I wasted 1/2 hour on that. With the top of the page, as you noted before. Now watch this and count the differences from your video as I wrote them in previous post:

[YOUTUBE]h2ZoEIVeQoE[/YOUTUBE]

[edit] The jerkiness in a couple of places on video can be attributed to my wet fingers (+32C outside and I'm sitting without A/C), refusing to slip on the Nexus screen. I believe it can be seen on the video. Running CM5.0.7.1.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
wow this shows such a complete difference from the other video next to the iphone. and i agree, your video is how smooth my nexus is on that same web page. that guy's nexus is clearly bogged down with something wrong with it, i dont know what though. but again the nexus to my eyes looks just as smooth as the iphone, so i'm standing by that opinion.
[Nexus One Q&A, Help & Troubleshooting] attn1:
It was a just a joke.

Look, I have started my share of threads that haven't exactly been popular around here, but I never expected to do it without getting flamed. It goes with the territory.

If you have less than a half dozen posts and start up a new thread in the Nexus One forums with a title like "GPU support!! WHY NOT???????" and then go on to make unfavorable comparisons between the Nexus One and the iPhone, you'd better be ready for some heat. Right or wrong, it looks a lot like trolling, even if it's not.

So if you want to make an argument, go ahead and make an argument, but if you can't laugh at something as genuinely funny as his reply, then maybe your sensitivity is better suited for book reading than rabble rousing on a forum full of die hards.

Instead of getting all offended, you could have just as easily offered to take him for a body wax and a tub of ice cream. It was a joke.
[Nexus One Q&A, Help & Troubleshooting] dalingrin:
Thanks for taking the time to post the video. I'll have to flash back to Cyanogen to see if it clears my sluggish scrolling. The weird thing is I just helped someone migrate from an iPhone to a Nexus One last week and their brand new Nexus One scrolled just like mine.
[Nexus One Q&A, Help & Troubleshooting] Eclair~:
Actually, anything favoring the smallest of Apple related things gets you flamed here. Is better to simply not mention Apple or related products at all it seems.

Random sentiment..
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
But that's not even the whole point. The second video posted showed a complete opposite experience on the smooth webpage compared to that first video. So its like hard proof imo.
[Nexus One Q&A, Help & Troubleshooting] attn1:
True enough. Edit: I will add that out of the box the N1 isn't as good as it can be, unlike the iPhone. And comparing stock phones isn't comparing apples to apples (notice the shameless pun there) either.
[Nexus One Q&A, Help & Troubleshooting] dalingrin:
I just wiped and flash Cyanogen 5.0.8-t5 and it is indeed smoother. It looks like scrolling in Jack_R1's video.

It seems scrolling is worse in Froyo even with all flash and ads disabled.

A better example is to go to www.ign.com

Even with Cyanogen installed, scrolling is pretty choppy on a Nexus One and a perfect ~60fps on a wee iPhone.

Which again goes back to the original point. I wish Android took advantage of the GPU like the iPhone does. I also think this is going to be needed for Android to scale to larger and higher resolution displays.
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
What bothered me more, is the difference between the browsers. Please note that my video shows 2.5 top row icons, while your shows only 2.

In any case, to make sure, I zoomed in to the same level, but it didn't change things.

I also noticed something: scrolling from the slowest speed up to some threshold, things are butter smooth. Then at some speed things get a bit jumpy. Still not as jumpy, but jumpier.

And then I looked some more, and saw the correlation with the movement of my own finger. It looks like the touchscreen input isn't smoothed out - and that's what can cause the scrolling to look bad. If you make sure that the finger stays pressed equally against the glass/protector all along and doesn't skip at all - the scrolling will be smooth. If you launch kinetic scrolling - it'll be quite smooth too. But if you move and your finger isn't contacting well (the touch isn't registering constantly and moving) - its movements won't be smoothed out, and you'll see jerkiness. The same one that accidentally found the way into the video I posted earlier.
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
You're mentioning scaling, but I bet you didn't consider that Nexus screen is already has more than 1.5 times the pixels of iPhone 3 on each axle? So it needs ~3 times more processing for the same scrolling. And the GPU is a bit below 3GS.

Actually, I think that developing a smooth experience takes time, quite a lot of it. And given the priorities which include lots of other stuff, I believe Google did the right thing - approach things from another angle, first have lots of functionality intact on a "good enough" level, and only then improve the visuals from "good enough".
[Nexus One Q&A, Help & Troubleshooting] dalingrin:
I agree scrolling with your finger in contact is not as smooth as letting the phone do kinetic scrolling. That isn't the problem that bothers me as much though.

My problem is that the more dynamic content on a webpage the slower the scrolling is on Android. A busier page like ign.com is a better example. Because the iPhone is rendering the page in OpenGL, it doesn't matter how much content is on the page. It is also always responsive and scrolls perfectly.

Either way, I'm glad you posted the video because now my phone scrolls a little smoother :)

I just hope when Froyo is officially released that scrolling is at least as fast as Cyanogen.

I did consider that. I'd also be willing to bet that the new iPhone 4 which has an even higher resolution screen will be perfectly smooth as well and no slower than a iPhone 3G.

I mostly agree with you. I wouldn't have sold my iPhone 3GS to get a Nexus One if I didn't.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
yeah i'm kinda disappointed that the GPU isnt better too. at least the upcoming galaxy is supposed to have superb GPU chipset.

anyone know what cyanogen has done that makes the browser so much smoother, compared to stock ROM?
[Nexus One Q&A, Help & Troubleshooting] Marine6680:
I noticed periods of poor performance and scrolling at times and other times it will be fine. I believe it is from the random high cpu loads I am seeing in froyo. When using a system monitor app I notice the cpu use can jump to 100% for no reason; I sometimes pick up the phone after it sits unused for a while and find it hot from the high cpu load even though it was in standby mode. I must reboot the phone, sometimes a few ties to fix the issue. I do hope it is just a bug and not my phone.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
It's just your phone. I'm on froyo and use system panel monitoring for a week straight, and no strange CPU usage whatsoever. It will go 12 hours with no activity above 0.5 %. Even longer. You should use system panel, turn on monitoring, and hit the "top apps" list and it will show exactly which apps or processes are using the CPU excessively.
[Nexus One Q&A, Help & Troubleshooting] Marine6680:
I do... I did... no dice...

It gives me no info that is out of the ordinary; there are no stand out apps that I can see as the cause. I did drop my phone a few weeks back, maybe that caused an issue.
[Nexus One Q&A, Help & Troubleshooting] Mr.Kakarot:
I loved my 3g and 3gs.... but now that I am sporting a n1.... I am not going to die without it, live wallpaper had me at... live :P

I do tend to agree with the op though, it is a smoother experience but not necessarily a better one.... just more polished I guess. Heck, my phone even brain farted and froze the other day... glad the battery is removable..... end result for me is, my n1 does what my iphones did... and a little more. I am also sure, I have not scratched the surface on this thing.... as it is still stock :(

I like the direction google and droid is going and I am glad I took a chance on the n1, I just wish froyo would get here....
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
That's just strange. So in system panel under monitoring, which shows up at the top of your "top apps" list and what is the highest percentage? For me, I run the monitoring in the background all week long. If I check my usage say, when I first wake up, and look at the last 8 hours, nothing breaks the 1% mark, and the top spot is system. And I have a bunch of services running, which all show as 0.1%. They are: official Twitter, touiter, battery life widget, Google listen, HTC keyboard, Facebook, Google finance, handcent, mint widget, digital clock widget, network monitor widget, Google voice, gmail, news weather widget, maps, and web browser.

But these all show up as 0.1%, yet they're active services and widgets etc. I can't imagine any more or less killing battery more than that.
[Nexus One Q&A, Help & Troubleshooting] :
I've read that froyo has problems where CPU usage goes up to 100% haven't experienced it myself though
[Nexus One Q&A, Help & Troubleshooting] Marine6680:
I see similar usage, system is the highest use.

This happens every time I charge the phone, 100% cpu the whole time. Sometimes it gets stuck and needs rebooted, other times not, and the random high use happens 3 or so times a week on average.

I have confirmed this high use with other monitoring apps. SystemPanel reports 45% system and 55% user on cpu. System does show a small use as well as systempanel (because it is running) but nothing else.

I believe the high load is really just idle cycles, because the phone is a little laggier but not unusable; though resource heavy apps slow down to a crawl when opening and running.
[Nexus One Q&A, Help & Troubleshooting] johnnie93:
we should make a dedicated thread and sign it and send it to Google :D
[Nexus One Q&A, Help & Troubleshooting] kuntau:
There is already thread on official android bug mentioned few page back. Now just go there and star and comment until we got google attention ;p

-------------------------------------

Sent via the XDA Tapatalk App
[G1 Android Development] kingklick:
[ROM] [v1.3] [FAST] KiNgxKxlicK Slide2G1 "NO LOADING SCREENS" {6/29/10 1:27pm PST}

My G1 was long ago fried, I have no G1/32b. Read my sig if you desire.

First, a foreword:

It is finally here. I have been working on this for sometime. I worked on it for weeks then a month or so only to find it did not boot. Had a syntax error in my init.rc. Well it finally here and it boots! :p So please enjoy post all bugs with a logcat and enjoy. I will put all the work into this you would expect from me.

ENJOY ALL!

Broken:

* Bluetooth (expected, its a sense ROM)

* Lights (Download HeroLED from the market)

* Browser Flash

Release Name: KiNgxKxlicK Slide2G1

Release Version: 1.3

MD5 Sum: 9b7ba794c5a531cf0aa38788be45ec36

Credits: Cyanogen, CCyrowski, ChiefzReloaded, Stericson, JAC, Eugene373, miketaylor00, Jubeh, Twisted, Fictionless, Shafty, any other dev I forgot to mention, and most importantly, my patient lady for putting up with ma devin' :D

Base Firmware: 2.1

Radio Required: Any

SPL Required: Death SPL

Partition Layout: Fat 32--EXT 1/2/3/4--Linux-Swap

Wipe Required: Full Wipe update

Special instructions: Linux-Swap partition 160Mb (Let me know if another size works better!)

Download:

Older Versions/Bases:

Patches/Fixes/AddOns:

Just like any other dev, I am not responsible to whatever happens to your phone *surprise* :p

ChEerS :cool:

"I live to DEV another DAY" -My quote

Follow me on Twitter if you like my work: www.twitter.com/kingklick92
[G1 Android Development] kingklick:
Changelog

Version 1.3

- New Base (full wipe)

- Now using Kernel #10! (BIG performance increase)

- Packed in every kernel module you'd need :)

=- turbo support

=- multi-tasking patch

=- same scheduler as #9

- Using the updated Multi tasking (kernel)

- Added Phone Prioitizer app to speed up incoming calls USE IT *thanks miketaylor00*

- Cleaned up first boot, still takes awhile though

- Cleaned up ramdisk

- Updated framework for loc *thanks russ*

- More I'll add

Version 1.2

- No wipe update

- GPS fixed *thanks for pointing it out gladiator*

- User.conf updated

- Shutdown is fully working! You can power off your device now

- Cleaned up ramdisk

- Edited init.rc for more functionality

- More edits to build.prop

- Dalvik vmemory intake increased

Version 1.1.1

- No wipe update

- May only be a .1 update but IS NECESSARY (much smoother and necessary bug fixes included)

- Camera fixed

- Updated user.conf for optimal performance

- Minor cleanup

- HTC loading screens should be gone

- Removed Bluetooth (broken anyway)

- CPU frequencies updated (576Mhz max)

- Swapped some libs from a previous release

Version 1.1

- No wipe update

- Fifo is set

- Fifo=1

- Removed Meltus Audio Hack

- Radio tweaks

- Data tweaks

- Added Swype

- Updated framework for browser fix *thanks ennatefox*

- Updated libs

- Disable Browser flash, it is broken and will crash browser

- Wifi is fixed (wifi fix not needed)

- Updated build.prop

- Testers have said 160Mb Swap is working great

- More I will add

Version 1.0

- First Mytouch slide release

- Using optimzied apk's, but more to come as usual ;) *thanks russ*

- Kept it old school, usual King ROM layout

- Rosie is the fastest I have seen it on any sense build

- Cleaning things up on first boot

- Give first boot plenty of time, it takes awhile

- Fixing Permissions on each boot

- Auto aligning everything

- Using my latest kernel #9 *fastest kernel of mine yet*

- Updated Ackprash Nexus boot animation

- Kernel has overclocking capabilities!

- Everything works that you would expect (wifi, gps, etc)

- Three usual partitions required (Fat32/EXT1-2-3-4/Linux-Swap)

- A2sd is automatic! Just have that second EXT partition

- Linux-swap is automatic! Just have that third Linux Swap partition 150Mb+ (Testers let me know what size is best please)

- Init tweaks all done by yours truly

- Using my Ramdisk

- Multi Touch enabled and is system wide

- User.conf called on and enabled

- Clean Shutdown and reboot working

- Mapped correctly for G1

- Mapped correctly for Sapphire 32b

- Some apps moved to /data for your ease (to remove them)

- Added AppPack from T-Mo

- Added Astro File Manager (Nope, I haven't changed!)

- Added Wireless tether

- Added Wired tether

- More I will remember!
[G1 Android Development] Ace42:
Do faves and genius button function correctly?
[G1 Android Development] kingofyo1:
YAY FINALLY!!!

downloading,flashing, will let ya knwo how it turns out!
[G1 Android Development] Briix:
how about a port for 32A sapphire? :D
[G1 Android Development] Markus214:
Browser

Can anyone confirm browser working? Broken says only lights..

Wait for confirmation than flashingggggggggg =)
[G1 Android Development] kingofyo1:
lol he hasnt even finished uploading yet, so cant confirm or deny anything
[G1 Android Development] kingklick:
my testers havent said anything about browser being broken.... :)
[G1 Android Development] lightninbug:
well from flashing all of kings other roms..this one should be a real treat! So glad Cyanogen part 2 (kingklick) is back!!!!!
[G1 Android Development] Bzerk1:
lights?

does that mean the LED's? or like backlight or backlight for keyboard, all of the above?

oh and btw hate to get killed on this, but im guessing BlueTooth isnt working still?

I love your work king i just want to know if i can rely on the rom for business.
[G1 Android Development] angelicrequiem:
King, you are THE man! i can't wait to try this out... Already nandroid'd :D
[G1 Android Development] MotoMudder77:
Most likely all of the above, just like the legend, Sense UI ROMs out. Theres an app on the market............cant think of the name but should do the trick.
[G1 Android Development] protomanez:
Is this...fast?
[G1 Android Development] angelicrequiem:
Heroled, i believe it is...
[G1 Android Development] BigWorldJust:
How's the battery...
[G1 Android Development] jcarrz1:
edited. :P
[G1 Android Development] Markus214:
haha kingof just read that dl was still uploading lol and no bt does not work still because its still a Sense build.
[G1 Android Development] smjfosho:
is king cool with you posting that?
[G1 Android Development] jcarrz1:
lol idk. unquote me please. it was in his 4shared folder tho... its public.
[G1 Android Development] Markus214:
Prediction...

If i may make a prediction here... I believe this thread will be a very active hot thread very fast and reach over 10 pages in a half hour its 5:12 Eastern Time for me so lets just be safe and extend it a little longer 6pm this thread will hit like 30 pages lol

"It's Good To Be The King"

Kings Back!!!
[G1 Android Development] protomanez:
Very very exciting :D This thing is faaaast!
[G1 Android Development] Abhi_UK:
Is swap automatic on this rom?
[G1 Android Development] Ozonethegreat:
Re: [ROM] [v1.0] [FAST] KiNgxKxlicK Slide2G1 "Touch Myslide" {6/10/10 1:17pm PST}

I have an interesting thought that may of some use to dev. I too have the "my" loading screen each time when loading the home screen. I tried the MT kernel found here in the forums. I noticed after flashing, I no longer had the loading screen issue but after about an hour, the system became laggy and started responding like previous sense roms.

Is this because the MT kernels are based on cyan's source while king uses something different? If not, is there a more effective way of implementing it? Or am I just being a noob? ;-)

-------------------------------------

Sent via the XDA Tapatalk App
[G1 Android Development] lightninbug:
which version did you flash of the multitouch kernel?
[G1 Android Development] Acidox:
Not sure if this has been said or resolved, but when I load this ROM onto my phone, it just sticks at the G1 loading screen and doesn't get any further.

Really need a good fast Sense ROM for my G1, havn't been able to find one which had a good speed apart from one which had no widgets and gave me bad signal.
[G1 Android Development] lightninbug:
well if your not sure if "its been said or resolved" try the f'n search button or try reading
[G1 Android Development] Shatterv2:
Here we go again..:(
[G1 Android Development] Shatterv2:
Try to not be an "f'n" douche over a phone forum. There are easier and less proclaimed ways to do what you just did. XDA is becoming something that it wasent before, a daycare school for 12 year old boys.
[G1 Android Development] Ozonethegreat:
I've tried the 2.6.33.34 version 7. I was thinking of trying the 2.6.34 but wasn't too sure about it.
[G1 Android Development] protomanez:
No, the XDA G1 Dev thread is. I like to call this place the slums and the high end phone sections civilization. There are still some educated people around but most are going to different phones because THEY can afford them, while immature kids are stuck with their G1s. I'm not saying everyone is like this but I'm finding more and more idiots posting.

/end rant

Let's try to co-operate here and not make this place a shizhouse. Keep it clean people.