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
Related
Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Also where do I download the following Flashable zips: (there is no dowload link)
Update 5/4/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL
Update 3/26/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL / MIUI GB & ICS
Update 3/6/12 Flashable zip for Mirage CM7.2 / ICS CM9
Update 3/2/12 Flashable zip for Mirage CM7.2 / ICS CM9 / MIUI v2.2.24
ZueKary said:
Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Click to expand...
Click to collapse
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
RASTAVIPER said:
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
Click to expand...
Click to collapse
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
ZueKary said:
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
Click to expand...
Click to collapse
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
RASTAVIPER said:
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thank you
Thanks (& battery drain issue)
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
pandachilli said:
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
Click to expand...
Click to collapse
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
battery issues [PARTIAL FIXES]
ZueKary said:
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
Click to expand...
Click to collapse
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
pandachilli said:
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Click to expand...
Click to collapse
ZueKary said:
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
Click to expand...
Click to collapse
Interesting - if possible let us know how it goes. I'm keen to find a nice stable build, Cm7/CM9 seems like the "best of both" however, if I find out Cm7.2 has a healthier battery experience, I'm likely to switch, or prep an alternative sd just in case!
I'll update back here if I find anything more re: battery on ROM
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
ingdebso England
RASTAVIPER said:
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
RASTAVIPER said:
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wish you had posted that before. I installed 7.2 (stable) according to this link: http://taosaur.blogspot.com/2011/09/running-cyanogenmod-7-from-sd-nook.html which is suppose to be based on this post: http://forum.xda-developers.com/show....php?t=1000957 with a newer image file. I did this on Friday and so far everything works wonderfully. Battery life is excellent. I think even better that when I was using the Stock and I have NOT installed any kind of battery saving app.
The only problem I keep having, which I also had with the previous installation is the status bar disappearing randomly. I get an error message "the application statusbar (process com.android.systemui) has stopped unexpectedly)". The only suggestion I have found is to wipe the card which did wipe before installing this version using "EaseUS Partition Master 9.1.1". If you have any suggestion on how to fix that issue I would feel very happy with the performance I have.
Even a tip on how to reopen the status bar without rebooting will be greatly appreciated.
pandachilli said:
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
Click to expand...
Click to collapse
My current installation is wonderful with battery life. If I can get a fix for the "the application statusbar (process com.android.systemui) has stopped unexpectedly)" error. It will be the closest to perfection I have tested so far and I had tested 3 different installations so far plus I used the stock for nearly a year.
I found the following recommendation in the link posted by RASTAVIPER (thank you!). I'm giving it a try right now. Will report tomorrow how it is working after unchecking "disable full screen".
Recommendations:
1) Regarding the status/notification bar force close issues, I recommend unchecking the "disable full screen" option in the Tablet Tweaks to avoid the status bar crashes. This also improves the app behavior especially movies and games that need full screen.
Click to expand...
Click to collapse
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
ZueKary said:
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
Click to expand...
Click to collapse
Great news - thanks for feeding back.. so you're using "[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards." ??
RE: battery - no drainage during sleep, random power off's etc?
Going to wipe my SD and start again this evening BUT...can't decide between your recommend ROM or RastsVipers's suggestion of "CM7, Mirage"
Confused.
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
satya-1998 said:
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
Click to expand...
Click to collapse
I like the handy tip of removing the phone.apk
Now can you tell me where is that thank you button? (Never mind. I found it )
My phone shuts down on 4.3 and 4.4 based roms.
It happens much less often on 4.2 and stock based roms.
It seems to happen when the screen is off. It doesn't shut down when I'm in the middle of doing something. I've seen that on other phones.
If the screen is off, but I'm listening to the music player or Pandora, it does not shut down.
It does not seem to be overheating.
I'm on my 3rd sim card in 2 months and my second class 4 SD card. I only bought a new one b/c used the one from my old phone and thought it was best to start fresh.
Currently I'm running the first CM11, but this has been happening on CM 10.2, AOKP, and a variety of other roms.
My recovery is TWRP 2.6.3.0
I use the regular GAPPS, not PaGAPPS and the appropriate GAPPS for the given AOSP base; 4.2/3/4
I flash SuperSu-v1.65 after a full wipe when installing new roms.
The current apps I have installed in addition to what comes with CM are:
Evernote
Freecell
Google Voice
gReader Pro
Pandora
Quickoffice
Rom Toolbox Pro
Scanner Radio
Shuttle+
SMS Backup+Restore
Solitaire
Tapatalk Pro
UPM - Universal Password Manager
Xposed Installer - I don't have any modules installed at the moment and the last time today it shut down by itself was before I installed Xposed.
I know that logcats are good for tracking down errors for apps that FC, though I don't know yet how to read logs.
Is there an app I can use that can show me activity before the last shutdown?
How can I track down what's causing it?
TIA
please delete
On 2nd thought I did not feel I could contribute well.
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
aviwdoowks said:
please delete
On 2nd thought I did not feel I could contribute well.
Click to expand...
Click to collapse
Thanks for trying though.
ATTACK said:
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
Click to expand...
Click to collapse
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
FirePsych said:
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
Click to expand...
Click to collapse
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Thanks,
I had read that the SOD had been reported elsewhere, but never saw any solutions. Just lots of folks replacing their phones.
I haven't had one in the last 24 hrs on the 12/08 CM nightly and flashed the 12/09 this morning.
I also made the MPdecisions change. We'll see if it sticks. I assume since it's a system file, I'll have to make the change every time I flash a new nightly or or new rom, but that's not a big deal.
Oh, and yes SOD is probably more accurate than "shutdown" because I've noticed that the led will flash if I've received a message, but I can't revive the phone, so obviously it's not complete shut down.
ATTACK said:
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Click to expand...
Click to collapse
@ATTACK.
Thank you!
I hate to jynx myself, butthis seems to have done the trick. Only had 1 or 2 BSOD since your response and I think both times were because I forgot to make the change after flashing a new rom.
Happy Holidays
FP
This thread may have saved my phone. I keep waking up to find my phone with a blinking LED notification and me being unable to get the screen to turn on. I renamed the MPdecision file and I'll hope for the best. (^^)
DOWNGRADING TO LOLLIPOP:: --- B151 from B331
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
----
THX @skeppley
THX @Demian3112
----
Figured the above was an important surprise for some of you... OP still valid
Hello Everyone! Im new to the whole Honor 5x thing, coming from an m8 now, and before that a nexus 6, and before that a z3 then before that an S4 and before that an HTC Evo 4G LTE... Along with some minors, LG Risio, Moto E, S5...
Im just happy to say that so far I really enjoy this phone! Within the first few days of using it on Lolipop, i was getting 1d 15h type battery life which if youve looked at the phones ive mentioned so far... Really..really..wasnt what I was used to. A Day? For sure, the htc would be at 18% getting back on the charger... and it would die at 10%... with how long id had it. But... A Day was doable.
Ive been looking for a phone for SOOooOOO long now that had good enough battery to last a day at max brightness... Tweaking kernels, and Installing various ROMS (all of them per device)... Crack Flashing, as some would say. It just became a hobby... Ive noticed many weird things about the community, to those reading... let me list them now...
1. People all of the sudden(within the last 2 years?) prefer stock android over anything, regardless of what additional features are being added... Such as battery life improvements, Multitasking improvements, theme improvements, usability improvements... People like stock android... hmmm?
2. People want to be nexus so bad they will theme other UI's to death, just to make it look like stock, generic android... hmm..
3. Battery life, while a common complaint, seems to be indifferent to how frequently people update their phones.. (note: Marshmellow EMUI has a multi core battery bug, listed on XDA under mods..) or what ROM they choose (note the most popular rom being one with significantly worse battery life than stock)
4. Security improvements are completely unnecessary to the community (note the most popular rom being one that hardly supports the fingerprint sensor)
5. No matter how many bugs (even those listed in OP) people will always flock to the latest update of android. And then subtly complain to the developer about the bugs they already know about..
Such a strange mixture of people...to be sure.
However what ive noticed here, is a complete lack of readily available information, so i am hoping some of you might be able to assist me.
TL;DR
So I succeeded in downgrading my phone from MM to LP, as the battery life thing is a legit problem for me, as much as it may not be for other people. However the fingerprint sensor has been disabled, and no longer exists in the settings list... nor is it part of the startup. (confusing to be sure, you would think it would be there, and just FC when clicking on it were there to be a bug, or if the OS didnt detect the sensor or something... it should still be there yeah? If i understand how it works...
Also I cant seem to flash a B151 rom at all, being on B33...3? <- marshmellow... and im assuming at this point that means i wasnt supposed to be able to downgrade... (oops)
So i got TWRP installed (whats up with all the random errors twrp is throwing? Assuming thats normal...?) and am awaiting a BMarshmellow rom to finish... Which leads me to...
Where are the Emui ROMS? Unless its closed... but if this rom maker can do it... ?
and also, is the fix to the battery life on marshmello noticable to those of you who also care about battery life at all?
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Demian3112 said:
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Click to expand...
Click to collapse
Well there is a fix for it in the mods section that fixes battery. Finally got this phone back to functional lol..
Anyway, the fix for the moment anyway looks like it works, just has to be redone every reboot but really isn't that hard. After applying mincores mincpu 0 the big cores only light up when necessary. So far its helping a lot with battery life at least noticeably. Listented to music the whole way to work this morning and was still at 97% when I got there (I have an hour drive) , and that's using Youtube Music over 4g.. Not too shabby.
Yesterday I got to work doing the same thing on marshmallow at about 85-90 so it is doing something, and watching Kernel Auditor shows the big cores turning off when not in use. Worth checking out, applying the settings that are mentioned there don't do much im afraid, as I cant get them to stick through a reboot yet.
Currently writing an init.d script to make that happen every boot.
For now to my knowledge though it is working. Though I think lollipop was for sure better apps on screen off actually worked properly -_-; which im noticing more and more it doesn't anymore. Its more like a Doze control which is annoying because Doze is not near as good as stock lollipop control. I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know!
TL;DR
I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know! Id much rather downgrade than continue to fix marshmallow.
Though for those of you wondering, Viper|Atmos//Sony Beats the audio mod works perfectly on this phone
Just finished Init.d for Mincpus to fix the whole Big Little problem Super good stuff. Phone now booting in the big little mode you were talking about. super easy stuff.
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
skeppley said:
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
Click to expand...
Click to collapse
U need the firmware had same.. revert though dload
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
You should try CyanogenMod 13: excellent battery life, USB OTG and gyro working, much better CPU & RAM management...
FP reader is working, but you must upgrade to MM first (to update trust zone and radio firmwares).
igotlostintampa said:
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
Click to expand...
Click to collapse
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
Demian3112 said:
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Click to expand...
Click to collapse
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on your bed at night? And then never again?
As for CM13, im fairly apathetic to the topic... Not to be annoying, or rude, but ive heard the excellent battery life claim a million times about stock android, and while ive noticed its improvements over something like...say, Sense, or Touchwiz... Ive never seen it beat the z3's battery saving tool (before marshmallow), or as of the day I got this phone, Huaweis non-debloated lollipop.
Ive never seen a phone still be at 30-40%, at the end of work, the day after the day I charged. Until this phone. The Z3 would make it a little past lunch if I barely used it on day 2, but this phone played pokemon go for 2 hours the day I charged it, I spent the day listening to streaming music, browsing for various small things, watching a few youtube videos, a little navigation... And it had 40% when I left work the next day lol at 100% auto brightness. Id love to see some screen on vs idle drain comparisons between this phones CM13 and Stock, at that point, ill believe a battery claim.
It played pokemon go at 60fps and the game is a known battery/gpu hog (s7 plays slower than this phone, likely due to lack of gyroscope?)
other than some various laggy UI glitches, the phone was pretty much what id been looking for (I Prefer Miui over stock android, this phone is similar)
igotlostintampa said:
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on yuur bed at night? And then never again?
Click to expand...
Click to collapse
What buildnumber and Custom version/Cust do you have? Might be able to link you the right firmware.. twrp backup doesnt backup firmware that explains that you dont have a finger print, is the H from Honor at boot logo Red also?
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
skeppley said:
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
Click to expand...
Click to collapse
Your Reply has been added to the OP for those concerned with Downgrading. Figured it might be nice to stumble upon the directions that, after reading many posts throughout the various roms, many people might actually be looking for. Will likely try this tonight when I get home, battery is much better with the battery fix, but not as good as lolipop
Great.
Hope to help others that were stuck the same way
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Demian3112 said:
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Click to expand...
Click to collapse
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
igotlostintampa said:
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
Click to expand...
Click to collapse
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Demian3112 said:
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Click to expand...
Click to collapse
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
igotlostintampa said:
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
Click to expand...
Click to collapse
Im using Force doze app.. U can whitelist apps and as soon as you turnoff your screen it starts doze... You wont get notifications from apps you didnt whitelist until you turn it back on
Good afternoon,
So after seeing a bunch of videos and out of boredom I ordered almost all the pieces to make the switch. Was amazed by how simple it was until I noticed that the OTG cable was not supported by the Nexus 7? And that to my understanding I would have to root and install a custom rom in order to do this?
Well I did some research and found timurs rom and installed it. Well noticed gapps wasn't installed. Went to install gapps then I spent an entire Saturday trying to get it to work with no avail. I'm not skilled in this line of work. Alot of the articles I'm finding are from 2012 -14.
Just wanna make sure I'm making the right steps not sure if there has been a new way of doing this or possibly an easier method? Would greatly appreciate it if someone could assist with this.
I would love to have GAPPS on which ever ROM will give me the requirements to install the Nexus as my head unit. Im just not entirely sure how to get it to work proplery. I apologize for my lack of knowledge in advance.
List of parts
-nexus 7 (wifi)
-radio harness
-otg
-usb hub
-dac (behringer UCA222)
As well as some other misc items such has a volume knob, just awaiting the Amplifier.
Thank you for your time, hopefully someone can help me with this :good:
So from what I've gathered Autodroid is the newest rom, just downloaded it. Will be giving it a shot tonight. If someone could help me with Google apps and installing it on there that would be awesome!!!
BlackenWkN7714 said:
So from what I've gathered Autodroid is the newest rom, just downloaded it. Will be giving it a shot tonight. If someone could help me with Google apps and installing it on there that would be awesome!!!
Click to expand...
Click to collapse
For Autodroid, look for Slim-Addons-mini_gapps.4.4.4.build.9-20150107.zip from Here.
I had issues with OTG+Charging with Autodroid, but the more i have been tweaking and trying different things, I think the high temperatures were what caused the tablet not to charge. Monitoring the battery, I have noticed when the temp is over say 110* F, it will not charge, but will hold the charge and not drain the battery. The lower the temp gets the faster it starts charging.
I would suggest not converting to F2FS if you plan to use OTG. I could not get it to work properly.
I'm currently running LineageOS 14.1 with Powereventmanager 1.8 installed. This has been working well for me the last week or so, but some issues have me wanting to go back to Autodroid. One issue i've noticed lately with LineageOS is the sound quality doesn't seem as good as Autodroid. It sounds decent for my factory system, but what bugs me is the volume control is not sensitive enough, its either way too loud or too quiet. There may be ways to fix this though, as i have not had time to research a fix. I dont run a DAC, I run my tablet via bluetooth to a headunit hid behind the tablet, so you may not have this issue.
Another issue i have is with PowerEventManager. It will put the tablet to deep sleep, but usually not the first time i turn the ignition off. I have to turn the ignition back on then off, then it will trigger powereventmanger. No big deal, but is a pain since i have to constantly make sure it does go to sleep.
You can also add the volume control buttons to the nav bar through the "buttons" setting. You can add media controls too. This works well for the most part, but there are times the icons disappear, though the control is still functional. I think this issue is caused by my icon size, but not 100% sure.
B|acknd said:
For Autodroid, look for Slim-Addons-mini_gapps.4.4.4.build.9-20150107.zip from Here.
I had issues with OTG+Charging with Autodroid, but the more i have been tweaking and trying different things, I think the high temperatures were what caused the tablet not to charge. Monitoring the battery, I have noticed when the temp is over say 110* F, it will not charge, but will hold the charge and not drain the battery. The lower the temp gets the faster it starts charging.
I would suggest not converting to F2FS if you plan to use OTG. I could not get it to work properly.
I'm currently running LineageOS 14.1 with Powereventmanager 1.8 installed. This has been working well for me the last week or so, but some issues have me wanting to go back to Autodroid. One issue i've noticed lately with LineageOS is the sound quality doesn't seem as good as Autodroid. It sounds decent for my factory system, but what bugs me is the volume control is not sensitive enough, its either way too loud or too quiet. There may be ways to fix this though, as i have not had time to research a fix. I dont run a DAC, I run my tablet via bluetooth to a headunit hid behind the tablet, so you may not have this issue.
Another issue i have is with PowerEventManager. It will put the tablet to deep sleep, but usually not the first time i turn the ignition off. I have to turn the ignition back on then off, then it will trigger powereventmanger. No big deal, but is a pain since i have to constantly make sure it does go to sleep.
You can also add the volume control buttons to the nav bar through the "buttons" setting. You can add media controls too. This works well for the most part, but there are times the icons disappear, though the control is still functional. I think this issue is caused by my icon size, but not 100% sure.
Click to expand...
Click to collapse
Hey thanks for the response!!
I ended up getting timurs rom to work. I attempted to go with Autodroid but it would never load up. Attempted timurs rom and it worked and figured I'd try gapps and finally it worked perfect and I have no issues now.
Now I'm trying to find the best method to incorporate Bluetooth to the car. I'm replacing my entire head unit with the tablet. I wanna be able to play music from my phone and have it come out of the cars speakers.
Any suggestion on that?
BlackenWkN7714 said:
Hey thanks for the response!!
I ended up getting timurs rom to work. I attempted to go with Autodroid but it would never load up. Attempted timurs rom and it worked and figured I'd try gapps and finally it worked perfect and I have no issues now.
Now I'm trying to find the best method to incorporate Bluetooth to the car. I'm replacing my entire head unit with the tablet. I wanna be able to play music from my phone and have it come out of the cars speakers.
Any suggestion on that?
Click to expand...
Click to collapse
Autodroid, you have to flash the kangaroo kernel after you flash the rom. there are people that say you have to flash a version of SlimKat and dirty flash Autodroid over it, but i never had to do this.
Check out HeadUnit Reloaded. it is an Android Auto clone. allows you to make a receive calls, stream music from your phone. There is a 5 minute trial, so make sure you have everything set up before you give it a try.
I've been debating on switching to a DAC, just so i can have better volume control. Something about using software buttons for control is just a pain. I've also thought of hard wiring my removable face from the head unit to somewhere it is accessible, but not sure i want to go through the trouble.
Have you thought of just using the phone as a hotspot and using your tablet for everything else? This is what i do and it saves me from having to fidget with my phone all the time.
Another tip for you, though i dont know what DPI Timurs rom is set at, but on AutoDroid I always increased the DPI to make things on screen larger and easier to control, since it is in a vehicle. I believe i had mine set at 230..
I'll be switching back to Autodroid this evening. the bugs i encounter using LineageOS have just been too much to deal with. Worked great for awhile, just need something more stable and worry free.
B|acknd said:
Autodroid, you have to flash the kangaroo kernel after you flash the rom. there are people that say you have to flash a version of SlimKat and dirty flash Autodroid over it, but i never had to do this.
Check out HeadUnit Reloaded. it is an Android Auto clone. allows you to make a receive calls, stream music from your phone. There is a 5 minute trial, so make sure you have everything set up before you give it a try.
I've been debating on switching to a DAC, just so i can have better volume control. Something about using software buttons for control is just a pain. I've also thought of hard wiring my removable face from the head unit to somewhere it is accessible, but not sure i want to go through the trouble.
Have you thought of just using the phone as a hotspot and using your tablet for everything else? This is what i do and it saves me from having to fidget with my phone all the time.
Another tip for you, though i dont know what DPI Timurs rom is set at, but on AutoDroid I always increased the DPI to make things on screen larger and easier to control, since it is in a vehicle. I believe i had mine set at 230..
I'll be switching back to Autodroid this evening. the bugs i encounter using LineageOS have just been too much to deal with. Worked great for awhile, just need something more stable and worry free.
Click to expand...
Click to collapse
I have thought about being able to supply a hot spot with my note 5. I found ways of getting around it without rooting it but those have seemed to be disabled. Still hoping to come across a simple way of doing it without paying for it or rooting the phone since I'm currently on the "lease program". I plan to keep the phone once I'm finished paying on it so I believe I should have an issue. I just don't wanna end up screwed if for some reason I have to turn it in and I get hit with a large fee since it's rooted.
I will definitely look into that app, can it be connected thru Bluetooth or just wifi? If wifi I will have to wait until I figure out how to make my phone wifi tethering enabled.
Also I though of an idea, I have found the Bluetooth devices for everyday car stereos. Box with usb to charge and an aux to plug into the car audio. My Dac has an input and an output. I'm currently not using the input since it's all thru usb. I'm wondering if I can hook up the $20 Bluetooth piece and then aquire a female 3.5 aux cable to make rca and hook that up to the input on the dac.
BlackenWkN7714 said:
I have thought about being able to supply a hot spot with my note 5. I found ways of getting around it without rooting it but those have seemed to be disabled. Still hoping to come across a simple way of doing it without paying for it or rooting the phone since I'm currently on the "lease program". I plan to keep the phone once I'm finished paying on it so I believe I should have an issue. I just don't wanna end up screwed if for some reason I have to turn it in and I get hit with a large fee since it's rooted.
I will definitely look into that app, can it be connected thru Bluetooth or just wifi? If wifi I will have to wait until I figure out how to make my phone wifi tethering enabled.
Also I though of an idea, I have found the Bluetooth devices for everyday car stereos. Box with usb to charge and an aux to plug into the car audio. My Dac has an input and an output. I'm currently not using the input since it's all thru usb. I'm wondering if I can hook up the $20 Bluetooth piece and then aquire a female 3.5 aux cable to make rca and hook that up to the input on the dac.
Click to expand...
Click to collapse
I'm not sure about Bluetooth with Headunit reloaded... you can use USB. To be able to make and receive calls, you have to have it connected to a "Bluetooth headset" according to their page, but i think this is just for phone calls.. I could be wrong though. I've been curious if my head unit would act as a "headset" since my tablet is connected through Bluetooth...
One day I will buy the app and play with it more, I'm just cheap
About your DAC, I dont see why that wouldn't work. I've read of people using stand alone Bluetooth adapters with their DAC. But like i said before I dont know anything first hand when it comes to DAC's.
Hello everyone,
As Android 10 and above seem to be a bit sluggish for this device, I decided to make an Android 9 LineageOS 16.0 build for my soon 9 year old SM-T800 tablet. It seems to be much smoother and stable then Android 10 and even while doing heavy web browsing, watching YouTube in 1080p or using Google Maps navigation in satellite mode, nothing crashed for me. The only issue I found is that the tablet gets a bit hot when actively using it. To sorta mitigate the issue, I recommend rooting the device, installing a kernel manager and limiting the CPU frequency to 1700MHz (where default is 1900MHz). The ROM itself has been very stable to use, only camera video recording and fingerprint scanner are not working as of now.
What works?
Boot
Wi-Fi
Bluetooth
Front and back cameras (photos only)
Video playback
Audio
Sensors
Flash
GPS
Microphone
What doesn't work?
Video recording in camera
Fingerprint scanner
Bluetooth is randomly hanging up when connecting peripherals
Offline charging
You tell me the rest
This build is SELinux Permissive!
Flashing instructions (clean flash):
Ensure you're on the latest Marshmallow firmware for your tablet
Use LATEST OFFICIAL TWRP, or LineageOS recovery (attached with the ROM)
Wipe Data and System partitions from recovery
Flash ROM zip from internal storage, SD Card, USB OTG or ADB sideload
Flash GApps (optional, my recommendation is OpenGApps 9.0 arm pico or nano)
Flash Magisk (optional)
Reboot and voila!
Otherwise, this ROM is good for users who wants better smoothness and stability and doesn't want to downgrade all the way down to Android 7.1.
If anyone wants a build for a model different than chagallwifi, tag me and I can try to build (You'll have to test it yourself!).
Get the builds from here:
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Sources:
AOSP: https://source.android.com/ (the base for everything)
LineageOS: https://github.com/LineageOS (the ROM)
Exynos5420: https://github.com/exynos5420 (Device, kernel and vendor sources)
Screenshots attached below
Screenshots of the build:
Do you plan on fixing the fingerprint sensor anytime soon? I use it on the LineageOS 17.1 build pretty often
Penguin76 said:
Hello everyone,
As Android 10 and above seem to be a bit sluggish for this device, I decided to make an Android 9 LineageOS 16.0 build for my soon 9 year old SM-T800 tablet. It seems to be much smoother and stable then Android 10 and even while doing heavy web browsing, watching YouTube in 1080p or using Google Maps navigation in satellite mode, nothing crashed for me. The only issue I found is that the tablet gets a bit hot when actively using it. To sorta mitigate the issue, I recommend rooting the device, installing a kernel manager and limiting the CPU frequency to 1700MHz (where default is 1900MHz). The ROM itself has been very stable to use, only camera video recording and fingerprint scanner are not working as of now.
What works?
Boot
Wi-Fi
Bluetooth
Front and back cameras (photos only)
Video playback
Audio
Sensors
Flash
GPS
Microphone
What doesn't work?
Video recording in camera
Fingerprint scanner
You tell me the rest
This build is SELinux Permissive!
Flashing instructions (clean flash):
Ensure you're on the latest Marshmallow firmware for your tablet
Use LATEST OFFICIAL TWRP, or LineageOS recovery (attached with the ROM)
Wipe Data and System partitions from recovery
Flash ROM zip from internal storage, SD Card, USB OTG or ADB sideload
Flash GApps (optional, my recommendation is OpenGApps 9.0 arm pico or nano)
Flash Magisk (optional)
Reboot and voila!
Otherwise, this ROM is good for users who wants better smoothness and stability and doesn't want to downgrade all the way down to Android 7.1.
If anyone wants a build for a model different than chagallwifi, tag me and I can try to build (You'll have to test it yourself!).
Get the builds from here:
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Sources:
AOSP: https://source.android.com/ (the base for everything)
LineageOS: https://github.com/LineageOS (the ROM)
Exynos5420: https://github.com/exynos5420 (Device, kernel and vendor sources)
Screenshots attached below
Click to expand...
Click to collapse
For cpu temperatures/speed limits,
Which cpu govenor in the kernel did you use?
You could build a version with the kernel limiting to 1700Mhz so people need to mess around with root.
I recommend upgrading the thermal pads inside the tablet as well
bluess57 said:
For cpu temperatures/speed limits,
Which cpu govenor in the kernel did you use?
You could build a version with the kernel limiting to 1700Mhz so people need to mess around with root.
I recommend upgrading the thermal pads inside the tablet as well
Click to expand...
Click to collapse
The current governor I used is schedutil, I'll try setting it to interactive and limiting the CPU frequency next build
Zakaria2328 said:
Do you plan on fixing the fingerprint sensor anytime soon? I use it on the LineageOS 17.1 build pretty often
Click to expand...
Click to collapse
I currently can't find the cause of the sensor not working. It reaches the fingerprint setup successfully, but holding or sliding my finger on the home button doesn't seem to do anything.
Hi Just a quick question.. my understanding is that android 9 does not support dark mode, that your screenshot almost seem to suggest that it does.
my reason for asking is that I am visually impaired, and really can't read anything on a white background. anyway just wanted clarification before I try out this rom.
Cheers
Quidam67 said:
Hi Just a quick question.. my understanding is that android 9 does not support dark mode, that your screenshot almost seem to suggest that it does.
my reason for asking is that I am visually impaired, and really can't read anything on a white background. anyway just wanted clarification before I try out this rom.
Cheers
Click to expand...
Click to collapse
Hi! Android 9 has a partial dark mode. The built in system apps as well as the system UI is dark, but third party apps do not support this dark theme and are light by the default. Many third party apps can be manually set to dark theme.
Penguin76 said:
Hi! Android 9 has a partial dark mode. The built in system apps as well as the system UI is dark, but third party apps do not support this dark theme and are light by the default. Many third party apps can be manually set to dark theme.
Click to expand...
Click to collapse
thanks, I think I'll give it a crack, i'm using the latest Lineage 20 build from another thread and to be honest it's super buggy lol. If this doesn't work out I can always go back to the 17.1 build which was actually pretty stable, but as you point out it's a bit on the sluggish side. Cheers
Or you might try unofficial LineageOS 18.1 (A11) which perfectly supports dark theme. I'm running it on my SM-T805 without any problems.
Cheers
Toscha
The problem
toscha42 said:
Or you might try unofficial LineageOS 18.1 (A11) which perfectly supports dark theme. I'm running it on my SM-T805 without any problems.
Cheers
Toscha
Click to expand...
Click to collapse
The problem I found with A10+ ROMs is that some slightly graphics heavier apps or even Google Maps in the browser can crash itself or even lock up the tablet completely.
For those graphics apps I can't tell. But Google Maps I use a lot and it's absolutely stable.
Cheers
Toscha
toscha42 said:
For those graphics apps I can't tell. But Google Maps I use a lot and it's absolutely stable.
Cheers
Toscha
Click to expand...
Click to collapse
The app itself works fine, but the Google Maps website will likely crash when it's opened in a browser when starting to navigate around the map. And there are many other websites that do crash the browser as well.
Penguin76 said:
The problem
The problem I found with A10+ ROMs is that some slightly graphics heavier apps or even Google Maps in the browser can crash itself or even lock up the tablet completely.
Click to expand...
Click to collapse
Watching youtube works fine, as that's all i do with this tablet now, other than checking my email. Setting up the e-mail did freeze the tablet a couple of times
hello,
So I tried out this rom and wanted to report back my findings.
I found it to be both stable and fast, but there were a few issues, which has led me back to 17.1 LuisROM which given my particular needs really does seem to be the best option. I have actually tried both18 and 20, but neither of them are as stable as17.1, at least based on the particular set of apps I use.
Anyway, the issues I had were:
1) the partial dark mode support was certainly not bad, but given the fact that apps don't follow the system theme, and I could find no way of setting the Google app to dark mode, it was less than ideal. this is no fault of the build at all It's just a limitation of being Android 9, and I imagine for most people it would not be an issue nor a reason not to use this ROM
2) I had a weird issue when I shut the tablet down and plugged it in to power source. The battery icon showed and and then the tablet froze up, so that if I disconnected it from the power source the battery icon still continued to display and the only way to boot it back up was to press and hold the home key, volume down and power. this would seem to suggest there is an issue with the Kernal/ boot loader.
3) I have the official Samsung case with built-in keyboard, but there appeared to be a problem with bluetooth and I simply could not get it to connect. this was the deciding factor like to go back to 17.1
Cheers
b
.
Do you have a link to LineageOS 18.1 705
Quidam67 said:
hello,
So I tried out this rom and wanted to report back my findings.
I found it to be both stable and fast, but there were a few issues, which has led me back to 17.1 LuisROM which given my particular needs really does seem to be the best option. I have actually tried both18 and 20, but neither of them are as stable as17.1, at least based on the particular set of apps I use.
Anyway, the issues I had were:
1) the partial dark mode support was certainly not bad, but given the fact that apps don't follow the system theme, and I could find no way of setting the Google app to dark mode, it was less than ideal. this is no fault of the build at all It's just a limitation of being Android 9, and I imagine for most people it would not be an issue nor a reason not to use this ROM
2) I had a weird issue when I shut the tablet down and plugged it in to power source. The battery icon showed and and then the tablet froze up, so that if I disconnected it from the power source the battery icon still continued to display and the only way to boot it back up was to press and hold the home key, volume down and power. this would seem to suggest there is an issue with the Kernal/ boot loader.
3) I have the official Samsung case with built-in keyboard, but there appeared to be a problem with bluetooth and I simply could not get it to connect. this was the deciding factor like to go back to 17.1
Cheers
b
.
Click to expand...
Click to collapse
Hello, I'm sorry for the issues you experienced with the ROM. I checked both of the issues and the offline charging issue seems to be there for me too. As you mentioned, it might be related to kernel, but I sadly can't find the actual cause of it as I'm still pretty new new to the world of Android development and I'm still learning how everything works. The Bluetooth issue is something I have now experienced as well. I tried connecting a pair of BT earbuds and they seem to be stuck at connecting at the Bluetooth page in settings. For now I'll update the known issues with those two bugs and maybe one day I'll find out what causes them. And by the way, since you now installed Android 10 on your tablet, how is it for browsing sites? Do sites crash often? Since this is the main thing I use the tablet for (and occasionally watching YouTube and navigation in the car).
Cheers
Penguin76
Penguin76 said:
Hello, I'm sorry for the issues you experienced with the ROM. I checked both of the issues and the offline charging issue seems to be there for me too. As you mentioned, it might be related to kernel, but I sadly can't find the actual cause of it as I'm still pretty new new to the world of Android development and I'm still learning how everything works. The Bluetooth issue is something I have now experienced as well. I tried connecting a pair of BT earbuds and they seem to be stuck at connecting at the Bluetooth page in settings. For now I'll update the known issues with those two bugs and maybe one day I'll find out what causes them. And by the way, since you now installed Android 10 on your tablet, how is it for browsing sites? Do sites crash often? Since this is the main thing I use the tablet for (and occasionally watching YouTube and navigation in the car).
Cheers
Penguin76
Click to expand...
Click to collapse
Klimtwifi build?
Penguin76 said:
Hello, I'm sorry for the issues you experienced with the ROM. I checked both of the issues and the offline charging issue seems to be there for me too. As you mentioned, it might be related to kernel, but I sadly can't find the actual cause of it as I'm still pretty new new to the world of Android development and I'm still learning how everything works. The Bluetooth issue is something I have now experienced as well. I tried connecting a pair of BT earbuds and they seem to be stuck at connecting at the Bluetooth page in settings. For now I'll update the known issues with those two bugs and maybe one day I'll find out what causes them. And by the way, since you now installed Android 10 on your tablet, how is it for browsing sites? Do sites crash often? Since this is the main thing I use the tablet for (and occasionally watching YouTube and navigation in the car).
Cheers
Penguin76
Click to expand...
Click to collapse
Hey there,
I wouldn't exactly call myself a power user, but I have not suffered a single website crash on the particular build I am using, Which I believe was created by a very knowledge Developer last year. It might be worth noting that I use Samsung Internet browser, Which in my opinion offers by far the best overall experience, Including a flawless dark mode option that seems to work for every website.
One thing I will mention about the spilled is that the developer seems to have gone AWOL and the download link to his builds no longer works. That said, I have a copy of the build on my google drive, download link SM-T800 Lineage 17.1
Give it a spin and see what you think, Overall I'm very happy with its stability and performance. Because of my visual impairment I mostly use audio based apps, such as Google Podcast, Audible, Poweranp Pro, But I also occasionally use Newpipe and VLC player and again, have not had any issues.
PS Good on you for creating your own build, I almost considered trying to do it myself but it's just too much to take on considering I can hardly see the screen lol
LuckyTheCoder said:
Klimtwifi build?
Click to expand...
Click to collapse
I can try to do a build for klimtwifi today