yashsingh1/xdaforums huggingface dataset:
[Sony Xperia M4 Aqua] dani020110:
The same, bootloops and I can see the same error
[Sony Xperia M4 Aqua] dimusa:
Its no possible to port that without code. The main reason its the internal memory or hardware
[Advantage X7500, MDA Ameo ROM Development] sabes143:
What is the wallpaper size for the DPI 96 in real VGA.

Also DPI 128 in realvga freezing after resetting itself in my athena. Needed hard reset to bring back to DPI 192.

In DPI 192 evrything smooth and no prob with battery or WMP. But i wanted to try the real vga at 128 or 96. 128 freezing problem need hard reset. 96 working but not WMP even applied the patch. i am going to install Core player 1.1.1. will update the result.

Please let me know why 128 freezing, and what size wallpaper to use at 96 dpi?

Thanks in advance.
[Advantage X7500, MDA Ameo ROM Development] keithwwalker:
The Athena doesn't realize whether you are in 96, 128, or 192 mode, so the wallpaper is squeezed horizontally in 96 as if you were still in 192. This makes the image tile.

I don't know if there is a workaround...
[Advantage X7500, MDA Ameo ROM Development] eaglesteve:
To avoid having to hard reset, use a safe mode program such as iLauncher, Pocket Plus etc. In that way, if it freezes, you have the option of doing a safe mode and run the RealVGA and set to the resolution does not freeze instead of having to hard reset.
[Advantage X7500, MDA Ameo ROM Development] Mahmood:
everytime u change the resolution you actually have to add 0,5 (50%) to the orignal size the image.

normal resolution is = 192

resolution with 128 = 192/1,5 = 128 (1 +0,5 = 1,5)

resolution with 96 = 192/2 = 96 ( because 1+0,5+0,5 = 2)

so wallpaper with 128 must be 1,5 (15%) larger then 192

and for 96 must be 2 X (200%) larger wallpaper then a normal 192.
[Advantage X7500, MDA Ameo ROM Development] sabes143:
DPI 96 and wallpaper size

Thanks for the reply to my question. i will try to create a wallpaper tonight and will comment tomorrow.

Thanks again
[Advantage X7500, MDA Ameo ROM Development] keithwwalker:
I'll give it a shot! but I think your numbers are off a bit. The 'resolutions' refer to the icon pixel sizes (96x96dpi) and not the VGA or otherwise resolution.
[Advantage X7500, MDA Ameo ROM Development] keithwwalker:
I think the workaround is this:

Assume your wallpaper measures 640x480 exactly.

WM5 assumes the top and bottom bars are 52 pixels in height when added together.

WM5 compresses your image vertically to get 480-52= 428 pixels, or to put is another way 428/480 = .89167 or ~89.2% vertical compression

The inverse of 89.2% is 121.5%

So if you vertically stretch your image 121.5%, then set as a background image, then it is squished down by WM5 to approximately the correct size.

I will try this out tonight....
[Advantage X7500, MDA Ameo ROM Development] keithwwalker:
Results

Before I started shrinking I thought I would try just subtracting pixels from the bottom of the image as it appears that the image starts just below the upper title bar - if the image is too large, the extra bit gets cutoff on the bottom.

At 92dpi icon resolution, the sum of the upper and lower wm6 bar heights equals 52 pixels

So 480-52=428 pixels

So I cropped an image to 640widthx428height pixels and viola! - the whole image displays nicely!

So here are my calculations for the different resolutions:

QVGA/192dpi : 52 pixels ht. = 640x376

128 dpi: 34 pixels ht.: 640x412

VGA/96dpi : 26 pixels ht.: 640x428

Cheers!

Keith Walker
[Advantage X7500, MDA Ameo ROM Development] keithwwalker:
Here's my 640x428 wallpaper on 96dpi

Fits perfectly!
[Advantage X7500, MDA Ameo ROM Development] eagle 1:
Looks Great..Thanks for providing the pixel height for all three resolutions!

You might want to remove your phone number!
[Advantage X7500, MDA Ameo ROM Development] keithwwalker:
Thanks, I noticed that right after I posted the images, lol:)
[Advantage X7500, MDA Ameo ROM Development] keithwwalker:
Conversely, for portrait mode in vga/96dpi, the wall paper would be sized:

480 pixel width

640-(2*26)=588 pixel height
[Xiaomi Mi 4C] siul_lasc:
Many of you probably have already noticed that this phone overheats when playing some heavy 3d game... Even with some benchmarking...

