Any chance of getting cm, maybe official so we can use the amazing cyandelta app.
Sent from my ADR6410LVW using xda app-developers app
playmobot said:
Any chance of getting cm, maybe official so we can use the amazing cyandelta app.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
That requires either a CM guy to have our phone and decide to develop for it, or one of our amazing dev's to port it. Since we just got the ability to unlock the bootloader, It'll take a little while for things to ramp up. Baby steps.
Patgt500 said:
That requires either a CM guy to have our phone and decide to develop for it, or one of our amazing dev's to port it. Since we just got the ability to unlock the bootloader, It'll take a little while for things to ramp up. Baby steps.
Click to expand...
Click to collapse
How hard can it be to port CM?? I ask because I am considering attempting to do this over thanksgiving... I never ported CM before and I don't have much of an understanding of the Android Source code... But I can get my way around basic source code editing, if I have a lot of help... So, if someone can tell me how to start porting this thing, I may attempt to do so over thanksgiving.. but don't get your hopes up, I am just a novice dude here...
I think there are some porting guides on xda somewhere for cm9 try looking at those. Im willing to test builds by the way.
Sent from my ADR6410LVW using xda app-developers app
I would imagine it would be fairly difficult, the rezound took some time to get AOSP on it.
litetaker said:
How hard can it be to port CM?? I ask because I am considering attempting to do this over thanksgiving... I never ported CM before and I don't have much of an understanding of the Android Source code... But I can get my way around basic source code editing, if I have a lot of help... So, if someone can tell me how to start porting this thing, I may attempt to do so over thanksgiving.. but don't get your hopes up, I am just a novice dude here...
Click to expand...
Click to collapse
Ya gotta start somewhere. Good luck!
good luck my friend.
prepare for many sleepless, banging head against the wall - nights/mornings.
What Andy said lol. Also, look in the rez forums, there are a few developers there who have already encountered some of the issues you may and they may be able to help you (particularly Chad)
Sent from my ADR6410LVW using Xparent Blue Tapatalk 2
Hehe I have a Jellybean AOKP test build available. Tester needs S-ON bootloader unlocked. Not S-Off, cause I don't want to brick anyone. Also need to be able to get/send me a logcat of the build. PM me.
dmeadows013 said:
Hehe I have a Jellybean AOKP test build available. Tester needs S-ON bootloader unlocked. Not S-Off, cause I don't want to brick anyone. Also need to be able to get/send me a logcat of the build. PM me.
Click to expand...
Click to collapse
Well that was quick! You're a boss dmeadows. Post that shiz in development, I'd help but I'll be busy until Sunday night unfortunately
Sent from my ADR6410LVW using Xparent Blue Tapatalk 2
dmeadows you just made my night. No joke.
Sent from my ADR6410LVW using Tapatalk 2
dmeadows013 said:
Hehe I have a Jellybean AOKP test build available. Tester needs S-ON bootloader unlocked. Not S-Off, cause I don't want to brick anyone. Also need to be able to get/send me a logcat of the build. PM me.
Click to expand...
Click to collapse
Great job!!! I can test it but briefly tonight. Or after Sunday.
Sent from my ADR6410LVW using XDA Premium HD app
I Dont mind testing as well. Pm me if you need peepz
Sent from my ADR6410LVW using xda app-developers app
Is this still being worked on? It would be great to have it. Thanks.
Sent from my ADR6410LVW using xda app-developers app
+1 miss aosp
Linch89 said:
+1 miss aosp
Click to expand...
Click to collapse
dmeadows013 said something about a build being available but not quite sure if he was being serious or not. Anyway, I have a plan cooking up. I will download source and try to compile it, but fair warning I am a total newb to aosp deving and it may take forever, or never, to make a working AOSP build. I'm getting myself a new laptop which should help me build this thing. So far I put it off as my primary machine is tied up doing my regular work and with this spare laptop, I can do the hell I want while doing my regular work. Multitasking at its best!
Also, I really want to get some pointers on how to setup the build for a new device. I know that if all we are trying to do is build for a device that is already supported, then you already have the necessary files to compile it for that device. But, what I don't know is how to set up the build environment for a new device. Someone with some know how will be greatly appreciated. Thanks!
litetaker said:
dmeadows013 said something about a build being available but not quite sure if he was being serious or not. Anyway, I have a plan cooking up. I will download source and try to compile it, but fair warning I am a total newb to aosp deving and it may take forever, or never, to make a working AOSP build. I'm getting myself a new laptop which should help me build this thing. So far I put it off as my primary machine is tied up doing my regular work and with this spare laptop, I can do the hell I want while doing my regular work. Multitasking at its best!
Also, I really want to get some pointers on how to setup the build for a new device. I know that if all we are trying to do is build for a device that is already supported, then you already have the necessary files to compile it for that device. But, what I don't know is how to set up the build environment for a new device. Someone with some know how will be greatly appreciated. Thanks!
Click to expand...
Click to collapse
I would talk to dmeandows, I tested a few builds for him that didn't boot up
you want CM, get a phone to AREOEVAN. he's the one that can do it.
Aldo101t said:
you want CM, get a phone to AREOEVAN. he's the one that can do it.
Click to expand...
Click to collapse
this is true, we should start a bounty thread for him to get aphone
Yesssssssssss let's get Evan's ass over here
Related
Obviously CM7 Development is not dead at this time. http://forum.xda-developers.com/showthread.php?t=1304881
No u should be working on reading a little. Mrinehart is working in his build in his spare time. He is a full time student. He has a device and several members test his work.
The other build (GSM) is under construction in HIS spare time. These things take lots of time. Be patient.they are being worked on.
Sent phrom my Mo-Pho
It's not dead...
Sent from my MB855 using xda premium
I believe the GSM Dev said himself he wouldn't support it as he wouldn't have time. So he's done what he can, I believe. And the CDMA one will be worked on again in probably a week or so. I think he had three weeks worth of school work that too priority.
xTMFxOffshore said:
I believe the GSM Dev said himself he wouldn't support it as he wouldn't have time. So he's done what he can, I believe. And the CDMA one will be worked on again in probably a week or so. I think he had three weeks worth of school work that too priority.
Click to expand...
Click to collapse
Ok, makes sense, was a little confusing with both ROMs getting quick updates and then dying off for a while.
I think the GSM build was based off the CDMA build and that was has been a long painful process to even get it booting.
xTMFxOffshore said:
I think the GSM build was based off the CDMA build and that was has been a long painful process to even get it booting.
Click to expand...
Click to collapse
I thought it was independent, as the CDMA build did not have CDMA actually working. BTW is there source code for the GSM build?
It may have been, I'm not totally sure. As for source code, You'd have to PM the Dev and ask. I have no idea on that.
It's on his github,
Lightsword1942 said:
I thought it was independent, as the CDMA build did not have CDMA actually working. BTW is there source code for the GSM build?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
As far as progress goes, alcohol(not money) is required as development is a huge pain in the (edited for language). It's trial and error and some people just have magical powers that others don't. Cm7 is based on aosp, while motoblur is too, motorola makes there own stuff to get it to work. Then they make there special files/drivers depend on other stuff that's theirs. Some of these drivers/files have no source. Theres where the problem is.
Now the GSM cm7 is actually a kang, or cm7 with built in moto files. The reason cdma doesn't work is because it isn't called correctly, as the files necessary are part of blur. The the other cm7 is pure cm. It's a long tedious road for anyone attempting cm but once we have it upgrading will be easy. Personally I think more people should be helping. Pm the CDMA dev and ask how to build to his point, sync with his git, read up on the cm forums and try to help. Even if you only fix a small thing, submitting it back to him and it will bring cm faster.
As far as me, I plan to start helping soon after I redo my dev box(ran out of room) . I hope others will too.
Sent from my MB855 using XDA App
jokersax11 said:
As far as progress goes, alcohol(not money) is required as development is a huge pain in the (edited for language). It's trial and error and some people just have magical powers that others don't. Cm7 is based on aosp, while motoblur is too, motorola makes there own stuff to get it to work. Then they make there special files/drivers depend on other stuff that's theirs. Some of these drivers/files have no source. Theres where the problem is.
Now the GSM cm7 is actually a kang, or cm7 with built in moto files. The reason cdma doesn't work is because it isn't called correctly, as the files necessary are part of blur. The the other cm7 is pure cm. It's a long tedious road for anyone attempting cm but once we have it upgrading will be easy. Personally I think more people should be helping. Pm the CDMA dev and ask how to build to his point, sync with his git, read up on the cm forums and try to help. Even if you only fix a small thing, submitting it back to him and it will bring cm faster.
As far as me, I plan to start helping soon after I redo my dev box. I hope others will too.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Well, I found cybik's(GSM) source code (https://github.com/cybik/Sunfire) and have been playing around with building it. I'm not sure how much help I can be with it though.
its true, development work is best done between .13-.20 BAC
seeing as how we don't pay these people to bring us anything, we can't really expect them to work on this day and night. I'm sure CM will be done eventually, I have no doubts about that. As for how long it's going to take, i really don't care. I'll happily accept a "when it's done" ETA.
devilsshadow said:
seeing as how we don't pay these people to bring us anything, we can't really expect them to work on this day and night. I'm sure CM will be done eventually, I have no doubts about that. As for how long it's going to take, i really don't care. I'll happily accept a "when it's done" ETA.
Click to expand...
Click to collapse
Yeah, I am just trying to see if there is anything that is holding development up.
shabbypenguin said:
its true, development work is best done between .13-.20 BAC
Click to expand...
Click to collapse
Balmers peak?
Sent from my MB855 using xda premium
Kcarpenter said:
Balmers peak?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Beat me to it...
Sent from my MB855 using xda premium
Kcarpenter said:
Balmers peak?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
relevant
http://xkcd.com/323/
It is dead
Sent from my MB855 using xda premium
LexLuger82 said:
It is dead
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Why is it you are always so negative? Yet don't contribute anything but complaining. Just curious.
Sent from my MB855 using XDA App
xTMFxOffshore said:
Why is it you are always so negative? Yet don't contribute anything but complaining. Just curious.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
lol pwnd..........
Even if you have no coding experience at all, you can help. Testing is the easiest way to help. There are millions of lines of code and ways to set up these phones. Testing is the most important part of the development process. Without testers bugs will roam free. There are two separate major test categories, kernels and roms. Then minor testing such as mods/themes/etc. Kernels are the brains of the phone. Roms is the body. Both need to be tested and both need to be improved. When you test please do more than just quadrant. Make specific repeatable comments that will help some one fix the issue. Thanks and happy testing
Sent from my MB855 using XDA App
Ill do some testing.
jokersax11 said:
Even if you have no coding experience at all, you can help. Testing is the easiest way to help. There are millions of lines of code and ways to set up these phones. Testing is the most important part of the development process. Without testers bugs will roam free. There are two separate major test categories, kernels and roms. Then minor testing such as mods/themes/etc. Kernels are the brains of the phone. Roms is the body. Both need to be tested and both need to be improved. When you test please do more than just quadrant. Make specific repeatable commits that will help some one fix the issue. Thanks and happy testing
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Im in for some testing
Sent from my MB855 using xda premium
I don't have the time, got a few $$$ to help someone buy a phone. can sens to your paypal Joker?
Sent from Photon 4G code name "Neo" using XDA Premium!
?
I have a photon already
dsims7_2000 said:
I don't have the time, got a few $$$ to help someone buy a phone. can sens to your paypal Joker?
Sent from Photon 4G code name "Neo" using XDA Premium!
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
I think he is refering to sending you money to buy a phone strictly for testing.... so you dont brick yours
Oh well i dont mind. Its almost impossible to brick this phone. As long as you dont play with bad bootloaders(*cough yay4juggs *cough).
gothymp said:
I think he is refering to sending you money to buy a phone strictly for testing.... so you dont brick yours
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
I do have a project i want tested. On the razr forum there is a project call debtop. Can someone flash my newest hardvfp kernel and test debtop on the photon. I believe i got the kernel to support it.
Edit gentop not debtop
Sent from my MB855 using XDA App
Ok - I'd love to help, but I'm not sure what your kernel is or the gentop is? I've rooted my phone, messed with a few simple things here and there, but other than that - I'm still learning. I did install a custom ROM on my old Hero, but I haven't messed with the Photon.
I do have time though - I work a lot of night shifts and if shown how to do something, I learn it quickly! If I can be any help, message me and I'll do what I can to help out!
I gotcha bubb. I'm in a 4G area if you you are still working on the bootloader
Hell I will even let you remote control my computer. Just don't go into the folder that says mmmm lol
No need. I actually know how to install a 64 bit operating system. Lol. Im slowly working on it. Its not a bootloader problem. Motorolas official engineering phones with real unlocked factory bootloaders dont have 4g. So obviously we gotta look elsewhere. Its possibly recovery related or some form of security check. Once we find exactly what it we can fix it. The best way is to dd everything. Like dd / lol. Once with stock, then after unlock only then recovey change. Once all three is pulled. Someone needs to run a diff, or physically cross check everything, eek. Once the culprit is found we will squash it. so obviously you can see this will be time consuming. Way more time then I ever get. I would have to take a vacation just to get that kind of time. I can do the squashing after the fact but atm im stuck trying to blindly fix it
AJC9000 said:
I gotcha bubb. I'm in a 4G area if you you are still working on the bootloader
Hell I will even let you remote control my computer. Just don't go into the folder that says mmmm lol
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
melodic manatee men masturbating lonely over leftovers.
Nope wont open that folder
AJC9000 said:
I gotcha bubb. I'm in a 4G area if you you are still working on the bootloader
Hell I will even let you remote control my computer. Just don't go into the folder that says mmmm lol
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Okay this is to everyone wanting to help. Find me cool patches. Remember your looking for arm no neon stuff the kernel is 2.6.32.9(kinda). I might update to .50 if I can ever find those patches. Most stuff I can manually patch and do, but 2.6.32.* patches are huge and I need .patch's to do that. If you find kernels from other phones with cool stuff please make sure they actually post source. A bfs 400+ patch for 2.6.32.9 would be awesome, so would proper autogroups. Post findings here.
Thanks and happy hunting
Sent from my MB855 using XDA App
I'm not a programmer but I would like to help if I can. Picked up my MoPho 3 weeks ago, rooted it, and did a couple buildprop tweaks but nothing else. Haven't unlocked it yet, either. I would like to flash a different rom and/or kernel but want to do more reading first. I also need to get the right sbf and such, too. Currently system version 45.3.6.MB855.sprint.en.us; Android 2.3.4; Baseband N_01.28.07R; Webtop WT-1.2.0-160; Kernel [email protected] #2; Build 4.5.1A-1SUN-198.6
I'm a MoPho-er
This is good!
Sent from my MB855 using XDA Premium App
I'd be happy to test, but I don't want to unlock the bootloader until it doesn't break 4g
Sent from my MB855 using xda premium
Joker this is just a thought but have you looked at the LTE drivers at all maybe something could be made from that or in any way be helpful
Lte drivers are there. Edit the build.prop
AJC9000 said:
Joker this is just a thought but have you looked at the LTE drivers at all maybe something could be made from that or in any way be helpful
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Not sure if I can say much on here but try to move the signal to Verizon.
I saw on the zumocast advert on the motorola website the photon was sporting the LTE icon. Maybe a minor error with one of the artists or maybe a hint...
IMPORTANT! I'm moving development to android-dev.us, if you want to know, read over there, HOWEVER, I will respond to anything posted over here
http://www.android-dev.us/showthrea...ion-CM7-SelfKang-Alphafied-Number-10-GB-2-3-7
Hey guys, I'm going to try to start to learn android rom development, and thought maybe porting a AOSP rom fromt the sensation would be a cool task to work with. Right now, I think the Sensation is the closest to our Amaze, but it's CM7 build is lacking. Either way, it will be a ton easier to port CM7 than CM9 for a complete noob, but that doesn't mean I don't need your help!
I like to keep an open mind and workflow on stuff (I collaborate musically like this) so anyone willing to help or learn something can hop right in and I would appreciate it!​
Some links I'm using for learning / porting:
Code:
It took a while, but I finally tracked down a mirror for the latest and last build of CM7 for the sensation:
[url]http://www.mediafire.com/?tc50rn6qvobj9us[/url]
I'm going to be using this kitchen:
[url]http://forum.xda-developers.com/showthread.php?t=633246[/url]
Found this guid for porting a rom. It's ment to be from CM7 to AOSP from the same phone, but it's worth a shot!
[url]http://forum.xda-developers.com/showthread.php?t=1512319[/url]
Along with some really specific files but for another phone, time to do some research :D
[url]http://androidforums.com/optimus-m-all-things-root/515246-guide-porting-lg-vortex-optimus-t-v-s-roms-m.html[/url]
EVEN MORE Porting guides with explanations for some of the files you're moving:
[url]http://androidforums.com/a70-all-things-root/444687-all-one-guide-porting-roms.html[/url]
Some build.prop info:
[url]http://www.blogtechnika.com/android-tweaking-demystified-part-i-build-prop-scripts-android-tweaking-demystified-part-i-build-prop-scripts[/url]
The latest ROM (Updated 3/19/2012) :
http://www.mediafire.com/?5128xikhv7xhdq3
Saved...
10char
Uno mas...
10char
hmmmm..... does it work with your amaze, since it isn't in the supported list i was holding back on using it
I appreciate you trying... But what makes you think the Amaze and Sensation are similar? From what I've read, Devs say they are COMPLETELY different phones.
Just thought I'd give you a heads up.
Best of luck to you though... I hope you get it working!
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
I appreciate you trying... But what makes you think the Amaze and Sensation are similar? From what I've read, Devs say they are COMPLETELY different phones.
Just thought I'd give you a heads up.
Best of luck to you though... I hope you get it working!
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
They are very different.... thus it has been a pain in the ass to port roms to it, but since you dont have to mess with changing the screen/resolution to match it, it makes it a little easier
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
I also just noticed your porting android 2.3.7..........................good luck doing that man may god be with you lol
Ok, yea, the internals are different. So far as I can tell the sensation has an S2 snapdragon and the Amaze has an S3. I don't know if I can even get this thing to boot, but I think it will be a great learning experience nevertheless!
Veras1996 said:
hmmmm..... does it work with your amaze, since it isn't in the supported list i was holding back on using it
Click to expand...
Click to collapse
You mean the rom? As of now im just going to try to move some drivers, libs, and kernel around and see what happens.
I got CM9 booting by just editing the build.prop from the sensation ported a ROM think it was CM9 but touch screen and features didn't work.
Diabolic Jr. said:
I got CM9 booting by just editing the build.prop from the sensation ported a ROM think it was CM9 but touch screen and features didn't work.
Click to expand...
Click to collapse
Woah! That's quite an accomplishment! You mind helping me with this port then?
And by editing the build prop, did you just pretty much copy the hardward identifiers from a stock ROM from the Amaze?
dubt17 said:
Woah! That's quite an accomplishment! You mind helping me with this port then?
And by editing the build prop, did you just pretty much copy the hardward identifiers from a stock ROM from the Amaze?
Click to expand...
Click to collapse
yea, i by editing the build prop you could boot almost any rom, but you take risk of bricking your phone
Veras1996 said:
yea, i by editing the build prop you could boot almost any rom, but you take risk of bricking your phone
Click to expand...
Click to collapse
Hmmmm, I'm wondering how bad this risk is? Like will editing the build prop, and keeping an existing kernel brick the phone? Because by my understanding I can ALWAYS boot into the bootloader, then recovery before it even touches the files that I'm injecting
Plus my phones S-ON, not that this means anything, because I have fastboot!
From what I've read, again, there have been 0 bricked s=on Amaze devices. There have been soft bricks, but ppl have always been able to fix in fastboot
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
From what I've read, again, there have been 0 bricked s=on Amaze devices. There have been soft bricks, but ppl have always been able to fix in fastboot
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Thanks, then back to the dev'n!
I've got a virtual box with ubuntu on it right now, but its hard drive isn't expanding past 8GB like it should be, so I have to figure this out first...
Trying to copy a stock ruu rom for some porting! Just not enough space
Alright, so I used dsixda's kitchen to port over the libs and some files. I then made an attempt to get the update-script to install and it seems as if it went through. Now I'm stuck on the white htc screen. I'm uploading as we speak, if anyone can help I would be grateful!
dubt17 said:
Alright, so I used dsixda's kitchen to port over the libs and some files. I then made an attempt to get the update-script to install and it seems as if it went through. Now I'm stuck on the white htc screen. I'm uploading as we speak, if anyone can help I would be grateful!
Click to expand...
Click to collapse
There's the soft brick my friend. Try to boot into recovery and restore. If you can't get into recovery, you will have to re-install a recovery using fastboot or adb. You can find the instructions on X's site in Amaze>Development> and find a recovery... It will be labeled "hard way" but its not really hard at all. It's easier than soft bricking your phone
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-2
And this is One of the reason the Amaze lacks development... It's a lil more difficult to dev on... Combine that with s=on and a phone only marketed in North America and you get a ghost town forum
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-2
glacierguy said:
There's the soft brick my friend. Try to boot into recovery and restore. If you can't get into recovery, you will have to re-install a recovery using fastboot or adb. You can find the instructions on X's site in Amaze>Development> and find a recovery... It will be labeled "hard way" but its not really hard at all. It's easier than soft bricking your phone
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
Thanks man! But not needed It's just installing to the system partition and one other, but both are active only after the bootloader, so I just hold down the "volume down" button while turning on, scroll to recovery and restore my backup. No trouble at all! In fact, since I'm basing this off the stock kernel, I don't think I need to install one until I can get it booting
Thanks for the help again dude, seriously, get that screen and help me with this
glacierguy said:
And this is One of the reason the Amaze lacks development... It's a lil more difficult to dev on... Combine that with s=on and a phone only marketed in North America and you get a ghost town forum
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
Really good point too hahahaha, didn't know this was a north american only phone. Dang it, means HTC will try to go through carriers for ICS... I hope they "leak" it before they send it off to T-Mob and such
dubt17 said:
Really good point too hahahaha, didn't know this was a north american only phone. Dang it, means HTC will try to go through carriers for ICS... I hope they "leak" it before they send it off to T-Mob and such
Click to expand...
Click to collapse
I'm pretty sure there is an XDA member, @Football I think his name is, that works for HTC that leaks the goodies for the devs.
We will be ok.
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-2
I just want to know Everything that is going to be done when ICS comes out........
New Kernal/ More Roms..........are any of you going to work on something let me now below!
Well pretty sure root is gonna be number one priority lol
freakboy13 said:
Well pretty sure root is gonna be number one priority lol
Click to expand...
Click to collapse
That should literally minutes for them to write a script that should work in recovery, IF the old one didn't work, which it might. You will still be able to unlock the bootloader, I think people forget that with a OEM unlockable bootloader, there is no cat and mouse game necessary.
Sent from my HTC_Amaze_4G using XDA
I'm going to be working on AOSP WiFi-Calling Mod & a ROM.
Pinky and Brain are coming out of retirement to try and take over the world.
Sent from my HTC_Amaze_4G using xda premium
Useless thread is useless. Everyone knows what's going to happen when ICS comes out.
http://www.xda-developers.com/android/pacman-rom-for-the-samsung-galaxy-nexus/
ive been seeing this on the xda homepage on and off for a while and it seems like a pretty bada$$ ROM, combinding settings from CM10, AOKP, and Paranoid.
I just wanted to throw this out there for any devs or potential devs that may be interested with impending releases of JB roms for our rezzys
If someone made this ROM it would be amazing... Hopefully someone will in the near future.
Sent from my Rezound fueled by jelly beans.
This would be an awesome Rom !,..hoping it can get ported.
Sent from my ADR6425LVW using Tapatalk 2
glad you guys took the time to check out the article, its really something, and who wouldnt love some arcade nostalgia?
agentofchaos said:
glad you guys took the time to check out the article, its really something, and who wouldnt love some arcade nostalgia?
Click to expand...
Click to collapse
Yea, this rom looks like it would be amazing and it would get rid of the need to decide between CM10 and AOKP.
Edit: I think i might try something with this. I found the github for the pacman rom. Note that i have little to no experience with building a rom so i probably will fail.
---------- Post added at 07:43 PM ---------- Previous post was at 07:21 PM ----------
If any devs see this and would like to give me pointers that would be much apperciated. :fingers-crossed:
Edit: Doing a repo sync right now.
jon7701 said:
Yea, this rom looks like it would be amazing and it would get rid of the need to decide between CM10 and AOKP.
Edit: I think i might try something with this. I found the github for the pacman rom. Note that i have little to no experience with building a rom so i probably will fail.
---------- Post added at 07:43 PM ---------- Previous post was at 07:21 PM ----------
If any devs see this and would like to give me pointers that would be much apperciated. :fingers-crossed:
Edit: Doing a repo sync right now.
Click to expand...
Click to collapse
Good luck Jon ! Hope it builds properly, probably have to change kernel ?
Sent from my ADR6425LVW using Tapatalk 2
I've been working on it on and off today. You have to bring in the device trees and kernel, and there's some recent commits in CM10 that were breaking things. I got a successful build earlier, but I haven't flashed it yet.
Sent from my ADR6425LVW using Tapatalk 2
mjh68 said:
Good luck Jon ! Hope it builds properly, probably have to change kernel ?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the support, and yea i was thinking i would have to change something with the kernal as well. I would probably use Funky Kernal if i figured it out.
shrike1978 said:
I've been working on it on and off today. You have to bring in the device trees and kernel, and there's some recent commits in CM10 that were breaking things. I got a successful build earlier, but I haven't flashed it yet.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Alright, i got it to build so far. Im wondering how you add commits into it though. Also do you think it would be safe to test being S-OFF?
shrike1978 said:
I've been working on it on and off today. You have to bring in the device trees and kernel, and there's some recent commits in CM10 that were breaking things. I got a successful build earlier, but I haven't flashed it yet.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Nice man I'm super excited for this to maybe come to life
Sent from my ADR6425LVW using xda app-developers app
OK it appears to be building right now. I'll probably leave it to build all night and hope for the best unless of course it stops.
Edit: It may fail because im getting low on space. If that happens though ill probably just extend my linux partition.
Edit2: It failed, tried to fix it, building again.
Sent from my Rezound fueled by jelly beans.
Ok it stopped building with the same result does anyone know about this? "make: *** [/home/jon/android/Pacman/out/target/common/obj/APPS/Bluetooth_intermediates/classes-full-debug.jar] Error 41"
Edit: I think it was just some files that went bad during the repo sync. Trying to brunch again.
Edit2: Still wont build
jon7701 said:
Ok it stopped building with the same result does anyone know about this? "make: *** [/home/jon/android/Pacman/out/target/common/obj/APPS/Bluetooth_intermediates/classes-full-debug.jar] Error 41"
Edit: I think it was just some files that went bad during the repo sync. Trying to brunch again.
Edit2: Still wont build
Click to expand...
Click to collapse
That build error is from a commit in the Bluetooth app package. I'm not booted into my build system at the moment, so I can't check for it.
shrike1978 said:
That build error is from a commit in the Bluetooth app package. I'm not booted into my build system at the moment, so I can't check for it.
Click to expand...
Click to collapse
Well when i looked at it i think it was BluetoothMnmSms.java or something like that. I also couldnt repo sync until i deleted that file and some other ones. If you want i can try to build again and give you a log of it.
There's going to be more involved than just pulling repos and brunching. We'll need to set up a pac_vigor build target for our phone because the cm_vigor target only builds the CM10 parts. I'm just playing it by ear at this point, but I'm not going to be able to mess with it any more today.
shrike1978 said:
There's going to be more involved than just pulling repos and brunching. We'll need to set up a pac_vigor build target for our phone because the cm_vigor target only builds the CM10 parts. I'm just playing it by ear at this point, but I'm not going to be able to mess with it any more today.
Click to expand...
Click to collapse
I knew there was gonna be more work then that. I might look more stuff up when I actually get back to my PC.
Sent from my Rezound fueled by jelly beans.
Noooo! I will not let this thread die! This is like a flashers wet dream.
Sent from my Rezound using xda app-developers app
Ohschit said:
Noooo! I will not let this thread die! This is like a flashers wet dream.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
I'm still gonna be working on this. Just haven't had a chance in a few days.
Sent from my ADR6425LVW using Tapatalk 2
Ohschit said:
Noooo! I will not let this thread die! This is like a flashers wet dream.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Lol. Ive been liking sense lately but if strike gets this to work ill probably switch back to AOSP.
@strike How would you go about making a build target for our device?
jon7701 said:
Lol. Ive been liking sense lately but if strike gets this to work ill probably switch back to AOSP.
@strike How would you go about making a build target for our device?
Click to expand...
Click to collapse
We have to mod some makefiles and make a device specific makefile and overlay. It should all be in the vendor tree..mostly in vendor/pac/ and vendor/pa/. I've made progress, but I still don't have it building.
For the record, the way I'm planning for this to work is if I get it working, I'll send it to my S-ON tester to make sure it works. Once that's established, I'll flash it myself to make sure it doesn't brick S-OFF. Then, I'll send out a few more PM's for testing and push my new vendor tree to github. When all is said and done, I'll get up with the PAC-Man team and see if we can get permission to release this thing publicly (once we also have permission from Chad to release his JB stuff as well).
If anyone else gets it working before me, I'd recommend a similar procedure...we don't need any bricks coming out of this if we can help it. There shouldn't be any since we're using Chad's JB device trees, but you can't be too safe.
Update: I think I have it. It's building now. I'll hopefully be able to get a test build out to my S-ON tester this evening.