yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] buachaille:
Get an iphone and ditch android man. you really get on my nerves. I want you to buy an iphone and ditch android and so does steve jobs. so just do it and we can all be happy :D

Here are some of "your" reasons why you should (your posts) :::::::

------

Google releasing another half baked product?

Not surprised.

------

Google hasn't delivered a decent browsing experience. They create android and if the stock browser sucks then it's an android problem. The browser is not some special feature that can excuse these...

------

I have tried different roms and no they have not made browsing any better. iOS browsing speed is far ahead of what Android...

------

Browsing on Android is terrible, even with flash turned off or set to 'On Demand'

The whole readjusting the page thing to fit the width of the phone slows it down way too much.

------

No it doesn't, but if you don't believe iOS generally has better quality apps than Android does, you haven't spent any significant time with an iOS device.

------

Glad to see people are realizing what terrible customer service Google has. They just don't care. They're concerned with getting Android on as many devices as they can so they can rake in the ad...

------

Unless things like this change, I won't be using the Android platform in the future. One of my top priorities/needs is great app support. If you don't have that, all this new hardware is useless IMO.

------

If you want to be Google's guinea pig, I guess it's worth it.

If you want a polished experience, nope.

------

I don't believe anyone that says browsing on their NS is "smooth"

You must have never actually used the iOS browser, if you can call this one "smooth"

------

Anyway, I'm going to shut down my Ipc and brush my Iteeth, and go to my Ibed.
[Nexus S Android Development] buachaille:
And yeah, just to avoid any confusion, I really pretty much hate apple.

I had an iphone 4 for 3 days, and it had "death grip" issues. Also, it would not allow me to attach a file when I was forwarding or replying to an email, it takes a tantrum if you want to view a flash website, you can't change the keyboard, and in general it was so locked down that I just did not want to know.

