Develop Bugs

[DEV][CDMA/GSM] Group Effort to Optimize Existing HoneyComb Ports

Full credit goes to Ssserpentine, SpaceMoose, and OldMacnut for their work on their united efforts to port Honeycomb to our tablets! It seems they are no longer working on it so I decided to create this thread and see what we all could to do together to improve what they have given us!
The point of this thread is to find ways to gather anyone with knowledge on developing, even if its just the "lowly 7-Zippers" like me, to see how we can remove minor bugs and small issues from the ROM. I know Oldmacnut was going to pick it up, but he has a lot on his plate right now and he has been in pain and is more interested in finishing the CM7 Port instead. I respect his decision, but so many people want honeycomb working on our tabs. So I am turning to the dev community here to see if we can group together and fix things in this rom together. If we cant solve the major bugs, lets address all the little things, cuz the little things add up.
Spacemoose made a list of suggestions from users earlier on how to solve minor issues, and little workarounds, but I would like to see if there is a way to roll up those fixes into one full updated ROM flashable through a zip/odin/heimdall file, and see if we can come up with more. You can see this post here, but I have added them to the second post as well in a more organized form.
Some Useful Links as Well:
SpaceMoose's Github
6-19-11 Apps Confirmed Working on [CDMA] / [GSM] Honeycomb Alpha 2.5
Currently Known Bugs:
CDMA
A) Red Border Around Screen at Random Times
B) Constant Gallery Force Close
C) Stock Launcher hangs for many seconds at a time randomly
D) SD Card Does Not Mount
E) Youtube app does not work
F) Orientation Sensor is not functional
G) Honeycomb thinks Device Keyboard is enabled by default
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
I) HQ Youtube does not work (LQ does on the mobile site)
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
K) Flash Player is not Fully Functional
GSM - Please Submit or confirm if the above bugs are the same and/or you have different ones!
Red - Signifies an issue that is unaddressed or has not been solved yet.
Orange - Signifies a Temporary Fix or Workaround is mentioned in the post I linked to.
Blue - Will signify a temporary fix or a work around that we have been able to include in a flashable file
Green - Will signify a bug that has been completely fixed in a flashable file.
------------------------------------------
Lets put our minds together and see what we can do guys! Btw this was inspired by Rodderik's thread [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR), so if youre interested in this, you might like his thread too!

Current Workarounds/Temporary Fixes:
Letters correspond to the bugs listed in the OP.
A)
Ssserpentine:
1) Open up Dev Tools
2) Go to Development Settings
3) StrictMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
Click to expand...
Click to collapse
B)
anfalas:
"Get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
Click to expand...
Click to collapse
C)
Ssserpentine:
“WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
Click to expand...
Click to collapse
D)
mattman83:
"to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
Click to expand...
Click to collapse
or
corodius:
"if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
Click to expand...
Click to collapse
E)
Use m.youtube.com to play LQ videos
Click to expand...
Click to collapse
F)
ztag100:
"If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Click to expand...
Click to collapse
G)
"one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
Click to expand...
Click to collapse
H) ---
I) ---
J) ---
K) ---
----------------------------
Submit a New Bug or Fix:
Please submit bugs using the color coded system I explained in the OP. If you are submitting information on solving a bug please address the bug by the corresponding letter so that we can stay organized and know what youre talking about. If you have a new bug please check the OP to make sure I havent listed it, then post it on here and dont worry about the letter, I will alphabetize them. Of course I will credit you in the OP for any fixes or workarounds you may find! Good luck to us all!

Reserved as well!

Yes, please
I would really love a Honeycomb ROM for the Galaxy Tab. There are many reasons why I want to put Honeycomb onto the original Galaxy Tab.
Just see the difference for yourself: Blank space, single pane, one-category-at-a-time menus in Gingerbread
VS.
Less blank space, concise, dual pane interfaces in Honeycomb.
Gingerbread apps are just designed for smaller smartphone screens, so they look too big and spaced-out on the 7-inch Galaxy Tab for my taste. I would really love to see some tablet-optimized apps on the Galaxy Tab!
-------------------------
And yes, I respect the developers and appreciate them so much for the time they put into making custom roms a reality for us!

Please make the thread for GSM also.

