yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] 651stp:
i dunno why i always get random reboots when i use pandora, i can be listening to music for 10-20 mins and it'll just freeze(music sounds like its skipping on a cd) then reboots itself. This has happened to me with these kernels for quite some time. :( runnin CM with 1.2 honity. my phone runs fine on 1.3 with netarchys kernel all day/night. weird.
[Nexus S Android Development] lordsandwich:
Can't get BLN to work with MoDaCo R14, even after a fresh wipe and install. BLN Control loads but nothing happens with the test notifications. Is there a log somewhere to see what's wrong?
[Nexus S Android Development] FaithCry:
try sending a text to yourself with the BLN on and the quickly shut off your screen, i tried the same thing, the test didnt work, but when i did this, it confirmed that the bln worked.
[Nexus S Android Development] onei0077:
That sounds like me too. I run poweramp instead. I tried not OC and still had a re boot after about 15 minutes of music. Cm7 26 h12bin v1

Sent from my Google.
[Nexus S Android Development] morfic:
The app does not give you any errors after starting it, yet after enabling BLN in the app, you can't even get the test to work?

Which nexus s is this?

Sent from my Nexus S
[Nexus S Android Development] morfic:
get the v2 file in the op.

V1's bln does not fully work.

The draw of the media apps could be the culprit, needing more power there.

I'll keep this in mind when working on new trinity

Sent from my Nexus S
[Nexus S Android Development] simms22:
reboot then try it.
[Nexus S Android Development] Worsty:
Is it just me or are both links for the cm7 kernel down?
[Nexus S Android Development] simms22:
it looks like dropbox is down right now. my dropbox app and online account wont download anything either. it should be fixed shortly.
[Nexus S Android Development] lordsandwich:
I'm on a Tmo US Nexus S. Not sure what did it, but after a series of reboots, wipes and nandroid restores, it seems to be working now. Thanks!
[Nexus S Android Development] drew_grant:
Stupid question but what's the difference between H12 and H14? One overclocks to 1.2GHz and the other clocks to 1.4?
[Nexus S Android Development] simms22:
correct :)
[Nexus S Android Development] irishrally:
In h12v2 when the screen is off if I hit a soft key the leds light up.
[Nexus S Android Development] morfic:
Thanks, I'll pass it on. Only good we have no reason to touch it if we don't use it.

I confirm this behavior, no false positives were caused by this on my pocketed Nexus S.

But i actually didn't get to pass this on before they *DID* turn off, we call this the "someone touched me" notification event.
[Nexus S Android Development] simms22:
i cant reproduce it. i tried to reproduce it, i want to reproduce it, but it just isnt happening. can we call it the *i want to be touched* notification event :eek:
[Nexus S Android Development] G1_Lucky:
Has anybody had their led buttons not respond after they unlock the device but if you lock and unlock again they come back to normal. Or is it just me? :)
[Nexus S Android Development] irishrally:
It was happening every time I tried, then I used cachemate and it stopped until I received a new notification using BLN and it started happening again.

