Related
No matter what I do or use, (Aptana or Eclipse) errors always show in the XML files and I can never get anything to run.
I've done google searches and I can't find answers...I also can't seem to force ignore the errors in the IDE.
The other day I almost broke my keyboard, it's driving me crazy because it's such a stupid issues I can't seem to fix.
PLEASE, I just want it to work...xda is my last resort, I don't want to bug you guys about this, but I just want answers.
*** BUMP ***
without the files and errors no one here can help you.
http://pastebin.com
nenn said:
without the files and errors no one here can help you.
http://pastebin.com
Click to expand...
Click to collapse
You want me to upload the entire eclipse/aptana setup I have?
This is not unique to the sources, this happens with any code...this has something to do with my IDE setup.
Same thing happens on my workstation and my desktop at home.
in the spirit of understanding the problem, how far along developing are you? have you tried compiling the sample code thats out there already?
without information on what you know how can anyone help you solve your problem?
nenn said:
in the spirit of understanding the problem, how far along developing are you? have you tried compiling the sample code thats out there already?
without information on what you know how can anyone help you solve your problem?
Click to expand...
Click to collapse
Yes, can't compile anything...it always tells me an XML error.
I'm not at a point where I can give you the exact error, but I probably can tomorrow.
Start Eclipse and delete all Errors in the Problems View.
Then try to recompile.
Sometimes it solve the problems
Post the xml manifest and errors.
It is a pain to get started. Take a break and try again.
I would recommend un-installing Eclipse and any Android SDK stuff and start from scratch re-installing everything. If you haven't already, use the Android developer section walkthrough to set Eclipse up properly. They indicate which versions of Eclipse and the JDK to download. Maybe you installed the wrong versions of Eclipse or JDK?
Just something to try.
PM Kingklick he's the best at compiling Android.
Ok so I am in the process of building my own android rom. I have built the system.ext2 file using nexus one 2.16.17001 base image. I then ran the build on my HD2 was able to get it to fully boot!
It seems to run really fast, but my first issue is I can not get network to connect, it simply does not recognise the sim card.
I know there are drivers I need to download and update the build with but I am unsure what I need to download and were to get them from.
If anybody could help me it would be great. I am very close to getting a working build!
Can anybody help with this?
GhostXSeries said:
Ok so I am in the process of building my own android rom. I have built the system.ext2 file using nexus one 2.16.17001 base image. I then ran the build on my HD2 was able to get it to fully boot!
It seems to run really fast, but my first issue is I can not get network to connect, it simply does not recognise the sim card.
I know there are drivers I need to download and update the build with but I am unsure what I need to download and were to get them from.
If anybody could help me it would be great. I am very close to getting a working build!
Click to expand...
Click to collapse
I've been trying to figure this out myself. I'm still working on it. I was able to get in the new radio - FRG33 built into the ROM, but that's about it so far.
Can you do me a huge favor? Don't suppose you can tell me - in a PM or otherwise - what steps you took to get it to boot as far as you did? I think if I can fiddle around with that I might be able to get the rest working.
Thanks!
Hatelfy I have sent you a PM as requested.
As Hatelfy suggests I think I need to extract the radio.img file and add the contents into my rom but I cant figure out how to extract the file. Does anybody have any ides?
I have tried mounting the file in ubuntu but it simply does not recognise the file type.
Don't know if it'd work but could you not use something like iso buster and extract raw data? Saying that I searched the other day "nbh extract" and there's a program on here somewhere that'll dump the contents into a folder if that's what you're after!?!?
Im not even sure if im on the right track. Everything on my build is working perfectly. Except the data. I cant get it to see the sim card. I am not sure what I have to update to get it to go on to the network.
Any ides?
Can anybody help with this?
GhostXSeries said:
Can anybody help with this?
Click to expand...
Click to collapse
OK, well how I did it was like this. Not sure if it's the right way of doing it, but the system didn't error and was perfectly happy doing it sooo..
Using a standard Android kitchen, I just downloaded the contents of the FRG33 Radio rom into the root of my working folder. After I was done tinkering with various aspects of my ROM I gave it the command to build from the working folder.
I guess what it does is looks for a radio from root and it incorporates everything on fly. (at least that's what the status messages said it did...)
Once I had my custom rom built I used Coffeeshop to make the system image. After that, I had no idea. I'm not even sure if I was supposed to incorporate anything to the build or not module wise.
When I get back home from work today i'll try out the info you gave me and get back to you and let you know if worked or not.
Hey man Can you PM me on what kitchen you used? I only know of the coffee shop?
Yep sure thing.
I've read the other threads about this but there is no help to be found there unfortunately.
I've been playing with App Inventor because I wanted to avoid learning Java but my think now is that seeing as I do JavaScript/PHP/mySQL and HTML/CSS anyway I might as well do my app development properly.
I've been following the instructions at the official developer.android.com site.
and the part where I have the problem is with Eclipse - at step 1 on that page. I've installed the JDK but when I try to install Eclipse I get an error telling me that there is no Virtual Java machine in the eclipse\jre\bin\ folder.
Well I'm following the instructions so what can I do about this? I don't even understand the error. Is there supposed to be a file in this folder, a folder which a.doesn't come with the standard Eclipse .zip file and which b.doesn't exist at all!
I tried this all before some time ago and got the same problem. At that time I couldn't even use App Inventor because of some JDK/JRE problem but I un-installed and reinstalled Java and App Inventor is working now.
This is one of the most frustrating computing problems I've faced because I've searched all over for an answer and there is nothing out there. Frankly I'm a little surprised at how poor the installation documentation is
The only thing I can think of is I have the wrong version of Eclipse. Which exact one is everyone else using?
Hello Subjective Effect. There is not a folder named eclipse\jre\bin in eclipse installation folder. The version i m using is eclipse-helios. I was not faced the problem you have.
I've solved that part of the problem by downloading a different version of Eclipse. It is a Helios version and is the one with Java. The installation instructions are not clear on this.
I now have another issue but I'll try work that out for the time being.
So I've no idea (again because the instructions are so poor) what to do about this.
I'm on the Android Developers site and trying to start the Hello World tutorial. I'm already stumped at the stage of creating a New Project because after I set up Project name, Application name, Package name and Create Activity clicking "Finish" gives this error:
[2010-10-28 01:33:03 - HelloAndroid] ERROR: Unable to open class file C:\workspace\HelloAndroid\gen\com\subjectiveeffect\helloandroid\R.java: No such file or directory
The reason I think the docs are poor is am I supposed to have created this directory or does Eclipse create it for you? And if it's supposed to be created for you what am I doing wrong?
Subjective Effect said:
So I've no idea (again because the instructions are so poor) what to do about this.
I'm on the Android Developers site and trying to start the Hello World tutorial. I'm already stumped at the stage of creating a New Project because after I set up Project name, Application name, Package name and Create Activity clicking "Finish" gives this error:
[2010-10-28 01:33:03 - HelloAndroid] ERROR: Unable to open class file C:\workspace\HelloAndroid\gen\com\subjectiveeffect\helloandroid\R.java: No such file or directory
The reason I think the docs are poor is am I supposed to have created this directory or does Eclipse create it for you? And if it's supposed to be created for you what am I doing wrong?
Click to expand...
Click to collapse
Mine seems to have that error no matter what I type in.
So what have you done about it? Or can I continue without worrying, is this a trivial error message?
1) you should download Eclipse 3.5.2 as Helios is not supported by Android plugin yet.
http://www.eclipse.org/downloads/packages/eclipse-classic-352/galileosr2
2) R.java problem should go away if you restart eclipse
Also, to start with better use the existing sample project HelloWorld rather than setting up your own.
This is a common known bug. You can use the latest eclipse version, once you setup a project, you will have to go under project properties and choose compiler version 1.6, which is set to 1.5 usually.
Tha will solve the problem, because i was facing the same a few days ago when starting to mess with SDK and Eclipse.
I had a similar problem and gave up for awhile and when I came back to it I found out that I didn't have my paths set correctly for the java jdk, not sure if that is it but it worked for me.
I find if I restart Eclipse it fixes things.
I've been playing with layouts!
Hi All
I have the most recent version of Oxygen which includes a "theme picker" app.
Similar to the one found in the HD ROM's it gives the opportunity to change the entire system theme, without flashing a zip. Which is good news
However, I have been trawling the internet trying to figure out how to create the .apk needed to create my own themes, failing miserably.
Could someone with the required knowledge post a tutorial maybe? Or a link to where the info is so that I can do my own research?
Thanks
i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.
str355 said:
i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.
Click to expand...
Click to collapse
Do you know I didn't even think of that
I shall do so and see what I can come up with
Well I downloaded the Android SDK and all the tools required, then I installed eclipse and started a tutorial on how to build an app - as I assumed this is what I will need to do... but then my brain started to hurt and I needed sleep!
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.