Related
Hello,
I have request for owners od Hermes.
Would someone write values from registry on path
"HKEY_LOCAL_MACHINE/SOFTWARE/HTC/Camera/P2" ?
This would be here:
"(Default)
CaptureFormat
CaptureType
Enable
EnableRecLimit
EncodeFormat
MainCamCaptSize
MainCamSupportCaptSize
Property
RecLimitedSize
RecLimitSize
SaveFolder"
and I am interesting about values of this keys.
I try set up video recording to higher resolution than 176x144 in HTC Artemis and this values from Hermes would be helpful for me.
Thanks for replies.
I get (decimal) :
CaptureFormat 16
CaptureType 1
Enable 1
EnableRecLimit 0
EncodeFormat 24
MainCamCaptSize 16
MainCamSupportCaptSize 58
Property 570
RecLimitedType 0
RecLimitSize 256000
SaveFolder My Videos
Good luck with your attempt
Cheers
Yannick
Thank you very much buddy
I'm just wondering. Is it a way to get the Dual to "work" faster, any apps, tweaks etc. I'ts fast enough but if it can get faster, it is'ent a problem
I'm from Norway, sorry about my English
Remeber to close the app's after using them are a smart one
But i dont know any other way....(yet)
Norwegian:
Hvis du skrur av programmene etter bruk så går det litt fortere
Serlig hvis du har mange oppe
I know that, but is there like any tweaking programs or something that speeds up the dual?
Nordmenn innpå her også Flotte greier
overclock?
no overclock in the moment ...
Speed Tweaks
The following 3 Registry tweaks increase system performance and makes the Dual more responsive:
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE\
Changed limit from 16384 to 32768
Navigate to: HKEY_LOCAL_MACHINE\System\StorageManager\FATFS
Changed - CacheSize to 4096
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\StorageManager\Filters\f sreplxfilt
Change “ReplStoreCacheSize” dword decimal value to 4096 or 8192 (I find 8192 best but you may find 4096 works better for you)
can anyone verify that these reg tweaks will speed up the responsiveness of our duals?
Work
The three Regisrty entries works with my Ita Dual, it seems to be more responsive and faster thanks gfreek
yes this key works ... i know some other deep in the FAT config ... must search for old docu ... if i found it ... i will post some other keys they work too!
gfreek said:
The following 3 Registry tweaks increase system performance and makes the Dual more responsive:
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE\
Changed limit from 16384 to 32768
Navigate to: HKEY_LOCAL_MACHINE\System\StorageManager\FATFS
Changed - CacheSize to 4096
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\StorageManager\Filters\f sreplxfilt
Change “ReplStoreCacheSize” dword decimal value to 4096 or 8192 (I find 8192 best but you may find 4096 works better for you)
Click to expand...
Click to collapse
My Glyphcache is only 8192 not 16384. What should I change it to?
gfreek said:
The following 3 Registry tweaks increase system performance and makes the Dual more responsive:
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE\
Changed limit from 16384 to 32768
Navigate to: HKEY_LOCAL_MACHINE\System\StorageManager\FATFS
Changed - CacheSize to 4096
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\StorageManager\Filters\f sreplxfilt
Change “ReplStoreCacheSize” dword decimal value to 4096 or 8192 (I find 8192 best but you may find 4096 works better for you)
Click to expand...
Click to collapse
hmm these settings don't seem to change much.
BUT the touchflo picture viewer is much slower now - when changing between pictures its not as smooth as before !
These settings are default on my german HTC Touch Dual.
Undying
How to overclock the niki?
Dump Question ... you cant overclock it!!! No one knows the right CPU Commands ...
Dump Question
Click to expand...
Click to collapse
Thank you for the very kind answer
you have right ... soory ^_^°
gfreek said:
The following 3 Registry tweaks increase system performance and makes the Dual more responsive:
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE\
Changed limit from 16384 to 32768
Navigate to: HKEY_LOCAL_MACHINE\System\StorageManager\FATFS
Changed - CacheSize to 4096
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\StorageManager\Filters\f sreplxfilt
Change “ReplStoreCacheSize” dword decimal value to 4096 or 8192 (I find 8192 best but you may find 4096 works better for you)
Click to expand...
Click to collapse
my limits are zero. do i still have to change it?
spanish dual rom
I have an old laptop with Wacom touch panel (Penabled). I am able to boot Remix OS fine but touch isn't working.
How to make touchscreen work?
Edit: Fixed by myself
View post #6 link: http://forum.xda-developers.com/showpost.php?p=65159778&postcount=6
The hardware must be unsupported.
TheBasterd said:
The hardware must be unsupported.
Click to expand...
Click to collapse
Nevermind, I fixed it myself
Care to share with the rest of us in case this issue comes up more often?
I would also be happy to know how to make a Wacom digitizer work on Remix OS as I'm looking into getting a Lenovo X61t to use with Remix OS.
YassinTP said:
I would also be happy to know how to make a Wacom digitizer work on Remix OS as I'm looking into getting a Lenovo X61t to use with Remix OS.
Click to expand...
Click to collapse
My laptop (Fujitsu T730) has Wacom digitizer with both touch input and pen. Using my method only touchscreen works (pen doesn't but I don't care )
You need to create live usb pendrive from official Android-X86 4.4 r4, run it live (without install) and copy from it inputattach file inside system/bin folder to Remix OS system/bin folder (you need rooted Remix OS for this) and set correct permissions.
Download from Play Store Terminal Emulator for Android and run:
su
inputattach --w8001 /dev/ttyS0 &
And touchscreen works
I have no idea why this file is missing in Remix OS while it is present in Android-X86 (Remix is based on Android-X86 after all)
It would be great if Remix developers could include it in next releases because as it is now you have to copy it every time you upgrade os.
Thank you very much!
Only thing is, the convertible I'm planning on buying only has a pen guess I'll just have to try if I get it working.
This is no working on my HP 2760p.
jarek3460 said:
This is no working on my HP 2760p.
Click to expand...
Click to collapse
I also tested it on HP 2760p. And it was working fine. I no longer use Remix OS so I can't confirm if this works on recent rom versions.
Remember that after copying file you have to set correct file permissions using any root capable file browser. (Try setting it to: rwxrwxrwx to be sure it works )
jarek3460 said:
This is no working on my HP 2760p.
Click to expand...
Click to collapse
were you able to ever get this working? I have a 2740p as well with only pen support
Rafostar said:
My laptop (Fujitsu T730) has Wacom digitizer with both touch input and pen. Using my method only touchscreen works (pen doesn't but I don't care )
You need to create live usb pendrive from official Android-X86 4.4 r4, run it live (without install) and copy from it inputattach file inside system/bin folder to Remix OS system/bin folder (you need rooted Remix OS for this) and set correct permissions.
Download from Play Store Terminal Emulator for Android and run:
su
inputattach --w8001 /dev/ttyS0 &
And touchscreen works
I have no idea why this file is missing in Remix OS while it is present in Android-X86 (Remix is based on Android-X86 after all)
It would be great if Remix developers could include it in next releases because as it is now you have to copy it every time you upgrade os.
Click to expand...
Click to collapse
I tried X86 Marshmellow and the Nought Beta versions, but touch is not working on them.
It is still working on Ubuntu Live and Debian. I ran lsusb and lsmod on them and got this result.
Code:
[email protected]:/home/ubuntu# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 0bda:5830 Realtek Semiconductor Corp.
Bus 001 Device 007: ID 0bda:b720 Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 0bda:5830 Realtek Semiconductor Corp.
Bus 001 Device 008: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
Bus 001 Device 006: ID 04d9:e200 Holtek Semiconductor, Inc.
Bus 001 Device 004: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code:
[email protected]:/home/ubuntu# lsmod
Module Size Used by
rfcomm 69632 2
bnep 20480 2
joydev 20480 0
rtsx_usb_ms 20480 0
memstick 20480 1 rtsx_usb_ms
intel_rapl 20480 0
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
coretemp 16384 0
hid_multitouch 20480 0
kvm_intel 172032 0
kvm 536576 1 kvm_intel
irqbypass 16384 1 kvm
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
aesni_intel 167936 0
aes_x86_64 20480 1 aesni_intel
lrw 16384 1 aesni_intel
gf128mul 16384 1 lrw
btusb 45056 0
uvcvideo 90112 0
videobuf2_vmalloc 16384 1 uvcvideo
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 28672 1 uvcvideo
glue_helper 16384 1 aesni_intel
btrtl 16384 1 btusb
ablk_helper 16384 1 aesni_intel
btbcm 16384 1 btusb
btintel 16384 1 btusb
cryptd 20480 2 aesni_intel,ablk_helper
bluetooth 520192 29 bnep,btbcm,btrtl,btusb,rfcomm,btintel
videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2
v4l2_common 16384 1 videobuf2_v4l2
serio_raw 16384 0
videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
input_leds 16384 0
media 24576 2 uvcvideo,videodev
intel_pch_thermal 16384 0
snd_hda_codec_realtek 86016 1
snd_hda_codec_hdmi 53248 1
snd_hda_codec_generic 77824 1 snd_hda_codec_realtek
snd_soc_rt5640 114688 0
snd_hda_intel 36864 5
snd_soc_ssm4567 16384 0
snd_soc_rl6231 16384 1 snd_soc_rt5640
snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
snd_soc_core 212992 2 snd_soc_rt5640,snd_soc_ssm4567
snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep 16384 1 snd_hda_codec
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_compress 20480 1 snd_soc_core
ac97_bus 16384 1 snd_soc_core
snd_rawmidi 32768 1 snd_seq_midi
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
snd_pcm 106496 7 snd_soc_rt5640,snd_soc_core,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_pcm_dmaengine,snd_hda_core
int3403_thermal 16384 0
mei_me 36864 0
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
mei 98304 1 mei_me
kxcjk_1013 20480 0
elan_i2c 36864 0
snd_timer 32768 2 snd_pcm,snd_seq
industrialio_triggered_buffer 16384 1 kxcjk_1013
dw_dmac 16384 0
lpc_ich 24576 0
8250_dw 16384 0
snd 81920 23 snd_hda_codec_realtek,snd_soc_core,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_compress
dw_dmac_core 24576 1 dw_dmac
int3400_thermal 16384 0
int3402_thermal 16384 0
processor_thermal_device 16384 0
acpi_als 16384 0
intel_soc_dts_iosf 16384 1 processor_thermal_device
acpi_thermal_rel 16384 1 int3400_thermal
int340x_thermal_zone 16384 3 int3402_thermal,processor_thermal_device,int3403_thermal
kfifo_buf 16384 2 industrialio_triggered_buffer,acpi_als
snd_soc_sst_acpi 16384 0
soundcore 16384 1 snd
i2c_designware_platform 16384 0
i2c_designware_core 20480 1 i2c_designware_platform
spi_pxa2xx_platform 24576 0
industrialio 57344 4 industrialio_triggered_buffer,acpi_als,kxcjk_1013,kfifo_buf
mac_hid 16384 0
acpi_pad 20480 0
parport_pc 32768 0
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,ppdev,parport_pc
autofs4 40960 2
overlay 49152 1
nls_iso8859_1 16384 3
dm_mirror 24576 0
dm_region_hash 24576 1 dm_mirror
dm_log 20480 2 dm_region_hash,dm_mirror
mmc_block 36864 2
hid_generic 16384 0
usbhid 49152 0
rtsx_usb_sdmmc 28672 0
rtsx_usb 24576 2 rtsx_usb_sdmmc,rtsx_usb_ms
uas 24576 0
usb_storage 69632 4 uas
i915 1208320 5
i2c_algo_bit 16384 1 i915
drm_kms_helper 147456 1 i915
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
ahci 36864 0
sysimgblt 16384 1 drm_kms_helper
libahci 32768 1 ahci
fb_sys_fops 16384 1 drm_kms_helper
drm 360448 6 i915,drm_kms_helper
video 40960 1 i915
i2c_hid 20480 0
hid 118784 4 i2c_hid,hid_multitouch,hid_generic,usbhid
sdhci_acpi 16384 0
sdhci 45056 1 sdhci_acpi
fjes 28672 0
Rafostar said:
I also tested it on HP 2760p. And it was working fine. I no longer use Remix OS so I can't confirm if this works on recent rom versions.
Remember that after copying file you have to set correct file permissions using any root capable file browser. (Try setting it to: rwxrwxrwx to be sure it works )
Click to expand...
Click to collapse
Thank you so much Rafostar this helped getting my touch screen working on my hp 2740p
although it worked after the command was inputted. it failed to work after reboot
to fix this I needed to edit system/etc/init.sh
edit init.sh function init_misc
add command to line 18
inputattach --w8001 /dev/ttyS0 &
Redesterdragon said:
Thank you so much Rafostar this helped getting my touch screen working on my hp 2740p
although it worked after the command was inputted. it failed to work after reboot
to fix this I needed to edit system/etc/init.sh
edit init.sh function init_misc
add command to line 18
inputattach --w8001 /dev/ttyS0 &
Click to expand...
Click to collapse
I forgot to mention that you have to do this every time after reboot or create/add it to a startup script like you did
Rafostar said:
I forgot to mention that you have to do this every time after reboot or create/add it to a startup script like you did
Click to expand...
Click to collapse
I noticed that after falling asleep the touchscreen stops working again till reboot or manually entering the command within the command line
Rafostar said:
I forgot to mention that you have to do this every time after reboot or create/add it to a startup script like you did
Click to expand...
Click to collapse
what would I do to activate inputattach during wake?
Redesterdragon said:
what would I do to activate inputattach during wake?
Click to expand...
Click to collapse
I found one method of disabling sleep using a wake_lock command by placing it within the init.sh file under the function_misc section line 19
echo lock_me > /sys/power/wake_lock
this will dim the screen but not turn off the CPU so the digitizer will remain active now.
Please let me know if this might cause any other unfavorable issues.
This is my partition table as generated by gdisk
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 32 entries
First usable sector is 34, last usable sector is 15269854
Partitions will be aligned on 2-sector boundaries
Total free space is 313196 sectors (152.9 MiB)
Code:
# Name Start (sector) End (sector) Size Size (Sectors) Partition GUID Code
1 modem 131072 262143 64 MB 131072 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
2 sbl1 262144 263167 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
3 sbl1bak 263168 264191 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
4 aboot 264192 266239 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
5 abootbak 266240 268287 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
6 rpm 268288 269311 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
7 rpmbak 269312 270335 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
8 tz 270336 271871 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
9 tzbak 271872 273407 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
10 pad 273408 275455 1024KiB 2048 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
11 modemst1 275456 278527 1.5MiB 3072 EBBEADAF-22C9-E33B-8F5D-0E81686A68CB
12 modemst2 278528 281599 1.5MiB 3072 0A288B1F-22C9-E33B-8F5D-0E81686A68CB
13 misc 281600 283647 1024KiB 2048 82ACC91F-357C-4A68-9C8F-689E1B1A23A1
14 fsc 283648 283649 1024Bytes 2 57B90A16-22C9-E33B-8F5D-0E81686A68CB
15 ssd 283650 283665 8KiB 16 2C86E742-745E-4FDD-BFD8-B6A7AC638772
16 splash 283666 304145 10MiB 20480 20117F86-E985-4357-B9EE-374BC1D8487D
17 DDR 393216 393279 32KiB 64 20A0C19C-286A-42FA-9CE7-F64C3226A794
18 fsg 393280 396351 1.5MiB 3072 638FF8E2-22C9-E33B-8F5D-0E81686A68CB
19 sec 396352 396383 16KiB 32 303E6AC3-AF15-4C54-9E9B-D9A8FBECF401
20 boot 396384 461919 32MiB 65536 20117F86-E985-4357-B9EE-374BC1D8487D
21 system 461920 4557919 2GB 4096000 97D7B011-54DA-4835-B3C4-917AD6E73D74
22 persist 4557920 4623455 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
23 apedata 4623456 4688991 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
24 cache 4688992 5213279 256MiB 524288 5594C694-C871-4B5F-90B1-690A6F68E0F7
25 recovery 5213280 5278815 32MiB 65536 9D72D4E4-9958-42DA-AC26-BEA7A90B0434
26 devinfo 5278816 5280863 1024KiB 2048 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
27 keystore 5373952 5374975 512KiB 1024 DE7D4029-0F5B-41C8-AE7E-F6C023A02B33
28 oem 5374976 5506047 64MiB 131072 7DB6AC55-ECB5-4E02-80DA-4D335B973332
29 config 5506048 5507071 512KiB 1024 91B72D4D-71E0-4CBF-9B8E-236381CFF17A
30 userdata 5507072 15269854 4.7GiB 9762783 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
My version of the tool is this
Code:
!/usr/bin/python
#===========================================================================
# This script parses "partition.xml" and creates numerous output files
# specifically, partition.bin, rawprogram.xml
# REFERENCES
# $Header: //source/qcom/qct/core/pkg/bootloaders/rel/1.2/boot_images/core/storage/tools/jsdcc/partition_load_pt/PartitioningTool.py#2 $
# $DateTime: 2012/01/12 16:00:13 $
# $Author: coresvc $
# when who what, where, why
# -------- --- -------------------------------------------------------
# 2011-03-22 ah rawprogram for GPT for 'grow' partition, since mjsdload.cmm couldn't handle big number
# 2011-03-22 ah Corrected final disk size patch (off by 1 sector), corrected GPT labels (uni-code)
# 2011-03-18 ah Fixed default bug for DISK_SIGNATURE, align_wpb -> align
# 2011-03-16 ah New DISK_SIGNATURE tag added for MBR partitions, Split partition0.bin into
# MBR0.bin and EBR0.bin, Corrected bug in backup GPT DISK patching
# 2011-03-10 ah Removes loadpt.cmm, splits partition0.bin to MBR0.bin, EBR0.bin
# 2011-03-09 ah Much more error checking, cleaner, adds "align_wpb" tag
# 2011-02-14 ah Added patching of DISK for GPT
# 2011-02-02 ah Allow MBR Type to be specified as "4C" or "0x4C"
# 2011-25-01 ah Outputs "patch.xml" as well, allows more optimal partition alignment
# 2010-12-01 ah Matching QPST, all EXT partitions 64MB aligned (configurable actually)
# More error checking, Removed CHS option, GPT output is 2 files (primary and backup)
# 2010-10-26 ah better error checking, corrected typo on physical_partition for > 0
# 2010-10-25 ah adds GPT, CFILE output, various other features
# 2010-10-08 ah released to remove compile errors of missing PERL script modules
I am purposely trying to keep my fsc partition to 1kb. I can make the change in my xml file to 2kb and the tool will continue. If I leave it at 1kb it will error out. Anyone else have this issue?
Should have held off asking. Once I found a newer version of the tool that issue is solved. Case closed.
follows the link of Stock Moto X4 ROM with Android 7.1.1 and September patch.
Model: X4 (Payton)
Version: NPW26.83-34-0-1
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The linked page shows a error, will be better if you can upload the file.
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
ebrandsberg said:
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
Click to expand...
Click to collapse
Just ran cat /proc/partitions.... dang, you are right
|payton_sprout:/ $ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
253 0 1048576 zram0
179 0 30535680 mmcblk0
179 1 3584 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 128 mmcblk0p9
179 10 128 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 128 mmcblk0p21
179 22 128 mmcblk0p22
179 23 256 mmcblk0p23
179 24 256 mmcblk0p24
179 25 112640 mmcblk0p25
179 26 112640 mmcblk0p26
179 27 1 mmcblk0p27
179 28 8 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 16384 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 2048 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 6144 mmcblk0p36
259 5 6144 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 512 mmcblk0p39
259 8 128 mmcblk0p40
259 9 16384 mmcblk0p41
259 10 512 mmcblk0p42
259 11 8192 mmcblk0p43
259 12 65536 mmcblk0p44
259 13 65536 mmcblk0p45
259 14 16384 mmcblk0p46
259 15 16384 mmcblk0p47
259 16 1024 mmcblk0p48
259 17 8192 mmcblk0p49
259 18 256 mmcblk0p50
259 19 256 mmcblk0p51
259 20 1 mmcblk0p52
259 21 1 mmcblk0p53
259 22 4608 mmcblk0p54
259 23 4608 mmcblk0p55
259 24 33424 mmcblk0p56
259 25 33424 mmcblk0p57
259 26 64 mmcblk0p58
259 27 64 mmcblk0p59
259 28 8192 mmcblk0p61
259 29 8192 mmcblk0p62
259 30 589824 mmcblk0p63
259 31 589824 mmcblk0p64
259 32 4227072 mmcblk0p65
259 33 4227072 mmcblk0p66
259 34 20262895 mmcblk0p67
179 32 4096 mmcblk0rpmb
252 0 4161104 dm-0
252 1 580580 dm-1
Click to expand...
Click to collapse
---------- Post added at 02:09 PM ---------- Previous post was at 01:56 PM ----------
Looks like the OP file was a leaked Brazilian version of the firmware... wonder if the boot.img is the same as US ?
And also looks like Motorola may be giving each variant of the device its own device name... not sure if this will be good down the line, development-wise, or not:
ro.product.name=payton_fi
ro.product.device=payton_sprout
Click to expand...
Click to collapse
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
saketkutta said:
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
Click to expand...
Click to collapse
Is this the partition scheme for Treble? If so, I'm fine with this personally, as it means they have thought ahead to help future-proof the phone (if there is such a thing).
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
crazyates said:
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
Click to expand...
Click to collapse
My custom OS on Nexus 5X took little more than 4 GB. Even if it was project treble (which is not confirmed yet BTW) it should not take more than 9 GB or 10 GB max. Mine out of the box it was 13 GB and something which is ridiculous)
Where did you get the ROM from? Link above is dead?
Iansip said:
Where did you get the ROM from? Link above is dead?
Click to expand...
Click to collapse
I don't think anyone got it here... I saw it bouncing around a couple Brazilian servers, but not open to download. Now that I look, it is the same Build # as the Project Fi version. So, hopefully it will turn up somewhere.
Seems the link in the OP is not dead, just goes to a secure server. It was originally posted on some G+ feeds, but no one has mirrored it yet, apparently
Actually, looks like that whole server is down right now. Every URL returns the same XML error. So maybe it will come back to life soon...
Oh, look at that... Moto has either geo or ISP restrictions on their download! VPN Proxy through server in Los Angeles, and download is running (sloooooowwwly).
Will update tomorrow morning.
UPDATE: Download died at 1.1 GB and the VPN workaround is no longer working. Grrrrr. Could probably extract boot.img anyway, but with no way to check the hash and no images to fall back on, too risky to actually patch/flash it
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
WARNING: This is unverified fimware for testing/research only. Please don't flash it and then complain when you paperweight your new X4.
UPDATED 10-27-2017: This ZIP has several corrupt files... verify anything against the MD5 in the "flashfile.xml" file before using!
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: 2702597112 bytes
SHA256 (unverified on the Motorola end!!!): 124f53fef572850532d029d00166829e200b777491502504c9de215fe7dd1046
DOWNLOAD: https://drive.google.com/open?id=0ByZWXbOZqmVqQ09FUXliN3hYMGs
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I'd love to see a unlock/root method. Hope to see TWRP asap!
Slickademo said:
How do you unlock and root? I just got mine today
Click to expand...
Click to collapse
Unlock is just a regular Motorola unlock... lot of threads on how that is done.
Root is a little more risky and complicated to explain here. The first thing we all need is a trusted factory image -- hopefully the one above is just that. I would suspect that once we confirm a factory image, root methods will be plentiful.
mightysween said:
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
Click to expand...
Click to collapse
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Oh, neat...definitely IP restricted then as I tried a VPN in LV and was still blocked. Wonder what the story is there!
Yes, if you end up with the same SHA256 let me know, we can at least be sure the file is intact.
---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Also FWIW, using that proxy link I posted gave me dl speeds of 2.5-3 Mbps, and plowed straight through to 100%.
mightysween said:
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: ~2.0 GB
CHECKSUM: UNVERIFIED! (my local SHA256: f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e)
DOWNLOAD: https://mega.nz/#!RkM2nSpL!4kHuZQfyHoSfeD-bfCcRxOi3A3rO7hz37RGcxRCglic
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
Also, if you wish to try a direct download from Motorola, this link may work... it is a proxy download through NordVPN. Again, no guarantees and no way to verify (though if you end up with the same SHA256 as above, there is good chance the file is intact).
DIRECT DOWNLOAD (via anon proxy): http://proxy-it.nordvpn.com/browse....cbNvGOLw5iqOebtX0lAb+hCJw==&b=1&f=norefer&pr=
Click to expand...
Click to collapse
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Code:
f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
gee one said:
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Click to expand...
Click to collapse
Thank you kindly! I downloaded again as well with same checksum, so I think we can assume the file is intact.