Kernel weed out
The original Kernel was build with debugging enabled in all parts.
Here is a greeting from the old kernel:
[ 0.000000] **********************************************************
[ 0.000000] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 0.000000] ** **
[ 0.000000] ** trace_printk() being used. Allocating extra memory. **
[ 0.000000] ** **
[ 0.000000] ** This means that this is a DEBUG kernel and it is **
[ 0.000000] ** unsafe for production use. **
[ 0.000000] ** **
[ 0.000000] ** If you see this message and you are not debugging **
[ 0.000000] ** the kernel, report this immediately to your vendor! **
[ 0.000000] ** **
[ 0.000000] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 0.000000] **********************************************************
Yes, this is how that device was sold.
I cut off a lot of debugging cruft. A lot. A lot.
fixed charge mode
The battery animation now works.
And there was a bug that the device did not turn off the display backlight. So it doesnāt do fast charge. I fixed that.
wireless charger
My device used to become punk after using a wireless charger. I fixed that somehow: The original code is crap. Iād like having the data sheets.
Android
fixed adb via wlan
Bug was, it did not remember the wireless network.
/e/os
I included Trebuchet launcher. You get the choice at the end of the welcome.
F-Droid with privileged extensions
bugs?
So far itās just āApp Loungeā that does not work for me, at least no commercial apps.
Thank you, for your contribution on this device that was hoped for a long time.
.
When i build /e/, i like to share also the recovery-e aside the main .zip file, (and the others mandatory .img to flash prior when exist).
i take it from /out/target/product and rename it following the /e/ naming convention (copy/paste from the main .zip filename).
Edit : reading your instructions, i just see you included the recovery into the main .zip
@piero : I am sorry but I donāt get the point of your reply.
Gigaset brand is not referenced in your first link. ADB request to already have the phone. And even if I known the code name of the GX290 and the GX290 plus, I didnāt find any list of compatible code name, neither in this topic nor in the sourceforge link.
So, your reply sound like a āsearch better before askingā. I could understand if your link would contain any helpful information. But here, if there it contains an answer to my question I didnāt find where, and I feel a little like talking with these bots which always give predefined answer whatever the question is, when you try to contact your phone operator.
It seems that the only difference between the two models is the quantity of ram and memory space. I donāt see any reason why they would need a different build, but I would have the confirmation before buying one. Will this build work with the āplusā model ?
i wanted to know the device codename to search XDAā¦
.
also, unlike some other Gigaset āPlusā device, the GX290_plus is not registred in the list of Android Supported devices - Google Play Help - Google Support (this list is not always accurate, there are some duplicate and some ommited devices)
Why i asked for device productnameā¦
But the reason you asked the question is that you still wanted some certainly after you had done your research. @piero has spent much time demonstating why there might be uncertainty !
You said
Gigaset brand is not referenced in your first link.
This is because you were reading what the forum creators call a āpreviewā ā unhelpful in this case. If you care please just read the link (briefly) [HOWTO] Find device codename ā¦ there it is demonstrated that there are many ways to find the device codename and you can then check your device is an exact match with the build. Is why you asked your original question.
