Related
There were quite a few builds around I have noticed, however with Tiad gone, there only seems to be the basic FRX* and GBX0A.
Even though I never liked "Tiad's" builds, I noticed quite a few things. With little/no coding experience (as far as I can tell) he was just modifying parts of code, causing problems, etc. But still making some huge UI changes that never seemed to have issues.
I have quite a bit of coding experience but never anything for mobile devices I would like to have a look and compile some builds, teaching myself basically.
So I have two questions regarding this:
1: Do the devs use an IRC or something? I would love to sit in on development and see how they work (without interrupting them of course ).
2: Is there some kind of 'cooking' software or a suite that has been put together, like some of the stuff I have seen in the Windows section for this device? Where do I start? I have seen the Chef Central but it is a bit 'full on' and seems to be a mess. I want to be device specific, if possible. Do I use THIS?
Oh and considering I own a RHOD110 (GSM) I am up for testing pretty much anything you guys want me to.
Who knows, by the time android is working I might be up for releasing public builds, and of course NO INCLUDED PAID APPS
ryannathans said:
There were quite a few builds around I have noticed, however with Tiad gone, there only seems to be the basic FRX* and GBX0A.
Even though I never liked "Tiad's" builds, I noticed quite a few things. With little/no coding experience (as far as I can tell) he was just modifying parts of code, causing problems, etc.
I have quite a bit of coding experience but never anything for mobile devices I would like to have a look and compile some builds, teaching myself basically.
So I have two questions regarding this:
1: Do the devs use an IRC or something? I would love to sit in on development and see how they work (without interrupting them of course ).
2: Is there some kind of 'cooking' software or a suite that has been put together, like some of the stuff I have seen in the Windows section for this device? Where do I start? I have seen the Chef Central but it is a bit 'full on' and seems to be a mess. I want to be device specific, if possible. Do I use THIS?
Oh and considering I own a RHOD110 (GSM) I am up for testing pretty much anything you guys want me to.
Who knows, by the time android is working I might be up for releasing public builds, and of course NO INCLUDED PAID APPS
Click to expand...
Click to collapse
Kernel Dev: http://htc-linux.org/wiki/index.php?title=IRC
Userland Dev: http://xdandroid.com/wiki/Chat
Steps for building stuff: http://forum.ppcgeeks.com/android-t...modules-tinboot-nand-boot-more-beginners.html
You can also find steps for building userland at xdandroid.com
Specifically, for building xdandroid - http://xdandroid.com/wiki/Getting_the_Source
If you follow those instructions, you will basically be able to build your own FRX05/GBX0A equivalents.
That's how I got started on my GPS quest.
Note that in terms of IRC channels, the two links above will eventually just take you to Freenode, so you can just go over to #htc-linux and #xdandroid on freenode. Activity seems to be highest in United States evening times. It can be quite dead at other times, as occasional people who have popped in to ask questions have discovered.
In terms of what goes into the mainline xdandroid codebase - ideally I would assume the devs wish to integrate whatever they can, however, I can see the following valid reasons to diverge:
1) Replacing large parts of the user interface (Sense, heavily themed builds) - This was one of the things tiad8 did and honestly not a part of his work that I had any problems with.
2) Situations where there is a free but binary-only component that replaces one of our open source components - Not ideal but sometimes a necessary evil for the end user. However, I think the mainline devs would appreciate knowing the situations in which this is done, either for the purposes of reverse engineering the component in question, finding a source tree for the component in question (sometimes possible), or just knowing whether or not a fix can be integrated upstream. - tiad8 would often grab stuff from random places without documenting it which annoyed a lot of people
Trying to minimize the deltas between "cooked" builds and what one might call the "baseline" build is probably what is best for all of us - only diverge when there is a clear rationale for it, and when there isn't a good reason for divergence, try to get stuff mainlined.
Also to note - when running from SD it isn't exactly "ROM" development, and the nice thing about running from SD is that it's a lot easier to make tweaks to userland since the key userland files are all in a normal ext2 filesystem.
Oh yeah - HIGHLY beneficial if you've got a 64-bit Linux box like I do!
Edit: If you read my GPS testing thread, you'll see some of the lessons learned on my journey, including a few useful tips like bind-mounting specific libs that you're working on.
Entropy512 said:
Specifically, for building xdandroid - http://xdandroid.com/wiki/Getting_the_Source
If you follow those instructions, you will basically be able to build your own FRX05/GBX0A equivalents.
That's how I got started on my GPS quest.
Note that in terms of IRC channels, the two links above will eventually just take you to Freenode, so you can just go over to #htc-linux and #xdandroid on freenode. Activity seems to be highest in United States evening times. It can be quite dead at other times, as occasional people who have popped in to ask questions have discovered.
In terms of what goes into the mainline xdandroid codebase - ideally I would assume the devs wish to integrate whatever they can, however, I can see the following valid reasons to diverge:
1) Replacing large parts of the user interface (Sense, heavily themed builds) - This was one of the things tiad8 did and honestly not a part of his work that I had any problems with.
2) Situations where there is a free but binary-only component that replaces one of our open source components - Not ideal but sometimes a necessary evil for the end user. However, I think the mainline devs would appreciate knowing the situations in which this is done, either for the purposes of reverse engineering the component in question, finding a source tree for the component in question (sometimes possible), or just knowing whether or not a fix can be integrated upstream. - tiad8 would often grab stuff from random places without documenting it which annoyed a lot of people
Trying to minimize the deltas between "cooked" builds and what one might call the "baseline" build is probably what is best for all of us - only diverge when there is a clear rationale for it, and when there isn't a good reason for divergence, try to get stuff mainlined.
Also to note - when running from SD it isn't exactly "ROM" development, and the nice thing about running from SD is that it's a lot easier to make tweaks to userland since the key userland files are all in a normal ext2 filesystem.
Oh yeah - HIGHLY beneficial if you've got a 64-bit Linux box like I do!
Edit: If you read my GPS testing thread, you'll see some of the lessons learned on my journey, including a few useful tips like bind-mounting specific libs that you're working on.
Click to expand...
Click to collapse
Sweet, yeah I will definitely be having a look at all resources. I DO have a 64bit Linux box, what is so beneficial? Can I achieve the same with a 64bit Virtual PC (providing I can allocate 4gb+ RAM which shouldn't be a problem on my beast )?
When I change or include anything I definitely want to include a list of all sources and information available to make sure the use is aware of what is going on. I never really like 'closed-source' development, as some of you may have seen with the Gaming Association I founded (all our mods are open source ).
Thanks, I will post again here if I need anything.
I think some of the prebuilt tools are 64-bit binaries. It's likely possible to get it working on a 32-bit box, but all of the documentation I've seen either strongly recommends/requires 64.
A VM should work fine - I think a few people are using that approach. Memory requirements aren't too bad unless you're doing a make -j4 on a quadcore - then you might drive into swap with a 4GB machine (I have...)
Entropy512 said:
I think some of the prebuilt tools are 64-bit binaries. It's likely possible to get it working on a 32-bit box, but all of the documentation I've seen either strongly recommends/requires 64.
A VM should work fine - I think a few people are using that approach. Memory requirements aren't too bad unless you're doing a make -j4 on a quadcore - then you might drive into swap with a 4GB machine (I have...)
Click to expand...
Click to collapse
I have an i5 750 OCed to 4Ghz, it is in fact a quad. Only 4GB RAM atm but very soon i will have 8
It is running a git clone command, downloaded 40 mb already and it is only 5%, oh great... xD haha
Trying to download and getting this error.
Code:
[email protected] ~ $ sudo apt-get install git build-essential gnupg flex bison gperf libsdl-dev esound zip curl libwxgtk2.6 libc6-dev-i386 g++-multilib lib32z1-dev lib32ncurses5-dev java-common openjdk-6-jdk sun-java5-jdk
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libsdl1.2-dev' instead of 'libsdl-dev'
Note, selecting 'libwxgtk2.6-0' for regex 'libwxgtk2.6'
Note, selecting 'libwxgtk2.6-dbg' for regex 'libwxgtk2.6'
Note, selecting 'libwxgtk2.6-dev' for regex 'libwxgtk2.6'
Note, selecting 'libwxgtk2.6-0-python' for regex 'libwxgtk2.6'
E: Unable to locate package libc6-dev-i386
E: Unable to locate package lib32z1-dev
E: Unable to locate package lib32ncurses5-dev
ryannathans said:
Trying to download perquisites and getting this error.
Click to expand...
Click to collapse
Have you tried to add a repository
Code:
add-apt-repository "deb http://archive.canonical.com/ maverick partner"
?
still getting the same error, however, when updating the list of updates, quite a few 'ign' or 'fail' but still most 'hit'.
Is everyone getting this error? It is happening on all my machines..
Don't remember encountering that error when I was getting set up...
I'm on Ubuntu 10.10 - you?
Entropy512 said:
Don't remember encountering that error when I was getting set up...
I'm on Ubuntu 10.10 - you?
Click to expand...
Click to collapse
Linux Mint 10 Gnome
Derived from Ubuntu 10.10, therefore both depositories should work.
Do you know what depository it is from?
From what I remember, I only had to add special repos for Java 5.
I do remember that back when I did it, there were some libs missing from the install directions in the wiki, that caused my build to bomb. I had to do some googling to find out what they were, and I THINK they were the ones you are having a problem with... hmm. Lemme do some more poking.
Edit: Try the prerequisites setup hints at http://source.android.com/source/download.html
Entropy512 said:
From what I remember, I only had to add special repos for Java 5.
I do remember that back when I did it, there were some libs missing from the install directions in the wiki, that caused my build to bomb. I had to do some googling to find out what they were, and I THINK they were the ones you are having a problem with... hmm. Lemme do some more poking.
Edit: Try the prerequisites setup hints at http://source.android.com/source/download.html
Click to expand...
Click to collapse
First repository worked but the other failed.
Code:
[email protected] ~ $ sudo add-apt-repository "deb-src http://archive.canonical.com/ubuntu lucid partner"
Error: 'deb-src http://archive.canonical.com/ubuntu lucid partner' invalid
I just removed -src and it accepted it, however I still get the same error with apt-get install as i did before
ill just install ubuntu instead...
and SAME error D:
Weird... I need to run out the door soon, but when I get home (going to be fairly late tonight) I'll try to look at my current repo setup.
Entropy512 said:
Weird... I need to run out the door soon, but when I get home (going to be fairly late tonight) I'll try to look at my current repo setup.
Click to expand...
Click to collapse
thanks Entropy
Uh yeah... anyway so what happened with that?
Entropy512 said:
Try the prerequisites setup hints at http://source.android.com/source/download.html
Click to expand...
Click to collapse
That's how I got the error.
I went on to...
Code:
sudo apt-get update
sudo apt-get install sun-java6-jdk
Things seem to be working fine for me.
Will post if anything changes... Ubuntu 10.10 x64
Getting errors about the update commands but repo is running fine. and javac points to where I tell it to via:
Code:
sudo update-java-alternatives -s java-1.5.0-sun
I suggest you continue to advance the installation until you run into a build problem, That will make an issue easier to resolve. Also... These issues should be posted/googled in a linux forum relevant to your distro.
Avid Droidery said:
Uh yeah... anyway so what happened with that?
Click to expand...
Click to collapse
Entropy helped me over IRC
libwxgtk2.6 could not be found via apt-get but libwxgtk2.6-0 was found and installed/works perfectly
should this be updated on the wiki?
ryannathans said:
should this be updated on the wiki?
Click to expand...
Click to collapse
I give you and Entropy my thanks and the thumbs up! As for your question, I am sure this is an installation issue specific to a certain platform. This would be relevant knowledge to any Wiki engaged in the topic.
- Keep up the great work!
https://wiki.ubuntu.com/ARM/TEGRA/AC100
"Adobe Flash
Dropping this library into ~/.mozilla/plugins allows flash playback. It warns though that it is out of date. http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so"
Sounds great! =)
I did put this new Ubuntu Image on my AC100, however some things don't work:
* ppa ac100 produces error 404, package ac100-settings isn't found
* high background load, virtually unusable
* no shortcuts (old Imgae did support)
* no suspend (crashes), no sound yet
* did not get flash to work with above plugin
Anyone ha dmore success?
The flash plugin (even only playback) of this Ubuntu doesn't work for my Linux
Ubuntu 11.10 x Folio100?
Hi,
On http://cdimage.ubuntu.com/releases/oneiric/beta-2/ there is a "Preinstalled desktop filesystem archive" for Toshiba AC100. Is it possible to use drivers used in http://forum.xda-developers.com/showthread.php?t=907960 to prepare a version for Folio 100?
Thanks.
semonma said:
The flash plugin (even only playback) of this Ubuntu doesn't work for my Linux
Click to expand...
Click to collapse
I found a solution, now I have flash in Chromium. Doesn't work in Firefox (probably because I am running Version 7).
Instructions:
put the libflashplayer.so in the Chromium plugin directory (/usr/lib/chromium-browser/plugins), easiest way is by wget command:
sudo wget -O /usr/lib/chromium-browser/plugins/libflashplayer.so http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so
install nvidea-tegra package
as it is not in the Oneiric repository yet I pulled this .deb and installed it via gdebi:
http://ppa.launchpad.net/ac100/ppa/...dia-tegra_12-0ubuntu1~alpha1monson6_armel.deb
I have no idea whether this is correct or latest, but it works to some extend.
Run chromium with
chromium-browser --allow-outdated-plugins
otherwise you get warning
360p Youtube runs smooth but when fullscreen has some slight lags, above resolutions do stutter.
Edit:
Here are some .deb packages of the main developer that seem to be newer. Did not test that. See the Readme: http://people.debian.org/~jak/ac100/README
Edit2:
With Beta 2 image and newest kernel (2.6.38-1000-ac100) the AC100 got quite usable now, sound via headphone works and performance bugs are largely reduced. Still some deadlocks by mmcd. Switching from ext4 to nilfs2 might yield some performance gain? And Debian hf, utilizing the Tegra FPU, also sounds promising.
Thank's a lot pibach, I'll try it this night =)
Brief update:
I added the developer ppa in sources list:
deb http://people.debian.org/~jak/ac100/ unreleased main non-free
and installed the package: xserver-xorg-video-tegra
it pulls in the package tegra-libraries
However I don't see any difference in video performace
nvidia-tegra package is not in there, package is stil unchanged
sudo apt-show-versions nvidia-tegra
nvidia-tegra 12-0ubuntu1~alpha1monson6 installed: No available version in archive
It is from this ppa: https://launchpad.net/~ac100/+archive/ppa
Seemingly this is for natty, does not seamlessly work with oneiric (Error 404 when added to sources.list as ):
"Changelog
nvidia-graphics-drivers-tegra (12-0ubuntu1~alpha1monson6) natty; urgency=low
* sigh, and build for the right release, oneiric doesnt work yet ...
-- Oliver Grawert <email address hidden> Tue, 05 Jul 2011 17:55:42 +0200"
However, it does work. Strange.
When I remove that nvidia-tegra package, I get some screen artefacts. Video then plays but very slow
Moreover, I can't find any xorg.conf file to set bit depth to 16 as mentioned in the Unbuntu Wiki.
So any chance to get better video (>360p) and maybe some HTML rendering boost?
Another hint: I got problems with Unity, Dash, Software Center bugging the CPU into performance problems, seems to be some memory lock with mmcd. Chromium 13 is also a lot faster, especially scrolling speed, than firefox 7 (both on smooth scrolling). But also runs into memory / CPU overload. Switching to lubuntu made all much snappier. It requires just 1 command:
sudo apt-get install lubuntu-desktop
and reboot into that one.
Maximus serves to undecorate the maximized windows -> more screen space
pibach said:
Moreover, I can't find any xorg.conf file to set bit depth to 16 as mentioned in the Unbuntu Wiki.
Click to expand...
Click to collapse
Thats probably because linux uses udev and dbus these days to detect your hardware on the fly when you start x.
Sent from my Folio 100 using xda premium
shidima_101 said:
Thats probably because linux uses udev and dbus these days to detect your hardware on the fly when you start x.
Click to expand...
Click to collapse
Yes, you're right. But that how it is described in the official ubuntu Wikipage. Strange. I have no glue how to do that nvidia tegra configuration.
When I launch Chromium-browser from terminal I get a lot of these errors:
ERROR:gl_surface_glx.cc(121)] glxQueryVersion failed
ERROR:gl_surface_linux.cc(73)] GLSurfaceGLX::InitializeOneOff failed.
So seemingly GLX Tegra hardware acceleration is not right.
BTW, the people at Arch Linux have more recent kernel and are on the status that suspend is working fine. Plus zram support there to come. See this thread. Don't know to what extend this will make the device snappier. Mine runs already quite snappy under LXDE.
I think with Linux on it the AC100 it is currently one of the best devices around. And you can get it quite cheap.
Edit:
On boot I usually get the error: unity support test closed unexpectedly
Probably something with GLX
Tegra shouldn't have any problems running Unity or Compiz.
Anybody got this to work propperly?
Edit2:
Launching Chromium in terminal:
chromium-browser --allow-outdated-plugins --use-gl=egl --ignore-gpu-blacklist
I get:
libEGL warning: GLX/DRI2 is not supported
To give you a brief status update:
I got suspend/resume to work
Flash works now in Firefox 7.0.1 (was already working in Chrome)
There seem to be a lot of work put into Ubuntu Oneiric and it's ARM version currently and it seems to be quite stable now.
On Folio100?
Is it usable on Folio 100?
The difference is only thouchscreen and Linux was already working (http://forum.xda-developers.com/showthread.php?t=907960).
Thanks.
gipposat said:
Is it usable on Folio 100?
The difference is only thouchscreen and Linux was already working (http://forum.xda-developers.com/showthread.php?t=907960).
Thanks.
Click to expand...
Click to collapse
but also Sound, Keyboard, NvEc, USB all might be slightly different. Isn't it?
pibach said:
but also Sound, Keyboard, NvEc, USB all might be slightly different. Isn't it?
Click to expand...
Click to collapse
No, I think everything is the same.
Bye
So, has anyone already tried it on Folio?
OK, I've given it a try and the boot image doesn't work, it definitely needs some porting.
hello pibach, thank you for your time testing stuff so we can make it work at the first time.
i installed drivers to make it work with flash, and its nice but sometimes i get a bug (probably due to graphic drivers making the screen get alot of artifacts, and only solution is a reboot, still a proble,m, probably due to alpha stage driver (nvidia could put something out that works decently....)
also, you say this version uses ext4? that should get it a lower performance comparing to nilfs (which i was using with phh's version) maybe disabling the journal? dont really know, will look into it.
how about changing the governor to performance instead of demand?
also...what about an SD card install? with a class 10 card should be fast? any info? worth buying a card to do it?
@Oinquer:
a) I got artifacts too, but only on Unity. I am on LXDE now and that works fine. Don't know why though.
b) I think you can choose ext4 or nilfs2 as you like. Can you point me to some links regarding performance comparisons and some more background info? I would give it a try then.
c) governor can be changed, sure.
d) the android bootloader cannot load from SD. But there might be some solution to do so, don't know. Meanwhile it should be no problem to have dual boot from internal MMC, for example Linux from partition 6 and android from partition 5 (SOS).
hello,
back to you, im using lxde now and installing the driver, hope artifacts go away.
EXT4 as far as i know has some benefits and some disavantages over ext3 and some other filesystems (checked yesterday after post), so performance might not change enough to notice.
governor , did it yesterday to performance, have to check flash playback now, but im not seeing big change except in boot time, that seems a few seconds less.
SD card, last version from phh's could be installed in SD card...and ubuntu wiki from AC100 says that if theres a blank SD card in slot at installation it will ask if you want to install there...im pretty sure its possible, but my sd card is in the trash bin, and cant buy one now...
here im hoping for the FPU stuff for the ac100...its getting there!!! quite usable, theres also a fix to have sound from internal speakers in ac100DOTgrandouDOTnet
will try it after i got everything sorted.
thank you for taking your time.
Sound is working in Ubuntu Oneiric Kernel that is in the proposed repository, works for me, but sound does not wake up after suspend yet.
SD card/USB boot does not work with Androib bootloader that is also used for Ubuntu Oneiric standard install. So you need to find one that can support that. Ccurrently there isn't any solution for that around, AFAIK. But you can put Linux on partition 6 and Android on Partition 5 and uses Android 2.1 bootloader.
This week's OTA update integrates Android M's latest security patch as well as Android-x86 rc2.
If you're new to Remix OS for PC, you can download it here: http://www.jide.com/remixos-for-pc#downloadNow
Here are the full release notes:
Remix OS for PC version: 3.0.201
Release date: August 16, 2016
Added latest Google Android M Security patch
Latest Android-x86 RC2 has been integrated and the highlighted features are as follows:
Fixed more Wi-Fi issues
Fixed more audio card loading issues
Fixed software rendering crashing issues on VM's like QEMU and VirtualBox
OTA support disabled if software was NOT installed by official Jide installer
Newly installed apps will have a small blue icon on it so they can be easily identified
As always, please give us your feedback here and help us continue to develop better!
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
Thanks!
I'm using 3.0.104, there is no ota update yet?
Sent from my Moto G using XDA Labs
Aguys said:
I'm using 3.0.104, there is no ota update yet?
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
@Aguys Can you check again? From our end, it looks good. Thanks for your patience!
Fresh install :
find --set-root --ignore-floppies /menu.lst
error 15: File not found
Remix folder injured I can not delete.
krystyan84 said:
Fresh install :
find --set-root --ignore-floppies /menu.lst
error 15: File not found
Remix folder injured I can not delete.
Click to expand...
Click to collapse
@krystyan84 - Are you using UEFI or Legacy boot? Can you send us feedback and a screenshot here?
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
Thanks!
krystyan84 said:
Fresh install :
find --set-root --ignore-floppies /menu.lst
error 15: File not found
Remix folder injured I can not delete.
Click to expand...
Click to collapse
Run chkdsk on the partition.
@RemixOS_Jason These OTAs seem to take 1-2 days to show up for me; are they rolled out by location?
RemixOS_Jason said:
@krystyan84 - Are you using UEFI or Legacy boot? Can you send us feedback and a screenshot here?
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
Thanks!
Click to expand...
Click to collapse
Sent :good:
Legacy boot Remix OS 3.0.201 (win10/remix dual boot 3.0.104 It worked well)
IMG
http://imgur.com/a/F1uZm
EDIT:
HypoTurtle:Run chkdsk on the partition.
This is interesting, chkdsk it was executed without error.
Reboot and Remix is boouted up :good:
krystyan84 said:
Sent :good:
Legacy boot Remix OS 3.0.201 (win10/remix dual boot 3.0.104 It worked well)
IMG
http://imgur.com/a/F1uZm
EDIT:
HypoTurtle:Run chkdsk on the partition.
This is interesting, chkdsk it was executed without error.
Reboot and Remix is boouted up :good:
Click to expand...
Click to collapse
In my case, when Remix OS running don't eject partition where Remix OS installed. If something wrong happens, that partition will not affected... CMIIW
Sent from my Moto G using XDA Labs
EDIT:
OTA update didn't work, I didn't wait and installed it once again on my Lenovo miix 700, but a HUGE DISAPPOINTMENT:
1) audio still not working (Realtek high definition audio),
2) no USB mount, it gives an error about a corrupted usb card.
3) YouTube doesn't work
4) kernel is not updated to 4.4.1.7
audio worked on Android x86 RC2
Any idea @RemixOS_Jason ?
Hi @RemixOS_Jason In my laptop, kernel verson is still 4.4.14 even after the update,Is it 4.4.17??? My update went fine and i'm on 3.0.201 now.
is over hdmi fixed? someone please try it.
KamaL said:
EDIT:
OTA update didn't work, I didn't wait and installed it once again on my Lenovo miix 700, but a HUGE DISAPPOINTMENT - audio still not working (Realtek high definition audio), no USB mount and now YouTube doesn't work.
audio worked on Android x86 RC2
Any idea @RemixOS_Jason
Click to expand...
Click to collapse
I thought your audio would be working with remix os since it's working on latest Android x86; that's very strange
Ludespeed said:
I thought your audio would be working with remix os since it's working on latest Android x86; that's very strange
Click to expand...
Click to collapse
unfortunately not... maybe because kernel isn't updated to the new version mentioned in the changelog
A clean install using Titanium Backup to restore apps. Very fast, smooth.
A few glitches:
1 phantom usb drive
2 no way to change the notifications
3 bluetooth doesn't work
still have the "sleep mode wake up hang" bug
KamaL said:
EDIT:
OTA update didn't work, I didn't wait and installed it once again on my Lenovo miix 700, but a HUGE DISAPPOINTMENT:
1) audio still not working (Realtek high definition audio),
2) no USB mount, it gives an error about a corrupted usb card.
3) YouTube doesn't work
4) kernel is not updated to 4.4.1.7
audio worked on Android x86 RC2
Any idea @RemixOS_Jason ?
Click to expand...
Click to collapse
1) audio still not working (Realtek high definition audio) - We are still working on more support for audio cards. Please be patient as this is still a continual work in progress.
2) no USB mount, it gives an error about a corrupted usb card - Our testers have shown that most external USB drives are supported. Can you send us your info through our user feedback form so we're aware of your specific device's issues? https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
3) YouTube doesn't work - I've been testing YouTube all day on my Remix OS for PC device. The app works fine. Watching on YouTube through Chrome has some issues, but on the whole, still works. Just not as well as the app. So, are you referring to the app or in browser experience?
4) kernel is not updated to 4.4.1.7 - I just checked with our PM and he stated that they're still testing this. Though we integrated rc2, this is one thing that was held back for testing to make sure it didn't affect overall system stability. However, stating it on the release notes was a mistake made on my part. There was miscommunication between myself and the PM and I listed this when it was still in our internal testing phase. I do apologize for this mistake and the confusion it may have caused!
HypoTurtle said:
Run chkdsk on the partition.
@RemixOS_Jason These OTAs seem to take 1-2 days to show up for me; are they rolled out by location?
Click to expand...
Click to collapse
@HypoTurtle It may be due to the servers in your location. Where are you writing to us from?
RemixOS_Jason said:
@HypoTurtle It may be due to the servers in your location. Where are you writing to us from?
Click to expand...
Click to collapse
The UK
where is the ota Update option in remix 3.0 32-bit , not find it.
RemixOS_Jason said:
1) audio still not working (Realtek high definition audio) - We are still working on more support for audio cards. Please be patient as this is still a continual work in progress.
2) no USB mount, it gives an error about a corrupted usb card - Our testers have shown that most external USB drives are supported. Can you send us your info through our user feedback form so we're aware of your specific device's issues? https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
3) YouTube doesn't work - I've been testing YouTube all day on my Remix OS for PC device. The app works fine. Watching on YouTube through Chrome has some issues, but on the whole, still works. Just not as well as the app. So, are you referring to the app or in browser experience?
4) kernel is not updated to 4.4.1.7 - I just checked with our PM and he stated that they're still testing this. Though we integrated rc2, this is one thing that was held back for testing to make sure it didn't affect overall system stability. However, stating it on the release notes was a mistake made on my part. There was miscommunication between myself and the PM and I listed this when it was still in our internal testing phase. I do apologize for this mistake and the confusion it may have caused!
Click to expand...
Click to collapse
Thank you for the detailed reply:
1) no audio - This is a popular sound card, and there are other threads on XDA and Google groups talking about this, so I hope it's high in your priority list. If you need me for any beta testing for this audio card, I'm in!
The fact that Android x86 RC2 has audio working gives hope it's not that difficult to implement it, right?
2) I was actually talking about a microSDXC card with exFAT format, a Kensington 64GB card, which doesn't mount. Is it a known bug?
3) Youtube doesn't work both using the standalone app and through browser. I don't know why.
4) This explains why it still shows the older kernel. Maybe this is the reason for missing audio???
Keep up the good work!!
"Blobs" are the files specific to each device that we need in order to compile custom ROMS that work on our device. The process of finding them is tedious and slow... I have been picking away at them for months when I have time. There are over 600 files so far! But there are also references to files that are not being found. They are either missing, or they are not located where they are expected to be located. This is where I need help.
So, if you want to help, go HERE:
https://github.com/mightysween/android_vendor_motorola_payton
and look through the proprietary-files.txt file for anywhere that it says "warning".... and then search inside of the firmware (working on 8.0+ now, not 7.1 please) and try to track down the file that it says is missing [obviously, you will need a system dump, or to search on a rooted device]. If you find it, please post below like this:
LINE NUMBER OF THE WARNING (from github)
PATH TO THE MISSING FILE (relative to /system... in other words, don't inlude your own local path)
Once this file is complete, we can use it to automatically pull the correct vendor files into our build environments... having a working recovery, active kernel developement and completed vendor blobs should open us up to more development efforts.
Also, if anyone has done any testing and knows of other proproetary files that are needed, please post them here so I can include them.
My time at the computer to work on this is really limited, so I have only identified a dozen or so daemons that definitely call for proprietary libs... I am sure there are more
I would love to pitch in on this but have zero experience with anything related to development. Do you think I could still be of help? Sounds like a basic enough task that it wouldn't be too difficult. Let me check and see that I understand the process.
Went to github and looked at proprietary-files.txt. The first warning I found was in line 49: "blob file libpn553_fw.so missing or broken". Then searched for that file in my device's system folder using ES File Explorer with Root Explorer enabled.
So is this what you're looking for?
49
/system/vendor/firmware/libpn553_fw.so
---------- Post added at 14:31 ---------- Previous post was at 14:07 ----------
I'd like to contribute in some way but if this is best not left to a complete noob then I totally understand
mightysween said:
Also, if anyone has done any testing and knows of other proproetary files that are needed, please post them here so I can include them.
My time at the computer to work on this is really limited, so I have only identified a dozen or so daemons that definitely call for proprietary libs... I am sure there are more
Click to expand...
Click to collapse
Do you have a link to a system dump?
TheBassDude said:
I would love to pitch in on this but have zero experience with anything related to development. Do you think I could still be of help? Sounds like a basic enough task that it wouldn't be too difficult. Let me check and see that I understand the process.
Went to github and looked at proprietary-files.txt. The first warning I found was in line 49: "blob file libpn553_fw.so missing or broken". Then searched for that file in my device's system folder using ES File Explorer with Root Explorer enabled.
So is this what you're looking for?
49
/system/vendor/firmware/libpn553_fw.so
---------- Post added at 14:31 ---------- Previous post was at 14:07 ----------
I'd like to contribute in some way but if this is best not left to a complete noob then I totally understand
Click to expand...
Click to collapse
Thanks, that is all there is to it
Just time consuming (especially after the first 500)...lol
QWZR said:
Do you have a link to a system dump?
Click to expand...
Click to collapse
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
mightysween said:
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
Click to expand...
Click to collapse
Mine gets here next week
mightysween said:
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
Click to expand...
Click to collapse
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
ebrandsberg said:
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
Click to expand...
Click to collapse
Any way that works is fine by me
I am on the road a lot and just don't have enough time to sit and work on it... so it is taking months. I bet a few people helping could finish it in a matter of hours.
I am hoping to have a few hours next week to work on it. But the sooner this is done, the sooner I can shift to trying to compile Lineage OS with working hardware.
BTW, Lineage *does* compile if I comment out all the stuff causing make errors... not much works, obviously.
The next step will be compiling with these blobs, then logging all the new errors and chasing down all the additional broken symlinks... and then adapting the kernel as needed.
Then, MAYBE we can get a base Lineage tree up and open up the X4 to building for other roms. I know someone started a skeleton tree for Carbon already on Github... they are likely just waiting for the completed device tree, too.
mightysween said:
Thanks, that is all there is to it
Just time consuming (especially after the first 500)...lol
Click to expand...
Click to collapse
ebrandsberg said:
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
Click to expand...
Click to collapse
I don't own this device yet, but I was thinking of getting one. I figured this might help you all out (you'll need to be running linux):
First, let's get a list of all the files on the phone, to make searching faster.
Code:
adb shell
su
find / > /sdcard/allfiles.txt
exit
exit
adb pull /sdcard/allfiles.txt
Now you should have allfiles.txt on your machine. Also grab the proprietary-files.txt, and then run this:
Code:
grep -Po '(?<=(blob file )).*(?= missing or broken)' proprietary-files.txt | xargs -I @ grep "@" allfiles.txt
That should find the paths of all the missing files (except the ones marked "wildcard")
BLuFeNiX said:
I don't own this device yet, but I was thinking of getting one. I figured this might help you all out (you'll need to be running linux):
First, let's get a list of all the files on the phone, to make searching faster.
Code:
adb shell
su
find / > /sdcard/allfiles.txt
exit
exit
adb pull /sdcard/allfiles.txt
Now you should have allfiles.txt on your machine. Also grab the proprietary-files.txt, and then run this:
Code:
grep -Po '(?<=(blob file )).*(?= missing or broken)' proprietary-files.txt | xargs -I @ grep "@" allfiles.txt
That should find the paths of all the missing files (except the ones marked "wildcard")
Click to expand...
Click to collapse
Thanks, I had recently completed this, but your code worked fantastic for double checking, and actually helped me find one that I had missed :good:
Now, on to identifying any more daemons that need proprietary files... and then assembling the tree itself... PROGRESS!
PHASE 1 is complete!
https://github.com/mightysween/android_vendor_motorola_payton
I am 99% sure that this is only ~75% of what will be needed to actually build LOS15. But it is a good foundation to work off of now.
My plan is to start attempting to compile LOS and take error logs to chase down the remaning missing stuff. LOTS to be done still to get to that point...hoping for some other builders/devs to materialize here and help out
Hi! Just a question: it´s mandatory to use A/B partition scheme to build a custom ROM for this device or it will be possible to use a traditional partition scheme and free up some GBs of internal storage for use?
christianrj said:
Hi! Just a question: it´s mandatory to use A/B partition scheme to build a custom ROM for this device or it will be possible to use a traditional partition scheme and free up some GBs of internal storage for use?
Click to expand...
Click to collapse
It would seem that we will still be stuck with A/B, as the bootloader does the initial check of the active slot. Perhaps there may be some clever ways around this in the future...but nothing I will be tackling.
mightysween said:
It would seem that we will still be stuck with A/B, as the bootloader does the initial check of the active slot. Perhaps there may be some clever ways around this in the future...but nothing I will be tackling.
Click to expand...
Click to collapse
You would probably need a custom kernel to do it properly. The bootloader passes a kernel param (androidboot.ro.boot.slot_suffix) specifying which slot to use. In the absense of a kernel param, the value is read from the ro.boot.slot_suffix build property.
That being said, you might be able to just repartition your device to only have 1 slot, flash your ROM, and use
Code:
fastboot --set-active=_a
. If your ROM has disabled OTA updates from the OEM, you should be fine.
I'm going to get an X4 in the coming weeks. I'd like to help with this soon. I'm a seasoned developer by trade and can collab on GitHub. Hope to be able to start working with you soon. :good:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Hariiiii said:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Click to expand...
Click to collapse
@vache at the Moto G5 Plus forums has already managed it using the /oem partition which is otherwise unused for custom ROMs
Hariiiii said:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Click to expand...
Click to collapse
Cool... seems it may be possible. Will follow the progress on the Redmi and G5 devices
navenedrob said:
I'm going to get an X4 in the coming weeks. I'd like to help with this soon. I'm a seasoned developer by trade and can collab on GitHub. Hope to be able to start working with you soon. :good:
Click to expand...
Click to collapse
The more I am reading about enabling Treble, the more I think it is entirely possible.... and probably the best direction to focus our efforts.
Seems like we have partitions that could be used as /vendor. I am reading up on exactly how the Treble vendor partition is set up. Tricky, but not implausible.
EDIT: Actually, none of the partitions we could potentially re-purpose for /vendor are big enough. So, it may be harder on this device than on others. It may require repartitioning.
Hello guys!
I'm starting this thread as I managed to install win10 on my X90L (Android) YogaBook
It was not easy to find a way to fix the ACPI error but it is possible!
Will update this post in a few hours with a guide on how to do it yourself.
UPDATE: link to the guide -> poz1.com/windows-on-android-lenovo-yogabook/
PLEASE NOTE THAT IF YOU CONTINUE YOU WILL END UP WITH A YOGABOOK WITHOUT INPUT DEVICES!!!
(EXTERNAL KEYBOARD WILL BE NEEDED) AND NO ANDROID INSTALL!!!
So far i got almost everything working except:
- Touchscreen
- Keyboard
- Webcam in the keyboard panel (the other one works fine)
- NFC
- Backlight Control (added 25/5/2018)
I'm getting very near to have the touch and the keyboard working though
P.s. In attach you find the outputs from 3DMark - IceStorm Extreme (default settings), would be much appreciated if someone with the real Win version shared its score
Any chance of posting you work to date. Got an X90F just crying out for Windows.
Broomfundel said:
Any chance of posting you work to date. Got an X90F just crying out for Windows.
Click to expand...
Click to collapse
I have added the link to the guide! If yo have any issues let me know but keep in mind that currently no input devices (touchscreen or keyboard) work!
Thanks for posting this. I am really so impressed. Will be trashing my X90F tomorrow. Just got to dig out a powered USB hub. Ill report back, and lets see what happens.
(Hopefully not a brick)
OK,
So far so good. I get to the amending of the of aml. But keep getting.
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation
iASL: Segmentation Fault
iASL: Terminating
To clarify the process. Decompile the DSTDroid.aml, then insert the OperationRegion (GNVS, SystemMemory, 0x7B3CF000, 0x0369)
Field (GNVS, AnyAcc, Lock, Preserve)
{ etc.. } section from the DSTDroid.dsl and use it to replace the equivalent section in the DSTWin.dsl in your files.
Then compile the DSTWin.dsl with the
iasli -ta DSDTWin.dsl
command.
This is how I am reading it, but have not managed to get it to work yet.
It decompiles with the two errors you mention, but wont recompile no matter how I try it.
I am using Notepadd++ so its not hidden characters.
Any thoughts, and thanks again for your efforts on this.
Broomfundel said:
OK,
So far so good. I get to the amending of the of aml. But keep getting.
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation
iASL: Segmentation Fault
iASL: Terminating
To clarify the process. Decompile the DSTDroid.aml, then insert the OperationRegion (GNVS, SystemMemory, 0x7B3CF000, 0x0369)
Field (GNVS, AnyAcc, Lock, Preserve)
{ etc.. } section from the DSTDroid.dsl and use it to replace the equivalent section in the DSTWin.dsl in your files.
Then compile the DSTWin.dsl with the
iasli -ta DSDTWin.dsl
command.
This is how I am reading it, but have not managed to get it to work yet.
It decompiles with the two errors you mention, but wont recompile no matter how I try it.
I am using Notepadd++ so its not hidden characters.
Any thoughts, and thanks again for your efforts on this.
Click to expand...
Click to collapse
Hello Broomfundel,
I never got that error, but it seems to be a problem of the ASL Compiler build not of your file.
I am using Mac so I have another build, if you want to post the file I can compile it for you .
Otherwise you can try an older release or to build the tool from source maybe?
Poz1 said:
Hello guys!
I'm starting this thread as I managed to install win10 on my X90L (Android) YogaBook
It was not easy to find a way to fix the ACPI error but it is possible!
Will update this post in a few hours with a guide on how to do it yourself.
UPDATE: link to the guide -> poz1.com/windows-on-android-lenovo-yogabook/
PLEASE NOTE THAT IF YOU CONTINUE YOU WILL END UP WITH A YOGABOOK WITHOUT INPUT DEVICES!!!
(EXTERNAL KEYBOARD WILL BE NEEDED) AND NO ANDROID INSTALL!!!
So far i got almost everything working except:
- Touchscreen
- Keyboard
- Webcam in the keyboard panel (the other one works fine)
- NFC
I'm getting very near to have the touch and the keyboard working though
Click to expand...
Click to collapse
Hi, i have the Lenovo Yoga Book Windows version, im crying to install Stock Android on it, can you PLZ write a guide about doing it, or at least if there is a way to install the kernelflinger.efi or the fastboot mode on YB windows it will be great.
to fix the whole bugs you faced, try to reinstall windows 10 using this methode https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Thanks
THE MAXIMUM POWER said:
Hi, i have the Lenovo Yoga Book Windows version, im crying to install Stock Android on it, can you PLZ write a guide about doing it, or at least if there is a way to install the kernelflinger.efi or the fastboot mode on YB windows it will be great.
to fix the whole bugs you faced, try to reinstall windows 10 using this methode https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Thanks
Click to expand...
Click to collapse
Hi,
KernelFlinger is opensource and come with an installer, it should be pretty simple to install it.
Right now I don't have my YogaBook as I am travelling but I can try in the next few days
OK, Older release worked, but I get a .hex file, your instructions talk about a new aml file. Do I use the .hex file or is there another option other than the -ta one that would create the aml.
BTW. I am enjoying this. So thanks again.
Broomfundel said:
OK, Older release worked, but I get a .hex file, your instructions talk about a new aml file. Do I use the .hex file or is there another option other than the -ta one that would create the aml.
BTW. I am enjoying this. So thanks again.
Click to expand...
Click to collapse
With the -ta option I get both the .hex and the .aml file but you can try -tc if it doesn't work. Maybe due to the different build
P.s. (for other people that may incur in this) If you don't get the output files check that you have as last line of the terminal
"Compilation complete. 0 Errors"
OK, I am getting 7 errors. My current theory is that the DSTDWin.dsl will only compile with the same version number of the compiler it was decompiled with. I have attached my DSDTDroid.dsl so you can have a go. At least it will prove I got things right up to that point. Might be worth posting the original DSTDWin.aml for me to try this end.
If we are lucky it might turn out that the patched DSTDWin.aml files are consistent across the same model devices.
So... It seems both pen mode and keyboard mode of holo keyboard won't work... Am I right?
It's sad that if they won't work even we install the drivers from the lenovo website
Poz1 said:
Hi,
KernelFlinger is opensource and come with an installer, it should be pretty simple to install it.
Right now I don't have my YogaBook as I am travelling but I can try in the next few days
Click to expand...
Click to collapse
can after installing Windows booting to kernelflinger? if you can make a thread about how can you install/reinstall kernelflinger will be amazing?
Thank you
Poz1 said:
Hello guys!
Click to expand...
Click to collapse
Have you tried with the ISO from this forum with the Windows injected drivers? Here https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
As Poz1 is obviously busy at the moment. Can anyone else get the DSTDWin.aml file for me to try and decode?
Thanks
Sorry guys I've been busy with university
Broomfundel said:
OK, I am getting 7 errors. My current theory is that the DSTDWin.dsl will only compile with the same version number of the compiler it was decompiled with. I have attached my DSDTDroid.dsl so you can have a go. At least it will prove I got things right up to that point. Might be worth posting the original DSTDWin.aml for me to try this end.
If we are lucky it might turn out that the patched DSTDWin.aml files are consistent across the same model devices.
Click to expand...
Click to collapse
There you go I'm also updating the files DSTDWin of my blog with one with some fixes Well they depend on the settings you use in your Bios (that's why Windows may not boot after install, it changes some parameters (the wait time of the bios and the default boot partition)). When you use the builtin one is the bios that "updates" it for you but for now we need to do it by hand If we are going to end with everything working we can release a patched "Win" bios and everything will be simpler
Riskypedia said:
So... It seems both pen mode and keyboard mode of holo keyboard won't work... Am I right?
It's sad that if they won't work even we install the drivers from the lenovo website
Click to expand...
Click to collapse
I know There something in the DSDT (the file that tells the os which and where your pc components are) that has to be fixed to make Windows see these parts correctly
THE MAXIMUM POWER said:
can after installing Windows booting to kernelflinger? if you can make a thread about how can you install/reinstall kernelflinger will be amazing?
Thank you
Click to expand...
Click to collapse
Didn't try Will do as soon as I have some free time :fingers-crossed:
Kinyapiplele said:
Have you tried with the ISO from this forum with the Windows injected drivers? Here https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Click to expand...
Click to collapse
Yep, but the problem is in the DSDT Thanks fot the input anyway
Poz1 said:
Sorry guys I've been busy with university
Click to expand...
Click to collapse
Don't worry, we all have real lives as well. I'm in the UK and we have a bank holiday on Monday. So this weekend, Ill get stuck in again.
Thanks for all your doing on this. You have already got further than anyone else who tried.
let me know if you have more problems
I have added a 3DMark test in the first post for those that are interested in how it performs
Poz1 said:
let me know if you have more problems
I have added a 3DMark test in the first post for those that are interested in how it performs
Click to expand...
Click to collapse
Just another Question, you as a Advance user, do you believe that we (yoga book Windows owners) can boot Android yb STOCK ROM ( i mean not the Android x86 based distros)?
Yes, but I think you would have to do the "reverse" DSDT injection (from win to android) as the official ROM has drivers for that components.
This means that, if you're lucky you would end up with our same problems (keyboard, pen and touch). If we don't fix that before
The problem with Android is that it is meant to be flashed on rom instead of being installed and this makes things more difficult.
It should be possible to flash the rom on an USB key, add grub and use it for DSDT injection like we do and see what happens.
Another problem is that the provided kernelflinger seems to have most of the security options enabled so 99% it will refuse to boot anyway.
Since it is opensource it should be possible to fix this anyway.
So yes, but it a loooong journey