yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Guides, News, & Discussion] scook94:
I'll (mostly likely) be getting the P9 Plus but am doing so in the realisation that full custom ROMs are unlikely to come to this device and those that do will likely not not have full functionality. Only for this phone is this not a deal breaker for me. If it was a pre-requisite for me buying a new phone I'd have been looking at the new Samsungs or HTC.

I really hope you won't be disappointed that you won't be able to get you P9 modded the way you want it, but I fear you may be.
[Huawei P9 Guides, News, & Discussion] hackslash:
Having owned four Huawei mobiles (P8, P8 Lite, Honor 6 and 4C) allow me to clarify some things for you:

Unlocking the bootloader is easy and won't effect any of the proprietary stuff (such as losing DRM keys, Bravia Engine on Sony devices). The bootloader once unlocked can also be re-locked pretty easily. I used P8 and unlocking bootloader didn't effected camera, sound, etc.

You can probably root Huawei devices without unlocking bootloader using Kingroot. Kingroot supports most of the Huawei devices and currently is also able to root Android 6.0 EMUI 4.0 devices. So I believe, Kingroot will add support for the P9 too.

Huawei devices lack development due to incomplete Kernel sources. I haven't the seen the face of stable Cyannogenmod for any of the Huawei devices I've owned. Honor 6 got CM 11 but was unstable for daily use. It's because of the Kirin SoC which has no good sources and is not development friendly. You won't find any spec sheet relating to any Kirin devices. Talking about Kernel sources, they're a mess and they won't even compile. Huawei releases some of the sources in order to be GPL compliant and if you try to compile AOSP, all proprietary stuff such as NFC, Fingerprint, IR Blaster (in this case) are extremely difficult to be run on custom ROM.

Since EMUI 3.1, almost all Huawei devices have double tap to wake feature. P9 should have it including off screen gestures and probably knock gestures.
[Huawei P9 Guides, News, & Discussion] clouds5:
Thx! Exactly the information I was looking for. This sounds good enough for me. I usually use stock roms with root/xposed and this should be possible on the P9. Good news about the bootloader as well.

The main reasons I used custom roms in the past was to improve performance and battery life. Both are basically not an issue anymore with current phones. And theming is built in anyway.
[MTCB Android Head Units Q&A] xrapidx:
Hopefully they all the same, but what is the GPS antenna plug/connector type? I need to try and find one which picks up a better signal - mine isn't great, I keep having to move it around the dash.

