The logic for EFragment gives an error if the EFragment annotated class has more than one constructor or if the constructor accepts any parameters. That rule makes sense for normal uses of EFragment since the FragmentBuilder needs to invoke the constructor on that class.

That rule however should not apply when the class it is annotating is abstract. In that case the constructor on the abstract class will never be called by AndroidAnnotations and will instead be called by constructors on the concrete subclass which should only have a default constructor (which can then call any constructor on the abstract class).