TheATHEiST said:
Please make the thread for GSM also.
Click to expand...
Click to collapse
Are the bugs the same? Or are there others that I havent mentioned? I will try to make a section for both tabs if theres different bugs in each one.

Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Still, hope is eternal, I suppose

PunkRock said:
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Click to expand...
Click to collapse
Easy man, in my frenzy of trying to organize the thread, I forgot to credit Ssserpentine in the OP, youre right he did contribute a lot, no need to be rash, I will update it right now.
EDIT: btw oldmacnut did make an audio fix, im running his rom right now, I downloaded it when he had it posted before he took it down, and Im sure some of the bugs I mentioned are fixable on the rom level rather than through adb. My goal wasnt to debug the rom completely, it was to incorporate all the existing bug fixes and workarounds into one rom, while possibly solving others. Also the GSM devs are aplenty here, while we barely have any CDMA, Im sure we have enough talent to make it better than what it is. It might not be flawless, but Im sure we can squeeze more functionality out of it.

Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium

oldmacnut said:
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
Yeah I know, the lack of source sucks along with the fact we dont have drivers. I dont think we'll have everything working anytime soon at all, if ever even, but I think some of the minor annoyances like the disappearing quick settings toggle, sdcard mounting issues, and graphical errors can be solved without that kind of stuff. Me personally, Id just like HQ Video Playback and 3D Graphics working a hundred percent along with orientation, but as you said no drivers so idk how easy that'd be. Still, Im sure we could solve some of these minor issues. I keep browsing over the Nook Color Forums trying to find hints to solving some of these things

GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium

BulletproofIdeal said:
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Nice to see something happening here. I love my Tab but would like some advancements in OS to address specific issues. I am very new to the dev side of the Android OS but would like to get involved.
--Mike

What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
On a different note, the alpha 2.5 HC Rom for gsm, the sd cards will not mount no matter what, I've tried The terminal and the mount instructions many times all I am able to do is get the tab to recognize my external sd as the internal sd, and if you try to go to settings applications and clear data for the gallery you get a force close as soon as you tap manage applications
Sent From Githrog's Tab

Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
Githrog said:
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
Click to expand...
Click to collapse
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant

Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Honeycomb is closed source. Nobody can make a tablet without Google's blessing. The reason given is that Honeycomb was rushed out the door, and the code isn't good enough for an open source release. They're right you know, setting the emulator to anything smaller than a tablet will result in about a million force closes. Honeycomb just isn't as supportive of hardware as Gingerbread was. To save developers the headache of supporting a platform that wasn't ready, Android's openness got shelved.
Luckily this is going to change. The big cheese said so himself on the Official Android Developers blog, "This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types." Source code is coming back. This will make the modding community's life much easier. Cyanogenmod 8 (I got excited just typing that) and Ice Cream Sandwich will be able to get hacked onto just about anything.
Click to expand...
Click to collapse

CROrION said:
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Click to expand...
Click to collapse
I just wanted an excuse to try out Honeycomb

BulletproofIdeal said:
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Click to expand...
Click to collapse
Wow now that is the kinda posts i like seeing on here! I will try to update the OP tonight with this info! Thanks so much! Definitely echo your sentiments about the fractured and fragmented development we have going on here, it really sucks =/
Ive found out that replacing the existing Gallery with Gallery3D should fix the FC that keeps popping up.
I think Ive found a working Youtube App (in LQ).
Ive also found a hint towards solving the sdcard mounting issue. Its not the vold.fstab its something either in the framework or ramdisk within the kernel, according to the Nook Color Forums.
This thread is interesting: http://forum.xda-developers.com/showthread.php?t=1062626 , actually the entire nook color forum is interesting for finding fixes.
Also changing the dalvik_heapsize to a certain value is supposed to increase app compatibility. Before I update the OP with some of these things, I wanna do a little more testing and see what I can come up with.

Sorry to bother for help,
Sorry to bother you guys for help, but I've been trying to install Oldmacnut's updated of Spacemoose's CDMA Honeycomb (2.5.1) for hours now, with no success.
I used Rodderick's awesome stock rom/kernel and got into clockworkmod (using 4.0.1.5 or 3.0.0.0), installed the zip from there, then rebooted the phone, but I would either 1) be stuck at logo for 10+ minutes 2) see the Sprint startup video loop over and over again, or 3) get stuck on a turned on, but black screen.
How did you guys install Honeycomb on your CDMA tab? Am I doing something wrong? Should I use Spacemoose's 2.5 rom instead of Oldmacnut's?
EDIT: NEVER MIND, IT BOOTED INTO HONEYCOMB. I am in a foreign language, haha, I'm guessing Portuguese?
EDIT EDIT: Google Translate detects the language as Catalan. Haha!