I came from blackberry, which lets you do what you need to, I tried ios (which doesn't), and then I went to android (which like blackberry, lets you do what you want).

So go and enjoy your sweet ios browser man. :confused:
[Nexus S Android Development] bringonblink:
The way I see it, out of the box ios works, its simple, it does not confuse people, what you see is what you get.

Once you start modding android though...the options are endless.

Android in the hands of someone who had only every used ios, aka has no idea of mods etc, probably is not a nice experience.

Ps stuck android browser is not yet gpu accelerated, hence it lags. Updates will come though. Opera is a good replacement
[Nexus S Android Development] meetagrawal:
What else do you want me to explain about random reboots? Several people in this thread have posted this. Am I somehow supposed to know what's causing the random reboot? It's an issue, and I posted about it. That's what this thread is for correct? Or am I supposed to just say only positive things about the ROM? It's a feedback thread so the guy who is putting in the time to create it can make it better for me, you, and everyone else.

I know how to use battery stats, and like I said, I was using it below average. The 1st thing on the list was Android System. My phone is not overclocked, but it had 15% remaining after 13 hours. It's not always an app that can kill battery. Ive used plenty of different ROMs which have affected the battery in different ways.

Sorry to burst anyone's preconceived notions of Apple users are dumb.
[Nexus S Android Development] meetagrawal:
Here are my stats for today. Display on for 45 mins
[Nexus S Android Development] Ok_Kaleidoscope5109:
Regarding this whole iPhone conflict:

I came from a Motorola Milestone. I had an iPod Touch 1G, iPhone 3GS, and an iPod Touch 4G. In fact, I sold the iPod Touch 1G after I got rid of my 3GS because I thought the 3G iPod would have a camera. Boy was I wrong.

My Motorola Milestone was SO SLOW even overclocked to 1.1ghz. While CM6 sped things up greatly with the recent memhacks that devs have been making, browsing wast errible. I bought an iPod Touch 4G in November for this reason. I was SICK and TIRED of the browser being choppy. I was SICK and tired of the browser not handling websites. Flash was useless because my 1.1ghz Milestone still could not handle it. Despite having a quadrant score close to a Nexus One, Google Maps would run out of memory a lot. I spent last weekend in LA trying to find my friend while my phone rebooted TWICE. I was lost like an idiot. Couldn't map anything. You know what I did? I tethered my iPod Touch instead and got **** done on Safari.

If you look at my record on Anandtech forums, people would think I'm an Apple fanboi or something.

Then I bought the Nexus S which came in yesterday. I shut up. BUTTERY SMOOTH. Stock is close to smooth but with a custom kernel + custom rom, the phone is SMOOTH. Faster than my iPod Touch DEFINITELY. While my iPod Touch 4G @ 800mhz SMOKED my Motorola Milestone at 1.1ghz, the Nexus S @ 1ghz is smoking EVERYTHING.

The reason browsing isn't 100% smooth on Android is because nothing is hardware accelerated. In GB only some animations are in the UI, bu toverall the launcher is not. That's why a lot of people complain about a lagfest. I would know about a lagfest if you saw my Motorola Milestone with its 30fps cap. This is absolutely inexcusable for google to go so sloppy and not hardware accelerate everything. Blame fragmentation all you want but at least make it nice on the Nexus phones. Hell even a Motorola Xoom is choppy as fvck with its hardware acceleration. I think Google needs to optimize code still.

However, devs have come a LOGN WAY to speed things up on Android. So to say that Android is slow as **** compared to iOS is probably not that true. I think when you compare equivalent specced devices, Android is less efficient. My Moto Milestone's 256MB RAM is JUST NOT ENOUGH. However on an iPod Touch, 256mb of RAM is more than enough. Android devices need more horsepower to get things done. But given Android phones have dual core models with oodles of RAM like 1GB, we should be ok.
[Nexus S Android Development] ryanyo88:
Has anyone tried the Netflix app using this rom? Its not recognizing my phone as a Nexus S and therefore says it is incompatible.
[Nexus S Android Development] DumbUglyDragon:
Tweeted by Koush:
[Nexus S Android Development] ryanyo88:
Perfect. Thanks a lot man.
[Nexus S Android Development] eiabea:
wuhu we are back on topic xD
[Nexus S Android Development] tankmaster90:
anybody????
[Nexus S Android Development] bringonblink:
you talking about the crt tube effect? if so mine is still here
[Nexus S Android Development] benrees21:
Wow funny stuff lol. Anyway.....has anyone updated to netarchy .12?

Sent from my Nexus S running NSCollab, Cyanbread Theme and OC'd to 1.2ghz (Perfection) ;)
[Nexus S Android Development] bringonblink:
i have, been running it for 3 hours, so far so good.

1.2ghz, smart ass, -25mV across the board
[Nexus S Android Development] serrov91:
I've been running netarchy .12 since yesterday night. Didnt have any reboots for the last twelve hours. Everything's smoother than ever!
[Nexus S Android Development] sano614:
Will that build.prop work on any version of cm7 or just the latest ones?
[Nexus S Android Development] the1theycalldave:
mine wasnt there when i first flashed 0.22 but i messed with turning off and on the animation settings and it came back
[Nexus S Android Development] sk3201:
So, now i am on .12 and unfortunately calls wont go fine...not on calls a lot. Today was on a road trip back home....first call recieved.,..after a cuple of minutes call was canceled.. took a look at the screen .. total reboot..not really reliable ..,i am on radio kd1, kernel netarchy. 12, stock vcore....
[Nexus S Android Development] eramsey:
If you are having problems with losing your screen off effect try going into spare parts and turning window animations back to normal. You can leave the transition animations on fast.
[Nexus S Android Development] bringonblink:
did this happen with KB3 radio? I've heard that for some people KD1 is causing reboots, worth a shot
[Nexus S Android Development] sk3201:
Look some posts before...that forced me to try out kd1...and another thing which is worth to mention. While on the call i was on a highway with 160 km/h and there was bad loud short anoying reoccuring sound parts in the call (don't know how to describe it)
[Nexus S Android Development] knzo:
Best ROM I've tried for NS. :)
[Nexus S Android Development] 0x6d6b:
Hey frank707,

I noticed that the BusyBox version you are using, v1.17.1, has a few bugs.

iproute seems to be broken, it segfaults on some operations like ip addr / ip -6 addr and thus whole IPv6 connections don't work.

I pushed the 1.17.2 binary to my phone and the bug(s) seem to be fixed. iproute works and same goes for IPv6 connections.
[Nexus S Android Development] benrees21:
Frank, I keep getting reboots during phonecalls. Must be a bug somewhere?

Sent from my Nexus S running NSCollab, Cyanbread Theme and OC'd to 1.2ghz (Perfection) ;)
[Nexus S Android Development] mikechw:
Yes... it happens to me too.. Especially when I talk more than 5 mins...
[Nexus S Android Development] mariosergio2112:
The Random Reboots are extremely annoying... im gonna try another rom.
[Nexus S Android Development] cheech87:
Did you get them on previous versions of cm as well? Or just 7.0.3?
[Nexus S Android Development] mariosergio2112:
i am using nscollab since 1.0.9... but with the latests, the reboot became more intense...
[Nexus S Android Development] Ok_Kaleidoscope5109:
i was on hold for 30 min with samsung support and then my phone rebooted -.-
[Nexus S Android Development] Netconn:
This is the most amount of reboots I've had since I've owned the NS on .22
[Nexus S Android Development] sk3201:
As stated already: +1. And wanted to know all the people having the same issue that it seems to be kernel related. In netarchy thread one Guy posted he has reboots during phone calls with miui and netarchy, but not with the original kernel....tester over one week....flashed 1.3.1 cm7 compatible netarchy kernel today....lets see
[Nexus S Android Development] netarchy:
And if you look further you'll find other reports in various places in the forums of people that have reboots on other kernels, including stock.

Even more confusing, if it's the kernel, then why isn't *every* single person getting the exact same thing? There are a lot more factors to be considered. I can say one thing though, just about all the reports I've seen lately about reboots have been on roms that use code from CM in one way or another. Makes me wonder if it could be related.
[Nexus S Android Development] bringonblink:
Strange are you guys ocing and uving? I have not had a reboot since flashing this and latest netarchy kernel.

Using smart ass too. Give us more info about your setup s
[Nexus S Android Development] suhas_sm:
#justAsking

1. How are CM7 governors compared to SETCPU ? I had been using set cpu for sometime now.

2. I had a random reboot today which while rebooting didnot show boot animation :confused:Only Capacitive buttons were lit and the phone had home screen when i pressed lock/unlock screen button. Could that have been due to kernel ? any rogue app ? or OC glitch ?
[Nexus S Android Development] mikechw:
The reboots usually happens when someone calls me then they hang out the phone. I then take the phone off my faces and I see a black screen. The phone will reboot after around 15 seconds..

My phone is at stock speed, interactive governor
[Nexus S Android Development] benrees21:
Same here I'm on 1.2ghz Interactive. Could it be an Interactive bug?

Sent from my Nexus S running NSCollab, Cyanbread Theme and OC'd to 1.2ghz (Perfection) ;)
[Nexus S Android Development] eiabea:
I flashed Netarchy 1.3.1 today in the morning, and i works perfect with this ROM, amazing battery life with smartass

no reboots :)
[Nexus S Android Development] bringonblink:
I will say this i used to get that black screen on phoen call then reboot, but when i updated to NScollab i also updated netarchys kernel to .12 which included the smart ass governor, and i have not had any reboots...

Try using smartass and see if ya still get reboots
[Nexus S Android Development] suhas_sm:
What does smart ass governor do ?
[Nexus S Android Development] bringonblink:
it scales between frequencies depending on load, its a

Rewrite of interactive to be more efficient
[Nexus S Android Development] Ok_Kaleidoscope5109:
Well every governor scales between frequencies depending on load. I believe for the most part it's the same (in principle) as interactive, meaning it's very responsive. It uses some similar concepts like idle loop and stuff.

The main difference I thought (and from looking through some code.... but I just skimmed it so I may miss some stuff) is that there are defined states like screen off where the governor caps your speed when the screen is off. Thus you don't need another app like setcpu to do your power management while eating up more RAM and using some cpu cycles to do so...
[Nexus S Android Development] sk3201:
sorry, obviously you have more information's...:-)

updated today in the morning the kernel to 1.3.1. Recieved my first call.....end of call black screen...reboot...governor is interactive, no UV ov .....bln through bln control app enabled

Will switch the governor as a Guy stated in netarchy thread that this issue isn't reproduceable with smartass..
[Nexus S Android Development] benrees21:
Yea that's me lol. Yea smartass does not do that, I think interactive must scale down too much on a phonecall causing it to reboot

Sent from my Nexus S running NSCollab, Cyanbread Theme and OC'd to 1.2ghz (Perfection) ;)
[Nexus S Android Development] Ok_Kaleidoscope5109:
Certainly. I think this is why people are also citing radios as well since it relates to phone calls? I don't think anyone's flat out pointing fingers at you netarchy. We love your work! There's clearly a few things at play here:

1) Kernel

