OK I just went from a nightly to a RC CM2 at the bottom of the screen there are what I think are quick launch buttons. On the nightly that I had it only had 3 as opposed to the RC has room for 5 and maybe more. Because there is room for more they are smaller. I'd like to change it back to where only 3 maybe 4 can be used but no more. Can anyone guide me as to where I would go for this set up.
Related
I've been doing the whole in dash tablet thing for a few years now. I've used the nook color, HTC flyer, and other gingerbread based tablets. I bought a Galaxy Tab 2 p3113 and was super stoked about it- but have run into a major obstacle that so far cannot be solved somehow. I've spent months trying to figure this one out with no success.
CM9 or any ICS rom for that matter, at a lcd density of 160 on a 7 inch tablet is uncomfortably small, especially in a car. 240 has always been great in the car on GB roms. But considering the Tab 2 has no hard keys, at 240 the soft keys not showing correctly renders the tablet useless. Market apps like soft keys for root and gesture controls are a joke flying down the highway.
I've read and used some local.prop entries with no success. I'm stuck with either squinting at a screen or jumping through hoops to navigate around it. This seems so easy, yet a Google search brings up next to nothing. All I want is my car tablet to stay in tablet mode above a density higher than 160. Simple right? It was simple to do in ginger bread.
Agreed. I'm in the same boat. I have searched for hours and have come up with nothing.
i never really messed around with cm9 but in aokp(would assume they have some of the same things) u can change the nav bar stuff around have u guys tried any of that?
I'm using CM10 on my OG Galaxy Tab 7, on screen navigation enabled, and LEFT Navigation enabled (240 DPI of course).
Works great.
I bought a Galaxy Tab 2 to do the same setup with, but couldn't get the CM10 Developers to help me get the left navigation going, but it DID work just fine at 240 DPI.
I've been using this setup in my car for a year and a half.
Tablet mode is cute and all, but the bigger navigation in phone mode is better in my opinion. Also, the quick widgets in phone mode are much easier to use while driving in my opinion.
I tried CM10 a week ago or so and had the same problem as CM9 and the buttons messing up. Even when the bar shows to the right, the buttons go from left to right, instead of top and bottom. It is very strange. AOKP did nothing better either.
Since I have the thread open, I've had a few other minor issues that you guys may know something about: I set up Tasker to script wifi/bt/gps/sync on and off with power as well as screen timeout and wake lock on charge. This is to shut down everything with ignition off and wake it all back up with the ignition. For some reason this only works about 80% of the time. It almost seems like a deep sleep or an embeded task killer is destroying the scripts that Tasker is trying to run. There is really no rhyme or reason to it. Tasker just fails sometimes and either I go out to a dead tablet or a tablet that wont stay on.
zavien3 said:
I've been doing the whole in dash tablet thing for a few years now. I've used the nook color, HTC flyer, and other gingerbread based tablets. I bought a Galaxy Tab 2 p3113 and was super stoked about it- but have run into a major obstacle that so far cannot be solved somehow. I've spent months trying to figure this one out with no success.
CM9 or any ICS rom for that matter, at a lcd density of 160 on a 7 inch tablet is uncomfortably small, especially in a car. 240 has always been great in the car on GB roms. But considering the Tab 2 has no hard keys, at 240 the soft keys not showing correctly renders the tablet useless. Market apps like soft keys for root and gesture controls are a joke flying down the highway.
I've read and used some local.prop entries with no success. I'm stuck with either squinting at a screen or jumping through hoops to navigate around it. This seems so easy, yet a Google search brings up next to nothing. All I want is my car tablet to stay in tablet mode above a density higher than 160. Simple right? It was simple to do in ginger bread.
Click to expand...
Click to collapse
I'm looking to get this SGT2 7" to put in my car dash. I'm not clear exactly what the issue is not having one yet, can anyone post screenshots of the issue or how the keys look? Or let me know if this is no longer an issue? I have not looked into various custom ROMs yet, just figuring out if this is going to work for my car at this point.
If your nav buttons are whats giving you trouble, get rid of them and use lmt launcher.
Hi,
I have a Nexus 4 with faux Kernel mako-jb-kernel-005m.zip installed.
Android version is JOP40D stock.
Since I use the stable version of faux kernel 004m I have some problems with my display.
If the screen was looked and I unlook the screen the colors are changed.The contrast is bad and all looks a little bit blue. If I restart my phone all colors are fine. Today morning I started my Phone and the screen won't start fast, first some stripes lighting and after 10 sec the boot screen was shown.
The core clock was min/max 384/918 MHz, GPU max clock was 400 MHz and the core was undervoltet -25mV. All works fine with kernel 003 stable version before.
Now I have reset my kernel to the stock kernel and test if the error came back.
Has anyone the same problem?
I don't know if it is a known bug thus I must send my phone abck to google or is this a software bug?
Sry for writing here, but I cant write inside the defeloper post to the faux kernel before I have written 10 posts.
thx
When you restart your phone, the color is stock settings, after awhile the settings you set in the faux app are accessed and set. You should try the Nexus display spreadsheet for colors you can use if you don't know what you're doing. You might have changed some settings in the app by mistake, but I'm not familiar with your issue but if kernel 003 was working better then just use that one or try the latest kernel 005
You can also try franco kernel, its better IMO and its flash and forget, if you want to get color control you'd have to buy the franco.Kernel updater though
Thanks for the post.
I have never changed my Color settings because I think the stock settings are OK. At the momment I running the stock kernel and all i fine. I will test to switch back to faux_005.
Thanks you are right, one of the last fauxClock updates has changed all shift controlls in the color setting to max (in both presets). I don't know why. I have set alle to factory settings with the table from your link.
thx for help
---- solved ---
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Ethan_Kok said:
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Click to expand...
Click to collapse
I upgraded to the latest stable CM10.1.2 release and have started getting random sleep of deaths (SD install). I've had them while plugged in, not plugged in, with screensaver on, with screensaver off (thought maybe keeping it active would help prevent)... I can't seem to find a pattern. I've tried every nightly since and am still seeing it. I tried rolling back to the first stable release, still there. I'm going to try rolling back from 1100 MHz to 1000, then 800, to see if that helps at all.
I'm a total newb to debugging this thing, but I'm happy to try and pull any logs to post if someone can point me in the right direction (I've looked around before on how to do this but get confused easily). Also, I'd be willing to try a clean install, but don't want to go through the hassle of reinstalling everything again. If there is a quick way to backup programs, I'm all ears.
The good news is, it runs great when it's up. Quite smooth. Pretty awesome stuff.
I believe Titanium Backup should back everything up.....
I have downgraded to CyanogenMod 7.2 as I am very exasperated with this issue, the short battery life and lagginess that the upgrade has brought.
I just installed the latest (( ROM )) Sacs Custom 4.3 Rom 1-26-14 V5.5 ultra onto my GS4 and I love the ROM. I love the ROM and only have one complaint and I'm hoping it will be easy to resolve. There is a nearly constant display of CPU usage in the left side of the Notification panel. It is flashing numbers about every 5 seconds. When I open Notifications I also see a small bar just below the widgets that displays status for CPU0-CPU3. I assume the two are related.
Anyway, I want to turn it off since it crushes my battery display, burns through my battery faster, and is generally annoying. I have not been able to find a way to disable this...feature. I don't see it in Pimp My Rom although I am wary to mess with anything in there.
Can someone please tell me how to turn this off. It's driving me crazy.
Thanks,
S
See title. Thinking again about updating now that we have another update out in C11 (I believe this is the most recent).
Would you if you had to chance to stay on Android 11? Still very much on the fence.
I haven't had the time or energy to do a clean install, so maybe these issues wouldn't show up normally but here is my experience so far:
1. Forcing the hz to be always 120 is no longer as simple and must be reset every boot
2. Also custom dpi must be set every boot
3. Widgets sizes are all off, some too big and some too small.
4. Always on display is forced on, and almost always doesn't turn on for about 20 seconds when taken out of a pocket, forcing a press of the power button.
5. When always on display doesn't show the fingerprint icon (either configured or after a few seconds), fingerprint scanning won't activate
6. Aptx TWS+ simply doesn't work anymore. Defaults to notmal aptx or aptx hd
7. Reply in floating window doesn't function at all
8. Notifications that are unread but still in the drawer don't show up on the lockscreen
The new fingerprint animations are dope though
crDroid 8.4 is running really nice!
There a couple things I don't like. The new animations are good and a change of system sounds/ringtone is nice. The UI is mostly a sidegrade if not a downgrade in utility. I felt the same going from 10 to 11 and now 11 to 12. I guess I will just get used to it.
What I don't like is the horrendous navigation buttons. What idiot at OnePlus thought it would be a good idea to space out the nav buttons an inch apart? Makes reaching my thumb over (and I have big hands) a pain in the ass. It looks stupid as **** too. I had to switch to gesture navigation mode because of this. Also they added crap like shelf and the qualcomm voice thing/quick device connect which are annoying as I couldn't get rid of the notifications. I tried turning quick device connect off in settings and it wouldn't work. had to mute the notification.
Also in recents/multitasking when I hit close all apps it should close all apps but instead it goes back to the app I was using. This is annoying as I developed the habit of closing all apps and shutting of my phone in a clean slate.
I will do a follow up post of bugs as I encounter them
Thanks for the responses guys. It's shocking to me that widely released software has this many issues still. I may just stay on A11 then. I am eyeing the Pixel 7 in Sept/Oct and I'll leave OP behind at that point. It was a good run.