Testing ROM for Dell Venue 8 3830 (LineageOS 14.1)
Most of resources are available. But has some bugs.
It could be used for fun (Retroarch, E-book readers, etc)
Was build using as base Asus T00F lineage source files
I'm posting here asking for help to implement/fix missing features (if anyone still interested on such old device)
All source code to build is available on github (links bellow).
Working
Boots
Display
Touchscreen
Wi-FI
Virtual Navigation Buttons
Sound
Rotation
Bluetooth (since 2023-05-10)
Not working:
Camera
Known issues:
- ARM apps not working due mismatches with libraries (Houdini)
- Observed battery is draining quicker than expected.
# Testing Image (should be flash using FASTBOOT)
# updated 2023-06-13
# WARNING: MAY BRICK YOUR DEVICE PERMANENTLY! USE AT YOUR OWN RISK!!!!
https://drive.google.com/drive/folders/16iG6I-X83USPGPR13yUbg54S3Mn0Y7Ff?usp=share_link
Boot tablet in fastboot mode (volume down + Power) and use "flash_cmds.sh" (Linux) / "flash_cmds.bat" (Windows) to flash files through fastboot (note that proper driver drivers and fastboot must be installed)
If you wish to submit cmds manually:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase config
fastboot erase data
fastboot erase logs
fastboot erase factory
fastboot oem stop_partitioning
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system_img.img.gz
Source Files
# LOCAL MANIFEST
GitHub - pstglia/local_manifests at DELL_VENUE_LOS_14.1
Contribute to pstglia/local_manifests development by creating an account on GitHub.
github.com
Init a NEW repo
(repo init -u https://github.com/LineageOS/android.git -b cm-14.1)
Copy local manifest to .repo/local_manifests and sync it.
repo sync -c --no-tags --no-clone-bundle -j$(nproc --all)
# Kernel
GitHub - pstglia/linux: Linux kernel source tree
Linux kernel source tree. Contribute to pstglia/linux development by creating an account on GitHub.
github.com
NOTE: must be build using gcc 4.7 [1]. Checkout commit c7931763d41be602407ed9d71e2c0292c6597e00, update prebuilts link to this gcc
and build using kernel_build.sh script. If everything goes as expected, You'll have a new_boot.img created
# device/dell/P801_NoModem
GitHub - pstglia/android_device_dell_P801_NoModem: general device configuration for Dell Venue 8 (P801_NoModem)
general device configuration for Dell Venue 8 (P801_NoModem) - GitHub - pstglia/android_device_dell_P801_NoModem: general device configuration for Dell Venue 8 (P801_NoModem)
github.com
# vendor/dell/P801_NoModem
GitHub - pstglia/android_vendor_dell_P801_NoModem: Vendor files (configs, libs, etc)
Vendor files (configs, libs, etc). Contribute to pstglia/android_vendor_dell_P801_NoModem development by creating an account on GitHub.
github.com
# hardware/libaudio
GitHub - pstglia/hardware-libaudio at DELL_VENUE_LOS_14.1
hardware/libaudio repo (forked from Android-x86.org) - GitHub - pstglia/hardware-libaudio at DELL_VENUE_LOS_14.1
github.com
# external/boringssl
GitHub - pstglia/android_external_boringssl: Boring ssl (libcrypto & friends)
Boring ssl (libcrypto & friends). Contribute to pstglia/android_external_boringssl development by creating an account on GitHub.
github.com
# system/core
GitHub - pstglia/system-core at DELL_VENUE_LOS_14.1
system/core repo (forked from Android-x86.org). Contribute to pstglia/system-core development by creating an account on GitHub.
github.com
# external/tinyalsa
GitHub - pstglia/android_external_tinyalsa: tinyalsa 1.0.2
tinyalsa 1.0.2. Contribute to pstglia/android_external_tinyalsa development by creating an account on GitHub.
github.com
# external/icu
https://github.com/pstglia/android_external_icu/tree/DELL_VENUE_LOS_14.1
# external/external/apache-http
GitHub - pstglia/android_external_apache-http: android_external_apache-http
android_external_apache-http. Contribute to pstglia/android_external_apache-http development by creating an account on GitHub.
github.com
NOTES:- openssl 3.0 (Mint 21.1 - Vera) will not generate a compatible x509 sign key for kernel modules.
OpenSSL 1.1.1f generates an accepted key
Credits / Thanks:
- The LineageOS Team
- Android-x86 Team / Chih-Wei Huang for the amazing project and repositories (used one of them here so far)
- vampirefo for providing CWM recovery and valuable information
- Social-Design-Concepts for providing unlocked firmwares (required to boot custom Image)
- Fabio Júnior Chaves da Silva (again, owner of this tablet)
- Dell for providing kernel source (wouldn't hurt to include some AOSP code also, but it's better than nothing )
- AlaskaLinuxUser AKLU from Youtube. Lot's of explanations about Android & Lineage.
[1] - https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.7/
How can one Help?
ikram.senguen said:
How can one Help?
Click to expand...
Click to collapse
Hi,
This is the list of missing features / issues:
Choose one of your preference and hands on!
update 2022-05-31: Audio and Rotation were fixed.
kernel display driver was updated. Experience is smoother
-[FIXED] Wi-fi is not working:
Help wanted: Fix code and make it work:
Status so far: Fixed.
It will work on boot if you keep it enabled. If you disable Wi-fi from settings and try to re-enable (or switch on/off airplane mode), it will stop working until you boot it again.
update 2022-06-02: Discovered that you can't ioctl wlan0 to up state when you disable it (using root + proper capabilities).
However, if you rmmod bcm4330 and insmod it again, you can enable it.
It seems a driver issue.
update 2022-06-03: Using stock kernel module for network, no issues with ioctl after disbling wi-fi
update 2023-06-13: Using T00F bcmdhd source with some changes to enable 4330, it runs ok.Now it's using compiled drivers for wi-fi instead of stock ones (except for firmwares)
-[FIXED] Sound is not working:
Help wanted: Investigate what's wrong and fix it
Status: Fixed [working since updated 2022-05-29]
Note: libaudio from stock image couldn't be loaded, so generated one from Android-x86 libaudio code (see [2]).
Maybe adjusts are needed on source, config and Boardconfig files.
update 2022-05-22: all libs are being loaded, but there are some errors when trying to load codecs. Config files must be checked (as well libs);
- [FIXED] Navigation menu is not being displayed:
Help wanted: Discover why is not being shown and fix it
Status: Fixed (created a overlay on device tree and made "def_force_show_navbar" to be enabled - see commit 8768b512c08b5fc60a7d7674ffce7c3a23a7857a)
- Camera is not working:
Help wanted: Make it work
Status so far: HALs must be copied. Possibly lot's of shims and Voodoos/Mojos required.
- [FIXED] Sensors are not working:
Help wanted: Make it work
Status: Fixed (replaced sensor_hal_config files)
- [FIXED] Bluetooth is not working:
Help wanted: Make it work
Status do far: Fixed (used harware/broadcom/libbt instead of vendor lib)
- [FIXED] Port/Enable zram to kernel:
Help wanted: Porting
Status: Enabled from stage tree (it was there all the time).
Seems to be working (at least swap was mounted using it)
- [FIXED] Sometimes backlight doesn't light up after resume
Status: Fixed. This ocurred when an out of range bright level was used ( > 100)
Edited liblights code (device/dell/P801_NoModem/liblights) and included a small check to ensure/force valid values ( from 0 to 100)
- [FIXED] ADB only works using network. Not working using USB
Status: Fixed. Copied drivers/usb/gadget changes from T00F Asus kernel and applied to Venue kernel
- Elevated Battery draining (specially on suspend attempt)
Something is blocking system from suspend. If you check dmesg, it keeps an infinite loop of suspend process (disable tasks, disable CPU's) and abort.
At first, wakeup reason is the "misterious" NETLINK. However, even blocking it and some other wakeup_sources it wakes.
This shows suspend backtrace (got from dump_stack):
Code:
[ 697.149972] Call Trace:
[ 697.149984] [<c19f90f3>] dump_stack+0x16/0x18
[ 697.149990] [<c12bc9c1>] resume_irqs+0xa1/0xe0
[ 697.149996] [<c12bca2f>] resume_device_irqs+0xf/0x20
[ 697.150004] [<c156a151>] dpm_resume_noirq+0x1a1/0x2b0
[ 697.150010] [<c156a8d0>] dpm_resume_start+0x10/0x20
[ 697.150015] [<c1288945>] suspend_enter+0xa5/0x260
[ 697.150022] [<c1a03cbd>] ? sub_preempt_count+0x3d/0x50
[ 697.150028] [<c1a03cbd>] ? sub_preempt_count+0x3d/0x50
[ 697.150034] [<c19f4646>] ? printk+0x3d/0x3f
[ 697.150040] [<c1569adc>] ? dpm_show_time+0xbc/0xf0
[ 697.150046] [<c156b952>] ? dpm_suspend+0x132/0x1e0
[ 697.150052] [<c1288baf>] suspend_devices_and_enter+0xaf/0x220
[ 697.150057] [<c1288fb8>] pm_suspend+0x298/0x300
[ 697.150063] [<c1289935>] try_to_suspend+0xa5/0xc0
[ 697.150069] [<c1a0091d>] ? _raw_spin_unlock_irq+0x1d/0x40
[ 697.150076] [<c125ebad>] process_one_work+0x11d/0x3d0
[ 697.150082] [<c14b091e>] ? __delay+0xe/0x10
[ 697.150088] [<c125f239>] worker_thread+0xf9/0x320
[ 697.150093] [<c1a00966>] ? _raw_spin_unlock_irqrestore+0x26/0x50
[ 697.150099] [<c125f140>] ? rescuer_thread+0x2b0/0x2b0
[ 697.150104] [<c1264cf4>] kthread+0x94/0xa0
[ 697.150112] [<c1a07077>] ret_from_kernel_thread+0x1b/0x28
[ 697.150117] [<c1264c60>] ? kthread_create_on_node+0xc0/0xc0
[ 697.150121] Wakeup from IRQ 32 penwell_otg
/sys/kernel/debug/mid_pmu_states and other files can give hints about the root cause.
Anyway, if you want to adventure yourself on trying to solve the problem, be my guest
[1] - https://github.com/pstglia/linux/tree/DELL_VENUE_LOS_14.1/modules/wlan/PRIVATE/bcm43xx
[2] - https://github.com/pstglia/hardware-libaudio/tree/DELL_VENUE_LOS_14.1
Additional info for those interested on improve this:
1) Added a debug service that collects dmesg & logcat 3 times every boot
output is recorded on /data/log_debug_venue8_3030.txt
2) ADB from usb cable is not working, but is working from network. This way, I suggest you enable these on "Developer options":
- Root acess: Select "ADB only".
- Android debugging
- ADB over network (note: You must connect to a network prior - IP and port will be displayed when enabling this option)
Once done, from PC, you can connect to adb:
# (will connect to tablet)
adb connect TABLET_IP_ADDR
# (will restart adbd on tablet, to root mode)
adb root
# (will connect again, now with root acess)
adb connect TABLET_IP_ADDR
Click to expand...
Click to collapse
3) If you want to make any change to /system on living image, you must remount /system with write privileges:
- Ensure you enabled adb over network as described on step 2
- connect to table and remount /system:
adb shell
mount -o rw,remount /system
Click to expand...
Click to collapse
How difficult would it be to port to the 7840? Or alternatively, would it be possible to help me learn how I could build it myself?
theabnormalguy said:
How difficult would it be to port to the 7840? Or alternatively, would it be possible to help me learn how I could build it myself?
Click to expand...
Click to collapse
Hi,
It has a medium/high level of difficult, depending how "perfect" do you want your port.
And more than difficult, it's *extremelly* time consuming. You must be prepared to spent weeks/ months in order to try to make something work.
And before starting anything, be sure is viable. A crucial point is having kernel source files for your device.
without it, don't waste your time.
In your case, take a look at opensource.dell.com
Learning: As a start, I'd recomend you to watch these videos:
https://www.youtube.com/c/AlaskaLinuxUserAKLU/playlists
You'll need to learn all of these (not limited to):
- Learn some C/C++ and java. You'll have to read source code to understand basicallyhow it works
- Learn Unix/Linux terminal commands. I'll need lots of find, grep, cd, cat, etc....
- Learn shell script
- Learn git
- Learn how to compile and cusomize a kernel
- Understand how Android source code/components are strutured (AOSP)
During your development, you'll need to carefully look at log files, include debugging info on scripts/codes, think,research, deduce, test, retest, test again,back some steps an try new appoaches.
And finally, I won't be working on any other device. After finishing this one I'm working on (or giving it up), not going to waste my time on custom roms sonner.... I have a life to live
Good luck
Project die?
FYA_EXel said:
Project die?
Click to expand...
Click to collapse
Not yet. I'm just looking for courage to go on.
If you see courage nearby, tell her that I'm looking for her
I intent to make bluetooth work and improve battery life. Camera is not a priority.
Remember everyone that source code is available. Everyone is free and invited to help improving this image.
Regards
pstglia
When I flash this rom, I get to the Lock Screen and it hard freezes. Anyone else get this problem? Thanks for all your work @pstglia
Update: I fixed it by wiping the data partition. This is incredible; this tablet has never been so smooth. Any advice on adding GAPPs?
the_Victorian said:
When I flash this rom, I get to the Lock Screen and it hard freezes. Anyone else get this problem? Thanks for all your work @pstglia
Click to expand...
Click to collapse
You are able to boot it but when locking screen you can't return to operation, having to boot it again.
Is this your issue?
If so, it's a known issue where backlight bright level goes to zero. If you blindly move the bright slider, you can have image again (or changing bright values bellow /sys using adb)
pstglia said:
You are able to boot it but when locking screen you can't return to operation, having to boot it again.
Is this your issue?
If so, it's a known issue where backlight bright level goes to zero. If you blindly move the bright slider, you can have image again (or changing bright values bellow /sys using adb)
Click to expand...
Click to collapse
Wow, thanks for your quick reply! I was just dumb and didn't wipe my android 4.4 data before installing; that fixed it. I have been tinkering trying to get GAPPs installed but run into error 70 in CWM when I do. Have you had success?
the_Victorian said:
Wow, thanks for your quick reply! I was just dumb and didn't wipe my android 4.4 data before installing; that fixed it. I have been tinkering trying to get GAPPs installed but run into error 70 in CWM when I do. Have you had success?
Click to expand...
Click to collapse
I have installed opengapps (x86, 7.1, pico). Don't remember having issues installing it.
But makes tablet really slow most of time.
pstglia said:
I have installed opengapps (x86, 7.1, pico). Don't remember having issues installing it.
But makes tablet really slow most of time.
Click to expand...
Click to collapse
Hmm that's interesting. I'm trying the same file but every recovery I try has given me error 7. Will continue tinkering. Something to do with system mount permissions maybe?
the_Victorian said:
Hmm that's interesting. I'm trying the same file but every recovery I try has given me error 7. Will continue tinkering. Something to do with system mount permissions maybe?
Click to expand...
Click to collapse
Afaik error 7 means package doesn't match the device. On Lineage images I bypass it by editing update-binary/updater-script inside META dir.
However I think opengapps does not perform these checks...
Have you tried formatting your cache partition before applying opengapps package?
Which recovery version are you using? Is the thethered one from SDC/Vampirefo?
I thought this moment would never come , I always dreamed of a custom rom for this device, I hope you can continue developing it
quevon24 said:
I thought this moment would never come , I always dreamed of a custom rom for this device, I hope you can continue developing it
Click to expand...
Click to collapse
Hi, I'll try to. But my limited knowledge doesn't allow me to advance the way I wish.
So, do not expect something perfect, fast and stable...
If we had some developer that could help on this, maybe you could have a really nice rom.
Note: All sources are available on github. See 1st post.
If I achieve some progress I'll share here.
The image I have is bootable and you can test anything if you understand the risks of potentially brick your device.
If you have nothing to lose, give a try
pstglia said:
Hi, I'll try to. But my limited knowledge doesn't allow me to advance the way I wish.
So, do not expect something perfect, fast and stable...
If we had some developer that could help on this, maybe you could have a really nice rom.
Note: All sources are available on github. See 1st post.
If I achieve some progress I'll share here.
The image I have is bootable and you can test anything if you understand the risks of potentially brick your device.
If you have nothing to lose, give a try
Click to expand...
Click to collapse
I just install the rom using Windows 11, i have the stock rom(android 4.2.2, 4.3 and 4.4.2) in case i brick the tablet.
I used apkmirror to install chrome x86 version, i can't use youtube because the lack of google play services
quevon24 said:
I just install the rom using Windows 11, i have the stock rom(android 4.2.2, 4.3 and 4.4.2) in case i brick the tablet.
I used apkmirror to install chrome x86 version, i can't use youtube because the lack of google play services
Click to expand...
Click to collapse
You can use opengapps for youtube & google stufff.
But at the current stage of this rom, it will make tablet really slow...
pstglia said:
Hi,
This is the list of missing features / issues:
Choose one of your preference and hands on!
update 2022-05-31: Audio and Rotation were fixed.
kernel display driver was updated. Experience is smoother
-[FIXED] Wi-fi is not working:
Help wanted: Fix code and make it work:
Status so far: Fixed.
It will work on boot if you keep it enabled. If you disable Wi-fi from settings and try to re-enable (or switch on/off airplane mode), it will stop working until you boot it again.
update 2022-06-02: Discovered that you can't ioctl wlan0 to up state when you disable it (using root + proper capabilities).
However, if you rmmod bcm4330 and insmod it again, you can enable it.
It seems a driver issue.
update 2022-06-03: Using stock kernel module for network, no issues with ioctl after disbling wi-fi
-[FIXED] Sound is not working:
Help wanted: Investigate what's wrong and fix it
Status: Fixed [working since updated 2022-05-29]
Note: libaudio from stock image couldn't be loaded, so generated one from Android-x86 libaudio code (see [2]).
Maybe adjusts are needed on source, config and Boardconfig files.
update 2022-05-22: all libs are being loaded, but there are some errors when trying to load codecs. Config files must be checked (as well libs);
- [FIXED] Navigation menu is not being displayed:
Help wanted: Discover why is not being shown and fix it
Status: Fixed (created a overlay on device tree and made "def_force_show_navbar" to be enabled - see commit 8768b512c08b5fc60a7d7674ffce7c3a23a7857a)
- Camera is not working:
Help wanted: Make it work
Status so far: HALs must be copied. Possibly lot's of shims and Voodoos/Mojos required.
- [FIXED] Sensors are not working:
Help wanted: Make it work
Status: Fixed (replaced sensor_hal_config files)
- [FIXED] Bluetooth is not working:
Help wanted: Make it work
Status do far: Fixed (used harware/broadcom/libbt instead of vendor lib)
- [FIXED] Port/Enable zram to kernel:
Help wanted: Porting
Status: Enabled from stage tree (it was there all the time).
Seems to be working (at least swap was mounted using it)
[1] - https://github.com/pstglia/linux/tree/DELL_VENUE_LOS_14.1/modules/wlan/PRIVATE/bcm43xx
[2] - https://github.com/pstglia/hardware-libaudio/tree/DELL_VENUE_LOS_14.1
Click to expand...
Click to collapse
sry, lack of response due to lack of knowledge: thought this is about Venue 7840
ikram.senguen said:
sry, lack of response due to lack of knowledge: thought this is about Venue 7840
Click to expand...
Click to collapse
Nope, this is for Venue 8 3830
Related
TIME TO MOVE ON
i wil be on xperia section
i am happy that i could help this section
Best Regards, Happy Cookling and Programing!
Hy all
I started this tread because the interest to android is growing
I invite all people with linux knowledge or C programing skills to join
If you know some hardware programing is better
We need
- developpers
- testers
i will not post an guide how to setup the compiler and set variables
if you dont know this stuff please stick to Google Android thread and dont post here stupid questions as IT IS READY / WHEN WILL IT BE READY
WE DO THIS IN OUR SPARE TIME AND WE HAVE FAMILY AND LIFE
So shell we invite the penguin to our phones?
WIKI Page
(Thanks Bikor_gj)
http://wiki.xda-developers.com/index.php?pagename=Niki_Android
GIT Trees
Vogue
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue
MSM
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.25
Reserved For Messages
Build Instructions for the ones that want to help
- Create working dir:
Code:
mkdir ~/android-kernel
- Go to the dir:
Code:
cd ~/android-kernel
- Clone the Linuxtogo GIT:
Code:
git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git
- Go into newly created dir:
Code:
cd ~/android-kernel/kernel
- Create a new branch, call it htc-msm and link it to the official htc-msm development branch:
Code:
- Descend into the "main" android dir:
Code:
cd ~/android-kernel
- Get toolchain:
Code:
wget http://www.codesourcery.com/gnu_too...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
- maybe you need to rename the just downloaded file (because after .tar.bz2 wget has added ?lite=arm). (HINT FOR LINUX-NEWBIES: USE TAB TO COMPLETE KNOWN FILENAMES!! - In this case type: mv arm(TAB) arm(TAB) -> backspace till 'bz2' is the last word)
Code:
mv arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2\?lite\=arm arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
- unpack the toolchain:
Code:
tar -xjf arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
- ascend again into the 'kernel' directory:
Code:
cd ~/android-kernel/kernel
- make the kernel:
Code:
git checkout -b htc-vogue origin/htc-vogue
You also have to use
Code:
make vogue_defconfig ARCH=arm
- export path so the newly downloaded toolchain will be used instead of your default compiler (which would compile for your computer instead of your phone):
Code:
export PATH=~/android-kernel/arm-2008q1/bin:$PATH
- make the zImage-file:
Code:
make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
Now the zImage file is created inside the directory kernel/arch/arm/boot.
When uploading this to your phone, remember that you only have to replace the zImage after each kernel build - the Linux environment on top of the kernel can just stay the same, so initrd (which is the ramdisk filesystem) can stay the same.
BR
Reserved For Kernel Status
Kernel status
no more power button //thanks biktor_gj
nike mtype added
audio working
call working
data working
sms unknown //due to keyboard and ts
keyboard screwed // somethings not right needs investigation
OnSreenKeyboard working
Touch screwed // SOLVED
when this kernel probelms will be solved i will release the new kernel
I have knowledge of both C and linux so I vollunteer
hi,
i can be a tester... also i have some little linux knowledge...
I have limited knowledge of both c and linux, so I possibly could help.
It seems useful however to setup an SVN or something, so even 'non-registered' developers can write patches and submit them for review. You can set up such an SVN for free at assembla.com, together with a wiki, TRAC and more. They even say you can ask for more storage space and stuff if your project is an open-source project.
If you have such an SVN developers like me can help without making any false promises of some sort.
I hope you know what I mean, it sounded better in my head
i know linux and i can do beta tester. i'm studying engineering too.
i also know linux and a bit of C...i can do testing too.
as you already know, I'm in too for development...
i will try the new kernel asap...
I tried this kernel and indeed, the keypad works on mine!
(touched the TS though, just because you said I wasn't allowed ) It froze, so reboot...
awesome! keys work all good! numbers work and also dpad and enter works!
(by the way: how will you make it possible to enter text? android is coded to enter numbers...
the_fish said:
awesome! keys work all good! numbers work and also dpad and enter works!
(by the way: how will you make it possible to enter text? android is coded to enter numbers...
Click to expand...
Click to collapse
I believe by the end of this year or somewhere in the beginning of 2009 Google is making a system for creating software input methods, which would theoretically allow us to write an application that would reroute direct hardware input. I think. We'll have to see what the future will (or the talented developers here) bring.
man, awesome!!! good job, jerpelea. keys work great!!
graey said:
I believe by the end of this year or somewhere in the beginning of 2009 Google is making a system for creating software input methods, which would theoretically allow us to write an application that would reroute direct hardware input. I think. We'll have to see what the future will (or the talented developers here) bring.
Click to expand...
Click to collapse
ok... the onscreen keyboard would be ok for the time we have to wait
Jerpelea: Why do you want Ubuntu as dev os? I'm using OpenSuSE and am able to build the kernel.
I am thinking (since 2 weeks) to try Ubuntu again (used to use it), but may take while before I get to it...
Boylen said:
Jerpelea: Why do you want Ubuntu as dev os? I'm using OpenSuSE and am able to build the kernel.
I am thinking (since 2 weeks) to try Ubuntu again (used to use it), but may take while before I get to it...
Click to expand...
Click to collapse
I think he is just saying that because it's easier for people to use??
works fine for me on vanilla debian
new kernel works fine screen still too responsive keys work calls work
it works! but after few minutes my nike is auto-turned off :O
garsim said:
it works! but after few minutes my nike is auto-turned off :O
Click to expand...
Click to collapse
i guess we have turn the auto turn off in wm to unlimited or run it on usb plug...
MOD EDIT: Thread closed at Volk's request. You can find his CM 10.2 here.
CM10.1 for WAVE and WAVE 2
Android Jellybean 4.2.2
READ http://code.google.com/p/badadroid/ and http://code.google.com/p/badadroid/wiki/FrequentlyAskedQuestions BEFORE POSTING (thanks to huntkb for updating it)
FEATURES
Android 4.2.2
CM sources of 21.10.2013
Updated to linux kernel version 3.0.86
272 MB RAM
F4k 720p patch for bigmem kernels (Video Fix)
New key Mapping:
- call key as CALL, Middle as HOME, endcall as ENDCALL
- Long press ENDCALL will show power menu
- lock key as POWER, framework patch is not yet ported
- Navigation Bar activated
- PIE control can be activated with Expanded desktop
GAPPS
http://goo.im/gapps/gapps-jb-20130301-signed.zip full gapps
flash through CWM (recovery)
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- GPS - http://forum.xda-developers.com/showpost.php?p=47209249&postcount=1371
- Conference Calls
- Bluetooth headset in calls
- Some problems with audio codec settings, but generally it should work
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM: http://www.multiupload.nl/HYU95BQ6D6
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- install zip from sdcard
- choose zip from sdcard
- cm-10.1-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393
CHANGELOG:
Lite ROM by Hero355 based on v2.1 http://forum.xda-developers.com/showpost.php?p=47351443&postcount=1514
v2.1 http://www.multiupload.nl/HYU95BQ6D6
- CM sources 05.11.2013
- [NETWORK] Added WCDMA only (UMTS900/2100) Mode selection
- Fixed modem power mode transition.
- [GPRS] Added suspend/resume network
- [SIM] Added basic SIM_IO implementation: reading Contacts, Messages, Voicemail number, SPN, ICCID from SIM card
- [SMS] Code optimization and cleanup. Thanks for Rebellos
- [SMS] Added MMS receiving
- Updated audio codec gain table from bada proprietary files
- And included all another updates after v2.0
BT fix for Wave 2 http://www.multiupload.nl/JAPFB1FLNS Thanks Tigrouzen for idea and BenzoX for testing
Just Flash it via Recovery
Kernel update for v 2.0 http://www.multiupload.nl/E68CJFUHGK
- Fixed wave 2 screen calibration. thanks to krischat1001
RIL_update2 for v2.0 http://www.multiupload.nl/E1JBJU4LTS
- some memory leaks fixed
- set low level debug AMSS
- some another fixes, probably can resolve restart in long idle state
RIL Update for v2.0 http://www.multiupload.nl/OP6YZQJ09Z
- Fix for IMSI reading
I hope now mobile internet will be work on all phones
APN settings should load automatically. Most of APN is stored in ROM in system/etc/apns-config.xml
If APN is not loaded automatically check this file and add APN settings in it, if there are no in it.
v2.0 http://www.multiupload.nl/PR4599CF5V
- CM sources 21.10.2013
- Mobile internet is fixed
- Fixed search available networks and select networks
- Fixed PIN and PUK entering
- Fixed SIM PIN enable/disable/change
- Fixed sending MMS, receiving is still not working
- Fixed network indicator
v1.3 http://www.multiupload.nl/DYXUMPUCQX
- CM sources of 26.09.2013
- [RIL] Сompleted CALL interface, except conference call, but i really never use it before.
If you report bug please attach logs with detailed description, i really tested most of causes with hangup, activate and holding calls and etc, but it is too many cases, and probably i didn't meet some and don't know that this cause is exist.
- Some optimization from platform side, ported from aries
RIL Update2 for v1.2 http://www.multiupload.nl/NMIONOUBJ9
- Reworked Call interface
- Just flash it via Recovery
RIL Update for v1.2 http://www.multiupload.nl/CSTPY6UKNU
- [SIM] Corrected reading SMSC from SIM card
- [CALL] Added DTMF support
- Just flash it via Recovery
v1.2 http://www.multiupload.nl/3QF7PV7HJR
- CM sources of 17.09.2013
- Added TARGET_ARCH_LOWMEM for Dalvik
- Fixed gsm voicecall common setting in audio codec (Big Thanks for Tigrouzen)
- Fixed all audio ril pathes except Bluetooth audio pathes
Kernel Update for v1.1 http://www.multiupload.nl/LM89AO62TG
- Audio recording and video recording fixed
- So now we can use VoIP applications on wave with Wi-Fi
- Audio in call is still broken
Big thank to Rebellos. i just found good topic on ALSA forum with solution and Rebellos implemented solution
v1.1 http://www.multiupload.nl/H0THJFGQAQ
- CM sources of 14.08.2013
- Fixed vibrator (Thanks to Rebellos)
- Fixed ENDCALL button behavior(Forgot to include it in v1)
v1 http://www.multiupload.nl/KT7LG7HXDJ
Initial release
CM sources of 8.08.2013
Update compared to Rebellos CM10 ROM http://forum.xda-developers.com/showthread.php?t=1851818
- Android 4.2.2 CM10.1 based
- Updated to linux kernel version 3.0.86
- ROW i/o scheduler
- 272 MB RAM
- F4k 720p patch for bigmem kernels (Video Fix)
- New key mapping
- Navigation bar activated
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-10.1 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.1/local_manifest.xm
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
cd .repo
wget [url]https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.1/local_manifest.xml[/url]
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
good job
you are amazing...:good::good:
I was hoped to my phone again
i will be glad, if some one will make screenshots and/or video review, i will add it in OP
disappointment :'(
.
thanks volk great job u are the best... i must ask a question for cm10.1 installation system memory 370mb free but my wave2 has got 90MB free . how can i delete this memory and which apps use system memory?
What is the main difference between this and FnF? Thanks
ibrahim1170 said:
thanks volk great job u are the best... i must ask a question for cm10.1 installation system memory 370mb free but my wave2 has got 90MB free . how can i delete this memory and which apps use system memory?
Click to expand...
Click to collapse
If you used CM10 Rebellos ROM you don't need check memory, just flash .zip via recovery and full wipe (all data will be deleted in android)
If not, try factory reset or reflash bada(in all cases you will lost all data in bada)
volk Thank you very much. king. I respect you
very good slim gapps for jb 4.2.2 please
nad4321 said:
What is the main difference between this and FnF? Thanks
Click to expand...
Click to collapse
Another Partition Layout: (FNF NAND - remove bada, FNF SD - eat some SD space for android, and as i know need backup SD before installation, restore after installation)
Easy installation
Another key mapping
Navbar and PIE control
Maybe something else
nice work man
but my simcard not detected
rom is fast & smooth
of course you set governor to
there is a alot option in this rom at compare to other rom
if you make call phone You'll all be happy
volk204 said:
reserved
Click to expand...
Click to collapse
Thank u so much volk ,
in new key mapping ,what about back key in android ?
someone plz test , 318mb ram kernel works or not ?
because for high quality games , 318mb ram kernel is important.
thanks a million to volk
blue966 said:
nice work man
but my simcard not detected
Click to expand...
Click to collapse
is it first installation? or you came from Rebellos CM10? do you had the same problem with CM10?
and for checking issue i need logcat -b radio
kktkaran said:
Thank u so much volk ,
in new key mapping ,what about back key in android ?
someone plz test , 318mb ram kernel works or not ?
because for high quality games , 318mb ram kernel is important.
thanks a million to volk
Click to expand...
Click to collapse
Back key is in navbar or in PIE control
But we can navigate in android without back key using touchscreen and home key
Kernel is 272MB RAM,
CM10 kernels will not work with CM10.1
thanks very much, and what about google play market?
monchester said:
thanks very much, and what about google play market?
Click to expand...
Click to collapse
download http://goo.im/gapps/gapps-jb-20130301-signed.zip full gapps and flash via recovery
thanks volk
can i connect my phone to charger when CM10.1 is on ?
Adam-110 said:
thanks volk
can i connect my phone to charger when CM10.1 is on ?
Click to expand...
Click to collapse
the same as for CM10
Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery
added to OP
volk204 said:
the same as for CM10
Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery
added to OP
Click to expand...
Click to collapse
thank you anyway... I appreciated
DELETED
Installation Instructions
Comming from a Pre "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file. (You WILL get an assert error!)
Read the warning on the screen.
Flash the ROM again!
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Comming from "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM or later
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file.
Ignore the warning on the screen.
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Change Log:
NOTE: All future changelogs will be attached below!
Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839 --> Slim-venturi-4.4.2.beta.1.9-UNOFFICIAL-20131223-1727 changes:
SlimRoms/frameworks_base:
2013-12-22: systemUI: fix notification dissapearing during recreation and possible <@Lars Greiss>
Code:
app crashes due that binded notifications are not there anymore
as well small cleanup
Change-Id: Ieed143088a55693fc56e6526e6b349d72b7b25cc
2013-12-22: Merge "fb: use SlimActions for torch tile and send as qualified user" into kk4.4 <@Gerrit Code Review>
2013-12-22: Merge "fb: lock statusbar recreation and release after ticker is done" into kk4.4 <@Gerrit Code Review>
2013-12-22: fb: use SlimActions for torch tile and send as qualified user <@Lars Greiss>
Code:
the broadcast and do not collape the panel bar
as well send with qualified user the IME switcher broadcast.
Change-Id: Ibad8b4f908e6d701999712f58b9996cd7a805fc4
2013-12-21: fb: lock statusbar recreation and release after ticker is done <@Lars Greiss>
Code:
In rare cases it happens that the ticker call just happened and a recreation
was called which results in a crah due of the missing binder.
To avoid it lock the recreation when a ticker call is in progress
and release it after it is done and notify the recreation to go ahead
Change-Id: Iedbf858bdb2ac2ad97563e344a571b384e17cfc7
2013-12-21: trds:[framework] dark images adjustments <@kroz>
Code:
Change-Id: Ie038c4a1aa535708c23f099fb5e836407e3d1603
SlimRoms/packages_apps_Camera2:
2013-12-22: TrueView Returns! <@Gerrit Code Review>
Code:
This adds the ability to view the complete sensor frame image
rather than the cropped preview used by AOSP to fill the entire
surface.
Change-Id: I79b14a165c66fa4f8b8e43598bd6a80e4de1c08b
2013-12-22: Fix Smart Capture label display <@Lars Greiss>
Code:
Change-Id: Ia3cceda0bf7fec21f2d019f07d416bfe8ebf211d
2013-12-22: Fixes Mako continues focus problem <@Lars Greiss>
Code:
rebase
Change-Id: I25187998003d357ec5ed3b10329fb39941f47bea
Signed-off-by: Josue Rivera <[email protected]>
2013-12-22: camera: Add ZSL support for Samsung/Qualcomm cameras <@Lars Greiss>
Code:
* Preview management for Samsung/Qualcomm cameras
Patchset 3: merge conflicts fixed
build errors fixed
PatchSet 4: codestyle corrections
Change-Id: Ib36bd21c9a76b45bced3eee2f25acc35b5d82b30
SlimRoms/packages_apps_InCallUI:
2013-12-21: Merge "TRDS: Dark InCallUI" into kk4.4 <@Gerrit Code Review>
2013-12-19: TRDS: Dark InCallUI <@kroz>
Code:
PS2:
- moved into right folder
PS3:
- redirect colors of original layout xml
Change-Id: I5bcfeb692bc4653e240df7c47216826452ee7d47
SlimRoms/packages_apps_Settings:
2013-12-22: Merge "First translation of Settings for KitKat" into kk4.4 <@Gerrit Code Review>
2013-12-18: First translation of Settings for KitKat <@gwindlord>
Code:
"Go To Sleep" paraphrased
Removed whitespace
Change-Id: I666cb60da3a0751ba1d4f351c2a46b1b159d9dd3
SlimRoms/packages_apps_Torch:
2013-12-22: Torch: add better error handling and added fallback mechanism <@Lars Greiss>
Code:
The handling of the Torch if an exception occured was very bad and
it was easy to break:
- notify the user with toast if the camera interface is not pressent
- catch the case that sys led controlled devices have wrong permissions
(eg third party kernel) and torch will completly crash.
Checking now if sys init is present.......if not successful
try to switch back to the camera interface.
- send broadcast change only if the state really switched
- when error occured turn off the service and the notification
- cleanup
- send broadcast with qualified users
Change-Id: Iabeb3b5f1c17d784a06c154f9a33e8d3d5214b7d
2013-12-21: make torch to a real system app <@Lars Greiss>
Code:
give it the correct permissions to allow to write
to sys interface with less permissions needed to
keep security alive
Thanks Alex for the hint to the hidden API
and gmillz for the idea
Change-Id: I44f70bdf3ecfb57ccac85eebe61e57a163bdf501
SlimRoms/vendor_slim:
2013-12-22: push to 1.9 <@Lars Greiss>
Code:
Change-Id: I4c4aab6fbd8440cda3649b1d77351aa0563dd15c
2013-12-22: push to 1.8 for weekly <@Lars Greiss>
Code:
waiting for feedback on last patches then we start jenkins
Change-Id: I1b8f5dcb6f8620506dfc4399b75c56802a3bd8e1
Older logs:
2013-12-22: clean up: movefiles.sh is no longer needed... <@Meticulus>
2013-12-22: overlay: SlimCenter overlay for ota. <@Meticulus>
Code:
-I've found that with just a few small adjustments you can redirect
SlimCenter to another url to check for updates.
2013-12-22: overlay: BOARD_USE_LEGACY_TOUCHSCREEN device tree flag. <@Meticulus>
Code:
-Everytime I repo sync my framework base commit to fix the touch screen
gets wiped out. In order to preserve it, I'm putting it in the overlay.
2013-12-20: ota: testing <@Meticulus>
2013-12-20: LVMv2: phase out the use of mmcblk0p14 as extra space. <@Meticulus>
Code:
-With the implementation of LVMv2, we don't need to use mmcblk0p14
(/vendor, /system/vendor) as extra space.
-mmcblk0p14 is now in the logical volume group "lvpool" along with
mmcblk0p13 and mmcblk0p16.
2013-12-20: ota: change device name from venturi to YP-G70 <@Meticulus>
2013-12-20: ota: removed beginning and ending spaces.. <@Meticulus>
2013-12-20: ota: ota update manifest. <@Meticulus>
Code:
-Initial commit of the ota manifest.
2013-12-19: slim.mk: build type switch. <@Meticulus>
Code:
-Switch from common full tablet to common full hybrid...
2013-12-19: init.venturi.rc: fix a small typo.. <@Meticulus>
2013-12-19: LVMv2: add lvm services to init.venturi.rc. <@Meticulus>
Code:
-This was left out of my initial commit here:
https://github.com/Meticulus/slim_device_samsung_venturi/commit/7ccd47c874f9a00c0397c8e8f17f3faaf72e256b
-This is absolutly neccessary for LVM...
2013-12-19: twrp: Correct screen resolution. <@Meticulus>
2013-12-18: LVMv2: initial implementation system(600M) <@Meticulus>
Code:
-Logical Volume Management
-The YP-G70 only has a 290m /system partition and this is not enough
to accomodate KitKat + full gapps. So, I'm implementing LVM so that
we can get dynamic volume resizing without having to change the under-
lying partitions.
-Partitions in Logical Group (Aprox 2.1G)
-- /dev/block/mmcblk0p13 (normally /system)
-- /dev/block/mmcblk0p16 (normally /data
-Logical volumes
-- /dev/lvpool/system (600M)
-- /dev/lvpool/data (100% remaining, aprox 1.5G)
-Installation Notes
--On the first flash, if the system logical volume is not present or
is less than 600M there is an assert error. This is so that if anyone
needs to backup information contained in /data, they can. In order to
proceed with the installation, the zip must be flashed a 2nd time.
--During the 2nd flash partitions in the logical group are wiped and
the logical volumes are created and formated then the /etc/fstab and
/etc/recovery.fstab are switched so that, when we hand everything off
to the normal rom installer, the new logical volumes are mounted.
-Reverting to a PRE-LVM ROM
--In the YP-G70 the "recovery", be it CWM or TWRP and in the kernel's
recovery-ramdisk. So in order to get a different recovery you just
flash a different kernel. So to get back to a PRE-LVM ROM, you just:
1. Reboot to recovery like normal.
2. Flash your PRE-LVM ROM like normal.
-- Note: All we really care about at this point is that the kernel
(boot.img) gets flashed. Ignore any other errors!
3. After the flash, Power off.
4. Hold volume up and power on, till you get to recovery.
5. Full wipe, including /system
6. Flash ROM + Gapps like normal
-Future Considerations
--LVMv2 allows us to quickly change the size of the system partition
as Android grows in size without having to manually repartition.
Manually repartitioning might cause unforseen problems with legacy
software.
-Meticulus
2013-12-17: recovery init: adb without /system <@Meticulus>
Code:
This allows "adb shell" to function when /system partition is not mounted
or for any reason /system/bin/sh is unavailable.
When /system IS mounted then adb uses mksh is used via /system/bin/sh
When /system IS NOT mounted then adb uses busybox via /sbin/sh
2013-12-14: Removed torch from build. <@Meticulus>
Code:
Torch isn't working at the moment anyways. May readd later!
2013-12-14: twrp: defined custom power key and fixed screen timeout problem. <@Meticulus>
2013-12-14: Initial commit <@Meticulus>
Super mine again!
BAH!! y u release while i'm at work....
Gonna test when i get home....
Flashy flashy, its like Christmas but better! no wrapping paper to clean up or relatives to dispose of.
Somehow I knew I would come on today to find KitKat available. Trying it now, will update later.
EDIT: No options for hardware buttons?
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I didn't really solve it, per say. I put in a cheap hack to change the permission of the directory: in the init.venturi.rc. I'll got some clean up to do, but I'll be pushing my device tree tomorrow and submitting some changes to yours so we can get CM11.
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
i'm having problems getting super user access, anyone else got this?
Lorddemonrage said:
i'm having problems getting super user access, anyone else got this?
Click to expand...
Click to collapse
My SU access is ok.
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
mr_ggcstop said:
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
Click to expand...
Click to collapse
TWRP is a "known issue", if you read the OP. (workin' on it)
Lorddemonrage said:
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Click to expand...
Click to collapse
I am aware of the "2 cards in mass storage issue", but for the su problem, haven't had any issues .... developer-options-> root (or something like that)
joemhewitt said:
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
Click to expand...
Click to collapse
yes including system:good:
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
aznflawless said:
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
Click to expand...
Click to collapse
No I am not. I can't maintain 2 Roms... I submitted patches to get CM11 working but someone else is going to have to build it...
@iurnait ???
Sent from my M470BSA using Tapatalk
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
bassbrick15 said:
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
Click to expand...
Click to collapse
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Been Waiting For This For Awhile Noe. Thanks Guys, I Guess With Patience Good Things Come. Hopefully The Same Can Be Said About The Rear Camera.
Sent from my YP-G70 using xda app-developers app
Meticulus said:
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Click to expand...
Click to collapse
Hi Meticulus!
First, let me thank you for all your time and energy spent in making this mod for an old device! I love my Player 5, but it is show it's age. I'm hoping your SlimKat 4.4.1 will breathe new life into it. (A shame Samsung stopped developing this line).
I have a Galaxy Player 5 running a rootedGingerbread 2.3.5 with CWM v5.0.2.7 (no TWRP)
Do you recommend any special preparation before applying SlimKat 4.4.1?
Since I'm using CWM, will I be able to restore back to Gingerbread using a current backup (just in case)?
As you might have guessed, I am not a frequent "mod"-er so I've fallen behind a bit.
Thank you for taking your time to help me and so many others!
SailfishOS (SFOS) is a GNU+Linux system using libhybris to leverage Android drivers from LineageOS.
About everything should work (except NFC, no userspace support for now).
You're root and you've SSH, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build or newer,
and have booted it at least once (otherwise WLAN problems).
See latest release post for OTA update instructions, or flash ZIP download link.
Warning : flashing zip over previous SFOS install erases it ! So use OTA to avoid that, or use integrated backup app...
Note : SFOS only flashes boot partition and install itself in /data/.stowaways/sailfishos/ so :
you can go back to LineageOS only by flashing the LOS boot image
you can reclaim diskspace used SFOS by removing /data/.stowaways/sailfishos/
Reference Wiki page on merproject.org
Kernel | Device | Vendor source trees
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.).
This is not mandatory (though prefered for the full experience) : should you choose not to register (and even if you do),
you still can install an alternative store using OpenRepos client Storeman
Reserved
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
andrejchern said:
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
Click to expand...
Click to collapse
I have installated seilfish os some time ago in my moto g2 and the battery life and boot speed its superior then any version of android ... ?
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
tess1 said:
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
Click to expand...
Click to collapse
It's all politics, also it's the system I use daily
some sort of hommage to a french industry of old (1898), rough-rided by financialization (see, can't build idol3 themselves)
fighting planned obsolescence
taking the power back on a device
powering it with an OS independent from GAFAM
having closer to classical GNU+Linux distro, though not totally open in the case of SFOS
Since 2010 I've been a Nokia N900 then N9 user (which ran with Maemo, resp. Meego, predecessors to SailfishOS) until summer 2017 when I got a Xperia X for the SailfishX release. Only ever used Android for a month, until the build-SFOS-for-X documentation was released and dived in the OS-building fun...
At the beginning of 2018 I looked for a cheap and decent french-branded-androphone (2Gb RAM, HD display) with a working LineageOS port and found the idol3 to begin a new SFOS port. It's been a long 8 months journey, where rebuilding LineageOS if only for the patch-level was not much, then also wanted to "upstream" some fixes or upgrades (eg. kernel) I wanted in SFOS...
I started using my idol3 again and I love Sailfish OS as soon as I figure out android apps im gonna use it alot more
Everything work fine, but the double tap to wake up the telephone.
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Best regard.
Antonio from Italy.
vknecht said:
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it* and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
It's a systemd-based GNU/Linux with 32bits-userspace system, and about every basis function should work.
You're root, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build, and have booted it at least once (otherwise WLAN problems).
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.). This is not mandatory (though prefered for the full experience, for now) : should you choose not to register (and even if you do), you still can install an alternative store using OpenRepos client Storeman
*basic Anbox support was added, but don't count on it for now (plz contribute if you can), it may be broken.
If you really want to try it : (don't just copy/paste, fix the URLs !)
Code:
### As root (devel-su), on the phone via SSH :
# Add mal's Anbox for SFOS repository
ssu ar home_mal_anbox [url]http://repo.merproject.org/obs/home:/mal:/anbox/sailfish_latest_armv7hl/[/url]
pkcon refresh
pkcon install anbox-sailfishos anbox-sailfishos-image-mixed-32-64-bit
rm -f /var/lib/anbox/overlay/system/lib64/libGLESv*
cp /vendor/lib/egl/libEGL_adreno.so /var/lib/anbox/overlay/vendor/lib/egl/
# Install a keyboard APK, eg [url]https://f-droid.org/fr/packages/rkr.simplekeyboard.inputmethod/[/url]
mkdir -p /var/lib/anbox/data/app
cp *apk /var/lib/anbox/data/app
### Networking is broken at the moment... ###
### Comment anbox-bridge.sh lines (ExecStartPre and ExecStopPost) ###
### in /lib/systemd/system/anbox-container-manager.service ###
# Restart Anbox
systemctl restart anbox-container-manager
# There's no "back" button for now
# Run Anbox from app screen again to go back to Anbox app launcher
This is a simultaneous release of SFOS 2.2.1.18 and 3.0.0.8, if you have problem with one version, try the other
SFOS 2.2.1.18
SFOS 3.0.0.8
Sorry no screenshot or video for now, you can find for other devices, looks should be the same.
SailfishOS fir idol3 Wiki page
Kernel | Device | Vendor source trees
Click to expand...
Click to collapse
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
zorro_tj said:
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Click to expand...
Click to collapse
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
For donations, maybe it will be possible later.
h3cat3 said:
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
Click to expand...
Click to collapse
One thing I could do is try building LOS 14.1 with idol347 defconfig, but afaik it's not really working.
Otherwise one could follow the SailfishOS HADK using a working CyanogenMod base and I'd be glad to help, but don't have time to start it myself at the moment.
Thanks!
vknecht said:
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you. Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it? if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
zorro_tj said:
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you.
Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it?
if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
You're welcome For now I don't see any drain, let's hope it stays like this.
I found out that the ini file is not necessary if one sets tp_gesture_id to 2, but still have to set this value on boot
and/or find why it's not the same as in LineageOS by default.
3.0.1.11 release for idol3 is still in devel phase, once it's ready (~ one week or so) it will be published in testing phase and then you'll be able to do
OTA through commandline.
One can flash a devel-image, but then can't rely on OTA : will have to re-flash a testing-image or do risky/unsupported repository-switch.
Those are generally built using SailfishOS porters' Gitlab-CI group, latest being the 20190227 devel image
SailfishOS 3.0.1.11 beta3
Backup...
Update using OTA : the integrated graphical updater doesn't work for community ports
Easiest is to install sfos-upgrade either through Storeman or direct RPM dowload.
Flash image : (erases previously installed SailfishOS)
sailfishos-idol3-release-3.0.1.11-20190321-beta3.zip
Changes :
SailfishOS 3.0.1.11 release notes (points specific to officially supported devices don't apply)
Kernel : enabled Yama security module
Enabled doubletap to wake
Sorry, Anbox confirmed to NOT work, have to check required overlayfs support, maybe broken with the kernel updates.
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
andrejchern said:
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
Click to expand...
Click to collapse
Sorry to hear that... does it happen regularly/systematically and quite early after boot, or after (somehow) extensive usage, especially browser ?
I supposed you tried with flashing as well as OTA ?
A known cause for reboot is fixed in this build (and beta2 iirc) by an updated connman package ("rpm -qi connman" shows ip6tfix in version).
Maybe it's related to Yama security, will make a build without it...
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
andrejchern said:
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
Click to expand...
Click to collapse
Could you try flashing the ZIP inside the artifact from this devel build ?
It uses the same kernel as 3.0.0.8, ie. without yama, pstore and iirc RTC write support...
This build works fine, no reboots. Thanks.
SailfishOS 3.0.1.11 beta4
Update from any previous betas using OTA :
has to be done from commandline (on device or through SSH, USB prefered) since the graphical client in settings doesn't support community ports.
Code:
# Install sfos-upgrade package like this, or through Storeman
curl -O https://openrepos.net/sites/default/files/packages/5928/sfos-upgrade-2.4-1.noarch.rpm
devel-su
pkcon install-local sfos-upgrade-2.4-1.noarch.rpm
sfos-upgrade 3.0.1.11
reboot
# Patience, it takes an additional reboot to flash boot partition
# Go to commandline again and run :
devel-su post_sfos-upgrade
or install by flashing sailfishos-idol3-release-3.0.1.11-20190329-beta4.zip
(this replaces previously installed SailfishOS and SailfishOS-data, backup if needed)
Changes
Fall back to previous kernel
Hey mate, great job! Everything worked fine with sfos-upgrade from command line! Thanks a lot!!!
Just a question... I haven't prediction text, it's normal? Thanks again.
Antonio from Italy.
Hi, there!
Now that we can use Project Croissant to get ChromeOS running or non-Chromebook devices, what is missing is a better kernel for improved compatibility.
Thanks to the threads by @nabil2000 I was able to successfully build a chromeos-4.14 kernel that boots on my test device (Lenovo MIIX320-10ICR - Z8350 processor) using a CONFIG from FydeOS 5.31 with most hardware enabled (WiFi, Bluetooth, sound), but it has the same issue as latest ATB builds: it freezes after a while. This doesn't happen with latest FydeOS or CloudReady builds (CloudReady bought FlintOS so I guess they are using some of their code now), so my guess if that their kernels have some patches that aren't included in the Chromium git. FydeOS is open-sourced only for RaspberryPi and TinkerBoard, there are no sources available for the PC or VMWare versions (PC version is not open source as many say, so be aware).
I already have some ideas to make the trackpad as well as the battery meter and brightness work, but it is not useful if the kernel isn't as stable as FydeOS (virtually no freezes or crashes once booted). I have already checked, and the issue is not the intel_idle.max_cstate issue that plagued most BayTrail/CherryTrail devices in the past (using value 1 doesn't change anything).
So any ideas how to get FydeOS kernel source? Patches to make the current chromeos-4.14 kernel stable?
UPDATE: As @nabil2000 reported, it seems that FydeOS is not willing to release their kernel source. But it is possible to get kernel config from v5.31 using configs.ko module, which is missing in the next version (v6.0). Using FydeOS v5.31 as base it is possible to build a very stable kernel for CherryTrail devices.
Thanks
Installation v71/v72 - kernel 4.14
FydeOS has the best support for the MIIX320-10ICR, with some caveats:
It will boot to a black screen, but you just need to wait until it finishes loading the hit Ctrl+Alt+Fn+F2, the screen will blink and then hit Ctrl+Alt+Fn+F1 to go back to ChromeOS (for some reason, the developer shell is blank in 5.31 but it seems to work fine on 6.0). Use Ctrl+Shift+Fn+F3 to rotate the screen manually;
WiFi works out of the box, Bluetooth is detected but audio does not work (Chromium misses a library for audio over Bluetooth);
Sound works too, but you need to install some UCM files (more about this later);
Camera does not work, and the trackpad works very well, with gestures, but does NOT click (tap to click work with a custom conf file, see below - the trackpad actually sends two events when clicking the physical button, as some Windows devices do, and this doesn't work with cmt driver).
First I tried to build the ChromeOS file using the chromium.img from FydeOS v5.31. It booted fine and I was amazed to see the ChromeOS logo and Google enrollment, but PlayStore setup didn't finish (low space?) and there was no way to install it to another driver: many GPT errors and the installer failed...
Then I tried to do everything on place:
Booted to FydeOS on USB drive;
As I could not get to the dev shell in v5.31, I had to login then use crosh and shell, then installed it on a second external disk (120GB SATA on USB, /dev/sdb):
PS: your device may be a different one, check the correct device name using "lsblk" or "fdisk -l" and be aware that this installation erases the whole disk!
Code:
sudo chromeos-install --dst /dev/sdb
After installing, I have used option 2A from GitHub page (very detailed, thanks!) with the script, soraka (or pyro) and caroline recoveries (both versions 11151.113 = v71) on another disk:
PS: FydOS v5.31 kernel does not have support to VTPM_PROXY, while v6.0 does, it means you cannot use swtpm.jar with FydeOS v5.31 and chromefy. For nocturne or Android Pie ARC, you must use FydeOS v6.0, otherwise ARC won't work.
Code:
sudo bash ./chromefy.sh /dev/sdb recovery.bin caroline.bin
Answered YES to use the local installation, YES to resize partitions and NO in the end to keep SELinux as enforced (it may work fine if you keep it to enforced with nocturne recovery tho when using FydeOS v6.0);
Rebooted using the final installation, logged in and everything seemed fine, but then Play Store would not show installed apps even after a reboot, so I tried a powerwash and it seems it fixed the issue, now it seems to be working fine.
Original post: https://forum.xda-developers.com/showpost.php?p=78891386&postcount=729
Post installation fixes v71/v72 - kernel 4.14
1. Sound
You need to install UCM files using linuxium-install-UCM-files.sh script after remounting rootfs as RW.
Code:
sudo remount -o rw,remount /
sudo bash ./linuxium-install-UCM-files.sh
2. Headphone jack
You must send this quirk to the rt5645 module when loading it, so while rootfs is still RW, as root add a file named "miix320.conf" to /etc/modprobe.d with this line:
Code:
options snd_soc_rt5645 quirk=0x1030
PS: if you have used the correct UCM files then the audio should change between speakers and headphones, but not mic. To enable internal mic:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev DMic
and to enable mic from headset:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev HSMic
3. Tap to click with trackpad
While rootfs is still RW, as root add a file named "50-mixx320.conf" to /etc/gestures:
Code:
Section "InputClass"
Identifier "MIIX320 conf"
MatchUSBID "048d:*"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "Tap Minimum Pressure" "1"
EndSection
PS: for this to work, make sure "tap-to-click" is enabled in trackpad section of system Settings. If you have another device, use "dmesg | grep input:" with "lsusb" to find your device USB id instead of "048d:*".
Still needing fixes:
- chrome://flags is blank for some reason, so any special flags should be added manually to "chrome_dev.conf" instead;
- Trackpad physical button click;
- Brightness control;
- Battery meter;
- Rotation;
- Automatic change between tablet/desktop modes;
- Cameras (hardly they will work as they rely on ATOMISP, which was abandoned and does not work even on newest kernels).
Original post: https://forum.xda-developers.com/showpost.php?p=78978577&postcount=757
reserved
Good news! With chromeos-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
lfom said:
Good news! With chrome-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
Click to expand...
Click to collapse
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
nabil2000 said:
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
Click to expand...
Click to collapse
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-dev in order to successfully build it.
lfom said:
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-devel in order to successfully build it.
Click to expand...
Click to collapse
I am a lazy billy - thanks - I like copy & paste, & think as little as I can afford
Could you help me patching it on my GPD pocket?
it uses cherry tail
https://forum.xda-developers.com/ha...gpd-pocket-t3928828/post79496417#post79496417
thank you