Greeting Developers ,
I am new to this ROM building/porting process.
I want to install Vanilla Android on my note-4, so after questioning Google number of times, I came across official Android development guide on official Android website: https://source.android.com/source/downloading.html
I have downloaded the Android source locally and was following various Guides and tutorials from XDA-University & forums only for the development process. http://xda-university.com/as-a-devel...ng-source-code
I discovered that for downloading/configuring the build for a specific device(trltexx), we need to create a localmanifest file that contains device tree, vendor and kernel configuration links for repo syncing.
Now, I want your expertise to guide me forward from this point. Questions being:
1. Can I use CM or other projects (eg. AICP etc.) device configurations for this AOSP project.
2. Can I use these configurations for cross-version android build, say if I want to compile version 6.x, can 5.x configs can be used. (Manufacturer will take several months to release version update)
or Create new configurations using some guide/tutorial/book or something.
In XDA, I know I'm at the write place posting my questions and asking for expertised help.
Thanks!!
Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe
contramundi said:
Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe
Click to expand...
Click to collapse
Thanks for your reply @contramundi, I got N-910G which is a snapdragon version. I just want to know if I can use AOSP sources from google and device configurations from CM, AOSP rom can be built or I need to use specific device configurations for AOSP.
Why?
There's no need to start a whole thread for this as there are numerous threads to ask such a simple question. You didn't say which version of AOSP you were building, but regardless-- yes, you can try to start with CM device trees, but prepared to change quite a bit as there are quite a few dependencies on CM enhancements there.
If you want a truly "vanilla" experience, I"d use the Code Aurora sources, not AOSP's, as CA has all the latest Qualcomm support/bug fixes for MSM and APQ devices, which only may hit the AOSP tree when they do a new release. It is the repository where Samsung starts with their version of Android, and it's where CM also gets its qcom support/repositories.
Gekke, slahyer, and I have done the work to make the Note 4 build/work-- both for lollipop and now starting for 6.0 Marshmallow. And speaking of 6.0, before you even think of building that w/AOSP, you'd also need tons of patches for the Samsung kernel which I also have also already done.
Rather than just applying our work to vanilla AOSP though, you're welcome to join the community effort on CM 13, which has already been successfully built for tmo, eur/xx, spr, and edge so far) on the other thread. You'll need to read about the last two months of posts to catch up. I also posted a link to instructions on building CM-13 in my .sig below.
If you are insisting on straight AOSP by yourself, I would recommend you look at the shamu (Nexus 6) model. It is the same soc as the Note 4, albeit with different peripherals (screen, fingerprint reader, etc.). But it might be a place to start. My build instructions would need some slight tweaking for vanilla AOSP, but I'm sure you could figure it out.
ft
Compiling 8.1 oreo for note 4
Hi,I have been trying to compile aosp for note 4 snapdragon variant.I have downloaded the repo and the required files.I started the compilation and after 25% of the compilation is over,it shows some error and stops the process.Can anyone please help me.I have added the screenshots for reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hey,
I've read various topics on the forum, but they seem to confuse me as they say different things:
when ICS was released, some people said we needed a newer kernel for our nook in order to run ICS. but now, we have a pre-alpha build which runs on the old kernel. There are various other devices which have ICS builds on a 2.6.32.x kernel, so why did some people say that we needed a newer kernel?
Are Dal and fattire building ics ontop of a gingerbread kernel?
And which kernel is the "default" for ics? a 3.0 kernel?
i'd appreciate some answers to enlighten me
Take a look here, from the dev thread, kernel is 2.6.32.9.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Homer
Homer_S_xda said:
Take a look here, from the dev thread, kernel is 2.6.32.9.
Homer
Click to expand...
Click to collapse
Yeah, i know we are on that kernel, but my question is: how is this possible? Are they porting ICS to a froyo kernel?
The HD2 uses a froyo kernel too, for it's ICS builds.
But why were people saying when the ics source code was just released that we need a newer kernel before ICS could be ported to our nook?
I think you might be confused between NT and NC.
AFAIK, NT does need newer kernel (as set of drivers since it has new hardware) while NC doesn't require to. I might be wrong though.
It's my understanding that the NC (not sure about the NT) doesn't actually need the new kernel to run, but it would make things a hell of a lot easier. Mainly, the problem seems to be getting outdated hardware drivers working with the newer parts of ICS--thus the lack of sound and video, among others--and that 2.6.35 has code and/or links to drivers that would help. But until B&N updates to that kernel (unlikely for now)m anyone working on CM9 has to deal with the old code and thus has an uphill battle.
IIRC, at first the CM9 team said it might never come to the NC, so I feel like we're kinda lucky. And if you read the first post of the DEV thread, you'll see that they're still iffy (and that's being generous) on a final, working, daily-driver version ever being released.
A lot of misleading info here , I'll try to make it simple and understandable
First , NT has a locked bootloader - it doesn't have anything to do with ICS or kernel ver.
ICS doesn't NEED 3.0 kernel to run ( proven on many devices ) , BUT there are some compatibility issues that needs fixing/back-porting/revere-engineering
and there are some things that can't be exactly ported ( or it's pretty hard and not worthy to reverse engineer ) , such as closed-source drivers
The main issues most devices encounter are GPU & Camera
Since we don't have a cam , the GPU drivers are the main thing to worry about
As dalingrin explained some time ago , there are closed-source libs that we need updated from the manufacturer to support ICS - It seems some can be found compatible with newer kernel versions ( 2.6.35 ) , but again it doesn't promise full support till an official ICS version for a similar spec device comes out
As I see it , a 2.6.35/37/38 or even better 3.0 ( as some devices starting to concentrate on now to get full gpu support & camera working instead of back-porting closed source drivers ) eventually will be necessary , because all we do now is relying on legacy support / hacks
I'm hoping for a community port of 3.0 kernel once ICS port will reach its full potential using 2.6.32 kernel ( now that fat-tire has caused many people to learn how to build , maybe we will see more progress soon )
im currently running geewiz's latest nightly and i would love to come back to Roms like avatar or domination, aokp, paranoid android.
and i would love to see the voicemail notifications fixed on those or other new roms, and from what i saw on geewiz's OP developer he released a source that needs to be incorperated to the sources or our fascinate roms, and if possible ported to other phone roms if possible, we need to get word out about this because voicemail notifications are something thats a major issue in Android 4.2.2 roms for almost all phones.
Credit goes to the OP for sharing their github sources for it, but as mentioned cyanogenmod has not replied, nor has other major roms, but this is a 99% pure fix for the voicemail notifications as it works perfectly on their rom and was shared in this following XDA-post
http://forum.xda-developers.com/showpost.php?p=45928409&postcount=491
@jkok
Seems to be a workable solution in an app at the play store
https://play.google.com/store/apps/details?id=com.steepcanyon.VMMonitor
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not a lot of testing a far as battery life, quickness, etc yet.
But it does seem to retrieve and work on our fassy
.
hhp_211 said:
@jkok
Seems to be a workable solution in an app at the play store
https://play.google.com/store/apps/details?id=com.steepcanyon.VMMonitor
View attachment 2306487
Not a lot of testing a far as battery life, quickness, etc yet.
But it does seem to retrieve and work on our fassy
.
Click to expand...
Click to collapse
oh ok! that seems to look great! if it works then the phone's roms are getting the broadcast, just not the native notification? that seems alright then but the main reason why i made this thread is so it can be added to the roms for native notifications, but i like the idea for this app too dw =),
jkok said:
im currently running geewiz's latest nightly and i would love to come back to Roms like avatar or domination, aokp, paranoid android.
and i would love to see the voicemail notifications fixed on those or other new roms, and from what i saw on geewiz's OP developer he released a source that needs to be incorperated to the sources or our fascinate roms, and if possible ported to other phone roms if possible, we need to get word out about this because voicemail notifications are something thats a major issue in Android 4.2.2 roms for almost all phones.
Credit goes to the OP for sharing their github sources for it, but as mentioned cyanogenmod has not replied, nor has other major roms, but this is a 99% pure fix for the voicemail notifications as it works perfectly on their rom and was shared in this following XDA-post
http://forum.xda-developers.com/showpost.php?p=45928409&postcount=491
Click to expand...
Click to collapse
I'm running AOKP 4.2.2 on my Incredible 2 -- would this fix work for it, do you think? I'm not sure what to do with these files in github...?
sjwoo said:
I'm running AOKP 4.2.2 on my Incredible 2 -- would this fix work for it, do you think? I'm not sure what to do with these files in github...?
Click to expand...
Click to collapse
unfortunantly these are if you are building the rom from source =( the files itsself without the source compiling to make the rom are useless, you would need the person who is compiling the rom to incorperate them into the source, but this is also only tested on Samsung Fascinate (fascinatemtd) using SamsungExtoyos3 RIL (may have mis-spelled the RIL name, but its simmalier at minumum), the RuimRecords,java file is still in the same place, so it will be fine, but this hack method is used to Spoof the CDMA phone as a GSM Phone (as fascinatemtd is a CDMA-ONLY device, it will read as a GSM tho, but all should stay fine) but please be cautious of adding the lines marked in GREEN and removing lines marked in RED if you do this manually, as it was only tested on this device as far as i know, and not the incredible 2, i can confirm its working in 4.4.2 as i have it working on my personal Dirty Unicorns (du44) builds for fascinatemtd, but please dont try this on the incredible 2 without proper testing but remember without compiling the rom from source, this method is useless to the average user to apply, hence the make-shift title tag"fix4rommakers" as its for rom-makers (people who compile from source)
jkok said:
unfortunantly these are if you are building the rom from source =( the files itsself without the source compiling to make the rom are useless, you would need the person who is compiling the rom to incorperate them into the source, but this is also only tested on Samsung Fascinate (fascinatemtd) using SamsungExtoyos3 RIL (may have mis-spelled the RIL name, but its simmalier at minumum), the RuimRecords,java file is still in the same place, so it will be fine, but this hack method is used to Spoof the CDMA phone as a GSM Phone (as fascinatemtd is a CDMA-ONLY device, it will read as a GSM tho, but all should stay fine) but please be cautious of adding the lines marked in GREEN and removing lines marked in RED if you do this manually, as it was only tested on this device as far as i know, and not the incredible 2, i can confirm its working in 4.4.2 as i have it working on my personal Dirty Unicorns (du44) builds for fascinatemtd, but please dont try this on the incredible 2 without proper testing but remember without compiling the rom from source, this method is useless to the average user to apply, hence the make-shift title tag"fix4rommakers" as its for rom-makers (people who compile from source)
Click to expand...
Click to collapse
Got it - thanks. I'm just having a devil of a time getting voicemail to work. The closest I've gotten is running AOKP 4.2.2, and it only works after a reboot. So I'm just rebooting the phone on a schedule every morning. Better than nothing!
PLEASE REFER TO THE CHANGE LOGS FOR CURRENT FEATURES.
IF IT'S NOT LISTED THERE, IT'S NOT IN THE BUILD
DUAL SIM (XT1033) IS NOT SUPPORTED. CONVERT TO GPE FIRST IN ORDER TO FLASH THIS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INSTRUCTIONS,
1. UPDATE RECOVERY
2. FACTORY RESET (If coming from another rom or stock)
3. INSTALL ROM - MIRROR
3.1 UNOFFICIAL BUILD - With all the changes CM is pushing you might get bugs and want a faster update to see if they got fixed. Clean flash this and do NOT use custom kernels. For a partial list of changes check here or, even better, sources are here
4. INSTALL GAPPS
4. REBOOT
5. CUSTOM KERNELS MAY BREAK ROOT, SIMPLY RE-FLASH SUPERSU
PA 4+ UPDATES DO NOT NEED A FACTORY RESET.
CREDITS,
AOSP/Google, Cyanogenmod, Goo, XDA, Krebsmilk, giannisgx89, Liquid,
AOKP, our users, supporters and donators, everyone who's helped us in the past,
heartfelt thanks to all of you!
Links:
Development:
Change Logs
XDA Forum
Github
Gerrit
Social:
Google+
Twitter
Facebook
Video review
Some screenshots
XDA:DevDB Information
AOSPA Legacy 4+, ROM for the Xiaomi Mi 2
Contributors
m11kkaa
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Created 2014-09-28
Last Updated 2014-09-28
is this based on PA 4.5 stable branch or on 4.6 beta?
anyhow GREAT job man! :good:
Launcher3 is force closing on me .
EDIT: No logs, going to bed that's why
Is there dual sin version of Mi2? First time I heard that.
Of course thanks a lot M1cha.....
why in general?
:cyclops: Oh, here is my favorite rom AOSPA, almost missed it.
But... the OP is quiet confusing, and why in general?
:laugh: Back in Android 4.3 time ParanoidAndroid is THE favorite rom of mine, I just can' froget that shining PIE control after the first sight.
But currently I'm lack on storage space on data partition (this is one serious problem for aries...) so trying out this new rom might not be a very good idea for me... I'll definitely check on this thread~ Anyone who tried this rom, please do share your experience!
:good: Thank you M1cha, for bringing this great rom to aries, as always - you're the best!
Am having issues with 4.6 BETA4 on MI2S. The video recording doesn't records audio. Please advise.
PS: I tried 4.6 BETA3 and it has the same problem.
EDIT: Could someone direct me which files to replace for the camera/video recording libraries? So I could copy from CM11?
EDIT2: Whatsapp voice note also doesn't seems to work.
I would like to change the min frecuency when the screen is on,with but change in a while and then set on 1024 MHz again.
Can you tell mehow can I do it?
Thanks for this great ROM
paul89rulez said:
why in general?
Click to expand...
Click to collapse
Didn't understand this comment
Why in general section and not in android development as it was in
I have a bug, I can't hear phone calls. Someone has this bug also?
I have true dual boot enabled with cyanogenmod 11 on system 1 and when using CyanogenMod everything works.
fpolle said:
I have a bug, I can't hear phone calls. Someone has this bug also?
I have true dual boot enabled with cyanogenmod 11 on system 1 and when using CyanogenMod everything works.
Click to expand...
Click to collapse
Not here.
What I'm seeing Its the phone don't go to sleep. I just get 2 hour of deep sleep in all day. It's normal?
I am the user for lgl22-"the branch of lgg2".
Our phone has a problem that everyway the compile rom(eg:VANIR AOSP,CM10,CM11,CM12,CM12.1) can not find the sim card.
And many developers try to compile it,but failed.
The latest developer is VANIR(https://sudosurootdev.com/),they start at April 2015.And we also donate him a device of
lgl22.In addition to,we donated about $70 in total for his development.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But the rom still can't find the sim card.
And the group seems to stop developing the lgl22,because up to now,the developer don't reply me by Hangouts or post on the
website(Because nobody can compile rom with sim card ok,so we request him just transplant vanir for 4.4 at june and he not
rely).I am not doubt sudosurootdev's ability,but we-----the user for lgl22 need use a good rom like aosp quickly.
So I want to find one or more developer's help,We still have about $60 left(JUST the first donation).
IF you transplant AOSP OR CM11 for lgl22 and it can find the sim card,It's all yours.
IF you compile the AOSP or CM or more and it can find the sim card,We will donate $100 and support you for a long time.
This the opensource code website(http://opensource.lge.com/osSch/list?types=ALL&search=lgl22)just lgl22 not lgl22c.
If you want to some help please reply me.
Let me introduce the history of the rom's development.Japanese developers started working until July 2014,but not
solved.http://site.kbc-brick.org/lge/lgl22-isai
Vietnamese developers:http://tekcafe.vn/threads/rom-cm12-android-lollipop-5-0-cho-lg-g2-isai-l22.81/
the latest developers of American:https://sudosurootdev.com/
BUT THEY DON'T SOLVE THE PROBLEM--------can't read the sim card
We even think only the LG or KDDI have way to solve it because the phone is made by them.
@xdabbeb
@genesixxbf3
@Cloudyfa
@varund7726
@dorimanx
@RenderBroken
@Rashed97
@blastagator
@OptimusRs
@P_Toti
@ahmed534
@timpohladthomas
@nobe1976
@aidasaidas75
@westcrip
@semdoc
@pjgraber03
@firebird11
@777jon
and many developers
wszgrcy said:
I am the user for lgl22-"the branch of lgg2".
Our phone has a problem that everyway the compile rom(eg:VANIR AOSP,CM10,CM11,CM12,CM12.1) can not find the sim card.
And many developers try to compile it,but failed.
The latest developer is VANIR(https://sudosurootdev.com/),they start at April 2015.And we also donate him a device of
lgl22.In addition to,we donated about $70 in total for his development.
But the rom still can't find the sim card.
And the group seems to stop developing the lgl22,because up to now,the developer don't reply me by Hangouts or post on the
website(Because nobody can compile rom with sim card ok,so we request him just transplant vanir for 4.4 at june and he not
rely).I am not doubt sudosurootdev's ability,but we-----the user for lgl22 need use a good rom like aosp quickly.
So I want to find one or more developer's help,We still have about $60 left(JUST the first donation).
IF you transplant AOSP OR CM11 for lgl22 and it can find the sim card,It's all yours.
IF you compile the AOSP or CM or more and it can find the sim card,We will donate $100 and support you for a long time.
This the opensource code website(http://opensource.lge.com/osSch/list?types=ALL&search=lgl22)just lgl22 not lgl22c.
If you want to some help please reply me.
Let me introduce the history of the rom's development.Japanese developers started working until July 2014,but not
solved.http://site.kbc-brick.org/lge/lgl22-isai
Vietnamese developers:http://tekcafe.vn/threads/rom-cm12-android-lollipop-5-0-cho-lg-g2-isai-l22.81/
the latest developers of American:https://sudosurootdev.com/
BUT THEY DON'T SOLVE THE PROBLEM--------can't read the sim card
We even think only the LG or KDDI have way to solve it because the phone is made by them.
@xdabbeb
@genesixxbf3
@Cloudyfa
@varund7726
@dorimanx
@RenderBroken
@Rashed97
@blastagator
@OptimusRs
@P_Toti
@ahmed534
@timpohladthomas
@nobe1976
@aidasaidas75
@westcrip
@semdoc
@pjgraber03
@firebird11
@777jon
and many developers
Click to expand...
Click to collapse
The reason they are having issues and it never works is because the files that control that for that version are not open source. This is alsao the reason you dont see many roms that fully work for alot of devices based in Asia.
This may not be an option for your device.
Thanks man. I will donate some too, if someone takes on the chalenge.
Sent from my LGL22 using Tapatalk
zelendel said:
The reason they are having issues and it never works is because the files that control that for that version are not open source. This is alsao the reason you dont see many roms that fully work for alot of devices based in Asia.
This may not be an option for your device.
Click to expand...
Click to collapse
+1
this is not releated to lack of good developers or anything like that ! but as Zelendel said, it is not fully open source, and without sources nothing to do :/
sry for that
I'm pretty sure that I'll get little help on it, but I'll give it a try.
So, I want to use 4.4 KitKat on my HD2, but the only ROM available for now is NexusHD2-4.4 by tytung and others. It's based on 2.6 kernel, has built-in GAPPS and some missing settings, like the setting to turn on screenshot button in power menu. There actually was a ROM based on more clean codebase and 3.0 kernel, but all the links are dead.
The point is - I want to build my own CM11, or LineageOS 11 if I'll use the latest cm-11.0 branch from LineageOS team, without any built-in Google apps and with a 3.0 kernel. But as far as I know, literally no one made even a short guide on how to build a ROM for HD2 - the only guides I've found are about installing the already built ROM. It's a shame that nobody made these kind of guides, although the device had very big community back in the golden days.
Honestly - I'm no expert in building Android ROMs. My last attempt was building LineageOS 14.1 for Samsung Galaxy Core Prime VE SM-G361H/DS that eventually was unsuccessful - and I don't even remember why it was so. But I see that in case of HD2 the ROM should be adapted to it, because literally all Android NAND ROMs on the device have AROMA installer that provides choice between RMNET for MAGLDR and PPP for both MAGLDR and cLK and other minor things. So I'm concerned that I will need to make some modifications to ROM code to make it work like already built CM11. I can be wrong, but forgive me please, because I haven't used this device for a while, and also haven't built any ROMs for any of my devices in a while.
Also I have very little info about the device tree of HD2, especially for 4.4, but I guess that's because of my zero experience. If you can help me, you can point me to the tree, kernel and other things that are crucial when building the ROM.
So, the question is - are there any recommendations that I may follow while configuring the build? What Linux distribution should I use to build the ROM (Google recommends Ubuntu 12.04 LTS, but I can try to do it either on Ubuntu 22.04 LTS or on Arch Linux)? And what are the other obstacles that may occur while building the ROM for such an old and very, very unsupported device that I may need to overcome?
(By the way, sorry for my English, it's not my native lang, but I think you've got the point)
So, I have succesfully compiled clean LineageOS 11 for HD2 using Arch Linux and Ubuntu 12.04 in Docker container, but I think the ROM should be adapted to use on that strange device, for example NativeSD install ability is not implemented yet.
My talents lie elsewhere, but I'd be really happy to find a basic ROM that enables me to log into Google to access Google Play and download apps from there.
Can't be too advanced as the HT2 just won't cope, but it seems with the ROMS available at the moment either you can either log into Google or access wifi/data, you cannot do both.
grayme said:
a basic ROM that enables me to log into Google to access Google Play and download apps from there.
Click to expand...
Click to collapse
For me the main goal is kinda different - I want a KitKat rom that has 3.0 kernel, compiled from the latest CM11 sources available (from LineageOS team) and without any GAPPS, because I see that they really slow down the system even on Jelly Bean ROMs. I don't give any promises anyway, but I can try to insert GAPPS somehow and adapt them to be installable on HD2.
By the way, here's the link to absolutely raw and unfinished ROM, without any adaptations to HD2, just right after the compilation process: MEGA
It still needs a lot to do, because as I see now, it's built for NAND-only installation, uses ppp and not adapted to use with MAGLDR and NativeSD in any way:
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wonder — why are there three different initrds for all three installation types. I'll experiment later with it, maybe I'll be really lucky and be really able to start this ROM on the device
So, I've analyzed some things, added some lines to initrd and rewrote updater-script - no luck at all. I wish I could make it bootable by any means
SuperHipster said:
I wonder — why are there three different initrds for all three installation types. I'll experiment later with it, maybe I'll be really lucky and be really able to start this ROM on the device
Click to expand...
Click to collapse
Because the fstab is in initrd and i already made data on ext ramdisk i will try to get this to boot this evening.
Any logs or sources?
J0SH1X said:
Because the fstab is in initrd and i already made data on ext ramdisk i will try to get this to boot this evening.
Any logs or sources?
Click to expand...
Click to collapse
I remember that I built it using this kernel and this tree. Unfortunately I have no logs whatsoever, because I was forced to wipe the HDD where all the sources and modifications (there were a little of them) were. And also I've got not so much time right now, I guess I'll be back when I have less problems in my personal life.