Related
HI is there any method to convert the default PA kernel to ALL-F2FS supported kernel..??
Nexus 7 wifi Grouper.
Twrp 2.7.1.1
Manually converted /system,/cache,/data partitions to f2fs using TWRP recovery.
then adb sideloaded PA 4.4 RC2. and it doesnt boot (loop) and /system converted to ext4 partition.
i can use the lego kernel or i can convert PA ROM to all f2fs supported using app but it will install Lego Kernel.
But i want to use the default kernel from PA to use with f2fs.
is there any solution..??
Default kernel is Google kernel...
#stayparanoid
Yeah I know that.. But is it possible to tweak the kernel to include f2fs drivers in it..!!
Sent from my Nexus 7 using XDA Premium 4 mobile app
We won't do it. You need to check the f2fs threads on what needs to be done but we will not support f2fs at this time which means we won't be patching or compiling anything extra to support it
#stayparanoid
Oh,,, hell yeah, i want it badly. :victory:
+1
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
SGWUser said:
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
Click to expand...
Click to collapse
Maybe sir arco will save us again when the sources are released You never know..
a port may come soon but we have to wait until it is final so they release cm 12
eri000 said:
a port may come soon but we have to wait until it is final so they release cm 12
Click to expand...
Click to collapse
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
dqsnunes said:
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
Click to expand...
Click to collapse
the CM team announced that there will be NO CM version until the google releases the final image of android L on AOSP.This doesn't mean we will have a final stable version of cm immediately BUT we will only see a cm12 build when final android L gets merged into aosp.
^That is for other phones that get CM OFFICIAL.For ancora we have to wait a little bit more for unofficial cm, which is based on official cm.So no official--- no unofficial (arco if he has time to mess with it,or others)
BTW, Android L is currently being ported to the Nexus 4 and Nexus 7 2012 right now. Both are almost functional.
I think even if we were to have Android L here, i don't think it will be responsive. Google said, Animation transitions run at 60fps, Im not sure if overall perfomance can run at the same fps because i bet our processor is not powerful enuff or smth. CMIIW.
Android L Port For Nexus 4
Newest Android L Port For Nexus 4 Is Now Fully Operational And Ready For Download
INFO
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
A swap partition for art can't help?
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Nice thinking and good luck :good:
sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Umm very interesting if you want some testers,i'm here.
If you have cm11 theme chooser:
http://forum.xda-developers.com/android/themes/theme-l-ready-t2802979
https://play.google.com/store/apps/details?id=nexbit.icons.moonshine
Settings>Performance>Force high-end graphics>check
AND YOU HAVE L IN YOUR WONDER(I LOVE MY WONDER)
what is android L? can someone tell me about it please?
smartiescoke said:
what is android L? can someone tell me about it please?
Click to expand...
Click to collapse
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
arsradu said:
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
Click to expand...
Click to collapse
whoa! really? awesome! i always been waiting google to update different kind of android version. ui and etc, hope it will come to our wonder soon! XD
oh man i love android L ui and statusbar. Hoping our Great Developer can bring this to our Wonder.
#sorry for my bad english.
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Monster212 said:
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Click to expand...
Click to collapse
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
SkOrPn said:
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
Click to expand...
Click to collapse
thank you very much for the reply.. i learned something new...
Monster212 said:
thank you very much for the reply.. i learned something new...
Click to expand...
Click to collapse
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
SkOrPn said:
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
Click to expand...
Click to collapse
Thank you for the info, I will now be looking for a good rom or kernal.....
Sent from my SM-T700 using Tapatalk
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
ashyx said:
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
Click to expand...
Click to collapse
thank you i will install it now and see how it goes...
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
SkOrPn said:
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
ashyx said:
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
Click to expand...
Click to collapse
Yeah agreed, EXT4 is slightly faster at reading, but just by a hair on my N7. However, on partitions that have write permissions, it can "sometimes" be three times faster at random writes. I been using F2FS since feb 2014 "religiously" on my Nexus 7 (and wont run a non-f2fs setup on it), so I am very well versed in its use. Legolas was the first one to bring it to custom Android (I know because I was one of his support techs helping users convert to it, until he disappeared that is lol. Then I started helping USBhost with CarbonROM), and was the first to release a F2FS app in the play store. He was also the first, and only individual, to have a Conversion app to convert your ROM to f2fs, which gave new life to my N7 and any ROM I tried back in 2014 (it did not support 5.0 though). Without F2FS, sadly my Nexus 7 is almost worthless.
If only I can find the many screenshot test results we've done with F2FS, it would come in handy here too. On the N7 its a night and day difference, but here this device is already plenty fast. Id love to see some insane results though.... If only Jaegeuk would develop a Windows driver already. I would like to use it for my Linux box, Windows and Android tbh, and format the sdcards with it, and maybe even USB storage drives to try and pick up on the write speeds a bit. Well see I guess...
My SkyHigh TW LL 5.0.2 kernels support both EXT4 and F2FS for DATA and CACHE partitions.
Note: You need to have supported base firmware for successful flash.
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
deadman96385 said:
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
Click to expand...
Click to collapse
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
UpInTheAir said:
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
Click to expand...
Click to collapse
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
deadman96385 said:
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
Click to expand...
Click to collapse
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
UpInTheAir said:
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
Click to expand...
Click to collapse
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
deadman96385 said:
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
Click to expand...
Click to collapse
It's the same (similar) ramdisk fstab changes for Samsung based kernel as well, not just source. Edit: As I said, all you need to do to actual "ROM" is just format the relevant partitions.
Hi,
I just ran Androbench for EXT4 and F2FS. Here are the results.
Tests EXT4 F2FS
1st pass 2nd pass 1st pass 2nd pass
Seq Red 119.39MB/s 123.15MB/s 130.49MB/s 130.25MB/s
Seq Write 25.34MB/s 25.4MB/s 27.18MB/s 27.03MB/s
Random Read 7.08MB/s 7.4MB/s 7.29MB/s 7.62MB/s
Random write 2.29MB/s 2.34MB/s 4.32MB/s 3.45MB/s
it would be nice if kenel n rom dev, make full support of f2fs either lollipop n kitkat
caldran said:
Hi,
I just ran Androbench for EXT4 and F2FS. Here are the results.
Tests EXT4 F2FS
1st pass 2nd pass 1st pass 2nd pass
Seq Red 119.39MB/s 123.15MB/s 130.49MB/s 130.25MB/s
Seq Write 25.34MB/s 25.4MB/s 27.18MB/s 27.03MB/s
Random Read 7.08MB/s 7.4MB/s 7.29MB/s 7.62MB/s
Random write 2.29MB/s 2.34MB/s 4.32MB/s 3.45MB/s
Click to expand...
Click to collapse
what rom and configuration did u use?
i tried with latest cm11, got a bit higher read speed but worse write speed than yours
Is it just me or f2fs isn't very battery friendly?
antr34 said:
it would be nice if kenel n rom dev, make full support of f2fs either lollipop n kitkat
Click to expand...
Click to collapse
Support for F2FS is already in All lollipop Roms for data and cache
hellskyer said:
Is it just me or f2fs isn't very battery friendly?
Click to expand...
Click to collapse
AFAIK, F2FS shouldn't have any affect on battery
onano said:
Support for F2FS is already in All lollipop Roms for data and cache
Click to expand...
Click to collapse
yeah but not in /system partition, i know its read only partition but according to the bench it should also give some boost, while in kitkat rom still need manual modification in updater-script n fstab in ramdisk boot.img.
any1 know how to make miui f2fs compatible?
antr34 said:
yeah but not in /system partition, i know its read only partition but according to the bench it should also give some boost, while in kitkat rom still need manual modification in updater-script n fstab in ramdisk boot.img.
any1 know how to make miui f2fs compatible?
Click to expand...
Click to collapse
well, our dev has not enabled it for system then there must be a reason.
Bringing to you Resurection Remix 5.6.8. This is an unofficial ROM which is built from source by merging Evervolvs Legacy code and HD2 related files.
Be warned The ROM is still at its early alpha stage
Credits:
CM TEAM for the amazing features and allowing me to build the rom.
EVERVOLV TEAM for the legacy codes.
@macs18max,marc1706, Tytung, Sportsstar89, Securecrt, Xylograph, ph03n!x, datagr, Rick_1995, Daekin, BSDgeek_Jake
texasice, marco.palumbi, Robbie-P, PixelFreak, chautruongthinh, Nikez for all HD2 kernels, libs, mods, corrections
azam, gilbert, @spezi77, elginsk8r , Kirmaniarslan, , legacyxperia, christian, onell, philipped346, Robbie-P, legacyxperia team
Working:
Wifi
Ril(cal,messenger)
Touchscreen
Audio
Sdcard
Mtp mode
Adb
Bugs:
Camera
Bluetooth
Ril(data)
Download:
Rom: https://drive.google.com/file/d/0B-TpiHEnTdWrcHFRZ3B4aUh5Mnc/view?usp=sharing
NativeSD recovery: https://drive.google.com/file/d/0B1gea2aywqJYcFJSSXFwUTdUV1U/view
All friend like my work,press Thank button
XDA:DevDB Information
[May 17.2016][M 6.0.1][ Resurrection Remix 5.6.8][Unofficial] Kernel 3.0.101 [ION], ROM for the HTC HD2
Contributors
thinhx2
Source Code: https://github.com/maniacx
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: AOSP,CM
Based On: AOSP
Version Information
Status: Testing
Created 2016-05-17
Last Updated 2016-08-02
Installation Instruction:
1. You need MAGLDR installed
2. Use NativeSD RECOVERY by downloading and extracting the folder name "recovery" into your sdcard. Then in MAGLDR, Choose boot folder as "recovery" in "Services > BootSettings > AD SD Dir".... Then Boot "AD SD"
3. You need a sdcard with 2 sd-ext partitions. You can create using recovery or laptop. There are lot of tutorial may not be exact
Installation video by onell http://forum.xda-developers.com/showpost.php?p=62279769&postcount=563
Installation video by intoSmartphones Toderici https://www.youtube.com/watch?v=4mj_pgtlXC8
You can use ext4. But you should make sure that both partitions are of the same format.
Create 2 partitions ext4 or f2fs 1Gb and up,swap partition 128mb and up. Now rom can work with ext4 or f2fs partitions
If you had additional swap or sdext3 partition, no problem, it will not interfere with the ROM. No need to remove addtional partition swap or sd-ext if any exist.
4. Reboot to recovery again..
5. Now copy the zip to the ROM and Install the ROM
6. Reboot to MAGDLR
7. Choose boot folder as NativeSD folder in MAGLDR > Services > BootSettings > AD SD Dir
8. Boot AD SD (Boot time take 20 mins... )
9. You can install both ROM (Like NativeSD ROM ) as ROM install in separate folder.
Rom build from source,no modified. This rom use boot.img to boot but magldr no support boot.img and boot from sdcard. This is fix:
Ext4 :http://forum.xda-developers.com/showpost.php?p=66895279&postcount=14 Thank @Robbie P help me
F2fs : use zImage ext4, initnd.gz f2fs :https://mega.nz/#!CkY2kSjK!Cqw678JnO.Q4xZKnI49knS5M thank @philipped346 share
Up
Hi thinhx2 thanks for your work, there are a couple of problems with the updater script.
Firstly it wipes sd-ext partition before installing /system directly to it, therefore you lose any nativeSD builds already installed
Secondly, it tries to install boot.img to a boot partition in NAND. We need to separate initrd.gz and zImage and install them to NativeSD folder on sdcard.
Am just trying this now, we will see if it boots, fingers crossed.
Robbie P said:
Hi thinhx2 thanks for your work, there are a couple of problems with the updater script.
Firstly it wipes sd-ext partition before installing /system directly to it, therefore you lose any nativeSD builds already installed
Secondly, it tries to install boot.img to a boot partition in NAND. We need to separate initrd.gz and zImage and install them to NativeSD folder on sdcard.
Am just trying this now, we will see if it boots, fingers crossed.
Click to expand...
Click to collapse
I can use file initrd.gz from cm13? I dont see this file in my folder build rom
thinhx2 said:
I can use file initrd.gz from cm13? I dont see this file in my folder build rom
Click to expand...
Click to collapse
magldr doesn't use boot.img, you have to extract the kernel and the ramdisk from it, I used this http://forum.xda-developers.com/showthread.php?t=2523070 then add 6mb of zeros to the ramdisk (initrd.gz)
will upload them soon, am still on bootanimation....
Edit; optimizing apps.....
Robbie P said:
magldr doesn't use boot.img, you have to extract the kernel and the ramdisk from it, I used this http://forum.xda-developers.com/showthread.php?t=2523070 then add 6mb of zeros to the ramdisk (initrd.gz)
will upload them soon, am still on bootanimation....
Edit; optimizing apps.....
Click to expand...
Click to collapse
And ...... ?
Bro can upload initrd.gz? Thank bro
thinhx2 said:
And ...... ��
Bro can upload initrd.gz? Thank bro
Click to expand...
Click to collapse
will do as soon as it finishes building dalvic, the new initrd.gz is on sdcard.
Am on 43 of 85.....
Robbie P said:
will do as soon as it finishes building dalvic, the new initrd.gz is on sdcard.
Am on 43 of 85.....
Click to expand...
Click to collapse
If booted bro can send me initrd.gz and take screenshot or picture? Thank bro. Now i need sleep. I try build this rom in 3 day. So crazy. Good luck
thinhx2 said:
If booted bro can send me initrd.gz and take screenshot or picture? Thank bro. Now i need sleep. I try build this rom in 3 day. So crazy. Good luck
Click to expand...
Click to collapse
Yes sir, will do. THANK YOU and sleep well.
71 of 85...
Robbie P said:
Yes sir, will do. THANK YOU and sleep well.
71 of 85...
Click to expand...
Click to collapse
Hehe good night waiting screenshot-picture
News?
downloading and see for instal , thank's bro .
philipped346 said:
downloading and see for instal , thank's bro .
Click to expand...
Click to collapse
No need download bro,waiting file initrd.gz from Robbie P
it boots fully. I had a reboot after boot but it is running smoothly now.
Received a text.
Not sure if data is working yet.
Can't work out how to take a screenshot, vol dn and power, home and power don't work. Will try harder.
Have attached initrd.gz
Also attached zImage, renamed to zImage.img so as to upload it, just rename it to zImage, put both in NativeSD folder and boot it from ad sd.
Remember this will wipe sd-ext, so best use a fresh sdcard with 2 ext partitions, both ext4 or both f2fs (not tried f2fs)
Edit; the attached initrd.gz will not work with f2fs, just ext4 for now.
Robbie P said:
it boots fully. I had a reboot after boot but it is running smoothly now.
Received a text.
Not sure if data is working yet.
Can't work out how to take a screenshot, vol dn and power, home and power don't work. Will try harder.
Have attached initrd.gz
Also attached zImage, renamed to zImage.img so as to upload it, just rename it to zImage, put both in NativeSD folder and boot it from ad sd.
Remember this will wipe sd-ext, so best use a fresh sdcard with 2 ext partitions, both ext4 or both f2fs (not tried f2fs)
Click to expand...
Click to collapse
Bro can enable pie to take screenshot?
Sorry, it is vol dn and power, but both at exactly the same time. Just trying to find where they are stored now
Robbie P said:
Sorry, it is vol dn and power, but both at exactly the same time. Just trying to find where they are stored now
Click to expand...
Click to collapse
System/urs/keylayout/htcleo-keypad.kl and bro try hold volum up and power or volum up and home?
yes vol dn and power does take the screenshot, but I can't find where it is stored. Not on sdcard, nor the emulated sdcard (in pictures or in dcim)
Have attached a dmesg anyway.
booting , bootanimation is fine !
philipped346 said:
booting , bootanimation is fine !
Click to expand...
Click to collapse
Great