Has there been any hope of getting touch recovery for the DS?....I used it on an LG phone I was unbricking for a co-worker and wow it is nice...clockwork but all touchscreen...I know ROM development is slow maybe one of the DEVs would think to hit up the guys to see how to get the DS rolling.
i might try this over the weekend http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html?m=1 but i hope its has an option for cwm touch
xmc wildchild22 said:
i might try this over the weekend http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html?m=1 but i hope its has an option for cwm touch
Click to expand...
Click to collapse
This might help too
http://www.xda-developers.com/android/team-utterchaos-releases-their-touch-recovery-source/
There is 2 or 3 touch recoveries out there...not sure how different they are from device to device...logically I would assume it is more based on partition structure since it is really before boot...but I dont know...it would be nice to have some advances...4ext was nice on the Glacier...
Guys, I'm working with Dees_troy to port TWRP 2.1. We can't port CWM touch because Koush has it closed source.
Indirect said:
Guys, I'm working with Dees_troy to port TWRP 2.1. We can't port CWM touch because Koush has it closed source.
Click to expand...
Click to collapse
I use TWRP on my kindle and it is a really cool recovery. I hope you can get it to work. if you need a tester just PM me.
dont forget to put it on github
It will be cool once we get an updated recovery....hopefully Indirect is able to make it happen...not sure how hard it is to get recoveries working...but will be great to have a nice touchscreen recovery...
4ext is pretty convenient. Though I admittedly still have a soft spot for CWM. Any reason why they didn't all start out as touch recoveries? It's nice to have both options as a failsafe.
That being said, I can't see how much harder it could be to port one to the MT4GS
Sent from my Sensation 4G using XDA
Personally, I like using the trackpad more. I've seen the touchscreen interface in action and it's not very intuitive. The trackpad is more precise
Especially when you're mucking around with things in recovery. The last thing you want to do is make a mistake or select the wrong thing
gtmaster303 said:
Personally, I like using the trackpad more. I've seen the touchscreen interface in action and it's not very intuitive. The trackpad is more precise
Especially when you're mucking around with things in recovery. The last thing you want to do is make a mistake or select the wrong thing
Click to expand...
Click to collapse
Well the one I seen still had the same inputs like the confirmation...why not use a touchscreen when we have touchscreen phones...its like using a rotary dial phone this day in age...some people like the old but a lot of us want the current tech and touch recovery is current. Might not be for everyone and thats cool...the current version works well...other than lack of charging when phone is off but I get tired of the volume rocker and stuff...rather cumbersome.
I figured I would check to see if there has been any progress here?
beezie916 said:
I figured I would check to see if there has been any progress here?
Click to expand...
Click to collapse
I believe I read that touch recovery will be possible only after we have a finished 3.0 kernel which is being worked on by teamds
Sent from my myTouch_4G_Slide using Tapatalk 2
rawdaddymagraden said:
I believe I read that touch recovery will be possible only after we have a finished 3.0 kernel which is being worked on by teamds
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
If your referring to the same thing I seen that was CM9 that needs the kernel change...I don't believe kernel effects recovery....
I didn't care about touch recoveries before, but now I've got a phone with button problems. I'm hoping to use a recovery to fix try some things, but I can't move around. So, now, a touch recovery would be better than a [... something really good to have].
Any news here?
My G2 has touch recovery. Honestly, the trackpad and hardware buttons are a better interface (making the touchscreen redundant).
Sent from Spaceball One.
blackknightavalon said:
My G2 has touch recovery. Honestly, the trackpad and hardware buttons are a better interface (making the touchscreen redundant).
Sent from Spaceball One.
Click to expand...
Click to collapse
No, they're not at all. I've been using 4EXT on my G2 since it was released for the phone up until yesterday when someone gave me their old MT4GS. One of the few things I miss from the G2 is 4EXT (apart from the alt and shift buttons switching spots and the power button switching sides). There is no way in hell that scrolling with the trackpad is better than touch. Trackpad scrolling overshoots for me if you want to go fast, or is too slow if you go at a normal pace (particularly painful when scrolling through an SD card with 20+ directories to find the zip you want to flash). Volume button scrolling is just as slow.
But why scroll down when you can just touch it. At the point 4EXT is at now, it's as functional as an OS level app is. It has a fully functioning notification bar with date/time/battery info, pull it down and you can see the recovery log. There are still safety measures in place (i.e. "are you sure you want to format /system"). It's easily theme-able and has a few more features than CWM (like FS and alignment checks, ext2/3<->4 conversion that will automatically restore your files after it's done). IMO, the touch screen makes hardware buttons redundant... at least in the recovery.
beano311 said:
No, they're not at all. I've been using 4EXT on my G2 since it was released for the phone up until yesterday when someone gave me their old MT4GS. One of the few things I miss from the G2 is 4EXT (apart from the alt and shift buttons switching spots and the power button switching sides). There is no way in hell that scrolling with the trackpad is better than touch. Trackpad scrolling overshoots for me if you want to go fast, or is too slow if you go at a normal pace (particularly painful when scrolling through an SD card with 20+ directories to find the zip you want to flash). Volume button scrolling is just as slow.
But why scroll down when you can just touch it. At the point 4EXT is at now, it's as functional as an OS level app is. It has a fully functioning notification bar with date/time/battery info, pull it down and you can see the recovery log. There are still safety measures in place (i.e. "are you sure you want to format /system"). It's easily theme-able and has a few more features than CWM (like FS and alignment checks, ext2/3<->4 conversion that will automatically restore your files after it's done). IMO, the touch screen makes hardware buttons redundant... at least in the recovery.
Click to expand...
Click to collapse
You were just being overzealous with the trackpad. I never got those problems with standard recovery.
Sent from Spaceball One.
Related
Last week Vaizard420 got my attention by booting my Honeycomb on the D1. I promised to get a real port going for you guys, and here it is.
http://t3hh4xx0r.com/projects-2/dev-ports/honeycomb/d1
Working
Data (i think)
Touchscreen
Text Messages
Notification and softkey lights
Not Working
Wifi
Gps
Calls (Honeycomb doesn't come with a phone app)
Hardware acceleration
Simple auto rotation
Camera
Downloads
OMHC_sholes.zip
Donate to help me get a D1, I can get one for $50.
Crazy wild stuff.
haha omg cant believe you making this one as well
Pretty pumped your creating this, knowing how well ur doing on the other port for TB
The sense 3.0 stuff? Haven't touched it recently.
I have my hands in everything xD
Sent from my ADR6400L using XDA App
is that zip file the one in the video?
Pithism said:
is that zip file the one in the video?
Click to expand...
Click to collapse
yes it is.
not sure, just use the top link to get the one in the video
Ya. I haven't watched the video but thats the one the tester sent me.
Sent from my ADR6400L using XDA App
Can't wait for wifi and gps to be finished!!!! Simply amazing work guys!
So what all would be required to get calls working on this? Is it just a matter of getting a phone app on there or is it a more complex problem? Id love to see this get to be a full fledged, stable rom.
It won't ever have working phone stuff.
This is honeycomb, not meant for phones
Sent from my ADR6400L using XDA App
You could have a duel boot setup to have both in one device, easier than switching backups. I'm gonna give this a run, any kernels work best for this?
Loaded this up, slow I expected. No on board keyboard that I got to work. The physical keyboard did not have functional numbers that I got to work. I could not get the power button to work either.Nice work though, looks good.
So, sent from my mobile. What's new?
sorry to bother, but i've a question.. i've got a samsung i9003 that has chipset mostly identical to droid, the rest of the hardware is different, i know, phone,gps,wifi,etc. it is possible to recompile kernel from milestone to samsung, knowing the differences,and adding the kernel modules to make it work? gingerbread for this phone is arriving next month,but no rom have been spotted, but i hopo... sorry to invade your section, but i wanted to ask to some developers and i hope a good reply... sorry for my english.
True, the original software isnt meant for phones BUT, he just managed to boot it on a phone, opening up the possibilty phone use. I want to know whats required to get it working.
I loaded up the rom and it works but there are missing elements, without them it is pretty much useless. I had no wifi or data so I could not load anything on it. Neat to play with though, needs a 1000 MHz kernel just to tinker with.
kind make me happy i made the choice of buying this phone in july last summer.
How about root access? Flashed another overclock kernel pushed setcpu but no root access
Very impressive although for phone use doesn't do much there. Plus I can't use the power switch to shut device on and off
did this project die? hopefully not just seems no development has happened in a while
Really, its not going to get any better than this. Only reason I ported it to my phone was because I wanted to see what it would look like. Then people started requesting ports. This was never and will never be anything close to a DD. Its just something fun to flash and play with for a minute, then go back to your ctual rom.
Sent from my Transformer TF101 using XDA Premium App
Does anyone know of a touch recovery being worked on for our beloved Xoom? I've been using the Rogue recovery for quite some time and while I think it is fantastic, I also think that the volume buttons on the Xoom pretty much suck. It would be amazing to have Koush's touch ClockWork, or pretty much any touch enabled recovery...
I would work on it myself, but I am pretty much clueless where to start...
Botero said:
Does anyone know of a touch recovery being worked on for our beloved Xoom? I've been using the Rogue recovery for quite some time and while I think it is fantastic, I also think that the volume buttons on the Xoom pretty much suck. It would be amazing to have Koush's touch ClockWork, or pretty much any touch enabled recovery...
I would work on it myself, but I am pretty much clueless where to start...
Click to expand...
Click to collapse
Eh - I'm pretty sure Team Rogue will be releasing one. I read it in Steady Hawkin's Twitter or possibly G+.
He also hinted at something "big" coming soon in the CM9 dev thread.
I too would love to see this implemented in our Xooms, I have it for my NS and its sooo frikkin convienient. I agree the volumes on Xoom are finicky for the task.
Just don't quote me on it....just my .02
Botero said:
Does anyone know of a touch recovery being worked on for our beloved Xoom? I've been using the Rogue recovery for quite some time and while I think it is fantastic, I also think that the volume buttons on the Xoom pretty much suck. It would be amazing to have Koush's touch ClockWork, or pretty much any touch enabled recovery...
I would work on it myself, but I am pretty much clueless where to start...
Click to expand...
Click to collapse
I'm still holding my breath with my fingers crossed! Quote this thread at my funeral.
I'm no developer but I have been messing around with something....this is what I have so far
https://www.youtube.com/watch?v=WwX03NwVKe0&feature=youtube_gdata_player
Sent from my Galaxy Nexus using Tapatalk
I talked to the Rogue guys and they said they are going to release one. It has my blessing because we got other things to handle. However, I fear their time is becoming limited. We have had touch recovery for ages now. Come on Rogue! Time for the rubber to hit the road here! Don't make me cook something up now .
Hey BigRush
It says you have a touch screen recovery on the xoom.
Where can i get it?
Please tell me I missed the release of this and I didn't see the post.
Any change a developer could do a mod to add the Galaxy Nexus navigation buttons to the screen? I for one don't like the physical home button and would really like the screen buttons. If the unoffical AOKP rom had the standard AOKP custom nav button mod I would be all over it but seeing how it's unofficial/alpha and the CM10 roms are very alpha I'd rather wait. Based on the info I found it's relatively easy mod if you know how to decomplie and recompile the framework-res.apk. I attempted to do this but kept running into issues and my limited knowledge of Android development (to say the least) seems to be the biggest huddle.
IMO, I'd still like the native button active but others would prefer them disabled.
Here a thread on the mod for CM9/CM10... http://forum.xda-developers.com/showthread.php?t=1788780&page=1
Thanks!
rkirmeier said:
Any change a developer could do a mod to add the Galaxy Nexus navigation buttons to the screen? I for one don't like the physical home button and would really like the screen buttons. If the unoffical AOKP rom had the standard AOKP custom nav button mod I would be all over it but seeing how it's unofficial/alpha and the CM10 roms are very alpha I'd rather wait. Based on the info I found it's relatively easy mod if you know how to decomplie and recompile the framework-res.apk. I attempted to do this but kept running into issues and my limited knowledge of Android development (to say the least) seems to be the biggest huddle.
IMO, I'd still like the native button active but others would prefer them disabled.
Here a thread on the mod for CM9/CM10... http://forum.xda-developers.com/showthread.php?t=1788780&page=1
Thanks!
Click to expand...
Click to collapse
It won't work on the stock ROM. But it works in CM10, I have it on my phone and am loving them. Just like my old Nexus.
I know the mod in the link I provided will not work on the stock rom. Thanks for your most value input and stating what is outright obvious for the mod in the link. No reason a developer couldn't create a mod that does work with the stock rom though. Already using a few mods on my stock rom.
rkirmeier said:
I know the mod in the link I provided will not work on the stock rom. Thanks for your most value input and stating what is outright obvious for the mod in the link. No reason a developer couldn't create a mod that does work with the stock rom though. Already using a few mods on my stock rom.
Click to expand...
Click to collapse
There might actually be a reason. The framework is totally different.
tekhna said:
There might actually be a reason. The framework is totally different.
Click to expand...
Click to collapse
Of course the framework is different, one is TouchWise and one is CM9/CM10 but that has absolutely nothing to do with a developer modifying the stock TW framework-res.apk with this mod. Why do users who have no clue keep adding their useless 2 cents? I now understand why the developers get so frustrated and the development forum in highly moderated!
Here a new thread to shows how to do this mod on any ROM. If I had the experience of decompling/compling apks or time I would do it.
http://thetechjournal.com/how-to/tutorial-how-to-use-on-screen-virtual-buttons-at-ice-cream-sandwich-rom-on-android.xhtml
rkirmeier said:
Of course the framework is different, one is TouchWise and one is CM9/CM10 but that has absolutely nothing to do with a developer modifying the stock TW framework-res.apk with this mod. Why do users who have no clue keep adding their useless 2 cents? I now understand why the developers get so frustrated and the development forum in highly moderated!
Here a new thread to shows how to do this mod on any ROM. If I had the experience of decompling/compling apks or time I would do it.
http://thetechjournal.com/how-to/tutorial-how-to-use-on-screen-virtual-buttons-at-ice-cream-sandwich-rom-on-android.xhtml
Click to expand...
Click to collapse
lol, someone who has no clue yelling at someone he thinks has no clue about clueless 2 cents. Being an asshole is a really great way to get people to do things for you, I've heard.
Im dont know why anybody wants onscreen buttons? Yea the nexus had them and thats fine. But with 2 capacitive buttons and a hardware button, why have nav buttons that do the same thing? All its does is take up screen space no?
droidstyle said:
Im dont know why anybody wants onscreen buttons? Yea the nexus had them and thats fine. But with 2 capacitive buttons and a hardware button, why have nav buttons that do the same thing? All its does is take up screen space no?
Click to expand...
Click to collapse
I agree with this. I have figured out how to get them and I've been using it for a day or so now. I don't like it. I thought I would, but I don't.
droidstyle said:
Im dont know why anybody wants onscreen buttons? Yea the nexus had them and thats fine. But with 2 capacitive buttons and a hardware button, why have nav buttons that do the same thing? All its does is take up screen space no?
Click to expand...
Click to collapse
I hate the physical home button and much prefer the on-screen buttons.
tekhna said:
I hate the physical home button and much prefer the on-screen buttons.
Click to expand...
Click to collapse
why?
droidstyle said:
why?
Click to expand...
Click to collapse
Because I'm used to capacitive buttons, it's clunky to use a physical button, and depressing the button off-balances the whole phone if you're using it one-handed.
tekhna said:
Because I'm used to capacitive buttons, it's clunky to use a physical button, and depressing the button off-balances the whole phone if you're using it one-handed.
Click to expand...
Click to collapse
I totally agree!
It's funny how people think that because they don't mind the physical home button that everyone else should feel the same way. The screen is big enough that I don't mind losing a little space. Give me a "touch" home button and task list button that I don't have to wait 2 seconds for...
tekhna said:
Because I'm used to capacitive buttons, it's clunky to use a physical button, and depressing the button off-balances the whole phone if you're using it one-handed.
Click to expand...
Click to collapse
To each is own...i would much rather have more screen. However if they designed this device like the nexus with only nav buttons, then that would be ok. I just dont like the idea of having multiple buttons that do the same thing.
tekhna said:
lol, someone who has no clue yelling at someone he thinks has no clue about clueless 2 cents. Being an asshole is a really great way to get people to do things for you, I've heard.
Click to expand...
Click to collapse
Whatever! It's the same BS that the developers get upset over. People who have no clue making useless statements that do nothing for the cause. It's a waste of space and time...
I could be wrong but I thought all ICS and JB frameworks have the vitual navigation button code, it just a matter of enabling it. See the second link I posted...
rkirmeier said:
I totally agree!
It's funny how people think that because they don't mind the physical home button that everyone else should feel the same way. The screen is big enough that I don't mind losing a little space. Give me a "touch" home button and task list button that I don't have to wait 2 seconds for...
Click to expand...
Click to collapse
I dont expect anybody to feel the same way...I was simply wanting to know why he didnt like hardware button.
rkirmeier said:
Whatever! It's the same BS that the developers get upset over. People who have no clue making useless statements that do nothing for the cause. It's a waste of space and time...
I could be wrong but I thought all ICS and JB frameworks have the vitual navigation button code, it just a matter of enabling it. See the second link I posted...
Click to expand...
Click to collapse
You "Totally agree" with the guy in one post and then call him clueless in another. A guy who has been part of xda since 2007 and has 1000 more thanks than you do. Be civil
bobdude5 said:
You "Totally agree" with the guy in one post and then call him clueless in another. A guy who has been part of xda since 2007 and has 1000 more thanks than you do. Be civil
Click to expand...
Click to collapse
I don't see why agreeing with someone preference for something and calling them out regarding a statement that seems clueless has anything to do with each other. Unless he knows for a fact that the Touchwiz ICS framework-res.apk has been stripped of the navigation button code (not just disabled) his comment was clueless... Having a 1000+ posts does not make someone an expert and if he knows for a fact then he should have said the TW ICS framework has been stripped of the navigation bar code...
There are plenty of opinions on the value of the mod. The original thread link I posted seemed to suggest there are a lot of people who want this. This thread so far may not support that for US users... Oh, well... If there is no dev that wants to do this mod then I guess I'll wait for a stable release of AOKP where I can modify/add buttons too...
Thanks!
rkirmeier said:
I know the mod in the link I provided will not work on the stock rom. Thanks for your most value input and stating what is outright obvious for the mod in the link. No reason a developer couldn't create a mod that does work with the stock rom though. Already using a few mods on my stock rom.
Click to expand...
Click to collapse
As I said in my post, "it won't work on the stock ROM". The support for it is just not there in TouchWiz. You can modify the framework-res.apk if you want (I've tried), but it just won't work. If you want on screen navigation keys, you'll need to get onto CM/AOSP.
Here are my reasons for preferring nexus style on-screen buttons:
1. I no longer have to overextend my thumb to press the menu button when holding the device with one hand. Usually this results in my palm hitting something on the screen unintentionally.
2. Once frustrated with #1, I will tilt the device down (increasing the chances of dropping the phone) to be able to successfully press the menu button. With on screen buttons I no longer have to do this.
3. If 1&2 are not an option I am forced to use 2 hands to control the device. With on screen buttons this is no longer so.
4. I will no longer accidentally press menu or back while playing a game in landscape mode.
5. I will no longer accidentally tap something on the bottom edge of the screen when attempting to press the back or menu button. Because it is a far stretch, part of my thumb will often interact with the lowest point of the screen before interacting with the back or menu button.
The slogan for this device shouldn't be "Designed for humans" but rather "Designed for gorilla hands".
If possible, I would also like to see on screen buttons on touchwiz.
Sent from my SCH-I535 using XDA App
michaelw9 said:
As I said in my post, "it won't work on the stock ROM". The support for it is just not there in TouchWiz. You can modify the framework-res.apk if you want (I've tried), but it just won't work. If you want on screen navigation keys, you'll need to get onto CM/AOSP.
Click to expand...
Click to collapse
Ok, thanks for the update and clarifying the the ICS framework has been stripped of the code for the onscreen navigation buttons. Really too bad but CM and AOKP are both coming long nicely...
Question of Curiosity, And of course, Preference
Im Considering Changing up roms Eventually, I use my phone quite frequently,
Tubing, Browsing the Web. and Music, Occasionally ill get my self addicted to a game i have an extended battery of course.
I do happen to text more frequently then others
i would like to know what the forum users of XDA Choose as their roms of their picking
I personally am having great expectations of JellyBelly
Hopefully v4 won't disappoint your great expectations
I'm sure jellbelly will meet or exceed expectations. I have been trying all the JB builds in this forum and it is the smoothest running so far. I have had issues with them all locking up sometimes but this one does it the least and is the only one that hasn't forced a battery pull.
Ianonymous said:
Question of Curiosity, And of course, Preference
Im Considering Changing up roms Eventually, I use my phone quite frequently,
Tubing, Browsing the Web. and Music, Occasionally ill get my self addicted to a game i have an extended battery of course.
I do happen to text more frequently then others
i would like to know what the forum users of XDA Choose as their roms of their picking
I personally am having great expectations of JellyBelly
Click to expand...
Click to collapse
I personally use newSENSE and ICS. I find cm10 to be too unstable.
junpei1337 said:
I'm sure jellbelly will meet or exceed expectations. I have been trying all the JB builds in this forum and it is the smoothest running so far. I have had issues with them all locking up sometimes but this one does it the least and is the only one that hasn't forced a battery pull.
Click to expand...
Click to collapse
I've Used, JellyBelly for a bit it still has the keyboard issue where if you hit the cap button once it will lock into All CAPS For the whole message and you have to toggle it many times to get it to unlock from caps or you just have to Hold the Shift ( Cap ) Button to Cap a letter and let it go.
I've also ran into a few problems . with the FN some Options such as the _ Underscore will not appear in some log in Selection boxes. i have to manually go to my soft touch keyboard and key it in by long pressing the Symbol.
None the less dont get me wrong its a great rom hands down. I would like to see those little kinks worked out.
Sorry man, but that's the way the keyboard is on JB, you gotta hold the shift or fn key down like on the computer.
bilgerryan said:
Sorry man, but that's the way the keyboard is on JB, you gotta hold the shift or fn key down like on the computer.
Click to expand...
Click to collapse
Since when? That was only a problem in decks as far as I knew
Sent from my PG06100 using xda app-developers app
BigSplit said:
Since when? That was only a problem in decks as far as I knew
Sent from my PG06100 using xda app-developers app
Click to expand...
Click to collapse
It has been that way for me on every JB ROM, with random times that it works correctly... IDK. Either way, I will probably not be doing any more work on JB until it is less buggy. It's just a headache when bugs pop up out of nowhere, some of the weird bugs aren't ROM specific either. Sorry guys, but it kinda takes the fun out of it when you are constantly fixing bugs. I may do one more update, but I don't know when that will be. For now I'll let the devs that are more talented than me see if they can work out some kinks, my main objective with JellyBelly was to reduce the lag so JB was more usable.
bilgerryan said:
Sorry man, but that's the way the keyboard is on JB, you gotta hold the shift or fn key down like on the computer.
Click to expand...
Click to collapse
I figured as much . I just dont understand the reason for caps locking all the time xD none the less im loving it so far.
Ianonymous said:
I figured as much . I just dont understand the reason for caps locking all the time xD none the less im loving it so far.
Click to expand...
Click to collapse
I don't understand a few of the bugs on JB lol
Not do I. I'm sure with the devs hard work it will be worked out
Sent from my PG06100 using xda app-developers app
I first tried out kushdeck's CM10 for the evoSHIFT! but found that very unstable. Constantly hangs and the phone would reboot.
Using bilgerryan's JellyBelly-CM10 v4 and it does still hang for a minute at times in the same places as kushdeck's. Primarily happens throughout settings such as viewing APPS then selecting something also SystemUI hangs.
penroid said:
I first tried out kushdeck's CM10 for the evoSHIFT! but found that very unstable. Constantly hangs and the phone would reboot.
Using bilgerryan's JellyBelly-CM10 v4 and it does still hang for a minute at times in the same places as kushdeck's. Primarily happens throughout settings such as viewing APPS then selecting something also SystemUI hangs.
Click to expand...
Click to collapse
Keep your eyes peeled for V6 of bilgerryan's JB ROM. Testing is going very nicely! I had similar freeze issues with previous versions, but I think he just about has the kinks worked out.
jdjohn said:
Keep your eyes peeled for V6 of bilgerryan's JB ROM. Testing is going very nicely! I had similar freeze issues with previous versions, but I think he just about has the kinks worked out.
Click to expand...
Click to collapse
I tried V6 just now, unfortunately I am not able to post in the thread as my account has less than 10 posts but I have run into a few issues with it thus far. The animations and scrolling are very choppy, this may be related to the "screen flickering" problems listed so i'll have to check the build.prop and make sure everything is as it is supposed to be there. As well, i've ran into a bug where upon backing out of the camera (which I use frequently), all icons and widgets vanish until phone reboot. That's quite a big problem! It's a fast ROM no doubt, and probably the best JB based ROM we have ATM.
Did you do a full wipe as described in this? http://forum.xda-developers.com/showthread.php?t=1266885
Chad The Pathfinder said:
Did you do a full wipe as described in this? http://forum.xda-developers.com/showthread.php?t=1266885
Click to expand...
Click to collapse
I did! Extra carefully making sure to wipe everything as usual - this is my second or third ROM flash and only the first time I've seen something like this. After the phone reboot I tried to force the camera bug again so I could screenshot it for bilgerryan but it hasn't shown back up yet. Will be continuing to test, really loving this room so far I just wish it was as smooth as the one I was using previously (RemICS-UX ReVamped).
I guess it could be a bad dl. You might try down loading again over WiFi or hard line then reflashing.
CheesecakeRecipe said:
I did! Extra carefully making sure to wipe everything as usual - this is my second or third ROM flash and only the first time I've seen something like this. After the phone reboot I tried to force the camera bug again so I could screenshot it for bilgerryan but it hasn't shown back up yet. Will be continuing to test, really loving this room so far I just wish it was as smooth as the one I was using previously (RemICS-UX ReVamped).
Click to expand...
Click to collapse
Install a cache cleaner on Play Store and if it starts getting laggy clear your cache. There are a few of them that are one click and done. Plus you gotta let this ROM settle for a bit.
bilgerryan said:
Install a cache cleaner on Play Store and if it starts getting laggy clear your cache. There are a few of them that are one click and done. Plus you gotta let this ROM settle for a bit.
Click to expand...
Click to collapse
Will give it a shot after I set aside some time and check the build.prop gpu tweak you mentioned in the topic, even though that may be outdated and no longer needed by v6. I did however have the camera back-out glitch happen again. When leaving the camera, no icons or widgets render. I was able to fix it this time by reopening the camera from the lock screen and backing out, but still very irritating and interesting behavior.
CheesecakeRecipe said:
Will give it a shot after I set aside some time and check the build.prop gpu tweak you mentioned in the topic, even though that may be outdated and no longer needed by v6. I did however have the camera back-out glitch happen again. When leaving the camera, no icons or widgets render. I was able to fix it this time by reopening the camera from the lock screen and backing out, but still very irritating and interesting behavior.
Click to expand...
Click to collapse
Yeah it should not be needed in v6.. What are your CPU settings? If you haven't overclocked it you might wanna set it at 1.2 or 1.3 GHz. I haven't been able to reproduce the camera thing you are talking about. Chad might be right. Looks like a bad download.
What do you think, what is enhanced, what is ruined?
For begining, I want to say that i love new Sense Keyboard.
Sent from my HTC One S
This should be put in sticky jb thread this is gonna be locked
k1llacanon said:
This should be put in sticky jb thread this is gonna be locked
Click to expand...
Click to collapse
Sticky JB thread done its job...
Sent from my HTC One S
It's still doing its job and as the mods have stated over and over..any jb conversations go there don't start a New thread
Sent from my HTC VLE_U using xda app-developers app
Caller photo quality is OK how but photo is still small. Have the same size as before...
Sent from my HTC One S
Has someone got VILLE C2 Jelly Bean Update????
PopaStefanx said:
Has someone got VILLE C2 Jelly Bean Update????
Click to expand...
Click to collapse
Thanks, dude, I couldn't see the other posts, they are so tiny, you are literally my savior
On topic: No, S3 users will probably get it 2-3 weeks later, maybe more.
I saw, that some users reported having a brick with SuperCID, is this true?
Because I don't want to change my CID back and stuff
Busybox
Hi
Just updated via OTA, reinstalled CWM_Recovery and installed superSU 0.99.
Phone is rooted once again but it seems like busybox is unable to install, tried a few different versions and none seem to stick, a few even causes a crash/reboot of the phone.
Have a few programs that are reliant on Busybox to function.
Am i the only one with this problem ?
I think the update is rubbish. If anything its not as smooth as the Ics update, project butter must be a vanilla only experience because there is no way it's buttery smooth
Sent from my HTC One S using xda app-developers app
I'm really annoyed about the new keyboard layout which was an utterly unnecessary change. Not to mention that the keyboard is somewhat laggy. Apart from that it's fine and I could live with it if I would get back full root functionality.
By the way, has anyone solved their root issues (SuperSU, Busybox, and a couple other apps and tools not working) yet?
xsatquest said:
Hi
Just updated via OTA, reinstalled CWM_Recovery and installed superSU 0.99.
Phone is rooted once again but it seems like busybox is unable to install, tried a few different versions and none seem to stick, a few even causes a crash/reboot of the phone.
Have a few programs that are reliant on Busybox to function.
Am i the only one with this problem ?
Click to expand...
Click to collapse
Nope I'm also having the same issues. After reading over the superSU thread it seems like HTC have done something to prevent system changes so it's basically a case of waiting until some devs find a work around
Is there an app to reorder the notifications in the notificationbar? I have 2 apps as trigger and new notifications are in the middle of these apps. I want new notifications at bottom.
Haven't got the update yet, but I'd like to know if they solved the touchbutton issue? And does USB OTG work now without extra cables? The only 2 things I'm missing.
Touch button issue is better so far but cannot say for sure that it is fixed, since now we have the Google now issue but not as frequently as before.
The new issue for me after the update is that the hands-free control is not customisable through apps after update, only single click function works for me, no track skipping or volume control
Sent from my HTC One S using Tapatalk 2
The worst update I've made on any phone....ever!
I need to downgrade ASAP, however, because I'm a relative noob and I'm unrooted I need some assistance. Any advice will be appreciated.
Just installed and had 10 minutes with it. To me my phone definitely seems a little quicker and more responsive, might just be me being excited about new stuff though! I use Swiftkey so never touch the Sense keyboard, I just gave the new one a quick go and switched back to Swiftkey, I can type on it almost as quick as a real keyboard so it would take something amazing to shift me from it. I like what I see of Google Now so far, we'll see how it pans out though. The camera changes seem good, fairly subtle differences but I think it's quicker too. I like the power saver mode, think that will be a useful one. Switching off data when the screen is off is a great feature.
So far, so good.
captaineasychord said:
Just installed and had 10 minutes with it. To me my phone definitely seems a little quicker and more responsive, might just be me being excited about new stuff though! I use Swiftkey so never touch the Sense keyboard, I just gave the new one a quick go and switched back to Swiftkey, I can type on it almost as quick as a real keyboard so it would take something amazing to shift me from it. I like what I see of Google Now so far, we'll see how it pans out though. The camera changes seem good, fairly subtle differences but I think it's quicker too. I like the power saver mode, think that will be a useful one. Switching off data when the screen is off is a great feature.
So far, so good.
Click to expand...
Click to collapse
Which processor do you have? S3 or S4? And have you played any games on it? Subway Surfer was quite quick and smooth on ICS, with Jellybean it's like a buffering movie on one of them crappy Chinese servers....
RootJunkie said:
Which processor do you have? S3 or S4? And have you played any games on it? Subway Surfer was quite quick and smooth on ICS, with Jellybean it's like a buffering movie on one of them crappy Chinese servers....
Click to expand...
Click to collapse
I noticed that! Subway surfer was laggy on the JB update. Restored my ICS rom and it's smooth as butter. WTF! And it's bound to be s4 because the s3 doesn't have it yet
I am pretty fond of the new No-Lockscreen option. Something I have missed from the AOSP versions, probably the only reason I will stick with sense on JB.
captaineasychord said:
Just installed and had 10 minutes with it. To me my phone definitely seems a little quicker and more responsive, might just be me being excited about new stuff though! I use Swiftkey so never touch the Sense keyboard, I just gave the new one a quick go and switched back to Swiftkey, I can type on it almost as quick as a real keyboard so it would take something amazing to shift me from it. I like what I see of Google Now so far, we'll see how it pans out though. The camera changes seem good, fairly subtle differences but I think it's quicker too. I like the power saver mode, think that will be a useful one. Switching off data when the screen is off is a great feature.
So far, so good.
Click to expand...
Click to collapse
Not sure, but since data is off while screen off, how come I receive my whatsapp messages, emails n stuff? I am just curious, since I read about power saver a while ago in One X forum, but forgot that and you reminded it to me.
P.s: I have power saver on since the update
Sent from my HTC One S using Tapatalk 2