[Q] Strange slider behaviour - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi all,
I am using team OES 4.2 Nighties ROM with KAT Kernel and I have installed the KAT audio ap.
My issue is that I only have one digital slider available under the top right menu (when i slide down the top right section of the screen).
Sometimes it is the brightness slider, and sometimes it switches to the Volume slider.
I cannot find any setting that would allow me to choose what is available in this section.
I would like to find there the Volume and brightness sliders, on top of each other.
Can anyone help me fix that?
Thank you in advance.
D

Deazo said:
Hi all,
I am using team OES 4.2 Nighties ROM with KAT Kernel and I have installed the KAT audio ap.
My issue is that I only have one digital slider available under the top right menu (when i slide down the top right section of the screen).
Sometimes it is the brightness slider, and sometimes it switches to the Volume slider.
I cannot find any setting that would allow me to choose what is available in this section.
I would like to find there the Volume and brightness sliders, on top of each other.
Can anyone help me fix that?
Thank you in advance.
D
Click to expand...
Click to collapse
Revert back to your nAndroid backup and or start fresh.... could just be a bad flash or a confused mod lol make sure you wipe dalvik caches before starting from scratch
sent from
TF-101 A.R.H.D Harmony Kernel w/KingBeatz
Samsung Galaxy S3
AOKP 4.2.2 Kt747 kernel w/KingBeatz

Thank you for the response.
The solution you propose is rather drastic...
I have finally found a rom/kernel combination that works, my tablet works pretty well and this is the only issue I am having really.
What is a "bad flash"?
When installing I have wiped everything twice, and even wiped cache and datsik after install.
Is there not a way to get into system files and replace what is broken?
Just a shot in the dark, I am no android expert...
Thanks again

Deazo said:
Thank you for the response.
The solution you propose is rather drastic...
I have finally found a rom/kernel combination that works, my tablet works pretty well and this is the only issue I am having really.
What is a "bad flash"?
When installing I have wiped everything twice, and even wiped cache and datsik after install.
Is there not a way to get into system files and replace what is broken?
Just a shot in the dark, I am no android expert...
Thanks again
Click to expand...
Click to collapse
Replacing system files through device never recommend unless you know what your doing that's just method for bricking
By bad flash means when the mod/kernel etc when being downloaded isn't complete or is missing small sections that causing a portion not to work ..
AOKP 4.2.2 by Task650
Ktoonz Kernel w/KingBeatz
TF101 A.R.H.D ICS w/KingBeatz

Related

[ROM][OFFICIAL] CyanogenMod 9 (ICS) for SGH-T769

