[GUIDE] How to build Android 11 with low ram - Android Software Development

When building Android 11 on a device with low ram (typically under 16gb of ram), when you get to metalava compilation it will fail with the error "java.lang.OutOfMemoryError: Java heap space"
I found the below patch which fixes this and should allow you to build the rom on a machine with as little as 8gb of ram.
Code:
Lowram fix for R. Run this command in your rom root directory:
cd build/soong
git fetch https://github.com/masemoel/build_soong_legion-r 11
# Specify heap size for metalava for R
# Reduce initial heap size for java from 2048mb to 1024mb
git cherry-pick b45c5ae22f74f1bdbb9bfbdd06ecf7a25033c78b
# Tune java compiler flags for low ram systems
# This is needed on systems with 8GB physical ram.
# sets the max heap size for java to 3112mb
git cherry-pick e020f2130224fbdbec1f83e3adfd06a9764cca87
# soong will be rebuilt the next time you build anything in aosp
Thanks to masemoel for the patch

Project Sakura have merged this into their repo so if building that rom there should be no need to alter anything

TheFixItMan said:
When building Android 11 on a device with low ram (typically under 16gb of ram), when you get to metalava compilation it will fail with the error "java.lang.OutOfMemoryError: Java heap space"
I found the below patch which fixes this and should allow you to build the rom on a machine with as little as 8gb of ram.
Code:
Lowram fix for R. Run this command in your rom root directory:
cd build/soong
git fetch https://github.com/masemoel/build_soong_legion-r 11
# Specify heap size for metalava for R
# Reduce initial heap size for java from 2048mb to 1024mb
git cherry-pick b45c5ae22f74f1bdbb9bfbdd06ecf7a25033c78b
# Tune java compiler flags for low ram systems
# This is needed on systems with 8GB physical ram.
# sets the max heap size for java to 3112mb
git cherry-pick e020f2130224fbdbec1f83e3adfd06a9764cca87
# soong will be rebuilt the next time you build anything in aosp
Thanks to masemoel for the patch
Click to expand...
Click to collapse
any guide to build with 8gb??
and compiling A10 requirement of ram?

[email protected] said:
any guide to build with 8gb??
and compiling A10 requirement of ram?
Click to expand...
Click to collapse
Building is the same regardless of ram
This patch is to solve the issue of metalava running out of memory if your source rom doesn't already include this patch in soong on android 11
Android 10 uses a different build system which you can find the patch for here
https://review.lineageos.org/c/LineageOS/android_build_soong/+/266411/3/java/droiddoc.go#77

Will this only work for compiling lineageos or any other rom?
I'm trying to build pixel experience.