iliveinabucket said:
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
Click to expand...
Click to collapse
Hehe that happened to me as well

First Impressions and problems encountered
HOLY SHOOT THIS IS QUITE FAST!
Considering there is no graphics acceleration support, Honeycomb runs much faster than I anticipated. SD card support is fantastic, and so is hearing sound! (I love you OMC) The UI is awetastic and the standard web browser is blazing fast. Scrolling in web pages is faster on Honeycomb than on Gingerbread stock.
The jittery touch screen bug I have is still there, unfortunately. Damn bug drives me crazy sometimes. I'm sure somebody has this problem that many of us have but have not found a fix to: http://forum.xda-developers.com/showthread.php?t=970965
Basically, when I hold down my finger to scroll on white or light-color backgrounds, the screen shakes back and forth in a spastic, noticeable way, especially when I hold it in place. This happens on every single rom I've been on, froyo, GB, CM7, and now Honeycomb. Has anyone found a fix for that yet?
Anyways, I think all the known Honeycomb bugs are true to me too. Youtube force closes on me, GPS doesn't work, auto-orientation doesn't work. Strangely enough, Quick Settings doesn't work for me. Anyone encounter that?

BUG: JB 4.1.2 update - Pressing Home Button to wake brings up task manager sometimes?

I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.

mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...

Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse

My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.

I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse

mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test

You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse

No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?

I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.

mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days

I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you

kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear

Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.

It's not all notes.
Sent from my SGH-T889 using xda premium

kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?

wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry

wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.

kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over

[Q&A] [ROM][D851] CyanogenMod 12.0

Q&A for [ROM][D851] CyanogenMod 12.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][D851] CyanogenMod 12.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Please be careful
Pretty sure I'm out of luck here and kind of screwed :/ but I edited the build.prop to 640, after saving etc. and rebooting I'm bricked. Phone won't boot pass the LG screen - and can't get into any sort of recovery. If anyone has any suggestions I would highly appreciate it. In that 'freak out' mode right now so please leave any criticisms to yourself. Thanks.

Deep sleep?
Anyone hit deep sleep? Tried this and the PAC-MAN version and I'm unable to to hit it.

richardhaid said:
Pretty sure I'm out of luck here and kind of screwed :/ but I edited the build.prop to 640, after saving etc. and rebooting I'm bricked. Phone won't boot pass the LG screen - and can't get into any sort of recovery. If anyone has any suggestions I would highly appreciate it. In that 'freak out' mode right now so please leave any criticisms to yourself. Thanks.
Click to expand...
Click to collapse
Make sure the phone is powered off. Power it back on while holding the Power button and the volume down button. As soon as the LG Logo appears, let go of both buttons and then hold them again. You will get a message asking if you wish to factory reset. Select yes and and it will boot to recovery. Reflash the rom and you should be fine.
Pretty hard to "brick" a phone from modifying your build.prop

Video Recording
Won't let me post in the main thread (new account), but it looks like the video recording issue is related to old drivers
review.cyanogenmod. org/#/c/78130/ (had to add some spaces before .ORG as it won't let me post an outside link yet.)
Props to $droyd$ for pointing this out.

Work Around for Hung Lock Screen
Occasionally, the lock screen becomes unresponsive to touch. I've found consistently that turning the screen off, then holding a finger on the touchscreen while pressing the power button to wake it up causes it to become responsive again. Can anyone else verify?

Spotify
Is Spotify working for anyone? I get an instant reboot when I open it. Tried clearing data, and uninstalling/reinstalling.
Also, seems that once it gets done rebooting, my SIM is unrecognized and I can't get data unless I reboot manually.

removed - turns out that I don't know crap about logcats, and what I posted is worthless.
I'll try to educate myself some more and pull one through ADB

Here is an app I found on the dev preview to fix the battery percentage/charging not showing on the icon. https://play.google.com/store/apps/details?id=de.kroegerama.android4batpercent