And due to that you have probably experienced some nice lag while the phone is overheated...

Well, I have experienced that... In real racing for example... And after having tried all the roms available and have only used miui when I bought it... I now got back to it.

And guess what... Besides the good look, the unbeattable camera app... I now realized that in miui, my phone does not get half the heat it got with cm, pac or lately with broken rom... Why does it happen I dont know... But the truth is miui is very fluid, the phone does not overheat anymore and I play real racing without any lag...

You should all try it...

Miui dev rom in my case.
[Xiaomi Mi 4C] FrankBullitt:
I'm using brokenOs with a modded thermal conf (got it from here on XDA forums) + kernel configs (used some configs discussed in the CM threads of the TS forums, applied using EX Kernel manager, but could be using the embedded kernel auditor) and I'm getting a much cooler phone and much better battery life than I ever did with MIUI. Not to mention a completely lag free experience like I was never able to get with any miui (eu, smiui, even chinese dev rom).

The camera app is probably the only thing the original miui has that I still think as a better software piece than any other on the playstore (althoug, you should try cameraMX. It's brutally good).

I used MIUI for a couple of months and initially gave it the benefit of the doubt. But no, I won't go back to it again now that I've tried others.
[Nexus 6P Q&A, Help & Troubleshooting] snappycg1996:
Maybe I just had really high expectations for this phone, maybe I just got a bad unit or maybe it's just that way.

When I first got my N6P, I had a time flashing it. My computer would freeze and the phone came back saying it was corrupt, then the phone reset itself. The files on my N5 are still on my N5 since it's so painful to transfer files. Here are some problems I'm having.

The Google app is telling me that the app is not compatible with my version of Android. What?? That makes absolutely no sense, and since it isn't compatible, I can't update it. I'm using an LG G Watch, and the device shows it's connected, but I am getting zero notifications on it. I open the Wear app and it tells me to update the Google app. This is where I hit a wall.

Second is Snapchat. I barely use Snapchat, but when I do, the app will not work. It freezes, stutters, lags, and requires a force close always. My Nexus 5 worked absolutely fine.

Third is the camera. The camera, since I rooted just will not open. I've looked up this issue and apparently its common, and flashing vendor.img fixes it. So I downloaded vendor.img and flashed it. I then got an error saying something was wrong internally with my device. Then I downloaded the latest factory image (that I'm on) and flashed that vendor.img instead of the one I downloaded. The error went away and the camera opened. Then that was that, it never opened again. Apps like Instagram, Facebook, Snapchat, etc will not use the camera at all, because I guess the camera API is corrupted. Why does this happen on the 6P after root?

