Related
Well to start off, my evo's soft buttons don't work. they light up and everything, but when I touch them, there is no haptic feedback, and they do not perform their function. However, the rest of my screen works. I've been working around this issue with various ICS/JB kangs that let me enable the nav bar. However, the only reason this is now a problem to me is that I've found a rom I want to stay on as a daily driver, but it doesn't have the option to enable the nav bar even though it's a cm9 base. I've tried to decompile the framework-res.apk and enable it in the bools.xml, but my lack of knowledge on how to create a flashable zip is keeping me from being able to use this correctly. I'm trying to implement this into the 1.3.1 update on team dirt's remICS-ux port. Will somebody please help me?
The Impaler said:
Well to start off, my evo's soft buttons don't work. they light up and everything, but when I touch them, there is no haptic feedback, and they do not perform their function. However, the rest of my screen works. I've been working around this issue with various ICS/JB kangs that let me enable the nav bar. However, the only reason this is now a problem to me is that I've found a rom I want to stay on as a daily driver, but it doesn't have the option to enable the nav bar even though it's a cm9 base. I've tried to decompile the framework-res.apk and enable it in the bools.xml, but my lack of knowledge on how to create a flashable zip is keeping me from being able to use this correctly. I'm trying to implement this into the 1.3.1 update on team dirt's remICS-ux port. Will somebody please help me?
Click to expand...
Click to collapse
I believe Mazda is working on the update final of Team D.I.R.T. RemICS - UX port. I'd ask in the dev thread and see if this is in that update, or maybe try his Twitter feed, see if there is any mention there.
Ferenczy68 said:
I believe Mazda is working on the update final of Team D.I.R.T. RemICS - UX port. I'd ask in the dev thread and see if this is in that update, or maybe try his Twitter feed, see if there is any mention there.
Click to expand...
Click to collapse
I asked about it in the thread a week or two ago, and Mazda said it could only be implemented as a flashable zip. Then, I asked if he had one,and never got any reply on it at all. And a few days later, I asked if that was a no to the nav bar zip, and nobody ever replied to me. SO I tried to make it myself, to no avail.
The Impaler said:
I asked about it in the thread a week or two ago, and Mazda said it could only be implemented as a flashable zip. Then, I asked if he had one,and never got any reply on it at all. And a few days later, I asked if that was a no to the nav bar zip, and nobody ever replied to me. SO I tried to make it myself, to no avail.
Click to expand...
Click to collapse
Roger that, my bad. Ummm, I guess wait for the update and see what's there. It should be out soon (hopefully)
Ferenczy68 said:
Roger that, my bad. Ummm, I guess wait for the update and see what's there. It should be out soon (hopefully)
Click to expand...
Click to collapse
I'm definitely looking forward to it!
The Impaler said:
I'm definitely looking forward to it!
Click to expand...
Click to collapse
Me too, it has been my daily since I loaded it. I don't use FFC and have no need of 4G so it's perfect for me. Clean, fast and stable...
Ferenczy68 said:
Me too, it has been my daily since I loaded it. I don't use FFC and have no need of 4G so it's perfect for me. Clean, fast and stable...
Click to expand...
Click to collapse
Same here! And unlike most people, I love the TouchWiz ui. I think it looks amazing. But the fact that I can't use my home, menu, or back buttons keeps me from being able to actually use this rom. If i could get a copy of it with the nav bar, my flashing days would be over (or at least until I got a new phone ).
******NOOB WARNING*****'
I've been searching for a few days and haven't come up with anything. I'm trying to remap my search key to have it launch my camera instead. I just rarely use it and very much miss my dedicate camera hard key. I've tried the button remapper on one of these threads to no avail there seems to be one dedicate to Galaxy S phones but when I launched that one it said I wasn't using a supported device ( I've got a Samsung Galaxy S2 SGH-T989), and when I downloaded the other button remapper it launched just fine but when I changed the command for the search key to camera it did nothing. Next I went into my root explorer and copied all .kl files with the 217 search key that I was lead to believe was the one I needed to edit and put them on my external sd and then preceded to modify the originals from "SEARCH" to "CAMERA." But that attempt failed as well. All that did was disable my search key all together. Not sure if I was on the right track here and just missed something or if that's just a completely idiotic attempt. Either way I've just Typically failed at my noobish attempt at Remapping my search key. If anyone can help this sad and disgraced noob please let me know.
Thanks!
P.S. My phone is rooted and I'm just running plain ole ICS 4.0.3 and I'm gonna post a screens of "about phone" section incase that helps at all. Sorry if I sound like an idiot but I'm very new to all this. Just rooted my first phone a few weeks ago. So if you could keep that in mind when you reply it would be much appreciated. Thanks again
jalight27 said:
******NOOB WARNING*****'
I've been searching for a few days and haven't come up with anything. I'm trying to remap my search key to have it launch my camera instead. I just rarely use it and very much miss my dedicate camera hard key. I've tried the button remapper on one of these threads to no avail there seems to be one dedicate to Galaxy S phones but when I launched that one it said I wasn't using a supported device ( I've got a Samsung Galaxy S2 SGH-T989), and when I downloaded the other button remapper it launched just fine but when I changed the command for the search key to camera it did nothing. Next I went into my root explorer and copied all .kl files with the 217 search key that I was lead to believe was the one I needed to edit and put them on my external sd and then preceded to modify the originals from "SEARCH" to "CAMERA." But that attempt failed as well. All that did was disable my search key all together. Not sure if I was on the right track here and just missed something or if that's just a completely idiotic attempt. Either way I've just Typically failed at my noobish attempt at Remapping my search key. If anyone can help this sad and disgraced noob please let me know.
Thanks!
P.S. My phone is rooted and I'm just running plain ole ICS 4.0.3 and I'm gonna post a screens of "about phone" section incase that helps at all. Sorry if I sound like an idiot but I'm very new to all this. Just rooted my first phone a few weeks ago. So if you could keep that in mind when you reply it would be much appreciated. Thanks again
Click to expand...
Click to collapse
If you have clockworkmod recovery, or any custom recovery, flash attached file via recovery.
Did I do something wrong here?
elesbb said:
If you have clockworkmod recovery, or any custom recovery, flash attached file via recovery.
Click to expand...
Click to collapse
Ok, well let me start out by saying I'm a moron. Below I posted and the whole recovery thing went way over my head. Lets just say the scapegoat there was not enough sleep and being way over worked. But anyway after writing that I realized how stupid I was. So I immediately pulled my head but of my but and went into recovery mode and installed your zip from there, reported, and still nothing for my search key. Is it because I screwed the pooh on my first attempt? Read the dribble I posted first and please lemme know:
First off, thank you very much for taking the time to reply and do all this for me. After reading your post I went out and got clockwork Rom manager which also lead me to download clockwork recovery. I then preceded to click on the zip file you provided and when it completed downloading I opened it. I took a snapshot of the screen that popped up. I clicked yes leaving the box checked that the program had checked for me (just as it is in the screen shot). Afterthat the phone preceded to do it's thing and a few minutes later the phone rebooted and now if I hit the search key it vibrates but doesn't actually do anything. Did I do something wrong along the way? Again, I really do appreciate you taking the time out for me and I'll be awaiting your response. Thanks!"
Stupid, I know. But I'll assume that that's probably the problem. If I can find some time tomorrow I'll try revolving the copy of the Rom I made before I killed my search key and then do it properly, and hopefully that'll be that and I'll FINALLY have my search key camera. Thanks again!
jalight27 said:
Ok, well let me start out by saying I'm a moron. Below I posted and the whole recovery thing went way over my head. Lets just say the scapegoat there was not enough sleep and being way over worked. But anyway after writing that I realized how stupid I was. So I immediately pulled my head but of my but and went into recovery mode and installed your zip from there, reported, and still nothing for my search key. Is it because I screwed the pooh on my first attempt? Read the dribble I posted first and please lemme know:
First off, thank you very much for taking the time to reply and do all this for me. After reading your post I went out and got clockwork Rom manager which also lead me to download clockwork recovery. I then preceded to click on the zip file you provided and when it completed downloading I opened it. I took a snapshot of the screen that popped up. I clicked yes leaving the box checked that the program had checked for me (just as it is in the screen shot). Afterthat the phone preceded to do it's thing and a few minutes later the phone rebooted and now if I hit the search key it vibrates but doesn't actually do anything. Did I do something wrong along the way? Again, I really do appreciate you taking the time out for me and I'll be awaiting your response. Thanks!"
Stupid, I know. But I'll assume that that's probably the problem. If I can find some time tomorrow I'll try revolving the copy of the Rom I made before I killed my search key and then do it properly, and hopefully that'll be that and I'll FINALLY have my search key camera. Thanks again!
Click to expand...
Click to collapse
That happened to me as well. I then opened up my camera and pressed the search key while my camera was open. It took a picture. And booted, after that, pressing the search key then launched the camera. So try that.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
elesbb said:
That happened to me as well. I then opened up my camera and pressed the search key while my camera was open. It took a picture. And booted, after that, pressing the search key then launched the camera. So try that.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Alright what I just did now, launch whatever camera app you use. Press the back button. Press and hold the search button. Should work.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Beautiful
elesbb said:
That happened to me as well. I then opened up my camera and pressed the search key while my camera was open. It took a picture. And booted, after that, pressing the search key then launched the camera. So try that.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
Alright what I just did now, launch whatever camera app you use. Press the back button. Press and hold the search button. Should work.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Beautiful. Just did what you said and works perfectly. Might have even been working before I just didn't hold the button when I was doing it yesterday. Thank you so much. Was kinda sceptical when I posted that I would just get a bunch of condescending remarks, but very happy to see this site isn't like some others I've been too. Anyway though, thanks a million. This is gonna be awesome for my twins. I keep missing good photos cuz it takes that extra few seconds to find my camera. Now I'll be able to get to it in a flash. Thanks again. You're awesome.
jalight27 said:
Beautiful. Just did what you said and works perfectly. Might have even been working before I just didn't hold the button when I was doing it yesterday. Thank you so much. Was kinda sceptical when I posted that I would just get a bunch of condescending remarks, but very happy to see this site isn't like some others I've been too. Anyway though, thanks a million. This is gonna be awesome for my twins. I keep missing good photos cuz it takes that extra few seconds to find my camera. Now I'll be able to get to it in a flash. Thanks again. You're awesome.
Click to expand...
Click to collapse
Not a problem! I have my camera set to a short cut on the lockscreen and a gesture when I'm in my phone lol. But that's a good idea to just assign it to another button
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Not a problem! I have my camera set to a short cut on the lockscreen and a gesture when I'm in my phone lol. But that's a good idea to just assign it to another button
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Hello again. I just download my first new ROM, Jedi mind trick, and I obviously lost my search button camera. Since I'm not running the stock ROM will the zip file you sent me previously still work to replace my search key with launching the camera? Thanks in advance!
The keymap files are at /system/usr/keylayout/
Different ROMs probably have different files, but I guess you can find the file(s) you need to change from "SEARCH" to "CAMERA"
Keep in mind, do a backup before change anything.
angellsl said:
The keymap files are at /system/usr/keylayout/
Different ROMs probably have different files, but I guess you can find the file(s) you need to change from "SEARCH" to "CAMERA"
Keep in mind, do a backup before change anything.
Click to expand...
Click to collapse
Right, always sure to do that. I made a backup of all the files I edited last time. Edited all the keylayout files last time though and didn't do anything. Maybe I missed one though. I'll give it a try and edit it when I'm do though. Thanks for the info!
---EDIT---Totally worked. Actually I think I had it set the first time I did this on my stock ICS Cruz when I pressed the search key once in camera it took a pic but the problem I was having all along was I just wasn't holding it down. Typical noob right? Oh well, learned my lesson. Try absolutely EVERYTHING before posting and sounding like a moron, lol. Anhway, elessb, would it be possible for you to instruct me on how to get to my camera on my lock screen like you have it. That would just be beyond amazing.
jalight27 said:
Right, always sure to do that. I made a backup of all the files I edited last time. Edited all the keylayout files last time though and didn't do anything. Maybe I missed one though. I'll give it a try and edit it when I'm do though. Thanks for the info!
---EDIT---Totally worked. Actually I think I had it set the first time I did this on my stock ICS Cruz when I pressed the search key once in camera it took a pic but the problem I was having all along was I just wasn't holding it down. Typical noob right? Oh well, learned my lesson. Try absolutely EVERYTHING before posting and sounding like a moron, lol. Anhway, elessb, would it be possible for you to instruct me on how to get to my camera on my lock screen like you have it. That would just be beyond amazing.
Click to expand...
Click to collapse
Which ROM are you on? The cm ROMs have custom shortcuts so that's how I got it there.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Which ROM are you on? The cm ROMs have custom shortcuts so that's how I got it there.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've got Jedi Mind Trick running right now. Its blazing fast but its kinda buggy. Was in love with it at first, but the longer I have it, the more it's annoying me. Programs seem to freeze up quite often and stall out the phone for 30 seconds or so, and it seems to be doing it at least 3/4 times a day. I've heard good things about the cm ROMs. I know its kinda off topic, well maybe not all that much since I'm interested in the camera shortcut, but is there a specific ROM you'd reccomend concerning the camera shortcut, and of course with overall functionality in mind as well.
Thanks!
jalight27 said:
I've got Jedi Mind Trick running right now. Its blazing fast but its kinda buggy. Was in love with it at first, but the longer I have it, the more it's annoying me. Programs seem to freeze up quite often and stall out the phone for 30 seconds or so, and it seems to be doing it at least 3/4 times a day. I've heard good things about the cm ROMs. I know its kinda off topic, well maybe not all that much since I'm interested in the camera shortcut, but is there a specific ROM you'd reccomend concerning the camera shortcut, and of course with overall functionality in mind as well.
Thanks!
Click to expand...
Click to collapse
The latest jelly bean nightly from either Erick or binaryBishop is amazing. It's better than my official nightly from cyanoGen mod on my s3
Sent from my SGH-T999 using Tapatalk 2
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
In light of the newly-minted LuneOS alpha release, I was wondering if anyone had experience dualbooting webOS on their Galaxy Nexus? I know it's possible to do so with Android-based ROMs, but I want to keep my CM nightlies as a fall-back, especially since the LuneOS is in such an early stage and technically does not officially support the device (they're looking for community support *hinthint devs*). If you do, please drop a note with your experience in this area! Thanks in advance. :good:
drfandroid said:
In light of the newly-minted LuneOS alpha release, I was wondering if anyone had experience dualbooting webOS on their Galaxy Nexus? I know it's possible to do so with Android-based ROMs, but I want to keep my CM nightlies as a fall-back, especially since the LuneOS is in such an early stage and technically does not officially support the device (they're looking for community support *hinthint devs*). If you do, please drop a note with your experience in this area! Thanks in advance. :good:
Click to expand...
Click to collapse
Well,it would be cool,even with sailfish os,that i really love
Anyway for everybody who wants to try webos (LunaOs) http://webos-ports.org/wiki/Maguro_Info
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
jsgraphicart said:
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
Click to expand...
Click to collapse
Wondering this as well.
they had, and still have the best multitasking on a mobile device i've ever used. it was just so fluid and intuitive. some of their features they incorporated are still ahead of their time today
x000x said:
they had, and still have the best multitasking on a mobile device i've ever used. it was just so fluid and intuitive. some of their features they incorporated are still ahead of their time today
Click to expand...
Click to collapse
Agreed. Has there been any other phone that uses a gesture area like they did? I loved that.
jsgraphicart said:
Agreed. Has there been any other phone that uses a gesture area like they did? I loved that.
Click to expand...
Click to collapse
I looked for a long time, but nothing recent. there was one thing kind of similar, a few years back called 'itching thumb' http://www.xda-developers.com/android/use-itching-thumb-to-multitask-in-android/ but was discontinued long ago.
Yeah, well I just checked the comments on their official release post, and after some helpful replies I can (sadly) announce that there is no dual-boot support. Also, the latest build they have is a couple weeks old, since they no longer have a maintainer for the device The post is here, if any of you want to skim it . So at this point it's either flash a build that's dated, without a fall-back that would come with dual-booting, or wait and see
drfandroid said:
Yeah, well I just checked the comments on their official release post, and after some helpful replies I can (sadly) announce that there is no dual-boot support. Also, the latest build they have is a couple weeks old, since they no longer have a maintainer for the device The post is here, if any of you want to skim it . So at this point it's either flash a build that's dated, without a fall-back that would come with dual-booting, or wait and see
Click to expand...
Click to collapse
There's a Sept. 1st build there. More towards the Center.
http://build.webos-ports.org/luneos-testing/images/maguro/
There's a Sept. 1st build there. More towards the Center.
Click to expand...
Click to collapse
Yes, I just noticed haha my bad. I was just paraphrasing a comment off of the post I linked to. Shame there's only dual-booting available on the Touchpad (for now at least). I'll probably wait until the next stable release or so before diving in.
jsgraphicart said:
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
Click to expand...
Click to collapse
im flashing it on a toroplus right now, gonna let you guys know how it goes when it finishes. on a related note, make sure to wipe /system before you flash, because the updater script doesnt do that. i had cm11 installed on there before and forgot to do it, so im reflashing clean now.
also, it looks like at least some of the android file system is retained, so that means we may be able to get data working by pulling libs from a 4.2.2 rom. dont quote me on that, ill try it and see what happens when i get this thing to boot. I pulled apart the boot.img and nothing seems to be stopping us there either from what I can tell.
edit: as much as i wish this worked, dont waste time flashing it if your not a maguro device. doesnt boot on toroplus, prolly wont boot on toro either.
whoshotjr2006 said:
im flashing it on a toroplus right now, gonna let you guys know how it goes when it finishes. on a related note, make sure to wipe /system before you flash, because the updater script doesnt do that. i had cm11 installed on there before and forgot to do it, so im reflashing clean now.
also, it looks like at least some of the android file system is retained, so that means we may be able to get data working by pulling libs from a 4.2.2 rom. dont quote me on that, ill try it and see what happens when i get this thing to boot. I pulled apart the boot.img and nothing seems to be stopping us there either from what I can tell.
edit: as much as i wish this worked, dont waste time flashing it if your not a maguro device. doesnt boot on toroplus, prolly wont boot on toro either.
Click to expand...
Click to collapse
That's too bad. What are you getting when it tries to boot? Have you let it sit for a while before coming to that conclusion? Maybe it doesn't have any sort of booting indication.
Update: I ended up going for it, and flashed the stable build onto my maguro. Worked, but none of the apps would open again after I had closed them for some reason (If I wanted to open Preware 2 again, I had to reboot the device...). The dev build wouldn't boot at all after flashing, so I'm running on the August 10th stable build.
jsgraphicart said:
That's too bad. What are you getting when it tries to boot? Have you let it sit for a while before coming to that conclusion? Maybe it doesn't have any sort of booting indication.
Click to expand...
Click to collapse
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
whoshotjr2006 said:
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
Click to expand...
Click to collapse
Well that sucks. Hopefully someone picks up development for this device. I'd like to try it out eventually. I have an HP Touchpad but it has Android on it as well. I havent looked into it yet but installing this might need a full wipe. I don't want to go through the hassel of starting all over again. lol
jsgraphicart said:
Well that sucks. Hopefully someone picks up development for this device. I'd like to try it out eventually. I have an HP Touchpad but it has Android on it as well. I havent looked into it yet but installing this might need a full wipe. I don't want to go through the hassel of starting all over again. lol
Click to expand...
Click to collapse
You're right, flashing it on your nexus pretty much requires a full wipe lol. The Gnex doesn't have dual-boot capability for LuneOS (yet!! ). I asked in the comments of the announcement post. Fingers crossed for that, though! Really hoping a dev steps out and continues the project, even if it's just on the side.
whoshotjr2006 said:
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
Click to expand...
Click to collapse
Any luck with the August 10th build? My build can't activate developer options (Settings--> Developer Options, flicked the switch, still says "Developer mode is disabled"-->entered Konami Code into search, tapped on the dev mode result, nothing happened), so I can't activate USB Debugging or anything like that. On top of that, the phone takes forever to even boot into the Google screen, and I can't get into Recovery or Fastboot mode. In essence, even if I wanted to re-attempt to flash the nightly or go back to Android, I can't. I was hoping to go try the PA 4.6 Beta on my Gnex, so I was a bit gutted. Any ideas??
drfandroid said:
Any luck with the August 10th build? My build can't activate developer options (Settings--> Developer Options, flicked the switch, still says "Developer mode is disabled"-->entered Konami Code into search, tapped on the dev mode result, nothing happened), so I can't activate USB Debugging or anything like that. On top of that, the phone takes forever to even boot into the Google screen, and I can't get into Recovery or Fastboot mode. In essence, even if I wanted to re-attempt to flash the nightly or go back to Android, I can't. I was hoping to go try the PA 4.6 Beta on my Gnex, so I was a bit gutted. Any ideas??
Click to expand...
Click to collapse
yep no luck for me here, mine just wont boot into it at all. I can still access fastboot though, holding both volume buttons from and power from completely off doesnt get you into fastboot? if your volume button hardware has gone bad, i know you can buy new on ebay for cheap, might have to do that. sorry to hear about your problem, and I hope you get it fixed somehow.
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.........................................