I have to remove the dash to get to it, so would prefer to know the type before ordering and replacing.
[MTCB Android Head Units Q&A] xrapidx:
Nobody know what the connector is called? :(
[MTCB Android Head Units Q&A] themissionimpossible:
Check this list to identify the GPS connector:

http://www.l-com.com/content/Coaxial-Connector-Chart.html

It should be a SMA type connector.
[MTCB Android Head Units Q&A] cranbiz:
Its a standard SMA connection on the Joying, can't see why others won't use the same. I had to extend my GPS antenna and used a 3' SMA male-SMA female.
[Mogul, XV6800 General] SINNN:
I downloaded the mms cab for the mogul thru PPCGEEKS. I sent one large 2 mp picture and it went thru to another mogul just fine. Then I tried to send another picture and got a error messsage of "Your message of 21k exceeds the limit of 0k.Please remove some content and try again." Does anyone else get this?:confused:
[Mogul, XV6800 General] nursemm05:
hack your registry and you can change the size limit.

1. hlm

2. software

3. arcsoft

4. arcsoft mms ua

5. config

7. ui

8. sizelimit

9. sendlimit (change this one)

AND...

with reg edit go:

1. hlm

2. software

3. arcsoft

4. arcsoft mms ua

5. config

7. mm1

8. 6654

9. send default (change this one)

I changed both of mine to 958400. the default to receive is 99999999. I suppose you could set that as the send default as well.
[Mogul, XV6800 General] SINNN:
I did your instructions of hack the reg and went to number 8 which you put "size limit1". Whant then?

Then I did the reg edit in your second intructions and went to mm1 but when i highlight that i dont see "send default". Im sorry.. im ususally good but i think theres some steps missing here..
[Mogul, XV6800 General] nursemm05:
Yes I did leave out a step in each, sorry for the confusion!
[Mogul, XV6800 General] SINNN:
care to share?
[Mogul, XV6800 General] nursemm05:
look in my first post, I edited it before I posted I left out a step
[Mogul, XV6800 General] SINNN:
thxs. I didn't notice it.
[Mogul, XV6800 General] monster28:
hello

the redid the mms and now u can send biger pix heres the new zip
[Mogul, XV6800 General] nursemm05:
do you know the limit for the new download?
[Mogul, XV6800 General] fusQer:
this stopped working for me. anyone else?
[Mogul, XV6800 General] Raspster:
Sprint shut down the MMS on the Mogul... As of right now, the only way you can send a picture is thru e-mail attachments. Yes I know... VERY STUPID!
[Mogul, XV6800 General] fusQer:
i wonder why they would do that. why is it against humanity to allow picture mail that we pay for to work with our moguls?
[Mogul, XV6800 General] Goose02:
Has there been any update about the MMS working again?
[Mogul, XV6800 General] jdmsohc22:
im curious as well..??
[Mogul, XV6800 General] 355Nation:
From what I've heard they're going to couple with the other big companies and start charging for MMS...which, I thought we were already paying for. :confused:

But, again, I stress it's what I've heard (ppcgeeks) so take it for what it's worth.
[MTCB Android Head Units Q&A] skydancer79:
Hello all. I bought this radio for my Skoda Fabia. I have a few question. My maxidot screen does not show file names, only track 1, track2, etc...if I use something else, like poweramp, it just shows OTHER MEDIA. Any way of fixing this? Pumpkin support doesn't have a clue.

Also, can I install Malaysk ROM for this radio? Since it has many hardware buttons, will they still work?

Thank you
[MTCB Android Head Units Q&A] halloj:
You need to provide a picture of your system screen to be able say yes or no.

Normally yes, but you never know, since Pumpkin is only a reseller.
[MTCB Android Head Units Q&A] skydancer79:
https://drive.google.com/file/d/0B305vO-CeHmQRGhldU01NWkzdHM/view?usp=sharing

https://drive.google.com/file/d/0B305vO-CeHmQZUJaaWhHaEQwUU0/view?usp=sharing

thanks
[MTCB Android Head Units Q&A] halloj:
To me that looks perfectly correct for Malaysk FW.
[XDA Assist] ThomasHoey:
Hi Everyone.

Firstly let me thank all the android tech support people in this forum, giving the great advice for the noobs like myself.

My problem

I recently Factory reset my HTC One M8 and now its stuck in a boot loop. when i power the phone on it hangs on the HTC logo screen. When the phone is on the power button does nothing when pressed on its own. Sometime if I do a hard reset by pressing vol+ and power it goes past the logo screen to android is starting, optimizing app but once it runs through all the apps it hangs on android is starting, starting apps.

Things I have tried.

loading bootloader using vol- and power, doesn't work

Hard resetting using vol+ and power, turns phone off but again hangs on logo screen, sometimes optimizes apps but hangs there.

Connecting to computer and running ADB, ADB doesn't find phone due to not being able to put phone into debugging mode.

Entering fastboot mode using power on then when phone loads quickly pressing vol- and single pressing power, doesn't work

hard resetting and when phone goes black, trying to enter recovery mode by pressing vol- and power, doesn't work

anyone with any ideas?

any advice would be greatly appreciated.
[XDA Assist] Trafalgar Square:
Hello,

you asked here:

HTC one M8 stuck in bootloop

No need to keep this thread open.

Thread closed.

Kind regards

Trafalgar Square

XDA Assist
[Wileyfox Storm] Wagster:
Hi,

I'm considering the Wileyfox Storm but reviews I've read really slate the main camera despite the impressive specs. I'm wondering if the problem was a software one and if it's been improved since the reviews came out in Oct/Nov?

Cheers guys.
[Wileyfox Storm] max650001:
I think it's a sony 13 mb sensor but it's doesn't have ois so yiu could had a nuce pictures but not always
[Xperia Z5 Premium Android Development] BustyLoli-Chan:
Following much of moonbutt74's advice and using the sources from his kernel (thank you so so so much!)

https://github.com/moonbutt74/kernel_sxz5p_aosp_4square

I was able to modify

https://github.com/moonbutt74/kerne...rm/boot/dts/qcom/dsi-panel-satsuki.dtsi#L1107

and create what I believe to be the first working truly 4k always on kernel for the z5p

I say what I believe to be because honestly I can't really tell.

I reset my wm density and wm size from the "emulated 4k thread" http://xdaforums.com/showpost.php?p=64587441&postcount=13

Screenshots taken appear to be in 4k

The phone seems to switch into 4k much in the way it would if it were "emulated" after the window manager loads

1440p video appears to be available on YouTube

And honestly it looks really sharp and everything seems to be rather tiny

As of right now I only have this build for the E6853, as it is the only device I own, and I've literally just managed to get this "working"

I'll consider trying to build this for the dual if the feedback here seems good and if people can actually confirm whether this is working or not.

I also don't even guarantee this loads on any device but my own. (This could be 100% a fluke)

Also also, if it does work, it'll probably destroy your battery.

Files

I flashed my file with fastboot

fastboot flash boot E6853-always4k.img

When it first boots the screen looks a little fudged up (for lack of a better word), but if you give it a little bit (for me at least, it boots and appears to be in 4k mode)

Please let me know what you find, and please don't blame me (but do let me know) if it doesn't work for you or breaks your device.

In other news,

At the time of writing this, I'm probably in possession of the only phone in the world natively running a 2160x3840 resolution right now, so that's pretty cool.
[Xperia Z5 Premium Android Development] raven213:
nice work gonna give a try :)

