Develop Bugs

Temperature hacks on the Tab (battery, and the other sensor)

First of all, I needed SetCPU to detect the battery temperature on my overclocked Galaxy Tab (to switch profile when overheating), so I modified my home-brewed kernel with this small patch:
http://forum.xda-developers.com/showthread.php?p=11454036#post11454036
This is fine, but on my JMI ROM (even with the correct /system/lib/hw/sensors.default.so library), applications like "SensorTest" were not displaying the temperature from the AK8973B sensor. I found a way to fix this.
Basically, I compiled this open-source driver (or alternatively, this one), which provides a custom sensors.default.so library and akmd service executable. The former is actually not needed, only the latter needs to be run on the Tab (because the standard /dev/akm8973_daemon device node is used, via ioctl to update the /dev/input values for compass, etc.).
First, I stopped the default /system/bin/akmd2 service. I then launched the custom akm daemon, which showed wrongly-calibrated values for the compass and orientation sensors (because I entered random digital and analog gain values), but the correct temperature was displayed (actually higher than the battery one !). I then stopped akmd, and re-launched akmd2...and magic: the temperature is now picked-up correctly !
Note that the gyroscope and accelerometer sensors are *not* affected these AKM modifications (they are effectively different hardware, with different drivers). The ambient light and proximity sensors are also different hardware (the latter isn't enabled on the Tab, by the way...I suspect we need to compile/install a driver for it).
I will do more testing with akmd and akmd2, and I will probably modify my init.rc to launch the service accordingly (in my custom initramfs).
I hope this helps.
Cheers, Dan
--- EDIT ---
Mhmmm, here's an interesting update:
There is no need to compile the open-source AKM daemon ! Instead, you just need to kill the /system/bin/akmd2 process, and restart it.
Well, actually it's not that simple: it only really works when the temperature sensor is polled (for example, when the SensorTest or Elixir app is displaying current values). Oh, and the temperature sensor only spits-out results when the compass sensor is also polled at the same time ! (Elixir is useful to test this, because sensors can be selectively activated)
I tried to reverse-engineer the values coming out of /dev/input/event4 (which corresponds to the compass sensor, as shown by the getevent command). I used shell commands similar to that (note the automatic conversion from hexadecimal to decimal values):
Code:
getevent | grep "/dev/input/event4:" | sed 's/ffffff//g' | awk '{print $2 " " $3 " " ("0x"$4)+0 ">" $4}'
Unfortunately my time ran out before I could make sense out the stream of values.
By the way, here is the script I used to stop+restart the AKM daemon in init.d/ :
Code:
get_akmd_pid()
{
ps -w | grep akmd2 | grep -v grep | awk '{print $1}'
}
pid=`get_akmd_pid`
echo "Killing /system/bin/akmd2 (PID: ${pid}) ..."
kill -9 $pid
pid=`get_akmd_pid`
echo "Checking that /system/bin/akmd2 process has been terminated: now PID = [${pid}] (should be empty)"
echo "Restarting /system/bin/akmd2..."
/system/bin/akmd2 &
pid=`get_akmd_pid`
echo "Checking that /system/bin/akmd2 process has been restarted: now PID = [${pid}] (should NOT be empty)"

What temperature do you consider too hot on your tab? I currently have my set to underclock from 1.4 ghz to 800 mhz whenever it reaches 90 degrees Fahrenheit (I am a worry-wart), but it reaches that a lot, so I was wondering what you have the maximum temperature set to before you bring the clock speed down.
Thanks

caveman999 said:
What temperature do you consider too hot on your tab?
Click to expand...
Click to collapse
I'm not sure yet. The battery temperature is lower than the one indicated by the AK8973 sensor. As it stands, SetCPU switches profiles based on the battery temperature, so personally I use conservative values (at the moment, 35 degrees Celcius).
By the way, the original post has been updated to reflect new findings.
Cheers, Daniel

my temp sensor is stuck at 30 c after flashing a kernel how do i get it to work. what you posted did not work. im actually stuck in a boot loop

nev310 said:
my temp sensor is stuck at 30 c after flashing a kernel how do i get it to work. what you posted did not work. im actually stuck in a boot loop
Click to expand...
Click to collapse
Same here, stuck on 30 degrees C. Any fix would be appreciated.

Any updates on this

Utilising the Adreno130 Graphics on the Hero

So as it says i wish to utilise the Adreno130 graphics like the legend utilises the adreno200
Taken from egl.cfg (Legend [Adreno200] )
Code:
# One line per configuration, of the form:
#
# D I TAG
#
# D: display (0: default)
# I: implementation (0: software, 1: hardware)
# TAG: a unique tag
#
# The library name loaded by EGL is constructed as (in that order):
#
# /system/lib/egl/libGLES_$TAG.so
# /system/lib/egl/lib{EGL|GLESv1_CM|GLESv2}_$TAG.so
#
0 0 android
0 1 adreno200
As you can see it uses a cfg to use the adreno200, Is there no way of changing it and the drivers so the hero does the same?? Im no developer so i really need help!

Nearly 500 views and not a single comment....Im beggining to think this should go in Development

bonesy said:
Nearly 500 views and not a single comment....Im beggining to think this should go in Development
Click to expand...
Click to collapse
only edit egl.cfg
Code:
0 0 android
0 1 qcom
to
Code:
0 0 android
0 1 adreno130
EDIT: Then you definitely must add adreno files also

Note that the differences between 200 and 130 can be quite large.
While 200 is considered as a separate GPU unit, the 130 is integrated into the CPU I believe.
While legend and newer uses KGSL for rendering triangles, we unfortunately still use hw3d. I believe this is due the GPU/integrated differences.
Maybe it is of any help...

Should this improve the gfx performance on our Heros?

Ooh it got moved! Thanks!
I think it may speed up a little but now im thinking the drivers will have to be made,
dont think it'll be easy...
Ill search through other Adreno 130 device rom's to see if i can find one that already uses them
...EDIT...
Adreno 200
A quantum leap in graphics quality from the OpenGL-Es 1.x, the Adreno 200 GPU has a unified shader architecture that makes maximum use of its graphics processing power. Developers can use this GPU to implement high-end effects that were previously impossible.
Dont think it will be possible after looking on the qdevnet site

bonesy after reading your thread I thought I would check this out a little and stumbled upon a thread over at simply android. looks like some devs working on the moto cliq had the same idea as you and they have been trying to contact qualcomm about this, doesn't look too promising at the moment but they are trying so maybe something will come out of it.
http://www.simply-android.com/discussion/833/mod-opengl-es-1.1-for-motorola-cliq/p9

Thanks for that, i will keep an eye there i managed to currupt my HD last night so it may take me a while to get back all the stuff..Hopefully they will have has a response by then!

Adjusting the "Touch Slop" in CM9 (from 8 to 16)

I responded in the larger CM9 thread but it will probably be buried in a day or so. And I think this will help devs who are working on CM9 builds at the moment.
------------------------------------------------------------------
jdommer said:
The correct settings for the our touch screen appear to be:
Code:
touch.deviceType = touchScreen
touch.orientationAware = 1
# Size
# Based on empirical measurements, we estimate the size of the contact
# using size = sqrt(area) * 28 + 0.
touch.size.calibration = default
touch.size.scale = 1
touch.size.bias = 0
touch.size.isSummed = 0
# Pressure
# Driver reports signal strength as pressure.
#
# A normal index finger touch typically registers about 80 signal strength
# units although we don't expect these values to be accurate.
touch.pressure.calibration = none
touch.pressure.scale = 1.0
# Orientation
touch.orientation.calibration = default
Unfortunately, that doesn't do anything for the tap/drag problem. The KF can't distinguish pressure or size of touch.
Looks like Android decides any touch where x1-x2 or y1-y2 > 8 as a drag. I can't find any place that that value is configurable after scouring the internets all morning, but if it could simply be turned up to maybe 12 that would probably alleviate 90% of our taps as drags problems.
Anyone have any idea, is there a config file or is that compiled in and has to be changed at source? I feel competent enough to dink with config files, but can't compile crap.
Click to expand...
Click to collapse
I build from the KFire-Android git as a testing model and i've been experimenting with a setting of "16" for touch slop, and in my opinion it's working much better.. could probably be 12, but who knows. I'm having a much easier time selecting things like Beautiful Widgets 1x1 Toggles, where before it was a trial of patience and about 10 touches.
This is a setting in the overlay config.xml file. I went ahead and committed it this morning to the KFire-Android org at Github:
https://github.com/KFire-Android/device-amazon-otter/commit/56b3d52fe6c645a18e60ab765e5b9831cb6a0663

Is the code that uses the clickSlop in android hackable for KFire?
I found on my device that most of the noise on taps was occurring in the last few samples (like the touchscreen firmware is averaging in some bad samples on finger release) and that by dropping the last few touch events I got much better touch response in my app. I'm not sure where to put such a state machine in the framework, though, or how to have it only for KFire...
(My state machine would buffer 3 samples ahead for the first 20 samples, and then drop the last 3 samples on finger up and patch N-3 to be a finger up instead of a move -- after 20 samples it just passed everything through with no buffering to avoid adding latency to drags).

[ROM][28 August] Virtuous Infinity 1.35.0 Is Out! [FULL Sense 4+Working Camera!]

Note: I am not a developer. I am merely informing the community about this rom. I take no credit for this rom. All credits for this rom go to the Virtuous Team for such an amazing rom I will post updates as the rom gets updated
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Virtuous Infinity
We are pleased to announce the first release of Virtuous Infinity.This ROM is the first ever which brings the full Sense 4 experience to your favorite WVGA device.Thanks to great effort of our M10 team (including Cypis, Diamondback and Flemmard) we finally cracked the new m10 format to bring you the lastest HTC software!It is based on the 1.11.401.110 release RUU of VilleC2. We would like to give special thanks to Football for the RUU.This build currently is a X-Series release, however, it is suitable for use as a daily driver if you can live with a few minor bugs.We hope to have the ROM feature complete as soon possible. Check bellow for a full list of what is working and what is not.
Primo is the result of a collaborative, team effort by the following developers:
Flemmard
Diamondback
rmk
chrisch
mdj
seo
eViL_Dee
cypis
cjward
tbalden
Features
Based on the VilleC2 ROM (1.11.401.110).
"Full" Sense 4 resized for WVGA resolution
Tweaks app build with latest HTC SDK 15
Fully Deodexed
Ported for almost full functionality on all of supported devices
Heavily optimized for fluid performance and usability.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Working
Camera
HW Acceleration
WiFi
Bluetooth
Mobile Data, SMS, MMS & Voice Calls
GPS
Sensors
Audio
USB Storgage (No 3rd Party App Required)
FM Radio
Not Working
Rosie: Folder isn't perfectly resized in landscape
Rosie: Mail widget is force closing
Weather: Weather animation in landscape mode broken
Weather :Full screen weather animation broken
Camera: Not all effects are working
You tell us
Screenshots:
Devices Supported:
Desire Z / G2
Desire HD
Inspire 4G
My Touch 4G
Desire S
Incredible S
My Touch 4G Slide
Incredible 2
Credits and Acknowledgements
Virtuous Team - For an amazing rom
Bangincrazy – For testing on MT4G
lowveld – For pointing us in the right direction to fix WiFi
Football – For the RUU
xvicdice – For music playback fix
Download Link:Bug Tracker​

Since you made a link here I'll go ahead and attach some stuff.
Wifi, Data, Music Player working.
Camera works rather nicely in both default app and third party apps (instagram etc)
Attached are some screen shot with the default camera app, actually doing special effects smoothly in live preview.
It's a bit slow, especially if you're multitasking, but I'm impressed with how far they got with the camera.
When initially setting up, the setup stage can seem painfully slow (i.e.: on screen keyboard taking a sec or two to register a key, or the next/confirm dialog taking just as long).
Also wake by trackpad doesn't work even though the option is there.
The power menu requires a longer than normal long-press to activate (noticed this when getting the screenshots).
Also Infinity appears to install some apps to the SD Card via it's own custom folder (screen shot also attached).
by the way in terms of 'not all effects', I haven't come across a single effect on the list of effects that didn't seem to crash (maybe not rendered, but didn't die either).

I've switched back to EliteMod in the meantime (normal working hours have approached), I haven't had much time to test extensively how multitasking behaves (i.e.: Facebook, twitter, etc) or any graphical type of games etc.
The free ram at just bout any time is around 10MB, and uptime showing loads around 5.0 on average. The launcher can lag a bit on redraw even if you got the device clocked to 1400mhz (I believe it's more a ram issue than anything, so between supercharger V6 and swap, it might be bearable.)
---------- Post added at 08:07 AM ---------- Previous post was at 08:05 AM ----------
Oh also adb connectivity is somewhat glitchy. Devices never showed up during the initial boot, and had to mess with the power menu a couple of times (between charge only, HTC sync, and disk) to get it to show up and be able to do stuff with adb shell. Switching between various USB modes tends to be laggy.
Though one nice thing about the preview is that I did not receive a single force close or crash, just lags, and some functionality not occurring at all (i.e.: trackpad wake, FM radio).

Desire HD (ace), Desire Z (vision), Inspire 4G bugs
When phone goes into sleep you need to make a long press of the power button to wake it up
Mic doesn't work in some apps like Voice Search, Soundhound, ...
Camera isn't working on some phones
Camcorder only works with disabling sound in the video settings

I have a funny feeling it's going to turn into a bit of a 'can you port Sense Camera to XXX ICS Rom?', when it was the other way around.

FM Radio appears to be broken on both the included FM app, and the FM Radio Widget.
Though fine with SpiritFM Free Edition (which of course requests root permission).
Also the stock FM Radio app, seems to never turn off, it's always "Turning Off", and when the dialog does go away, it's still "On" (showing the icon in the status bar)

How's video recording, 720p?
The above mention of 10MB of free RAM is scaring me away from trying it though. Hell with CM7 as soon as it hits 70MB's, I feel like its lagging too much.

Tried some games with this, with supercharger, swap and 1.4ghz o/c:
Temple Run: Without swap it closes immediately, with swap its getting huge lags while playing, but when theres no lags its smoother then previous kernels.
Death Rally: Smooth as s..t.
Helicopter 3D: Smooth as f..k.
these games rather heavy considering their 3d natures. so its a good thing that this rom can run them smoothly.
generally speaking, if you make this your dd, it will drive you crazy time to time because the interface is slower then most of the roms out there. hope it will get better tho.
edit: with swap and supercharge i get 100-120 mb free ram ( at least it shows that way on the task manager)

boost3d23 said:
How's video recording, 720p?
The above mention of 10MB of free RAM is scaring me away from trying it though. Hell with CM7 as soon as it hits 70MB's, I feel like its lagging too much.
Click to expand...
Click to collapse
I find this pretty common of just about every ICS rom though (mostly cached it would seem). i.e.: free ram is wasted ram.
I'll try out the video soon as TiB does some app restores (I kind of doubt it's full 720, but maybe it'll surprise me).
---------- Post added at 10:15 AM ---------- Previous post was at 10:13 AM ----------
By the way home screen lag ain't so bad once you replace HTC Sense with the Apex Launcher (though I guess some people want the whole experience )
---------- Post added at 10:24 AM ---------- Previous post was at 10:15 AM ----------
720p is Selectable (though 1080p is also shown, obviously won't record at that though), however when you finish recording and had audio turned on, it's the forever-saving-video issue.
With audio off... did saving video for a while, and then force closed, and also a very funky buffer issue (like the screen split in half and scrolled up while recording.
The result from both are files with thumbnails with exclamation marks.
Now if I set the Video quality to 800x480 Wide (default), and audio off, it saves fine.

I respect your work.I'm about to try.

Can't even get it working it lag badly after the setup and hot reboot more than 6 times =\ anyway,good job to them as they get the camera working make me looking forward for updates XD
Sent from my Desire Z using xda app-developers app

Steven How said:
Can't even get it working it lag badly after the setup and hot reboot more than 6 times =\
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
Would help if your hboot/radio/etc info was in your signature

kbeezie said:
Would help if your hboot/radio/etc info was in your signature
Click to expand...
Click to collapse
Ah...I forget abt radio and all those... does it effect the performance? And I'm using a Italian dz not g2
Sent from my Desire Z using xda app-developers app

Steven How said:
Ah...I forget abt radio and all those... does it effect the performance? And I'm using a Italian dz not g2
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
As long as it's a DZ hboot it should be fine (i.e.: because the G2 hboot only has a ~400MB /system which is way too small, as this preview takes up about 96% of /system on DZ hboot).
Also depending on what rom you're coming from (i.e.: /system, etc may still be formatted as ext3 instead of ext4).
And far as radio... I don't know if this requires 26.13.04.19 or equivalent.
I guess if you can attempt a logcat output, might be helpful to someone who knows how to read those things.

kbeezie said:
As long as it's a DZ hboot it should be fine (i.e.: because the G2 hboot only has a ~400MB /system which is way too small, as this preview takes up about 96% of /system on DZ hboot).
Also depending on what rom you're coming from (i.e.: /system, etc may still be formatted as ext3 instead of ext4).
And far as radio... I don't know if this requires 26.13.04.19 or equivalent.
I guess if you can attempt a logcat output, might be helpful to someone who knows how to read those things.
Click to expand...
Click to collapse
I'm using 4ext recovery and I only left 20mb in my system space..I have restore back to ARHD 6.3.3.. until infinity become more rock stable perhaps? hope so
Sent from my Desire Z using xda app-developers app

Steven How said:
I'm using 4ext recovery and I only left 20mb in my system space..I have restore back to ARHD 6.3.3.. until infinity become more rock stable perhaps? hope so
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
Hence why it NEEDs the DZ hboot
it is an alpha/preview
I enabled swap with this script http://dl.dropbox.com/u/1169731/swap_enabler.sh (ie: pop it on /data/local/tmp, chmod 775 , run it, reboot). So will see how SD-swap helps it.

I would remove some unesacary apps from the Rom to free up space
Sent from my HTC Sensation 4G using xda premium

I DO know how to enable swap lol, but it still lag badly.. after opening an app it hang there and finally reboot...lol I understand it's an alpha build so I'm not that demanding for the best performance for now
Sent from my Desire Z using xda app-developers app

evilcuber said:
I would remove some unesacary apps from the Rom to free up space
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Seems kind of pointless since the /system partition isn't normally going to change after installation. So removing those apps from /system doesn't really give you much benefits in 'freeing up space'. If it were on /data/app that'd be a different story, but it's pretty light in that department upon start.
Now you *could* disable some system apps (if it won't break anything) to improve some degree of performance, but then again what would be the point of testing/previewing if you didn't take it as is.
---------- Post added at 11:26 AM ---------- Previous post was at 11:15 AM ----------
So with 128MB swap on, overall it does seem smoother. However for any *new* item, there can be occasional freezes for a few seconds, in which time I'll notice the swap usage (via adb shell) will jump 20-30MB at a time, eventually once the phone has unfrozen it'll be quite smooth after that. In the last 3 freezes I've jumped from about 30MB to 60MB to 96MB.
Right now it's down to 87MB after about a minute since the last freeze (added a power widget to the desktop, taped the brightness, froze for about 15-20 seconds, changed the brightness, was smooth after that).
Also I'm not using the launcher that came with it, but rather Apex Pro and fancy widgets.
current memory usage, uptime and top:
Code:
[email protected]:/ # free
total used free shared buffers
Mem: 370420 360300 10120 0 600
-/+ buffers: 359700 10720
Swap: 131580 88232 43348
[email protected]:/ # uptime
15:25:04 up 34 min, load average: 2.69, 3.22, 3.40
Code:
Mem: 360772K used, 9648K free, 0K shrd, 1020K buff, 57144K cached
CPU0: 5.7% usr 5.7% sys 0.0% nic 88.4% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.18 2.93 3.29 2/680 8348
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
316 104 1000 S 425m117.2 0 2.3 com.android.systemui
209 104 1000 S 403m111.3 0 1.1 system_server
7173 104 10148 S 378m104.5 0 0.0 com.facebook.katana
421 104 10165 S 373m103.0 0 0.0 com.anddoes.launcher
467 104 10141 S 372m102.7 0 0.0 com.htc.idlescreen.shortcut
513 104 10018 S 351m 97.0 0 0.0 android.process.acore
3783 104 10017 S 334m 92.2 0 1.1 com.google.process.gapps
501 104 1001 S 329m 91.0 0 2.3 com.android.phone
760 104 9999 S 322m 89.0 0 0.0 com.htc.launcher
7847 104 1000 S 313m 86.4 0 0.0 com.android.settings:remote
1323 104 10018 S 310m 85.6 0 0.0 com.android.htccontacts
482 104 10163 S 310m 85.5 0 0.0 com.touchtype.swiftkey
7394 104 10106 S 309m 85.3 0 0.0 com.android.mms
7882 104 10017 S 301m 83.0 0 0.0 com.google.android.gsf.login
8235 104 10014 S 301m 83.0 0 0.0 com.htc.calendar
8192 104 10014 S 301m 83.0 0 0.0 com.htc.bg
8163 104 9996 S 300m 82.9 0 0.0 com.htc.notes
7862 104 10153 S 300m 82.8 0 0.0 com.google.android.googlequicksear
8214 104 10146 S 300m 82.7 0 0.0 com.dropbox.android
5568 104 10162 S 298m 82.3 0 0.0 com.mhuang.overclocking.ProfilesSe

kbeezie said:
Seems kind of pointless since the /system partition isn't normally going to change after installation. So removing those apps from /system doesn't really give you much benefits in 'freeing up space'. If it were on /data/app that'd be a different story, but it's pretty light in that department upon start.
Now you *could* disable some system apps (if it won't break anything) to improve some degree of performance, but then again what would be the point of testing/previewing if you didn't take it as is.
---------- Post added at 11:26 AM ---------- Previous post was at 11:15 AM ----------
So with 128MB swap on, overall it does seem smoother. However for any *new* item, there can be occasional freezes for a few seconds, in which time I'll notice the swap usage (via adb shell) will jump 20-30MB at a time, eventually once the phone has unfrozen it'll be quite smooth after that. In the last 3 freezes I've jumped from about 30MB to 60MB to 96MB.
Right now it's down to 87MB after about a minute since the last freeze (added a power widget to the desktop, taped the brightness, froze for about 15-20 seconds, changed the brightness, was smooth after that).
Also I'm not using the launcher that came with it, but rather Apex Pro and fancy widgets.
current memory usage, uptime and top:
Code:
[email protected]:/ # free
total used free shared buffers
Mem: 370420 360300 10120 0 600
-/+ buffers: 359700 10720
Swap: 131580 88232 43348
[email protected]:/ # uptime
15:25:04 up 34 min, load average: 2.69, 3.22, 3.40
Code:
Mem: 360772K used, 9648K free, 0K shrd, 1020K buff, 57144K cached
CPU0: 5.7% usr 5.7% sys 0.0% nic 88.4% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.18 2.93 3.29 2/680 8348
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
316 104 1000 S 425m117.2 0 2.3 com.android.systemui
209 104 1000 S 403m111.3 0 1.1 system_server
7173 104 10148 S 378m104.5 0 0.0 com.facebook.katana
421 104 10165 S 373m103.0 0 0.0 com.anddoes.launcher
467 104 10141 S 372m102.7 0 0.0 com.htc.idlescreen.shortcut
513 104 10018 S 351m 97.0 0 0.0 android.process.acore
3783 104 10017 S 334m 92.2 0 1.1 com.google.process.gapps
501 104 1001 S 329m 91.0 0 2.3 com.android.phone
760 104 9999 S 322m 89.0 0 0.0 com.htc.launcher
7847 104 1000 S 313m 86.4 0 0.0 com.android.settings:remote
1323 104 10018 S 310m 85.6 0 0.0 com.android.htccontacts
482 104 10163 S 310m 85.5 0 0.0 com.touchtype.swiftkey
7394 104 10106 S 309m 85.3 0 0.0 com.android.mms
7882 104 10017 S 301m 83.0 0 0.0 com.google.android.gsf.login
8235 104 10014 S 301m 83.0 0 0.0 com.htc.calendar
8192 104 10014 S 301m 83.0 0 0.0 com.htc.bg
8163 104 9996 S 300m 82.9 0 0.0 com.htc.notes
7862 104 10153 S 300m 82.8 0 0.0 com.google.android.googlequicksear
8214 104 10146 S 300m 82.7 0 0.0 com.dropbox.android
5568 104 10162 S 298m 82.3 0 0.0 com.mhuang.overclocking.ProfilesSe
Click to expand...
Click to collapse
This rom didn't come with virtuous oc?
Sent from my Desire Z using xda app-developers app

[Q] ZE551ML LCD on a ZE550ML ?

I recently dropped my phone on concrete, the glass smashed, and was looking to fix it...
Just wanted to know if anyone knew if a:
ZE551ML display(1080p) can be put into a ZE550ML(720p) body?
They are running on the same chipset right? So do they basically have the same internals?
If I'm not mistaken you can buy a version of the ZE551ML that has the exact same specs as a ZE550ML with 16gb, 3gb, 1.8ghz but just with a 1080p display.
The only problem I could see was display drivers being incompatible but the ribbon cables look identical. Maybe like just installing different firmware would make my phone a ZE551ML, unless there are other hardware differences as well. Other than that I don't see why it wouldn't work.
Dunno, just wanted to know if anyone had tried it but I'm gonna try it anyway unless someone says it won't work.
Here's links to the completely display assembly:
http://www.parts4repair.com/complet...us-zenfone-2-ze551ml/#PhotoSwipe1435569358683
http://www.parts4repair.com/complet...us-zenfone-2-ze550ml/#PhotoSwipe1435569377968

I don't think anyone had tried that yet, given the phone had not been out for long. If you give it a try let us know.
Sent from my ASUS_Z00AD using Tapatalk

R3MaK3R said:
I recently dropped my phone on concrete, the glass smashed, and was looking to fix it...
Just wanted to know if anyone knew if a:
ZE551ML display(1080p) can be put into a ZE550ML(720p) body?
They are running on the same chipset right? So do they basically have the same internals?
If I'm not mistaken you can buy a version of the ZE551ML that has the exact same specs as a ZE550ML with 16gb, 3gb, 1.8ghz but just with a 1080p display.
The only problem I could see was display drivers being incompatible but the ribbon cables look identical. Maybe like just installing different firmware would make my phone a ZE551ML, unless there are other hardware differences as well. Other than that I don't see why it wouldn't work.
Dunno, just wanted to know if anyone had tried it but I'm gonna try it anyway unless someone says it won't work.
Here's links to the completely display assembly:
http://www.parts4repair.com/complet...us-zenfone-2-ze551ml/#PhotoSwipe1435569358683
http://www.parts4repair.com/complet...us-zenfone-2-ze550ml/#PhotoSwipe1435569377968
Click to expand...
Click to collapse
Did you ever tried this out? FULLHD screen on the ZE550ML?

So I got the screen a couple weeks ago, just got round to ordering the proper ZE550ML screen now.
To answer my own question, NO, this doesn't work. I just get weird half screen thing, assuming it has something to do with the phone only outputting 50% of the pixels and the screen just generally not being made for it.
Photos:
https://drive.google.com/folderview...ZQT2hMb3ExU0xSdE5sV2pQQUNGWFhyTk0&usp=sharing
ZE551ML display is NOT compatible with ZE550ML body as far as I have tested.
thread closed. (don't know how to close a thread)

Good to know
Sent from my ASUS_Z00AD using Tapatalk

Did you change the DPI? You should try, I think you can use the full hd screen with this trick

Hi, can you test this command? <adb shell wm size 720x1280>
I think the Rom or Kernel has to be modded.

Yeah, i just remembered those commands and revisted this forum so consider this thread reopened. That probably should have been the first thing I tried.
I have already bricked my device flashing boot.img files through fastboot and had to reset the phone to factory. Therefore I can't use those shell commands anymore as they give me errors in adb sideload.
I can only go into adb sideload and fastboot.
Trying to sideload a ZE551ML rom fails around 50%. If I could somehow force the rom to flash(with some modding) I guess it might work??
At the same time it could still be a hardware issue.
If anyone knows how to make a rom for a different device flash without problems that would be nice.
UPDATE 01:
Okay I've managed to get into adb shell since my phone didn't actually reset..
Here is a display info dump:
C:\adb>adb shell dumpsys display
DISPLAY MANAGER (dumpsys display)
mOnlyCode=false
mSafeMode=false
mPendingTraversal=false
mGlobalDisplayState=OFF
mNextNonDefaultDisplayId=1
mDefaultViewport=DisplayViewport{valid=true, displayId=0, orientation=0, logic
alFrame=Rect(0, 0 - 720, 1280), physicalFrame=Rect(0, 0 - 720, 1280), deviceWidt
h=720, deviceHeight=1280}
mExternalTouchViewport=DisplayViewport{valid=false, displayId=0, orientation=0
, logicalFrame=Rect(0, 0 - 0, 0), physicalFrame=Rect(0, 0 - 0, 0), deviceWidth=0
, deviceHeight=0}
mSingleDisplayDemoMode=false
mWifiDisplayScanRequestCount=0
Display Adapters: size=5
LocalDisplayAdapter
OverlayDisplayAdapter
mCurrentOverlaySetting=
mOverlays: size=0
WifiDisplayAdapter
mCurrentStatus=WifiDisplayStatus{featureState=1, scanState=0, activeDisplayS
tate=0, activeDisplay=null, displays=[], sessionInfo=WifiDisplaySessionInfo:
Client/Owner: Client
GroupId:
Passphrase:
SessionId: 0
IP Address: }
mFeatureState=1
mScanState=0
mActiveDisplayState=0
mActiveDisplay=null
mDisplays=[]
mAvailableDisplays=[]
mRememberedDisplays=[]
mPendingStatusChangeBroadcast=false
mSupportsProtectedBuffers=true
mDisplayController:
mWifiDisplayOnSetting=true
mWifiP2pEnabled=false
mWfdEnabled=false
mWfdEnabling=false
mNetworkInfo=null
mScanRequested=false
mDiscoverPeersInProgress=false
mDesiredDevice=null
mConnectingDisplay=null
mDisconnectingDisplay=null
mCancelingDisplay=null
mConnectedDevice=null
mConnectionRetriesLeft=0
mRemoteDisplay=null
mRemoteDisplayInterface=null
mRemoteDisplayConnected=false
mAdvertisedDisplay=null
mAdvertisedDisplaySurface=null
mAdvertisedDisplayWidth=0
mAdvertisedDisplayHeight=0
mAdvertisedDisplayFlags=0
mIsCP=true
mAvailableWifiDisplayPeers: size=0
VirtualDisplayAdapter
UsbDisplayAdapter
Display Devices: size=1
DisplayDeviceInfo{"Built-in Screen": 720 x 1280, 60.000004 fps, supportedRefre
shRates [60.000004], density 320, 268.0 x 268.0 dpi, appVsyncOff 7500000, presDe
adline 12666666, touch INTERNAL, rotation 0, type BUILT_IN, state OFF, FLAG_DEFA
ULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUF
FERS}
mAdapter=LocalDisplayAdapter
[email protected]
mCurrentLayerStack=-1
mCurrentOrientation=0
mCurrentLayerStackRect=Rect(0, 0 - 720, 1280)
mCurrentDisplayRect=Rect(0, 0 - 720, 1280)
mCurrentSurface=null
mBuiltInDisplayId=0
mPhys=PhysicalDisplayInfo{720 x 1280, 60.000004 fps, density 2.0, 268.0 x 26
8.0 dpi, secure true, appVsyncOffset 7500000, bufferDeadline 12666666}
mState=OFF
Logical Displays: size=1
Display 0:
mDisplayId=0
mLayerStack=0
mHasContent=true
mPrimaryDisplayDevice=Built-in Screen
mBaseDisplayInfo=DisplayInfo{"Built-in Screen", app 720 x 1280, real 720 x 1
280, largest app 720 x 1280, smallest app 720 x 1280, 60.000004 fps, supportedRe
freshRates [60.000004], rotation 0, density 320 (268.0 x 268.0) dpi, layerStack
0, appVsyncOff 7500000, presDeadline 12666666, type BUILT_IN, state OFF, FLAG_SE
CURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
mOverrideDisplayInfo=DisplayInfo{"Built-in Screen", app 720 x 1280, real 720
x 1280, largest app 1280 x 1241, smallest app 720 x 681, 60.000004 fps, support
edRefreshRates [60.000004], rotation 0, density 250 (268.0 x 268.0) dpi, layerSt
ack 0, appVsyncOff 7500000, presDeadline 12666666, type BUILT_IN, state ON, FLAG
_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
Callbacks: size=45
0: mPid=603, mWifiDisplayScanRequested=false
1: mPid=798, mWifiDisplayScanRequested=false
2: mPid=902, mWifiDisplayScanRequested=false
3: mPid=926, mWifiDisplayScanRequested=false
4: mPid=988, mWifiDisplayScanRequested=false
5: mPid=1087, mWifiDisplayScanRequested=false
6: mPid=1263, mWifiDisplayScanRequested=false
7: mPid=1279, mWifiDisplayScanRequested=false
8: mPid=1297, mWifiDisplayScanRequested=false
9: mPid=1314, mWifiDisplayScanRequested=false
10: mPid=1332, mWifiDisplayScanRequested=false
11: mPid=1349, mWifiDisplayScanRequested=false
12: mPid=1366, mWifiDisplayScanRequested=false
13: mPid=1401, mWifiDisplayScanRequested=false
14: mPid=1447, mWifiDisplayScanRequested=false
15: mPid=1548, mWifiDisplayScanRequested=false
16: mPid=1627, mWifiDisplayScanRequested=false
17: mPid=1748, mWifiDisplayScanRequested=false
18: mPid=1897, mWifiDisplayScanRequested=false
19: mPid=1920, mWifiDisplayScanRequested=false
20: mPid=2172, mWifiDisplayScanRequested=false
21: mPid=2241, mWifiDisplayScanRequested=false
22: mPid=2310, mWifiDisplayScanRequested=false
23: mPid=2399, mWifiDisplayScanRequested=false
24: mPid=2464, mWifiDisplayScanRequested=false
25: mPid=2726, mWifiDisplayScanRequested=false
26: mPid=2936, mWifiDisplayScanRequested=false
27: mPid=2982, mWifiDisplayScanRequested=false
28: mPid=4042, mWifiDisplayScanRequested=false
29: mPid=4735, mWifiDisplayScanRequested=false
30: mPid=5048, mWifiDisplayScanRequested=false
31: mPid=5124, mWifiDisplayScanRequested=false
32: mPid=5204, mWifiDisplayScanRequested=false
33: mPid=5237, mWifiDisplayScanRequested=false
34: mPid=5380, mWifiDisplayScanRequested=false
35: mPid=5586, mWifiDisplayScanRequested=false
36: mPid=5822, mWifiDisplayScanRequested=false
37: mPid=6166, mWifiDisplayScanRequested=false
38: mPid=8600, mWifiDisplayScanRequested=false
39: mPid=8624, mWifiDisplayScanRequested=false
40: mPid=8684, mWifiDisplayScanRequested=false
41: mPid=9643, mWifiDisplayScanRequested=false
42: mPid=9905, mWifiDisplayScanRequested=false
43: mPid=10986, mWifiDisplayScanRequested=false
44: mPid=11030, mWifiDisplayScanRequested=false
Display Power Controller Locked State:
mDisplayReadyLocked=true
mPendingRequestLocked=policy=OFF, useProximitySensor=false, screenBrightness=6
4, screenAutoBrightnessAdjustment=1.6, useAutoBrightness=true, blockScreenOn=fal
se, lowPowerMode=false, dozeScreenBrightness=-1, dozeScreenState=UNKNOWN, transf
ormPolicy=8, brightnessOverride=false
mPendingRequestChangedLocked=false
mPendingWaitForNegativeProximityLocked=false
mPendingUpdatePowerStateLocked=false
Display Power Controller Configuration:
mScreenBrightnessDozeConfig=1
mScreenBrightnessDimConfig=10
mScreenBrightnessDarkConfig=1
mScreenBrightnessRangeMinimum=10
mScreenBrightnessRangeMaximum=255
mUseSoftwareAutoBrightnessConfig=true
mColorFadeFadesConfig=false
Display Power Controller Thread State:
mPowerRequest=policy=OFF, useProximitySensor=false, screenBrightness=64, scree
nAutoBrightnessAdjustment=1.6, useAutoBrightness=true, blockScreenOn=false, lowP
owerMode=false, dozeScreenBrightness=-1, dozeScreenState=UNKNOWN, transformPolic
y=8, brightnessOverride=false
mWaitingForNegativeProximity=false
mProximitySensor={Sensor name="PSH Proximity sensor", vendor="Intel Inc.", ver
sion=1, type=8, maxRange=5.0, resolution=5.0, power=0.35, minDelay=0}
mProximitySensorEnabled=false
mProximityThreshold=5.0
mProximity=Unknown
mPendingProximity=Unknown
mPendingProximityDebounceTime=-1 (3045884 ms ago)
mScreenOffBecauseOfProximity=false
mAppliedAutoBrightness=false
mAppliedDimming=true
mAppliedLowPower=false
mPendingScreenOnUnblocker=null
mPendingScreenOff=false
mScreenBrightnessRampAnimator.isAnimating()=false
mColorFadeOnAnimator.isStarted()=false
mColorFadeOffAnimator.isStarted()=false
Display Power State:
mScreenState=OFF
mScreenBrightness=10
mScreenReady=true
mScreenUpdatePending=false
mColorFadePrepared=true
mColorFadeLevel=0.0
mColorFadeReady=true
mColorFadeDrawPending=false
Photonic Modulator State:
mPendingState=OFF
mPendingBacklight=0
mActualState=OFF
mActualBacklight=0
mChangeInProgress=false
Color Fade State:
mPrepared=true
mMode=1
mDisplayLayerStack=0
mDisplayWidth=720
mDisplayHeight=1280
mSurfaceVisible=true
mSurfaceAlpha=1.0
Automatic Brightness Controller Configuration:
mScreenAutoBrightnessSpline=MonotoneCubicSpline{[(0.0, 0.031512607: 0.00117647
05), (50.0, 0.09033614: 9.663866E-4), (100.0, 0.12815127: 5.5672275E-4), (200.0,
0.16386555: 2.8361342E-4), (300.0, 0.18487395: 1.9957982E-4), (400.0, 0.2037815
2: 1.6806723E-4), (500.0, 0.2184874: 1.3655462E-4), (650.0, 0.23739496: 1.260504
7E-4), (800.0, 0.25630254: 1.1554626E-4), (1000.0, 0.27731094: 1.3235293E-4), (1
500.0, 0.35714287: 1.3445377E-4), (2000.0, 0.4117647: 7.668066E-5), (3000.0, 0.4
5588234: 3.2563017E-5), (4000.0, 0.47689074: 1.4705882E-5), (5000.0, 0.4852941:
6.302521E-6), (7000.0, 0.49369746: 7.5091754E-7), (10000.0, 0.5: 6.257642E-6), (
12500.0, 0.6260504: 5.0E-5), (15000.0, 0.75: 5.0E-5), (17500.0, 0.8760504: 5.0E-
5), (20000.0, 1.0: 4.9579834E-5)]}
mScreenBrightnessRangeMinimum=10
mScreenBrightnessRangeMaximum=255
mLightSensorWarmUpTimeConfig=0
Automatic Brightness Controller State:
mLightSensor={Sensor name="PSH Ambient Light sensor", vendor="Intel Inc.", ver
sion=1, type=5, maxRange=6553.5, resolution=0.1, power=0.35, minDelay=0}
mTwilight.getCurrentState()={TwilightState: isNight=true, mYesterdaySunset=25/
07/2015 6:33:16 pm, mTodaySunrise=26/07/2015 5:42:18 am, mTodaySunset=26/07/2015
6:33:15 pm, mTomorrowSunrise=27/07/2015 5:42:21 am}
mLightSensorEnabled=false
mLightSensorEnableTime=2946565 (99319 ms ago)
isBrightnessOverride=false
mAmbientLux=19.0
mBrighteningLuxThreshold=0.0
mDarkeningLuxThreshold=0.0
mLastObservedLux=19.0
mLastObservedLuxTime=3006466 (39418 ms ago)
mRecentLightSamples=0
mAmbientLightRingBuffer=AmbientLightRingBuffer{mCapacity=15, mStart=0, mEnd=0,
mCount=0, mRingLux=[], mRingTime=[]}
mScreenAutoBrightness=42
mScreenAutoBrightnessAdjustment=1.6
mLastScreenAutoBrightnessGamma=1.0
Click to expand...
Click to collapse
It seems that the phone touch sensitivity is about the top left part of the screen. I think it is ABOUT 1280x720 effectively of the 1920x1080 if the actual touch panel. It doesn't seem like it's gonna work but I'm still kinda hoping there is some way maybe like the kernal or something ??
Picture of how it works: (I added in a screen grab as I'm using androidscreencast to see whats happening onscreen)
https://drive.google.com/file/d/0B5_XK_MjRYKhUjY5SW9HYS1tVjg/view
When I use "adb shell wm size 1080x1920" it doesn't change the area of the effective touch screen either just changes the scaling
Also anyone who has a ZE551ML and is reading this could they PLEASE do a "adb shell dumpsys display" and post it here, not sure if it's useful but would just like to see the differences

I wonder if this screen would work for the ZE551KL (Laser). If you try to look for screens for it, you'll only come across ones advertised for the ZE551ML and others for ZD551ML, some of which are advertised as being for ZE551KL as well (it's printed on the ribbon cable). However, the front camera for the ZD551KL is in a different spot than the ZE551KL and ZE551ML, both of which have identical looking displays. I'm surprised that it's not the ZE551ML display doesn't have ZE551KL also printed on it.

so you had no success? the same thing happened to my phone and I am trying to fix it but there is only ze551ml screen available