3017 replies to this topic

[ernopiros]

Does anyone is experience problems with the touchscreen?

I've been using Konsta since cm9 and i had to replace de screen months ago. Everything was fine until a couple of weeks when the screen started to behave strangely (no response, pressing a button activates other buttons, zoom when swipe)

So what i want to ask you is if someone is experience this or its an hardware issue?

Thanks

[96frozen]

What the community is doing is amazing, the armv6 project is awesome! Open source is a beauty

[kahush]

Thanks KonstaT and devs for the great work!
Downloading and testing...

[HumaDroid]

 ernopiros, on 01 January 2013 - 12:58 PM, said:

Does anyone is experience problems with the touchscreen?

Thanks

Do you face same issues with other roms?

[96frozen]

Sweet, thanks for the new build! Is it possible to port that "headset plugged in" to cm10? If so, how can i do it?

[ernopiros]

 HumaDroid, on 01 January 2013 - 03:01 PM, said:

Do you face same issues with other roms?

haven't tried other. i started to face this issues in the last build of Konsta's cm10. Did a full wipe, installed the cm10.1 but this issue stands...

i even cleaned inside the phone (screen and digitizer) because there were some dust in there

Edited by ernopiros, 01 January 2013 - 03:55 PM.

[sej7278]

 KonstaT, on 01 January 2013 - 12:33 PM, said:

Yeah, there was no other choice. I'll still try to get stuff usefull for everyone to get merged upstream CyanogenMod and hopefully get rid some of those forks. I'm not going to fork projects that get updated every day (e.g. frameworks/base and settings), I'll probably just later publish patches for features that I've added. AndroidARMv6 project is a bit too chaotic for my OCD but there's definately some nice work being done there.

its actually easier to some degree - less manual patches to apply, and since armv6/512mb has absolutely zero support from cyanogenmod now, why not fork it all?

