yashsingh1/xdaforums huggingface dataset:
[G4 General] FPtje:
They can always say "**** you", but that doesn't mean they should. I do not want to hear a defeatist "we kinda deserve it" attitude. Wm is a standard android command. Apps should be able to deal with it. Apps have every right to say "you cannot use my app with a different wm density", just like they can say "you cannot use my app if you also have that other app installed", but they cannot without coming across as lazy assholes unwilling to properly maintain their software.

Thanks, I added an extra notice that it's the update that broke it. They only need to look at their vcs logs for that update to see where it went wrong. I have also given them a possible way to reproduce it. I'm making it as easy as possible for them to debug.
[G4 General] Azure1203:
Only issue I seem to have at 540 is in the Play Store the 'top developer' symbol is really big. Changing to 560 fix that?
[G4 General] phineous:
Sadly, no.
[G4 General] mrcrusha829:
Get Xposed and then install root cloak!
[G4 General] masze:
are'nt xposed bootlooping G4 still?
[G4 General] IIIIkoolaidIIII:
Root Cloak doesn't work for the apps I want to use that are blocked. Plus I don't want to have to keep adding mods to make things work, it just makes the system unstable. I'm looking at modding the build.prob in another way for now, but haven't yet found an adb way that works yet. Will keep hunting though.
[G4 General] Azure1203:
One other thing I've noticed at 540 is Facebook Messenger still has big icons and is a bit of a mess. Hardly ever use it though so no big deal. Otherwise 540 works great.
[G4 General] Azure1203:
Anyone having issues with swiftkey basically getting screwed up if you change the DPI? I originally had it working at 540, then did a factory reset to try and fix the touchscreen issues, and now setting it to 540 everything is normal except for SwiftKey.
[G4 General] IIIIkoolaidIIII:
See comments above dude, already been discussed. No solution as yet.
[G4 General] KnifeFed:
1440x2560@5.5" = 534.04 PPI. I've been running at 534 PPI since day one and everything has been working great, including SwiftKey.
[G4 General] IIIIkoolaidIIII:
Will give it a go now.

Edit

Tried it and still issues with SwiftKey, so guess your on old version of SwiftKey then.
[G4 General] Azure1203:
Doesn't work for me either using Swiftkey.

:/
[G4 General] KnifeFed:
How are you setting it? I'm using Texdroider. My SwiftKey version is 5.3.3.73.
[G4 General] IIIIkoolaidIIII:
Well then you have root, the issue is with setting it via adb and not having root.
[G4 General] KnifeFed:
Ah yes, you need root for it to work properly. I thought this was already established, sorry.
[G4 General] IIIIkoolaidIIII:
If you'd read through you'd see it was and that altering via adb without root is what we're trying to achieve with everything work well.
[G4 General] ExTREmE99:
thank god for apk mirror. for those who ran into this, here's the version you need: 5.3.2.67 from June 25th

http://www.apkmirror.com/apk/swiftk...ftkey-keyboard-5-3-2-67-android-apk-download/
[G4 General] Azure1203:
I can confirm that this apk works. Thanks man! Set DPI to 540.
[G4 General] IIIIkoolaidIIII:
Aye so glad for app mirror been such a savior many times. BACK to 540 dpi with old SwiftKey, it's going to big me having the update sitting there though lol

---------- Post added at 12:46 AM ---------- Previous post was at 12:01 AM ----------

A quick FYI the latest SwiftKey Keyboard 5.3.4.58 didn't fix the issue so over sized.
[G4 General] Cor-master:
The dpi is definitely all screwed up on this phone. My nav buttons are bigger than my nexus 7!
[G4 General] :
Changed to 540 on my b815eur variant all seems to work just fine.
[G4 General] djkinetic:
Anyone know how to disable this, it seems that using this command locks the density to whatever it is set, regardless of the build.prop. Now that we have root on all variants using the build.prop would be more advantageous, unfortunately if you used ADB the density is locked to the value you set in ABD regardless of the value in the build.prop. I tried to set to 640 with the adb command, and change to 500 in the build.prop but no lucky it stays locked at 640. So I'm looking for a way to completely disable this via adb.

Found the command its adb shell wm density reset
[G4 General] jaxon5115:
It Worked!

Thank You, I thought I was not going to be able to fix this, you are my savior.
[G4 General] davdavo:
Hi Guys,