2) ROM? CM7 code is susceptible? Other poorly made ROMs?

3) Unstable OC/UV?

4) Radio

5) Some app running in the background

A lot of times people improperly attribute failures to recent updates despite not having done any comprehensive tests.
[Nexus S Android Development] Babydollll:
I'm running NSCollab 1.0.22 OC to 1.2 on demand governor and I have not experienced any reboots. I am also using Kb3 radio kernel version 1.3.0.11 { cfs }
[Nexus S Android Development] sk3201:
Guys, yes, I was just a bit quick :-)

If it the governer, it is the kernel, and people using just different settings..tried already a few things you mentioned...but enough...

Love all the work here
[Nexus S Android Development] :
what if that reboot things related with bln support? or everyone need to use that application to disable it or do we need to disable it?
[Nexus S Android Development] jkurl:
I just haf my first random reboot. It was during a phone call so I went back to kd3 radio and 1.3.0.12 kernel. Never had one random reboot on that kernel. Just flashed back to the old radio it seemed better anyway.
[Nexus S Android Development] mariosergio2112:
I dont think its the radio... im using kd3 and the reboots don't leave me... :(
[Nexus S Android Development] Ok_Kaleidoscope5109:
Have you tried KD1? I've seen reboots on KB3 but only twice, and that was after a long conversation. My short convos are just fine.
[Nexus S Android Development] leejeans:
u can use smartass governor without setcpu?how?
[Nexus S Android Development] suhas_sm:
Its under Settings > CM Settings > Performance > CPU Settings > Available Governors.
[Nexus S Android Development] Dukko:
No reboots, latest NSCollab, on demand governor.

