Pretty simple actually. Just set up the gesture in gmd gesture control and under action go to media actions. Media volume is the one you want.
Sent from my One using Tapatalk
Nexus 7 2013 Timur's Kernel USB OTG + Charging is here
- Thread starter ChocoboX
- Start date
- Status
Pretty simple actually. Just set up the gesture in gmd gesture control and under action go to media actions. Media volume is the one you want.
Sent from my One using Tapatalk
Now that i have volume control im trying to get next problem solved!
In my opinion spotify interface is to small to be handy in a moving car.
Ex: trying to hit the right song and miss becouse bar is to small and car is moving, play pause and so on.
anyone know if you can get new themes? or change sizes on stuff in spotify?
Also next challange. revesle cam to grabber card. anyone got a grabber card working win timurs kernel?
/Diio
In my opinion spotify interface is to small to be handy in a moving car.
Ex: trying to hit the right song and miss becouse bar is to small and car is moving, play pause and so on.
anyone know if you can get new themes? or change sizes on stuff in spotify?
Also next challange. revesle cam to grabber card. anyone got a grabber card working win timurs kernel?
/Diio
Quick question: tried searching but didn't find much. T1mur does this kernel support DVB modules like last gens did? Was thinking about getting one for the FM radio. I only use it at drive-ins so its not high priority for me. Just curious
Android 4.4.4
I have successfully ported my kernel to 4.4.4. Since 4.4.4 is a bugfix release, I would suggest we skip 4.4.3 altogether.
If you have a rooted tablet (and I think you do), you will not be able to upgrade via Android OTA images. You can, of course, use a Google factory image, but this will make you lose all your apps and settings. However...
This article: http://forums.androidcentral.com/ne...-how-flash-4-3-factory-images-your-nexus.html describes how you can upgrade via factory image AND avoid loosing your data (avoid wiping your /data partition). The article was written for 4.3.x. But when using the correct factory image (KTU84P for flo) from here: https://developers.google.com/android/nexus/images#razorktu84p, you will be able to upgrade to 4.4.4, without loosing any of your settings, apps, etc. The key is, to follow the info in the orange "TIP:" box at the bottom of the page. You need to remove the "-w" parameter from the flash-all script. When this is done, you still need to re-install your recovery system of choice and then re-install SuperSU. That's all.
I will make my 4.4.4 kernel available soon. If you're a sponsor, have a flo device and are interested in upgrading, please drop me a mail with "4.4.4 kernel beta" in the subject line. Thank you.
I have successfully ported my kernel to 4.4.4. Since 4.4.4 is a bugfix release, I would suggest we skip 4.4.3 altogether.
If you have a rooted tablet (and I think you do), you will not be able to upgrade via Android OTA images. You can, of course, use a Google factory image, but this will make you lose all your apps and settings. However...
This article: http://forums.androidcentral.com/ne...-how-flash-4-3-factory-images-your-nexus.html describes how you can upgrade via factory image AND avoid loosing your data (avoid wiping your /data partition). The article was written for 4.3.x. But when using the correct factory image (KTU84P for flo) from here: https://developers.google.com/android/nexus/images#razorktu84p, you will be able to upgrade to 4.4.4, without loosing any of your settings, apps, etc. The key is, to follow the info in the orange "TIP:" box at the bottom of the page. You need to remove the "-w" parameter from the flash-all script. When this is done, you still need to re-install your recovery system of choice and then re-install SuperSU. That's all.
I will make my 4.4.4 kernel available soon. If you're a sponsor, have a flo device and are interested in upgrading, please drop me a mail with "4.4.4 kernel beta" in the subject line. Thank you.
Last edited:
^ awesome!!!
Wish thats why I'm here, Im trying to figure out the intent setup to call an event in tasker to force a suspend. heres the deal.
I log obd2 data from my car as Im testing some things for a new supercharger. When i pull into my house I have tasker ship some data off to a file server automatically. Problem is with Timur as soon as I cut the ignition the device kills all the radios. I would normally be ok with setting the time-out to like 60 seconds but sometimes it takes a lot longer than that, and I have some error handling built in in case of a flakey connection.
Ultimately, I'd like the device not to suspend until I send an intent to do so.
- I set the timeout of screen to 5 minutes
- Have tasker do its thing and send the following intent when complete.
Send Intent [
Action:timur.event.gotoSuspend
Cat:
Mime Type:
Data:
Extra:
Extra:
Package:
Class:
Target:
]
The result now is ... well .. nothing. It will just count down for 5 minutes the suspend naturally.
Im hoping there is data or target info thats missing causing this.
Thanks in advance.
Wish thats why I'm here, Im trying to figure out the intent setup to call an event in tasker to force a suspend. heres the deal.
I log obd2 data from my car as Im testing some things for a new supercharger. When i pull into my house I have tasker ship some data off to a file server automatically. Problem is with Timur as soon as I cut the ignition the device kills all the radios. I would normally be ok with setting the time-out to like 60 seconds but sometimes it takes a lot longer than that, and I have some error handling built in in case of a flakey connection.
Ultimately, I'd like the device not to suspend until I send an intent to do so.
- I set the timeout of screen to 5 minutes
- Have tasker do its thing and send the following intent when complete.
Send Intent [
Action:timur.event.gotoSuspend
Cat:
Mime Type:
Data:
Extra:
Extra:
Package:
Class:
Target:
]
The result now is ... well .. nothing. It will just count down for 5 minutes the suspend naturally.
Im hoping there is data or target info thats missing causing this.
Thanks in advance.
C
chaserwaser25
Guest
I just rooted my device using wugfresh. Is this all I need to do and then get your kernal and install?
"Xtended NavBar Supercharges Your On-Screen Navigation Bar using Xposed"
http://www.xda-developers.com/andro...s-your-on-screen-navigation-bar-using-xposed/
(Didn't have a chance to try this myself yet.)
http://www.xda-developers.com/andro...s-your-on-screen-navigation-bar-using-xposed/
(Didn't have a chance to try this myself yet.)
nice! but not customizable and should however swipe to use play/pause.
I'm trying to ask on xposed module request thread a module that revive the old usbrom navbar
This is because... you don't call timur.event.gotoSuspend.
timur.event.gotoSuspend intent broadcast calls you: https://timur.mobi/timurs-kernel-n7-2013/faq/#broadcast-intents
What about this? Use timur.event.gotoSuspend event to turn the screen off (via tasker),
then do your data processing "in the dark" and finally, suspend transition will happens at
the +5 minute mark.
@chaserwaser25: Don't know wugfresh, but if it...
- unlocks the bootloader (what you can use "fastboot oem unlock" for)
- installs a custom recovery system (like CWM recovery)
- installs SuperSU (or something providing the same functionality)
...then yeah, this is all it takes.
---------- Post added at 04:44 PM ---------- Previous post was at 04:36 PM ----------
v2 for 4.4.4 (unlike v1 for 4.4.2 - and unlike stock Android kernel) enables you to load kernel modules (loadable device drivers) at startup.
I am providing easycap + powermate modules (.ko files, via separate download).
Timur's Kernel v2 also makes /dev/video* devices accessible to 3rd party apps. No need to change permissions for the video devices. (Also working post suspend.)
I am not currently providing DVB drivers.
Last edited:
Am I understanding right, it is $40 USD to use this kernel?
Just jumping in to dash mounted N7 game.
Just jumping in to dash mounted N7 game.
Last edited:
If you wanna be in the beta program you have to donate.. Otherwise you can wait till Timur will release the final release free.
Marco
Inviato dal mio GT-I9505 utilizzando Tapatalk
Marco
Inviato dal mio GT-I9505 utilizzando Tapatalk
Unless I missed the change, there well be no free release this time
Sent from my SCH-I605 using Tapatalk
I presume that there will be a free release any time.. Soon or later. Anyway... I know Timur is borderline but this kernel worth every single penny.
Marco
Inviato dal mio GT-I9505 utilizzando Tapatalk
He posted before it isn't the kernel, it is the otter software you are paying for. Either way I paid for the pre release and it has been worth it. Excellent tech support
Sent from my SCH-I605 using Tapatalk
So where can i download the, as the title says, Nexus 7 2013 Timur's Kernel USB OTG + Charging sources?
They MUST be made public.
This stated in the op:
violates the GPL_v2 licence and is NOT legal.
Last edited:
Reposting.
Your aren't buying, you are "sponsoring". It's a gray area, I agree, but between tech support and the fact it works so well I dont care and I don't regret it one bit
Sent from my SCH-I605 using Tapatalk
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5More good news!
By fixing a shortcoming in the default kernel, I was able to further reduce battery discharge in suspend mode.
With this modification in place, discharge in suspend mode will not be "around 4% to 7% in 10 hours", like mentioned above, but more like 1% - 2% in 24 hours. This is with the OTG adapter plugged and all USB devices connected.
It means, that you only need to charge your tablet for 6 minutes a day (or 45 minutes per week), to keep it at 100% charge level. And that your battery can stay operational through 50 days / 7 weeks of deep sleep. (Not yet tested in practice.)
The screenshot below was taken after waking my device after nearly 22 hours of deep sleep:
This modification is implemented in FI-kernel 04-02 (or newer). Note: you need to have services 03-28b (or newer) installed as well. Both installers are immediately available for download.
Thank you Kevin, for pointing me in the right direction.
Mod edit: Link removed.4I am looking for a small number of users, ready to test Timur's Kernel v2.0 alpha on 4.4.3 (flo + deb).
To begin with, you should have a rooted stock 4.4.3 on your tablet already.
If things go well, I will do a v2.0 beta soft launch starting next week.
By soft launch I mean a slowly widening user base for the v2.0 / 4.4.3 kernel.
When the v2.0 kernel is confirmed to be as stable as the v1.0 kernel, the beta period will end - and the v1.0 release will be eol'd.
If you are interested in participating, please drop me a line.4
Release v1.0 (May 06th and newer) has been made available to all my sponsors. After three month in beta, I am very confident with this release. Thank you very much for your support. If you cannot find the new installer, please contact me. I am still missing flo/deb info for a few users.
Release notes: https://timur.mobi/timurs-kernel-n7-2013/updates
Sorry, there will be no free-to-download version this time. My free-to-download solution for Nexus 7 2012 can be found here: http://rootzwiki.com/forum/513-nexus-7-development
To get access to Timur's Kernel for Nexus 7 2013, you need to become a sponsor. Please check this page on May 12th: https://timur.mobi/timurs-kernel-n7-2013
I will also make my kernel sources available to sponsors soon. Most likely starting the week after (May 19-25). If you like to get access to my kernel sources, please drop me a line.
Timur4Quick update on the state of the project.
I have spent the last couple of weeks fixing two specific issues related to suspend mode:
Issue 1: On removal of external power, the screen was turning off, but the tablet did NOT transition into deep sleep. In this situation, the device would appear to be OFF, but the CPU was continuing to work and the tablet was discharging at a rate of about 4% per hour. In all cases this happened due to 3rd party "wake locks", preventing the device from entering suspend mode properly. All wake lock related issues should be fixed now.
Issue 2: Device has transitioned to deep sleep, but would wake up randomly, due to 3rd party "alarm events". The modified "Firm Sleep" functionality will now take care of all of these issues.
I added the following new info to PowerEventMgr, in order to make it possible for a user to verify proper suspend mode operations:
After waking a device from sleep (here: after ~10 hours), both duration values "Screen off" and "Last suspend" should be close to identical. It is OK for the two values to be roughly 60 seconds apart, like in the image above. This means that the tablet went into suspend mode ~60 seconds *after* the screen was switched off. And that the tablet did not wake up once during suspend mode. In full suspend mode, the battery will discharge 0.4% to 0.7% per hour (4% to 7% in 10 hours). Recharging back to 100% should be possible in about 20 - 25 minutes.
None of the core "charging while in host mode" code has been touched in the last couple of weeks.
New posts
-
Development [ROM][13][OFFICIAL] Evolution X - Poco X3 Pro [vayu]- Latest: elizabethangelalorenza
-
