yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] yak84:
I just wanna say that my idle "problem" have seen to resolve itself, I think the cell tower near my home was acting up.

Anyway been running latest experiment kernel for a week now without a signal problem , all is smooth and stable as a rock.
[Nexus 5 Original Android Development] Stryder5:
A specific version number would be better when asked that question, when someone is trying to diagnose something. It's nice to assume you have the latest, but you should double check. What if there was an update between when you post that and when the other person reads it?

Sent from my hammerhead
[Nexus 5 Original Android Development] Silentbob999:
Try the weekly 5.8. (5.9 tomorrow)

Me and another guy got similar problem back to March/April. With our log Kufi fix the issue. I am pretty sure Stable 5 have that problem fixed (was related with a quiet hour bug and some other stuff) but you are not losing anything with the weekly.

However, it's really weird that you don't get that problem with Franco.

Maybe something with 4.4.3 kernel that don't play well with the old stable 5.

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] derukun:
There wasn't, (and likely wouldn't be because people here respond pretty promptly thankfully) :D.

But yeah it is on Stable 5 for Slimkat (That's what it's called... or do you mean the build number?) and on the Bricked kernel stable that was released June 4th. Is that a 4.4.3 kernel?

That might actually be the reason, somehow. Stable 5 is still 4.4.2 I think.

And I agree that it is strange. On Franco I barely get any wakelocks, 6-7 SOT no problem.

I'll wait for Slimkat Stable 6 (which will be 4.4.3 probably) and then flash Bricked.
[Nexus 5 Original Android Development] Stryder5:
Yes, I was referring to build number/date for whatever you refer to. Just simply saying the "latest" version isn't a good answer since "latest" can change very quickly. Sounds like you figured out the problem though. Don't use 4.4.3 kernels on 4.4.2 ROMs. Either use an older 4.4.2 kernel, or wait for a 4.4.3 ROM.
[Nexus 5 Original Android Development] DroidIt!:
The slim latest slim weekly on slimroms website is 4.4.3. You can either try that + bricked or wait till this evening for the next weekly. Either way, whatever you decide I'd do a full wipe (wipe all except internal storage) and then flash slim + Gapps + kernel. Also there were some issues with the AIO Gapps that the slim team put out, so I'd maybe try minimal Gapps as well.

from my N5
[Nexus 5 Original Android Development] derukun:
Just flashed 5.8 weekly and bricked kernel, let's hope all goes well...
[Nexus 5 Original Android Development] DroidIt!:
Should be good. I've used the slim + bricked combo myself for about a month now and never had a problem at all ;)

from my N5
[Nexus 5 Original Android Development] derukun:
Okay, seems to be running fine. No strange wakelocks from system_server, phones going into deep sleep as it should.

Of course I can't really do an accurate comparison atm (can't compare a stable build to a weekly, nor 4.4.2 to 4.4.3) nor is my battery even at a full charge...

but at least its deep sleeping.

Thanks for all your help and putting up with my foul attitude, I'm glad it's working now.

Will update in a few weeks to let you know how its going with Bricked.
[Nexus 5 Original Android Development] RobbieL811:
Anytime you have problems like that, the first thing you should do is clean flash. It will fix the problem a lot of the times. At least manually wipe system then reflash ROM. Enjoy the kernel.

Sent from my Nexus 5
[Nexus 5 Original Android Development] IgnorantNerd:
What are your settings for the kickass battery life?
[Nexus 5 Original Android Development] yak84:
All stock settings apart from boost freq for CPU0&CPU1 set to 1.3GHz and boost_time set to 1500.
[Nexus 5 Original Android Development] benzso63:
Anyone using this Kernel on the Nexus 5. Compare to ElementX, which has better battery life?
[Nexus 5 Original Android Development] Tommy-Geenexus:
Battery life depends on too many things, mostly on brightness and installed apps causing wakelocks and so on.

Test it yourself, bricked offers a good performance/batterylife combo.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] benzso63:
Thanks, I just installed. But it is not like the elementx kernel that you can configure settings right. Once I install, reboot it that's it ?
[Nexus 5 Original Android Development] PetritH:
Yeah, Bricked doesn't have Aroma Installer, flash and reboot also make sure to dirty flash your rom first, dont flash it over another kernel, then you have apps like trickster mod that u can configure yourself, uv, uc and other stuff
[Nexus 5 Original Android Development] benzso63:
I did all that. But I will need a different app to configure it ? sorry I am new to this.
[Nexus 5 Original Android Development] yak84:
The best app to use is Kcontrol ,https://play.google.com/store/apps/details?id=de.bricked.kcontrol and a great way to support show-p1984.

