Database Users

[q] a few questions (battery, missing market, fc youtube)

sorry if some of these questions have already been asked and answered. unfortunantely, my computer crashed due to a manufacturing flaw so I can only access google and this forum via my epic (which can be a pain sometimes). also, since heros threads are always deleted, I cannot ask these questions there. please, any feedback and help would greatly appreciated.
okay so I reflashed backed snack 1.6 w/ ultimate after testing some of the newest froyo builds. id rather wat until I get the official ota upgrade.
after reflashing 1.6 for some reason, android market doesn't appear to be installed. where can I download the application? I even tried reflashing 1.6 over itself but that didn't work.
also, I'm using the new gingerbread youtube but I signed in and now I get a constant fc when I try to open it. how can I fix this? if I can't, where can I download an earlier version of youtube?
another question. this time about battery. using 1.6 w/ ultimate, I get fairly decent battery. only problem is, my battery stats say that my display and standby are what is killing my battery the most. nothing ever runs in the background, every so often I unlock my phone to either check the time or texts or facebook real quick, brightness is on its lowest setting, silent mode, juicedefender running correctly (battery life: x1.56), no data running in the background, drm killed, battery calibrated and battery stats wiped, and everything else possible to to save battery.
and something I'm noticing now that the phone is charging, the battery is quite hot and I'm not even using the phone. it only overheats when its charging and I've also noticed that its only hot when I use certain roms/kernels. any insight on this issue? any way to monitor and regulate temperature?
once again, any help would be appreciated!
Sent through the Matrix

Ill take a stab at these. Reason for you market not showing, can't say? Did you wipe 3 times before flashing bs 1.6?
Also never sign in on gingerbread youtube on 2.1 build. I don't think anyone has got that working yet. Simply clear the cache for youtube and you should be set.
Lastly, I don't know what to say about your bettery.. what do you have setcpu running at? Do you have profiles to lower your phones speed when in standby? Couldn't hurt to give it a shot.
Sorry about your computer, all my info is based on personal experience don't really have a "dev" type answer for ya. But hope some of this helps.
Goodluck!
Sent from my SPH-D700 using XDA App

skelit0r said:
Ill take a stab at these. Reason for you market not showing, can't say? Did you wipe 3 times before flashing bs 1.6?
Also never sign in on gingerbread youtube on 2.1 build. I don't think anyone has got that working yet. Simply clear the cache for youtube and you should be set.
Lastly, I don't know what to say about your bettery.. what do you have setcpu running at? Do you have profiles to lower your phones speed when in standby? Couldn't hurt to give it a shot.
Sorry about your computer, all my info is based on personal experience don't really have a "dev" type answer for ya. But hope some of this helps.
Goodluck!
Click to expand...
Click to collapse
thank you for your reply.
yes I did wipe both data, cache, and davlik 3 times. I guess I will do that now and report back.
how would I go about clearing the cache for one specific app? I know I can do that when I open up my settings and go to app development but youtube doesn't show up in that list.
setpcu is oc at 1300 and uc at 200 conservative. profiles are as follows:
charging/full - 1000 and 200 conservative
battery < 15% - 800 and 400 conservative
screen off - 600 and 400 conservative
yeah, brand new computer too. all of a sudden it couldn't recognize the hard drive. and yes, most of my info is based on personal experience and creeping on forums.
edit: wiped everything 3 times and reflashed. market till not appear.
Sent through the Matrix

For youtube I just open it up without a data connection and step through the process of signing out only enabling data when needed.
If you're missing market then you need to flash back stock with odin then start fresh. Baked doesn't remove market at all. If anything it's the fastest responding market I've used.
Heat from the battery is usually caused by programs requesting cycles or data. Just restart the phone before bed after your initial battery calibration.