edit: im using RomAur-v3.0 will this kernel work?? just asking before i flash thanks
[Xperia Z5 Premium Android Development] Rubensss:
I have installed it and I have to say that is all too small , icons , options, keyboards, etc ... for everyday use would be very uncomfortable. I also noticed lag when accessing the application drawer in transitions panel and keypad ... I 've become the kernel of zacharias.maladroid , anyway thanks for your work . a greeting
[Xperia Z5 Premium Android Development] moonbutt74:
B,

okay e6853

Fudgy at beginning as you said. :silly:

That's Sony's splash logo though, doesnt display right at 4k, and the boot animation as well, again Sony.

Gonna need 4k bootanimations!

Note : does not play well with Nova Launcher. xD

What is your screen density in the screen shots? At default I'm @

shell@E6853:/ $ wm size
Physical size: 2160x3840
shell@E6853:/ $ wm density
Physical density: 480
Override density: 560

I'd like to see the patch/mod you did to kernel , please post? I want to tuck that modification into a cm build to see what happens. NVM i missed the link in OP.

What are your obeservations on battery consumption?

On a side note this modification seems to break the booting to recovery via bootec setup.

m
[Xperia Z5 Premium Android Development] BustyLoli-Chan:
Honestly, I have no idea :D

:(

Please let me know what you find though!

Nothing is to prevent you from adjusting the DPI manually at this point. This was purely to see if 4k could be done. You can easily tweak it it to your liking from here either with builp.prop, wm density or some other app dpi changing app. :)

My density is the same as yours minus the override density, but I'm using action launcher. (I'll agree with Rubensss though some things are just too tiny. I'll probably start messing with my actual density later today)

shell@E6853:/ $ wm density
vm density
Physical density: 480
shell@E6853:/ $ wm size
vm size
Physical size: 2160x3840

The link in the original post is the original file. I've pushed the 4k modification(s) to here:

https://github.com/BustyLoli-Chan/k...arch/arm/boot/dts/qcom/dsi-panel-satsuki.dtsi

I've not had a real chance to take it out and test battery life yet, (I stayed up super late working on it and spent most of today sleeping)

Also I was worried about recovery. I haven't checked it yet, but I thought it might simply fail or look crazy because I took 1080p mode out entirely to force 4k to work. All my previous attempts to set 4k preferred and have it play nice with 1080p had failed, but I can mess around more with it today (or you can if you want now that you have the file.)

Everything else I tried seemed to cause serious problems and with this for some reason it just suddenly booted and worked.

