Related
so as the title,I have flashed the newest fw and flash Sense roms &GPE roms from many teams like ARHD Inscertcoin Ordroid etc.I:silly: hope to experience the speed of ART ,so after a new rom is flashed with a full wipe,I changed the runtime into ART and roboot as required,but I've NEVER seen it is booting to the system:crying::crying::crying:,it aaways stuck on the bootanimation,I used to wait up to 1.5hours ,but it was still on the bootanimation
Anyone has the same problem?:cryingr just me?
stszf9124 said:
so as the title,I have flashed the newest fw and flash Sense roms &GPE roms from many teams like ARHD Inscertcoin Ordroid etc.I:silly: hope to experience the speed of ART ,so after a new rom is flashed with a full wipe,I changed the runtime into ART and roboot as required,but I've NEVER seen it is booting to the system:crying::crying::crying:,it aaways stuck on the bootanimation,I used to wait up to 1.5hours ,but it was still on the bootanimation
Anyone has the same problem?:cryingr just me?
Click to expand...
Click to collapse
ART is in development and should only be used by devs who want to test their app. Many users are reporting bootloop with ART while using a custom kernel (maybe this is your situation). I dont know if there is a way to switch back to dalvik without booting. So you might want to do a fresh install of your rom again from recovery.
stszf9124 said:
so as the title,I have flashed the newest fw and flash Sense roms &GPE roms from many teams like ARHD Inscertcoin Ordroid etc.I:silly: hope to experience the speed of ART ,so after a new rom is flashed with a full wipe,I changed the runtime into ART and roboot as required,but I've NEVER seen it is booting to the system:crying::crying::crying:,it aaways stuck on the bootanimation,I used to wait up to 1.5hours ,but it was still on the bootanimation
Anyone has the same problem?:cryingr just me?
Click to expand...
Click to collapse
You waited for 1.5 hrs? LOL!
nukeman239 said:
You waited for 1.5 hrs? LOL!
Click to expand...
Click to collapse
Perhaps it needed a bit longer?
stszf9124 said:
so as the title,I have flashed the newest fw and flash Sense roms &GPE roms from many teams like ARHD Inscertcoin Ordroid etc.I:silly: hope to experience the speed of ART ,so after a new rom is flashed with a full wipe,I changed the runtime into ART and roboot as required,but I've NEVER seen it is booting to the system:crying::crying::crying:,it aaways stuck on the bootanimation,I used to wait up to 1.5hours ,but it was still on the bootanimation
Anyone has the same problem?:cryingr just me?
Click to expand...
Click to collapse
I am a bit of a noob, however it is my understanding that ART only works on odexed ROMs. I think all Sense ROMs and most GPE ROMs are all deodexed, so that could be your issue. Try an odexed ROM, if one exists (I prefer Sense ROMs so I am not sure what is available for GPE).
Nope ART doesn't work on any sense ROM at all. It only works on GPE odexed
Sent from my HTCONE using Tapatalk
alray said:
ART is in development and should only be used by devs who want to test their app. Many users are reporting bootloop with ART while using a custom kernel (maybe this is your situation). I dont know if there is a way to switch back to dalvik without booting. So you might want to do a fresh install of your rom again from recovery.
Click to expand...
Click to collapse
yep .i did a full wipe before flash the roms,but still failed to run in ART ,gave up ,there 's the only way to back into dalvik is reboot to recovery and wipe /data
elvisypi said:
Nope ART doesn't work on any sense ROM at all. It only works on GPE odexed
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
tried GPE roms with odex.but still failed ,and I preffer Sense roms cuz China's network blocks most of the gapps
stszf9124 said:
tried GPE roms with odex.but still failed ,and I preffer Sense roms cuz China's network blocks most of the gapps
Click to expand...
Click to collapse
Just don't use ART you will notice no difference in overall performance atm
alray said:
Just don't use ART you will notice no difference in overall performance atm
Click to expand...
Click to collapse
Using ART with SinLessROM GE v5.1.3 currently and I do notice it is smoother and apps open a bit quicker.
You cannot have Xposed installed at all though. Whatsapp requires flashing a file to work though but performs
fine after.
After converting to art you can always convert back easily!
stszf9124 said:
so as the title,I have flashed the newest fw and flash Sense roms &GPE roms from many teams like ARHD Inscertcoin Ordroid etc.I:silly: hope to experience the speed of ART ,so after a new rom is flashed with a full wipe,I changed the runtime into ART and roboot as required,but I've NEVER seen it is booting to the system:crying::crying::crying:,it aaways stuck on the bootanimation,I used to wait up to 1.5hours ,but it was still on the bootanimation
Anyone has the same problem?:cryingr just me?
Click to expand...
Click to collapse
Actually you can Enable ART runtime on any Stock ROM via recovery
taranfx said:
Actually you can Enable ART runtime on any Stock ROM via recovery[/URL]
Click to expand...
Click to collapse
If I installed cwm or twrp would I trip knox or loose warranty
( I am rooted knox 0×0) my rom is ANJ2 or should I change to ANG6 (I'm using the S5 ) SM-G900FD
THANKS
if u r using custom rom or custom kernel or xposed framwork.........so ART its not compatible with ! thats why
moudy75799 said:
If I installed cwm or twrp would I trip knox or loose warranty
( I am rooted knox 0×0) my rom is ANJ2 or should I change to ANG6 (I'm using the S5 ) SM-G900FD
THANKS
Click to expand...
Click to collapse
This is the htc one forums your in the wrong place
I upgraded my P1000 from cm-10.1-20131117-NIGHTLY-p1.zip to cm-11-20131210-NIGHTLY-p1.zip
After the update it was kinda working fine. Gapps did not work yet since I did not upgrade that yet, so I installed pa_gapps-full-4.4-20131126-signed.zip.
And rebooted.
That's where the trouble started.
Apps crashed and the P1000 did not startup fine.
I decided to do a full wipe, cleared all caches and re-flashed the P1000.
I does not start anymore (stays on the CM11 boot screen).
What did I miss?
It's not your fault.
It's many different but similar errors in past few days on experimental CM11 builds.
Read http://forum.xda-developers.com/showthread.php?t=2560605 for example.
MarviXDA said:
It's not your fault.
It's many different but similar errors in past few days on experimental CM11 builds.
Read http://forum.xda-developers.com/showthread.php?t=2560605 for example.
Click to expand...
Click to collapse
Thanks,
It seems I updated to CM11 a bit to early, having confidence
If there is someone having a glorious idea...I'm open to those, hehe....
I flashed back to cm10... Maybe it was a bit too early to go to CM11....
This thread can be closed
brenzef said:
I flashed back to cm10... Maybe it was a bit too early to go to CM11....
This thread can be closed
Click to expand...
Click to collapse
Your original problem was using PA GAPPS full. Its to big for the /system partition. You should use one of the BaNkS Gapps versions instead. CM11 runs extremely well on SGT 7, especially after switching to ART.
ulev said:
Your original problem was using PA GAPPS full. Its to big for the /system partition. You should use one of the BaNkS Gapps versions instead. CM11 runs extremely well on SGT 7, especially after switching to ART.
Click to expand...
Click to collapse
That was a very good tip!!!!!
THANKS, upgraded to CM11 with BaNkS Gapps.
+1
brenzef said:
That was a very good tip!!!!!
THANKS, upgraded to CM11 with BaNkS Gapps.
+1
Click to expand...
Click to collapse
Glad I could be of help.
Just out of curiosity.. Any one able to get the ART runtime to work properly with any 4.4 roms? I havent tried any stock roms, as out here Rogers hasnt rolled out the update.
I've tried two popular roms so far, and no dice. I even went as far as Odexing the rom and it still wont boot up.
Thanks guys!
ART has bugs in 4.4, need 4.4.2
kolyan said:
ART has bugs in 4.4, need 4.4.2
Click to expand...
Click to collapse
Art worked good on my N5 before there was 4.4.2. I am downloading CM11 with Art compatible Gapps.. Giving it a shot soon
CyanogenMod 12.1
Hey guys, I no longer have this phone (or Sprint), but here's an update.
Download: Android File Host and Dev-Host
MD5: 73124015ae2883d8024b8df197e7288f
GApps
Kernel: GitHub
Reserved (Maybe?)
Working well here, other than the IR blaster....any ideas on how to make that work?
lerxst_x said:
Working well here, other than the IR blaster....any ideas on how to make that work?
Click to expand...
Click to collapse
No, I tried looking for a how to or something on it, I might try some time, I don't know exactly what it entails.
Also nfc...
@superfes
Thanks for releasing unofficially CM12.1. I'm using it since yesterday and its working fine so far. However, I get settings fc sometimes and mostly on bootup.
Another issue is with camera focus on micro shots which makes the device force reboot. It was present in cm12 long ago but it was solved or vanished later. Now seems to be back on CM12.1
Of course without a log, we cannot figure out these issues so I will post it asap here.
Btw; thanks for including d2s feature in the kernel. I have been missing it for long on official CM ROMs.
superfes said:
No, I tried looking for a how to or something on it, I might try some time, I don't know exactly what it entails.
Click to expand...
Click to collapse
Tested IR and its working fine, including recording. I'm using latest version of Smart IR Remote - AnyMote.
Best Regards
For some reason I wasn't able to receive calls. They said it rang once then went to voicemail. IR also wasn't working through peel but I never really use it. Other than that OMG the ROM! This is the only CM rom that doesn't have issues with my FFC on official CM it has a weird tint to it with every app
Sent from my One using Tapatalk
Everything works great other than the camera. Same issue as most here, using the camera most of the time results in a reboot of the phone.
Flashing the 2015-6-22 build right now! I'll update after it's been tested.
update: the camera seems to work fine, and doesn't cause reboots now. But I get random reboots just out of the blue. And that was happening before the update. But issues with the camera seem to be fixed. So that's awesome!
I'm gonna transition from official cm12 nightlies to this build. I am also gonna try the 20150602 cm 12.1 gapps build (located on http://wiki.cyanogenmod.org/w/Google_Apps) since this is a newer version..hope it works. will try to post any issues. If you don't hear from me, assume it is working great! Thanks for this build superfes.
OK loaded fine with newest version gapps, so far so good
I too confirm that force reboot in camera focus is now fixed. Thanks a lot.
However, wake features are no longer available. Looks like you have changed the kernel.
Can we use the kernel from the previous build of yours?
CRACING said:
I too confirm that force reboot in camera focus is now fixed. Thanks a lot.
However, wake features are no longer available. Looks like you have changed the kernel.
Can we use the kernel from the previous build of yours?
Click to expand...
Click to collapse
I was trying to fork this one: http://forum.xda-developers.com/sprint-htc-one/development/kernel-elite-kernels-t2961835
But I messed up a merge, I'm trying to get it back to working, as soon as the merge is stable I'll build it back in.
Until then you can just use the AOSP kernel there.
superfes said:
I was trying to fork this one: http://forum.xda-developers.com/sprint-htc-one/development/kernel-elite-kernels-t2961835
But I messed up a merge, I'm trying to get it back to working, as soon as the merge is stable I'll build it back in.
Until then you can just use the AOSP kernel there.
Click to expand...
Click to collapse
Ok but that kernel isn't updated from January and is a Android 5.0 kernel. Does it still work well on CM12.1?
CRACING said:
Ok but that kernel isn't updated from January and is a Android 5.0 kernel. Does it still work well on CM12.1?
Click to expand...
Click to collapse
Yeah, that's the one I originally included ^_^
superfes said:
Yeah, that's the one I originally included ^_^
Click to expand...
Click to collapse
Lol, good to know that it works.
btw, is it possible for you to update that kernel? adding new upstream changes or it isn't necessary?
CRACING said:
btw, is it possible for you to update that kernel? adding new upstream changes or it isn't necessary?
Click to expand...
Click to collapse
That's what I was trying to do when I messed up the merge, I think the trouble is rather minor, just been busy at work.
superfes said:
That's what I was trying to do when I messed up the merge, I think the trouble is rather minor, just been busy at work.
Click to expand...
Click to collapse
Oh I see. Anyway, take your own time and if you need any testings from me, just let me know.
Hi
I like this rom so far, but I was hoping to reinstall the Beats sound back. I downloaded the apk, but it says an error when I try to install. The music through the speakers sound rather tinny without it. Has anyone installed Beats or anything similar to improve the sound quality?
Thank you.
So I have been using this rom since the 25th as a daily driver, I actually have had only 1 random reboot (unlike on the cm12 rom I had previously where it would reboot almost every day) Camera seems to work flawless where some have reported that it reboots but is def fixed.
I am having one major issue where I get no service 90% of my day, and I only get an exclamation point next to my service bars. The only way to *sometimes* get it back is by going into my mobile network settings and toggling the preferred network type back and forth from global/CDMA + LTE/EvDo/EvDo only/CDMA w/o EvDo/GSM only (where GSM only was to force it out of the proper net type and back in so I could toggle it back to CDMA base right after) And sometimes that didnt even work. I would also toggle airplane mode on and off with similar results. It is quite frustrating. Does this have anything to do with the fact that I never updated my stock radio/kernel? Does anybody know a fix to this? GPS also isn't working (and hasn't been for over a year)
Other than that everything else is working great, best CM12+ rom out so far! Please, if anyone knows of a solution to my connection issues please share! Thanks!
Hey all,
So I recently developed an Xposed module while running KitKat. I released it and users are having trouble getting it to work correctly when running Lollipop 5.1.1 - can someone recommend me a stable ROM with working Bluetooth, SMS, and support for Xposed?
mrinehart93 said:
Hey all,
So I recently developed an Xposed module while running KitKat. I released it and users are having trouble getting it to work correctly when running Lollipop 5.1.1 - can someone recommend me a stable ROM with working Bluetooth, SMS, and support for Xposed?
Click to expand...
Click to collapse
There are many great ROMs on every variant of the HTC One M7 that run well on 5.1.1. My personal favorite is Candy5, which can be found here.
In terms of Xposed itself, as long as you flash the correct framework flashable for the version of Android you're running, (in your case, 5.1.1) then everything will work.
For the correct framework files to flash on top of your 5.1.1 ROM of choice, here they are.
Get the arm version, NOT arm64. Arm is the compatible version for our phone.
On top of this, you need to install the .apk for Xposed as well to utilize the framework modules (this shouldn't be a surprise to you, as you've used Xposed on KitKat)
Signal2Noise said:
There are many great ROMs on every variant of the HTC One M7 that run well on 5.1.1. My personal favorite is Candy5, which can be found here.
In terms of Xposed itself, as long as you flash the correct framework flashable for the version of Android you're running, (in your case, 5.1.1) then everything will work.
For the correct framework files to flash on top of your 5.1.1 ROM of choice, here they are.
Get the arm version, NOT arm64. Arm is the compatible version for our phone.
On top of this, you need to install the .apk for Xposed as well to utilize the framework modules (this shouldn't be a surprise to you, as you've used Xposed on KitKat)
Click to expand...
Click to collapse
Thanks for the reply! I ended up trying out Candy and AICP... both are kinda buggy, though. AICP doesn't find my cell network, and Candy makes weird static noises randomly Which ROM do you use?
mrinehart93 said:
Thanks for the reply! I ended up trying out Candy and AICP... both are kinda buggy, though. AICP doesn't find my cell network, and Candy makes weird static noises randomly Which ROM do you use?
Click to expand...
Click to collapse
I use Candy5 as a daily driver and actually, I helped the ROM developer fix the static noise you mentioned. The link for the full ROM with that fix can be found here. It's by far the smoothest (and most stable) stock-like ROM on the m7spr because of the wonderful Candy Kernel baked in.
Signal2Noise said:
I use Candy5 as a daily driver and actually, I helped the ROM developer fix the static noise you mentioned. The link for the full ROM with that fix can be found here. It's by far the smoothest (and most stable) stock-like ROM on the m7spr because of the wonderful Candy Kernel baked in.
Click to expand...
Click to collapse
Awesome, I'll check that link out. How is the battery life for you? Last time I actually "tried" Lollipop ROMs were a few months ago, and battery life was pretty bad which kept me on KitKat.
mrinehart93 said:
Awesome, I'll check that link out. How is the battery life for you? Last time I actually "tried" Lollipop ROMs were a few months ago, and battery life was pretty bad which kept me on KitKat.
Click to expand...
Click to collapse
You're right in that Lollipop ROMs have pretty terrible battery life. This one has much better battery than any other ROM on stock Android. It's not great, but it is rather good once your battery is optimized to it, considering.
For example, I went to a theme park with this ROM and I would check my phone just about every ten minutes. When I got to the park itself, it was only on 10% (reason being because I didn't charge it overnight, haha!). With power saver mode enabled, it lasted over three hours before dying, which is impressive for any ROM, let alone a Lollipop ROM.
It's a fine accomplishment of the CandyROM team for sure.
Signal2Noise said:
You're right in that Lollipop ROMs have pretty terrible battery life. This one has much better battery than any other ROM on stock Android. It's not great, but it is rather good once your battery is optimized to it, considering.
For example, I went to a theme park with this ROM and I would check my phone just about every ten minutes. When I got to the park itself, it was only on 10% (reason being because I didn't charge it overnight, haha!). With power saver mode enabled, it lasted over three hours before dying, which is impressive for any ROM, let alone a Lollipop ROM.
It's a fine accomplishment of the CandyROM team for sure.
Click to expand...
Click to collapse
I'll definitely be checking this out when I get a chance, thank you for the replies!
mrinehart93 said:
I'll definitely be checking this out when I get a chance, thank you for the replies!
Click to expand...
Click to collapse
No problem!
Have a nice evening