Hi
I have successfully upgraded my Ideos X5 U8800 to 2.3.5 official Gingerbread, rooted it, and then repartitioned it using Blepart recovery. Subsequently I have checked out cm11 source, including Blefish repositories/code for the U8800 (thanks for good work, by the way!), compiled/built and installed a ROM. This was my first build.
OK. Good so far. Only I am looking to build cm10.1 because my goal is to eventually get this handset running Ubuntu Touch. Therefore, the next step is to get it running on cm10.1.
My problem is that I cannot find the source I need. I have tried to set up a fresh source tree and check out cm10.1 source combined with Blefish's source by specifying branch cm10.1 for the latter, using the files I used in .repo/local_manifests to get the cm11 device source etc. from Blefish. However, something seems to be missing as the lunch command fails and compilation aborts. Also, I can see that development has been discontinued on this branch for the U8800.
Any suggestions?
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Blefish said:
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Click to expand...
Click to collapse
Thanks for the quick response!
The Ubuntu Touch guide specifically states cm-10.1, but I will sign up with their forums and check whether I can use cm-11.
The following passage from the Ubuntu Touch Porting Guide gives the impression I might be able to base my work on cm-11? Would you agree?
"For quick reference, these are the current components used from Android:
Linux Kernel (stock Android kernel provided by the vendor, with a few changes to support some extra features needed by Ubuntu, such as Apparmor)
OpenGL ES2.0 HAL and drivers
Media (stagefright) HAL, to re-use the hardware video decoders
RILD for modem support
As Ubuntu is running as the main host on top of an Android kernel and the communication between the Android services and HAL happens via Binder, Sockets and libhybris. "
I am hoping this could work, as it would be a tremendous help, now that I have a running ROM built on 20 May with your source tree for the device specific code etc. which works like a charm! :good:
Best regards,
aribk
Related
Hey everyone.
I have downloaded CM9 source to build for our phone.
I have a problem: Since I have not built anything from source, I don't where to get the proprietary drivers for our phone.
I am guessing I would need dzo's ICS drivers, but I don't know where to get them from.
Can anyone tell me the URL of the driver for dzo's ICS and what command I need to enter in the terminal to download the drivers to the source.
Thanks a lot guys.
You can look at dzo's github. But it isn't enough for build CM9 so I'm building CM9 device and vendor tree for CM9.
You can look at my github.
hello all I'm thinking about building My own set of ROMs for the N7 And N4 based on the 4.2.2_r1 source code now how do I include such things as pie control reboot menu and other things like that and would Ubuntu 10.04 be a good version to compile on
Does anyone have a recent or mako specific guide on how to build Paranoid Android builds, I'd like to cherry pick a few smaller features into the already powerful ROM.
Would following the OmniRom guide and basically replacing the Omni values with the correct Paranoid Android values work out? Or is there other specific stuff I need to do?
I've got Ubuntu 13.04 & currently building OmniRom whenever I see there's a bit of a decent update but other then that I'm pretty much a noob .
http://forum.xda-developers.com/showthread.php?t=1863547
Basically just clone the PA source, add the mako specific stuff (kernel, device, and vendor from TheMuppets repo) and compile. If you have any other questions just ask in the thread a linked above.
Although I have used Android (phones & tablet) for about 4 years, I have only just started dipping my toes into the exciting world of rooting and mods. And so I have just wiped my Samsung Galaxy S3 and flashed the most recent Omnirom - a process which was so painless as to be almost pleasant!
It seems, however, that multiview/split screen is not available in this particular version of Omnirom (or if it is, it's so well hidden that I've not been able to find it!). So I'm wondering if it's possible to compile my own version of Omnirom from source, with just those parts of it I need. I used to compile linux kernels (before the days of loadable modules); can I do the same with Omnirom? That is, can I compile a version of Omnirom which might contain different fuctionailty that the nightly build?
Thanks!
It's pretty straightforward of you have a Linux box, and doable on Mac as well. There are great instructions on the OmniROM wiki. Plan on the source sync taking several hours (or overnight) the first time. Make sure you set up ccache so that subsequent builds go quickly.
http://docs.omnirom.org/Main_Page
Once you've built a straight-up version that works, you can branch and cherry-pick the multi-window patches from the OmniROM Gerrit instance.
---
Posted from whatever phone booted today
Hi all! First post to xda-developers, hoping for some assistance with an app that ran fine on stock, now not running on OmniROM. The application is Katawa Shoujo Ver5, the 334MB Monolithic release. I logcatted it down to an error that basically tells me that it cannot open _imaging.so and _sqlite3.so. I researched and found that these libraries belonged to a whole laundry list of 32bit libraries that my python 2.7 does not have. So, I have to figure out how to either add these libs manually or import them into python, how would I go about fixing the issue??
Device: SGH-T999L (T-Mobile)
ROM: OmniROM 4.4.4
Kernel: BMS (Not sure of exact, my phone is dead atm, sorry!) Will Update if needed when I get home
Linux Version: 3.4.y
austinyork1 said:
Hi all! First post to xda-developers, hoping for some assistance with an app that ran fine on stock, now not running on OmniROM. The application is Katawa Shoujo Ver5, the 334MB Monolithic release. I logcatted it down to an error that basically tells me that it cannot open _imaging.so and _sqlite3.so. I researched and found that these libraries belonged to a whole laundry list of 32bit libraries that my python 2.7 does not have. So, I have to figure out how to either add these libs manually or import them into python, how would I go about fixing the issue??
Device: SGH-T999L (T-Mobile)
ROM: OmniROM 4.4.4
Kernel: BMS (Not sure of exact, my phone is dead atm, sorry!) Will Update if needed when I get home
Linux Version: 3.4.y
Click to expand...
Click to collapse
Um, Omni does not include python to begin with, so... Issues you're having with third-party apps missing components (from an Omni perspective, python on a mobile device is a third-party app) aren't something relevant to Omni
Oh yeah, your device is also not officially supported. Even of the d2 family were, an alternate kernel means you have a modified configuration and we're not going to waste time on it. Argue that your issue is kernel-related all you want, it shows that you've modified the system so who knows what else you hacked.