Database Users

[kernel] [odin3] Overclock to 1.2 GHz!

OK guys, thanks to AJerman and many others who have posted in this thread, we have had success in compiling, loading and running a bug free kernel. The wakeup lag is there, but is highly reduced. Also, if someone could figure out how to compile a boot.img so that we can simply flash the kernel through recovery (I have no idea how), we would really be grateful, for all of us with either Linux or Mac. Anyway, here is the link, flash it through Odin3. http://www.multiupload.com/8UM79T8VNE . Bug reports are welcome, as are logcats. Please download SetCPU from the market, or for free from an xda thread (I forgot where it is, I think it's in the G1 section). Set to OnDemand to reduce wakeup, set lowest possible value for min, and highest for max (1.2 GHz). Of course, you can also use profiles if you are an advanced SetCPU user. Thanks for reading, here we go!
We now have a successfully compiled kernel for the Captivate that overclocks the phone to 1.2 GHz. The link is coming soon. Also, many are complaining about garbled audio on custom kernels, even compiling directly from source. Either way, that is now fixed:
GOT IT! Sounds perfect again! Just download the Vibrant source and copy the ENTIRE sound/soc/codecs folder over to the Captivate source. Like I said before, they are almost identical for the most part, so I looked and saw the A1026 files were in the Vibrant source, among other missing files, turned on A1026 in the .config and copied the codecs folder and it sounds good as new again! I'm already late to go meet some friends messing with this, so try it out NukaCola and see if it works for you. I'll test the rest of the audio as I go, but this is good so far. When I get back I'm going to ext4 enable my kernel, OC'd to 1.2 GHz and see if I can hit a 2K quadrant score, haha.
Click to expand...
Click to collapse
The Hummingbird processor inside all Galaxy S models can theoretically be overclocked to 1.6 GHz [stable], and potentially past, if a genius can do that. Please, devs, post a link compiled kernel so that I can put it in the OP and people can start hacking their phones, I'll give full credit to the dev.
The i9000 folks have successfully created a 1.2 GHz standard voltage overclock. Is anyone over here interested in helping to port it over to the Captivate? I have no experience in kernels, but I'd love to learn and do my best to help out. Here is the link: http://forum.xda-developers.com/showthread.php?t=743782 . Also, the few of us with Linux or OS X would love to see an option for flashing from recovery. Just let me know if anyone is interested, and thanks in advance.
Click to expand...
Click to collapse

AHHH, between froyo, the lag fix, and this, I'm tempted to return the captivate and buy a Galaxy S>...... Too bad they're $700.....

I will look at it and see what I can do. I will attempt to port it and make it a flashable zip. I cant guarantee anything

hansmrtn said:
I will look at it and see what I can do. I will attempt to port it and make it a flashable zip. I cant guarantee anything
Click to expand...
Click to collapse
You Sir would be my new hero.....

I'm going to look at it over the weekend as well since I've got the source for the kernel at home. I've got a friend that I can possibly get to be my tester as I only have an n1. We'll find a way guys.

bedwa said:
I'm going to look at it over the weekend as well since I've got the source for the kernel at home. I've got a friend that I can possibly get to be my tester as I only have an n1. We'll find a way guys.
Click to expand...
Click to collapse
Sounds like a plan my friend

I'd really like to get involved in the Dev side of things. Problem is I know 0 about Linux. Anyone recommend a good tutorial? I got time and patience.

Dont port - use your source and follow directions in the main post

Don't port? I guess building from source would work too, but I don't see what's wrong with porting, but I know nothing about kernels, so I'm in the dark.
Sent from my SAMSUNG-SGH-I897 using XDA App

porting M110S/i9000 kernel to Vibrant will be very a difficult process.
It would be MUCH easier just to start from Vibrant source and apply changes there.

ok, I have made the changes to the kernel source, just need to figure out how to compile it now

designgears said:
ok, I have made the changes to the kernel source, just need to figure out how to compile it now
Click to expand...
Click to collapse
That is awesome to hear. It sucks to see the Vibrant development moving along much quicker than ours! So much so that I tried to flash an update.zip from the Vibrant threads and I can safely say that it doesn't work.