Here is an excellent explanation about various tunables in the kernel to play with :

http://xdaforums.com/showpost.php?p=47399641&postcount=2
[Nexus 5 Original Android Development] benzso63:
Thanks for the info. But what if I just install the kernel without tweaking it using the Kcontrol or other app. By default will I still get good battery on it ?
[Nexus 5 Original Android Development] PetritH:
Yeah ofc mate, just flash and enjoy
[Nexus 5 Original Android Development] Dragusdrake:
It is possible to make a script for dt2w that power on it only if the proximity sensor is awake?

For example

If

Proximity sensor bla bla bla ON

Then

Echo 2 SYS/android_touch/doubletap2wake

If

Proximity sensor bla bla bla OFF

Then

Echo 0 SYS/android_touch/doubletap2wake

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] rlaw:
You mean like for phone calls and stuff? I s'pose you could do it with Tasker, might need a plugin. Something like making the proximity state a variable and making a profile to activate upon that variable.

Or just a profile that runs when a call is active might be simpler. Simple exit task, too.
[Nexus 5 Original Android Development] benzso63:
Using it with Mahdi-Rom 2.6. Looks pretty good for battery life.
[Nexus 5 Original Android Development] Spider_Pig27:
Does anyone know if the kernel comes with cooler color options or if your able too apply cooler color options through K-Control?
[Nexus 5 Original Android Development] yak84:
You can configure screen color with Kcontrol yes.
[Nexus 5 Original Android Development] Spider_Pig27:
Awesome thanks
[Nexus 5 Original Android Development] NineInchNails:
Last few pages were pretty entertaining but also disappointing to see happen in any thread.

Where did the respect go?
[Nexus 5 Original Android Development] erisboxx:
Can anyone point me to the latest version of this kernel the stables download link only shows a page with the last downloaded dated in April
[Nexus 5 Original Android Development] fbf2201:
Latest beta in Downloads - no issues so far
[Nexus 5 Original Android Development] DroidIt!:
Some need more of a helping hand than others to see the light. It happens :)

from my N7
[Nexus 5 Original Android Development] om22:
Just installed latest stable and it's the first kernel to get s2w working on PA ROM for me.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] PetritH:
install latest beta which has 4.4.3 commits
[Nexus 5 Original Android Development] jordi_e:
hello,

does this kernel support stock rom 4.4.3,

sorry for noob question but I didn't see someone mention about it at least for 3 pages back

thanks
[Nexus 5 Original Android Development] jlevy73:
Yes it does.
[Nexus 5 Original Android Development] Stryder5:
Post right above yours mentions 4.4.3 commits in the latest betas. But the latest stable should still work.
[Nexus 5 Original Android Development] jordi_e:
got it, though I was just missed it thanks
[Nexus 5 Original Android Development] Tylog:
Before anybody ask, no Kernel changes in 4.4.4 :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] benzso63:
Does sweep2wake and doubletap2wake drain batteries ? I don't have it enabled but just wondering.

currently I am on Mahdi-Rom 2.6 with Bricked Kernel.
[Nexus 5 Original Android Development] :
Yes they still do on the Nexus 5. Not MASSIVE drain but drain is still there.
[Nexus 5 Original Android Development] benzso63:
Thanks, I will give it a try and see how it is.
[Nexus 5 Original Android Development] benzso63:
I have Kcontrol installed and enabled doubletap2wake , after I reboot it. Double tap the screen it won't turn on. is there something I am missing ?
[Nexus 5 Original Android Development] Janzen254:
Did you turn on set on boot for dt2w? You might have to wait until the BOOT_COMPLETED.
[Nexus 5 Original Android Development] benzso63:
I did, see attached screen shot. What do you mean by wait till BOOT_COMPLETED.

once i checked both. There is no option to boot or something. All i did was reboot the phone thats it.

But not working though
[Nexus 5 Original Android Development] show-p1984:
Silly question: Did you turn on dt2w under the dt2w settings? Or just the "apply on boot" part in the generic app settings? :)
[Nexus 5 Original Android Development] benzso63:
I have Apply settings on boot and Apply doubleTap2Wake Settings both set to "ON".

I am not sure if I understand turn on dt2w under the dt2w settings, where can I find another settings under that. Cause once I tap that , it will turn it off and on , thats all it does.

The attached screen shot is also checked. Enabled.

But still nothing workings. doubletap screen won't turn on.
[Nexus 5 Original Android Development] show-p1984:
logcat from bootup and from toggling the switch.