I don't have root, but the adb method didn't work for me with error: device '(null)' not found . Can you help? Why is that? Cheers,

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell wm density 600 && adb

reboot

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device '(null)' not found
[G4 General] geoff5093:
I used texdroider_dpi to change the DPI to 540. Rebooted and have no issues, love the screen real estate! Camera, SwiftKey, and every other app so far is working great.
[G4 General] frmorrison:
Editing the density in Build.prop with Rom Toolbox was easy. I ended up with a DPI of 600. 540 works fine, but I sort of like the large icons from the default 640, so I picked halfway.
[G4 General] xbayyx:
Yeah I chose 600 as well. 540 Just seems way too tiny for my taste
[G4 General] ctstalin:
Got a optimising android bootloop after setting it to 540 :(
[G4 General] Lightshield:
I just used Texdroider_DPI with my rooted Verizon G4. Set it to 540 and so far no issues at all using Nova. SwiftKey, Lockscreen icons and Camera are all working fine. Thanks guys!
[G4 General] DjCalvin:
As did I. Ended up having to KDZ back to 11A.

I backed up my build.prop file, bu wasn't able to get root from adb while it was optimizing.

Fac reset didnt help either.

Side note: I had changed via wm density to 540 before root, but swiftkey was HUGE. reset back to 640, then went the build.prop route..

Will try again though.
[G4 General] Azure1203:
Any idea if the latest Swiftkey update screws everything up for those of us who haven't rooted yet?
[G4 General] Snakecharmed:
There was a SwiftKey update today (July 30), but I don't know whether the update fixed any DPI scaling issues with the previous version.

You really have to be rooted for DPI changes to go smoothly though. I used texdroider_dpi and changing from stock to 540 was painless. No optimizing dialogs, no boot loops. Everything works and looks fine except for a couple of LG's stock widgets I've been using: Clock 5x2 and Music 5x1.

Clock 5x2 now shows the other time zones I had set in my world clock, which I don't want to see on the home screen. I replaced that with DIGI Clock Widget from Forestree in the Play Store. Music 5x1 now has a large solid bar that's the white/blue inverse of the rest of the widget's background at the right side of the widget, but it's not a usability issue. It just looks a little odd.

SwiftKey, Camera, lock screen icons, and all other apps I've tried so far are working normally. The increased screen real estate is great, especially when it comes to browsing mobile sites. At 540, the mobile web on this phone no longer looks like it was optimized for your grandparents.
[G4 General] FPtje:
I really hate that you can't go far below 540 even with root and build.prop
[G4 General] Usraek:
I have a setting of 534 DPI using textdroider with no crashing/problems, and in Settings->Display you can choose a system font size, which helps a bit. I'm using 'small' and be sure to reboot after choosing.

I can't wait for Xposed though, as I want per-app DPI!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] RoryHa:
So I have a Nexus 5 that's screen is dying for the second time and I'm considering my options including a replacement phone. The Z3c is obviously a great spec phone and nicely built... I'm attracted to it by it sensible size also. The Nexus 5 I'm coming from is about the limit of size I'm willing to go. However I'm afraid of moving from the open world of easily being able to install custom ROM's and do whatever I like to the phone. I've read up on what's involved in doing this on the Z3c but I still have some reservations:

How stable are the ROM's available for the Z3c, I'm really just interested in a close to stock ROM with bloatware removed, I'n not looking for experimental features/customisations. I've used Cyanogenmod before on another device, and other ROMs and there always seemed to be something that never worked quite as well as the stock ROM. (CM had bluetooth problems for me)

If you go the route of unlocking the bootloader, are the DRM protected features that are lost deal-breaking? Is it possible to achieve what I want (clean ROM, root) without unlocking the bootloader?

Thanks for your help in advance!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] sfrique:
I am facing prettu much the same problem...

But i am moving away from a lg g2. ( it does not have the best custom rom support, but it works)

Anyway, i am willing to give a shot to the stock sony android... because of the DRM keys..

Well.. lets see what the people have to say!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Dsteppa:
1: The Roms here are really stable and most of them are close to stock Roms so you won't have to worry about that, since most of them are near stock Roms you won't have to worry about the stability either.

2: Only you can judge if you're going to miss the DRM features, I didn't and still don't I couldn't wait for root, so I unlocked my BL and I never regretted my choice.

The only downside to this phone is the camera in my opinion, so gather some info about the camera first.

