1474 replies to this topic

[dreis911]

bezerra, on 21 November 2012 - 02:16 PM, said:

Ganster already said that had a mistake on first line, is "debug.sw.hw=1" and  not "debug.sf.hw=1"

Yes.
But I tried them both... with the same result. The phone goes crazy!

[dreis911]

Ganster, on 21 November 2012 - 02:24 PM, said:

Very understandable bugreport...

Ok. Fair enough.
When I restart the phone:
1- Cid shows!
2- the Boot animation doesn't run
3- the screen only shows the "status bar" and background image, no icons, no navigation bar, no notification drawer, it's an empty phone.
4- the light goes down
If I press "power button" it shows the same screen (3) and there's no padlock to drag and unlock the phone.
I press "power button" for 1 sec to show the "power menu" it shows this menu with normal illumination and dims the menu immediately.
I press "power off" and the window "your phone will shut down" shows for a millisecond and disappears.
The "power menu" doesn't disappear but I press it on the place where the "OK button" (from the window "your phone will shut down") should be.
Then it shuts down.

I forgot to say that the "hardware buttons" don't work either.

Edited by dreis911, 21 November 2012 - 03:23 PM.

[Ganster]

Hmm, may be I was fix something in my test ROM, because that strings work ok for me...

[dreis911]

Ganster, on 21 November 2012 - 03:55 PM, said:

Hmm, may be I was fix something in my test ROM, because that strings work ok for me...

I understand.
And it seems to work for someone else:

mum1989, on 21 November 2012 - 12:20 PM, said:

Great !
Thanks for the tips Ganster   (no lag when "Scroll widget" )

[slumslayer]

Ganster, on 21 November 2012 - 03:55 PM, said:

Hmm, may be I was fix something in my test ROM, because that strings work ok for me...

I've got the same problem, lockscreen, notifications and launcher are 'invisible' with those lines. But you can see them during the screen off animation and the phone is working : I can unlock it and launch an app.

[mum1989]

dreis911, on 21 November 2012 - 04:12 PM, said:

I understand.
And it seems to work for someone else:

Yep and I restart my phone and it's OK for the moment. (but i wrote "debug.sw.hw=1 " I Will try "debug.sf.hw=1"

Edit : not good my phone is crazy too with "debug.sf.hw=1"

How i can edit the file    (i can use the phone ) with adb ?

edit 2 : It's Ok with adb  recovery  etc..

Edited by mum1989, 21 November 2012 - 06:41 PM.

[dreis911]

mum1989, on 21 November 2012 - 05:46 PM, said:

Yep and I restart my phone and it's OK for the moment. (but i wrote "debug.sw.hw=1 " I Will try "debug.sf.hw=1"

Edit : not good my phone is crazy too with "debug.sf.hw=1"

How i can edit the file    (i can use the phone ) with adb ?

edit 2 : It's Ok with adb  recovery  etc..

That, I don't know, but you can upgrade with Konsta's ROM 2012/10/31.
You won't lose anything! .... I didn't. And it will be OK.

[themechooser]

im struggling to install this rom.

I cannot do vol+menu key, the previous rom just boots as normal. I have unzipped folder to leave image folder on root of sd card(folder contains imge.bin and md5)
if i try to install via clockwork mod it aborts installation.

help please

[mum1989]

dreis911, on 21 November 2012 - 06:47 PM, said:

That, I don't know, but you can upgrade with Konsta's ROM 2012/10/31.
You won't lose anything! .... I didn't. And it will be OK.

it's ok I do this 'cp /system/build.prop.bak /system/build.prop (with revovery)

[german_psycho]

Thank you very, very, very, very much for this great Rom. Just installed it and it works like a charm.
Seems much faster than the CM7 stable (2.3.7?) that I had on my phone.

Great work!

Edited by german_psycho, 22 November 2012 - 04:54 PM.

[Cata_Simi]

please update html5 browser streaming in cm9 too

