1.17 as I did not know that there is 1.21.
build completed successfully (02:50:34 (hh:mm:ss))
e-2.1-r-20240606-CUSTOM_MINI-serranoltexx
.
it contains :
AppLounge
GmsCore
GsfProxy
FakeStore
com.google.android.maps.jar
Mail
BlissLauncher
BlissIconPack
AccountManager
Camera
Calendar
eDrive
DroidGuard
Message
Notes
Browser
BrowserWebView
PwaPlayer
Because of /system partition too small,
|Filesystem |Size |Used |Avail |Use% |Mounted on|
|/dev/block/mmcblk0p21 |1.4G |1.4G |1.6M |100% |/system/etc/gps_debug.conf|
It dont include :
Advanced_Privacy (for now unfortunatly, my main goal is to incude it even by removing other apps)
Maps (you can add Magic-Earth from Aurora Store)
PdfViewer (you can add one from F-droid Store)
LibreOfficeViewer
Tasks
OpenKeyChain
Pico TTS
eSpeakTTS
SpeakNG
VOSK
Talkback
OpenWeatherMapWeatherProvider
e-2.1-r-20240606-CUSTOM_MINI-serranoltexx
Please share your feed back …
Thanks Piero. I installed it and it seems to work very well.
I will update if there will be problems.
thanks for reporting…
should be a typo error here,
“GT-I9195” is one of the “serranolte” devices, for which i builded serranoltexx
when
“GT-I9195I” is “serranovelte” and is different device that is not compatible with this build…
is not a stock firmware reference, i presume you are on latest Samsung firmware (I9195XXSCQAN_KitKat(Android 4.4.2) but with CyanogenMod 13.0-20161221 installed over it.
i don’t plan to set up an OTA-update server for this unofficial build, so no matter
it is expected as i have removed “OpenWeatherMapWeatherProvider” to gain place in the /system partition
isn’t it the default for “unofficial” or “custom” ?
i have signed using my “personnal account” (named “antec” in the build number) not using “public keys”
I have a problem. I tried to update from e-1.17-r-20231106-CUSTOM_MINI-test-serranoltexx to e-2.1-r-20240606-CUSTOM_MINI-serranoltexx
I went to recovery mode I authorized adb sideload. It went to 48% as usual and then a message appeared. signature not verified. Install anyway I said yes. BUt everything stopped. Thus I rebooted and now the device is stucked. If I tried to go into recovery it shows Galaxy recovery but then it becomes black again and is looping on that. I can stop on Download. What can I do ?
Best regards
Sergio
Answers
recovery-e
Galaxy logo with the blue line recovery on the top
indeed with another device which had TWRP it worked very well
i don’t i have time today to reproduce :
install e-1.17-r, update the recovery to recovery-e-1.17-r, then try the update to e-2.1-r.
so my quick advise is to flash TWRP and see…
After a lot of efforts I good unlocked the phone. Then I installed TWRP and e-2.1. However after installation it did not work correctly. When I want in parameter update it did not give the version of the e-o. The 4G did not work (the cross appeared on the side of the intensity) Thus I went back to e-1.17 and everything works
Thanks a lot @piero !!
I didn’t saw it.
Do you maintain it ? Is the outage responsible of dead links ?
Sorry but i haven’t the skill to maintain, i only can attempt to build from time to time…
version 2.1 is not working as we need,
better is to try version 1.17 or use the original 0.18.
What i want to learn is repartitionning the mmcblk0
device storage to extend /system partition from 1.5GB to 2.0GB,
and simply build a complete e-2.2-r
Yes. my /e/cloud is currently not accessible…
Ok, how is it done ? Is there a partition table or so to modify ?
One have to modify the PIT file (easy to do, even have to be precise) AND also modify some expected values in the sources (i don’t know where)…
@tcecyk i know you are comfortable with GitHub
Some devices already have been repartitioned (Samsung Galaxy s2, Gogol Nexus 7…)
@piero you can look at how repartitioning is done from the flo/flox scripts, but calculating offsets will be involved
There is another problem.
The setting application stops working when touching system update.
Is this a major problem or I can ignore it
Best
You could look in BoardConfig.mk
as adjusted here for bacon
.
BoardConfig.mk
is expected at top level of device tree, but the entry needed maybe found in android_device_samsung_serrano-common
in your case.
This topic was automatically closed after 179 days. New replies are no longer allowed.