How hard would it be.. - Droid Eris Q&A, Help & Troubleshooting

So out of curiosity, how hard would it be to port over a N1 rom to the eris? I don't really have any experience in making ROMs but I have a kitchen installed on my spare computer and would like to make one. I heard porting is easier than building from the ground up. But then I figure I'd have to change the resolutions, radio, etcetc. Or would it not be that hard? Thanks.

Sheen160 said:
So out of curiosity, how hard would it be to port over a N1 rom to the eris? I don't really have any experience in making ROMs but I have a kitchen installed on my spare computer and would like to make one. I heard porting is easier than building from the ground up. But then I figure I'd have to change the resolutions, radio, etcetc. Or would it not be that hard? Thanks.
Click to expand...
Click to collapse
Hard. The N1 is a totally different platform with a different processor and screen resolution. Its better to stick to porting from phones that are closer to the Eris.

punk.kaos said:
Hard. The N1 is a totally different platform with a different processor and screen resolution. Its better to stick to porting from phones that are closer to the Eris.
Click to expand...
Click to collapse
Alright. Thanks Kaos, you're the man

Related

[MODS] Step up and identify yourselves.

I'm just curious who these seasoned devs are in here. I'm trying to see where this is going cause right now I see two paths: a really useful resource or a super duper kangkit/get rich quick scheme.
Until then I'm off to cook some food, not a rom.
TheDudeOfLife said:
I'm just curious who these seasoned devs are in here. I'm trying to see where this is going cause right now I see two paths: a really useful resource or a super duper kangkit/get rich quick scheme.
Until then I'm off to cook some food, not a rom.
Click to expand...
Click to collapse
I'm envisioning a multipurpose/variety thread. The likes of which never before seen. A thread so historically consequential, that the once elusive trade magic, some only hinted of in the fables of yesteryear, will be exposed, explained and made the standard. Oh yes, I'm with you when you say, "sounds much too important for just one dev to endure singlehandedly!" Which is why I bring you, the thread which will overclock your kernels 'till they pop ............................................................TOP ROM N' COOKING WITH YOUR HOSTS, DUDE AND KING!!
My mom says hi
I'd really like to see this become an active source of information between developers. A place where even some of the best can learn a thing or two.
Anyway... stepping up:
NPRussell
Creator of the various VillainROMs on the HTC Hero, capable of more than file moving and winzip, luckily.
I'll help out in here as much as possible to help get things moving!
@Cyanogen; Great introductory thread
I'm no mod, but I do have some priveleges.
Let me introduce myself.
Most of you won't know me for my efforts on Winmo i guess, since this is Android Chef Central. I worked with the best guys on creating a driver(pack) for Windows based MSM7XXX devices.
Now, I'm helping out XDA as much as I can.
Pleased to meet.
I am jcarrz1, an activist in the community and a fairly basic rom modder, etc. that looks for unique roms/bases and ideas for my creations.
not anything special, mind you.
im jamezelle(James L.) I dev for vogue-android, the eris and motodroid.
jamezelle said:
im jamezelle(James L.) I dev for vogue-android, the eris and motodroid.
Click to expand...
Click to collapse
wow all this time I thought I read some where you were a woman....don't know where I got that from lol....still loving Sense-able...
I myself can only winzip and push files plus some recoloring in gimp still trying to learn more...
NeoS2007 said:
I'm no mod, but I do have some priveleges.
Let me introduce myself.
Most of you won't know me for my efforts on Winmo i guess, since this is Android Chef Central. I worked with the best guys on creating a driver(pack) for Windows based MSM7XXX devices.
Now, I'm helping out XDA as much as I can.
Pleased to meet.
Click to expand...
Click to collapse
Hey man, your graphics driver packs were more than appreciated for my Diamond / Touch Pro / Touch HD ROMs! They made a difference.
BTW ... I'm dsixda, who got his life stolen away after starting on the Windows Mobile 6.x Onyx ROMs for the Elf/Elfin ;-)
Now that I'm on Android I really want to get back to doing actual development work. (I don't think writing Mortscripts for my ROMs count, do they?) However, the stock Android ROMs in my opinion are useful enough for my day-to-day activities... I'm just a file pushing guy for now ;-)
I am charansingh. Just learnt how to build cyanogen mod from source, Have been building overclocked kernels for personal use lately just for testing. Now digging into cyanogen mod source to see if i can see something interesting to learn, edit and make something new. Lately i edited setting in the camera to allow unlimited video record time kind of. And will be doing more as a get time to do it
Keep it clean guys!​
dsixda said:
Hey man, your graphics driver packs were more than appreciated for my Diamond / Touch Pro / Touch HD ROMs! They made a difference.
BTW ... I'm dsixda, who got his life stolen away after starting on the Windows Mobile 6.x Onyx ROMs for the Elf/Elfin ;-)
Click to expand...
Click to collapse
Hey thanks man. I'm glad i've helped out people with my packs. I'm new to Android so i won't be much of a help in the graphics department, but I hope to help out as much as I can to get the best out of our snapdragon chipsets.
LOL
Warped420 or Michael, started the LEGION MODZ TEAM. Learned everything I know about building from PlayfulGod and Junkie 2100.
Built a JellyBeer $ROM$. But no visual until we used Hroark13's legacy mods.
I made a Tutorial on XDA.
Always here to help
Edit. I really should slow down and read. I'm not a mod
BCRichster- Newer member of LEGION MODS Team. I got your back, Warped420!
Theming is my focus, but trying to learn as much as I can about everything I can. Android Rocks! :beer:
Sent from my confused Warp/Nexus using Tapatalk 2

