Related
To start: Yes, I have searched the forums for similar items. There are no helpful responses. Hopefully this extra info helps.
Phone: HTC Evo 4G
OS: Cyanogenmod 7.1.0 Supersonic
Kernel Info: 2.6.37.6-cyanogenmod-01509-g8913be8
Background: I need to speak with serial devices via the USB port. The specific device I want to send data is an FTDI device. I am successfully communicating with the device via my Linux-based desktop. The challenge is porting my code to Android.
Here we go.
I started here: http://android.serverbox.ch/?p=285
To get the development environment and kernel for my phone I followed this:
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
When compiling my kernel I ran into a problem with the environment variables defined in the tutorial. I replaced CCOMPILE with CROSS_COMPILE and pointed it to my Code Sourcery install:
export CROSS_COMPILE=/home/LINUX_USER/Hardware/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-
I updated my kernel configuration (according to the FTDI tutorial) and tried to build the kernel and FTDI kernel module. My first attempt to "make" the kernel didn't work. I found this:
http://forum.xda-developers.com/archive/index.php/t-932190.html
Which provided me with a flag to get make to run:
# make EXTRA_AFLAGS=-mfpu=neon
The FTDI kernel module built successfully and I pushed the module to the SD card and tried to install module:
# /home/LINUX_USER/Hardware/android/android-sdk-linux/platform-tools/adb push drivers/usb/serial/ftdi_sio.ko /sdcard/
# insmod /sdcard/ftdi_sio.ko
insmod: init_module '/sdcard/ftdi_sio.ko' failed (Exec format error)
Since it didn't work I checked dmesg
# dmesg shows this:
[snip]
<3>[20821.873504] ftdi_sio: version magic '2.6.37.6-cyanogenmod-g996b70e preempt mod_unload ARMv7 ' should be '2.6.37.6-cyanogenmod-01509-g8913be8 preempt mod_unload ARMv7 '
I validated the kernel version on my phone and looked for a fix:
# uname -a
Linux localhost 2.6.37.6-cyanogenmod-01509-g8913be8 #1 PREEMPT Wed Jul 27 21:34:30 EDT 2011 armv7l GNU/Linux
The following tutorial provided me with instructions on how to address this issue:
http://glandium.org/blog/?p=2214
I changed the subversion number for the kernel by updating .scmversion to contain the following data:
-01509-g8913be8
After recompiling I tried to load the FTDI module again and got the following messages:
# insmod ftdi_sio.ko
insmod: init_module 'ftdi_sio.ko' failed (No such file or directory)
# dmesg | tail -15
<6>[58392.044647] batt: batt power_supply_changed: battery at 58389757684756 (2011-11-16 17:35:59.423392893 UTC)
<4>[58392.053100] at 58389762414981 (2011-11-16 17:35:59.413322092 UTC)
<4>[58413.600006] ftdi_sio: Unknown symbol usb_register_driver (err 0)
<4>[58413.602172] ftdi_sio: Unknown symbol usb_serial_handle_sysrq_char (err 0)
<4>[58413.604858] ftdi_sio: Unknown symbol usb_serial_disconnect (err 0)
<4>[58413.607910] ftdi_sio: Unknown symbol usb_serial_generic_open (err 0)
<4>[58413.610290] ftdi_sio: Unknown symbol usb_serial_generic_close (err 0)
<4>[58413.612609] ftdi_sio: Unknown symbol usb_control_msg (err 0)
<4>[58413.615142] ftdi_sio: Unknown symbol usb_deregister (err 0)
<4>[58413.617340] ftdi_sio: Unknown symbol usb_serial_generic_unthrottle (err 0)
<4>[58413.619262] ftdi_sio: Unknown symbol usb_serial_handle_break (err 0)
<4>[58413.622161] ftdi_sio: Unknown symbol usb_serial_generic_throttle (err 0)
<4>[58413.622955] ftdi_sio: Unknown symbol usb_serial_probe (err 0)
<4>[58413.624511] ftdi_sio: Unknown symbol usb_serial_register (err 0)
<4>[58413.630371] ftdi_sio: Unknown symbol usb_serial_deregister (err 0)
Since this failed I tried other compilers as well with the same results.
export CROSS_COMPILE=/home/LINUX_USER/Hardware/android/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
export CROSS_COMPILE=/home/LINUX_USER/Hardware/android/cyanogenmod/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
I need help understanding what I should try next.
Thank you,
cutaway
If you still haven't gotten it running I posted a kernel on the cyanogenmod site with these modules in /system/lib/modules.
Load usbcore.ko, usbserial.ko, then ftdi_sio.ko
Unfortunately I don't have any devices to test, so let me know if it works.
sbradymobile said:
If you still haven't gotten it running I posted a kernel on the cyanogenmod site with these modules in /system/lib/modules.
Load usbcore.ko, usbserial.ko, then ftdi_sio.ko
Unfortunately I don't have any devices to test, so let me know if it works.
Click to expand...
Click to collapse
Link please. I have looked but I cannot locate it.
Thank you,
cutaway
http://db.tt/JQVbCGQS
sbradymobile said:
Load usbcore.ko, usbserial.ko, then ftdi_sio.ko
Unfortunately I don't have any devices to test, so let me know if it works.
Click to expand...
Click to collapse
Okay, I tried but it failed for the reason I thought it would. The .scmversion extensions don't match the kernel I have. I am not going to load the whole kernel as I don't want to trouble shoot the whole system or worry about other issues.
I appreciate your effort.
I need somebody to help me understand why I can successfully build a kernel module with my kernel's .config but it does not have the proper symbols to run the module. I would have thought it would fail to compile. /me sighs
You need host mode for this to work, so the main issue is you have to strip out msm_hsusb and gadget code that is built in to the kernel. This means you need a new kernel image for this to work as there is no module to unload.
The kernel I posted earlier will not work because msm_hsusb is still registered on boot, preventing the ehci-hcd module from loading.
You can try this one if you like http://db.tt/0s7xRlYW; I was able to get ehci-hcd to load, but the dmesg output shows an irq problem.
It is the most recent CM7 kernel.
sbradymobile said:
You need host mode for this to work, so the main issue is you have to strip out msm_hsusb and gadget code that is built in to the kernel. This means you need a new kernel image for this to work as there is no module to unload.
The kernel I posted earlier will not work because msm_hsusb is still registered on boot, preventing the ehci-hcd module from loading.
You can try this one if you like link was here; I was able to get ehci-hcd to load, but the dmesg output shows an irq problem.
It is the most recent CM7 kernel.
Click to expand...
Click to collapse
Was you succeded to bring FTDI up and running?
In the same vein of a similar question asked not too long ago about Win 8, do you guys think we could get Ubuntu, Linux Mint or any other distro on our tablets? Seems far more plausible and I'd love to see this
Try the "complete Linux installer" from the play store I haven't tried it yet but it said it was compatible with the n7
Sent from my Nexus 7 using xda premium
I've been trying to, and I've had some success.
I installed Ubuntu ARM to my /cache partition (/dev/mmcblk0p4)
Then I compiled my own kernel from the official sources, only adding TTY and framebuffer console support to the config.
Then I made it into a boot.img like this:
Code:
$ touch initrd.cpio
$ mkbootimg --kernel zImage --ramdisk initrd.cpio --cmdline "console=tty0 root=/dev/mmcblk0p4 rootfstype=ext4 init=/sbin/init" -o boot.img
Now I can load Ubuntu from fastboot:
Code:
$ fastboot boot boot.img
Well kinda... I can boot to a command line session fine, but I haven't gotten Xorg to work yet.
When I try to start X the kernel panics and the device reboots.
Does anybody know if there's an Xorg driver for Tegra 3?
Good luck! I hope to see it work.
Sent from my Nexus 7 using xda premium
Ubuntu on android
I am currently trying to implement ubuntu on my nexus 7 as well, rather than running it through a vnc viewer, which I think its very slow.
Help
How do you extract the ubuntu image and where do you place it?
steevp said:
I've been trying to, and I've had some success.
I installed Ubuntu ARM to my /cache partition (/dev/mmcblk0p4)
Then I compiled my own kernel from the official sources, only adding TTY and framebuffer console support to the config.
Then I made it into a boot.img like this:
Code:
$ touch initrd.cpio
$ mkbootimg --kernel zImage --ramdisk initrd.cpio --cmdline "console=tty0 root=/dev/mmcblk0p4 rootfstype=ext4 init=/sbin/init" -o boot.img
Now I can load Ubuntu from fastboot:
Code:
$ fastboot boot boot.img
Well kinda... I can boot to a command line session fine, but I haven't gotten Xorg to work yet.
When I try to start X the kernel panics and the device reboots.
Does anybody know if there's an Xorg driver for Tegra 3?
Click to expand...
Click to collapse
http://www.nvidia.com/content/devzone/linux-for-tegra.html
That seems to be the link to the Nvidia drivers
thanks Grey Goshawk. I will try it out.
robbalmbra said:
How do you extract the ubuntu image and where do you place it?
Click to expand...
Click to collapse
I started with Ubuntu core armhf and added what I wanted.
https://wiki.ubuntu.com/Core
If you're looking for a pre-built image you might try lilstevie's Ubuntu image for the transformer prime. I think it includes the tegra driver so maybe it will work better.
Once I was finished I tarred up my Ubuntu rootfs, copied it to the internal storage, and then extracted it like this (requires busybox):
Code:
tar xvf /sdcard/myrootfs.tar -C /cache
I believe the /cache partition is only 512 MB, so there's not a lot of room for Ubuntu. If you need more space you might want to try /data or maybe a USB drive instead.
Sent from my Nexus 7 using Tapatalk 2
I will try 'lilstevie's Ubuntu image' and report back. Thanks
I have tried the nvidia tegra link, however when it comes to the stage of flashing to the apx it fails and i feel if i muck this up i may brick my nexus 7. I have tried to boot up using 'steevp' method, however it doesn't work.
If possible could you attach your root fs and kernel and or boot.img? That would be a great help.
bump
I'd love to see this come to fruition, it would be cool to run gnome on it, and id use it heavy duty. It would be cool to safe strap it, and have a dual boot. now if only someone would port safe strap >.<
Agreed if Ubuntu or similar could dual boot on this I would be so stoked.
Sent from my Galaxy Nexus using xda premium
For my part, I have played with a chrooted Debian Wheezy and a modified kernel (to enable some toys, such as the virtual frame buffer, binfmt_misc (useful when I will try a x86 chrooted Debian system), all kind of USB drivers...).
Most tools seems to be working fine ; however I have not been able to start an X server (after stopping Android with : setprop ctl.stop zygote; setprop ctl.stop bootanim). I have tried several alternatives :
Xorg with fbdev module
Nothing showing up on screen. Logs flooded with
Code:
[ 9838.003] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
Xorg with tegra driver
I untar-ed the driver from NVIDIA to the root filesystem and made a symbolic link from the API-12 driver to tegra_drv.so. Then I copied all tegra-related device to the chrooted /dev.
Still nothing showing up on screen. The server crashes when loading icewm with :
Code:
[ 9810.410] (WW) TEGRA(0): Error flipping DC window (head 0): Permission denied.
[ 9813.217] (WW) TEGRA(0): LVDS-1: Error querying display modes: No such device.
[ 9813.219]
[ 9813.221] Backtrace:
[ 9813.221]
[ 9813.223] Segmentation fault at address 0x28
[ 9813.224]
Fatal server error:
[ 9813.225] Caught signal 11 (Segmentation fault). Server aborting
[ 9813.225]
[ 9813.226]
Please consult the The X.Org Foundation support
at [I cannot post link as a new user]
for help.
[ 9813.226] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 9813.227]
[ 9813.228] (II) device control: off
[ 9813.250] (II) pointer_property
[ 9813.250] (II) pointer_property
[ 9813.250] (II) device control: close
[ 9813.250] (II) UnloadModule: "multitouch"
[ 9813.250] (WW) TEGRA(0): Error putting cursor for head 0: Permission denied.
[ 9813.250] (WW) TEGRA(0): Error putting ARGB cursor window for head 0: Permission denied.
[ 9813.256] (WW) TEGRA(0): Error putting display window 0 on head 0: Permission denied.
[ 9813.257] (WW) TEGRA(0): Error putting cursor for head 1: Permission denied.
[ 9813.257] (WW) TEGRA(0): Error putting ARGB cursor window for head 1: Permission denied.
[ 9813.257] (WW) TEGRA(0): Error putting display window 0 on head 1: Permission denied.
[ 9813.258] Server terminated with error (1). Closing log file.
Xfbdev server
Both server and icewm are able to start. Everything displays correctly on screen. However, no mouse driver, so no interaction are possible...
It would seem that, for the time being, the best solution is tightvncserver combined with android-vnc.
I have also tried to play with qemu-system-i386, but my pre-installed windows systems (98 and XP) don't start, printing "Input/output error" when booting.
However, playing with FUSE and sshfs (or mount.cifs) can enable transparent access from Android apps to an ssh (or windows) file server
Okay you got a nice way done in that work! I'll try to setup VirtualGL instead of a regular VNC server. Still less efficient than a native output but could help. I will work with the linuxonandroid stuff to help this team as much as I can.
Bodhi Linux for Nexus 7
http://jeffhoogland.blogspot.in/2012/12/bodhi-armhf-alpha-for-nexus-7.html
Anyone tried this yet?
Hello All,
I'm unable to insert a simple kernel module on my rooted S4 I9505.
below are the errors
Code:
insmod /data/local/tmp/testHello.ko
insmod: init_module '/data/local/tmp/testHello.ko' failed (Exec format error)
and kmsg's are
Code:
<4>[ 2127.554107] TIMA: lkmauth--launch the tzapp to check kernel module; module len is 71334
<4>[ 2127.554168] TIMA: lkmauth -- hdr before kreq is : e337b000
<4>[ 2127.554199] TIMA: lkmauth--send cmd (lkmauth) cmdlen(304:320), rsplen(264:320) id 0x00050000, req (0xE352A000), rsp(0xE352A140), module_start_addr(0xE337B000) module_len 71334
<3>[ 2127.581909] TIMA: lkmauth--verification failed -1
<4>[ 2127.582183] TIMA: MSG=lkm_modified; result (TIMA_RESULT=MSG=lkm_modified;)
<6>[ 2129.417541] [debug_wake_locks]active wake lock msm_otg
Any help or pointers would be of great help
Best Regards
Basha
did u manage to insmod your module? im having same issue on my i9505 stock kernel rooted. it seems to also come up prevention information in the status bar
DipSprayArc said:
did u manage to insmod your module? im having same issue on my i9505 stock kernel rooted. it seems to also come up prevention information in the status bar
Click to expand...
Click to collapse
This means that module format is not same as stock kernel even if you compile your module based on the stock kernel config.
Also for the "Detection information" dialog in status bar you need to tweak as explained in this and/or this thread based on your model
Hit thanks if this helps
Am trying to run a ATH9K_htc driver. I compiled as a module with the kernel but no good same extra version. Is there anyway to do this? Mayb modify kernel to take insmod --forced? Or this may already be set can't remember.
Thanks for solution to detection information. Had been looking
Cheers
---------- Post added at 01:29 AM ---------- Previous post was at 01:24 AM ----------
Also read that they may need some kind of digital signing? ELF?
DipSprayArc said:
Am trying to run a ATH9K_htc driver. I compiled as a module with the kernel but no good same extra version. Is there anyway to do this? Mayb modify kernel to take insmod --forced? Or this may already be set can't remember.
Thanks for solution to detection information. Had been looking
Cheers
---------- Post added at 01:29 AM ---------- Previous post was at 01:24 AM ----------
Also read that they may need some kind of digital signing? ELF?
Click to expand...
Click to collapse
either you add extra version in Makefile like
Code:
VERSION = 3
PATCHLEVEL = 4
SUBLEVEL = 0
EXTRAVERSION =-431985 // this string should match with target kernel version(extra)
Or
try to disable CONFIG_MODVERSIONS check in your kernel config.
HIT Thanks if its helps
Code:
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
IMPORTANT INFORMATION
What is working:
Boots
Audio (playback && recording)
Bluetooth
Graphics
Camera (photos only)
Sensors
RIL
Wifi
USB
Video playback (HW/SW)
What is not working:
GPS
Video recording
maybe yet something
Download:
FTP server
Older releases:
FTP server
Installation order:
The installation below requires a repartition of the phone internal sdcard in order this ROM fit on /system partition. DO NOT proceed an installation if you are unsure what you're doing and how to deal with a possible consequencies.
before installation make sure you have a TWRP recovery
install chrono kernel (both ROM and the corresponding kernel are located in the same directory - see ROM link below)
reboot recovery
flash ReParted zip. This will wipe system, data and cache partitions!
install ROM
install SuperSU
install chrono kernel again
*please note a possibly undesirable effect of the repartition: cache partition will be decreased to 15 MB and some ROMs that rely upon this partition won't boot. To restore original sdcard partition layout, flash stock 4.1.2 ROM (with PIT file).
Credits:
@SergeyL
@rINanDO
@AdrianDC
@3liteking148
@Meticulus
@Unjustified Dev
@golden-guy
@nieltg
@isaak
@NovaFusion
@TeamCanjica
LineageOS community
Google
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
Source code:
Manifest: LOS 15.0, LOS 15.1
Device tree: LOS 15.1,
Kernel: LOS 15.1
other repos
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, SergeyL
Source Code: https://github.com/ChronoMonochrome/android/tree/cm-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP recovery
Version Information
Status: Beta
Created 2018-03-11
Last Updated 2018-12-31
Reserved
Changelog
9.08.2018 - build #2
sources updates - thanks @SergeyL for patches
system time fixes (thanks @rINanDO, @millosr and @mickybart)
wifi autoconnection fix
video recording fix
fix IMEI not showed (thanks @rINanDO , @Ziyan, @MWisBest)
change default CPU governor to Interactive
wifi background scan disabled for a better battery life
unified (codina / janice) release *
* release folder now contains two kernel zip's - for codina (Ace 2) and janice (S Advance). Do not forget to flash the kernel after ROM installation, accordingly to your phone model.
12.03.2018 - build #1
initial release
Reserved
OMG Going to flash now, thanks chrono!
Just one word for my feedback: Incredible
Good jobs, man! :good:
Any chance, i will get this on my I9070P?
Thanks you for helping Janice build so many awesome Rom. Really can't wait stable version this few Rom.
hfte said:
Any chance, i will get this on my I9070P?
Click to expand...
Click to collapse
Yes, I'm planning to support P model later. For now you can use /system/lib/tee folder from any I9070P ROM to get RIL working.
Hello ChronoMonoChrome and thanks for all the work and passion you put into your every project. Thank you very much again.
So, my way to do it was this one (the only way I got it to boot):
1- Went back to Stock Firmware, Jelly Bean. I bricked my janice so I had to
2-Booted into stock recovery and flashed this TempCWM
3-From the CWM, I flashed the kernel to get the TWRP recovery
4-Rebooted to get TWRP
5-Flashed ReParted.zip, the ROM and reflashed the Kernel. This one is important, if you don't there's a chance it won't boot
6-Enjoy Oreo
As a few notes:
-The ROM takes a while to install, be patient
-Both TWRP and CWM don't detect the external SD card, so you should copy the ZIP files to the internal storage
-ROM doesn't include GAPPS, if you want them I recommend going to opengapps.org and get the pico ones for ARM. Just bare functionality and from there you install what you need.
Thanks Chrono for giving us Oreo when we had lost hope
So I've been using it for a little while now and it runs surprisingly fast. At least faster that others Android 5+ ROMs in the forum. It has pretty fast boot times too.
Some stuff that I noticed:
-I can't change CPU frequency via kernel tuner. Edit: I think it may have somthing to do with me losing root
-I can't install APKs from the system. I have to install the from Play Store or ADB
-System UI has a little tendency to stop responding
Edit1: After 12h of usage it only entered deep sleep for 7s according to kernel tuner
Edit2: I lose root after rebooting the phone, have to flash SuperSU from recovery.
Will edit if I find anything else. Still, pretty good job so far Chrono
Hey @ChronoMonochrome I was viewing the logcat from adb and found that this is repeated quite often, especially when the phone lags or stops responding: Error opening /dev/memcg/apps/uid_10009/pid_3083/memory.soft_limit_in_bytes; errno=2
Like here:
Code:
03-21 15:57:59.142 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10074/pid_4271/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.142 2170 2182 W SchedPolicy: add_tid_to_cgroup failed to write '4271' (Permission denied); fd=3
03-21 15:57:59.143 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10076/pid_5919/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.143 2170 2182 W SchedPolicy: add_tid_to_cgroup failed to write '5537' (Permission denied); fd=27
03-21 15:57:59.143 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10062/pid_5537/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.144 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10018/pid_5318/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.158 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10074/pid_4271/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.158 2170 2182 W SchedPolicy: add_tid_to_cgroup failed to write '4271' (Permission denied); fd=27
03-21 15:57:59.159 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10019/pid_5723/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.159 2170 2182 W SchedPolicy: add_tid_to_cgroup failed to write '5723' (Permission denied); fd=27
03-21 15:57:59.160 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10076/pid_5919/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.160 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10062/pid_5537/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.161 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10062/pid_5537/memory.soft_limit_in_bytes; errno=2
03-21 15:57:59.247 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10009/pid_3083/memory.soft_limit_in_bytes; errno=2
03-21 15:58:05.456 1934 1934 I chatty : uid=0(root) /system/bin/lmkd identical 72 lines
03-21 15:58:05.478 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10009/pid_3083/memory.soft_limit_in_bytes; errno=2
03-21 15:58:05.479 2170 2184 E memtrack: Couldn't load memtrack module
03-21 15:58:05.479 2170 2184 W android.os.Debug: failed to get memory consumption info: -1
03-21 15:58:05.533 1934 1934 E lowmemorykiller: Error opening /dev/memcg/apps/uid_10009/pid_3083/memory.soft_limit_in_bytes; errno=2
It may be important, I don't know
LOL downloading right now
Wow its fast, better than any rom that i used so far.
Keep it up man, good work
You guys have Android Oreo on this ancient device but not a single Sailfish OS builds? jesus developers get your priorities straight.
Can you give us some extra room on /data? I ran out of space quickly. I tried using parted and putting an extra gb to data by taking it from the UMS partition but I got a bootanimation infinite loop
Best ROM for daily use??
gt610 said:
Best ROM for daily use??
Click to expand...
Click to collapse
I've tried it, but it's so laggy as of now. Maybe media scanner was running or something, but was unusable even in app drawer. I'd suggest LineageOS 11 which seems to be the smoothest in my opinion.
#Henkate said:
I've tried it, but it's so laggy as of now. Maybe media scanner was running or something, but was unusable even in app drawer. I'd suggest LineageOS 11 which seems to be the smoothest in my opinion.
Click to expand...
Click to collapse
Can you tell me which recovery should i use, every time i flash a recovery my phone gets stuck in bootloop
gt610 said:
Can you tell me which recovery should i use, every time i flash a recovery my phone gets stuck in bootloop
Click to expand...
Click to collapse
I've installed LOS 11 by following those steps. If you have further questions about LOS 11 or something else which isn't related to this thread, please ask in the correct section or make a new thread under Q&A, so this thread would be clean.
[ 75% 3/4] glob device/coolpad/C106/bluetooth
ninja: error: '/home/mamarma9904/lineage/out/target/product/C106/obj_arm/SHARED_LIBRARIES/libtfa9890_intermediates/export_includes', needed by '/home/mamarma9904/lineage/out/target/product/C106/obj_arm/SHARED_LIBRARIES/audio_amplifier.msm8952_intermediates/import_includes', missing and no known rule to make it
14:11:12 ninja failed with: exit status 1
I have above error. how to fix this error?
this phone's kernel source does not released so I use similar device kernel.
or there is prebuilt kernel zImage.
https://github.com/mamarama9904/android_device_c106
https://github.com/mamarama9904/proprietary_vendor_coolpad_c106
https://github.com/LineageOS/android_kernel_leeco_msm8976
https://forum.xda-developers.com/cool1/development/kernel-stockpatched-t3830919