Database Info

Recompile and overwrite applications in system/app

As an experiment I am trying to rebuild some standard android applications and replace them in system/app on the G1. I have been through all the steps to get the source code and build for the dream platform and have built the various .apk files of interest (e.g. AlarmClock.apk, Browser.apk etc)
To put the files on the device I delete the old .apk and .odex files and copy my newly built .apk file on to the device. However when I try to run the application it crashes with the following message.
The application Alarm Clock (process com.android.alarmclock) has stopped unexpectedly. Please try again.
I know that replacing the applications like this is possible, because the AutoRotating Browser build works fine when copies over in this manner.
I'm using JF1.31 (RC8)
My initial reaction was that I was not signing the applications properly but having read some posts I think the default built .apk should have the right key already in it.
Another theory I have is that perhaps the applications from the head of the source tree are not compatible with the RC8 (or RC30) Android OS releases. Can anyone tell me how to get the source tree which corresponds to this baseline, I've done some reading around but cannot figure it out. I presume I need to do a repo init -u git://android.git.kernel.org/platofrm/manifest.git -b BASELINE but I can't figure out what BASELINE should be.
Many thanks in advance for any help you can give me!!!

There are some branches in android sources:
master
cupcake
release-1.0
Apps from the first two will not run on default G1, you need to reinstall a whole system. I think by default, following google docs you'll get master. So you need to download a release-1.0 sources.
I may be wrong, but that is what I'm see from my experience.

Thanks for that, I'll get the 1.0 branch downloaded and have a go with that.
Cheers for your help!

I was also trying to recompile some of the built-in apps, specifically the browser, but I can't even get it to build. I get a bunch of import errors, stating that it can't find some of the android libraries, such as android.net.http.AndroidHttpClient, android.os.AsyncTask, etc. I've got the android.jar from the SDK in my build path, and it finds some of them, such as android.webkit.URLUtil.
Can anyone shed some light on what I need to do to get it to see the missing libraries? Thanks.

UndeadCretin said:
Thanks for that, I'll get the 1.0 branch downloaded and have a go with that.
Cheers for your help!
Click to expand...
Click to collapse
There are around a dozen build breaks in release-1.0... all of them are due to missing header #includes in various .c and .h files. So, when it doesn't work, don't give up. Fix the breaks and everything will build properly.

Are you resigning the .apk files? Cuz you have to do that for them to work correctly.

Koush said:
There are around a dozen build breaks in release-1.0... all of them are due to missing header #includes in various .c and .h files. So, when it doesn't work, don't give up. Fix the breaks and everything will build properly.
Click to expand...
Click to collapse
Yep I fixed these problems but I have now hit upon the following problem:
(unknown): error 17: Field android.hardware.SensorManager.LIGHT_NO_MOON has changed value from 0.0010f to 0.001f
******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************
I've been in and modified SensorManager back to 0.0010f and that let me build get further but I hit the same error again later in the build.
Given that release-1.0 should be a stable branch is it normal to get all these build issues?

Managed to fix the java issue by modifying public_api.xml. Then hit several more C++ problems which I fixed and finally I can build the lot!
Just tried building the AlarmClock application and running on the G1 and it works fine. Thanks everyone for your help!

>Managed to fix the java issue by modifying public_api.xml. Then hit several more C++ problems which I fixed and finally I can build the lot!
Can you write, what did you fix?

^ Agreed, let us know which files need modifying and what needs doing, i've been trying to get my release-1.0 build root working too!
Alternatively, UndeadCretin, could you build the firmware (release-1.0) with a modified framework-res i can send you?

Ok, I managed to compile it without any editing of xml.
Just added stdlib, string, vector headers to dozen of cpp/h.