Well, to be honest, ONE reboot last week. But it was strange, as I was using my phone 2 seconds before. When I lit the screen, there was the "insert PIN" screen. :confused:

No bootanimation, no black screen. It can't have rebooted in 2 seconds…
[Nexus S Android Development] mikechw:
No more reboot for 2 days after I changed to performance governor... stock freq. KD1 radio.
[Nexus S Android Development] mikechw:
With interactive governor, I get reboots very often..after calls..

I m on .22 nscollab.
[Nexus S Android Development] sk3201:
Netarchy is already looking into it.
[Nexus S Android Development] bringonblink:
Use smart ass
[Nexus S Android Development] captiv123:
Hi all,

Sorry if this is a newB question but I need some help please;

I tried installing and got the following;

Installing update...

Welcome to NSCollab

Wiping Cache

Extracting System : CM 7

Cleaning System

Finalizing Installation

Flashing Kernel: Netarchy CFS

assert failed: write_raw_image("/tmp/boot.img","boot")

E:Error in /sdcard/NSCollab-1.0.22.zip

(Status 7)

Installation aborted

Any idea how I can fix this ??

Thanks so much
[Nexus S Android Development] kemsiro:
did you check the md5 hash? try download the file again
[Nexus S Android Development] handzsolo:
Thanks it happens with other ROMS also though..

I download file on my mac, mount USB storage, load the downloaded ROM zip file onto my Nexus S, then follow instructions,,

Am I doing something wrong??
[Nexus S Android Development] jkurl:
I got reboots on smartass as well, however it was on kernel 1.3.1. I think there must have been a bug in it. Haven't tried 1.3.2 yet. I switched roms for now just to test some others.

Franks rom was very stable, smooth and very minimal reboots. Can't wait to see his next update.
[Nexus S Android Development] 0x6d6b:
What CWM version are you using?
[Nexus S Android Development] frank707:
ROM Download: Download NSCollab-1.0.23

[MD5 : e66d743078cc5415fb8ce34b2fc097d3 ]

[05/19] 1.0.23

[system] CyanogenMod 7 [7.0.3]

[kernel] Netarchy CFS [1.3.2] (stability has been great / 4 days no reboots)

[update] Books [1.3.4]

[update] Maps [5.4.0]

[update] Music [3.0]

[update] Rom Manager [4.2.1.0]

[fix] Netflix Compatibility
[Nexus S Android Development] frank707:
NSCollab development is going to be much more active again. I have been somewhat busy with work and life, but all is well now. So i will push updates out as soon as possible going forward, especially when it comes to fixes for existing bugs.
[Nexus S Android Development] sam_htc_touch:
Thats good news Frank!! Downloading 23 now, can I do it through ROM Manager or need to do it from here. Remember that there were some issues for a previous version in which ppl had advised against using ROM Manager!

Edit : Dont want to take chances as SwiftFTP really simplifies things, I download the ROm from here, transfer it wirelessly to my Nexus S and reboot it in recovery :)
[Nexus S Android Development] :
Good news.Welcome back :) how about nigthlies?