my OCD tells me to delete a few more wallpapers/dictionaries and restore apollo (i don't use it, but i have nothing against it) and get rid of that fecking bootanimation - pretty but i'd prefer 20secs off my boot time and 1.5mb in /system

all we need in frameworks/base is to fix the F1_NewVoicemail.ogg typo and optionally the two reviews from gerrit i guess?

s2e is messing about royally for some reason, only seems to work every other boot, it seems its losing its settings or not installing properly or something. i might try a wipe of /sd-ext and /data as it was fine with 21/12

gonna try a self-build now. happy new year!

edit: bugger, it seems taking the CM bootanimation out, still leaves the default android one, echo 1 > /data/property/persist.sys.nobootanimation does nothing either, looking at the init.goldfish.sh script, we have to add one of these to system.prop "ro.kernel.android.bootanim=0" or "debug.sf.nobootanimation=1"

edit 2: seems colour banding is back in my build like konstat's 21/12 build, but the 01/13 build was fine.....?

Edited by sej7278, 01 January 2013 - 07:30 PM.

[HumaDroid]

nothing shows in "Manage and restore backups" in ROM manager.
Anybody face this?

[sej7278]

 HumaDroid, on 01 January 2013 - 04:54 PM, said:

nothing shows in "Manage and restore backups" in ROM manager.
Anybody face this?

none of the cwm6's support rommanager, use cwm touch or the hardware keys, ditch rommananger.

[HDuser]

 KonstaT, on 21 December 2012 - 08:31 AM, said:

Merged commits not mentioned in the changelog.

1.1.2013 changelog:

• backported USB gadget driver from msm-3.0 kernel (thanks to WaylandACE)
  
  • fixed native USB tethering
    
  • fixed issues with apps failing because of borked usb0 interface (e.g. network speedtest apps)
• switched to wpa_supplicant_8
  
• added power hal and boostpulse support to ondemand governor
  
• Quick Settings: Swipe to switch (1)
  
• Add persistent notification when headphones are plugged in (1)
  
• CyanogenMod clock widget - Chronus (merged)

21.12.2012 changelog:

• new world order

ulo kahein ka sala ini deer bad update kita ae te kuch bhi non working mein se workin ni kia

[sameen.asil]

I've been using this rom since a week... no probs, its working fine

Edited by sameen.asil, 01 January 2013 - 06:14 PM.

[sameen.asil]

 ernopiros, on 01 January 2013 - 12:58 PM, said:

Does anyone is experience problems with the touchscreen?

I've been using Konsta since cm9 and i had to replace de screen months ago. Everything was fine until a couple of weeks when the screen started to behave strangely (no response, pressing a button activates other buttons, zoom when swipe)

So what i want to ask you is if someone is experience this or its an hardware issue?

Thanks

I've been using this rom since a week, no touch screen probs at all, its working fine...maybe your cell has some hardware probs....

[KonstaT]

 sej7278, on 01 January 2013 - 04:11 PM, said:

edit: bugger, it seems taking the CM bootanimation out, still leaves the default android one, echo 1 > /data/property/persist.sys.nobootanimation does nothing either

edit 2: seems colour banding is back in my build like konstat's 21/12 build, but the 01/13 build was fine.....?

It seems that the property needs to be renamed. Using debug.sf.nobootanimation doesn't disable it either. I now uploaded patches for additional features and there's two for that (1,2).

Is this color banding some OLED specific issue because I've never had any problems with it? I have locally this but I didn't push it to github because it seems to be somewhat wip.

[sej7278]

 KonstaT, on 01 January 2013 - 06:56 PM, said:

It seems that the property needs to be renamed. Using debug.sf.nobootanimation doesn't disable it either. I now uploaded patches for additional features and there's two for that (1,2).

Is this color banding some OLED specific issue because I've never had any problems with it? I have locally this but I didn't push it to github because it seems to be somewhat wip.

i don't think its oled-specific, although i do have an oled. people used to moan about it in cm7/9 and i never noticed it, but since 10/10.1 i have. tom_g explained it once long ago - it should be set to 2 for our devices (fix blur+dither) and indeed is in the system.prop, but the code isn't there to do anything with it i guess (without your surfaceflinger patch).

as far as nobootanimation goes, it seems that the code to chose it is hacked together in the init script and should be in the cpp as you have done (as you can then use settings app rather than build flags).

i'll have a go at merging in some of the patches in a bit.

Edited by sej7278, 01 January 2013 - 07:39 PM.

[sm4tik]

I can confirm that color banding thing. It was present in 21/12 build but today's build is fine with a tft screen.

[wuiwu]

wow,so cool

[Lazaroid]

I've been testing pretty much every one of Konstat's releases of 4.0, 4.1, and now 4.2 since about July and very impressed with the progress for what is now a relatively underpowered phone! Kudos to all involved.



I've never bothered upgrading CWM from 5.0.0.5 (I think it is; could be 5.0.5.0: currently upgrading to latest ROM so can't check!). Is there any advantage to upgrading it to 6.0.2.7? OK, I don't currently have touch support but I'm not convinced I'd trust that enough to use it!

I'm fairly happy testing ROMs because I know I can go back to a backup from before installation. My current CWM seems to do all that I need so is there any point in touching it?

[sej7278]

 KonstaT, on 01 January 2013 - 06:56 PM, said:

It seems that the property needs to be renamed. Using debug.sf.nobootanimation doesn't disable it either. I now uploaded patches for additional features and there's two for that (1,2).

Is this color banding some OLED specific issue because I've never had any problems with it? I have locally this but I didn't push it to github because it seems to be somewhat wip.

colour banding is fixed with that patch (rebased, attached) on my oled.  fw_native.patch.zip   1.95K   13 downloads

the bootanimation patches work but result in just a black screen whilst booting, but it does boot 20secs faster....

ah, it seems that s2e doesn't work on the first boot after doing a nandroid, although first boot after other recovery operations (install zip) seems fine. a reboot seems to fix it anyway. not your recovery.

Edited by sej7278, 01 January 2013 - 10:20 PM.

[daaneel]

Awesome ROM, hard bricked my SGS 2 with some buggy rom so had to switch back to my trusty blade...
Great to have 4.2 running on it, makes the downgrade less painful

Not asking ETAs, but I am wondering about the video hw decoding.
Will it be hard to port Ganster's patch that fixed this for cm9&10 to this ROM?
Thanks for all the hard work Konsta!

[..Abel..]

great work !!