yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] stoehner:
I guess I can't use this with bs harmony rom...think I'm bricked, any ideas to get into recovery? I'm stuck on android upgrading screen

Ps...got into recovery!
[Nexus 7 (2013) Original Android Development] AarSyl:
Lol...no, far from bricked. Hold the power + vol up buttons until the device reboots AND you see the Google logo. Then you can release. It will boot directly into recovery. Not sure how you got there, but this is one method.

Also, give the glitch Kernel a run....it works great for CM (Harmony is included).

_______________________________________

Phone: HTC EVO 4G LTE

Sense 5, S-Off

Tablet: ASUS Nexus 7.2

Rooted, Custom Rom & Kernel

_______________________________________
[Nexus 7 (2013) Original Android Development] katsooba:
You can use usb and dac with stock, but you will not get charge.
[Nexus 7 (2013) Original Android Development] username4this:
How do you guys update?

Just dirty flash it ontop of the older version?
[Nexus 7 (2013) Original Android Development] AarSyl:
Wipe caches in recovery and flash.

_______________________________________

Phone: HTC EVO 4G LTE

Sense 5, S-Off

Tablet: ASUS Nexus 7.2

Rooted, Custom Rom & Kernel

_______________________________________
[Nexus 7 (2013) Original Android Development] antonholmstedt:
I don't even wipe cache, maybe I should.
[Nexus 7 (2013) Original Android Development] username4this:
I didn't wipe cache and with the same settings I scored 28 000 on Antutu.

Couple of points more than with 2.4 version.
[Nexus 7 (2013) Original Android Development] NovaSlim:
I wipe cache and dalvik in recovery then flash ontop of the older version.
[Nexus 7 (2013) Original Android Development] leo81486:
is the OTG host + charging for car works now???:cyclops:
[Nexus 7 (2013) Original Android Development] melander:
i tried 2.6 kernel on CleanROM 2.6

i am unable to detect 3G modem in PPP widget in automatic mode

tried to do manual detection

can see the port "icera" selected that but then the widget just says "unknown device"

any thoughts?
[Nexus 7 (2013) Original Android Development] flar2:
Sorry, not yet

Did it work before?

If it worked before, it should work now. There were no changes to that aspect of the kernel.
[Nexus 7 (2013) Original Android Development] gnotelover97:
Really great kernel. Smooth performance. I just had one question. I was not being able to change minimum frequency of my processor from 1.2 GHz to 384 MHz. After disabling MP Decision system of Qualcomm, I was able to do that. Will disabling this hotplug and frequency system of Qualcomm affect my Nexus?
[Nexus 7 (2013) Original Android Development] Pfeffernuss:
No you shouldn't. When flashing a kernel that is completely unnecessary. If you like to wipe, please do. Will it have a result, well no :D
[Nexus 7 (2013) Original Android Development] antonholmstedt:
Haha good to know, thought I missed something :)
[Nexus 7 (2013) Original Android Development] konradsa:
Hi flar2,

I have a problem with 2.6. This morning, I noticed the battery seemed to be draining more quickly than normal. When I checked with trickster mod, one core seems to be stuck at full speed, see attached screenshot. Going back to 2.5 for now.
[Nexus 7 (2013) Original Android Development] melander:
I just tried it today, it could be with the 3g modem that I have, will test this out further. thanks for the response.
[Nexus 7 (2013) Original Android Development] kingston73:
If anybody was wondering, the 2.6 is working well with the latest aokp. I've only been using it a day though so I can't say anything about battery life. Definitely made it smoother than the stock aokp kernel though.

---------- Post added at 08:07 AM ---------- Previous post was at 08:00 AM ----------

What rom are you using? You have 2 window and HALO? Nice...:good:
[Nexus 7 (2013) Original Android Development] schlager:
anyone tested the DVB modules? I have a DAB stick but not sure where to get the app to run it...

