After a year of usage I've run ROM benchmark which resulted in 230MB read and 118MB write (sequential ofc). I also found (and lost) thread on MIUI site. There was a table that compared storage speeds. This results are almost perfect match for eMMC 5.1. also "cat /proc/scsi/scsi" command reported that I have "Toshiba thglf2g9j8lbatrh" memory chip. I could not find it on Toshiba site neither in eMMC section, nor in UFS.
I have a silver 3/64 version, probably one of the first ones, bought it on "11th of November" a year ago.
So go ahead check your devices. Please, let me know what results you will get.
I'm getting 433MB/s read, 131MB/s write (both sequential). Bought my phone in April 2017 and still running Nougat.
Josua. said:
I'm getting 433MB/s read, 131MB/s write (both sequential). Bought my phone in April 2017 and still running Nougat.
Click to expand...
Click to collapse
Can you please run the command from OP? It requires root though. You can execute it from PC using ADB: you would have to download it if you have not already, then add "ADB shell su " before the command from OP and execute it from command line. You can also do it from device itself: download some terminal app, add just "su " to the command and run it
Same here eMMC on my device, and I bought it in 06.2017... But I am not power user, so I don't care
WORMrus said:
Can you please run the command from OP? It requires root though. You can execute it from PC using ADB: you would have to download it if you have not already, then add "ADB shell su " before the command from OP and execute it from command line. You can also do it from device itself: download some terminal app, add just "su " to the command and run it
Click to expand...
Click to collapse
Sure! I got the same result: TOSHIBA Model: THGLF2G9J8LBATRH
My XiaoMi Mi5s 128gb version , purchased on 13.10.2016 use the KLUDG8J1CB-C0B1 UFS 2.0 memory. I think all 128gb variants use this memory according to this:
http://deviceinfohw.ru/devices/variants.php?model=MI 5s&set_brand=Xiaomi&set_vendor=Xiaomi.
I have the 128 GB version and used A1 SD Benchmark, result of internal memory is:
480 MB/s read and 127 MB/s write
Using the latest official Global ROM 9.2.1.0.
If your device doesn't have enough free space, the io performance will drop off a lot.
Well, it kinda seems like a false alarm. I've conducted more benchmarks and found out that results are heavily dependent on read-ahead value that you can set in Kernel Adiutor at i\o scheduler tab. If it is set to a minimum default value of 128 then you get results that are natural to eMMC 5.1, but as soon as I increased value to 512 and then 1024 I've got 358 and 160 r/w (for 1024) speeds. Values were used in this order 128->512->128->1024. I forgot to take screenshot of 512 and can't compare it to 1024, but it was close to it and really far away from 128. It might be a lucky coincidence, but this parameter is the only thing that was changed between measurements.
Increasing the read-ahead value will increase your RAM usage and keep the flash, in cases of random reads, longer busy and thus can cause lower performance.
I also have Toshiba UFS memory. Read and write are good.
Well, I'm having like 288 MB/s on read, and only 31 MB/s on write, with ~7 GB of free space.
Once you get below 10-15% of free space, the write rate will drastically decrease on every flash based storage type.
dariusz666 said:
I also have Toshiba UFS memory. Read and write are good.
Click to expand...
Click to collapse
Is this good bro?
henmadx said:
Is this good bro?
Click to expand...
Click to collapse
Yes, it is. I have similar results.
There is my test results: 3/64GB version, Toshiba, phone bought on 2017-08-14
Well, I found this in a Chinese forum.
Code:
imgsrc.baidu.com/forum/pic/item/cf5440380cd7912300b80158a7345982b3b78092.jpg
Related
Hello all,
I seem to have only 256MB RAM on my nexus one.
How I checked the RAM:
Command Prompt -> adb shell
-> cat /proc/meminfo
Gives me a total of 212.
Very strange.
Do a search.
I agree do a search.
Short answer is they held back some Ram on the stock Kernel.
Cyanogen put out a "high-mem" kernel which increased us up to abour 400, but it requires root to flash it.
My mistake, should have done a search first. But looking at 212MB RAM was rather shocking
@seanowns
Thank you.
Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
eljanor said:
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/showthread.php?t=767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Now I'll check your link, thanks.
EDIT: GREAT! IT WORK PERFECTLY! Now it's only find the way to run at boot a script for activating wifi, but I think it's easy, with or without a program.
Thanks a lot
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
x1l0n said:
How did you try to do it?
Anyway, there are a lot of ways to do it. Let's try first with adb (I'm writting this for a windows environment, because I'm too lazy to boot into linux, so sorry):
You plug in your tattoo through UsB on your PC. You start your command prompt and go to the folder where adb.exe is contained. The you write adb pull /etc/init.d/02squashsf c:\02squashsf <- this will save 02squashsf from your tattoo to your pc in the c:\ directory/partition. After that open the 02squashsf file with ... notepad/notepad++ and comment the line as described in my previous post. After you save the now modified 02squashsf file go to command prompt again and execute : adb push c:\02squashsf /etc/init.d/02squashsf <- this will copy 02squashsf from your c:\ to your tattoo. Pretty easy!
2nd Way:
Start RootExplorer on your tattoo and go to the folder /etc/init.d. Then click the small button in the upper right corner which says "Mount as R/W" (this will mount the system partition as Read/Write access). Find the 02squashsf file and long click it (until the menu pops up) and then choose edit as text file (or something similar). After it has been opened comment out the line as described in my previous post and save the file after the modification. That is all.
By the way, there is a 3rd way - unpacking the squash and editing its contents to be correct. But I don't really have the time...
And remember that a backup takes only a few minutes to make, but a mistake can cost you hours to fix if you have no backup
Click to expand...
Click to collapse
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
eljanor said:
You´re welcome! Actually, you don´t need to write a script - just open the "/etc/init.d/02squashsf" file as a text file and put a # in front of the line "busybox losetup /dev/block/loop0 /system/squashfs/modules.sqf" to comment it out.
Try the "2nd Way" from the following quote I took from the official spqrom thread (Page 70):
Takes 1 minute of your time, and you never ever have to think about it again, no matter how often you reboot. Not sure what the effect of outcommenting this line is though, but I didn´t run into any problems so far...
Click to expand...
Click to collapse
Eheheheheeh I'm using a safe "fourth way", that I thought.
A normal way (not that 3) is typing these commands on Terminal Emulator directly from the phone.
Well, so why don't insert them into "Preferences -> Initial command" and give to Terminal Emulator the superuser authorization (with flag "Remember")?
Now, every boot, I simply open Terminal Emulator with a link on the desktop, waiting few seconds and it work!
Sometimes the default power widget doesn't work, so I must enter in Settings -> WiFi and turn it on. But it work without typing nothing more or modify a system file
Baboo85 said:
I know, actually I'm using KiljackenROM 1.4 (only Android 2.1) and if I set to 768MHz the phone crashes and reboot. Without a voltage increment, I think 710MHz is the maximum stable (and it's ok as it is).
Click to expand...
Click to collapse
Talking about voltages, are they controllable in some accessible way? I'd give it a go any time if I could find any useful information on the subject. Any help?
Baboo85 said:
Hi all
I recently installed SetCPU on my Tattoo with SPQRom 0.6 (Android 2.2) and actually it working in underclock (19MHz).
It seems that perflock can be disabled.
But on overclock I can't surpass the default freq 528MHz, even setting that manually (setcpu.txt)
Wich overclock frequency can I use? My kernel version is 2.6.29-fy-bfs
Thanks.
Click to expand...
Click to collapse
Just a question of confirming something.
With the new SPQRom 0.7 room we still have to flash a new kernel like eljanor user advised?
[Q] SetCPU on Tattoo
I had the same problem too... You have to flash a special OC kernel first. Check the Spqrom thread pages 68 to 70 (http://forum.xda-developers.com/show...767049&page=68), there you will find a download link and a step by step description.
Basically you flash the kernel and then edit one line in a system file to get Wifi back. It´s really not that difficult, even I managed it. After that you can use SetCPU, I went to 710 MHz, that seems to be the stable maximum.
Click to expand...
Click to collapse
Or it's this new room already is ready to be Over-clocked?
Thanks in advance
So, how far have you guys have went? I've read that for some of you, 710 MHz is the stable max, but for me, my tattoo seems to crash occasionally on that clock speed. My stable max is one step lower, 691 MHz.
bladez said:
My stable max is one step lower, 691 MHz.
Click to expand...
Click to collapse
I agree. Most stable and powerful is 691MHz. I have tested tatto by System Benchmark from market and its shows max results on 619MHz, next 710MHz are got worst resulsts in Cpu and Graphics tests. 691MHz optimal.
I also experimented with System Benchmark, and I got the best results on 730, though it did reboot occasionally.
my is 680
Use with 2.0.54 only, root is not yet available with 2.0.71
disclaimer: swap IS evil, you don't want it! Swap is a dirty workaround for crappy hardware (well somekind of) ... Don't complain if you put a swapfile on your internal memory (the 8 or 16GB flash disk) and it will stop working. Swap read and write like hell, so if you want to try it, please use an external disk, like usb, or better: micro SD. And of course i'm not responsible for anything ...
a) download http://hitme.resetbutton.de/priv/swapfiles.zip
b) unzip it somewhere on your PC
c) pick what you want ... i prepared a 128, 256 and 512MB swapfile in it. It might be smart to start with 256MB
d1) connect to your PC and use the dropdown area (on the Archos notification bar) to enable file transfers
d2) on my system the sd card is mounted on windows as "removable disk" .. the internal is A101IT, so if you have a sd card use "removable disk"
d3) transfer the file (the size you want, or all) to your Archos device, as i said: internal memory might be a bad idea, use a sd card
d4) on a windows system use the "safe remove hardware" or whatever it's called and unmount the disk form the archos. After that, on the archos at the orange Android screen: click the button
e) use z4root to root your device temporarily ( you can find it here: http://forum.xda-developers.com/showthread.php?t=833953 or google for z4root)
f) use the first option in z4root! a permanent root will not work (at the moment). If it's not working: enable USB debugging AND connect it to a PC
g) download a terminal if you haven't so far. Search in the market for "terminal emulator"
h) start the terminal and enter: su
at the first time you will get a request that you really want it. If you don't get it: root didn't work, happens sometimes. Power off your device and try again at e)
i) locate where you put your swapfile ... it should be /mnt/storage/sdcard, or if you don't have a sd card: /mnt/storage
j) go into the directory by typing: cd /mnt/storage/sdcard ... or cd /mnt/storage (without a sdcard)
you can list the content of the directory with: ls
k) type: swapon swap256
or the file you copied (swap128, swap256, swap512)
l) type: free
you should now see that you have swap memory
m) report back which file works best for you!
This will now work until you reboot your device. If you do: start again at e) .. of course you don't have to download z4root or the terminal again, so it's:
root with z4root
start terminal and enter su
goto the directory where the swapfile is (cd something)
swapon swap256 ( or whatever you used)
control with: free
done
WARNING: if you use a swapfile, which is described here, you can't use a usb connection to copy files without doing this:
start the terminal, enter: su
go to the directory where the file is ( cd /mnt/storage/sdcard or /mnt/storage) and do:
swapoff swap256 (or whatever you used)
This mini howto is for a swapFILE ... the advantage is that you don't have to make new partitions on your sdcard, but it might be a little bit slower than a swapPARTITION. If i have more time i will wikify this and extend it with the partition part ...
Credits go to http://forum.archosfans.com/viewtopic.php?f=74&t=42718
Is there any way to make that into a script that can be run during boot?
Also - you can download terminal emulator from Archos Aps and no root required.
impossible without perm root (we cannot modify root fs, so no chance for boot scripts...)
wait for SDE and custom roms
You can only use this while temp rooted (to use the command swapon), also, there should be NO reason why you should be rebooting anyway...
I tried this successfully in my Archos 101 but using the Internal Storage, not the SD card itself. I ran it for 3 hours straight opening very heavy stuff. It solves the stability issue, now my 101 doesn't hang when I open too much stuff.
My only concern is that the swap file operation may shorten the lifespan of the media because such media usually has a finite number or write operation cycles to it.
Just enabled a swap512 on a spare sdcard i had. Initial impressions is... WOW this thing flies! Apps are just popping open now with no lag and flicking screen to screen is almost instant. Will report back on the stability after I've had a chance to play with it but THANK YOU OP!!
Use a fairly good MicroSD card with it, high read/write cycles on it. It will last longer then.
Wow this worked great. My system is flying.
A put the 512 on an 8gb sd card.
I opened dolphin with 8 tabs, angry birds seasons paused after playing no problem. Then opened regular angry birds and played that with all others still running. No issue.
I also have music playing in the background.
I opened the my piano ap and played that with all others in the background.
Works just perfectly.
Here are my memory stats under free
used: 242148 free 2604
swap
used: 143652 free 380628
I'm going to try this too... once I got the archos rooted again... z4root isn't very reliable to be honest. Currently it's not working 90% of the time. But that's another issue in another thread.
Working fine too... I'm using launcher pro, started some apps, played angry birds seasons and yet no freeze.
Firefox beta was unusable without swap, now working like a charme. I'm checkin on Dolphin HD next.
Works great, put a 512swap on my 8 gb micro sd and no freezes anymore
Really Fix Freeze problem, it look smooth now...
Why ?
7895123 said:
Why ?
Click to expand...
Click to collapse
because it doesn't run out of memory.
Memory management isn't too good with our stock froyo because it doesn't end applications when it should.
Sent from my HTC Legend using XDA App
Thank you very much. I will try on my Archos 101IT
This will not work with the newest firmware as temp root no longer works. However, the improved CPU and memory management should compensate for that.
true. z4root closes unexpectedly (=crashes).
so far no freezes with new firmware
chulri said:
true. z4root closes unexpectedly (=crashes).
so far no freezes with new firmware
Click to expand...
Click to collapse
Not true. I'm on the latest firmware, running Z4Root temp rooted, and swapping 512. Not sure why it'd not working for you guys.
EDIT: I didn't see the latest posted in the forum. I'm still on 2.0.54, not the newest
I have already tried on microSD and found it work fine.
#free
total used free shared buffers
Mem: 244048 240692 3356 0 5260
Swap: 262136 0 262136
Total: 506184 240692 265492
Archos 101 - 16 GB + microSD 8 GB setCPU max: 1000 min 800
Did you upgrade from 2.0.54 or did you do a wipe/reflash?
aamon17 said:
Not true. I'm on the latest firmware, running Z4Root temp rooted, and swapping 512. Not sure why it'd not working for you guys.
Click to expand...
Click to collapse
Found something interesting over in the main Android Dev forum, did a search here and didn't find anything so I thought I'd share it.
Brainmaster has discovered a way to make our phones able to read SD Cards faster, check it out. There are a couple different settings you can use, I personally find the 3072kb to work best for me. It boosted my read speed from about 11.1MB/s to about 17.9MB/s and my write speed from 4.3MB/s to about 8.8MB/s.
I downloaded the CWM version of the fix (2048 KB) And it didnt work.. I heard somewhere the CWM versions don't work for SGS
So how did you apply the fix??? Im on Serendipity 6.3
noside12123 said:
I downloaded the CWM version of the fix (2048 KB) And it didnt work.. I heard somewhere the CWM versions don't work for SGS
So how did you apply the fix??? Im on Serendipity 6.3
Click to expand...
Click to collapse
I used the same file yesterday. You need to rename the file to "S77sdcardspeedfix" in system>etc>init.d
Reboot for the changes to take affect.
Put this in a terminal emulator. It will only do it til a reboot though, so it's just for testing.
#!/system/bin/sh
echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
Sent from my CM7 powered captivate
tietherope said:
I used the same file yesterday. You need to rename the file to "S77sdcardspeedfix" in system>etc>init.d
Reboot for the changes to take EFFECT (Not AFFECT) .
Click to expand...
Click to collapse
Thanks man!!!! will test my speeds in a few minutes
EDIT: It works but no noticable speed increase
tietherope said:
I used the same file yesterday. You need to rename the file to "S77sdcardspeedfix" in system>etc>init.d
Reboot for the changes to take affect.
Click to expand...
Click to collapse
yeah! this finally fixed the reboot issue!
Is this safe to flash with CyanogenMod 7?
So I have tried this to no success. SD Tools seems to just test our internal SD cards. At stock which I am getting ~7-8 MB/s write and ~15-17 MB/s read. When I try CWM flashing the 1024, 2048, 3072, adn 4096 zip files and renaming the 77whatchamacallit to S77whatchamacallit, I get even worse performance in SD Tools testing, down to like 5 MB/s write!
I get more success with the echo of the read_ahead_kb posted above but like it was said, the settings only last till reboot. Any permanent fix? I also found the 4096 to work best on our internal SD cards with the ADB method.
Make a script named something like ... S_sdcard_fix.sh ...with nothing but this in it...
#!/system/bin/sh
echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
Then place it in /etc/init.d/ ...and it will stick through reboot ...
..also it will be in my next Onix release by default (2048)
EDIT
Heres the script for those that need it...you can change the "2048" to which ever size you want
http://berryfx.com/RobBeane/Kernel/Files/S_sdcard_fix.sh
Awesome ! Thanks existz
Sent from my GT-I9000 [Continuum v4 ] using XDA Premium App
I have applied the 2048 zip after changing that 77sd... to S77sd... and I'm no longer getting reboots but FCs from gallery, or suddenly it lags for like 5 seconds without responding.
Im using the HTC HD2 with cyanogen 7
SD Tools - Info and Benchmark tools.
With SD Tools you can check your microSD card information (Name, Date, MID, OEMID,...). You can check if your card is fake. (Check serial number and MID and OEMID).
You can also benchmark sd card writing and reading speeds.
You can also submit results and information to internet. In future there will be results. (As soon I got enough results).
Please write to me sreenshot if there are some problems.
Does not shows Card Info On Galaxy S, but you can check speed of external sd Card.
Please write to me, if you got suggestions, or problem report. I can not reply you to comment. And I can't fix problems if I got no feedback. If SD Tools can not test external card, please let me know. (I know for Samsung Galaxy S)
Known bugs: Read speeds are sometimes incorrect (High values). This happened after reset.
Click to expand...
Click to collapse
That's the app description... details the limitations with our phones.
EDIT on my captivate I got 6.4 / 10.7 (didn't apply the fix)
using serendipity 6.3 Onix 2.0.3
I've tried the script way, and the S77 way, and neither sticks through reboot
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
The SD Tools benchmark doesn't show much improvement on the first run, the second run will return much better results. Make sure to run it at least twice before you assume it did not stick.
I have come to the conclusion that SDTools is not a good app to benchmark with. Read through the entire thread that this script came from and there was a little discussion in exists onix thread around page 357 or so. The "S" in front of the 77 fixed it for me.
Sent from my OC'd Samsung Captivate
Xp3r7 said:
Is this safe to flash with CyanogenMod 7?
Click to expand...
Click to collapse
Yes i just flashed it, best results for me are with the 2048 and 3072 sizes.
So one of the things that keeps some of us from overclocking to 1.4 Ghz + is the external SD card speed... anybody have better stability overclocking with this fix??
Edit: ahh, just realized this is for internel SD card, nm
Sent from my SGH-I897 using XDA Premium App
According to this post along with @LastStandingDroid & @HackerOO7, the Nougat Honor 8 kernel doesn't support loop mounts. Evidently the Marshmallow kernel does, as I'm using Magisk* with no issue.
On a stock unrooted Nougat FRD-L04, the command 'cat /proc/devices" returns (less relevant data snipped):
Code:
127|HWFRD:/ $ cat /proc/devices
Block devices:
1 ramdisk
259 blkext
[B] [U]7 loop[/U][/B]
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 device-mapper
254 zram
It would appear that the FRD Nougat is still somewhat loop aware, in that there are references that still exist, but just evidently not the kernel driver. In light of the fact that there is no Nougat kernel source, and even if there was it would be a Huawei mess, it's unlikely we're ever going to be able to build in loop support from scratch on a stock-base ROM.
In light of that, has anyone attempted building a loadable kernel module for the N kernel (4.1.18 I believe) and installing it via 'insmod'? What are some angles we can try and take to get loop support, and thus Magisk support, back into N.
* (If you're unfamiliar with what Magisk is and does, it allows you to, among other things, get root and modify the system without modifying the system, thus allowing you to continue to use applications (Pokemon Go, Android Pay, banking applications) that otherwise would not allow you to use them with root or a modified system))
Telperion said:
According to this post along with @LastStandingDroid & @HackerOO7, the Nougat Honor 8 kernel doesn't support loop mounts. Evidently the Marshmallow kernel does, as I'm using Magisk* with no issue.
On a stock unrooted Nougat FRD-L04, the command 'cat /proc/devices" returns (less relevant data snipped):
Code:
127|HWFRD:/ $ cat /proc/devices
Block devices:
1 ramdisk
259 blkext
[B] [U]7 loop[/U][/B]
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 device-mapper
254 zram
It would appear that the FRD Nougat is still somewhat loop aware, in that there are references that still exist, but just evidently not the kernel driver. In light of the fact that there is no Nougat kernel source, and even if there was it would be a Huawei mess, it's unlikely we're ever going to be able to build in loop support from scratch on a stock-base ROM.
In light of that, has anyone attempted building a loadable kernel module for the N kernel (4.1.18 I believe) and installing it via 'insmod'? What are some angles we can try and take to get loop support, and thus Magisk support, back into N.
* (If you're unfamiliar with what Magisk is and does, it allows you to, among other things, get root and modify the system without modifying the system, thus allowing you to continue to use applications (Pokemon Go, Android Pay, banking applications) that otherwise would not allow you to use them with root or a modified system))
Click to expand...
Click to collapse
You're right that stock nougat (b360 anyway) doesn't have kernel support for "mount -o loop" or loop device for some reason. Until at least now, I've not seen any Huawei stock kernel source for that kernel. If we had it, then it'd not be a big issue. I noticed this development today: https://github.com/OpenKirin/android_kernel_huawei_frd/tree/7.x
From @surdu_petru , who today uploaded a real version of TWRP for Nougat Honor 8, more specifically from his github where there appears to be a 7.x.x Honor 8 kernel at the link above. I'm guessing that if you pull that source, and the "android-recommended.cfg" .config file, you'll see that CONFIG_BLK_DEV_LOOP=y. So if that's buildable source, then it looks ready to go for your uses.
It's too bad that /proc/config.gz (current honor 8 kernel config) isn't kept in /proc like nearly all other androids, but it's not. Without that, it's hard to rebuild the exact configuration and only add the loop device. (or build the module).
Anyway: I was kind of excited to notice what surdu_petru had done and you can possibly figure out how to do your loop module addition if he used that kernel code at the first pointer above. -- cheers.
That's an encouraging development, I'll check it out. As much as I prefer the Nougat interface, especially the recents, notifications, and quick settings, I prefer Magisk to those things so I'll hang out on MM for now.
Looks like still no kernel source for Nougat so not much we can do on that angle yet.
One possibility may be to fork Magisk's source and modify it to use a ramdisk instead of a loop device. It's pretty far out of my expertise though.
@wraithewok
I see that Source code for Mate 9 is released on this page http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
I know that it is based on Kirin 960. Can't we use it as a base for our Honor 8?
Telperion said:
Looks like still no kernel source for Nougat so not much we can do on that angle yet.
One possibility may be to fork Magisk's source and modify it to use a ramdisk instead of a loop device. It's pretty far out of my expertise though.
@wraithewok
Click to expand...
Click to collapse
Almost everytime I deal with ramdisks, they're implemented via loop devices. I'll have to read around and see if people do ramdisks another way.
---------- Post added at 07:00 AM ---------- Previous post was at 06:32 AM ----------
morpheus302 said:
I see that Source code for Mate 9 is released on this page http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
I know that it is based on Kirin 960. Can't we use it as a base for our Honor 8?
Click to expand...
Click to collapse
From what I've read about 960 (cortex-a73) vx. 950 (a720), there are architectural differences to prevent throttling, etc. It's not just a case of binning (where the "faster" chips are binned as 960's, rather than 950's). I'd like to see a "hammer Honor" campaign nagging them to release their Honor 8 Nougat source like for mate 9. I've put a post on their forum, but they have a record of nearly zero response to anyone that isn't just praising them.
*my post on Honor forum* https://club-us.hihonor.com/honor8.32/where-can-we-get-kernel-source-for-honor-8-nougat.1835
From my googling, it appears to be possible, but you're right that it's not common. Most of what I've found is from old Linux tutorials, not Android specific. It should be doable though.
hachamacha said:
Almost everytime I deal with ramdisks, they're implemented via loop devices. I'll have to read around and see if people do ramdisks another way.
Click to expand...
Click to collapse
hachamacha said:
Almost everytime I deal with ramdisks, they're implemented via loop devices. I'll have to read around and see if people do ramdisks another way.
Click to expand...
Click to collapse
Here's one article I ran across:
http://surfer.nmr.mgh.harvard.edu/partition/ramdisk.html said:
Create a ramdisk device if one does not already exist in /dev:
/home/tony# mknod -m 660 /dev/ram b 1 1
/home/tony# chown root.disk /dev/ram
Zero out the space you need on the ramdisk device:
/home/tony# dd if=/dev/zero of=/dev/ram bs=1k count=4k
4096+0 records in
4096+0 records out
Make a file system on the ram disk, specifying the size:
/home/tony# /sbin/mkfs -t ext2 -m 0 /dev/ram 4096
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
1024 inodes, 4096 blocks
204 blocks (4.98%) reserved for the super user
First data block=1
1 block group
8192 blocks per group, 8192 fragments per group
1024 inodes per group
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Mount the ram disk as you would a regular device:
/home/tony# mount -t ext2 /dev/ram /mnt/disk
Click to expand...
Click to collapse
Telperion said:
Here's one article I ran across:
Click to expand...
Click to collapse
I'm not 100% but this looks like a way to create a ramdisk once you're already logged on or sudo'd to root user. I don't think you'll have access to the full realm of busybox type commands, /sbin,/usr/sbin cmds, without being root. Is that a showstopper since the idea here is to use the ramdisk to get root?
Another thing I don't quite get is what keeps the zeroed out ram from being overwritten by any actions on the phone since no one is bothering to do an malloc(*).?
However: If you could achieve some temporary root, then it looks fine (but catch 22 , blah blah)::
Oh! I guess I wasn't quite thinking of this right.. If you have the latest TWRP installed, and you can boot into it, and use adb shell to reach it, then it must have /xbin/su built in so that it can do anything at all. I guess you can execute everything from TWRP. Then the only question is can you mount the ext2 ramdisk without problem and actually get magisk (sp?) to use it.
Anyway, it does look worth a shot. Thanks for the link.
hachamacha said:
Anyway, it does look worth a shot. Thanks for the link.
Click to expand...
Click to collapse
As far as I understand the way Magisk works, it's essentially loop mounting a symlinked fileystem over top of /system/ and the actual files are located in an .IMG elsewhere. So in light of that, shouldn't it be possible to just change the method of mounting while keeping the functionality the same? Instead of using a loop block device, we'd be using a ram block device.
This is beyond my expertise, but I was able to mount a ramdisk as a block device on Ubuntu so conceptually I think it should be possible.
Have there been any updates?
Latest beta of Magisk works great.
morpheus302 said:
Latest beta of Magisk works great.
Click to expand...
Click to collapse
Are you on stock ROM?!
yes, b389
jonny190 said:
Have there been any updates?
Click to expand...
Click to collapse
It's been working since B381 I believe it was. So yeah. Before that loop was broken or just disabled
Sent from my FRD-L09 using Tapatalk
morpheus302 said:
yes, b389
Click to expand...
Click to collapse
Thanks
LastStandingDroid said:
It's been working since B381 I believe it was. So yeah. Before that loop was broken or just disabled
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
HI there, I was wondering if xposed works on B381 and onwards? Thanks!
Neeosx said:
HI there, I was wondering if xposed works on B381 and onwards? Thanks!
Click to expand...
Click to collapse
Yes it works I've tried it on b381 so I can confirm it works
Sent from my NATASHA using Tapatalk
So magisk is working and you can use magisk hide to use android pay? If its fully working then i'll consider unlocking bootloader again.
colliflower1107 said:
So magisk is working and you can use magisk hide to use android pay? If its fully working then i'll consider unlocking bootloader again.
Click to expand...
Click to collapse
Yes it is working use the universal safety net module in magisk.