logcat | grep kcontrol > file

I suspect though that you started KControl for the first time with dt2w already enabled. (from a different app or sth) which then causes this behavior. KControl is meant to be launched for the first time with your kernels default settings (from bootup, fresh, without anything changed) so it can read in the defaults properly.

You can mitigate that by disabling and enabling dt2w once (if you started KControl with dt2w enabled for the first time) or wipe KControl's data from Android, disable any on boot apps and scripts you have, reboot, and launch KControl so it can properly read in your defaults.
[Nexus 5 Original Android Development] benzso63:
Wah! That sounds little complicated to me, not too technical here. :rolleyes:
[Nexus 5 Original Android Development] Citizen_Snips:
http://xdaforums.com/showthread.php?t=1726238

:good:
[Nexus 5 Original Android Development] overkillZ:
Is the stable version updated with 4.4.4/4.4.3 commits?
[Nexus 5 Original Android Development] yak84:
No but you can flash the latest experimental build , I've been using it for over a week now and it's as stable as it gets.
[Nexus 5 Original Android Development] hsahin4:
Does bricked kernel compatible with CM-11?
[Nexus 5 Original Android Development] Citizen_Snips:
No. This is an AOSP kernel, not CAF...
[Nexus 5 Original Android Development] Ubichinon:
Im running the latest stable version on 4.4.4 and i have 0 problems.
[Nexus 5 Original Android Development] Savant:
I missed my n5 and bricked and all the other goodies that come from a nexus. I have a m8 and its a totally different world there.
[Nexus 5 Original Android Development] PetritH:
You will miss your Nexus even more when we will be playing with Android L tomorrow :P
[Nexus 5 Original Android Development] Savant:
Yeah, but I still have it and using it now. I use both, I have the 1+1 and a few others my company likes me lol.
[Nexus 5 Original Android Development] PetritH:
Haha, thats nice then, u gonna enjoy tomorrow together with us
[Nexus 5 Accessories] chrisngrod:
[YOUTUBE]HIWv8zNgXpY[/YOUTUBE]

This is my third install of a Spigen Glas product. Prior to that I installed a lot of ZAGG InvisibleSHIELDs simply because they were easy to find when a new phone was released and did the job for the most part.

There is a recall on this screen protector and despite getting the notice before I got this package, the pre recall version still came. Expect the final product to be a lot better.

Of course plastic, film, and glass screen protectors have their own set of strengths and weaknesses. If you're interested in my opinion, I'll give it to you. Just ask.

UPDATE (after the replacement came in)

Removing the old:

[YOUTUBE]w7bB8GPxN0g[/YOUTUBE]

Installing the new:

[YOUTUBE]sgU6p51wSAE[/YOUTUBE]

No issues with this one!
[Nexus 5 Accessories] chefdave12118:
Nice video!
[Nexus 5 Accessories] onmike:
Good video.
[Nexus 5 Accessories] chrisngrod:
Thanks guys. I know it's kind of long, but I've gotten gigged on cutting any of it out. Either way I'm darned if I do, darned if I don't. :D
[Nexus 5 Accessories] chrisngrod:
UPDATED the OP

The replacement has arrived and is much better than the original. :good:
[AT&T, Rogers HTC One X, Telstra One XL] josh45595:
after flashing the latest cleanrom, my htc one x will not boot to anything. when i hold down power and volume down, the bottom buttons flash a few times an the htc splash screen come up and then nothing. i had root and custom recovery. Is there any way to get back to recovery?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Are you s-on? If so did you flash the boot.img via fastboot afterwards? If you can't get to the bootloader it's most likely a matter of bad timing with the button combo. Hold volume down, then power, wait for the screen to go blank, after a couple seconds let go of power but keep holding volume down.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
You should be able to get into bootloader. As timmaaa mentioned, failure to get into bootloader is almost always the user performing the button combo incorrectly. Since in nearly all cases, damage to hboot would brick the device (the screen and charge light would not be coming on at all).

After the capacitive buttons flash, and the screen goes dark, be sure to let go of the power button, but

keep holding down

the vol down rocker) until the white hboot screen comes up.

