yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] sucker4pa1n:
Used it for a day...

I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.

When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.

With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC ;)

Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
[Droid Incredible Android Development] jermaine151:
2.15.00.09 radio literally KILLED my battery. I went back to 2.15.00.07 and battery life is great again. FYI.
[Droid Incredible Android Development] htc(hot-taco-cheese):
Everything is good for me with this kernel. No issues. Flashed it last night.
[Droid Incredible Android Development] Amin Sabet:
At the moment, I'm using Miui but wanted to note that this is the only kernel which allows Pre-9 Wifi tether to work on Miui (in my hands, King's #1 and #2 AOSP kernels gave me errors with Wifi Tether). Thanks for providing this kernel, Koush. Will give it a try with CM and see how that goes.
[Droid Incredible Android Development] grape ape:
I had a soft reboot last night with this new kernel while I was on facebook. 0 wifi used.

Radio 2.15.00.07
[Droid Incredible Android Development] hajabooja:
Not sure if it's the kernel or just the latest nightly, but I'm loosing my data connection quite often. Otherwise, its running great.
[Droid Incredible Android Development] clabbin:
My built in wifi tethering isn't working either....sad day. I was loving how fast my phone charged
[Droid Incredible Android Development] dnoyeb:
New version, number. 11 is online, testing now.
[Droid Incredible Android Development] mikeacela:
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.

Droid Incredible

S-off

.77 hboot

Latest radio

Ruby Rom
[Droid Incredible Android Development] dnoyeb:
Funny, I'm running the test2 on Ruby as well. Been rock stable for 4hours. Practically a record for my phone on Ruby. Hope it makes it through the night.
[Droid Incredible Android Development] tdiman:
Using the "test2" kernel.

Built in tethering works for me.

I'm running the 9/27 nightly.

No other issues so far.

P.S. I would love if internal memory was mounted properly in Windows.
[Droid Incredible Android Development] Ty07allstar:
Does anyone know if this new kernel is underclocked?
[Droid Incredible Android Development] ejkeebler:
Another question would be, does anyone know if test kernel #1 or #2 is the test kernel in rom manager?
[Droid Incredible Android Development] dnoyeb:
showing up as a 245-998mhz one with compcache optional... Not that I put much credence in quadrant scores, but I'm pulling over a 1300 on that. So plenty quick.
[Droid Incredible Android Development] Ty07allstar:
Also does anyone know if its undervolted?
[Droid Incredible Android Development] seanmcd72:
#2 is running at default clock.

So far looking good on test#2 for me (9.26 nightly). I just had a meeting in a location where the phone has frozen up nearly every time I was running CM 6.02 or any previous build and it worked fine. If I make it out to lunch, then back home later today without a freeze I think we may have a winner. Or at least I'll have a winner... :p
[Droid Incredible Android Development] coburnicus:
I grabbed the test kernel on friday night via the ROM manager, am I running the latest test, or is there a new one with the same name? In other words do I have to redo it to get the test #2 I am seeing comments about?
[Droid Incredible Android Development] ordovice:
I am running test2 and my only issue is with wifi cutting out and erroring out when running things like streaming media in the background, but no reboots. Tt just cuts out the wifi, and resumes relatively well upon turning the screen back on. For some reason the screen being off sets off a timer that cuts out the wifi after a while. I've tested this with both Pandora and Slacker. No cut outs when running over 1x CDMA (3G doesn't work in my office) except when my signal becomes nonexistant.
[Droid Incredible Android Development] tdavis42:
I haver been getting random 3g cut outs where I can't get any data but I still show a signal. I have to do a reboot to get it back. This only started happening in the past day or so once I flashed the 09252010 nightly build. SO I don't know if it has to do with that or what but I just thought I would throw it out there. I just flashed KingX's #2 kernel so I will see if it happens with it today on the same nightly build. Wifi was off if that would make a difference.
[Droid Incredible Android Development] Epicardium:
So I have installed Kernel 2.6.32.15-......#6

Can someone verify that this is the Test#2?
[Droid Incredible Android Development] dnoyeb:
it is not. test2 is #11

edit: on a side note, i'm coming up on 24 hours uptime with Ruby 1.1.1 with this kernel... normally on ruby I wouldn't last more than about 3-4 hours... so I am pretty sure that he's got himself a winner here...

