Hello, since the Hox has much roms , and yes it's more supported, i was thinking , by searching with some guides here on xda , if porting a Hox rom on our Hox+ is possible?
clitoridys said:
Hello, since the Hox has much roms , and yes it's more supported, i was thinking , by searching with some guides here on xda , if porting a Hox rom on our Hox+ is possible?
Click to expand...
Click to collapse
no they have different processors so when installing the phone would crash causing a brick. brick is when the phone dosent turn on.
They are different devices , ask the dev to rewrite the rom for hox+ DDD
SomebodyEpic said:
no they have different processors so when installing the phone would crash causing a brick. brick is when the phone dosent turn on.
Click to expand...
Click to collapse
I tried this when I had my One V (I wanted Sense 4+ on it). This is complicated. I don't think you'll get any more than a boot screen (if that). Don't count on even this working though. Like the guy above said, the hardware is VERY different.
If you do port though, make sure you use Cyanogenmod as a base. But then again, why do it? It's much better to use a compiled ROM than a ported one.
hendrickson02 said:
I tried this when I had my One V (I wanted Sense 4+ on it). This is complicated. I don't think you'll get any more than a boot screen (if that). Don't count on even this working though. Like the guy above said, the hardware is VERY different.
If you do port though, make sure you use Cyanogenmod as a base. But then again, why do it? It's much better to use a compiled ROM than a ported one.
Click to expand...
Click to collapse
Sure but the Hox has more roms... i was thinkin that the devices was the same, except for the memory.
clitoridys said:
Sure but the Hox has more roms... i was thinkin that the devices was the same, except for the memory.
Click to expand...
Click to collapse
No totally I understand. Easy mistake to make. Still, you can try. Just use your version of HOX+'s CM 10 or 10.1 as a base for porting. Who knows, it might work. Beware of thus AT&T HOX+ though, as no one has gotten the call audio to work yet.
I mean the sense roms , not aosp/aokp
Inviato dal mio HTC Sensation XE with Beats Audio Z715e con Tapatalk 2
You misunderstand. If you want to port, you should use CM as a base. You put the X Rom on top of the CM layer.
Sent from my HTC One X+ using xda app-developers app
In addition to having different processors, the phones also have different modems I believe. The thread for Paranoid Android on the AT&T HTC One X+ has more details about why devs can't get voice to work in AOSP ROMs on the HOX+. For the One X as I understand it, devs could use the modem drivers from ICS builds to get them working in JB. But the HOX+ has never has ICS on it, and has a different modem than the International version to work on AT&T.
Related
Is there a way to run stock android ( so i can get the newest updates from google) on AT&T HTC One x+ LTE in US? I already have my phone bootloader unlocked and rooted. If yes what is the safest way to have a backup of whatever i currently have and get stock android on it. Do all the hardware features ( camera, bluetooth...) work correctly?
manivannanrajah said:
Is there a way to run stock android ( so i can get the newest updates from google) on AT&T HTC One x+ LTE in US? I already have my phone bootloader unlocked and rooted. If yes what is the safest way to have a backup of whatever i currently have and get stock android on it. Do all the hardware features ( camera, bluetooth...) work correctly?
Click to expand...
Click to collapse
Lloir has a CM 10.1 build at http://forum.xda-developers.com/showthread.php?t=2135938
Solomon56 has a PA build over at http://forum.xda-developers.com/showthread.php?t=2219520
However, a number of features aren't working yet, call audio being the biggest of them.
Just to clarify i dont want a mod just vanilla android. My HOX+ has become increasingly slow, is there a way i can find out why. The camera has so many dropped frames and sluggish as hell. (i have sense 4+ on android 4.1.1 with swapps, paperland and nova launcher running). even hitting the call app takes about 4 secs to load!
manivannanrajah said:
Just to clarify i dont want a mod just vanilla android. My HOX+ has become increasingly slow, is there a way i can find out why. The camera has so many dropped frames and sluggish as hell. (i have sense 4+ on android 4.1.1 with swapps, paperland and nova launcher running). even hitting the call app takes about 4 secs to load!
Click to expand...
Click to collapse
You don't need stock for that. Just get the Titanium app and remove all the AT&T apps (AT&T maps and AT&T contacts, for instance). Reboot and I think you'll notice it's smoother and faster.
That being said, I think when the devs DO get AOSP-ish roms on this phone it will live up to its full potential.
Btw, what you want, right now, is quite impossible, but don't worry. We're working on helping the main dev get a new phone. We're confident that the devs will be able to get AT LEAST Cyanogenmod. Dunno about pure AOSP though.
if it gets CM it will get AOSP
....that being said Lloir knows more than me
Sent from my HTC One X+ using xda app-developers app
hendrickson02 said:
....that being said Lloir knows more than me
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Now that stock android flavor of HTC one is announced and kernel code is released can we expect roms for AT&T HOX+ with similar features to come?
manivannanrajah said:
Is there a way to run stock android ( so i can get the newest updates from google) on AT&T HTC One x+ LTE in US? I already have my phone bootloader unlocked and rooted. If yes what is the safest way to have a backup of whatever i currently have and get stock android on it. Do all the hardware features ( camera, bluetooth...) work correctly?
Click to expand...
Click to collapse
There is a thread in General forum by hasoon...
You should at least read the main forums before asking questions...
manivannanrajah said:
Now that stock android flavor of HTC one is announced and kernel code is released can we expect roms for AT&T HOX+ with similar features to come?
Click to expand...
Click to collapse
The HTC One and HTC One X+ are similar devices in name only. Any progress made with the HTC One will almost assuredly not result in any progress on the HOX+ and vice versa.
edit: This is regarding AOSP, I am unsure of the possibility of porting Sense 5 from the One to the HOX+
Recently, I flashed cyanogenmod 10.1 on my AT&T HTC One X+ (plus). I used the ROM from lloir.com, and to my satisfaction, I was able to flash the ROM successfully. However, once I began to use the ROM I realized that I was not aware of an issue from using nightly builds, my phone reboots every 5 minutes, literally. I knew that the camera and gps would not work, but it seems that my carrier does not work either. For these reasons, I ask you guys to let me know of ROMs that function more smoothly on the AT&T HOX+. I already tried AOKP/Paranoid Android and that also rebooted about every 5 minutes. If you guys know of a fairly stock ROM that is somewhat stable (rebooting only a few times a day), I would greatly appreciate the advice. From what I've seen on other forums, there are many more ROMs for the international version but not quite as many for the AT&T version.
Thanks,
John Carrot
The two front runners seem to be Elegancia and ViperXL. I've used both, and they are good. I'm currently using ViperXL simply because.
I think I read somewhere here that, until we get S-Off(?) not much more can be done. It's looking more and more like that isn't happening, but I'm satisfied with my phone for now. When 4.3 finally drops, it might be a different story.
Sent from my HTC One X+ using Tapatalk 4 Beta
deeteroderdas said:
The two front runners seem to be Elegancia and ViperXL. I've used both, and they are good. I'm currently using ViperXL simply because.
I think I read somewhere here that, until we get S-Off(?) not much more can be done. It's looking more and more like that isn't happening, but I'm satisfied with my phone for now. When 4.3 finally drops, it might be a different story.
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
Basically, the ROMs based off of Sense work much better with the HTC One X+ than the ones based off of stock android. I think I'll use your suggestion, but the reason I rooted and added a custom ROM was to get a more stock experience. However, if the stock type version of Android for the HOX+ do not function properly, I will most certainly go back to sense. It is a bit disappointing, but that's life. Thanks.
deeteroderdas said:
The two front runners seem to be Elegancia and ViperXL. I've used both, and they are good. I'm currently using ViperXL simply because.
I think I read somewhere here that, until we get S-Off(?) not much more can be done. It's looking more and more like that isn't happening, but I'm satisfied with my phone for now. When 4.3 finally drops, it might be a different story.
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just an fyi, the lack of AOSP ROMs for the AT&T HOX+ is not at all related to S-Off. I think it's mostly a lack of developers and the fact that the AT&T HOX+ is a surprisingly unique device (only LTE phone with Tegra 3 I believe)
Best ROM threads are not allowed. Thread closed.
So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Darian_A said:
So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
Click to expand...
Click to collapse
Only if HTC, Qualcomm, and Texas Instruments provide the corresponding updated sources for development. Otherwise what few developers that are left here will still be banging their heads against the wall to port it.
Darin_Ram said:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Click to expand...
Click to collapse
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
KT-82166 said:
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
Click to expand...
Click to collapse
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Roms
Darin_Ram said:
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Click to expand...
Click to collapse
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Sense Jellybean...
Once we have sense Jellybean, the next working will be KitKat.
We are very close to having the very first Sense jellybean rom
4.3 roms
The evervolv rom is currently the best "4.3" rom for the Amaze. Found here: evervolv.com/devices/ruby.
Although, the mobile data is very choppy. It will connect but it's seems to when it wants. Not sure about the intricacies of that. But, a bit of a dealbreaker for me at this point. The good news is evervolv has been updating this rom with
tweaks and bug fixes everyday. So, it looks very promising. Also note, I have found an "unofficial" cm10.2
build by sportsstar89 but the sound does not work. If you search 'ruby' on goo.im you will find it. I would post a link
but the site seems to be down atm. I am currently running cm10/1006-nightly, what i've found to be the best jelly bean
rom at this point. There is also an unofficial cm10.1 build that is pretty good as well. It can be found here: droidfirmwares.com/cm10-1-android-4-2-2-jelly-bean-custom-firmware-for-htc-amaze-4g.html/2. I ran it for quite a while w/o any noticeable
trouble. I just prefer official cm builds i guess.
Fadiayad said:
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Click to expand...
Click to collapse
I don't think you can get the keyboard on CM10 unless there's an app or someone made a port or something.
The snapshot feature works differently with Cyanogenmod cause they use the long press power button then selecting screenshot, though you'll have to enable the feature in the system settings.
Flip to silent the phone? Must be a feature I don't use lol
Idk, I liked the ICS stock tmobile (I de-bloated it myself using root uninstaller. Got rid of anything pertaining to t-mobile and it runs like a dream.)
Nenamark2 benchmark averages at 47 fps.
Antutu results are a little over 9000 (Let the Dragon Ball Z jokes start now lmao)
Overclocking is something that I would have loved to do on this stock rom, but I'll just run V6 Supercharger script instead.
Though pushing min. clock to about 1.2ghz gives a slight difference in benchmarks.
Hmmmmmm.......
It would take a lot of developer skills to get it on this device. CM said if they didn't officially support the device before, they won't start now regardless of ram specs. The s4 has it, but even better there is a dev for the international s4 that has made a 4.3.1 ROM which is made up of 85% straight Google source with 15% cm commits to get it to work on our device. And IMO, aosp is better and more stable than cm10.2 and has way less lag.
Sent from my GT-I9505 using Tapatalk
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
from what i have seen and heard kit kat will be better on amaze
Darian_A said:
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
Click to expand...
Click to collapse
Unfortunatelly jeepers007 bricked his device
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
chevycowboyusa said:
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Odysseus1962 said:
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Click to expand...
Click to collapse
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for you comments, now I fully understand your dilemma. The issue isn't just getting a working JB ROM, it's getting a working JB/sense ROM. You see I'm sense agnostic. My HD2 had sense with windows, but all of the best android ROMs for it were aosp or cm based, so I got used to not having it. Now I've got it again with the nrg ROM so I use it. When I ran Tytung's cm ROMs I always customize anyway. To me cm or aosp is like having a blank canvas to paint on. You have the basic features, but It's infinitely customizable to taste. Sense gives a different platform. You can still customize, but It's not as flexible to customize as aosp or cm. In a way it's factory customized. Either way I'd just love to see a fully functioning JB on our devices. Please keep up the good work!
Ciao
I've asked somthing in above post..
Can anyone reply please... I want to start my work though....
Sent from my Amaze 4G using xda app-developers app
shubham211995 said:
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
I'm not the most experienced but from my knowleged you should be ok as long as you watch what partitions you format.
Sent from my HTC_Amaze_4G using xda app-developers app
Hello,
I am really new to rooting and installing custom rom's etc and could use some help with updating my international HOX+ to Android 4.4.2.
I am looking for a really stable ROM for everyday use. I really don't want to give up on any hardware function of my HOX+.
Can anyone guide me through it a bit please ?
Thanks so much in advance.
when you install a custom rom you will be loosing all of the HTC features that your phone currently has.. is that ok?
sid394 said:
when you install a custom rom you will be loosing all of the HTC features that your phone currently has.. is that ok?
Click to expand...
Click to collapse
Yes, I'm aware of that.
I'm just looking for a good stable build. Which one do you recommend ?
I love ParanoidAndroid.. but there's one annoying bug where the music stutters sometimes when playing. If you dont mind then thats my first choice. Or else the only other option is Carbon Rom. And then don't try elitekernel rightaway, use the boot.img that comes inside the rom for now.
sid394 said:
when you install a custom rom you will be loosing all of the HTC features that your phone currently has.. is that ok?
Click to expand...
Click to collapse
What exactly will be lost?
You will be loosing the beautiful (atleast for me) Sense UI along with its widgets and HTC specific apps. With aosp based roms the phone's software will look just like every other android phone. I've switched back and forth between CM/PA/Carbon and ARHD/InsertCoin/Viper a THOUSAND times(literally!) and then finally decided that the best for this phone is InsertCoin 5.0.6 along with the kernel that comes with it. It is by far the fastest and smoothest rom of all mentioned above. Battery life may be a little bit bad because of the performance but I can live with it. Also I got the best battery life from PA rom by the way.
All ROMs are best in their own so you are not allowed to compare the ROMs. Against the XDA Rules
Use the Stock ROMs for best stable at max what I can say.
Sent from my HTC One X+_Upgraded Model using XDA Premium 4 mobile app
sid394 said:
You will be loosing the beautiful (atleast for me) Sense UI along with its widgets and HTC specific apps. With aosp based roms the phone's software will look just like every other android phone.
Click to expand...
Click to collapse
I won't be crying after a bugged, black and white sense 5 .
Just like every other android phone? Nah, there are too many themes around.
I bought the HTC One X+ international version for the tegra3 and 64gb capacity.... but it seems like there are hardly any roms which are fully functional. I am currently using the Venom ViperX+ ROM... and it SUCKS... terrible rom.. slow as all hell... mad problems with maps and force closes in general.... I am about to switch to Android Revolution HD because it is the only rom that even seems like it has a chance at working fully. There have been all these projects forever CM10.2, CM11, and now I see there is one for CM12... what is the point if none of them work correctly???
Could anyone recommend a stable rom?
MrBoard said:
I bought the HTC One X+ international version for the tegra3 and 64gb capacity.... but it seems like there are hardly any roms which are fully functional. I am currently using the Venom ViperX+ ROM... and it SUCKS... terrible rom.. slow as all hell... mad problems with maps and force closes in general.... I am about to switch to Android Revolution HD because it is the only rom that even seems like it has a chance at working fully. There have been all these projects forever CM10.2, CM11, and now I see there is one for CM12... what is the point if none of them work correctly???
Could anyone recommend a stable rom?
Click to expand...
Click to collapse
Go back to fully stock if you want a truely stable ROM, else CM11 on my HOX+ is consider fully functional already. Small bugs which I encountered which is FM radio not working, Video record only in 3GP format. But that does not bug me because I rarely use those feature.
MrBoard said:
I bought the HTC One X+ international version for the tegra3 and 64gb capacity.... but it seems like there are hardly any roms which are fully functional. I am currently using the Venom ViperX+ ROM... and it SUCKS... terrible rom.. slow as all hell... mad problems with maps and force closes in general.... I am about to switch to Android Revolution HD because it is the only rom that even seems like it has a chance at working fully. There have been all these projects forever CM10.2, CM11, and now I see there is one for CM12... what is the point if none of them work correctly???
Could anyone recommend a stable rom?
Click to expand...
Click to collapse
Wow...how about you help out? Or say what your having issues with? Or how about you make your own ROM and release it? Then everyone can tell you how awful it is.
Sure, Let's click the "Create Stable ROM" button.
That's not how ROM development works buddy. It's not as easy as you think specially not for the HOX+.
You see, Developers on here don't get paid for the ROMS they make. They mostly make it for fun in their free time they're not obliged in ANY WAY to provide you with ROMs.
So if you have nothing nice to say then you better stay quiet
Oh and I tried ViperX+ ROM a long time ago and it was running fine for me
Plus its your fault for buying a 2 years old device without checking if it had ROMS or not.
ok... sorry... i didn't mean to sound rude... honestly... I was just getting irritated with my phone lagging out in the viper rom...
I didnt mean to offend anyone... especially you Lloir... cuz I know you've done alot of work on here...
I apologize once more...
Lloir's 4.3 AOSP works great as does Omni. Carbon great too. Those are good to try before that first impression goes pear shaped. Oh, it did already. Oops.
Sent using the XDA Free mobile app