might be able to add all the blocks mentioning 1080p back in under the ones that say 4k (since my first edit was to just leave 4k where it was and move the preferred mode flag which didn't seem to work)

Now that we know this is working I would like to seriously and formally thank you for all of your help and hard work with assisting me to the point where I could actually make this work. I'd also be lying if I said fesar's thread and AndroPlus'es post weren't huge inspirations for me to try to get this done.
[Xperia Z5 Premium Android Development] moonbutt74:
[MENTION=7165114]BustyLoli-Chan[/MENTION]

Hey check /try this out modify build with 4k option WIP

The above commit modifies the kernel build with a 4k option in line with your experiment.

Instead of modifying arch/arm/boot/dts/qcom/dsi-panel-satsuki.dtsi

I added arch/arm/boot/dts/qcom/dsi-panel-satsuki-4k.dtsi , which contains your modifications so far.

When you run the build script and get to the menuconfig portion, going to

Platform selection ---> [ ] Impose 4k resolution on Satsuki Target

Permits you to build your 4k display experiment. This way you can work/mod arch/arm/boot/dts/qcom/dsi-panel-satsuki-4k.dtsi

and leave the orriginal [2k] version intact.

Currently in menuconfig

Boot options --->Build a concatenated Image.gz/dtb by default does select the new/correct dtsi's but still doesn't find the resulting dtb's though they DO build. I have a little work to do there. But zImage and dtb.img DO build. and do boot the device correctly.

The dtb's select based on whether the 4k option is enabled or not.

You don't actually need any of the above but it seemed like a less destructive way to care for your kernel source. :)

That and I was wondering if it would actually work, which it mostly does. If you're interested in this setup, I'll update you when i figure out why making the Image.gz-dtb doesn't find the 4k dtbs.

This is that portion of the build

make[1]: *** No rule to make target 'arch/arm64/boot/dts/msm8994-v2.0-kitakami_satsuki_generic-4k.dtb', needed by 'arch/arm64/boot/Image.gz-dtb'. Stop.
/storage/sxZ5_dev/kernel/aosp_4square/arch/arm64/Makefile:84: recipe for target 'Image.gz-dtb' failed

But other wise the normal dt.img does generate

DTB combiner:
Input directory: './arch/arm/boot/dts/qcom/'
Output file: 'build_satsuki/out/boot.img-dtb'
Found file: msm8994-v2.0-kitakami_satsuki_generic-4k.dtb ... chipset: 207, rev: 131072, platform: 8, subtype: 0
Found file: msm8994-v2.1-kitakami_satsuki_generic-4k.dtb ... chipset: 207, rev: 131073, platform: 8, subtype: 0
=> Found 2 unique DTB(s)

and the resulting kernel binary and dt.img

-rw------- 1 root root 784384 Apr 20 23:56 boot.img-dtb
-rwxr-xr-x 1 root root 19487944 Apr 20 23:56 boot.img-zImage

The normal [2k] build will run without issue

-rw------- 1 root root 788480 Apr 21 00:14 boot.img-dtb
-rwxr-xr-x 1 root root 19487944 Apr 21 00:14 boot.img-zImage
-rw-r--r-- 1 root root 8827937 Apr 21 00:14 boot.img-zImage_gz

m
[Xperia Z5 Premium Android Development] BustyLoli-Chan:
I feel as though some if not all of this is over my head lol

I've been trying to get recovery and the pre-OS systems to work.

I added 1080p timings back into my script over here https://github.com/BustyLoli-Chan/k...arch/arm/boot/dts/qcom/dsi-panel-satsuki.dtsi

The device still boots, but there is no change over the 4k only version, which makes sense really because nothing ever tells the device to switch to 1080p over the preferred 4k. I realize there are a lot of "extra" things in the 4k timings that aren't present in the 1080p but I don't know if any of these settings will achieve what I am looking for.

I was going to try going through and changing each section of the dtsi file to be 4k in the hopes that maybe the pre OS parts of the code use a different sets of timings that the actually OS does (so it could default to 1080p until the OS boots and then start 4k mode) but truthfully, I don't know if any such an option/special timing at all exists.

I feel like the way the phone operates by default is that it stays in 1080p mode until some software in Sony's proprietary apps feeds it the right command to go 4k.

A more graceful way to implement 4k always on would probably be to wait until the OS boots and then feed the panel that command (that way all the pre OS systems still work fine). If we could find the code for that, such an implementation could probably allow you to toggle 4k on or off somewhere in the system settings or somewhere as accessible as the power menu, but such an implementation would be entirely outside the scope of files I'm currently trying to edit.

All in all, I've learned I really don't know a whole lot about any of this.

I hope to learn and figure out more, but documentation and resources seem scarce.
[Xperia Z5 Premium Android Development] lotusalex2000:
Hi moonbutt74

Do you think its possible to make a version of the kernel for the z5 Premium Dual (E6883)?

I'm a VR NERD.

I use my z5 premium only for VR because for all other things i use a Samsung S7.

I hope you can help me, because its a shame from Sony that the display are not usable in 4K with the Zeiss VR One. Its only possible without head tracking. with the sony movie player...:(.

I start with test: S7+Gear VR vs. Z5premium Dual+VR One and today the best VR Phone is the S7

but only because the bad software from Sony. :(

Thank you
[Xperia Z5 Premium Android Development] BustyLoli-Chan:
It looks like the DTSI file for the Satsuki is the same regardless of whether you have the Dual or the Regular, so in theory you should just be able to run the build script for "./hmm-satsuki-dsds" pull the current kernel image from your device, replace the kernel, repack the image, and flash it and get 4k.
[Xperia Z5 Premium Android Development] lotusalex2000:
Thanks BustyLoli-Chan

i try it. :)
[Xperia Z5 Premium Android Development] EMJI79:
What about battery life?
[Xperia Z5 Premium Android Development] BustyLoli-Chan:
Battery life is usually fine in my opinion if the phone screen isn't constantly on. If you are constantly using the screen though, man does it drain. usually playing around with it though I can make it through about a full class day. I'd estimate 5-6 hours of regular use, but do not quote me on that.
[Xperia Z5 Premium Android Development] EMJI79:
Would be great to choose display app by app: for example, 4k on YouTube, Google +, instagram,... 2k on Chrome and 1080p everywhere else.

Something like that.

Would it be possible to have an Xposed module do that?
[Xperia Z5 Premium Android Development] xyfl0203:
e6883 can be used?
[Xperia Z5 Premium Android Development] freefrank:
github down?
[Xperia Z5 Premium Android Development] lotusalex2000:
I need some help with the compiler

Hi

I use a guide to compile the kernel. developer.sonymobile.com/knowledge-base/open-source/open-devices/how-to-build-and-flash-a-linux-kernel/how-to-build-and-flash-a-linux-kernel-from-sony-copyleft-archives

1. Unlock the boot loader : done :)

2. Download a cross compiler :

I use the /android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/

because in the next step I use :

3. export CROSS_COMPILE=/android/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-

Done :)