worry said:
>Managed to fix the java issue by modifying public_api.xml. Then hit several more C++ problems which I fixed and finally I can build the lot!
Can you write, what did you fix?
Click to expand...
Click to collapse
To fix the java issue, I modified frameworks/base/core/java/android/hardware/SensorManager to change the LIGHT_NO_MOON value to 0.0010f (from 0.001f) and in out/target/common/obj/PACKAGING I modified the <field name="LIGHT_NO_MOON" to have value-"0.0010f">
After this there were several other c++ files which were missing relevant includes. I'm afraid I didn't keep a note of these so cannot provide much detail but mostly they were missing one of the following
#include "stdlib.h"
#include "string.h"
#include "stdio.h"
I think one file needed the following include
#include <string>
and there were a couple of other files that needed other includes. The best way to find these is to google for the function name that isn't building and you should be able to find the appropriate include (that's how I did it).
Hope that helps a bit!

were you able to repo sync after adding the local_manifest.xml?

ximonx said:
were you able to repo sync after adding the local_manifest.xml?
Click to expand...
Click to collapse
I did try that previously but it didn't work. I don't think the relevant files for the dream build are available in the release-1.0 branch. This wasn't a problem for me since I'm only interested in building the applications which work fine with the generic build.

I would like to do the same for the mms application. Could you give me the steps or a link how to do it? I mean do I need the whole sources from android platform to do it? How can I just compile one application?

Phlogiston said:
I would like to do the same for the mms application. Could you give me the steps or a link how to do it? I mean do I need the whole sources from android platform to do it? How can I just compile one application?
Click to expand...
Click to collapse
I downloaded the whole Android source (the release-1.0 branch) and compiled the lot. It may be possible to just build the individual application but I do not know how. It is not vital to build for the dream platform if you only care about the applications since they will work fine with the generic build.
So the basic steps to start are:
Get yourself a Linux or Mac OS platform (I use Ubuntu running in VMWare on my XP box).
Follow the instructions here: http://source.android.com/download but when you come to repo init add the flag -b release-1.0
Fix various build problems

When recompiling individual apps to replace system apps is there a way of just building a single application or does the entire thing need making?

ximonx said:
When recompiling individual apps to replace system apps is there a way of just building a single application or does the entire thing need making?
Click to expand...
Click to collapse
My experience is that you have to do the whole thing if you are building from source. There is one way I know of to get around this, which is to use baksmali and smali.

Just to be clear, making the entire thing = build from source root?

ximonx said:
Just to be clear, making the entire thing = build from source root?
Click to expand...
Click to collapse
If you are asking me--yes, that's what I mean. Make sure to build for dream-open as the target (it's generic by default).

[Q] How to compile ROM from Paulburton's ICS source??

Can anyone provide me some reference or guide on how to compile the ROM for tf101 from Paulburton's ICS source.

rajkumard said:
Can anyone provide me some reference or guide on how to compile the ROM for tf101 from Paulburton's ICS source.
Click to expand...
Click to collapse
Check his website for repo information. Beyond that, its no different than compiling any rom from source.
You should know that you probably will not get anything different than what he has released thus far, that is, unless you have coded your own changes.

Thanks, I will check the link. I believe he has few bug fixes which I need, that's the reason why I wanted to compile it.

rajkumard said:
Thanks, I will check the link. I believe he has few bug fixes which I need, that's the reason why I wanted to compile it.
Click to expand...
Click to collapse
Understood. I do know that Paul is neck deep with finals, and other school stuff, so there is no harm in running a compile yourself. I just wanted to make sure you knew what to expect. His repo sync is a tad different from other instructions, i.e. CyanogenMod...but once you get it all pulled down, its essentially the same steps for the compile portion.

Actually I am new to this. All these days I have been only using the ROM's and never tried to compile one. This is my first time and I appreciate your help. The link really helper, I have started syncing the repo, looks like it's going to be a while. I will post if I run into any issues.

rajkumard said:
Actually I am new to this. All these days I have been only using the ROM's and never tried to compile one. This is my first time and I appreciate your help. The link really helper, I have started syncing the repo, looks like it's going to be a while. I will post if I run into any issues.
Click to expand...
Click to collapse
I will tell you this...use ccache, its a huge time saver when you need to rebuild after making changes. Also...dedicated build system really is recommended, and without question, the more juice its got, the better.
Here are a couple of links...including a kernel specific one from CyanogenMod's wiki. I use both when I am bored and just want to compile something
Yet Another Tutorial on Building Android from Sources
Building Kernel from Source
Compiling ICS from Source
Hope these help!