First off, the ROM is great overall so thanks for all the hard work. I have two issues, but neither is a big deal.
First, I can't encrypt the phone. When I try, it just reboots and sits on the boot up screen.
Second, Google Authenticator force closes. It will open, but as soon as I hit "Begin Setup" it just closes.
Is there any information on either of these issues?

I've been using this as my daily driver for two days now and there's only been one kernal crash!
Less apps FC than with the stock ROM... this build is amazing. Thank you!

Is there a way to change the order of the navigation keys?
Sent from my LG-D851 using XDA Free mobile app

Stupid question probably, but how hard would it be to get the IR blaster working? For people like me who have an LG TV, not having it working is killing me.

music
I cleaned flashed the latest build and neither Google play music or appollo music are working and also the phone only shows that it's charging if you have it plugged up while booting

How do you switch the back button and the recent apps button.
Sent from my LG-D851 using XDA Free mobile app

Anyone have messages going to the wrong people while using the new messenger App along with cm12?

I'm running Pac Rom (Lollipop) on my G3 now. Anybody know of any major differences between this and the Pac Rom build ? Thanks.

EibonMusic said:
I'm running Pac Rom (Lollipop) on my G3 now. Anybody know of any major differences between this and the Pac Rom build ? Thanks.
Click to expand...
Click to collapse
All lollipop builds are very similar from a feature standpoint at the moment.
I'm running with Phantom because he is doing am excellent job keeping everyone updated. ?
Sent from my LG-D851 using Tapatalk

quaman said:
I cleaned flashed the latest build and neither Google play music or appollo music are working and also the phone only shows that it's charging if you have it plugged up while booting
Click to expand...
Click to collapse
Third party music apps and other sounds are working though.

quaman said:
Third party music apps and other sounds are working though.
Click to expand...
Click to collapse
Google music has worked fine in every build I have flashed
Sent from my LG-D851 using Tapatalk