Also, why are there no DVB modules for 4.4? Is it an issue with Kitkat?
[Nexus 7 (2013) Original Android Development] farenteria:
If I recall correctly, you must have MP decision on since that's the only way to control the cores with this kernel. Otherwise they'll all be on all of the time (someone correct me if I'm wrong there).

As far as to not changing the minimum, it's actually at 384, but apps will not show the minimum properly when MP decision is on. I'm not sure why, but it may be due to a boost in frequency when touching the screen (again, someone correct me if I'm wrong)
[Nexus 7 (2013) Original Android Development] flar2:
This has been asked a million times. You should just leave it be, the minimum is 384 by default. You're seeing the effects of touchboost. Mpdecision should be left enabled.

This is due to an app or system running wild. A reboot would probably fix it.

I haven't got around to it yet.
[Nexus 7 (2013) Original Android Development] schlager:
yet another happy customer.

flashed with AOKP 2013-12-30 + ElementalX.

works great! looking forward to DVB support.
[Nexus 7 (2013) Original Android Development] wantabe:
[MENTION=4684315]flar2[/MENTION] ElementalX governor w/gboost enabled is much, much smoother now for me than it was on v2.4 and benchmarks seem to be a little higher also. I always ended up going back to ondemand but I'm sticking with the ElementalX governor and will see what kind of improvement in battery life I can get if any. Awesome job!
[Nexus 7 (2013) Original Android Development] csec:
Guys, I am recently having suspend _ backoff wakelocks. 16hours of them this is the second time in past 4 days. On 2.4 and now on 2.6. My Flo was on table and wifi was also turned off. No touching of the screen.

I looked around and couldn't track down the issue.

BTW, I am on Stock 4.4.2. And new to my Flo. :D

Anyone knows anything about this?

EDIT: the device was never in deep sleep state in this cycle! 16 hours on 384 MHz.
[Nexus 7 (2013) Original Android Development] GialanG:
I googled and found this: http://hackups.blogspot.com/2013/08/suspend-backoff-wakelock-on-android.html
[Nexus 7 (2013) Original Android Development] sokinso:
Hey guys today morning I faced a weird touch screen issue scrolling on Facebook and other apps was so sluggish and touch screen was losing my touches many times.

After a reboot everything works fine.

what was that about.

Running stock 4.4.2 with 2.6 on ART
[Nexus 7 (2013) Original Android Development] LoopDoGG79:
Could be ART, since it's considered experimental.
[Nexus 7 (2013) Original Android Development] _cb_:
Hi flar2, thanks, marvelous work!

I really like what you have done so far to get OTG host + charging working. I think I got one workaround for those who need to recover after power loss without doing any physical reconnection. I'm doing an unbind and bind on the otg hub after charger reconnection, and this helps the USB-bus to reconnect all connected devices.

echo "2-0:1.0" > /sys/bus/usb/drivers/hub/unbind
echo "2-0:1.0" > /sys/bus/usb/drivers/hub/bind

I guess there are nicer ways to do this through ioctl or by the kernel itself by doing something similar as the EMI recovery hack. Sorry, I'm not allowed to submit urls, but search google for usb-port-nn-disabled-by-hub-emi-re-enabling.
[Nexus 7 (2013) Original Android Development] aycockonxion:
Is it necessary to manually enable DoubleTap or anything? This doesn't seem to be working for me.
[Nexus 7 (2013) Original Android Development] combatdeity:
I've had this issue before on stock, no idea what causes it, wasnt running ART either.
[Nexus 7 (2013) Original Android Development] csec:
Yeah, I already saw these kind of explanations. A fairly elaborate one on Github.

About Google Chrome issue, I thought it was in Google's upstream to fix, as it is not a new issue.

I wondered if it is something kernel related, like DT2W, just wanted to know that there isn't something I missed, as I am new to Flo (Not new to android!, or Google. ;) ).
[Nexus 7 (2013) Original Android Development] NovaSlim:
by default the power button toggles double Tap on/off(thus turning the screen off by power button also disabled dt2w) , let the screen timeout and shut down by itself then try double/triple tap the screen to see if it wakes up.
[Nexus 7 (2013) Original Android Development] konradsa:
Keeps happening to me too, haven't found the cause for this yet. I posted about this a week or so back, and flar2 said he doesn't think it's kernel related.
[Nexus 7 (2013) Original Android Development] sokinso:
Was it just one time or it happens more regularly?
[Nexus 7 (2013) Original Android Development] wantabe:
[MENTION=4684315]flar2[/MENTION] Well sir, I have to say that I picked up my N7 this morning, looked at the screen, and immediately thought "This is Ridiculous!" I've always managed to get pretty decent battery life when the tablet was idle but this was the first time seeing those kinds of numbers! Running stock 4.4.2, 1620/450 frequencies, elementalx L2 & bus, elementalx governor w/gboost enabled, dt2w and s2w disabled, deadline i/o scheduler, max screen off @ 1026, uv @ 850. Very impressed with the performance and battery life of v2.6. Awesome job! Thank you!
[Nexus 7 (2013) Original Android Development] aycockonxion:
I see, that does work. I just finally saw that note on the OP also. I wonder just how much disabling the power button toggle would really drain the battery.
[Nexus 7 (2013) Original Android Development] csec:
flar2 is probably right. It's usually not kernel related.

BTW, this kernel is awesome. Thanks for the effort, flar2. :good:
[Nexus 7 (2013) Original Android Development] red man:
Hay im running Dirty Unicorn(4.4.2) and the latest elementalX kernal and it does charge my nexus 7 with the OTG cable and sends power to my DAC, but the sound is still playing through the speakers of my Nexus.

the DAC im using is the Behringer UCA-222 it works fine with CM10.2, but no OTG charging.

I just tried cleanrom with elementalx and same thing, DAC turns on but sound is still coming from internal speakers
[Nexus 7 (2013) Original Android Development] flar2:
I think Rom support is necessary

but you could try having the sac plugged in before booting up the tablet and see if that works.
[Nexus 7 (2013) Original Android Development] red man:
Yea, think so. Clean rom and dark unicorn are good roms, but I guess I will be going back to cm10.2

You did some awesome work with this kernel and I thank you for that.

I was reading that cm10.2 with the DAC and wireless charging works.

Will give that a shot.
[Nexus 7 (2013) Original Android Development] babyjesuz:
any possible way this kernel can run on nexus 4 also?
[Nexus 7 (2013) Original Android Development] jugster:
Yes, of course.

Not probable though.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] xanthrax:
as far as I can see you hate nexus 4 to death

if you really want to kill it just flash another non-nexus 4 kernel and you can avoid to blame flar for that...

but if you're talking about porting it to n4 then you have to think first whether flar owns a nexus 4 or not

sent from my Darkside of Nexus 7 LTE
[Nexus 7 (2013) Original Android Development] marcus6999:
I've seen that the kernel keeps always the four cores awake. Just wanted to know if this action may not be draining a lot of battery in case sometimes we only want to read pdf's, books or maybe doing things that are not such performance demanding?
[Nexus 7 (2013) Original Android Development] flar2:
There's something wrong with your setup

Did you flash Franco kernel before this? If so you need to dirty flash your ROM to repair the installation then reinstall ElementalX.
[Nexus 7 (2013) Original Android Development] marcus6999:
Okey, dirty-flashed the rom and reflashed kernel, everything works perfectly now, I was with faux kernel before.

Thanks flar2. :)
[Nexus 7 (2013) Original Android Development] CallMeTut:
I'm new to flashing and switching aroung on rom's and such... I've been attempting to edit the confg file but can't (most likly because it's in use with the kernel using it while running). How do I change the config file? I was attempting to change the lid=1 to lid=0 or do I need to just re-flash the zip and adjust my setting that I want when re-installing? I would think if I just copied the file to my pc then edited it I would still get an error trying to copy the file back to the tablet since the file would still be in use... any assistance would be appreciated.

Tutor
[Nexus 7 (2013) Original Android Development] flar2:
If using ES File Explorer, open the menu, click tools, then turn on Root Explorer. Long press Root Explorer to bring up another menu, click Mount R/W and set /system to RW. Then you should be able to edit the file.
[Nexus 7 (2013) Original Android Development] babyjesuz:
right..

let me re-phrase that so maybe i can get a response thats a little more relevant..

any possible way this kernel can be ported to the nexus 4?
[Nexus 7 (2013) Original Android Development] El Nino1977:
As the previous guy responded, unless someone with the knowledge willing to compile its very unlikely when the dev (flar) doesn't own the device. Also the device has different hardware capabilities.
[Nexus 7 (2013) Original Android Development] CallMeTut:
Thx flar2
[Nexus 7 (2013) Original Android Development] schlager:
I am using using an otg y cable (http://www.amazon.com/Micro-Cable-P...id=1389293141&sr=8-1&keywords=usb+otg+y+cable) and I am not seeing the expected effect for USB otg charging.

I've set USB host mode charging in the kernel installer (set to Y in the config file). The otg device requires power from the Y cable to operate, however, the Nexus does not charge from the Y cable (i think..). Disconnecting the otg device has no effect. I have to remove the Y cable and plug in the charger cable directly.

Is this an issue with high current (tablet style) chargers (shorted data pins?). Should I just consider the Nexus to be charging properly even though the status bar isn't showing the Charge symbol?
[Nexus 7 (2013) Original Android Development] Austin808:
Flar2,

Thanks for this great Kernel. It's perfect for the N7. Love the double tap to wake feature.

One issue I have is that when using it in OmniROM, I am unable to flash the OTA update. The OTA downloads fine, but when I click on the flash button nothing happens. When using the OmniROM kernel it flashes correctly. Not sure if this is something built into the OmniROM kernel or not.
[Nexus 7 (2013) Original Android Development] flar2:
If it isn't showing the charge symbol, it's not charging. It could be the cable. Certain cables don't send power to the uplink. The setup I use is a standard otg adapter and a separate y-cable.

It's probably like getting stock OTAs. The OTA process is looking for the stock kernel, and if it doesn't find it, it aborts. If the OTA update is to be failsafe, it needs a standard setup.
[Nexus 7 (2013) Original Android Development] Austin808:
Okay thanks. I would rather use your Kernel and take the extra step to flash the OTA manually.
[Nexus 7 (2013) Original Android Development] phanguy:
use this:

http://xdaforums.com/showthread.php?t=2545628

based on cm11 and works with flars kernel. i'm using it in my car and it's smooth sailing. once flar builds in support for usb hubs then i'll be 100% set. otherwise as of now i'm only running the dac on the y cable that's connected to my nexus 7.
[Nexus 7 (2013) Original Android Development] roco446:
Should doubletap2wake works with a rooted Stock 4.4.2? I'm trying it but nothing happens, im sure that it is enabled with the "1" but doesnt works :(

I need that function!
[Nexus 7 (2013) Original Android Development] red man:
Did you make sure it was enabled when you flashed the kernel
[Nexus 7 (2013) Original Android Development] CallMeTut:
Works on mine...
[Nexus 7 (2013) Original Android Development] crazyyyk:
After install 2.6 on pure 4.4.2 stock I noticed a huge battery drain... Had to revert to stock...
[Nexus 7 (2013) Original Android Development] flar2:
Apps and system services cause battery drain, not the kernel. Maybe some google services were running wild.

Strangely enough, 4,000 others downloaded 2.6 and did not have this problem. I'm guessing you didn't even try rebooting, but immediately blame the kernel for your problems and feel the need to come here and tell the world, perhaps to warn others.
[Nexus 7 (2013) Original Android Development] flar2:
Did you enable the "power button toggles s2w/dt2w" option? Perhaps you turned off the screen with the power button and disabled doubletap2wake.
[Nexus 7 (2013) Original Android Development] crazyyyk:
I didn't blame the kernel. I just said. I lost 12% of battery for 4 hours when the tablet was in deep sleep, just after install the kernel. All my apps, include system from google was hibernated with greenify.

In aroma I choosed all stock + uV 725mV + all double taps and slides disabled + disable gboost.
[Nexus 7 (2013) Original Android Development] hello247:
Let the kernel settle in. Then see
[Nexus 7 (2013) Original Android Development] jugster:
Fyi,

The above is what is called blaming the kernel. Saying reverting to stock means that something was wrong with not stock, which is this kernel.

Unless you meant changing ROMs which I don't think you meant.

So yes, you did blame the kernel.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] xanthrax:
Look what can happen if one doesn't switch off the lights before sleep, aka, killing the running apps... Pic taken from n4 but can apply to n7 also

sent from my Darkside of Nexus 4
[Nexus 7 (2013) Original Android Development] LinearEquation:
No doubt, I had the six axis app drain my battery down to 2%. I figured the tablet would have died at 10% or so but nope, drained the heck out of it.
[Nexus 7 (2013) Original Android Development] xanthrax:
I'm too using sixaxis and always kill the process but last night I switched off the screen leaving that game in background...

sent from my Darkside of Nexus 7 LTE

---------- Post added at 09:23 AM ---------- Previous post was at 09:18 AM ----------

the way people express themselves can be sometime misunderstood , just don't discourage the guy, he will figure out one day

sent from my Darkside of Nexus 7 LTE
[Nexus 7 (2013) Original Android Development] kingston73:
Easiest thing to do would be just reflash the kernel and make sure you have d2w button checked in the options. 2.6 is working great for me:good:
[Nexus 7 (2013) Original Android Development] hello247:
just tried this kernel. quite pleased with it.

is there way to make the frequency stick after using the aroma installer? maybe change it in the elementalx.conf file?
[Nexus 7 (2013) Original Android Development] flar2:
Best thing to do is choose your max frequency in aroma and let it be. Everything works best on this kernel if you leave the frequency min and max alone. The governor will use the optimal frequencies.
[Nexus 7 (2013) Original Android Development] treyweez11:
[MENTION=4684315]flar2[/MENTION] ! I see that you said leave the min and max alone. The stock min is 1026. Should we still not take it down to 384? Will it go lower if we don't change it lower? I'm using trickster mod
[Nexus 7 (2013) Original Android Development] flar2:
The minimum is 384. Touch boost is 1026. It's working properly.
[Nexus 7 (2013) Original Android Development] ayenzel:
anyone know of what is this sandbox processed? it happens only after I flash this kernel..
[Nexus 7 (2013) Original Android Development] Lazy79:
It's chrome. Should happen with every kernel.you've set up the flag in chrome for these sandbox processes.
[Nexus 7 (2013) Original Android Development] Traxex_:
Anyone has the problem that you can't turn on WLAN after flashing the newest version?

Gesendet von meinem Nexus 5 mit Tapatalk

//edit: Nvm, I forgot that I'm still on Android 4.3. :rolleyes:

Which was the latest Version working with that jelly bean? 1.8 I suppose?
[Nexus 7 (2013) Original Android Development] PlayDude77:
Yeah, I would advise you guys not to mess with the settings after the aroma installer because when I did my tablet became a little sluggish for some reason.
[Nexus 7 (2013) Original Android Development] AzN MusiQ:
The battery drain on my nexus is very high in standby mode, anyone know why?

Gesendet von meinem Nexus 7
[Nexus 7 (2013) Original Android Development] sokinso:
Almost the same and I don't know why.
[Nexus 7 (2013) Original Android Development] Lazy79:
Make a dump with better battery stats. Looks like badland and a chrome sandboxed process are related to each other. That's strange lol I don't think its the kernel because idle/standby drain of battery is great here. However, I'm using greenify and don't have Facebook here (I prefer klyph as fb app - also because its easier to greenify and needs less battery..). The worst app on my device is tapatalk followed by chrome (beta) in terms of battery drain when using the apps. Maybe you have location services not on power save / device only mode? But to be honest a log by BBS would tell us more and probably its better to post it in the BBS thread and ask for help. As said, here it's really great in terms of the battery drain when its not used.
[Nexus 7 (2013) Original Android Development] konradsa:
While my battery life is not too bad, I definitely had better battery life with 2.4 than I have now with 2.6.

Flar2, can you suggest some options to change for better battery life? Like disabling gboost, keeping GPU at 400, etc. Which options in the installer should have an impact on battery life and which shouldn't? Thanks.
[Nexus 7 (2013) Original Android Development] kkd28:
keep stock is the best solution for battery.
[Nexus 7 (2013) Original Android Development] jugster:
Actually, it isn't. Lots of kernels are better than stock with regards to battery.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] Dan1234567890:
Maybe he ment stock as "default" settings...?:sly:
[Nexus 7 (2013) Original Android Development] kkd28:
yes. just with default settings, and some undervolt might help.
[Nexus 7 (2013) Original Android Development] jugster:
Not true either. Think about it.

Stock is made to fit most people pretty good. It's not made to offer best performance or best battery life. Just reasonably good everything.

If you want best of performance or battery then use a custom kernel.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] nikr123:
Some (most) custom kernels can improve performance without reduced battery. For me, I use custom kernels mostly for bonus features. I would also like to remind you that stock kernels might not always be perfectly optimized
[Nexus 7 (2013) Original Android Development] konradsa:
I agree, I think the battery life I have gotten with any version of ElementalX was always better than stock.

I was just wondering what flar2 recommends in terms of default settings for best battery life. I am sure some settings don't have much of an impact (e.g., GPU from 400 to 450 probably doesn't make much of a difference), while others like undervoting, gboost, governor, s2w, etc. could make more of a difference.
[Nexus 7 (2013) Original Android Development] waz675:
Undervolting helps the tablet run cooler but I haven't really ever seen it give better battery life, at least testing on a few (other)android devices.

It may help on this, don't know but on the 1st.gen tegra3 one, definitely didn't. If I had spare time these days I'd test it but alas, spare time is a very rare.commodity for me these days due to our 2 kids heh
[Nexus 7 (2013) Original Android Development] jugster:
If you have felt the device to be cooler when under volting, then indeed you have seen better battery life. What energy isn't used to heat up your device is used to get CPU cycles out of it.

Under volting has never helped me, not measurably anyway. Not with regards to heat or battery life. At full speed the CPU tend to get pretty hot and at idle it runs very cool. All my devices are like that actually. Of course it varies from device to device how hot they get etc. but as a general rule that seems to be true for me.

Again, YMMV.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] sparkie420:
Are there not Mako kernels already in existence?