Then I tried clearing cache again and it didn't go away. There seems to be some form of relationship with clearing cache but not sure exactly what it is ... or maybe this one instance was a coincidence.
[Nexus S Android Development] terryhau:
Yeah i'm getting that, on BLN V1 and V2.
[Nexus S Android Development] Rafael Cadina:
Same here :(
[Nexus S Android Development] irishrally:
Yes, at some point I had this happen too.

I found patterns in the screen off LED light up I mentioned above. If the LEDs are lighting up when the screen is off when I touch them I can get it to stop by rebooting. I then sent myself a text via GV and after turning the screen on to clear the notification, if I turn the screen off the LEDs will light up again when the soft button are touched. So, after the first time BLN is used, when the screen is off the LEDs will light up when touched (on my phone).

One time it was crazy and all but the menu button lit up, then after a few seconds it turned on as well. This points to us possibly being able to light up soft button LEDs individually for more informed notifications.

morfic: if you don't want us talking about BLN in here let us know, please.
[Nexus S Android Development] simms22:
i just reproduced it! i sent myself an email, got the notification, lights started blinking. i turned on the screen, then turned it off. still blinking. i turned the screen back on, unlocked, pulled down the notification bar, DID NOT clear or open the notification, then turned the screen back off. no blinking. so i touched one of the soft buttons, and they lit up. clearing the notification fixed the issue.
[Nexus S Android Development] irishrally:
I'm not sure we are talking about the same "issue". I'm specifically talking about the LEDs lighting up when touched when the screen is off and there are no notifications.
[Nexus S Android Development] simms22:
oh.. then i found a different one :eek:

maybe there are notifications, but just hidden.
[Nexus S Android Development] morfic:
I was going to point that out too.

But decided to cut him some slack due to his head making a dent in some beam of the metal gate at his work. I'm glad he can tie his shoes right now. Be nice too. :)

Sent from my Nexus S
[Nexus S Android Development] simms22:
aww, you do care :D
[Nexus S Android Development] irishrally:
Another little thing that isn't an issue but different is that the boot animation freezes for a second or two at the beginning of honeycomb (HC) animation. This didn't happen with other kernels when I loaded my saved version of the HC animation. I tried loading up the version of the HC animation that I had saved and the same thing happened.
[Nexus S Android Development] drew_grant:
I have that same issue. I'm using the H12 kernel and the buttons don't blink even when I have them set to blink. Hopefully this can be worked out in future versions, but this is what I've been waiting for for the longest time.
[Nexus S Android Development] eiabea:
i hope this helps
[Nexus S Android Development] ph1r:
See attached screenshot:
[Nexus S Android Development] Serious_Beans:
CM 7 nightly #28
[Nexus S Android Development] dario3040:
Morfic have you also experienced rebooting and freezing?

Just curious.

Honity14-233 has been most stable btw.
[Nexus S Android Development] eiabea:
looks like there are online a few i9023 users, because when europe sleeps the thread is very busy, but when i hit F5 the whole day at work, nothing happens :D
[Nexus S Android Development] vivmar:
I have same situation..any idea?
[Nexus S Android Development] eiabea:
as far as i know, the i9023 does not use the same drivers for BLN :(

but the devs looking into it ;)
[Nexus S Android Development] slimjimwoods:
I'm getting the 'someone touched me' notification sometimes, sometimes no keys when unlocked, and sometimes BLN working perfectly. I've bought BLN pro but gone back to an older kernel for now.
[Nexus S Android Development] th3s7riker:
same for me ;)
[Nexus S Android Development] Luxferro:
I was having issues when I would unlock it after getting a notification, none of the hard buttons were lit, and they didnt function till i locked and unlocked again. It did work okay for a while though before that started to happen.

I've since decided I don't need a LED or BLN. I made a tasker repeat notification sound loop instead. It will do a sound notification every 10 seconds for 20 minutes, then stop. or stop when the screen is unlocked/on.
[Nexus S Android Development] jumaaneface:
ahhh so that was the source of the capacitive buttons being non-functional?

is this happening for everyone or just a few? I have only seen it while using CM7 and not with MIUI
[Nexus S Android Development] drew_grant:
Finally the keys started blinking but I am constantly getting reboots.
[Nexus S Android Development] jlevy73:
h12 blnV2 not stable for me. Two issues:

1. Phone is rebooting quite a bit

2. Unresponsive capacitative keys upon waking the device after bln.

Love,

Murph :eek:
[Nexus S Android Development] terodeg:
i'm on cyangenmod nightly 28 of 21/03/2011 and this kernel dont boot
[Nexus S Android Development] stavros86:
also problems here sometimes buttons are unresponsive, capacitive buttons light when touched with screen off and some odd problem with the calls i couldnt make a call and i rebooted myphone but even then sometimes i can call a number and sometimes i cant with full signal(modaco V2 bln)
[Nexus S Android Development] drew_grant:
Flashed both the 12 and 14 and I have the same issues on both. I don't think my phone likes any of the Honity kernels because they all seem to do the same things.
[Nexus S Android Development] dnts:
I have issues with media playback.. the phone just reboots in the middle of a song being played. I connected the phone to dump logcat during this reboot and I see nothing that can be of concern.. Reboots just happen at different times. Can't link that to anything.

I think it only happens with the screen off, though.

