Related
Hello XDA.
I have used Eclipse, and wanted to try out Android Studio.
The problem is, when creating a new project, i get a "Resolve Error":
Failed to import Gradle project: Could not create an instance of Tooling API implementation using the specified Gradle distribution 'h**p://services.gradle.org/distributions/gradle-1.6-bin.zip'.
Could not determine implementation class for service 'org.gradle.tooling.internal.protocol.ConnectionVersion4' specified in resource 'jar:file:/C:/Users/Me/.gradle/wrapper/dists/gradle-1.6-bin/72srdo3a5eb3bic159kar72vok/gradle-1.6/lib/gradle-launcher-1.6.jar!/META-INF/services/org.gradle.tooling.internal.protocol.ConnectionVersion4'.
C:\Users (Access is denied)
Consult IDE log for more details (Help | Show Log)
Click to expand...
Click to collapse
Seems like noone else got this problem.
I run as Administrator.
Why XDA, WHY?
Are you really creating totally new, empty project? That error message sound more like your gradle has problems importing an existing gradle project.
I'm running into the same issue, and yes, when creating a totally new project this error raises... Even though, after pressing ok, it continues loading (linux version)...
Sent from my LG-P350 using xda app-developers app
Broke'n'Droid said:
Are you really creating totally new, empty project? That error message sound more like your gradle has problems importing an existing gradle project.
Click to expand...
Click to collapse
Yes, like dbarrera said.
This is Windows version.
Any idea?
Have you tried updating your SDK and have you checked your gradle.build in root folder for any errors?
Sent from my SAMSUNG-SGH-I747 using xda premium
ansfent had
tepews said:
Hello XDA.
I have used Eclipse, and wanted to try out Android Studio.
The problem is, when creating a new project, i get a "Resolve Error":
Seems like noone else got this problem.
I run as Administrator.
Why XDA, WHY?
Click to expand...
Click to collapse
I ran into all sorts of trouble trying to set up Android Studio on my Windows 7 64 bit machine: Missing environment variables, mismatching JRE/Android SDK versions, Gradle compatibility issues, etc., etc. After serveral failed attempts, I finally gave up and went back to my old reliable ADT/Eclipse IDE. I don't want to sound pessimist, but I would give it a little more time.
hey Guy's...
if you have problems with gradle try to download the gradle-1.6-bin.zip from http://services.gradle.org/distributions/gradle-1.6-bin.zip and then copy it to the *\Android\android-studio\lib* directory.
"
Download Gradle from its distribution page at http://services.gradle.org/distributions/gradle-1.6-bin.zip
Then you should copy all the contents of gradle-1.6 to \Android\android-studio\plugins\gradle directory
You should also copy the gradle.jar file to \Android\android-studio\lib\ directory"
Finally you should restart Android Studio. After restart everything should work fine.
let me know if it work`s :silly:
It`s Weekend... :highfive:
I have a lot of problems with Android Studio, so I will work with Eclipse until Google fixes all bugs.
still not working...
dude1986 said:
hey Guy's...
if you have problems with gradle try to download the gradle-1.6-bin.zip from and then copy it to the *\Android\android-studio\lib* directory.
"
Download Gradle from its distribution page at
Then you should copy all the contents of gradle-1.6 to \Android\android-studio\plugins\gradle directory
You should also copy the gradle.jar file to \Android\android-studio\lib\ directory"
let me know if it work`s :silly:
It`s Weekend... :highfive:
Click to expand...
Click to collapse
I've tried this process, but it's not working...
Everytime I try to start a new project, I receive a message:
org.jetbrains.plugins.gradle.settings.GradleSettings cannot be cast to org.jetbrains.plugins.gradle.settings.GradleSettings
Do you know what could be causing this?
Thanks in advance.:good:
Finally you should restart Android Studio. After restart everything should work fine.
Hi,
If anyone has trouble with Android Studio, try to install it not in C:// (for Windows), but in another partition. I use it, and it always worked. And also, Android Studio usually will download Gradle by itself automatically.
If the problem still persist, try to re-install (re-download the newest version if necessary). Based on my tips above.
Hello, I am new to the community and although I have flashed loads of roms to various devices this is the first I have tried to build from source.
As it says in the title I am trying to build for my Oppo find 5 which there is a nightly build for, I wanted to try and build from source though.
I have set up the build environment as described on the omni website.
I have followed a set of instructions but when I come to build using
Code:
brunch find5
i dont get a zip in the out folder. I do get the following notes though in the terminal after the build.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Click to expand...
Click to collapse
Those errors are meaningless. Post the full log as an attachment please.
Although I'd suggest reading through the errors first - the first skill anyone needs in Android development is the ability to look through a log and analyze what is what.
At the very least you might've forgotten envsetup. You probably forgot to pull blobs with extract-files (or finding them through some other source...) too - nearly everyone does.
Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:
jejecule said:
Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:
Click to expand...
Click to collapse
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote
maxwen said:
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote
Click to expand...
Click to collapse
yes i'm sure. i was first using the one from themuppets github, then Guillaume advised me to use the coyote ones. Size of the find5 vendor folder is 40,1MB, 132 files. Strangely i had this issues with my last 5 builds, but with the today one, problem disappeared and now my baseband is recognised and everything ok, though i still have this no radio.img message at the end of the build.
Really strange indeed i hate not to know what was the issue Anyway i will build again tomorrow and let you know, Chasmodo from Asylum team is also helping me a lot in understanding some stuffs as i'm a new and noob in building
One question about blobs: when i try to extract it from my device, it works when i run an 4.3 aokp build but then i get error in building. If i try to extract blobs from omni 4.4 (official nightly) i get some access denied on some blobs and then also some errors in the build. No issue with coyote ones though.
Many thanks for your time mate!
So guys, my problem with find5 modem seems to be fixed, no issue with today build neither. But.....now facing exactly the same issue with jftlexx(i9505)...
Build went OK, blobs from coyote, flash and boot OK....but no modem again, I may be do wrong stuff when flashing or missing something.
Before flashing I always do factory reset + wipe system, then flash build, gapps(pa ones mostly) + supersu.
Same repo, same vendor, I9300 OK but manually added local manifest as in your tuto.
Rebuilding atm
Thanks a lot
Sent from my Find 5 using xda app-developers app
Hi all
Im trying to compile OmniRom for Galaxy Note 2 N7100.
Did everything as instructed.
When running "brunch n7100" I have an error:
=============================================
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_n7100'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
=============================================
What should I do to fix it?
Thanks
EDIT: OK, "The Muppets", of cause. Not it builds...
sms2000 said:
EDIT: OK, "The Muppets", of cause. Not it builds...
Click to expand...
Click to collapse
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
PonsAsinorem said:
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
Click to expand...
Click to collapse
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
sms2000 said:
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
Click to expand...
Click to collapse
It didn't not stop...
Actually it is compiling libchromodium.so (forget how it spell), which is 1.2GB in size.
Just let it run for few hours, it will completed eventually.
PS: I'm using VM on Win8.1 4GB, no complain here.
Sent from Windows 98
Yep, it fails again and again on 'libwebviewchromium.so'. The well known 'Error 1' aka not enough RAM.
I recently built a dedicated computer (8Gb + Haswell 3220) just for ROM compiler but have no time to install it properly. Dealing with VMs is not good.
My VM has 4Gb RAM of total 8Gb installed. I know I need 8+ but have to wait till new RAM received.
For now the thread is on hold.
Thanks for all your help.
EDIT: Just for the small experiment I added a 8Gb 'swap' partition to VM and the following build succeeded using no more than 450Mb of it.
I think we need 6 to 8Gb of RAM for good.
Now the question is would it boot and run for good? But we will see...
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
dynomist said:
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
Click to expand...
Click to collapse
I indeed failed to boot. Just the black screen with nothing. I think it was a very bad idea to use TheMuppets with "jallybean".
And what is "media_profiles.xml" for? And where?
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
dynomist said:
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
Click to expand...
Click to collapse
Yes, if you can download the closed source parts from the phone itself. I cannot. Something wrong with switching 'adbd' to 'root'. It switches sort of but locks at the downloading (never finishes).
Currently I'm recompiling with 'DonkeyCoyote'.
'Nightly' build fails to pass boot animation
I downloaded and installed OmniRom Nightly. Not good.
It cannot pass the boot animation. The OMNI BA just loops across different colors for 15 minutes already.
As I remember the same problem I have with any AOSP or CM ROM. I suspect the problem is the boot loader related.
When I installed my first 4.3 ROM it required the latest BL and I flashed it. Should I downgrade now? Which version of BL works for sure and where can I find it?
Thanks.
EDIT: I verified. My Bootloader - MJ5. Is it OK?
EDIT 2: Downgraded to DMF2 and succeeded installing OmniRom Nightly. Testing...
glad that you able to solve the booting prob...
pls update the roms status after u done with your testing
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Thank you for this!
Sent from my SM-P900 using Tapatalk
trying to build kernel
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
dodo99x said:
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
Click to expand...
Click to collapse
It looks like you're in Windows. To my knowledge it is not possible to compile a Linux kernel in windows. I would recommend downloading virtual box and installing some Linux distro in there. This is what I was talking about in the "environment" section at the top of the article.
For android development I find that you need access to a lot of tools where some are only available on Windows and others are only available on Linux so a Windows PC with a Linux VM is ideal in my opinion.
Oh ok, no problem. I just misread the guide. I've setup a build environment in a vm before to compile aosp for my Nexus 10. Shouldn't be too hard to do it again. I recently rebuilt my pc so the vm I had got nuked.
Sent from my SM-P900 using Tapatalk
ok I got my Ubuntu VM up and running using this guide
http://forum.xda-developers.com/showpost.php?p=50748836&postcount=25
installed android NDK to ~android/NDK, and unzipped the kernel source to ~android/kernel
followed your guide to build a SELinux permissive kernel but i'm getting some errors when trying to compile. here's the output:
http://pastebin.com/Npdu7J5h
EDIT: retried doing the EXPORT command and now it seems to be compiling
dodo99x said:
EDIT: retried doing the EXPORT command and now it seems to be compiling
Click to expand...
Click to collapse
When you export a variable in the terminal it only exists for that one session, so if you open a new terminal instance you need to run the command again. If you want to set it permanently normally you can just put the export command into ~/.bashrc
Oh I see. I'll give that a try. I was able to create a new boot.img following the rest of your guide. I have yet to try flashing it though. Will have to find some info about all the kernel options that can be set. Hopefully be able to integrate HMP to get all eight cores running at the same time.
Sent from my SM-P900 using Tapatalk
Cool, let us know how that goes. I wonder how much it would affect battery life.
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Click to expand...
Click to collapse
I tried to install this using VBox Odin and I couldnt get it to work. Tried using BOOTLOADER and also PDA. Not sure the correct one but neither worked for me. Also, Moblie ODin hasnt yet worked but when it does, things will be much easier for me at least.
I have a newly rooted SM-900. I will have to find time someday to compile the kernel against what I have. Must be a slightly newer version than the one you posted. That is only thing I can think since I just got my 12.2. Thanks for the detailed info.
Camera?
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
aarstar said:
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
Click to expand...
Click to collapse
The camera fails for me too. I dumped a logcat and isolated the issue here:
W/ActivityManager( 2746): Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
V/ApplicationPolicy( 2746): isApplicationStateBlocked userId 0 pkgname com.google.android.GoogleCamera
But... the camera is not a huge deal. It did, however, break wifi. I did not get a logcat of that yet, but I would assume it is also a permission issue.
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
aarstar said:
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
Click to expand...
Click to collapse
Wow, I totally missed that entire line in the OP... You literally just made my whole day. I fought this all day long, desperate to get ubuntu working. Thank you for pointing that out.
I get "xt_mark.h" is missing (no such file or directory) error. Any idea why that may be?
I'm using the source for p900 international hoping that I may sidestep the camera issue that way (by enabling permissive to the international kernel I mean), but as it stands it does not compile.
I've googled it but until now it was/is to no avail...
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play).
Click to expand...
Click to collapse
Hey Graeme H,
we both have the same intention. I am downloading the international Kernel at the moment and will compile it again for you guys. The download takes a little longer as I am at vacations.
I am going this route: doviak.net/debian-kit/debian-kit_p00.html . In the future I would like to have arch linux running on this device but a customized debian would be okay for the beginning, too.
Eventually I will try to use framebuffer instead of vnc or something like that. I would love to use sublime-text and dwm on that device with that resolution
Good luck guys. I will try to update.
Edit: hehe I have dwm in front of me now and the resolution is so high that I am barely able to read
Compiled the kernel and flashed in on my device but my camera is still not working. Maybe we need to edit the config:
# Camera sensor devices
#
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_TCM825X is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
CONFIG_VIDEO_S5K6B2=y
# CONFIG_S5K6B2_CSI_C is not set
CONFIG_S5K6B2_CSI_D=y
CONFIG_S5K6B2_POSITION_FRONT=y
# CONFIG_S5K6B2_POSITION_REAR is not set
CONFIG_VISION_MODE=y
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_S5K6AA is not set
Click to expand...
Click to collapse
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
PHP:
smylion said:
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
Click to expand...
Click to collapse
Compiled from Kitkat source. [ur#l]erhan.es/upload/sm-p900-permissive-intl.tar[/url] (odin)
Thank you but the link does not work
smylion said:
Thank you but the link does not work
Click to expand...
Click to collapse
Sorry, it is erhan.es/upload/sm-p900-intl-permissive.tar
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?