oh, and one other thing... no more wifi caused skips while listening to BT media audio... only time I ever get a skip now is if I task the phone pretty hard while running BT audio.
[Droid Incredible Android Development] Epicardium:
Ok. Thanks. So, to answer the other guys question from a few entries back...I guess the version on RomManager is not Test#2. That's where I got mine.
[Droid Incredible Android Development] mike.d:
If you get to 48 hrs, consider doing a manual reboot and trying to duplicate the stability. I had a run on CM6 9/8 Nightly where the phone was up/stable for 11 days and I thought my problems were all gone. Restarted the phone and it was chaos again within an hour.
[Droid Incredible Android Development] dnoyeb:
eh, 24 hours was enough for me, already did a manual reboot for the hell of it.

i haven't seen anyone running test2 (aka #11) have any reboots yet.

also, in all reality until these two test kernels hit in the past few days, there hadn't been any changes in the kernel since cm6.02, so until now, there really was no reason to think that the rom would be any more stable.

Anyways, going to jump back over to the CM area soon as the nightly comes out tonight... Ruby was rock stable but is severely hacked up by me to get BT media working... (I had pulled in the BT stack from CM along with the music player and email app..)
[Droid Incredible Android Development] seanmcd72:
Kernel 11 (test2) also doing great for me! I'm just a few hours from 24hours uptime without a reboot or freeze. Been using wifi at work and at home like I normally do. I've never made it past 12 hours previously with CM 6.xx

EDIT - sometime around the 24 hour mark I had a random reboot (at last not a freeze) while charging. Definitely an improvement but still has something wrong.
[Droid Incredible Android Development] ordovice:
I just got the mobile data drop out running 9/27 with the test2 kernel. Was it introduced in the kernel or the nightly is the question.
[Droid Incredible Android Development] itch808:
Maybe it's just me, but where is everyone finding the test#2 (Kernal 11)? I don't see it under ROM manager. I only see "test kernel", is this the same thing?
[Droid Incredible Android Development] s197:
Download here: http://www.clockworkmod.com/download/htc/inc/inc-test2.zip

Let me qualify by saying that Ruby is very stable for me (reboots are very infrequent) but I'm currently at about 10hrs up time with this kernel. Everything seems stable, battery life is good. I can do a 24+ hr test over the weekend.

Anyway, reason I'm posting is I think the cell tower triangulation may not be working. When I open google maps, I don't get the arrow with the blue radius. GPS does lock on, but prior to locking, there's no arrow on the map. Anyone else notice this? Again this is running Ruby. Not a deal breaker because GPS still locks relatively quickly but figured I'd mention it.
[Droid Incredible Android Development] jermaine151:
3 reboots in 12 hours with the test kernel #2 on ShadowRom. :( I'm at work and letting it run a logcat to a file all day to see if I can catch what's causing it. The last 2 were after a 1/2 hour each (leaving home wireless access point).
[Droid Incredible Android Development] mcgoo99:
i'm on the 9/27 CM nightly with test2 and almost no apps. no reboots or freezes, and i'm nearly at 24 hours with 31% battery remaining. this is unheard of, until now my CM6's wouldn't last past 8 hours.

granted the phone has seen minimal use...maybe ten texts, one phone call, no wifi, and almost no BT, and a few minutes of web browser, but still...amazingly happy with battery life now. gonna turn on wifi and see how that goes

edit: just turned on wifi for the first time, got a hard lock up within two minutes. yikes. battery percentage dropped 15% almost immediately too. double yikes.
[Droid Incredible Android Development] seanmcd72:
Similar experience. I went about 24 hours without an issue, then plugged it into the HTC AC charger and at some point I got a reboot. I didn't realize it until a few hours later. It's definitely better, but something still lingers. Koush you are on the right track! Battery life was much better overall than previously as well. One thing I can't recall is if wifi was on or off when it rebooted. I turned it off at some point to run some speed tests. I think it had rebooted before that though.
[Droid Incredible Android Development] ordovice:
I'm now testing with the 9/24 nightly as I didn't have the mobile data cutout I've gotten with 9/27 and 9/28
[Droid Incredible Android Development] ardax:
No help here. Did a full wipe, installed CM 6.0.2, 9/26 gapps, and test #2 last night. On my way to work this morning I noticed my phone wouldn't wake up. After 15 min or so I got a chance to do a battery pull. Turned off WiFi and restored my Virtuous nandroid.