When unlocking the BL you also lose some camera quality (only really noticeable in low light conditions tho).

See my topic (in sig) for pictures).

And you don't have to unlock your BL at all if you don't want to, only if you want to use another Kernel.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] RoryHa:
Thanks for the info

I had a look at the photo there and they are not as good as I thought the camera is.. still they are not bad. The Nexus 5 I currently have is not amazing either so it's not really a deal breaker for me. It seems to be the one thing all non-flagship phones compromise on is the quality of the camera.
[LG G Flex] Monster__Addict:
i wake the phone from standby and there are black bars running across the display in portrat, then in about 4 seconds the bars are gone..it happens every time, any clue why?
[LG G Flex] ahmed banna:
Can you send photos
[General Questions and Answers] jayram1408:
I have had a few people get down on me because i feel if someone has a answer, and they put more time and energy into telling you all the reasons why they shouldn't/can't help. It just seems down right mean. I thought these forums were a place of sharing and learning to help one and another. It just seems like it is becoming less of that as time progresses. not everyone here is a "Phone wiz" and that's why they come, seeking knowledge. So what if the question has been answered already? XDA is not a small web site in its infancy anymore. It has a lot of information to surf thru. All I am saying is you know the answer is a simple do this, or see this post would be great, instead of google it, or you need to look harder. Are people that full of themselves that they are to above everyone to help some noob out? Everyone was a noob at some point. My point is lets try to help each other instead of help ourselves only. There is a good saying I once heard, "watch who you step on , on your way to the top, because they won't be there to catch you when you fall". :highfive:
[General Questions and Answers] Darth:
Many people help on this site.... All the time and everywhere. But the ones who find help easy are the ones who also try to to help themselves first. They research, search and do their best to find answers...and then they ask for help when they're stumped.

The ones that have trouble getting help, are the ones who log in...find a thread or make one, reading nothing, searching for nothing and ask for help.

XDA is about learning, and sharing work... It's not a quick stop tech support help desk. If someone can't put in an effort to read, read... And read some more before they decide to start messing with their expensive device... Then this is not the hobby for them.

Most experienced members can spot the difference quickly between the types I've mentioned, and they interact accordingly.

Also, the site has rules... And one particular rule is not followed as often as it should be unfortunately...... That would be rule number 1: Search before posting.

And so... I'm going to close this thread now, because I can guarantee this will not be a constructive discussion. :good:

Regards,

Darth

Forum Moderator
[Android Q&A, Help & Troubleshooting] QA Bot:
Q&A for [DEV] [RK30SDK/RK3066] Zedupad - ischool

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [DEV] [RK30SDK/RK3066] Zedupad - ischool. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Networking] Syquus:
First of all, thanks to readers. You'll end this post tired of me, but i'd be happy if you can!

directly to the party: I have an SPV M600 from Orange Spain (known here as Prophet) SIM unlocked.

It's a G4 model.

My "numbers" actually, are:

IPL/SPL: 2.21.0001

GSM: 2.61.21 (not last, previous, i tried with all available since 2.0x)

OS: 4.0.0.0 (WM6 PDA VIET 4.0.0.0.4)

My first uses with my prophet when i bought it, it didnt work PROPERLY (wifi) but at least (

sometimes

) detected wifis (when SSID broadcast was enabled on AP devices). Other times, it didnt detect nothing, but using manual configuraion of Wireless network, worked.

Since i upgraded to WM6 (so many different versions, searching for the one that matches my requisites), Bluetooth & Wifi have died.

I couldn't enable Bluetooth or Wireless on my prophet (

both at the same time

, strange!). When it boots (from a soft reset) it has ALWAYS the Bluetooth (on CommManager) as enabled(but doesnt work really). I can "disable" (remember its "enabled, but really is no working, so disabled internally) it, and then if i click on BT button again, nothings happen. It can't be enabled again unless I make a soft reset.

Explanation animation​

Well. In this point, i'vent tried nothing, so Lets go to Bluetooth - Add new device. What do i got? Problem with Bluetooth Hardware.

Explanation animation
​

So at this time,

Bluetooth died.

So lets go back to my Wifi troubles:

I can "enable" it on CommManager. And (as BT) sometimes icons changes to enabled (and the antena on upper taskbar appears)

sometimes not.

If BT icon is lighting, then i can't enable Wifi. If wifi is enabled, i cant enable BT (well, really, it doesn't depend on wifi. remember BT can't be "enabled" unless i've restarted from a soft reset).