Failure to boot into the OS after flashing a ROM is most often due to you not manually flashing the boot.img via fastboot (again, as timmaaa already mentioned). This is required if you are s-on and hboot 1.14 or higher (you haven't given those details).
[PDA2, XDA IIi, 2020i Software Upgrading] kev0360:
I use a THB car kit on my 2i, the phone answering works ok for it but the Tom Tom sound only uses the 2i speaker.

Is it possible to route it via the thb amp instead?
[PDA2, XDA IIi, 2020i Software Upgrading] Lord Buckingham:
Which ROM build are you running? The latest O2 Rom has a patch file to route the audio through the car kit. if you do not have thsi i can mail you the file.
[PDA2, XDA IIi, 2020i Software Upgrading] Ra1der:
TT5 and Sound but with Parrot CK3300

I have a similar issue and wodered if you could help with this. The TT5 sound works fine when the XDAIIi is not in any powered cradle but as soon as I put it in a powered cradle, necessary for long journeys, the sound is auto muted somehow. The GPS system and car Kit is combined but its not physicaly connected to the XDAIIi. THe powred cradle is just that just power. Interestingly this doesn't happen on my wifes XDAIii which I haven't upgraded the ROM on.

Lazy mans answer is to revert back to the old ROM somehow but hey we like to progress!
[PDA2, XDA IIi, 2020i Software Upgrading] baldave:
Tom Tom sound

I have a similar problem, but i believe it is due to the fact the cradle was designed for the XDA1, but i could be wrong! I have the XDA 1 and the XDA IIi and the TOM TOM car kit works fine with the XDA1, but no sound with the XDA IIi

Can anyone help? :)
[PDA2, XDA IIi, 2020i Software Upgrading] sexyali:
can the patch be used for the holux cr100, i am using pugz rom!
[PDA2, XDA IIi, 2020i Software Upgrading] festen:
Please follow-up this discussion in following topic:

http://xdaforums.com/viewtopic.php?t=39735

This way we keep it central. Thanks!
[PDA2, XDA IIi, 2020i Software Upgrading] Sidewindr:
festen: That's a Wizzard thread not an Apline one ...

I too have a THB Bury car kit and have had the same problems and the response from THB when I contacted their support was the XDA2i is not supported. I am sure there is a way to do it tho. I was thinking of making a phono jack to plug into the headphones and then plug that into the

NAV input of my stereo :D
[PDA2, XDA IIi, 2020i Software Upgrading] kev0360:
Updating the ROM did the trick, sound through the speakers for TOM TOM and the incoming phone calls.