Unfortunately, I need my phone. I could deal with the occasional FCs, but I can't run anything that randomly reboots and hard locks.
[Droid Incredible Android Development] tdiman:
6.1.0 will be the first 'everyday use' stable CM release for the incredible.

6.0.2 was never really stable. Unfortunately, because it is labeled as such, many people are using it thinking that the nightlies are worse, which they are not.

Ergo, try the 9/28 nightly with the test 2 kernel, or wait until 6.1, which I can't imagine is very far off.
[Droid Incredible Android Development] tdiman:
My guess is that it is because you are using a kernel being developed for CyanogenMod nightlies with a custom ROM that Koush and co. have nothing to do with based off an old snapshot of the CM source.
[Droid Incredible Android Development] jermaine151:
What about the 5 or 6 posts, following mine, that are all getting reboots, lock ups and data cut outs, with Koush and Co.'s ROM? It's an AOSP kernel and should work with any AOSP rom. That's how that works.
[Droid Incredible Android Development] dnoyeb:
No issues here on cm nightly. One side note, maybe radio version has something to do with stability now as well.
[Droid Incredible Android Development] s197:
So no one else is experiencing the issue with the cell tower triangulation not working?
[Droid Incredible Android Development] ardax:
So I noticed. :)

Much as I love testing out new stuff, I think I'll wait until 6.1.0 goes stable.
[Droid Incredible Android Development] dnoyeb:
all i'm getting here in the office is a dot... so maybe... but i'm not moving either, so maybe it doesn't know which way i'm going...

course, it locked right on to my location without having GPS satellites though (in the middle of the building and it says searching for GPS satellites..) so perhaps that means it had to of used triangulation..

hmm..

oh, and sadly after 18 hours I did have a reboot on CM 9/28 with test2...

edit: bah, only lasted 4 hours this time while at the office... ohwell, going to jump back to my hacked up version of Ruby to see if it is stable or if that was just a fluke...
[Droid Incredible Android Development] jermaine151:
Hey dnoyeb, I don't do BT streaming, yet, so I don't know how well MIUI does on that but if Ruby reboots on you, give MIUI v0.2 a try. I'm running it now, with Launcher Pro and the stock King kernel and so far it's the most stable AOSP I've tried. I'm at 12 hours (so not completely convinced), but CM, Ruby, Shadow and all the others would've rebooted over night and then again when I left my wireless AP at home to come to work. None of that with this one. I'll keep ya' updated.
[Droid Incredible Android Development] larsrya8:
In contrast, on CM 6.0.2 with the stock kernel and I'm currently at 62 hours uptime (since I nandroided back from Virtuous). The WiFi has been on at least half of that time, walking in and out of range from the various AP's. No BT though.

