Related
I'm sure many of you will be happy about this.
App FC's fixed once and for all.
Issues:
? and sym keys
Other than that, nothing.
CHANGELOG
1.00
Kanged daniel60104's fixes on 3rd sense and data2ext
cleaned some stuff up
couple speed tweaks
proper .32 kernel
fixed pretty much everything except ? and sym keys
0.87
Fixed most if not all FC's.
0.86
Fixed SD card mounting
0.85
Fixed sound, live wallpapers, other little things.
ROM will now ask what language you want upon first boot.
Does not require you to be running a previous version.
0.84
Fixed keyboard lights, other random things.
This is based off a Chinese leak of the HTC Gratia ROM.
Download: 1.0
Video:
http://www.youtube.com/watch?v=TIrFbL8-EvI
Just to clarify, touchscreen works
As seen on AndroidCommunity http://androidcommunity.com/gratiou...froyo-on-the-customizable-htc-sense-20101024/
And soon after, on TalkAndroid http://www.talkandroid.com/19014-gratious-slide-0-8-leaked-out-for-froyo-and-htc-sense/
Thanks To:
Kernelzilla for helping me get started.
Eugene_373 for pointing me in the right direction on SD issues
etu_aty for being so supportive
everyone in #mytouchslide on irc.freenode.net
Edit: Just to be clear, Daniel60104 deserves just as much, if not more, credit as I do on this whole Froyo Sense movement. Though I posted the first ROM, if it wasn't for Daniel, we wouldn't have working kb lights, front lights, wifi, etc.
So please, before you thank me, thank him for keeping this alive while I was too busy to work on anything.
Besides wifi what would be some other issues. Cause i have a diffrent rom booted on my phone and im pretty pleased with it. So i just want to be clarified.
immortalxgod said:
Besides wifi what would be some other issues. Cause i have a diffrent rom booted on my phone and im pretty pleased with it. So i just want to be clarified.
Click to expand...
Click to collapse
Not many that I've noticed. The only issues i've noticed are wifi, kb lights, and the ? and sym keys like in early froyo roms. Those should be easy fixes.
It looks cool, but your video is backwards. LMAO!
heybobitsme said:
It looks cool, but your video is backwards. LMAO!
Click to expand...
Click to collapse
lmao yeah I know, stupid apple I'll post a non-backwards version soon.
OMG, This is AWESOME !! Thanks, I could care less about the issues no wifi and the keyboard issue I'm sure will be resolved as soon as one of you awesome Devs get a hold of this thing.
THANK YOU !!!
*edit* - Flashing now !
love it but...
Love the rom the only thing.. and its a BIG issue, is my sd card isn't recognized as being there. I read somewhere that this leak has that problem just was hoping it had been fixed with this rom's release.
Sha0ggy said:
Love the rom the only thing.. and its a BIG issue, is my sd card isn't recognized as being there. I read somewhere that this leak has that problem just was hoping it had been fixed with this rom's release.
Click to expand...
Click to collapse
Yeah I just noticed this as well, and I can't deal with that either. I just tried a fix. Not sure yet if it worked, but it's booting as I type. Threw in a couple different things too. If it worked, I'll post up the new version.
Edit: Nevermind, didn't boot.
Sorry guys, in between taking care of a 9 month old baby, wrestling practice, and more schoolwork than I've ever had, it's hard to find time for eating, let alone Android You guys mean a lot to me though. I'll do my best to fix this a.s.a.p.
I found the issue as well NO SD Card support. That's a deal breaker for me.... And Miguel, that's awesome and I'm sure people will be patient in waiting for a fix. Thanks !
I love you. Btw, what are the flying greyscaled boxes floating around on the homescreen
Sent from my HTC Hero using XDA App
wow great work! i would love to try this rom but sd support and wifi are necessities for me, but its great to see people contributing to this forum
Wow, great rom apart from no wifi and the inability to read the SD card. It's super smooth and stable oh and its Froyo!
Ahh, another problem, callers can't hear me and vise versa.
Sent from my HTC Hero using XDA App
uzi132 said:
Ahh, another problem, callers can't hear me and vise versa.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Really? Now that's really odd. Are you sure its not your signal? I'd test but I get no service where I'm at right now, so I nandroided back to cm6 so I can keep up with the thread.
Sent from my T-Mobile myTouch 3G Slide using XDA App
uzi132 said:
Ahh, another problem, callers can't hear me and vise versa.
Click to expand...
Click to collapse
Yup having the same problem
illfxckinqwill said:
Yup having the same problem
Click to expand...
Click to collapse
Alright thanks for helping me test guys
So so far the issues I'm aware of are:
Wifi
Kb lights
? and sym keys
No sound in phone.
SD Card Mounting
If there's anything else, please let me know.
And the weather animations I guess they're called, when you unlock phone and not touch it the weather animation appears but in grey
Sent from my HTC Hero using XDA App
please get this rom working!
migueltherocker said:
I'm sure many of you will be happy about this.
http://www.mediafire.com/?9afcbal1dfcb8rp
Issues:
Wifi (for now)
Other tidbits
There's some really cool stuff in here.
WHEN YOU BOOT:
It will be in chinese.
When it's done booting, go to settings, scroll down to the A symbol, press the first option, then select english. then you're golden
This is based off a Chinese leak of the HTC Gratia ROM.
Video:
http://www.youtube.com/watch?v=TIrFbL8-EvI
Just to clarify, touchscreen works
As seen on AndroidCommunity http://androidcommunity.com/gratiou...froyo-on-the-customizable-htc-sense-20101024/
And soon after, on TalkAndroid http://www.talkandroid.com/19014-gratious-slide-0-8-leaked-out-for-froyo-and-htc-sense/
Click to expand...
Click to collapse
great start man i thought you would be the one to start work on this lol
migueltherocker said:
Alright thanks for helping me test guys
So so far the issues I'm aware of are:
Wifi
Kb lights
? and sym keys
No sound in phone.
SD Card Mounting
If there's anything else, please let me know.
Click to expand...
Click to collapse
i wonder if the sdcard mounting problem comes from the fact that when applying this update it is writing something to the sdcard? this is the first time ive ever seen a rom do this.
also the fact that the build.prop is reading wrong i wonder if changing language and region to en and US will boot it up in english. also changing the hero to espresso inside it as well may help somewhat
Does any of the rom's have a mic working?
I've just installed S-voice and want to test it.
Thanks
No. It's a hardware/driver issue across the board.
Sent from my rezound
try use the webos
adder101 said:
Does any of the rom's have a mic working?
I've just installed S-voice and want to test it.
Thanks
Click to expand...
Click to collapse
Some of the CM7 roms had limited success with the mic but CM9 isn't ready yet
And S-voice won't work in webos lol
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
rkaede said:
try use the webos
Click to expand...
Click to collapse
s-voice for ics only, even then it had to be modified as its exclusive for Samsung s3.
If it worked in gb even if it was not that good, surely it could be made to work in ics.
Though the installation of s-voice was without any problems.
x000x said:
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
Click to expand...
Click to collapse
Mic and camera are at the bottom of the pile of things to do, getting an OS that was never designed for the TouchPad is no easy thing, drivers and wrappers have to be written from scratch with no support from HP. So have faith in the developers, remember most of them are either at full time work or school/college and are offering you there work for free, maybe you could ask HP to fix the camera and mic I think they would abandon that idea faster than they abandoned the TouchPad itself.
x000x said:
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
Click to expand...
Click to collapse
BIGSimon said:
Mic and camera are at the bottom of the pile of things to do, getting an OS that was never designed for the TouchPad is no easy thing, drivers and wrappers have to be written from scratch with no support from HP. So have faith in the developers, remember most of them are either at full time work or school/college and are offering you there work for free, maybe you could ask HP to fix the camera and mic I think they would abandon that idea faster than they abandoned the TouchPad itself.
Click to expand...
Click to collapse
Exactly what BIGSimon said. CM9 is still ALPHA. Meaning some things will not work. Not everything that is released is perfect right away. Developing ROMs isn't always an easy task. What they have done in 5 months is pretty damn great.
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
x000x said:
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
Click to expand...
Click to collapse
There's a big difference between Android 2.3.7 gingerbread and Android 4.0.4 ice cream sandwich which meant everything had to be re-written to work Android 5 jelly bean is more of an evolution of ICS so drivers will carry over, all the work that's been done now will mean that when JB is released the touchpad will get it a lot faster with everything working
Sent from my HTC Wildfire using Tapatalk 2
x000x said:
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
Click to expand...
Click to collapse
JellyBean will be a minor update, it will have a version 4.1, it isn't as huge step as going from 2.3 to 4.0.
Anyway, sound is surely being worked on (developers (partially, maybe) have gotten rid of bad screen-off sound issue last week), and we will see some progress in a time. If you want a tablet with all features working out-of-the-box, i guess, you should buy another device.
The latest audiolibs seems to be working great. Too bad S-Voice is having connection problems. Anyone know how to resolve the server issues in S-Voice?
+ 1 ;-)
BuffMcBigHuge said:
The latest audiolibs seems to be working great. Too bad S-Voice is having connection problems. Anyone know how to resolve the server issues in S-Voice?
Click to expand...
Click to collapse
Do you have your device spoofed to be a galaxy s3? I think you need to that for it to work
jsgraphicart said:
Do you have your device spoofed to be a galaxy s3? I think you need to that for it to work
Click to expand...
Click to collapse
I was able to get it working by flashing this:
http://forum.xda-developers.com/showthread.php?t=1667046
Works wonderfully with the new audiolib!
Is there a flashable audiolib somewhere?
--update--
Found it
http://goo.im/devs/jcsullins/cmtouchpad/testing
Sent from my SGH-T989 using Tapatalk 2
Izeltokatl said:
Is there a flashable audiolib somewhere?
--update--
Found it
http://goo.im/devs/jcsullins/cmtouchpad/testing
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Nighlyy 0620 has everything mic needs already included.
Wanna play some games with a Wii Remote on your Rezound?
A lot of you were wanting to connect a Wii Remote to your Rezound (myself included) and several were annoyed and rather upset to find that Sense UI just doesn't do the job. Sense masks the necessary drivers. Well I have good news, but it's obviously not going to work with every ROM. Needless to say, it'll take some playing with. If you have a Sense based ROM, you'll probably have a harder time; though, the ROM I am using is not completely Senseless, so who knows... you may luck up!
What I am using:
CleanROM Developer Edition 1.4
3.13xx Kernel from the same developer and post.
ICS Firmware (Not sure if this will matter or not.)
It took some playing with, but I finally got my Wii controller to connect. Here's what you do. Go to the links below.
First:
Here
Second:
Here
You can get it from the market, but you have to have the second link in order for the Wii driver to be recognized by the program.
Before going into the program... let me save you some time. Go into a text field in a program, type "0000" and copy that text. You'll use this later.
Once you have these installed, it gets tricky.
1) Do NOT turn on bluetooth first... open the program and let the program start bluetooth using the check box.
2) Once BT is turned on, tap "Select IME", Select "Bluez IME"
3) Tap "Select Device"
4)Scan. Press 1 + 2 buttons simultaneously on the controller. The address for your controller should show up. Tap on it.
It will now ask you to confirm pairing with bluetooth device, open that dialog box. While the dialog box for accepting the bluetooth device is up, paste the text you copied earlier into the text field and hit "OK." (The controller may stop pairing, and the dialog box may go away, don't panic.) By default, the PIN is 0000. If you can type it, do so. If not, it'll probably still work (I didn't actually have to type it in, it just started working. )
Okay, now that you have it semi-paired, you'll only tap on "Select IME" from now on. When you tap it and select a different input method, it will automatically turn bluetooth off. Likewise, when you tap "Select IME" and select "Bluez IME," it will turn bluetooth on and display "Connecting to XX.XX.XX.XX" (<-- your Wii remotes address here). At this point, simply press 1 + 2 and it should display connected. To test if it's working, simply scroll through the menu using the d-pad. That's it!
This is my first walkthrough and I apologize if it's hard to understand! It goes without saying that I am not responsible for what you do to your phone. But it should all go smoothly!
Let us all know if you have come up with any better solutions and I'll update accordingly! Enjoy guys!
Here is a video as proof to the nay-sayers!
Wii Remote with HTC Rezound
Will give this a try. Does this support only the main remote or does the attachment with the analog stuck work also?
vudu said:
Will give this a try. Does this support only the main remote or does the attachment with the analog stuck work also?
Click to expand...
Click to collapse
I have 2 Wii remotes, one is original Nintendo, the other is after market. I got both of them to work. I have not tried the nun-chuck with it, but I know some of the emulators have an option for it. I'm assuming the nun-chuck works with other phones using this program, so I don't see how it wouldn't work. I'll probably try that out tomorrow.
Edit: The nun-chuck does in fact work with it. I plugged mine up before pairing, and it had no effect on pairing. Works great with Mario 3!
thanks for the write up. i have a freind thats been tyring to get this to work with no luck. i am going to give this a shot myself
did not work for me same rom as you bud and kernel too but it keeps saying connection refused
snowman122 said:
did not work for me same rom as you bud and kernel too but it keeps saying connection refused
Click to expand...
Click to collapse
Are you on ICS Firmware? Also, at what point is it saying that? Before it recognizes the device or after an attempt to pair?
sanders858 said:
Are you on ICS Firmware? Also, at what point is it saying that? Before it recognizes the device or after an attempt to pair?
Click to expand...
Click to collapse
nope still on gb firmware and when it tries to pair!
snowman122 said:
nope still on gb firmware and when it tries to pair!
Click to expand...
Click to collapse
I don't know all the changes they made with the firmware update, but I would assume that bluetooth was one of the changes made. I say that because before the firmware leak, devs were having issues getting BT to work with the ICS Roms. So, that being said, this may only be possible with the firmware update. Keep in mind, however, that I had to play with it quite a bit to get it to work. It was totally worth it though, I was playing Supe Mario 64 on my phone with the nun-chuck and all. Flawless performance!
sanders858 said:
I don't know all the changes they made with the firmware update, but I would assume that bluetooth was one of the changes made. I say that because before the firmware leak, devs were having issues getting BT to work with the ICS Roms. So, that being said, this may only be possible with the firmware update. Keep in mind, however, that I had to play with it quite a bit to get it to work. It was totally worth it though, I was playing Supe Mario 64 on my phone with the nun-chuck and all. Flawless performance!
Click to expand...
Click to collapse
i guess ima keep trying as soon as my new digitizer gets here i have a humongous scratch on my phone and cant see the screen to well!
snowman122 said:
i guess ima keep trying as soon as my new digitizer gets here i have a humongous scratch on my phone and cant see the screen to well!
Click to expand...
Click to collapse
Oh you're the one that accidentally dropped it while it slid on the ground with a small rock under it?
Moderators please note that I do in fact read.
sanders858 said:
Oh you're the one that accidentally dropped it while it slid on the ground with a small rock under it?
Moderators please note that I do in fact read.
Click to expand...
Click to collapse
yeah it sucks man!!
Dude I got it to work on newts Rom!!! Only thing when it does connect the lights on the remote won't stop flashing so it's gonna kill battery. Any ideas?
Sent from my ICS Rezound
LakerStar25 said:
Dude I got it to work on newts Rom!!! Only thing when it does connect the lights on the remote won't stop flashing so it's gonna kill battery. Any ideas?
Sent from my ICS Rezound
Click to expand...
Click to collapse
Yeah they are going to keep blinking I remember in used the Wii controller on my incredible lights will keep blinking buddy
Sent from my ADR6425LVW using XDA
Yeah mine have always blinked with all my phones. Not sure how much drain it's actually going to have though. Glad to hear you got it working though! Are you on the new firmware?
Sent from my ADR6425LVW using XDA
cant get it working on mine in my sig. not sure if bluetooth is working in general though so that might be it.
if this works on ICS that would be cool
yojoe600 said:
if this works on ICS that would be cool
Click to expand...
Click to collapse
I'm using ICS now, but I see what you're saying. When we get the official ICS ota, the devs are going to start pushing out truly senseless roms and they will likely have no problem doing this (because of the ics kernel.) Fully ASOP roms can supposedly do this natively.
Sent from my ADR6425LVW using XDA
sanders858 said:
I'm using ICS now, but I see what you're saying. When we get the official ICS ota, the devs are going to start pushing out truly senseless roms and they will likely have no problem doing this (because of the ics kernel.) Fully ASOP roms can supposedly do this natively.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Yes they can.
sanders858 said:
Yeah mine have always blinked with all my phones. Not sure how much drain it's actually going to have though. Glad to hear you got it working though! Are you on the new firmware?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Cool thanks I won't worry about the lights then. Yea I'm on newest leaked firmware running Newts One XxX RLS1.
Sent from my ICS Rezound
LakerStar25 said:
Cool thanks I won't worry about the lights then. Yea I'm on newest leaked firmware running Newts One XxX RLS1.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Awesome. It's looking like the new firmware is the key. I haven't tried it with a Sense ROM, if be interested to see if it works with Sense and ICS firmware.
Sent from my ADR6425LVW using XDA
I'm hoping someone else has already solved this issue, but I seem to be running into serious problems with AOSP CM ROMs with regards to the power button. Recently I actually bricked my original EVO 4G LTE and got a "new" one via the insurance replacement program with Sprint. I immediately obtained rooted, installed recovery, and obtained S-off. I then proceeded to install CM10.2 (deck's build) and am actually still running 9/20 version of this ROM.
My problem with the power-button is that it sometimes does not respond to a press where it may not wake the screen or sleep the screen. Sometimes it takes 2, 3 or more presses to get it to respond. Additionally, sometimes after the screen sleeps it will immediately wake again. It's as if the button is not properly de-bounced. My first thought was that the power-button was physically broken.
So as an experiment I rolled back to previous versions of CM10.1 and got the same results, even after clean flashes. Then I tried rolling back the stock ROM which came with the phone, from a nandroid backup. Shockingly, no power button issues at all. So with a sense based ROM, it seems to work perfectly, but a AOSP based ROM (specifically, CM10.x) I see the issues.
Could this be a kernel issue? Anyone else seen or resolved this issue already?
Thanks. Sincerely,
Frustrated.
Yeah I have that sometimes too although occasionally it won't even wake up and will have shut off by itself
Sent from my EVO using xda app-developers app
Promising update.
I updated the latest TP firmware from Captain Throwback, on a whim. While it doesn't seem to have fixed the issue, it seems much improved. The jury is still out - and it's only been an hour or so since I installed, so this is hardly enough data to say definitively. But promising.
FW is here: http://tinyw.in/cRCf
nebhead said:
Promising update.
I updated the latest TP firmware from Captain Throwback, on a whim. While it doesn't seem to have fixed the issue, it seems much improved. The jury is still out - and it's only been an hour or so since I installed, so this is hardly enough data to say definitively. But promising.
FW is here: http://tinyw.in/cRCf
Click to expand...
Click to collapse
Yup, spoke too soon. Still having issues. The search continues.
I just got a replacement evo lte and my power button sucks.. I gotta hold it down for a few seconds to wake or lock and that was before root.. I'm rooted now and on sense 5 r145 but I use the swipe to unlock and lock and it works great.. I said forget the power button...
Sent from my EVO using xda app-developers app
hondafreak513 said:
I just got a replacement evo lte and my power button sucks.. I gotta hold it down for a few seconds to wake or lock and that was before root.. I'm rooted now and on sense 5 r145 but I use the swipe to unlock and lock and it works great.. I said forget the power button...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
So your power button was bad with the stock ROM too? That's a bummer. At least mine seems to work OK with the stock ROM. Maybe I should try some modified stock ROMs to see if there is a difference there.
You're not alone. My brother and I both have EVO's and we're both experiencing this issue. It's annoying as hell having to press the power button multiple times to wake the device. Didn't start having this issue until the end of the CM.1 cycle. I also went back to Sense and found no problems. It only appears to occur on non sense ROMs. Does anyone have any insight to this or possibly a fix?
It's a kernel issue. That problem did not pop up until the 3.4 kernels started coming out.
AndrasLOHF said:
It's a kernel issue. That problem did not pop up until the 3.4 kernels started coming out.
Click to expand...
Click to collapse
Well that's great news (sort-of) and means that some day someone could potentially resolve this in the kernel. Maybe we need to X-Post with the CM10.2 development forum, unless they are already aware and are working on this.
nebhead said:
I'm hoping someone else has already solved this issue, but I seem to be running into serious problems with AOSP CM ROMs with regards to the power button.
Could this be a kernel issue? Anyone else seen or resolved this issue already?
Click to expand...
Click to collapse
There were certain nightly/kernel mixes with the 10.2 and Haunted kernel that seemed to clear it up for me.
I can't for the life of me remember which combination. Sorry.
One thing that alleviated that for me a bit was enabling "Volume Buttons Wake Up Handset" or whatever it was.
physix said:
There were certain nightly/kernel mixes with the 10.2 and Haunted kernel that seemed to clear it up for me.
I can't for the life of me remember which combination. Sorry.
One thing that alleviated that for me a bit was enabling "Volume Buttons Wake Up Handset" or whatever it was.
Click to expand...
Click to collapse
Cool, I think I may try the Haunted Kernel. Nandroiding first of course. I will report back later.
Yeah try a new kernel and use kernel tuner and turn on the Swype to wake option it is pretty cool..
Sent from my EVO using xda app-developers app
Haunted Kernel 31 + Unofficial CM10.2 9/20 Build (Deck) appears to still have issues. Although it seems a bit better than before. As to whether this introduces new issues, I'm not sure yet.
The work on the kernel is ongoing. Trust me, it's way better than it was before.
Captain_Throwback said:
The work on the kernel is ongoing. Trust me, it's way better than it was before.
Click to expand...
Click to collapse
Yup, expected to have a few hiccups using bleeding edge ROMs & kernels. Glad to hear that these types of things are being addressed. The Haunted kernel definitely makes things much, much better. It's definitely daily driver quality now.
As a side note, I've also noted that the WiFi seems to work better with the Haunted kernel as well. Not sure if that's related, but where I used to have difficulty staying connect to WiFi at home and at work, it now seems rock solid. Still a bit too early to be definitive, but so far so good.
nebhead said:
Yup, expected to have a few hiccups using bleeding edge ROMs & kernels. Glad to hear that these types of things are being addressed. The Haunted kernel definitely makes things much, much better. It's definitely daily driver quality now.
As a side note, I've also noted that the WiFi seems to work better with the Haunted kernel as well. Not sure if that's related, but where I used to have difficulty staying connect to WiFi at home and at work, it now seems rock solid. Still a bit too early to be definitive, but so far so good.
Click to expand...
Click to collapse
Haunted Kernel is still behind some, last I checked. So while you may have some benefits, you will lose/miss some fixes/optimizations. But to each his own.
Captain_Throwback said:
Haunted Kernel is still behind some, last I checked. So while you may have some benefits, you will lose/miss some fixes/optimizations. But to each his own.
Click to expand...
Click to collapse
Good to know. I will keep flashing and keep trying the new builds as they become available. For now, this seems to be a good combo for me. The current Haunted governor actually kinda seems to be draining the battery fast so I may tweak that. Anyway, thanks for all the responses here, this has really enlightened me on this issue.
Hey.. I'm behind for a reason
Sent from my EVO using Tapatalk now Free
Boy, the DNA forums have been a ghost town these past few weeks.
I'm a long time flasher of several different ROMs (currently on Liquid), but I'm really getting the itch for 5.0. Are we waiting for the GP HTC One to get 5.0 (then port it to the DNA), waiting for ASOP (like CM) to finish their framework, or is the DNA "too old" and have the devs moved on to newer devices? I'm starting to consider a Nexus 6, but really the DNA is a fine piece of hardware and it's a shame to toss it.
Thanks for any thoughts
Fightermelee said:
Boy, the DNA forums have been a ghost town these past few weeks.
I'm a long time flasher of several different ROMs (currently on Liquid), but I'm really getting the itch for 5.0. Are we waiting for the GP HTC One to get 5.0 (then port it to the DNA), waiting for ASOP (like CM) to finish their framework, or is the DNA "too old" and have the devs moved on to newer devices? I'm starting to consider a Nexus 6, but really the DNA is a fine piece of hardware and it's a shame to toss it.
Thanks for any thoughts
Click to expand...
Click to collapse
Try this:
I managed to mess up bluetooth, so that's not currently working. But that's the main fail I've found so far. Test away. Let me know what doesn't work. At your own risk. I've been running it for a few days without any other hiccups.
EOS Droid DNA Lollipop ROM: http://daniel.johanssons.net/downloa...FICIAL-dlx.zip
And you'll need to flash this before rebooting: http://download.chainfire.eu/632/Sup...erSU-v2.30.zip
And you'll need some gapps: https://s.basketbuild.com/gapps
I flash all 3 at one time without any issues so far. But ROM+SuperSU is a must for now, or screen will lock up after a little bit. Tested flashing on both twrp 2.7+ and 2.8
mopartonyg said:
Try this:
I managed to mess up bluetooth, so that's not currently working. But that's the main fail I've found so far. Test away. Let me know what doesn't work. At your own risk. I've been running it for a few days without any other hiccups.
EOS Droid DNA Lollipop ROM: http://daniel.johanssons.net/downloa...FICIAL-dlx.zip
And you'll need to flash this before rebooting: http://download.chainfire.eu/632/Sup...erSU-v2.30.zip
And you'll need some gapps: https://s.basketbuild.com/gapps
I flash all 3 at one time without any issues so far. But ROM+SuperSU is a must for now, or screen will lock up after a little bit. Tested flashing on both twrp 2.7+ and 2.8
Click to expand...
Click to collapse
Awesome thanks man! I'll flash it on Monday and let you know what happens! I didn't honestly expect a ROM so fast lol
mopartonyg said:
Try this:
I managed to mess up bluetooth, so that's not currently working. But that's the main fail I've found so far. Test away. Let me know what doesn't work. At your own risk. I've been running it for a few days without any other hiccups.
EOS Droid DNA Lollipop ROM: http://daniel.johanssons.net/downloa...FICIAL-dlx.zip
And you'll need to flash this before rebooting: http://download.chainfire.eu/632/Sup...erSU-v2.30.zip
And you'll need some gapps: https://s.basketbuild.com/gapps
I flash all 3 at one time without any issues so far. But ROM+SuperSU is a must for now, or screen will lock up after a little bit. Tested flashing on both twrp 2.7+ and 2.8
Click to expand...
Click to collapse
Heading to http://daniel.johanssons.net/downloa...FICIAL-dlx.zip prompts me for a login to view/download the file. Is it any trouble to throw the ROM onto mega or an equivalent? Thanks and sorry
Fightermelee said:
Heading to http://daniel.johanssons.net/downloa...FICIAL-dlx.zip prompts me for a login to view/download the file. Is it any trouble to throw the ROM onto mega or an equivalent? Thanks and sorry
Click to expand...
Click to collapse
Does for me to, not sure why. Go to original thread page 9 for all down loads. just tried it works ok.
http://forum.xda-developers.com/showthread.php?t=2766239
Fightermelee said:
Heading to http://daniel.johanssons.net/downloa...FICIAL-dlx.zip prompts me for a login to view/download the file. Is it any trouble to throw the ROM onto mega or an equivalent? Thanks and sorry
Click to expand...
Click to collapse
It looks like the link didn't get copied over properly over here. It links to download...ficial-dlx.zip, which is obviously not right.
Try this: http://daniel.johanssons.net/downloads/eos-5-20141127-UNOFFICIAL-dlx.zip
Or you can just go to my main page and the dlx builds will be on the bottom @ daniel.johanssons.net
danjull said:
It looks like the link didn't get copied over properly over here. It links to download...ficial-dlx.zip, which is obviously not right.
Try this: http://daniel.johanssons.net/downloads/eos-5-20141127-UNOFFICIAL-dlx.zip
Or you can just go to my main page and the dlx builds will be on the bottom @ daniel.johanssons.net
Click to expand...
Click to collapse
AWESOME thanks a lot! Will reply to this thread after a few days with the results!
So I couldn't wait for Monday for the Lollipop goodness and flashed the other day. Was nervous with a weird error in CWM when flashing, but after 3-4 minutes it finished successfully with no intervention on my side. Bootup took a few minutes too (~5), for anyone who give this a try . Just hang out and let it do its thing.
The ROM runs great. I had some issues with Bluetooth (known issue though), but otherwise it's very stable. There's really no extra options in this build, and unfortunately that was a dealbreaker for me (my power button doesn't work, and I need "volume to unlock"). I wish I could have rode this bull longer.
Happy to know that support isn't completely dead yet! I'll be lurking some more for when more builds come! Thanks again to everyone.
Fightermelee said:
So I couldn't wait for Monday for the Lollipop goodness and flashed the other day. Was nervous with a weird error in CWM when flashing, but after 3-4 minutes it finished successfully with no intervention on my side. Bootup took a few minutes too (~5), for anyone who give this a try . Just hang out and let it do its thing.
The ROM runs great. I had some issues with Bluetooth (known issue though), but otherwise it's very stable. There's really no extra options in this build, and unfortunately that was a dealbreaker for me (my power button doesn't work, and I need "volume to unlock"). I wish I could have rode this bull longer.
Happy to know that support isn't completely dead yet! I'll be lurking some more for when more builds come! Thanks again to everyone.
Click to expand...
Click to collapse
All that is in the works. Lollipop changed quite a bit, so it's not just a quick implementation. But it's coming.
Looking forward to it! No rush thanks again
Pinning Apps problem
mopartonyg said:
Try this:
I managed to mess up bluetooth, so that's not currently working. But that's the main fail I've found so far. Test away. Let me know what doesn't work. At your own risk. I've been running it for a few days without any other hiccups.
Click to expand...
Click to collapse
The rom looks great, except when pinning an app, you get stuck, because long pressing the 'back' and 'overview' buttons doesn't unlock the device.
Is there a way to add more options for configuring the recent apps button?
In CM11, I configured recent apps to work as a menu button, and long press home to work as a recent apps switcher. Much more useful in my opinion.
prrlhkr said:
The rom looks great, except when pinning an app, you get stuck, because long pressing the 'back' and 'overview' buttons doesn't unlock the device.
Is there a way to add more options for configuring the recent apps button?
In CM11, I configured recent apps to work as a menu button, and long press home to work as a recent apps switcher. Much more useful in my opinion.
Click to expand...
Click to collapse
sorry i am not the person to ask
prrlhkr said:
The rom looks great, except when pinning an app, you get stuck, because long pressing the 'back' and 'overview' buttons doesn't unlock the device.
Is there a way to add more options for configuring the recent apps button?
In CM11, I configured recent apps to work as a menu button, and long press home to work as a recent apps switcher. Much more useful in my opinion.
Click to expand...
Click to collapse
Fightermelee said:
So I couldn't wait for Monday for the Lollipop goodness and flashed the other day. Was nervous with a weird error in CWM when flashing, but after 3-4 minutes it finished successfully with no intervention on my side. Bootup took a few minutes too (~5), for anyone who give this a try . Just hang out and let it do its thing.
The ROM runs great. I had some issues with Bluetooth (known issue though), but otherwise it's very stable. There's really no extra options in this build, and unfortunately that was a dealbreaker for me (my power button doesn't work, and I need "volume to unlock"). I wish I could have rode this bull longer.
Happy to know that support isn't completely dead yet! I'll be lurking some more for when more builds come! Thanks again to everyone.
Click to expand...
Click to collapse
danjull said:
All that is in the works. Lollipop changed quite a bit, so it's not just a quick implementation. But it's coming.
Click to expand...
Click to collapse
..