2794 replies to this topic

[nokiafan02]

Merry Christmas KonstaT!

[dhavaljp.95]

I m facing a strange problem .. My phone when plugged to the charger,it doesn't show any increment on the indicator . If charged when phone is switched off then it charges, what should I do ?? BTW great work @konsta

[dkkerry]

Happy to see KonstaT back, can't wait to try out this rom

[JimJam707]

Great Job KonstaT! Long live the blade!

[ThomsoN6]

ROM is stable and smooth. I had only one phone restart, when my blade was in my pocket ;p
I am very surprised by the smoothness of the interface... it is smoother than any JB ROM!
Generally there are no problems


Merry Christmas for all of you! ;>

[Snap.IT]

Wrong thread, good work Konstat and Hyvää joulua.

Edited by Snap.IT, 25 December 2012 - 05:11 AM.

[Farkaspók]

Hi KonstaT!

I tried all versions of your 4.1.2 port from 2012.08.21, but in all of them the voip bug still exists, so i can't upgrade to newer versions, i must use the 2012.08.21 release.

But now i tried this 4.2.1 port and surprise, the voip works well! So i immediately upgrade to this. Thank you for your great work!

[sej7278]

merry xmas folks. well done konstat - i've been watching your github with anticipation, just did a custom build but noticed there's a shedload of patches to apply to lose 40mb+ of cyanogenmod/google cruft again.

[anantk]

Hi KonstaT,

You are the best judge for this CM 10.1 ZTE ROM development.

But could you please check URL http://forum.xda-dev...d.php?t=1836116, where users are having JB ROM on their Sony Xperia X8 mobile, which is less powerfull than our ZTE Blade mobile with native USB tethering, Native WIFI tethering and even FM Radio functionality working.

[lineone]

great job KonstaT.
thank you.

[KonstaT]

 docck, on 24 December 2012 - 02:33 PM, said:

Don't know mmaybe it'd be helpful for KonstaT. In http://www.modaco.co...-now-available/ devs worked on porting BT for 4.2 Android. They has success and now BT works on CM 10.1 ROMs for Advent Vega tablet.

Well, I've been looking for a device with working bluetooth on a non-Broadcom bluetooth hardware. Maybe I somehow missed the 'success' part as it seems that bluetooth is still an issue for them?

Google changed the bluetooth stack completely in 4.2 and the new bluedroid is developed by Broadcom. There's also a Qualcomm based solution in AOSP (for Nexus 4) but it is only partially open and for much newer Atheros chip (Atheros WCN3660?) than what we have. I did manage to make little progress with bluetooth using the qcom stuff, but pretty much only sign of life that it's giving is a wakelock (good old msm_serial_hs_dma that some might remember from ICS). I've actually broken bluetooth intentionally in the release build, I'm sure people prefer a device that can enter deep sleep preperly.