Then it got stolen........
[PDA2, XDA IIi, 2020i Software Upgrading] Ra1der:
I guessed it right I am lazy. Reverted to a chance backup copy of the original o2 ROM and TT5 sound fine and self mute during call!
[Ouya General] Alexsandra:
I downloaded Oct version from XBMC website. It is able to play 720p and 1080p movies without any issue. The most important thing is it doesn`t have any passthrough issue. It can decode DTS/DD and output it into my home theater!!! The only thing that you have to do is to modify its default setting. Please see the following settings

system - settings -audio output

Audio output - HDMI

Speaker Configuration - 5.1

After that, enjoy the impressive audio effects from your speakers.

By the way, you have to own home theater that can support HDMI input/output or buy an hdmi switcher that can separate audio and output via coaxial.
[Ouya General] dexter84:
It doesn't work for me. When I play dts movie on ouya I still get hiss noise in my amp. This isn't fixed yet.
[Ouya General] dalamario:
It's not the ouya the problem, is your amp. Pass-through means that the digital audio signal is not decoded/processed by ouya but sent directly to the amp or home theater "as is".

If you have hiss noise it's because your amp it's not able to decode the audio. Your ouya is connected directly to your home theater? Or with the TV between it?

Ouya --> TV --> Home Theater

In this case, TV can be the problem.
[Ouya General] bimbar:
Known ouya xbmc bug, not receiver problem.

ARBEIT ANGST KONSUMTERROR
[Ouya General] dalamario:
The OP was speaking about xbmc 13, not the ouya xbmc (are two different things). XBMC 13 it's working fine.

I use DD and DTS passthrough without any problem.
[Ouya General] dexter84:
My setup is as follows: Ouya <=> Amp <=> TV

When I start playback I get hissing sound. I don't think it is the amp, because I have two options to solve it and make it work temporarily:

1. Restart amp during playback. After restart DTS sign appears on the amp and it's working ok until I stop or pause

2. Start playback with amp powered off and power it on after playback begun. The result is same as in first case
[Ouya General] backlund:
Same here. Tried 13 monthly and latest nightly and the passthrough issue is still present. Now that the storage issue is getting ironed out, I hope they dedicate some time to getting this fixed. Unfortunately, as more time passes, I start to wonder if they'll just blow it off until Ouya 2.0.
[Ouya General] flamepanther:
If you take the survey from the Abominable Snowman release notes, the passthrough issue is one of the choices for what they should focus on next. If you're worried, you should go vote on it.
[Ouya General] backlund:
Thanks. Survey submitted!
[Ouya General] gfdsaorg:
it is not 100% fixed, but seems to be more convenient here. Only had to do the amp on/off trick once to get the audio decoded properly. On the previous builds and on the current (v12.4) ouya xbmc the trick has to be performed every time the audio stream is interrupted (start/stop). Going to games and the ouya xbmc, playing music or even turning off the amp doesn't seem to affect it anymore.
[Ouya General] Alexsandra:
Most of my DD/DTS 720P movies can play without any problem. But some 1080P movie I met problem. I dont know why because others can play very well. I hope the stable version of xbmc 13 could solve this issue.....
[Ouya General] nchantmnt:
Im on nightly 10 and for now I don't have any issues at all. But may vary by setup and media files.

Gesendet von meinem HTC One X+ mit Tapatalk
[Ouya General] huckjam:
I've been running that as well with no problems and I just switched to a new receiver and it works great on it too. No hissing great sound on everything played on it. But I really haven't had any problems with any of the libstagefright versions of xbmc I sideloaded. The only problems I had was the one in the ouya store ironically.
[Ouya General] nchantmnt:
Glad to hear that. Well, I must say one issue stays with the new version. Sometimes during playback xbmc just crashes. But no idea if it's because of low memory, bug in this nightly or even because of me controlling the xbmc with yatse from my phone. Guess I will have to take a deeper look into it. :)

Gesendet von meinem HTC One X+ mit Tapatalk
[Ouya General] danbst:
I must admit I got tired of updating every day so I'm not sure how far we've come..... The last November monthly build was still suffering from the bug that causes massive stutter after around 70-80 minutes. This isn't the Wifi/Lan buffer lag but dropped frames (I play 99% of my files from USB). I remember reading one of the Devs finally understood the cause but I wasn't sure if it was baked into any nightlies yet.

Anyone else have this and if so has it been sorted on any build yet please?
[Ouya General] drumst1x:
I can't speak to the 70-80 minute bug as I've only just set up my Ouya (last night), but when I installed the nightly (2013-12-08) it worked perfectly for 5 minutes with a 1080p mkv stream. Decoded 5.1 (i had to go into audio settings to set it to 5.1). I didn't use passthrough, as I couldn't figure out how to get it to work.

OUYA -----[HDMI]----> Samsung TV -------[SPDIF]------> Yamaha Receiver

surround has always worked from my STB (same setup as above, but replace OUYA with STB). However with a laptop I've never been able to get surround working, only 2.0. Can't believe this is working with the ($99!!!!!) Ouya and streaming everything over wifi with ease! I may never upgrade beyond this version :)

Ouya store version is crippled (decode licenses) and not working nearly as well.
[Ouya General] tarvoke:
had been trying the nightlies but recently went back to v13 alpha-10 monthly.

local 1080p and 720p files don't seem to have any problem. (e.g. stuff from auby.no, big buck bunny, etc.)

networked 720p over SMB/CIFS started out awful (normal audio but stuck video) but eventually stabilized and are now decent (e.g. Venture Bros. season 5 mkv h264+dd5.1) - it did crash/force-quit xbmc once or twice, but was perfectly fine on restart.

haven't tried networked 1080p.

networked SD (xvid or like 480p 264, no problems there at all.)

hmm the default subtitle settings will need some tweaking lol.
[Ouya General] nchantmnt:
For everyone lacking a decent home cinema center or other dts compatible hardware: try spmc

It's basically unofficial xbmc for ouya with full Dolby digital and dts encoding and decoding capabilities.

Gesendet von meinem HTC One X+ mit Tapatalk
[Ouya General] Ipse_Tase:
Word of advice: I have a few mkv's that freeze SPMC (12.4.1) but play just fine in XBMC 12.3.2 - killa.sampla.1080p.mkv is one example.

I poked koying (SPMC author) about that, as it might be a libstagefreight issue.

http://www.gossamer-threads.com/lists/mythtv/users/386450
[Ouya General] muppetnuts:
Keeps Crashing

I have used all of the recommended versions of XBMC on my ouya (sideloaded and Ouya store) and they all keep crashing and going back to main Ouya menu whgen 10-15 minutes into a movie. Its begins with 630MB of Ram available but after 10 mins of usage its at 65MB of ram.

I have followed all instructions laid out in the XBMC posts on here but still having problems. Any ideas??

Cheers in advance