Database Users

[ROM][4.2.1][AOSP] LaNight (Project Extreme Butter) [v9.4.1]

Like the title says, this is a work in progress and i'm releasing the zip for 4.2.1 for LaNightv9.x. I don't want anyone flashing previous LaNight flash this by mistake thus a new thread. This is a thread for android 4.2.1 only.
LaNight is a pure AOSP build, meaning it is NOT CM or built from CM source, so please do NOT ask for CM features. However, it does use device/hardware files from CM and rest from its own build.. so any device specific problems that is in CM may or may not be in LaNight. If you don't like "pure" AOSP, move on.
Features:
- Android 4.2.1 JellyBean
- Pawtip kernel for 4.2
- Build.prop tweaks
- init.d tweaks
- Galaxy Nexus Tweaked HW Acceleration
- New CM10.1 partition
- Speed and Cleanness of AOSP
- GPS Hack
- KC1 modem
- Stock Fonts
- And a lot more stuff!
What's working:
- Camera
- Logcat
- Sound
- Surface flinger
- Media Scanner
- Touch
- GPS
- Phone
- Internal Storage
- Tether
- Slight problem with Virtual Operators and roaming
- Bluetooth
- Everything
- Settings -> Storage FC
- Mount Ext SD to PC
- WiFi
- Data
- SMS
What's not working:
- Nothing i could find
Download:
- v9.2.1 Download is HERE
- v9.3 Download is HERE
- v9.4.1 Download is HERE
Others:
- Potential WiFi fix for people that don't have their WiFi working from HERE (DO NOT FLASH IF IT'S WORKING!)
- WiFi Fix from paw tip(I don't know what he did there to fix it in his ROM) http://goo.im/devs/pawitp/galaxysmtd_aosp42/fixes/20121125_wifi_fix.zip
- Clock font fix http://forum.xda-developers.com/showpost.php?p=34798184&postcount=55
Screen shots
- http://forum.xda-developers.com/showpost.php?p=34797716&postcount=54
Recommended flash procedure:
- Keep a copy of efs folder for security
- Reboot into recovery
- Make a nand backup before you proceed
- Wipe data/ factory reset
- mount and storage -> Wipe System/cache/data/datadata
- Wipe cache/cache partition
- Advanced -> Wipe dalvik cache
- Wipe voltage cache (If the option is given)
- devil -> run clean NStools options
- devil -> run clean init.d directory
- install rom zip from sdcard
- install rom zip once again if it boots you back in recovery (It's flashing kernel/recovery/partition if it finds an incompatible partition)
Required Set up:
- Settings > developer > background process limit > at most 2
- Settings > developer > Force 4x MSAA
Special thanks to:
Google
Whole CM10 Team
TeamHacksung
Pawtip (For first functional AOSP)
Derteufel (For the kernel and first AOSP rom)
Elitemovil(For the first 4.2 port)
Bigixie
Be18
Steeve76
HP40
iall5tar
mkalter (HW acceleration)
mikel.canovas & H3llstorm(For GPS hack)​

Will try it out tomorrow. Thanks for all your hard work ace.
Sent from my SGH-I897 using Tapatalk 2

I will help.
Ace,
I can help a little. I will load this up and try a couple of modems, etc today but the majority of testing will have to wait until tomorrow. Let me know if that is too late. Thanks for the new toy.:victory:
Update:
Got it to boot easily with standard clears and wipes.
Had to revert back to Lanight 8.5 DD to load a GAPPS package and some modems on my SD card, USB doesn't work for me. It comes up and says "Connected as installer" which my PC doesn't recognize. So, I loaded several modems, a couple of GAPPS packages and reflashed. (BTW, if I select MTP in the USB select option, the PC sees the I897 but can't read the memory)
No advanced recovery options, have to power down and 3 button to recovery (Boo!)
KDH_Next_Gen_GAPPS kills the setup wizard.
gapps-jb-20121117-JOP40C-dmd151 loads OK with a couple of force closes, those can be worked through.
No modems install or are recognized.
Manual APNs do not save.
Lockscreen is a little skewed with the clock being partially obscured on wake.
Checking for storage from settings kills settings.apk
More later.. Thanks Ace, most fun I have had all day.

Play around with it that's why I posted here. Try new things and see if you can get it working. And share the findings here.
I will upload test2 today, hopefully the data,phone and storage issue is fixed.

I tried jl3, jk4 and kg3 modems, but none of them worked. This still is a great start. I see great potential with this one. I'll keep trying and reporting.

Maybe try replacing apns-conf.xml in system/etc with cm10 conf?

dave71670 said:
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
Click to expand...
Click to collapse
Thanks for the tip Dave71670, I will play around more tomorrow but I tried to replace some of the files in the zip and my 7zip or WinRAR couldn't recognize the format of the zipped files. Really weird. I PM'ed Ace on it. I will try more hacking tricks later. I love this kind of stuff.

dave71670 said:
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
Click to expand...
Click to collapse
Downloading the latest CM10 now. I'll replace the .xml and report back.

Test2 is up Let the testing begin! Changelog for Test2 is huge so I prefer full wipe even if coming from test1.
Many things has been fixed from build.prop to storage and ril related framework issues. I hope the changes will take affect with the boot.
Test2 Changelog:
- Huge fix in build.prop
- Almost Everything ril/storage related in Framework has been hacked to work
- Added init.d fixes
- apns-config.xml has been edited
- Changed the modem
- vold.fstab hacked
- using the ril drivers from pawtip source code
- A lot more things has been changed that I don't remember
- Some drivers were edited to put on forced mode to work with the device
On a side note: I saw pawtip and CM10 jumped in to help bring 4.2 AOSP for I9000 and this is something I appreciate with all my heart's content. I don't have the time to test his build but i'm sure he did a decent job and the word is out he fixed many issues. I will look into his build whenever I get more time. You can flash his build after a minor edit in updater-script then flash the appropriate cappy kernel to make things work if you do decide to try it. Enjoy!

AceofSpades90 said:
Test2 is up Let the testing begin! Changelog for Test2 is huge so I prefer full wipe even if coming from test1.
Many things has been fixed from build.prop to storage and ril related framework issues. I hope the changes will take affect with the boot.
On a side note: I saw pawtip and CM10 jumped in to help bring 4.2 AOSP for I9000 and this is something I appreciate with all my heart's content. I don't have the time to test his build but i'm sure he did a decent job and the word is out he fixed many issues. I will look into his build whenever I get more time. You can flash his build after a minor edit in updater-script then flash the appropriate cappy kernel to make things work if you do decide to try it. Enjoy!
Click to expand...
Click to collapse
Hey Ace, which kernel did you include in your build? I am running aosp with devil and the storage issues are mostly all I'm facing. I think with the correct kernel this issue would be fixed. If you are using stock kernel I will give it a shot.

dave71670 said:
Hey Ace, which kernel did you include in your build? I am running aosp with devil and the storage issues are mostly all I'm facing. I think with the correct kernel this issue would be fixed. If you are using stock kernel I will give it a shot.
Click to expand...
Click to collapse
I'm using Devil3_1.9.1_KLP_cappy_CFS_BLN_CMC_20121119.zip from HERE in test1 and test2 which is the latest for our cappy.
Derteufel said he fixed the mounting points(to make storage work) in his recent release of I9000 1.9.2 but that shouldn't be a problem since I updated Test1 AND Test2 with updated mount points so I don't see the need for 1.9.2 in my build. Everyone still has storage problems with 1.9.2, i'm more interested in pawtip's kernel if he does release it for our devices or I may have to find a way to compile it.
EDIT: Are you saying the data and phone is working for you? If that is the case, can you share how you got it to work?

AceofSpades90 said:
I'm using Devil3_1.9.1_KLP_cappy_CFS_BLN_CMC_20121119.zip from HERE in test1 and test2 which is the latest for our cappy.
Derteufel said he fixed the mounting points(to make storage work) in his recent release of I9000 1.9.2 but that shouldn't be a problem since I updated Test2 with updated mount points so I don't see the need for 1.9.2 in test2. Everyone still has storage problems with 1.9.2, i'm more interested in pawtip's kernel if he does release it for our devices or I may have to find a way to compile it.
Click to expand...
Click to collapse
I am using 1.9.1 as well. I know that pawitp fixed mount points in his kernel so I may have to compile it since he has the source up. I am downloading your build now. Thanks Ace

dave71670 said:
I am using 1.9.1 as well. I know that pawitp fixed mount points in his kernel so I may have to compile it since he has the source up. Thanks Ace
Click to expand...
Click to collapse
Thanks for always helping me out lol. Can't appreciate enough.

AceofSpades90 said:
Thanks for always helping me out lol. Can't appreciate enough.
Click to expand...
Click to collapse
No problem. I am getting file for repo now. I will let you know how it goes.
Edit: Just saw your edit. I am using a modified version of pawitp's build. It is the ril changes that he made to get data and phone to work.

dave71670 said:
Edit: Just saw your edit. I am using a modified version of pawitp's build. It is the ril changes that he made to get data and phone to work.
Click to expand...
Click to collapse
oh ok, the only place left untouched is service.jar under framework lol I messed around with pretty much everything I known existed or has to do with ril.
Someone in pawtip thread said he changed his dpi to 210 and the storage worked? Did you try it? Does it work on pawtip release? I'm just curious if dpi has anything to do with it... hmmm..

AceofSpades90 said:
oh ok, the only place left untouched is service.jar under framework lol I messed around with pretty much everything I known existed or has to do with ril.
Someone in pawtip thread said he changed his dpi to 210 and the storage worked? Did you try it? Does it work on pawtip release? I'm just curious if dpi has anything to do with it... hmmm..
Click to expand...
Click to collapse
I just tried and as I suspected dpi didn't make any difference. He has storage working out of the box with his kernel so I think that is where the issue lies.

dave71670 said:
I just tried and as I suspected dpi didn't make any difference. He has storage working out of the box with his kernel so I think that is where the issue lies.
Click to expand...
Click to collapse
lol THANK YOU! I thought I wasn't bright enough for such an original and creative idea haha

Lost Root
Ace,
I lost root when I installed test2. Alot of other things are definitely fixed though. I will play around a bit and see if I can get root back and do some further testing. Great job again.

Looks like a good start, will try when there are less things that don't work. GL.

Devil 1.9.4 released for I9000, flash it and see if the storage issue is resolved.

[Guide] Building AOSP & Adding Features

First off I'd like to apologize if this is in the wrong place or if it is perceived as advertising, I simply want to contribute to the dev community and this site, and in particular the Nexus 9 forum that has been the centre of my learning as I took up the hobby of AOSP.
I have been back and forth with AOSP, I've contributed a little bit here and there on the Android development forums but would like to properly document how to build AOSP and more importantly (because it is even less well documented) how to add features, change existing features and generally customize the operating system to your liking. I am by no means an expert but I feel I have enough knowledge that I can share it with others who may be in the position I was a number of months ago. I always found it very difficult to find a centralized location for the information I needed.
To this end I have started a site to do just that. I am using a Nexus 9 for my AOSP development but most (if not all) of the tutorials and information should be applicable to basically any AOSP/Nexus device. I have started things off by creating a tutorial on how to build AOSP from 'scratch' so to speak and a tutorial on how to add items to the power menu such as 'reboot', 'airplane mode' etc.
If anybody would like certain topics covered or just have any feedback or comments please reply here or leave them on the articles themselves. I'll do my best to accommodate / respond.
The link is: http://littlelostandroid.wordpress.com
From tomorrow the following (nicer) link should also work: www.alittlelostandroid.com
I should also add that the blog will be ongoing about all things android device but this initial series will be about also and implementing features.

wow this is a real good guide/blog u put together please do continue

Dreamlogix said:
wow this is a real good guide/blog u put together please do continue
Click to expand...
Click to collapse
Thanks! The next post should be up in a day or two, its been a busy week.

New post up about flashing the build to a device!
www.alittlelostandroid.com

This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:

whowatchlist said:
This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:
Click to expand...
Click to collapse
So I changed the theme so that you can see the most recent posts on the side and work from that. I'm still getting to grips with WordPress to be honest but hopefully that's better now.

Another post about setting up and storing your code on GIT repos:
https://littlelostandroid.wordpress...-open-source-project-part-4-git-repositories/

Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?

THX for your work !
There are plans to continue this great guide?

scoobydu said:
Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?
Click to expand...
Click to collapse
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Topse said:
THX for your work !
There are plans to continue this great guide?
Click to expand...
Click to collapse
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?

seanashmore said:
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?
Click to expand...
Click to collapse
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.

Topse said:
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.
Click to expand...
Click to collapse
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.

seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.

Topse said:
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.
Click to expand...
Click to collapse
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).

[/STRIKE]
seanashmore said:
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).
Click to expand...
Click to collapse
I try this for recovery https://github.com/peteralfonso/platform_build/commit/9b3a020058b84fb1f9cfba600f4a958572a805c3
edit: i think this is to old...

seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage

Topse said:
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage
Click to expand...
Click to collapse
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.

seanashmore said:
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.
Click to expand...
Click to collapse
Year , but zip is easier to use/share.

Topse said:
Year , but zip is easier to use/share.
Click to expand...
Click to collapse
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.

seanashmore said:
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.
Click to expand...
Click to collapse
:good:
I like it to try different ways.Good for learning and deeper understanding.
For my personal use is this way no problem.
But for sharing with other people is a flashable zip file the most used way.

Upcoming Kitakami Platform changes - should I wait or?

Hello,
humberos mentioned in irc this morning that I shouldn't use the Kitakami tree as they were being changed soon.
I just wanted to ask here because I can't leave IRC connected while AFK at the moment.
Are the changes moving the tree from /device/sony/kitakami to /device/sony/kitakami-common?
and, also: Should I wait for a device tree to be made for the Suzuran instead of trying to build one that I started with the Bootable Recovery?
I have an AOSP base working for it, but it was mashed up between the 7.0.0 R32 build instructions on the Sony Developers page, and the 7.1 branch for Omnirom/android_bootable_recovery.
I would still like to attempt to build a device tree to use as practice, and flash the entire OmniROM image to my device if I manage to successfully build the entire image.
I was able to build the kernel out of the 7.1 Omni - using msm8994-perf_defconfig and also aosp_kitakami_suzuran_defconfig, but I'm pretty sure that there are some projects in my build environment that are in the transition phase (of what I mentioned above with the "kitakami-common" changes) so I don't think I have everything linking correctly to export the kernel to the correct output directory.
I'm still new to this, (I'm a student) but I've been able get the TWRP recovery working and flashed to my device in the last 2 weeks (having zero experience with Linux and Ubuntu beforehand), and sort out the busybox/toybox problems with unzip... I thought changing my project from just a 'Recovery' to the entire System, Kernel and Recovery would be good practice and actually get me involved with some programming, instead of just finding premade templates and copying them and fault finding.

