Related
I have a Byond Mibook Mi3 tablet with
- Telechips TCC8923 1.2Ghz CPU
- Mali400 GPU
- running Android 4.0.3 ICS
- Primary Camera 2MP & Front Camera 0.3MP
- no GPS/Bluetooth
I Googled for custom roms and couldn't find one for my device
But I managed to find some devices seemingly similar either visually or on specs (though some have extra GPS/bluetooth)
- FreeLander PD20
- OEM A7 7"
- Hyundai A7 ART
- E420 (unbranded)
I also managed to get this page "telechips.com/technical_support/kor/opensource/opensource_list.asp" from Telechips support which says Open Source Software and lists Linux Kernel, Android sources in .tar.gz format.
I would also like to know whether I can flash any AOKP or AOSP ROM on my device?
If so pls let me know which Jelly bean ROM is best suited for my device or o ROM with best compatibility (I prefer a vanilla experience)
please I have the hyundai A7ART and'm also looking for a rom JB
shivji said:
I have a Byond Mibook Mi3 tablet with
- Telechips TCC8923 1.2Ghz CPU
- Mali400 GPU
- running Android 4.0.3 ICS
- Primary Camera 2MP & Front Camera 0.3MP
- no GPS/Bluetooth
I Googled for custom roms and couldn't find one for my device
But I managed to find some devices seemingly similar either visually or on specs (though some have extra GPS/bluetooth)
- FreeLander PD20
- OEM A7 7"
- Hyundai A7 ART
- E420 (unbranded)
I also managed to get this page "telechips.com/technical_support/kor/opensource/opensource_list.asp" from Telechips support which says Open Source Software and lists Linux Kernel, Android sources in .tar.gz format.
I would also like to know whether I can flash any AOKP or AOSP ROM on my device?
If so pls let me know which Jelly bean ROM is best suited for my device or o ROM with best compatibility (I prefer a vanilla experience)
Click to expand...
Click to collapse
Shivji- were you able to flash custom rom ? i too want to know about them. wish to flash my tablet mi3
OmniROM for P900 Only
installation:
install custom recovery TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
install omnirom with recovery
install gapps (optional): http://forum.xda-developers.com/showthread.php?t=2397942
for root flash zip file with recovery: http://download.chainfire.eu/589/SuperSU/
Changelog:
R2:
-improve overal stability
-bug fixes
known issues:
camera is not working
buttons backlight is not working
download links:
R2:
P900 https://yadi.sk/d/SUn2aByFcaEAM
XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy Note Pro 12.2
Contributors
bonuzzz, Valera1978, arcadia2uk
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-11-04
Last Updated 2014-11-20
Reserved
To anyone who flashed this, can you do the following immediately after installation?
1) Let the rom be installed and after setting up everything that it may be required from you (your google account?), wait for a while and then reboot the tablet.
2) Once the reboot is completed go to Settings-> Apps and from there navigate to the "Running" TAB. Once there please report the "USED" amount (it would be like "700MB used", or sth like this).
Thanks.
Latest update: 11082014 2.30pm EST
Thank you bonuzzz and Valera1978. This OmniROM directly built from source is out of the box the smoothest and reactive ROM I've seen on the T-900. I have been fortunate to run this version in alpha and beta over the past 4 or 5 days and I have not seen any extraordinary issues with the release.
Note for v.2 - Be very patient in flashing v2, from that system format starts in TWRP until extraction kicks in there's currently a delay of up to 3 minutes
Just as under the SM-P900 cm11 tread, I have performed some functionality testing of the device and some extra features, they are shown below as working, not working or not tested. The functionality grid was developed based on weaknesses in earlier AOSP builds and ports for the large format Samsung Tab/Note Pro family:
- mtp - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/ activated. Check mark USB debugging notify.
- adb
- External SD - working out of the box
- Ext4 SD card mounting on external SD - Auto-mount does not work, tested on Sandisk 128Gb SD
- USB OTG including USB storage
- Off-mode charging
- Encryption tested on backup restore in TWRP 2.8.1.1 restore failed in data, but must be related to a TWRP error Encryption process in ROM takes about an hour to perform, if someone is interested in performing the test and report back it would be great, but theoretically it should work.
-----------------------------------------
- Lid sensor
- IR blaster - worked by using IR 2.0
- OC settings - located in Settings/Performance/ if you click the 3 dots in upper right corner you can chose a toggle, or a drawer mode where a multitude of performance settings and information is available, most of them are currently not used.
- Advanced reboot - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/. Check mark Advanced reboot.
- Screen rotation specific issue with T-900
-----------------------------------------
- Play Store
- Google Play movies download and playback
- Google Play streaming Movies & TV
- DRM - tested with Audible, Google Books and Amazon Kindle
-----------------------------------------
- Zona
- Popcorn Time - need upgrade to latest version 2.3 beta, includes built-in VPN and Chromecast support with subtitles, earlier version timed out
- YouTube 1080p playback - 1440p will work w. v5.9.0.12, but I believe this to be a false positive.
- Netflix
-----------------------------------------
- Chromecast with #MirrorEnabler hack, allowing for screen cast
- MHL connector
- Miracast
-----------------------------------------
- Capacitive lights - I assume this is the backlights for the capacitive buttons
- Capacitive keys
- Home button - correct function performed
- Brightness manual + auto
- Vibrator
- S-Pen according to OP only available on P-900
-----------------------------------------
- GPS lock and voice directed navigation
- WiFi both 2.4 GHz & 5 GHz are working
- Bluetooth
- Microphone
- Audio on both speakers
- Headphones
-----------------------------------------
- Camera - in progress; the camera "works", but does not allow for single shots to be taken, and crashes in video mode, but panorama shots are working
- Torch as of v2
- Camera Sensors as of v2
-----------------------------------------
- Xposed Framework and modules - need re-initialization after each boot (common to all AOSP ROM's)
- Superuser - installation of latest flashable version SuperSU through TWRP is recommended - make sure to enter into SuperSU settings and execute "Install SuperSU backup script" under the CUSTOM ROM label before re-flashing a ROM update.
- Hangouts Dialer phone calls via Hangouts
-----------------------------------------
The following are standard limitations and options for OmniROM:
Write access to your external SD-card works out of the box, but just in case i suggest to d/l JRummy's SD KitKat Fixer
init.d support also works out of the box, otherwise d/l Uni-init by Ryuinferno.
If you think to much heat is building up use Performance/Governor set to ondemand, or conservative and I/O Schedduler to bfq, in addition to increase battery time you can set Wi-Fi/Advanced/Keep Wi-Fi on during sleep/ to Only when plugged in and make sure the Wi-Fi/Advanced/Wi-Fi optimization/ is checked and reduce Display/Sleep/ to below 1 minute. You can also use some apps to improve battery eg Easy Battery Saver, or the more sophisticated AutoCon+ Save Battery & Data and and to put hanging apps to hibernation Greenify that I believe require Xposed Installer. To improve charging time, you can use an app eg Faster Charger. Finally, I have also used PurePerformances in order to further improve the performances and VIPER4AndroidFX to allow for louder speaker sound and enhanced listening experience.
Stevethegreat said:
To anyone who flashed this, can you do the following immediately after installation?
1) Let the rom be installed and after setting up everything that it may be required from you (your google account?), wait for a while and then reboot the tablet.
2) Once the reboot is completed go to Settings-> Apps and from there navigate to the "Running" TAB. Once there please report the "USED" amount (it would be like "700MB used", or sth like this).
Thanks.
Click to expand...
Click to collapse
1.1Gb RAM used, but I'm running MultiROM, besides that I had only installed SuperSU and Pico gapps, I have exactly the same usage displayed with cm11.
IR port is working. Tested with smart ir
flip cover is working also
I dont understand issue with screen rotation
bonuzzz said:
IR port is working. Tested with smart ir
flip cover is working also
I dont understand issue with screen rotation
Click to expand...
Click to collapse
The screen doesn't automatically rotate when turning the device, although I have automatic rotation enabled in System/Display/ with values 0/90/180/270. However, with some apps a forced rotation arrive that turn the screen from landscape to portrait, after this the screen stay in portrait until another app trigger a turn to landscape. Anyway, blocking the screen in landscape, or in portrait with the apps I mentioned in my post works perfectly well, but it's a forced rotation, not automatic. It could be device specific? - note issue only concern T-900, not P900/901
I retested IR and Lid and they worked when flashing the ROM with TWRP 8.2.1.1. This was either a glitch, or the fact that I flashed in MultiROM.
arcadia2uk said:
For me the screen don't rotate automatically when turning the screen, although I have automatic enabled in System/Display/. However, with some apps I have automatic rotation that turn the screen from landscape to portrait, after this the screen stay in portrait until another app trigger a turn to landscape. However, blocking the screen in landscape, or in portrait with mentioned apps works perfectly well, but it's a forced rotation, not automatic. It could be device specific?
Click to expand...
Click to collapse
download please z-device test https://play.google.com/store/apps/details?id=zausan.zdevicetest and send me screenshot of his report
multirom in current state uses kernel from primary rom in additional roms. Concerning screen rotation, I think it is specific for t900 and I'll solve it in next release.
bonuzzz said:
download please z-device test https://play.google.com/store/apps/details?id=zausan.zdevicetest and send me screenshot of his report
multirom in current state uses kernel from primary rom in additional roms. Concerning screen rotation, I think it is specific for t900 and I'll solve it in next release.
Click to expand...
Click to collapse
That kernel use can explain some of the oddities I've experienced.
On the T-900 I had the screen rotation issues as well, along with other users, so I believe it's a T900 issue. It works with stock ROM though. Also, I just forwarded some screen shots.
Hey guys thanks for yet an other custom rom you sure have been working hard! I did some reading about this omnirom and i conclude imo it is prefereable to cyan, is valeria working only on omni now i noticed she released a new cm. Thanks again looking forward to next release.
Hi friends, I wanted to thank you for bringing OmniRom to the Note Pro 12.2.
I will be sure to install it this coming weekend when I have some time
I'm currently on CM and it's very nice, but I like the idea of Omni being truly open source.
Your efforts are greatly appreciated.
Ok I was excited when OmniROM was originally announced but honestly that was mostly because of the multi window stuff the is now available via Xposed. How is Omni better than CM? I have to say I have the CM build on my tablet and it's exceptional, can't believe it's this good when the Note 12.2 just recently become supported. Is Omni really noticeably faster/smoother?
rkirmeier said:
Ok I was excited when OmniROM was originally announced but honestly that was mostly because of the multi window stuff the is now available via Xposed. How is Omni better than CM? I have to say I have the CM build on my tablet and it's exceptional, can't believe it's this good when the Note 12.2 just recently become supported. Is Omni really noticeably faster/smoother?
Click to expand...
Click to collapse
My experience running the beta release that even at this stage it is already faster and smoother than cm-11. Try it and and you can tell directly by the screen transitions, and this is just the beginning. But the reason for OmniROM is more flexibility, it's a true AOSP ROM, meaning there's a lot more flexibility in deploying the code, than under cm that start loosing its freedom in development under a corporate flag. Besides, Omni is already better prepared for this, you can see this in it's deployment of the OmniSwitch as well as other features, eg. under the performance tab, where OC, undervoltage and other settings, and there is more...
However, the best way is to try it out and judge for your self.
On the other hand, if you really want to read up about it, check out this article
arcadia2uk said:
My experience running the beta release that even at this stage it is already faster and smoother than cm-11. Try it and and you can tell directly by the screen transitions, and this is just the beginning. But the reason for OmniROM is more flexibility, it's a true AOSP ROM, meaning there's a lot more flexibility in deploying the code, than under cm that start loosing its freedom in development under a corporate flag. Besides, Omni is already better prepared for this, you can see this in it's deployment of the OmniSwitch as well as other features, eg. under the performance tab, where OC, undervoltage and other settings, and there is more...
However, the best way is to try it out and judge for your self.
On the other hand, if you really want to read up about it, check out this article
Click to expand...
Click to collapse
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Thanks for the info and that is an interesting read. I'll probably give OmniROM a try...
notspike said:
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Click to expand...
Click to collapse
I don't believe it is implemented. But, the split view feature in the video exist as the xposed module: XMultiWindow. This was Omin's first release of the multi-window feature, and the development is still ongoing for a more feature packed floating window solution. See for example this concept idea.
notspike said:
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Click to expand...
Click to collapse
multiwindow had been removed from omnirom in spring 2014.
published first release for P901. I dont have this tab, so I cant testing. I hope mobile part is working here. Write your feedback please
bonuzzz said:
published first release for P901. I dont have this tab, so I cant testing. I hope mobile part is working here. Write your feedback please
Click to expand...
Click to collapse
can't download it !! when i press the download button nothing happens!! does camera work in this build ?? Thanks.
francesco totti said:
can't download it !! when i press the download button nothing happens!! does camera work in this build ?? Thanks.
Click to expand...
Click to collapse
https://yadi.sk/d/xTQ0HUhocaBpC
no. camera is not working yet
Guyz can any 1 port nexus 5 lollipop update for galaxy grand duos i9082.
When will the new lollipop update come for our grand duos....???
Sent from my GT-I9082 using XDA Premium 4 mobile app
::thumbup:
Sent from my GT-I9082
pawitp said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo.
Device-specific source code for the Samsung Galaxy Grand Duos are available from https://github.com/pawitp/android_device_samsung_i9082 and https://github.com/pawitp/android_kernel_samsung_i9082.
Compatibilitiy Patches: https://gist.github.com/pawitp/cba169c87dba57eea8ef
(Please give credit if you use them in your ROM and if you fix something, please submit patches.)
Do not submit bug on CyanogenMod issue tracker
Downloads
ROM: http://goo.im/devs/pawitp/i9082_cm12.0
Google Apps: For now, find your own package
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Dual SIM
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
screenrecord does not work
FM Radio does not work
Sometimes wake up causes music stutter
Video recording does not work
.wav playback does not work (.mp3 works fine)
SELinux is in permissive mode
Wi-Fi HAL (i.e. Scanning MAC Address Randomization) not implemented
Sim Tool Kit (STK) not fully working
Video in YouTube app sometimes freeze
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Additionally, Dual SIM has the following limitations:
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
3G may not work properly if Dual SIM mode is enabled with only 1 SIM inserted
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod recovery with SELinux support (.tar) (.zip by codekidX). Older CWM will result in a "status 7" error.
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again.
Changelog
20141116: Initial release
FAQ
How do I enable/disable Dual SIM?
Dual SIM support is enabled by default. If you only use 1 SIM and wants to disable Dual SIM support, you can use the following instruction:
Enable:
Code:
su
setprop persist.radio.multisim.config dsds
Disable:
Code:
su
setprop persist.radio.multisim.config none
(Instruction screenshots)
Are delta updates available?
Delta updates are not yet available for CM 12.0.
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Will you make this official CM?
Due to the amount of work and commitment involved, I am not planning to make an official CM port.
Can contacts be saved to phone/SIM?
No. It is not supported in AOSP-based ROMs.
Can I send files over Wi-Fi Direct?
Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Can I mirror your ROM?
You're free to, but I will not list it in this post.
Is overclock (OC) available?
1.3 GHz OC is available in Settings -> Performance -> Processor (enable developer mode first). Higher frequencies are not enabled since benchmark does not show additional benefit.
Will feature X from a previous version of CM be implemented?
I don't know, probably will be, eventually. I don't really involve myself in the feature-set side of CM.
Will you add OTA support?
No.
I cannot add APNs
Make sure you set the correct MCC/MNC code, the APN will not appear otherwise. Also make sure to use menu -> save (back button means discard).
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (I9082 or I9082L):
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- My real-life friend for letting me borrow his phone to work on this
- RampantRhino for donating a phone to help me continue with this project
Click to expand...
Click to collapse
See this
Press thanks if I helped
Sent from my GT-I9082 using XDA Premium 4 mobile app
Legendary PAWITP has given us a great cm12 ROM
I find it almost 100% similar to the official lollipop
Great ROM...
I cannot thank "pawitp" enough....
Grand users are lucky to have such great developers like pawitp, xenon, and others...
Archlinux Phone for Sony Xperia S
Part of GNU/Linux for Android devices project
First of all, this project is not ready for end users but everything is provided to build an archlinux system for the Sony Xperia S. So you will be able to have a complete system with GPU hardware acceleration, support of vibrator, sensors, GPS, wifi etc (everything is not yet tested like bluetooth, nfc...). Graphical applications are already able to display (Qt/Kwin tested but GTK3/kwin should be ok too).
This project is not just for this device and is really open to support multiple devices and GNU/Linux distributions. So you can share this project everywhere (xda, distributions forum...) ! Contribution are welcome and can be discussed directly on this thread to share efforts.
Introduction
This is a project to create a convergence between the desktop and the mobile/phablet/TV... so to build new mobile OS based on existing GNU/Linux distributions with the most common parts possible. We share some common base between mer-hybris (SailfishOS) and Ubuntu Touch but the architecture and integration are different (refer to Architecture).
Cell phone are powerful and expensive for flag ship so why just use it as a phone ?
Imagine that your cell phone can become your core device ! Plug it to a big screen and this is your workstation ! Plug it to an 'empty' laptop (no CPU, no RAM needed ...) and this is your laptop ! Move everywhere and this is just your mobile phone !
This is what motivate this project.
Applications
Applications are critical on a mobile platform and we hope to support Android application as soon as possible (need further studies to complete the architecture).
GNU/Linux applications are already compatible but not always adapted for a mobile phone for now but... We hope a lot of plasma mobile and KDE convergence guideline for Application developers
Source code
There is few projects and some fork available under my github but if you want to start to port a new distribution or a new device, everything is documented in the gnulinux_support project.
Android needs to be modified but we deliver a solution that permit to be integrated upstream and so to compile Android or Android for GNU/Linux with the same code.
For now we have only Android 5.1.1 patches available but 6.0 will come soon. CyanogenMod 12.1 and 13.0 can be a good target to support a lot of devices in the future (or at least to simplify the portage process per device).
manifest for Sony Xperia S
manifest for Pure AOSP 5.1.1 (can be used for Nexus devices)
Documentations
Architecture schema
Main documentation
Archlinux installation
Videos
https://vimeo.com/177893595
Distributions supported
archlinux (archlinuxarm)
Project status
This project is in an early stage and for developers but we created solid base of works and the portage of plasma mobile, ofono, ... and amazing features will start over those solid base to provide an end user product
Todo :
pulseaudio support for GNU/Linux - Android Hw (and maybe for Android to support sound from Android application)
fix libinput/kwin environment
ofono (or maybe an alternative/hybrid solution that can use the Android Telephony Framework ? no study yet on this point)
flashing after boot.img package update + generation of a custom initramfs
security with crypto, firewall and SELinux (SELinux or equivalent integration will mainly depend of the distribution support but for now this is disabled)
plasma mobile or other ?
localisation framework (see freedesktop project)
OMX
merge everything possible to every upstream projects used to create GNU/Linux for Android devices
overlayfs into kernel ? (not mandatory but can be a great solution for the Android rootfs and schroot)
... (a lot that I forget)
BUT despite this long list of todo... We already did :
New architecture (GNU/Linux and Android integration, systemd, libhybris, chroot, wayland ...)
SurfaceFlinger Composer supported by Qt and Kwin
schroot for Android (Android can run into a chroot and we can interact easily with it)
systemd integration (with reboot to bootloader and recovery, Android /init support, etc)
libhybris_ext (compatibility version with support of Android 5+)
Android integration with GNULINUX_SUPPORT (rc, init, busybox, ramdisk, OTA ... adaptation)
clean rootfs with only 2 symlinks that permit to see that we are on an Android device (nothing more)
OpenGL support (with backend hwcomposer or SurfaceFlinger)
Archlinux support (OTA and packaging)
Design a possible solution for a lot of other GNU/Linux distributions (share architecture and Android adaptation)
Documentation
Download
Binaries will be available when really usable for end user. For now everything can be compiled from source code
Devices supported
Sony Xperia S (nozomi): work in progress (this is our reference device)
RESERVED
I will provide OTA file, binaries (archlinux packages), images and video to show what is working and how really soon
Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk
Demetris said:
Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Multi screen is not yet supported on kwin_wayland so for now I have just focused to render on the main screen (0) but it will be possible to do it for hdmi (1). But for sure I hope to support hdmi output.
For now I will focus to port plasma-mobile/ofono/pulseaudio.
Impatient to try another gift from genius mickybart.
Waiting............
wow something new
waiting eagerly...
lovely, cannot wait to try it
finally there is hope to ditch android, ios and windows
I have not a lot of time to work on this project with the release of nAOSP b11 but once done I will rework on it and provides binaries for Devs.
But, I think that this "new OS" powered with plasma is a good choice and I'm happy to see that plasma 5.7 integrate such kind of features :
https://www.kde.org/announcements/plasma-5.7.0.php
https://blog.martin-graesslin.com/blog/2016/05/virtual-keyboard-support-in-kwinwayland-5-7/
Great improvement have been done on Wayland support too.
If some of you are interesting to do some packaging with Archlinux, I'm really interested to get some help to provide a usable system for end user. The work for now is more too package/install user tools (so integration of components). I miss pulseaudio and ofono patching but I'm optimist to solve every issues.
finally nAOSP 6.0 b11 and b12 took me more time than expected but I'm back on this project.
For information, I updated everything to Qt 5.7.x support.
Some pull request have been done and are in discussion for at least qt5-qpa-hwcomposer-plugin (mer-hybris).
I decided to don't provide binaries for now as there is not a lot of sense to do it except if you are interesting to help the project (mainly to package some stuffs, integrate tools for GPS, ofono, pulseaudio etc).
I just finalized to record a small video. I will cut it and upload it to prove that archlinux arm phone can be a reality with the proposed new architecture (and on our Xperia S).
I will work again on the kwin/libinput issue. Maybe just a logind/dbus/kwin discussion issue. Once fixed that should permit to have a graphical keyboard by default (I know that for iOS or Android this is normal... but not really on a GNU/Linux desktop) !
I continue to look for help on this project and if you can create some packages like the one for plasma-mobile and derived repo let me know in PM or in the thread.
small video of the project
https://vimeo.com/177893595
Great achievement today
libinput is working and so I'm now able to move windows, plug a keyboard to write a text file, plug the mouse (pointer is not visible) ...
Menus are well displayed now with the good size.
Next steps : pulseaudio, wifi, plasma-mobile... (and bug fix on the kwin backend).
wow mickybart !. u just struck my interest in coming back to this phone! amazing work. my phone was unusable and parts needed replacement. looking at the activity of yours in this section made me repair the device and try out your work.. cheers mate! keep going with ur awesome work!
OnePlus X (onyx) port
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !
latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
nik012003 said:
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !
Click to expand...
Click to collapse
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
mickybart said:
...
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future !
Let me know your advice and if you thing to base your work on CM 13.0...
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Click to expand...
Click to collapse
I've not tried arch but have attempted similar to this project with Debian (raspbian) on ancient hardware with partial success.
As free time rears its rare head I'll be trying to adapt your project for my newer HTC based on cm13.
By the way, your work on N ril from github is great, allows my cm14 to get/make calls without rebooting. Now if I can just figure out why rild takes forever to stop dying and respawing and start actually running...
mickybart said:
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
Click to expand...
Click to collapse
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
nik012003 said:
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
Click to expand...
Click to collapse
Thanks. I will give it a try but to have a more automatic process I will maybe follow what is done in mer-hybris :
https://github.com/mer-hybris/pulseaudio-modules-droid
(as common on XDA, see below. work is released under MIT license)
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
I am happy to announce a port of Sailfish OS to Sony Xperia XZ2. It is expected that this port would allow us to add support to XZ2 compact and XZ3 in a rather simple manner. As I have a single-sim device, that's the model its ported to first. To cover all six devices in Tama family, I may need some assistance from the owners. Please open an issue in the project's main repo to discuss specific model and what's needed to make it possible.
As this announcement is made at TMO and XDA, I will keep it short and avoid repetition.
Current features, state, download links: https://github.com/sailfishos-sony-tama/main/blob/master/README.md
The port was made possible thanks to the help from Sailfish porters (mal, piggz, deathmist, Mister_Magister,*vknecht, spiiroin) as well as Sony AOSP community (MartinX3, jerpelea, oshmoun,*Marijn,*kholk). And I suspect that I forgot someone, as very many contributed. Thank you very much!
I will be following on XDA and TMO. Please file issues centrally, at Github.
Sailfish OS, ROM for the Xperia XZ2
Contributors
rinigus Thaodan
ROM OS Version: 10.x
ROM Kernel: Linux 4.14.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 4.5.0.16
Stable Release Date: 2023-02-13
Created 2019-11-24
Last Updated 2023-02-13
Holy ****, thank you!
Edit:
First!
Edit0:
Will you open redirection threads to this project in the XZ3 and XZ2 compact sections in XDA like I did, since it is for every tama device?
Otherwise the XZ3 and XZ2C users may not see it.
Will do, its a good idea.
XZ3 are here. Not bootable at the moment however. Just black screen after unlocked bootloader message. No sign of sony logo. Not sure if it even should be displayed btw
ozamyatin said:
XZ3 are here. Not bootable at the moment however. Just black screen after unlocked bootloader message. No sign of sony logo. Not sure if it even should be displayed btw
Click to expand...
Click to collapse
Great to hear that someone tried, thanks!
I have not made any images for XZ3 yet. So, which image did you flash?
To make XZ3 image, I need to know how partitions are organized on XZ3. As I don't have XZ3, interested user has to provide such list. Please upload list either here or at https://github.com/sailfishos-sony-tama/main/issues/41 - its expected that its the same for dual and single sim variants.
Command to generate the list is given at with example result
https://github.com/sailfishos-sony-tama/main/issues/38#issuecomment-558017361
You could run it via adb (Android full OS or TWRP). As soon as I have that list, I will need to compile base AOSP for XZ3, kernel, few other packages and will be able to make images (XZ3 single/dual).
Meanwhile I set up CI and other build envs. Soon, images for XZ2 dual and XZ2c (single/dual) are coming for testing. But that's a separate post later a bit.
development builds for XZ2 and XZ2c variants
I am expanding a raster of devices with the images from Tama family. As mentioned above, XZ3 is
still missing mount points, hence its builds are not ready. However, as large fraction of the build if offloaded to the build servers, including generation of the images, it will be 'easy' to extend it to XZ3.
Currently, there are development builds for
- XZ2 single sim - release build is available as well and better use that
- XZ2 dual sim
- XZ2 compact single and dual
The images are available at https://thaodan.de/public/sailfishos/community/images/sony/tama/ (select appropriate device image, as based on its code https://developer.sony.com/develop/open-devices/get-started/supported-devices-and-functionality). Thanks to Thaodan for providing server space!
I have not tested those images as mine is from earlier days. In particular, I am looking for feedback regarding
- whether images work on any of the devices. They do share the same vbmeta (see flashing instructions) which maybe a wrong assumption of mine.
- whether dual sim support works on dual-sim devices
In short, if you flashed it, please do report back. Even if its just report all is OK.
Boot sequence is as follows:
- screen regarding unlocked bootloader
- SONY logo
- white brighter led while on SONY logo
- white dimmer led while on SONY logo
- blank screen
- Sailfish greeting
Please note these are development images. If all works as intended (boots and functionality is as for XZ2 single sim), we will make new release images. The difference is in over-the-air update support - this is available to release images only.
Hi you did great job with this port. I installed it without problems and everything is working fine. Sailfish is beautiful and smooth but without android apps support i can't use it as daily driver.
bartys said:
Hi you did great job with this port. I installed it without problems and everything is working fine. Sailfish is beautiful and smooth but without android apps support i can't use it as daily driver.
Click to expand...
Click to collapse
Thanks! Yes, Android support is missing. For myself, I found that live without Android apps is fine. For banking apps, and that's all what I have to use once in a while, I use another device. But your mileage may vary.
Would you mind telling which device did you test it on and which build did you use?
rinigus said:
Thanks! Yes, Android support is missing. For myself, I found that live without Android apps is fine. For banking apps, and that's all what I have to use once in a while, I use another device. But your mileage may vary.
Would you mind telling which device did you test it on and which build did you use?
Click to expand...
Click to collapse
I used build from github on xperia xz2 h8216
rinigus said:
Great to hear that someone tried, thanks!
I have not made any images for XZ3 yet. So, which image did you flash?
To make XZ3 image, I need to know how partitions are organized on XZ3. As I don't have XZ3, interested user has to provide such list. Please upload list either here or at https://github.com/sailfishos-sony-tama/main/issues/41 - its expected that its the same for dual and single sim variants.
Command to generate the list is given at with example result
https://github.com/sailfishos-sony-tama/main/issues/38#issuecomment-558017361
You could run it via adb (Android full OS or TWRP). As soon as I have that list, I will need to compile base AOSP for XZ3, kernel, few other packages and will be able to make images (XZ3 single/dual).
Meanwhile I set up CI and other build envs. Soon, images for XZ2 dual and XZ2c (single/dual) are coming for testing. But that's a separate post later a bit.
Click to expand...
Click to collapse
Thank you for your great effort in making things clear. :good:
I tried to flash XZ2 version. Naive maybe
Followed your request to upload the partition scheme for XZ3. You might check it out on GitHub. Just in case, my hardware is XZ3 4GB/64GB Dual Sim akatsuki 9436.
ozamyatin said:
Thank you for your great effort in making things clear. :good:
I tried to flash XZ2 version. Naive maybe
Followed your request to upload the partition scheme for XZ3. You might check it out on GitHub. Just in case, my hardware is XZ3 4GB/64GB Dual Sim akatsuki 9436.
Click to expand...
Click to collapse
Thanks! Looks like mount points are the same as for other devices in Tama family. Now I will have to build AOSP and Sailfish components for XZ3. After that, images will be generated using CI and uploaded to the same server as development builds above. Give me couple of days and it will be ready for testing.
New development builds are out covering all Tama variants. See https://forum.xda-developers.com/showpost.php?p=81060529&postcount=6 for instructions.
rinigus said:
New development builds are out covering all Tama variants. See https://forum.xda-developers.com/showpost.php?p=81060529&postcount=6 for instructions.
Click to expand...
Click to collapse
Ironically enough, after reflashing the right image files according to the instruction, the boot sequence for me is as follows:
- screen regarding unlocked bootloader
- SONY logo
- white brighter led while on SONY logo
- white dimmer led while on SONY logo
- no led while on SONY logo
- SONY LOGO for a lot of time
Stuck. What can be done for debugging such case on Sailfish?
ozamyatin said:
Ironically enough, after reflashing the right image files according to the instruction, the boot sequence for me is as follows:
- screen regarding unlocked bootloader
- SONY logo
- white brighter led while on SONY logo
- white dimmer led while on SONY logo
- no led while on SONY logo
- SONY LOGO for a lot of time
Stuck. What can be done for debugging such case on Sailfish?
Click to expand...
Click to collapse
Thanks a lot for reporting. There are ways to debug it, just will require some patience. Looks like Sailfish as such boots, just it cannot start GUI for one or another reason.
First, let's see if we get lucky. Hold power button for some time. Led should turn red and device will shut down. Try to start again. Do you have the same issue or GUI starts?
If we are not lucky, let me check if recovery image is fine. For speeding up debugging - do you have Linux PC or something else?
Its late over here, I am off for tonight. Will be able to continue tomorrow evening.
There is no Android app support
So can't I download any apps？:crying:
Guangd said:
There is no Android app support
So can't I download any apps？:crying:
Click to expand...
Click to collapse
No, there is no Android support. It also doesn't support iOS apps, Windows apps, Playstation games, and programs compiled for VAX.
Yes, you can download apps written for Sailfish OS.
On constructive note: all devices that are not XZ2 single sim will have to be tested first with few commands to get access to Jolla Store. If you happen to have such device, get in touch with me and I will ask you to make these tests. You could open an issue at Github for it (Jolla Store access for HYYYY) or ask here.
rinigus said:
No, there is no Android support. It also doesn't support iOS apps, Windows apps, Playstation games, and programs compiled for VAX.
Yes, you can download apps written for Sailfish OS.
On constructive note: all devices that are not XZ2 single sim will have to be tested first with few commands to get access to Jolla Store. If you happen to have such device, get in touch with me and I will ask you to make these tests. You could open an issue at Github for it (Jolla Store access for HYYYY) or ask here.
Click to expand...
Click to collapse
What is needed to add the android support?
A bought license from sailfish?
Because on their website there is a payable version with android support for specific phones.
"Sailfish licensing customers choose if they wish to use, or not to use, the Android application compatibility part in the OS."
MartinX3 said:
What is needed to add the android support?
A bought license from sailfish?
Because on their website there is a payable version with android support for specific phones.
"Sailfish licensing customers choose if they wish to use, or not to use, the Android application compatibility part in the OS."
Click to expand...
Click to collapse
In practice, there are two ways to get Android support:
- get an officially supported device (xperia x, xa2, 10) and buy license. That will allow you to use their Aliendalvik software which provides Android support. Not perfect support, but works for decent amount of apps.
- develop open-source Android compatibility stack, for example Anbox. I don't know much about Anbox development, though. From the outsider perspective, such as mine, it looks rather slow.
At this moment, none will work on Xperia Tama. As mentioned earlier in the thread, look what you really need and, if it is missing, develop it. Obviously, it will not work for closed-protocols apps. But then you have to choose, whether to stay on Android, get dumb phone for few Android apps that you need, or ditch the closed-protocol apps. In some respect, trying to emulate Android on other platforms seems to me unproductive, but that's my personal opinion.
@ozamyatin: we are starting to debug xz3 issue with ljo at TMO thread (http://talk.maemo.org/showthread.php?t=100877 ). I hope it will get resolved soon. Right now we have to get logs and then proceed from there
XZ3 dual/single and XZ2 dual released
XZ3 dual has been yesterday fixed together with ljo. Turned out that the touchscreen device had a different name and I forgot to adjust boot cmd line. I have uploaded XZ3 dual/single and XZ2 dual to the released images.
If you get any issues with Jolla Store access, please let me know
XZ2c is expected to be released in a week or so. Device has been ordered by one of Sailfish users and I think we will be able to finalize its release soon.