Related
I am working on an open source RTL support for Android and I need help testing...
I have attached a normal app (that should work on any Android 1.5 and up) that runs my method before calling drawText.
The purpose is to make drawText call to it so it will support BiDi.
It reads a file called /sdcard/test.txt from which it gets the test string.
It does not support newlines.
Try it and tell me what you think.
The reason I don't publish the source yet is because knowing how it works would prevent it from being tested properly.
I hope I'm putting this in the right forum...
Hebrew Supported...
Is it also, support the font for Hebrew?
Because in ver 2.1, the have Hebrew but sometimes you see square or ? signs.
TheAgent1982 said:
Is it also, support the font for Hebrew?
Because in ver 2.1, the have Hebrew but sometimes you see square or ? signs.
Click to expand...
Click to collapse
The fonts exist, there's no work necessary on them, you have to push them to the device and that's it...
biditest with Android 2.2 FroYo (FRF50) Arabic test.txt
I tested with Android 2.2 FroYo (FRF50)
without /sdcard/test.txt and with my own text
I don't know about the Hebrew, the Arabic text are not joined (re-shaped) correctly
dudyk said:
The fonts exist, there's no work necessary on them, you have to push them to the device and that's it...
Click to expand...
Click to collapse
I have TP2 running Android 2.1 .
So, any idea how to do it?
Thanks for writing an open source BiDi support.
I did a very short test:
1. It did not render the whole line of text.
2. It looks like it has problems when switching from one language to another. E.g. the closing bracket after the hebrew word is rendered as open.
I attached the original text files and screen shots.
In addition I attache a screen shot of TxtPad Light and how it is rendered there.
TheAgent1982 said:
Is it also, support the font for Hebrew?
Because in ver 2.1, the have Hebrew but sometimes you see square or ? signs.
Click to expand...
Click to collapse
This might be a problem of character encoding.
I did a test with a UTF-8 file and a Hebrew ISO 8859-8. The first rendered the letters correct but the second showed only question marks. (See picture)
As alternative keyboard I recommend using either AnySoftKeyboard or SmartKeyboard.
It is in CM-5.0.8, with a fix on the issue list.
Dear Dudy,
Will your fix work for 2.1 as well? Can you give directions how to apply it to other ROMs? I own an HTC Desire, and would love to implement the fix. So far I just have the common StaticLayout fix.
Thanks,
Ron
EDIT: More specifically, it would be great if you can tell us which files to take from the CM update with the help of baksmali and smali in order to graft them into other distros. That's the way I implanted StaticLayout.smali in MoDaCo roms.
CM 5.0.8 is 2.1. It should apply to any 2.1/2.2 rom, just take my 4 commits from CM's git from framework base repository.
dudyk said:
CM 5.0.8 is 2.1. It should apply to any 2.1/2.2 rom, just take my 4 commits from CM's git from framework base repository.
Click to expand...
Click to collapse
Thanks for the reply, Dudy. I'll be more specific about what I am trying to do: I am trying to pull the files with your patches from the CM-5.0.8 ROM without compiling anything.
With the StaticLayout fix, I used baksmali and smali to disassemble the classes.dex from framework.jar and replace StaticLayout.smali. This worked.
When I look at the page github.com/dudyk/android_frameworks_base/commit/1b0aca31c3e03a5a323276cd15a8df4203a1792c - the one with your commits (is that the right one?) I cannot figure out all the files that I would need to replace. Sorry, I am not a programmer...
I can pretty much figure out that all the files preceeded by core/java/android/ will be found with their exact names in the classes.dex from framework.jar. But I have no idea where to locate the compiled files that resulted from AndroidGraphics2D, the three Canvas files and the ResourceTypes.
If you can point me at the right direction I'll be able to convert a script that was used for the StaticLayout fix so that anyone with a Mac or Linux would be able to easily implement your fix to any none-odexed distro.
Thanks so much in advance!
you didn't add U+0600 support in your Canvas.java @ cyanogen's git
PapaDocta said:
you didn't add U+0600 support in your Canvas.java @ cyanogen's git
Click to expand...
Click to collapse
Why do you say that? I tested for U0590 to U07B1, isn't that enough?
my bad.. i don't know how i overlooked the U07B1.... it's more than enough
Dear Dudy, I really need your help.
Back in the old days (a month ago), before your wonderful work, the best fix we had was Omri Baumer's StaticLayout fix. I was able to use the baksmali and the smali utilities to extract the smali file from framework.jar of CM, and graft it into ANY phone. Another user on the iAndroid forums created a script that automated everything.
I wanted to do the same with your fix. So I compiled a vanilla 2.1 and then applied only your patches, manually, and recompiled. I used baksmali to disassemble all the framework files, and discovered that the changed files were:
android/graphics/Canvas.smali
android/graphics/Canvas$EdgeType.smali
android/graphics/Canvas$VertexMode.smali
android/text/Layout.smali
android/text/SpannableStringBuilder.smali
android/text/Styled.smali
android/widget/TextView$CharWrapper.smali
The two additional Canvas files were tagged as changed, but no textual difference is evident. So altogether we are talking about 5 files that ideally would be easily grafted into ANY device running 2.1, without recompilation.
The problem was that the new Canvas.smali file caused boot loops on my HTC Desire. Logcat caught this:
Code:
D/AndroidRuntime( 103): --- registering native functions ---
W/dalvikvm( 103): Unable to register: not native: Landroid/graphics/Canvas;.drawText (Ljava/lang/String;FFLandroid/graphics/Paint;)V
E/JNIHelp ( 103): RegisterNatives failed for 'android/graphics/Canvas'
E/AndroidRuntime( 103): Unable to register all android natives
This did NOT happen when I tried the vanilla Canvas.smali. So it must be something in your patches. If you can help me figure out how to fix this, your fix will be easily implemented into any un-odexed 2.1 device. The script is all reworked and ready... Just this problem needs ironing out.
Thanks so much - for your wonderful work, and for taking the time to read this.
Ron
ClassicalDude said:
I wanted to do the same with your fix. So I compiled a vanilla 2.1 and then applied only your patches, manually, and recompiled. I used baksmali to disassemble all the framework files, and discovered that the changed files were:
android/graphics/Canvas.smali
android/graphics/Canvas$EdgeType.smali
android/graphics/Canvas$VertexMode.smali
android/text/Layout.smali
android/text/SpannableStringBuilder.smali
android/text/Styled.smali
android/widget/TextView$CharWrapper.smali
The two additional Canvas files were tagged as changed, but no textual difference is evident. So altogether we are talking about 5 files that ideally would be easily grafted into ANY device running 2.1, without recompilation.
The problem was that the new Canvas.smali file caused boot loops on my HTC Desire. Logcat caught this:
Code:
D/AndroidRuntime( 103): --- registering native functions ---
W/dalvikvm( 103): Unable to register: not native: Landroid/graphics/Canvas;.drawText (Ljava/lang/String;FFLandroid/graphics/Paint;)V
E/JNIHelp ( 103): RegisterNatives failed for 'android/graphics/Canvas'
E/AndroidRuntime( 103): Unable to register all android natives
This did NOT happen when I tried the vanilla Canvas.smali. So it must be something in your patches. If you can help me figure out how to fix this, your fix will be easily implemented into any un-odexed 2.1 device. The script is all reworked and ready... Just this problem needs ironing out.
Thanks so much - for your wonderful work, and for taking the time to read this.
Ron
Click to expand...
Click to collapse
My changes add a native method (a C++ one) to the sources, from what I know, it is in the dex file, but maybe smali's files do not extract it, or extract it differently.
I never tried to disassemble files in android and reassemble them, so I have no idea how to help you besides describing the changes to you.
P.S.
Do you think that HebVillian is using my fix this way? I believe that I'm the first to fix this for ROMs above 2.0 (BTW, it's in the froyo branch of CM as well).
I don't know about HebVillain. The maker of the rom was made aware of the way I patched StaticLayout, so it may well be. Perhaps he also read your thread and applied the actual patches...
I noticed that in one of your commits:
http://github.com/dudyk/android_fra...0aca31c3e03a5a323276cd15a8df4203a1792c#diff-5
You added "native" to drawText. It is exactly the function in that line that is throwing the error on boot - about not being native. I tried recompiling with that particular change reversed, but it did not make a difference. Can you investigate the matter? Perhaps the way the Nexus 1 boots is different than that of other devices, and the checks are not as strict. If this is indeed a code problem, perhaps it needs to be addressed for the patch to be viable for other devices.
Take everything I say with a grain of salt - I am no programmer. Just following what I read and understand.
I have no idea if this helps, but googling the words
android registernatives
results in quite a few technical posts complaining about similar problems...
I am sorry for being a nag. But I hope I am getting closer to the source of the problem.
The Android emulator was able to boot up just fine with the patches applied. The logcat stated at the beginning of the runtime:
Code:
D/AndroidRuntime( 29): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 29): CheckJNI is ON
I/ ( 30): ServiceManager: 0xad08
D/AudioHardwareInterface( 30): setMode(NORMAL)
I/CameraService( 30): CameraService started: pid=30
The very same smali files, when applied to the HTC Desire's framework, generated the native error I quoted before. But logcat shows that the beginning of its runtime is indeed different:
Code:
D/AndroidRuntime( 197): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 197): CheckJNI is OFF
D/dalvikvm( 197): Precise GC configured ON
D/dalvikvm( 197): creating instr width table
I/dalvikvm( 197): mlock: /data/dalvik-cache/[email protected]@[email protected], fd=7
So - how do we make the Desire, or any other device, turn on CheckJNI and turn off precise GC?
EDIT: In one of CM's change logs it was written that Precise GC was turned off because of its memory consumption. I am just assuming that this is indeed the cause for my problems. How can we check it?
CheckJNI and Precise GC don't matter.
Repatched and recompiled 2.2 source. The emulator runs beautifully with or without JNI checks. My HTC desire, with a 2.2 rom, still complains about the same function not being native.
The port dudyk did to Omri Baumer's patch works partially - the numbers are not reversed, but the whole line is aligned to the left (with hebrew text appearing to the left of the number, instead of the right).
I have no idea what else to do or to check.
i tried the latest cm6 nightly build and still it won't align Arabic RTL correctly.. it aligns it as LTR and there no reshaping as well....
Hi guys,
today I would like to present to you a simple project that was born on this thread to accomplish a very simple task: since there are thousand of Custom ROMs around here, so much of them are LineageOS based, and because of this their forced to build every time all the ROM and post updates here. Users are also forced to check if their preferred ROM was updated or not. That's why I decided to understand how LineageOS OTA Updater System App works. Because of this I've wrote a simple REST Server API emulation that fully works with your ROM (if integrated of course). How? Continue reading down here.
How does it work?
Of course is as simple as it should be. Clone the repo (is a simple PHP website that you can host on any shared hosting*/VPS that you like) and upload it into your preferred hosting. That's it. If you point your web browser to that address the App is already working.
After, you have to upload all your build to the _builds/ folder, and you're done.
The two already working calls /api and /api/v1/build/get_delta should answer correctly the updater app to make it work (remember that visiting it as a browser is not sufficent).
How to integrate it with my ROM?
You have two options:
- Declare cm.updater.uri on your own build.prop file with the value of you own server URL where you have deployed it (This can be done also by the user with any Android App from the Market)
- Replace the string conf_update_server_url_def value inside values.xml of the OTA App source code (COMPILE TIME ONLY!)
Which builds does it support?
Anything that will be borned by the official guide on how to build your custom LineageOS ROM! So, in poor words will be: stable, rcs, nightly and snapshots (likely called EXPERIMENTAL), from CM7 to CM14.
Delta updates SHOULD work too. Just try it and tell me if they works
How can I debug it?
You can use this simple UnitTest that I've already pushed into my GitHub. Feel free to use it everytime you need. It's based upon NodeJS and Unirest.
Is it free?
"Free software is a matter of liberty, not price. To understand the concept, you should think of free as in free speech, not as in free beer."
—Richard Stallman
Click to expand...
Click to collapse
Use it as you want, do anything you want with it as it's MIT licensed.
Is it free of bugs?
That's why I'm here Only you can help me to squash all the remaining bugs!
I hope this will be useful to anyone of you, helping the ROM community providing a simple OTA updater that already works on LineageOS official ROMs.
Greets.
---
Project Home: https://github.com/julianxhokaxhiu/LineageOTA
More about the study: http://blog.julianxhokaxhiu.com/how-the-cm-ota-server-works-and-how-to-implement-and-use-ours
Changelog Build Scripts ( thanks to @Deltadroid ): https://github.com/syphyr/cm_build_scripts/blob/master/make_changelog
* On a Shared Hosting you can ONLY provide a FULL ROM download, NOT DELTAs!
---
Donators:
- @BlueFlame4 x2
Hey, I'm having trouble using your docker image behind a Nginx https reverse proxy. The server is correctly answering the requests:
Code:
{
"id":null,
"response":[
{
"incremental":"",
"api_level":"",
"url":"http:\/\/MYDOMAIN\/\/builds\/full\/lineage-17.1-20200830-UNOFFICIAL-lavender.zip",
"timestamp":1598774045,
"md5sum":"718fb89f935b979edd57b2642234d1fa",
"changes":"",
"channel":"unofficial",
"filename":"lineage-17.1-20200830-UNOFFICIAL-lavender.zip",
"romtype":"unofficial",
"datetime":1598774045,
"version":"17.1",
"id":"50533a894b2ab0d9b2711444ca4f2b530a8ff2389723ea2bd7ada6e029599e2c",
"size":914450521
}
],
"error":null
}
But the returned `url` is http-only and the updater can't download it (throws error). WhenI try to curl it without `-L` I only get `301 Moved Permanently`. Only when I append `-L` I get the correct binary response over https. I'm pretty sure this is a redirecting issue.
Here's my Nginx config:
Code:
server{
server_name MYDOMAIN;
server_tokens off;
listen 80;
listen [::]:80 ipv6only=on;
# Redirect all HTTP requests to HTTPS with a 301 Moved Permanently response.
return 301 https://$host$request_uri;
}
server {
server_name MYDOMAIN;
server_tokens off;
listen 443 ssl http2;
listen [::]:443 ssl http2 ipv6only=on;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_pass http://127.0.0.1:24087;
proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
add_header Strict-Transport-Security "max-age=15768000; includeSubdomains; preload";
add_header Referrer-Policy same-origin;
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options DENY;
add_header X-Xss-Protection "1; mode=block";
[...]
Any idea what I'm doing wrong?
Basically I want to know how to force the `url` response in the JSON to be `https` instead of `http`. (At least that's what I think is the reason for the updater not being able to download the image.)
Code:
08-30 16:00:19.407 7025 7025 D UpdaterController: Starting 50533a894b2ab0d9b2711444ca4f2b530a8ff2389723ea2bd7ada6e029599e2c
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: Error downloading file
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: java.io.IOException: Cleartext HTTP traffic to MYDOMAIN not permitted
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at com.android.okhttp.HttpHandler$CleartextURLFilter.checkURLPermitted(HttpHandler.java:124)
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:462)
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:131)
08-30 16:00:19.409 7025 7921 E HttpURLConnectionClient: at org.lineageos.updater.download.HttpURLConnectionClient$DownloadThread.run(HttpURLConnectionClient.java:250)
08-30 16:00:19.409 7025 7921 E UpdaterController: Download failed
EDIT: Solved!
Code:
location / {
proxy_pass http://127.0.0.1:24087;
proxy_http_version 1.1;
proxy_cache_bypass $http_upgrade;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
#proxy_set_header Host $host;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-NginX-Proxy true;
}
Not sure if this project is still supported, but with build.prop change, it just checks for updates forever on phone. When I try debugging with the UnitTest script, I get "Not Found The requested URL /CyanogenModOTA/api was not found on this server." (definitely server-related) I've gotten this working before on another VPS, so I'm wondering why it's not on my build server.
Are there any specific packages I need to install to get this working?
Here is my php config: http://hongbuild.ddns.net:81/test.php
klvnhng said:
Not sure if this project is still supported, but with build.prop change, it just checks for updates forever on phone. When I try debugging with the UnitTest script, I get "Not Found The requested URL /CyanogenModOTA/api was not found on this server." (definitely server-related) I've gotten this working before on another VPS, so I'm wondering why it's not on my build server.
Are there any specific packages I need to install to get this working?
Here is my php config: http://hongbuild.ddns.net:81/test.php
Click to expand...
Click to collapse
Since build.prop is in the system.new.dat file in lollipop builds, I just started copying it over from my build server and modified the Build.php file to look for the file instead of inside the zip. I just got this working on my web server. Only issue I'm having is related to change logs but I'm going to try and figure that one out later.
Here are the changes I did to get this working with CyanogenMod 12 (all changes will be assumed from the CyanogenModOTA directory):
- mkdir -p builds/buildprop <-- this is where you copy your build.prop from each build (they go in a folder with the same name as the build zip e.x. cm-12-20150103-NIGHTLY)
- mkdir -p builds/changelog <-- this will have your change logs (name them the same as the build zip except with a .txt extension)
- update setConfig( 'basePath', 'CyanogenModOTA' ) to setConfig( 'basePath', 'http://wfhome.net/CyanogenModOTA' ) in index.php (that is my server)
- change the Build constructor function to this (I updated the preg_match_all line, added the buildPropFolder variable, updated the $this->buildProp line, and changed the changeLogUrl line):
Code:
private $buildPropFolder = '';
public function __construct($fileName, $physicalPath) {
/*
$tokens Schema:
array(
1 => [CM VERSION] (ex. 10.1.x, 10.2, 11, etc.)
2 => [DATE OF BUILD] (ex. 20140130)
3 => [CHANNEL OF THE BUILD] (ex. RC, RC2, NIGHTLY, etc.)
4 => [MODEL] (ex. i9100, i9300, etc.)
)
*/
preg_match_all( '/cm-([0-9\.]+-)(\d+-)?([a-zA-Z0-9]+-)?([a-zA-Z0-9]+).zip/', $fileName, $tokens );
$tokens = $this->removeTrailingDashes( $tokens );
$this->filePath = $physicalPath . '/' . $fileName;
$this->buildPropFolder = str_replace('/full', '/buildprop', $physicalPath) . '/' . preg_replace('/\\.[^.\\s]{3,4}$/', '', $fileName);
$this->buildProp = explode( "\n", file_get_contents($this->buildPropFolder . '/build.prop') );
$this->channel = $this->_getChannel( str_replace( range( 0 , 9 ), '', $tokens[3] ) );
$this->filename = $fileName;
$this->url = $this->_getUrl( '', Flight::cfg()->get('buildsPath') );
$this->changelogUrl = str_replace('/full', '/changelog', $this->_getChangelogUrl());
$this->timestamp = filemtime( $this->filePath );
$this->incremental = $this->getBuildPropValue( 'ro.build.version.incremental' );
$this->apiLevel = $this->getBuildPropValue( 'ro.build.version.sdk' );
$this->model = $this->getBuildPropValue( 'ro.cm.device' );
}
Also he has memcached setup in there, so you might make sure you have memcache installed and set to run on startup on your server. You also need xdelta3 to create delta builds although, I don't think it is working ( I compiled the latest version of xdelta3 and it doesn't appear to do anything as there are not any files being created in the delta folder).
Hope that helps.
Thanks for the help (I'll definitely need it when I actually want to start USING the server), but it seems you've misunderstood me. Right now, I can't even get the rest server running properly-that's why I'm getting a 404 error.
Notice you get an output when you go to http://wfhome.net/CyanogenModOTA/api, I don't get anything!
klvnhng said:
Thanks for the help (I'll definitely need it when I actually want to start USING the server), but it seems you've misunderstood me. Right now, I can't even get the rest server running properly-that's why I'm getting a 404 error.
Notice you get an output when you go to http://wfhome.net/CyanogenModOTA/api, I don't get anything!
Click to expand...
Click to collapse
Ah sorry. First thing I see is that you need mod_rewrite installed in apache.
Code:
sudo a2enmod rewrite
sudo service apache2 restart
Need help with development
First I would like to thank you for using this product and playing with it (which involves patching, testing, etc.).
Since the first post I've made here in XDA the project evolved a little since I rewrote entirely the project to make it composer friendly. Rather than that, the Delta build process is actually non working (I tried to create a ZIP but I don't have enough knowledge in ROM development to tell if it's enough or not) so it's just a WIP layer that should be addressed and fixed (I've already found a Python project which does this already but I'm of the idea that this should be somehow not be a bloated software that needs to install binaries here and there to make it working).
So, actually I'm not really working in this project but It's in my TODO list, meanwhile I'll be very happy to have pull requests with useful patches to make this KK, LL and more compatible So feel free to contribute and thanks again for using it!
JulianXhokaxhiu said:
First I would like to thank you for using this product and playing with it (which involves patching, testing, etc.).
Since the first post I've made here in XDA the project evolved a little since I rewrote entirely the project to make it composer friendly. Rather than that, the Delta build process is actually non working (I tried to create a ZIP but I don't have enough knowledge in ROM development to tell if it's enough or not) so it's just a WIP layer that should be addressed and fixed (I've already found a Python project which does this already but I'm of the idea that this should be somehow not be a bloated software that needs to install binaries here and there to make it working).
So, actually I'm not really working in this project but It's in my TODO list, meanwhile I'll be very happy to have pull requests with useful patches to make this KK, LL and more compatible So feel free to contribute and thanks again for using it!
Click to expand...
Click to collapse
Thank YOU for making it! Really appreciate the time and effort you've put into this project.
rjwil1086 said:
Ah sorry. First thing I see is that you need mod_rewrite installed in apache.
Code:
sudo a2enmod rewrite
sudo service apache2 restart
Click to expand...
Click to collapse
That did it, thanks :good:
I've also implemented your changes, but when I check for updates on my phone, I still get "No new updates found". I've copied my new build over to builds/full, and the build.prop to builds/buildprop/cm*
rjwil1086 thank you very much for your help and suggestions, I made my own server http://paksman.ddns.net/cyanogenmodota, edited build.prop for cm updater to look for server url, made all the changes as you but I always get "No new updates found". Not sure if there is a problem with my server or with this project in general. Have you made any success to make this work?
I have it working. I'll upload mine to github tonight
Think I solved my own problem. My builds were all tagged as 'UNOFFICIAL'. When I changed this to 'NIGHTLY' (for the build and build.prop folder respectively ) they finally started to be recognised by cm updater app. JulianXhokaxhiu and rjwil1086, thank you so much for your effort,your work is being much appreciated.
Packsman said:
Think I solved my own problem. My builds were all tagged as 'UNOFFICIAL'. When I changed this to 'NIGHTLY' (for the build and build.prop folder respectively ) they finally started to be recognised by cm updater app. JulianXhokaxhiu and rjwil1086, thank you so much for your effort,your work is being much appreciated.
Click to expand...
Click to collapse
Yup. Sorry. I knew that but forgot to mention it. That's an issue with the CMUpdater app more than it is with the REST implementation. It doesn't look for unofficial files
Packsman said:
Think I solved my own problem. My builds were all tagged as 'UNOFFICIAL'. When I changed this to 'NIGHTLY' (for the build and build.prop folder respectively ) they finally started to be recognised by cm updater app. JulianXhokaxhiu and rjwil1086, thank you so much for your effort,your work is being much appreciated.
Click to expand...
Click to collapse
Awesome! This fixed it for me as well. Thanks to everyone for the help
[CyanogenMod][OTA][PHP] Open Source REST Server for you
Hi, I have been tested server code with a free host (000webhost) then accessed the web, I received messages:
Warning: Unexpected character in input: '\' (ASCII=92) state=1 in /home/a5885282/public_html/index.php on line 27
Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home/a5885282/public_html/index.php on line 27
The line 27 of index.php is "use \JX\CmOta\CmOta;". But I don't know about PHP. Please help me solve this issue.
@rjwil1086 , @klvnhng , @Packsman please help me to solve following error:
$ node index.js
<h1>500 Internal Server Error</h1><h3>Undefined offset: 0 (8)</h3><pre>#0 /var/www/CyanogenModOTA/src/Helpers/Build.php(214): flight\Engine->handleError(8, 'Undefined offse...', '/var/www/Cyanog...', 214, Array)
#1 /var/www/CyanogenModOTA/src/Helpers/Build.php(63): JX\CmOta\Helpers\Build->removeTrailingDashes(Array)
#2 /var/www/CyanogenModOTA/src/Helpers/Builds.php(115): JX\CmOta\Helpers\Build->__construct('cm-11-20140103-...', '/var/www/Cyanog...')
#3 /var/www/CyanogenModOTA/src/Helpers/Builds.php(49): JX\CmOta\Helpers\Builds->getBuilds()
#4 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Loader.php(123): JX\CmOta\Helpers\Builds->__construct()
#5 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Loader.php(80): flight\core\Loader->newInstance('\JX\CmOta\Helpe...', Array)
#6 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Engine.php(69): flight\core\Loader->load('builds', true)
#7 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->__call('builds', Array)
#8 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->builds()
#9 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Flight.php(43): flight\core\Dispatcher::invokeMethod(Array, Array)
#10 /var/www/CyanogenModOTA/src/CmOta.php(97): Flight::__callStatic('builds', Array)
#11 /var/www/CyanogenModOTA/src/CmOta.php(97): Flight::builds()
#12 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(160): JX\CmOta\{closure}()
#13 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(143): flight\core\Dispatcher::callFunction(Object(Closure), Array)
#14 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Engine.php(310): flight\core\Dispatcher::execute(Object(Closure), Array)
#15 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->_start()
#16 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(142): flight\core\Dispatcher::invokeMethod(Array, Array)
#17 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(48): flight\core\Dispatcher::execute(Array, Array)
#18 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Engine.php(64): flight\core\Dispatcher->run('start', Array)
#19 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->__call('start', Array)
#20 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/core/Dispatcher.php(191): flight\Engine->start()
#21 /var/www/CyanogenModOTA/vendor/mikecao/flight/flight/Flight.php(43): flight\core\Dispatcher::invokeMethod(Array, Array)
#22 /var/www/CyanogenModOTA/src/CmOta.php(80): Flight::__callStatic('start', Array)
#23 /var/www/CyanogenModOTA/src/CmOta.php(80): Flight::start()
#24 /var/www/CyanogenModOTA/index.php(35): JX\CmOta\CmOta->run()
#25 {main}</pre>
Thank you so much.
Thanks all, I fixed.
[CyanogenMod][OTA][PHP] Open Source REST Server for you
I have just creat susscess a server. Thanks.
But, now I want creat a update OTA app for other AOSP ( andoird L) and using that server which I have just creat.
Can I using CMupdater for it? Can you give me some suggest?
Hi, need help to understand!
First of all, i want to say Thank You! For this great job!
I installed server, activated mod rewrite in apache2, apt-get install memcached, made chown for all files to www-data in CyanogenModOTA directory
created directories builds/buildprop, builds/changelog
created file romname.txt in changelog
copied file rom archive to build/full directory
and when i open in browser my ota site: http ota.mydomain.com i see the dir listing as described above
when i try to open url http ota.mydomain.com/api - i see the 404 error.
what exactly i have to do as the next step?
is any json file missed in web root directory (in same place as index.php) ?
and I leave index.php almost unchanged (as in the repository) - just changed string: ->setConfig( 'basePath', '/' )
Thank You once again!
vvzar said:
First of all, i want to say Thank You! For this great job!
I installed server, activated mod rewrite in apache2, apt-get install memcached, made chown for all files to www-data in CyanogenModOTA directory
created directories builds/buildprop, builds/changelog
created file romname.txt in changelog
copied file rom archive to build/full directory
and when i open in browser my ota site: http ota.mydomain.com i see the dir listing as described above
when i try to open url http ota.mydomain.com/api - i see the 404 error.
what exactly i have to do as the next step?
is any json file missed in web root directory (in same place as index.php) ?
and I leave index.php almost unchanged (as in the repository) - just changed string: ->setConfig( 'basePath', '/' )
Thank You once again!
Click to expand...
Click to collapse
Are you sure that modrewrite is working? Can you share a working URL?
lingak said:
I have just creat susscess a server. Thanks.
But, now I want creat a update OTA app for other AOSP ( andoird L) and using that server which I have just creat.
Can I using CMupdater for it? Can you give me some suggest?
Click to expand...
Click to collapse
Honestly I don't know, we have to check if OTA app is the same in Lollipop and works of course the same. If so, we're already safe and yes it can work out of the box. If not, we have to fix it. If you already have a working example, feel free to do a pull request
JulianXhokaxhiu said:
Are you sure that modrewrite is working? Can you share a working URL?
[email protected]:/home/user# a2enmod rewrite
Module rewrite already enabled
[email protected]:/home/user#
.htaccess:
[email protected]:/home/user# cat /var/www/html/CyanogenModOTA/.htaccess
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]
[email protected]:/home/user#
Is any other rules i have to check?
What about statement <Directory /var/www/html/CyanogenModOTA> ?
Is enouph AllowOverride All and Allow from all ?
test url : http ota.smylink.org
Click to expand...
Click to collapse
vvzar said:
JulianXhokaxhiu said:
Are you sure that modrewrite is working? Can you share a working URL?
[email protected]:/home/user# a2enmod rewrite
Module rewrite already enabled
[email protected]:/home/user#
.htaccess:
[email protected]:/home/user# cat /var/www/html/CyanogenModOTA/.htaccess
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]
[email protected]:/home/user#
Is any other rules i have to check?
What about statement <Directory /var/www/html/CyanogenModOTA> ?
Is enouph AllowOverride All and Allow from all ?
test url : http ota.smylink.org
Click to expand...
Click to collapse
Technically it should be enough but the order of where you placed it is important too.
Anyway, going to your URL is just making me think that the PHP code is running well (the redirect to builds folder is triggered by CMOTA Rest Code). You're just missing the htaccess rules.
I'm quite sure you just have to figure out your own server setup to understand if mod_rewrite is properly working (allowing htaccess files to be read and parsed).
Click to expand...
Click to collapse
First time building AOSPextended 8 rom.
I've run in to a few errors so far that I was able to resolve. However, I don't understand how to resolve this one.
Code:
device/huawei/kiwi/init/init_kiwi.cpp:205:9: error: use of undeclared identifier 'WARNING'
WARNING("Unknown variant: %s", model.c_str());
I have already added this to init_kiwi.cpp:
Code:
#include <android-base/logging.h>
But after that I'm still getting the error. Suggestions?
I think I figured it out. I took a look at logging.h and constructed this:
Code:
LOG(WARNING) << "Unknown variant: %s" << model.c_str();
to replace this:
Code:
WARNING("Unknown variant: %s", model.c_str());
I'm compiling it now. Will report back if it works.
Yep, that was it. No more build error.
Have you managed to build it successfully? Any other issues after that ??
I'm still working on it. I believe the error from this post was at a 4% build. I encountered many errors after that which I have resolved. It's mostly updating the code in the device tree to work with android 8. As of today, I'm at a 21% build and need to migrate more code. I'll post an update when I have a solid Alpha build.
It's great that more people are being involved in developing for this device ) I am still learning so one day i could help.. I am willing to test out builds if there is any need for that.
Does anybody know current stage Lineage 15.1 for x2? Is it usable after compiling as is, or some fixes are still needed to get it bootable and usable?
There is already a LOS 15.1 thread and please delete this thread from here.
giaur said:
Does anybody know current stage Lineage 15.1 for x2? Is it usable after compiling as is, or some fixes are still needed to get it bootable and usable?
Click to expand...
Click to collapse
Heyyo, it was bootable yes but right meow I'm currently having issues and attempting to synchronize from scratch again. Not sure if I changed something or if a repo sync is causing issues.
Currently moto999999 and I are the only people trying to fix bugs on the x2 for lineage-15.1... So any extra help is appreciated.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
[email protected] said:
There is already a LOS 15.1 thread and please delete this thread from here.
Click to expand...
Click to collapse
If you're taking about the LineageOS 15.1 blue thread I don't think luchetto was using official lineage-15.1 sources so his build would never be official. It's just a build he was working on.
The official lineage-15.1 is currently only being worked on by moto999999 and I... Hence me saying if anyone wanted to help fix bugs with us the assistance would be appreciated.
I haven't bothered making a thread about it since there's still a bit of work to be done.
Or if you're taking about the Lineage-15.0 thread by andr68rus? It has been long since discontinued and he no longer develops for the Le Max 2 as he now owns a Xiaomi Mi Mix 2 (and a smexy device it is).
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
@giaur I forgot to mention but here is my local manifest and my build scripts if you wish to help or if anyone else wants to help.
https://github.com/lineage-o-x2/local_manifests
For now I am unable to compile Lineage 15.1 sources. Do you have any working build?
giaur said:
For now I am unable to compile Lineage 15.1 sources. Do you have any working build?
Click to expand...
Click to collapse
Heyyo, sorry for late reply. Please check the github link in my previous post.
Do you have telegram? We use that for LeEco devs to communicate
ThE_MarD said:
Heyyo, sorry for late reply. Please check the github link in my previous post.
Do you have telegram? We use that for LeEco devs to communicate
Click to expand...
Click to collapse
Thanks for info. I'm planning to launch daily builds, as soon as I manage to compile sources. I will try your manifest tomorrow, mine contains TheMuppets only. I own already set server +script to automatically upload builds to mega.nz.
I don't have Telegram, but I can create account
Almost there... something happened with Jack, but I'm not sure what exactly - the same config was working to compile Nougat:
Code:
[ 83% 81888/98073] Building with Jack: /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack
FAILED: /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack
/bin/bash -c "(rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack ) && (rm -rf /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc ) && (mkdir -p /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/ ) && (mkdir -p /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc ) && (rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list ) && (touch /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list ) && (if [ -d \"/home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/src\" ]; then find /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/src -name '*.java' >> /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list; fi ) && (tr ' ' '\\n' < /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list | build/tools/normalize_path.py | sort -u > /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq ) && (if [ -s /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq ] ; then export tmpEcjArg=\"@/home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq\"; else export tmpEcjArg=\"\"; fi; JACK_VERSION=4.32.CANDIDATE /home/michal/lineage15/out/host/linux-x86/bin/jack @build/core/jack-default.args -g -D jack.java.source.version=1.7 --classpath /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/sdk_v21_intermediates/classes.jack -D jack.import.resource.policy=keep-first -D jack.import.type.policy=keep-first -D jack.android.min-api-level=21 --output-jack /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack \$tmpEcjArg || ( rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack ; exit 41 ) ) && (rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list ) && (mv /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc.java-source-list )"
Connection to the Jack server timeout, retrying with debug
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 8076 (#0)
ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /root/.jack-server/server.pem
CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* Operation timed out after 150000 milliseconds with 0 out of 0 bytes received
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
Machine has only 8 GB RAM, so I was forced to increase Jack cheap memory, like this:
Code:
JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4096m"
This was enough to compile Nougat, maybe I will should try with larger value.
why r u opening seperate thread for asking it @giaur
shivatejapeddi said:
why r u opening seperate thread for asking it @giaur
Click to expand...
Click to collapse
Beceause there is no existing one? This thread is about issues with Lineage 15.1 compilation.
@ThE_MarD your manifest giving me error message:
Code:
fatal: duplicate path device/leeco/x2 in /home/michal/lineage15/.repo/manifest.xml
With my previous manifest I had TheMuppets only included, build won't boot at all. Now I'm trying with your manifest, we'll see.
@ThE_MarD your manifest giving me error message:
Code:
fatal: duplicate path device/leeco/x2 in /home/michal/lineage15/.repo/manifest.xml
With my previous manifest I had TheMuppets only included, build won't boot at all. Now I'm trying with your manifest, we'll see.
giaur said:
@ThE_MarD your manifest giving me error message:
With my previous manifest I had TheMuppets only included, build won't boot at all. Now I'm trying with your manifest, we'll see.
Click to expand...
Click to collapse
Hmm that's not my manifest amigo. I don't have a manifest.xml. I'd recommend reviewing that XML file or deleting it if there's nothing in there you need.
my manifest is local_manifest.xml
ThE_MarD said:
Hmm that's not my manifest amigo. I don't have a manifest.xml. I'd recommend reviewing that XML file or deleting it if there's nothing in there you need.
my manifest is local_manifest.xml
Click to expand...
Click to collapse
Of course, I mean "local_manifest", after applying it I got that error message. Anyway, compilation has been succeded, if anybody wish to try:
https://mega.nz/#!LV1HVBDC!q---2tIplvLJUFbVv4VKr-V_JHVpiJrXPykR-AwXKUU
Md5:
https://mega.nz/#!yUFnmDzL!OrNT-rpaLFagY3BJwZ_vyTKQcBcjs5kr39mMnYUpeCY
I hope no bootloop this time.
giaur said:
Of course, I mean "local_manifest", after applying it I got that error message. Anyway, compilation has been succeded, if anybody wish to try:
https://mega.nz/#!LV1HVBDC!q---2tIplvLJUFbVv4VKr-V_JHVpiJrXPykR-AwXKUU
Md5:
https://mega.nz/#!yUFnmDzL!OrNT-rpaLFagY3BJwZ_vyTKQcBcjs5kr39mMnYUpeCY
I hope no bootloop this time.
Click to expand...
Click to collapse
Downloaded, will test and report back.
---------- Post added at 10:16 AM ---------- Previous post was at 09:56 AM ----------
giaur said:
Of course, I mean "local_manifest", after applying it I got that error message. Anyway, compilation has been succeded, if anybody wish to try:
https://mega.nz/#!LV1HVBDC!q---2tIplvLJUFbVv4VKr-V_JHVpiJrXPykR-AwXKUU
Md5:
https://mega.nz/#!yUFnmDzL!OrNT-rpaLFagY3BJwZ_vyTKQcBcjs5kr39mMnYUpeCY
I hope no bootloop this time.
Click to expand...
Click to collapse
Well, No error in installation, but not boot.
With GAPPS they enter on boot animation but still there forever, without they not pass the boot logo.
Beackman said:
Downloaded, will test and report back.
---------- Post added at 10:16 AM ---------- Previous post was at 09:56 AM ----------
Well, No error in installation, but not boot.
With GAPPS they enter on boot animation but still there forever, without they not pass the boot logo.
Click to expand...
Click to collapse
Yes, I can confirm. I'm going to make new, fresh build. Probably Lineage bug, already fixed: https://github.com/LineageOS/android_device_leeco_x2/commit/fd453e976c4f9ff828bf83310c2bab6563491f96 we'll see.
ThE_MarD said:
Heyyo, it was bootable yes but right meow I'm currently having issues and attempting to synchronize from scratch again. Not sure if I changed something or if a repo sync is causing issues.
Currently moto999999 and I are the only people trying to fix bugs on the x2 for lineage-15.1... So any extra help is appreciated.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
If you're taking about the LineageOS 15.1 blue thread I don't think luchetto was using official lineage-15.1 sources so his build would never be official. It's just a build he was working on.
The official lineage-15.1 is currently only being worked on by moto999999 and I... Hence me saying if anyone wanted to help fix bugs with us the assistance would be appreciated.
I haven't bothered making a thread about it since there's still a bit of work to be done.
Or if you're taking about the Lineage-15.0 thread by andr68rus? It has been long since discontinued and he no longer develops for the Le Max 2 as he now owns a Xiaomi Mi Mix 2 (and a smexy device it is).
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
@giaur I forgot to mention but here is my local manifest and my build scripts if you wish to help or if anyone else wants to help.
https://github.com/lineage-o-x2/local_manifests
Click to expand...
Click to collapse
Thank you. I have LineageOS 15.1 sources already downloaded. I will sync x2 sources and try to help
Awesome! Glad to hear more people are jumping on board to help
If you have Telegram then please pm me I we have a developer chat group which is a little faster than these forums
New build up: https://mega.nz/#!fc9BmBQa!1u-Jv4nrLzAyCgPb8NcsGhz2tQ1gMtvvgjXRW31YIho
I'm confused. I'm pretty sure it booted, but after flashing it again only blue led and black screen. Or I just flashed different zip first time (so it booted). I am able to clean install rom I was before though. Totally confused. I've tried then 2 times to clean flash my build, not booting. Strange.
You can test and tell me if it works for you.
giaur said:
New build up: https://mega.nz/#!fc9BmBQa!1u-Jv4nrLzAyCgPb8NcsGhz2tQ1gMtvvgjXRW31YIho
I'm confused. I'm pretty sure it booted, but after flashing it again only blue led and black screen. Or I just flashed different zip first time (so it booted). I am able to clean install rom I was before though. Totally confused. I've tried then 2 times to clean flash my build, not booting. Strange.
You can test and tell me if it works for you.
Click to expand...
Click to collapse
Booted fine, now is OK.
Beackman said:
Booted fine, now is OK.
Click to expand...
Click to collapse
Strange
can some dev post the method to make roms like @hunfatal it will be easier to bring other roms to this device. im sure a lot of users would be interested in using variety of roms
https://www.google.pt/search?source...i19k1j0i22i30i19k1j0i22i10i30k1.0.f0TyAkeA2NU
google is your friend...
you have to learn by yourself if you have no one that teaches you... I learned myself too...
4 essential things:
1- rom source
2-device tree
3- device kernel
4-device vendor
Marado said:
https://www.google.pt/search?source...i19k1j0i22i30i19k1j0i22i10i30k1.0.f0TyAkeA2NU
google is your friend...
you have to learn by yourself if you have no one that teaches you... I learned myself too...
4 essential things:
1- rom source
2-device tree
3- device kernel
4-device vendor
Click to expand...
Click to collapse
how do u integrate security patches?
psychem said:
how do u integrate security patches?
Click to expand...
Click to collapse
Security patches are integrated when you update the source with "Repo sync"...
on older versions like lollipop or marshmallow don´t know never tried it..
maybe with git pull or git merge...
Marado said:
Security patches are integrated when you update the source with "Repo sync"...
on older versions like lollipop or marshmallow don´t know never tried it..
maybe with git pull or git merge...
Click to expand...
Click to collapse
what if the source hasnt been updated? like hunfatal was updating RR before LOS was updated by YM
psychem said:
what if the source hasnt been updated? like hunfatal was updating RR before LOS was updated by YM
Click to expand...
Click to collapse
You can send a pm to @hunfatal, he will certainly respond your questions....
but RR is based on lineage, so their source is synchronized.
:good: I left a msg on his thread. He wants to keep it a secret :angel:
psychem said:
:good: I left a msg on his thread. He wants to keep it a secret :angel:
Click to expand...
Click to collapse
Send pm to him...
I could build a rom, but Yumemichi is doing a great job, then i´m focusing my energy
on a great custom kernel for onyx...:silly:
Marado said:
Send pm to him...
I could build a rom, but Yumemichi is doing a great job, then i´m focusing my energy
on a great custom kernel for onyx...:silly:
Click to expand...
Click to collapse
looking forward to the kernel!
psychem said:
looking forward to the kernel!
Click to expand...
Click to collapse
It´s a kernel like many others...:crying:
but did you already build a rom or not? just ask if you have any questions...
Marado said:
It´s a kernel like many others...:crying:
but did you already build a rom or not? just ask if you have any questions...
Click to expand...
Click to collapse
will do it over the weekend when i have free time. will ask then
Marado said:
Send pm to him...
I could build a rom, but Yumemichi is doing a great job, then i´m focusing my energy
on a great custom kernel for onyx...:silly:
Click to expand...
Click to collapse
I have tried most of the custom ROMs available for onyx but I always had to switch back to stock because I faced one common issues in all ROMs : heavy app like snapchat, amazon, Instagram, etc stops working in some time and I have to reopen that app to continue might be because:
>> Its not allowing more CPU usage or might be I need to change Kernel
or
>> device get uncertified after installing custom ROM so version of apps from playstore are not stable or compatible with device
or
>> Some problem with patching WebView with G-Apps
I am just guessing the reasons but you can guide me with possible solution to help my experience with customized ROMs more smoother on OPX
cd247 said:
I have tried most of the custom ROMs available for onyx but I always had to switch back to stock because I faced one common issues in all ROMs : heavy app like snapchat, amazon, Instagram, etc stops working in some time and I have to reopen that app to continue might be because:
>> Its not allowing more CPU usage or might be I need to change Kernel
or
>> device get uncertified after installing custom ROM so version of apps from playstore are not stable or compatible with device
or
>> Some problem with patching WebView with G-Apps
I am just guessing the reasons but you can guide me with possible solution to help my experience with customized ROMs more smoother on OPX
Click to expand...
Click to collapse
Have no idea... But i know that Snapchat was app problem, i think with the last update is working...
other apps i dont know...
Marado said:
Have no idea... But i know that Snapchat was app problem, i think with the last update is working...
other apps i dont know...
Click to expand...
Click to collapse
@Marado
@YumeMichi
@hunfatal
i was trying to build but got into some problems
i overwrote this symlink file when i was trying to solve the errors below - manifest.xml from /root/android/lineage/.repo/ . how do i get it back?
errors were
Code:
[email protected]:~/android/lineage# repo init -u https://github.com/YumeMichi/kernel_oneplus_onyx.git -b lineage-16.0
From https://github.com/YumeMichi/kernel_oneplus_onyx
+ 0419ab9712e...975fdef3f0e cm-14.1 -> origin/cm-14.1 (forced update)
+ 954e6772a58...4e6c6a06b1e cm-14.1-sultan -> origin/cm-14.1-sultan (forced update)
+ 3e184d8da6c...c87e54b532b lineage-15.1-sultan -> origin/lineage-15.1-sultan (forced update)
+ 5b3dca0a275...674e2f500b0 lineage-16.0 -> origin/lineage-16.0 (forced update)
.repo/manifests/: discarding 23 commits
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
Code:
[email protected]:~/android/lineage# breakfast onyx
including vendor/lineage/vendorsetup.sh
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_onyx".
11:42:12 dumpvars failed with: exit status 1
Device onyx not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_oneplus_onyx
Traceback (most recent call last):
File "vendor/lineage/build/tools/roomservice.py", line 258, in <module>
default_revision = get_default_revision()
File "vendor/lineage/build/tools/roomservice.py", line 114, in get_default_revision
m = ElementTree.parse(".repo/manifest.xml")
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in parse
source = open(source, "rb")
IOError: [Errno 2] No such file or directory: '.repo/manifest.xml'
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_onyx".
11:42:14 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_onyx".
11:42:14 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_onyx'
** Do you have the right repo manifest?
Marado said:
Send pm to him...
I could build a rom, but Yumemichi is doing a great job, then i´m focusing my energy
on a great custom kernel for onyx...:silly:
Click to expand...
Click to collapse
Whoa !!
For Pie ?
Great news ! You can PM me for testing !
@psychem you are building Lineageos?
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
Kéno40 said:
Whoa !!
For Pie ?
Great news ! You can PM me for testing !
Click to expand...
Click to collapse
I will release it for everybody testing....:silly:
Marado said:
you are building Lineageos?
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
I will release it for everybody testing....:silly:
Click to expand...
Click to collapse
trying to.
psychem said:
trying to.
Click to expand...
Click to collapse
try repo sync again...
Marado said:
try repo sync again...
Click to expand...
Click to collapse
Code:
[email protected]:~/android/lineage# repo sync
Traceback (most recent call last):
File "/root/android/lineage/.repo/repo/main.py", line 531, in <module>
_Main(sys.argv[1:])
File "/root/android/lineage/.repo/repo/main.py", line 507, in _Main
result = repo._Run(argv) or 0
File "/root/android/lineage/.repo/repo/main.py", line 158, in _Run
copts, cargs = cmd.OptionParser.parse_args(argv)
File "/root/android/lineage/.repo/repo/command.py", line 67, in OptionParser
self._Options(self._optparse)
File "/root/android/lineage/.repo/repo/subcmds/sync.py", line 189, in _Options
self.jobs = self.manifest.default.sync_j
File "/root/android/lineage/.repo/repo/manifest_xml.py", line 360, in default
self._Load()
File "/root/android/lineage/.repo/repo/manifest_xml.py", line 407, in _Load
self.manifestProject.worktree))
File "/root/android/lineage/.repo/repo/manifest_xml.py", line 443, in _ParseManifestXml
root = xml.dom.minidom.parse(path)
File "/usr/lib/python2.7/xml/dom/minidom.py", line 1918, in parse
return expatbuilder.parse(file)
File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 922, in parse
fp = open(file, 'rb')
IOError: [Errno 2] No such file or directory: '/root/android/lineage/.repo/manifest.xml'
you have the repo bin folder inside Lineage source folder?
if yes delete it, and open terminal in desktop and place it there...
you´re using yumemichi´s sources right? the easiest way to build is download the sources direct from yume github, place in lineage source "device" "kernel" and "vendor", change the makefiles in device folder (in this case there is no need because yumemichi source is for lineage too) and brunch onyx....
In this way you don´t need to mess with manifest files (that is probably what you did) and if they´re wrong is a pain to sync back the source...