An example after touching BT icon, of how "WLAN" kick my ass:

Explanation animation.​

Just take a sight on some other info regarding to my xda:

Other settings.​

IS THERE ANYTHING SUSPICIOUS?

Things i've tried:

Change GSM/Radio ROM: All availables tried. Some strange changes in Connections panel: early versions: WLAN icon. Newer version: Wi-Fi & WLAN icons. what for?

Other WM6 roms:

PDAViet 1.0

PDAViet 1.1

PDAViet 1.1 modified with some CommManager fixes from Franlov (great Spanish cooker).

Original Qtek 2.20.736 Rom.

ASERG 3.09

"Step1" PDAViet rom. As it was WM5, i tried to make work bt or wifi.No success

Always well done, guided by cooker instructions. Hard Resets always done after flashing, etc

Maybe there is something in my operator rom (cid locked!) that could create conflicts?

I'm really sad about this trouble. Because i'm 99% sure there isn't any HW problem related but i'm not able to solve it. This would be one of the few problems (tech related) that can beat me grr.

If someone gots any idea on what to do or what to test... help would be much appreciated.

Last step would be restore original Rom (test if it works... i don't think so) and send it to my operator to manage an RMA.

Note: Sorry for my english.
[Networking] nypra1314:
Hi,

I got exactly the same problems when I installed the new HTC Today plugin and AudioManager. Media Player backgrounds and windows cluthered together, only 5 seconds of every song is playing.

Yesterday I did a hard reset and everything is back to normal now, only no new Audio Manager. :(

Qtek S200

WM5
[Networking] asosa1414:
I have the same problem in Spain With an M600 from orange.

But also I cant use the phone. It does not find any network.

If find a Rom working fine with this please tell me where

BEst regards
[Networking] gompie99:
i have the same problem with the nbd v7.4 not with the wm6 business edition.

So i think its a software problem.

Anyone a solution?
[Networking] Syquus:
Hello again. I've solved my problem: Buy a new Prophet :D .

Other one was broken. Maybe because of a failed flashing stage (i remember some errors...).

Now i've it working perfetcly. No misfunction. BT or wifi can work correctly. I've upgraded OS Rom without any problem.

Note: I have NOT upgraded Radio ROM. I've read there are people with problems when upgrading to latest versions. For example i remember two guys that had problems with their prophet when using a RadioRom newer than x.19.x

That is my version, and i repeat, IF:

Same Prophet User

Same knowledges

Same software (programs & OS rom)

Different Prophet <---------- The problem was Hardware!

Maybe software conflicts can cause same issues than my first post in this thread. Mine was a HW problem.

Good luck guys.
[Networking] Noonski:
Not HW problem

This doesn't seem to be a hardware problem. But i do like you homescreen background where did you get it or IAW, do you have it for me at PM?
[Networking] Syquus:
For sure: It was a hardware problem. (If you understand an unstable rom memory as Software, ok, then it's software). I dunno understand "IAW"....

Cheers
[Networking] xetro:
Same for me with PDAVIET 4.0.0.0.6

I dont think it is a HW problem because somtimes WIFI works, sometimes it plays dead with me :(

BT stays dead with the PDAVIET 4.0.0.0.6 ROM :'(

Tried a lot, so some help would be great !!

By the way, it has the 6 button HTC_Home_Plugin and 8 button comm manager, maybe changing that can help?
[Networking] Syquus:
Hear me: Change your prophet ;)
[Xiaomi Mi 4i] 111kaustav111:
Simple question , does our device support native USB MHL for HDMI screencasting? Can anyone confirm. How can it be tested ?

Thanks
[Xiaomi Mi 4i] ck41:
Nope . I have already tested it but it's not working.
[XDA Assist] xerxed:
GUYS PLEASE HELP !! I unlocked my bootloader using fast boot and It showed success then when I turned on my phone it was stuck on xperia waves . Then I read it on many of the threads to flash the stock rom using flash tool to repair the problem but the flash tool showing

04/033/2015 14:33:37 - INFO - Selected Bundle for Sony Xperia M (C1905). FW release : 15.4.A.1.9. Customization : CE

04/033/2015 14:33:37 - INFO - Preparing files for flashing

04/033/2015 14:33:37 - ERROR - invalid LOC header (bad signature)

04/033/2015 14:33:37 - INFO - Cannot open bundle. Flash operation canceled

im not getting what to do please help me revive my phone .
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. Try asking here, http://xdaforums.com/xperia-m They are the experts on your device. Also see this, http://xdaforums.com/showthread.php?t=2484622
[XDA Assist] xerxed:
Dit it by myslef .. Still thanks.

Thanks but solved it by flashing rom from other source and keeping in mind of my model that was C1904 and the loc header vanished.
[XDA Assist] jd1639:
Great! Glad you got it fixed. I'll close this thread.
[XDA Assist] rubenyjoana:
Hello everyone I have a problem with my s4 I explain . buy 2 broken s4 one screen and a motherboard to assemble all paracio going well but then I realized that if I'm in a place where there is little sign the lost completely out strikethrough circle and there is no network or data I tested many things and I can not find the solution. I've changed the antenna and cable. versoin returned it to 4.4.2 because when lit it asked me to upgrade to 5.0.1 I've gotten several modems and no longer that I'm going crazy acer please aver if someone can help me. thanks
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. See if someone in this forum can help you, i9505 They are the experts on your device. Specifically start here, http://xdaforums.com/showthread.php?t=2192886
[XDA Assist] rubenyjoana:
I do not understand English

thank you for answering the problem is not English . then it costs me muxo find a solution so that there comes that go with the google translator if I could turn alguen particular solution would greatly appreciate it . thanks :D
[XDA Assist] jd1639:
See the link I gave you and ask for help there.
[Galaxy S 4 Q&A, Help & Troubleshooting] parksy87:
I'm new to the whole custom rom scene so far have tried cyanogen mod and wasn't happy with the battery life, so have tried imperium rom, and I'm happy with it other than the fact I can't set a pin on it, I can only lock it using a pattern.

If I try and set a pin it either doesn't recognise it's been set and just unlocks the phone as normal or it unmounts the sd card. I'm sure I read about updating the boot loader solving it, and this may sound like a silly question, but is that not part of the custom rom anyway? If not how do I go about updating just that?
[Micromax Canvas Turbo A250] simplyme2908:
Hello everybody, I have a canvas turbo a250 when I was trying to extend system partitions it got bricked. I request the help of anybody kind enough to give a tutorial on how I can recover it.

Thanks in advance
[Micromax Canvas Turbo A250] Appy013:
flash stock v5 rom by SP flash tool, full method is given on a thread named Micromax Canvas Turbo Stock V5 ROM
[Micromax Canvas Turbo A250] simplyme2908:
Link?
[Micromax Canvas Turbo A250] Appy013:
Link

[URL = http://xdaforums.com/canvas-turbo/development/micromax-canvas-turbo-stock-v5-rom-t3096768] Click Here[/URL]
[Micromax Canvas Turbo A250] simplyme2908:
Couldn't recover it thanks for ur help anyays
[Micromax Canvas Turbo A250] Appy013:
really you couldnt recover, msg me on whats app for more....
[Micromax Canvas Turbo A250] simplyme2908:
Number?
[XDA Assist] sai prakash:
Actually i wanted to update my phone by installing custom rom.For that i downloaded custom rom from xda developers website and the comments even good about working.After that i have rooted my phone using framaroot then downloaded apps like rom manager and twrp manager.Even using these apps didn't help me to get recovery mode in special way, it is coming in natural stock recovery mode.After that using rom manager app,i choose 'install zip file from sd card' option while the recovery is set to the twrp recovery mode and then i chose to begin the installation.Suddenly the phone got light off on screen and i thought that it is going to recovery mode but even after 2 hours there is nothing new coming on screen.I realized my phone got hard bricked,it is not getting into any recovery mode or download mode with combination buttons.I tried with odin to install stock firmware but the problem is it is strucking at 'setup connection' stage and gets fail.Please tell me what to do now?(my phone has only software warranty not hardware warranty now)
[XDA Assist] jd1639:
What device are we talking about?
[Samsung Gear S] leoles2171:
Please Help?
[XDA Assist] XDA Visitor:
My note's exynos should have a 4 arm cortex-a15 @ 1.90 GHz & a 4 arm cortex-a7 @ 1.30 GHz but my cortex-a7 has somehow been overclocked to 1.90 GHz and the cluster switch between these two has stopped and because of this i think all the cores run at the same time and my tablet over heats and runs out of battery very quick . what should i do ? please help