Building Lineage OS 14.1 for Grouper - clang error

Hi everyone, I have decided to build LOS 14.1. I know builds already exist, but I thought I would like to do it myself to enable me to update to the latest sources easily.
I have taken @AndDiSa's kernel and device tree for AOSP-7.1.0, and modified them to be compatible (I believe anyway) with LOS sources.
However, when I build, I get a significant way through and then I get the error "clang++: error: unknown argument: "-mapcs" " (I have attached a screenshot of the actual terminal output - There was a lot of text I didn't understand above it)
I have searched and searched, but I cannot find any reference to this argument.
Any help would be much appreciated
Edit: By the way, if you want to see the sources, they are the grouper kernel and device trees on my github (https://github.com/thepiguy0)

@ThePiGuy probably you would like to have a look at my change request. This should help to solve the compile error

AndDiSa said:
@ThePiGuy probably you would like to have a look at my change request. This should help to solve the compile error
Click to expand...
Click to collapse
Thanks for the quick reply I have applied the patch now. I'll update you on the outcome

@AndDiSa following on from that, it does appear to have solved the compilation issue (it has now got further than it did last time). How come your fix hasn't been merged (I noticed that it was submitted last year)?

@ThePiGuy nobody felt responible to review and to merge the fix. I have had submitted two other changes. Not sure whether they are still needed to compile, ...
I have the impression the Nexus 7 is almost abandoned on LineageOS, but I might be wrong.

AndDiSa said:
@ThePiGuy nobody felt responible to review and to merge the fix. I have had submitted two other changes. Not sure whether they are still needed to compile, ...
I have the impression the Nexus 7 is almost abandoned on LineageOS, but I might be wrong.
Click to expand...
Click to collapse
It's a real shame, as LOS is generally one of the best ways to revive a device, and the nexus 7 2012 was immensely popular.
As for compiling, I have hit another error. It states that there is an unknown type name "aligned_u64" in the file if_packet.h which is located in the kernel, under include/linux/.
I have found the line, and it is under the hdr_v1 structure. How should I fix this? I have noticed that LOS default repos and your LOS branch have a different and much shorter version of this file

@ThePiGuy replace by "__aligned_u64" and it should compile as was already posted by @Charles IV

Hope the change works for you.
Most official Lineage development seems halted for grouper, although hazzer does seem to be doing a bit of meddling.
I also just bought a Nexus 7 for 5 LOSCoins, so maybe they're doing something with it

Charles IV said:
Hope the change works for you.
Most official Lineage development seems halted for grouper, although hazzer does seem to be doing a bit of meddling.
I also just bought a Nexus 7 for 5 LOSCoins, so maybe they're doing something with it
Click to expand...
Click to collapse
Your fix worked beautifully - I got to the packaging of the OS at the end (after modifying a few SEPolicies), and then something happened - it was so close
Edit: @AndDiSa any ideas?

@ThePiGuy looks as if you are trying to build the userimage formated as f2fs file system. I am not sure whether this is supported as I never changed there anything and, hostestly speaking, which is not of much use as you can always format the /data partition in recovery. If you have boot.img and system.img everything should be fine and you can flash them using fastboot.

AndDiSa said:
@ThePiGuy looks as if you are trying to build the userimage formated as f2fs file system. I am not sure whether this is supported as I never changed there anything and, hostestly speaking, which is not of much use as you can always format the /data partition in recovery. If you have boot.img and system.img everything should be fine and you can flash them using fastboot.
Click to expand...
Click to collapse
Ok I will do. I didn't change anything relating to the formatting of the userimage (not knowingly anyway), so I'm surprised that is has defaulted to that. Where would I change this to get it back to ext4?

@AndDiSa unfortunately once I flashed the System.img and boot.img, I got into a bootloop where it would show the google logo and unlocked padlock, flash and start again. Could it be due to outdated proprietary blobs? Would I be better off using unlegacy android blobs (they seem to be updated fairly frequently for such an old device)

@ThePiGuy I doubt that the blobs are the reason why ... If it remains on the Google start page it's an indication that there is either a kernel crash or that there are permission issues, i.e. your selinux configuration has some problems. Did you try to boot into TWRP directly and to have a look at /proc/last_kmsg ?

AndDiSa said:
@ThePiGuy I doubt that the blobs are the reason why ... If it remains on the Google start page it's an indication that there is either a kernel crash or that there are permission issues, i.e. your selinux configuration has some problems. Did you try to boot into TWRP directly and to have a look at /proc/last_kmsg ?
Click to expand...
Click to collapse
No I didn't (I'm very new to this - the only other thing I have built is for my G4, which just seemed to work without any issues)
Having had a look now, it looks like it is a kernel panic (I have attached the last_mksg with a .txt extension to get XDA to allow it)

@ThePiGuy which kernel sources do you use? I had similar issues years ago when I was trying to set up the Nougat-Kernel.
Can you please check whether you have the __BRILLO__ option set in system/core/init/Android.mk?
Code:
diff --git a/init/Android.mk b/init/Android.mk
index 67541b8..ff343e9 100644
--- a/init/Android.mk
+++ b/init/Android.mk
@@ -10,7 +10,7 @@ else
init_options += -DALLOW_LOCAL_PROP_OVERRIDE=0 -DALLOW_PERMISSIVE_SELINUX=0
endif
-init_options += -DLOG_UEVENTS=0
+init_options += -DLOG_UEVENTS=0 -D__BRILLO__
init_cflags += \
$(init_options) \

AndDiSa said:
@ThePiGuy which kernel sources do you use? I had similar issues years ago when I was trying to set up the Nougat-Kernel.
Can you please check whether you have the __BRILLO__ option set in system/core/init/Android.mk?
Code:
diff --git a/init/Android.mk b/init/Android.mk
index 67541b8..ff343e9 100644
--- a/init/Android.mk
+++ b/init/Android.mk
@@ -10,7 +10,7 @@ else
init_options += -DALLOW_LOCAL_PROP_OVERRIDE=0 -DALLOW_PERMISSIVE_SELINUX=0
endif
-init_options += -DLOG_UEVENTS=0
+init_options += -DLOG_UEVENTS=0 -D__BRILLO__
init_cflags += \
$(init_options) \
Click to expand...
Click to collapse
I have forked your kernel source (you can see my fork at https://github.com/thepiguy0/android_kernel_asus_grouper).
Unfortunately I can't see that file at all

@ThePiGuy that Android.mk is located in the system/core project in the init directory, not in the kernel.

AndDiSa said:
@ThePiGuy that Android.mk is located in the system/core project in the init directory, not in the kernel.
Click to expand...
Click to collapse
Ah yes I see it now. No I didn't have that option. I'll add it and see if it works

(Accidental duplicate post - see below)

@AndDiSa one thing that has just occurred to me - I have just noticed all the patches in your grouper manifest - will I need to apply all those patches if I use your sources?

I need a little bit of help porting crDroid 6 to the sm-t350

I need a little bit of help portingh crDroid 6 to the sm-t350. Nubianprince started then got pulled away by work. I have initalized the crdroid repo, but i when i run repo sync i think it only downloaded like, 300 mb. i do have an android pie enviroment, does repo link resources? i dont know what is going on there. I will upload my roomservice.xml. I had to remove a couple lines from the original and manually clone them because it keeped giving me an error. the original is here https://github.com/Nubianprince/local_manifests/blob/master/crdroid-ten.xml .
Currently i am using this device tree: https://github.com/Nubianprince/android_vendor_samsung_gt58wifi most custom roms i see are using this: https://github.com/Valera1978/android_device_samsung_gtaxlwifi . I have not seen any non sm-5xx devices using it though, so i hesitate to switch. i worked out a a couple errors of things being defined twice, and then built. but i think i am missing something as the build fails with this: FAILED: ninja: 'out/target/product/gt58wifi/root/init.usb.configfs.rc', needed by 'out/target/product/gt58wifi/ramdisk-recovery.cpio', missing and no known rule to make it
Is there a "quick fix" to provide this file? I am not actually sure what i am missing, or what creates it.
Any help would be appreciated.

This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.

nubianprince said:
This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.
Click to expand...
Click to collapse
Yes, it does make sense. I just don't know enough about the android environment to know where the file, or what is pointing to it, would / should be.

Okay. I believe there is a missing, or many many missing makefiles. I found the file and manually copied it to out, and then the build fails with another missing file. Rinse and repeat, there are a ton of files not being put where they should be. Now what to do with that information, i am not sure ??. I tried including a couple of the make files from android 9, but they didn't make any difference.
oh yeah, and if i do lunch instead of brunch it fails with a different file missing: FAILED: ninja: 'out/target/product/gt58wifi/system/addon.d/50-lineage.sh', needed by 'out/target/product/gt58wifi/verified_assembled_framework_manifest.xml', missing and no known rule to make it

it makes no sense adding files to the "out" folder, fix the issues in your "device" folder check your device.mk file

Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.

lividhen99 said:
Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.
Click to expand...
Click to collapse
What device tree are you using, do you have it on Github?

nubianprince said:
What device tree are you using, do you have it on Github?
Click to expand...
Click to collapse
I am just using the device trees (ten branch) on your GitHub. I haven't made any changes that have gotten me anywhere so i haven't committed my local changes to my GitHub.

That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo

nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I have been away for a while and haven't followed along, but the last week I spent compiling ROMs. I also tried compiling Android 10 using "stock" lineageos gt58wifi and I got stuck at the logo as well. I also tried another device from the msm8916 repository and got stuck at the logo.
The "stock" gt58wifi build, as we all know, has problems with audio, bluetooth, smart cover, etc, etc in all versions 14.1, 15.0, 16.0 and won't even boot with 17.1.
When I first compiled it, it would fail due an error with a config.xml file. I submitted a patch, like others, but haven't seen anything yet.
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/pulls

nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I'm working on SM-T560NU 17.1. It too was stuck at the boot logo. I built an eng build and found it was the hardware vibrator that was getting stuck in a loop. If you remove the vibrator hal from
/device/samsung/msm8916-common/manifest.xml
that should work on the SM-T350 because both platforms share the same msm8916 code?
I did build SM-T350 with 17.1 and was stuck at boot logo and gave up. However, I have not rebuilt it knowing this new information. I will try again with the above change in a few days?

So, as retiredtab has said, he got android 10 booting. But it has all the issues android 9 did: no camera, sound, Bluetooth, or Hal sensor (sort of, it can turn the device on but not off). The system ui is also a little funny on crdroid, not sure about lineage. I don't know how to fix these issues, or where the roots of the problems may lay. Do you have any suggestions for learning more about the android source code? I feel like the aosp docs are good, but you kind of have to know what you're looking for.

I think part of the problem with the SM-T350 is that there has never been a fully working build since day 1. Lineageos 14 had problems to begin with and they were never fixed and got carried over to 15, 16 and now 17. If stock Lineageos 16 was fully working, then getting it to work on 17 would be less of a challenge.
The most likely problem to no audio, camera, bluetooth etc is the Samsung proprietary blobs are not in the correct directories or the configuration blob files are pointing to the wrong directory.
When I face this problem, I find it helpful to look at a working roomservice.xml file and do comparisons.
If there is no working roomservice.xml like "stock" lineageos 14, 15, and 16 for the SM-T350, then I look at similar models. For example, the T550 is the bigger brother and it helps to look through it's roomservice.xml file for hints.
Remember that a compiler mainly checks for syntax errors, not semantic. If you make a typo, a compiler will flag that as an error, but if you write correct syntax, but put a file or files in directory ABC instead of XYZ, the compiler won't say anything.
Another thing that might help is doing a logcat of a working build and comparing it to a non working build. There might be a very obvious error message like "can't find audio.hw.msm8916 in directory /device/samsung/msm8916" or something like that.
Learning how to use tools like meld and diff help tremendously in finding file and directory differences in case you put the blobs in the wrong place. See
https://www.tecmint.com/compare-find-difference-between-two-directories-in-linux/
I used meld when troubleshooting the stuck at boot logo.
If you are a visual learner, I found the following youtube channel helping in learning the overall process of building ROMs.
https://www.youtube.com/c/AlaskaLinuxUserAKLU/videos

I think we have lineage 16 fully working. I think the part I'm having trouble with here is the difference between where the files are read from in Android Q vs P.
If I understood what you said incorrectly, please say so.