Windows Phone 7 on Topaz... COME ON DEVS!

Hey, you probably heard that WP7 has been ported on HD2.
Well, that's a great start. But I think we can try it out... Even it would be a lot buggy or slow or anything else... I think if we contact DFT (Dark Forces Team) they might help us out... I know it's near impossible (because of our ARMv6 CPU. == WP7 needs an ARMv7 CPU which HD2 has it.) But it's not impossible completely... Let's do something about it... What do you say devs?
I'm just waiting for the hackers team is to discuss about this. Because I am only new person in the world PHONE.
im will suporter to u all
Come on ,it will be great to run wp7 on topaz
Oh golly, because you demanding it will sure make them motivated.
When you say "Lets do something" you must mean, "I cant do it, can you do it for me?". Why not learn reverse engineering, and then doing something yourself? Because realy, if you want dev's to do all the work for you, you obviously should stick to the Windows-GUI manipulation level, doubt being spoof-feed will help you.
Desert Storm said:
Oh golly, because you demanding it will sure make them motivated.
When you say "Lets do something" you must mean, "I cant do it, can you do it for me?". Why not learn reverse engineering, and then doing something yourself? Because realy, if you want dev's to do all the work for you, you obviously should stick to the Windows-GUI manipulation level, doubt being spoof-feed will help you.
Click to expand...
Click to collapse
First of all, I don't see any reason to answer you directly. In second, I'm a developer but can't do it alone. I'm asking for help. So just keep learning things. You may someday understand what I was asking for.
Personally, I wouldn't mind seeing a port for the Topaz, and I'd probly try it out... But I'm looking forward to the cracking of WP7 on WP7 phones so that I can upgrade to a new phone and not be stuck with that horrible start screen
Black.Heart said:
First of all, I don't see any reason to answer you directly. In second, I'm a developer but can't do it alone. I'm asking for help. So just keep learning things. You may someday understand what I was asking for.
Click to expand...
Click to collapse
I know you have some developing skills, although I dont know if it goes beyond changing the registry and gui-manipulation, but the system-level developers are unlikely to port the Windows 7 to the Topaz, mainly because its a old device now, outdated and slow.
(And I know that you've got some knowledge because I used eclipse for few days, good ROM)
Desert Storm said:
I know you have some developing skills, although I dont know if it goes beyond changing the registry and gui-manipulation, but the system-level developers are unlikely to port the Windows 7 to the Topaz, mainly because its a old device now, outdated and slow.
(And I know that you've got some knowledge because I used eclipse for few days, good ROM)
Click to expand...
Click to collapse
I appreciate that... But as I mentioned above, it's near impossible... Not completely. Your'e right... Topaz has ARMv6 processor... WP7 requires ARMv7. But i'm talking about experiencing it on Topaz... By the way, I agree with oldness of Topaz... I'm gonna buy a Desire HD
It's wishfull thinking and never going to happen. The best us topaz owners can expect to get for our outdated phones is a 100% working Android.
hoosbude said:
The best us topaz owners can expect to get for our outdated phones is a 100% working Android.
Click to expand...
Click to collapse
And wouldn't that be great!!!!
That ain't true I find that the ui from wp7 is lite and simple. This can easily be ported to our devices with a little magic. But The part of windows live games or xbox live is the part that our devices cant handle. Our devices aren't old they where made cheap by htc and att to cover some sectors of the market. But our devices could have been easily been made with the same stuff as hd2, as few months passed since each launched.
The ui is simpler than ours and faster I think it could be done......just that I need to finish studying by then to make this. And I don't think of waiting is another great idea. As we are shadowed by what could have been if we had a twin processor to hd2's. But, we bought this and I find it great!
And please respect each other!!!!!
I think it's NOT possible because of hardware requirements.
mahra said:
I think it's NOT possible because of hardware requirements.
Click to expand...
Click to collapse
our device was made of tinking on this.. As I read before it was tought to be ported in form of an upgrade. But it was left in the clouds. And our device have the custom buttons on a new device like android and wp7. Ram can't be a prob. If the UI was made for speed and simplicity. Just the xbox live games won't run properly.
joefrank said:
our device was made of tinking on this.. As I read before it was tought to be ported in form of an upgrade. But it was left in the clouds. And our device have the custom buttons on a new device like android and wp7. Ram can't be a prob. If the UI was made for speed and simplicity. Just the xbox live games won't run properly.
Click to expand...
Click to collapse
I agree... But no one is taking TD2 seriously. Because there are at least 2 similar devices (TP2, THD) no one is focusing on TD2. That's why we don't see any salient improvement on Android development. HD2 devs focused on it and made the progress finished soon. I think the best way we can do right now, is contacting Cotulla from DFT. He could help me and other devs. I just don't know how to contact him!
Black.Heart said:
I agree... But no one is taking TD2 seriously. Because there are at least 2 similar devices (TP2, THD) no one is focusing on TD2. That's why we don't see any salient improvement on Android development. HD2 devs focused on it and made the progress finished soon. I think the best way we can do right now, is contacting Cotulla from DFT. He could help me and other devs. I just don't know how to contact him!
Click to expand...
Click to collapse
AH man! I've been focussing on another site. WWW.htc-pure.com, which I am a moderator. And for years I've been here quietly. but I think I will try to move here to help. Lets see what I can do.
wp7 requires ARMv7 instruction set on cpu. but topaz is just ARMv6 i think. that's why I think it's not possible
Moreover, why would you want WP7? The only thing it has going for it is that it runs smoothly and doesn't crash, which it would NOT do if someone did manage to port it. Better off building skins over 6.5.x; that way you could at least retain functionality...
joefrank said:
AH man! I've been focussing on another site. WWW.htc-pure.com, which I am a moderator. And for years I've been here quietly. but I think I will try to move here to help. Lets see what I can do.
Click to expand...
Click to collapse
I am waiting, good luck man
Black.Heart said:
I agree... But no one is taking TD2 seriously. Because there are at least 2 similar devices (TP2, THD) no one is focusing on TD2. That's why we don't see any salient improvement on Android development. HD2 devs focused on it and made the progress finished soon. I think the best way we can do right now, is contacting Cotulla from DFT. He could help me and other devs. I just don't know how to contact him!
Click to expand...
Click to collapse
actually, hd2 had devices that only need to be (partially) reverse-engeneered. hell some libs etc worked directly from Desire, cotulla took half of its radio SW to get rmnet data working and ...HD7...well it's hd2 without hardware buttons!...
magldr is child's play and development was over in 2 months but they kept it testing for that time to see how phone will respond to tottaly diffrent os.
now find something like that for Touch(something).
htc was lazy with hardware at the time and hackers took advantage of that.
but these devices nature is so much different that every piece of system would have to be homebrew-and devs struggle with android for a long time with sources and inch from their nose. imagine rewriting even basic parts of kernel to support armv6 without any proper source. i truly can't imagine wp7 being done...
even with few developers, reasonable timeframe would be over year or two!
i own 3 htc phones and one td2 just for fun of it, to see evolution of htc's over the years.. go buy yourself hd2 if you really wish to hack the hell out of your phone. they go really cheap - around $200 - and save yourself time
stirkac said:
actually, hd2 had devices that only need to be (partially) reverse-engeneered. hell some libs etc worked directly from Desire, cotulla took half of its radio SW to get rmnet data working and ...HD7...well it's hd2 without hardware buttons!...
magldr is child's play and development was over in 2 months but they kept it testing for that time to see how phone will respond to tottaly diffrent os.
now find something like that for Touch(something).
htc was lazy with hardware at the time and hackers took advantage of that.
but these devices nature is so much different that every piece of system would have to be homebrew-and devs struggle with android for a long time with sources and inch from their nose. imagine rewriting even basic parts of kernel to support armv6 without any proper source. i truly can't imagine wp7 being done...
even with few developers, reasonable timeframe would be over year or two!
i own 3 htc phones and one td2 just for fun of it, to see evolution of htc's over the years.. go buy yourself hd2 if you really wish to hack the hell out of your phone. they go really cheap - around $200 - and save yourself time
Click to expand...
Click to collapse
I agree. I'm moving to iPhone 4 or Sensation or EVO 3D...

[Q] Froyo with Sense for Rhodium?

Okay so this may be a useless post and it is my first one so don't beat me up too badly. I have been searching all over the place to find a Froyo build with HTC Sense. It seems as though development has been halted because apparently Sense is too large for the Rhodium CPU and the screen resolution is too high. How can this be true when the Rhodium runs Sense in Windows Mobile 6.5? I want to see a Froyo build that has HTC Sense and camera support. Can or has this been done? Would someone be willing to do it if enough people were willing to donate? I just want my Rhodium to work the way I know it can. I know there is a 2.1 build with Sense but there is no camera and there are many bugs with it and is not useful to me. Any help is greatly appreciated.
If anyone finds any Froyo with sense builds for phones that are NOT the HD or HD2, please post a link to them in this forum.
Thank you.
Sense on WinMo != Sense on Android
So don't confuse them. Why do you want sense? It's just a big piece of bloat, and most of the things you can find in other places (IE Fancy Widget).
Sense in Winmo is native code, Sense in Android is Java. Unfortunately, the gains in terms of development ease gained with Java are offset by the inefficiencies of Java on lower-end hardware.
Also, the problem with Sense is that it needs to be ripped from a Sense-enabled HTC native Android device, and in many cases, the binary has enough customization that it does Bad Things on our devices.
As I understand it, the only Sense-enabled build seen on our devices so far was 2.1, and had, as you mention, resolution issues.
Also keep in mind that the Windows Mobile stock UI was very dated, so Sense was a major upgrade for it. My experience with Sense-enabled Android devices is that it offers very little and just slows the device down. Actually, this seems true for all manufacturer-provided alternate interfaces (like the crappiness of MOTOBLUR...)
Entropy512 said:
Sense in Winmo is native code, Sense in Android is Java. Unfortunately, the gains in terms of development ease gained with Java are offset by the inefficiencies of Java on lower-end hardware.
Also, the problem with Sense is that it needs to be ripped from a Sense-enabled HTC native Android device, and in many cases, the binary has enough customization that it does Bad Things on our devices.
As I understand it, the only Sense-enabled build seen on our devices so far was 2.1, and had, as you mention, resolution issues.
Also keep in mind that the Windows Mobile stock UI was very dated, so Sense was a major upgrade for it. My experience with Sense-enabled Android devices is that it offers very little and just slows the device down. Actually, this seems true for all manufacturer-provided alternate interfaces (like the crappiness of MOTOBLUR...)
Click to expand...
Click to collapse
Just to back this up, I used one of Tiad's Froyo Sense builds for a bout 2 minutes. It it not worth it. Definitely, not worth it.
ryannathans said:
Just to back this up, I used one of Tiad's Froyo Sense builds for a bout 2 minutes. It it not worth it. Definitely, not worth it.
Click to expand...
Click to collapse
Where did you get Froyo Build from Tiad including Sense? AFAIK he just released Eclaire builds containing the UI...
wavesshock said:
Where did you get Froyo Build from Tiad including Sense? AFAIK he just released Eclaire builds containing the UI...
Click to expand...
Click to collapse
He claimed they were Froyo, I only looked at it literally for a minute and never noted what it actually was. I wouldn't be surprised if it was Eclaire.
Anyway, when I get this bloody repo sync command to go through without errors I will start making my own builds I guarantee, they will be better than Tiad, and I don't exactly plan on including any warez
ryannathans said:
He claimed they were Froyo, I only looked at it literally for a minute and never noted what it actually was. I wouldn't be surprised if it was Eclaire.
Anyway, when I get this bloody repo sync command to go through without errors I will start making my own builds I guarantee, they will be better than Tiad, and I don't exactly plan on including any warez
Click to expand...
Click to collapse
Are you going to make sense-builds or do you plan to develop on stock android ports?
Entropy512 said:
Sense in Winmo is native code, Sense in Android is Java. Unfortunately, the gains in terms of development ease gained with Java are offset by the inefficiencies of Java on lower-end hardware.
Also, the problem with Sense is that it needs to be ripped from a Sense-enabled HTC native Android device, and in many cases, the binary has enough customization that it does Bad Things on our devices.
As I understand it, the only Sense-enabled build seen on our devices so far was 2.1, and had, as you mention, resolution issues.
Also keep in mind that the Windows Mobile stock UI was very dated, so Sense was a major upgrade for it. My experience with Sense-enabled Android devices is that it offers very little and just slows the device down. Actually, this seems true for all manufacturer-provided alternate interfaces (like the crappiness of MOTOBLUR...)
Click to expand...
Click to collapse
Thank you. This makes some sense of it (no pun intended). I know there are other widgets that use less resources and look better than sense but I like the look and feel of it. I am probably going to be upgrading to an Evo 4g or Evo 3g so I'll have my sense soon anyway but I was able to get some use from the 2.1 sense build once I used a new kernel and used the "clean slate" scene setting. The only thing missing was the camera. I can get by with some sluggishness as I have been using Windows Mobile for a long time but I cannot get by without that camera support seen in the newer 2.2 builds. Also, the Hero has the same CPU speed as the Rhodium. I am not sure if this makes much difference but the phones are very similar in both screen size and processor speed. As well as the Evo Shift as far as screen. I am still new to all this though and those subtle similarities may really be nothing. I'll keep searching and post if I find anything.
ryannathans said:
Just to back this up, I used one of Tiad's Froyo Sense builds for a bout 2 minutes. It it not worth it. Definitely, not worth it.
Click to expand...
Click to collapse
Where did you get those builds? That was the question I asked in the initial post lol. I love testing so I don't really care if they suck.
nickelghandi said:
Where did you get those builds? That was the question I asked in the initial post lol. I love testing so I don't really care if they suck.
Click to expand...
Click to collapse
On his website, because tiad8 has been banned from xda-devs.
@nickelghandi
Maybe you can test the panda homescreen with sense theme.
http://forum.ppcgeeks.com/android-tp2/113446-nsfw-post-your-tp2-android-home-screen-7.html
Hi,
Is there any way to install some of the Sense applications (Music, Video, Image player) on a HTC Touch Pro2 with the CBX0 Android ROM?. I have a Hero device with almost the same hardware and the Sense applications runs well and I´m use with these applications.
Regards,
clarf
clarf said:
Hi,
Is there any way to install some of the Sense applications (Music, Video, Image player) on a HTC Touch Pro2 with the CBX0 Android ROM?. I have a Hero device with almost the same hardware and the Sense applications runs well and I´m use with these applications.
Regards,
clarf
Click to expand...
Click to collapse
If you can find the APK's, maybe.
But Sense is a proprietary thing. So it's not 'open' - not easily ported/moved to other devices. All XDAndroid builds are AOSP - straight from Google. All open source.
Good luck. If you want, there's a 2.1 Eclair Sense build - but it hasn't been updated since 2010.
arrrghhh said:
If you can find the APK's, maybe.
But Sense is a proprietary thing. So it's not 'open' - not easily ported/moved to other devices. All XDAndroid builds are AOSP - straight from Google. All open source.
Good luck. If you want, there's a 2.1 Eclair Sense build - but it hasn't been updated since 2010.
Click to expand...
Click to collapse
Thanks for reply,
Well many functions on my HTC phone have issues with old kernel versions, I don´t think I could use Eclair Sense if it´s not maintained/updated.
I´ll search first for the APK´s then...
Thank you
clarf
clarf said:
Thanks for reply,
Well many functions on my HTC phone have issues with old kernel versions, I don´t think I could use Eclair Sense if it´s not maintained/updated.
I´ll search first for the APK´s then...
Thank you
clarf
Click to expand...
Click to collapse
You could always try a new kernel on an old system...
But either way, that stuff is ancient.

Rom porting

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.

Interested in BeagleBoard / PandaBoard

Hey peeps.
Was looking at these boards online, does anyone here really use them? If so do you find them usefull for developing ROMs?
Ive never used them before but it looks pretty interesting.
As I understand you could build an Android ROM and boot it up on an SD Card installed in the board plugged into a TV?
Is there any benifit using these over an actual device? Apart from the odd bricking lol
CdTDroiD said:
Hey peeps.
Was looking at these boards online, does anyone here really use them? If so do you find them usefull for developing ROMs?
Ive never used them before but it looks pretty interesting.
As I understand you could build an Android ROM and boot it up on an SD Card installed in the board plugged into a TV?
Is there any benifit using these over an actual device? Apart from the odd bricking lol
Click to expand...
Click to collapse
I have an engineering buddy who owns a Beagle Board specially the Beagle Bone black and he used it to follow along with a lot of the free-electrons training material, he loved it learned a lot he said allowed him to get a lot more exposure to embedded development at all stages of the process. He also used it experiment with compiling ROM's, which he liked to use more then his phone (He only had one device to develop one) because whenever he would mess something up he could easily re-flash a working image and didn't have to risk his phone. As far as benefits are concerned there easier to work with in-terms of flashing and risk then regular devices, you can do more with them then most phones/tablets (You can flash literally anything on it from different bootloaders and homemade bootloaders, to other cool electronics projects). Overall he said it was great to have around as an all purpose learning board and project board for all areas of Android development and other embedded tasks. The Panda Board hasn't been updated in several years, and while it was good at the time is pretty outdated now. Additionally the Beagle Board is cheaper and has better hardware then the Panda Board.

Categories

Resources