himanish25 said:
Will this only work for compiling lineageos or any other rom?
I'm trying to build pixel experience.
Click to expand...
Click to collapse
It will work with any rom that is android 11 based (assuming the patch hasn't already been applied)
It just adds the java value to soong. You can look in build/soong/java/droiddoc.go to see if the values are already there or not manually.

Does this still work? I have not applied the mentioned patch.
I have 14G of RAM in my Ubuntu 20.04 in virtual box. Still Android 11 compiling failing when it tries to build the kernel image. Building snoog works fine.
Does this fix my issue by applying the patch?
Also is there a similar patch for Android 12 compiling?

V T Vishwanath said:
Does this still work? I have not applied the mentioned patch.
I have 14G of RAM in my Ubuntu 20.04 in virtual box. Still Android 11 compiling failing when it tries to build the kernel image. Building snoog works fine.
Does this fix my issue by applying the patch?
Also is there a similar patch for Android 12 compiling?
Click to expand...
Click to collapse
This is specifically for soong metalava failing due to
java.lang.OutOfMemoryError: Java heap space
It will not fix any other compiling error
I do not know what changes were made to soong in android 12

The patch only needs to be applied once? Or after / before each repo sync? I have installed the patch but still get an error at the end:
Code:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at com.intellij.psi.impl.source.tree.JavaElementType$$Lambda$160/0x0000000100464840.get(Unknown Source)
at com.intellij.psi.impl.source.tree.JavaElementType$JavaCompositeElementType.createCompositeNode(JavaElementType.java:42)
at com.intellij.lang.ASTFactory.composite(ASTFactory.java:80)
at com.intellij.lang.impl.PsiBuilderImpl.createComposite(PsiBuilderImpl.java:1285)
at com.intellij.lang.impl.PsiBuilderImpl.bind(PsiBuilderImpl.java:1203)
at com.intellij.lang.impl.PsiBuilderImpl.buildTree(PsiBuilderImpl.java:919)
at com.intellij.lang.impl.PsiBuilderImpl.getTreeBuilt(PsiBuilderImpl.java:905)
at com.intellij.psi.impl.source.JavaFileElementType.parseContents(JavaFileElementType.java:82)
at com.intellij.psi.impl.source.tree.LazyParseableElement.lambda$ensureParsed$0(LazyParseableElement.java:206)
at com.intellij.psi.impl.source.tree.LazyParseableElement$$Lambda$216/0x00000001004f2840.run(Unknown Source)
at com.intellij.psi.impl.DebugUtil.performPsiModification(DebugUtil.java:553)
at com.intellij.psi.impl.source.tree.LazyParseableElement.ensureParsed(LazyParseableElement.java:205)
at com.intellij.psi.impl.source.tree.LazyParseableElement.getFirstChildNode(LazyParseableElement.java:254)
at com.intellij.psi.impl.source.tree.CompositeElement.countChildren(CompositeElement.java:449)
at com.intellij.psi.impl.source.tree.CompositeElement.getChildrenAsPsiElements(CompositeElement.java:411)
at com.intellij.psi.impl.source.PsiJavaFileBaseImpl.getClasses(PsiJavaFileBaseImpl.java:66)
at com.android.tools.metalava.model.psi.PsiBasedCodebase.initialize(PsiBasedCodebase.kt:137)
at com.android.tools.metalava.Driver.parseSources(Driver.kt:932)
at com.android.tools.metalava.Driver.parseSources$default(Driver.kt:901)
at com.android.tools.metalava.Driver.loadFromSources(Driver.kt:825)
at com.android.tools.metalava.Driver.processFlags(Driver.kt:235)
at com.android.tools.metalava.Driver.run(Driver.kt:118)
at com.android.tools.metalava.Driver.run$default(Driver.kt:100)
at com.android.tools.metalava.Driver.main(Driver.kt:86)
19:00:14 ninja failed with: exit status 1

TheFixItMan said:
This is specifically for soong metalava failing due to
java.lang.OutOfMemoryError: Java heap space
It will not fix any other compiling error
I do not know what changes were made to soong in android 12
Click to expand...
Click to collapse
Original author of the patch here, it does nothing by the way, thats why I abandoned it. https://review.lineageos.org/c/LineageOS/android_build_soong/+/262657/4

It doesn't work on Android 12 but there's still a way, I have compiled Android 12 with 8gb RAM and 12gb swap.
- In build/soong/java/droidstubs.go find :
cmd.BuiltTool("metalava").ImplicitTool(ctx.Config().HostJavaToolPath(ctx, "metalava.jar")).
- Now after :
Flag(config.JavacVmFlags).
- Add ::
Flag("-J-Xmx6114m").
Or whatever value you want.
Then it works.
In my case I didn't need to change the values in makevars.go and config.go but you may have to depending on your computer.
Good luck guys!!!

jolebaltringue said:
It doesn't work on Android 12 but there's still a way, I have compiled Android 12 with 8gb RAM and 12gb swap.
- In build/soong/java/droidstubs.go find :
cmd.BuiltTool("metalava").ImplicitTool(ctx.Config().HostJavaToolPath(ctx, "metalava.jar")).
- Now after :
Flag(config.JavacVmFlags).
- Add ::
Flag("-J-Xmx6114m").
Or whatever value you want.
Then it works.
In my case I didn't need to change the values in makevars.go and config.go but you may have to depending on your computer.
Good luck guys!!!
Click to expand...
Click to collapse
How long did it take you to complete the compile?
(I want to do that too)

Hello
Does it work for A12 builds also ?

I compiled Android x86_64 r-x86 and LinageOS nougat-x86 (cm 14.1) version with a Dell inspiron 3847 (quad core i5 -4460 , with 12 gb of ram... and 12.5gb of swap space lol) on Ubuntu Server 22.04 LTS. minimal install option.
I installed zram-config first.
I'm kinda dumb and i set up my partition with 250 gb 239 available to me.... so I ran out of space a couple of times and failed building the iso to another drive
i ended up doing --depth=1 on my repo init and repo sync - c to get the folder size down to 80 gb!!!! and finished up the build on one dive.
I did the nougat first and it took me a few days figuring out the right packages and env variables because i was following a couple of diffent guides lol . so i didn't really see how long it took me to compile the whole thing when i got it working... maybe 6.5 hours....
I did the export _JAVA_OPTIONS="-Xmx4g" thing but i don't think it stuck because I restarted my machine once and i didn't add it to a start up script and i don't think i put it in again on my finishing attempt.
Doing Android r-x86 was easy once i had the packages in place and switched my python back to v3. Compile time was like 9.25 hours...
oh i did m -j3 or m -j2 when building , so I didn't really go full tilt....
If I had give some one advice is prob start out with 300 gb or more... prob more on your partition.
And read the official google guide to setting up ur system first.. I kinda ignored warnings and just skimmed Android x86 site guide plus alot of googling of errors.
Oh maybe it would be worth trying a free trial of cloud computing.... sigh..

Related

[Discussion]Linux and Android on the HD2 *READ POST3 BEFORE ASKING QUESTIONS*

Development thread for Linux on the HTC HD2
PLEASE READ THE FAQ BEFORE POSTING QUESTIONS
Introduction:
To run any Linux based user space on a device -this includes android, debian, ubuntu, openembedded, etc- you need a working Linux kernel.
This thread discusses the development on Linux kernel and user space on the HTC HD2.
All android ports to windows phones are based on the efforts of porting the Linux kernel to these devices. This is what all the porting is about. Nobody is porting Google Android to these phones. It works already.
Contributing:
This is not a secret club. All source code and development information is publicly available. Everybody who is willing to contribute is free to join the development process.
People working on porting Linux to HD2:
You can donate to the developers putting a lot of time into this Linux kernel port.
(putting together android files (=>making "roms") is not the porting)
cr2
NetRipper
dcordes
Markinus
LeTama
Cotulla
dan1j3l
Parad0XUA
manusfreedom
Technical information for interested people:
General Developer Information:
http://htc-linux.org/
Leo/HD2 Wikipage
http://htc-linux.org/wiki/index.php?title=Leo
Leo/HD2 Linux Kernel:
git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git htc-msm-2.6.32
gitweb: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
Patches welcome!!
How to compile the Kernel:
http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel
=> use htc-msm-2.6.32 branch and htcleo machine type
How to contribute: (Please be aware that this is primarily for developers!)
http://htc-linux.org/wiki/index.php?title=Contact
Newsflash:
Check http://twitter.com/htc_linux for extra quick news
03/24/2010 compass working, battery monitor added
03/26/2010 moved to new htc-msm-2.6.32 branch
03/29/2010 don't use ondemand governor
04/01/2010 add ext3
04/05/2010 dex, rtc, battery monitor, merged with google updates
04/08/2010 naming and pm changes, timer problem is fixed (other low level problems still exist)
04/09/2010 memory remapped
04/14/2010 clock updates
05/01/2010 the cause for the segmentation faults is still unknown. a new kernel was added based on codeaurora (see Leo kernel link 1st post)
05/13/2010 update Image build with latest (minor) changes.
05/19/2010 vfp/neon enabled in the 2.6.32.9 kernel. built with gcc-4.4.4 cross toolchain
05/20/2010 new video player demo added
06/02/2010 nothing new. but we are still working...
06/10/2010 more attention to segfault/illegal instruction problem on lkml
06/12/2010 usb host mode works perfectly. patches and build following
06/12/2010 usb host mode changes committed, kernel build uploaded
06/20/2010 linux is booting on qsd8250 based acer s200 - let's see if same cpu crash problem can be observed
06/21/2010 same cpu crash on s200 - the problem is not specific to leo
06/23/2010 Cotulla discovered desire/bravo bootloader has some workaround for a qsd8250 CPU hardware bug..
06/24/2010 LeTama tried out running patched bravo kernel on leo and got the segfaults
06/25/2010 Mailing list post from K. 'Cotulla' Ivan on how he found the solution to the infamous segmentation / illegal instruction problem on htc leo / hd2. Code in attachment see mailing list
06/25/2010 NetRipper included Cotulla's qsd8250 initialization code in haret. Build available on NetRipper's website also see Mailing List
06/25/2010 http://twitpic.com/20cruy http://twitpic.com/20cohg Messing around with ubuntu and other distributions using usb keyboard and mouse. Full potential of hd2's great speed and big display show. This runs real smooth. Soon as I got something easy to install I will upload it along with instructions on how to power the usb peripherals - without which you can't interact yet.
06/28/2010 Android is working. It was very simple problem with a missing configuration setting in the kernel which is fixed now.
06/29/2010 EXTRA EXTRA Major hurdle taken towards using touchscreen GPIO are xnow fixed. Again it's a problem about initialization so we need to add this in HaRET as well.
06/29/2010 NetRipper - aka Fastest HaRET Developer In The West - made a HaRET with GPIO IRQ fix
06/30/2010 Touchscreen source code now in linuxtogo git
06/30/2010 New wiki page on using usb host mode to connect peripheral devices.
06/30/2010 zImage build with touchscreen, keypad, usb-host mode posted in build section.
06/30/2010 First version of Ubuntu for HD2 released in the Build section
07/01/2010 android with sense for HD2 in Build section
07/04/2010 sensors working - (compass, G, light, proximity) - code available in git. See Build section for set of files to test. zImage in Advanced section updated. Thanks for the patch go to Parad0XUA
07/05/2010 Vibro working too. Code pushed, zImage updated.
07/05/2010 LeTama added WiFi support. Patch and Build following
07/08/2010 Timers updated in htc-msm-2.6.32 kernel
link to frequently updated kernel (zImage) autobuilds in advanced builds section added
new wiki page with detailed status info http://htc-linux.org/wiki/index.php?title=Leo/Status
07/10/2010 initial testing with 3g data connection, WiFi patches in git soon.
07/10/2010 Source code for 3g data connection and WiFi are available from git now
07/11/2010 New extra smooth android kit with the most recent Linux Kernel available in Android section! This has all kinds of stuff like hardware 3d acceleration, bluetooth, WiFi and 3g data connection included.
07/13/2010 support for camera added. taking videos does not work yet
07/14/2010 ongoing merge of Cotullas entire linux kernel sources (which added all the new features in recent builds) with the git kernel source code repository for hd2 Preliminary patch at http://oe.netripper.com/files/cotulla-merge.diff Sorry for the delayed release of the sources!
07/16/2010 Many of the recent changes now in official git repository
07/17/2010 Initial support for battery monitor and audio recording available. Linux kernel zImages on cotulla's site. No code available yet.
07/18/2010 FM receiver working in android
07/19/2010 Proximity sensor working in official git repository
07/20/2010 we created a facebook page for the htc-linux project
07/22/2010 due to legal concerns I will not directly link to ripped android images with proprietary parts which I am not allowed to distribute (e.g. HTC Sense). I don't want to cope with some lawyer mail.
07/24/2010 please read this before releasing HD2 android roms http://forum.xda-developers.com/showthread.php?p=7336826
07/25/2010 some new updates in the local cotulla source tree farm: seems like he added support for switching the panel (display) on/off. Find latest zImage (Linux kernel builds) on cotula's site Unfortunately there is still no source code for the recent changes but it will be released soon.
07/25/2010 turbo mode problem fix source code in official git kernel repository. autobuilds as usual on netripper site (look for zImage builds below)
07/26/2010 Ready to go Ubuntu v0.2 with very big changelog in the making
07/26/2010 a stable solution to the 3g DATA problem is found. I will add the kernel code and builds for the chefs later.
07/27/2010 New ubuntu with working touchscreen, 3g, WiFi, texting, etc. available soon for hd2
07/28/2010 Patchfor stable 3G Data connection in git. Google Android will need some adjustments to make use of it.
07/28/2010 GPS library was successfully patched to make use of the HD2 GPS in android: http://cotulla.pp.ru/leo/Android/libgps.so
07/30/2010 Ubuntu for HD2 v0.2 final version released. Go grab it! It's feature rich and touchscreen friendly.
08/03/2010 New progress with the Linux kernel with audio during calls. A binary image can be downloaded from here. Sorry but no sources are available for this. (Patch author cotulla doesn't show the code yet)
08/03/2010 Speak of the devil. Thank Cotulla for making his entire Linux kernel source code available. Now it's the turn of the fellow developers to merge it for ease of access and modification in the HD2 git kernel source repository.
08/08/2010 All of the recent source code is now available in the Linux kernel git repository. See first post for further information.
08/09/2010 Linux kernel image (zImage) and module autobuilds from the git source code are available at http://oe.netripper.com/files/htcleo_autobuild/ (-latest files always link to the latest build and get automatically update once there are changes in the source code available in git)
08/10/2010 We are working to get a stable solution to use more memory in git. This is a useful initrd to test memory for errors automatically: http://linuxtogo.org/~lgorris/initrd-memtester-armv7a.cpio.gz
08/11/2010 Full memory source code in git - uptodate zImage and modules at http://oe.netripper.com/files/htcleo_autobuild/ use THESE memory settings in startup.txt
08/14/2010 Kernel update: 1) LED driver added 2) Support for WiFi-Hotspot (iptables) enabled. Update kernel and modules via instructions in FAQ page.
08/20/2010 Flashlight support added. Grab the latest development kernel to get it! http://htc-linux.org/wiki/index.php?title=Leo/UpdateKernel
08/31/2010 Many changes in the Linux kernel since the last update:
working flashlight
ppp stability
usb stability (works with windows7 now)
fixed usb host mode kernel
working backlight control in normal Linux distros
working WiFi master (access point) mode: enables tethering (you might need to update firmware files. )
09/05/2010 We have been working on a new kernel base for the HD2 for few days now. Markinus started the initiative by introducing our present HD2 specific changes in the EVO4G release kernel source code. Right now the htc-msm-2.6.32 branch is still more advanced. We might create an autobuild for the EVO4G base kernel in case it will be superior at some point.
Builds
Global notes:
*None of the current releases will touch your internal flash. After restart you are back in the usual winmo.
*When Linux is booted, windoes mobile is shutdown abruptly. Although this is very rare it can cause some data loss. Please save your work and make frequent backups!
*You need at least a 2.08 radio rom version installed on your HD2. If yu have an older version you might not be able to boot Linux.
Separate files
For updating purposes and 'rom' creation
Automatically compiled Linux kernel builds for the HTC HD2 from GIT source code.
SEE FAQ SECTION BELOW FOR HOW TO INSTALL FRESH KERNEL
View GIT changelog
Click here to view autobuild history (archived dated zImages and modules)
Most recent zImage (Linux kernel image)
zImage-htcleo-latest
The Linux kernel is the core element of your operating system. It contains most of the drivers. It is supplied in form of a compressed (gzipped) executable binary Image. Along with an initial rootfilesystem aka initrd it is loaded into memory and executed by the bootlaoder HaRET.
Most recent Linux kernel modules to match zImage-htcleo-latest (has bcm4329.ko)
modules-htcleo-latest.tgz
Kernel modules are drivers that are not included in the zImage. They go seperately in .ko files. bcm4329.ko holds the wifi driver and tun.ko is needed for tunneling. For android use you must extract the modules.tgz file, search for the .ko files you need and copy them into /system/lib/modules/ directory. See FAQ for how to copy files into your android install.
HaRET (bootloader)
HaRET.exe
The haret bootloader is used to start Linux according to the instructions it reads from the file default.txt . If HaRET sees a file called startup.txt it will use this instead and boot Linux directly without any prompt.
startup.txt (bootloader/HaRET configuration - auto updated to match latest GIT kernel)
startup.txt
NOTE: This example configuration only holds the parameters critical to booting with latest GIT. Ask the person supplying you with 'roms' for additional parameters needed. See FAQ section for more detail on parameters.
Android
Please browse the main HD2 Android forum for various recent builds.
It is always important to install a recent kernel. See post #3 for how to.
Ubuntu
Ubuntu for HD2 v0.2
This second version has many new features like connectivity and is fully functional with the HD2 touchscreen. (No more USB stuff needed!)
If you would like to use USB devices like keyboard, mouse, usb stick etc, see here
release date: July 30, 2010
filename: hd2-ubuntu_0.2.zip
size: 773MB
md5sum: 2d67bbe658cc7a9e8599e8adf7724768
torrent: (use encouraged)
http://linuxtogo.org/~lgorris/hd2/hd2-ubuntu_0.2.zip.torrent
http://oe.netripper.com/files/hd2-ubuntu_0.2.zip.torrent
direct mirrors:
http://linuxtogo.org/~lgorris/hd2/hd2-ubuntu_0.2.zip
http://oe.netripper.com/files/hd2-ubuntu_0.2.zip
http://htc-linux.org/stuff/leo/hd2-ubuntu_0.2.zip
Quickinstall
It is important to check included readme.txt for safety notes, usage instructions and other confusion!
*1) get storage card with at least 3GB free space
*2) extract archive into root directory of storage card so that ubuntu folder is in \Sotrage Card\ubuntu
*3) runt haret exe
Features and Changelog
Kernel
*Updated Linux kernel based on htc-msm-2.6.32 revision '3af9a39113d40887f42688108ff0dbdeefd8e4cc' (see first post)
*Improved touch screen and keypad driver allow for decent navigation with the bare device
*WiFi driver
*3g driver
*Vibration driver
*Many [[Msm_Usb_Host|USB host]] drivers added (usb mass storage, audio, networking)
*Battery, panel and bluetooth drivers not installed yet due to lack of available source code. (only zImages available)
*Exact kernel source code with patches used included in archive.
Rootfilesystem based on the Karmic Koala from 0.1 release with
*Enlarged rootfilesystem size (2,6GB)
*Many tweaks for touchscreen use: on screen keyboard, enlarged GUI components, ..
*One touch super easy operation of 3G and WiFi connections, screen rotation and other things
*New packages installed, e.g. firefox and fennec browser with kinetic scrolling, pidgin instant messaging, ..
*Easy installation of extra languages etc
*GUI for the media player (gnome-mplayer) to allow basic control of the video playback
Note for testers of the old 0.2-beta release
Thanks a lot for checking the beta and providing feedback! This allowed for fixing the following in final 0.2 release:
*The off-screen content (e.g. wicd passphrase) problem was resolved adding ALT key (Home button on HD2) to drag windows around
*Add gnome-mplayer gui for the accerlated mplayer
*3G DNS hack removed (opendns caused problems accessing many websites)
*Enlarge on screen keybaord
~
Frequently Asked Questions
FREQUENTLY ASKED QUESTIONS & INSTRUCTIONS
Not so small Smallprint
TRY AND WORK THINGS OUT FOR YOURSELF BEFORE POSTING QUESTIONS. IF THAT DOESNT GIVE RESULTS THEN READ THE THREAD (THE LAST 20 PAGES SHOULD SUFFICE). THEN TRY THE SEARCH BUTTON.
IF YOU ASK A QUESTION THAT HAS BEEN COVERED IN THIS POST THEN YOU WILL BE GIVEN A WARNING AND YOUR MESSAGES WILL BE MONITORED. DO IT AGAIN AND YOU WILL BE GIVEN A 1 WEEK BAN.
IF YOU SEE A QUESTION BEING ASKED IN THE THREAD WHICH IS COVERED IN THE FAQ THEN PLEASE REPLY WITH A SIMPLE LINK TO THE FAQ AND THEN REPORT THE USER TO mskip (moderator).
IT IS RECOMMENDED TO INSTALL A HARDSPL ON YOUR DEVICE FIRST
YOU CAN FIND OUT MORE INFORMATION ABOUT INSTALLING HARDSPL AND CHANGING YOUR RADIO *HERE*
USEFUL SITES
Changelog of official HD2 GIT Linux kernel (shows driver changes etc)
Latest zImage (Linux kernel) and module files (automatically updated from GIT): http://oe.netripper.com/files/htcleo_autobuild/zImage-htcleo-latest
Port progress overview: http://htc-linux.org/wiki/index.php?title=Leo/Status
Android builds and download links: http://gamesquare.co.uk/ or http://robsbay.co.uk/
INSTALLATION INSTRUCTIONS FOR DIFFERENT BUILDS
DarkStone1337 - HTC Sense (Desire build)
1. Download from one of the above sites and extract the contents to your pc
2. Copy all files to the ROOT of your Storage Card
3. Soft Reset your device then using a File Manager goto your Storage Card and run clrad.exe (it wont do anything but it has run) followed by haret.exe (do this within 30 seconds of your phone booting into Windows Mobile)
4. Wait for Android to boot (may take upto 5 minutes)
5. Update your Linux kernel and Linux kernel modules (drivers). See below
DarkStone1337 - Froyo build
1. Download from one of the above sites and extract the contents to your pc
2. Copy the Android folder (including all files within the folder) to the ROOT of your Storage Card
3. Soft Reset your device then using a File Manager goto your Storage Card, Android folder and run clrad.exe (it wont do anything but it has run) followed by haret.exe (do this within 30 seconds of your phone booting into Windows Mobile)
4. Wait for Android to boot (may take upto 5 minutes)
5. Update your Linux kernel and Linux kernel modules (drivers). See below
Patched RootFS files (thanks to michyprima) to gain Root access to your Android Build:
DarkStones DesireV5 build - *HERE*
Useage: Copy the required file across to the right place on your Storage Card, overwrite the existing file. Load Android and thats it.
INSTALLING NEW LINUX KERNEL (zImage) AND MODULES (.ko files)
Three Things to know about the Linux kernel
1) The Linux kernel is the center of your of your operating system. Its core is seated in the kernel image (zImage file - the z means it is compressed). It contains most of the drivers.
2) Some drivers go external via Linux kernel modules (.ko files). E.g. in the HTC HD2 Linux kernel, the WiFi module is supplied as bcm4329.ko
3) The kernel image and kernel modules are made to match. They need to have the exact same version. This means if you pick a random .ko file things might go wrong => Find always up to date kernel image and matching modules here
Editing startup.txt
1) The following lines are needed in startup.txt to make GIT kernels work in any build !
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1E400000
set initrd_offset 0x00a00000
set kernel zImage
<ADDITIONAL PARAMTERS GO HERE!!!!!!!!1 Remove this line.>
bootlinux
Click to expand...
Click to collapse
2)Additionally you need to specify the following. Those parameters are dependent on the build you use. Look them up in your present startup.txt
*Initial ram disk filename (set initrd initrd.gz)
*Command line paramters (set cmdline "foo=bar google=android" )
Click to expand...
Click to collapse
Installing the latest Linux kernel image (zImage)
1) Download the latest Linux kernel image (right click, save file as)
1a)for Google Android
1b) for classical GNU/Linux based distros (Ubuntu, openemebdded, meego, maemo etc)
Be aware these build links are dynamic and will be updated once the Linux kernel source code is updated. See here for static links
2) Rename the file to zImage
3) Overwrite your old zImage file with the newly obtained zImage file
Click to expand...
Click to collapse
Installing the matching Linux kernel modules (.ko files)
1) Download the latest Linux kernel modules to match your kernel image
1a) for classical GNU/Linux based distros (Ubuntu...)
1b) for Google Android
2) Install the modules...
2a) in GNU/Linux
As root run
cd /
tar xvf /path/to/modules-htcleo-usbhost-latest.tgz
Click to expand...
Click to collapse
2b) For Google Android...
extract the modules-htcleo-latest.tgz file
you will notice it contains a directory structure.
example for module locations within modules-htcleo-latest.tgz :
WiFI module:
lib/modules/2.6.32.9-38151-g827fa85/kernel/drivers/net/wireless/bcm4329_204/bcm4329.ko
Network tunneling module:
lib/modules/2.6.32.9-38151-g827fa85/kernel/drivers/net/tun.ko
Yet Another Flash Filesystem module:
lib/modules/2.6.32.9-38151-g827fa85/kernel/fs/yaffs2/yaffs.ko
Basically you want to copy all .ko files you need into /system/lib/modules directory
Learn 3 Methods to do so detailed in the following:
memin1857 said:
Three different methods for replacing bcm4329.ko (which makes wifi work) Method B seems to be the best.
Easiest: (uses winmo, does not use third party app or commands)
A) (MAY ONLY WORK FOR SHUBCRAFT BUILD) Under winmo, create a folder named root inside your Android folder in your sdcard. This folder named root will be the actual root when Android boots up.
For example:
Create this folder structure under winmo:
STORAGE CARD\Android\root\system\lib\modules
and copy the bcm4329.ko file in it. It will look like this:
STORAGE CARD\Android\root\system\lib\modules\bcm4329.ko
Boot Android and the file gets copied to the protected Android file system. (/system/lib/modules)
If you do this from within Android, reboot to take effect.
B) Start a Terminal Emulator within Android. (Install a terminal emulator from market if not already installed) Copy bcm4329.ko to sdcard root beforehand. Filename has to be all lowercase. Enter these commands:
su
mount -o rw,remount /system
cp /sdcard/bcm4329.ko /system/lib/modules
you should get no response and wifi should work immediately.
you may want to make system readonly again with command
mount -o remount r /system
Delete old bcm4329.ko file if it exists at /sdcard/Android/root/system/lib/modules or it will come back on next reboot.
C) Use a third party app like Root Explorer, Droid Explorer, Root Manager, ES File Explorer and copy the bcm4239.ko file to /system/lib/modules which is mounted in read-write (RW) mode.
(DROID EXPLORER RUNS FROM WINDOWS XP/VISTA/7 and uses adb. No reboot required. Others run from within Android)
You can do A, B OR C. You don't need to do them all. Method A had only been tested in shubcraft v1.2b build.
As a fourth way you can use adb command that comes with android sdk. install usb drivers from within android sdk and connect your hd2 with usb debugging enabled. commands are same with terminal just put adb in front of it and run from folder adb is in.
If you copy an incorrect version of bcm4329.ko that is not matched to your zImage kernel wifi will say error and not work.
You can also WAIT for a new build that properly includes these files already to come out.
You can get bcm4329.ko file from http://oe.netripper.com/files/htcleo_autobuild/modules-htcleo-latest.tgz
Open the tgz file with winrar or similar program. The bcm4329.ko file is under lib\modules\2.32.xxxx\kernel\drivers\net\wireless\bcmxxx
Click to expand...
Click to collapse
Click to expand...
Click to collapse
GENERAL FAQ
*Some Roms are reported to work better with Android than other Roms. Duttys Roms seem to have the robot voice problem on calls. Miri's WM6.5 v17 Roms and NRGz Energy Roms seem to work best and have fewer problems.
* With some old radio rom versions it is impossible to boot Linux. Make sure you install a 2.08 + Radio. known working Radios are 2.10.50.08_2 and 2.12.50.02_2
* With the working Linux kernel any kind of Linux based userspace can be used on hd2. This includes google android and any other Linux distribution.
* This is a work in progress! Lots of stuff is still missing. Check http://htc-linux.org/wiki/index.php?title=Leo/Status for current state of affairs
* We know about most available sources of Linux kernel code for the snapdragon devices. It is not necessary to point to evo, bravo, nexus etc.
ANDROID TIPS AND HELP
No Sound in Android: Make sure you run clrad.exe BEFORE running the haret.exe file to boot Android. When you run it, it will not do anything but it does run.
Mobile Internet isnt working on TMOUS HD2: T-Mous users have to manually enter the APN for the mobile internet to work. Go into Network, Mobile Networks, APN. If the APN screen is blank press the Windows button and choose "Add APN" from the menu that pops up. Enter the following, Name: epc.tmobile.com, APN: epc.tmobile.com. Leave the rest blank. Then press with Windows button again and save. Your mobile internet will now work.
Setting up APN (Access Point Name) for Wireless Internet (other than TMOUS): Get your settings from *HERE* then on Android goto Settings, Wireless & Networks, Mobile Networks, Access Point Names. If bank press the Windows Button, New APN and enter your details.
For those having issues with WiFi turning on and off: Go to Settings>Wireless and Networks>Wi-Fi settings>Advanced(Windows key)>WiFi sleep policy> Select Never
Green Screen when booting into Android: Pull out and reinsert the battery, restart the phone and try again.
Phone gets stuck when loading Android (progresses very slow or stuck in the same postion for several minutes): Pull out and reinsert the battery. Delete all references to Android from your storage card including the cache folders and any folders Android created. Then copy the downloaded files back to the ROOT of your storage card or where you are supposed to place them (including the AndroidApps and media folders if you have them). Soft reset your device and run the clrad and haret files within 30 seconds of WinMo loading or use a program such as JMZ's Bootloader.
Sleep of Death (not coming out of sleep): Update your Linux kernel image and modules as instructed above, then restart your phone and restart Android. If you keep getting Sleep of Death with the newest Linux kernel image and Linux kernel modules files then reformat your storage card with FAT32 and start over again. Always make sure you run the latest Linux kernel image and modules.
How to install .apk files on Android: Copy the .apk file to your storage card that you want to install. (see kernel guide for android file copying howto) Load Android and run 'Linda File Manager' from the programs list, then browse to 'SD Card' (complete action using Linda File Manager if asked) and then to the folder where you put the .apk file. Note: To see more information on the screen minimise the keyboard, then click 'view' and select 'details'. Once you have found your .apk file click on it then tick 'Use by default for this action' and select 'package installer'. Now just follow the onscreen instructions to install your program. OR you can copy the .apk files to the AndroidApps folder in the ROOT of your Storage Card and they should auto install when Android loads (most of the time).
Battery isn’t charging in Android: Install the latest Linux kernel image and Linux kernel modules as detailed above.
Excessive Power Consumption: Remember that all these builds are still in beta version and not complete. Alot of things are still being ironed out.
Programs and system functions not working (such as Video camera, Bluetooth, Keyboard backlight on sleep, etc): Install the latest Linux kernel image and Linux kernel modules as detailed above.
No Ringtones or Notifications in setup (in DarkStone's Builds): Download the following file http://gamesquare.co.uk/media.zip (copy the link into your browsers address bar or it wont download). Extract the 'media' folder (make sure the folder has sub folders with the sounds inside those) to the root of your SD card. Now go to Settings, Sound and Display, Phone Ringtone or Notification Sound and they should be there.
What is a zImage? zImage is a Linux kernel binary image. It is the core of your operating system containing most of the drivers. The prepended z means that it is compressed with the gzip algorithm, making it smaller than the non compressed Image file.
Can I use more multiple zImage files at the same time? No. Your phone can only execute one Linux kernel at a time. HaRET.exe (the bootloader) reads the kernel filename from startup.txt - You can maintain multiple zImage files on your phone but chose only one via startup.txt
How do I change the background wallpaper? Hold your finger on the screen and select Wallapers from the popup list.
How do I change the settings? Press the Start Menu button on your phone (middle hardware button) to bring up the menu, then select the bottom middle button (settings or preferences depending on your Android build).
I cant update an app thats pre-installed (i.e. facebook or twitter): Download Root Explorer from the Market, then open it and browse to the 'system, app' folder. Delete the apk file of the app you want to update then try downloading and installing it again.
If you are trying out a TEST build of Android then you SHOULD have a basic level of intelligence (laughs quietly to self) so PLEASE use your brain and try to work things out for yourself before posting a question.
USEFUL ANDROID APPS
* Android System Info (by ElectricSheep, Excellent system information app): Download FREE from Market
* Battery Indicator (gives battery and temperature % readout in the taskbar): Download FREE from Market
* BatteryMinder (excellent battery information program with time left and temperature): Download FREE from Market
* CalWidget (excellent alternative to the standard calendar with lots of sizes): Download FREE from Market
* Dropbox (from Dropbox inc. excellent way to transfer files to your phone): Download FREE from Market
* FaceBook for Android (v1.2): Download FREE from Market
* Footmob (football from everywhere): Download FREE from Market
* Gmote (allows you to control your pc from your phone): Download from http://www.gmote.org/
* Google Earth (great app for viewing anywhere on the earth): Download FREE from Market
* Google Goggles (visual recognition app, well worth trying): Download FREE from Market
* Handcent SMS (enhances your sms functions and has a nice message widget): Download FREE from Market
* lastfm (really good free music streaming player similar to Pandora): Download FREE from Market
* MoreLocale 2 (nice little program that adds more locales and even add custom ones): Download FREE from Market
* Myplayer (watch on-demand tv programs for free): Download FREE from Market
* Nexus One Torch (by Ben Buxton, LED works when High Brightness is turned on): Download FREE from Market
* Opera Mini Browser (very nice and feature packed internet browser): Download FREE from Market
* Phonebook 2 (excellent contact manager app): Download FREE from the Market
* Photoshop.com Mobile (nice image editing program): Download FREE from the Market
* Qik Video Camera (record and share video, works as video camera on beta roms): Download FREE from the Market
* Ringdroid (create your own RingTones): Download FREE from Market
* SetCPU (great app allows you to tune the cpu for different situations): Download *HERE*, HowToUse it *HERE*
* Sky Remote record (says it all - tested and working fine for UK): Download FREE from Market
* TempMonitor Lite (puts temperature in taskbar): Download FREE from Market
* Zedge Ringtones & Wallpapers (free ringtones, message tones and wallpapers): Download FREE from Market
USEFUL ANDROID INFORMATION
1. The difference between Desire Builds and Froyo Builds (thanks to memin1857)
Desire build is ripped from an HTC Desire. It is Android version 2.1 (Eclair)
Froyo build is ripped from a Nexus One. It is Android version 2.2 (Froyo)
Froyo is a newer and much faster Android version. It is currently only available on Nexus one officially. Other newer phones will get it eventually.
HTC Sense is the user interface on top of Android. Desire builds have it already. It can be disabled for standard Android interface.
2. Importing WM Contacts into Android (thanks to brownman)
You need PIM Backup, a computer with internet access and a Gmail account.
1. Open PIM Backup on your Windows Mobile device. Select the Backup action and unselect everything but contacts, then hit Next.
2. At the "Select backup filename and folder" screen, unselect the "compress backup" and "binary backup" options, then hit Next.
3. Transfer the BACKUP.PIB file that you just made from your phone to your computer. Change the extension from .PIB to .RAR, then extract the file.
4. The extracted file should be BACKUP.CSC. Simply change the extension to .CSV and import the file to your gmail account. All your contacts can now be imported to your phone through gmail - just follow the instructions given in the phone's contact menu.
or activesync with google http://www.google.com/support/mobile/bin/answer.py?hl=en&answer=138636
3. Putting a Shortcut button on HTC Sense, etc to start Linux (in order to boot Android, Ubuntu, etc)
1. Make sure you have your Android build copied to your Storage Card as instructed earlier in this FAQ
2. Install mskip's Android Loader from *HERE* and install to DEVICE Memory
3. Add a Shortcut Button to your Sense, Mobile Shell or other Today Screen Plugin
4. Click on the button to start Android loading
4. Adding languages to Android Operating SystemBU
Read *THIS* thread.
Mark & dcordes​
Nice with an update thread like this, but may I ask, is this a "developers only" thread or? - Just to be sure.
mooooooa said:
Nice with an update thread like this, but may I ask, is this a "developers only" thread or? - Just to be sure.
Click to expand...
Click to collapse
you can rant as much as you like.. I will focuse on the first two posts ;P
Is it not possible to take the sw from the new HTC Evo4g is out sprint??
LG (GertS) said:
Is it not possible to take the sw from the new HTC Evo4g is out sprint??
Click to expand...
Click to collapse
Den nye HTC Evo kan jo nærmest ikke sammenlignes med HTC HD2. Andet batteri, HDMI udgang, større kamera, front kamera osv osv. Så nej.
-
Short version @English:
No. - The Evo has different hardware.
Alright, i booted the image... and the flashlight turned on for a sec, then everything turned black... thats it right?
i had to swap the default.txt to get haret to boot :/
This is only somewhat related, but nonetheless should make people less hesitant about trying android if and when we have a working ROM.
I talked to TMobile (US), and, while you cannot use an Android device on a Smartphone plan (which is what the HD2 uses), you can switch back and forth, more or less at will, between Android and Smartphone data plans. Knowing this will certainly come in handy when actually trying to connect to the internet.
Personally, I just purchased the HD2, and after using a G1 with Android for a year and a half, I feel like I am going to puke. Why is Winmo such a confusing mess? For some reason I thought it was a mature operating system, but it feels much less polished and stable than Android. Back to the store with it until linux is cracked!
should i sell my nexus one or the htc hd2? hopfully we see android on this thing and i might consider keeping the htc hd2....what u guys think? keep or sell? the hd2 screen makes my nexus one look silly...ha
ok a bit further on .. I managed to find a working (ahem) config for usbnet .. i have managed to ping my leo from my linux box and managed to get a telnet prompt .. The telnet does not fully let me in due to lack of job control i think but for now this is cool ..
Markinus is working on refining this work and making the config default so we can all benefit without the pain ..
for now if you want to see (well my brain dumps and some other output ...
http://pastebin.com/D2VZYFiv
and try the Image, root filesystem and default.txt (and dot-config if your kernel compile inclined)
The shell is crashy and not useful yet ...
http://www.megaupload.com/?d=IQ55N0Q3
Enjoy !
Cass67 said:
ok a bit further on .. I managed to find a working (ahem) config for usbnet .. i have managed to ping my leo from my linux box and managed to get a telnet prompt .. The telnet does not fully let me in due to lack of job control i think but for now this is cool ..
Markinus is working on refining this work and making the config default so we can all benefit without the pain ..
for now if you want to see (well my brain dumps and some other output ...
http://pastebin.com/D2VZYFiv
and try the Image, root filesystem and default.txt (and dot-config if your kernel compile inclined)
The shell is crashy and not useful yet ...
http://www.megaupload.com/?d=IQ55N0Q3
Enjoy !
Click to expand...
Click to collapse
What about the datasheet for the touchscreen driver? Any news?
chris5932 said:
What about the datasheet for the touchscreen driver? Any news?
Click to expand...
Click to collapse
Not as far as i have heard ..
i've a questino though @ devs. you said that the kernel is the difficult part... and after that we can easily get linux etc on it? even maemo ?.. since it's based on linux
just wanted to drop in and say hi. unfortunately there's no news yet regarding the freeze problem.
that video is just a joke. some VNC client as they say on the site. as you can see he has winmo screenlock ^^
once we have the kernel problem fixed of course you can run maemo on the hd2.
edit: btw, any datasheet news ?
It's kinda quiet in here since the recent news about WP7S.
Thanx for the update DCordes, can you put into perspective on where about you guys are then?
Is Linux booting?
If so, how is it running?
What hardware are you having problems with?
What hardware is working?
Do you have a projected ET for having Android on the HD2? Even if not finalised, but maybe first Boot?
Thanx
Keep up the good work guys (DCordes, Netripper, Markinus, CR2, Tidsk and the rest of the guys)
Seg
it's actually all in the first post. we have that problem with the kernel freezing and we don't know why yet. that's the big show stopper right now.
except for that the overall situation looks very good! sd card and even usb host is working already ^^
Hi from France,
No idea about the kernel freeze problem ... What should happen after SD card driver being loaded ?
About the multitouch datasheet, I've been searching for it for 2 days, I didn't find anything. I just asked Elan about the release date of this. Waiting for reply ...
Thanks for your work
CleM71 said:
What should happen after SD card driver being loaded ?
Click to expand...
Click to collapse
for me it crashes after init is executed (initrd or extracted to mmc, no difference) or when rootdelay is added in cmdline.
CleM71 said:
About the multitouch datasheet, I've been searching for it for 2 days, I didn't find anything. I just asked Elan about the release date of this. Waiting for reply ...
Click to expand...
Click to collapse
thanks I'm very curiious if somebody will get a reply when I tried the same thing for an aptina camera module they never answered.
with usb host working it's actually not so critical. we could use usb mouse or keyboard until we have a working leo ts driver.
ragdoll20 said:
i know, i know, you will take donations once there is some work done *beta* or something.
Click to expand...
Click to collapse
I can't speak for the other devs but I personally never said such things.
Well, the guys that are really actively working on this are written in the first post.
Anyway, Tigerzen, Cass_VM and me, we're working on this with more relax, but we're only active testers and rarely we've helped in the kernel development (if we have).
There are many things working now, but what we really need is a datasheet for our Elan digitizer(/controller) for developing a driver for our touchscreen.
Hoping the best....
The Eugenia Project Developer
-kholk

[WIP] Open Bootloader Development for Archos Gen8

Hey geeks,
you might know my hardware hacking thread already:
http://forum.xda-developers.com/showthread.php?t=1199450
Some time ago i started thinking about starting with an open bootloader for Archos Gen8.
So i started from scratch and made use of external boot mode to completely start from external MicroSD and leave the internal memory alone.
Remark: This is a geek project, there's no GUI or something. So don't expect anything useful right now.
At the moment you'll need some hardware hacking, because you'll need a serial console over uart3.
Unfortunately you'll also need a dirty hack to power up the MicroSD permanently.
Don't hesitate to ask for details about it.
So this is for the weird ones out there...
Right now there's work in progress, because stock kernel stucks at some point in the boot process.
Maybe there's some setup missing in the bootcode (it's very basic at the moment) or stock kernel relies heavily on avboot at some point.
I will work on this issue whenever i'll find some time.
Anyway it might be still an interesting project for at least a very few of you, so here's the source code:
- x-loader-archos
- u-boot-2011.09-archos
As pointed out the Archos implementation is very basic at the moment, but the code itself works very well and had been tested on A101IT Gen8.
To further devices, e.g. A70S Gen8, the machine id had to be included in the board file, the rest of the setup in early stage should be very similar.
The code bases:
- x-loader (https://gitorious.org/x-loader/x-loader)
- u-boot (taken from this archive: http://www.technexion.com/images/downloads/ARM_CPU_Modules/TDM-3730/linux-2.6.32-tdm3730.tar.xz)
I'd like to switch to official u-boot release 2011.09 as a base soon.
To start playing with it:
- open your case and start hacking, to get serial console working
- tweak the hardware to power the MicroSD slot permanently
- create a bootable MicroSD for OMAP systems
- place the binaries on your card
- insert the card and use vitalifs kernel module to reboot your device in external bootmode
Please refer to these posts from vitalif (thanks a lot for contributing!!!):
http://forum.xda-developers.com/showpost.php?p=22719203&postcount=105
http://forum.xda-developers.com/showpost.php?p=22765441&postcount=108
You might start digging in the source code and create your own loader:
- use a linux machine with a recent distribution
- setup a cross environment with ARM cross compiler suitable for ARMV7
- extract the sources to directory of your choice
- to compile x-load:
Code:
cd ./x-loader-archos
make archos_config
make
- to compile u-boot-2011.09-archos:
Code:
cd ./u-boot-2011.09-archos
make a101it_config
make
It might be required to tweak the top-level Makefiles to point at your toolchain.
I used my ready to work toolchain (for 32-bit linux only) here:
http://forum.xda-developers.com/showthread.php?t=1328027
Unfortunately i haven't found some time to create a project page at gitorious,
but hopefully i'll manage to do so in the next weeks...
I know this is a very very special project, but anyway if there's some interest, this might lead to something useful in the end.
If the bootcode is working very nice some day, it might also be possible to replace stock loader, but that's fiction yet.
You might ask what for...
I say... it's just for fun!
cheers,
scholbert
Boot console output... so far
Hey,
it had been posted already but her again for completeness...
The console log on UART3 starting custom kernel configured with stock config:
Code:
Texas Instruments X-Loader 1.5.1 (Mar 26 2012 - 20:41:11)
Found 0256 MB
Archos Gen8
Reading boot sector
Loading u-boot.bin from mmc
Done!
U-Boot 2011.09 (Mar 23 2012 - 18:53:39)
OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Archos 101IT Gen8 + LPDDR/MMC
I2C: ready
DRAM: 256 MiB
MMC: OMAP SD/MMC: 0
Using default environment
In: serial
Out: serial
Err: serial
Die ID #144800029ff800000160a4bb18027009
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2987000 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-2.6.29-omap1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2986936 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux.............................................................
................................................................................
..................................................... done, booting the kernel.
<6>Initializing cgroup subsys cpu
<5>Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (GCC) ) #1
PREEMPT Thu Mar 22 23:59:34 CET 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Archos A101IT board
fixup_archos: [console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/linuxrc d
ebug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0 mmc_block
.split=0.0001:512M]
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 65536
<7>free_area_init_node: node 0, pgdat c05fd368, node_mem_map c06a5000
<7> Normal zone: 512 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 65024 pages, LIFO batch:15
<4>L2 CACHE is enabled in bootloader
<6>OMAP3630 ES1.2
<6>DIE ID: 144800029FF800000160A4BB18027009
<6>FEATURE_STATUS: 00000c00
<6>SRAM: Mapped pa 0x40200000 to va 0xfc800000 size: 0x100000
<6>Reserving 4915200 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
<5>Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/
linuxrc debug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0
mmc_block.split=0.0001:512M
<3>Unknown boot option `androidboot.console=ttyGS0': ignoring
<3>Unknown boot option `omapdss.debug=0': ignoring
<6>Clocking rate (Crystal/DPLL/ARM core): 26.0/332/600 MHz
BTW, i extracted the function from Archos loader setup up PLL and MPU stuff.
Need some time to extract the stock setup for PLL at early stage.
Maybe this will give some answers.
One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell
TBC
Have fun!
scholbert
One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell.
Click to expand...
Click to collapse
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert
scholbert said:
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert
Click to expand...
Click to collapse
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Thanks for what you did this far and for posting your info .
divx118
Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Thanks again for all that amazing information scholbert
Hey,
first off all thanks for your interest and your replies
Some words on your comments though...
divx118 said:
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Click to expand...
Click to collapse
I did not want to sound frustrated, because i'm not.
All i do with the device and all that hacking stuff is fun and mostly for educational purpose
Maybe i'll continue working with this stuff, but for now i wanted to point out to not expect too much.
Some guys out there, bricked their devices and were looking for a solution.
That's why i wrote it down.
Basically it should be possible to recover bricks by using external boot procedure, but it's still far from a simple solution.
grim-a101 said:
Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Click to expand...
Click to collapse
Yeah that's a good point, the barrier for this kind of hacking is little high.
Unfortunately you'll have to tweak the hardware, to gain access to the serial debugging port and cheat the power management of the MicroSD slot.
Most of you simply want to use the device and do some less harder tweaks at system level.
Anyway, there are some other possibilities as well (e.g. using USB and TI Flash) to access the platform. Maybe i'll do some research here as well.
Thanks again for appreciation!!!
Regards,
scholbert

Androidx86 & Forks for UEFI Windows based tablets (custom kernels)

Androidx86 & Forks using custom kernelsfor UEFI Windows tablets
Android 6.0 Marshmallow [Stock Download] [Source]
Android 4.4.4 KitKat [As above]
RemixOS 2.0 (Android 5.1.1) [Stock Download] [Source]
PheonixOS 1.0.3 (Android 5.1.1) [Stock Download]​
Custom Kernels Included
Cube i7_Stylus
kernel device_tree
Android 6.0 MM -- post @Wootever
Android 4.4.4 KK -- post [Additional Files] @Wootever
RemixOS 2.0 -- post @asplash
PhoenixOS 1.0.3 -- post
Kernels -- located here
Hacks-Scripts-Tools
Hacks and workarounds that can be used to overcome reported issues. These will be primarily bash scripts; hopefully these can be included in the source code in some way if useful/needed.
Scripts
General scripts - use an app to launch them at boot; or make use of /etc/init.shSleep mode [effectiveness will depend on what sleep modes your device/kernel has access to (`dmesg | grep ACPI`); and will need to be modified if your screen brightness is reported elsewhere]
Code:
watch -n 60 '[ "`cat /sys/class/drm/card0/card0-eDP-1/intel_backlight/actual_brightness`" = "0" ] && echo "mem" > /sys/power/state' &
Which watches the brightness level every minute and if it's zero then puts the device into S3 sleep.
This can be modified in cases where specific modules don't comeback after sleep like the following for a rotation sensor
Code:
watch -n 60 '[ "`cat /sys/class/drm/card0/card0-eDP-1/intel_backlight/actual_brightness`" = "0" ] && setprop ro.sleep 1 && echo "mem" > /sys/power/state' &
watch -n 60 '[ "`getprop ro.sleep`" = "1" ] && [ "`cat /sys/class/drm/card0/card0-eDP-1/intel_backlight/actual_brightness`" != "0" ] && setprop ro.sleep 0 && am force-stop com.android.launcher3 && rmmod kxcjk_1013 && modprobe kxcjk_1013' &
Which restarts the kxcjk_1013 module and restarts the launcher on wakeup​
Build.prop edits RemixOS
ro.remixos.box=true
changing this value to false opens up more options in settings/taskbar and is preferable on tablets
ro.remixos.no_wallpaper=true
changing this to false will let you have a wallpaper if you turn of the file based launcher in settings​RMXTool by @imadlatch is a great tool for resizing data/system.img and having a poke through the system.img while in Windows​Proposition
It should be trivial to modify the ramdisk of Androidx86 ROMS to bind mount an additional .img to host the device specific modules/firmware for trying out new generic ROM releases - obviously full ROM build are preferrably but not always available.
Will need to have a look into the module packing that the build does in order to pack correctly when just compiling a kernel & modules.​
XDA:DevDB Information
Androidx86 & Forks, ROM for the Android General
Contributors
HypoTurtle
ROM OS Version: KitKat; RemixOS/PhoenixOS (Lollipop); Marshmallow
Version Information
Status: Stable
Created 2016-02-12
Last Updated 2016-02-12
Reserved
INSTALLATIONThere are numerous ways these can be installed and there are numerous post reporting different methods, so please don't repeat posts detailing the same issue.
I will list tried and tested installation methods (using Grub2) and a quick rundown of what makes upa grub.cfg file​
Reserved
FAQIf you have a question that hasn't been answered so far - have a look here first before posting​
Thanks @HypoTurtle for making a separate thread for Android releases on the Cube i7 Stylus device! The original thread became quite messy, and it is important to have a dedicated one for Android.
First of all, I think we should really thank the great developers in this forum, @Wootever @asplash @HypoTurtle and all other members and testers for their contribution in preparing a good android image for this tablet.
I've been testing all Android releases in the main thread, and the most stable and usable one was Wootever's 4.4 release.
All other Lollipop (RemixOS and Pheonix OS) and Marshmallow releases seem to suffer from a few major problems:
1) lack of efficient stand by / sleep mode
2) high battery drain
3) no video codecs supporting hardware acceleration
I wonder if this is the case with other x86 based laptops/tablets , and whether the x86-android team are working on fixing these essential features.
Keep up the great work everyone!
@HypoTurtle
Can you please post the script in the first entry for sleep mode in the lollipop releases?
also, any new updates or releases ?
A new beta release of RemixOS has been released.
http://www.jide.com/en/remixos-for-...rce=sendgrid.com&utm_medium=email#downloadNow
Has anyone tested it?
KamaL said:
A new beta release of RemixOS has been released.
http://www.jide.com/en/remixos-for-...rce=sendgrid.com&utm_medium=email#downloadNow
Has anyone tested it?
Click to expand...
Click to collapse
Stock RemixOS Beta, runs with a reported 4.4.2 kernel with as expected wifi not working, switching to the 4.4.0 kernel/modules/firmware we are currently using will work, but I'd rather wait until when/if the kernel source is released.
EDIT. Cube i7 Stylus kernel + modules attached. These are taken from RemixOS Alpha - so it's the kernel @asplash compiled. You need a rooted system.img or unpack/repack system.img within Windows/Linux. Just copy files over / and run the sh while running to set permissions. Then switch the kernel.
Too big to attach so available here
Just a couple of screenshots, it's seems very few people have figured out how to get rotation to work, and I'm sure even fewer have found how to enable apps like Twilight, Lux or Tincore Keymapper...
I'll post procedure in a bit just making sure it doesn't irreversibly mess with anything.
HypoTurtle said:
Stock RemixOS Beta, runs with a reported 4.4.2 kernel with as expected wifi not working, switching to the 4.4.0 kernel/modules/firmware we are currently using will work, but I'd rather wait until when/if the kernel source is released.
EDIT. Cube i7 Stylus kernel + modules attached. These are taken from RemixOS Alpha - so it's the kernel @asplash compiled. You need a rooted system.img or unpack/repack system.img within Windows/Linux. Just copy files over / and run the sh while running to set permissions. Then switch the kernel.
Too big to attach so available here
Click to expand...
Click to collapse
Thanks.
Can you explain step by step how to do it?
Also, any improvements over the previous builds in terms of battery consumption and sleep mode?
Thanks
<MOD EDIT - Non-English Quote Removed.>
Bluetooth not working (same with remix os) for me and I expand data.img with RMXtools but still in android I see 3gb,is there other way to expand?and i can see only 2678MB of ram
asplash said:
essayer d'ajouter
"blacklist btusb" dans /system/etc/modules.blacklist
et redemarre
Click to expand...
Click to collapse
Thanks,bt is working now,for data.img and ram?
leo06 said:
Thanks,bt is working now,for data.img and ram?
Click to expand...
Click to collapse
<MOD EDIT> data.img
KamaL said:
Thanks.
Can you explain step by step how to do it?
Also, any improvements over the previous builds in terms of battery consumption and sleep mode?
Thanks
Click to expand...
Click to collapse
Download it and have a look it should be fairly clear simpilest way is to copy to somewhere you can mount in android (usb, sdcard etc.), then with root file browser copy over, then replace the kernel.
Alternatively use something like RMXTools to open the system.img, copy the files over then repack system, boot, fix module permissions, then switch kernel.
Jide have just released their 4.4.y sources, so going to compile (at least the wifi driver) asap unless @asplash is already setup for a compile. There is a benefit with it at least with exfat (my exfat partitioned sdcard auto mounts with 4.4.2 but not with 4.4.0).
asplash said:
avez vous essayez ceci data.img
Click to expand...
Click to collapse
Do you know why i can't see usb stick and sd card in es file explorer?
asplash said:
de quel format son t'il ? exfat? ntfs?
Click to expand...
Click to collapse
The usb i formated from inside android but still i can't see from es file explorer and sd card is ntfs,i can see both from settings
leo06 said:
The usb i formated from inside android but still i can't see from es file explorer and sd card is ntfs,i can see both from settings
Click to expand...
Click to collapse
/mnt/media_rw/****
Can we install xposed framework in Android?
leo06 said:
Bluetooth not working (same with remix os) for me and I expand data.img with RMXtools but still in android I see 3gb,is there other way to expand?and i can see only 2678MB of ram
Click to expand...
Click to collapse
I answer to myself for 3gb of ram, just realized that is x86 not x64
@asplash
Thank you for your great work on Android for the Cube.
About your latest CM13 ROM:
-Deep sleep seems to work (at last). After coming back from sleep brightness goes up and the device remains unresponsive for a while but after pressing the Windows button everything comes back to normal.
-My 128 GB NTFS formatted MicroSD card can be read from settings and from a file explorer using /mnt/media_rw, but it isn't easily accessible from many apps.
-Battery level isn't read properly, it shows 100% all the time.
-Built-in root doesn't remember a previously granted access, installing SuperSU solves the problem.
-The app GMD Gesture Control (a must have for me) doesn't recognize the touchscreen device. It worked on your Lollipop ROM.
-Only 3 Gb of RAM seem to be accessible, your Lollipop ROM aparently could see the full 4 GB.
-The device doesn't boot with the 8 Gb data.img, it gets stuck on the boot animation.
Speaking about your Lollipop ROM, it's been my Android choice for more than a month. Since its only drawback was the inability to enter deep sleep it would be lovely if you could post a new Lollipop ROM with that issue solved.
ariadnejro said:
@asplash
Thank you for your great work on Android for the Cube.
About your latest CM13 ROM:
-Deep sleep seems to work (at last). After coming back from sleep brightness goes up and the device remains unresponsive for a while but after pressing the Windows button everything comes back to normal.
-My 128 GB NTFS formatted MicroSD card can be read from settings and from a file explorer using /mnt/media_rw, but it isn't easily accessible from many apps.
-Battery level isn't read properly, it shows 100% all the time.
-Built-in root doesn't remember a previously granted access, installing SuperSU solves the problem.
-The app GMD Gesture Control (a must have for me) doesn't recognize the touchscreen device. It worked on your Lollipop ROM.
-Only 3 Gb of RAM seem to be accessible, your Lollipop ROM aparently could see the full 4 GB.
-The device doesn't boot with the 8 Gb data.img, it gets stuck on the boot animation.
Speaking about your Lollipop ROM, it's been my Android choice for more than a month. Since its only drawback was the inability to enter deep sleep it would be lovely if you could post a new Lollipop ROM with that issue solved.
Click to expand...
Click to collapse
For the battery it happens the same to me but after reboot is OK, drops by 4,5,8% and not by 1%,i mean now is 55% and after some time it shows 50%,for 3gb of ram self-test my previous post, it's 32bit Version of Android so only see 3gb,for data.img I use wootever 6gb data.img and it works

Where to get arm-eabi-5.2-ub and arm-linux-androideabi-4.9-sm toolchain?

To build this rom: http://forum.xda-developers.com/opt.../rom-euphoria-os-1-0-beta-unofficial-t2990338
I need a more up to date tool chain than deployed in the EOS repo:
prebuilts/gcc/linux-x86/arm/arm-eabi-5.2-ub/bin//arm-eabi-gcc
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9-sm/bin/arm-linux-androideabi-gcc
When I change the BoardConfig such that it uses the old toolchains the compiler crashes with an internal error and the only way to to fix it is to turn of optimization form -O3 to -Os or -O1
Hence I would like to compile it with the toolchain the author used.
Where do I get it from?
EDIT: when i go on http://sabermod.com/ i only get an empty page so i need some t3d party download source for i guess arm-linux-androideabi-4.9-sm

OPEN BETA for 17.1 UNOFFICIAL LineageOS T550 rom

BEFORE YOU decide to try this rom, please read all of post 1 and 2.
The UNOFFICIAL LineageOS 17.1 T550 ROM
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
Let me be clear, I have the SM-P550, NOT the SM-T550.
So I built a SM-P550 rom which is almost the same as the SM-T550 except the "P" stands for Pen.
I believe my P550 rom with minor modifications will work on the T550, but I have no T550 to test it on. I believe it will work because I have used virsys T550 rom on my P550 and it works, but the X-axis touch is inverted.
So I built SM-P550 with code to fix the X-axis touch inverted problem and it's one of line code. If I leave that one line of code out, then the X-axis will be correct for the T550. I have tested my 17.1 T550 rom on my P550 and it works, but again with the X-axis inverted. Just remember I don't have a T550 to test it on so you may run into bootloops, stuck at boot animation, etc.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT attempt this ROM. You must know how to use these tools to revert back to your old rom. I'm not a Windows user so do not expect any help from me. My main OS is Lubuntu 20.04 LTS and all my roms are built on this platform.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
Again, the T550 rom that I built does boot and function on my P550, but I have no T550 to verify.
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
The rom has the latest monthly 2021 security patches.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. camera
8. touchscreen X-axis works properly
9. Google play store - use pico apps
10. flip flap smart cover
11. audio over bluetooth
What doesn't work
1. LineageOS FM Radio app does not work. The P550 and T550 don't have the LTE chipset for it to work.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Why are you releasing a ROM for a tablet that you do not own?
A1) I don't own the SM-T550, but have the SM-P550. I also build roms for the SM-T350 and SM-T560NU. All these platforms use the same msm8916 code base. As such, all my work from the SM-T350, SM-T560NU and SM-P550 could possibly benefit SM-T550 users. For one P550 owner, there are probably twenty T550 owners.
Q2) What if my app, xyz, doesn't work?
A2) I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit, not mine as I don't even have the T550.
Q3) Your rom is laggy and buggy.
A3) If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research newpipe, microg, youtube vanced, aurora store etc.
Q4) What TWRP should I use?
A4) Use 3.4.0.0. Get it at
Download TWRP for gt510wifi
Download TWRP Open Recovery for gt510wifi
dl.twrp.me
Q5) Why should I use this rom?
A5) You don't. I only offer it because I have built the SM-P550 and it was an easy change to make a SM-T550 rom. If you don't like this rom, then don't use it. Yes, it's that simple.
Q6) Can you build SM-T555 (LTE) or a crDroid version of the SM-T550?
A6) No. All the source code is open source and my changes are in the repo diff file. You can use these two with the roomservice.xml to build your own rom.
Q7) Will you offer monthly updates with security patches?
A7) That all depends on if I continue to have high speed Internet and on the reaction of the posts in this thread. If people are going to complain, then I have NO incentive to make an update. Remember, I don't have the T550 so I get zero benefit from making this rom for myself.
Q8) Can you help me? I'm a newbie. Can you provide step by step instructions?
A8) There are lots of tutorials, videos, etc on how to flash roms. Do your own research.
Q9) Can I report a bug with respect to the rom?
A9) Yes, but you need to supply a) how to recreate it b) a logcat c) a github commit showing how it was fixed. Even then, if I don't have the means to recreate it, I won't be working on it.
Q10) Can I build this rom? Where are the source and kernel source files?
A10) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
aala27 - Repositories
aala27 has 7 repositories available. Follow their code on GitHub.
github.com
Q11) Okay, I understand the consequences and that this is beta rom and willing to take the risks outlined, now where can I find the rom?
A11) Downloads are at
retiredtab - Browse /SM-T550/17.1 at SourceForge.net
sourceforge.net
Hi rretiredtab
I have a T550 with the latest virsys image 16.0 from March 2020.
It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
I'm ready for a new challenge. If I can help you, please let me know.
Best regards
Schaagi
Hi retiredtab,
I ready to try this rom
Schaagi said:
I have a T550 with the latest virsys image 16.0 from March 2020. It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
Click to expand...
Click to collapse
My 16.0 rom for the SM-P550 is based on virsys repos. However, I was only able to make 2 builds using his repos before a LineageOS update in Sept 2020 caused it to get stuck at the boot animation.
Then I tried virsys 17.1 repo and it too gets stuck at the boot animation. I know virsys built crDroid Android 10 rom and uploaded it sometime June 2020, but his Android 10 repos on github are dated March 2020 so whatever patches he did to get crDroid working isn't on github.
I don't know if 17.1 will be faster than 16.0. The 17.1 builds, by default, use an overclocked CPU and GPU in the kernel code. However, I don't know if you will see any real world differences in performance from the overclocking.
In addition, I don't know if virsys March 16.0 March 2020 is overclocked or not. You can always download an utility like CPUinfo at
CPU Info | F-Droid - Free and Open Source Android App Repository
Information about device hardware and software
f-droid.org
to see if the CPU is running at 1.2Ghz or 1.6Ghz (overclocked).
@Schaagi and @Simone101, please let me know if the T550 ROM boots or not after you have installed it. I'm pretty sure it will, but would like to know ASAP.
Then, afterwards, you can let me know how it works over a 24 to 48 hour period. I'm interested to see if it randomly reboots or crashes.
As for speed and performance, just remember it's a 5 year old entry level tablet and unless LineageOS is written in assembler language, it will never match a top of the line model tablet.
Thank you.
I've installed your image as clean-install. It boots !!!
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
First installation without opengapps -ok
Second one with opengapps - ok
Restore Data from previous image - ok
As next I will try to install magisk.
Wow, good job. I will check it for the next days and give feedback later.
Best regards
Schaagi
Schaagi said:
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
Click to expand...
Click to collapse
Can you provide a screenshot of the error please?
I haven't seen the bluetooth error before on my SM-P550 and I reboot my SM-P550 a lot because I'm always flashing new builds.
I don't use bluetooth at all, but when I turn it on, I can see my neighbor's 65 inch TV. Also, I can pair two tablets together using bluetooth.
Meanwhile I have installed Magisk 21.1 and it works too
I've attached 2 screenshots from Bluetooth error.
Schaagi said:
I've attached 2 screenshots from Bluetooth error.
Click to expand...
Click to collapse
The above is why we need BETA testers.
Okay, I ran into the bluetooth error problem on the SM-T350 and it was due to a missing bluetooth library.
In my SM-T350, I have
Code:
# RT 17.1 copy bluetooth file otherwise bluetooth keeps crashing
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/vendor/lib/libbtnv.so:$(TARGET_COPY_OUT_VENDOR)/lib/libbtnv.so
Those 3 lines of code are not in the T550 build. It's easy to add and I can create another BETA build. It's building right now and probably be done in the next 2 hours or so.
If you want to add the libbtnv.so file yourself, here are the instructions
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libbtnv.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Click download.
5) Goto the directory where the libbtnv.so is saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$ adb push libbtnv.so /system/vendor/lib/libbtnv.so
libbtnv.so: 1 file pushed, 0 skipped. 48.5 MB/s (16128 bytes in 0.000s)
8) Check to make sure file was pushed.
Code:
$ adb shell ls -al /system/vendor/lib/libbtnv.so
-rw-r--r-- 1 root root 16128 Dec 19 21:24 /system/vendor/lib/libbtnv.so
9) Reboot into system and bluetooth error should be gone.
OR
Just wait until my next build is done to get rid of the bluetooth errors. I'm confident the error is due to the missing bluetooth library file.
I will send you and Simone101 a PM when the new build is done.
The new BETA build is finished, but having problems uploading to host server right now. I will try again in a couple of hours to upload. I will PM when I get it uploaded.
I've installed the new image and bluetooth error has gone.But I'didn't test the functionality of bluetooth at the moment.
Will check more in detail and inform you about the results. Thank you.
Regards
Schaagi
@retiredtab
I want to test your ROM , where I can download it.
At the moment I use the cdroid 10 by virsys
My CPU runs at performance mode with 1600 MHz.
bierma32 said:
At the moment I use the cdroid 10 by virsys
Click to expand...
Click to collapse
Over at the T550 thread, it seems that some people who are using crDroid 10 are reporting
1) camera not working
2) brightness not working
3) browser crash (that's you)
#1 and #2 work on my build. As for #3, if you are using the built in Jelly browser, I have noticed that if you open more than 4 windows, it crashes sometimes.
While not perfect, I found that smartcookieweb app works better than Jelly.
Releases · CookieJarApps/SmartCookieWeb
A secure, open source web browser for Android. Contribute to CookieJarApps/SmartCookieWeb development by creating an account on GitHub.
github.com
The Brave browser seems to work the most reliable. You can use Aurora store to download it from play store or try downloading brave apk somewhere.
On a daily basis, I use smartcookieweb as it has built in adblocker and suits my daily browsing needs.
@retiredtab
Both cameras works on Cdroid for me.
Yes, browsers crashes after some times, I use opera mini.
Bluetooth works for, tested sending and recive images.
GPS is not working, will try it again next time.
Magisk 21 works.
WiFi works.
Hi retiredtab,
Nice to see that anybody has try to give us an update for this fossile
Please let me knoe where can I download and test your build.
regards,
L
bierma32 said:
GPS is not working
Click to expand...
Click to collapse
No need to retest GPS. I already know what's wrong. This is the same problem I had with the T350.
The T550 build is missing the commands
Code:
# GPS
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/lib/libloc_api_v02.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_api_v02.so \
vendor/samsung/msm8916-common/proprietary/lib/libloc_ds_api.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_ds_api.so
Now I did test the T550 build on my P550, but it looks like when I made the final image, some of my scripts or commits didn't get copied, like the above, over when I initially changed some P550 naming/parameters to T550.
Some background. I had only 1 hard drive for the P550 and T550 code. I did test bluetooth and gps on my P550 and both work.
After I tested everything, I then later split the P550 onto one hard drive and the T550 to another so I wouldn't get confused when compiling and making changes. I suspect now that I forgot to copy over my T350 script to fix gps and bluetooth onto the new T550 drive.
To fix gps without having to re-download another 440MB file,
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libloc_ds_api.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
and
proprietary_vendor_samsung/libloc_api_v02.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Download both files above (libloc_ds_api.so and libloc_api_v02.so).
5) Goto the directory where both are saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$adb push libloc_api_v02.so /system/vendor/lib/libloc_api_v02.so
libloc_api_v02.so: 1 file pushed, 0 skipped. 7.6 MB/s (116316 bytes in 0.015s)
$adb push libloc_ds_api.so /system/vendor/lib/libloc_ds_api.so
libloc_ds_api.so: 1 file pushed, 0 skipped. 29.5 MB/s (26132 bytes in 0.001s)
8) Check that both files exist.
$adb shell ls -al /system/vendor/lib/libloc_api_v02.so
-rw-r--r-- 1 root root 116316 Dec 7 2020 /system/vendor/lib/libloc_api_v02.so
$adb shell ls -al /system/vendor/lib/libloc_ds_api.so
-rw-r--r-- 1 root root 26132 Dec 7 2020 /system/vendor/lib/libloc_ds_api.so
9) Reboot into system and GPS should be work now.
I'm making a new BETA image again and before I upload it, I will retest everything again on my P550. It's a bit awkard as everything is mapped backwards on the X-axis.
I'll post here when it's up.
Well it was around 1AM in the morning when I saw the gps not working post and now it's 2:13AM. I'm just waiting for the last 5 minutes of my new build, but the host server is having major problems right now.
So I'm going to sleep and will try uploading the new image tomorrow after I retest everything with the P550 running the T550 image. Everything will be mapped backwards for me on the X-axis while testing.
Dec 21 BETA build up. Androidfilehost is having major problems so I put it up on sourceforge.net. No way I could go to sleep with this hanging over my head. It's 2:30AM. Now I'm going to sleep in tomorrow.
Dec 21 build has gps fix.
Ooh i want really like to test!

Categories

Resources