here is steps i used on M110S (Korean Galaxy S)
1. install codesourcery toolchain (GNU/Linux version i think 202)
2. install initramfs directory and source list for your phone
2. goto linux-2.xxxx directory of source
4. make menuconfig - find and point to your initramfs source list
3. make -j8 HOSTCFLAGS="-g -O2" ARCH=arm CROSS_COMPILE="PATHTOTOOLCHAIN/arm-none-linux-gnueabi-"
4. Kernel: arch/arm/boot/zImage is ready -- if you see this you succeeded, file size should be 6-7MB
5. tar -cvf mykernel.tar arch/arm/boot/zImage
6. Flash using odin

this would kick some ace

Be aware that the reason for the lack of Captivate kernel development is because the kernel source currently does not work correctly.
The kernel source causes microphone distortion rendering calls worthless. My guess is that the problem is the A1026 voice processor driver can't be compiled as of now.
Check out NukaCola's speed fix thread for more info.

I am subscribing to this one...cannot wait to OC

Be aware that we have yet to be able to compile a kernel that didn't have sound distortion issues. I don't know what changes were made for this mod, but not even a stock kernel is working right after we compile it yet. Look in the speed fix topic for more info.

Okay, this is very preliminary, I'm not ready to give this to anyone for fear of blowing up people's phones and being blamed. I'm going to review my code changes a little more and test a little more, but this is on stock voltage:
{
"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"
}
Also, I got a 1540 Quadrant score running at 1.2 GHz along with the data folder on an ext3 partition on SD if anyone is curious. I was getting 1400s or so. I'd say it jumped around 50-100 points in Quadrant. Nothing huge as I expected, but not bad.

AJerman said:
Also, I got a 1540 Quadrant score running at 1.2 GHz along with the data folder on an ext3 partition on SD if anyone is curious. I was getting 1400s or so. I'd say it jumped around 50-100 points in Quadrant. Nothing huge as I expected, but not bad.
Click to expand...
Click to collapse
Sounds good. How is your voice quality?
You cood check it using loopback test:
*#*#197328640#*#*
Common-factory test-audio loopback- and both pcm and packet for the handset plz.

XorZone said:
Sounds good. How is your voice quality?
You cood check it using loopback test:
*#*#197328640#*#*
Common-factory test-audio loopback- and both pcm and packet for the handset plz.
Click to expand...
Click to collapse
Same as every other kernel I've compiled to date:
http://www.zshare.net/audio/790823995f7a3425/
That's really bothering me. I mean, people can probably understand you, but you have to speak loud and clear for them to even be able to barely hear you. We need to get that figured out ASAP or all our kernel mods are a little less useful.