http://source.android.com/source/initializing.html
http://wiki.cyanogenmod.com/wiki/Building_from_source
You will probably need these... be sure to cross reference the CM website against the google one. There are a few differences.

Thank you for the links. I got a spare machine and am thinking it is about time I did something productive with it.

Thanks for all the links, I was using one of the links that you have provided. It had the with step by step instruction. I followed it, most of the things went fine and some issues I was able to resolve. Now when try to build the rom using the make command I get the following error. I am doing the sync again to see if it resolves. I will try it out tomorrow. Meanwhile if any of you have any suggestions please let me know. btw I have tried the solution provided in one of the xda thread (repo sync -f) already and it did not resolve.
ERROR:
cts/apps/CtsVerifier/lib/colorchecker/Android.mk:22: external/stlport/libstlport.mk: No such file or directory
make: *** No rule to make target `external/stlport/libstlport.mk'. Stop.

rajkumard said:
Thanks for all the links, I was using one of the links that you have provided. It had the with step by step instruction. I followed it, most of the things went fine and some issues I was able to resolve. Now when try to build the rom using the make command I get the following error. I am doing the sync again to see if it resolves. I will try it out tomorrow. Meanwhile if any of you have any suggestions please let me know. btw I have tried the solution provided in one of the xda thread (repo sync -f) already and it did not resolve.
ERROR:
cts/apps/CtsVerifier/lib/colorchecker/Android.mk:22: external/stlport/libstlport.mk: No such file or directory
make: *** No rule to make target `external/stlport/libstlport.mk'. Stop.
Click to expand...
Click to collapse
The obvious question would be does the folder/file exist?
Code:
$ ls external/stlport/libstlport.mk
external/stlport/libstlport.mk
If it is...type 'env' at your command prompt and see what environment variables are set to see if the external folder should be seen.
Re-run 'source ./build/envsetup.sh', then 'lunch' and choose the tf101-userdebug (or what ever Paul uses now) option listed after running lunch.
See if that helps.

I'm repo sync'ing now- gosh, it takes longer to sync than it does to build. I still have to clone the kernel. I think it's been downloading for 2 hours!
I've actually never flashed this ROM, but that won't stop me from building it

Thanks gVibeR. The external folder exist but the 'stlport' folder does not exist. And I also did not see any option with 'tf101' in it when I run 'lunch'. I tried re-syncing the repo but i ran into out of space error. I did not know where to delete all the earlier repo downloads. This was a brand new Ubuntu installed with 25gig disk space. I will keep looking and let know if I had any luck.

rajkumard said:
Thanks gVibeR. The external folder exist but the 'stlport' folder does not exist. And I also did not see any option with 'tf101' in it when I run 'lunch'. I tried re-syncing the repo but i ran into out of space error. I did not know where to delete all the earlier repo downloads. This was a brand new Ubuntu installed with 25gig disk space. I will keep looking and let know if I had any luck.
Click to expand...
Click to collapse
I think you'll need more space than that - once you start building, the directory will swell to over 20gb. For comparison, andromadus(ICS) for the vision is 21g and CM7 (GB) is 18gb.
I'm still downloading, but spark source is at least 11gb and that doesn't include the kernel or the out directory, which will fill up after building.
I think you will need at least 25gb for the build plus whatever for ubuntu. If you are hard up for space, you can install one of the server versions of ubuntu, which doesn't include the GUI (~1.5gb).
The repo files are stored in .repo, which will be hidden. Use ls -a to see it, although I think it manages and discards old commits.

Thanks gee one, I have more than enough space, just thought 25gig should be fine. I will install Ubuntu again with more space and give it a try. Let me know how it goes for you, please post if you got any issues and resolved it.

Native programming of webos LG TVs using Qt 5.2.1