Lastly is the battery life. I'm a college student with bills and have got to wait until next payday to get my phone turned on with service, so I've been using airplane mode with WiFi. Adaptive brightness is off, 20% brightness, NFC, WiFi and Bluetooth scanning is off, GPS off, ambient display is off since I have my watch, and I get almost 3 hours SOT, usually 2.5. Keep in mind, this is in airplane mode! I see people getting 4, 5, and 6+ hours SOT on the forums, saying that everything is turned on and pulling data, etc. This is insanely disappointing to me, as I hoped with the big battery and Marshmallow, it would be more optimized. I paid 700 dollars for this 128GB phone, so I expected the battery to be better than my N5 was back in 2013. Currently I have 87% battery and it's dropping while I'm not using it. I have 18 minutes SOT. :(

The phone itself though is truly amazing and beautiful. Very premium feeling, very sleek, very thin and light. The front facing speakers BLOWS my mind on how crisp and loud they are. They are wonderful. The display colors and crispness is gorgeous. The fingerprint scanner is really great to have, and the phone is very fast.

I don't know what to do. If I can't get better battery life then I'm going to need to return the phone, even though I sincerely don't want to.

Help with any of these? :( I really just want better battery from such a premium device and it truly saddens me now.
[Nexus 6P Q&A, Help & Troubleshooting] Gizmoe:
What are you running. Stock or custom. I am on full stock and don't have any of those issues. I also only plug in my phone about an hour a day and I am a heavy user. It seems you may just have a bad chip though. It happens.
[Nexus 6P Q&A, Help & Troubleshooting] TyrellP:
I agree, I wanna say he have a bad unit, I get 4-5 hours of screen on time and I'm on my phone from the minute I get up, until I go to sleep. I'm a really heavy user
[Nexus 6P Q&A, Help & Troubleshooting] Soulfly3:
so, by the sounds of it, you flashed a bunch of things improperly, and now are wondering why things aren't working?

(before you get sassy, you did flash things imporoperly (comp freezing, phone resetting), because you had some errors, and your vendor was out of date etc.. This isn't an insult, happens to all of us at some point or another)

follow THIS guide, and go back to COMPLETE stock:

http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

from there, I am more than certain you will see things improve. drastically.
[Nexus 6P Q&A, Help & Troubleshooting] dratsablive:
The Camera not working is usually an indication of an improper kernel/boot img.
[Nexus 6P Q&A, Help & Troubleshooting] snappycg1996:
I'm not the only one with this bad battery it seems though. Are there really that many defective units??? I'm on complete stock 6.0.1 with latest February patch.

I don't know. I'm gonna factory reset I guess, battery is draining pretty rapidly now. 38 mins SOT and 48% battery...

I'm gonna try factory resetting. As of now, battery is complete garbage. I don't see how a wrong root/vendor.ing flash could cause dramatic battery loss.

I flashed the wrong vendor.IMG for my version which probsbly is causing it. I'm gonna just factory reset.
[Nexus 6P Q&A, Help & Troubleshooting] snappycg1996:
What do y'all make of this??
[Nexus 6P Q&A, Help & Troubleshooting] Soulfly3:
you have massive wakelocks which is draining your battery.

Just factory reset and follow the instructions in the link i gave you to go to the latest stock
[Nexus 6P Q&A, Help & Troubleshooting] snappycg1996:
I will after I deplete the battery lower, I just wanna see how long it lasts.

The device is also now slowing down a bit. The RAM is really being used..

EDIT: tries uploading screenshots. It's over 2 GBs being used on RAM.
[Nexus 6P Q&A, Help & Troubleshooting] TonzaTheChosenOne:
Your phone is just messed up, I'm sure that once you get it completely stock, it'll work better and have a better SOT.

There's been some reports of bluetooth causing wakelocks when using smartwatches.
[Nexus 6P Q&A, Help & Troubleshooting] adotkdotjh:
:confused: Not judging. Just confused.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
Sounds to me like you've done something to the phone yourself that's causing these problems. Especially the camera not opening, that's a symptom of having the wrong boot.img flashed to the device. Factory resetting won't help if you have the wrong boot.img flashed. You need to flash the factory images to ensure that everything is in line. See my guide for details:

http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
[Nexus 6P Q&A, Help & Troubleshooting] snappycg1996:
What's confusing? I saved up the money over my paychecks and then my college mkney came back in and I was able to buy it finally. The G Watch was on sale for 100 when I bought it.

It just doesn't make sense how it could be making my battery so bad. But like I said, I'm working on flashing the factory image right now.

I am gonna flash the stock image 6.0.1 and then root systemless and see if that helps. Besides that though, I'm not sure how that could be causing such terrible battery. It's very disappointing.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
It kinda does make sense, I don't know exactly what you've done to cause these problems but mismatches can affect battery performance. Go back to stock, flash the latest SuperSU beta and nothing else and see how it performs.
[Nexus 6P Q&A, Help & Troubleshooting] snappycg1996:
Should I lock my bootloader and then unlock it again? Or just flash factory?
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
No need to mess with the bootloader, just leave it unlocked.
[Nexus 6P Q&A, Help & Troubleshooting] cstrife999:
It has to be your unit. Of the four users I know none have these issues. If restoring doesn't fix it...
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
It doesn't have to be the unit at all, it's likely to be a result of inexperience and bad flashing.
[Nexus 6P Q&A, Help & Troubleshooting] snappycg1996:
Flashed back to complete stock, and rooted. Phone feels faster, camera now works, BUT battery is still not up to par with what others get and reviews say. I can barely get two hours, it's usually around 2:40. I have no rogue apps, I have BBS, and WLD showing nothing out of the ordinary. Normal drainers like scanning is off and I am using greenify. With no luck. Battery life is still just like my N5 when it was brand new in 2013. For a 2015/2016 phone, it's very disappointing.

Anything else you guys would recommend?
[Nexus 6P Q&A, Help & Troubleshooting] TonzaTheChosenOne:
Uninstall Greenify, it's known for messing up with Doze.

Btw, are you living in a bad reception area? Do you use wifi or 4G most of the time? Brightness?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Banayat:
Hi folks, some system (or user apps) like mediaserver cannot read internal storage. It was noticeable to me, when I've installed Xposed Media Scanner. It always shows up no scan for internal storage ("internal sd") on boot. It does not matter if I place a music/picture file on it. Even most music players cannot find anything on internal storage. I always have to choose through file explorer which music file should be played in this case. Btw, there is no ".nomedia" file placed or something. I hope everyone got the point. Can anyone help?
[G4 Q&A, Help & Troubleshooting] Yotam.B:
Hey everyone,

Recently my device is very slow. I downloaded the app CPU-Z and my surprise that 5 of 6 cores are not working.

Notably, the device is not on battery saving mode.

H815 Android 5.1 no rooted.

Does anyone know what the problem is and how to fix it? Because it is nearly impossible to use the device.

Thanks ;)
[G4 Q&A, Help & Troubleshooting] alitavas:
Cores 5 and 6 is for Big Cpu and they will enable only when it need

If you are sure that it not work try Download Kernel adiutor then in cpu settings click on the checkbox cpu cores

Sent from my Xperia SP
[Lenovo A850] sahniana:
My problem is, after I power on my phone, it stuck at orange logo with white background. Then after a while, it reboot, and stuck again at that logo. Here's my memory test result from SP Flash Tool. What should I do? I flashed S203 CN rom and this problem persist.

===============	Memory Detection Report	===============

Internal RAM:

Size = 0x00020000 (128KB)

External RAM:

Type = DRAM

Size = 0x40000000 (1024MB/8192Mb)

NAND Flash:

ERROR: NAND Flash was not detected!

EMMC :

EMMC_PART_BOOT1	Size = 0x0000000000400000(4MB)
EMMC_PART_BOOT2	Size = 0x0000000000400000(4MB)
EMMC_PART_RPMB	Size = 0x0000000000080000(0MB)
EMMC_PART_GP1	Size = 0x0000000000000000(0MB)
EMMC_PART_GP2	Size = 0x0000000000000000(0MB)
EMMC_PART_GP3	Size = 0x0000000000000000(0MB)
EMMC_PART_GP4	Size = 0x0000000000000000(0MB)
EMMC_PART_USER	Size = 0x00000001D2000000(7456MB)
[Galaxy S II Q&A, Help & Troubleshooting] liriusz:
Hello, I’m having a problem with my s2. At present I have the cyanogen 13 installed, but I have encountered many problems with this particular software. I decided to return to the stock 4.1.2 by odin, nevertheless it didn’t come off. I’ve been trying several times, but odin is not able to upload stock firmware or CWM. It stopped generally on "<id:0/004>boot.bin". I used two version of rom. I desperately need an advice.
[Galaxy S II Q&A, Help & Troubleshooting] keithross39:
Not totally sure on this, but I believe CM13 sets the device up with a different partition layout to the standard needed for stock 4.1.2......

That being the case, it may be necessary to flash a stock pit file along with the firmware.....

Don't attempt this on my say-so.....wait for someone else to confirm or refute this before attempting. [MENTION=5811506]gsstudios[/MENTION] can you comment?

http://i.imgur.com/rVnFwJM.jpg
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
[MENTION=7288808]liriusz[/MENTION]

If you've repitted your device, you will need to revert back to stock partition sizes.

If you haven't repitted your device, I would start by checking the stock ROM files. Check if they are downloaded properly and not corrupt. Try using a different cable, see if a different ROM firmware will flash or not.

If you don't understand what repartitioning/repitting means, you have the stock partition sizes from samsung and the stock ROM should flash without issues.

gsstudios
[Galaxy S II Q&A, Help & Troubleshooting] keithross39:
Hi [MENTION=5811506]gsstudios[/MENTION] doesn't flashing CM13 automatically remap the partitions? (Correct me if I'm wrong) that being the case, the OP probably/possibly is not aware of it being done......

http://i.imgur.com/rVnFwJM.jpg
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
I believe that the only partition it will touch is the system partition (to allow bigger partition sizes, but by default it will not do anything). This will still not affect installation of stock rom. A repartition will work good either way since it will erase isorec recovery which is only used in CM12.1 and CM13 and some other hidden files that could cause problems.

gsstudios
[Galaxy S II Q&A, Help & Troubleshooting] keithross39:
Ok...understood....thanks for clearing that up :thumbup::thumbup: I've learnt something new.....again.

That's what I like about XDA :) :)

http://i.imgur.com/rVnFwJM.jpg
[Galaxy S III Q&A, Help & Troubleshooting] Leojrk:
What prevents the galaxy s3 have support photos in RAW format?
[Xperia Z2 Q&A, Help & Troubleshooting] diyar95:
I flashed twrp kernel now it will reboot into recovery mode it wont reboot into system please I need stock boot.img I cant power up my phone till someone send it please I'm waiting

xperia z2

D6502 running 5.1.1
[Xperia Z2 Q&A, Help & Troubleshooting] maddboss:
Just flash a whole stock firmware with flashtool and your phone will work :D
[Xperia Z2 Q&A, Help & Troubleshooting] diyar95:
I know but I don't have firmware and I cant download it my internet limited I will be charged :( please just send boot.img
[Xperia Z2 Q&A, Help & Troubleshooting] maddboss:
OK :D but I think you will need the kernel too :D
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
Hey guys bare with me long story,

Last week I decided to try out Cyanogen Mod (12.1). I had not flashed anything to this phone previously or rooted it. I wanted to flash Cyanogen due to less bloat but I did not want to root because I have work software that needs to go on the phone which will not activate with root enabled. So I flashed cyanogen and it was great but my battery started draining and bluetooth was not working properly on it. I decided to give Temasek 's last Lollipop release a try after this because it did not install root either. I gave that a go and still got severe battery drain. So I decided to flash back stock (N900W8VLU2DOH1), but as soon as I did I noticed my two soft key's were not working upon doing so. Back button would not work at all and the other would just open search. So I did multtiple wipes , update from kies etc. But no luck fixing the soft keys. FInally I read that flashing a custom kernal would fix the softkey issue for now until another Samsung update comes out. So I flashed Idle kernal and it fixed the softkeys but now I keep getting a "Unfortunately Knox has closed" message upon start and sometimes out of knowhere. This is really annoying.

Has anybody else ran in to this and know any fixes for it ? Even for just the knox popup. I think it may have to do with the touchkey's firmware from what I read and I'm hoping the next official update from samsung will fix this. I would try another custom rom as long as root is not enabled and battery and bluetooth are functioning properly, just not sure what else to try.

Any help would be much appreciated.

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] Suroky:
Hi.