Wish we could figure out why stability varies so widely. :(
[Droid Incredible Android Development] dnoyeb:
heck on stock kernel #4 that ships with the nightlies, I've been cruising along just fine on this latest android 2.2.1 version that hit yesterday...

(knock on wood)...

if I get any reboots i'm going to push the #11 to it, but so far its rocking strong.
[Droid Incredible Android Development] Ty07allstar:
Are you using wifi at all? I was running kings #1 but for some reason wifi kept making me reboot every couple of hours. Just flashed 9/29 nightly and will be staying with the stock kernel. Hopefully this solves my issue.
[Droid Incredible Android Development] Mr. Spontaneous:
I was having issues, and I think it's because the ROM isn't using AGPS correctly. I downloaded GPS Status, though, and by using that to download the AGPS data my lock times have gone from 1 minute to 10 seconds.

I don't know if that was the problem you were having, but I figured I'd put it out there.

Are you using Wi-Fi?
[Droid Incredible Android Development] tdavis42:
Did 2.2.1 already get integrated into Cyanogen? I have the 28th I think and it is still saying FRF83.
[Droid Incredible Android Development] GMK83:
FR83 is newer version. FR91 was the old.
[Droid Incredible Android Development] tdavis42:
If I'm not mistaken FRF is old and FRG3? is the new 2.2.1.
[Droid Incredible Android Development] Panda Fuzz:
Yes, 8/3 nightly has 2.2.1. FRF and FRG are hex btw.
[Droid Incredible Android Development] marcmarshall:
So I'm running my first custom ROM about a week now- Virtuous with adrenalyn custom kernel. Want to try another. Read this thread and I'm a little confused. Which version of CM should I load with this test kernel?
[Droid Incredible Android Development] Panda Fuzz:
6.0.2 or the nightly
[Droid Incredible Android Development] marcmarshall:
Thanks. I'll give it a try.
[Droid Incredible Android Development] marcmarshall:
Panda Fuzz:

Actually I saw this posted on this thread so I'm not sure what you are saying is completely correct. They do go on to say the nightly are more stable.

"6.0.2 was never really stable."

"So I noticed."
[Droid Incredible Android Development] dnoyeb:
The latest nightlies (anything past oct1st) have a new RIL file in them (radio interface layer) which fixes the reboots that many of us were having. So yes, the nightlies are a great deal more stable in that way.

the only issue is the camcorder doesn't work properly. lots of force closes.
[Droid Incredible Android Development] marcmarshall:
MMS- resolved

I like the camcorder. I'm running Virtuous with custom adrenalyne and just noticed I can't send MMS.

resolved- problem was in handcent
[Droid Incredible Android Development] marcmarshall:
Anyone have any opinion as to which kernel runs best (particularly for battery life) with Virtuous Rom- stock, adrenalyn custom, test?
[Droid Incredible Android Development] larsrya8:
This kernel is for AOSP roms, not Sense-based.

For Virtuous, I would recommend the stock kernel (to keep things simple). The biggest power draws are the display and radios; you won't notice much by switching kernels (unless it's a badly written kernel, which neither are).
[Droid Incredible Android Development] jesssiii:
Does that mean the stock radio uses LESS or MORE power than those other 2 radios in the INC Official radio thread? The rumor was the 19 radio saved battery life.
[Vibrant Q&A, Help & Troubleshooting] ibuddha:
my vibrant is stuck n the black screen following the Galaxy S logo it won't do anything just sits there. I've tried a millions things but I can't get the phone into DL mode to used Odin but adb won't recognize it whatsoever. please help me.

i'm hardware locked so i can't even make the phone boot into download mode whatsoever and adb isn't recognizing my vibrant WTF. please!! some on help!!!
[Vibrant Q&A, Help & Troubleshooting] watcher64:
See my post in this thread ... http://xdaforums.com/showthread.php?t=791978

It is the second post in the thread, should get you to download mode ..
[Desire Q&A, Help & Troubleshooting] DearTanker:
I use a Official rom only with ROOT.i think this is not enough . i was thinking:can i get A2SD+ with flash an *.zip? can somebody help me? Thank you!! and sorry for my english.:(
[Desire Q&A, Help & Troubleshooting] K900:
Darktremor A2SD

Sent from my HDfied HTC Desire
[Desire Q&A, Help & Troubleshooting] Pyr0x64:
if it's an official rom, you will have to edit the boot.img/ramdisk to enable support

instructions here:

http://xdaforums.com/showpost.php?p=7021331&postcount=4
[Desire Q&A, Help & Troubleshooting] RevoWution:
Or you could just flash one of the many custom ROMs available in the "Android Development" section. Almost all of them will either have A2SD or A2SD+ :)

Custom ROMs are almost always faster and more feature-rich than the stock 2.2 ROM.
[Desire Q&A, Help & Troubleshooting] mayurh:
custom roms are faster yes lots of extra features but "some" give fc's and stuff and i guess not as stable as the stock rom?
[Desire Q&A, Help & Troubleshooting] leoking3:
I would also like to know if this is possible. I am not interested in custom roms. I just want A2SD+. So , is anyone sure if this can be done?

Edit: yeah, only working in Linux...so...not feasable for me.
[Droid X General] amoeller:
I was looking at the OTA ZIP file from VZW and noticed some BIN and IMG files. I'm guessing that it bootloader and baseband images. Is there a way that I can swap out those files with a nicer bootloader? Basicly what I want is stock OTA 2.2 with 29.01 or 30.01 bootloader but I want the new baseband with the update. Can I do this or does it just fail because of signatures, checksums, or some other crap I can't think of?