nadcicle said:
For youtube I just open it up without a data connection and step through the process of signing out only enabling data when needed.
If you're missing market then you need to flash back stock with odin then start fresh. Baked doesn't remove market at all. If anything it's the fastest responding market I've used.
Heat from the battery is usually caused by programs requesting cycles or data. Just restart the phone before bed after your initial battery calibration.
Click to expand...
Click to collapse
as I stated, I have no computer at the moment. so using odin to go back to stock is out of the question as of now. hopefully there's got to be another way without using odin. if not then I suppose I'm stuck in this predicament until I get my computer back from geek squad. and yes, I've never had a problem with heroes work before. but for some reason, this is happening.
and as I've stated before, no programs or data run in the background on my phone. after initial calibration I rebooted it. and after every boot, I toggle airplane mode on and then off. ill continue to moniter battery temps and see if the problem persists.
Sent through the Matrix

fromchaos0646 said:
as I stated, I have no computer at the moment. so using odin to go back to stock is out of the question as of now. hopefully there's got to be another way without using odin. if not then I suppose I'm stuck in this predicament until I get my computer back from geek squad. and yes, I've never had a problem with heroes work before. but for some reason, this is happening.
and as I've stated before, no programs or data run in the background on my phone. after initial calibration I rebooted it. and after every boot, I toggle airplane mode on and then off. ill continue to moniter battery temps and see if the problem persists.
Sent through the Matrix
Click to expand...
Click to collapse
Sorry bout that, I did read over that you hadn't had a computer. I overlooked it though. It just sounds like you might have somehow of gotten a corrupt install somehow.
Maybe you can try reinstalling 1.6 over top of itself. I don't really see anything wrong with that, but as stated before though. Make sure you wipe cache and dalvichk 3 times each before you do so.

nadcicle said:
Sorry bout that, I did read over that you hadn't had a computer. I overlooked it though. It just sounds like you might have somehow of gotten a corrupt install somehow.
Maybe you can try reinstalling 1.6 over top of itself. I don't really see anything wrong with that, but as stated before though. Make sure you wipe cache and dalvichk 3 times each before you do so.
Click to expand...
Click to collapse
that's okay.
hm that might be what's wrong. ill download it again later. right now, I'm watching two dumbasses snort a line of fire ants on 1000 ways to die. xD (too lazy right now)
Sent through the Matrix