[huibuhh]

btw, did a short test if KonstaT's 4.2  camera and keyboard also work on CM9:
- the keyboard does not even show up after flashing and when trying to open/install the .apk in file browser there is a parsing failure message
- the camera works great. camera, camcorder, panorama, everything just fine. Only when trying to apply posteffects to photos via gallery the gallery shuts down with a failure message regarding the com.android.gallery3d process. So it does work but i see no real benefit from using it instead of the cam this release comes with.

Edited by huibuhh, 26 November 2012 - 03:35 PM.

[JMS74]

I beg for wifi tethering. not the the third party ad hoc mode that needs root access to login but the normal AP mode..

[daemond]

Wifi tethering is nice, but it kills the battery very quickly. Have you considered Bluetooth tethering instead? Or does that not cut it because you want to tether to multiple clients?

[JMS74]

daemond, on 26 November 2012 - 10:19 PM, said:

Wifi tethering is nice, but it kills the battery very quickly. Have you considered Bluetooth tethering instead? Or does that not cut it because you want to tether to multiple clients?

Yeah, I've tried some times and didn't work, have you got it working? if so care to provide a tutorial?
more than one client is the goal but one is better than none.

Edited by JMS74, 27 November 2012 - 04:56 AM.

[Last Boyscout]

@Gangster

In the CM9 ROM your update

Quote

UPD5: You can use updated OMX from attachment, and my last changes in libstagefright to enable HW playback of AVI, DivX, WMA and RealMedia formats!

Is not integreated

Is it enough to replace your new files in the ROM? (Unpack, Replace, Pack, Flash the modified ROM)? Or is there more to do?

Edited by Last Boyscout, 27 November 2012 - 09:47 PM.

[andr0idbeliev3r]

So Ganster KonstaT said mdp composition is a placebo, is it true?

[KonstaT]

andr0idbeliev3r, on 27 November 2012 - 09:59 PM, said:

So Ganster KonstaT said mdp composition is a placebo, is it true?

Oh for f*cks sake!

Ganster originally wrote debug.sw.hw=1. That does absolutely nothing because such property doesn't exist! It doesn't matter which debug.composition.type you use with that because it will always fall back to cpu composition.
https://github.com/C...com_ui.cpp#L388

debug.sf.hw=1 will switch to gpu composition and adding debug.composition.type=mdp will do horrible things simply because it doesn't work on our device.

[andr0idbeliev3r]

KonstaT, on 27 November 2012 - 10:12 PM, said:

Oh for f*cks sake!

Ganster originally wrote debug.sw.hw=1. That does absolutely nothing because such property doesn't exist! It doesn't matter which debug.composition.type you use with that because it will always fall back to cpu composition.
https://github.com/C...com_ui.cpp#L388

debug.sf.hw=1 will switch to gpu composition and adding debug.composition.type=mdp will do horrible things simply because it doesn't work on our device.

I wasn't talking about debug.sf.hw, i know that debug.SW.HW don't work i'm not a complete noob on android.

Don't worry KonstaT i won't even use mdp if you say it's placebo, i think you may have quated the wrong post.

And calm down ok?
I am a proud user of your builds and i use them as you published them(except for some audio mods )

I would never ask such dumb questions about debug.SW.hw not working because as you said it doesn't exist.

And i have readed an article about mdp composition and you are right it does go back to the gpu, i never used mdp, ui is good enough.

[huibuhh]

KonstaT, on 27 November 2012 - 10:12 PM, said:

debug.sf.hw=1 will switch to gpu composition and adding debug.composition.type=mdp will do horrible things simply because it doesn't work on our device.

It is all so easy:

Quote

Out of curiosity I wrote 2 lines into build.prop, in an attempt to make BOTH CPU and GPU to work the graphics.
(...)
So all you have to do is add debug.composition.type=gpu to build.prop, underneath that add debug.composition.type=cpu. Reboot and experience a difference.