crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.
Related
Unofficial build of SlimKat
Dont post in official threads please. I may have messed something up and i dont want to bother other people because of my mistakes.
After leeching for years on XDA (didnt even had an account) i finaly decided to give something back to the community.
Features:
Im using the build scripts from Slimsaber
Features of Slimsaber but not all are working!
Used newest Linaro 4.8.3 (2014.04) optimized for cortex-a15 from here for kernel and rom.
Did some patches so it compiles with strict-aliasing :victory:. But i hate those freaking pointers. So maybe i messed something up.
all the nice placebo compile flags: -O3 -mcpu=cortex-a15 -mfpu=neon-vfpv4 -mfloat-abi=softfp -funroll-loops -fomit-frame-pointer
Other flags:BOARD_USES_HGL := true, BOARD_USES_OVERLAY := true, USE_OPENGL_RENDERER := true, TARGET_USES_ION := true, TARGET_USES_C2D_COMPOSITION := true
all the nice placebo build.prop tweaks: debug.sf.hw=1, debug.composition.type=c2d, debug.performance.tuning=1, persist.sys.composition.type=c2d, persist.sys.ui.hw=1, hw3d.force=1, hw2d.force=1, video.accelerate.hw=1, force_hw_ui=true, debug.egl.hw=1, debug.overlayui.enable=1 (actualy i dont know which ones are working and which ones arent even in the code )
f2fs for data and cache partition. (I think the first released z ultra rom with f2fs. Correct me if im wrong please)
DPI set to 280 (tablet layout).
Install instructions:
Be running at least Android 4.3 or 4.4.2 with an unlocked BL (14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681 or 14.3.B.0.757 etc)
Make a backup of everything on your phone. Im not responsible for any loss of data!
Boot into recovery
Factory reset/wipe data
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom
Install Gapps (I use this one)
Optional: for even more placebo install this soundmod.
Not Working:
Nothing known
Not Tested (would be nice if someone could test it):
ART
Miracast
Other models then C6833
Bugs:
WARNING: ADB/USB Debbuging is always enabled on reboot! So if you have sensitive data on your phone this ROM is NOT for you! (maybe someone can help. tried to disable it via build.prop and settings.db but didnt work . I think it has something todo with the build scripts from Slimsaber but hadnt had time to check it.)
[*]After installing the ROM for the first time you have to go to developer settings and disable root and reenable it in order for it to work!
Its already set to apps only after installing but it wont work! You only have to do this once. If you reflash you dont have to do it again.
Some graphics glitches because of "USE_OPENGL_RENDERER := TRUE" in some system apps (like Browser).
Actualy i read somewhere that its not needed but it wouldnt be placebo without it
If you use MHL some of the screen will not be displayed (It displays only like 1900*1000)
Downloads:
FormatPartitions-userdata_cache.zip. Credits goto legolas83
PlaceboRom-togari-4.4.2-20140515.zip
RestorePartitions_ext4_userdata_cache. If you want to go back to another rom. Credits goto legolas83
I will try to build every two weeks.
I had only one freeze on my device (C6833) in over 1,5 months (with older builds) but consider these build as NOT STABLE. I dont want that you lose your job because of me.
Special thanks to team slimroms.
Visit official website at http://www.slimroms.net
Slimsaber is the inspiration for this rom. High five @fusionjack.
If I have time i will setup a github account so contributions will be clear.
At the moment im using repos from Slimkat, Slimsaber, CyanogenMod, VanirAOSP, AOKP, Linaro
If i missed something or didnt gave proper credits i can assure that this is a mistake.
Contact me please so i can correct it.
XDA:DevDB Information
PlaceboRom, ROM for the Sony Xperia Z Ultra
Contributors
MusterMaxMueller, fusionjack, [vertigo], dboliver, blueether, Christopher83, legolas83, prbassplayer, SlimRoms, CyanogenMod, VanirAOSP, AOKP, Linaro, FreeXperia, CodeAurora, Google
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681, 14.3.B.0.757 or newer
Based On: SlimKat, CynanogenMod, VanirAOSP, AOKP
Version Information
Status: Testing
Created 2014-05-15
Last Updated 2014-05-15
Reserved
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Reserved
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
Looks promising, yah the first F2FS! :highfive:
MusterMaxMueller said:
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Click to expand...
Click to collapse
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
keep it up mate...looking forward for this rom. :good:
@blueether
I think i dont get you. AOSP/Slim is released under ASL. So changes made to rom dont need to be published? Altough i will when i have time. And is defconfig considered part of the kernel? Because of "make menuconfig"? Does anyone know for sure? If i interpret this and this correctly changes to Makefile have to be published but defconfig not. They even mention build flags!I know its pedantic just want to know. It seems there is no defenite time frame when sources have to be published?
blueether said:
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
Click to expand...
Click to collapse
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
mac231us said:
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
Click to expand...
Click to collapse
That did it thank you.
reread it. i think youre right
blueether said:
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
i have no problems using minimal gapps from op.
try using the one from op.
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
F2FS mount and sysfs options
For those interested in tweaking F2FS, check my post here.
wrong install instructions
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
download not working
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Premananda_laishram said:
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Click to expand...
Click to collapse
I'm uploading to mega atm, should be up in about 20 - 30 min
Google Drive mirror: https://drive.google.com/a/fryett.net/file/d/0B2qGRw4S7bAuUkxWVzVXQzNJOXc/edit?usp=sharing
Mega mirror: https://mega.co.nz/#!9pt1xSQL!ozJyip-yzATId0_Po7sG1_sisWH8UfnNVOhHmxh-4fA
Premananda_laishram said:
Please upload to mega or somewhere else
Click to expand...
Click to collapse
you could also use the download tab ?
not working
Flashing instructions not working. Hangs at boot logo
Premananda_laishram said:
Flashing instructions not working. Hangs at boot logo
Click to expand...
Click to collapse
which install instructions doesnt work?
the first or the second one?
try first without flashing gapps.
This thread is for development updates, and an eventual release of testing candidates for the future of dual booting CM12 android roms on the Amazon Fire TV. At this time I am not planing on supporting the Fire TV stick since my development platform is based off USB3 booting.
There currently isn't even a stable branch in CM12 upstream so things are quite tricky right now.
I may eventually setup public nightlies once the core is stable.
IN PROGRESS FORM HERE: https://t.co/TXp9z7htDx
The goals for development are in this order:
Wifi [working]
Bluetooth [crashing]
Stable core [random resets possibly storage related]
Audio [possibly needs hacking to default to hdmi]
Recovery system [rom boots using the recovery partition currently]
Hardware Acceleration [untested]
Android TV addons [require stable core]
USB Formating and install app [apparently not everyone knows what gparted is]
Modified version of Rbox's bootloader [I'd like to add recovery to the loader then have stock and custom boot options]
Also, if you want to be ready for possible nightly testing, I highly recommend going to walmart and buying one of the playstation USB3 hubs. It's about $20 but allows you to plug in a USB3 drive and keyboard and mouse until bluetooth is working.
SETTING UP USB BOOTING:
Code:
#include <std_disclaimer.h>
/* * Your warranty is now void. *
* I am not responsible for bricked devices, dead USB drives,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in these files
* before flashing them! 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. */
PART ONE [Preparing the drive]:
This process will eventually be streamlined but for now I'll explain the process and how it relates to testing builds during development. Since the Fire TV only has an 8gb flash chip and has no hardware recovery trigger, it is quite the unforgiving device to develop on. The current boot method for my CM12 builds involves flashing over the recovery partition and using it as a sort of dualboot partition. The modified recovery partition then searches for ext4 partitions on and external (USB3 preferred) flash drive. Currently each build generates its own boot image to be flashed over recovery, but I'm currently in the process of exploring the possibility of following Rbox's method of loading a boot image from a system folder instead making only one flash to the actual device necessary going forward.
For USB3 booting during the development process I highly recommend using a USB3 hub for a keyboard and mouse while bluetooth pairing and control mapping is being worked on. I also recommend a USB3 drive.
1) Turn on a Linux machine or boot a Live CD
2) Open Gparted
3) Delete any partitions on the usb drive
4) Create three ext4 partitions, the first partion is system and should be about 1GB, the THIRD partition is cache, and should be about 768mb with 0mb following, you should then have the middle portion empty in the display, in this SECOND partition make your data partition fill the rest of the space.
PART TWO [Preparing the bootloader]:
WARNING this process currently involves replacing your recovery partition, remember kids dd and root is like holding a grenade, make sure you don't throw it at something you care about.
Also, if you are testing a build and it does not load using the previous bootloader, try flashing the latest one from the nightlies (and vise versa) as I am still in the process of stream lining the boot process as far as what should take place before system bring up on our device. If a different boot image loads the system with noticeably more stability let me know asap so I can track the causes of my current issues.
Code:
adb connect <STOCK FIRE TV IP>
adb push boot-<DATE>.img /sdcard
adb shell
cd /sdcard
su
dd if=boot-<DATE>.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Next I recommend side loading this apk to make rebooting into USB boot easier.
The three most recent "boot" images have been added to the downloads section, remember these should be flashed to recovery. Although they would work in boot, that would disable Rbox's loader and prevent you from loading stock OS.
PART THREE [Playing with instability]:
Great so now you have a USB3 booting image flashed to your recovery partition and you have an empty flash drive. This is where the tinkering begins. In the download section you will find a .tar.gz archive with a somewhat booting system with the aforementioned issues. Inside this archive is a system.img file which you will use dd to flash to the first partition of the flash drive you formated. After the system image is flashed you can plug your flash drive into your hub and reboot into recovery. Things will be great, wifi will show up and if you're quick enough you can complete setup and make it to the launcher. (the issue I'm currently working on is an odd timed reset that may be kernel or storage related oddly if you make it to the launcher and don't touch anything, it takes longer to reset)
If you made it this far, welcome to development. You can help by "kanging" (replacing system apk's and files with other versions to find more stable matches, or remove apks until things don't die then report back to me) Also if you make it to this point go ahead and fill out the form I mentioned earlier. Eventually any hotfix builds I do between nightly builds will be accessible to those users to play with.
Overhauling the boot system next and working on the reset debugging.
XDA:DevDB Information
TechVendetta ROM Development, ROM for the Amazon Fire TV
Contributors
TechVendetta, rbox
Source Code: https://github.com/TechV/android_device_amazon_bueller
ROM OS Version: 5.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-01-29
Last Updated 2015-01-29
Reserved
UPDATE: I'm pretty much settled in to my new job/home now so I'm going to resume this project shortly. The first order of business is to see what sort of driver improvements we got from Amazon and whether their modifications help resolve the issues I was having. I only have the original FireTV so I'll be only testing on that. Not sure if the new one has an unlocked bootloader or recovery system so that will be up to whichever brave soul wants to test that. Hopefully tomorrow I can resync my repos and get a look at whats changed.
Reserved
Thanks for the update! Looking forward to seeing how this progresses.
Thanks for your work!
It would be nice run a CM12 build in Fire TV
So far the main system seems promising, I feel like the reset issue, which is the primary major roadblock is either in the kernel, or in the storage management/selinux services. Selinux should be disabled in this build so I'm looking into the other two options right now.
TechVendetta said:
So far the main system seems promising, I feel like the reset issue, which is the primary major roadblock is either in the kernel, or in the storage management/selinux services. Selinux should be disabled in this build so I'm looking into the other two options right now.
Click to expand...
Click to collapse
Thank you for keeping us updated!
[email protected] said:
Thank you for keeping us updated!
Click to expand...
Click to collapse
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
TechVendetta said:
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
Click to expand...
Click to collapse
Hey,
i've got one question for the installation:
you use the recovery as boot partition (because you dont want to mess with the actual boot partition where the bootmenu is).
is there a reason we cant use rbox's bootmenu, add another entry "usb boot" which will boot from /system/boot/usbboot.img ?
Or is the only reason that this just hasnt been added by rbox so we have to use another way?
I think this would be the most brick safe version and shouldnt be a big problem for rbox to implement....
Chris
[edit]
i'm really looking forward to this
aHcVolle said:
Hey,
i've got one question for the installation:
you use the recovery as boot partition (because you dont want to mess with the actual boot partition where the bootmenu is).
is there a reason we cant use rbox's bootmenu, add another entry "usb boot" which will boot from /system/boot/usbboot.img ?
Or is the only reason that this just hasnt been added by rbox so we have to use another way?
I think this would be the most brick safe version and shouldnt be a big problem for rbox to implement....
Chris
[edit]
i'm really looking forward to this
Click to expand...
Click to collapse
Thats one of the goals I put up there, just unlike rboxs current loader I know a way to make it remote controlled. ;D I started a bit on it. The "friendly user release" will have a root installer app that will handle multiboot, formating flash drives, recovery options, updates etc.
Really looking forward to a CM12 Android TV ROM. It would be nice to know that Amazon would not be able to kill a rooted Fire TV when this becomes reality. Peace of Mind regarding the Fire TV would be Priceless!
Xposed too http://forum.xda-developers.com/showthread.php?t=3030118
hhairplane said:
Xposed too http://forum.xda-developers.com/showthread.php?t=3030118
Click to expand...
Click to collapse
I'm a big fan of exposed, I'll have to add that to my testing list. I get a bit more free time tonight so I'll be getting back to looking at WiFi and Bluetooth and the installer. I still have two possible routes for both installing and updating i have to consider.
Sent from my LG-VM670 using XDA Free mobile app
TechVendetta said:
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
Click to expand...
Click to collapse
Any luck with the video acceleration, eg for Kodi or others such as Netflix, etc? How about hdmi audio?
Thanks for the update!
Video acceleration appears to be working, haven't got to audio. Had a death in the family this morning so i haven't had time to test my latest build.
Sent from my LG-VM670 using XDA Free mobile app
Sorry to hear that, Family is first! Although, maybe working on this will help take your mind away from that. Feel better!
TechVendetta said:
Video acceleration appears to be working, haven't got to audio. Had a death in the family this morning so i haven't had time to test my latest build.
Sent from my LG-VM670 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry to hear that.
I recently installed CM 12 on a 2012 kfhd and wow!--it really brought that device to life! Performance/OC options are built right into the OS and another Dev made a custom kernel to oc to 1.7 ghz. But I have limited experience with CM and Android TV. Can we expect a similar UI and performance options with this? Or is it different for the set top boxes?
BTW--I think it's really great you're doing this. Lots of people are excited and it's very appreciated!!!
KLit75 said:
I recently installed CM 12 on a 2012 kfhd and wow!--it really brought that device to life! Performance/OC options are built right into the OS and another Dev made a custom kernel to oc to 1.7 ghz. But I have limited experience with CM and Android TV. Can we expect a similar UI and performance options with this? Or is it different for the set top boxes?
BTW--I think it's really great you're doing this. Lots of people are excited and it's very appreciated!!!
Click to expand...
Click to collapse
I can overclock the kernel but I'm not sure if it will be necessary yet. As for the features, CM12 doesn't even have a "stable" build yet. (they call them M builds now) They are still porting customizations like that in. That rom may use some stuff pulled in by the dev from other projects like paranoid, aokp etc. I'm listening to what people are asking for and I'll be taking it into consideration once I get to tweaking release candidates.
TechVendetta said:
I can overclock the kernel but I'm not sure if it will be necessary yet. As for the features, CM12 doesn't even have a "stable" build yet. (they call them M builds now) They are still porting customizations like that in. That rom may use some stuff pulled in by the dev from other projects like paranoid, aokp etc. I'm listening to what people are asking for and I'll be taking it into consideration once I get to tweaking release candidates.
Click to expand...
Click to collapse
Sounds great. Thinking now...an OC kernel probably isn't necessary since it's already real fast. But this rom I have works well on a relatively low end/older device. So I'm super excited about your project. Thanks again!
Announcing Sailfish for the Sony Xperia SP
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Update 15 Feb 2016
I've uploaded a new version of SailfishOS 2.0.0.10 to the Mega folder, called sailfishos-huashan-release-2.0.0.10-1.zip. This is again based off CM-12.1, the same release as stated below. This release fixes a kernel bug which lets a lot of the Sailfish system crash. This also fixes the wlan connectivity, startup-wizard which sets the themes, on-screen keyboard not popping up, and SIM unlock never asked. I've got a fix for the backlight in the works.
Update 14 Feb 2016
A very experimental CM-12.1 based SailfishOS 2.0.0.10 build is uploaded to the Mega folder linked below.
This version is based off cm-12.1-20160212-NIGHTLY-huashan.zip. I want to stress that many things in this build are broken.
Update 05 Feb 2016
This port is heavily outdated. I do not have much spare time on my hands to continue porting but I will try to post a nightly version soon.
This version was based on Sailfish 1.1.6 and CM-11.0, but the world has moved on to Sailfish 2.0 and CM-12.1, and so must this port.
There's a photo up on imgur:
http://i.imgur.com/Vg3SZ6w.jpg
Special thanks to:
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Everyone from the SailfishOS team/community, sledges and mal- in particular.
Known issues:
Half the backlight doesnt work, this is clearly visible at the top of the screen
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Settings hangs for few seconds on first start (this seems to be related to bluetooth not being set up)
What works:
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi, GPS (does take a while to get a fix though), most of the sensors (proximity, lightsensor etc)
The half of the display backlight that does work is adjusted based on lightsensor input.
Charging, bottom ledbar basic functionality, audio works, audio via 3'5 jack also works.
Installation:
Insert default warranty void message here. Your warranty is now void
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an offical Sailfish OS build, and the Xperia SP is not the Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, search for it first on bit.ly/port-bugs, if your bug is not yet there, you can add it there or post it in this thread (I'll try to keep the xda thread and bugzilla in sync).
The Sailfish OS image does not provide recovery, and since the Xperia SP does not have a recovery partition, you need a seperate bootimage with only recovery on it to flash cm/stock/sailfishos upgrade.
The Sailfish OS image is based on a specific version of Cyanogenmod 11, which you will need to flash first.
You can find all the required files in a Mega folder: http://mega.nz/#F!7YhSTDIA!Akpjs8s3qT5_nEkN04fQ-Q
You can find a bootimage with only TWRP recovery in it called recoveryboot.img
This image can be flashed with fastboot (with phone turned off, hold vol up and plug in usb), then `fastboot flash boot recoveryboot.img`. After that reboot the phone (fastboot reboot), and it will boot into recovery. If you already have recovery from cm, then you can use that as well.
First do a full wipe (make a backup first if needed, TWRP can do this , then install CM11, the specific version you need is called: cm-11-20150712-NIGHTLY-huashan.zip
There is no need to reboot cause you wont use CM11 anyway, so just proceed and flash the Sailfish OS image, which is called: sailfishos-huashan-release-1.1.6.27-UNOFFICIAL-maikel-201508201214.zip
Flashing Sailfish OS is not as fast as flashing cm11, but it shouldn't take more than 10 minutes.
Then reboot. The first boot may take some time, during which the Sony logo is not displayed (WIP).
If the boot takes more than, lets say five minutes, try a reboot. You can power off the device by holding the power button until the LED bar turns red or the display brightness goes back to full, when the leds and display turn off the device is powered off.
If this doesn't work you can remove the back cover and press the little button in the little hole for 5 seconds, the device will vibrate thrice and the phone will be forced off.
If you want to return to your previous rom or restore a backup, use the recoveryboot.img using the commands stated at the top of this document, to boot into TWRP.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Sources
In order to comply with the GPL, the kernel sources used for this port are available here:
CM-11.0 based port: https://github.com/maikelwever/android_kernel_sony_msm8x60
CM-12.1 based port: https://github.com/maikelwever/android_kernel_sony_msm8960t
edit: make links + sailfish 2.0 notice, kernel sources, 2.0 link
You rock! Very interesting project. Sailfish is an unknown world for me (and for most of us I think), I might try this ROM out sooner or later.
Why do we need to install CM11 first? Is it based on it?
Goob job bro!!!!
But I'll try this port later since it's kinda buggy
Hope you will fix those bugs.
Tomoms said:
Why do we need to install CM11 first? Is it based on it?
Click to expand...
Click to collapse
SailfishOS uses libhybris to communicate with the hardware, which in turn is talking to the Android HAL (like hwcomposer), to avoid having to write drivers for each phone, which would be pretty much impossible due to the proprietary blobs used on almost every phone.
The libhybris build included in this SailfishOS port is based on CM11, so that's why you need that.
CM12 based SailfishOS is currently experimental, when that gets more stable I will try to make a CM12 based build.
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
boylush said:
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
Click to expand...
Click to collapse
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
maikoool said:
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
Click to expand...
Click to collapse
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Tomoms said:
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Click to expand...
Click to collapse
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
maikoool said:
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
Click to expand...
Click to collapse
man i was waiting for this thing :fingers-crossed:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
will follow this thread closely...........
finally something new and different to use.
cheers
avi.singh9993 said:
will follow this thread closely...........
finally something new and different to use.
cheers
Click to expand...
Click to collapse
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
This looks really good, if it will ever be in daily driver state this will be my go to rom
sledges said:
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
Click to expand...
Click to collapse
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Why don't you post please? DIT - doing it together!
sledges said:
Why don't you post please? DIT - doing it together!
Click to expand...
Click to collapse
well i asked my friend to post it,
many people saw it but unfortunately not much of a positive feedback.
now it's onto developer and his hardwork to develop and make it atleast daily driver. then some people will be interested in trying it
Tomoms said:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
Click to expand...
Click to collapse
I agree totally that it's the dream of a geek. I've noted all your comments and will try to fix them. Thank you very much for taking the time to test!
Spasik said:
This looks really good, if it will ever be in daily driver state this will be my go to rom
Click to expand...
Click to collapse
That's what I'm aiming for too!
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Sorry, but I couldn't care less about Facebook. I'm pretty convinced that everyone that is willing to try something like this is already on XDA anyway. Hopefully the work related part will be better possible when Android app emulation or something similar finally makes it to community Sailfish builds.
PS: I've been a bit busy with other things lately, sorry for not responding that fast. I'll try to roll a build with fixes and the latest Sailfish (1.1.7.28) asap.
This has changed the mac of my device
can I ask how's the development going?
If someone could port the only rom i would like to be ported on the SP: ColourOS, it will be AMaZING
After further developments we have realised making a whole new kernel is not worth it as all functions we could want can be just made into a custom ROM
This Project is now currently about how to make android wear darker, basically a theme for it. Since android wear those not contain any theme engine all ui mods must be done by hand ie apk modding. Anyone willing to mod the ui is welcome to do so as I do not have time but I will compile it into a system.img
For everyone to enjoy here are all the apks contained in the system ie everything with a GUI.
modify at your will and upload fully working signed apk if you would like to test it
XDA:DevDB Information
Make Android Wear Great , ROM for the LG G Watch
Contributors
Xmaster24, invisiblek
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 6.0.1 bootloader
Based On: Stock
Version Information
Status: Testing
Created 2016-02-24
Last Updated 2016-04-08
Reserved
Latest changelog will be kept here find rest HERE
24/02/2016: 0.2
Removed Files (can all be found HERE)
/etc/NOTICE.html.gz
/recovery-from-boot.p
/framework/wifi-service.jar
/bin
applypatch
install-recovery.sh
/lib/wifi-service
(See post below for all explanations)
Added Files:
/priv-app/LgeWatchFace (for fall back on factory reset)
23/02/2016: 0.1
/app
LGeWorldClock
PreBuiltWearFit
/priv-app
MinModWatchfaces
PrebuiltWearsky (might cause breakage)
WristGesturesTutorial (same as ^)
LgeWatchFace
Nice job! We would probably prefer not crippling fresh installs, so getting at least one watch face back in would be ideal.
Check out `the fonts/ directory, I bet some of those can be tossed out. Looks like you might gain a nice chunk of space by doing that. May need to look at/tweak etc/fonts.xml and etc/system_fonts.xml though, they reference the ttf files.
recovery-from-boot.p can definitely go. We don't need that.
These hals can probably go since they should be overridden by their msm8226/dory counterparts in the same dir. (Not saving much room at all by doing so, but it might get to the point where every kb counts)
lib/hw/power.default.so
lib/hw/audio.primary.default.so
lib/hw/gralloc.default.so
Others that should be fine:
etc/NOTICE.html.gz
Might cause some breakage, but since we don't have wifi you could try removing these:
lib/libwifi-service.so
framework/wifi-service.jar
Some other ideas I had if it came down to it would be to move some of the apps to /data/. Maybe creating a flashable zip or something to do so?
Another idea would be to ship one or several "mini" squashfs images and mount them right after we mount /system/. For instance a fonts.img that's just the fonts/ directory, we could mount it during init right after system gets mounted. Not sure how much extra compression would be needed or space gained, and really this would probably be a last resort hack, but might just do the trick.
Yet another idea is to shove more things into ramdisk, we have some room there still.
EDIT:
These can go too:
bin/install-recovery.sh (this is what clobbers twrp every boot, service is disabled in my ramdisk, but we should kill it anyway)
bin/applypatch (only install-recovery.sh needs this)
invisiblek said:
Nice job! We would probably prefer not crippling fresh installs, so getting at least one watch face back in would be ideal.
Check out `the fonts/ directory, I bet some of those can be tossed out. Looks like you might gain a nice chunk of space by doing that. May need to look at/tweak etc/fonts.xml and etc/system_fonts.xml though, they reference the ttf files.
recovery-from-boot.p can definitely go. We don't need that.
These hals can probably go since they should be overridden by their msm8226/dory counterparts in the same dir. (Not saving much room at all by doing so, but it might get to the point where every kb counts)
lib/hw/power.default.so
lib/hw/audio.primary.default.so
lib/hw/gralloc.default.so
Others that should be fine:
etc/NOTICE.html.gz
Might cause some breakage, but since we don't have wifi you could try removing these:
lib/libwifi-service.so
framework/wifi-service.jar
Some other ideas I had if it came down to it would be to move some of the apps to /data/. Maybe creating a flashable zip or something to do so?
Another idea would be to ship one or several "mini" squashfs images and mount them right after we mount /system/. For instance a fonts.img that's just the fonts/ directory, we could mount it during init right after system gets mounted. Not sure how much extra compression would be needed or space gained, and really this would probably be a last resort hack, but might just do the trick.
Yet another idea is to shove more things into ramdisk, we have some room there still.
EDIT:
These can go too:
bin/install-recovery.sh (this is what clobbers twrp every boot, service is disabled in my ramdisk, but we should kill it anyway)
bin/applypatch (only install-recovery.sh needs this)
Click to expand...
Click to collapse
I looked through the fonts and yes a lot of the non-English ones can go but that would destroy international support
Was going to create installer for removed watchfaces as they really don't require system access,fit could also be installed on /data not sure if step counting will still work, main reason to have the app at all. Thanks for suggestions will add smallest watchface back and delete the suggested files tomorrow
@invisiblek could you also create a recovery with the ability to wipe the new system as @rbox 's build cannot do so for future updates when we create a recovery package so the new system can actually be flashed PS. I gave you edit permissions for the files
Do you know what prebuiltwearsky.apk does?
Phonesky.apk is the Phone's Play Store
Sent from my Nexus 10 using Tapatalk
drewski_1 said:
Do you know what prebuiltwearsky.apk does?
Phonesky.apk is the Phone's Play Store
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Thanks for pointing that out but seeing as Android wear has no playstore I assumed it was the sky watchface
Edit; just checked, yes it's package id is com.android.vending so it must be some playstore for wear. Wonder what it's purpose is as all apps regardless of source can communicate to wear and install apps. Hopefully after @invisiblek s changes it will be able to fit whatever functionality it serves. Never thought I would say this in 2016 but it's quite large at 2.95 MB will hope it fits
edit edit: now that I think about it it might just be a residual app from wifi enabled watches as you are able to install apps to those while they are connected to wifi and not the phone by bluetooth. Can someone test it to be sure? thanks
Thinking of calling this freedom rom as it gives us the freedom to R/W to system. Looks like someone already beat me to it http://forum.xda-developers.com/verizon-galaxy-s5/development/wip-aosp-themed-rom-t3098153 thread seems dead thought won't mind if we use it
Edit even better idea Freedom ROwM (Read Or write) as I kinda pun because ROM = read only memory but this whole project is to make it Read Write
Bad news everyone just tested build and @invisiblek 's kernel cannot boot the system. Will update soon hopefully
Xmaster24 said:
invisiblek could you also create a recovery with the ability to wipe the new system as rbox's build cannot do so for future updates when we create a recovery package so the new system can actually be flashed PS. I gave you edit permissions for the files
Click to expand...
Click to collapse
Well, twrp inherently auto-detects the filesystem before wiping it. It look like there are options in there to change the filesystem though. I could mess around with adding squashfs formatting support, but that really doesn't do much for us.
Xmaster24 said:
Bad news everyone just tested build and @invisiblek 's kernel cannot boot the system. Will update soon hopefully
Click to expand...
Click to collapse
Any chance of getting a kernel log from this?
invisiblek said:
Well, twrp inherently auto-detects the filesystem before wiping it. It look like there are options in there to change the filesystem though. I could mess around with adding squashfs formatting support, but that really doesn't do much for us.
Any chance of getting a kernel log from this?
Click to expand...
Click to collapse
Device is completely undetected by pc and is essentially bricked so yeah don't have a jtag or anything
It's up for grabs if you wanna try it. It did no damage to my device maybe to my pants because I could not boot to bootloader but managed to anyway. Will send you stock squashfs image if you don't already have it
I am watching and waiting to test.
---------- Post added at 02:46 PM ---------- Previous post was at 02:44 PM ----------
Could we use a Linux kernel that supports healthy honey? And more so towards slimsaber ROM for the LG G2?I am wondering if marshmallow os might conflict with my current daily driver ROM . I think a Linux kernel will make this ROM more compatible for different roms.
Crumplet said:
I am watching and waiting to test.
---------- Post added at 02:46 PM ---------- Previous post was at 02:44 PM ----------
Could we use a Linux kernel that supports healthy honey? And more so towards slimsaber ROM for the LG G2?I am wondering if marshmallow os might conflict with my current daily driver ROM . I think a Linux kernel will make this ROM more compatible for different roms.
Click to expand...
Click to collapse
I think you are on the wrong forum this is for the LG G watch not LG G2
Just to add ; all android devices run off a Linux kernel, Literally all of them even the x86 ones and what in the hell is healthy honey? All google shows is some Honeypot distro for pc. You seem to be trolling me cause you must be high when you wrote this
what are the possible benefits in switching to EX4 filesystem?
Just curious here on one thing.... how hard would it be to remove the tutorial stuff that you have to always go through upon doing a factory reset and G Watch setup? This ROM looks promising for sure.
Also a few name ideas:
FreedomG ROM
LibertyG Watch
SleekWatch ROM
MarshSlimmed ROM
SlimmedG ROM
SleekG ROM
GWatch Slimmed ROM
AngryManMLS said:
Just curious here on one thing.... how hard would it be to remove the tutorial stuff that you have to always go through upon doing a factory reset and G Watch setup? This ROM looks promising for sure.
Also a few name ideas:
FreedomG ROM
LibertyG Watch
SleekWatch ROM
MarshSlimmed ROM
SlimmedG ROM
SleekG ROM
GWatch Slimmed ROM
Click to expand...
Click to collapse
I have removed the gesture tutorials apk which should get rid of all those tutorials. Thanks for the name suggestions
Jaocagomez said:
what are the possible benefits in switching to EX4 filesystem?
Click to expand...
Click to collapse
Ext4 is R/W while the current SquashFS is R/O
Dirty Unicorns Android 9, PIE by Flintman for HP TouchpadClick HERE for How to Flash the ROM
________________________________________________________________
Work in progress, not workingBluethooth
Camera
Home button________________________________________________________________
Disclaimer: I am not a developer, just a regular user like YOU.
That have found a way to improve the Tablet and would like others to benefit by sharing the information.
I am not the creator of the ROM or Recovery mentioned.
All credits goes to the developer@flintman and the Dirty Unicorns Team.
________________________________________________________________
Nice Find Thanks!
Touchie Pad said:
Nice Find Thanks!
Click to expand...
Click to collapse
You are welcome!
The following does not work, installing only the ROM.
Camera
Bluetooth
Youtube plays very well
Very smooth
Microphone works.
Wifi works perfectly.
The only problem is that the internal storage is not accessible.
It can not even save screenshots, no access. ( it is fix on the 3-28-2019 version )
I dirty flashed the 13.x over 12.5x and did not do the open gapps, so I will have to sideload them I guess at some point since I cannot get to internal storage like you said.
It boots up, but lots of stuff does not work (like bluetooth). At least the March 2019 security updates are in place!
Thanks
I can't believe we now have Pie on the old work horse. Thank you so much. I wiped everything but internal storage and did a clean install with open pico gapps. I had previously installed the DU swap in the boot directory and booting with it goes to a boot loop. I went back to 8.1 and deleted the DU swap in the boot directory and did another clean install of 9. It came right up and the few apps I have installed work. I tried installing YouTube but the play store says this version is not compatible. It won't even show it as an option. There is no access to storage from either the files app or ES File Explorer. I even tried USB with Windows and android shades out the file transfer option. All my other Pie devices give you an option in setting to set up the SD as either removeable or internal memory. I am wondering if we need to reformat internal memory to get access. I hate to kill it since I have all my install files there as well as TP Toolbox. Any suggestions welcome.
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage. ( is all fixed on version 3-28-2019 )
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
HP_TOUCHPAD said:
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage.
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
Click to expand...
Click to collapse
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes. I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working. I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
johnbelloh said:
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes.
The partition sizes applied using the following:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
Will work with Pie, Q and any future release of Android.
The /system partition is set to 1.8G, which can accommodate a Super variant of the google open gapps.
I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working.
Is storage space not Memory or RAM. It will be about 500MB to 600MB extra of storage space not Memory, it does not affect performance.
I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
Click to expand...
Click to collapse
There is no SKZ kernel for Pie at the moment and it will not work with Pie 9 as it only works with 8.1.
The stock Kernel of Pie 9 is not optimize yet to use the swap partition, as soon as Pie is fix it will be available and the system will improve performance and stability as more RAM (Memory) will be available in Android. (Update Pie is completely optimize more than any other ROM
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
larrywilson said:
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
Click to expand...
Click to collapse
Thanks for the update ! The direct link now is updated to 03-28-2019 built.
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
johnbelloh said:
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
Click to expand...
Click to collapse
Android Pie is optimize and is swap enable from the core, all settings are set to be use with the swap partition.
Flintman did a marvelous job incorporating all the changes and making Pie available for the HP Touchpad with more improvement on its way that it could be the best ROM ever. I will update this guide soon.
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Steelskinz said:
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Click to expand...
Click to collapse
If you are using 8.1 now and enjoying your setup, then my recommendation is to keep using it that way until Pie which is 100% stable now with more features than 8.1, gets Bluetooth working and any other minor issues resolved. As of now Pie is working as Oreo. Pie is using the swap partition and fully optimized as 8.1 and 7.1.2. The only thing to do is to flash it just like any other ROM.
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
Thanks, Lister
Lister Of Smeg said:
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Yes Flintman still providing support and now has created the best ROM.
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
The swap partition must be created as in this guide:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
WebOS came with a swap partition and all the ROMS were install side by side with WebOS but never implemented the use of SWAP, Android 9 is the first ROM to completely take advantage of swap thanks to Flintman for applying all the changes. And all future version of Android for the HP Touchpad will have support for the swap partition.
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
Yes the partition that is created is the original from WebOS dev/store/swap.
In WebOS is a 400 MB
The new partition is 500 MB, it can be change to any size if the user wants to.
If you want to use any new ROM, 7.1.2 ,8.1 and 9 the /system partition must be 1400 MB, it can be resize using the ToolBox.
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
The /boot partition is a fix 32MB can not be change and there is no need for it to be larger.
Download the ToolBox from Here
Unzip the file rename TPToolbox-2015-01-08-v42.bin to uImage.ToolBox
Using TWRP Recovery mount /boot and using the TWRP File Manager copy uImage.ToolBox to /boot.
Using TWRP any boot uImage can be move from /boot to the SDCARD and then can be copy back.
There is no need for /boot to be larger as the boot files can easily be copy to it when need it to be use.
Think of it as a CD or USB disk that you insert into the PC to boot from, is the same concept. If you need to use the ToolBox make some space by removing a boot uImage and then copy the ToolBox in /boot.
Thanks, Lister
Click to expand...
Click to collapse
You are welcome!
Hi @HP_TOUCHPAD,
First of all, thank you for the very prompt and DETAILED reply, this is perfect and contains EXACTLY what I need to know. And apologies for the delay getting back to you, my brothers son has been in hospital last couple of days... So been a bit back and forth.
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition. Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
Thanks once again...
Lister
HP_TOUCHPAD said:
You are welcome!
Click to expand...
Click to collapse
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition.
Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
The ROMS Kernels available from my guide for Evervolv 7.1.2 and DU 8.1 are my changes to make use of swap with optimization.
Flintman integrated all the changes posted on my guide to the Kernel, Ramdisk and also to the ROM of Pie (9).
Android Pie (9) is the first ROM to completely take advantage of the swap partition thanks to Flintman for improving and making the extra changes.
Thanks once again...
Lister
Click to expand...
Click to collapse
You are welcome.
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Click to expand...
Click to collapse
The /boot partition is 32MB, It shows that WebOS is also installed. Before moving any files from /boot make sure to do a backup just in case if the wrong file gets removed. The ToolBox does not need to be in the /boot directory to be use . It can be loaded into the memory by placing the Tablet into Recovery Mode and from the PC with the novacom drivers install load it.
novacom boot mem:// <uImage.ToolBox
The ToolBox will be loaded into memory and use for anything need it, there is no need to keep it in the /boot.
The most important file to be in /boot uImage.moboot 63.KiB (boot manager)