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...
Bangsters V1.5 (CM6) Froyo Theme
AXI + NOAXI + EVO | RMNET + PPP | BRUT MAPS
Highlights:
- WIFI Tethering/Hotspot! Works flawless with RMNET, for PPP need to run a script
- USB Mass Storage
- Cyanogen CM6 latest nightly
- Change Internet, DPI and Data Image size from startup.txt
- led light and keypad lights
- GPS fixed
- Bluetooth fixed (supposedly, please test and confirm)
- Michyprima RC11 Normal with AXI and NON AXI, or EVO zImage (easily switch between the three via startup.txt, or even use your own)
- added BRUT MAPS
- updated to latest launcherpro and ADW Launcher
- GPS Zone easily configurable via startup.txt as well
I'm releasing this build which I use daily. It's now V1.5 as it is a stable build suited for daily use. This is a standard froyo theme (2.2) with adjustable dpi settings and adjustable data image size from startup.txt. It is also using the latest R11 zImages from MichyPrima and Evo zImages. Simply switch via editing startup.txt
Note: Previous users of RC1.0/1.1 please wipe everything and reinstall as I changed a lot.... I went the route of everyone else with a system.ext2 file system instead of htcleo_update.tar.gz... this makes it easier to reinstall build as you only have to delete data.img.
To upgrade from previous version while keeping your data intact:
Previous users of V1/V1.1,1.2,1.3, you can just copy over the system.ext2, rootfs.img, and root folder as well as the other folders, and leave your data.img so that you get to keep your settings.
Some features:
CM6 Nightly 9/19/2010 build
180 dpi or 240dpi, easily change from startup.txt - more icons in screen when combined with ADW Launcher
Includes ADW Launcher and LauncherPro
Following Working: Camera w/ Flash, Camcorder, GPS (USA default), 3G, Wifi, WIFI Tethering/Hotspot, Flashlight with 180dpi, LED, Keypad Lights, USB Mass Storage
Froyo Default Theme, FRG33
UserData adjustable. Just make the changes in startup.txt before first boot! Will take some time on first boot due to size of data image being created.
choose from different zImages. Just make the changes in startup.txt to choose between MichyPrima's R11 AXI, NOAXI, and EVO.
Need to Test:
Not sure - Bluetooth (someone has to test since I have no BT headset to test with)
Again, I'm releasing this since I use it. Use if you want to at your own risk (don't worry it won't brick your phone)
I'm using this build with ChuckyDroid Rom (with FD DriodBoot cooked in) and radio 2.12.50 without any issues.
NOTE:
Thanks to all those who have donated. If you want me to put your name here, please PM me and with the paypal code.
louie317, ktran1588, partie, bler, Uglymittens, and others whom I don't know their userids yet so i can't post here
-----------
If you're feeling generous feel free to donate
Latest Version Download: 1.5 Uploaded 10.09.2010
DOWNLOAD HERE VIA MULTIUPLOAD (1.5)
NETWORK SWITCHER SCRIPT (switch between RMNET and PPP script for GScript)
Download this and extract to gscript folder in the root of the sdcard (outside of Android folder!). Then go to GScript and load the script. This file is already in V1.4 download.
Warning! Read everything before you make any modifications to the files.
#be careful when editing the settings.
set cmdline "rel_path=Android data_size=2048 lcd_res=180 conn_type=ppp kernel_type=axi gps_zone=us"
boot
AVAILABLE OPTIONS FOR STARTUP.TXT:
# conn_type: ppp,rmnet
# kernel_type: axi, noaxi, evo, custom
# gps_zone: us, europe, etc (pls check your zone based on pool.ntp.org
# lcd_res: any variable from 140 to 240, my default is 180, Froyo default is 240
# data_size: 2048 for 2GB, 1024 for 1GB, 512 for 512MB
# rel_path: Android. Be careful when changing this. this is the android folder in the sdcard
If you are having issues booting, try editing startup.txt and change set cmdline "rel_path=Android data_size=2048 lcd_res=180 conn_type=ppp kernel_type=axi gps_zone=us" to "set cmdline rel_path=Android data_size=2048 lcd_res=180 conn_type=ppp kernel_type=axi gps_zone=us loop_partition=mmcblk0""
Instructions on setting Data Image Size, setting DPI resolution, changing between PPP/RMNET, changing GPS ZONE, using AXI/NOAXI/EVO or your own zImage:
Before running Android for the first time (or if you want to change the data image, then just delete your existing data.img file), edit startup.txt and look for the line
set cmdline "rel_path=Android data_size=2048 lcd_res=180 conn_type=ppp kernel_type=axi gps_zone=us"
Change that line to adjust your desired data image size, screen resolution, and to switch between RMNET/PPP.
How to change Data Image:
change this: data_size=2048
2048 = 2GB, 1024 = 1GB, 512 = 512MB
Example. to have 1GB image size set it to 1024, for 2GB set it to 2048. 512MB put 512. Default is set to 512.
Change Screen Resolution:
To change the DPI easily via startup.txt, edit the variable that says dpi_res = 180 and change it according to your preference. Set it to 240 to have default resolution.
To switch between PPP/RMNET:
To switch between RMNET and PPP, change this variable, conn_type=ppp in startup.txt. Options are ppp and rmnet. You don't have to replace any file or anything, just this variable
Note: In PPP mode, WIFI router needs to run a script to fix the iptables (thanks Warrenb). In the Android folder, there is a file, ppp_wifi_router.sh. You need to run that everytime you activate WIFI Router. You can run it two ways:
1. Open the file in terminal.
2. Copy the contents of that file to G-Scripts so it's one click from Home screen
WARNING! If you are switching zImages, make sure that the zImage supports both RMNET and PPP if you want both. IF NOT, then MAKE SURE that the setting in startup.txt is the same! Example: Evo based kernels are PPP only, so makesure startup.txt says ppp.
To switch between AXI, NOAXI, and uploading your own zImge READ THIS!!
In startup.txt look at this line:
set cmdline "rel_path=Android data_size=2048 lcd_res=180 conn_type=ppp kernel_type=axi gps_zone=us"
the kernel_type=axi specifies to dynamically load the AXI kernel. If this does not work for you, change axi to noaxi. then reboot.
If you want to use your own zImage, change axi to custom, then upload your own zImage into the Android folder. Also upload the equivalent modules with it. If you do not set this to custom, whatever zImage you copy to the Android folder will be replaced.
Also I included Power Control Plus by accident. It is a paid app and will not run without license. Either buy the license in market or just uninstall it.
To Set GPS ZONE:
In startup.txt:
set cmdline "rel_path=Android data_size=2048 lcd_res=180 conn_type=ppp kernel_type=axi gps_zone=us"
Change the part that says gps_zone=us. If it's europe, change it to europe. It can be anything before the xxxxxx.pool.ntp.org. US is us.pool.ntp.org (hence I put "us"). For europe it europe.pool.ntp.org (hence I put "europe"), and so forth....
Refer to pool.ntp.org for this.
For those having Issues Sending MMS:
Adjust the APN settings (below is for TMO US) Leave the other fields the way they are and only change these fields!
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username: (leave this blank)
Password: (leave this blank)
Server: (leave this blank)
MMSC: http://mms.msg.english.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.50
MMS Port: 8080
MMS Protocol: WAP 2.0 (if you have this)
MCC: 310
MNC: 260
APN Type: default,supl,mms
If you have a different carrier, boot into WINMO and get the APN settings for MMS, then plug them into your Andoird Settings.
Please go through this Checklist:
1. Format SDCARD, NOT Quick Format but Full Format, use 32K block size (THIS IS VERY IMPORTANT)
2. Switch to Chuckydroid Rom
3. Switch to 2.10.50_26 radio (especially if using TMO USA)
4. Re-download the build
5. Do not change the settings of startup.txt and boot it (for testing purposes as that default setting is what I use I have no issues whatsoever)
6. download setcpu and set for Interactive Governor
7. Go to Spare Parts and speed up transitions, and disable compatibility mode
8. For those having Issues Sending MMS adjust APN settings and use settings above for TMO US. If you have a different carrier, boot into WINMO and get the APN settings for MMS, then plug them into your Andoird Settings.
If something still is wrong after this I'll be puzzled myself.....
I was just able to use GPS, Wifi Tethering, Phone Call, send a 5MB email all at the same time while going home from Philadelphia yesterday. Search this thread for the word Sonic to see that post.)
Changelog:
V1.5
- Further changes to rootfs
- updated to latest Nightly
- fixed minor bugs
V1.4
- Totally reworked rootfs.img script on how startup options are handled. Should be working better than 1.3 and 1.3a
- Added option to choose EVO zImage via startup.txt
- updated to latest Nightly
- fixed some bugs (wallpaper, etc)
- more changes
V1.3a patch
- reworked script how startup.txt is processed.
V1.3a
- Re-Added LauncherPro (latest version)
- Updated ADW Launcher to latest
- Installed BRUT Maps
- modification in startup.txt
- GPS Zone now configured via startup.txt
- Included both AXI and NON AXI kernel from MichyPrima. To switch, easily change from startup.txt.
- replaced led light driver for battery issues
- some minor stuff...
V1.3
- fixed Bluetooth. Now it does data transfer between a MAc/PC and the HD2. For BT calls, someone has to check and confirm, since I don't have any BT headset (If you want, donate so I can buy one)
- Modified startup. Now takes in variables for screen resolution, data image size, and RMNET/PPP
- Easily switch between RMNET/PPP without replacing any files... just edit startup.txt then reboot.
- Uses MichyPrima's R11 Normal Kernel with both AXI/NOAXI
- some minor fixes for stability and speed
NOTE: I tried installing brut maps but didn't get to test it. I'll fix this soon for 1.3A
V1.2a
- fixed browser related issue (broswer FC, Facebook, Zedge)
- fixed wifi router bug
V1.2
- CM6 Nightly FRG33 (9/5/2010 buiid)
- Improved performance, speed, and stability
- Adjusted some widget to 35% transparency (News and Weather)
- Bluetooth update (please confirm since I don't have any BT devices)
V1.1
- Fixed GPS
- Minor changes on default apps
- Superuser updated to latest version
- removed Amazon MP3 app from default
- Bluetooth update (please confirm since I don't have any BT devices)
V1.00
Initial Non RC Release
RC 1.1
Camera fix
RC 1.0
Build preview for beta testing
Yupppiieee..!!!
Thanks..!!!
Link please for "Download"..!!!
Cant wait to beta test ......you might want to put a donate to paypal link in your sig
bangsters said:
Download here:
MEGAUPLOAD: http://www.megaupload.com/?d=WO6TH14M
Click to expand...
Click to collapse
Downloadin now..!!!
Will keep you updated..!!!
Thanks, really appreciate your hard work & also of all the other DEV's on XDA..!!!
XDA rocks & you are the 1's responsible..!!
thx bro. downloading now.
also i second adding the donation link. i cant figure out how to make my own roms, so hey why not send a beer your way.
/cheers
i need a 1gb data file. can you post a fix for that.
edit1: dont forget for bootup issues add:
set cmdline "rel_path=Android loop_partition=mmcblk0"
edit2: data on att connects but does not function at all (this is in edge mode) during the intial setup wizard. otherwise so far only the edge icon doesn't not animate.
songokussm said:
thx bro. downloading now.
also i second adding the donation link. i cant figure out how to make my own roms, so hey why not send a beer your way.
/cheers
i need a 1gb data file. can you post a fix for that.
Click to expand...
Click to collapse
i'll post the 1GB file and other upgrades, and mirrors later.... jsut tried to do this as soon as possible so you guys can get it.
i'll polish the build later.... reuploading....
i think guys we became leo android addictors its 6 am here in lebanon and im refreshing android development thread regularly to catch any new work downloading now for testing thanks Bangsters for the hard work you rock
Thanx a lot bangster will report back after test.
thx working good
just change with that in statup.txt
set cmdline "rel_path=Android loop_partition=mmcblk0"
Can you post what's working and what's not please and I will donation also
I am wondering about this rom. No idea what it is, and do leds work?
wawa144st said:
Can you post what's working and what's not please and I will donation also
Click to expand...
Click to collapse
the whats working stuff is in the readme when u download the file.
itsedstech said:
the whats working stuff is in the readme when u download the file.
Click to expand...
Click to collapse
Thanks but I'm not home yet just was wondering what's working and what's not that's usually what they post when they post a build that's why
wawa144st said:
Thanks but I'm not home yet just was wondering what's working and what's not that's usually what they post when they post a build that's why
Click to expand...
Click to collapse
oh sorry well heres what the readme says
Whats working:
- Wifi
- GPS
- 3G
- Camera with flash
- Bluetooth
- Everything thats working on other builds
itsedstech said:
the whats working stuff is in the readme when u download the file.
Click to expand...
Click to collapse
itsedstech said:
oh sorry well heres what the readme says
Whats working:
- Wifi
- GPS
- 3G
- Camera with flash
- Bluetooth
- Everything thats working on other builds
Click to expand...
Click to collapse
Thanks alot and what's not please
itsedstech said:
- Everything thats working on other builds
Click to expand...
Click to collapse
they all say that but then i try a new one and leds arent working.
Booting now! Looks sweet with the higher res
Randy Couture just wooped the floor with Tony lol.... 1st round TKO.....
now waiting for main fight with BJ Penn... then off to more changes on the build
Please be patient. this is the best I can come up with in 2+ hours.
Flashed Looks AAAAaaaAAwwwwEEeSSSoooMMeeee..!!!l
Thanks a lot once again..!!!
Even a good QUAD score, I got 1389..!!!
Screen shots anyone?
Maybe I'm missing something, but how is the dpi higher than other roms? Isn't that a hardware restriction based on the screen?
For use with Streak Gingerbread Roms
Edit 12-7-11
This is the marked end of Gkernels project,
Gkernels 1.5 FINAL
but the marked beginning of Gxkernels!
Changes to 1.5 include:
Bumped the Dell source to 2.6.35.14 -Stable
Removed QoS in networking for reasons clear to my mind
Flashable zip here: http://db.tt/JuCSscC8
Developer tar.gz here: http://db.tt/pNkHIPRQ
Special thanks to you, the user of Gkernels!
-G
Edit 12-4-11
Gkernels1.4.3.1 now a flashable zip from your recovery, for easy installs!
lex parsimoniae
Special thanks going to _n0p_ for this method!
Download link here:http://db.tt/XrDJQ6Jv
to install:
copy the zip to sdcard, launch recovery in your streak, flash the zip file
for future releases, I will include the standard Gkernels tar.gz for rom developers, and also the flashable zip file, as two separate links for the community.
-Greg
Edit 12-3-11
GKERNELS1.4.3.1
Built with an older toolchain arm-eabi-4.3.1
Changes from 1.4.0.1 include:
<*> General filesystem local caching manager
<*> Filesystem caching on files
Wifi-
<*> Common routines for IEEE802.11 drivers
--- Bluetooth subsystem support
[*] L2CAP Extended Features support (EXPERIMENTAL)
networking options-
[*] IP: multicasting
[*] IP: ARP daemon support
Qos service changed-
<*> Hierarchical Fair Service Curve (HFSC)
---removed from 1.4.0.1 version---
adjust priority to speedup resume thread, (seems to help with wifi issue, special thanks DSC-Team)
Again, no overclocking;
Download Link here: http://db.tt/0vlfvlaI
Edit 11-27-11
1.4.0.1
changes since 1.3.3:
Suspend sleep mode (Power collapse suspend)
Control the low power modes of memory
Default Memory Low Power Mode during Idle (Memory in retention)
Default Memory Low Power Mode during Suspend (Memory in deep power down)
Enable standalone power collapse
Android RAM Console Enable error correction
Virtual Contiguous Memory (VCM) Layer
Download link: http://db.tt/ZnaqJ9qH
I am fairly certain wifi freeze issue is resolved. Further testing is needed to prove this;
Enjoy!
-Greg
Gkernels 1.3.3 still attached below
Gkernels 1.3.3
changes from Gkernels1.0
Enable WiFi control function abstraction
Preallocate memory for WiFi buffers
Enable KSM for page merging
Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)
I've got some under-volting going on with static voltage regulator
kernel switched to low resolution timer
Cross-Compiled using arm-eabi-4.4.3 from Dell 4.05 source, thanks given to Dj Steve for his tip with wifi practices. Thanks going out to kernel cross-compiling sources and books; thanks to all the rom chefs;
To me, Streak kernel work is more of an art than a science. Include Gkernels in your rom; do what you feel with it, all is permitted.
Installation Instructions
Method 1:Assumption is on a linux distro,
obtain a prebuilt fastboot and adb binary, and get them into your /bin folder, to use the commands from anywhere within your system
download Gkernels1.3 and extract, if you have not already done so.
attach streak to computer with usb cable;
from the extracted archive directory run this command in terminal:
sudo adb reboot bootloader
the streak will then boot into the fastboot mode
Then:
fastboot -i 0x413c flash boot boot.img
Then:
fastboot -i 0x413c reboot
then from same directory, run this command as phone is rebooting:
sudo adb push dhd.ko /system/lib/modules
I then recommend rebooting one more time.
Method 2: Any system
Re-substitute the boot.img and dhd.ko in the archive, by replacing same files, in your chosen rom's update zip;
transfer to the device
then flash as you would, the rom using your prior flashed recovery.
Thanks to Delirium77!
Method 3: Bypass for adb with root explorer/total commander app from the market
flash the boot.img with fastboot per method 1-
copy the dhd.ko file to your sd card, unplug your device, and using root explorer/total commander, navigate to the file on the sdcard, then move it to:
/system/lib/modules
ensure the dhd.ko file has correct permissions, then your wifi will function after a reboot.
-Greg
Thanks for your work!
can you build for your kernel few modules?
cifs.ko, slow-work.ko
for slow-work there is some kind of manual editing and preparing.
or if you give me your .config i will try this myself?
EDIT:
also you can statically compile CIFS filesystem into kernel
mind if i ask what advantage/s does this kernel have over Steve's gingerstreak kernel?
I can provide a .config file, sometime this evening, as I am away-
Gkernels is a project based on the 4.05 Dell source;
It is not better than another kernel in that regard, I am trying to get all I can out of it, without overclock. Changes to my knowledge, that differ from the Steve kernel, are listed above;
Thanks to _n0p_ 's tip 1.3.3 solves the RTC issue- Thanks _n0p_
I believe this was done by changing to the low resolution timer.
-Greg
.config
Sorry for the delay, I was detained-
attached is the .config for 1.3.3
Working with an attempt to solve the wifi issues-
one environment seemed to work during my testing, yet at a great sacrifice to battery life, by enabling:
control the low power modes of memory -->
Default Memory Low Power Mode during Idle (Memory active)
Default Memory Low Power Mode during Suspend (Memory active)
I am still uncertain-
before I release a 1.4, I will trial more of these modes
-Greg
Can this modes be switched by detecting if external power supplied?
--
I've also recieved some requests, saying that power (and maybe other) buttons sometimes "flickers". Is there any way to filter key events a little?
--
Thank you for your devotion,
Sergei
I will look into this.
Hi, there seems to be some screen tearing , I suspect that it has something to do with vsync. Could this be fixed with a new kernel update or is this ROM related?
Sharptv-
This may be kernel, rom or both related;
you may try and experiment with different roms and kernels-
This could also be screen density related, on my device there is minimal tearing on default density
I had some screen tearing on power rom but none on DSC....
Good work on the kernal
May bishnu grant you many donkeys and wives
@Roy
are u indian
Hi GSpecial!
I'd like to ask you to join forces with ltrifonov.
You both are advanced system builders, i think Streakers community would really benefit from your teamwork!
That's an awesome job you are doing. Never was able to crack more than 1500 upload until now!
Sent from the SuperStreak!
borijess said:
That's an awesome job you are doing. Never was able to crack more than 1500 upload until now!
Sent from the SuperStreak!
Click to expand...
Click to collapse
Is this considered a good score?? I just did the test and got 10ping, 15162kbps down and 8912kbps up
Sent from my Dell Streak using xda premium
Greg, your new kernel 1.4.0.1 (can say after a day of tests), is absolutely fantastic.
Fast, responsive even with conservative governor waking from 128Mhz - and WiFi is simply excellent!
Thank you!
Nop can you make a flashable zip plz???
You might pay attention to Downloads section for DSC ROM (not ad )
greekunit690 said:
Is this considered a good score?? I just did the test and got 10ping, 15162kbps down and 8912kbps up
Sent from my Dell Streak using xda premium
Click to expand...
Click to collapse
I guess compared to u rs no but normally I was getting around 1000 up. So its 3 times as fast now for me.
Sent from the SuperStreak!
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