Kinda sucks for a first post but I had to do it someday. Been browsing this place for more than a year.
I'm on a Canadian carrier (Videotron) and many of you know that with some phones, like the MT4G (Panache) un less you use a sense ROM, you will have issues with the VM notification (MIUI and some others). The bug is simple if you look at the system info, the field ''my phone number'' is unknown instead of displaying your actual number. On the CM7 builds the issue is the same but it can be fixed manually. But some ROMS like MIUI, you are unable to get this damn thing to work.
I found a fix that I would love to try but unfortunately, I have no clue how to flash it. I went trough so many treads and pages and never read anything on how to fix it. there are tons on unanswered question.
The big question is : how can I flash this on MIUI? http:..review.cyanogenmod.com/#change,11318
It's a script to *fix* the VM notification. I tried installing the zip trough recovery but it failed. I tried running the java script trough ''Script Manager'' but it fails (Syntax error). Both attempts are from the SD card.
This is no script. This is a Java source file fix, which requires recompilation of telephony service, which lies inside the framework - so the whole framework needs to be recompiled.
You have 2 ways of achieving it:
1) Recompile MIUI source code.
2) Decompile MIUI framework, convert the fix code into smali format and merge into decompiled framework, recompile the framework.
ouch. Sounds prety much out of my league for now. Got a lot of reading to do before I'm able to do that lol.
You could open a bug to MIUI team, asking them to integrate support, and point them to CM git that you posted. I believe they'll integrate in sooner or later.
Thnx for the advice. I will give it a shot
Sent from my HTC Glacier using XDA
Hi, this is the first rom I'm trying to build and I think the first for my device (Samsung Galaxy Music). I was trying to build omnirom 4.4 however after a long wait, it gave me a hundreds of errors that seem to be related to Webcore? (I'm sorry I'm also still kinda of a newbie and don't know too much about programing).
I'm using a Virtual Box and this is all what I could copy from the terminal (they were too much errors)
Edit: This is what appears before the bunch of errors and this is my device tree. It is still incomplete and needs some work but at least is a place to start
Re: new "developer's edition" N910V ROM compatability
From the few ROMs I've tried to flash so far, I've gotten a lot of error 7s in TWRP
As far as I can tell from some googling, this means that the updater-script in the ROM isn't allowing it to be installed on the device because it's not one of the ones in it's approved list based on some prop file somewhere
I think the fix to this is to edit the updater-script file by making it a .txt doc, deleting some amount of lines after the "assert," and changing it back to a file before putting it back into the ROM... so I'm trying to learn enough about coding to find out where exactly I should stop the deletion at. Or, alternatively, what I'd have to add.
It's also possible that I'm totally wrong and I'm getting this error for another reason entirely.
If anyone knows what they're doing here, I'd definitely be open to suggestions. If this is what the problem is, I imagine it won't be hard for devs to edit though.
Hello all. I am attempting to build Pixel Experience based upon Android 10 however when I am trying to build it throws an error to include vendor/secure.
Does anyone have a clue how to fix this?
Here is my entire terminal log:
https://pastebin.com/7BCax7YS
My first try would be edit the build file, since no vendor/secure folder to be found on the device.
But that it's basically a guess
Breno Spangler said:
My first try would be edit the build file, since no vendor/secure folder to be found on the device.
But that it's basically a guess
Click to expand...
Click to collapse
Yeah, I thought the same thing, but what build file? I can not find a single thing about this online. It has to pass this inspection to build.
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.