[Q&A] [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss

Q&A for [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

jewnersey said:
not sure why that's happening..but a new build should be up in the next day, hopefully, with some of the kinks ironed out. Probably best to just wait until then.
Click to expand...
Click to collapse
@ jewnersey: It could be the greatest rom :angel:, if you can embedded camera features in the next update. Not forcing you to do that immediately, just requesting you since you are engaged with your job. Thanks.

cant believe how great this rom is..i agree..so so many options...one of the best custom roms ever had..it flashed perfect for me..ive read how some people are haveing problems with wifi not working,i flashed the rom,then kernal,then gapps,and wifi worked out of the box..if it diddnt i was gonna flash a diff recovery like philz and try again..normally that works for me...only issue ive had is when pressing language and input it crashes.i was gonna install a themed google keyboard and activate it as main keyboard but cant get into the settings to even see what keyboard is installed..but still love the rom and understand its a work in progress...thanks bliss team for this rom and port,much better then what i had before this!!!
update..now see witch keyboard is installed threw settings/apps....it is android keyboard..could request that android keyboard come with diff themed options i really like the shafta google keyboards,but cant install if google keyboard allready exsists,and i dont wanna mess with freezeing/uninstalling system apps

any lovin for the t705??
we uad some advancements but got stuck at the lte implementation.
could be due to the 4g/3g intel chip samdung used for its exynos chip.....
i feel so cheated out of my snapdragon 801.....

Am uploading a newer build that should be much cleaner and ironed out.
As far as other devices... I am not a developer, so bug fixing etc is currently beyond me... However, if there is a CM port for the device, I can probably port Bliss for that device, but all the shortcomings of the CM rom will exist in Bliss as well.. Either way, I will see what I can do after I make sure T700 is running smoothly.

New build is up.

Hey
It would be nicer if you have some specific screenshots. BTW, hope you guys can ported this rom to T805 lots of Asian users are waiting for you

stkpxl said:
Tried the new build. Tried to create a second user (which is a must for me). When trying to use the new user, the launcher crashes and basically wont let me do anything. With the new CM11 build, I don't have that issue. Which is weird, since I understand thats what your build is using.
Click to expand...
Click to collapse
will look into this.
vo.tran.thanh.luong said:
It would be nicer if you have some specific screenshots. BTW, hope you guys can ported this rom to T805 lots of Asian users are waiting for you
Click to expand...
Click to collapse
screenshots added.....
I am basically relying on the real developers, so once CM or an equivalent arrives for 805, ill fire up a Bliss derivation.

Thank you for your hard work providing this rom! just couldn't stand the stutter of touchwiz.
one thing I desperately miss is the color calibration though.
I can't find the option in settings. could somebody please point it out to me?
another thing I noticed is that the tablet runs smoother when plugged in. when I pull the plug I have a tiny bit of stutter. Do you have any suggestions how to fix this?

Screen Locks automatically and frequently
Hi Jewnersy,
I appreciate your efforts in creating the Bliss Rom for Samsung Tab S (T700). I have been using the rom from the last two releases. I love the settings and customizations provided in the Rom . I observed one small issue in the latest build. I am using a Flipcover cover for my Tab. When I close the cover, screen goes off which is fine. But When I open the cover am able to the see the lock screen, but not able to unlock the screen by swiping the lock icon to right side. After swiping it to right side, screen suddenly locks again. After giving trails for 10 - 15 times, am able to unlock the device. While watching movies also screen locking unexpectedly. Please help me in getting a solution for the issue. Thanks again for your response & support in advance.

schmandchen said:
Thank you for your hard work providing this rom! just couldn't stand the stutter of touchwiz.
one thing I desperately miss is the color calibration though.
I can't find the option in settings. could somebody please point it out to me?
another thing I noticed is that the tablet runs smoother when plugged in. when I pull the plug I have a tiny bit of stutter. Do you have any suggestions how to fix this?
Click to expand...
Click to collapse
Don't think there are any color options built in to the rom unfortunately. Regarding stuttering.. I'm not sure I'm having that issue. The latest rom had been smooth as butter for me... Interactive governor, cfq, Westwood.
Dynamic status bar will cause constant stutter. Use the xposed mod discussed in thread as an alternative
raghavamsc said:
Hi Jewnersy,
I appreciate your efforts in creating the Bliss Rom for Samsung Tab S (T700). I have been using the rom from the last two releases. I love the settings and customizations provided in the Rom . I observed one small issue in the latest build. I am using a Flipcover cover for my Tab. When I close the cover, screen goes off which is fine. But When I open the cover am able to the see the lock screen, but not able to unlock the screen by swiping the lock icon to right side. After swiping it to right side, screen suddenly locks again. After giving trails for 10 - 15 times, am able to unlock the device. While watching movies also screen locking unexpectedly. Please help me in getting a solution for the issue. Thanks again for your response & support in advance.
Click to expand...
Click to collapse
I noticed a flip cover quirk as well. Will investigate tomorrow and grab some other fixes from other folks.

WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
---------- Post added at 03:32 AM ---------- Previous post was at 03:27 AM ----------
Zimus said:
WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
Click to expand...
Click to collapse
Feel free to ignore this particular post, I'm going to post a bunch of B.S. until I can get my total post count over the 10 post threshold so that I can actually post bug reports in the proper thread.

Zimus said:
WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
---------- Post added at 03:32 AM ---------- Previous post was at 03:27 AM ----------
Feel free to ignore this particular post, I'm going to post a bunch of B.S. until I can get my total post count over the 10 post threshold so that I can actually post bug reports in the proper thread.
Click to expand...
Click to collapse
Wow I tested too! I posted in the rom thread. If your reporting bugs then it's OK to post in the rom thread. q and a stuff goes here about the thread. It's just to remind you to ask questions here. I'm surprised Ui lag is gone! Once you make more than 100 posts then there's no limit on posts.

DUHAsianSKILLZ said:
Wow I tested too! I posted in the rom thread. If your reporting bugs then it's OK to post in the rom thread. q and a stuff goes here about the thread. It's just to remind you to ask questions here. I'm surprised Ui lag is gone! Once you make more than 100 posts then there's no limit on posts.
Click to expand...
Click to collapse
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...

Zimus said:
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...
Click to expand...
Click to collapse
Lol. After a few posts you can post there. Did you try the camera and see if it works? I forgot to check that.

Zimus said:
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...
Click to expand...
Click to collapse
not my decision, but rather the forums.
ANYWAYS, did you try without the kernel or with the kernel?

DUHAsianSKILLZ said:
Lol. After a few posts you can post there. Did you try the camera and see if it works? I forgot to check that.
Click to expand...
Click to collapse
I switched back to the 11/27 build due to wifi not working on the 12/15 build. The camera doesn't work on 11/27, but the developer is already aware of that issue. Give me a few min and I'll re-flash the 12/15 build and check the camera.

Zimus said:
I switched back to the 11/27 build due to wifi not working on the 12/15 build. The camera doesn't work on 11/27, but the developer is already aware of that issue. Give me a few min and I'll re-flash the 12/15 build and check the camera.
Click to expand...
Click to collapse
let me know if you are using the 'skyhigh' kernel or not...
basically need to know if wifi is broken with and without kernel
as well as camera under both conditions,

jewnersey said:
not my decision, but rather the forums.
ANYWAYS, did you try without the kernel or with the kernel?
Click to expand...
Click to collapse
I tried just the ROM w/o flashing the SkyHigh kernel - wifi still wouldn't turn on. My apologies on my rant concerning the 10 post minimum, the "error" message made it sound like it was your decision -- sorry!

Zimus said:
I tried just the ROM w/o flashing the SkyHigh kernel - wifi still wouldn't turn on. My apologies on my rant concerning the 10 post minimum, the "error" message made it sound like it was your decision -- sorry!
Click to expand...
Click to collapse
not a problem.
Let me have a look at the source and see if i can figure whats going wrong. probably something super easy. hopefully can post a new build in a few hours. did you try camera?

[Q&A] [ROM][SM-T320][5.1.1_r3][UBERTC 4.9]UnofficialTemasek v12.3[June4]

Q&A for [ROM][SM-T320][5.1.1_r3][UBERTC 4.9]UnofficialTemasek v12.3[June4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T320][5.1.1_r3][UBERTC 4.9]UnofficialTemasek v12.3[June4]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Thanks
Thanks for that awesome rom, super fast and solid as a rock, full of features, some that I never see on other rom like otg usb notification unmount, it's the best rom that i tried on my tab pro, continue your great job :good:

Deleted

dead tablet
Hi guys. I installed this ROM a few days ago was very happy even though the battery durava unless the rom official ... but today I've run into a problem I connect to the tablet in the morning around 30 min. and he had 96% of battery I have left and I have gone to work my surprise was at the vuelata my tablet etaba off and there is no way to Ramp up've left more than 4 hours to charge and so far nothing, alkene over them past that ??? and that I can do to get right the problem. sorry for the language.
a greeting

Keyboard sound
How to turn off or change that ugly keyboard sound the first ROM for me so far it is good few glitches

Disabling back and recent hardware keys
i originally dirty flashed this rom over cyogenmod 12.1 and it mostly worked but had some issues. doing a clean install helped most of them, but i ran into a new problem i didn't have with the dirty flash. i prefer an onscreen nav bar to hardware keys but i want to keep the home button working, just disable the back and recent buttons. in the dirty flash disabling hardware keys did just this, but now it disables all 3 of them. i noticed that i can leave the hardware keys turned on and disable the recent button, buy changing the short press and long press action to nothing, but i don't have a way to disable the back key.
My question is if there is any method which i missed that would allow me to disable to back key aswell? did i miss a setting somewhere? oddly enough with all the problems i had with the dirty flash, this one thing worked how i wanted it too, and now its not. i know i can change the key bind for it with xposesd, but as was discused before it causes a boot loop.
other then this problem, this is a fantastic rom and i am extremely great full for all the time and work that went into making it possible. and especially thank all the people that come to these fourms and help clueless people like myself.

innocentus said:
How to turn off or change that ugly keyboard sound the first ROM for me so far it is good few glitches
Click to expand...
Click to collapse
It should be under settings>control>input

bricked device
so i flashed your rom one week ago and 2 days ago without warning or something the device shut down .when i try to power on i cant only black screen and thats all no recovery no download mode only a black screen ,the battery was full what can i do?thank you

innocentus said:
so i flashed your rom one week ago and 2 days ago without warning or something the device shut down .when i try to power on i cant only black screen and thats all no recovery no download mode only a black screen ,the battery was full what can i do?thank you
Click to expand...
Click to collapse
Known as sleep of death. Hold power button for at least 30 seconds. I sent mine back before I discovered that to reset takes way longer than most devices.
---------- Post added at 07:19 PM ---------- Previous post was at 07:11 PM ----------
@konchar
Disable in settings, buttons, hardware keys. The navbar height is set to 0, increase this or you won't see it
New version of the ROM out today. Much improved, xsposed working again. IMO Temasek rocks.

Thanks gscollier i didn'try that even i browse the web all day. I sent mine too at warranty service mine i think it's death because. I keep it in charge 4hours and still nothing. Thanks again for the news it's really a good rom and fast just trebuchet stops from time to time

@gscollier
@konchar
Disable in settings, buttons, hardware keys. The navbar height is set to 0, increase this or you won't see it
New version of the ROM out today. Much improved, xsposed working again. IMO Temasek rocks.
Click to expand...
Click to collapse
thanks for the response, but it doesn't quite help me with my problem. I think you misunderstood, i know how to disable all hardware keys and have no problem with the onscreen nav bar. what im trying to do is disable the hardware keys for back and recent while leaving the home button functional. it can be done with xposed modules but i cant seem to get xposed to work here, even with the new update.
once again thanks for the reply, i will keep looking for a solution.

konchar said:
@gscollier
thanks for the response, but it doesn't quite help me with my problem. I think you misunderstood, i know how to disable all hardware keys and have no problem with the onscreen nav bar. what im trying to do is disable the hardware keys for back and recent while leaving the home button functional. it can be done with xposed modules but i cant seem to get xposed to work here, even with the new update.
once again thanks for the reply, i will keep looking for a solution.
Click to expand...
Click to collapse
Got it, don't think you can disable only back and recent but not home. So, xposed. I don't know what module you are using but make sure you have the xposed alpha from here:
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Many modules cause bootloops but I have 4 working with no problems on the latest Temasek ROM. I strongly recommend ROM backup before flashing the xposed zip and also each time you try a module. Slightly time consuming but quicker than flashing the ROM from scratch. If a module causes bootloop you can wipe cache and davlik cache in recovery. If it still bootloops that module just won't work for now. Trial and error I'm afraid.

Niathi said:
Hi guys. I installed this ROM a few days ago was very happy even though the battery durava unless the rom official ... but today I've run into a problem I connect to the tablet in the morning around 30 min. and he had 96% of battery I have left and I have gone to work my surprise was at the vuelata my tablet etaba off and there is no way to Ramp up've left more than 4 hours to charge and so far nothing, alkene over them past that ??? and that I can do to get right the problem. sorry for the language.
a greeting
Click to expand...
Click to collapse
Try to press start button more than 30 seconds, it will reboot,

BT-tethering
Sorry, if it is a known CM-issue!
I couldn't get bluetooth-tethering to work. For me that is a very important feature on a mobile device without SIM-Slot. That's why I had to go back to laggy TW-ROM.

So for this ROM you flash then wipe data/factory reset? Is that considered a clean flash?

ntdouglas said:
So for this ROM you flash then wipe data/factory reset? Is that considered a clean flash?
Click to expand...
Click to collapse
A "clean flash" is wiping everything first, then flashing.

Thanks vasumit! How frequently do you plan on providing updates to this ROM? I'm trying to decide between this and CM12.1 as my daily driver.

in the last build from 7.10 doesn't show the performance tab of the kernel . anybody same problem on a clean install thanks

Thanks sharkie. Developers instructions stated otherwise. I clean flashed this ROM and it is nice. Has anyone noticed on the android launch screen its grainy or pixelated? Games and internet look awesome. Same problem when I was running stock CyanogenMod 12.1. Also how do I get the clock widget out of military time?
---------- Post added at 03:40 AM ---------- Previous post was at 02:57 AM ----------
Another problem to report. I flashed the gapps package recommended by the developer and all I see is the play store. What's up?

Can anyone share your performance setting with me?
This ROM is nice in term of general performance and feature, especially in comparison with the original CM12.1 which gave me huge unresponsive issue during app installation.
However the CPU temperature is quite hot and my tab have broken down three time in a row during the last two days. I have to let the it rest for about an hour before turning it back on and right now i'm still waiting, don't know if it will come back to life or not. Really scary, this one.
Can anyone confirm the temp issue? This is the first time i encounter this much trouble on a device after install CM based ROM. First is the unresponsiveness of original 12.1, now this.........................................