How hard is porting roms from the att HTC one x to the rezound? Please don't go to hard on me. Just was curious. Seems a lot of devs that are here also are on HTC one x. Awesome phone but sucks not having s-off and no expandable memory
Sent from my ADR6425LVW using Tapatalk 2
I would think it would take some effort and knowledge to port a rom and have it run up to standards. So probably not that easy.
Thank you Jon. Just was curious cause I have both phones. The one x is very snappy but the rezound us alot more fun to. Dev with.
Sent from my ADR6425LVW using Tapatalk 2
Actually i just looked and found a guide to porting a sense rom in between devices. It actually doesnt look that hard, it looks more like replacing just replacing files if anything. I think it just depends on what rom your trying too port. If your trying to port over a different sense version it might require more work. If your trying to port an AOSP rom it might not be too difficult. Porting an android version is probably the hardest.
I see. Would be nice to try figure out that stuff. I am too inexperienced to try I think. Done minor things. Was just seeing if the one xl jellybean update that dropped last night would help the devs over here.
Sent from my ADR6425LVW using Tapatalk 2
I was actually thinking of making a very basic rom to start with like a sense 3.6 rom that might have some tweaks and such. Maybe try making my own AOSP rom, though im not entirely sure how to go about making an AOSP rom. I suppose i could also try using the guide i found to port over a sense rom as well.
Wanna share where that guide is?
Sent from my HTC One XL using xda app-developers app
http://www.xda-developers.com/android/port-sense-roms-between-sense-devices-in-six-easy-steps/
I havent tried it yet, it might work.
This one may work out better
http://forum.xda-developers.com/showthread.php?t=1598713
Just keep in mind when porting, it will be better as well as easier if you can port from a device similar to what you are porting too. Similar cpus, gpus, lte, screen resolution and network type. It all needs to be taken into consideration.
Personally if I was you, I'd start looking at Sprint devices if you want to port to the Rezound. Sprint and Verizon have the closest devices and the closest bands of any other providers out there.
Of course there are always tricks to getting around porting a full rom. Once you get to going and learn your way around porting real good, you'll learn what they are and how to do it. If you need an example of this, look up my AOKP + TouchWiz hybrid for the Rezound.
Edit: This thread made me feel nastalgic. I remember back when I first started porting. I worked and worked hard learning new tricks here and there. Back then I wrote a guide. It wouldn't be useful now, but if you wanted to humor me and see how this old dog did it back in the day you should check it out http://forum.xda-developers.com/showthread.php?t=1169570
wildstang83 said:
Just keep in mind when porting, it will be better as well as easier if you can port from a device similar to what you are porting too. Similar cpus, gpus, lte, screen resolution and network type. It all needs to be taken into consideration.
Personally if I was you, I'd start looking at Sprint devices if you want to port to the Rezound. Sprint and Verizon have the closest devices and the closest bands of any other providers out there.
Of course there are always tricks to getting around porting a full rom. Once you get to going and learn your way around porting real good, you'll learn what they are and how to do it. If you need an example of this, look up my AOKP + TouchWiz hybrid for the Rezound.
Edit: This thread made me feel nastalgic. I remember back when I first started porting. I worked and worked hard learning new tricks here and there. Back then I wrote a guide. It wouldn't be useful now, but if you wanted to humor me and see how this old dog did it back in the day you should check it out http://forum.xda-developers.com/showthread.php?t=1169570
Click to expand...
Click to collapse
Thanks wildstang for the advice, Ill probably try just porting a rom that is really basic. Which phone do you recommend attempting to port a rom from for beginners?
jon7701 said:
Which phone do you recommend attempting to port a rom from for beginners?
Click to expand...
Click to collapse
One X or Evo 4G LTE.
jon7701 said:
Thanks wildstang for the advice, Ill probably try just porting a rom that is really basic. Which phone do you recommend attempting to port a rom from for beginners?
Click to expand...
Click to collapse
Snuzzo's on it
Snuzzo said:
One X or Evo 4G LTE.
Click to expand...
Click to collapse
Alright, I found a One X rom that looks interesting, I might give it an attempt. :good:
Edit: Just finished porting the rom, it doesnt boot or even show anything on my screen, but it installed. Trying something different.
jon7701 said:
Alright, I found a One X rom that looks interesting, I might give it an attempt. :good:
Edit: Just finished porting the rom, it doesnt boot or even show anything on my screen, but it installed. Trying something different.
Click to expand...
Click to collapse
Ok, so it did not error in recovery right?
wildstang83 said:
Ok, so it did not error in recovery right?
Click to expand...
Click to collapse
It did but i figured out the problem. I didnt expect the rom to work since i tried porting the 4.2 rom from the One X. :silly: Ill try a sense 4 or 4.1 rom later.
Related
I was doing a little bit of surfing and noticed that cyanogen has made a cyanogen 9 version for the galaxy 2 and the nexus s... And I was wondering if it was possible to get this on our phones...
This should be in the general section...
Anyways one day it will
Sent from my HTC_Amaze_4G using XDA App
Agree is should go in general. Cyanogen said that it wouldn't be until maybe January for an alpha of CM9.
As for asking for your specific phone, give it time... it hasn't even been a month since ICS source was released.
Sent from my HTC Inspire 4G using xda premium
Right. Moving to General.
jbizz said:
Agree is should go in general. Cyanogen said that it wouldn't be until maybe January for an alpha of CM9.
As for asking for your specific phone, give it time... it hasn't even been a month since ICS source was released.
Sent from my HTC Inspire 4G using xda premium
Click to expand...
Click to collapse
In the meantime, CM7.1 would be nice - but will they just skip over 7.1 for new devices and focus on 9?
Just as a heads up, Max Krivonos posted that he stopped working on CM7 for the amaze and is going straight to CM9,
Double edged sword. Great for CM9 but no CM at all for a few months.
Yea I really miss CM. Wish it would get here asap.
Sent from my HTC Amaze 4G using xda premium
I've thought alot about selling this phone due to the lack of having a huge community support (face it, it's no Sensation, Desire Z/HD, Evo, etc)... The hardware is good, the replacement? Obviously a Galaxy Nexus, if there is a solid CM9 port for this device, I would probably just save myself the trouble and keep using this, This has everything that the international GNex would have, except for the huge high res amoled screen. Please Koush/Max!!!! (I would think quite a bit could be borrowed from the Pyramid builds, with the obvious exception of the NFC/camera)
Uh... How long has the phone been out?? Let's face that first before complaining about the lack of development... It'd be nice if there was but its not going to happen over night...
jmhalder said:
I've thought alot about selling this phone due to the lack of having a huge community support (face it, it's no Sensation, Desire Z/HD, Evo, etc)... The hardware is good, the replacement? Obviously a Galaxy Nexus, if there is a solid CM9 port for this device, I would probably just save myself the trouble and keep using this, This has everything that the international GNex would have, except for the huge high res amoled screen. Please Koush/Max!!!! (I would think quite a bit could be borrowed from the Pyramid builds, with the obvious exception of the NFC/camera)
Click to expand...
Click to collapse
Be patient my friend! I think the reason behind (kinda) lacking developtment for this phone is because there will be an ICS came out soon for it in early 2012 and most Devs are waiting for the official Amaze ICS release rather than wasting their time to built rom that would only last for less than two months
On that perspective I am really thankful for Xboarder for his effort to brought us something to satisfied our addictiveness of flashing meanwhile
I am more thankful to Max Krivonos, and Keyan Mobli (Scepterr/kmobs), Max is probably gonna be the maintainer for the Amaze for CM9 and is currently the maintainer for the MT4GS, kmobs is the maintainer of the Sensation for CM9 and has it to a point where he's said "So I'm now using ICS as my daily driver"... There is hope, but if you're looking for CM7/9 or any REAL AOSP build, don't expect xboarder to deliver that, I don't think he compiles anything, he's a themer/kanger/(insert less offensive term here). There is hope, but I'm dying to see some actual AOSP builds, GB or ICS.
jmhalder said:
I am more thankful to Max Krivonos, and Keyan Mobli (Scepterr/kmobs), Max is probably gonna be the maintainer for the Amaze for CM9 and is currently the maintainer for the MT4GS, kmobs is the maintainer of the Sensation for CM9 and has it to a point where he's said "So I'm now using ICS as my daily driver"... There is hope, but if you're looking for CM7/9 or any REAL AOSP build, don't expect xboarder to deliver that, I don't think he compiles anything, he's a themer/kanger/(insert less offensive term here). There is hope, but I'm dying to see some actual AOSP builds, GB or ICS.
Click to expand...
Click to collapse
Well, I'm by no mean a tech guy or whatsoever in that manner. All I can do is follows instruction to flashing Rom and stuff so when it come to judging who done what I have no idea eventhough I'm very much understanding what kang is ...
Perhaps when Max and whoever on CyanogenMod team came over and gave us some ICS or CM9 goodness, 'til then, the very few peoples who get this Amaze forum go on as it is and gave us something to played with is Xboarder56, Mike1986 and NRGZ28 .... and for that I am appreciates their times and effort putting into it
Heck, I even thanksful those themer like Alexia Whitehurst, killathenoob, TheSneakerWhore for uploading their theme file even though I myself know how to extract files from rom and uploading onto UOT kitchen
Those guy are ways better than those who did nothing .
antiquezip said:
Heck, I even thanksful those themer like Alexia Whitehurst, killathenoob, TheSneakerWhore for uploading their theme file even though I myself know how to extract files from rom and uploading onto UOT kitchen
Those guy are ways better than those who did nothing .
Click to expand...
Click to collapse
Just trying to keep options out there during our "slow" (see:new) period. Development takes time--Hell, I'm stuck on a macbook until I can save up for a notebook. Once I get that, I'll be able to do real theming/modding. UOT framework feels like a cop-out right now, but it is all that is being offered and we need the activity to draw more people. I have a to-do list of mods I want to do, but until I get my hardware back, it isn't happening.
Ultimately, it is patience. This phone is very new--ICS is around the corner.
antiquezip said:
Well, I'm by no mean a tech guy or whatsoever in that manner. All I can do is follows instruction to flashing Rom and stuff so when it come to judging who done what I have no idea eventhough I'm very much understanding what kang is ...
Perhaps when Max and whoever on CyanogenMod team came over and gave us some ICS or CM9 goodness, 'til then, the very few peoples who get this Amaze forum go on as it is and gave us something to played with is Xboarder56, Mike1986 and NRGZ28 .... and for that I am appreciates their times and effort putting into it
Heck, I even thanksful those themer like Alexia Whitehurst, killathenoob, TheSneakerWhore for uploading their theme file even though I myself know how to extract files from rom and uploading onto UOT kitchen
Those guy are ways better than those who did nothing .
Click to expand...
Click to collapse
+1.
There is still very much a lot of effort being put in here.
I also am thankful to everyone helping out during our slow period. Although I can't wait for some true aosp action. I absolutely hate sense. It's pretty, but I just prefer aosp
wow man way to talk behind my back look at this:
https://github.com/Xboarder56/android_device_htc_ruby
wasnt gonna release yet but im working on cm7/cm9 compile so dont talk **** when you dont know.
PS: who fixed the recovery problem, me
PS: you compile just a basic recovery, hell port sense 3.5 with working data then talk
pss: just for prove recovery i compile 5.0.2.7 still working on fixing charging bug in this one but you make one of those without cm7 team and then you talk **** man i put hours into working on this **** for you just say that it makes me want to quite becuase you dont understand
http://www.multiupload.com/6ZLPJLUZ1S (5.0.2.7 recovery) happy now
Please refrain from argueing in thread's , take it to a PM . xBoarder doe's all of the work for us so don't even .
oh xboarder just schooled him. but back on topic i wish i could help xboarder but i know nothing about making roms and such.
ajbk4life1 said:
oh xboarder just schooled him. but back on topic i wish i could help xboarder but i know nothing about making roms and such.
Click to expand...
Click to collapse
its not easy building a device tree but i did build one i still got to find all the libs to get it to compile right but thats the device tree it will compile cm7 just doenst boot all the way right now but it does compile working recoverys
Has anyone tried porting the stock, rooted, or otherwise Rom from the Nexus 4?
If no one has I will give it a shot. The two phones aren't all that different ours has the LTE on the chip set activated but I believe they have basically the same Qualcomm chip set.
Also if anyone knows more about it than I do feel free to inform me. I'm always up for a hacking adventure but I don't want to start something I'll never be able to finish.
CrazyLineman777 said:
Has anyone tried porting the stock, rooted, or otherwise Rom from the Nexus 4?
If no one has I will give it a shot. The two phones aren't all that different ours has the LTE on the chip set activated but I believe they have basically the same Qualcomm chip set.
Also if anyone knows more about it than I do feel free to inform me. I'm always up for a hacking adventure but I don't want to start something I'll never be able to finish.
Click to expand...
Click to collapse
Yea some people have tried but the kernel isn't working on the att model but give it a shot maybe you know a little more. I think a lot of people would appreciate it. Good luck
Sent from my LG-E970 using xda premium
CrazyLineman777 said:
Has anyone tried porting the stock, rooted, or otherwise Rom from the Nexus 4?
If no one has I will give it a shot. The two phones aren't all that different ours has the LTE on the chip set activated but I believe they have basically the same Qualcomm chip set.
Also if anyone knows more about it than I do feel free to inform me. I'm always up for a hacking adventure but I don't want to start something I'll never be able to finish.
Click to expand...
Click to collapse
Apparently there is also a bunch of driver issues.
Dsmforlife92 said:
Yea some people have tried but the kernel isn't working on the att model but give it a shot maybe you know a little more. I think a lot of people would appreciate it. Good luck
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
I should figured AT&T would screw us like that. Man this is gonna take some work, but I certainly will give it a shot. This won't be my first port of a Rom but it'll be my first one where I've had to work on a Kernel. Wish me luck guys.
CrazyLineman777 said:
I should figured AT&T would screw us like that. Man this is gonna take some work, but I certainly will give it a shot. This won't be my first port of a Rom but it'll be my first one where I've had to work on a Kernel. Wish me luck guys.
Click to expand...
Click to collapse
Make it happen dude! If you need or want some help let me know. I have lots of free time
CrazyLineman777 said:
Has anyone tried porting the stock, rooted, or otherwise Rom from the Nexus 4?
If no one has I will give it a shot. The two phones aren't all that different ours has the LTE on the chip set activated but I believe they have basically the same Qualcomm chip set.
Also if anyone knows more about it than I do feel free to inform me. I'm always up for a hacking adventure but I don't want to start something I'll never be able to finish.
Click to expand...
Click to collapse
Head over to the IRC channel, #lg-optimus-g, most of the current developers are always on there and they will be more than willing to have someone new that has some experience and willingness to help!
DonMarek said:
Head over to the IRC channel, #lg-optimus-g, most of the current developers are always on there and they will be more than willing to have someone new that has some experience and willingness to help!
Click to expand...
Click to collapse
I believe I've found a sort of attempt at what I'm looking to do.
http://forum.xda-developers.com/showthread.php?t=2099784
This essentially turns the phone into a Nexus 4 so that essentially the firmware is tricked into thinking that our phone is the Nexus 4. It appears as if in order to put vanilla android on here I'll need to take pieces of this hack, and sort of finish it. Like getting the Capacitive buttons working, which will require a bit of kernel hacking. It appears as if reflashing the modem, which I think after I take apart the original firmware I can sort of shove in there, will fix the LTE, so says the post, and the issue of the SD card. This method may be more intensive than is necessary. However it's looking like this is all I've got to work with as of right now.
I'm going to try and make a Rom that's still ICS and as close to Vanilla as is possible, then I'll give moving it up to Jelly Bean a shot. Also this may take a while as I am in college, and I've only got a small amount of experience so this will sort of be a learning experience for me.
Also I'm not too familiar with using IRC. I'm used to doing stuff on my own. For my original Android phone, the HTC Inspire. The dev community over there was awesome, they're probably still going, but I'm more used to taking a base like CM 9 or CM 10 nightlies and making them my own for my phone. So this will be a hacking adventure. A hackventure if you will.
CrazyLineman777 said:
I believe I've found a sort of attempt at what I'm looking to do.
http://forum.xda-developers.com/showthread.php?t=2099784
This essentially turns the phone into a Nexus 4 so that essentially the firmware is tricked into thinking that our phone is the Nexus 4. It appears as if in order to put vanilla android on here I'll need to take pieces of this hack, and sort of finish it. Like getting the Capacitive buttons working, which will require a bit of kernel hacking. It appears as if reflashing the modem, which I think after I take apart the original firmware I can sort of shove in there, will fix the LTE, so says the post, and the issue of the SD card. This method may be more intensive than is necessary. However it's looking like this is all I've got to work with as of right now.
I'm going to try and make a Rom that's still ICS and as close to Vanilla as is possible, then I'll give moving it up to Jelly Bean a shot. Also this may take a while as I am in college, and I've only got a small amount of experience so this will sort of be a learning experience for me.
Also I'm not too familiar with using IRC. I'm used to doing stuff on my own. For my original Android phone, the HTC Inspire. The dev community over there was awesome, they're probably still going, but I'm more used to taking a base like CM 9 or CM 10 nightlies and making them my own for my phone. So this will be a hacking adventure. A hackventure if you will.
Click to expand...
Click to collapse
SD Card requires ramdisk edits too
Sent from my LG-E970 using xda app-developers app
Hey guys I've had my DNA since launch weekend. I've become interested now that I've seen there are methods for S-OFF and then now return to stock methods.
I am fully stock with the most recent OTA update. So I need help in figuring out which methods of S-OFF are easiest as I know I've seen different requirements for each one and it seems they keep changing so I can't keep up with them.
Also with the ROM's, are there any fully complete ones that work 99.9999% with the phones features. I have used CM 10 on my Incredible 2. Any thoughts as to which ROM's to start out with?
I know I could search the $hit out of this, but I read into things too much and then just get frustrated when trying to find a ROM or a method and never pick something.
**********Update**********
I moonshined my phone this weekend, so now it's time to look at each of the ROM's that you guys mentioned! Thanks again for the help in this!!
I really would appreciate any help on the matter and I thank you in advance!!
NOS7 seems to be my most fav all around so far. Very complete
Sent from my HTC6435LVW using Tapatalk 4 Beta
like viper Dna the best no bugs at all very smooth and you can have tweaks and customize it to your liking. Moonshine to achieve s off worked flawlessly for me and it can now be run on windows so it's very simple.
Sent from my HTC6435LVW using xda premium[/QUOTE]
Sent from my HTC6435LVW using xda premium
I personally think Revone method is the easiest way to get S-off .
If you want 99% bug free I would recommend NOS7
Moonshine -> TWRP -> Carbon -> Win
Sent from my Carbonized DNA
I'd probably suggest PAC or carbon. I'm on PAC right now, but next time I clean flash a rom, carbon is going on my phone.
Sent from my HTC6435LVW using xda app-developers app
I'd suggest not asking users as you will get a different answer from every single one of them. Research each ROM and make a decision based on what you want.
As for S-Off, both methods are insanely easy. Pick one and go with it.
Phaded said:
I'd suggest not asking users as you will get a different answer from every single one of them. Research each ROM and make a decision based on what you want.
As for S-Off, both methods are insanely easy. Pick one and go with it.
Click to expand...
Click to collapse
I understand that different people will like different ROM's, but their suggestions do help with making a starting choice in figuring out which ones to give a shot first. I just tend to over research stuff and never making a choice as I can't decide which to pick. Sometimes it's easier to just start off with suggestions from others who have already done what I was trying to do.
Again thanks everyone for your inputs and suggestions! I'm going to research the methods for getting S-Off and pick one. I will most likely get this done this weekend.
If you are a fan of Sense 5 and okay with using android 4.1, then go for newt's NOS7 rom, it's essentially bug-free and super smooth.
If you're an AOSP kind of guy, I would highly suggest flyhalf's CM10.1 build paired with crpalmer's aosp kernel. Keep in mind that it is a WIP, so there is plenty of room for optimization, and some features (such as bluetooth audio) may not be working.. it is android 4.2.2, so you do have some features over 4.1, but it's whatever you prefer. There are more updates on CM based roms for the DNA because it is still generally new, and the developers are active on their respective roms.
I definitely would go with a Sense 5 Rom. I had nothing with problems with CyanogenMod on this phone. I take a lot of the talk of good things about it on this phone as circle jerking. I really had quite a few problems, even on the later versions that came out earlier this month.
Switched to NOS M7 and have had no problems what-so-ever.
mracrawford said:
I definitely would go with a Sense 5 Rom. I had nothing with problems with CyanogenMod on this phone. I take a lot of the talk of good things about it on this phone as circle jerking. I really had quite a few problems, even on the later versions that came out earlier this month.
Switched to NOS M7 and have had no problems what-so-ever.
Click to expand...
Click to collapse
As offensive as your post can be to developers, I do agree that a sense 5 ROM is most likely what the OP will enjoy using the most, and personally I also enjoyed NOS M7 quite a bit.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
As offensive as your post can be to developers, I do agree that a sense 5 ROM is most likely what the OP will enjoy using the most, and personally I also enjoyed NOS M7 quite a bit.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I wasnt trying to be offensive by any means. I understand the work that goes in to these roms and I appreciate it immensely. BUT I wanted to give this guy my most honest opinion from my experience. I don't want him to end up Rom swapping like mad if he doesn't have to, I've had zero problems with NOS M7. On Cyanogen I had force quits, bluetooth cutting in and out, wireless tether dropping constantly, now I have none of that.
mracrawford said:
I wasnt trying to be offensive by any means. I understand the work that goes in to these roms and I appreciate it immensely.
Click to expand...
Click to collapse
No, you don't or you wouldn't call it circle jerking. Given the OPs requirements a sense 5 ROM, NOS M7 in particular would seem to best fit his requirements, which also seems to fit yours, no reason to talk like that about our work OR the users that support and enjoy it enough to recommend another user give it a try, even though they really don't meet the OPs stated needs in a ROM. Everyone has their opinion, especially on XDA, there's no reason to be insulting because you disagree with their ROM choice.
Tapatalked from my HTC DNA - Carbon
Bad terminology, you're correct. It's been a looooooong day, and lots of work, lots of redditting, saw the term and used it. I should have re-read my post before I said I wasn't trying be insulting because that totally was. I'm sorry.
mracrawford said:
I wasnt trying to be offensive by any means. I understand the work that goes in to these roms and I appreciate it immensely. BUT I wanted to give this guy my most honest opinion from my experience. I don't want him to end up Rom swapping like mad if he doesn't have to, I've had zero problems with NOS M7. On Cyanogen I had force quits, bluetooth cutting in and out, wireless tether dropping constantly, now I have none of that.
Click to expand...
Click to collapse
Carbon is my daily driver and I've had zero problems. Granted I don't use blue tooth or tether, but I haven't had a single force close. I had some connection issues, but due to a bad flash.
Sent from my Nexus 7 using xda app-developers app
I personally used the Moonshine method. It was very simple. I already use a Linux distribution so my PCs OS wasn't an issue. Just run the exploit and, for me at least, everything went very smoothly. I tried out CM10.1, Revolt, Carbon, Rootbox (one of the earlier more buggy builds), and Hatka Supreme. I'm currently running CarbonROM (the 6/11 build) with stock kernel and am loving it! I've considered trying the latest build of Rootbox, but not sure if I want to go through the setup process again. Its all a matter at personal opinion, just my $0.02 USD!
Sent from my HTC6435LVW using xda app-developers app
I just moonshined my phone, so now it's time to look at each of the ROM's that you guys mentioned! Thanks again for the help in this!!
+1 for NOS M7 haven't had a single issue with it. Only issues I have had are with mods or themes for it. Can't speak for an AOSP ROM as I haven't tried one yet. Also FYI I would recommend using crpalmer's kernel.
I'm in the same boat OP. I tried Viper's rom and it was too much of a change for me. I wasn't ready to ditch the stock (or a stock-like) interface yet. Been researching roms, but it's tough like mentioned earlier, b/c it's very subjective.
I just want everything to work, debloat, hotspot capabilities and some customization options. I like the stock look and I haven't had the phone long enough to tire of it just yet.
I've had a rooted phone before and I do get bored with things after a while, so I know I'll run through roms over the next time period before I buy a new phone. I want to get my mileage out of each one.
I tried to download Hatka (sp?) earlier today, but I guess it's unavailable atm.
Downloading Nos7 now. It's going EXTREMELY slow though. I even switched to wifi and still at 5% after 4 minutes.
natypes said:
I'm in the same boat OP. I tried Viper's rom and it was too much of a change for me. I wasn't ready to ditch the stock (or a stock-like) interface yet. Been researching roms, but it's tough like mentioned earlier, b/c it's very subjective.
I just want everything to work, debloat, hotspot capabilities and some customization options. I like the stock look and I haven't had the phone long enough to tire of it just yet.
I've had a rooted phone before and I do get bored with things after a while, so I know I'll run through roms over the next time period before I buy a new phone. I want to get my mileage out of each one.
I tried to download Hatka (sp?) earlier today, but I guess it's unavailable atm.
Downloading Nos7 now. It's going EXTREMELY slow though. I even switched to wifi and still at 5% after 4 minutes.
Click to expand...
Click to collapse
Here is the Hatka download http://www.androidfilehost.com/?fid=22909751817929231
I run CM10 only
Droid DNA
Good Morning to you all!
Sorry if this has already been posted but I couldn't find much of anything on this topic. Does a "Google Edition" Rom exist for the EVO 4G LTE? I know we have the AOSP and AOKP roms but this is something I've wanted to ask for a while. I love the pure Google experience and I just have to wait about a year until i can upgrade to a new phone like a Nexus.
Thank you again for taking the the time to read this and for all the awesome work all you Developers put in for making this awesome phone even better.
Sent from my EVO using xda app-developers app
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
I'm with you on that one. Not sure why anyone with knowledge of rooting (who doesn't mind a voided warranty) would want to buy a GE phone.
______________________________
HTC Evo 4G LTE
I don't have any problem with any AOSP Rom other than signal and connectivity issues. But its really just curiosity for me and I'm a big fan of Google so the idea of having a Google Editon EVO sounds cool to me.
Sent from my EVO using xda app-developers app
Well it won't happen.
And aosp is just as much Google as a GE would be.
Sent from my Nexus 7 using xda premium
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
scottspa74 said:
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
ZamoraDC said:
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You could always try Evervolv. That's probably the closest to AOSP, that is, with the least customization.
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
How difficult is this to do?
Sent from my EVO using xda app-developers app
ZamoraDC said:
How difficult is this to do?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I can't say.
For the DNA it was extremely simple (but zarboz is a boss so he would've gotten it anyway) since the two devices are almost identical (One and DNA).
But the fact that you guys have a 3.4.x official HTC kernel should help.
hacked together using core binaries from other devices when necessary.
Click to expand...
Click to collapse
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
If you think about it, this site probably wouldn't even exist if OEMs made good software. They often do have access to proprietary drivers and documentation, but most of that is slowly getting open sourced anyway.
That type of reasoning is a fallacy because more often then not OEMs are just too plain cheap to do things properly. They just need to hit their deadlines. So your only real options are to either buy a nexus device, or invest a little time in helping fix any issues that you may find.
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
Have you ever used one of the IRC builds of cm10 or cm10.1? They're more stable and are more feature rich than the stock ROM that shipped with this device or any of the updates that they were gracious enough to let sense users download over the air. The 3.0 kernel was seriously stable, but the 3.4 kernel is (nearly as) stable _and_ leaves more RAM for your silly animation effects and whatever. It's based on the reference kernel for the chip set, if I'm not making an arse of myself. So pick a build. I know 1/16 was an awesome cm10, and like I said in another topic I had 191 hours uptime on the 7/23 cm10.1 before I rebooted to rule out the ROM when I was having data issues(it was the network) </rant>
Sent from my EVO using xda app-developers app
xHausx said:
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
Click to expand...
Click to collapse
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
xHausx said:
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
Click to expand...
Click to collapse
Ha! That was my first smartphone! I first signed up on xda (under a different name) when that phone launched (I got it as the att tilt) so that I could run manila and then android on it! That display driver issue was so frustrating. Sorry for ot, but I haven't thought about that in ages.
CNexus said:
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
Click to expand...
Click to collapse
It's not accurate to say the binaries are made for other devices when the devices are all basically the same. The MSM8960, for example, has it's own binaries, but the same chip is used in a range of devices from the Evo LTE, Blackberry Z10, One X (LTE), One XL, Windows Phone 8X, LG Mach, Moto Droid Razr M, Droid Razr, Razr Max, Atrix HD, Incredible HD, Xperia GX TL SX & V, Galaxy S III... the list goes on
The binaries all of those devices use were developed for the Qualcomm devkit I've linked below.
When you're working with a sense ROM versus an AOSP ROM there are many differences in not only appearance but the framework as well, but once you start getting down to the kernel level the hardware is all basically the same. Where we have the advantage over OEMs is that most companies know it's counterproductive and a waste of money to go after enthusiasts who borrow their binaries from one device to use on something else. If an OEM did that they would be sued in a heartbeat.
https://developer.qualcomm.com/mobile-development/development-devices/snapdragon-s4-msm8960-mdps
edit: probably actually this instead, but same difference: http://shop.intrinsyc.com/products/dragonboard-members-only
To digress back to the OP's original question though, the google edition One is basically just the one with AOSP on it. If you can find a pure AOSP ROM it'll be the exact same thing.
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
ZamoraDC said:
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Why don't you just build AOSP? You can use the CM kernel and pull the relevant vendor files from an existing AOSP ROM (or find an up-to-date github with them).
That way you don't have to worry about having the extra customizations, but you'll still have a kernel built from Qualcomm source along with the ROM.
asop aokp cm
I have tried a lot of ROMs and I find these devs do a much better job than stock ROMs yes you have some bugs in some but the always work them out cudos to the devs I'm just glad they still support my device and having gabe up on it
I plan on building and porting one of the 2 roms! Not both. I love both roms. Just maintaining both would be time consuming. I'd just like to no witch one people would be more interested in?
SighIsAnonymous said:
I plan on building and porting one of the 2 roms! Not both. I love both roms. Just maintaining both would be time consuming. I'd just like to no witch one people would be more interested in?
Click to expand...
Click to collapse
Firefox os.
Sent from my SGH-I777 using xda app-developers app
SighIsAnonymous said:
I plan on building and porting one of the 2 roms! Not both. I love both roms. Just maintaining both would be time consuming. I'd just like to no witch one people would be more interested in?
Click to expand...
Click to collapse
Ubuntu Touch because we can use most of the android apps in the new ROM as well
http://forum.xda-developers.com/showthread.php?t=2173773
bleggy said:
http://forum.xda-developers.com/showthread.php?t=2173773
Click to expand...
Click to collapse
I understand he has a working ROM! But I read through the comments on his post. From what I understand he's not working on it anymore. Or he had a problem I forget. Also its very outdated!:d But if he begins to continue working on it, Ill go ahead and port Firefox OS.
Just an update guys! My i777's charger port F***ed up. I'm awaiting another, I'm going to replace it when it gets here(This Friday or next Monday hopefully.) I've set up my build environment, but as you no some crucial files needed to build UBUNTU TOUCH can only come from my phone Via adb! I know there's other ways of retrieving these files, I'm just to lazy! Anyways all I need it my phone back to life!!!!! Then I will begin building and porting UT to our i777. If I can't find a fix for what I'm taking as a BIG SCREW UP ON CANONICALS PART(Love ya Canonical!) regarding some Bugs or something not reading a locked SIM I guess. Ill go ahead and begin instead building and porting Firefox OS.
are you ok?