CM13 Z3+ Ivy E6553 Alpha -- Secondary Testing

Status
Not open for further replies.
Search This thread
M

moonbutt74

Guest
This is a no-frills thread.

I am looking for additional competent testers to provide proper feedback.
Testers are assumed to be experienced. Thank you.

Okay here it is.

Flash in order of appearance. Required.


Thanks @MotexT for initial testing and feedback.
So, working:
All CM apps; RIL; WiFi, Bluetooth; Theme Engine, Audio, Bluetooth/WiFI Hotspot work confirmed

Buggy:
Bluetooth (crashes of Bluetooth Share);
Camera (color bugs, frontal camera take photos with glitches);
Initial load/Load after reboot (glitches, performance loss - solving easy with locking/unlocking device);
AutoBrightness (small delay when switching brightness levels on the fly)
Screen Recorder

Not working:
NFC;
External SD Card;
OTG

Again this is alpha. This is for sinlge sim, you are welcome to test on dsds, i would be very interested in the results.

Cyanogenmod Source

Thanks to/for

@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization

@zacharias.maladroit For answering questions, many questions. [ still have more... xD ]

Those of you without a sense of humor, go away.

Okay current features i'm working on and stuff that works/doesn't work

UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.

USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget

I am working my kernel source here toward net-huntery goodness.

The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.

This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..

Thank you.

m
 
Last edited:
M

moonbutt74

Guest
Notes and Updates

NOTE

SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.

I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:

Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.


Use BETA-SuperSU-v2.52
Would have posted earlier but needed a smoke break *>cough<*

NOTE: this initial offering is in 3 parts due to limited bandwidth issues.
When i have resolved external storage i will upload a new build.
NFC may take a little longer.
 
Last edited:
M

moonbutt74

Guest
Breathing Room

Reserved 2
@MotexT will be posting screens, as time permits, in post number 4.

Trolls will be burned.
 
Last edited:

MotexT

Senior Member
Aug 25, 2014
196
423
Paris
Screenshots

Here we have some screenshots. If you need more - PM me, will add them ASAP. Also include the type of screenshot.
 

Attachments

  • Screenshot_20160509-173307.jpg
    Screenshot_20160509-173307.jpg
    115.4 KB · Views: 537
  • Screenshot_20160509-173332.png
    Screenshot_20160509-173332.png
    128.8 KB · Views: 493
  • Screenshot_20160509-173339.png
    Screenshot_20160509-173339.png
    83.1 KB · Views: 482
  • Screenshot_20160509-173344.png
    Screenshot_20160509-173344.png
    107 KB · Views: 466
  • Screenshot_20160509-173400.jpg
    Screenshot_20160509-173400.jpg
    85.5 KB · Views: 453
  • Screenshot_20160509-173404.png
    Screenshot_20160509-173404.png
    159.6 KB · Views: 446
  • Screenshot_20160509-173413.jpg
    Screenshot_20160509-173413.jpg
    88.7 KB · Views: 425
  • Screenshot_20160508-121717.jpg
    Screenshot_20160508-121717.jpg
    122.6 KB · Views: 432
Last edited:
M

moonbutt74

Guest
I'm using a single SIM version.

Please continue the work. I'll start testing by the weekend.

Thanks,

If i can get you to specifically test and log screen recorder that would be great. [including during playback]
Currently it appears to function but when it comes to playback of the recorded file, playback breaks.

Thanks.

m
 

KOALAaufPILLEN

Senior Member
Nov 29, 2011
170
14
Berlin
Hy well this thread need a clean start

And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention :)

BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?

Sent from my E6553 using XDA-Developers mobile app
 

MotexT

Senior Member
Aug 25, 2014
196
423
Paris
So, a small report about this ROM. For now I'm using it two days in a row, and it's pretty stable - you can use main functions without any troubles: WiFi, RIL, Themes Engine etc. Bluetooth works great, crashes sometimes and automatically restarts - not a big deal. It's a really smooth for alpha build and could be used even as daily driver if you close your eyes on some small bugs with not so important stuff. Anyways, testers are welcome
 
M

moonbutt74

Guest
Hy well this thread need a clean start

And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention :)

BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?

K, actually i don't know. But it's cool that you have a smart watch, would you mind be a tester/logger for that function in particular?
That would be great.

Thanks

m
 

风野龙太

New member
Oct 4, 2015
4
0
Single sim
How to solve this?:crying:
Full selinux support is present.
MTP Enabled
installing '/sdcard/cm_ivy-test_rebuild.zip'...
checking for MD5 file...
Skipping MD5 check: no md5 file found
target:sony/cm_ivy/ivy:6.0.1/Nega_spork/76b3bfd6c4:user debug/test-keys
could not detect filesystem for /dev/block/bootdevice/by-name/system,assuming ext4
mount:failed to mount /dev/block/bootdevice/by-name/system at /system failed;no such volume
E:Error executing updater binary in zip '/sdcard/cm_ivy-test_rebuild.zip'
Error flashing zip '/sdcard/cm_ivy-test_rebuild.zip'
updarting partition details...
......done
 

orangekid

Sr. Mod / Mod Committee / RC-RT Committee Lead
Staff member
Apr 10, 2009
14,602
8,414
Ok cleaned this up a bit.

I don't really have much issue with discussion on GIT etiquette, and tips to keep your "house clean" as it were. I think that's a good thing with devs working together on things like that.

Here's the bottom line. If you are merging commits into a kernel you have to keep the original authorship, period. To do otherwise is kang. We all know this.

Now if some dude has some private repo where during personal testing authorship is removed, but anything merged into the public kernel or the release repo/binary maintains proper authorship, then that is a bit gray, but the user is not clearly attempting to claim authorship at all.

If anyone sees a blatant kang, or attempt to hide/claim authorship, please report to the mods for handling. If this particular point needs more discussion, please open up a thread about it and have a non flame war discussion about it.
@moonbutt74 - I do ask that you make it very blatantly sure what your public release repo is, and that your authorship is maintained, and I actually recommend you do not link your personal playground repo to avoid situations.

Thanks guys.
 
  • Like
Reactions: lukeaddison
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    After looking thru all and speaking with the OP, I am closing this thread.
    3
    Screenshots

    Here we have some screenshots. If you need more - PM me, will add them ASAP. Also include the type of screenshot.
    1
    Ok cleaned this up a bit.

    I don't really have much issue with discussion on GIT etiquette, and tips to keep your "house clean" as it were. I think that's a good thing with devs working together on things like that.

    Here's the bottom line. If you are merging commits into a kernel you have to keep the original authorship, period. To do otherwise is kang. We all know this.

    Now if some dude has some private repo where during personal testing authorship is removed, but anything merged into the public kernel or the release repo/binary maintains proper authorship, then that is a bit gray, but the user is not clearly attempting to claim authorship at all.

    If anyone sees a blatant kang, or attempt to hide/claim authorship, please report to the mods for handling. If this particular point needs more discussion, please open up a thread about it and have a non flame war discussion about it.
    @moonbutt74 - I do ask that you make it very blatantly sure what your public release repo is, and that your authorship is maintained, and I actually recommend you do not link your personal playground repo to avoid situations.

    Thanks guys.