death sleep (doesn't turn on from sleep) - voltage / current issue?

I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.

thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
If I remember correctly, there were a lot of people having this issue with SFR and you shoudl check that thread for more info. However, long story short, this can definitely be related to underclocking and/or undervolting.
Are you using SetCPU to underclock? If so, set your minimum speed to 200 MhZ as I think that resolved it for most people.

ok, set to 200mhz (was at 100mhz) will see if that fixes it. thanks.

I'm having the same issue since flashing Emotionless Beast. Used Voltage Control to set to 200. Is there a way to keep the settings through a reboot?

ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.

thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
Same thing happen to me a few time on twilight but since I'm been on genocide 2.0 kernel no problem for me genocide is the best for my phone
Try it out with jornaling on
Sent from my SPH-D700 using xda premium

I know this might sound stupid, but I had a problem similar to this the other day. It was only the screen was blank, but would still accept inputs on it. I could unlock the phone (using the TW lockscreen) and then, I was able to hold the power key and select reboot (on-screen location pressed from memory).
Is it just the screen, or the entire phone?

thetoady said:
ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.
Click to expand...
Click to collapse
Hmm... Is it also undervolted? Might try changing that. FYI, I have also been using Genocide with no problems for a while now...

Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.

thetoady said:
Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.
Click to expand...
Click to collapse
Try genocide 2.0 kernel & when you use titanium backup don't re install the app &data just install the apps hit the thank you button if I helped you in anyway!
Sent from my SPH-D700 using xda premium

Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's good advice. Didn't UV and OV cause some bricks once? My phone does that death sleep thing when I was at 100 Mhz on Genocide. Set it to 200 and no more problems.

uSo things were a bit more involved.
My phone died totally (major FC avalanch on startup), so I reimaged it, installed genocide and restored from backup (over an hour! w/ data) and its behaving well now.
though I do hate the spam genocide puts in the boot image.

Questions about standby mode

I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?

chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.

All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..

Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!

Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.

Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.

OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.

cool, thanks. I'll try this today.

chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.

[Q] Sleep of death on cm10.1 for NookColor ES1.2?

Hi,
Was wondering if anyone else with a Nook Color sees any SODs on the latest cm10.1 nightlies?
Have tried to read through a fair number of threads, but most of them are concerned with SODs on earlier versions, and no one seems to have talked about having them on cm10.1.
I can't find a way to get a log of when it happens, because it doesn't happen when plugged in, and when it does happen, adb doesn't report any device being attached.
Anyone with a good idea, or who also experiences SODs even now?

cinaeco1 said:
Hi,
Was wondering if anyone else with a Nook Color sees any SODs on the latest cm10.1 nightlies?
Have tried to read through a fair number of threads, but most of them are concerned with SODs on earlier versions, and no one seems to have talked about having them on cm10.1.
I can't find a way to get a log of when it happens, because it doesn't happen when plugged in, and when it does happen, adb doesn't report any device being attached.
Anyone with a good idea, or who also experiences SODs even now?
Click to expand...
Click to collapse
First question: are you overclocking? If you're seeing SODs with the max CPU speed set above 1000 MHz, dial it down to 1000 MHz and see if they still occur. If you're seeing SODs at 1000 MHz, try 800 MHz. (If you're crashing at 1000 MHz, but not at 800 MHz, please let us know ASAP!)

steven676 said:
First question: are you overclocking? If you're seeing SODs with the max CPU speed set above 1000 MHz, dial it down to 1000 MHz and see if they still occur. If you're seeing SODs at 1000 MHz, try 800 MHz. (If you're crashing at 1000 MHz, but not at 800 MHz, please let us know ASAP!)
Click to expand...
Click to collapse
Yeah, I was at 1100MHz.
When I was on 1100MHz, I didn't think it would be the overclock, because SODs would not occur if I had wifi turned off.
I'll see if it still happens at 1000MHz.
So far, on a clean install of the latest nightly, nothing yet. Will see how it goes for the day.
Thanks!

Still happening
Hm.
I've now tried 1000MHz and 800MHz, and I have had SODs on both.
Was a clean install of 20130605.
Formatted system, data and cache before install.
No other settings that I know of changed, other than moving from 1000MHz to 800MHz.
Connected to wifi, signed into to gmail account, so far have only done store update, installed xda app, and KeePassDroid.
Have noticed that when I'm away from my wifi (at work) where it is connected to nothing, it doesn't SOD.
Only SODs after I get back home, perhaps an hour after turning it on to see if it's okay.
Makes me think it's related to that wifi thing mentioned about older firmwares, but wasn't that built in, starting from cm9 or something?
I suppose it's good that it's SODing on both frequencies and not just one?
How should I be trying to get (hopefully) helpful info off this?

cinaeco1 said:
Hm.
I've now tried 1000MHz and 800MHz, and I have had SODs on both.
Was a clean install of 20130605.
Formatted system, data and cache before install.
No other settings that I know of changed, other than moving from 1000MHz to 800MHz.
Connected to wifi, signed into to gmail account, so far have only done store update, installed xda app, and KeePassDroid.
Have noticed that when I'm away from my wifi (at work) where it is connected to nothing, it doesn't SOD.
Only SODs after I get back home, perhaps an hour after turning it on to see if it's okay.
Makes me think it's related to that wifi thing mentioned about older firmwares, but wasn't that built in, starting from cm9 or something?
I suppose it's good that it's SODing on both frequencies and not just one?
How should I be trying to get (hopefully) helpful info off this?
Click to expand...
Click to collapse
Mine does the same thing. Not over clocked and only occurs when WiFi is on and connected. Running cm10.1 rc4. Did the same thing on rc3.

cinaeco1 said:
I suppose it's good that it's SODing on both frequencies and not just one?
Click to expand...
Click to collapse
Welllll ... define "good" -- it means that we can rule out the clock speed as a cause, but it also means we have no other candidate causes that immediately come to mind ...
cinaeco1 said:
Have noticed that when I'm away from my wifi (at work) where it is connected to nothing, it doesn't SOD.
Only SODs after I get back home, perhaps an hour after turning it on to see if it's okay.
Makes me think it's related to that wifi thing mentioned about older firmwares, but wasn't that built in, starting from cm9 or something?
Click to expand...
Click to collapse
Some potentially useful data points to collect:
If you haven't filled out the hardware survey already, please do so.
If you can, please try out a clean install of the April 14 CM10 nightly. (To be clear, I don't expect a difference, but I do want to rule out a couple of things as potential causes.)
Can you connect to the tablet via adb while it's SODing? If so, get dmesg and logcat output from the device while it's doing that. If not, then try this: while the tablet is hooked up to a computer via USB, hold down the power button until it shuts off, turn it on again, and grab the contents of /proc/last_kmsg (if the file exists) and post them. (If there's no /proc/last_kmsg after doing that, let me know.)

Have now done the hardware survey, and will be testing out the cm10 rom.
When SOD happens, I can't get adb to see the device, so yeah, I'll try that which you've mentioned.

CM10 april nightly also SOD'd.
No device found by adb during SOD.
Connected NC to computer with USB cable and forced power off as suggested.
When NC booted, used Terminal to have a look at `/proc`, but didn't see a `last_kmsg` file.
Will flash back to CM10.1 anyway, and see if I can get a `last_kmsg` file

cinaeco1 said:
CM10 april nightly also SOD'd.
No device found by adb during SOD.
Connected NC to computer with USB cable and forced power off as suggested.
When NC booted, used Terminal to have a look at `/proc`, but didn't see a `last_kmsg` file.
Will flash back to CM10.1 anyway, and see if I can get a `last_kmsg` file
Click to expand...
Click to collapse
Hm, very puzzling ... I'm afraid we're sort of operating blind then. Can you try the new wifi firmware I've just put up in the CM10.1 thread and see whether that helps your problem?

Hmm... CM10.1 didn't give me a `last_kmsg` either.
Okay, I shall try the wifi driver a couple of weeks later, after we come back from a trip Thanks!

I still had an SOD on the new wifi driver. Have updated to a later nightly that seems to have this driver built in anyway (think I saw it in the change log?). I'll be half-trying to figure out if there is a pattern to how these SODs are happening... but in the mean time, I guess just using the device as it is.

[Q] What dash installation ROM?

Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated

adamsilver1987 said:
Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
Click to expand...
Click to collapse
I've been running Timur's ROM as well and I really want an alternative as well as I've been facing issues with the ROM, and it looks like Timur has discontinued development on the 2012 model.
From what I've seen so far though CM11 should support USB DACs so I'm keen to try that out.
Some notes:
Fast charge - that's a kernel setting so any custom kernel should allow that.
Sleep/Wake on power - After many months of usage, sleep or even firm sleep has been a hit or miss for me. When it works, it works really well but sometimes a some random app might cause a wakelock, draining the battery. Even otherwise, there are many other issues such as USB audio doesn't resume. Plus the battery tends to drains quicker + looses health because of being in a hot car.
So instead, what I'm planning to do, is to just completely shutdown/boot up a tablet on power. Some notes:
- Bootup time is fairly quick - about 30 seconds, upto a minute, which is acceptable for me. You can reduce the startup time even further by using apps like BootManager to prevent unnecessary apps from starting up. Perhaps we can slim down the ROM further by deleting unnecessary apks etc.
- Fresh start is always a better option - you don't want your tablet to crash while driving right? I've had to reboot many times before or during driving, and it annoys me to say the least.
- USB audio always works fine when booted (well, with Timur's ROM anyways, need to test with CM11/others)
- No battery drain due to device standby or wakelocks
- No overheating and loss of battery health
- For shutdown on power loss, we can use Tasker. Maybe make a script to first turn the screen off, and after say 10 minutes of idle turn off the device completely (this will give us a chance to resume quickly in case we stopped the car for some reason).
- For startup on power, we can use the fastboot oem command to make the device automatically power up
On-Screen Volume: From daily usage, this hasn't been very practical in reality. I mean if you're driving, you really shouldn't be looking at the screen and trying to aim at the tiny buttons. Instead, a better option would be to use gestures to control the volume. There are heaps of apps for this, eg: All In One Gestures, Tasker, Gesture Navigation, GMD GestureControl, etc. You could use a single-swipe down and swipe-up to increase the volume up/down. Swipe left/right to change tracks. Two finger swipes to switch between apps. Just use your imagniation.
Might seem like a lot of work initially, but IMHO it'll be worth it, at least to get a stable ROM which is updated regularly (not to mention, you get to use the newest GApps!).
My only concern is to get the DAC working on startup. Might have to look into Timur's startup scripts to see how he does it - maybe even port the FHD scripts over to 2012 if necessary.

do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks

adamsilver1987 said:
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
Click to expand...
Click to collapse
Kang-aroo kernel.
http://forum.xda-developers.com/showthread.php?t=2558717
Supports fastcharge, OTG, hotplug DAC, firm sleep, multiboot and more.

thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again

adamsilver1987 said:
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
Click to expand...
Click to collapse
Use a kernel tweaking app, like TricksterMod.

ok downloaded that and it means nothing to me im afraid. how would i turn on fast charge for example or OTG host mode, firm sleep etc ?
only thing i can find where i assume you can set things is the " SysCtrl Editor" but it jsut comes up with a huge list of stuff that i have no idea about.
i assume i need to find fast charge in sysctrl and change it from 0 to 1... but cant find anything under the search. not a clue what id be looking for
starting to think Timurs rom was simple compared to this. haha
thanks for the help

Use PowerEventManager:
http://forum.xda-developers.com/showthread.php?p=50265682#post50265682

i saw that, but yet again. dont know how to use it ? where do i place it on the tablet. it doesnt show up in recovery mode

You have to install it. Copy it to your device and then use a file manager to open and install it. It will create an icon in your drawer. When you open it, you'll have options to configure firm-sleep etc.

Done. Worked at first but now I've reverted to timurs rom. The tablet froze loads. Wouldnt open some apps at all and power on/off with ignition wasn't reliable. Sometimes it woke, sometimes it didnt. Will give it another go when i habe more time i think.

On a related note, I haven't had much luck with getting my DAC to work with other ROMs - even with Kang-aroo kernel. I'll have to try CM11 with _crue_'s USB audio patches and Netfluke's kernel this weekend and see how it goes.
Edit: No luck. Maybe because it's I'm on tilapia. Even with cm11, Netfluke's latest kernel, and _crue_'s updated audio patches for cm11, couldn't get it to work. And it's a Fiio E17, which I've had no issues with on Timur's ROM.
And no, I'm not going back to Timur's CM10 - it's old. I can't use any of the newer GApps on it, and the ROM is buggy.
I think I'll swap my tilapia with my 2013 deb and use that as a car device instead. It looks like Timur just updated his kernel to v1.0 which fixes a lot of bugs - at least it's being actively developed. As for my tilapia, I'll switch to a more stable/mainstream ROM like Omni and forget about USB audio for now.

Where did u get timurs updated kernel? Cant find a link

adamsilver1987 said:
Where did u get timurs updated kernel? Cant find a link
Click to expand...
Click to collapse
Oh, you'll have to donate for now, but it should be made public soon.

How much and where?
Thanks