Also i don't now why but i cant see flash player voodo control on the market.
[Nexus S Android Development] frank707:
Will try out the latest nightly sometime tomorrow, and if it isn't to buggy i'll package a test release for nscollab users until cm 7.1 is finalized.
[Nexus S Android Development] frank707:
In my testing i have found that if you disable the option to wipe dalvik when prompted in rom manager, the install goes smoothly.
[Nexus S Android Development] sam_htc_touch:
Thanks! Would remember that for 24 ;) Have transferred the image through SwiftFTP and all is well for now :)
[Nexus S Android Development] :
anyone can confirm that? about what i wrote.I cant see flashplayer also voodo control in the market because voodo control has new version 1.0.6.1 and flashplayer reached 10.0.3

so if this buil has older version i cant install the newest ones.
[Nexus S Android Development] frank707:
Voodoo control is updated to the latest version. Flash player is not included in the rom. On my market it is available under top free apps.
[Nexus S Android Development] :
ok but i cant see.intresting i can try again.
[Nexus S Android Development] sam_htc_touch:
I have just updated to Flash 10.0.3 with Frank's version 23. However one strange thing which I observed - About Phone shows Android Version as 2.3.4, Radio is XXKD1.

Could this be due to the fact that I was tinkering around with getting GTalk Video Chat when 2.3.4 had come out? I don't think CM 7.3 is based on 2.3.4?
[Nexus S Android Development] frank707:
I believe that was updated because i pulled the fix for the build.prop for netflix from koush. But the rom is in fact 2.3.3.
[Nexus S Android Development] bringonblink:
Cheers dude
[Nexus S Android Development] :
doesnt mater so much but still can't see.i used applanet instead of market.
[Nexus S Android Development] bringonblink:
Err just updated to .23 and in the About settings, it is saying my andtroid version is 2.3.4? I was under the impression the .23 is still CM 7.0.3?

Can someone else check theirs please?

*Confused*

EDIT:

Also just realized but my email and books app are not showing up in the app drawer, the APKS are there in system\app... also if i try and reinstall them, it installs fine but the 'open' button is greyed out :S
[Nexus S Android Development] frank707:
The build.prop was set to 2.3.4 so it shows under system settings as a 2.3.4 rom. The rom is actually 2.3.3. It was a part of the Netflix fix.

As far as books, you may want to fix permissions and uninstall updates.

Sent from my Nexus S
[Nexus S Android Development] bringonblink:
I don't have any updates for google books installed :S And what about the mail.apk?

Thanks for the reply.

EDIT

unintalled updates from the appliocatiosbn but still not working. They are also showing as greyd out in applications menu for som reason

EDIT2

Figured it out, looks like gapps wasn't flashing properly, deleted email, car home and books, and reflashed .23 and it works now
[Nexus S Android Development] eiabea:
i just wanted to update, but CWM wrote that:

ClockworkMod Recovery v3.0.2.4

-- Installing: /sdcard/NSCollab-1.0.23.zip

Finding update package...

Installing update...

assert failed: !less_than_int(1297306095, getprop("ro.build.date.utc"))

E:Error in /sdcard/NSCollab-1.0.23.zip

(Status 7)

Installation aborted.

:(
[Nexus S Android Development] bringonblink:
Try redownloading .23

Also what option are you chooseing, you should be using the 'flash from zip' and not the 'update'
[Nexus S Android Development] eiabea:
just tried --> same error :confused:
[Nexus S Android Development] captiv123:
CWM V3.0.0.5

Is this the right version?? Or could this be causing me problems ??

It's the one I found in the "how to root on a mac thread"

I don't see a "flash from zip" option

Please let me know

Thanks again for all your help :)
[Nexus S Android Development] 0x6d6b:
Hm, try this version: http://xdaforums.com/showpost.php?p=12006879&postcount=1
[Nexus S Android Development] captiv123:
Yes sorry forgot, i had tried that but had the exact same error as mentioned initially :confused:
[Nexus S Android Development] lfmmoura:
I wish I'd seen this before... Coming from .21, the only thing that worked for me was to install directly from recovery, and with a full wipe. Anything other than that, including a full wipe from within rom manager, didn't seem to work.
[Nexus S Android Development] :
Update from 1.0.22 to 1.0.23 didn't work

Just ignore this post.
[Nexus S Android Development] mikechw:
My Bluetooth connection with my car will disconnect after some time, if I have tethering turned on. Also it makes my 3g connection very slow... It works if tendering and Bluetooth is not turned on at the same time.
[Nexus S Android Development] lfmmoura:
Frank has explained the 2.3.4 display, however I believe the radio is coming from somewhere else. I don't think NSCollab updates the radio, and mine still shows KB3.
[Nexus S Android Development] eiabea:
i can do what i want, but i always get this error -.-

any other ideas?