Might have to wait until someone comes up with a bluez based solution (CAF already had it done once but it's reverted again) or try hacking the Broadcom stuff at some point. Either way I suspect that sorting out bluetooth is going to take weeks rather than days.

 Farkaspók, on 25 December 2012 - 09:54 AM, said:

Hi KonstaT!

I tried all versions of your 4.1.2 port from 2012.08.21, but in all of them the voip bug still exists, so i can't upgrade to newer versions, i must use the 2012.08.21 release.

But now i tried this 4.2.1 port and surprise, the voip works well! So i immediately upgrade to this. Thank you for your great work!

It seems that it's something in upstream CyanogenMod code that's causing your issue. I'm glad it's working for you but I haven't done anything to fix/break it. All device specific audio stuff is pretty much the same than it is in 4.1.

 anantk, on 25 December 2012 - 05:17 PM, said:

But could you please check URL http://forum.xda-dev...d.php?t=1836116, where users are having JB ROM on their Sony Xperia X8 mobile, which is less powerfull than our ZTE Blade mobile with native USB tethering, Native WIFI tethering and even FM Radio functionality working.

Sorry, but that's exactly the kind of stuff that I don't need. Especially not cross-posted on several thread, and especially not after you've already posted that same thing before and someone has already given you a valid answer. Device you're referring to has completely different wifi hardware and it has completely different FM hardware!

Then there's certain difference between some things not listed as 'not working' or someone claiming it's working - and it actually working. If you'd bothered to search the thread you linked, you would have know that it doesn't have working USB tethering (and their bugtracker has exactly the same logcat on this issue that I used to have on Blade).

I, on the other hand, did manage to sort some old USB related issues.
 Screenshot_2012-12-25-13-46-01.png   37.57K   94 downloads  Screenshot_2012-12-25-14-02-39.png   259K   93 downloads

Merry Christmas equally to everyone (if you celebrate it).

[Snap.IT]

 anantk, on 25 December 2012 - 05:17 PM, said:

Hi KonstaT,

You are the best judge for this CM 10.1 ZTE ROM development.

But could you please check URL http://forum.xda-dev...d.php?t=1836116, where users are having JB ROM on their Sony Xperia X8 mobile, which is less powerfull than our ZTE Blade mobile with native USB tethering, Native WIFI tethering and even FM Radio functionality working.

What is the point of this post?

You're referring to another forum where they have another phone with other hardware working?

How do you imagine that that is helpful at all?

This is like referring to Nexus 4 and proclaim that they have FM radio working just fine so KonstT should look into that and upgrade everyones Blade with other hardware.

It's not just that you're being daft about it, it's that this has been repeated constantly for several hundred of pages in four threads.

[Snap.IT]

 KonstaT, on 25 December 2012 - 07:19 PM, said:

Well, I've been looking for a device with working bluetooth on a non-Broadcom bluetooth hardware. Maybe I somehow missed the 'success' part as it seems that bluetooth is still an issue for them?

Google changed the bluetooth stack completely in 4.2 and the new bluedroid is developed by Broadcom. There's also a Qualcomm based solution in AOSP (for Nexus 4) but it is only partially open and for much newer Atheros chip (Atheros WCN3660?) than what we have. I did manage to make little progress with bluetooth using the qcom stuff, but pretty much only sign of life that it's giving is a wakelock (good old msm_serial_hs_dma that some might remember from ICS). I've actually broken bluetooth intentionally in the release build, I'm sure people prefer a device that can enter deep sleep preperly.

Might have to wait until someone comes up with a bluez based solution (CAF already had it done once but it's reverted again) or try hacking the Broadcom stuff at some point. Either way I suspect that sorting out bluetooth is going to take weeks rather than days.


It seems that it's something in upstream CyanogenMod code that's causing your issue. I'm glad it's working for you but I haven't done anything to fix/break it. All device specific audio stuff is pretty much the same than it is in 4.1.


Sorry, but that's exactly the kind of stuff that I don't need. Especially not cross-posted on several thread, and especially not after you've already posted that same thing before and someone has already given you a valid answer. Device you're referring to has completely different wifi hardware and it has completely different FM hardware!

Then there's certain difference between some things not listed as 'not working' or someone claiming it's working - and it actually working. If you'd bothered to search the thread you linked, you would have know that it doesn't have working USB tethering (and their bugtracker has exactly the same logcat on this issue that I used to have on Blade).

I, on the other hand, did manage to sort some old USB related issues.
Screenshot_2012-12-25-13-46-01.png Screenshot_2012-12-25-14-02-39.png

Merry Christmas equally to everyone (if you celebrate it).

Very nice.

God Jul!

[C3C0]

That hs_dma wakelock. It reminds me of modified bt init script I  did in the past to get rid of it in ics. Wouldn't it help on jb, too?
Just a quick-shot...
https://github.com/C...init.qcom.bt.sh

[sej7278]

can anyone remember the settings to fix colour banding, 16-bit alpha should be on as well as dither+blur fixes as i recall, but doesn't seem to help. also seems bloody slow, are there gfx acceleration problems perhaps?

Edited by sej7278, 26 December 2012 - 02:30 AM.

[Snap.IT]

 sej7278, on 26 December 2012 - 02:00 AM, said:

can anyone remember the settings to fix colour banding, 16-bit alpha should be off and dither+blur fix on as i recall, but doesn't seem to help. also seems bloody slow, are there gfx acceleration problems perhaps?

It's a pre-alpha ROM, what the hell did you expect? A perfect version in one release, read the bloody OP and stop whining about it, either patch it or shut up.

[sej7278]

 Snap.IT, on 26 December 2012 - 02:21 AM, said:

It's a pre-alpha ROM, what the hell did you expect? A perfect version in one release, read the bloody OP and stop whining about it, either patch it or shut up.

whoaaaa, take a chill pill. i'm only asking not whining! konstat's not really said much about what we should expect - should it be up to cm10 levels (which from the working/not working lists it seems like it) or should it be considered alpha.

looking at it /data/property/persist.sys.* are being ignored as things like dithering/alpha/nobootanimation settings just don't work, that's all. i can't find anything on gerrit about it, and they don't seem to have changed how it works in aosp, so i'm just wondering if its a problem with the rom.

also to *me* it seems a lot slower than cm10, and i noticed on github konstat mentioned that gfx acceleration has changed (back to pre-ics methods?) so i was just wondering if we can get some background info on that.

[vNa5h]

And here begins the flame wars, ball sucking..yada yada

[Stu C]

 Snap.IT, on 26 December 2012 - 02:21 AM, said:

It's a pre-alpha ROM, what the hell did you expect? A perfect version in one release, read the bloody OP and stop whining about it, either patch it or shut up.

I don't want to start a fight, but it has to be said that your response was out of order. Add to that, sej has made massive contributions to the development of CM on the Blade since the beginning, and deserves respect for that. If a team is going to fix this, I want sej on that team!

[sej7278]

it seems to me that the settings parts of alpha/blur/dithering are merged, but the frameworks/native bits aren't, which explains why the properties are being set but do naff all:

see the commit from cm10:  http://review.cyanog....org/#/c/19532/

10.1 branch doesn't have it: https://github.com/C.../surfaceflinger

apologies to konstat, i hadn't realised how behind cm10 the cm10.1 commits are, after a few hours looking through the code the whole of cm10.1 seems alpha especially for older/non-aosp hardware, its a miracle it even boots on anything other than nexus4 as it is! the surfaceflinger patches won't apply anyway as there's no concept of dithering in the code yet.

Edited by sej7278, 26 December 2012 - 10:32 AM.