CyanogenMod 9 is a free, community built distribution of Android 4.0 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This phone isn't my daily driver, so I only tested a few things, and only slightly:
Known Bugs:
BLN is wonky. This is a CM9 thing and applies pretty much to all the msm8660 devices that use the cypress-touchkey BLN driver. Unlikely to be fixed
Other things maybe? Discuss in the thread...
How to get it:
Download: http://get.cm/?device=t769 (ChangeLog)
Or download it directly through ROM Manager or CM Updater.
Google Apps:
Make sure to download and install the ICS GApps
http://goo.im/gapps/gapps-ics-20120429-signed.zip
IF YOU ARE COMING FROM ANOTHER ROM, PLEASE MAKE SURE TO DO A FACTORY/DATA RESET BEFORE USING THIS. This isn't up for debate. A reset of the dalvik cache helps too. If you do a dirty flash, please make sure to do a dalvik cache wipe. If you have searched this forum for a problem and haven't found it, please do a nandroid backup, then a full factory/data reset and check to see if you still have the problem. If it still persists AFTER the factory/data reset, then report it here.
Thank You!
CyanogenMod Team (all of you, seriously, you guys are awesome)
SGH-T989 Devs (all of you, cuz I basically stole all your configs)
ShabbyPenguin & PlayfulGod for encouraging me when times looked grim.
UberPinguin and others on #jb-dev-e4gt for helping me get all of this work into CM proper
Oreo, my dog, for licking me whenever I needed it.
Older/Unofficial Versions (don't use if you can help it).
For older/legacy/test/unofficial versions of my work, you can find them (for a while at least) here: My Funhouse. Please take care and all necessary steps to verify MD5 sums before installing any zips.
Since CM9 is not a moving target like CM10, it may be some time before we get a point release. Therefore the occassional CM9 Nightly will have to do.
I'm not creating a Q&A thread for this one. Please behave yourselves and be nice to your neighbors.
That is all
Nice work getting it official man
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
erikmm said:
Nice work getting it official man
Click to expand...
Click to collapse
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work
does cm9 have wifi calling?
Bradlees said:
does cm9 have wifi calling?
Click to expand...
Click to collapse
no it doesnt.
dr4stic said:
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work
Click to expand...
Click to collapse
Lol yea that's true I got aokp-jb and ics almost complete so again thanks for the work
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
I've been using this due to the stability over cm10. Good stuff!
Hardkeys illumination
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?
lnxzilla said:
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?
Click to expand...
Click to collapse
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.
dr4stic said:
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.
Click to expand...
Click to collapse
I see, tnx for the clarification as it was my understanding the issue only occurs when the lights are actually used for notifications hence the BLN name. Oddly enough I didn't notice this happening when I was running the unofficial build, must have been a coincidence then I suppose.
CM9 after 11/2 will contain WiFi Random MAC fix
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run
dr4stic said:
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run
Click to expand...
Click to collapse
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......
boulos said:
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......
Click to expand...
Click to collapse
This is why swiching mounts is not great. The kernel flash replaces the boot.img.
Your best bet might be to wait till the next CM9 nightly comes out and modify that one.
Nightly build
CM9 downloads seem to go to internal storage but CWM was directed to perform update from external sd (ie microsd card). Unless I'm missing something, it doesn't look like the location can be changed manually.
Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?
creeve4 said:
Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?
Click to expand...
Click to collapse
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.
Which cm9 version are you using?
Sent from my SAMSUNG-SGH-T769 using xda premium
lnxzilla said:
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.
Click to expand...
Click to collapse
I've found that CLEAN flashes eliminate this for me on all ROMS. I think multiple dirty flashes like flashing updates over previous versions will eventually mess things up expecially when changes r made to the kernel
-I'm not a Dev, I just flash alot-
-If I've helped you the Thanks button is only 2 clicks away!
@woodzx67: Currently latest official cm9 20121125
@johnb380: Started fresh with a full wipe a few times already, makes no difference in this case as the data connection issue has always been there for me with cm9 in particular. I've only used cm10 briefly, don't recall that happening but then again the SOD issue prevented it from running for too long.

[Q] CM10 from BRUCE - Graphic problems (artefacts)

Hi, yesterday I flashed my stock HTC Sensation for the first time with CM10 4.1.2 from Bruce. I unlocked Bootloader, flashed 4EXT, wiped all, flashed Bruces ROM, flashed Gapps... I am still S-ON. Everything running great, but I have some graphic problems:
In default Camera app in panorama mode, I have many colored stripes, that are blinking on screen in about second interval.
I find two games not working. "Whale Trails" and "Riptide GP". Both start with black screen and sound only. If i turn off and turn on display with power button, I can see also graphic in Whale Trails, but it has a few stripes with frozen graphic on top of it, but game graphic under this frozen stripes is running normal.
In Riptide GP a couldnt see any graphic by no means...
I have sometimes some problems with colored mini stripes and dots even in Chrome browser, so I am using default CM10 browser.
I tried lower CPU frequency, but this didnt help.
Do you have any idea, where can be problem? THX!
Chrome and panaroma glitches are known problems.. Yet to fix those
As for the games.. Mostly because of using old adreno drivers of gpu (ics) yet to have jb drivers iirc
Sent from my HTC Sensation using xda premium
OK, so all my described problems will be (maybe) fixed in some of the future Bruces ROM? Including newer GPU drivers? So I should wait, or I should flash "something" now to repair it? Thank you for your patience with one noob
Mastegl said:
OK, so all my described problems will be (maybe) fixed in some of the future Bruces ROM? Including newer GPU drivers? So I should wait, or I should flash "something" now to repair it? Thank you for your patience with one noob
Click to expand...
Click to collapse
we need to wait :/
there is no fix yet for them
Thank you for clarifying the situation When there will be some new ROM from Bruce, should I do full wipe again before flash? I rather dont I read somewhere that I dont need to wipe when flashing from previous build... is it right?
Mastegl said:
Thank you for clarifying the situation When there will be some new ROM from Bruce, should I do full wipe again before flash? I rather dont I read somewhere that I dont need to wipe when flashing from previous build... is it right?
Click to expand...
Click to collapse
yes ..no need of full wipe ..when updating the same rom

Problem - cm10.1.0 androidarmv6 19.05.13 build

My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Jacek95 said:
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Click to expand...
Click to collapse
i'm using the CM10.1.0 RC2 jenkins build too.
i did a clean install, and had no problems with the notification.
though the first run android setup did crash for me too..[flashed the ROM twice]
i guess you should do a clean install!!
Do a clean install. One more thing, gapps are already included in the builds.
No need to flash the gapps
Jacek95 said:
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Click to expand...
Click to collapse
Gapps are already included in the ROM. No need to flash them again. If you flash the gapps, you may get those bugs as there isn't enough space for ROM as well as gapps.
try a clean install without flashing gapps.
rhar**** said:
Gapps are already included in the ROM. No need to flash them again. If you flash the gapps, you may get those bugs as there isn't enough space for ROM as well as gapps.
try a clean install without flashing gapps.
Click to expand...
Click to collapse
okay, will try now and report results soon
thanx for your effort
Okay, everything working fine, me flashing gapps over embedded ones in rom was the problem.

[Q] Random visual flashes/errors while using fresh PA

Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck
Turn off the corresponding setting in the developer options.
Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.
Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel

Ambient display keeps screen backlight on

Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!

Categories

Resources