I'm not sure if many are aware, but LG TVs running webos (under webos 2.x here) probably contain a *full* installation of Qt ( in my case full Qt 5.2.1 is installed). When I said full, I mean that all Qt quick, declarative, webKit, gui, network, OpenGL, etc. Qt libraries are available .
So far I've managed to successfully test/run the following:
-simple OpenGL ES applications (webos uses the Wayland architecture, see https://wayland.freedesktop.org for details ); I can actually compile and run any client included in Weston 1.2.0, see https://wayland.freedesktop.org/releases/ for what is available.
- Qt QML, Qt GUI applications also with WebKit can all be compiled and run on the TV.
- Kernel modules: compiled CIFS module and I'm able to moutn SMBA shares under SmartShare. Recording to Samba shares not possible unfortunately....
- getevent android tool ported to linux (see https://github.com/ndyer/getevent). Very useful for finding various key events. I used it to write my own 'daemon' to listen to Magic Remote key presses and start other applications.
- I've managed to also compile qemu-i386 (from qemu-stable 2.4) so that I can run the native sopcast linux i386 client (sp-sc-auth) on the TV itself. This in combination with a custom-made Qt application for choosing sop streams and SS IPTV means that I can watch sopcast streams on my TV at the push of a remote button.
- Custom-made ambilight. I capture screen, decode produced jpeg file, do led color computations and spit them via usb (libusb available on the TV) to an arduino controlling the LEDS.
====
Needless to say, but as prerequisites you need a rooted TV, access to TV via telnet and/or ssh/sftp, extracted rootfs from your TV, toolchain and kernel sources (if you need compile additional modules). Toolchain and kernel sources are available for my TV, from the LG open-source website.
If other people are interesting I can post some more details.

I was trying to do the same thing, I compile several sources with curl library after extracting the file system , can you give me more info on the Qt library?
thanks

y=fx said:
I was trying to do the same thing, I compile several sources with curl library after extracting the file system , can you give me more info on the Qt library?
thanks
Click to expand...
Click to collapse
Well, I think that the Qt library version installed on your TV may not be the same with mine; probably it depends on the webos version. On my TV I have Qt 5.2.1 (easy to tell from the file extension,; for instance I have Qt lib files with names such as libQt5Core.so.5.2.1, etc.) By luck I'm running Kubuntu 14.04 which uses, by default, the same Qt version. So this means that I've already had all Qt headers installed under /usr/include.
In your case, you'll need to download all Qt dev library packages matching the libs. from your tv, and extract them manually somewhere. Once you have that generate makefiles using qmake, then modify them to point to your libs. and headers.
Let me know how it goes for you.

xtreme_protector said:
Well, I think that the Qt library version installed on your TV may not be the same with mine; probably it depends on the webos version. On my TV I have Qt 5.2.1 (easy to tell from the file extension,; for instance I have Qt lib files with names such as libQt5Core.so.5.2.1, etc.) By luck I'm running Kubuntu 14.04 which uses, by default, the same Qt version. So this means that I've already had all Qt headers installed under /usr/include.
In your case, you'll need to download all Qt dev library packages matching the libs. from your tv, and extract them manually somewhere. Once you have that generate makefiles using qmake, then modify them to point to your libs. and headers.
Let me know how it goes for you.
Click to expand...
Click to collapse
I did it this way for the sdl2 library, but I had to copy the whole file system and mount it to make a chroot . The problem I encountered for the QT library (the version in use on my TV is 5.4.1) it's with the compiler. I do not have a compiler that supports c++11 , I only found version 4.2.3 of gcc/g++ as a working ipk package ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/gcc_4.2.3-1_arm.ipk
Code:
Target: arm-none-linux-gnueabi
Configured with: ../gcc-4.2/configure --build=i386-pc-linux-gnu --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi --prefix=/opt --disable-nls --disable-static --with-as=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-as --with-ld=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-ld --enable-languages=c,c++ --disable-multilib --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --enable-shared --enable-symvers=gnu --enable-__cxa_atexit
Thread model: posix
gcc version 4.2.3
edit: ok I was able to fill out a small program correctly

y=fx said:
I did it this way for the sdl2 library, but I had to copy the whole file system and mount it to make a chroot . The problem I encountered for the QT library (the version in use on my TV is 5.4.1) it's with the compiler. I do not have a compiler that supports c++11 , I only found version 4.2.3 of gcc/g++ as a working ipk package ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/gcc_4.2.3-1_arm.ipk
Code:
Target: arm-none-linux-gnueabi
Configured with: ../gcc-4.2/configure --build=i386-pc-linux-gnu --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi --prefix=/opt --disable-nls --disable-static --with-as=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-as --with-ld=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-ld --enable-languages=c,c++ --disable-multilib --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --enable-shared --enable-symvers=gnu --enable-__cxa_atexit
Thread model: posix
gcc version 4.2.3
how did you fill out the qt sources ? does the qt source you compiled work?
Click to expand...
Click to collapse
I did not recompile Qt. I simply used all libs from the TV (rootfs) and local additional header files. As I said, I generate makefiles using qmake, modify them to point them to the TV libraries and then compile whatever I need... Btw. I cross-compiled my Qt programs.
Regarding the toolchain, I have version 4.6.4 (dated 20120731).

xtreme_protector said:
I did not recompile Qt. I simply used all libs from the TV (rootfs) and local additional header files. As I said, I generate makefiles using qmake, modify them to point them to the TV libraries and then compile whatever I need... Btw. I cross-compiled my Qt programs.
Regarding the toolchain, I have version 4.6.4 (dated 20120731).
Click to expand...
Click to collapse
I have always used the dynamic libraries present, however I managed to compile and package a test program. Now the next step is to do some porting, eg kodi .
good news www.cnx-software.com/2018/03/19/lg-releases-webos-open-source-edition-optimized-for-raspberry-pi-3/

y=fx said:
I have always used the dynamic libraries present, however I managed to compile and package a test program. Now the next step is to do some porting, eg kodi .
good news www.cnx-software.com/2018/03/19/lg-releases-webos-open-source-edition-optimized-for-raspberry-pi-3/
Click to expand...
Click to collapse
Regarding kodi, I've already started . I've started with Jarvis since it has support for wayland. Unfortunately even this requires g++ 4.7.x or better. Not sure if teh standard arm gcc toolchain (4.7 on ubuntu 14.0.4) produces runnable executables. Will try this evening, though.
Edit: The arm cross-compiler installed by default in ubuntu 14.0.4 works. So, most likely any " arm-linux-gnueabi" will work for you. I'm using now "arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.7.3-12ubuntu1) 4.7.3"
If you have ideas regarding kodi porting, let me know. It would be just great to have it running on our TVs.
===
Also the link you posted regarding webos on RPI looks promising, indeed. Question is what is inside .
Edit: kodi already starts but cannot create the window system. I know what happened: the modified configure script failed to enable building the wayland back end. Will try again, although my TV uses really old wayland ( version1.1.0). I'll keep you posted...

Well, regarding kodi, I enabled wayland, libraries load fine, but now I get a "Illegal instruction" error. This is a tough one since without proper tools (gdb, strace), it's difficult to figure out what's going on.
If anyone could help figuring this one out, let me know.

Hi this morning I ported a small application. I posted the app on github https://github.com/Sputkin/uMario_Jakowski .
xtreme_protector said:
Well, regarding kodi, I enabled wayland, libraries load fine, but now I get a "Illegal instruction" error. This is a tough one since without proper tools (gdb, strace), it's difficult to figure out what's going on.
If anyone could help figuring this one out, let me know.
Click to expand...
Click to collapse
How are you connecting dynamic libraries ? how you have configured the project

y=fx said:
Hi this morning I ported a small application. I posted the app on github https://github.com/Sputkin/uMario_Jakowski .
Click to expand...
Click to collapse
Nice, will have a look. How did you manage to pack it as an ipk ? Where does it install ? Is a native app, i..e, does it appear in the webos start menu ?
y=fx said:
How are you connecting dynamic libraries ? how you have configured the project
Click to expand...
Click to collapse
Right, so it's a mix of existing libs from TV (rootfs) and my own compiled ones. The process was as follows:
- configure kodi for wayland, cross-compilation, arm arch, etc. Of course the configure script would stop in some missing library.
- Whenever the above happens, patch/modify the configure script to skip checking for the installed lib. If the library exists in the rootfs, nothing to do.
- Else, download source of the library, cross-compile it for arm, install it in some dir.
- In the end, the configure script finishes...
- Trying then to make kodi, the linking process stops for missing libraries (on my TV the libs. names end in libxxx.so.ver.subver_etc.so, so no way for the patched build system to find the proper name for the *.so file). In this case, I've manually modified the Makefile to point to the library (using -l:libxxx.so.ver.subver_etc.so). It's a very cumbersome process, but hey, for now it's good enough...
===
I could upload my configure file for kodi Jarvis. Also, the main modified Makefile might help, to get you an idea about what I mean...
My point is that I;m just trying to see if kodi 'can' work, without lots of source code modifications. If this succeeds, of course, we need to take a step back and build a sound build system for the webos.
One more update regarding kodi: I now have gdb and strace running on the TV, and i can trace where the "illegal instruction" happens. Unfortunately it is in the boost library, in function try_lock() (which has different implementations for different architectures). I'm going to try to bypass the error by forcing to use the pthread library. Let's see what comes out .

xtreme_protector said:
Nice, will have a look. How did you manage to pack it as an ipk ? Where does it install ? Is a native app, i..e, does it appear in the webos start menu ?
Click to expand...
Click to collapse
I used the tools provided in the sdk, ares-package ares-install ..... etc . here you can find my template https://github.com/Sputkin/uMario_Jakowski/tree/master/webos_ipk
if you can, upload the configuration file for jarvis branch

Well, kodi starts now !!!
Let's see what works .

Well, no 'magic remote' input, so cannot tell ....

y=fx said:
I used the tools provided in the sdk, ares-package ares-install ..... etc . here you can find my template https://github.com/Sputkin/uMario_Jakowski/tree/master/webos_ipk
if you can, upload the configuration file for jarvis branch
Click to expand...
Click to collapse
Please see my prev. questions. How did you pack it ? What it uses (SDL maybe ???). Up to my head in the kodi stuff. I need to get them 'magic mote'' working, just to see where the next crash is....

you can connect an HID device
---------- Post added at 06:51 PM ---------- Previous post was at 06:40 PM ----------
xtreme_protector said:
Please see my prev. questions. How did you pack it ? What it uses (SDL maybe ???). Up to my head in the kodi stuff. I need to get them 'magic mote'' working, just to see where the next crash is....
Click to expand...
Click to collapse
uses the SDL2 library entirely so it should work on any version with this library . To package, you must use the ares-package script provided in the LG SDK , copy the appinfo.json file and the images in the folder where you have compiled kodi , change the name of the executable in the appinfo.json file and then exec
Code:
ares-package .

Ok, clear, thanks. Will try.
===
Now, any idea how to get some 'input' into kodi ?
Edit: How could I force kodi to use the magic mote (which I suppose/hope is some touch/mouse interface) ??? Is there a kodi setting ?

xtreme_protector said:
Ok, clear, thanks. Will try.
===
Now, any idea how to get some 'input' into kodi ?
Edit: How could I force kodi to use the magic mote (which I suppose/hope is some touch/mouse interface) ??? Is there a kodi setting ?
Click to expand...
Click to collapse
...

Even with a usb keyboard connected, I cannot get kodi to respond to keys (no crashes though ...
What's going on ? Ideas ?

xtreme_protector said:
Even with a usb keyboard connected, I cannot get kodi to respond to keys (no crashes though ...
What's going on ? Ideas ?
Click to expand...
Click to collapse
please upload the configuration file so that I can test it directly

y=fx said:
please upload the configuration file so that I can test it directly
Click to expand...
Click to collapse
That's not going to be so simple I mean I did not have to modify only the configure script but lots other places. I'll update the whole sheebag; will bet back with the link.

Winfile

https://github.com/Microsoft/winfile was open source recently, so I built it for rt.

It doesnt ran under WinRT8.1 with same error like WinDjView "number 1566 didn't fnd in the library". Rebuilded new one WinDjView with leaked MFC from VS2001beta works well (with some limitation). Please research this bug. I need an 2window file manager for my RT. How can I help ya?

any chance to get the error as shown in the English ui? would be more familiar to me.
I don't think this project uses mfc.
my guess is some linked dll has an ordinal of 1566 which moved in the dll between rt8.0 and rt8.1. if i get some time I'll recreate the libs from custom def and avoid including ordinal values, so the linker will be forced to load by symbol name.
a note to remind myself how to do that:
lib.exe /def:libfile.def /out:libfile.lib

Please look at there its my opened issue
https://github.com/Microsoft/winfile/issues/6
Unfortunately even when I install English UI some parts of UI still in prenstalled language (Russian in my case) ecen when it sets to English and reboot. This error is still in Russain and Im not sure how it sounds correctly in English.

hooddy said:
Please look at there its my opened issue
https://github.com/Microsoft/winfile/issues/6
Unfortunately even when I install English UI some parts of UI still in prenstalled language (Russian in my case) ecen when it sets to English and reboot. This error is still in Russain and Im not sure how it sounds correctly in English.
Click to expand...
Click to collapse
Privet! Yes, thanks, I am in that github thread also.
Please try this one if you have the time and willingness.
TLDR; Made libs without ordinals to force the system to load libraries and symbols by name. Based upon your error message containing a numerical value and not knowing whether the system will fail if incorrect ordinal or will retry by name.
Steps to produce are different from these: http://www.wanderinghuman.com/blog/archives/000123.html
In addition to that workspace, here's the changes:
Linked without each library individually to see which symbols were used
For each library
created a library.def file with the missing symbols obtained from linked errors
used this command: lib /def:library.def /out:library.lib /MACHINE:ARM
If First time;Observed linker error on resulting library about 0x1c0 (MACHINE:ARM) and remembered that's the Windows CE ARM thumb1
Hex edited library.lib to replace 0x1c0 with 0x1c4 (THUMB2) where relevant
end
Adjusted linker properties to hard code my libraries, so it didn't search default libraries.
Linked and produced what is attached here.
Edit, had typo in a def file, so fixing binary after fixing it/

smb_gaiden said:
any chance to get the error as shown in the English ui? would be more familiar to me.
I don't think this project uses mfc.
my guess is some linked dll has an ordinal of 1566 which moved in the dll between rt8.0 and rt8.1. if i get some time I'll recreate the libs from custom def and avoid including ordinal values, so the linker will be forced to load by symbol name.
a note to remind myself how to do that:
lib.exe /def:libfile.def /out:libfile.lib
Click to expand...
Click to collapse
NEVER LINK WITH ORDINALS, JUST NEVER. That made me lose a metric ton of time reporting stuff which was already ported to RT otherwise. It's a very bad idea, it's worse having builds with ordinals than no builds at all; a fixed version is attached by the way.
Why are you doing it by generating .libs? that's not required anymore, just add the ARM desktop SDK in individual components on VSinstaller

black_blob said:
NEVER LINK WITH ORDINALS, JUST NEVER. That made me lose a metric ton of time reporting stuff which was already ported to RT otherwise. It's a very bad idea, it's worse having builds with ordinals than no builds at all; a fixed version is attached by the way
Click to expand...
Click to collapse
Thanks for the build. I miss some dll to run it. Can ya share it please?
And please share your Far manager build. I really miss them.

smb_gaiden said:
Privet! Yes, thanks, I am in that github thread also.
Please try this one if you have the time and willingness.
TLDR; Made libs without ordinals to force the system to load libraries and symbols by name. Based upon your error message containing a numerical value and not knowing whether the system will fail if incorrect ordinal or will retry by name.
Steps to produce are different from these: http://www.wanderinghuman.com/blog/archives/000123.html
In addition to that workspace, here's the changes:
Linked without each library individually to see which symbols were used
For each library
created a library.def file with the missing symbols obtained from linked errors
used this command: lib /def:library.def /out:library.lib /MACHINE:ARM
If First time;Observed linker error on resulting library about 0x1c0 (MACHINE:ARM) and remembered that's the Windows CE ARM thumb1
Hex edited library.lib to replace 0x1c0 with 0x1c4 (THUMB2) where relevant
end
Adjusted linker properties to hard code my libraries, so it didn't search default libraries.
Linked and produced what is attached here.
Edit, had typo in a def file, so fixing binary after fixing it/
Click to expand...
Click to collapse
Privet! Ill try this new build and it's not workd with the same error as early was. What about all you write there I not really undasttod what can I do for you to improve it Im sorry for my stupidility(((

black_blob
can you tell me more about that please?

hooddy said:
Privet! Ill try this new build and it's not workd with the same error as early was. What about all you write there I not really undasttod what can I do for you to improve it Im sorry for my stupidility(((
Click to expand...
Click to collapse
you'll have to install the ucrt compatibility update
smb_gaiden said:
black_blob
can you tell me more about that please?
Click to expand...
Click to collapse
Windows 10 SDKs for VS2017 have the full set of ARM .libs these days. Set the SDK version to 10.0.16299

black_blob said:
you'll have to install the ucrt compatibility update
Click to expand...
Click to collapse
Where I can get it? Some msu file please. I try to obtain this dll form powershell and dot.net at github with no luck.

@black_blob thank you
@hooddy don't try to understand, just some development information.

smb_gaiden said:
@black_blob thank you
@hooddy don't try to understand, just some development information.
Click to expand...
Click to collapse
I thinks it's an https://support.microsoft.com/en-us/help/3118401/update-for-universal-c-runtime-in-windows I didn't get it over WU. Can ya share direct link for KB3118401 and KB2919355 msu for WinRT please?

Maybe this can help to build proper
https://github.com/Microsoft/winfile/issues/102

Well how about working RT build? Nope?

hooddy said:
Well how about working RT build? Nope?
Click to expand...
Click to collapse
Ended up choosing the nuclear option, and that seems to work alright.

black_blob said:
Ended up choosing the nuclear option, and that seems to work alright.
Click to expand...
Click to collapse
Ya make my day! Thank ya really much!

black_blob said:
Ended up choosing the nuclear option, and that seems to work alright.
Click to expand...
Click to collapse
Oh cool, you saved my future self some time! I ordered a surface RT in order to run 8.1 and leave my main one undisturbed. However, still have some work to do elsewhere, so can you elaborate on the nuclear option in order to save my future self more time? Thank you very much!

Static linking for everything + LTCG + removal of all unused code. It ends up working so well that it has the same size as the binary with outside depends.

I got my new (used) surface rt a few days ago, spent 3 days discovering the service pack update black screen error, installing all the service packs, then using the tool provided by Qiangong et. all.
Reproduced the error with my Winfile and realised that there was one critical library that was being linked with ordinals. Drum roll... kernel32.lib due to not using /NODEFAULTLIBS.
Anyway, it has been corrected and attached is a dynamically linked winfile.exe which runs on Windows RT 8.1. It has already been signed.

Build Android 11 from source

Hi, I'm trying to build Android 11. When I run the command
repo sync
I obtai the error
fatal: remove-project element specifies non-existent project: platform/prebuilts/gcc/darwin-x86/mips/mips64el-linux-android-4.9
What it means? How can I resolve it?
Many thanks

Check this report from GitHub. It doesn't look like a big deal. Maybe missing resources/files that you probably don't need if you are building an OS for a phone.
I see they simple removed a line from local_manifests/untracked.xml of which contains the error.

Hi, many thanks for your reply. I have removed more than 10 lines from the xml files.
Is it a normal behaviour? Why the files are not correct?

denisgottardello said:
Hi, many thanks for your reply. I have removed more than 10 lines from the xml files.
Is it a normal behaviour? Why the files are not correct?
Click to expand...
Click to collapse
I didn't find a direct answer. But I've searched the errors, and found that your error on the OP has a darwin-x86 on it.
So I did Google that, and found that it is an Operating System that has something to do with Mac OS, released in 2000, still active.
So as the errors of other builders. I noticed that they're building an OS for mobile phones, which does not include, for an example, darwin-x86. So I asked myself .. What's the point of including an arch that you won't need?
I think when you're building the OS, you do export the arch you're targeting, right? So did it include darwin-x86?