[UPDATE][BUILD][11.4.2010][Erick's Evo build for hd2 v0.2][Kernel: 2.6.32.15 #5]

{
"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"
}
Ok so my hd2 got stolen and i need to buy a new one to make more builds.....so i im going to start updating this build once i get my new hd2(this might take along time becouse i need to earn the money)sorry ...... SO FAR ITS REALLY STABLE AND FAST!!! SO PLEASE DOWNLOAD AND TRY IT THANKS!!!!!!!!!!!!!!
Installation Instructions:
1. Unzip the contents to your SD card. All of the files should extract into a folder named "Android".
2. Browse to the Android folder on your SD card and run CLRCAD.exe, then Haret.exe.
3. Let Android boot. The first boot will take longer.
4. YOUR READY!!!!!!!!! ENJOY HTC EVO ;D
Known issues:
Some apps dont work most of them do
There are menu items for 4G. The hardware doesn't support 4G!!!!!!
Battery tips
Use SetCPU for better battery life.
Turn off live wallpaper for better performance and battery life.
(This build does not drain your battery life)
ChangeLog:
v0.2
3g works now!!! REALLY FAST
changed the starting image
Wifi thetering works
Freezing problems fixed
Got faster!!!
v0.1.5
No more premature camera
Better screen quality!!!!
v0.1
first build
Tested on HTC HD2
The latest kernels and modules can always be found here: http://oe.netripper.com/files/htcleo...uild_evo_tree/
Also check out my blog (its about the hd2) http://leo-htc.blogspot.com/
Oh and check out my facebook page "LIKE" it please!!!!http://www.facebook.com/?ref=home#!/pages/Ericks-HTC-HD2/155309767838377
Download here:
If you like my work and want to buy me a coke click on the can

To improve your thread, look at some of the other builds and see what they have. There is also a sticky that tells you what you should have in your post.
http://forum.xda-developers.com/showthread.php?t=734563
------------------------------------------
If you are making a Rom with Android built in or an Android Build that is run from haret then please INCLUDE with your file a readme.txt file in the ROOT of your release archive with the following information:
*What BUILD version?
An internal version # that can be used to identify the authors exact release (e.g. my-rom-v0.5.zip) for easier reference for the users and fellow developers benefiting from the release.
*Which kernel image and kernel modules are used?
Where are zImage and modules.ko originally downloaded (in case the chef didn't compile on their own) and where is the kernel source code for the kernel and modules.
In case the chef did not compile on his own, he should still be able find out where the source code is.
(The license under which the Linux kernel is released requires the distribution of the source code that was used when distributing builds.)
*What rootfilesystems are used?
Where was it taken from, what does it include (android version it's based on etc) and in case of self compilation, where is the source code.
(In case of most windows mobile shipped devices that's often some rootfs file e.g. named android.ext2 and an initial ram filesystem often named initrd.cpio.gz).
*ChangeLog*
A ChangeLog is really an essential addition in every build as it informs the end user what modifications have been made from the last build. This will save you ALOT of questions as to what has been added, deleted or modified and therefore is a requirement for everyones benefit.
*WindowsMobile version your Android Build was tested on*
Please include your WinMo Build version, HTC OemDrivers (if known), XIP (if known) and Radio version so that users know what the Android Build was tested on and can replicate if neccessary for fault finding purposes.
------------------------------------------
------------------------------------------
If you are unable to obtain any of this information and thus can't make it available through an included readme.txt you should not distribute your rom and keep it for personal use only.
If you are using an exact copy of a present release (e.g. in case of a WinCE rom that has an android 'dual boot' option) you must include the readme.txt from the original rom chef.
If you release a Rom and do not have the required information then you will be asked to either create and include a readme.txt file with your Rom or ask for the thread to be deleted.
Click to expand...
Click to collapse

i want try this, but you should be share some informations, some screenshots this build. And you must say what is this? Froyo, nexus or others?

It just Woo, nothing to say, cooool

In your testing, what works and what doesn't?

Well so far everything works fine exept wifi thetering and some apps from the market dont work either but im working on that

alright i'll give it a try! just make sure you update info about the build!

Make sure you update your post with the information mentioned in my post above, otherwise a moderator will delete this thread.

What about the battery life?

What kernel is it built with?

ok thanks!!! I WILL!!

If u use harstin 7.5 kernel the premature flash will go away
Sent from my hd2 aka tmobile evo eatin on some froyo

jriv said:
If u use harstin 7.5 kernel the premature flash will go away
Sent from my hd2 aka tmobile evo eatin on some froyo
Click to expand...
Click to collapse
Not just that, it will fix laggy screen responsiveness and the light sensor is far better.

jriv said:
If u use harstin 7.5 kernel the premature flash will go away
Sent from my hd2 aka tmobile evo eatin on some froyo
Click to expand...
Click to collapse
Were can i find the harstin 7.5 kernel!!!!

erick1026 said:
Were can i find the harstin 7.5 kernel!!!!
Click to expand...
Click to collapse
dude, i will assume you have been too busy building roms vs reading about them. here is a link, but it is in the same thread your build is in. good luck and try and avoid the noob questions if you are looking to make a name. hope all works out for ya.
http://forum.xda-developers.com/showthread.php?t=787588

erick,
Can you point me to any information that would help me start to make my own rom? I can't seem to find the info anywhere!

RobertsDF said:
erick,
Can you point me to any information that would help me start to make my own rom? I can't seem to find the info anywhere!
Click to expand...
Click to collapse
All you need is a kitchen to get started.

mattfmartin said:
All you need is a kitchen to get started.
Click to expand...
Click to collapse
Do you know which kitchen I should use?

RobertsDF said:
Do you know which kitchen I should use?
Click to expand...
Click to collapse
The only one that I know of is Coffee shop. I don't know if those things get outdated or not. Its been around for a while.

mattfmartin said:
The only one that I know of is Coffee shop. I don't know if those things get outdated or not. Its been around for a while.
Click to expand...
Click to collapse
Cmyeah, coffee shop is the only one that I have found. Seems outdated but ill give it a try.
Sent from my HTC HD2 using Tapatalk

[ROMs] 4.2.2 ROM's

I have two ROM's I thought I would share. They are both 4.2.2 ROMs; one is AOKP, and the other CyanogenMod. Niether have working Bluetooth and do have most of the current 4.2.2 bugs.
If anyone is curious they can see my Github, my username is CDMoncrieff
I've uploaded the files to Dev-Host under CDMoncrieff and the files are:
cm_tenderloin.april8.zip - 152.30 MB
aokp_tenderloin.april8.zip - 133.95 MB -been told it may wipe SD contents on some Touchpads. Back-up to your PC before flashing please!
Use a file explorer to drop this file in system/bin to fix the multiple light touches bug. ts_srv - 17.84 KB
{
"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"
}

CDMoncrieff said:
I have two ROM's I thought I would share. They are both 4.2.2 ROMs; one is AOKP, and the other CyanogenMod. Niether have working Bluetooth and do have most of the current 4.2.2 bugs.
If anyone is curious they can see my Github, my username is CDMoncrieff
I am not able to post links yet (<10 posts), but I've uploaded the files to Dev-Host under CDMoncrieff and the files are:
cm_tenderloin.april8.zip
aokp_tenderloin.april8.zip
Click to expand...
Click to collapse
Thanks for the Roms. Question, which gapps should we use? Thanks again.

chicle_11 said:
Thanks for the Roms. Question, which gapps should we use? Thanks again.
Click to expand...
Click to collapse
The 4.2.2 GAPPs package

A question for you, where did you learn to build ROMs for the HP touchpad? I've been googleing how to set up a build environment on Ubuntu, which I've nearly completed but then all guides on building cm10.1 (for example) only cover supported devices of which the Touchpad isn't.... I can't find much with Google at least on Touchpad specific ROM building.
Sent from my Nexus 4 using Tapatalk 2

Nathanation064689 said:
A question for you, where did you learn to build ROMs for the HP touchpad? I've been googleing how to set up a build environment on Ubuntu, which I've nearly completed but then all guides on building cm10.1 (for example) only cover supported devices of which the Touchpad isn't.... I can't find much with Google at least on Touchpad specific ROM building.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2043285
This is hands down the best guide for setting up your build environment. Its okay to be on 13.04 as well, you might just have some unmet dependantcies you need to install. You'll likely be told you are holding broken packages and will need to meet the dependencies before you can install the other packages.
sudo apt-get install gcc
sudo apt-get install g++
After following that guide you should be set up to build.
Building for unsupported devices depends on the ROM you are trying to create. Basically you just need to follow the file paths in your local repository until you find something out of place or missing, then fix it.
You can see my githib at github.com/cdmoncrieff where you can see some of the commits I made to build for AOKP to get an idea of the process. There is also a short build-instructions repo with a few details of the process for 4.2.2. If you have any questions, which if you are going to try building, I will be glad to help

I still need more posts before links, here's another!

OK that's great I will take a look, the main problem for me at the moment is time. I'm currently using Ubuntu 12.10 I'm hoping to at least compile cm9 or cm10 to start with as they are pretty much fully operational. SGA's efforts with 4.2 and yours have inspired me to have ago. I guess the battery life is the main item that needs work in 4.2.2 and working out how to get Bluetooth working. What are your plans? Do you intend to try to improve on the current builds?
Sent from my Nexus 4 using Tapatalk 2

Where I can :good:

These are the links?
http://d-h.st/search?search_by=2&search_for=cdmoncrief
Sent from my GT-N7000 using xda app-developers app

keenan316 said:
These are the links?
http://d-h.st/search?search_by=2&search_for=cdmoncrief
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes, thanks!

This should be moved to development thread. You mind if I request that it is? By the way thank you for sharing!

nickster1 said:
This should be moved to development thread. You mind if I request that it is? By the way thank you for sharing!
Click to expand...
Click to collapse
Yes, but still no takers on the DL?

I will tonight when I get a chance.

CDMoncrieff said:
Yes, but still no takers on the DL?
Click to expand...
Click to collapse
That sounds good.

Wich bugs 4.2.2 has?

Unpredictable power draw
No Bluetooth
Kind of flakey WiFi
Rotated camera preview
I think that's it...

CDMoncrieff said:
Yes, but still no takers on the DL?
Click to expand...
Click to collapse
I downloaded the AOSP version earlier and will be flashing tomorrow.
Do I have to wipe / factory reset, format system, etc, or can I get away with just wiping cache and wiping dalvik cache.
Thanks.

Thread moved to development, now that the OP has permissions to post in dev forums

CDMoncrieff said:
Yes, but still no takers on the DL?
Click to expand...
Click to collapse
I'm sure plenty of people will download it in next few days
Will be getting it myself later tonite just to try it out
Tried it on a mate's tp and seems very good
Sent from my LT26i using xda premium

I've looked at your github and there are some useful changes in there I may move over to my rom. I just started getting phantom touches in one corner so I'll try out the ts_srv.c change. I might try the system tunings to system.prop, why did you choose those changes?
Why did you disable backuptool in tenderloin_ota_from_target_files? It is what keeps your gapps when you flash. Does it cause you some problems? I find it works just fine.
good job on the rom.
By the way, the camera driver is consuming lots of power (90mA sleep) so I reverted those three commits. The camera doesn't work but I'm down to 19 and I hope to get back to 4. (it's in my new branch c10.1, I'm still new at git so I left my old tree with camera for those who want it and a new tree with it reverted for me.)
Keep up the good work.

MOD Kernel RM5S Beta 1.25 up to 940 / 925 GPU 670K AnTuTu!

Releases are available here, I suggest V3: Release MOD-RM5S-HIGH · mrslezak/android_kernel_nubia_sm8250 (github.com)
Go to the thread in the RM5G group which has more details here - some minor bugs; game mode switch is backwards, high brightness: https://forum.xda-developers.com/t/...0mhz-battery-1-4-stable.4112811/post-84209945
It can be flashed from TWRP on a rooted device. Also install Magisk. You can see the main page there for details, although the RM5S version doesn't have all the features of the RM5G version, it works.
Github source (I don't own this phone, commits aren't proper, look at them in the RM5G repo if you want the proper commits): mrslezak/android_kernel_nubia_sm8250 (github.com)
Note this was just by chance found to be compatible with the LOS kernel our dev made, so I figured why not share with the RM5S folks. Android 10 ONLY. Don't try on R.
Enjoy your new fast phone!
MattoftheDead
{
"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"
}

Others in the Telegram channel are also getting 670K results. One more thing that does not work is the led notification / lights I believe. Can't be fixed as no kernel source available unfortunately.

This kernel can be flashed on 7.14 euro firnware? Nubia Red Magic 5S phone. Just flash the zip file via TWRP?

On Red Magic 5S, firmware 7.15, the core is up, switching the game mode backwards, the logo below does not light up, the ice indicator does not light,when the screen is off, the fan does not work when charging.

mslezak, Thank you very much for your hard work, but the core on 5S does not bring much benefit, I sat on it for a day, in normal use it is the same as on the stock core, I only play tanks, the battery consumption is 25% per hour, the drain is 20% , plus all sorts of glitches on your core, in short, I don't recommend your core for 5S.

Klirensxp said:
mslezak, Thank you very much for your hard work, but the core on 5S does not bring much benefit, I sat on it for a day, in normal use it is the same as on the stock core, I only play tanks, the battery consumption is 25% per hour, the drain is 20% , plus all sorts of glitches on your core, in short, I don't recommend your core for 5S.
Click to expand...
Click to collapse
V3 works quite well on 5s roms. 8.11 and 7.14
Not enough folk to test on 8.12 and 7.15
The only bugs reported, have been
game space button only working in reverse ( got to switch it off to activate game space)
Game space options menu not opening
LED controls not working on 5S devices.
..
In reality this kernel is actually a LOS 17 kernel, it just randomly happened to boot on 5S, it was not intended at all.
As it worked even in a basic way, Matt put his other tweaks and mods into it then shared it.
It still took months of time to tweak his builds for the 5G, so he really does deserve alot of credit for this work.
Im personally working on a 5S stock mod, hoping to release my test builds soon.

Patrick Morgan said:
V3 works quite well on 5s roms. 8.11 and 7.14
Not enough folk to test on 8.12 and 7.15
The only bugs reported, have been
game space button only working in reverse ( got to switch it off to activate game space)
Game space options menu not opening
LED controls not working on 5S devices.
..
In reality this kernel is actually a LOS 17 kernel, it just randomly happened to boot on 5S, it was not intended at all.
As it worked even in a basic way, Matt put his other tweaks and mods into it then shared it.
It still took months of time to tweak his builds for the 5G, so he really does deserve alot of credit for this work.
Im personally working on a 5S stock mod, hoping to release my test builds soon.
Click to expand...
Click to collapse
thanks. As you are working on the rom, could you please check if red magic moment can be extracted as a separate app, which mods can then tweak to work with game updates? It would be awesome given Nubia takes ages to update. Thanks.

Mod edit - translated by https://www.deepl.com/translator:
Hi all, is it possible to optimise for my game for a fee?
***********************************
Вем привет если ли возможность оптимизировать по под мою игру за отдельную плату?

letzdoit said:
thanks. As you are working on the rom, could you please check if red magic moment can be extracted as a separate app, which mods can then tweak to work with game updates? It would be awesome given Nubia takes ages to update. Thanks.
Click to expand...
Click to collapse
Many people asked for this to record games, so far no port has been 100% working. I don't dev this kind of stuff I just do kernels and the internals of things. On XDA and for my primary job.
BTW the TG channel has an updated version of the RM5S and RM5G LOS / custom ROM that was fixed by a few devs to get the lights and such working https://github.com/fandango96/android_kernel_nubia_sm8250 check under the releases page, this ROM is supposed to work on the 8.12 kernel with all working on RMOS Q. Davide Garberi / official LOS dev rebuilt the kernel from scratch then Ali Shahid fixed some of the rewritten code "bugs" and Fandango fixed the remainder.
I do have an R kernel build out there, just no one has tested it. Nubia has not released the vendor DTS/DTSI files required to build so I used those from the Q release.

mslezak said:
Many people asked for this to record games, so far no port has been 100% working. I don't dev this kind of stuff I just do kernels and the internals of things. On XDA and for my primary job.
BTW the TG channel has an updated version of the RM5S and RM5G LOS / custom ROM that was fixed by a few devs to get the lights and such working https://github.com/fandango96/android_kernel_nubia_sm8250 check under the releases page, this ROM is supposed to work on the 8.12 kernel with all working on RMOS Q. Davide Garberi / official LOS dev rebuilt the kernel from scratch then Ali Shahid fixed some of the rewritten code "bugs" and Fandango fixed the remainder.
I do have an R kernel build out there, just no one has tested it. Nubia has not released the vendor DTS/DTSI files required to build so I used those from the Q release.
Click to expand...
Click to collapse
Thanks. Can you please share the link of the TG channel?

It's in the 2nd paragraph of the first post here. I never owned a RM5S so other people worked on fixing the bugs they could find there. I think the moderators took down my TG link when I posted after your question.

Building CM11/LineageOS 11 from latest sources

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.