4. Download the kernel source. Thanks for moonbutt74's : Done :)

5. Identify your device’s config file name : ??????? :confused: WITH buildprop Editor i find under BUILD INFO ro.board.platform: msm8994 and in the Kernel directory arch/arm64/ there is a file msm8994_defconfig :fingers-crossed: lets try it.

6. Configure the kernel

open Terminal and : make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE msm8994_defconfig

now i see some bla bla and no errors :)

7. Build the kernel and needed modules

I try in Terminal: make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE -j 1

Now i get:

#make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE -j 1

#Makefile:605: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler

# CHK include/generated/uapi/linux/version.h

# CHK include/generated/utsrelease.h

# CC kernel/bounds.s

#gcc: error: unrecognized command line option ‘-mlittle-endian’

#gcc: error: unrecognized command line option ‘-mgeneral-regs-only’

#/home/lotusalex2000/backup/android/kernel/./Kbuild:35: recipe for target 'kernel/bounds.s' failed

#make[1]: *** [kernel/bounds.s] Error 1

#Makefile:862: recipe for target 'prepare0' failed

#make: *** [prepare0] Error 2

what did I do wrong?????

:crying:
[Xperia Z5 Premium Android Development] EMJI79:
Maybe Satsuki?
[Xperia Z5 Premium Android Development] lotusalex2000:
I read some other guides and I think, its problem with my PC. I hope that i find someone that can compile the kernel.

[MENTION=7165114]BustyLoli-Chan[/MENTION]

BustyLoli-Chan can you please compile your kernel again, with the config satsuki-dsds in the Folder of moonbutt74? Thats the Config for the Z5 Premium Dual Sim

Thank you
[Xperia Z5 Premium Android Development] EMJI79:
Can you please give link to other guides you found?
[Xperia Z5 Premium Android Development] lotusalex2000:
the best,

with Kernel from z5 Premium

http ://developer.sonymobile.com/knowledge-base/open-source/open-devices/how-to-build-and-flash-a-linux-kernel/how-to-build-and-flash-a-linux-kernel-for-aosp-supported-devices/
[Xperia Z5 Premium Android Development] HillyHd:
does not boot on my phone just boot loops with green LED on
[Xperia Z5 Premium Android Development] lotusalex2000:
after look this video https://www.youtube.com/watch?v=OG41hMstx8o

the compiler work,

but now i have a image file and my problem is to get the boot.img
[Xperia Z5 Premium Android Development] lotusalex2000:
after install all software in the video

download the kernel:

Kernel from : https://github.com/SonyAosp/kernel

the Z5 Premium dual are: aosp_kitakami_satsuki_dsds_defconfig

Terminal: to make the Kernel:

go into the Kernel folder (kernel-n)

export CROSS_COMPILE=/home/lotusalex2000/android+kernel/aarch64-linux-android-4.9-uber-master/bin/aarch64-linux-android-

export ARCH=arm64

sudo apt-get install -y ccache &&echo 'export PATH="/usr/lib/ccache:$PATH"' | tee -a ~/.bashrc &&source ~/.bashrc && echo $PATH

make aosp_kitakami_satsuki_dsds_defconfig

make

at the end i get: :)

OBJCOPY arch/arm64/boot/Image

GZIP arch/arm64/boot/Image.gz
[Xperia Z5 Premium Android Development] EMJI79:
Good luck :)

I am watching you, hope you succeed cause I am looking forward to using it on my future z5 premium ;)

If i may i would suggest the possibility to choose 1080p/1440p/4k app by app to manage battery.

Keep up the good work
[Xperia Z5 Premium Android Development] iwilltouchthesky:
Delete this post please