This happened to my twice.

After much try and error, the solution I found is to REPARTITION the phone using a PIT file for your Phone.

Please find the PIT file for your variant and flash an official samsung rom while selecting the PIT file in ODIN.

Should work. please let us know the result.
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
Hi Suroky,

Thank you very much for the reply. I will try this later today and let you know how it goes.
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
I flashed the PIT file as mentioned and reflashed the stock samsung firmware with Odin. Still no luck. Upon boot I am unable to press the back button and when I press the left softkey it takes me into the search screen. Any other ideas ?

Thanks,
[Galaxy Note 3 Q&A, Help & Troubleshooting] Suroky:
Hi.

Did you select REPARTITION into ODIN? Please be aware this can brick your phone as well.... Be sure to use the PIT file for your device, as there are many variants with different partitions.
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
I selected the PIT file but I did not check the box that said re-partition. Sorry my bad! I will try this again and see if it makes a difference !

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] audit13:
Isn't OH1 the latest for Canadian carriers? Maybe try that version.

http://www.sammobile.com/firmwares/database/SM-N900W8/
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
Hi Audit,

I flashed the latest (OH1) as well. That's the firmware I am on at the moment, still no luck though. Thanks for the suggestion though. Going to try reflashing with PIT and repartition selected as Suroky suggested. Hopefully that does the job.
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
Just tried this again with the proper PIT and Re-Partition checked on in Odin. Still no luck, softkeys still not working. Anyone else have any ideas ?

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] Suroky:
Repartition MUST BE ON.
[Galaxy Note 3 Q&A, Help & Troubleshooting] audit13:
Adding a PIT file automatically checks re-partition in Odin 3.07 for me.

Try this:

uncheck everything in Odin except f.reset time, flash just the ROM without a PIT file, when you see the word "reset" in the status window, remove the USB cable, remove battery, wait 5 seconds, replace the battery, use the key combination to boot into recovery, perform a factory wipe, and reboot to the ROM.

Are you using an original Samsung USB cable? Maybe try flashing on a different USB port?
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
Sorry Surokey, I meant repartition was on not off. Still no luck
[Galaxy Note 3 Q&A, Help & Troubleshooting] rich6619:
Re-Partition does the same for me in Odin. So I did try it twice with the PIT and RePartition on with no luck.

No I lost the original usb cable not long ago. Just using a standard usb 2.0 cable. I've tried on multiple usb ports as well.

I will test out what you mentioned and see what happens.

Thanks!