I was very excited about BLN (and got the app in a heartbeat) but given this lack of playback capabilities.. I will have to get rid of it for now :-(

Edit: Screen off problem confirmed. Let it play for 10 minutes pluged with screen on. Then switched screen off (still plugged), counted to 5... and boom. Reboot.

Arrrggggg.....
[Nexus S Android Development] alexis_p3300:
Still dead touch buttons after receive sms on modaco kernel v2 btw i dont use bln i just want the power and voodoo goods! !
[Nexus S Android Development] 651stp:
I mentioned this earlier too. I tend to get a lot of random reboots when listening to music wether its through pandora or through stock music player. Also had a random reboot while my phone was ringing today when i was about to pick it up, it just went to splash screen. My main concern is the music playback. This is my main source of music all day and i listen to music 8+ hours a day. :( hopefully we find a fix.
[Nexus S Android Development] Rafael Cadina:
Same here sadly.

Won't boot ever
[Nexus S Android Development] dnts:
Tried on both BT headset and built in speaker. When the screen is on - all is well. Once it is shut off... the count down starts. When it was the internal speaker, I could hear the last few milliseconds of buffered audio being played over an over again for 10 seconds until the splash screen came on at which time the noise stopped. This leads me to believe that the kernel somehow halts until the built in watchdog timeout resets the system. Hope this info is helpfull for the developers..

Another thing that might provide a clue - maybe it's due to SD card (faux SD that is) access? music playback has intensive storage access. I wonder if it's possible to play a long track from other storage to check this out.
[Nexus S Android Development] Vandam500:
Yep I have since this numerous times since I flashed Honity 12 BLNv1. Not sure if it does the same on V2.
[Nexus S Android Development] formuk:
My phone has also gone ape **** after installing this kernel (CM7/vsv6BLN). I have all the issues reported above.

Also, when the time screen dims before timing out, the dim part is bright neon green... once tapped, normal colors return.

I can't even boot into clockwork... for some reason it just sticks at the Google sign but never goes into recovery for me to flash another kernel. STUCK! :(

Any help would be much appreciated.
[Nexus S Android Development] morfic:
I will build two test kernels to address the race condition where there are lights when they shouldn't be, keys non responsive until lock/unlock cycle. All of them.

Those who report issues will be asked to thoroughly test either kernel.

You will need to specify:

- Phone model.

-Rom and release (i can't accept reports if your cm7 is a kang, too many sources for those)

- Filename of kernel flashed. (Instead of "this kernel")

Reports of "non booting" followed by reports of issues only a.running phone would be experiencing will be ignored. (This will include any other contradictory reports)

Those with proper reports deserve I spend my limited time on utilizing their reports and not wild goose chases.

The screen captures provided seem to indicate i9023 do not use the same driver or do not use it in the same way.

We will have to see how bad those news are.

BLN is a modification of the touchkey driver, since i9023 work otherwise normally with this kernel, I'll see which driver it is. Correct me if this kernel never worked correct on i9023 before.

Everyone still on v1 bln kernels, upgrade immediately, a lot of the "buttons not working" issues are fixed in there. Treat this like your PC's bios, everything working? Cool, wait till you see a worthwhile feature. You have issues, always test the latest version before reporting anything. If problem persists, add the info that upgrading did not solve the problem, having this info is good to have.

I will try to get those kernels out tonight, work has started again, so my replies will come far less often than the past 4-5 days, sorry :/

Thanks for the screen captures,

Daniel

Sent from my Nexus S
[Nexus S Android Development] morfic:
Pull battery and replace it.

Press and hold Vol Up + Power

Once in fastboot menu, choose recovery and press power button.

What happens next?

Sent from my Nexus S
[Nexus S Android Development] Rafael Cadina:
Morfic, thanks for that.

I couldn't flash honity12 bln v2 (latest) on my device. It gets stuck on the boot animation then an infinite bootloop starts.

Here i run cm7 nightly #29, radio kb3, cwm recovery 3.0.0.19 on a 2.3.3 android phone. It is an american phone (samoled screen). Do you need any additional info?
[Nexus S Android Development] morfic:
Correct me if i recall this wrong, you never booted a Honity, not even those before BLN was added, correct?

We should address your issue with OC Kernels later, i believe your phone may be very sensitive to the voltages and need LESS than currently used.

I simplified the code in a way i should be able to go to another set of voltages quickly, but want to address BLN first.

The "s10" test kernel should work for you, plain as they come + bln added only.

The "h14" should be of the "locks me up at boot time" flavor for *YOUR* phone (just noting so onlookers don't think i release kernels planning for them not to work :) )
[Nexus S Android Development] morfic:
The following two test kernels should be flashed "h14 before s10 after a new nightly was flashed" (don't worry modacoers, what will be found should benefit you the same)

Reason for this is h14 no longer includes the liblights file, after a nightly, you have the stock version back, painless and reliably.

s10, the 1.0 ghz stock/samsung kernel with only BLN patched in should be flashed 2nd as it reintroduces the required liblights file for BLN.

Test for those issues you experienced on both kernels for the same amount of time. Report back which problems you still experience with which kernel/both/none.

Thanks,

Daniel

If you reverse the order, you possibly spoil what you find.

http://goo.gl/2j6wD h14 cm7 with all the goods, minus bln.

http://goo.gl/Wewqh s10, stock as they come with ONLY bln added
[Nexus S Android Development] morfic:
duplicate in need of deletion, sorry for pulling a simms22
[Nexus S Android Development] dnts:
OK. Flashed Honity12 - cm7 - w/ VSV6 + BLN V2

My setup: i9020T (SAMOLED, US version). Currently with CM Nightly 29.

Played back MP3 on the stock player, internal speaker. Ran for ~7 minutes and then the audio got stuck (repeating the 100ms in the buffer for like 10 seconds) and rebooted. Same as with the previous version.

Will now try the S10 with BLN and see what happens.
[Nexus S Android Development] docsamsom:
Can this be used for Axura? I tried the modaco h14, but got stuck in an boot loop. I have tried your kernels before and my phone was relatively stable even at 1.6 GHz.
[Nexus S Android Development] dario3040:
Well. I can report that the honity 14 blind v2 simplified code v3 works fine. I haven't had any problems yet.
[Nexus S Android Development] ph1r:
tested both h14 without bln and s10 with bln, both running stable and good.

but i never had problems referring to stability and/or audio problems, like others!

btw: running cm#29

just bln won't work on my i9023. but i'm sure you devs can work out everything ,)

if you need someone for testing, here i am! :D
[Nexus S Android Development] eiabea:
just reseted my phone to completely stock, because of warranty (have some pixel errors :mad: )

and i was wondering that in the bootloader the "phone name" is "herring"

isn't the nexus is called "crespo" ??

checked the phone from my boss, his phone is also called "herring"

HW Rev 52

Bootloader: i9020

Baseband: i9020

Provider: T-Mobile Austria

now i am really confused!! cause i bought my phone before 2 weeks

HW Rev 51

Bootloader: i9023

Baseband: i9023

Provider: A1 (mobilkom)

so my hardware is older, but my baseband and bootloader newer???
[Nexus S Android Development] tomqman:
Working great here thanks

Sent from my Nexus S
[Nexus S Android Development] morfic:
Welcome.

Sent from my Nexus S
[Nexus S Android Development] jonjon68:
Should keep it. Anytime you can get away from Team Whiskey imagery and distance you're MODs from that crew, it's a good thing. Good job. Keep it up.
[Nexus S Android Development] morfic:
Interesting comment. If that relates in anyway to my other bootlogos, all my brain children.

Just couldn't resist honity, it was just too awesome.

I was so happy with how trinity14 had turned out, I wanted it to stick out.

Now it does. :)

Sent from my Nexus S
[Nexus S Android Development] morfic:
Obviously glad you like it :)

If I muster the time I think vibrant needs a DoW -> HoneyDoW move.

Sent from my Nexus S
[Nexus S Android Development] Jrbourque:
Amazing kernel so far, couldn't oc before this one, will see battery more so tomorrow for the true test ....and same as everyone bln would push this beyond amazing ...thank you for your work
[Nexus S Android Development] di2356:
whoa. first kernel to work at 1.4ghz on my nexy. 1.5 pleeease?
[Nexus S Android Development] morfic:
BLN will come.

Aside, lest the 2.3.3 dust settle....

Sent from my Nexus S
[Nexus S Android Development] 651stp:
my phone freezes everytime i play pandora for 5 minutes. could be just my phone. either way good job morfic :D
[Nexus S Android Development] onei0077:
You are the man.
[Nexus S Android Development] Jrbourque:
Anyone else experiencing the phone getting hot?
[Nexus S Android Development] CB620:
Your overclocking that's normal
[Nexus S Android Development] Jrbourque:
My g2 never heated up this much but my nexus one did get kind of hot now that I think of it
[Nexus S Android Development] kenvan19:
How much of an overclock were you running on your G2? Out of the box the G2 is actually underclocked from 1GHz to 800MHz so only once you start going over that 1GHz are you actually adding extra load to the processor.

Also, I watched the video that simms posted of this boot animation and I wasn't that impressed. Curiosity finally got the best of me so I flashed the kernel and holy f***, the video just doesn't do it justice. Its so cool!
[Nexus S Android Development] Jrbourque:
I was clocked at 1.5 on g2 .. Im not to crazy concerned just checking to make sure others were running with a little heat and good
[Nexus S Android Development] simms22:
thats what i was telling people, the video just didnt do it any justice. its so much more awesome in real life. maybe if i had an hd video camera...
[Nexus S Android Development] simms22:
where you plugged in? or were you watching a flash movie or using pandora? if yes to any of these, then its normal.
[Nexus S Android Development] Jrbourque:
Mostly navigating through forums, Twitter etc but actually its my screen I feel getting hot not the back but nothing crazy hot

Edit : not plugged in when I had it clocked at 1ghz while charging

Edit 2: but don't get me wrong my nexus hasn't run better than with this kernel
[Nexus S Android Development] Worsty:
sweet kernel...finally 1.4Ghz stable... could only attain 1.3Ghz for the rest.

Mine got hot if i'm plug in to charge the phone but i've set a profile on setcpu where it goes to 200/200 when screen is off so it cools of pretty quickly.
[Nexus S Android Development] simms22:
Hanity14 is working great with the latest cm7 kang, which is 2.3.3 based.
[Nexus S Android Development] formuk:
That didn't work either.

But weirdly enough this procedure did:

Opened ROM Manager, selected install ROM from SD, selected new kernel (just went back to netarchy til things get sorted out in this one or I may just have a very voltage sensitive phone) and it booted into clockwork recovery and flashed it. Strange that it wouldn't boot into clockwork normally with the Vol Up + Power combo.
[Nexus S Android Development] Rafael Cadina:
Here i have alredy tried to flash honity previous versions (h12 and h14 with no bln) but it failed.

With netarchy 1.3.0 i can oc to 1.2 stably. But beyond that point i start to have problems. So i thought honity 12 would fit my phone cause i had alredy oc before to 1.2 succesfully.

Btw, i 'll try the s10 version. Where can i find it bro?
[Nexus S Android Development] TKEMerph:
Hey I'm coming from a Vibrant and I use to flash kernels through SNS Kernel Flasher... I see alot of people flashing through ClockworkRecovery, Should I be fine with just flashing through CWR or should I go into Kernel Flasher and make a backup and flash there...?

ty!
[Nexus S Android Development] formuk:
I'd be safe and flash clockwork. Minimize chances of ur NS going kaput.
[Nexus S Android Development] TKEMerph:
I just flashed it, everything seems fine. Except my BLN buttons at the bottom disappear (go dark, cant use) - I'm sure some others have ran into this problem?
[Nexus S Android Development] simms22:
which one did you flash? filename please :)
[Nexus S Android Development] simms22:
btw, this isnt a vibrant. the nexus s is made to flash things, repeatedly. use the recovery to flash roms, kernels, themes, etc.. its much easier that way :D
[Nexus S Android Development] danon.brown:
will this work on the Evo? I've been looking for this since the Evo was released
[Nexus S Android Development] simms22:
i dont know. it needs to be patched for the EVO and put into a custom kernel. but i think it was written for samsung devices.
[Nexus S Android Development] danon.brown:
Thanks i'll try it later after work
[Nexus S Android Development] morfic:
You can pause on testing until I can build BLN v3 patched kernel tonight, for testing I will keep it in the "very stock" kernel.

My H12 asks more from gpu and memory than stock kernels like netarchy.

I already have the menu config option for "defanged" kernel.

I will make sure they are available as soon as the work on bln is complete.

Sent from my Nexus S
[Nexus S Android Development] obyn:
hm. i flashed Honity12 - cm7 - w/ VSV6 + BLN V2.

is there something i need to do to activate bln?

i searched the thread but found no similar questions so i assume it's automatic?

i just hear the notification sound but screen stays black.

i have a us nexus s (9020) with kb3 radio running miui 1.3.18.
[Nexus S Android Development] simms22:
you need the bln control app from the market to make it work. there is a free and a pro version. the pro(paid) version is worth it :)
[Nexus S Android Development] dario3040:
Actually the i9023 has a superlcd screen and some different drivers. Its not an upgrade (i'd say downgrade).

And if my facts are correct: Herring is the codename for the motherboard while crespo is the device code name
[Nexus S Android Development] eiabea:
herring, what a stupid name XD, but okay

why a downgrade?
[Nexus S Android Development] simms22:
is that a herring in your pocket, or are you just happy to see me :eek:

anyways, hes says downgrade because the 9020 is a super amoled screen and the 9023 is a lcd screen. super amoled displays more vivid colors and a true black.