Related
CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
FAQ (Please Read!!)
What is CyanogenMod (by mad-murdock)?
CyanogenMod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Q: How do I install this?
A:
Latest version: http://download.cyanogenmod.com/?device=galaxys2 (for when nightlies are working normally)
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Only for the International version of the Galaxy S2, US versions like the AT&T have their own device specific builds.
Note: sometimes you need to flash twice back to back without a reboot in the middle. The install should take a little time, if it happens very quickly, flash again.
Install via ClockworkMod (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Samsung Galaxy S2.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for Samsung Galaxy S2, choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You can go back and forth freely between CM7 and other ROMs via ROM Manager or ClockworkMod recovery as the file systems are the same and nandroid backup/restore works to go between ROMs.
Q: What are the known issues?
A: Issues that I can remember:
- Video playback - some formats are not recognized, use an alternative app for video playback
- Camera - some modes don't work
- TVout, MHL
- FMRadio
- Issues when using the 2G/3G-Switch
- Volume issues (some report too high, others too low)
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2 - this shows all the
changes that have gone into a nightly, including anything that is device specific to Galaxy S2 and anything that has gone into common code that is also included on Galaxy S2. If you see another device sometimes in the Galaxy S2 changelog, it is because the changes were done to common code and the repository is also included on the Galaxy S2.
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSII phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps. They are available in ROMManager. ROMManager also asks you if you want to install the Google Apps addon when you install via ROMManager.
Q: My phone is running too hot, my phone is not going into deep sleep
A: Try to isolate which application is using too much CPU. The first thing to try is to remove your media (video, music etc) files. Files recorded using Samsung camera, but other files as well, can frequently cause the stock Media Scanner to fail and go into an infinite loop. Then try to isolate which files are causing problems, and report them to us. If it isn't media, then it is some other application. Try to remove that application if it is a third-party application (and report a bug to them).
Q: I cannot find my media files that are on my external sd card
A: Look under /mnt/emmc as that is where CM7 mounts the external sd card as opposed to /mnt/sdcard/external_sd that Samsung ROMs use.
Q: Can I run Samsung Applications like Kies, Phone, Email, AllShare?
A: No. Any applications that use special calls into the Samsung TouchWiz framework will not work.
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: My Notification bar Sound widget does not toggle through the options.
A: Settings > CyanogenMod Settings > Interface > Notification Power Widgets > Widget Buttons > Sound Modes and set the modes you want it to toggle through.
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
Q: How do I go back to a Samsung stock ROM?
A: Just use ClockworkMod or ROM Manager backup/restore facility to go back and forth between stock (or any other ROM) and CM7.
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes.
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager. Nightly builds should up in ROM Manager when the CyanogenMod buildbot builds the nightly successfully. Every new device needs to also get added to the ROM Manager manifest before it is available. But, the same files are also available at http://download.cyanogenmod.com when the buildbot successfully builds a nightly.
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer). We will also try to put these enhancements into CM7 ourselves.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: Try to get the logcat output and last_kmsg to your report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this.
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Nice Q&A here. This is a MUST READ before flashing CM7
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager.
Click to expand...
Click to collapse
I have premium rom manager but dont see any cm7 roms in the download section
???
darkevangerion said:
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Click to expand...
Click to collapse
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Thanks for your fast answer.
And thanks for the rom, obviously
EDIT : Hmmm... "Tonight" = "Tomorrow" for European. :/
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Click to expand...
Click to collapse
Thanks.
Why can't i register my device for notification on updates from nightly?
I got rom manager premium
Sent from my GT-I9100 using XDA Premium App
Answered 3 posts above.
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
carda21 said:
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
Click to expand...
Click to collapse
It's strange, it's work fine for me.
Hunteres said:
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
Click to expand...
Click to collapse
Take a look at the #5 post
No official nightly build has been built yet by the build bot......thats the automated rombuilder witch is used to build the roms.....so if no rom is built no rom in rom manager ......
Sent from my GT-I9100 using Tapatalk
i have just tryed installing an app via the market website to my mobile and its working fine for me....
Hello,
Is there any way I can increase vibration intensity? It is fine when I reboot it but after a minute the vibration becomes very weak to the point where I can barely feel it. (When typing and pressing "menu" or "back button" etc
Sent from my GT-I9100 using XDA App
It's a known issue of this ROM.
There is nothing to do for this time.
Cyanogen #1 !
Issue gonna be FIX, by next build's
i just have one question, someone said they used kg1 modem does that actually stay or would cm7 just overwrite it anyway?
since im too noob to post in development section i want to thank you all at teamhacksung for this
Also...why was the stock camera app replaced with one that is worse? (Camcorder is worse.) Its a great rom. But can someone explain this to me?
Sent from my GT-I9100 using XDA App
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Warning : Not for new users, flash this build only if you know what you are doing !!!
What is CyanogenMod (in less terse form - by mad-murdock)?
since i am a bit idle right now, i try to answer this.
cyanogenmod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Installation instructions:
in following post - will move moved to Q&A Forum when that is up.
teamhacksung:
atin - http://gplus.to/atinm
codeworkx - http://gplus.to/codeworkx
coolya - http://gplus.to/coolya
unhelpful - http://twitter.com/unhelpfulone
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Modems:
TBD
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
CyanogenMod 7 (w/ Gingerbread 2.3.7) for AT&T Galaxy SII
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
FAQ (Please Read!!)
What is CyanogenMod (by mad-murdock)?
CyanogenMod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Q: How do I install this?
A:
Latest version:
Temporarily while buildbot is down:
You can get it from ROM Manager (look for teamhacksung builds for Galaxy SII AT&T) or
http://www.multiupload.com/RT29P7AOFS (md5: c8115d0a01d0a47b286ff5c9cc504175)
Previous kang: http://www.multiupload.com/A30J9DZN37 (md5: a23d1b99ff73da31e5d0421ec18e15e3)
Normally: http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Note: You may need to flash twice back to back if the first one goes by too quickly - the actual flash takes a little time and sometimes the first flash doesn't "stick".
Install via ClockworkMod recovery (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Samsung AT&T Galaxy S2.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for AT&T Samsung Galaxy S2, choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You can go back and forth freely between CM7 and other ROMs via ClockworkMod recovery as the file systems are the same and nandroid backup/restore works to go between ROMs.
Q: What are the known issues?
A: Issues that I can remember:
- Video playback - some formats are not recognized, use an alternative app for video playback
- Camera - some video and still modes don't work
- TVout, MHL
- Dock
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2att - this shows all the changes that have gone into a nightly, including anything that is device specific to Galaxy S2 and anything that has gone into common code that is also included on Galaxy S2. If you see another device sometimes in the Galaxy S2 changelog, it is because the changes were done to common code and the repository is also included on the Galaxy S2.
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSII phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps. They are available in ROMManager. ROMManager also asks you if you want to install the Google Apps addon when you install via ROMManager.
Q: Can I run Samsung Applications like Kies, Phone, Email, AllShare?
A: No. Any applications that use special calls into the Samsung TouchWiz framework will not work.
Q: I cannot find my media files that are on my external sd card
A: Look under /mnt/emmc as that is where CM7 mounts the external sd card as opposed to /mnt/sdcard/external_sd that Samsung ROMs use.
Q: My phone is running too hot, my phone is not going into deep sleep
A: Try to isolate which application is using too much CPU. The first thing to try is to remove your media (video, music etc) files. Files recorded using Samsung camera, but other files as well, can frequently cause the stock Media Scanner to fail and go into an infinite loop. Then try to isolate which files are causing problems, and report them to us. If it isn't media, then it is some other application. Try to remove that application if it is a third-party application (and report a bug to them).
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: My Status bar Sound widget does not toggle through the options.
A: Settings > CyanogenMod Settings > Interface > Notification Power Widgets > Widget Buttons > Sound Modes and set the modes you want it to toggle through.
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
Q: How do I go back to a Samsung stock ROM?
A: Just use ClockworkMod or ROM Manager backup/restore facility to go back and forth between stock (or any other ROM) and CM7.
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes.
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager. Nightly builds should up in ROM Manager when the CyanogenMod buildbot builds the nightly successfully. Every new device needs to also get added to the ROM Manager manifest before it is available. But, the same files are also available at http://download.cyanogenmod.com when the buildbot successfully builds a nightly.
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer). We will also try to put these enhancements into CM7 ourselves.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: Try to get the logcat output and last_kmsg to your report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this.
And one more.
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Codeworkx just put up a test build (http://codeworkx.de/download/galaxys2att/cm7-galaxys2att-KANG.zip) - it should work, but right now none of us has an AT&T SGS2, so need someone else to try it. Install it via ClockworkMod recovery as explained in the second post.
Let us know if it basically works.
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Another Phone gets the best Android ROM ever!!! ;-)
jivy26 said:
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Click to expand...
Click to collapse
Thanks - excellent! Change your signature to say "AT&T SGS2 CyanogenMod 7!"
Lol already did
Phone: AT&T SGS2
Running: CM7
getting signature verification failed. and yes, i am already rooted.
LOL seriously...already cm7 is here?? Can't wait to get home and throw this on here
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Lol already did
Phone: AT&T SGS2
Running: CM7
Click to expand...
Click to collapse
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
atinm said:
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
Click to expand...
Click to collapse
Yea just had to install cm7 let it reboot it won't load passed galaxy s2. Pull battery goo into cwm install again gtg
Sent from my SGH-I777 using xda premium
seattleboi1982 said:
getting signature verification failed. and yes, i am already rooted.
Click to expand...
Click to collapse
Did you follow the instructions in the second post in the thread? As in, did you use the "Harder way" - flash ClockworkMod recovery etc?
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Used super one click to root Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
jivy26 said:
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok, great - the "harder way" (and only way at the moment!). Thanks!
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
My order is in, should be seeing my Galaxy S II very soon, stoked!
I'll be testing just about everything pushed out once its here, I'll be reporting back as much as possible can't wait!
Drew489 said:
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
Click to expand...
Click to collapse
I didn't even know there was a MIUI for AT&T Samsung Galaxy SII yet. As far as no sound - we haven't been able to test anything ourselves as we don't have a device to test on yet (maybe in a couple of days). The code itself hasn't changed much, but it is possible you're seeing something valid that we'll have to fix.
jivy26 said:
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Click to expand...
Click to collapse
Did you test voice calls? Can you report back?
System: Android 2.3.3 (Gingerbread) - Discontinued May 2, 2014
About:
This is a fork of the DSC ROM, which is based on the Olleh KT 407 ROM. Its genesis came about as a result of a request by lordofazeroth (here) asking to delete all unnecessary apps from /system/app in the next release. My answer was matter of fact: to do it himself rather than asking _n0p_ to do it. This was because I had already created a private version of DSC for my needs and felt that if people really wanted apps out they should take them out themselves.
However, thinking back on it, lordofazeroth's request wasn't wholly out of line. While getting rid of some apps, e.g. HTML Viewer, made no sense, one thing that did make sense was removing the Google apps from /system/app. This was in keeping with Google's direction regarding the apps. Starting around the time Gingerbread was released, Google began to remove most of the Google apps from new versions of Android and making them available for download via the Play Store. Looking in an ICS Google apps package for AOSP ROMs, the only Google apps remaining in the package that could also be downloaded from the Play Store are Google Talk (now known as Hangouts) Google Search, and Voice Search. I fully expect that future Google Apps packages for AOSP ROMs would only contain the Play Store, Google Services Framework, the minor apps that aren't on the Play Store (Google Gallery, News & Weather), and support files.
While getting rid of the apps from /system/app made sense, a lot of people still associate a complete Android experience with having the apps and didn't want to lose them. Fortunately, the DSC ROM has a solution in the form of a firstboot.zip whose contents are extracted and installed while the system boots the first time. It was a simple matter to move the Google apps currently in /system/app to the firstboot.zip and have them installed when the ROM is installed. This makes the end user expecting the Google apps preinstalled happy because the apps are present. And if an end user doesn't wish a particular app to be installed, e.g. Maps, they can completely uninstall it and not be left with the original version in the ROM.
So, based on this idea, I put together my own version of the DSC ROM with this shift in design and am releasing it to the public. Since the ROM is essentially DSC with a few minor changes, it should function as well as DSC does. It's hoped that if _n0p_ releases a new version of DSC that this design change can be folded back into DSC.
Differences between DSC and the Traveller DSC fork:
DSC 2.3's updates are included in the ROM, thus no need to apply patches after installing the ROM.
The DSC 2.3 kernel was replaced with the swap-enabled version of the same kernel (as of version 2.3.4).
SuperSU replaces SimpleSU. SimpleSU's binary isn't recognized as valid by certain apps, e.g. Busybox Free.
The Traveller ICS Theme and the Stargate boot animation are now the default. wway's Gingertrue theme and Ace32's boot animation are available as a flashable theme zip.
Zeam has been replaced with HoloLauncher.
The CM7 File Manager app has been added to /system/app.
Gmail, Hangouts, Maps, Quick Search, Voice Search, and YouTube are all in dsc_firstboot.zip instead of being embedded in the /system directory.
All Google apps, including the Play Store, were updated to their latest available versions.
Google Play Services and Google Street View are new to the ROM. If after uninstalling Google Play Services the app reappears in your app drawer, then Google has pushed the app back to the device. Please do not complain on the forums about this, as it is expected behavior and not a fault of the ROM or device.
Antutu CPU Master Free, WiFi Reassociate, Superdim, System Panel, and ClockSync were all removed from the ROM. In using DSC I have never encountered a problem that required any of these apps, and I replaced Antutu with the XDA version of SetCPU. All should be available through the Play Store if desired or needed, except for the XDA version of SetCPU.
Ghost Commander was removed because the CM7 File Manager app was included in /system/app. Ghost Commander should still be available through the Play Store.
The Streak FM Radio app was replaced by the March 11th version of Spirit FM Free. The limitations of the Streak FM Radio app are well known (no volume control). The Spirit FM Free app is apparently limited to either Blended Audio or Mono sound - it's not clear which - but at least the volume can be controlled. The March 11th version of Spirit FM Free is also the last version that supports the Dell Streak.
ZRAM Status was added to monitor ZRAM usage in the ROM (as of version 2.3.5).
Bugs:
Google Maps may cause excessive battery drain. Freeze Maps or uninstall it if this issue is encountered.
Arabic and Hebrew text in Aroma may appear backwards due to lack of right to left support.
Touchscreen support in Aroma is erratic. Scrolling using the touchscreen does not function, and it may require a few taps to get selections to properly register. As an alternative, the volume controls and the camera button can be used to navigate and select items. This is likely a hardware issue and not fixable in Aroma.
Tips:
Disable notifications in SuperSU for a clean look and to speed up the boot process.
SuperSU will receive updates from the Play Store. To save storage space convert the update to a system app.
Undervolting the CPU using the DSC CPU Voltage Configuration app is highly recommended to maximize battery life.
HoloLauncher has the ability to hide apps in the app drawer. If you know you're never going to use a particular system app, e.g. the email client, hide it instead of deleting it from the ROM.
Customize dsc_firstboot.zip to meet your needs. For example, if you use Google Earth, rename the APK file to com.google.earth.apk and add it to dsc_firstboot.zip.
Google Car Home was left in /system/app because if uninstalled it cannot be downloaded from the Play Store.
The original release of the Hangouts 2.0 app (from Android 4.4) had a bug which allowed it to work on Gingerbread. If wishing to use Hangouts in place of the stock Messaging app, set the app to not be automatically updated in the Play Store or you will lose SMS capability when the app updates.
Changelog:
2.4.6:
UPDATE: Hunderteins has released another SSL Ciphers update, this time around to boost speed and security of HTTPS connections by implementing new encryption and authentication algorithms.
UPDATED APPS: Google Play Services, Hangouts and YouTube.
Older Revisions:
2.4.5:
UPDATE: OpenSSL firmware updated to fix the Heartbleed bug.
UPDATED APPS: Google Play, Google Play Services, Hangouts, Maps, SuperSU, and YouTube.
2.4.4
UPDATE: HoloLauncher updated to 2.11. Now has a color theming option similar to what is available in KitKat.
BUG FIX: Hebrew language in Aroma now displays.
BUG FIX: Grammar fixes for some screen text in Aroma.
Because 2.4.4 is being released so soon after 2.4.3, I'm leaving 2.4.3's updates visible as well as providing a patch for current users to install rather than downloading the entire ROM and installing it again.
2.4.4 Update.zip - 819.16 KB
2.4.3
NEW: PDroid for Arabic users now available.
UPDATES: SuperSU, Flash Player, YouTube, Hangouts, Google Play Services, and AFWall+. The release of Flash Player included here is the final release from Adobe. There will be no further bug fixes or updates.
UPDATE: Aroma Installer updated to 2.70RC2. This update restores touch support to the installer, which was missing in 2.51 as well as allowing the user to quit the installer at any point prior to installing Traveller DSC or its features.
BUG FIX: Fixed the issue with Arabic support not properly installing. For Arabic support to work the base ROM (and any added features) must be installed prior to installing Arabic support. This means you will have to run Aroma twice to enable Arabic support. The first time will be to install the ROM. After installing the ROM and letting everything in dsc_firstboot.zip install, reboot into the recovery and run Aroma the second time. Select the Arabic menu choice and install those options on top of Traveller DSC.
After selecting Arabic in the Language & Keyboard options in Settings, the very first time the power button is used to shut down the Streak the device will hot reboot and attempt to cycle through the boot animation. It will fail and then hot reboot a second time. This second time the device should boot to the launcher.
2.4.2
UPDATE: Play Store updated to 4.5.10.
UPDATE: Clock font changed to the version used in Android 4.4, resolving an issue with a portion of the clock being cut off when the pattern lock is used.
UPDATE: Common fonts used in both Android 2.3.3 and 4.4 were updated to the Android 4.4 versions.
2.4.1
BUG FIX: Replaced the tabbed browser with the original stock browser to resolve a force close issue with Voice Search. Clearly the tabbed browser wasn't quite ready for prime time.
2.4.0
NEW: Installation is done via the Aroma Installer. There is no touch support for the Streak, so the volume controls and the power button must be used to navigate. As a result of this change, all the various modifications available have been rolled into the zip file, meaning there will be no separate downloads needed for this version of Traveller DSC. The increase in size of the zip file also means that MediaFire cannot be used. Dev-Host will be used instead.
NEW: A new version of the zRAM app was compiled from its sources, with a black background and with memory readouts expressed in MB rather than bytes. It is now also a system app.
NEW: The stock browser is now a version of Lightning Browser compiled from source, with a custom dark theme to fit the rest of the ROM.
UPDATED APPS: AFWall+, Google Play Services, HoloLauncher, SuperSU, and YouTube.
UPDATE: Roboto Condensed is now the default font, for that Android 4.4 look.
UPDATE: Arabic patch users can now fully benefit from the SSL Cipher improvements due to a fix in framework.jar.
BUG FIX: In QuickPanel, the Auto-brightness indicator can now be clearly distinguished from the maximum brightness indicator.
BUG FIX: The "System Updates" option in Settings > About phone now links to this thread instead of the DSC thread.
BUG FIX: The "Build Version" option finally had a version bump, to 2.4.
NOTE: Gingertrue users will not have the new browser installed. While the browser is available for download here, it may not install. Gingertrue users wishing to use the tabbed browser will need to convert it to a system app using an app like Apps2ROM. The other option would be to install a copy of Lightning Browser.
NOTE: The browser may force close after exiting. The cause is unknown at this time, but may also affect Lightning Browser, since the former was compiled from the source of the latter.
2.3.10
SuperSU reverted to 1.65. See explanation here.
Fixed bugs caused by developer error when adding ciphers patch.
Default wallpaper was changed.
Changelog for versions prior to 2.3.10 was removed.
Links:
Flashing Instructions
407 ROM [Dev-Host Links Removed]
Mega
ROM Download
DSC "Flash Me Before Installing" Pack
How to add your files to the Traveller DSC ROM
While the Traveller DSC ROM does change several things in the system, notably replacing SimpleSU and Zeam with SuperSU and HoloLauncher, its biggest "selling point" if you will is the ability to customize the app package that is installed with the base ROM. The DSC ROM includes a zip file located in /system/etc named "dsc_firstboot.zip". After DSC is installed and the system rebooted, during the Google account setup and for a short period of time afterwards a script is run that installs all the apps found in dsc_firstboot.zip.
The base DSC ROM included in its dsc_firstboot.zip the following apps: Adobe Flash, AnTuTu CPU Master Free, WiFi Reassociate, DSP Manager, Ghost Commander, Maps, YouTube, Droidwall, Dell Swype, DSC Wallpapers, Superdim, SystemPanel, ClockSync, and Streak FM Radio. Many of the Google apps remained in the ROM. For Traveller DSC, as already mentioned in the first post in the thread, all the Google apps except for the Play Store and Car Home were pulled from the ROM and stored instead in dsc_firstboot.zip. This is because all of these apps had new versions in the Play Store and thus there seemed to be no reason to keep old versions in /system/app. At the same time I changed up the apps package.
Traveller DSC includes in dsc_firstboot.zip the following apps: Adobe Flash, DSP Manager, Maps, GMail, Google Play Services, Quick Search, Street View, Voice Search, YouTube, Droidwall, Spirit FM Free, Dell Swype, zRAM Status, and DSC Wallpapers.
Traveller DSC encourages customization. I want you to make this ROM your own. If you want to delete the Google apps, go ahead. If you want to do what I did and add Google Music, you can do that too. This brief tutorial explains how. But keep in mind the following: dsc_firstboot.zip cannot be larger than the remaining space in the /system partition. If the file is too large the Streak may freeze at the Dell logo or end up in a boot loop. If this happens, remove apps until the file is smaller than the remaining space in the /system partition, then install the ROM again.
Tools required - PC: WinZip, WinRAR (preferred) or 7-Zip. Do not use the built-in Windows zip utility as it corrupts the zip file.
Tools Required - Streak: An app backup utility such as App Backup & Restore.
Optional - PC users with Chrome: APK Downloader extension.
Extract dsc_firstboot.zip from the Traveller DSC ROM.
On the Streak back up the installed app you want to add using an app backup utility. Ideally, when backing up the app you do not want its user-friendly name, but the name Android associates with the app, e.g. com.google.android.gm.apk instead of GMail.apk. There is a means to get the Android name of the app, using the Play Store on the PC.
Connect the Streak to the PC and download the backed-up app to a directory of your choosing.
Rename the app if necessary. See below.
Open up dsc_firstboot.zip with WinZip, WinRAR, or 7-Zip. Simply drag and drop the new app into the dsc_firstboot.zip window. The file will be compressed and added to the rest.
To add the new dsc_firstboot.zip to the ROM, open up the ROM's zip file, navigate to /system/etc, then simply drag and drop the new zip file into the directory. The ROM's zip file will update itself, overwriting the old zip file with the new one.
Copy the new ROM file to the Streak and install the ROM.
If the app on the Streak carries a friendly name, open up a browser window on the PC and head to the Play Store. Search for the app in the Play Store and look at the URL. The Android name of the app is found within the URL. For example, if wanting to embed Kongregate Arcade into dsc_firstboot.zip you would find it in the Play Store. The URL would be play.google.com/store/apps/details?id=com.kongregate.android.kongarcade. The Android name is found after /details?id= in the URL, thus the Android name for Kongregate Arcade would be com.kongregate.android.kongarcade. Rename the apk file from Kongregate Archade.apk to com.kongregate.android.kongarcade.apk and then follow steps 5-7 above.
If using Chrome, use the APK Downloader extension and download a copy of the app directly from the Play Store to eliminate the need to use a backed-up version of the app on the Streak. Google recently changed things and now all files downloaded from the Play Store using APK Downloader have a filename consisting of a random number, so it's necessary to give the downloaded file the correct name. When the Windows prompt appears asking for a location to save the file in, rename the downloaded file to the name referenced in the URL, e.g. com.kongregate.android.kongarcade.apk. From there, follow steps 1, 5, 6, and 7.
NOTE: This tutorial may be revised from time to time in order to clarify details or simply to make things easier to understand.
hello, thanks for the rom. i came from cm7 based rom. if i want to try this rom, can i just flash the zip just like usually ? I read instruction link, confused about flash_me, just seems lots of step to flash a DSC rom. My baseband already 406.
Thanks.
Sent from my Dell Streak 5
Powered by INDOSAT
The provided baseband files improve the voice quality but are not essential to getting the ROM to work. As this is merely a tweaked version of DSC I put out as a proof of concept, everything you know about DSC still applies.
I'm not sure what's the difference between the pdroid version and basic.....I don't know which one to try
Sent from my Dell Streak using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1357056
PDroid is a privacy add-on.
Had a data wipe after I did a reboot. Unfortunate as it seemed nice as a "update" for DSC 2.3.
Explain please? I've never had a data loss issue in the entire time I've been running this ROM (several months before I released it).
Strephon Alkhalikoi said:
Explain please? I've never had a data loss issue in the entire time I've been running this ROM (several months before I released it).
Click to expand...
Click to collapse
Don't take it as a slight on your ROM, personally I think it's more of an issue with my device. I did fresh install over DSC 2.3 after that I had a data wipe after a random restart. With this ROM I'd rebooted after I changed default orientation to portrait in DSC config resulting in complete wiping, i.e. upon restart I was welcomed with the Welcome to Dell Streak touch here to continue screen.
I wasn't taking your comments in a negative fashion. Sorry if I gave that impression.
I don't change the default orientation so I've not noticed that. One thing I did notice is that ever since I changed the baseband in my Streak to 366 WiFi has never failed to initialize after waking up the Streak. The "beta" versions of this ROM I ran using the 406 baseband and often had to engage and disengage airplane mode to wake up the WiFi. It still doesn't stop me from having an occasional spontaneous reboot, but it's an improvement. So, I recommend using the 366 baseband, which can be installed using the DSC "Flash Me Before Installing" pack.
Thanks for sharing... I am downloading the files and will read thru all the instruction before proceeding...
I have place back the picture to show the problem.
For some reason XDA is adding <br /> to the end of the links here, which is why people were getting the request for a decryption key. I've edited my post to fix the links.
ROM updated to correct the chef's not realizing that the version of Spirit FM he added did not support the Streak any longer.
Currently testing one of _n0p_'s older versions of the kernel to see if replacing the kernel fixes the spontaneous reboot issues I and a couple other people have been getting at random times. If this does fix things, I'll provide an updated ROM. If anyone wants to try this out, you can download the u28 (DSC 2.0 release) boot.img from _n0p_'s DSC thread here.
Some updated information available here.
Any update on your test results @strephon
Sent from my Dell Streak using Tapatalk 2
ammujee said:
Any update on your test results?
Click to expand...
Click to collapse
Check the DSC thread. I reported my results there.
Just for anyone waiting for an update.. @Strephon Alkhalikoi has updated an 'all in one' fixed version 2.3.3 in the OP.
Thanks. :highfive:
I'm having problems downloading from the MEGA links on the first page... does anyone have any mirrors set up?
I had no trouble. Possibly an Internet issue?
OK, I successfully grabbed the rom and the "Gingertrue Theme and Phoenix Boot Animation"
...however when attempting to install the theme zip I got a failure. (Status 6)
Hello guys,
This is my first post as a suggestion for solving a poblem as well as exposure of a subject.
Ok let's go
First, do it for your own risk, and not penalize me if something goes wrong, ok?
The rom that I am using is the Android 7.0 Elephone_P9000_20170419 Nougat, which you can download on the site needrom.com (probably also work with rom Elephone_P9000_20170418, downloaded from the official site elephone, but had no chance to test).
It is mandatory that you have installed TWRP Recovery, it is your only means of security in case something wrong happens. Always make security backups. (I'll post one soon, how to easily install from the Flash Tool).
Download the file through the link https://www.androidfilehost.com/?w=files&flid=23253 faceunlock_lollipop5.1_20150402.zip
INSTALLATION
1. Place the file on the SD card, or on the internal memory of the phone;
2. Boot at the Recovery https://forum.xda-developers.com/elephone-p9000/development/recovery-unofficial-twrp-elephone-p9000-t3426678 TWRP;
3. Install the zip file;
4. Reboot your phone;
Process terminated, your trusted app face has been installed.
https://goo.gl/photos/N4y8j4HEc135xq5U6
RECOMMENDATIONS
The file loads the old (Marshmellow) version of the application, but it is fully functional; the recent version of the app is not working, so it is not recommended that you manually update this file.
Always remember to make a backup of security.
I still have other things to publish, such as:
- Fully functional Google apps and Pixel Launcher (official) with the opportunity to recover backup through the Google account, which is not possible with only the official rom version of the P9000 Elephone. I have tested this rom for two weeks, and will post soon;
- A very beautiful and functional thema (for me the best thema)... I'll make a surprise ;-P
I hope you like it
THANKS
@asdfasdfvful follows link from the original post;
@Jonny and yours fully functional non official TWRP, thank you so much man;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds UNOFFICIAL?
There are no differences. its pure /e/. "just" build on my server
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Camera does work but only for photo, i.e. video recording fails.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? STOOOOOOP! NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easiest way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot to mention ....!
Sources
build manifest
XDA:DevDB Information
gtexslte_eos-n_unofficial, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld(!)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-18
Last Updated 2020-11-18
FAQ
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
No plans on my site. I may check that later but the chance is very low.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-
steadfasterX said:
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
No plans on my site. I may check that later but the chance is very low.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
On windows:
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-
Click to expand...
Click to collapse
Very nice job. Looking awesome:good:
Everything is ok except some problems/issues.
First is the camera. As you have said, camera does work but only for photo. But it only happens on the foundation.e.camera (default camera app). And in other apps require camera such as Qanda, it does not work. Like this:
The second problem is the cellular (or phone signal) problem. It says that "Emergency calls only" and I can't use mobile data(4g) or make any phone calls.
The next one is stability. Sometimes Espeak have fc (force-close) after using camera app.
and sometimes Bliss launcher (pre-installed) have some fc when i press home button.
Sorry if I can't provide to you the proper log because of some reasons.
Anyways, the rom works very well and actually better than the LOS i used before.
Without Google spyware, The performance increases and i have more ram to do other things.
I hope you will fix those issues i have mentioned above in future OTA updates.
Thank you for the nice work.
espeak is a known issue of /e/ OS and should be fixed hopefully anytime soon: https://gitlab.e.foundation/e/backlog/-/issues/1890
cam is nothing I will work on sorry..
signal issue is very likely because of your STOCK firmware --> make a screenshot of the full " about" menu in settings (where you see build number etc)
Can I encrypt /data partition like in the Settings > Encryption > Encrypt phone
and Encrypt SD Card with this ROM?
Also, how stable it is for daily driver/use?
Did you fix the mic routing issue when in call? Use earphone mic instead of the built in mic of the tablet?
How about the video when app like Element.io or some other video conferencing apps?
steadfasterX said:
espeak is a known issue of /e/ OS and should be fixed hopefully anytime soon: https://gitlab.e.foundation/e/backlog/-/issues/1890
cam is nothing I will work on sorry..
signal issue is very likely because of your STOCK firmware --> make a screenshot of the full " about" menu in settings (where you see build number etc)
Click to expand...
Click to collapse
Here are some screenshots
This one is from "about tablet" menu.
And I bonus some screenshots include some information i have from the "Device info HW" app (ru.andr7e.deviceinfohw, maybe you've already known it before).
That's all the screenshot i provided.
GAPS does not work. I'm using the open_gapps-arm-7.1-nano-20170503.zip version
ijlara said:
GAPS does not work. I'm using the open_gapps-arm-7.1-nano-20170503.zip version
Click to expand...
Click to collapse
Uhm.. Maybe read the OP again??
Sorry ... I really read it and ended up forgetting that GAPS doesn't work ....
johnnyhoang said:
Everything is ok except some problems/issues.
First is the camera. As you have said, camera does work but only for photo. But it only happens on the foundation.e.camera (default camera app). And in other apps require camera such as Qanda, it does not work. Like this:
The second problem is the cellular (or phone signal) problem. It says that "Emergency calls only" and I can't use mobile data(4g) or make any phone calls.
The next one is stability. Sometimes Espeak have fc (force-close) after using camera app.
and sometimes Bliss launcher (pre-installed) have some fc when i press home button.
Sorry if I can't provide to you the proper log because of some reasons.
Anyways, the rom works very well and actually better than the LOS i used before.
Without Google spyware, The performance increases and i have more ram to do other things.
I hope you will fix those issues i have mentioned above in future OTA updates.
Thank you for the nice work.
Click to expand...
Click to collapse
ok your cell service issue could come from a too old stock firmware. yours is from 2016 and there were some releases later on.
I have adjusted the OP with instructions (pls see topic "Requirements") with the firmware I am using without issues.
.-
It is difficult to find a ROM that works well on this device. It is for my daughter and I also can't get a ROM that works with Samsung's Kids Mode.
steadfasterX said:
ok your cell service issue could come from a too old stock firmware. yours is from 2016 and there were some releases later on.
I have adjusted the OP with instructions (pls see topic "Requirements") with the firmware I am using without issues.
.-
Click to expand...
Click to collapse
i have tried so many ways. And it is not working after all.
installed T285XXU0AQH1 baseband from the BTU csc , but the cell service issues still happening.
my original csc is XXV, and the latest update still T285XXU0API1 baseband (20171115 ver.)
johnnyhoang said:
i have tried so many ways. And it is not working after all.
installed T285XXU0AQH1 baseband from the BTU csc , but the cell service issues still happening.
my original csc is XXV, and the latest update still T285XXU0API1 baseband (20171115 ver.)
Click to expand...
Click to collapse
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
steadfasterX said:
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
Click to expand...
Click to collapse
Ok,i have given up. I don't know the way to install that properly because of the CSC differences(you said it should be in T285XXU0AQH1 but it didn't available in my country XXV. XXV still use T285XXU0API1 even with the latest update from 2017). So i will use that normally bc i'm ok without cellular.Btw things still work like a charm, and i have no regret of choosing this rom.
steadfasterX said:
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
Click to expand...
Click to collapse
Sorry for misunderstanding.
I have found the reason why the cellular issues comes out. It is made by the SIM card itself, not the baseband version or the stock firmware version as you have said. I was wrong when i think that it come from the software or stock firmware. Now i found out the reason for that. Sincerely apologize to you.
johnnyhoang said:
Ok,i have given up. I don't know the way to install that properly because of the CSC differences(you said it should be in T285XXU0AQH1 but it didn't available in my country XXV. XXV still use T285XXU0API1 even with the latest update from 2017). So i will use that normally bc i'm ok without cellular.Btw things still work like a charm, and i have no regret of choosing this rom.
Click to expand...
Click to collapse
Anyways thanks for noticing the recquirements. I think it is not necessary now since i found the real reason for the cellular issues.
When I changed another SIM card, it works flawlessly.
johnnyhoang said:
Sorry for misunderstanding.
I have found the reason why the cellular issues comes out. It is made by the SIM card itself, not the baseband version or the stock firmware version as you have said. I was wrong when i think that it come from the software or stock firmware. Now i found out the reason for that. Sincerely apologize to you.
Anyways thanks for noticing the recquirements. I think it is not necessary now since i found the real reason for the cellular issues.
When I changed another SIM card, it works flawlessly.
Click to expand...
Click to collapse
great stuff and thx for the feedback!
It ok, but google services framework stop. Fash zip Dolby Atmos (DAP_r6.5.zip) work Vanced manager install Youtube Vancednon root work. addonsu-14.1-arm-signed.zip work. VOLUME+BOOSTING+SOUND+(Very+Loud).zip work
binhdt said:
It ok, but google services framework stop. Can not flash zip Dolby Atmos, Vanced manager can not install Youtube Vanced
Click to expand...
Click to collapse
apps which require google crap will not work on /e/. That is by design..
You can browse the e foundation forum to find alternatives though.
How To's: https://doc.e.foundation/how-tos/
General Forum: https://community.e.foundation/
--> e.g a quick search here shows a bunch of alternatives for youtube: https://community.e.foundation/t/alternative-to-youtube/23703/10
or here another huge listing: https://github.com/tycrek/degoogle
Other alternatives: https://community.e.foundation/t/ho...urce-alternatives-of-your-apps-services/13616
.-
steadfasterX said:
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds UNOFFICIAL?
There are no differences. its pure /e/. "just" build on my server
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Camera does work but only for photo, i.e. video recording fails.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? STOOOOOOP! NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easiest way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot to mention ....!
Sources
build manifest
XDA:DevDB Information
gtexslte_eos-n_unofficial, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld(!)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-18
Last Updated 2020-11-18
Click to expand...
Click to collapse
I just flashed it and looks very nice thank you, titanium backup force closed, is there any restriction?
hotmatua.parulian said:
I just flashed it and looks very nice thank you, titanium backup force closed, is there any restriction?
Click to expand...
Click to collapse
Should work. Follow FAQ #1 in the second post