Thanks
[Nexus One General] yanivt:
Hey all.

Been having problems with a Nexus One that crashes at seemingly random times.

I have been unable to pin it on anything, and am asking your help.

It appears to be independent of the Rom installed, whether there is an SD card present, or whether its connected to a USB cable or phone charger.

Any help would be greatly appreciated.

Phone Info:

Nexus One (AT&T model)

Radio: 4.06.00.12_7

Current Rom: Enomther's TheOfficial Nexus1 - v2.12.2

Provider: Rogers (BC, Canada)

Logcat output attached as screen capture image.
[Nexus One General] OzCDN:
This has been reported by a few users. I sent mine in for repair and got it back not repaired - they couldn't replicate the problem.

My case has been escalated which means a HTC guy called and asked me a few questions and then told me to wait for an email (a few days ago).

I believe my problem started when I seriously overheated it ... driving with navigation on, 3g downloading maps and traffic data, car charger plugged in all on a very hot day on a very hot dashboard. This was the first reboot and they got more and more often after that. Now I can't run anything for more than 5 minutes if 3G or wireless is on (in 'Airplane' mode I can run for quite a while without a reboot).
[Nexus One General] ocbaud:
mine was doing the same thing.

getting progressively worse until the phone was basically unusable earlier this week.

I was running CM6 at first when it started happening.

installed the newest nightly and it worked better for a bit then got even worse.

uninstalled the stand alone version of gmail from the market and it worked for a couple hours and then kept rebooting on me.

finally i did a factory data/cache wipe and installed a rooted stock rom and things have been working PERFECT for over half a week.
[Nexus One General] wsrider:
I had the same issue. first reboot happen when i had nav running plunged in then after a few months utube , browser etc would restart my phone. it didn't matter which rom i used or stock. I sent it in and they fixed it. i had issues with htc but it got fixed.
[Nexus One General] productofusa:
Yup, same here, strange thing is it isn't a complete reboot. Hard to explain but what happens is i'll touch the phone and then it will immediatly go to the CM6 boot logo, then immediatly to the lock screen, (which I have disabled) then to my normal desktop. Total time elapsed maybe 5/6 seconds, wierd.

A normal reboot usually takes about say a minute or so. just started happening 3/4 days ago, and happens maybe twice a day at most, some days not at all. Probably wait until Cyanogen includes 2.2.1 into 6.0.0 stable then reflash.
[Nexus One General] goku31640:
Ive been having the same problem for about a week now, but I'm still using stock, not rooted. Its weird, because its a really fast reboot. It goes to the Booting X, for about 6 seconds, then it boot up just fine. I cant understand it.
[Nexus One General] tchamander:
this really sucks

I am keeping my ATT nexus one around for gingerbread but these random reboots are really killing me....I use the phone for five minutes and it just reboots by itself....The phone runs really well for those five minutes...Ive done five factory resets but it is still just doing these phantom reboots.... Anybody find out anything more about this...or know a fix....the phone is not rooted and it is clean stock froyo...so please help or keep talking about it so htc will address this issue lol which i doubt since this phone is starting to become ancient....(cant wait till nexus S) =P
[Nexus One General] yanivt:
With regards to the original problem posted, I believe I've managed to diagnose it correctly.

The problem lies with faulty heat distribution. The phone would crash and reboot more often in times of great stress:

charging the phone (heats up the battery)

running many applications at once (heavy system load)

navigation (heavy dataand gps traffic, image processing)

This coupled with the fact that changing the OS did nothing to remedy the problem solidified the notion that the problem was hardware based.

Given this, I contacted HTC Nexus One support and had the phone repaired.

Note: HTC will honor the warranty and fix hardware issues for an unlocked Nexus One. With software issues, you're on your own (for obvious reasons).
[Nexus One General] deprecate:
This is exactly what my phone is off to warranty for. I experienced this with every rom tried. I wipe my phone completely and put stock froyo on only to see the exact same behaviour...so at least I'm not crazy :)

The tech told me it was a hardware problem so that is a bit of a mind ease.
[Nexus One General] pilgrim011:
It seems Nexus One and Desire are really similar: HTC Desire rebooting on its own.

P.S. It's a problem with faulty motherboard, if you're within warranty, it should be replaced.;)